From owner-ietf@ietf.org  Tue Jul  1 03:14:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01031
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Jul 2003 03:14:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19XF7D-0008LR-DR
	for ietf-list@asgard.ietf.org; Tue, 01 Jul 2003 02:59:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19XF6E-0008HP-K6
	for ietf@asgard.ietf.org; Tue, 01 Jul 2003 02:58: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 CAA16384
	for <ietf@ietf.org>; Tue, 1 Jul 2003 02:58:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XF6C-0000DM-00
	for ietf@ietf.org; Tue, 01 Jul 2003 02:58:44 -0400
Received: from web20714.mail.yahoo.com ([66.163.169.155])
	by ietf-mx with smtp (Exim 4.12)
	id 19XF5R-0000Cu-00
	for ietf@ietf.org; Tue, 01 Jul 2003 02:57:58 -0400
Message-ID: <20030701065657.5265.qmail@web20714.mail.yahoo.com>
Received: from [80.240.192.37] by web20714.mail.yahoo.com via HTTP; Mon, 30 Jun 2003 23:56:57 PDT
Date: Mon, 30 Jun 2003 23:56:57 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Re: A Quantum Cryptography ( QC ) Critique 
To: Valdis.Kletnieks@vt.edu, ietf@ietf.org
In-Reply-To: <200306301732.h5UHWPNS029090@turing-police.cc.vt.edu>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-180510833-1057042617=:4702"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-180510833-1057042617=:4702
Content-Type: text/plain; charset=us-ascii

I don't think I really miss points, remember some years ago I spoke of satelittes versus UMTS, all IETF guys praised UMTS.  But now we have more GAN sets / hand held sats  than UMTS.  Thats besides the point ( UMTS will catch up ) - The point is that if you are developing a blue laser based quantum comm system for submarine warfare, you will not have an optic fibre cable to send those "keys" to the boys below.  The enemy will also receive the Keys, solve that and you are  a millionaire. You can't send keys over optic fibre without the thugs out there catching them, before the encryption sequence -  Can you???
 
Furthermore we can tap computer key board radiation from close range and relay it to get keys anyway!  Are they keyboard or automatically generated?
 
Nyagudi


Valdis.Kletnieks@vt.edu wrote:
On Mon, 30 Jun 2003 02:41:37 PDT, NM Research said:

> (1) QC assumes that most of the photons from the transmitter of a 
> "quantum" message, reach the receiver. This assumption is therefore used to
> errorneously deduce that the communicating parties will therefore be 
> able to detect interception or interference.
> Problem(a): This is not true for blue laser transceiver technology, 
> as the receiver of a "quantum" message in this case needs far less than 
> 0.0001% of photons routed through blue laser routing satelittes, to receive a
> message.
> Problem(b): Optical fibre losses an appreciable amount of photons which 
> can be "tapped" non-intrusively.

You're missing the point. You can tap the cable, but you can't actually peek
at the photons as they go by without tipping off that you're peeking *at those
particular photons*.

> (2) Traditional intelligence gathering can be used to intercept or 
> reveal quantum cryptography keys and settings - e.g. the tapping of computer
> monitor radiation, or intrusion into a network via weaknesses in 
> wireless security or simply by way of deployment of corrupt practices.

Marcus Ranum coined the phrase "Rubber Hose Cryptography" for this. No amount
of 1024-versus-2048 bit key arguing is going to matter if The Bad Guys tell you
"Give us the key or we'll beat the snot out of you" (not that such people are
ready available to most criminal organizations and governments), and it's long
been known that most off-the-shelf crypto's biggest weakness is deployment by
stupid users....

> (3) Quantum cryptographic communications is based on monoplex and not 
> the duplex model of channel usage - I stand to be corrected.

Ever actually *looked* at the average GBIC? There's a send side and a receive
side, just because it's easier to build a fiber *pair* of unidirectional
links....

> (4) Intrusive penetration into a quantum cryptography secured network 
> causes inteference which results into the jamming or shutdown of the system, 
> while intrusive penetration into a "standard code" network will not result in
> the stoppage of communications. 
> Note : Those who intercept or retrieve standard code security 
> information, I many cases never get to interprete it. The intentions of a hacker 
> may simply be to interfere - DoS ( Denial of Service ).

Actually, no.

Most QC implementations are *poor* at transmitting data - they're only good for
giving both participants the same truly random unsnoopable session key. So for
any *practical* use, you'd use QC to exchange the session key and then some
other scheme to encrypt the session using the key.

Such hybrid operations are standard practice in practical cryptography - for
instance, RSA is very nice but takes an inordinate amount of time to do a
"real" amount of data (for instance, a 10K E-mail) as you have to treat that
10K as an 80,000 bit integer and do math on it. So what PGP (for instance)
does is use RSA to secure a very much smaller session key (256 or so bits), and
then use that key to initialize some symmetric cypher such as IDEA.

Remember that this has to be discussed in the context of threat models.

The people likely to be deploying QC anytime soon are *ALSO* the people who
worry about things like the physical diversity of their network, so a motivated
attacker can't cut them off the network by hitting one target. I'm *NOT* going
to say much on this topic, other that to mention "Just how many ways *are*
there to run a fiber path into Manhattan?"

Sure, a dedicated hacker could disrupt my QC. On the other hand, I have to do
my day-to-day work in a Real World where a credible estimate has 3 million
compromised machines (http://www.vnunet.com/News/1141901) - and it probably
would not take more than a few thousand to totally DDoS our 2xOC12. Of course,
our net is engineered to give 2xOC12 reliably, and hacker resilience is just a
by product. If our goal had been to resist intrusions and we cared enough to
deploy QC, you can be *sure* that our network design would be hardened against
other attacks as well.... ;)

> (5) Commercially available Quantum Cryptography technology is only 
> optical fibre based, and cannot secure satelitte based blue laser quantum
> communications technology.

Comment 1: New technology, it's not surprising that it's not available in every
flavor yet. How many colors were cars available in when the Model T came out? ;)

Comment 2: Is there a *market* for satellite based blue laser? Seems to me that
the first heavy rainstorm would cause packet loss unless you had enough power
budget to punch through - in which case it's not a comm device, it's a weapon.

> ATTACHMENT part 2 application/pgp-signature 


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

<DIV>I don't think I really miss points, remember some years ago I spoke of satelittes versus UMTS, all IETF guys praised UMTS.&nbsp; But now we have more GAN sets / hand held sats &nbsp;than UMTS.&nbsp; Thats besides the point ( UMTS will&nbsp;catch up )&nbsp;- The point is that if you are developing a blue laser based quantum comm system for submarine warfare, you will not have an optic fibre cable to send those "keys" to the boys below.&nbsp; The enemy will also receive the Keys, solve that and you are&nbsp; a millionaire. You can't send keys over optic fibre without the thugs out there catching them, before the encryption sequence -&nbsp; Can you???</DIV>
<DIV>&nbsp;</DIV>
<DIV>Furthermore we can tap computer key board radiation from close range and relay it to get keys anyway!&nbsp; Are they keyboard or automatically generated?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi</DIV>
<DIV><BR><BR><B><I>Valdis.Kletnieks@vt.edu</I></B> wrote:</DIV>
<DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid; WIDTH: 100%">On Mon, 30 Jun 2003 02:41:37 PDT, NM Research <NM_RESEARCH@YAHOO.COM>said:<BR><BR>&gt; (1) QC assumes that most of the photons from the transmitter of a <BR>&gt; "quantum" message, reach the receiver. This assumption is therefore used to<BR>&gt; errorneously deduce that the communicating parties will therefore be <BR>&gt; able to detect interception or interference.<BR>&gt; Problem(a): This is not true for blue laser transceiver technology, <BR>&gt; as the receiver of a "quantum" message in this case needs far less than <BR>&gt; 0.0001% of photons routed through blue laser routing satelittes, to receive a<BR>&gt; message.<BR>&gt; Problem(b): Optical fibre losses an appreciable amount of photons which <BR>&gt; can be "tapped" non-intrusively.<BR><BR>You're missing the point. You can tap the cable, but you can't actually peek<BR>at the photons as they go by without tipping off !
 that
 you're peeking *at those<BR>particular photons*.<BR><BR>&gt; (2) Traditional intelligence gathering can be used to intercept or <BR>&gt; reveal quantum cryptography keys and settings - e.g. the tapping of computer<BR>&gt; monitor radiation, or intrusion into a network via weaknesses in <BR>&gt; wireless security or simply by way of deployment of corrupt practices.<BR><BR>Marcus Ranum coined the phrase "Rubber Hose Cryptography" for this. No amount<BR>of 1024-versus-2048 bit key arguing is going to matter if The Bad Guys tell you<BR>"Give us the key or we'll beat the snot out of you" (not that such people are<BR>ready available to most criminal organizations and governments), and it's long<BR>been known that most off-the-shelf crypto's biggest weakness is deployment by<BR>stupid users....<BR><BR>&gt; (3) Quantum cryptographic communications is based on monoplex and not <BR>&gt; the duplex model of channel usage - I stand to be corrected.<BR><BR>Ever actually *looked* at the !
 average
 GBIC? There's a send side and a receive<BR>side, just because it's easier to build a fiber *pair* of unidirectional<BR>links....<BR><BR>&gt; (4) Intrusive penetration into a quantum cryptography secured network <BR>&gt; causes inteference which results into the jamming or shutdown of the system, <BR>&gt; while intrusive penetration into a "standard code" network will not result in<BR>&gt; the stoppage of communications. <BR>&gt; Note : Those who intercept or retrieve standard code security <BR>&gt; information, I many cases never get to interprete it. The intentions of a hacker <BR>&gt; may simply be to interfere - DoS ( Denial of Service ).<BR><BR>Actually, no.<BR><BR>Most QC implementations are *poor* at transmitting data - they're only good for<BR>giving both participants the same truly random unsnoopable session key. So for<BR>any *practical* use, you'd use QC to exchange the session key and then some<BR>other scheme to encrypt the session using the key.<BR><BR>Such hyb!
 rid
 operations are standard practice in practical cryptography - for<BR>instance, RSA is very nice but takes an inordinate amount of time to do a<BR>"real" amount of data (for instance, a 10K E-mail) as you have to treat that<BR>10K as an 80,000 bit integer and do math on it. So what PGP (for instance)<BR>does is use RSA to secure a very much smaller session key (256 or so bits), and<BR>then use that key to initialize some symmetric cypher such as IDEA.<BR><BR>Remember that this has to be discussed in the context of threat models.<BR><BR>The people likely to be deploying QC anytime soon are *ALSO* the people who<BR>worry about things like the physical diversity of their network, so a motivated<BR>attacker can't cut them off the network by hitting one target. I'm *NOT* going<BR>to say much on this topic, other that to mention "Just how many ways *are*<BR>there to run a fiber path into Manhattan?"<BR><BR>Sure, a dedicated hacker could disrupt my QC. On the other hand, I have to d!
 o<BR>my
 day-to-day work in a Real World where a credible estimate has 3 million<BR>compromised machines (http://www.vnunet.com/News/1141901) - and it probably<BR>would not take more than a few thousand to totally DDoS our 2xOC12. Of course,<BR>our net is engineered to give 2xOC12 reliably, and hacker resilience is just a<BR>by product. If our goal had been to resist intrusions and we cared enough to<BR>deploy QC, you can be *sure* that our network design would be hardened against<BR>other attacks as well.... ;)<BR><BR>&gt; (5) Commercially available Quantum Cryptography technology is only <BR>&gt; optical fibre based, and cannot secure satelitte based blue laser quantum<BR>&gt; communications technology.<BR><BR>Comment 1: New technology, it's not surprising that it's not available in every<BR>flavor yet. How many colors were cars available in when the Model T came out? ;)<BR><BR>Comment 2: Is there a *market* for satellite based blue laser? Seems to me that<BR>the first heavy rains!
 torm
 would cause packet loss unless you had enough power<BR>budget to punch through - in which case it's not a comm device, it's a weapon.<BR><BR>&gt; ATTACHMENT part 2 application/pgp-signature </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!
--0-180510833-1057042617=:4702--



From owner-ietf@ietf.org  Tue Jul  1 04:37:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02943
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Jul 2003 04:37:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19XGWJ-0004Al-5T
	for ietf-list@asgard.ietf.org; Tue, 01 Jul 2003 04:29:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19XGVw-00048B-Iw
	for ietf@asgard.ietf.org; Tue, 01 Jul 2003 04:29:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02801
	for <ietf@ietf.org>; Tue, 1 Jul 2003 04:29:22 -0400 (EDT)
From: chuyonggang@sina.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XGVp-000119-00
	for ietf@ietf.org; Tue, 01 Jul 2003 04:29:17 -0400
Received: from [202.108.35.233] (helo=sina.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19XGVO-00010z-00
	for ietf@ietf.org; Tue, 01 Jul 2003 04:28:51 -0400
Received: (qmail 11838 invoked by uid 99); 1 Jul 2003 08:28:12 -0000
Message-ID: <20030701082812.11836.qmail@sina.com>
To: ietf@ietf.org, internet-drafts@ietf.org
Subject: about the internet-drafts submission
MIME-Version: 1.0
Date: Tue, 01 Jul 2003 16:28:12 +0800
X-Mailer: SinaMail 3.0Beta (FireToad)
X-Priority: 3
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,
I submitted two Internet-Drafts by attaching a copy of them and sending two mails to internet-drafts@ietf.org two weeks ago. It has not yet been announced on the announcement-lists.

The subjects of the two mails are  "submit a draft". The names of the two drafts are "draft-yang-ldids-framework-00.txt" and "draft-yang-scxp-00.txt",respectively.

Did i miss something? Can you check it and give me a reply? 

Thanks,
Y.G. Chu

===================================================================



From owner-ietf@ietf.org  Tue Jul  1 05:04: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 FAA03513
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Jul 2003 05:04:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19XH0a-0005jg-N1
	for ietf-list@asgard.ietf.org; Tue, 01 Jul 2003 05:01:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19XGz6-0005dl-4d
	for ietf@asgard.ietf.org; Tue, 01 Jul 2003 04:59: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 EAA03382
	for <ietf@ietf.org>; Tue, 1 Jul 2003 04:59:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XGz3-0001Ed-00
	for ietf@ietf.org; Tue, 01 Jul 2003 04:59:29 -0400
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 19XGyt-0001EO-00
	for ietf@ietf.org; Tue, 01 Jul 2003 04:59:19 -0400
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 19XGyX-0004wz-00
	for <ietf@ietf.org>; Tue, 01 Jul 2003 09:58:57 +0100
Date: Tue, 1 Jul 2003 09:58:57 +0100
To: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
Message-ID: <20030701085857.GA15880@fysh.org>
References: <iluel1fkrdb.fsf@latte.josefsson.org> <20030628004726.4EDE2230012@fh.vix.com> <20030630161659.GB9368@fysh.org> <iluk7b3gg8w.fsf@latte.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <iluk7b3gg8w.fsf@latte.josefsson.org>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

Simon Josefsson wrote:
>The intention was to make sure future extensions aren't disallowed by
>the syntax.

Yes.  I'm wondering what kind of extensions might be permitted.
I'm concerned, as with several recent protocols, that perhaps an
extension mechanism has been added simply because it's very normal for
IETF protocols to have an extension mechanism, with no real thought
about what class of semantic features might be expressed by extensions.
It wouldn't be the first instance of cargo cult protocol design.

If the intent of the dns URI type is to express a <name,type,class>
tuple, then presumably any extension would be making the URI express
something other than such a tuple, in which case I think it would be
better to use a new URI scheme rather than overload an existing one.

>Can you elaborate?  The intention is that, e.g., a binary label with
>the ASCII value 0x17 is expressed as dns:%17.  There are some text and
>examples for this.

No, that's a text label containing a single octet with value 0x17.
I was referring to RFC2673 bit labels.  Consider also what should be
done for other EDNS0 extended label types (RFC2671).

-zefram
-- 
Anderw Main (Zefram) <zefram@fysh.org>



From owner-ietf@ietf.org  Tue Jul  1 10:22: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 KAA02239
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Jul 2003 10:22:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19XLgw-0002pk-Vn
	for ietf-list@asgard.ietf.org; Tue, 01 Jul 2003 10:01:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19XCuF-0004QZ-3m
	for ietf@asgard.ietf.org; Tue, 01 Jul 2003 00:38: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 AAA01300
	for <ietf@ietf.org>; Tue, 1 Jul 2003 00:38:14 -0400 (EDT)
From: niket@acm.org
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XCuC-00071K-00
	for ietf@ietf.org; Tue, 01 Jul 2003 00:38:12 -0400
Received: from smtp6.mindspring.com ([207.69.200.110])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XCu2-00071G-00
	for ietf@ietf.org; Tue, 01 Jul 2003 00:38:02 -0400
Received: from host-66-81-218-142.rev.o1.com ([66.81.218.142] helo=TOSHIBA)
	by smtp6.mindspring.com with smtp (Exim 3.33 #1)
	id 19XCtW-0005PF-00; Tue, 01 Jul 2003 00:37:31 -0400
Message-ID: <3F010D9E.4F53@acm.org>
Date: Mon, 30 Jun 2003 21:27:10 -0700
X-Mailer: Mozilla 3.01 (WinNT; I)
MIME-Version: 1.0
To: Zefram <zefram@fysh.org>
CC: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
References: <20030626191147.9241F1390E@sa.vix.com> <20030626201839.GA6888@fysh.org> <iluk7b7kuzw.fsf@latte.josefsson.org> <20030629183709.GA23233@fysh.org>
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 I understand it, originally the DNS system interpreted w.x in domain
y.z first as w.x.y.z. then w.x.z. then w.x.. If you wanted to be
absolutely sure you got w.y you had to say w.y..

In interesting aside - many countries (e.g. UK) seem to be using a
domain naming system that ends in .cc (.uk) but kind of echoes what we
have locally in the US (.com, .org, .edu etc), but (maybe) don't go the
next step and allow people to just say something like ibm.com and mean
ibm.com.uk.. I wonder why not - it would make things a lot more relevant
to the local people, and if they really wanted the international .com
they could add the trailing dot. Or does it already work that way?

 Zefram wrote:
> 
> Simon Josefsson wrote:
> >one added some text to clarify that it was actually intended to allow
> >for zero length dnsname's (to denote the DNS root).
> 
> This is technically correct, according to RFC 1034, but will be confusing.
> "dns:" intuitively looks incomplete.  It's more conventional to name
> the root domain in absolute form, as ".".  An interesting comparison:
> the "dig" DNS lookup tool from the BIND folks doesn't accept "" as a
> domain name; it insists on the root domain being specified as ".".
> 
> So I argue that requiring the root domain to be represented as "." in the
> context of the URI, forbidding a zero-length <dnsname>, will make for a
> clearer protocol, more likely to be implemented correctly.  This isn't
> an absolute matter, though; both versions of the protocol are workable.
> 
> -zefram






From owner-ietf@ietf.org  Tue Jul  1 20:57: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 UAA23270
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Jul 2003 20:57:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19XVkm-00050f-ES
	for ietf-list@asgard.ietf.org; Tue, 01 Jul 2003 20:45:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19XVjo-0004xE-Du
	for ietf@asgard.ietf.org; Tue, 01 Jul 2003 20:44: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 UAA22972
	for <ietf@ietf.org>; Tue, 1 Jul 2003 20:44:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XVjm-0003Lz-00
	for ietf@ietf.org; Tue, 01 Jul 2003 20:44:42 -0400
Received: from [203.254.224.25] (helo=mailout2.samsung.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19XVjl-0003Ln-00
	for ietf@ietf.org; Tue, 01 Jul 2003 20:44:42 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov  6 2002))
 id <0HHD00E0CGPMCH@mailout2.samsung.com> for ietf@ietf.org; Wed,
 02 Jul 2003 09:44:10 +0900 (KST)
Received: from ep_mmp2 (localhost [127.0.0.1])
 by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6
 2002)) with ESMTP id <0HHD0089VGPJ2D@mailout2.samsung.com> for ietf@ietf.org;
 Wed, 02 Jul 2003 09:44:08 +0900 (KST)
Received: from daniel7209 ([168.219.203.183])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18
 2003)) with ESMTPA id <0HHD006FYGPJ9O@mmp2.samsung.com> for ietf@ietf.org;
 Wed, 02 Jul 2003 09:44:07 +0900 (KST)
Date: Wed, 02 Jul 2003 09:44:19 +0900
From: Soohong Daniel Park <soohong.park@samsung.com>
Subject: Where can I find capwap BOF Agenda ?
To: ietf@ietf.org
Message-id: <010e01c34033$126f0000$b7cbdba8@daniel7209>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

Hi all

I am searching for capwap Agenda....

Friday, July 18
OPS  capwap  Control And Provisioning of Wirelsss Acc. Point BOF



Daniel (Soohong Daniel Park)
Mobile Platform Lab,SAMSUNG Electronics






From owner-ietf@ietf.org  Wed Jul  2 20: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 UAA03275
	for <ietf-web-archive@odin.ietf.org>; Wed, 2 Jul 2003 20:04:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19XrNm-0005PW-DX
	for ietf-list@asgard.ietf.org; Wed, 02 Jul 2003 19:51:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19XpOB-00011X-6Y
	for ietf@asgard.ietf.org; Wed, 02 Jul 2003 17:43: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 RAA20712
	for <ietf@ietf.org>; Wed, 2 Jul 2003 17:43:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XpOB-0001nT-00
	for ietf@ietf.org; Wed, 02 Jul 2003 17:43:43 -0400
Received: from tomts6.bellnexxia.net ([209.226.175.26] helo=tomts6-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19XpOA-0001nQ-00
	for ietf@ietf.org; Wed, 02 Jul 2003 17:43:42 -0400
Received: from yahoo.com ([65.93.184.129]) by tomts6-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030702214340.MEAI20796.tomts6-srv.bellnexxia.net@yahoo.com>
          for <ietf@ietf.org>; Wed, 2 Jul 2003 17:43:40 -0400
Date: Wed, 2 Jul 2003 17:43:38 -0400
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: the end-to-end name problem
From: S Woodside <sbwoodside@yahoo.com>
To: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <3D7401EA-ACD6-11D7-8022-000393414368@yahoo.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

End is an overloaded word. Overloaded words are great for politicians 
and poets because they can means so many different things. Some 
overloaded words (with many definitions) are spring (13), start (21), 
home (19), box (13), point (37), sign (18), hard (21), ... [0]

I think there's a problem with the name "end-to-end". End is a word 
with a lot of definitions: for example wordnet [1] lists 14 senses for 
the noun end and 4 more for the verb. Indeed, we must walk down to the 
5th definition before we  come to the one that is relevant. [2]

1. end -- (either extremity of something that has length; "the end of 
the pier"; "she knotted the end of the thread"; "they rode to the end 
of the line")
2. end, ending -- (the point in time at which something ends; "the end 
of the year"; "the ending of warranty period")
3. end, last, final stage -- (the concluding parts of an event or 
occurrence; "the end was exciting"; "I had to miss the last of the 
movie")
4. goal, end -- (the state of affairs that a plan is intended to 
achieve and that (when achieved) terminates behavior intended to 
achieve it; "the ends justify the means")
5. end -- (a final part or section; "we have given it at the end of the 
section since it involves the calculus"; "Start at the beginning and go 
on until you come to the end")

We all know what the end-to-end principle means. It's (reportedly) THE 
guiding principle of the IETF, and THE guiding principle of IETF design 
decisions. The problem I am trying to demonstrate with this dictionary 
analysis, is that average non-indoctrinated person needs to travel a 
long way from the simple word "end" in order to get to the definition 
that the IETF actually means.

Semantics, at its worst, is something that can be argued about 
endlessly and pointlessly. But, I'm sure that many people in the IETF 
spend at least some time introducing the CONCEPT of end-to-end 
networking to novices. Novices, who know english but not the internet, 
may be confused.

One alternative, used is "edge networking" and edge has much fewer 
definitions (only 6 for the noun) and the very FIRST one is the 
relevant one. [3]

1. edge, border -- (the boundary of a surface)

simon



[0] Counts are from WordNet [1]
[1] http://www.cogsci.princeton.edu/~wn/
[2] http://www.cogsci.princeton.edu/cgi-bin/webwn1.7.1?word=end&stage=1
[3] http://www.cogsci.princeton.edu/cgi-bin/webwn1.7.1?word=edge&stage=1

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Wed Jul  2 21:15: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 VAA08611
	for <ietf-web-archive@odin.ietf.org>; Wed, 2 Jul 2003 21:15:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19XsZE-0001nU-Jb
	for ietf-list@asgard.ietf.org; Wed, 02 Jul 2003 21:07:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19XsDn-0005rn-6Q
	for ietf@asgard.ietf.org; Wed, 02 Jul 2003 20:45: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 UAA07079
	for <ietf@ietf.org>; Wed, 2 Jul 2003 20:45:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XsDl-0007dz-00
	for ietf@ietf.org; Wed, 02 Jul 2003 20:45:09 -0400
Received: from grouse.mail.pas.earthlink.net ([207.217.120.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XsDk-0007dw-00
	for ietf@ietf.org; Wed, 02 Jul 2003 20:45:09 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by grouse.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19XsDj-0007Jg-00; Wed, 02 Jul 2003 17:45:07 -0700
Date: Wed, 2 Jul 2003 20:41:21 -0400
From: Keith Moore <moore@cs.utk.edu>
To: S Woodside <sbwoodside@yahoo.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: the end-to-end name problem
Message-Id: <20030702204121.138fa13d.moore@cs.utk.edu>
In-Reply-To: <3D7401EA-ACD6-11D7-8022-000393414368@yahoo.com>
References: <3D7401EA-ACD6-11D7-8022-000393414368@yahoo.com>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

] We all know what the end-to-end principle means. 

well, you'd think so - but these days I hear it used to justify all kinds of
things that have nothing to do with its original meaning.  I think it's 
becoming a religion - something that is accepted without question, and usually, 
without undertanding.




From owner-ietf@ietf.org  Wed Jul  2 22:00: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 WAA10418
	for <ietf-web-archive@odin.ietf.org>; Wed, 2 Jul 2003 22:00:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19XtK3-0000nD-4l
	for ietf-list@asgard.ietf.org; Wed, 02 Jul 2003 21:55:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19XtIk-0000Ie-Oh
	for ietf@asgard.ietf.org; Wed, 02 Jul 2003 21:54: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 VAA10153
	for <ietf@ietf.org>; Wed, 2 Jul 2003 21:54:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XtIj-0001AS-00
	for ietf@ietf.org; Wed, 02 Jul 2003 21:54:21 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19XtIh-00019I-00
	for ietf@ietf.org; Wed, 02 Jul 2003 21:54:20 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 2117A625A3; Thu,  3 Jul 2003 03:53:50 +0200 (CEST)
Date: Thu, 03 Jul 2003 03:53:50 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: erosen@cisco.com
Cc: ietf@ietf.org
Subject: The requirements cycle (Re: WG review: Layer 2 Virtual....)
Message-ID: <255350000.1057197230@askvoll.hjemme.alvestrand.no>
In-Reply-To: <200306301526.h5UFQCg5026476@rtp-core-1.cisco.com>
References:  <200306301526.h5UFQCg5026476@rtp-core-1.cisco.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

apologies for a long delay in responding.... I am not the responsible AD 
for this WG, and have not been closely involved, so I may not have all my 
facts straight, especially for the Time Before The ID-Tracker.....

--On mandag, juni 30, 2003 11:26:12 -0400 Eric Rosen <erosen@cisco.com> 
wrote:

>
> Harald> It might  have something  to do with  the fact  that the WG  has
> not requested that the  IESG process these drafts.... if  the WG
> has not come  to consensus on  asking for  the drafts  to be
> published, I'm afraid the IESG cannot do anything.
>
> I consider this answer to be rather disingenuous.

It was; I missed the context, which I should have been aware of.
Back to the arguments on requirements documents and dependencies...

> The WG has  not requested that the IESG process these  drafts because the
> WG chairs have  told the  WG that  the ADs have  told them  that the
> drafts in question cannot be submitted to the IESG until numerous other
> drafts that no one  will  ever  read  (requirements,  framework,
> architecture)  have  been approved by the  IESG.  Of course, most of
> those  numerous other drafts were completed about 18 months ago, though a
> few of them have now come out of the seemingly endless  "IESG reviews,
> WG makes minor  change, IESG  reviews, WG change" cycle.

to be specific - are you talking about draft-ietf-ppvpn-requirements and 
draft-ietf-ppvpn-framework? (I couldn't find a ppvpn-architecture in the 
tracker). Are there others in the set?

For -requirements, the tracker shows to be first submitted for IESG 
evaluation on June 21, 2002 (version 04), comments sent to author on July 
29, with a comment from the WG chair saying "2 months' work" on July 30, 
and the next mention in the tracker on February 17. Still issues with 
version -06; the tracker has interesting comments to read.

For -framework, the tracker shows it first submitted for IESG evaluation on 
June 21, 2002 (version 05). Version -08 was approved on May 23 this year.

I'll agree that these have been in the IESG spin cycle 12 months. But I 
won't agree that they were *completed* either 12 or 18 months ago.

And I don't understand why WG updates to fix problems take 2-3 months per 
cycle when the WG thinks that it's important to be finished with the docs.

> So you  can't honestly  answer Yakov by  saying "the  WG hasn't asked  us
> to process  these  drafts";  the  answer   to  Yakov's  question  would
> be  an explanation of (a) why all these  prior drafts are really
> necessary, (b) why it is reasonable for such a long  review cycle, and
> (c) why it is reasonable to delay  starting to process the  protocol
> specs until the  prior specs are already on the RFC Editor's queue.

(a) did any of the technologies change because of issues that were 
discovered in the discussions that were needed to clarify the requirements 
and framework?
If yes - I rest my case.
If no - why did it take any time at all to produce them?

(b) 3-6 month cycles are not reasonable.
Unfortunately, there is little that the IESG can do when the WG knows what 
the comments are and chooses not to act upon them for 2-5 months. Yelling 
more at the people responsible (WG chairs and document editors) might have 
helped. But whose job is that, really?

(c) is the IESG supposed to care about inconsistencies between the 
requirements (which are what the *WG* thinks should be satisfied) and the 
technologies that will be proposed for standardization?
if yes - how can the IESG do that when the requirements are not stable?
if no - I do not understand what "WG consensus on requirements" can mean.

I think we have unanimous agreement that the PPVPN WG's framework documents 
have taken far too long. We probably also agree that it's rare that 
blame-shifting on a public mailing list improves communication.

But I think it's too simplistic to say that "the IESG is the problem".

                 Harald





From owner-ietf@ietf.org  Wed Jul  2 22:42: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 WAA11763
	for <ietf-web-archive@odin.ietf.org>; Wed, 2 Jul 2003 22:42:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Xtvy-0003Dh-OH
	for ietf-list@asgard.ietf.org; Wed, 02 Jul 2003 22:34:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Xtro-0001sn-33
	for ietf@asgard.ietf.org; Wed, 02 Jul 2003 22:30: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 WAA11403
	for <ietf@ietf.org>; Wed, 2 Jul 2003 22:30:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xtrm-0001e0-00
	for ietf@ietf.org; Wed, 02 Jul 2003 22:30:34 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xtrl-0001dx-00
	for ietf@ietf.org; Wed, 02 Jul 2003 22:30:33 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id E927D625A3; Thu,  3 Jul 2003 04:30:03 +0200 (CEST)
Date: Thu, 03 Jul 2003 04:30:04 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Paul Vixie <vixie@fh.vix.com>, ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt 
Message-ID: <268260000.1057199403@askvoll.hjemme.alvestrand.no>
In-Reply-To: <20030628004726.4EDE2230012@fh.vix.com>
References:  <20030628004726.4EDE2230012@fh.vix.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable



--On l=F8rdag, juni 28, 2003 00:47:26 +0000 Paul Vixie <vixie@fh.vix.com>=20
wrote:

> dns is a distributed, autonomous, coherent, reliable database.  a syntax
> that allows entity A and entity B to speak incoherently about a given
> <qname, qtype,qclass> would violate the coherency of the design.  the
> only exception would be if you intended to be able to represent all
> attributes of a dns query, which i think would be useless, but would
> allow hostport but require RD, buffer size, and other EDNS OPT options to
> be invented later.

just because I feel like fiddling around with definitions...

using the definitions of RFC 3254, "Definitions for talking about=20
directories" (ok, I'm quoting myself again :-), I'd say:

- the global DNS service is a global, cooperative repository - "there can=20
be only one", and the pieces pass stuff around between each other.

- there exist local repositories that use the DNS protocol for access, but=20
that are not the global repository (split horizon installations and=20
"alternate root" stuff, for instance).

Hostport may or may not be useful for identifiying access to those=20
services; as the IRC community has learned, and the WWW folks may be=20
learning, identifying the place where a service is available is not a=20
functional replacement for naming the service, but that doesn't prevent=20
people from using it as if it was.

("hostport" does seem a bit recursive, though; in what DNS service is the=20
"host" part of the "hostport" to be looked up?..... RFC 2396 is silent on=20
the issue....)

                   Harald






From owner-ietf@ietf.org  Thu Jul  3 01:08: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 BAA15587
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 01:08:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19XwCz-0007xu-DG
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 01:00:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19XwCc-0007lX-4N
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 01:00: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 BAA15396
	for <ietf@ietf.org>; Thu, 3 Jul 2003 01:00:13 -0400 (EDT)
From: Klensin@JCK.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XwCa-0002nK-00
	for ietf@ietf.org; Thu, 03 Jul 2003 01:00:12 -0400
Received: from 12-203-8-135.client.attbi.com ([12.203.8.135] helo=MY)
	by ietf-mx with esmtp (Exim 4.12)
	id 19XwCV-0002nG-00
	for ietf@ietf.org; Thu, 03 Jul 2003 01:00:07 -0400
To: <ietf@ietf.org>
Subject: Re: Movie
Date: Wed, 2 Jul 2003 21:57:51 --0700
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="CSmtpMsgPart123X456_000_4AED0982"
Message-Id: <E19XwCV-0002nG-00@ietf-mx>
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multipart message in MIME format

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

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

Found virus WORM_SOBIG.E in file details.pif (in your_details.zip)
The uncleanable file your_details.zip is moved to /etc/iscan/virus/virAYBw3aqYo.

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

--CSmtpMsgPart123X456_000_4AED0982
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Please see the attached zip file for details.
--CSmtpMsgPart123X456_000_4AED0982
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


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

your_details.zip is removed from here because it contains a virus.

---------------------------------------------------------
--CSmtpMsgPart123X456_000_4AED0982--




From owner-ietf@ietf.org  Thu Jul  3 01:48: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 BAA16563
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 01:48:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Xwtb-0000rU-SN
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 01:44:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19XwtD-0000ej-Kg
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 01:44:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16453
	for <ietf@ietf.org>; Thu, 3 Jul 2003 01:44:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XwtB-0003As-00
	for ietf@ietf.org; Thu, 03 Jul 2003 01:44:13 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19XwtB-0003Ao-00
	for ietf@ietf.org; Thu, 03 Jul 2003 01:44:13 -0400
Received: from [147.28.0.62] (helo=127.0.0.1 ident=zinin)
	by psg.com with esmtp (Exim 4.14)
	id 19XwtB-0005Kb-M6
	for ietf@ietf.org; Thu, 03 Jul 2003 05:44:13 +0000
Date: Wed, 2 Jul 2003 22:40:59 -0700
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.62i) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <50260449456.20030702224059@psg.com>
To: ietf@ietf.org
Subject: IESG on WG review for L2VPN and L3VPN
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks-

 [On behalf of the IESG]

 The IESG discussed final approval of L2VPN and L3VPN Working Groups at
 the IESG telechat on June 26, 2003. The IESG considered the feedback
 provided by the IETF community and would like to thank all people who
 expressed their opinion. Given that creation of the two WGs is
 proposed as part of separation of L2 VPN and L3 VPN work within the
 existing PPVPN WG (which will be closed as a result), and that the scope
 of work is not being extended beyond the limits effective for PPVPN,
 the IESG decided to approve formation of the two new WGs. Formal
 announcement will be sent out by the secretariat shortly.

-- 
Alex Zinin
IETF SUB-IP Area Co-director




From owner-ietf@ietf.org  Thu Jul  3 02:02: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 CAA19273
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 02:02:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Xx78-0004ND-1t
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 01:58:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Xx6u-0004B2-Rd
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 01:58: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 BAA16903
	for <ietf@ietf.org>; Thu, 3 Jul 2003 01:58:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xx6s-0003L7-00
	for ietf@ietf.org; Thu, 03 Jul 2003 01:58:22 -0400
Received: from ns1.vrx.net ([199.166.27.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Xx6r-0003Kz-00
	for ietf@ietf.org; Thu, 03 Jul 2003 01:58:22 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP
	id 7A679D378; Thu,  3 Jul 2003 01:54:58 -0400 (EDT)
Mime-Version: 1.0
X-Sender: stef@vrx.net
Message-Id: <v04220810bb297258da86@[192.168.1.14]>
In-Reply-To: <20030702204121.138fa13d.moore@cs.utk.edu>
References: <3D7401EA-ACD6-11D7-8022-000393414368@yahoo.com>
 <20030702204121.138fa13d.moore@cs.utk.edu>
Date: Wed, 2 Jul 2003 22:54:52 -0700
To: Keith Moore <moore@cs.utk.edu>
From: Einar Stefferud <Stef@thor.nma.com>
Subject: Re: the end-to-end name problem
Cc: S Woodside <sbwoodside@yahoo.com>, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

Quite so Keith! -- We have found something to agree on;-)...

End-to-Endness does not alone define the Internet.  

I expect we could safely say that TCP/IP is an End-to-End protocol pair, and 
though it is a critical part of the Internet, it is not "The Internet".

Fully describing the Internet requires much more sophisticated mathematical 
logic than simply declaring that it employs End-to-Endness, even though 
some of its parts do exhibit end-to-endness which is put to good use to make 
The Whole Internet work as it does.

So, we must not do away with End-to-Endness where it is used, or ignore all 
the rest of what makes the Internet what it is. 

Cheers...\Stef

At 20:41 -0400 7/2/03, Keith Moore wrote:
>] We all know what the end-to-end principle means. 
>
>well, you'd think so - but these days I hear it used to justify all kinds of
>things that have nothing to do with its original meaning.  I think it's 
>becoming a religion - something that is accepted without question, and usually, 
>without undertanding.


[SNIP]...




From owner-ietf@ietf.org  Thu Jul  3 05:36: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 FAA03756
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 05:36:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Y0Nf-0003RJ-UL
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 05:27:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Y0MR-0003HV-Jf
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 05:26:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03522
	for <ietf@ietf.org>; Thu, 3 Jul 2003 05:26:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y0MP-0004Yb-00
	for ietf@ietf.org; Thu, 03 Jul 2003 05:26:37 -0400
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y0MH-0004YY-00
	for ietf@ietf.org; Thu, 03 Jul 2003 05:26:29 -0400
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 19Y0MA-0001ZS-00
	for <ietf@ietf.org>; Thu, 03 Jul 2003 10:26:22 +0100
Date: Thu, 3 Jul 2003 10:26:22 +0100
To: ietf@ietf.org
Subject: Re: the end-to-end name problem
Message-ID: <20030703092622.GA4914@fysh.org>
References: <3D7401EA-ACD6-11D7-8022-000393414368@yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3D7401EA-ACD6-11D7-8022-000393414368@yahoo.com>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

S Woodside wrote:
>                                              we must walk down to the 
>5th definition before we  come to the one that is relevant. [2]
>
>1. end -- (either extremity of something that has length; "the end of 
>the pier"; "she knotted the end of the thread"; "they rode to the end 
>of the line")

This definition looks relevant.  More relevant than the fifth.

-zefram



From owner-ietf@ietf.org  Thu Jul  3 06:17: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 GAA04947
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 06:17:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Y14y-0002Ps-D0
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 06:12:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Y14L-0002G7-5t
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 06:12: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 GAA04820
	for <ietf@ietf.org>; Thu, 3 Jul 2003 06:11:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y14I-0004uk-00
	for ietf@ietf.org; Thu, 03 Jul 2003 06:11:58 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y14H-0004ub-00
	for ietf@ietf.org; Thu, 03 Jul 2003 06:11:58 -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 h63ACcxS040459;
	Thu, 3 Jul 2003 12:12:38 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 3 Jul 2003 12:11:49 +0200
Subject: Re: the end-to-end name problem
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: S Woodside <sbwoodside@yahoo.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <3D7401EA-ACD6-11D7-8022-000393414368@yahoo.com>
Message-Id: <C2C47F64-AD3E-11D7-A3AF-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, jul 2, 2003, at 23:43 Europe/Amsterdam, S Woodside wrote:

> I think there's a problem with the name "end-to-end". End is a word 
> with a lot of definitions: for example wordnet [1] lists 14 senses for 
> the noun end and 4 more for the verb. Indeed, we must walk down to the 
> 5th definition before we  come to the one that is relevant. [2]

[...]

> Semantics, at its worst, is something that can be argued about 
> endlessly and pointlessly. But, I'm sure that many people in the IETF 
> spend at least some time introducing the CONCEPT of end-to-end 
> networking to novices. Novices, who know english but not the internet, 
> may be confused.

You're falling in your own trap here. The concept "end" is very 
fundamental and as such understood by everyone who can read and write. 
The dictionary just lists some ways in which the concept is applied. 
The fact that there are many applications shows the concept is 
fundamental, not that it is ambiguous, as you suggest.

> One alternative, used is "edge networking" and edge has much fewer 
> definitions (only 6 for the noun) and the very FIRST one is the 
> relevant one.

I don't know about you, but "end to end" sounds like something that I 
might grasp intuitively, but "edge to edge" not so much. Also, "edge" 
is used for other stuff in the industry.




From owner-ietf@ietf.org  Thu Jul  3 07:09: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 HAA06057
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 07:09:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Y1oM-0001jo-Sp
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 06:59:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Y1nM-0001TY-0P
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 06:58: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 GAA05787
	for <ietf@ietf.org>; Thu, 3 Jul 2003 06:58:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y1nJ-00058X-00
	for ietf@ietf.org; Thu, 03 Jul 2003 06:58:29 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y1nI-00058P-00
	for ietf@ietf.org; Thu, 03 Jul 2003 06:58:28 -0400
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200307031044.TAA19354@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id TAA19354; Thu, 3 Jul 2003 19:44:04 +0900
Subject: Re: the end-to-end name problem
In-Reply-To: <3D7401EA-ACD6-11D7-8022-000393414368@yahoo.com> from S Woodside
 at "Jul 2, 2003 05:43:38 pm"
To: S Woodside <sbwoodside@yahoo.com>
Date: Thu, 3 Jul 2003 19:44:02 +0859 ()
CC: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-ietf@ietf.org
Precedence: bulk

Simon;

> We all know what the end-to-end principle means. It's (reportedly) THE 
> guiding principle of the IETF, and THE guiding principle of IETF design 
> decisions. The problem I am trying to demonstrate with this dictionary 
> analysis, is that average non-indoctrinated person needs to travel a 
> long way from the simple word "end" in order to get to the definition 
> that the IETF actually means.

Wrong.

It is the principle of not the IETF but the Internet.

As you should recognize, most, if not all, of recent activity of
IETF is against the principle, against which, the Internet is
operated.

Well organized standardization body such as IETF is an intermediate
intelligent entity between end users and the Internet.

That is, according to the principle, an intermediate intelligent
entity of IETF MUST be removed.

						Masataka Ohta



From owner-ietf@ietf.org  Thu Jul  3 10:04: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 KAA11276
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 10:04:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Y4St-0005rq-Nc
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 09:49:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Y4Sc-0005o6-3l
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 09:49:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10677
	for <ietf@ietf.org>; Thu, 3 Jul 2003 09:49:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y4Sb-0006Vc-00
	for ietf@ietf.org; Thu, 03 Jul 2003 09:49:17 -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 19Y4SZ-0006Ut-00
	for ietf@ietf.org; Thu, 03 Jul 2003 09:49:15 -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 XAA1575372;
	Thu, 3 Jul 2003 23:48:41 +1000 (EST)
Message-ID: <3F043439.81238B24@swin.edu.au>
Date: Thu, 03 Jul 2003 23:48:41 +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: the end-to-end name problem
References: <3D7401EA-ACD6-11D7-8022-000393414368@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


S Woodside wrote:
	[..]
> Novices, who know english but not the internet,
> may be confused.

Forgive me for not thinking it insightful to observe that
technical terminologies are often confusing to novices.

This insight is hardly a compelling argument for gratuitous
word substitutions. Likewise a dictionary is hardly a compelling
substitute for going direct to the paper(s) in which the
end to end principle has been articulated.

cheers,
gja
-- 
Grenville Armitage
http://caia.swin.edu.au
I come from a LAN downunder.



From owner-ietf@ietf.org  Thu Jul  3 14:28: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 OAA00111
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 14:28:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Y8jD-0007Av-6J
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 14:22:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Y8gw-0005cB-LQ
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 14: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 OAA29746
	for <ietf@ietf.org>; Thu, 3 Jul 2003 14:20:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y8gv-0005zD-00
	for ietf@ietf.org; Thu, 03 Jul 2003 14:20:21 -0400
Received: from tomts5.bellnexxia.net ([209.226.175.25] helo=tomts5-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y8gu-0005zA-00
	for ietf@ietf.org; Thu, 03 Jul 2003 14:20:20 -0400
Received: from yahoo.com ([65.93.183.106]) by tomts5-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030703182019.IQCB3524.tomts5-srv.bellnexxia.net@yahoo.com>;
          Thu, 3 Jul 2003 14:20:19 -0400
Date: Thu, 3 Jul 2003 14:20:20 -0400
Subject: Re: the end-to-end name problem
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Zefram <zefram@fysh.org>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <20030703092622.GA4914@fysh.org>
Message-Id: <01390FA4-AD83-11D7-A0F9-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Thursday, July 3, 2003, at 05:26  AM, Zefram wrote:

> S Woodside wrote:
>>                                              we must walk down to the
>> 5th definition before we  come to the one that is relevant. [2]
>>
>> 1. end -- (either extremity of something that has length; "the end of
>> the pier"; "she knotted the end of the thread"; "they rode to the end
>> of the line")
>
> This definition looks relevant.  More relevant than the fifth.

It's talking about something linear.

simon




From owner-ietf@ietf.org  Thu Jul  3 14:28: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 OAA00128
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 14:28:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Y8ia-0006Nk-H6
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 14:22:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Y7Kq-0007Z8-In
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 12:53: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 MAA24342
	for <ietf@ietf.org>; Thu, 3 Jul 2003 12:53:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y7Kp-00034z-00
	for ietf@ietf.org; Thu, 03 Jul 2003 12:53:27 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y7Ko-000323-00
	for ietf@ietf.org; Thu, 03 Jul 2003 12:53:26 -0400
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h63Gqmfq009031;
	Thu, 3 Jul 2003 12:52:48 -0400 (EDT)
Message-Id: <200307031652.h63Gqmfq009031@rtp-core-1.cisco.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: The requirements cycle (Re: WG review: Layer 2 Virtual....) 
In-reply-to: Your message of Thu, 03 Jul 2003 03:53:50 +0200.
             <255350000.1057197230@askvoll.hjemme.alvestrand.no> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 03 Jul 2003 12:52:48 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


Harald> did  any of  the technologies  change  because of  issues that  were
Harald> discovered  in  the discussions  that  were  needed  to clarify  the
Harald> requirements and framework? 

No. 

Harald> If no - why did it take any time at all to produce them? 

Not sure what you mean, it always  takes time to produce a document, even if
the document is just a "rock fetch". 

Harald> there is  little that  the IESG can  do when  the WG knows  what the
Harald> comments are and chooses not to act upon them for 2-5 months. 

This reminds me  of Dilbert's pointy-haired boss, who  says "your project is
late,  so I  want  you to  give me  hourly  status reports."   When we  have
documents which aren't really necessary in the first place, which ultimately
will not  have any impact on the  technology, but which need  to be massaged
and remassaged  so as to get  them past the  IESG, I think it's  quite clear
where the responsibility for the delay is coming from. 

Harald> And  I don't  understand why  WG updates  to fix  problems  take 2-3
Harald> months  per cycle  when  the WG  thinks  that it's  important to  be
Harald> finished with the docs. 

Well, each  objection from  the IESG  needs to be  discussed and  a response
crafted.  

Harald> is  the IESG  supposed  to care  about  inconsistencies between  the
Harald> requirements (which  are what the  *WG* thinks should  be satisfied)
Harald> and the technologies that will be proposed for standardization? 

Sure; but the reqs,  framework, protocol specs, and applicability statements
were all  ready 18 months ago.  They  could have been submitted  as a group.
But we were told, "first you need  to submit the first document, then a year
or so  later you can  submit the  second".  This is  a very peculiar  way to
encourage progress  ;-) From the WG  perspective, the specs  have been ready
for review  forever, but  the IESG has  refused to  look at them  because of
bogus process issues.  And then they turn around and accuse the WG of making
slow progress! 









From owner-ietf@ietf.org  Thu Jul  3 15:10: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 PAA02107
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 15:10:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Y9Ne-0001xr-Uy
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 15:04:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Y9Ip-0005JU-Gy
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 14:59: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 OAA01199
	for <ietf@ietf.org>; Thu, 3 Jul 2003 14:59:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y9Io-00071G-00
	for ietf@ietf.org; Thu, 03 Jul 2003 14:59:30 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y9In-000718-00
	for ietf@ietf.org; Thu, 03 Jul 2003 14:59:29 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h63IxIN22909;
        Thu, 3 Jul 2003 14:59:18 -0400 (EDT)
Date: Thu, 3 Jul 2003 14:59:17 -0400
From: Keith Moore <moore@cs.utk.edu>
To: erosen@cisco.com
Cc: moore@cs.utk.edu, harald@alvestrand.no, ietf@ietf.org
Subject: Re: The requirements cycle (Re: WG review: Layer 2 Virtual....)
Message-Id: <20030703145917.08caf04b.moore@cs.utk.edu>
In-Reply-To: <200307031652.h63Gqmfq009031@rtp-core-1.cisco.com>
References: <255350000.1057197230@askvoll.hjemme.alvestrand.no>
	<200307031652.h63Gqmfq009031@rtp-core-1.cisco.com>
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
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Sure; but the reqs,  framework, protocol specs, and applicability
> statements were all  ready 18 months ago.  They  could have been
> submitted  as a group. But we were told, "first you need  to submit
> the first document, then a year or so  later you can  submit the 
> second".  This is  a very peculiar  way to encourage progress  ;-)

L2VPN is not progress.  It's the opposite.



From owner-ietf@ietf.org  Thu Jul  3 15:57: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 PAA04016
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 15:57:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YA79-0004wl-0z
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 15:51:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YA63-0004gJ-SA
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 15:50: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 PAA03903
	for <ietf@ietf.org>; Thu, 3 Jul 2003 15:50:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YA62-0000cE-00
	for ietf@ietf.org; Thu, 03 Jul 2003 15:50:22 -0400
Received: from tomts8.bellnexxia.net ([209.226.175.52] helo=tomts8-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19YA61-0000cB-00
	for ietf@ietf.org; Thu, 03 Jul 2003 15:50:21 -0400
Received: from yahoo.com ([65.93.183.106]) by tomts8-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030703195019.EQSG24417.tomts8-srv.bellnexxia.net@yahoo.com>;
          Thu, 3 Jul 2003 15:50:19 -0400
Date: Thu, 3 Jul 2003 15:50:18 -0400
Subject: Re: the end-to-end name problem
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org, Keith Moore <moore@cs.utk.edu>
To: Einar Stefferud <Stef@thor.nma.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <v04220810bb297258da86@[192.168.1.14]>
Message-Id: <92B9E080-AD8F-11D7-A0F9-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Thursday, July 3, 2003, at 01:54  AM, Einar Stefferud wrote:

> I expect we could safely say that TCP/IP is an End-to-End protocol 
> pair, and
> though it is a critical part of the Internet, it is not "The Internet".

It isn't? Then what is "the internet" ?

There are at least two other network arguments that can be made to 
support the end-to-end principle (and potentially rename it)

The network effect - whether it's Metcalfe's law, or Reed's law, or 
otherwise. The network effect, I think, is real. We can say that the 
network effect reinforces the upwards scaling of any network, by 
delivering much better than linear payback. Thus, it can be argued that 
the IDEAL network, is a network that scales upwards as quickly as 
possible, for as long as possible. Now, we can compose an argument that 
the most scalable network, is an end-to-end network, because it 
contains the simplest network core, and thus the most easy to scale 
network core. If that argument is valid, then we can say that the 
network effect supports the end-to-end principle.

The neutral network argument - this is an argument that I have seen 
much more from the side of economics and law. I have seen the term used 
in relation to the internet by Lawrence Lessig [1]. Network neutrality 
argues that a network should be unbiased to any particular USER or USE. 
This would again lead to a principle network simplicity, since any kind 
of complexity would either (a) indicate an effort to control the 
network internals or (b) allow operators to impose greater control by 
taking advantage of the complexity.

> Fully describing the Internet requires much more sophisticated 
> mathematical
> logic than simply declaring that it employs End-to-Endness, even though
> some of its parts do exhibit end-to-endness which is put to good use 
> to make
> The Whole Internet work as it does.

Perhaps the neutral network arguments in economics would help.

simon

> So, we must not do away with End-to-Endness where it is used, or 
> ignore all
> the rest of what makes the Internet what it is.
>
> Cheers...\Stef
>
> At 20:41 -0400 7/2/03, Keith Moore wrote:
>> ] We all know what the end-to-end principle means.
>>
>> well, you'd think so - but these days I hear it used to justify all 
>> kinds of
>> things that have nothing to do with its original meaning.  I think 
>> it's
>> becoming a religion - something that is accepted without question, 
>> and usually,
>> without undertanding.
>
>
> [SNIP]...
>
>

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Thu Jul  3 16:00: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 QAA04285
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 16:00:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YACy-0005u8-O7
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 15:57:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YAAq-0005aD-0V
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 15:55: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 PAA03978
	for <ietf@ietf.org>; Thu, 3 Jul 2003 15:55:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YAAo-0000od-00
	for ietf@ietf.org; Thu, 03 Jul 2003 15:55:18 -0400
Received: from tomts23.bellnexxia.net ([209.226.175.185] helo=tomts23-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19YAAo-0000oa-00
	for ietf@ietf.org; Thu, 03 Jul 2003 15:55:18 -0400
Received: from yahoo.com ([65.93.183.106]) by tomts23-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030703195516.XSUE11594.tomts23-srv.bellnexxia.net@yahoo.com>;
          Thu, 3 Jul 2003 15:55:16 -0400
Date: Thu, 3 Jul 2003 15:55:15 -0400
Subject: Re: the end-to-end name problem
Content-Type: text/plain; charset=ISO-8859-1; 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: <C2C47F64-AD3E-11D7-A3AF-00039388672E@muada.com>
Message-Id: <43FC238C-AD90-11D7-A0F9-000393414368@yahoo.com>
Content-Transfer-Encoding: quoted-printable
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


On Thursday, July 3, 2003, at 06:11  AM, Iljitsch van Beijnum wrote:

> On woensdag, jul 2, 2003, at 23:43 Europe/Amsterdam, S Woodside wrote:
>
>> I think there's a problem with the name "end-to-end". End is a word=20=

>> with a lot of definitions: for example wordnet [1] lists 14 senses=20
>> for the noun end and 4 more for the verb. Indeed, we must walk down=20=

>> to the 5th definition before we  come to the one that is relevant. >> =
[2]
>
> [...]
>
>> Semantics, at its worst, is something that can be argued about=20
>> endlessly and pointlessly. But, I'm sure that many people in the IETF=20=

>> spend at least some time introducing the CONCEPT of end-to-end=20
>> networking to novices. Novices, who know english but not the=20
>> internet, may be confused.
>
> You're falling in your own trap here. The concept "end" is very=20
> fundamental and as such understood by everyone who can read and write.=20=

> The dictionary just lists some ways in which the concept is applied.=20=

> The fact that there are many applications shows the concept is=20
> fundamental, not that it is ambiguous, as you suggest.

The fact that the word "end" has so many meanings does imply that it's=20=

a common word. But people are aware that the popular can have many=20
different meanings. The problem is that the meaning intended by=20
End-To-End is not among the na=EFve meanings. It is a typical trap in=20
naming things to choose a word that is misleading. It is often much=20
simpler to choose a word that is totally made up or has no=20
significance, like an acronym, or a combination of letters and numbers.=20=

Like TCP/IP, which has no naive meaning at all, and requires the naive=20=

person to dive in to make any conclusion.

>> One alternative, used is "edge networking" and edge has much fewer=20
>> definitions (only 6 for the noun) and the very FIRST one is the=20
>> relevant one.
>
> I don't know about you, but "end to end" sounds like something that I=20=

> might grasp intuitively, but "edge to edge" not so much.

That is, perhaps, a good thing, since I think that most naive people=20
will THINK that they intuitively grasp what end-to-end means, but they=20=

are wrong.

simon

--
www.simonwoodside.com -- 99% Devil, 1% Angel=




From owner-ietf@ietf.org  Thu Jul  3 16:47: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 QAA05475
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 16:47:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YAqm-0003LW-5a
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 16:38:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YAlr-0002hb-Cn
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 16:33: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 QAA05200
	for <ietf@ietf.org>; Thu, 3 Jul 2003 16:33:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YAlk-0001jX-00
	for ietf@ietf.org; Thu, 03 Jul 2003 16:33:28 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19YAlj-0001fb-00
	for ietf@ietf.org; Thu, 03 Jul 2003 16:33:28 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 8A4676223F; Thu,  3 Jul 2003 22:32:56 +0200 (CEST)
Date: Thu, 03 Jul 2003 22:32:56 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: erosen@cisco.com
Cc: ietf@ietf.org
Subject: Re: The requirements cycle (Re: WG review: Layer 2 Virtual....) 
Message-ID: <351620000.1057264376@askvoll.hjemme.alvestrand.no>
In-Reply-To: <200307031652.h63Gqmfq009031@rtp-core-1.cisco.com>
References:  <200307031652.h63Gqmfq009031@rtp-core-1.cisco.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

high level bit of this reply:

from my perspective, the management of the PPVPN WG appears not to have 
been optimal, to say the least. But I'm not willing to blame *all* the 
delay and confusion on the IESG.

even if a WG feels abused by the IESG, or its AD, that's no excuse for a WG 
not fighting back - in this case, by rapidly removing the IESG's apparent 
excuses for delay.

Dejection is an explanation, not an excuse.

Details:

--On torsdag, juli 03, 2003 12:52:48 -0400 Eric Rosen <erosen@cisco.com> 
wrote:

>
> Harald> did  any of  the technologies  change  because of  issues that
> were Harald> discovered  in  the discussions  that  were  needed  to
> clarify  the Harald> requirements and framework?
>
> No.
>
> Harald> If no - why did it take any time at all to produce them?
>
> Not sure what you mean, it always  takes time to produce a document, even
> if the document is just a "rock fetch".

sorry; "rock fetch" is beyond my scope of American idiom. But version -01 
of the framework document is dated July 19, 2001, and the first version 
submitted to the IESG is dated February 15, 2002. (I don't have a copy of 
-00). So the WG spent at least 7 months and 5 versions on it before 
submission. I took that as a hint that there might have been controversy in 
the working group about it.

> Harald> there is  little that  the IESG can  do when  the WG knows  what
> the Harald> comments are and chooses not to act upon them for 2-5 months.
>
> This reminds me  of Dilbert's pointy-haired boss, who  says "your project
> is late,  so I  want  you to  give me  hourly  status reports."

just as well that I did not suggest that the IESG could yell more at the WG 
to update the documents, then....

> When we
> have documents which aren't really necessary in the first place, which
> ultimately will not  have any impact on the  technology, but which need
> to be massaged and remassaged  so as to get  them past the  IESG, I think
> it's  quite clear where the responsibility for the delay is coming from.

If I accepted your evaluation as true, I'd agree with you.

> Harald> And  I don't  understand why  WG updates  to fix  problems  take
> 2-3 Harald> months  per cycle  when  the WG  thinks  that it's  important
> to  be Harald> finished with the docs.
>
> Well, each  objection from  the IESG  needs to be  discussed and  a
> response crafted.

which should take approximately 3 days of work, IMHO.
Comments that translate to "you are referencing an obsolete version of 
LDAP" should take approximately 2 minutes to fix.

> Harald> is  the IESG  supposed  to care  about  inconsistencies between
> the Harald> requirements (which  are what the  *WG* thinks should  be
> satisfied) Harald> and the technologies that will be proposed for
> standardization?
>
> Sure; but the reqs,  framework, protocol specs, and applicability
> statements were all  ready 18 months ago.  They  could have been
> submitted  as a group. But we were told, "first you need  to submit the
> first document, then a year or so  later you can  submit the  second".
> This is  a very peculiar  way to encourage progress  ;-) From the WG
> perspective, the specs  have been ready for review  forever, but  the
> IESG has  refused to  look at them  because of bogus process issues.  And
> then they turn around and accuse the WG of making slow progress!

I did not see that instruction.
On the surface, your suggestion seems a sensible one; if the WG had 
officially declared consensus on all the documents at that time, I do not 
understand why you couldn't do it that way.

Did the WG declare consensus on all those documents 18 months ago (January 
2002)? (And in the interest of being specific, I'd like you to say which 
documents you think of when you say that......)

                    Harald




From owner-ietf@ietf.org  Thu Jul  3 17:11: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 RAA06832
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 17:11:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YBGj-0007Kh-6w
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 17:05:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YBG7-0007Dh-Rr
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 17:04: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 RAA06433
	for <ietf@ietf.org>; Thu, 3 Jul 2003 17:04:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YBG6-0002iS-00
	for ietf@ietf.org; Thu, 03 Jul 2003 17:04:50 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YBG5-0002iP-00
	for ietf@ietf.org; Thu, 03 Jul 2003 17:04:49 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h63L4ltU017475;
	Thu, 3 Jul 2003 17:04:47 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h63L4lVZ017474;
	Thu, 3 Jul 2003 17:04:47 -0400
Date: Thu, 3 Jul 2003 17:04:47 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200307032104.h63L4lVZ017474@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: the end-to-end name problem
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

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

    > a dictionary is hardly a compelling substitute for going direct to the
    > paper(s) in which the end to end principle has been articulated.

I couldn't agree with your suggestion more; were I Tsar of the Internet, I'd
make it a rule to bind and gag anyone who utters the phrase "end-to-end
principle" who hasn't read this excellent paper, easily available here:

    http://www.reed.com/Papers/EndtoEnd.html

However, I will differ with you slightly, in that reading this paper will not
necessarily produce 100% enlightenment. If you actually talk with the authors,
you will discover that in the time since the paper was written, their
understanding of what they were trying to get at has deepened (they now talk
about a "network end-end principle", which has important differenced with an
"application end-end principle"), and in addition two of them (Reed and Clark)
have since gone in slightly different directions in their thinking!

I was discussing this all with them at length, but alas I don't have access to
all my notes at this instant; perhaps I can produce another page containing
some additional commentary on the end-end principle, in addition to:

    http://users.exis.net/~jnc/tech/end_end.html

which discusses one popular misconception about the end-end principle.

	Noel



From owner-ietf@ietf.org  Thu Jul  3 17:14: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 RAA07062
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 17:14:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YBMX-0008AM-36
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 17:11:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YBMJ-00081t-Ix
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 17:11: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 RAA06818
	for <ietf@ietf.org>; Thu, 3 Jul 2003 17:11:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YBMI-0002wB-00
	for ietf@ietf.org; Thu, 03 Jul 2003 17:11:14 -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 19YBMH-0002w8-00
	for ietf@ietf.org; Thu, 03 Jul 2003 17:11:13 -0400
Received: from localhost ([127.0.0.1] helo=ran.psg.com)
	by ran.psg.com with esmtp (Exim 4.20)
	id 19YBMB-000CQu-6R; Thu, 03 Jul 2003 14:11:07 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 3 Jul 2003 14:11:06 -0700
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: Re: The requirements cycle (Re: WG review: Layer 2 Virtual....)
References: <255350000.1057197230@askvoll.hjemme.alvestrand.no>
	<200307031652.h63Gqmfq009031@rtp-core-1.cisco.com>
	<20030703145917.08caf04b.moore@cs.utk.edu>
Message-Id: <E19YBMB-000CQu-6R@ran.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> L2VPN is not progress.  It's the opposite.

users do want ways to bridge a layer two lan across the internet.
and this seems a legitimate desire that should be doable without
breaking anything.  of course, this will drift into areas where we
know large l2 networks have problems.  but, if properly done, that
should not affect the internet across which the lans are bridged.

otoh, those kinds of l2 issues and others should make us very
cautious when evaluating schemes to make the transforming the
internet core into an l2 circuit network.

randy




From owner-ietf@ietf.org  Thu Jul  3 17:27: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 RAA07606
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 17:27:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YBYf-0002PP-Lm
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 17:24:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YBTI-0001aB-AO
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 17:18: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 RAA07277
	for <ietf@ietf.org>; Thu, 3 Jul 2003 17:18:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YBTG-0003JJ-00
	for ietf@ietf.org; Thu, 03 Jul 2003 17:18:26 -0400
Received: from gull.mail.pas.earthlink.net ([207.217.120.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YBTG-0003JF-00
	for ietf@ietf.org; Thu, 03 Jul 2003 17:18:26 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19YBTC-0004GO-00; Thu, 03 Jul 2003 14:18:22 -0700
Date: Thu, 3 Jul 2003 17:14:32 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Randy Bush <randy@psg.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: The requirements cycle (Re: WG review: Layer 2 Virtual....)
Message-Id: <20030703171432.08df329b.moore@cs.utk.edu>
In-Reply-To: <E19YBMB-000CQu-6R@ran.psg.com>
References: <255350000.1057197230@askvoll.hjemme.alvestrand.no>
	<200307031652.h63Gqmfq009031@rtp-core-1.cisco.com>
	<20030703145917.08caf04b.moore@cs.utk.edu>
	<E19YBMB-000CQu-6R@ran.psg.com>
X-Mailer: Sylpheed version 0.9.1 (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

] > L2VPN is not progress.  It's the opposite.
] 
] users do want ways to bridge a layer two lan across the internet.

yeah, I know.  of course, there are some things users want to do that you simply 
cannot make work well.  not that we've let that stop us before...



From owner-ietf@ietf.org  Thu Jul  3 19:39: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 TAA26112
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 19:39:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YDW5-0007b9-7k
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 19:29:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YDV3-0007Mq-Fr
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 19:28: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 TAA25749
	for <ietf@ietf.org>; Thu, 3 Jul 2003 19:28:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YD0l-0007nl-00
	for ietf@ietf.org; Thu, 03 Jul 2003 18:57:07 -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 19YD0k-0007nE-00
	for ietf@ietf.org; Thu, 03 Jul 2003 18:57:06 -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 IAA1609869;
	Fri, 4 Jul 2003 08:56:34 +1000 (EST)
Message-ID: <3F04B4A1.FB8061DB@swin.edu.au>
Date: Fri, 04 Jul 2003 08:56:33 +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: the end-to-end name problem
References: <43FC238C-AD90-11D7-A0F9-000393414368@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


S Woodside wrote:
	[..]
> That is, perhaps, a good thing, since I think that most naive people
> will THINK that they intuitively grasp what end-to-end means, but they
> are wrong.

Most naive people are wrong about many things, but this is not an argument
for making up new words to express broadly-similar-but-different-in-context
concepts. It is an argument for naive people to recognize their lack
of knowledge and go to the sources pertinent to the subject matter.
Which, for the purposes of understanding packet networking and "the
internet", is NOT your local dictionary.

gja



From owner-ietf@ietf.org  Thu Jul  3 21:37: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 VAA29523
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Jul 2003 21:37:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YFMF-0007Ys-W1
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 21:27:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YFM1-0007Ri-C7
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 21:27: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 VAA29353
	for <ietf@ietf.org>; Thu, 3 Jul 2003 21:27:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YFLz-0007QD-00
	for ietf@ietf.org; Thu, 03 Jul 2003 21:27:11 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19YFLy-0007PN-00
	for ietf@ietf.org; Thu, 03 Jul 2003 21:27:10 -0400
Received: from cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 03 Jul 2003 18:28:12 -0700
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h641Qd7F012389;
	Thu, 3 Jul 2003 18:26:39 -0700 (PDT)
Received: from ABIERMAN-W2K.cisco.com (sjc-vpn2-909.cisco.com [10.21.115.141])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AJD90685;
	Thu, 3 Jul 2003 18:26:38 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030703182332.024cbfa0@mira-sjc5-c.cisco.com>
X-Sender: abierman@mira-sjc5-c.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 03 Jul 2003 18:23:50 -0700
To: Soohong Daniel Park <soohong.park@samsung.com>
From: Andy Bierman <abierman@cisco.com>
Subject: Re: Where can I find capwap BOF Agenda ?
Cc: ietf@ietf.org
In-Reply-To: <010e01c34033$126f0000$b7cbdba8@daniel7209>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 05:44 PM 7/1/2003, Soohong Daniel Park wrote:
>Hi all
>
>I am searching for capwap Agenda....

http://www.ietf.org/ietf/03jul/capwap.txt


>Friday, July 18
>OPS  capwap  Control And Provisioning of Wirelsss Acc. Point BOF
>
>
>
>Daniel (Soohong Daniel Park)
>Mobile Platform Lab,SAMSUNG Electronics

Andy




From owner-ietf@ietf.org  Fri Jul  4 00:08: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 AAA02613
	for <ietf-web-archive@odin.ietf.org>; Fri, 4 Jul 2003 00:08:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YHhO-0005m6-9G
	for ietf-list@asgard.ietf.org; Thu, 03 Jul 2003 23:57:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YHgp-0005gB-Ej
	for ietf@asgard.ietf.org; Thu, 03 Jul 2003 23:56: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 XAA02318
	for <ietf@ietf.org>; Thu, 3 Jul 2003 23:56:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YHgn-0001Ns-00
	for ietf@ietf.org; Thu, 03 Jul 2003 23:56:49 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YHgm-0001Nb-00
	for ietf@ietf.org; Thu, 03 Jul 2003 23:56:48 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 160CF13978
	for <ietf@ietf.org>; Fri,  4 Jul 2003 03:56:19 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt 
In-Reply-To: Message from Simon Josefsson <jas@extundo.com> 
	of "Tue, 01 Jul 2003 03:51:18 +0200."
	<iluof0fggkp.fsf@latte.josefsson.org> 
X-Mailer: MH-E 7.4; nmh 1.0.4; GNU Emacs 21.3.1
Date: Fri, 04 Jul 2003 03:56:19 +0000
Message-Id: <20030704035619.160CF13978@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

sorry to lose momentum on this thread, i got busy with something else briefly:

> > a dns resource lives where its parent NS RRs say it lives -- and not, as
> > you also suggest...
> >
> >> The hostport describes the authority that know the intended DNS
> >> resource.  An authority is useful even for abstract, non-DNS-protocol,
> >> DNS resources.  DNS resources themselves are indexed by (NAME, CLASS,
> >> TYPE), but to distinguish between the answer that entity A
> >> knows/generate, and the answer that entity B knows/generate, an
> >> authority scope like "hostport" is needed.
> >
> > ...in the answers that different entities can generate.
> 
> This view limit the usefulness of the URI, as it cannot be used to
> refer to, e.g., not-yet delegated data.  It can be useful to use DNS
> URIs to denote DNS data in a delegation request, to indicate where the
> new data will be placed, so it can be checked for conformance with
> various rules.

i guess we're in different weeds now.  because of the high abstractness
of your "hostport" definition, there's no guaranty that the dns protocol
will even be used by the uri-handler to resolve the pseudoquery.  so, the
idea of "not-yet-delegated" has no foundation at all.

here's the real issue: there are many companies and political movements who
think that iana's namespace is not the only namespace.  new.net, for
example.  iab takes a very strong "single unique namespace" view, and as
such, the i* organizations (iesg in this case) will probably (and ought to,
in my view) take a very dim view of any attempt to standardize a uri that
permits a "multiple namespace" fiction to be operable.

to me the layering violation of your "hostpart" suggestion is jarring, and
obvious, and is approximately equal to extending "hostpart" in normal http:
(and telnet: and mail: and so on) uri's to allow one to specify not only a
hostname, but also the address of the dns server which ought to be asked
to resolve the A or AAAA query.  "http://new.net:foo.sex/bar/", anyone?  if
you answered "no" then you gotta ask yourself why allow a "hostport" in a
dns: uri if you dislike its tangible equivilent in other parts of the spec.

> > you can't have it both ways.  either you're trying to represent dns data
> > using the <qname,qtype,qclass> tuple, or you're trying to represent
> > the query itself.
> 
> I'm trying, like the document says, to represent dns data using the
> <qname,qtype,qclass> tuple together with the authority/server.  The
> authority was added to be able to denote data that, for some reason,
> is not linked into the global DNS.  The reason could be multiple
> roots, split-view DNS, disconnected operation, efficiency or whatnot.

ah, meat.  for multiple roots, the iab has (thankfully) recognized that
the dns just doesn't work that way.  for split-dns and disconnected
operation, the place to put that kind of policy is in the resolver, not
in every application who calls it.  see
	http://sa.vix.com/~vixie/proxynet.pdf
for an example of how to do this (it's from 1995 but the code still
compiles if anybody still wants it.)  the tradeoff between efficiency
and correctness weighs VERY heavily on the side of correctness, such that
the likelihood of getting the wrong data or no data by using "hostport"
for efficiency is MUCH HIGHER than the likelihood of a performance problem
from not using it.  (for user populations of a global size, as ours is.)

> I could remove the hostport element if the consensus is that doing so
> would improve the usefulness of the URI.  Anyone else with an opinion?
> Remove hostport or keep it?

for my part, i'd like to hear the iab's input, since this goes to the
architecture of the overall internet system.



From owner-ietf@ietf.org  Fri Jul  4 01:21:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04276
	for <ietf-web-archive@odin.ietf.org>; Fri, 4 Jul 2003 01:21:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YIry-0004zy-2i
	for ietf-list@asgard.ietf.org; Fri, 04 Jul 2003 01:12:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YIrh-0004tx-H8
	for ietf@asgard.ietf.org; Fri, 04 Jul 2003 01:12: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 BAA04170
	for <ietf@ietf.org>; Fri, 4 Jul 2003 01:12:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YIrf-00029O-00
	for ietf@ietf.org; Fri, 04 Jul 2003 01:12:07 -0400
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19YIre-00029L-00
	for ietf@ietf.org; Fri, 04 Jul 2003 01:12:06 -0400
Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h645BsST019738
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK);
	Fri, 4 Jul 2003 07:11:55 +0200
To: Paul Vixie <paul@vix.com>
Cc: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
References: <20030704035619.160CF13978@sa.vix.com>
From: Simon Josefsson <jas@extundo.com>
X-Payment: hashcash 1.2 0:030704:paul@vix.com:b205965dd6d03e0a
X-Hashcash: 0:030704:paul@vix.com:b205965dd6d03e0a
X-Payment: hashcash 1.2 0:030704:ietf@ietf.org:e53fe6f2bfdb7db6
X-Hashcash: 0:030704:ietf@ietf.org:e53fe6f2bfdb7db6
Date: Fri, 04 Jul 2003 07:11:53 +0200
In-Reply-To: <20030704035619.160CF13978@sa.vix.com> (Paul Vixie's message of
 "Fri, 04 Jul 2003 03:56:19 +0000")
Message-ID: <ilu65milvty.fsf@latte.josefsson.org>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=-32.4 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul Vixie <paul@vix.com> writes:

>> This view limit the usefulness of the URI, as it cannot be used to
>> refer to, e.g., not-yet delegated data.  It can be useful to use DNS
>> URIs to denote DNS data in a delegation request, to indicate where the
>> new data will be placed, so it can be checked for conformance with
>> various rules.
>
> i guess we're in different weeds now.  because of the high abstractness
> of your "hostport" definition, there's no guaranty that the dns protocol
> will even be used by the uri-handler to resolve the pseudoquery.  so, the
> idea of "not-yet-delegated" has no foundation at all.
>
> here's the real issue: there are many companies and political movements who
> think that iana's namespace is not the only namespace.  new.net, for
> example.  iab takes a very strong "single unique namespace" view, and as
> such, the i* organizations (iesg in this case) will probably (and ought to,
> in my view) take a very dim view of any attempt to standardize a uri that
> permits a "multiple namespace" fiction to be operable.

I don't see how this relate to being able to specify the DNS server to
query in a URI to denote DNS data.

Can you describe how the DNS URI with a "hostport" make multiple
namespaces operable?

Having multiple namespaces is not [inter]operable by definition, IMHO.

The DNS URI is not an attempt in this direction.

> to me the layering violation of your "hostpart" suggestion is jarring, and
> obvious, and is approximately equal to extending "hostpart" in normal http:
> (and telnet: and mail: and so on) uri's to allow one to specify not only a
> hostname, but also the address of the dns server which ought to be asked
> to resolve the A or AAAA query.  "http://new.net:foo.sex/bar/", anyone?  if
> you answered "no" then you gotta ask yourself why allow a "hostport" in a
> dns: uri if you dislike its tangible equivilent in other parts of the spec.

I see no problem here.  A HTTP URI should not contain the DNS server
address to use, since the HTTP specification describe how the server
is found.  Same goes for mailto; RFC 821 and 2821 describe how the
SMTP server for a mail address is found.  Adding the DNS server to use
would expose details that should be hidden in the application.

The situation is different for a DNS URI, since RFC 1024/1025 describe
how you query a specific DNS server (IP) via the DNS protocol.

I claim it can be useful to specify this information, but acknowledge
that removing the hostport would remove this potential confusion.

>> > you can't have it both ways.  either you're trying to represent dns data
>> > using the <qname,qtype,qclass> tuple, or you're trying to represent
>> > the query itself.
>> 
>> I'm trying, like the document says, to represent dns data using the
>> <qname,qtype,qclass> tuple together with the authority/server.  The
>> authority was added to be able to denote data that, for some reason,
>> is not linked into the global DNS.  The reason could be multiple
>> roots, split-view DNS, disconnected operation, efficiency or whatnot.
>
> ah, meat.  for multiple roots, the iab has (thankfully) recognized that
> the dns just doesn't work that way.

The global DNS namespace and the DNS protocol are not the same thing.

I believe the IAB has only recognized that the former, the namespace,
doesn't work with multiple roots, in RFC 2826.  And like I say above,
I don't see how the DNS URI further the multiple namespace root cause.

That the DNS protocol can handle multiple roots is a technical
property that can be used for good purposes, in which "hostport" can
be useful.  (Of course, it is not only useful for multiple roots.)  Do
you have a reference to where the IAB recognize that the DNS protocol
technically doesn't work with multiple roots?

> for split-dns and disconnected operation, the place to put that kind
> of policy is in the resolver, not in every application who calls it.

DNS URIs can be used to put this kind of policy in the resolver.
Applications are not generally expected to support DNS URIs.

> the tradeoff between efficiency and correctness weighs
> VERY heavily on the side of correctness, such that the likelihood of
> getting the wrong data or no data by using "hostport" for efficiency
> is MUCH HIGHER than the likelihood of a performance problem from not
> using it.  (for user populations of a global size, as ours is.)

Some people still do experiment to improve the efficiency in the DNS.
The DNS URI is not intended to be used widely (see the specification,
and "Intended Usage"), nor will the "hostport" field always be
present; that's why it is optional.  People would avoid using the
"hostport" field if it decreased correctness for them.

>> I could remove the hostport element if the consensus is that doing so
>> would improve the usefulness of the URI.  Anyone else with an opinion?
>> Remove hostport or keep it?
>
> for my part, i'd like to hear the iab's input, since this goes to the
> architecture of the overall internet system.

There hasn't been much input on the DNS URI, so I do appreciate when
anyone looks at it.

I guess we simply have different opinions, so I'm not sure splitting
more hairs over various definitions will be productive, although
hopefully this discussion can be informative for others, when they
form their own opinion.

Thanks,
Simon




From owner-ietf@ietf.org  Sat Jul  5 03:15:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01801
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 03:15:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Yh2p-00040O-7e
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 03:01:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Yh25-0003xR-P5
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 03:00: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 DAA01543
	for <ietf@ietf.org>; Sat, 5 Jul 2003 03:00:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Yh22-0006pO-00
	for ietf@ietf.org; Sat, 05 Jul 2003 03:00:26 -0400
Received: from [203.199.93.15] (helo=WS0005.indiatimes.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Yh21-0006oz-00
	for ietf@ietf.org; Sat, 05 Jul 2003 03:00:26 -0400
Received: from 192.168.57.15 (a2 [192.168.57.22])
	by WS0005.indiatimes.com (8.9.3/8.9.3) with SMTP id MAA08346
	for <ietf@ietf.org>; Sat, 5 Jul 2003 12:29:24 +0530
From: "Rohit Gupta" <rohitgupta416@indiatimes.com>
Message-Id: <200307050659.MAA08346@WS0005.indiatimes.com>
To: <ietf@ietf.org>
Reply-To: "Rohit Gupta"<rohitgupta416@indiatimes.com>
Subject: First Timers
Date: Sat, 05 Jul 2003 12:23:51 +0530
X-URL: http://indiatimes.com
Content-Type: multipart/alternative;
	   boundary="=_MAILER_ATTACH_BOUNDARY1_200375612235135005211"
MIME-Version: 1.0
Sender: owner-ietf@ietf.org
Precedence: bulk

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

Hi,


We will be attending the 57th IETF meeting to be held in Vienna and this will be ours first IETF Meeting. Is there any dress code which is followed out there?


I went  though the Tao of IETF from the ietf.org site and just was interested in others experiences.


Rohit


 


 
Get Your Private, Free E-mail from Indiatimes at  http://email.indiatimes.com
Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com
Bid for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now !

--=_MAILER_ATTACH_BOUNDARY1_200375612235135005211
Content-Type: text/html; charset=us-ascii

<P>Hi,</P>
<P>We will be attending the 57th IETF meeting to be held in Vienna and this will be ours first IETF Meeting. Is there any dress code which is followed out there?</P>
<P>I went&nbsp; though the Tao of IETF from the ietf.org site and just was interested in others experiences.</P>
<P>Rohit</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<hr><font face="Arial" size="2"><b>Get Your Private, Free E-mail from Indiatimes at  </font><a href="http://email.indiatimes.com"><font face="Arial" size="2">http://email.indiatimes.com</a></b><br>Buy The Best In <b>BOOKS</b> at <A href="http://www.bestsellers.indiatimes.com">http://www.bestsellers.indiatimes.com</A><br>Bid for <b>Air Tickets @ Re.1</b> on Air Sahara Flights. Just log on to <a href="http://airsahara.indiatimes.com">http://airsahara.indiatimes.com</a> and Bid Now !</font>

--=_MAILER_ATTACH_BOUNDARY1_200375612235135005211--




From owner-ietf@ietf.org  Sat Jul  5 06:17: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 GAA04601
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 06:17:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Yjyj-0004v8-SE
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 06:09:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Yjyd-0004sB-RY
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 06:09:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04489
	for <ietf@ietf.org>; Sat, 5 Jul 2003 06:09:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Yjyb-0000CV-00
	for ietf@ietf.org; Sat, 05 Jul 2003 06:09: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 19Yjya-0000CS-00
	for ietf@ietf.org; Sat, 05 Jul 2003 06:09:05 -0400
Received: from cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 05 Jul 2003 03:05:42 -0700
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h65A8X7F015844;
	Sat, 5 Jul 2003 03:08:34 -0700 (PDT)
Received: (ole@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) id DAA20973; Sat, 5 Jul 2003 03:08:33 -0700 (PDT)
X-Authentication-Warning: wells.cisco.com: ole set sender to ole@cisco.com using -f
Date: Sat, 5 Jul 2003 03:08:33 -0700 (PDT)
From: "Ole J. Jacobsen" <ole@cisco.com>
Reply-To: Ole Jacobsen <ole@cisco.com>
To: Rohit Gupta <rohitgupta416@indiatimes.com>
cc: ietf@ietf.org
Subject: Re: First Timers
In-Reply-To: <200307050659.MAA08346@WS0005.indiatimes.com>
Message-ID: <Pine.HPX.4.44.0307050257360.15194-100000@wells.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Rohit,

The IETF prides itself on formality. You should be prepared to wear only
the finest and most conservative business suits. For social events such
as the opening reception, we generally expect to greet each other in
tuxedos.

See for example https://www.execstyle.com/fashion.asp

OK, I'm kidding!

This will be my 50th IETF, and I can count on one hand the number of
people times the number of events where I have actually seen a suit.

"Casual and comfortable" is a phrase that describes us well. We favor the
practical over the formal. Don't be surprised to see people sitting on
the floor or hanging out the side of a building if such a location
improves 802.11 reception.

Welcome to the club!

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj


On Sat, 5 Jul 2003, Rohit Gupta wrote:

> Hi,
>
>
> We will be attending the 57th IETF meeting to be held in Vienna and this
> will be ours first IETF Meeting. Is there any dress code which is
> followed out there?
>
>
> I went though the Tao of IETF from the ietf.org site and just was
> interested in others experiences.
>
>
> Rohit
>
>

>




From owner-ietf@ietf.org  Sat Jul  5 08:51:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06497
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 08:51:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YmNk-00046c-DL
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 08:43:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YmNN-00043g-5d
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 08:42: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 IAA06395
	for <ietf@ietf.org>; Sat, 5 Jul 2003 08:42:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YmNM-0000mg-00
	for ietf@ietf.org; Sat, 05 Jul 2003 08:42:48 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19YmNL-0000mX-00
	for ietf@ietf.org; Sat, 05 Jul 2003 08:42:47 -0400
Received: from employees.org (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 05 Jul 2003 05:44:13 -0700
Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h65CgF7F024118
	for <ietf@ietf.org>; Sat, 5 Jul 2003 05:42:15 -0700 (PDT)
Received: from cisco.com (sjc-vpn3-85.cisco.com [10.21.64.85])
	by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with SMTP id AHS84194;
	Sat, 5 Jul 2003 05:33:33 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation); Sat, 5 Jul 2003 08:41:59 -0400
Date: Sat, 5 Jul 2003 08:41:59 -0400
From: Scott W Brim <swb@employees.org>
To: ietf@ietf.org
Subject: Re: First Timers
Message-ID: <20030705124159.GH2188@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>, ietf@ietf.org
References: <200307050659.MAA08346@WS0005.indiatimes.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200307050659.MAA08346@WS0005.indiatimes.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, Jul 05, 2003 12:23:51PM +0530, Rohit Gupta allegedly wrote:
> We will be attending the 57th IETF meeting to be held in Vienna and
> this will be ours first IETF Meeting. Is there any dress code which is
> followed out there?

Most people wear shoes.



From owner-ietf@ietf.org  Sat Jul  5 09:23: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 JAA07148
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 09:23:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YmwZ-0006DY-Km
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 09:19:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ymw3-0006A6-8g
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 09:18: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 JAA07051
	for <ietf@ietf.org>; Sat, 5 Jul 2003 09:18:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ymw2-0000yL-00
	for ietf@ietf.org; Sat, 05 Jul 2003 09:18:38 -0400
Received: from h-135-207-24-32.research.att.com ([135.207.24.32] helo=mailman.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ymw1-0000xs-00
	for ietf@ietf.org; Sat, 05 Jul 2003 09:18:37 -0400
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mailman.research.att.com (8.12.8/8.12.8) with ESMTP id h65DBK3j009407;
	Sat, 5 Jul 2003 09:11:22 -0400
Received: from berkshire.research.att.com (raptor.research.att.com [135.207.23.32])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h65DI3V02861;
	Sat, 5 Jul 2003 09:18:03 -0400 (EDT)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id BDE3D7B4D; Sat,  5 Jul 2003 09:18:01 -0400 (EDT)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
To: "Rohit Gupta" <rohitgupta416@indiatimes.com>
Cc: ietf@ietf.org
Subject: Re: First Timers 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 05 Jul 2003 09:18:01 -0400
From: "Steven M. Bellovin" <smb@research.att.com>
Message-Id: <20030705131801.BDE3D7B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <200307050659.MAA08346@WS0005.indiatimes.com>, "Rohit Gupta" writes:
>
>--=_MAILER_ATTACH_BOUNDARY1_200375612235135005211
>Content-Type: text/plain; charset=us-ascii
>
>Hi,
>
>
>We will be attending the 57th IETF meeting to be held in Vienna and this will 
>be ours first IETF Meeting. Is there any dress code which is followed out ther
>e?

"Extremely casual".  A T-shirt, shorts, and sandals are quite common, 
and (in warm weather) close to the norm.

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





From owner-ietf@ietf.org  Sat Jul  5 10:49: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 KAA09638
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 10:49:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YoFr-0000Oz-OY
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 10:43:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YoFQ-0000Lo-8q
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 10:42: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 KAA09518
	for <ietf@ietf.org>; Sat, 5 Jul 2003 10:42:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YoFO-0001f5-00
	for ietf@ietf.org; Sat, 05 Jul 2003 10:42:42 -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 19YoFO-0001ey-00
	for ietf@ietf.org; Sat, 05 Jul 2003 10:42:42 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19YUDl-0005KW-00; Fri, 04 Jul 2003 13:19:41 -0400
Date: Fri, 4 Jul 2003 13:19:36 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Rohit Gupta <rohitgupta416@indiatimes.com>
cc: ietf@ietf.org
Subject: Re: First Timers
In-Reply-To: <200307050659.MAA08346@WS0005.indiatimes.com>
Message-ID: <Pine.LNX.4.44.0307041317410.20491-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 5 Jul 2003, Rohit Gupta wrote:

Rohit,

I arrived with two backpacks, a laptop, and a sleeping bag and camped in
the hotel during my first IETF.

Enjoy!
Scott


> Hi,
>
>
> We will be attending the 57th IETF meeting to be held in Vienna and this will be ours first IETF Meeting. Is there any dress code which is followed out there?
>
>
> I went  though the Tao of IETF from the ietf.org site and just was interested in others experiences.
>
>
> Rohit
>
>
>
>
>
>
> Get Your Private, Free E-mail from Indiatimes at  http://email.indiatimes.com
> Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com
> Bid for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now !
>

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




From owner-ietf@ietf.org  Sat Jul  5 12:27: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 MAA10926
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 12:27:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ypli-0004S5-Ia
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 12:20:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ypkr-0004Qe-Rk
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 12:19: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 MAA10849
	for <ietf@ietf.org>; Sat, 5 Jul 2003 12:19:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ypkq-0003HT-00
	for ietf@ietf.org; Sat, 05 Jul 2003 12:19:16 -0400
Received: from nerf.yikes.com ([157.22.12.202] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ypkp-0003HP-00
	for ietf@ietf.org; Sat, 05 Jul 2003 12:19:15 -0400
Received: from [63.193.24.36] (rick.perlman.com [63.193.24.36])
	by nerf.yikes.com (8.12.9/8.12.6) with ESMTP id h65GIXcs001415
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 5 Jul 2003 09:18:34 -0700 (PDT)
User-Agent: Microsoft-Entourage/10.1.1.2418
Date: Sat, 05 Jul 2003 09:19:05 -0700
Subject: Re: First Timers
From: Richard Perlman <perl@lucent.com>
To: Ole Jacobsen <ole@cisco.com>, Rohit Gupta <rohitgupta416@indiatimes.com>
CC: <ietf@ietf.org>
Message-ID: <BB2C4889.13ED6%perl@lucent.com>
In-Reply-To: <Pine.HPX.4.44.0307050257360.15194-100000@wells.cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Rohit:

Don't believe a word Ole says.  I have seen him at many of his 50 IETF
meetings and most of the time his T-Shirt has been recently washed.

Truly, for the meetings and opening Sunday night "feed," wear whatever you
feel comfortable in.  As noted by others, T-Shirts, shorts and sandals are
common, but at list one distinguished attendee has never been seen in less
than a 3-piece suit (really).

HOWEVER, consider that the meetings will be in Vienna and although it is
summer, Vienna is still a little on the conservative side (no political
comment intended).  So, if you plan on going around town, I'd suggest a
sport-shirt (short sleeved would be fine) and long pants.  Depending on
where you want to eat dinner, you might need a jacket - but of course, your
choice of restaurants is strictly up to you.

Richard

On 7/5/03 3:08 AM, "Ole J. Jacobsen" <ole@cisco.com> wrote:

...
> OK, I'm kidding!
> 
> This will be my 50th IETF, and I can count on one hand the number of
> people times the number of events where I have actually seen a suit.
> 
> "Casual and comfortable" is a phrase that describes us well. We favor the
> practical over the formal. Don't be surprised to see people sitting on
> the floor or hanging out the side of a building if such a location
> improves 802.11 reception.
> 
> Welcome to the club!
> 
> Ole




From owner-ietf@ietf.org  Sat Jul  5 13:15: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 NAA11672
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 13:15:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YqY7-0005ur-5R
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 13:10:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YqXN-0005tO-PU
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 13:09: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 NAA11469
	for <ietf@ietf.org>; Sat, 5 Jul 2003 13:09:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YqXM-0003lg-00
	for ietf@ietf.org; Sat, 05 Jul 2003 13:09:24 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YqXL-0003la-00
	for ietf@ietf.org; Sat, 05 Jul 2003 13:09:23 -0400
Received: from BBFUJIP.brandenburg.com (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h65HCMF10005;
	Sat, 5 Jul 2003 10:12:23 -0700
Date: Sat, 5 Jul 2003 17:53:41 +0200
From: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: The Bat! (v1.63 Beta/11) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <1451723728.20030705175341@brandenburg.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: ietf@ietf.org
Subject: Re: The requirements cycle (Re: WG review: Layer 2 Virtual....)
In-Reply-To: <351620000.1057264376@askvoll.hjemme.alvestrand.no>
References: <200307031652.h63Gqmfq009031@rtp-core-1.cisco.com>
 <351620000.1057264376@askvoll.hjemme.alvestrand.no>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald,

HTA> even if a WG feels abused by the IESG, or its AD, that's no excuse for a WG
HTA> not fighting back - in this case, by rapidly removing the IESG's apparent
HTA> excuses for delay.

HTA> Dejection is an explanation, not an excuse.


This seems to reflect a view of human behavior that might work well for
machines, but not for humans.  When people in positions of authority
impose situations that are silly, wasteful, damaging, etc., those on
whom they are imposed usually view them as silly, wasteful, damaging, etc.

When people believe their actions are s/w/d/... they have a reaction
that is generally called "natural".  A typical result of this reaction
is de-motivation.

We might applaud those who can overcome this natural process, but we
should never lame those who do not.

Blame the folks doing the imposing.

Or, to state this more constructively, do not focus on the people who
become discouraged by external forces that are... discouraging.

Focus in getting those forces turned into something constructive.


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 Jul  5 13: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 NAA12112
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 13:44:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YqyE-0006xX-RM
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 13:37:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Yqxu-0006vw-Lk
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 13:36: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 NAA11995
	for <ietf@ietf.org>; Sat, 5 Jul 2003 13:36:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Yqxs-0003za-00
	for ietf@ietf.org; Sat, 05 Jul 2003 13:36:48 -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 19Yqxr-0003zV-00
	for ietf@ietf.org; Sat, 05 Jul 2003 13:36:47 -0400
Received: from localhost ([127.0.0.1] helo=ran.psg.com)
	by ran.psg.com with esmtp (Exim 4.20)
	id 19Yqxo-000Otu-Sq; Sat, 05 Jul 2003 10:36:44 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sat, 5 Jul 2003 10:36:44 -0700
To: "Rohit Gupta" <rohitgupta416@indiatimes.com>
Cc: <ietf@ietf.org>
Subject: Re: First Timers
References: <200307050659.MAA08346@WS0005.indiatimes.com>
Message-Id: <E19Yqxo-000Otu-Sq@ran.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> We will be attending the 57th IETF meeting to be held in Vienna and this
> will be ours first IETF Meeting. Is there any dress code which is followed
> out there?

yes, clothes are pretty universally expected to be worn.

randy




From owner-ietf@ietf.org  Sat Jul  5 14:03: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 OAA12402
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 14:03:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YrIa-0007oG-Vo
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 13:58:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YrGD-0007kd-UG
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 13:55: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 NAA12317
	for <ietf@ietf.org>; Sat, 5 Jul 2003 13:55:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YrGC-00048a-00
	for ietf@ietf.org; Sat, 05 Jul 2003 13:55:44 -0400
Received: from nic.cafax.se ([192.71.228.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YrGA-00048X-00
	for ietf@ietf.org; Sat, 05 Jul 2003 13:55:43 -0400
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h65Htfmb003943;
	Sat, 5 Jul 2003 19:55:41 +0200 (MEST)
Received: (from bygg@localhost)
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h65HtfeI003942;
	Sat, 5 Jul 2003 19:55:41 +0200 (MEST)
Date: Sat, 5 Jul 2003 19:55:40 WET DST
From: Johnny Eriksson <bygg@cafax.se>
To: <ietf@ietf.org>
Cc: "Rohit Gupta" <rohitgupta416@indiatimes.com>
Subject: Re: First Timers
In-Reply-To: Your message of Sat, 5 Jul 2003 10:36:44 -0700
Message-ID: <CMM.0.91.0.1057427740.bygg@nic.cafax.se>
Sender: owner-ietf@ietf.org
Precedence: bulk

Randy Bush <randy@psg.com>:

> > We will be attending the 57th IETF meeting to be held in Vienna and this
> > will be ours first IETF Meeting. Is there any dress code which is followed
> > out there?
> 
> yes, clothes are pretty universally expected to be worn.

What randy means is that worn clothing is OK.

> randy

--Johnny



From owner-ietf@ietf.org  Sat Jul  5 14: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 OAA12830
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 14:34:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YrmX-0000aB-JZ
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 14:29:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YrmL-0000YQ-Sg
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 14:28:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12691
	for <ietf@ietf.org>; Sat, 5 Jul 2003 14:28:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YrmG-0004PQ-00
	for ietf@ietf.org; Sat, 05 Jul 2003 14:28:52 -0400
Received: from balin.ap.univie.ac.at ([131.130.11.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YrmF-0004PM-00
	for ietf@ietf.org; Sat, 05 Jul 2003 14:28:51 -0400
Received: from univie.ac.at (localhost [127.0.0.1])
	by balin.ap.univie.ac.at (8.12.8/8.11.1/0.0.0) with ESMTP id h65ISnEA1378874;
	Sat, 5 Jul 2003 20:28:49 +0200 (CEST)
Message-ID: <3F0718E0.4020906@univie.ac.at>
Date: Sat, 05 Jul 2003 20:28:48 +0200
From: Ulrich Kiermayr <ulrich.kiermayr@univie.ac.at>
Organization: Vienna University Computer Center
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701
X-Accept-Language: en-us, en, de-at
MIME-Version: 1.0
To: Richard Perlman <perl@lucent.com>
CC: Ole Jacobsen <ole@cisco.com>, Rohit Gupta <rohitgupta416@indiatimes.com>,
        ietf@ietf.org
Subject: Re: First Timers
References: <BB2C4889.13ED6%perl@lucent.com>
In-Reply-To: <BB2C4889.13ED6%perl@lucent.com>
X-Enigmail-Version: 0.75.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by balin.ap.univie.ac.at id h65ISnEA1378874
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hi,

> HOWEVER, consider that the meetings will be in Vienna and although it i=
s
> summer, Vienna is still a little on the conservative side (no political
> comment intended). =20

Since when? (Ok - I was out of town last week, so it might have changed=20
during that time)

> So, if you plan on going around town, I'd suggest a
> sport-shirt (short sleeved would be fine) and long pants. =20

Hmmmm, considering the mild 35=B0C we had in June, this dresscode might=20
cause ou some problems. - Note that air-conditioning is not too common=20
in AT.
Seriously, as long as you do not walk around without any clothes,=20
everything is ok. :-)

> Depending on
> where you want to eat dinner, you might need a jacket - but of course, =
your
> choice of restaurants is strictly up to you.

I live here - I go out regularly - i never was required to wear a jacket=20
  to diner. But maybe there are places here I still do not know ....

lG uk
--=20
------------------------------------------------------------------------
Ulrich Kiermayr         Zentraler Informatikdienst der Universitaet Wien
Network Security              Universitaetsstrasse 7, 1010 Wien, Austria
------------------------------------------------------------------------
eMail:   ulrich.kiermayr@univie.ac.at          Tel: (+43 1) 4277 / 14104
Hotline: security.zid@univie.ac.at             Fax: (+43 1) 4277 /  9140
------------------------------------------------------------------------
GPG Key fingerprint =3D BF0D 5749 4DC1 ED74 AB67  7180 105F 491D A8D7 64D=
8





From owner-ietf@ietf.org  Sat Jul  5 17:01: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 RAA16197
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 17:01:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Yu4m-0004Pv-6h
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 16:56:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Yu3s-0004OR-7K
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 16:55: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 QAA15901
	for <ietf@ietf.org>; Sat, 5 Jul 2003 16:55:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Yu3q-0005TF-00
	for ietf@ietf.org; Sat, 05 Jul 2003 16:55:10 -0400
Received: from shockwave.systems.pipex.net ([62.241.160.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Yu3q-0005T5-00
	for ietf@ietf.org; Sat, 05 Jul 2003 16:55:10 -0400
Received: from ieee.org (userdd211.dsl.pipex.com [62.190.227.211])
	by shockwave.systems.pipex.net (Postfix) with ESMTP
	id 4DBC91623AAD6; Sat,  5 Jul 2003 21:54:36 +0100 (BST)
Message-ID: <3F073A77.A5D4B4D@ieee.org>
Date: Sat, 05 Jul 2003 21:52:07 +0100
From: Dominic Pinto <dominic.pinto@ieee.org>
Reply-To: dominic.pinto@ieee.org
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Cc: Rohit Gupta <rohitgupta416@indiatimes.com>, ietf@ietf.org
Subject: Re: First Timers
References: <Pine.HPX.4.44.0307050257360.15194-100000@wells.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> On Sat, 5 Jul 2003, Rohit Gupta wrote:
> 
> > Hi,
> >
> >
> > We will be attending the 57th IETF meeting to be held in Vienna and this
> > will be ours first IETF Meeting. Is there any dress code which is
> > followed out there?
> >
> >
> > I went though the Tao of IETF from the ietf.org site and just was
> > interested in others experiences.
> >


Hey, what's with this 'out there', X-Files, or maybe US-centric, stuff?



From owner-ietf@ietf.org  Sat Jul  5 17:01: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 RAA16202
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 17:01:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Yu2q-0004N0-PT
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 16:54:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Yu2C-0004LX-V0
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 16:53: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 QAA15865
	for <ietf@ietf.org>; Sat, 5 Jul 2003 16:53:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Yu2B-0005SK-00
	for ietf@ietf.org; Sat, 05 Jul 2003 16:53:27 -0400
Received: from shockwave.systems.pipex.net ([62.241.160.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Yu2B-0005SH-00
	for ietf@ietf.org; Sat, 05 Jul 2003 16:53:27 -0400
Received: from ieee.org (userdd211.dsl.pipex.com [62.190.227.211])
	by shockwave.systems.pipex.net (Postfix) with ESMTP id 68B1A160006D4
	for <ietf@ietf.org>; Sat,  5 Jul 2003 21:52:51 +0100 (BST)
Message-ID: <3F073A0F.4DB90A64@ieee.org>
Date: Sat, 05 Jul 2003 21:50:23 +0100
From: Dominic Pinto <dominic.pinto@ieee.org>
Reply-To: dominic.pinto@ieee.org
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: First Timers
References: <CMM.0.91.0.1057427740.bygg@nic.cafax.se>
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

Johnny Eriksson wrote:
> 
> Randy Bush <randy@psg.com>:
> 
> > > We will be attending the 57th IETF meeting to be held in Vienna and this
> > > will be ours first IETF Meeting. Is there any dress code which is followed
> > > out there?
> >
> > yes, clothes are pretty universally expected to be worn.
> 
> What randy means is that worn clothing is OK.
> 

as is pre-owned, and probably distressed.



From owner-ietf@ietf.org  Sat Jul  5 17:09: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 RAA16517
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 17:09:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YuEU-0005Nu-Bi
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 17:06:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YuEP-0005MB-Qs
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 17:06: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 RAA16473
	for <ietf@ietf.org>; Sat, 5 Jul 2003 17:06:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YuEO-0005cy-00
	for ietf@ietf.org; Sat, 05 Jul 2003 17:06:04 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YuEN-0005cp-00
	for ietf@ietf.org; Sat, 05 Jul 2003 17:06:03 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 60A441394C
	for <ietf@ietf.org>; Sat,  5 Jul 2003 21:05:33 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt 
In-Reply-To: Message from Simon Josefsson <jas@extundo.com> 
	of "Fri, 04 Jul 2003 07:11:53 +0200."
	<ilu65milvty.fsf@latte.josefsson.org> 
X-Mailer: MH-E 7.4; nmh 1.0.4; GNU Emacs 21.3.1
Date: Sat, 05 Jul 2003 21:05:33 +0000
Message-Id: <20030705210533.60A441394C@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> I don't see how this relate to being able to specify the DNS server to
> query in a URI to denote DNS data.
> 
> Can you describe how the DNS URI with a "hostport" make multiple
> namespaces operable?

i did.  any time you add to the tuple needed to identify an rrset, you're
extending the protocol.  <qname,qtype,qclass> is a full specification, and
<qname,qtype,qclass,datasource> is a different, and overfull, specification.

> Having multiple namespaces is not [inter]operable by definition, IMHO.

yes, i know that.  although i saw a header go by indicating that simon higgs
has commented on this thread, so by now you probably have evidence that that
view is not universal outside of the iab (and of course you and i.)

> The DNS URI is not an attempt in this direction.

i knew that.  but it will be abused to support the meaningless fiction of
multiple namespaces, and in fact i cannot think of any other likely use for
it -- the diagnostic capabilities you aluded to earlier in this thread are
not going to be accessed through a uri interface, except that if they are,
you will also need to be able to specify RD, buffer size, and so on.

> I claim it can be useful to specify this information, but acknowledge
> that removing the hostport would remove this potential confusion.

while i think we mean "to whom" differently in "useful" above, i think we've
found the beginnings of a basis for agreement.

> > ah, meat.  for multiple roots, the iab has (thankfully) recognized that
> > the dns just doesn't work that way.
> 
> The global DNS namespace and the DNS protocol are not the same thing.

and yet you said earlier that the back end protocol used by an invoker of
a dns: uri might not even be dns.  if hostport is present and denotes port
22, will the telnet protocol be used to satisfy the metaquery?  i really
do think that the dns namespace and the dns protocol cannot be usefully
disconnected from each other.

> I believe the IAB has only recognized that the former, the namespace,
> doesn't work with multiple roots, in RFC 2826.

what rfc 2826 says is that there can only be one root per namespace and
that the public namespace can therefore have only one root.  both of which
are true of course.

without quoting half of rfc's 1034, 1035, 2136, and 2181, let me ask what
a standards-limited caching resolver with no nonstandard extensions added
to support multiple namespaces will do when presented with the following
events:

Receive: query for www.foo.com IN A
Forward: query for www.foo.com (to known nameservers of foo.com)
Receive: response to forwarded query,
		including "foo.com IN NS www.bar.sex"
		      and "www.bar.sex IN A ..."
Forward: response to forwarded query (to client who initiated query)
Cache: www.foo.com IN A ...
       www.bar.sex IN A ...
       foo.com IN NS ...
Receive: query for www.bar.sex (will the answer be NXDOMAIN i wonder?)
Receive: query for mail.foo.com (will the query be forwarded to a .sex server?)

the two questions i add parenthetically at the end have no direct answer
in the dns standards documents.  i believe they can be answered by principle
since we know we're dealing with a distributed coherent reliable autonomous
database, but not everyone finds "coherence" convenient and not everyone
answers these kinds of questions by reference to principle in any case.

you can only find the answers directly from the existing literature if you
assume the existence of only one namespace and only one root.  if you want
to be able to operate in a multiple-namespace world, then you must implement
beyond the standards (which proxynet does) or try to extend the standards
(which has not been attempted unless you count rfc1597 and there only dimly.)

>                                                 And like I say above,
> I don't see how the DNS URI further the multiple namespace root cause.

without the hostport, it can't.  let's please just take it out and move on.

> That the DNS protocol can handle multiple roots is a technical
> property that can be used for good purposes, in which "hostport" can
> be useful.

but it can't.  if you want to support multiple namespaces, you have a
huge amount of work to do which is outside of, and not specified by, the
dns protocol.  see proxynet, which i gave a url for earlier, to see an
example of the kind of work that has to be done.

> The DNS URI is not intended to be used widely (see the specification,
> and "Intended Usage"), nor will the "hostport" field always be
> present; that's why it is optional.

if you make implementation of it optional, so that a url specifying it might
have undefined results depending on the whim of the implementor, that'd be
fine.  allow experiments, by all means.

>                                         People would avoid using the
> "hostport" field if it decreased correctness for them.

by that statement you tell me that you work with different people than i do.



From owner-ietf@ietf.org  Sat Jul  5 19:56: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 TAA20153
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 19:56:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YwjI-0007wO-1W
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 19:46:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YwjF-0007up-Dm
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 19:46: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 TAA20033
	for <ietf@ietf.org>; Sat, 5 Jul 2003 19:46:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YwjB-0006MB-00
	for ietf@ietf.org; Sat, 05 Jul 2003 19:46:01 -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 19YwjB-0006Ly-00
	for ietf@ietf.org; Sat, 05 Jul 2003 19:46:01 -0400
Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h65NjTpZ010367
	for <ietf@ietf.org>; Sat, 5 Jul 2003 16:45:29 -0700 (PDT)
Received: from cisco.com (sjc-vpn3-85.cisco.com [10.21.64.85])
	by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with SMTP id AHS95219;
	Sat, 5 Jul 2003 16:36:40 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation); Sat, 5 Jul 2003 19:45:12 -0400
Date: Sat, 5 Jul 2003 19:45:12 -0400
From: Scott W Brim <swb@employees.org>
To: ietf@ietf.org
Subject: Re: The requirements cycle (Re: WG review: Layer 2 Virtual....)
Message-ID: <20030705194512.D1840@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>, ietf@ietf.org
References: <200307031652.h63Gqmfq009031@rtp-core-1.cisco.com> <351620000.1057264376@askvoll.hjemme.alvestrand.no> <1451723728.20030705175341@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <1451723728.20030705175341@brandenburg.com>; from dcrocker@brandenburg.com on Sat, Jul 05, 2003 at 05:53:41PM +0200
Sender: owner-ietf@ietf.org
Precedence: bulk

This is wayyy too abstract and theoretical.  

On Sat, Jul 05, 2003 05:53:41PM +0200, Dave Crocker allegedly wrote:
> Harald,
> 
> HTA> even if a WG feels abused by the IESG, or its AD, that's no excuse for a WG
> HTA> not fighting back - in this case, by rapidly removing the IESG's apparent
> HTA> excuses for delay.
> 
> HTA> Dejection is an explanation, not an excuse.
> 
> 
> This seems to reflect a view of human behavior that might work well for
> machines, but not for humans.  When people in positions of authority
> impose situations that are silly, wasteful, damaging, etc., those on
> whom they are imposed usually view them as silly, wasteful, damaging, etc.
> 
> When people believe their actions are s/w/d/... they have a reaction
> that is generally called "natural".  A typical result of this reaction
> is de-motivation.
> 
> We might applaud those who can overcome this natural process, but we
> should never lame those who do not.
> 
> Blame the folks doing the imposing.
> 
> Or, to state this more constructively, do not focus on the people who
> become discouraged by external forces that are... discouraging.
> 
> Focus in getting those forces turned into something constructive.
> 
> 
> 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 Jul  5 21:34: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 VAA21645
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 21:34:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19YyJ0-0002hy-90
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 21:27:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YyIe-0002gK-Q5
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 21:26: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 VAA21529
	for <ietf@ietf.org>; Sat, 5 Jul 2003 21:26:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YyIc-0006mC-00
	for ietf@ietf.org; Sat, 05 Jul 2003 21:26:42 -0400
Received: from smtpsrv12.isis.unc.edu ([152.2.1.243] helo=smtp.unc.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19YyIc-0006m9-00
	for ietf@ietf.org; Sat, 05 Jul 2003 21:26:42 -0400
Received: from [192.168.1.101] (rdu57-255-231.nc.rr.com [66.57.255.231])
	(authenticated bits=0)
	by smtp.unc.edu (8.12.9/8.12.9) with ESMTP id h661P8t4004919
	(version=TLSv1/SSLv3 cipher=IDEA-CBC-SHA bits=128 verify=NOT);
	Sat, 5 Jul 2003 21:25:09 -0400 (EDT)
Date: Sat, 05 Jul 2003 21:25:04 -0400
From: Simon Spero <ses@unc.edu>
To: Scott W Brim <swb@employees.org>, ietf@ietf.org
Subject: Re: First Timers
Message-ID: <376460062.1057440304@[192.168.1.101]>
In-Reply-To: <20030705124159.GH2188@sbrim-w2k01>
References: <200307050659.MAA08346@WS0005.indiatimes.com>
 <20030705124159.GH2188@sbrim-w2k01>
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 Saturday, July 05, 2003 8:41 AM -0400 Scott W Brim <swb@employees.org> 
wrote:

> Most people wear shoes.

No shirt, no shoes, denial of service.

Simon
p.s.
If you must remove your shirt and tie, make sure you have a t-shirt on 
underneath it. 



From owner-ietf@ietf.org  Sat Jul  5 23:18: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 XAA23361
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 23:18:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Yzvd-0005f1-FI
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 23:11:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YzvF-0005dK-2I
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 23:10: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 XAA23164
	for <ietf@ietf.org>; Sat, 5 Jul 2003 23:10:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YzvC-0007J9-00
	for ietf@ietf.org; Sat, 05 Jul 2003 23:10:38 -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 19YzvC-0007Iu-00
	for ietf@ietf.org; Sat, 05 Jul 2003 23:10:38 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19Yft9-0005St-00; Sat, 05 Jul 2003 01:47:11 -0400
Date: Sat, 5 Jul 2003 01:47:10 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Simon Spero <ses@unc.edu>
cc: Scott W Brim <swb@employees.org>, <ietf@ietf.org>
Subject: Re: First Timers
In-Reply-To: <376460062.1057440304@[192.168.1.101]>
Message-ID: <Pine.LNX.4.44.0307050146420.21010-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 5 Jul 2003, Simon Spero wrote:

> --On Saturday, July 05, 2003 8:41 AM -0400 Scott W Brim <swb@employees.org>
> wrote:
>
> > Most people wear shoes.
>
> No shirt, no shoes, denial of service.

unless you feel more comfortable without shoes, in which case, please wash
your feet.

>
> Simon
> p.s.
> If you must remove your shirt and tie, make sure you have a t-shirt on
> underneath it.
>
>

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




From owner-ietf@ietf.org  Sat Jul  5 23:28: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 XAA23590
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Jul 2003 23:28:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Z09B-0006aJ-J6
	for ietf-list@asgard.ietf.org; Sat, 05 Jul 2003 23:25:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Z08W-0006YX-32
	for ietf@asgard.ietf.org; Sat, 05 Jul 2003 23:24:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23538
	for <ietf@ietf.org>; Sat, 5 Jul 2003 23:24:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Z08U-0007Qe-00
	for ietf@ietf.org; Sat, 05 Jul 2003 23:24:22 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Z08T-0007QU-00
	for ietf@ietf.org; Sat, 05 Jul 2003 23:24:21 -0400
Received: from rshockeybox.shockey.us (h-69-3-5-197.MCLNVA23.covad.net [69.3.5.197])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h663QcF30384;
	Sat, 5 Jul 2003 20:26:38 -0700
Message-Id: <5.2.0.9.2.20030705231617.01b89320@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sat, 05 Jul 2003 23:19:33 -0400
To: Ulrich Kiermayr <ulrich.kiermayr@univie.ac.at>,
        Richard Perlman <perl@lucent.com>
From: Richard Shockey <richard@shockey.us>
Subject: Re: First Timers
Cc: ietf@ietf.org
In-Reply-To: <3F0718E0.4020906@univie.ac.at>
References: <BB2C4889.13ED6%perl@lucent.com>
 <BB2C4889.13ED6%perl@lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

A
>>Depending on
>>where you want to eat dinner, you might need a jacket - but of course, your
>>choice of restaurants is strictly up to you.
>
>I live here - I go out regularly - i never was required to wear a 
>jacket  to diner. But maybe there are places here I still do not know ....


what about the Vienna Rathaus? after all it is a spactular venue.. I was 
thinking of pulling out the suit and bowtie or that one if for no reason 
other than to honor our gracious hosts..



>l


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
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  Sun Jul  6 04:33: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 EAA09013
	for <ietf-web-archive@odin.ietf.org>; Sun, 6 Jul 2003 04:33:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Z4ke-0003ZF-Bt
	for ietf-list@asgard.ietf.org; Sun, 06 Jul 2003 04:20:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Z4ji-0003Y1-8p
	for ietf@asgard.ietf.org; Sun, 06 Jul 2003 04:19:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08877
	for <ietf@ietf.org>; Sun, 6 Jul 2003 04:19:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Z4jf-0000gX-00
	for ietf@ietf.org; Sun, 06 Jul 2003 04:19:03 -0400
Received: from sdf-eu.org ([192.94.73.35] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Z4jf-0000gU-00
	for ietf@ietf.org; Sun, 06 Jul 2003 04:19:03 -0400
Received: from sdf-eu.org (IDENT:pfortuny@localhost [127.0.0.1] (may be forged))
	by sdf-eu.org (8.12.8/8.11.6) with ESMTP id h668Im7C004847
	for <ietf@ietf.org>; Sun, 6 Jul 2003 08:18:48 GMT
Received: (from pfortuny@localhost)
	by sdf-eu.org (8.12.8/8.12.8/Submit) id h668ImH7004846
	for ietf@ietf.org; Sun, 6 Jul 2003 08:18:48 GMT
Date: Sun, 6 Jul 2003 08:18:48 +0000
From: Pedro Fortuny <pfortuny@sdf-eu.org>
To: IETF <ietf@ietf.org>
Subject: basic refs
Message-ID: <20030706081848.GA4575@SDF-EU.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by sdf-eu.org id h668Im7C004847
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Getting started with the IPv6 protocol (and new to this list :)
Any basic references (no need to be exhaustive at all) (I mean, six
or seven rfc's would be more than ok).

Thx.
--=20
Pedro Fortuny Ayuso ---------------------->      pfortuny.sdf-eu.org
Colegio Mayor Pe=F1afiel, Universidad de Valladolid
C/ Estudios 6, 47005 Valladolid, Spain -->        www.cmpenafiel.org
pfortuny@sdf-eu.org                         Tfn. Nr. 34  983  298277



From owner-ietf@ietf.org  Sun Jul  6 04:45: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 EAA09364
	for <ietf-web-archive@odin.ietf.org>; Sun, 6 Jul 2003 04:45:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Z55y-0006IB-IH
	for ietf-list@asgard.ietf.org; Sun, 06 Jul 2003 04:42:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Z55L-0006Gw-1N
	for ietf@asgard.ietf.org; Sun, 06 Jul 2003 04:41:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09207
	for <ietf@ietf.org>; Sun, 6 Jul 2003 04:41:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Z55I-0000nB-00
	for ietf@ietf.org; Sun, 06 Jul 2003 04:41:24 -0400
Received: from web80606.mail.yahoo.com ([66.218.79.95])
	by ietf-mx with smtp (Exim 4.12)
	id 19Z55H-0000n1-00
	for ietf@ietf.org; Sun, 06 Jul 2003 04:41:24 -0400
Message-ID: <20030706084055.35137.qmail@web80606.mail.yahoo.com>
Received: from [64.110.82.211] by web80606.mail.yahoo.com via HTTP; Sun, 06 Jul 2003 01:40:55 PDT
Date: Sun, 6 Jul 2003 01:40:55 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: The Future of Quantum Cryptography
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1358207993-1057480855=:30827"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-1358207993-1057480855=:30827
Content-Type: text/plain; charset=us-ascii

P(t) - photons transmitted
P(l) - photons lost ( by absorption in space or by transparency / inefficiency of optical fibre )
P(r) - photons received
 
The future of secure quantum cryptography is dependent upon the following :
 
Condition ( a) : Development of a super efficient optical fibre such that P(t) = P(r) whereby if P(t)>P(r)  or P(t)<P(r) the system automatically shuts down.
Problem - material sciences and detector efficiency are still not up to that standard.
 
Condition (b) : Development of a super efficient optical fibre such that P(l) in any surface area of the fibre accessible  to the hacker do not comprise a statistically complete quantum key or quantum message.
Problem - as in (a) but is  easier to achieve than Condition (a).
 
Condition (c) : For satellite routed quantum messages, before routing a message from a transmitter to a receiver - a very high resolution intelligent space-based synthetic aperture radar coupled with scanning of SAR imagery by supercomputers would be used to locate a receiver antennae ( i.e. resolution of SAR approx. 1cm ).  A transponder would be used to probe and identify the laser receiver antennae of mobile unit.  This would allow the satellites to route the laser beam / quantum key directly to the laser antennae thereby eliminating P(l) to the background - e.g enemies in a battle-space.
Problem - a directed beam would be good for civilian networks and surface naval vessels, but a disadvantage to submarines as they could be located by enemies.  This would minimize the usage of this technology in submarines to quantum key reception mode only before reverting to broad undirected beam reception mode.
Problem - this mode of prioritized satcoms would be too expensive.
 
Optionally : Ships / vehicles and submarines i.e. would have a Galileo tracking on their laser antennae.
Problem - enemies could abuse tracking signals from antennae.
 
Field units could also originate quantum keys!
 
Nyagudi Musandu
tel.: 254-722-484730 ( CAUTION : this line is not secure )


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

<DIV>P(t) - photons transmitted</DIV>
<DIV>P(l) - photons lost ( by absorption in space or by transparency / inefficiency of optical fibre )</DIV>
<DIV>P(r) - photons received</DIV>
<DIV>&nbsp;</DIV>
<DIV>The future of secure quantum cryptography is dependent upon the following :</DIV>
<DIV>&nbsp;</DIV>
<DIV>Condition ( a) : Development of a super efficient optical fibre such that P(t) = P(r) whereby if P(t)&gt;P(r)&nbsp; or P(t)&lt;P(r) the system automatically shuts down.</DIV>
<DIV>Problem - material sciences and detector efficiency are still not up to that standard.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Condition (b) : Development of a super efficient optical fibre such that P(l) in any surface area of the fibre accessible&nbsp; to the hacker do not comprise a statistically complete quantum key or quantum message.</DIV>
<DIV>Problem - as in (a) but is&nbsp; easier to achieve than Condition (a).</DIV>
<DIV>&nbsp;</DIV>
<DIV>Condition (c) : For satellite routed quantum messages, before routing a message from a transmitter to a receiver - a very high resolution intelligent space-based synthetic aperture radar coupled with scanning of SAR imagery by supercomputers would be used to locate a receiver antennae ( i.e. resolution of SAR approx. 1cm ).&nbsp; A transponder would be used to probe and identify the laser receiver antennae of mobile unit.&nbsp; This would allow the satellites to route the laser beam / quantum key directly to the laser antennae thereby eliminating P(l) to the background - e.g enemies in a battle-space.</DIV>
<DIV>Problem - a directed beam would be good for civilian networks and surface naval vessels, but a disadvantage to submarines as they could be located by enemies.&nbsp; This would minimize the usage of this technology in submarines to quantum key reception mode only before reverting to broad undirected beam reception mode.</DIV>
<DIV>Problem - this mode of prioritized satcoms would be too expensive.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Optionally : Ships / vehicles and submarines i.e. would have a Galileo tracking on their laser antennae.</DIV>
<DIV>Problem - enemies could abuse tracking signals from antennae.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Field units could also originate quantum keys!</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi Musandu</DIV>
<DIV>tel.: 254-722-484730 ( CAUTION : this line is not secure )</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-1358207993-1057480855=:30827--



From owner-ietf@ietf.org  Sun Jul  6 11:50: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 LAA15995
	for <ietf-web-archive@odin.ietf.org>; Sun, 6 Jul 2003 11:50:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ZBbY-0005lK-E3
	for ietf-list@asgard.ietf.org; Sun, 06 Jul 2003 11:39:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ZBaf-0005jo-3D
	for ietf@asgard.ietf.org; Sun, 06 Jul 2003 11:38: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 LAA15819
	for <ietf@ietf.org>; Sun, 6 Jul 2003 11:38:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZBae-000399-00
	for ietf@ietf.org; Sun, 06 Jul 2003 11:38:12 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZBad-000396-00
	for ietf@ietf.org; Sun, 06 Jul 2003 11:38:11 -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 h66FcpxS092629;
	Sun, 6 Jul 2003 17:38:51 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Sun, 6 Jul 2003 17:38:01 +0200
Subject: Re: basic refs
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: IETF <ietf@ietf.org>
To: Pedro Fortuny <pfortuny@sdf-eu.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <20030706081848.GA4575@SDF-EU.ORG>
Message-Id: <D3A03D84-AFC7-11D7-8009-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On zondag, jul 6, 2003, at 10:18 Europe/Amsterdam, Pedro Fortuny wrote:

> Getting started with the IPv6 protocol (and new to this list :)
> Any basic references (no need to be exhaustive at all) (I mean, six
> or seven rfc's would be more than ok).

A good start would be:

Internet Protocol, Version 6 (IPv6) Specification  (RFC 2460) (85890 
bytes)
IP Version 6 Addressing Architecture  (RFC 3513) (53920 bytes)
An IPv6 Aggregatable Global Unicast Address Format  (RFC 2374) (25068 
bytes)
IPv6 Stateless Address Autoconfiguration  (RFC 2462) (61210 bytes)
Transmission of IPv6 Packets over Ethernet Networks  (RFC 2464) (12725 
bytes)
Neighbor Discovery for IP Version 6 (IPv6)  (RFC 2461) (222516 bytes)

You should also read:

http://ispcolumn.isoc.org/2003-01/Waiting.html
http://ispcolumn.isoc.org/2003-01/WaitingResp.html

Note that due to the fact that IPv6 has been in development for a very 
long time, you're likely to find a lot of obsolete information when 
searching for IPv6 info on the web. Be suspect of anything that isn't 
from this century and any discussion of pTLAs/sTLAs, A6 or 24 bit flow 
label fields and to a lesser degree site local addresses. Also, IPv6 
implementations tend to be fairly basic. Don't expect to see much IPv6 
over PPP or DHCPv6, for instance.




From owner-ietf@ietf.org  Sun Jul  6 13:54: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 NAA18434
	for <ietf-web-archive@odin.ietf.org>; Sun, 6 Jul 2003 13:54:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ZDbL-0000kC-6t
	for ietf-list@asgard.ietf.org; Sun, 06 Jul 2003 13:47:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ZDak-0000id-K5
	for ietf@asgard.ietf.org; Sun, 06 Jul 2003 13:46: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 NAA18124
	for <ietf@ietf.org>; Sun, 6 Jul 2003 13:46:23 -0400 (EDT)
From: john.loughney@kolumbus.fi
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZDaj-0003oP-00
	for ietf@ietf.org; Sun, 06 Jul 2003 13:46:25 -0400
Received: from cust-smtp1.radiolinja.fi ([213.161.33.208])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZDai-0003oA-00
	for ietf@ietf.org; Sun, 06 Jul 2003 13:46:24 -0400
Received: from [10.64.0.28] (rl045006.radiolinja.net [213.161.45.6])
	by cust-smtp1.radiolinja.fi (Postfix) with ESMTP
	id 1A06040006; Sun,  6 Jul 2003 20:46:15 +0300 (EEST)
Reply-To: john.loughney@kolumbus.fi
To: "Pedro Fortuny" <pfortuny@sdf-eu.org>
Cc: "IETF" <ietf@ietf.org>
Subject: RE: basic refs
Date: Sun,  6 Jul 2003 20:46:10 +0300
Message-ID: <tQWSb6F5K84c.QPZgQrXg@smtp.mobiili.net>
X-Mailer: Symbian OS Email Version 7.0
MIME-Version: 1.0
Content-Language: i-default
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hi,

> Getting started with the IPv6 protocol (and new to this list :)
> Any basic references (no need to be exhaustive at all) (I mean, six
> or seven rfc's would be more than ok).

Try =
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-node-requirements-04.txt=


br,
John




From owner-ietf@ietf.org  Sun Jul  6 18:55: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 SAA25050
	for <ietf-web-archive@odin.ietf.org>; Sun, 6 Jul 2003 18:55:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ZIFi-0006dZ-AA
	for ietf-list@asgard.ietf.org; Sun, 06 Jul 2003 18:45:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ZIF0-0006aZ-0y
	for ietf@asgard.ietf.org; Sun, 06 Jul 2003 18:44:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24952
	for <ietf@ietf.org>; Sun, 6 Jul 2003 18:44:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZIEy-00054T-00
	for ietf@ietf.org; Sun, 06 Jul 2003 18:44:16 -0400
Received: from smtp101.mail.sc5.yahoo.com ([216.136.174.139])
	by ietf-mx with smtp (Exim 4.12)
	id 19ZIEx-00054Q-00
	for ietf@ietf.org; Sun, 06 Jul 2003 18:44:15 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 6 Jul 2003 22:44:14 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'shogunx'" <shogunx@sleekfreak.ath.cx>
Cc: <ietf@ietf.org>
Subject: RE: First Timers
Date: Mon, 7 Jul 2003 00:44:10 +0200
Organization: Internet Society
Message-ID: <01ab01c34410$1edf1dd0$3e00a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 5 (Lowest)
X-MSMail-Priority: Low
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <Pine.LNX.4.44.0307050146420.21010-100000@sleekfreak.ath.cx>
Importance: Low
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

Hey, ShogunX, is that part of your anatomy on
http://sleekfreak.ath.cx:81/images/data.jpg?
:))

=>-----Original Message-----
=>From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On 
=>Behalf Of shogunx
=>
(...)
=>
=>sleekfreak pirate broadcast
=>world tour 2002-3
=>live from the pirate hideout
=>http://sleekfreak.ath.cx:81





From owner-ietf@ietf.org  Sun Jul  6 20:30: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 UAA26549
	for <ietf-web-archive@odin.ietf.org>; Sun, 6 Jul 2003 20:30:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ZJif-00017p-T0
	for ietf-list@asgard.ietf.org; Sun, 06 Jul 2003 20:19:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ZJiR-000165-Ip
	for ietf@asgard.ietf.org; Sun, 06 Jul 2003 20:18: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 UAA26436
	for <ietf@ietf.org>; Sun, 6 Jul 2003 20:18:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZJiP-0005ks-00
	for ietf@ietf.org; Sun, 06 Jul 2003 20:18:45 -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 19ZJiP-0005ko-00
	for ietf@ietf.org; Sun, 06 Jul 2003 20:18:45 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19YzhF-00069H-00; Sat, 05 Jul 2003 22:56:13 -0400
Date: Sat, 5 Jul 2003 22:56:12 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr>
cc: ietf@ietf.org
Subject: RE: First Timers
In-Reply-To: <01ab01c34410$1edf1dd0$3e00a8c0@tomson.be>
Message-ID: <Pine.LNX.4.44.0307052247450.22086-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Ahh.  Almost like radio free europe.  My apologies to all associated for
both my being unable to attend this IETF, and for the unfortunate display
of my social commentary on current commercial operating systems to the
entire IETF.  the link in question reads:  "NEW section for Windows users.
Click here!"  posted in response to repeated requests to port my software
applications to proprietary operating systems.

I look forward to seeing everyone in Minneapolis.

Scott


On Mon, 7 Jul 2003, Tomson Eric (Yahoo.fr) wrote:

> Hey, ShogunX, is that part of your anatomy on
> http://sleekfreak.ath.cx:81/images/data.jpg?
> :))
>
> =>-----Original Message-----
> =>From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On
> =>Behalf Of shogunx
> =>
> (...)
> =>
> =>sleekfreak pirate broadcast
> =>world tour 2002-3
> =>live from the pirate hideout
> =>http://sleekfreak.ath.cx:81
>
>
>
>

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




From owner-ietf@ietf.org  Mon Jul  7 00:10: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 AAA29448
	for <ietf-web-archive@odin.ietf.org>; Mon, 7 Jul 2003 00:10:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ZNBW-0002JC-60
	for ietf-list@asgard.ietf.org; Mon, 07 Jul 2003 00:01:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ZN9J-0002FG-KR
	for ietf@asgard.ietf.org; Sun, 06 Jul 2003 23:58: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 XAA29241
	for <ietf@ietf.org>; Sun, 6 Jul 2003 23:58:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZN9H-00079g-00
	for ietf@ietf.org; Sun, 06 Jul 2003 23:58:43 -0400
Received: from [203.199.93.15] (helo=WS0005.indiatimes.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZN9G-000797-00
	for ietf@ietf.org; Sun, 06 Jul 2003 23:58:42 -0400
Received: from 192.168.57.15 (a2 [192.168.57.22])
	by WS0005.indiatimes.com (8.9.3/8.9.3) with SMTP id JAA04135;
	Mon, 7 Jul 2003 09:26:58 +0530
From: "Rohit Gupta" <rohitgupta416@indiatimes.com>
Message-Id: <200307070356.JAA04135@WS0005.indiatimes.com>
To: <dominic.pinto@ieee.org>, "Ole Jacobsen"<ole@cisco.com>
CC: "Rohit Gupta"<rohitgupta416@indiatimes.com>, <ietf@ietf.org>
Reply-To: "Rohit Gupta"<rohitgupta416@indiatimes.com>
Subject: Re: Re: First Timers
Date: Mon, 07 Jul 2003 09:21:26 +0530
X-URL: http://indiatimes.com
Content-Type: multipart/alternative;
	   boundary="=_MAILER_ATTACH_BOUNDARY1_2003771921261102520059"
MIME-Version: 1.0
Sender: owner-ietf@ietf.org
Precedence: bulk

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

:-)


Thanks a lot to everyone for all the help !!! 

dominic.pinto@ieee.org wrote:




&gt; On Sat, 5 Jul 2003, Rohit Gupta wrote:
&gt; 
&gt; &gt; Hi,
&gt; &gt;
&gt; &gt;
&gt; &gt; We will be attending the 57th IETF meeting to be held in Vienna and this
&gt; &gt; will be ours first IETF Meeting. Is there any dress code which is
&gt; &gt; followed out there?
&gt; &gt;
&gt; &gt;
&gt; &gt; I went though the Tao of IETF from the ietf.org site and just was
&gt; &gt; interested in others experiences.
&gt; &gt;


Hey, what's with this 'out there', X-Files, or maybe US-centric, stuff?


Get Your Private, Free E-mail from Indiatimes at  http://email.indiatimes.com
Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com
Bid for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now !

--=_MAILER_ATTACH_BOUNDARY1_2003771921261102520059
Content-Type: text/html; charset=us-ascii

<P>:-)</P>
<P>Thanks a lot to everyone for all the help !!! <BR><BR><B><I>dominic.pinto@ieee.org</B></I> wrote:<BR><BR></P>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid"><BR><BR>&gt; On Sat, 5 Jul 2003, Rohit Gupta wrote:<BR>&gt; <BR>&gt; &gt; Hi,<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; We will be attending the 57th IETF meeting to be held in Vienna and this<BR>&gt; &gt; will be ours first IETF Meeting. Is there any dress code which is<BR>&gt; &gt; followed out there?<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; I went though the Tao of IETF from the ietf.org site and just was<BR>&gt; &gt; interested in others experiences.<BR>&gt; &gt;<BR><BR><BR>Hey, what's with this 'out there', X-Files, or maybe US-centric, stuff?<BR></BLOCKQUOTE><BR>
<hr><font face="Arial" size="2"><b>Get Your Private, Free E-mail from Indiatimes at  </font><a href="http://email.indiatimes.com"><font face="Arial" size="2">http://email.indiatimes.com</a></b><br>Buy The Best In <b>BOOKS</b> at <A href="http://www.bestsellers.indiatimes.com">http://www.bestsellers.indiatimes.com</A><br>Bid for <b>Air Tickets @ Re.1</b> on Air Sahara Flights. Just log on to <a href="http://airsahara.indiatimes.com">http://airsahara.indiatimes.com</a> and Bid Now !</font>

--=_MAILER_ATTACH_BOUNDARY1_2003771921261102520059--




From owner-ietf@ietf.org  Mon Jul  7 09:38: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 JAA24377
	for <ietf-web-archive@odin.ietf.org>; Mon, 7 Jul 2003 09:38:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ZVyG-0005Fy-Ob
	for ietf-list@asgard.ietf.org; Mon, 07 Jul 2003 09:23:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ZVxT-0005F5-8G
	for ietf@asgard.ietf.org; Mon, 07 Jul 2003 09:23:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24143
	for <ietf@ietf.org>; Mon, 7 Jul 2003 09:23:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZVxS-00047u-00
	for ietf@ietf.org; Mon, 07 Jul 2003 09:23:06 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19ZVxR-00047d-00
	for ietf@ietf.org; Mon, 07 Jul 2003 09:23:05 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003070709313426523
 for <ietf@ietf.org>; Mon, 07 Jul 2003 09:31:34 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 7 Jul 2003 09:20:04 -0400
Message-ID: <3F097384.5060201@centive.com>
Date: Mon, 07 Jul 2003 09:20:04 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: First Timers
References: <BB2C4889.13ED6%perl@lucent.com>
In-Reply-To: <BB2C4889.13ED6%perl@lucent.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Jul 2003 13:20:04.0314 (UTC) FILETIME=[7A3783A0:01C3448A]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Richard Perlman wrote:

>On 7/5/03 3:08 AM, "Ole J. Jacobsen" <ole@cisco.com> wrote:
>  
>
>>"Casual and comfortable" is a phrase that describes us well. We favor the
>>practical over the formal.
>>
>Don't believe a word Ole says.  I have seen him at many of his 50 IETF
>meetings and most of the time his T-Shirt has been recently washed.
>
Ah, but wearing clean clothes at IETF is practical; it's so inconvenient 
when somebody walks by, gets a whiff, passes out, and trips over your 
power cord.

-- 
/==========================================\
|John Stracke      |jstracke@centive.com   |
|Principal Engineer|http://www.centive.com |
|Centive           |My opinions are my own.|
|==========================================|
|"Who died and made you king?" "My father."|
\==========================================/





From owner-ietf@ietf.org  Mon Jul  7 10:35: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 KAA27746
	for <ietf-web-archive@odin.ietf.org>; Mon, 7 Jul 2003 10:35:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ZWwI-00055L-K3
	for ietf-list@asgard.ietf.org; Mon, 07 Jul 2003 10:25:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ZWvL-00054E-9m
	for ietf@asgard.ietf.org; Mon, 07 Jul 2003 10:24: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 KAA27236
	for <ietf@ietf.org>; Mon, 7 Jul 2003 10:24:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZWvJ-0004kp-00
	for ietf@ietf.org; Mon, 07 Jul 2003 10:24:57 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZWvI-0004kW-00
	for ietf@ietf.org; Mon, 07 Jul 2003 10:24:56 -0400
Received: from BBFUJIP.brandenburg.com (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h67ER8F08408;
	Mon, 7 Jul 2003 07:27:10 -0700
Date: Sun, 6 Jul 2003 22:58:06 +0200
From: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: The Bat! (v1.63 Beta/11) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <15951714882.20030706225806@brandenburg.com>
To: Scott W Brim <swb@employees.org>
CC: ietf@ietf.org
Subject: Re: The requirements cycle (Re: WG review: Layer 2 Virtual....)
In-Reply-To: <20030705194512.D1840@sbrim-w2k01>
References: <200307031652.h63Gqmfq009031@rtp-core-1.cisco.com>
 <351620000.1057264376@askvoll.hjemme.alvestrand.no>
 <1451723728.20030705175341@brandenburg.com> <20030705194512.D1840@sbrim-w2k01>
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

Scott,

SWB> This is wayyy too abstract and theoretical.  

Unfortunately, it was intentional.

I was sufficiently surprised that anyone would blame the working group
for failing to overcome inappropriate barriers, imposed by management
that I fell into academic mode, to try to moderate the reaction.

So, try just the end of my note:

>> Blame the folks doing the imposing.
>> 
>> Or, to state this more constructively, do not focus on the people who
>> become discouraged by external forces that are... discouraging.
>> 
>> Focus in getting those forces turned into something constructive.


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




From owner-ietf@ietf.org  Mon Jul  7 12:46: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 MAA02914
	for <ietf-web-archive@odin.ietf.org>; Mon, 7 Jul 2003 12:46:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ZYw7-00005H-CK
	for ietf-list@asgard.ietf.org; Mon, 07 Jul 2003 12:33:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ZYw1-0008Vr-R9
	for ietf@asgard.ietf.org; Mon, 07 Jul 2003 12:33: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 MAA02313
	for <ietf@ietf.org>; Mon, 7 Jul 2003 12:33:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y5HY-0007Lf-00
	for ietf@ietf.org; Thu, 03 Jul 2003 10:41:56 -0400
Received: from [62.145.94.16] (helo=mail.uruklink.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Y5Fw-0007KO-00
	for ietf@ietf.org; Thu, 03 Jul 2003 10:41:55 -0400
Received: from arshad [10.1.10.151] by mail.uruklink.net with ESMTP
  (SMTPD32-7.07) id A09169011E; Thu, 03 Jul 2003 18:41:21 +0400
Message-ID: <007001c34171$08598420$970a010a@arshad>
From: "massaly" <massaly@uruklink.net>
To: <ietf@ietf.org>
Date: Thu, 3 Jul 2003 18:38:22 +0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000B_01C34192.47F3DA60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2479.0001
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0001
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_000B_01C34192.47F3DA60
Content-Type: text/plain;
	charset="windows-1256"
Content-Transfer-Encoding: quoted-printable



------=_NextPart_000_000B_01C34192.47F3DA60
Content-Type: text/html;
	charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1256">
<META content=3D"MSHTML 6.00.2479.1" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_000B_01C34192.47F3DA60--




From owner-ietf@ietf.org  Mon Jul  7 15:39: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 PAA10990
	for <ietf-web-archive@odin.ietf.org>; Mon, 7 Jul 2003 15:39:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ZbiL-0006bL-Vc
	for ietf-list@asgard.ietf.org; Mon, 07 Jul 2003 15:31:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Zbhj-0006aL-HF
	for ietf@asgard.ietf.org; Mon, 07 Jul 2003 15:31: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 PAA10675
	for <ietf@ietf.org>; Mon, 7 Jul 2003 15:31:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Zbhi-0001TS-00
	for ietf@ietf.org; Mon, 07 Jul 2003 15:31:14 -0400
Received: from iserver.sj.symbol.com ([63.145.233.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Zbhh-0001TK-00
	for ietf@ietf.org; Mon, 07 Jul 2003 15:31:13 -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 h67JRJwQ028279
	for <ietf@ietf.org>; Mon, 7 Jul 2003 12:27:19 -0700 (PDT)
Received: from SJ-DOM-MTA by gwianameserver.sj.symbol.com
	with Novell_GroupWise; Mon, 07 Jul 2003 12:31:06 -0700
Message-Id: <sf09680a.036@gwianameserver.sj.symbol.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2
Date: Mon, 07 Jul 2003 12:31:00 -0700
From: "Clint Chaplin" <cchaplin@sj.symbol.com>
To: <ole@cisco.com>
Cc: <ietf@ietf.org>
Subject: Re: First Timers
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

If this is your 50th IETF, I find it difficult to believe that you
haven't seen Bob Moskowitz more than five times....

Clint (JOATMON) Chaplin

>>> "Ole J. Jacobsen" <ole@cisco.com> 7/5/03 03:08:33 >>>
Rohit,

The IETF prides itself on formality. You should be prepared to wear
only
the finest and most conservative business suits. For social events
such
as the opening reception, we generally expect to greet each other in
tuxedos.

See for example https://www.execstyle.com/fashion.asp 

OK, I'm kidding!

This will be my 50th IETF, and I can count on one hand the number of
people times the number of events where I have actually seen a suit.

"Casual and comfortable" is a phrase that describes us well. We favor
the
practical over the formal. Don't be surprised to see people sitting on
the floor or hanging out the side of a building if such a location
improves 802.11 reception.

Welcome to the club!

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj 


On Sat, 5 Jul 2003, Rohit Gupta wrote:

> Hi,
>
>
> We will be attending the 57th IETF meeting to be held in Vienna and
this
> will be ours first IETF Meeting. Is there any dress code which is
> followed out there?
>
>
> I went though the Tao of IETF from the ietf.org site and just was
> interested in others experiences.
>
>
> Rohit
>
>

>



________________________________________________________________________
This email has been scanned for computer viruses.



From owner-ietf@ietf.org  Mon Jul  7 16:28: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 QAA13589
	for <ietf-web-archive@odin.ietf.org>; Mon, 7 Jul 2003 16:28:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ZcVh-0000zP-Fl
	for ietf-list@asgard.ietf.org; Mon, 07 Jul 2003 16:22:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ZcTB-0000lS-PO
	for ietf@asgard.ietf.org; Mon, 07 Jul 2003 16:20: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 QAA13142
	for <ietf@ietf.org>; Mon, 7 Jul 2003 16:20:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZcTA-0002Af-00
	for ietf@ietf.org; Mon, 07 Jul 2003 16:20:16 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZcT9-00029l-00
	for ietf@ietf.org; Mon, 07 Jul 2003 16:20:15 -0400
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h67KJZfq026689;
	Mon, 7 Jul 2003 16:19:35 -0400 (EDT)
Message-Id: <200307072019.h67KJZfq026689@rtp-core-1.cisco.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: The requirements cycle 
In-reply-to: Your message of Thu, 03 Jul 2003 22:32:56 +0200.
             <351620000.1057264376@askvoll.hjemme.alvestrand.no> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 07 Jul 2003 16:19:35 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


Eric> Not sure  what you mean, it  always takes time to  produce a document,
Eric> even if the document is just a "rock fetch".

Harald> sorry; "rock fetch" is beyond my scope of American idiom. 

"Rock  fetch":   when  the "boss"  sends  the  workers  out on  useless  but
time-consuming tasks.  

Harald> But version  -01 of the framework  document is dated  July 19, 2001,
Harald> and the  first version submitted to  the IESG is  dated February 15,
Harald> 2002. 

About six months to get the WG  to agree on the framework, that doesn't seem
excessive for a document.  It's a rock fetch though because there is no real
need for a framework document. 

Harald> I took that as a hint  that there might have been controversy in the
Harald> working group about it. 

It  was  never a  very  controversial  document.   My recollection  is  that
framework and requirements were ready about  January of 2002, which is why I
said that they were ready about  18 months ago.  So were the protocol specs,
applicability statements, etc.

Eric> Well,  each  objection from  the  IESG needs  to  be  discussed and  a
Eric> response crafted. 

Harald> which should take approximately 3 days of work, IMHO.  Comments that
Harald> translate  to "you  are  referencing an  obsolete  version of  LDAP"
Harald> should take approximately 2 minutes to fix. 

Comments which were  received last fall (I first saw them  a few weeks prior
to  the Atlanta  IETF  meeting)  required a  considerable  reworking of  the
document.  (Sisyphus comes to mind here ;-))

Harald> Did the  WG declare consensus on  all those documents  18 months ago
Harald> (January 2002)? 

The WG  was told by the  WG chairs that the  IESG would not allow  the WG to
even consider  the solutions documents until the  framework and requirements
documents  were approved  by the  IESG.  Something  is very  wrong  with the
process here.

The L3VPN  protocol specs  themselves haven't changed  in years, which  is a
good thing, given  the large amount of interoperable  deployment by multiple
vendors!










From owner-ietf@ietf.org  Mon Jul  7 17:58: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 RAA17986
	for <ietf-web-archive@odin.ietf.org>; Mon, 7 Jul 2003 17:58:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Zdqv-0003vZ-CA
	for ietf-list@asgard.ietf.org; Mon, 07 Jul 2003 17:48:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ZdqM-0003uF-Ob
	for ietf@asgard.ietf.org; Mon, 07 Jul 2003 17:48:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17545
	for <ietf@ietf.org>; Mon, 7 Jul 2003 17:48:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZdqL-0003NH-00
	for ietf@ietf.org; Mon, 07 Jul 2003 17:48:17 -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 19ZdqK-0003N0-00
	for ietf@ietf.org; Mon, 07 Jul 2003 17:48:16 -0400
Received: from cisco.com (171.68.223.137)
  by sj-iport-2.cisco.com with ESMTP; 07 Jul 2003 14:45:22 -0700
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h67LlipZ023864;
	Mon, 7 Jul 2003 14:47:44 -0700 (PDT)
Received: (ole@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) id OAA12365; Mon, 7 Jul 2003 14:47:44 -0700 (PDT)
X-Authentication-Warning: wells.cisco.com: ole set sender to ole@cisco.com using -f
Date: Mon, 7 Jul 2003 14:47:44 -0700 (PDT)
From: "Ole J. Jacobsen" <ole@cisco.com>
Reply-To: Ole Jacobsen <ole@cisco.com>
To: Clint Chaplin <cchaplin@sj.symbol.com>
cc: ietf@ietf.org
Subject: Re: First Timers
In-Reply-To: <sf09680a.035@gwianameserver.sj.symbol.com>
Message-ID: <Pine.HPX.4.44.0307071447300.6595-100000@wells.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Bob Is the exception that proves the rule.

ole



Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj







From owner-ietf@ietf.org  Mon Jul  7 18:44:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20266
	for <ietf-web-archive@odin.ietf.org>; Mon, 7 Jul 2003 18:44:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ZedI-0003Zv-Pm
	for ietf-list@asgard.ietf.org; Mon, 07 Jul 2003 18:38:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ZecT-0003V9-E2
	for ietf@asgard.ietf.org; Mon, 07 Jul 2003 18:38: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 SAA20194
	for <ietf@ietf.org>; Mon, 7 Jul 2003 18:37:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZecR-0003mm-00
	for ietf@ietf.org; Mon, 07 Jul 2003 18:37:59 -0400
Received: from kaoru.nikojet.com ([64.157.40.90])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZecQ-0003mj-00
	for ietf@ietf.org; Mon, 07 Jul 2003 18:37:58 -0400
Received: from nikotel.com (c177222.adsl.hansenet.de [213.39.177.222])
	(authenticated (0 bits))
	by kaoru.nikojet.com (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id h67Mbne02551
	(using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO);
	Tue, 8 Jul 2003 00:37:56 +0200
Message-ID: <3F09F63D.4020000@nikotel.com>
Date: Tue, 08 Jul 2003 00:37:49 +0200
From: Michael Koehler <koehler@nikotel.com>
Organization: Econo / Nikotel / mac2phone
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tomson_Eric@Yahoo.fr
CC: "'shogunx'" <shogunx@sleekfreak.ath.cx>, ietf@ietf.org
Subject: Re: First Timers
References: <01ab01c34410$1edf1dd0$3e00a8c0@tomson.be>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

i read about that before: draft-001-jabberanal-proposal-001.txt

Tomson Eric (Yahoo.fr) wrote:

>Hey, ShogunX, is that part of your anatomy on
>http://sleekfreak.ath.cx:81/images/data.jpg?
>:))
>
>  
>





From owner-ietf@ietf.org  Mon Jul  7 19:51: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 TAA21783
	for <ietf-web-archive@odin.ietf.org>; Mon, 7 Jul 2003 19:51:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ZfdD-0005Qa-V5
	for ietf-list@asgard.ietf.org; Mon, 07 Jul 2003 19:42:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Zfcc-0005Q2-6u
	for ietf@asgard.ietf.org; Mon, 07 Jul 2003 19:42: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 TAA21662
	for <ietf@ietf.org>; Mon, 7 Jul 2003 19:42:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Zfca-0004Cj-00
	for ietf@ietf.org; Mon, 07 Jul 2003 19:42:12 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZfcZ-0004Cg-00
	for ietf@ietf.org; Mon, 07 Jul 2003 19:42:12 -0400
Received: from [147.28.0.62] (helo=127.0.0.1 ident=zinin)
	by psg.com with esmtp (Exim 4.14)
	id 19ZfcU-0001xt-2n; Mon, 07 Jul 2003 23:42:06 +0000
Date: Mon, 7 Jul 2003 16:41:30 -0700
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.62i) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <105670879814.20030707164130@psg.com>
To: Eric Rosen <erosen@cisco.com>
CC: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: The requirements cycle
In-Reply-To: <200307072019.h67KJZfq026689@rtp-core-1.cisco.com>
References: <200307072019.h67KJZfq026689@rtp-core-1.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric,

  Looking at this from the high-level perspective...

  Though I became the responsible AD for PPVPN just recently, I was
  exposed to certain aspects of interaction between ADs are PPVPN WG
  chairs. There was clearly a communication problem there. I believe
  it's been solved and we are in a much better shape now. Trying to
  investigate who said what and whose fault that was in the past will
  not be pretty, so I suggest we don't go there. One thing I can say
  for sure is that we (IESG) don't say things like "first you need to
  submit the first document, then a year or so later you can submit
  the second."

  Regarding requirements and framework documents being "rock fetching"
  in general:

  Again, I was not on the IESG when PPVPN was started, however, I
  think that naturally well-scoped technologies with a clear direction
  in the solution space very often do not need requirements and
  frameworks. If the problem space is reasonably big and/or there are
  multiple possible solutions that address seemingly identical
  problems, clearly documented requirements may help the IETF decide
  whether different solutions represent major approaches providing
  different coverage of the problem space (and hence satisfying
  requirements of different subsets of customers) and thus make sense
  to be progressed in parallel as independent technologies.
  Requirements may also help the SP decide which technology to deploy
  in their networks by checking how requirements important to them are
  addressed in each technology.

  A framework document seems to be a good idea when the technology is
  composed of multiple pieces that are not obviously related to each
  other and/or the relationship aspects among them are not clearly
  visible.

  It seems that the VPN problem and solution spaces are large and
  complex enough to warrant both requirements and framework documents.
  That said, these documents do not have to be long and fat, and it
  should be possible to produce an acceptable quality document within
  6 months.

  Regarding IESG feedback (where my piece was probably the biggest):
  Predicated on the assumption that reqs/fw documents are not needed,
  any feedback, whether it is from the IESG or not, will be perceived
  as a rock fetch. If we assume those are useful, IESG review is part
  of the process of ensuring high quality of these documents.

  Regards,
  
-- 
Alex
http://www.psg.com/~zinin/

Monday, July 7, 2003, 1:19:35 PM, Eric Rosen wrote:

Eric>> Not sure  what you mean, it  always takes time to  produce a document,
Eric>> even if the document is just a "rock fetch".

Harald>> sorry; "rock fetch" is beyond my scope of American idiom. 

> "Rock  fetch":   when  the "boss"  sends  the  workers  out on  useless  but
> time-consuming tasks.  

Harald>> But version  -01 of the framework  document is dated  July 19, 2001,
Harald>> and the  first version submitted to  the IESG is  dated February 15,
Harald>> 2002. 

> About six months to get the WG  to agree on the framework, that doesn't seem
> excessive for a document.  It's a rock fetch though because there is no real
> need for a framework document. 

Harald>> I took that as a hint  that there might have been controversy in the
Harald>> working group about it. 

> It  was  never a  very  controversial  document.   My recollection  is  that
> framework and requirements were ready about  January of 2002, which is why I
> said that they were ready about  18 months ago.  So were the protocol specs,
> applicability statements, etc.

Eric>> Well,  each  objection from  the  IESG needs  to  be  discussed and  a
Eric>> response crafted. 

Harald>> which should take approximately 3 days of work, IMHO.  Comments that
Harald>> translate  to "you  are  referencing an  obsolete  version of  LDAP"
Harald>> should take approximately 2 minutes to fix. 

> Comments which were  received last fall (I first saw them  a few weeks prior
> to  the Atlanta  IETF  meeting)  required a  considerable  reworking of  the
> document.  (Sisyphus comes to mind here ;-))

Harald>> Did the  WG declare consensus on  all those documents  18 months ago
Harald>> (January 2002)? 

> The WG  was told by the  WG chairs that the  IESG would not allow  the WG to
> even consider  the solutions documents until the  framework and requirements
> documents  were approved  by the  IESG.  Something  is very  wrong  with the
> process here.

> The L3VPN  protocol specs  themselves haven't changed  in years, which  is a
> good thing, given  the large amount of interoperable  deployment by multiple
> vendors!




From owner-ietf@ietf.org  Wed Jul  9 03:30: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 DAA22100
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Jul 2003 03:30:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19a949-0000B5-Va
	for ietf-list@asgard.ietf.org; Wed, 09 Jul 2003 03:08:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19a90O-00007J-Ul
	for ietf@asgard.ietf.org; Wed, 09 Jul 2003 03:04: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 DAA20851
	for <ietf@ietf.org>; Wed, 9 Jul 2003 03:04:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a90M-0004Cs-00
	for ietf@ietf.org; Wed, 09 Jul 2003 03:04:42 -0400
Received: from [158.38.152.233] (helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19a90M-0004Cm-00
	for ietf@ietf.org; Wed, 09 Jul 2003 03:04:42 -0400
Received: from [192.168.1.4] (nat.alvestrand.no [217.13.28.204])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 8598A61B97; Wed,  9 Jul 2003 09:04:12 +0200 (CEST)
Date: Wed, 09 Jul 2003 09:04:39 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: ietf@ietf.org
Subject: Re: The requirements cycle (Re: WG review: Layer 2 Virtual....)
Message-ID: <61570000.1057734279@askvoll.hjemme.alvestrand.no>
In-Reply-To: <15951714882.20030706225806@brandenburg.com>
References: <200307031652.h63Gqmfq009031@rtp-core-1.cisco.com>
 <351620000.1057264376@askvoll.hjemme.alvestrand.no>
 <1451723728.20030705175341@brandenburg.com>
 <20030705194512.D1840@sbrim-w2k01>
 <15951714882.20030706225806@brandenburg.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Dave,

I try to work from the theory that neither of the parties involved in this=20
conflict are technically incompetent or deliberately malicious.

Assigning "blame" to one party, and appearing to declare their actions to=20
have no possible rational explanation, is not compatible with this theory.

(Note that one party's actions being *wrong* when viewed in hindsight is=20
*not* incompatible with the theory!)

                           Harald

--On s=F8ndag, juli 06, 2003 22:58:06 +0200 Dave Crocker=20
<dcrocker@brandenburg.com> wrote:

> Scott,
>
> SWB> This is wayyy too abstract and theoretical.
>
> Unfortunately, it was intentional.
>
> I was sufficiently surprised that anyone would blame the working group
> for failing to overcome inappropriate barriers, imposed by management
> that I fell into academic mode, to try to moderate the reaction.
>
> So, try just the end of my note:
>
>>> Blame the folks doing the imposing.
>>>
>>> Or, to state this more constructively, do not focus on the people who
>>> become discouraged by external forces that are... discouraging.
>>>
>>> Focus in getting those forces turned into something constructive.
>
>
> d/
> --
>  Dave Crocker <mailto:dcrocker@brandenburg.com>
>  Brandenburg InternetWorking <http://www.brandenburg.com>
>  Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>
>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which
> is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on
> what to pass are made solely by Raffaele D'Albenzio.
>





From owner-ietf@ietf.org  Wed Jul  9 03:58: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 DAA22922
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Jul 2003 03:58:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19a9kj-0001r5-PX
	for ietf-list@asgard.ietf.org; Wed, 09 Jul 2003 03:52:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19a9iW-0001kP-La
	for ietf@asgard.ietf.org; Wed, 09 Jul 2003 03:50: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 DAA22633
	for <ietf@ietf.org>; Wed, 9 Jul 2003 03:50:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a9iU-0004kh-00
	for ietf@ietf.org; Wed, 09 Jul 2003 03:50:18 -0400
Received: from web80601.mail.yahoo.com ([66.218.79.90])
	by ietf-mx with smtp (Exim 4.12)
	id 19a9iT-0004ke-00
	for ietf@ietf.org; Wed, 09 Jul 2003 03:50:17 -0400
Message-ID: <20030709074948.99032.qmail@web80601.mail.yahoo.com>
Received: from [213.147.69.76] by web80601.mail.yahoo.com via HTTP; Wed, 09 Jul 2003 00:49:48 PDT
Date: Wed, 9 Jul 2003 00:49:48 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Address Allocation via Symmetric Amplification of Light
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-340828380-1057736988=:97421"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-340828380-1057736988=:97421
Content-Type: text/plain; charset=us-ascii

P(t) - photons transmitted
P(r) - photons received
 
Symmetric Amplification of Light : P(t)<P(r) whereby polarity of each and every photon received is equivalent to the polarity of the photon it has been amplified from - while maintaining wavelength and frequency characteristics of the photon transmitted ( the photon it has been amplified from ).
 
The importance of such a system is to sustain results obtained from quantum computing or routing from filters in a system in optical format, allowing for their redirecting to different system memory addresses ( to be received after filteration / confirmation by a photocell ).
 
Nyagudi Musandu
tel.: 254-722-484730


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

<DIV>P(t) - photons transmitted</DIV>
<DIV>P(r) - photons received</DIV>
<DIV>&nbsp;</DIV>
<DIV>Symmetric Amplification of Light : P(t)&lt;P(r) whereby polarity of each and every photon received is equivalent to the polarity of the photon it has been amplified from - while maintaining wavelength and frequency characteristics of the photon transmitted ( the photon it has been amplified from ).</DIV>
<DIV>&nbsp;</DIV>
<DIV>The importance of such a system is to sustain results obtained from quantum computing or routing from filters in a system in optical format, allowing for their redirecting to different system memory addresses ( to be received after filteration / confirmation by a photocell ).</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi Musandu</DIV>
<DIV>tel.: 254-722-484730</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-340828380-1057736988=:97421--



From owner-ietf@ietf.org  Wed Jul  9 08:58: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 IAA29306
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Jul 2003 08:58:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19aEO7-0005cg-UB
	for ietf-list@asgard.ietf.org; Wed, 09 Jul 2003 08:49:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19YXwS-0001Uc-GV
	for ietf@asgard.ietf.org; Fri, 04 Jul 2003 17:18: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 RAA08463
	for <ietf@ietf.org>; Fri, 4 Jul 2003 17:18:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YXwQ-0002jQ-00
	for ietf@ietf.org; Fri, 04 Jul 2003 17:18:02 -0400
Received: from sccrmhc12.comcast.net ([204.127.202.56])
	by ietf-mx with esmtp (Exim 4.12)
	id 19YXwM-0002jA-00
	for ietf@ietf.org; Fri, 04 Jul 2003 17:17:58 -0400
Received: from dockmaster.higgs.com (c-66-229-146-5.we.client2.attbi.com[66.229.146.5](untrusted sender))
          by comcast.net (sccrmhc12) with SMTP
          id <2003070421171501200am73be>; Fri, 4 Jul 2003 21:17:16 +0000
Message-Id: <5.2.1.1.2.20030704135618.01898c48@oak.higgs.net>
X-Sender: simon@higgs.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Fri, 04 Jul 2003 14:17:04 -0700
To: Paul Vixie <paul@vix.com>, ietf@ietf.org
From: Simon Higgs <simon@higgs.com>
Subject: Re: concerning draft-josefsson-dns-url-08.txt
In-Reply-To: <004301c34236$1fd5d340$8e00a8c0@IPV16>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk


>Sent: Friday, July 04, 2003 9:09 AM
>Subject: "here's the real issue: there are many companies and political 
>movements who...think"...
>
> > "here's the real issue: there are many companies and political 
> movements who...think"
> >
> > http://www.ietf.org/mail-archive/ietf/Current/msg21491.html
> > From: Paul Vixie <paul@vix.com>
> > Date: Fri, 04 Jul 2003 03:56:19 +0000
> > "here's the real issue: there are many companies and political 
> movements who
> > think that iana's namespace is not the only namespace.  new.net, for
> > example.  iab takes a very strong "single unique namespace" view, and as
> > such, the i* organizations (iesg in this case) will probably (and ought to,
> > in my view) take a very dim view of any attempt to standardize a uri that
> > permits a "multiple namespace" fiction to be operable."
> > ====

Paul, this is complete and utter nonsense.

The *REAL* issue is access the IANA/DoC/ICANN root. If access that single 
"Precious" root is open (to allow competition per the original requirements 
which drove Draft Postel / IAHC / gTLD-MoU / White Paper / New Corp / DoC / 
ICANN), then every single alt.root becomes irrelevant.

The alt.roots are a solution to a problem that the i* organizations refuse 
to solve. Most of the inhabitants of the alt.roots are there because i* has 
put them there by refusing their requests for inclusion in the single 
"Precious" root.

As a result, we've discovered that it is possible for there to be more than 
one root and the genie is out of the bottle. The alt.roots could be "cat 
herded" back into a single root if i* wanted this to happen. The drafts 
have been published and rejected.

The conclusion we have to draw from this is that i*'s actions encourage the 
creation of multiple roots and that it has made it very clear that i* ants 
total control over it's own root at the expense of the Internet communities 
wishes for name space expansion.



Best Regards,

Simon Higgs

--

The Blog: http://www.simonhiggs.com/

###








From owner-ietf@ietf.org  Wed Jul  9 09:08: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 JAA29618
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Jul 2003 09:08:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19aEbf-0006Jf-Mn
	for ietf-list@asgard.ietf.org; Wed, 09 Jul 2003 09:03:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19aAMQ-0005kI-Oy
	for ietf@asgard.ietf.org; Wed, 09 Jul 2003 04:31: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 EAA23794
	for <ietf@ietf.org>; Wed, 9 Jul 2003 04:31:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aAMN-00053J-00
	for ietf@ietf.org; Wed, 09 Jul 2003 04:31:31 -0400
Received: from coconut.itojun.org ([219.101.47.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aAMM-00053D-00
	for ietf@ietf.org; Wed, 09 Jul 2003 04:31:30 -0400
Received: from itojun.org (localhost [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP id 1924F9F
	for <ietf@ietf.org>; Wed,  9 Jul 2003 17:31:30 +0900 (JST)
Date: Wed, 09 Jul 2003 17:31:26 +0900
From: Jun-ichiro itojun Hagino <itojun@itojun.org>
Subject: draft-ietf-ngtrans-ipv6-smtp-requirement
Message-Id: <20030709083130.1924F9F@coconut.itojun.org>
To: undisclosed-recipients:;
Sender: owner-ietf@ietf.org
Precedence: bulk

------- Blind-Carbon-Copy

To: iesg@ietf.org
Cc: ngtrans@sunroof.eng.sun.com, Ned Freed <ned.freed@mrochek.com>,
    Ted Hardie <hardie@qualcomm.com>
Subject: draft-ietf-ngtrans-ipv6-smtp-requirement
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
From: itojun@iijlab.net
Date: Wed, 09 Jul 2003 17:31:26 +0900
Sender: itojun@itojun.org

	a couple of IETFs ago, it was suggested at the ngtrans wg meeting
	that the document draft-ietf-ngtrans-ipv6-smtp-requirement-xx "should
	be handed to SMTP experts in application area".  since then, there
	has been no actions taken.  the fact is, there is no active working
	group for SMTP and email-related activities.  also ngtrans wg is
	concluded.  therefore, the document is in "zombie" state.

	I still want the document (or the contents of it) be published, as
	it contains critical guidelines for IPv6/v4 dual stack SMTP operation.
	I would like to ask IESG to decide and take appropriate actions,
	such as:
	- poke SMTP experts, let them work on the topic and produce an RFC
	- let me handle the document as an individual submission and publish
	  it as an RFC

	thanks.

itojun

------- End of Blind-Carbon-Copy





From owner-ietf@ietf.org  Wed Jul  9 13:03: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 NAA10202
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Jul 2003 13:03:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19aIC5-000684-SG
	for ietf-list@asgard.ietf.org; Wed, 09 Jul 2003 12:53:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19aIBD-00066K-MM
	for ietf@asgard.ietf.org; Wed, 09 Jul 2003 12: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 MAA09677
	for <ietf@ietf.org>; Wed, 9 Jul 2003 12:52:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aIBC-0000f4-00
	for ietf@ietf.org; Wed, 09 Jul 2003 12:52:30 -0400
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aIBB-0000f0-00
	for ietf@ietf.org; Wed, 09 Jul 2003 12:52:29 -0400
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h69GqRv05432;
	Wed, 9 Jul 2003 09:52:27 -0700
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Wed, 9 Jul 2003 09:52:26 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: NM Research <nm_research@yahoo.com>
cc: ietf@ietf.org
Subject: Re: Address Allocation via Symmetric Amplification of Light
In-Reply-To: <20030709074948.99032.qmail@web80601.mail.yahoo.com>
Message-ID: <Pine.LNX.4.10.10307090945220.3504-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 9 Jul 2003, NM Research wrote:
> P(t) - photons transmitted
> P(r) - photons received
> 
> Symmetric Amplification of Light : P(t)<P(r) whereby polarity of
> each and every photon received is equivalent to the polarity of
> the photon it has been amplified from - while maintaining
> wavelength and frequency characteristics of the photon
> transmitted ( the photon it has been amplified from ).
> 
> The importance of such a system is to sustain results obtained
> from quantum computing or routing from filters in a system in
> optical format, allowing for their redirecting to different
> system memory addresses ( to be received after filteration /
> confirmation by a photocell ).

This thing does not let itself be done.  An amplifier with the
properties that you specify has to be linear (to maintain the
wavelength and frequency characteristics), and the quantum
machanical processes through which it must operate will result in an
additive Gaussian noise component with a _minimum_ power spectral
density of (G-1) h nu per polarization, where G is the power gain, h
is Planck's constant, and nu is the frequency.  This spoils the
sorts of entangled states used in quantum computing.

If you wish to discuss this further let's take it off-line, as it is
not topical for the IETF list.

//cmh




From owner-ietf@ietf.org  Wed Jul  9 16:18: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 QAA19939
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Jul 2003 16:18:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19aLC3-0004Qo-J1
	for ietf-list@asgard.ietf.org; Wed, 09 Jul 2003 16:05:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19aIBG-00067l-TV
	for ietf@asgard.ietf.org; Wed, 09 Jul 2003 12:52: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 MAA09681
	for <ietf@ietf.org>; Wed, 9 Jul 2003 12:52:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aIBF-0000fD-00
	for ietf@ietf.org; Wed, 09 Jul 2003 12:52:33 -0400
Received: from darius.cyrusoft.com ([63.163.82.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aIBE-0000f7-00
	for ietf@ietf.org; Wed, 09 Jul 2003 12:52:32 -0400
Received: from socrates.cyrusoft.com (localhost [127.0.0.1])
	by darius.cyrusoft.com (8.9.3/8.9.3) with ESMTP id MAA24251;
	Wed, 9 Jul 2003 12:41:02 -0400 (EDT)
Date: Wed, 09 Jul 2003 12:44:51 -0400
From: Cyrus Daboo <daboo@cyrusoft.com>
To: Jun-ichiro itojun Hagino <itojun@itojun.org>, ietf@ietf.org
Subject: Re: draft-ietf-ngtrans-ipv6-smtp-requirement
Message-ID: <2147483647.1057754691@socrates.cyrusoft.com>
In-Reply-To: <20030709083130.1924F9F@coconut.itojun.org>
References:  <20030709083130.1924F9F@coconut.itojun.org>
X-Mailer: Mulberry/3.1.0b3 (Mac OS/PPC)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

--On Wednesday, July 9, 2003 5:31 PM +0900 Jun-ichiro itojun Hagino 
<itojun@itojun.org> wrote:

| 	I still want the document (or the contents of it) be published, as
| 	it contains critical guidelines for IPv6/v4 dual stack SMTP operation.
| 	I would like to ask IESG to decide and take appropriate actions,
| 	such as:
| 	- poke SMTP experts, let them work on the topic and produce an RFC
| 	- let me handle the document as an individual submission and publish
| 	  it as an RFC

The ietf-smtp mailing list is still active. Consider posting and discussing 
this document there:

<mailto:ietf-smtp@imc.org>

List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Subscribe: <mailto:ietf-smtp-request@imc.org?body=subscribe>


-- 
Cyrus Daboo





From owner-ietf@ietf.org  Wed Jul  9 17:37:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23334
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Jul 2003 17:37:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19aMSS-0007KR-Be
	for ietf-list@asgard.ietf.org; Wed, 09 Jul 2003 17:26:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19aMS4-0007IU-PS
	for ietf@asgard.ietf.org; Wed, 09 Jul 2003 17:26: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 RAA23005
	for <ietf@ietf.org>; Wed, 9 Jul 2003 17:26:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aMS2-0003io-00
	for ietf@ietf.org; Wed, 09 Jul 2003 17:26:10 -0400
Received: from coconut.itojun.org ([219.101.47.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aMS1-0003iW-00
	for ietf@ietf.org; Wed, 09 Jul 2003 17:26:09 -0400
Received: from itojun.org (localhost [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP
	id B6BF993; Thu, 10 Jul 2003 06:25:58 +0900 (JST)
To: John C Klensin <john@jck.com>
Cc: ietf@ietf.org
In-reply-to: john's message of Wed, 09 Jul 2003 10:20:58 -0400.  <150843140.1057746058@p3.JCK.COM> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: draft-ietf-ngtrans-ipv6-smtp-requirement 
From: itojun@iijlab.net
Date: Thu, 10 Jul 2003 06:25:58 +0900
Message-Id: <20030709212558.B6BF993@coconut.itojun.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

>Whoops...   draft-ietf-ngtrans-ipv6-smtp-requirement-07.txt is 
>shown in the I-D index as the latest version as having been 
>deleted around 30 April.  This makes it a bit hard to obtain and 
>review... if you want some action soon, can you find a copy and 
>get it posted in some prominent place?

	ftp.itojun.org:~ftp/pub/paper has 06.

itojun



From owner-ietf@ietf.org  Thu Jul 10 00:20: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 AAA04481
	for <ietf-web-archive@odin.ietf.org>; Thu, 10 Jul 2003 00:20:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19aSjS-0001eU-E2
	for ietf-list@asgard.ietf.org; Thu, 10 Jul 2003 00:08:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19aSfv-0001Z3-UK
	for ietf@asgard.ietf.org; Thu, 10 Jul 2003 00:04:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04248
	for <ietf@ietf.org>; Thu, 10 Jul 2003 00:04:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aSft-0006fE-00
	for ietf@ietf.org; Thu, 10 Jul 2003 00:04:54 -0400
Received: from bay7-dav40.bay7.hotmail.com ([64.4.10.97] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19aSft-0006fB-00
	for ietf@ietf.org; Thu, 10 Jul 2003 00:04:53 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 9 Jul 2003 21:04:22 -0700
Received: from 63.228.85.179 by bay7-dav40.bay7.hotmail.com with DAV;
	Thu, 10 Jul 2003 04:04:22 +0000
X-Originating-IP: [63.228.85.179]
X-Originating-Email: [fritz_saad@hotmail.com]
From: "Fritz F. Saad" <Fritz_Saad@hotmail.com>
To: <ietf@ietf.org>
Subject: IPv6 Dynamic discovery of home agents
Date: Wed, 9 Jul 2003 22:04:17 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <BAY7-DAV40ezWL1lNua000883f5@hotmail.com>
X-OriginalArrivalTime: 10 Jul 2003 04:04:22.0599 (UTC) FILETIME=[583ECD70:01C34698]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Greetings,

Just wondering if you have pointers to RFCs (or RFC drafts) regarding the
following items:

1- Dynamic discovery of home agents
2- Query home agent for registered nodes with specific home agents

Any pointers, RFCs, ideas are appreciated.

All the best,
Fritz.



From owner-ietf@ietf.org  Thu Jul 10 00:37: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 AAA04923
	for <ietf-web-archive@odin.ietf.org>; Thu, 10 Jul 2003 00:37:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19aT6f-0002dA-S4
	for ietf-list@asgard.ietf.org; Thu, 10 Jul 2003 00:32:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19aT69-0002bU-L2
	for ietf@asgard.ietf.org; Thu, 10 Jul 2003 00:32:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04847
	for <ietf@ietf.org>; Thu, 10 Jul 2003 00:31:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aT67-0006qk-00
	for ietf@ietf.org; Thu, 10 Jul 2003 00:31:59 -0400
Received: from web80606.mail.yahoo.com ([66.218.79.95])
	by ietf-mx with smtp (Exim 4.12)
	id 19aT66-0006qS-00
	for ietf@ietf.org; Thu, 10 Jul 2003 00:31:58 -0400
Message-ID: <20030710043128.8905.qmail@web80606.mail.yahoo.com>
Received: from [213.147.67.206] by web80606.mail.yahoo.com via HTTP; Wed, 09 Jul 2003 21:31:28 PDT
Date: Wed, 9 Jul 2003 21:31:28 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Much Regreted
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-955201535-1057811488=:7439"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-955201535-1057811488=:7439
Content-Type: text/plain; charset=us-ascii

Sorry for the posting. Much regretted to have caused a storm, and I have received your complaints both public and private in good faith.
 
I was just trying to emphasize that the current solid state physics and protocols that IETF discusses cannot be sustained in the future if quantum internet systems are to realized. 
 
At times absurdity in the present my be reality in the future.
 
Regrets,
Nyagudi


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

<DIV>Sorry for the posting. Much regretted to have caused a storm, and I have received your complaints both public and private in good faith.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I was just trying to emphasize that the current solid state physics and protocols that IETF discusses cannot be sustained in the future if quantum internet systems are to realized. </DIV>
<DIV>&nbsp;</DIV>
<DIV>At times absurdity in the present my be reality in the future.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Regrets,</DIV>
<DIV>Nyagudi</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-955201535-1057811488=:7439--



From owner-ietf@ietf.org  Thu Jul 10 05:32: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 FAA23771
	for <ietf-web-archive@odin.ietf.org>; Thu, 10 Jul 2003 05:32:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19aXWX-0001Mf-AT
	for ietf-list@asgard.ietf.org; Thu, 10 Jul 2003 05:15:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19aXWT-0001Kx-6c
	for ietf@asgard.ietf.org; Thu, 10 Jul 2003 05:15: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 FAA23420
	for <ietf@ietf.org>; Thu, 10 Jul 2003 05:15:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aXWQ-0000oP-00
	for ietf@ietf.org; Thu, 10 Jul 2003 05:15:26 -0400
Received: from kirk.rvdp.org ([80.126.101.63])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aXWP-0000oM-00
	for ietf@ietf.org; Thu, 10 Jul 2003 05:15:26 -0400
Received: (from rvdp@localhost)
	by kirk.rvdp.org (8.11.6p2/8.11.6) id h6A9FOe15799
	for ietf@ietf.org; Thu, 10 Jul 2003 11:15:24 +0200 (CEST)
Date: Thu, 10 Jul 2003 11:15:24 +0200
From: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
To: ietf@ietf.org
Subject: jabber at Vienna IETF
Message-ID: <20030710091524.GB14246@rvdp.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Sender: owner-ietf@ietf.org
Precedence: bulk

A message was sent to wgchairs@ietf.org about jabber at the Vienna
IETF. I am not on that list and
ftp://ftp.ietf.org/ietf-mail-archive/wgchairs/current is unreachable
since yesterday. So, I cannot check for any updates.

The message said:

---
To make sure everything is running ok, do a "Join Group Chat" with your
Jabber client:

    Group/Room: testing
    Server:     conference.ietf.jabber.com

This conference room is up and running right now (although probably no
one will be in it when you connect).
---

I tried this and also conference.ietf.jabber.at. Both don't seem to have
this session (yet?).

I would like to do some testing before the IETF starts. Any updates
on this?

	rvdp



From owner-ietf@ietf.org  Thu Jul 10 06:05: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 GAA24533
	for <ietf-web-archive@odin.ietf.org>; Thu, 10 Jul 2003 06:05:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19aYD7-00034j-Mg
	for ietf-list@asgard.ietf.org; Thu, 10 Jul 2003 05:59:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19aYCt-000335-0h
	for ietf@asgard.ietf.org; Thu, 10 Jul 2003 05:59:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24430
	for <ietf@ietf.org>; Thu, 10 Jul 2003 05:59:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aYCq-000171-00
	for ietf@ietf.org; Thu, 10 Jul 2003 05:59:16 -0400
Received: from jay.songbird.com ([208.184.79.253])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aYCp-00016x-00
	for ietf@ietf.org; Thu, 10 Jul 2003 05:59:15 -0400
Received: from Rincewind.ninebynine.org (jay.songbird.com [208.184.79.253])
	(authenticated)
	by jay.songbird.com (8.11.6/8.11.3) with ESMTP id h6A9xB028575;
	Thu, 10 Jul 2003 02:59:12 -0700
Message-Id: <5.1.0.14.2.20030710091331.02db7710@127.0.0.1>
X-Sender: gk-bulk@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 10 Jul 2003 09:17:41 +0100
To: NM Research <nm_research@yahoo.com>, ietf@ietf.org
From: Graham Klyne <GK@ninebynine.org>
Subject: Re: Much Regreted
In-Reply-To: <20030710043128.8905.qmail@web80606.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

Without beginning to understand the physics involved, I think it would be a 
loss if short concise postings like yours [1] were to be discouraged from 
this IETF list.  I do think the occasional challenge to conventional 
thinking is very healthy and desirable.

#g
--

[1] http://www1.ietf.org/mail-archive/ietf/Current/msg21526.html

At 21:31 09/07/03 -0700, NM Research wrote:
>Sorry for the posting. Much regretted to have caused a storm, and I have 
>received your complaints both public and private in good faith.
>
>I was just trying to emphasize that the current solid state physics and 
>protocols that IETF discusses cannot be sustained in the future if quantum 
>internet systems are to realized.
>
>At times absurdity in the present my be reality in the future.
>
>Regrets,
>Nyagudi
>
>
>Do you Yahoo!?
><http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*http://promo.yahoo.com/sbc/>SBC 
>Yahoo! DSL - Now only $29.95 per month!

-------------------
Graham Klyne
<GK@NineByNine.org>
PGP: 0FAA 69FF C083 000B A2E9  A131 01B9 1C7A DBCA CB5E




From owner-ietf@ietf.org  Thu Jul 10 06:26: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 GAA25446
	for <ietf-web-archive@odin.ietf.org>; Thu, 10 Jul 2003 06:26:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19aYWT-00045P-9l
	for ietf-list@asgard.ietf.org; Thu, 10 Jul 2003 06:19:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19aYVq-00043Q-Mw
	for ietf@asgard.ietf.org; Thu, 10 Jul 2003 06:18: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 GAA25295
	for <ietf@ietf.org>; Thu, 10 Jul 2003 06:18:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aYVo-0001Lh-00
	for ietf@ietf.org; Thu, 10 Jul 2003 06:18:52 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aYVn-0001Le-00
	for ietf@ietf.org; Thu, 10 Jul 2003 06:18:51 -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 h6AAJUxS050340
	for <ietf@ietf.org>; Thu, 10 Jul 2003 12:19:30 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 10 Jul 2003 12:18:47 +0200
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: Lawful interception
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <E4CF22A8-B2BF-11D7-BA46-00039388672E@muada.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

With regard to draft-baker-slem-architecture-01.txt and the surrounding 
issues: is anything happening in this area in Vienna?




From owner-ietf@ietf.org  Thu Jul 10 11:39: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 LAA07920
	for <ietf-web-archive@odin.ietf.org>; Thu, 10 Jul 2003 11:39:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19adOQ-00050v-Ad
	for ietf-list@asgard.ietf.org; Thu, 10 Jul 2003 11:31:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19adOI-0004za-Oo
	for ietf@asgard.ietf.org; Thu, 10 Jul 2003 11:31: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 LAA07571
	for <ietf@ietf.org>; Thu, 10 Jul 2003 11:31:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19adOH-00042S-00
	for ietf@ietf.org; Thu, 10 Jul 2003 11:31:25 -0400
Received: from smtpsrv10.isis.unc.edu ([152.2.1.241] helo=smtp.unc.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19adOH-00042P-00
	for ietf@ietf.org; Thu, 10 Jul 2003 11:31:25 -0400
Received: from [192.168.1.101] (rdu57-255-231.nc.rr.com [66.57.255.231])
	(authenticated bits=0)
	by smtp.unc.edu (8.12.9/8.12.9) with ESMTP id h6AFVKWX007365
	(version=TLSv1/SSLv3 cipher=IDEA-CBC-SHA bits=128 verify=NOT)
	for <ietf@ietf.org>; Thu, 10 Jul 2003 11:31:21 -0400 (EDT)
Date: Thu, 10 Jul 2003 11:31:15 -0400
From: Simon Spero <ses@unc.edu>
To: ietf@ietf.org
Subject: RFP:  IPV6  addressable light switches
Message-ID: <105040703.1057836675@[192.168.1.101]>
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

[This is the best time to ask questions like this, as the flood of drafts 
triggers so much avoidance behaviour]

I remember that one of the advantages of IPV6 was that it would allow 
addressing down to the level of individual light switches.

It's been 11 years since the Boston T Party;  has anybody implemented this 
- either natively or through bridging to X-10? If so, what sort of prices 
were involved?  I prefer not to buy from X-10 (the company) because of 
their role in evolving the evil of pop-ups.

How many people have converted their home network to pure V6? Is it 
possible to get native V6 using Road Runner ?  Has anyone done this in the 
presence of V4 only appliances (i.e. ReplayTV)?

Any switchers want to stand up and be counted?  Someone should grab an XL-1 
in Vienna and roll tape (even though they'll probably all end "My name is 
<x> and I'm a network protocol designer"). Could be the next Ellen 
Fleiss... 



From owner-ietf@ietf.org  Fri Jul 11 04:37:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20982
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Jul 2003 04:37:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19atCa-0006HB-EH
	for ietf-list@asgard.ietf.org; Fri, 11 Jul 2003 04:24:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19atCL-0006G5-Ot
	for ietf@asgard.ietf.org; Fri, 11 Jul 2003 04:24: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 EAA20570
	for <ietf@ietf.org>; Fri, 11 Jul 2003 04:24:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19atCJ-0003Sv-00
	for ietf@ietf.org; Fri, 11 Jul 2003 04:24:07 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19atCI-0003SX-00
	for ietf@ietf.org; Fri, 11 Jul 2003 04:24:06 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h6B8Nae26264
	for <ietf@ietf.org>; Fri, 11 Jul 2003 11:23:36 +0300
Date: Fri, 11 Jul 2003 11:23:36 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: IETF57 Wien WLAN readiness?
Message-ID: <Pine.LNX.4.44.0307111122520.26262-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,
                                                                              
As a lot of folks are coming to IETF57 early, it would be interesting to
know when:
 - the WLAN network is estimated to be operational
 - when/whether it is possible to come to the conf. center
(i.e. as it isn't in a hotel, is it open for IETF'ers e.g. on Saturday
already)
                                                                              
-- 
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  Fri Jul 11 08:58: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 IAA27822
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Jul 2003 08:58:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19axDG-000272-Lq
	for ietf-list@asgard.ietf.org; Fri, 11 Jul 2003 08:41:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19axD4-00026I-R2
	for ietf@asgard.ietf.org; Fri, 11 Jul 2003 08:41:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27539
	for <ietf@ietf.org>; Fri, 11 Jul 2003 08:41:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19axD4-0005Lg-00
	for ietf@ietf.org; Fri, 11 Jul 2003 08:41:10 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19axD3-0005LS-00
	for ietf@ietf.org; Fri, 11 Jul 2003 08:41:09 -0400
Received: from BBFUJIP.brandenburg.com (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h6BCiBF12820;
	Fri, 11 Jul 2003 05:44:11 -0700
Date: Thu, 10 Jul 2003 16:24:14 +0200
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: <45169560975.20030710162414@brandenburg.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: ietf@ietf.org
Subject: Re: The requirements cycle (Re: WG review: Layer 2 Virtual....)
In-Reply-To: <61570000.1057734279@askvoll.hjemme.alvestrand.no>
References: <200307031652.h63Gqmfq009031@rtp-core-1.cisco.com>
 <351620000.1057264376@askvoll.hjemme.alvestrand.no>
 <1451723728.20030705175341@brandenburg.com> <20030705194512.D1840@sbrim-w2k01>
 <15951714882.20030706225806@brandenburg.com>
 <61570000.1057734279@askvoll.hjemme.alvestrand.no>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald,

HTA> I try to work from the theory that neither of the parties involved in this
HTA> conflict are technically incompetent or deliberately malicious.

Me too.

That's why talking about "intentions" or even "competence" in these
discussions is usually not very helpful.  So, it's a good thing that I
did not do that.


HTA> Assigning "blame" to one party, and appearing to declare their actions to
HTA> have no possible rational explanation, is not compatible with this theory.

I do not recall "declar[ing] their actions to have no possible rational
explanation".  What text are you referring to?

I was careful in my characterization of the problem being discussed. It
was a very specific situation, and it does occur.

Now, I do acknowledge that the word "blame" is uncomfortable, but it has
the correct denotation for its use.

We are discussing problems. Problems have causes. The word "blame" is an
efficient and precise term for referring to the source (cause) of a
problem.

However, saying something like "we should focus our attention on the source of
the difficulty, rather than suggest focusing our attention on those who
are the object of it" strikes me as awkward enough to be silly.

Please remember that I was responding to a note from you in which you
said:

HTA> even if a WG feels abused by the IESG, or its AD, that's no excuse for a WG
HTA> not fighting back - in this case, by rapidly removing the IESG's apparent
HTA> excuses for delay.

In other words, you appear to be saying that a working group should be
expected to perform any action imposed on them, no matter how
unreasonable. Perhaps that is not what you meant, but it is the meaning
I take from your sentence.

And it is a position with which I disagree strongly.

That is:

       When an inappropriate requirement is imposed on a working group,
       the correct action is to remove the requirement.

       It is not appropriate to tell the working group that they have
       "no excuse.. [for not] rapidly removing the IESG's apparent
       excuses for delay."

       
HTA> (Note that one party's actions being *wrong* when viewed in hindsight is
HTA> *not* incompatible with the theory!)

Sometimes a problem is truly due to a "systems" difficulty, in which all
of the participants have a problem in the overall interaction.  In these
cases, it is extremely counter-productive to assign blame.

However, I described a very specific situation and I was (and am)
claiming that this is not a "system" problem but a problem in the
administration of the process.  Hence it is appropriate to focus on
those doing this kind of problematic administration.

You may well respond that their administration is not the problem. Given
the conditions that I specified, it would be extremely helpful to hear
why it is acceptable to delay competent work that conforms to its
charter and has no known technical problems.

However it is not true that everyone always performs well.  There are
errors made.

In these cases, we need to discuss the error and its cause, so we can
discuss how to fix it.

We are not going to make progress fixing the IETF's problems if people
have no permission to speak frankly.

     We are one year after Yokohama, and no changes have yet been made.

For that matter, we have little participation in the discussions.

     That should worry folks, quite a lot.

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 Jul 11 11:24: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 LAA03377
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Jul 2003 11:24:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19azNl-0001hW-At
	for ietf-list@asgard.ietf.org; Fri, 11 Jul 2003 11:00:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19azMs-0001hH-MF
	for ietf@asgard.ietf.org; Fri, 11 Jul 2003 10:59:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02654
	for <ietf@ietf.org>; Fri, 11 Jul 2003 10:59:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19azMn-0006H4-00
	for ietf@ietf.org; Fri, 11 Jul 2003 10:59:21 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19azMm-0006Gg-00
	for ietf@ietf.org; Fri, 11 Jul 2003 10:59:21 -0400
Received: from cisco.com (171.68.223.137)
  by sj-iport-3.cisco.com with ESMTP; 11 Jul 2003 08:01:55 -0700
Received: from [10.32.254.183] (stealth-10-32-254-183.cisco.com [10.32.254.183])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with SMTP id h6BEwhpZ010549
	for <ietf@ietf.org>; Fri, 11 Jul 2003 07:58:44 -0700 (PDT)
Date: Fri, 11 Jul 2003 10:58:42 -0400
From: "David R. Oran" <oran@cisco.com>
To: ietf@ietf.org
Subject: Vienna Social event (sorry for bothering such a  wide audience)
Message-ID: <215357812.1057921122@[10.32.254.183]>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I tried online registration for the social event via

http://files.aon.at/ietf/payment.htm

and got "this form is no longer valid"

There were no links on any of the pages to tech support for the social 
event sponsors.

Any ideas?

Dave.




From owner-ietf@ietf.org  Fri Jul 11 13:12: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 NAA06479
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Jul 2003 13:12:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19b1Fs-0002r9-IS
	for ietf-list@asgard.ietf.org; Fri, 11 Jul 2003 13:00:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19b1Fn-0002qm-0j
	for ietf@asgard.ietf.org; Fri, 11 Jul 2003 13:00: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 NAA05998
	for <ietf@ietf.org>; Fri, 11 Jul 2003 13:00:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19b1Fl-0007Cp-00
	for ietf@ietf.org; Fri, 11 Jul 2003 13:00:13 -0400
Received: from www.routeexplorer.com ([65.192.41.10] helo=mailman.packetdesign.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19b1Fk-0007CU-00
	for ietf@ietf.org; Fri, 11 Jul 2003 13:00:12 -0400
Received: from packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.12.8/8.12.8) with ESMTP id h6BGxa3V008947;
	Fri, 11 Jul 2003 09:59:37 -0700 (PDT)
	(envelope-from casner@acm.org)
Date: Fri, 11 Jul 2003 10:05:39 -0700 (PDT)
From: Stephen Casner <casner@acm.org>
To: Pekka Savola <pekkas@netcore.fi>
cc: ietf@ietf.org
Subject: Re: IETF57 Wien WLAN readiness?
In-Reply-To: <Pine.LNX.4.44.0307111122520.26262-100000@netcore.fi>
Message-ID: <20030711100055.F2784-100000@oak.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 11 Jul 2003, Pekka Savola wrote:
> As a lot of folks are coming to IETF57 early, it would be interesting to
> know when:
>  - the WLAN network is estimated to be operational
>  - when/whether it is possible to come to the conf. center
> (i.e. as it isn't in a hotel, is it open for IETF'ers e.g. on Saturday
> already)

A portion/extension of the WLAN is installed in the lobby and 1st
floor of the Crowne Plaza hotel.  I've been using it since yesterday.

                                                        -- Steve




From owner-ietf@ietf.org  Fri Jul 11 13:21: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 NAA06810
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Jul 2003 13:21:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19b1VM-0003FQ-6F
	for ietf-list@asgard.ietf.org; Fri, 11 Jul 2003 13:16:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19b1Us-0003Df-IS
	for ietf@asgard.ietf.org; Fri, 11 Jul 2003 13:15: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 NAA06639
	for <ietf@ietf.org>; Fri, 11 Jul 2003 13:15:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19b1Uo-0007Q6-00
	for ietf@ietf.org; Fri, 11 Jul 2003 13:15:46 -0400
Received: from [216.93.164.123] (helo=zak.ecotroph.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19b1Un-0007Q2-00
	for ietf@ietf.org; Fri, 11 Jul 2003 13:15:45 -0400
Received: from thinkingcat.com (softdnserr [::ffff:68.169.63.42])
  (AUTH: LOGIN leslie, TLS: TLSv1/SSLv3,128bits,RC4-MD5)
  by zak.ecotroph.net with esmtp; Fri, 11 Jul 2003 13:15:37 -0400
Message-ID: <3F0EF062.7050606@thinkingcat.com>
Date: Fri, 11 Jul 2003 13:14:10 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: ietf@ietf.org
Subject: Re: Lawful interception
References: <E4CF22A8-B2BF-11D7-BA46-00039388672E@muada.com>
In-Reply-To: <E4CF22A8-B2BF-11D7-BA46-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

Howdy,

I don't know if it constitutes something "happening" in
the area, but we're trying to firm up plans for Fred Baker
to say some words about it at the IAB plenary on Wednesday
evening.

Leslie.

Iljitsch van Beijnum wrote:
> With regard to draft-baker-slem-architecture-01.txt and the surrounding 
> issues: is anything happening in this area in Vienna?
> 
> 




From owner-ietf@ietf.org  Fri Jul 11 14:14: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 OAA08720
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Jul 2003 14:14:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19b2Ds-0004cC-Be
	for ietf-list@asgard.ietf.org; Fri, 11 Jul 2003 14:02:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19b2B6-0004bJ-K3
	for ietf@asgard.ietf.org; Fri, 11 Jul 2003 13:59: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 NAA08353
	for <ietf@ietf.org>; Fri, 11 Jul 2003 13:59:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19b2B5-0000Ax-00
	for ietf@ietf.org; Fri, 11 Jul 2003 13:59:27 -0400
Received: from [206.112.85.61] (helo=mail.cdt.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19b2B4-0000Ak-00
	for ietf@ietf.org; Fri, 11 Jul 2003 13:59:26 -0400
Received: from [10.0.1.19] (66.safeclick.net [63.119.245.66])
	by mail.cdt.org (Postfix) with ESMTP
	id 5AA2A490010; Fri, 11 Jul 2003 13:55:49 -0400 (EDT)
Mime-Version: 1.0
X-Sender: john@mail.cdt.org
Message-Id: <a05200f02bb34a801aa23@[10.0.1.19]>
Date: Fri, 11 Jul 2003 13:59:50 -0400
To: ietf@ietf.org
From: John Morris <jmorris@cdt.org>
Subject: draft-morris-policy-considerations-00.txt
Cc: "Davidson, Alan " <abd@cdt.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

Thanks to those who responded off list to my solicitation of feedback 
on this I-D a couple of weeks ago.  This draft suggests public policy 
considerations that the IETF should consider in making design 
decisions.  The draft would really benefit from broad input.  The 
abstract and link are below.

I would like to discuss the draft with anyone interested who might be 
in Vienna next week.  Just to give a target time and place, I plan to 
grab some coffee/pastry/fruit and meet in Hall GH on the Blue Level 
from 8:00 to 8:30 a.m. on Wednesday, July 16, and I invite anyone who 
wants to discuss this draft to stop by.  If you know you plan to 
come, let me know off list (in case there is a groundswell to change 
the time or place).  I'd also be happy to talk about this in a more 
bar oriented "bar bof" some evening.

John

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
>	Title		: Public Policy Considerations for Internet Design
>                           Decisions
>	Author(s)	: J. Morris, A. Davidson
>	Filename	: draft-morris-policy-considerations-00.txt
>	Pages		: 21
>	Date		: 2003-6-24
>
>This document suggests public policy questions that the IETF should
>consider and possibly address when developing new standards and
>protocols, and modifying or enhancing old standards and protocols. 
>This document contains questions to be considered, as opposed to
>guidelines or rules that should in all cases be followed.  This first
>draft provides a framework for identifying and discussing questions
>of public policy concern, and invites members of the IETF community
>to contribute to the questions and discussions raised here.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-morris-policy-considerations-00.txt



From owner-ietf@ietf.org  Fri Jul 11 17:03: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 RAA16950
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Jul 2003 17:03:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19b4pS-0006As-Kx
	for ietf-list@asgard.ietf.org; Fri, 11 Jul 2003 16:49:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19b4pA-0006AR-9Q
	for ietf@asgard.ietf.org; Fri, 11 Jul 2003 16:49: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 QAA16198
	for <ietf@ietf.org>; Fri, 11 Jul 2003 16:48:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19b4p8-00029Y-00
	for ietf@ietf.org; Fri, 11 Jul 2003 16:48:58 -0400
Received: from router.boolean.net
	([198.144.206.49] helo=pretender.boolean.net ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19b4p7-00029Q-00
	for ietf@ietf.org; Fri, 11 Jul 2003 16:48:58 -0400
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h6BKmmc6055476;
	Fri, 11 Jul 2003 20:48:50 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030711224414.01bdf130@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 11 Jul 2003 22:45:37 +0200
To: Pekka Savola <pekkas@netcore.fi>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: IETF57 Wien WLAN readiness?
Cc: ietf@ietf.org
In-Reply-To: <Pine.LNX.4.44.0307111122520.26262-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

BTW, there is free wireless access in the Museum Quarter.
Good beer, good food, and good bits.

Kurt

At 10:23 AM 7/11/2003, Pekka Savola wrote:
>Hi,
>                                                                              
>As a lot of folks are coming to IETF57 early, it would be interesting to
>know when:
> - the WLAN network is estimated to be operational
> - when/whether it is possible to come to the conf. center
>(i.e. as it isn't in a hotel, is it open for IETF'ers e.g. on Saturday
>already)
>                                                                              
>-- 
>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  Sat Jul 12 06:36: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 GAA09049
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Jul 2003 06:36:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19bHZ2-0008FF-E8
	for ietf-list@asgard.ietf.org; Sat, 12 Jul 2003 06:25:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19bHYN-0008Ew-1I
	for ietf@asgard.ietf.org; Sat, 12 Jul 2003 06:24: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 GAA08542
	for <ietf@ietf.org>; Sat, 12 Jul 2003 06:24:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19bHYK-0005RD-00
	for ietf@ietf.org; Sat, 12 Jul 2003 06:24:28 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19bHYJ-0005Qg-00
	for ietf@ietf.org; Sat, 12 Jul 2003 06:24:27 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h6CANpa04997
	for <ietf@ietf.org>; Sat, 12 Jul 2003 13:23:51 +0300
Date: Sat, 12 Jul 2003 13:23:51 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: Re: IETF57 Wien WLAN readiness?
In-Reply-To: <Pine.LNX.4.44.0307111122520.26262-100000@netcore.fi>
Message-ID: <Pine.LNX.4.44.0307121321460.4778-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 11 Jul 2003, Pekka Savola wrote:
> As a lot of folks are coming to IETF57 early, it would be interesting to
> know when:
>  - the WLAN network is estimated to be operational
>  - when/whether it is possible to come to the conf. center
> (i.e. as it isn't in a hotel, is it open for IETF'ers e.g. on Saturday
> already)

I can personally attest that it seems to be working fine. (IPv6 too :-).

-- 
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  Sat Jul 12 17:53: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 RAA13640
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Jul 2003 17:53:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19bS2J-00022R-FS
	for ietf-list@asgard.ietf.org; Sat, 12 Jul 2003 17:36:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19bS1n-000226-OS
	for ietf@asgard.ietf.org; Sat, 12 Jul 2003 17:35: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 RAA12471
	for <ietf@ietf.org>; Sat, 12 Jul 2003 17:35:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19bS1m-0005o2-00
	for ietf@ietf.org; Sat, 12 Jul 2003 17:35:34 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 19bS1l-0005ng-00
	for ietf@ietf.org; Sat, 12 Jul 2003 17:35:33 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 697DD61BB3; Sat, 12 Jul 2003 23:35:03 +0200 (CEST)
Date: Sat, 12 Jul 2003 23:34:58 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: ietf@ietf.org
Subject: Re: The requirements cycle (Re: WG review: Layer 2 Virtual....)
Message-ID: <122634218.1058052898@localhost>
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

Dave,

you are talking about actions that could be taken by all the actors in the 
system. I was talking about the actions that the WG could take on its own.

--On 10. juli 2003 16:24 +0200 Dave Crocker <dhc@dcrocker.net> wrote:

> HTA> even if a WG feels abused by the IESG, or its AD, that's no excuse
> for a WG not fighting back - in this case, by rapidly removing the
> IESG's apparent excuses for delay.
>
> In other words, you appear to be saying that a working group should be
> expected to perform any action imposed on them, no matter how
> unreasonable. Perhaps that is not what you meant, but it is the meaning
> I take from your sentence.

OK, let abstract out the case, and let us go through this theoretical 
example in more detail.

- A writer group is seeking to have a document published.
- A gatekeeper group is imposing a requirement that must be fulfilled
  before the document can be published.
- The working group feels that this requirement is unreasonable.

Now, assume that both parties are acting in good faith, both parties are 
reasonably competent at their work, and that both parties are interested in 
seeing the document published.

Since we're assuming good faith, rationality and competence on both sides, 
we must assume the gatekeeper group had what it thought was a rational 
reason to impose the requirement. It would be irrational for the gatekeeper 
group to drop the requirement without being convinced that its reason was 
wrong or insufficient.

I see a number of rational actions from the writer group, which need not be 
exclusive:

A - Try to convince the gatekeeper group to drop the requirement.
B - Try to fulfil the requirement with the minimum amount of energy.
C - Take their business elsewhere (give up).

In an ideal world, there would be dialogue enough between the writer group 
and the gatekeeper group that one would convince the other about the 
reasonableness of the requirement. In the real world, this doesn't always 
happen.

What I was saying is that I don't see the group's action that seems to have 
happened here (procrastination in fulfilling the requirement, after being 
convinced that convincing the gatekeeper group to drop it won't work) as 
rational. Understandable, but not rational.








From owner-ietf@ietf.org  Sun Jul 13 14:01: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 OAA01256
	for <ietf-web-archive@odin.ietf.org>; Sun, 13 Jul 2003 14:01:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19bl03-0007mQ-KI
	for ietf-list@asgard.ietf.org; Sun, 13 Jul 2003 13:51:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19bkzj-0007ly-Hm
	for ietf@asgard.ietf.org; Sun, 13 Jul 2003 13:50: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 NAA00983
	for <ietf@ietf.org>; Sun, 13 Jul 2003 13:50:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19bkzi-0006SC-00
	for ietf@ietf.org; Sun, 13 Jul 2003 13:50:42 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19bkzh-0006S9-00
	for ietf@ietf.org; Sun, 13 Jul 2003 13:50:41 -0400
Received: from BBFUJIP.brandenburg.com (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h6DHrlF25109;
	Sun, 13 Jul 2003 10:53:47 -0700
Date: Sun, 13 Jul 2003 15:26:28 +0200
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: <8117483489.20030713152628@brandenburg.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: ietf@ietf.org
Subject: Re: The requirements cycle (Re: WG review: Layer 2 Virtual....)
In-Reply-To: <122634218.1058052898@localhost>
References: <122634218.1058052898@localhost>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald,

HTA> you are talking about actions that could be taken by all the actors in the
HTA> system. I was talking about the actions that the WG could take on its own.

THe original discussion was about problems with IESG-related actions.
Your introduction of a derivative thread about actions the WG might take
was cast as there being "no excuse" for their not taking those actions.

Since the focus had been on problems due to IESG-related barriers that
were viewed as frankly inappropriate, directing the focus over to the WG
is a distraction.  (Note that, alas, it has at least had that effect.)


HTA> - A gatekeeper group is imposing a requirement that must be fulfilled
HTA>   before the document can be published.
HTA> - The working group feels that this requirement is unreasonable.

HTA> Now, assume that both parties are acting in good faith, both parties are
HTA> reasonably competent at their work, and that both parties are interested in
HTA> seeing the document published.

Sorry, no.

With respect to the situation that I have twice described very
carefully, the imposed requirements are not reasonable and not
"competent".

Let's remember that competence relates to specific skill-sets. The
skill-set at issue here is one of working group oversight. The problems
being discussed are/were about difficulties in IESG
administration/oversight of WGs.

There needs to be equivalent focus about problems with WG chair
management, WG participant actions, and even IETF-wide participation in
review, etc. of working group.

But we will not make progress if any attempt to focus on a specific
component of this system results in defensiveness or a redirection of
focus.

So, sorry, but no we cannot assert that the AD in the hypothetical was
acting competently, with respect to WG management.  Please review the
description of the circumstances that I described.  I repeat:  they were
carefully cast, and they DO occur in the IETF.

Therefore, the rest of your latest response to me pertains to some
independent sub-thread of all this.  I have no comment on it, because I
would rather get some discussion of one thread at a time, rather than
jumping around.

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




From owner-ietf@ietf.org  Mon Jul 14 00:36:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13739
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 00:36:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19bujq-0005fH-PO
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 00:14:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19bujD-0005eu-Ej
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 00:14: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 AAA13439
	for <ietf@ietf.org>; Mon, 14 Jul 2003 00:14:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19bujB-0001CB-00
	for ietf@ietf.org; Mon, 14 Jul 2003 00:14:17 -0400
Received: from web80601.mail.yahoo.com ([66.218.79.90])
	by ietf-mx with smtp (Exim 4.12)
	id 19bujA-0001Bp-00
	for ietf@ietf.org; Mon, 14 Jul 2003 00:14:16 -0400
Message-ID: <20030714041346.49394.qmail@web80601.mail.yahoo.com>
Received: from [64.86.232.101] by web80601.mail.yahoo.com via HTTP; Sun, 13 Jul 2003 21:13:46 PDT
Date: Sun, 13 Jul 2003 21:13:46 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Re: Much Regreted
To: Graham Klyne <GK@ninebynine.org>, ietf@ietf.org
In-Reply-To: <5.1.0.14.2.20030710091331.02db7710@127.0.0.1>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-65815791-1058156026=:49266"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-65815791-1058156026=:49266
Content-Type: text/plain; charset=us-ascii

I feel that I have valid arguements against some current quantum coding, gates, qubits, etc.  I am more for a statiscally and AI approach rather than protocols. Furthermore with wavelength, frequency and polarity you could assign each and every word a place/bit.  If the IETF is not carefully something will come along that will kill them like fidonet.  It is not remote : IPv6 and Internet 2 may be still born.
 
Nyagudi 

Graham Klyne <GK@ninebynine.org> wrote:
Without beginning to understand the physics involved, I think it would be a 
loss if short concise postings like yours [1] were to be discouraged from 
this IETF list. I do think the occasional challenge to conventional 
thinking is very healthy and desirable.

#g
--

[1] http://www1.ietf.org/mail-archive/ietf/Current/msg21526.html

At 21:31 09/07/03 -0700, NM Research wrote:
>Sorry for the posting. Much regretted to have caused a storm, and I have 
>received your complaints both public and private in good faith.
>
>I was just trying to emphasize that the current solid state physics and 
>protocols that IETF discusses cannot be sustained in the future if quantum 
>internet systems are to realized.
>
>At times absurdity in the present my be reality in the future.
>
>Regrets,
>Nyagudi
>
>
>Do you Yahoo!?
>SBC 
>Yahoo! DSL - Now only $29.95 per month!

-------------------
Graham Klyne

PGP: 0FAA 69FF C083 000B A2E9 A131 01B9 1C7A DBCA CB5E




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

<DIV>I feel that I have valid arguements against some current quantum coding, gates, qubits, etc.&nbsp;&nbsp;I am more for a statiscally and AI approach&nbsp;rather than protocols. Furthermore with wavelength, frequency and polarity&nbsp;you could assign each and every word a place/bit.&nbsp; If the IETF is not&nbsp;carefully something will come along that will kill them like fidonet.&nbsp; It is not remote : IPv6 and Internet 2 may be still born.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi&nbsp;<BR><BR><B><I>Graham Klyne &lt;GK@ninebynine.org&gt;</I></B> wrote:</DIV>
<DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid; WIDTH: 100%">Without beginning to understand the physics involved, I think it would be a <BR>loss if short concise postings like yours [1] were to be discouraged from <BR>this IETF list. I do think the occasional challenge to conventional <BR>thinking is very healthy and desirable.<BR><BR>#g<BR>--<BR><BR>[1] http://www1.ietf.org/mail-archive/ietf/Current/msg21526.html<BR><BR>At 21:31 09/07/03 -0700, NM Research wrote:<BR>&gt;Sorry for the posting. Much regretted to have caused a storm, and I have <BR>&gt;received your complaints both public and private in good faith.<BR>&gt;<BR>&gt;I was just trying to emphasize that the current solid state physics and <BR>&gt;protocols that IETF discusses cannot be sustained in the future if quantum <BR>&gt;internet systems are to realized.<BR>&gt;<BR>&gt;At times absurdity in the present my be reality in the
 future.<BR>&gt;<BR>&gt;Regrets,<BR>&gt;Nyagudi<BR>&gt;<BR>&gt;<BR>&gt;Do you Yahoo!?<BR>&gt;<HTTP: evt="1207/*http://promo.yahoo.com/sbc/" rd.yahoo.com *http: pa.yahoo.com>SBC <BR>&gt;Yahoo! DSL - Now only $29.95 per month!<BR><BR>-------------------<BR>Graham Klyne<BR><GK@NINEBYNINE.ORG><BR>PGP: 0FAA 69FF C083 000B A2E9 A131 01B9 1C7A DBCA CB5E<BR><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!
--0-65815791-1058156026=:49266--



From owner-ietf@ietf.org  Mon Jul 14 02:23: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 CAA27596
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 02:23:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19bwbx-0002ze-RL
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 02:14:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19bwb8-0002aw-BV
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 02:14: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 CAA26655
	for <ietf@ietf.org>; Mon, 14 Jul 2003 02:14:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19bwb6-0001eo-00
	for ietf@ietf.org; Mon, 14 Jul 2003 02:14:04 -0400
Received: from web80605.mail.yahoo.com ([66.218.79.94])
	by ietf-mx with smtp (Exim 4.12)
	id 19bwb5-0001eY-00
	for ietf@ietf.org; Mon, 14 Jul 2003 02:14:03 -0400
Message-ID: <20030714061334.51728.qmail@web80605.mail.yahoo.com>
Received: from [62.8.64.24] by web80605.mail.yahoo.com via HTTP; Sun, 13 Jul 2003 23:13:34 PDT
Date: Sun, 13 Jul 2003 23:13:34 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Feasibility of 4G systems
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1836237954-1058163214=:50738"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-1836237954-1058163214=:50738
Content-Type: text/plain; charset=us-ascii

About the  feasibility of 4g systems.  I feel that they have a bright future, if and only if the human understanding of the particulate nature of electromagnetic radiation is not enhanced to the level of manipulation and usage, and remains primitive as it current exists.
 
If organizations like CERN can manage to manipulate em-radiation communications at quantum level, then there will be quantum wireless communications.  With Wifi already in the market, 3g, 4g will be a sure flop if such an innovation comes.
 
Of course the entry costs for any new internet rivals will depend on US Government or EU funding.
 
Nyagudi


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

<DIV>About the&nbsp; feasibility of 4g systems.&nbsp; I feel that they have a bright future, if and only if the human understanding of the particulate nature of electromagnetic radiation is not enhanced to the level of manipulation and usage, and remains primitive as it current exists.</DIV>
<DIV>&nbsp;</DIV>
<DIV>If organizations like CERN can manage to manipulate em-radiation communications at quantum level, then there will be quantum wireless communications.&nbsp; With Wifi already in the market, 3g,&nbsp;4g will be a sure flop if such an innovation comes.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Of course the entry costs for any new internet rivals will depend on US Government or EU funding.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi</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-1836237954-1058163214=:50738--



From owner-ietf@ietf.org  Mon Jul 14 03:12: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 DAA28932
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 03:12:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19bxPJ-0006Bm-GB
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 03:05:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19bxOe-0006An-UN
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 03:05:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28448
	for <ietf@ietf.org>; Mon, 14 Jul 2003 03:05:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19bxOc-00020p-00
	for ietf@ietf.org; Mon, 14 Jul 2003 03:05:14 -0400
Received: from [81.160.170.167] (helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19bxOb-00020j-00
	for ietf@ietf.org; Mon, 14 Jul 2003 03:05:13 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h6E72AF16817
	for <ietf@ietf.org>; Mon, 14 Jul 2003 09:02:10 +0200
Message-ID: <3F125572.1090308@it.su.se>
Date: Mon, 14 Jul 2003 09:02:10 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: ssl jabber?
X-Enigmail-Version: 0.76.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

It would be nice to be able to speak ssl to the conference server...

      Cheers Leif




From owner-ietf@ietf.org  Mon Jul 14 04:05: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 EAA00556
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 04:05:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19byAr-0007Tq-NI
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 03:55:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19byAe-0007Su-UY
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 03:54:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00239
	for <ietf@ietf.org>; Mon, 14 Jul 2003 03:54:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19byAc-0002RX-00
	for ietf@ietf.org; Mon, 14 Jul 2003 03:54:50 -0400
Received: from [208.245.212.109] (helo=hades.jabber.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19byAb-0002RU-00
	for ietf@ietf.org; Mon, 14 Jul 2003 03:54:50 -0400
Received: by hades.jabber.org (Postfix, from userid 1005)
	id 2658B63EE7; Mon, 14 Jul 2003 02:54:39 -0500 (CDT)
Date: Mon, 14 Jul 2003 02:54:39 -0500
From: Peter Saint-Andre <stpeter@jabber.org>
To: Leif Johansson <leifj@it.su.se>
Cc: ietf@ietf.org
Subject: Re: ssl jabber?
Message-ID: <20030714075439.GA12561@jabber.org>
References: <3F125572.1090308@it.su.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F125572.1090308@it.su.se>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Jul 14, 2003 at 09:02:10AM +0200, Leif Johansson wrote:
> It would be nice to be able to speak ssl to the conference server...

True. Server-to-server TLS is part of the XMPP specs (where XMPP is an
IETF adaptation of the Jabber protocol), but existing implementations
have not yet been updated to reflect the more robust security of the
XMPP specifications. Expect implementations and deployments in the
coming months (perhaps by the time of the Minneapolis meeting).

Peter




From owner-ietf@ietf.org  Mon Jul 14 04:40: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 EAA02034
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 04:40:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19bylV-0008U9-Fg
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 04:32:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19bylP-0008Sz-VX
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 04:32: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 EAA01711
	for <ietf@ietf.org>; Mon, 14 Jul 2003 04:32:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19bylN-0002nj-00
	for ietf@ietf.org; Mon, 14 Jul 2003 04:32:49 -0400
Received: from [81.160.209.90] (helo=garlic.apnic.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19bylM-0002ng-00
	for ietf@ietf.org; Mon, 14 Jul 2003 04:32:48 -0400
Received: from garlic.apnic.net (localhost [127.0.0.1])
	by garlic.apnic.net (8.12.9/8.12.9) with ESMTP id h6E8WcYt003067
	for <ietf@ietf.org>; Mon, 14 Jul 2003 18:32:38 +1000 (EST)
Received: (from ggm@localhost)
	by garlic.apnic.net (8.12.9/8.12.9/Submit) id h6E8WcsA002361;
	Mon, 14 Jul 2003 18:32:38 +1000 (EST)
Date: Mon, 14 Jul 2003 18:32:37 +1000
From: George Michaelson <ggm@apnic.net>
To: ietf@ietf.org
Subject: IETF jabber howto pointers please?
Message-Id: <20030714183237.01dd4c16.ggm@apnic.net>
In-Reply-To: <20030714075439.GA12561@jabber.org>
References: <3F125572.1090308@it.su.se>
	<20030714075439.GA12561@jabber.org>
Organization: APNIC Pty Ltd
X-Mailer: Sylpheed version 0.9.0claws84 (GTK+ 1.2.10; i386-pc-netbsdelf1.6U)
X-Fruit-Of-The-Month-Club: persimmon
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


Could somebody re-post a pointer to the canonical 'IETF jabber' howto please?

the various archived documents seem to be a twisty maze. the archives for
sessions I found were for March, nothing current.

-George



From owner-ietf@ietf.org  Mon Jul 14 05:53: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 FAA04224
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 05:53:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19bzqS-0001mi-27
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 05:42:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19bzpA-0001lR-CV
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 05:40: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 FAA03965
	for <ietf@ietf.org>; Mon, 14 Jul 2003 05:40:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19bzp7-0003Na-00
	for ietf@ietf.org; Mon, 14 Jul 2003 05:40:45 -0400
Received: from [208.245.212.109] (helo=hades.jabber.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19bzp6-0003NX-00
	for ietf@ietf.org; Mon, 14 Jul 2003 05:40:45 -0400
Received: by hades.jabber.org (Postfix, from userid 1005)
	id E1B2463EE7; Mon, 14 Jul 2003 04:40:44 -0500 (CDT)
Date: Mon, 14 Jul 2003 04:40:44 -0500
From: Peter Saint-Andre <stpeter@jabber.org>
To: George Michaelson <ggm@apnic.net>
Cc: ietf@ietf.org
Subject: Re: IETF jabber howto pointers please?
Message-ID: <20030714094044.GA16642@jabber.org>
References: <3F125572.1090308@it.su.se> <20030714075439.GA12561@jabber.org> <20030714183237.01dd4c16.ggm@apnic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030714183237.01dd4c16.ggm@apnic.net>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Jul 14, 2003 at 06:32:37PM +1000, George Michaelson wrote:

> Could somebody re-post a pointer to the canonical 'IETF jabber' howto please?

http://www.jabber.org/ietf/chat.php

I've just updated it to reflect the fact that hosting for the text
conferencing service is in Vienna this time.

Peter




From owner-ietf@ietf.org  Mon Jul 14 07:20: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 HAA09637
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 07:20:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19c1BV-0003U4-FB
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 07:07:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19c1A6-0003Sz-Me
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 07: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 HAA08322
	for <ietf@ietf.org>; Mon, 14 Jul 2003 07:06:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c1A4-0004eO-00
	for ietf@ietf.org; Mon, 14 Jul 2003 07:06:28 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c1A3-0004dh-00
	for ietf@ietf.org; Mon, 14 Jul 2003 07:06:27 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h6EB5vV31107
	for <ietf@ietf.org>; Mon, 14 Jul 2003 14:05:57 +0300
Date: Mon, 14 Jul 2003 14:05:56 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: Kill 6to4/site-locals from the IETF57 WLAN please.
Message-ID: <Pine.LNX.4.44.0307141404380.31100-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

Someone(s) in IETF57 WLAN appear to advertise site-locals and 6to4 
addresses.  Please stop.

]# /sbin/ip -6 a l
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue 
    inet6 ::1/128 scope host 
4: eth1: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast 
qlen 100
    inet6 fec0::4:260:1dff:fef0:2fa9/64 scope site dynamic 
       valid_lft 172789sec preferred_lft 1789sec
    inet6 fe80::260:1dff:fef0:2fa9/64 scope link 
    inet6 2002:51a0:da47:4:260:1dff:fef0:2fa9/64 scope global dynamic 
       valid_lft 172789sec preferred_lft 1789sec
    inet6 2001:7f9:8400:10:260:1dff:fef0:2fa9/64 scope global dynamic 
       valid_lft 2591989sec preferred_lft 604789sec

-- 
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  Mon Jul 14 08:10: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 IAA14335
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 08:10:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19c24e-0005GA-Es
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 08:04:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19c24C-0005F5-Cw
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 08:04: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 IAA14033
	for <ietf@ietf.org>; Mon, 14 Jul 2003 08:04:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c24B-00069I-00
	for ietf@ietf.org; Mon, 14 Jul 2003 08:04:27 -0400
Received: from [81.160.179.149] (helo=drakken.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19c24A-000698-00
	for ietf@ietf.org; Mon, 14 Jul 2003 08:04:26 -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 h6EC4Cjp001708;
	Mon, 14 Jul 2003 14:04:12 +0200 (CEST)
Date: Mon, 14 Jul 2003 14:04:12 +0200
From: Marshall Rose <mrose@dbc.mtview.ca.us>
To: George Michaelson <ggm@apnic.net>
Cc: ietf@ietf.org
Subject: Re: IETF jabber howto pointers please?
Message-Id: <20030714140412.3f0f578e.mrose@dbc.mtview.ca.us>
In-Reply-To: <20030714183237.01dd4c16.ggm@apnic.net>
References: <3F125572.1090308@it.su.se>
	<20030714075439.GA12561@jabber.org>
	<20030714183237.01dd4c16.ggm@apnic.net>
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

> Could somebody re-post a pointer to the canonical 'IETF jabber' howto
> please?
> 
> the various archived documents seem to be a twisty maze. the archives
> for sessions I found were for March, nothing current.

briefly: login to your jabber as usual

you will find conference rooms at ietf.jabber.at

try the "hallway" room first...

/mtr



From owner-ietf@ietf.org  Mon Jul 14 10:55: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 KAA26771
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 10:55:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19c4XW-0006Ys-Pc
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 10:42:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19c4Wy-0006Xr-Hg
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 10:42: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 KAA25575
	for <ietf@ietf.org>; Mon, 14 Jul 2003 10:42:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c4Wx-0000oF-00
	for ietf@ietf.org; Mon, 14 Jul 2003 10:42:19 -0400
Received: from [81.160.179.149] (helo=drakken.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19c4Ww-0000oB-00
	for ietf@ietf.org; Mon, 14 Jul 2003 10:42:18 -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 h6EEgF1c003124;
	Mon, 14 Jul 2003 16:42:15 +0200 (CEST)
Date: Mon, 14 Jul 2003 16:42:15 +0200
From: Marshall Rose <mrose@dbc.mtview.ca.us>
To: ietf@ietf.org
Subject: jabber at ietf57
Message-Id: <20030714164215.69f044b3.mrose@dbc.mtview.ca.us>
In-Reply-To: <20030714140412.3f0f578e.mrose@dbc.mtview.ca.us>
References: <3F125572.1090308@it.su.se>
	<20030714075439.GA12561@jabber.org>
	<20030714183237.01dd4c16.ggm@apnic.net>
	<20030714140412.3f0f578e.mrose@dbc.mtview.ca.us>
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

we had some server instability this afternoon... looks like it's
resolved now!

/mtr



From owner-ietf@ietf.org  Mon Jul 14 13:03: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 NAA04957
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 13:03:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19c6YM-0000Vo-KJ
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 12:51:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19b5b4-00071t-R3
	for ietf@asgard.ietf.org; Fri, 11 Jul 2003 17:38:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18415
	for <ietf@ietf.org>; Fri, 11 Jul 2003 17:38:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19b5b3-0002qr-00
	for ietf@ietf.org; Fri, 11 Jul 2003 17:38:29 -0400
Received: from minbar.fac.cs.cmu.edu ([128.2.185.161])
	by ietf-mx with smtp (Exim 4.12)
	id 19b5b2-0002ql-00
	for ietf@ietf.org; Fri, 11 Jul 2003 17:38:28 -0400
Received: from minbar.fac.cs.cmu.edu ([127.0.0.1]) by minbar.fac.cs.cmu.edu
          id aa12788; 11 Jul 2003 17:37 EDT
Date: Fri, 11 Jul 2003 17:37:43 -0400 (EDT)
From: Jeffrey Hutzelman <jhutz@cmu.edu>
X-X-Sender:  <jhutz@minbar.fac.cs.cmu.edu>
To: ietf@ietf.org
MMDF-Warning:  Parse error in original version of preceding line at minbar.fac.cs.cmu.edu
Subject: IETF PGP Key Signing Party - RESCHEDULED
Message-ID: <Pine.LNX.4.33L.0307111737160.29721-100000@minbar.fac.cs.cmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Greetings...  As has become traditional, we will be holding a PGP key
signing party at the IETF meeting next week in Vienna.  Ted Ts'o will
be unable to attend this IETF meeting, so I have agreed to organize
the session in his place.

Please note that because the IETF has rooms booked in the conference
center only until 22:00 each day, our usual Wednesday-night time slot
after the plenary was not available.  Instead, we will be holding the
event at the beginning of the dinner break on MONDAY, at 17:30.  Due
to the late change, the Secretariat has not yet told me what room we'll
be using; when I find out, I'll send an update and post the time on
the message board.

The rest of this text was generously donated by Ted Ts'o, modulo
some changes relating to the details.  The procedure we will use is
the following:

o People who wish to participate should email an ASCII extract of
  their PGP public key to <jhutz@cmu.edu> by noon on Monday, July
  14, 2003.  Please include a subject line of "IETF PGP KEY", and
  please DO NOT MIME-ENCRYPT your e-mail.  Send it to me as plain
  text, and do NOT base-64 encode things.  (I will be running the
  entire mail folder file through GPG, and PGP-keys that are base-64
  encoded will get ignored unless I take manual action to fix things.
  I will try do the manual fixup, but I make no guarantees about
  catching all of them.)

  The method of generating the ASCII extract under Unix is:

	pgp -kxa my_email_address mykey.asc		(pgp 2.6.2)
	pgpk -xa my_email_address > mykey.asc		(pgp 5.x)
	gpg --export -a my_email_address > mykey.asc	(gpg)

  If you're using Windows or Macintosh, hopefully it will be Intuitively
  Obvious (tm) using the GUI interface how to generate an ASCII armored
  key that begins "-----BEGIN PGP PUBLIC KEY BLOCK-----".

o By 4pm on Monday, you will be able to fetch the complete key ring
  from any of the following locations with all of the keys that were
  submitted:

        /afs/grand.central.org/project/ietf-pgp/ietf57.pgp
        http://grand.central.org/dl/ietf-pgp/ietf57.pgp
        ftp://grand.central.org/pub/ietf-pgp/ietf57.pgp

o At 5:30pm, come prepared with the PGP Key fingerprint of your PGP
  public key; we will have handouts with all of the key fingerprints of
  the keys that people have mailed in.

o In turn, readers at the front of the room will recite people's keys;
  as your key fingerprint is read, stand up, and at the end of reading
  of your PGP key fingerprint, acknowledge that the fingerprint as read
  was correct.

o Later that evening, or perhaps when you get home, you can sign the
  keys corresponding to the fingerprints which you were able to verify
  on the handout; note that it is advisable that you only sign keys of
  people when you have personal knowledge that the person who stood up
  during the reading of his/her fingerprint really is the person which
  he/she claimed to be.

o Submit the keys you have signed to the PGP keyservers.  A good one to
  use is the one at MIT: simply send mail containing the ascii armored
  version of your PGP public key to <pgp@pgp.mit.edu>.

Note that you don't have to have a laptop with you; if you don't have
any locally trusted computing resources during the key signing party,
you can make notes on the handout, and then take the handout home and
sign the keys later.

-- Jeffrey T. Hutzelman (N3NHS) <jhutz+@cmu.edu>
   Sr. Research Systems Programmer
   School of Computer Science - Research Computing Facility
   Carnegie Mellon University - Pittsburgh, PA






From owner-ietf@ietf.org  Mon Jul 14 13:10: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 NAA05850
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 13:10:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19c6lx-0001GF-9R
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 13:05:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19c6lk-0001CW-D4
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 13:05: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 NAA05353
	for <ietf@ietf.org>; Mon, 14 Jul 2003 13:05:40 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c6li-0003Ds-00
	for ietf@ietf.org; Mon, 14 Jul 2003 13:05:42 -0400
Received: from h80ad26b1.async.vt.edu ([128.173.38.177] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19c6le-0003DO-00
	for ietf@ietf.org; Mon, 14 Jul 2003 13:05:40 -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 h6EH5YMQ028534;
	Mon, 14 Jul 2003 13:05:34 -0400
Message-Id: <200307141705.h6EH5YMQ028534@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: Much Regreted 
In-Reply-To: Your message of "Sun, 13 Jul 2003 21:13:46 PDT."
             <20030714041346.49394.qmail@web80601.mail.yahoo.com> 
References: <20030714041346.49394.qmail@web80601.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_2123095642P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 14 Jul 2003 13:05:33 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

(Answering 2 related mails)

On Sun, 13 Jul 2003 21:13:46 PDT, NM Research <nm_research@yahoo.com>  said:

> I feel that I have valid arguements against some current quantum coding,
> gates, qubits, etc.  I am more for a statiscally and AI approach rather than
> protocols.

On the other hand, the current coding/gates/qubits/etc has been demonstrating
actual success at several hundred kilometers distance.

You can argue "statistically and AI" all you want, but it's a tough argument against
working hardware...

You also seem to be *vastly* confused regarding protocols.  I fail to see how
you intend to have *any* functional product that doesn't implement a protocol.
A protocol is just an agreed-on method for doing things in a consistent order
known to produce a desired result.  Dialing a person's phone number correctly
is a protocol - get them in the right order, you reach the person you wanted,
do it wrong and if you're lucky, you'll get the "Your call cannot be completed as
dialed" message...

Consider the following "breakfast protocol": "(1) Take 3 eggs. (2) Break eggs
into bowl, discarding shells. (3) Beat eggs. (4) Heat frying pan over burner.
(5) Pour eggs into pan, stir occasionally. (6) When done, turn off burner, and
put eggs on plate (7) Eat".  That's a protocol for making scrambled eggs.  Now
statistically, I could say there's 7! ways to order these steps, of which some
very small number produce edible eggs, and some orderings are merely icky
(forgetting to discard the shells, or failing to turn on the burner, for
instance), while some are hazardous (failing to get the pan onto the burner
before pouring the eggs onto the burner, or failing to turn off the burner).

Most people prefer to follow the kitchen protocols because they know what to
expect when they finish.  A very small number of people experiment with the
kitchen protocols - this requires deep understanding of why the protocols are
the way they are, and the ability to predict what protocols are destined for
success or failure.  I suppose we COULD call these people "kitchen protocol
designers", but most people just call them chefs....

Now you're quite welcome to design a statistical cell phone.  I suspect that most
people want a nice predictable workable one that follows a protocol of some sort.

> Furthermore with wavelength, frequency and polarity you could assign
> each and every word a place/bit.  If the IETF is not carefully something will
> come a long that will kill them like fidonet.  It is not remote : IPv6 and
> Internet 2 may be still born.

Not really.  All the IETF needs to do is write a "IP over FOO" document and
we're done. ;)  You're confusing the distinction between link-level transport
and what most end users actually care about - application-to-application
communication. IPv6 and Internet2 don't *care* about what medium they're
running over - there's no technical reason to prohibit avian-based IPv6 a la
RFC1149, or IPv6 over telepathy. And end users don't usually know or care -
they launch their e-mail software, and their mail moves from their mail server
to their client.

On Sun, 13 Jul 2003 23:13:34 -0700, NM Research <nm_research@yahoo.com> said:
> About the  feasibility of 4g systems.  I feel that they have a bright future,
> if and only if the human understanding of the particulate nature of
> electromagnetic radiation is not enhanced to the level of manipulation and
> usage, and remains primitive as it current exists.

I would recommend that you go back and re-read the famous double-slit
experiment until *you* understand EM radiation's particulate nature - or lack
thereof.  And to avoid being called a crank, please remember that the current
"primitive" EM and QM theory has been *highly* successful, and unless your
"enhanced" theory does a BETTER job of explaining things, it won't be taken
seriously.  Quick sanity check for your theory:  Use it to compute the thermal
noise emitted by a reverse-biased zener diode.  If it doesn't get it right,
figure out why.  If you don't understand why I picked that, you're in *WAY*
over your head...

There's little to no evidence for an imminent breakthrough in our
understanding. And even if somebody had such a break-through *TODAY*, you're
still looking at several *decades* before we have any real fallout.  For
example, look at when Einstein did his work on the photoelectric effect (1905)
- this had hints that lasers were possible (I have to admit not remembering if
that paper predicted photon cascading, or what later paper did so).  The first
laser actually came around in the 1950s.  And when did we actually see
widespread deployment of surgical lasers and LED lasers for fiberoptic use?

I think it's safe to assume that the market will choose a 4G device available NOW
rather than wait 20 years for a quantum device.....

> If organizations like CERN can manage to manipulate em-radiation
> communications at quantum level, then there will be quantum wireless
> communications.  With Wifi already in the market, 3g, 4g will be a sure flop if
> such an innovation comes.
 
Oh my, *such* a confusion of ideas here.

Let's look at what CERN does:

*  They spend *tens of millions* of dollars.

* *very high* energies - major drain on the power grid when running

* All the action happens in several cubic meters

* millions of events (data rates approacing terabytes per second here)

* If a researcher finds ONE or TWO events out of the millions, he gets a Nobel.

Consumer technology:

* Has to be *cheap* - $49 or "free with 2-year service contract" phones....

* low power (we're talking a cell phone battery here - the use of something
other than standard radio waves doesn't change the fact that there's a certain
upper limit to what a safe chemical battery can store per kilogram - and if
you're positing a cheap and safe sub-kilogram nuclear/fusion/whatever power
source, the societal implications of THAT far outweigh quantum communications)

* People want to be able to call more than a few meters

* they don't like making dozens of phone calls before they get the right person.

For another data point, I suggest you read Eric Drexler's "Engines of Creation",
look at the date that was published, look at the *current* state of nanotechnology,
and remember that nanotech does *NOT* involve any conceptual breakthroughs,
it's *all* engineering.

Then ask yourself why you're convinced that the IETF needs to worry about
world-wide point-to-point QM communications (check that power budget again ;)
anytime soon?

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

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

iD8DBQE/EuLdcC3lWbTT17ARAi7fAJ90Rd5RLddxdkPElhoHLUL0EN8RnQCffXYz
OOwEB1Q80Te0q9X4OZZyNaU=
=hBZn
-----END PGP SIGNATURE-----

--==_Exmh_2123095642P--



From owner-ietf@ietf.org  Mon Jul 14 13:25: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 NAA06439
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 13:25:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19c6zU-00024z-8k
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 13:19:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19c6z4-00023o-TT
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 13:19: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 NAA06247
	for <ietf@ietf.org>; Mon, 14 Jul 2003 13:19:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c6z3-0003RH-00
	for ietf@ietf.org; Mon, 14 Jul 2003 13:19:29 -0400
Received: from natint.juniper.net ([207.17.136.129] helo=merlot.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19c6z3-0003RD-00
	for ietf@ietf.org; Mon, 14 Jul 2003 13:19:29 -0400
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h6EHIHu84333;
	Mon, 14 Jul 2003 10:18:17 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200307141718.h6EHIHu84333@merlot.juniper.net>
To: Alex Zinin <zinin@psg.com>
cc: Eric Rosen <erosen@cisco.com>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: The requirements cycle 
In-Reply-To: Your message of "Mon, 07 Jul 2003 16:41:30 PDT."
             <105670879814.20030707164130@psg.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18515.1058203097.1@juniper.net>
Date: Mon, 14 Jul 2003 10:18:17 -0700
From: Yakov Rekhter <yakov@juniper.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

Alex,

> Eric,
> 
>   Looking at this from the high-level perspective...
> 
>   Though I became the responsible AD for PPVPN just recently, I was
>   exposed to certain aspects of interaction between ADs are PPVPN WG
>   chairs. There was clearly a communication problem there. I believe
>   it's been solved and we are in a much better shape now. Trying to
>   investigate who said what and whose fault that was in the past will
>   not be pretty, so I suggest we don't go there. 

I suggest we *do* go there (irrespective of whether it will, or
will not be pretty), as doing this could help us to understand the
mistakes that have been made. And unless we do understand these
mistakes, we are (very) likely to repeat them.

Yakov.



From owner-ietf@ietf.org  Mon Jul 14 13:35: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 NAA07307
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 13:35:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19c7A6-0002fF-Dk
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 13:30:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19c77z-0002cC-Lp
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 13:28: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 NAA06861
	for <ietf@ietf.org>; Mon, 14 Jul 2003 13:28:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c77y-0003bJ-00
	for ietf@ietf.org; Mon, 14 Jul 2003 13:28:42 -0400
Received: from balan.ap.univie.ac.at ([131.130.11.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c77x-0003bG-00
	for ietf@ietf.org; Mon, 14 Jul 2003 13:28:41 -0400
Received: from univie.ac.at (localhost [127.0.0.1])
	by balan.ap.univie.ac.at (8.12.8/8.11.1/0.0.0) with ESMTP id h6EHSc7m646194;
	Mon, 14 Jul 2003 19:28:38 +0200 (CEST)
Message-ID: <3F12E846.7060807@univie.ac.at>
Date: Mon, 14 Jul 2003 19:28:38 +0200
From: Ulrich Kiermayr <ulrich.kiermayr@univie.ac.at>
Organization: Vienna University Computer Center
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701
X-Accept-Language: en-us, en, de-at
MIME-Version: 1.0
To: Jeffrey Hutzelman <jhutz@cmu.edu>
CC: ietf@ietf.org
Subject: Re: IETF PGP Key Signing Party - RESCHEDULED
References: <Pine.LNX.4.33L.0307111737160.29721-100000@minbar.fac.cs.cmu.edu>
In-Reply-To: <Pine.LNX.4.33L.0307111737160.29721-100000@minbar.fac.cs.cmu.edu>
X-Enigmail-Version: 0.75.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

Jeffrey Hutzelman wrote:
> Greetings...  As has become traditional, we will be holding a PGP key
> signing party at the IETF meeting next week in Vienna.  Ted Ts'o will
> be unable to attend this IETF meeting, so I have agreed to organize
> the session in his place.
> 
> Please note that because the IETF has rooms booked in the conference
> center only until 22:00 each day, our usual Wednesday-night time slot
> after the plenary was not available.  Instead, we will be holding the
> event at the beginning of the dinner break on MONDAY, at 17:30.  Due
> to the late change, the Secretariat has not yet told me what room we'll
> be using; when I find out, I'll send an update and post the time on
> the message board.

Hmmmm, that was not very helpful, since majordomo sent out the mail @

Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by mailbox.univie.ac.at (8.12.2/8.12.2) with ESMTP id h6EH5xoQ072474
	for <ulrich.kiermayr@univie.ac.at>; Mon, 14 Jul 2003 19:06:17 +0200

was this just with my email address, or a server problem (i did get 
other mails from the ml during that time)?

lG uk
-- 
------------------------------------------------------------------------
Ulrich Kiermayr         Zentraler Informatikdienst der Universitaet Wien
Network Security              Universitaetsstrasse 7, 1010 Wien, Austria
------------------------------------------------------------------------
eMail:   ulrich.kiermayr@univie.ac.at          Tel: (+43 1) 4277 / 14104
Hotline: security.zid@univie.ac.at             Fax: (+43 1) 4277 /  9140
------------------------------------------------------------------------
GPG Key fingerprint = BF0D 5749 4DC1 ED74 AB67  7180 105F 491D A8D7 64D8





From owner-ietf@ietf.org  Mon Jul 14 13:41: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 NAA07683
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 13:41:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19c7Gs-00037q-D4
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 13:37:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19c7Es-0002uy-KM
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 13:35:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07360
	for <ietf@ietf.org>; Mon, 14 Jul 2003 13:35:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c7Em-0003jC-00
	for ietf@ietf.org; Mon, 14 Jul 2003 13:35:44 -0400
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19c7Em-0003j3-00
	for ietf@ietf.org; Mon, 14 Jul 2003 13:35:44 -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>;
          Mon, 14 Jul 2003 13:35:42 -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"
X-Priority: 2 (High)
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: That's *really* new!
Date: Mon, 14 Jul 2003 13:35:42 -0400
Message-ID: <20030714173542532.AAA425@hq.lindsayelec.com@rflooker1>
Sender: owner-ietf@ietf.org
Precedence: bulk


Valdis.Kletnieks@vt.edu wrote:
>"...IPv6 over telepathy"

Dan says:
Wow! I had that idea yesterday; (It's almost like you where reading my mind) !!!

Scoundrel!






From owner-ietf@ietf.org  Mon Jul 14 13:51: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 NAA04959
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 13:03:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19c6YM-0000Vu-Og
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 12:51:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19b9Tr-0006rh-1Q
	for ietf@asgard.ietf.org; Fri, 11 Jul 2003 21:47: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 VAA00528
	for <ietf@ietf.org>; Fri, 11 Jul 2003 21:47:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19b9Tp-0006Lm-00
	for ietf@ietf.org; Fri, 11 Jul 2003 21:47:17 -0400
Received: from [81.160.15.16] (helo=drakken.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19b9To-0006Lh-00
	for ietf@ietf.org; Fri, 11 Jul 2003 21:47:16 -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 h6C1lBF4001470;
	Fri, 11 Jul 2003 18:47:11 -0700 (PDT)
Date: Fri, 11 Jul 2003 18:47:11 -0700
From: Marshall Rose <mrose+mtr.ietf@dbc.mtview.ca.us>
To: ietf@ietf.org
Subject: text conferencing at ietf57
Message-Id: <20030711184711.239f9273.mrose+mtr.ietf@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

	     Remote Access for the 57th IETF meeting in Vienna:
                             Text Conferencing

At each IETF meeting, two of the working group meeting rooms are equipped
for video multicast and remote participation.  That is, for every IETF
meeting slot, two of the working groups can see and hear the
meeting. For the 57th IETF, in *addition* to the usual network A/V, text
conferencing will be provided for every working group that meets.

All of the conference rooms will be hosted on

    ietf.jabber.at

and each is named using the official IETF abbreviation found in the
agenda (e.g., "apparea",  "dhc", "forces", and so on -- for all the
examples that follow, we'll use "foobar" as the abbreviation).

Each conference room also has a 'bot which records everything that gets
sent. So, the minute taker can review this information right after the
meeting.

In addition to the conference rooms for each wg that is meeting, there
are three others of general interest: bar, hallway, and plenary.
    

1. Before the meeting:

1.1. If you want to participate
    
If you don't already have one, get yourself a Jabber client, here are some
suggestions:

    platform    suggestion
    --------    ----------
    win32       http://exodus.jabberstudio.org
    'nix        http://gabber.sf.net
    macos       http://jabberfox.sf.net

When you start the client for the first time, it will eventually ask if
you want to register on a public server. Go ahead and do
that. 
    
If you want to find out more, instead of choosing these defaults, here
are pointers to some additional information:
    
    list of clients:    http://www.jabber.org/user/clientlist.php
              howto:    http://www.jabber.org/user/userguide/
        server list:    http://www.jabber.org/user/publicservers.php

To make sure everything is running ok, do a "Join Group Chat" with your
Jabber client:
    
    Group/Room: hallway
    Server:     ietf.jabber.at

This conference room is up and running right now (although probably no
one will be in it when you connect).
    
1.2. What the Chair does
    
If you want to make text conferencing available, you'll need to have a
volunteer scribe in the meeting room. The scribe will be typing in a
running commentary as to what's going on in the room (who's presenting,
what question is being asked, etc.)
    
So, why not send an email out on the mailing list now, before the
meeting, to ask for volunteers?
    
    
2. At the meeting

2.1. What the Chair does

When a session starts, the chair asks if someone in the room is willing
to act as "scribe". If no one volunteers, read no further, we're done!

Otherwise, the scribe should do a "Join Group Chat" with their Jabber
client, e.g.,

    Group/Room: foobar
    Server:     ietf.jabber.at


2.2. What the Scribe does

The scribe types in a running commentary as to what's going on in the
room. For example, if a speaker makes a presentation, the scribe types
in the URL for the presentation (more on this in a bit).

Simlarly, during question time, a remote participant can type a question
into the room and the scribe can pass it on to the speaker.


2.3. What each Presenter does

Each presenter should put a copy of their presentation on a web server
somewhere, so remote participants can follow along. 
    

2.4. Where to find the conference log
    
    http://ietf.jabber.at/logs/
    
                                  #######





From owner-ietf@ietf.org  Mon Jul 14 14:14: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 OAA10154
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 14:14:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19c7ju-0004Mu-Dl
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 14:07:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19c7jC-0004LQ-Sw
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 14:07: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 OAA09535
	for <ietf@ietf.org>; Mon, 14 Jul 2003 14:07:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c7jB-0004GB-00
	for ietf@ietf.org; Mon, 14 Jul 2003 14:07:09 -0400
Received: from citadel.cequrux.com ([192.96.22.18])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c7jA-0004G5-00
	for ietf@ietf.org; Mon, 14 Jul 2003 14:07:08 -0400
Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id UAA21913; Mon, 14 Jul 2003 20:06:54 +0200 (SAST)
Received: by citadel.cequrux.com via recvmail id 21899; Mon, 14 Jul 2003 20:06:28 +0200 (SAST)
Date: Mon, 14 Jul 2003 20:06:26 +0200
From: Alan Barrett <apb@cequrux.com>
To: Peter Saint-Andre <stpeter@jabber.org>
Cc: ietf@ietf.org
Subject: Re: IETF jabber howto pointers please?
Message-ID: <20030714180626.GC17486@apb.cequrux.com>
References: <3F125572.1090308@it.su.se> <20030714075439.GA12561@jabber.org> <20030714183237.01dd4c16.ggm@apnic.net> <20030714094044.GA16642@jabber.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030714094044.GA16642@jabber.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 14 Jul 2003, Peter Saint-Andre wrote:
> > Could somebody re-post a pointer to the canonical 'IETF jabber'
> > howto please?
> http://www.jabber.org/ietf/chat.php

Two questions:

1) Are there any open-source text-based clients that actually work?
   I prefer not to have to use a graphical environment to view text, and
   I couldn't get sjabber to work.

2) Jabber, Inc. (jabber.com) are spammers, and I would not want to
   support them in any way.  It appears that "Jabber" is a trademark
   owned by the spammers, and this bothers me.  Does jabber.org have a
   position on spam?

--apb (Alan Barrett)



From owner-ietf@ietf.org  Mon Jul 14 14: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 OAA10166
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 14:15:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19c7hy-0004K4-A7
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 14:05:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19c7hG-0004Im-Np
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 14:05: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 OAA09466
	for <ietf@ietf.org>; Mon, 14 Jul 2003 14:05:09 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c7hF-0004FQ-00
	for ietf@ietf.org; Mon, 14 Jul 2003 14:05:09 -0400
Received: from h80ad26b1.async.vt.edu ([128.173.38.177] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19c7hE-0004FN-00
	for ietf@ietf.org; Mon, 14 Jul 2003 14:05:08 -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 h6EI4tMQ029537;
	Mon, 14 Jul 2003 14:04:55 -0400
Message-Id: <200307141804.h6EI4tMQ029537@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: dank@hq.lindsayelec.com (Dan Kolis)
Cc: ietf@ietf.org
Subject: Re: That's *really* new! 
In-Reply-To: Your message of "Mon, 14 Jul 2003 13:35:42 EDT."
             <20030714173542532.AAA425%hq.lindsayelec.com@rflooker1> 
References: <20030714173542532.AAA425%hq.lindsayelec.com@rflooker1>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1917054850P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 14 Jul 2003 14:04:55 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 14 Jul 2003 13:35:42 EDT, dank@hq.lindsayelec.com (Dan Kolis)  said:
> 
> Valdis.Kletnieks@vt.edu wrote:
> >"...IPv6 over telepathy"
> 
> Dan says:
> Wow! I had that idea yesterday; (It's almost like you where reading my mind) 
!!!

The draft for IPv6 over telepathy strongly recommends the use of IPSEC in
multi-hop configurations, for all the obvious data-interception and data-injection
reasons..... 

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

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

iD8DBQE/EvDHcC3lWbTT17ARArY/AKDK4cfIOx955HK0Zqsh/qOs9mOLJwCfX8wN
qhiBHGXUIxqxjyoF+MWQlC4=
=Xyjs
-----END PGP SIGNATURE-----

--==_Exmh_-1917054850P--



From owner-ietf@ietf.org  Mon Jul 14 14:23: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 OAA11278
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Jul 2003 14:23:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19c7sd-00055m-1Q
	for ietf-list@asgard.ietf.org; Mon, 14 Jul 2003 14:16:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19c7sT-00051N-2v
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 14:16:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10557
	for <ietf@ietf.org>; Mon, 14 Jul 2003 14:16:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c7sS-0004XS-00
	for ietf@ietf.org; Mon, 14 Jul 2003 14:16:44 -0400
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19c7sR-0004XJ-00
	for ietf@ietf.org; Mon, 14 Jul 2003 14:16:43 -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>;
          Mon, 14 Jul 2003 14:16:42 -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"
X-Priority: 2 (High)
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: Innovations in protocols
Date: Mon, 14 Jul 2003 14:16:42 -0400
Message-ID: <20030714181642103.AAA350@hq.lindsayelec.com@rflooker1>
Sender: owner-ietf@ietf.org
Precedence: bulk

>On Mon, 14 Jul 2003 13:35:42 EDT, dank@hq.lindsayelec.com (Dan Kolis)  said:
>> Valdis.Kletnieks@vt.edu wrote:
>> >"...IPv6 over telepathy"
>> Dan says:
>> Wow! I had that idea yesterday; (It's almost like you where reading my mind) 
>!!!
>The draft for IPv6 over telepathy strongly recommends the use of IPSEC in
>multi-hop configurations, for all the obvious data-interception and
data-injection
>reasons..... 

Also useful for all TCP/IP; (Telepathy Control Protocol / Intra-Polergeist)
messaging. Not required for UDP (Uber Daemon Protocol) though.








From owner-ietf@ietf.org  Tue Jul 15 01:14: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 BAA04511
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 01:14:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cHp0-0000Wo-Mx
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 00:53:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cHoe-0000UA-B2
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 00:53: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 AAA02440;
	Tue, 15 Jul 2003 00:53:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cHob-0001NZ-00; Tue, 15 Jul 2003 00:53:25 -0400
Received: from coconut.itojun.org ([219.101.47.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cHoa-0001NW-00; Tue, 15 Jul 2003 00:53:24 -0400
Received: from itojun.org (localhost [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP
	id 7210B13; Tue, 15 Jul 2003 13:53:22 +0900 (JST)
To: Mark Handley <M.Handley@cs.ucl.ac.uk>
Cc: iab@ietf.org, ietf@ietf.org
In-reply-to: M.Handley's message of Mon, 14 Jul 2003 20:39:41 +0100.  <885.1058211581@eve.cs.ucl.ac.uk> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: Multicast Last Mile BOF report 
From: itojun@iijlab.net
Date: Tue, 15 Jul 2003 13:53:22 +0900
Message-Id: <20030715045322.7210B13@coconut.itojun.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

>There are a number of concerns, including security, potential for
>using this for DoS, and whether there's a business model for the
>replicator.  Much of the discussion ratholed on whether there's a
>business model, and to what extent this works around existing ISP's
>business models.

	my guess is that DoS/abuse possibility is very similar to that of
	6to4 relay routers, or even worse (as multicast-last-mile creates
	state while 6to4 relay router does not).

itojun



From owner-ietf@ietf.org  Tue Jul 15 02:33: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 CAA24405
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 02:33:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cJE6-000895-8q
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 02:23:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cJDw-00085n-Ce
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 02:23: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 CAA23106
	for <ietf@ietf.org>; Tue, 15 Jul 2003 02:23:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cJDt-0003dh-00
	for ietf@ietf.org; Tue, 15 Jul 2003 02:23:37 -0400
Received: from [208.245.212.109] (helo=hades.jabber.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cJDs-0003dc-00
	for ietf@ietf.org; Tue, 15 Jul 2003 02:23:36 -0400
Received: by hades.jabber.org (Postfix, from userid 1005)
	id BCF9363EDF; Tue, 15 Jul 2003 01:23:37 -0500 (CDT)
Date: Tue, 15 Jul 2003 01:23:37 -0500
From: Peter Saint-Andre <stpeter@jabber.org>
To: Alan Barrett <apb@cequrux.com>
Cc: ietf@ietf.org
Subject: Re: IETF jabber howto pointers please?
Message-ID: <20030715062337.GC12886@jabber.org>
References: <3F125572.1090308@it.su.se> <20030714075439.GA12561@jabber.org> <20030714183237.01dd4c16.ggm@apnic.net> <20030714094044.GA16642@jabber.org> <20030714180626.GC17486@apb.cequrux.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030714180626.GC17486@apb.cequrux.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Jul 14, 2003 at 08:06:26PM +0200, Alan Barrett wrote:

> 1) Are there any open-source text-based clients that actually work?
>    I prefer not to have to use a graphical environment to view text, and
>    I couldn't get sjabber to work.

There is no really good text-based client. You might try Jarl, a client
written in Perl that contains a CLI mode. Other options are IMcom and
JabberX. Work is definitely needed in this area.

> 2) Jabber, Inc. (jabber.com) are spammers, and I would not want to
>    support them in any way.  It appears that "Jabber" is a trademark
>    owned by the spammers, and this bothers me.  Does jabber.org have a
>    position on spam?

The Jabber Software Foundation (JSF), which provides a central hub at 
jabber.org for Jabber developers and the network of Jabber servers and 
users, is 100% opposed to spam and has worked hard to ensure that spam 
is extremely difficult (it's always dangerous to say impossible) over 
Jabber/XMPP. The "Jabber" trademark is indeed owned by Jabber, Inc. but 
is currently being transferred to the JSF (it was purchased from its 
previous owner, Oquirrh Technologies, by the parent company of Jabber, 
Inc. in order to prevent potential liabilities early in the development 
of the open-source Jabber developer community, which predated Jabber, 
Inc.); that transfer is not yet complete, but work is proceeding. The 
JSF is a non-profit membership organization but has several sponsoring 
companies, one of which is Jabber, Inc.; while we have no control over 
our sponsors, as executive director of the JSF I will work to persuade 
any sponsoring company that sends unsoliticed bulk email to cease and 
desist.

Feel free to contact me via email or jabber at <stpeter@jabber.org> if
you would like to discuss this further.

Peter

-- 
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.php




From owner-ietf@ietf.org  Tue Jul 15 02:45: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 CAA25584
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 02:45:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cJVW-0006ib-53
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 02:41:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cJUX-0006gm-TM
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 02:40: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 CAA25160;
	Tue, 15 Jul 2003 02:40:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cJUV-00046A-00; Tue, 15 Jul 2003 02:40:47 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cJUU-00044x-00; Tue, 15 Jul 2003 02:40:46 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h6F6e9t07829;
	Tue, 15 Jul 2003 09:40:10 +0300
Date: Tue, 15 Jul 2003 09:40:09 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: itojun@iijlab.net
cc: Mark Handley <M.Handley@cs.ucl.ac.uk>, <iab@ietf.org>, <ietf@ietf.org>
Subject: Re: Multicast Last Mile BOF report 
In-Reply-To: <20030715045322.7210B13@coconut.itojun.org>
Message-ID: <Pine.LNX.4.44.0307150938440.7800-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 15 Jul 2003 itojun@iijlab.net wrote:
> >There are a number of concerns, including security, potential for
> >using this for DoS, and whether there's a business model for the
> >replicator.  Much of the discussion ratholed on whether there's a
> >business model, and to what extent this works around existing ISP's
> >business models.
> 
> 	my guess is that DoS/abuse possibility is very similar to that of
> 	6to4 relay routers, or even worse (as multicast-last-mile creates
> 	state while 6to4 relay router does not).

However, note that *IF* there's already an accepted premise of state, it
might be slightly easier to secure.  With 6to4 relay routers, the
statelessness is the thing which is simultaneously the bug and the
feature.

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




From owner-ietf@ietf.org  Tue Jul 15 03:35: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 DAA29089
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 03:35:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cKC5-0002D9-Gs
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 03:25:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cKBq-0002Bv-Ku
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 03: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 DAA28549
	for <ietf@ietf.org>; Tue, 15 Jul 2003 03:25:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cKBo-0004xZ-00
	for ietf@ietf.org; Tue, 15 Jul 2003 03:25:32 -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 19cKBm-0004xN-00
	for ietf@ietf.org; Tue, 15 Jul 2003 03:25:30 -0400
Received: from sandelman.ottawa.on.ca ([2002:51a0:4ed::1])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p2/8.11.6) with ESMTP id h6F7PIW13162
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK)
	for <ietf@ietf.org>; Tue, 15 Jul 2003 03:25:20 -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 h6F7PHd6002473
	for <ietf@ietf.org>; Tue, 15 Jul 2003 09:25:18 +0200
To: ietf@ietf.org
Subject: Re: text conferencing at ietf57 
In-reply-to: Your message of "Fri, 11 Jul 2003 18:47:11 PDT."
             <20030711184711.239f9273.mrose+mtr.ietf@dbc.mtview.ca.us> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 15 Jul 2003 09:25:17 +0200
Message-ID: <2472.1058253917@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-ietf@ietf.org
Precedence: bulk

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


I am using gabber from Debian.
Version 0.8.7.

I get SSL errors when I have it on, and connection errors when I turn it off.

If there is a gabber expert who'd like to aid me, find me, or look for
"Aharonov" on irc.freenode.net.

]                   At IETF57 in Wien, Austria                  |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] printk("Just another Debian GNU/Linux using, kernel hacking, security guy");[

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBPxOsW4qHRg3pndX9AQHksAP9FPmLENG5sLOOVQ82WiioNelyyPGPjWwY
IgBMH56WymeY5kdEsrzvF4ZlEm5G9lzq/nVJDnaQ6WeCZtizh0WR+VtPJrrlbzQr
m3E07puG8d7wB2zQz4xawW1K52Ksj+L++j//+90IKmkfXLgiKKUORCU2gNjBWXZT
KUAZ7O/q8V4=
=1JFZ
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Tue Jul 15 03:35: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 DAA29105
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 03:35:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cKFx-0002G1-Gl
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 03:29:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cKC9-0002DM-17
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 03:25: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 DAA28581
	for <ietf@ietf.org>; Tue, 15 Jul 2003 03:25:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cKC6-0004y4-00
	for ietf@ietf.org; Tue, 15 Jul 2003 03:25:50 -0400
Received: from [64.254.114.115] (helo=megisto-sql1.megisto.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cKC6-0004xM-00
	for ietf@ietf.org; Tue, 15 Jul 2003 03:25:50 -0400
Received: by megisto-sql1 with Internet Mail Service (5.5.2653.19)
	id <3XTK9M6M>; Tue, 15 Jul 2003 03:16:11 -0400
Message-ID: <C3F7A1AD0781F84784B5528466CA09DD013A5293@megisto-sql1>
From: Phil Roberts <PRoberts@MEGISTO.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: New Internet AD
Date: Tue, 15 Jul 2003 03:16:06 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C34AA0.F4EB25E0"
Sender: owner-ietf@ietf.org
Precedence: bulk

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

------_=_NextPart_001_01C34AA0.F4EB25E0
Content-Type: text/plain


The nomcom is pleased to announce that it has selected Margaret Wasserman
to fill the mid-term vacancy in the Internet Area.
 
Thanks are due again to many folks.  First thanks are due to
all of those who volunteered to serve on the nomcom, and especially
to those who were randomly selected and served as voting members
of the nomcom.  They contributed considerable time from their busy
schedules to participate in weekly calls, to conduct interviews, to
read questionnaires, and to make the selection of candidates.
 
Thanks to those in the community who volunteered to serve in this role,
both to those who were selected and those not chosen this
time around.  Thanks very much for completing the questionnaires, and
participating in interviews.
 
Thanks are also due to the IETF as a whole for providing input to the
process through nominations, recommendations, and feedback on
potential candidates.
 
The voting members of the nomcom are:
Edward Lewis
Alec Brusilovsky
Michael Richardson
Eva Jonsson
Stephen Trowbridge
Frank Alfano
Thomas Kurien
Dennis Beard
Richard Draves
Eva Gustafsson
 
The nonvoting members are:
Phil Roberts - chair
Allison Mankin - IESG liaison
Eric Rescorla - IAB liaison
Ted Ts'o - past chair


------_=_NextPart_001_01C34AA0.F4EB25E0
Content-Type: text/html

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

<META content="MSHTML 6.00.2722.900" name=GENERATOR></HEAD>
<BODY>
<DIV><BR><FONT face=Arial><FONT size=2>The nomcom is pleased to announce that it 
has selected Margaret Wasserman<BR>to fill the mid-term vacancy&nbsp;<SPAN 
class=431462107-15072003>in the Internet Area.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Thanks are due again to many folks.&nbsp; First 
thanks are due to<BR>all of those who volunteered to serve on the nomcom, and 
especially<BR>to those who were randomly selected and served as voting 
members<BR>of the nomcom.&nbsp; They contributed considerable time from their 
busy<BR>schedules to participate in weekly calls, to conduct interviews, 
to<BR>read questionnaires, and to make the selection of candidates.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Thanks to those in the community who volunteered to 
serve in this role,<BR>both to those who were selected and those not chosen 
this<BR>time around.&nbsp; Thanks very much for completing the questionnaires, 
and<BR>participating in interviews.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Thanks are also due to the IETF as a whole for 
providing input to the<BR>process through nominations, recommendations, and 
feedback on<BR>potential candidates.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>The voting members of the nomcom are:<BR>Edward 
Lewis<BR>Alec Brusilovsky<BR>Michael Richardson<BR>Eva Jonsson<BR>Stephen 
Trowbridge<BR>Frank Alfano<BR>Thomas Kurien<BR>Dennis Beard<BR>Richard 
Draves<BR>Eva Gustafsson</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>The nonvoting members are:<BR>Phil Roberts - 
chair<BR>Allison Mankin - IESG liaison<BR>Eric Rescorla - IAB liaison<BR>Ted 
Ts'o - past chair<BR></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C34AA0.F4EB25E0--



From owner-ietf@ietf.org  Tue Jul 15 05:33: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 FAA10208
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 05:33:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cM3E-0005RF-KU
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 05:24:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cM2s-0005QK-T2
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 05:24: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 FAA09216
	for <ietf@ietf.org>; Tue, 15 Jul 2003 05:24:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cM2q-0007aE-00
	for ietf@ietf.org; Tue, 15 Jul 2003 05:24:24 -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 19cM2p-0007aA-00
	for ietf@ietf.org; Tue, 15 Jul 2003 05:24:23 -0400
Received: from sandelman.ottawa.on.ca ([2002:51a0:4ed::1])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p2/8.11.6) with ESMTP id h6F9OHW14290
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK)
	for <ietf@ietf.org>; Tue, 15 Jul 2003 05:24:20 -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 h6F9OHHO005760
	for <ietf@ietf.org>; Tue, 15 Jul 2003 11:24:17 +0200
To: ietf@ietf.org
Subject: Re: Innovations in protocols 
In-reply-to: Your message of "Mon, 14 Jul 2003 14:16:42 EDT."
             <20030714181642103.AAA350@hq.lindsayelec.com@rflooker1> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 15 Jul 2003 11:24:16 +0200
Message-ID: <5759.1058261056@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-ietf@ietf.org
Precedence: bulk

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


>>>>> "Dan" == Dan Kolis <dank@hq.lindsayelec.com> writes:
    >> On Mon, 14 Jul 2003 13:35:42 EDT, dank@hq.lindsayelec.com (Dan Kolis)  said:
    >>> Valdis.Kletnieks@vt.edu wrote:
    >>> >"...IPv6 over telepathy"
    >>> Dan says:
    >>> Wow! I had that idea yesterday; (It's almost like you where reading
    >>> my mind)  
    >> !!!
    >> The draft for IPv6 over telepathy strongly recommends the use of IPSEC
    >> in multi-hop configurations, for all the obvious data-interception and
    >> data-injection
    >> reasons..... 

    Dan> Also useful for all TCP/IP; (Telepathy Control Protocol /
    Dan> Intra-Polergeist) 
    Dan> messaging. Not required for UDP (Uber Daemon Protocol) though.

  Most IPsec uses ESP (Extra Sensory Perception) to transfer data "securely",
with the actual packet being just spare garbage that is transmitted to make
it not too obvious that we are violating causality. 

  It isn't clear that if you have TCP (as described above) that actually need
more security than that - since you can avoid even transmitting the data.

]                   At IETF57 in Wien, Austria                  |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] printk("Just another Debian GNU/Linux using, kernel hacking, security guy");[



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBPxPIP4qHRg3pndX9AQH6hgP7BXT1yK+1hxJyfa4+0RNzm4o2ZHBbTJlg
hxk6XfBRuDtCw7JB5PpogD62+xRwmbTt+1CIPMhChhOUBCS/L0BhOvsqy0/dvlCj
IzhkDAwRihJlqbqk7KPawaYIE7hTjoDYuW1TFSft61Z1o2hjr2j9ulKejzbrh0FH
giqcooekcus=
=pAI9
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Tue Jul 15 10:09: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 KAA19570
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 10:09:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cQNG-0000FA-OK
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 10:01:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19c9Ap-0001NA-P5
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 15:39: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 PAA19574;
	Mon, 14 Jul 2003 15:39:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c9Ao-0006TO-00; Mon, 14 Jul 2003 15:39:46 -0400
Received: from [81.160.150.208] (helo=eve.cs.ucl.ac.uk)
	by ietf-mx with esmtp (Exim 4.12)
	id 19c9Am-0006T6-00; Mon, 14 Jul 2003 15:39:45 -0400
Received: from eve.cs.ucl.ac.uk (localhost [127.0.0.1])
	by eve.cs.ucl.ac.uk (8.12.9/8.12.2) with ESMTP id h6EJdfQR000886;
	Mon, 14 Jul 2003 20:39:42 +0100 (BST)
From: Mark Handley <M.Handley@cs.ucl.ac.uk>
X-Organisation: UCL
To: iab@ietf.org, ietf@ietf.org
Subject: Multicast Last Mile BOF report
Date: Mon, 14 Jul 2003 20:39:41 +0100
Message-ID: <885.1058211581@eve.cs.ucl.ac.uk>
Sender: owner-ietf@ietf.org
Precedence: bulk


[Note: the host my incoming email is on is hosed, so I can't currently
read email]


Multicast Last Mile BOF Report

The problem being tackled isn't completely clearly defined, but the
general philopshy is that multicast is not being deployed because most
potential receivers are using ISPs that don't supply multicast
service.  The proposal is that we need some form of auto-tunnelling
protocol which would allow a receiver to request unicast tunnelling of
multgicast traffic from a replicator somewhere on the
multicast-capable internet.  Such proposals have come up repeatedly
over the last ten years.

Th




From owner-ietf@ietf.org  Tue Jul 15 10:09: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 KAA19576
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 10:09:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cQPC-00023U-Nw
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 10:03:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19c9Ap-0001NA-P5
	for ietf@asgard.ietf.org; Mon, 14 Jul 2003 15:39: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 PAA19574;
	Mon, 14 Jul 2003 15:39:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19c9Ao-0006TO-00; Mon, 14 Jul 2003 15:39:46 -0400
Received: from [81.160.150.208] (helo=eve.cs.ucl.ac.uk)
	by ietf-mx with esmtp (Exim 4.12)
	id 19c9Am-0006T6-00; Mon, 14 Jul 2003 15:39:45 -0400
Received: from eve.cs.ucl.ac.uk (localhost [127.0.0.1])
	by eve.cs.ucl.ac.uk (8.12.9/8.12.2) with ESMTP id h6EJdfQR000886;
	Mon, 14 Jul 2003 20:39:42 +0100 (BST)
From: Mark Handley <M.Handley@cs.ucl.ac.uk>
X-Organisation: UCL
To: iab@ietf.org, ietf@ietf.org
Subject: Multicast Last Mile BOF report
Date: Mon, 14 Jul 2003 20:39:41 +0100
Message-ID: <885.1058211581@eve.cs.ucl.ac.uk>
Sender: owner-ietf@ietf.org
Precedence: bulk


[Note: the host my incoming email is on is hosed, so I can't currently
read email]


Multicast Last Mile BOF Report

The problem being tackled isn't completely clearly defined, but the
general philopshy is that multicast is not being deployed because most
potential receivers are using ISPs that don't supply multicast
service.  The proposal is that we need some form of auto-tunnelling
protocol which would allow a receiver to request unicast tunnelling of
multgicast traffic from a replicator somewhere on the
multicast-capable internet.  Such proposals have come up repeatedly
over the last ten years.

There isn't a single proposal on the table, so there are a lot of
different ways this might be done.  The chairs seem to have in mind
sending some kind of UDP-based join message towards the source, with
the router-alert option set.  When the packet reaches a
replication-capable router, the router joins the multicast group, and
tunnels the multicast traffic to the receiver.  The proposal seems to
be focussed on SSM, and only on tunnelling to receivers, although
there was a little pushbak on this.

Other people have slightly different solutions, depending on how the
tunnelling is done, whether the original soure and multicast addresses
are preserved, and how the search for the replicator is done.

There are a number of concerns, including security, potential for
using this for DoS, and whether there's a business model for the
replicator.  Much of the discussion ratholed on whether there's a
business model, and to what extent this works around existing ISP's
business models.

There seems to be a reasonable consensus in the room that something
should be done.  I think the idea isn't inherently bad.  The devil's
in the details.

I know Bill said this wasn't supposed to become a WG, but I suspect
the chairs don't feel the same way.  There's probably consensus in the
room for a WG, although not consensus on a particular solution.  I'm
not 100% convinced, but it wouldn't be a rediculous idea.





From owner-ietf@ietf.org  Tue Jul 15 10:09: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 KAA19608
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 10:09:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cQPC-00023n-TC
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 10:03:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cJcQ-0001Jo-HE
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 02:48:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25977
	for <ietf@ietf.org>; Tue, 15 Jul 2003 02:48:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cJcO-0004Je-00
	for ietf@ietf.org; Tue, 15 Jul 2003 02:48:56 -0400
Received: from [64.254.114.115] (helo=megisto-sql1.megisto.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cJcN-0004JH-00
	for ietf@ietf.org; Tue, 15 Jul 2003 02:48:55 -0400
Received: by megisto-sql1 with Internet Mail Service (5.5.2653.19)
	id <3XTK9MZG>; Tue, 15 Jul 2003 02:39:11 -0400
Message-ID: <C3F7A1AD0781F84784B5528466CA09DD013A528C@megisto-sql1>
From: Phil Roberts <PRoberts@MEGISTO.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Nomcom Result
Date: Tue, 15 Jul 2003 02:39:03 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C34A9B.C81F0BD0"
Sender: owner-ietf@ietf.org
Precedence: bulk

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

------_=_NextPart_001_01C34A9B.C81F0BD0
Content-Type: text/plain


The nomcom is pleased to announce that it has selected Margaret Wasserman
to fill the mid-term vacancy left by Erik Nordmark's resignation.
 
Thanks are due again to many folks.  First thanks are due to
all of those who volunteered to serve on the nomcom, and especially
to those who were randomly selected and served as voting members
of the nomcom.  They contributed considerable time from their busy
schedules to participate in weekly calls, to conduct interviews, to
read questionnaires, and to make the selection of candidates.
 
Thanks to those in the community who volunteered to serve on the IESG
and the IAB, both to those who were selected and those not chosen this
time around.  Thanks very much for completing the questionnaires, the
follow-up questionnaires, and participating in interviews.
 
Thanks are also due to the IETF as a whole for providing input to the
process through nominations, recommendations, and feedback on
potential candidates.
 
The voting members of the nomcom are:
Edward Lewis
Alec Brusilovsky
Michael Richardson
Eva Jonsson
Stephen Trowbridge
Frank Alfano
Thomas Kurien
Dennis Beard
Richard Draves
Eva Gustafsson
 
The nonvoting members are:
Phil Roberts - chair
Allison Mankin - IESG liaison
Eric Rescorla - IAB liaison
Ted Ts'o - past chair


------_=_NextPart_001_01C34A9B.C81F0BD0
Content-Type: text/html

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

<META content="MSHTML 6.00.2722.900" name=GENERATOR></HEAD>
<BODY><FONT face=Arial size=2>
<DIV><BR>The nomcom is pleased to announce that it has selected Margaret 
Wasserman<BR>to fill the mid-term vacancy left by Erik Nordmark's 
resignation.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks are due again to many folks.&nbsp; First thanks are due to<BR>all of 
those who volunteered to serve on the nomcom, and especially<BR>to those who 
were randomly selected and served as voting members<BR>of the nomcom.&nbsp; They 
contributed considerable time from their busy<BR>schedules to participate in 
weekly calls, to conduct interviews, to<BR>read questionnaires, and to make the 
selection of candidates.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks to those in the community who volunteered to serve on the 
IESG<BR>and the IAB, both to those who were selected and those not chosen 
this<BR>time around.&nbsp; Thanks very much for completing the questionnaires, 
the<BR>follow-up questionnaires, and participating in interviews.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks are also due to the IETF as a whole for providing input to 
the<BR>process through nominations, recommendations, and feedback 
on<BR>potential candidates.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The voting members of the nomcom are:<BR>Edward Lewis<BR>Alec 
Brusilovsky<BR>Michael Richardson<BR>Eva Jonsson<BR>Stephen Trowbridge<BR>Frank 
Alfano<BR>Thomas Kurien<BR>Dennis Beard<BR>Richard Draves<BR>Eva 
Gustafsson</DIV>
<DIV>&nbsp;</DIV>
<DIV>The nonvoting members are:<BR>Phil Roberts - chair<BR>Allison Mankin - IESG 
liaison<BR>Eric Rescorla - IAB liaison<BR>Ted Ts'o - past 
chair<BR></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C34A9B.C81F0BD0--





From owner-ietf@ietf.org  Tue Jul 15 10:09: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 KAA19606
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 10:09:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cQPD-000242-1P
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 10:03:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cKhx-0003ny-0v
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 03:58: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 DAA01559
	for <ietf@ietf.org>; Tue, 15 Jul 2003 03:58:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cKhu-0005fP-00
	for ietf@ietf.org; Tue, 15 Jul 2003 03:58:42 -0400
Received: from liandra.pc.cs.cmu.edu.ietf57.telekom.at ([81.160.141.214] helo=liandra.pc.cs.cmu.edu)
	by ietf-mx with smtp (Exim 4.12)
	id 19cKht-0005fI-00
	for ietf@ietf.org; Tue, 15 Jul 2003 03:58:41 -0400
Received: from liandra.pc.cs.cmu.edu ([127.0.0.1]) by liandra.pc.cs.cmu.edu
          id aa04761; 15 Jul 2003 9:58 CEST
Date: Tue, 15 Jul 2003 09:58:14 +0200 (CEST)
From: Jeffrey Hutzelman <jhutz@cmu.edu>
X-X-Sender:  <jhutz@liandra.pc.cs.cmu.edu>
To: Ulrich Kiermayr <ulrich.kiermayr@univie.ac.at>
cc: ietf@ietf.org
MMDF-Warning:  Parse error in original version of preceding line at liandra.pc.cs.cmu.edu
Subject: Re: IETF PGP Key Signing Party - RESCHEDULED
In-Reply-To: <3F12E846.7060807@univie.ac.at>
Message-ID: <Pine.LNX.4.33L.0307150954250.3174-100000@liandra.pc.cs.cmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 14 Jul 2003, Ulrich Kiermayr wrote:

> Jeffrey Hutzelman wrote:
> > Greetings...  As has become traditional, we will be holding a PGP key
> > signing party at the IETF meeting next week in Vienna.  Ted Ts'o will
> > be unable to attend this IETF meeting, so I have agreed to organize
> > the session in his place.
> >
> > Please note that because the IETF has rooms booked in the conference
> > center only until 22:00 each day, our usual Wednesday-night time slot
> > after the plenary was not available.  Instead, we will be holding the
> > event at the beginning of the dinner break on MONDAY, at 17:30.  Due
> > to the late change, the Secretariat has not yet told me what room we'll
> > be using; when I find out, I'll send an update and post the time on
> > the message board.
>
> Hmmmm, that was not very helpful, since majordomo sent out the mail @
>
> Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
> 	by mailbox.univie.ac.at (8.12.2/8.12.2) with ESMTP id h6EH5xoQ072474
> 	for <ulrich.kiermayr@univie.ac.at>; Mon, 14 Jul 2003 19:06:17 +0200
>
> was this just with my email address, or a server problem (i did get
> other mails from the ml during that time)?

It's unclear whether it was a server problem or a moderation problem. I'm
not subscribed to this list, so it's possible my message was held for some
time.  I talked to folks from the IETF Secretariat on Sunday, and they did
not remember seeing my message in the moderation queue.  However, Marcia
Beaulieu was kind enough to arrange for the message to be sent to the IETF
announcement list on Sunday afternoon, and to post a notice on the agenda
board, which I had hoped would be sufficient.

My apologies to anyone who was excluded due to the problems with the
announcement.

-- Jeffrey T. Hutzelman (N3NHS) <jhutz+@cmu.edu>
   Sr. Research Systems Programmer
   School of Computer Science - Research Computing Facility
   Carnegie Mellon University - Pittsburgh, PA






From owner-ietf@ietf.org  Tue Jul 15 10:09: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 KAA19638
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 10:09:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cQJO-0007eH-W8
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 09:57:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cQIe-0007dR-5c
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 09:57: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 JAA18673
	for <ietf@ietf.org>; Tue, 15 Jul 2003 09:56:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cQId-00025j-00
	for ietf@ietf.org; Tue, 15 Jul 2003 09:56:59 -0400
Received: from relay.pair.com ([209.68.1.20])
	by ietf-mx with smtp (Exim 4.12)
	id 19cQIN-00025a-00
	for ietf@ietf.org; Tue, 15 Jul 2003 09:56:43 -0400
Received: (qmail 30388 invoked from network); 15 Jul 2003 13:56:05 -0000
Received: from unknown (HELO gnet) (202.153.33.14)
  by relay.pair.com with SMTP; 15 Jul 2003 13:56:05 -0000
X-pair-Authenticated: 202.153.33.14
Message-Id: <Version.32.20030715105346.010f9880@pop3.norton.antivirus>
X-Sender: incomin/hd1.vsnl.net.in@pop3.norton.antivirus
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
X-Priority: 1 (Highest)
Date: Tue, 15 Jul 2003 19:34:27 +0530
To: dank@hq.lindsayelec.com (Dan Kolis), ietf@ietf.org
From: incomin <incomin@hd1.vsnl.net.in>
Subject: Re: Innovations in protocols
In-Reply-To: <20030714181642103.AAA350@hq.lindsayelec.com@rflooker1>
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

<html><div>Dear Friends ,</div>
<br>
<div><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&nbsp; As part of Draft for
IPV6 we&nbsp; must think of creating Intelegent / Knowledge protocols
where in it should become building blocks to create next generation
Internet called &quot; Inter Intelegent Knowledge process Net&quot; where
net thinks and acts according to Individual users requirements. Through
this , Information should reach automatically according to Individuals
requirements and meets their needs. Today we are searching for
Information and that too we don't&nbsp; know the information we are
getting really meets our requirements. </div>
<br>
<div>For example&nbsp; i may be looking for a Information on &quot;
creating a New protocol on VOIP &quot;&nbsp; Like this some more people
around the world already working on similar work , and the information is
matching each other and&nbsp;&nbsp; meeting Individual priorities and got
High scale , than the&nbsp;&nbsp; best of information must reach
automatically to the user.&nbsp; This is one of the services where in the
Net should automatically provide. </div>
<br>
<div>The Net should link people around the world based on the Individual
customized requirements , same </div>
<div>frequency of Knowledge thoughts, Ideas ,&nbsp; Goals , business
requirements etc. </div>
<br>
<div>The future is to create H-commerce or Knowledge - commerce. where in
knowlege is barterd for survival and growth rather than currency as
instrument. The protocols i want to see&nbsp; Human control protocol /
Human protocol which will be next TCP/IP.</div>
<br>
<div>Good day to you all .</div>
<div>K.S.Raju </div>
<div>&quot; We make net to think and act&quot;</div>
<div>&quot; We connect human contacts &quot; </div>
<br>
<div>&nbsp; </div>
<br>
<br>
<div>At 02:16 PM 7/14/03 -0400, Dan Kolis wrote:</div>
<div>&gt;&gt;On Mon, 14 Jul 2003 13:35:42 EDT, dank@hq.lindsayelec.com
(Dan Kolis)&nbsp; said:</div>
<div>&gt;&gt;&gt; Valdis.Kletnieks@vt.edu wrote:</div>
<div>&gt;&gt;&gt; &gt;&quot;...IPv6 over telepathy&quot;</div>
<div>&gt;&gt;&gt; Dan says:</div>
<div>&gt;&gt;&gt; Wow! I had that idea yesterday; (It's almost like you
where reading my mind) </div>
<div>&gt;&gt;!!!</div>
<div>&gt;&gt;The draft for IPv6 over telepathy strongly recommends the
use of IPSEC in</div>
<div>&gt;&gt;multi-hop configurations, for all the obvious
data-interception and</div>
<div>&gt;data-injection</div>
<div>&gt;&gt;reasons..... </div>
<div>&gt;</div>
<div>&gt;Also useful for all TCP/IP; (Telepathy Control Protocol /
Intra-Polergeist)</div>
<div>&gt;messaging. Not required for UDP (Uber Daemon Protocol)
though.</div>
<div>&gt; </div>
<BR>

**********************************************<br>
<i>Human commerce Net Pvt. Ltd,<br>
#49, Srinivasa Nagar colony East <br>
S.R.Nagar , Hyderabad , A.P , India<br>
Ph: 91-40-23745240 E-mail ; Info@humancommerce.com<br>
<br>
<b>&quot; We Make Net To Think and Act &quot; <br>
&quot; We connect Human contacts &quot; <br>
</b></i>******************************************************************</html>




From owner-ietf@ietf.org  Tue Jul 15 14:18: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 OAA28420
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 14:18:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cUCL-0003tL-2q
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 14:06:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cUBy-0003sm-J3
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 14:06:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28221
	for <ietf@ietf.org>; Tue, 15 Jul 2003 14:06:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cUBx-0004Ec-00
	for ietf@ietf.org; Tue, 15 Jul 2003 14:06:21 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cUBm-0004EW-00
	for ietf@ietf.org; Tue, 15 Jul 2003 14:06:10 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h6FI5dN22502;
        Tue, 15 Jul 2003 14:05:39 -0400 (EDT)
Date: Tue, 15 Jul 2003 14:05:38 -0400
From: Keith Moore <moore@cs.utk.edu>
To: ietf@ietf.org
Cc: moore@cs.utk.edu
Subject: no multicast of IETF plenaries
Message-Id: <20030715140538.2bf49a13.moore@cs.utk.edu>
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
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

from http://videolab.uoregon.edu/events/ietf/ietf57.html:

> NEWS:
> 
>       07-15-2003 - We're not going to broadcast the two plenary
>      sessions in the evening wednesday and thursday. They are in
>      different rooms for our equipment, and moving it is too hard.
>      Currently we plan on recording the two plenaries and they should
>      be accessible later.

I'm sorry to learn this.  The multicast access is actually turning out
to be quite useful for me this time around, and the plenaries are
important parts of the meeting.  I hate to miss them.  Watching the
recorded meetings isn't the same because there's no way to provide
real-time feedback.  

(fwiw, in my experience Jabber isn't a very good mechanism for keeping
track of what's going on, but it has worked quite well for making the
occasional remotely-originated comment.)

despite the inability to multicast the plenaries, I'm very appreciative
to the multicast team for allowing me to participate in some of the WG
meetings from Tennessee.

Keith
 



From owner-ietf@ietf.org  Tue Jul 15 15:19: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 PAA01020
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 15:19:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cVAK-0001wY-EQ
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 15:08:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cV9M-0001dZ-9x
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 15:07: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 PAA29929
	for <ietf@ietf.org>; Tue, 15 Jul 2003 15:07:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cV9K-0004d7-00
	for ietf@ietf.org; Tue, 15 Jul 2003 15:07:42 -0400
Received: from jis.mit.edu ([18.7.21.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cV99-0004cw-00
	for ietf@ietf.org; Tue, 15 Jul 2003 15:07:32 -0400
Received: from mit.edu (localhost [127.0.0.1])
	by jis.mit.edu (8.12.8p1/8.12.8) with ESMTP id h6FJ6bql010431;
	Tue, 15 Jul 2003 15:06:37 -0400 (EDT)
Message-ID: <3F1450BE.1060308@mit.edu>
Date: Tue, 15 Jul 2003 15:06:38 -0400
From: "Jeffrey I. Schiller" <jis@mit.edu>
Organization: Massachusetts Institute of Technology
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020607
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: ietf@ietf.org
Subject: Re: no multicast of IETF plenaries
References: <20030715140538.2bf49a13.moore@cs.utk.edu>
X-Enigmail-Version: 0.63.3.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

I too would appreciate the plenaries being multicasted.

			-Jeff

Keith Moore wrote:
> from http://videolab.uoregon.edu/events/ietf/ietf57.html:
> 
> 
>>NEWS:
>>
>>      07-15-2003 - We're not going to broadcast the two plenary
>>     sessions in the evening wednesday and thursday. They are in
>>     different rooms for our equipment, and moving it is too hard.
>>     Currently we plan on recording the two plenaries and they should
>>     be accessible later.
> 
> 
> I'm sorry to learn this.  The multicast access is actually turning out
> to be quite useful for me this time around, and the plenaries are
> important parts of the meeting.  I hate to miss them.  Watching the
> recorded meetings isn't the same because there's no way to provide
> real-time feedback.  
> 
> (fwiw, in my experience Jabber isn't a very good mechanism for keeping
> track of what's going on, but it has worked quite well for making the
> occasional remotely-originated comment.)
> 
> despite the inability to multicast the plenaries, I'm very appreciative
> to the multicast team for allowing me to participate in some of the WG
> meetings from Tennessee.
> 
> Keith
>  
> 





From owner-ietf@ietf.org  Tue Jul 15 15:53: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 PAA01929
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 15:53:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cVm4-0005XA-9S
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 15:47:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cVlB-0005WO-UL
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 15:46: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 PAA01698
	for <ietf@ietf.org>; Tue, 15 Jul 2003 15:46:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cVlA-0004u7-00
	for ietf@ietf.org; Tue, 15 Jul 2003 15:46:48 -0400
Received: from ns.live.com ([66.80.62.34])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cVku-0004u0-00
	for ietf@ietf.org; Tue, 15 Jul 2003 15:46:32 -0400
Received: from ns.live.com (localhost.live.com [127.0.0.1])
	by ns.live.com (8.12.9/8.12.9) with ESMTP id h6FJiphZ057721
	for <ietf@ietf.org>; Tue, 15 Jul 2003 12:46:06 -0700 (PDT)
	(envelope-from rsf@ns.live.com)
Received: (from rsf@localhost)
	by ns.live.com (8.12.9/8.12.9/Submit) id h6FJio1a057720;
	Tue, 15 Jul 2003 12:44:50 -0700 (PDT)
	(envelope-from rsf)
Message-Id: <4.3.1.1.20030715124031.00b7bd10@laptop-localhost>
X-Sender: rsf@laptop-localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 15 Jul 2003 12:41:58 -0700
To: ietf@ietf.org
From: Ross Finlayson <finlayson@live.com>
Subject: Re: no multicast of IETF plenaries
In-Reply-To: <3F1450BE.1060308@mit.edu>
References: <20030715140538.2bf49a13.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:06 PM 7/15/03, Jeffrey I. Schiller wrote:
>I too would appreciate the plenaries being multicasted.

Me too :-)  (But failing that, please try to make the recorded video 
available promptly.)

         Ross.




From owner-ietf@ietf.org  Tue Jul 15 16:09: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 QAA02768
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Jul 2003 16:09:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cW2W-00069b-3y
	for ietf-list@asgard.ietf.org; Tue, 15 Jul 2003 16:04:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cW1o-00068m-M9
	for ietf@asgard.ietf.org; Tue, 15 Jul 2003 16:04: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 QAA02449
	for <ietf@ietf.org>; Tue, 15 Jul 2003 16:03:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cW1n-00053b-00
	for ietf@ietf.org; Tue, 15 Jul 2003 16:03:59 -0400
Received: from [81.160.15.20] (helo=garlic.apnic.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cW1c-00053O-00
	for ietf@ietf.org; Tue, 15 Jul 2003 16:03:48 -0400
Received: from garlic.apnic.net (localhost [127.0.0.1])
	by garlic.apnic.net (8.12.9/8.12.9) with ESMTP id h6FK3Jl1000756;
	Wed, 16 Jul 2003 06:03:19 +1000 (EST)
Received: (from ggm@localhost)
	by garlic.apnic.net (8.12.9/8.12.9/Submit) id h6FK3IhX000591;
	Wed, 16 Jul 2003 06:03:18 +1000 (EST)
Date: Wed, 16 Jul 2003 06:03:18 +1000
From: George Michaelson <ggm@apnic.net>
To: Ross Finlayson <finlayson@live.com>
Cc: ietf@ietf.org
Subject: Re: no multicast of IETF plenaries
Message-Id: <20030716060318.72854552.ggm@apnic.net>
In-Reply-To: <4.3.1.1.20030715124031.00b7bd10@laptop-localhost>
References: <20030715140538.2bf49a13.moore@cs.utk.edu>
	<4.3.1.1.20030715124031.00b7bd10@laptop-localhost>
Organization: APNIC Pty Ltd
X-Mailer: Sylpheed version 0.9.0claws84 (GTK+ 1.2.10; i386-pc-netbsdelf1.6U)
X-Fruit-Of-The-Month-Club: persimmon
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



On Tue, 15 Jul 2003 12:41:58 -0700 Ross Finlayson <finlayson@live.com> wrote:

> At 12:06 PM 7/15/03, Jeffrey I. Schiller wrote:
> >I too would appreciate the plenaries being multicasted.
> 
> Me too :-)  (But failing that, please try to make the recorded video 
> available promptly.)
> 
>          Ross.
> 

Why not pipe the audio to the location with the mixing desk and feed, so its at
worst 0.5 plenaries? it will actually be more, the audio is far more significant
than the video in this respect.

Having done some meeting multicasting in conference centers and having seen this
one, which is fully wired for simultaneous translation, I can't believe there
isn't 75-Ohm audio cabling between all halls via patch panels...

cheers
	-George

-- 
George Michaelson       |  APNIC
Email: ggm@apnic.net    |  PO Box 2131 Milton QLD 4064
Phone: +61 7 3367 0490  |  Australia
  Fax: +61 7 3367 0482  |  http://www.apnic.net



From owner-ietf@ietf.org  Wed Jul 16 01:30: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 BAA18551
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 01:30:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ceam-0006pe-3E
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 01:12:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ceaU-0006p9-Lc
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 01: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 BAA17800;
	Wed, 16 Jul 2003 01:12:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ceaS-0002ar-00; Wed, 16 Jul 2003 01:12:20 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ceaH-0002aI-00; Wed, 16 Jul 2003 01:12:09 -0400
Received: from [127.0.0.1] (helo=roam.psg.com ident=root)
	by psg.com with esmtp (Exim 4.14)
	id 19ceZe-000ICV-6M; Wed, 16 Jul 2003 05:11:30 +0000
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.20)
	id 19ceZd-00077c-23; Wed, 16 Jul 2003 07:11:29 +0200
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 16 Jul 2003 07:11:28 +0200
To: Mark Handley <M.Handley@cs.ucl.ac.uk>
Cc: iab@ietf.org, ietf@ietf.org
Subject: Re: Multicast Last Mile BOF report
References: <885.1058211581@eve.cs.ucl.ac.uk>
Message-Id: <E19ceZd-00077c-23@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The problem being tackled isn't completely clearly defined, but the
> general philopshy is that multicast is not being deployed because most
> potential receivers are using ISPs that don't supply multicast
> service.  The proposal is that we need some form of auto-tunnelling
> protocol which would allow a receiver to request unicast tunnelling of
> multgicast traffic from a replicator somewhere on the
> multicast-capable internet.  Such proposals have come up repeatedly
> over the last ten years.

there is a serious contest to see how many mechanisms multicast
and v6 can develop to overcome why they are not being deployed.
they should get a clue.

randy




From owner-ietf@ietf.org  Wed Jul 16 01:58: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 BAA19199
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 01:58:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cfFP-0007k7-RQ
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 01:54:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cfEV-0007jR-4D
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 01:53: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 BAA19117
	for <ietf@ietf.org>; Wed, 16 Jul 2003 01:53:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cfEO-000334-00
	for ietf@ietf.org; Wed, 16 Jul 2003 01:53:36 -0400
Received: from letters.cs.ucsb.edu ([128.111.41.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cfED-00032t-00
	for ietf@ietf.org; Wed, 16 Jul 2003 01:53:25 -0400
Received: from jackson.cs.ucsb.edu (jackson [128.111.52.10])
	by letters.cs.ucsb.edu (8.11.7+Sun/8.11.6) with ESMTP id h6G5qvS12841;
	Tue, 15 Jul 2003 22:52:58 -0700 (PDT)
Received: from jackson.cs.ucsb.edu (localhost [127.0.0.1])
	by jackson.cs.ucsb.edu (8.12.8/8.12.8) with ESMTP id h6G5qvBa010058;
	Tue, 15 Jul 2003 22:52:57 -0700
Received: (from almeroth@localhost)
	by jackson.cs.ucsb.edu (8.12.8/8.12.8/Submit) id h6G5qvrO010056;
	Tue, 15 Jul 2003 22:52:57 -0700
Date: Tue, 15 Jul 2003 22:52:57 -0700
From: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
Message-Id: <200307160552.h6G5qvrO010056@jackson.cs.ucsb.edu>
To: randy@psg.com
Subject: Re: Multicast Last Mile BOF report
Cc: ietf@ietf.org
Sender: owner-ietf@ietf.org
Precedence: bulk


>>> The problem being tackled isn't completely clearly defined, but the
>>> general philopshy is that multicast is not being deployed because most
>>> potential receivers are using ISPs that don't supply multicast
>>> service.  The proposal is that we need some form of auto-tunnelling
>>> protocol which would allow a receiver to request unicast tunnelling of
>>> multgicast traffic from a replicator somewhere on the
>>> multicast-capable internet.  Such proposals have come up repeatedly
>>> over the last ten years.
>>
>>there is a serious contest to see how many mechanisms multicast
>>and v6 can develop to overcome why they are not being deployed.
>>they should get a clue.

Look at how many mechanisms NAT required before it was deployable.

Ease of deployment != good

-Kevin



From owner-ietf@ietf.org  Wed Jul 16 02: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 CAA16785
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 02:38:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cfmJ-0006w5-PI
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 02:28:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cfm1-0006uo-J1
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 02:28: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 CAA13508
	for <ietf@ietf.org>; Wed, 16 Jul 2003 02:28:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cflz-0003M3-00
	for ietf@ietf.org; Wed, 16 Jul 2003 02:28:19 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cflo-0003Lt-00
	for ietf@ietf.org; Wed, 16 Jul 2003 02:28:08 -0400
Received: from [127.0.0.1] (helo=roam.psg.com ident=root)
	by psg.com with esmtp (Exim 4.14)
	id 19cflV-000MgS-0L; Wed, 16 Jul 2003 06:27:49 +0000
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.20)
	id 19cffp-0000As-Fv; Wed, 16 Jul 2003 08:21:57 +0200
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 16 Jul 2003 08:21:55 +0200
To: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
Cc: ietf@ietf.org
Subject: Re: Multicast Last Mile BOF report
References: <200307160552.h6G5qvrO010056@jackson.cs.ucsb.edu>
Message-Id: <E19cffp-0000As-Fv@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>> there is a serious contest to see how many mechanisms multicast
>> and v6 can develop to overcome why they are not being deployed.
>> they should get a clue.
> Look at how many mechanisms NAT required before it was deployable.

there was demand for nat.

> Ease of deployment != good

and 500 gadgets do not make a technology adopted when it has no
business model folk can understand.

randy




From owner-ietf@ietf.org  Wed Jul 16 04:55: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 EAA21728
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 04:55:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19chwo-0002Vw-Ih
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 04:47:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19chwh-0002V3-3R
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 04:47: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 EAA21450
	for <ietf@ietf.org>; Wed, 16 Jul 2003 04:47:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19chwe-0004n2-00
	for ietf@ietf.org; Wed, 16 Jul 2003 04:47:28 -0400
Received: from darkwing.uoregon.edu ([128.223.142.13] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19chwT-0004mL-00
	for ietf@ietf.org; Wed, 16 Jul 2003 04:47:18 -0400
Received: from twin.uoregon.edu (twin.uoregon.edu [128.223.214.27])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h6G8k4oD018856
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Wed, 16 Jul 2003 01:46:04 -0700 (PDT)
Date: Wed, 16 Jul 2003 01:44:44 -0700 (PDT)
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
X-X-Sender: joelja@twin.uoregon.edu
To: Keith Moore <moore@cs.utk.edu>
cc: ietf@ietf.org
Subject: Re: no multicast of IETF plenaries
In-Reply-To: <20030715140538.2bf49a13.moore@cs.utk.edu>
Message-ID: <Pine.LNX.4.44.0307160138300.4280-100000@twin.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Basically we were unable to use the same rooms for the plenary the we use 
for the regular sessions. For us it's just to much to move the ch1 
equipment in two hours. It is possible the the equipment I,m using will be 
able to source mpeg-1 but not the other sources from the plenary . if it 
works I'll update the webpage at least two hours before the plenary.

joelja

On Tue, 15 Jul 2003, Keith Moore wrote:

> from http://videolab.uoregon.edu/events/ietf/ietf57.html:
> 
> > NEWS:
> > 
> >       07-15-2003 - We're not going to broadcast the two plenary
> >      sessions in the evening wednesday and thursday. They are in
> >      different rooms for our equipment, and moving it is too hard.
> >      Currently we plan on recording the two plenaries and they should
> >      be accessible later.
> 
> I'm sorry to learn this.  The multicast access is actually turning out
> to be quite useful for me this time around, and the plenaries are
> important parts of the meeting.  I hate to miss them.  Watching the
> recorded meetings isn't the same because there's no way to provide
> real-time feedback.  
> 
> (fwiw, in my experience Jabber isn't a very good mechanism for keeping
> track of what's going on, but it has worked quite well for making the
> occasional remotely-originated comment.)
> 
> despite the inability to multicast the plenaries, I'm very appreciative
> to the multicast team for allowing me to participate in some of the WG
> meetings from Tennessee.
> 
> Keith
>  
> 

-- 
-------------------------------------------------------------------------- 
Joel Jaeggli	      Academic User Services   joelja@darkwing.uoregon.edu    
--    PGP Key Fingerprint: 1DE9 8FCA 51FB 4195 B42A 9C32 A30D 121E      --
  In Dr. Johnson's famous dictionary patriotism is defined as the last
  resort of the scoundrel.  With all due respect to an enlightened but
  inferior lexicographer I beg to submit that it is the first.
	   	            -- Ambrose Bierce, "The Devil's Dictionary"





From owner-ietf@ietf.org  Wed Jul 16 05:22: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 FAA22560
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 05:22:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ciPr-0003U4-5v
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 05:17:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ciPR-0003Sr-PA
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 05: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 FAA22376
	for <ietf@ietf.org>; Wed, 16 Jul 2003 05:17:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ciPP-00052A-00
	for ietf@ietf.org; Wed, 16 Jul 2003 05:17:11 -0400
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ciPE-000521-00
	for ietf@ietf.org; Wed, 16 Jul 2003 05:17:00 -0400
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6G9GAZ20133
	for <ietf@ietf.org>; Wed, 16 Jul 2003 05:16:10 -0400 (EDT)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NLVYV1F3>; Wed, 16 Jul 2003 05:16:11 -0400
Message-ID: <D38D073716F2D411BEE400508BCF6296083B65FD@zcard04k.ca.nortel.com>
From: "Hamid Ould-Brahim" <hbrahim@nortelnetworks.com>
To: ietf@ietf.org
Subject: Re: The requirements cycle 
Date: Wed, 16 Jul 2003 05:16:10 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: owner-ietf@ietf.org
Precedence: bulk

Alex,

[clipped]...

>  Again, I was not on the IESG when PPVPN was started, however, I
>  think that naturally well-scoped technologies with a clear direction
>  in the solution space very often do not need requirements and
>  frameworks. 

....

>  It seems that the VPN problem and solution spaces are large and
>  complex enough to warrant both requirements and framework documents.
>  That said, these documents do not have to be long and fat, and it
>  should be possible to produce an acceptable quality document within
>  6 months.

>  Regarding IESG feedback (where my piece was probably the biggest):
>  Predicated on the assumption that reqs/fw documents are not needed,
>  any feedback, whether it is from the IESG or not, will be perceived
>  as a rock fetch. If we assume those are useful, IESG review is part
>  of the process of ensuring high quality of these documents.

In fact the reason why the PPVPN wg was created is because there were
two solutions (VR and 2547) already defined with some known 
*deployment* already happening. That's what motivated the ADs
to scope the WG to just standardize these two solutions which 
at that time the WG was called "NBVPN" for network-based VPNs. 

There was in fact no need for the framework and requirements drafts
since day one there was no objective to create the "best/optimum"
approach and the wg didn't debate at all the question
of which one is best VR versus 2547. It was pretty much left to 
the market to decide. 

I am pretty sure that the feedback on that was given initially
to the ADs/IESG, and I don't understand why it was ignored 
(at least from my perception).

I think the chairs were just following the advice of the IESG
on that (that the framework and requirements are necessary before
any solution is considered). 

If you notice the ppvpn charter included a statement
that indicates that no new protocols will be developed. 
This was added because of the existence of the solutions (well
before the working group was created), and there was a feeling that
if the wg allows for new protocols, etc, the delay for getting
the solutions standardized for the providers would have been
much bigger. 

It is ironic that the wg members initially
tried to address the potential technical reasons that can happen for
delaying the work but couldn't predict that the
IESG request to develop the framework and requirements drafts
are mostly the reasons for the actual delay. 

And it is unfortunate that the recent ppvpn decisions just ignored 
and didn't explicitly acknowledged that fact.

I think the delay situation  and its impact on the
IESG decision on what to do with ppvpn wg should have taken into account 
the actual history of ppvpn working group... 

Hamid.



From owner-ietf@ietf.org  Wed Jul 16 09:27: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 JAA29306
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 09:27:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cmDz-0001gr-PE
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 09:21:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cmCO-0001eB-Mm
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 09:20: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 JAA28946
	for <ietf@ietf.org>; Wed, 16 Jul 2003 09:19:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cmCO-0006yA-00
	for ietf@ietf.org; Wed, 16 Jul 2003 09:20:00 -0400
Received: from gull.mail.pas.earthlink.net ([207.217.120.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cmCD-0006y1-00
	for ietf@ietf.org; Wed, 16 Jul 2003 09:19:49 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19cmBr-0001uQ-00; Wed, 16 Jul 2003 06:19:27 -0700
Date: Wed, 16 Jul 2003 09:19:10 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Randy Bush <randy@psg.com>
Cc: moore@cs.utk.edu, almeroth@cs.ucsb.edu, ietf@ietf.org
Subject: Re: Multicast Last Mile BOF report
Message-Id: <20030716091910.56602e24.moore@cs.utk.edu>
In-Reply-To: <E19cffp-0000As-Fv@roam.psg.com>
References: <200307160552.h6G5qvrO010056@jackson.cs.ucsb.edu>
	<E19cffp-0000As-Fv@roam.psg.com>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


] and 500 gadgets do not make a technology adopted when it has no
] business model folk can understand.

one business model that might be understandable is: you should support
multicast if/when it saves you enough bandwidth (over the same content
being sent over separate unicast streams) to make it worth your cost.



From owner-ietf@ietf.org  Wed Jul 16 10:03: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 KAA00868
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 10:03:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cmoj-0003WV-Fp
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 09:59:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cmnZ-0003NS-0b
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 09:58:25 -0400
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00482
	for <ietf@ietf.org>; Wed, 16 Jul 2003 09:58:20 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200307161348.WAA06832@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id WAA06832; Wed, 16 Jul 2003 22:48:07 +0900
Subject: Re: Multicast Last Mile BOF report
In-Reply-To: <20030716091910.56602e24.moore@cs.utk.edu> from Keith Moore at "Jul
 16, 2003 09:19:10 am"
To: Keith Moore <moore@cs.utk.edu>
Date: Wed, 16 Jul 2003 22:48:06 +0859 ()
CC: Randy Bush <randy@psg.com>, almeroth@cs.ucsb.edu, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-ietf@ietf.org
Precedence: bulk

Keith;

> ] and 500 gadgets do not make a technology adopted when it has no
> ] business model folk can understand.
> 
> one business model that might be understandable is: you should support
> multicast if/when it saves you enough bandwidth (over the same content
> being sent over separate unicast streams) to make it worth your cost.

It means it saves nothing for receivers that they don't want to
receive multicast stream.

Then, senders are not motvated to send multicast stream.

Also, the bandwidth saving is beneficial to ISPs that ISPs supporting
multicast should charge less to its customers. It's not bad if ISPs are
competitive and backbone bandwidth were expensive.

								Masataka Ohta



From owner-ietf@ietf.org  Wed Jul 16 10:07: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 KAA01471
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 10:07:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cmtZ-00074w-1e
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 10:04:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cmtM-0006wr-7r
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 10:04: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 KAA00990
	for <ietf@ietf.org>; Wed, 16 Jul 2003 10:04:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cmtL-0007R7-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:04:23 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cmtA-0007R2-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:04:12 -0400
Received: from [127.0.0.1] (helo=roam.psg.com ident=root)
	by psg.com with esmtp (Exim 4.14)
	id 19cmt5-000PxZ-Aw; Wed, 16 Jul 2003 14:04:07 +0000
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.20)
	id 19cmt4-0000OF-1z; Wed, 16 Jul 2003 16:04:06 +0200
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 16 Jul 2003 16:04:05 +0200
To: Keith Moore <moore@cs.utk.edu>
Cc: almeroth@cs.ucsb.edu, ietf@ietf.org
Subject: Re: Multicast Last Mile BOF report
References: <200307160552.h6G5qvrO010056@jackson.cs.ucsb.edu>
	<E19cffp-0000As-Fv@roam.psg.com>
	<20030716091910.56602e24.moore@cs.utk.edu>
Message-Id: <E19cmt4-0000OF-1z@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>> and 500 gadgets do not make a technology adopted when it has no
>> business model folk can understand.
> one business model that might be understandable is: you should support
> multicast if/when it saves you enough bandwidth (over the same content
> being sent over separate unicast streams) to make it worth your cost.

if i needed to save bandwidth, which is not demonstrated as i sell it
</sarcasm>, that there is no content my customers want means i will add
capex and opex to save no bandwidth.

randy




From owner-ietf@ietf.org  Wed Jul 16 10:11:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01972
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 10:11:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cmwS-00026X-RH
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 10:07:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cmuR-0007P2-9h
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 10:05: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 KAA01147
	for <ietf@ietf.org>; Wed, 16 Jul 2003 10:05:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cmuQ-0007Ri-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:05:30 -0400
Received: from turkey.mail.pas.earthlink.net ([207.217.120.126])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cmuF-0007Qd-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:05:19 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by turkey.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19cmre-0005JZ-00; Wed, 16 Jul 2003 07:02:38 -0700
Date: Wed, 16 Jul 2003 10:02:21 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: moore@cs.utk.edu, randy@psg.com, almeroth@cs.ucsb.edu, ietf@ietf.org
Subject: Re: Multicast Last Mile BOF report
Message-Id: <20030716100221.53b43471.moore@cs.utk.edu>
In-Reply-To: <200307161348.WAA06832@necom830.hpcl.titech.ac.jp>
References: <20030716091910.56602e24.moore@cs.utk.edu>
	<200307161348.WAA06832@necom830.hpcl.titech.ac.jp>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wed, 16 Jul 2003 22:48:06 +0859 ()
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> wrote:

] > one business model that might be understandable is: you should support
] > multicast if/when it saves you enough bandwidth (over the same content
] > being sent over separate unicast streams) to make it worth your cost.
] 
] It means it saves nothing for receivers that they don't want to
] receive multicast stream.
] 
] Then, senders are not motvated to send multicast stream.

maybe the ISPs supporting multicast could prioritize that traffic, thus 
providing better service on multicast than unicast, thus providing an
incentive for receivers to use multicast over unicast.



From owner-ietf@ietf.org  Wed Jul 16 10:24: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 KAA02967
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 10:24:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cn9B-0002ZK-8A
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 10:20:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cn5w-00025i-3q
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 10:17: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 KAA02711
	for <ietf@ietf.org>; Wed, 16 Jul 2003 10:17:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cn5s-0007aB-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:17:20 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cn5g-0007Zl-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:17:09 -0400
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200307161404.XAA06925@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id XAA06925; Wed, 16 Jul 2003 23:04:18 +0900
Subject: Re: Multicast Last Mile BOF report
In-Reply-To: <20030716100221.53b43471.moore@cs.utk.edu> from Keith Moore at "Jul
 16, 2003 10:02:21 am"
To: Keith Moore <moore@cs.utk.edu>
Date: Wed, 16 Jul 2003 23:04:17 +0859 ()
CC: randy@psg.com, almeroth@cs.ucsb.edu, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-ietf@ietf.org
Precedence: bulk

Keith;

> ] > one business model that might be understandable is: you should support
> ] > multicast if/when it saves you enough bandwidth (over the same content
> ] > being sent over separate unicast streams) to make it worth your cost.
> ] 
> ] It means it saves nothing for receivers that they don't want to
> ] receive multicast stream.
> ] 
> ] Then, senders are not motvated to send multicast stream.
> 
> maybe the ISPs supporting multicast could prioritize that traffic, thus 
> providing better service on multicast than unicast, thus providing an
> incentive for receivers to use multicast over unicast.

Prioritization is orthogonal to uni/mulitcast issue.

Users will favour those ISPs which prioritize unicast and pay more money.

Other users may use the prioritized multicast for 1:1 communication.

							Masataka Ohta



From owner-ietf@ietf.org  Wed Jul 16 10:32:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03426
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 10:32:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cnGn-00033q-KZ
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 10:28:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cn9S-0002ZM-Pk
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 10:21: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 KAA02887
	for <ietf@ietf.org>; Wed, 16 Jul 2003 10:20:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cn9R-0007c0-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:21:01 -0400
Received: from turkey.mail.pas.earthlink.net ([207.217.120.126])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cn9H-0007bx-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:20:51 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by turkey.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19cn94-0005rE-00; Wed, 16 Jul 2003 07:20:38 -0700
Date: Wed, 16 Jul 2003 10:20:21 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: moore@cs.utk.edu, randy@psg.com, almeroth@cs.ucsb.edu, ietf@ietf.org
Subject: Re: Multicast Last Mile BOF report
Message-Id: <20030716102021.16e4e3d9.moore@cs.utk.edu>
In-Reply-To: <200307161404.XAA06925@necom830.hpcl.titech.ac.jp>
References: <20030716100221.53b43471.moore@cs.utk.edu>
	<200307161404.XAA06925@necom830.hpcl.titech.ac.jp>
X-Mailer: Sylpheed version 0.9.1 (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

] Users will favour those ISPs which prioritize unicast and pay more money.

more money will nearly always buy more bandwidth.

] Other users may use the prioritized multicast for 1:1 communication.

the trick is to only prioritize multicast for which there are enough listeners.
but this seems doable.




From owner-ietf@ietf.org  Wed Jul 16 10:32:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03448
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 10:32:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cnA2-0002bj-1p
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 10:21:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cn7e-0002Vy-VD
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 10:19: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 KAA02779
	for <ietf@ietf.org>; Wed, 16 Jul 2003 10:19:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cn7c-0007at-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:19:08 -0400
Received: from swan.mail.pas.earthlink.net ([207.217.120.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cn7R-0007aS-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:18:58 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by swan.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19cn6O-0002f1-00; Wed, 16 Jul 2003 07:17:53 -0700
Date: Wed, 16 Jul 2003 10:17:36 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Randy Bush <randy@psg.com>
Cc: moore@cs.utk.edu, almeroth@cs.ucsb.edu, ietf@ietf.org
Subject: Re: Multicast Last Mile BOF report
Message-Id: <20030716101736.32c99623.moore@cs.utk.edu>
In-Reply-To: <E19cmt4-0000OF-1z@roam.psg.com>
References: <200307160552.h6G5qvrO010056@jackson.cs.ucsb.edu>
	<E19cffp-0000As-Fv@roam.psg.com>
	<20030716091910.56602e24.moore@cs.utk.edu>
	<E19cmt4-0000OF-1z@roam.psg.com>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

] >> and 500 gadgets do not make a technology adopted when it has no
] >> business model folk can understand.
] > one business model that might be understandable is: you should support
] > multicast if/when it saves you enough bandwidth (over the same content
] > being sent over separate unicast streams) to make it worth your cost.
] 
] if i needed to save bandwidth, which is not demonstrated as i sell it
] </sarcasm>,

if your customers pay flat rate and you can deliver them the same or better
service at less cost to you, isn't this at least some incentive?
(perhaps not enough to overcome your costs?)

if your customers pay per megabyte and they can get better service at
less cost by using multicast, isn't this also an incentive of a different
sort?

] that there is no content my customers want means i will add
] capex and opex to save no bandwidth.

indeed, lack of content is a problem.  multicast won't fly unless/until 
there is content available through it that lots of people want to get.  
IETF meetings are great for me but they have a limited audience overall.



From owner-ietf@ietf.org  Wed Jul 16 10:32: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 KAA03518
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 10:32:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cnGn-00033w-W4
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 10:28:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cn9e-0002Zk-AH
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 10:21:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02891
	for <ietf@ietf.org>; Wed, 16 Jul 2003 10:21:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cn9d-0007c5-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:21:13 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19cn9S-0007bf-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:21:02 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003071610293709279
 for <ietf@ietf.org>; Wed, 16 Jul 2003 10:29:37 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 16 Jul 2003 10:17:33 -0400
Message-ID: <3F155E7C.9030202@centive.com>
Date: Wed, 16 Jul 2003 10:17:32 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Multicast Last Mile BOF report
References: <20030716091910.56602e24.moore@cs.utk.edu>	<200307161348.WAA06832@necom830.hpcl.titech.ac.jp> <20030716100221.53b43471.moore@cs.utk.edu>
In-Reply-To: <20030716100221.53b43471.moore@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Jul 2003 14:17:33.0191 (UTC) FILETIME=[FFA02170:01C34BA4]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:

>maybe the ISPs supporting multicast could prioritize that traffic, thus 
>providing better service on multicast than unicast, thus providing an
>incentive for receivers to use multicast over unicast.
>  
>
This would provide an incentive to game the system and use multicast 
even if you had only one receiver.

Isn't the real problem the fact that the set of streams that people 
might receive is so diverse, most links won't be carrying more than one 
copy of the unicast stream anyway? Multicast would help only at the 
sender's end, in the case of flash crowds; and the sender's ISP has no 
incentive to shrink the size of the bitpipe the sender needs to buy.

-- 
/==============================================================\
|John Stracke      |jstracke@centive.com                       |
|Principal Engineer|http://www.centive.com                     |
|Centive           |My opinions are my own.                    |
|==============================================================|
|"But she calls her ship _Mercy of the Goddess_!" "Kali." "Oh."|
\==============================================================/





From owner-ietf@ietf.org  Wed Jul 16 10:38:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04145
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 10:38:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cnGw-000353-IA
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 10:28:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cnBY-0002d8-TU
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 10:23: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 KAA02928
	for <ietf@ietf.org>; Wed, 16 Jul 2003 10:23:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cnBY-0007ct-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:23:12 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cnBN-0007ck-00
	for ietf@ietf.org; Wed, 16 Jul 2003 10:23:01 -0400
Received: from [127.0.0.1] (helo=roam.psg.com ident=root)
	by psg.com with esmtp (Exim 4.14)
	id 19cnBI-0001Fy-2j; Wed, 16 Jul 2003 14:22:56 +0000
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.20)
	id 19cnBH-0000RV-9J; Wed, 16 Jul 2003 16:22:55 +0200
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 16 Jul 2003 16:22:54 +0200
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: Re: Multicast Last Mile BOF report
References: <200307160552.h6G5qvrO010056@jackson.cs.ucsb.edu>
	<E19cffp-0000As-Fv@roam.psg.com>
	<20030716091910.56602e24.moore@cs.utk.edu>
	<E19cmt4-0000OF-1z@roam.psg.com>
	<20030716101736.32c99623.moore@cs.utk.edu>
Message-Id: <E19cnBH-0000RV-9J@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

let's get real here.  though we have been pushing it since i was
in nappies (and i have deployed it in isp(s), and i also donate
to hopeless progressive causes), there is far more email traffic
about multicast than there is actual multicast traffic on the WAN
internet (yes, it is heavily used on a few LANs).

randy




From owner-ietf@ietf.org  Wed Jul 16 16:14: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 QAA15547
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 16:14:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19csS2-00050O-Nk
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 16:00:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19csRR-0004z0-8E
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 15:59: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 PAA15234
	for <ietf@ietf.org>; Wed, 16 Jul 2003 15:59:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19csRP-0002hP-00
	for ietf@ietf.org; Wed, 16 Jul 2003 15:59:55 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19csRF-0002f9-00
	for ietf@ietf.org; Wed, 16 Jul 2003 15:59:45 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h6GJx2N19831;
        Wed, 16 Jul 2003 15:59:03 -0400 (EDT)
Date: Wed, 16 Jul 2003 15:59:02 -0400
From: Keith Moore <moore@cs.utk.edu>
To: ietf@ietf.org
Cc: moore@cs.utk.edu
Subject: re the plenary discussion on partial checksums
Message-Id: <20030716155902.73c23bd8.moore@cs.utk.edu>
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
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I'm not sure what the problem is here:

- UDP checksums are optional
- optional checksums probably aren't applicable to TCP
- IPv4 has IP header checksums
- IPv6 could define an option for IP header checksum
  (could be applicable to IPv4 also, if you want a stronger checksum
   for the header)
- whether L2 drops packets whose checksum fails is an L2 matter;
  the ability to turn this on or off is an L2 feature
- if the app needs a different integrity check than all-or-nothing,
  this is something that belongs in the app protocol

so it seems like what we need is a bit in the IP header to indicate that
L2 integrity checks are optional, and to specify for various kinds of
IP-over-FOO how to implement that bit in FOO.  and maybe that bit could
go in the IP option to provide a stronger checksum than normally exists
in the IP header (so that the header, at least, is protected)

Keith



From owner-ietf@ietf.org  Wed Jul 16 16:25: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 QAA16084
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 16:25:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19csmO-0005oz-1t
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 16:21:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19csmB-0005mk-NY
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 16:21: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 QAA15922;
	Wed, 16 Jul 2003 16:21:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19csmA-0002pP-00; Wed, 16 Jul 2003 16:21:22 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cslz-0002oq-00; Wed, 16 Jul 2003 16:21:11 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id C875061B98; Wed, 16 Jul 2003 22:19:08 +0200 (CEST)
Date: Wed, 16 Jul 2003 22:18:57 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dave Crocker <dcrocker@brandenburg.com>,
        Marshall Rose <mrose@dbc.mtview.ca.us>, iesg@ietf.org
Cc: impp@iastate.edu, ietf <IETF@ietf.org>
Subject: Response from a former IMPP Chair (Re: Last Call: A Model for
 Presence and Instant Messaging to Proposed Standard)
Message-ID: <209845592.1058393937@localhost>
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

WRITTEN IN MY ROLE AS FORMER IMPP CHAIR

Dave and Marshall,

I have issues with your presentation of reality.
I am unable to see technical issues of real substance in your comments; the 
issues seem all to be procedural, and revolve around the missing update to 
the WG charter.
Since I was one of the WG chairs at the two IETF meetings immediately 
following the "group of nine" effort, I accept responsibility for this 
procedural error. The charter should have been updated.

However, I must take issue with some of your presentation of how the WG 
decided issues, as well as some of your specific issues.
In particular, your statement:

> The problem with the group's dichotomy between end-to-end vs. gateway
> goals was discussed repeatedly.  Only towards the end of the working
> group's effort did this appear to become resolved -- in the direction of
> an end-to-end content standard.  However, even then it was clear that the
> few remaining participants in the group continued to hold very different
> understandings of the goal.

is directly contradicting the minutes of the December 15, 2000 meeting of 
the WG in San Diego, which say:

> ROOT: Should messages passed wround in CPIM-compliant
> Q: do we think that we need to be able to pass around a pile of bits that
> can be signed:
> A: Rough consensus in the room (all but 1 raised hand yes)
>
> Q: Should CPIM specify structure of this message?
> A: All think it should specify the format.

The exact format was thereafter discussed in March 2001 and August 2001.
Because of (I believe) the failure of the editor to update the core CPIM 
document between February 2001 and November 2001, the group did not meet in 
December 2001; the format was discussed again in March 2002, July 2002, 
November 2002 and November 2002. At no time do the minutes record a 
decision of the group to revisit or reverse its decision to support a 
single format for interoperability.

For a further instance, consider this complaint:

> How can "duration" have any useful meaning when there is no baseline
> reference for the starting point or ending point of the duration and
> when Internet exchange latencies are completely unpredictable? In other
> words, when a participant receives a duration value from another
> participant, what does it mean? Duration relative to what point of time?
> We do not know how many seconds it took for the service data to reach
> the receiving participant.

The decision to use intervals was a very visible one in the WG, and none of 
the minutes I have read show this decision being challenged at any working 
group meeting; indeed, instead we see long wrangles over the meaning of 
"duration = 0", which is hard indeed to express in a format that has a 
"baseline reference".
While I have not found this in the minutes, I believe the justification for 
using duration was the same as that used for the sysUptime in SNMP: That 
one should NOT require the elements of an IM system to have synchronized 
clocks.

A common thread running through the minutes of IMPP meetings is the 
perception that all major issues have been settled:

San Diego, December 1999:

> The goal is that the group will finish its work and then go away,
> hopefully before the next IETF.

London August 2001:

> LD: We've reached some kind of closure on all major points; really hope
> this will have been the last IMPP meeting (i.e., that we can wrap this
> into revised & finished documents before the next IETF).

My conclusions:

The working group has suffered from very slow document updates, a bad error 
in judgment (mine) re charter update, and repeated re-raising of old closed 
issues (for instance, at Atlanta in November 2002, Dave Crocker could be 
heard re-raising the issue of the need for loop control, which the group 
had discussed and decided in December 2000, choosing hopcount as the 
preferred mechanism in March 2001).

However, I find the criticisms raised against the process leading to the 
forwarding of these documents to the IESG to be very much off target.

               Harald Alvestrand
               Speaking as a former chair of the IMPP group




From owner-ietf@ietf.org  Wed Jul 16 16: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 QAA16222
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 16:29:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19csrC-00062t-5w
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 16:26:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19csr4-00060f-OH
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 16:26: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 QAA16111
	for <ietf@ietf.org>; Wed, 16 Jul 2003 16:26:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19csr3-0002rG-00
	for ietf@ietf.org; Wed, 16 Jul 2003 16:26:25 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19csqs-0002qU-00
	for ietf@ietf.org; Wed, 16 Jul 2003 16:26:14 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003071616335222794
 for <ietf@ietf.org>; Wed, 16 Jul 2003 16:33:52 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 16 Jul 2003 16:21:48 -0400
Message-ID: <3F15B3DB.2080600@centive.com>
Date: Wed, 16 Jul 2003 16:21:47 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: re the plenary discussion on partial checksums
References: <20030716155902.73c23bd8.moore@cs.utk.edu>
In-Reply-To: <20030716155902.73c23bd8.moore@cs.utk.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Jul 2003 20:21:48.0218 (UTC) FILETIME=[E23C99A0:01C34BD7]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:

>so it seems like what we need is a bit in the IP header to indicate that
>L2 integrity checks are optional, and to specify for various kinds of
>IP-over-FOO how to implement that bit in FOO.
>  
>
How would an app know to set this bit? The problem is that different L2s 
will have different likelihoods of corruption; you may decide that it's 
safe to set the bit on Ethernet, but not on 802.11*.  And, in general, 
the app doesn't know all of the L2s that may be involved when it sends a 
packet.

-- 
/==========================================\
|John Stracke      |jstracke@centive.com   |
|Principal Engineer|http://www.centive.com |
|Centive           |My opinions are my own.|
|==========================================|
|Linux: the Unix defragmentation tool.     |
\==========================================/





From owner-ietf@ietf.org  Wed Jul 16 17:03: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 RAA17459
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 17:03:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ctIH-0007Wz-Oy
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 16:54:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ctH0-0007Tb-B7
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 16:53: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 QAA16988
	for <ietf@ietf.org>; Wed, 16 Jul 2003 16:53:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ctGz-0003AB-00
	for ietf@ietf.org; Wed, 16 Jul 2003 16:53:13 -0400
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ctGo-00039v-00
	for ietf@ietf.org; Wed, 16 Jul 2003 16:53:02 -0400
Received: (from bill@localhost)
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) id h6GKYBW19845;
	Wed, 16 Jul 2003 16:34:11 -0400
Date: Wed, 16 Jul 2003 16:34:11 -0400
From: Bill Strahm <bill@strahm.net>
To: John Stracke <jstracke@centive.com>
Cc: ietf@ietf.org
Subject: Re: re the plenary discussion on partial checksums
Message-ID: <20030716163411.B19166@strahm.net>
References: <20030716155902.73c23bd8.moore@cs.utk.edu> <3F15B3DB.2080600@centive.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3F15B3DB.2080600@centive.com>; from jstracke@centive.com on Wed, Jul 16, 2003 at 04:21:47PM -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

Ok, I have to ask a silly question (not like that would be a first on this list)

Why, oh WHY would I want to receive a known corrupted packet ?

Are we talking about someone thinks they can eeke out 1% more performance
because their phy/mac can cut over immediately rather than wait for the packet
and verify the checksum ??? (or compute it on the sending side)

I guess I don't see the benefit, I guess rather than a hardware L2 check, you 
rely on something in your hardware later up to fail a check (including a L7
protocol) and drop the frame there ???

I wish I had been there to see the discussion

Bill


On Wed, Jul 16, 2003 at 04:21:47PM -0400, John Stracke wrote:
> Keith Moore wrote:
> 
> >so it seems like what we need is a bit in the IP header to indicate that
> >L2 integrity checks are optional, and to specify for various kinds of
> >IP-over-FOO how to implement that bit in FOO.
> >  
> >
> How would an app know to set this bit? The problem is that different L2s 
> will have different likelihoods of corruption; you may decide that it's 
> safe to set the bit on Ethernet, but not on 802.11*.  And, in general, 
> the app doesn't know all of the L2s that may be involved when it sends a 
> packet.
> 
> -- 
> /==========================================\
> |John Stracke      |jstracke@centive.com   |
> |Principal Engineer|http://www.centive.com |
> |Centive           |My opinions are my own.|
> |==========================================|
> |Linux: the Unix defragmentation tool.     |
> \==========================================/
> 
> 



From owner-ietf@ietf.org  Wed Jul 16 17:17:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18032
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 17:17:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ctUr-0008Dp-Vn
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 17:07:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ctUD-0008C0-9I
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 17:06: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 RAA17646
	for <ietf@ietf.org>; Wed, 16 Jul 2003 17:06:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ctUB-0003O3-00
	for ietf@ietf.org; Wed, 16 Jul 2003 17:06:52 -0400
Received: from p2.cavebear.com ([199.184.128.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ctU0-0003NJ-00
	for ietf@ietf.org; Wed, 16 Jul 2003 17:06:41 -0400
Received: from npax.cavebear.com (npax.cavebear.com [192.203.17.71])
	by p2.cavebear.com (8.12.5/8.11.6) with SMTP id h6GL5A2n010172
	for <ietf@ietf.org>; Wed, 16 Jul 2003 14:05:10 -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 h6GL5ANW032124
	for <ietf@ietf.org>; Wed, 16 Jul 2003 14:05:10 -0700
Date: Wed, 16 Jul 2003 14:05:09 -0700 (PDT)
Reply-To: Karl Auerbach <karl@cavebear.com>
To: Keith Moore <moore@cs.utk.edu>
cc: ietf@ietf.org
Subject: Re: re the plenary discussion on partial checksums
In-Reply-To: <20030716155902.73c23bd8.moore@cs.utk.edu>
Message-ID: <Pine.LNX.4.44.0307161352330.31453-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.71 (Hoop, Jr.)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 16 Jul 2003, Keith Moore wrote:

> so it seems like what we need is a bit in the IP header to indicate that
> L2 integrity checks are optional

A lot of folks seem to forget that from the point of view of IP L2
includes the busses between memory and the L2 network interface.  There
have been more than a few recorded cases where packet errors were
introduced as the packet flowed in or out of memory, unprotected by link
CRCs.

To my way of thinking we don't need a bit in the IP header, we need a bit
in the heads of implementors to remind them that relying on link-by-link
protection can be dangerous even if the links have strong CRCs.

> ... IP option to provide a stronger checksum than normally exists

The last time I saw a comparision of checksum algorithm strengths was back 
in the OSI days when the IP checksum was compared to the OSI Fletcher 
checksum (my memory is that the IP checksum came in second.)

		--karl--





From owner-ietf@ietf.org  Wed Jul 16 17:31: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 RAA18430
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 17:31:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ctnx-0000hA-SI
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 17:27:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ctlu-0000co-Fw
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 17:25: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 RAA18310
	for <ietf@ietf.org>; Wed, 16 Jul 2003 17:25:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ctlt-0003fN-00
	for ietf@ietf.org; Wed, 16 Jul 2003 17:25:09 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ctli-0003f3-00
	for ietf@ietf.org; Wed, 16 Jul 2003 17:24:58 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h6GLOSN28130;
        Wed, 16 Jul 2003 17:24:29 -0400 (EDT)
Date: Wed, 16 Jul 2003 17:24:28 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Karl Auerbach <karl@cavebear.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: re the plenary discussion on partial checksums
Message-Id: <20030716172428.78e89503.moore@cs.utk.edu>
In-Reply-To: <Pine.LNX.4.44.0307161352330.31453-100000@npax.cavebear.com>
References: <20030716155902.73c23bd8.moore@cs.utk.edu>
	<Pine.LNX.4.44.0307161352330.31453-100000@npax.cavebear.com>
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
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > so it seems like what we need is a bit in the IP header to indicate
> > that L2 integrity checks are optional
> 
> A lot of folks seem to forget that from the point of view of IP L2
> includes the busses between memory and the L2 network interface. 
> There have been more than a few recorded cases where packet errors
> were introduced as the packet flowed in or out of memory, unprotected
> by link CRCs.

For apps that tolerate lossage (or more precisely, for apps that work
better in the face of some transmission errors than they do if all
packets with transmission errors are dropped), it doesn't matter whether
the errors occur in the memory-to-interface link or somewhere else -
they'll deal with the errors no matter where they occur.  

Of course, the apps that can't tolerate lossage won't set the "lossage
is okay" bit, and they'll continue to expect that the packets that do
arrive, arrive intact.   For one particular L2 technology X this might
simply mean that packets that don't have that bit set, but do have
errors, are dropped.   For another L2 technology Y it might mean that if
that bit is not set then the IP-over-Y spec will require FEC or
link-level retry or both to make sure that those packets have a
reasonable probability of getting there intact.

> To my way of thinking we don't need a bit in the IP header, we need a
> bit in the heads of implementors to remind them that relying on
> link-by-link protection can be dangerous even if the links have strong
> CRCs.

Actually, it seems like we need a bit in the heads of people who don't
understand that 

- some kinds of links have inherently high error rates, 
- some apps are capable of dealing with less-than-perfect data,
- adding FEC and/or link-level retry to get error rates down to the
  level we're accustomed to from wire or fiber carries with it a
  substantial penalty in bandwidth and/or delay
- we'd like to be able to use those kinds of links with IP,
- we'd like to be able to run those apps over IP, and over those
  links, without paying the bandwidth or delay penalty for
  apps that don't need it.
- we'd like a stable spec for this so we can carve it in stone, 
  (er, silicon)
- since it's going to be carved in stone (silicon) we would do well
  to get it right.

Yes, this is a change to IP, and to the IP architecture.
But it's not rocket science, and it doesn't have to affect things that
don't use it explicitly.



From owner-ietf@ietf.org  Wed Jul 16 17:49: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 RAA18913
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 17:49:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cu5e-0001Wb-V0
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 17:45:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cu5W-0001Uz-My
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 17:45:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18834
	for <ietf@ietf.org>; Wed, 16 Jul 2003 17:45:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cu5V-0003qb-00
	for ietf@ietf.org; Wed, 16 Jul 2003 17:45:25 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cu5K-0003qV-00
	for ietf@ietf.org; Wed, 16 Jul 2003 17:45:14 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h6GLj4N28474;
        Wed, 16 Jul 2003 17:45:05 -0400 (EDT)
Date: Wed, 16 Jul 2003 17:45:03 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John Stracke <jstracke@centive.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: re the plenary discussion on partial checksums
Message-Id: <20030716174503.76d66ff5.moore@cs.utk.edu>
In-Reply-To: <3F15B3DB.2080600@centive.com>
References: <20030716155902.73c23bd8.moore@cs.utk.edu>
	<3F15B3DB.2080600@centive.com>
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
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> >so it seems like what we need is a bit in the IP header to indicate
> >that L2 integrity checks are optional, and to specify for various
> >kinds of IP-over-FOO how to implement that bit in FOO.
> >
> How would an app know to set this bit? The problem is that different
> L2s will have different likelihoods of corruption; you may decide that
> it's safe to set the bit on Ethernet, but not on 802.11*.  And, in
> general, the app doesn't know all of the L2s that may be involved when
> it sends a packet.

I'm not sure that the app needs to know how much lossage to expect, or
to specify how much lossage is too much.  It just wants the bits, errors
included.  Depending on the app's needs it might dynamically adapt to
varying degrees of error by adding its own FEC, e2e retransmission,
and/or interleaving, and this probably works better than trying to have
the app either determine statically how much error it can expect or by
having the app specify to the network how much error is acceptable.

I suppose we could define a maximum error rate (say 15%) that
IP-over-FOO should be designed to provide if the "lossage okay" bit is
set.  But practically speaking I doubt it's necessary to do that-
links that are designed to support lossy traffic will already have
enough FEC or whatever to suit that kind of traffic.

The biggest questions I have are:

- where to put this bit? 

- are there unintended consequences of doing this that we can forsee?


Keith



From owner-ietf@ietf.org  Wed Jul 16 17:54: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 RAA19078
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Jul 2003 17:54:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19cu9V-0001en-8C
	for ietf-list@asgard.ietf.org; Wed, 16 Jul 2003 17:49:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19cu8a-0001ab-UW
	for ietf@asgard.ietf.org; Wed, 16 Jul 2003 17:48: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 RAA18873
	for <ietf@ietf.org>; Wed, 16 Jul 2003 17:48:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cu8Z-0003rZ-00
	for ietf@ietf.org; Wed, 16 Jul 2003 17:48:35 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cu8O-0003rW-00
	for ietf@ietf.org; Wed, 16 Jul 2003 17:48:24 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h6GLm8N28493;
        Wed, 16 Jul 2003 17:48:10 -0400 (EDT)
Date: Wed, 16 Jul 2003 17:48:08 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Bill Strahm <bill@strahm.net>
Cc: moore@cs.utk.edu, jstracke@centive.com, ietf@ietf.org
Subject: Re: re the plenary discussion on partial checksums
Message-Id: <20030716174808.42022108.moore@cs.utk.edu>
In-Reply-To: <20030716163411.B19166@strahm.net>
References: <20030716155902.73c23bd8.moore@cs.utk.edu>
	<3F15B3DB.2080600@centive.com>
	<20030716163411.B19166@strahm.net>
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
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Why, oh WHY would I want to receive a known corrupted packet ?

why oh why would you ever want to talk with someone over a phone that
occasionally clicked or popped?

why or why would you ever want to watch a video with snow, or an
occasional missing pixel, or even an occasional missing frame?

sometimes getting a lossy packet is better than not getting one at all,
or having to wait for a retransmission.



From owner-ietf@ietf.org  Thu Jul 17 03:28:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19886
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 03:28:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d333-0007KI-F7
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 03:19:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d31q-0007C2-B8
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 03:18: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 DAA19643
	for <ietf@ietf.org>; Thu, 17 Jul 2003 03:18:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d31n-00028J-00
	for ietf@ietf.org; Thu, 17 Jul 2003 03:18:11 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d31c-00028D-00
	for ietf@ietf.org; Thu, 17 Jul 2003 03:18:00 -0400
Received: from [127.0.0.1] (helo=roam.psg.com ident=root)
	by psg.com with esmtp (Exim 4.14)
	id 19d2z6-000A0i-Es; Thu, 17 Jul 2003 07:15:24 +0000
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.20)
	id 19d1SZ-000FqQ-Nd; Thu, 17 Jul 2003 07:37:43 +0200
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 17 Jul 2003 07:37:43 +0200
To: Keith Moore <moore@cs.utk.edu>
Cc: Bill Strahm <bill@strahm.net>, jstracke@centive.com, ietf@ietf.org
Subject: Re: re the plenary discussion on partial checksums
References: <20030716155902.73c23bd8.moore@cs.utk.edu>
	<3F15B3DB.2080600@centive.com>
	<20030716163411.B19166@strahm.net>
	<20030716174808.42022108.moore@cs.utk.edu>
Message-Id: <E19d1SZ-000FqQ-Nd@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>> Why, oh WHY would I want to receive a known corrupted packet ?
> why oh why would you ever want to talk with someone over a phone that
> occasionally clicked or popped?

and why would i mind cheese with holes in it?  i don't care about
cheese or voice phones.  i care about internet data packets.

randy




From owner-ietf@ietf.org  Thu Jul 17 03:40:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20675
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 03:40:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d3IX-0008Vb-CR
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 03:35:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d3Hf-0008Tg-Dk
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 03:34: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 DAA20334
	for <ietf@ietf.org>; Thu, 17 Jul 2003 03:34:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d3Hd-0002L6-00
	for ietf@ietf.org; Thu, 17 Jul 2003 03:34:33 -0400
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d3HS-0002JD-00
	for ietf@ietf.org; Thu, 17 Jul 2003 03:34:22 -0400
Received: from mobilebill (12-210-40-123.client.attbi.com[12.210.40.123](untrusted sender))
          by attbi.com (rwcrmhc11) with SMTP
          id <2003071707303301300njqkee>; Thu, 17 Jul 2003 07:30:33 +0000
From: "bill" <bill@strahm.net>
To: "'Keith Moore'" <moore@cs.utk.edu>,
        "'John Stracke'" <jstracke@centive.com>
Cc: <ietf@ietf.org>
Subject: RE: re the plenary discussion on partial checksums
Date: Thu, 17 Jul 2003 00:30:18 -0700
Message-ID: <008901c34c35$4674c020$1c02a8c0@mobilebill>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-reply-to: <20030716174503.76d66ff5.moore@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

What bit is needed ?

Again, this is a layer 2 property.  If you want to receive layer 2
frames with errors in them just get a Layer 2 device and tell it to not
do the checksum calculation (much like you put an ethernet nic into
Promiscous mode so it doesn't drop all of the frames not destined for
it.

As for asking for end-end characterization of this, I think it is
crazy... The bit can be in your IP header address fields(and on small
ACK packets, statistically it WILL be there) so the packet wouldn't have
even made it to your host, it can be in the TCP port fields so it won't
be received on the correct connection... Much more, the infrastructure
might as well let the packet get dropped.

I would have a hard time taking an IP header bit and making it the "Do
not drop this packet in the presense of a bit error somewhere in the
frame from layer 2 - layer 3".  Don't think it is a good idea.
Bill

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of
Keith Moore
Sent: Wednesday, July 16, 2003 2:45 PM
To: John Stracke
Cc: moore@cs.utk.edu; ietf@ietf.org
Subject: Re: re the plenary discussion on partial checksums


> >so it seems like what we need is a bit in the IP header to indicate 
> >that L2 integrity checks are optional, and to specify for various 
> >kinds of IP-over-FOO how to implement that bit in FOO.
> >
> How would an app know to set this bit? The problem is that different 
> L2s will have different likelihoods of corruption; you may decide that

> it's safe to set the bit on Ethernet, but not on 802.11*.  And, in 
> general, the app doesn't know all of the L2s that may be involved when

> it sends a packet.

I'm not sure that the app needs to know how much lossage to expect, or
to specify how much lossage is too much.  It just wants the bits, errors
included.  Depending on the app's needs it might dynamically adapt to
varying degrees of error by adding its own FEC, e2e retransmission,
and/or interleaving, and this probably works better than trying to have
the app either determine statically how much error it can expect or by
having the app specify to the network how much error is acceptable.

I suppose we could define a maximum error rate (say 15%) that
IP-over-FOO should be designed to provide if the "lossage okay" bit is
set.  But practically speaking I doubt it's necessary to do that- links
that are designed to support lossy traffic will already have enough FEC
or whatever to suit that kind of traffic.

The biggest questions I have are:

- where to put this bit? 

- are there unintended consequences of doing this that we can forsee?


Keith






From owner-ietf@ietf.org  Thu Jul 17 03: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 DAA21328
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 03:53:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d3SE-0000pv-2W
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 03:45:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d3Qi-0000ai-3x
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 03:43: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 DAA20831
	for <ietf@ietf.org>; Thu, 17 Jul 2003 03:43:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d3Qf-0002S6-00
	for ietf@ietf.org; Thu, 17 Jul 2003 03:43:53 -0400
Received: from nmh.informatik.uni-bremen.de ([134.102.224.3] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d3QU-0002Qi-00
	for ietf@ietf.org; Thu, 17 Jul 2003 03:43:42 -0400
Received: from tzi.org (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.12.9/8.12.9) with ESMTP id h6H7gF6d019585;
	Thu, 17 Jul 2003 09:42:15 +0200 (MEST)
Date: Thu, 17 Jul 2003 09:42:11 +0200
Subject: Re: re the plenary discussion on partial checksums
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Carsten Bormann <cabo@tzi.org>, John Stracke <jstracke@centive.com>,
        ietf@ietf.org
To: Keith Moore <moore@cs.utk.edu>
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20030716174503.76d66ff5.moore@cs.utk.edu>
Message-Id: <2CE3D717-B82A-11D7-B4D9-00039390397C@tzi.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The biggest questions I have are:
>
> - where to put this bit?

Right now, the *only* way an L2 with varied service levels can derive 
what service levels to use for best-effort traffic is to perform a 
layer violation.  Continuing this tradition, the bit would be:

less_than_perfect_L2_error_detection = (ip.protocol == IPPROTO_UDPLITE)

Additionally the L3-L2 mapping can layer-violate up into the UDP-lite 
header and extract information about unequal error protection it may 
need i.e., apply more protection to data covered by the UDP-lite 
checksum than the uncovered data.  Of course, the same thing can be 
done for unequal error detection (do apply good L2 error detection to 
the part covered by the UDP-lite checksum).

Ugly?  Yes.
Unfortunately, the alternative is to make L3-L2 mappings a first-class 
citizen in the IP architecture and provide a way for an application to 
provide information that could help/influence this mapping.  As RSVP 
has demonstrated, this is hairy stuff (even ignoring multicast).

> - are there unintended consequences of doing this that we can forsee?

Some issues raised at the plenary were:

-- the old NFS-on-UDP-without-checksums story.  Folks using UDP-lite 
for non-error-tolerant data get what they deserve.

-- a general feeling that nobody knows what will blow up when L2s do 
less error detection.  "Allowing" this only for clearly defined cases 
(like ip.protocol == IPPROTO_UDPLITE) might help to allay these 
well-founded fears.

Gruesse, Carsten

PS.: those who don't know what all this is good for might want to read 
up on voice codecs like GSM 06.10 that have data fields for excitation 
energy -- generally, it is better to have a slightly corrupted packet 
with new values for this arrive than to error-conceal an erasure.
Of course, once this starts to get implemented, there are other 
possible applications, e.g. application-layer FEC.




From owner-ietf@ietf.org  Thu Jul 17 04:08: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 EAA22068
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 04:08:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d3jd-0006v1-I7
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 04:03:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d3gy-0006iA-Jb
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 04:00:44 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21702
	for <ietf@ietf.org>; Thu, 17 Jul 2003 04:00:40 -0400 (EDT)
Received: from [127.0.0.1] (helo=roam.psg.com ident=root)
	by psg.com with esmtp (Exim 4.14)
	id 19d3gx-000D3Y-7j
	for ietf@ietf.org; Thu, 17 Jul 2003 08:00:43 +0000
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.20)
	id 19d3gw-000GmD-Ia
	for ietf@ietf.org; Thu, 17 Jul 2003 10:00:42 +0200
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 17 Jul 2003 10:00:42 +0200
To: ietf <ietf@ietf.org>
Subject: in-addr.arpa missing
Message-Id: <E19d3gw-000GmD-Ia@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

i received 81.160.221.53 via dhcp.  but

Host 53.221.160.81.in-addr.arpa not found: 3(NXDOMAIN)

randy




From owner-ietf@ietf.org  Thu Jul 17 04:34: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 EAA22938
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 04:34:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d454-0008Fq-7S
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 04:25:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d40R-000875-Qz
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 04:20: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 EAA22542
	for <ietf@ietf.org>; Thu, 17 Jul 2003 04:20:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d40P-0002yz-00
	for ietf@ietf.org; Thu, 17 Jul 2003 04:20:49 -0400
Received: from nmh.informatik.uni-bremen.de ([134.102.224.3] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d40E-0002yq-00
	for ietf@ietf.org; Thu, 17 Jul 2003 04:20:38 -0400
Received: from tzi.org (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.12.9/8.12.9) with ESMTP id h6H8KH6d003822;
	Thu, 17 Jul 2003 10:20:17 +0200 (MEST)
Date: Thu, 17 Jul 2003 10:20:04 +0200
Subject: Re: re the plenary discussion on partial checksums
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Carsten Bormann <cabo@tzi.org>, ietf@ietf.org
To: John Stracke <jstracke@centive.com>
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <3F15B3DB.2080600@centive.com>
Message-Id: <77B9F4DB-B82F-11D7-B4D9-00039390397C@tzi.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> How would an app know to set this bit? The problem is that different 
> L2s will have different likelihoods of corruption; you may decide that 
> it's safe to set the bit on Ethernet, but not on 802.11*.

Aah, there's the confusion.  The apps we have in mind would think that 
it is pointless (but harmless) to set the bit on Ethernet, but would be 
quite interested in setting it on 802.11*.

This is not "is my data safe even if I give up some L2 error 
detection", this is "L2 error detection destroys data that I could 
salvage".
Don't think "NFS on bad Ethernet cards" (yes, I'm old enough to have 
been hit by this, too!), think "conversational media data on wireless 
links that give you 35 % more bandwidth if you give up some error 
protection" (35 % was Pekka Pessi's figure on the plenary jabber, IIRC).

Gruesse, Carsten

*) e.g., in order to salvage half of a video packet that got an error 
in the middle.  (Reducing packet sizes to achieve a similar effect is 
highly counterproductive on media with a very high per-packet overhead 
such as 802.11.)  Of course, 802.11 has retransmissions, so maybe this 
is a bad example, but it does illustrate the point.




From owner-ietf@ietf.org  Thu Jul 17 04:41: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 EAA23201
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 04:41:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d4Fi-0000ci-Lu
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 04:36:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d4BL-0000AU-MX
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 04:32: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 EAA22893
	for <ietf@ietf.org>; Thu, 17 Jul 2003 04:32:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d4BJ-0003As-00
	for ietf@ietf.org; Thu, 17 Jul 2003 04:32:05 -0400
Received: from [213.219.58.242] (helo=homer)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d4B8-00039m-00
	for ietf@ietf.org; Thu, 17 Jul 2003 04:31:54 -0400
Date: Thu, 17 Jul 2003 09:30:19 +0100
Subject: Re: re the plenary discussion on partial checksums
From: Jonathan Hogg <jonathan.hogg@seventh-wave-systems.com>
To: bill <bill@strahm.net>, "'Keith Moore'" <moore@cs.utk.edu>,
        "'John Stracke'" <jstracke@centive.com>
CC: IETF <ietf@ietf.org>
Message-ID: <BB3C1D2B.1CD0C%jonathan.hogg@seventh-wave-systems.com>
In-Reply-To: <008901c34c35$4674c020$1c02a8c0@mobilebill>
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 17/7/03 8:30, bill wrote:

> I would have a hard time taking an IP header bit and making it the "Do
> not drop this packet in the presense of a bit error somewhere in the
> frame from layer 2 - layer 3".  Don't think it is a good idea.

What if that bit got corrupted?

Jonathan





From owner-ietf@ietf.org  Thu Jul 17 04:41: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 EAA23223
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 04:41:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d4Fi-0000cb-C4
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 04:36:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d4B3-00006K-QA
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 04:31:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22880
	for <ietf@ietf.org>; Thu, 17 Jul 2003 04:31:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d4B1-0003AS-00
	for ietf@ietf.org; Thu, 17 Jul 2003 04:31:47 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d4Aq-00039z-00
	for ietf@ietf.org; Thu, 17 Jul 2003 04:31:36 -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 h6H8VpxS058022;
	Thu, 17 Jul 2003 10:31:52 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 17 Jul 2003 10:30:57 +0200
Subject: Re: re the plenary discussion on partial checksums
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: <20030716155902.73c23bd8.moore@cs.utk.edu>
Message-Id: <FD4B13C8-B830-11D7-9CD6-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, jul 16, 2003, at 21:59 Europe/Amsterdam, Keith Moore wrote:

> I'm not sure what the problem is here:

> - UDP checksums are optional

Not in IPv6. If this is the only thing we need at the transport layer 
then we might want to change this back to the IPv4 behavior.

> - IPv6 could define an option for IP header checksum
>   (could be applicable to IPv4 also, if you want a stronger checksum
>    for the header)

It would make sense to make this more general. IIRC, GSM uses a scheme 
where some bits must be transferred correct some bits may have errors 
but are important enough to protect with forward error correction and 
some other bits are not important so they don't get any protection at 
all. Now obviously we don't want to carry FEC overhead over our 1 in 
10^8 bit error links so there must be some way to map application 
requirements to different link layers for the same packet so some links 
will add the necessary FEC for the important part of the data on the 
link and then strip it off again, but other links either simply turn 
off the CRC or do nothing (as the bit error rate is so minimal that 
implementing turning off the CRC on a per-packet basis isn't worth it). 
This is what I was getting at (way too cryptically) at the microphone 
yesterday.

Then an application-specific CRC over the uncorruptable part can happen 
at the receiver. Such a mechanism could also address the problem that 
our current checksums or even link CRCs aren't strong enough for much 
larger packets.

> - whether L2 drops packets whose checksum fails is an L2 matter;
>   the ability to turn this on or off is an L2 feature

Obviously not. If I'm doing A/V over wifi I would probably want the 
802.11b MAC to adopt multicast behavior where it sends the packet at a 
fixed rate without link layer retransmits and then have them delivered 
to the other side if there are errors as well, but if I'm also doing 
TCP over this link I would want this traffic to be treated as usual. So 
this must be a per-packet mechanism.

> so it seems like what we need is a bit in the IP header to indicate 
> that
> L2 integrity checks are optional, and to specify for various kinds of
> IP-over-FOO how to implement that bit in FOO.  and maybe that bit could
> go in the IP option to provide a stronger checksum than normally exists
> in the IP header (so that the header, at least, is protected)

I think the best way to do this is using diffserv to enable/disable the 
special link handling. If special link handling is required then the 
packet can be further inspected to see how much of it should receive 
additional FEC protection.

Yes, the IP header (but certainly not always just that) would be 
uncorruptable. E2e dictates that the receiving host checks this but we 
probably want to do it after special links too.

Interesting aspect: it should be possible to make this work with IPsec 
encryption but not authentication, but not so well with ciphers in CBC 
mode. A stream cipher would be better here.




From owner-ietf@ietf.org  Thu Jul 17 05:14: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 FAA24789
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 05:14:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d4kX-0002mW-FU
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 05:08:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d4jP-0002hP-5x
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 05:07:19 -0400
Received: from klapautius.it.su.se ([81.160.170.167])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24472
	for <ietf@ietf.org>; Thu, 17 Jul 2003 05:07:14 -0400 (EDT)
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h6H8wBF16210;
	Thu, 17 Jul 2003 10:58:11 +0200
Message-ID: <3F166523.7060200@it.su.se>
Date: Thu, 17 Jul 2003 10:58:11 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
CC: ietf <ietf@ietf.org>
Subject: Re: in-addr.arpa missing
References: <E19d3gw-000GmD-Ia@roam.psg.com>
In-Reply-To: <E19d3gw-000GmD-Ia@roam.psg.com>
X-Enigmail-Version: 0.76.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Randy Bush wrote:

>i received 81.160.221.53 via dhcp.  but
>
>Host 53.221.160.81.in-addr.arpa not found: 3(NXDOMAIN)
>
>randy
>
>
>  
>
If you think that is strange I got 81.160.251.0 just now (!) but I am not
sure it isn't pocketpc 200x thumbing its nose at me :-)

       Cheers Leif




From owner-ietf@ietf.org  Thu Jul 17 05:16: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 FAA24923
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 05:16:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d4pN-00033v-FJ
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 05:13:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d4m1-0002rL-OF
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 05:10:01 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24560
	for <ietf@ietf.org>; Thu, 17 Jul 2003 05:09:57 -0400 (EDT)
Received: from [127.0.0.1] (helo=roam.psg.com ident=root)
	by psg.com with esmtp (Exim 4.14)
	id 19d4m0-000Gnj-5h; Thu, 17 Jul 2003 09:10:00 +0000
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.20)
	id 19d4lz-000GsO-53; Thu, 17 Jul 2003 11:09:59 +0200
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 17 Jul 2003 11:09:58 +0200
To: Leif Johansson <leifj@it.su.se>
Cc: ietf <ietf@ietf.org>
Subject: Re: in-addr.arpa missing
References: <E19d3gw-000GmD-Ia@roam.psg.com>
	<3F166523.7060200@it.su.se>
Message-Id: <E19d4lz-000GsO-53@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> If you think that is strange I got 81.160.251.0 just now

given the netmask, that is a perfectly legitimate interface
address

randy




From owner-ietf@ietf.org  Thu Jul 17 05:19: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 FAA25203
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 05:19:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d4pN-000341-QV
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 05:13:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d4m4-0002rN-RP
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 05:10:04 -0400
Received: from linux.research.att.com (H-135-207-24-16.research.att.com [135.207.24.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24564
	for <ietf@ietf.org>; Thu, 17 Jul 2003 05:10:00 -0400 (EDT)
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by linux.research.att.com (8.12.8/8.12.8) with ESMTP id h6H9OqJh026703;
	Thu, 17 Jul 2003 05:24:52 -0400
Received: from berkshire.research.att.com (raptor.research.att.com [135.207.23.32])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h6H99SV27436;
	Thu, 17 Jul 2003 05:09:28 -0400 (EDT)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id DD9C67B4D; Thu, 17 Jul 2003 11:09:26 +0200 (CEST)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: re the plenary discussion on partial checksums 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 17 Jul 2003 11:09:26 +0200
From: "Steven M. Bellovin" <smb@research.att.com>
Message-Id: <20030717090927.DD9C67B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <FD4B13C8-B830-11D7-9CD6-00039388672E@muada.com>, Iljitsch van Beijn
um writes:

>
>Interesting aspect: it should be possible to make this work with IPsec 
>encryption but not authentication, but not so well with ciphers in CBC 
>mode. A stream cipher would be better here.
>
>
Here is the Security Considerations text that Gorry Fairhurst has
inserted into draft-ietf-tsvwg-udp-lite-01.txt to satisfy my DISCUSS:

---

Security Considerations

The security impact of UDP-Lite is related to its interaction with
authentication and encryption mechanisms. When the partial checksum option
of UDP-Lite is enabled, the insensitive portion of a packet may change in
transit. This is contrary to the idea behind most authentication mechanisms:
authentication succeeds if the packet has not changed in transit. Unless
authentication mechanisms that operate only on the sensitive part of packets
are developed and used, authentication will always fail for UDP-Lite packets
where the insensitive part has been damaged.

The IPSec integrity check (Encapsulation Security Protocol, ESP, or
Authentication Header, AH) is applied (at least) to the entire IP packet
payload. Corruption of any bit within the protected area will then result in
discarding the UDP-Lite packet by the IP receiver.

Encryption (e.g. IPSEC ESP with payload, but no integrity check)
may be used.  Note that omitting an integrity check can, under
certain circumstances, compromise confidentiality [Bell98].

If a few bits of an encrypted packet are damaged, the decryption
transform will typically spread errors so that the packet becomes
too damaged to be of use.  Many encryption transforms today exhibit
this behavior.  There exist encryption transforms, stream ciphers,
which do not cause error propagation.  Proper use of stream ciphers
can be quite difficult, especially when authentication-checking is
omitted [BB01].  In particular, an attacker can cause predictable
changes to the ultimate plaintext, even without being able to
decrypt the ciphertext.


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





From owner-ietf@ietf.org  Thu Jul 17 05:19: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 FAA25316
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 05:19:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d4pO-00034H-5B
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 05:13:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d4nw-0002wv-Ic
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 05: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 FAA24642
	for <ietf@ietf.org>; Thu, 17 Jul 2003 05:11:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d4nu-0003a3-00
	for ietf@ietf.org; Thu, 17 Jul 2003 05:11:58 -0400
Received: from [81.160.170.167] (helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d4nj-0003Zj-00
	for ietf@ietf.org; Thu, 17 Jul 2003 05:11:47 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h6H97hF16237;
	Thu, 17 Jul 2003 11:07:43 +0200
Message-ID: <3F16675E.2080708@it.su.se>
Date: Thu, 17 Jul 2003 11:07:42 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
CC: ietf <ietf@ietf.org>
Subject: Re: in-addr.arpa missing
References: <E19d3gw-000GmD-Ia@roam.psg.com>	<3F166523.7060200@it.su.se> <E19d4lz-000GsO-53@roam.psg.com>
In-Reply-To: <E19d4lz-000GsO-53@roam.psg.com>
X-Enigmail-Version: 0.76.2.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

Randy Bush wrote:

>>If you think that is strange I got 81.160.251.0 just now
>>    
>>
>
>given the netmask, that is a perfectly legitimate interface
>address
>
>randy
>
>  
>
True but I'm not getting any traffic through though...




From owner-ietf@ietf.org  Thu Jul 17 05:27: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 FAA25969
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 05:27:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d501-00051E-CN
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 05:24:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d4wO-0004Um-0w
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 05:20:44 -0400
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25446
	for <ietf@ietf.org>; Thu, 17 Jul 2003 05:20:39 -0400 (EDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h6H9K2J03522;
	Thu, 17 Jul 2003 12:20:02 +0300
Date: Thu, 17 Jul 2003 12:20:00 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Randy Bush <randy@psg.com>
cc: Leif Johansson <leifj@it.su.se>, ietf <ietf@ietf.org>
Subject: Re: in-addr.arpa missing
In-Reply-To: <E19d4lz-000GsO-53@roam.psg.com>
Message-ID: <Pine.LNX.4.44.0307171218560.3330-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 17 Jul 2003, Randy Bush wrote:
> > If you think that is strange I got 81.160.251.0 just now
> 
> given the netmask, that is a perfectly legitimate interface
> address

Be glad it didn't give you 81.260.250.255 because some filter out all 
addresses that end up with .255 :-)

Even in ISP backbones.

-- 
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 Jul 17 05:43: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 FAA27063
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 05:43:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d5Da-0006fx-8U
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 05:38:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d592-00068i-Oy
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 05:33:48 -0400
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26562
	for <ietf@ietf.org>; Thu, 17 Jul 2003 05:33:44 -0400 (EDT)
Received: from twin.uoregon.edu (twin.uoregon.edu [128.223.214.27])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h6H9SloD014231
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Thu, 17 Jul 2003 02:28:47 -0700 (PDT)
Date: Thu, 17 Jul 2003 02:27:14 -0700 (PDT)
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
X-X-Sender: joelja@twin.uoregon.edu
To: Leif Johansson <leifj@it.su.se>
cc: Randy Bush <randy@psg.com>, ietf <ietf@ietf.org>
Subject: Re: in-addr.arpa missing
In-Reply-To: <3F166523.7060200@it.su.se>
Message-ID: <Pine.LNX.4.44.0307170226540.10289-100000@twin.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Thu, 17 Jul 2003, Leif Johansson wrote:

> Randy Bush wrote:
> 
> >i received 81.160.221.53 via dhcp.  but
> >
> >Host 53.221.160.81.in-addr.arpa not found: 3(NXDOMAIN)
> >
> >randy
> >
> >
> >  
> >
> If you think that is strange I got 81.160.251.0 just now (!) but I am not
> sure it isn't pocketpc 200x thumbing its nose at me :-)

It's a big subnet.
 
>        Cheers Leif
> 
> 

-- 
-------------------------------------------------------------------------- 
Joel Jaeggli	      Academic User Services   joelja@darkwing.uoregon.edu    
--    PGP Key Fingerprint: 1DE9 8FCA 51FB 4195 B42A 9C32 A30D 121E      --
  In Dr. Johnson's famous dictionary patriotism is defined as the last
  resort of the scoundrel.  With all due respect to an enlightened but
  inferior lexicographer I beg to submit that it is the first.
	   	            -- Ambrose Bierce, "The Devil's Dictionary"





From owner-ietf@ietf.org  Thu Jul 17 05:46: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 FAA27300
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 05:46:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d5Db-0006gU-2G
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 05:38:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d5A0-0006GO-Vj
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 05:34: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 FAA26629
	for <ietf@ietf.org>; Thu, 17 Jul 2003 05:34:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d59y-0003wg-00
	for ietf@ietf.org; Thu, 17 Jul 2003 05:34:46 -0400
Received: from darkwing.uoregon.edu ([128.223.142.13] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d59n-0003u5-00
	for ietf@ietf.org; Thu, 17 Jul 2003 05:34:35 -0400
Received: from twin.uoregon.edu (twin.uoregon.edu [128.223.214.27])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h6H9UuoD014439
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Thu, 17 Jul 2003 02:30:56 -0700 (PDT)
Date: Thu, 17 Jul 2003 02:29:23 -0700 (PDT)
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
X-X-Sender: joelja@twin.uoregon.edu
To: Leif Johansson <leifj@it.su.se>
cc: Randy Bush <randy@psg.com>, ietf <ietf@ietf.org>
Subject: Re: in-addr.arpa missing
In-Reply-To: <3F16675E.2080708@it.su.se>
Message-ID: <Pine.LNX.4.44.0307170227410.10289-100000@twin.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 17 Jul 2003, Leif Johansson wrote:

> Randy Bush wrote:
> 
> >>If you think that is strange I got 81.160.251.0 just now
> >>    
> >>
> >
> >given the netmask, that is a perfectly legitimate interface
> >address
> >
> >randy
> >
> >  
> >
> True but I'm not getting any traffic through though...

some borken os's don't like ip address that end in 0 or 255...
 
> 

-- 
-------------------------------------------------------------------------- 
Joel Jaeggli	      Academic User Services   joelja@darkwing.uoregon.edu    
--    PGP Key Fingerprint: 1DE9 8FCA 51FB 4195 B42A 9C32 A30D 121E      --
  In Dr. Johnson's famous dictionary patriotism is defined as the last
  resort of the scoundrel.  With all due respect to an enlightened but
  inferior lexicographer I beg to submit that it is the first.
	   	            -- Ambrose Bierce, "The Devil's Dictionary"





From owner-ietf@ietf.org  Thu Jul 17 06:28: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 GAA28548
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 06:28:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d5vm-00048x-K0
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 06:24:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d5tt-00041J-VP
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 06:22: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 GAA28430;
	Thu, 17 Jul 2003 06:22:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d5tr-0004P1-00; Thu, 17 Jul 2003 06:22:11 -0400
Received: from ratree.psu.ac.th ([202.12.73.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d5tf-0004Os-00; Thu, 17 Jul 2003 06:22:00 -0400
Received: from delta.cs.mu.OZ.AU (delta.coe.psu.ac.th [172.30.0.98])
	by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id h6HAJn805038;
	Thu, 17 Jul 2003 17:19:49 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h6HA9js12841;
	Thu, 17 Jul 2003 17:10:42 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: Dave Crocker <dcrocker@brandenburg.com>,
        Marshall Rose <mrose@dbc.mtview.ca.us>, iesg@ietf.org,
        impp@iastate.edu, ietf <IETF@ietf.org>
Subject: Re: Response from a former IMPP Chair (Re: Last Call: A Model for Presence and Instant Messaging to Proposed Standard) 
In-Reply-To: <209845592.1058393937@localhost> 
References: <209845592.1058393937@localhost> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 17 Jul 2003 17:09:45 +0700
Message-ID: <13409.1058436585@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Wed, 16 Jul 2003 22:18:57 +0200
    From:        Harald Tveit Alvestrand <harald@alvestrand.no>
    Message-ID:  <209845592.1058393937@localhost>

  | However, I find the criticisms raised against the process leading to the 
  | forwarding of these documents to the IESG to be very much off target.
  | 
  |                Harald Alvestrand
  |                Speaking as a former chair of the IMPP group

Hmm - I know nothing whatever about the IMPP working group, nor any of
the issues raised by Dave & Marshall, but your response (this message)
makes it appear that the WG activity was all wrong.

Your characterisation of what happened revolves entirely around what
happened at WG meetings (during IETF meetings), and cites minutes of
those meetings as evidence of WG decisions.

That cannot possibly be correct.   WG decisions are supposed to be taken
on the WG mailing list, decisions at IETF meetings are close to no-ops
(though they can provide a lot of beneficial advice).

Your message should have been citing the mailing list archives for the WG
as justification of the decisions made, and lack of unresolved (serious)
objections.

kre





From owner-ietf@ietf.org  Thu Jul 17 07:56: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 HAA01921
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 07:56:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d7Fj-00014n-Ea
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 07:48:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d7Cj-0000ud-6a
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 07:45:45 -0400
Received: from noxmail.sandelman.ottawa.on.ca (cyphermail.sandelman.ottawa.on.ca [192.139.46.78])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01510
	for <ietf@ietf.org>; Thu, 17 Jul 2003 07:45:42 -0400 (EDT)
Received: from sandelman.ottawa.on.ca ([2002:51a0:4ea::1])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p2/8.11.6) with ESMTP id h6HBjbW26657
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK);
	Thu, 17 Jul 2003 07:45:39 -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 h6HBjawf003608;
	Thu, 17 Jul 2003 13:45:36 +0200
To: Randy Bush <randy@psg.com>
cc: ietf <ietf@ietf.org>
Subject: Re: in-addr.arpa missing 
In-reply-to: Your message of "Thu, 17 Jul 2003 10:00:42 +0200."
             <E19d3gw-000GmD-Ia@roam.psg.com> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 17 Jul 2003 13:45:36 +0200
Message-ID: <3606.1058442336@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-ietf@ietf.org
Precedence: bulk

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


For what it is worth, the wavesec network has a reverse map. 

Put:

option oe-key code 159 = string;
option oe-gateway code 160 = ip-address;
send oe-key = "16896 4 1 <some-base64>";

request subnet-mask, broadcast-address, time-offset, routers, 
	domain-name, domain-name-servers, host-name, oe-gateway;
require subnet-mask, routers, domain-name-servers, oe-gateway;

in your dhclient.conf, and you'll get an IP on the other network,
which has reverse. see www.wavesec.org. I don't know yet how to do
this for OS/X, or the LookOut OS.

We offered to help the hosts do the reverse map for the rest, but
it wasn't possible to get the right people there on Saturday/Sunday.

]                   At IETF57 in Wien, Austria                  |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] printk("Just another Debian GNU/Linux using, kernel hacking, security guy");[

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBPxaMX4qHRg3pndX9AQGYxQP+NyjTQql46P1RjKbw2c7jivx/mHv45tJI
JhKFeQGACUaxEAgoKYJU4utAJmEtnts8UiuyJg4J7xuEULEdM/raaYaCVmhLpFmV
yF/XMk1al5KXWsF+xYrw3x/bty6GoYp0XexDlhkdHJOQb7ORILFSsciyU0TWRX0I
jhQvyWw7lhQ=
=GH5u
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Thu Jul 17 08:18: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 IAA02980
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 08:18:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d7dZ-0003BR-1F
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 08:13:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d7cq-00035n-Ko
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 08:12:44 -0400
Received: from merlot.juniper.net (natint.juniper.net [207.17.136.129])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02633;
	Thu, 17 Jul 2003 08:12:40 -0400 (EDT)
Received: from kummer.juniper.net (kummer.juniper.net [172.17.12.90])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h6HC6gu35580;
	Thu, 17 Jul 2003 05:06:42 -0700 (PDT)
	(envelope-from kireeti@juniper.net)
Received: from localhost (kireeti@localhost)
	by kummer.juniper.net (8.11.6/8.9.3) with ESMTP id h6HC6gu13632;
	Thu, 17 Jul 2003 05:06:42 -0700 (PDT)
	(envelope-from kireeti@juniper.net)
X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs
Date: Thu, 17 Jul 2003 05:06:42 -0700 (PDT)
From: Kireeti Kompella <kireeti@juniper.net>
To: Jonathan Sadler <jonathan.sadler@tellabs.com>
cc: iesg@ietf.org, "" <ietf@ietf.org>, "" <ccamp@ops.ietf.org>
Subject: Re: Last Call: Routing Extensions in Support of Generalized MPLS 
 vto  Proposed Standard
In-Reply-To: <20030630033022.C32724@kummer.juniper.net>
Message-ID: <20030717043253.F13517@kummer.juniper.net>
References: <H0000c08064ac643.1044985131.mailw02@MHS> <3E59A5B4.880B91D2@tellabs.com>
 <20030630033022.C32724@kummer.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Betts, Brungard, Dotaro, Grammel, Kompella, Papadimitriou, Prattico,
Sadler, Vigoureux and Zinin got together to iron out the last few
issues in the document "Routing Extensions in Support of GMPLS".

In the interests of progressing this document in a timely fashion,
we examined these issues from two points of view:
a) is the current document set fundamentally broken, and if not, what
   caveats should be stated?
b) how do we move forward and address these issues, whether in the
   current doc set or in the future?

The consensus we reached for (a) is that the current doc set is okay in a
single layer network, but it doesn't capture inter-layer relationships.
So, we will state that in draft-ietf-ccamp-gmpls-routing-06.txt, and
then progress it.

As for (b), this will be one of the charter items for the ASON Routing
Reqts DT.  They will be chartered to state clearly what the requirements
are, what relations should be captured in a technology/layer independent
document, and what should be part of the layer-dependent documents.
These will then be addressed in future documents.

Many thanks to all who took part for getting together on such short
notice, and for the courteous and productive discussion!

Kireeti.



From owner-ietf@ietf.org  Thu Jul 17 08:33: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 IAA03663
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 08:33:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d7q8-0004Qh-Pk
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 08:26:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d7pv-0004My-RM
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 08: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 IAA03307
	for <ietf@ietf.org>; Thu, 17 Jul 2003 08:26:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d7pu-0005k8-00
	for ietf@ietf.org; Thu, 17 Jul 2003 08:26:14 -0400
Received: from hawk.mail.pas.earthlink.net ([207.217.120.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d7pk-0005k3-00
	for ietf@ietf.org; Thu, 17 Jul 2003 08:26:04 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by hawk.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19d7os-0003J9-00; Thu, 17 Jul 2003 05:25:10 -0700
Date: Thu, 17 Jul 2003 08:24:50 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "bill" <bill@strahm.net>
Cc: moore@cs.utk.edu, jstracke@centive.com, ietf@ietf.org
Subject: Re: re the plenary discussion on partial checksums
Message-Id: <20030717082450.414a16e2.moore@cs.utk.edu>
In-Reply-To: <008901c34c35$4674c020$1c02a8c0@mobilebill>
References: <20030716174503.76d66ff5.moore@cs.utk.edu>
	<008901c34c35$4674c020$1c02a8c0@mobilebill>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


] What bit is needed ?
] 
] Again, this is a layer 2 property.  If you want to receive layer 2
] frames with errors in them just get a Layer 2 device and tell it to not
] do the checksum calculation (much like you put an ethernet nic into
] Promiscous mode so it doesn't drop all of the frames not destined for
] it.

a) some apps can deal with lossage, some not.  so you want to control
   this on a per-packet basis
b) the L2 link in question may not be directly attached to the host
   that wants to control this - so you need a bit in the header that
   lets the sending host communicate to the link.
] 
] As for asking for end-end characterization of this, I think it is
] crazy... The bit can be in your IP header address fields(and on small
] ACK packets, statistically it WILL be there) so the packet wouldn't have
] even made it to your host, 

You have to make sure there's adequate protection for the IP header
(and the packet length) even when the payload isn't protected.  if the IP 
header is corrupted or the packet is a different length than when transmited
on the link, it still has to be dropped.

] it can be in the TCP port fields so it won't
] be received on the correct connection... 

I don't think this will ever be used with TCP.   This is for apps that don't
want to wait for retransmission of damaged packets, so they probably don't
want to wait for retransmission of lost packets either.

] I would have a hard time taking an IP header bit and making it the "Do
] not drop this packet in the presense of a bit error somewhere in the
] frame from layer 2 - layer 3".  Don't think it is a good idea.

I don't know where the bit comes from - there certainly aren't many bits left
in IPv4.  It could be a new protocol number, but that's ugly in a different way.
(and dare I say it, it won't work through existing NATs)



From owner-ietf@ietf.org  Thu Jul 17 10:49: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 KAA09828
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 10:49:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19d9rv-0001kn-HJ
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 10:36:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d9qF-0001fs-17
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 10:34: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 KAA09410
	for <ietf@ietf.org>; Thu, 17 Jul 2003 10:34:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d9qE-0006qf-00
	for ietf@ietf.org; Thu, 17 Jul 2003 10:34:42 -0400
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d9q3-0006qb-00
	for ietf@ietf.org; Thu, 17 Jul 2003 10:34:31 -0400
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5] helo=irams1.ira.uka.de)
	by iramx2.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10 (Debian))
	id 19d9pg-0000O9-00; Thu, 17 Jul 2003 16:34:08 +0200
Received: from localhost ([127.0.0.1] helo=i72mn12.tm.uka.de)
	by irams1.ira.uka.de with esmtp (Exim 3.30 #7 (Debian))
	id 19d9pg-0003Rr-00; Thu, 17 Jul 2003 16:34:08 +0200
Date: Thu, 17 Jul 2003 16:34:17 +0200
From: Roland Bless <bless@tm.uka.de>
To: Randy Bush <randy@psg.com>
Cc: ietf <ietf@ietf.org>
Subject: Re: in-addr.arpa missing
Message-Id: <20030717163417.6e2f7b74.bless@tm.uka.de>
In-Reply-To: <E19d3gw-000GmD-Ia@roam.psg.com>
References: <E19d3gw-000GmD-Ia@roam.psg.com>
Organization: Institute of Telematics, University of Karlsruhe
X-Mailer: Sylpheed version 0.9.3claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thu, 17 Jul 2003 10:00:42 +0200 Randy Bush <randy@psg.com> wrote:

> i received 81.160.221.53 via dhcp.  but
> 
> Host 53.221.160.81.in-addr.arpa not found: 3(NXDOMAIN)

:-(

Yes, I got the same result first. However, after enabling
my dhcp client to send my hostname, I obviously got a dynDNS
entry and reverse lookup works now.



From owner-ietf@ietf.org  Thu Jul 17 13:09: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 NAA13965
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 13:09:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dC7G-0004Rj-8F
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 13:00:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dC6K-0004PL-6a
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 12:59: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 MAA13732
	for <ietf@ietf.org>; Thu, 17 Jul 2003 12:59:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dC6J-0007hw-00
	for ietf@ietf.org; Thu, 17 Jul 2003 12:59:27 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dC67-0007hY-00
	for ietf@ietf.org; Thu, 17 Jul 2003 12:59:16 -0400
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200307171645.BAA11812@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id BAA11812; Fri, 18 Jul 2003 01:45:10 +0900
Subject: Re: re the plenary discussion on partial checksums
In-Reply-To: <77B9F4DB-B82F-11D7-B4D9-00039390397C@tzi.org> from Carsten Bormann
 at "Jul 17, 2003 10:20:04 am"
To: Carsten Bormann <cabo@tzi.org>
Date: Fri, 18 Jul 2003 01:45:09 +0859 ()
CC: John Stracke <jstracke@centive.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-ietf@ietf.org
Precedence: bulk

Gruesse, Carsten;

> > How would an app know to set this bit? The problem is that different 
> > L2s will have different likelihoods of corruption; you may decide that 
> > it's safe to set the bit on Ethernet, but not on 802.11*.
> 
> Aah, there's the confusion.  The apps we have in mind would think that 
> it is pointless (but harmless) to set the bit on Ethernet, but would be 
> quite interested in setting it on 802.11*.

If the application is voice and the datalink is SONET, it
may be fine to ignore some errors.

However, the problem, in general, is that packets are often
corrupted a lot to be almost meaningless even if the contents
is voice.

Still, it may be possible to design a datalink protocol to ignore
a few bits, but not beyond, of errors in packets.

But, it is, then, easy to have ECC to fix the errors that no
sane person design such protocol.

> in the middle.  (Reducing packet sizes to achieve a similar effect is 
> highly counterproductive on media with a very high per-packet overhead 
> such as 802.11.)  Of course, 802.11 has retransmissions, so maybe this 
> is a bad example, but it does illustrate the point.

The problem of 802.11 is that packets are often corrupted a lot
by collisions (from hidden terminals).

> *) e.g., in order to salvage half of a video packet that got an error 

You need extra check sum which consumes bandwidth.

Note that, for multicast case, you can't behave adaptively to all
the receivers that all the receivers suffer from the bandwidth loss.

							Masataka Ohta



From owner-ietf@ietf.org  Thu Jul 17 13:39:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14774
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 13:39:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dCf8-0006Sm-47
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 13:35:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dCf1-0006QO-IW
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 13:35: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 NAA14702
	for <IETF@ietf.org>; Thu, 17 Jul 2003 13:35:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dCf0-00009H-00
	for IETF@ietf.org; Thu, 17 Jul 2003 13:35:18 -0400
Received: from seka.erols.net ([207.96.1.96])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dCel-00009B-00
	for IETF@ietf.org; Thu, 17 Jul 2003 13:35:03 -0400
Received: from lords.seka.erols.net ([81.160.212.80])
	by seka.erols.net (8.11.6+Sun/8.9.1) with ESMTP id h6HHYWP13634
	for <IETF@ietf.org>; Thu, 17 Jul 2003 13:34:32 -0400 (EDT)
Message-Id: <5.1.1.6.2.20030717133024.03a22188@seka.erols.net>
X-Sender: enger@seka.erols.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Thu, 17 Jul 2003 13:34:27 -0400
To: IETF@ietf.org
From: "Robert M. Enger" <enger@seka.erols.net>
Subject: plenary power
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk



Perhaps a simple COTS product would have satisfied
the local public safety authorities:

http://www.cableorganizer.com/cord-protector-flexiduct/







From owner-ietf@ietf.org  Thu Jul 17 13:59: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 NAA15369
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 13:59:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dCwY-0007eA-2S
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 13:53:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dCvd-0007bb-Bs
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 13:52: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 NAA15234
	for <ietf@ietf.org>; Thu, 17 Jul 2003 13:52:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dCvc-0000Fs-00
	for ietf@ietf.org; Thu, 17 Jul 2003 13:52:28 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dCvR-0000Fl-00
	for ietf@ietf.org; Thu, 17 Jul 2003 13:52:17 -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 h6HHqLxS064036;
	Thu, 17 Jul 2003 19:52:21 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 17 Jul 2003 19:51:32 +0200
Subject: Re: re the plenary discussion on partial checksums
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: <20030717082450.414a16e2.moore@cs.utk.edu>
Message-Id: <4CE9BD25-B87F-11D7-8BCE-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, jul 17, 2003, at 14:24 Europe/Amsterdam, Keith Moore 
wrote:

> ] I would have a hard time taking an IP header bit and making it the 
> "Do
> ] not drop this packet in the presense of a bit error somewhere in the
> ] frame from layer 2 - layer 3".  Don't think it is a good idea.

> I don't know where the bit comes from - there certainly aren't many 
> bits left
> in IPv4.  It could be a new protocol number, but that's ugly in a 
> different way.
> (and dare I say it, it won't work through existing NATs)

Again: this seems like a perfect job for diffserv.




From owner-ietf@ietf.org  Thu Jul 17 14:37: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 OAA17065
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 14:37:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dDUP-0001A8-Qa
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 14:28:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dDSQ-00010s-3j
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 14:26:22 -0400
Received: from carwash.centivinc.com (carwash.centive.com [65.220.90.249])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA16707
	for <ietf@ietf.org>; Thu, 17 Jul 2003 14:26:18 -0400 (EDT)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003071714225821352
 for <ietf@ietf.org>; Thu, 17 Jul 2003 14:22:58 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 17 Jul 2003 14:10:54 -0400
Message-ID: <3F16E6AE.1080109@centive.com>
Date: Thu, 17 Jul 2003 14:10:54 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: re the plenary discussion on partial checksums
References: <BB3C1D2B.1CD0C%jonathan.hogg@seventh-wave-systems.com>
In-Reply-To: <BB3C1D2B.1CD0C%jonathan.hogg@seventh-wave-systems.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Jul 2003 18:10:54.0343 (UTC) FILETIME=[C3602170:01C34C8E]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jonathan Hogg wrote:

>On 17/7/03 8:30, bill wrote:
>  
>
>>I would have a hard time taking an IP header bit and making it the "Do
>>not drop this packet in the presense of a bit error somewhere in the
>>frame from layer 2 - layer 3".  Don't think it is a good idea.
>>    
>>
>What if that bit got corrupted?
>  
>
This is a good point.  If an L2 error can make a normal "discard on 
errors" packet come through marked as "tolerate errors", then 
implementing this feature can introduce errors in existing applications.

-- 
/==========================================================\
|John Stracke      |jstracke@centive.com                   |
|Principal Engineer|http://www.centive.com                 |
|Centive           |My opinions are my own.                |
|==========================================================|
|"Where's your sense of adventure?" "Hiding under the bed."|
\==========================================================/





From owner-ietf@ietf.org  Thu Jul 17 16:21: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 QAA21144
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 16:21:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dF57-0005kC-7w
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 16:10:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dF4D-0005hc-Jo
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 16:09: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 QAA20765
	for <ietf@ietf.org>; Thu, 17 Jul 2003 16:09:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dF48-00014Q-00
	for ietf@ietf.org; Thu, 17 Jul 2003 16:09:24 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dF3x-00014F-00
	for ietf@ietf.org; Thu, 17 Jul 2003 16:09:13 -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 VAA06144
	for <ietf@ietf.org>; Thu, 17 Jul 2003 21:08:33 +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 VAA04716
	for <ietf@ietf.org>; Thu, 17 Jul 2003 21:08:32 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h6HK8W020246
	for ietf@ietf.org; Thu, 17 Jul 2003 21:08:32 +0100
Date: Thu, 17 Jul 2003 21:08:32 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Vienna wireless/networking...
Message-ID: <20030717200832.GA20187@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

Randy's comments on the Vienna wireless at the IESG tonight are spot on.
The network's been great all week.

Given the WLAN problems seen in so many other events (IETF and otherwise) 
could I ask that the network be publicly documented as a guide for those 
providing WLAN in the future?   It would be really helpful.

The IPv6 has also been good when I've tried - less than 10ms to hop onto
either 6NET (for my home NREN access) or GEANT (for example for Japan)
from the venue :)   

I think there have been some IPv6 blips, but not through local problems.

Good job - and a high standard for Minneapolis to match!

Tim



From owner-ietf@ietf.org  Thu Jul 17 16:26: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 QAA21259
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 16:26:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dFGi-0006MX-KR
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 16:22:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19d4pa-00036C-LX
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 05:13:42 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24751
	for <ietf@ietf.org>; Thu, 17 Jul 2003 05:13:38 -0400 (EDT)
Received: from [127.0.0.1] (helo=roam.psg.com ident=root)
	by psg.com with esmtp (Exim 4.14)
	id 19d4kj-000Gkz-5o
	for ietf@ietf.org; Thu, 17 Jul 2003 09:08:41 +0000
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.20)
	id 19d4ki-000Gs2-5V
	for ietf@ietf.org; Thu, 17 Jul 2003 11:08:40 +0200
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 17 Jul 2003 11:08:39 +0200
To: ietf <ietf@ietf.org>
Subject: help wanted
Message-Id: <E19d4ki-000Gs2-5V@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

we need a few good wg chairs.  expertise in one of v6, radius, or
wireless necessary.  experience with operations and ietf process
are major plusses.  ability to catch me in corridors is also a
plus :-)

randy






From owner-ietf@ietf.org  Thu Jul 17 17:01: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 RAA22637
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 17:01:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dFme-0008HN-HN
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 16:55:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dFge-00083k-HS
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 16: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 QAA22158
	for <ietf@ietf.org>; Thu, 17 Jul 2003 16:49:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dFgd-0001I2-00
	for ietf@ietf.org; Thu, 17 Jul 2003 16:49:11 -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 19dFgS-0001Hq-00
	for ietf@ietf.org; Thu, 17 Jul 2003 16:49:00 -0400
Received: from limbo (limbo.unfix.org [10.100.13.33])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 0C7AF7F42; Thu, 17 Jul 2003 22:48:21 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Tim Chown'" <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
Subject: RE: Vienna wireless/networking...
Date: Thu, 17 Jul 2003 22:48:19 +0200
Organization: Unfix
Message-ID: <055f01c34ca4$c46f4580$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
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <20030717200832.GA20187@login.ecs.soton.ac.uk>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Tim Chown wrote:

<SNIP>
> The IPv6 has also been good when I've tried - less than 10ms=20
> to hop onto either 6NET (for my home NREN access) or GEANT
> (for example for Japan) from the venue :)  =20

I heared a lot of complaints to anything outside 6net/geant/dante =
though.

Watching the looking glasses reveals that 6net/geant/dante
simply don't peer enough with commercial ISP's.

Good example is the www.deepspace6.net thread.

For example, a simply trace from my home to that box:

traceroute to deepspace6.net (3ffe:8300:0:1:10:a7ff:fe16:27f4) from
3ffe:8114:2000:240:290:27ff:fe24:bbab, 30 hops max, 16 byte packets
 1  purgatory.unfix.org (3ffe:8114:2000:240:290:27ff:fe24:c19f)  2.6 ms
2.216 ms  2.078 ms
 2  gw-20.ams-02.nl.sixxs.net (3ffe:8114:1000::26)  20.494 ms  21.748 ms
21.354 ms
 3  2001:6e0::2 (2001:6e0::2)  20.647 ms  21.43 ms  20.869 ms
 4  gw-viagenie-cnit.ipv6.cnit.it (3ffe:830f::3)  127.75 ms  127.818 ms
128.406 ms
 5  gw-cnit-viagenie.ipv6.cnit.it (3ffe:830f::2)  292.836 ms *  292.115 =
ms
 6  gw-fe-na.ipv6.cnit.it (3ffe:8300::4)  314.947 ms *  316.817 ms
 7  3ffe:8300:0:1:10:a7ff:fe16:27f4 (3ffe:8300:0:1:10:a7ff:fe16:27f4)
318.12 ms  316.753 ms  320.819 ms

gw-viagenie-cnit, aha we are going over the US?
That would look like intouch at AMS-IX would have bad connectivity,
even though I know that AMS-IX is one of the better places to peer with
IPv6.

And now the fun part, same box, RIR prefix:

jeroen@heaven:~$ traceroute6 www.deepspace6.net
traceroute to deepspace6.net (2001:760:204:10:10:a7ff:fe16:27f4) from
3ffe:8114:2000:240:290:27ff:fe24:bbab, 30 hops max, 16 byte packets
 1  purgatory.unfix.org (3ffe:8114:2000:240:290:27ff:fe24:c19f)  9.787 =
ms
1.627 ms  1.924 ms
 2  gw-20.ams-02.nl.sixxs.net (3ffe:8114:1000::26)  50.029 ms  20.31 ms
20.147 ms
 3  2001:6e0::2 (2001:6e0::2)  19.823 ms  20.262 ms  20.967 ms
 4  gw.ipv6.lt (2001:778:11:5::1)  80.526 ms  79.947 ms  79.496 ms
 5  2001:6e0:0:10f::2 (2001:6e0:0:10f::2)  68.388 ms  68.343 ms  68.664 =
ms
 6  6net-gw.nordu.net (2001:948:0:f008::1)  70.851 ms  69.125 ms  69.524 =
ms
 7  * * *
 8  * * *
 9  *

http://www.sixxs.net/tools/grh/lg/?prefix=3D3ffe:8300::/28&matchtype=3Dmo=
re
http://www.sixxs.net/tools/grh/lg/?prefix=3D2001:760::/32&matchtype=3Dmor=
e

Backs this up, where you can see that most 'transit' goes over viagenie =
=3D=3D
us.
PS: Both 2001:760::/32 and 2001:760::/35 are announced with different =
paths
;)

Note that the IETF prefix, apparently has a somewhat better route
mysteriously:

http://www.sixxs.net/tools/grh/lg/?prefix=3D2001:7f9:8400:d1::/32&matchty=
pe=3Dmo
re

jeroen@heaven:~$ traceroute6 2001:7f9:8400:d1::2
traceroute to 2001:7f9:8400:d1::2 (2001:7f9:8400:d1::2) from
3ffe:8114:2000:240:290:27ff:fe24:bbab, 30 hops max, 16 byte packets
 1  purgatory.unfix.org (3ffe:8114:2000:240:290:27ff:fe24:c19f)  1.191 =
ms
1.427 ms  1.274 ms
 2  gw-20.ams-02.nl.sixxs.net (3ffe:8114:1000::26)  19.896 ms  20.129 ms
20.081 ms
 3  2001:6e0::2 (2001:6e0::2)  29.802 ms  20.869 ms  20.15 ms
 4  gw.ipv6.lt (2001:778:11:5::1)  79.846 ms  81.081 ms  79.084 ms
 5  * * *
 6  * * *
 7  * * *
 8  aconet-gw.at1.at.geant.net (2001:798:2010:10dd::2)  79.834 ms  =
78.767 ms
79.544 ms
 9  2001:628:4fe::8447 (2001:628:4fe::8447)  80.355 ms  80.578 ms  =
80.872 ms
10  2001:890:600:4f1::2 (2001:890:600:4f1::2)  81.057 ms  80.481 ms  =
81.882
ms
Borked, jups indeed 6net has great connectivity, when you stay in the
acedemic world...

Not traceable though, and ofcourse quite asynchronous...

</sarcasme>

Greets,
 Jeroen




From owner-ietf@ietf.org  Thu Jul 17 17:21: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 RAA23102
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 17:21:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dG60-0001B3-FT
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 17:15:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dG55-00018I-Uu
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 17:14:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22979
	for <ietf@ietf.org>; Thu, 17 Jul 2003 17:14:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dG54-0001Tp-00
	for ietf@ietf.org; Thu, 17 Jul 2003 17:14:26 -0400
Received: from heron.mail.pas.earthlink.net ([207.217.120.189])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dG4P-0001TR-00
	for ietf@ietf.org; Thu, 17 Jul 2003 17:13:45 -0400
Received: from [81.160.15.244] (helo=STJOHNS-LAPTOP2.mindspring.com)
	by heron.mail.pas.earthlink.net with asmtp (TLSv1:RC4-SHA:128)
	(Exim 3.33 #1)
	id 19dG25-0001DC-00
	for ietf@ietf.org; Thu, 17 Jul 2003 14:11:21 -0700
Message-Id: <6.0.0.12.2.20030717163927.041605c8@pop.mindspring.com>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.12 (Beta)
Date: Thu, 17 Jul 2003 17:11:18 -0400
To: ietf@ietf.org
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Critique vs Criticism - Plenary comments
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-ELNK-Trace: 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4d597a6088feec769992a9f37f519c66ab350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
Sender: owner-ietf@ietf.org
Precedence: bulk

Folks -

I want to make a further comment about tonight's discussion about the site 
and site logistics.  I'd like to ask all of you to listen to the discussion 
less as a bashing of the local host and the city and people of Vienna, and 
more as I think it was intended - a critique of the site and facilities as 
they relate to serving the needs of the IETF.  The person who started the 
discussion made at least three separate points related to the facilities - 
at no time did he impugn or otherwise denigrate Vienna, the people of 
Vienna, or the local host.

The points were (as near as I remember) - that the geographic separation of 
hotel and meeting facilities was a problem, that there were power issues in 
the rooms both related to the amount and to the location, and that there 
was no water in any of the rooms until the near the end.

We've had meetings with geographic separation before - mostly this causes 
problems in the formation of the usual IETF bar BOFs.  Going back to the 
beginning of the IETF, much of the small group discussion at the IETF has 
taken place after or between the session in and around the bar at the 
conference hotel.  Quite a lot of the ideas which have made it into the 
standards process have started because of the free flow of information and 
the liberal application of two or three beers.  The Bar BOF is a well 
established part of the IETF meeting culture and meetings without an 
obvious place to meet post session have generally been less productive.

The power issues are more properly the purview of the facility (e.g. the 
conference center) coordinator.  Letting the secretariat know about the 
problem is both appropriate and helpful for their evaluation of the 
facility for possible later use.

The lack of water, drinking fountains, cups, etc was frankly painful to 
me.  This was attributed to the policy of the conference facility... maybe 
I'm spoiled, but I found this policy strange and unusual and not applicable 
to any of the other facilities we've met at previously.


I do want to echo Randy Bush and others with thanks to the host for an 
excellent wireless system and network.  I didn't have to fall back once to 
the terminal room, so I can't comment on good/bad there.

Please, let's try and take comments at face value and not treat the people 
making them like they're trying to kick your puppy.

Thanks - Mike

ps - I've been to 55 of the IETF meetings...  I get to comment from time to 
time.




From owner-ietf@ietf.org  Thu Jul 17 17:44: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 RAA23663
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Jul 2003 17:44:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dGTE-0002fS-Ha
	for ietf-list@asgard.ietf.org; Thu, 17 Jul 2003 17:39:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dGSg-0002cU-Oa
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 17:38: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 RAA23527
	for <ietf@ietf.org>; Thu, 17 Jul 2003 17:38:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dGSa-0001bs-00
	for ietf@ietf.org; Thu, 17 Jul 2003 17:38:44 -0400
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dGSP-0001bd-00
	for ietf@ietf.org; Thu, 17 Jul 2003 17:38:33 -0400
Received: from amalisxp.attbi.com (unknown[81.160.15.138](misconfigured sender))
          by attbi.com (rwcrmhc12) with SMTP
          id <2003071721373601400s5n98e>; Thu, 17 Jul 2003 21:37:37 +0000
Message-Id: <6.0.0.10.0.20030717173519.045137b0@mail.attbi.com>
X-Sender: andymalis@mail.attbi.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.10 (Beta)
Date: Thu, 17 Jul 2003 17:35:38 -0400
To: ietf@ietf.org
From: "Andrew G. Malis" <andymalis@attbi.com>
Subject: Two lost SecureID tokens found at the Crown Plaza
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

Two lost SecureID tokens have been found at the Crown Plaza Hotel.  One was 
found on the second floor today (Thursday), and the other was found 
Wednesday evening in the lounge.  They have been given to lost and found in 
the hotel.

Andy Malis and Bert Wijnen




From owner-ietf@ietf.org  Fri Jul 18 04:08: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 EAA21753
	for <ietf-web-archive@odin.ietf.org>; Fri, 18 Jul 2003 04:08:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dPyV-0008AA-RP
	for ietf-list@asgard.ietf.org; Fri, 18 Jul 2003 03:48:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dPy7-00088x-Qr
	for ietf@asgard.ietf.org; Fri, 18 Jul 2003 03:47: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 DAA21264
	for <ietf@ietf.org>; Fri, 18 Jul 2003 03:47:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dPy5-00067d-00
	for ietf@ietf.org; Fri, 18 Jul 2003 03:47:53 -0400
Received: from [131.130.119.250] (helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dPxu-00067V-00
	for ietf@ietf.org; Fri, 18 Jul 2003 03:47:42 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h6I7hcF22527
	for <ietf@ietf.org>; Fri, 18 Jul 2003 09:43:38 +0200
Message-ID: <3F17A52A.3030205@it.su.se>
Date: Fri, 18 Jul 2003 09:43:38 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: more stuff that was good
X-Enigmail-Version: 0.76.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Coffee - transparency is not always a good thing :-) Food for thought 
for IETFs in the US.

       Cheers Leif




From owner-ietf@ietf.org  Fri Jul 18 04:10: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 EAA21836
	for <ietf-web-archive@odin.ietf.org>; Fri, 18 Jul 2003 04:10:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dQFx-00009M-9Z
	for ietf-list@asgard.ietf.org; Fri, 18 Jul 2003 04:06:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dQFX-00006P-OQ
	for ietf@asgard.ietf.org; Fri, 18 Jul 2003 04:05:55 -0400
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21697
	for <ietf@ietf.org>; Fri, 18 Jul 2003 04:05:52 -0400 (EDT)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id EAA09981
	for <ietf@ietf.org>; Fri, 18 Jul 2003 04:02:07 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id EAA09959
	for <ietf@ietf.org>; Fri, 18 Jul 2003 04:02:06 -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: Critique vs Criticism - Plenary comments
Date: Fri, 18 Jul 2003 11:04:50 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9A0E@is0004avexu1.global.avaya.com>
Thread-Topic: Critique vs Criticism - Plenary comments
Thread-Index: AcNMqagEybxjS2yATDyaSxc9vGXZegAWH7fg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Michael StJohns" <mstjohns@mindspring.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

These facilities discussions! As my wife said - did you finish all =
technical subjects to talk about?

But what the ... I have also attended 30+ IETF meetings, so let me =
comment on two details issues:

1. 'Bar BOF' - what was exactly the problem in Vienna? That there was no =
bar, with TV loudly shouting CNN or ESPN? On the other hand there was a =
sandwich bar, you could buy drinks (including beer), or had them for =
free (excluding beer) for most of the time. There was plenty of sitting =
space around, and I had at least three editing sessions during the week. =
Much, much better than in San Francisco for example.=20
2. Water was brought in rooms on Wednesday morning, which is rather =
middle of the week, not 'near the end'.

BTW,  I am still waiting to attend an IETF meeting in a US facility =
serving decent coffee. In Vienna, there was plenty of it, and we did not =
have to pour it by ourselves :-)

Dan


> -----Original Message-----
> From: Michael StJohns [mailto:mstjohns@mindspring.com]
> Sent: 18 July, 2003 12:11 AM
> To: ietf@ietf.org
> Subject: Critique vs Criticism - Plenary comments
>=20
>=20
> Folks -
>=20
> I want to make a further comment about tonight's discussion=20
> about the site=20
> and site logistics.  I'd like to ask all of you to listen to=20
> the discussion=20
> less as a bashing of the local host and the city and people=20
> of Vienna, and=20
> more as I think it was intended - a critique of the site and=20
> facilities as=20
> they relate to serving the needs of the IETF.  The person who=20
> started the=20
> discussion made at least three separate points related to the=20
> facilities -=20
> at no time did he impugn or otherwise denigrate Vienna, the people of=20
> Vienna, or the local host.
>=20
> The points were (as near as I remember) - that the geographic=20
> separation of=20
> hotel and meeting facilities was a problem, that there were=20
> power issues in=20
> the rooms both related to the amount and to the location, and=20
> that there=20
> was no water in any of the rooms until the near the end.
>=20
> We've had meetings with geographic separation before - mostly=20
> this causes=20
> problems in the formation of the usual IETF bar BOFs.  Going=20
> back to the=20
> beginning of the IETF, much of the small group discussion at=20
> the IETF has=20
> taken place after or between the session in and around the bar at the=20
> conference hotel.  Quite a lot of the ideas which have made=20
> it into the=20
> standards process have started because of the free flow of=20
> information and=20
> the liberal application of two or three beers.  The Bar BOF is a well=20
> established part of the IETF meeting culture and meetings without an=20
> obvious place to meet post session have generally been less=20
> productive.
>=20
> The power issues are more properly the purview of the=20
> facility (e.g. the=20
> conference center) coordinator.  Letting the secretariat know=20
> about the=20
> problem is both appropriate and helpful for their evaluation of the=20
> facility for possible later use.
>=20
> The lack of water, drinking fountains, cups, etc was frankly=20
> painful to=20
> me.  This was attributed to the policy of the conference=20
> facility... maybe=20
> I'm spoiled, but I found this policy strange and unusual and=20
> not applicable=20
> to any of the other facilities we've met at previously.
>=20
>=20
> I do want to echo Randy Bush and others with thanks to the=20
> host for an=20
> excellent wireless system and network.  I didn't have to fall=20
> back once to=20
> the terminal room, so I can't comment on good/bad there.
>=20
> Please, let's try and take comments at face value and not=20
> treat the people=20
> making them like they're trying to kick your puppy.
>=20
> Thanks - Mike
>=20
> ps - I've been to 55 of the IETF meetings...  I get to=20
> comment from time to=20
> time.
>=20
>=20
>=20



From owner-ietf@ietf.org  Fri Jul 18 04:37: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 EAA22940
	for <ietf-web-archive@odin.ietf.org>; Fri, 18 Jul 2003 04:37:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dQg4-0003uA-3w
	for ietf-list@asgard.ietf.org; Fri, 18 Jul 2003 04:33:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dQfF-0003t3-O2
	for ietf@asgard.ietf.org; Fri, 18 Jul 2003 04:32:29 -0400
Received: from p2.piuha.net (p2.piuha.net [131.160.192.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22819
	for <ietf@ietf.org>; Fri, 18 Jul 2003 04:32:26 -0400 (EDT)
Received: from piuha.net (p4.piuha.net [131.160.192.4])
	by p2.piuha.net (Postfix) with ESMTP id 0E2AB6A906
	for <ietf@ietf.org>; Fri, 18 Jul 2003 11:27:27 +0300 (EEST)
Message-ID: <3F17AED5.5040600@piuha.net>
Date: Fri, 18 Jul 2003 11:24:53 +0300
From: Jari Arkko <jari.arkko@piuha.net>
Reply-To: jari.arkko@piuha.net
Organization: None
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: IETF locations
References: <3F17A52A.3030205@it.su.se>
In-Reply-To: <3F17A52A.3030205@it.su.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I'd like to thank the local hosts for organizing such a good meeting.
In terms of overall service level, this has been one of the best
meetings ever. No network problems that I could see, excellent
social event, t-shirts, bags, very nice city, ... Yeah next time we
need more powerplugs, but I hear that is something that the
secretariat can request from the hotel -- if it costs extra
then so be it, it has to be done even for safety reasons.

Someone complained yesterday that the subway stopped running
too early. I actually thought it was very positive that there
*was* a subway system, unlike in many of the other places
we've been to... Of course the closer the hotels are to the
meeting place, the better. But it wasn't too bad, actually,
for me it took 20 minutes to get here and I was quite far
away.

I say we need more meetings in Europe.

--Jari




From owner-ietf@ietf.org  Fri Jul 18 04:39: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 EAA23015
	for <ietf-web-archive@odin.ietf.org>; Fri, 18 Jul 2003 04:39:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dQix-0003y0-OR
	for ietf-list@asgard.ietf.org; Fri, 18 Jul 2003 04:36:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dQiw-0003wj-5f
	for ietf@asgard.ietf.org; Fri, 18 Jul 2003 04:36:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22905
	for <ietf@ietf.org>; Fri, 18 Jul 2003 04:36:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dQit-0006UL-00
	for ietf@ietf.org; Fri, 18 Jul 2003 04:36:15 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dQij-0006Te-00
	for ietf@ietf.org; Fri, 18 Jul 2003 04:36:05 -0400
Received: from cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 18 Jul 2003 01:39:08 -0700
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h6I8Y7uD009304
	for <ietf@ietf.org>; Fri, 18 Jul 2003 01:34:08 -0700 (PDT)
Received: (ole@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) id BAA21378; Fri, 18 Jul 2003 01:34:07 -0700 (PDT)
X-Authentication-Warning: wells.cisco.com: ole set sender to ole@cisco.com using -f
Date: Fri, 18 Jul 2003 01:34:07 -0700 (PDT)
From: "Ole J. Jacobsen" <ole@cisco.com>
Reply-To: Ole Jacobsen <ole@cisco.com>
To: The IETF <ietf@ietf.org>
Subject: Korean cell phones
Message-ID: <Pine.HPX.4.44.0307180125120.10543-100000@wells.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


In response to my comments at the plenary, the situation in Korea is a bit
more complex than "they have their own incompatible system". In summary:

- GSM is very limited, if at all existent (I found one network listed as
  "planned for Sept  2003")

- Some pages claim "not compatible with your US handset" -- i.e. no
  CDMA roaming

- Many pages offer rentals

- Some providers appear to offer roaming using your GSM SIM card in a
  Korean CDMA handset (unless I got that all wrong)

Google for "Korean Cell Phones" or "Roaming in Korea" for more info.

Otherwise, I am pretty sure you can get a phone and a prepaid service for
something reasonable, but I will know more when I visit there in 30 days.

Since Samsung is the sponsor, why not just include a phone for each
attendee in the registration packet in stead of a T-shirt? :-)

Cheers,

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj






From owner-ietf@ietf.org  Fri Jul 18 05:29:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24528
	for <ietf-web-archive@odin.ietf.org>; Fri, 18 Jul 2003 05:29:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dRPX-0005ew-L8
	for ietf-list@asgard.ietf.org; Fri, 18 Jul 2003 05:20:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dROk-0005e2-VK
	for ietf@asgard.ietf.org; Fri, 18 Jul 2003 05:19: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 FAA24234
	for <ietf@ietf.org>; Fri, 18 Jul 2003 05:19:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dROi-0006th-00
	for ietf@ietf.org; Fri, 18 Jul 2003 05:19:28 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dROS-0006tU-00
	for ietf@ietf.org; Fri, 18 Jul 2003 05:19:13 -0400
Received: (from falk@localhost)
	by nit.isi.edu (8.11.6/8.11.6) id h6I9ImC21013
	for ietf@ietf.org; Fri, 18 Jul 2003 02:18:48 -0700
Date: Fri, 18 Jul 2003 02:18:48 -0700
From: Aaron Falk <falk@isi.edu>
To: ietf@ietf.org
Subject: when is the wireless going away?
Message-ID: <20030718091848.GS19946@isi.edu>
Mail-Followup-To: ietf@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

-in the Austria Center?

-in the Crowne Plaza?

Inquiring minds want to know.

--aaron



From owner-ietf@ietf.org  Fri Jul 18 05:49:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25239
	for <ietf-web-archive@odin.ietf.org>; Fri, 18 Jul 2003 05:49:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dRnj-0006fz-GD
	for ietf-list@asgard.ietf.org; Fri, 18 Jul 2003 05:45:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dRmS-0006eD-T2
	for ietf@asgard.ietf.org; Fri, 18 Jul 2003 05:44:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25129
	for <ietf@ietf.org>; Fri, 18 Jul 2003 05:43:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dRmQ-00079d-00
	for ietf@ietf.org; Fri, 18 Jul 2003 05:43:58 -0400
Received: from nmh.informatik.uni-bremen.de ([134.102.224.3] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dRmF-00079G-00
	for ietf@ietf.org; Fri, 18 Jul 2003 05:43:47 -0400
Received: from tzi.org (nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.12.9/8.12.9) with ESMTP id h6I9ghWF015623;
	Fri, 18 Jul 2003 11:42:47 +0200 (MEST)
Date: Fri, 18 Jul 2003 11:42:34 +0200
Subject: Re: Korean cell phones
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Carsten Bormann <cabo@tzi.org>, The IETF <ietf@ietf.org>
To: Ole Jacobsen <ole@cisco.com>
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <Pine.HPX.4.44.0307180125120.10543-100000@wells.cisco.com>
Message-Id: <289E365F-B904-11D7-B4D9-00039390397C@tzi.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> - Some pages claim "not compatible with your US handset" -- i.e. no
>   CDMA roaming

Ole,

I remember from the last time I worked on Korean CDMA systems they had 
a different frequency (1700 MHz?).

Gruesse, Carsten




From owner-ietf@ietf.org  Fri Jul 18 09:30: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 JAA29635
	for <ietf-web-archive@odin.ietf.org>; Fri, 18 Jul 2003 09:30:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dVBh-0001o4-QZ
	for ietf-list@asgard.ietf.org; Fri, 18 Jul 2003 09:22:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dFo8-0008Qq-Ug
	for ietf@asgard.ietf.org; Thu, 17 Jul 2003 16:56: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 QAA22333;
	Thu, 17 Jul 2003 16:56:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dFo7-0001Jz-00; Thu, 17 Jul 2003 16:56:55 -0400
Received: from 64.221.212.133.ptr.us.xo.net ([64.221.212.133] helo=vivacenetworks.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dFnw-0001Jk-00; Thu, 17 Jul 2003 16:56:44 -0400
Received: from AMALISXP.tellabs.com ([10.120.0.2]) by vivacenetworks.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 17 Jul 2003 13:55:49 -0700
Message-Id: <6.0.0.10.0.20030717165317.045137b0@po1.vivacenetworks.com>
X-Sender: vivacenet\amalis@po1.vivacenetworks.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.10 (Beta)
Date: Thu, 17 Jul 2003 16:55:43 -0400
To: ietf@ietf.org, iesg-secretary@ietf.org
From: "Andrew G. Malis" <andy.malis@tellabs.com>
Subject: Two lost SecureID tokens found at the Crown Plaza
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 17 Jul 2003 20:55:50.0131 (UTC) FILETIME=[CDB98C30:01C34CA5]
Sender: owner-ietf@ietf.org
Precedence: bulk

Two lost SecureID tokens have been found at the Crown Plaza Hotel.  One was 
found on the second floor today (Thursday), and the other was found 
Wednesday evening in the lounge.  They have been given to lost and found in 
the hotel.

Andy Malis and Bert Wijnen






From owner-ietf@ietf.org  Fri Jul 18 11:06: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 LAA03425
	for <ietf-web-archive@odin.ietf.org>; Fri, 18 Jul 2003 11:06:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dWfd-0001Wf-BJ
	for ietf-list@asgard.ietf.org; Fri, 18 Jul 2003 10:57:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dWf3-0001Vq-8v
	for ietf@asgard.ietf.org; Fri, 18 Jul 2003 10:56: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 KAA03196
	for <ietf@ietf.org>; Fri, 18 Jul 2003 10:56:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dWf2-0001Tk-00
	for ietf@ietf.org; Fri, 18 Jul 2003 10:56:40 -0400
Received: from buffoon.automagic.org ([208.185.30.208] ident=qmailr)
	by ietf-mx with smtp (Exim 4.12)
	id 19dWer-0001Td-00
	for ietf@ietf.org; Fri, 18 Jul 2003 10:56:29 -0400
Received: (qmail 76888 invoked by uid 0); 18 Jul 2003 14:56:09 -0000
Received: from localhost.automagic.org (HELO isc.org) (root@127.0.0.1)
  by localhost.automagic.org with SMTP; 18 Jul 2003 14:56:09 -0000
Date: Fri, 18 Jul 2003 10:56:07 -0400
Subject: Re: Korean cell phones
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: The IETF <ietf@ietf.org>
To: Ole Jacobsen <ole@cisco.com>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <Pine.HPX.4.44.0307180125120.10543-100000@wells.cisco.com>
Message-Id: <F6709FD8-B92F-11D7-9A86-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Friday, Jul 18, 2003, at 04:34 Canada/Eastern, Ole J. Jacobsen wrote:

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


Joe




From owner-ietf@ietf.org  Fri Jul 18 14:07: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 OAA06760
	for <ietf-web-archive@odin.ietf.org>; Fri, 18 Jul 2003 14:07:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dZRr-0003pN-Tj
	for ietf-list@asgard.ietf.org; Fri, 18 Jul 2003 13:55:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dZRL-0003ok-My
	for ietf@asgard.ietf.org; Fri, 18 Jul 2003 13:54:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06434
	for <ietf@ietf.org>; Fri, 18 Jul 2003 13:54:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dZRK-0002I0-00
	for ietf@ietf.org; Fri, 18 Jul 2003 13:54:42 -0400
Received: from tx2.citynet.net ([66.118.64.13] ident=[jSZiJp3mPxNPt9al9K/16z+4ulJ7po8E])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dZR9-0002HM-00
	for ietf@ietf.org; Fri, 18 Jul 2003 13:54:31 -0400
Received: from a (dhcp-69-43-8-056.park.dialup.citynet.net [69.43.8.56])
	by tx2.citynet.net (8.12.9/8.12.6=Outbound) with SMTP id h6IHo2HN007590
	for <ietf@ietf.org>; Fri, 18 Jul 2003 13:50:03 -0400
Message-ID: <001c01c34d55$24a72ac0$38082b45@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: <ietf@ietf.org>
Subject: IETF meeting 
Date: Fri, 18 Jul 2003 13:50:56 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

All you lucky guys who got to go to the meeting just have to rub it in.

    Bill





From owner-ietf@ietf.org  Fri Jul 18 14:09: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 OAA06850
	for <ietf-web-archive@odin.ietf.org>; Fri, 18 Jul 2003 14:09:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dZbX-0003w9-RW
	for ietf-list@asgard.ietf.org; Fri, 18 Jul 2003 14:05:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dZal-0003vT-Hz
	for ietf@asgard.ietf.org; Fri, 18 Jul 2003 14:04:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06697
	for <ietf@ietf.org>; Fri, 18 Jul 2003 14:04:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dZak-0002Le-00
	for ietf@ietf.org; Fri, 18 Jul 2003 14:04:26 -0400
Received: from tx1.citynet.net ([66.118.64.12] helo=tx1.wvinternetservices.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dZaZ-0002LY-00
	for ietf@ietf.org; Fri, 18 Jul 2003 14:04:15 -0400
Received: from a (dhcp-69-43-8-056.park.dialup.citynet.net [69.43.8.56])
	by tx1.wvinternetservices.com (8.12.9/8.12.6=Outbound) with SMTP id h6II2aHm018580
	for <ietf@ietf.org>; Fri, 18 Jul 2003 14:02:40 -0400
Message-ID: <000701c34d56$de6b3540$38082b45@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: <ietf@ietf.org>
Subject: Meeting
Date: Fri, 18 Jul 2003 14:03:15 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

By the way. Ted Tytso did you get to go to the meeting? Did IBM fund it for
you?

    Bill





From owner-ietf@ietf.org  Fri Jul 18 15:35: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 PAA10880
	for <ietf-web-archive@odin.ietf.org>; Fri, 18 Jul 2003 15:35:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19datr-0005Kj-M5
	for ietf-list@asgard.ietf.org; Fri, 18 Jul 2003 15:28:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19datB-0005K6-GF
	for ietf@asgard.ietf.org; Fri, 18 Jul 2003 15:27: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 PAA10567
	for <ietf@ietf.org>; Fri, 18 Jul 2003 15:27:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19datA-0002vG-00
	for ietf@ietf.org; Fri, 18 Jul 2003 15:27:32 -0400
Received: from twix.hotpop.com ([204.57.55.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dasz-0002ud-00
	for ietf@ietf.org; Fri, 18 Jul 2003 15:27:21 -0400
Received: from hotpop.com (kubrick.hotpop.com [204.57.55.16])
	by twix.hotpop.com (Postfix) with SMTP id 383364A3BB2
	for <ietf@ietf.org>; Fri, 18 Jul 2003 19:25:57 +0000 (UTC)
Received: from hotpop.com (dsl092-168-196.wdc1.dsl.speakeasy.net [66.92.168.196])
	by smtp-2.hotpop.com (Postfix) with ESMTP
	id 68AA21800B5; Fri, 18 Jul 2003 19:26:00 +0000 (UTC)
From: Dave Aronson <dja2003@hotpop.com>
To: "Bill Cunningham" <billc44@citynet.net>, <ietf@ietf.org>
Subject: Re: IETF meeting
Date: Fri, 18 Jul 2003 15:29:29 -0400
User-Agent: KMail/1.5
References: <001c01c34d55$24a72ac0$38082b45@a>
In-Reply-To: <001c01c34d55$24a72ac0$38082b45@a>
Approved: Look, Ah say, look at me when Ah'm typin' at yew, boah!
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200307181529.29909.dja2003@hotpop.com>
X-HotPOP: -----------------------------------------------
                   Sent By HotPOP.com FREE Email
             Get your FREE POP email at www.HotPOP.com
          -----------------------------------------------
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

"Bill Cunningham" <billc44@citynet.net> wrote:

 > All you lucky guys who got to go to the meeting just have to rub it
 > in.

Maybe next time, those of us who can't go, should organize local IETF 
Pity Parties.  Some clubs I'm in do this during their big annual bashes.

-- 
David J. Aronson, Unemployed Software Engineer in the Washington DC area
See http://destined.to/program for online resume, and other information.





From owner-ietf@ietf.org  Sat Jul 19 10:32: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 KAA15555
	for <ietf-web-archive@odin.ietf.org>; Sat, 19 Jul 2003 10:32:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dsTU-00075J-BL
	for ietf-list@asgard.ietf.org; Sat, 19 Jul 2003 10:14:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dsSy-0006wI-KA
	for ietf@asgard.ietf.org; Sat, 19 Jul 2003 10:13: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 KAA15085
	for <ietf@ietf.org>; Sat, 19 Jul 2003 10:13:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dsSx-0002Kn-00
	for ietf@ietf.org; Sat, 19 Jul 2003 10:13:39 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dsSn-0002KW-00
	for ietf@ietf.org; Sat, 19 Jul 2003 10:13:29 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 3F96161B87
	for <ietf@ietf.org>; Sat, 19 Jul 2003 16:12:53 +0200 (CEST)
Date: Sat, 19 Jul 2003 12:56:32 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: IETF financials for 2002, and budget for 2003
Message-ID: <47501253.1058619392@localhost>
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

These are now up on the Chair's web page.

http://www.ietf.org/u/chair/

The budget is modified since the March presentation; the financials for 
2003 are the same.

                   Harald




From owner-ietf@ietf.org  Sat Jul 19 14:30: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 OAA19475
	for <ietf-web-archive@odin.ietf.org>; Sat, 19 Jul 2003 14:30:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19dwKU-0001B1-GS
	for ietf-list@asgard.ietf.org; Sat, 19 Jul 2003 14:21:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19dwKQ-0001Aa-Sa
	for ietf@asgard.ietf.org; Sat, 19 Jul 2003 14:21: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 OAA19347;
	Sat, 19 Jul 2003 14:21:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dwKP-0003Vo-00; Sat, 19 Jul 2003 14:21:05 -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 19dwKE-0003V8-00; Sat, 19 Jul 2003 14:20:54 -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 h6JIK0mH027500;
	Sat, 19 Jul 2003 11:20:00 -0700 (PDT)
Date: Sat, 19 Jul 2003 11:19:59 -0700
From: Marshall Rose <mrose@dbc.mtview.ca.us>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: Dave Crocker <dcrocker@brandenburg.com>, iesg@ietf.org, impp@iastate.edu,
        ietf <IETF@ietf.org>
Subject: Re: Response from a former IMPP Chair (Re: Last Call: A Model for
 Presence and Instant Messaging to Proposed Standard)
Message-Id: <20030719111959.20aaccde.mrose@dbc.mtview.ca.us>
In-Reply-To: <209845592.1058393937@localhost>
References: <209845592.1058393937@localhost>
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

> WRITTEN IN MY ROLE AS FORMER IMPP CHAIR
> 
> Dave and Marshall,
> ...

harald - first, thanks very much for the note.

dave and i are having a bit of trouble co-ordinating our post-vienna schedules,
so it will probably be a couple of days before we can respond in full to your
reply. (but, don't worry... we will!)

in the meantime, may i ask a question: it was unclear to me whether your reply
was meant as an alternative interpretation of events or an actual rebuttal. if
the former, that's fine. if the latter, then there were a large number of things
which you just skipped over. should i interpret that as your agreement, or, if
not, do you plan on discussing those issues in the future.

of course, if you didn't intend to address those issues, that's fine. i'm just
trying to figure out your position with respect to the breadth of material we
presented.

thanks!

/mtr



From owner-ietf@ietf.org  Sun Jul 20 00: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 AAA28825
	for <ietf-web-archive@odin.ietf.org>; Sun, 20 Jul 2003 00:08:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19e5Ko-0001iI-4T
	for ietf-list@asgard.ietf.org; Sat, 19 Jul 2003 23:58:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19e5KX-0001i0-Rc
	for ietf@asgard.ietf.org; Sat, 19 Jul 2003 23:57: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 XAA28668
	for <ietf@ietf.org>; Sat, 19 Jul 2003 23:57:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19e5KV-0006PI-00
	for ietf@ietf.org; Sat, 19 Jul 2003 23:57:48 -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 19e5KG-0006P9-00
	for ietf@ietf.org; Sat, 19 Jul 2003 23:57:32 -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 h6K3u1o10033
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK)
	for <ietf@ietf.org>; Sat, 19 Jul 2003 23:56:12 -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 h6I9kwNP005556
	for <ietf@ietf.org>; Fri, 18 Jul 2003 11:46:58 +0200
To: ietf@ietf.org
Subject: Re: Critique vs Criticism - Plenary comments 
In-reply-to: Your message of "Thu, 17 Jul 2003 17:11:18 EDT."
             <6.0.0.12.2.20030717163927.041605c8@pop.mindspring.com> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Fri, 18 Jul 2003 11:46:58 +0200
Message-ID: <5554.1058521618@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-ietf@ietf.org
Precedence: bulk

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


>>>>> "Michael" == Michael StJohns <mstjohns@mindspring.com> writes:
    Michael> and the city and people of Vienna, and more as I think it was
    Michael> intended - a critique of the site and facilities as they relate
    Michael> to serving the needs of the IETF.  The person who started the
    Michael> discussion made at least three separate points related to the
    Michael> facilities - at no time did he impugn or otherwise denigrate
    Michael> Vienna, the people of Vienna, or the local host.

  I want to concur with this.
  I actually have no problem with having my room further from the conference
centre. When there is an official hotel, I find it annoying to not be in
the conference hotel - but with everyone having to travel, it is much
more equitable.

  I found the S-Bahn convenient, cheap and fast. It stopped running
on me Wednesday night (12:30pm exit), but that was okay. I intend to spend
Saturday visiting the end of each line for fun. (Okay, I'm a train nut)

    Michael> We've had meetings with geographic separation before - mostly
    Michael> this causes problems in the formation of the usual IETF bar
    Michael> BOFs.  Going back to the beginning of the IETF, much of the
    Michael> small group discussion at the IETF has taken place after or
    Michael> between the session in and around the bar at the conference
    Michael> hotel.  Quite a lot of the ideas which have made it into the

  So, I want to echo this and emphasis this point. 
  The lack of a bar with nice seats that would be open to reasonable hours
(i.e. midnight) really hurt. Things seemed to close very early downtown,
or at least open places were hard to find.

    Michael> I do want to echo Randy Bush and others with thanks to the host
    Michael> for an excellent wireless system and network.  I didn't have to

  Yes... it just worked. Thank you to Telekom Austria.

]                   At IETF57 in Wien, Austria                  |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] printk("Just another Debian GNU/Linux using, kernel hacking, security guy");[


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBPxfCEIqHRg3pndX9AQFwKgQAprIFQ/CWKclNb2kB5R6vlBB+IY2x1QRW
vNO3u0ygxBQAKKkyDyiI8z/axeBeqZCQf9xVNC7k6HytGeWNvCfw8/hSPE2hbWMG
HcAAKH+aEaPS8rF5h7M58eFpfQaKyt3PD9jeGjLTqB1ypbp+UR/NKVrOuU/ZzRbx
jIESm0KZdBA=
=cSXK
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Sun Jul 20 04:09: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 EAA14254
	for <ietf-web-archive@odin.ietf.org>; Sun, 20 Jul 2003 04:09:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19e97w-0001Fc-8J
	for ietf-list@asgard.ietf.org; Sun, 20 Jul 2003 04:01:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19e972-0001FI-Fj
	for ietf@asgard.ietf.org; Sun, 20 Jul 2003 04:00: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 EAA14173
	for <ietf@ietf.org>; Sun, 20 Jul 2003 04:00:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19e970-0000Nm-00
	for ietf@ietf.org; Sun, 20 Jul 2003 04:00:06 -0400
Received: from web80605.mail.yahoo.com ([66.218.79.94])
	by ietf-mx with smtp (Exim 4.12)
	id 19e96p-0000NB-00
	for ietf@ietf.org; Sun, 20 Jul 2003 03:59:55 -0400
Message-ID: <20030720075903.96015.qmail@web80605.mail.yahoo.com>
Received: from [213.147.67.206] by web80605.mail.yahoo.com via HTTP; Sun, 20 Jul 2003 00:59:03 PDT
Date: Sun, 20 Jul 2003 00:59:03 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Evidence of Symmetric Amplification of Light
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-2035849872-1058687943=:94995"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-2035849872-1058687943=:94995
Content-Type: text/plain; charset=us-ascii

CLARIFICATION:
In solid state physics light can be amplified quasi-symmetrically by sandwiching gen1,2, or 3 light amplifiers between the relevant polarity filters.  Though this process involves photon-electron-photon conversion and well choosen light types and a well calibrated arrangement.  Furthermore the amplified light can be routed back into optical fibre in limited quantum communications applications or shone onto a discerning grid (AI) of photocells.
 
Nyagudi


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

<DIV>CLARIFICATION:</DIV>
<DIV>In solid state physics light can be amplified quasi-symmetrically by sandwiching gen1,2, or 3 light amplifiers between the relevant polarity filters.&nbsp; Though this process involves photon-electron-photon conversion and well choosen light types and a well calibrated arrangement.&nbsp; Furthermore the amplified light can be routed back into optical fibre in limited quantum communications applications or shone onto a discerning grid (AI) of photocells.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi</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-2035849872-1058687943=:94995--



From owner-ietf@ietf.org  Sun Jul 20 05:52: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 FAA15663
	for <ietf-web-archive@odin.ietf.org>; Sun, 20 Jul 2003 05:52:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19eAkZ-0004IX-EW
	for ietf-list@asgard.ietf.org; Sun, 20 Jul 2003 05:45:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19eAjw-0004IL-Bh
	for ietf@asgard.ietf.org; Sun, 20 Jul 2003 05:44: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 FAA15594
	for <ietf@ietf.org>; Sun, 20 Jul 2003 05:44:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eAju-0000yN-00
	for ietf@ietf.org; Sun, 20 Jul 2003 05:44:22 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eAjj-0000yD-00
	for ietf@ietf.org; Sun, 20 Jul 2003 05:44:11 -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 KAA10984
	for <ietf@ietf.org>; Sun, 20 Jul 2003 10:43:51 +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 KAA21865
	for <ietf@ietf.org>; Sun, 20 Jul 2003 10:43:51 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h6K9hpn05433
	for ietf@ietf.org; Sun, 20 Jul 2003 10:43:51 +0100
Date: Sun, 20 Jul 2003 10:43:51 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: Critique vs Criticism - Plenary comments
Message-ID: <20030720094351.GA5299@login.ecs.soton.ac.uk>
References: <6.0.0.12.2.20030717163927.041605c8@pop.mindspring.com> <5554.1058521618@marajade.sandelman.ottawa.on.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5554.1058521618@marajade.sandelman.ottawa.on.ca>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, Jul 18, 2003 at 11:46:58AM +0200, Michael Richardson wrote:
>
>   I actually have no problem with having my room further from the conference
> centre. When there is an official hotel, I find it annoying to not be in
> the conference hotel - but with everyone having to travel, it is much
> more equitable.

I think at any IETF there will be some who prefer to sit in a hotel all
week with everything to hand, and others who will prefer to make thir own
(cheaper) booking and explore the city a bit (yes, there was open WLAN in the
city too!).   The San Francisco venue allowed both very well for example.
 
>   The lack of a bar with nice seats that would be open to reasonable hours
> (i.e. midnight) really hurt. Things seemed to close very early downtown,
> or at least open places were hard to find.

The Vienna venue "encouraged" us to explore the city :)   But with the U1
line this was quite easy, and a lot of fun.  You could get unlimited metro
travel for 24 Euros for the week, although noone in Vienna ever seemed to
check tickets!  

Regarding late night bars, the Swedenplatz (excuse spelling?) which was 5
stops south on the U1 had many good bars and places to eat open very late, 
well past the last metro, but were also very well served by taxis (which in 
Vienna were quite cheap, less than 10 Euros from anywhere back to my hotel).

I think what some people missed was the ability to buy food or coffee between 
the afternoon and evening session.  I don't quite understand why the bar that
served food and drink and lunchtime was shut in the evening break.   But
that encouraged exploration :)  With the U1 line you had time to get to a
restaurant and back in the break.   But for the "all in one" people who like
the SFO or Minneapolis style hotel it's less well suited.

>   Yes... it just worked. Thank you to Telekom Austria.

Yep :)

Tim



From owner-ietf@ietf.org  Sun Jul 20 06:42:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16303
	for <ietf-web-archive@odin.ietf.org>; Sun, 20 Jul 2003 06:42:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19eBYt-000544-5k
	for ietf-list@asgard.ietf.org; Sun, 20 Jul 2003 06:37:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19eBYF-00053M-DI
	for ietf@asgard.ietf.org; Sun, 20 Jul 2003 06: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 GAA16210
	for <ietf@ietf.org>; Sun, 20 Jul 2003 06:36:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eBYD-0001Dr-00
	for ietf@ietf.org; Sun, 20 Jul 2003 06:36:21 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eBY2-0001Dn-00
	for ietf@ietf.org; Sun, 20 Jul 2003 06:36:10 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 18A5061BDB
	for <ietf@ietf.org>; Sun, 20 Jul 2003 12:35:36 +0200 (CEST)
Date: Sun, 20 Jul 2003 12:35:17 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Plenary presentations
Message-ID: <132626386.1058704517@localhost>
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

Some people may be interested in a rapid view of the IESG plenary 
presentations from Vienna.

I have placed a copy of the .ppt files I have and their .pdf versions in my 
personal webserver:

http://www.alvestrand.no/ietf/july2003/

At the moment, the problem presentation and the IP Storage presentation are 
not there; I hope to get them too eventually.

There are also the Jabber notes and the scribe's notes, that either are 
available or will be shortly.

Enjoy!

                    Harald




From owner-ietf@ietf.org  Sun Jul 20 11:18: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 LAA21178
	for <ietf-web-archive@odin.ietf.org>; Sun, 20 Jul 2003 11:18:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19eFgL-0008IN-7R
	for ietf-list@asgard.ietf.org; Sun, 20 Jul 2003 11:01:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19eFgD-0008Hn-Q8
	for ietf@asgard.ietf.org; Sun, 20 Jul 2003 11:00: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 LAA21002;
	Sun, 20 Jul 2003 11:00:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eFgC-0002pg-00; Sun, 20 Jul 2003 11:00:52 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eFg1-0002on-00; Sun, 20 Jul 2003 11:00:42 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 7961361B8F; Sun, 20 Jul 2003 16:59:22 +0200 (CEST)
Date: Sun, 20 Jul 2003 13:26:52 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Marshall Rose <mrose@dbc.mtview.ca.us>
Cc: Dave Crocker <dcrocker@brandenburg.com>, iesg@ietf.org, impp@iastate.edu,
        ietf <IETF@ietf.org>
Subject: Re: Response from a former IMPP Chair (Re: Last Call: A Model for
 Presence and Instant Messaging to Proposed Standard)
Message-ID: <135721407.1058707612@localhost>
In-Reply-To: <20030719111959.20aaccde.mrose@dbc.mtview.ca.us>
References: <209845592.1058393937@localhost>
 <20030719111959.20aaccde.mrose@dbc.mtview.ca.us>
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

Marshall,

I found that when I tried to understand your note, it seemed to consist of 
three themes:

- A basic disagreement on the direction of the group, and an interpretation 
of history that appeared to say that the group had not consciously and 
conscientously made the decision to go down the path you disagreed with
- A number of issues that made sense given the interpretation above
- A number of relatively minor issues

I decided to address the first one; the second group did not make sense to 
address as long as we had disagreement on the first one, and the third one 
did not seem to me like one I could contribute any particular expertise in 
solving; in a less polarized context, I would see most of these as "minor 
wording edits" that the document editors would handle as a matter of course.

I am looking forward to your response.

                       Harald

--On 19. juli 2003 11:19 -0700 Marshall Rose <mrose@dbc.mtview.ca.us> wrote:

>> WRITTEN IN MY ROLE AS FORMER IMPP CHAIR
>>
>> Dave and Marshall,
>> ...
>
> harald - first, thanks very much for the note.
>
> dave and i are having a bit of trouble co-ordinating our post-vienna
> schedules, so it will probably be a couple of days before we can respond
> in full to your reply. (but, don't worry... we will!)
>
> in the meantime, may i ask a question: it was unclear to me whether your
> reply was meant as an alternative interpretation of events or an actual
> rebuttal. if the former, that's fine. if the latter, then there were a
> large number of things which you just skipped over. should i interpret
> that as your agreement, or, if not, do you plan on discussing those
> issues in the future.
>
> of course, if you didn't intend to address those issues, that's fine. i'm
> just trying to figure out your position with respect to the breadth of
> material we presented.
>
> thanks!
>
> /mtr
>
>







From owner-ietf@ietf.org  Sun Jul 20 14:58: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 OAA24431
	for <ietf-web-archive@odin.ietf.org>; Sun, 20 Jul 2003 14:58:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19eJEx-00028w-GK
	for ietf-list@asgard.ietf.org; Sun, 20 Jul 2003 14:48:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19eJEj-00028L-Nz
	for ietf@asgard.ietf.org; Sun, 20 Jul 2003 14:48: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 OAA24308
	for <ietf@ietf.org>; Sun, 20 Jul 2003 14:48:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eJEi-0004RN-00
	for ietf@ietf.org; Sun, 20 Jul 2003 14:48:44 -0400
Received: from filesrv1.baby-dragons.com ([199.33.245.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eJEX-0004RC-00
	for ietf@ietf.org; Sun, 20 Jul 2003 14:48:33 -0400
Received: from filesrv1.baby-dragons.com (localhost [127.0.0.1])
	by filesrv1.baby-dragons.com (8.12.9/8.12.7) with ESMTP id h6KImAMd008210;
	Sun, 20 Jul 2003 14:48:10 -0400
Received: from localhost (babydr@localhost)
	by filesrv1.baby-dragons.com (8.12.9/8.12.7/Submit) with ESMTP id h6KImA5f008207;
	Sun, 20 Jul 2003 14:48:10 -0400
X-Authentication-Warning: filesrv1.baby-dragons.com: babydr owned process doing -bs
Date: Sun, 20 Jul 2003 14:48:10 -0400 (EDT)
From: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
To: NM Research <nm_research@yahoo.com>
cc: ietf@ietf.org
Subject: Re: Evidence of Symmetric Amplification of Light
In-Reply-To: <20030720075903.96015.qmail@web80605.mail.yahoo.com>
Message-ID: <Pine.LNX.4.56.0307201446090.7820@filesrv1.baby-dragons.com>
References: <20030720075903.96015.qmail@web80605.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

	Hello Nyagudi ,  Would you please post any referances to validate
	your statements ?  This is not meant to disparage those statements
	just to shed a bit more light ;-) .  Tia,   JimL

On Sun, 20 Jul 2003, NM Research wrote:
> CLARIFICATION:
> In solid state physics light can be amplified quasi-symmetrically by
sandwiching gen1,2, or 3 light amplifiers between the relevant polarity
filters.  Though this process involves photon-electron-photon conversion
and well choosen light types and a well calibrated arrangement.
Furthermore the amplified light can be routed back into optical fibre in
limited quantum communications applications or shone onto a discerning
grid (AI) of photocells.
> Nyagudi
-- 
       +------------------------------------------------------------------+
       | James   W.   Laferriere | System    Techniques | Give me VMS     |
       | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
       | babydr@baby-dragons.com | Coudersport PA 16915 |   only  on  AXP |
       +------------------------------------------------------------------+



From owner-ietf@ietf.org  Mon Jul 21 03:25: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 DAA19926
	for <ietf-web-archive@odin.ietf.org>; Mon, 21 Jul 2003 03:25:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19eUrp-0006Ll-Vy
	for ietf-list@asgard.ietf.org; Mon, 21 Jul 2003 03:13:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19eUqw-0006Kt-45
	for ietf@asgard.ietf.org; Mon, 21 Jul 2003 03:12: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 DAA19674
	for <ietf@ietf.org>; Mon, 21 Jul 2003 03:12:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eUqt-0000Vc-00
	for ietf@ietf.org; Mon, 21 Jul 2003 03:12:56 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eUqj-0000VZ-00
	for ietf@ietf.org; Mon, 21 Jul 2003 03:12:45 -0400
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h6L7Bspp020549
	for <ietf@ietf.org>; Mon, 21 Jul 2003 00:11:54 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (dhcp-ams-cam-avl42-144-254-206-137.cisco.com [144.254.206.137])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AJK00398;
	Mon, 21 Jul 2003 00:08:12 -0700 (PDT)
Message-Id: <5.2.0.9.2.20030720104704.04f9b8f0@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sun, 20 Jul 2003 11:44:33 +0200
To: ietf@ietf.org
From: Fred Baker <fred@cisco.com>
Subject: Re: re the plenary discussion on partial checksums
In-Reply-To: <Pine.LNX.4.44.0307161352330.31453-100000@npax.cavebear.com
 >
References: <20030716155902.73c23bd8.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 02:05 PM 7/16/2003 -0700, Karl Auerbach wrote:
>The last time I saw a comparision of checksum algorithm strengths was back
>in the OSI days when the IP checksum was compared to the OSI Fletcher
>checksum (my memory is that the IP checksum came in second.)

um, well, it was certainly behind the Fletcher checksum; the IP and TCP 
checksums are trivial to beat - you can literally swap any two 16 bit words 
without fear. The Fletcher checksum isn't as strong as a CRC, but I did see 
its strength compared positively with a CRC. The XNS checksum (one's 
complement sum, like IP, but with rotation) fell somewhere in between.

As I understood the discussion, it wasn't so much about getting a better 
error check as it was adding FEC, however. Even a 32 bit CRC loses its 
value above 10^5 bits, and we're talking about 10^5 *bytes*.

At 04:34 PM 7/16/2003 -0400, Bill Strahm wrote:
>Why, oh WHY would I want to receive a known corrupted packet ?

usually it is something about it taking multiple seconds for data to arrive 
with a very high BER, and including FEC in the application data that would 
allow the system to recover enough useful information to make it 
worthwhile. Think interplanetary space. There is also discussion of 64K 
MTUs in some sectors, which I tend to think is misguided (I understand 
reasons for larger packets, or at least I think I do, but I think the 
trade-offs don't justify them).  




From owner-ietf@ietf.org  Mon Jul 21 06: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 GAA22592
	for <ietf-web-archive@odin.ietf.org>; Mon, 21 Jul 2003 06:15:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19eXZE-0000Ti-Mi
	for ietf-list@asgard.ietf.org; Mon, 21 Jul 2003 06:06:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19eXZ8-0000Sv-AI
	for ietf@asgard.ietf.org; Mon, 21 Jul 2003 06:06: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 GAA22465
	for <ietf@ietf.org>; Mon, 21 Jul 2003 06:06:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eXZ5-0001Qj-00
	for ietf@ietf.org; Mon, 21 Jul 2003 06:06:43 -0400
Received: from web80604.mail.yahoo.com ([66.218.79.93])
	by ietf-mx with smtp (Exim 4.12)
	id 19eXYv-0001Qe-00
	for ietf@ietf.org; Mon, 21 Jul 2003 06:06:33 -0400
Message-ID: <20030721100539.43983.qmail@web80604.mail.yahoo.com>
Received: from [62.56.233.4] by web80604.mail.yahoo.com via HTTP; Mon, 21 Jul 2003 03:05:39 PDT
Date: Mon, 21 Jul 2003 03:05:39 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Re: Evidence of Symmetric Amplification of Light
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>, ietf@ietf.org
In-Reply-To: <Pine.LNX.4.56.0307201446090.7820@filesrv1.baby-dragons.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-113034854-1058781939=:43686"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-113034854-1058781939=:43686
Content-Type: text/plain; charset=us-ascii

You can check up with any reputable night vision combat googles manufacturers, I read the technical documents from one of them.  That's how I drew my conclusions.  Though they have their own optical fibre twists - I have a proprietary method of re-routing into optical fibre - i.e I intend to get a patent.
 
Nyagudi

"Mr. James W. Laferriere" <babydr@baby-dragons.com> wrote:
Hello Nyagudi , Would you please post any referances to validate
your statements ? This is not meant to disparage those statements
just to shed a bit more light ;-) . Tia, JimL

On Sun, 20 Jul 2003, NM Research wrote:
> CLARIFICATION:
> In solid state physics light can be amplified quasi-symmetrically by
sandwiching gen1,2, or 3 light amplifiers between the relevant polarity
filters. Though this process involves photon-electron-photon conversion
and well choosen light types and a well calibrated arrangement.
Furthermore the amplified light can be routed back into optical fibre in
limited quantum communications applications or shone onto a discerning
grid (AI) of photocells.
> Nyagudi
-- 
+------------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network Engineer | P.O. Box 854 | Give me Linux |
| babydr@baby-dragons.com | Coudersport PA 16915 | only on AXP |
+------------------------------------------------------------------+

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

<DIV>You can check up with any reputable night vision combat googles manufacturers, I read the technical documents from one of them.&nbsp; That's how I drew my conclusions.&nbsp; Though they have their own optical fibre twists - I have a proprietary method of re-routing into optical fibre - i.e I intend to get a patent.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi<BR><BR><B><I>"Mr. James W. Laferriere" &lt;babydr@baby-dragons.com&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px; WIDTH: 100%">Hello Nyagudi , Would you please post any referances to validate<BR>your statements ? This is not meant to disparage those statements<BR>just to shed a bit more light ;-) . Tia, JimL<BR><BR>On Sun, 20 Jul 2003, NM Research wrote:<BR>&gt; CLARIFICATION:<BR>&gt; In solid state physics light can be amplified quasi-symmetrically by<BR>sandwiching gen1,2, or 3 light amplifiers between the relevant polarity<BR>filters. Though this process involves photon-electron-photon conversion<BR>and well choosen light types and a well calibrated arrangement.<BR>Furthermore the amplified light can be routed back into optical fibre in<BR>limited quantum communications applications or shone onto a discerning<BR>grid (AI) of photocells.<BR>&gt; Nyagudi<BR>-- <BR>+------------------------------------------------------------------+<BR>| James W. Laferriere | System Techniques | Give me VMS |<BR>| Ne!
 twork
 Engineer | P.O. Box 854 | Give me Linux |<BR>| babydr@baby-dragons.com | Coudersport PA 16915 | only on AXP |<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-113034854-1058781939=:43686--



From owner-ietf@ietf.org  Mon Jul 21 06: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 GAA22597
	for <ietf-web-archive@odin.ietf.org>; Mon, 21 Jul 2003 06:15:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19eXbA-0000VM-Mi
	for ietf-list@asgard.ietf.org; Mon, 21 Jul 2003 06:08:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19eXZa-0000Tl-7M
	for ietf@asgard.ietf.org; Mon, 21 Jul 2003 06:07:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22476
	for <ietf@ietf.org>; Mon, 21 Jul 2003 06:07:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eXZX-0001Qx-00
	for ietf@ietf.org; Mon, 21 Jul 2003 06:07:11 -0400
Received: from web80602.mail.yahoo.com ([66.218.79.91])
	by ietf-mx with smtp (Exim 4.12)
	id 19eXZN-0001Qg-00
	for ietf@ietf.org; Mon, 21 Jul 2003 06:07:01 -0400
Message-ID: <20030721100558.6034.qmail@web80602.mail.yahoo.com>
Received: from [62.56.233.4] by web80602.mail.yahoo.com via HTTP; Mon, 21 Jul 2003 03:05:58 PDT
Date: Mon, 21 Jul 2003 03:05:58 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Re: Evidence of Symmetric Amplification of Light
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>, ietf@ietf.org
In-Reply-To: <Pine.LNX.4.56.0307201446090.7820@filesrv1.baby-dragons.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1722271691-1058781958=:5583"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-1722271691-1058781958=:5583
Content-Type: text/plain; charset=us-ascii

You can check up with any reputable night vision combat googles manufacturers, I read the technical documents from one of them.  That's how I drew my conclusions.  Though they have their own optical fibre twists - I have a proprietary method of re-routing into optical fibre - i.e I intend to get a patent.
 
Nyagudi

"Mr. James W. Laferriere" <babydr@baby-dragons.com> wrote:
Hello Nyagudi , Would you please post any referances to validate
your statements ? This is not meant to disparage those statements
just to shed a bit more light ;-) . Tia, JimL

On Sun, 20 Jul 2003, NM Research wrote:
> CLARIFICATION:
> In solid state physics light can be amplified quasi-symmetrically by
sandwiching gen1,2, or 3 light amplifiers between the relevant polarity
filters. Though this process involves photon-electron-photon conversion
and well choosen light types and a well calibrated arrangement.
Furthermore the amplified light can be routed back into optical fibre in
limited quantum communications applications or shone onto a discerning
grid (AI) of photocells.
> Nyagudi
-- 
+------------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network Engineer | P.O. Box 854 | Give me Linux |
| babydr@baby-dragons.com | Coudersport PA 16915 | only on AXP |
+------------------------------------------------------------------+

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

<DIV>You can check up with any reputable night vision combat googles manufacturers, I read the technical documents from one of them.&nbsp; That's how I drew my conclusions.&nbsp; Though they have their own optical fibre twists - I have a proprietary method of re-routing into optical fibre - i.e I intend to get a patent.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi<BR><BR><B><I>"Mr. James W. Laferriere" &lt;babydr@baby-dragons.com&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px; WIDTH: 100%">Hello Nyagudi , Would you please post any referances to validate<BR>your statements ? This is not meant to disparage those statements<BR>just to shed a bit more light ;-) . Tia, JimL<BR><BR>On Sun, 20 Jul 2003, NM Research wrote:<BR>&gt; CLARIFICATION:<BR>&gt; In solid state physics light can be amplified quasi-symmetrically by<BR>sandwiching gen1,2, or 3 light amplifiers between the relevant polarity<BR>filters. Though this process involves photon-electron-photon conversion<BR>and well choosen light types and a well calibrated arrangement.<BR>Furthermore the amplified light can be routed back into optical fibre in<BR>limited quantum communications applications or shone onto a discerning<BR>grid (AI) of photocells.<BR>&gt; Nyagudi<BR>-- <BR>+------------------------------------------------------------------+<BR>| James W. Laferriere | System Techniques | Give me VMS |<BR>| Ne!
 twork
 Engineer | P.O. Box 854 | Give me Linux |<BR>| babydr@baby-dragons.com | Coudersport PA 16915 | only on AXP |<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-1722271691-1058781958=:5583--



From owner-ietf@ietf.org  Mon Jul 21 07:16: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 HAA24268
	for <ietf-web-archive@odin.ietf.org>; Mon, 21 Jul 2003 07:16:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19eYXE-0002Gm-7F
	for ietf-list@asgard.ietf.org; Mon, 21 Jul 2003 07:08:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19eYVc-0002F6-Cb
	for ietf@asgard.ietf.org; Mon, 21 Jul 2003 07:07: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 HAA24113
	for <ietf@ietf.org>; Mon, 21 Jul 2003 07:07:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19eYVZ-0001of-00
	for ietf@ietf.org; Mon, 21 Jul 2003 07:07:09 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19eYVP-0001oU-00
	for ietf@ietf.org; Mon, 21 Jul 2003 07:06:59 -0400
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <PLG3K7YN>; Mon, 21 Jul 2003 07:06:05 -0400
Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922BBB@ftmail.lab.flarion.com>
From: Soliman Hesham <H.Soliman@flarion.com>
To: "'Tim Chown'" <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: RE: Critique vs Criticism - Plenary comments
Date: Mon, 21 Jul 2003 07:05:38 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk



 > I think what some people missed was the ability to buy food 
 > or coffee between 
 > the afternoon and evening session.  I don't quite understand 
 > why the bar that
 > served food and drink and lunchtime was shut in the evening 
 > break.   But
 > that encouraged exploration :)  With the U1 line you had 
 > time to get to a
 > restaurant and back in the break.   But for the "all in one" 
 > people who like
 > the SFO or Minneapolis style hotel it's less well suited.

=> You're being very kind to Minneapolis to compare it with
Vienna ! The fact that some people prefer that to Vienna
shocks me, but anyway, I guess they'll enjoy the next meeting.
Have we finished complaining about one of the most
beautiful cities in the world yet (because it didn't
have enough power plugs....sigh)?

Hesham




From owner-ietf@ietf.org  Mon Jul 21 15: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 PAA08817
	for <ietf-web-archive@odin.ietf.org>; Mon, 21 Jul 2003 15:47:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19egTk-0005o6-C3
	for ietf-list@asgard.ietf.org; Mon, 21 Jul 2003 15:37:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19egTh-0005nU-HT
	for ietf@asgard.ietf.org; Mon, 21 Jul 2003 15:37: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 PAA08659
	for <ietf@ietf.org>; Mon, 21 Jul 2003 15:37:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19egTg-0005mx-00
	for ietf@ietf.org; Mon, 21 Jul 2003 15:37:44 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19egTV-0005m3-00
	for ietf@ietf.org; Mon, 21 Jul 2003 15:37:33 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id D87DFABBC; Mon, 21 Jul 2003 12:42:36 -0700 (PDT)
To: Soliman Hesham <H.Soliman@flarion.com>
Cc: "'Tim Chown'" <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: Critique vs Criticism - Plenary comments
References: <748C6D0A58C0F94CA63C198B6674697A01922BBB@ftmail.lab.flarion.com>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 21 Jul 2003 12:42:36 -0700
In-Reply-To: <748C6D0A58C0F94CA63C198B6674697A01922BBB@ftmail.lab.flarion.com>
Message-ID: <kjn0f7vf83.fsf@romeo.rtfm.com>
Lines: 37
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Soliman Hesham <H.Soliman@flarion.com> writes:

>  > I think what some people missed was the ability to buy food 
>  > or coffee between 
>  > the afternoon and evening session.  I don't quite understand 
>  > why the bar that
>  > served food and drink and lunchtime was shut in the evening 
>  > break.   But
>  > that encouraged exploration :)  With the U1 line you had 
>  > time to get to a
>  > restaurant and back in the break.   But for the "all in one" 
>  > people who like
>  > the SFO or Minneapolis style hotel it's less well suited.
> 
> => You're being very kind to Minneapolis to compare it with
> Vienna ! The fact that some people prefer that to Vienna
> shocks me, but anyway, I guess they'll enjoy the next meeting.
> Have we finished complaining about one of the most
> beautiful cities in the world yet (because it didn't
> have enough power plugs....sigh)?

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

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

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Wed Jul 23 14:03: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 OAA21738
	for <ietf-web-archive@odin.ietf.org>; Wed, 23 Jul 2003 14:03:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19fNhD-00013S-Tb
	for ietf-list@asgard.ietf.org; Wed, 23 Jul 2003 13:46:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19fNgt-000135-RR
	for ietf@asgard.ietf.org; Wed, 23 Jul 2003 13:46: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 NAA20982;
	Wed, 23 Jul 2003 13:46:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fNgs-0006Pt-00; Wed, 23 Jul 2003 13:46:14 -0400
Received: from [65.125.189.56] (helo=drakken.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19fNgh-0006PR-00; Wed, 23 Jul 2003 13:46:03 -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 h6NHjR2e001147;
	Wed, 23 Jul 2003 10:45:27 -0700 (PDT)
Date: Wed, 23 Jul 2003 10:45:27 -0700
From: Marshall Rose <mrose@dbc.mtview.ca.us>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: Dave Crocker
 <dcrocker@brandenburg.com>, iesg@ietf.org, impp@iastate.edu,
        ietf
 <IETF@ietf.org>
Subject: Re: Response from a former IMPP Chair (Re: Last Call: A Model for
 Presence and Instant Messaging to Proposed Standard)
Message-Id: <20030723104527.6a89218d.mrose@dbc.mtview.ca.us>
In-Reply-To: <209845592.1058393937@localhost>
References: <209845592.1058393937@localhost>
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

> WRITTEN IN MY ROLE AS FORMER IMPP CHAIR
    
harold - as indicated in my previous note, here is a reply!
    
although i'm the only address listed on the "From:" line, that's a
limitation of the mail client i'm using. please consider this a note
from Marshall and Dave.

so, we'll start at the end of your reply, because that's more direct.

    
> My conclusions:
> 
> The working group has suffered from very slow document updates, a bad error 
> in judgment (mine) re charter update, and repeated re-raising of old closed 
> issues (for instance, at Atlanta in November 2002, Dave Crocker could be 
> heard re-raising the issue of the need for loop control, which the group 
> had discussed and decided in December 2000, choosing hopcount as the 
> preferred mechanism in March 2001).
> 
> However, I find the criticisms raised against the process leading to the 
> forwarding of these documents to the IESG to be very much off target.

we confess that we're a bit disappointed with your response. we spent
considerable effort laying out a detailed complaint, and even included a
table of contents, viz.,
    
> >      1.   PROCESS FAILURES
> >      1.1. Lack of participation and constituency
> >      1.2. Out of scope with charter
> >      1.3. Failure to resolve issues raised in the working group
> > 
> >      2.   TECHNICAL FAILURES
> >      2.1. Confused and conflicting goals
> >      2.2. Incomplete and unclear specifications.

but you addressed the least interesting of these.
    
perhaps issue 2.2 can be handled by applying some engineering and
editing. yet they weren't, when they were raised in the working group.
as things stand, the document is simply not viable on its own.
    
the other issue you addressed is issue 1.3, while we might quibble with
your timeline, we think you're missing the big picture, which is bleak.
the work has no serious constituency. it cannot perform the task it
describes for itself, as a gateway between heterogeneous services. few
people created the work. few are interested in using it. 
    
in other words, issues 1.1, 1.2, and 2.1 are fatal. they're also
essentially un-arguable. (or rather, no one's popped up to argue with us
over them and it's been a month, eh?)
    
issue 2.1 tells us that the documents are going to be a failure in
theory, and issue 1.1 tells us that the documents are going to be a
failure in practice.
    
finally, issue 1.2 tell us that we're not even following our own rules.
charters matter. otherwise, why have them? sanctity of the charter is
perhaps the single most "sacred" aspect of the way we do things.

we confess, if the work were "good", we could look the other way on the
process problems. but, let's face it, no one is arguing that we're
talking about a quality work product here. in fact, no one is even
arguing that the work product is going to see any meaningful use in
production.
    
for the life of us, we can't figure out why anyone would want to defend
this work...
    
/mtr
    
ps: secondary to the fatal problems with the specification, your note
cited other process issues. you claim that a working group meeting was
not held due to failures of the document's editor to revise the document
between february and november, 2001. presumably you mean the cpim main
document, rather than the msgfmt, pidf or datetime documents that were
revised during that time. fortunately, your former co-chair's
"(Un)updated todos" note of 14 oct and the cpim document editor's note
of 29 oct make clear that the real reasons for not holding a meeting,
which has nothing to do with the editor...



From owner-ietf@ietf.org  Mon Jul 28 04:22: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 EAA23437
	for <ietf-web-archive@odin.ietf.org>; Mon, 28 Jul 2003 04:22:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19h2yB-0003z5-4F
	for ietf-list@asgard.ietf.org; Mon, 28 Jul 2003 04:02:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19h2xK-0003y6-61
	for ietf@asgard.ietf.org; Mon, 28 Jul 2003 04:02: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 EAA22798
	for <ietf@ietf.org>; Mon, 28 Jul 2003 04:02:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19h2xH-0006aZ-00
	for ietf@ietf.org; Mon, 28 Jul 2003 04:02:03 -0400
Received: from web41812.mail.yahoo.com ([66.218.93.146])
	by ietf-mx with smtp (Exim 4.12)
	id 19h2xH-0006aO-00
	for ietf@ietf.org; Mon, 28 Jul 2003 04:02:03 -0400
Message-ID: <20030728080134.45369.qmail@web41812.mail.yahoo.com>
Received: from [203.200.20.226] by web41812.mail.yahoo.com via HTTP; Mon, 28 Jul 2003 01:01:34 PDT
Date: Mon, 28 Jul 2003 01:01:34 -0700 (PDT)
From: Rohit Gupta <rohitgupta416@yahoo.com>
Subject: doubt
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

What is the procedure to convert a document from
"standards track" to "proposed standard"?

As i understand, it goes something like this.

IETF after a lot of discussions comes up with a
protoocol which it thinks can solve the problem
plauging this world (ISPs). After everyone is
convinced we come out with a "standards track" doc.
ALl vendors are supposed to comply/conform with it.

The implementations start rolling out.

Over a period of time, people learn more about this
new protocol, gain more experience and then they come
out with another RFC which explains this new protocol
and they call it the "proposed standard" 

Is my understanding of the procedure correct? And
generally how long (in years approx) does it take for
a specificiation to mature from a "standards track" to
a proposed standard.

Cheers,
Rohit

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com



From owner-ietf@ietf.org  Mon Jul 28 04:38: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 EAA23895
	for <ietf-web-archive@odin.ietf.org>; Mon, 28 Jul 2003 04:38:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19h3SA-0004ZX-Rc
	for ietf-list@asgard.ietf.org; Mon, 28 Jul 2003 04:33:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19h3Rt-0004ZD-UY
	for ietf@asgard.ietf.org; Mon, 28 Jul 2003 04:33: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 EAA23800
	for <ietf@ietf.org>; Mon, 28 Jul 2003 04:33:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19h3Rr-000762-00
	for ietf@ietf.org; Mon, 28 Jul 2003 04:33:39 -0400
Received: from ierw.net.avaya.com ([198.152.13.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 19h3Rq-00075y-00
	for ietf@ietf.org; Mon, 28 Jul 2003 04:33:38 -0400
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id EAA27291
	for <ietf@ietf.org>; Mon, 28 Jul 2003 04:30:47 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id EAA27284
	for <ietf@ietf.org>; Mon, 28 Jul 2003 04:30:46 -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: doubt
Date: Mon, 28 Jul 2003 11:33:31 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F04258E91@is0004avexu1.global.avaya.com>
Thread-Topic: doubt
Thread-Index: AcNU4bmvZVdI2+2PR1qQjKHxworQ2gAAQq4w
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Rohit Gupta" <rohitgupta416@yahoo.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Proposed Standard is one (the first) of the Standards Track Maturity =
Levels. See Section 4.1 in RFC 2026.=20

Dan


> -----Original Message-----
> From: Rohit Gupta [mailto:rohitgupta416@yahoo.com]
> Sent: 28 July, 2003 11:02 AM
> To: ietf@ietf.org
> Subject: doubt
>=20
>=20
> Hi,
>=20
> What is the procedure to convert a document from
> "standards track" to "proposed standard"?
>=20
> As i understand, it goes something like this.
>=20
> IETF after a lot of discussions comes up with a
> protoocol which it thinks can solve the problem
> plauging this world (ISPs). After everyone is
> convinced we come out with a "standards track" doc.
> ALl vendors are supposed to comply/conform with it.
>=20
> The implementations start rolling out.
>=20
> Over a period of time, people learn more about this
> new protocol, gain more experience and then they come
> out with another RFC which explains this new protocol
> and they call it the "proposed standard"=20
>=20
> Is my understanding of the procedure correct? And
> generally how long (in years approx) does it take for
> a specificiation to mature from a "standards track" to
> a proposed standard.
>=20
> Cheers,
> Rohit
>=20
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
>=20
>=20



From owner-ietf@ietf.org  Tue Jul 29 14:06: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 OAA03025
	for <ietf-web-archive@odin.ietf.org>; Tue, 29 Jul 2003 14:06:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19hYhQ-0002iE-0n
	for ietf-list@asgard.ietf.org; Tue, 29 Jul 2003 13:55:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19hYgT-0002c0-OO
	for ietf@asgard.ietf.org; Tue, 29 Jul 2003 13:54: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 NAA02455;
	Tue, 29 Jul 2003 13:54:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19hYgS-0000S8-00; Tue, 29 Jul 2003 13:54:48 -0400
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19hYgR-0000Ro-00; Tue, 29 Jul 2003 13:54:48 -0400
Received: from ala-mrwtemp.windriver.com ([147.11.233.24])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id KAA08117;
	Tue, 29 Jul 2003 10:53:56 -0700 (PDT)
Message-Id: <5.1.0.14.2.20030729123821.03442ff8@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 29 Jul 2003 12:56:30 -0400
To: wgchairs-training@ops.ietf.org, ietf@ietf.org
From: Margaret Wasserman <mrw@windriver.com>
Subject: edu-discuss mailing list
Cc: edu-discuss@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk


Hi All,

We have established a mailing list for the discussion of the
IETF's internal education efforts, which were discussed at
the Education (edu) BOF in Vienna.  A summary of the BOF
appears below, and full minutes will be sent to the edu-discuss
mailing list.

People who are interested in tracking or participating in our
internal education efforts should subscribe to the edu-discuss
mailing list.  Subscription information can be found at:

https://www1.ietf.org/mailman/listinfo/edu-discuss

Over the next several weeks, Harald Alvestrand and I will be
working to establish the core education team, and to officially
charter this activity.

Margaret



Education (edu) BOF Summary
===========================

The session was attended by approximately 35 people, and there
was a very high level of engagement and participation.  The BOF
focused on internal educational activities within the IETF --
primarily role and process education.

Early discussions focused on our current educational activities
and ideas/suggestions for improving them.  There was a strong
sense that these activities are important, and that we should
continue and expand them as possible.  Priorities for improvement
included editor training, programs to help non-North Americans
become acclimated to the IETF, and mentoring programs for new
attendees.

The second half of the meeting focused on how to organize and
manage our internal educational efforts moving forward.

Margaret Wasserman presented a proposal for an "education team"
to run the education efforts, something between a WG and a
directorate.  In particular:

Form an education team to run this effort
     - Effort overseen by the General AD
     - General AD appoints team leader(s)
     - Leader(s) and AD choose the team from volunteers,
       refresh and expand the team as needed
     - Team membership publicly known

Community visibility and feedback
     - IETF web page for educational activities
     - Public discussion mailing list
     - Education team archives publicly available
     - Occasional (~yearly?) open meetings at IETF

During the meeting, we agreed that the team should have a written
charter, and that the charter should be included on the web site.

There was a strong consensus of those present that we should form
an education team to run these efforts, as described above.

The meeting ended with emphasis from the General AD that continuing
our existing educational activities should be the top priority of
the education team.









