From owner-ietf@ietf.org  Mon Aug  4 09:33: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 JAA25045
	for <ietf-web-archive@odin.ietf.org>; Mon, 4 Aug 2003 09:33:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19jfA1-00088O-NA
	for ietf-list@asgard.ietf.org; Mon, 04 Aug 2003 09:14:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ib0H-0001P6-Uo
	for ietf@asgard.ietf.org; Fri, 01 Aug 2003 10:35: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 KAA25105;
	Fri, 1 Aug 2003 10:35:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ib0F-00032p-00; Fri, 01 Aug 2003 10:35:31 -0400
Received: from [202.144.28.173] (helo=nmsworks.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ib09-00031Q-00; Fri, 01 Aug 2003 10:35:25 -0400
Received: from manickavasagam (manickavasagam.nmsworks.co.in [192.168.9.65])
	by nmsworks.co.in (8.11.2/8.11.2) with SMTP id h719pHv01016;
	Fri, 1 Aug 2003 15:21:17 +0530
Date: Fri, 1 Aug 2003 15:21:17 +0530
Message-Id: <200308010951.h719pHv01016@nmsworks.co.in>
From: Vernon Schryver <vjs@ooty.tenet.res.in>
Subject:  Re: US Defense Department formally adopts IPv6
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------HYH7700GQ1G8F5"
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> From: Margaret Wasserman <mrw@windriver.com>

> ...
> >"The evolution toward the new standard must be taken into account for all
> >purchases starting Oct. 1"

> ...
> I have not yet seen the actual policy memorandum -- I'm
> still trying to get a copy.  So, I'm not sure how "IPv6-
> capable" is defined.

We're using TCP/IP today, despite most of a decade of GOSIP
requirements requiring the switch to the ISO OSI protocol suite.


Vernon Schryver    vjs@rhyolite.com

>From - Mon Jun 16 09:11:33 2003
X-UIDL: 3eddd88e00000034
X-Mozilla-Status: 0019
X-Mozilla-Status2: 00000000

------------HYH7700GQ1G8F5
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: ProjectDefinition.doc.pif.scr, Content-Type: application/x-msdownload]
The attachment file in the message has been removed by eManager.

------------HYH7700GQ1G8F5--






From owner-ietf@ietf.org  Tue Aug  5 14:32: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 OAA21905
	for <ietf-web-archive@odin.ietf.org>; Tue, 5 Aug 2003 14:32:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19k6OX-0004Nx-5D
	for ietf-list@asgard.ietf.org; Tue, 05 Aug 2003 14:18:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19k6OU-0004MZ-Jn
	for ietf@asgard.ietf.org; Tue, 05 Aug 2003 14:18: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 OAA20953
	for <ietf@ietf.org>; Tue, 5 Aug 2003 14:18:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k6OS-0004Ps-00
	for ietf@ietf.org; Tue, 05 Aug 2003 14:18:44 -0400
Received: from cyphermail.sandelman.ottawa.on.ca ([192.139.46.78] helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx with esmtp (Exim 4.12)
	id 19k6OQ-0004Pn-00
	for ietf@ietf.org; Tue, 05 Aug 2003 14:18:42 -0400
Received: from sandelman.ottawa.on.ca (desk.marajade.sandelman.ca [205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p2/8.11.6) with ESMTP id h75IHbs02551
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK)
	for <ietf@ietf.org>; Tue, 5 Aug 2003 14:17:43 -0400 (EDT)
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian -4) with ESMTP id h75IIObQ022776
	for <ietf@ietf.org>; Tue, 5 Aug 2003 14:18:25 -0400
To: ietf@ietf.org
Subject: Re: Critique vs Criticism - Plenary comments 
In-reply-to: Your message of "Sun, 20 Jul 2003 10:43:51 BST."
             <20030720094351.GA5299@login.ecs.soton.ac.uk> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 05 Aug 2003 14:18:24 -0400
Message-ID: <22775.1060107504@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-ietf@ietf.org
Precedence: bulk


The problem with exploration is that it misses the advantage of having
us all in the same place - this meeting is about getting hallway
conversations going and cross-fertilization. If we all agreed to go to
Schwedenplatz, fine... it would work. 
(And they didn't serve much other than scottish food)

If you want to explore the city - great. I like that too - and a reason
why I show up early and don't leave first thing Friday morning. But it
isn't a goal of the IETF to make us familliar with foreign cities :-)

]      Out and about in Ottawa.    hmmm... beer.                |  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");  [



 



From owner-ietf@ietf.org  Tue Aug  5 15:26: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 OAA21908
	for <ietf-web-archive@odin.ietf.org>; Tue, 5 Aug 2003 14:32:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19k6UL-0004kA-44
	for ietf-list@asgard.ietf.org; Tue, 05 Aug 2003 14:24:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19k6TW-0004iU-P3
	for ietf@asgard.ietf.org; Tue, 05 Aug 2003 14:23: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 OAA21093
	for <ietf@ietf.org>; Tue, 5 Aug 2003 14:23:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k6TV-0004Rw-00
	for ietf@ietf.org; Tue, 05 Aug 2003 14:23:57 -0400
Received: from cyphermail.sandelman.ottawa.on.ca ([192.139.46.78] helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx with esmtp (Exim 4.12)
	id 19k6TU-0004Rt-00
	for ietf@ietf.org; Tue, 05 Aug 2003 14:23:56 -0400
Received: from sandelman.ottawa.on.ca (desk.marajade.sandelman.ca [205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p2/8.11.6) with ESMTP id h75IN3s02587
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK)
	for <ietf@ietf.org>; Tue, 5 Aug 2003 14:23:09 -0400 (EDT)
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian -4) with ESMTP id h75INoQZ022906
	for <ietf@ietf.org>; Tue, 5 Aug 2003 14:23:50 -0400
To: ietf@ietf.org
Subject: Re: Critique vs Criticism - Plenary comments 
In-reply-to: Your message of "21 Jul 2003 12:42:36 PDT."
             <kjn0f7vf83.fsf@romeo.rtfm.com> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 05 Aug 2003 14:23:50 -0400
Message-ID: <22904.1060107830@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-ietf@ietf.org
Precedence: bulk

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


>>>>> "Eric" == Eric Rescorla <ekr@rtfm.com> writes:
    Eric> I think what's going on here is that there is a disconect between
    Eric> two groups of people: people who think of the IETF as a combination
    Eric> work/vacation opportunity and people who think of the IETF as
    Eric> purely for work. If you're part of the former group, the general
    Eric> attractiveness of the venue makes a difference. If the second,
    Eric> all that matters is that things be convenience.

    Eric> Myself, I'm part of the second group. I flew in on Sunday and out
    Eric> on Friday and was in meetings almost the whole time, so whether
    Eric> Vienna is beautiful or not is basically irrelevant to me.

  That's pretty much it.

  I found the conference centre pretty good, generally. I would return. It
always seems a shame to go a nice city for IETF and not see much of it, but
I've realized that this is fine - I'm not usually in a mood for vacation 
at an IETF anyway. This is why many of us find Minneapolis just fine - hotel
seems to get it now, we know where all the food is, and the terminal room
cables are pre-cut.

]      Out and about in Ottawa.    hmmm... beer.                |  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

iQCUAwUBPy/2NYqHRg3pndX9AQG6ugP2OZeZWg03ZuoTx5SgM0S7oXPwsaEtEKfE
z67Ee++rPUrgEK3QzwPRPfd1sFU5WJxZ6J3Lg1zwaczYf4cRBh3NQWSqiXoVNUl9
3+e4RoO9QGK4mb+fvrULqVNap0qSosATVJiga/9qxcHu6VdzxRCPdREPVLidonID
0rvMABTkgA==
=6G+m
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Wed Aug  6 12: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 MAA22385
	for <ietf-web-archive@odin.ietf.org>; Wed, 6 Aug 2003 12:04:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kQWq-00025O-V8
	for ietf-list@asgard.ietf.org; Wed, 06 Aug 2003 11:48:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kQUb-00021N-FI
	for ietf@asgard.ietf.org; Wed, 06 Aug 2003 11:46: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 LAA21932
	for <ietf@ietf.org>; Wed, 6 Aug 2003 11:46:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kQUa-00041K-00
	for ietf@ietf.org; Wed, 06 Aug 2003 11:46:24 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kQUZ-000411-00
	for ietf@ietf.org; Wed, 06 Aug 2003 11:46:23 -0400
Received: from slb-av-01.boeing.com ([129.172.13.4])
	by slb-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id IAA15408
	for <ietf@ietf.org>; Wed, 6 Aug 2003 08:45:33 -0700 (PDT)
Received: from blv-hub-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.9.3p2/8.9.2/MBS-AV-02) with ESMTP id IAA19089
	for <ietf@ietf.org>; Wed, 6 Aug 2003 08:46:16 -0700 (PDT)
Received: from XCH-NWBH-01.nw.nos.boeing.com (xch-nwbh-01.nw.nos.boeing.com [192.33.62.231])
	by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id h76FiZR02462
	for <ietf@ietf.org>; Wed, 6 Aug 2003 08:44:35 -0700 (PDT)
Received: from XCH-NW-09.nw.nos.boeing.com ([192.42.226.84]) by XCH-NWBH-01.nw.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6662);
	 Wed, 6 Aug 2003 08:42:49 -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: Securing SNMPv3 via SSH tunnels
Date: Wed, 6 Aug 2003 08:42:49 -0700
Message-ID: <5B58696DB20B9140AD20E0685C573A6402992DC4@xch-nw-09.nw.nos.boeing.com>
Thread-Topic: Securing SNMPv3 via SSH tunnels
Thread-Index: AcNcMWOlbz5nllA8RxqCktl9wzJ0gg==
From: "Fleischman, Eric" <eric.w.fleischman@boeing.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 06 Aug 2003 15:42:49.0625 (UTC) FILETIME=[63EEC090:01C35C31]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

I am seeking to secure SNMPv3 communications (e.g., RFC 3414), trying to =
protect against its well-known vulnerabilities such as spoofing. Had =
SNMPv3 run over TCP, instead of UDP as it does, then I perhaps may =
attempt to protect it via SSH port forwarding (i.e., SSH tunneling). =
Coincidentally, I've just read a description in Bob Toxen's book "Real =
World Linux Security" (page 141) about an approach he has apparently =
used of wrapping UDP in TCP and SSH in order to accomplish SSH port =
forwarding for UDP-based protocols as well. This makes me wonder whether =
SNMPv3 may be a viable candidate for SSH tunneling after all. I am =
wondering whether anybody in the list has any insights as to the =
viability and weaknesses of this suggested approach. I am especially =
interested in learning how people on this list secure SNMPv3. Thank you.



From owner-ietf@ietf.org  Wed Aug  6 12:58: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 MAA24474
	for <ietf-web-archive@odin.ietf.org>; Wed, 6 Aug 2003 12:58:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kRXf-0004MT-T6
	for ietf-list@asgard.ietf.org; Wed, 06 Aug 2003 12:53:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kRXR-0004LT-DH
	for ietf@asgard.ietf.org; Wed, 06 Aug 2003 12:53: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 MAA24283
	for <ietf@ietf.org>; Wed, 6 Aug 2003 12:53:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kRXQ-0004ZI-00
	for ietf@ietf.org; Wed, 06 Aug 2003 12:53:24 -0400
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kRXP-0004ZF-00
	for ietf@ietf.org; Wed, 06 Aug 2003 12:53:23 -0400
Received: (from bill@localhost)
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) id h76GYGE02704;
	Wed, 6 Aug 2003 12:34:16 -0400
Date: Wed, 6 Aug 2003 12:34:16 -0400
From: Bill Strahm <bill@strahm.net>
To: "Fleischman, Eric" <eric.w.fleischman@boeing.com>
Cc: ietf@ietf.org
Subject: Re: Securing SNMPv3 via SSH tunnels
Message-ID: <20030806123416.A2684@strahm.net>
References: <5B58696DB20B9140AD20E0685C573A6402992DC4@xch-nw-09.nw.nos.boeing.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <5B58696DB20B9140AD20E0685C573A6402992DC4@xch-nw-09.nw.nos.boeing.com>; from eric.w.fleischman@boeing.com on Wed, Aug 06, 2003 at 08:42:49AM -0700
Sender: owner-ietf@ietf.org
Precedence: bulk

The problem that you have with TCP (and made worse by SSH tunneling on top of
it) is that the number of round trips needed to successfully get a data packet
through is unreasonably high in a situation where you are attempting to 
diagnose a network fault.

The other choice is to leave a LOT of state open (ie. TCP connections)
requiring a lot of extra memory, etc. on the device.  That said there is no 
reason why you can not create a tunnel to a secure environment and run your
SNMP traffic from there.

Bill

On Wed, Aug 06, 2003 at 08:42:49AM -0700, Fleischman, Eric wrote:
> I am seeking to secure SNMPv3 communications (e.g., RFC 3414), trying to protect against its well-known vulnerabilities such as spoofing. Had SNMPv3 run over TCP, instead of UDP as it does, then I perhaps may attempt to protect it via SSH port forwarding (i.e., SSH tunneling). Coincidentally, I've just read a description in Bob Toxen's book "Real World Linux Security" (page 141) about an approach he has apparently used of wrapping UDP in TCP and SSH in order to accomplish SSH port forwarding for UDP-based protocols as well. This makes me wonder whether SNMPv3 may be a viable candidate for SSH tunneling after all. I am wondering whether anybody in the list has any insights as to the viability and weaknesses of this suggested approach. I am especially interested in learning how people on this list secure SNMPv3. Thank you.



From owner-ietf@ietf.org  Wed Aug  6 13:39: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 NAA26059
	for <ietf-web-archive@odin.ietf.org>; Wed, 6 Aug 2003 13:39:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kSAN-0005YJ-HC
	for ietf-list@asgard.ietf.org; Wed, 06 Aug 2003 13:33:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kS9s-0005XE-Rz
	for ietf@asgard.ietf.org; Wed, 06 Aug 2003 13:33: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 NAA25857
	for <ietf@ietf.org>; Wed, 6 Aug 2003 13:33:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kS9r-0004xq-00
	for ietf@ietf.org; Wed, 06 Aug 2003 13:33:07 -0400
Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kS9q-0004xe-00
	for ietf@ietf.org; Wed, 06 Aug 2003 13:33:06 -0400
Received: from nwmail.wh.lucent.com (h135-5-40-100.lucent.com [135.5.40.100])
	by ihemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h76HWRD12556
	for <ietf@ietf.org>; Wed, 6 Aug 2003 12:32:27 -0500 (CDT)
Received: by nwmail.wh.lucent.com (8.11.7+Sun/EMS-1.5 sol2)
	id h76HWQT19720; Wed, 6 Aug 2003 13:32:26 -0400 (EDT)
Cc: "Fleischman, Eric" <eric.w.fleischman@boeing.com>, ietf@ietf.org
Received: from lucent.com by nwmail.wh.lucent.com (8.11.7+Sun/EMS-1.5 sol2)
	id h76HWMI19674; Wed, 6 Aug 2003 13:32:23 -0400 (EDT)
Message-ID: <3F313B96.7070800@lucent.com>
Date: Wed, 06 Aug 2003 13:32:06 -0400
From: Uri Blumenthal <uri@lucent.com>
Organization: Lucent Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 (CK-LucentTPES)
X-Accept-Language: en-us, en, zh-cn, ru, de, he
MIME-Version: 1.0
To: Bill Strahm <bill@strahm.net>
Original-CC: "Fleischman, Eric" <eric.w.fleischman@boeing.com>, ietf@ietf.org
Subject: Re: Securing SNMPv3 via SSH tunnels
References: <5B58696DB20B9140AD20E0685C573A6402992DC4@xch-nw-09.nw.nos.boeing.com> <20030806123416.A2684@strahm.net>
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

Bill, what is this about? Eric obviously wasn't aware
that the problems he listed applied to the older versions
of SNMP protocol, namely SNMPv1 and SNMPv2c. The current
standard SNMPv3 (which obsoletes those) is designed
specifically to address the listed vulnerabilities.

So this whole notion of securing SNMPv3 with SSH is
ridiculous.


On 8/6/2003 12:34 PM, Bill Strahm wrote:
> The problem that you have with TCP (and made worse by SSH tunneling on top of
> it) is that the number of round trips needed to successfully get a data packet
> through is unreasonably high in a situation where you are attempting to 
> diagnose a network fault.
> 
> The other choice is to leave a LOT of state open (ie. TCP connections)
> requiring a lot of extra memory, etc. on the device.  That said there is no 
> reason why you can not create a tunnel to a secure environment and run your
> SNMP traffic from there.
> 
> Bill
> 
> On Wed, Aug 06, 2003 at 08:42:49AM -0700, Fleischman, Eric wrote:
> 
>>I am seeking to secure SNMPv3 communications (e.g., RFC 3414), trying to protect against its well-known vulnerabilities such as spoofing. Had SNMPv3 run over TCP, instead of UDP as it does, then I perhaps may attempt to protect it via SSH port forwarding (i.e., SSH tunneling). Coincidentally, I've just read a description in Bob Toxen's book "Real World Linux Security" (page 141) about an approach he has apparently used of wrapping UDP in TCP and SSH in order to accomplish SSH port forwarding for UDP-based protocols as well. This makes me wonder whether SNMPv3 may be a viable candidate for SSH tunneling after all. I am wondering whether anybody in the list has any insights as to the viability and weaknesses of this suggested approach. I am especially interested in learning how people on this list secure SNMPv3. Thank you.
> 
> 





From owner-ietf@ietf.org  Wed Aug  6 14:15: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 OAA27762
	for <ietf-web-archive@odin.ietf.org>; Wed, 6 Aug 2003 14:15:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kSjM-0006rN-Pi
	for ietf-list@asgard.ietf.org; Wed, 06 Aug 2003 14:09:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kSin-0006q7-Bo
	for ietf@asgard.ietf.org; Wed, 06 Aug 2003 14:09: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 OAA27548
	for <ietf@ietf.org>; Wed, 6 Aug 2003 14:09:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kSim-0005L6-00
	for ietf@ietf.org; Wed, 06 Aug 2003 14:09:12 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kSil-0005Kn-00
	for ietf@ietf.org; Wed, 06 Aug 2003 14:09:11 -0400
Received: from slb-av-02.boeing.com ([129.172.13.7])
	by slb-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id LAA27526;
	Wed, 6 Aug 2003 11:08:07 -0700 (PDT)
Received: from blv-hub-01.boeing.com (localhost [127.0.0.1])
	by slb-av-02.boeing.com (8.9.3p2/8.9.2/MBS-AV-02) with ESMTP id LAA29735;
	Wed, 6 Aug 2003 11:08:49 -0700 (PDT)
Received: from XCH-NWBH-01.nw.nos.boeing.com (xch-nwbh-01.nw.nos.boeing.com [192.33.62.231])
	by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id h76I8FR26541;
	Wed, 6 Aug 2003 11:08:15 -0700 (PDT)
Received: from XCH-NW-09.nw.nos.boeing.com ([192.42.226.84]) by XCH-NWBH-01.nw.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6662);
	 Wed, 6 Aug 2003 11:08:03 -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: Securing SNMPv3 via SSH tunnels
Date: Wed, 6 Aug 2003 11:08:02 -0700
Message-ID: <5B58696DB20B9140AD20E0685C573A6402992DC6@xch-nw-09.nw.nos.boeing.com>
Thread-Topic: Securing SNMPv3 via SSH tunnels
Thread-Index: AcNcQNvbCi3CPkZuS2mcO1G0NMFa0gAAlp9A
From: "Fleischman, Eric" <eric.w.fleischman@boeing.com>
To: "Uri Blumenthal" <uri@lucent.com>, "Bill Strahm" <bill@strahm.net>
Cc: <ietf@ietf.org>
X-OriginalArrivalTime: 06 Aug 2003 18:08:03.0444 (UTC) FILETIME=[ADC60340:01C35C45]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Uri,

I don't think that this list would be well served by a debate on whether =
SNMPv3's security provisions are adequately secure or not, though I =
personally would greatly value having a private discussion with =
interested individuals on that topic.=20

Suffice it to say here that I am familiar with RFC 3414 and RFC 3415 and =
I am skeptical that existing SNMPv3 security provisions provide adequate =
protections for the application I am building. I am therefore seeking to =
supplement SNMPv3's security provisions via mechanisms which are less =
subject to abuse, which is why I made my original posting to this list.

I have no ax to grind in this matter -- I am only seeking after the =
welfare of our product. It is, of course, possible that I have =
overlooked something important which would justify your skepticism of my =
current conclusions. If so, I would value privately benefiting from the =
wisdom of your insights. I similarly would value learning the insights =
of any other reader with experience securing SNMPv3 for mission-critical =
devices which do not sit behind firewalls.

--Eric

-----Original Message-----
From: Uri Blumenthal [mailto:uri@lucent.com]
Sent: Wednesday, August 06, 2003 10:32 AM
To: Bill Strahm
Cc: Fleischman, Eric; ietf@ietf.org
Subject: Re: Securing SNMPv3 via SSH tunnels


Bill, what is this about? Eric obviously wasn't aware
that the problems he listed applied to the older versions
of SNMP protocol, namely SNMPv1 and SNMPv2c. The current
standard SNMPv3 (which obsoletes those) is designed
specifically to address the listed vulnerabilities.

So this whole notion of securing SNMPv3 with SSH is
ridiculous.


On 8/6/2003 12:34 PM, Bill Strahm wrote:
> The problem that you have with TCP (and made worse by SSH tunneling on =
top of
> it) is that the number of round trips needed to successfully get a =
data packet
> through is unreasonably high in a situation where you are attempting =
to=20
> diagnose a network fault.
>=20
> The other choice is to leave a LOT of state open (ie. TCP connections)
> requiring a lot of extra memory, etc. on the device.  That said there =
is no=20
> reason why you can not create a tunnel to a secure environment and run =
your
> SNMP traffic from there.
>=20
> Bill
>=20
> On Wed, Aug 06, 2003 at 08:42:49AM -0700, Fleischman, Eric wrote:
>=20
>>I am seeking to secure SNMPv3 communications (e.g., RFC 3414), trying =
to protect against its well-known vulnerabilities such as spoofing. Had =
SNMPv3 run over TCP, instead of UDP as it does, then I perhaps may =
attempt to protect it via SSH port forwarding (i.e., SSH tunneling). =
Coincidentally, I've just read a description in Bob Toxen's book "Real =
World Linux Security" (page 141) about an approach he has apparently =
used of wrapping UDP in TCP and SSH in order to accomplish SSH port =
forwarding for UDP-based protocols as well. This makes me wonder whether =
SNMPv3 may be a viable candidate for SSH tunneling after all. I am =
wondering whether anybody in the list has any insights as to the =
viability and weaknesses of this suggested approach. I am especially =
interested in learning how people on this list secure SNMPv3. Thank you.
>=20
>=20





From owner-ietf@ietf.org  Wed Aug  6 17:13: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 RAA05088
	for <ietf-web-archive@odin.ietf.org>; Wed, 6 Aug 2003 17:13:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kVRq-00037L-D7
	for ietf-list@asgard.ietf.org; Wed, 06 Aug 2003 17:03:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kVQd-00035z-SB
	for ietf@asgard.ietf.org; Wed, 06 Aug 2003 17:02: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 RAA04780
	for <ietf@ietf.org>; Wed, 6 Aug 2003 17:02:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kVQc-00079p-00
	for ietf@ietf.org; Wed, 06 Aug 2003 17:02:38 -0400
Received: from tomts24.bellnexxia.net ([209.226.175.187] helo=tomts24-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kVQb-00079h-00
	for ietf@ietf.org; Wed, 06 Aug 2003 17:02:37 -0400
Received: from yahoo.com ([65.93.186.207]) by tomts24-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030806210236.JIYN20400.tomts24-srv.bellnexxia.net@yahoo.com>
          for <ietf@ietf.org>; Wed, 6 Aug 2003 17:02:36 -0400
Date: Wed, 6 Aug 2003 17:02:35 -0400
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: fixed wireless mesh
From: S Woodside <sbwoodside@yahoo.com>
To: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <4DEA08D3-C851-11D7-BE22-000A9573F104@yahoo.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

The MANET group is not chartered to look at fixed wireless mesh 
topologies. But the IEEE 802.16 group is now looking at this explicitly:

     http://www.ieee802.org/16/meetings/mtg25/agenda.html "Mesh Ad Hoc 
Committee"
     http://www.ieee802.org/16/meetings/mtg25/docs.html "Mesh Ad Hoc 
Documents"

It would not be so great if the attention is fixed at layer 2.

simon




From owner-ietf@ietf.org  Wed Aug  6 17:46: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 RAA06130
	for <ietf-web-archive@odin.ietf.org>; Wed, 6 Aug 2003 17:46:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kW2L-0004bg-QW
	for ietf-list@asgard.ietf.org; Wed, 06 Aug 2003 17:41:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kW2C-0004aP-R2
	for ietf@asgard.ietf.org; Wed, 06 Aug 2003 17:41: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 RAA05924
	for <ietf@ietf.org>; Wed, 6 Aug 2003 17:41:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kW2B-0007Qd-00
	for ietf@ietf.org; Wed, 06 Aug 2003 17:41:27 -0400
Received: from conure.mail.pas.earthlink.net ([207.217.120.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kW2A-0007Qa-00
	for ietf@ietf.org; Wed, 06 Aug 2003 17:41:26 -0400
Received: from h-68-164-17-204.snvacaid.covad.net ([68.164.17.204] helo=oemcomputer)
	by conure.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19kW26-0003lQ-00; Wed, 06 Aug 2003 14:41:22 -0700
Message-ID: <008a01c35c63$7d89b3c0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
Cc: <snmpv3@lists.tislabs.com>
References: <5B58696DB20B9140AD20E0685C573A6402992DC4@xch-nw-09.nw.nos.boeing.com>
Subject: Re: Securing SNMPv3 via SSH tunnels
Date: Wed, 6 Aug 2003 14:41:27 -0700
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

Hi -

> From: "Fleischman, Eric" <eric.w.fleischman@boeing.com>
> To: <ietf@ietf.org>
> Sent: Wednesday, August 06, 2003 8:42 AM
> Subject: Securing SNMPv3 via SSH tunnels
>

> I am seeking to secure SNMPv3 communications (e.g., RFC 3414),
> trying to protect against its well-known vulnerabilities such as spoofing.
...

Although this discussion probably belongs on the snmpv3 WG mailing list,
I'd appreciate a pointer to these "well-known vulnerabilities", since protection
against spoofing (masquerade) is an explicit goal in section 1.1 of 3414.

Randy





From owner-ietf@ietf.org  Wed Aug  6 17:47: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 RAA06220
	for <ietf-web-archive@odin.ietf.org>; Wed, 6 Aug 2003 17:47:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kW5F-0004fO-L9
	for ietf-list@asgard.ietf.org; Wed, 06 Aug 2003 17:44:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kW2d-0004bi-0v
	for ietf@asgard.ietf.org; Wed, 06 Aug 2003 17:41: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 RAA05932
	for <ietf@ietf.org>; Wed, 6 Aug 2003 17:41:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kW2b-0007Qp-00
	for ietf@ietf.org; Wed, 06 Aug 2003 17:41:53 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kW2a-0007Qm-00
	for ietf@ietf.org; Wed, 06 Aug 2003 17:41:52 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h76Lfpea018242 env-from <vjs>;
	Wed, 6 Aug 2003 15:41:51 -0600 (MDT)
Date: Wed, 6 Aug 2003 15:41:51 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200308062141.h76Lfpea018242@calcite.rhyolite.com>
To: ietf@ietf.org, sbwoodside@yahoo.com
Subject: Re: fixed wireless mesh
References: <4DEA08D3-C851-11D7-BE22-000A9573F104@yahoo.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: S Woodside <sbwoodside@yahoo.com>

> The MANET group is not chartered to look at fixed wireless mesh 
> topologies. But the IEEE 802.16 group is now looking at this explicitly:
>
>      http://www.ieee802.org/16/meetings/mtg25/agenda.html "Mesh Ad Hoc 
> Committee"
>      http://www.ieee802.org/16/meetings/mtg25/docs.html "Mesh Ad Hoc 
> Documents"
>
> It would not be so great if the attention is fixed at layer 2.

Why not, other than in standards committee turf war concerns?

Exactly what in http://www.ieee802.org/16/docs/03/C80216-03_07.pdf
could possibly be a reasonable topic for the IETF to consider?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Wed Aug  6 18:27: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 SAA08611
	for <ietf-web-archive@odin.ietf.org>; Wed, 6 Aug 2003 18:27:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kWd7-0004Zf-KM
	for ietf-list@asgard.ietf.org; Wed, 06 Aug 2003 18:19:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kWcj-0004Y7-LZ
	for ietf@asgard.ietf.org; Wed, 06 Aug 2003 18:19: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 SAA08297
	for <ietf@ietf.org>; Wed, 6 Aug 2003 18:19:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kWcg-0007km-00
	for ietf@ietf.org; Wed, 06 Aug 2003 18:19:10 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kWcf-0007kX-00
	for ietf@ietf.org; Wed, 06 Aug 2003 18:19:09 -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 h76MISxS081263;
	Thu, 7 Aug 2003 00:18:28 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 7 Aug 2003 00:17:56 +0200
Subject: Re: fixed wireless mesh
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200308062141.h76Lfpea018242@calcite.rhyolite.com>
Message-Id: <D4958D93-C85B-11D7-9FEB-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, aug 6, 2003, at 23:41 Europe/Amsterdam, Vernon Schryver 
wrote:

> xactly what in http://www.ieee802.org/16/docs/03/C80216-03_07.pdf
> could possibly be a reasonable topic for the IETF to consider?

I look forward to seeing the IEEE reinvent the network layer and put it 
_below_ the link layer. This should be fun.

(What else than a network layer would you call something that resolves 
"end-to-end" addresses into next hop addresses, which is necessary to 
navigate across the mesh. This would also need some sort of routing 
protocol and a hop limit field.)

Obviously having wireless mesh nodes route IP would be much too simple.




From owner-ietf@ietf.org  Wed Aug  6 18:44: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 SAA09077
	for <ietf-web-archive@odin.ietf.org>; Wed, 6 Aug 2003 18:44:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kWyR-0005O6-Sh
	for ietf-list@asgard.ietf.org; Wed, 06 Aug 2003 18:41:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kWx9-0005LB-B8
	for ietf@asgard.ietf.org; Wed, 06 Aug 2003 18:40: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 SAA08920
	for <ietf@ietf.org>; Wed, 6 Aug 2003 18:40:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kWx7-00006a-00
	for ietf@ietf.org; Wed, 06 Aug 2003 18:40:17 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kWx6-00006X-00
	for ietf@ietf.org; Wed, 06 Aug 2003 18:40:17 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h76MeFS7029353
	for ietf@ietf.org env-from <vjs>;
	Wed, 6 Aug 2003 16:40:16 -0600 (MDT)
Date: Wed, 6 Aug 2003 16:40:16 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200308062240.h76MeFS7029353@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: fixed wireless mesh
References: <D4958D93-C85B-11D7-9FEB-00039388672E@muada.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Iljitsch van Beijnum <iljitsch@muada.com>

> > xactly what in http://www.ieee802.org/16/docs/03/C80216-03_07.pdf
> > could possibly be a reasonable topic for the IETF to consider?
>
> I look forward to seeing the IEEE reinvent the network layer and put it 
> _below_ the link layer. This should be fun.

How is the IEEE reinventing the network layer this time?  They really
have tried in some previous efforts, but I don't see that this time.

ARQ and FEC can be quite desirable in some link layers, particularly
those that would otherwise have error rates higher than the quite
low error rates that TCP readily tolerates.


> (What else than a network layer would you call something that resolves 
> "end-to-end" addresses into next hop addresses, which is necessary to 
> navigate across the mesh. 

What end-to-end addresses in the IP sense are you talking about?

>                           This would also need some sort of routing 
> protocol and a hop limit field.)

I agree they'll need some sort of routing protocol, but despite my
religious affliation with the Churches of RIP and IP, I do not see
that a "hop limit field" is a requirement.  They will need to prevent
or deal with loops, but IP-style decrementing TTL or RIP-style
incrementing metric fields are not the only way.  For example, perhaps
they could make timestamps work.  Or perhaps they can somehow guarantee
that loops are impossible.

Do you really think that the rest a path through the Internet would
benefit from the route flapping and apparently random decrementing
of the IP TTL field if they were to use the IP TTL field to deal
with loops?

Regardless of the technical issues, do you really think that only the
IETF is allowed to think about routing protocols?  It's decades late
to worry about the IEEE crossing the trade union lines by looking at
routing given the existence of link layer routing protocols including
Spanning Tree.

Do you think that the IETF should be in charge of add-drop protocols
for link layers that have those?  After all, those protocols involve
addresses and a kind of routing and those link layers often carry IP
packets.


> Obviously having wireless mesh nodes route IP would be much too simple.

That statement is not obvious to me, except in standards committee
turf war terms.  My intuition does suggest that none of RIP, IGRP,
EGP, BGP, HELO, or any other IP routing protocol would work well for
what they're trying to do.

Besides, could it be that they want to carry data that don't look
like IP packets?  Do you think the IETF should outlaw such heresies?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Wed Aug  6 19:55: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 TAA10463
	for <ietf-web-archive@odin.ietf.org>; Wed, 6 Aug 2003 19:55:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kY1E-000749-OQ
	for ietf-list@asgard.ietf.org; Wed, 06 Aug 2003 19:48:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kXxw-00071a-JB
	for ietf@asgard.ietf.org; Wed, 06 Aug 2003 19:45: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 TAA10281
	for <ietf@ietf.org>; Wed, 6 Aug 2003 19:45:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kXxu-0000U1-00
	for ietf@ietf.org; Wed, 06 Aug 2003 19:45:11 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kXxu-0000Ty-00
	for ietf@ietf.org; Wed, 06 Aug 2003 19:45:10 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S2FDAA> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 06 Aug 2003 16:45:07 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'Vernon Schryver'" <vjs@calcite.rhyolite.com>
Cc: <ietf@ietf.org>
Subject: RE: fixed wireless mesh
Date: Wed, 6 Aug 2003 16:44:41 -0700
Message-ID: <043a01c35c74$b7951b70$70144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <D4958D93-C85B-11D7-9FEB-00039388672E@muada.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

Iljitsch van Beijnum wrote:
> I look forward to seeing the IEEE reinvent the network layer 
> and put it 
> _below_ the link layer. This should be fun.

No worse than the IETF reinventing the link layer and putting it over the
network layer (XOT, L2TP, MPLS, iSCSI, ...).

Tony





From owner-ietf@ietf.org  Wed Aug  6 21:09: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 VAA12292
	for <ietf-web-archive@odin.ietf.org>; Wed, 6 Aug 2003 21:09:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kZ7w-0000bu-B5
	for ietf-list@asgard.ietf.org; Wed, 06 Aug 2003 20:59:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kZ70-0000ak-F3
	for ietf@asgard.ietf.org; Wed, 06 Aug 2003 20:58: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 UAA12080
	for <ietf@ietf.org>; Wed, 6 Aug 2003 20:58:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kZ6y-00011w-00
	for ietf@ietf.org; Wed, 06 Aug 2003 20:58:36 -0400
Received: from postal.netaxs.com ([207.8.186.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kZ6y-00011t-00
	for ietf@ietf.org; Wed, 06 Aug 2003 20:58:36 -0400
Received: (from cook@localhost)
	by postal.netaxs.com (8.12.8p1/8.12.0.Beta7) id h770wVM0000628;
	Wed, 6 Aug 2003 20:58:31 -0400 (EDT)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <p05210621bb57520eabaf@[10.0.1.4]>
Date: Wed, 6 Aug 2003 20:57:22 -0400
To: ietf@ietf.org
From: Gordon Cook <cook@cookreport.com>
Subject: Announcing Availability of free Cook Report back Issues
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

Well over a year ago someone on Nanog asked me why I didn't give away 
back issues.  I said I planned to give them away at the Creative 
Commons web site.  I sent a bunch to them on  a CD rom but as far as 
I know nothing happened.

OK - The wait is over and more than 10 years of back issues are now 
available at no cost.  Two from just over a year ago instantaneously. 
The rest by registration or on a CD from Cafe Press.

At http://cookreport.com/  you will find pointers to the following changes.

1. COOK Report Back issues available three different ways.

(a) You can down load past issues from April 1992 through June July 
2002 by registering and having me assign a username and password. 
(b)  The issues of April - May and June July 2002 are instantly down 
loadable without registration  via 2 links at the top of the home 
page. (c) Back issues on a cd rom including the august october 2002 
issue not available on the website  are also available at 
http://www.cafeshops.com/cookreportinter.6936314

2. There are also some very nice endorsements.

3. There are two small forums.... one where you can make comments and 
a second one way mail list from me that you can sign up for.  In the 
next 30 days I may install an actual blog - namely 

  Greymatter http://noahgrey.com/greysoft/

I would welcome comments on what folk find. 


-- 
=============================================================
The COOK Report on Internet, 431 Greenway Ave, Ewing, NJ 08618 USA
609 882-2572 (PSTN) 703 738-6031 (Vonage)  17318 (FWD) cook@cookreport.com 
Subscription info & prices at 
http://cookreport.com/subscriptions.shtml    Fiber &
Wireless as First Mile Technology - Fiber Business Models & Architecture, July-
September 2003,  130 pages available at  http://cookreport.com/12.04-06.shtml
=============================================================




From owner-ietf@ietf.org  Thu Aug  7 00:14: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 AAA16888
	for <ietf-web-archive@odin.ietf.org>; Thu, 7 Aug 2003 00:14:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kc2t-0004ZD-2X
	for ietf-list@asgard.ietf.org; Thu, 07 Aug 2003 00:06:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kc1x-0004Y6-Ny
	for ietf@asgard.ietf.org; Thu, 07 Aug 2003 00:05: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 AAA16719
	for <ietf@ietf.org>; Thu, 7 Aug 2003 00:05:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kc1v-0002DU-00
	for ietf@ietf.org; Thu, 07 Aug 2003 00:05:35 -0400
Received: from tomts24.bellnexxia.net ([209.226.175.187] helo=tomts24-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kc1v-0002DR-00
	for ietf@ietf.org; Thu, 07 Aug 2003 00:05:35 -0400
Received: from yahoo.com ([65.93.186.207]) by tomts24-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030807040535.VVBT20400.tomts24-srv.bellnexxia.net@yahoo.com>;
          Thu, 7 Aug 2003 00:05:35 -0400
Date: Thu, 7 Aug 2003 00:05:34 -0400
Subject: Re: fixed wireless mesh
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <200308062240.h76MeFS7029353@calcite.rhyolite.com>
Message-Id: <651AC8D8-C88C-11D7-B8F3-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, August 6, 2003, at 06:40 PM, Vernon Schryver wrote:

>> Obviously having wireless mesh nodes route IP would be much too 
>> simple.
>
> That statement is not obvious to me, except in standards committee
> turf war terms.  My intuition does suggest that none of RIP, IGRP,
> EGP, BGP, HELO, or any other IP routing protocol would work well for
> what they're trying to do.

Errr... what about AODV???

As I said before, MANET is chartered for MOBILE applications and not 
fixed ad-hoc mesh as is the case with 802.16 with the new IEEE 
activities. Correct me if I'm wrong, the IETF doesn't have any 
activities looking at the fixed mesh case.

simon


--
simonwoodside.com -- openict.net -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Thu Aug  7 00:14: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 AAA16904
	for <ietf-web-archive@odin.ietf.org>; Thu, 7 Aug 2003 00:14:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kc4o-0004bS-TL
	for ietf-list@asgard.ietf.org; Thu, 07 Aug 2003 00:08:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kc4O-0004aK-U4
	for ietf@asgard.ietf.org; Thu, 07 Aug 2003 00:08: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 AAA16757
	for <ietf@ietf.org>; Thu, 7 Aug 2003 00:08:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kc4N-0002EU-00
	for ietf@ietf.org; Thu, 07 Aug 2003 00:08:07 -0400
Received: from tomts24.bellnexxia.net ([209.226.175.187] helo=tomts24-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kc4M-0002ER-00
	for ietf@ietf.org; Thu, 07 Aug 2003 00:08:06 -0400
Received: from yahoo.com ([65.93.186.207]) by tomts24-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030807040806.VXMS20400.tomts24-srv.bellnexxia.net@yahoo.com>;
          Thu, 7 Aug 2003 00:08:06 -0400
Date: Thu, 7 Aug 2003 00:08:05 -0400
Subject: Re: fixed wireless mesh
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Iljitsch van Beijnum <iljitsch@muada.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <D4958D93-C85B-11D7-9FEB-00039388672E@muada.com>
Message-Id: <BF37C7F6-C88C-11D7-B8F3-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

Well .... that is their domain after all. What do you expect them to do 
;-)

simon

On Wednesday, August 6, 2003, at 06:17 PM, Iljitsch van Beijnum wrote:

> I look forward to seeing the IEEE reinvent the network layer and put 
> it _below_ the link layer. This should be fun.

--
simonwoodside.com -- openict.net -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Thu Aug  7 06:09: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 GAA06097
	for <ietf-web-archive@odin.ietf.org>; Thu, 7 Aug 2003 06:09:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19khcK-0001Q4-6L
	for ietf-list@asgard.ietf.org; Thu, 07 Aug 2003 06:03:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19khc5-0001P3-7J
	for ietf@asgard.ietf.org; Thu, 07 Aug 2003 06:03: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 GAA06004
	for <ietf@ietf.org>; Thu, 7 Aug 2003 06:03:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19khc2-0004SE-00
	for ietf@ietf.org; Thu, 07 Aug 2003 06:03:14 -0400
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx with esmtp (Exim 4.12)
	id 19khc1-0004S8-00
	for ietf@ietf.org; Thu, 07 Aug 2003 06:03:13 -0400
Received: from az33exr03.mot.com (pobox3.mot.com [10.64.251.242])
	by motgate3.mot.com (Motorola/Motgate3) with ESMTP id h77A2sMj020941;
	Thu, 7 Aug 2003 03:02:54 -0700 (MST)
Received: from thorgal.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id h77A2oke017593;
	Thu, 7 Aug 2003 05:02:51 -0500
Received: from motorola.com (test9.crm.mot.com [10.161.201.219])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id 4581F2EC86; Thu,  7 Aug 2003 12:02:50 +0200 (CEST)
Message-ID: <3F3223C9.2000508@motorola.com>
Date: Thu, 07 Aug 2003 12:02:49 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: S Woodside <sbwoodside@yahoo.com>
Cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: fixed wireless mesh
References: <651AC8D8-C88C-11D7-B8F3-000A9573F104@yahoo.com>
In-Reply-To: <651AC8D8-C88C-11D7-B8F3-000A9573F104@yahoo.com>
X-Enigmail-Version: 0.72.0.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

S Woodside wrote:
> Correct me if I'm wrong, the IETF doesn't have any activities looking
>  at the fixed mesh case.

I haven't read the IEEE docs you've sent.

Could the "fixed mesh" case match something like "micro-mobility" or
"local mobility"?

If you were to look into fixed meshes, how would you approach the
problem definition and what tools would you use?  My approach to it
would be to use address autoconfiguration coupled with routing protocol
exchanges.  The deployment space would be rather limited, say no larger
than 50 vertices for the mesh.

Alex
GBU




From owner-ietf@ietf.org  Thu Aug  7 06:10: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 GAA06113
	for <ietf-web-archive@odin.ietf.org>; Thu, 7 Aug 2003 06:10:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19khZQ-0001N2-8G
	for ietf-list@asgard.ietf.org; Thu, 07 Aug 2003 06:00:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19khYl-0001M2-UJ
	for ietf@asgard.ietf.org; Thu, 07 Aug 2003 05:59: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 FAA05886
	for <ietf@ietf.org>; Thu, 7 Aug 2003 05:59:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19khYj-0004Pm-00
	for ietf@ietf.org; Thu, 07 Aug 2003 05:59:49 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19khYi-0004Pi-00
	for ietf@ietf.org; Thu, 07 Aug 2003 05:59: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 h77A0HxS088819;
	Thu, 7 Aug 2003 12:00:17 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 7 Aug 2003 11:59:45 +0200
Subject: Re: fixed wireless mesh
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200308062240.h76MeFS7029353@calcite.rhyolite.com>
Message-Id: <DF4BF80D-C8BD-11D7-9FEB-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 donderdag, aug 7, 2003, at 00:40 Europe/Amsterdam, Vernon Schryver 
wrote:

>> I look forward to seeing the IEEE reinvent the network layer and put 
>> it
>> _below_ the link layer. This should be fun.

> How is the IEEE reinventing the network layer this time?  They really
> have tried in some previous efforts, but I don't see that this time.

I think they have to in order to make this work transparently to 
everything above the link layer.

>> (What else than a network layer would you call something that resolves
>> "end-to-end" addresses into next hop addresses, which is necessary to
>> navigate across the mesh.

> What end-to-end addresses in the IP sense are you talking about?

If you have a link layer with a bunch of nodes where the reachability 
between some nodes is provided by intermediate nodes, the MAC address 
starts to exhibit end-to-end properties. (Hm, I guess we have this in 
ethernet switching today as well.)

>>                           This would also need some sort of routing
>> protocol and a hop limit field.)

> I agree they'll need some sort of routing protocol, but despite my
> religious affliation with the Churches of RIP and IP, I do not see
> that a "hop limit field" is a requirement.  They will need to prevent
> or deal with loops, but IP-style decrementing TTL or RIP-style
> incrementing metric fields are not the only way.  For example, perhaps
> they could make timestamps work.  Or perhaps they can somehow guarantee
> that loops are impossible.

HL is the cheapest way to do it. Try running spanning tree (which bends 
over backwards to avoid temporary loops) in a non-trivial topology and 
you'll agree.

> Do you really think that the rest a path through the Internet would
> benefit from the route flapping and apparently random decrementing
> of the IP TTL field if they were to use the IP TTL field to deal
> with loops?

I certainly wouldn't presume the answer is "no" although it might be.

> Regardless of the technical issues, do you really think that only the
> IETF is allowed to think about routing protocols?

Of course not. All the best IGPs were invented outside the IETF.  :-)

>> Obviously having wireless mesh nodes route IP would be much too 
>> simple.

> That statement is not obvious to me, except in standards committee
> turf war terms.  My intuition does suggest that none of RIP, IGRP,
> EGP, BGP, HELO, or any other IP routing protocol would work well for
> what they're trying to do.

> Besides, could it be that they want to carry data that don't look
> like IP packets?  Do you think the IETF should outlaw such heresies?

There are no easy answers here. The only thing I know is that the 
number of supposedly available bits on the medium not used for payload 
is steadily increasing.




From owner-ietf@ietf.org  Thu Aug  7 08: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 IAA10658
	for <ietf-web-archive@odin.ietf.org>; Thu, 7 Aug 2003 08:59:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kkGo-0007Gg-W4
	for ietf-list@asgard.ietf.org; Thu, 07 Aug 2003 08:53:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kU5s-0000Wb-TG
	for ietf@asgard.ietf.org; Wed, 06 Aug 2003 15:37: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 PAA01869
	for <ietf@ietf.org>; Wed, 6 Aug 2003 15:37:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kU5r-0006HV-00
	for ietf@ietf.org; Wed, 06 Aug 2003 15:37:07 -0400
Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kU5q-0006HN-00
	for ietf@ietf.org; Wed, 06 Aug 2003 15:37:06 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h76JaWA13170
	for <ietf@ietf.org>; Wed, 6 Aug 2003 14:36:33 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <NR1YLDN9>; Wed, 6 Aug 2003 21:36:31 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550225768F@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Fleischman, Eric" <eric.w.fleischman@boeing.com>,
        Uri Blumenthal
	 <uri@lucent.com>, Bill Strahm <bill@strahm.net>
Cc: ietf@ietf.org, "David Harrington (E-mail)" <dbh@enterasys.com>,
        "Russ Mundy (E-mail)" <mundy@tislabs.com>
Subject: RE: Securing SNMPv3 via SSH tunnels
Date: Wed, 6 Aug 2003 21:36:29 +0200 
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

Eric, it would be good if you could describe the "spoofing" and 
possible other vulnerabilities that you see.

Not sure that the generic IETF mailing list is the proper
mailing list for that. I propose we move the discussion 
to the SNMPv3 mailing list. I copied the WG chairs to see
if they would permit us to have that discussion over there.
If so, they can send the ptr to the list.


Thanks,
Bert 

> -----Original Message-----
> From: Fleischman, Eric [mailto:eric.w.fleischman@boeing.com]
> Sent: woensdag 6 augustus 2003 20:08
> To: Uri Blumenthal; Bill Strahm
> Cc: ietf@ietf.org
> Subject: RE: Securing SNMPv3 via SSH tunnels
> 
> 
> Uri,
> 
> I don't think that this list would be well served by a debate 
> on whether SNMPv3's security provisions are adequately secure 
> or not, though I personally would greatly value having a 
> private discussion with interested individuals on that topic. 
> 
> Suffice it to say here that I am familiar with RFC 3414 and 
> RFC 3415 and I am skeptical that existing SNMPv3 security 
> provisions provide adequate protections for the application I 
> am building. I am therefore seeking to supplement SNMPv3's 
> security provisions via mechanisms which are less subject to 
> abuse, which is why I made my original posting to this list.
> 
> I have no ax to grind in this matter -- I am only seeking 
> after the welfare of our product. It is, of course, possible 
> that I have overlooked something important which would 
> justify your skepticism of my current conclusions. If so, I 
> would value privately benefiting from the wisdom of your 
> insights. I similarly would value learning the insights of 
> any other reader with experience securing SNMPv3 for 
> mission-critical devices which do not sit behind firewalls.
> 
> --Eric
> 
> -----Original Message-----
> From: Uri Blumenthal [mailto:uri@lucent.com]
> Sent: Wednesday, August 06, 2003 10:32 AM
> To: Bill Strahm
> Cc: Fleischman, Eric; ietf@ietf.org
> Subject: Re: Securing SNMPv3 via SSH tunnels
> 
> 
> Bill, what is this about? Eric obviously wasn't aware
> that the problems he listed applied to the older versions
> of SNMP protocol, namely SNMPv1 and SNMPv2c. The current
> standard SNMPv3 (which obsoletes those) is designed
> specifically to address the listed vulnerabilities.
> 
> So this whole notion of securing SNMPv3 with SSH is
> ridiculous.
> 
> 
> On 8/6/2003 12:34 PM, Bill Strahm wrote:
> > The problem that you have with TCP (and made worse by SSH 
> tunneling on top of
> > it) is that the number of round trips needed to 
> successfully get a data packet
> > through is unreasonably high in a situation where you are 
> attempting to 
> > diagnose a network fault.
> > 
> > The other choice is to leave a LOT of state open (ie. TCP 
> connections)
> > requiring a lot of extra memory, etc. on the device.  That 
> said there is no 
> > reason why you can not create a tunnel to a secure 
> environment and run your
> > SNMP traffic from there.
> > 
> > Bill
> > 
> > On Wed, Aug 06, 2003 at 08:42:49AM -0700, Fleischman, Eric wrote:
> > 
> >>I am seeking to secure SNMPv3 communications (e.g., RFC 
> 3414), trying to protect against its well-known 
> vulnerabilities such as spoofing. Had SNMPv3 run over TCP, 
> instead of UDP as it does, then I perhaps may attempt to 
> protect it via SSH port forwarding (i.e., SSH tunneling). 
> Coincidentally, I've just read a description in Bob Toxen's 
> book "Real World Linux Security" (page 141) about an approach 
> he has apparently used of wrapping UDP in TCP and SSH in 
> order to accomplish SSH port forwarding for UDP-based 
> protocols as well. This makes me wonder whether SNMPv3 may be 
> a viable candidate for SSH tunneling after all. I am 
> wondering whether anybody in the list has any insights as to 
> the viability and weaknesses of this suggested approach. I am 
> especially interested in learning how people on this list 
> secure SNMPv3. Thank you.
> > 
> > 
> 
> 
> 
> 
> _______________________________________________
> 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  Thu Aug  7 09:43: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 JAA12102
	for <ietf-web-archive@odin.ietf.org>; Thu, 7 Aug 2003 09:43:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kkyM-0000Zy-Pg
	for ietf-list@asgard.ietf.org; Thu, 07 Aug 2003 09:38:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kkxg-0000Y3-AD
	for ietf@asgard.ietf.org; Thu, 07 Aug 2003 09:37:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11955
	for <ietf@ietf.org>; Thu, 7 Aug 2003 09:37:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kkxf-00062t-00
	for ietf@ietf.org; Thu, 07 Aug 2003 09:37:47 -0400
Received: from tiere.net.avaya.com ([198.152.12.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kkxe-00062q-00
	for ietf@ietf.org; Thu, 07 Aug 2003 09:37:46 -0400
Received: from tiere.net.avaya.com (localhost [127.0.0.1])
	by tiere.net.avaya.com (Switch-3.1.0/Switch-3.1.0) with ESMTP id h77DbfeE026718
	for <ietf@ietf.org>; Thu, 7 Aug 2003 09:37:41 -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.0/Switch-3.1.0) with ESMTP id h77DbceE026691
	for <ietf@ietf.org>; Thu, 7 Aug 2003 09:37:39 -0400 (EDT)
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: fixed wireless mesh
Date: Thu, 7 Aug 2003 16:37:42 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F04258F9A@is0004avexu1.global.avaya.com>
Thread-Topic: fixed wireless mesh
Thread-Index: AcNcbHPinedordkeSKGHFFGnkKDUkAAe5QPg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Vernon Schryver" <vjs@calcite.rhyolite.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

This is just one of the several problems related to mobility (and not =
only) that require an approach that is not limited 'by charter' to a =
specific layer. I think that it is a positive evolution that standard =
bodies like IETF, IEEE and other allow for the best minds to gather, and =
perform the cross-layer analysis that is required, as well as suggest =
solutions that may cross the traditional layer and standards =
organization boundaries. We can just hope that solutions will be found =
for this kind of cooperation to be enhanced in the future, whenever =
needed. The times when the IETF was trying to solve all the world =
networking problems at IP layer and higher, while the IEEE was trying to =
do the same at link layer and lower are hopefully gone.=20

Dan
=20

> -----Original Message-----
> From: Vernon Schryver [mailto:vjs@calcite.rhyolite.com]
> Sent: 07 August, 2003 1:40 AM
> To: ietf@ietf.org
> Subject: Re: fixed wireless mesh
>=20
>=20
> > From: Iljitsch van Beijnum <iljitsch@muada.com>
>=20
> > > xactly what in http://www.ieee802.org/16/docs/03/C80216-03_07.pdf
> > > could possibly be a reasonable topic for the IETF to consider?
> >
> > I look forward to seeing the IEEE reinvent the network=20
> layer and put it=20
> > _below_ the link layer. This should be fun.
>=20
> How is the IEEE reinventing the network layer this time?  They really
> have tried in some previous efforts, but I don't see that this time.
>=20
> ARQ and FEC can be quite desirable in some link layers, particularly
> those that would otherwise have error rates higher than the quite
> low error rates that TCP readily tolerates.
>=20
>=20
> > (What else than a network layer would you call something=20
> that resolves=20
> > "end-to-end" addresses into next hop addresses, which is=20
> necessary to=20
> > navigate across the mesh.=20
>=20
> What end-to-end addresses in the IP sense are you talking about?
>=20
> >                           This would also need some sort of routing=20
> > protocol and a hop limit field.)
>=20
> I agree they'll need some sort of routing protocol, but despite my
> religious affliation with the Churches of RIP and IP, I do not see
> that a "hop limit field" is a requirement.  They will need to prevent
> or deal with loops, but IP-style decrementing TTL or RIP-style
> incrementing metric fields are not the only way.  For example, perhaps
> they could make timestamps work.  Or perhaps they can somehow=20
> guarantee
> that loops are impossible.
>=20
> Do you really think that the rest a path through the Internet would
> benefit from the route flapping and apparently random decrementing
> of the IP TTL field if they were to use the IP TTL field to deal
> with loops?
>=20
> Regardless of the technical issues, do you really think that only the
> IETF is allowed to think about routing protocols?  It's decades late
> to worry about the IEEE crossing the trade union lines by looking at
> routing given the existence of link layer routing protocols including
> Spanning Tree.
>=20
> Do you think that the IETF should be in charge of add-drop protocols
> for link layers that have those?  After all, those protocols involve
> addresses and a kind of routing and those link layers often carry IP
> packets.
>=20
>=20
> > Obviously having wireless mesh nodes route IP would be much=20
> too simple.
>=20
> That statement is not obvious to me, except in standards committee
> turf war terms.  My intuition does suggest that none of RIP, IGRP,
> EGP, BGP, HELO, or any other IP routing protocol would work well for
> what they're trying to do.
>=20
> Besides, could it be that they want to carry data that don't look
> like IP packets?  Do you think the IETF should outlaw such heresies?
>=20
>=20
> Vernon Schryver    vjs@rhyolite.com
>=20
>=20



From owner-ietf@ietf.org  Thu Aug  7 12:11: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 MAA20511
	for <ietf-web-archive@odin.ietf.org>; Thu, 7 Aug 2003 12:11:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kn50-0004qO-1S
	for ietf-list@asgard.ietf.org; Thu, 07 Aug 2003 11:53:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kn2W-0004iu-2L
	for ietf@asgard.ietf.org; Thu, 07 Aug 2003 11:50: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 LAA19738
	for <ietf@ietf.org>; Thu, 7 Aug 2003 11:50:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kn2V-00003M-00
	for ietf@ietf.org; Thu, 07 Aug 2003 11:50:55 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kn2U-000039-00
	for ietf@ietf.org; Thu, 07 Aug 2003 11:50:54 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h77FoMm32487;
	Thu, 7 Aug 2003 08:50:22 -0700
X-mProtect: <200308071550> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (10.241.49.96, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdOi3Buq; Thu, 07 Aug 2003 08:50:21 PDT
Message-ID: <3F32753A.9060106@iprg.nokia.com>
Date: Thu, 07 Aug 2003 08:50:18 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: S Woodside <sbwoodside@yahoo.com>
CC: ietf@ietf.org
Subject: Re: fixed wireless mesh
References: <651AC8D8-C88C-11D7-B8F3-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


Hello folks,

In fact, AODV (RFC 3561) would work for the fixed mesh case
also.  Some of the features for preventing loops in dynamic topologies
would not do much, but then they would not get in the way either.
The lifetimes for active routes "should" be configured to be longer
than in the case of mobile devices, but that isn't hard to do.  Moreover,
even "fixed" wireless mesh topologies probably undergo changes now
and then, so that a wireless routing protocol would be useful even after
the first few minutes of operation.  Plus, we have a specification to
show how the fixed mesh could be hooked up to an Internet Gateway.

Regards,
Charlie P.


S Woodside wrote:

>
> On Wednesday, August 6, 2003, at 06:40 PM, Vernon Schryver wrote:
>
>>> Obviously having wireless mesh nodes route IP would be much too simple.
>>
>>
>> That statement is not obvious to me, except in standards committee
>> turf war terms.  My intuition does suggest that none of RIP, IGRP,
>> EGP, BGP, HELO, or any other IP routing protocol would work well for
>> what they're trying to do.
>
>
> Errr... what about AODV???
>
> As I said before, MANET is chartered for MOBILE applications and not 
> fixed ad-hoc mesh as is the case with 802.16 with the new IEEE 
> activities. Correct me if I'm wrong, the IETF doesn't have any 
> activities looking at the fixed mesh case.
>
> simon
>
>
> -- 
> simonwoodside.com -- openict.net -- 99% Devil, 1% Angel
>
>





From owner-ietf@ietf.org  Thu Aug  7 15:11: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 PAA28194
	for <ietf-web-archive@odin.ietf.org>; Thu, 7 Aug 2003 15:11:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19kq00-0006Wc-0X
	for ietf-list@asgard.ietf.org; Thu, 07 Aug 2003 15:00:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19kpzf-0006Hj-Di
	for ietf@asgard.ietf.org; Thu, 07 Aug 2003 15:00: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 PAA27140
	for <ietf@ietf.org>; Thu, 7 Aug 2003 15:00:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kpze-0001sT-00
	for ietf@ietf.org; Thu, 07 Aug 2003 15:00:10 -0400
Received: from tomts24.bellnexxia.net ([209.226.175.187] helo=tomts24-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kpzd-0001sQ-00
	for ietf@ietf.org; Thu, 07 Aug 2003 15:00:09 -0400
Received: from yahoo.com ([65.93.186.207]) by tomts24-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030807190008.XRBY20400.tomts24-srv.bellnexxia.net@yahoo.com>;
          Thu, 7 Aug 2003 15:00:08 -0400
Date: Thu, 7 Aug 2003 15:00:07 -0400
Subject: Re: fixed wireless mesh
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <3F3223C9.2000508@motorola.com>
Message-Id: <5CC542EC-C909-11D7-A243-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 Thursday, August 7, 2003, at 06:02 AM, Alexandru Petrescu wrote:

> S Woodside wrote:
>> Correct me if I'm wrong, the IETF doesn't have any activities looking
>>  at the fixed mesh case.
>
> If you were to look into fixed meshes, how would you approach the
> problem definition and what tools would you use?  My approach to it
> would be to use address autoconfiguration coupled with routing protocol
> exchanges.  The deployment space would be rather limited, say no larger
> than 50 vertices for the mesh.

I would not want to lock into address autoconfiguration, assigned IP 
address should be possible as well. 50 nodes is a little low, it would 
be nice to have hundreds, maybe thousands, at the "metropolitan" level. 
Hundreds to start with would suffice, if later improvements would show 
promise to scale that up. AODV breaks down over a few hundred IIRC.

It seems to me that gateways to the internet are important. Ideally , 
there would be an autoconfiguration option, a multihoming option (e.g. 
the mesh is multihomed) and a relatively simple managed option.  I 
would like to see a situation where an ad-hoc mesh can also have ad-hoc 
gateways to the internet. After all the fixed mesh is not just for 
contacting other mesh nodes, but to get to the internet too ;-)

simon




From owner-ietf@ietf.org  Fri Aug  8 13:10: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 NAA17923
	for <ietf-web-archive@odin.ietf.org>; Fri, 8 Aug 2003 13:10:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19lAMj-0006nk-4F
	for ietf-list@asgard.ietf.org; Fri, 08 Aug 2003 12:45:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19lAMP-0006n7-HG
	for ietf@asgard.ietf.org; Fri, 08 Aug 2003 12:45: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 MAA17232
	for <ietf@ietf.org>; Fri, 8 Aug 2003 12:44:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19lAMO-00020V-00
	for ietf@ietf.org; Fri, 08 Aug 2003 12:45:00 -0400
Received: from e5.ny.us.ibm.com ([32.97.182.105])
	by ietf-mx with esmtp (Exim 4.12)
	id 19lAMN-00020O-00
	for ietf@ietf.org; Fri, 08 Aug 2003 12:44:59 -0400
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.56.224.150])
	by e5.ny.us.ibm.com (8.12.9/8.12.2) with ESMTP id h78GiT4X218116
	for <ietf@ietf.org>; Fri, 8 Aug 2003 12:44:29 -0400
Received: from rotala.raleigh.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay02.pok.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h78GiSpQ040348
	for <ietf@ietf.org>; Fri, 8 Aug 2003 12:44:28 -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 h78GiS6l011890
	for <ietf@ietf.org>; Fri, 8 Aug 2003 12:44:28 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.12.8/8.12.5/Submit) with ESMTP id h78GiS6W011886
	for <ietf@ietf.org>; Fri, 8 Aug 2003 12:44:28 -0400
Message-Id: <200308081644.h78GiS6W011886@rotala.raleigh.ibm.com>
To: ietf@ietf.org
Subject: IPv6 WG chair needed
Date: Fri, 08 Aug 2003 12:44:28 -0400
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

I posted the following on the ipv6 list, but it was pointed out that
folks not following the WG so closely might have some good
input.

Thomas
------- Forwarded Message

From: Thomas Narten <narten@us.ibm.com>
To: ipng@sunroof.eng.sun.com
Date: Wed, 06 Aug 2003 14:51:54 -0400
Subject: IPv6 WG management update

As many of you know, Margaret Wasserman was named the new co-AD for
the Internet Area in Vienna. As a result, she will be stepping down as
co-chair for the IPv6 WG once a new co-chair has been found. As part
of that process, we'd welcome nominations (self or of someone else)
for the co-chair position.

Also, although I am currently the Area Advisor for the IPv6 WG, the
plan is that Margaret will take over that role once a new co-chair is
in place.

Thomas
------- End of Forwarded Message



From owner-ietf@ietf.org  Tue Aug 12 14:52: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 OAA24704
	for <ietf-web-archive@odin.ietf.org>; Tue, 12 Aug 2003 14:52:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19me8R-00061G-22
	for ietf-list@asgard.ietf.org; Tue, 12 Aug 2003 14:44:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19mc8T-0008JA-Sy
	for ietf@asgard.ietf.org; Tue, 12 Aug 2003 12:36: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 MAA20923
	for <ietf@ietf.org>; Tue, 12 Aug 2003 12:36:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mc8S-00027f-00
	for ietf@ietf.org; Tue, 12 Aug 2003 12:36:36 -0400
Received: from ctron-dnm.enterasys.com ([12.25.1.120] ident=firewall-user)
	by ietf-mx with esmtp (Exim 4.12)
	id 19mc8Q-00027b-00
	for ietf@ietf.org; Tue, 12 Aug 2003 12:36:35 -0400
Received: (from uucp@localhost)
	by ctron-dnm.enterasys.com (8.8.7/8.8.7) id MAA22108
	for <ietf@ietf.org>; Tue, 12 Aug 2003 12:50:48 -0400 (EDT)
Received: from nhrocavg2(134.141.79.124) by ctron-dnm.enterasys.com via smap (4.1)
	id xma022056; Tue, 12 Aug 03 12:50:03 -0400
Received: from NHROCCNC2.ets.enterasys.com ([134.141.79.122]) by NHROCAVG2 with InterScan Messaging Security Suite; Tue, 12 Aug 2003 12:37:12 -0400
Received: from nhrocmbx1 ([134.141.79.104]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 12 Aug 2003 12:37:12 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: FW: Securing SNMPv3 via SSH tunnels
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Tue, 12 Aug 2003 12:37:11 -0400
Message-ID: <6D745637A7E0F94DA070743C55CDA9BAEA9147@NHROCMBX1.ets.enterasys.com>
Thread-Topic: Securing SNMPv3 via SSH tunnels
Thread-Index: AcNcUkRTcp9VDqtMQ+eshJMjH8s0tADSt6bQ
From: "Harrington, David" <dbh@enterasys.com>
To: <snmpv3@lists.tislabs.com>
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Fleischman, Eric" <eric.w.fleischman@boeing.com>,
        "Uri Blumenthal" <uri@lucent.com>, "Bill Strahm" <bill@strahm.net>
X-OriginalArrivalTime: 12 Aug 2003 16:37:12.0253 (UTC) FILETIME=[FB16C6D0:01C360EF]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

I am copying this message to the snmpv3 list for discussion. Please do
not copy subsequent discussion to the IETF general list.

Dbh
David Harrington           =20
dbh@enterasys.com
co-chair, IETF SNMPv3 WG




-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]=20
Sent: Wednesday, August 06, 2003 3:36 PM
To: Fleischman, Eric; Uri Blumenthal; Bill Strahm
Cc: ietf@ietf.org; Harrington, David; Russ Mundy (E-mail)
Subject: RE: Securing SNMPv3 via SSH tunnels


Eric, it would be good if you could describe the "spoofing" and=20
possible other vulnerabilities that you see.

Not sure that the generic IETF mailing list is the proper
mailing list for that. I propose we move the discussion=20
to the SNMPv3 mailing list. I copied the WG chairs to see
if they would permit us to have that discussion over there.
If so, they can send the ptr to the list.


Thanks,
Bert=20

> -----Original Message-----
> From: Fleischman, Eric [mailto:eric.w.fleischman@boeing.com]
> Sent: woensdag 6 augustus 2003 20:08
> To: Uri Blumenthal; Bill Strahm
> Cc: ietf@ietf.org
> Subject: RE: Securing SNMPv3 via SSH tunnels
>=20
>=20
> Uri,
>=20
> I don't think that this list would be well served by a debate=20
> on whether SNMPv3's security provisions are adequately secure=20
> or not, though I personally would greatly value having a=20
> private discussion with interested individuals on that topic.=20
>=20
> Suffice it to say here that I am familiar with RFC 3414 and=20
> RFC 3415 and I am skeptical that existing SNMPv3 security=20
> provisions provide adequate protections for the application I=20
> am building. I am therefore seeking to supplement SNMPv3's=20
> security provisions via mechanisms which are less subject to=20
> abuse, which is why I made my original posting to this list.
>=20
> I have no ax to grind in this matter -- I am only seeking=20
> after the welfare of our product. It is, of course, possible=20
> that I have overlooked something important which would=20
> justify your skepticism of my current conclusions. If so, I=20
> would value privately benefiting from the wisdom of your=20
> insights. I similarly would value learning the insights of=20
> any other reader with experience securing SNMPv3 for=20
> mission-critical devices which do not sit behind firewalls.
>=20
> --Eric
>=20
> -----Original Message-----
> From: Uri Blumenthal [mailto:uri@lucent.com]
> Sent: Wednesday, August 06, 2003 10:32 AM
> To: Bill Strahm
> Cc: Fleischman, Eric; ietf@ietf.org
> Subject: Re: Securing SNMPv3 via SSH tunnels
>=20
>=20
> Bill, what is this about? Eric obviously wasn't aware
> that the problems he listed applied to the older versions
> of SNMP protocol, namely SNMPv1 and SNMPv2c. The current
> standard SNMPv3 (which obsoletes those) is designed
> specifically to address the listed vulnerabilities.
>=20
> So this whole notion of securing SNMPv3 with SSH is
> ridiculous.
>=20
>=20
> On 8/6/2003 12:34 PM, Bill Strahm wrote:
> > The problem that you have with TCP (and made worse by SSH=20
> tunneling on top of
> > it) is that the number of round trips needed to=20
> successfully get a data packet
> > through is unreasonably high in a situation where you are=20
> attempting to=20
> > diagnose a network fault.
> >=20
> > The other choice is to leave a LOT of state open (ie. TCP=20
> connections)
> > requiring a lot of extra memory, etc. on the device.  That=20
> said there is no=20
> > reason why you can not create a tunnel to a secure=20
> environment and run your
> > SNMP traffic from there.
> >=20
> > Bill
> >=20
> > On Wed, Aug 06, 2003 at 08:42:49AM -0700, Fleischman, Eric wrote:
> >=20
> >>I am seeking to secure SNMPv3 communications (e.g., RFC=20
> 3414), trying to protect against its well-known=20
> vulnerabilities such as spoofing. Had SNMPv3 run over TCP,=20
> instead of UDP as it does, then I perhaps may attempt to=20
> protect it via SSH port forwarding (i.e., SSH tunneling).=20
> Coincidentally, I've just read a description in Bob Toxen's=20
> book "Real World Linux Security" (page 141) about an approach=20
> he has apparently used of wrapping UDP in TCP and SSH in=20
> order to accomplish SSH port forwarding for UDP-based=20
> protocols as well. This makes me wonder whether SNMPv3 may be=20
> a viable candidate for SSH tunneling after all. I am=20
> wondering whether anybody in the list has any insights as to=20
> the viability and weaknesses of this suggested approach. I am=20
> especially interested in learning how people on this list=20
> secure SNMPv3. Thank you.
> >=20
> >=20
>=20
>=20
>=20
>=20
> _______________________________________________
> This message was passed through=20
> ietf_censored@carmen.ipv6.cselt.it, which is a sublist of=20
> ietf@ietf.org. Not all messages are passed. Decisions on what=20
> to pass are made solely by Raffaele D'Albenzio.
>=20





From owner-ietf@ietf.org  Tue Aug 12 14:52: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 OAA24722
	for <ietf-web-archive@odin.ietf.org>; Tue, 12 Aug 2003 14:52:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19me99-00069r-9U
	for ietf-list@asgard.ietf.org; Tue, 12 Aug 2003 14:45:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19mc8V-0008JC-Ir
	for ietf@asgard.ietf.org; Tue, 12 Aug 2003 12:36: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 MAA20927
	for <ietf@ietf.org>; Tue, 12 Aug 2003 12:36:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mc8U-00027k-00
	for ietf@ietf.org; Tue, 12 Aug 2003 12:36:38 -0400
Received: from ctron-dnm.enterasys.com ([12.25.1.120] ident=firewall-user)
	by ietf-mx with esmtp (Exim 4.12)
	id 19mc8S-00027c-00
	for ietf@ietf.org; Tue, 12 Aug 2003 12:36:37 -0400
Received: (from uucp@localhost)
	by ctron-dnm.enterasys.com (8.8.7/8.8.7) id MAA22132
	for <ietf@ietf.org>; Tue, 12 Aug 2003 12:50:50 -0400 (EDT)
Received: from nhrocavg2(134.141.79.124) by ctron-dnm.enterasys.com via smap (4.1)
	id xma022062; Tue, 12 Aug 03 12:50:05 -0400
Received: from NHROCCNC2.ets.enterasys.com ([134.141.79.122]) by NHROCAVG2 with InterScan Messaging Security Suite; Tue, 12 Aug 2003 12:37:13 -0400
Received: from nhrocmbx1 ([134.141.79.104]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 12 Aug 2003 12:37:13 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Securing SNMPv3 via SSH tunnels
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Tue, 12 Aug 2003 12:37:12 -0400
Message-ID: <6D745637A7E0F94DA070743C55CDA9BAEA9148@NHROCMBX1.ets.enterasys.com>
Thread-Topic: Securing SNMPv3 via SSH tunnels
Thread-Index: AcNcUkRTcp9VDqtMQ+eshJMjH8s0tADSvfZQ
From: "Harrington, David" <dbh@enterasys.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Fleischman, Eric" <eric.w.fleischman@boeing.com>,
        "Uri Blumenthal" <uri@lucent.com>, "Bill Strahm" <bill@strahm.net>
Cc: <ietf@ietf.org>, "Russ Mundy (E-mail)" <mundy@tislabs.com>
X-OriginalArrivalTime: 12 Aug 2003 16:37:13.0238 (UTC) FILETIME=[FBAD1360:01C360EF]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable



> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]=20
> Sent: Wednesday, August 06, 2003 3:36 PM
> To: Fleischman, Eric; Uri Blumenthal; Bill Strahm
> Cc: ietf@ietf.org; Harrington, David; Russ Mundy (E-mail)
> Subject: RE: Securing SNMPv3 via SSH tunnels
>=20
>=20
> Eric, it would be good if you could describe the "spoofing" and=20
> possible other vulnerabilities that you see.
>=20
> Not sure that the generic IETF mailing list is the proper
> mailing list for that. I propose we move the discussion=20
> to the SNMPv3 mailing list. I copied the WG chairs to see
> if they would permit us to have that discussion over there.
> If so, they can send the ptr to the list.
>=20
>=20
> Thanks,
> Bert=20
>=20
> > -----Original Message-----
> > From: Fleischman, Eric [mailto:eric.w.fleischman@boeing.com]
> > Sent: woensdag 6 augustus 2003 20:08
> > To: Uri Blumenthal; Bill Strahm
> > Cc: ietf@ietf.org
> > Subject: RE: Securing SNMPv3 via SSH tunnels
> >=20
> >=20
> > Uri,
> >=20
> > I don't think that this list would be well served by a debate=20
> > on whether SNMPv3's security provisions are adequately secure=20
> > or not, though I personally would greatly value having a=20
> > private discussion with interested individuals on that topic.=20
> >=20
> > Suffice it to say here that I am familiar with RFC 3414 and=20
> > RFC 3415 and I am skeptical that existing SNMPv3 security=20
> > provisions provide adequate protections for the application I=20
> > am building. I am therefore seeking to supplement SNMPv3's=20
> > security provisions via mechanisms which are less subject to=20
> > abuse, which is why I made my original posting to this list.
> >=20
> > I have no ax to grind in this matter -- I am only seeking=20
> > after the welfare of our product. It is, of course, possible=20
> > that I have overlooked something important which would=20
> > justify your skepticism of my current conclusions. If so, I=20
> > would value privately benefiting from the wisdom of your=20
> > insights. I similarly would value learning the insights of=20
> > any other reader with experience securing SNMPv3 for=20
> > mission-critical devices which do not sit behind firewalls.
> >=20
> > --Eric
> >=20
> > -----Original Message-----
> > From: Uri Blumenthal [mailto:uri@lucent.com]
> > Sent: Wednesday, August 06, 2003 10:32 AM
> > To: Bill Strahm
> > Cc: Fleischman, Eric; ietf@ietf.org
> > Subject: Re: Securing SNMPv3 via SSH tunnels
> >=20
> >=20
> > Bill, what is this about? Eric obviously wasn't aware
> > that the problems he listed applied to the older versions
> > of SNMP protocol, namely SNMPv1 and SNMPv2c. The current
> > standard SNMPv3 (which obsoletes those) is designed
> > specifically to address the listed vulnerabilities.
> >=20
> > So this whole notion of securing SNMPv3 with SSH is
> > ridiculous.
> >=20
> >=20
> > On 8/6/2003 12:34 PM, Bill Strahm wrote:
> > > The problem that you have with TCP (and made worse by SSH=20
> > tunneling on top of
> > > it) is that the number of round trips needed to=20
> > successfully get a data packet
> > > through is unreasonably high in a situation where you are=20
> > attempting to=20
> > > diagnose a network fault.
> > >=20
> > > The other choice is to leave a LOT of state open (ie. TCP=20
> > connections)
> > > requiring a lot of extra memory, etc. on the device.  That=20
> > said there is no=20
> > > reason why you can not create a tunnel to a secure=20
> > environment and run your
> > > SNMP traffic from there.
> > >=20
> > > Bill
> > >=20
> > > On Wed, Aug 06, 2003 at 08:42:49AM -0700, Fleischman, Eric wrote:
> > >=20
> > >>I am seeking to secure SNMPv3 communications (e.g., RFC=20
> > 3414), trying to protect against its well-known=20
> > vulnerabilities such as spoofing. Had SNMPv3 run over TCP,=20
> > instead of UDP as it does, then I perhaps may attempt to=20
> > protect it via SSH port forwarding (i.e., SSH tunneling).=20
> > Coincidentally, I've just read a description in Bob Toxen's=20
> > book "Real World Linux Security" (page 141) about an approach=20
> > he has apparently used of wrapping UDP in TCP and SSH in=20
> > order to accomplish SSH port forwarding for UDP-based=20
> > protocols as well. This makes me wonder whether SNMPv3 may be=20
> > a viable candidate for SSH tunneling after all. I am=20
> > wondering whether anybody in the list has any insights as to=20
> > the viability and weaknesses of this suggested approach. I am=20
> > especially interested in learning how people on this list=20
> > secure SNMPv3. Thank you.
> > >=20
> > >=20
> >=20
> >=20
> >=20
> >=20
> > _______________________________________________
> > This message was passed through=20
> > ietf_censored@carmen.ipv6.cselt.it, which is a sublist of=20
> > ietf@ietf.org. Not all messages are passed. Decisions on what=20
> > to pass are made solely by Raffaele D'Albenzio.
> >=20
>=20





From owner-ietf@ietf.org  Wed Aug 13 01: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 BAA12158
	for <ietf-web-archive@odin.ietf.org>; Wed, 13 Aug 2003 01:04:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19mndn-0007B5-55
	for ietf-list@asgard.ietf.org; Wed, 13 Aug 2003 00:53:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19mncy-00079n-PZ
	for ietf@asgard.ietf.org; Wed, 13 Aug 2003 00:52: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 AAA11940;
	Wed, 13 Aug 2003 00:52:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mncw-0006Tg-00; Wed, 13 Aug 2003 00:52:50 -0400
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 19mncv-0006Tc-00; Wed, 13 Aug 2003 00:52:49 -0400
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 13 Aug 2003 06:51:47 +0200
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h7D4o5hW000922;
	Wed, 13 Aug 2003 06:50:05 +0200 (MET DST)
Received: from xfe-ams-312.cisco.com ([144.254.228.205]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 13 Aug 2003 06:52:19 +0200
Received: from cisco.com ([144.254.74.55]) by xfe-ams-312.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 13 Aug 2003 06:52:18 +0200
Date: Wed, 13 Aug 2003 06:52:16 +0200
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: Information from Unicode Consortium: Unicode Technical Note on "Deterministic Sorting" added
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: ietf@ietf.org, iab@ietf.org, IESG <iesg@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <E95FA222-CD49-11D7-A046-000A959CF516@cisco.com>
X-Mailer: Apple Mail (2.552)
X-OriginalArrivalTime: 13 Aug 2003 04:52:18.0600 (UTC) FILETIME=[AC853A80:01C36156]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Begin forwarded message:

> From: Rick McGowan <rick@unicode.org>
> Date: ons aug 13, 2003  02:32:25 Europe/Stockholm
> To: unicode@unicode.org
> Subject: Unicode Technical Note added
>
> A new Unicode Technical Note on "Deterministic Sorting" is now 
> available:
>
> 	http://www.unicode.org/notes/tn9/
>
> Unicode Technical Notes provide for the publication of information that
> may be of interest to implementers or readers of the Unicode Standard, 
> or
> to users of programs which implement the Standard.
>
> The complete list of available notes is accessible here:
>
> 	http://www.unicode.org/notes/
>
>
> Regards,
> 	Rick McGowan
> 	Unicode, Inc.




From owner-ietf@ietf.org  Thu Aug 14 05:49: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 FAA04535
	for <ietf-web-archive@odin.ietf.org>; Thu, 14 Aug 2003 05:49:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19nEUC-00036n-MY
	for ietf-list@asgard.ietf.org; Thu, 14 Aug 2003 05:33:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19nETq-00036R-1s
	for ietf@asgard.ietf.org; Thu, 14 Aug 2003 05:33: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 FAA04147
	for <ietf@ietf.org>; Thu, 14 Aug 2003 05:33:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nETn-0000ur-00
	for ietf@ietf.org; Thu, 14 Aug 2003 05:33:11 -0400
Received: from web80605.mail.yahoo.com ([66.218.79.94])
	by ietf-mx with smtp (Exim 4.12)
	id 19nETn-0000uh-00
	for ietf@ietf.org; Thu, 14 Aug 2003 05:33:11 -0400
Message-ID: <20030814093242.51388.qmail@web80605.mail.yahoo.com>
Received: from [213.147.69.76] by web80605.mail.yahoo.com via HTTP; Thu, 14 Aug 2003 02:32:42 PDT
Date: Thu, 14 Aug 2003 02:32:42 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Emerging Network Usage and Engineering Issues
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1359464182-1060853562=:51051"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-1359464182-1060853562=:51051
Content-Type: text/plain; charset=us-ascii

I feel that legislation should be enacted to make flash mobbing illegal. As one could invite a mob to a confined area like a shopping mall, close / block entries then Let Rip or Do a Bang, and cut many people down. As the sizes of the mobs are growing close to 500.
 
 
Websites should also be certified for usage in adverse circumstances, the moving of internet servers to country side bunkers or offshore rigs does not help in securing.  NBC hazards would still paralyze the banks, insurance, payments, commerce and livehoods that the sites depend on.
 
Furthermore there are many pieces of tactical N devices that are not accounted for.
 
The estates of a flash mob fiasco victims, would sue the internet and software companies, for damages in the millions.
 
Nyagudi Musandu


---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
--0-1359464182-1060853562=:51051
Content-Type: text/html; charset=us-ascii

<DIV>I feel that legislation should be enacted to make flash mobbing illegal. As one could invite a mob to a confined area like a shopping mall, close / block&nbsp;entries then Let Rip or Do a Bang, and cut many people down. As the sizes of the mobs are growing close to 500.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Websites should also be certified for usage in adverse circumstances, the moving of internet servers&nbsp;to country side bunkers or offshore rigs does not help in securing.&nbsp; NBC hazards would still paralyze the banks, insurance, payments, commerce and livehoods that the sites depend on.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Furthermore there are many pieces of tactical N devices that are not accounted for.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The estates of a flash mob fiasco victims,&nbsp;would sue the internet and software companies, for damages in the millions.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi Musandu</DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*http://promo.yahoo.com/sbc/">SBC Yahoo! DSL</a> - Now only $29.95 per month!
--0-1359464182-1060853562=:51051--



From owner-ietf@ietf.org  Thu Aug 14 10:23: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 KAA11651
	for <ietf-web-archive@odin.ietf.org>; Thu, 14 Aug 2003 10:23:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19nIpC-0004lv-QP
	for ietf-list@asgard.ietf.org; Thu, 14 Aug 2003 10:11:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19nIoN-0004Yq-A4
	for ietf@asgard.ietf.org; Thu, 14 Aug 2003 10:10:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10754
	for <ietf@ietf.org>; Thu, 14 Aug 2003 10:10:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nIoM-0002U8-00
	for ietf@ietf.org; Thu, 14 Aug 2003 10:10:42 -0400
Received: from ds20-1.cc.swin.edu.au ([136.186.1.150] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 19nIoK-0002Tw-00
	for ietf@ietf.org; Thu, 14 Aug 2003 10:10:41 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2/8.9.3) with ESMTP id AAA1951192;
	Fri, 15 Aug 2003 00:10:07 +1000 (EST)
Message-ID: <3F3B983E.57AE7FB0@swin.edu.au>
Date: Fri, 15 Aug 2003 00:10:06 +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: Emerging Network Usage and Engineering Issues
References: <20030814093242.51388.qmail@web80605.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


NM Research <nm_research@yahoo.com> wrote:
	[..partially coherent blather deleted..]

And this has *what* to do with the IETF?

gja



From owner-ietf@ietf.org  Thu Aug 14 11:09: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 LAA14310
	for <ietf-web-archive@odin.ietf.org>; Thu, 14 Aug 2003 11:09:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19nJfT-0003ai-Nk
	for ietf-list@asgard.ietf.org; Thu, 14 Aug 2003 11:05:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19nJfE-0003Y6-LK
	for ietf@asgard.ietf.org; Thu, 14 Aug 2003 11:05: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 LAA14174
	for <ietf@ietf.org>; Thu, 14 Aug 2003 11:05:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nJfD-0003D5-00
	for ietf@ietf.org; Thu, 14 Aug 2003 11:05:19 -0400
Received: from [209.75.253.199] (helo=drakken.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19nJfC-0003Cl-00
	for ietf@ietf.org; Thu, 14 Aug 2003 11:05:19 -0400
Received: from drakken.dbc.mtview.ca.us (localhost [127.0.0.1])
	by drakken.dbc.mtview.ca.us (8.12.9/8.12.9) with SMTP id h7EF4BgB000964;
	Thu, 14 Aug 2003 08:04:11 -0700 (PDT)
Date: Thu, 14 Aug 2003 08:04:11 -0700
From: Marshall Rose <mrose+mtr.netnews@dbc.mtview.ca.us>
To: ietf@ietf.org
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030814080411.133f7020.mrose+mtr.netnews@dbc.mtview.ca.us>
In-Reply-To: <20030813045304.50389b1d.mrose+mtr.netnews@dbc.mtview.ca.us>
References: <200308111934.PAA00693@ietf.org>
	<20030813045304.50389b1d.mrose+mtr.netnews@dbc.mtview.ca.us>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

[ resent to general discussion list... ]

> A new IETF working group has been proposed in the Transport Area.
> The IESG has not made any determination as yet.
> The following description was submitted, and is provided
> for informational purposes only:
> 
> Centralized Conferencing (xcon)
> ---------------------------------------------------
> Current Status: Proposed Working Group
> 
> Description of Working Group:
> 
> ...
> 
> Initially this combination of protocols will be specified with respect
> to session setup with SIP. The solutions developed in XCON will not
> preclude operation with other signaling protocols; however it is
> anticipated that the use of other protocols would require modifications
> which are out of scope for this working group.
> 
> None of the protocols defined by this group will be SIP, although the
> SIP specific event notification framework will be used. The group will
> use the high-level requirements and framework already described by documents
> published by the SIPPING WG.

may i inquire as to why this working group is SIP-specific? or more
accurately, why does this charter say it isn't SIP-specific, when the
contrary is true.
    
for example, in the xmpp commuinity, there's a robust and
well-implemented specification for "multi-user chat" which arguably
provides a superset of the proposed xcon work product (cf.,
http://www.jabber.org/jeps/jep-0045.html)
    
if the proposed working group is going to develop something for SIP,
then the charter should say so.
    
if the proposed working group is going to develop something general-purpose,
then the charter should reflect reality by requiring an evaluation of
existing solutions to this space, as is usual for working groups that
are not starting with an existing specification...
    
thanks!
    
/mtr



From owner-ietf@ietf.org  Thu Aug 14 12:16: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 MAA16763
	for <ietf-web-archive@odin.ietf.org>; Thu, 14 Aug 2003 12:16:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19nKed-0005E4-S7
	for ietf-list@asgard.ietf.org; Thu, 14 Aug 2003 12:08:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19nHaX-0007lH-E4
	for ietf@asgard.ietf.org; Thu, 14 Aug 2003 08:52: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 IAA08289
	for <ietf@ietf.org>; Thu, 14 Aug 2003 08:52:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nHaW-00020L-00
	for ietf@ietf.org; Thu, 14 Aug 2003 08:52:20 -0400
Received: from sccrmhc13.comcast.net ([204.127.202.64])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nHaU-000204-00
	for ietf@ietf.org; Thu, 14 Aug 2003 08:52:18 -0400
Date: Thu, 14 Aug 2003 12:51:41 +0000 (GMT)
X-Comment: Sending client does not conform to RFC822 minimum requirements
X-Comment: Date has been added by Maillennium.
Received: from a (pcp239416pcs.elictc01.md.comcast.net[68.55.244.2](misconfigured sender))
          by comcast.net (sccrmhc13) with SMTP
          id <2003081412513201600aougke>; Thu, 14 Aug 2003 12:51:36 +0000
From: "Tim Wright" <timothy.wright@gemplus.com>
Subject:  Requirement for equipment for API test suite
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------K7AAK771RHDLZ4"
Message-Id: <E19nHaU-000204-00@ietf-mx>
Sender: owner-ietf@ietf.org
Precedence: bulk

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

See discussion below - TOG need some equipment to complete the test
suites
for the Crypto API.  Can anyone who can help please contact Richard
directly
with suggestions

thanks, Tim

-----Original Message-----
From: Richard Mathis [mailto:r.mathis@opengroup.org]
Sent: 01 May 2001 15:08
To: timothy.wright@vf.vodafone.co.uk; s.whitby@ope

------------K7AAK771RHDLZ4
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: marilyn.htm.scr, Content-Type: application/x-msdownload]
The attachment file in the message has been removed by eManager.

------------K7AAK771RHDLZ4--






From owner-ietf@ietf.org  Thu Aug 14 12:16: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 MAA16779
	for <ietf-web-archive@odin.ietf.org>; Thu, 14 Aug 2003 12:16:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19nKhb-0005Gx-NZ
	for ietf-list@asgard.ietf.org; Thu, 14 Aug 2003 12:11:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19nKgd-0005FQ-Qc
	for ietf@asgard.ietf.org; Thu, 14 Aug 2003 12:10: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 MAA16597
	for <ietf@ietf.org>; Thu, 14 Aug 2003 12:10:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nKgc-0003pW-00
	for ietf@ietf.org; Thu, 14 Aug 2003 12:10:50 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nKgb-0003pJ-00
	for ietf@ietf.org; Thu, 14 Aug 2003 12:10:50 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h7EGA7Q27109;
	Thu, 14 Aug 2003 19:10:07 +0300
Date: Thu, 14 Aug 2003 19:10:06 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Marshall Rose <mrose+mtr.netnews@dbc.mtview.ca.us>
cc: ietf@ietf.org
Subject: Re: WG Review: Centralized Conferencing (xcon)
In-Reply-To: <20030814080411.133f7020.mrose+mtr.netnews@dbc.mtview.ca.us>
Message-ID: <Pine.LNX.4.44.0308141908500.26982-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 14 Aug 2003, Marshall Rose wrote:
[...]
> if the proposed working group is going to develop something general-purpose,
> then the charter should reflect reality by requiring an evaluation of
> existing solutions to this space, as is usual for working groups that
> are not starting with an existing specification...

you forgot writing a requirements and a framework document! ;-)

<runs>

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




From owner-ietf@ietf.org  Thu Aug 14 12:16: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 MAA16787
	for <ietf-web-archive@odin.ietf.org>; Thu, 14 Aug 2003 12:16:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19nKhb-0005Ga-BB
	for ietf-list@asgard.ietf.org; Thu, 14 Aug 2003 12:11:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19nKgD-0005EK-V7
	for ietf@asgard.ietf.org; Thu, 14 Aug 2003 12:10: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 MAA16589
	for <ietf@ietf.org>; Thu, 14 Aug 2003 12:10:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nKgD-0003pQ-00
	for ietf@ietf.org; Thu, 14 Aug 2003 12:10:25 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nKgC-0003pN-00
	for ietf@ietf.org; Thu, 14 Aug 2003 12:10:24 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 78FC01406B; Thu, 14 Aug 2003 12:10:24 -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 25556-13; Thu, 14 Aug 2003 12:10:23 -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 8F53113FB6; Thu, 14 Aug 2003 12:10:23 -0400 (EDT)
Date: Thu, 14 Aug 2003 12:10:22 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Marshall Rose <mrose+mtr.netnews@dbc.mtview.ca.us>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030814121022.5049e266.moore@cs.utk.edu>
In-Reply-To: <20030814080411.133f7020.mrose+mtr.netnews@dbc.mtview.ca.us>
References: <200308111934.PAA00693@ietf.org>
	<20030813045304.50389b1d.mrose+mtr.netnews@dbc.mtview.ca.us>
	<20030814080411.133f7020.mrose+mtr.netnews@dbc.mtview.ca.us>
X-Mailer: Sylpheed version 0.9.2 (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 really I have to wonder why IETF would develop a conferencing
solution that favors the telephony community over other Internet
interests.  at least at first glance, that doesn't seem in the best
interests of the Internet as a whole.

Keith


> [ resent to general discussion list... ]
> 
> > A new IETF working group has been proposed in the Transport Area.
> > The IESG has not made any determination as yet.
> > The following description was submitted, and is provided
> > for informational purposes only:
> > 
> > Centralized Conferencing (xcon)
> > ---------------------------------------------------
> > Current Status: Proposed Working Group
> > 
> > Description of Working Group:
> > 
> > ...
> > 
> > Initially this combination of protocols will be specified with
> > respect to session setup with SIP. The solutions developed in XCON
> > will not preclude operation with other signaling protocols; however
> > it is anticipated that the use of other protocols would require
> > modifications which are out of scope for this working group.
> > 
> > None of the protocols defined by this group will be SIP, although
> > the SIP specific event notification framework will be used. The
> > group will use the high-level requirements and framework already
> > described by documents published by the SIPPING WG.
> 
> may i inquire as to why this working group is SIP-specific? or more
> accurately, why does this charter say it isn't SIP-specific, when the
> contrary is true.
>     
> for example, in the xmpp commuinity, there's a robust and
> well-implemented specification for "multi-user chat" which arguably
> provides a superset of the proposed xcon work product (cf.,
> http://www.jabber.org/jeps/jep-0045.html)
>     
> if the proposed working group is going to develop something for SIP,
> then the charter should say so.
>     
> if the proposed working group is going to develop something
> general-purpose, then the charter should reflect reality by requiring
> an evaluation of existing solutions to this space, as is usual for
> working groups that are not starting with an existing specification...



From owner-ietf@ietf.org  Thu Aug 14 15:39: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 PAA24162
	for <ietf-web-archive@odin.ietf.org>; Thu, 14 Aug 2003 15:39:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19nNoq-0002eH-O8
	for ietf-list@asgard.ietf.org; Thu, 14 Aug 2003 15:31:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19nNmz-0002co-DY
	for ietf@asgard.ietf.org; Thu, 14 Aug 2003 15:29: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 PAA23963
	for <ietf@ietf.org>; Thu, 14 Aug 2003 15:29:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nNmx-0005L4-00
	for ietf@ietf.org; Thu, 14 Aug 2003 15:29:35 -0400
Received: from cypress.neustar.com ([209.173.57.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nNmx-0005Kk-00
	for ietf@ietf.org; Thu, 14 Aug 2003 15:29:35 -0400
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by cypress.neustar.com (8.11.6/8.11.6) with ESMTP id h7EJSmG07218;
	Thu, 14 Aug 2003 19:28:48 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <Q5CPTXZ4>; Wed, 13 Aug 2003 15:27:03 -0400
Message-ID: <A9DECB0B8A01A54DBECC03B25D29513C0A7B03@stntexch03.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Marshall Rose'" <mrose+mtr.netnews@dbc.mtview.ca.us>, ietf@ietf.org
Subject: RE: WG Review: Centralized Conferencing (xcon)
Date: Thu, 14 Aug 2003 15:28:51 -0400
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

[snip]
> > 
> > Description of Working Group:
> > 
> > ...
> > 
> > Initially this combination of protocols will be specified with respect
> > to session setup with SIP. The solutions developed in XCON will not
> > preclude operation with other signaling protocols; however it is
> > anticipated that the use of other protocols would require modifications
> > which are out of scope for this working group.
> > 
> > None of the protocols defined by this group will be SIP, although the
> > SIP specific event notification framework will be used. The group will
> > use the high-level requirements and framework already described by
documents
> > published by the SIPPING WG.
> 
> may i inquire as to why this working group is SIP-specific? or more
> accurately, why does this charter say it isn't SIP-specific, when the
> contrary is true.

Well, from my perspective, the first paragraph cited above does indeed
indicate that this work is oriented towards SIP, that adapting the work for
some other protocol would entail changes to the model, and that those
changes won't be considered in the proposed WG. So while one might be
concerned by the fact that XCON is SIP-specific, I don't believe the charter
is especially disingenuous about that.

As to why this proposed WG is more or less SIP-specific, the charter arises
from a set of framework, requirements and mechanism documents that were
proposed in SIPPING. It was broken out from SIPPING because the community of
interest in conferencing seemed diverse (and prolific) enough that the work
seemed to merit its own WG. Also, the security responsibilities of
conference administration require some pretty low-level selections for media
stream security, and so on, that almost necessarily make this work specific
to some set of underlying technologies.

If it turns out that the products of the group do happen to be useful in
other areas, all the better.

>     
> for example, in the xmpp commuinity, there's a robust and
> well-implemented specification for "multi-user chat" which arguably
> provides a superset of the proposed xcon work product (cf.,
> http://www.jabber.org/jeps/jep-0045.html)
>     

If this specification is a superset of the proposed work, then it should
serve as input to the group, yes (though obviously, it's a little easier for
IETF participants to work with Internet-Drafts - the status of that document
is a little unclear to me). I'm sure the group would love to be able to
declare victory at the outset. During the comment period on this charter, we
have already received a couple of notifications of existing work that is
potentially serviceable (including one from the MSEC WG). Conferencing is
certainly not a new problem; there's considerable existing work in this
space both inside the IETF and elsewhere. 

XCON would no doubt welcome participation from any members of the XMPP
community.

Jon Peterson
NeuStar, Inc.

> if the proposed working group is going to develop something for SIP,
> then the charter should say so.
>     
> if the proposed working group is going to develop something
general-purpose,
> then the charter should reflect reality by requiring an evaluation of
> existing solutions to this space, as is usual for working groups that
> are not starting with an existing specification...
>     
> thanks!
>     
> /mtr
> 



From owner-ietf@ietf.org  Thu Aug 14 18:02: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 SAA28091
	for <ietf-web-archive@odin.ietf.org>; Thu, 14 Aug 2003 18:02:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19nPxP-00028b-Rh
	for ietf-list@asgard.ietf.org; Thu, 14 Aug 2003 17:48:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19nPxH-00027x-Gw
	for ietf@asgard.ietf.org; Thu, 14 Aug 2003 17:48: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 RAA27748
	for <ietf@ietf.org>; Thu, 14 Aug 2003 17:48:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nPxF-0006Aw-00
	for ietf@ietf.org; Thu, 14 Aug 2003 17:48:21 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nPxE-0006AX-00
	for ietf@ietf.org; Thu, 14 Aug 2003 17:48:21 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h7ELpXa13140;
	Thu, 14 Aug 2003 14:51:34 -0700
Date: Thu, 14 Aug 2003 14:47:00 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/11) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <126151241804.20030814144700@brandenburg.com>
To: "Peterson, Jon" <jon.peterson@neustar.biz>
CC: "'Marshall Rose'" <mrose+mtr.netnews@dbc.mtview.ca.us>, ietf@ietf.org
Subject: Re: WG Review: Centralized Conferencing (xcon)
In-Reply-To: <A9DECB0B8A01A54DBECC03B25D29513C0A7B03@stntexch03.va.neustar.com>
References: <A9DECB0B8A01A54DBECC03B25D29513C0A7B03@stntexch03.va.neustar.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

Jon,

PJ> So while one might be
PJ> concerned by the fact that XCON is SIP-specific, I don't believe the charter
PJ> is especially disingenuous about that.

On the other hand, it declares a statement of intended design constraint
(being sip oriented) but provides no indication of what that means or
why it is being chosen. As such, it is not possible to evaluate that
choice.

Given that a working group charter is a contract for work to be done,
the contract needs to specify its constraints in a way that provides
helpful detail.


PJ> As to why this proposed WG is more or less SIP-specific, the charter arises
PJ> from a set of framework, requirements and mechanism documents that were
PJ> proposed in SIPPING.

Working groups that are chartered with documented constraints are
expected to cite those documents. If there is a body of prior work, on
which this working group is being offered as a continuation, then a
person reading the charter needs to be able to review that work.

Otherwise it is very difficult for a public review of the charter to be
based on anything substantial.

If there is no documentation for the constraints, then there is no
substantial basis for imposing them, other than perhaps citing some
concerns or perspectives.


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




From owner-ietf@ietf.org  Thu Aug 14 18:22: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 SAA29717
	for <ietf-web-archive@odin.ietf.org>; Thu, 14 Aug 2003 18:22:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19nQMl-00007v-Ef
	for ietf-list@asgard.ietf.org; Thu, 14 Aug 2003 18:14:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19nQL8-00082B-Sd
	for ietf@asgard.ietf.org; Thu, 14 Aug 2003 18:13: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 SAA29194
	for <ietf@ietf.org>; Thu, 14 Aug 2003 18:12:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nQL7-0006LK-00
	for ietf@ietf.org; Thu, 14 Aug 2003 18:13:01 -0400
Received: from pine.neustar.com ([209.173.57.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 19nQL6-0006LH-00
	for ietf@ietf.org; Thu, 14 Aug 2003 18:13:00 -0400
Received: from chiimc01.npac.com ([10.32.90.4])
	by pine.neustar.com (8.11.0/8.11.0) with ESMTP id h7EMC9o29072;
	Thu, 14 Aug 2003 22:12:09 GMT
Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19)
	id <QZC9TV1X>; Thu, 14 Aug 2003 17:14:56 -0500
Message-ID: <A9DECB0B8A01A54DBECC03B25D29513C0A7B09@stntexch03.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Dave Crocker'" <dcrocker@brandenburg.com>
Cc: "'Marshall Rose'" <mrose+mtr.netnews@dbc.mtview.ca.us>, ietf@ietf.org
Subject: RE: WG Review: Centralized Conferencing (xcon)
Date: Thu, 14 Aug 2003 17:12:12 -0500
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


> 
> Jon,
> 
> PJ> So while one might be
> PJ> concerned by the fact that XCON is SIP-specific, I don't believe the
charter
> PJ> is especially disingenuous about that.
> 
> On the other hand, it declares a statement of intended design constraint
> (being sip oriented) but provides no indication of what that means or
> why it is being chosen. As such, it is not possible to evaluate that
> choice.
> 
> Given that a working group charter is a contract for work to be done,
> the contract needs to specify its constraints in a way that provides
> helpful detail.
> 

I think that's reasonable, yes. Hopefully the document citations you counsel
us (below) to include would help with this to some degree. I also think
importing some high-level text to the charter making a few of the more
important points (i.e. the need to identify media security solutions that
can interoperate with application-layer conference administration) would
also probably be appropriate.

> 
> PJ> As to why this proposed WG is more or less SIP-specific, the charter
arises
> PJ> from a set of framework, requirements and mechanism documents that
were
> PJ> proposed in SIPPING.
> 
> Working groups that are chartered with documented constraints are
> expected to cite those documents. If there is a body of prior work, on
> which this working group is being offered as a continuation, then a
> person reading the charter needs to be able to review that work.
> 

Yes, this is also reasonable. The XCON BoF charter cited five SIPPING
documents (largely of a framework/requirements bent), and seven
contributions that were believed to be applicable to XCON itself, but those
documents were not carried over to the proposed XCON WG charter. I think it
would make sense for at least some of these documents to be included in the
WG charter as well.

> Otherwise it is very difficult for a public review of the charter to be
> based on anything substantial.
> 
> If there is no documentation for the constraints, then there is no
> substantial basis for imposing them, other than perhaps citing some
> concerns or perspectives.
> 

Thanks, this was very helpful.

Jon Peterson
NeuStar, Inc.

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



From owner-ietf@ietf.org  Sat Aug 16 14:37: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 OAA15774
	for <ietf-web-archive@odin.ietf.org>; Sat, 16 Aug 2003 14:37:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19o5g0-0006Nb-Af
	for ietf-list@asgard.ietf.org; Sat, 16 Aug 2003 14:21:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19o5fD-0006LW-Lg
	for ietf@asgard.ietf.org; Sat, 16 Aug 2003 14:20: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 OAA15499
	for <ietf@ietf.org>; Sat, 16 Aug 2003 14:20:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19o5fC-0004HQ-00
	for ietf@ietf.org; Sat, 16 Aug 2003 14:20:30 -0400
Received: from ip166.usw12.rb1.bel.nwlink.com ([209.20.253.166] helo=ran.psg.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19o5fB-0004HN-00
	for ietf@ietf.org; Sat, 16 Aug 2003 14:20:29 -0400
Received: from localhost ([127.0.0.1] helo=ran.psg.com)
	by ran.psg.com with esmtp (Exim 4.20)
	id 19o5fA-000Gob-Qx; Sat, 16 Aug 2003 11:20:28 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sat, 16 Aug 2003 11:20:28 -0700
To: Joe Abley <jabley@isc.org>
Cc: Ole Jacobsen <ole@cisco.com>, The IETF <ietf@ietf.org>
Subject: Re: Korean cell phones
References: <Pine.HPX.4.44.0307180125120.10543-100000@wells.cisco.com>
	<F6709FD8-B92F-11D7-9A86-00039312C852@isc.org>
Message-Id: <E19o5fA-000Gob-Qx@ran.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>> - GSM is very limited, if at all existent (I found one network listed 
>> as
>>   "planned for Sept  2003")
> 
> I was in Seoul a few weeks ago and my tri-band GSM handset couldn't 
> find any network. There may be GSM coverage somewhere, but it certainly 
> doesn't make itself easy to find.
> 
> > - Some providers appear to offer roaming using your GSM SIM card in a
> >   Korean CDMA handset (unless I got that all wrong)
> 
> There are some details here:
> 
>    http://www.ktfroaming.com/
> 
> KT seem to have a large pile of agreements in place with GSM operators. 
> Microcell send me a flyer not long ago which said that you could rent a 
> CDMA handset at the airport suitable for use with one of their SIMs for 
> $1.50 per day (Canadian dollars).

you may want to check out

    <http://www.sktelecom.com/eng/services/ir_roaming.html>

randy




From owner-ietf@ietf.org  Mon Aug 18 00:53: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 AAA28192
	for <ietf-web-archive@odin.ietf.org>; Mon, 18 Aug 2003 00:53:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19obif-00085W-9v
	for ietf-list@asgard.ietf.org; Mon, 18 Aug 2003 00:34:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19obiU-00085G-Go
	for ietf@asgard.ietf.org; Mon, 18 Aug 2003 00:34: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 AAA27965
	for <ietf@ietf.org>; Mon, 18 Aug 2003 00:33:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19obiR-0004co-00
	for ietf@ietf.org; Mon, 18 Aug 2003 00:33:59 -0400
Received: from web80604.mail.yahoo.com ([66.218.79.93])
	by ietf-mx with smtp (Exim 4.12)
	id 19obiR-0004ch-00
	for ietf@ietf.org; Mon, 18 Aug 2003 00:33:59 -0400
Message-ID: <20030818043329.62490.qmail@web80604.mail.yahoo.com>
Received: from [213.147.67.206] by web80604.mail.yahoo.com via HTTP; Sun, 17 Aug 2003 21:33:29 PDT
Date: Sun, 17 Aug 2003 21:33:29 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Re: [Fwd: Emerging Network Usage and Engineering Issues]
To: grenville armitage <garmitage@swin.edu.au>, ietf@ietf.org
In-Reply-To: <3F3D7323.6595EB7B@swin.edu.au>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1180329718-1061181209=:60295"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-1180329718-1061181209=:60295
Content-Type: text/plain; charset=us-ascii

My answer to your question is that I want IETF, ISO and ITU to set nuclear warfare standards, i.e. if for example you see a web site with a standard ISO NW standard you know that it has dispersed critical manpower, inventories, has an alternative transport system, reliable NW capable suppliers and survival capability for dispersed staff.  Plus cutting edge IETF protocol implementation.  So that I can choose to use the sites the same way I choose ISO 9XXX.
 
Then Central Banks would be the first to practice those standards.
 
I am talking from my own experience of what goes on in a city after a mega-terror attack.  USA is not prepared for one, some of its cell phone masts have no standy batteries and generators, that would be part of ISO/IETF NW.  USA network of mini-nuke detectors may have no power back up.
 
Nyagudi



My question was to the entire list, and it still has not been
answered.

gja

> ATTACHMENT part 2 message/rfc822 
Date: Fri, 15 Aug 2003 04:00:24 -0700 (PDT)
From: NM Research 
Subject: Re: Emerging Network Usage and Engineering Issues
To: grenville armitage 

At times feel free to insult me privately not on the list.  The internet was not made for e-commerce, its mission was to communicate during nuclear warfare.
 
Meanwhile you can wait for the blast - some says some tactical torpedoes may be missing.
 
Nyagudi

grenville armitage <garmitage@swin.edu.au> wrote:

NM Research wrote:
[..partially coherent blather deleted..]

And this has *what* to do with the IETF?

gja



---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!

---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
--0-1180329718-1061181209=:60295
Content-Type: text/html; charset=us-ascii

<DIV>My answer to your question is that I want IETF, ISO and ITU to set nuclear warfare standards, i.e. if for example you see a web site with a standard ISO NW standard you know that it has dispersed critical manpower, inventories, has an alternative transport system, reliable NW capable suppliers and survival capability for dispersed staff.&nbsp; Plus cutting edge IETF protocol implementation.&nbsp; So that I can choose to use the sites the same way I choose ISO 9XXX.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Then Central Banks would be the first to practice those standards.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I am talking from my own experience of what goes on in a city after a mega-terror attack.&nbsp; USA is not prepared for one, some of its cell phone masts have no standy batteries and generators, that would be part of ISO/IETF NW.&nbsp; USA network of mini-nuke detectors may have no power back up.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi<BR></DIV><BR><B><I></I></B>
<BLOCKQUOTE style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px; WIDTH: 100%"><BR>My question was to the entire list, and it still has not been<BR>answered.<BR><BR>gja<BR><BR>&gt; ATTACHMENT part 2 message/rfc822 <BR>Date: Fri, 15 Aug 2003 04:00:24 -0700 (PDT)<BR>From: NM Research <NM_RESEARCH@YAHOO.COM><BR>Subject: Re: Emerging Network Usage and Engineering Issues<BR>To: grenville armitage <GARMITAGE@SWIN.EDU.AU><BR><BR>
<DIV>
<DIV>At times feel free to insult me privately not on the list.&nbsp; The internet was not made for e-commerce, its mission was to communicate during nuclear warfare.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Meanwhile you can wait for the blast - some says some tactical torpedoes may be missing.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi<BR><BR><B><I>grenville armitage &lt;garmitage@swin.edu.au&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px; WIDTH: 100%"><BR>NM Research <NM_RESEARCH@YAHOO.COM>wrote:<BR>[..partially coherent blather deleted..]<BR><BR>And this has *what* to do with the IETF?<BR><BR>gja<BR></BLOCKQUOTE></DIV>
<P>
<HR SIZE=1>
Do you Yahoo!?<BR><A href="http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*http://promo.yahoo.com/sbc/">SBC Yahoo! DSL</A> - Now only $29.95 per month!</BLOCKQUOTE><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*http://promo.yahoo.com/sbc/">SBC Yahoo! DSL</a> - Now only $29.95 per month!
--0-1180329718-1061181209=:60295--



From owner-ietf@ietf.org  Mon Aug 18 08:03: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 IAA16941
	for <ietf-web-archive@odin.ietf.org>; Mon, 18 Aug 2003 08:03:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19oiZS-00015T-FU
	for ietf-list@asgard.ietf.org; Mon, 18 Aug 2003 07:53:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19oiZJ-000156-6Y
	for ietf@asgard.ietf.org; Mon, 18 Aug 2003 07:53: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 HAA16758
	for <ietf@ietf.org>; Mon, 18 Aug 2003 07:52:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19oiZI-0006gd-00
	for ietf@ietf.org; Mon, 18 Aug 2003 07:53:00 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 19oiZH-0006gN-00
	for ietf@ietf.org; Mon, 18 Aug 2003 07:52:59 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (NAVGW 2.5.2.11) with SMTP id M2003081808025725100
 ; Mon, 18 Aug 2003 08:02:57 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 18 Aug 2003 07:49:15 -0400
Message-ID: <3F40BD39.4040006@centive.com>
Date: Mon, 18 Aug 2003 07:49:13 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: NM Research <nm_research@yahoo.com>, ietf@ietf.org
CC: grenville armitage <garmitage@swin.edu.au>
Subject: Re: [Fwd: Emerging Network Usage and Engineering Issues]
References: <20030818043329.62490.qmail@web80604.mail.yahoo.com>
In-Reply-To: <20030818043329.62490.qmail@web80604.mail.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Aug 2003 11:49:15.0000 (UTC) FILETIME=[BF85AF80:01C3657E]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

NM Research wrote:

> My answer to your question is that I want IETF, ISO and ITU to set 
> nuclear warfare standards,

It might be useful for someone to produce such standards, but they're 
really not in the IETF's domain of expertise.  Maybe some part of ISO 
would be better.

>     The internet was not made for e-commerce, its mission was to
>     communicate during nuclear warfare.
>
False.

-- 
/==============================================================\
|John Stracke      |jstracke@centive.com                       |
|Principal Engineer|http://www.centive.com                     |
|Centive           |My opinions are my own.                    |
|==============================================================|
|"If there's anything The Flintstones have taught us, it's that|
|pelicans can be used to mix cement." -- Homer Simpson         |
\==============================================================/





From owner-ietf@ietf.org  Tue Aug 19 03:38: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 DAA00531
	for <ietf-web-archive@odin.ietf.org>; Tue, 19 Aug 2003 03:38:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19p0is-000127-CU
	for ietf-list@asgard.ietf.org; Tue, 19 Aug 2003 03:16:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19p0hv-00011H-Ck
	for ietf@asgard.ietf.org; Tue, 19 Aug 2003 03:15: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 DAA00094
	for <ietf@ietf.org>; Tue, 19 Aug 2003 03:15:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p0hr-0005YH-00
	for ietf@ietf.org; Tue, 19 Aug 2003 03:15:03 -0400
Received: from web80602.mail.yahoo.com ([66.218.79.91])
	by ietf-mx with smtp (Exim 4.12)
	id 19p0hq-0005YE-00
	for ietf@ietf.org; Tue, 19 Aug 2003 03:15:02 -0400
Message-ID: <20030819071433.46993.qmail@web80602.mail.yahoo.com>
Received: from [213.147.67.206] by web80602.mail.yahoo.com via HTTP; Tue, 19 Aug 2003 00:14:33 PDT
Date: Tue, 19 Aug 2003 00:14:33 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Re: [Fwd: Emerging Network Usage and Engineering Issues]
To: John Stracke <jstracke@centive.com>, ietf@ietf.org
In-Reply-To: <3F40BD39.4040006@centive.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-947090500-1061277273=:45342"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-947090500-1061277273=:45342
Content-Type: text/plain; charset=us-ascii

Please qualify your false statement I would appreciate - what was A-net all about.  IETF is a powerful mover, just as it spoke against spamming.  Without IETF prodding nothing would ever happen.  Imagine that UK sub crews are told to tune into BBC to check if London has been nuked, before retaliating.  BBC and other internet media orgs should look for such a standard.
 
I do not really think that it is lack of stray nukes that keeps us safe.  It may be that those who have them lack triggering knowledge and transport to target is a problem.  Even if you have nuke detectors, they could use microwave EMP disruptors to get to town. Ok RAND Corp and others would also help.
 
Nyagudi

John Stracke <jstracke@centive.com> wrote:
NM Research wrote:

> My answer to your question is that I want IETF, ISO and ITU to set 
> nuclear warfare standards,

It might be useful for someone to produce such standards, but they're 
really not in the IETF's domain of expertise. Maybe some part of ISO 
would be better.

> The internet was not made for e-commerce, its mission was to
> communicate during nuclear warfare.
>
False.

-- 
/==============================================================\
|John Stracke |jstracke@centive.com |
|Principal Engineer|http://www.centive.com |
|Centive |My opinions are my own. |
|==============================================================|
|"If there's anything The Flintstones have taught us, it's that|
|pelicans can be used to mix cement." -- Homer Simpson |
\==============================================================/



---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
--0-947090500-1061277273=:45342
Content-Type: text/html; charset=us-ascii

<DIV>Please qualify your false statement I would appreciate - what was A-net all about.&nbsp; IETF is a powerful mover, just as it&nbsp;spoke against spamming.&nbsp; Without IETF prodding nothing would ever happen.&nbsp; Imagine that UK sub crews are told to tune into BBC to check if London has been nuked, before retaliating.&nbsp; BBC and other internet media orgs should look for such a standard.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I do not really think that it is lack of stray nukes that keeps us safe.&nbsp; It may be that those who have them lack triggering knowledge and transport to target is a problem.&nbsp; Even if you have nuke detectors, they could use microwave EMP disruptors to get to town. Ok RAND Corp and others would also help.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi<BR><BR><B><I>John Stracke &lt;jstracke@centive.com&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px; WIDTH: 100%">NM Research wrote:<BR><BR>&gt; My answer to your question is that I want IETF, ISO and ITU to set <BR>&gt; nuclear warfare standards,<BR><BR>It might be useful for someone to produce such standards, but they're <BR>really not in the IETF's domain of expertise. Maybe some part of ISO <BR>would be better.<BR><BR>&gt; The internet was not made for e-commerce, its mission was to<BR>&gt; communicate during nuclear warfare.<BR>&gt;<BR>False.<BR><BR>-- <BR>/==============================================================\<BR>|John Stracke |jstracke@centive.com |<BR>|Principal Engineer|http://www.centive.com |<BR>|Centive |My opinions are my own. |<BR>|==============================================================|<BR>|"If there's anything The Flintstones have taught us, it's that|<BR>|pelicans can be used to mix cement." -- Homer Simpson
 |<BR>\==============================================================/<BR><BR></BLOCKQUOTE><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*http://promo.yahoo.com/sbc/">SBC Yahoo! DSL</a> - Now only $29.95 per month!
--0-947090500-1061277273=:45342--



From owner-ietf@ietf.org  Tue Aug 19 07:36: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 HAA05335
	for <ietf-web-archive@odin.ietf.org>; Tue, 19 Aug 2003 07:36:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19p4dl-0005G4-US
	for ietf-list@asgard.ietf.org; Tue, 19 Aug 2003 07:27:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19p4dF-0005F6-L3
	for ietf@asgard.ietf.org; Tue, 19 Aug 2003 07: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 HAA05112
	for <ietf@ietf.org>; Tue, 19 Aug 2003 07:26:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p4dF-0006ii-00
	for ietf@ietf.org; Tue, 19 Aug 2003 07:26:33 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p4dE-0006iY-00
	for ietf@ietf.org; Tue, 19 Aug 2003 07:26:32 -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 h7JBQoxS076629;
	Tue, 19 Aug 2003 13:26:51 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Tue, 19 Aug 2003 13:26:18 +0200
Subject: Re: [Fwd: Emerging Network Usage and Engineering Issues]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: NM Research <nm_research@yahoo.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <20030819071433.46993.qmail@web80602.mail.yahoo.com>
Message-Id: <F3842B37-D237-11D7-977B-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On dinsdag, aug 19, 2003, at 09:14 Europe/Amsterdam, NM Research wrote:

> Please qualify your false statement I would appreciate - what was 
> A-net all about.

The confusion that the ARPAnet supposedly had a military function stems 
from the research done by Paul Baran at the RAND Corporation in the 
early to mid 1960s. He proposed high-availability packet switched 
network for military command and control. The ARPAnet however was about 
logging in on remote computers so that researchers could more easily 
work together.

As for making nuclear-proof standards: the IETF is all about running 
code. How do you propose we test these protocols?




From owner-ietf@ietf.org  Tue Aug 19 09:00: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 JAA08400
	for <ietf-web-archive@odin.ietf.org>; Tue, 19 Aug 2003 09:00:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19p60v-0007Du-9X
	for ietf-list@asgard.ietf.org; Tue, 19 Aug 2003 08:55:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19p60e-0007Ch-07
	for ietf@asgard.ietf.org; Tue, 19 Aug 2003 08:54: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 IAA08079
	for <ietf@ietf.org>; Tue, 19 Aug 2003 08:54:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p60d-0007UY-00
	for ietf@ietf.org; Tue, 19 Aug 2003 08:54:47 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p60c-0007UU-00
	for ietf@ietf.org; Tue, 19 Aug 2003 08:54:46 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.9/8.12.2) with ESMTP id h7JCse6H004381;
	Tue, 19 Aug 2003 08:54:40 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.9/8.12.2/Submit) id h7JCsdFs004380;
	Tue, 19 Aug 2003 08:54:39 -0400 (EDT)
Date: Tue, 19 Aug 2003 08:54:39 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200308191254.h7JCsdFs004380@newdev.harvard.edu>
To: iljitsch@muada.com, nm_research@yahoo.com
Subject: Re: [Fwd: Emerging Network Usage and Engineering Issues]
Cc: ietf@ietf.org
In-Reply-To: <F3842B37-D237-11D7-977B-00039388672E@muada.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

Iljitsch wrote:
> The confusion that the ARPAnet supposedly had a military function stems 
> from the research done by Paul Baran at the RAND Corporation in the 
> early to mid 1960s. He proposed high-availability packet switched 
> network for military command and control. 

in case anyone is interested, Baran's work is on-line at 
http://www.rand.org/publications/RM/baran.list.html

Scott



From owner-ietf@ietf.org  Tue Aug 19 11:27: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 LAA18074
	for <ietf-web-archive@odin.ietf.org>; Tue, 19 Aug 2003 11:27:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19p8FJ-0001Lh-PX
	for ietf-list@asgard.ietf.org; Tue, 19 Aug 2003 11:18:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19p8ET-0001K4-21
	for ietf@asgard.ietf.org; Tue, 19 Aug 2003 11:17: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 LAA17455
	for <ietf@ietf.org>; Tue, 19 Aug 2003 11:17:08 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p8ER-0001wU-00
	for ietf@ietf.org; Tue, 19 Aug 2003 11:17:12 -0400
Received: from h80ad2795.async.vt.edu ([128.173.39.149] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p8EQ-0001wR-00
	for ietf@ietf.org; Tue, 19 Aug 2003 11:17:10 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7JFGxVq028544;
	Tue, 19 Aug 2003 11:16:59 -0400
Message-Id: <200308191516.h7JFGxVq028544@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: John Stracke <jstracke@centive.com>, ietf@ietf.org
Subject: Re: [Fwd: Emerging Network Usage and Engineering Issues] 
In-Reply-To: Your message of "Tue, 19 Aug 2003 00:14:33 PDT."
             <20030819071433.46993.qmail@web80602.mail.yahoo.com> 
References: <20030819071433.46993.qmail@web80602.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_580016852P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 19 Aug 2003 11:16:58 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Tue, 19 Aug 2003 00:14:33 PDT, NM Research <nm_research@yahoo.com>  said:

> Please qualify your false statement I would appreciate - what was A-net all
> about.  IETF is a powerful mover, just as it spoke against spamming.  Without
> IETF prodding nothing would ever happen.

As far as I know, the IETF hasn't said anything more helpful than "Spam is
Bad", and most of the anti-spamming work done so far has been totally outside
the IETF (and, in fact, quite often totally contrary to the requirements in
RFC2821/2822). I don't think it's been the IETF speaking about spamming, so
much as the fact that the service providers are tired of having to handle
anywhere from 1M (our mail server) to 2B (MSN/Hotmail) spams inbound per day.

And if the IETF *has* done something substantiative, it certainly hasn't done
anything to the actual amount of spam.  When people have seen even a 10% drop
in spam in-transit per month for 3 months straight, *then* I'll accept that
something is actually working.

And John Strack was right on the nuclear warfare thing too:

http://www.isoc.org/internet/history/brief.shtml  says:

(footnote 5) "It was from the RAND study that the false rumor started claiming
that the ARPANET was somehow related to building a network resistant to nuclear
war. This was never true of the ARPANET, only the unrelated RAND study on
secure voice considered nuclear war. However, the later work on Internetting
did emphasize robustness and survivability, including the capability to
withstand losses of large portions of the underlying networks."


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

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

iD8DBQE/Qj9qcC3lWbTT17ARAhciAKDtP4PEO53QNHgc1Ch5Hh8JPHWiiwCgsvpn
neAbln3kvbCkYc047MQp59I=
=JmAB
-----END PGP SIGNATURE-----

--==_Exmh_580016852P--



From owner-ietf@ietf.org  Tue Aug 19 12:00: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 MAA19959
	for <ietf-web-archive@odin.ietf.org>; Tue, 19 Aug 2003 12:00:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19p8iL-0002gF-BF
	for ietf-list@asgard.ietf.org; Tue, 19 Aug 2003 11:48:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19p8hQ-0002dP-SA
	for ietf@asgard.ietf.org; Tue, 19 Aug 2003 11:47:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19273
	for <ietf@ietf.org>; Tue, 19 Aug 2003 11:47:03 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19p8hP-0002RW-00
	for ietf@ietf.org; Tue, 19 Aug 2003 11:47:07 -0400
Received: from h80ad2795.async.vt.edu ([128.173.39.149] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19p8hN-0002RO-00
	for ietf@ietf.org; Tue, 19 Aug 2003 11:47:05 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7JFl3Vq029372;
	Tue, 19 Aug 2003 11:47:03 -0400
Message-Id: <200308191547.h7JFl3Vq029372@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: ietf@ietf.org
Cc: postmaster@skystream.com
Subject: E-mail Caught by Spam Filter Re: [Fwd: Emerging Network Usage an d Engineering (fwd)
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_583529628P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 19 Aug 2003 11:47:03 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_583529628P
Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0"
Content-Id: <29361.1061308022.0@turing-police.cc.vt.edu>

------- =_aaaaaaaaaa0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <29361.1061308022.1@turing-police.cc.vt.edu>

Hmm.. Comment about the IETF's stance on spam, and look what happens. ;)

I don't think this is an IETF-sanctioned practice, and I'm fairly sure that it's the IETF
mail host they're actually complaining about.  Of course, it isn't like they could
be *HELPFUL* and actually *LIST* which IP address and which blacklist.

Also, gotta love the way they send it to the RFC2822 From:, not the RFC2821
MAIL FROM: like the standards require.  But I think I commented about people
breaking standards, so that's no surprise either....

Mostly mentioning it because if one of the IETF servers *is* in one of those
blacklists, things are going to get ugly...


------- =_aaaaaaaaaa0
Content-Type: message/rfc822
Content-ID: <29361.1061308022.2@turing-police.cc.vt.edu>
Content-Description: forwarded message

Return-Path: <NMXEXSPP3_SERVER1@SkyStream.com>
Received: from localhost (localhost [127.0.0.1]) 	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7JFbaVv029143 	for <valdis@localhost>; Tue, 19 Aug 2003 11:37:43 -0400
Received: from fan.cc.vt.edu [198.82.161.8] 	by localhost with POP3 (fetchmail-6.2.2) 	for valdis@localhost (single-drop); Tue, 19 Aug 2003 11:37:43 -0400 (EDT)
Received: from zidane.cc.vt.edu (evil-zidane.cc.vt.edu [10.1.1.13])  by lyta.cc.vt.edu (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002))  with ESMTP id <0HJV000Q5I0EJE@lyta.cc.vt.edu> for valdis@ims-ms-daemon  (ORCPT Valdis.Kletnieks@vt.edu); Tue, 19 Aug 2003 11:36:14 -0400 (EDT)
Received: from server1.skystream.com (server1.skystream.com [63.89.190.5]) 	by zidane.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) 	with ESMTP id BUG02297; Tue, 19 Aug 2003 11:36:11 -0400 (EDT)
Received: by SERVER1 with Internet Mail Service (5.5.2655.55) 	id <RF4W2F7N>; Tue, 19 Aug 2003 08:36:05 -0700
Content-return: allowed
Date: Tue, 19 Aug 2003 08:36:01 -0700
From: "Postmaster/Webmaster/Etc." <Master@SkyStream.com>
Subject: E-mail Caught by Spam Filter  Re: [Fwd: Emerging Network Usage an	d  Engineering Issues]
To: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>
Message-id: <B25E2E5A003CD311B61E00902778AF2A0B22C635@SERVER1>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-type: multipart/alternative;  boundary="----_=_NextPart_001_01C36667.97F9C8E0"

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_01C36667.97F9C8E0
Content-Type: text/plain

Your e-mail to the SkyStream recipient has been blocked!

This is due to your e-mail servers IP being listed on one or more of the
internet based Spam filter lists below.  Please notify your IT Dept or your
ISP and make sure they are aware of the issue.

Multihop.dsbl.org
Relays.ordb.org
Relays.osirsoft.com
Lists.dsbl.org

You may send and e-mail to postmaster@skystream.com from an alternate e-mail
account or one of the internet based e-mail servers i.e. Hotmail.com or
Yahoo.com and ask to have your account added to the approved list. You can
also call 408-616-3111 and ask to have your system placed on the approved
list.

Thank You,

SkyStream  IT

------_=_NextPart_001_01C36667.97F9C8E0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>E-mail Caught by Spam Filter  Re: [Fwd: Emerging Network Usage =
and Engineering Issues] </TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Your e-mail to the SkyStream recipient has been =
blocked!</FONT>
</P>

<P><FONT SIZE=3D2>This is due to your e-mail servers IP being listed on =
one or more of the internet based Spam filter lists below.&nbsp; Please =
notify your IT Dept or your ISP and make sure they are aware of the =
issue.</FONT></P>

<P><FONT SIZE=3D2>Multihop.dsbl.org</FONT>
<BR><FONT SIZE=3D2>Relays.ordb.org</FONT>
<BR><FONT SIZE=3D2>Relays.osirsoft.com</FONT>
<BR><FONT SIZE=3D2>Lists.dsbl.org</FONT>
</P>

<P><FONT SIZE=3D2>You may send and e-mail to postmaster@skystream.com =
from an alternate e-mail account or one of the internet based e-mail =
servers i.e. Hotmail.com or Yahoo.com and ask to have your account =
added to the approved list. You can also call 408-616-3111 and ask to =
have your system placed on the approved list.</FONT></P>

<P><FONT SIZE=3D2>Thank You,</FONT>
</P>

<P><FONT SIZE=3D2>SkyStream&nbsp; IT</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C36667.97F9C8E0--


------- =_aaaaaaaaaa0--

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

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

iD8DBQE/QkZ2cC3lWbTT17ARAmxSAKDHwEIIl029EW6rge0It0CmBQFZnwCgvPb2
uJVXh2y/7+wXu1X889TEbSc=
=HSTR
-----END PGP SIGNATURE-----

--==_Exmh_583529628P--



From owner-ietf@ietf.org  Tue Aug 19 14: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 OAA26989
	for <ietf-web-archive@odin.ietf.org>; Tue, 19 Aug 2003 14:08:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pAmA-0006o2-M9
	for ietf-list@asgard.ietf.org; Tue, 19 Aug 2003 14:00:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pAlr-0006mK-AX
	for ietf@asgard.ietf.org; Tue, 19 Aug 2003 13:59: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 NAA26455
	for <ietf@ietf.org>; Tue, 19 Aug 2003 13:59:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pAlq-0004bq-00
	for ietf@ietf.org; Tue, 19 Aug 2003 13:59:50 -0400
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19pAlp-0004bn-00
	for ietf@ietf.org; Tue, 19 Aug 2003 13:59:49 -0400
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.14)
	id 19pAlo-0000sz-Lv
	for ietf@ietf.org; Tue, 19 Aug 2003 17:59:48 +0000
Received: from rwelty by skipper.averillpark.net with local (Exim 4.14)
	id 19pAkm-0004y9-NO
	for ietf@ietf.org; Tue, 19 Aug 2003 13:58:44 -0400
Date: Tue, 19 Aug 2003 13:58:44 -0400 (EDT)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re: E-mail Caught by Spam Filter Re: [Fwd: Emerging Network Usage
To: ietf@ietf.org
Message-ID: <Mahogany-0.65.0-18895-20030819-135844.00@averillpark.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
Organization: Averilll Park Networking
X-Mailer: Mahogany 0.65.0 'Claire', compiled for Linux 2.4.20-19.9 i686
Reply-To: rwelty@averillpark.net
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/>.
Sender: owner-ietf@ietf.org
Precedence: bulk

Valdis.Kletnieks@vt.eud wrote about a spam filter having issues; the actual
text from the spam filter bounce is:

>This is due to your e-mail servers IP being listed on one or more of the
>internet based Spam filter lists below.  Please notify your IT Dept or
>your ISP and make sure they are aware of the issue.

>Multihop.dsbl.org
>Relays.ordb.org
>Relays.osirsoft.com
>Lists.dsbl.org


it is my understanding that the osirusoft zones are badly hosed, or at
least, were badly hosed some time over the past several days.

in other words, it's probably poor handling of a failure condition rather
than a true blacklist entry.

richard
-- 
Richard Welty                                         rwelty@averillpark.net
Averill Park Networking                                         518-573-7592
    Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security





From owner-ietf@ietf.org  Tue Aug 19 18:38: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 SAA13580
	for <ietf-web-archive@odin.ietf.org>; Tue, 19 Aug 2003 18:38:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pEzL-00043q-AP
	for ietf-list@asgard.ietf.org; Tue, 19 Aug 2003 18:30:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pEyX-00041M-Jw
	for ietf@asgard.ietf.org; Tue, 19 Aug 2003 18:29: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 SAA13312
	for <ietf@ietf.org>; Tue, 19 Aug 2003 18:29:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pEyV-00012G-00
	for ietf@ietf.org; Tue, 19 Aug 2003 18:29:12 -0400
Received: from adsl-64-168-10-250.dsl.scrm01.pacbell.net ([64.168.10.250] helo=miz-mishtal.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19pEyV-000122-00
	for ietf@ietf.org; Tue, 19 Aug 2003 18:29:11 -0400
Received: from shego (dhcpd254.dbc.mtview.ca.us [64.168.10.254])
	by miz-mishtal.dbc.mtview.ca.us (8.12.6/8.12.6) with SMTP id h7JMT58p012053;
	Tue, 19 Aug 2003 15:29:06 -0700 (PDT)
Message-ID: <003301c366a1$4b60aaa0$6801a8c0@shego>
From: "Marshall Rose" <mrose@dbc.mtview.ca.us>
To: "Peterson, Jon" <jon.peterson@neustar.biz>
Cc: <ietf@ietf.org>
References: <A9DECB0B8A01A54DBECC03B25D29513C0A7B03@stntexch03.va.neustar.com>
Subject: Re: WG Review: Centralized Conferencing (xcon)
Date: Tue, 19 Aug 2003 15:29:02 -0700
Organization: Dover Beach Consulting, Inc.
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

jon - sorry for the delay in replying.

fundamentally, i think it comes down to accuracy in labelling. if the sip
folks want to do conferencing, then they should have a working group to do
that. however, the charter for that working group should not imply that the
scope of the working group is anything beyond sip.

a reasonable person reading the charter would conclude that the scope of the
working group is somewhat more generic than sip.

if the goal for this working group is to be generic, then the charter is
likely unacceptable since it assumes "facts not entered into evidence",
i.e., it is sip-centric, and there is a fair body of deployed work that
manages to do conferencing very well without using that acronym. if that is
not the intention, then  i suggest that the working group be called
something like sipxcon to avoid any confusion.

as to whether the working group belongs in apps or tsv, a generic
conferencing working group clearly belongs in apps. however, a sip-specific
working group can probably comfortably reside in either.

/mtr




From owner-ietf@ietf.org  Tue Aug 19 19:10: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 TAA14832
	for <ietf-web-archive@odin.ietf.org>; Tue, 19 Aug 2003 19:10:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pFYx-0005k6-6F
	for ietf-list@asgard.ietf.org; Tue, 19 Aug 2003 19:06:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pFWR-0005fA-0f
	for ietf@asgard.ietf.org; Tue, 19 Aug 2003 19:04: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 TAA14652
	for <ietf@ietf.org>; Tue, 19 Aug 2003 19:04:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pFWP-0001JU-00
	for ietf@ietf.org; Tue, 19 Aug 2003 19:04:13 -0400
Received: from pine.neustar.com ([209.173.57.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pFWO-0001JR-00
	for ietf@ietf.org; Tue, 19 Aug 2003 19:04:12 -0400
Received: from chiimc01.npac.com ([10.32.90.4])
	by pine.neustar.com (8.11.0/8.11.0) with ESMTP id h7JN3Vo16853;
	Tue, 19 Aug 2003 23:03:31 GMT
Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19)
	id <QZC9T62M>; Tue, 19 Aug 2003 18:06:20 -0500
Message-ID: <A9DECB0B8A01A54DBECC03B25D29513C0A7B20@stntexch03.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Marshall Rose'" <mrose@dbc.mtview.ca.us>
Cc: ietf@ietf.org
Subject: RE: WG Review: Centralized Conferencing (xcon)
Date: Tue, 19 Aug 2003 18:03:45 -0500
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


[from the charter text]
> Initially this combination of protocols will be specified with respect
> to session setup with SIP. The solutions developed in XCON will not
> preclude operation with other signaling protocols; however it is
> anticipated that the use of other protocols would require modifications
> which are out of scope for this working group.

Regarding the name 'xcon' versus something like 'sipxcon', as the paragraph
above states, XCON does not want to preclude the possibility that its
mechanisms will work with other signaling protocols. It's possible that a
mechanism for conference control designed with SIP in mind could have some
applicability to other protocols (MGCP and Megaco come to mind - more likely
than not, anything SDP-based - but perhaps even non-IETF protocols like
H.323, and so on). In that sense I think the work really is somewhat more
generic than SIP - the group will not go out of its way to ensure its
applicability elsewhere, but the work isn't so tightly-coupled to SIP that
applicability in the rough neighborhood is impossible or even vastly
unlikely. 

As far as I can tell, the paragraph above strikes the right balance, and
doesn't make unreasonable or ambitious claims about applicability. Perhaps
that paragraph's wording could be improved, or it could be placed more
prominently in the charter, or something (suggestions welcome). But I can't
imagine the charter text could be construed to imply that protocols like,
for example, XMPP would be bound or even encouraged to support the results
of XCON.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Marshall Rose [mailto:mrose@dbc.mtview.ca.us]
> Sent: Tuesday, August 19, 2003 3:29 PM
> To: Peterson, Jon
> Cc: ietf@ietf.org
> Subject: Re: WG Review: Centralized Conferencing (xcon)
> 
> 
> jon - sorry for the delay in replying.
> 
> fundamentally, i think it comes down to accuracy in 
> labelling. if the sip
> folks want to do conferencing, then they should have a 
> working group to do
> that. however, the charter for that working group should not 
> imply that the
> scope of the working group is anything beyond sip.
> 
> a reasonable person reading the charter would conclude that 
> the scope of the
> working group is somewhat more generic than sip.
> 
> if the goal for this working group is to be generic, then the 
> charter is
> likely unacceptable since it assumes "facts not entered into 
> evidence",
> i.e., it is sip-centric, and there is a fair body of deployed 
> work that
> manages to do conferencing very well without using that 
> acronym. if that is
> not the intention, then  i suggest that the working group be called
> something like sipxcon to avoid any confusion.
> 
> as to whether the working group belongs in apps or tsv, a generic
> conferencing working group clearly belongs in apps. however, 
> a sip-specific
> working group can probably comfortably reside in either.
> 
> /mtr
> 



From owner-ietf@ietf.org  Wed Aug 20 01:27: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 BAA27516
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 01:27:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pLKW-0007V1-Be
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 01:16:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pLJb-0007Th-42
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 01:15: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 BAA27083
	for <ietf@ietf.org>; Wed, 20 Aug 2003 01:15:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pLJZ-0004LF-00
	for ietf@ietf.org; Wed, 20 Aug 2003 01:15:21 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pLJY-0004Kn-00
	for ietf@ietf.org; Wed, 20 Aug 2003 01:15:20 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 445F961BB8; Wed, 20 Aug 2003 07:14:49 +0200 (CEST)
Date: Tue, 19 Aug 2003 19:54:50 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Marshall Rose'" <mrose@dbc.mtview.ca.us>
Cc: ietf@ietf.org
Subject: RE: WG Review: Centralized Conferencing (xcon)
Message-ID: <773350489.1061322890@localhost>
In-Reply-To: <A9DECB0B8A01A54DBECC03B25D29513C0A7B20@stntexch03.va.neustar.com>
References:  <A9DECB0B8A01A54DBECC03B25D29513C0A7B20@stntexch03.va.neustar.co
 m>
X-Mailer: Mulberry/3.0.2 (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

listening in on this conversation, it seems to me that Marshall is talking 
about "conferencing" in a sense which includes a lot of different 
mechanisms, the premier one being instant messaging, while Jon (and the 
XCON charter) speaks about "conferencing" in a sense that starts out 
assuming that voice is included, and that video is the logical next step, 
while conferencing based on IM, if thought of at all, is regarded as a 
small side issue.

I don't know how to add markers to the charter to make it obvious how the 
word "conferencing" is intended here, however. And it may not even make the 
issue go away.

And, of course, I may have misunderstood the charter (or Marshall).

                      Harald




From owner-ietf@ietf.org  Wed Aug 20 02:34: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 CAA25694
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 02:34:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pMPv-0007nu-Nb
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 02:25:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pMPi-0007kB-QT
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 02:25: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 CAA20828
	for <ietf@ietf.org>; Wed, 20 Aug 2003 02:25:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pMPd-0004s9-00
	for ietf@ietf.org; Wed, 20 Aug 2003 02:25:41 -0400
Received: from dns1.vpop.net ([207.178.248.2] helo=boromir.vpop.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19pMPd-0004s6-00
	for ietf@ietf.org; Wed, 20 Aug 2003 02:25:41 -0400
Received: from [192.168.0.10] (ppp-67-118-247-225.dialup.pltn13.pacbell.net [67.118.247.225])
	by boromir.vpop.net (Postfix) with ESMTP
	id 12A4F3A688D; Tue, 19 Aug 2003 23:25:37 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <a05111b02bb68c4373ed7@[192.168.0.10]>
In-Reply-To: <773350489.1061322890@localhost>
References: 
 <A9DECB0B8A01A54DBECC03B25D29513C0A7B20@stntexch03.va.neustar.co m>
 <773350489.1061322890@localhost>
Date: Tue, 19 Aug 2003 23:25:38 -0700
To: Harald Tveit Alvestrand <harald@alvestrand.no>,
        "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Marshall Rose'" <mrose@dbc.mtview.ca.us>
From: Ari Ollikainen <Ari@OLTECO.com>
Subject: RE: WG Review: Centralized Conferencing (xcon)
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 7:54 PM -0700 8/19/03, Harald Tveit Alvestrand wrote:
>listening in on this conversation, it seems to me that Marshall is talking about "conferencing" in a sense which includes a lot of different mechanisms, the premier one being instant messaging, while Jon (and the XCON charter) speaks about "conferencing" in a sense that starts out assuming that voice is included, and that video is the logical next step, while conferencing based on IM, if thought of at all, is regarded as a small side issue.
>
>I don't know how to add markers to the charter to make it obvious how the word "conferencing" is intended here, however. And it may not even make the issue go away.

	
	In the context of audio and video conferencing why not add those
	words to the description...we've been here before (~10 years ago
	with the remconf BOF and its spinoffs).


 

 _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
 You can't depend on your judgement when your imagination is out of focus.	
						          -- Mark Twain.
 _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

       OLTECO                    Ari Ollikainen
       P.O. BOX 20088            Networking Architecture & Technology
       Stanford, CA              Ari@OLTECO.com
       94309-0088                415.517.3519 



From owner-ietf@ietf.org  Wed Aug 20 11:25: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 LAA13644
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 11:25:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pUb0-0003Mo-FN
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 11:09:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pUYT-0003J2-3y
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 11:07: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 LAA12760
	for <ietf@ietf.org>; Wed, 20 Aug 2003 11:07:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pUYS-0001gp-00
	for ietf@ietf.org; Wed, 20 Aug 2003 11:07:20 -0400
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pUYR-0001gd-00
	for ietf@ietf.org; Wed, 20 Aug 2003 11:07:19 -0400
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id h7KF6Wlt013514;
	Wed, 20 Aug 2003 11:06:32 -0400 (EDT)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <QX7JZ1Y7>; Wed, 20 Aug 2003 10:06:32 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E86330@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Cc: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>
Subject: RE: WG Review: Centralized Conferencing (xcon)
Date: Wed, 20 Aug 2003 10:06:31 -0500
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

Harald Tveit Alvestrand writes:

> Listening in on this conversation, it seems to me that
> Marshall is talking about "conferencing" in a sense which
> includes a lot of different mechanisms, the premier one
> being instant messaging, while Jon (and the XCON charter)
> speaks about "conferencing" in a sense that starts out
> assuming that voice is included, and that video is the
> logical next step, while conferencing based on IM, if
> thought of at all, is regarded as a small side issue.

As one of the chairs of the BOF, such was certainly
*not* my understanding. The solution is intended to
address media streams in general, not just voice
and video.

In particular, many people with whom I have spoken
regarding XCON expressed interest in its application
to instant messaging. Additionally, one of the
strongest motivations within the SIMPLE community
for adding session-mode messaging is the ability to
take advantage of any other capabilities that can be
applied to SIP sessions, such as multiparty
conferencing.

To reinforce that point: one of the primary reasons
(in my estimation) that SIMPLE has not proposed
solutions for chat rooms is the realization that such
functionality comes for free once a general
conferencing solution is defined. I would posit that
the expectation of SIMPLE is that the solution
created by XCON will be usable for this application.

> I don't know how to add markers to the charter to
> make it obvious how the word "conferencing" is
> intended here, however.

I believe any modifications to the charter that
de-emphasized text as a media type would be a
disservice to a significant number of potential
XCON participants.

/a



From owner-ietf@ietf.org  Wed Aug 20 12:36: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 MAA18373
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 12:36:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pVor-0004iq-Cy
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 12:28:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pVnx-0004fa-3u
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 12:27: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 MAA18077
	for <ietf@ietf.org>; Wed, 20 Aug 2003 12:27:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pVnw-0003Ae-00
	for ietf@ietf.org; Wed, 20 Aug 2003 12:27:24 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pVnv-00039u-00
	for ietf@ietf.org; Wed, 20 Aug 2003 12:27:23 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id F2C2D61BEE; Wed, 20 Aug 2003 18:26:51 +0200 (CEST)
Date: Wed, 20 Aug 2003 09:00:17 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Adam Roach <adam@dynamicsoft.com>, "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: WG Review: Centralized Conferencing (xcon)
Message-ID: <820477123.1061370017@localhost>
In-Reply-To: <9BF66EBF6BEFD942915B4D4D45C051F3E86330@dyn-tx-exch-001.dynamicsoft.com>
References:  <9BF66EBF6BEFD942915B4D4D45C051F3E86330@dyn-tx-exch-001.dynamics
 oft.com>
X-Mailer: Mulberry/3.0.2 (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 20. august 2003 10:06 -0500 Adam Roach <adam@dynamicsoft.com> wrote:

> I believe any modifications to the charter that
> de-emphasized text as a media type would be a
> disservice to a significant number of potential
> XCON participants.

Thanks - that means I misunderstood the charter, and that Marshall's 
concerns need addressing.

                    Harald






From owner-ietf@ietf.org  Wed Aug 20 12:59: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 MAA19585
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 12:59:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pWFu-0006TI-KU
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 12:56:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pWDt-0006Jc-Q5
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 12:54: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 MAA19322
	for <ietf@ietf.org>; Wed, 20 Aug 2003 12:54:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pWDs-0003X2-00
	for ietf@ietf.org; Wed, 20 Aug 2003 12:54:12 -0400
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pWDs-0003WW-00
	for ietf@ietf.org; Wed, 20 Aug 2003 12:54:12 -0400
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id h7KGrelt014149;
	Wed, 20 Aug 2003 12:53:40 -0400 (EDT)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <QX7JZ195>; Wed, 20 Aug 2003 11:53:40 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E86333@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: WG Review: Centralized Conferencing (xcon)
Date: Wed, 20 Aug 2003 11:53:38 -0500
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

Harald Tveit Alvestrand writes:

>--On 20. august 2003 10:06 -0500 Adam Roach <adam@dynamicsoft.com> wrote:
>
> > I believe any modifications to the charter that
> > de-emphasized text as a media type would be a
> > disservice to a significant number of potential
> > XCON participants.
> 
> Thanks - that means I misunderstood the charter, and that Marshall's 
> concerns need addressing.

I believe Jon is doing a commendable job of addressing
Marshall's concerns. I agree with, and have nothing to
add to, Jon's response on this topic (sent yesterday).

/a



From owner-ietf@ietf.org  Wed Aug 20 13:22: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 NAA20668
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 13:22:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pWXH-0007s6-Al
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 13:14:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pSJV-00082u-Ni
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 08:43:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06751
	for <ietf@ietf.org>; Wed, 20 Aug 2003 08:43:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pSJU-0000Lr-00
	for ietf@ietf.org; Wed, 20 Aug 2003 08:43:45 -0400
Received: from dgesmtp01.wcom.com ([199.249.16.16])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pSJU-0000Ll-00
	for ietf@ietf.org; Wed, 20 Aug 2003 08:43:44 -0400
Received: from pmismtp03.wcomnet.com ([166.38.62.38])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HJX008684GLK9@firewall.wcom.com> for ietf@ietf.org; Wed,
 20 Aug 2003 12:38:45 +0000 (GMT)
Received: from pmismtp03.wcomnet.com by pmismtp03.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HJX002014GL9K@pmismtp03.wcomnet.com>; Wed,
 20 Aug 2003 12:38:45 +0000 (GMT)
Received: from vint.mci.com ([166.50.135.91])
 by pmismtp03.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HJX00LQL4GFOO@pmismtp03.wcomnet.com>; Wed,
 20 Aug 2003 12:38:44 +0000 (GMT)
Date: Wed, 20 Aug 2003 08:38:34 -0400
From: "vinton g. cerf" <vinton.g.cerf@mci.com>
Subject: Re: WG Review: Centralized Conferencing (xcon)
In-reply-to: <003301c366a1$4b60aaa0$6801a8c0@shego>
X-Sender: vcerf@pop.mcilink.com
To: Marshall Rose <mrose@dbc.mtview.ca.us>,
        "Peterson, Jon" <jon.peterson@neustar.biz>
Cc: ietf@ietf.org
Message-id: <5.2.0.9.2.20030820083312.02f1a5e0@pop.mcilink.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Content-type: text/plain; charset=us-ascii
References: <A9DECB0B8A01A54DBECC03B25D29513C0A7B03@stntexch03.va.neustar.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

As a prospective supplier of SIP-based services, I am very interested in seeing SIP-based definitions for the support of a wide range of conferencing tools ranging from voice/video to IM and mixtures that might include a participant with only a phone and a fax machine. This is not to say that I would reject other protocol bases for such service but rather to say that we have a significant investment in SIP-based services and would like to see them expanded in standard ways so as to encourage interworking among parties offering such services. 

I leave it to the IESG and other interested parties to figure out how best to achieve that objective. Perhaps a SIP-oriented WG is the appropriate vehicle, recognizing that what ever procedures are invented, rooted in the SIP system, might well have counterparts in other signalling enviroments and could therefore be re-incarnated in them. Whether that would confer interworking between the SIP and non-SIP systems is beyond my ability to predict. 

Vint

 At 03:29 PM 8/19/2003 -0700, Marshall Rose wrote:
>jon - sorry for the delay in replying.
>
>fundamentally, i think it comes down to accuracy in labelling. if the sip
>folks want to do conferencing, then they should have a working group to do
>that. however, the charter for that working group should not imply that the
>scope of the working group is anything beyond sip.
>
>a reasonable person reading the charter would conclude that the scope of the
>working group is somewhat more generic than sip.
>
>if the goal for this working group is to be generic, then the charter is
>likely unacceptable since it assumes "facts not entered into evidence",
>i.e., it is sip-centric, and there is a fair body of deployed work that
>manages to do conferencing very well without using that acronym. if that is
>not the intention, then  i suggest that the working group be called
>something like sipxcon to avoid any confusion.
>
>as to whether the working group belongs in apps or tsv, a generic
>conferencing working group clearly belongs in apps. however, a sip-specific
>working group can probably comfortably reside in either.
>
>/mtr

Vint Cerf
SVP Architecture & Technology
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  Wed Aug 20 13:22: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 NAA20677
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 13:22:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pWXI-0007sI-1C
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 13:14:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pTBx-0000kE-RQ
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 09:40: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 JAA08616
	for <ietf@ietf.org>; Wed, 20 Aug 2003 09:39:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pTBw-0000w3-00
	for ietf@ietf.org; Wed, 20 Aug 2003 09:40:00 -0400
Received: from dgesmtp02.wcom.com ([199.249.16.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pTBv-0000vo-00
	for ietf@ietf.org; Wed, 20 Aug 2003 09:39:59 -0400
Received: from pmismtp03.wcomnet.com ([166.38.62.38])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HJX00DE470CN8@firewall.wcom.com> for ietf@ietf.org; Wed,
 20 Aug 2003 13:33:49 +0000 (GMT)
Received: from pmismtp03.wcomnet.com by pmismtp03.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HJX00D016ZEWS@pmismtp03.wcomnet.com>; Wed,
 20 Aug 2003 13:33:48 +0000 (GMT)
Received: from hsinnreich2 ([166.50.143.66])
 by pmismtp03.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HJX00BO3707G3@pmismtp03.wcomnet.com>; Wed,
 20 Aug 2003 13:33:45 +0000 (GMT)
Date: Wed, 20 Aug 2003 08:33:44 -0500
From: Henry Sinnreich <Henry.Sinnreich@mci.com>
Subject: RE: WG Review: Centralized Conferencing (xcon)
In-reply-to: <5.2.0.9.2.20030820083312.02f1a5e0@pop.mcilink.com>
To: "'vinton g. cerf'" <vinton.g.cerf@mci.com>,
        "'Marshall Rose'" <mrose@dbc.mtview.ca.us>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>
Cc: ietf@ietf.org, Alan Johnston <alan.johnston@mci.com>,
        Robert Sparks <rsparks@dynamicsoft.com>
Message-id: <0HJX00BO4708G3@pmismtp03.wcomnet.com>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Office Outlook, Build 11.0.5329
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Thread-index: AcNnF/6bTQCJdCIeSNepO54wVfw6pgABGQtw
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Given the IM background in this discussion, I fail to see why there should
be an IM-originated conferencing option to confuse everyone, when SIP
conferencing is supporting all types of media and presence and IM just as
well (plus events, user preferences, mobility etc.) in a consistent way.

It is high time the IETF should get its act together and converge on the one
single multiparty (conferencing!) multimedia session protocol: SIP. And
avoid such confusions as Marshall does in the attached.

Look at the huge penetration of SIP with wired and mobile service providers,
as well as on tens of millions of desktops: The IETF SIP work is already the
de facto standard. Let's just stay focused.

It is thus entirely appropriate XCON should be a SIP oriented WG for
centralized conferencing.

Thanks,

Henry Sinnreich
MCI

> -----Original Message-----
> From: vinton g. cerf [mailto:vinton.g.cerf@mci.com]
> Sent: Wednesday, August 20, 2003 7:39 AM
> To: Marshall Rose; Peterson, Jon
> Cc: ietf@ietf.org
> Subject: Re: WG Review: Centralized Conferencing (xcon)
> 
> As a prospective supplier of SIP-based services, I am very interested in
> seeing SIP-based definitions for the support of a wide range of
> conferencing tools ranging from voice/video to IM and mixtures that might
> include a participant with only a phone and a fax machine. This is not to
> say that I would reject other protocol bases for such service but rather
> to say that we have a significant investment in SIP-based services and
> would like to see them expanded in standard ways so as to encourage
> interworking among parties offering such services.
> 
> I leave it to the IESG and other interested parties to figure out how best
> to achieve that objective. Perhaps a SIP-oriented WG is the appropriate
> vehicle, recognizing that what ever procedures are invented, rooted in the
> SIP system, might well have counterparts in other signalling enviroments
> and could therefore be re-incarnated in them. Whether that would confer
> interworking between the SIP and non-SIP systems is beyond my ability to
> predict.
> 
> Vint
> 
>  At 03:29 PM 8/19/2003 -0700, Marshall Rose wrote:
> >jon - sorry for the delay in replying.
> >
> >fundamentally, i think it comes down to accuracy in labelling. if the sip
> >folks want to do conferencing, then they should have a working group to
> do
> >that. however, the charter for that working group should not imply that
> the
> >scope of the working group is anything beyond sip.
> >
> >a reasonable person reading the charter would conclude that the scope of
> the
> >working group is somewhat more generic than sip.
> >
> >if the goal for this working group is to be generic, then the charter is
> >likely unacceptable since it assumes "facts not entered into evidence",
> >i.e., it is sip-centric, and there is a fair body of deployed work that
> >manages to do conferencing very well without using that acronym. if that
> is
> >not the intention, then  i suggest that the working group be called
> >something like sipxcon to avoid any confusion.
> >
> >as to whether the working group belongs in apps or tsv, a generic
> >conferencing working group clearly belongs in apps. however, a sip-
> specific
> >working group can probably comfortably reside in either.
> >
> >/mtr
> 
> Vint Cerf
> SVP Architecture & Technology
> 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  Wed Aug 20 13:55: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 NAA25542
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 13:55:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pX4B-0001l0-M1
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 13:48:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pWxZ-0001Xi-GN
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 13:41: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 NAA22952
	for <ietf@ietf.org>; Wed, 20 Aug 2003 13:41:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pWxY-0004LD-00
	for ietf@ietf.org; Wed, 20 Aug 2003 13:41:24 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pWxX-0004L4-00
	for ietf@ietf.org; Wed, 20 Aug 2003 13:41: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 h7KHjFa27419;
	Wed, 20 Aug 2003 10:45:15 -0700
Date: Wed, 20 Aug 2003 10:40:36 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/11) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <18627649017.20030820104036@brandenburg.com>
To: "Peterson, Jon" <jon.peterson@neustar.biz>
CC: ietf@ietf.org
Subject: Re: WG Review: Centralized Conferencing (xcon)
In-Reply-To: <A9DECB0B8A01A54DBECC03B25D29513C0A7B20@stntexch03.va.neustar.com>
References: <A9DECB0B8A01A54DBECC03B25D29513C0A7B20@stntexch03.va.neustar.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

Jon,

Perhaps it will help to consider the proposed text from the vantage
point of someone who is not already familiar with SIP and SIP history.

It might also help to consider how concrete (or not) the proposed
language is:


PJ> [from the charter text]
>> Initially this combination of protocols will be specified with respect
>> to session setup with SIP.

This says that SIP provides a basis, but there is no indication of what
this means. There is no operationally or technically objective meaning to
"specified with respect to". It could mean absolutely anything. So the
text is conceptual, rather than concrete.

That is, it states a philosophical focus on SIP, but nothing more.  In
terms of "contract" language, it has no content that can be enforced.
The one possible use of this sentence is to provide a basis for
excluding non-SIP work.


>> The solutions developed in XCON will not
>> preclude operation with other signaling protocols;

Again, this is a statement of philosophy that has no operational or
technical meat to it.  In the abstract, yes, one can do things to
preclude operation with other signalling protocols, but there is no
well-established set of design actions that folks will know about, for
creating such "preclusion".

Further, it is pretty darn rare to have a working group do anything to
"preclude" actions outside of the working group scope.

In fact there is a track record of design work that says the actual
outcome of the working group will be the opposite of what the charter
text declares: Absent careful attention to other uses, a design tends to
be workable only for the envisioned scenario.


>> however it is
>> anticipated that the use of other protocols would require modifications
>> which are out of scope for this working group.

In other words, this is work that is only for SIP.


PJ> Regarding the name 'xcon' versus something like 'sipxcon', as the paragraph
PJ> above states, XCON does not want to preclude the possibility that its
PJ> mechanisms will work with other signaling protocols.

Actually, yes it does. The SIP environment is the only scope of this work.

Unless the charter states what will be done to *ensure* that other
signalling environments can be supported, the odds are quite high that
none will be possible.


PJ> It's possible that a mechanism for conference control designed with
PJ> SIP in mind could have some applicability to other protocols

Unfortunately, this sort of statement has no effect. Anything is
"possible". So the text is just commentary about the unknown future.

On the average, it has no place in a charter, because it says nothing
about what what the working group will or will not do. Yet that is the
purpose of a charter.

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




From owner-ietf@ietf.org  Wed Aug 20 16:43: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 QAA09155
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 16:43:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pZg6-0001qV-79
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 16:35:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pZe4-0001a6-Nx
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 16:33: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 QAA08708
	for <ietf@ietf.org>; Wed, 20 Aug 2003 16:33:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pZe1-0007Rs-00
	for ietf@ietf.org; Wed, 20 Aug 2003 16:33:25 -0400
Received: from lakehearnglobal.coxinc.com ([206.157.224.254] helo=hatl0ms21.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 19pZe0-0007RI-00
	for ietf@ietf.org; Wed, 20 Aug 2003 16:33:24 -0400
Received: from mail pickup service by hatl0ms21.CORP.COX.COM with Microsoft SMTPSVC;
	 Wed, 20 Aug 2003 16:24:49 -0400
Received: from bastion2.cox.com ([10.225.2.51]) by hatl0ms21.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 20 Aug 2003 13:58:04 -0400
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion2.cox.com (8.11.7+Sun/8.11.6) with SMTP id h7KHw3U22970;
	Wed, 20 Aug 2003 13:58:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pX4B-0001l0-M1
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 13:48:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pWxZ-0001Xi-GN
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 13:41: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 NAA22952
	for <ietf@ietf.org>; Wed, 20 Aug 2003 13:41:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pWxY-0004LD-00
	for ietf@ietf.org; Wed, 20 Aug 2003 13:41:24 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pWxX-0004L4-00
	for ietf@ietf.org; Wed, 20 Aug 2003 13:41: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 h7KHjFa27419;
	Wed, 20 Aug 2003 10:45:15 -0700
Date: Wed, 20 Aug 2003 10:40:36 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/11) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <18627649017.20030820104036@brandenburg.com>
To: "Peterson, Jon" <jon.peterson@neustar.biz>
CC: ietf@ietf.org
Subject: Re: WG Review: Centralized Conferencing (xcon)
In-Reply-To: <A9DECB0B8A01A54DBECC03B25D29513C0A7B20@stntexch03.va.neustar.com>
References: <A9DECB0B8A01A54DBECC03B25D29513C0A7B20@stntexch03.va.neustar.com>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Aug 2003 17:58:05.0281 (UTC) FILETIME=[9B061510:01C36744]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jon,

Perhaps it will help to consider the proposed text from the vantage
point of someone who is not already familiar with SIP and SIP history.

It might also help to consider how concrete (or not) the proposed
language is:


PJ> [from the charter text]
>> Initially this combination of protocols will be specified with respect
>> to session setup with SIP.

This says that SIP provides a basis, but there is no indication of what
this means. There is no operationally or technically objective meaning to
"specified with respect to". It could mean absolutely anything. So the
text is conceptual, rather than concrete.

That is, it states a philosophical focus on SIP, but nothing more.  In
terms of "contract" language, it has no content that can be enforced.
The one possible use of this sentence is to provide a basis for
excluding non-SIP work.


>> The solutions developed in XCON will not
>> preclude operation with other signaling protocols;

Again, this is a statement of philosophy that has no operational or
technical meat to it.  In the abstract, yes, one can do things to
preclude operation with other signalling protocols, but there is no
well-established set of design actions that folks will know about, for
creating such "preclusion".

Further, it is pretty darn rare to have a working group do anything to
"preclude" actions outside of the working group scope.

In fact there is a track record of design work that says the actual
outcome of the working group will be the opposite of what the charter
text declares: Absent careful attention to other uses, a design tends to
be workable only for the envisioned scenario.


>> however it is
>> anticipated that the use of other protocols would require modifications
>> which are out of scope for this working group.

In other words, this is work that is only for SIP.


PJ> Regarding the name 'xcon' versus something like 'sipxcon', as the paragraph
PJ> above states, XCON does not want to preclude the possibility that its
PJ> mechanisms will work with other signaling protocols.

Actually, yes it does. The SIP environment is the only scope of this work.

Unless the charter states what will be done to *ensure* that other
signalling environments can be supported, the odds are quite high that
none will be possible.


PJ> It's possible that a mechanism for conference control designed with
PJ> SIP in mind could have some applicability to other protocols

Unfortunately, this sort of statement has no effect. Anything is
"possible". So the text is just commentary about the unknown future.

On the average, it has no place in a charter, because it says nothing
about what what the working group will or will not do. Yet that is the
purpose of a charter.

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





From owner-ietf@ietf.org  Wed Aug 20 19:52: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 TAA19871
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 19:52:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pcdM-0008Um-VG
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 19:44:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pcdF-0008Rp-Qi
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 19:44: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 TAA19539
	for <ietf@ietf.org>; Wed, 20 Aug 2003 19:44:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pcdE-0001ui-00
	for ietf@ietf.org; Wed, 20 Aug 2003 19:44:48 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pcdD-0001uf-00
	for ietf@ietf.org; Wed, 20 Aug 2003 19:44:47 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id EDFE1140DD; Wed, 20 Aug 2003 19:44:47 -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 00986-05; Wed, 20 Aug 2003 19:44: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 6B00B1407F; Wed, 20 Aug 2003 19:44:46 -0400 (EDT)
Date: Wed, 20 Aug 2003 19:43:08 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Henry Sinnreich <Henry.Sinnreich@mci.com>
Cc: moore@cs.utk.edu, vinton.g.cerf@mci.com, mrose@dbc.mtview.ca.us,
        jon.peterson@neustar.biz, ietf@ietf.org, alan.johnston@mci.com,
        rsparks@dynamicsoft.com
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030820194308.0ac058c1.moore@cs.utk.edu>
In-Reply-To: <0HJX00BO4708G3@pmismtp03.wcomnet.com>
References: <5.2.0.9.2.20030820083312.02f1a5e0@pop.mcilink.com>
	<0HJX00BO4708G3@pmismtp03.wcomnet.com>
X-Mailer: Sylpheed version 0.9.3 (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 high time the IETF should get its act together and converge on the one
> single multiparty (conferencing!) multimedia session protocol: SIP. 

Why in the world should IETF bias a conferencing solution toward the telephony
providers?  I mean, if SIP turned out to be a good solution for everyone, fine.
But the group shouldn't assume a priori that SIP is the right direction.




From owner-ietf@ietf.org  Wed Aug 20 20:37: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 UAA21900
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 20:37:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pdOm-0002RL-Rs
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 20:33:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pdNV-0002Mx-Iy
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 20:32:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21741
	for <ietf@ietf.org>; Wed, 20 Aug 2003 20:32:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pdNT-0002Ub-00
	for ietf@ietf.org; Wed, 20 Aug 2003 20:32:35 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pdNT-0002UM-00
	for ietf@ietf.org; Wed, 20 Aug 2003 20:32:35 -0400
Received: from rshockeybox.shockey.us (h-68-165-240-37.MCLNVA23.covad.net [68.165.240.37])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h7L0aKa21576;
	Wed, 20 Aug 2003 17:36:20 -0700
Message-Id: <5.2.0.9.2.20030820202023.02d7f3e0@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 20 Aug 2003 20:31:10 -0400
To: Keith Moore <moore@cs.utk.edu>, Henry Sinnreich <Henry.Sinnreich@mci.com>
From: Richard Shockey <richard@shockey.us>
Subject: Re: WG Review: Centralized Conferencing (xcon)
Cc: moore@cs.utk.edu, vinton.g.cerf@mci.com, mrose@dbc.mtview.ca.us,
        jon.peterson@neustar.biz, ietf@ietf.org, alan.johnston@mci.com,
        rsparks@dynamicsoft.com
In-Reply-To: <20030820194308.0ac058c1.moore@cs.utk.edu>
References: <0HJX00BO4708G3@pmismtp03.wcomnet.com>
 <5.2.0.9.2.20030820083312.02f1a5e0@pop.mcilink.com>
 <0HJX00BO4708G3@pmismtp03.wcomnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 07:43 PM 8/20/2003 -0400, Keith Moore wrote:

> > It is high time the IETF should get its act together and converge on 
> the one
> > single multiparty (conferencing!) multimedia session protocol: SIP.
>
>Why in the world should IETF bias a conferencing solution toward the telephony
>providers?  I mean, if SIP turned out to be a good solution for everyone, 
>fine.
>But the group shouldn't assume a priori that SIP is the right direction.

Keith with all due respect ..first I would not charactize SIP as having a 
bias towards telephony providers, far from it. Its now supported by a truly 
staggering list of software developers and service providers who may or may 
not have associations with the incumbent global TDM regime including 
Microsoft, Lotus/IBM, and open source providers such as iptel.org 
increasing support from Apple and I suspect AOL as well.

I think the XCON folks were trying to be inclusive in their charter 
development but frankly I don't think its necessary. The IETF now has three 
SIP related WG's operating well and producing good work and the scope of 
the XCON proposal IMHO should be directed at SIP specifically. Its a 
complex issue, there is a real problem statement and a focused WG could 
tackle the problem head on and deliver results. This was the direction we 
took with SIPPING for the specific IM problem and its what we need to do 
with SIP Conferencing.

Most sincerely,

sip:rshockey@iptel.org



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




From owner-ietf@ietf.org  Wed Aug 20 21:17: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 VAA23683
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 21:17:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pdzY-0004X6-Aj
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 21:11:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pdx2-0004O6-LT
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 21:09: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 VAA23365
	for <ietf@ietf.org>; Wed, 20 Aug 2003 21:09:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pdx0-0002u7-00
	for ietf@ietf.org; Wed, 20 Aug 2003 21:09:19 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pdx0-0002u4-00
	for ietf@ietf.org; Wed, 20 Aug 2003 21:09:18 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 826331409E; Wed, 20 Aug 2003 21:09:18 -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 11940-11; Wed, 20 Aug 2003 21:09:17 -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 BC13013FF5; Wed, 20 Aug 2003 21:09:16 -0400 (EDT)
Date: Wed, 20 Aug 2003 21:07:38 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "vinton g. cerf" <vinton.g.cerf@mci.com>
Cc: moore@cs.utk.edu, henry.sinnreich@mci.com, mrose@dbc.mtview.ca.us,
        jon.peterson@neustar.biz, ietf@ietf.org, alan.johnston@mci.com,
        rsparks@dynamicsoft.com
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030820210738.2a2be202.moore@cs.utk.edu>
In-Reply-To: <5.2.0.9.2.20030820201708.03006130@pop.mcilink.com>
References: <0HJX00BO4708G3@pmismtp03.wcomnet.com>
	<5.2.0.9.2.20030820083312.02f1a5e0@pop.mcilink.com>
	<0HJX00BO4708G3@pmismtp03.wcomnet.com>
	<5.2.0.9.2.20030820201708.03006130@pop.mcilink.com>
X-Mailer: Sylpheed version 0.9.3 (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

> SIP may have been initially motivated by telephony style applications but it
> is a very general and extensible negotiation protocol - it was that aspect
> that grabbed my attention when I first heard about Schulzrinne's work on it
> several years ago. I think the point really is that SIP is extensible and
> may be a very reasonable platform on which to build a wide range of peer to
> peer and distributed application control.

SIP certainly is extensible, but I strongly suspect that we wouldn't be giving
it serious consideration for this use if there weren't already a substantial
investment in it from the telephony world.  What makes sense for telephone
providers (because of that investment) doesn't necessarily make sense for the
Internet.  SIP should of course be considered, but it shouldn't be assumed as
part of the solution path before the WG has even had a chance to consider
other, possibly less complex, alternatives.

Keith



From owner-ietf@ietf.org  Wed Aug 20 21:17: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 VAA23689
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 21:17:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pdyl-0004U7-B3
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 21:11:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pdvQ-00049V-6Q
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 21:07: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 VAA23293
	for <ietf@ietf.org>; Wed, 20 Aug 2003 21:07:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pdvJ-0002sp-00
	for ietf@ietf.org; Wed, 20 Aug 2003 21:07:33 -0400
Received: from adsl-64-168-10-254.dsl.scrm01.pacbell.net ([64.168.10.254] helo=drakken.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19pdvI-0002sh-00
	for ietf@ietf.org; Wed, 20 Aug 2003 21:07:32 -0400
Received: from drakken.dbc.mtview.ca.us (localhost [127.0.0.1])
	by drakken.dbc.mtview.ca.us (8.12.9/8.12.9) with SMTP id h7L178Lq015063;
	Wed, 20 Aug 2003 18:07:08 -0700 (PDT)
Date: Wed, 20 Aug 2003 18:07:08 -0700
From: Marshall Rose <mrose@dbc.mtview.ca.us>
To: Richard Shockey <richard@shockey.us>
Cc: Keith Moore <moore@cs.utk.edu>, Henry Sinnreich <Henry.Sinnreich@mci.com>,
        vinton.g.cerf@mci.com, jon.peterson@neustar.biz, ietf@ietf.org,
        alan.johnston@mci.com, rsparks@dynamicsoft.com
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030820180708.2a1b18f6.mrose@dbc.mtview.ca.us>
In-Reply-To: <5.2.0.9.2.20030820202023.02d7f3e0@shockey.us>
References: <0HJX00BO4708G3@pmismtp03.wcomnet.com>
	<5.2.0.9.2.20030820083312.02f1a5e0@pop.mcilink.com>
	<0HJX00BO4708G3@pmismtp03.wcomnet.com>
	<5.2.0.9.2.20030820202023.02d7f3e0@shockey.us>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I think the XCON folks were trying to be inclusive in their charter 
> development but frankly I don't think its necessary. The IETF now has three 
> SIP related WG's operating well and producing good work and the scope of 
> the XCON proposal IMHO should be directed at SIP specifically. Its a 
> complex issue, there is a real problem statement and a focused WG could 
> tackle the problem head on and deliver results. This was the direction we 
> took with SIPPING for the specific IM problem and its what we need to do 
> with SIP Conferencing.

richard - unfortunately, this isn't what the proposed charter says or
intends. 
    
i'll repeat what i've said twice before, but i'll use different words:
    
    if the sip folks want to have a working group to work on
    sip-specific conferencing, fine. we can judge the charter on its
    merits in the context of sip.
    
    the xmpp folks have a workable, deployed solution in the
    conferencing space. if they decide to take this work to the ietf,
    then that should also be accorded the same courtesy in being judged
    on its merits in the context of xmpp.
    
    the proposed charter (and jon's clarifications) have a considerably
    larger scope than doing sip-specific conferencing. further, it is
    disingenuous to say that other perspectives will be considered,
    because, to paraphrase sinnreich: "there is but one god, and it's
    name is sip".
    
so, as much as i enjoy these little skirmishes, i repeat my call for
peace:
    
    tailor the proposed charter so that it limits itself to sip-specific
    conference, and no one outside of the sip community will much care...
    
/mtr



From owner-ietf@ietf.org  Wed Aug 20 21:34: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 VAA24408
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 21:34:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19peHw-0006Dl-Pj
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 21:30:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19peHJ-0006B3-Au
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 21:30: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 VAA24283
	for <ietf@ietf.org>; Wed, 20 Aug 2003 21:30:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19peHH-00039C-00
	for ietf@ietf.org; Wed, 20 Aug 2003 21:30:15 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19peHG-000392-00
	for ietf@ietf.org; Wed, 20 Aug 2003 21:30:14 -0400
Received: from rshockeybox.shockey.us (h-68-165-240-37.MCLNVA23.covad.net [68.165.240.37])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h7L1Y4a24991;
	Wed, 20 Aug 2003 18:34:04 -0700
Message-Id: <5.2.0.9.2.20030820211455.02a204b0@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 20 Aug 2003 21:29:20 -0400
To: Marshall Rose <mrose@dbc.mtview.ca.us>
From: Richard Shockey <richard@shockey.us>
Subject: Re: WG Review: Centralized Conferencing (xcon)
Cc: Keith Moore <moore@cs.utk.edu>, Henry Sinnreich <Henry.Sinnreich@mci.com>,
        vinton.g.cerf@mci.com, jon.peterson@neustar.biz, ietf@ietf.org,
        alan.johnston@mci.com, rsparks@dynamicsoft.com
In-Reply-To: <20030820180708.2a1b18f6.mrose@dbc.mtview.ca.us>
References: <5.2.0.9.2.20030820202023.02d7f3e0@shockey.us>
 <0HJX00BO4708G3@pmismtp03.wcomnet.com>
 <5.2.0.9.2.20030820083312.02f1a5e0@pop.mcilink.com>
 <0HJX00BO4708G3@pmismtp03.wcomnet.com>
 <5.2.0.9.2.20030820202023.02d7f3e0@shockey.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 06:07 PM 8/20/2003 -0700, Marshall Rose wrote:

> > I think the XCON folks were trying to be inclusive in their charter
> > development but frankly I don't think its necessary. The IETF now has 
> three
> > SIP related WG's operating well and producing good work and the scope of
> > the XCON proposal IMHO should be directed at SIP specifically. Its a
> > complex issue, there is a real problem statement and a focused WG could
> > tackle the problem head on and deliver results. This was the direction we
> > took with SIPPING for the specific IM problem and its what we need to do
> > with SIP Conferencing.
>
>richard - unfortunately, this isn't what the proposed charter says or
>intends.

I know .. we are in total agreement the charter needs to be rewritten and 
more specific. Though again though I have no direct knowledge of the 
thinking of the charter authors I do belive they felt the obligation to be 
"inclusive" of other protocols. OK maybe they were trying to be politically 
correct..I don't know.

>
>i'll repeat what i've said twice before, but i'll use different words:
>
>     if the sip folks want to have a working group to work on
>     sip-specific conferencing, fine. we can judge the charter on its
>     merits in the context of sip.

ack and I agree that is the best approach.

>
>     the xmpp folks have a workable, deployed solution in the
>     conferencing space. if they decide to take this work to the ietf,
>     then that should also be accorded the same courtesy in being judged
>     on its merits in the context of xmpp.

IMHO yes however I would say .. if the XMPP community can contribute a 
architectural model that might be useful to SIP than I hope ..hope they 
would be willing to share such valuable insights.


>
>so, as much as i enjoy these little skirmishes

I know you do :-) and after all its the dog days of August and we all need 
a little entertainment from time to time.  I've noticed we have'nt had a ID 
and ASCII debate in a while..

>, i repeat my call for
>peace:
>
>     tailor the proposed charter so that it limits itself to sip-specific
>     conference, and no one outside of the sip community will much care...

That very reasonable.

My very best wishes ..

>
>/mtr


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




From owner-ietf@ietf.org  Wed Aug 20 23:33: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 XAA28864
	for <ietf-web-archive@odin.ietf.org>; Wed, 20 Aug 2003 23:33:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pg1P-00036A-Sr
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 23:21:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pg1J-00032L-Pb
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 23:21: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 XAA28493
	for <ietf@ietf.org>; Wed, 20 Aug 2003 23:21:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pg1H-0004HV-00
	for ietf@ietf.org; Wed, 20 Aug 2003 23:21:51 -0400
Received: from [206.157.230.254] (helo=hatl0ms20.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 19pg1G-0004H5-00
	for ietf@ietf.org; Wed, 20 Aug 2003 23:21:51 -0400
Received: from mail pickup service by hatl0ms20.CORP.COX.COM with Microsoft SMTPSVC;
	 Wed, 20 Aug 2003 23:21:14 -0400
Received: from bastion.cox.com ([10.230.2.65]) by hatl0ms20.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 20 Aug 2003 11:32:48 -0400
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion.cox.com (8.11.6+Sun/8.11.6) with SMTP id h7KFWdO27820;
	Wed, 20 Aug 2003 11:32:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pUb0-0003Mo-FN
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 11:09:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pUYT-0003J2-3y
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 11:07: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 LAA12760
	for <ietf@ietf.org>; Wed, 20 Aug 2003 11:07:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pUYS-0001gp-00
	for ietf@ietf.org; Wed, 20 Aug 2003 11:07:20 -0400
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pUYR-0001gd-00
	for ietf@ietf.org; Wed, 20 Aug 2003 11:07:19 -0400
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id h7KF6Wlt013514;
	Wed, 20 Aug 2003 11:06:32 -0400 (EDT)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <QX7JZ1Y7>; Wed, 20 Aug 2003 10:06:32 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E86330@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Cc: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>
Subject: RE: WG Review: Centralized Conferencing (xcon)
Date: Wed, 20 Aug 2003 10:06:31 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 20 Aug 2003 15:32:56.0936 (UTC) FILETIME=[54721680:01C36730]
Sender: owner-ietf@ietf.org
Precedence: bulk

Harald Tveit Alvestrand writes:

> Listening in on this conversation, it seems to me that
> Marshall is talking about "conferencing" in a sense which
> includes a lot of different mechanisms, the premier one
> being instant messaging, while Jon (and the XCON charter)
> speaks about "conferencing" in a sense that starts out
> assuming that voice is included, and that video is the
> logical next step, while conferencing based on IM, if
> thought of at all, is regarded as a small side issue.

As one of the chairs of the BOF, such was certainly
*not* my understanding. The solution is intended to
address media streams in general, not just voice
and video.

In particular, many people with whom I have spoken
regarding XCON expressed interest in its application
to instant messaging. Additionally, one of the
strongest motivations within the SIMPLE community
for adding session-mode messaging is the ability to
take advantage of any other capabilities that can be
applied to SIP sessions, such as multiparty
conferencing.

To reinforce that point: one of the primary reasons
(in my estimation) that SIMPLE has not proposed
solutions for chat rooms is the realization that such
functionality comes for free once a general
conferencing solution is defined. I would posit that
the expectation of SIMPLE is that the solution
created by XCON will be usable for this application.

> I don't know how to add markers to the charter to
> make it obvious how the word "conferencing" is
> intended here, however.

I believe any modifications to the charter that
de-emphasized text as a media type would be a
disservice to a significant number of potential
XCON participants.

/a




From owner-ietf@ietf.org  Thu Aug 21 00:46: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 AAA01899
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 00:46:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19phA0-0006qO-27
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 00:34:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ph9b-0006nQ-Uk
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 00:34: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 AAA01512
	for <ietf@ietf.org>; Thu, 21 Aug 2003 00:34:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ph9Z-00056Q-00
	for ietf@ietf.org; Thu, 21 Aug 2003 00:34:29 -0400
Received: from [206.157.230.254] (helo=hatl0ms20.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ph9Z-000566-00
	for ietf@ietf.org; Thu, 21 Aug 2003 00:34:29 -0400
Received: from mail pickup service by hatl0ms20.CORP.COX.COM with Microsoft SMTPSVC;
	 Thu, 21 Aug 2003 00:34:00 -0400
Received: from bastion.cox.com ([10.230.2.65]) by hatl0ms20.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 20 Aug 2003 21:20:25 -0400
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion.cox.com (8.11.6+Sun/8.11.6) with SMTP id h7L1IxU14019;
	Wed, 20 Aug 2003 21:19:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pdyl-0004U7-B3
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 21:11:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pdvQ-00049V-6Q
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 21:07: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 VAA23293
	for <ietf@ietf.org>; Wed, 20 Aug 2003 21:07:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pdvJ-0002sp-00
	for ietf@ietf.org; Wed, 20 Aug 2003 21:07:33 -0400
Received: from adsl-64-168-10-254.dsl.scrm01.pacbell.net ([64.168.10.254] helo=drakken.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19pdvI-0002sh-00
	for ietf@ietf.org; Wed, 20 Aug 2003 21:07:32 -0400
Received: from drakken.dbc.mtview.ca.us (localhost [127.0.0.1])
	by drakken.dbc.mtview.ca.us (8.12.9/8.12.9) with SMTP id h7L178Lq015063;
	Wed, 20 Aug 2003 18:07:08 -0700 (PDT)
Date: Wed, 20 Aug 2003 18:07:08 -0700
From: Marshall Rose <mrose@dbc.mtview.ca.us>
To: Richard Shockey <richard@shockey.us>
Cc: Keith Moore <moore@cs.utk.edu>, Henry Sinnreich <Henry.Sinnreich@mci.com>,
        vinton.g.cerf@mci.com, jon.peterson@neustar.biz, ietf@ietf.org,
        alan.johnston@mci.com, rsparks@dynamicsoft.com
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030820180708.2a1b18f6.mrose@dbc.mtview.ca.us>
In-Reply-To: <5.2.0.9.2.20030820202023.02d7f3e0@shockey.us>
References: <0HJX00BO4708G3@pmismtp03.wcomnet.com>
	<5.2.0.9.2.20030820083312.02f1a5e0@pop.mcilink.com>
	<0HJX00BO4708G3@pmismtp03.wcomnet.com>
	<5.2.0.9.2.20030820202023.02d7f3e0@shockey.us>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Aug 2003 01:20:27.0983 (UTC) FILETIME=[67B4FDF0:01C36782]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I think the XCON folks were trying to be inclusive in their charter 
> development but frankly I don't think its necessary. The IETF now has three 
> SIP related WG's operating well and producing good work and the scope of 
> the XCON proposal IMHO should be directed at SIP specifically. Its a 
> complex issue, there is a real problem statement and a focused WG could 
> tackle the problem head on and deliver results. This was the direction we 
> took with SIPPING for the specific IM problem and its what we need to do 
> with SIP Conferencing.

richard - unfortunately, this isn't what the proposed charter says or
intends. 
    
i'll repeat what i've said twice before, but i'll use different words:
    
    if the sip folks want to have a working group to work on
    sip-specific conferencing, fine. we can judge the charter on its
    merits in the context of sip.
    
    the xmpp folks have a workable, deployed solution in the
    conferencing space. if they decide to take this work to the ietf,
    then that should also be accorded the same courtesy in being judged
    on its merits in the context of xmpp.
    
    the proposed charter (and jon's clarifications) have a considerably
    larger scope than doing sip-specific conferencing. further, it is
    disingenuous to say that other perspectives will be considered,
    because, to paraphrase sinnreich: "there is but one god, and it's
    name is sip".
    
so, as much as i enjoy these little skirmishes, i repeat my call for
peace:
    
    tailor the proposed charter so that it limits itself to sip-specific
    conference, and no one outside of the sip community will much care...
    
/mtr




From owner-ietf@ietf.org  Thu Aug 21 01:10: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 BAA03085
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 01:10:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19phey-0000MH-1E
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 01:06:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19phcC-0000Dj-6d
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 01:04: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 BAA02924
	for <ietf@ietf.org>; Thu, 21 Aug 2003 01:04:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19phc9-0005Ux-00
	for ietf@ietf.org; Thu, 21 Aug 2003 01:04:01 -0400
Received: from [206.157.230.254] (helo=hatl0ms20.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 19phc8-0005Ue-00
	for ietf@ietf.org; Thu, 21 Aug 2003 01:04:01 -0400
Received: from mail pickup service by hatl0ms20.CORP.COX.COM with Microsoft SMTPSVC;
	 Thu, 21 Aug 2003 01:02:37 -0400
Received: from bastion2.cox.com ([10.225.2.51]) by hatl0ms20.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 20 Aug 2003 20:40:04 -0400
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion2.cox.com (8.11.7+Sun/8.11.6) with SMTP id h7L0dwV13753;
	Wed, 20 Aug 2003 20:39:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pdOm-0002RL-Rs
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 20:33:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pdNV-0002Mx-Iy
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 20:32:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21741
	for <ietf@ietf.org>; Wed, 20 Aug 2003 20:32:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pdNT-0002Ub-00
	for ietf@ietf.org; Wed, 20 Aug 2003 20:32:35 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pdNT-0002UM-00
	for ietf@ietf.org; Wed, 20 Aug 2003 20:32:35 -0400
Received: from rshockeybox.shockey.us (h-68-165-240-37.MCLNVA23.covad.net [68.165.240.37])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h7L0aKa21576;
	Wed, 20 Aug 2003 17:36:20 -0700
Message-Id: <5.2.0.9.2.20030820202023.02d7f3e0@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 20 Aug 2003 20:31:10 -0400
To: Keith Moore <moore@cs.utk.edu>, Henry Sinnreich <Henry.Sinnreich@mci.com>
From: Richard Shockey <richard@shockey.us>
Subject: Re: WG Review: Centralized Conferencing (xcon)
Cc: moore@cs.utk.edu, vinton.g.cerf@mci.com, mrose@dbc.mtview.ca.us,
        jon.peterson@neustar.biz, ietf@ietf.org, alan.johnston@mci.com,
        rsparks@dynamicsoft.com
In-Reply-To: <20030820194308.0ac058c1.moore@cs.utk.edu>
References: <0HJX00BO4708G3@pmismtp03.wcomnet.com>
 <5.2.0.9.2.20030820083312.02f1a5e0@pop.mcilink.com>
 <0HJX00BO4708G3@pmismtp03.wcomnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 21 Aug 2003 00:40:07.0046 (UTC) FILETIME=[C4B75260:01C3677C]
Sender: owner-ietf@ietf.org
Precedence: bulk

At 07:43 PM 8/20/2003 -0400, Keith Moore wrote:

> > It is high time the IETF should get its act together and converge on 
> the one
> > single multiparty (conferencing!) multimedia session protocol: SIP.
>
>Why in the world should IETF bias a conferencing solution toward the telephony
>providers?  I mean, if SIP turned out to be a good solution for everyone, 
>fine.
>But the group shouldn't assume a priori that SIP is the right direction.

Keith with all due respect ..first I would not charactize SIP as having a 
bias towards telephony providers, far from it. Its now supported by a truly 
staggering list of software developers and service providers who may or may 
not have associations with the incumbent global TDM regime including 
Microsoft, Lotus/IBM, and open source providers such as iptel.org 
increasing support from Apple and I suspect AOL as well.

I think the XCON folks were trying to be inclusive in their charter 
development but frankly I don't think its necessary. The IETF now has three 
SIP related WG's operating well and producing good work and the scope of 
the XCON proposal IMHO should be directed at SIP specifically. Its a 
complex issue, there is a real problem statement and a focused WG could 
tackle the problem head on and deliver results. This was the direction we 
took with SIPPING for the specific IM problem and its what we need to do 
with SIP Conferencing.

Most sincerely,

sip:rshockey@iptel.org



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<





From owner-ietf@ietf.org  Thu Aug 21 01:14: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 BAA03652
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 01:14:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19phjo-0000nn-FB
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 01:11:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19phiv-0000d6-D9
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 01:11:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03117
	for <ietf@ietf.org>; Thu, 21 Aug 2003 01:10:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19phit-0005YH-00
	for ietf@ietf.org; Thu, 21 Aug 2003 01:10:59 -0400
Received: from [206.157.230.254] (helo=hatl0ms20.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 19phis-0005XI-00
	for ietf@ietf.org; Thu, 21 Aug 2003 01:10:58 -0400
Received: from mail pickup service by hatl0ms20.CORP.COX.COM with Microsoft SMTPSVC;
	 Thu, 21 Aug 2003 01:09:51 -0400
Received: from bastion2.cox.com ([10.225.2.51]) by hatl0ms20.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 20 Aug 2003 19:56:07 -0400
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion2.cox.com (8.11.7+Sun/8.11.6) with SMTP id h7KNu6V11639;
	Wed, 20 Aug 2003 19:56:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pcdM-0008Um-VG
	for ietf-list@asgard.ietf.org; Wed, 20 Aug 2003 19:44:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pcdF-0008Rp-Qi
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 19:44: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 TAA19539
	for <ietf@ietf.org>; Wed, 20 Aug 2003 19:44:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pcdE-0001ui-00
	for ietf@ietf.org; Wed, 20 Aug 2003 19:44:48 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pcdD-0001uf-00
	for ietf@ietf.org; Wed, 20 Aug 2003 19:44:47 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id EDFE1140DD; Wed, 20 Aug 2003 19:44:47 -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 00986-05; Wed, 20 Aug 2003 19:44: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 6B00B1407F; Wed, 20 Aug 2003 19:44:46 -0400 (EDT)
Date: Wed, 20 Aug 2003 19:43:08 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Henry Sinnreich <Henry.Sinnreich@mci.com>
Cc: moore@cs.utk.edu, vinton.g.cerf@mci.com, mrose@dbc.mtview.ca.us,
        jon.peterson@neustar.biz, ietf@ietf.org, alan.johnston@mci.com,
        rsparks@dynamicsoft.com
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030820194308.0ac058c1.moore@cs.utk.edu>
In-Reply-To: <0HJX00BO4708G3@pmismtp03.wcomnet.com>
References: <5.2.0.9.2.20030820083312.02f1a5e0@pop.mcilink.com>
	<0HJX00BO4708G3@pmismtp03.wcomnet.com>
X-Mailer: Sylpheed version 0.9.3 (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
X-OriginalArrivalTime: 20 Aug 2003 23:56:10.0605 (UTC) FILETIME=[A14659D0:01C36776]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> It is high time the IETF should get its act together and converge on the one
> single multiparty (conferencing!) multimedia session protocol: SIP. 

Why in the world should IETF bias a conferencing solution toward the telephony
providers?  I mean, if SIP turned out to be a good solution for everyone, fine.
But the group shouldn't assume a priori that SIP is the right direction.





From owner-ietf@ietf.org  Thu Aug 21 01:38: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 BAA04974
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 01:38:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19phwO-0002N0-5P
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 01:24:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19phvk-0002Jk-1I
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 01:24: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 BAA04415
	for <ietf@ietf.org>; Thu, 21 Aug 2003 01:24:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19phvh-0005z6-00
	for ietf@ietf.org; Thu, 21 Aug 2003 01:24:14 -0400
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 19phvh-0005yv-00
	for ietf@ietf.org; Thu, 21 Aug 2003 01:24:13 -0400
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id h7L5Nhlt017799
	for <ietf@ietf.org>; Thu, 21 Aug 2003 01:23:43 -0400 (EDT)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <QX7JZF0F>; Thu, 21 Aug 2003 00:23:44 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E86358@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: WG Review: Centralized Conferencing (xcon)
Date: Thu, 21 Aug 2003 00:23:43 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Richard Shockey writes:

> I think the XCON folks were trying to be inclusive
> in their charter development but frankly I don't think
> its necessary. The IETF now has three SIP related WG's
> operating well and producing good work and the scope
> of the XCON proposal IMHO should be directed at SIP
> specifically. Its a complex issue, there is a real
> problem statement and a focused WG could tackle the
> problem head on and deliver results. This was the
> direction we took with SIPPING for the specific IM
> problem and its what we need to do with SIP Conferencing.

I think some clarification is in order.

The SIP conferencing work has been well underway for
quite some time now in the SIP and SIPPING working
groups. It is essentially complete, and will be in WGLC
momentarily. We don't need a SIP conferencing working
group; SIP conferencing already has a home.

That said, for a conferencing solution to be complete,
there are certain things that are required -- such as
floor control and membership permissions -- for which
SIP is simply not appropriate.

The raison d'=EAtre for XCON is precisely to do the
part of conferencing that is not SIP. The relationship
between the XCON protocols and SIP are far looser than
would legitimately warrant the level of concern being
expressed on this list.

For example: to be able to talk about specific media
streams in a conference, you need to be able to identify
streams of media. XCON does so in terms of SDP, since
that is the mechanism used by SIP to establish media
streams.

To examine what this means in the context of the charter's
claim that the solutions developed in XCON will not preclude
operation with other signaling protocols: if someone were
to decide to apply XCON to some theoretical IP-based call
control protocol that used PSTN TDM trunks for conveying
media [1], these identifiers could be replaced with SS7
circuit identification codes.

If the initial proposals being presented as input to
XCON had some strong binding to SIP that made their use
in other contexts difficult, I would understand the
concerns being expressed in this forum. However, the
proposed solutions (all of which I expect to instantly
be accepted as working group items in the case that the
working group is chartered) demonstrate no such binding.
I invite those with concerns to carefully examine the
protocol proposals [2] and indicate where they believe
this not to be the case.

/a

[1] This theoretical protocol is intentionally fantastic
    to avoid the discussion being bogged down with descriptions
    of any political reasons why certain protocol communities
    may elect to use different conferencing solutions.

[2] http://www.softarmor.com/xcon/drafts/



From owner-ietf@ietf.org  Thu Aug 21 01:52: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 BAA05436
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 01:52:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19piGi-0003aj-Ir
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 01:45:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19piGM-0003XW-Ir
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 01:45: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 BAA05293
	for <ietf@ietf.org>; Thu, 21 Aug 2003 01:45:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19piGK-0006Es-00
	for ietf@ietf.org; Thu, 21 Aug 2003 01:45:32 -0400
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 19piGJ-0006EX-00
	for ietf@ietf.org; Thu, 21 Aug 2003 01:45:31 -0400
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id h7L5j1lt017863
	for <ietf@ietf.org>; Thu, 21 Aug 2003 01:45:01 -0400 (EDT)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <QX7JZF0Z>; Thu, 21 Aug 2003 00:45:02 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E86359@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: WG Review: Centralized Conferencing (xcon)
Date: Thu, 21 Aug 2003 00:45:01 -0500
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

Marshall Rose writes:

> the xmpp folks have a workable, deployed solution in the
> conferencing space. if they decide to take this work to the ietf,
> then that should also be accorded the same courtesy in being judged
> on its merits in the context of xmpp.

I can understand that you have concerns that XCON may
produce something so generally useful that it might get
in the way of rubber stamping protocols developed
elsewhere. I do not believe that it is in the greater
interest of the IETF, though, to intentionally cripple
working groups merely to allow for the eventuality of
the introduction of competing work.

/a



From owner-ietf@ietf.org  Thu Aug 21 07:17: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 HAA28679
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 07:17:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pnFP-0002Vn-6I
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 07:04:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pnFJ-0002Tb-W2
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 07:04: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 HAA28272
	for <ietf@ietf.org>; Thu, 21 Aug 2003 07:04:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pnFH-0001ee-00
	for ietf@ietf.org; Thu, 21 Aug 2003 07:04:47 -0400
Received: from [213.172.48.142] (helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 19pnFG-0001eM-00
	for ietf@ietf.org; Thu, 21 Aug 2003 07:04:46 -0400
Received: from consulintel02 ([221.143.6.168])
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v6.8.4.R)
	with ESMTP id 14-md50000000074.tmp
	for <ietf@ietf.org>; Thu, 21 Aug 2003 13:05:51 +0200
Message-ID: <00c601c367d4$205f25a0$a8068fdd@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ipng@sunroof.eng.sun.com>
Cc: <ietf@ietf.org>
References: <4.3.2.7.2.20030820171247.033ceeb0@mailhost.iprg.nokia.com> <20030821104427.GB26313@rvdp.org>
Subject: Re: Moving the ipng mailing list
Date: Thu, 21 Aug 2003 20:05:18 +0900
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Processed: consulintel.es, Thu, 21 Aug 2003 13:05:51 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 221.143.6.168
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Completely agree, even is time (overdue) to get ALL the IETF/ISOC related sites with IPv6 support !

Regards,
Jordi

----- Original Message ----- 
From: "Ronald van der Pol" <Ronald.vanderPol@rvdp.org>
To: "Bob Hinden & Margaret Wasserman" <hinden@iprg.nokia.com>
Cc: <ipng@sunroof.eng.sun.com>; "Margaret Wasserman" <mrw@windriver.com>; "Alain Durand" <Alain.Durand@Sun.COM>; "John Beck"
<John.Beck@Sun.COM>
Sent: Thursday, August 21, 2003 7:44 PM
Subject: Re: Moving the ipng mailing list


> On Wed, Aug 20, 2003 at 17:24:00 -0700, Bob Hinden & Margaret Wasserman wrote:
>
> > The current plan is to move the list to ietf.org.
>
> Can the list be moved to a server that supports IPv6 transport? E.g.,
> it looks like all the ops.ietf.org lists are delivered over IPv6 now.
>
> rvdp
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------
>

*****************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on-line at:
http://www.ipv6-es.com





From owner-ietf@ietf.org  Thu Aug 21 08:59: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 IAA02996
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 08:59:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19povu-0006ud-KE
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 08:52:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19povX-0006sW-98
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 08:52: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 IAA02688
	for <ietf@ietf.org>; Thu, 21 Aug 2003 08:52:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19povW-0002lx-00
	for ietf@ietf.org; Thu, 21 Aug 2003 08:52:30 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19povV-0002ld-00
	for ietf@ietf.org; Thu, 21 Aug 2003 08:52:29 -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 h7LCqfxS008753;
	Thu, 21 Aug 2003 14:52:44 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 21 Aug 2003 14:52:15 +0200
Subject: Re: Moving the ipng mailing list
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <00c601c367d4$205f25a0$a8068fdd@consulintel.es>
Message-Id: <4A9443DF-D3D6-11D7-8839-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 donderdag, aug 21, 2003, at 13:05 Europe/Amsterdam, JORDI PALET 
MARTINEZ wrote:

>> Can the list be moved to a server that supports IPv6 transport? E.g.,
>> it looks like all the ops.ietf.org lists are delivered over IPv6 now.

I have received messages for the multi6@ops.ietf.org list over IPv6 
once in a blue moon, but it's IPv4 99% of the time. Also:

 > host -t mx ops.ietf.org
ops.ietf.org mail is handled (pri=0) by psg.com
 > telnet -6 psg.com 25
Trying 2001:418:1::62...
telnet: connect to address 2001:418:1::62: Operation timed out
telnet: Unable to connect to remote host




From owner-ietf@ietf.org  Thu Aug 21 12:04: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 MAA11512
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 12:04:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19priB-0004jk-Nw
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 11:50:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19prhr-0004fL-6C
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 11:50: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 LAA10748
	for <ietf@ietf.org>; Thu, 21 Aug 2003 11:50:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19prhq-0004js-00
	for ietf@ietf.org; Thu, 21 Aug 2003 11:50:34 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 19prho-0004j5-00
	for ietf@ietf.org; Thu, 21 Aug 2003 11:50:33 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h7LFnvE07553;
	Thu, 21 Aug 2003 08:49:57 -0700
X-mProtect: <200308211549> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (209.157.142.164, claiming to be "spruce.iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdKmJEj7; Thu, 21 Aug 2003 08:49:55 PDT
Message-Id: <4.3.2.7.2.20030821084623.03469b10@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 21 Aug 2003 08:48:23 -0700
To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: Bob Hinden <hinden@iprg.nokia.com>
Subject: IPv6 Support at IETF.ORG [was Moving the ipng mailing list]
Cc: <ietf@ietf.org>
In-Reply-To: <00c601c367d4$205f25a0$a8068fdd@consulintel.es>
References: <4.3.2.7.2.20030820171247.033ceeb0@mailhost.iprg.nokia.com>
 <20030821104427.GB26313@rvdp.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

Jordi,

Yes, I agree this is long overdue.

Bob

At 04:05 AM 8/21/2003, JORDI PALET MARTINEZ wrote:
>Completely agree, even is time (overdue) to get ALL the IETF/ISOC related 
>sites with IPv6 support !
>
>Regards,
>Jordi




From owner-ietf@ietf.org  Thu Aug 21 12:05: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 MAA11539
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 12:05:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19preI-0004B9-H7
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 11:46:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19prdR-00048n-KU
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 11:46: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 LAA10491
	for <ietf@ietf.org>; Thu, 21 Aug 2003 11:45:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19prdP-0004g5-00
	for ietf@ietf.org; Thu, 21 Aug 2003 11:45:59 -0400
Received: from pmesmtp02.wcom.com ([199.249.20.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 19prdK-0004fa-00
	for ietf@ietf.org; Thu, 21 Aug 2003 11:45:55 -0400
Received: from pmismtp04.wcomnet.com ([166.38.62.39])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HJZ00MES7IO5P@firewall.wcom.com> for ietf@ietf.org; Thu,
 21 Aug 2003 15:40:00 +0000 (GMT)
Received: from pmismtp04.wcomnet.com by pmismtp04.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HJZ003017INUW@pmismtp04.wcomnet.com>; Thu,
 21 Aug 2003 15:40:00 +0000 (GMT)
Received: from hsinnreich2 ([166.50.153.111])
 by pmismtp04.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HJZ002E77IGGU@pmismtp04.wcomnet.com>; Thu,
 21 Aug 2003 15:39:59 +0000 (GMT)
Date: Thu, 21 Aug 2003 10:39:52 -0500
From: Henry Sinnreich <Henry.Sinnreich@mci.com>
Subject: RE: WG Review: Centralized Conferencing (xcon)
In-reply-to: <7BFAA4C6-D3E7-11D7-A5AF-0003938AF740@cisco.com>
To: "'Rohan Mahy'" <rohan@cisco.com>,
        "'Henry Sinnreich'" <Henry.Sinnreich@mci.com>
Cc: "'vinton g. cerf'" <vinton.g.cerf@mci.com>,
        "'Marshall Rose'" <mrose@dbc.mtview.ca.us>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>, ietf@ietf.org,
        "'Alan Johnston'" <alan.johnston@mci.com>,
        "'Robert Sparks'" <rsparks@dynamicsoft.com>
Message-id: <0HJZ002E87IGGU@pmismtp04.wcomnet.com>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Office Outlook, Build 11.0.5329
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Thread-index: AcNn9AiSvg+mqGG2QeatgL9Fl6azPgAA89ig
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Leaving the SIP-XMPP discussion aside (nobody will change their mind anyway)
a matter of concern is the 100% dominance of protocol experts in this
discussion and no real participation from conference service operators and
conference platform vendors. This raises several flags...

As a participant in developing IP conference services, I have seen the
challenge of integrating IP conference technology with AAA (OSS) and with
operator support services.

In this light, I believe we need to start with generic requirements for XCON
target systems (what should they be anyway?) and examine/compare the
candidate protocols later. Such a document SHOULD be co-authored by (1)
conferencing services providers first and (2) by conferencing platform
vendors, second.

Could we shift this debate from protocols to requirements?

Henry

> -----Original Message-----
> From: Rohan Mahy [mailto:rohan@cisco.com]
> Sent: Thursday, August 21, 2003 9:55 AM
> To: Henry Sinnreich
> Cc: 'vinton g. cerf'; 'Marshall Rose'; 'Peterson, Jon'; ietf@ietf.org;
> Alan Johnston; Robert Sparks
> Subject: Re: WG Review: Centralized Conferencing (xcon)
> 
> Greetings.
> 
> Henry, If we wanted to do a SIP-only conferencing solution, we would
> have left this work in SIPPING.  However we discovered that several of
> the problems we were trying to solve were applicable to non-SIP
> signaled conferences (including mixed protocol conferences).  We also
> wanted to get wider input from the IETF community since there is a lot
> of previous work that's gone on. Just like RTP/RTCP streams are setup
> by SIP, H.323, MGCP, Megaco, and even proprietary signaling protocols,
> there is no reason that a common approach for conference policy,
> rosters, inter-conference media manipulation, and floor control can't
> be used by vendors which use any signaling protocol.  (I will remind
> you that, for example, my company has an installed base of over 2
> million phones which are using a proprietary protocol.)  Please rest
> assured however that SIPPING would make sure that any SIP-specific
> pieces get done in SIPPING in a way that works with the output of XCON.
> 
> As for Marshall's comments: there is certainly nothing nefarious about
> having a large body of source work when trying to start a Working Group
> (I cite XMPP as a recent example). What is important is for folks to
> focus on the *charter text* and the desired output, rather than make
> assumptions about the intent of those contributors. As for his
> suggestion that a generic conferencing working group should live in
> APPS instead of TSV, please consider that MMUSIC was the original host
> for conferencing work in IETF and therefore there is some precedent for
> the work to happen in TSV.  I am fine with either, but I believe this
> issue was already worked out among Ted, Ned, Allison, and Jon.
> Marshall, if there is something specific that you don't like about the
> charter as a generic conferencing working group, please propose
> alternate rewording.
> 
> thanks,
> -rohan
> co-chair SIP and SIPPING WGs
> 
> On Wednesday, August 20, 2003, at 06:33 AM, Henry Sinnreich wrote:
> > Given the IM background in this discussion, I fail to see why there
> > should
> > be an IM-originated conferencing option to confuse everyone, when SIP
> > conferencing is supporting all types of media and presence and IM just
> > as
> > well (plus events, user preferences, mobility etc.) in a consistent
> > way.
> >
> > It is high time the IETF should get its act together and converge on
> > the one
> > single multiparty (conferencing!) multimedia session protocol: SIP. And
> > avoid such confusions as Marshall does in the attached.
> >
> > Look at the huge penetration of SIP with wired and mobile service
> > providers,
> > as well as on tens of millions of desktops: The IETF SIP work is
> > already the
> > de facto standard. Let's just stay focused.
> >
> > It is thus entirely appropriate XCON should be a SIP oriented WG for
> > centralized conferencing.
> >
> > Thanks,
> >
> > Henry Sinnreich
> > MCI
> >
> >> -----Original Message-----
> >> From: vinton g. cerf [mailto:vinton.g.cerf@mci.com]
> >> Sent: Wednesday, August 20, 2003 7:39 AM
> >> To: Marshall Rose; Peterson, Jon
> >> Cc: ietf@ietf.org
> >> Subject: Re: WG Review: Centralized Conferencing (xcon)
> >>
> >> As a prospective supplier of SIP-based services, I am very interested
> >> in
> >> seeing SIP-based definitions for the support of a wide range of
> >> conferencing tools ranging from voice/video to IM and mixtures that
> >> might
> >> include a participant with only a phone and a fax machine. This is
> >> not to
> >> say that I would reject other protocol bases for such service but
> >> rather
> >> to say that we have a significant investment in SIP-based services and
> >> would like to see them expanded in standard ways so as to encourage
> >> interworking among parties offering such services.
> >>
> >> I leave it to the IESG and other interested parties to figure out how
> >> best
> >> to achieve that objective. Perhaps a SIP-oriented WG is the
> >> appropriate
> >> vehicle, recognizing that what ever procedures are invented, rooted
> >> in the
> >> SIP system, might well have counterparts in other signalling
> >> enviroments
> >> and could therefore be re-incarnated in them. Whether that would
> >> confer
> >> interworking between the SIP and non-SIP systems is beyond my ability
> >> to
> >> predict.
> >>
> >> Vint
> >>
> >>  At 03:29 PM 8/19/2003 -0700, Marshall Rose wrote:
> >>> jon - sorry for the delay in replying.
> >>>
> >>> fundamentally, i think it comes down to accuracy in labelling. if
> >>> the sip
> >>> folks want to do conferencing, then they should have a working group
> >>> to
> >> do
> >>> that. however, the charter for that working group should not imply
> >>> that
> >> the
> >>> scope of the working group is anything beyond sip.
> >>>
> >>> a reasonable person reading the charter would conclude that the
> >>> scope of
> >> the
> >>> working group is somewhat more generic than sip.
> >>>
> >>> if the goal for this working group is to be generic, then the
> >>> charter is
> >>> likely unacceptable since it assumes "facts not entered into
> >>> evidence",
> >>> i.e., it is sip-centric, and there is a fair body of deployed work
> >>> that
> >>> manages to do conferencing very well without using that acronym. if
> >>> that
> >> is
> >>> not the intention, then  i suggest that the working group be called
> >>> something like sipxcon to avoid any confusion.
> >>>
> >>> as to whether the working group belongs in apps or tsv, a generic
> >>> conferencing working group clearly belongs in apps. however, a sip-
> >> specific
> >>> working group can probably comfortably reside in either.
> >>>
> >>> /mtr
> >>
> >> Vint Cerf
> >> SVP Architecture & Technology
> >> 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 Aug 21 13:47: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 NAA16438
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 13:47:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ptMk-0002ZG-Bs
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 13:36:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ptLb-0002Ul-12
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 13:35: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 NAA16026
	for <ietf@ietf.org>; Thu, 21 Aug 2003 13:35:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ptLZ-00067t-00
	for ietf@ietf.org; Thu, 21 Aug 2003 13:35:41 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ptLY-00067q-00
	for ietf@ietf.org; Thu, 21 Aug 2003 13:35:41 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 619F41411A; Thu, 21 Aug 2003 13:35: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 17420-05; Thu, 21 Aug 2003 13:35:39 -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 BF4E5140E9; Thu, 21 Aug 2003 13:35:38 -0400 (EDT)
Date: Thu, 21 Aug 2003 13:35:37 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Henry Sinnreich <Henry.Sinnreich@mci.com>
Cc: moore@cs.utk.edu, rohan@cisco.com, Henry.Sinnreich@mci.com,
        vinton.g.cerf@mci.com, mrose@dbc.mtview.ca.us,
        jon.peterson@neustar.biz, ietf@ietf.org, alan.johnston@mci.com,
        rsparks@dynamicsoft.com
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030821133537.7527d5c3.moore@cs.utk.edu>
In-Reply-To: <0HJZ002E87IGGU@pmismtp04.wcomnet.com>
References: <7BFAA4C6-D3E7-11D7-A5AF-0003938AF740@cisco.com>
	<0HJZ002E87IGGU@pmismtp04.wcomnet.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

> Leaving the SIP-XMPP discussion aside (nobody will change their mind
> anyway) a matter of concern is the 100% dominance of protocol experts
> in this discussion and no real participation from conference service
> operators and conference platform vendors. This raises several
> flags...

once again, an attempt to coerce IETF into preserving the status quo in
the market.

is it really IETF's job to legislate full employment for conference
service operators?



From owner-ietf@ietf.org  Thu Aug 21 14:00: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 NAA17167
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 13:59:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ptdB-0003VH-PK
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 13:53:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pqoE-0002F9-Rl
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 10:53: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 KAA08670
	for <ietf@ietf.org>; Thu, 21 Aug 2003 10:53:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pqoD-0004BE-00
	for ietf@ietf.org; Thu, 21 Aug 2003 10:53:05 -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 19pqoD-0004Ay-00
	for ietf@ietf.org; Thu, 21 Aug 2003 10:53:05 -0400
Received: from cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 21 Aug 2003 08:00:56 -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 h7LEqN8s028990;
	Thu, 21 Aug 2003 07:52:24 -0700 (PDT)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AKQ00113;
	Thu, 21 Aug 2003 07:44:09 -0700 (PDT)
Date: Thu, 21 Aug 2003 07:55:20 -0700
Subject: Re: WG Review: Centralized Conferencing (xcon)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "'vinton g. cerf'" <vinton.g.cerf@mci.com>,
        "'Marshall Rose'" <mrose@dbc.mtview.ca.us>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>, ietf@ietf.org,
        Alan Johnston <alan.johnston@mci.com>,
        Robert Sparks <rsparks@dynamicsoft.com>
To: Henry Sinnreich <Henry.Sinnreich@mci.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <0HJX00BO4708G3@pmismtp03.wcomnet.com>
Message-Id: <7BFAA4C6-D3E7-11D7-A5AF-0003938AF740@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

Greetings.

Henry, If we wanted to do a SIP-only conferencing solution, we would 
have left this work in SIPPING.  However we discovered that several of 
the problems we were trying to solve were applicable to non-SIP 
signaled conferences (including mixed protocol conferences).  We also 
wanted to get wider input from the IETF community since there is a lot 
of previous work that's gone on. Just like RTP/RTCP streams are setup 
by SIP, H.323, MGCP, Megaco, and even proprietary signaling protocols, 
there is no reason that a common approach for conference policy, 
rosters, inter-conference media manipulation, and floor control can't 
be used by vendors which use any signaling protocol.  (I will remind 
you that, for example, my company has an installed base of over 2 
million phones which are using a proprietary protocol.)  Please rest 
assured however that SIPPING would make sure that any SIP-specific 
pieces get done in SIPPING in a way that works with the output of XCON.

As for Marshall's comments: there is certainly nothing nefarious about 
having a large body of source work when trying to start a Working Group 
(I cite XMPP as a recent example). What is important is for folks to 
focus on the *charter text* and the desired output, rather than make 
assumptions about the intent of those contributors. As for his 
suggestion that a generic conferencing working group should live in 
APPS instead of TSV, please consider that MMUSIC was the original host 
for conferencing work in IETF and therefore there is some precedent for 
the work to happen in TSV.  I am fine with either, but I believe this 
issue was already worked out among Ted, Ned, Allison, and Jon.  
Marshall, if there is something specific that you don't like about the 
charter as a generic conferencing working group, please propose 
alternate rewording.

thanks,
-rohan
co-chair SIP and SIPPING WGs

On Wednesday, August 20, 2003, at 06:33 AM, Henry Sinnreich wrote:
> Given the IM background in this discussion, I fail to see why there 
> should
> be an IM-originated conferencing option to confuse everyone, when SIP
> conferencing is supporting all types of media and presence and IM just 
> as
> well (plus events, user preferences, mobility etc.) in a consistent 
> way.
>
> It is high time the IETF should get its act together and converge on 
> the one
> single multiparty (conferencing!) multimedia session protocol: SIP. And
> avoid such confusions as Marshall does in the attached.
>
> Look at the huge penetration of SIP with wired and mobile service 
> providers,
> as well as on tens of millions of desktops: The IETF SIP work is 
> already the
> de facto standard. Let's just stay focused.
>
> It is thus entirely appropriate XCON should be a SIP oriented WG for
> centralized conferencing.
>
> Thanks,
>
> Henry Sinnreich
> MCI
>
>> -----Original Message-----
>> From: vinton g. cerf [mailto:vinton.g.cerf@mci.com]
>> Sent: Wednesday, August 20, 2003 7:39 AM
>> To: Marshall Rose; Peterson, Jon
>> Cc: ietf@ietf.org
>> Subject: Re: WG Review: Centralized Conferencing (xcon)
>>
>> As a prospective supplier of SIP-based services, I am very interested 
>> in
>> seeing SIP-based definitions for the support of a wide range of
>> conferencing tools ranging from voice/video to IM and mixtures that 
>> might
>> include a participant with only a phone and a fax machine. This is 
>> not to
>> say that I would reject other protocol bases for such service but 
>> rather
>> to say that we have a significant investment in SIP-based services and
>> would like to see them expanded in standard ways so as to encourage
>> interworking among parties offering such services.
>>
>> I leave it to the IESG and other interested parties to figure out how 
>> best
>> to achieve that objective. Perhaps a SIP-oriented WG is the 
>> appropriate
>> vehicle, recognizing that what ever procedures are invented, rooted 
>> in the
>> SIP system, might well have counterparts in other signalling 
>> enviroments
>> and could therefore be re-incarnated in them. Whether that would 
>> confer
>> interworking between the SIP and non-SIP systems is beyond my ability 
>> to
>> predict.
>>
>> Vint
>>
>>  At 03:29 PM 8/19/2003 -0700, Marshall Rose wrote:
>>> jon - sorry for the delay in replying.
>>>
>>> fundamentally, i think it comes down to accuracy in labelling. if 
>>> the sip
>>> folks want to do conferencing, then they should have a working group 
>>> to
>> do
>>> that. however, the charter for that working group should not imply 
>>> that
>> the
>>> scope of the working group is anything beyond sip.
>>>
>>> a reasonable person reading the charter would conclude that the 
>>> scope of
>> the
>>> working group is somewhat more generic than sip.
>>>
>>> if the goal for this working group is to be generic, then the 
>>> charter is
>>> likely unacceptable since it assumes "facts not entered into 
>>> evidence",
>>> i.e., it is sip-centric, and there is a fair body of deployed work 
>>> that
>>> manages to do conferencing very well without using that acronym. if 
>>> that
>> is
>>> not the intention, then  i suggest that the working group be called
>>> something like sipxcon to avoid any confusion.
>>>
>>> as to whether the working group belongs in apps or tsv, a generic
>>> conferencing working group clearly belongs in apps. however, a sip-
>> specific
>>> working group can probably comfortably reside in either.
>>>
>>> /mtr
>>
>> Vint Cerf
>> SVP Architecture & Technology
>> 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 Aug 21 13:59: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 NAA17164
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 13:59:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ptdC-0003VZ-I3
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 13:53:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19psYB-0000Ob-Ii
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 12:44: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 MAA13728
	for <ietf@ietf.org>; Thu, 21 Aug 2003 12:44:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19psY9-0005aO-00
	for ietf@ietf.org; Thu, 21 Aug 2003 12:44:37 -0400
Received: from [206.14.210.116] (helo=mail.xythos.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19psY8-0005aK-00
	for ietf@ietf.org; Thu, 21 Aug 2003 12:44:36 -0400
Received: from ravms by mail.xythos.com with mail-ok (Exim 3.36 #3)
	id 19psXt-0006xS-00; Thu, 21 Aug 2003 16:44:21 +0000
Received: from [198.144.203.248] (helo=lisalap)
	by mail.xythos.com with asmtp (Exim 3.36 #3)
	id 19psXp-0006vD-00; Thu, 21 Aug 2003 16:44:19 +0000
From: "Lisa Dusseault" <lisa@xythos.com>
To: "'Keith Moore'" <moore@cs.utk.edu>,
        "'Henry Sinnreich'" <Henry.Sinnreich@mci.com>
Cc: <vinton.g.cerf@mci.com>, <mrose@dbc.mtview.ca.us>,
        <jon.peterson@neustar.biz>, <ietf@ietf.org>, <alan.johnston@mci.com>,
        <rsparks@dynamicsoft.com>
Subject: RE: WG Review: Centralized Conferencing (xcon)
Date: Thu, 21 Aug 2003 09:44:34 -0700
Message-ID: <013801c36803$9599c8a0$f8cb90c6@lisalap>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-reply-to: <20030820194308.0ac058c1.moore@cs.utk.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Envelope-To: alan.johnston@mci.com,
 Henry.Sinnreich@mci.com,
 ietf@ietf.org,
 jon.peterson@neustar.biz,
 moore@cs.utk.edu,
 mrose@dbc.mtview.ca.us,
 rsparks@dynamicsoft.com,
 vinton.g.cerf@mci.com
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I'm also concerned that conferencing semantics could lead to 
basic interoperability problems that would be difficult to 
surmount.  If you can imagine XMPP in common usage for either
instant messaging or software agent communication (think 'bots')
and also SIMPLE in common usage for instant messaging, with 
SIP already deployed for joining conferences, then we have to 
plan for conferencing servers that can choose to support 
XMPP and SIP/SIMPLE access without crippling either protocol
suite or requiring client rewrites.

Lisa

> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On 
> Behalf Of Keith Moore
> Sent: Wednesday, August 20, 2003 4:43 PM
> To: Henry Sinnreich
> Cc: moore@cs.utk.edu; vinton.g.cerf@mci.com; 
> mrose@dbc.mtview.ca.us; jon.peterson@neustar.biz; 
> ietf@ietf.org; alan.johnston@mci.com; rsparks@dynamicsoft.com
> Subject: Re: WG Review: Centralized Conferencing (xcon)
> 
> 
> > It is high time the IETF should get its act together and 
> converge on 
> > the one single multiparty (conferencing!) multimedia 
> session protocol: 
> > SIP.
> 
> Why in the world should IETF bias a conferencing solution 
> toward the telephony providers?  I mean, if SIP turned out to 
> be a good solution for everyone, fine. But the group 
> shouldn't assume a priori that SIP is the right direction.
> 
> 
> 
> 







From owner-ietf@ietf.org  Thu Aug 21 14:01: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 OAA17445
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 14:01:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pti2-00045z-1E
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 13:58:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ptfs-0003lZ-Gc
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 13:56: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 NAA16954
	for <ietf@ietf.org>; Thu, 21 Aug 2003 13:56:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ptfr-0006M2-00
	for ietf@ietf.org; Thu, 21 Aug 2003 13:56:39 -0400
Received: from iserver.sj.symbol.com ([63.145.233.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ptfq-0006Ls-00
	for ietf@ietf.org; Thu, 21 Aug 2003 13:56:38 -0400
Received: from gwianameserver.sj.symbol.com (symsjdmz.sj.symbol.com [63.145.233.50])
	by iserver.sj.symbol.com (8.12.8/8.12.8) with ESMTP id h7LHokwQ027427
	for <ietf@ietf.org>; Thu, 21 Aug 2003 10:50:46 -0700 (PDT)
Received: from SJ-DOM-MTA by gwianameserver.sj.symbol.com
	with Novell_GroupWise; Thu, 21 Aug 2003 10:56:32 -0700
Message-Id: <sf44a560.004@gwianameserver.sj.symbol.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2
Date: Thu, 21 Aug 2003 10:56:19 -0700
From: "Clint Chaplin" <cchaplin@sj.symbol.com>
To: <ietf@ietf.org>
Subject: www.ietf.org.
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

What's going on with the www.ietf.org web site?  All I'm getting is the
default Apache test page.....

Clint (JOATMON) Chaplin



From owner-ietf@ietf.org  Thu Aug 21 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 OAA19316
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 14:23:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pu0R-00067m-19
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 14:17:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ptwp-0005x4-MB
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 14:14: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 OAA18332
	for <ietf@ietf.org>; Thu, 21 Aug 2003 14:14:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ptwo-0006hf-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:14:10 -0400
Received: from adsl-64-168-10-254.dsl.scrm01.pacbell.net ([64.168.10.254] helo=drakken.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ptwn-0006hW-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:14:09 -0400
Received: from drakken.dbc.mtview.ca.us (localhost [127.0.0.1])
	by drakken.dbc.mtview.ca.us (8.12.9/8.12.9) with SMTP id h7LIE3Lq020565;
	Thu, 21 Aug 2003 11:14:03 -0700 (PDT)
Date: Thu, 21 Aug 2003 11:14:03 -0700
From: Marshall Rose <mrose@dbc.mtview.ca.us>
To: Adam Roach <adam@dynamicsoft.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030821111403.35bea5b8.mrose@dbc.mtview.ca.us>
In-Reply-To: <9BF66EBF6BEFD942915B4D4D45C051F3E86359@dyn-tx-exch-001.dynamicsoft.com>
References: <9BF66EBF6BEFD942915B4D4D45C051F3E86359@dyn-tx-exch-001.dynamicsoft.com>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

here is your reply to me:

> > the xmpp folks have a workable, deployed solution in the
> > conferencing space. if they decide to take this work to the ietf,
> > then that should also be accorded the same courtesy in being judged
> > on its merits in the context of xmpp.
> 
> I can understand that you have concerns that XCON may
> produce something so generally useful that it might get
> in the way of rubber stamping protocols developed
> elsewhere. I do not believe that it is in the greater
> interest of the IETF, though, to intentionally cripple
> working groups merely to allow for the eventuality of
> the introduction of competing work.
    
here is your reply to richard
    
> ...
> However, the
> proposed solutions (all of which I expect to instantly
> be accepted as working group items in the case that the
> working group is chartered) demonstrate no such binding.
> ...
    
accordingly, i think your statement regarding "rubber stamping" is
pointed in the wrong direction... in addition to the controversial
wording in the proposed charter, we now have an issue regarding bias on
the part of the proposed chairs...
    
/mtr



From owner-ietf@ietf.org  Thu Aug 21 14:23: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 OAA19320
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 14:23:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pu0R-000699-Sg
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 14:17:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ptyo-00061N-CR
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 14:16: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 OAA18553
	for <ietf@ietf.org>; Thu, 21 Aug 2003 14:16:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ptym-0006lQ-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:16:12 -0400
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ptyc-0006ix-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:16:03 -0400
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id h7LIEqlt021885;
	Thu, 21 Aug 2003 14:14:52 -0400 (EDT)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <QX7JZHGW>; Thu, 21 Aug 2003 13:14:53 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E86378@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Lisa Dusseault'" <lisa@xythos.com>, "'Keith Moore'" <moore@cs.utk.edu>,
        "'Henry Sinnreich'" <Henry.Sinnreich@mci.com>
Cc: vinton.g.cerf@mci.com, mrose@dbc.mtview.ca.us, jon.peterson@neustar.biz,
        ietf@ietf.org, alan.johnston@mci.com,
        Robert Sparks <rsparks@dynamicsoft.com>
Subject: RE: WG Review: Centralized Conferencing (xcon)
Date: Thu, 21 Aug 2003 13:14:51 -0500
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

Lisa Dusseault writes:

> I'm also concerned that conferencing semantics could lead to 
> basic interoperability problems that would be difficult to 
> surmount.

Once again, I implore those with concerns to read the
XCON input documents. As can be easily verified, the
model being proposed in no way binds itself to any
SIP-specific concepts.

/a



From owner-ietf@ietf.org  Thu Aug 21 14:23: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 OAA19435
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 14:23:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pu0S-00069F-6Z
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 14:17:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ptz1-00061S-Vc
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 14: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 OAA18596
	for <ietf@ietf.org>; Thu, 21 Aug 2003 14:16:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ptz0-0006ma-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:16:26 -0400
Received: from fw.osdl.org ([65.172.181.6] helo=mail.osdl.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ptyn-0006j0-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:16:13 -0400
Received: from dragon.pdx.osdl.net (dragon.pdx.osdl.net [172.20.1.27])
	by mail.osdl.org (8.11.6/8.11.6) with SMTP id h7LIFPo12289;
	Thu, 21 Aug 2003 11:15:25 -0700
Date: Thu, 21 Aug 2003 11:11:16 -0700
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Clint Chaplin" <cchaplin@sj.symbol.com>
Cc: ietf@ietf.org
Subject: Re: www.ietf.org.
Message-Id: <20030821111116.5f3a41e5.rddunlap@osdl.org>
In-Reply-To: <sf44a560.004@gwianameserver.sj.symbol.com>
References: <sf44a560.004@gwianameserver.sj.symbol.com>
Organization: OSDL
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i686-pc-linux-gnu)
X-Face: +5V?h'hZQPB9<D&+Y;ig/:L-F$8p'$7h4BBmK}zo}[{h,eqHI1X}]1UhhR{49GL33z6Oo!`
 !Ys@HV,^(Xp,BToM.;N_W%gT|&/I#H@Z:ISaK9NqH%&|AO|9i/nB@vD:Km&=R2_?O<_V^7?St>kW
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 Thu, 21 Aug 2003 10:56:19 -0700 "Clint Chaplin" <cchaplin@sj.symbol.com> wrote:

| What's going on with the www.ietf.org web site?  All I'm getting is the
| default Apache test page.....

It works for me.

--
~Randy
"Everything is relative."



From owner-ietf@ietf.org  Thu Aug 21 14:24: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 OAA19511
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 14:24:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pu0S-00069L-Kn
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 14:17:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ptz3-00061U-5h
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 14:16: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 OAA18613
	for <ietf@ietf.org>; Thu, 21 Aug 2003 14:16:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ptz1-0006mo-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:16:27 -0400
Received: from mail.krawutschke.com ([195.234.143.25] helo=joshua.krawutschke.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ptyx-0006jm-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:16:24 -0400
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: www.ietf.org.
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Thu, 21 Aug 2003 18:15:52 -0000
Message-ID: <C50038D33CB70E41920AD6D853AA23F404FC2B@Joshua.krawutschke.org>
Thread-Topic: www.ietf.org.
Thread-Index: AcNoD0KPH//bztwEQpS4F/RizpofRQAAOHxg
From: "Matthias Krawutschke" <Matthias@krawutschke.com>
To: "Clint Chaplin" <cchaplin@sj.symbol.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Clint,

this is wrong. If i do that I've got the correct page from IETF.
Please clear your Cache or proxy.

Matthias


-----Urspr=FCngliche Nachricht-----
Von: Clint Chaplin [mailto:cchaplin@sj.symbol.com]=20
Gesendet: Donnerstag, 21. August 2003 17:56
An: ietf@ietf.org
Betreff: www.ietf.org.

What's going on with the www.ietf.org web site?  All I'm getting is the
default Apache test page.....

Clint (JOATMON) Chaplin






From owner-ietf@ietf.org  Thu Aug 21 14:26: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 OAA20017
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 14:26:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pu6N-0006gw-Aq
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 14:24:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pu25-0006CQ-I7
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 14:19: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 OAA18986
	for <ietf@ietf.org>; Thu, 21 Aug 2003 14:19:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pu24-0006qi-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:19:36 -0400
Received: from adsl-64-168-10-254.dsl.scrm01.pacbell.net ([64.168.10.254] helo=drakken.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19pu23-0006qZ-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:19:35 -0400
Received: from drakken.dbc.mtview.ca.us (localhost [127.0.0.1])
	by drakken.dbc.mtview.ca.us (8.12.9/8.12.9) with SMTP id h7LIJOLq020266;
	Thu, 21 Aug 2003 11:19:25 -0700 (PDT)
Date: Thu, 21 Aug 2003 11:19:24 -0700
From: Marshall Rose <mrose@dbc.mtview.ca.us>
To: Rohan Mahy <rohan@cisco.com>
Cc: Henry Sinnreich <Henry.Sinnreich@mci.com>,
        "'vinton g. cerf'" <vinton.g.cerf@mci.com>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>, ietf@ietf.org,
        Alan Johnston <alan.johnston@mci.com>,
        Robert Sparks <rsparks@dynamicsoft.com>
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030821111924.6a55fd5e.mrose@dbc.mtview.ca.us>
In-Reply-To: <7BFAA4C6-D3E7-11D7-A5AF-0003938AF740@cisco.com>
References: <0HJX00BO4708G3@pmismtp03.wcomnet.com>
	<7BFAA4C6-D3E7-11D7-A5AF-0003938AF740@cisco.com>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> As for Marshall's comments: there is certainly nothing nefarious about 
> having a large body of source work when trying to start a Working Group 
> (I cite XMPP as a recent example). What is important is for folks to 
> focus on the *charter text* and the desired output, rather than make 
> assumptions about the intent of those contributors.
    
and, as has been repeatedly pointed out, the text in the proposed
charter is rather poor. we now have four sets of people with entirely
different interpretations (some from the SIP camp, some from the XMPP
camp, plus the IETF chair).
    
    
> Marshall, if there is something specific that you don't like about the 
> charter as a generic conferencing working group, please propose 
> alternate rewording.

that's easy:
    
    1,$s/conferencing/SIP-based conferencing/g
    
/mtr



From owner-ietf@ietf.org  Thu Aug 21 14:29: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 OAA20366
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 14:29:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pu6N-0006hJ-NL
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 14:24:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pu2r-0006FN-PC
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 14:20: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 OAA19037
	for <ietf@ietf.org>; Thu, 21 Aug 2003 14:20:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pu2q-0006rq-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:20:24 -0400
Received: from adsl-64-168-10-254.dsl.scrm01.pacbell.net ([64.168.10.254] helo=drakken.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19pu2p-0006rn-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:20:23 -0400
Received: from drakken.dbc.mtview.ca.us (localhost [127.0.0.1])
	by drakken.dbc.mtview.ca.us (8.12.9/8.12.9) with SMTP id h7LIKBLq021171;
	Thu, 21 Aug 2003 11:20:11 -0700 (PDT)
Date: Thu, 21 Aug 2003 11:20:11 -0700
From: Marshall Rose <mrose@dbc.mtview.ca.us>
To: Henry Sinnreich <Henry.Sinnreich@mci.com>
Cc: "'Rohan Mahy'" <rohan@cisco.com>,
        "'Henry Sinnreich'" <Henry.Sinnreich@mci.com>,
        "'vinton g. cerf'" <vinton.g.cerf@mci.com>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>, ietf@ietf.org,
        "'Alan Johnston'" <alan.johnston@mci.com>,
        "'Robert Sparks'" <rsparks@dynamicsoft.com>
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030821112011.05752fc2.mrose@dbc.mtview.ca.us>
In-Reply-To: <0HJZ002E87IGGU@pmismtp04.wcomnet.com>
References: <7BFAA4C6-D3E7-11D7-A5AF-0003938AF740@cisco.com>
	<0HJZ002E87IGGU@pmismtp04.wcomnet.com>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> In this light, I believe we need to start with generic requirements for XCON
> target systems (what should they be anyway?) and examine/compare the
> candidate protocols later. Such a document SHOULD be co-authored by (1)
> conferencing services providers first and (2) by conferencing platform
> vendors, second.
> 
> Could we shift this debate from protocols to requirements?

something we can both agree on!
    
cheers,
    
/mtr



From owner-ietf@ietf.org  Thu Aug 21 14:40: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 OAA21270
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 14:40:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19puIq-0000y0-Qg
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 14:36:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19puDR-0000Wb-4x
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 14:31: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 OAA20552
	for <ietf@ietf.org>; Thu, 21 Aug 2003 14:31:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19puDP-0007ET-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:31:19 -0400
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 19puDO-0007Dn-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:31:18 -0400
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id h7LIUclt021973;
	Thu, 21 Aug 2003 14:30:38 -0400 (EDT)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <QX7JZHHP>; Thu, 21 Aug 2003 13:30:39 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E8637C@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Marshall Rose'" <mrose@dbc.mtview.ca.us>,
        Adam Roach
	 <adam@dynamicsoft.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: WG Review: Centralized Conferencing (xcon)
Date: Thu, 21 Aug 2003 13:30:38 -0500
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

Marshall Rose [mailto:mrose@dbc.mtview.ca.us] writes:

> > However, the
> > proposed solutions (all of which I expect to instantly
> > be accepted as working group items in the case that the
> > working group is chartered) demonstrate no such binding.
> > ...
>     
> accordingly, i think your statement regarding "rubber stamping" is
> pointed in the wrong direction... in addition to the controversial
> wording in the proposed charter, we now have an issue 
> regarding bias on the part of the proposed chairs...

An understandable interpretation of my words (especially
taken out of the context of the larger point I was trying
to make), but not what I intended.

That paragraph was intended to convey what I perceived the
overall feel of the participants in the BOF to be. Any
decisions, of course, will be taken to the working group
for consensus.

/a



From owner-ietf@ietf.org  Thu Aug 21 14:49: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 NAA17163
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 13:59:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ptZJ-0003Dg-OR
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 13:49:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pdG8-000207-HQ
	for ietf@asgard.ietf.org; Wed, 20 Aug 2003 20:25: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 UAA21481
	for <ietf@ietf.org>; Wed, 20 Aug 2003 20:24:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pdG5-0002RA-00
	for ietf@ietf.org; Wed, 20 Aug 2003 20:24:58 -0400
Received: from pmesmtp01.wcom.com ([199.249.20.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pdG5-0002Qu-00
	for ietf@ietf.org; Wed, 20 Aug 2003 20:24:57 -0400
Received: from pmismtp01.wcomnet.com ([166.38.62.36])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HJY00KGP0VDGT@firewall.wcom.com> for ietf@ietf.org; Thu,
 21 Aug 2003 00:18:49 +0000 (GMT)
Received: from pmismtp01.wcomnet.com by pmismtp01.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HJY006010VD6Z@pmismtp01.wcomnet.com>; Thu,
 21 Aug 2003 00:18:49 +0000 (GMT)
Received: from vint.mci.com ([166.50.98.17])
 by pmismtp01.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HJY000HH0VBPY@pmismtp01.wcomnet.com>; Thu,
 21 Aug 2003 00:18:49 +0000 (GMT)
Date: Wed, 20 Aug 2003 20:18:43 -0400
From: "vinton g. cerf" <vinton.g.cerf@mci.com>
Subject: Re: WG Review: Centralized Conferencing (xcon)
In-reply-to: <20030820194308.0ac058c1.moore@cs.utk.edu>
X-Sender: vcerf@pop.mcilink.com
To: Keith Moore <moore@cs.utk.edu>, Henry Sinnreich <henry.sinnreich@mci.com>
Cc: moore@cs.utk.edu, mrose@dbc.mtview.ca.us, jon.peterson@neustar.biz,
        ietf@ietf.org, alan.johnston@mci.com, rsparks@dynamicsoft.com
Message-id: <5.2.0.9.2.20030820201708.03006130@pop.mcilink.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Content-type: text/plain; charset=us-ascii
References: <0HJX00BO4708G3@pmismtp03.wcomnet.com>
 <5.2.0.9.2.20030820083312.02f1a5e0@pop.mcilink.com>
 <0HJX00BO4708G3@pmismtp03.wcomnet.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

keith,

SIP may have been initially motivated by telephony style applications but it is a very general and extensible negotiation protocol - it was that aspect that grabbed my attention when I first heard about Schulzrinne's work on it several years ago. I think the point really is that SIP is extensible and may be a very reasonable platform on which to build a wide range of peer to peer and distributed application control.

vint

At 07:43 PM 8/20/2003 -0400, Keith Moore wrote:
>Why in the world should IETF bias a conferencing solution toward the telephony
>providers?  I mean, if SIP turned out to be a good solution for everyone, fine.
>But the group shouldn't assume a priori that SIP is the right direction.

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 Aug 21 14:49: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 OAA21852
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 14:49:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19puIs-00010i-HY
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 14:36:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19puHV-0000r7-8S
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 14:35: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 OAA20972
	for <ietf@ietf.org>; Thu, 21 Aug 2003 14:35:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19puHT-0007K9-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:35:31 -0400
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19puHT-0007K6-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:35:31 -0400
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Thu, 21 Aug 2003 14:35:28 -0400
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: Pretty clear ... SIP
Date: Thu, 21 Aug 2003 14:35:28 -0400
Message-ID: <20030821183528722.AAA161@hq.lindsayelec.com@rflooker1>
Sender: owner-ietf@ietf.org
Precedence: bulk

Since SIP is IETF not ITU its only reasonable to have internet believers
lean towards it.

H.323 ? Ahhh no thanks.

No serious look at these can even consider H.323 etc and its derivitives as
useful in the general case. The only reason they were used is the absence of
a better alternative.

Try to hook your Sony Playstation up through H.323

When would that move through committee? Spring of 2010 ??

Oh. Another reason for IETF to believe in it is that its basically a free
comm technology. H.323 wants to drag in the old timers and their costs
structures... dependance of geography, etc so there is a credible reason by
most criterea.

Regs,
Dan




From owner-ietf@ietf.org  Thu Aug 21 14: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 OAA21857
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 14:49:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19puIr-000107-Pe
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 14:36:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19puG4-0000ol-8V
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 14:34: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 OAA20822
	for <ietf@ietf.org>; Thu, 21 Aug 2003 14:33:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19puG2-0007Iv-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:34:02 -0400
Received: from 96.136.33.65.cfl.rr.com ([65.33.136.96] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19puFm-0007Ig-00
	for ietf@ietf.org; Thu, 21 Aug 2003 14:34:02 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19paDP-0001vQ-00; Wed, 20 Aug 2003 17:09:59 -0400
Date: Wed, 20 Aug 2003 17:09:31 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Matthias Krawutschke <Matthias@krawutschke.com>
cc: Clint Chaplin <cchaplin@sj.symbol.com>, <ietf@ietf.org>
Subject: Re: AW: www.ietf.org.
In-Reply-To: <C50038D33CB70E41920AD6D853AA23F404FC2B@Joshua.krawutschke.org>
Message-ID: <Pine.LNX.4.44.0308201708540.7255-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: QUOTED-PRINTABLE

i get an unknown host with ping6 www.ietf.org

scott


On Thu, 21 Aug 2003, Matthias Krawutschke wrote:

> Clint,
>
> this is wrong. If i do that I've got the correct page from IETF.
> Please clear your Cache or proxy.
>
> Matthias
>
>
> -----Urspr=FCngliche Nachricht-----
> Von: Clint Chaplin [mailto:cchaplin@sj.symbol.com]
> Gesendet: Donnerstag, 21. August 2003 17:56
> An: ietf@ietf.org
> Betreff: www.ietf.org.
>
> What's going on with the www.ietf.org web site?  All I'm getting is the
> default Apache test page.....
>
> Clint (JOATMON) Chaplin
>
>
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81




From owner-ietf@ietf.org  Thu Aug 21 15:20: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 PAA24438
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 15:20:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19putc-00038p-1J
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 15:14:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19puqO-0002AW-Sv
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 15:11: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 PAA23585
	for <ietf@ietf.org>; Thu, 21 Aug 2003 15:11:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19puqN-00005O-00
	for ietf@ietf.org; Thu, 21 Aug 2003 15:11:35 -0400
Received: from dgesmtp01.wcom.com ([199.249.16.16])
	by ietf-mx with esmtp (Exim 4.12)
	id 19puqM-00004n-00
	for ietf@ietf.org; Thu, 21 Aug 2003 15:11:34 -0400
Received: from pmismtp02.wcomnet.com ([166.38.62.37])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HJZ00JIWH1KW5@firewall.wcom.com> for ietf@ietf.org; Thu,
 21 Aug 2003 19:05:44 +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 <0HJZ00901H1JQW@pmismtp02.wcomnet.com>; Thu,
 21 Aug 2003 19:05:44 +0000 (GMT)
Received: from xs578v3521.mci.com ([166.50.143.87])
 by pmismtp02.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HJZ0085KH1HOM@pmismtp02.wcomnet.com>; Thu,
 21 Aug 2003 19:05:43 +0000 (GMT)
Date: Thu, 21 Aug 2003 14:05:40 -0500
From: Alan Johnston <alan.johnston@mci.com>
Subject: Re: WG Review: Centralized Conferencing (xcon)
In-reply-to: <20030821111924.6a55fd5e.mrose@dbc.mtview.ca.us>
X-Sender: Alan.Johnston@pop.mcit.com
To: Marshall Rose <mrose@dbc.mtview.ca.us>, Rohan Mahy <rohan@cisco.com>
Cc: Henry Sinnreich <Henry.Sinnreich@mci.com>,
        "'vinton g. cerf'" <vinton.g.cerf@mci.com>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>, ietf@ietf.org,
        Robert Sparks <rsparks@dynamicsoft.com>
Message-id: <5.2.1.1.0.20030821135118.02bd8120@pop.mcit.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Content-type: text/plain; charset=us-ascii; format=flowed
References: <7BFAA4C6-D3E7-11D7-A5AF-0003938AF740@cisco.com>
 <0HJX00BO4708G3@pmismtp03.wcomnet.com>
 <7BFAA4C6-D3E7-11D7-A5AF-0003938AF740@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

At 11:19 AM 8/21/2003 -0700, Marshall Rose wrote:
> > As for Marshall's comments: there is certainly nothing nefarious about
> > having a large body of source work when trying to start a Working Group
> > (I cite XMPP as a recent example). What is important is for folks to
> > focus on the *charter text* and the desired output, rather than make
> > assumptions about the intent of those contributors.
>
>and, as has been repeatedly pointed out, the text in the proposed
>charter is rather poor. we now have four sets of people with entirely
>different interpretations (some from the SIP camp, some from the XMPP
>camp, plus the IETF chair).
>

Marshall,

I think the misunderstanding comes from your interpretation that when the 
charter text says "session setup using SIP" you think this means "session 
setup using SIP and IM and presence using SIMPLE".  You do understand the 
difference, no?

XCON requires a signaling protocol - that is part of the definition of the 
working group as *Centralized* conferencing.  A signaling protocol (not IM 
and presence protocol) is needed to establish, modify, tear down, and 
manipulate media sessions.  The nature of the streams will vary from RTP 
voice and video to IM text streams.  The IM text streams can be *any* 
protocol - SIMPLE, XMPP, or some proprietary IM protocol. XCON will work 
with them all.  Are you opposed to this?

If we don't use SIP as the example signaling protocol in our documents, 
should we use an ITU-T signaling protocol instead?  H.323, ISDN?  Of course 
not, we use an IETF proposed standard for session signaling, SIP.

Nothing in XCON is specific to SIP - I repeat nothing.  However, the 
documents will need to make reference to a signaling protocol, and SIP, as 
mentioned in the charter text, is it.  The likely output of XCON will be 
XML-based protocols that work at a higher level than any signaling 
protocol.  Are you perhaps opposed to the use of XML to control and create 
conferences?  This seems to be in line with the Jabber document which you 
have referenced a few times, which by the way, is exclusively limited to 
text messaging, which is a subset of the XCON problem space.

I propose wording changes to the charter which will make clear the 
distinction between SIP signaling and SIMPLE for IM - I believe this is the 
source of the technical disputes.

Thanks,
Alan Johnston
XCON BOF co-chair.


>
> > Marshall, if there is something specific that you don't like about the
> > charter as a generic conferencing working group, please propose
> > alternate rewording.
>
>that's easy:
>
>     1,$s/conferencing/SIP-based conferencing/g
>

>/mtr




From owner-ietf@ietf.org  Thu Aug 21 15:58: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 PAA26270
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 15:58:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pvQY-0006u5-6Z
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 15:48:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pvPy-0006qK-No
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 15:48: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 PAA25964
	for <ietf@ietf.org>; Thu, 21 Aug 2003 15:48:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pvPv-0000XU-00
	for ietf@ietf.org; Thu, 21 Aug 2003 15:48: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 19pvPu-0000XR-00
	for ietf@ietf.org; Thu, 21 Aug 2003 15:48: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 CC9847F5F;
	Thu, 21 Aug 2003 21:48:04 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'shogunx'" <shogunx@sleekfreak.ath.cx>
Cc: <ietf@ietf.org>
Subject: RE: AW: www.ietf.org.
Date: Thu, 21 Aug 2003 21:48:02 +0200
Organization: Unfix
Message-ID: <001a01c3681d$22d34fc0$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
In-Reply-To: <Pine.LNX.4.44.0308201708540.7255-100000@sleekfreak.ath.cx>
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

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

"shogunx" wrote:

> i get an unknown host with ping6 www.ietf.org

Which is quite logical as that host doesn't have any AAAA's.

If you want to reach the IETF site using only IPv6,
you could use http://www.ietf.org.sixxs.org
(see http://ipv6gate.sixxs.net for more about that)

Notez bien that www.ietf.org has two hosts:
$ host -t any www.ietf.org
www.ietf.org            A       132.151.6.21
www.ietf.org            A       4.17.168.6

And if you have a problem with the site it might
be very interresting to also include a traceroute
to the host you are having problems with.
Also a good debugger is to simply telnet to port
80 of the host or to do some tcpdumps.

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/

iQA/AwUBP0Uh6SmqKFIzPnwjEQK+kwCfb3dqhlZ72qYNE/1qow0nAkllCuIAnjb/
7rRBOpOfuUZ7MP3eXznUOHyj
=Fihu
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Thu Aug 21 16:30: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 QAA28348
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 16:30:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pw0N-0001VP-8k
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 16:25:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pvwe-00015d-NX
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 16:22: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 QAA27685
	for <ietf@ietf.org>; Thu, 21 Aug 2003 16:22:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pvwd-00013a-00
	for ietf@ietf.org; Thu, 21 Aug 2003 16:22:07 -0400
Received: from 96.136.33.65.cfl.rr.com ([65.33.136.96] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19pvwc-00013X-00
	for ietf@ietf.org; Thu, 21 Aug 2003 16:22:06 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19pbux-0003LM-00; Wed, 20 Aug 2003 18:59:03 -0400
Date: Wed, 20 Aug 2003 18:58:42 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Jeroen Massar <jeroen@unfix.org>
cc: ietf@ietf.org
Subject: RE: AW: www.ietf.org.
In-Reply-To: <001a01c3681d$22d34fc0$210d640a@unfix.org>
Message-ID: <Pine.LNX.4.44.0308201856510.7255-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 21 Aug 2003, Jeroen Massar wrote:

> "shogunx" wrote:
>
> > i get an unknown host with ping6 www.ietf.org
>
> Which is quite logical as that host doesn't have any AAAA's.

exactly.

>
> If you want to reach the IETF site using only IPv6,
> you could use http://www.ietf.org.sixxs.org
> (see http://ipv6gate.sixxs.net for more about that)
>

why is the IETF on a third level domain?


> Notez bien that www.ietf.org has two hosts:
> $ host -t any www.ietf.org
> www.ietf.org            A       132.151.6.21
> www.ietf.org            A       4.17.168.6
>
> And if you have a problem with the site it might
> be very interresting to also include a traceroute
> to the host you are having problems with.
> Also a good debugger is to simply telnet to port
> 80 of the host or to do some tcpdumps.
>
> Greets,
>  Jeroen
>
>
>
> ------------ Output from gpg ------------
> gpg: Signature made Thu Aug 21 15:47:53 2003 EDT using DSA key ID 333E7C23
> gpg: WARNING: signature digest conflict in message
> gpg: Can't check signature: general error
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81




From owner-ietf@ietf.org  Thu Aug 21 16:32: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 QAA28546
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 16:32:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pw49-0001lz-Ng
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 16:29:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pw48-0001ii-3I
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 16:29: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 QAA28302
	for <ietf@ietf.org>; Thu, 21 Aug 2003 16:29:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pw46-0001Fk-00
	for ietf@ietf.org; Thu, 21 Aug 2003 16:29:50 -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 19pw45-0001Fh-00
	for ietf@ietf.org; Thu, 21 Aug 2003 16:29:50 -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 2C24E7FAD;
	Thu, 21 Aug 2003 22:29:49 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'shogunx'" <shogunx@sleekfreak.ath.cx>
Cc: <ietf@ietf.org>
Subject: RE: AW: www.ietf.org.
Date: Thu, 21 Aug 2003 22:29:47 +0200
Organization: Unfix
Message-ID: <005201c36822$f79c53a0$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
In-Reply-To: <Pine.LNX.4.44.0308201856510.7255-100000@sleekfreak.ath.cx>
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

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

shogunx [mailto:shogunx@sleekfreak.ath.cx] wrote:

> On Thu, 21 Aug 2003, Jeroen Massar wrote:
> 
> > "shogunx" wrote:
> >
> > > i get an unknown host with ping6 www.ietf.org
> >
> > Which is quite logical as that host doesn't have any AAAA's.
> 
> exactly.

Then what is the problem, they didn't publish any
IPv6 addresses because there is no IPv6 access there.
Same goes for about 99% of the internet. If they
where publishing IPv6 records then they would be in err.

> > If you want to reach the IETF site using only IPv6,
> > you could use http://www.ietf.org.sixxs.org
> > (see http://ipv6gate.sixxs.net for more about that)
> >
> 
> why is the IETF on a third level domain?

Read the site, it's a rewriting proxy gimmick.

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/

iQA/AwUBP0UruSmqKFIzPnwjEQJsSQCfQVJY03btr74on+yj7Pr5HUZflxYAn2zB
lboyGcIhfNg2XccdfY+tzGhO
=1vqZ
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Thu Aug 21 18:11: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 SAA04194
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 18:11:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pxY6-0002cX-Sx
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 18:04:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pxXI-0002L1-AF
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 18:04: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 SAA03188
	for <ietf@ietf.org>; Thu, 21 Aug 2003 18:03:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pxX4-0002TW-00
	for ietf@ietf.org; Thu, 21 Aug 2003 18:03:50 -0400
Received: from pmesmtp01.wcom.com ([199.249.20.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pxX3-0002Sv-00
	for ietf@ietf.org; Thu, 21 Aug 2003 18:03:50 -0400
Received: from pmismtp05.wcomnet.com ([166.38.62.53])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HJZ00B6IP3QF4@firewall.wcom.com> for ietf@ietf.org; Thu,
 21 Aug 2003 21:59:51 +0000 (GMT)
Received: from pmismtp05.wcomnet.com by pmismtp05.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HJZ00K01P3O7O@pmismtp05.wcomnet.com>; Thu,
 21 Aug 2003 21:59:50 +0000 (GMT)
Received: from hsinnreich2 ([166.50.143.136])
 by pmismtp05.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HJZ00GXAP3BIG@pmismtp05.wcomnet.com>; Thu,
 21 Aug 2003 21:59:50 +0000 (GMT)
Date: Thu, 21 Aug 2003 16:59:35 -0500
From: Henry Sinnreich <Henry.Sinnreich@mci.com>
Subject: RE: WG Review: Centralized Conferencing (xcon)
In-reply-to: <20030821133537.7527d5c3.moore@cs.utk.edu>
To: "'Keith Moore'" <moore@cs.utk.edu>,
        "'Henry Sinnreich'" <Henry.Sinnreich@mci.com>
Cc: rohan@cisco.com, Henry.Sinnreich@mci.com, vinton.g.cerf@mci.com,
        mrose@dbc.mtview.ca.us, jon.peterson@neustar.biz, ietf@ietf.org,
        alan.johnston@mci.com, rsparks@dynamicsoft.com
Message-id: <0HJZ00GXQP3OIG@pmismtp05.wcomnet.com>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Office Outlook, Build 11.0.5329
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Thread-index: AcNoDcg/iwDsPwqbTYq+Rh862D8aiAAHTmlw
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith,

> is it really IETF's job to legislate full employment for conference
> service operators?

I find this very hard to understand. Are not service providers and network
managers the people supposed to bring these services into operation? Who
else has the operational credentials to define requirements for
conferencing?

If this was an emotional response, you need not reply.

Henry

> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Keith
> Moore
> Sent: Thursday, August 21, 2003 12:36 PM
> To: Henry Sinnreich
> Cc: moore@cs.utk.edu; rohan@cisco.com; Henry.Sinnreich@mci.com;
> vinton.g.cerf@mci.com; mrose@dbc.mtview.ca.us; jon.peterson@neustar.biz;
> ietf@ietf.org; alan.johnston@mci.com; rsparks@dynamicsoft.com
> Subject: Re: WG Review: Centralized Conferencing (xcon)
> 
> > Leaving the SIP-XMPP discussion aside (nobody will change their mind
> > anyway) a matter of concern is the 100% dominance of protocol experts
> > in this discussion and no real participation from conference service
> > operators and conference platform vendors. This raises several
> > flags...
> 
> once again, an attempt to coerce IETF into preserving the status quo in
> the market.
> 
> is it really IETF's job to legislate full employment for conference
> service operators?




From owner-ietf@ietf.org  Thu Aug 21 19:14: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 TAA08223
	for <ietf-web-archive@odin.ietf.org>; Thu, 21 Aug 2003 19:14:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19pyTB-0001PD-EB
	for ietf-list@asgard.ietf.org; Thu, 21 Aug 2003 19:03:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19pyRg-0001Jc-3d
	for ietf@asgard.ietf.org; Thu, 21 Aug 2003 19:02: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 TAA07608
	for <ietf@ietf.org>; Thu, 21 Aug 2003 19:02:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pyRe-0003H5-00
	for ietf@ietf.org; Thu, 21 Aug 2003 19:02:18 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19pyRd-0003H2-00
	for ietf@ietf.org; Thu, 21 Aug 2003 19:02:17 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 3369D13FF2; Thu, 21 Aug 2003 19:02:18 -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 23442-04; Thu, 21 Aug 2003 19:02:17 -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 5535914140; Thu, 21 Aug 2003 19:02:16 -0400 (EDT)
Date: Thu, 21 Aug 2003 19:00:34 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Henry Sinnreich <Henry.Sinnreich@mci.com>
Cc: moore@cs.utk.edu, Henry.Sinnreich@mci.com, rohan@cisco.com,
        vinton.g.cerf@mci.com, mrose@dbc.mtview.ca.us,
        jon.peterson@neustar.biz, ietf@ietf.org, alan.johnston@mci.com,
        rsparks@dynamicsoft.com
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030821190034.6a8ed354.moore@cs.utk.edu>
In-Reply-To: <0HJZ00GXQP3OIG@pmismtp05.wcomnet.com>
References: <20030821133537.7527d5c3.moore@cs.utk.edu>
	<0HJZ00GXQP3OIG@pmismtp05.wcomnet.com>
X-Mailer: Sylpheed version 0.9.3 (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

> Are not service providers and network
> managers the people supposed to bring these services into operation? 

I certainly don't share that assumption.  Then again, I don't share the
assumption that any central coordinating authority is needed to set up
conferencing services.



From owner-ietf@ietf.org  Fri Aug 22 10:35: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 KAA29462
	for <ietf-web-archive@odin.ietf.org>; Fri, 22 Aug 2003 10:35:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qCnZ-0005mI-PD
	for ietf-list@asgard.ietf.org; Fri, 22 Aug 2003 10:21:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19q3o6-0007dE-Tm
	for ietf@asgard.ietf.org; Fri, 22 Aug 2003 00:45: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 AAA20547
	for <ietf@ietf.org>; Fri, 22 Aug 2003 00:45:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19q3o4-0006V4-00
	for ietf@ietf.org; Fri, 22 Aug 2003 00:45:48 -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 19q3o3-0006UZ-00
	for ietf@ietf.org; Fri, 22 Aug 2003 00:45:47 -0400
Received: from cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 21 Aug 2003 21:53:52 -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 h7M4jF8s003862;
	Thu, 21 Aug 2003 21:45:16 -0700 (PDT)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AKQ88678;
	Thu, 21 Aug 2003 21:36:59 -0700 (PDT)
Date: Thu, 21 Aug 2003 21:48:15 -0700
Subject: Re: WG Review: Centralized Conferencing (xcon)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Henry Sinnreich <Henry.Sinnreich@mci.com>,
        "'vinton g. cerf'" <vinton.g.cerf@mci.com>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>, ietf@ietf.org,
        Alan Johnston <alan.johnston@mci.com>,
        Robert Sparks <rsparks@dynamicsoft.com>
To: Marshall Rose <mrose@dbc.mtview.ca.us>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <20030821111924.6a55fd5e.mrose@dbc.mtview.ca.us>
Message-Id: <D77D2715-D45B-11D7-85BF-0003938AF740@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

Marshall,

You got it exactly backwards.  There will not be a SIP-specific 
conferencing WG.  There was however a lot of interest in a 
non-SIP-specific conferencing WG.  If you don't like the current XCON 
charter text, then propose some alternate wording for a 
non-SIP-specific conferencing WG.  Otherwise forever hold your peace.

thanks,
-rohan



On Thursday, August 21, 2003, at 11:19 AM, Marshall Rose wrote:

>> As for Marshall's comments: there is certainly nothing nefarious about
>> having a large body of source work when trying to start a Working 
>> Group
>> (I cite XMPP as a recent example). What is important is for folks to
>> focus on the *charter text* and the desired output, rather than make
>> assumptions about the intent of those contributors.
>
> and, as has been repeatedly pointed out, the text in the proposed
> charter is rather poor. we now have four sets of people with entirely
> different interpretations (some from the SIP camp, some from the XMPP
> camp, plus the IETF chair).
>
>
>> Marshall, if there is something specific that you don't like about the
>> charter as a generic conferencing working group, please propose
>> alternate rewording.
>
> that's easy:
>
>     1,$s/conferencing/SIP-based conferencing/g
>
> /mtr






From owner-ietf@ietf.org  Fri Aug 22 11:14: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 LAA02151
	for <ietf-web-archive@odin.ietf.org>; Fri, 22 Aug 2003 11:14:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qDQF-0003OS-9V
	for ietf-list@asgard.ietf.org; Fri, 22 Aug 2003 11:01:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qDQ8-0003MF-DC
	for ietf@asgard.ietf.org; Fri, 22 Aug 2003 11:01:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01396
	for <ietf@ietf.org>; Fri, 22 Aug 2003 11:01:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qDQ7-0005at-00
	for ietf@ietf.org; Fri, 22 Aug 2003 11:01:43 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qDQ6-0005aq-00
	for ietf@ietf.org; Fri, 22 Aug 2003 11:01:42 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 815A914158; Fri, 22 Aug 2003 11:01: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 01118-15; Fri, 22 Aug 2003 11:01:41 -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 3239C14167; Fri, 22 Aug 2003 11:01:41 -0400 (EDT)
Date: Fri, 22 Aug 2003 11:01:40 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Rohan Mahy <rohan@cisco.com>
Cc: moore@cs.utk.edu, mrose@dbc.mtview.ca.us, Henry.Sinnreich@mci.com,
        vinton.g.cerf@mci.com, jon.peterson@neustar.biz, ietf@ietf.org,
        alan.johnston@mci.com, rsparks@dynamicsoft.com
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030822110140.3d64b283.moore@cs.utk.edu>
In-Reply-To: <D77D2715-D45B-11D7-85BF-0003938AF740@cisco.com>
References: <20030821111924.6a55fd5e.mrose@dbc.mtview.ca.us>
	<D77D2715-D45B-11D7-85BF-0003938AF740@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

> You got it exactly backwards.  There will not be a SIP-specific 
> conferencing WG.  There was however a lot of interest in a 
> non-SIP-specific conferencing WG. 

Well it seems like the charter authors (and IESG) have plenty of
feedback by now.  Now it's up to them to revise that charter to correct
the (mis?) impression that the group was intended to promote use of SIP
for this situation.

Until the charter is revised, is there anything left to discuss?

Keith



From owner-ietf@ietf.org  Fri Aug 22 11:47: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 LAA03715
	for <ietf-web-archive@odin.ietf.org>; Fri, 22 Aug 2003 11:47:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qDvC-0005K5-FI
	for ietf-list@asgard.ietf.org; Fri, 22 Aug 2003 11:33:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qDpV-00053m-3b
	for ietf@asgard.ietf.org; Fri, 22 Aug 2003 11:27: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 LAA02941
	for <ietf@ietf.org>; Fri, 22 Aug 2003 11:27:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qDpU-0005y9-00
	for ietf@ietf.org; Fri, 22 Aug 2003 11:27:56 -0400
Received: from tx2.citynet.net ([66.118.64.13] ident=[MZr+aAtWLrIefcboSE5w2cISjgzVR3CH])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qDpT-0005xt-00
	for ietf@ietf.org; Fri, 22 Aug 2003 11:27:55 -0400
Received: from a (dhcp-69-43-8-072.park.dialup.citynet.net [69.43.8.72])
	by tx2.citynet.net (8.12.9/8.12.6=Outbound) with SMTP id h7MBV6qb019077
	for <ietf@ietf.org>; Fri, 22 Aug 2003 07:31:12 -0400
Message-ID: <000501c368a1$1f99c3a0$48082b45@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: <ietf@ietf.org>
Subject: ietf.org
Date: Fri, 22 Aug 2003 07:32:40 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The site works fine for me too. I see no test page.





From owner-ietf@ietf.org  Fri Aug 22 12:39: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 MAA06146
	for <ietf-web-archive@odin.ietf.org>; Fri, 22 Aug 2003 12:39:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qEeE-0008Iy-1k
	for ietf-list@asgard.ietf.org; Fri, 22 Aug 2003 12:20:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qEdM-0008EB-FX
	for ietf@asgard.ietf.org; Fri, 22 Aug 2003 12:19: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 MAA05224
	for <ietf@ietf.org>; Fri, 22 Aug 2003 12:19:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qEdL-0006YU-00
	for ietf@ietf.org; Fri, 22 Aug 2003 12:19:27 -0400
Received: from dgesmtp02.wcom.com ([199.249.16.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qEdK-0006YL-00
	for ietf@ietf.org; Fri, 22 Aug 2003 12:19:26 -0400
Received: from dgismtp04.wcomnet.com ([166.38.58.144])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HK10096D3V8WK@firewall.wcom.com> for ietf@ietf.org; Fri,
 22 Aug 2003 16:16:20 +0000 (GMT)
Received: from dgismtp04.wcomnet.com by dgismtp04.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HK1005013TM68@dgismtp04.wcomnet.com>; Fri,
 22 Aug 2003 16:16:20 +0000 (GMT)
Received: from hsinnreich2 ([166.35.136.95])
 by dgismtp04.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HK10050M3UFHE@dgismtp04.wcomnet.com>; Fri,
 22 Aug 2003 16:15:52 +0000 (GMT)
Date: Fri, 22 Aug 2003 11:15:52 -0500
From: Henry Sinnreich <Henry.Sinnreich@mci.com>
Subject: RE: WG Review: Centralized Conferencing (xcon)
In-reply-to: <20030821190034.6a8ed354.moore@cs.utk.edu>
To: "'Keith Moore'" <moore@cs.utk.edu>,
        "'Henry Sinnreich'" <Henry.Sinnreich@mci.com>
Cc: Henry.Sinnreich@mci.com, rohan@cisco.com, vinton.g.cerf@mci.com,
        mrose@dbc.mtview.ca.us, jon.peterson@neustar.biz, ietf@ietf.org,
        alan.johnston@mci.com, rsparks@dynamicsoft.com
Message-id: <0HK10050P3UFHE@dgismtp04.wcomnet.com>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Office Outlook, Build 11.0.5329
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Thread-index: AcNoOEYYd1qat3tRTKGQ/snv7hgpggAgGz9A
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I certainly don't share that assumption.  Then again, I don't share the
> assumption that any central coordinating authority is needed to set up
> conferencing services.

This is an interesting point. The XCON WG is about _Centralized_
conferencing platforms. Who does operate such centralized systems?

Thanks, Henry

> -----Original Message-----
> From: Keith Moore [mailto:moore@cs.utk.edu]
> Sent: Thursday, August 21, 2003 6:01 PM
> To: Henry Sinnreich
> Cc: moore@cs.utk.edu; Henry.Sinnreich@mci.com; rohan@cisco.com;
> vinton.g.cerf@mci.com; mrose@dbc.mtview.ca.us; jon.peterson@neustar.biz;
> ietf@ietf.org; alan.johnston@mci.com; rsparks@dynamicsoft.com
> Subject: Re: WG Review: Centralized Conferencing (xcon)
> 
> > Are not service providers and network
> > managers the people supposed to bring these services into operation?
> 
> I certainly don't share that assumption.  Then again, I don't share the
> assumption that any central coordinating authority is needed to set up
> conferencing services.




From owner-ietf@ietf.org  Fri Aug 22 13: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 NAA07536
	for <ietf-web-archive@odin.ietf.org>; Fri, 22 Aug 2003 13:10:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qFKX-0002Da-PM
	for ietf-list@asgard.ietf.org; Fri, 22 Aug 2003 13:04:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qFIH-000235-QI
	for ietf@asgard.ietf.org; Fri, 22 Aug 2003 13:01:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07224
	for <ietf@ietf.org>; Fri, 22 Aug 2003 13:01:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qFIG-0006ye-00
	for ietf@ietf.org; Fri, 22 Aug 2003 13:01:44 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19qFIF-0006yO-00
	for ietf@ietf.org; Fri, 22 Aug 2003 13:01:44 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h7MGnEn03901
	for <ietf@ietf.org>; Fri, 22 Aug 2003 09:49:14 -0700
Date: Fri, 22 Aug 2003 09:49:14 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: RE: WG Review: Centralized Conferencing (xcon)
In-Reply-To: <0HK10050P3UFHE@dgismtp04.wcomnet.com>
Message-ID: <Pine.LNX.4.33.0308220940171.309-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Fri, 22 Aug 2003, Henry Sinnreich wrote:

> > I certainly don't share that assumption.  Then again, I don't share the
> > assumption that any central coordinating authority is needed to set up
> > conferencing services.
>
> This is an interesting point. The XCON WG is about _Centralized_
> conferencing platforms. Who does operate such centralized systems?

It seems to me that the issue isn't whether a conferencing service could
be setup without a central authority but rather if when there is a need
for central control, what are the protocols used to coordinate with the
controlling authority. I believe there is a need for both forms of
organization:
  a.  Distributed control
  b.  Centralized control

WebEx and Placeware (now owned by MS) are examples of centralized systems
which currently exist.

Dave Morris




From owner-ietf@ietf.org  Fri Aug 22 14:17: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 OAA11429
	for <ietf-web-archive@odin.ietf.org>; Fri, 22 Aug 2003 14:17:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qGKW-0007iR-1o
	for ietf-list@asgard.ietf.org; Fri, 22 Aug 2003 14:08:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qGEo-0006vJ-G0
	for ietf@asgard.ietf.org; Fri, 22 Aug 2003 14:02: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 OAA10713
	for <ietf@ietf.org>; Fri, 22 Aug 2003 14:02:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qGEn-0007iw-00
	for ietf@ietf.org; Fri, 22 Aug 2003 14:02:13 -0400
Received: from adsl-64-168-10-254.dsl.scrm01.pacbell.net ([64.168.10.254] helo=drakken.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19qGEm-0007io-00
	for ietf@ietf.org; Fri, 22 Aug 2003 14:02:12 -0400
Received: from drakken.dbc.mtview.ca.us (localhost [127.0.0.1])
	by drakken.dbc.mtview.ca.us (8.12.9/8.12.9) with SMTP id h7MI24WY000685;
	Fri, 22 Aug 2003 11:02:04 -0700 (PDT)
Date: Fri, 22 Aug 2003 11:02:04 -0700
From: Marshall Rose <mrose@dbc.mtview.ca.us>
To: Adam Roach <adam@dynamicsoft.com>
Cc: Adam Roach <adam@dynamicsoft.com>, "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-Id: <20030822110204.1af79b63.mrose@dbc.mtview.ca.us>
In-Reply-To: <9BF66EBF6BEFD942915B4D4D45C051F3E8637C@dyn-tx-exch-001.dynamicsoft.com>
References: <9BF66EBF6BEFD942915B4D4D45C051F3E8637C@dyn-tx-exch-001.dynamicsoft.com>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> An understandable interpretation of my words (especially
> taken out of the context of the larger point I was trying
> to make), but not what I intended.
> 
> That paragraph was intended to convey what I perceived the
> overall feel of the participants in the BOF to be. Any
> decisions, of course, will be taken to the working group
> for consensus.

good. sorry for the confusion!

/mtr



From owner-ietf@ietf.org  Fri Aug 22 16:09: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 QAA17041
	for <ietf-web-archive@odin.ietf.org>; Fri, 22 Aug 2003 16:09:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qHyn-0007NH-GB
	for ietf-list@asgard.ietf.org; Fri, 22 Aug 2003 15:53:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qHw3-0007FC-AY
	for ietf@asgard.ietf.org; Fri, 22 Aug 2003 15: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 PAA16385
	for <ietf@ietf.org>; Fri, 22 Aug 2003 15:50:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qHw1-00014r-00
	for ietf@ietf.org; Fri, 22 Aug 2003 15:50:57 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qHw0-00014X-00
	for ietf@ietf.org; Fri, 22 Aug 2003 15:50:56 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 5387161BB0; Fri, 22 Aug 2003 21:50:26 +0200 (CEST)
Date: Fri, 22 Aug 2003 12:50:25 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Henry Sinnreich <Henry.Sinnreich@mci.com>
Cc: ietf@ietf.org
Subject: RE: WG Review: Centralized Conferencing (xcon)
Message-ID: <1007082788.1061556625@[192.168.1.4]>
In-Reply-To: <0HK10050P3UFHE@dgismtp04.wcomnet.com>
References:  <0HK10050P3UFHE@dgismtp04.wcomnet.com>
X-Mailer: Mulberry/3.0.2 (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 22. august 2003 11:15 -0500 Henry Sinnreich <Henry.Sinnreich@mci.com> 
wrote:

>> I certainly don't share that assumption.  Then again, I don't share the
>> assumption that any central coordinating authority is needed to set up
>> conferencing services.
>
> This is an interesting point. The XCON WG is about _Centralized_
> conferencing platforms. Who does operate such centralized systems?

to use a specific example....

in the case of something like the IESG teleconference, I would expect the 
IETF secretariat to be in control of the conference, and that all 
participants are able to securely assert identities that the secretariat 
can verify.

The protocols should make no assumptions on whether the programs executing 
the conference authority run on machines operated by the secretariat, AT&T 
or a service provider in rural India, and should make no assumptions on 
whether the trust is rooted in Verisign or psg.com, or is brokered through 
a mechanism that doesn't need a single root for its trust mechanism.

If "centralized conference control" doesn't mean that anyone with the 
required resources can be a center, I think we're on a very wrong path.

My opinion, of course.

                            Harald





From owner-ietf@ietf.org  Fri Aug 22 16:44: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 QAA18884
	for <ietf-web-archive@odin.ietf.org>; Fri, 22 Aug 2003 16:44:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qIhJ-0001kh-9R
	for ietf-list@asgard.ietf.org; Fri, 22 Aug 2003 16:39:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qIdi-0001aI-Ma
	for ietf@asgard.ietf.org; Fri, 22 Aug 2003 16:36: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 QAA18493
	for <ietf@ietf.org>; Fri, 22 Aug 2003 16:35:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qIdd-0001be-00
	for ietf@ietf.org; Fri, 22 Aug 2003 16:36:01 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qIdc-0001ak-00
	for ietf@ietf.org; Fri, 22 Aug 2003 16:36:00 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h7MKdxa02984;
	Fri, 22 Aug 2003 13:39:59 -0700
Date: Fri, 22 Aug 2003 13:34:25 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/11) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <627986323.20030822133425@brandenburg.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: ietf@ietf.org
Subject: Re: WG Review: Centralized Conferencing (xcon)
In-Reply-To: <1007082788.1061556625@[192\.168\.1\.4]>
References: <0HK10050P3UFHE@dgismtp04.wcomnet.com>
 <1007082788.1061556625@[192.168.1.4]>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald,


HTA> and should make no assumptions on
HTA> whether the trust is rooted in Verisign or psg.com, or is brokered through
HTA> a mechanism that doesn't need a single root for its trust mechanism.

HTA> If "centralized conference control" doesn't mean that anyone with the
HTA> required resources can be a center, I think we're on a very wrong path.


The style of protocol needed for a single, centralized control
mechanism, versus a distributed and cooperative control mechanism,
typically is quite different.

The obvious example would be centralized dns control -- as we now have
for each node in the tree -- versus efforts to create multiple
authorities for any given node, such as the root.

Did you have in mind a way to reconcile this?


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




From owner-ietf@ietf.org  Fri Aug 22 17:09: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 RAA20597
	for <ietf-web-archive@odin.ietf.org>; Fri, 22 Aug 2003 17:09:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qJ4X-0003iR-99
	for ietf-list@asgard.ietf.org; Fri, 22 Aug 2003 17:03:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qJ3k-0003ct-Ua
	for ietf@asgard.ietf.org; Fri, 22 Aug 2003 17: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 RAA20356
	for <ietf@ietf.org>; Fri, 22 Aug 2003 17:02:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qJ3j-00021d-00
	for ietf@ietf.org; Fri, 22 Aug 2003 17:02:59 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19qJ3i-00021Y-00
	for ietf@ietf.org; Fri, 22 Aug 2003 17:02:58 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h7MKoVn04490
	for <ietf@ietf.org>; Fri, 22 Aug 2003 13:50:32 -0700
Date: Fri, 22 Aug 2003 13:50:31 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: Re: WG Review: Centralized Conferencing (xcon)
In-Reply-To: <627986323.20030822133425@brandenburg.com>
Message-ID: <Pine.LNX.4.33.0308221345560.309-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Fri, 22 Aug 2003, Dave Crocker wrote:

> Harald,
>
>
> HTA> and should make no assumptions on
> HTA> whether the trust is rooted in Verisign or psg.com, or is brokered through
> HTA> a mechanism that doesn't need a single root for its trust mechanism.
>
> HTA> If "centralized conference control" doesn't mean that anyone with the
> HTA> required resources can be a center, I think we're on a very wrong path.
>
>
> The style of protocol needed for a single, centralized control
> mechanism, versus a distributed and cooperative control mechanism,
> typically is quite different.
>
> The obvious example would be centralized dns control -- as we now have
> for each node in the tree -- versus efforts to create multiple
> authorities for any given node, such as the root.
>
> Did you have in mind a way to reconcile this?

Different protocols ... Harald's only stipulation is that the protocol
shouldn't prevent anyone from creating a centeralized conference control
facility.

The distinction I see between centralized control and distributed control
is with centralized control, I must have a way to establish trust with the
control facility which I must trust to authenticate all other participants
in a similar fashion.  With a distributed mechanism, I must establish a
trust relationship directly with each participant.




From owner-ietf@ietf.org  Fri Aug 22 17:30: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 RAA21655
	for <ietf-web-archive@odin.ietf.org>; Fri, 22 Aug 2003 17:30:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qJQ0-0005mB-Jo
	for ietf-list@asgard.ietf.org; Fri, 22 Aug 2003 17:26:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qJOQ-0005dX-6I
	for ietf@asgard.ietf.org; Fri, 22 Aug 2003 17:24: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 RAA21404
	for <ietf@ietf.org>; Fri, 22 Aug 2003 17:24:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qJOO-0002Fm-00
	for ietf@ietf.org; Fri, 22 Aug 2003 17:24:20 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qJOO-0002FQ-00
	for ietf@ietf.org; Fri, 22 Aug 2003 17:24:20 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id F28EF61C19; Fri, 22 Aug 2003 23:23:48 +0200 (CEST)
Date: Fri, 22 Aug 2003 14:22:14 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: ietf@ietf.org
Subject: Re: WG Review: Centralized Conferencing (xcon)
Message-ID: <1012591790.1061562134@localhost>
In-Reply-To: <627986323.20030822133425@brandenburg.com>
References: <0HK10050P3UFHE@dgismtp04.wcomnet.com>
 <1007082788.1061556625@[192.168.1.4]>
 <627986323.20030822133425@brandenburg.com>
X-Mailer: Mulberry/3.0.2 (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 22. august 2003 13:34 -0700 Dave Crocker <dhc@dcrocker.net> wrote:

> Harald,
>
>
> HTA> and should make no assumptions on
> HTA> whether the trust is rooted in Verisign or psg.com, or is brokered
> through HTA> a mechanism that doesn't need a single root for its trust
> mechanism.
>
> HTA> If "centralized conference control" doesn't mean that anyone with the
> HTA> required resources can be a center, I think we're on a very wrong
> path.
>
>
> The style of protocol needed for a single, centralized control
> mechanism, versus a distributed and cooperative control mechanism,
> typically is quite different.
>
> The obvious example would be centralized dns control -- as we now have
> for each node in the tree -- versus efforts to create multiple
> authorities for any given node, such as the root.
>
> Did you have in mind a way to reconcile this?

no, I was responding to Henry Sinnreich's comment on "who will operate the 
centralized functions" only. I thought it was obvious from xcon's charter 
that "multiple authority for a single conference" conference management is 
out of scope, and I'm still talking about xcon.

                        Harald





From owner-ietf@ietf.org  Sat Aug 23 13:09: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 NAA17567
	for <ietf-web-archive@odin.ietf.org>; Sat, 23 Aug 2003 13:09:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qbci-0001ej-NA
	for ietf-list@asgard.ietf.org; Sat, 23 Aug 2003 12:52:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qbbV-0001c3-Lf
	for ietf@asgard.ietf.org; Sat, 23 Aug 2003 12:51: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 MAA16816
	for <ietf@ietf.org>; Sat, 23 Aug 2003 12:51:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qbbU-00040c-00
	for ietf@ietf.org; Sat, 23 Aug 2003 12:51:04 -0400
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qbbU-00040Z-00
	for ietf@ietf.org; Sat, 23 Aug 2003 12:51:04 -0400
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h7NGp3024909;
	Sat, 23 Aug 2003 09:51:03 -0700
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Sat, 23 Aug 2003 09:51:02 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: ietf@ietf.org
Subject: Re: Internal WG Review: Recharter of ADSL MIB (adslmib)
In-Reply-To: <200308191926.PAA03106@ietf.org>
Message-ID: <Pine.LNX.4.10.10308230923230.16882-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Regarding the following:

On Tue, 19 Aug 2003, IESG-Secretary wrote:
> A new charter for the ADSL MIB (adslmib)
> in the Operations and Management Area
> of the IETF is being considered.
> The draft charter is provided below for your review
> and comment.
> 
> The IETF Secretariat
> 
> 
> ADSL MIB (adslmib)
> ---------------------
> + lines with a + sign are new text
> - lines with a - sign will be removed from charter
> 
>  Description of Working Group:
[ ... ]
> - In addition, the group will continue to work on the promotion of the
> - ADSLMIB, the ADSL Extension MIB, and the HDSL2/SHDSL MIB through the
> - IETF standards process.

I'm curious as to why this is being removed.  The WG charter currently
lists three RFCs, all at Proposed standard:

Definitions of Managed Objects for the ADSL Lines (RFC 2662,
August 1999)

Definitions of Managed Objects for HDSL2 and SHDSL Lines (RFC 3276,
May 2002)

Definitions of Extension Managed Objects for Asymmetric Digital
Subscriber Lines (RFC 3440, December 2002)

Does it mean that the WG will no longer attempt to advance these
specifications to Draft Standard?

Mike Heard




From owner-ietf@ietf.org  Sat Aug 23 13:50: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 NAA19117
	for <ietf-web-archive@odin.ietf.org>; Sat, 23 Aug 2003 13:50:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qcSK-00045O-Tf
	for ietf-list@asgard.ietf.org; Sat, 23 Aug 2003 13:45:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qcQV-00040f-TI
	for ietf@asgard.ietf.org; Sat, 23 Aug 2003 13:43: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 NAA18872
	for <ietf@ietf.org>; Sat, 23 Aug 2003 13:43:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qcQS-0004Uv-00
	for ietf@ietf.org; Sat, 23 Aug 2003 13:43:44 -0400
Received: from tomts24.bellnexxia.net ([209.226.175.187] helo=tomts24-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19qcQS-0004Us-00
	for ietf@ietf.org; Sat, 23 Aug 2003 13:43:44 -0400
Received: from yahoo.com ([65.93.188.48]) by tomts24-srv.bellnexxia.net
          (InterMail vM.5.01.06.04 201-253-122-130-104-20030726) with ESMTP
          id <20030823174338.XVCW29033.tomts24-srv.bellnexxia.net@yahoo.com>;
          Sat, 23 Aug 2003 13:43:38 -0400
Date: Sat, 23 Aug 2003 13:43:36 -0400
Subject: Re: Pretty clear ... SIP
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: dank@hq.lindsayelec.com (Dan Kolis)
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <20030821183528722.AAA161@hq.lindsayelec.com@rflooker1>
Message-Id: <52F15CC4-D591-11D7-A96B-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

The difference between internet telephony and voice chat.

This is fairly critical actually. It doesn't matter if you're talking 
about H323 or SIP although obviously there is a bias in each one 
towards one or the other. The commonly used VoIP name does NOT do 
enough to differentiate, we need to be talking about IP telephony and 
voice chat as two DIFFERENT beasts since they have substantially 
different expectations of availability!

People expect a telephony system to be available even if the power goes 
down, virtually all the time, how many nines of availability? Lots. 
More than the internet actually. In fact, they would basically expect 
IPtel systems to keep working even if the internet goes down. They 
reach for the IP phone, a physical object on their desk, most likely. 
This is not really "internet" stuff this is the adaptation of internet 
protocol to telephony fields where internet availability doesn't cut it.

On the other hand, voice chat is also VoIP but the expectation are 
completely different. People basically expect it will operate through 
the computer. It will only work if the internet connection is working. 
Power failure ? goodbye. This is not a telephone replacement. It's a 
supplement. It's going to be dirt cheap and have all the other goodness 
that typically characterizes internet technology.

simon

On Thursday, August 21, 2003, at 02:35 PM, Dan Kolis wrote:

> Since SIP is IETF not ITU its only reasonable to have internet 
> believers
> lean towards it.
>
> H.323 ? Ahhh no thanks.
>
> No serious look at these can even consider H.323 etc and its 
> derivitives as
> useful in the general case. The only reason they were used is the 
> absence of
> a better alternative.
>
> Try to hook your Sony Playstation up through H.323
>
> When would that move through committee? Spring of 2010 ??
>
> Oh. Another reason for IETF to believe in it is that its basically a 
> free
> comm technology. H.323 wants to drag in the old timers and their costs
> structures... dependance of geography, etc so there is a credible 
> reason by
> most criterea.
>
> Regs,
> Dan
>
>

--
      anti-spam: do not post this address publicly
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Sat Aug 23 20:57: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 UAA03718
	for <ietf-web-archive@odin.ietf.org>; Sat, 23 Aug 2003 20:57:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qj2g-0004vL-Fi
	for ietf-list@asgard.ietf.org; Sat, 23 Aug 2003 20:47:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qj1v-0004t2-Aq
	for ietf@asgard.ietf.org; Sat, 23 Aug 2003 20:46: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 UAA03347
	for <ietf@ietf.org>; Sat, 23 Aug 2003 20:46:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qj1t-0007gU-00
	for ietf@ietf.org; Sat, 23 Aug 2003 20:46:49 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19qj1t-0007gG-00
	for ietf@ietf.org; Sat, 23 Aug 2003 20:46:49 -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 UAA19118;
	Sat, 23 Aug 2003 20:40:08 -0400
Date: Sat, 23 Aug 2003 20:40:09 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: Dan Kolis <dank@hq.lindsayelec.com>
cc: ietf@ietf.org
Subject: Re: Pretty clear ... SIP
In-Reply-To: <20030821183528722.AAA161@hq.lindsayelec.com@rflooker1>
Message-ID: <Pine.LNX.4.44.0308232009200.18318-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Err, I think there are some things missing:

1) H.323 closely matches PSTN protocols and capabilities. Its
interoperability with ISDN and SS7 are far more natural.

2) H.323 is more efficiently coded using ASN.1.  One might not think that
this matters, but in fact it matters a great deal in large volumes.
H.323 is PER encoded, which frequently results in about 50% compression
over uncompressed data. Smaller packets have lower latency, and take less
time to transmit. Advances in processor speed over IO speed has made
compression almost a zero cost feature.

3) Standardization is _way_ better with H.323.  The IETF process relies on
the standard-writers to do the implementations, which we then hope are
well documented in the standard. They aren't always so well documented. So
long as the group of implementers is small, this isn't a problem. But in
large groups, it doesn't work very well. Such an iterative process of
implementation/documentation/implementation is slower than complete
specification -> implementation except when the group of implementers and
documenters are small, so that undocumented or vague parts can be passed
informally amoung the implementers.  For example, consider that the DNS
groups have been struggling for years with ambiguities in RFC 1035.
Things still aren't fully specified, and there is a great deal of
difference and incompatibility between Bind 9 implementation and other DNS
implementations.  It doesn't seem that these ambiguities will be resolved
soon.

4) H.323 has free infrastructure: There are free ASN.1 compilers (I'm even
am about to release one). There are free implementation of H.323 protocol
stacks, and free h.323 software.

5) H.323 moved through 4 major well defined enhancements far faster than
SIP.

6) SIP started out saying that it could do the job simpler and easier than
H.323. So far, this hasn't proven to be the case. SIP is now just as
complicated as H.323. The reason for the complication is driven mostly by
the PSTN, and the features that you find on phones and PBX's. These
features haven't changed, so the complexity is still the same.

However, this is not to say the SIP effort was wasted. Not in the least.
There has been a tremendous amount of productive feedback and cross
pollenation between the two groups. There is nothing like competiton to
make one think pragmatically.  SIP significantly influenced the attention
to performance in H.323 after version 1, and resulted in features like
FastStart and other procedures to reduce the startup traffic. There are
probably other examples of productive feedback between the two.

H.323 and ASN.1 eventually surpass a text based protocol because they are
better specified and can be implemented by compiler, securely, and
compatibily.  A compiler handles more of the compatibility between
different implementations. Text based protocols are by definition vague.
Handwritten parsers offer more opportunities for bugs, incompatibilities,
and security problems.  ASN.1 has other advantages that I won't go into
here.

The most pointed past disadvantage of ASN.1 was that it was complicated
and expensive, because there were no free compilers, and decoders were
also hard to come by. That has all changed. Etherreal and other free
packet analyzers have H.323 modules, and can now easily incorporate other
ASN.1 based protocols.  Recent enhancements to ASN.1 allows for
specification of encoder rules so protocols like IP or Q.931 can be
specified and implemented by compiler. There is really no reason for the
IETF not to consider using ASN.1 for protocol specification, and in fact,
it does in the GSSAPI.

		--Dean

On Thu, 21 Aug 2003, Dan Kolis wrote:

> Since SIP is IETF not ITU its only reasonable to have internet believers
> lean towards it.
>
> H.323 ? Ahhh no thanks.
>
> No serious look at these can even consider H.323 etc and its derivitives as
> useful in the general case. The only reason they were used is the absence of
> a better alternative.
>
> Try to hook your Sony Playstation up through H.323
>
> When would that move through committee? Spring of 2010 ??
>
> Oh. Another reason for IETF to believe in it is that its basically a free
> comm technology. H.323 wants to drag in the old timers and their costs
> structures... dependance of geography, etc so there is a credible reason by
> most criterea.
>
> Regs,
> Dan
>
>
>




From owner-ietf@ietf.org  Sat Aug 23 22:12: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 WAA05800
	for <ietf-web-archive@odin.ietf.org>; Sat, 23 Aug 2003 22:12:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qkFE-0008J8-7p
	for ietf-list@asgard.ietf.org; Sat, 23 Aug 2003 22:04:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qkEi-0008GS-7M
	for ietf@asgard.ietf.org; Sat, 23 Aug 2003 22:04: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 WAA05603
	for <ietf@ietf.org>; Sat, 23 Aug 2003 22:04:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qkEg-0000hd-00
	for ietf@ietf.org; Sat, 23 Aug 2003 22:04:06 -0400
Received: from p2.cavebear.com ([199.184.128.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qkEf-0000hS-00
	for ietf@ietf.org; Sat, 23 Aug 2003 22:04:05 -0400
Received: from npax.cavebear.com (npax.cavebear.com [192.203.17.71])
	by p2.cavebear.com (8.12.8/8.12.8) with SMTP id h7O23U5F024130
	for <ietf@ietf.org>; Sat, 23 Aug 2003 19:03:30 -0700
Received: from npax.cavebear.com (localhost.localdomain [127.0.0.1])
	by npax.cavebear.com (8.12.8/8.12.8) with ESMTP id h7O23UBF014531
	for <ietf@ietf.org>; Sat, 23 Aug 2003 19:03:30 -0700
Received: by npax.cavebear.com (tmda-sendmail, from uid 2000);
	Sat, 23 Aug 2003 19:03:30 -0700 (PDT)
Date: Sat, 23 Aug 2003 19:03:30 -0700 (PDT)
Reply-To: Karl Auerbach <karl@cavebear.com>
To: IETF <ietf@ietf.org>
Subject: Re: Pretty clear ... SIP
In-Reply-To: <Pine.LNX.4.44.0308232009200.18318-100000@vista.av8.net>
Message-ID: <Pine.LNX.4.44.0308231831280.13826-100000@npax.cavebear.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
From: Karl Auerbach <karl@cavebear.com>
X-Delivery-Agent: TMDA/0.82 (Needles)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 23 Aug 2003, Dean Anderson wrote:

> H.323 and ASN.1 eventually surpass ...

Ummm, based on my own direct experience with ASN.1 since the mid 1980's
(X.400, SNMP, CMIP...), I disagree.

It has been my experience that ASN.1, no matter which encoding rules are
used, has proven to be a failure and lingering interoperability and
denial-of-service disaster.

For example, the flaws in ASN.1 parsers in SNMP engines have proven to be
a decades+ old vulnerability for the net.

We'd be much better off with XML, Scheme expressions, or Python pickles
than with ASN.1 both for expressing data structures in documents and for 
encoding data structures into binary for carriage in packets.

If one wants compression, then it is better to apply it to the entire
packet, or the byte stream - the results will almost always be much, much
better then the item by item packing done by ASN.1's encoding rules.  (I
was always amused that using BER, ASN.1 integers were frequently bigger
than simply 32-bit binary, particularly when carrying unsigned numbers,
which are rather common in networking protocols.)

(In addition, with the 60 octet minimum packet size imposed by many data
links, compression of typically small packets - such as those containing
SDP information - often doesn't result in much of a gain anyway.)

As far as SIP vs H.323 goes - apart from the market fact that it is
getting increasingly more difficult to find new products that support
H.323 - I find H.323 to be qualitiatively worse, as measured in units of
elegance, than SIP.  I too am sorry that SIP has gotten more complex as it
has experienced actual implementation pressures.  However, H.323 started
out as a mish mosh - a large dollup of ISDN, a dab of SDP, a chunk of
RTP/RTCP - and it remains a mish mosh.

		--karl--













From owner-ietf@ietf.org  Sun Aug 24 00:40: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 AAA09275
	for <ietf-web-archive@odin.ietf.org>; Sun, 24 Aug 2003 00:40:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qmYO-0006Gh-Rw
	for ietf-list@asgard.ietf.org; Sun, 24 Aug 2003 00:32:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qmXE-0006BV-VI
	for ietf@asgard.ietf.org; Sun, 24 Aug 2003 00:31:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09073
	for <ietf@ietf.org>; Sun, 24 Aug 2003 00:31:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qmXC-0001rR-00
	for ietf@ietf.org; Sun, 24 Aug 2003 00:31:22 -0400
Received: from snipe.mail.pas.earthlink.net ([207.217.120.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qmXC-0001rO-00
	for ietf@ietf.org; Sun, 24 Aug 2003 00:31:22 -0400
Received: from h-68-164-73-43.snvacaid.covad.net ([68.164.73.43] helo=oemcomputer)
	by snipe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19qmXC-0007FI-00
	for ietf@ietf.org; Sat, 23 Aug 2003 21:31:22 -0700
Message-ID: <002201c369f8$90f83f60$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "IETF" <ietf@ietf.org>
References: <Pine.LNX.4.44.0308231831280.13826-100000@npax.cavebear.com>
Subject: Re: Pretty clear ... SIP
Date: Sat, 23 Aug 2003 21:31:19 -0700
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

Hi -

> From: "Karl Auerbach" <karl@cavebear.com>
> To: "IETF" <ietf@ietf.org>
> Sent: Saturday, August 23, 2003 7:03 PM
> Subject: Re: Pretty clear ... SIP
>

> On Sat, 23 Aug 2003, Dean Anderson wrote:
>
> > H.323 and ASN.1 eventually surpass ...
>
> Ummm, based on my own direct experience with ASN.1 since the mid 1980's
> (X.400, SNMP, CMIP...), I disagree.
>
> It has been my experience that ASN.1, no matter which encoding rules are
> used, has proven to be a failure and lingering interoperability and
> denial-of-service disaster.
>
> For example, the flaws in ASN.1 parsers in SNMP engines have proven to be
> a decades+ old vulnerability for the net.
...

In fairness,
    1) SNMP's (ab)use of ASN.1 pretty much precludes the use of ASN.1 compiler
         technology.  All the implementations I know of used hand-coded encoders and
         decoders.  The vulnerabilities aren't a result of ASN.1, but rather of trusting
         humans to do a compiler's job.
    2) Dean was specifically writing about PER, which can be *much* more compact
        than BER would ever hope to be.  PER can potentially result in a more compact
        encoding than applying compression to a single packet.  Look at the spec to see
        why.

Randy





From owner-ietf@ietf.org  Sun Aug 24 03:03: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 DAA25134
	for <ietf-web-archive@odin.ietf.org>; Sun, 24 Aug 2003 03:03:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19qomm-0001nV-0B
	for ietf-list@asgard.ietf.org; Sun, 24 Aug 2003 02:55:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qolB-0001is-5D
	for ietf@asgard.ietf.org; Sun, 24 Aug 2003 02:53: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 CAA24853
	for <ietf@ietf.org>; Sun, 24 Aug 2003 02:53:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qol9-0002wT-00
	for ietf@ietf.org; Sun, 24 Aug 2003 02:53:55 -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 19qol8-0002w3-00
	for ietf@ietf.org; Sun, 24 Aug 2003 02:53:54 -0400
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id C246918DB
	for <ietf@ietf.org>; Sun, 24 Aug 2003 02:53:24 -0400 (EDT)
Date: Sun, 24 Aug 2003 02:53:24 -0400
From: Rob Austein <sra+ietf@hactrn.net>
To: ietf@ietf.org
Subject: Re: Pretty clear ... SIP
In-Reply-To: <002201c369f8$90f83f60$7f1afea9@oemcomputer>
References: <Pine.LNX.4.44.0308231831280.13826-100000@npax.cavebear.com>
	<002201c369f8$90f83f60$7f1afea9@oemcomputer>
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: <20030824065324.C246918DB@thrintun.hactrn.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

At Sat, 23 Aug 2003 21:31:19 -0700, Randy Presuhn wrote:
> 
> In fairness,
>     1) SNMP's (ab)use of ASN.1 pretty much precludes the use of ASN.1 compiler
>          technology.  All the implementations I know of used hand-coded encoders and
>          decoders.  The vulnerabilities aren't a result of ASN.1, but rather of trusting
>          humans to do a compiler's job.
>     2) Dean was specifically writing about PER, which can be *much* more compact
>         than BER would ever hope to be.  PER can potentially result in a more compact
>         encoding than applying compression to a single packet.  Look at the spec to see
>         why.

I've used ASN.1 compiler technology for a project that included an
H.323-related frob, and ended up wishing I hadn't.  Can you say more
than 2MB just for the ASN.1 PER encoder/decoder on a box with an 8MB
flash chip? (For comparision, the embedded Linux kernel on this same
box was quite a bit less than 1MB.)  I knew you could.  No doubt we
could have gotten a smaller implementation if we'd been willing to
throw serious money at it, but H.323 wasn't even the main point of the
box, it was just an extra feature that Marketing hung on the side
because it made a cute demo.  YMMV, but based on that experience I'd
have a hard time believing that ASN.1 PER is worth the trouble.



From owner-ietf@ietf.org  Sun Aug 24 16:31: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 QAA23165
	for <ietf-web-archive@odin.ietf.org>; Sun, 24 Aug 2003 16:31:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19r1Fw-0001MD-3K
	for ietf-list@asgard.ietf.org; Sun, 24 Aug 2003 16:14:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19r1C5-0001IC-QL
	for ietf@asgard.ietf.org; Sun, 24 Aug 2003 16:10: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 QAA22322
	for <ietf@ietf.org>; Sun, 24 Aug 2003 16:10:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19r1C4-00032e-00
	for ietf@ietf.org; Sun, 24 Aug 2003 16:10:32 -0400
Received: from evrtwa1-ar8-4-65-021-158.evrtwa1.dsl-verizon.net ([4.65.21.158] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19r1C3-00032a-00
	for ietf@ietf.org; Sun, 24 Aug 2003 16:10:31 -0400
Received: from eagleswings (127.0.0.1:4528)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S314F7> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Sun, 24 Aug 2003 13:10:30 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: <ietf@ietf.org>
Cc: <ipng@sunroof.eng.sun.com>
Subject: Solving the right problems ...
Date: Sun, 24 Aug 2003 13:08:40 -0700
Message-ID: <01df01c36a7b$840dbb80$63124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

In the ongoing saga about topology reality vs. application perception of
stability, it occurs to me we are not working on the right problem. In =
short
we have established a sacred invariant in the application / transport
interface, and the demands on either side of that interface are the root =
of
conflict.

Mobile IP, and the multi6 DHT work are attempts to mitigate it through
slight of hand at the IP layer, while SCTP attempts to mask the topology
reality in the transport layer. (These are probably not the only =
examples,
but they are the ones that come to mind this morning.) Yet none of these
really do the job in all cases.

We all agree that applications should not be aware of topology. At the =
same
time,  application developers insist on the right to pass around =
incomplete
topology information. There are arguments that the IP address is =
overloaded
as an endpoint name. I don't particularly buy that, because the real
endpoint is either a protocol, or a specific port of a protocol. From =
one
perspective, when applications use addresses in referrals, they are
specifying that routing through a particular point in the topology will
reach the desired endpoint named 'transport/port-id'. But that is a
semantics and perception discussion which doesn't help reach the goal.

In any case, what applications need is a stable reference to other
participants in the app. Yet we know that current and projected reality =
says
that topology is not stable, or consistently reachable. This could be =
due to
technology issues of the underlying links, or simple policy. Either way, =
the
network as seen by the transport layer is not, and will never be stable =
or
consistently reachable from everywhere. Given that, the direct interface
with the transport layer creates a failure mode for an application =
expecting
stability.=20

Where this leads us is to the sacred invariant, and the need to solve =
the
problem in the right place. I suggest it is time for the IETF to realize
that the protocols are no longer being used in the network of 1985, so =
it is
time to insert a formal stabilization layer between application & =
transport.


Such a layer would be responsible for managing intermittent connectivity
states and varying attachment points of the transport layers below.
Applications that interact with this layer would be insulated from the
inconsistencies being experienced by the transport layer. It would also =
be
reasonable for this layer to manage multiple simultaneous transport
interactions so that the application perceived a single data path to its
peer. With appropriate trust between the stack and the network policy, =
this
would even simplify the process of QoS markings for parallel related =
data
sets.=20

The next place that leads us is to a name space. At this point I see no
reason to avoid using the FQDN structure, but acknowledge that the DNS =
as
currently deployed is not even close to being up to the task. The =
protocols
are not so much the issue as the deployment and operation model that is
focused on a limited number of nodes operated by a small community of
guru's, where the expectation is that any changes occur on the order of
several days or longer. What we ultimately need in a name service to =
support
the suggested layer is the capability for every consumer device with
electrons in it to automatically and dynamically register its current
attachment information with rapid (that doesn't mean sub-second, more =
along
the lines of a cell phone that powers up away from its home) global
convergence. As there are multiple trust boundary issues involved =
(because
not every device will be subscribed to a service), making this scale =
will
require pushing the database distribution out to smaller pockets. Making =
it
reliable for Joe-sixpack will probably require that part of the
infrastructure exists on his side of the interconnect & trust boundary =
from
any other networks. Automating the attachment of a massive number of =
small
dataset servers will probably require something with better scaling
characteristics than the current DNSsec deployment model.

Since many networks have usage policies established around the sacred
invariant, there will need to be some recommendations on how to apply =
those
policies to this new layer. We could even consider a protocol between =
this
layer and a policy entity that would aggregate applications into a =
policy
consistent with the what the network can deliver for various transport
protocols. This distribution of policy awareness would have much better
scaling characteristics than per app signaling, as well as the ability =
to
locally group unrelated transports that any given app might be using.

Bottom line is that we are spending lots of time and effort trying to =
force
fit solutions into spaces where they don't work well and end up creating
other problems. We are doing this simply to maintain the perception of
stability up to the application, over a sacred interface to a very =
unstable
network. Stability to the application is required, but forcing =
applications
to have direct interaction with the transport layer is not. Yes we =
should
continue to allow that direct interaction, but we should be clear that =
there
are no guarantees of stability on that interface. If the application =
does
not want to take care of connections coming and going to the same device =
at
potentially different places, it needs to have an intermediate =
stabilization
layer available.

Tony




From owner-ietf@ietf.org  Sun Aug 24 16:46: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 QAA23718
	for <ietf-web-archive@odin.ietf.org>; Sun, 24 Aug 2003 16:46:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19r1g3-0002Mg-Dj
	for ietf-list@asgard.ietf.org; Sun, 24 Aug 2003 16:41:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19r1fc-0002LX-G3
	for ietf@asgard.ietf.org; Sun, 24 Aug 2003 16:41: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 QAA23521
	for <ietf@ietf.org>; Sun, 24 Aug 2003 16:40:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19r1fb-0003Nk-00
	for ietf@ietf.org; Sun, 24 Aug 2003 16:41:03 -0400
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 19r1fa-0003Nh-00
	for ietf@ietf.org; Sun, 24 Aug 2003 16:41:02 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1)
  with ESMTP-TLS id 418684 for ietf@ietf.org; Sun, 24 Aug 2003 15:41:06 -0500
Message-ID: <3F4922DC.8000007@ehsco.com>
Date: Sun, 24 Aug 2003 15:41:00 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Pretty clear ... SIP
References: <Pine.LNX.4.44.0308231831280.13826-100000@npax.cavebear.com>	<002201c369f8$90f83f60$7f1afea9@oemcomputer> <20030824065324.C246918DB@thrintun.hactrn.net>
In-Reply-To: <20030824065324.C246918DB@thrintun.hactrn.net>
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 8/24/2003 1:53 AM Rob Austein wrote:

> I've used ASN.1 compiler technology for a project that included an
> H.323-related frob, and ended up wishing I hadn't.  Can you say more
> than 2MB just for the ASN.1 PER encoder/decoder on a box with an 8MB
> flash chip? (For comparision, the embedded Linux kernel on this same
> box was quite a bit less than 1MB.)  I knew you could.  No doubt we
> could have gotten a smaller implementation if we'd been willing to
> throw serious money at it, but H.323 wasn't even the main point of the

quick-n-dirty = bloat is a universal. I've seen rfc822 parsers that were
nearly as large for example. As far as that goes, moving bloat around
within a layer doesn't seem to matter much in the end, and ASN.1 parser
bloat is just as bad as XML or 822 or [...] parser bloat.

The question of where compression should occur is a good one. The usual
suspects are the application or the data-link layers, but I'm not sure
there are overwhelmingly compelling arguments for either, or that equally
compelling arguments couldn't be made for transport or network layer
compression for that matter.

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






From owner-ietf@ietf.org  Sun Aug 24 17:51: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 RAA26381
	for <ietf-web-archive@odin.ietf.org>; Sun, 24 Aug 2003 17:51:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19r2f1-0004L0-6W
	for ietf-list@asgard.ietf.org; Sun, 24 Aug 2003 17:44:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19r2eb-0004Jc-OJ
	for ietf@asgard.ietf.org; Sun, 24 Aug 2003 17:44: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 RAA26123
	for <ietf@ietf.org>; Sun, 24 Aug 2003 17:43:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19r2ea-0004Ee-00
	for ietf@ietf.org; Sun, 24 Aug 2003 17:44:04 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19r2eZ-0004Eb-00
	for ietf@ietf.org; Sun, 24 Aug 2003 17:44:03 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id EFC4B140B8; Sun, 24 Aug 2003 17:44: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 19742-09; Sun, 24 Aug 2003 17:44:01 -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 95AA2140AA; Sun, 24 Aug 2003 17:44:00 -0400 (EDT)
Date: Sun, 24 Aug 2003 17:42:08 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Tony Hain" <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: Solving the right problems ...
Message-Id: <20030824174208.727f4884.moore@cs.utk.edu>
In-Reply-To: <01df01c36a7b$840dbb80$63124104@eagleswings>
References: <01df01c36a7b$840dbb80$63124104@eagleswings>
X-Mailer: Sylpheed version 0.9.3 (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

[trying to keep this as brief as possible]

> In the ongoing saga about topology reality vs. application perception of
> stability, it occurs to me we are not working on the right problem. 

agree.

> We all agree that applications should not be aware of topology. At the same
> time,  application developers insist on the right to pass around incomplete
> topology information. 

Let's rephrase this in a less loaded way.  Application developers need
reasonably stable and reliable endpoint identifiers.  At present, the IP
address is the closest available approximation to such an identifier. 
Therefore apps developers don't want to give up the ability to pass these
things around and expect them to work from other locations in the network,
until such time as a suitable replacement is available and widely deployed.

(Note that even after such a replacement exists, there will still be some apps
that need to pass around locators - network management tools in particular.
But they will have less need to insist that those locators be usable from
other network locations.)

> In any case, what applications need is a stable reference to other
> participants in the app. Yet we know that current and projected reality says
> that topology is not stable, or consistently reachable. 

agree.

> Either way, the
> network as seen by the transport layer is not, and will never be stable or
> consistently reachable from everywhere. Given that, the direct interface
> with the transport layer creates a failure mode for an application expecting
> stability. 
> 
> Where this leads us is to the sacred invariant, and the need to solve the
> problem in the right place. I suggest it is time for the IETF to realize
> that the protocols are no longer being used in the network of 1985, so it is
> time to insert a formal stabilization layer between application & transport.

Disagree.  The layer needs to be between the current network and transport
layers.  If the layer were between transport and applications, many of the
services provided by transport would end up having to be re-implemented in
higher layers.  It would also force routing decisions to be made by layers
much more distant from the network layer that maintains reachability and state
information than the transport layer.

> The next place that leads us is to a name space. At this point I see no
> reason to avoid using the FQDN structure, but acknowledge that the DNS as
> currently deployed is not even close to being up to the task. 

Disagree.  A big part of the reason DNS is not up to the task is that its name
structure is a very poor fit for this purpose.  There is no need to have these
names be human-meaningful or to have them delegated along the lines that DNS
is delegated.  There is already a lot of semantic loading of DNS names (many
would say they're too overloaded already) which would strain their ability to
be used in this new layer.  There is a large benefit to having these names be
terse and fixed-length (though perhaps not as important or useful as it is for
IP addresses, and having a variable length name for endpoints would provide
some  additional flexibility).  There is also a benefit to being able to reuse
existing transport protocols in terms of these new names, though that can be
finessed.  Finally, using 128-bit identifiers that were API and protocol
compatible with IPv6 locators (but distinguishable from them) might be very
useful in smoothly transitioning existing stacks and apps.

Then there's the problem that DNS's protocol and replication models aren't
really a good fit either, and this hinders any effort to make it suitable
for identifier-to-locator mapping.

(Admittedly, if I thought that the new layer should go between transport and
apps then DNS-like names would make a tad more sense.)

> Since many networks have usage policies established around the sacred
> invariant, there will need to be some recommendations on how to apply those
> policies to this new layer. We could even consider a protocol between this
> layer and a policy entity that would aggregate applications into a policy
> consistent with the what the network can deliver for various transport
> protocols. This distribution of policy awareness would have much better
> scaling characteristics than per app signaling, as well as the ability to
> locally group unrelated transports that any given app might be using.

Lots of work is needed in the policy area.  But being able to express policies
in terms of stable and reliable host identifers, instead of expressing them
exclusively in terms of attachment points or links, would help a great deal.

> Bottom line is that we are spending lots of time and effort trying to force
> fit solutions into spaces where they don't work well and end up creating
> other problems. We are doing this simply to maintain the perception of
> stability up to the application, over a sacred interface to a very unstable
> network. Stability to the application is required, but forcing applications
> to have direct interaction with the transport layer is not. Yes we should
> continue to allow that direct interaction, but we should be clear that there
> are no guarantees of stability on that interface. If the application does
> not want to take care of connections coming and going to the same device at
> potentially different places, it needs to have an intermediate stabilization
> layer available.

It appears that we agree on much of the above, especially if you leave out 
loaded words like "sacred".  It needs to be understood that the needs of apps
are legitimate, even while admitting that these needs are stretching existing
network layer services beyond their capabilities.

This was a constructive post.  Thanks.

Keith



From owner-ietf@ietf.org  Sun Aug 24 18:13: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 SAA27953
	for <ietf-web-archive@odin.ietf.org>; Sun, 24 Aug 2003 18:13:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19r33F-00012G-Hh
	for ietf-list@asgard.ietf.org; Sun, 24 Aug 2003 18:09:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19r30U-0000FG-0E
	for ietf@asgard.ietf.org; Sun, 24 Aug 2003 18:06: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 SAA27206
	for <ietf@ietf.org>; Sun, 24 Aug 2003 18:06:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19r30S-0004T1-00
	for ietf@ietf.org; Sun, 24 Aug 2003 18:06:40 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19r30S-0004Sk-00
	for ietf@ietf.org; Sun, 24 Aug 2003 18:06:40 -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 RAA15828;
	Sun, 24 Aug 2003 17:59:44 -0400
Date: Sun, 24 Aug 2003 17:59:47 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: Karl Auerbach <karl@cavebear.com>
cc: IETF <ietf@ietf.org>
Subject: Re: Pretty clear ... SIP
In-Reply-To: <Pine.LNX.4.44.0308231831280.13826-100000@npax.cavebear.com>
Message-ID: <Pine.LNX.4.44.0308241726590.24445-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Sat, 23 Aug 2003, Karl Auerbach wrote:

> On Sat, 23 Aug 2003, Dean Anderson wrote:
>
> > H.323 and ASN.1 eventually surpass ...
>
> Ummm, based on my own direct experience with ASN.1 since the mid 1980's
> (X.400, SNMP, CMIP...), I disagree.
>
> It has been my experience that ASN.1, no matter which encoding rules are
> used, has proven to be a failure and lingering interoperability and
> denial-of-service disaster.
>
> For example, the flaws in ASN.1 parsers in SNMP engines have proven to be
> a decades+ old vulnerability for the net.

This isn't quite fair. Most of these vulnerabilities were hand-encoded, as
are some X.509 (BER) certificate decoders.  Hand-coded ASN.1 suffers from
the same issues as other hand-coded encoders. This is not a flaw in ASN.1.
At least ASN.1 offers a path out.  Ad-hoc text-based protocols won't do
that.

In the few cases where the compilers were are fault, the compilers were
fixed, and applications fixed by relinking.  There are test suites for
compilers that try to crack the generated decoders. This offers a degree
of assurance that can't be found in any ad-hoc protocol.

> We'd be much better off with XML, Scheme expressions, or Python pickles
> than with ASN.1 both for expressing data structures in documents and for
> encoding data structures into binary for carriage in packets.

XML has its advantages. But mostly, I've found that the biggest advantage
with XML is the ability for hierarchical queries and for hierarchical
storage. Beats the heck out of LDAP.  But this isn't entirely unique to
XML.  LDAP is meant to store a specific type of hierarchical information.
XML is general purpose.  But it is also hugely inefficient.

Another problem with text based protocols, is that when they are
encrypted, they are still ascii.  You know that there is going to be a 0
bit every 8 bits, and you generally know the alignment of the plaintext in
the cryptotext. I note that book that described the DES cracker machine
would brute force every key until it found ascii text.  Unaligned PER
doesn't suffer this problem.  Even if it has large amounts of ascii, there
is no way to determine what the alignment of the plaintext is, without
having the actual decrypted packet. A cracker machine would have a much
more difficult time detecting probable successes.  Further, if you define
the alphabet to be used in the protocol, most regular text is constrained
enough so that it can be sent using 7 bits (and no padding 0's) with
unaligned PER.

> If one wants compression, then it is better to apply it to the entire
> packet, or the byte stream - the results will almost always be much, much
> better then the item by item packing done by ASN.1's encoding rules.  (I
> was always amused that using BER, ASN.1 integers were frequently bigger
> than simply 32-bit binary, particularly when carrying unsigned numbers,
> which are rather common in networking protocols.)

When you add in the Tag and length, thats true. But then RADIUS protocol
also uses Tag/Length/Value encoding, although it doesn't call it BER. It
has the same drawback.

And of course, the protocol specifier is free to specify one of 4 variants
of PER. This does not change the semantics of the protocol, and doesn't
affect the specification of the protocol, which can be done roughly
independent of the choice of encoding.  Though, of course, you have to
specify the encoding to be used in a sentence, somewhere in the semantics
of the specification.

> (In addition, with the 60 octet minimum packet size imposed by many data
> links, compression of typically small packets - such as those containing
> SDP information - often doesn't result in much of a gain anyway.)

Well, there are typically 20 to 40 bytes of header on such links.  On low
bandwidth links, there typically aren't any minimums. And on ATM, a little
compression can make a big difference.

> As far as SIP vs H.323 goes - apart from the market fact that it is
> getting increasingly more difficult to find new products that support
> H.323 -

Few products?  Every Microsoft OS ships with an h323 client called
netmeeting. Now, its h323 compatibility has been criticized (like just
about every other 'standard' feature of Microsoft), but I haven't found
any shortage of H323 products out there.

> I find H.323 to be qualitiatively worse, as measured in units of
> elegance, than SIP.

I find just the opposite. Now I have to worry about the security of SIP
phones, and that they might be used for evesdropping.  H323 and and
trusted ASN.1 compilers can go a long way past SIP for ensuring
trustability of such devices.

> I too am sorry that SIP has gotten more complex as
> it has experienced actual implementation pressures.  However, H.323
> started out as a mish mosh - a large dollup of ISDN, a dab of SDP, a
> chunk of RTP/RTCP - and it remains a mish mosh.

Multiple tools make up a toolkit.  H323 uses the right tool for the right
job--something that SIP really missed out on.

		--Dean




From owner-ietf@ietf.org  Sun Aug 24 21:21: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 VAA04810
	for <ietf-web-archive@odin.ietf.org>; Sun, 24 Aug 2003 21:21:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19r5uH-0008Jf-Ng
	for ietf-list@asgard.ietf.org; Sun, 24 Aug 2003 21:12:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19r5ts-0008I8-PE
	for ietf@asgard.ietf.org; Sun, 24 Aug 2003 21: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 VAA04406
	for <ietf@ietf.org>; Sun, 24 Aug 2003 21:11:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19r5tq-0006VG-00
	for ietf@ietf.org; Sun, 24 Aug 2003 21:12:02 -0400
Received: from p2.cavebear.com ([199.184.128.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19r5tq-0006Ui-00
	for ietf@ietf.org; Sun, 24 Aug 2003 21:12:02 -0400
Received: from npax.cavebear.com (npax.cavebear.com [192.203.17.71])
	by p2.cavebear.com (8.12.8/8.12.8) with SMTP id h7P1BV5F010453
	for <ietf@ietf.org>; Sun, 24 Aug 2003 18:11:31 -0700
Received: from npax.cavebear.com (localhost.localdomain [127.0.0.1])
	by npax.cavebear.com (8.12.8/8.12.8) with ESMTP id h7P1BVBF013332
	for <ietf@ietf.org>; Sun, 24 Aug 2003 18:11:31 -0700
Received: by npax.cavebear.com (tmda-sendmail, from uid 2000);
	Sun, 24 Aug 2003 18:11:30 -0700 (PDT)
Date: Sun, 24 Aug 2003 18:11:30 -0700 (PDT)
Reply-To: Karl Auerbach <karl@cavebear.com>
To: Dean Anderson <dean@av8.com>
cc: IETF <ietf@ietf.org>
Subject: Re: Pretty clear ... SIP
In-Reply-To: <Pine.LNX.4.44.0308241726590.24445-100000@vista.av8.net>
Message-ID: <Pine.LNX.4.44.0308241659480.12198-100000@npax.cavebear.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
From: Karl Auerbach <karl@cavebear.com>
X-Delivery-Agent: TMDA/0.82 (Needles)
Sender: owner-ietf@ietf.org
Precedence: bulk


> > It has been my experience that ASN.1, no matter which encoding rules are
> > used, has proven to be a failure and lingering interoperability and
> > denial-of-service disaster.

I think the nugget of our discussion is the old, and probably
unanswerable, question of what is the proper balance between present
function and future (unforeseen) extension.

Back in the 1970's I met a very smart system designer.  He drew a
distinction between "intricate" and "complicated".  A fine watch with many
moving parts could be intricate as being a well engineered solution to a
specific problem, while a Rube Goldberg timepiece could be complicated and
not well engineered.  The difference being the fact that unnecessary
elements are elided from an intricate solution unless there is a specific
articulated reason to leave them in.

ASN.1 (along with other general purpose encoders such as XML) carry a 
heavy burden of machinery that is present whether it is needed or used or 
not.

Your point about ASN.1/PER having some security benefits because the
cleartext is less predictable is interesting - and I sense that it is
quite valid.  However I would suggest that there is a much greater risk
that comes from putting the heavy and complex machinery of ASN.1/*ER
engines into deployed implemtations - and that is that most
implementations of products are very poorly tested against any but the
most mainstream of traffic flows.  A complicated engine such as ASN.1/*ER
is full of nooks and crannies where undetected flaws could exist.

A simple encoding, well suited to the particular job at hand, is less 
likely to contain untested code paths, whether those paths be generated by 
compiler or by hand.

(By-the-way, I don't accept the assertion that compiler generated
ASN.1/*ER engines are going to be better than hand tooled ones - most of
the latter that I've seen (some of which I've written) use libraries for
all the heavy lifting - fix a bug in the library and relink and you're
done, just like with a compiler.  And I agree with Rob A. that in many
embedded devices, we still can't ignore memory and processing
inefficiencies.)

The net is slowly evolving an edge layer of devices that are best
described as sealed appliances - these are small devices that will tend to
never experience an update to the factory installed code image.  It is far
more important to get these right before they are shipped than to have the
ability to extend their capabilities in the field.

I do not believe that complicated representations such as ASN.1/*ER
reflect a good balance between engineering needs for the present and
expansibility for the future - thus I put ASN.1 and *ER into the
"complicated" rather than the "intricate" category.

It is certainly true that net telephony and conferencing need
extensibility - but I would suggest that the hooks for extensibility ought
to be concisely defined and placed in specific parts of the protocol
structures (such as the SDP part of today's call establishment protocols).  
I see no need to burden the entire protocol representation under a mutable
layer of complexity such as ASN.1 when there is no reason that can be
articulated to require such mutability.

By way of analogy: IPv6 addresses could have been of variable size, like
NSAPs.  But so far I don't think that enough reasons have been put forth
to justify moving away from a relatively solid and fixed-size format to a
variable address format.

Good engineering includes a kinda sixth sense of knowing when to stop
adding features.

> And of course, the protocol specifier is free to specify one of 4 variants
> of PER....

When I see phrases like "4 variants" I hear "one normal way and three
routes for attack".  Which reminds of of why the Internet isn't running
ISO/OSI today.  (Although I was surprised to learn recently that the ICAO
is presently mandating voice over CLNP for some new ground-air and air-air
systems for commercial airplanes.)

ISO/OSI had lots of good ideas.  But it could never focus or prune.  It
built a top heavy, over-optioned Vasa[*] that tipped over and sank before
it could ever be deployed.

[* - The Vasa was a 17th century Swedish warship that was so larded with 
options that it tipped over and sank on its first trip across the harbor.]

I really want VOIP and conferencing to work, not sink.

> > As far as SIP vs H.323 goes - apart from the market fact that it is
> > getting increasingly more difficult to find new products that support
> > H.323 -
> 
> Few products?  Every Microsoft OS ships with an h323 client called
> netmeeting.

Netmeeting dates from around 1997.

Most of my hard VOIP phones are either SCCP (let's not talk about that ;-)  
and/or SIP.  I haven't heard much "buzz" about new H.323 work.

> I find just the opposite. Now I have to worry about the security of SIP
> phones, and that they might be used for evesdropping.  H323 and and
> trusted ASN.1 compilers can go a long way past SIP for ensuring
> trustability of such devices.

You are not alone in your concerns about security.  I too am concerned
about spoofing of SIP messages but I haven't gotten my hands dirty enough
with SIP at that level to know whether I'm just being paranoid or whether
there is really some substance to my concern.

However, I don't see how an ASN.1 compiler adds or subtracts anything from
the tap-ability, legal or not, of a VOIP conversation.  What am I not 
seeing?

(Let's not go off into the infinite set of painful issues surrounding 
things like CALEA.)

		--karl--





From owner-ietf@ietf.org  Mon Aug 25 02:37: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 CAA27995
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 02:37:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rAp5-0006e4-7H
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 02:27:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rAob-0006cS-RG
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 02:26: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 CAA27415
	for <ietf@ietf.org>; Mon, 25 Aug 2003 02:26:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rAoZ-0002ce-00
	for ietf@ietf.org; Mon, 25 Aug 2003 02:26:55 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rAoY-0002ca-00
	for ietf@ietf.org; Mon, 25 Aug 2003 02:26:55 -0400
Received: from [127.0.0.1] (helo=roam.psg.com)
	by psg.com with esmtp (Exim 4.20)
	id 19rAoZ-000G2c-MJ; Mon, 25 Aug 2003 06:26:55 +0000
Received: from localhost ([127.0.0.1] helo=roam.psg.com)
	by roam.psg.com with esmtp (Exim 4.20)
	id 19rAoY-0001kh-2r; Mon, 25 Aug 2003 15:26:54 +0900
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 25 Aug 2003 15:26:53 +0900
To: shogunx <shogunx@sleekfreak.ath.cx>
Cc: ietf@ietf.org
Subject: Re: AW: www.ietf.org.
References: <C50038D33CB70E41920AD6D853AA23F404FC2B@Joshua.krawutschke.org>
	<Pine.LNX.4.44.0308201708540.7255-100000@sleekfreak.ath.cx>
Message-Id: <E19rAoY-0001kh-2r@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> i get an unknown host with ping6 www.ietf.org

try ping




From owner-ietf@ietf.org  Mon Aug 25 04:11: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 EAA01523
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 04:11:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rCJ1-0001dO-5m
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 04:02:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rCIV-0001VE-65
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 04:01: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 EAA01205
	for <ietf@ietf.org>; Mon, 25 Aug 2003 04:01:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rCIS-00043W-00
	for ietf@ietf.org; Mon, 25 Aug 2003 04:01:52 -0400
Received: from 96.136.33.65.cfl.rr.com ([65.33.136.96] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rCIQ-00043T-00
	for ietf@ietf.org; Mon, 25 Aug 2003 04:01:52 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19qsGv-0005pS-00; Sun, 24 Aug 2003 06:38:57 -0400
Date: Sun, 24 Aug 2003 06:38:53 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Randy Bush <randy@psg.com>
cc: ietf@ietf.org
Subject: Re: AW: www.ietf.org.
In-Reply-To: <E19rAoY-0001kh-2r@roam.psg.com>
Message-ID: <Pine.LNX.4.44.0308240622260.22378-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 25 Aug 2003, Randy Bush wrote:

> > i get an unknown host with ping6 www.ietf.org
>
> try ping
>

well right all that works Randy.  i can ping6 6bone.net all day long too,
via 6in4 encapsulation.  62 hops away.  not a problem.  so this server has
a route to the 6-bone.  and i'm in the third world, Florida.  no multicast
routing here either. which would be handy, but a remote x session
handles all the rtp i can eat, so that solves that for now.  what is
missing, it appears is a v6 route to www.ietf.org.  and an associated AAAA and v6 address for www.ietf.org,
of course.  unless there is a reason why that host should not be using v6
services, hmm?


>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81/




From owner-ietf@ietf.org  Mon Aug 25 04:18: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 EAA01895
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 04:18:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rCVa-0002Mr-Lk
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 04:15:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rCVR-0002Ju-7k
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 04:15:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01800
	for <ietf@ietf.org>; Mon, 25 Aug 2003 04:15:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rCVO-0004Dx-00
	for ietf@ietf.org; Mon, 25 Aug 2003 04:15:14 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rCVO-0004Du-00
	for ietf@ietf.org; Mon, 25 Aug 2003 04:15:14 -0400
Received: from [127.0.0.1] (helo=roam.psg.com)
	by psg.com with esmtp (Exim 4.20)
	id 19rCVP-000La5-6i; Mon, 25 Aug 2003 08:15:15 +0000
Received: from localhost ([127.0.0.1] helo=roam.psg.com)
	by roam.psg.com with esmtp (Exim 4.20)
	id 19rCVM-0002Dn-42; Mon, 25 Aug 2003 17:15:12 +0900
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 25 Aug 2003 17:15:11 +0900
To: shogunx <shogunx@sleekfreak.ath.cx>
Cc: ietf@ietf.org
Subject: Re: AW: www.ietf.org.
References: <E19rAoY-0001kh-2r@roam.psg.com>
	<Pine.LNX.4.44.0308240622260.22378-100000@sleekfreak.ath.cx>
Message-Id: <E19rCVM-0002Dn-42@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> unless there is a reason why that host should not be using v6
> services, hmm?

because it works now?

v6 has one salient feature, more address space.  religious selling
does not help the case for v6.  make it work simply and directly,
not through 42 hacks.  get router, dsl, ... vendors to support it.
then it will be used.

randy




From owner-ietf@ietf.org  Mon Aug 25 04:55: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 EAA04123
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 04:55:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rD3S-00047Y-OF
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 04:50:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rD2X-00045K-Tx
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 04:49: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 EAA03864
	for <ietf@ietf.org>; Mon, 25 Aug 2003 04:49:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rD2V-00054U-00
	for ietf@ietf.org; Mon, 25 Aug 2003 04:49:27 -0400
Received: from 96.136.33.65.cfl.rr.com ([65.33.136.96] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rD2H-00053l-00
	for ietf@ietf.org; Mon, 25 Aug 2003 04:49:27 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19qt0Q-0005ri-00; Sun, 24 Aug 2003 07:25:58 -0400
Date: Sun, 24 Aug 2003 07:25:58 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Randy Bush <randy@psg.com>
cc: ietf@ietf.org
Subject: Re: AW: www.ietf.org.
In-Reply-To: <E19rCVM-0002Dn-42@roam.psg.com>
Message-ID: <Pine.LNX.4.44.0308240722500.22439-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 25 Aug 2003, Randy Bush wrote:

> > unless there is a reason why that host should not be using v6
> > services, hmm?
>
> because it works now?

not unless we are waiting for a zone refresh.

; <<>> DiG 9.2.2 <<>> @partybus ietf.org AAAA
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55312
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;ietf.org.			IN	AAAA

;; AUTHORITY SECTION:
ietf.org.		3590	IN	SOA	ns.ietf.org. action.CNRI.Reston.VA.US. 2003071402 3600 600 2400000 86400

;; Query time: 2 msec
;; SERVER: 192.168.100.1#53(partybus)
;; WHEN: Sun Aug 24 00:46:21 2003
;; MSG SIZE  rcvd: 89


>
> v6 has one salient feature, more address space.

well, the hex addresses are nice too, from a security standpoint.

> religious selling
> does not help the case for v6.  make it work simply and directly,
> not through 42 hacks.  get router, dsl, ... vendors to support it.
> then it will be used.



mine works because of 1 hack:)



>
> randy
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81/




From owner-ietf@ietf.org  Mon Aug 25 06:37: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 GAA09027
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 06:37:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rEdE-00089G-Br
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 06:31:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rEd0-00086i-7O
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 06:31: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 GAA08803
	for <ietf@ietf.org>; Mon, 25 Aug 2003 06:31:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rEcx-0006o8-00
	for ietf@ietf.org; Mon, 25 Aug 2003 06:31:11 -0400
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19rEcw-0006nf-01
	for ietf@ietf.org; Mon, 25 Aug 2003 06:31:11 -0400
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 16661; Mon, 25 Aug 2003 06:27:32 -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: Pretty clear ... SIP
Date: Mon, 25 Aug 2003 06:30:42 -0400
Message-ID: <4A3384433CE2AB46A63468CB207E209D4F6688@zoe.office.snowshore.com>
Thread-Topic: Pretty clear ... SIP
Thread-Index: AcNqp2HlcT/wuPMJQbCq0SbagmfBsQATDn3Q
From: "Eric Burger" <eburger@snowshore.com>
To: "Karl Auerbach" <karl@cavebear.com>, "Dean Anderson" <dean@av8.com>
Cc: "IETF" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

So here's the nightmare scenario: X.693 (XER - XML Encoding Rules for =
ASN.1).

You get the "best" of ASN.1 and XML -- undecipherable ASCII text with =
lots of angle brackets :-)

> -----Original Message-----
> From: Karl Auerbach [mailto:karl@cavebear.com]
> Sent: Sun, August 24, 2003 9:12 PM
> To: Dean Anderson
> Cc: IETF
> Subject: Re: Pretty clear ... SIP
>=20
>=20
>=20
> > > It has been my experience that ASN.1, no matter which=20
> encoding rules are
> > > used, has proven to be a failure and lingering=20
> interoperability and
> > > denial-of-service disaster.
>=20
> I think the nugget of our discussion is the old, and probably
> unanswerable, question of what is the proper balance between present
> function and future (unforeseen) extension.
>=20
> Back in the 1970's I met a very smart system designer.  He drew a
> distinction between "intricate" and "complicated".  A fine=20
> watch with many
> moving parts could be intricate as being a well engineered=20
> solution to a
> specific problem, while a Rube Goldberg timepiece could be=20
> complicated and
> not well engineered.  The difference being the fact that unnecessary
> elements are elided from an intricate solution unless there=20
> is a specific
> articulated reason to leave them in.
>=20
> ASN.1 (along with other general purpose encoders such as XML) carry a=20
> heavy burden of machinery that is present whether it is=20
> needed or used or=20
> not.
[snip]




From owner-ietf@ietf.org  Mon Aug 25 08:44: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 IAA13741
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 08:44:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rGb8-0004jj-7v
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 08:37:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rGaa-0004hY-Py
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 08:36: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 IAA13371
	for <ietf@ietf.org>; Mon, 25 Aug 2003 08:36:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rGaa-0000Go-00
	for ietf@ietf.org; Mon, 25 Aug 2003 08:36:52 -0400
Received: from aragorn.bbn.com ([128.33.0.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rGaZ-0000GE-00
	for ietf@ietf.org; Mon, 25 Aug 2003 08:36:51 -0400
Received: from [128.89.88.34] (comsec.bbn.com [128.89.88.34])
	by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id h7PCaD1J024227;
	Mon, 25 Aug 2003 08:36:13 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@po2.bbn.com
Message-Id: <p05210600bb6fb20a15ec@[128.89.88.34]>
In-Reply-To: <Pine.LNX.4.44.0308231831280.13826-100000@npax.cavebear.com>
References: <Pine.LNX.4.44.0308231831280.13826-100000@npax.cavebear.com>
Date: Mon, 25 Aug 2003 08:33:26 -0400
To: Karl Auerbach <karl@cavebear.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: Pretty clear ... SIP
Cc: IETF <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
Sender: owner-ietf@ietf.org
Precedence: bulk

At 19:03 -0700 8/23/03, Karl Auerbach wrote:
>On Sat, 23 Aug 2003, Dean Anderson wrote:
>
>>  H.323 and ASN.1 eventually surpass ...
>
>Ummm, based on my own direct experience with ASN.1 since the mid 1980's
>(X.400, SNMP, CMIP...), I disagree.
>
>It has been my experience that ASN.1, no matter which encoding rules are
>used, has proven to be a failure and lingering interoperability and
>denial-of-service disaster.
>
>For example, the flaws in ASN.1 parsers in SNMP engines have proven to be
>a decades+ old vulnerability for the net.

To be fair, the flaws were in an implementation that one person 
developed and many used. The same sort of problem with a 
vulnerability being widespread has occurred in other contexts, w/o 
regard to the encoding scheme. So, this really is a red herring in 
this argument.

>We'd be much better off with XML, Scheme expressions, or Python pickles
>than with ASN.1 both for expressing data structures in documents and for
>encoding data structures into binary for carriage in packets.

Certainly XML is not going to yield a smaller encoding, so your 
reasons for preferring it have to be based on value judgements in 
other dimensions.


steve



From owner-ietf@ietf.org  Mon Aug 25 14:12: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 OAA06288
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 14:12:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rLew-000577-Kh
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 14:01:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rLbb-0004nb-Ga
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 13:58: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 NAA04655
	for <ietf@ietf.org>; Mon, 25 Aug 2003 13:58:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rLba-0004vq-00
	for ietf@ietf.org; Mon, 25 Aug 2003 13:58:14 -0400
Received: from evrtwa1-ar8-4-65-021-158.evrtwa1.dsl-verizon.net ([4.65.21.158] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rLbY-0004vc-00
	for ietf@ietf.org; Mon, 25 Aug 2003 13:58:12 -0400
Received: from eagleswings (127.0.0.1:3116)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S3167F> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Mon, 25 Aug 2003 10:58:14 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Randy Bush'" <randy@psg.com>, "'shogunx'" <shogunx@sleekfreak.ath.cx>
Cc: <ietf@ietf.org>
Subject: RE: AW: www.ietf.org.
Date: Mon, 25 Aug 2003 10:57:07 -0700
Message-ID: <031201c36b32$4ccaecd0$63124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <E19rCVM-0002Dn-42@roam.psg.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Randy Bush wrote:
> ...
> v6 has one salient feature, more address space.  religious=20
> selling does not help the case for v6. =20

I don't think making a server accessable over IPv6 is religious selling.
Some might even consider it 'running code', ... or don't we believe in =
that
anymore?

> make it work simply=20
> and directly, not through 42 hacks.  get router, dsl, ...=20
> vendors to support it. then it will be used.

Therein lies the problem. Unless a critical mass is using IPv6, there is
little incentive for router & dsl vendors to build it. Even when they =
do,
service providers are slow if not reluctant to turn it on. As much as =
you
don't like them, some of the 42 hacks are required to establish that
critical mass. We don't need all of them everywhere, but each has its =
own
warts. Different warts are acceptable or not in different environments. =
We
need to provide a reasonably small set of mechanisms, with documented =
warts,
so that the critical mass can pull the SP's (who in turn pull the =
product
vendors) into the simple deployment you are asking for.=20

Bottom line, the end user doesn't know or care about IP or any version
issues. They type names, or click on links, and magic happens. It is our =
job
to make that magic happen in more places, and as transparently as =
possible.=20

Tony




From owner-ietf@ietf.org  Mon Aug 25 15:29: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 PAA11820
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 15:29:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rMwx-0005zs-BS
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 15:24:23 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rMuN-0005ZC-CS
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 15:21: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 PAA11505
	for <ietf@ietf.org>; Mon, 25 Aug 2003 15:21:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rMuL-0006L3-00
	for ietf@ietf.org; Mon, 25 Aug 2003 15:21:41 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rMuK-0006KQ-00
	for ietf@ietf.org; Mon, 25 Aug 2003 15:21:41 -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 PAA24846;
	Mon, 25 Aug 2003 15:16:14 -0400
Date: Mon, 25 Aug 2003 15:16:17 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: Karl Auerbach <karl@cavebear.com>
cc: IETF <ietf@ietf.org>
Subject: Re: Pretty clear ... SIP
In-Reply-To: <Pine.LNX.4.44.0308241659480.12198-100000@npax.cavebear.com>
Message-ID: <Pine.LNX.4.44.0308251439510.24445-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Sun, 24 Aug 2003, Karl Auerbach wrote:

>
> > > It has been my experience that ASN.1, no matter which encoding rules are
> > > used, has proven to be a failure and lingering interoperability and
> > > denial-of-service disaster.
>
> I think the nugget of our discussion is the old, and probably
> unanswerable, question of what is the proper balance between present
> function and future (unforeseen) extension.
>
> Back in the 1970's I met a very smart system designer.  He drew a
> distinction between "intricate" and "complicated".  A fine watch with many
> moving parts could be intricate as being a well engineered solution to a
> specific problem, while a Rube Goldberg timepiece could be complicated and
> not well engineered.  The difference being the fact that unnecessary
> elements are elided from an intricate solution unless there is a specific
> articulated reason to leave them in.
>
> ASN.1 (along with other general purpose encoders such as XML) carry a
> heavy burden of machinery that is present whether it is needed or used or
> not.

Karl brings up many good points here.

> Your point about ASN.1/PER having some security benefits because the
> cleartext is less predictable is interesting - and I sense that it is
> quite valid.

> However I would suggest that there is a much greater risk
> that comes from putting the heavy and complex machinery of ASN.1/*ER
> engines into deployed implemtations - and that is that most
> implementations of products are very poorly tested against any but the
> most mainstream of traffic flows.  A complicated engine such as ASN.1/*ER
> is full of nooks and crannies where undetected flaws could exist.
>
> A simple encoding, well suited to the particular job at hand, is less
> likely to contain untested code paths, whether those paths be generated by
> compiler or by hand.

A compiler-generated code is going to be more uniform than hand-generated
code.  Once you have cleared the compiler output, you can have greater
confidence that its output will be free of security vulnerabilities.

> (By-the-way, I don't accept the assertion that compiler generated
> ASN.1/*ER engines are going to be better than hand tooled ones - most of
> the latter that I've seen (some of which I've written) use libraries for
> all the heavy lifting - fix a bug in the library and relink and you're
> done, just like with a compiler.  And I agree with Rob A. that in many
> embedded devices, we still can't ignore memory and processing
> inefficiencies.)

I agree that the inefficiencies of compilers have to be improved. And I
think they can be improved. However, I note that the size of SIP libraries
are also becoming quite large.  To some extent, the comparision is due to
the greater functionality that is built into the H323 library.  I think
that the SIP group underestimated the value of this functionality early
on, and were forced to add it later.  Certainly, one of the effects of the
SIP effort has been to validate the utility of this functionality.

> The net is slowly evolving an edge layer of devices that are best
> described as sealed appliances - these are small devices that will tend to
> never experience an update to the factory installed code image.  It is far
> more important to get these right before they are shipped than to have the
> ability to extend their capabilities in the field.

Agree.

> I do not believe that complicated representations such as ASN.1/*ER
> reflect a good balance between engineering needs for the present and
> expansibility for the future - thus I put ASN.1 and *ER into the
> "complicated" rather than the "intricate" category.

I respond only that things must be made as simple as possible, and no
simpler.

> It is certainly true that net telephony and conferencing need
> extensibility - but I would suggest that the hooks for extensibility ought
> to be concisely defined and placed in specific parts of the protocol
> structures (such as the SDP part of today's call establishment protocols).
> I see no need to burden the entire protocol representation under a mutable
> layer of complexity such as ASN.1 when there is no reason that can be
> articulated to require such mutability.

ASN.1 is not automatically extensible.  You have to specify where the
protocol can be extended.  If you don't use extensions, it should be
possible to have an ASN.1 runtime that omits the code to handle them. (One
of many possible runtime optimatizations that are possible but rarely seen
in practice, except with hand-coded encoders/decoders)

> By way of analogy: IPv6 addresses could have been of variable size, like
> NSAPs.  But so far I don't think that enough reasons have been put forth
> to justify moving away from a relatively solid and fixed-size format to a
> variable address format.

I think it depends on what kind of overhead it adds to the specification
and the implementations. In an ASN.1, it adds very little, and is of
little concern to the application programmer.  However, ASN.1 allows one
to specify fixed length fields wherever it is felt appropriate.

> > And of course, the protocol specifier is free to specify one of 4 variants
> > of PER....
>
> When I see phrases like "4 variants" I hear "one normal way and three
> routes for attack".

This is how they came into existance, historically.  BER existed first,
and there was discovered an ambiguity in the ordering of fields. This
created 2 variants of BER (Basic unordered, and Cannonical ordered). When
PER was created, these same 2 variants (though 'unordered' is the way
listed in the specification--PER doesn't send the tag) were kept, and an
additonal combination of aligned or unaligned were added for a total of 4
variants.

> ISO/OSI had lots of good ideas.  But it could never focus or prune.  It
> built a top heavy, over-optioned Vasa[*] that tipped over and sank before
> it could ever be deployed.

I think a lot of what hurt the ISO/OSI stack was the lack of cheap
commercial ASN.1 compilers.  In the beginning, there were no compilers.
One also had to learn ASN.1, and (to start) BER, before one could begin
writing an encoder. By contract, the IETF specifications of concrete
fields and offsets were much easier to start implmementing in C.

I would make an analogy to Graphics: Turtle Graphics are much easier get
started with, but people seem not to use that for "industrial" graphics
applications.

> Netmeeting dates from around 1997.

And it still works, due to ASN.1, so long as you can interoperate with a
h323 version 2 client.  Pick up a SIP client from several years ago, and
see how far you can get.

> You are not alone in your concerns about security.  I too am concerned
> about spoofing of SIP messages but I haven't gotten my hands dirty enough
> with SIP at that level to know whether I'm just being paranoid or whether
> there is really some substance to my concern.

Both are equally vulnerable to spoofing. Sometimes I hear people say that
its harder to spoof h323, but in princple, its not any harder if you have
the right tools. If this was ever true, it was mostly the effect of lack
of tools in the past. It has no bearing on the future.

> However, I don't see how an ASN.1 compiler adds or subtracts anything from
> the tap-ability, legal or not, of a VOIP conversation.  What am I not
> seeing?

A trustworthy ASN.1 decoder means that someone cannot connect to an H323
system, effect a buffer overflow, and begin listening to what is going on.
The generated decoder stands as a secure interface between the application
programmer, and the intruder. We don't depend so much on the application
programmer to have appropriate knowledge about things like buffer
overflows.

		--Dean




From owner-ietf@ietf.org  Mon Aug 25 15:44: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 PAA12496
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 15:44:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rNBX-0007ZT-7M
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 15:39:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rN8l-0007NP-MG
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 15:36: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 PAA12206
	for <ietf@ietf.org>; Mon, 25 Aug 2003 15:36:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rN8k-0006X0-00
	for ietf@ietf.org; Mon, 25 Aug 2003 15:36:34 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rN8j-0006Ws-00
	for ietf@ietf.org; Mon, 25 Aug 2003 15:36:33 -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 h7PJauxS076774;
	Mon, 25 Aug 2003 21:36:56 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Mon, 25 Aug 2003 21:36:33 +0200
Subject: Re: AW: www.ietf.org.
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Randy Bush <randy@psg.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <E19rCVM-0002Dn-42@roam.psg.com>
Message-Id: <6EA7C10C-D733-11D7-83FB-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 maandag, aug 25, 2003, at 10:15 Europe/Amsterdam, Randy Bush wrote:

>> unless there is a reason why that host should not be using v6
>> services, hmm?

> because it works now?

But for some boxes only if I use NAT, and having to use NAT makes for a 
liberal definition of "works".

> v6 has one salient feature, more address space.  religious selling
> does not help the case for v6.  make it work simply and directly,
> not through 42 hacks.  get router, dsl, ... vendors to support it.
> then it will be used.

So when everyone else is running IPv6, the IETF will start doing it 
too? Not good enough. The proof of the pudding is in the eating. The 
proof of the protocol is in running production traffic over it.

The IETF www server uses Apache2 which supports IPv6 just fine, BTW. As 
do all the major OS vendors and a good number of router vendors. If 
there is a reason why it is not a good idea to run www.ietf.org over 
IPv6 at this point in time: no big deal. "It works now" doesn't qualify 
as such a reason, IMO.

But I see psg.com (which handles mail for ops.ietf.org) now actually 
accepts connections on port 25 as per the MX and AAAA records that have 
been in place for a long time so I guess there is progress.




From owner-ietf@ietf.org  Mon Aug 25 17:11: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 RAA16324
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 17:11:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rOMV-0005S5-EV
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 16:54:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19qKwc-0002BN-CH
	for ietf@asgard.ietf.org; Fri, 22 Aug 2003 19:03: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 TAA26717
	for <ietf@ietf.org>; Fri, 22 Aug 2003 19:03:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qKwa-0003A3-00
	for ietf@ietf.org; Fri, 22 Aug 2003 19:03:44 -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 19qKwa-00039p-00
	for ietf@ietf.org; Fri, 22 Aug 2003 19:03:44 -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 h7MN36Pl024553;
	Fri, 22 Aug 2003 16:03:06 -0700 (PDT)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AKR75404;
	Fri, 22 Aug 2003 15:54:43 -0700 (PDT)
Date: Fri, 22 Aug 2003 16:06:04 -0700
Subject: Re: WG Review: Centralized Conferencing (xcon)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Henry Sinnreich <Henry.Sinnreich@mci.com>, vinton.g.cerf@mci.com,
        mrose@dbc.mtview.ca.us, jon.peterson@neustar.biz,
        alan.johnston@mci.com, rsparks@dynamicsoft.com, ietf@ietf.org
To: Keith Moore <moore@cs.utk.edu>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <20030821190034.6a8ed354.moore@cs.utk.edu>
Message-Id: <34DF722C-D4F5-11D7-85BF-0003938AF740@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 Thursday, August 21, 2003, at 04:00 PM, Keith Moore wrote:
>> Are not service providers and network
>> managers the people supposed to bring these services into operation?
>
> I certainly don't share that assumption.  Then again, I don't share the
> assumption that any central coordinating authority is needed to set up
> conferencing services.

What do you mean by central coordinating authority?  A big service 
provider, or *any* point of control?

I am certainly interested in hearing requirements from the large 
operators, but not to the exclusion of requirements for on my own 
equipment, local, or community-hosted conference services.

XCON was envisioned as a way to handle "tightly-coupled conferences" 
with a central point of control. However, there is no reason this 
central point of control has to be hosted by a service provider.  It 
could be running in your phone or IM client for example.

I believe loosely-coupled conferences bring problems with a very 
different timeline, and I do not wish to bog down XCON with these 
problems. Indeed, I believe that much of the interest at the XCON BOF 
was because we weren't trying to boil the ocean.

thanks,
-rohan






From owner-ietf@ietf.org  Mon Aug 25 20:31: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 UAA24814
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 20:31:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rRcX-0002c2-4c
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 20:23:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rRbR-0002YZ-Ek
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 20:22: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 UAA24382
	for <ietf@ietf.org>; Mon, 25 Aug 2003 20:22:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rRbP-0001Rf-00
	for ietf@ietf.org; Mon, 25 Aug 2003 20:22:27 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rRbP-0001Ra-00
	for ietf@ietf.org; Mon, 25 Aug 2003 20:22:27 -0400
Received: from [127.0.0.1] (helo=roam.psg.com)
	by psg.com with esmtp (Exim 4.20)
	id 19rRbN-0007aG-4l; Tue, 26 Aug 2003 00:22:25 +0000
Received: from localhost ([127.0.0.1] helo=roam.psg.com)
	by roam.psg.com with esmtp (Exim 4.20)
	id 19rRbM-0000BK-7k; Tue, 26 Aug 2003 09:22:24 +0900
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 26 Aug 2003 09:22:23 +0900
To: Tony Hain <alh-ietf@tndh.net>
Cc: ietf@ietf.org
Subject: RE: AW: www.ietf.org.
References: <E19rCVM-0002Dn-42@roam.psg.com>
	<031201c36b32$4ccaecd0$63124104@eagleswings>
Message-Id: <E19rRbM-0000BK-7k@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>> v6 has one salient feature, more address space.  religious 
>> selling does not help the case for v6.  
> I don't think making a server accessable over IPv6 is religious selling.
> Some might even consider it 'running code', ... or don't we believe in that
> anymore?

with the current size of the ietf product set, one can not run all
code.  the fact is that all users can get to www.ietf.org.  no, i
can not get to it usefully using v6, readably on my i-mode phone,
etc.  so stick to the middle of the road.

> Therein lies the problem. Unless a critical mass is using IPv6, there is
> little incentive for router & dsl vendors to build it. Even when they do,
> service providers are slow if not reluctant to turn it on.

this assertion is false, or disingenuous at best.  backbone service
providers are turning it on at great pain, much of that pain due to
lack of support from large router vendors.

> As much as you don't like them, some of the 42 hacks are required
> to establish that critical mass. 

nope.  they *detract* from it because it makes it appear as if one
*needs* all that kink to use ipv6.  in fact, one needs almost
nothing but real dual-stack deployment.  gussying it up with 3" of
pancake makeup does not make it more attractive.  you have been
operating on that theory for many years and it has not worked.

> Bottom line, the end user doesn't know or care about IP or any
> version issues.  They type names, or click on links, and magic
> happens. 

yep.  as i said <http://www.ietf.org/> usually works pretty well.

> It is our job to make that magic happen in more places, and as
> transparently as possible.

no.  it is the vendors' and operators' jobs.

randy




From owner-ietf@ietf.org  Mon Aug 25 22: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 WAA28593
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 22:46:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rThv-00047m-W7
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 22:37:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rThQ-00044e-OQ
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 22:36: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 WAA28266
	for <ietf@ietf.org>; Mon, 25 Aug 2003 22:36:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rThO-0002X6-00
	for ietf@ietf.org; Mon, 25 Aug 2003 22:36:46 -0400
Received: from evrtwa1-ar8-4-65-021-158.evrtwa1.dsl-verizon.net ([4.65.21.158] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rThN-0002X3-00
	for ietf@ietf.org; Mon, 25 Aug 2003 22:36:46 -0400
Received: from eagleswings (127.0.0.1:4955)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S31779> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Mon, 25 Aug 2003 19:36:44 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Randy Bush'" <randy@psg.com>
Cc: <ietf@ietf.org>
Subject: RE: AW: www.ietf.org.
Date: Mon, 25 Aug 2003 19:35:29 -0700
Message-ID: <037f01c36b7a$b73ee380$63124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <E19rRbM-0000BK-7k@roam.psg.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Randy Bush wrote:
> this assertion is false, or disingenuous at best. =20
> backbone service providers are turning it on at great=20
> pain, much of that pain due to lack of support from=20
> large router vendors.

A few are working on lab efforts, and a very small number are offering
service. Even if the transit ISP's had full up support today, that =
doesn't
get the job done. The real issue is to convince the smaller ISP's that =
offer
service directly to the end user.


> you have been operating on that theory for many years and it has not
worked.

If one goes back to the origin of ngtrans, I was the one pushing hard to
make sure that dual stack was the priority, and that all of that was
specified before any solutions for corner cases. Even with dual stack as =
the
primary approach, many network managers are expressing reluctance =
because
they don't want to overlook the corner case that is important in their
network. Independent of that, app developers see no value in building =
code
for a network that they can't rely on working. It has only been recent =
work
with 6to4 & teredo creating the perception of an end-to-end (in this =
case it
only works at the end points) IPv6 network that has allowed apps to move
beyond what they can do with IPv4.


> > Bottom line, the end user doesn't know or care about IP or any =
version=20
> > issues.  They type names, or click on links, and magic happens.
>=20
> yep.  as i said <http://www.ietf.org/> usually works pretty well.

So why shouldn't port 25 work?

> > It is our job to make that magic happen in more places, and as=20
> > transparently as possible.
>=20
> no.  it is the vendors' and operators' jobs.

Ok, it is our job to create the consistency so that vendors can create
products for operators to deploy and deliver services. In any case, just
having a deployment in a few backbone routers doesn't get the job done.

Tony






From owner-ietf@ietf.org  Mon Aug 25 23:04: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 XAA29477
	for <ietf-web-archive@odin.ietf.org>; Mon, 25 Aug 2003 23:04:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rU3q-0005Ux-Db
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 22:59:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rU2l-0005Rm-Og
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 22:58: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 WAA29176
	for <ietf@ietf.org>; Mon, 25 Aug 2003 22:58:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rU2j-0002lA-00
	for ietf@ietf.org; Mon, 25 Aug 2003 22:58:49 -0400
Received: from 96.136.33.65.cfl.rr.com ([65.33.136.96] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rU2h-0002l1-00
	for ietf@ietf.org; Mon, 25 Aug 2003 22:58:49 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19rA0x-0006Hu-00; Mon, 25 Aug 2003 01:35:39 -0400
Date: Mon, 25 Aug 2003 01:35:30 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Tony Hain <alh-ietf@tndh.net>
cc: "'Randy Bush'" <randy@psg.com>, <ietf@ietf.org>
Subject: RE: AW: www.ietf.org.
In-Reply-To: <037f01c36b7a$b73ee380$63124104@eagleswings>
Message-ID: <Pine.LNX.4.44.0308250134420.24104-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 25 Aug 2003, Tony Hain wrote:

> Randy Bush wrote:
> > this assertion is false, or disingenuous at best.
> > backbone service providers are turning it on at great
> > pain, much of that pain due to lack of support from
> > large router vendors.
>
> A few are working on lab efforts, and a very small number are offering
> service. Even if the transit ISP's had full up support today, that doesn't
> get the job done. The real issue is to convince the smaller ISP's that offer
> service directly to the end user.
>
funny, i'm building a wireless version of that now, and ARIN seems to want
$2500 from me for an allocation.


>
> > you have been operating on that theory for many years and it has not
> worked.
>
> If one goes back to the origin of ngtrans, I was the one pushing hard to
> make sure that dual stack was the priority, and that all of that was
> specified before any solutions for corner cases. Even with dual stack as the
> primary approach, many network managers are expressing reluctance because
> they don't want to overlook the corner case that is important in their
> network. Independent of that, app developers see no value in building code
> for a network that they can't rely on working. It has only been recent work
> with 6to4 & teredo creating the perception of an end-to-end (in this case it
> only works at the end points) IPv6 network that has allowed apps to move
> beyond what they can do with IPv4.
>
>
> > > Bottom line, the end user doesn't know or care about IP or any version
> > > issues.  They type names, or click on links, and magic happens.
> >
> > yep.  as i said <http://www.ietf.org/> usually works pretty well.
>
> So why shouldn't port 25 work?
>
> > > It is our job to make that magic happen in more places, and as
> > > transparently as possible.
> >
> > no.  it is the vendors' and operators' jobs.
>
> Ok, it is our job to create the consistency so that vendors can create
> products for operators to deploy and deliver services. In any case, just
> having a deployment in a few backbone routers doesn't get the job done.
>
> Tony
>
>
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81/




From owner-ietf@ietf.org  Tue Aug 26 04:19: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 EAA23011
	for <ietf-web-archive@odin.ietf.org>; Tue, 26 Aug 2003 04:19:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rYuC-0004Lg-Jv
	for ietf-list@asgard.ietf.org; Tue, 26 Aug 2003 04:10:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rYte-0004Iu-3b
	for ietf@asgard.ietf.org; Tue, 26 Aug 2003 04:09: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 EAA22679
	for <ietf@ietf.org>; Tue, 26 Aug 2003 04:09:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rYtb-0005d1-00
	for ietf@ietf.org; Tue, 26 Aug 2003 04:09:43 -0400
Received: from web80603.mail.yahoo.com ([66.218.79.92])
	by ietf-mx with smtp (Exim 4.12)
	id 19rYtb-0005cp-00
	for ietf@ietf.org; Tue, 26 Aug 2003 04:09:43 -0400
Message-ID: <20030826080914.16913.qmail@web80603.mail.yahoo.com>
Received: from [213.147.69.72] by web80603.mail.yahoo.com via HTTP; Tue, 26 Aug 2003 01:09:14 PDT
Date: Tue, 26 Aug 2003 01:09:14 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Re: [Fwd: Emerging Network Usage and Engineering Issues]
To: Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org
In-Reply-To: <F3842B37-D237-11D7-977B-00039388672E@muada.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

A scenario where all the ecommerce code and routing
code ( paid traffic ) would fail is if the Financial
Capital City of the World is Struck in a light nuke
attack.  Are you, or is the code capable of handle
this ?
If so I am very comfortable.

Nyagudi Musandu 

How do you propose we test these protocols?
> 
> 


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com



From owner-ietf@ietf.org  Tue Aug 26 05:15: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 FAA24455
	for <ietf-web-archive@odin.ietf.org>; Tue, 26 Aug 2003 05:15:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rZr3-0007Hu-8t
	for ietf-list@asgard.ietf.org; Tue, 26 Aug 2003 05:11:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rZon-0007CK-Hl
	for ietf@asgard.ietf.org; Tue, 26 Aug 2003 05:08: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 FAA24317
	for <ietf@ietf.org>; Tue, 26 Aug 2003 05:08:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rZol-0006C3-00
	for ietf@ietf.org; Tue, 26 Aug 2003 05:08:47 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rZok-0006Bz-00
	for ietf@ietf.org; Tue, 26 Aug 2003 05:08:46 -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 h7Q99AxS085557;
	Tue, 26 Aug 2003 11:09:10 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Tue, 26 Aug 2003 11:08:48 +0200
Subject: Re: [Fwd: Emerging Network Usage and Engineering Issues]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: NM Research <nm_research@yahoo.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <20030826080914.16913.qmail@web80603.mail.yahoo.com>
Message-Id: <E739F710-D7A4-11D7-83FB-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On dinsdag, aug 26, 2003, at 10:09 Europe/Amsterdam, NM Research wrote:

> A scenario where all the ecommerce code and routing
> code ( paid traffic ) would fail is if the Financial
> Capital City of the World is Struck in a light nuke
> attack.  Are you, or is the code capable of handle
> this ?

This is not a matter of code, but a matter of hardware. You need to 
have all your hardware in a Faraday cage to avoid the electronics from 
being fried by the EM pulse. But even then you're not safe: someone who 
is supposed to know about these things once told me that fiber optic 
cables have the nasty tendency to explode when a nuke goes off. The 
huge EM fields cause induction in the steel mechanical reinforcement in 
the cable, causing it to get incredibly hot incredibly fast. I also 
gather that radioactivity degrades the transparency of fiber, so that 
could lead to trouble even if the cable doesn't explode.

But our current routing protocols will be happy to route around failed 
routers and links. No problems there.




From owner-ietf@ietf.org  Tue Aug 26 05:31: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 FAA25118
	for <ietf-web-archive@odin.ietf.org>; Tue, 26 Aug 2003 05:31:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ra5j-0008Gz-1m
	for ietf-list@asgard.ietf.org; Tue, 26 Aug 2003 05:26:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ra50-0008Ee-Kh
	for ietf@asgard.ietf.org; Tue, 26 Aug 2003 05:25: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 FAA24885
	for <ietf@ietf.org>; Tue, 26 Aug 2003 05:25:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ra4y-0006RD-00
	for ietf@ietf.org; Tue, 26 Aug 2003 05:25:32 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ra4x-0006QT-00
	for ietf@ietf.org; Tue, 26 Aug 2003 05:25:31 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 259F361BE2; Tue, 26 Aug 2003 11:25:01 +0200 (CEST)
Date: Mon, 25 Aug 2003 23:49:46 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Karl Auerbach <karl@cavebear.com>
Cc: IETF <ietf@ietf.org>
Subject: ASN.1 (Re: Pretty clear ... SIP)
Message-ID: <156559971.1061855386@localhost>
In-Reply-To: <Pine.LNX.4.44.0308251439510.24445-100000@vista.av8.net>
References:  <Pine.LNX.4.44.0308251439510.24445-100000@vista.av8.net>
X-Mailer: Mulberry/3.0.2 (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

Aah.... an ASN.1 firefight!
It's been a LONG time since we've had one of those, but they used to be a 
regularly scheduled event on this list.

I used to have opinions on this debate - for a trip down memory lane, check 
out the "canonical X.400 vs SMTP debate" on my website (sorry, typing 
offline at the moment - google will find it).

One note, however:

--On 25. august 2003 15:16 -0400 Dean Anderson <dean@av8.com> wrote:

>> It is certainly true that net telephony and conferencing need
>> extensibility - but I would suggest that the hooks for extensibility
>> ought to be concisely defined and placed in specific parts of the
>> protocol structures (such as the SDP part of today's call establishment
>> protocols). I see no need to burden the entire protocol representation
>> under a mutable layer of complexity such as ASN.1 when there is no
>> reason that can be articulated to require such mutability.
>
> ASN.1 is not automatically extensible.  You have to specify where the
> protocol can be extended.  If you don't use extensions, it should be
> possible to have an ASN.1 runtime that omits the code to handle them. (One
> of many possible runtime optimatizations that are possible but rarely seen
> in practice, except with hand-coded encoders/decoders)

One warning to those with long memories and strong opinions:

The way one does extensibility in ASN.1 has changed greatly since the first 
(1984) versions of ASN.1. Lots of the hard opinions people have here are 
based on ASN.1(1984) experience, which was what SNMP originally used.

I have had people tell me that the post-1988 versions of ASN.1 are really 
nice in this department, but haven't used ASN.1 seriously since 
approximately 1992 (when PER was just being stabilized).
So I'm not qualified to say whether they are right or not.

Aside on complexity: The definition of ABNF, the "formal" language used to 
define the SIP syntax, RFC 2234, is 14 pages long, and has been blasted by 
several people as being a too complex tool for proper protocol description.

I haven't checked the pagecount of the ITU recommendations defining ASN.1 
recently, but the last time I had one in hand (X.208/88), I'd estimate it 
as at least 10 times that number of pages.

                      Harald










From owner-ietf@ietf.org  Tue Aug 26 06:27: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 GAA26988
	for <ietf-web-archive@odin.ietf.org>; Tue, 26 Aug 2003 06:27:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19raxu-0002RM-Sv
	for ietf-list@asgard.ietf.org; Tue, 26 Aug 2003 06:22:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rawN-0002N7-Jn
	for ietf@asgard.ietf.org; Tue, 26 Aug 2003 06:20: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 GAA26527
	for <ietf@ietf.org>; Tue, 26 Aug 2003 06:20:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rawL-0006qy-00
	for ietf@ietf.org; Tue, 26 Aug 2003 06:20:41 -0400
Received: from web80605.mail.yahoo.com ([66.218.79.94])
	by ietf-mx with smtp (Exim 4.12)
	id 19rawK-0006qi-00
	for ietf@ietf.org; Tue, 26 Aug 2003 06:20:40 -0400
Message-ID: <20030826102011.99254.qmail@web80605.mail.yahoo.com>
Received: from [213.147.69.72] by web80605.mail.yahoo.com via HTTP; Tue, 26 Aug 2003 03:20:11 PDT
Date: Tue, 26 Aug 2003 03:20:11 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Re: [Fwd: Emerging Network Usage and Engineering Issues]
To: Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org
In-Reply-To: <E739F710-D7A4-11D7-83FB-00039388672E@muada.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-18131299-1061893211=:97700"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-18131299-1061893211=:97700
Content-Type: text/plain; charset=us-ascii

Ofcourse I know about EMP.  But what I mean is this, all international credit cards, bank transfers, insurance, commerce deals etc. are supported, initiated, terminated or developed in a city in USA.    Even if you want to make a bank transfer from one street to another in Kenya, you go through the USA/ that city.  Do you get the picture??
 
Nyagudi Musandu

Iljitsch van Beijnum <iljitsch@muada.com> wrote:
On dinsdag, aug 26, 2003, at 10:09 Europe/Amsterdam, NM Research wrote:

> A scenario where all the ecommerce code and routing
> code ( paid traffic ) would fail is if the Financial
> Capital City of the World is Struck in a light nuke
> attack. Are you, or is the code capable of handle
> this ?

This is not a matter of code, but a matter of hardware. You need to 
have all your hardware in a Faraday cage to avoid the electronics from 
being fried by the EM pulse. But even then you're not safe: someone who 
is supposed to know about these things once told me that fiber optic 
cables have the nasty tendency to explode when a nuke goes off. The 
huge EM fields cause induction in the steel mechanical reinforcement in 
the cable, causing it to get incredibly hot incredibly fast. I also 
gather that radioactivity degrades the transparency of fiber, so that 
could lead to trouble even if the cable doesn't explode.

But our current routing protocols will be happy to route around failed 
routers and links. No problems there.


---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
--0-18131299-1061893211=:97700
Content-Type: text/html; charset=us-ascii

<DIV>Ofcourse I know about EMP.&nbsp; But what I mean is this, all international credit cards, bank transfers, insurance, commerce deals etc. are supported, initiated, terminated or developed in a city in USA.&nbsp;&nbsp;&nbsp;&nbsp;Even if you want to make a bank transfer from one street to another in Kenya, you go through the USA/ that city.&nbsp; Do you get the picture??</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi Musandu<BR><BR><B><I>Iljitsch van Beijnum &lt;iljitsch@muada.com&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px">On dinsdag, aug 26, 2003, at 10:09 Europe/Amsterdam, NM Research wrote:<BR><BR>&gt; A scenario where all the ecommerce code and routing<BR>&gt; code ( paid traffic ) would fail is if the Financial<BR>&gt; Capital City of the World is Struck in a light nuke<BR>&gt; attack. Are you, or is the code capable of handle<BR>&gt; this ?<BR><BR>This is not a matter of code, but a matter of hardware. You need to <BR>have all your hardware in a Faraday cage to avoid the electronics from <BR>being fried by the EM pulse. But even then you're not safe: someone who <BR>is supposed to know about these things once told me that fiber optic <BR>cables have the nasty tendency to explode when a nuke goes off. The <BR>huge EM fields cause induction in the steel mechanical reinforcement in <BR>the cable, causing it to get incredibly hot incredibly fast. I also <BR>gather that radioactivity degrades !
 the
 transparency of fiber, so that <BR>could lead to trouble even if the cable doesn't explode.<BR><BR>But our current routing protocols will be happy to route around failed <BR>routers and links. No problems there.<BR></BLOCKQUOTE><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*http://promo.yahoo.com/sbc/">SBC Yahoo! DSL</a> - Now only $29.95 per month!
--0-18131299-1061893211=:97700--



From owner-ietf@ietf.org  Tue Aug 26 09:11: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 JAA02637
	for <ietf-web-archive@odin.ietf.org>; Tue, 26 Aug 2003 09:11:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rdTk-0001R2-LH
	for ietf-list@asgard.ietf.org; Tue, 26 Aug 2003 09:03:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rdSR-0001MX-Rt
	for ietf@asgard.ietf.org; Tue, 26 Aug 2003 09:01: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 JAA02198
	for <ietf@ietf.org>; Tue, 26 Aug 2003 09:01:55 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rdSR-0000Pt-00
	for ietf@ietf.org; Tue, 26 Aug 2003 09:01:59 -0400
Received: from h80ad2714.async.vt.edu ([128.173.39.20] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rdSP-0000Pq-00
	for ietf@ietf.org; Tue, 26 Aug 2003 09:01:57 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7QD1sMe015618;
	Tue, 26 Aug 2003 09:01:54 -0400
Message-Id: <200308261301.h7QD1sMe015618@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: [Fwd: Emerging Network Usage and Engineering Issues] 
In-Reply-To: Your message of "Tue, 26 Aug 2003 03:20:11 PDT."
             <20030826102011.99254.qmail@web80605.mail.yahoo.com> 
References: <20030826102011.99254.qmail@web80605.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1296281260P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 26 Aug 2003 09:01:54 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Tue, 26 Aug 2003 03:20:11 PDT, NM Research <nm_research@yahoo.com>  said:

> Ofcourse I know about EMP.  But what I mean is this, all international credit
> cards, bank transfers, insurance, commerce deals etc. are supported, initiated,
> terminated or developed in a city in USA.    Even if you want to make a bank 
> transfer from one street to another in Kenya, you go through the USA/ that city.
> Do you get the picture??

Given that there isn't any *single* city that has *all* the banks - offhand, I
can think of Boston, NYC, Chicago, and San Francisco as having large financial
districts, it would take multiple hits. Presumably, most of the larger banks
have some sort of off-site disaster recovery plans.

I posit that if enough nukes go off to take out enough banks to matter, the
question of whether the net is moving bits will be of secondary importance.  I
know I'm going to be busy getting my children to someplace the fallout isn't.

And at that point, an OC12 isn't going to matter as much as a box of rifle ammunition.

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

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

iD8DBQE/S1pCcC3lWbTT17ARAgsLAJ9etHi7cYEL3Nvzti3/R0LWtNaY1ACaA+UC
GZ/vZEdpdtJ3lyc6SZedhAQ=
=qHbd
-----END PGP SIGNATURE-----

--==_Exmh_1296281260P--



From owner-ietf@ietf.org  Tue Aug 26 10:27: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 KAA07995
	for <ietf-web-archive@odin.ietf.org>; Tue, 26 Aug 2003 10:27:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19refI-0006Fr-Tx
	for ietf-list@asgard.ietf.org; Tue, 26 Aug 2003 10:19:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rcsI-0008Ow-01
	for ietf@asgard.ietf.org; Tue, 26 Aug 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 IAA01228;
	Tue, 26 Aug 2003 08:24:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rcsG-0000Bd-00; Tue, 26 Aug 2003 08:24:36 -0400
Received: from odin2.bull.net ([192.90.70.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rcsF-0000BZ-00; Tue, 26 Aug 2003 08:24:35 -0400
Received: from clbull.frcl.bull.fr (IDENT:root@clbull.frcl.bull.fr [129.182.8.31])
	by odin2.bull.net (8.9.3/8.9.3) with ESMTP id OAA35904;
	Tue, 26 Aug 2003 14:29:33 +0200
Received: from bull.net (frcls4013.frcl.bull.fr [129.182.108.120])
	by clbull.frcl.bull.fr (8.9.3/8.9.3) with ESMTP id OAA05548;
	Tue, 26 Aug 2003 14:25:03 +0200
Message-ID: <3F4B516C.4050607@bull.net>
Date: Tue, 26 Aug 2003 14:24:12 +0200
From: Denis Pinkas <Denis.Pinkas@bull.net>
Organization: Bull SA.
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en, fr
MIME-Version: 1.0
To: iesg@ietf.org, ietf@ietf.org
CC: Tim Polk <wpolk@nist.gov>, Stephen Kent <kent@bbn.com>
Subject: Re: Last Call: 'Internet X.509 Public Key Infrastructure Warranty
          Certificate Extension' to Informational RFC
References: <E19me7r-0005yz-8u@asgard.ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The IESG has received a request from the Public-Key Infrastructure (X.509) 
> WG to consider 'Internet X.509 Public Key Infrastructure Warranty 
> Certificate Extension' <draft-ietf-pkix-warranty-extn-03.txt> as an 
> Informational RFC. 
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2003-08-26.


I am quite surprised to see that the IESG received a request from the PKIX 
chairs while a discussion still takes place on the PKIX mailing list on the 
document.

The last response from the lead editor (Alice Sturgeon) is dated August 13. 
She recognizes that at least some "clarifications" are needed.

The e-mail is duplicated below and exhibits that there is good progress but 
still no consensus on the document.

At least some changes to the June version (version 3) are expected before 
the document can be published.

Regards,

Denis

Note: I am back from holidays, just today (i.e. August 26 th).

===============================================================================

Hello Denis,

Please see my comments inserted below, as [AS2], to distinguish from the 
first set of replies to your original comments.

Alice

Alice Sturgeon
Chair, Canadian Advisory Committee - Information Technology Security
ISO/IEC JTC 1/SC 27
and
System Policy Architect & Manager of Standards
SPYRUS

-----Original Message-----
From: owner-ietf-pkix@mail.imc.org
[mailto:owner-ietf-pkix@mail.imc.org]On Behalf Of Denis Pinkas
Sent: Tuesday, July 29, 2003 6:38 AM
To: asturgeon@spyrus.com
Cc: ietf-pkix@imc.org
Subject: Re: I-D ACTION:draft-ietf-pkix-warranty-extn-03.txt



Alice,

Please see my responses below.

Comments on warranty-extn-03.txt (June 2003)

1- On page 2. The text mentions: "A relying party that has a warranty from a
CA".

Does this mean that a relying party must have a contract with the CA to get
advantage of the warranty ?
[Alice] No.

Does this mean that a relying party will get a warranty without a contract
signed with the CA ?
[Alice] Yes.

Does this extension allow to make the difference between the case of a
signed contract and the case of an unsigned contract where the guarantees
could be different?

[Alice] No. If there are any differences in the T&C pertaining to a
contractual arrangement, these differences will be outside of, beyond the
scope, and not pertinent to, the warranty offered in the certificate.  It
applies equally to all relying parties, whether or not a contract has been
signed.

[Denis] Then say something like: "Whether or not relying parties have signed
agreements with CAs, the CA will provide Terms and Conditions for this
warranty which relates to its liability."

[AS2] Alternatively, to make the same point, it could remain implicit.

2 - The difference between the base warranty and the extended warranty is
not crystal clear.

How can a relying party know whether it can have the benefits of the base
warranty or of the extended warranty ?

If the extended warranty is present, then the relying party has the benefit
of the extended warranty.  In short, if it is present, then the relying
party knows that the relying party has the benefit of the extended warranty
by its presence alone.  The syntax shows that the extended warranty MAY be
present:
   Warranty ::= CHOICE  {
         none                 NULL,            -- No warranty provided
         wData                WarrantyData  }  -- Explicit warranty

     WarrantyData ::= SEQUENCE  {
         base                 WarrantyInfo,
         extended             WarrantyInfo OPTIONAL,
         tcURL                TermsAndConditionsURL OPTIONAL  }

If the tcURL is present, a human being might understand the terms and
conditions (if he can understand the local language used), but a computer
program will not be able to do so. This means that computers cannot
understand the difference.

[Alice] The computer does not need to know what is in the T&C.  If the tcURL
is present, it is optionally for the benefit of the human reader. Perhaps
you could suggest some text to clarify this in the I-D if you still think it
is needed.

[Denis] Then say something like: "Warranty extensions are only aimed for
human interpretation and contain data that is inappropriate for computer
based verification schemes, the warranty extension MUST NOT be an active
component in automated certification path validation."

[AS2] But this is not necessarily true. It may be that the RP (i.e., the 
human) has to go to a T&C document if the extended warranty is present, if 
the RP wants to know what exactly is in the T&C, but there should be the 
option of not going to the T&C.  If the extended warranty is not present (as 
noted in the syntax, it is optional), then there is no reason that the 
extension could not be processed by the computer. Therefore, the warranty 
extension is NOT "only aimed for human interpretation...".  This may be 
irrelevant to the point of automated certificate path validation, because 
the extension is non-critical.

3 - There is no security on the information placed at the tcURL parameter
since no hash of the terms and conditions is being used. These conditions
could change overtime and relying parties would not be able to demonstrate
that they have changed.

[Alice]
It seems to me that the time stamp on the certificate would suffice to place
the warranty in a point of time at which the specified terms and conditions
applied; there is no need for the extension to demonstrate that as this is
covered by the certificate itself.  This is no different from the
paper-based world in that if an insurance policy changes its terms, it
cannot do so retroactively to the detriment of clients who have paid for a
specific coverage, unless it notified the clients and compensates them
accordingly.

[Denis] The problem is that the CA could change the policy and the relying
party will be unable to demonstrate that the policy has changed. A
time-stamp token over the certificate would not help. A time-stamp token
over the T&C would help, but the relying party does not necessarily have
access to one TSU. The hash approach is much simpler.

[AS2] A hash function on the T&C?

4 - Is the "Relying party Agreement" a document to signed by the parties or
not ? This should be said.

[Alice]
Use of the term "Relying Party Agreement" is no different from its normal
usage, just as "Certificate Policy" is used in the same context without any
change to the meaning from normal usage, as per RFC 2527 and its successor.
In other words, defining the terms, either Relying Party Agreement or
Certificate Policy is not necessary to the understanding of this extension.

[Denis] The term "Relying Party Agreement" is confusing. Use a wording like
"Terms and Conditions for Relying parties" which does not imply that there
is an agreement signed but that unilaterally the CA provides terms and
conditions. Relying parties may like them or not. If they disagree with
them, then this is still "Terms and Conditions for Relying parties".

[AS2] Maybe so, but the RP has the option of not using or relying on the 
certificate. As I said before, this is normal terminology, and should not be 
confusing; it is not being used with a different meaning.

5 - The WarrantyValidityPeriod is insufficient. Usually there is a period to
claim for a compensation which must be made X months or Y days after the
date of the event which created the damage. It is thus not possible to ask
for a warranty during e.g. the whole validity period of the certificate.
Another time period parameter is missing.

[Alice]
This is exactly what the validity period is stating: that the warranty is
valid for a specified time, which is either the validity period of the
certificate, or another, specified time using the parameters as defined in
the I-D.  It is presented and offered this way, so there is no need for
another validity parameter.  If an offeror wanted to specify a time within
which claims could be made, then a shorter time period than the validity of
the certificate can be used.  This is unlike the paper-based world in the
sense that insurance policies are normally of long duration, whereas this
extension is associated with a certificate that normally has a validity of
two-three years.

[Denis] The semantics of the warranty validity period is not defined ! There
is a need to define more precisely what "the warranty validity period" is.
Here is a proposal along my original text. If it does not fit, please
propose an alternative:

" The warranty validity period is a time period to claim for a compensation
which must be made X months or Y days after the date of the event which
created the damage. It is unrelated to the certificate validity period."

[AS2] What if the warranty validity period is indeed the same as the 
certificate validity period? This was the scenario assumed to be most 
likely, as it is stated in s.2.2, and therefore the option was created to 
allow for a reduction in size of the extension by having NULL in warranty 
validity period in the case where it was the same as the certificate 
validity period.  When it is not the same as the certificate validity 
period, then the parameters available for warranty validity period can be used.

6 - The wType offers only two types of warranty: aggregated and per
transaction.

"Aggregated" means that that once the value of the fulfilled claims reaches
the maximum warranty amount, then no further claim will be fulfilled.

"Per transaction" means that each claim is handled independently but no
individual claim can exceed the maximum warranty amount.

Each type has its own problems:

"Aggregated" is like a race where late claimants will get no compensation at
all because they were not "fast enough". It is questionable whether such a
race condition will be acceptable.
It should be understood that aggregation applies to one warranty and one
claimant.  This is analogous to the paper-based world.  When you are covered
by warranty for X product or service, e.g., health insurance, there is often
an upper limit (viz. the "value") up to which claims will be met for each
claimant; i.e., one insured person.
"Per transaction" means that the CA cannot compute the maximum amount of
money that it may have to give away. Which insurance company will ever
insure a risk for which an upper limit cannot be computed ?

[Alice]
The T&C, as noted in section 1, as covered by insurance, will specify the
maximum. The type of warranty selected depends on the nature of the
transactions, the parties to the transactions (e.g., individuals, large
institutions, etc.).

[Denis] What I am asking for is to allow a combination of both types, which
is currently not possible. See below again.

None of these schemes is acceptable. Some combination should be allowed:

    - a maximum amount per transaction, and
    - a maximum amount per certificate with a maximum time period
      to claim for a compensation after the date of the event
      (no race problem implied).

[AS2] You have a good point. We may need some clarification in s.2.2 to 
explain exactly what the currency amount means.  This is clearly stated (and 
obvious) with respect to aggregate, but not so with per-transaction.  It 
should be indicated that there will be a maximum total of per-transaction 
claims, which would be standard practice, and necessary for the ongoing 
health of the CA.  The total warranty offered for per-transaction claims 
could be expressed as a new parameter indicating number of per-transaction 
claims before the maximum would br reached, which would be simple to 
calculate since the per-transaction maximum is stated; e.g., a sub-line 
after the per-transaction type code, number of transactions as a maximum.

7 - The content of the security consideration should be augmented to
indicate the difference between what a computer program can do and a human
being can do with this extension.

[Alice]
I would have thought this to be blindingly obvious.  We would, however, be
quite willing to consider some proposed words to address this, if you do
think it is necessary.

[Denis] If my text proposal related to comment 2 is inserted, then this is
no more needed.

[AS2] Still willing to consider a proposal, but as you can see from my 
response to your comments on point 2, I don't think this is quite right.

8 - The document is not mature enough and its added value is still
questionable.

[Alice]
We believe that it is mature.  Its value may be questionable to those who do
not want to use it, but given that it is (a) proposed as Informational and
(b) always non-critical, surely its availability for use is innocuous for
those that do not want to use it.  For those who do want to use it, and we
have heard from quite a number who do, it will be useful and valuable.  As
in section 1: "When a certificate contains a warranty certificate extension,
the extension MUST be non-critical, ..."

[Denis]
As you can see, we have progressed, but several issues still need to be
addressed.

[AS2] Yes, we have made progress.

Denis
 

> File(s) can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-pkix-warranty-extn-03.txt
> 







From owner-ietf@ietf.org  Tue Aug 26 10:28: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 KAA08046
	for <ietf-web-archive@odin.ietf.org>; Tue, 26 Aug 2003 10:28:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19regH-0006g9-DL
	for ietf-list@asgard.ietf.org; Tue, 26 Aug 2003 10:20:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rdPF-0001GY-0v
	for ietf@asgard.ietf.org; Tue, 26 Aug 2003 08:58: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 IAA02110
	for <ietf@ietf.org>; Tue, 26 Aug 2003 08:58:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rdPE-0000Oy-00
	for ietf@ietf.org; Tue, 26 Aug 2003 08:58:40 -0400
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rdPD-0000OW-00
	for ietf@ietf.org; Tue, 26 Aug 2003 08:58:39 -0400
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA13813;
	Tue, 26 Aug 2003 08:58:08 -0400 (EDT)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA07755;
	Tue, 26 Aug 2003 08:58:08 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <Q2FAV6MG>; Tue, 26 Aug 2003 08:58:08 -0400
Message-ID: <313680C9A886D511A06000204840E1CF070B5D43@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>,
        Karl Auerbach
	 <karl@cavebear.com>
Cc: IETF <ietf@ietf.org>
Subject: RE: ASN.1 (Re: Pretty clear ... SIP)
Date: Tue, 26 Aug 2003 08:58:06 -0400
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

Good points, esp. the references to 2234.

May I also point out that many SIP stacks use automatically generated
parsers from the ABNF description.  These have many, but not all, of
the advantages claimed by ASN.1.  It was a goal of the RFC3261
work to make the ABNF grammar complete enough to use a parser generator.
Strict compliance to 2234 is helpful in this regard.

The proof is in the pudding.  Our experience with interoperability testing
is quite good, and contrary to statements on this thread, most current
systems interoperate with very old SIP devices.  This is more true of
old SIP phones than it is of old proxy servers.  If you use a time line
based comparison (age of spec vs interoperability results), I think you
would find SIP beats the pants off of H.323, which in the first several
years was dismal, but of late is pretty good. 

Also note that SIP is quite compressible, c.f. RFC3320, and the wireless
folks, currently one of the applications most concerned with the 
number of bits on the wire, seem quite content with compressed SIP, and
are not beating the doors down for ASN.1 encoding.

This version of the ASN.1 debate at least is focusing on PER.  The
last one I remember was the Megaco debate, which was BER based.  They
lost that one; the work showed BER encoded ASN.1 was both longer and
slower than text encoded.  With Megaco, you have directly comparable
messages.

Brian

> -----Original Message-----
> From: Harald Tveit Alvestrand [mailto:harald@alvestrand.no]
> Sent: Tuesday, August 26, 2003 2:50 AM
> To: Karl Auerbach
> Cc: IETF
> Subject: ASN.1 (Re: Pretty clear ... SIP)
> 
> 
> Aah.... an ASN.1 firefight!
> It's been a LONG time since we've had one of those, but they 
> used to be a 
> regularly scheduled event on this list.
> 
> I used to have opinions on this debate - for a trip down 
> memory lane, check 
> out the "canonical X.400 vs SMTP debate" on my website (sorry, typing 
> offline at the moment - google will find it).
> 
> One note, however:
> 
> --On 25. august 2003 15:16 -0400 Dean Anderson <dean@av8.com> wrote:
> 
> >> It is certainly true that net telephony and conferencing need
> >> extensibility - but I would suggest that the hooks for 
> extensibility
> >> ought to be concisely defined and placed in specific parts of the
> >> protocol structures (such as the SDP part of today's call 
> establishment
> >> protocols). I see no need to burden the entire protocol 
> representation
> >> under a mutable layer of complexity such as ASN.1 when there is no
> >> reason that can be articulated to require such mutability.
> >
> > ASN.1 is not automatically extensible.  You have to specify 
> where the
> > protocol can be extended.  If you don't use extensions, it should be
> > possible to have an ASN.1 runtime that omits the code to 
> handle them. (One
> > of many possible runtime optimatizations that are possible 
> but rarely seen
> > in practice, except with hand-coded encoders/decoders)
> 
> One warning to those with long memories and strong opinions:
> 
> The way one does extensibility in ASN.1 has changed greatly 
> since the first 
> (1984) versions of ASN.1. Lots of the hard opinions people 
> have here are 
> based on ASN.1(1984) experience, which was what SNMP originally used.
> 
> I have had people tell me that the post-1988 versions of 
> ASN.1 are really 
> nice in this department, but haven't used ASN.1 seriously since 
> approximately 1992 (when PER was just being stabilized).
> So I'm not qualified to say whether they are right or not.
> 
> Aside on complexity: The definition of ABNF, the "formal" 
> language used to 
> define the SIP syntax, RFC 2234, is 14 pages long, and has 
> been blasted by 
> several people as being a too complex tool for proper 
> protocol description.
> 
> I haven't checked the pagecount of the ITU recommendations 
> defining ASN.1 
> recently, but the last time I had one in hand (X.208/88), I'd 
> estimate it 
> as at least 10 times that number of pages.
> 
>                       Harald
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> This message was passed through 
> ietf_censored@carmen.ipv6.cselt.it, which is a sublist of 
> ietf@ietf.org. Not all messages are passed. Decisions on what 
> to pass are made solely by Raffaele D'Albenzio.
> 





From owner-ietf@ietf.org  Tue Aug 26 12:34: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 MAA13579
	for <ietf-web-archive@odin.ietf.org>; Tue, 26 Aug 2003 12:34:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rgdK-0003Xp-7a
	for ietf-list@asgard.ietf.org; Tue, 26 Aug 2003 12:25:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rgcB-0003Ny-Ip
	for ietf@asgard.ietf.org; Tue, 26 Aug 2003 12:24: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 MAA13116
	for <ietf@ietf.org>; Tue, 26 Aug 2003 12:24:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rgcA-00036m-00
	for ietf@ietf.org; Tue, 26 Aug 2003 12:24:14 -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 19rgc8-00036T-00
	for ietf@ietf.org; Tue, 26 Aug 2003 12:24:14 -0400
Received: from cisco.com (171.71.177.238)
  by sj-iport-2.cisco.com with ESMTP; 26 Aug 2003 09:33:23 -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 h7QGNctH011244;
	Tue, 26 Aug 2003 09:23:38 -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 AHL88700;
	Tue, 26 Aug 2003 09:23:35 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id JAA25506; Tue, 26 Aug 2003 09:23:34 -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: <16203.35206.868113.121005@thomasm-u1.cisco.com>
Date: Tue, 26 Aug 2003 09:23:34 -0700 (PDT)
To: Dean Anderson <dean@av8.com>
Cc: Karl Auerbach <karl@cavebear.com>, IETF <ietf@ietf.org>
Subject: Re: Pretty clear ... SIP
In-Reply-To: <Pine.LNX.4.44.0308241726590.24445-100000@vista.av8.net>
References: <Pine.LNX.4.44.0308231831280.13826-100000@npax.cavebear.com>
	<Pine.LNX.4.44.0308241726590.24445-100000@vista.av8.net>
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

Dean Anderson writes:
 > > I find H.323 to be qualitiatively worse, as measured in units of
 > > elegance, than SIP.
 > 
 > I find just the opposite. Now I have to worry about the security of SIP
 > phones, and that they might be used for evesdropping.  H323 and and
 > trusted ASN.1 compilers can go a long way past SIP for ensuring
 > trustability of such devices.

::snort::



From owner-ietf@ietf.org  Tue Aug 26 14:23: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 OAA18465
	for <ietf-web-archive@odin.ietf.org>; Tue, 26 Aug 2003 14:23:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19riPU-00046W-H1
	for ietf-list@asgard.ietf.org; Tue, 26 Aug 2003 14:19:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19riJM-0003qO-Sw
	for ietf@asgard.ietf.org; Tue, 26 Aug 2003 14:12: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 OAA17910
	for <ietf@ietf.org>; Tue, 26 Aug 2003 14:12:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19riJL-0004Ih-00
	for ietf@ietf.org; Tue, 26 Aug 2003 14:12:55 -0400
Received: from evrtwa1-ar8-4-65-021-158.evrtwa1.dsl-verizon.net ([4.65.21.158] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19riJK-0004Ic-00
	for ietf@ietf.org; Tue, 26 Aug 2003 14:12:55 -0400
Received: from eagleswings (127.0.0.1:3820)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S318B0> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 26 Aug 2003 11:12:53 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Robert Honore'" <robert@digi-data.com>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: Solving the right problems ...
Date: Tue, 26 Aug 2003 11:11:45 -0700
Message-ID: <03f101c36bfd$82850740$63124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <3F4B9B88.3070305@digi-data.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Robert Honore wrote:
> Perhaps this proposal really requires another working group or=20
> something. =20

To be clear, I was not recommending where the work get done, that is why =
it
was sent to the IETF list. I only cc'd the IPv6 list because it ties =
into
the recent discussion. In fact it is not clear to me where this work =
belongs
because the IETF area structure is very focused around the current =
layers.
It is also not clear that a new area is required to create a new layer, =
but
maybe that would help focus work in both defining how such a layer would
interact both up and down, as well as name space and interaction =
protocols
along the lines of HIP/DHT/...=20

The only thing that was clear to me was that the efforts to change the
behavior of lower layers only makes them more complex while creating
unintended side effects. At the same time, an optional layer between app =
&
transport could provide the consistency that some apps require, without
changing the widely deployed and well refined lower layers.

Tony




From owner-ietf@ietf.org  Tue Aug 26 15:34: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 PAA29104
	for <ietf-web-archive@odin.ietf.org>; Tue, 26 Aug 2003 15:34:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rjTO-0003b1-8u
	for ietf-list@asgard.ietf.org; Tue, 26 Aug 2003 15:27:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rjT0-0003Wb-Lf
	for ietf@asgard.ietf.org; Tue, 26 Aug 2003 15:26: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 PAA27754
	for <ietf@ietf.org>; Tue, 26 Aug 2003 15:26:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rjSz-00076l-00
	for ietf@ietf.org; Tue, 26 Aug 2003 15:26:57 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rjSy-00076i-00
	for ietf@ietf.org; Tue, 26 Aug 2003 15:26:56 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 1324514085; Tue, 26 Aug 2003 15:26:57 -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 10344-14; Tue, 26 Aug 2003 15:26:56 -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 551AF13FF6; Tue, 26 Aug 2003 15:26:56 -0400 (EDT)
Date: Tue, 26 Aug 2003 15:26:55 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Tony Hain" <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Solving the right problems ...
Message-Id: <20030826152655.42463ecb.moore@cs.utk.edu>
In-Reply-To: <03f101c36bfd$82850740$63124104@eagleswings>
References: <3F4B9B88.3070305@digi-data.com>
	<03f101c36bfd$82850740$63124104@eagleswings>
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 the same time, an optional layer between app &
> transport could provide the consistency that some apps require,
> without changing the widely deployed and well refined lower layers.

why you keep insisting that this layer belongs between apps and
transport, when doing so would clearly require considerable complexity
to restore functionality that already exists at layer 4, completely
eludes me.



From owner-ietf@ietf.org  Tue Aug 26 19: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 TAA21332
	for <ietf-web-archive@odin.ietf.org>; Tue, 26 Aug 2003 19:25:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rn1u-0006kc-6d
	for ietf-list@asgard.ietf.org; Tue, 26 Aug 2003 19:15:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rn1P-0006hA-SF
	for ietf@asgard.ietf.org; Tue, 26 Aug 2003 19:14: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 TAA20276
	for <ietf@ietf.org>; Tue, 26 Aug 2003 19:14:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rn1N-0004V0-00
	for ietf@ietf.org; Tue, 26 Aug 2003 19:14:41 -0400
Received: from mbt-nis-server.cajunnet.com ([209.62.192.2] helo=mobiletel2.mobiletel.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rn1M-0004Us-00
	for ietf@ietf.org; Tue, 26 Aug 2003 19:14:40 -0400
Received: from Ynusaoz (thibras1-port194.cajunnet.com [209.62.197.194])
	by mobiletel2.mobiletel.com (8.11.6/8.11.6) with SMTP id h7QNAcH26273
	for <ietf@ietf.org.>; Tue, 26 Aug 2003 18:10:38 -0500
Date: Tue, 26 Aug 2003 18:10:38 -0500
Message-Id: <200308262310.h7QNAcH26273@mobiletel2.mobiletel.com>
From: vcerf <vcerf@MCI.NET>
To: ietf@ietf.org
Subject:  
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=D1cRf050VYF4IO
Sender: owner-ietf@ietf.org
Precedence: bulk

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

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

--D1cRf050VYF4IO
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: Like.scr, Content-Type: audio/x-wav]
The attachment file in the message has been removed by eManager.

--D1cRf050VYF4IO

Content-Type: application/octet-stream;
	name=whit5sm[1].jpg
Content-Transfer-Encoding: base64
Content-ID: <A919fCjB52xw4W691s>

/9j/4AAQSkZJRgABAgEASABIAAD/7QCqUGhvdG9zaG9wIDMuMAA4QklNA+0AAAAAABAASAAA
AAEAAQBIAAAAAQABOEJJTQPzAAAAAAAIAAAAAAAAAAA4QklNJxAAAAAAAAoAAQAAAAAAAAAC
OEJJTQP0AAAAAAASADUAAAABAC0AAAAGAAAAAAABOEJJTQP3AAAAAAAcAAD/////////////
////////////////A+gAADhCSU0EBgAAAAAAAgAC/+4ADkFkb2JlAGSAAAAAAP/bAEMADAgI
CAkIDAkJDBELCgsRFQ8MDA8VGBMTFRMTGBEMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwM
DAwMDAwMDP/AAAsIAOkAkAEBEQD/xACiAAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsQ
AAEEAQMCBAIFBwYIBQMMMwEAAhEDBCESMQVBUWETInGBMgYUkaGxQiMkFVLBYjM0coLRQwcl
klPw4fFjczUWorKDJkSTVGRFwqN0NhfSVeJl8rOEw9N14/NGJ5SkhbSVxNTk9KW1xdXl9VZm
doaWprbG1ub2N0dXZ3eHl6e3x9fn9//dAAQAEv/aAAgBAQAAPwDn3NOsdlAyNCoEaz4p4kfD
QeKgQCSfBKJjt4pFsgDsFED3eY0Sewg6f70xbBk9/wCKc1naSPmq1lbgIdpPCrWNIafH+9U7
TrAQioFNqnbyF//QwXzJ7j8VAiQNoQoM+YJTFpnj4JnAjjkp/MjQJ3Nk/HkKIrJP5Fq4HTPW
g2FoZxucYBP7rf311GH9VulW1mt7XufAAe3Qg/nOb9JTs+pvS63hoLosO1rnu2hp7S1rVx/1
h6Hb03JNVo3HlrhwR+8Fz9rZnyVG6uD+WEB3CgfBMnbyv//Rw3AnU9+EAug8wmncfMDlScZa
ADEpthjXny4TFxIide8KJ8EXGYDZAntC6DE6nju6sWBodThfoKwP5Pte9v7z32bl1vTM6mwu
FY0HPd38n+ytC3fbWQBDwZYDwSPzVifWrp7OodN9SvR9IkHkidXVuXlWU303uadC0/BULSZK
rOMIZJURypNMkL//0sC0RKCdT+VLWJ01S00/e7eClukAHhQII0HZJxJ9oU/WdSx1nfTjx8VL
pWcaWWUV41b73uc6yyxrnvJiWittb69q6jplV/Uej/bqqSMip/o2UBzhHp+x30d3010HRsXJ
xmeta1lBePfRW7eDHFvtbX7/AOt/nrSrqp37gDstBDhyCDzvbK8n+uPTx03q+TjiSyd1bjpL
Xe5pXMWu1QXoZTJ2nUL/08Cwul0j4qAYOfHsU20QQR8iphjRHwTBoGs68FRLdCIlD9sx38Fc
w6mWPDHAEHUA+Pmpuq+yZjsumsFjhtsguEfymx9Lctv6rO6rh49mPZhvrZk2+rVe920Brv32
sPqLpG/tKo/Y8ktuDjvrymQC5k+5lg/0jVsw6qtobw2PdxEfnLjf8Y/Sm5uGzqFTD6+O0i0x
/g/zf5Ptc5eVXAg+CAZUJ/2JpUmcr//UxLQJkaIZhp7JnTqRynZrBcnfG0EfMKJDQJjRB/OB
jVW6iWtkaOWh04BtwfdqxvvcCdJA9vt/rK/XVl5b2VBztthDRtcA0fR+lu93t/dXVdLrsooZ
VY/1W1AtBPMQeVr0H1CI1HdV+rY4+zWVkgV2CATxuP5rh+65eHfWPp78HqFtZZtYXEtPb4LF
I1USE0J2DUL/1ce6sRzE/igEwOQCFEPafOUVoBgkD5KLiB8FEnSSFB0QI76ozZJJboOy2enY
oLTLjH53iUEZFmJmssLoFTwWs5H9Vdf0fIsvoD3/AE7HE7R2H7v+atzFfBG0EAH3Smyus9Ca
84eTl0OscNcfcHuI4/mmb3LivrT9Srepj1OnWsuLZdUy07LA0/4Ik+yxv7nqelYvMepdNzum
5LsXOpfj3N/NeCJH7zf3m/1VTdKb8E7RqF//1sd7i7SNR2VDJscwSNZ4QqrHHWNedFbFpIEj
+JTFzmg+ag5xjQSI4+aed0DbHirVBDNSN0xE6T5LfxGerWGY52kN9wiDrz9L6Wz95QyOksr3
ZWdeyitoBZW7+deP+CpH6T3v/OcrGB1W+m1lOOxtDSBDnHc6J/OaParGRbmZDHHLyHW1sjcy
djTPfbXtUOlVY7Mqx+PjNxyK3OFke9/5247QWrX+3vN7WY5JLYdZp4jdsGitdS6Ng9b6ecPq
dYsa4EseP5ypx/wlL/zP6q8Q670fJ6L1XI6dkavodo8cOYRurtb/AMYxZw1U2jUaL//XxbY9
zjoPGVQvexxGsHwUKWguInjlEOg0HglqWye3yTkkATMwiVCTJ1jhJ1zPUNo1FP0D2Jbrtj+W
5dF9VrMW7Nf9qt9JmNQbLT5k7D7tfdudtVnr19NxH2ejYHCGNdq90f4W15+j9L6CzMVjq9pk
7x+cNSrtl7mOc24GQQHAGN/9ZazXnD6bZmuG97K3NbOkl5gN/wA9SwK3U1tobLMixu+wgzH8
ouW5huiva4lzh7p5Oq5H/GR9WT1PHb1jDaXZWKzbkViJfS33b2/vWUf+ev6i8rDagfcST5aL
oeidM+rWVii/Oy76LQ5weyutzw1o+jY5/pFnu/rL/9Dms27aIB1OqzX2lxn71Oq8NPx7o5ud
tkcaKYvJaZ4Kb1h5aKTLi+Kqv5x52gfFXrcdgqLA2Ksdsu8S8j2t/wCluV3HopxKQ72veWzY
7UmQd0ItbrLrC6wj1XDQeA/NbojYtFj7C1oDnQXciIH5ytYFFmWW22AF5G8gDQS7z/kLT+sI
Zj9MrZAj169D4Nmztt/dVfpOQMi95aNKzLnHUlxGi3ar6ha0gxXaCJaefuR8IB5LnAhjXxXP
cfvLwzr7G19e6hj1MDK2ZVwZWOAA9w2rqfqydn1O6kBy5uRp/wBbav/R4zNtd6uwwBH5VVnX
4piT2+RRm2HbB4CI13tOsiFAuLiGt1J0lbOLjNwaftN3LGF7u+v5qT/teTi1VVgg3u3WuGrh
pvVzp+LbZY2t1xvqYA6z1AQ5rh9Bn0vo/wAixaeLiC3IeH6MYTJB1E/4MI3TqSyrLySyQGua
088A9ytvomC+uikv5LGankAiVW+uY24NPuArF1c+AJPptJ/d+nuQOn10Y+6r1C5lRLXNZ9Bz
o/SONh2+r/YWnRm9PrY2rHAsa0wGgkgfcCr2B1Cu8hrrGNcJAZBGg/rLx/6+YYwvrfnsGgts
F7fhaBb/ANW5y2fqy9jvqh1Rp5DL9vx9P/zFf//S4bLtLrCTz4Ku2whEEESnETCPXTbYRUzb
vdptLmtdPhDnBXelYTm5bvtbHVimZa4Ee4CXD3futXQYttJA9Vu4c2E9iR/0tjXbFN1FdbXX
Md6e0eyPzY4/tIuKdmC+0OG60Gwu7wB7P7W1BwWvqxBLiLLATwTq7WXO3bvzluik09JNFZ2l
zS1xPiR7v+qWo3Irx6yC72siQ0HSB/nLnPrR1HJzH1YVtVdeHdNjRednqOYPZueT7K27mv2f
4RZmFb12uu3LZXj9UxcT220YxL9h0Pqsaz0nXMr3e/0f0S6PA6xkWUVkipstnZZjXVtHfb9o
qdcz/orXxr22GLcNrXH6L2w9jiOdln5rv5FjKl5r/jTsxn/WmNri9uNSHkEDU73jsfzHNUfq
1mdGr6LfjZdmSHWG0WehTv2teA3c62fT+iv/0+CyHS4nzQCSNVJj5bC1uiYRzcunGYfTtyLW
Uss5LWkG261oP53pN9i6/q/1f+reD0LLdVQ11rWba3El9jrJG1rd373+EXMYGRk9RooO6x2R
iTTfbyPR9oxGWud9K1v6Wlv5/orTa5tdjaGuMwXHx/e939ZysOaLCzHY6W5D2tA7jedrmf5q
tdTfdXUMb02MZbDawHTDR5bWqfTQLcltensG4jtp8lr5WZXjtbW6vdL4E8DTcN39ZWgWOMlo
O4jUA9u+sIPWOnV9SxPSsqbY+qXVB0wXEbdj/wA7a5rlzfTfqb1oXPsy8p/S7nwcVmO4cAem
1tttYeytu3/Rep/LW50/o3VsW4Uuzctt1kmu6y1uVjuLRrU9vp0W0v2/6Rn9Sxa2Jm5Flb6L
Ybk0HZbWdRu+lP7zq3t99a88/wAZWJhu6zhZtB25OZX+s1vP51RFVdnu/fZ7P+to31ZxXj6s
dd3aOrZkbuOzOy//1PP3EoZbJha/1fwKMn7Xk2BtowKfVZjuMeq9x2Vs/lsZ/OPr/wAIrH1W
z8u/60Nz7aftVtbXufVUAwwGeh+jaxuxmxv0VvdT6z0ywi9gecd0NrDxsf6hO072O/m9jv0b
3uWRg537N6m5uVUyvFyRssoA9rNd1du/3ep7vf6+9dEemUOm+gyHs2tM6sH0t0/nKhi02Dr+
FU8khhss47sY7b/0lZ6857epYnqAgbHiDAJPtf8A9FF+rz92U5+0aDUnnXTT70bP6kcaizLO
I7qNYy/01TC5jgyHe5jm7vo7V3PSP2fdg05eCGmjJY19bwNS0jh353tRMqpzD69cy0e9o7j/
AMkqGVHtsZq0jc3uBrtc0oBNjchjy+HNjcDw5v8A5JqzqLabOpW2MeW5VG6qys676530v/60
4/8Aba80+vHUP2j9ZrWVmGYwbjtM6Sz3W/8Agrnra+q19j/qz1gXOLrHU3gknmKe/wDmr//V
8+eY+Ceum+6TUxzwOSASP85dl9QGWY90jaRkNdY5xA3/AKN3p+k3cfdv3JvqbhnAv6nmZO9m
Uxxobj7SHkgi539Xc4VrU6HZnY9GQcquq4ueXXMaC2wBzuLG2N23NVbq2H0nOYMfo2Q1uU8F
zsKqxrmaDfYHUP3Nod/xPpoLrMlzXZVjfszAdrnUy9kDTc5tY31cbXstQuj5n2n6wVhtjbNm
Pc7eDubJADiQidYqe7quO57gSA6JMwDDdv4o3SchuJmAvI9O0bXHWAfzSVqdMudVYQ8EFt59
QHwePbLf7Dlu/VK9tF3UekAFlWNaL8cO0ivI3PdW3+Qy9ln/AG4ujOoWT1GplA3lwrrHM6Bc
7nfWroNUNuy2V7HQHme37uwF9i5vr3166bh3P/Y5GbfawAXatrrkf2XWuXnzbHvvFjnS5zpc
93ifpOMrt/qzkNs6H1ZzZANWR+NQbP8AaX//1vPHHcOdOF0fTuldT+sDmGx3oYjGtY3YNrA1
o2j0qmw1zv8ASOXadP8AqhhU4tFV4LziuL6btWWe76THOrd76935q1jhNbq0ETrvmZ+LiqGf
0PpWYfUysdtzwNpc6eB+aQ2GrmLa8no3VDhdJxa3th1jG2bmgMfta7bYHNf+jerb8TquS83W
4jMfLI1vxcj3nT/C12s9G3/txY/Q2Ws+tdptaG2DFu3gN2ToB7mO9rd3730Fd6pY1nVMZzw6
pzQdtbiHTMfRc327dFcysj6vUVubl21Y9g0cyS58+Pp173f9FZV31z6bUfabcl7YZ6jWhosY
33VmwW+/1aXt9n76y8H66dSwuvX9Vxg+2q0en6F54p3bq6nPb/olu9U/xu9StpFPS8duHcB7
7rCLT8KWfQb/AFn71xfVOt9X6ld6+fm25Nn8pxAA/daxsNaqTQ65250NnRzjr/1RWh0XBxcz
NqqtY57HFwsLdAAB7HaLuR9VvqkK2l2Nawubo5rnEmPzxXfub/0VWrwsPpfTc+qiSH41ska7
nEOh3Ltv6P01/9fj/q7iY+Z1Kum9hsY4wGAfSPhp+avWcejHx2NZW1oDRtAAgR4e1WnPmS7m
NAfvUnPaWAcN00CoZRcGPcNWgavZq9v9n89czmXm3qbRe4nZVuqyMdheHhzhptb9C72IuPg3
ZDv53Nxn8h7yxzT/AF69vsVPEeMbqgzOqW12YzqrqKHCWvtLi0bmV+93obq/5z8//BpurMx8
wMdjMLbK3bmSC2I4/nQxv+asXqn1TzsqcvFfjxTUHZhNh3SCTZkW+30+/u9J65a53pWms7Hl
hID28O80N1txb+cGGQOYPl/KU24mU66ukM22X7fTDobIf9B258ez+UomkxZue0Gs6tJ1Jnb7
Nv0kxawNrIsB3fSaOW691qdD6j0zpvV25V/rXY9W7Z6e0OdI2+9rv5J/eXS5n+MPo7vTOL0x
77KhDX3PaAZ+luZtsUsTqY6v0zNzrK24wLLa201atEVlzfpfvbvcv//QyfqGK2Ztn6MPvewe
m4idgJ95H7u795d+/dVs4AmCANfBTuZcfezWBwOVGrIGhcC0CA8OHBjx1VXqDBc77Oxu3ePf
cHbIB7sd+c9Sow9lPptcA0nhsmT3J/rfvrL+st1uD0XKtxQS7Ztc9s+1r/a+zc33fRXFfV+0
3WZPUbrC41MbWzU+0H2j+T7WtXQWZDMcOeaoprbrY0lzi6fpP3e33Ocqmf8AW+jp+BkYRxvW
+3VuqcJDS0OGzcXbSuIdnR9obRUymrJgFkbtrWndtY96A7IudSylzyamEuYzsCfpOSsNrwHW
OLtoa0bjMNj2tH8lDSCSccrq/qy8Ho2aw6gMuI8v0fK//9G99UumDp2XdjhoeQ1gc+PcX6l/
u/dXTZTRtqEQ4+SbaXVOIIYeASD2VLDex11mLfLXxuEiQZKNl4wqxnOcz1WVh1gYBPGpDWrC
b9Zvq1UC59t9M6lr6rGmf81Vc/62/VfJodj2ZAsqsbssrc1wBaeRwuMb1TpvRc+13S4zcLIb
tvovESP3WWj3e39/ao5v1nOVRXgYuK3EodYw2Hc57nBpDm17n/Rr3Kt19vsYdgDi7VwnXThY
+0+HgrFGHda2pzWE73PaPPYN7v8Aoqxj9Kzc19dVbCDb6LGl0ge5rnNO4/1VpV/UvP8Asrcl
zSQ6tlkQRt9xbex8+32Vt9Rc7tZPtJJ+GkJjtgQIP5xJ5Tare6VlfZuk3ggzfuY0gTyNq//S
6T6uPde7JyAIY+5wHj7S5nitLqTXek1w/NcoUE/Y+CBwD4/uoWZjh91TwNjmcHy/rKWRdcMV
zWw6x4LWA8bo7rkMnI+u2LX+ks6cWsGpc8NO0fybHLjurdd6lYSzIyKbPKgAiPDdHuXP2PL3
SrFWuXTAmSzT7l2VXSWdQcTYwvFTSQzxBBZ/nK7hfVbpd36WuuXbGEAmdhYfa5rR+9t9+9a9
P1ext7ttbQ4k2N0+iXA+rG/8560a+m0UjZRW1rm6SBAgfRVXq5GD9XuqZEatosDZEmXj02/+
fF462qwAk6N49uqi5uxxAg6cc6qLtpdoI0117qyy63bXRuIZ3b85X//T6f6rBpwHPaIJe6fm
S7/vy1MwE0eOoQsVodjvY7g6jtzwhOyam3NoyfZZ/g3HUOHk7+Ssr6x5nSaKKmdTDfTlzmBz
iAfzddrm+1edfWH6y9IumjpODS0iZyTX4/6Jrvc7+vauXJJMkyVKCe3xVvpzN/UMduo97fuH
uXpn1brDn5Dm7nGAxjg1zh/a9P6K3MWl4aW2U+keILQDorDK2sd7R4zAVo4xdJbqQO3K5D/G
HkkdA+xYxDrL72i5rHAuDGjd7mMLnfzm1ec1YgNcve3c0kFplhgfRduP0kPLpwq2sLXl13Nj
R9H4ByF6X23Ld9kpLGky2oHdtH9YqEOF4a/6TXQfkV//1On+p5DujMcDJJ/g3utq1m+vaeCo
VM21gd41TXVNfG4fRO5p7yvIf8Z+Z9o+sX2VplmDU2sgcb3fprf+rY1ceGnsnAPJlWKse17X
OqktaDujnb3JWl9XMRzs59rwf0DSB/Wd7P8AySsZtbr8+22my6l1ADKfSBExz+nlm33I9f1h
+t+A3TqjvTjQXltp/wDBmvUX/Xz6zEQ7qREafo662/iGLPzfrT1jMG3Jzsm9n7r7CGn4sZ7V
nPzr3+0GGjQDUoRutdy4/kTNY9/EkpAua4gEjsYU6DFrPDcF/9XuejdOHTOn04Tq7LCxomxr
Y1iPo7n/APVK+Q0ABtTyNNYEiUMsdueBXZDdGmBBn+0iigObLZYeweO/9WV5/m/4oL87Kty8
jrIdde82WO+znVzjuP8A2oQh/iVbB/yvz/3X/wDfhL/xlW/+W/8A7L/+p0en/E/6TXMHVyA5
paS3Hgw7953re5amB/i2xsPEsqOa6y+wlxvNYGsbK/ZvP0P6yoXf4qsm5xNnXbIPZtDW/wDU
2Ksf8S2M8y/q9hP/ABI/9KpD/Ephaz1Ww/8AWW/+lE3/AIyeF/5bW/8AbLf/AEohv/xL4zXe
3qNzxpqKmD482J2/4mMOYOfkgePpVf8ApVWMb/FBgUB7vtuS90QBsrbPw9z1X/8AGaw9w3Z2
T7vCurn/ALcU6f8AE7hNsa/7bkgAzDmVf+TX/9b1FJJUuo59+Ixz2UhzGATY920FzjtZTUxj
bbbrnu9u3YnwcnNffZj5ldbLGV12g1EnSwvb6T2u3fpK3Vfv/pFd8u6oZ+I6yx2Va+6yqqoC
nGx3OY71JcbLZrfX6ljm+myrd/N+9IPyMLKox7bTkU5JLK3PA9Vjmsdb73M2ttp2V/T2b2P/
ANIr5Wd1XrOP02uNjsnLdHo4lUGxxJ2smfbVXu/wtiB0rqOdkVsvy30Nxod6l4lrH2OPsqw3
WFu/Gob7PtT/AOlv/mf0a0srIpxsay++wVVVtJdYe3h/Wd+41ZHSMvqP2ItqFufbZY57Lchw
Yytjv5uu3IYz9M9v03txabfTe/0VbfhdYsaHnqXo2gghlVLDVoRuY5t3qXv3N9v8/WtLRC25
BJ/SNAnQAdkRJf/X9S7JQhXZGPjs35FrKWfvWODR97yFi0dVx+pXMzaWWZYqJ+wYzAds6s+2
ZFjgKad7f5n1X/oqP8H6tqNZ0nqdj22OyK915Ls4e8AhumNRT6bq3/Z6Jt3Ne9n2ix/qWf6J
Bd9VAa72My9n2p4N0VgSwBwbTsrdW3azd7P8H/wfrv8AWVr9g+nY+3Gzsul9tRrP6T1G7iS7
7Q1l4sYyz/i9jFZwOl1YbQ51j8i8N2etaSTBO5zWA/Q3u9z/AN//AAiln0Z97qRiZf2RjXE5
H6MWOe2PoVuf7aX7vz9liysr6reteXtvD6nOBfVaHGW7f0m+1jm3X2X2/wA862z+Z/V/5tTy
uhW5d72dQqx+o4dra62ssmoUsad1raaGMt3eo7/hWf6L+bRc7obup+uzPex1DQW4FDQfTrOz
YzJvZ/h8hjz+j/wVH+D/AEn6RQcz6xVsxMWqqv0q6wy+5t3vcWhrGa20/o6n+6yzYy6//q0+
Cz6x00215JqdYHO9K179zG1ifS2j+ftte3+efkWVJdByuuZjKrMz0249bIda3V2RZHvsr27a
6MWt381t9T7R/wAX/ObAT9wkF//Q9SEQlKHdRRcNt9TLQJgPaHDXR30lPQAAaAduySq2dTw2
Z9fTdxfl2tL/AE2Au2MaJ9S9w9tLPzWb/po9eRXa+2tkl1DgyyQQNxa2z2uPtf7Ht+glkZOP
i0PyMmxtNNYl9jyGtA+JSoyG5FLbmBzWPEt3tLXROjtjvc3d/KQsvKOJGRYQMZo2vaGl1hse
6uujZB27fdteot6pieoymwvossMMbcx1e4/use8ek539V6tpEgAkmABJJWW8/tmza0/5KZo9
w4yXD8xjv+4df+E/7lfQ/mP53UEAADSOAEyfukF//9H1KNFz/Ueq52R1T9lYtVrKqngZd1QB
tdWWer+rlxaytm91dNtu71q/+D/RpM631Omy7Dd0591zbBXjGptnpBrgbGsysh7XVtdRVs9W
6uyyu25WKeqdcbkPrzOjv9IENZfjW12NOnuLmXOx7Wt3/R9i0sizIZSXY9Xq3GA2tzg0Ak/S
sf8AuM/P2b/5CxsHpPXenvvdTkY1zsm1llj7GuBA1de1mz3/AEnbavVut/z1q432rHxS/qWR
XZY0ue+xjfTrayZa1rXOe7axn573rJtx7+uZtOVU70cbEfLRYze1xH0d9bnM/Tb/AH/8B/hv
0/6OixT03quBYBg5DbsXbW30ct1j3e02Ovey6X+m6zezZ7PT/R/zaH9m+tr8W1rr8MZD7NwL
mufWGCNtNTNjHM+j/OXfaHp/sn1hziMXqbsavDLWeucfc51jh7rGM9Xb6Ld7fp/uf8Itv4qv
k4GFlPa/Jpba5ggbhIg67XN+i9v9dHgAAAQBoAOITjhMnESkOy//0vRup5OZRjbcCn18y47K
GukVtcf8NkP/ADKam+//AIT+arS6b09uFTDnerkWe6+8iC93J/qs3O9rVblJIoGXnYuFWbMm
wMbEgQS4x+7Wzc93+as7qtmFlZdWLfnCumj9LfiVyX2OmKWWOZufsb9P0K/01v8A1tWftOQK
ScfHZiY1bf53KPpta0d/s7Pe1v8AxrqE9XWOnehXZdmUNc9zaid2wG13FbGWn1PdPtV1r2uG
5hDge4Mj8FV6h1OvBrn0333O/m6Kx7nE6N979tbP7TkQZ2IcZ2Sbq/Rrn1LA4FrSz+cG/wDk
LPPVOpZW1/S6K3VuIg3bwC3u99jdrKfb9Gtv2i39+utaGTnYmLbTVdYGWZLi2ln5ziBve7b+
4xv85Z9BiIzIx3kNZaxx8A4E/lU9E/dMF//T9RS1SSULrfSqfZsdZsBOysbnOj81jf3li29H
zbnnKe0evc+RQXnZXMn1cu1pFuX6P+CxqfTx2fmf9yFN/wBX7aGMZgurm3c7NvuLhZY47QzW
jbto/wC69L8f/B/y0J3R+uX041WRk0iukk21NLy17vb6bt22tzKadv6HH/659p9VGwehGvNs
yM6ujJ27m41ka1sdt9rKXM9tljv5++y+66xXL68Xp7fXxMEWZDzsrZQxrS4u/wBJYAGVVe39
JbYs+/pHU8h7br7W2Zd3tL/8BiV8u+y47v6TkO/01/5/6R/6Ov0EK3oWXZU7Hx6mY9WMQcay
2z1L7rGn+dvs2WNoq/wza2fzl/8AOen9BXj/AM5PUftGM2ltIFQL3Pebe5tPpVM/N9mz2fpF
njo/WBScm8V5HUr9rXuJY7ZP/DZFb2VYtTv8Di4vq2ItFHU8XJrF3TqMuuvY12XUyplhcGF1
mRXVu/Ot9Ov/AAOz+cRWZ/1ksvrtHThViPL91L3M9cBv80Xu9b0mev8A2/R/lovT+sdRtgdS
6Xfgl+te2Lxq4tDLDjb/AE37Nr3+psYtVf/U9RSTJ0k4T+CbxSSHKXZJMkl2STpBf//Z
--D1cRf050VYF4IO--



From owner-ietf@ietf.org  Wed Aug 27 03:50: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 DAA02799
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 03:50:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rusf-0005qk-Nd
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 03:38:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rusB-0005nt-L2
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 03:37: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 DAA01740
	for <ietf@ietf.org>; Wed, 27 Aug 2003 03:37:37 -0400 (EDT)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rus7-00004s-00
	for ietf@ietf.org; Wed, 27 Aug 2003 03:37:39 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rus5-00004p-00
	for ietf@ietf.org; Wed, 27 Aug 2003 03:37:38 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h7R7bZB19302
	for <ietf@ietf.org>; Wed, 27 Aug 2003 10:37:37 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T644f6391a3ac158f21083@esvir01nok.ntc.nokia.com>;
 Wed, 27 Aug 2003 10:37:35 +0300
Received: from esebe007.NOE.Nokia.com ([172.21.138.47]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 27 Aug 2003 10:37:35 +0300
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebe007.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 27 Aug 2003 10:37:34 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Solving the right problems ...
Date: Wed, 27 Aug 2003 10:37:34 +0300
Message-ID: <DADF50F5EC506B41A0F375ABEB320636A8B2B3@esebe023.ntc.nokia.com>
Thread-Topic: Solving the right problems ...
Thread-Index: AcNr/wN22GQCvWYeRu+JsvvT4vrWugAbs6OA
To: <alh-ietf@tndh.net>, <robert@digi-data.com>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
X-OriginalArrivalTime: 27 Aug 2003 07:37:34.0854 (UTC) FILETIME=[14DA0260:01C36C6E]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Tony,

A very quick question about your idea.  Does this layer have a=20
protocol / interface to other elements on the network? Or are
you proposing something more like an abstract API?

thanks,
John

> -----Original Message-----
> From: ext Tony Hain [mailto:alh-ietf@tndh.net]
> Sent: 26 August, 2003 21:12
> To: 'Robert Honore'
> Cc: ietf@ietf.org; ipng@sunroof.eng.sun.com
> Subject: RE: Solving the right problems ...
>=20
>=20
> Robert Honore wrote:
> > Perhaps this proposal really requires another working group or=20
> > something. =20
>=20
> To be clear, I was not recommending where the work get done, that is =
why it
> was sent to the IETF list. I only cc'd the IPv6 list because it ties =
into
> the recent discussion. In fact it is not clear to me where this work =
belongs
> because the IETF area structure is very focused around the current =
layers.
> It is also not clear that a new area is required to create a new =
layer, but
> maybe that would help focus work in both defining how such a layer =
would
> interact both up and down, as well as name space and interaction =
protocols
> along the lines of HIP/DHT/...=20
>=20
> The only thing that was clear to me was that the efforts to change the
> behavior of lower layers only makes them more complex while creating
> unintended side effects. At the same time, an optional layer between =
app &
> transport could provide the consistency that some apps require, =
without
> changing the widely deployed and well refined lower layers.
>=20
> Tony
>=20
>=20
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------
>=20



From owner-ietf@ietf.org  Wed Aug 27 07:30: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 HAA17872
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 07:30:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ryKV-0006G9-G8
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 07:19:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ryKC-0006Db-LS
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 07:18: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 HAA17094
	for <ietf@ietf.org>; Wed, 27 Aug 2003 07:18:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ryK9-0003W2-00
	for ietf@ietf.org; Wed, 27 Aug 2003 07:18:49 -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 19ryK9-0003Vz-00
	for ietf@ietf.org; Wed, 27 Aug 2003 07:18:49 -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 AFFD57F4C;
	Wed, 27 Aug 2003 13:18:46 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: <alh-ietf@tndh.net>, <ietf@ietf.org>
Cc: <ipng@sunroof.eng.sun.com>
Subject: RE: Solving the right problems ...
Date: Wed, 27 Aug 2003 13:18:38 +0200
Organization: Unfix
Message-ID: <002001c36c8c$f7426250$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

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

Tony Hain wrote:

> Mobile IP, and the multi6 DHT work are attempts to mitigate it through
> slight of hand at the IP layer, while SCTP attempts to mask the =
topology
> reality in the transport layer. (These are probably not the only =
examples,
> but they are the ones that come to mind this morning.) Yet none of =
these
> really do the job in all cases.

I totally agree with your current insight that we need to seperate
the routing from the host identifier. IMHO every host should have
one globally unique ID and could have multiple transports, even if
those are IPv4, IPv6, IPX or whatever based and going over multiple
links or not. Though we should limit to IP based protocols to not
make it too complicated. Such a mechanism could solve problems for:
"site-locals" constructions, multihoming, mobile-ip without hindering
the size of the routing table as people could continue to use current
routing, thus TLA based and fully aggregated to the TLA level in the =
GRT.

I've been looking into this since the very heated debate about =
site-locals.
As imho there might be a way to solve that in the same problem too.
Though I am still conducting research on that topic. As far as it stands
I think that HIP is going the best way there is. LIN6 is flawed as it
won't scale and can't be deployed easily. Next to those I got my
own odd idea and I will probably work it out and implement it as a proof
of concept. Though timing on when and how may be completely unknown.

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/

iQA/AwUBP0yTjimqKFIzPnwjEQJ4bgCcCoFKvXdeIWGUCyBb7RG8OVudWzUAn2LE
/vVwNICKx7S74eza85dhxItX
=3DBvT1
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Wed Aug 27 11:21: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 LAA08169
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 11:21:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s20U-0007tY-D3
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 11:14:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s1cS-0000hy-9s
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 10:49: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 KAA04225
	for <ietf@ietf.org>; Wed, 27 Aug 2003 10:49:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s1cO-0007Zb-00
	for ietf@ietf.org; Wed, 27 Aug 2003 10:49:52 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s1cN-0007ZU-00
	for ietf@ietf.org; Wed, 27 Aug 2003 10:49:52 -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 h7REo5xS004356;
	Wed, 27 Aug 2003 16:50:06 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Wed, 27 Aug 2003 16:49:46 +0200
Subject: Re: Solving the right problems ...
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <alh-ietf@tndh.net>, <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
To: "Jeroen Massar" <jeroen@unfix.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <002001c36c8c$f7426250$210d640a@unfix.org>
Message-Id: <B3649D46-D89D-11D7-83FB-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, aug 27, 2003, at 13:18 Europe/Amsterdam, Jeroen Massar 
wrote:

> I totally agree with your current insight that we need to seperate
> the routing from the host identifier. IMHO every host should have
> one globally unique ID and could have multiple transports, even if
> those are IPv4, IPv6, IPX or whatever based and going over multiple
> links or not. Though we should limit to IP based protocols to not
> make it too complicated. Such a mechanism could solve problems for:
> "site-locals" constructions, multihoming, mobile-ip without hindering
> the size of the routing table as people could continue to use current
> routing, thus TLA based and fully aggregated to the TLA level in the 
> GRT.

The multi6 wg has been working on locator/identifier separation as a 
way to solve the multihoming in IPv6 problem for a while now.

The problems we're facing (apart from the fact that there are many ways 
to skin this particular cat and everyone has a different preference) is 
that additional mechanisms are needed to get the extra information 
across, and there is a price to be paid in one or more of: additional 
round trips, more dependence on the DNS or something similar to DNS, 
additional per-packet overhead, loss of backward compatibility, 
increased complexity.




From owner-ietf@ietf.org  Wed Aug 27 12:30: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 MAA13772
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 12:30:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s37b-0000jb-JG
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 12:26:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s31y-0000Kf-Ld
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 12:20: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 MAA12852
	for <ietf@ietf.org>; Wed, 27 Aug 2003 12:20:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s31x-0001tM-00
	for ietf@ietf.org; Wed, 27 Aug 2003 12:20:21 -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 19s31w-0001tJ-00
	for ietf@ietf.org; Wed, 27 Aug 2003 12:20:21 -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 52D857F4C;
	Wed, 27 Aug 2003 18:20:19 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: Solving the right problems ...
Date: Wed, 27 Aug 2003 18:20:10 +0200
Organization: Unfix
Message-ID: <00c601c36cb7$16e61be0$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
In-Reply-To: <B3649D46-D89D-11D7-83FB-00039388672E@muada.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

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

Iljitsch van Beijnum [mailto:iljitsch@muada.com] wrote:
 
> On woensdag, aug 27, 2003, at 13:18 Europe/Amsterdam, Jeroen Massar 
> wrote:
> 
> > I totally agree with your current insight that we need to seperate
> > the routing from the host identifier. IMHO every host should have
> > one globally unique ID and could have multiple transports, even if
> > those are IPv4, IPv6, IPX or whatever based and going over multiple
> > links or not. Though we should limit to IP based protocols to not
> > make it too complicated. Such a mechanism could solve problems for:
> > "site-locals" constructions, multihoming, mobile-ip without hindering
> > the size of the routing table as people could continue to use current
> > routing, thus TLA based and fully aggregated to the TLA level in the 
> > GRT.
> 
> The multi6 wg has been working on locator/identifier separation as a 
> way to solve the multihoming in IPv6 problem for a while now.

And ever since they haven't progressed much unfortunatly :(
 
> The problems we're facing (apart from the fact that there are 
> many ways to skin this particular cat and everyone has a different 
> preference) is that additional mechanisms are needed to get the extra
> information across, and there is a price to be paid in one or more of:
> additional round trips, more dependence on the DNS or something similar
> to DNS,

Indeed, one will always have this problem, my current idea relies
on DNS, but if a program currently tries to contact another host
it will usually already do a forward resolve and some apps
(ssh for instance) also like to do a reverse resolve already.
So these shouldn't be much of a problem. In the idea I have I
have also added the possibility to limit these lookups until
a failure occurs.

> additional per-packet overhead,

Not required for my idea.

> loss of backward compatibility, 

I covered that in my idea, by simply adding functionality
and not replacing it in a manner which could cause
unexpected effects on the installed base.
The installed base won't have the benefit

> increased complexity.

Not overcomable, but it should not be noticeble much in
the idea I have. It's also more of a Proof of concept for me
to see if I can get such a mechanism to work and to proof
that such mechanisms are viable. Query me at RIPE next week
if you want to hear more about it.

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/

iQA/AwUBP0zaOimqKFIzPnwjEQL+ZQCeIR0X0MEUnLsow6IGwKfFLsYTstEAn2SQ
zMvifMn7z9A12oPp82cjXmCF
=LdLQ
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Wed Aug 27 12:33: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 MAA14175
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 12:33:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s3BU-0001Lu-RM
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 12:30:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s3B9-0001EM-JK
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 12:29: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 MAA13707
	for <ietf@ietf.org>; Wed, 27 Aug 2003 12:29:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s3B8-00026d-00
	for ietf@ietf.org; Wed, 27 Aug 2003 12:29:50 -0400
Received: from evrtwa1-ar8-4-65-021-158.evrtwa1.dsl-verizon.net ([4.65.21.158] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19s3B7-00026K-00
	for ietf@ietf.org; Wed, 27 Aug 2003 12:29:49 -0400
Received: from eagleswings (127.0.0.1:3347)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S31A36> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 27 Aug 2003 09:29:44 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: <john.loughney@nokia.com>, <robert@digi-data.com>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: Solving the right problems ...
Date: Wed, 27 Aug 2003 09:28:27 -0700
Message-ID: <052701c36cb8$3e9c2a70$63124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <DADF50F5EC506B41A0F375ABEB320636A8B2B3@esebe023.ntc.nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

john.loughney@nokia.com wrote:
> A very quick question about your idea.  Does this layer have a=20
> protocol / interface to other elements on the network? Or are=20
> you proposing something more like an abstract API?

Simple question, complex answer ... It really depends on where you are
looking at it from, and how the name space discussion gets resolved. As =
I
was writing that, it occurred to me that from the app perspective what =
you
want is to provide most of the characteristics of the transport API, =
making
it somewhat transparent but the layer is really a manager substituting
application name space identifiers for topology references, etc. At the =
same
time there may need to be some protocol between the layer peers and/or
infrastructure services to establish identities, along the lines of
HIP/DHT/enhanced DNS/etc. As I see it, the hard work is getting this =
part
done well.

The thought was that the protocol parts of TCP/UDP/SCTP/... do what they =
do
as directed from above, and do that efficiently. In the abstract, there =
is
no reason that the entity above them can't deal with changing connection
state, or topology attachment points. In the current environment though, =
we
have apps parked in that spot, and we agree that dealing with changes is =
too
much complexity to ask of apps in general.=20

Historically, since we have apps parked in that spot, there has been an
insistence that all of the topology complexity get resolved in the lower
layers. Pushing complexity into the lower layers makes them less =
efficient,
and will unnecessarily break many of the operational assumptions that =
exist.
Providing an optional stabilization layer above transport allows =
endpoints
to come and go at different points in the topology, while the =
application
remains oblivious to the changes.

Tony





From owner-ietf@ietf.org  Wed Aug 27 12: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 MAA16008
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 12:47:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s3Ol-0003b6-Vd
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 12:43:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s3Lf-0003Lj-DI
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 12: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 MAA14977
	for <ietf@ietf.org>; Wed, 27 Aug 2003 12:40:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s3LR-0002SA-00
	for ietf@ietf.org; Wed, 27 Aug 2003 12:40:29 -0400
Received: from evrtwa1-ar8-4-65-021-158.evrtwa1.dsl-verizon.net ([4.65.21.158] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19s3LQ-0002S7-00
	for ietf@ietf.org; Wed, 27 Aug 2003 12:40:29 -0400
Received: from eagleswings (127.0.0.1:3929)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S31A3F> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 27 Aug 2003 09:40:34 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Jeroen Massar'" <jeroen@unfix.org>, <ietf@ietf.org>
Cc: <ipng@sunroof.eng.sun.com>
Subject: RE: Solving the right problems ...
Date: Wed, 27 Aug 2003 09:39:16 -0700
Message-ID: <052f01c36cb9$c1dea790$63124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <002001c36c8c$f7426250$210d640a@unfix.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Jeroen Massar wrote:
> ... As far as it stands I think that HIP=20
> is going the best way there is. LIN6 is flawed as it won't=20
> scale and can't be deployed easily. Next to those I got my=20
> own odd idea and I will probably work it out and implement it=20
> as a proof of concept. Though timing on when and how may be=20
> completely unknown.

What I was trying to point out is that HIP/etc. is only part of the
solution. What an identity protocol needs is a point in the stack which =
is
being identified. We can try to stuff it into each of the transport
protocols, but we will have to do that over for each, and there would =
need
to be complex api options if apps wanted to avoid the identity / =
topology
mapping. It will be much simpler to leave the existing api path for the =
apps
that want that service, and provide a layer above transport to manage =
the
mappings.

Tony






From owner-ietf@ietf.org  Wed Aug 27 12:53: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 MAA16716
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 12:53:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s3Uq-0004LW-Hu
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 12:50:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s3Ud-0004Bf-W7
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 12:50: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 MAA16350
	for <ietf@ietf.org>; Wed, 27 Aug 2003 12:49:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s3Ua-0002yo-00
	for ietf@ietf.org; Wed, 27 Aug 2003 12:49:56 -0400
Received: from evrtwa1-ar8-4-65-021-158.evrtwa1.dsl-verizon.net ([4.65.21.158] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19s3UY-0002yd-00
	for ietf@ietf.org; Wed, 27 Aug 2003 12:49:55 -0400
Received: from eagleswings (127.0.0.1:4279)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S31A44> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 27 Aug 2003 09:50:00 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'Jeroen Massar'" <jeroen@unfix.org>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: Solving the right problems ...
Date: Wed, 27 Aug 2003 09:48:42 -0700
Message-ID: <053001c36cbb$13208b90$63124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <B3649D46-D89D-11D7-83FB-00039388672E@muada.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Iljitsch van Beijnum wrote:
> The multi6 wg has been working on locator/identifier separation as a=20
> way to solve the multihoming in IPv6 problem for a while now.
>=20
> The problems we're facing (apart from the fact that there are=20
> many ways=20
> to skin this particular cat and everyone has a different=20
> preference) is=20
> that additional mechanisms are needed to get the extra information=20
> across, and there is a price to be paid in one or more of: additional=20
> round trips, more dependence on the DNS or something similar to DNS,=20
> additional per-packet overhead, loss of backward compatibility,=20
> increased complexity.
>=20

At least the backward compatibility issue is primarily due to trying to
force a lower layer to mask the topological realities. There may be some
need for additional round trips, or enhanced mapping infrastructure, but =
if
that only applied to apps using a new stabilization layer, there =
wouldn't be
as much complaint because those would see a clear benefit. In any case I
don't think adding a layer will be a trivial task, but from here it =
looks
like the least the path of least resistance.

Tony






From owner-ietf@ietf.org  Wed Aug 27 12:55: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 MAA17018
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 12:55:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s3Wk-0004cx-Up
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 12:52:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s3V3-0004MY-7W
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 12:50: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 MAA16409
	for <ietf@ietf.org>; Wed, 27 Aug 2003 12:50:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s3V2-0002zq-00
	for ietf@ietf.org; Wed, 27 Aug 2003 12:50:24 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s3V1-0002zP-00
	for ietf@ietf.org; Wed, 27 Aug 2003 12:50:23 -0400
Received: from f02v-19-157.d0.club-internet.fr ([212.195.238.157] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.20)
	id 19s3Uj-0001qC-8S; Wed, 27 Aug 2003 09:50:05 -0700
Message-Id: <5.2.0.9.0.20030827183604.026d5b70@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 27 Aug 2003 18:52:29 +0200
To: Iljitsch van Beijnum <iljitsch@muada.com>,
        "Jeroen Massar" <jeroen@unfix.org>
From: jfcm <info@utel.net>
Subject: Re: Solving the right problems ...
Cc: <alh-ietf@tndh.net>, <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
In-Reply-To: <B3649D46-D89D-11D7-83FB-00039388672E@muada.com>
References: <002001c36c8c$f7426250$210d640a@unfix.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; 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 - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
Sender: owner-ietf@ietf.org
Precedence: bulk

Using a 1D numbering plan to support 5 (?) distinct dimensions (plan, 
technology, network routing, global host addressing and interface 
identification) looks like X121 or old telephony.

Which additionnal information do you need to move accross if you use fixed 
size dimension and gives evey dimension its separate numbering 
authority/structure and then concatenate them into a multidimentional 
address? Like for mobiles.

I remember when CCITT voted they would never allocate addresses of more 
than X bytes. (was it not 32?). Would anyone recall if at that time they 
discussed some kind of layer splitting? Old experience often carries 
interesting concepts. They were probably thinking hierarchichal instead of 
multidimensional?
jfc


At 16:49 27/08/03, Iljitsch van Beijnum wrote:

>On woensdag, aug 27, 2003, at 13:18 Europe/Amsterdam, Jeroen Massar wrote:
>
>>I totally agree with your current insight that we need to seperate
>>the routing from the host identifier. IMHO every host should have
>>one globally unique ID and could have multiple transports, even if
>>those are IPv4, IPv6, IPX or whatever based and going over multiple
>>links or not. Though we should limit to IP based protocols to not
>>make it too complicated. Such a mechanism could solve problems for:
>>"site-locals" constructions, multihoming, mobile-ip without hindering
>>the size of the routing table as people could continue to use current
>>routing, thus TLA based and fully aggregated to the TLA level in the GRT.
>
>The multi6 wg has been working on locator/identifier separation as a way 
>to solve the multihoming in IPv6 problem for a while now.
>
>The problems we're facing (apart from the fact that there are many ways to 
>skin this particular cat and everyone has a different preference) is that 
>additional mechanisms are needed to get the extra information across, and 
>there is a price to be paid in one or more of: additional round trips, 
>more dependence on the DNS or something similar to DNS, additional 
>per-packet overhead, loss of backward compatibility, increased complexity.
>
>
>
>
>
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.512 / Virus Database: 309 - Release Date: 19/08/03




From owner-ietf@ietf.org  Wed Aug 27 13:24: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 NAA19679
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 13:24:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s3xr-0007ZG-4q
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 13:20:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s3tt-00079x-50
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 13:16: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 NAA19004
	for <ietf@ietf.org>; Wed, 27 Aug 2003 13:15:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s3ts-0003i1-00
	for ietf@ietf.org; Wed, 27 Aug 2003 13:16:04 -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 19s3tr-0003hy-00
	for ietf@ietf.org; Wed, 27 Aug 2003 13:16:03 -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 3EF2D7F4C;
	Wed, 27 Aug 2003 19:16:02 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Tony Hain'" <alh-ietf@tndh.net>, <ietf@ietf.org>
Cc: <ipng@sunroof.eng.sun.com>
Subject: RE: Solving the right problems ...
Date: Wed, 27 Aug 2003 19:15:53 +0200
Organization: Unfix
Message-ID: <00e301c36cbe$df6d3c90$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
In-Reply-To: <052f01c36cb9$c1dea790$63124104@eagleswings>
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

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

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

[?Does this need to keep going to both ietf@ietf.org & ipng@sunroof?]

> Jeroen Massar wrote:
> > ... As far as it stands I think that HIP 
> > is going the best way there is. LIN6 is flawed as it won't 
> > scale and can't be deployed easily. Next to those I got my 
> > own odd idea and I will probably work it out and implement it 
> > as a proof of concept. Though timing on when and how may be 
> > completely unknown.
> 
> What I was trying to point out is that HIP/etc. is only part of the
> solution. What an identity protocol needs is a point in the 
> stack which is being identified. We can try to stuff it into each
> of the transport protocols, but we will have to do that over for
> each, and there would need to be complex api options if apps
> wanted to avoid the identity / topology mapping. It will be 
> much simpler to leave the existing api path for the apps
> that want that service, and provide a layer above transport 
> to manage the mappings.

My current idea puts it at the resolver level. The application
gets the 128bits identifier, which actuall is a IPv6 address,
either given out from a special registry or simply from an
/48 that is already assigned to you. This address can be used
for both routing and identification purposes and can easily
be assigned to hosts by using RA.

The stack/API then maintains a list of routing IP's that
are associated by that "IdentifierIP" and then replaces it
before it enters the network with the routing IP that is
to be used for actually routing the packet. On initial
communication there could be an extra header sent along
which says "this packet originates from this Identifier IP"
along with a signature, verifyable through eg DNS to check
it is really it. HIP is much further there though.

This way apps don't need to know about it, they only need
to know about IPv6. One could also pass this along to IPv4
except then it needs an extra magic packet for the IDIP.
See HIP again. And I am thinking about using the above for
solving a little problem for dynamic hosts in the SixXS project.

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/

iQA/AwUBP0znSSmqKFIzPnwjEQJiqACfem9Xk2LFRgFNM/wb67MXSmO4UEUAoJla
C7Xsb0R5XDzB2qC900ki1SUx
=I6ut
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Wed Aug 27 13:33: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 NAA20532
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 13:33:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s46W-0000OD-5P
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 13:29:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s432-0008GY-Qw
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 13:25: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 NAA19778
	for <ietf@ietf.org>; Wed, 27 Aug 2003 13:25:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s431-0003u2-00
	for ietf@ietf.org; Wed, 27 Aug 2003 13:25:31 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s430-0003tz-00
	for ietf@ietf.org; Wed, 27 Aug 2003 13:25:30 -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 h7RHPqxS006143;
	Wed, 27 Aug 2003 19:25:52 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Wed, 27 Aug 2003 19:25:34 +0200
Subject: Re: Solving the right problems ...
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
To: "Tony Hain" <alh-ietf@tndh.net>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <053001c36cbb$13208b90$63124104@eagleswings>
Message-Id: <77409D36-D8B3-11D7-83FB-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, aug 27, 2003, at 18:48 Europe/Amsterdam, Tony Hain wrote:

> but if that only applied to apps using a new stabilization layer, 
> there wouldn't be as much complaint because those would see a clear 
> benefit.

So when will vendors recompile their apps for multihoming? Right after 
they're done recompiling them for IPv6?

It might be useful to start thinking about what we can do in the long 
term if we don't care about supporting existing applications, but this 
won't solve any of today's or tomorrow's problems.




From owner-ietf@ietf.org  Wed Aug 27 13:33: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 NAA20548
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 13:33:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s45l-0000Io-48
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 13:28:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s40O-0007ys-Br
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 13:22: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 NAA19467
	for <ietf@ietf.org>; Wed, 27 Aug 2003 13:22:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s40N-0003po-00
	for ietf@ietf.org; Wed, 27 Aug 2003 13:22:47 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s40M-0003pl-00
	for ietf@ietf.org; Wed, 27 Aug 2003 13:22:46 -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 h7RHN8xS006113;
	Wed, 27 Aug 2003 19:23:08 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Wed, 27 Aug 2003 19:22:49 +0200
Subject: Re: Solving the right problems ...
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
To: jfcm <info@utel.net>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <5.2.0.9.0.20030827183604.026d5b70@mail.utel.net>
Message-Id: <155A29C3-D8B3-11D7-83FB-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, aug 27, 2003, at 18:52 Europe/Amsterdam, jfcm wrote:

> Using a 1D numbering plan to support 5 (?) distinct dimensions (plan, 
> technology, network routing, global host addressing and interface 
> identification) looks like X121 or old telephony.

> Which additionnal information do you need to move accross if you use 
> fixed size dimension and gives evey dimension its separate numbering 
> authority/structure and then concatenate them into a multidimentional 
> address? Like for mobiles.

I have three problems with this.

First, "fixed size" always means "wrong size".

Second, with going from 20 to 40 bytes for the IP header I feel we've 
pretty much used up our overhead increasing budget for this decade.

Last but not least: having an identifier and a locator in the same 
packet is useless as we have mechanisms to authenticate identifiers and 
mechanisms to authenticate locators, but without mechanisms to 
authenticate the association between a locator and an identifier, we 
open up a whole new world of denial of service. Fixing this by carrying 
auth data (= a signature) inband would be an unacceptable increase of 
overhead, and doing it out of band would be redundant as it is much 
more efficient to carry the actual data out of band than the 
authentication data for the inband data.

> I remember when CCITT voted they would never allocate addresses of 
> more than X bytes. (was it not 32?).

32 bytes? This wasn't for voice, was it? I really wouldn't care much 
for dialing 75 digit phone numbers...

The way I see it:

We now have FQDNs that identify services or hosts, and we have IP 
addresses, that identify hosts or routing+interface. In order to 
decrease the ambiguity to managable levels, we need to move the FQDNs 
and especially IP addresses away from identifying hosts, and introduce 
and explicit host or "stack name" identifier. Host identifiers should 
look like IPv6 (maybe optionally IPv4) addresses, in order to be able 
to keep using our current protocols that expect 16/4 bit values. (And 
there isn't much of substance to be gained by giving them a different 
shape.) Where necessary, FQDNs can be replaced by application specific 
namespaces with a system to map those names to host identifiers to go 
along with such a new space. The hard part is coming up with a way to 
do the host/location mapping in a way that is simple, fast, cheap, 
secure, flexible and reliable.

Iljitsch




From owner-ietf@ietf.org  Wed Aug 27 13:33: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 NAA20563
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 13:33:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s457-0000BB-Si
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 13:27:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s3zG-0007gD-3r
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 13:21: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 NAA19404
	for <ietf@ietf.org>; Wed, 27 Aug 2003 13:21:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s3zE-0003oT-00
	for ietf@ietf.org; Wed, 27 Aug 2003 13:21:37 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s3zE-0003oQ-00
	for ietf@ietf.org; Wed, 27 Aug 2003 13:21:36 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 84D581413B; Wed, 27 Aug 2003 13:21: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 11116-02; Wed, 27 Aug 2003 13:21: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 C00D714138; Wed, 27 Aug 2003 13:21:35 -0400 (EDT)
Date: Wed, 27 Aug 2003 13:21:35 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Tony Hain" <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, john.loughney@nokia.com, robert@digi-data.com,
        ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: Solving the right problems ...
Message-Id: <20030827132135.385f0c2f.moore@cs.utk.edu>
In-Reply-To: <052701c36cb8$3e9c2a70$63124104@eagleswings>
References: <DADF50F5EC506B41A0F375ABEB320636A8B2B3@esebe023.ntc.nokia.com>
	<052701c36cb8$3e9c2a70$63124104@eagleswings>
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

> Historically, since we have apps parked in that spot, there has been
> an insistence that all of the topology complexity get resolved in the
> lower layers.

uh, no.  the design is for a clean separation of function between the
layers that know about network topology and the hosts, which aren't
supposed to need to know about such things.  that separation of function
is still highly desirable.  

what has changed is that we're now expecting a layer 3 that was designed
for relatively stable networks of wired hosts to suddenly accomodate
mobile and nomadic hosts and networks, without significant change.

you can't solve the right problems without first recognizing what they
are.






From owner-ietf@ietf.org  Wed Aug 27 13:52: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 NAA22040
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 13:52:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s4Ox-0003Gq-Qg
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 13:48:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s4KU-0002t4-K2
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 13: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 NAA21542
	for <ietf@ietf.org>; Wed, 27 Aug 2003 13:43:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s4KT-0004Px-00
	for ietf@ietf.org; Wed, 27 Aug 2003 13:43:33 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s4KS-0004PY-00
	for ietf@ietf.org; Wed, 27 Aug 2003 13:43:32 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h7RHgiD07248;
	Wed, 27 Aug 2003 10:42:44 -0700
X-mProtect: <200308271742> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.67, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpd5mufhe; Wed, 27 Aug 2003 10:42:43 PDT
Message-ID: <3F4CEFA5.2010202@iprg.nokia.com>
Date: Wed, 27 Aug 2003 10:51:33 -0700
From: Fred Templin <ftemplin@iprg.nokia.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: jfcm <info@utel.net>, ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: Solving the right problems ...
References: <155A29C3-D8B3-11D7-83FB-00039388672E@muada.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

Iljitsch van Beijnum wrote:

> The hard part is coming up with a way to do the host/location mapping 
> in a way that is simple, fast, cheap, secure, flexible and reliable.


Wouldn't we all start deploying, e.g., HIP tomorrow if we had a solution for
this? And, how might that solution be any different than MIP HoA/CoA
binding management? Again, I'm looking forward to seeing any proposals
that may be forthcoming.

Fred
ftemplin@iprg.nokia.com






From owner-ietf@ietf.org  Wed Aug 27 14:50: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 OAA26006
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 14:50:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s5CE-0007Mv-Ki
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 14:39:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s56v-00075d-VU
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 14:33: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 OAA24774
	for <ietf@ietf.org>; Wed, 27 Aug 2003 14:33:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s56u-0005DP-00
	for ietf@ietf.org; Wed, 27 Aug 2003 14:33:36 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s56t-0005DM-00
	for ietf@ietf.org; Wed, 27 Aug 2003 14:33:36 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id A4F501413A; Wed, 27 Aug 2003 14:33:35 -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 26969-06; Wed, 27 Aug 2003 14:33: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 D6C8114130; Wed, 27 Aug 2003 14:33:34 -0400 (EDT)
Date: Wed, 27 Aug 2003 14:33:34 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Solving the right problems ...
Message-Id: <20030827143334.23a50cf0.moore@cs.utk.edu>
In-Reply-To: <155A29C3-D8B3-11D7-83FB-00039388672E@muada.com>
References: <5.2.0.9.0.20030827183604.026d5b70@mail.utel.net>
	<155A29C3-D8B3-11D7-83FB-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

> We now have FQDNs that identify services or hosts, and we have IP 
> addresses, that identify hosts or routing+interface. In order to 
> decrease the ambiguity to managable levels, we need to move the FQDNs 
> and especially IP addresses away from identifying hosts, and introduce
> and explicit host or "stack name" identifier. Host identifiers should 
> look like IPv6 (maybe optionally IPv4) addresses, in order to be able 
> to keep using our current protocols that expect 16/4 bit values. (And 
> there isn't much of substance to be gained by giving them a different 
> shape.) 

mostly agree, except that I suspect it works better to put the new layer
between IP and transport than to insert a layer underneath IP.  part of
this assumption is that the new layer can still be nil for hosts whose
location is fixed and that do not need unreasonably stable addresses.

> Where necessary, FQDNs can be replaced by application specific
> namespaces with a system to map those names to host identifiers to go 
> along with such a new space. 

I don't see a need to change FQDNs themselves - but the meanings of the
IP addresses that they map to will change slightly.

> The hard part is coming up with a way to 
> do the host/location mapping in a way that is simple, fast, cheap, 
> secure, flexible and reliable.

yup.  that, and making the transition work smoothly.

Keith



From owner-ietf@ietf.org  Wed Aug 27 14:50: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 OAA26009
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 14:50:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s5EM-0007d1-5x
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 14:41:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s5Ce-0007Rn-7I
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 14:39: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 OAA25245
	for <ietf@ietf.org>; Wed, 27 Aug 2003 14:39:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s5CZ-0005IO-00
	for ietf@ietf.org; Wed, 27 Aug 2003 14:39:27 -0400
Received: from cs180094.pp.htv.fi ([213.243.180.94] helo=hades.pp.htv.fi)
	by ietf-mx with esmtp (Exim 4.12)
	id 19s5CX-0005IL-00
	for ietf@ietf.org; Wed, 27 Aug 2003 14:39:26 -0400
Received: from hades.pp.htv.fi (liljeber@localhost [127.0.0.1])
	by hades.pp.htv.fi (8.12.9/8.12.9/Debian-5) with ESMTP id h7RIeabO025898;
	Wed, 27 Aug 2003 21:40:37 +0300
Received: (from liljeber@localhost)
	by hades.pp.htv.fi (8.12.9/8.12.9/Debian-5) id h7RIeQ9w025897;
	Wed, 27 Aug 2003 21:40:26 +0300
X-Authentication-Warning: hades.pp.htv.fi: liljeber set sender to mika.liljeberg@welho.com using -f
Subject: Re: Solving the right problems ...
From: Mika Liljeberg <mika.liljeberg@welho.com>
To: Keith Moore <moore@cs.utk.edu>
Cc: Tony Hain <alh-ietf@tndh.net>, john.loughney@nokia.com,
        robert@digi-data.com, ietf@ietf.org, ipng@sunroof.eng.sun.com
In-Reply-To: <20030827132135.385f0c2f.moore@cs.utk.edu>
References: <DADF50F5EC506B41A0F375ABEB320636A8B2B3@esebe023.ntc.nokia.com>
	 <052701c36cb8$3e9c2a70$63124104@eagleswings>
	 <20030827132135.385f0c2f.moore@cs.utk.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1062009626.9714.273.camel@hades>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4 
Date: Wed, 27 Aug 2003 21:40:26 +0300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wed, 2003-08-27 at 20:21, Keith Moore wrote:
> what has changed is that we're now expecting a layer 3 that was designed
> for relatively stable networks of wired hosts to suddenly accomodate
> mobile and nomadic hosts and networks, without significant change.

TCP/IP was designed for such networks. What has changed is that we no
longer have provider indepdendent addressing. Which means routing
protocols can no longer do the job.

	MikaL




From owner-ietf@ietf.org  Wed Aug 27 14:59: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 OAA26974
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 14:59:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s5Rl-0000oJ-Q2
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 14:55:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s5OA-00006o-Go
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 14:51: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 OAA26094
	for <ietf@ietf.org>; Wed, 27 Aug 2003 14:51:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s5O9-0005Ud-00
	for ietf@ietf.org; Wed, 27 Aug 2003 14:51:25 -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 19s5O8-0005UV-00
	for ietf@ietf.org; Wed, 27 Aug 2003 14:51:24 -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 489F27F4C;
	Wed, 27 Aug 2003 20:51:23 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Mika Liljeberg'" <mika.liljeberg@welho.com>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: Solving the right problems ...
Date: Wed, 27 Aug 2003 20:51:14 +0200
Organization: Unfix
Message-ID: <00f401c36ccc$314c7b90$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <1062009626.9714.273.camel@hades>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

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

Mika Liljeberg wrote:

> On Wed, 2003-08-27 at 20:21, Keith Moore wrote:
> > what has changed is that we're now expecting a layer 3 that was =
designed
> > for relatively stable networks of wired hosts to suddenly accomodate
> > mobile and nomadic hosts and networks, without significant change.
>=20
> TCP/IP was designed for such networks. What has changed is that we no
> longer have provider indepdendent addressing. Which means routing
> protocols can no longer do the job.

Routing protocols can keep doing a perfect job as they are.
An ISP has a TLA in IPv6 and it provides routability from and
to the address space in this TLA. That is the routing part:
sending a packet from A to B. Just like your postal address.

The Identifier part goes on top of that making the packet
have a signature, saying "this packet is from me".

Then there is a third part in the process which allows
a single identity to have multiple Routing IP's: postal addresses.
Just like one can send you a postal packet to your office and
to your work address, both with your name on it which
will make sure that it arrives at you.

Thus we don't need PI, which is a stupid pain on the
routing tables. We need Identifiers.

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/

iQA/AwUBP0z9oimqKFIzPnwjEQIk7wCfT2Z79cB+Luag3N+E+fzdHleyxLoAoLok
8Cy/EPr5O7yA4RCCJGAsmgfq
=3DHjyf
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Wed Aug 27 15:16: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 PAA29272
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 15:16:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s5jV-0000XV-Ru
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 15:13:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s5iQ-00005o-UX
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 15:12: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 PAA28670
	for <ietf@ietf.org>; Wed, 27 Aug 2003 15:12:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s5iP-000620-00
	for ietf@ietf.org; Wed, 27 Aug 2003 15:12:21 -0400
Received: from evrtwa1-ar8-4-65-021-158.evrtwa1.dsl-verizon.net ([4.65.21.158] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19s5iO-00061x-00
	for ietf@ietf.org; Wed, 27 Aug 2003 15:12:20 -0400
Received: from eagleswings (127.0.0.1:4795)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S31A90> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 27 Aug 2003 12:12:26 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>
Cc: <ietf@ietf.org>
Subject: RE: Solving the right problems ...
Date: Wed, 27 Aug 2003 12:11:08 -0700
Message-ID: <055201c36cce$f897da30$63124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <77409D36-D8B3-11D7-83FB-00039388672E@muada.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

> So when will vendors recompile their apps for multihoming? 
> Right after 
> they're done recompiling them for IPv6?

It will be the same step, because the only reason they would be recompiling
for IPv6 is to accomidate customer demand. Since the larger customers that
might create demand are almost all multihomed, that will be a primary
feature in the porting effort.

Tony






From owner-ietf@ietf.org  Wed Aug 27 15:16: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 PAA29295
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 15:16:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s5ip-0000Jy-8m
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 15:12:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s5cP-0006nL-Du
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 15:06: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 PAA27697
	for <ietf@ietf.org>; Wed, 27 Aug 2003 15:06:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s5cN-0005uS-00
	for ietf@ietf.org; Wed, 27 Aug 2003 15:06:07 -0400
Received: from evrtwa1-ar8-4-65-021-158.evrtwa1.dsl-verizon.net ([4.65.21.158] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19s5cN-0005uJ-00
	for ietf@ietf.org; Wed, 27 Aug 2003 15:06:07 -0400
Received: from eagleswings (127.0.0.1:4380)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S31A8B> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 27 Aug 2003 12:05:51 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Jeroen Massar'" <jeroen@unfix.org>, <ietf@ietf.org>
Cc: <ipng@sunroof.eng.sun.com>
Subject: RE: Solving the right problems ...
Date: Wed, 27 Aug 2003 12:04:34 -0700
Message-ID: <055001c36cce$0dae5ee0$63124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <00e301c36cbe$df6d3c90$210d640a@unfix.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Jeroen Massar wrote:
> [?Does this need to keep going to both ietf@ietf.org & ipng@sunroof?]
>=20

Not as far as I am concerned. If we take the suggested path, the work is
clearly outside the IPv6 WG, and anyone on the IPv6 list that cares to
follow the discussion is now aware of it. I will be dropping ipng from =
any
further responses to this thread.

> My current idea puts it at the resolver level. The=20
> application gets the 128bits identifier, which actuall is a=20
> IPv6 address, either given out from a special registry or=20
> simply from an /48 that is already assigned to you. This=20
> address can be used for both routing and identification=20
> purposes and can easily be assigned to hosts by using RA.
>=20
> The stack/API then maintains a list of routing IP's that
> are associated by that "IdentifierIP" and then replaces it=20
> before it enters the network with the routing IP that is to=20
> be used for actually routing the packet. On initial=20
> communication there could be an extra header sent along which=20
> says "this packet originates from this Identifier IP" along=20
> with a signature, verifyable through eg DNS to check it is=20
> really it. HIP is much further there though.

The only issue is the slight of hand in 'The stack/API then maintains a =
list
of routing IP's ...'. It would appear your assumption is that L4 or =
below
would perform the substitution magic, and have a protocol to communicate =
to
the peer what the magic is. I am saying that this should simply be a =
formal
layer between L4 & L7. This avoids messing with existing lower layers =
which
would create compatibility issues both for the peer node, as well as
application expectations about what the lower layers do.

>=20
> This way apps don't need to know about it, they only need
> to know about IPv6. One could also pass this along to IPv4=20
> except then it needs an extra magic packet for the IDIP. See=20
> HIP again. And I am thinking about using the above for=20
> solving a little problem for dynamic hosts in the SixXS project.

So you prove my original point, 'there is a sacred invariant, and we =
must
avoid messing with the app / transport interface at all costs'. =
Everything
you described would fit cleanly in an entity that sat between L4 & L7. =
In
fact from an architectural perspective, the "IdentifierIP" you describe
would be the name of the point in the stack shared by all interfaces &
transports. It really doesn't matter if that name is variable length =
ascii,
or fixed length binary, but I am sure many will share their favorite
opinion.

Tony




From owner-ietf@ietf.org  Wed Aug 27 15:42: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 PAA01724
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 15:42:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s64o-0004fu-VM
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 15:35:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s647-0004bQ-Ij
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 15:34: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 PAA01248
	for <ietf@ietf.org>; Wed, 27 Aug 2003 15:34:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s646-0006Y9-00
	for ietf@ietf.org; Wed, 27 Aug 2003 15:34:46 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s645-0006Y6-00
	for ietf@ietf.org; Wed, 27 Aug 2003 15:34:45 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 4D30314142; Wed, 27 Aug 2003 15:34:44 -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 07474-14; Wed, 27 Aug 2003 15:34:42 -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 071D814040; Wed, 27 Aug 2003 15:34:42 -0400 (EDT)
Date: Wed, 27 Aug 2003 15:34:41 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Tony Hain" <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Solving the right problems ...
Message-Id: <20030827153441.755dc4f8.moore@cs.utk.edu>
In-Reply-To: <055001c36cce$0dae5ee0$63124104@eagleswings>
References: <00e301c36cbe$df6d3c90$210d640a@unfix.org>
	<055001c36cce$0dae5ee0$63124104@eagleswings>
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

> Jeroen Massar wrote:
> > [?Does this need to keep going to both ietf@ietf.org &
> > ipng@sunroof?]
> > 
> 
> Not as far as I am concerned. If we take the suggested path, the work
> is clearly outside the IPv6 WG, 

only because you insist that the layer belongs between 4 and 7.  but
since the layer belongs between 3 and 4, or maybe between 2 and 3,
it clearly does impinge on IPv6.




From owner-ietf@ietf.org  Wed Aug 27 15:50: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 PAA02544
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 15:50:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s6AQ-0004yW-Fw
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 15:41:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s66P-0004lg-05
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 15:37: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 PAA01400
	for <ietf@ietf.org>; Wed, 27 Aug 2003 15:37:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s66N-0006bF-00
	for ietf@ietf.org; Wed, 27 Aug 2003 15:37:07 -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 19s66L-0006ap-00
	for ietf@ietf.org; Wed, 27 Aug 2003 15:37:06 -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 4DBCB7F4C;
	Wed, 27 Aug 2003 21:37:00 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Tony Hain'" <alh-ietf@tndh.net>, <ietf@ietf.org>
Subject: RE: Solving the right problems ...
Date: Wed, 27 Aug 2003 21:36:51 +0200
Organization: Unfix
Message-ID: <010101c36cd2$90c0c3f0$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <055001c36cce$0dae5ee0$63124104@eagleswings>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

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

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

<SNIP similar part>

> > This way apps don't need to know about it, they only need
> > to know about IPv6. One could also pass this along to IPv4=20
> > except then it needs an extra magic packet for the IDIP. See=20
> > HIP again. And I am thinking about using the above for=20
> > solving a little problem for dynamic hosts in the SixXS project.
>=20
> So you prove my original point, 'there is a sacred invariant,=20
> and we must avoid messing with the app / transport interface at all=20
> costs'. Everything you described would fit cleanly in an entity
> that sat between L4 & L7.

Agreed.

As for transparency for 'old' application that don't support this
we could invent a new RR which holds the identifier for that host,
or simply use TXT records, eg:

purgatory.unfix.org.   TXT   "POINT 2042::1"
                       AAAA  3ffe:8114:2000:240:290:27ff:fe24:c19f
                       AAAA  2001:db8:1:1:210:dcff:fe20:7c7c

The reverse of the Identifier IP contains the Routing IP's to be used.
Additionally the TXT record contains it's public key with which the
extension headers are signed and which could also be used for the =
switchovers.

POINT <Identifier IP> <Public Key>

Example:=20
1....2.4.0.2.ip6.arpa. TXT   "POINT 2042::1 =
8d9f2acfbe7c54e4893a34e50656a602"
                       AAAA  3ffe:8114:2000:240:290:27ff:fe24:c19f
                       AAAA  2001:db8:1:1:210:dcff:fe20:7c7c

I chose IPv6 for the identifier, as every new installation will
be getting IPv6 addresses anyways (hopefully) and there should
be enough to address all the hosts in the world and beyond.
Distribution of this Identifier IP could easily be done by RA
or DHCPv6 with a special flag for example. The address can be
taken from a standard delegation from an ISP, as long as
you also get to control the reverse, or from a seperate registry
that doesn't allow using these addresses for routing, almost like
the IX allocations but not quite like those. This will give
companies PI _like_ addresses, but they are not used for routing
and thus don't do any harm to the size of the GRT.

Applications keep to see IPv6 addresses but they are actually
Identifier IP's, so no harm done to the installed base.
We only need the 'magic' for passing along what happens when
a link breaks down and thus that the packet
Next to that the stack must replace the Identifier IP with
the routing IP, based on some rules/assumptions/...
Thus hosts that support this scheme benefit from it, others don't.

Same trick can be applied to IPv4, except for the updates
being stuffed in the Extension headers we could use a special
udp proto which does the same trick. The signature in DNS
can be used in verifying that it is really the sending host
thus even allowing other routing IP's to be used than those
stored in DNS.

Yes, in this setup we have a dependency on DNS, but that is
just a way of distributing data that works. Lowering the TTL
could allow 'mobility' if we wanted that remote hosts could
contact the moving host. LIN6 solves this by introducing a
faster and directer form of DNS called a Mobile Agent.

> In fact from an architectural perspective, the "IdentifierIP"=20
> you describe would be the name of the point in the stack shared by
> all interfaces & transports.

Actually my document called it IdentifierIP at first but I changed
it to "Point" as it is a point in the network, not a node, which
represents the "Routing IP".

> It really doesn't matter if that name
> is variable length ascii, or fixed length binary, but I am sure
> many will share their favorite opinion.

A current application calls getaddrinfo() or similar to retrieve
the IP of a remote host. In my idea I choose for an IPv6 address
to be returned. The kernel or the API would then mask the IPv6
address passed to the program, which it further uses to identify
the remote host replacing incoming packets to the identifier ip
and outgoing packets with the routing IP's. Keeping normal
behaviour, allowing multiple independent uplinks etc.

As for OSI:
7: Application
6: Presentation - we replace the IdentifierIP with the routing IP
5: Session      -=20
4: Transport    - TCP/UDP
3: Network      - The IP protocol
2: Data link    - Ethernet/POS/ATM/DSL/*
1: Physical     - The cable or the air ;)

Presentation, as we 'present' the network to the application.
Just like it says :)

There generally explains my idea for my final thesis...

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/

iQA/AwUBP00IUimqKFIzPnwjEQK6VgCePkHsQiI+krZ007PnEJk91h/zSCQAnRra
nLyfNiqSwQ9BrVNOWEqSG5wa
=3DsGa+
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Wed Aug 27 19: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 TAA16806
	for <ietf-web-archive@odin.ietf.org>; Wed, 27 Aug 2003 19:07:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19s99h-0001X8-9e
	for ietf-list@asgard.ietf.org; Wed, 27 Aug 2003 18:52:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19s98R-0001SU-J4
	for ietf@asgard.ietf.org; Wed, 27 Aug 2003 18:51: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 SAA15982
	for <ietf@ietf.org>; Wed, 27 Aug 2003 18:51:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19s98Q-0002Ht-00
	for ietf@ietf.org; Wed, 27 Aug 2003 18:51:26 -0400
Received: from [202.99.23.242] (helo=peoplemail.com.cn)
	by ietf-mx with smtp (Exim 4.12)
	id 19s98B-0002H3-00
	for ietf@ietf.org; Wed, 27 Aug 2003 18:51:16 -0400
Received: from peoplemail.com.cn([127.0.0.1]) by peoplemail.com.cn(JetMail 2.5.3.0)
	with SMTP id jm43f4d874b; Wed, 27 Aug 2003 22:49:15 -0000
Received: from asgard.ietf.org([202.99.23.243]) by peoplemail.com.cn(JetMail 2.5.3.0)
	with SMTP id jm13f4aa726; Mon, 25 Aug 2003 22:48:23 -0000
Received: from ([132.151.6.40]) by peoplemail.com.cn(AIMC 2.9.5.4)
	with SMTP id jm43f4b0579; Tue, 26 Aug 2003 06:54:23 +0800
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19rNBX-0007ZT-7M
	for ietf-list@asgard.ietf.org; Mon, 25 Aug 2003 15:39:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rN8l-0007NP-MG
	for ietf@asgard.ietf.org; Mon, 25 Aug 2003 15:36: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 PAA12206
	for <ietf@ietf.org>; Mon, 25 Aug 2003 15:36:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rN8k-0006X0-00
	for ietf@ietf.org; Mon, 25 Aug 2003 15:36:34 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rN8j-0006Ws-00
	for ietf@ietf.org; Mon, 25 Aug 2003 15:36:33 -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 h7PJauxS076774;
	Mon, 25 Aug 2003 21:36:56 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Mon, 25 Aug 2003 21:36:33 +0200
Subject: Re: AW: www.ietf.org.
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Randy Bush <randy@psg.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <E19rCVM-0002Dn-42@roam.psg.com>
Message-Id: <6EA7C10C-D733-11D7-83FB-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
X-Auto-Forward: jaglee@peoplemail.com.cn
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On maandag, aug 25, 2003, at 10:15 Europe/Amsterdam, Randy Bush wrote:

>> unless there is a reason why that host should not be using v6
>> services, hmm?

> because it works now?

But for some boxes only if I use NAT, and having to use NAT makes for a 
liberal definition of "works".

> v6 has one salient feature, more address space.  religious selling
> does not help the case for v6.  make it work simply and directly,
> not through 42 hacks.  get router, dsl, ... vendors to support it.
> then it will be used.

So when everyone else is running IPv6, the IETF will start doing it 
too? Not good enough. The proof of the pudding is in the eating. The 
proof of the protocol is in running production traffic over it.

The IETF www server uses Apache2 which supports IPv6 just fine, BTW. As 
do all the major OS vendors and a good number of router vendors. If 
there is a reason why it is not a good idea to run www.ietf.org over 
IPv6 at this point in time: no big deal. "It works now" doesn't qualify 
as such a reason, IMO.

But I see psg.com (which handles mail for ops.ietf.org) now actually 
accepts connections on port 25 as per the MX and AAAA records that have 
been in place for a long time so I guess there is progress.





From owner-ietf@ietf.org  Thu Aug 28 00:52: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 AAA16452
	for <ietf-web-archive@odin.ietf.org>; Thu, 28 Aug 2003 00:52:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sEar-0000kz-VV
	for ietf-list@asgard.ietf.org; Thu, 28 Aug 2003 00:41:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sEaH-0000hI-TA
	for ietf@asgard.ietf.org; Thu, 28 Aug 2003 00:40: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 AAA15696
	for <ietf@ietf.org>; Thu, 28 Aug 2003 00:40:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sEaF-0002UD-00
	for ietf@ietf.org; Thu, 28 Aug 2003 00:40:31 -0400
Received: from stoneport.math.uic.edu ([131.193.178.160])
	by ietf-mx with smtp (Exim 4.12)
	id 19sEaF-0002U4-00
	for ietf@ietf.org; Thu, 28 Aug 2003 00:40:31 -0400
Received: (qmail 54489 invoked by uid 1016); 28 Aug 2003 04:47:30 -0000
Date: 28 Aug 2003 04:47:30 -0000
Message-ID: <20030828044730.54488.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: namedroppers@ops.ietf.org
Cc: ietf@ietf.org
Subject: Re: wcard-clarify breaking RFC 2308 NXDOMAIN
References: <20030820100735.39120ccd.olaf@ripe.net> <20030826024218.10706.qmail@cr.yp.to> <20030826141441.GK910@apb.cequrux.com> <20030826174447.46552.qmail@cr.yp.to> <20030827101350.GN910@apb.cequrux.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Alan Barrett writes:
> If Paul Vixie said that,

``After RFC 2308, empty nonterminals are signalled with NXDOMAIN.''
http://groups.google.com/groups?selm=199912080700.XAA18392%40bb.rc.vix.com

> he was wrong.  His mistake does not amount to a change of the protocol.

Let me get this straight. After the BIND company

   (1) issues an RFC that clearly allows NXDOMAIN in this situation,
   (2) tells a new implementor that NXDOMAIN in this situation is fine,
   (3) publishes BIND 9, which uses NXDOMAIN in this situation, and
   (4) allows this use of NXDOMAIN to be deployed for four years,

you think it's perfectly reasonable for the BIND company to change its
mind and publish a new RFC saying---without a shred of justification---
that NXDOMAIN in this situation is prohibited?

If the answer to my question in 1999 had been ``Don't use NXDOMAIN,'' I
would have done the extra work to generate NODATA. But Vixie said that
NXDOMAIN was allowed (in fact, required). So I used NXDOMAIN.

Now, four years later, the BIND company is trying to force my users into
a completely unnecessary patch cycle. If the BIND company wants to screw
BIND users, I don't particularly care; but having the BIND company abuse
the standards process to punish _my_ users is completely unacceptable.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Thu Aug 28 05:56: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 FAA23322
	for <ietf-web-archive@odin.ietf.org>; Thu, 28 Aug 2003 05:56:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sJL1-0006PU-Ui
	for ietf-list@asgard.ietf.org; Thu, 28 Aug 2003 05:45:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sJK1-0006Mt-RM
	for ietf@asgard.ietf.org; Thu, 28 Aug 2003 05:44: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 FAA22315
	for <ietf@ietf.org>; Thu, 28 Aug 2003 05:44:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sJJz-0000zg-00
	for ietf@ietf.org; Thu, 28 Aug 2003 05:44:03 -0400
Received: from citadel.cequrux.com ([192.96.22.18])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sJJw-0000zb-00
	for ietf@ietf.org; Thu, 28 Aug 2003 05:44:01 -0400
Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id LAA13097; Thu, 28 Aug 2003 11:43:48 +0200 (SAST)
Received: by citadel.cequrux.com via recvmail id 13093; Thu, 28 Aug 2003 11:43:40 +0200 (SAST)
Date: Thu, 28 Aug 2003 11:43:38 +0200
From: Alan Barrett <apb@cequrux.com>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: namedroppers@ops.ietf.org, ietf@ietf.org
Subject: Re: wcard-clarify breaking RFC 2308 NXDOMAIN
Message-ID: <20030828094338.GQ910@apb.cequrux.com>
References: <20030820100735.39120ccd.olaf@ripe.net> <20030826024218.10706.qmail@cr.yp.to> <20030826141441.GK910@apb.cequrux.com> <20030826174447.46552.qmail@cr.yp.to> <20030827101350.GN910@apb.cequrux.com> <20030828044730.54488.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030828044730.54488.qmail@cr.yp.to>
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 28 Aug 2003, D. J. Bernstein wrote:
> Let me get this straight. After the BIND company
> 
>    (1) issues an RFC that clearly allows NXDOMAIN in this situation,
>    (2) tells a new implementor that NXDOMAIN in this situation is fine,
>    (3) publishes BIND 9, which uses NXDOMAIN in this situation, and
>    (4) allows this use of NXDOMAIN to be deployed for four years,

(1) did not happen.
(2) was a mistake by one person, not by a company or the IETF.
(3) is a bug in bind 9.
(4) is a bug in bind 9.

> you think it's perfectly reasonable for the BIND company to change its
> mind and publish a new RFC saying---without a shred of justification---
> that NXDOMAIN in this situation is prohibited?

Since the premises to not hold, the conclusion makes no sense.

--apb (Alan Barrett)



From owner-ietf@ietf.org  Thu Aug 28 11: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 LAA24208
	for <ietf-web-archive@odin.ietf.org>; Thu, 28 Aug 2003 11:31:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sOYF-0004dP-SN
	for ietf-list@asgard.ietf.org; Thu, 28 Aug 2003 11:19:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sOXN-0004b2-6f
	for ietf@asgard.ietf.org; Thu, 28 Aug 2003 11:18: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 LAA23392
	for <ietf@ietf.org>; Thu, 28 Aug 2003 11:18:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sOXL-00019N-00
	for ietf@ietf.org; Thu, 28 Aug 2003 11:18:11 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sOXL-000197-00
	for ietf@ietf.org; Thu, 28 Aug 2003 11:18:11 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP
	id D14DB139C1; Thu, 28 Aug 2003 15:17:36 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: namedroppers@ops.ietf.org, ietf@ietf.org
Subject: Re: wcard-clarify breaking RFC 2308 NXDOMAIN 
In-Reply-To: Message from Alan Barrett <apb@cequrux.com> 
	of "Thu, 28 Aug 2003 11:43:38 +0200."
	<20030828094338.GQ910@apb.cequrux.com> 
X-Mailer: MH-E 7.4; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 28 Aug 2003 15:17:36 +0000
Message-Id: <20030828151736.D14DB139C1@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> >    (3) publishes BIND 9, which uses NXDOMAIN in this situation, and

> (3) is a bug in bind 9.

which version/versions, specifically?  see below.

---

;; ANSWER SECTION:
version.bind.           0       CH      TXT     "9.3.0a0"

---

;; QUESTION SECTION:
;this.example.vix.com.          IN      A

;; AUTHORITY SECTION:
example.vix.com.        3600    IN      SOA     example.vix.com. root.vix.com. 2003082602 1800 900 604800 86400

---

#fh:i386# grep this example.vix.com 
test.a.is.this  A       127.0.0.5

---

i don't know why any of you is bothering to refute bernstein's assertions,
or even respond to him, or even read his tripe.  however, do consider the
likelihood of him defending my prior comments had he DISAGREED with them,
and also consider that whilest i did in fact misunderstand/misread RFC2308,
several other members of what bernstein laughably calls "the bind company",
notably the author of rfc2308 and a coauthor of the current wildcard draft,
have views remarkably different than the one bernstein quotes me as having.

can we have some serious discourse now?



From owner-ietf@ietf.org  Thu Aug 28 13:13: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 NAA01273
	for <ietf-web-archive@odin.ietf.org>; Thu, 28 Aug 2003 13:13:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sQEH-00010W-6i
	for ietf-list@asgard.ietf.org; Thu, 28 Aug 2003 13:06:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sQD9-0000yI-Er
	for ietf@asgard.ietf.org; Thu, 28 Aug 2003 13:05: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 NAA00642
	for <ietf@ietf.org>; Thu, 28 Aug 2003 13:05:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sQD7-0002va-00
	for ietf@ietf.org; Thu, 28 Aug 2003 13:05:25 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sQD6-0002vX-00
	for ietf@ietf.org; Thu, 28 Aug 2003 13:05:25 -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 h7SH5ixS021330;
	Thu, 28 Aug 2003 19:05:44 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 28 Aug 2003 19:05:19 +0200
Subject: Re: Solving the right problems ...
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org, ipng@sunroof.eng.sun.com
To: Fred Templin <ftemplin@iprg.nokia.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <3F4CEFA5.2010202@iprg.nokia.com>
Message-Id: <CDEB92DA-D979-11D7-97B3-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, aug 27, 2003, at 19:51 Europe/Amsterdam, Fred Templin 
wrote:

>> The hard part is coming up with a way to do the host/location mapping 
>> in a way that is simple, fast, cheap, secure, flexible and reliable.

> Wouldn't we all start deploying, e.g., HIP tomorrow if we had a 
> solution for this?

I'm not exactly current on what's happening with HIP but aren't there 
supposed to be working implementations today?

> And, how might that solution be any different than MIP HoA/CoA
> binding management?

One of the main mechanisms we're considering in the multi6 design team 
(or multi6 DT #1 I should say) is a distributed database that holds the 
mapping from identifier to a set of locators. For multihoming this 
makes a lot of sense as you know all your possible addresses in 
advance. With MIP this is different, but there you have the advantage 
that the home agent is (presumably) always available, while the point 
of multihoming is to survive failures.




From owner-ietf@ietf.org  Thu Aug 28 13:38: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 NAA03544
	for <ietf-web-archive@odin.ietf.org>; Thu, 28 Aug 2003 13:38:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sQeq-0002r0-Ax
	for ietf-list@asgard.ietf.org; Thu, 28 Aug 2003 13:34:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sQdL-0002l6-39
	for ietf@asgard.ietf.org; Thu, 28 Aug 2003 13:32: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 NAA03024
	for <ietf@ietf.org>; Thu, 28 Aug 2003 13:32:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sQdJ-0003Uy-00
	for ietf@ietf.org; Thu, 28 Aug 2003 13:32:29 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sQdJ-0003Uv-00
	for ietf@ietf.org; Thu, 28 Aug 2003 13:32:29 -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 h7SHWlxS021654;
	Thu, 28 Aug 2003 19:32:47 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 28 Aug 2003 19:32:23 +0200
Subject: Re: Solving the right problems ...
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Keith Moore <moore@cs.utk.edu>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <20030827143334.23a50cf0.moore@cs.utk.edu>
Message-Id: <95DBCD76-D97D-11D7-97B3-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, aug 27, 2003, at 20:33 Europe/Amsterdam, Keith Moore wrote:

>> we need to move the FQDNs and especially IP addresses away from 
>> identifying hosts, and introduce and explicit host or "stack name" 
>> identifier.

> mostly agree, except that I suspect it works better to put the new 
> layer
> between IP and transport than to insert a layer underneath IP.

Not sure where you got the idea that I was talking about a layer 
underneath IP. The best way to do this would architecturally between 
transport and IP. It should be possible to implement this in such a way 
that both TCP and other transport and also IP remain unchanged, but I 
expect implementers to take advantage of the TCP state to make better 
rehoming decisions.

> part of
> this assumption is that the new layer can still be nil for hosts whose
> location is fixed and that do not need unreasonably stable addresses.

Unfortunately, it's not this simple. A single homed, fixed location 
host could be talking to another host that is multihomed and/or moving 
around. Both ends must implement something like this for it to work.

>> Where necessary, FQDNs can be replaced by application specific
>> namespaces with a system to map those names to host identifiers to go
>> along with such a new space.

> I don't see a need to change FQDNs themselves - but the meanings of the
> IP addresses that they map to will change slightly.

There is no need to change FQDNs. But today we let an FQDN point to a 
bunch of hosts and then let the application take care of selecting the 
host it wants to talk to and what exactly it wants from the host. I can 
imagine a system where things like files in a peer to peer file sharing 
network or TV channels streamed from a network of streaming servers use 
a namespace particular to that application, with an 
application-specific lookup service to go with it. So I can type 
something like tv://cnn/ and the lookup service for the A/V streaming 
namespace returns the closest host that can stream the required 
content. Obviously we can do this today using our existing protocols 
and some glue here and there, but that way we don't get to take 
advantage of the special properties of A/V streaming, such as a 
carefully synchronized jump from one server to another in mid-stream so 
there is no interruption in the image or sound.




From owner-ietf@ietf.org  Thu Aug 28 15:26: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 PAA11303
	for <ietf-web-archive@odin.ietf.org>; Thu, 28 Aug 2003 15:26:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sSIR-00077m-VG
	for ietf-list@asgard.ietf.org; Thu, 28 Aug 2003 15:19:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19rhmN-0001EA-S6
	for ietf@asgard.ietf.org; Tue, 26 Aug 2003 13:38: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 NAA16555
	for <ietf@ietf.org>; Tue, 26 Aug 2003 13:38:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19rhmF-0003tH-00
	for ietf@ietf.org; Tue, 26 Aug 2003 13:38:43 -0400
Received: from ns.digi-data.com ([209.94.197.193] helo=digi-data.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19rhmD-0003sm-00
	for ietf@ietf.org; Tue, 26 Aug 2003 13:38:41 -0400
Received: from exchsvr.digi-data.com ([10.1.1.11]) by odin.digi-data.com with ESMTP id <119079>; Tue, 26 Aug 2003 13:38:03 -0400
Received: from digi-data.com ([10.1.1.31]) by exchsvr.digi-data.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 26 Aug 2003 13:39:09 -0400
Message-ID: <3F4B9B88.3070305@digi-data.com>
Date:  Tue, 26 Aug 2003 13:40:24 -0400
From: Robert Honore <robert@digi-data.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tony Hain <alh-ietf@tndh.net>
CC: ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: Solving the right problems ...
References: <01df01c36a7b$840dbb80$63124104@eagleswings>
In-Reply-To: <01df01c36a7b$840dbb80$63124104@eagleswings>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Aug 2003 17:39:09.0929 (UTC) FILETIME=[F4C79D90:01C36BF8]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dear Tony Hain,

Perhaps this proposal really requires another working group or 
something.  I seem to remember someone making a similar proposal a 
several years ago on this list and it didn't seem to get a good 
reception then.  For what it is worth, though, I really do think it is 
an idea whose time has come.

It seems everyone has espoused the idea that the application *must* talk 
directly to the network transport in order to be efficient and/or 
resilient, but given the capabilities IPv6 is supposed to have, I wonder 
how much of a good idea it is to cling to that concept.

It is not worthwhile to suggest that the direct application/transport 
interface be eliminated, but it should be possible for an application to 
specify what kind of service it wants from the (transport, network) 
combination and something is there to handle that where the requested 
service is different from that natively provided by the 
(transport,network) combination.  Problem is that right now, every time 
an application needs such a service, the application programmer must 
code his own provisions for it, and none of the propositions I have seen 
discussed so far seems to deal with that.

Keith Moore's statement is quite correct, viz:
> Application developers need
> reasonably stable and reliable endpoint identifiers.  At present, the IP
> address is the closest available approximation to such an identifier.

Two questions arise out of that though, at least as far as Keith Moore's 
statement is concerned.  The first one is how stable is stable?  That 
is, how long is that identifier supposed to remain stable.  And the 
second question is what should be the context of that identifier's validity?

Also from Keith Moore:
> Disagree.  The layer needs to be between the current network and transport
> layers.  If the layer were between transport and applications, many of the
> services provided by transport would end up having to be re-implemented in
> higher layers.

And
> It would also force routing decisions to be made by layers
> much more distant from the network layer that maintains reachability and state
> information than the transport layer.

Does Mr. Moore care to explain a little why he believes these two 
statements?  As far as I can tell it needs not necessarily be so.

Yours sincerely,
Robert Honore.


Tony Hain wrote:
> In the ongoing saga about topology reality vs. application perception of
> stability, it occurs to me we are not working on the right problem. In short
> we have established a sacred invariant in the application / transport
> interface, and the demands on either side of that interface are the root of
> conflict.
> 
> Mobile IP, and the multi6 DHT work are attempts to mitigate it through
> slight of hand at the IP layer, while SCTP attempts to mask the topology
> reality in the transport layer. (These are probably not the only examples,
> but they are the ones that come to mind this morning.) Yet none of these
> really do the job in all cases.
> 
> We all agree that applications should not be aware of topology. At the same
> time,  application developers insist on the right to pass around incomplete
> topology information. There are arguments that the IP address is overloaded
> as an endpoint name. I don't particularly buy that, because the real
> endpoint is either a protocol, or a specific port of a protocol. From one
> perspective, when applications use addresses in referrals, they are
> specifying that routing through a particular point in the topology will
> reach the desired endpoint named 'transport/port-id'. But that is a
> semantics and perception discussion which doesn't help reach the goal.
> 
> In any case, what applications need is a stable reference to other
> participants in the app. Yet we know that current and projected reality says
> that topology is not stable, or consistently reachable. This could be due to
> technology issues of the underlying links, or simple policy. Either way, the
> network as seen by the transport layer is not, and will never be stable or
> consistently reachable from everywhere. Given that, the direct interface
> with the transport layer creates a failure mode for an application expecting
> stability. 
> 
> Where this leads us is to the sacred invariant, and the need to solve the
> problem in the right place. I suggest it is time for the IETF to realize
> that the protocols are no longer being used in the network of 1985, so it is
> time to insert a formal stabilization layer between application & transport.
> 
> 
> Such a layer would be responsible for managing intermittent connectivity
> states and varying attachment points of the transport layers below.
> Applications that interact with this layer would be insulated from the
> inconsistencies being experienced by the transport layer. It would also be
> reasonable for this layer to manage multiple simultaneous transport
> interactions so that the application perceived a single data path to its
> peer. With appropriate trust between the stack and the network policy, this
> would even simplify the process of QoS markings for parallel related data
> sets. 
> 
> The next place that leads us is to a name space. At this point I see no
> reason to avoid using the FQDN structure, but acknowledge that the DNS as
> currently deployed is not even close to being up to the task. The protocols
> are not so much the issue as the deployment and operation model that is
> focused on a limited number of nodes operated by a small community of
> guru's, where the expectation is that any changes occur on the order of
> several days or longer. What we ultimately need in a name service to support
> the suggested layer is the capability for every consumer device with
> electrons in it to automatically and dynamically register its current
> attachment information with rapid (that doesn't mean sub-second, more along
> the lines of a cell phone that powers up away from its home) global
> convergence. As there are multiple trust boundary issues involved (because
> not every device will be subscribed to a service), making this scale will
> require pushing the database distribution out to smaller pockets. Making it
> reliable for Joe-sixpack will probably require that part of the
> infrastructure exists on his side of the interconnect & trust boundary from
> any other networks. Automating the attachment of a massive number of small
> dataset servers will probably require something with better scaling
> characteristics than the current DNSsec deployment model.
> 
> Since many networks have usage policies established around the sacred
> invariant, there will need to be some recommendations on how to apply those
> policies to this new layer. We could even consider a protocol between this
> layer and a policy entity that would aggregate applications into a policy
> consistent with the what the network can deliver for various transport
> protocols. This distribution of policy awareness would have much better
> scaling characteristics than per app signaling, as well as the ability to
> locally group unrelated transports that any given app might be using.
> 
> Bottom line is that we are spending lots of time and effort trying to force
> fit solutions into spaces where they don't work well and end up creating
> other problems. We are doing this simply to maintain the perception of
> stability up to the application, over a sacred interface to a very unstable
> network. Stability to the application is required, but forcing applications
> to have direct interaction with the transport layer is not. Yes we should
> continue to allow that direct interaction, but we should be clear that there
> are no guarantees of stability on that interface. If the application does
> not want to take care of connections coming and going to the same device at
> potentially different places, it needs to have an intermediate stabilization
> layer available.
> 
> Tony
> 
> 
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------
> 







From owner-ietf@ietf.org  Thu Aug 28 17: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 RAA19698
	for <ietf-web-archive@odin.ietf.org>; Thu, 28 Aug 2003 17:15:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sTzw-000567-8y
	for ietf-list@asgard.ietf.org; Thu, 28 Aug 2003 17:08:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sTz0-00053h-Tf
	for ietf@asgard.ietf.org; Thu, 28 Aug 2003 17:07: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 RAA19122
	for <ietf@ietf.org>; Thu, 28 Aug 2003 17:07:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sTyz-00076x-00
	for ietf@ietf.org; Thu, 28 Aug 2003 17:07:05 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sTyy-00076u-00
	for ietf@ietf.org; Thu, 28 Aug 2003 17:07:04 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 50E02141AF; Thu, 28 Aug 2003 17:07:05 -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 09343-13; Thu, 28 Aug 2003 17:07:04 -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 7884C14194; Thu, 28 Aug 2003 17:07:04 -0400 (EDT)
Date: Thu, 28 Aug 2003 17:07:03 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Robert Honore <robert@digi-data.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: where the indirection layer belongs
Message-Id: <20030828170703.550694c3.moore@cs.utk.edu>
In-Reply-To: <3F4B9B88.3070305@digi-data.com>
References: <01df01c36a7b$840dbb80$63124104@eagleswings>
	<3F4B9B88.3070305@digi-data.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 seems everyone has espoused the idea that the application *must*
> talk directly to the network transport in order to be efficient and/or
> resilient, but given the capabilities IPv6 is supposed to have, I
> wonder how much of a good idea it is to cling to that concept.

These "capabilities" should be regarded as bugs which are being fixed.

In particular, the fact that IPv6 hosts can, in ordinary circumstances,
have multiple addresses has led people to believe that it's reasonable
to expect IPv6 apps to deal with an arbitrary number of addresses per
host, some of which work to send traffic to the destination and some of
which don't, and to have this behavior vary from one source location to
another.  First, nobody has ever explained how these hosts can reliably
determine which addresses will work.  Neither source address
selection nor multi-faced DNS are satisfactory answers.  Second, this
robs apps of the best endpoint identifier they have.

> It is not worthwhile to suggest that the direct application/transport 
> interface be eliminated, but it should be possible for an application
> to specify what kind of service it wants from the (transport, network)
> combination and something is there to handle that where the requested 
> service is different from that natively provided by the 
> (transport,network) combination. 

No, it's not worthwhile.  Any kind of routing needs to happen below the
transport layer rather than above it.  That's not to say that you can't
make something work above the transport layer, but that to do so you
have to re-implement routing, acknowledgements, buffering and
retransmissions, duplicate suppression, and windowing in this new layer
when transport protocols already provide it.

> Keith Moore's statement is quite correct, viz:
> > Application developers need
> > reasonably stable and reliable endpoint identifiers.  At present,
> > the IP address is the closest available approximation to such an
> > identifier.
> 
> Two questions arise out of that though, at least as far as Keith
> Moore's statement is concerned.  The first one is how stable is
> stable?  That is, how long is that identifier supposed to remain
> stable. 

Good question.  My best answer so far is: stable enough so that the
vast majority of applications don't have to implement additional logic
to allow them to survive broken TCP/SCTP/etc. connections, or (to put it
another way) stable enough so that failures due to address/prefix
changes are not a significant source of failure for most applications
(as compared to, say, uncorrectable network failures and host failures).

IMHO, apps should be able to assume that an advertised address-host
binding is valid for a minimum of a week.  This is a minimum - it
should be longer whenever possible.  (however there's no requirement to
maintain addresses longer than the nets will be accessible anyway -
i.e., you don't expect the addresses for the ietf conference net to
remain valid after the net is unplugged...but they shouldn't be reused
within a week either.)

> And the second question is what should be the context of that
> identifier's validity?

The identifier should be unique within the entire Internet.  In some
cases (e.g. small networks without connectivity to the Internet core)
"very likely to be unique within the Internet" would probably
suffice.  That doesn't mean that you can send to any point from any
other point, because there will still be access controls.  But if an
address is advertised for a host, and you have permission to send to
that host, you should be able to use that address to send to that host.

> Also from Keith Moore:
> > Disagree.  The layer needs to be between the current network and
> > transport layers.  If the layer were between transport and
> > applications, many of the services provided by transport would end
> > up having to be re-implemented in higher layers.
> 
> And
> > It would also force routing decisions to be made by layers
> > much more distant from the network layer that maintains reachability
> > and state information than the transport layer.
> 
> Does Mr. Moore care to explain a little why he believes these two 
> statements?  As far as I can tell it needs not necessarily be so.

The first one I explained above in slightly more detail.  The second one
should be obvious.  If an address becomes invalid because of a topology
change somewhere distant in the network, how is a layer above layer 4
going to know about it?  It doesn't have access to routing protocol
updates - those happen at layer 3 and aren't normally propagated to
hosts anyway.  When you think about it, you probably don't want hosts to
have to listen for information about distant state changes in the
network - that would place a tremendous burden on small hosts and nets
with low-bandwidth connections.



From owner-ietf@ietf.org  Thu Aug 28 20:43: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 UAA05544
	for <ietf-web-archive@odin.ietf.org>; Thu, 28 Aug 2003 20:43:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sX8S-0003lJ-DE
	for ietf-list@asgard.ietf.org; Thu, 28 Aug 2003 20:29:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sX81-0003iw-Pa
	for ietf@asgard.ietf.org; Thu, 28 Aug 2003 20:28: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 UAA04161
	for <ietf@ietf.org>; Thu, 28 Aug 2003 20:28:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sX80-0002S0-00
	for ietf@ietf.org; Thu, 28 Aug 2003 20:28:36 -0400
Received: from evrtwa1-ar8-4-65-029-016.evrtwa1.dsl-verizon.net ([4.65.29.16] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19sX7z-0002Ro-00
	for ietf@ietf.org; Thu, 28 Aug 2003 20:28:35 -0400
Received: from eagleswings (127.0.0.1:3022)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S31CD5> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 28 Aug 2003 17:28:42 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>,
        "'Robert Honore'" <robert@digi-data.com>
Cc: <ietf@ietf.org>
Subject: RE: where the indirection layer belongs
Date: Thu, 28 Aug 2003 17:27:33 -0700
Message-ID: <00e601c36dc4$57081170$63124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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: <20030828170703.550694c3.moore@cs.utk.edu>
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Keith Moore wrote:
> Second, this robs apps of the best endpoint=20
> identifier they have.

Rather than being so locked into topology locators as endpoint =
identifiers,
we need to be specifying an infrastructure for endpoint identifiers and =
any
mapping protocol that might be needed. To some degree this is where the
multi6 design team is headed, but they appear to have a goal of
'transparently' stuffing the result in the lower layers. The one thing =
that
is obvious from that approach is that it will end up breaking something.

>=20
> > It is not worthwhile to suggest that the direct=20
> application/transport
> > interface be eliminated, but it should be possible for an=20
> application
> > to specify what kind of service it wants from the=20
> (transport, network)
> > combination and something is there to handle that where the=20
> requested=20
> > service is different from that natively provided by the=20
> > (transport,network) combination.=20
>=20
> No, it's not worthwhile.  Any kind of routing needs to happen=20
> below the transport layer rather than above it.  That's not=20
> to say that you can't make something work above the transport=20
> layer, but that to do so you have to re-implement routing,=20
> acknowledgements, buffering and retransmissions, duplicate=20
> suppression, and windowing in this new layer when transport=20
> protocols already provide it.

This is simply wrong. Decisions about topology need to happen below the
application, but that does not equate to below the transport API, unless =
you
hold to the position that the app/transport interface is a sacred =
invariant.


> ...
> The first one I explained above in slightly more detail.  The=20
> second one should be obvious.  If an address becomes invalid=20
> because of a topology change somewhere distant in the=20
> network, how is a layer above layer 4 going to know about it?=20
>  It doesn't have access to routing protocol updates - those=20
> happen at layer 3 and aren't normally propagated to hosts=20
> anyway.  When you think about it, you probably don't want=20
> hosts to have to listen for information about distant state=20
> changes in the network - that would place a tremendous burden=20
> on small hosts and nets with low-bandwidth connections.

Yet you advocate propagating L3 changes to all host stacks so that some =
yet
to be defined glue can magically make the change transparent to the app.
Rather than relying on 'sometimes wanted, sometimes not' magic in the =
lower
layers, it makes much more sense to put an optional layer above L4 to =
reopen
a path using alternate topology information. This still allows the app =
to
choose a direct L4 interface, and removes the need to have the app say =
'give
me mapping, or turn it off' in the API. That would be implicit in its =
choice
of the stabilization layer vs. direct L4.

Tony






From owner-ietf@ietf.org  Thu Aug 28 21:58: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 VAA11430
	for <ietf-web-archive@odin.ietf.org>; Thu, 28 Aug 2003 21:58:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sYOp-0007Sq-67
	for ietf-list@asgard.ietf.org; Thu, 28 Aug 2003 21:50:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sYO0-0007QS-IF
	for ietf@asgard.ietf.org; Thu, 28 Aug 2003 21:49:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10908
	for <ietf@ietf.org>; Thu, 28 Aug 2003 21:49:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sYNy-00047X-00
	for ietf@ietf.org; Thu, 28 Aug 2003 21:49:10 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sYNy-00047U-00
	for ietf@ietf.org; Thu, 28 Aug 2003 21:49:10 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 16F7B141B1; Thu, 28 Aug 2003 21:49:11 -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 25483-12; Thu, 28 Aug 2003 21:49:09 -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 64D73141A9; Thu, 28 Aug 2003 21:49:09 -0400 (EDT)
Date: Thu, 28 Aug 2003 21:49:08 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Tony Hain" <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, robert@digi-data.com, ietf@ietf.org
Subject: Re: where the indirection layer belongs
Message-Id: <20030828214908.22059017.moore@cs.utk.edu>
In-Reply-To: <00e601c36dc4$57081170$63124104@eagleswings>
References: <20030828170703.550694c3.moore@cs.utk.edu>
	<00e601c36dc4$57081170$63124104@eagleswings>
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 Moore wrote:
> > Second, this robs apps of the best endpoint identifier they have.
> 
> Rather than being so locked into topology locators as endpoint
> identifiers, we need to be specifying an infrastructure for endpoint
> identifiers and any mapping protocol that might be needed. 

I don't disagree, but the devil is in the details, and you also have to
pay careful attention to transitions.

> To some
> degree this is where the multi6 design team is headed, but they appear
> to have a goal of'transparently' stuffing the result in the lower
> layers. The one thing that is obvious from that approach is that it
> will end up breaking something.

I can't comment on multi6 since I'm not up to date on what they are
doing.

> >  Any kind of routing needs to happen 
> > below the transport layer rather than above it.  That's not 
> > to say that you can't make something work above the transport 
> > layer, but that to do so you have to re-implement routing, 
> > acknowledgements, buffering and retransmissions, duplicate 
> > suppression, and windowing in this new layer when transport 
> > protocols already provide it.
> 
> This is simply wrong. Decisions about topology need to happen below
> the application, but that does not equate to below the transport API,
> unless you hold to the position that the app/transport interface is a
> sacred invariant.

You are missing something fundamental here - if a TCP connection breaks
(isn't closed cleanly) then the two endpoints can get out of sync
regarding how much data was delivered.  You can't fix this at higher
layers without an unacceptable amount of complexity and overhead.
This has nothing to do with the app/transport interface being a sacred
invariant - it happens any time you try to layer something on top of
transport that has to survive breakage of the transport layer.

(how many ways do I have to explain this?)


> > If an address becomes invalid 
> > because of a topology change somewhere distant in the 
> > network, how is a layer above layer 4 going to know about it? 
> >  It doesn't have access to routing protocol updates - those 
> > happen at layer 3 and aren't normally propagated to hosts 
> > anyway.  When you think about it, you probably don't want 
> > hosts to have to listen for information about distant state 
> > changes in the network - that would place a tremendous burden 
> > on small hosts and nets with low-bandwidth connections.
> 
> Yet you advocate propagating L3 changes to all host stacks so that
> some yet to be defined glue can magically make the change transparent
> to the app.

It's a lot less glue than the L4-L7 approach, and most of it has to deal
with authentication that would be needed for any kind of
remotely-originated routing update anyway, regardless of what layer it
lived at.

> Rather than relying on 'sometimes wanted, sometimes not'
> magic in the lower layers, it makes much more sense to put an optional
> layer above L4 to reopen a path using alternate topology information.

No, it doesn't make sense to add a considerable amount of overhead and
complexity that isn't needed and often won't be used.

> This still allows the app to choose a direct L4 interface, and removes
> the need to have the app say 'give me mapping, or turn it off' in the
> API. That would be implicit in its choice of the stabilization layer
> vs. direct L4.

Yes you can do that but it presumes that the host knows a priori whether
or not it needs the stabilization layer.  I would make the
mechanism used to provide stable addresses a property of the network-
either the network provides "reasonably" stable addresses (i.e. plenty
of prior notice before changing them) or it provides a stabilization
layer.  That way, networks that don't need it don't pay the overhead.

Keith



From owner-ietf@ietf.org  Thu Aug 28 22:32: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 WAA13687
	for <ietf-web-archive@odin.ietf.org>; Thu, 28 Aug 2003 22:32:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sYye-0001DZ-16
	for ietf-list@asgard.ietf.org; Thu, 28 Aug 2003 22:27:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sYyX-0001Ap-ES
	for ietf@asgard.ietf.org; Thu, 28 Aug 2003 22:26: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 WAA13336
	for <ietf@ietf.org>; Thu, 28 Aug 2003 22:26:52 -0400 (EDT)
From: wsimpson@greendragon.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sYyV-0004gx-00
	for ietf@ietf.org; Thu, 28 Aug 2003 22:26:55 -0400
Received: from venera.isi.edu ([128.9.176.32])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sYyS-0004gs-00
	for ietf@ietf.org; Thu, 28 Aug 2003 22:26:52 -0400
Received: from LIBRARY1 (ptlddslgw5poola226.ptld.uswest.net [63.229.132.226])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id TAA12213
	for <ietf@venera.isi.edu>; Thu, 28 Aug 2003 19:24:28 -0700 (PDT)
Message-Id: <200308290224.TAA12213@venera.isi.edu>
To: <ietf@ISI.EDU>
Subject: Thank you!
Date: Thu, 28 Aug 2003 19:28:10 --0700
X-MailScanner: Found to be clean
Importance: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MSMail-Priority: Normal
X-Priority: 3 (Normal)
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="_NextPart_000_191E086F"
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multipart message in MIME format

--_NextPart_000_191E086F
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Please see the attached file for details.
--_NextPart_000_191E086F
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: wicked_scr.scr, Content-Type: application/octet-stream]
The attachment file in the message has been removed by eManager.

--_NextPart_000_191E086F--




From owner-ietf@ietf.org  Thu Aug 28 23:17: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 XAA17421
	for <ietf-web-archive@odin.ietf.org>; Thu, 28 Aug 2003 23:17:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sZeF-000604-FW
	for ietf-list@asgard.ietf.org; Thu, 28 Aug 2003 23:10:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sZc1-0005sg-4n
	for ietf@asgard.ietf.org; Thu, 28 Aug 2003 23:07:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16757
	for <ietf@ietf.org>; Thu, 28 Aug 2003 23:07:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sZby-0005Xb-00
	for ietf@ietf.org; Thu, 28 Aug 2003 23:07:42 -0400
Received: from ns.indranet.co.nz ([210.54.239.210] helo=mail.acheron.indranet.co.nz)
	by ietf-mx with esmtp (Exim 4.12)
	id 19sZbx-0005X1-00
	for ietf@ietf.org; Thu, 28 Aug 2003 23:07:41 -0400
Received: from ijir (enso.acheron.indranet.co.nz [192.168.1.1])
	by mail.acheron.indranet.co.nz (8.11.2/8.11.2) with ESMTP id h7T36WY26948;
	Fri, 29 Aug 2003 15:06:32 +1200
Date: Fri, 29 Aug 2003 15:06:32 +1200
From: Andrew McGregor <andrew@indranet.co.nz>
To: Iljitsch van Beijnum <iljitsch@muada.com>,
        Fred Templin <ftemplin@iprg.nokia.com>
cc: ietf@ietf.org, ipng@sunroof.eng.sun.com, hipsec@honor.trusecure.com
Subject: Re: Solving the right problems ...
Message-ID: <85000000.1062126392@ijir>
In-Reply-To: <CDEB92DA-D979-11D7-97B3-00039388672E@muada.com>
References:  <CDEB92DA-D979-11D7-97B3-00039388672E@muada.com>
X-Mailer: Mulberry/3.1.0b6 (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

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



- --On Thursday, August 28, 2003 07:05:19 PM +0200 Iljitsch van Beijnum 
<iljitsch@muada.com> wrote:

> On woensdag, aug 27, 2003, at 19:51 Europe/Amsterdam, Fred Templin wrote:
>
>>> The hard part is coming up with a way to do the host/location mapping
>>> in a way that is simple, fast, cheap, secure, flexible and reliable.
>
>> Wouldn't we all start deploying, e.g., HIP tomorrow if we had a
>> solution for this?
>
> I'm not exactly current on what's happening with HIP but aren't there
> supposed to be working implementations today?

There are.  Four of them, in fact, but none are yet production quality.

If anyone wants to play or read some code, these are the available ones:

<http://gaijin.iki.fi/hipl/> Linux USAGI, IPv6 only

<http://www.hip4inter.net/index.shtml> NetBSD, dual stack

<http://www.sharemation.com/adm01bass/pyhip-2003-07-19.tar.bz2> Linux, 
Python in userspace (therefore needs no kernel IPSEC), dual stack

There are drafts about the various mappings, but no implementation yet.

There are also ideas around about how to transparently autodetect HIP 
support in the responder, with no a-priori knowledge.

The (new) hipsec mailing list is at 
<http://honor.trusecure.com/mailman/listinfo/hipsec>.

Andrew


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iQCVAwUBP07DOVGmVIGYWzvRAQFTHQP7BUYZ6x/jBX1s7yP3Oro5qEa28ABZumGY
nOQwval68BsGkTjdX6qxrXbMNsnvNbLpIrY0u01/rthVSfDNTH4+FMLhUzjUl0+e
1K+H+2tygLmYCUPKf5xBOwKSgmwp9vaOMfC9EH1ZkaLmC2q7tFX3RJasBv41OG/u
1TyDMOXf5Vo=
=G9KU
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Thu Aug 28 23:59: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 XAA21555
	for <ietf-web-archive@odin.ietf.org>; Thu, 28 Aug 2003 23:59:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19saKp-0008PS-5r
	for ietf-list@asgard.ietf.org; Thu, 28 Aug 2003 23:54:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19saKX-0008Mc-B3
	for ietf@asgard.ietf.org; Thu, 28 Aug 2003 23:53:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21054
	for <ietf@ietf.org>; Thu, 28 Aug 2003 23:53:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19saKV-0006ZH-00
	for ietf@ietf.org; Thu, 28 Aug 2003 23:53:43 -0400
Received: from evrtwa1-ar8-4-65-029-016.evrtwa1.dsl-verizon.net ([4.65.29.16] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19saKU-0006ZE-00
	for ietf@ietf.org; Thu, 28 Aug 2003 23:53:42 -0400
Received: from eagleswings (127.0.0.1:4271)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S31D2A> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 28 Aug 2003 20:53:50 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <robert@digi-data.com>, <ietf@ietf.org>
Subject: RE: where the indirection layer belongs
Date: Thu, 28 Aug 2003 20:52:35 -0700
Message-ID: <010601c36de0$fbc17f50$63124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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: <20030828214908.22059017.moore@cs.utk.edu>
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Keith Moore wrote:
> You are missing something fundamental here - if a TCP=20
> connection breaks (isn't closed cleanly) then the two=20
> endpoints can get out of sync regarding how much data was=20
> delivered.  You can't fix this at higher layers without an=20
> unacceptable amount of complexity and overhead. This has=20
> nothing to do with the app/transport interface being a sacred=20
> invariant - it happens any time you try to layer something on=20
> top of transport that has to survive breakage of the transport layer.

And apps are in exactly that position today. This is still not a valid
reason to insist on adding complexity into the transport or IP layers. =
If a
connection breaks before closing, the notification up is 'broken', then
whatever is there has to decide if it wants to try something else. Today =
the
app has to have the complexity, but there is no reason we can't put that
into a stack layer once for any app that wants it.

> It's a lot less glue than the L4-L7 approach,=20

That is a matter of speculation.

> and most of it=20
> has to deal with authentication that would be needed for any=20
> kind of remotely-originated routing update anyway, regardless=20
> of what layer it lived at.

I agree, but the lower layers are not designed with that in mind, so to =
some
it would appear you want a substantial amount of change to something =
that is
already working well. Never mind the =
transition/deployment/interoperability
issues.


> No, it doesn't make sense to add a considerable amount of=20
> overhead and complexity that isn't needed and often won't be used.

More speculation. In any case, if it is not used it is simply an idle =
module
at the top of the stack.=20


> Yes you can do that but it presumes that the host knows a=20
> priori whether or not it needs the stabilization layer.  I=20
> would make the mechanism used to provide stable addresses a=20
> property of the network- either the network provides=20
> "reasonably" stable addresses (i.e. plenty of prior notice=20
> before changing them) or it provides a stabilization layer. =20
> That way, networks that don't need it don't pay the overhead.

Optimizing before the design is started only ensures that something will =
get
overlooked or dropped as 'too much overhead'.=20

I raised the 'right problems' thread after the observation that we had
several embryonic efforts to separate endpoint identifiers from topology
locators, but all of them are focused on inserting complexity into the =
lower
layers. Those layers don't need complexity to do their job, and any =
changes
in behavior will break current operational assumptions about how those
layers work. Also everyone agrees that the place that needs the =
complexity
of the current & future unstable network masked is the application.
Therefore the place we should be focusing solutions is in the interface
between transport & app.=20

--- Solve the right problem

Tony






From owner-ietf@ietf.org  Fri Aug 29 01:36: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 BAA29374
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 01:36:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sbl9-0004Lc-UN
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 01:25:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sbkV-0004IM-Fb
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 01:24: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 BAA28345
	for <ietf@ietf.org>; Fri, 29 Aug 2003 01:24:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sbkT-0000Qb-00
	for ietf@ietf.org; Fri, 29 Aug 2003 01:24:37 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sbkR-0000QV-00
	for ietf@ietf.org; Fri, 29 Aug 2003 01:24:35 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 9FDB71419D; Fri, 29 Aug 2003 01:24: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 22875-08; Fri, 29 Aug 2003 01:24:35 -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 1980613FAF; Fri, 29 Aug 2003 01:24:35 -0400 (EDT)
Date: Fri, 29 Aug 2003 01:22:26 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Tony Hain" <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, robert@digi-data.com, ietf@ietf.org
Subject: Re: where the indirection layer belongs
Message-Id: <20030829012226.5db10360.moore@cs.utk.edu>
In-Reply-To: <010601c36de0$fbc17f50$63124104@eagleswings>
References: <20030828214908.22059017.moore@cs.utk.edu>
	<010601c36de0$fbc17f50$63124104@eagleswings>
X-Mailer: Sylpheed version 0.9.3 (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 missing something fundamental here - if a TCP 
> > connection breaks (isn't closed cleanly) then the two 
> > endpoints can get out of sync regarding how much data was 
> > delivered.  You can't fix this at higher layers without an 
> > unacceptable amount of complexity and overhead. This has 
> > nothing to do with the app/transport interface being a sacred 
> > invariant - it happens any time you try to layer something on 
> > top of transport that has to survive breakage of the transport layer.
> 
> And apps are in exactly that position today. This is still not a valid
> reason to insist on adding complexity into the transport or IP layers.

Okay, well you've just demonstrated that you're insane.



From owner-ietf@ietf.org  Fri Aug 29 02:49: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 CAA18488
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 02:49:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19scuj-0006Sv-Pr
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 02:39:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sctW-0006Pl-EB
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 02:38: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 CAA17434
	for <ietf@ietf.org>; Fri, 29 Aug 2003 02:37:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sctU-0002IR-00
	for ietf@ietf.org; Fri, 29 Aug 2003 02:38:00 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sctT-0002Hs-00
	for ietf@ietf.org; Fri, 29 Aug 2003 02:37:59 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h7T6fgE08555;
	Thu, 28 Aug 2003 23:41:42 -0700
Date: Thu, 28 Aug 2003 23:36:53 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/11) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <13755138394.20030828233653@brandenburg.com>
To: multi6a@percival.cs.ucla.edu
Subject: Multiple Address Service for Transport (MAST)
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

Howdy,

I've just posted a new mobility/multi-homing proposal as an internet-draft.

The multi6 mailing list is probably the most appropriate venue for
discussing this proposal, so it is the only address showing in the TO
field. However, I have blind cc'd additional lists, for notification:

        ietf, because of a current thread about end point identifiers

        HIP, since my proposal is related to theirs

        end-to-end, since that's what this is about.

The I-D name is:

        draft-crocker-mast-proposal-00.txt

It is also available at:

      <http://brandenburg.com/specifications/draft-crocker-mast-proposal-00.txt>


Herewith the abstract for the proposal:

     Classic Internet transport protocols use a single source IP
     address and a single destination IP address, as part of the
     identification for an individual data flow.  TCP includes
     these in its definition of a connection and its calculation
     of the header checksum.  Hence the transport service is tied
     to a particular IP address pair. This is problematic for
     multi-homed hosts and for mobile hosts.  Both have multiple
     IP addresses but cannot use more than one, for any single
     transport association (context).  Multiple Address Service
     for Transport (MAST) defines a mechanism that transparently
     supports association of multiple IP addresses with any
     transport association.  It requires no change to the IP
     infrastructure, and no change to IP modules or transport
     modules in the end-systems. Instead, it defines a wedge
     layer between IP and transport that operates only in the end
     systems and affects only participating hosts.

As the document notes a couple of times, this is an extended proposal,
rather than a complete specification. It's being put forward in the
current form to solicit comments about the approach and the design, and
to find out whether folks are interested in pursuing it further.

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




From owner-ietf@ietf.org  Fri Aug 29 05: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 FAA02116
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 05:21:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sfJW-00063d-Rm
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 05:13:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sfIr-00060W-6Y
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 05:12: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 FAA01326
	for <ietf@ietf.org>; Fri, 29 Aug 2003 05:12:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sfIo-0005jB-00
	for ietf@ietf.org; Fri, 29 Aug 2003 05:12:18 -0400
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sfIm-0005j7-00
	for ietf@ietf.org; Fri, 29 Aug 2003 05:12:17 -0400
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by penguin-ext.wise.edt.ericsson.se (8.12.9/8.12.9/WIREfire-1.7) with ESMTP id h7T9C431012684;
	Fri, 29 Aug 2003 11:12:08 +0200 (MEST)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2655.55)
	id <QY1LQ42N>; Fri, 29 Aug 2003 11:13:07 +0200
Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D03F52BD3@Esealnt877.al.sw.ericsson.se>
From: "Yuri Ismailov (KI/EAB)" <yuri.ismailov@ericsson.com>
To: "'Tony Hain'" <alh-ietf@tndh.net>, "'Keith Moore'" <moore@cs.utk.edu>
Cc: robert@digi-data.com, ietf@ietf.org
Subject: RE: where the indirection layer belongs
Date: Fri, 29 Aug 2003 11:10:19 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Well, I fully support the idea of a new layer above the transport with new names and whatever names resolution system requires. I think that because the idea is hanging in the air during so long time and being researched by academy during number of years, there is definitely a need for a new group.

There are few, however quite strong arguments for that. First of all why limit ourselves with the question "where the indirection layer belongs?" There is no any indication that more than one indirection layer is possible in the stack and if right design assumed, there will be no collision rather addition of new functionality.

Secondly, looking far back in time (end of 70's, beginning of 80's) the right problem was already addressed by lets say V.Serf, J. Saltzer, D. Reed, D. Clark, .... It was identified that the current bundling of IP addresses and TCP port numbers "allows to connect but not allows to reconnect". End-to-end principal, besides all, states that the function distribution between layers is one of the most important system design principals. Given that, given the fact of multihoming, given the need for mobility support, given the need for v6-v4 internetworking, etc., there is a bunch of new stack features, which are desirable to implement. New layer design becomes more and more demanding.

Thirdly, if to stay below transport layer all efforts will not let go beyond a device (host) level. Obviously, there is a need for naming users, devices, content, services or anything else one might think about. Just an example (there are hundreds of such examples), support for multihoming does not negate move of a flow from one interface to another (the reason does not really matter and this is a reasonable service for applications). Staying below transport and using current, de-facto "endpoint" - socket, which bundles IP address with port numbers we will not get any further in doing that in a good way. This is still multihoming of devices, what about "multideviced" users? If one has more than one device and wants to move a flow between devices would this be possible if implemented below transport layer? ....

Next, what really surprises, is that all talking about new functionality but none of the existing implementations should be changed. If so, we will and already are stuck with virtual interfaces, multiple IP addresses (even per interface), sending multiple IP headers in packets and end up with hacks configuring and reconfiguring routing table without even giving a try to understand that it is not always possible and in the cases when possible might be harmful for applications not willing to use those services requiring all imaginable reconfigurations.


/Yuri




From owner-ietf@ietf.org  Fri Aug 29 05:35: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 FAA03646
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 05:35:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sfbu-0007Lr-1K
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 05:32:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sfb8-0007JH-PX
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 05:31: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 FAA03036
	for <ietf@ietf.org>; Fri, 29 Aug 2003 05:31:08 -0400 (EDT)
From: chris@w3.org
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sfb6-0006A3-00
	for ietf@ietf.org; Fri, 29 Aug 2003 05:31:12 -0400
Received: from [218.20.55.206] (helo=HUANG)
	by ietf-mx with esmtp (Exim 4.12)
	id 19sfax-00068n-00
	for ietf@ietf.org; Fri, 29 Aug 2003 05:31:04 -0400
To: <ietf@ietf.org>
Subject: Re: Wicked screensaver
Date: Fri, 29 Aug 2003 17:35:54 +0800
X-MailScanner: Found to be clean
Importance: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MSMail-Priority: Normal
X-Priority: 3 (Normal)
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="_NextPart_000_00A63C4F"
Message-Id: <E19sfax-00068n-00@ietf-mx>
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multipart message in MIME format

--_NextPart_000_00A63C4F
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

See the attached file for details
--_NextPart_000_00A63C4F
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: your_details.pif, Content-Type: application/octet-stream]
The attachment file in the message has been removed by eManager.

--_NextPart_000_00A63C4F--




From owner-ietf@ietf.org  Fri Aug 29 08:40: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 IAA18402
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 08:40:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19siRO-0007oU-Q9
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 08:33:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19siPA-0007hw-6T
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 08:31: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 IAA17572
	for <ietf@ietf.org>; Fri, 29 Aug 2003 08:30:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19siP9-0001uz-00
	for ietf@ietf.org; Fri, 29 Aug 2003 08:31:03 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19siP8-0001uw-00
	for ietf@ietf.org; Fri, 29 Aug 2003 08:31:02 -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 h7TCVJxS033901;
	Fri, 29 Aug 2003 14:31:21 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Fri, 29 Aug 2003 14:30:56 +0200
Subject: Re: where the indirection layer belongs
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org, multi6@ops.ietf.org
To: "Yuri Ismailov (KI/EAB)" <yuri.ismailov@ericsson.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <4E85E49D1F0CBF4F96EA08E335750D7D03F52BD3@Esealnt877.al.sw.ericsson.se>
Message-Id: <A350E016-DA1C-11D7-B146-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

[CC'ing multi6 as I don't think everyone there knows about this thread 
on the IETF discussion list, but please remove either ietf or multi6 if 
this discussion continues.]

On vrijdag, aug 29, 2003, at 11:10 Europe/Amsterdam, Yuri Ismailov 
(KI/EAB) wrote:

> Thirdly, if to stay below transport layer all efforts will not let go 
> beyond a device (host) level. Obviously, there is a need for naming 
> users, devices, content, services or anything else one might think 
> about.

But aren't we squarely inside the application domain here?

> This is still multihoming of devices, what about "multideviced" users? 
> If one has more than one device and wants to move a flow between 
> devices would this be possible if implemented below transport layer? 
> ....

That's a good point.

But first of all: let's not get too carried away with new and 
interesting problems thereby forgetting about actual needs that users 
have today. We need a way to allow multihoming in IPv6 that doesn't 
have the scaling problems our current IPv4 multihoming practices have.

It's not uncommon to see a FQDN point to several IP addresses so that 
the service identified by the FQDN can be provided either by

(a) multiple hosts, or
(b) a host with multiple addresses.

Now if we want to support moving from one addresses to another in the 
middle of an (application level) session, we have two choices: build a 
mechanism that assumes (a) and by extension also works with (b), or 
focus on (b) exclusively.

It looks like Tony Hain wants to go for (a) while Keith Moore assumes 
(b), hence the insanity claims because a solution for (a), which by its 
nature can only reasonably implemented above TCP, is much more involved 
and less efficient than one that only supports (b), which can work on a 
per-packet basis below TCP and other transports.

As a member of the multi6 design team that works on a (b) solution I'm 
convinced that such a solution will provide many benefits and should be 
developed and implemented.

However, this doesn't say anything about the need for an (a) solution. 
Obviously (a) would be good to have. Peer to peer file sharing 
applications extensively use mechanisms like this, where they download 
parts of a file from different hosts.

Also, the current socket API isn't exactly the optimum way for 
applications to interact with the network. It would make sense to 
create something new that sits between the transport(s) and the 
application, and delegate some tasks that are done by applications 
today, most notably name resolution. This allows us to implement new 
namespaces or new address formats without any pain to application 
developers or users stuck with applications that aren't actively 
maintained by developers. This would also be a good opportunity to 
create sensible ways for applications to ask for advanced services from 
the network.

But the real question here is: does this new "thing" have to be a 
layer? In the layering system we have today, each layer talks to the 
underlying one on the local system, but it also interacts with the same 
layer on the remote end.

I'm not convinced this is called for here. For instance, a host that 
implements the above could use a new advanced API to open a set of TCP 
sessions to all the addresses that a FQDN points to, and then 
distribute HTTP requests for the different parts of a file over these 
sessions. But on the other end of one or more of these sessions, there 
could be a regular HTTP server that is completely unaware of the new 
mechanisms and uses existing socket API calls.

So yes, we need something new above the transport layer, but no, it 
shouldn't be a "layer".

Iljitsch




From owner-ietf@ietf.org  Fri Aug 29 10:19: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 KAA27515
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 10:19:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sjy9-0000Rr-KS
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 10:11:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sjx0-0008RN-67
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 10: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 KAA25787
	for <ietf@ietf.org>; Fri, 29 Aug 2003 10:09:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sjm8-0003WA-00
	for ietf@ietf.org; Fri, 29 Aug 2003 09:58:52 -0400
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sjm7-0003W7-00
	for ietf@ietf.org; Fri, 29 Aug 2003 09:58:51 -0400
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by penguin-ext.wise.edt.ericsson.se (8.12.9/8.12.9/WIREfire-1.7) with ESMTP id h7TDwn31023279;
	Fri, 29 Aug 2003 15:58:49 +0200 (MEST)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2655.55)
	id <QY1LTF99>; Fri, 29 Aug 2003 15:59:53 +0200
Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D03F52BD7@Esealnt877.al.sw.ericsson.se>
From: "Yuri Ismailov (KI/EAB)" <yuri.ismailov@ericsson.com>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>
Cc: ietf@ietf.org, multi6@ops.ietf.org
Subject: RE: where the indirection layer belongs
Date: Fri, 29 Aug 2003 15:57:00 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk


Regarding (a) and (b) alternatives it would be nice to have both. However it is not clear why multihoming for v6 and v4 are different issues. Handling of multiple addresses per host is the stack design issue.
The major problem is not to choose the right interface and to send data through it. Applications can do this today, for example SO_DONOTROUTE option in WinSock2. The issue is to CHANGE between interfaces. Current design is OK as long as there is no dynamics.

Honestly, I think that solving one problem at a time may create problems for solving other problems.
Given broad changes in the stack - whole IETF work essentially, creates a good opportunity to review current design and introduce changes, which allow to avoid fixes.
For example, try to implement and run at the same time more than one draft/RFC introducing IP tunneling. I have had quite fun playing around with this and seriously, if to look at the real problem, it is the fact that the same name - IP address, is horribly overloaded with different semantics.

Why layer? Because if it is not layer, then sockets, in their current form, will still be a limit due to the bundling with IP addresses.

-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
Sent: Friday, August 29, 2003 2:31 PM
To: Yuri Ismailov (KI/EAB)
Cc: ietf@ietf.org; multi6@ops.ietf.org
Subject: Re: where the indirection layer belongs


[CC'ing multi6 as I don't think everyone there knows about this thread 
on the IETF discussion list, but please remove either ietf or multi6 if 
this discussion continues.]

On vrijdag, aug 29, 2003, at 11:10 Europe/Amsterdam, Yuri Ismailov 
(KI/EAB) wrote:

> Thirdly, if to stay below transport layer all efforts will not let go 
> beyond a device (host) level. Obviously, there is a need for naming 
> users, devices, content, services or anything else one might think 
> about.

But aren't we squarely inside the application domain here?

> This is still multihoming of devices, what about "multideviced" users? 
> If one has more than one device and wants to move a flow between 
> devices would this be possible if implemented below transport layer? 
> ....

That's a good point.

But first of all: let's not get too carried away with new and 
interesting problems thereby forgetting about actual needs that users 
have today. We need a way to allow multihoming in IPv6 that doesn't 
have the scaling problems our current IPv4 multihoming practices have.

It's not uncommon to see a FQDN point to several IP addresses so that 
the service identified by the FQDN can be provided either by

(a) multiple hosts, or
(b) a host with multiple addresses.

Now if we want to support moving from one addresses to another in the 
middle of an (application level) session, we have two choices: build a 
mechanism that assumes (a) and by extension also works with (b), or 
focus on (b) exclusively.

It looks like Tony Hain wants to go for (a) while Keith Moore assumes 
(b), hence the insanity claims because a solution for (a), which by its 
nature can only reasonably implemented above TCP, is much more involved 
and less efficient than one that only supports (b), which can work on a 
per-packet basis below TCP and other transports.

As a member of the multi6 design team that works on a (b) solution I'm 
convinced that such a solution will provide many benefits and should be 
developed and implemented.

However, this doesn't say anything about the need for an (a) solution. 
Obviously (a) would be good to have. Peer to peer file sharing 
applications extensively use mechanisms like this, where they download 
parts of a file from different hosts.

Also, the current socket API isn't exactly the optimum way for 
applications to interact with the network. It would make sense to 
create something new that sits between the transport(s) and the 
application, and delegate some tasks that are done by applications 
today, most notably name resolution. This allows us to implement new 
namespaces or new address formats without any pain to application 
developers or users stuck with applications that aren't actively 
maintained by developers. This would also be a good opportunity to 
create sensible ways for applications to ask for advanced services from 
the network.

But the real question here is: does this new "thing" have to be a 
layer? In the layering system we have today, each layer talks to the 
underlying one on the local system, but it also interacts with the same 
layer on the remote end.

I'm not convinced this is called for here. For instance, a host that 
implements the above could use a new advanced API to open a set of TCP 
sessions to all the addresses that a FQDN points to, and then 
distribute HTTP requests for the different parts of a file over these 
sessions. But on the other end of one or more of these sessions, there 
could be a regular HTTP server that is completely unaware of the new 
mechanisms and uses existing socket API calls.

So yes, we need something new above the transport layer, but no, it 
shouldn't be a "layer".

Iljitsch



From owner-ietf@ietf.org  Fri Aug 29 14:44: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 OAA22452
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 14:44:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19so7R-0001aV-RY
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 14:37:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19so5x-0001UE-R6
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 14:35: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 OAA21699
	for <ietf@ietf.org>; Fri, 29 Aug 2003 14:35:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19so5w-0003F4-00
	for ietf@ietf.org; Fri, 29 Aug 2003 14:35:36 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19so5v-0003F1-00
	for ietf@ietf.org; Fri, 29 Aug 2003 14:35:35 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id D5326141B3; Fri, 29 Aug 2003 14:35:35 -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 11164-06; Fri, 29 Aug 2003 14:35: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 F069A140F5; Fri, 29 Aug 2003 14:35:34 -0400 (EDT)
Date: Fri, 29 Aug 2003 14:35:34 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Robert Honore <robert@digi-data.com>
Cc: moore@cs.utk.edu, alh-ietf@tndh.net, ietf@ietf.org
Subject: Re: where the indirection layer belongs
Message-Id: <20030829143534.67c6a983.moore@cs.utk.edu>
In-Reply-To: <3F4F6AF9.2020802@digi-data.com>
References: <20030828170703.550694c3.moore@cs.utk.edu>
	<00e601c36dc4$57081170$63124104@eagleswings>
	<20030828214908.22059017.moore@cs.utk.edu>
	<3F4F6AF9.2020802@digi-data.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

(regarding the complexity of putting a general-purpose layer to survive
address changes between L4 and L7)

>   But why do you assert that it will take lots of complexity and 
> overhead?  Can you point to some code where they tried this?  As far
> as I know, nobody has really given this an earnest try as yet.  At
> least not with any IP protocols.

I tried this in connection with a project called SNIPE that I worked on
several years ago.  SNIPE was an attempt to build a very
reliable distributed computing environment that supported, among other
things, the ability to access a computing resource via multiple
addresses (mostly in order to exploit high-bandwidth local networks
not necessarily using IP), and the ability of both hosts and processes
to migrate to other addresses.  It used a DNS-like service similar to
RESCAP (for those who remember that) to register the addresses at which
a process was accessible, and it attempted to provide TCP-like streams
on top of TCP and this registry that would survive changes in those
addresses.  Basically I found that you can get such a service to work
reasonably well and reasonably efficiently if endpoints don't move
without adequate notice.  OTOH if hosts or processes do move without
adequate notice then you end up needing to implement the mechanisms I
mentioned earlier, and that involves extra copies and extra overhead. 

The reason I am preposing that the two problems (changing addresses
with adequate notice and changing addresses without adequate notice) be
treated separately is that by trying to make a single mechanism serve
both purposes you end up with a lot of inefficiency and/or cost that
aren't needed in most cases.  And that's true (for different reasons)
regardless of whether you insert that single layer between L3 and L4 or
between L4 and L7.

> What specific glue do you believe it requires for the L4 to L7
> approach? 

Thought I'd said this already: buffering of data until acknowledged by
the peer, generation and processing of acknowledgements, retransmission
of lost messages due to broken connections, windowing (so you don't
degrade to stop-and-wait), duplicate suppression.  You also need to
multiplex control and data information over the same stream and to probe
for other addresses when you get a failure on the one you were using.

>   How does that compare to what is needed in an L3 solution?

If you work on the problem at (or just above) L3, transport protocols
already have the code needed to recover from lost messages, so you don't
have to reimplement that.  You basically need a mechanism by which the
layer can realize it needs to start routing packets differently, and do
so.  You probably need multiple ways that the layer can get that
information because the remote address can change for a variety of
reasons and in lots of different places in the network.   (That's
equally true for the L4-L7 layer as for the L3-L4 layer, but the L4-L7
layer isn't in a position to get some of that information.  The L3-L4
layer can potentially recover from address changes more quickly but to
do that safely it has to be able to authenticate and establish a basis
for trust in a wider variety of information sources.)

> > Yes you can do that but it presumes that the host knows a priori
> > whether or not it needs the stabilization layer.  I would make the
> > mechanism used to provide stable addresses a property of the
> > network- either the network provides "reasonably" stable addresses
> > (i.e. plenty of prior notice before changing them) or it provides a
> > stabilization layer.  That way, networks that don't need it don't
> > pay the overhead.
> 
> But I would argue that the host or at least the application's designer
> knows whether it will need the stabilisation layer. 

It can't know that reliably unless the network without the stabilization
layer has well-defined properties - e.g. the network won't change
addresses of a network without advertising those changes with a minimum
amount of advance notice.  If addresses can potentially change at
arbitrary times with no assurance of stability then every app needs the
stabilization layer (or provide its own means of recovery).

> Making the 
> mechanism that provides the stable network addresses a property of the
> network leaves the question of how.  Even if that were achieved
> though, that still does not completely or effectively address the
> problem of one application process identifying its peer across the
> network.

Well, there's no way I can supply all of the details in a few email
messages.  I've been trying to find time to write them up.  In the
meantime I want to discourage too much momentum behind trying to solve
all of the address changing problems in any one place - particularly
between L4 and L7, because I already know that that won't work well.

Keith





From owner-ietf@ietf.org  Fri Aug 29 14:58: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 OAA23495
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 14:58:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19soOi-0002y6-RJ
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 14:55:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19soOV-0002uy-At
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 14:54: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 OAA23302
	for <ietf@ietf.org>; Fri, 29 Aug 2003 14:54:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19soOT-0003kf-00
	for ietf@ietf.org; Fri, 29 Aug 2003 14:54:46 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19soOT-0003kc-00
	for ietf@ietf.org; Fri, 29 Aug 2003 14:54:45 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id CD0B7141C8; Fri, 29 Aug 2003 14:54: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 14451-15; Fri, 29 Aug 2003 14:54:45 -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 2A6E714096; Fri, 29 Aug 2003 14:54:45 -0400 (EDT)
Date: Fri, 29 Aug 2003 14:54:44 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Robert Honore <robert@digi-data.com>
Cc: moore@cs.utk.edu, yuri.ismailov@ericsson.com, alh-ietf@tndh.net,
        ietf@ietf.org, vinton.g.cerf@mci.com
Subject: Re: where the indirection layer belongs
Message-Id: <20030829145444.2ea04bcf.moore@cs.utk.edu>
In-Reply-To: <3F4F9DF9.1070509@digi-data.com>
References: <4E85E49D1F0CBF4F96EA08E335750D7D03F52BD3@Esealnt877.al.sw.ericsson.se>
	<3F4F9DF9.1070509@digi-data.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

> Regarding this discussion about an indirection layer, I am thinking we
> really should propose the formation of some forum for discussion of
> these issues. [...] Call it an indirection layer or a stabilisation
> layer or whatever you want, but we need a forum where we can specify
> the problem we are trying to solve and to consider the possible
> solutions for it.  Does anybody agree?

I don't disagree with the need for a forum at some point, just with the
presumption that a single layer can reasonably solve all of the problems
associated with the various sources of address changes.  So I'd really
push back against an effort to try to accomplish the latter.

Also, experience with the IRTF "name space research group" (which was
tasked to work on a similar problem, though phrased somewhat
differently) has probably left some people (including probably myself)
feeling a bit ...  well, hesitant.  If a relatively small, select
group of very talented experts couldn't agree on how to solve a problem,
is an open forum consisting of an arbitrary number of people with
varying levels of expertise likely to do better?  Bottom line is that
it's very difficult to reconcile the views of people with experience in
very different parts of the network - apps vs. routing vs. transport -
even if they're all highly competent.  It's probably even more difficult
if you have larger numbers of people and you can't assume the competence
level.

Obviously we need to solve this problem.  We just need to be careful
about how we go about it if we hope to be successful.

Personally I think a forum might be a bit premature, as it would
distract various peoples' energy away from efforts to draft strawman
architectures, and instead tempt them to spend time getting in sync with
the group.  Maybe we could have a BOF in Minneapolis and wait for after
that to formally organize a discussion group?

Ketih



From owner-ietf@ietf.org  Fri Aug 29 16:26: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 QAA01952
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 16:26:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19spjw-00037d-IL
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 16:21:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19spit-0002uJ-10
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 16:19: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 QAA01557
	for <ietf@ietf.org>; Fri, 29 Aug 2003 16:19:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19spir-00062A-00
	for ietf@ietf.org; Fri, 29 Aug 2003 16:19:53 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 19spiq-000622-00
	for ietf@ietf.org; Fri, 29 Aug 2003 16:19:52 -0400
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308292008.FAA01012@necom830.hpcl.titech.ac.jp>
Received: from mohta@localhost by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id FAA01012; Sat, 30 Aug 2003 05:07:47 +0859
Subject: Re: where the indirection layer belongs
In-Reply-To: <20030829143534.67c6a983.moore@cs.utk.edu> from Keith Moore at "Aug
 29, 2003 02:35:34 pm"
To: Keith Moore <moore@cs.utk.edu>
Date: Sat, 30 Aug 2003 05:07:45 +0859 ()
CC: Robert Honore <robert@digi-data.com>, alh-ietf@tndh.net, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-ietf@ietf.org
Precedence: bulk

Keith;

> (regarding the complexity of putting a general-purpose layer to survive
> address changes between L4 and L7)

It is not merely complex but also useless to have such a layer.

The basic problem of the approach to have such a layer is that
only the application layer has proper knowledge on proper
timeout value to try other addresses.

So, the issue can be solved only involving application layer, though
most applications over TCP can be satisfied by a default timeout of
TCP. In either case, there is no room to have an additional layer.

I documented it long ago (April 2000) in draft-ohta-e2e-multihoming-*.txt

               The Architecture of End to End Multihoming

(current most version is 05) that:

   To support the end to end multihoming, no change is necessary on
   routing protocols. Instead, APIs and applications must be modified to
   detect and react against the loss of connection.  In case of TCP
   where there is a network wide defact agreement on the semantics
   (timeout period) of the loss of connectivity, most of the work can be
   done by the kernel code at the transport layer, though some timing
   may be adjusted for some application. However, in general, the
   condition of "loss of connectivity" varies application by application
   that the multihoming must directly be controlled by application
   programs.

							Masataka Ohta

PS

Layering is abstraction and not indirection at all.



From owner-ietf@ietf.org  Fri Aug 29 17:13: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 RAA05640
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 17:13:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sqTX-0006cb-NF
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 17:08:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sqRy-0006Vh-5D
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 17: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 RAA05181
	for <ietf@ietf.org>; Fri, 29 Aug 2003 17:06:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sqRw-0007Gl-00
	for ietf@ietf.org; Fri, 29 Aug 2003 17:06:28 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sqRv-0007Gi-00
	for ietf@ietf.org; Fri, 29 Aug 2003 17:06:27 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 17D981409D; Fri, 29 Aug 2003 17:06:28 -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 07528-02; Fri, 29 Aug 2003 17:06:27 -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 7167513FEA; Fri, 29 Aug 2003 17:06:27 -0400 (EDT)
Date: Fri, 29 Aug 2003 17:06:27 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: moore@cs.utk.edu, yuri.ismailov@ericsson.com, ietf@ietf.org,
        multi6@ops.ietf.org
Subject: Re: where the indirection layer belongs
Message-Id: <20030829170627.49778fa0.moore@cs.utk.edu>
In-Reply-To: <A350E016-DA1C-11D7-B146-00039388672E@muada.com>
References: <4E85E49D1F0CBF4F96EA08E335750D7D03F52BD3@Esealnt877.al.sw.ericsson.se>
	<A350E016-DA1C-11D7-B146-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

> It's not uncommon to see a FQDN point to several IP addresses so that 
> the service identified by the FQDN can be provided either by
> 
> (a) multiple hosts, or
> (b) a host with multiple addresses.
> 
> Now if we want to support moving from one addresses to another in the 
> middle of an (application level) session, we have two choices: build a
> mechanism that assumes (a) and by extension also works with (b), or 
> focus on (b) exclusively.
> 
> It looks like Tony Hain wants to go for (a) while Keith Moore assumes 
> (b),

No.  A client can't tell whether multiple addresses associated with an
DNS name indicate multiple hosts or multiple addresses for the same
host.  No matter where the stabilization layer(s) live, using DNS as a
means to map from identity to locations simply won't work.  It might be
good enough for initial connection (assuming that if a service exists on
multiple hosts, any of them will do), but it's not good enough for
re-establishing an already-open connection, because you might get a
different host the next time.

>  hence the insanity claims because a solution for (a), 

I don't know whether Tony assumes (a) or not.  But that has nothing to
do with why I made that particular claim.

> As a member of the multi6 design team that works on a (b) solution I'm
> convinced that such a solution will provide many benefits and should
> be developed and implemented.

And I'm equally convinced that a solution that assumes (b) is a
nonstarter.  There is already too much practice that conflicts with
it.  Like it or not, DNS names are no longer "host" names in practice;
they're "service" names.  A service can be a host but it's not
reasonable to assume that a service _is_ a host.

> Also, the current socket API isn't exactly the optimum way for 
> applications to interact with the network. It would make sense to 
> create something new that sits between the transport(s) and the 
> application, and delegate some tasks that are done by applications 
> today, most notably name resolution. This allows us to implement new 
> namespaces or new address formats without any pain to application 
> developers or users stuck with applications that aren't actively 
> maintained by developers. 

No it doesn't.  What it allows "us" to do is impose subtle changes in
the behavior of lower layers, and introduce new failure modes, without
giving applications any way to deal with them. 


> But the real question here is: does this new "thing" have to be a 
> layer? 

It depends on which "thing" you are talking about.  For the L3-L4 thing,
it's either a new layer or a change to an existing layer.  If you
have both the L4-L7 thing and the L3-L4 thing, the former is either a
new layer or (my personal opinion) a new API that knowledgable apps
call explicitly.




From owner-ietf@ietf.org  Fri Aug 29 17:30: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 RAA07020
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 17:30:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sqlo-0008PG-8x
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 17:27:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sql5-0008LZ-Gm
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 17:26: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 RAA06647
	for <ietf@ietf.org>; Fri, 29 Aug 2003 17:26:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sql4-00003p-00
	for ietf@ietf.org; Fri, 29 Aug 2003 17:26:14 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sql3-00003m-00
	for ietf@ietf.org; Fri, 29 Aug 2003 17:26:13 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id AAA931409D; Fri, 29 Aug 2003 17:26:13 -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 11182-05; Fri, 29 Aug 2003 17:26:12 -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 AF2AB140AB; Fri, 29 Aug 2003 17:26:12 -0400 (EDT)
Date: Fri, 29 Aug 2003 17:26:12 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "vinton g. cerf" <vinton.g.cerf@mci.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: where the indirection layer belongs
Message-Id: <20030829172612.45e1a5f5.moore@cs.utk.edu>
In-Reply-To: <5.2.0.9.2.20030829074311.02f60d20@pop.mcilink.com>
References: <3F4B9B88.3070305@digi-data.com>
	<01df01c36a7b$840dbb80$63124104@eagleswings>
	<3F4B9B88.3070305@digi-data.com>
	<5.2.0.9.2.20030829074311.02f60d20@pop.mcilink.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, the reason I named a specific time interval was to provoke
discussion, so I suppose I shouldn't be disappointed...

I am not sure that one week is the best figure.  I imagine that figure
could reasonably be picked to be anywhere between several hours on the
low end to a few weeks on the high end.


However as I've written in other messages today I believe that trying to
use a single mechanism to handle all cases where addresses change is
probably too expensive (either in money or reduced performance or both),
and to me it makes sense to handle two cases separately - those for
which the change is known about well in advance, and those for which it
is not.  The idea is for l3 or l4 to handle the unanticipated changes
and for l7 (or a layer between l4 and l7) to handle those that are
anticipated and announced.

For the anticipated changes, one week notice/stability does not seem
like an onerous requirement.   For unanticipated changes of wired
networks, I don't think providing redirection for one week is too
expensive either.  And for mobile networks I think it's reasonable to
expect them to pay for redirection services.  In this way the costs of
providing the infrastructure necessary to compensate for the lack of
natural address stability (i.e. the ability to move without one week's
notice) can be borne by those who need that service; others need not pay
for it.  Finally, one week is long enough that most apps (i.e.
those whose connections never have to last that long) won't have to
worry about it or pay for the extra overhead.  You could pick a shorter
time interval but it would eventually start to impact a significant
number of apps.

Of course, there will still be apps that need to worry about user
mobility rather than host mobility.  Since the network doesn't know
anything about users, those apps will still need to provide their own
facilities to keep track of users' network locations.

Keith

p.s. and yes, AOL's IM tracking is quite dynamic, but it's also highly
centralized.  based on the experience with ICANN I think it would be
very difficult to manage the political issues associated with a central
Internet prefix mapping service - though the experience with the ongoing
ENUM work seems, at least from my distant vantage point, to be somewhat
more promising.


> as one thinks about VPNs, tunneling, mobility and the like, assuming a
> week is probably a bad idea. Think a bit about the way AOL's IM tracks
> the binding of an IM handle to an IP address - it is quite dynamic.



From owner-ietf@ietf.org  Fri Aug 29 17:30: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 RAA07038
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 17:30:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sqju-0008Hk-KP
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 17:25:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sqhz-00089I-JY
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 17:23: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 RAA06495
	for <ietf@ietf.org>; Fri, 29 Aug 2003 17:22:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sqhy-00000q-00
	for ietf@ietf.org; Fri, 29 Aug 2003 17:23:02 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sqhx-00000e-00
	for ietf@ietf.org; Fri, 29 Aug 2003 17:23:01 -0400
Received: from f02m-19-95.d0.club-internet.fr ([212.195.214.95] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.20)
	id 19sqhf-0000cc-Fl; Fri, 29 Aug 2003 14:22:43 -0700
Message-Id: <5.2.0.9.0.20030829215137.02fb8a30@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 29 Aug 2003 22:08:05 +0200
To: Keith Moore <moore@cs.utk.edu>, Robert Honore <robert@digi-data.com>
From: jfcm <info@utel.net>
Subject: Re: where the indirection layer belongs
Cc: moore@cs.utk.edu, yuri.ismailov@ericsson.com, alh-ietf@tndh.net,
        ietf@ietf.org, vinton.g.cerf@mci.com
In-Reply-To: <20030829145444.2ea04bcf.moore@cs.utk.edu>
References: <3F4F9DF9.1070509@digi-data.com>
 <4E85E49D1F0CBF4F96EA08E335750D7D03F52BD3@Esealnt877.al.sw.ericsson.se>
 <3F4F9DF9.1070509@digi-data.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; 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 - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
Sender: owner-ietf@ietf.org
Precedence: bulk

At 20:54 29/08/03, Keith Moore wrote:
>Personally I think a forum might be a bit premature, as it would
>distract various peoples' energy away from efforts to draft strawman
>architectures, and instead tempt them to spend time getting in sync with
>the group.  Maybe we could have a BOF in Minneapolis and wait for after
>that to formally organize a discussion group?

Dear Keith,
I fully agree with that. However I feel that the IPv6 numbering plan and 
all the related issues are /  have beein discussed a lot in different fora 
without addressing my expectations - and since I am just one inter pares - 
without probably addressong many other ones expectations. This makes all of 
us uncertain about what has been discussed, where, how specialists have 
decided things we think we have to disagree with, where we can contribute 
in wasting the minium time for everyone.

Might I suggest a preliminary approach: instead of trying to propose 
solutions now, why not to try to list all the demands. Independently from 
any solution. Then to try to put some order into them by possible 
solutions. Such a step could be open to everyone. I am sure that many of us 
would leave the rest to specialists should we be sure that our pet needs 
will be supported or will be considered.

Also, I understand that many feel there is a possible need for multiple 
numbering plans. It would be better to clarify that now.

jfc

I must say that this mail is also a test to see if I am flamed because I 
would be - as many other here who do not tell it - ignoring what I should 
know. A good way to learn. IPv6 is not something for specialists to define: 
it concerns everyone, and everything in the network archiecture.





From owner-ietf@ietf.org  Fri Aug 29 17:59: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 RAA09351
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 17:59:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19srBw-0002Zx-BX
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 17:54:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19srBO-0002WE-M5
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 17:53: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 RAA08954
	for <ietf@ietf.org>; Fri, 29 Aug 2003 17:53:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19srBN-0001AM-00
	for ietf@ietf.org; Fri, 29 Aug 2003 17:53:25 -0400
Received: from smtpzilla5.xs4all.nl ([194.109.127.141])
	by ietf-mx with esmtp (Exim 4.12)
	id 19srBM-0001AF-00
	for ietf@ietf.org; Fri, 29 Aug 2003 17:53:24 -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 h7TLrO4N048776
	for <ietf@ietf.org>; Fri, 29 Aug 2003 23:53:24 +0200 (CEST)
From: "Fam. van den Berg" <inanbe@xs4all.nl>
To: <ietf@ietf.org>
Subject: FW: Virus alert
Date: Fri, 29 Aug 2003 23:53:30 +0200
Message-ID: <000b01c36e77$fc586180$5001a8c0@thelady>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000C_01C36E88.BFE13180"
X-Priority: 1 (Highest)
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: High
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_000C_01C36E88.BFE13180
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

 
All,
 
Today I recieved 2 mails with the following subjects:
 
Wicked screensaver
Thank you!
 
The sender was owner@ietf.org, according to the header.
 
This may indicate that this ietf mailinglist is infected with the sobig
f virus.
I recommend that all the participiants on this list update their
virusscanner and scan their computer for viruses.
 
With kind regards,
 
A. van den Berg, Netherlands

------=_NextPart_000_000C_01C36E88.BFE13180
Content-Type: text/html;
	charset="US-ASCII"
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=3Dus-ascii">
<TITLE>Bericht</TITLE>

<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Dnl dir=3Dltr align=3Dleft><SPAN =

class=3D354564621-29082003><FONT face=3DArial =
size=3D2>All,</FONT></SPAN></DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>Today =
I recieved 2=20
mails with the following subjects:</FONT></SPAN></DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>Wicked =

screensaver</FONT></SPAN></DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>Thank=20
you!</FONT></SPAN></DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>The =
sender was <A=20
href=3D"mailto:owner@ietf.org">owner@ietf.org</A>, according to the=20
header.</FONT></SPAN></DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>This =
may indicate=20
that this ietf mailinglist is infected with the sobig f=20
virus.</FONT></SPAN></DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>I =
recommend that all=20
the participiants on this list update their virusscanner and scan their =
computer=20
for viruses.</FONT></SPAN></DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>With =
kind=20
regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>A. van =
den Berg,=20
Netherlands</FONT></SPAN></DIV></BODY></HTML>

------=_NextPart_000_000C_01C36E88.BFE13180--




From owner-ietf@ietf.org  Fri Aug 29 18:17: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 SAA11828
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 18:17:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19srVR-0000za-MI
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 18:14:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19srSA-0008Uv-Hq
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 18:10: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 SAA10941
	for <ietf@ietf.org>; Fri, 29 Aug 2003 18:10:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19srS9-0001cg-00
	for ietf@ietf.org; Fri, 29 Aug 2003 18:10:45 -0400
Received: from smtpzilla3.xs4all.nl ([194.109.127.139])
	by ietf-mx with esmtp (Exim 4.12)
	id 19srS8-0001ca-00
	for ietf@ietf.org; Fri, 29 Aug 2003 18:10:44 -0400
Received: from thelady (a213-84-140-41.adsl.xs4all.nl [213.84.140.41])
	by smtpzilla3.xs4all.nl (8.12.9/8.12.9) with ESMTP id h7TMAhPY038161;
	Sat, 30 Aug 2003 00:10:43 +0200 (CEST)
From: "A. Kremer" <inanbe@xs4all.nl>
To: "'Fam. van den Berg'" <inanbe@xs4all.nl>, <ietf@ietf.org>
Subject: RE: Virus alert
Date: Sat, 30 Aug 2003 00:10:50 +0200
Message-ID: <000401c36e7a$67dc1d50$5001a8c0@thelady>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0005_01C36E8B.2B64ED50"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <000b01c36e77$fc586180$5001a8c0@thelady>
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0005_01C36E8B.2B64ED50
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Perhaps you are right, but I don't see any harm in warning people about
possible viruses on their computer, even if it seems to be unnecessary.
:)

-----Oorspronkelijk bericht-----
Van: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] Namens Fam. van
den Berg
Verzonden: vrijdag 29 augustus 2003 23:54
Aan: ietf@ietf.org
Onderwerp: FW: Virus alert
Urgentie: Hoog


 
All,
 
Today I recieved 2 mails with the following subjects:
 
Wicked screensaver
Thank you!
 
The sender was HYPERLINK "mailto:owner@ietf.org"owner@ietf.org,
according to the header.
 
This may indicate that this ietf mailinglist is infected with the sobig
f virus.
I recommend that all the participiants on this list update their
virusscanner and scan their computer for viruses.
 
With kind regards,
 
A. van den Berg, Netherlands


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003
 

------=_NextPart_000_0005_01C36E8B.2B64ED50
Content-Type: text/html;
	charset="Windows-1252"
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=3DWindows-1252">
<TITLE>Bericht</TITLE>

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

size=3D2>Perhaps you are right, but I don't see any harm in warning =
people about=20
possible viruses on their computer, even if it seems to be unnecessary.=20
:)</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Dnl dir=3Dltr =
align=3Dleft><FONT face=3DTahoma=20
  size=3D2>-----Oorspronkelijk bericht-----<BR><B>Van:</B> =
owner-ietf@ietf.org=20
  [mailto:owner-ietf@ietf.org] <B>Namens </B>Fam. van den=20
  Berg<BR><B>Verzonden:</B> vrijdag 29 augustus 2003 =
23:54<BR><B>Aan:</B>=20
  ietf@ietf.org<BR><B>Onderwerp:</B> FW: Virus alert<BR><B>Urgentie:</B> =

  Hoog<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Dnl dir=3Dltr =
align=3Dleft><SPAN=20
  class=3D354564621-29082003><FONT face=3DArial =
size=3D2>All,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial =
size=3D2>Today I recieved 2=20
  mails with the following subjects:</FONT></SPAN></DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial =
size=3D2>Wicked=20
  screensaver</FONT></SPAN></DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial =
size=3D2>Thank=20
  you!</FONT></SPAN></DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>The =
sender was <A=20
  href=3D"mailto:owner@ietf.org">owner@ietf.org</A>, according to the=20
  header.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>This =
may indicate=20
  that this ietf mailinglist is infected with the sobig f=20
  virus.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>I =
recommend that=20
  all the participiants on this list update their virusscanner and scan =
their=20
  computer for viruses.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>With =
kind=20
  regards,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D354564621-29082003><FONT face=3DArial size=3D2>A. =
van den Berg,=20
  Netherlands</FONT></SPAN></DIV><BR>
  <P><FONT size=3D2>---<BR>Incoming mail is certified Virus =
Free.<BR>Checked by=20
  AVG anti-virus system (http://www.grisoft.com).<BR>Version: 6.0.512 / =
Virus=20
  Database: 309 - Release Date:=20
19-8-2003<BR></FONT></P></BLOCKQUOTE></BODY></HTML>
<BR>

<P><FONT SIZE=3D2>---<BR>
Outgoing mail is certified Virus Free.<BR>
Checked by AVG anti-virus system (http://www.grisoft.com).<BR>
Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003<BR>
</FONT> </P>

------=_NextPart_000_0005_01C36E8B.2B64ED50--




From owner-ietf@ietf.org  Fri Aug 29 18:37: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 SAA13427
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 18:37:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19srlt-0003nK-AJ
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 18:31:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19srhj-0003WN-OQ
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 18:26: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 SAA12646
	for <ietf@ietf.org>; Fri, 29 Aug 2003 18:26:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19srhi-00021o-00
	for ietf@ietf.org; Fri, 29 Aug 2003 18:26:50 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19srhh-00021S-00
	for ietf@ietf.org; Fri, 29 Aug 2003 18:26:49 -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 SAA29324;
	Fri, 29 Aug 2003 18:21:17 -0400
Date: Fri, 29 Aug 2003 18:21:24 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: "Fam. van den Berg" <inanbe@xs4all.nl>
cc: ietf@ietf.org
Subject: Re: FW: Virus alert
In-Reply-To: <000b01c36e77$fc586180$5001a8c0@thelady>
Message-ID: <Pine.LNX.4.44.0308291817160.28072-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

The from address is typically forged, but seems to be frequently be real
addresses.

I've been getting quite a large number of virus disinfection replies to
various addresses that come to me.  (Quite odd, too, since some of the
addresses being used haven't been used for 10 years, but are still
forwarding mail to my real addresses...)

		--Dean

On Fri, 29 Aug 2003, Fam. van den Berg wrote:

>
> All,
>
> Today I recieved 2 mails with the following subjects:
>
> Wicked screensaver
> Thank you!
>
> The sender was owner@ietf.org, according to the header.
>
> This may indicate that this ietf mailinglist is infected with the sobig
> f virus.
> I recommend that all the participiants on this list update their
> virusscanner and scan their computer for viruses.
>
> With kind regards,
>
> A. van den Berg, Netherlands
>




From owner-ietf@ietf.org  Fri Aug 29 18:37: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 SAA13440
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 18:37:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19srm3-0003oY-J3
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 18:31:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19srjE-0003d7-F6
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 18:28: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 SAA12749
	for <ietf@ietf.org>; Fri, 29 Aug 2003 18:28:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19srjB-000235-00
	for ietf@ietf.org; Fri, 29 Aug 2003 18:28:21 -0400
Received: from smtpzilla2.xs4all.nl ([194.109.127.138])
	by ietf-mx with esmtp (Exim 4.12)
	id 19srjA-00022u-00
	for ietf@ietf.org; Fri, 29 Aug 2003 18:28:20 -0400
Received: from thelady (a213-84-140-41.adsl.xs4all.nl [213.84.140.41])
	by smtpzilla2.xs4all.nl (8.12.9/8.12.9) with ESMTP id h7TMSJTD056331;
	Sat, 30 Aug 2003 00:28:20 +0200 (CEST)
From: "A. Kremer" <inanbe@xs4all.nl>
To: "'David Morris'" <dwm@xpasc.com>
Cc: <ietf@ietf.org>
Subject: RE: Virus alert
Date: Sat, 30 Aug 2003 00:28:25 +0200
Message-ID: <000d01c36e7c$dda14680$5001a8c0@thelady>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 1 (Highest)
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: High
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <Pine.LNX.4.33.0308291510160.17924-100000@egate.xpasc.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ok... I sent this warning because I was concerned about possible
unwanted effects on the list.

Excuse me for the inconvenience. It won't happen again.

-----Oorspronkelijk bericht-----
Van: David Morris [mailto:dwm@xpasc.com] 
Verzonden: zaterdag 30 augustus 2003 0:11
Aan: A. Kremer
Onderwerp: RE: Virus alert



I do ... sending such warnings just multiplies the effect of the virus.

On Sat, 30 Aug 2003, A. Kremer wrote:

> Perhaps you are right, but I don't see any harm in warning people 
> about possible viruses on their computer, even if it seems to be 
> unnecessary.
> :)
>
> -----Oorspronkelijk bericht-----
> Van: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] Namens Fam. van 
> den Berg
> Verzonden: vrijdag 29 augustus 2003 23:54
> Aan: ietf@ietf.org
> Onderwerp: FW: Virus alert
> Urgentie: Hoog
>
>
>
> All,
>
> Today I recieved 2 mails with the following subjects:
>
> Wicked screensaver
> Thank you!
>
> The sender was HYPERLINK "mailto:owner@ietf.org"owner@ietf.org,
> according to the header.
>
> This may indicate that this ietf mailinglist is infected with the 
> sobig f virus. I recommend that all the participiants on this list 
> update their virusscanner and scan their computer for viruses.
>
> With kind regards,
>
> A. van den Berg, Netherlands
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003
>
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003
>
>


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003
 




From owner-ietf@ietf.org  Fri Aug 29 18:51: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 SAA14768
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 18:51:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ss2C-0005g2-3G
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 18:48:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ss0x-0005YO-2y
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 18:46: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 SAA14370
	for <ietf@ietf.org>; Fri, 29 Aug 2003 18:46:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ss0v-0002XE-00
	for ietf@ietf.org; Fri, 29 Aug 2003 18:46:41 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ss0v-0002Wf-00
	for ietf@ietf.org; Fri, 29 Aug 2003 18:46:41 -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 SAA15278;
	Fri, 29 Aug 2003 18:41:03 -0400
Date: Fri, 29 Aug 2003 18:41:10 -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: Virus alert
In-Reply-To: <000401c36e7a$67dc1d50$5001a8c0@thelady>
Message-ID: <Pine.LNX.4.44.0308291837540.28072-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Caution is always a good thing. :-)

		--Dean

On Sat, 30 Aug 2003, A. Kremer wrote:

> Perhaps you are right, but I don't see any harm in warning people about
> possible viruses on their computer, even if it seems to be unnecessary.
> :)
>
> -----Oorspronkelijk bericht-----
> Van: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] Namens Fam. van
> den Berg
> Verzonden: vrijdag 29 augustus 2003 23:54
> Aan: ietf@ietf.org
> Onderwerp: FW: Virus alert
> Urgentie: Hoog
>
>
>
> All,
>
> Today I recieved 2 mails with the following subjects:
>
> Wicked screensaver
> Thank you!
>
> The sender was HYPERLINK "mailto:owner@ietf.org"owner@ietf.org,
> according to the header.
>
> This may indicate that this ietf mailinglist is infected with the sobig
> f virus.
> I recommend that all the participiants on this list update their
> virusscanner and scan their computer for viruses.
>
> With kind regards,
>
> A. van den Berg, Netherlands
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003
>
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003
>
>




From owner-ietf@ietf.org  Fri Aug 29 19: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 TAA17666
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 19:28:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ssb6-0008RT-Ev
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 19:24:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ssaf-0008NV-Aj
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 19: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 TAA17314
	for <ietf@ietf.org>; Fri, 29 Aug 2003 19:23:28 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ssac-0003jC-00
	for ietf@ietf.org; Fri, 29 Aug 2003 19:23:34 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ssab-0003j9-00
	for ietf@ietf.org; Fri, 29 Aug 2003 19:23:33 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta3/8.12.10.Beta3) with ESMTP id h7TNNTm8010320;
	Fri, 29 Aug 2003 19:23:29 -0400
Message-Id: <200308292323.h7TNNTm8010320@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: "A. Kremer" <inanbe@xs4all.nl>
Cc: ietf@ietf.org
Subject: Re: Virus alert 
In-Reply-To: Your message of "Sat, 30 Aug 2003 00:10:50 +0200."
             <000401c36e7a$67dc1d50$5001a8c0@thelady> 
References: <000401c36e7a$67dc1d50$5001a8c0@thelady>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1653979359P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 29 Aug 2003 19:23:29 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sat, 30 Aug 2003 00:10:50 +0200, "A. Kremer" <inanbe@xs4all.nl>  said:

> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003

And every single copy of Sobig-F goes out with the header:

X-MailScanner: Found to be clean

What's wrong with this picture?

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

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

iD8DBQE/T+BxcC3lWbTT17ARApfjAKC83xgD/nfJxGFmt/9au7a7m59OWACg794a
V5UM6smFMbkzPAtGaz8gMRI=
=jtqo
-----END PGP SIGNATURE-----

--==_Exmh_-1653979359P--



From owner-ietf@ietf.org  Fri Aug 29 20:49: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 UAA23002
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 20:49:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19stht-0004tO-6R
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 20:35:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19stdr-0004ag-Fi
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 20:30: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 UAA21930
	for <ietf@ietf.org>; Fri, 29 Aug 2003 20:30:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19stdp-0005XY-00
	for ietf@ietf.org; Fri, 29 Aug 2003 20:30:57 -0400
Received: from adsl-66-137-237-100.dsl.rcsntx.swbell.net
	([66.137.237.100] helo=frascone.com ident=qmailr)
	by ietf-mx with smtp (Exim 4.12)
	id 19stdp-0005XV-00
	for ietf@ietf.org; Fri, 29 Aug 2003 20:30:57 -0400
Received: (qmail 20229 invoked by uid 507); 30 Aug 2003 00:30:46 -0000
Date: Fri, 29 Aug 2003 19:30:44 -0500
From: David Frascone <dave@frascone.com>
To: ietf@ietf.org
Subject: Re: FW: Virus alert
Message-ID: <20030830003044.GW24424@wolverine>
References: <000b01c36e77$fc586180$5001a8c0@thelady> <Pine.LNX.4.44.0308291817160.28072-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.0308291817160.28072-100000@vista.av8.net>
User-Agent: Mutt/1.3.28i
X-Virus-Scanned: by AMaViS 0.3.12
Sender: owner-ietf@ietf.org
Precedence: bulk

With the current virii usually forging the from field with random
addresses from its victim's address book, I turned off my virus
scanner's warning to the senders . . I only send a polite note to the
intended recipient.

Responding to virii, or warning users that they are infected is a waste
of time.

'course, I probably get 25 e-mails a day telling me that I sent someone
Sobig, which would be pretty impressive, since I run Suse :)

-Dave

On Friday, 29 Aug 2003, Dean Anderson wrote:
> The from address is typically forged, but seems to be frequently be real
> addresses.
> 
> I've been getting quite a large number of virus disinfection replies to
> various addresses that come to me.  (Quite odd, too, since some of the
> addresses being used haven't been used for 10 years, but are still
> forwarding mail to my real addresses...)
> 
> 		--Dean
> 
> On Fri, 29 Aug 2003, Fam. van den Berg wrote:
> 
> >
> > All,
> >
> > Today I recieved 2 mails with the following subjects:
> >
> > Wicked screensaver
> > Thank you!
> >
> > The sender was owner@ietf.org, according to the header.
> >
> > This may indicate that this ietf mailinglist is infected with the sobig
> > f virus.
> > I recommend that all the participiants on this list update their
> > virusscanner and scan their computer for viruses.
> >
> > With kind regards,
> >
> > A. van den Berg, Netherlands
> >
> 
> 

-- 
David Frascone

    Why do they tell us to watch "The Today Show" tomorrow?



From owner-ietf@ietf.org  Fri Aug 29 21:18: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 VAA24996
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 21:18:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19suIV-0007pX-Jt
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 21:12:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19suHv-0007lJ-Pz
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 21:12: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 VAA24541
	for <ietf@ietf.org>; Fri, 29 Aug 2003 21:12:17 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19suHu-0006n7-00
	for ietf@ietf.org; Fri, 29 Aug 2003 21:12:22 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19suHt-0006n4-00
	for ietf@ietf.org; Fri, 29 Aug 2003 21:12:21 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta3/8.12.10.Beta3) with ESMTP id h7U1CFm8012680;
	Fri, 29 Aug 2003 21:12:15 -0400
Message-Id: <200308300112.h7U1CFm8012680@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: David Frascone <dave@frascone.com>
Cc: ietf@ietf.org
Subject: Re: FW: Virus alert 
In-Reply-To: Your message of "Fri, 29 Aug 2003 19:30:44 CDT."
             <20030830003044.GW24424@wolverine> 
References: <000b01c36e77$fc586180$5001a8c0@thelady> <Pine.LNX.4.44.0308291817160.28072-100000@vista.av8.net>
            <20030830003044.GW24424@wolverine>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1596698121P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 29 Aug 2003 21:12:15 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Fri, 29 Aug 2003 19:30:44 CDT, David Frascone <dave@frascone.com>  said:

> 'course, I probably get 25 e-mails a day telling me that I sent someone
> Sobig, which would be pretty impressive, since I run Suse :)

I should be so lucky.  I'm averaging almost that many AV-scanner alerts bouncing
to me an *hour*.  And inbound Sobig-F are above 1 per minute.

I still say we should have put this in the "security considerations" in RFC1341:

"If you think you know how to secure active objects in e-mail, you are
probably very mistaken.  There be serious and nasty dragons here."

(with apologies to the authors of 'xterm').

On the other hand, maybe we didn't do THAT badly - I can only think of one
vendor that really didn't pay attention....


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

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

iD8DBQE/T/nvcC3lWbTT17ARArTbAKCAcoCMdCV9eYtcI7uVxSpDGGkSLwCdFIoS
J0bLH1Lq7uOZ6CGVtTIpJI4=
=//QQ
-----END PGP SIGNATURE-----

--==_Exmh_-1596698121P--



From owner-ietf@ietf.org  Fri Aug 29 21:55: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 VAA27607
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 21:55:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19suqT-0001qt-2R
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 21:48:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19supM-0001iZ-2A
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 21:46: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 VAA27051
	for <ietf@ietf.org>; Fri, 29 Aug 2003 21:46:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19supH-00005N-00
	for ietf@ietf.org; Fri, 29 Aug 2003 21:46:51 -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 19supE-00004Z-00
	for ietf@ietf.org; Fri, 29 Aug 2003 21:46:50 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19sYmx-0000nr-00; Thu, 28 Aug 2003 22:14:59 -0400
Date: Thu, 28 Aug 2003 22:14:26 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Valdis.Kletnieks@vt.edu
cc: David Frascone <dave@frascone.com>, <ietf@ietf.org>
Subject: Re: FW: Virus alert 
In-Reply-To: <200308300112.h7U1CFm8012680@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0308282213270.3076-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Can't we just hack the mailman configs to dump mails with X-sender value
of outlook or outlook express?  That would solve the problem, no;)

Scott



On Fri, 29 Aug 2003 Valdis.Kletnieks@vt.edu wrote:

> On Fri, 29 Aug 2003 19:30:44 CDT, David Frascone <dave@frascone.com>  said:
>
> > 'course, I probably get 25 e-mails a day telling me that I sent someone
> > Sobig, which would be pretty impressive, since I run Suse :)
>
> I should be so lucky.  I'm averaging almost that many AV-scanner alerts bouncing
> to me an *hour*.  And inbound Sobig-F are above 1 per minute.
>
> I still say we should have put this in the "security considerations" in RFC1341:
>
> "If you think you know how to secure active objects in e-mail, you are
> probably very mistaken.  There be serious and nasty dragons here."
>
> (with apologies to the authors of 'xterm').
>
> On the other hand, maybe we didn't do THAT badly - I can only think of one
> vendor that really didn't pay attention....
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81/




From owner-ietf@ietf.org  Fri Aug 29 22:31: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 WAA00575
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 22:31:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19svT9-0004sy-Oh
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 22:28:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19svSv-0004oV-Bg
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 22:27: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 WAA00164
	for <ietf@ietf.org>; Fri, 29 Aug 2003 22:27:42 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19svSt-0001R5-00
	for ietf@ietf.org; Fri, 29 Aug 2003 22:27:47 -0400
Received: from h80ad276f.async.vt.edu ([128.173.39.111] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19svSr-0001QC-00
	for ietf@ietf.org; Fri, 29 Aug 2003 22:27:46 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta3/8.12.10.Beta3) with ESMTP id h7U2QkXW019477;
	Fri, 29 Aug 2003 22:26:46 -0400
Message-Id: <200308300226.h7U2QkXW019477@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: David Frascone <dave@frascone.com>, ietf@ietf.org
Subject: Re: FW: Virus alert 
In-Reply-To: Your message of "Thu, 28 Aug 2003 22:14:26 EDT."
             <Pine.LNX.4.44.0308282213270.3076-100000@sleekfreak.ath.cx> 
References: <Pine.LNX.4.44.0308282213270.3076-100000@sleekfreak.ath.cx>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-943786272P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 29 Aug 2003 22:26:45 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Thu, 28 Aug 2003 22:14:26 EDT, shogunx said:
> Can't we just hack the mailman configs to dump mails with X-sender value
> of outlook or outlook express?  That would solve the problem, no;)

Well, the only problem with that idea is that we explicitly do *NOT* have a
"Your clue must be ->THIS<- tall to ride the IETF list" policy... ;)


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

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

iD8DBQE/UAtlcC3lWbTT17ARApxnAJ0SWITl+yyW+7zXPMgK9BdK6lg7tgCfeLGB
WyBu4jml8AW4eFY/XdDmLNo=
=GVOu
-----END PGP SIGNATURE-----

--==_Exmh_-943786272P--



From owner-ietf@ietf.org  Fri Aug 29 23:00: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 XAA02981
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 23:00:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19svsW-0006oM-91
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 22:54:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19svhL-0006C1-BE
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 22:42: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 WAA01692
	for <ietf@ietf.org>; Fri, 29 Aug 2003 22:42:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19svhJ-0001xB-00
	for ietf@ietf.org; Fri, 29 Aug 2003 22:42:41 -0400
Received: from tomts24.bellnexxia.net ([209.226.175.187] helo=tomts24-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19svhI-0001x7-00
	for ietf@ietf.org; Fri, 29 Aug 2003 22:42:40 -0400
Received: from yahoo.com ([65.93.180.133]) by tomts24-srv.bellnexxia.net
          (InterMail vM.5.01.06.04 201-253-122-130-104-20030726) with ESMTP
          id <20030830024234.NEQL29033.tomts24-srv.bellnexxia.net@yahoo.com>;
          Fri, 29 Aug 2003 22:42:34 -0400
Date: Fri, 29 Aug 2003 22:42:34 -0400
Subject: Re: Solving the right problems ...
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>,
        "Tony Hain" <alh-ietf@tndh.net>
To: Iljitsch van Beijnum <iljitsch@muada.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <77409D36-D8B3-11D7-83FB-00039388672E@muada.com>
Message-Id: <9C38DB5A-DA93-11D7-AAE7-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, August 27, 2003, at 01:25 PM, Iljitsch van Beijnum wrote:

> On woensdag, aug 27, 2003, at 18:48 Europe/Amsterdam, Tony Hain wrote:
>
>> but if that only applied to apps using a new stabilization layer, 
>> there wouldn't be as much complaint because those would see a clear 
>> benefit.
>
> So when will vendors recompile their apps for multihoming? Right after 
> they're done recompiling them for IPv6?
>
> It might be useful to start thinking about what we can do in the long 
> term if we don't care about supporting existing applications, but this 
> won't solve any of today's or tomorrow's problems.

Well since a lot of people are still looking for a good reason to move 
to IPv6, and this might be one of them ...

simon


--
simonwoodside.com -- openict.net -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Fri Aug 29 23:40: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 XAA05714
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 23:40:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19swXq-0001sJ-Bk
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 23:36:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19swXH-0001oB-0C
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 23:36: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 XAA05524
	for <ietf@ietf.org>; Fri, 29 Aug 2003 23:36:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sw8p-0003Nb-00
	for ietf@ietf.org; Fri, 29 Aug 2003 23:11:07 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19svuk-0002ym-00
	for ietf@ietf.org; Fri, 29 Aug 2003 22:56:34 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id B2A2B14164; Fri, 29 Aug 2003 22:56:35 -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 29557-13; Fri, 29 Aug 2003 22:56:35 -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 BAAC114050; Fri, 29 Aug 2003 22:56:34 -0400 (EDT)
Date: Fri, 29 Aug 2003 22:54:22 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Valdis.Kletnieks@vt.edu
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: FW: Virus alert
Message-Id: <20030829225422.1fcab494.moore@cs.utk.edu>
In-Reply-To: <200308300112.h7U1CFm8012680@turing-police.cc.vt.edu>
References: <000b01c36e77$fc586180$5001a8c0@thelady>
	<Pine.LNX.4.44.0308291817160.28072-100000@vista.av8.net>
	<20030830003044.GW24424@wolverine>
	<200308300112.h7U1CFm8012680@turing-police.cc.vt.edu>
X-Mailer: Sylpheed version 0.9.3 (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 still say we should have put this in the "security considerations" in RFC1341:

It's pretty difficult to miss the ones that are already there - which certainly
would have been sufficient to stop Sobig had they been heeded.



From owner-ietf@ietf.org  Fri Aug 29 23:46: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 XAA06290
	for <ietf-web-archive@odin.ietf.org>; Fri, 29 Aug 2003 23:46:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19swec-0002kj-QW
	for ietf-list@asgard.ietf.org; Fri, 29 Aug 2003 23:43:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sweQ-0002g5-Oe
	for ietf@asgard.ietf.org; Fri, 29 Aug 2003 23:43: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 XAA06038
	for <ietf@ietf.org>; Fri, 29 Aug 2003 23:43:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sweM-0004lR-00
	for ietf@ietf.org; Fri, 29 Aug 2003 23:43:43 -0400
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sweM-0004hM-00
	for ietf@ietf.org; Fri, 29 Aug 2003 23:43:42 -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);
	 Fri, 29 Aug 2003 20:43:12 -0700
Received: from 157.54.6.150 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 29 Aug 2003 20:43:12 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-05.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Fri, 29 Aug 2003 20:43:20 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Fri, 29 Aug 2003 20:43:11 -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.0);
	 Fri, 29 Aug 2003 20:41:00 -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: FW: Virus alert 
Date: Fri, 29 Aug 2003 20:43:10 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA04EE2557@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: FW: Virus alert 
thread-index: AcNunzamE6Xne5dvRluw+EddTzLuegACLskg
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: <Valdis.Kletnieks@vt.edu>, "shogunx" <shogunx@sleekfreak.ath.cx>
Cc: "David Frascone" <dave@frascone.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 30 Aug 2003 03:41:00.0583 (UTC) FILETIME=[87A56370:01C36EA8]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

>> Can't we just hack the mailman configs to dump mails with X-sender
value
>> of outlook or outlook express?  That would solve the problem, no;)
>=20
> Well, the only problem with that idea is that we explicitly do *NOT*
have > a "Your clue must be ->THIS<- tall to ride the IETF list"
policy... ;)

The Sobig worm includes its own SMTP code, and places arbitrary values
in the header fields. The source address is forged, and so are various
other fields, including X-Mailer. The worm finds target source and
destination addresses by reading files on the user's disk, not by using
a specific Outlook or OE API. It propagates by "social engineering",
when users open some executable attachments. User can do click on
attachments with many mailers, not just Outlook and OE. In fact, the
latest versions of Outlook automatically strip such attachments.

-- Christian Huitema





From owner-ietf@ietf.org  Sat Aug 30 00:19: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 AAA07514
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 00:19:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sx6h-0005Io-4o
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 00:12:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sx5k-0005ED-NQ
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 00:12: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 AAA07331
	for <ietf@ietf.org>; Sat, 30 Aug 2003 00:11:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sx5i-0005hi-00
	for ietf@ietf.org; Sat, 30 Aug 2003 00:11:58 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sx5h-0005hb-00
	for ietf@ietf.org; Sat, 30 Aug 2003 00:11:57 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 8BB921413D; Sat, 30 Aug 2003 00:11: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 31673-02; Sat, 30 Aug 2003 00:11: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 A3146140A4; Sat, 30 Aug 2003 00:11:55 -0400 (EDT)
Date: Sat, 30 Aug 2003 00:09:42 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Christian Huitema" <huitema@windows.microsoft.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Criminals
Message-Id: <20030830000942.2a8df81f.moore@cs.utk.edu>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA04EE2557@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References: <DAC3FCB50E31C54987CD10797DA511BA04EE2557@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: Sylpheed version 0.9.3 (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

> User can do click on
> attachments with many mailers, not just Outlook and OE.

Note that any mailer that does this violates the MIME specifications,
which specifically warn against the presentation of content-types not
known to be safe, against a mail reader implementing the ability to present
arbitrary content via a content-type parameter (e.g. "filename"),
and recommends that the most that should be done with unknown content-types
is to offer to save the content to a file.

The working group that produced MIME went to a lot of effort to research the
hazards associated with transmission of arbitrary content by email, and to
craft a series of recommendations that would minimize the harm done.  One
vendor in particular deliberately ignored those recommendations.  It also 
produced mail readers that didn't properly label content on outgoing mail and
ignored the content-type parameter on incoming mail, instead looking at the
suffix of a nonstandard "filename" parameter (which was only intended for use
with application/octet-stream).  When I was on IESG, a program manager with
that company (in charge of an email product) assured me that this decision was
deliberate, as it was thought that it would maximize their company's
penetration in the market.  Obviously, it did serve that end, and other
vendors of mail readers for that platform were forced to emulate (to some
degree) the nonstandard and dangerous behavior of the market leader's
products.

This decision has cost the network billions of dollars, including significant
costs to people who do not use that company's software products (and who
therefore aren't bound by its EULAs).

Words that come to mind to describe this include: Willful, Criminal, and
Negligence.  Another word that comes to mind:  Prison.  As in "some people need
to spend a lot of time there".




From owner-ietf@ietf.org  Sat Aug 30 01:24: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 BAA10719
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 01:24:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19sy7a-0001xV-CJ
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 01:17:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19sy6Y-0001oG-Om
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 01:16:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10167
	for <ietf@ietf.org>; Sat, 30 Aug 2003 01:16:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19sy6W-0007Zi-00
	for ietf@ietf.org; Sat, 30 Aug 2003 01:16: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 19sy6V-0007Zb-00
	for ietf@ietf.org; Sat, 30 Aug 2003 01:16:52 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19sc50-000126-00; Fri, 29 Aug 2003 01:45:50 -0400
Date: Fri, 29 Aug 2003 01:45:43 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Christian Huitema <huitema@windows.microsoft.com>
cc: Valdis.Kletnieks@vt.edu, David Frascone <dave@frascone.com>,
        <ietf@ietf.org>
Subject: RE: FW: Virus alert 
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA04EE2557@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Message-ID: <Pine.LNX.4.44.0308290138490.3954-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 29 Aug 2003, Christian Huitema wrote:

> >> Can't we just hack the mailman configs to dump mails with X-sender
> value
> >> of outlook or outlook express?  That would solve the problem, no;)
> >
> > Well, the only problem with that idea is that we explicitly do *NOT*
> have > a "Your clue must be ->THIS<- tall to ride the IETF list"
> policy... ;)
>
> The Sobig worm includes its own SMTP code, and places arbitrary values
> in the header fields.

You mean to say that there is a full MTA tucked away in there?


> The source address is forged, and so are various
> other fields, including X-Mailer.

Perhaps you misunderstood my intentions.  My intentions accociated with
this post had nothing to do with the worm.


> The worm finds target source and
> destination addresses by reading files on the user's disk, not by using
> a specific Outlook or OE API. It propagates by "social engineering",
> when users open some executable attachments.

Since when is social engineering a desktop activity.  The last time I
checked, social engineering was along the lines of thank you for the shiny
new job, now i'm going to hide a rouge server on your network.

> User can do click on
> attachments with many mailers, not just Outlook and OE. In fact, the
> latest versions of Outlook automatically strip such attachments.
>

I'm glad I don't have to click on my mail.


> -- Christian Huitema
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81/




From owner-ietf@ietf.org  Sat Aug 30 02:50: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 CAA26465
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 02:50:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19szQr-0005Oh-IZ
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 02:41:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19szP1-0005Ei-TL
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 02:40:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25794
	for <ietf@ietf.org>; Sat, 30 Aug 2003 02:39:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19szOz-000244-00
	for ietf@ietf.org; Sat, 30 Aug 2003 02:40:01 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 19szOy-000240-00
	for ietf@ietf.org; Sat, 30 Aug 2003 02:40:00 -0400
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308300626.PAA05748@necom830.hpcl.titech.ac.jp>
Received: from mohta@localhost by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id PAA05748; Sat, 30 Aug 2003 15:26:39 +0900
Subject: Re: Criminals
In-Reply-To: <20030830000942.2a8df81f.moore@cs.utk.edu> from Keith Moore at "Aug
 30, 2003 00:09:42 am"
To: Keith Moore <moore@cs.utk.edu>
Date: Sat, 30 Aug 2003 15:26:38 +0859 ()
CC: Christian Huitema <huitema@windows.microsoft.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-ietf@ietf.org
Precedence: bulk

Keith;

MIME developers are.

MIME is too much e-mail centric.

Whether one use content-type or file name is irrelevant to mail
security, just as whether one use uuencode or base64 is
irrelevant, on both of which MIME developers wasted a lot of time.

> It also 
> produced mail readers that didn't properly label content on outgoing mail and
> ignored the content-type parameter on incoming mail, instead looking at the
> suffix of a nonstandard "filename" parameter (which was only intended for use
> with application/octet-stream).

On most OSes, including but not limited to UNIX, that's the way to
designate content types of files.

MIME should have followed the practice and IANA could be the central
authority to register filename extensions with their possible security
holes.

Instead, MIME developers arrogantly claimed that OSes should be
modified to support MIME content-type (and even that text files
on OSes should use MIME format to support other tags such as
charset).

Rest of us righteously ignored it.

> Words that come to mind to describe this include: Willful, Criminal, and
> Negligence.

Exactly. But, see above.

							Masataka Ohta



From owner-ietf@ietf.org  Sat Aug 30 03:29: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 DAA28416
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 03:29:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19t07Q-0008MV-KN
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 03:25:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19t06Y-0008Is-0f
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 03:25: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 DAA28174
	for <ietf@ietf.org>; Sat, 30 Aug 2003 03:24:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19t06V-0003Nb-00
	for ietf@ietf.org; Sat, 30 Aug 2003 03:24:59 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19t06V-0003NW-00
	for ietf@ietf.org; Sat, 30 Aug 2003 03:24:59 -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 h7U7PGxS049026;
	Sat, 30 Aug 2003 09:25:16 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Sat, 30 Aug 2003 09:24:53 +0200
Subject: Re: where the indirection layer belongs
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Keith Moore <moore@cs.utk.edu>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <20030829170627.49778fa0.moore@cs.utk.edu>
Message-Id: <0C72D372-DABB-11D7-B146-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, aug 29, 2003, at 23:06 Europe/Amsterdam, Keith Moore wrote:

>> It's not uncommon to see a FQDN point to several IP addresses so that
>> the service identified by the FQDN can be provided either by

>> (a) multiple hosts, or
>> (b) a host with multiple addresses.

> No.  A client can't tell whether multiple addresses associated with an
> DNS name indicate multiple hosts or multiple addresses for the same
> host.

Right. And a session can't jump from one address to another either. So 
when we implement the latter, we also address the former.

>> As a member of the multi6 design team that works on a (b) solution I'm
>> convinced that such a solution will provide many benefits and should
>> be developed and implemented.

> And I'm equally convinced that a solution that assumes (b) is a
> nonstarter.  There is already too much practice that conflicts with
> it.

To be more precise: the idea is to have transport sessions move from 
one address to another when there is a rehoming event. Obviously there 
will be changes to the process of publishing additional addresses.

>> It would make sense to
>> create something new that sits between the transport(s) and the
>> application, and delegate some tasks that are done by applications
>> today, most notably name resolution. This allows us to implement new
>> namespaces or new address formats without any pain

> No it doesn't.  What it allows "us" to do is impose subtle changes in
> the behavior of lower layers, and introduce new failure modes, without
> giving applications any way to deal with them.

Well if we make a new API that allows applications to set up sessions 
based on FQDNs, and then later we decide that the next version of IP 
really needs variable length addresses where the address length in bits 
is a prime number, existing applications _should_ continue to work. 
Experience shows there are always cases where things aren't as simple 
as all this in practice, but I don't see how this can be worse than 
being 100% positive that the applications won't work and must be 
changed to support the new address format.

>> But the real question here is: does this new "thing" have to be a
>> layer?

> It depends on which "thing" you are talking about.

New API and/or mechanisms to distribute operations over multiple hosts.

> For the L3-L4 thing, it's either a new layer or a change to an 
> existing layer.

Agree: both ends must cooperate, so a layer (new or modifications to an 
existing one) makes sense.

> If you have both the L4-L7 thing and the L3-L4 thing, the former is 
> either a new layer or (my personal opinion) a new API that 
> knowledgable apps
> call explicitly.

Right, and API != layer.




From owner-ietf@ietf.org  Sat Aug 30 05:43: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 FAA04378
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 05:43:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19t29E-0007aa-Ew
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 05:35:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19t28X-0007Wh-NP
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 05:35: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 FAA04139
	for <ietf@ietf.org>; Sat, 30 Aug 2003 05:35:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19t28V-0006pA-00
	for ietf@ietf.org; Sat, 30 Aug 2003 05:35:11 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19t28U-0006p7-00
	for ietf@ietf.org; Sat, 30 Aug 2003 05:35:10 -0400
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id KAA11819;
	Sat, 30 Aug 2003 10:35:09 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id KAA02937;
	Sat, 30 Aug 2003 10:35:08 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h7U9Z8h29089;
	Sat, 30 Aug 2003 10:35:08 +0100
Date: Sat, 30 Aug 2003 10:35:08 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Valdis.Kletnieks@vt.edu
Cc: "A. Kremer" <inanbe@xs4all.nl>, ietf@ietf.org
Subject: Re: Virus alert
Message-ID: <20030830093508.GE28816@login.ecs.soton.ac.uk>
References: <000401c36e7a$67dc1d50$5001a8c0@thelady> <200308292323.h7TNNTm8010320@turing-police.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200308292323.h7TNNTm8010320@turing-police.cc.vt.edu>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, Aug 29, 2003 at 07:23:29PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Sat, 30 Aug 2003 00:10:50 +0200, "A. Kremer" <inanbe@xs4all.nl>  said:
> 
> > ---
> > Incoming mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.512 / Virus Database: 309 - Release Date: 19-8-2003
> 
> And every single copy of Sobig-F goes out with the header:
> 
> X-MailScanner: Found to be clean
> 
> What's wrong with this picture?

Well, as the group that made MailScanner, we take the presence of that line 
as a great compliment by the virus writer :)

Aside:  MailScanner (which is open source and free) is one of few gateway
spam/virus detectors that can cater for those virii that forge email From:
headers so that warnings do not erroneously go back to the forged sender.   

See www.mailscanner.info if you're interested.

Tim



From owner-ietf@ietf.org  Sat Aug 30 08:06: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 IAA08809
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 08:06:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19t4Ou-0007xB-PN
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 08:00:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19t4Ng-0007tS-O6
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 07:59: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 HAA08482
	for <ietf@ietf.org>; Sat, 30 Aug 2003 07:58:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19t4Ng-0002K5-00
	for ietf@ietf.org; Sat, 30 Aug 2003 07:59:00 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19t4Nf-0002K1-00
	for ietf@ietf.org; Sat, 30 Aug 2003 07:58:59 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 8735314066; Sat, 30 Aug 2003 07:58:59 -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 01667-15; Sat, 30 Aug 2003 07:58: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 8CAF313FB0; Sat, 30 Aug 2003 07:58:58 -0400 (EDT)
Date: Sat, 30 Aug 2003 07:56:44 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: where the indirection layer belongs
Message-Id: <20030830075644.6853c58a.moore@cs.utk.edu>
In-Reply-To: <0C72D372-DABB-11D7-B146-00039388672E@muada.com>
References: <20030829170627.49778fa0.moore@cs.utk.edu>
	<0C72D372-DABB-11D7-B146-00039388672E@muada.com>
X-Mailer: Sylpheed version 0.9.3 (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

> To be more precise: the idea is to have transport sessions move from 
> one address to another when there is a rehoming event. Obviously there 
> will be changes to the process of publishing additional addresses.

I'm also interested in ways of doing this.  I just don't think it's 
appropriate to use FQDNs as the identifiers.

Keith



From owner-ietf@ietf.org  Sat Aug 30 13:02: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 NAA20810
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 13:02:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19t8x9-000775-4G
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 12:51:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19t8ws-00073M-Sz
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 12:51: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 MAA20554
	for <ietf@ietf.org>; Sat, 30 Aug 2003 12:51:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19t8wr-0001lC-00
	for ietf@ietf.org; Sat, 30 Aug 2003 12:51:37 -0400
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx with esmtp (Exim 4.12)
	id 19t8wq-0001ky-00
	for ietf@ietf.org; Sat, 30 Aug 2003 12:51:37 -0400
Received: from inet-vrs-01.redmond.corp.microsoft.com ([157.54.8.27]) by mail1.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 30 Aug 2003 09:51:05 -0700
Received: from 157.54.5.25 by inet-vrs-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Sat, 30 Aug 2003 09:51:05 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 30 Aug 2003 09:51:05 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 30 Aug 2003 09:51:04 -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.0);
	 Sat, 30 Aug 2003 09:49:33 -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: FW: Virus alert 
Date: Sat, 30 Aug 2003 09:50:50 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA04EE2581@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: FW: Virus alert 
thread-index: AcNutfoo3Qtmg83sSeOvGvlpPQgPEwAXtpDQ
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "shogunx" <shogunx@sleekfreak.ath.cx>
Cc: <Valdis.Kletnieks@vt.edu>, "David Frascone" <dave@frascone.com>,
        <ietf@ietf.org>
X-OriginalArrivalTime: 30 Aug 2003 16:49:33.0603 (UTC) FILETIME=[B0674F30:01C36F16]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


>> >> Can't we just hack the mailman configs to dump mails with X-sender
>> value
>> >> of outlook or outlook express?  That would solve the problem, no;)
>> >
>> > Well, the only problem with that idea is that we explicitly do
*NOT*
>> have > a "Your clue must be ->THIS<- tall to ride the IETF list"
>> policy... ;)
>>
>> The Sobig worm includes its own SMTP code, and places arbitrary
values
>> in the header fields.
>
> You mean to say that there is a full MTA tucked away in there?

Yes. Maybe not a full MTA, but definitely enough to format messages and
execute SMTP. The common assumption is that Sobig was written by one or
several criminals, with the purpose of installing a network of mail
relays "zombies", and then to sell the services of this network of
zombies to spammers. The same SMTP agent is probably also used to send
spam from the zombies. If you compare the headers of mail generated by
the worm and those of random spam, you will find that they are very
similar.=20

There is another link between Sobig and spam. It appears that these
networks of zombies are used in denial of service attacks against
anti-spam services.=20

By the way, the worm does not only include its own SMTP service. It
seems to also include its own DNS code, probably in order to get the MX
records of its targets. This DNS agent is parameterized to start any
look-up at the A-root, with the side effect of overloading this root
server.

-- Christian Huitema




From owner-ietf@ietf.org  Sat Aug 30 13:02: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 NAA20827
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 13:02:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19t92x-0007TV-BV
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 12:57:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19t92c-0007Pg-GT
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 12:57: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 MAA20640
	for <ietf@ietf.org>; Sat, 30 Aug 2003 12:57:27 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19t92a-0001ug-00
	for ietf@ietf.org; Sat, 30 Aug 2003 12:57:33 -0400
Received: from h80ad269d.async.vt.edu ([128.173.38.157] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19t92Z-0001ud-00
	for ietf@ietf.org; Sat, 30 Aug 2003 12:57:31 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta3/8.12.10.Beta3) with ESMTP id h7UGvJiM015668;
	Sat, 30 Aug 2003 12:57:19 -0400
Message-Id: <200308301657.h7UGvJiM015668@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: Keith Moore <moore@cs.utk.edu>,
        Christian Huitema <huitema@windows.microsoft.com>, ietf@ietf.org
Subject: Re: Criminals 
In-Reply-To: Your message of "Sat, 30 Aug 2003 15:26:38 +0859."
             <200308300626.PAA05748@necom830.hpcl.titech.ac.jp> 
References: <200308300626.PAA05748@necom830.hpcl.titech.ac.jp>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_2045139354P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 30 Aug 2003 12:57:19 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sat, 30 Aug 2003 15:26:38 +0859, Masataka Ohta said:
> MIME is too much e-mail centric.

For an E-mail centric protocol, it's worked pretty well on port 80....

> On most OSes, including but not limited to UNIX, that's the way to
> designate content types of files.

But it's not *universally* true, so you have to come up with some sideband
way of conveying information.  And in fact, even if two systems both
support extensions as a *mandatory* flagging, you can still run into
trouble - what if the two systems don't use the *same* extension for
a filetype that should be portable?  Should a postscript file end in .PS,
.ps, .PST?  Should a VisualBasic script be .VB or .VBS?  Is a image/jpeg
file a .JPG or .JPEG?

And if extensions are non-mandatory, it's just a mess.  Think about the
security implications of "Here's an executable called foo.JPG" (Microsoft
didn't - that's the basic cause of MS03-032).

> Instead, MIME developers arrogantly claimed that OSes should be
> modified to support MIME content-type (and even that text files
> on OSes should use MIME format to support other tags such as
> charset).

No.

This claim is right up there with "SMTP developers arrogantly claimed
that OSs should be modified to support network-standard EOL".

And of course they didn't.  They merely insisted that the user agent at
either end convert to/from the local format.

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

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

iD8DBQE/UNducC3lWbTT17ARAiNZAKDwcWp+FAhDvyMpmogSY06DnUM/jgCcClqT
dvzNQFbbrVWC2KO4kOWykZo=
=AVC5
-----END PGP SIGNATURE-----

--==_Exmh_2045139354P--



From owner-ietf@ietf.org  Sat Aug 30 13:37: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 NAA22366
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 13:37:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19t9bo-00027Q-Va
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 13:33:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19t9bi-00023c-8f
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 13:33: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 NAA22186
	for <ietf@ietf.org>; Sat, 30 Aug 2003 13:33:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19t9bf-0002z5-00
	for ietf@ietf.org; Sat, 30 Aug 2003 13:33:47 -0400
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 19t9bf-0002z0-00
	for ietf@ietf.org; Sat, 30 Aug 2003 13:33:47 -0400
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 19t9be-0005FF-00
	for <ietf@ietf.org>; Sat, 30 Aug 2003 18:33:46 +0100
Date: Sat, 30 Aug 2003 18:33:45 +0100
To: ietf@ietf.org
Subject: Re: FW: Virus alert
Message-ID: <20030830173345.GA18591@fysh.org>
References: <DAC3FCB50E31C54987CD10797DA511BA04EE2581@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA04EE2581@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

Christian Huitema wrote:
>By the way, the worm does not only include its own SMTP service. It
>seems to also include its own DNS code, probably in order to get the MX
>records of its targets. This DNS agent is parameterized to start any
>look-up at the A-root, with the side effect of overloading this root
>server.

Does this mean we can stop the virus and associated spam just by switching
off the A root?

-zefram



From owner-ietf@ietf.org  Sat Aug 30 14:19: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 OAA23770
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 14:19:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tAEV-00059B-1F
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 14:13:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tADx-000554-J5
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 14:13: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 OAA23516
	for <ietf@ietf.org>; Sat, 30 Aug 2003 14:13:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tADw-0003op-00
	for ietf@ietf.org; Sat, 30 Aug 2003 14:13:20 -0400
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tADv-0003oX-00
	for ietf@ietf.org; Sat, 30 Aug 2003 14:13:19 -0400
Received: from mail6.microsoft.com ([157.54.6.196]) by mail4.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 30 Aug 2003 11:13:02 -0700
Received: from inet-vrs-06.redmond.corp.microsoft.com ([157.54.6.181]) by mail6.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 30 Aug 2003 11:12:44 -0700
Received: from 157.54.8.23 by inet-vrs-06.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Sat, 30 Aug 2003 11:12:45 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 30 Aug 2003 11:12:43 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 30 Aug 2003 11:12:44 -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.0);
	 Sat, 30 Aug 2003 11:11:00 -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: FW: Virus alert
Date: Sat, 30 Aug 2003 11:12:43 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA04EE258C@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: FW: Virus alert
thread-index: AcNvHcOQ25Aix+QiR0KLu2Lw0jMnkAABCToQ
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Zefram" <zefram@fysh.org>, <ietf@ietf.org>
X-OriginalArrivalTime: 30 Aug 2003 18:11:01.0139 (UTC) FILETIME=[119A1E30:01C36F22]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

>> By the way, the worm does not only include its own SMTP service. It
>> seems to also include its own DNS code, probably in order to get the
MX
>> records of its targets. This DNS agent is parameterized to start any
>> look-up at the A-root, with the side effect of overloading this root
>> server.
>
> Does this mean we can stop the virus and associated spam just by
switching
> off the A root?

I would suggest that you engage in serious testing before trying
anything like that!=20

-- Christian Huitema




From owner-ietf@ietf.org  Sat Aug 30 14:29: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 OAA24364
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 14:29:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tAQ6-0006MF-IQ
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 14:25:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tAPd-0006IP-4n
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 14:25: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 OAA24205
	for <ietf@ietf.org>; Sat, 30 Aug 2003 14:25:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tAPc-00049P-00
	for ietf@ietf.org; Sat, 30 Aug 2003 14:25:24 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tAPb-00047N-00
	for ietf@ietf.org; Sat, 30 Aug 2003 14:25:23 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h7UIPK1j006012
	for ietf@ietf.org env-from <vjs>;
	Sat, 30 Aug 2003 12:25:20 -0600 (MDT)
Date: Sat, 30 Aug 2003 12:25:20 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200308301825.h7UIPK1j006012@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: FW: Virus alert
References: <DAC3FCB50E31C54987CD10797DA511BA04EE2581@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Christian Huitema" <huitema@windows.microsoft.com>

> ...
> Yes. Maybe not a full MTA, but definitely enough to format messages and
> execute SMTP. ...

What do you mean by "execute SMTP"?  Does it interpret and respond to
SMTP response codes to its SMTP commands or just open a TCP connection
and send a largely constant handful of lines of text before the first
header line?  The samples I've captured have pretty rudimentary SMTP
envelopes.

> ...
> By the way, the worm does not only include its own SMTP service. It
> seems to also include its own DNS code, probably in order to get the MX
> records of its targets. ...

That would be far more impresssive, although given the many resolver
libraries available, nothing to write home about.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sat Aug 30 15:25: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 PAA27542
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 15:25:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tBFO-0001aF-FT
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 15:18:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tBBv-0000bF-Jn
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 15:15: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 PAA26987
	for <ietf@ietf.org>; Sat, 30 Aug 2003 15:15:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tBBu-0005KF-00
	for ietf@ietf.org; Sat, 30 Aug 2003 15:15:18 -0400
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tBBt-0005K4-00
	for ietf@ietf.org; Sat, 30 Aug 2003 15:15:17 -0400
Received: from mobilebill (12-225-210-60.client.attbi.com[12.225.210.60](untrusted sender))
          by attbi.com (rwcrmhc12) with SMTP
          id <2003083019091801400sorf2e>; Sat, 30 Aug 2003 19:09:18 +0000
From: "bill" <bill@strahm.net>
To: "'Christian Huitema'" <huitema@windows.microsoft.com>,
        "'Zefram'" <zefram@fysh.org>, <ietf@ietf.org>
Subject: Testing Root A going away
Date: Sat, 30 Aug 2003 12:08:57 -0700
Message-ID: <005b01c36f2a$2bd82140$6501a8c0@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.2627
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA04EE258C@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.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

Didn't J Postel run a test similar to that once <G>...

On a side note, how would you go about testing something like this ?

What would be considered pass/fail metrics - well written applications
vs. people doing silly and stupid things (ie. Would it be consisdered a
failrue that sobig fails because it was incorrectly written ?)

Bill

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of
Christian Huitema
Sent: Saturday, August 30, 2003 11:13 AM
To: Zefram; ietf@ietf.org
Subject: RE: FW: Virus alert


>> By the way, the worm does not only include its own SMTP service. It 
>> seems to also include its own DNS code, probably in order to get the
MX
>> records of its targets. This DNS agent is parameterized to start any 
>> look-up at the A-root, with the side effect of overloading this root 
>> server.
>
> Does this mean we can stop the virus and associated spam just by
switching
> off the A root?

I would suggest that you engage in serious testing before trying
anything like that! 

-- Christian Huitema






From owner-ietf@ietf.org  Sat Aug 30 15:31: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 PAA28019
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 15:31:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tBP5-0002gu-2J
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 15:28:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tBOw-0002b4-Fh
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 15:28: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 PAA27805
	for <ietf@ietf.org>; Sat, 30 Aug 2003 15:28:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tBOu-0005i0-00
	for ietf@ietf.org; Sat, 30 Aug 2003 15:28:45 -0400
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tBOu-0005gY-00
	for ietf@ietf.org; Sat, 30 Aug 2003 15:28:44 -0400
Received: from mail6.microsoft.com ([157.54.6.196]) by mail1.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 30 Aug 2003 12:28:09 -0700
Received: from inet-vrs-06.redmond.corp.microsoft.com ([157.54.6.181]) by mail6.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 30 Aug 2003 12:28:05 -0700
Received: from 157.54.6.197 by inet-vrs-06.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Sat, 30 Aug 2003 12:28:03 -0700
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by INET-HUB-06.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 30 Aug 2003 12:28:01 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 30 Aug 2003 12:28:04 -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.0);
	 Sat, 30 Aug 2003 12:26:07 -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: Testing Root A going away
Date: Sat, 30 Aug 2003 12:28:00 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA04EE2599@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Testing Root A going away
thread-index: AcNvKvlNQfI10iPmT4qW1gDu3dNYwQAAPGVg
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "bill" <bill@strahm.net>, "Zefram" <zefram@fysh.org>, <ietf@ietf.org>
X-OriginalArrivalTime: 30 Aug 2003 19:26:07.0893 (UTC) FILETIME=[8FD63450:01C36F2C]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


> Didn't J Postel run a test similar to that once <G>...
>=20
> On a side note, how would you go about testing something like this ?

Obviously, cutting of the A root would have some pretty drastic
consequences. On the other hand, there are many computers that have no
business contacting directly the root servers. For example, in many
enterprises and campuses, computers are suppose to send their DNS
traffic to a configured relay.=20

> What would be considered pass/fail metrics - well written applications
> vs. people doing silly and stupid things (ie. Would it be consisdered
a
> failrue that sobig fails because it was incorrectly written ?)

Looking at bugs in worms and using these bugs to squash the worms is
fair game. Another known bug is the SMTP Hello line always contains a
single token host name, instead of an FQDN. However, it is very likely
that such bugs will be corrected in a next release -- say, Sobig.G.=20

The better question for the IETF is whether we should do something to
SMTP to make it less easy to send spoofed mail.

-- Christian Huitema




From owner-ietf@ietf.org  Sat Aug 30 16:56: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 QAA01400
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 16:56:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tCgQ-0000QP-FF
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 16:50:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tCfr-0000Ls-1h
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 16:50: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 QAA01173
	for <ietf@ietf.org>; Sat, 30 Aug 2003 16:50:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tCfp-0007kP-00
	for ietf@ietf.org; Sat, 30 Aug 2003 16:50:17 -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 19tCfn-0007kL-00
	for ietf@ietf.org; Sat, 30 Aug 2003 16:50:17 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19sqdc-0001qt-00; Fri, 29 Aug 2003 17:18:32 -0400
Date: Fri, 29 Aug 2003 17:17:53 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Christian Huitema <huitema@windows.microsoft.com>
cc: bill <bill@strahm.net>, Zefram <zefram@fysh.org>, <ietf@ietf.org>
Subject: RE: Testing Root A going away
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA04EE2599@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Message-ID: <Pine.LNX.4.44.0308291716430.7121-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

>
> The better question for the IETF is whether we should do something to
> SMTP to make it less easy to send spoofed mail.

what, so one couldn't telnet in and send arbitrary mail?  include a
reversedns lookup in SMTP?  good luck on widespread implementation.


>
> -- Christian Huitema
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81/




From owner-ietf@ietf.org  Sat Aug 30 17:01: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 RAA01759
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 17:01:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tCoJ-0001Gm-JB
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 16:59:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tCk6-0000hw-Bz
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 16:54: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 QAA01323
	for <ietf@ietf.org>; Sat, 30 Aug 2003 16:54:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tCk5-0007nm-00
	for ietf@ietf.org; Sat, 30 Aug 2003 16:54:41 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tCk4-0007ng-00
	for ietf@ietf.org; Sat, 30 Aug 2003 16:54:40 -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 h7UKsvxS057556;
	Sat, 30 Aug 2003 22:54:59 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Sat, 30 Aug 2003 22:54:34 +0200
Subject: Re: Testing Root A going away
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "Christian Huitema" <huitema@windows.microsoft.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA04EE2599@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Message-Id: <295E6FA0-DB2C-11D7-B146-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, aug 30, 2003, at 21:28 Europe/Amsterdam, Christian Huitema 
wrote:

> Obviously, cutting of the A root would have some pretty drastic
> consequences.

If that is the case then some people have been reading the relevant 
RFCs with their eyes closed. The only consequence should some sporadic 
short delays when a resolver asks the A but there is no answer so there 
is a timeout and one of the other root servers must be consulted.

> On the other hand, there are many computers that have no
> business contacting directly the root servers. For example, in many
> enterprises and campuses, computers are suppose to send their DNS
> traffic to a configured relay.

How would that make a difference, other than that a central resolver 
can cache more efficiently? If a host needs a domain in a 
not-yet-cached TLD resolved, then someone somewhere has to ask one of 
the root servers for the information about this TLD, whether this is 
the host that needs the information or some other system working on 
behalf of this host.

> The better question for the IETF is whether we should do something to
> SMTP to make it less easy to send spoofed mail.

Well, draft-fecyk-dsprotocol-04.txt is in the RFC editor queue and this 
seems like a fair step in the good direction, without heaving read it 
in detail. So unless this is no good it should be shipped as and RFC 
and then the ball is in the vendors' court.




From owner-ietf@ietf.org  Sat Aug 30 17:35: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 RAA03088
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 17:35:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tDJ8-0004DL-DJ
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 17:30:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tDBP-0003hH-Vs
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 17:22: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 RAA02719
	for <ietf@ietf.org>; Sat, 30 Aug 2003 17:22:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tDBO-0000xi-00
	for ietf@ietf.org; Sat, 30 Aug 2003 17:22:54 -0400
Received: from bean.ar.com ([66.123.187.68])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tDBN-0000xM-00
	for ietf@ietf.org; Sat, 30 Aug 2003 17:22:53 -0400
Received: from flash.ar.com (wessorh@flash [66.123.187.80])
	by bean.ar.com (8.12.6/8.12.6) with ESMTP id h7ULLXjT023416;
	Sat, 30 Aug 2003 14:21:33 -0700 (PDT)
Date: Sat, 30 Aug 2003 14:22:18 -0700 (PDT)
From: Rick Wesson <wessorh@ar.com>
To: Christian Huitema <huitema@windows.microsoft.com>
cc: bill <bill@strahm.net>, Zefram <zefram@fysh.org>, <ietf@ietf.org>
Subject: RE: Testing Root A going away
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA04EE2599@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Message-ID: <Pine.LNX.4.33.0308301420320.363-100000@flash.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 30 Aug 2003, Christian Huitema wrote:

[snip]

> Obviously, cutting of the A root would have some pretty drastic
> consequences. On the other hand, there are many computers that have no
> business contacting directly the root servers. For example, in many
> enterprises and campuses, computers are suppose to send their DNS
> traffic to a configured relay.

not realy. If 'A' stops answering you'll just ask questions of the others.
The issue is not if 'A' goes off the air, there are always other servers
to talk to.

-rick





From owner-ietf@ietf.org  Sat Aug 30 17:36: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 RAA03247
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 17:36:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tDM2-0004R9-L2
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 17:33:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tDLN-0004Ma-DQ
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 17:33: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 RAA03025
	for <ietf@ietf.org>; Sat, 30 Aug 2003 17:33:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tDLL-00014T-00
	for ietf@ietf.org; Sat, 30 Aug 2003 17:33:11 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19tDLL-00014O-00
	for ietf@ietf.org; Sat, 30 Aug 2003 17:33:11 -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 RAA28836;
	Sat, 30 Aug 2003 17:25:11 -0400
Date: Sat, 30 Aug 2003 17:25:19 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: David Frascone <dave@frascone.com>
cc: ietf@ietf.org
Subject: Re: FW: Virus alert
In-Reply-To: <20030830003044.GW24424@wolverine>
Message-ID: <Pine.LNX.4.44.0308301700140.548-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Fri, 29 Aug 2003, David Frascone wrote:

> With the current virii usually forging the from field with random
> addresses from its victim's address book, I turned off my virus
> scanner's warning to the senders . . I only send a polite note to the
> intended recipient.

Don't do that. That is quite likely what the Virus writer wants you to do:
Stop notifying people about infections.  The worst that happens is that
people get notifications, and update their anti-virus, which finds
nothing.  The best that happens is that the headers included in such a
notification reveal the IP address of an infected zombie.

Also, in the current cases, I don't think the addresses aren't taken from
address books.  I'm getting responses to addresses that haven't been used
for email and addresses that haven't been used in years. Certainly, these
aren't in anyone's address book.  In one case, the address is on a little
used web site (but even spammers rarely spam it, and in another, its in a
reasonably public area, but not used)

The Virus writer obviously went to some trouble to pick valid addresses.
It stands to reason that they expect that someone is getting mail to these
addresses.  It also stands to reason that the abuser expects those persons
to get Virus notifications.

Most probably, virus notifications tend to frustrate the purposes of
the Virus operator, since the infected will not stay infected. It seems
possible that the virus operators are trying to manipulate people to stop
sending or responding to virus notifications.

In past cases, the forged from address was the target of the abuse: the
abuser hoped to have people block mail with the common from address, thus
getting some measure of revenge on that person.  Most people have
filtering on From: addresses for this reason.

The best thing to do in response to such an attack is to do things that
frustrate purposes the abuser, catch the abuser, or nothing at all.
Never succumb to what might be a desired manipulation--That only
encourages more abuse.


		--Dean





From owner-ietf@ietf.org  Sat Aug 30 17:48: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 RAA03707
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 17:48:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tDXf-00069n-4B
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 17:45:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tDXE-00064b-JE
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 17:45:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03635
	for <ietf@ietf.org>; Sat, 30 Aug 2003 17:45:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tDXD-0001VW-00
	for ietf@ietf.org; Sat, 30 Aug 2003 17:45:27 -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 19tDX7-0001VF-00
	for ietf@ietf.org; Sat, 30 Aug 2003 17:45:23 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19srUi-0001sn-00; Fri, 29 Aug 2003 18:13:24 -0400
Date: Fri, 29 Aug 2003 18:12:50 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Dean Anderson <dean@av8.com>
cc: David Frascone <dave@frascone.com>, <ietf@ietf.org>
Subject: Re: FW: Virus alert
In-Reply-To: <Pine.LNX.4.44.0308301700140.548-100000@vista.av8.net>
Message-ID: <Pine.LNX.4.44.0308291811490.7240-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 30 Aug 2003, Dean Anderson wrote:

How beautiful to be immune behind an open-source kernel;)  The rest of the
world worries.  I eat a sandwich.

Scott


>
>
> On Fri, 29 Aug 2003, David Frascone wrote:
>
> > With the current virii usually forging the from field with random
> > addresses from its victim's address book, I turned off my virus
> > scanner's warning to the senders . . I only send a polite note to the
> > intended recipient.
>
> Don't do that. That is quite likely what the Virus writer wants you to do:
> Stop notifying people about infections.  The worst that happens is that
> people get notifications, and update their anti-virus, which finds
> nothing.  The best that happens is that the headers included in such a
> notification reveal the IP address of an infected zombie.
>
> Also, in the current cases, I don't think the addresses aren't taken from
> address books.  I'm getting responses to addresses that haven't been used
> for email and addresses that haven't been used in years. Certainly, these
> aren't in anyone's address book.  In one case, the address is on a little
> used web site (but even spammers rarely spam it, and in another, its in a
> reasonably public area, but not used)
>
> The Virus writer obviously went to some trouble to pick valid addresses.
> It stands to reason that they expect that someone is getting mail to these
> addresses.  It also stands to reason that the abuser expects those persons
> to get Virus notifications.
>
> Most probably, virus notifications tend to frustrate the purposes of
> the Virus operator, since the infected will not stay infected. It seems
> possible that the virus operators are trying to manipulate people to stop
> sending or responding to virus notifications.
>
> In past cases, the forged from address was the target of the abuse: the
> abuser hoped to have people block mail with the common from address, thus
> getting some measure of revenge on that person.  Most people have
> filtering on From: addresses for this reason.
>
> The best thing to do in response to such an attack is to do things that
> frustrate purposes the abuser, catch the abuser, or nothing at all.
> Never succumb to what might be a desired manipulation--That only
> encourages more abuse.
>
>
> 		--Dean
>
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81/




From owner-ietf@ietf.org  Sat Aug 30 18:15: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 SAA05642
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 18:15:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tDtu-0003zC-I0
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 18:08:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tDsX-0003Tp-7q
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 18:07: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 SAA04808
	for <ietf@ietf.org>; Sat, 30 Aug 2003 18:07:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tDsV-00026L-00
	for ietf@ietf.org; Sat, 30 Aug 2003 18:07:27 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19tDsU-000263-00
	for ietf@ietf.org; Sat, 30 Aug 2003 18:07:26 -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 SAA31065;
	Sat, 30 Aug 2003 18:03:51 -0400
Date: Sat, 30 Aug 2003 18:03:59 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: shogunx <shogunx@sleekfreak.ath.cx>
cc: Christian Huitema <huitema@windows.microsoft.com>, bill <bill@strahm.net>,
        Zefram <zefram@fysh.org>, <ietf@ietf.org>
Subject: RE: Testing Root A going away
In-Reply-To: <Pine.LNX.4.44.0308291716430.7121-100000@sleekfreak.ath.cx>
Message-ID: <Pine.LNX.4.44.0308301739200.548-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 29 Aug 2003, shogunx wrote:
> > The better question for the IETF is whether we should do something to
> > SMTP to make it less easy to send spoofed mail.
>
> what, so one couldn't telnet in and send arbitrary mail?  include a
> reversedns lookup in SMTP?  good luck on widespread implementation.

Reverse DNS lookups tell one nothing about the legitimacy of the email
being sent.  This has been hashed over on both namedroppers and DNSOP.

I also recently hashed out the Information Theoretic problems with
suppressing spam with a group of PhDs from one of my old companies.
After a great deal of arguing about the definition of Covert Channel (in
particular whether cooperation was required or not), it was determined (to
a high degree of confidence--but not to a formal proof) that spam is
indeed a covert channel, and therefore subject to the axiom that one
cannot prove there are no covert channels. I should note that during the
course of research I made to on the topic, which included reading a number
of original papers on the subject of Covert Channels, Side Channels, and
like concepts, I could find no written proof of this axiom, but neither
was it challenged as being untrue.

This confirms the intuition that digital signature schemes, and cost
schemes and other such suppression schemes cannot succeed.  Spam is
essentially dependent on the will of the sender, and given viruses, that
will can be subverted for many senders no matter what suppression scheme
is used. Spam can be detected, and stopped after detection, but it cannot
be made impossible to send.

The question is really whether SMTP has sufficient identification
information to track down an abuser, or infected user. The answer to this
question is "yes".  Even with an open proxy, the SMTP information will
identify the open proxy. The anonymity offered by the open proxy is
completely independent of SMTP.  However, to identify the abuser, one may
need law enforcement authority, or be willing to undertake a civil action
at some expense.  This is consistent with the PSTN, in which the identify
of a user can't generally be determined by another end user, but can
usually be determined using law enforcement authority.  Indeed, as with
the PSTN, some anonymity is appropriate.  One would probably not want to
allow end users to be able to identify another end user against their will
without a court order of some sort or some evidence of a criminal act.

		--Dean








From owner-ietf@ietf.org  Sat Aug 30 18:20: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 SAA06190
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 18:20:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tE2d-0007cs-7k
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 18:17:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tE1z-00078r-Sm
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 18:17: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 SAA06003
	for <ietf@ietf.org>; Sat, 30 Aug 2003 18:17:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tE1y-0002MU-00
	for ietf@ietf.org; Sat, 30 Aug 2003 18:17:14 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19tE1x-0002Lr-00
	for ietf@ietf.org; Sat, 30 Aug 2003 18:17: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 SAA21983;
	Sat, 30 Aug 2003 18:11:15 -0400
Date: Sat, 30 Aug 2003 18:11:23 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: shogunx <shogunx@sleekfreak.ath.cx>
cc: David Frascone <dave@frascone.com>, <ietf@ietf.org>
Subject: Re: FW: Virus alert
In-Reply-To: <Pine.LNX.4.44.0308291811490.7240-100000@sleekfreak.ath.cx>
Message-ID: <Pine.LNX.4.44.0308301809540.548-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Open source kernels aren't immune. They just aren't at focus this time.

Have fun with the sandwich. ;-)

		--Dean

On Fri, 29 Aug 2003, shogunx wrote:

> On Sat, 30 Aug 2003, Dean Anderson wrote:
>
> How beautiful to be immune behind an open-source kernel;)  The rest of the
> world worries.  I eat a sandwich.
>
> Scott




From owner-ietf@ietf.org  Sat Aug 30 19:38: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 TAA08413
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 19:38:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tFAI-0005J5-Vy
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 19:29:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tF85-00054S-AE
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 19:27: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 TAA08093
	for <ietf@ietf.org>; Sat, 30 Aug 2003 19:27:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tF83-00040M-00
	for ietf@ietf.org; Sat, 30 Aug 2003 19:27:35 -0400
Received: from mail2.asianet.co.th ([203.144.222.230] helo=mail.asianet.co.th)
	by ietf-mx with esmtp (Exim 4.12)
	id 19tF82-00040E-00
	for ietf@ietf.org; Sat, 30 Aug 2003 19:27:35 -0400
Received: from ppp-203.144.222.224.revip.asianet.co.th (HELO mail.asianet.co.th) ([203.144.222.224])
          (envelope-sender <jrace@attglobal.net>)
          by mail2.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 31 Aug 2003 06:26:57 +0700
Received: from ppp-203.144.202.216.revip.asianet.co.th (HELO localhost) ([203.144.202.216])
          (envelope-sender <jrace@attglobal.net>)
          by mx2.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <jrace@attglobal.net>; 31 Aug 2003 06:25:00 +0700
From: "Dr. Jeffrey Race" <jrace@attglobal.net>
To: "Jeffrey Race" <jrace@attglobal.net>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Date: Sun, 31 Aug 2003 06:26:54 +0700
Reply-To: "Dr. Jeffrey Race" <jrace@attglobal.net>
X-Mailer: PMMail 1.96a For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: RE: Testing Root A going away
Message-Id: <E19tF82-00040E-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Sat, 30 Aug 2003 18:03:59 -0400 (EDT), Dean Anderson wrote:
> Spam can be detected, and stopped after detection, but it cannot
>be made impossible to send.
>>The question is really whether SMTP has sufficient identification
>information to track down an abuser, or infected user. The answer to this
>question is "yes".  Even with an open proxy, the SMTP information will
>identify the open proxy.

You cannot prevent it from being sent ONCE and, as you have so elegantly
stated, no technical means will ever succeed in stopping spam.

But (as you say above) you can identify the upload path.  

The only solution is to shut down the upload path, which is the method
(generically speaking) that society at large uses to handle such problems. 
Those interested in this variant approach may wish to take a look at

 <http://www.camblab.com/nugget/spam_03.pdf> [the reasoning]

    and

 <http://www.camblab.com/misc/univ_std.txt>  [the fix].

On the sound basis, shown time over time in multiple industries, that
"quality is free", the variant approach I nominate will be essentially
costless.

I'd welcome any comments.

Jeffrey Race





From owner-ietf@ietf.org  Sat Aug 30 19:41: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 TAA08615
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 19:41:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tFJ9-00067d-A4
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 19:39:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tFED-0005az-Ii
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 19:33: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 TAA08254
	for <ietf@ietf.org>; Sat, 30 Aug 2003 19:33:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tFEB-0004CS-00
	for ietf@ietf.org; Sat, 30 Aug 2003 19:33:55 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tFEB-0004CP-00
	for ietf@ietf.org; Sat, 30 Aug 2003 19:33:55 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id CAEFB14174; Sat, 30 Aug 2003 19:33: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 12949-05; Sat, 30 Aug 2003 19:33: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 94A741407C; Sat, 30 Aug 2003 19:33:54 -0400 (EDT)
Date: Sat, 30 Aug 2003 19:31:39 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: moore@cs.utk.edu, huitema@windows.microsoft.com, ietf@ietf.org
Subject: Re: Testing Root A going away
Message-Id: <20030830193139.3d1a4bc0.moore@cs.utk.edu>
In-Reply-To: <295E6FA0-DB2C-11D7-B146-00039388672E@muada.com>
References: <DAC3FCB50E31C54987CD10797DA511BA04EE2599@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<295E6FA0-DB2C-11D7-B146-00039388672E@muada.com>
X-Mailer: Sylpheed version 0.9.3 (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 Sat, 30 Aug 2003 22:54:34 +0200
Iljitsch van Beijnum <iljitsch@muada.com> wrote:

> Well, draft-fecyk-dsprotocol-04.txt is in the RFC editor queue 

that's odd.  the document claims to be a candidate for proposed standard, but
the I-D tracker says "not assigned yet" under "shepherding AD".  and I haven't
seen any Last Call announcement nor any request for it to be reviewed
in the usual fora that discuss email topics (e.g. ietf-smtp).

so I think it has a ways to go before publication.



From owner-ietf@ietf.org  Sat Aug 30 20:07: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 UAA09375
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 20:07:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tFhC-0008Rm-2n
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 20:03:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tFVq-0007mQ-B9
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 19:52: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 TAA09013
	for <ietf@ietf.org>; Sat, 30 Aug 2003 19:52:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tFVo-0004cH-00
	for ietf@ietf.org; Sat, 30 Aug 2003 19:52:08 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tFVn-0004c9-00
	for ietf@ietf.org; Sat, 30 Aug 2003 19:52:07 -0400
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id AAA22404
	for <ietf@ietf.org>; Sun, 31 Aug 2003 00:52:07 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id AAA08391
	for <ietf@ietf.org>; Sun, 31 Aug 2003 00:52:07 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h7UNq7G05190
	for ietf@ietf.org; Sun, 31 Aug 2003 00:52:07 +0100
Date: Sun, 31 Aug 2003 00:52:06 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: FW: Virus alert
Message-ID: <20030830235206.GB5088@login.ecs.soton.ac.uk>
References: <20030830003044.GW24424@wolverine> <Pine.LNX.4.44.0308301700140.548-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.0308301700140.548-100000@vista.av8.net>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, Aug 30, 2003 at 05:25:19PM -0400, Dean Anderson wrote:
> 
> The Virus writer obviously went to some trouble to pick valid addresses.
> It stands to reason that they expect that someone is getting mail to these
> addresses.  It also stands to reason that the abuser expects those persons
> to get Virus notifications.

I don't think so; isn't it more likely the writer wants the infection to
spread, and the best chance for that is that the recipient sees a From:
address that they recognise and "trust", rather than kerjregj@jsfjkh.com,
so they look at the content where they otherwise would be wary?

I don't see a problem with notifications where the virus is known not to
forge the sender.

Tim



From owner-ietf@ietf.org  Sat Aug 30 20:07: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 UAA09391
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 20:07:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tFhB-0008Rb-Ob
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 20:03:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tFTk-0007kh-Ir
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 19:50: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 TAA08959
	for <ietf@ietf.org>; Sat, 30 Aug 2003 19:49:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tFTi-0004b8-00
	for ietf@ietf.org; Sat, 30 Aug 2003 19:49:58 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tFTh-0004b4-00
	for ietf@ietf.org; Sat, 30 Aug 2003 19:49:57 -0400
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308302341.IAA17929@necom830.hpcl.titech.ac.jp>
Received: from mohta@localhost by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id IAA17929; Sun, 31 Aug 2003 08:41:15 +0900
Subject: Re: Criminals
In-Reply-To: <200308301657.h7UGvJiM015668@turing-police.cc.vt.edu> from "(env:"
 "Valdis.Kletnieks@vt.edu)" at "Aug 30, 2003 12:57:19 pm"
To: Valdis.Kletnieks@vt.edu
Date: Sun, 31 Aug 2003 08:41:15 +0859 ()
CC: Keith Moore <moore@cs.utk.edu>,
        Christian Huitema <huitema@windows.microsoft.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-ietf@ietf.org
Precedence: bulk

Valdis;

> > MIME is too much e-mail centric.
> 
> For an E-mail centric protocol, it's worked pretty well on port 80....

MIME worked on port 80 only as well as pre-MIME 822.

MIME worked pretty badly with the rest of the OS.

All that was necessary is to document file name extensions such as
"tar", "uu" and "822" and email could have worked better with OS.
MIME complexities such as multipart and base64 is just a reinvention
of wheel.

> > On most OSes, including but not limited to UNIX, that's the way to
> > designate content types of files.
> 
> But it's not *universally* true, so you have to come up with some sideband
> way of conveying information.  And in fact, even if two systems both
> support extensions as a *mandatory* flagging, you can still run into
> trouble

No.

> - what if the two systems don't use the *same* extension for
> a filetype that should be portable?

It's just an issue of escaping.

Add, say, "X", if some extension is reserved on some OS.

> Should a postscript file end in .PS,
> .ps, .PST?  Should a VisualBasic script be .VB or .VBS?  Is a image/jpeg
> file a .JPG or .JPEG?

Should a MIME content type of postscript file be "PS", "ps", "PST",
"postscript" or "PostScript"? Should a VisualBasic script be "VB", "VBS"
or "visual-basic"?  Is a image/jpeg file a "JPG" or "JPEG"?

It's just an issue of registration and registration authority.

> > Instead, MIME developers arrogantly claimed that OSes should be
> > modified to support MIME content-type (and even that text files
> > on OSes should use MIME format to support other tags such as
> > charset).
> 
> No.
> 
> This claim is right up there with "SMTP developers arrogantly claimed
> that OSs should be modified to support network-standard EOL".

Wrong. It is not a line format issue but an issue of OS internal features.

MIME developers arrogantly assumes OSes should support file type
using MIME content type.

And poor OS developers, such as Microsoft, actually did so.

> And of course they didn't.  They merely insisted that the user agent at
> either end convert to/from the local format.

The local format does support ASCII file names but have no room
to store content type.

							Masataka Ohta




From owner-ietf@ietf.org  Sat Aug 30 23:46: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 XAA16068
	for <ietf-web-archive@odin.ietf.org>; Sat, 30 Aug 2003 23:46:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19tIyQ-0008WO-2W
	for ietf-list@asgard.ietf.org; Sat, 30 Aug 2003 23:33:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19tIxY-0008RB-4M
	for ietf@asgard.ietf.org; Sat, 30 Aug 2003 23:33: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 XAA15612
	for <ietf@ietf.org>; Sat, 30 Aug 2003 23:32:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19tIxV-0002FI-00
	for ietf@ietf.org; Sat, 30 Aug 2003 23:32:57 -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 19tIxS-0002F7-00
	for ietf@ietf.org; Sat, 30 Aug 2003 23:32:57 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19swvE-00023M-00; Sat, 30 Aug 2003 00:01:08 -0400
Date: Sat, 30 Aug 2003 00:00:45 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Dean Anderson <dean@av8.com>
cc: David Frascone <dave@frascone.com>, <ietf@ietf.org>
Subject: Re: FW: Virus alert
In-Reply-To: <Pine.LNX.4.44.0308301809540.548-100000@vista.av8.net>
Message-ID: <Pine.LNX.4.44.0308292359310.7891-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 30 Aug 2003, Dean Anderson wrote:

> Open source kernels aren't immune. They just aren't at focus this time.

If a worm is executing visual basic code, then i think i am pretty darn
immune.


>
> Have fun with the sandwich. ;-)
>

It was wonderful.

> 		--Dean
>
> On Fri, 29 Aug 2003, shogunx wrote:
>
> > On Sat, 30 Aug 2003, Dean Anderson wrote:
> >
> > How beautiful to be immune behind an open-source kernel;)  The rest of the
> > world worries.  I eat a sandwich.
> >
> > Scott
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81/




