From owner-ietf@ietf.org  Thu Jan  2 13:24:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10638;
	Thu, 2 Jan 2003 13:24:18 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18U9wy-0004tV-00
	for ietf-list@ran.ietf.org; Thu, 02 Jan 2003 13:20:12 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18U9wX-0004ja-00
	for ietf@ran.ietf.org; Thu, 02 Jan 2003 13:19:45 -0500
Received: from almso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10357;
	Thu, 2 Jan 2003 13:12:34 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h02HsIFJ021829;
	Thu, 2 Jan 2003 13:15:45 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E00BD950A; Thu, 2 Jan 2003 13:15:35 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 2 Jan 2003 13:15:35 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704A175C6@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: CORRECTION: Last Call: CR-LDP Extensions for ASON to    Informational
Thread-Index: AcKw9f/pGD3arRlVQoCRxYc1rN+OfQBkNDgQ
From: "Ash, Gerald R (Jerry), ALASO" <gash@att.com>
To: <iesg@ietf.org>
Cc: "Ash, Gerald R (Jerry), ALASO" <gash@att.com>,
        "Adrian Farrel" <afarrel@movaz.com>,
        "Atsushi Iwata" <iwata@ccm.CL.nec.co.jp>,
        "Norihito Fujita" <n-fujita@bk.jp.nec.com>,
        "Simon Marshall-Unitt" <smu@dataconnection.com>,
        "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>,
        "Osama Aboul-Magd" <osama@nortelnetworks.com>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA10638

A crankback TLV is suggested in Section 4.3.  While crankback is a desirable extension to both CR-LDP and RSVP-TE (and required by ASON), the proposal ignores the prior work done in http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt.  The advantages of the proposed method should be identified and justified.  

Furthermore, crankback is not yet within the charter of any IETF Working Group, although this has been proposed (e.g., the IETF-54/CCAMP minutes state 'The charter update is way overdue. Items may be added - protection/restoration, crankback and multi-area operations'). It seems inappropriate to specify a particular crankback extension independent of the possible future work of an IETF Working Group.

Jerry Ash

-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org]
Sent: Tuesday, December 31, 2002 12:40 PM
Subject: CORRECTION: Last Call: CR-LDP Extensions for ASON to
Informational

**PLEASE NOTE THIS IS A TWO WEEK LAST CALL.**

The IESG has received a request to consider CR-LDP Extensions for ASON 
<draft-aboulmagd-ccamp-crldp-ason-ext-02.txt> as an Informational RFC.  
This has been reviewed in the IETF but is not the product of an IETF 
Working Group.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the 
iesg@ietf.org or ietf@ietf.org mailing lists by 2003-1-15.

Files can be obtained via http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.txt







From owner-ietf@ietf.org  Thu Jan  2 13:35:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11024;
	Thu, 2 Jan 2003 13:35:28 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UAEL-0006Uf-00
	for ietf-list@ran.ietf.org; Thu, 02 Jan 2003 13:38:09 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UADw-0006TQ-00
	for ietf@ran.ietf.org; Thu, 02 Jan 2003 13:37:44 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10906;
	Thu, 2 Jan 2003 13:30:33 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h02IXib17820;
	Thu, 2 Jan 2003 10:33:44 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id SAA22047;
	Thu, 2 Jan 2003 18:33:44 GMT
Date: Thu, 2 Jan 2003 18:33:44 GMT
Message-Id: <200301021833.SAA22047@gra.isi.edu>
To: iesg@ietf.org, gash@att.com
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

  *> A crankback TLV is suggested in Section 4.3.  While crankback is a
  *> desirable extension to both CR-LDP and RSVP-TE (and required by
  *> ASON), the proposal ignores the prior work done in
  *> http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt.
 *>  The advantages of the proposed method should be identified and
  *> justified.


Maybe it's time for someone to write an I-D entitled
"Crankback Considered Harmful" ?

Bob Braden



From owner-ietf@ietf.org  Thu Jan  2 14:31:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12159;
	Thu, 2 Jan 2003 14:31:33 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UB6Y-0001fT-00
	for ietf-list@ran.ietf.org; Thu, 02 Jan 2003 14:34:10 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UA5Z-0005k1-00
	for ietf@ran.ietf.org; Thu, 02 Jan 2003 13:29:05 -0500
Received: from zcars04e.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10585;
	Thu, 2 Jan 2003 13:21:54 -0500 (EST)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04e.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h02IOtl18818;
	Thu, 2 Jan 2003 13:24:55 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <ZC6R4DHZ>; Thu, 2 Jan 2003 13:24:55 -0500
Message-ID: <710197BD5AF9D4119E4400508BCFA1360644904A@zcard04u.ca.nortel.com>
From: "Osama Aboul-Magd" <osama@nortelnetworks.com>
To: "Ash, Gerald R (Jerry), ALASO" <gash@att.com>, iesg@ietf.org
Cc: Adrian Farrel <afarrel@movaz.com>, Atsushi Iwata <iwata@ccm.CL.nec.co.jp>,
        Norihito Fujita <n-fujita@bk.jp.nec.com>,
        Simon Marshall-Unitt <smu@dataconnection.com>,
        "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>, ietf@ietf.org,
        "Stephen Shew" <sdshew@nortelnetworks.com>
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informat
	ional
Date: Thu, 2 Jan 2003 13:24:53 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2B28C.3E972A98"
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_01C2B28C.3E972A98
Content-Type: text/plain

Hi Gerry,

This draft is not entirely about crankback. It only reflects agreements
reached at the ITU.

I'd be very happy referencing your draft have it been an RFC. Unfortunately
ITU rules don't allow the referencing of work that is still in progress.

Regards;

Osama Aboul-Magd
ATI Strategic Standards and Protocols
Nortel Networks
P.O. Box 3511, Station C
Ottawa, Ontario, Canada
K1Y-4H7
Tel: +1 613 763 5827
e.mail:osama@nortelnetworks.com


-----Original Message-----
From: Ash, Gerald R (Jerry), ALASO [mailto:gash@att.com] 
Sent: Thursday, January 02, 2003 1:16 PM
To: iesg@ietf.org
Cc: Ash, Gerald R (Jerry), ALASO; Adrian Farrel; Atsushi Iwata; Norihito
Fujita; Simon Marshall-Unitt; Lin, Zhi-Wei (Zhi); Aboul-Magd, Osama
[CAR:1A00:EXCH]; ietf@ietf.org
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to
Informational

A crankback TLV is suggested in Section 4.3.  While crankback is a desirable
extension to both CR-LDP and RSVP-TE (and required by ASON), the proposal
ignores the prior work done in
http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt.  The
advantages of the proposed method should be identified and justified.  

Furthermore, crankback is not yet within the charter of any IETF Working
Group, although this has been proposed (e.g., the IETF-54/CCAMP minutes
state 'The charter update is way overdue. Items may be added -
protection/restoration, crankback and multi-area operations'). It seems
inappropriate to specify a particular crankback extension independent of the
possible future work of an IETF Working Group.

Jerry Ash

-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org]
Sent: Tuesday, December 31, 2002 12:40 PM
Subject: CORRECTION: Last Call: CR-LDP Extensions for ASON to
Informational

**PLEASE NOTE THIS IS A TWO WEEK LAST CALL.**

The IESG has received a request to consider CR-LDP Extensions for ASON 
<draft-aboulmagd-ccamp-crldp-ason-ext-02.txt> as an Informational RFC.  
This has been reviewed in the IETF but is not the product of an IETF 
Working Group.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the 
iesg@ietf.org or ietf@ietf.org mailing lists by 2003-1-15.

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.
txt





------_=_NextPart_001_01C2B28C.3E972A98
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to =
Informational</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi Gerry,</FONT>
</P>

<P><FONT SIZE=3D2>This draft is not entirely about crankback. It only =
reflects agreements reached at the ITU.</FONT>
</P>

<P><FONT SIZE=3D2>I'd be very happy referencing your draft have it been =
an RFC. Unfortunately ITU rules don't allow the referencing of work =
that is still in progress.</FONT></P>

<P><FONT SIZE=3D2>Regards;</FONT>
</P>

<P><FONT SIZE=3D2>Osama Aboul-Magd</FONT>
<BR><FONT SIZE=3D2>ATI Strategic Standards and Protocols</FONT>
<BR><FONT SIZE=3D2>Nortel Networks</FONT>
<BR><FONT SIZE=3D2>P.O. Box 3511, Station C</FONT>
<BR><FONT SIZE=3D2>Ottawa, Ontario, Canada</FONT>
<BR><FONT SIZE=3D2>K1Y-4H7</FONT>
<BR><FONT SIZE=3D2>Tel: +1 613 763 5827</FONT>
<BR><FONT SIZE=3D2>e.mail:osama@nortelnetworks.com</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Ash, Gerald R (Jerry), ALASO [<A =
HREF=3D"mailto:gash@att.com">mailto:gash@att.com</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, January 02, 2003 1:16 PM</FONT>
<BR><FONT SIZE=3D2>To: iesg@ietf.org</FONT>
<BR><FONT SIZE=3D2>Cc: Ash, Gerald R (Jerry), ALASO; Adrian Farrel; =
Atsushi Iwata; Norihito Fujita; Simon Marshall-Unitt; Lin, Zhi-Wei =
(Zhi); Aboul-Magd, Osama [CAR:1A00:EXCH]; ietf@ietf.org</FONT></P>

<P><FONT SIZE=3D2>Subject: RE: CORRECTION: Last Call: CR-LDP Extensions =
for ASON to Informational</FONT>
</P>

<P><FONT SIZE=3D2>A crankback TLV is suggested in Section 4.3.&nbsp; =
While crankback is a desirable extension to both CR-LDP and RSVP-TE =
(and required by ASON), the proposal ignores the prior work done in <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-0=
4.txt" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-iwata-mpls-c=
rankback-04.txt</A>.&nbsp; The advantages of the proposed method should =
be identified and justified.&nbsp; </FONT></P>

<P><FONT SIZE=3D2>Furthermore, crankback is not yet within the charter =
of any IETF Working Group, although this has been proposed (e.g., the =
IETF-54/CCAMP minutes state 'The charter update is way overdue. Items =
may be added - protection/restoration, crankback and multi-area =
operations'). It seems inappropriate to specify a particular crankback =
extension independent of the possible future work of an IETF Working =
Group.</FONT></P>

<P><FONT SIZE=3D2>Jerry Ash</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: The IESG [<A =
HREF=3D"mailto:iesg-secretary@ietf.org">mailto:iesg-secretary@ietf.org</=
A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, December 31, 2002 12:40 PM</FONT>
<BR><FONT SIZE=3D2>Subject: CORRECTION: Last Call: CR-LDP Extensions =
for ASON to</FONT>
<BR><FONT SIZE=3D2>Informational</FONT>
</P>

<P><FONT SIZE=3D2>**PLEASE NOTE THIS IS A TWO WEEK LAST CALL.**</FONT>
</P>

<P><FONT SIZE=3D2>The IESG has received a request to consider CR-LDP =
Extensions for ASON </FONT>
<BR><FONT SIZE=3D2>&lt;draft-aboulmagd-ccamp-crldp-ason-ext-02.txt&gt; =
as an Informational RFC.&nbsp; </FONT>
<BR><FONT SIZE=3D2>This has been reviewed in the IETF but is not the =
product of an IETF </FONT>
<BR><FONT SIZE=3D2>Working Group.</FONT>
</P>

<P><FONT SIZE=3D2>The IESG plans to make a decision in the next few =
weeks, and solicits</FONT>
<BR><FONT SIZE=3D2>final comments on this action.&nbsp; Please send any =
comments to the </FONT>
<BR><FONT SIZE=3D2>iesg@ietf.org or ietf@ietf.org mailing lists by =
2003-1-15.</FONT>
</P>

<P><FONT SIZE=3D2>Files can be obtained via <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-=
ason-ext-02.txt" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-aboulmagd-cc=
amp-crldp-ason-ext-02.txt</A></FONT>
</P>
<BR>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C2B28C.3E972A98--





From owner-ietf@ietf.org  Thu Jan  2 14:31:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12184;
	Thu, 2 Jan 2003 14:31:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UB4b-0001KT-00
	for ietf-list@ran.ietf.org; Thu, 02 Jan 2003 14:32:09 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Tz93-0005fY-00
	for ietf@ran.ietf.org; Thu, 02 Jan 2003 01:47:57 -0500
Received: from tere.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19919
	for <ietf@ietf.org>; Thu, 2 Jan 2003 01:40:53 -0500 (EST)
Received: from tere.cc.columbia.edu (localhost [127.0.0.1])
	by tere.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id h026i4bv000975;
	Thu, 2 Jan 2003 01:44:04 -0500 (EST)
Received: from localhost by tere.cc.columbia.edu (8.12.3/8.12.3/Submit) with ESMTP id h026i4JI000971;
	Thu, 2 Jan 2003 01:44:04 -0500 (EST)
X-Authentication-Warning: tere.cc.columbia.edu: rh120 owned process doing -bs
Date: Thu, 2 Jan 2003 01:44:04 -0500 (EST)
From: Ronda Hauben <rh120@columbia.edu>
To: ietf@ietf.org
cc: braden@isi.edu, "" <rh120@columbia.edu>
Subject: Re: 20th Anniversary of the Internet
Message-ID: <Pine.GSO.4.50.0301020137090.619-100000@tere.cc.columbia.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


Good to see the cutover to TCP/IP from NCP on January 2, 1983 being
celebrated.

The TCP/IP Digest moderated by Mike Muuss contained an interesting
documentation of the problems and efforts that led up to and followed
the cutover. I have a draft paper on the digest at:


http://www.columbia.edu/~rh120/other/tcpdigest_paper.txt

The paper is

               From the ARPANET to the Internet
              A Study of the ARPANET TCP/IP Digest
             and of the Role of Online Communication
     in the Transition from the ARPANET to the Internet
                       by Ronda Hauben
                       rh120@columbia.edu

Cheers

Ronda
rh120@columbia.edu












From owner-ietf@ietf.org  Thu Jan  2 16:03:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14280;
	Thu, 2 Jan 2003 16:03:38 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UCVe-0005K6-00
	for ietf-list@ran.ietf.org; Thu, 02 Jan 2003 16:04:10 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UCNf-0005AR-00
	for ietf@ran.ietf.org; Thu, 02 Jan 2003 15:55:55 -0500
Received: from atlntex01.movaz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13799;
	Thu, 2 Jan 2003 15:48:41 -0500 (EST)
Received: from BLIULAPTOP ([172.16.24.104]) by atlntex01.movaz.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 2 Jan 2003 15:51:53 -0500
Message-ID: <023601c2b2a0$c82a44c0$681810ac@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: <iesg@ietf.org>
Cc: "Osama Aboul-Magd" <osama@nortelnetworks.com>, <ietf@ietf.org>
References: <28F05913385EAC43AF019413F674A01704A175C6@OCCLUST04EVS1.ugd.att.com>
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 2 Jan 2003 15:51:53 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
X-OriginalArrivalTime: 02 Jan 2003 20:51:53.0906 (UTC) FILETIME=[C7F57920:01C2B2A0]
Sender: owner-ietf@ietf.org
Precedence: bulk

Thanks for the opportunity to comment. I think it is important to document
extensions and modifications made by other bodies to IETF protocols.

I would caution against progressing this draft until the referenced ITU material
(G.7713.3) has reached consent within the ITU since to move it forward at this
stage as an informational RFC might be misleading.

At that point, perhaps Osama could clarify in the draft, that this draft
introduces no new TLVs, messages or procedures others than those already agreed
within the ITU. That is, that this draft is truly informational. Currently the
text reads as though this draft is, itself, defining new material.

With regard to the crankback extensions described in the draft, I would question
whether the information contained in the new Crankback TLV is sufficient to
handle all scenarios and would urge the author to examine
http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt.  It might
be helpful if the draft expanded the description of the contents of the ER-HOP
TLV that is included in the Crankback TLV. However, if the purpose of the draft
is simply to report on the decisions made within the ITU, and if the ITU has
determined that the extensions documented here are sufficient for their purposes
then there is no further work required.

It might be useful in the context of this draft for the author to comment on the
process which led to the definition of the extensions described, why they are
deemed sufficient, and what issues remain to be addressed. This would be
beneficial because the IETF readership has, in general, not been party to the
debate within the ITU.

It would be helpful if, for the error codes, there was some indication of the
circumstances under which the codes can be generated and the actions that should
be taken on receipt of a code. For many, the answers are intuitive (which is not
to say that they should not be described) but for others some description is
necessary.

With regard to IANA considerations...
Has the ITU already assigned TLV and error code numbers? (or in the process of
doing so for G.7713.3). If so, I suggest that this draft should indicate those
numbers. If not, are you asking IANA to allocate numbers from within the space
intended for IETF standardization in which case, how is this draft wholly
informational?

Please note that the correct expansion of GMPLS is Generalized Multi-Protocol
Label Switching, and that the correct expansion of CR-LDP is Constraint-based
Routed Label Distribution Protocol.

In section 4.3, "Crankbck" should read "Crankback"

Should the security section reference draft-ietf-mpls-generalized-cr-ldp-07.txt
rather than RFCs 3036 and 3212? After all, this is really a GMPLS not an MPLS
draft.

References should be split as informational and normative.

Should G.7713.3 be listed as a distinct reference (other than G.7713)?

Regards,
Adrian
-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org]
Sent: Tuesday, December 31, 2002 12:40 PM
Subject: CORRECTION: Last Call: CR-LDP Extensions for ASON to
Informational

**PLEASE NOTE THIS IS A TWO WEEK LAST CALL.**

The IESG has received a request to consider CR-LDP Extensions for ASON
<draft-aboulmagd-ccamp-crldp-ason-ext-02.txt> as an Informational RFC.
This has been reviewed in the IETF but is not the product of an IETF
Working Group.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2003-1-15.

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.txt











From owner-ietf@ietf.org  Thu Jan  2 16:03:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14305;
	Thu, 2 Jan 2003 16:03:41 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UCVe-0005K0-00
	for ietf-list@ran.ietf.org; Thu, 02 Jan 2003 16:04:10 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UBiP-0004Vl-00
	for ietf@ran.ietf.org; Thu, 02 Jan 2003 15:13:17 -0500
Received: from atlntex01.movaz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13012;
	Thu, 2 Jan 2003 15:06:03 -0500 (EST)
Received: from BLIULAPTOP ([172.16.24.104]) by atlntex01.movaz.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 2 Jan 2003 15:09:14 -0500
Message-ID: <022f01c2b29a$d29086f0$681810ac@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: "Osama Aboul-Magd" <osama@nortelnetworks.com>,
        "Ash, Gerald R \(Jerry\), ALASO" <gash@att.com>, <iesg@ietf.org>
Cc: "Atsushi Iwata" <iwata@ccm.CL.nec.co.jp>,
        "Norihito Fujita" <n-fujita@bk.jp.nec.com>,
        "Simon Marshall-Unitt" <smu@dataconnection.com>,
        "Lin, Zhi-Wei \(Zhi\)" <zwlin@lucent.com>, <ietf@ietf.org>,
        "Stephen Shew" <sdshew@nortelnetworks.com>
References: <710197BD5AF9D4119E4400508BCFA1360644904A@zcard04u.ca.nortel.com>
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 2 Jan 2003 15:09:14 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_022C_01C2B270.E975ADC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
X-OriginalArrivalTime: 02 Jan 2003 20:09:14.0450 (UTC) FILETIME=[D2677B20:01C2B29A]
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_022C_01C2B270.E975ADC0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to InformationalHi =
Osama,
It would appear that your draft references several other drafts that are =
not yet RFCs. Will you be removing these references?
Thanks,
Adrian
  ----- Original Message -----=20
  From: Osama Aboul-Magd=20
  To: Ash, Gerald R (Jerry), ALASO ; iesg@ietf.org=20
  Cc: Adrian Farrel ; Atsushi Iwata ; Norihito Fujita ; Simon =
Marshall-Unitt ; Lin, Zhi-Wei (Zhi) ; ietf@ietf.org ; Stephen Shew=20
  Sent: Thursday, January 02, 2003 1:24 PM
  Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to =
Informational


  Hi Gerry,=20

  This draft is not entirely about crankback. It only reflects =
agreements reached at the ITU.=20

  I'd be very happy referencing your draft have it been an RFC. =
Unfortunately ITU rules don't allow the referencing of work that is =
still in progress.

  Regards;=20

  Osama Aboul-Magd=20
  ATI Strategic Standards and Protocols=20
  Nortel Networks=20
  P.O. Box 3511, Station C=20
  Ottawa, Ontario, Canada=20
  K1Y-4H7=20
  Tel: +1 613 763 5827=20
  e.mail:osama@nortelnetworks.com=20



  -----Original Message-----=20
  From: Ash, Gerald R (Jerry), ALASO [mailto:gash@att.com]=20
  Sent: Thursday, January 02, 2003 1:16 PM=20
  To: iesg@ietf.org=20
  Cc: Ash, Gerald R (Jerry), ALASO; Adrian Farrel; Atsushi Iwata; =
Norihito Fujita; Simon Marshall-Unitt; Lin, Zhi-Wei (Zhi); Aboul-Magd, =
Osama [CAR:1A00:EXCH]; ietf@ietf.org

  Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to =
Informational=20

  A crankback TLV is suggested in Section 4.3.  While crankback is a =
desirable extension to both CR-LDP and RSVP-TE (and required by ASON), =
the proposal ignores the prior work done in =
http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt.  =
The advantages of the proposed method should be identified and =
justified. =20

  Furthermore, crankback is not yet within the charter of any IETF =
Working Group, although this has been proposed (e.g., the IETF-54/CCAMP =
minutes state 'The charter update is way overdue. Items may be added - =
protection/restoration, crankback and multi-area operations'). It seems =
inappropriate to specify a particular crankback extension independent of =
the possible future work of an IETF Working Group.

  Jerry Ash=20

  -----Original Message-----=20
  From: The IESG [mailto:iesg-secretary@ietf.org]=20
  Sent: Tuesday, December 31, 2002 12:40 PM=20
  Subject: CORRECTION: Last Call: CR-LDP Extensions for ASON to=20
  Informational=20

  **PLEASE NOTE THIS IS A TWO WEEK LAST CALL.**=20

  The IESG has received a request to consider CR-LDP Extensions for ASON =

  <draft-aboulmagd-ccamp-crldp-ason-ext-02.txt> as an Informational RFC. =
=20
  This has been reviewed in the IETF but is not the product of an IETF=20
  Working Group.=20

  The IESG plans to make a decision in the next few weeks, and solicits=20
  final comments on this action.  Please send any comments to the=20
  iesg@ietf.org or ietf@ietf.org mailing lists by 2003-1-15.=20

  Files can be obtained via =
http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-=
02.txt=20






------=_NextPart_000_022C_01C2B270.E975ADC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: CORRECTION: Last Call: CR-LDP Extensions for ASON =
to Informational</TITLE>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3019.2500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DCourier size=3D2>Hi Osama,</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>It would appear that your draft =
references=20
several other drafts that are not yet RFCs. Will you be removing these=20
references?</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>Adrian</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A href=3D"mailto:osama@nortelnetworks.com" =
title=3Dosama@nortelnetworks.com>Osama=20
  Aboul-Magd</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:gash@att.com"=20
  title=3Dgash@att.com>Ash, Gerald R (Jerry), ALASO</A> ; <A=20
  href=3D"mailto:iesg@ietf.org" title=3Diesg@ietf.org>iesg@ietf.org</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
href=3D"mailto:afarrel@movaz.com"=20
  title=3Dafarrel@movaz.com>Adrian Farrel</A> ; <A=20
  href=3D"mailto:iwata@ccm.CL.nec.co.jp" =
title=3Diwata@ccm.CL.nec.co.jp>Atsushi=20
  Iwata</A> ; <A href=3D"mailto:n-fujita@bk.jp.nec.com"=20
  title=3Dn-fujita@bk.jp.nec.com>Norihito Fujita</A> ; <A=20
  href=3D"mailto:smu@dataconnection.com" =
title=3Dsmu@dataconnection.com>Simon=20
  Marshall-Unitt</A> ; <A href=3D"mailto:zwlin@lucent.com"=20
  title=3Dzwlin@lucent.com>Lin, Zhi-Wei (Zhi)</A> ; <A =
href=3D"mailto:ietf@ietf.org"=20
  title=3Dietf@ietf.org>ietf@ietf.org</A> ; <A=20
  href=3D"mailto:sdshew@nortelnetworks.com"=20
  title=3Dsdshew@nortelnetworks.com>Stephen Shew</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, January 02, =
2003 1:24=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: CORRECTION: Last =
Call:=20
  CR-LDP Extensions for ASON to Informational</DIV>
  <DIV><BR></DIV>
  <P><FONT size=3D2>Hi Gerry,</FONT> </P>
  <P><FONT size=3D2>This draft is not entirely about crankback. It only =
reflects=20
  agreements reached at the ITU.</FONT> </P>
  <P><FONT size=3D2>I'd be very happy referencing your draft have it =
been an RFC.=20
  Unfortunately ITU rules don't allow the referencing of work that is =
still in=20
  progress.</FONT></P>
  <P><FONT size=3D2>Regards;</FONT> </P>
  <P><FONT size=3D2>Osama Aboul-Magd</FONT> <BR><FONT size=3D2>ATI =
Strategic=20
  Standards and Protocols</FONT> <BR><FONT size=3D2>Nortel =
Networks</FONT>=20
  <BR><FONT size=3D2>P.O. Box 3511, Station C</FONT> <BR><FONT =
size=3D2>Ottawa,=20
  Ontario, Canada</FONT> <BR><FONT size=3D2>K1Y-4H7</FONT> <BR><FONT =
size=3D2>Tel:=20
  +1 613 763 5827</FONT> <BR><FONT size=3D2><A=20
  =
href=3D"mailto:e.mail:osama@nortelnetworks.com">e.mail:osama@nortelnetwor=
ks.com</A></FONT>=20
  </P><BR>
  <P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2>From: Ash,=20
  Gerald R (Jerry), ALASO [<A=20
  href=3D"mailto:gash@att.com">mailto:gash@att.com</A>] </FONT><BR><FONT =

  size=3D2>Sent: Thursday, January 02, 2003 1:16 PM</FONT> <BR><FONT =
size=3D2>To: <A=20
  href=3D"mailto:iesg@ietf.org">iesg@ietf.org</A></FONT> <BR><FONT =
size=3D2>Cc: Ash,=20
  Gerald R (Jerry), ALASO; Adrian Farrel; Atsushi Iwata; Norihito =
Fujita; Simon=20
  Marshall-Unitt; Lin, Zhi-Wei (Zhi); Aboul-Magd, Osama [CAR:1A00:EXCH]; =
<A=20
  href=3D"mailto:ietf@ietf.org">ietf@ietf.org</A></FONT></P>
  <P><FONT size=3D2>Subject: RE: CORRECTION: Last Call: CR-LDP =
Extensions for ASON=20
  to Informational</FONT> </P>
  <P><FONT size=3D2>A crankback TLV is suggested in Section 4.3.&nbsp; =
While=20
  crankback is a desirable extension to both CR-LDP and RSVP-TE (and =
required by=20
  ASON), the proposal ignores the prior work done in <A=20
  =
href=3D"http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04=
.txt"=20
  =
target=3D_blank>http://www.ietf.org/internet-drafts/draft-iwata-mpls-cran=
kback-04.txt</A>.&nbsp;=20
  The advantages of the proposed method should be identified and=20
  justified.&nbsp; </FONT></P>
  <P><FONT size=3D2>Furthermore, crankback is not yet within the charter =
of any=20
  IETF Working Group, although this has been proposed (e.g., the =
IETF-54/CCAMP=20
  minutes state 'The charter update is way overdue. Items may be added - =

  protection/restoration, crankback and multi-area operations'). It =
seems=20
  inappropriate to specify a particular crankback extension independent =
of the=20
  possible future work of an IETF Working Group.</FONT></P>
  <P><FONT size=3D2>Jerry Ash</FONT> </P>
  <P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2>From: The=20
  IESG [<A=20
  =
href=3D"mailto:iesg-secretary@ietf.org">mailto:iesg-secretary@ietf.org</A=
>]</FONT>=20
  <BR><FONT size=3D2>Sent: Tuesday, December 31, 2002 12:40 PM</FONT> =
<BR><FONT=20
  size=3D2>Subject: CORRECTION: Last Call: CR-LDP Extensions for ASON =
to</FONT>=20
  <BR><FONT size=3D2>Informational</FONT> </P>
  <P><FONT size=3D2>**PLEASE NOTE THIS IS A TWO WEEK LAST CALL.**</FONT> =
</P>
  <P><FONT size=3D2>The IESG has received a request to consider CR-LDP =
Extensions=20
  for ASON </FONT><BR><FONT=20
  size=3D2>&lt;draft-aboulmagd-ccamp-crldp-ason-ext-02.txt&gt; as an =
Informational=20
  RFC.&nbsp; </FONT><BR><FONT size=3D2>This has been reviewed in the =
IETF but is=20
  not the product of an IETF </FONT><BR><FONT size=3D2>Working =
Group.</FONT> </P>
  <P><FONT size=3D2>The IESG plans to make a decision in the next few =
weeks, and=20
  solicits</FONT> <BR><FONT size=3D2>final comments on this =
action.&nbsp; Please=20
  send any comments to the </FONT><BR><FONT size=3D2>iesg@ietf.org or=20
  ietf@ietf.org mailing lists by 2003-1-15.</FONT> </P>
  <P><FONT size=3D2>Files can be obtained via <A=20
  =
href=3D"http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-a=
son-ext-02.txt"=20
  =
target=3D_blank>http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp=
-crldp-ason-ext-02.txt</A></FONT>=20
  </P><BR><BR><BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_022C_01C2B270.E975ADC0--






From owner-ietf@ietf.org  Thu Jan  2 16:41:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15084;
	Thu, 2 Jan 2003 16:41:16 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UD8L-0007Bu-00
	for ietf-list@ran.ietf.org; Thu, 02 Jan 2003 16:44:09 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UD70-00079l-00
	for ietf@ran.ietf.org; Thu, 02 Jan 2003 16:42:46 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14940;
	Thu, 2 Jan 2003 16:35:33 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h02LZMb20611;
	Thu, 2 Jan 2003 13:35:22 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id VAA22184;
	Thu, 2 Jan 2003 21:35:22 GMT
Date: Thu, 2 Jan 2003 21:35:22 GMT
Message-Id: <200301022135.VAA22184@gra.isi.edu>
To: iesg@ietf.org, afarrel@movaz.com, ietf@ietf.org
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Cc: osama@nortelnetworks.com
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

  *> 
  *> Thanks for the opportunity to comment. I think it is important to document
  *> extensions and modifications made by other bodies to IETF protocols.
  *> 
  *> I would caution against progressing this draft until the referenced ITU
  *> material (G.7713.3) has reached consent within the ITU since to move it
  *> forward at this stage as an informational RFC might be misleading.
  *> 
Adrian,

There is a procedural catch-22 here.  This document was written, I believe,
to satisfy the IANA requirements for documentation oft code points to
be assigned for the ITU.  Presumably the ITU cannot progress their document
until these code points are assigned, yet the IANA is naturally wary about
assigning undocumented code points.

  *> At that point, perhaps Osama could clarify in the draft, that this
  *> draft introduces no new TLVs, messages or procedures others than those
  *> already agreed within the ITU. That is, that this draft is truly
  *> informational. Currently the text reads as though this draft is,
  *> itself, defining new material.

I believe the document implies that, but maybe you need them to say,
"Cross my heart and hope to die if it's not ITU-compliant"?

That said, the RFC Editor was asked to publish this as an independent
submission, and we are following procedures.  Those procedures
include asking the IESG to advise-and-consent to publication, which
led in turn to the Last Call. But the RFC Editor does not want to
publish anything whose confusion factor exceeds the long-term benefits
of publication, so we are pleased to get your input.

Bob Braden for the RFC Editor



From owner-ietf@ietf.org  Thu Jan  2 16:56:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15515;
	Thu, 2 Jan 2003 16:56:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UDMw-00089t-00
	for ietf-list@ran.ietf.org; Thu, 02 Jan 2003 16:59:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UDMk-00088i-00
	for ietf@ran.ietf.org; Thu, 02 Jan 2003 16:59:02 -0500
Received: from hq.lindsayelec.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15416
	for <ietf@ietf.org>; Thu, 2 Jan 2003 16:51:49 -0500 (EST)
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; Thu, 2 Jan 2003 16:54:58 -0500
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: The essential non-weirdness of Son'ys Playstation PS2
Cc: barb@eng.utah.edu, chad@playstation2-linux.com
Date: Thu, 2 Jan 2003 16:54:58 -0500
Message-ID: <20030102215458581.AAA521@hq.lindsayelec.com@rflooker1>
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

I happen to have an aquaintance who taught a course in California on writing
video games. This code fragment example is *hard* to find and *harder* to
believe. 

With the Playstation PS2 selling 27 boxes a minute worldwide... and game
consoles selling 5+ billion $ a year, the box is actually *easy* to program! 

The below is 100% of the source to make some stars fly by. The point is how
totally ordinary this all is. Compiled under Linux with free compilers, yet!

Sony has done a good job of making the last step of making a PS2 compliant
CD very difficult. But, fooling the box for testing is reasonably easy. And
they are not unreasonable about the publishing rights, etc.

The below seems completely accessable. A few weird libraries in the includes
and that's it!
 
I don't know if you find this as unexpected as I do. I visualized it would
take a dozen $100K programs glued together by weirdo "good luck" code to run. 

Don't forget this $250 computer has 15 times the throughput of a Pentium at
1 GHz. And an audiance that would crawl over broken glass to play.

I think the audience on this email reflector might find this interesting.
Hope I'm right on that...

The author is on the CC line and the leading comments. Thanks for WWW access
to this code!

Regards to all,
Dan Kolis



// lilplasma.c
// my non-vpu-using first attempt at PS2 graphics.
// inefficient, but pretty!
//
// - barb@eng.utah.edu
// (or) chad@playstation2-linux.com

// to compile:
// cc -o lilplasma lilplasma.c -lps2dev -lm

#include <stdio.h>
#include <stdlib.h>
#include <assert.h>
#include <unistd.h>
#include <signal.h>
#include <linux/ps2/dev.h>
#include <ps2gs.h>
#include <ps2dma.h>
#include <math.h>

static int gsFd = 0;
static ps2_gs_gparam *gsParam;
static ps2_gs_dbuff gsDb;
static ps2_gs_finish gsFinish;

typedef struct {
  ps2_giftag     tag;
  ps2_gsreg_rgbaq rgb0;
  ps2_gsreg_addr rgb0Addr;
  ps2_gsreg_xyz  xyz0;
  ps2_gsreg_addr xyz0Addr;
  ps2_gsreg_rgbaq rgb1;
  ps2_gsreg_addr rgb1Addr;
  ps2_gsreg_xyz  xyz1;
  ps2_gsreg_addr xyz1Addr;
  ps2_gsreg_rgbaq rgb2;
  ps2_gsreg_addr rgb2Addr;
  ps2_gsreg_xyz  xyz2;
  ps2_gsreg_addr xyz2Addr;
} TriPacket __attribute__((aligned(16)));

static TriPacket triPacket;

static int costa[256];
static int t;

void cleanup()
{
  if (gsFd > 0) { ps2_gs_close(); }
}

void draw();
void renderinit();

int main( int argc, char *argv[] )
{
  int frame, field;
  signal( SIGINT, exit );
  atexit( cleanup );

  //triPacket = memalign( 128, 128 ); 

  gsFd = ps2_gs_open(-1);
  assert( gsFd > 0 );
  gsParam = ps2_gs_get_gparam();
  ps2_gs_vc_graphicsmode();

  ps2_gs_reset( 0, PS2_GS_INTERLACE, PS2_GS_VESA, PS2_GS_FRAME,
PS2_GS_640x480, PS2_GS_60Hz );

  ps2_gs_set_dbuff( &gsDb, PS2_GS_PSMCT32,
    gsParam->width, gsParam->height,
    PS2_GS_TEST_ZTST_NEVER, PS2_GS_PSMZ16S, 0 );

  *(__u64 *)&gsDb.clear0.rgbaq =
    PS2_GS_SETREG_RGBAQ( 0,0,0, 0x80, 0x3f800000 );

  *(__u64 *)&gsDb.clear1.rgbaq =
    PS2_GS_SETREG_RGBAQ( 0,0,0, 0x80, 0x3f800000 );

  //ps2_gs_put_drawenv( &gsDb.giftag1 );

  ps2_gs_set_finish( &gsFinish );
  ps2_gs_wait_finish( &gsFinish );

  ps2_gs_start_display(1);

  field = 0;
  frame = !ps2_gs_sync_v( 0 );
  renderinit();
  while(1) {
    ps2_gs_set_half_offset( frame ? &gsDb.draw1 : &gsDb.draw0, field );
    ps2_gs_swap_dbuff( &gsDb, field );
    draw();
    ps2_gs_wait_finish( &gsFinish );
    frame = !ps2_gs_sync_v( 0 );
    field = field ^ 1;
  }

  return 0;
}
  
void renderinit( )
{
  triPacket.tag.NLOOP = 6;
  triPacket.tag.EOP   = 1;
  triPacket.tag.PRE   = 1;
  triPacket.tag.FLG   = PS2_GIFTAG_FLG_PACKED;
  triPacket.tag.NREG  = 1;
  triPacket.tag.REGS0 = PS2_GIFTAG_REGS_AD;
  triPacket.tag.PRIM  =
    PS2_GS_SETREG_PRIM(
       PS2_GS_PRIM_PRIM_TRIANGLE,
       PS2_GS_PRIM_IIP_GOURAUD,
       PS2_GS_PRIM_TME_OFF,
       PS2_GS_PRIM_FGE_OFF,
       PS2_GS_PRIM_ABE_OFF,      
       PS2_GS_PRIM_AA1_OFF,
       PS2_GS_PRIM_FST_STQ,
       PS2_GS_PRIM_CTXT_CONTEXT1,
       PS2_GS_PRIM_FIX_NOFIXDDA );
  triPacket.rgb0Addr = PS2_GS_RGBAQ;
  triPacket.rgb1Addr = PS2_GS_RGBAQ;
  triPacket.rgb2Addr = PS2_GS_RGBAQ;
  triPacket.xyz0Addr = PS2_GS_XYZF2;
  triPacket.xyz1Addr = PS2_GS_XYZF2;
  triPacket.xyz2Addr = PS2_GS_XYZF2;
  triPacket.xyz0.Z = 0xFFFFFF;
  triPacket.xyz1.Z = 0xFFFFFF;
  triPacket.xyz2.Z = 0xFFFFFF;

  {
    int x;
    for (x = 0; x < 256; x++) {
      costa[x] = (int)(32767.0f * cos((float)x * 3.14159f * 2.0f / 256.0f));
    }
  }
}

void triangle( unsigned char r0,
       unsigned char g0,
       unsigned char b0,
       int x0, int y0,
       unsigned char r1,
       unsigned char g1,
       unsigned char b1,
       int x1, int y1,
       unsigned char r2,
       unsigned char g2,
       unsigned char b2,
       int x2, int y2 )
{
  triPacket.rgb0.R = r0;
  triPacket.rgb0.G = g0;
  triPacket.rgb0.B = b0;
  triPacket.rgb1.R = r1;
  triPacket.rgb1.G = g1;
  triPacket.rgb1.B = b1;
  triPacket.rgb2.R = r2;
  triPacket.rgb2.G = g2;
  triPacket.rgb2.B = b2;

  triPacket.xyz0.X = (gsParam->center_x + x0) << 4;
  triPacket.xyz0.Y = (gsParam->center_y + y0) << 4;
  triPacket.xyz1.X = (gsParam->center_x + x1) << 4;
  triPacket.xyz1.Y = (gsParam->center_y + y1) << 4;
  triPacket.xyz2.X = (gsParam->center_x + x2) << 4;
  triPacket.xyz2.Y = (gsParam->center_y + y2) << 4;

  ps2_gs_put_drawenv( &(triPacket.tag) );
}

void draw()
{
  unsigned char r[64][48];
  unsigned char g[64][48];
  unsigned char b[64][48];
  int x, y;

  t++;

  for (x = 0; x < 17; x++) {
    for (y = 0; y < 13; y++) {
      r[x][y] = (((int)costa[(x * 22 + t * 8) & 255] +
          (int)costa[(y * 19 + t * 6) & 255] +
  (int)costa[((x + x + y) * 9 + t * 4) & 255] +
  (int)costa[((x + x + x + y) * 10 + t * 2) & 255] 
  ) >> 10) + 128;

      g[x][y] = (((int)costa[((x + y + y) * 18 + t * 3) & 255] +
  (int)costa[(y * 32 + t * 9) & 255] +
          (int)costa[(x * 17 - t * 4) & 255] +
  (int)costa[((x + y) * 12 + t * 5) & 255] 
  ) >> 10) + 128;

      b[x][y] = (((int)costa[((x + x + y) * 18 + t * 2) & 255] +
  (int)costa[((y + x) * 8 + t * 7) & 255] +
          (int)costa[(x * 10 - t * 3) & 255] +
          (int)costa[(y * 23 + t * 5) & 255]
  ) >> 10) + 128;
    }
  }

  for (x = 0; x < 16; x++) {
    for (y = 0; y < 12; y++) {
      triangle( r[x][y], g[x][y], b[x][y],
(x - 8) * 40 , (y - 6) * 40,
r[x+1][y], g[x+1][y], b[x+1][y],
(x - 8 + 1) * 40 , (y - 6) * 40,
r[x][y+1], g[x][y+1], b[x][y+1],
(x - 8) * 40 ,  (y - 6+1) * 40 );

      triangle( r[x+1][y], g[x+1][y], b[x+1][y],
(x - 8+1) * 40 , (y - 6) * 40,
r[x+1][y+1], g[x+1][y+1], b[x+1][y+1],
(x - 8+1) * 40 , (y - 6+1) * 40,
r[x][y+1], g[x][y+1], b[x][y+1],
(x - 8)   * 40,  (y - 6+1) * 40 );
    }
  }
}


Document end
02 Jan 2003



Dan Kolis - Lindsay Electronics Ltd dank@hq.lindsayelec.com
50 Mary Street West, Lindsay Ontario Canada K9V 2S7
(705) 324-2196               (705) 324-5474 Fax
An ISO 9001 Company; SCTE Member ISM-127194
/Document end




From owner-ietf@ietf.org  Fri Jan  3 10:03:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10302;
	Fri, 3 Jan 2003 10:03:20 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UTIv-0003uI-00
	for ietf-list@ran.ietf.org; Fri, 03 Jan 2003 10:00:09 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UFQ1-0002gH-00
	for ietf@ran.ietf.org; Thu, 02 Jan 2003 19:10:33 -0500
Received: from zcars04f.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17430;
	Thu, 2 Jan 2003 19:03:17 -0500 (EST)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h0306Ec07091;
	Thu, 2 Jan 2003 19:06:14 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <ZC6R4GKL>; Thu, 2 Jan 2003 19:06:15 -0500
Message-ID: <710197BD5AF9D4119E4400508BCFA13606449146@zcard04u.ca.nortel.com>
From: "Osama Aboul-Magd" <osama@nortelnetworks.com>
To: Adrian Farrel <afarrel@movaz.com>,
        "Ash, Gerald R (Jerry), ALASO"
	 <gash@att.com>, iesg@ietf.org
Cc: Atsushi Iwata <iwata@ccm.CL.nec.co.jp>,
        Norihito Fujita <n-fujita@bk.jp.nec.com>,
        Simon Marshall-Unitt <smu@dataconnection.com>,
        "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>, ietf@ietf.org,
        "Stephen Shew" <sdshew@nortelnetworks.com>
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informat
	ional
Date: Thu, 2 Jan 2003 19:06:14 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2B2BB.EE32FC64"
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_01C2B2BB.EE32FC64
Content-Type: text/plain

Hi Adrian,

 

Those references are not included in the ITU document. Besides I am only
referencing drafts that already are WG documents and progressing at IETF.

 

Regards;

 

Osama Aboul-Magd

ATI Strategic Standards and Protocols

Nortel Networks

P.O. Box 3511, Station C

Ottawa, Ontario, Canada

K1Y-4H7

Tel: +1 613 763 5827

e.mail:osama@nortelnetworks.com

 

-----Original Message-----
From: Adrian Farrel [mailto:afarrel@movaz.com] 
Sent: Thursday, January 02, 2003 3:09 PM
To: Aboul-Magd, Osama [CAR:1A00:EXCH]; Ash, Gerald R (Jerry), ALASO;
iesg@ietf.org
Cc: Atsushi Iwata; Norihito Fujita; Simon Marshall-Unitt; Lin, Zhi-Wei
(Zhi); ietf@ietf.org; Shew, Stephen [SKY:QW33:EXCH]
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to
Informational

 

Hi Osama,

It would appear that your draft references several other drafts that are not
yet RFCs. Will you be removing these references?

Thanks,

Adrian

----- Original Message ----- 

From: Osama <mailto:osama@nortelnetworks.com>  Aboul-Magd 

To: Ash, Gerald R (Jerry), ALASO <mailto:gash@att.com>  ; iesg@ietf.org
<mailto:iesg@ietf.org>  

Cc: Adrian Farrel <mailto:afarrel@movaz.com>  ; Atsushi
<mailto:iwata@ccm.CL.nec.co.jp>  Iwata ; Norihito Fujita
<mailto:n-fujita@bk.jp.nec.com>  ; Simon <mailto:smu@dataconnection.com>
Marshall-Unitt ; Lin, <mailto:zwlin@lucent.com>  Zhi-Wei (Zhi) ;
ietf@ietf.org <mailto:ietf@ietf.org>  ; Stephen
<mailto:sdshew@nortelnetworks.com>  Shew 

Sent: Thursday, January 02, 2003 1:24 PM

Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to
Informational

 

Hi Gerry, 

This draft is not entirely about crankback. It only reflects agreements
reached at the ITU. 

I'd be very happy referencing your draft have it been an RFC. Unfortunately
ITU rules don't allow the referencing of work that is still in progress.

Regards; 

Osama Aboul-Magd 
ATI Strategic Standards and Protocols 
Nortel Networks 
P.O. Box 3511, Station C 
Ottawa, Ontario, Canada 
K1Y-4H7 
Tel: +1 613 763 5827 
e.mail:osama@nortelnetworks.com <mailto:e.mail:osama@nortelnetworks.com>  

 

-----Original Message----- 
From: Ash, Gerald R (Jerry), ALASO [mailto:gash@att.com
<mailto:gash@att.com> ] 
Sent: Thursday, January 02, 2003 1:16 PM 
To: iesg@ietf.org <mailto:iesg@ietf.org>  
Cc: Ash, Gerald R (Jerry), ALASO; Adrian Farrel; Atsushi Iwata; Norihito
Fujita; Simon Marshall-Unitt; Lin, Zhi-Wei (Zhi); Aboul-Magd, Osama
[CAR:1A00:EXCH]; ietf@ietf.org <mailto:ietf@ietf.org> 

Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to
Informational 

A crankback TLV is suggested in Section 4.3.  While crankback is a desirable
extension to both CR-LDP and RSVP-TE (and required by ASON), the proposal
ignores the prior work done in
http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt
<http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt> .
The advantages of the proposed method should be identified and justified.  

Furthermore, crankback is not yet within the charter of any IETF Working
Group, although this has been proposed (e.g., the IETF-54/CCAMP minutes
state 'The charter update is way overdue. Items may be added -
protection/restoration, crankback and multi-area operations'). It seems
inappropriate to specify a particular crankback extension independent of the
possible future work of an IETF Working Group.

Jerry Ash 

-----Original Message----- 
From: The IESG [mailto:iesg-secretary@ietf.org
<mailto:iesg-secretary@ietf.org> ] 
Sent: Tuesday, December 31, 2002 12:40 PM 
Subject: CORRECTION: Last Call: CR-LDP Extensions for ASON to 
Informational 

**PLEASE NOTE THIS IS A TWO WEEK LAST CALL.** 

The IESG has received a request to consider CR-LDP Extensions for ASON 
<draft-aboulmagd-ccamp-crldp-ason-ext-02.txt> as an Informational RFC.  
This has been reviewed in the IETF but is not the product of an IETF 
Working Group. 

The IESG plans to make a decision in the next few weeks, and solicits 
final comments on this action.  Please send any comments to the 
iesg@ietf.org or ietf@ietf.org mailing lists by 2003-1-15. 

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.
txt
<http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02
.txt>  






------_=_NextPart_001_01C2B2BB.EE32FC64
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">


<meta name=Generator content="Microsoft Word 10 (filtered)">
<title>RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational</title>

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:HGSoeiKakupoptai;
	panose-1:4 11 10 9 0 0 0 0 0 0;}
@font-face
	{font-family:"\@HGSoeiKakupoptai";
	panose-1:4 11 10 9 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{margin-right:0in;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body bgcolor=white lang=EN-US link=blue vlink=blue>

<div class=Section1>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Hi Adrian,</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Those references are not included in the
ITU document. Besides I am only referencing drafts that already are WG
documents and progressing at IETF.</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Regards;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<div>

<p class=MsoNormal><font size=3 color=navy face=HGSoeiKakupoptai><span
style='font-size:12.0pt;font-family:HGSoeiKakupoptai;color:navy'>Osama
Aboul-Magd</span></font></p>

<p class=MsoNormal><b><font size=3 color="#ff6600" face="Times New Roman"><span
style='font-size:12.0pt;color:#FF6600;font-weight:bold'>ATI Strategic Standards
and Protocols</span></font></b></p>

<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
style='font-size:12.0pt;color:navy'>Nortel Networks</span></font></p>

<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
style='font-size:12.0pt;color:navy'>P.O. Box 3511, Station C</span></font></p>

<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
style='font-size:12.0pt;color:navy'>Ottawa, Ontario, Canada</span></font></p>

<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
lang=FR style='font-size:12.0pt;color:navy'>K1Y-4H7</span></font></p>

<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
lang=FR style='font-size:12.0pt;color:navy'>Tel: +1 613 763 5827</span></font></p>

<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
lang=FR style='font-size:12.0pt;color:navy'>e.mail:osama@nortelnetworks.com</span></font></p>

</div>

<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=FR
style='font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Adrian Farrel
[mailto:afarrel@movaz.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, January 02, 2003
3:09 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Aboul-Magd, Osama
[CAR:1A00:EXCH]; Ash, Gerald R (Jerry), ALASO; iesg@ietf.org<br>
<b><span style='font-weight:bold'>Cc:</span></b> Atsushi Iwata; Norihito
Fujita; Simon Marshall-Unitt; Lin, Zhi-Wei (Zhi); ietf@ietf.org; Shew, Stephen
[SKY:QW33:EXCH]<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: CORRECTION: Last
Call: CR-LDP Extensions for ASON to Informational</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>&nbsp;</span></font></p>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Courier><span
style='font-size:10.0pt;font-family:Courier'>Hi Osama,</span></font></p>

</div>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Courier><span
style='font-size:10.0pt;font-family:Courier'>It would appear that your draft
references several other drafts that are not yet RFCs. Will you be removing
these references?</span></font></p>

</div>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Courier><span
style='font-size:10.0pt;font-family:Courier'>Thanks,</span></font></p>

</div>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Courier><span
style='font-size:10.0pt;font-family:Courier'>Adrian</span></font></p>

</div>

<blockquote style='border:none;border-left:solid black 1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>----- Original Message ----- </span></font></p>

</div>

<div style='font-color:black'>

<p class=MsoNormal style='margin-left:.5in;background:#E4E4E4'><b><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial;font-weight:bold'>From:</span></font></b><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> <a
href="mailto:osama@nortelnetworks.com" title="osama@nortelnetworks.com">Osama
Aboul-Magd</a> </span></font></p>

</div>

<div>

<p class=MsoNormal style='margin-left:.5in'><b><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial;font-weight:bold'>To:</span></font></b><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> <a
href="mailto:gash@att.com" title="gash@att.com">Ash, Gerald R (Jerry), ALASO</a>
; <a href="mailto:iesg@ietf.org" title="iesg@ietf.org">iesg@ietf.org</a> </span></font></p>

</div>

<div>

<p class=MsoNormal style='margin-left:.5in'><b><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial;font-weight:bold'>Cc:</span></font></b><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> <a
href="mailto:afarrel@movaz.com" title="afarrel@movaz.com">Adrian Farrel</a> ; <a
href="mailto:iwata@ccm.CL.nec.co.jp" title="iwata@ccm.CL.nec.co.jp">Atsushi
Iwata</a> ; <a href="mailto:n-fujita@bk.jp.nec.com"
title="n-fujita@bk.jp.nec.com">Norihito Fujita</a> ; <a
href="mailto:smu@dataconnection.com" title="smu@dataconnection.com">Simon
Marshall-Unitt</a> ; <a href="mailto:zwlin@lucent.com" title="zwlin@lucent.com">Lin,
Zhi-Wei (Zhi)</a> ; <a href="mailto:ietf@ietf.org" title="ietf@ietf.org">ietf@ietf.org</a>
; <a href="mailto:sdshew@nortelnetworks.com" title="sdshew@nortelnetworks.com">Stephen
Shew</a> </span></font></p>

</div>

<div>

<p class=MsoNormal style='margin-left:.5in'><b><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial;font-weight:bold'>Sent:</span></font></b><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> Thursday,
January 02, 2003 1:24 PM</span></font></p>

</div>

<div>

<p class=MsoNormal style='margin-left:.5in'><b><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial;font-weight:bold'>Subject:</span></font></b><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> RE:
CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational</span></font></p>

</div>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>Hi Gerry,</span></font> </p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>This draft is not entirely about crankback. It only
reflects agreements reached at the ITU.</span></font> </p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>I'd be very happy referencing your draft have it been
an RFC. Unfortunately ITU rules don't allow the referencing of work that is
still in progress.</span></font></p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>Regards;</span></font> </p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>Osama Aboul-Magd</span></font> <br>
<font size=2><span style='font-size:10.0pt'>ATI Strategic Standards and
Protocols</span></font> <br>
<font size=2><span style='font-size:10.0pt'>Nortel Networks</span></font> <br>
<font size=2><span style='font-size:10.0pt'>P.O. Box 3511, Station C</span></font>
<br>
<font size=2><span style='font-size:10.0pt'>Ottawa, Ontario, Canada</span></font>
<br>
<font size=2><span style='font-size:10.0pt'>K1Y-4H7</span></font> <br>
<font size=2><span style='font-size:10.0pt'>Tel: +1 613 763 5827</span></font> <br>
<font size=2><span style='font-size:10.0pt'><a
href="mailto:e.mail:osama@nortelnetworks.com">e.mail:osama@nortelnetworks.com</a></span></font>
</p>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>&nbsp;</span></font></p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>-----Original Message-----</span></font> <br>
<font size=2><span style='font-size:10.0pt'>From: Ash, Gerald R (Jerry), ALASO
[<a href="mailto:gash@att.com">mailto:gash@att.com</a>] </span></font><br>
<font size=2><span style='font-size:10.0pt'>Sent: Thursday, January 02, 2003
1:16 PM</span></font> <br>
<font size=2><span style='font-size:10.0pt'>To: <a href="mailto:iesg@ietf.org">iesg@ietf.org</a></span></font>
<br>
<font size=2><span style='font-size:10.0pt'>Cc: Ash, Gerald R (Jerry), ALASO;
Adrian Farrel; Atsushi Iwata; Norihito Fujita; Simon Marshall-Unitt; Lin,
Zhi-Wei (Zhi); Aboul-Magd, Osama [CAR:1A00:EXCH]; <a href="mailto:ietf@ietf.org">ietf@ietf.org</a></span></font></p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>Subject: RE: CORRECTION: Last Call: CR-LDP Extensions
for ASON to Informational</span></font> </p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>A crankback TLV is suggested in Section 4.3.&nbsp;
While crankback is a desirable extension to both CR-LDP and RSVP-TE (and required
by ASON), the proposal ignores the prior work done in <a
href="http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt"
target="_blank">http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt</a>.&nbsp;
The advantages of the proposed method should be identified and justified.&nbsp;
</span></font></p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>Furthermore, crankback is not yet within the charter
of any IETF Working Group, although this has been proposed (e.g., the
IETF-54/CCAMP minutes state 'The charter update is way overdue. Items may be
added - protection/restoration, crankback and multi-area operations'). It seems
inappropriate to specify a particular crankback extension independent of the
possible future work of an IETF Working Group.</span></font></p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>Jerry Ash</span></font> </p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>-----Original Message-----</span></font> <br>
<font size=2><span style='font-size:10.0pt'>From: The IESG [<a
href="mailto:iesg-secretary@ietf.org">mailto:iesg-secretary@ietf.org</a>]</span></font>
<br>
<font size=2><span style='font-size:10.0pt'>Sent: Tuesday, December 31, 2002
12:40 PM</span></font> <br>
<font size=2><span style='font-size:10.0pt'>Subject: CORRECTION: Last Call:
CR-LDP Extensions for ASON to</span></font> <br>
<font size=2><span style='font-size:10.0pt'>Informational</span></font> </p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>**PLEASE NOTE THIS IS A TWO WEEK LAST CALL.**</span></font>
</p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>The IESG has received a request to consider CR-LDP
Extensions for ASON </span></font><br>
<font size=2><span style='font-size:10.0pt'>&lt;draft-aboulmagd-ccamp-crldp-ason-ext-02.txt&gt;
as an Informational RFC.&nbsp; </span></font><br>
<font size=2><span style='font-size:10.0pt'>This has been reviewed in the IETF
but is not the product of an IETF </span></font><br>
<font size=2><span style='font-size:10.0pt'>Working Group.</span></font> </p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>The IESG plans to make a decision in the next few
weeks, and solicits</span></font> <br>
<font size=2><span style='font-size:10.0pt'>final comments on this
action.&nbsp; Please send any comments to the </span></font><br>
<font size=2><span style='font-size:10.0pt'>iesg@ietf.org or ietf@ietf.org
mailing lists by 2003-1-15.</span></font> </p>

<p style='margin-left:.5in'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>Files can be obtained via <a
href="http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.txt"
target="_blank">http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.txt</a></span></font>
</p>

<p class=MsoNormal style='margin-right:0in;margin-bottom:12.0pt;margin-left:
.5in'><font size=3 face="Times New Roman"><span style='font-size:12.0pt'><br>
<br>
</span></font></p>

</blockquote>

</div>

</body>

</html>

------_=_NextPart_001_01C2B2BB.EE32FC64--





From owner-ietf@ietf.org  Fri Jan  3 15:45:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18756;
	Fri, 3 Jan 2003 15:45:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UYaz-0005PB-00
	for ietf-list@ran.ietf.org; Fri, 03 Jan 2003 15:39:09 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UYaW-0005O0-00
	for ietf@ran.ietf.org; Fri, 03 Jan 2003 15:38:40 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18466
	for <ietf@ietf.org>; Fri, 3 Jan 2003 15:31:13 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 9A6D062414
	for <ietf@ietf.org>; Fri,  3 Jan 2003 21:34:24 +0100 (CET)
Date: Fri, 03 Jan 2003 21:34:24 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Power outage on some IETF lists' host
Message-ID: <174500000.1041626064@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


The site hosting ops.ietf.org, subip.ietf.org, psg.com and various WG 
mailing lists is without connectivity because of a storm and a resulting 
power failure.

We do not yet know when they will be available again, but under the 
circumstances, it could take some time.

Just so you know....

                Harald




From owner-ietf@ietf.org  Sat Jan  4 03:25:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07716;
	Sat, 4 Jan 2003 03:25:09 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UjU3-00075t-00
	for ietf-list@ran.ietf.org; Sat, 04 Jan 2003 03:16:43 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18UjT2-00074x-00
	for ietf@ran.ietf.org; Sat, 04 Jan 2003 03:15:41 -0500
Received: from ratree.psu.ac.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07568;
	Sat, 4 Jan 2003 03:07:57 -0500 (EST)
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 h048APV20618;
	Sat, 4 Jan 2003 15:10:26 +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 h0487S813463;
	Sat, 4 Jan 2003 19:07:29 +1100 (EST)
From: Robert Elz <kre@munnari.OZ.AU>
To: iab@iab.org
cc: iesg@ietf.org, ietf@ietf.org, rfc-editor@isi.edu
Subject: Appeal against IESG decision
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 04 Jan 2003 15:07:28 +0700
Message-ID: <13461.1041667648@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

This is an appeal to the IAB against the IESG decision to reject
my appeal against their earlier decision to approve the publication
of draft-ietf-ipngwg-addr-arch-v3-11.txt as a Draft Standard.

The issues here are very simple, and no lengthy examination of mailing
list archives, taking of evidence, hearing opinions, ... should be
necessary in this case.   I believe that none of the facts are in any
kind of dispute.

Those facts are

1) RFC2026 says, in section 4.1.2 ...

   A specification from which at least two independent and interoperable
   implementations from different code bases have been developed, and
   for which sufficient successful operational experience has been
   obtained, may be elevated to the "Draft Standard" level. [...]

   The requirement for at least two independent and interoperable
   implementations applies to all of the options and features of the
   specification.  In cases in which one or more options or features
   have not been demonstrated in at least two interoperable
   implementations, the specification may advance to the Draft Standard
   level only if those options or features are removed.

2) draft-ietf-ipngwg-addr-arch-v3-11.txt contains at least one (and perhaps
two) features for which there are not two interoperable implementations.

The one is:

	For all unicast addresses, except those that start with binary 
	value 000, Interface IDs are required to be 64 bits long and 
	to be constructed in Modified EUI-64 format.

There's no dispute that there are no interoperable implementations of
this - there are no implementations of it at all (or no documented ones
anyway).

Note that the spec actually gives no option here, other than the exceptions
(the 000 addresses, and multicast), interface IDs are required to be 64
bits long.    While all implementations I'm aware of allow 64 bit IDs,
none have been presented that require it.  The draft *requires* it.

Any reasonable reading of 2026 would require that that feature of the
specification be removed from the draft before the draft is permitted to
be published as a draft standard.   Of course, as an alternative, the WG
or IESG could have the draft, as it is, published as a Proposed Standard,
and await the necessary two implementations of the feature before requesting
advancement.

The IESG's opinion of this seems to be that the "two implementations of
every feature" applies only where they consider it important enough to
bother checking.   I have no problems with drafts advancing when no-one
brings to the attention of the IESG that there is a problem in this area.
But when a problem is pointed out, the clear words of 2026 really must be
enforced.

The rationale for this requirement in 2026 is simple (as the IESG should
know, as the author of 2026 is a member of the IESG).   First, it ensures
that the text in the document is clear enough that it can be implemented
in an interoperable way.   And second, it helps make sure that the
document doesn't get cluttered with requirements in practice no-one
bothers to implement - that is, that the document is a proper specification,
and anyone reading the document can implement from it, with the
expectation that their implementation will interoperate with others.

The quoted text from the draft fails both of those tests.   We have no
implementations so we don't know that the text is clear enough to be
implemented correctly.   It may seem obvious that the text is clear to
any reader - but the IETF has always ignored "seem obvious" and required
actual implementation experience as a demonstration.

Second, an implementation which did faithfully follow the words of the
draft would fail to interoperate correctly with every other known
implementation of it.   It may be claimed that it is the other
implementations, or the way they are configured, that is at fault here,
but that's not relevant - the aim is to get interoperability, and if
we have operators configuring /112, /226, /227 and similar prefix
lengths (that is, interface ID's that are 16, 2, or 1, and other,
numbers of bits long) - and we do - then an implementation that enforced
the 64 bit IID requirement (allowed only /64 prefix on an interface)
would fail to interoperate with other implementations (with all other
existing implementations).

This seems to be a "placeholder" fluff feature, being maintained to
perhaps allow some future design to allow applications to simply "know"
what is the prefix, and what is the interface-ID.   The requirement for
existing implementations in 2026 is a specific requirement that such
fluff be removed from docs before they're allowed to advance to DS status.

The extra requirement should be removed from the document, and then, if
the WG so desires, published as a PS (or Experimental) RFC of its own.
If it then becomes accepted and implemented, it could be merged back with
the main document in a later revision.


The second issue in the appeal to the IESG concerned the 'u' bit, which
is one of the bits of the IID as defined.

The IESG referred to this as ...

 B/ Robert says "The requirement that where the 'u' bit (the inverted L 
 bit from the MAC address) is set, the IID is globally unique."

and eventually concluded ...

 The IESG notes that there is no wording in
 draft-ietf-ipngwg-addr-arch-v3-11.txt requiring that IIDs be globally
 unique.

and then quoted two passages from the draft, only the last part of
which is relevant.

   In
   the resulting Modified EUI-64 format the "u" bit is set to one (1) to
   indicate global scope, and it is set to zero (0) to indicate local
   scope.

It is true that the doc does not expressly say "globally unique", what
it says is "indicate global scope".

The draft also says ...

   Modified EUI-64 format based Interface identifiers may have global
   scope when derived from a global token (e.g., IEEE 802 48-bit MAC or
   IEEE EUI-64 identifiers [EUI64]) or may have local scope [...]

And ...

   The use of the universal/local bit in the Modified EUI-64 format
   identifier is to allow development of future technology that can take
   advantage of interface identifiers with global scope.

I doubt I'm the only reader to come to the conclusion that "have global
scope" actually means "be globally unique".   What's more, a review of
various IPv6 related mailing lists will show this opinion expressed over
and over again.   Clearly there are many readers who have leapt to this
wrong conclusion, if it is in fact wrong, and as the IESG have concluded,
there is no actual expectation that the IID will be any more than probably
globally unique, then the draft should probably be more explicit in saying
that, rather than allowing readers to leap to the incorrect interpretation.

But there is more to this than the IESG apparently understood.   The question
isn't just whether the 'u' bit being set implies that the IID is globally
unique (or has "global scope") but whether there are any implementations at
all that actually enforce the setting of the 'u' bit only when the IID
has been formed from a (probably) globally unique token (a MAC address
or similar).   Here there has been one implementation reported on the
mailing list (but not in the interoperability report) - but for DS status,
one implementation isn't enough.

Other implementations allow the user to configure the 'u' bit set without
having any knowledge or expectation, or reason to assume, that the address
is derived from any kind of globally unique token (or token with global scope).
What's more, they do this for good reason, as without that ability, users have
no way to remove a NIC, and replace it with another, and retain the original
(auto-configured) IPv6 address (which being based upon the MAC address that
the old NIC provided, would have had the 'u' bit set).   In this case the
address is in fact based upon a globally unique token, but the implementation
has no way to know that, and so must also allow the 'u' bit to be set when
the rest of the IID is 0, or 1, or 2, which are most certainly not tokens
with any kind of global scope.    What's more, as the old NIC may be now in
use in some other host, there's no reason in the example cited to assume that
there's any uniqueness at all - for correct IPv6 operation, the NIC can't
be connected to the same subnet as where it used to be, but beyond that
IPv6 works just fine with the same IID on different nets).

Once again, we have a feature of the specification which is either not
implemented, or at best, is not clear.

The IESG's response to all of this is ...

 When considering this appeal, it is clear from the interoperability
 reports that there are implementations that generate the interface ID
 from the EUI-64 identifier, which makes it be 64 bits long. It is
 also clear that the uniqueness properties of EUI-64 based identifiers
 will be the same as the EUI-64 identifiers from which they are derived
 (which is slightly weaker than a requirement for global uniqueness).

Yes - though in practice implementations (bar one) allow addresses to be
generated from EUI-64's, but they also allow indistinguishable addresses
to be manually configured - so in practice (which is what the interoperable
implementation requirement is attempting to ensure that the specification
conforms to) extracting an IID from an IPv6 address, and expecting it to
have any kind of similar properties of global uniqueness as an EUI-64
would be a false expectation, and the draft should not lead people into
expecting otherwise.   Only if implementations actually enforced this
requirement (which they can easily do, as the one which has done it shows,
though of course, this loses functionality) would this expectation be
justified.

 So for at least some implementations, they are capable of acting as
 specified in the document being challenged.

No.   The requirement challenged is a "must only be" - or if you like,
a MUST NOT.   The fact that it is possible to conform with the spec
using existing implementations has nothing to do with the issue at all.

The IESG's response here would be the equivalent of responding to a
requirement that "All cars must be red" by pointing to a few red cars
and saying "see, it can be done".   That it can be done isn't the issue,
the issue is that the specification says it MUST be done.   To be advanced
to DS, all that is required is that there be 2 conforming implementations,
what the rest do is irrelevant (until the doc is ready to be advanced to full
standard).   For some specifications, 2 implementations itself is a large
hurdle, for IPv6, it isn't, there are many implementations.   That none
of them have implemented one of the requirements of the doc, and only one
another, should be a pretty obvious red flag that these requirements should
not remain in the document.

The IESG also says ...

 We traditionally require that things interoperate when configured 
 correctly, not that they interoperate when configured incorrectly, or 
 that it be impossible to configure them incorrectly.

Of course, that's as it should be.   That is, except where the specification
explicitly says that something must not be possible.   There's no point
keeping a prohibition in the specification if no-one takes any notice of
it.   There's no difference here to keeping some other feature that no-one
bothers to implement.

And again from the IESG ...

 Implementation reports are used to verify that independent 
 implementations can succesfully interoperate. This is a quality check 
 on the clarity of the documents.

Yes.   But the IESG have managed to conveniently forget the other purpose
for the requirement - that is, as a check that the features are actually
being implemented, and that the document isn't describing things which in
practice everyone ignores.

But even without that, here we have no quality check on the clarity of
the relevant statements in the documents - no-one has implemented them.
(No-one has implemented one, there's only one implementation of the other).
We're only guessing if we assume that the statements are clear enough.

IESG again:

 Requiring explicit verification on all statements would be a change to 
 existing practice and one that would likely increase the difficulty in 
 advancing documents on the standards track.

That's what was intended.   If existing practice has been to ignore
the two implementation requirement, when it is known not to be met,
then I submit that the IESG has been operating contrary to the clear
instructions of 2026.

It need not be onerous to enforce this however - it is entirely reasonable
to expect the community to point out any flaws in the implementation
reports as published.   If there are no reported problems, the IESG,
and the community, are justified in assuming that the reports fully
document the required interoperability of every feature.   Where there
are reports that interoperability of some feature has not been properly
documented, then it should be easy for the implementation report to be
corrected, if the feature has in fact been implemented and tested.  If it
has been implemented, but not tested, then the report should be seen as
being of benefit, in showing a potential trouble area, not as a burden.
If testing shows that all works, then there's real harm done, and the
implementation report can be corrected.   If testing shows 
non-interoperability, then clearly there's something that needs fixing
(in some cases, just implementation bugs, after which further testing
will show the specification is fine).   On the other hand if testing is
not possible, because the feature has not been implemented, then it really
should be removed from the document before it is advanced.   That's what
the requirement in 2026 is there for.

The IESG again ...

 There are many places in IETF standards where a field is stated to be
 a specific length or a value to be within a range. Requiring that the
 limits be enforced in software for all of these cases would put a
 significant extra burden on the implementers and the documenters of
 the implementations for questionable benefit.

This is once again based upon a misunderstanding of what is required.
No-one is requiring that the limits be enforced in general.   What is
being asked is that someone (sometwo really) has done it.   What's the
point of a requirement that is universally ignored?   There is none,
it is misleading, and should not be permitted in a Draft Standard.

I would ask that the IAB instruct the IESG to overturn their decision
to publish the draft (draft-ietf-ipngwg-addr-arch-v3-11.txt) as a
Draft Standard, and at their choice, either publish it as a Proposed
Standard, or return it to the working group for amendments that will
allow it to be published as a Draft Standard.

kre

ps: I would also request that the RFC editor continue to defer
publication of this draft until the IAB has dealt with this appeal.




From owner-ietf@ietf.org  Sat Jan  4 10:29:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12292;
	Sat, 4 Jan 2003 10:29:56 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Uq4r-0004MJ-00
	for ietf-list@ran.ietf.org; Sat, 04 Jan 2003 10:19:09 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Uq12-0004KF-00
	for ietf@ran.ietf.org; Sat, 04 Jan 2003 10:15:12 -0500
Received: from mail.enyo.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12087
	for <ietf@ietf.org>; Sat, 4 Jan 2003 10:07:32 -0500 (EST)
Received: from [212.9.189.171] (helo=deneb.enyo.de)
	by mail.enyo.de with esmtp (Exim 3.34 #2)
	id 18Upvq-0004wA-00
	for ietf@ietf.org; Sat, 04 Jan 2003 16:09:50 +0100
Received: from fw by deneb.enyo.de with local (Exim 3.34 #4)
	id 18Upwh-0000SF-00
	for ietf@ietf.org; Sat, 04 Jan 2003 16:10:43 +0100
To: ietf@ietf.org
Subject: RFC authoring tools
From: Florian Weimer <fw@deneb.enyo.de>
Mail-Followup-To: ietf@ietf.org
Date: Sat, 04 Jan 2003 16:10:43 +0100
Message-ID: <87r8btrlvw.fsf@deneb.enyo.de>
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i686-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Are there any tools which can produce documents in standard RFC format
from high-level markup?

These feature are required:

 - source format is human-readable ASCII (with embedded markup)
 - high-level, non-visual markup
 - libre conversion software to RFC format
 - automatic generation of cross references, bibliographical
   information, and table of contents

Wishlist items are:

 - conversion to nice-looking PDF 
 - conversion to HTML
 - conditional inclusion of pieces, depending on the output format
   (ASCII art for text version, bitmap for HTML etc.)

Whether the tool is based on SGML, XML, (La)TeX or *roff doesn't
really matter to me.



From owner-ietf@ietf.org  Sat Jan  4 14:14:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14728;
	Sat, 4 Jan 2003 14:14:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UtgQ-0001Fd-00
	for ietf-list@ran.ietf.org; Sat, 04 Jan 2003 14:10:10 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Utg5-0001Eu-00
	for ietf@ran.ietf.org; Sat, 04 Jan 2003 14:09:49 -0500
Received: from agitator.ibr.cs.tu-bs.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14613
	for <ietf@ietf.org>; Sat, 4 Jan 2003 14:02:09 -0500 (EST)
Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81])
	by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h04J5JBU006310
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL);
	Sat, 4 Jan 2003 20:05:19 +0100
Received: from hansa.ibr.cs.tu-bs.de (strauss@localhost [127.0.0.1])
	by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h04J5JAa026029
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL);
	Sat, 4 Jan 2003 20:05:19 +0100
Received: (from strauss@localhost)
	by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h04J5JNo026026;
	Sat, 4 Jan 2003 20:05:19 +0100
From: Frank Strauss <strauss@ibr.cs.tu-bs.de>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: ietf@ietf.org
Subject: Re: RFC authoring tools
References: <87r8btrlvw.fsf@deneb.enyo.de>
Date: 04 Jan 2003 20:05:19 +0100
In-Reply-To: <87r8btrlvw.fsf@deneb.enyo.de>
Message-ID: <ypwwulkzqfk.fsf@hansa.ibr.cs.tu-bs.de>
Lines: 15
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi!

Florian> Are there any tools which can produce documents in standard
Florian> RFC format from high-level markup? [...]

See RFC 2629 (Writing I-Ds and RFCs using XML) by Marshall T. Rose.

This document describes a DTD and its application for authoring
RFC-like documents. It also contains references to his open source
tool "xml2rfc" that allows to compile such XML documents to IETF
conformant text files and to HTML pages. 

I used it for some documents and I really like it a lot.

 -frank



From owner-ietf@ietf.org  Sat Jan  4 14:14:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14726;
	Sat, 4 Jan 2003 14:14:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18UtjL-0001HW-00
	for ietf-list@ran.ietf.org; Sat, 04 Jan 2003 14:13:11 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Uti9-0001GL-00
	for ietf@ran.ietf.org; Sat, 04 Jan 2003 14:11:57 -0500
Received: from exchange.ad.skymv.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14628
	for <ietf@ietf.org>; Sat, 4 Jan 2003 14:04:17 -0500 (EST)
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
X-Habeas-SWE-8: Message (HCM) and not spam.  Please report use of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
content-class: urn:content-classes:message
Subject: RE: RFC authoring tools
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Importance: normal
Date: Sat, 4 Jan 2003 11:07:20 -0800
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <138AA78F80DCE84B8EE424399FFBF9C907C9B1@exchange.ad.skymv.com>
Thread-Topic: RFC authoring tools
Thread-Index: AcK0B0bvX8/QB1JVQEOHR8edwicY1wAHRtdA
From: "Dan Kohn" <dan@dankohn.com>
To: "Florian Weimer" <fw@deneb.enyo.de>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA14726

Are you in luck.  Marshall Rose has provided us with a lovely little
tool called xml2rfc, which also supports output to HTML.

http://xml.resource.org/

          - dan
--
Dan Kohn <mailto:dan@dankohn.com>
<http://www.dankohn.com/>  <tel:+1-650-327-2600>  

  Randomly generated quote:
As the British Constitution is the most subtle organism which has
proceeded from the womb and long gestation of progressive history, so
the American Constitution is, so far as I can see, the most wonderful
work ever struck off at a given time by the brain and purpose of man.  -
W.E. Gladstone


-----Original Message-----
From: Florian Weimer [mailto:fw@deneb.enyo.de] 
Sent: Saturday, January 04, 2003 07:11
To: ietf@ietf.org
Subject: RFC authoring tools


Are there any tools which can produce documents in standard RFC format
from high-level markup?

These feature are required:

 - source format is human-readable ASCII (with embedded markup)
 - high-level, non-visual markup
 - libre conversion software to RFC format
 - automatic generation of cross references, bibliographical
   information, and table of contents

Wishlist items are:

 - conversion to nice-looking PDF 
 - conversion to HTML
 - conditional inclusion of pieces, depending on the output format
   (ASCII art for text version, bitmap for HTML etc.)

Whether the tool is based on SGML, XML, (La)TeX or *roff doesn't
really matter to me.

_______________________________________________
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  Sun Jan  5 19:28:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12582;
	Sun, 5 Jan 2003 19:28:24 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VKqK-0003ZM-00
	for ietf-list@ran.ietf.org; Sun, 05 Jan 2003 19:10:12 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VKpU-0003Yy-00
	for ietf@ran.ietf.org; Sun, 05 Jan 2003 19:09:20 -0500
Received: from ncsmtp03.ogw.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12312;
	Sun, 5 Jan 2003 19:01:20 -0500 (EST)
Received: from mail5.carolina.rr.com (fe5 [24.93.67.52])
	by ncsmtp03.ogw.rr.com (8.12.5/8.12.2) with ESMTP id h0603mib029872;
	Sun, 5 Jan 2003 19:03:49 -0500 (EST)
Received: from dougpro ([24.88.167.199]) by mail5.carolina.rr.com  with Microsoft SMTPSVC(5.5.1877.757.75);
	 Sun, 5 Jan 2003 19:03:08 -0500
Message-ID: <02fc01c2b517$36d4dbb0$0701a8c0@nailed.org>
From: "Doug" <Dougxx2@carolina.rr.com>
To: "Fred Baker" <fred@cisco.com>
Cc: <ietf@ietf.org>, <namedroppers@ops.ietf.org>, <iesg@ietf.org>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>
References: <5.2.0.9.2.20021206132845.01b56f88@mira-sjcm-4.cisco.com>
Subject: Re: namedroppers, continued
Date: Sun, 5 Jan 2003 19:04:41 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello everyone,

It seems to me if the mail server administrators would make the decision to
require people that send emails from their servers to log into a valid
account on that server and use the same valid account on the server as a
return address it would negate the ability of a large percentage of the
spamers to send the spam anon. This would allow easier filtering of many of
the offending messages by domain. Additionally, the sending account field
and the reply to field should be equal and clients should be required to use
an email address that is associated with the account used to log into the
server in the first place. This will need to be implemented in the beginning
by administrators who run software capable of it, and it would be
implemented later as part of the email client and/or server software using
new software releases, patches, and individual customizations of existing
software. I know that there are many people who will scream and gnash their
teeth at this suggestion as it will force them to identify themselves to
anon mailing lists but I think it would be an acceptable compromise if we
could eliminate a major portion of the spam clogging our inboxes. Clients
need to be identified by ISP based email servers using their DNS and IP
address footprints and clients attempting to send email with improper
footprints should be disregarded (making it very difficult to send email
from the server if you truly are not a valid subscriber to the service, much
like many of the current news servers do). Then to deal with the anonymous
email servers out there (hotmail, yahoo, etc...) the operators of those
services should require clients logging into those accounts to send email
from a valid IP address with no unsecured proxy services running on them
(much like many IRC servers are doing) and transmit this IP information
along with the email being sent. This would allow for pinpoint
identification of the senders of spam using IP addresses MAC addresses and
time stamped logs for the specific purposes of taking legal action against
these network abuses. I know it will be argued that this will require
cooperation between ISPs and that some systems are already implementing
these measures but if all administrators as a single body insist that
everyone adhere to these rules or be excluded from sending email to clients
of their services and enforced this through IP block and domain blocking the
stragglers would be forced to adhere to these rules. Further, if a body such
as the IETF stood behind this and perhaps drafted specifications for
administrators, and software developers to follow when making new
clients/servers and updating existing clients/servers it would hold added
weight in the market place. The extra cost associated with such actions
could be offset by saved resources, and additional revenues made as a result
of higher subscription rates justified by superior spam filtering techniques
and a greater number of subscribers to the service due to better service
quality. I would also like to suggest that the California law that requires
all unsolicited emails be appended with adv: in the subject line be expanded
to a federal law and additionally require emails that are solicited by
signing up for a service include exact information about who the sender
bought your email address from in the email.

These are just some ideas I have had on eliminating spam and should in no
way be considered a flame against anyone. I know there is no way that this
will stop all unsolicited email from being sent or received. I just thought
they might help to get some people rolling on a solution and that it would
be better than complaining about it. After all doesn't a global solution
make more sense than venting about what should be done to keep it out of
this mailing list.

Thank you for your time and attention,

Douglas Huyler
Dougxx2@carolina.rr.com
704-721-0212

P.S. I am sorry this email comes so long after the original post was made
but I don't read the list very often and after reading this thread from the
begining to December 6th I thought I would reply. If someone else has
brought these things up after this point I am sorry, but I haven't caught up
with the list yet.


----- Original Message -----
From: "Fred Baker" <fred@cisco.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: <ietf@ietf.org>; <namedroppers@ops.ietf.org>; <iesg@ietf.org>
Sent: Friday, December 06, 2002 4:41 PM
Subject: RE: namedroppers, continued


> At 08:28 AM 12/2/2002 -0800, Hallam-Baker, Phillip wrote:
> >The only way to resolve this issue properly would be to require every
> >submission to an IETF mailing list to be cryptographically signed (PGP
> >or S/MIME), to require the subscribers to register their signing key and
> >to then filter the mail sent out on the list so that only signed mail
> >gets through.
>
> I would be in favor of that, personally, as long as we can ensure that the
> appropriate signature facility (be it RSA, PGP, or whatever) is freely
> available to all who need to use it. The issue here is not us corporate
> types who have a business reason to buy the software, it is the students
> who often lack the funds. The big issue would be the procedures for
posting
> one's key to the appropriate place - what is to stop a spammer from
posting
> a key and sending the spam anyway? I'm not proposing a mechanism, but
> someone who is good at such things might well find it of value.
>
> It doesn't address the "off topic" issue. As you say, that could be left
to
> a working group chair equiped with formal procedures developed by
consensus
> within the work group or adopted by the working group from a more general
> place (ie, the IETF could suggest a procedure, and the WG could adopt it
if
> it didn't feel another procedure would be better).
>
> I have had a private exchange, over the past few days, with someone who
> wished that the IETF would please document some good spam-elimination
> procedure, so that it could be used world-wide to completely eliminate
> spam. I think that boils down to "provide a global PKI" in this solution,
> and presumes that spammers are incapable of using one. That might be a
> great research topic. Too bad nobody has ever thought of it before; we
> could really use the outcome of that research. (OK, so it's a lame attempt
> at humor...)
>
> I think it was Steve Bellovin that suggested a procedure for reducing the
> utility of spoofing source addresses in emails; if not, it was me and I
> happened to suggest something his favorite algorithm fit into, by having a
> host in each mail domain (mailid.example.com) be able to assert that its
> domain had or had not sent an email within a given recent  time period
> whose MD5 hash, when divided by <vector of prime numbers> resulted in
> <vector of remainders>. I could write that up in an internet draft if
folks
> think it makes sense. That would be a more global procedure that didn't
> require a PKI and only addressed spoofed addresses.
>




From owner-ietf@ietf.org  Sun Jan  5 22:06:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14263;
	Sun, 5 Jan 2003 22:06:17 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VNYi-0004sM-00
	for ietf-list@ran.ietf.org; Sun, 05 Jan 2003 22:04:12 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VNYQ-0004s5-00
	for ietf@ran.ietf.org; Sun, 05 Jan 2003 22:03:54 -0500
Received: from ncsmtp02.ogw.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14133;
	Sun, 5 Jan 2003 21:55:54 -0500 (EST)
Received: from mail4.carolina.rr.com (fe4 [24.93.67.51])
	by ncsmtp02.ogw.rr.com (8.12.5/8.12.2) with ESMTP id h062wFup003574;
	Sun, 5 Jan 2003 21:58:15 -0500 (EST)
Received: from dougpro ([24.88.167.199]) by mail4.carolina.rr.com  with Microsoft SMTPSVC(5.5.1877.757.75);
	 Sun, 5 Jan 2003 21:59:54 -0500
Message-ID: <004201c2b52f$9aab8ea0$0701a8c0@nailed.org>
From: "Doug" <Dougxx2@carolina.rr.com>
To: <ietf@ietf.org>
Cc: <namedroppers@ops.ietf.org>, <iesg@ietf.org>
Subject: Fw: namedroppers, continued  (flamed in less than an hour. figures)
Date: Sun, 5 Jan 2003 21:59:16 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I am wondering, is Daniel Senie normally rude to people she doesn't know or
is she just having a bad day? I sent a message out with some informal
suggestions in it that I thought might be helpful and she instantly jumps
down my throat with a nasty reply? It isn't like she or anyone can accuse me
of being a troll as I have only posted once or twice before. I am sorry I
didn't consult my english professor or a text for proper form before I sent
it (I really am), but I guess I thought it was an INFORMAL forum and I know
my email was intended as an informal thought process to be shared with the
group on an INFORMAL basis. Well anyway let me know what is going on with
this as I am confused now (I really don't understand the attitude). I have
included the entire text of her message below as well as my reply so
everyone might know what I am talking about.


Her message

----- Original Message -----
From: "Daniel Senie" <dts@senie.com>
To: "Doug" <Dougxx2@carolina.rr.com>
Sent: Sunday, January 05, 2003 7:45 PM
Subject: Re: namedroppers, continued


> Paragraph breaks MIGHT have made your email readable. Instead, I suspect
> many folks will just hit delete.
>

My reply to her

Well, I am sorry Mrs. Senie, that you feel the need to flame me for throwing
out a few informal ideas in an informal open forum. Next time I will be sure
to consult my old english professor on the proper format.

Jeesh Couldn't come up with one descent comment could ya?

What's next spelling errors and typos

Doug

----- Original Message -----
From: "Daniel Senie" <dts@senie.com>
To: "Doug" <Dougxx2@carolina.rr.com>
Sent: Sunday, January 05, 2003 7:45 PM
Subject: Re: namedroppers, continued


> Paragraph breaks MIGHT have made your email readable. Instead, I suspect
> many folks will just hit delete.
>




From owner-ietf@ietf.org  Sun Jan  5 22:50:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15003;
	Sun, 5 Jan 2003 22:50:01 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VOID-0005X5-00
	for ietf-list@ran.ietf.org; Sun, 05 Jan 2003 22:51:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VOI1-0005Wn-00
	for ietf@ran.ietf.org; Sun, 05 Jan 2003 22:51:01 -0500
Received: from cobalt.sopac.org.fj (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14926;
	Sun, 5 Jan 2003 22:42:49 -0500 (EST)
Received: by cobalt.sopac.org.fj (Postfix, from userid 416)
	id CA0B917C2D; Mon,  6 Jan 2003 03:45:55 +0000 (UTC)
Received: from bigiron.sopac.org.fj (unknown [10.0.0.180])
	by cobalt.sopac.org.fj (Postfix) with ESMTP
	id 0F8AA17C06; Mon,  6 Jan 2003 03:45:55 +0000 (UTC)
Received: by BIGIRON with Internet Mail Service (5.5.2650.21)
	id <W0Q5AMDW>; Mon, 6 Jan 2003 15:46:09 +1200
Message-ID: <F12ECEA0435AD211B5280008C7ACBC85016B46F7@BIGIRON>
From: Franck Martin <Franck@sopac.org>
To: "'Doug'" <Dougxx2@carolina.rr.com>, ietf@ietf.org
Cc: namedroppers@ops.ietf.org, iesg@ietf.org
Subject: RE: namedroppers, continued  (flamed in less than an hour. figure
	s)
Date: Mon, 6 Jan 2003 15:46:08 +1200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=2.7 required=5.0 tests=SUBJ_HAS_SPACES version=2.20
X-Spam-Level: **
Sender: owner-ietf@ietf.org
Precedence: bulk

Some people on the IETF as being technos lack people skills, that's why they
work with computers...

Do not worry about that... Each time I post a suggestion/comment I get
always a bunch of answer like: "This is real stupid" without explaining me
why...

If your ego can pass that, you will be admitted to the IETF confrerie and be
able to do the same to newbies...

Cheers.

Franck Martin

> -----Original Message-----
> From: Doug [mailto:Dougxx2@carolina.rr.com]
> Sent: Monday, 6 January 2003 2:59 
> To: ietf@ietf.org
> Cc: namedroppers@ops.ietf.org; iesg@ietf.org
> Subject: Fw: namedroppers, continued (flamed in less than an hour.
> figures)
> 
> 
> I am wondering, is Daniel Senie normally rude to people she 
> doesn't know or
> is she just having a bad day? I sent a message out with some informal
> suggestions in it that I thought might be helpful and she 
> instantly jumps
> down my throat with a nasty reply? It isn't like she or 
> anyone can accuse me
> of being a troll as I have only posted once or twice before. 
> I am sorry I
> didn't consult my english professor or a text for proper form 
> before I sent
> it (I really am), but I guess I thought it was an INFORMAL 
> forum and I know
> my email was intended as an informal thought process to be 
> shared with the
> group on an INFORMAL basis. Well anyway let me know what is 
> going on with
> this as I am confused now (I really don't understand the 
> attitude). I have
> included the entire text of her message below as well as my reply so
> everyone might know what I am talking about.
> 
> 
> Her message
> 
> ----- Original Message -----
> From: "Daniel Senie" <dts@senie.com>
> To: "Doug" <Dougxx2@carolina.rr.com>
> Sent: Sunday, January 05, 2003 7:45 PM
> Subject: Re: namedroppers, continued
> 
> 
> > Paragraph breaks MIGHT have made your email readable. 
> Instead, I suspect
> > many folks will just hit delete.
> >
> 
> My reply to her
> 
> Well, I am sorry Mrs. Senie, that you feel the need to flame 
> me for throwing
> out a few informal ideas in an informal open forum. Next time 
> I will be sure
> to consult my old english professor on the proper format.
> 
> Jeesh Couldn't come up with one descent comment could ya?
> 
> What's next spelling errors and typos
> 
> Doug
> 
> ----- Original Message -----
> From: "Daniel Senie" <dts@senie.com>
> To: "Doug" <Dougxx2@carolina.rr.com>
> Sent: Sunday, January 05, 2003 7:45 PM
> Subject: Re: namedroppers, continued
> 
> 
> > Paragraph breaks MIGHT have made your email readable. 
> Instead, I suspect
> > many folks will just hit delete.
> >
> 
> 



From owner-ietf@ietf.org  Sun Jan  5 23:15:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15315;
	Sun, 5 Jan 2003 23:15:01 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VOgO-00060Y-00
	for ietf-list@ran.ietf.org; Sun, 05 Jan 2003 23:16:12 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VOfy-00060F-00
	for ietf@ran.ietf.org; Sun, 05 Jan 2003 23:15:46 -0500
Received: from sj-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15217
	for <ietf@ietf.org>; Sun, 5 Jan 2003 23:07:45 -0500 (EST)
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h064AwFp025463;
	Sun, 5 Jan 2003 20:10:58 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ABU72911;
	Sun, 5 Jan 2003 20:10:57 -0800 (PST)
Message-Id: <200301060410.ABU72911@mira-sjc5-c.cisco.com>
To: "Doug" <Dougxx2@carolina.rr.com>
cc: ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: Fw: namedroppers, continued (flamed in less than an hour. figures) 
In-Reply-To: Message from Dougxx2@carolina.rr.com
   of "Sun, 05 Jan 2003 21:59:16 EST." <004201c2b52f$9aab8ea0$0701a8c0@nailed.org> 
Date: Sun, 05 Jan 2003 23:10:56 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

I'm not sure which is more impressive - that you chose to
forward private email to several mailing lists, or that you
chose to insult someone by referring to him as a woman.  

Melinda



From owner-ietf@ietf.org  Sun Jan  5 23:38:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15641;
	Sun, 5 Jan 2003 23:38:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VP3p-0006YD-00
	for ietf-list@ran.ietf.org; Sun, 05 Jan 2003 23:40:25 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VP3O-0006XK-00
	for ietf@ran.ietf.org; Sun, 05 Jan 2003 23:39:59 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15560
	for <ietf@ietf.org>; Sun, 5 Jan 2003 23:31:56 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h064Yt33029839;
	Sun, 5 Jan 2003 23:34:56 -0500
Message-Id: <200301060434.h064Yt33029839@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Melinda Shore <mshore@cisco.com>
Cc: Doug <Dougxx2@carolina.rr.com>, ietf@ietf.org
Subject: Re: Fw: namedroppers, continued (flamed in less than an hour. figures) 
In-Reply-To: Your message of "Sun, 05 Jan 2003 23:10:56 EST."
             <200301060410.ABU72911@mira-sjc5-c.cisco.com> 
References: <200301060410.ABU72911@mira-sjc5-c.cisco.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1529868119P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sun, 05 Jan 2003 23:34:55 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sun, 05 Jan 2003 23:10:56 EST, Melinda Shore said:
> I'm not sure which is more impressive - that you chose to
> forward private email to several mailing lists, or that you
> chose to insult someone by referring to him as a woman.  

Could be worse.  We've had no complaints from any of the robotic or
space-alien intelligences about the human-centric language used on this list,
even in the face of evidence that there are multiple representatives
of each of those categories lurking (and sometimes even posting)....

In addition, I can think of a number of lunatic-fringe feminists who would
start frothing at the mouth for the undeserved compliment implicit in the
gender error....

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

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

iD8DBQE+GQducC3lWbTT17ARApOtAKDVdm40TOAL0LLjvJPLJkbvTRM7kQCg2o0P
nlwgp0PlN0DQEQ0gDThtf68=
=vGDk
-----END PGP SIGNATURE-----

--==_Exmh_1529868119P--



From owner-ietf@ietf.org  Sun Jan  5 23:38:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15640;
	Sun, 5 Jan 2003 23:38:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VP3p-0006YJ-00
	for ietf-list@ran.ietf.org; Sun, 05 Jan 2003 23:40:25 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VP3S-0006XP-00
	for ietf@ran.ietf.org; Sun, 05 Jan 2003 23:40:02 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15564;
	Sun, 5 Jan 2003 23:31:59 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h064Z333029854;
	Sun, 5 Jan 2003 23:35:03 -0500
Message-Id: <200301060435.h064Z333029854@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Franck Martin <Franck@sopac.org>
Cc: "'Doug'" <Dougxx2@carolina.rr.com>, ietf@ietf.org,
        namedroppers@ops.ietf.org, iesg@ietf.org
Subject: Re: namedroppers, continued (flamed in less than an hour. figure s) 
In-Reply-To: Your message of "Mon, 06 Jan 2003 15:46:08 +1200."
             <F12ECEA0435AD211B5280008C7ACBC85016B46F7@BIGIRON> 
References: <F12ECEA0435AD211B5280008C7ACBC85016B46F7@BIGIRON>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1529921543P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sun, 05 Jan 2003 23:35:03 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 06 Jan 2003 15:46:08 +1200, Franck Martin said:
> Some people on the IETF as being technos lack people skills, that's why they
> work with computers...

I usually explain it as "We're talking here about a collection of people who
are paid vast sums of money for their ability to carry on productive
conversations with inanimate objects".

It's usually easy to see the need for the cutting of slack at that point. ;)

> If your ego can pass that, you will be admitted to the IETF confrerie and be
> able to do the same to newbies...

Can anybody provide the original citation for the statement (similar to):

"The flame you are complaining about did not cast any aspersion on your
parentage or dietary preferences, and as such was mild by IETF standards"?
-- 
				Valdis Kletnieks
				Computer Systems Senior Engineer
				Virginia Tech


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

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

iD8DBQE+GQd3cC3lWbTT17ARAmrqAJwJg0SfV2TxG1nxHrKy9MFNBa1XgQCfdSQ/
D9lWVTmMZd3QF6Oo3WgvBoU=
=bPIn
-----END PGP SIGNATURE-----

--==_Exmh_1529921543P--



From owner-ietf@ietf.org  Sun Jan  5 23:57:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16050;
	Sun, 5 Jan 2003 23:57:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VPN1-0007Rv-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 00:00:15 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VPMo-0007RK-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 00:00:02 -0500
Received: from cobalt.sopac.org.fj (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15991
	for <ietf@ietf.org>; Sun, 5 Jan 2003 23:51:53 -0500 (EST)
Received: by cobalt.sopac.org.fj (Postfix, from userid 416)
	id 085BD17C2E; Mon,  6 Jan 2003 04:55:04 +0000 (UTC)
Received: from bigiron.sopac.org.fj (unknown [10.0.0.180])
	by cobalt.sopac.org.fj (Postfix) with ESMTP
	id 7F90117C01; Mon,  6 Jan 2003 04:55:03 +0000 (UTC)
Received: by BIGIRON with Internet Mail Service (5.5.2650.21)
	id <W0Q5AMHR>; Mon, 6 Jan 2003 16:55:18 +1200
Message-ID: <F12ECEA0435AD211B5280008C7ACBC85016B46FE@BIGIRON>
From: Franck Martin <Franck@sopac.org>
To: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
        Melinda Shore <mshore@cisco.com>
Cc: Doug <Dougxx2@carolina.rr.com>, ietf@ietf.org
Subject: RE: Fw: namedroppers, continued (flamed in less than an hour. fig
	ures) 
Date: Mon, 6 Jan 2003 16:55:17 +1200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
MIME-Version: 1.0
Content-Type: multipart/signed;
	protocol="application/x-pkcs7-signature";
	micalg=SHA1;
	boundary="----=_NextPart_000_00B9_01C2B5A4.64420EF0"
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Spam-Status: No, hits=2.7 required=5.0 tests=SUBJ_HAS_SPACES version=2.20
X-Spam-Level: **
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00B9_01C2B5A4.64420EF0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
> Sent: Monday, 6 January 2003 4:35 
> To: Melinda Shore
> Cc: Doug; ietf@ietf.org
> Subject: Re: Fw: namedroppers, continued (flamed in less than an hour.
> figures) 
> 
> 
> On Sun, 05 Jan 2003 23:10:56 EST, Melinda Shore said:
> > I'm not sure which is more impressive - that you chose to
> > forward private email to several mailing lists, or that you
> > chose to insult someone by referring to him as a woman.  
> 
> Could be worse.  We've had no complaints from any of the robotic or
> space-alien intelligences about the human-centric language 
> used on this list,
> even in the face of evidence that there are multiple representatives
> of each of those categories lurking (and sometimes even posting)....

In which category would you fit Jim Fleming ?

------=_NextPart_000_00B9_01C2B5A4.64420EF0
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Disposition: attachment;
	filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKVzCCBSQw
ggSNoAMCAQICAQIwDQYJKoZIhvcNAQEFBQAwgYkxCzAJBgNVBAYTAkZKMQ0wCwYDVQQIEwRGaWpp
MQ0wCwYDVQQHEwRTdXZhMQ4wDAYDVQQKEwVTT1BBQzEMMAoGA1UECxMDSVRVMRYwFAYDVQQDEw1T
T1BBQyBSb290IENBMSYwJAYJKoZIhvcNAQkBFhdhZG1pbmlzdHJhdG9yQHNvcGFjLm9yZzAeFw0w
MjA1MDkyMjEwMDZaFw0wMzA1MDkyMjEwMDZaMIGFMQswCQYDVQQGEwJGSjENMAsGA1UECBMERmlq
aTENMAsGA1UEBxMEU3V2YTEOMAwGA1UEChMFU09QQUMxDDAKBgNVBAsTA0lUVTEZMBcGA1UEAxQQ
ZnJhbmNrQHNvcGFjLm9yZzEfMB0GCSqGSIb3DQEJARYQZnJhbmNrQHNvcGFjLm9yZzCBnzANBgkq
hkiG9w0BAQEFAAOBjQAwgYkCgYEA0soRghfaBJ3B6+yxHxEkHbtCF4a/ZNNUs9Sn38pBwXT0D/R6
iqhC+CCxjO/7mCe4F6pRZMTuN0Rv84ZMa77aNDBcVWiSsssoUS+64yxTefwnq3+gifNO7mVxE8yr
a/LvvwKIGmr0R0Hz8kTidyUzcoQROFHfD27FJpjEsVFtOmcCAwEAAaOCApwwggKYMAkGA1UdEwQC
MAAwPwYJYIZIAYb4QgENBDIWMENlcnRpZmljYXRlIGlzc3VlZCBieSBodHRwczovL3d3dy5zb3Bh
Yy5vcmcvc3NsLzAdBgNVHQ4EFgQUukKEVhwnVd3F4n9WW26fA4c6wBEwgbYGA1UdIwSBrjCBq4AU
OqATltJqhrl/LVS+UDvT8aTsUa+hgY+kgYwwgYkxCzAJBgNVBAYTAkZKMQ0wCwYDVQQIEwRGaWpp
MQ0wCwYDVQQHEwRTdXZhMQ4wDAYDVQQKEwVTT1BBQzEMMAoGA1UECxMDSVRVMRYwFAYDVQQDEw1T
T1BBQyBSb290IENBMSYwJAYJKoZIhvcNAQkBFhdhZG1pbmlzdHJhdG9yQHNvcGFjLm9yZ4IBADAp
BglghkgBhvhCAQIEHBYaaHR0cHM6Ly93d3cuc29wYWMub3JnL3NzbC8wNQYJYIZIAYb4QgEEBCgW
Jmh0dHBzOi8vd3d3LnNvcGFjLm9yZy9zc2wvc29wYWMtY2EuY3JsMDkGCWCGSAGG+EIBAwQsFipo
dHRwczovL3d3dy5zb3BhYy5vcmcvc3NsL3Jldm9jYXRpb24uaHRtbD8wNgYJYIZIAYb4QgEHBCkW
J2h0dHBzOi8vd3d3LnNvcGFjLm9yZy9zc2wvcmVuZXdhbC5odG1sPzA0BglghkgBhvhCAQgEJxYl
aHR0cHM6Ly93d3cuc29wYWMub3JnL3NzbC9wb2xpY3kuaHRtbDAuBgNVHRIEJzAlhiNodHRwczov
L3d3dy5zb3BhYy5vcmcvc3NsL3NvcGFjLmNydDA3BgNVHR8EMDAuMCygKqAohiZodHRwczovL3d3
dy5zb3BhYy5vcmcvc3NsL3NvcGFjLWNhLmNybDANBgkqhkiG9w0BAQUFAAOBgQB+4WRRdMulWDp2
MNawJy9mksHVGL2l5BN6eBOcRcoi1cLgOvISZwoAp7C/vE/37lQRqbHcHATn4FU+bGjuxMu/YBYH
ax5TYWV9G3/Gc0HA4UhPuvDLS1Z7woFsI5Ra2mJGyJgE8IWxt2HfRjR5fBEY/+PHVumXaRyxi6Fj
em+AaTCCBSswggSUoAMCAQICAQAwDQYJKoZIhvcNAQEFBQAwgYkxCzAJBgNVBAYTAkZKMQ0wCwYD
VQQIEwRGaWppMQ0wCwYDVQQHEwRTdXZhMQ4wDAYDVQQKEwVTT1BBQzEMMAoGA1UECxMDSVRVMRYw
FAYDVQQDEw1TT1BBQyBSb290IENBMSYwJAYJKoZIhvcNAQkBFhdhZG1pbmlzdHJhdG9yQHNvcGFj
Lm9yZzAeFw0wMjA1MDkwNDUxMDlaFw0xMjA1MDYwNDUxMDlaMIGJMQswCQYDVQQGEwJGSjENMAsG
A1UECBMERmlqaTENMAsGA1UEBxMEU3V2YTEOMAwGA1UEChMFU09QQUMxDDAKBgNVBAsTA0lUVTEW
MBQGA1UEAxMNU09QQUMgUm9vdCBDQTEmMCQGCSqGSIb3DQEJARYXYWRtaW5pc3RyYXRvckBzb3Bh
Yy5vcmcwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJ/G829ctvoXf2qH0/THNKgdgTHjqOoJ
8M6B4jDu/t5kv3EQFXz65b8bAt3DnWtL29gSgmZ2Og4f5J1GjmqFRlzH8BJFGArWi6MmLuLmSvl3
ltM211jm66wxU+ePB2v4lledogiLRkIlAlZzzpLrdm6SlWPoxrZUE4juSKucSK/dAgMBAAGjggKf
MIICmzAdBgNVHQ4EFgQUOqATltJqhrl/LVS+UDvT8aTsUa8wgbYGA1UdIwSBrjCBq4AUOqATltJq
hrl/LVS+UDvT8aTsUa+hgY+kgYwwgYkxCzAJBgNVBAYTAkZKMQ0wCwYDVQQIEwRGaWppMQ0wCwYD
VQQHEwRTdXZhMQ4wDAYDVQQKEwVTT1BBQzEMMAoGA1UECxMDSVRVMRYwFAYDVQQDEw1TT1BBQyBS
b290IENBMSYwJAYJKoZIhvcNAQkBFhdhZG1pbmlzdHJhdG9yQHNvcGFjLm9yZ4IBADAMBgNVHRME
BTADAQH/MD8GCWCGSAGG+EIBDQQyFjBDZXJ0aWZpY2F0ZSBpc3N1ZWQgYnkgaHR0cHM6Ly93d3cu
c29wYWMub3JnL3NzbC8wKQYJYIZIAYb4QgECBBwWGmh0dHBzOi8vd3d3LnNvcGFjLm9yZy9zc2wv
MDUGCWCGSAGG+EIBBAQoFiZodHRwczovL3d3dy5zb3BhYy5vcmcvc3NsL3NvcGFjLWNhLmNybDA5
BglghkgBhvhCAQMELBYqaHR0cHM6Ly93d3cuc29wYWMub3JnL3NzbC9yZXZvY2F0aW9uLmh0bWw/
MDYGCWCGSAGG+EIBBwQpFidodHRwczovL3d3dy5zb3BhYy5vcmcvc3NsL3JlbmV3YWwuaHRtbD8w
NAYJYIZIAYb4QgEIBCcWJWh0dHBzOi8vd3d3LnNvcGFjLm9yZy9zc2wvcG9saWN5Lmh0bWwwLgYD
VR0SBCcwJYYjaHR0cHM6Ly93d3cuc29wYWMub3JnL3NzbC9zb3BhYy5jcnQwNwYDVR0fBDAwLjAs
oCqgKIYmaHR0cHM6Ly93d3cuc29wYWMub3JnL3NzbC9zb3BhYy1jYS5jcmwwDQYJKoZIhvcNAQEF
BQADgYEAVgR9VJL3PAR6ljg8PVSyGIJ+t+yvhtU6q6cEuONs1EILhhLae4XmajjVeXud9t/U+jNm
4IZi3XqWymeLV1oj/exU7Lcnog5CeA9QirpH+xlzHd2ByMW1RvbSmhgsbv8nQ7Y21Foxdx3lkAfi
V2ya75RUFFATHjfddz5R2osj7yAxggKUMIICkAIBATCBjzCBiTELMAkGA1UEBhMCRkoxDTALBgNV
BAgTBEZpamkxDTALBgNVBAcTBFN1dmExDjAMBgNVBAoTBVNPUEFDMQwwCgYDVQQLEwNJVFUxFjAU
BgNVBAMTDVNPUEFDIFJvb3QgQ0ExJjAkBgkqhkiG9w0BCQEWF2FkbWluaXN0cmF0b3JAc29wYWMu
b3JnAgECMAkGBSsOAwIaBQCgggFaMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTAzMDEwNjA0NTUxOFowIwYJKoZIhvcNAQkEMRYEFC6CrwzL/dSoeLsEeo9m8p+5qHeL
MFgGCSqGSIb3DQEJDzFLMEkwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIHMA0G
CCqGSIb3DQMCAgEoMAcGBSsOAwIaMAoGCCqGSIb3DQIFMIGgBgkrBgEEAYI3EAQxgZIwgY8wgYkx
CzAJBgNVBAYTAkZKMQ0wCwYDVQQIEwRGaWppMQ0wCwYDVQQHEwRTdXZhMQ4wDAYDVQQKEwVTT1BB
QzEMMAoGA1UECxMDSVRVMRYwFAYDVQQDEw1TT1BBQyBSb290IENBMSYwJAYJKoZIhvcNAQkBFhdh
ZG1pbmlzdHJhdG9yQHNvcGFjLm9yZwIBAjANBgkqhkiG9w0BAQEFAASBgLlnG/pplmLrPCNw0x6g
/OHZpd6YKdsWJwhoSFVjxvL/Il5BkFP2PWal94xiycEAF1krqSylgJ/2ETQp6PJP5+ChGz7iKgiO
4u/k/3JEXxE7wwATyJ87ke9exvqXD5DL+RLIBmoaeVH0U4SUcKkYtvAogyjDIZA2FuSgbHUNzFPX
AAAAAAAA

------=_NextPart_000_00B9_01C2B5A4.64420EF0--




From owner-ietf@ietf.org  Sun Jan  5 23:59:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16132;
	Sun, 5 Jan 2003 23:59:09 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VPP0-0007UJ-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 00:02:18 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VPNh-0007S2-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 00:00:57 -0500
Received: from cobalt.sopac.org.fj (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16018
	for <ietf@ietf.org>; Sun, 5 Jan 2003 23:52:54 -0500 (EST)
Received: by cobalt.sopac.org.fj (Postfix, from userid 416)
	id D720A17C2B; Mon,  6 Jan 2003 04:56:06 +0000 (UTC)
Received: from bigiron.sopac.org.fj (unknown [10.0.0.180])
	by cobalt.sopac.org.fj (Postfix) with ESMTP
	id 6298417C01; Mon,  6 Jan 2003 04:56:06 +0000 (UTC)
Received: by BIGIRON with Internet Mail Service (5.5.2650.21)
	id <W0Q5AMHT>; Mon, 6 Jan 2003 16:56:21 +1200
Message-ID: <F12ECEA0435AD211B5280008C7ACBC85016B46FF@BIGIRON>
From: Franck Martin <Franck@sopac.org>
To: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
        Melinda Shore <mshore@cisco.com>
Cc: Doug <Dougxx2@carolina.rr.com>, ietf@ietf.org
Subject: RE: Fw: namedroppers, continued (flamed in less than an hour. fig
	ures) 
Date: Mon, 6 Jan 2003 16:56:20 +1200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Spam-Status: No, hits=2.7 required=5.0 tests=SUBJ_HAS_SPACES version=2.20
X-Spam-Level: **
Sender: owner-ietf@ietf.org
Precedence: bulk

> -----Original Message-----
> From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
> Sent: Monday, 6 January 2003 4:35 
> To: Melinda Shore
> Cc: Doug; ietf@ietf.org
> Subject: Re: Fw: namedroppers, continued (flamed in less than an hour.
> figures) 
> 
> 
> On Sun, 05 Jan 2003 23:10:56 EST, Melinda Shore said:
> > I'm not sure which is more impressive - that you chose to
> > forward private email to several mailing lists, or that you
> > chose to insult someone by referring to him as a woman.  
> 
> Could be worse.  We've had no complaints from any of the robotic or
> space-alien intelligences about the human-centric language 
> used on this list,
> even in the face of evidence that there are multiple representatives
> of each of those categories lurking (and sometimes even posting)....

In which category would you fit Jim Fleming?



From owner-ietf@ietf.org  Mon Jan  6 01:04:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16955;
	Mon, 6 Jan 2003 01:04:56 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VQNu-0000gN-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 01:05:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VQN2-0000fY-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 01:04:20 -0500
Received: from ncsmtp03.ogw.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16839;
	Mon, 6 Jan 2003 00:56:17 -0500 (EST)
Received: from mail5.carolina.rr.com (fe5 [24.93.67.52])
	by ncsmtp03.ogw.rr.com (8.12.5/8.12.2) with ESMTP id h065wliZ014374;
	Mon, 6 Jan 2003 00:58:47 -0500 (EST)
Received: from dougpro ([24.88.167.199]) by mail5.carolina.rr.com  with Microsoft SMTPSVC(5.5.1877.757.75);
	 Mon, 6 Jan 2003 00:58:07 -0500
Message-ID: <001701c2b548$ce05baf0$0701a8c0@nailed.org>
From: "Doug" <Dougxx2@carolina.rr.com>
To: "grenville armitage" <garmitage@swin.edu.au>
Cc: <ietf@ietf.org>, <namedroppers@ops.ietf.org>, <iesg@ietf.org>,
        "Daniel Senie" <dts@senie.com>
References: <004201c2b52f$9aab8ea0$0701a8c0@nailed.org> <3E18F6DD.69EE90B8@swin.edu.au>
Subject: Re: Fw: namedroppers, continued  (flamed in less than an hour. figures)
Date: Mon, 6 Jan 2003 00:59:41 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Grenvill Armitage,

That is not the point and you know it. It is all about the nonsense
attitude.
Just ask yourself if it was all about making a polite suggestion then tell
me
why the word "might" was capitalized. Try reading what she wrote and
putting emphasis on that word. Oh yeah I am going to continue to repost
the nonsense as long as they are rude enough to keep sending it. The
purpose of it is so that everyone knows how they are treating people and
so that the other people that are being harassed by this incredibly rude
person know that it is not just them and that this person is an incredible
TROLL. What you are refering to as netiquette is an unspoken rule of
USENET not a mailing list as far as I know, so I don't believe it applies
here.
In addition, I would like to add I thought this was a forum for
professionals
not kids. Before you start claiming that this person is not being a TROLL
check out what the next response was. It isn't very professional or
condusive
to getting anything done in my opinion. Of course maybe the IETF isn't
interested in getting anything done or talking about any real ideas. What do
you think? I think that anyone that makes replies to messages in a public
forum
like THIS one which (unlike what usenet has turned into) is supposed to be
about solving problems and getting things done, needs to be revealed to the
group as a TROLL and a CHILD. I will personally be filtering the rest of the
email from her since I don't have the time nor the desire to deal with the
stupidity
and I know there are plenty of other people here with things to say that are
worth hearing. Hopefully you won't be the next person to go in my filter
Grenville
since I actually believe you were trying to do something here even if it was
misguided. Bye bye Daniel. Oh, don't bother replying to my message with the
obligatory "well fine I will ignore you to" because I won't see it.

P.S. If you doubt the my claim that it was the entire message either time I
can
always post them as file attachments for the whole group to see.

Done with this nonsense now,
Doug
Dougxx2@carolina.rr.com
704-721-0212

what follows is the childish reply I got from Daniel Senie
------------------------------------
At 09:40 PM 1/5/2003

>>Well, I am sorry Mrs. Senie,
>
>Mrs.? heh.
>
>>  that you feel the need to flame me for throwing
>>out a few informal ideas in an informal open forum. Next time I will be
sure
>>to consult my old english professor on the proper format.
>>
>>Jeesh Couldn't come up with one descent comment could ya?
>>
>You perhaps mean "decent"? The word you used refers to decreasing altitude.
>>
>>
>>What's next spelling errors and typos
>>
>Absolutely. Should you wish to communicate your ideas to others, it'd
>REALLY help if you learned to communicate effectively.
-------------------------------------------------
end of childish rant from Daniel Senie

Oh and for your information Daniel I think anyone with a reading level over
fourth grade could understand what I said and I think everyone that did
bother to read it knows it.



----- Original Message -----
From: "grenville armitage" <garmitage@swin.edu.au>
To: "Doug" <Dougxx2@carolina.rr.com>
Sent: Sunday, January 05, 2003 10:24 PM
Subject: Re: Fw: namedroppers, continued (flamed in less than an hour.
figures)


>
> Doug wrote:
> >
> > I am wondering, is Daniel Senie normally rude to people she doesn't know
or
> > is she just having a bad day?
>
> My reading of what you claim is the entirety of Senie's email to you
> is that you received a perfectly valid and succint suggestion. You seem
> to be overreacting, and committing a greater netiquette sin of re-posting
> someone's private email to you.
>
> What exactly are you upset about?
>
> cheers,
> gja
> --
> Grenville Armitage
> http://caia.swin.edu.au




From owner-ietf@ietf.org  Mon Jan  6 01:25:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17324;
	Mon, 6 Jan 2003 01:25:43 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VQl8-0001Ig-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 01:29:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VQkg-0001Ho-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 01:28:46 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17189
	for <ietf@ietf.org>; Mon, 6 Jan 2003 01:20:42 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h066Nn33030511;
	Mon, 6 Jan 2003 01:23:49 -0500
Message-Id: <200301060623.h066Nn33030511@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Doug <Dougxx2@carolina.rr.com>
Cc: ietf@ietf.org
Subject: Re: namedroppers, continued 
In-Reply-To: Your message of "Sun, 05 Jan 2003 19:04:41 EST."
             <02fc01c2b517$36d4dbb0$0701a8c0@nailed.org> 
References: <5.2.0.9.2.20021206132845.01b56f88@mira-sjcm-4.cisco.com>
            <02fc01c2b517$36d4dbb0$0701a8c0@nailed.org>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1898191268P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 06 Jan 2003 01:23:48 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sun, 05 Jan 2003 19:04:41 EST, Doug said:

> It seems to me if the mail server administrators would make the decision to
> require people that send emails from their servers to log into a valid

Your proposal would fix the problem, but end up tossing a large quantity
of babies out with the bathwater.  The problem is that for the case of
a mailing list, you have *4* (at least) things to keep track of:

1) The RFC821 recipient address.  For your copy of this posting, it's "your
email address".

2) The RFC821 sender address.  It should be available in the Return-Path:
header in most well-behaved mail systems as you look at your mail.

3) The RFC822 From: address.

4) The RFC822 To: address.

Another problem is that I am (fortunately) still receiving more mail
each day that counts as "legitimate unsolicited" (problem reports about
our servers, people who have seen my name and are looking for technical
advice, etc) than I do actual spam.

It's not as easy as it looks... :)

/Valdis

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

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

iD8DBQE+GSD0cC3lWbTT17ARAu+QAJ0YQeGZ6Sy7adUzmZypl8yDLzJTAgCg1vW8
3bN+7xNmh+g9/ldgDlhHYP8=
=X0qD
-----END PGP SIGNATURE-----

--==_Exmh_-1898191268P--



From owner-ietf@ietf.org  Mon Jan  6 01:26:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17382;
	Mon, 6 Jan 2003 01:26:40 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VQn5-0001LF-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 01:31:15 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VQn1-0001Jh-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 01:31:11 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17274
	for <ietf@ietf.org>; Mon, 6 Jan 2003 01:23:07 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h066QF33030527;
	Mon, 6 Jan 2003 01:26:15 -0500
Message-Id: <200301060626.h066QF33030527@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Franck Martin <Franck@sopac.org>
Cc: ietf@ietf.org
Subject: Re: Fw: namedroppers, continued (flamed in less than an hour. fig ures) 
In-Reply-To: Your message of "Mon, 06 Jan 2003 16:56:20 +1200."
             <F12ECEA0435AD211B5280008C7ACBC85016B46FF@BIGIRON> 
References: <F12ECEA0435AD211B5280008C7ACBC85016B46FF@BIGIRON>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1897894097P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 06 Jan 2003 01:26:15 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 06 Jan 2003 16:56:20 +1200, Franck Martin said:
> > -----Original Message-----
> > From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
> > Could be worse.  We've had no complaints from any of the robotic or
> > space-alien intelligences about the human-centric language 
> > used on this list,
> > even in the face of evidence that there are multiple representatives
> > of each of those categories lurking (and sometimes even posting)....
> 
> In which category would you fit Jim Fleming?

I have an opinion on that.  Jim probably does as well.  But remember these
three things:

1) The IETF is based on consensus.

2) William Gibson defined cyberspace as a consensual hallucination.

3) There is no spoon. ;)

I never said I exhaustively enumerated the options - I've seen more than one
delivered product that was obviously designed by a committee of cetaceans, as
the product worked, but the design choices were just... bizarre.  To the extent
that I couldn't fathom the thought processes involved.  So either the designer
was a dolphin or I am.  I'm pretty sure I'm not, but see point 3 above. ;)

And c'mon.. let's admit it - most dot-bombs had fatally flawed business
models, which were usually the result of some Upper Management Suit failing
to realize that chimpanzees are usually joking(*).

(And yes, I know I've dissembled rather than answer the actual question. That
was intentional...)

/Valdis

(*) Of course, humans suffer from this as well.  If you ever manage to catch
me as liveware, get me to tell the story behind "Geez Randy, now we need to
take you out back and beat the snot out of you *twice*" "But Val, I didn't think
they were taking me seriously this time either..."  ;)


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

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

iD8DBQE+GSGHcC3lWbTT17ARAt3RAJsH7/Xj1lafCvJHfnLJZBwNfrkoXACcDHvp
9+GD3xKOP7lL6EMCm+9hLzA=
=EjRQ
-----END PGP SIGNATURE-----

--==_Exmh_-1897894097P--



From owner-ietf@ietf.org  Mon Jan  6 02:05:28 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22023;
	Mon, 6 Jan 2003 02:05:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VRKy-0002jI-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 02:06:16 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VRKl-0002iG-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 02:06:03 -0500
Received: from ncsmtp02.ogw.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17854
	for <ietf@ietf.org>; Mon, 6 Jan 2003 01:58:01 -0500 (EST)
Received: from mail6.carolina.rr.com (fe6 [24.93.67.53])
	by ncsmtp02.ogw.rr.com (8.12.5/8.12.2) with ESMTP id h0670Oup019497;
	Mon, 6 Jan 2003 02:00:24 -0500 (EST)
Received: from dougpro ([24.88.167.199]) by mail6.carolina.rr.com  with Microsoft SMTPSVC(5.5.1877.757.75);
	 Mon, 6 Jan 2003 02:01:31 -0500
Message-ID: <0a0501c2b551$6ea12c30$0701a8c0@nailed.org>
From: "Doug" <Dougxx2@carolina.rr.com>
To: <Valdis.Kletnieks@vt.edu>
Cc: <ietf@ietf.org>
References: <5.2.0.9.2.20021206132845.01b56f88@mira-sjcm-4.cisco.com>            <02fc01c2b517$36d4dbb0$0701a8c0@nailed.org> <200301060623.h066Nn33030511@turing-police.cc.vt.edu>
Subject: Re: namedroppers, continued 
Date: Mon, 6 Jan 2003 02:01:27 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: <Valdis.Kletnieks@vt.edu>
To: "Doug" <Dougxx2@carolina.rr.com>
Cc: <ietf@ietf.org>
Sent: Monday, January 06, 2003 1:23 AM
Subject: Re: namedroppers, continued


>> It seems to me if the mail server administrators would make the decision
to
>> require people that send emails from their servers to log into a valid
>
>Your proposal would fix the problem, but end up tossing a large quantity
>of babies out with the bathwater.  The problem is that for the case of
>a mailing list, you have *4* (at least) things to keep track of:

There are many comercial email servers that require the people sending email
with their server to log into the server using a valid username and pass
before
doing so. I doubt they are losing any valid emails. All it does is to keep
unauthorized users from using the server without a valid password. The
reason
to require that the sender address in the outgoing email matches the email
address refrenced in the account is to keep people from sending spam from
these email servers and using fraudulant return and/or sender address.
I fail to see how this throws out any babies. perhaps I am missing
something.

>
>1) The RFC821 recipient address.  For your copy of this posting, it's "your
>email address".

>2) The RFC821 sender address.  It should be available in the Return-Path:
>header in most well-behaved mail systems as you look at your mail.

>3) The RFC822 From: address.

>4) The RFC822 To: address.

I know what the recipient address, sender address, from address, and to
address in headers look like. The problem is that many spammers use false
information here and change it on a regular basis. This makes it impossible
to block their email at the client end. My proposal is very basically to
make
it mandatory to put valid information in these fields in order to be able to
send the email.

>Another problem is that I am (fortunately) still receiving more mail
>each day that counts as "legitimate unsolicited" (problem reports about
>our servers, people who have seen my name and are looking for technical
>advice, etc) than I do actual spam.

I also never intended for servers to be using filters on unsolicited emails
just
because they are unsolicited. My intention was to suggest that people who
were sending unwanted and unsolicited "comercial" email should be blocked.
I suggested that servers that refused to cooperate with the rest of the spam
hating world could be blocked just in case but, this may be a bit harsh.
In addition the steps I mentioned would allow for the person receiving these
emails to gather information to allow them to easily take legal action
against the
spammers that still managed to get through. IE if everyone is forced to use
valid
information in the headers to be able to send the email without using some
exploit on the server then it should be easy to track them down. If of
course
they are forced to use exploits to send their anon spam then the admins of
the
system would eventually find this and take action to block them and/or
prosecute them. Perhaps you could be scanning header information as well on
the receiving server (not the client or the sending server) to allow you to
check
for nonsense return addresses like this@for.example or fraudulant source DNS
and IP information. Another thing that could be checked for is wether the
sending account matches the reply to address.

>It's not as easy as it looks... :)

Oh no I never said it was easy and I also never said I knew it all. I am
just
making a suggestion as to a possible solution to the problem.

:)
Doug

>/Valdis

P.S. I do seriously want to know how this would stop valid email users from
getting/sending their email.





From owner-ietf@ietf.org  Mon Jan  6 02:15:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27890;
	Mon, 6 Jan 2003 02:15:01 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VRXf-0003GZ-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 02:19:23 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VRTy-0003EV-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 02:15:34 -0500
Received: from net.cc.swin.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23532
	for <ietf@ietf.org>; Mon, 6 Jan 2003 02:07:32 -0500 (EST)
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by net.cc.swin.edu.au (8.9.3/8.9.3) with ESMTP id SAA28098;
	Mon, 6 Jan 2003 18:10:40 +1100 (AEDT)
Message-ID: <3E192BF2.1A9A408B@swin.edu.au>
Date: Mon, 06 Jan 2003 18:10:42 +1100
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: Doug <Dougxx2@carolina.rr.com>
CC: ietf@ietf.org
Subject: Re: Fw: namedroppers, continued  (flamed in less than an hour. figures)
References: <004201c2b52f$9aab8ea0$0701a8c0@nailed.org> <3E18F6DD.69EE90B8@swin.edu.au> <001701c2b548$ce05baf0$0701a8c0@nailed.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


Doug re-posts and cross-posts yet another private email and writes:
	[..]
> What you are refering to as netiquette is an unspoken rule of
> USENET not a mailing list as far as I know, so I don't believe it applies
> here.

I respectfully suggest you are mistaken. (On a number of points, and
this one in particular.)

	[..]
> Hopefully you won't be the next person to go in my filter
> Grenville

Either way is fine with me :)

	[..]
> P.S. If you doubt the my claim that it was the entire message either time I
> can
> always post them as file attachments for the whole group to see.

No need. I just wasn't sure if you'd posted the entire message because,
based on what you re-posted, there didn't seem to be enough to
get all worked up about. Still doesn't, but you're free to assume
all you want about how things are supposed to work in the IETF. You've
clearly been around this organization and our mailing lists for a long time.

cheers,
gja
-- 
Grenville Armitage
http://caia.swin.edu.au



From owner-ietf@ietf.org  Mon Jan  6 02:37:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28521;
	Mon, 6 Jan 2003 02:37:06 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VRq3-0003xD-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 02:38:23 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VRou-0003uc-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 02:37:12 -0500
Received: from fsnt.future.futsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28097
	for <ietf@ietf.org>; Mon, 6 Jan 2003 02:29:07 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0004089877@fsnt.future.futsoft.com> for <ietf@ietf.org>;
 Mon, 06 Jan 2003 13:06:56 +0530
Received: from ramanad (ramanad.future.futsoft.com [10.8.3.18])
	by kailash.future.futsoft.com (8.12.2/8.12.2) with SMTP id h067TZw0020577
	for <ietf@ietf.org>; Mon, 6 Jan 2003 12:59:35 +0530
Reply-To: <ramanad@future.futsoft.com>
From: "Ramana Divvi" <ramanad@future.futsoft.com>
To: <ietf@ietf.org>
Subject:  Clarification regarding RFC2507
Date: Mon, 6 Jan 2003 12:59:45 +0530
Message-Id: <001401c2b555$6395bb40$1203080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
In-Reply-To: <0a0501c2b551$6ea12c30$0701a8c0@nailed.org>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi
In RFC2507( page : 22 ), it is given that compressed non-TCP headers
contains one BYTE optional 'DATA' field.
If any one knows , please tell me what is the main purpose of this one Byte
DATA field.
Thanks in advance.
With Kind Regards,
Ramana.


***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information 
and should not be circulated or used for any purpose other than for 
what it is intended. 

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. 
FSL accepts no responsibility for loss or damage arising from 
the use of the information transmitted by this email including
damage from virus.
***************************************************************************



From owner-ietf@ietf.org  Mon Jan  6 02:37:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28570;
	Mon, 6 Jan 2003 02:37:43 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VRs1-0003zl-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 02:40:25 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VRq7-0003xF-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 02:38:28 -0500
Received: from ncsmtp03.ogw.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28154
	for <ietf@ietf.org>; Mon, 6 Jan 2003 02:30:24 -0500 (EST)
Received: from mail5.carolina.rr.com (fe5 [24.93.67.52])
	by ncsmtp03.ogw.rr.com (8.12.5/8.12.2) with ESMTP id h067WOil018975;
	Mon, 6 Jan 2003 02:32:56 -0500 (EST)
Received: from dougpro ([24.88.167.199]) by mail5.carolina.rr.com  with Microsoft SMTPSVC(5.5.1877.757.75);
	 Mon, 6 Jan 2003 02:31:53 -0500
Message-ID: <0a3b01c2b555$e6d93f40$0701a8c0@nailed.org>
From: "Doug" <Dougxx2@carolina.rr.com>
To: "grenville armitage" <garmitage@swin.edu.au>
Cc: <ietf@ietf.org>
References: <004201c2b52f$9aab8ea0$0701a8c0@nailed.org> <3E18F6DD.69EE90B8@swin.edu.au> <001701c2b548$ce05baf0$0701a8c0@nailed.org> <3E192BF2.1A9A408B@swin.edu.au>
Subject: Re: Fw: namedroppers, continued  (flamed in less than an hour. figures)
Date: Mon, 6 Jan 2003 02:33:26 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: "grenville armitage" <garmitage@swin.edu.au>
To: "Doug" <Dougxx2@carolina.rr.com>
Cc: <ietf@ietf.org>
Sent: Monday, January 06, 2003 2:10 AM
Subject: Re: Fw: namedroppers, continued (flamed in less than an hour.
figures)


>
> Doug re-posts and cross-posts yet another private email and writes:
> [..]

the reason it was cross posted was that I was not sure which mailing list
you were reading it on or Daniel either for that matter.

> > What you are refering to as netiquette is an unspoken rule of
> > USENET not a mailing list as far as I know, so I don't believe it
applies
> > here.
>

"as far as I know, so I don't believe" IE take it for what it is (my
opinion) and if I am indeed mistaken sorry to bother you with my mistake.

> I respectfully suggest you are mistaken. (On a number of points, and
> this one in particular.)
>
> [..]
> > Hopefully you won't be the next person to go in my filter
> > Grenville
>
> Either way is fine with me :)
>

Me to... I doubt you will be going there as your actually replying to me in
some sort of a civil manner but I guess you never know what tommorow will
bring.

> [..]
> > P.S. If you doubt the my claim that it was the entire message either
time I
> > can
> > always post them as file attachments for the whole group to see.
>
> No need. I just wasn't sure if you'd posted the entire message because,
> based on what you re-posted, there didn't seem to be enough to
> get all worked up about. Still doesn't, but you're free to assume

Good I really didn't want to have to post it again. The insult she levered
against me is that she was implying that not only did I not format it
incorrectly but that readers of it would not be able to understand it even
if I had inserted the paragraph breaks she was requesting. This was intended
as a shot at my ability to communicate.

> all you want about how things are supposed to work in the IETF. You've
> clearly been around this organization and our mailing lists for a long
time.
>

As far as how things work in the IETF well I am kind of new here since I
have only been subscribed to the list for about a year now and I have only
made as I stated one or two other posts. I guess I just assumed this was a
forum for professional adults that would be free from the usual trolling and
childish insults found in other arenas like usenet. Perhaps I was wrong but
I would like to think that I wasn't. Then again don't we all like to be
right about things like that.

> cheers,
> gja
> --
> Grenville Armitage
> http://caia.swin.edu.au

Now can we be done with this nonsense?
Thanks,
Doug




From owner-ietf@ietf.org  Mon Jan  6 03:52:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29421;
	Mon, 6 Jan 2003 03:52:24 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VSvE-0005dS-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 03:47:48 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VStp-0005c9-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 03:46:22 -0500
Received: from mailman.packetdesign.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29227
	for <ietf@ietf.org>; Mon, 6 Jan 2003 03:38:09 -0500 (EST)
Received: from packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.12.3/8.12.3) with ESMTP id h068ece4027018;
	Mon, 6 Jan 2003 00:40:39 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Mon, 6 Jan 2003 00:52:58 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Ramana Divvi <ramanad@future.futsoft.com>
cc: ietf@ietf.org
Subject: Re: Clarification regarding RFC2507
In-Reply-To: <001401c2b555$6395bb40$1203080a@future.futsoft.com>
Message-ID: <20030106005228.M19531-100000@oak.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 6 Jan 2003, Ramana Divvi wrote:

> Hi
> In RFC2507( page : 22 ), it is given that compressed non-TCP headers
> contains one BYTE optional 'DATA' field.
> If any one knows , please tell me what is the main purpose of this one Byte
> DATA field.

See Section 3.3.1 of RFC 2508.

                                                        -- Steve




From owner-ietf@ietf.org  Mon Jan  6 05:11:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00573;
	Mon, 6 Jan 2003 05:11:08 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VUF2-0007KH-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 05:12:20 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VUEL-0007JE-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 05:11:37 -0500
Received: from fsnt.future.futsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00467
	for <ietf@ietf.org>; Mon, 6 Jan 2003 05:03:30 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0004091106@fsnt.future.futsoft.com> for <ietf@ietf.org>;
 Mon, 06 Jan 2003 15:41:17 +0530
Received: from ramanad (ramanad.future.futsoft.com [10.8.3.18])
	by kailash.future.futsoft.com (8.12.2/8.12.2) with SMTP id h06A3uw0023327
	for <ietf@ietf.org>; Mon, 6 Jan 2003 15:33:56 +0530
Reply-To: <ramanad@future.futsoft.com>
From: "Ramana Divvi" <ramanad@future.futsoft.com>
To: <ietf@ietf.org>
Subject: RE:  Clarification regarding RTP
Date: Mon, 6 Jan 2003 15:34:07 +0530
Message-Id: <001801c2b56a$f42f5a20$1203080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi 
I have very basic doubt ( please don't laugh at me).
How will we know , UDP is carrying RTP payload?.
Is there any reserved port numbers for this case?

Thanks in advance.
With Kind Regards,
Ramana.


***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information 
and should not be circulated or used for any purpose other than for 
what it is intended. 

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. 
FSL accepts no responsibility for loss or damage arising from 
the use of the information transmitted by this email including
damage from virus.
***************************************************************************



From owner-ietf@ietf.org  Mon Jan  6 07:22:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01960;
	Mon, 6 Jan 2003 07:22:49 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VWGn-0003iF-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 07:22:17 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VWGC-0003h9-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 07:21:40 -0500
Received: from mail.enyo.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01831
	for <ietf@ietf.org>; Mon, 6 Jan 2003 07:13:33 -0500 (EST)
Received: from [212.9.189.171] (helo=deneb.enyo.de)
	by mail.enyo.de with esmtp (Exim 3.34 #2)
	id 18VWAc-0005Jk-00; Mon, 06 Jan 2003 13:15:54 +0100
Received: from fw by deneb.enyo.de with local (Exim 3.34 #4)
	id 18VWBS-0000KO-00; Mon, 06 Jan 2003 13:16:46 +0100
To: Frank Strauss <strauss@ibr.cs.tu-bs.de>
Cc: ietf@ietf.org
Subject: Re: RFC authoring tools
From: Florian Weimer <fw@deneb.enyo.de>
Mail-Followup-To: Frank Strauss <strauss@ibr.cs.tu-bs.de>, ietf@ietf.org
Date: Mon, 06 Jan 2003 13:16:46 +0100
In-Reply-To: <ypwwulkzqfk.fsf@hansa.ibr.cs.tu-bs.de> (Frank Strauss's
 message of "04 Jan 2003 20:05:19 +0100")
Message-ID: <87lm1y3235.fsf@deneb.enyo.de>
User-Agent: Gnus/5.090011 (Oort Gnus v0.11) Emacs/21.2 (i386-pc-linux-gnu)
References: <87r8btrlvw.fsf@deneb.enyo.de>
	<ypwwulkzqfk.fsf@hansa.ibr.cs.tu-bs.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Frank Strauss <strauss@ibr.cs.tu-bs.de> writes:

> This document describes a DTD and its application for authoring
> RFC-like documents. It also contains references to his open source
> tool "xml2rfc" that allows to compile such XML documents to IETF
> conformant text files and to HTML pages. 
>
> I used it for some documents and I really like it a lot.

Yes, indeed.  I think I had a look at two years ago, but ditched it
for some reason (maybe I didn't discover the switch for TOC
generation).

I've made a Debian package of it, and hope that it finds its way into
the archive some day.



From owner-ietf@ietf.org  Mon Jan  6 08:20:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02837;
	Mon, 6 Jan 2003 08:20:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VXBs-0005DY-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 08:21:16 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VXBR-0005CA-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 08:20:49 -0500
Received: from agitator.ibr.cs.tu-bs.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02769
	for <ietf@ietf.org>; Mon, 6 Jan 2003 08:12:43 -0500 (EST)
Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81])
	by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h06DFtBU018307
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL);
	Mon, 6 Jan 2003 14:15:55 +0100
Received: from hansa.ibr.cs.tu-bs.de (strauss@localhost [127.0.0.1])
	by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h06DFsAa014882
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL);
	Mon, 6 Jan 2003 14:15:54 +0100
Received: (from strauss@localhost)
	by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h06DFs6v014879;
	Mon, 6 Jan 2003 14:15:54 +0100
From: Frank Strauss <strauss@ibr.cs.tu-bs.de>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: ietf@ietf.org
Subject: Re: RFC authoring tools
References: <87r8btrlvw.fsf@deneb.enyo.de>
	<ypwwulkzqfk.fsf@hansa.ibr.cs.tu-bs.de> <87lm1y3235.fsf@deneb.enyo.de>
Date: 06 Jan 2003 14:15:54 +0100
In-Reply-To: <87lm1y3235.fsf@deneb.enyo.de>
Message-ID: <ypwy95yo1v9.fsf@hansa.ibr.cs.tu-bs.de>
Lines: 19
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi!

>> This document describes a DTD and its application for authoring
>> RFC-like documents. It also contains references to his open source
>> tool "xml2rfc" that allows to compile such XML documents to IETF
>> conformant text files and to HTML pages. 
>> 
>> I used it for some documents and I really like it a lot.

Florian> Yes, indeed.  I think I had a look at two years ago, but
Florian> ditched it for some reason (maybe I didn't discover the
Florian> switch for TOC generation).

Florian> I've made a Debian package of it, and hope that it finds its
Florian> way into the archive some day.

Cool. Wo finde ich denn derweil das Debian Package? :-)

 -frank



From owner-ietf@ietf.org  Mon Jan  6 08:31:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03095;
	Mon, 6 Jan 2003 08:31:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VXOS-0005s0-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 08:34:16 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VXKh-0005nw-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 08:30:23 -0500
Received: from mail.enyo.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02951
	for <ietf@ietf.org>; Mon, 6 Jan 2003 08:22:17 -0500 (EST)
Received: from [212.9.189.171] (helo=deneb.enyo.de)
	by mail.enyo.de with esmtp (Exim 3.34 #2)
	id 18VXF7-0007Oy-00; Mon, 06 Jan 2003 14:24:37 +0100
Received: from fw by deneb.enyo.de with local (Exim 3.34 #4)
	id 18VXFx-0000O0-00; Mon, 06 Jan 2003 14:25:29 +0100
To: Frank Strauss <strauss@ibr.cs.tu-bs.de>
Cc: ietf@ietf.org
Subject: Re: RFC authoring tools
From: Florian Weimer <fw@deneb.enyo.de>
Mail-Followup-To: Frank Strauss <strauss@ibr.cs.tu-bs.de>, ietf@ietf.org
Date: Mon, 06 Jan 2003 14:25:29 +0100
In-Reply-To: <ypwy95yo1v9.fsf@hansa.ibr.cs.tu-bs.de> (Frank Strauss's
 message of "06 Jan 2003 14:15:54 +0100")
Message-ID: <87el7q2ywm.fsf@deneb.enyo.de>
User-Agent: Gnus/5.090011 (Oort Gnus v0.11) Emacs/21.2 (i386-pc-linux-gnu)
References: <87r8btrlvw.fsf@deneb.enyo.de>
	<ypwwulkzqfk.fsf@hansa.ibr.cs.tu-bs.de> <87lm1y3235.fsf@deneb.enyo.de>
	<ypwy95yo1v9.fsf@hansa.ibr.cs.tu-bs.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Frank Strauss <strauss@ibr.cs.tu-bs.de> writes:

> Florian> I've made a Debian package of it, and hope that it finds its
> Florian> way into the archive some day.
>
> Cool. Wo finde ich denn derweil das Debian Package? :-)

Oh, it's available at <http://www.enyo.de/fw/debian/xml2rfc/>, but
it's still pending review.



From owner-ietf@ietf.org  Mon Jan  6 08:56:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03548;
	Mon, 6 Jan 2003 08:53:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VXev-0006ai-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 08:51:17 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VXeJ-0006ZE-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 08:50:39 -0500
Received: from agitator.ibr.cs.tu-bs.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03427
	for <ietf@ietf.org>; Mon, 6 Jan 2003 08:42:34 -0500 (EST)
Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81])
	by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h06DjkBU029573
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL);
	Mon, 6 Jan 2003 14:45:46 +0100
Received: from hansa.ibr.cs.tu-bs.de (strauss@localhost [127.0.0.1])
	by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h06DjjAa017883
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL);
	Mon, 6 Jan 2003 14:45:45 +0100
Received: (from strauss@localhost)
	by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h06Djjq0017880;
	Mon, 6 Jan 2003 14:45:45 +0100
From: Frank Strauss <strauss@ibr.cs.tu-bs.de>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: ietf@ietf.org
Subject: Re: RFC authoring tools
References: <87r8btrlvw.fsf@deneb.enyo.de>
	<ypwwulkzqfk.fsf@hansa.ibr.cs.tu-bs.de> <87lm1y3235.fsf@deneb.enyo.de>
	<ypwy95yo1v9.fsf@hansa.ibr.cs.tu-bs.de> <87el7q2ywm.fsf@deneb.enyo.de>
Date: 06 Jan 2003 14:45:45 +0100
In-Reply-To: <87el7q2ywm.fsf@deneb.enyo.de>
Message-ID: <ypwu1gmo0hi.fsf@hansa.ibr.cs.tu-bs.de>
Lines: 10
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi!

>> Cool. Wo finde ich denn derweil das Debian Package? :-)

Florian> Oh, it's available at <http://www.enyo.de/fw/debian/xml2rfc/>, but
Florian> it's still pending review.

Thanks.

 -frank



From owner-ietf@ietf.org  Mon Jan  6 09:43:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04368;
	Mon, 6 Jan 2003 09:43:43 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VYR3-0008JI-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 09:41:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VYNk-0008Du-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 09:37:37 -0500
Received: from smtp02.mrf.mail.rcn.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04094
	for <ietf@ietf.org>; Mon, 6 Jan 2003 09:29:26 -0500 (EST)
Received: from 216-164-191-84.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([216.164.191.84] helo=localhost)
	by smtp02.mrf.mail.rcn.net with smtp (Exim 3.35 #4)
	id 18VYIy-0007g7-00; Mon, 06 Jan 2003 09:32:40 -0500
From: "Dr. Jeffrey Race" <jrace@attglobal.net>
To: "Melinda Shore" <mshore@cisco.com>,
        "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: "Doug" <Dougxx2@carolina.rr.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 06 Jan 2003 09:32:40 -0500
Reply-To: "Dr. Jeffrey Race" <jrace@attglobal.net>
X-Mailer: PMMail 1.96a For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: Fw: namedroppers, continued (flamed in less than an hour. figures)
Message-Id: <E18VYIy-0007g7-00@smtp02.mrf.mail.rcn.net>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Sun, 05 Jan 2003 23:34:55 -0500, Valdis.Kletnieks@vt.edu wrote:

>> chose to insult someone by referring to him as a woman.

Actually women are a superior life form (to men that is).

Jeffrey Race




From owner-ietf@ietf.org  Mon Jan  6 10:03:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04967;
	Mon, 6 Jan 2003 10:03:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VYpX-0000tJ-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 10:06:19 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VYoy-0000s4-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 10:05:44 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04741
	for <ietf@ietf.org>; Mon, 6 Jan 2003 09:57:35 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id BBE2062207; Mon,  6 Jan 2003 16:00:48 +0100 (CET)
Date: Mon, 06 Jan 2003 16:00:49 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Doug <Dougxx2@carolina.rr.com>, Valdis.Kletnieks@vt.edu
Cc: ietf@ietf.org
Subject: Re: namedroppers, continued 
Message-ID: <286390000.1041865249@askvoll.hjemme.alvestrand.no>
In-Reply-To: <0a0501c2b551$6ea12c30$0701a8c0@nailed.org>
References: <5.2.0.9.2.20021206132845.01b56f88@mira-sjcm-4.cisco.com>       
     <02fc01c2b517$36d4dbb0$0701a8c0@nailed.org>
 <200301060623.h066Nn33030511@turing-police.cc.vt.edu>
 <0a0501c2b551$6ea12c30$0701a8c0@nailed.org>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On mandag, januar 06, 2003 02:01:27 -0500 Doug <Dougxx2@carolina.rr.com> 
wrote:

>> Your proposal would fix the problem, but end up tossing a large quantity
>> of babies out with the bathwater.  The problem is that for the case of
>> a mailing list, you have *4* (at least) things to keep track of:
>
> There are many comercial email servers that require the people sending
> email with their server to log into the server using a valid username and
> pass before
> doing so. I doubt they are losing any valid emails. All it does is to keep
> unauthorized users from using the server without a valid password. The
> reason
> to require that the sender address in the outgoing email matches the email
> address refrenced in the account is to keep people from sending spam from
> these email servers and using fraudulant return and/or sender address.
> I fail to see how this throws out any babies. perhaps I am missing
> something.

well....think about how mail from someone who is not an user of that system 
(like me) can send mail there....

how does your system tell the difference between a remote mail server and a 
malicious user?

                 Harald




From owner-ietf@ietf.org  Mon Jan  6 10:16:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05207;
	Mon, 6 Jan 2003 10:16:15 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VZ31-0001Zc-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 10:20:15 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VZ2u-0001YB-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 10:20:08 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05136
	for <ietf@ietf.org>; Mon, 6 Jan 2003 10:11:59 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h06FF733001086;
	Mon, 6 Jan 2003 10:15:07 -0500
Message-Id: <200301061515.h06FF733001086@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Doug <Dougxx2@carolina.rr.com>
Cc: ietf@ietf.org
Subject: Re: namedroppers, continued 
In-Reply-To: Your message of "Mon, 06 Jan 2003 02:01:27 EST."
             <0a0501c2b551$6ea12c30$0701a8c0@nailed.org> 
References: <5.2.0.9.2.20021206132845.01b56f88@mira-sjcm-4.cisco.com> <02fc01c2b517$36d4dbb0$0701a8c0@nailed.org> <200301060623.h066Nn33030511@turing-police.cc.vt.edu>
            <0a0501c2b551$6ea12c30$0701a8c0@nailed.org>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1798958414P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 06 Jan 2003 10:15:07 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 06 Jan 2003 02:01:27 EST, Doug said:

> There are many comercial email servers that require the people sending email
> with their server to log into the server using a valid username and pass
> before
> doing so. I doubt they are losing any valid emails. All it does is to keep
> unauthorized users from using the server without a valid password. The
> reason
> to require that the sender address in the outgoing email matches the email
> address refrenced in the account is to keep people from sending spam from
> these email servers and using fraudulant return and/or sender address.
> I fail to see how this throws out any babies. perhaps I am missing
> something.

What you're missing is that I can configure *MY* server so it will only:

1) Accept mail *TO* a local recipient.
2) Allow relaying of mail to a *remote* recipient after doing some sort of
authentication that it's one of my users.

And in fact, the last I heard, open relays were only 1% or so of the total
mailservers out there - so the above is already the usual state of affairs.

Note there's no requirement that *inbound* mail be authenticated, which is
the basic source of the spam problem.  Your mail server will probably
accept mail for your userid from anyplace without authentication.

Now let's say you *do* start requiring authentication for inbound mail.
Let's consider this piece of mail, which is being sent to both you and
the IETF list...

1) What userid/password does the IETF mailserver use to authenticate
itself to your mail server?  Remember in your answer to note that forcing
users to manually update a whitelist of mailing lists they are on is
a helpdesk nightmare, and hard to scale - our main mailserver has some
80K mailboxes/aliases on it, and I'm on a lot of lists.  However, just
because *I* am on a list hosted at some site doesn't mean that any other
users on my mail server wants to accept mail from that site.  However,
even if you decide *that* cost is toleralble, there's still:

2) What userid/password does my laptop use to authenticate itself to your
mail server?  And note that you can't just say "my laptop has to send it to
my mail server" - because then you need to get the userid/password pair to
my mail server.  Remember that your answer has to scale to 40 million .coms,
and that it has to work on a sender/recipient pair basis (otherwise, it's
like inviting a vampyre in - if they can get one person at your server to
OK the mail, then they can commence spamming all your users).  Note that
answers like the "reply to this message to prove you're not a spammer"
schemes are *NOT* a long-term solution - if any of those packages becomes
widespread enough to actually impact the spam problem, the spammers will
have a little Perl program scanning the bounces and canning the "yes I'm
not a spammer" responses.



-- 
				Valdis Kletnieks
				Computer Systems Senior Engineer
				Virginia Tech


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

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

iD8DBQE+GZ16cC3lWbTT17ARAi4zAKDtpp0fioT23rHRSHTYkyCFw9bzugCgh3zR
I15R9qshWaAYEmD51FEBVPA=
=wlLx
-----END PGP SIGNATURE-----

--==_Exmh_-1798958414P--



From owner-ietf@ietf.org  Mon Jan  6 13:23:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09417;
	Mon, 6 Jan 2003 13:23:19 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Vbt8-0000ie-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 13:22:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VbsT-0000i1-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 13:21:33 -0500
Received: from tx1.wvinternetservices.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09218
	for <ietf@ietf.org>; Mon, 6 Jan 2003 13:13:23 -0500 (EST)
Received: from a (63-144-68-89.citynet.net [63.144.68.89])
	by tx1.wvinternetservices.com (8.12.6/8.12.6=Outbound) with SMTP id h06ISMbF023643;
	Mon, 6 Jan 2003 13:28:23 -0500
Message-ID: <002c01c2b5af$73c093a0$5944903f@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: "Dr. Jeffrey Race" <jrace@attglobal.net>,
        "Melinda Shore" <mshore@cisco.com>, <Valdis.Kletnieks@vt.edu>
Cc: "Doug" <Dougxx2@carolina.rr.com>, <ietf@ietf.org>
References: <E18VYIy-0007g7-00@smtp02.mrf.mail.rcn.net>
Subject: Re: Fw: namedroppers, continued (flamed in less than an hour. figures)
Date: Mon, 6 Jan 2003 13:14:26 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> Actually women are a superior life form (to men that is).
> 
> Jeffrey Race

Ohh Boy.




From owner-ietf@ietf.org  Mon Jan  6 14:18:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11157;
	Mon, 6 Jan 2003 14:18:58 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VcnG-0001jJ-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 14:20:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VRir-0003nj-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 02:30:57 -0500
Received: from sopacsun.fig.net.fj (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28006
	for <ietf@ietf.org>; Mon, 6 Jan 2003 02:22:52 -0500 (EST)
Received: from flinux.sopac.org.fj (unknown [202.62.1.33])
	by sopacsun.fig.net.fj (Postfix) with ESMTP
	id C8270AAB60; Mon,  6 Jan 2003 02:25:09 -0500 (EST)
Received: by flinux.sopac.org.fj (Postfix, from userid 500)
	id 54988AE48B; Mon,  6 Jan 2003 19:24:53 +1200 (FJT)
Subject: Re: Please recant or appologize to Jim Flemming
From: Franck Martin <franck@sopac.org>
To: Jeff Williams <jwkckid1@ix.netcom.com>
Cc: director@sopac.org, ietf@ietf.org
In-Reply-To: <3E19414D.AF2A3B47@ix.netcom.com>
References: <3E19414D.AF2A3B47@ix.netcom.com>
Content-Type: multipart/alternative; boundary="=-l1sK+NbedsBRcgfI/9xj"
X-Mailer: Ximian Evolution 1.0.8-3mdk 
Date: 06 Jan 2003 19:24:52 +1200
Message-Id: <1041837892.3322.130.camel@flinux.sopac.org.fj>
Mime-Version: 1.0
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-l1sK+NbedsBRcgfI/9xj
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

I have never requested to be on this list, I have requested to have
myself removed from the list and advised where this discussion could be
taken to...

I never made a claim that this was a SPAM, but as everybody is using a
distribution list, I needed to specify it to everybody that I don't want
to receive any more messages...

It is well known that Jim Flemming is often forbiden to post on the IETF
mailing list because he does not know when to STOP an argument.

I think Jim Flemming should apologise to me for putting me on HIS
distribution list without my consent. Moreover YOU should apologise to
me for involving my director and tryng some dirty scare tactics. It
won't work!

But I know you won't... so end of discussion!

Cheers.
Franck

On Mon, 2003-01-06 at 20:41, Jeff Williams wrote:

    Frank,
    
      I believe your outburst and false claim to Jim referring to his post
    as SPAM is atrocious and uncalled for.  Please recant or apologize to
    Jim.
    
    Thank you for your cooperation in advance.
    
      Kindest regards,
    
    --
    Jeffrey A. Williams
    Spokesman for INEGroup - (Over 127k members/stakeholders strong!)
    CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
    Information Network Eng. Group. INEG. INC.
    E-Mail jwkckid1@ix.netcom.com
    Contact Number: 214-244-4827 or 972-244-3801
    Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
    
    

--=-l1sK+NbedsBRcgfI/9xj
Content-Type: text/html; charset=utf-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/1.0.4">
</HEAD>
<BODY>
I have never requested to be on this list, I have requested to have myself removed from the list and advised where this discussion could be taken to...
<BR>

<BR>
I never made a claim that this was a SPAM, but as everybody is using a distribution list, I needed to specify it to everybody that I don't want to receive any more messages...
<BR>

<BR>
It is well known that Jim Flemming is often forbiden to post on the IETF mailing list because he does not know when to STOP an argument.
<BR>

<BR>
I think Jim Flemming should apologise to me for putting me on HIS distribution list without my consent. Moreover YOU should apologise to me for involving my director and tryng some dirty scare tactics. It won't work!
<BR>

<BR>
But I know you won't... so end of discussion!
<BR>

<BR>
Cheers.
<BR>
Franck
<BR>

<BR>
On Mon, 2003-01-06 at 20:41, Jeff Williams wrote:
    <BLOCKQUOTE>
<PRE><FONT COLOR="#737373"><FONT SIZE="3"><I>Frank,</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I></FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>  I believe your outburst and false claim to Jim referring to his post</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>as SPAM is atrocious and uncalled for.  Please recant or apologize to</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>Jim.</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I></FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>Thank you for your cooperation in advance.</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I></FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>  Kindest regards,</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I></FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>--</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>Jeffrey A. Williams</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>Spokesman for INEGroup - (Over 127k members/stakeholders strong!)</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>Information Network Eng. Group. INEG. INC.</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>E-Mail jwkckid1@ix.netcom.com</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>Contact Number: 214-244-4827 or 972-244-3801</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>Address: 5 East Kirkwood Blvd. Grapevine Texas 75208</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I></FONT></FONT></I>
</PRE>
    </BLOCKQUOTE>
</BODY>
</HTML>

--=-l1sK+NbedsBRcgfI/9xj--





From owner-ietf@ietf.org  Mon Jan  6 14:19:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11171;
	Mon, 6 Jan 2003 14:19:01 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VcnG-0001jP-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 14:20:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VS3e-0004v5-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 02:52:26 -0500
Received: from mta4.rcsntx.swbell.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28686
	for <ietf@ietf.org>; Mon, 6 Jan 2003 02:44:24 -0500 (EST)
Received: from swbell.net ([208.191.74.37]) by mta4.rcsntx.swbell.net
 (iPlanet Messaging Server 5.1 HotFix 1.6 (built Oct 18 2002))
 with ESMTP id <0H8A009HA8BD6O@mta4.rcsntx.swbell.net> for ietf@ietf.org; Mon,
 06 Jan 2003 01:47:38 -0600 (CST)
Date: Mon, 06 Jan 2003 01:47:37 -0600
From: Joseph Holsten <gaph@swbell.net>
Subject: General Question
To: ietf@ietf.org
Message-id: <1FD5A6FE-214B-11D7-B4D1-000393DAFA00@swbell.net>
MIME-version: 1.0
X-Mailer: Apple Mail (2.551)
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

is any conversation directly relating to computers, or any derivative 
thereof, currently being discussed on this list? if, by scanning the 
last five emails from this list, you come to the conclusion that there 
is not, i as you as politely as possible that you not respond to said 
emails. if you can keep this idea in your mind at any point you wish to 
write, it may simplify the lives of many who subscribe to this list.
any response should be addressed to me, gaph@swbell.net , not the list, 
ietf@ietf.org.
thank you for your time
-gaph






From owner-ietf@ietf.org  Mon Jan  6 14:20:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11310;
	Mon, 6 Jan 2003 14:20:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Vcqo-0001lQ-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 14:23:54 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VSnk-0005Wv-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 03:40:04 -0500
Received: from barry.mail.mindspring.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29186
	for <ietf@ietf.org>; Mon, 6 Jan 2003 03:31:56 -0500 (EST)
Received: from dialup-64.152.233.62.dial1.dallas1.level3.net ([64.152.233.62] helo=ix.netcom.com)
	by barry.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 18VSio-0000Hh-00; Mon, 06 Jan 2003 03:34:58 -0500
Message-ID: <3E195C52.5556940D@ix.netcom.com>
Date: Mon, 06 Jan 2003 02:37:07 -0800
From: Jeff Williams <jwkckid1@ix.netcom.com>
Organization: INEGroup Spokesman
X-Mailer: Mozilla 4.08 [en] (Win95; U; 16bit)
MIME-Version: 1.0
To: Franck Martin <franck@sopac.org>
CC: director@sopac.org, ietf@ietf.org, Jim Fleming <JimFleming@ameritech.net>
Subject: Re: Please recant or appologize to Jim Flemming
References: <3E19414D.AF2A3B47@ix.netcom.com> <1041837892.3322.130.camel@flinux.sopac.org.fj>
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

Frank and all,

  I believe you did list in the changed subject line of your response
that the term SPAM in caps was used and put there by yourself.
Hence you are again not being honest.  So again I will ask you
kindly to recant and to please apologize to Jim Flemming
and everyone else that received that response of yours.

  If necessary I will repost your reply in question in it's
entirety with full headers...

  In addition I have no interest in attempting to scare anyone.
I copied the director of SOPAC.ORG in order to ensure
that such tactics as you seem to employ are regrettable,
disruptive, dishonest, and totally unnecessary, will be addressed
and known by your management structure at the top as well
as should not be a part or practice from within your organization,
SOPAC.

Franck Martin wrote:

>    I have never requested to be on this list, I have requested to have
>
> myself removed from the list and advised where this discussion could
> be
> taken to...
>
> I never made a claim that this was a SPAM, but as everybody is using a
>
> distribution list, I needed to specify it to everybody that I don't
> want
> to receive any more messages...
>
> It is well known that Jim Flemming is often forbiden to post on the
> IETF
> mailing list because he does not know when to STOP an argument.
>
> I think Jim Flemming should apologise to me for putting me on HIS
> distribution list without my consent. Moreover YOU should apologise to
>
> me for involving my director and tryng some dirty scare tactics. It
> won't work!
>
> But I know you won't... so end of discussion!
>
> Cheers.
> Franck
>
> On Mon, 2003-01-06 at 20:41, Jeff Williams wrote:
>
>     Frank,
>
>       I believe your outburst and false claim to Jim referring to his
> post
>     as SPAM is atrocious and uncalled for.  Please recant or apologize
> to
>     Jim.
>
>     Thank you for your cooperation in advance.
>
>       Kindest regards,
>
>     --
>     Jeffrey A. Williams
>     Spokesman for INEGroup - (Over 127k members/stakeholders strong!)
>     CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
>     Information Network Eng. Group. INEG. INC.
>     E-Mail jwkckid1@ix.netcom.com
>     Contact Number: 214-244-4827 or 972-244-3801
>     Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
>
>
>
>

Regards,
--
Jeffrey A. Williams
Spokesman for INEGroup - (Over 127k members/stakeholders strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number: 214-244-4827 or 972-244-3801
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208







From owner-ietf@ietf.org  Mon Jan  6 14:58:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12885;
	Mon, 6 Jan 2003 14:58:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Vd8Z-0003CJ-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 14:42:15 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Vd7x-0003B8-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 14:41:37 -0500
Received: from kristieandaaron.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA11757
	for <ietf@ietf.org>; Mon, 6 Jan 2003 14:33:27 -0500 (EST)
Received: (qmail 4296 invoked from network); 6 Jan 2003 19:36:40 -0000
Received: from unknown (HELO FLIPPY) (10.0.0.2)
  by 0 with SMTP; 6 Jan 2003 19:36:40 -0000
From: "Aaron D. Britt" <flip@deru.com>
To: <ietf@ietf.org>
Subject: RE: Please recant or appologize to Jim Flemming
Date: Mon, 6 Jan 2003 12:36:48 -0700
Message-ID: <NBEJLOBAIEPFMKBOONAGEEJHDFAA.flip@deru.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <3E195C52.5556940D@ix.netcom.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Can we talk about something technical?  All this he said, she said, my
feelings are hurt etc. is just unprofessional (IMO).  Everyone apologize to
everyone else, and lets talk about some topics that represent what this
discussion list is about, the IETF (Internet Engineering Task Force).

This list is starting to look like your common every day IRC channel.  We
are better then this, can we not rise to the challenge?

-Aaron


-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org]On Behalf Of Jeff
Williams
Sent: Monday, January 06, 2003 3:37 AM
To: Franck Martin
Cc: director@sopac.org; ietf@ietf.org; Jim Fleming
Subject: Re: Please recant or appologize to Jim Flemming


Frank and all,

  I believe you did list in the changed subject line of your response
that the term SPAM in caps was used and put there by yourself.
Hence you are again not being honest.  So again I will ask you
kindly to recant and to please apologize to Jim Flemming
and everyone else that received that response of yours.

  If necessary I will repost your reply in question in it's
entirety with full headers...

  In addition I have no interest in attempting to scare anyone.
I copied the director of SOPAC.ORG in order to ensure
that such tactics as you seem to employ are regrettable,
disruptive, dishonest, and totally unnecessary, will be addressed
and known by your management structure at the top as well
as should not be a part or practice from within your organization,
SOPAC.

Franck Martin wrote:

>    I have never requested to be on this list, I have requested to have
>
> myself removed from the list and advised where this discussion could
> be
> taken to...
>
> I never made a claim that this was a SPAM, but as everybody is using a
>
> distribution list, I needed to specify it to everybody that I don't
> want
> to receive any more messages...
>
> It is well known that Jim Flemming is often forbiden to post on the
> IETF
> mailing list because he does not know when to STOP an argument.
>
> I think Jim Flemming should apologise to me for putting me on HIS
> distribution list without my consent. Moreover YOU should apologise to
>
> me for involving my director and tryng some dirty scare tactics. It
> won't work!
>
> But I know you won't... so end of discussion!
>
> Cheers.
> Franck
>
> On Mon, 2003-01-06 at 20:41, Jeff Williams wrote:
>
>     Frank,
>
>       I believe your outburst and false claim to Jim referring to his
> post
>     as SPAM is atrocious and uncalled for.  Please recant or apologize
> to
>     Jim.
>
>     Thank you for your cooperation in advance.
>
>       Kindest regards,
>
>     --
>     Jeffrey A. Williams
>     Spokesman for INEGroup - (Over 127k members/stakeholders strong!)
>     CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
>     Information Network Eng. Group. INEG. INC.
>     E-Mail jwkckid1@ix.netcom.com
>     Contact Number: 214-244-4827 or 972-244-3801
>     Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
>
>
>
>

Regards,
--
Jeffrey A. Williams
Spokesman for INEGroup - (Over 127k members/stakeholders strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number: 214-244-4827 or 972-244-3801
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208








From owner-ietf@ietf.org  Mon Jan  6 14:58:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12902;
	Mon, 6 Jan 2003 14:58:34 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VdAY-0003GO-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 14:44:18 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VdAN-0003Ey-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 14:44:07 -0500
Received: from ncsmtp03.ogw.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11931
	for <ietf@ietf.org>; Mon, 6 Jan 2003 14:35:58 -0500 (EST)
Received: from mail7.carolina.rr.com (fe7 [24.93.67.54])
	by ncsmtp03.ogw.rr.com (8.12.5/8.12.2) with ESMTP id h06JbCih017904
	for <ietf@ietf.org>; Mon, 6 Jan 2003 14:38:29 -0500 (EST)
Received: from dougpro ([24.88.167.199]) by mail7.carolina.rr.com  with Microsoft SMTPSVC(5.5.1877.757.75);
	 Mon, 6 Jan 2003 14:35:30 -0500
Message-ID: <00cb01c2b5bb$247563a0$0701a8c0@nailed.org>
From: "Doug" <Dougxx2@carolina.rr.com>
To: <ietf@ietf.org>
Subject: Re: namedroppers, continued
Date: Mon, 6 Jan 2003 14:38:09 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I believe the answer to your first question is you would send mail
using
your own mail server not someone else's. Although...I do see unique
issues
involved in people using mail servers that are not part of their
network
(hotmail, yahoo...) to send email if they try to authenticate you as
part of
their network before allowing you to send email. I believe the
solution to
that problem is that those commercial mail servers (free or premium)
would
not be able to authenticate you as part of their network before
allowing you
to send your email. They would then require clients logging into those
accounts (with valid user names and passwords) to send email from a
valid IP
address with no unsecured proxy services running on them (much like
many IRC
servers are doing) and transmit this IP information along with the
email
being sent. This would allow for pinpoint identification of the
sender's
using IP addresses MAC addresses and time stamped logs for the
specific
purposes of taking legal action against these network abuses.

Your second question is a bit harder for me to answer. I believe (I
may be
incorrect) that there is already a difference between a receiving mail
server's transaction with a sending or relaying mail server and a mail
client. I would never claim that it is impossible for a malicious user
to do
anything (I know better). On the other hand if we can achieve
authentication
before sending email and it becomes a requirement of the system then
it
should make the actions of a malicious user stand out in the logs of
the
server allowing for tracking, blocking, and prosecution of those users
for
the unauthorized access and (mis)use of private network resources. My
solution does NOT have a way of completely stopping spam from being
sent but
perhaps in conjunction with other actions it can stop a majority of
spam
from being sent. Additionally, my solution makes it easier for end
users and
administrators to track the actions of spammers and find their virtual
locations. I would further suggest that once this information is
gathered
and verified with the spammers ISP subpoenas, court orders, cease and
desist
orders, fines under existing laws, and criminal prosecution could do
the
rest.

I am not claiming that this will eliminate spam on it's own. I am
claiming
that it will make it harder for the offending parties to get away with
sending spam in a manner that is not compliant with TOS agreements and
the
law. This solution would require a concerted effort by the
administration
comunity as a whole and I think that is where the problem truely is.

----- Original Message -----
From: "Harald Tveit Alvestrand" <harald@alvestrand.no>
To: "Doug" <Dougxx2@carolina.rr.com>; <Valdis.Kletnieks@vt.edu>
Cc: <ietf@ietf.org>
Sent: Monday, January 06, 2003 10:00 AM
Subject: Re: namedroppers, continued


>
>
> --On mandag, januar 06, 2003 02:01:27 -0500 Doug
<Dougxx2@carolina.rr.com>
> wrote:
>
> >> Your proposal would fix the problem, but end up tossing a large
quantity
> >> of babies out with the bathwater.  The problem is that for the
case of
> >> a mailing list, you have *4* (at least) things to keep track of:
> >
> > There are many comercial email servers that require the people
sending
> > email with their server to log into the server using a valid
username
and
> > pass before
> > doing so. I doubt they are losing any valid emails. All it does is
to
keep
> > unauthorized users from using the server without a valid password.
The
> > reason
> > to require that the sender address in the outgoing email matches
the
email
> > address refrenced in the account is to keep people from sending
spam
from
> > these email servers and using fraudulant return and/or sender
address.
> > I fail to see how this throws out any babies. perhaps I am missing
> > something.
>
> well....think about how mail from someone who is not an user of that
system
> (like me) can send mail there....
>
> how does your system tell the difference between a remote mail
server and
a
> malicious user?
>
>                  Harald
>




From owner-ietf@ietf.org  Mon Jan  6 14:58:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12951;
	Mon, 6 Jan 2003 14:58:46 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VdLr-000445-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 14:55:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VdKL-00042z-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 14:54:26 -0500
Received: from mailman.packetdesign.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12340
	for <ietf@ietf.org>; Mon, 6 Jan 2003 14:46:15 -0500 (EST)
Received: from packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.12.3/8.12.3) with ESMTP id h06Jmbe4091152;
	Mon, 6 Jan 2003 11:48:38 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Mon, 6 Jan 2003 12:01:10 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Ramana Divvi <ramanad@future.futsoft.com>
cc: ietf@ietf.org
Subject: RE:  Clarification regarding RTP
In-Reply-To: <001801c2b56a$f42f5a20$1203080a@future.futsoft.com>
Message-ID: <20030106115907.F19994-100000@oak.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 6 Jan 2003, Ramana Divvi wrote:

> I have very basic doubt ( please don't laugh at me).
> How will we know , UDP is carrying RTP payload?.
> Is there any reserved port numbers for this case?

The UDP port numbers used with RTP are assigned dynamically.  See
Section 7 of RFC 1890, which is being revised in Section 8 of
draft-ietf-avt-profile-new-12, for an explanation.

If your question is in regard to RTP header compression, Section 3.1
of RFC 2508 explains that the compressor must decide heuristically
whether a UDP stream carries RTP.

In other cases, the UDP port numbers are learned from the signaling
protocol that sets up the session between/among the endpoints.

These questions regarding RTP would be more appropriately directed to
the avt@ietf.org mailing list of the Audio/Video Transport working
group.

Please be sure to read carefully the documents I have mentioned, and
the references they point to where appropriate, before asking further
questions.  For example, your first question was answered in the
document you were reading (RFC 2507).  Section 5.3.2 says: "Data field
is explained in section 12", and Section 12 explains the use and gives
a pointer to RFC 2508, same as I did in my first reply.

                                                        -- Steve




From owner-ietf@ietf.org  Mon Jan  6 16:39:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15576;
	Mon, 6 Jan 2003 16:39:16 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Veyd-0001iV-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 16:40:07 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VeyQ-0001gB-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 16:39:54 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14066
	for <ietf@ietf.org>; Mon, 6 Jan 2003 15:33:42 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h06KasH2008165;
	Mon, 6 Jan 2003 15:36:54 -0500
Message-Id: <200301062036.h06KasH2008165@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Doug <Dougxx2@carolina.rr.com>
Cc: ietf@ietf.org
Subject: Re: namedroppers, continued 
In-Reply-To: Your message of "Mon, 06 Jan 2003 14:38:09 EST."
             <00cb01c2b5bb$247563a0$0701a8c0@nailed.org> 
References: <00cb01c2b5bb$247563a0$0701a8c0@nailed.org>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-632410382P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 06 Jan 2003 15:36:54 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 06 Jan 2003 14:38:09 EST, Doug <Dougxx2@carolina.rr.com>  said:
> I believe the answer to your first question is you would send mail
> using
> your own mail server not someone else's. Although...I do see unique
> issues
> involved in people using mail servers that are not part of their
> network
> (hotmail, yahoo...) to send email if they try to authenticate you as
> part of
> their network before allowing you to send email.
You're still missing the point.

How do you tell the difference between:

1) The IETF mail server sending for the IETF list.
2) The large SUN box across the hall that's the main vt.edu mail server.
3) My laptop.

Currently, my laptop will send directly to the destination.  The problem is
that although it would be trivial to change it so that it uses the central
Virginia Tech mail hub, that doesn't fix your problem - there's still no
authenticator for the vt.edu mail server at your mail server either....

Oh, and don't even suggest chasing MX records - the MX for vt.edu points
at one set of boxes, but you will almost certainly *NOT* get a connection
from them, as our outbound servers are at different addresses.  And no, we
won't change this unless you first manage to get hotmail.com and aol.com
to not use different inbound and outbound addresses first, as they do the
same thing for the same reasons.
-- 
				Valdis Kletnieks
				Computer Systems Senior Engineer
				Virginia Tech


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

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

iD8DBQE+GejmcC3lWbTT17ARAjMBAJwIdkPd4dCnS5t+d7/iArhW+PJsTwCg5cPO
X3x4T5JfmXpgmVyeuXnna50=
=lHRo
-----END PGP SIGNATURE-----

--==_Exmh_-632410382P--



From owner-ietf@ietf.org  Mon Jan  6 19:07:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19552;
	Mon, 6 Jan 2003 19:07:29 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VgRe-0003VL-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 18:14:10 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VgR9-0003Ui-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 18:13:39 -0500
Received: from ncsmtp02.ogw.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18227
	for <ietf@ietf.org>; Mon, 6 Jan 2003 18:05:18 -0500 (EST)
Received: from mail6.carolina.rr.com (fe6 [24.93.67.53])
	by ncsmtp02.ogw.rr.com (8.12.5/8.12.2) with ESMTP id h06N7gup029780;
	Mon, 6 Jan 2003 18:07:42 -0500 (EST)
Received: from dougpro ([24.88.167.199]) by mail6.carolina.rr.com  with Microsoft SMTPSVC(5.5.1877.757.75);
	 Mon, 6 Jan 2003 18:08:50 -0500
Message-ID: <011101c2b5d8$8fe30b20$0701a8c0@nailed.org>
From: "Doug" <Dougxx2@carolina.rr.com>
To: <Valdis.Kletnieks@vt.edu>
Cc: <ietf@ietf.org>
References: <00cb01c2b5bb$247563a0$0701a8c0@nailed.org> <200301062036.h06KasH2008165@turing-police.cc.vt.edu>
Subject: Re: namedroppers, continued 
Date: Mon, 6 Jan 2003 18:08:44 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I am apparently missing something here but I am going to give it a
shot anyway.

You can tell the difference between 1, 2, and 3 because they all have
a different DNS/IP footprint.

You can send email directly to the IETF mail server? Do you have an
account on that server?

I myself use a SMTP server to send out my email. It goes from my email
client to the SMTP server I happen to be using and it then gets
relayed through the network until it reaches the destination email
server.

The validation I have been referring to would take place between the
mail client and the originating server. The entire point would be to
verify the identity of the person sending the email or at least the
account it is being sent from.

I am not suggesting that the destination email server should ask for
authentication for every email it receives before it relays it on to
another mail server or a client. I am saying that the originating
server should ask for it before accepting it and relaying it on to the
network.

The originating server would then be able to assure correct header
information by not allowing an email to be sent unless the outgoing
email was tagged with the proper DNS/IP footprint (not that of an
unsecured proxy server or a spoofed IP) and a return/reply address
that is associated with the account that the client used to
authenticate with the server. This in effect means that you cannot use
a different return/reply address (or a fake return/reply address) that
cannot be traced back to your account on the originating server by the
recipient or an IP/DNS footprint that cannot be traced back to your
machine or a point on your network by the recipient. This is to force
the person sending the email to be accountable for the email sent.

I am not suggesting that the recipient or even the relaying server
should be allowed to connect back to the originating mail server or
the client that sent the email. That would create security risks for
networks hosting mail servers and clients sending the email.

I am suggesting that before someone drops an email onto an originating
mail server that the server should take what I consider to be
reasonable steps to authenticate the user and confirm their identity
and account status on that server. The server would then tag
information onto the email that would identify the machine on which
the email client that sent the email resides (not the information of
an unsecured proxy). In addition, the originating server should tag
information that identifies the account (on the originating
server/network) that the client used to send the email and force the
originating client to provide a valid reply address that is associated
with the account to the recipient of the email.

I am not suggest that originating servers should be tagging the exact
virtual location of an inbound or outbound server to anything or
changing MX records to reflect the correct virtual location to the
outside world. In fact, if this is not done it helps keep those
outbound email servers hidden from the outside world and helps keep
malicious users from finding them and exploiting them in some way to
send their email without authorization. I do feel that I should be
able to identify the actual network on which that server resides so I
can contact someone there to help track down someone who is sending
spam.

Does the above clear up any confusion? Is there anything I am missing
here? If so please tell me what because I would welcome the
opportunity to learn something new. There may very well be big gaps in
this plan I am just unaware of what they are so I welcome the
opportunity to learn that you or anyone may pointing them out would
bring.

Doug
Dougxx2@carolina.rr.com
704-721-0212

P.S. As a side note if anyone thinks this is not a proper forum for
exchanging ideas about this please do tell me. It is not my goal here
to disrupt anything. I am just trying to exchange some ideas with a
large body of professionals in the hopes of learning something and
hopefully contributing something helpful. I would also like to invite
the moderators of this forum to contribute what they think of this
line of discussion. If they think it is unproductive I would be more
than willing to drop it and never breath another word about anything
unless it falls into any guidelines they would like to set forth.
Please, anyone, do feel free to respond with anything you feel would
be helpful constructive or apropriate on this subject.



----- Original Message -----
From: <Valdis.Kletnieks@vt.edu>
To: "Doug" <Dougxx2@carolina.rr.com>
Cc: <ietf@ietf.org>
Sent: Monday, January 06, 2003 3:36 PM
Subject: Re: namedroppers, continued

>> I believe the answer to your first question is you would send mail
>> using
>>your own mail server not someone else's. Although...I do see unique
>> issues
>> involved in people using mail servers that are not part of their
>> network
>> (hotmail, yahoo...) to send email if they try to authenticate you
as
>> part of
>> their network before allowing you to send email.
>You're still missing the point.
>
>How do you tell the difference between:
>
>1) The IETF mail server sending for the IETF list.
>2) The large SUN box across the hall that's the main vt.edu mail
server.
>3) My laptop.
>
>Currently, my laptop will send directly to the destination.  The
problem is
>that although it would be trivial to change it so that it uses the
central
>Virginia Tech mail hub, that doesn't fix your problem - there's still
no
>authenticator for the vt.edu mail server at your mail server
either....
>
>Oh, and don't even suggest chasing MX records - the MX for vt.edu
points
>at one set of boxes, but you will almost certainly *NOT* get a
connection
>from them, as our outbound servers are at different addresses.  And
no, we
>won't change this unless you first manage to get hotmail.com and
aol.com
>to not use different inbound and outbound addresses first, as they do
the
>same thing for the same reasons.
>--
>    Valdis Kletnieks
>    Computer Systems Senior Engineer
>    Virginia Tech





From owner-ietf@ietf.org  Tue Jan  7 01:25:53 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24804;
	Tue, 7 Jan 2003 01:25:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VgkG-0003kl-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 18:33:24 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VgjR-0003jl-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 18:32:33 -0500
Received: from dc-mx04.cluster1.charter.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18568
	for <ietf@ietf.org>; Mon, 6 Jan 2003 18:24:20 -0500 (EST)
Received: from [66.191.42.4] (HELO thewilliamsfam)
  by dc-mx04.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9)
  with SMTP id 50882976 for ietf@ietf.org; Mon, 06 Jan 2003 18:27:35 -0500
Reply-To: "Craig Williams" <wcraig72@yahoo.com>
From: "Craig S. Williams" <cwilliams97@charter.net>
To: <ietf@ietf.org>
Subject: RE: Please recant or appologize to Jim Flemming
Date: Mon, 6 Jan 2003 18:27:35 -0500
Message-ID: <HHEJKGPNJJIKHAGPBNAKKEBLCDAA.cwilliams97@charter.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <NBEJLOBAIEPFMKBOONAGEEJHDFAA.flip@deru.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

"Can't we all just get a long?"

I'm sorry guys, I just had to say that.  ;-)

Craig S. Williams
(hp)   919.776.7427
(mb)  919.345.7614
(em)  wcraig72@yahoo.com
(wb)  http://www.thewilliamsfam.net

 -----Original Message-----
From: 	owner-ietf@ietf.org [mailto:owner-ietf@ietf.org]  On Behalf Of Aaron
D. Britt
Sent:	Monday, January 06, 2003 2:37 PM
To:	ietf@ietf.org
Subject:	RE: Please recant or appologize to Jim Flemming

Can we talk about something technical?  All this he said, she said, my
feelings are hurt etc. is just unprofessional (IMO).  Everyone apologize to
everyone else, and lets talk about some topics that represent what this
discussion list is about, the IETF (Internet Engineering Task Force).

This list is starting to look like your common every day IRC channel.  We
are better then this, can we not rise to the challenge?

-Aaron


-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org]On Behalf Of Jeff
Williams
Sent: Monday, January 06, 2003 3:37 AM
To: Franck Martin
Cc: director@sopac.org; ietf@ietf.org; Jim Fleming
Subject: Re: Please recant or appologize to Jim Flemming


Frank and all,

  I believe you did list in the changed subject line of your response
that the term SPAM in caps was used and put there by yourself.
Hence you are again not being honest.  So again I will ask you
kindly to recant and to please apologize to Jim Flemming
and everyone else that received that response of yours.

  If necessary I will repost your reply in question in it's
entirety with full headers...

  In addition I have no interest in attempting to scare anyone.
I copied the director of SOPAC.ORG in order to ensure
that such tactics as you seem to employ are regrettable,
disruptive, dishonest, and totally unnecessary, will be addressed
and known by your management structure at the top as well
as should not be a part or practice from within your organization,
SOPAC.

Franck Martin wrote:

>    I have never requested to be on this list, I have requested to have
>
> myself removed from the list and advised where this discussion could
> be
> taken to...
>
> I never made a claim that this was a SPAM, but as everybody is using a
>
> distribution list, I needed to specify it to everybody that I don't
> want
> to receive any more messages...
>
> It is well known that Jim Flemming is often forbiden to post on the
> IETF
> mailing list because he does not know when to STOP an argument.
>
> I think Jim Flemming should apologise to me for putting me on HIS
> distribution list without my consent. Moreover YOU should apologise to
>
> me for involving my director and tryng some dirty scare tactics. It
> won't work!
>
> But I know you won't... so end of discussion!
>
> Cheers.
> Franck
>
> On Mon, 2003-01-06 at 20:41, Jeff Williams wrote:
>
>     Frank,
>
>       I believe your outburst and false claim to Jim referring to his
> post
>     as SPAM is atrocious and uncalled for.  Please recant or apologize
> to
>     Jim.
>
>     Thank you for your cooperation in advance.
>
>       Kindest regards,
>
>     --
>     Jeffrey A. Williams
>     Spokesman for INEGroup - (Over 127k members/stakeholders strong!)
>     CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
>     Information Network Eng. Group. INEG. INC.
>     E-Mail jwkckid1@ix.netcom.com
>     Contact Number: 214-244-4827 or 972-244-3801
>     Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
>
>
>
>

Regards,
--
Jeffrey A. Williams
Spokesman for INEGroup - (Over 127k members/stakeholders strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number: 214-244-4827 or 972-244-3801
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208








From owner-ietf@ietf.org  Tue Jan  7 03:15:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06710;
	Tue, 7 Jan 2003 03:15:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VkWB-00071W-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 22:35:07 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VkVD-00070j-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 22:34:07 -0500
Received: from sj-msg-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22461
	for <ietf@ietf.org>; Mon, 6 Jan 2003 22:23:19 -0500 (EST)
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id h073Qcfm008750;
	Mon, 6 Jan 2003 19:26:38 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ABV44872;
	Mon, 6 Jan 2003 19:26:31 -0800 (PST)
Message-Id: <200301070326.ABV44872@mira-sjc5-c.cisco.com>
To: "Doug" <Dougxx2@carolina.rr.com>
cc: ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: namedroppers, continued 
In-Reply-To: Message from Dougxx2@carolina.rr.com
   of "Mon, 06 Jan 2003 18:08:44 EST." <011101c2b5d8$8fe30b20$0701a8c0@nailed.org> 
Date: Mon, 06 Jan 2003 22:26:31 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

In that environment, anybody can get around what you're
proposing by setting up their own first hop mail server.
Or <n> hop mail server, for that matter.

Melinda



From owner-ietf@ietf.org  Tue Jan  7 03:16:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06765;
	Tue, 7 Jan 2003 03:16:21 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Vkyh-0007IT-00
	for ietf-list@ran.ietf.org; Mon, 06 Jan 2003 23:04:35 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VkrE-0007El-00
	for ietf@ran.ietf.org; Mon, 06 Jan 2003 22:56:52 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22713
	for <ietf@ietf.org>; Mon, 6 Jan 2003 22:48:00 -0500 (EST)
Received: from rshockeybox.shockey.us (h-69-3-5-197.MCLNVA23.covad.net [69.3.5.197])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id TAA27916
	for <ietf@ietf.org>; Mon, 6 Jan 2003 19:50:58 -0800
Message-Id: <5.2.0.9.2.20030106225140.01f49328@popd.ix.netcom.com>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 06 Jan 2003 22:53:03 -0500
To: ietf@ietf.org
From: Richard Shockey <richard@shockey.us>
Subject: vote now...vote often
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk


---------------------------------------------------------------
5) Power Bracket Game: Who's the most powerful person in
    networking?
---------------------------------------------------------------
Decide in our2003 Power Bracket Game. We've used the results
from our annual Power CEO survey to come up with a list of 64
possible people. Start winnowing the field with today's
matchups: IAB Chair Leslie Daigle vs. Sprint CEO Bill Esrey and
Fidelity CIO Don Halle vs. SAP America President Bill
McDermott. We'll run two matchups every weekday until we get to
the semi-final round.

DocFinder: 3736
http://www.nwfusion.com/power/2002/bracket.html

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


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




From owner-ietf@ietf.org  Tue Jan  7 03:51:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07286;
	Tue, 7 Jan 2003 03:51:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VpUY-0005lr-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 03:53:46 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VpTs-0005lN-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 03:53:04 -0500
Received: from psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07148;
	Tue, 7 Jan 2003 03:44:52 -0500 (EST)
Received: from psg.com
	([147.28.0.62] helo=127.0.0.1 ident=zinin)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18VpP3-000MMv-00; Tue, 07 Jan 2003 00:48:05 -0800
Date: Tue, 7 Jan 2003 00:47:31 -0800
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1532748802.20030107004731@psg.com>
To: ietf@ietf.org
CC: iesg@ietf.org, "Pyda Srisuresh" <srisuresh@yahoo.com>,
        "Kireeti Kompella" <kireeti@juniper.net>, Rohit Dube <rohit@xebeo.com>,
        <acee@redback.com>, <ospf@discuss.microsoft.com>
Subject: Re: Last Call: Traffic Engineering Extensions to OSPF Version 2 to  Proposed Standard
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

<RTG AD hat on>

Let me try to summarize this discussion.

Part of the discussion was on draft-katz-yeung vs
draft-srisuesh-ospf-te. Based on the following note from Suresh--

  > Make no mistake. The comments I sent to the IETF were solely
  > in response to the IETF last call on the katz-yeung draft; not
  > in comparison with any specific draft.

--I will ignore the arguments related to this comparison.

Further comments in this e-mail are based on the text of Suresh'es
original message to the IESG:


> The draft is a solution to providing TE within an OSPF area.

This does not seem to be an argumentive statement. In fact, the draft
is supposed to do exactly this. Nothing's wrong here.

> The draft has serious scalability limitations in
> extending this to inter-area and mixed networks (with TE and
> non-TE nodes).

Because a) inter-area TE is a non-goal for this draft, and b) the
inter-area TE topic is still in the exploration stage, the draft is
not required (nor should it be assumed) to deal with inter-area TE
scenarios. Hence, I do not believe that inter-area TE properties
should be considered when deciding whether the draft should be
published as an RFC or not.

Kireeti suggested adding the following text to further clarify the
scope of the document:

  "This document purposely does not say how the mechanisms described
  here can be used for traffic engineering across multiple OSPF areas;
  that task is left to future documents."

Which I think is a fine idea.
  
Wrt the mixed network scenarios, there doesn't appear to be consensus
that behavior of the mechanism that the WG came up with and described
in draft-katz-yueng is incorrect or dangerous for the network. On the
contrary, my knowledge of the deployment experience suggests that the
mechanism is adequate.

> Please see my comments below. I would not
> recommend using this draft as the basis for building further
> TE-extensions to inter-area and mixed networks.

Design of the mechanisms for TE in inter-area scenarios is work in
progress and subject to the IETF consensus rules. Suresh is welcome to
participate in this process.

> The draft apparently evolved over time with no requirements
> document to guide it. The vendors and implementors behind the
> draft may have been guided by different set of requirements
> and motivations, such as having some working code. Unfortunately,
> this ad-hoc approach has a cost. Any new requirements are having 
> to be met in a reactive mode and having to be provided as fixes 
> on top of this "working" code. This is not right and doesnt bode 
> well for the future of the protocol.

As Kireeti mentioned, RFC2702 describes some requirements for MPLS TE.
Suresh argued though that it does not describe the requirements for
the IGP extensions that would satisfy the MPLS TE requirements. I
would like to note, however, that this document has been in the WG for
a very long time, passed the WG last call, and there is a consensus
that the described mechanism is adequate for the intra-area TE task.

> Below are my specific comments on the draft.
> 
> 1. The draft basically describes link TLVs for area-wide
>    flooding. OSPF is an AS-wide IGP, not just area-wide.  
> 
>    So, I would suggest renaming the draft as "TE extensions
>    to an OSPFv2 area", instead of the current title,
>    "TE extensions to OSPFV2". 

As Kireeti replied, the abstract already spells this out. Though I do
not believe this is a must, spelling this out in the title would also
be fine. I'd leave this up to the authors of the document.

>    Large OSPF networks with multiple areas will not
>    run this protocol.

See above for the multi-area related discussion.

> 2. It is confusing to refer an opaque LSA with with a
>    specific sub-type as "TE LSA". It makes it sound like a 
>    stand-alone OSPF LSA with a distinct LSA type - which 
>    is is not. OSPF LSAs define the flooding scope. TE LSA
>    does not.
>    
>    One suggestion would be to refer Opaque LSAs with specific 
>    sub-type 1 as "TE-type Opaque LSA".

I believe that this is a question of editorial preferences.
Changing this terminology wouldn't substantially increase
clarity or readability of the document. Leaving this up to
the authors.

> 3. The limitations section (section 1.2) should mention the 
>    following limiations with a mixed network containing TE 
>    and non-TE nodes.
>
>       1. When a network area is constituted of TE and
>          native-nodes (supporting IP-only links), the opaque 
>          LSAs will flood all nodes in the area, thereby 
>          disrupting native OSPF nodes.
> 
>          As As a general rule, a TE network is likely to generate 
>          significantly more control traffic than a native OSPF 
>          network. The excess traffic is almost directly proportional
>          to the rate at which TE circuits are set up and torn down 
>          within the TE network. 
> 
>          The more frequent and wider the flooding frequency, 
>          the larger the number of retransmissions and Acks. 
>          It is undesirable to flood non-TE nodes with TE TLVs.

Kireeti replied:

> You're right, however, that if non-TE-capable nodes are present in the
> network, they will have to flood the LSAs carrying TE information as
> well.  However, this is a natural characteristic of OSPF flooding and
> Opaque LSA mechanism not changed by the TE extensions, hence does not
> need to be explicitly explained.

Suresh:

> Yes. The draft uses Opaque LSA to propogate TE metrics.
> Naturally, all the limitations of the opaque LSA will limit
> the TE extensions.

The consensus within the WG was to use Opaque LSAs to distribute
TE information and not change the underlying flooding mechanisms
that are critical for the protocol to operate correctly. Given
this, I will agree with Kireeti that the draft does not have to
spell out what is already natural to the protocol and is not
changed. Mentioning this will do no harm, however. I'd leave
this up to the authors as well.

>       2. A link cannot be reserved for TE-only use. All links
>          must be subjectable to best-effort IP traffic first, 
>          before any of the links are permitted to carry TE traffic.
>          
>          In a mixed network, an OSPF router supporting TE-links 
>          and native IP-links could potentially select a TE link 
>          to be its least cost link and inundate the link with 
>          best-effort IP traffic,  thereby rendering the link 
>          unusable for TE purposes.

Kireeti suggested that there are at least two ways to exclude a link
from the regular IP topology--1) discourage usage of a given link by
announcing the maximum possible link cost in the regular OSPF LSAs,
and 2) not announce a link in regular LSAs at all. Suresh pointed out
that the first method does not completely exclude a link from the
regular topology (indeed, when no alternative path is available, such
a link will still be used.) Though these mechanisms are not perfect,
there does not appear to be consensus that they are inadequate.

To summarize, I would like to thank Suresh for his comments and say
that though there are a couple of places where the document could
benefit from a clarification, no show-stoppers have been identified,
and the draft should go forward. What I would also like to emphasize
is that not only there was an overwhelming consensus on the draft in
the OSPF WG where it was produced (as well as in the GMPLS community
that extended the mechanism to support optical networks), but also the
described mechanism has been implemented by several router vendors,
and deployed in a number of SP networks.

Regards.

Alex





From owner-ietf@ietf.org  Tue Jan  7 04:26:07 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07759;
	Tue, 7 Jan 2003 04:26:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Vq1R-0006le-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 04:27:45 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Vpzm-0006jn-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 04:26:02 -0500
Received: from dot-god.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07638
	for <ietf@ietf.org>; Tue, 7 Jan 2003 04:17:50 -0500 (EST)
Received: from localhost (baptista@localhost)
	by dot-god.com (8.11.4/8.11.4) with ESMTP id h079LGT13908;
	Tue, 7 Jan 2003 04:21:16 -0500
Date: Tue, 7 Jan 2003 04:21:16 -0500 (EST)
From: Joe Baptista <baptista@dot-god.com>
To: Richard Shockey <richard@shockey.us>
cc: <ietf@ietf.org>
Subject: Re: vote now...vote often
In-Reply-To: <5.2.0.9.2.20030106225140.01f49328@popd.ix.netcom.com>
Message-ID: <Pine.LNX.4.33.0301070420530.25474-100000@dot-god.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


is vint cerf on the list?

On Mon, 6 Jan 2003, Richard Shockey wrote:

>
> ---------------------------------------------------------------
> 5) Power Bracket Game: Who's the most powerful person in
>     networking?
> ---------------------------------------------------------------
> Decide in our2003 Power Bracket Game. We've used the results
> from our annual Power CEO survey to come up with a list of 64
> possible people. Start winnowing the field with today's
> matchups: IAB Chair Leslie Daigle vs. Sprint CEO Bill Esrey and
> Fidelity CIO Don Halle vs. SAP America President Bill
> McDermott. We'll run two matchups every weekday until we get to
> the semi-final round.
>
> DocFinder: 3736
> http://www.nwfusion.com/power/2002/bracket.html
>
> -----------------
>
>
>  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Richard Shockey, Senior Manager, Strategic Technology Initiatives
> NeuStar Inc.
> 46000 Center Oak Plaza  -   Sterling, VA  20166
> Voice +1 571.434.5651 Cell : +1 314.503.0640,  Fax: +1 815.333.1237
> <mailto:richard@shockey.us> or <mailto:richard.shockey@neustar.biz>
>   <http://www.neustar.biz> ; <http://www.enum.org>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
>




From owner-ietf@ietf.org  Tue Jan  7 07:15:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10678;
	Tue, 7 Jan 2003 07:15:23 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Vsf0-0003a5-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 07:16:46 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VsbD-0003Xu-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 07:12:51 -0500
Received: from prue.eim.surrey.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10546
	for <ietf@ietf.org>; Tue, 7 Jan 2003 07:04:36 -0500 (EST)
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 18VsUL-0002R3-00; Tue, 07 Jan 2003 12:05:45 +0000
Date: Tue, 7 Jan 2003 12:05:43 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Doug <Dougxx2@carolina.rr.com>
cc: Valdis.Kletnieks@vt.edu, "" <ietf@ietf.org>
Subject: Re: namedroppers, continued 
In-Reply-To: <011101c2b5d8$8fe30b20$0701a8c0@nailed.org>
Message-ID: <Pine.GSO.4.50.0301071154470.12319-100000@artemis.ee.surrey.ac.uk>
References: <00cb01c2b5bb$247563a0$0701a8c0@nailed.org>
 <200301062036.h06KasH2008165@turing-police.cc.vt.edu>
 <011101c2b5d8$8fe30b20$0701a8c0@nailed.org>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-102.4 required=7.0
	tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,NOSPAM_INC,
	      QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_03_05,
	      SUPERLONG_LINE,USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.43
X-Scanner: exiscan *18VsUL-0002R3-00*YC1j9L7/1NY* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

Doug has rediscovered the idea of closing open mail relays to prevent
unauthorised use by outsiders sending to outsiders. This was a big
thing in the early 90s when email became popular.

Doug has also come up with the idea of adding the IP address of the
originating client machine (not necessarily using SMTP) in a header
so that an attempt can be made to identify it - e.g. Hotmail has done
that for years.

L.

missing mail admin experience, I think.

On Mon, 6 Jan 2003, Doug wrote:

> I am apparently missing something here but I am going to give it a
> shot anyway.
>
> You can tell the difference between 1, 2, and 3 because they all have
> a different DNS/IP footprint.
>
> You can send email directly to the IETF mail server? Do you have an
> account on that server?
>
> I myself use a SMTP server to send out my email. It goes from my email
> client to the SMTP server I happen to be using and it then gets
> relayed through the network until it reaches the destination email
> server.
>
> The validation I have been referring to would take place between the
> mail client and the originating server. The entire point would be to
> verify the identity of the person sending the email or at least the
> account it is being sent from.
>
> I am not suggesting that the destination email server should ask for
> authentication for every email it receives before it relays it on to
> another mail server or a client. I am saying that the originating
> server should ask for it before accepting it and relaying it on to the
> network.
>
> The originating server would then be able to assure correct header
> information by not allowing an email to be sent unless the outgoing
> email was tagged with the proper DNS/IP footprint (not that of an
> unsecured proxy server or a spoofed IP) and a return/reply address
> that is associated with the account that the client used to
> authenticate with the server. This in effect means that you cannot use
> a different return/reply address (or a fake return/reply address) that
> cannot be traced back to your account on the originating server by the
> recipient or an IP/DNS footprint that cannot be traced back to your
> machine or a point on your network by the recipient. This is to force
> the person sending the email to be accountable for the email sent.
>
> I am not suggesting that the recipient or even the relaying server
> should be allowed to connect back to the originating mail server or
> the client that sent the email. That would create security risks for
> networks hosting mail servers and clients sending the email.
>
> I am suggesting that before someone drops an email onto an originating
> mail server that the server should take what I consider to be
> reasonable steps to authenticate the user and confirm their identity
> and account status on that server. The server would then tag
> information onto the email that would identify the machine on which
> the email client that sent the email resides (not the information of
> an unsecured proxy). In addition, the originating server should tag
> information that identifies the account (on the originating
> server/network) that the client used to send the email and force the
> originating client to provide a valid reply address that is associated
> with the account to the recipient of the email.
>
> I am not suggest that originating servers should be tagging the exact
> virtual location of an inbound or outbound server to anything or
> changing MX records to reflect the correct virtual location to the
> outside world. In fact, if this is not done it helps keep those
> outbound email servers hidden from the outside world and helps keep
> malicious users from finding them and exploiting them in some way to
> send their email without authorization. I do feel that I should be
> able to identify the actual network on which that server resides so I
> can contact someone there to help track down someone who is sending
> spam.
>
> Does the above clear up any confusion? Is there anything I am missing
> here? If so please tell me what because I would welcome the
> opportunity to learn something new. There may very well be big gaps in
> this plan I am just unaware of what they are so I welcome the
> opportunity to learn that you or anyone may pointing them out would
> bring.
>
> Doug
> Dougxx2@carolina.rr.com
> 704-721-0212
>
> P.S. As a side note if anyone thinks this is not a proper forum for
> exchanging ideas about this please do tell me. It is not my goal here
> to disrupt anything. I am just trying to exchange some ideas with a
> large body of professionals in the hopes of learning something and
> hopefully contributing something helpful. I would also like to invite
> the moderators of this forum to contribute what they think of this
> line of discussion. If they think it is unproductive I would be more
> than willing to drop it and never breath another word about anything
> unless it falls into any guidelines they would like to set forth.
> Please, anyone, do feel free to respond with anything you feel would
> be helpful constructive or apropriate on this subject.
>
>
>
> ----- Original Message -----
> From: <Valdis.Kletnieks@vt.edu>
> To: "Doug" <Dougxx2@carolina.rr.com>
> Cc: <ietf@ietf.org>
> Sent: Monday, January 06, 2003 3:36 PM
> Subject: Re: namedroppers, continued
>
> >> I believe the answer to your first question is you would send mail
> >> using
> >>your own mail server not someone else's. Although...I do see unique
> >> issues
> >> involved in people using mail servers that are not part of their
> >> network
> >> (hotmail, yahoo...) to send email if they try to authenticate you
> as
> >> part of
> >> their network before allowing you to send email.
> >You're still missing the point.
> >
> >How do you tell the difference between:
> >
> >1) The IETF mail server sending for the IETF list.
> >2) The large SUN box across the hall that's the main vt.edu mail
> server.
> >3) My laptop.
> >
> >Currently, my laptop will send directly to the destination.  The
> problem is
> >that although it would be trivial to change it so that it uses the
> central
> >Virginia Tech mail hub, that doesn't fix your problem - there's still
> no
> >authenticator for the vt.edu mail server at your mail server
> either....
> >
> >Oh, and don't even suggest chasing MX records - the MX for vt.edu
> points
> >at one set of boxes, but you will almost certainly *NOT* get a
> connection
> >from them, as our outbound servers are at different addresses.  And
> no, we
> >won't change this unless you first manage to get hotmail.com and
> aol.com
> >to not use different inbound and outbound addresses first, as they do
> the
> >same thing for the same reasons.
> >--
> >    Valdis Kletnieks
> >    Computer Systems Senior Engineer
> >    Virginia Tech
>
>
>
> _______________________________________________
> 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.
>

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



From owner-ietf@ietf.org  Tue Jan  7 07:38:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11126;
	Tue, 7 Jan 2003 07:38:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Vm3J-0007nL-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 00:13:25 -0500
Received: from [10.27.2.28] (helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Vm14-0007k3-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 00:11:06 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22953
	for <ietf@ietf.org>; Mon, 6 Jan 2003 23:09:25 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h074CWCR003297;
	Mon, 6 Jan 2003 23:12:32 -0500
Message-Id: <200301070412.h074CWCR003297@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Doug <Dougxx2@carolina.rr.com>
Cc: ietf@ietf.org
Subject: Re: namedroppers, continued 
In-Reply-To: Your message of "Mon, 06 Jan 2003 18:08:44 EST."
             <011101c2b5d8$8fe30b20$0701a8c0@nailed.org> 
References: <00cb01c2b5bb$247563a0$0701a8c0@nailed.org> <200301062036.h06KasH2008165@turing-police.cc.vt.edu>
            <011101c2b5d8$8fe30b20$0701a8c0@nailed.org>
X-Verified-Sender-Address: it-really-was-saddam@someplace.with.more.sand.than.here.net
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1648343258P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 06 Jan 2003 23:12:31 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 06 Jan 2003 18:08:44 EST, Doug said:
> You can tell the difference between 1, 2, and 3 because they all have
> a different DNS/IP footprint.

They do? Are you sure of this?  I'll give you a hint - if you're outside
the two /16's of our network, and you get an inbound SMTP connection from us,
looking up the PTR to get the hostname will almost certainly *NOT* have
the string 'mail' in it.

And the inbound and outbound mail servers at ietf.org are called 'odin' and
'ran', respectively..  Not much info there.

And last I heard, about 30% of the PTR space is broken beyond use due to
cluenessness on the ISP's part, so you can't get a DNS name you can trust.

So what DNS/IP footprint were you planning to use?

> You can send email directly to the IETF mail server?

Yes, sometimes multiple times an hour if I'm in a verbose mood...

>                                                       Do you have an
> account on that server?

Nope, no account there. Don't need one, works fine..

> I myself use a SMTP server to send out my email. It goes from my email
> client to the SMTP server I happen to be using and it then gets
> relayed through the network until it reaches the destination email
> server.

OK.. to be *very* pedantic, I use an SMTP server as well.  My MUA (Mail
User Agent) exmh hands the mail to the SMTP server I happen to be using,
and the SMTP server relays mail everyplace.  It just happens that my preferred
SMTP server happens to be already running on my laptop....

> I am not suggesting that the destination email server should ask for
> authentication for every email it receives before it relays it on to
> another mail server or a client. I am saying that the originating
> server should ask for it before accepting it and relaying it on to the
> network.

Aha.  I see now.  What you *want* is what all properly run mail servers
*ALREADY* do.  It's amazingly useful for tracking down users that are being
silly and need a slap upside the head to clear the kloo blockage.  What
it's NOT useful for is stopping the determined spammer who doesn't use
your mail server to inject the mail into the net....

The reason it doesn't stop spam is because you're missing an important
point - you seem to think that "if the sending server validates the user,
we won't have spam.."

> authenticate with the server. This in effect means that you cannot use
> a different return/reply address (or a fake return/reply address) that

Hmm.. so the mail I'm replying to wouldn't work, because I got it from the IETF server
but it has your From: address on it - therefore the IETF server must be
lying about who it is and who the sender is.

Actually, that's not quite true - there's usually 
> cannot be traced back to your account on the originating server by the
> recipient or an IP/DNS footprint that cannot be traced back to your
> machine or a point on your network by the recipient. This is to force
> the person sending the email to be accountable for the email sent.

OK.. and this is *forcing* it *how*?

Think carefully here - the receiving end is trusting what the sender
sends.

> and account status on that server. The server would then tag
> information onto the email that would identify the machine on which
> the email client that sent the email resides (not the information of
> an unsecured proxy). In addition, the originating server should tag
> information that identifies the account (on the originating
> server/network) that the client used to send the email and force the
> originating client to provide a valid reply address that is associated
> with the account to the recipient of the email.

And of *COURSE*, not even a SPAMMER would be so unrighteous as to forge
a "this mail was approved" header.

This mail has a 'X-Verified-Sender-Address:' header that identifies
the originating address.  Take a look at it, and tell me if you feel any
better about having verified the origin.  And remember that since I control
my machine, I can make a similar change to any *OTHER* header (From:, Sender:,
X-Authenticated:, or whatever).

And the spammer controls his server....

/Valdis


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

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

iD8DBQE+GlOvcC3lWbTT17ARApSwAJ4z7eh6RcaT8foaOP6oeXfJPWH+JQCdG3sI
coFoXE7JlB4MG4miW6opJAo=
=1iMc
-----END PGP SIGNATURE-----

--==_Exmh_-1648343258P--



From owner-ietf@ietf.org  Tue Jan  7 13:12:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22929;
	Tue, 7 Jan 2003 13:12:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VxUn-0001At-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 12:26:33 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VwXq-0006hv-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 11:25:39 -0500
Received: from hosting.altserver.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19560
	for <ietf@ietf.org>; Tue, 7 Jan 2003 11:17:17 -0500 (EST)
Received: from lns07v-11-53.w.club-internet.fr ([212.194.142.53] helo=mine.utel.net)
	by hosting.altserver.com with esmtp (Exim 3.36 #1)
	id 18VwSa-0006YY-00; Tue, 07 Jan 2003 08:20:13 -0800
Message-Id: <5.1.0.14.0.20030107144504.029ad580@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 07 Jan 2003 14:56:36 +0100
To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>, Doug <Dougxx2@carolina.rr.com>
From: jfcm <info@utel.net>
Subject: Re: namedroppers, continued 
Cc: Valdis.Kletnieks@vt.edu, "" <ietf@ietf.org>
In-Reply-To: <Pine.GSO.4.50.0301071154470.12319-100000@artemis.ee.surrey
 .ac.uk>
References: <011101c2b5d8$8fe30b20$0701a8c0@nailed.org>
 <00cb01c2b5bb$247563a0$0701a8c0@nailed.org>
 <200301062036.h06KasH2008165@turing-police.cc.vt.edu>
 <011101c2b5d8$8fe30b20$0701a8c0@nailed.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-330C66FA; boundary="=======B035769======="
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - hosting.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - utel.net
Sender: owner-ietf@ietf.org
Precedence: bulk

--=======B035769=======
Content-Type: text/plain; x-avg-checked=avg-ok-330C66FA; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit

At 13:05 07/01/03, Lloyd Wood wrote:
>Doug has rediscovered the idea of closing open mail relays to prevent
>unauthorised use by outsiders sending to outsiders. This was a big
>thing in the early 90s when email became popular.
>
>Doug has also come up with the idea of adding the IP address of the
>originating client machine (not necessarily using SMTP) in a header
>so that an attempt can be made to identify it - e.g. Hotmail has done
>that for years.
>
>missing mail admin experience, I think.

This remarks shows that the problem is around for more than ten years and 
that no one found a satisfactory solution in using the present system. 
Would this feed back from real world not be enough for us to understand its 
'cybernetic' (true meaning) lesson : the current mail system model is 
inadequate.

Question now is : do we have to investigate a new one? or can an 
architectural change/addition may elegantly address the case? probably a 
mix of both due to the existing e-mail system use. ie a new e-mail system 
with a retro-compatibility with the current one. Or would it also be a new 
TCP/IP design, compatible with the old one? Or/and a new IPv6 compatible 
with the old one?

May be Dick Clarke will tell us next week how much he wants to invest into 
such a Nextnet?
jfc






--=======B035769=======--




From owner-ietf@ietf.org  Tue Jan  7 13:52:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24025;
	Tue, 7 Jan 2003 13:52:25 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Vyhl-00042y-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 13:44:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Vya8-0003xG-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 13:36:10 -0500
Received: from b.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA23578
	for <ietf@ietf.org>; Tue, 7 Jan 2003 13:27:48 -0500 (EST)
Received: (qmail 21255 invoked from network); 7 Jan 2003 18:31:03 -0000
Received: from ultra.sonic.net (208.201.224.22)
  by b.smtp-out.sonic.net with SMTP; 7 Jan 2003 18:31:03 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id h07IV3f21411;
	Tue, 7 Jan 2003 10:31:03 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 7 Jan 2003 10:30:55 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01072003-103052-1244.MMD@SonomaDesign.com; Tue, 7 Jan 2003 10:30:52 -0800
Received: by prop.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Tue Jan  7 10:30:59 2003)
X-From_: owner-ietf@ietf.org  Tue Jan  7 10:20:01 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by prop.sonic.net (8.11.6/8.8.5) with ESMTP id h07IJtJ26232;
	Tue, 7 Jan 2003 10:19:56 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18VxUn-0001At-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 12:26:33 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VwXq-0006hv-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 11:25:39 -0500
Received: from hosting.altserver.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19560
	for <ietf@ietf.org>; Tue, 7 Jan 2003 11:17:17 -0500 (EST)
Received: from lns07v-11-53.w.club-internet.fr ([212.194.142.53] helo=mine.utel.net)
	by hosting.altserver.com with esmtp (Exim 3.36 #1)
	id 18VwSa-0006YY-00; Tue, 07 Jan 2003 08:20:13 -0800
Message-Id: <5.1.0.14.0.20030107144504.029ad580@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 07 Jan 2003 14:56:36 +0100
To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>, Doug <Dougxx2@carolina.rr.com>
From: jfcm <info@utel.net>
Subject: Re: namedroppers, continued 
Cc: Valdis.Kletnieks@vt.edu, "" <ietf@ietf.org>
In-Reply-To: <Pine.GSO.4.50.0301071154470.12319-100000@artemis.ee.surrey
 .ac.uk>
References: <011101c2b5d8$8fe30b20$0701a8c0@nailed.org>
 <00cb01c2b5bb$247563a0$0701a8c0@nailed.org>
 <200301062036.h06KasH2008165@turing-police.cc.vt.edu>
 <011101c2b5d8$8fe30b20$0701a8c0@nailed.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-330C66FA; boundary="=======B035769======="
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - hosting.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - utel.net
X-OriginalArrivalTime: 07 Jan 2003 18:30:55.0874 (UTC) FILETIME=[EAA4F620:01C2B67A]
Sender: owner-ietf@ietf.org
Precedence: bulk

--=======B035769=======
Content-Type: text/plain; x-avg-checked=avg-ok-330C66FA; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit

At 13:05 07/01/03, Lloyd Wood wrote:
>Doug has rediscovered the idea of closing open mail relays to prevent
>unauthorised use by outsiders sending to outsiders. This was a big
>thing in the early 90s when email became popular.
>
>Doug has also come up with the idea of adding the IP address of the
>originating client machine (not necessarily using SMTP) in a header
>so that an attempt can be made to identify it - e.g. Hotmail has done
>that for years.
>
>missing mail admin experience, I think.

This remarks shows that the problem is around for more than ten years and 
that no one found a satisfactory solution in using the present system. 
Would this feed back from real world not be enough for us to understand its 
'cybernetic' (true meaning) lesson : the current mail system model is 
inadequate.

Question now is : do we have to investigate a new one? or can an 
architectural change/addition may elegantly address the case? probably a 
mix of both due to the existing e-mail system use. ie a new e-mail system 
with a retro-compatibility with the current one. Or would it also be a new 
TCP/IP design, compatible with the old one? Or/and a new IPv6 compatible 
with the old one?

May be Dick Clarke will tell us next week how much he wants to invest into 
such a Nextnet?
jfc






--=======B035769=======--





From owner-ietf@ietf.org  Tue Jan  7 13:52:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24024;
	Tue, 7 Jan 2003 13:52:23 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Vyhl-000434-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 13:44:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VycJ-0003yO-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 13:38:24 -0500
Received: from ncsmtp02.ogw.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23625
	for <ietf@ietf.org>; Tue, 7 Jan 2003 13:30:03 -0500 (EST)
Received: from mail6.carolina.rr.com (fe6 [24.93.67.53])
	by ncsmtp02.ogw.rr.com (8.12.5/8.12.2) with ESMTP id h07IWPup025261;
	Tue, 7 Jan 2003 13:32:25 -0500 (EST)
Received: from dougpro ([24.88.167.199]) by mail6.carolina.rr.com  with Microsoft SMTPSVC(5.5.1877.757.75);
	 Tue, 7 Jan 2003 13:33:34 -0500
Message-ID: <009e01c2b67b$45926590$0701a8c0@nailed.org>
From: "Doug" <Dougxx2@carolina.rr.com>
To: <ietf@ietf.org>
Cc: "Lloyd Wood" <l.wood@eim.surrey.ac.uk>
Subject: Re: namedroppers, continued
Date: Tue, 7 Jan 2003 13:33:28 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello Mr. Wood,

----- Original Message -----
From: "Lloyd Wood" <l.wood@eim.surrey.ac.uk>
To: "Doug" <Dougxx2@carolina.rr.com>
Cc: <Valdis.Kletnieks@vt.edu>; <ietf@ietf.org>
Sent: Tuesday, January 07, 2003 7:05 AM
Subject: Re: namedroppers, continued


> Doug has rediscovered the idea of closing open mail relays to
prevent
> unauthorised use by outsiders sending to outsiders. This was a big
> thing in the early 90s when email became popular.

This may seem to be a bit basic for some of the people who have worked
on this problem for years. My intention was not to prove that I had
the latest and greatest solution to the spam problem. It was to get
the ball rolling in an open discussion forum and present my ideas on
the topic in the hopes that someone who knew more than me on the topic
would as well.

>
> Doug has also come up with the idea of adding the IP address of the
> originating client machine (not necessarily using SMTP) in a header
> so that an attempt can be made to identify it - e.g. Hotmail has
done
> that for years.

After examining the headers of many of the spam advertisments I get
and trying to contact the administrator of the network it came from I
find that it is usually futile because the network doesn't exist and
the IP information is incorrect. I also find that most use false
sender and reply address information (in an attempt to keep recipiants
from filtering them). This makes it hard (at least for me) to do
anything about them. I have experimented with filters for subject
wording but this unfortunately hits on some of my wanted email as
well. This reduces my ability to to block them on the receiving end.
Even if I could it doesn't help the net congestion they cause or do
anything about the processing time it is using across the net. These
things leads me to propose that a more global solution needs to be
implemented. The problem here is that when you bring this up for
discussion in a professional environment like this one people don't
want to discuss it. Instead they consider it a problem that has no
solution and just want to forget about it.

>
> L.
>
> missing mail admin experience, I think.

Very true. I have never administered anything other than my http and
ftp servers. I have thought of turning on the mailserver but I do not
know enough about administering it yet and I really have no need for
it. I certainly hope that nobody thought I actually ran my own mail
server because I was not my intention to pretend that I did.

It is nice to see someone with more knowledge and/or experience on the
topic than me taking the time to think (and talk) about it.

Thanks for the input,
Doug
Asking questions, presenting possible solutions, and learning from
mistakes is how we get solutions.
---------------snipped previous for sake of size------------------




From owner-ietf@ietf.org  Tue Jan  7 15:36:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27633;
	Tue, 7 Jan 2003 15:36:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W0A1-0007jz-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 15:17:17 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W03g-0007aY-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 15:10:44 -0500
Received: from b.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA25017
	for <ietf@ietf.org>; Tue, 7 Jan 2003 14:13:12 -0500 (EST)
Received: (qmail 28240 invoked from network); 7 Jan 2003 19:16:28 -0000
Received: from turbo.sonic.net (208.201.224.26)
  by b.smtp-out.sonic.net with SMTP; 7 Jan 2003 19:16:28 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h07JG5X09162;
	Tue, 7 Jan 2003 11:16:05 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 7 Jan 2003 11:15:55 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01072003-111554-1269.MMD@SonomaDesign.com; Tue, 7 Jan 2003 11:15:54 -0800
Received: by prop.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Tue Jan  7 11:16:01 2003)
X-From_: owner-ietf@ietf.org  Tue Jan  7 11:11:03 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h07J9so29469;
	Tue, 7 Jan 2003 11:09:59 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Vyhl-000434-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 13:44:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18VycJ-0003yO-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 13:38:24 -0500
Received: from ncsmtp02.ogw.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23625
	for <ietf@ietf.org>; Tue, 7 Jan 2003 13:30:03 -0500 (EST)
Received: from mail6.carolina.rr.com (fe6 [24.93.67.53])
	by ncsmtp02.ogw.rr.com (8.12.5/8.12.2) with ESMTP id h07IWPup025261;
	Tue, 7 Jan 2003 13:32:25 -0500 (EST)
Received: from dougpro ([24.88.167.199]) by mail6.carolina.rr.com  with Microsoft SMTPSVC(5.5.1877.757.75);
	 Tue, 7 Jan 2003 13:33:34 -0500
Message-ID: <009e01c2b67b$45926590$0701a8c0@nailed.org>
From: "Doug" <Dougxx2@carolina.rr.com>
To: <ietf@ietf.org>
Cc: "Lloyd Wood" <l.wood@eim.surrey.ac.uk>
Subject: Re: namedroppers, continued
Date: Tue, 7 Jan 2003 13:33:28 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Jan 2003 19:15:55.0624 (UTC) FILETIME=[33D21E80:01C2B681]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello Mr. Wood,

----- Original Message -----
From: "Lloyd Wood" <l.wood@eim.surrey.ac.uk>
To: "Doug" <Dougxx2@carolina.rr.com>
Cc: <Valdis.Kletnieks@vt.edu>; <ietf@ietf.org>
Sent: Tuesday, January 07, 2003 7:05 AM
Subject: Re: namedroppers, continued


> Doug has rediscovered the idea of closing open mail relays to
prevent
> unauthorised use by outsiders sending to outsiders. This was a big
> thing in the early 90s when email became popular.

This may seem to be a bit basic for some of the people who have worked
on this problem for years. My intention was not to prove that I had
the latest and greatest solution to the spam problem. It was to get
the ball rolling in an open discussion forum and present my ideas on
the topic in the hopes that someone who knew more than me on the topic
would as well.

>
> Doug has also come up with the idea of adding the IP address of the
> originating client machine (not necessarily using SMTP) in a header
> so that an attempt can be made to identify it - e.g. Hotmail has
done
> that for years.

After examining the headers of many of the spam advertisments I get
and trying to contact the administrator of the network it came from I
find that it is usually futile because the network doesn't exist and
the IP information is incorrect. I also find that most use false
sender and reply address information (in an attempt to keep recipiants
from filtering them). This makes it hard (at least for me) to do
anything about them. I have experimented with filters for subject
wording but this unfortunately hits on some of my wanted email as
well. This reduces my ability to to block them on the receiving end.
Even if I could it doesn't help the net congestion they cause or do
anything about the processing time it is using across the net. These
things leads me to propose that a more global solution needs to be
implemented. The problem here is that when you bring this up for
discussion in a professional environment like this one people don't
want to discuss it. Instead they consider it a problem that has no
solution and just want to forget about it.

>
> L.
>
> missing mail admin experience, I think.

Very true. I have never administered anything other than my http and
ftp servers. I have thought of turning on the mailserver but I do not
know enough about administering it yet and I really have no need for
it. I certainly hope that nobody thought I actually ran my own mail
server because I was not my intention to pretend that I did.

It is nice to see someone with more knowledge and/or experience on the
topic than me taking the time to think (and talk) about it.

Thanks for the input,
Doug
Asking questions, presenting possible solutions, and learning from
mistakes is how we get solutions.
---------------snipped previous for sake of size------------------





From owner-ietf@ietf.org  Tue Jan  7 16:05:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28705;
	Tue, 7 Jan 2003 16:04:52 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W0bZ-0000Ff-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 15:45:45 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W0OP-0008Id-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 15:32:09 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27309
	for <ietf@ietf.org>; Tue, 7 Jan 2003 15:23:50 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h07KQtoM010986;
	Tue, 7 Jan 2003 15:26:55 -0500
Message-Id: <200301072026.h07KQtoM010986@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Doug <Dougxx2@carolina.rr.com>
Cc: ietf@ietf.org
Subject: Re: namedroppers, continued 
In-Reply-To: Your message of "Tue, 07 Jan 2003 13:33:28 EST."
             <009e01c2b67b$45926590$0701a8c0@nailed.org> 
References: <009e01c2b67b$45926590$0701a8c0@nailed.org>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_4182422P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 07 Jan 2003 15:26:55 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Tue, 07 Jan 2003 13:33:28 EST, Doug said:

> After examining the headers of many of the spam advertisments I get
> and trying to contact the administrator of the network it came from I
> find that it is usually futile because the network doesn't exist and
> the IP information is incorrect. I also find that most use false
> sender and reply address information (in an attempt to keep recipiants
> from filtering them). This makes it hard (at least for me) to do
> anything about them.

The trick here is to remember that except for the relative few spammers that
are advocating a religious/political/philosophical viewpoint (a la "Uncertainty
Principle is Untenable!"), the spammers *WANT* you to be able to contact them
via *some* means - they can't extract money (their usual goal) from you if
you can't get back to them.

Moreover, it has to be relatively simple to find - it has to be simple enough
that even a victim who doesn't have enough kloo to stop to wonder why the
"confidential and private" Nigerian scam arrived via spammage can figure out
how to get aboard....

-- 
				Valdis Kletnieks
				Computer Systems Senior Engineer
				Virginia Tech


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

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

iD8DBQE+GzgPcC3lWbTT17ARAm+PAKDbhvSsyIu9Xzg8yLh3I/gz4TOIGwCgrZie
w6Pn6+7E0x55O+v+A/ribP4=
=5jrw
-----END PGP SIGNATURE-----

--==_Exmh_4182422P--



From owner-ietf@ietf.org  Tue Jan  7 16:44:28 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29714;
	Tue, 7 Jan 2003 16:44:06 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W1DT-0003uU-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 16:24:55 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W1AA-0001ev-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 16:21:33 -0500
Received: from b.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA28948
	for <ietf@ietf.org>; Tue, 7 Jan 2003 16:12:47 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: (qmail 13207 invoked from network); 7 Jan 2003 21:16:02 -0000
Received: from turbo.sonic.net (208.201.224.26)
  by b.smtp-out.sonic.net with SMTP; 7 Jan 2003 21:16:02 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h07LG1G23917;
	Tue, 7 Jan 2003 13:16:01 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 7 Jan 2003 13:15:54 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01072003-131554-1339.MMD@SonomaDesign.com; Tue, 7 Jan 2003 13:15:54 -0800
Received: by ultra.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Tue Jan  7 13:16:00 2003)
X-From_: owner-ietf@ietf.org  Tue Jan  7 13:14:23 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by prop.sonic.net (8.11.6/8.8.5) with ESMTP id h07LE7302601;
	Tue, 7 Jan 2003 13:14:09 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W0bZ-0000Ff-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 15:45:45 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W0OP-0008Id-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 15:32:09 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27309
	for <ietf@ietf.org>; Tue, 7 Jan 2003 15:23:50 -0500 (EST)
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h07KQtoM010986;
	Tue, 7 Jan 2003 15:26:55 -0500
Message-Id: <200301072026.h07KQtoM010986@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Doug <Dougxx2@carolina.rr.com>
Cc: ietf@ietf.org
Subject: Re: namedroppers, continued 
In-Reply-To: Your message of "Tue, 07 Jan 2003 13:33:28 EST."
             <009e01c2b67b$45926590$0701a8c0@nailed.org> 
References: <009e01c2b67b$45926590$0701a8c0@nailed.org>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_4182422P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 07 Jan 2003 15:26:55 -0500
X-OriginalArrivalTime: 07 Jan 2003 21:15:54.0979 (UTC) FILETIME=[F6F88330:01C2B691]
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Tue, 07 Jan 2003 13:33:28 EST, Doug said:

> After examining the headers of many of the spam advertisments I get
> and trying to contact the administrator of the network it came from I
> find that it is usually futile because the network doesn't exist and
> the IP information is incorrect. I also find that most use false
> sender and reply address information (in an attempt to keep recipiants
> from filtering them). This makes it hard (at least for me) to do
> anything about them.

The trick here is to remember that except for the relative few spammers that
are advocating a religious/political/philosophical viewpoint (a la "Uncertainty
Principle is Untenable!"), the spammers *WANT* you to be able to contact them
via *some* means - they can't extract money (their usual goal) from you if
you can't get back to them.

Moreover, it has to be relatively simple to find - it has to be simple enough
that even a victim who doesn't have enough kloo to stop to wonder why the
"confidential and private" Nigerian scam arrived via spammage can figure out
how to get aboard....

-- 
				Valdis Kletnieks
				Computer Systems Senior Engineer
				Virginia Tech


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

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

iD8DBQE+GzgPcC3lWbTT17ARAm+PAKDbhvSsyIu9Xzg8yLh3I/gz4TOIGwCgrZie
w6Pn6+7E0x55O+v+A/ribP4=
=5jrw
-----END PGP SIGNATURE-----

--==_Exmh_4182422P--




From owner-ietf@ietf.org  Tue Jan  7 17:28:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01369;
	Tue, 7 Jan 2003 17:28:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W1uj-00083q-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 17:09:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W1q7-0007Y5-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 17:04:51 -0500
Received: from smtp02.mrf.mail.rcn.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00543
	for <ietf@ietf.org>; Tue, 7 Jan 2003 16:56:30 -0500 (EST)
Received: from 216-164-191-84.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([216.164.191.84] helo=localhost)
	by smtp02.mrf.mail.rcn.net with smtp (Exim 3.35 #4)
	id 18W1lB-0005dx-00
	for ietf@ietf.org; Tue, 07 Jan 2003 16:59:45 -0500
From: "Dr. Jeffrey Race" <jrace@attglobal.net>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 07 Jan 2003 16:59:46 -0500
Reply-To: "Dr. Jeffrey Race" <jrace@attglobal.net>
X-Mailer: PMMail 1.96a For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: namedroppers, continued
Message-Id: <E18W1lB-0005dx-00@smtp02.mrf.mail.rcn.net>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Tue, 07 Jan 2003 15:26:55 -0500, Valdis.Kletnieks@vt.edu wrote:
>The trick here is to remember that except for the relative few spammers that
>are advocating a religious/political/philosophical viewpoint (a la "Uncertainty
>Principle is Untenable!"), the spammers *WANT* you to be able to contact them
>via *some* means - they can't extract money


See <www.camblab.com/nugget/extermin.htm>

If the contact data are invalid, report to RIR or to ICANN.  They
are obliged to correct the data.

Jeffrey Race




From owner-ietf@ietf.org  Tue Jan  7 18:10:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02413;
	Tue, 7 Jan 2003 18:09:26 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W2YV-0001HF-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 17:50:43 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W2Sl-000127-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 17:44:48 -0500
Received: from tndh.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01607
	for <ietf@ietf.org>; Tue, 7 Jan 2003 17:36:09 -0500 (EST)
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S1C20A> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 07 Jan 2003 14:39:25 -0800
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Doug'" <Dougxx2@carolina.rr.com>, <ietf@ietf.org>
Cc: "'Lloyd Wood'" <l.wood@eim.surrey.ac.uk>
Subject: RE: namedroppers, continued
Date: Tue, 7 Jan 2003 14:39:02 -0800
Message-ID: <043c01c2b69d$9499e6f0$9f144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <009e01c2b67b$45926590$0701a8c0@nailed.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA02413

Doug wrote:
> ...
> After examining the headers of many of the spam advertisments 
> I get and trying to contact the administrator of the network 
> it came from I find that it is usually futile because the 
> network doesn't exist and the IP information is incorrect. I 
> also find that most use false sender and reply address 
> information (in an attempt to keep recipiants from filtering 
> them). This makes it hard (at least for me) to do anything 
> about them. I have experimented with filters for subject 
> wording but this unfortunately hits on some of my wanted 
> email as well. This reduces my ability to to block them on 
> the receiving end. Even if I could it doesn't help the net 
> congestion they cause or do anything about the processing 
> time it is using across the net. These things leads me to 
> propose that a more global solution needs to be implemented. 
> The problem here is that when you bring this up for 
> discussion in a professional environment like this one people 
> don't want to discuss it. Instead they consider it a problem 
> that has no solution and just want to forget about it.

An approach that is more effective than scanning for content is to
simply block connections from the last hop in the SMTP chain before
yours. This kills both direct spammers as well as open relays. The list
can be long (mine is ~ 256 /24's for a private little mailer), but that
is a tradeoff against how much space you want to block at a time. On
several occasions I have considered putting in 61/8, 200/6, & 210/7,
because that would remove 3/4 of the list, but that also creates a
guilt-by-association for people with no control over their address space
or those who are abusing it. 

While this approach avoids having the content traverse the wire, some of
the machines are tenacious, as yesterday's log shows. 
http://www.tndh.net/~tony/ietf/2003-01-05-log.txt

Tony





From owner-ietf@ietf.org  Tue Jan  7 18:10:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02415;
	Tue, 7 Jan 2003 18:09:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W2aZ-0001OL-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 17:52:51 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W2Yw-0001Ii-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 17:51:10 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA01730
	for <ietf@ietf.org>; Tue, 7 Jan 2003 17:42:48 -0500 (EST)
Received: (qmail 10843 invoked from network); 7 Jan 2003 22:46:03 -0000
Received: from turbo.sonic.net (208.201.224.26)
  by a.smtp-out.sonic.net with SMTP; 7 Jan 2003 22:46:03 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h07Mk3P13604
	for <ietf@ietf.org>; Tue, 7 Jan 2003 14:46:03 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 7 Jan 2003 14:45:55 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01072003-144554-1382.MMD@SonomaDesign.com; Tue, 7 Jan 2003 14:45:54 -0800
Received: by turbo.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Tue Jan  7 14:46:01 2003)
X-From_: owner-ietf@ietf.org  Tue Jan  7 14:36:54 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h07Mail13000;
	Tue, 7 Jan 2003 14:36:46 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W1uj-00083q-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 17:09:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W1q7-0007Y5-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 17:04:51 -0500
Received: from smtp02.mrf.mail.rcn.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00543
	for <ietf@ietf.org>; Tue, 7 Jan 2003 16:56:30 -0500 (EST)
Received: from 216-164-191-84.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([216.164.191.84] helo=localhost)
	by smtp02.mrf.mail.rcn.net with smtp (Exim 3.35 #4)
	id 18W1lB-0005dx-00
	for ietf@ietf.org; Tue, 07 Jan 2003 16:59:45 -0500
From: "Dr. Jeffrey Race" <jrace@attglobal.net>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 07 Jan 2003 16:59:46 -0500
Reply-To: "Dr. Jeffrey Race" <jrace@attglobal.net>
X-Mailer: PMMail 1.96a For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: namedroppers, continued
Message-Id: <E18W1lB-0005dx-00@smtp02.mrf.mail.rcn.net>
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Jan 2003 22:45:55.0698 (UTC) FILETIME=[8A0CD520:01C2B69E]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Tue, 07 Jan 2003 15:26:55 -0500, Valdis.Kletnieks@vt.edu wrote:
>The trick here is to remember that except for the relative few spammers that
>are advocating a religious/political/philosophical viewpoint (a la "Uncertainty
>Principle is Untenable!"), the spammers *WANT* you to be able to contact them
>via *some* means - they can't extract money


See <www.camblab.com/nugget/extermin.htm>

If the contact data are invalid, report to RIR or to ICANN.  They
are obliged to correct the data.

Jeffrey Race





From owner-ietf@ietf.org  Tue Jan  7 18:49:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03840;
	Tue, 7 Jan 2003 18:48:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W2sB-0001jC-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 18:11:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W2li-0001c8-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 18:04:22 -0500
Received: from calcite.rhyolite.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02049
	for <ietf@ietf.org>; Tue, 7 Jan 2003 17:55:58 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.7.Beta0/8.12.7.Beta0) id h07Mx5Vr018276
	for ietf@ietf.org env-from <vjs>;
	Tue, 7 Jan 2003 15:59:05 -0700 (MST)
Date: Tue, 7 Jan 2003 15:59:05 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200301072259.h07Mx5Vr018276@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: namedroppers, continued
References:  <E18W1lB-0005dx-00@smtp02.mrf.mail.rcn.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Dr. Jeffrey Race" <jrace@attglobal.net>

> ...
> If the contact data are invalid, report to RIR or to ICANN.  They
> are obliged to correct the data.

No, contrary to the common hope to extract petty vengence from spammers,
they are merely forced to provide contact data that is not obviously
bogus.  Worse, by forcing spammers to be less creative, these efforts
make them harder to recognize.  A random name and address from the
nearest phone book is not readily identifiable, unlike the false names
previously favored by many spammers.  Both sorts of domain contacts
are useless for contacting spammers.

Besides, domain contact addresses generally unrelated and are
certainly irrelevant to the contact addresses for collecting money
in almost all spam.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue Jan  7 19:32:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05327;
	Tue, 7 Jan 2003 19:31:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W3Vn-0003H4-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 18:51:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W3H6-0002pZ-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 18:36:58 -0500
Received: from b.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA03330
	for <ietf@ietf.org>; Tue, 7 Jan 2003 18:27:49 -0500 (EST)
Received: (qmail 5735 invoked from network); 7 Jan 2003 23:31:04 -0000
Received: from prop.sonic.net (208.201.224.193)
  by b.smtp-out.sonic.net with SMTP; 7 Jan 2003 23:31:04 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by prop.sonic.net (8.11.6/8.8.5) with ESMTP id h07NV4l21463;
	Tue, 7 Jan 2003 15:31:04 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 7 Jan 2003 15:30:57 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01072003-153054-1405.MMD@SonomaDesign.com; Tue, 7 Jan 2003 15:30:54 -0800
Received: by prop.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Tue Jan  7 15:31:00 2003)
X-From_: owner-ietf@ietf.org  Tue Jan  7 15:26:30 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h07NPmi07818;
	Tue, 7 Jan 2003 15:26:04 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W2YV-0001HF-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 17:50:43 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W2Sl-000127-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 17:44:48 -0500
Received: from tndh.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01607
	for <ietf@ietf.org>; Tue, 7 Jan 2003 17:36:09 -0500 (EST)
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S1C20A> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 07 Jan 2003 14:39:25 -0800
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Doug'" <Dougxx2@carolina.rr.com>, <ietf@ietf.org>
Cc: "'Lloyd Wood'" <l.wood@eim.surrey.ac.uk>
Subject: RE: namedroppers, continued
Date: Tue, 7 Jan 2003 14:39:02 -0800
Message-ID: <043c01c2b69d$9499e6f0$9f144104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <009e01c2b67b$45926590$0701a8c0@nailed.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by turbo.sonic.net id h07NPmi07818
X-OriginalArrivalTime: 07 Jan 2003 23:30:57.0479 (UTC) FILETIME=[D46FE570:01C2B6A4]
Content-Transfer-Encoding: 8bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Doug wrote:
> ...
> After examining the headers of many of the spam advertisments 
> I get and trying to contact the administrator of the network 
> it came from I find that it is usually futile because the 
> network doesn't exist and the IP information is incorrect. I 
> also find that most use false sender and reply address 
> information (in an attempt to keep recipiants from filtering 
> them). This makes it hard (at least for me) to do anything 
> about them. I have experimented with filters for subject 
> wording but this unfortunately hits on some of my wanted 
> email as well. This reduces my ability to to block them on 
> the receiving end. Even if I could it doesn't help the net 
> congestion they cause or do anything about the processing 
> time it is using across the net. These things leads me to 
> propose that a more global solution needs to be implemented. 
> The problem here is that when you bring this up for 
> discussion in a professional environment like this one people 
> don't want to discuss it. Instead they consider it a problem 
> that has no solution and just want to forget about it.

An approach that is more effective than scanning for content is to
simply block connections from the last hop in the SMTP chain before
yours. This kills both direct spammers as well as open relays. The list
can be long (mine is ~ 256 /24's for a private little mailer), but that
is a tradeoff against how much space you want to block at a time. On
several occasions I have considered putting in 61/8, 200/6, & 210/7,
because that would remove 3/4 of the list, but that also creates a
guilt-by-association for people with no control over their address space
or those who are abusing it. 

While this approach avoids having the content traverse the wire, some of
the machines are tenacious, as yesterday's log shows. 
http://www.tndh.net/~tony/ietf/2003-01-05-log.txt

Tony






From owner-ietf@ietf.org  Tue Jan  7 20:03:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06511;
	Tue, 7 Jan 2003 20:03:05 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W4BQ-0005pj-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 19:35:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W491-0005cl-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 19:32:31 -0500
Received: from sccrmhc02.attbi.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05072
	for <ietf@ietf.org>; Tue, 7 Jan 2003 19:24:03 -0500 (EST)
Received: from attbi.com (12-234-28-165.client.attbi.com[12.234.28.165])
          by sccrmhc02.attbi.com (sccrmhc02) with SMTP
          id <2003010800271900200jpjlqe>; Wed, 8 Jan 2003 00:27:19 +0000
Message-ID: <3E1B70CB.CA71051B@attbi.com>
Date: Tue, 07 Jan 2003 16:28:59 -0800
From: Peter Deutsch <pdeutsch@attbi.com>
Reply-To: pdeutsch@earthlink.net
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Craig Williams <wcraig72@yahoo.com>
CC: ietf@ietf.org
Subject: Re: Please recant or appologize to Jim Flemming
References: <HHEJKGPNJJIKHAGPBNAKKEBLCDAA.cwilliams97@charter.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"Craig S. Williams" wrote:
> 
> "Can't we all just get a long?"


Seems more like Strother Martin in "Cool Hand Luke"

       "What we have here, is a failure to communicate..."


				- peterd



---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software

  ""It doesn't hurt to be optimistic. You can always cry later."
                             -- Lucimar Santos De Lima
------------------------------------------------------------------



From owner-ietf@ietf.org  Tue Jan  7 20:04:28 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06537;
	Tue, 7 Jan 2003 20:03:49 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W4BE-0005oK-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 19:34:48 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W41S-0004y7-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 19:24:49 -0500
Received: from b.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA04790
	for <ietf@ietf.org>; Tue, 7 Jan 2003 19:15:55 -0500 (EST)
Received: (qmail 24315 invoked from network); 8 Jan 2003 00:19:10 -0000
Received: from ultra.sonic.net (208.201.224.22)
  by b.smtp-out.sonic.net with SMTP; 8 Jan 2003 00:19:10 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id h08011D07624
	for <ietf@ietf.org>; Tue, 7 Jan 2003 16:01:01 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 7 Jan 2003 16:00:54 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01072003-160054-1420.MMD@SonomaDesign.com; Tue, 7 Jan 2003 16:00:54 -0800
Received: by sub.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Tue Jan  7 16:01:00 2003)
X-From_: owner-ietf@ietf.org  Tue Jan  7 15:58:14 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h07Nvo727769;
	Tue, 7 Jan 2003 15:57:52 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W2sB-0001jC-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 18:11:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W2li-0001c8-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 18:04:22 -0500
Received: from calcite.rhyolite.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02049
	for <ietf@ietf.org>; Tue, 7 Jan 2003 17:55:58 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.7.Beta0/8.12.7.Beta0) id h07Mx5Vr018276
	for ietf@ietf.org env-from <vjs>;
	Tue, 7 Jan 2003 15:59:05 -0700 (MST)
Date: Tue, 7 Jan 2003 15:59:05 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200301072259.h07Mx5Vr018276@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: namedroppers, continued
References:  <E18W1lB-0005dx-00@smtp02.mrf.mail.rcn.net>
X-OriginalArrivalTime: 08 Jan 2003 00:00:54.0682 (UTC) FILETIME=[03A74FA0:01C2B6A9]
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Dr. Jeffrey Race" <jrace@attglobal.net>

> ...
> If the contact data are invalid, report to RIR or to ICANN.  They
> are obliged to correct the data.

No, contrary to the common hope to extract petty vengence from spammers,
they are merely forced to provide contact data that is not obviously
bogus.  Worse, by forcing spammers to be less creative, these efforts
make them harder to recognize.  A random name and address from the
nearest phone book is not readily identifiable, unlike the false names
previously favored by many spammers.  Both sorts of domain contacts
are useless for contacting spammers.

Besides, domain contact addresses generally unrelated and are
certainly irrelevant to the contact addresses for collecting money
in almost all spam.


Vernon Schryver    vjs@rhyolite.com




From owner-ietf@ietf.org  Tue Jan  7 20:59:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08225;
	Tue, 7 Jan 2003 20:59:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W5AU-0000VY-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 20:38:06 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W58q-0000Oc-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 20:36:24 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA07431
	for <ietf@ietf.org>; Tue, 7 Jan 2003 20:27:46 -0500 (EST)
Received: (qmail 13533 invoked from network); 8 Jan 2003 01:31:01 -0000
Received: from turbo.sonic.net (208.201.224.26)
  by a.smtp-out.sonic.net with SMTP; 8 Jan 2003 01:31:01 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h081V1t23139;
	Tue, 7 Jan 2003 17:31:01 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 7 Jan 2003 17:30:54 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01072003-173053-1454.MMD@SonomaDesign.com; Tue, 7 Jan 2003 17:30:53 -0800
Received: by sub.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Tue Jan  7 17:31:00 2003)
X-From_: owner-ietf@ietf.org  Tue Jan  7 17:17:56 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id h081HIC04452;
	Tue, 7 Jan 2003 17:17:21 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W4BQ-0005pj-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 19:35:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W491-0005cl-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 19:32:31 -0500
Received: from sccrmhc02.attbi.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05072
	for <ietf@ietf.org>; Tue, 7 Jan 2003 19:24:03 -0500 (EST)
Received: from attbi.com (12-234-28-165.client.attbi.com[12.234.28.165])
          by sccrmhc02.attbi.com (sccrmhc02) with SMTP
          id <2003010800271900200jpjlqe>; Wed, 8 Jan 2003 00:27:19 +0000
Message-ID: <3E1B70CB.CA71051B@attbi.com>
Date: Tue, 07 Jan 2003 16:28:59 -0800
From: Peter Deutsch <pdeutsch@attbi.com>
Reply-To: pdeutsch@earthlink.net
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Craig Williams <wcraig72@yahoo.com>
CC: ietf@ietf.org
Subject: Re: Please recant or appologize to Jim Flemming
References: <HHEJKGPNJJIKHAGPBNAKKEBLCDAA.cwilliams97@charter.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Jan 2003 01:30:54.0307 (UTC) FILETIME=[9614B330:01C2B6B5]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"Craig S. Williams" wrote:
> 
> "Can't we all just get a long?"


Seems more like Strother Martin in "Cool Hand Luke"

       "What we have here, is a failure to communicate..."


				- peterd



---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software

  ""It doesn't hurt to be optimistic. You can always cry later."
                             -- Lucimar Santos De Lima
------------------------------------------------------------------




From owner-ietf@ietf.org  Tue Jan  7 21:34:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09232;
	Tue, 7 Jan 2003 21:33:50 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W5hb-0001e9-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 21:12:19 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W5Vk-0001IL-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 21:00:05 -0500
Received: from culsu.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA08022
	for <ietf@ietf.org>; Tue, 7 Jan 2003 20:51:35 -0500 (EST)
Received: FROM culsu.net BY culsu.net ; Tue, 7 Jan 2003 20:54:40 -5:00 
Message-ID: <003b01c2b6b8$e80032c0$2267810a@culsu.net>
From: "Daniel Pelstring" <culsu@culsu.net>
To: "Doug" <Dougxx2@carolina.rr.com>
Cc: <ietf@ietf.org>
References: <009e01c2b67b$45926590$0701a8c0@nailed.org>
Subject: Re: namedroppers, continued
Date: Tue, 7 Jan 2003 20:54:35 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Doug,

    This topic comes up quite often.  It has been discussed at length many
times.  Do not take criticism of your ideas too harshly, it is just that
most people here have seen these same solutions proposed by many people over
many years.  It gets a bit old and, patience gets a bit short.  A very quick
summary of the solutions proposed during these discussions is as follows:

A) Anybody can send mail to anybody (what we currently have.)

B) Mail servers check that the sender is authorized to send mail to the
users of its system.

C) Sending mail requires some sort of computationally expensive to compute,
easy to check, data to be sent along with messages (probably based on sender
address, receiver address and message)

    Unfortunately, B requires that there be some way to authenticate users
of other systems.  The only way that has been thought of to do this is to
have some central authority to do this.  While it is certainly possible,
this is thought to be a bad idea for many reasons, the most prominent of
which is the potential for abuse.  Lacking a central authority, this can be
done on mail servers already, with no need to involve the IETF (an example
would be whilelists.).

    Unfortuantely, C would have to be computable in a reasonable amount of
time in order not to be a major headache.  This means that the spammers
large cluster of powerful computers would still be able to send many
messages.  It would also wreak havoc with mailing lists.  It would also
become easier to compute as time goes on, due to the ever progressing nature
of computers.  This does not even take into account that we would be
creating a standard with the sole purpose of inefficiency, which probably
makes most engineers wince and, although that may not seem like such a
horrible idea right now, this standard could survive far into the future,
with implications yet to be known (keep in mind the scale on which these
standards will be implemented.)  If another solution is implemented in the
future, this may come back to bite us.

    At the moment, it seems the IETF consensus (notice the *seem* here, this
is my personal opinion taken from reading the discourse on these lists) is
that the best solution is A.  At some point another solution may hold the
majority favor, but that time is not now.

    Of course, it is possible that there is a solution that has not been
thought of, in which case it is a bad idea to discourage people from
thinking about it.  Know, however, that this list contains many extremely
arrogant (many of them justifiably so) experts in their chosen field, who
dislike their time being wasted.  I encourage you, if you have further
ideas, to do the required research to see if it would work before sending a
message and, be very thorough.  Also know that if you choose to get into a
flame war with people on this list, that some them have likely been doing
this for decades and, are probably much better at it than you are.  It is
likely to do nothing but frustrate you.  If you have another idea and, have
questions about how to check that it is at least feasable, I would be happy
to point you in the right direction.

-Daniel Pelstring


----- Original Message -----
From: "Doug" <Dougxx2@carolina.rr.com>
To: <ietf@ietf.org>
Cc: "Lloyd Wood" <l.wood@eim.surrey.ac.uk>
Sent: Tuesday, January 07, 2003 1:33 PM
Subject: Re: namedroppers, continued


> Hello Mr. Wood,
>
> ----- Original Message -----
> From: "Lloyd Wood" <l.wood@eim.surrey.ac.uk>
> To: "Doug" <Dougxx2@carolina.rr.com>
> Cc: <Valdis.Kletnieks@vt.edu>; <ietf@ietf.org>
> Sent: Tuesday, January 07, 2003 7:05 AM
> Subject: Re: namedroppers, continued
>
>
> > Doug has rediscovered the idea of closing open mail relays to
> prevent
> > unauthorised use by outsiders sending to outsiders. This was a big
> > thing in the early 90s when email became popular.
>
> This may seem to be a bit basic for some of the people who have worked
> on this problem for years. My intention was not to prove that I had
> the latest and greatest solution to the spam problem. It was to get
> the ball rolling in an open discussion forum and present my ideas on
> the topic in the hopes that someone who knew more than me on the topic
> would as well.
>
> >
> > Doug has also come up with the idea of adding the IP address of the
> > originating client machine (not necessarily using SMTP) in a header
> > so that an attempt can be made to identify it - e.g. Hotmail has
> done
> > that for years.
>
> After examining the headers of many of the spam advertisments I get
> and trying to contact the administrator of the network it came from I
> find that it is usually futile because the network doesn't exist and
> the IP information is incorrect. I also find that most use false
> sender and reply address information (in an attempt to keep recipiants
> from filtering them). This makes it hard (at least for me) to do
> anything about them. I have experimented with filters for subject
> wording but this unfortunately hits on some of my wanted email as
> well. This reduces my ability to to block them on the receiving end.
> Even if I could it doesn't help the net congestion they cause or do
> anything about the processing time it is using across the net. These
> things leads me to propose that a more global solution needs to be
> implemented. The problem here is that when you bring this up for
> discussion in a professional environment like this one people don't
> want to discuss it. Instead they consider it a problem that has no
> solution and just want to forget about it.
>
> >
> > L.
> >
> > missing mail admin experience, I think.
>
> Very true. I have never administered anything other than my http and
> ftp servers. I have thought of turning on the mailserver but I do not
> know enough about administering it yet and I really have no need for
> it. I certainly hope that nobody thought I actually ran my own mail
> server because I was not my intention to pretend that I did.
>
> It is nice to see someone with more knowledge and/or experience on the
> topic than me taking the time to think (and talk) about it.
>
> Thanks for the input,
> Doug
> Asking questions, presenting possible solutions, and learning from
> mistakes is how we get solutions.
> ---------------snipped previous for sake of size------------------
>
>
>




From owner-ietf@ietf.org  Tue Jan  7 22:18:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09961;
	Tue, 7 Jan 2003 22:18:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W6Pf-0003Or-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 21:57:51 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W6Jq-000372-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 21:51:55 -0500
Received: from b.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA09352
	for <ietf@ietf.org>; Tue, 7 Jan 2003 21:42:47 -0500 (EST)
Received: (qmail 12982 invoked from network); 8 Jan 2003 02:46:01 -0000
Received: from ultra.sonic.net (208.201.224.22)
  by b.smtp-out.sonic.net with SMTP; 8 Jan 2003 02:46:01 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id h082k1h24837;
	Tue, 7 Jan 2003 18:46:01 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 7 Jan 2003 18:45:53 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01072003-184553-1478.MMD@SonomaDesign.com; Tue, 7 Jan 2003 18:45:53 -0800
Received: by ultra.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Tue Jan  7 18:46:00 2003)
X-From_: owner-ietf@ietf.org  Tue Jan  7 18:45:49 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h082jOP17897;
	Tue, 7 Jan 2003 18:45:29 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W5hb-0001e9-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 21:12:19 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W5Vk-0001IL-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 21:00:05 -0500
Received: from culsu.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA08022
	for <ietf@ietf.org>; Tue, 7 Jan 2003 20:51:35 -0500 (EST)
Received: FROM culsu.net BY culsu.net ; Tue, 7 Jan 2003 20:54:40 -5:00 
Message-ID: <003b01c2b6b8$e80032c0$2267810a@culsu.net>
From: "Daniel Pelstring" <culsu@culsu.net>
To: "Doug" <Dougxx2@carolina.rr.com>
Cc: <ietf@ietf.org>
References: <009e01c2b67b$45926590$0701a8c0@nailed.org>
Subject: Re: namedroppers, continued
Date: Tue, 7 Jan 2003 20:54:35 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Jan 2003 02:45:53.0838 (UTC) FILETIME=[1002A4E0:01C2B6C0]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Doug,

    This topic comes up quite often.  It has been discussed at length many
times.  Do not take criticism of your ideas too harshly, it is just that
most people here have seen these same solutions proposed by many people over
many years.  It gets a bit old and, patience gets a bit short.  A very quick
summary of the solutions proposed during these discussions is as follows:

A) Anybody can send mail to anybody (what we currently have.)

B) Mail servers check that the sender is authorized to send mail to the
users of its system.

C) Sending mail requires some sort of computationally expensive to compute,
easy to check, data to be sent along with messages (probably based on sender
address, receiver address and message)

    Unfortunately, B requires that there be some way to authenticate users
of other systems.  The only way that has been thought of to do this is to
have some central authority to do this.  While it is certainly possible,
this is thought to be a bad idea for many reasons, the most prominent of
which is the potential for abuse.  Lacking a central authority, this can be
done on mail servers already, with no need to involve the IETF (an example
would be whilelists.).

    Unfortuantely, C would have to be computable in a reasonable amount of
time in order not to be a major headache.  This means that the spammers
large cluster of powerful computers would still be able to send many
messages.  It would also wreak havoc with mailing lists.  It would also
become easier to compute as time goes on, due to the ever progressing nature
of computers.  This does not even take into account that we would be
creating a standard with the sole purpose of inefficiency, which probably
makes most engineers wince and, although that may not seem like such a
horrible idea right now, this standard could survive far into the future,
with implications yet to be known (keep in mind the scale on which these
standards will be implemented.)  If another solution is implemented in the
future, this may come back to bite us.

    At the moment, it seems the IETF consensus (notice the *seem* here, this
is my personal opinion taken from reading the discourse on these lists) is
that the best solution is A.  At some point another solution may hold the
majority favor, but that time is not now.

    Of course, it is possible that there is a solution that has not been
thought of, in which case it is a bad idea to discourage people from
thinking about it.  Know, however, that this list contains many extremely
arrogant (many of them justifiably so) experts in their chosen field, who
dislike their time being wasted.  I encourage you, if you have further
ideas, to do the required research to see if it would work before sending a
message and, be very thorough.  Also know that if you choose to get into a
flame war with people on this list, that some them have likely been doing
this for decades and, are probably much better at it than you are.  It is
likely to do nothing but frustrate you.  If you have another idea and, have
questions about how to check that it is at least feasable, I would be happy
to point you in the right direction.

-Daniel Pelstring


----- Original Message -----
From: "Doug" <Dougxx2@carolina.rr.com>
To: <ietf@ietf.org>
Cc: "Lloyd Wood" <l.wood@eim.surrey.ac.uk>
Sent: Tuesday, January 07, 2003 1:33 PM
Subject: Re: namedroppers, continued


> Hello Mr. Wood,
>
> ----- Original Message -----
> From: "Lloyd Wood" <l.wood@eim.surrey.ac.uk>
> To: "Doug" <Dougxx2@carolina.rr.com>
> Cc: <Valdis.Kletnieks@vt.edu>; <ietf@ietf.org>
> Sent: Tuesday, January 07, 2003 7:05 AM
> Subject: Re: namedroppers, continued
>
>
> > Doug has rediscovered the idea of closing open mail relays to
> prevent
> > unauthorised use by outsiders sending to outsiders. This was a big
> > thing in the early 90s when email became popular.
>
> This may seem to be a bit basic for some of the people who have worked
> on this problem for years. My intention was not to prove that I had
> the latest and greatest solution to the spam problem. It was to get
> the ball rolling in an open discussion forum and present my ideas on
> the topic in the hopes that someone who knew more than me on the topic
> would as well.
>
> >
> > Doug has also come up with the idea of adding the IP address of the
> > originating client machine (not necessarily using SMTP) in a header
> > so that an attempt can be made to identify it - e.g. Hotmail has
> done
> > that for years.
>
> After examining the headers of many of the spam advertisments I get
> and trying to contact the administrator of the network it came from I
> find that it is usually futile because the network doesn't exist and
> the IP information is incorrect. I also find that most use false
> sender and reply address information (in an attempt to keep recipiants
> from filtering them). This makes it hard (at least for me) to do
> anything about them. I have experimented with filters for subject
> wording but this unfortunately hits on some of my wanted email as
> well. This reduces my ability to to block them on the receiving end.
> Even if I could it doesn't help the net congestion they cause or do
> anything about the processing time it is using across the net. These
> things leads me to propose that a more global solution needs to be
> implemented. The problem here is that when you bring this up for
> discussion in a professional environment like this one people don't
> want to discuss it. Instead they consider it a problem that has no
> solution and just want to forget about it.
>
> >
> > L.
> >
> > missing mail admin experience, I think.
>
> Very true. I have never administered anything other than my http and
> ftp servers. I have thought of turning on the mailserver but I do not
> know enough about administering it yet and I really have no need for
> it. I certainly hope that nobody thought I actually ran my own mail
> server because I was not my intention to pretend that I did.
>
> It is nice to see someone with more knowledge and/or experience on the
> topic than me taking the time to think (and talk) about it.
>
> Thanks for the input,
> Doug
> Asking questions, presenting possible solutions, and learning from
> mistakes is how we get solutions.
> ---------------snipped previous for sake of size------------------
>
>
>





From owner-ietf@ietf.org  Wed Jan  8 00:24:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13054;
	Wed, 8 Jan 2003 00:23:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W8Jh-0001Rg-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 23:59:49 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W8JF-0001PI-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 23:59:22 -0500
Received: from cobalt.sopac.org.fj (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12629
	for <ietf@ietf.org>; Tue, 7 Jan 2003 23:50:42 -0500 (EST)
Received: by cobalt.sopac.org.fj (Postfix, from userid 416)
	id 3340417C31; Wed,  8 Jan 2003 04:52:32 +0000 (UTC)
Received: from bigiron.sopac.org.fj (unknown [10.0.0.180])
	by cobalt.sopac.org.fj (Postfix) with ESMTP id EFE0217C09
	for <ietf@ietf.org>; Wed,  8 Jan 2003 04:52:31 +0000 (UTC)
Received: by BIGIRON with Internet Mail Service (5.5.2650.21)
	id <W0Q5AQDL>; Wed, 8 Jan 2003 16:52:43 +1200
Message-ID: <F12ECEA0435AD211B5280008C7ACBC85016B4719@BIGIRON>
From: Franck Martin <Franck@sopac.org>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: FW: Please recant or appologize to Jim Flemming
Date: Wed, 8 Jan 2003 16:52:42 +1200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20
Sender: owner-ietf@ietf.org
Precedence: bulk


http://www.dnso.org/clubpublic/ga/Arc10/msg01532.html

I think we close the thread here, but beware of scam artists that try to
change the Internet and the IETF by false claims, terrorist tactics and
highjacking good mailing lists like the IETF by subscribing IETF members to
their rants.

If only we could get all along....



From owner-ietf@ietf.org  Wed Jan  8 01:12:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15867;
	Wed, 8 Jan 2003 01:11:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W9A4-0003FN-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 00:53:56 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W992-0003Bv-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 00:52:53 -0500
Received: from dot-god.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15363
	for <ietf@ietf.org>; Wed, 8 Jan 2003 00:44:21 -0500 (EST)
Received: from localhost (baptista@localhost)
	by dot-god.com (8.11.4/8.11.4) with ESMTP id h085kVi17309;
	Wed, 8 Jan 2003 00:46:31 -0500
Date: Wed, 8 Jan 2003 00:46:30 -0500 (EST)
From: Joe Baptista <baptista@dot-god.com>
To: Franck Martin <Franck@sopac.org>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: FW: Please recant or appologize to Jim Flemming
In-Reply-To: <F12ECEA0435AD211B5280008C7ACBC85016B4719@BIGIRON>
Message-ID: <Pine.LNX.4.33.0301080036100.25474-100000@dot-god.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Wed, 8 Jan 2003, Franck Martin wrote:

>
> http://www.dnso.org/clubpublic/ga/Arc10/msg01532.html

The interesting thing about Jeff Williams is that he could be anyone.
Maybe a soviet spy whos still out in the cold.  Or a U.S. government
agent living in a missile sile somewhere in Kansas - or is that Texas.
Who knows.  To date many members of the press have quoted Jeff
extensively.  And I have yet to see any of those members of the press
correct their copy when these claims that he is a fiction are made to
them.  They check their fact - don't they?

Obviously he must be for real - the press would not lead us astray
claiming him to be a expert without verifiable proof.  Or would they?
hmmm?

The one thing I do know about Jeff Williams.  If he is a fiction - the man
is abviously a genious having imposed himself far and wide fooling even
the press showing us that reporters are fools to be had.  If he is for
real - well the press already considers him an expert in the field so
there's no contest there.

cheers
joe baptista






From owner-ietf@ietf.org  Wed Jan  8 01:12:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15846;
	Wed, 8 Jan 2003 01:11:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W98C-00039k-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 00:52:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W97T-00036S-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 00:51:15 -0500
Received: from b.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA15340
	for <ietf@ietf.org>; Wed, 8 Jan 2003 00:42:45 -0500 (EST)
Received: (qmail 1987 invoked from network); 8 Jan 2003 05:46:01 -0000
Received: from ultra.sonic.net (208.201.224.22)
  by b.smtp-out.sonic.net with SMTP; 8 Jan 2003 05:46:01 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id h085k1B26722
	for <ietf@ietf.org>; Tue, 7 Jan 2003 21:46:01 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 7 Jan 2003 21:45:53 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01072003-214553-1507.MMD@SonomaDesign.com; Tue, 7 Jan 2003 21:45:53 -0800
Received: by turbo.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Tue Jan  7 21:46:00 2003)
X-From_: owner-ietf@ietf.org  Tue Jan  7 21:32:51 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h085WfG28701;
	Tue, 7 Jan 2003 21:32:43 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W8Jh-0001Rg-00
	for ietf-list@ran.ietf.org; Tue, 07 Jan 2003 23:59:49 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W8JF-0001PI-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 23:59:22 -0500
Received: from cobalt.sopac.org.fj (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12629
	for <ietf@ietf.org>; Tue, 7 Jan 2003 23:50:42 -0500 (EST)
Received: by cobalt.sopac.org.fj (Postfix, from userid 416)
	id 3340417C31; Wed,  8 Jan 2003 04:52:32 +0000 (UTC)
Received: from bigiron.sopac.org.fj (unknown [10.0.0.180])
	by cobalt.sopac.org.fj (Postfix) with ESMTP id EFE0217C09
	for <ietf@ietf.org>; Wed,  8 Jan 2003 04:52:31 +0000 (UTC)
Received: by BIGIRON with Internet Mail Service (5.5.2650.21)
	id <W0Q5AQDL>; Wed, 8 Jan 2003 16:52:43 +1200
Message-ID: <F12ECEA0435AD211B5280008C7ACBC85016B4719@BIGIRON>
From: Franck Martin <Franck@sopac.org>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: FW: Please recant or appologize to Jim Flemming
Date: Wed, 8 Jan 2003 16:52:42 +1200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20
X-OriginalArrivalTime: 08 Jan 2003 05:45:53.0541 (UTC) FILETIME=[35228B50:01C2B6D9]
Sender: owner-ietf@ietf.org
Precedence: bulk


http://www.dnso.org/clubpublic/ga/Arc10/msg01532.html

I think we close the thread here, but beware of scam artists that try to
change the Internet and the IETF by false claims, terrorist tactics and
highjacking good mailing lists like the IETF by subscribing IETF members to
their rants.

If only we could get all along....




From owner-ietf@ietf.org  Wed Jan  8 02:14:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25089;
	Wed, 8 Jan 2003 02:13:48 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W9wL-0005Ga-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 01:43:49 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W9pf-0004sH-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 01:37:03 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA16655
	for <ietf@ietf.org>; Wed, 8 Jan 2003 01:27:46 -0500 (EST)
Received: (qmail 17464 invoked from network); 8 Jan 2003 06:31:02 -0000
Received: from turbo.sonic.net (208.201.224.26)
  by a.smtp-out.sonic.net with SMTP; 8 Jan 2003 06:31:02 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h086V2G20317;
	Tue, 7 Jan 2003 22:31:02 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 7 Jan 2003 22:30:53 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01072003-223053-1515.MMD@SonomaDesign.com; Tue, 7 Jan 2003 22:30:53 -0800
Received: by ultra.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Tue Jan  7 22:31:00 2003)
X-From_: owner-ietf@ietf.org  Tue Jan  7 22:27:05 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by prop.sonic.net (8.11.6/8.8.5) with ESMTP id h086Qol04571;
	Tue, 7 Jan 2003 22:26:55 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18W9A4-0003FN-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 00:53:56 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W992-0003Bv-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 00:52:53 -0500
Received: from dot-god.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15363
	for <ietf@ietf.org>; Wed, 8 Jan 2003 00:44:21 -0500 (EST)
Received: from localhost (baptista@localhost)
	by dot-god.com (8.11.4/8.11.4) with ESMTP id h085kVi17309;
	Wed, 8 Jan 2003 00:46:31 -0500
Date: Wed, 8 Jan 2003 00:46:30 -0500 (EST)
From: Joe Baptista <baptista@dot-god.com>
To: Franck Martin <Franck@sopac.org>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: FW: Please recant or appologize to Jim Flemming
In-Reply-To: <F12ECEA0435AD211B5280008C7ACBC85016B4719@BIGIRON>
Message-ID: <Pine.LNX.4.33.0301080036100.25474-100000@dot-god.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 08 Jan 2003 06:30:53.0870 (UTC) FILETIME=[7EA80CE0:01C2B6DF]
Sender: owner-ietf@ietf.org
Precedence: bulk


On Wed, 8 Jan 2003, Franck Martin wrote:

>
> http://www.dnso.org/clubpublic/ga/Arc10/msg01532.html

The interesting thing about Jeff Williams is that he could be anyone.
Maybe a soviet spy whos still out in the cold.  Or a U.S. government
agent living in a missile sile somewhere in Kansas - or is that Texas.
Who knows.  To date many members of the press have quoted Jeff
extensively.  And I have yet to see any of those members of the press
correct their copy when these claims that he is a fiction are made to
them.  They check their fact - don't they?

Obviously he must be for real - the press would not lead us astray
claiming him to be a expert without verifiable proof.  Or would they?
hmmm?

The one thing I do know about Jeff Williams.  If he is a fiction - the man
is abviously a genious having imposed himself far and wide fooling even
the press showing us that reporters are fools to be had.  If he is for
real - well the press already considers him an expert in the field so
there's no contest there.

cheers
joe baptista







From owner-ietf@ietf.org  Wed Jan  8 02:26:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06354;
	Wed, 8 Jan 2003 02:26:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WA76-0005gi-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 01:54:56 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WA6K-0005e0-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 01:54:08 -0500
Received: from tx2.wvinternetservices.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17111
	for <ietf@ietf.org>; Wed, 8 Jan 2003 01:45:42 -0500 (EST)
Received: from a (63-144-68-249.citynet.net [63.144.68.249])
	by tx2.wvinternetservices.com (8.12.6/8.12.6=Outbound) with SMTP id h086gjqw029926
	for <ietf@ietf.org>; Wed, 8 Jan 2003 01:42:47 -0500
Message-ID: <003b01c2b6e1$bc8f4d00$f944903f@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: <ietf@ietf.org>
Date: Wed, 8 Jan 2003 01:46:50 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Who does the real IE work in the Internet world? Is it the IESG or IAB?
Seems like there's more arguing on this list than anything else.




From owner-ietf@ietf.org  Wed Jan  8 03:31:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13409;
	Wed, 8 Jan 2003 03:31:24 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WBHU-0000AP-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 03:09:44 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WBEC-0008VM-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 03:06:21 -0500
Received: from b.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA12855
	for <ietf@ietf.org>; Wed, 8 Jan 2003 02:57:47 -0500 (EST)
Received: (qmail 15831 invoked from network); 8 Jan 2003 08:01:02 -0000
Received: from ultra.sonic.net (208.201.224.22)
  by b.smtp-out.sonic.net with SMTP; 8 Jan 2003 08:01:02 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id h08812008431
	for <ietf@ietf.org>; Wed, 8 Jan 2003 00:01:02 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 00:00:55 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-000054-1534.MMD@SonomaDesign.com; Wed, 8 Jan 2003 00:00:54 -0800
Received: by sub.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 00:01:01 2003)
X-From_: owner-ietf@ietf.org  Tue Jan  7 23:34:52 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id h087YjI19618;
	Tue, 7 Jan 2003 23:34:47 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WA76-0005gi-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 01:54:56 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WA6K-0005e0-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 01:54:08 -0500
Received: from tx2.wvinternetservices.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17111
	for <ietf@ietf.org>; Wed, 8 Jan 2003 01:45:42 -0500 (EST)
Received: from a (63-144-68-249.citynet.net [63.144.68.249])
	by tx2.wvinternetservices.com (8.12.6/8.12.6=Outbound) with SMTP id h086gjqw029926
	for <ietf@ietf.org>; Wed, 8 Jan 2003 01:42:47 -0500
Message-ID: <003b01c2b6e1$bc8f4d00$f944903f@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: <ietf@ietf.org>
Date: Wed, 8 Jan 2003 01:46:50 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Jan 2003 08:00:55.0073 (UTC) FILETIME=[12063910:01C2B6EC]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Who does the real IE work in the Internet world? Is it the IESG or IAB?
Seems like there's more arguing on this list than anything else.





From owner-ietf@ietf.org  Wed Jan  8 13:11:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00134;
	Wed, 8 Jan 2003 13:11:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WKGo-0000lf-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 12:45:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WJSj-0004g1-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 11:54:00 -0500
Received: from maile.telia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24513;
	Wed, 8 Jan 2003 11:45:00 -0500 (EST)
Received: from d1o888.telia.com (d1o888.telia.com [213.67.172.241])
	by maile.telia.com (8.12.5/8.12.5) with ESMTP id h08GmFaA003019;
	Wed, 8 Jan 2003 17:48:15 +0100 (CET)
X-Original-Recipient: iesg@ietf.org
Received: from pi.se (h70n2fls31o888.telia.com [213.64.120.70])
	by d1o888.telia.com (8.10.2/8.10.1) with ESMTP id h08GmE209693;
	Wed, 8 Jan 2003 17:48:14 +0100 (CET)
Message-ID: <3E1C556F.2040704@pi.se>
Date: Wed, 08 Jan 2003 17:44:31 +0100
From: Loa Andersson <loa@pi.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Adrian Farrel <afarrel@movaz.com>
CC: iesg@ietf.org, Osama Aboul-Magd <osama@nortelnetworks.com>, ietf@ietf.org
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
References: <28F05913385EAC43AF019413F674A01704A175C6@OCCLUST04EVS1.ugd.att.com> <023601c2b2a0$c82a44c0$681810ac@movaz.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

Adrian,

trying to understand what you are saying - it seems like you are
implying that there is no consensus with in ITU on how to progress
this, and that therefore would be premature for IETF to publish
this as an informational RFC. Correct?

Anyhow - I think it would be appropriate to add a note clarifying that
IETF will not progress cr-ldp beyond Proposed Standard.

/Loa


Adrian Farrel wrote:
< snip >

> I would caution against progressing this draft until the referenced ITU material
> (G.7713.3) has reached consent within the ITU since to move it forward at this
> stage as an informational RFC might be misleading.
> 

-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se





From owner-ietf@ietf.org  Wed Jan  8 13:17:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00504;
	Wed, 8 Jan 2003 13:17:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WKI6-0000xP-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 12:46:58 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WJxO-00045R-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 12:25:34 -0500
Received: from atlntex01.movaz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25915;
	Wed, 8 Jan 2003 12:17:01 -0500 (EST)
Received: from BLIULAPTOP ([172.16.24.104]) by atlntex01.movaz.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 8 Jan 2003 12:20:11 -0500
Message-ID: <072601c2b73a$332fc4f0$681810ac@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: "Loa Andersson" <loa@pi.se>
Cc: <iesg@ietf.org>, "Osama Aboul-Magd" <osama@nortelnetworks.com>,
        <ietf@ietf.org>
References: <28F05913385EAC43AF019413F674A01704A175C6@OCCLUST04EVS1.ugd.att.com> <023601c2b2a0$c82a44c0$681810ac@movaz.com> <3E1C556F.2040704@pi.se>
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Date: Wed, 8 Jan 2003 12:20:11 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
X-OriginalArrivalTime: 08 Jan 2003 17:20:11.0513 (UTC) FILETIME=[33389E90:01C2B73A]
Sender: owner-ietf@ietf.org
Precedence: bulk

> trying to understand what you are saying - it seems like you are
> implying that there is no consensus with in ITU on how to progress
> this, and that therefore would be premature for IETF to publish
> this as an informational RFC. Correct?

I'm not quite saying that.
I am saying that it sounds to me from the discussion that the ITU has not yet
reached consent. It seemed to me that if the draft is intended to document the
ITU preferences as informational, it would be as well to wait until the ITU has
fully signed off. I don't see any rush for this.

> Anyhow - I think it would be appropriate to add a note clarifying that
> IETF will not progress cr-ldp beyond Proposed Standard.

Adrian





From owner-ietf@ietf.org  Wed Jan  8 13:25:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00829;
	Wed, 8 Jan 2003 13:25:05 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WKIL-00012A-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 12:47:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WK3S-0006O8-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 12:31:50 -0500
Received: from mailb.telia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26667;
	Wed, 8 Jan 2003 12:23:15 -0500 (EST)
Received: from d1o888.telia.com (d1o888.telia.com [213.67.172.241])
	by mailb.telia.com (8.12.5/8.12.5) with ESMTP id h08HQTCn005688;
	Wed, 8 Jan 2003 18:26:30 +0100 (CET)
X-Original-Recipient: iesg@ietf.org
Received: from pi.se (h70n2fls31o888.telia.com [213.64.120.70])
	by d1o888.telia.com (8.10.2/8.10.1) with ESMTP id h08HQT226299;
	Wed, 8 Jan 2003 18:26:29 +0100 (CET)
Message-ID: <3E1C5E67.2040603@pi.se>
Date: Wed, 08 Jan 2003 18:22:47 +0100
From: Loa Andersson <loa@pi.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Adrian Farrel <afarrel@movaz.com>
CC: iesg@ietf.org, Osama Aboul-Magd <osama@nortelnetworks.com>, ietf@ietf.org
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
References: <28F05913385EAC43AF019413F674A01704A175C6@OCCLUST04EVS1.ugd.att.com> <023601c2b2a0$c82a44c0$681810ac@movaz.com> <3E1C556F.2040704@pi.se> <072601c2b73a$332fc4f0$681810ac@movaz.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

Adrian,


Adrian Farrel wrote:
>>trying to understand what you are saying - it seems like you are
>>implying that there is no consensus with in ITU on how to progress
>>this, and that therefore would be premature for IETF to publish
>>this as an informational RFC. Correct?
> 
> 
> I'm not quite saying that.
> I am saying that it sounds to me from the discussion that the ITU has not yet
> reached consent. It seemed to me that if the draft is intended to document the
> ITU preferences as informational, it would be as well to wait until the ITU has
> fully signed off. I don't see any rush for this.

ok - I can see the difference - and it seems that you are correct. If
the ITU discussion still has some way to go before the discussion
settles and the preferences better known - wouldn't it be appropriate to 
wait until this happens?

Osama, care to comment?

/Loa

> 
> 
>>Anyhow - I think it would be appropriate to add a note clarifying that
>>IETF will not progress cr-ldp beyond Proposed Standard.
> 
> 
> Adrian
> 
> 
> 
> 


-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se





From owner-ietf@ietf.org  Wed Jan  8 13:55:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02025;
	Wed, 8 Jan 2003 13:55:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WKuM-00020m-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 13:26:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WKhp-000052-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 13:13:33 -0500
Received: from dot-god.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29900
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:05:00 -0500 (EST)
Received: from localhost (baptista@localhost)
	by dot-god.com (8.11.4/8.11.4) with ESMTP id h08I8C230465
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:08:12 -0500
Date: Wed, 8 Jan 2003 13:08:12 -0500 (EST)
From: Joe Baptista <baptista@dot-god.com>
To: <ietf@ietf.org>
Subject: SWAMP SPACE 192/8 thru 205/8
Message-ID: <Pine.LNX.4.33.0301081307300.25474-100000@dot-god.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


I understand swamp space is 192/8 thru 205/8.  Am I correct.  Also can
anyone provide me with a history of how these allocation got that name
??? swamp space ???

Thanks in advance.

Cheers
Joe Baptista

--
Planet Communications & Computing Facility
a division of The dot.GOD Registry, Limited






From owner-ietf@ietf.org  Wed Jan  8 14:10:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00133;
	Wed, 8 Jan 2003 13:11:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WKGa-0000Zp-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 12:45:24 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WHeR-0002LA-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 09:57:53 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21391
	for <ietf@ietf.org>; Wed, 8 Jan 2003 09:49:01 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h08EplRA010100;
	Wed, 8 Jan 2003 09:51:47 -0500
Message-Id: <200301081451.h08EplRA010100@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Bill Cunningham <billc44@citynet.net>
Cc: ietf@ietf.org
In-Reply-To: Your message of "Wed, 08 Jan 2003 01:46:50 EST."
             <003b01c2b6e1$bc8f4d00$f944903f@a> 
References: <003b01c2b6e1$bc8f4d00$f944903f@a>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1080810820P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 08 Jan 2003 09:51:47 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Wed, 08 Jan 2003 01:46:50 EST, Bill Cunningham <billc44@citynet.net>  said:
> Who does the real IE work in the Internet world? Is it the IESG or IAB?

That's what working groups are for.

> Seems like there's more arguing on this list than anything else.

You haven't been here long, have you? ;)


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

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

iD8DBQE+HDsCcC3lWbTT17ARAvc9AKDbTH7V6pp7vxp4oZjVrVpx49c13ACgvtzG
22TEu5NFN7ZeOhMETmd9VNI=
=X5N+
-----END PGP SIGNATURE-----

--==_Exmh_1080810820P--



From owner-ietf@ietf.org  Wed Jan  8 14:09:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02505;
	Wed, 8 Jan 2003 14:09:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WLDB-0003f1-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 13:45:57 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WL4B-00032P-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 13:36:46 -0500
Received: from b.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00992
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:27:47 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: (qmail 8313 invoked from network); 8 Jan 2003 18:31:03 -0000
Received: from sub.sonic.net (208.201.224.8)
  by b.smtp-out.sonic.net with SMTP; 8 Jan 2003 18:31:03 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h08IV3i10593;
	Wed, 8 Jan 2003 10:31:03 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 10:30:54 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-103053-1662.MMD@SonomaDesign.com; Wed, 8 Jan 2003 10:30:53 -0800
Received: by sub.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 10:31:02 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 10:30:28 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id h08IUIe09811;
	Wed, 8 Jan 2003 10:30:19 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WKGa-0000Zp-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 12:45:24 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WHeR-0002LA-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 09:57:53 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21391
	for <ietf@ietf.org>; Wed, 8 Jan 2003 09:49:01 -0500 (EST)
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h08EplRA010100;
	Wed, 8 Jan 2003 09:51:47 -0500
Message-Id: <200301081451.h08EplRA010100@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Bill Cunningham <billc44@citynet.net>
Cc: ietf@ietf.org
In-Reply-To: Your message of "Wed, 08 Jan 2003 01:46:50 EST."
             <003b01c2b6e1$bc8f4d00$f944903f@a> 
References: <003b01c2b6e1$bc8f4d00$f944903f@a>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1080810820P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 08 Jan 2003 09:51:47 -0500
X-OriginalArrivalTime: 08 Jan 2003 18:30:54.0620 (UTC) FILETIME=[144F5DC0:01C2B744]
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Wed, 08 Jan 2003 01:46:50 EST, Bill Cunningham <billc44@citynet.net>  said:
> Who does the real IE work in the Internet world? Is it the IESG or IAB?

That's what working groups are for.

> Seems like there's more arguing on this list than anything else.

You haven't been here long, have you? ;)


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

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

iD8DBQE+HDsCcC3lWbTT17ARAvc9AKDbTH7V6pp7vxp4oZjVrVpx49c13ACgvtzG
22TEu5NFN7ZeOhMETmd9VNI=
=X5N+
-----END PGP SIGNATURE-----

--==_Exmh_1080810820P--




From owner-ietf@ietf.org  Wed Jan  8 14:48:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04118;
	Wed, 8 Jan 2003 14:47:56 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WLN7-0004QW-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 13:56:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WLIV-000454-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 13:51:34 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA01657
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:42:50 -0500 (EST)
Received: (qmail 19582 invoked from network); 8 Jan 2003 18:46:06 -0000
Received: from sub.sonic.net (208.201.224.8)
  by a.smtp-out.sonic.net with SMTP; 8 Jan 2003 18:46:06 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h08Ik5i21864;
	Wed, 8 Jan 2003 10:46:05 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 10:45:57 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-104553-1665.MMD@SonomaDesign.com; Wed, 8 Jan 2003 10:45:53 -0800
Received: by ultra.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 10:46:02 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 10:35:14 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by tempest.sonic.net (8.11.6/8.8.5) with ESMTP id h08IZ1j09555;
	Wed, 8 Jan 2003 10:35:02 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WKIL-00012A-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 12:47:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WK3S-0006O8-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 12:31:50 -0500
Received: from mailb.telia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26667;
	Wed, 8 Jan 2003 12:23:15 -0500 (EST)
Received: from d1o888.telia.com (d1o888.telia.com [213.67.172.241])
	by mailb.telia.com (8.12.5/8.12.5) with ESMTP id h08HQTCn005688;
	Wed, 8 Jan 2003 18:26:30 +0100 (CET)
X-Original-Recipient: iesg@ietf.org
Received: from pi.se (h70n2fls31o888.telia.com [213.64.120.70])
	by d1o888.telia.com (8.10.2/8.10.1) with ESMTP id h08HQT226299;
	Wed, 8 Jan 2003 18:26:29 +0100 (CET)
Message-ID: <3E1C5E67.2040603@pi.se>
Date: Wed, 08 Jan 2003 18:22:47 +0100
From: Loa Andersson <loa@pi.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Adrian Farrel <afarrel@movaz.com>
CC: iesg@ietf.org, Osama Aboul-Magd <osama@nortelnetworks.com>, ietf@ietf.org
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
References: <28F05913385EAC43AF019413F674A01704A175C6@OCCLUST04EVS1.ugd.att.com> <023601c2b2a0$c82a44c0$681810ac@movaz.com> <3E1C556F.2040704@pi.se> <072601c2b73a$332fc4f0$681810ac@movaz.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Jan 2003 18:45:57.0151 (UTC) FILETIME=[2E42AAF0:01C2B746]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Adrian,


Adrian Farrel wrote:
>>trying to understand what you are saying - it seems like you are
>>implying that there is no consensus with in ITU on how to progress
>>this, and that therefore would be premature for IETF to publish
>>this as an informational RFC. Correct?
> 
> 
> I'm not quite saying that.
> I am saying that it sounds to me from the discussion that the ITU has not yet
> reached consent. It seemed to me that if the draft is intended to document the
> ITU preferences as informational, it would be as well to wait until the ITU has
> fully signed off. I don't see any rush for this.

ok - I can see the difference - and it seems that you are correct. If
the ITU discussion still has some way to go before the discussion
settles and the preferences better known - wouldn't it be appropriate to 
wait until this happens?

Osama, care to comment?

/Loa

> 
> 
>>Anyhow - I think it would be appropriate to add a note clarifying that
>>IETF will not progress cr-ldp beyond Proposed Standard.
> 
> 
> Adrian
> 
> 
> 
> 


-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se






From owner-ietf@ietf.org  Wed Jan  8 15:00:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04775;
	Wed, 8 Jan 2003 15:00:29 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WLN9-0004Qm-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 13:56:15 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WLIb-00045A-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 13:51:33 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA01665
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:42:50 -0500 (EST)
Received: (qmail 19601 invoked from network); 8 Jan 2003 18:46:06 -0000
Received: from sub.sonic.net (208.201.224.8)
  by a.smtp-out.sonic.net with SMTP; 8 Jan 2003 18:46:06 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h08Ik6i21883;
	Wed, 8 Jan 2003 10:46:06 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 10:45:57 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-104556-1668.MMD@SonomaDesign.com; Wed, 8 Jan 2003 10:45:56 -0800
Received: by ultra.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 10:46:04 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 10:39:15 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id h08IdEe28447;
	Wed, 8 Jan 2003 10:39:14 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WKI6-0000xP-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 12:46:58 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WJxO-00045R-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 12:25:34 -0500
Received: from atlntex01.movaz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25915;
	Wed, 8 Jan 2003 12:17:01 -0500 (EST)
Received: from BLIULAPTOP ([172.16.24.104]) by atlntex01.movaz.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 8 Jan 2003 12:20:11 -0500
Message-ID: <072601c2b73a$332fc4f0$681810ac@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: "Loa Andersson" <loa@pi.se>
Cc: <iesg@ietf.org>, "Osama Aboul-Magd" <osama@nortelnetworks.com>,
        <ietf@ietf.org>
References: <28F05913385EAC43AF019413F674A01704A175C6@OCCLUST04EVS1.ugd.att.com> <023601c2b2a0$c82a44c0$681810ac@movaz.com> <3E1C556F.2040704@pi.se>
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Date: Wed, 8 Jan 2003 12:20:11 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
X-OriginalArrivalTime: 08 Jan 2003 17:20:11.0513 (UTC) FILETIME=[33389E90:01C2B73A]
Sender: owner-ietf@ietf.org
Precedence: bulk

> trying to understand what you are saying - it seems like you are
> implying that there is no consensus with in ITU on how to progress
> this, and that therefore would be premature for IETF to publish
> this as an informational RFC. Correct?

I'm not quite saying that.
I am saying that it sounds to me from the discussion that the ITU has not yet
reached consent. It seemed to me that if the draft is intended to document the
ITU preferences as informational, it would be as well to wait until the ITU has
fully signed off. I don't see any rush for this.

> Anyhow - I think it would be appropriate to add a note clarifying that
> IETF will not progress cr-ldp beyond Proposed Standard.

Adrian






From owner-ietf@ietf.org  Wed Jan  8 15:04:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04910;
	Wed, 8 Jan 2003 15:02:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WLN8-0004Qd-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 13:56:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WLIX-000455-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 13:51:31 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA01662
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:42:50 -0500 (EST)
Received: (qmail 19590 invoked from network); 8 Jan 2003 18:46:06 -0000
Received: from sub.sonic.net (208.201.224.8)
  by a.smtp-out.sonic.net with SMTP; 8 Jan 2003 18:46:06 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h08Ik6i21879;
	Wed, 8 Jan 2003 10:46:06 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 10:45:57 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-104554-1666.MMD@SonomaDesign.com; Wed, 8 Jan 2003 10:45:54 -0800
Received: by ultra.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 10:46:02 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 10:38:58 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by prop.sonic.net (8.11.6/8.8.5) with ESMTP id h08IcsE17739;
	Wed, 8 Jan 2003 10:38:55 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WKGo-0000lf-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 12:45:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WJSj-0004g1-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 11:54:00 -0500
Received: from maile.telia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24513;
	Wed, 8 Jan 2003 11:45:00 -0500 (EST)
Received: from d1o888.telia.com (d1o888.telia.com [213.67.172.241])
	by maile.telia.com (8.12.5/8.12.5) with ESMTP id h08GmFaA003019;
	Wed, 8 Jan 2003 17:48:15 +0100 (CET)
X-Original-Recipient: iesg@ietf.org
Received: from pi.se (h70n2fls31o888.telia.com [213.64.120.70])
	by d1o888.telia.com (8.10.2/8.10.1) with ESMTP id h08GmE209693;
	Wed, 8 Jan 2003 17:48:14 +0100 (CET)
Message-ID: <3E1C556F.2040704@pi.se>
Date: Wed, 08 Jan 2003 17:44:31 +0100
From: Loa Andersson <loa@pi.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Adrian Farrel <afarrel@movaz.com>
CC: iesg@ietf.org, Osama Aboul-Magd <osama@nortelnetworks.com>, ietf@ietf.org
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
References: <28F05913385EAC43AF019413F674A01704A175C6@OCCLUST04EVS1.ugd.att.com> <023601c2b2a0$c82a44c0$681810ac@movaz.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Jan 2003 18:45:57.0182 (UTC) FILETIME=[2E4765E0:01C2B746]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Adrian,

trying to understand what you are saying - it seems like you are
implying that there is no consensus with in ITU on how to progress
this, and that therefore would be premature for IETF to publish
this as an informational RFC. Correct?

Anyhow - I think it would be appropriate to add a note clarifying that
IETF will not progress cr-ldp beyond Proposed Standard.

/Loa


Adrian Farrel wrote:
< snip >

> I would caution against progressing this draft until the referenced ITU material
> (G.7713.3) has reached consent within the ITU since to move it forward at this
> stage as an informational RFC might be misleading.
> 

-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se






From owner-ietf@ietf.org  Wed Jan  8 16:01:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07155;
	Wed, 8 Jan 2003 16:00:48 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WLgU-0005qj-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 14:16:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WLZo-0005ET-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 14:09:21 -0500
Received: from hosting.altserver.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02199
	for <ietf@ietf.org>; Wed, 8 Jan 2003 14:00:25 -0500 (EST)
Received: from lns15v-6-219.w.club-internet.fr ([212.195.197.219] helo=mine.utel.net)
	by hosting.altserver.com with esmtp (Exim 3.36 #1)
	id 18WLUI-0003Vh-00
	for ietf@ietf.org; Wed, 08 Jan 2003 11:03:39 -0800
Message-Id: <5.1.0.14.0.20030108200752.032f81e0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 08 Jan 2003 20:08:29 +0100
To: ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: FW: Please recant or appologize to Jim Flemming
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-36D36B12; boundary="=======34D24FD8======="
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - hosting.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - utel.net
Sender: owner-ietf@ietf.org
Precedence: bulk

--=======34D24FD8=======
Content-Type: text/plain; x-avg-checked=avg-ok-36D36B12; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit

Are others receiveing mails twice on this list?

BTW I suggest you make some more home work on Jeff. As an IETF scientist. 
Assume what Jeff says is true and try to understand how that can be. The 
brain behind is  cute and consistent. He certainly enjoys the fun of the 
litterature and FAQs on him ... since he actually wrote/writes parts of it 
:-).
jfc


On 06:46 08/01/03, Joe Baptista said:
>On Wed, 8 Jan 2003, Franck Martin wrote:
> > http://www.dnso.org/clubpublic/ga/Arc10/msg01532.html
>
>The interesting thing about Jeff Williams is that he could be anyone.
>Maybe a soviet spy whos still out in the cold.  Or a U.S. government
>agent living in a missile sile somewhere in Kansas - or is that Texas.
>Who knows.  To date many members of the press have quoted Jeff
>extensively.  And I have yet to see any of those members of the press
>correct their copy when these claims that he is a fiction are made to
>them.  They check their fact - don't they?
>
>Obviously he must be for real - the press would not lead us astray
>claiming him to be a expert without verifiable proof.  Or would they?
>hmmm?
>
>The one thing I do know about Jeff Williams.  If he is a fiction - the man
>is abviously a genious having imposed himself far and wide fooling even
>the press showing us that reporters are fools to be had.  If he is for
>real - well the press already considers him an expert in the field so
>there's no contest there.
>
>cheers
>joe baptista
>
>
>
>
>
>
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.427 / Virus Database: 240 - Release Date: 06/12/02

--=======34D24FD8=======--




From owner-ietf@ietf.org  Wed Jan  8 16:26:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07874;
	Wed, 8 Jan 2003 16:26:24 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WLqv-0006dF-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 14:27:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WLln-0006Bw-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 14:21:49 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA02716
	for <ietf@ietf.org>; Wed, 8 Jan 2003 14:12:50 -0500 (EST)
Received: (qmail 23804 invoked from network); 8 Jan 2003 19:16:06 -0000
Received: from ultra.sonic.net (208.201.224.22)
  by a.smtp-out.sonic.net with SMTP; 8 Jan 2003 19:16:06 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id h08JG6C01670
	for <ietf@ietf.org>; Wed, 8 Jan 2003 11:16:06 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 11:15:57 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-111553-1681.MMD@SonomaDesign.com; Wed, 8 Jan 2003 11:15:53 -0800
Received: by prop.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 11:16:01 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 11:05:07 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by prop.sonic.net (8.11.6/8.8.5) with ESMTP id h08J4r507643;
	Wed, 8 Jan 2003 11:04:55 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WKuM-00020m-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 13:26:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WKhp-000052-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 13:13:33 -0500
Received: from dot-god.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29900
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:05:00 -0500 (EST)
Received: from localhost (baptista@localhost)
	by dot-god.com (8.11.4/8.11.4) with ESMTP id h08I8C230465
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:08:12 -0500
Date: Wed, 8 Jan 2003 13:08:12 -0500 (EST)
From: Joe Baptista <baptista@dot-god.com>
To: <ietf@ietf.org>
Subject: SWAMP SPACE 192/8 thru 205/8
Message-ID: <Pine.LNX.4.33.0301081307300.25474-100000@dot-god.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 08 Jan 2003 19:15:57.0666 (UTC) FILETIME=[5F737420:01C2B74A]
Sender: owner-ietf@ietf.org
Precedence: bulk


I understand swamp space is 192/8 thru 205/8.  Am I correct.  Also can
anyone provide me with a history of how these allocation got that name
??? swamp space ???

Thanks in advance.

Cheers
Joe Baptista

--
Planet Communications & Computing Facility
a division of The dot.GOD Registry, Limited







From owner-ietf@ietf.org  Wed Jan  8 16:52:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09168;
	Wed, 8 Jan 2003 16:52:05 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WN5r-00059s-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 15:46:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WN3J-00050N-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 15:43:54 -0500
Received: from boreas.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06378
	for <ietf@ietf.org>; Wed, 8 Jan 2003 15:35:06 -0500 (EST)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6/8.11.2) id h08Kc5o22640;
	Wed, 8 Jan 2003 12:38:05 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200301082038.h08Kc5o22640@boreas.isi.edu>
Subject: Re: SWAMP SPACE 192/8 thru 205/8
In-Reply-To: <Pine.LNX.4.33.0301081307300.25474-100000@dot-god.com> from Joe Baptista at "Jan 8, 3 01:08:12 pm"
To: baptista@dot-god.com (Joe Baptista)
Date: Wed, 8 Jan 2003 12:38:05 -0800 (PST)
Cc: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

% 
% I understand swamp space is 192/8 thru 205/8.  Am I correct.  Also can
% anyone provide me with a history of how these allocation got that name
% ??? swamp space ???
% 
% Thanks in advance.
% 
% Cheers
% Joe Baptista
% 
% --
% Planet Communications & Computing Facility
% a division of The dot.GOD Registry, Limited

	the definition is one of local interpretation, per ISP.
	So if you define "swamp space" as 192/8 thru 205/8, then
	you are accurate, as far as you are concerned. Others will
	have divergent views and definitions.

	the term came into use roughly the same time as the term
	"tier-x" emerged as a classification for ISPs.
	
	Check the CIDR wg archives and the NANOG mailing archives
	roughly 1996-1998 for more detail.


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



From owner-ietf@ietf.org  Wed Jan  8 17:04:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09485;
	Wed, 8 Jan 2003 17:04:46 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WNM5-000652-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 16:03:17 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WNIY-0005r2-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 15:59:40 -0500
Received: from kcmso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06779;
	Wed, 8 Jan 2003 15:50:52 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h08KmOxQ013460;
	Wed, 8 Jan 2003 14:54:08 -0600 (CST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E00F131AE; Wed, 8 Jan 2003 15:53:59 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Date: Wed, 8 Jan 2003 15:47:33 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704A17601@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Thread-Index: AcK3Q9VYNioMJmMqRGi6msBPb8SUfAABzSvA
From: "Ash, Gerald R (Jerry), ALASO" <gash@att.com>
To: "Loa Andersson" <loa@pi.se>, "Adrian Farrel" <afarrel@movaz.com>
Cc: "Ash, Gerald R (Jerry), ALASO" <gash@att.com>, <iesg@ietf.org>,
        "Osama Aboul-Magd" <osama@nortelnetworks.com>, <ietf@ietf.org>,
        "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>, <hklam@lucent.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA09485

Adrian> I am saying that it sounds to me from the discussion that 
Adrian> the ITU has not yet reached consent. It seemed to me that 
Adrian> if the draft is intended to document the ITU preferences as 
Adrian> informational, it would be as well to wait until the ITU has
Adrian> fully signed off. I don't see any rush for this.

Loa> ok - I can see the difference - and it seems that you are correct. If
Loa> the ITU discussion still has some way to go before the discussion
Loa> settles and the preferences better known - wouldn't it be 
Loa> appropriate to wait until this happens?

ASON Signaling Recommendations G.7713.2 (GMPLS RSVP-TE) and G.7713.3 (GMPLS CR-LDP) are proposed for consent at the upcoming SG15 meeting, 20-31 January (Geneva).  A Liaison was sent to the IETF containing Recommendation text, but I can't find it on http://www.ietf.org/IESG/LIAISON/.

Both documents propose detailed protocol specifications including new TLVs (e.g., crankback TLV in G.7713.3).  The intent of these Recommendations is unclear.  

If these are statements of 'ITU preferences/requirements' which are made known to the IETF through the Informational RFCs, such as Osama's and Zhi's, then fine.  IETF can then take up the 'preferences/requirements' and consider them for upgrading RSVP-TE and CR-LDP protocols (although CR-LDP is capped).  

However, if they are intended as alternative protocol specs competing with the IETF specs, then that's a problem.  Which spec does a vendor implement and an operator use, given interoperability needs, etc.?  It would be analogous to the IETF specifying their version of G.709.

A clarification of the intent of these Recs. would be helpful.

Jerry Ash




From owner-ietf@ietf.org  Wed Jan  8 17:27:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09965;
	Wed, 8 Jan 2003 17:27:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WNn7-0007iH-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 16:31:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WNdl-0007I7-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 16:21:37 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA07523
	for <ietf@ietf.org>; Wed, 8 Jan 2003 16:12:47 -0500 (EST)
Received: (qmail 8737 invoked from network); 8 Jan 2003 21:16:03 -0000
Received: from tempest.sonic.net (208.201.224.25)
  by a.smtp-out.sonic.net with SMTP; 8 Jan 2003 21:16:03 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by tempest.sonic.net (8.11.6/8.8.5) with ESMTP id h08LG3502950
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:16:03 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 13:15:54 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-131553-1734.MMD@SonomaDesign.com; Wed, 8 Jan 2003 13:15:53 -0800
Received: by prop.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 13:16:02 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 13:11:43 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by tempest.sonic.net (8.11.6/8.8.5) with ESMTP id h08LBW501350;
	Wed, 8 Jan 2003 13:11:36 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WLgU-0005qj-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 14:16:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WLZo-0005ET-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 14:09:21 -0500
Received: from hosting.altserver.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02199
	for <ietf@ietf.org>; Wed, 8 Jan 2003 14:00:25 -0500 (EST)
Received: from lns15v-6-219.w.club-internet.fr ([212.195.197.219] helo=mine.utel.net)
	by hosting.altserver.com with esmtp (Exim 3.36 #1)
	id 18WLUI-0003Vh-00
	for ietf@ietf.org; Wed, 08 Jan 2003 11:03:39 -0800
Message-Id: <5.1.0.14.0.20030108200752.032f81e0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 08 Jan 2003 20:08:29 +0100
To: ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: FW: Please recant or appologize to Jim Flemming
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-36D36B12; boundary="=======34D24FD8======="
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - hosting.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - utel.net
X-OriginalArrivalTime: 08 Jan 2003 21:15:54.0276 (UTC) FILETIME=[20F6FE40:01C2B75B]
Sender: owner-ietf@ietf.org
Precedence: bulk

--=======34D24FD8=======
Content-Type: text/plain; x-avg-checked=avg-ok-36D36B12; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit

Are others receiveing mails twice on this list?

BTW I suggest you make some more home work on Jeff. As an IETF scientist. 
Assume what Jeff says is true and try to understand how that can be. The 
brain behind is  cute and consistent. He certainly enjoys the fun of the 
litterature and FAQs on him ... since he actually wrote/writes parts of it 
:-).
jfc


On 06:46 08/01/03, Joe Baptista said:
>On Wed, 8 Jan 2003, Franck Martin wrote:
> > http://www.dnso.org/clubpublic/ga/Arc10/msg01532.html
>
>The interesting thing about Jeff Williams is that he could be anyone.
>Maybe a soviet spy whos still out in the cold.  Or a U.S. government
>agent living in a missile sile somewhere in Kansas - or is that Texas.
>Who knows.  To date many members of the press have quoted Jeff
>extensively.  And I have yet to see any of those members of the press
>correct their copy when these claims that he is a fiction are made to
>them.  They check their fact - don't they?
>
>Obviously he must be for real - the press would not lead us astray
>claiming him to be a expert without verifiable proof.  Or would they?
>hmmm?
>
>The one thing I do know about Jeff Williams.  If he is a fiction - the man
>is abviously a genious having imposed himself far and wide fooling even
>the press showing us that reporters are fools to be had.  If he is for
>real - well the press already considers him an expert in the field so
>there's no contest there.
>
>cheers
>joe baptista
>
>
>
>
>
>
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.427 / Virus Database: 240 - Release Date: 06/12/02

--=======34D24FD8=======--





From owner-ietf@ietf.org  Wed Jan  8 17:40:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10761;
	Wed, 8 Jan 2003 17:40:20 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WOCC-0001MH-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 16:57:08 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WO9S-0001AS-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 16:54:19 -0500
Received: from iserver.sj.symbol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08883
	for <ietf@ietf.org>; Wed, 8 Jan 2003 16:45:36 -0500 (EST)
Received: from gwianameserver.sj.symbol.com (symsjdmz.sj.symbol.com [63.145.233.50])
	by iserver.sj.symbol.com (8.12.2/8.12.2) with SMTP id h08LjaqQ016710
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:45:36 -0800 (PST)
Received: from SJ-DOM-Message_Server by gwianameserver.sj.symbol.com
	with Novell_GroupWise; Wed, 08 Jan 2003 13:48:52 -0800
Message-Id: <se1c2c44.030@gwianameserver.sj.symbol.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.7.1 Beta
Date: Wed, 08 Jan 2003 13:48:40 -0800
From: "Clint Chaplin" <cchaplin@sj.symbol.com>
To: <ietf@ietf.org>, <info@utel.net>
Subject: Re: FW: Please recant or appologize to Jim Flemming
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA10761

I too have been receiving mails twice from this list.  The duplicate mails seem to be about ½ to 1 hour apart.

Clint (JOATMON) Chaplin

>>> jfcm <info@utel.net> 1/8/03 11:08:29 >>>
Are others receiveing mails twice on this list?

BTW I suggest you make some more home work on Jeff. As an IETF scientist. 
Assume what Jeff says is true and try to understand how that can be. The 
brain behind is  cute and consistent. He certainly enjoys the fun of the 
litterature and FAQs on him ... since he actually wrote/writes parts of it 
:-).
jfc


On 06:46 08/01/03, Joe Baptista said:
>On Wed, 8 Jan 2003, Franck Martin wrote:
> > http://www.dnso.org/clubpublic/ga/Arc10/msg01532.html 
>
>The interesting thing about Jeff Williams is that he could be anyone.
>Maybe a soviet spy whos still out in the cold.  Or a U.S. government
>agent living in a missile sile somewhere in Kansas - or is that Texas.
>Who knows.  To date many members of the press have quoted Jeff
>extensively.  And I have yet to see any of those members of the press
>correct their copy when these claims that he is a fiction are made to
>them.  They check their fact - don't they?
>
>Obviously he must be for real - the press would not lead us astray
>claiming him to be a expert without verifiable proof.  Or would they?
>hmmm?
>
>The one thing I do know about Jeff Williams.  If he is a fiction - the man
>is abviously a genious having imposed himself far and wide fooling even
>the press showing us that reporters are fools to be had.  If he is for
>real - well the press already considers him an expert in the field so
>there's no contest there.
>
>cheers
>joe baptista
>
>
>
>
>
>
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.427 / Virus Database: 240 - Release Date: 06/12/02




From owner-ietf@ietf.org  Wed Jan  8 17:41:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10803;
	Wed, 8 Jan 2003 17:40:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WOOI-0002TZ-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 17:09:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WOLX-0002Ak-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 17:06:54 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA09354
	for <ietf@ietf.org>; Wed, 8 Jan 2003 16:57:51 -0500 (EST)
Received: (qmail 16649 invoked from network); 8 Jan 2003 22:01:07 -0000
Received: from turbo.sonic.net (208.201.224.26)
  by a.smtp-out.sonic.net with SMTP; 8 Jan 2003 22:01:07 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h08M17U01095;
	Wed, 8 Jan 2003 14:01:07 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 14:00:58 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-140057-1753.MMD@SonomaDesign.com; Wed, 8 Jan 2003 14:00:57 -0800
Received: by sub.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 14:01:06 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 14:00:39 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id h08M0S020710;
	Wed, 8 Jan 2003 14:00:31 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WN5r-00059s-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 15:46:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WN3J-00050N-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 15:43:54 -0500
Received: from boreas.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06378
	for <ietf@ietf.org>; Wed, 8 Jan 2003 15:35:06 -0500 (EST)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6/8.11.2) id h08Kc5o22640;
	Wed, 8 Jan 2003 12:38:05 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200301082038.h08Kc5o22640@boreas.isi.edu>
Subject: Re: SWAMP SPACE 192/8 thru 205/8
In-Reply-To: <Pine.LNX.4.33.0301081307300.25474-100000@dot-god.com> from Joe Baptista at "Jan 8, 3 01:08:12 pm"
To: baptista@dot-god.com (Joe Baptista)
Date: Wed, 8 Jan 2003 12:38:05 -0800 (PST)
Cc: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Jan 2003 22:00:58.0088 (UTC) FILETIME=[6C8FF680:01C2B761]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

% 
% I understand swamp space is 192/8 thru 205/8.  Am I correct.  Also can
% anyone provide me with a history of how these allocation got that name
% ??? swamp space ???
% 
% Thanks in advance.
% 
% Cheers
% Joe Baptista
% 
% --
% Planet Communications & Computing Facility
% a division of The dot.GOD Registry, Limited

	the definition is one of local interpretation, per ISP.
	So if you define "swamp space" as 192/8 thru 205/8, then
	you are accurate, as far as you are concerned. Others will
	have divergent views and definitions.

	the term came into use roughly the same time as the term
	"tier-x" emerged as a classification for ISPs.
	
	Check the CIDR wg archives and the NANOG mailing archives
	roughly 1996-1998 for more detail.


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




From owner-ietf@ietf.org  Wed Jan  8 17:58:07 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11758;
	Wed, 8 Jan 2003 17:57:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WOdY-0003bJ-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 17:25:24 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WOZz-0003K4-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 17:22:09 -0500
Received: from b.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA09685
	for <ietf@ietf.org>; Wed, 8 Jan 2003 17:12:49 -0500 (EST)
Received: (qmail 9329 invoked from network); 8 Jan 2003 22:16:05 -0000
Received: from tempest.sonic.net (208.201.224.25)
  by b.smtp-out.sonic.net with SMTP; 8 Jan 2003 22:16:05 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by tempest.sonic.net (8.11.6/8.8.5) with ESMTP id h08MG4T24793;
	Wed, 8 Jan 2003 14:16:04 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 14:15:55 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-141554-1760.MMD@SonomaDesign.com; Wed, 8 Jan 2003 14:15:54 -0800
Received: by turbo.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 14:16:03 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 14:14:07 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h08MDwK27670;
	Wed, 8 Jan 2003 14:14:00 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WNM5-000652-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 16:03:17 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WNIY-0005r2-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 15:59:40 -0500
Received: from kcmso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06779;
	Wed, 8 Jan 2003 15:50:52 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h08KmOxQ013460;
	Wed, 8 Jan 2003 14:54:08 -0600 (CST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E00F131AE; Wed, 8 Jan 2003 15:53:59 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Date: Wed, 8 Jan 2003 15:47:33 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704A17601@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Thread-Index: AcK3Q9VYNioMJmMqRGi6msBPb8SUfAABzSvA
From: "Ash, Gerald R (Jerry), ALASO" <gash@att.com>
To: "Loa Andersson" <loa@pi.se>, "Adrian Farrel" <afarrel@movaz.com>
Cc: "Ash, Gerald R (Jerry), ALASO" <gash@att.com>, <iesg@ietf.org>,
        "Osama Aboul-Magd" <osama@nortelnetworks.com>, <ietf@ietf.org>,
        "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>, <hklam@lucent.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by turbo.sonic.net id h08MDwK27670
X-OriginalArrivalTime: 08 Jan 2003 22:15:55.0745 (UTC) FILETIME=[839B8D10:01C2B763]
Content-Transfer-Encoding: 8bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Adrian> I am saying that it sounds to me from the discussion that 
Adrian> the ITU has not yet reached consent. It seemed to me that 
Adrian> if the draft is intended to document the ITU preferences as 
Adrian> informational, it would be as well to wait until the ITU has
Adrian> fully signed off. I don't see any rush for this.

Loa> ok - I can see the difference - and it seems that you are correct. If
Loa> the ITU discussion still has some way to go before the discussion
Loa> settles and the preferences better known - wouldn't it be 
Loa> appropriate to wait until this happens?

ASON Signaling Recommendations G.7713.2 (GMPLS RSVP-TE) and G.7713.3 (GMPLS CR-LDP) are proposed for consent at the upcoming SG15 meeting, 20-31 January (Geneva).  A Liaison was sent to the IETF containing Recommendation text, but I can't find it on http://www.ietf.org/IESG/LIAISON/.

Both documents propose detailed protocol specifications including new TLVs (e.g., crankback TLV in G.7713.3).  The intent of these Recommendations is unclear.  

If these are statements of 'ITU preferences/requirements' which are made known to the IETF through the Informational RFCs, such as Osama's and Zhi's, then fine.  IETF can then take up the 'preferences/requirements' and consider them for upgrading RSVP-TE and CR-LDP protocols (although CR-LDP is capped).  

However, if they are intended as alternative protocol specs competing with the IETF specs, then that's a problem.  Which spec does a vendor implement and an operator use, given interoperability needs, etc.?  It would be analogous to the IETF specifying their version of G.709.

A clarification of the intent of these Recs. would be helpful.

Jerry Ash





From owner-ietf@ietf.org  Wed Jan  8 18:22:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12890;
	Wed, 8 Jan 2003 18:22:39 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WP5J-0005nn-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 17:54:05 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WP2k-0005US-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 17:51:28 -0500
Received: from dot-god.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10912
	for <ietf@ietf.org>; Wed, 8 Jan 2003 17:42:46 -0500 (EST)
Received: from localhost (baptista@localhost)
	by dot-god.com (8.11.4/8.11.4) with ESMTP id h08Mk3B12605;
	Wed, 8 Jan 2003 17:46:03 -0500
Date: Wed, 8 Jan 2003 17:46:02 -0500 (EST)
From: Joe Baptista <baptista@dot-god.com>
To: jfcm <info@utel.net>
cc: <ietf@ietf.org>
Subject: Re: FW: Please recant or appologize to Jim Flemming
In-Reply-To: <5.1.0.14.0.20030108200752.032f81e0@mail.utel.net>
Message-ID: <Pine.LNX.4.33.0301081741290.25474-100000@dot-god.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Wed, 8 Jan 2003, jfcm wrote:

> Are others receiveing mails twice on this list?
>
> BTW I suggest you make some more home work on Jeff. As an IETF scientist.
> Assume what Jeff says is true and try to understand how that can be. The
> brain behind is  cute and consistent. He certainly enjoys the fun of the
> litterature and FAQs on him ... since he actually wrote/writes parts of it
> :-).

i'm a fan.  someday i hope to meet jeff and maybe fly him down to my mars
retreat.  oops have i just said something incriminating ?

the real fools are the ones who write endless streams of devoted affection
to him.  he informed.  involved.  i've always considered him an evolved
intellectual life form - probably our first self made electronic citizen.

he certainly commands their attentions.

Cheers
Joe Baptista

--
Planet Communications & Computing Facility
a division of The dot.GOD Registry, Limited





From owner-ietf@ietf.org  Wed Jan  8 18:40:46 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13306;
	Wed, 8 Jan 2003 18:40:24 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WPKc-0007J4-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 18:09:54 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WPHW-00070M-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 18:06:51 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA11754
	for <ietf@ietf.org>; Wed, 8 Jan 2003 17:57:48 -0500 (EST)
Received: (qmail 25172 invoked from network); 8 Jan 2003 23:01:03 -0000
Received: from sub.sonic.net (208.201.224.8)
  by a.smtp-out.sonic.net with SMTP; 8 Jan 2003 23:01:03 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h08N13V00418;
	Wed, 8 Jan 2003 15:01:03 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 15:00:54 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-150053-1776.MMD@SonomaDesign.com; Wed, 8 Jan 2003 15:00:53 -0800
Received: by prop.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 15:01:02 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 14:52:23 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h08MppV27166;
	Wed, 8 Jan 2003 14:51:54 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WOCC-0001MH-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 16:57:08 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WO9S-0001AS-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 16:54:19 -0500
Received: from iserver.sj.symbol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08883
	for <ietf@ietf.org>; Wed, 8 Jan 2003 16:45:36 -0500 (EST)
Received: from gwianameserver.sj.symbol.com (symsjdmz.sj.symbol.com [63.145.233.50])
	by iserver.sj.symbol.com (8.12.2/8.12.2) with SMTP id h08LjaqQ016710
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:45:36 -0800 (PST)
Received: from SJ-DOM-Message_Server by gwianameserver.sj.symbol.com
	with Novell_GroupWise; Wed, 08 Jan 2003 13:48:52 -0800
Message-Id: <se1c2c44.030@gwianameserver.sj.symbol.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.7.1 Beta
Date: Wed, 08 Jan 2003 13:48:40 -0800
From: "Clint Chaplin" <cchaplin@sj.symbol.com>
To: <ietf@ietf.org>, <info@utel.net>
Subject: Re: FW: Please recant or appologize to Jim Flemming
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
X-MIME-Autoconverted: from quoted-printable to 8bit by sub.sonic.net id h08MppV27166
X-OriginalArrivalTime: 08 Jan 2003 23:00:54.0682 (UTC) FILETIME=[CC4CA7A0:01C2B769]
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id RAA11755
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA13306

I too have been receiving mails twice from this list.  The duplicate mails seem to be about ½ to 1 hour apart.

Clint (JOATMON) Chaplin

>>> jfcm <info@utel.net> 1/8/03 11:08:29 >>>
Are others receiveing mails twice on this list?

BTW I suggest you make some more home work on Jeff. As an IETF scientist. 
Assume what Jeff says is true and try to understand how that can be. The 
brain behind is  cute and consistent. He certainly enjoys the fun of the 
litterature and FAQs on him ... since he actually wrote/writes parts of it 
:-).
jfc


On 06:46 08/01/03, Joe Baptista said:
>On Wed, 8 Jan 2003, Franck Martin wrote:
> > http://www.dnso.org/clubpublic/ga/Arc10/msg01532.html 
>
>The interesting thing about Jeff Williams is that he could be anyone.
>Maybe a soviet spy whos still out in the cold.  Or a U.S. government
>agent living in a missile sile somewhere in Kansas - or is that Texas.
>Who knows.  To date many members of the press have quoted Jeff
>extensively.  And I have yet to see any of those members of the press
>correct their copy when these claims that he is a fiction are made to
>them.  They check their fact - don't they?
>
>Obviously he must be for real - the press would not lead us astray
>claiming him to be a expert without verifiable proof.  Or would they?
>hmmm?
>
>The one thing I do know about Jeff Williams.  If he is a fiction - the man
>is abviously a genious having imposed himself far and wide fooling even
>the press showing us that reporters are fools to be had.  If he is for
>real - well the press already considers him an expert in the field so
>there's no contest there.
>
>cheers
>joe baptista
>
>
>
>
>
>
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.427 / Virus Database: 240 - Release Date: 06/12/02





From owner-ietf@ietf.org  Wed Jan  8 18:41:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13369;
	Wed, 8 Jan 2003 18:41:19 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WPU3-00089B-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 18:19:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WPRC-0007lH-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 18:16:45 -0500
Received: from boromir.vpop.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12490
	for <ietf@ietf.org>; Wed, 8 Jan 2003 18:07:42 -0500 (EST)
Received: from [192.168.0.10] (ppp-67-118-247-209.dialup.pltn13.pacbell.net [67.118.247.209])
	by boromir.vpop.net (Postfix) with ESMTP
	id CE8B83A6320; Wed,  8 Jan 2003 15:10:53 -0800 (PST)
Mime-Version: 1.0
Message-Id: <a05111b0fba425f67bbe2@[192.168.0.10]>
In-Reply-To: <5.1.0.14.0.20030108200752.032f81e0@mail.utel.net>
References: <5.1.0.14.0.20030108200752.032f81e0@mail.utel.net>
Date: Wed, 8 Jan 2003 15:10:51 -0800
To: jfcm <info@utel.net>, ietf@ietf.org
From: Ari Ollikainen <Ari@OLTECO.com>
Subject: Re: FW: Please recant or appologize to Jim Flemming
Cc: support@sonic.net, abuse@sonic.net, dane@sonic.net
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 8:08 PM +0100 1/8/03, jfcm wrote:
>Content-Type: text/plain; x-avg-checked=avg-ok-36D36B12; charset=us-ascii; format=flowed
>Content-Transfer-Encoding: 8bit
>
>Are others receiveing mails twice on this list?
>

	Apparently someone at SonomaDesigns hosted by sonic.net
	is reflecting ALL ietf list messages back to the list:

	[an excerpt from the header of the last message received]

Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WNdl-0007I7-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 16:21:37 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA07523
	for <ietf@ietf.org>; Wed, 8 Jan 2003 16:12:47 -0500 (EST)
Received: (qmail 8737 invoked from network); 8 Jan 2003 21:16:03 -0000
Received: from tempest.sonic.net (208.201.224.25)
  by a.smtp-out.sonic.net with SMTP; 8 Jan 2003 21:16:03 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by tempest.sonic.net (8.11.6/8.8.5) with ESMTP id h08LG3502950
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:16:03 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 13:15:54 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-131553-1734.MMD@SonomaDesign.com; Wed, 8 Jan 2003 13:15:53 -0800
Received: by prop.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 13:16:02 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 13:11:43 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by tempest.sonic.net (8.11.6/8.8.5) with ESMTP id h08LBW501350;
	Wed, 8 Jan 2003 13:11:36 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WLgU-0005qj-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 14:16:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WLZo-0005ET-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 14:09:21 -0500

 

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

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



From owner-ietf@ietf.org  Wed Jan  8 19:25:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14706;
	Wed, 8 Jan 2003 19:24:49 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WQ7p-00025s-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 19:00:45 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WPzP-0001X6-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 18:52:13 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA13428
	for <ietf@ietf.org>; Wed, 8 Jan 2003 18:42:48 -0500 (EST)
Received: (qmail 31518 invoked from network); 8 Jan 2003 23:46:03 -0000
Received: from prop.sonic.net (208.201.224.193)
  by a.smtp-out.sonic.net with SMTP; 8 Jan 2003 23:46:03 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by prop.sonic.net (8.11.6/8.8.5) with ESMTP id h08Nk3h04093;
	Wed, 8 Jan 2003 15:46:03 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 15:45:54 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-154553-1793.MMD@SonomaDesign.com; Wed, 8 Jan 2003 15:45:53 -0800
Received: by ultra.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 15:46:02 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 15:32:03 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h08NVqp10188;
	Wed, 8 Jan 2003 15:31:55 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WP5J-0005nn-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 17:54:05 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WP2k-0005US-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 17:51:28 -0500
Received: from dot-god.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10912
	for <ietf@ietf.org>; Wed, 8 Jan 2003 17:42:46 -0500 (EST)
Received: from localhost (baptista@localhost)
	by dot-god.com (8.11.4/8.11.4) with ESMTP id h08Mk3B12605;
	Wed, 8 Jan 2003 17:46:03 -0500
Date: Wed, 8 Jan 2003 17:46:02 -0500 (EST)
From: Joe Baptista <baptista@dot-god.com>
To: jfcm <info@utel.net>
cc: <ietf@ietf.org>
Subject: Re: FW: Please recant or appologize to Jim Flemming
In-Reply-To: <5.1.0.14.0.20030108200752.032f81e0@mail.utel.net>
Message-ID: <Pine.LNX.4.33.0301081741290.25474-100000@dot-god.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 08 Jan 2003 23:45:54.0760 (UTC) FILETIME=[15ABDC80:01C2B770]
Sender: owner-ietf@ietf.org
Precedence: bulk


On Wed, 8 Jan 2003, jfcm wrote:

> Are others receiveing mails twice on this list?
>
> BTW I suggest you make some more home work on Jeff. As an IETF scientist.
> Assume what Jeff says is true and try to understand how that can be. The
> brain behind is  cute and consistent. He certainly enjoys the fun of the
> litterature and FAQs on him ... since he actually wrote/writes parts of it
> :-).

i'm a fan.  someday i hope to meet jeff and maybe fly him down to my mars
retreat.  oops have i just said something incriminating ?

the real fools are the ones who write endless streams of devoted affection
to him.  he informed.  involved.  i've always considered him an evolved
intellectual life form - probably our first self made electronic citizen.

he certainly commands their attentions.

Cheers
Joe Baptista

--
Planet Communications & Computing Facility
a division of The dot.GOD Registry, Limited






From owner-ietf@ietf.org  Wed Jan  8 19:41:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15350;
	Wed, 8 Jan 2003 19:40:39 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WQO3-0003EK-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 19:17:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WQFl-0002ed-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 19:09:04 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA14056
	for <ietf@ietf.org>; Wed, 8 Jan 2003 18:59:08 -0500 (EST)
Received: (qmail 1540 invoked from network); 9 Jan 2003 00:02:24 -0000
Received: from sub.sonic.net (208.201.224.8)
  by a.smtp-out.sonic.net with SMTP; 9 Jan 2003 00:02:24 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h0902NS01095;
	Wed, 8 Jan 2003 16:02:23 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 16:01:04 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-160103-1806.MMD@SonomaDesign.com; Wed, 8 Jan 2003 16:01:03 -0800
Received: by prop.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 16:01:12 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 15:57:13 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h08Nukf30535;
	Wed, 8 Jan 2003 15:56:50 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WPU3-00089B-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 18:19:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WPRC-0007lH-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 18:16:45 -0500
Received: from boromir.vpop.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12490
	for <ietf@ietf.org>; Wed, 8 Jan 2003 18:07:42 -0500 (EST)
Received: from [192.168.0.10] (ppp-67-118-247-209.dialup.pltn13.pacbell.net [67.118.247.209])
	by boromir.vpop.net (Postfix) with ESMTP
	id CE8B83A6320; Wed,  8 Jan 2003 15:10:53 -0800 (PST)
Mime-Version: 1.0
Message-Id: <a05111b0fba425f67bbe2@[192.168.0.10]>
In-Reply-To: <5.1.0.14.0.20030108200752.032f81e0@mail.utel.net>
References: <5.1.0.14.0.20030108200752.032f81e0@mail.utel.net>
Date: Wed, 8 Jan 2003 15:10:51 -0800
To: jfcm <info@utel.net>, ietf@ietf.org
From: Ari Ollikainen <Ari@OLTECO.com>
Subject: Re: FW: Please recant or appologize to Jim Flemming
Cc: support@sonic.net, abuse@sonic.net, dane@sonic.net
Content-Type: text/plain; charset="us-ascii"
X-OriginalArrivalTime: 09 Jan 2003 00:01:04.0948 (UTC) FILETIME=[342F8740:01C2B772]
Sender: owner-ietf@ietf.org
Precedence: bulk

At 8:08 PM +0100 1/8/03, jfcm wrote:
>Content-Type: text/plain; x-avg-checked=avg-ok-36D36B12; charset=us-ascii; format=flowed
>Content-Transfer-Encoding: 8bit
>
>Are others receiveing mails twice on this list?
>

	Apparently someone at SonomaDesigns hosted by sonic.net
	is reflecting ALL ietf list messages back to the list:

	[an excerpt from the header of the last message received]

Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WNdl-0007I7-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 16:21:37 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA07523
	for <ietf@ietf.org>; Wed, 8 Jan 2003 16:12:47 -0500 (EST)
Received: (qmail 8737 invoked from network); 8 Jan 2003 21:16:03 -0000
Received: from tempest.sonic.net (208.201.224.25)
  by a.smtp-out.sonic.net with SMTP; 8 Jan 2003 21:16:03 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by tempest.sonic.net (8.11.6/8.8.5) with ESMTP id h08LG3502950
	for <ietf@ietf.org>; Wed, 8 Jan 2003 13:16:03 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 13:15:54 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01082003-131553-1734.MMD@SonomaDesign.com; Wed, 8 Jan 2003 13:15:53 -0800
Received: by prop.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Jan  8 13:16:02 2003)
X-From_: owner-ietf@ietf.org  Wed Jan  8 13:11:43 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by tempest.sonic.net (8.11.6/8.8.5) with ESMTP id h08LBW501350;
	Wed, 8 Jan 2003 13:11:36 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WLgU-0005qj-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 14:16:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WLZo-0005ET-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 14:09:21 -0500

 

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

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




From owner-ietf@ietf.org  Thu Jan  9 09:01:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09502;
	Thu, 9 Jan 2003 09:01:56 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Wc50-0000jn-00
	for ietf-list@ran.ietf.org; Thu, 09 Jan 2003 07:46:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Wc4E-0000iT-00
	for ietf@ran.ietf.org; Thu, 09 Jan 2003 07:45:53 -0500
Received: from smtp016.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA07978
	for <ietf@ietf.org>; Thu, 9 Jan 2003 07:36:46 -0500 (EST)
Received: from 212.68.224.51.brutele.be (HELO toto) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 9 Jan 2003 12:40:02 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'Clint Chaplin'" <cchaplin@sj.symbol.com>
Cc: <ietf@ietf.org>
Subject: Receiving mails twice (was: Please recant or appologize to Jim Flemming)
Date: Thu, 9 Jan 2003 13:42:08 +0100
Organization: Eric Tomson
Message-ID: <019801c2b7dc$881d87c0$2200a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <se1c2c44.030@gwianameserver.sj.symbol.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA09502

I get them twice, too!

-----Original Message-----
From: Clint Chaplin

I too have been receiving mails twice from this list.  The duplicate
mails seem to be about ½ to 1 hour apart.

Clint (JOATMON) Chaplin

>>> jfcm <info@utel.net> 1/8/03 11:08:29 >>>

Are others receiveing mails twice on this list?

jfc

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com



From owner-ietf@ietf.org  Thu Jan  9 09:02:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09552;
	Thu, 9 Jan 2003 09:02:29 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WdL3-0000OF-00
	for ietf-list@ran.ietf.org; Thu, 09 Jan 2003 09:07:17 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WdKO-0000Mh-00
	for ietf@ran.ietf.org; Thu, 09 Jan 2003 09:06:36 -0500
Received: from a.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA09416
	for <ietf@ietf.org>; Thu, 9 Jan 2003 08:57:49 -0500 (EST)
Received: (qmail 20856 invoked from network); 9 Jan 2003 14:01:05 -0000
Received: from tempest.sonic.net (208.201.224.25)
  by a.smtp-out.sonic.net with SMTP; 9 Jan 2003 14:01:05 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by tempest.sonic.net (8.11.6/8.8.5) with ESMTP id h09E15r23988;
	Thu, 9 Jan 2003 06:01:05 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 9 Jan 2003 06:00:54 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01092003-060054-1948.MMD@SonomaDesign.com; Thu, 9 Jan 2003 06:00:54 -0800
Received: by prop.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Thu Jan  9 06:01:04 2003)
X-From_: owner-ietf@ietf.org  Thu Jan  9 05:54:13 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h09Ds5g21142;
	Thu, 9 Jan 2003 05:54:07 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Wc50-0000jn-00
	for ietf-list@ran.ietf.org; Thu, 09 Jan 2003 07:46:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Wc4E-0000iT-00
	for ietf@ran.ietf.org; Thu, 09 Jan 2003 07:45:53 -0500
Received: from smtp016.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA07978
	for <ietf@ietf.org>; Thu, 9 Jan 2003 07:36:46 -0500 (EST)
Received: from 212.68.224.51.brutele.be (HELO toto) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 9 Jan 2003 12:40:02 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'Clint Chaplin'" <cchaplin@sj.symbol.com>
Cc: <ietf@ietf.org>
Subject: Receiving mails twice (was: Please recant or appologize to Jim Flemming)
Date: Thu, 9 Jan 2003 13:42:08 +0100
Organization: Eric Tomson
Message-ID: <019801c2b7dc$881d87c0$2200a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <se1c2c44.030@gwianameserver.sj.symbol.com>
X-MIME-Autoconverted: from quoted-printable to 8bit by sub.sonic.net id h09Ds5g21142
X-OriginalArrivalTime: 09 Jan 2003 14:00:54.0791 (UTC) FILETIME=[86DF6170:01C2B7E7]
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id IAA09417
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA09552

I get them twice, too!

-----Original Message-----
From: Clint Chaplin

I too have been receiving mails twice from this list.  The duplicate
mails seem to be about ½ to 1 hour apart.

Clint (JOATMON) Chaplin

>>> jfcm <info@utel.net> 1/8/03 11:08:29 >>>

Are others receiveing mails twice on this list?

jfc

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com




From owner-ietf@ietf.org  Thu Jan  9 16:13:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26461;
	Thu, 9 Jan 2003 16:13:13 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WhER-0000Mj-00
	for ietf-list@ran.ietf.org; Thu, 09 Jan 2003 13:16:43 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Wdu8-0002IY-00
	for ietf@ran.ietf.org; Thu, 09 Jan 2003 09:43:32 -0500
Received: from smtp018.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA11453
	for <ietf@ietf.org>; Thu, 9 Jan 2003 09:34:40 -0500 (EST)
Received: from 212.68.224.51.brutele.be (HELO toto) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 9 Jan 2003 14:37:56 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: <cchaplin@sj.symbol.com>
Cc: <ietf@ietf.org>
Subject: FW: Delivery Status Notification (Failure)
Date: Thu, 9 Jan 2003 15:40:26 +0100
Organization: Eric Tomson
Message-ID: <000e01c2b7ed$0e1f9c40$2200a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_000F_01C2B7F5.6FE40440"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_000F_01C2B7F5.6FE40440
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Having sent my previous mail "Receiving mails twice" to the list, I got
this one a few minutes later!

-----Original Message-----
From: postmaster@SonomaDesign.com [mailto:postmaster@SonomaDesign.com] 
Sent: jeudi 9 janvier 2003 15:16
To: Tomson_Eric@Yahoo.fr
Subject: Delivery Status Notification (Failure)


This is an automatically generated Delivery Status Notification.

Unable to deliver message to the following recipients, because the
message was forwarded more than the maximum allowed times. This could
indicate a mail loop.

       ietf@ietf.org
       cchaplin@sj.symbol.com




------=_NextPart_000_000F_01C2B7F5.6FE40440
Content-Type: message/delivery-status;
	name="details.txt"
Content-Disposition: attachment;
	filename="details.txt"
Content-Transfer-Encoding: 7bit

Reporting-MTA: dns;server.SDG.local
Received-From-MTA: dns;server.SDG.local
Arrival-Date: Thu, 9 Jan 2003 06:15:54 -0800

Final-Recipient: rfc822;ietf@ietf.org
Action: failed
Status: 4.4.6

Final-Recipient: rfc822;cchaplin@sj.symbol.com
Action: failed
Status: 4.4.6

------=_NextPart_000_000F_01C2B7F5.6FE40440--

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en frangais !
Yahoo! Mail : http://fr.mail.yahoo.com



From owner-ietf@ietf.org  Thu Jan  9 17:53:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28975;
	Thu, 9 Jan 2003 17:53:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WlYY-00066Y-00
	for ietf-list@ran.ietf.org; Thu, 09 Jan 2003 17:53:46 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WlXr-000637-00
	for ietf@ran.ietf.org; Thu, 09 Jan 2003 17:53:03 -0500
Received: from almso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28817;
	Thu, 9 Jan 2003 17:44:10 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h09LxYH7027978;
	Thu, 9 Jan 2003 17:47:26 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E00FC4EB5; Thu, 9 Jan 2003 17:47:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 9 Jan 2003 17:47:25 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704A17617@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Thread-Index: AcK3W6WXQTTQemkeR72leF3lr9ewHAAyXxmQ
From: "Ash, Gerald R (Jerry), ALASO" <gash@att.com>
To: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
Cc: "Ash, Gerald R (Jerry), ALASO" <gash@att.com>, <iesg@ietf.org>,
        "Osama Aboul-Magd" <osama@nortelnetworks.com>, <ietf@ietf.org>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Lazer, Monica A, ALASO" <mlazer@att.com>,
        "Varma, Eve L (Eve)" <evarma@lucent.com>,
        "Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Brungard, Deborah A, ALASO" <dbrungard@att.com>,
        "Loa Andersson" <loa@pi.se>, "Adrian Farrel" <afarrel@movaz.com>,
        "Stephen Trowbridge" <sjtrowbridge@lucent.com>,
        "Lazer, Monica A, ALASO" <mlazer@att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA28975

Zhi,

> In terms of where the liaisons are, not sure. I checked the 
> link as well, and couldn't find any of the liaisons that was 
> sent from ITU-T Q.14/15 to IETF CCAMP WG.

Thanks to Kam for showing us the linkage, it's rather complicated...  Maybe that's why we've seen no discussion in CCAMP on these ASON Signaling Recommendations [G.7713.2 (GMPLS RSVP-TE) and G.7713.3 (GMPLS CR-LDP)].  Hopefully folks will look at them and provide comments.
 
> In terms of the intentions of the draft Recommendations 
> G.7713.x series, these draft Recommendations are targeted to 
> support the ASON control plane network. There is a difference 
> between what IETF is working on and what ITU is working on, 
> and these are mainly targeted for large incumbent carriers 
> such as your company (and many of these requirements are 
> driven by large carriers). 

So I guess you're saying that the G.7713.x Recommendations are actually 'requirements', presumably to be considered by the IETF for GMPLS extensions.  Is that also the purpose of yours and Osama's Informational RFCs on 'GMPLS extensions for ASON'?  That is, http://www.ietf.org/internet-drafts/draft-lin-ccamp-gmpls-ason-rsvpte-04.txt and http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.txt are actually GMPLS requirements for CCAMP to consider, is that right?

BTW, 'large carriers' (and medium and small carriers, too) are providing requirements/needs directly into the GMPLS effort in IETF, as well as indirectly through the ITU.

> For example, one obvious 
> difference is the support of only IP addressing within the 
> GMPLS. In the ITU ASON extensions, the G.7713.x protocols 
> include support for not only the IP addresses, but also NSAP 
> addresses.
> 
> Another obvious difference is that when ITU was developing 
> ASON and IETF developing GMPLS, there was a position within 
> CCAMP (during GMPLS development) that there is an inherent 
> sharing of information between a user of the network and the 
> network itself (the overlay vs. peer discussion). The ITU has 
> always taken the approach that we need to support a range of 
> information sharing, from fully sharing info (the I-NNI 
> interface) to flexible info sharing (the E-NNI interface) to 
> no sharing of info (the UNI interface). The majority of the 
> extensions (NOTE these are extensions and not competing 
> protocols) are to support these fundamental network design decisions.
> 
> Another example of the difference in design philosophy is in 
> the area of routing. Within the CCAMP, routing extensions are 
> made to the existing protocols to support additional link 
> attributes for GMPLS. However, the concept of multiple 
> domains and hierarchies are not really provided (not beyond 
> what the existing protocol provides). These concepts (domains 
> and hierarchies) are again driven by the large carriers (such 
> as AT&T and BT). What we (as ITU-T participants) did were to 
> listen to these requirements and added extensions that 
> supports the carriers' requirements.

First, I think there is confusion in terminology across the various standards bodies.  For example, and quoting from Deborah Brungard: "One key item is the confusion between OIF, IETF, ITU participants on the definition of inter-domain interface. In ITU terminology, inter-domain is between carriers (and as an option for the carrier to use within his domain). Inter-domain is based on reachability, no topology sharing. Also no hierarchy. G.8080 is very clear on this. For OIF, an inter-domain interface is between vendors islands i.e. OIF is an interop forum. For IETF, it's interior (e.g. GMPLS/OSPF) and exterior (e.g. BGP)."

Second, we should align the ITU and IETF 'GMPLS' efforts.  That is, we need to a) understand the terminology, and b) provide the requirements from ITU to IETF (as you are doing through your informational RFCs).

> In terms of your question about interoperability, the 
> protocol extensions from the ITU is designed as 
> optional/additional "tools" as part of the GMPLS toolkit. If 
> a vendor chooses to support the ITU's ASON application, they 
> will implement. Otherwise they will only implement the core 
> GMPLS and no more. Which vendor decides to implement what 
> really depends on what carriers (such as your company) are 
> going to ask for. The carriers have set the requirements in 
> ITU and those requirements have driven the protocol 
> extensions. The protocol design within the IETF were driven 
> from a different direction (or a different set of companies 
> -- more the enterprise customers).

You're suggesting that a common set of requirements is driving the G.7713.x series, maybe so, but then why does CR-LDP have crankback and RSVP-TE doesn't have crankback (as one example of inconsistencies)?  Also, I'm not sure it's a great approach for vendors to decide which 'GMPLS extensions' to implement based on 2 versions of GMPLS (IETF and ITU), and also based on what operators ask for (it still sounds like we're getting 2 versions of GMPLS).

> Hope this answers your questions and concerns, and hope 
> others will chime in with their opinion on this...

Yes, I hope others will comment on this thread.

Thanks,
Jerry

> 
> Zhi
> 
> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALASO [mailto:gash@att.com]
> Sent: Wednesday, January 08, 2003 3:48 PM
> To: Loa Andersson; Adrian Farrel
> Cc: Ash, Gerald R (Jerry), ALASO; iesg@ietf.org; Osama Aboul-Magd;
> ietf@ietf.org; Lin, Zhi-Wei (Zhi); hklam@lucent.com
> Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to
> Informational
> 
> Adrian> I am saying that it sounds to me from the discussion that 
> Adrian> the ITU has not yet reached consent. It seemed to me that 
> Adrian> if the draft is intended to document the ITU preferences as 
> Adrian> informational, it would be as well to wait until the ITU has
> Adrian> fully signed off. I don't see any rush for this.
> 
> Loa> ok - I can see the difference - and it seems that you are correct. If
> Loa> the ITU discussion still has some way to go before the discussion
> Loa> settles and the preferences better known - wouldn't it be 
> Loa> appropriate to wait until this happens?
> 
> ASON Signaling Recommendations G.7713.2 (GMPLS RSVP-TE) and 
> G.7713.3 (GMPLS CR-LDP) are proposed for consent at the 
> upcoming SG15 meeting, 20-31 January (Geneva).  A Liaison was 
> sent to the IETF containing Recommendation text, but I can't 
> find it on http://www.ietf.org/IESG/LIAISON/.
> 
> Both documents propose detailed protocol specifications 
> including new TLVs (e.g., crankback TLV in G.7713.3).  The 
> intent of these Recommendations is unclear.  
> 
> If these are statements of 'ITU preferences/requirements' 
> which are made known to the IETF through the Informational 
> RFCs, such as Osama's and Zhi's, then fine.  IETF can then 
> take up the 'preferences/requirements' and consider them for 
> upgrading RSVP-TE and CR-LDP protocols (although CR-LDP is capped).  
> 
> However, if they are intended as alternative protocol specs 
> competing with the IETF specs, then that's a problem.  Which 
> spec does a vendor implement and an operator use, given 
> interoperability needs, etc.?  It would be analogous to the 
> IETF specifying their version of G.709.
> 
> A clarification of the intent of these Recs. would be helpful.
> 
> Jerry Ash
> 



From owner-ietf@ietf.org  Thu Jan  9 18:03:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29342;
	Thu, 9 Jan 2003 18:03:19 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Wllr-0007CO-00
	for ietf-list@ran.ietf.org; Thu, 09 Jan 2003 18:07:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Wlkg-00078m-00
	for ietf@ran.ietf.org; Thu, 09 Jan 2003 18:06:18 -0500
Received: from b.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA29103
	for <ietf@ietf.org>; Thu, 9 Jan 2003 17:57:23 -0500 (EST)
Received: (qmail 18751 invoked from network); 9 Jan 2003 23:00:39 -0000
Received: from ultra.sonic.net (208.201.224.22)
  by b.smtp-out.sonic.net with SMTP; 9 Jan 2003 23:00:39 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by ultra.sonic.net (8.11.6/8.8.5) with ESMTP id h09N0dN24711;
	Thu, 9 Jan 2003 15:00:39 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 9 Jan 2003 15:00:29 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01092003-150028-3.MMD@SonomaDesign.com; Thu, 9 Jan 2003 15:00:28 -0800
Received: by ultra.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Thu Jan  9 15:00:37 2003)
X-From_: owner-ietf@ietf.org  Thu Jan  9 14:57:45 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by tempest.sonic.net (8.11.6/8.8.5) with ESMTP id h09Mvhs16111;
	Thu, 9 Jan 2003 14:57:44 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WlYY-00066Y-00
	for ietf-list@ran.ietf.org; Thu, 09 Jan 2003 17:53:46 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WlXr-000637-00
	for ietf@ran.ietf.org; Thu, 09 Jan 2003 17:53:03 -0500
Received: from almso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28817;
	Thu, 9 Jan 2003 17:44:10 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h09LxYH7027978;
	Thu, 9 Jan 2003 17:47:26 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E00FC4EB5; Thu, 9 Jan 2003 17:47:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 9 Jan 2003 17:47:25 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704A17617@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
Thread-Index: AcK3W6WXQTTQemkeR72leF3lr9ewHAAyXxmQ
From: "Ash, Gerald R (Jerry), ALASO" <gash@att.com>
To: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
Cc: "Ash, Gerald R (Jerry), ALASO" <gash@att.com>, <iesg@ietf.org>,
        "Osama Aboul-Magd" <osama@nortelnetworks.com>, <ietf@ietf.org>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Lazer, Monica A, ALASO" <mlazer@att.com>,
        "Varma, Eve L (Eve)" <evarma@lucent.com>,
        "Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Brungard, Deborah A, ALASO" <dbrungard@att.com>,
        "Loa Andersson" <loa@pi.se>, "Adrian Farrel" <afarrel@movaz.com>,
        "Stephen Trowbridge" <sjtrowbridge@lucent.com>,
        "Lazer, Monica A, ALASO" <mlazer@att.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by tempest.sonic.net id h09Mvhs16111
X-OriginalArrivalTime: 09 Jan 2003 23:00:29.0720 (UTC) FILETIME=[E7D58180:01C2B832]
Content-Transfer-Encoding: 8bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Zhi,

> In terms of where the liaisons are, not sure. I checked the 
> link as well, and couldn't find any of the liaisons that was 
> sent from ITU-T Q.14/15 to IETF CCAMP WG.

Thanks to Kam for showing us the linkage, it's rather complicated...  Maybe that's why we've seen no discussion in CCAMP on these ASON Signaling Recommendations [G.7713.2 (GMPLS RSVP-TE) and G.7713.3 (GMPLS CR-LDP)].  Hopefully folks will look at them and provide comments.
 
> In terms of the intentions of the draft Recommendations 
> G.7713.x series, these draft Recommendations are targeted to 
> support the ASON control plane network. There is a difference 
> between what IETF is working on and what ITU is working on, 
> and these are mainly targeted for large incumbent carriers 
> such as your company (and many of these requirements are 
> driven by large carriers). 

So I guess you're saying that the G.7713.x Recommendations are actually 'requirements', presumably to be considered by the IETF for GMPLS extensions.  Is that also the purpose of yours and Osama's Informational RFCs on 'GMPLS extensions for ASON'?  That is, http://www.ietf.org/internet-drafts/draft-lin-ccamp-gmpls-ason-rsvpte-04.txt and http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.txt are actually GMPLS requirements for CCAMP to consider, is that right?

BTW, 'large carriers' (and medium and small carriers, too) are providing requirements/needs directly into the GMPLS effort in IETF, as well as indirectly through the ITU.

> For example, one obvious 
> difference is the support of only IP addressing within the 
> GMPLS. In the ITU ASON extensions, the G.7713.x protocols 
> include support for not only the IP addresses, but also NSAP 
> addresses.
> 
> Another obvious difference is that when ITU was developing 
> ASON and IETF developing GMPLS, there was a position within 
> CCAMP (during GMPLS development) that there is an inherent 
> sharing of information between a user of the network and the 
> network itself (the overlay vs. peer discussion). The ITU has 
> always taken the approach that we need to support a range of 
> information sharing, from fully sharing info (the I-NNI 
> interface) to flexible info sharing (the E-NNI interface) to 
> no sharing of info (the UNI interface). The majority of the 
> extensions (NOTE these are extensions and not competing 
> protocols) are to support these fundamental network design decisions.
> 
> Another example of the difference in design philosophy is in 
> the area of routing. Within the CCAMP, routing extensions are 
> made to the existing protocols to support additional link 
> attributes for GMPLS. However, the concept of multiple 
> domains and hierarchies are not really provided (not beyond 
> what the existing protocol provides). These concepts (domains 
> and hierarchies) are again driven by the large carriers (such 
> as AT&T and BT). What we (as ITU-T participants) did were to 
> listen to these requirements and added extensions that 
> supports the carriers' requirements.

First, I think there is confusion in terminology across the various standards bodies.  For example, and quoting from Deborah Brungard: "One key item is the confusion between OIF, IETF, ITU participants on the definition of inter-domain interface. In ITU terminology, inter-domain is between carriers (and as an option for the carrier to use within his domain). Inter-domain is based on reachability, no topology sharing. Also no hierarchy. G.8080 is very clear on this. For OIF, an inter-domain interface is between vendors islands i.e. OIF is an interop forum. For IETF, it's interior (e.g. GMPLS/OSPF) and exterior (e.g. BGP)."

Second, we should align the ITU and IETF 'GMPLS' efforts.  That is, we need to a) understand the terminology, and b) provide the requirements from ITU to IETF (as you are doing through your informational RFCs).

> In terms of your question about interoperability, the 
> protocol extensions from the ITU is designed as 
> optional/additional "tools" as part of the GMPLS toolkit. If 
> a vendor chooses to support the ITU's ASON application, they 
> will implement. Otherwise they will only implement the core 
> GMPLS and no more. Which vendor decides to implement what 
> really depends on what carriers (such as your company) are 
> going to ask for. The carriers have set the requirements in 
> ITU and those requirements have driven the protocol 
> extensions. The protocol design within the IETF were driven 
> from a different direction (or a different set of companies 
> -- more the enterprise customers).

You're suggesting that a common set of requirements is driving the G.7713.x series, maybe so, but then why does CR-LDP have crankback and RSVP-TE doesn't have crankback (as one example of inconsistencies)?  Also, I'm not sure it's a great approach for vendors to decide which 'GMPLS extensions' to implement based on 2 versions of GMPLS (IETF and ITU), and also based on what operators ask for (it still sounds like we're getting 2 versions of GMPLS).

> Hope this answers your questions and concerns, and hope 
> others will chime in with their opinion on this...

Yes, I hope others will comment on this thread.

Thanks,
Jerry

> 
> Zhi
> 
> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALASO [mailto:gash@att.com]
> Sent: Wednesday, January 08, 2003 3:48 PM
> To: Loa Andersson; Adrian Farrel
> Cc: Ash, Gerald R (Jerry), ALASO; iesg@ietf.org; Osama Aboul-Magd;
> ietf@ietf.org; Lin, Zhi-Wei (Zhi); hklam@lucent.com
> Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to
> Informational
> 
> Adrian> I am saying that it sounds to me from the discussion that 
> Adrian> the ITU has not yet reached consent. It seemed to me that 
> Adrian> if the draft is intended to document the ITU preferences as 
> Adrian> informational, it would be as well to wait until the ITU has
> Adrian> fully signed off. I don't see any rush for this.
> 
> Loa> ok - I can see the difference - and it seems that you are correct. If
> Loa> the ITU discussion still has some way to go before the discussion
> Loa> settles and the preferences better known - wouldn't it be 
> Loa> appropriate to wait until this happens?
> 
> ASON Signaling Recommendations G.7713.2 (GMPLS RSVP-TE) and 
> G.7713.3 (GMPLS CR-LDP) are proposed for consent at the 
> upcoming SG15 meeting, 20-31 January (Geneva).  A Liaison was 
> sent to the IETF containing Recommendation text, but I can't 
> find it on http://www.ietf.org/IESG/LIAISON/.
> 
> Both documents propose detailed protocol specifications 
> including new TLVs (e.g., crankback TLV in G.7713.3).  The 
> intent of these Recommendations is unclear.  
> 
> If these are statements of 'ITU preferences/requirements' 
> which are made known to the IETF through the Informational 
> RFCs, such as Osama's and Zhi's, then fine.  IETF can then 
> take up the 'preferences/requirements' and consider them for 
> upgrading RSVP-TE and CR-LDP protocols (although CR-LDP is capped).  
> 
> However, if they are intended as alternative protocol specs 
> competing with the IETF specs, then that's a problem.  Which 
> spec does a vendor implement and an operator use, given 
> interoperability needs, etc.?  It would be analogous to the 
> IETF specifying their version of G.709.
> 
> A clarification of the intent of these Recs. would be helpful.
> 
> Jerry Ash
> 




From owner-ietf@ietf.org  Thu Jan  9 19:25:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01494;
	Thu, 9 Jan 2003 19:25:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Wmza-0003ua-00
	for ietf-list@ran.ietf.org; Thu, 09 Jan 2003 19:25:46 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Wmyu-0003qo-00
	for ietf@ran.ietf.org; Thu, 09 Jan 2003 19:25:04 -0500
Received: from lightwave.chromisys.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01279;
	Thu, 9 Jan 2003 19:16:10 -0500 (EST)
Received: by lightwave.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <4GJZ1D0P>; Thu, 9 Jan 2003 16:19:23 -0800
Message-ID: <9D42C6E086250248810DCADA39CE7EFC97210E@nimbus>
From: John Drake <jdrake@calient.net>
To: "'Ash, Gerald R (Jerry), ALASO'" <gash@att.com>,
        "Lin, Zhi-Wei (Zhi)"
	 <zwlin@lucent.com>
Cc: iesg@ietf.org, Osama Aboul-Magd <osama@nortelnetworks.com>, ietf@ietf.org,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Lazer, Monica A, ALASO" <mlazer@att.com>,
        "Varma, Eve L (Eve)"
	 <evarma@lucent.com>,
        "Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Brungard, Deborah A, ALASO" <dbrungard@att.com>,
        Loa Andersson
	 <loa@pi.se>, Adrian Farrel <afarrel@movaz.com>,
        Stephen Trowbridge
	 <sjtrowbridge@lucent.com>,
        "Lazer, Monica A, ALASO" <mlazer@att.com>
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informat
	ional
Date: Thu, 9 Jan 2003 16:19:13 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Gerry,

I share your concerns.

I skimmed the informational RFCs you cited and they don't look much like
requirements documents.  Rather, they look like ITU protocol enhancements to
IETF protocols.  Quoting from the abstracts:  "It proposes additional
extensions to these signaling protocols to support the capabilities of an
ASON network." and "This document describes Constraint Route Label
Distribution Protocol (CR-LDP) extensions for use across ASON reference
points."

Using your example that it would be ill-considered for the IETF to develop
its own version of G.709, I think it would be better if ASON requirements
were brought into CCAMP and worked on there.

Thanks,

John 
 
  
    
-----Original Message-----
From: Ash, Gerald R (Jerry), ALASO [mailto:gash@att.com]
Sent: Thursday, January 09, 2003 2:47 PM
To: Lin, Zhi-Wei (Zhi)
Cc: Ash, Gerald R (Jerry), ALASO; iesg@ietf.org; Osama Aboul-Magd;
ietf@ietf.org; Lam, Hing-Kam (Kam); Lazer, Monica A, ALASO; Varma, Eve L
(Eve); Stephen Shew (E-mail); Alan McGuire (E-mail); Brungard, Deborah
A, ALASO; Loa Andersson; Adrian Farrel; Stephen Trowbridge; Lazer,
Monica A, ALASO
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to
Informational


Zhi,

> In terms of where the liaisons are, not sure. I checked the 
> link as well, and couldn't find any of the liaisons that was 
> sent from ITU-T Q.14/15 to IETF CCAMP WG.

Thanks to Kam for showing us the linkage, it's rather complicated...  Maybe
that's why we've seen no discussion in CCAMP on these ASON Signaling
Recommendations [G.7713.2 (GMPLS RSVP-TE) and G.7713.3 (GMPLS CR-LDP)].
Hopefully folks will look at them and provide comments.
 
> In terms of the intentions of the draft Recommendations 
> G.7713.x series, these draft Recommendations are targeted to 
> support the ASON control plane network. There is a difference 
> between what IETF is working on and what ITU is working on, 
> and these are mainly targeted for large incumbent carriers 
> such as your company (and many of these requirements are 
> driven by large carriers). 

So I guess you're saying that the G.7713.x Recommendations are actually
'requirements', presumably to be considered by the IETF for GMPLS
extensions.  Is that also the purpose of yours and Osama's Informational
RFCs on 'GMPLS extensions for ASON'?  That is,
http://www.ietf.org/internet-drafts/draft-lin-ccamp-gmpls-ason-rsvpte-04.txt
and
http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.
txt are actually GMPLS requirements for CCAMP to consider, is that right?

BTW, 'large carriers' (and medium and small carriers, too) are providing
requirements/needs directly into the GMPLS effort in IETF, as well as
indirectly through the ITU.

> For example, one obvious 
> difference is the support of only IP addressing within the 
> GMPLS. In the ITU ASON extensions, the G.7713.x protocols 
> include support for not only the IP addresses, but also NSAP 
> addresses.
> 
> Another obvious difference is that when ITU was developing 
> ASON and IETF developing GMPLS, there was a position within 
> CCAMP (during GMPLS development) that there is an inherent 
> sharing of information between a user of the network and the 
> network itself (the overlay vs. peer discussion). The ITU has 
> always taken the approach that we need to support a range of 
> information sharing, from fully sharing info (the I-NNI 
> interface) to flexible info sharing (the E-NNI interface) to 
> no sharing of info (the UNI interface). The majority of the 
> extensions (NOTE these are extensions and not competing 
> protocols) are to support these fundamental network design decisions.
> 
> Another example of the difference in design philosophy is in 
> the area of routing. Within the CCAMP, routing extensions are 
> made to the existing protocols to support additional link 
> attributes for GMPLS. However, the concept of multiple 
> domains and hierarchies are not really provided (not beyond 
> what the existing protocol provides). These concepts (domains 
> and hierarchies) are again driven by the large carriers (such 
> as AT&T and BT). What we (as ITU-T participants) did were to 
> listen to these requirements and added extensions that 
> supports the carriers' requirements.

First, I think there is confusion in terminology across the various
standards bodies.  For example, and quoting from Deborah Brungard: "One key
item is the confusion between OIF, IETF, ITU participants on the definition
of inter-domain interface. In ITU terminology, inter-domain is between
carriers (and as an option for the carrier to use within his domain).
Inter-domain is based on reachability, no topology sharing. Also no
hierarchy. G.8080 is very clear on this. For OIF, an inter-domain interface
is between vendors islands i.e. OIF is an interop forum. For IETF, it's
interior (e.g. GMPLS/OSPF) and exterior (e.g. BGP)."

Second, we should align the ITU and IETF 'GMPLS' efforts.  That is, we need
to a) understand the terminology, and b) provide the requirements from ITU
to IETF (as you are doing through your informational RFCs).

> In terms of your question about interoperability, the 
> protocol extensions from the ITU is designed as 
> optional/additional "tools" as part of the GMPLS toolkit. If 
> a vendor chooses to support the ITU's ASON application, they 
> will implement. Otherwise they will only implement the core 
> GMPLS and no more. Which vendor decides to implement what 
> really depends on what carriers (such as your company) are 
> going to ask for. The carriers have set the requirements in 
> ITU and those requirements have driven the protocol 
> extensions. The protocol design within the IETF were driven 
> from a different direction (or a different set of companies 
> -- more the enterprise customers).

You're suggesting that a common set of requirements is driving the G.7713.x
series, maybe so, but then why does CR-LDP have crankback and RSVP-TE
doesn't have crankback (as one example of inconsistencies)?  Also, I'm not
sure it's a great approach for vendors to decide which 'GMPLS extensions' to
implement based on 2 versions of GMPLS (IETF and ITU), and also based on
what operators ask for (it still sounds like we're getting 2 versions of
GMPLS).

> Hope this answers your questions and concerns, and hope 
> others will chime in with their opinion on this...

Yes, I hope others will comment on this thread.

Thanks,
Jerry

> 
> Zhi
> 
> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALASO [mailto:gash@att.com]
> Sent: Wednesday, January 08, 2003 3:48 PM
> To: Loa Andersson; Adrian Farrel
> Cc: Ash, Gerald R (Jerry), ALASO; iesg@ietf.org; Osama Aboul-Magd;
> ietf@ietf.org; Lin, Zhi-Wei (Zhi); hklam@lucent.com
> Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to
> Informational
> 
> Adrian> I am saying that it sounds to me from the discussion that 
> Adrian> the ITU has not yet reached consent. It seemed to me that 
> Adrian> if the draft is intended to document the ITU preferences as 
> Adrian> informational, it would be as well to wait until the ITU has
> Adrian> fully signed off. I don't see any rush for this.
> 
> Loa> ok - I can see the difference - and it seems that you are correct. If
> Loa> the ITU discussion still has some way to go before the discussion
> Loa> settles and the preferences better known - wouldn't it be 
> Loa> appropriate to wait until this happens?
> 
> ASON Signaling Recommendations G.7713.2 (GMPLS RSVP-TE) and 
> G.7713.3 (GMPLS CR-LDP) are proposed for consent at the 
> upcoming SG15 meeting, 20-31 January (Geneva).  A Liaison was 
> sent to the IETF containing Recommendation text, but I can't 
> find it on http://www.ietf.org/IESG/LIAISON/.
> 
> Both documents propose detailed protocol specifications 
> including new TLVs (e.g., crankback TLV in G.7713.3).  The 
> intent of these Recommendations is unclear.  
> 
> If these are statements of 'ITU preferences/requirements' 
> which are made known to the IETF through the Informational 
> RFCs, such as Osama's and Zhi's, then fine.  IETF can then 
> take up the 'preferences/requirements' and consider them for 
> upgrading RSVP-TE and CR-LDP protocols (although CR-LDP is capped).  
> 
> However, if they are intended as alternative protocol specs 
> competing with the IETF specs, then that's a problem.  Which 
> spec does a vendor implement and an operator use, given 
> interoperability needs, etc.?  It would be analogous to the 
> IETF specifying their version of G.709.
> 
> A clarification of the intent of these Recs. would be helpful.
> 
> Jerry Ash
> 



From owner-ietf@ietf.org  Thu Jan  9 19:36:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01713;
	Thu, 9 Jan 2003 19:36:15 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WnE6-0004wQ-00
	for ietf-list@ran.ietf.org; Thu, 09 Jan 2003 19:40:46 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Wn9m-0004ja-00
	for ietf@ran.ietf.org; Thu, 09 Jan 2003 19:36:18 -0500
Received: from b.smtp-out.sonic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA01571
	for <ietf@ietf.org>; Thu, 9 Jan 2003 19:27:22 -0500 (EST)
Received: (qmail 30742 invoked from network); 10 Jan 2003 00:30:39 -0000
Received: from sub.sonic.net (208.201.224.8)
  by b.smtp-out.sonic.net with SMTP; 10 Jan 2003 00:30:39 -0000
Received: from server.SDG.local (adsl-209-204-181-95.sonic.net [209.204.181.95])
	by sub.sonic.net (8.11.6/8.8.5) with ESMTP id h0A0Uc819141;
	Thu, 9 Jan 2003 16:30:38 -0800
Received: from server.SDG.local ([10.0.0.2]) by server.SDG.local with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 9 Jan 2003 16:30:28 -0800
Received: by server.SDG.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
	 id MSG01092003-163027-40.MMD@SonomaDesign.com; Thu, 9 Jan 2003 16:30:27 -0800
Received: by prop.sonic.net (mbox sdg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Thu Jan  9 16:30:37 2003)
X-From_: owner-ietf@ietf.org  Thu Jan  9 16:30:07 2003
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id h0A0U5725332;
	Thu, 9 Jan 2003 16:30:05 -0800
X-envelope-info: <owner-ietf@ietf.org>
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Wmza-0003ua-00
	for ietf-list@ran.ietf.org; Thu, 09 Jan 2003 19:25:46 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Wmyu-0003qo-00
	for ietf@ran.ietf.org; Thu, 09 Jan 2003 19:25:04 -0500
Received: from lightwave.chromisys.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01279;
	Thu, 9 Jan 2003 19:16:10 -0500 (EST)
Received: by lightwave.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <4GJZ1D0P>; Thu, 9 Jan 2003 16:19:23 -0800
Message-ID: <9D42C6E086250248810DCADA39CE7EFC97210E@nimbus>
From: John Drake <jdrake@calient.net>
To: "'Ash, Gerald R (Jerry), ALASO'" <gash@att.com>,
        "Lin, Zhi-Wei (Zhi)"
	 <zwlin@lucent.com>
Cc: iesg@ietf.org, Osama Aboul-Magd <osama@nortelnetworks.com>, ietf@ietf.org,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Lazer, Monica A, ALASO" <mlazer@att.com>,
        "Varma, Eve L (Eve)"
	 <evarma@lucent.com>,
        "Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Brungard, Deborah A, ALASO" <dbrungard@att.com>,
        Loa Andersson
	 <loa@pi.se>, Adrian Farrel <afarrel@movaz.com>,
        Stephen Trowbridge
	 <sjtrowbridge@lucent.com>,
        "Lazer, Monica A, ALASO" <mlazer@att.com>
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informat
	ional
Date: Thu, 9 Jan 2003 16:19:13 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 10 Jan 2003 00:30:28.0828 (UTC) FILETIME=[79F401C0:01C2B83F]
Sender: owner-ietf@ietf.org
Precedence: bulk

Gerry,

I share your concerns.

I skimmed the informational RFCs you cited and they don't look much like
requirements documents.  Rather, they look like ITU protocol enhancements to
IETF protocols.  Quoting from the abstracts:  "It proposes additional
extensions to these signaling protocols to support the capabilities of an
ASON network." and "This document describes Constraint Route Label
Distribution Protocol (CR-LDP) extensions for use across ASON reference
points."

Using your example that it would be ill-considered for the IETF to develop
its own version of G.709, I think it would be better if ASON requirements
were brought into CCAMP and worked on there.

Thanks,

John 
 
  
    
-----Original Message-----
From: Ash, Gerald R (Jerry), ALASO [mailto:gash@att.com]
Sent: Thursday, January 09, 2003 2:47 PM
To: Lin, Zhi-Wei (Zhi)
Cc: Ash, Gerald R (Jerry), ALASO; iesg@ietf.org; Osama Aboul-Magd;
ietf@ietf.org; Lam, Hing-Kam (Kam); Lazer, Monica A, ALASO; Varma, Eve L
(Eve); Stephen Shew (E-mail); Alan McGuire (E-mail); Brungard, Deborah
A, ALASO; Loa Andersson; Adrian Farrel; Stephen Trowbridge; Lazer,
Monica A, ALASO
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to
Informational


Zhi,

> In terms of where the liaisons are, not sure. I checked the 
> link as well, and couldn't find any of the liaisons that was 
> sent from ITU-T Q.14/15 to IETF CCAMP WG.

Thanks to Kam for showing us the linkage, it's rather complicated...  Maybe
that's why we've seen no discussion in CCAMP on these ASON Signaling
Recommendations [G.7713.2 (GMPLS RSVP-TE) and G.7713.3 (GMPLS CR-LDP)].
Hopefully folks will look at them and provide comments.
 
> In terms of the intentions of the draft Recommendations 
> G.7713.x series, these draft Recommendations are targeted to 
> support the ASON control plane network. There is a difference 
> between what IETF is working on and what ITU is working on, 
> and these are mainly targeted for large incumbent carriers 
> such as your company (and many of these requirements are 
> driven by large carriers). 

So I guess you're saying that the G.7713.x Recommendations are actually
'requirements', presumably to be considered by the IETF for GMPLS
extensions.  Is that also the purpose of yours and Osama's Informational
RFCs on 'GMPLS extensions for ASON'?  That is,
http://www.ietf.org/internet-drafts/draft-lin-ccamp-gmpls-ason-rsvpte-04.txt
and
http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.
txt are actually GMPLS requirements for CCAMP to consider, is that right?

BTW, 'large carriers' (and medium and small carriers, too) are providing
requirements/needs directly into the GMPLS effort in IETF, as well as
indirectly through the ITU.

> For example, one obvious 
> difference is the support of only IP addressing within the 
> GMPLS. In the ITU ASON extensions, the G.7713.x protocols 
> include support for not only the IP addresses, but also NSAP 
> addresses.
> 
> Another obvious difference is that when ITU was developing 
> ASON and IETF developing GMPLS, there was a position within 
> CCAMP (during GMPLS development) that there is an inherent 
> sharing of information between a user of the network and the 
> network itself (the overlay vs. peer discussion). The ITU has 
> always taken the approach that we need to support a range of 
> information sharing, from fully sharing info (the I-NNI 
> interface) to flexible info sharing (the E-NNI interface) to 
> no sharing of info (the UNI interface). The majority of the 
> extensions (NOTE these are extensions and not competing 
> protocols) are to support these fundamental network design decisions.
> 
> Another example of the difference in design philosophy is in 
> the area of routing. Within the CCAMP, routing extensions are 
> made to the existing protocols to support additional link 
> attributes for GMPLS. However, the concept of multiple 
> domains and hierarchies are not really provided (not beyond 
> what the existing protocol provides). These concepts (domains 
> and hierarchies) are again driven by the large carriers (such 
> as AT&T and BT). What we (as ITU-T participants) did were to 
> listen to these requirements and added extensions that 
> supports the carriers' requirements.

First, I think there is confusion in terminology across the various
standards bodies.  For example, and quoting from Deborah Brungard: "One key
item is the confusion between OIF, IETF, ITU participants on the definition
of inter-domain interface. In ITU terminology, inter-domain is between
carriers (and as an option for the carrier to use within his domain).
Inter-domain is based on reachability, no topology sharing. Also no
hierarchy. G.8080 is very clear on this. For OIF, an inter-domain interface
is between vendors islands i.e. OIF is an interop forum. For IETF, it's
interior (e.g. GMPLS/OSPF) and exterior (e.g. BGP)."

Second, we should align the ITU and IETF 'GMPLS' efforts.  That is, we need
to a) understand the terminology, and b) provide the requirements from ITU
to IETF (as you are doing through your informational RFCs).

> In terms of your question about interoperability, the 
> protocol extensions from the ITU is designed as 
> optional/additional "tools" as part of the GMPLS toolkit. If 
> a vendor chooses to support the ITU's ASON application, they 
> will implement. Otherwise they will only implement the core 
> GMPLS and no more. Which vendor decides to implement what 
> really depends on what carriers (such as your company) are 
> going to ask for. The carriers have set the requirements in 
> ITU and those requirements have driven the protocol 
> extensions. The protocol design within the IETF were driven 
> from a different direction (or a different set of companies 
> -- more the enterprise customers).

You're suggesting that a common set of requirements is driving the G.7713.x
series, maybe so, but then why does CR-LDP have crankback and RSVP-TE
doesn't have crankback (as one example of inconsistencies)?  Also, I'm not
sure it's a great approach for vendors to decide which 'GMPLS extensions' to
implement based on 2 versions of GMPLS (IETF and ITU), and also based on
what operators ask for (it still sounds like we're getting 2 versions of
GMPLS).

> Hope this answers your questions and concerns, and hope 
> others will chime in with their opinion on this...

Yes, I hope others will comment on this thread.

Thanks,
Jerry

> 
> Zhi
> 
> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALASO [mailto:gash@att.com]
> Sent: Wednesday, January 08, 2003 3:48 PM
> To: Loa Andersson; Adrian Farrel
> Cc: Ash, Gerald R (Jerry), ALASO; iesg@ietf.org; Osama Aboul-Magd;
> ietf@ietf.org; Lin, Zhi-Wei (Zhi); hklam@lucent.com
> Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to
> Informational
> 
> Adrian> I am saying that it sounds to me from the discussion that 
> Adrian> the ITU has not yet reached consent. It seemed to me that 
> Adrian> if the draft is intended to document the ITU preferences as 
> Adrian> informational, it would be as well to wait until the ITU has
> Adrian> fully signed off. I don't see any rush for this.
> 
> Loa> ok - I can see the difference - and it seems that you are correct. If
> Loa> the ITU discussion still has some way to go before the discussion
> Loa> settles and the preferences better known - wouldn't it be 
> Loa> appropriate to wait until this happens?
> 
> ASON Signaling Recommendations G.7713.2 (GMPLS RSVP-TE) and 
> G.7713.3 (GMPLS CR-LDP) are proposed for consent at the 
> upcoming SG15 meeting, 20-31 January (Geneva).  A Liaison was 
> sent to the IETF containing Recommendation text, but I can't 
> find it on http://www.ietf.org/IESG/LIAISON/.
> 
> Both documents propose detailed protocol specifications 
> including new TLVs (e.g., crankback TLV in G.7713.3).  The 
> intent of these Recommendations is unclear.  
> 
> If these are statements of 'ITU preferences/requirements' 
> which are made known to the IETF through the Informational 
> RFCs, such as Osama's and Zhi's, then fine.  IETF can then 
> take up the 'preferences/requirements' and consider them for 
> upgrading RSVP-TE and CR-LDP protocols (although CR-LDP is capped).  
> 
> However, if they are intended as alternative protocol specs 
> competing with the IETF specs, then that's a problem.  Which 
> spec does a vendor implement and an operator use, given 
> interoperability needs, etc.?  It would be analogous to the 
> IETF specifying their version of G.709.
> 
> A clarification of the intent of these Recs. would be helpful.
> 
> Jerry Ash
> 




From owner-ietf@ietf.org  Thu Jan  9 22:27:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05487;
	Thu, 9 Jan 2003 22:27:37 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Wpoi-0001cS-00
	for ietf-list@ran.ietf.org; Thu, 09 Jan 2003 22:26:44 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Wplj-0001U1-00
	for ietf@ran.ietf.org; Thu, 09 Jan 2003 22:23:39 -0500
Received: from fsnt.future.futsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05236
	for <ietf@ietf.org>; Thu, 9 Jan 2003 22:14:42 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0004129964@fsnt.future.futsoft.com>;
 Fri, 10 Jan 2003 08:52:21 +0530
Received: from ramanad (ramanad.future.futsoft.com [10.8.3.18])
	by kailash.future.futsoft.com (8.12.2/8.12.2) with SMTP id h0A3EqBq022594;
	Fri, 10 Jan 2003 08:44:52 +0530
Reply-To: <ramanad@future.futsoft.com>
From: "Ramana Divvi" <ramanad@future.futsoft.com>
To: <Tomson_Eric@Yahoo.fr>, "'Clint Chaplin'" <cchaplin@sj.symbol.com>
Cc: <ietf@ietf.org>
Subject: RE: Receiving mails twice (was: Please recant or appologize to Jim Flemming)
Date: Fri, 10 Jan 2003 08:45:18 +0530
Message-Id: <000001c2b856$81cd2a40$1203080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <019801c2b7dc$881d87c0$2200a8c0@tomson.be>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Type: text/plain;
	charset="iso-8859-1"
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id WAA05238
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id WAA05487

I am also getting each mail twice from this list.
Regards,
Ramana.

 -----Original Message-----
From: 	owner-ietf@ietf.org [mailto:owner-ietf@ietf.org]  On Behalf Of Tomson
Eric (Yahoo.fr)
Sent:	Thursday, 9 January 2003 6:12 PM
To:	'Clint Chaplin'
Cc:	ietf@ietf.org
Subject:	Receiving mails twice (was: Please recant or appologize to Jim
Flemming)

I get them twice, too!

-----Original Message-----
From: Clint Chaplin

I too have been receiving mails twice from this list.  The duplicate
mails seem to be about 1/2 to 1 hour apart.

Clint (JOATMON) Chaplin

>>> jfcm <info@utel.net> 1/8/03 11:08:29 >>>

Are others receiveing mails twice on this list?

jfc

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information 
and should not be circulated or used for any purpose other than for 
what it is intended. 

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. 
FSL accepts no responsibility for loss or damage arising from 
the use of the information transmitted by this email including
damage from virus.
***************************************************************************



From owner-ietf@ietf.org  Fri Jan 10 11:11:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02107;
	Fri, 10 Jan 2003 11:11:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18X1cC-0005yk-00
	for ietf-list@ran.ietf.org; Fri, 10 Jan 2003 11:02:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18X1bw-0005x1-00
	for ietf@ran.ietf.org; Fri, 10 Jan 2003 11:02:20 -0500
Received: from auemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01755;
	Fri, 10 Jan 2003 10:58:56 -0500 (EST)
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0AG0Xd18124;
	Fri, 10 Jan 2003 11:00:33 -0500 (EST)
Received: from lucent.com (sjtrowbridge-1.dr.lucent.com [135.4.20.16]) by ihmail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id KAA18551; Fri, 10 Jan 2003 10:00:31 -0600 (CST)
Message-ID: <3E1EEE1E.C9AF047@lucent.com>
Date: Fri, 10 Jan 2003 09:00:30 -0700
From: Stephen Trowbridge <sjtrowbridge@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD EMS-1.5  (Windows NT 5.0; U)
X-Accept-Language: en,zh
MIME-Version: 1.0
To: "Ash, Gerald R (Jerry), ALASO" <gash@att.com>
CC: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>, iesg@ietf.org,
        Osama Aboul-Magd <osama@nortelnetworks.com>, ietf@ietf.org,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Lazer, Monica A, ALASO" <mlazer@att.com>,
        "Varma, Eve L (Eve)" <evarma@lucent.com>,
        "Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Brungard, Deborah A, ALASO" <dbrungard@att.com>,
        Loa Andersson <loa@pi.se>, Adrian Farrel <afarrel@movaz.com>,
        Wesam Alanqar <wesam.alanqar@mail.sprint.com>,
        Scott Bradner <sob@harvard.edu>, "Wijnen, Bert" <bwijnen@lucent.com>
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informational
References: <28F05913385EAC43AF019413F674A01704A17617@OCCLUST04EVS1.ugd.att.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

Jerry,
> Thanks to Kam for showing us the linkage, it's rather complicated...  Maybe that's why we've seen no discussion in CCAMP on these ASON Signaling Recommendations [G.7713.2 (GMPLS RSVP-TE) and G.7713.3 (GMPLS CR-LDP)].  Hopefully folks will look at them and provide comments.

I don't understand what more can possibly have been done to make
ccamp participants aware of the ITU-T work. Here is what has occurred to
advertise it:
- The IETF/ITU-T collaboration agreement has been revised by Gary Fishman
  and Scott Bradner to ease communication (see RFC 3356) to ease communication.
- I have put together the publicly accessible FTP area to share documents
  outside of the ITU-T.
- Scott Bradner has arranged for there to be the liaison area on the IESG
  web site where incoming liaisons are posted.
- ITU-T Study Group 15 has sent numerous liaisons to IETF ccamp, on the
  occasion of every Study Group 15 meeting, and every Q.12/15 or Q.14/15
  Rapportuer group meeting.
- At the Salt Lake City, Minneapolis, Yokohama, and Atlanta IETF meetings,
  either Wesam Alanquar or I have given presentations in ccamp about what
  we were doing in ITU-T and where the information can be found. The
  location of documents has been emailed to the ccamp list at least at
  the time of every IETF meeting when the presentations were given and
  when the liaisons were sent.
- Maarten Vissers gave technical presentation at the sub-IP area meeting
  in Salt Lake City about the ASON work in ITU-T.

Emails like Kam's are REMINDERs about information that has been widely advertised
for a long time. By no means are they the first time you should be hearing about
it. With the amount of information that has been sent from the ITU-T side, it
seems like only those who are intentionally trying to ignore the ITU-T work would
not have seen these documents much earlier.

I am anxious to hear if you have any ideas about how we could better advertise
this work within ccamp. It feels like we are beating people over the heads with
it, but somehow the message isn't getting through to everybody.
Regards,
Steve



From owner-ietf@ietf.org  Fri Jan 10 11:28:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02654;
	Fri, 10 Jan 2003 11:28:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18X1yR-00070i-00
	for ietf-list@ran.ietf.org; Fri, 10 Jan 2003 11:25:35 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18X1yC-0006yq-00
	for ietf@ran.ietf.org; Fri, 10 Jan 2003 11:25:20 -0500
Received: from e35.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02473
	for <ietf@ietf.org>; Fri, 10 Jan 2003 11:21:57 -0500 (EST)
Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.194.24])
	by e35.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id h0AGPDeP026194;
	Fri, 10 Jan 2003 11:25:13 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.12.14])
	by westrelay03.boulder.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id h0AGPCFU047658;
	Fri, 10 Jan 2003 09:25:12 -0700
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id h0AGOqL09468;
	Fri, 10 Jan 2003 11:24:52 -0500
Message-Id: <200301101624.h0AGOqL09468@rotala.raleigh.ibm.com>
To: "D. J. Bernstein" <djb@cr.yp.to>
cc: ietf@ietf.org, iesg@ietf.org, namedroppers <namedroppers@ops.ietf.org>
Subject: Dan Bernstein's issues about namedroppers list operation
Date: Fri, 10 Jan 2003 11:24:52 -0500
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

Dan Bernstein has been making repeated claims that Randy is censoring
his postings to namedroppers. I took a look at the claims he has made
and here is how I see things.

Executive summary: I see no evidence that Randy is censoring postings
from Dan. It is the case that some of his messages do not appear to
have made it out on namedroppers, but it is unclear why this is.
Furthermore, given that most of these missing messages were cc'ed to
other lists (i.e., the ietf and iesg lists), there is no evidence of
censorship.

Namedroppers is a posters-only mailing list that is run in conformance
with the policies outlined in
http://www.ietf.cnri.reston.va.us/IESG/STATEMENTS/mail-submit-policy.txt.

Specifically, all mail sent to namedroppers is:

1) first run through spamassassin. Mail that is rejected here is not
   archived, as the number of such messages is large. All mail sent to
   mailing lists on the server hosting namedroppers is run though
   spamassassin, so this is not a namedroppers-specific procedure.

2) if sent by a subscriber to the mailing list (or by someone in the
   known posters list), the message is sent immediately.

3) Otherwise, it is queued waiting for approval (or rejection) by the
   maling list operators. Both Randy and Mark Kosters see these
   rejected postings. Mark has indicated that he has seen no rejected
   postings that were not forwarded to the namedroppers mailing list
   that should have been.

It does appear that *some* of the message that Dan has sent to
namedroppers have not appeared on the namedroppers mailing list. But
it is unclear why that happened. At the time of these postings, some
of his other messages have gone through. Also, most of the messages
that didn't appear did appear on other mailing lists that were
cc'ed. It is unclear why those messages did not make it to
namedroppers, but now that Dan's posting address is in the the list of
know posters for namedroppers, and his mail seems to be getting
through, it seems best to just keep an eye on further problems and
investigate them as soon as they happen (e.g, when relevant logs are
available). I see no evidence that Randy (or anyone else) is singling
out anyone's postings for rejection.

Details on specifics follow.
   
"D. J. Bernstein" <djb@cr.yp.to> writes:

> Bush imposed his mailing-list control methods without IESG approval, in
> violation of RFC 2418, section 3.2. He has been caught engaging in
> content-based censorship several times:

>    http://cr.yp.to/djbdns/namedroppers.html

>     Background
> 
> The DNS protocol is covered by various IETF specifications.
> Unfortunately, obeying those specifications is not sufficient to ensure
> interoperability with BIND, in part because the specifications are
> ambiguous or otherwise flawed, and in part because BIND violates the
> specifications in many ways.
> 
> These facts have hurt competition, and contributed to BIND's market
> share, at the expense of the users. For example, one site using lbnamed,
> a special-purpose DNS implementation, has had interoperability problems
> with BIND, and has been planning to abandon lbnamed in favor of BIND,
> even though this means giving up some useful features.
> 
> In late 1999, after yet another BIND security hole was announced, I
> wrote a free BIND replacement. Interoperability among DNS
> implementations is, of course, essential. I found the IETF
> specifications horribly inadequate.
> 
> 
>     The namedroppers mailing list
> 
> IETF carries out its DNS protocol standardization activities within the
> DNSEXT working group. The DNSEXT mailing list is
> namedroppers@internic.net, also known as comp.protocols.dns.std.

This is old and incorrect, for quite some time. The mailing list is
namedroppers@ops.ietf.org. Mail from the mailing list may be gatewayed
one-way to usenet, but the reverse is not true. [Actually, I've been
told that usenet mail is selectively being forwarded back to the list
by someone, but it seems "very selectively", as this has happened to
only a handful of messages in several months.]

> ``Within the scope of this WG are protocol issues, including message
> formats, message handling, and data formats,'' the DNSEXT charter says.
> Several specific issues have been identified as work items, but other
> DNS protocol issues remain clearly within the charter. In particular,
> namedroppers is obviously the right forum for implementors to discuss
> current and future DNS interoperability problems.
> 
> Unfortunately, namedroppers is being run in a way that slows down, and
> sometimes prevents, public communication among DNS implementors.
> 
> Messages to namedroppers are not forwarded directly to subscribers. They
> are first sent to Randy Bush. They wait for Bush's review. Bush
> discards, edits, or misdirects messages that he doesn't like, and passes
> along what's left.
> 
> Here are some specific examples. Many of these incidents involved
> opsmail.internic.net, which used some painfully slow, creaky, obsolete
> software to distribute messages to subscribers.
> 
>     * 1998-12: Bush discarded a message from Richard Sexton commenting
>       on a proposed extension to MX records, a DNS protocol element.
>     * 1998-12: Bush edited a message of mine, unilaterally removing a
>       paragraph at the top that asked why opsmail was so slow. How is
>       someone supposed to find out what the namedroppers subscribers
>       think of how the mailing list is run, if complaints to the list
>       are censored?
>     * 1999-01: Bush discarded a message from Richard Sexton about client
>       interpretation of the AA bit, a DNS protocol element, by NSI, the
>       operators of some well-known DNS TLDs.
>     * 1999-12: Bush discarded a message of mine
>       <namedroppers/19991219005223-16101-qmail@cr-yp-to> concerning yet
>       another DNS protocol violation by BIND. ``This belongs in
>       bind-users@isc.org, not namedroppers,'' Bush told me
>       <namedroppers/e11zwx7-0000lb-00@roam-psg-com>, incorrectly.
>     * 1999-12-31: opsmail finally sent a message that it had received on
>       1999-11-04, nearly two months earlier, to a namedroppers
>       subscription address that had been removed from the list on
>       1999-11-25.
>     * 1999-12-31: I sent an urgent message
>       <namedroppers/19991231010737-16203-qmail@cr-yp-to> to namedroppers
>       attempting to confirm rumors of a DNS server bug that, if true,
>       would have been triggered on occasion by my new DNS cache. Someone
>       else sent a message to namedroppers 14 hours later, and then
>       another message 4 hours after that; 12 minutes later, Bush sent
>       those two messages to opsmail; several hours later, opsmail
>       finally forwarded the messages to me. A day later, I asked Bush
>       why my message hadn't appeared yet. He finally sent my message to
>       opsmail three days after I had sent it. I saw a copy from opsmail
>       several hours after that.
>     * 2000-01-12: I sent another message
>       <namedroppers/20000113013505-28147-qmail@cr-yp-to> to namedroppers
>       pointing out a security problem that I had described on bugtraq,
>       and asking DNSEXT to fix the relevant RFC, which had been
>       co-written by Bush. My message never appeared on namedroppers.
>       Bush didn't send me an explanation. I learned much later that Bush
>       had deliberately misdirected
>       <namedroppers/20000123065236-2897-qmail@cr-yp-to> my message,
>       sending it to the dnsop mailing list.
>     * 2000-01-28: I sent a message
>       <namedroppers/20000128015807-6574-qmail@cr-yp-to> to namedroppers
>       pointing out how Bush's censorship activities had biased DNSEXT
>       discussions, and a message
>       <namedroppers/20000129035223-3523-qmail@cr-yp-to> to namedroppers
>       criticizing Bush's unilateral statement of the namedroppers scope.
>       These messages were direct responses to recent namedroppers
>       messages, the first by Thomas Narten, the second by Bush. Bush
>       sent both messages back to me, without saying explicitly what he
>       had done with them.
>     * 2000-02-20: I pointed out
>       <namedroppers/20000220195445-21265-qmail@cr-yp-to> on namedroppers
>       that thousands of system administrators were using dotted-decimal
>       domain names in MX records. There was some discussion on
>       namedroppers. Rob Austein and Bill Manning asked for evidence;
>       Bush claimed that he couldn't find even a single example ``in
>       almost twenty thousand zones secondaried here from all over the
>       world.'' A few days later, I sent survey results
>       <namedroppers/20000225221016-31751-qmail@cr-yp-to> to namedroppers
>       showing that there were approximately fifteen /thousand/
>       second-level .com domains with dotted-decimal domain names in
>       their MX records, usually with no other MX records. My message
>       never appeared on namedroppers. ``Please report bugs in peoples
>       zone files to the people with the bugs, not namedroppers,'' Bush
>       told me.
>     * 2000-02-21: Bush discarded a message from Dean Anderson
>       <namedroppers/3-0-32-20000221220332-01705a94@odie-av8-com>
>       supporting expansion of the MX protocol definition to allow
>       dotted-decimal domain names.
>     * 2000-02-23: I sent another message
>       <namedroppers/20000223081350-27092-qmail@cr-yp-to> to namedroppers
>       objecting to Bush's censorship. Bush discarded my message.
>     * 2000-03-12: I sent a message
>       <namedroppers/20000312222447-11277-qmail@cr-yp-to> to namedroppers
>       asking about DNS query transmission strategy. Bush wrote back:
>       ``if your question is about the protocol, then fine. if it is
>       about how the dns operates and how folk's implementations effect
>       that, then post it to the mailing list for that implementation or
>       to the dnsop list. i.e. keep your bind bashing off this list.'' I
>       responded: ``My message asks about an efficiency problem in the
>       DNS protocol, and gives some illustrative examples. Are you going
>       to pass my message along to the list, or not?'' Bush discarded my
>       messages without further comment.
>     * 2001-03-17: I sent a message
>       <namedroppers/20010317134602-7103-qmail@cr-yp-to> to namedroppers
>       objecting to a BIND company proposal to modify the DNS protocol.
>       Bush discarded my message without comment.

All of the above is so old there is no point in discussing again. See,
for example, http://www.iab.org/Documents/BernsteinAppealResponse.txt

>     * 2002.11.17: I sent a message
>       <namedroppers/20021117174553-55961-qmail@cr-yp-to> to namedroppers
>       objecting to Bush and Gudmundsson sending the axfr-clarify
>       <axfr-clarify.html> document to the IESG, and summarizing ten
>       problems with that document. Bush silently discarded my
>     message.

This message was sent to the iesg, ietf and namedroppers mailing
list. The message did make it out on at least the iesg mailing list
(where I saw a copy), but I do not see it in the namedroppers archive.

>     * 2002.11.20: I sent a message
>       <namedroppers/20021120084916-34961-qmail@cr-yp-to> to namedroppers
>       discussing the lack of consensus behind axfr-clarify and
>       complaining about Bush's censorship. Bush silently discarded my
>       message.

Again, this message was posted to the ietf, iesg and namedroppers
list. I see this message did get posted to the iesg list; I do not see
it in the namedroppers archive.

>     * 2002.11.20, continued: I sent a message
>       <namedroppers/20021120103907-63440-qmail@cr-yp-to> to namedroppers
>       discussing the interoperability problems in axfr-clarify. Bush
>       silently discarded my message. After Bush wrote (on another list)
>       ``it is easy to miss and therefore delete mis-posts,'' I sent a
>       message <namedroppers/20021120202122-31601-qmail@cr-yp-to> to
>       namedroppers saying ``Funny how this happens so often for people
>       you disagree with'' and reminding Bush that he was causing
>       problems for newsgroup readers, sublist readers, and ``readers
>       with private subscription addresses''; Bush allowed that message
>       through.

Again, this message was posted to the ietf, iesg and namedroppers
list. I see this message made it do the iesg list; I do not see it in
the namedroppers archive.

>     * 2002.11.20, continued: I sent a message
>       <namedroppers/20021120203439-43796-qmail@cr-yp-to> to namedroppers
>       discussing the use of separate TCP/UDP ports. Bush silently
>       discarded my message.

This note was allegedely sent to namedroppers (and no where else). It
is not in the namedroppers archive. It is noted, however, that other
messages from Dan did appear on namedroppers that day.

>       My subscription address stopped receiving messages from the
>       namedroppers mailing list. About 40 hours later, I asked Bush what
>       was going on:
> 
>           Is that address still on the list? If not, why not? Does your
>           software reveal subscription addresses? Does it allow
>           unconfirmed unsubscription requests? Does it use
>           non-cryptographic cookies in confirmation notices? If the
>           address is still on the list, why aren't the outgoing messages
>           being delivered? Is there some general problem with all
>           addresses?
>
>       Suddenly the messages all came through.

Can't say what this was all about. Temporary mail problems?

>     * 2002.11.23: I sent a message
>       <namedroppers/20021123061646-22603-qmail@cr-yp-to> and another
>       message <namedroppers/20021123172816-71385-qmail@cr-yp-to> to
>       namedroppers. Bush promptly forwarded both messages. However, in
>       the second message, he manually inserted my subscription address,
>       despite my previous comments about private subscription addresses
>       and forged unsubscription requests. (Was this malicious, or was it
>       just mind-bogglingly stupid?)

Or perhaps, it was to make it clear to the poster which address the
posting was coming from, since there seems to be confusion at times
about whether someone is posting from the same address to which they
are subscribed.

"D. J. Bernstein" <djb@cr.yp.to> writes:

>     * 2002.11.25: I sent a message
> From: "D. J. Bernstein" <djb@cr.yp.to>
> To: namedroppers@ops.ietf.org
> Cc: sob@harvard.edu
> Date: 15 Dec 2002 03:18:14 -0000
> Subject: Re: repeating records
> Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.

> I've noticed that Randy Bush discarded Len Budney's note on this topic:
> http://groups.google.com/groups?selm=asnul4%24640g%241%40isrv4.isc.org

Not so.  Len's note was posted to usenet, not to the namedroppers
mailing list. Mail from usenet cannot be assumed to get gatewayed back
to the mailing list.

Thomas



From owner-ietf@ietf.org  Fri Jan 10 12:36:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05557;
	Fri, 10 Jan 2003 12:36:57 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18X30K-0001WG-00
	for ietf-list@ran.ietf.org; Fri, 10 Jan 2003 12:31:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18X2zm-0001UN-00
	for ietf@ran.ietf.org; Fri, 10 Jan 2003 12:31:02 -0500
Received: from prue.eim.surrey.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04676;
	Fri, 10 Jan 2003 12:27:42 -0500 (EST)
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 18X2zP-0006wG-00; Fri, 10 Jan 2003 17:30:39 +0000
Date: Fri, 10 Jan 2003 17:30:37 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Thomas Narten <narten@us.ibm.com>
cc: "D. J. Bernstein" <djb@cr.yp.to>, "" <ietf@ietf.org>, "" <iesg@ietf.org>,
        namedroppers <namedroppers@ops.ietf.org>
Subject: Re: Dan Bernstein's issues about namedroppers list operation
In-Reply-To: <200301101624.h0AGOqL09468@rotala.raleigh.ibm.com>
Message-ID: <Pine.GSO.4.50.0301101725380.22543-100000@artemis.ee.surrey.ac.uk>
References: <200301101624.h0AGOqL09468@rotala.raleigh.ibm.com>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-102.7 required=7.0
	tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,NOSPAM_INC,
	      QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,
	      SUBJECT_IS_LIST,USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.43
X-Scanner: exiscan *18X2zP-0006wG-00*tJ9wuycKRGc* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 10 Jan 2003, Thomas Narten wrote:

> Dan Bernstein has been making repeated claims that Randy is censoring
> his postings to namedroppers. I took a look at the claims he has made
> and here is how I see things.
>
> Executive summary: I see no evidence that Randy is censoring postings
> from Dan. It is the case that some of his messages do not appear to
> have made it out on namedroppers, but it is unclear why this is.
[..]
> It does appear that *some* of the message that Dan has sent to
> namedroppers have not appeared on the namedroppers mailing list. But
> it is unclear why that happened.

In other words, you see no evidence that Bush _isn't_ censoring
postings from Bernstein.

[Much justifying-the-status-quo snipped]

> All of the above is so old there is no point in discussing again.

A jolly refreshing attitude. Wish it was brought up more whenever that
'American Constituion' thing comes up.

L.

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



From owner-ietf@ietf.org  Fri Jan 10 13:55:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11245;
	Fri, 10 Jan 2003 13:55:10 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18X3Kw-0002ZH-00
	for ietf-list@ran.ietf.org; Fri, 10 Jan 2003 12:52:54 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18X3EM-0002MD-00
	for ietf@ran.ietf.org; Fri, 10 Jan 2003 12:46:06 -0500
Received: from as.vix.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05863;
	Fri, 10 Jan 2003 12:42:45 -0500 (EST)
Received: from as.vix.com (localhost [127.0.0.1])
	by as.vix.com (Postfix) with ESMTP
	id 4A501379FBB; Fri, 10 Jan 2003 17:46:01 +0000 (GMT)
From: Paul Vixie <paul@vix.com>
To: Thomas Narten <narten@us.ibm.com>
Cc: "D. J. Bernstein" <djb@cr.yp.to>, ietf@ietf.org, iesg@ietf.org,
        namedroppers <namedroppers@ops.ietf.org>
Subject: Re: Dan Bernstein's issues about namedroppers list operation 
In-Reply-To: Message from Thomas Narten <narten@us.ibm.com> 
	of "Fri, 10 Jan 2003 11:24:52 EST."
	<200301101624.h0AGOqL09468@rotala.raleigh.ibm.com> 
X-Mailer: MH-E 7.0; nmh 1.0.4; Emacs 21.2
Date: Fri, 10 Jan 2003 17:46:01 +0000
Message-Id: <20030110174601.4A501379FBB@as.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

thomas, et al,

i have a bone to pick.  while dr. bernstein would most likely say that
i am no friend to him nor to his chosen issues, the fact is that his
complaint has some validity if you look at it edge-on rather than face-on.

> Namedroppers is a posters-only mailing list that is run in conformance
> with the policies outlined in
> http://www.ietf.cnri.reston.va.us/IESG/STATEMENTS/mail-submit-policy.txt.
> 
> Specifically, all mail sent to namedroppers is:
> 
> 1) first run through spamassassin. Mail that is rejected here is not
>    archived, as the number of such messages is large. All mail sent to
>    mailing lists on the server hosting namedroppers is run though
>    spamassassin, so this is not a namedroppers-specific procedure.

this is just wrong.  spamassassin operates at the MUA level, and as such,
the originating MTA receives a "final OK" and drops the connection before
spamassassin begins its job.  the MUA's only choices when dropping mail
due to spamassassin's filtering are: issue a new message back to the sender
to inform them of the bounce, or silently drop.  because most of the mail
spamassassin will drop has an invalid sender address, choice #2 is common.

for an IETF list, if submitted mail is being dropped, there must be notice
back to the sender.  because the sender address will generally not be usable,
the only possible choice is to issue the rejection at the MTA level.  this
will require tighter integration of spamassassin into the MTA level than is
currently done on randy's system, or indeed, currently done anywhere at all.

silent drops are fatal to the IETF's policy of open discourse, and dr.
bernstein is right to complain about that aspect of the namedroppers problems
he is experiencing.  every time one of dr. bernstein's messages is dropped, 
dr. bernstein's originating MTA should experience an SMTP delivery error and
therefore have the option of informing dr. bernstein that such rejection has
occurred.

one other very minor point:

> > I've noticed that Randy Bush discarded Len Budney's note on this topic:
> > http://groups.google.com/groups?selm=asnul4%24640g%241%40isrv4.isc.org
> 
> Not so.  Len's note was posted to usenet, not to the namedroppers
> mailing list. Mail from usenet cannot be assumed to get gatewayed back
> to the mailing list.

as the usenet moderator of comp.protocols.dns.std, i set up a bidirectional
gateway which isc operates.  this gateway is far from perfect, and many posts
have been dropped (silently, of course) over the years, and anyone who wants
to really ensure that their words appear on namedroppers should avoid the use
of the usenet->namedroppers gateway, and mail their words directly to the
namedroppers list.

paul



From owner-ietf@ietf.org  Fri Jan 10 14:23:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13113;
	Fri, 10 Jan 2003 14:23:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18X4GU-00005Y-00
	for ietf-list@ran.ietf.org; Fri, 10 Jan 2003 13:52:22 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18X3Jj-0002Xn-00
	for ietf@ran.ietf.org; Fri, 10 Jan 2003 12:51:39 -0500
Received: from kalia.dbc.mtview.ca.us (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06013
	for <ietf@ietf.org>; Fri, 10 Jan 2003 12:48:18 -0500 (EST)
Received: from kalia.dbc.mtview.ca.us (localhost [127.0.0.1])
	by kalia.dbc.mtview.ca.us (8.12.6/8.12.6) with SMTP id h0AHpO42000632;
	Fri, 10 Jan 2003 09:51:24 -0800 (PST)
Date: Fri, 10 Jan 2003 09:51:23 -0800
From: Marshall Rose <mrose@dbc.mtview.ca.us>
To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
Cc: narten@us.ibm.com, ietf@ietf.org
Subject: Re: Dan Bernstein's issues about namedroppers list operation
Message-Id: <20030110095123.1f7f2765.mrose@dbc.mtview.ca.us>
In-Reply-To: <Pine.GSO.4.50.0301101725380.22543-100000@artemis.ee.surrey.ac.uk>
References: <200301101624.h0AGOqL09468@rotala.raleigh.ibm.com>
	<Pine.GSO.4.50.0301101725380.22543-100000@artemis.ee.surrey.ac.uk>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.8claws (GTK+ 1.2.10; i386-unknown-netbsdelf1.6)
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 Fri, 10 Jan 2003, Thomas Narten wrote:
> 
> > Dan Bernstein has been making repeated claims that Randy is censoring
> > his postings to namedroppers. I took a look at the claims he has made
> > and here is how I see things.
> >
> > Executive summary: I see no evidence that Randy is censoring postings
> > from Dan. It is the case that some of his messages do not appear to
> > have made it out on namedroppers, but it is unclear why this is.
> [..]
> > It does appear that *some* of the message that Dan has sent to
> > namedroppers have not appeared on the namedroppers mailing list. But
> > it is unclear why that happened.
> 
> In other words, you see no evidence that Bush _isn't_ censoring
> postings from Bernstein.

when someone develops the technology to prove a negative, let me know, because
from there it's just a quick hop, skip, and a jump to building a time-machine.

/mtr



From owner-ietf@ietf.org  Fri Jan 10 14:41:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13840;
	Fri, 10 Jan 2003 14:41:17 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18X4oU-0001Cc-00
	for ietf-list@ran.ietf.org; Fri, 10 Jan 2003 14:27:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18X4mb-0000i4-00
	for ietf@ran.ietf.org; Fri, 10 Jan 2003 14:25:33 -0500
Received: from calcite.rhyolite.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13100;
	Fri, 10 Jan 2003 14:22:11 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.7.Beta0/8.12.7.Beta0) id h0AJPQEt013992 env-from <vjs>;
	Fri, 10 Jan 2003 12:25:26 -0700 (MST)
Date: Fri, 10 Jan 2003 12:25:26 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200301101925.h0AJPQEt013992@calcite.rhyolite.com>
To: iesg@ietf.org, ietf@ietf.org
Subject: Re: Dan Bernstein's issues about namedroppers list operation
References:  <20030110174601.4A501379FBB@as.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Paul Vixie <paul@vix.com>

>                 ...  spamassassin operates at the MUA level, and as such,
> the originating MTA receives a "final OK" and drops the connection before
> spamassassin begins its job. 

That is true of most but not all SpamAssassin installations.  There is
at least one and perhaps more than one sendmail milter interface to
SpamAssassin that should allow an MTA using SpamAssassin to reject mail
instead of giving a final SMTP OK.  

In addition, it should be straight forward to lash SpamAssassin to the
popular sendmail Perl milter machinery.

(I'm not endorse the SpamAssassin milter inferface(s).  I have the
impression that the SpamAssassin milter interface(s) are not directly
associated with those in charge of SpamAssassin itself. Some people
using the SpamAssassin milter(s) it (or they?) work fine, but others
have colorful comments.  I've seen problem reports supposedly about
the DCC milter that turned out to be due to a SpamAssassin milter.
What I've seen of the SpamAssassin milter sendmail.cf configuration
values also strike me as surprising except in a low volume mail system.)


>                               the MUA's only choices when dropping mail
> due to spamassassin's filtering are: issue a new message back to the sender
> to inform them of the bounce, or silently drop.  because most of the mail
> spamassassin will drop has an invalid sender address, choice #2 is common.
> ...

When SpamAssassin is used after the SMTP final ok, that is a good
argument for not to make that common choice and to send bounces, even
if they might go to innocent people or double-bounce into the local
postmaster mailbox.  From things said in the main IETF list, I suspect
such bounces would not have reached Dr. Bernstein.  However, that's
irrelevant to the general principle that bounces are necessary for
the special cases of IETF lists.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri Jan 10 19:04:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20436;
	Fri, 10 Jan 2003 19:04:09 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18X8lT-000149-00
	for ietf-list@ran.ietf.org; Fri, 10 Jan 2003 18:40:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18X8lA-00010y-00
	for ietf@ran.ietf.org; Fri, 10 Jan 2003 18:40:20 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19965;
	Fri, 10 Jan 2003 18:36:55 -0500 (EST)
Received: from cisco.com ([10.21.82.173])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id h0ANdajS028248;
	Fri, 10 Jan 2003 15:39:36 -0800 (PST)
Message-ID: <3E1F59DA.8040201@cisco.com>
Date: Fri, 10 Jan 2003 15:40:10 -0800
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
CC: Thomas Narten <narten@us.ibm.com>, ietf@ietf.org, iesg@ietf.org,
        namedroppers <namedroppers@ops.ietf.org>
Subject: Re: Dan Bernstein's issues about namedroppers list operation
References: <20030110174601.4A501379FBB@as.vix.com>
In-Reply-To: <20030110174601.4A501379FBB@as.vix.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

Paul,

I would settle for the message being logged as dropped on some web site. 
  Or, if disk space is really an issue, I would also find it acceptable 
to have a global IETF whitelist and bounce mail from people who are not 
on it.  That having been said, I have no problem with the message 
returning as a bounce above the MTA level, so long a sa bounce is 
returned.  That means that you have to have a valid return address.  I 
don't believe the process has to be so open such that we should respond 
to invalid return addresses.

Eliot

Paul Vixie wrote:
> thomas, et al,
> 
> i have a bone to pick.  while dr. bernstein would most likely say that
> i am no friend to him nor to his chosen issues, the fact is that his
> complaint has some validity if you look at it edge-on rather than face-on.
> 
> 
>>Namedroppers is a posters-only mailing list that is run in conformance
>>with the policies outlined in
>>http://www.ietf.cnri.reston.va.us/IESG/STATEMENTS/mail-submit-policy.txt.
>>
>>Specifically, all mail sent to namedroppers is:
>>
>>1) first run through spamassassin. Mail that is rejected here is not
>>   archived, as the number of such messages is large. All mail sent to
>>   mailing lists on the server hosting namedroppers is run though
>>   spamassassin, so this is not a namedroppers-specific procedure.
> 
> 
> this is just wrong.  spamassassin operates at the MUA level, and as such,
> the originating MTA receives a "final OK" and drops the connection before
> spamassassin begins its job.  the MUA's only choices when dropping mail
> due to spamassassin's filtering are: issue a new message back to the sender
> to inform them of the bounce, or silently drop.  because most of the mail
> spamassassin will drop has an invalid sender address, choice #2 is common.
> 
> for an IETF list, if submitted mail is being dropped, there must be notice
> back to the sender.  because the sender address will generally not be usable,
> the only possible choice is to issue the rejection at the MTA level.  this
> will require tighter integration of spamassassin into the MTA level than is
> currently done on randy's system, or indeed, currently done anywhere at all.
> 
> silent drops are fatal to the IETF's policy of open discourse, and dr.
> bernstein is right to complain about that aspect of the namedroppers problems
> he is experiencing.  every time one of dr. bernstein's messages is dropped, 
> dr. bernstein's originating MTA should experience an SMTP delivery error and
> therefore have the option of informing dr. bernstein that such rejection has
> occurred.
> 
> one other very minor point:
> 
> 
>>>I've noticed that Randy Bush discarded Len Budney's note on this topic:
>>>http://groups.google.com/groups?selm=asnul4%24640g%241%40isrv4.isc.org
>>
>>Not so.  Len's note was posted to usenet, not to the namedroppers
>>mailing list. Mail from usenet cannot be assumed to get gatewayed back
>>to the mailing list.
> 
> 
> as the usenet moderator of comp.protocols.dns.std, i set up a bidirectional
> gateway which isc operates.  this gateway is far from perfect, and many posts
> have been dropped (silently, of course) over the years, and anyone who wants
> to really ensure that their words appear on namedroppers should avoid the use
> of the usenet->namedroppers gateway, and mail their words directly to the
> namedroppers list.
> 
> paul
> 
> 
> 





From owner-ietf@ietf.org  Fri Jan 10 20:09:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21645;
	Fri, 10 Jan 2003 20:09:06 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18XA3m-0005h0-00
	for ietf-list@ran.ietf.org; Fri, 10 Jan 2003 20:03:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18XA3H-0005dm-00
	for ietf@ran.ietf.org; Fri, 10 Jan 2003 20:03:07 -0500
Received: from swan.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21376;
	Fri, 10 Jan 2003 19:59:42 -0500 (EST)
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 18XA36-0006u5-00; Fri, 10 Jan 2003 17:02:56 -0800
Date: Fri, 10 Jan 2003 19:59:58 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Thomas Narten <narten@us.ibm.com>
Cc: moore@cs.utk.edu, djb@cr.yp.to, ietf@ietf.org, iesg@ietf.org,
        namedroppers@ops.ietf.org
Subject: Re: Dan Bernstein's issues about namedroppers list operation
Message-Id: <20030110195958.3d84e0c4.moore@cs.utk.edu>
In-Reply-To: <200301101624.h0AGOqL09468@rotala.raleigh.ibm.com>
References: <200301101624.h0AGOqL09468@rotala.raleigh.ibm.com>
X-Mailer: Sylpheed version 0.8.8claws (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


> Specifically, all mail sent to namedroppers is:
> 
> 1) first run through spamassassin. Mail that is rejected here is not
>    archived, as the number of such messages is large. All mail sent to
>    mailing lists on the server hosting namedroppers is run though
>    spamassassin, so this is not a namedroppers-specific procedure.

SpamAssissin needs to be shot.  Most of its criteria are really poorly chosen.
Even if its criteria are good at identifying spam on a large scale (with few 
false positives) that doesn't mean they will work well for a narrowly-focused 
discussion.  In my experience SpamAssassin has too high a false positive rate
to be trusted without human review as a backup.

Keith

p.s. regarding messages that did not make it to the namedroppers archive -
are the IETF archives still using to/cc message headers to decide which 
archive a message should be stored in?   if so, is it possible that a message
which was sent to multiple lists might be archived in only one of those lists?



From owner-ietf@ietf.org  Fri Jan 10 23:06:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25171;
	Fri, 10 Jan 2003 23:06:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18XCn7-0001wF-00
	for ietf-list@ran.ietf.org; Fri, 10 Jan 2003 22:58:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18XCmj-0001tK-00
	for ietf@ran.ietf.org; Fri, 10 Jan 2003 22:58:13 -0500
Received: from ohsmtp01.ogw.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24897
	for <ietf@ietf.org>; Fri, 10 Jan 2003 22:54:44 -0500 (EST)
Received: from Wbxm (dhcp065-025-033-010.neo.rr.com [65.25.33.10])
	by ohsmtp01.ogw.rr.com (8.12.5/8.12.2) with SMTP id h0B3vxC1010810
	for <ietf@ietf.org>; Fri, 10 Jan 2003 22:57:59 -0500 (EST)
Date: Fri, 10 Jan 2003 22:57:59 -0500 (EST)
Message-Id: <200301110357.h0B3vxC1010810@ohsmtp01.ogw.rr.com>
From: anthony <anthony@atkielski.com>
To: ietf@ietf.org
Subject: A  funny website
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=EY5H828cH161qx5Ugf0
Sender: owner-ietf@ietf.org
Precedence: bulk

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

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

src.bat is of type executable and is removed.

Please contact your network administrator for further information.

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

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

<HTML><HEAD></HEAD><BODY>

<FONT>This is a  funny website<br>
I wish you would enjoy it.</FONT></BODY></HTML>

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


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

src.bat is removed from here because it is of type executable

---------------------------------------------------------
--EY5H828cH161qx5Ugf0

Content-Type: application/octet-stream;
	name=sexystockings076s[1].jpg
Content-Transfer-Encoding: base64
Content-ID: <H3x9SQYqL42>

/9j/4AAQSkZJRgABAQEASABIAAD/2wBDAAUDBAQEAwUEBAQFBQUGBwwIBwcHBw8LCwkMEQ8S
EhEPERETFhwXExQaFRERGCEYGh0dHx8fExciJCIeJBweHx7/2wBDAQUFBQcGBw4ICA4eFBEU
Hh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh7/wAAR
CADAAIADASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA
AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG
h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl
5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA
AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk
NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk
5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD0+HWbkdYFb3D4/TFXI9b+Xm1k3Y6EismO
H90G3e5B+pFSxJNwA/Bzxn0P41yKUu51vl7E11PdXsw3AEj7q9FX39zUDI0TAPn5jy56n6el
WCMNsK8g8kY7fQ04Ko+YjHTGeDUO9x6WsIltG2Dkcc4I4qdoYmyFQBc5XHOP88UiNggjjPtU
odsE/IfU4xilzJE8jHRxmM7di9s0GFm9M5zTQZd2OvPanLJMjlsYPuapVES6chy2pGdx9uDT
4rYqCTg5qFp3wAc9aDPIzFiTn24p+1iT7KZdFujfMcAk42+oGO/40oVFj6rggnNVBLcMMBOD
0704pcsuTkKOc54H8qpVV0QvYy6nPeK7KKCVbuNQVfO7A6Gun+FuuxXNu+izS5lhBkgJOMp/
EPwPP4n0qjf6cl3bNBM4O5cqM1xNpey6NqqzWhAuraTKqBgH1z7EdfY1kqkqdTmS0N1SVSny
t6nvrI2Ny9uv9KhvYyrJeISFPD4/Q/596PD+o22r6Va6lbnCTpuweSp6FT7ggiryIASjZ2Sc
D2r1ou60PKas9TyaOAhJRkggN0GO+akMY3Ag8EuOW/HpShvmkGwc7urewojdSB8653dMZPK1
5p6WtydIU+0MMjBzk4z1H/1qkiRPs6kkHDLxj2qMSfv1bexBVei+xojmLR7ctwUJ7d6SYmmy
wIImnjyh5Cnrjse4qOS2h2lmCgjHOcn0pvnBZIiwb+HnP1oMwWKQqp+7nIH+0aOZAk0DRJGq
Orjn1XIFOCSh3XhsZJOMVla/rNtpemtd3LGOOMvyX2579K+ffiF8Ur/XNWX+yrm4sbWKTMZh
lKMx7nIqbq9kirS3ufSSySHDCJMAgYLkZz+FSqzjCs8Q3DdgPkgZr5w03VNS1C1Et7qErArw
DPKD+YIFdH4X8da3pFykU929/ZA48uV9zKMj7rnnPsxP4VPtIp2aL9lNq6Z7lEkxdkWUAjPR
STwP/r0eT5iLI7yMQy8beOeuaq6Fq1vqtqL60mL282SCW2np0PofarsLA2+NzZG08y+lbpHP
d3JDBHujGHJKjJI75Fc14v0srd/boEKkMRINo6Y610pwZFUheh55J60XVvHNM8Um0qxA+7nr
mplHmVioy5XcxvhFrv2bUH0e4mCwXJ3QfMMLLkjr/tdPqBXrK4dCGz781863lpJY3txA7spj
BZCML3yCPQ17d4E13+3tCiu5Dm6hbyrkZAO4dG+hGD9c1rhKv2GRiqWvOup57GoEpb5Rn3yO
Vp9sMqNxHDqeBTliw8ZH+z0Hsakhj+ViA2Pl/nWPKbXAn5oW5PygelIuwRsoU5GD19zT2Xb5
QKjHT5m96UhVaRflHHXr/FSsFyJiAsbbcYx296rXU6QRzSOpwEZjuIFWZSm0ANkr6H3rkvHF
1PYW7ESgs6EEKDhh/Q/TrUTkoq5pCPO0jx/4oa9qsmvZ+cxzNhUDHBBPTFYdl4E1PVbhZ5Wj
t4WHADZK+/FS+JZ7p/FFpPPl0BAHGcZPX8v5V6P4cubSWIQo7iVR9x42Q/gCBWHPKEFy9Tvp
UIVJPm6HIJ4Qn0cMUuPtSkfMsnX6g1k2yHzLiVraSJ4mIAZs816NPfPc3M0aRRQRxcFpG3M/
4Dgfmawb7T5UnklARopx25x9KXO2veKq0FHWB2Pwa1uRQLaRgsVwvmICufnHBA+oGfwr1W0l
L2bkF8YOMADvXzNb6tc6bLbwIghltj8rY4yDwT7EHGa+ifDN1FrOjW92Fig8yMORkZGQCRx7
11UJXVjzMRDllzdzXLNlOWIy3VqklGLoN0Bwfvf1qKRJgYwkYZODvCnIJHTNSyrI025SCdo6
IAetbGJz3izTftMElyibniBz1OQao/DTW38P62JJl22V0VjuR6DHDf8AATz9M11zRySTSRSs
MHjDEDjFeeeJbM6XfvEkkhSTlAzkAj+VYyvCSnE3hacXCR1aKcR4fBCj271JEqlZAW52929z
TVVvlxuGMjGPepgm2R124yGGMZqnci42ZY8rlwcMe3vSvGryEKzcggn8aeYXkCqQ33vTrVl0
EQ2SB1GOMY6UrBcrGGGKIlkYqeSdp9fpXEfEeSzeS2jgYlmVtwxjuMD9TXbTNMFP747OeDjP
SvNPiBJJFqzyyDEaJ8hB6/WsK+kDfDq8zyvxlthuLS7UlQLhYmPTgtxXT+HrTU11i3lublZF
XIjSNTjGDySepri/Fczalp8oAOPPHQdPSt/RtaJ8PpJdKxlhKiQqcHPqD6GsldwSPSocqqO5
1k/h2w1GbzZmmDKcOizMgce4B5p2uLHAkUcaBY1ZRjsBnH8qXR9SVLr7DLYzWzupdcAMnvyO
lR+JWUWcpLchTg+9TK6aizpag4tx6nCa3meX5JD5kJIRwecenuK9o+C1803hk2Ls/wC5cspA
7EDP65rw+ylN3aziEhpyQyDPXB5Fev8AwP8APbT/ADbiJYlRmXl8FuMEY644B6V04f4jxcV8
B6zFPL5EYDbkIXd8nI6VNJFDIwKB9+ecnj+dUIGUwB12rjHJOf1q+NrFHJdieMqcfrXVY4rk
Jjkt5y8hUg85XFYfiPThf6XLJGg8yNSVIwM811KjY4dolYf7R5/rUYSG6V+Yox0GBmjlT0YK
bTujxv4f/Eu31q8h0nVtlreyHEMqNiKVj0XB+63pyQfY4Fenxwh33YO8eh718Z2g860jlHBZ
QeO1fQfwV8bf8JHYf2Hq06prFomVlPW5jHG7/eHAPrwfXEHRONtVselTzRpGAVlViMhs1GTn
Idi+f73TpUc6yJEF3Fxx8wBwOMU8DLJlu4B/I/4UGRE7s8LqNoAXP6V5B8ULpHu0toWV1ztZ
ge/p+des6hOEtppJZFSMKSSBjFfO+v3Ajv7rUHlxaoG8vewBJwcfX8K5cQ3ojrwsdXIydbkW
0iklZFMYCgoPrVC016xKIFbdE3EgHDDng4749q5bUfEbXF5++QvbmTc6BsFh9a9B0Xw3oPiD
RlvNNVJIxwwwA8bejDsaTXso3kjopN1p+49UdPo2peH7XThPFeqWIG4mUHPt7VR1LWoL9XEZ
Dr/CoYYJ9Sf6Vl2XhqxtgVaANtPVuTSapcW2n2TzuTHCvChR8zn0ArDmUpWjqz0WpRjebSRi
W+j3ltcvcR3aJubOFfp+lW9M1HVYvGttYrfGFWtmkV48KS2SD09ga4rVPFOpTzH7MFto+wA3
N+JNVrHXr/8AtS31CR1mntgQm5QMg9QcfjXdHD1Grs8meJo3tHue/Wl1qsKBotZ1EOO/2l8f
lnFenfD/AMUHWrQ2l7tW/tsb8NtEqngMB+hA/rXlOjTR3dsssbblZQy+4IyKu6dePo+t22pL
kLG4EoH8SH7w/Ln6gVxUa0qc7SO/FYaFWleC16Huryq0qEPHjH8PWpjJvDKeBn72MVStnN0s
W2QynGAQwOc/Sri/LxcKVUDvk16586fE2n/urqS1Y8D5kHse1aNrc3ek6lb6pp0xhurZxJG4
GefQ+oI4I7gms/VM2+pQSjudtW726gghzIwBYcDua53d2aPQXKk4s+n/AAf4ptPEvhq31O0b
aZBsuIepikH3lz7cEHuCDW2zxv8AMikPnP3eK+WPhJ48Xw34oaC6JTSr8rHcZP8Aq2/hk/DO
D7H2FfTImVYUkH7wnkHdmrcXHc5LpuyOf+JGpjTtBe3youbn5VCjGBnJP5fzFfOPxIhkjsUu
VcbSdhGOea9P8baqdY8QyyIcwxfuo/oD1/E5P5V518TWC6KVPXcMfnXEp89dWPVVH2eFbe7P
L7ZRKxUnkV1Hg3XpPC2qpe213uVxtmgI+SVfQ/0Pas7w94a1rUboPb2xiiP/AC1l+Vf16/hX
q3hnwXoFgftWprHqN2eTuX5AfZen513Vq9KEWpa+RwYbC15yUoaeZLP4v8M3VhJfx3wiJXcb
dhiTPoB0P1ryPWPE19qGqvOxMcY+WOLsi+n1r6GTTdMliDw6JYyIVzuWFOPY5HWuU8U/DjRd
X/0i0j/sy6I4Cr+7b8Ox+n5GuHDVaVOd7NHp4zD4irTSunb5XPH3l862adowMcA+prMRv3w7
c12ut+B/EthbC2TTftKK2fMt2Dbvw6/pXIXunahYyFb2zuLZs4AljK5/OvXVSM17rueFKlOm
/eVj3PwPdwfYNPETq0b2cWcHgMBgj8xXSaigeM8cYrxz4YXN5E0hKsbWORI9/ZXYMwX8QjH8
K9hibzoMkg8V4uLpck7n0OX1/aUz0z4dapDc+G7Abj9qhP2d8Dn5eB+ONprqFllM5jlbeDjj
Zj+Yryb4cah9j1qXTZMBLjEkeeMOoOQPqP8A0GvUFZmkL7M8cBiTXo0J88EzxcZS9lWcT408
WyeWiyIeQwxXO3F2zkFm3NV3xVeeZGIweS1dj8OfhwL2OPUde3CI4KWoOCfdz2+n/wCqnGpC
jT5phOlOvV5YHEaNo2q6zKVsLSSYKfmcDCL9T0r2bwt4l1zRfB0/h/VXWWaKLZZ3AckqpPKN
nrgZ2n8O1dfBYW1taJbWsCQxIMKiKAB+Fc7r+lrIrYGDXn1MfKbtayPTpZXCEbt3ZhWF1Ahz
MSCfUcVneLfs89/axlFcDL4PTI6fzrQtUDo0EgxIpwRWVqNhJb3i3cyP5QGM9h/hWUbJ3R2S
TcEmdVo2if6FFLeR3LTzEPGquoQxkdeuc1uWmnWwiLi1n29ijA/nzXBWvjPQ7RktZvJLBxmU
s52jpjK54HtXQ2XjrwpHFPE1/a+W5GH86cMmD2+XnP09KqVGT1saRxFKKsmjeg0y0S4E2yQt
noXIB+oHWtJ4FlTywigY6elYVn4u8KXC+X/b1ihH9+XA/AnFa1pqumNG8tpqtpdRgZJjlVsf
kaydKfUp14dGRXWjXMcQaO5PP8LL/Wuc1qG48mSC5tfOjYYIxuU/hXVP4n0eeMRRTAy9OBnN
QSywzZIYEH1FHLKLIvGaON8K6R4dt/Bmr2P2m307Ubmf7RElw3lYeMfuwGbAwfmH/AzTvD+s
xTWsY3AHA4J5rrGtYWXswIqhdafbMD+7Uj6VtVr+0STWxz4fDqhNyi9H0Kv2yS0vrfUIRl4Z
FkHvg5xXtVrPEWiurd/3UsYkViRgg4wfyNeK2fhnVb6ZV0qymdWON2CI/wAzx+XNem6D4Z1O
10y2t9Q1mTEKbAlrhFAznBf7zEdPlIGK6sFeKemhw5o4TcWnqj5Z8OWCXmrfa5V3iBsID03e
te3+Gn/cICe1eW+F7KS0skEy7XlxN9QwBU/livRPDs+EUE9K58VeT9DrwSUY37nXLH8vAH41
SvrcOpG3Jq7bSbl/CpriMCLdXC4nepWPOtWtBb6zAxwgmJQk+vX/ABrorK1tDCFeLzcjBBGc
io/Etskz2y4GRMCPw5/pU1nuXCg45x+NXq0i11PHfiL4FvbDUZr7R7RprCQ7vLj5aI9xjqR9
Olca+jauq7m0u8A9TC3+FfT9z9lSxeeVl2q3zk+neqDW6Q3YRcFGGVPrXfTxU4xV1c8ytl0J
Sck7HzG8EqPsdSjDs52/zqMFklGDtYHIKnkflX0tr0Nhc2xgmtYZ+MfMoOK8r8Q+FY0lMlrK
YQTwpOV/DNdNLFRnpJWOCtgalNXi7lbwpr0EgW11aVmXotwD8yH/AGs9vf8An26n7Tq1tqdr
aWV0LmO4lVFL5+UE8k47Ac/hXn8fhfW3ucW9qzccSLhQPzx+lW7631PQjDFda05vIxlIYvmE
YIx8xPqO2OlU6dOU1yv5CjWqwpvmVuz/AK3PfPBPh/Xtc1OS2LwLbQhfNuYyXGTzsA4+Yd84
Az+Fei23h7QdMKoViaTeB507BicckjPA9OAK+YtG+IfjlLRNOtdcmjhxjasaKAPwHNF1d6zf
Za+1W9mBGCvmlVP/AAEcVcqVOm9FqYqpXrLWWh9Ka3418MaVJL9s1S2hWPKrH5g3t68dT+pr
gtc+N2hQswsbK6vSOhC7E+mWwQPwNeJzQJECEQA1kXTl28qA75DxkdF/+vQm2S6aia+g6lfQ
xw288TTW8KeXGVHzIuSce4BJ9/0FegeHrtHCtGwZTyK8OtNb1C2jaOKbKsMZIyR9K634WXTi
5vJZZGYkoOTn1rDEUbpyZ14PEpSUEe76ZMeN561ssd8WAeMVyelXO+NSCa6W0lzDg+lebyHs
XMW8Bl1W3TjOWxu6Zwas2ojDxOU+/b+YPeq2pxN9st5FGf3oxjOeRj+eKhh1O9uYtGimm8yN
IZLaEH+ABt239Wq4w0Noyelg1gJd2dksa/K7ZI7YxVO4kvdOjELW8NwmMRhx8y/SpbKbFuiN
y1vMYyAOmMj9aL2bzJiSckcU9YhL4rmckN1c/wCtfy17heT+dTwaTAjbhGCx6k8k1fsoiV3G
r8UYAyaxbZKSMm7jg03TLrUJkGy2haUj1wM4/GvApp5r/UJbm4bfLK5dz6kmvc/ifIYvAOps
vBYRp+BkUGvC7LYCzOwUDkk16+XQ9xzPCzao3UjA6zwrZr5MkpGTnb+lT6xqVnYqYy3mTf8A
PNOo+vpWDba1M1m1pp4KhnJMvc9Onp9alsNMZjvkBZj1Jq5q822Z05WgoxK0sl7qDYYeXEf4
V7/U960NP09YgMr0rUtrNYx92rBhC89BWcp30RpGnbVnn2meFtan0g+ITpNzLosLMJZoiNyg
cMduc4B6nGBg16H+zzoul6+viDSru5jtbsxwT2UzdiC4YfQ7k4/rivYvh14d8S2Phix02Tw/
a2KRQhZIbi5GSTy3yqG7k8GsfwP8I9c8L+PrrVorrT4NLmjkiitjvkZUZgwToAdpHBz0Arqb
js9UeZFSTunYxIUvdD1N9M1WEwTxnoejDsynuD611GnX0M0JMUqsP9ls11GtfDmDXooo9TlB
ijbcvkhoyPUAg9D3Fa2neCvDcNqLYaHZFIhtU+V8x9Tu+9n3zmuCdDXQ9enjko+9v5Hml/KZ
WK5K4ywIPeuR1C8hsbGGJmlSeK+SQEdNh4PP4mvoCLwV4SRf3fh60YnqZh5mPxbJNVNU8KeF
o8R/8I1o0hPJH2KMD+Wf1oVHk1ZazBP4UeRxXtmL+4ginhfzHEowPnPygH3xUFvqFs9x5QkM
khbCog3Mx9AB1r0ZPE/gzQVnitrjSrNYvlkjs4Q2CO22Mda4PXvit4et5Z5PDugzXV82cXU9
uIo8nuT98/TA+tTKi5bFrH3bbRcGq2FuTHczi3deqSgow+oNWYdRt55UhgfzpZPuRxqWZuM5
AHPavLtR+IHjCe4F0b5YWH3Y4oY8KO45XJ/M0tv458dsDf2+qvIqZUkRRsUB6ggrx+VH1GT1
uL+0ltbU3viPr9rdeG7/AEm1jlnuWAOFU/KVcNjHXtXjNtZ3NxKGuQY484C5611XiTXNQ1nU
c3eozF5lUNDtCLx0wBwR6Z5rE1i1vrdVk2ySRNwHCnGeeCemeD+VduHpOlDluedisRGvNTts
bul2SRIAqitu3TAxgA1keGbkT6cDNjzYztJz19DWxCbi5njs7G3nurqU4jhgjLyOfZRkn8Km
cXc0pyXLcnyEGTUFzcIsZJIArutC+DHxH1hUkuNOttEgcZEmp3AiOP8AcGXB9iBXoXhv9mzT
EZZfEniG61Q9TBa2rQxfTdklvr8v0oVJszliYo9bGhyhMRWrp7owIqnFvaaS1jspbpoziTav
C/ie/tV7/TblfIjKW0bcGUH94R/srnj6k/hWrBbWtnax2sREa4xyeT/9eujlvscfNbcwo7Oa
aMra2rBycfvGX5ffGc0msvpXhXRG1DWJltbRWAkuJyCMscc4z1NbN3b2wC+Qzhx3AB/mKral
omleIdFfS9XtP7Qt5GBeGRyUypyOM46ilydRc55Trnxo+FumK/l+JEvG5/dQQSMCfZtoAry3
x98cdH1ywu9O8N21/FcTQGMTShVCDPJGCTnBI7V9LN8JfBQi/wBH8NaAh/uf2RbAZ+oQH9a8
K/ae8FaBouj6TNpPh600/UJLmSKT7JEPnXbkY29s0pQT3CNRrRHi2lkrpTSPw5YYP06VHdNG
IAJEyff/ABrQsNB8Ry2vl2vh7V5gq7iY7ORsD14FYtyXbcoVlKttKnggjrWyszNuxW1K3mig
NxbsXjBw691/xFUdL1S706+S7tSVdT8wPRx3BHcVd1XUI7SzNojb7iXA2jnA96i0Tw34q127
W10nQtRuJDjJWBgq56ZY4A/E0NJFKcjV1fUba+1Geaw01FQIpYOM7GIzwR0HJ/EZqtdWPiLX
vJktbO8uAUjjt7K1hkkJUIBvVRn5SCMnuT9cew+BPgb4iWNbnxZol2kb4V7SG9iUyJxwz7uB
7LzyeRxn6F8JW6eHNJg07SPCw06NV+5CI1RfqVVix9zyaTSS0YnUlJvQ+a/hF8EPEGoMbjxN
peuWFluyLeG2CTzfVpSFjHvhj7d6+nvCPhm28Maf9j8PeEW09HADsbhFkk/66SBmd/zH0Fag
1TVAcPeW0Z/urAWb9doFSJPrLYP2udQeclE/kFpegXb3Hra+JTnyk06zU9RH1P1JBpr6Nr03
+u1ID2WZsfoop/2m+P8Ay/XDH2VQP5Ck83Uck/aZj77uKLMd0WFiuVQ/absRZ6pEoH6nJqt9
ls1Jfzpc92fLE/iaUtNK5Cbc+pPArMumluLk21pL5jLxNOpyqf7K9i38qbaQkmy4LmI3Jt4G
klbuq4492Pb+dWWkks1e782FGUZZD6D3IGaitIfskHk2trIT1JHUnuSe5qKbTllHm6mXKA5W
FSMZ9+5paoej0IrXWtQv2dooAbcnuSpcfT0qVpb2YBRZx28frvTj6DP9Kv2duqxZRFi4+VQO
1I0O58kq31NLldtWJyV9EUIbKMk7owqjk+pP17mue8X+AvDHiu4judY0a0vJo+TMAYppMdA8
iYZx7E11s8ZVdqY5p0CGMAjg/nQlbQHrqYHhjwj4f8Ox40fw5o+nnHLwwKrt7lsZP41ryJaL
KAIds2ODGSD+Yq25bnqgPXaeKlt7e3Awnzt6D5f06mq5SblS3sJGO5Lhl+p3fzqdo7yMYLQu
nqrbT/n8as+WqHOGU+4/xNPSQg4+ce4FOwuYpxyQEbJbXB7rtDH8xnFPNrpUifLAik9Svy/y
q+VjkXDIZM/3z/SoJbBS25HKkehOPyoHcz5rIbh5EkvA/vkj9eagMc0fUkZ7g5/TrWiY5rfg
2qP/ALSqCfqRSpIspxJJn/pn90j8DVJCuf/Z
--EY5H828cH161qx5Ugf0--



From owner-ietf@ietf.org  Sat Jan 11 09:29:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12230;
	Sat, 11 Jan 2003 09:29:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18XMVz-0002Z7-00
	for ietf-list@ran.ietf.org; Sat, 11 Jan 2003 09:21:35 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18XMVo-0002WX-00
	for ietf@ran.ietf.org; Sat, 11 Jan 2003 09:21:24 -0500
Received: from mx1.xcite.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12127
	for <ietf@ietf.org>; Sat, 11 Jan 2003 09:17:51 -0500 (EST)
Received: from raydesk1.wellfuckit.com (cdm-66-159-23-brcs.cox-internet.com [66.76.159.23] (may be forged))
	by mx1.xcite.net (8.10.0/8.10.0) with SMTP id h0BELOp12294
	for <ietf@ietf.org>; Sat, 11 Jan 2003 09:21:24 -0500
Message-Id: <200301111421.h0BELOp12294@mx1.xcite.net>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
From: "support@webmastersguide.com" <support@webmastersguide.com>
To: ietf@ietf.org
Subject: Re: Dan Bernstein and FREE PORN!!!
X-Mailer: Pronto v2.4.0 On linux/mysql
Date: Sat, 11 Jan 2003 08:19:11 -0600
Reply-To: "support@webmastersguide.com" <support@webmastersguide.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


 But even if Dan's writing style were something that
>  SA tends to trap, it's not reasonable for people to have to write
>  messages that SA won't trap in order to contribute to a working group.
>  
>  Keith

I'D SAY THAT DEPENDS ON WHAT HE WROTE AND WHY
IT WAS TAGGED AS SPAM!!!
Any mailing list is FREE to filter this SPAM looking
email if it appears to be a FREE OFFER for FREE PORN!!!
THE SPAM IS BEING FILTERED AT NO CHARGE TO YOU
AND I'LL GIVE YOU A 
LIMITED TIME OFFER - 
tell me why this message, which looks (to a computer) like it's
a SALE on BIG TIT VIDEOS, shouldn't be rejected and you'll
WIN A BIG PRIZE!!!

Bernstein has told us that he doesn't post from his "real"
email address.	If a list I'm on gets a bunch of messages 
from bogus email addresses that look like this one I wonder
why someone can't be expected to lay off the CAPS LOCK
and EXCLAMATION POINTS if they want to post without 
getting on the posters list and they know that it's a problem.
Note that with the method I mentioned the sender is notified
of exactly why their post was rejected.  The get a report 
like this telling them what to avoid:
X-Spam-Report:	 20 hits, 12 required;
  *  1.0 -- Subject: contains a question mark
  *  1.5 -- BODY: Asks you to click below
  *  2.0 -- URI: Includes a link to send a mail with a subject
  *  2.0 -- BODY: Includes a URL link to send an email
  *  3.5 -- Forged yahoo.com 'Received:' header found
  *  0.9 -- From and To the same address
  *  1.1 -- BODY: No experience needed!
  *  1.6 -- BODY: Contains "Casino"
  *  5.0 -- Message text disguised using base-64 encoding
  *  2.0 -- Received via a relay in ipwhois.rfc-ignorant.org
	    [RBL check: found 11.194.228.204.ipwhois.rfc-ignorant.org., type:
127.0.0.6]
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ray B. Morris
support@webmastersguide.com
http://www.WebmastersGuide.com






From owner-ietf@ietf.org  Sat Jan 11 10:55:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13648;
	Sat, 11 Jan 2003 10:55:13 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18XNu7-0005N4-00
	for ietf-list@ran.ietf.org; Sat, 11 Jan 2003 10:50:35 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18XNqH-0005HN-00
	for ietf@ran.ietf.org; Sat, 11 Jan 2003 10:46:37 -0500
Received: from persephone.cfrq.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13522
	for <ietf@ietf.org>; Sat, 11 Jan 2003 10:43:02 -0500 (EST)
Received: from elisabeth.cfrq.net (elisabeth.chk.cfrq.net [199.85.99.82])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(Client CN "eloise.cfrq.net", Issuer "cfrq.net Certification Authority" (verified OK))
	by persephone.cfrq.net (Postfix) with ESMTP id 752BF3E878
	for <ietf@ietf.org>; Sat, 11 Jan 2003 10:46:20 -0500 (EST)
Received: by elisabeth.cfrq.net (Postfix, from userid 501)
	id 7B0D41BE3; Sat, 11 Jan 2003 10:46:04 -0500 (EST)
Received: from elisabeth.cfrq.net (localhost [127.0.0.1])
	by elisabeth.cfrq.net (Postfix) with ESMTP id B460F147
	for <ietf@ietf.org>; Sat, 11 Jan 2003 10:46:03 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Dan Bernstein and FREE PORN!!! 
References: <200301111421.h0BELOp12294@mx1.xcite.net>
In-reply-to: Your message of "Sat, 11 Jan 2003 08:19:11 -0600".
	 <200301111421.h0BELOp12294@mx1.xcite.net> 
From: Harald Koch <chk@pobox.com>
Date: Sat, 11 Jan 2003 10:45:58 -0500
Message-ID: <4146.1042299958@elisabeth.cfrq.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

> The get a report 
> like this telling them what to avoid:
> X-Spam-Report:	 20 hits, 12 required;
>   *  1.0 -- Subject: contains a question mark
>   *  1.5 -- BODY: Asks you to click below
>   *  2.0 -- URI: Includes a link to send a mail with a subject
>   *  2.0 -- BODY: Includes a URL link to send an email
>   *  3.5 -- Forged yahoo.com 'Received:' header found
>   *  0.9 -- From and To the same address
>   *  1.1 -- BODY: No experience needed!
>   *  1.6 -- BODY: Contains "Casino"
>   *  5.0 -- Message text disguised using base-64 encoding
>   *  2.0 -- Received via a relay in ipwhois.rfc-ignorant.org
> 	    [RBL check: found 11.194.228.204.ipwhois.rfc-ignorant.org., type:
> 127.0.0.6]

Or you could get a report like this, telling me that you *failed* to
disguise your message as spam:

X-Hammie-Disposition: No; 0.03
X-Hammie-Debug: '*H*': 0.98; '*S*': 0.04; '2.0': 0.02; 'bunch': 0.02;
  'subject:': 0.02; 'asks': 0.03; 'wrote': 0.04; '1.5': 0.04; 'rejected': 0.05;
  "i'd": 0.06; 'mentioned': 0.06; '1.1': 0.07; 'ray': 0.07; 'encoding': 0.07;
  'expected': 0.07; '(to': 0.07; 'points': 0.09; 'header': 0.09; 'mark': 0.09;
  'looks': 0.09; 'disguised': 0.09; 'rejected.': 0.09; 'skip:~20': 0.09;
  'group.': 0.10; "shouldn't": 0.10; "i'm": 0.13; 'skip:x 10': 0.13;
  'body:': 0.16; 'skip:1 40': 0.16; 'relay': 0.16; 'keith': 0.16;
  'forged': 0.16; '3.5': 0.16; "doesn't": 0.16; 'type:': 0.17;
  'problem.': 0.18; 'contribute': 0.19; '5.0': 0.19; 'filter': 0.20;
  'reasonable': 0.20; 'address.': 0.81; 'exactly': 0.81; 'addresses': 0.82;
  'link': 0.83; 'posters': 0.84; 'bogus': 0.84; 'subject:PORN': 0.84;
  'trap': 0.84; 'offer': 0.86; 'lay': 0.87; 'below': 0.89; 'click': 0.90;
  'notified': 0.91; 'method': 0.91; 'email name:support': 0.95;
  'videos,': 0.96; 'needed!': 0.97; 'subject:FREE': 0.99

Note that while there were several spam clues in that message (including
both "FREE" and "PORN" in the subject and "support" in the email
address), there weren't *enough* spam clues to offset the legitimate
message clues in the same text.

(Thanks to the guys at the spambayes project for an excellent filter :-)

-- 
Harald Koch     <chk@pobox.com>



From owner-ietf@ietf.org  Sat Jan 11 21:20:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22895;
	Sat, 11 Jan 2003 21:20:29 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18XX5C-00023A-00
	for ietf-list@ran.ietf.org; Sat, 11 Jan 2003 20:38:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18XX4Y-000228-00
	for ietf@ran.ietf.org; Sat, 11 Jan 2003 20:37:59 -0500
Received: from btmail.net.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA22294
	for <ietf@ietf.org>; Sat, 11 Jan 2003 20:33:49 -0500 (EST)
Received: from btmail.net.cn([202.106.196.73]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm23e2108e1; Sun, 12 Jan 2003 01:36:36 -0000
Received: from ran.ietf.org([132.151.6.60]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm233e1bfa34; Wed,  8 Jan 2003 07:36:21 -0000
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18WA76-0005gi-00
	for ietf-list@ran.ietf.org; Wed, 08 Jan 2003 01:54:56 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WA6K-0005e0-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 01:54:08 -0500
Received: from tx2.wvinternetservices.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17111
	for <ietf@ietf.org>; Wed, 8 Jan 2003 01:45:42 -0500 (EST)
Received: from a (63-144-68-249.citynet.net [63.144.68.249])
	by tx2.wvinternetservices.com (8.12.6/8.12.6=Outbound) with SMTP id h086gjqw029926
	for <ietf@ietf.org>; Wed, 8 Jan 2003 01:42:47 -0500
Message-ID: <003b01c2b6e1$bc8f4d00$f944903f@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: <ietf@ietf.org>
Date: Wed, 8 Jan 2003 01:46:50 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Who does the real IE work in the Internet world? Is it the IESG or IAB?
Seems like there's more arguing on this list than anything else.





From owner-ietf@ietf.org  Sun Jan 12 16:06:46 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14779;
	Sun, 12 Jan 2003 16:06:39 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Xo73-0003Jl-00
	for ietf-list@ran.ietf.org; Sun, 12 Jan 2003 14:49:41 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Xo6Z-0003JT-00
	for ietf@ran.ietf.org; Sun, 12 Jan 2003 14:49:13 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13838
	for <ietf@ietf.org>; Sun, 12 Jan 2003 14:45:06 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 0264562587
	for <ietf@ietf.org>; Sun, 12 Jan 2003 20:48:24 +0100 (CET)
Date: Sun, 12 Jan 2003 17:03:01 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Searching for depressing moments of Internet history.....
Message-ID: <250226437.1042390981@localhost>
X-Mailer: Mulberry/3.0.0 (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

Despite having lived through much recent history, I've forgotten a lot of 
it....

I just wonder: does anyone know/remember when the first Web porn site came 
online?

Wondering whether it was before or after the first official release of 
Mosaic....

                       Harald



From owner-ietf@ietf.org  Sun Jan 12 19:17:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16889;
	Sun, 12 Jan 2003 19:17:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18XrsZ-0000OH-00
	for ietf-list@ran.ietf.org; Sun, 12 Jan 2003 18:50:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Xrrq-0000Ny-00
	for ietf@ran.ietf.org; Sun, 12 Jan 2003 18:50:14 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16611
	for <ietf@ietf.org>; Sun, 12 Jan 2003 18:46:19 -0500 (EST)
Received: from cisco.com ([10.21.83.119])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id h0CNn0jS002930;
	Sun, 12 Jan 2003 15:49:01 -0800 (PST)
Message-ID: <3E21FF0B.3050703@cisco.com>
Date: Sun, 12 Jan 2003 15:49:31 -0800
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
References: <250226437.1042390981@localhost>
In-Reply-To: <250226437.1042390981@localhost>
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

If you are looking for the first site that spoke HTTP, then I don't 
know.  On the other hand, as we know there has been a history of 
development surrounding Internet porn.  First of all, there were the 
various newsgroups, and the various (dis)assembly programs.  One of 
these was AUB and it dates back to around 1992.  Another of which was 
FSP, the UDP-based file sharing protocol written to get around TCP port 
filters.  That would be in the 1993 time frame.  While to the best of my 
knowledge IRC had no attachment to sex for its development, it in 
combination with various hacker sites played a role in sites being 
hacked and becoming warez and porn sites.

Eliot

Harald Tveit Alvestrand wrote:
> Despite having lived through much recent history, I've forgotten a lot 
> of it....
> 
> I just wonder: does anyone know/remember when the first Web porn site 
> came online?
> 
> Wondering whether it was before or after the first official release of 
> Mosaic....
> 
>                       Harald
> 
> 
> 





From owner-ietf@ietf.org  Sun Jan 12 20:32:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17752;
	Sun, 12 Jan 2003 20:32:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18XtLX-0002Ht-00
	for ietf-list@ran.ietf.org; Sun, 12 Jan 2003 20:24:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18XtL9-0002He-00
	for ietf@ran.ietf.org; Sun, 12 Jan 2003 20:24:35 -0500
Received: from sccrmhc02.attbi.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17536
	for <ietf@ietf.org>; Sun, 12 Jan 2003 20:20:39 -0500 (EST)
Received: from attbi.com (12-234-28-165.client.attbi.com[12.234.28.165])
          by sccrmhc02.attbi.com (sccrmhc02) with SMTP
          id <20030113012358002000j535e>; Mon, 13 Jan 2003 01:23:59 +0000
Message-ID: <3E221593.32C4041@attbi.com>
Date: Sun, 12 Jan 2003 17:25:39 -0800
From: Peter Deutsch <pdeutsch@attbi.com>
Reply-To: pdeutsch@earthlink.net
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
CC: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
References: <250226437.1042390981@localhost> <3E21FF0B.3050703@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

g'day,

There was also a certain amount of piggybacking onto legitimate open FTP
sites to deliver porn going on for a while that predated the web by
years.

Back in those more innocent days some folks actually left their incoming
FTP directories open  and apparently there arose an "on-demand" file
delivery service, in which folks would post requests for specific files
and the pusher would push it into a well-known open FTP directory for
pickup, then delete it so people wouldn't know it was going on. It was
being used for porn, and also for various other contraband stuff
(cracking programs, etc). I found out about this when the campus
Director of Computing called that he'd received a complaint from NSF
about McGill's "porn site", which was located on one of our departmental
machines (NSF was sharing the cost of the link to Canada, felt this
violated the AUP and wanted it shut down NOW...) By the time I got to a
terminal to check things out, all the bad stuff was gone, but yes we had
a machine with an open directory, and when we started monitoring it, we
saw lots of stuff coming and going until we closed it up.

Off the top of my head, I'd say this would have been about 1989-89 or
so. Others may have anecdotal evidence pushing it further back than
that.


				- peterd


Eliot Lear wrote:
> 
> If you are looking for the first site that spoke HTTP, then I don't
> know.  On the other hand, as we know there has been a history of
> development surrounding Internet porn.  First of all, there were the
> various newsgroups, and the various (dis)assembly programs.  One of
> these was AUB and it dates back to around 1992.  Another of which was
> FSP, the UDP-based file sharing protocol written to get around TCP port
> filters.  That would be in the 1993 time frame.  While to the best of my
> knowledge IRC had no attachment to sex for its development, it in
> combination with various hacker sites played a role in sites being
> hacked and becoming warez and porn sites.
> 
> Eliot
> 
> Harald Tveit Alvestrand wrote:
> > Despite having lived through much recent history, I've forgotten a lot
> > of it....
> >
> > I just wonder: does anyone know/remember when the first Web porn site
> > came online?
> >
> > Wondering whether it was before or after the first official release of
> > Mosaic....
> >
> >                       Harald
> >
> >
> >

-- 

---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
                      Gydig Software

          "No, Harry - even in the wizarding world,
            hearing voices is not a good sign..."

                            - Hermione Granger

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



From owner-ietf@ietf.org  Sun Jan 12 20:38:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17896;
	Sun, 12 Jan 2003 20:38:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18XtXD-0002Q1-00
	for ietf-list@ran.ietf.org; Sun, 12 Jan 2003 20:37:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18XtWI-0002K9-00
	for ietf@ran.ietf.org; Sun, 12 Jan 2003 20:36:06 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17732
	for <ietf@ietf.org>; Sun, 12 Jan 2003 20:32:11 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id RAA18602
	for <ietf@ietf.org>; Sun, 12 Jan 2003 17:35:13 -0800
Date: Sun, 12 Jan 2003 17:35:17 -0800
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.62 Christmas Edition) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <131199466177.20030112173517@brandenburg.com>
To: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
In-Reply-To: <3E21FF0B.3050703@cisco.com>
References: <250226437.1042390981@localhost> <3E21FF0B.3050703@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

Folks,

In the early '70s, an ARPA database research company, called Computer
Corporation of America (CCA) had a service that allowed you to make a telnet
connection to a special port.

It would spit out a randomly-selected limerick and then close the
connection.

Almost all the limericks were filthy enough to surprise hardened limerick
afficionados.

d/

ps. If you submitted 3 new limericks that they added to the database, you would
get a copy of the entire set.



Sunday, January 12, 2003, 3:49:31 PM, you wrote:
Eliot> If you are looking for the first site that spoke HTTP, then I don't 
Eliot> know.  On the other hand, as we know there has been a history of 
Eliot> development surrounding Internet porn.  First of all, there were the 
Eliot> various newsgroups, and the various (dis)assembly programs.  One of 
Eliot> these was AUB and it dates back to around 1992.

d/
-- 
 Dave <mailto:dhc2@dcrocker.net>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 t +1.408.246.8253; f +1.408.850.1850




From owner-ietf@ietf.org  Sun Jan 12 20:39:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17966;
	Sun, 12 Jan 2003 20:39:34 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18XtZ6-0002hC-00
	for ietf-list@ran.ietf.org; Sun, 12 Jan 2003 20:39:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18XtYR-0002g5-00
	for ietf@ran.ietf.org; Sun, 12 Jan 2003 20:38:19 -0500
Received: from mail-blue.research.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17825
	for <ietf@ietf.org>; Sun, 12 Jan 2003 20:34:25 -0500 (EST)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 98C9B4CFFD; Sun, 12 Jan 2003 20:37:43 -0500 (EST)
Received: from berkshire.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id UAA27930;
	Sun, 12 Jan 2003 20:37:42 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 5EB827B4D; Sun, 12 Jan 2003 20:37:41 -0500 (EST)
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: Eliot Lear <lear@cisco.com>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history..... 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 12 Jan 2003 20:37:41 -0500
Message-Id: <20030113013741.5EB827B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <3E21FF0B.3050703@cisco.com>, Eliot Lear writes:
>If you are looking for the first site that spoke HTTP, then I don't 
>know.  On the other hand, as we know there has been a history of 
>development surrounding Internet porn.  First of all, there were the 
>various newsgroups, and the various (dis)assembly programs.  One of 
>these was AUB and it dates back to around 1992.  Another of which was 
>FSP, the UDP-based file sharing protocol written to get around TCP port 
>filters.  That would be in the 1993 time frame.  While to the best of my 
>knowledge IRC had no attachment to sex for its development, it in 
>combination with various hacker sites played a role in sites being 
>hacked and becoming warez and porn sites.
>

Google's archive has the first alt.sex posting as April 8, 1988.

It's very rare that I have a work-related justification for searching 
alt.sex...

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





From owner-ietf@ietf.org  Sun Jan 12 21:45:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19185;
	Sun, 12 Jan 2003 21:45:34 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18XuJX-0003u5-00
	for ietf-list@ran.ietf.org; Sun, 12 Jan 2003 21:26:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18XuIa-0003te-00
	for ietf@ran.ietf.org; Sun, 12 Jan 2003 21:26:00 -0500
Received: from cobalt.sopac.org.fj (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18601
	for <ietf@ietf.org>; Sun, 12 Jan 2003 21:21:48 -0500 (EST)
Received: by cobalt.sopac.org.fj (Postfix, from userid 416)
	id 16FAE17C1A; Mon, 13 Jan 2003 02:24:54 +0000 (UTC)
Received: from bigiron.sopac.org.fj (unknown [10.0.0.180])
	by cobalt.sopac.org.fj (Postfix) with ESMTP id C157C17C04
	for <ietf@ietf.org>; Mon, 13 Jan 2003 02:24:53 +0000 (UTC)
Received: by BIGIRON with Internet Mail Service (5.5.2650.21)
	id <CYRCTDNC>; Mon, 13 Jan 2003 14:25:09 +1200
Message-ID: <F12ECEA0435AD211B5280008C7ACBC85016B474B@BIGIRON>
From: Franck Martin <Franck@sopac.org>
To: ietf@ietf.org
Subject: RE: Searching for depressing moments of Internet history..... 
Date: Mon, 13 Jan 2003 14:25:08 +1200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-4.1 required=5.0 tests=PORN_8,PORN_10 version=2.20
Sender: owner-ietf@ietf.org
Precedence: bulk

> -----Original Message-----
> From: Steven M. Bellovin [mailto:smb@research.att.com]
> Sent: Monday, 13 January 2003 1:38 
> To: Eliot Lear
> Cc: Harald Tveit Alvestrand; ietf@ietf.org
> Subject: Re: Searching for depressing moments of Internet 
> history..... 
> 
> 
> In message <3E21FF0B.3050703@cisco.com>, Eliot Lear writes:
> >If you are looking for the first site that spoke HTTP, then I don't 
> >know.  On the other hand, as we know there has been a history of 
> >development surrounding Internet porn.  First of all, there were the 
> >various newsgroups, and the various (dis)assembly programs.  One of 
> >these was AUB and it dates back to around 1992.  Another of 
> which was 
> >FSP, the UDP-based file sharing protocol written to get 
> around TCP port 
> >filters.  That would be in the 1993 time frame.  While to 
> the best of my 
> >knowledge IRC had no attachment to sex for its development, it in 
> >combination with various hacker sites played a role in sites being 
> >hacked and becoming warez and porn sites.
> >
> 
> Google's archive has the first alt.sex posting as April 8, 1988.
> 
> It's very rare that I have a work-related justification for searching 
> alt.sex...
> 
An interesting subject for a thesis:

The Porn and The Internet.

You think I can apply for a grant to the NSF? 



From owner-ietf@ietf.org  Sun Jan 12 22:06:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19421;
	Sun, 12 Jan 2003 22:06:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18XutM-0007tq-00
	for ietf-list@ran.ietf.org; Sun, 12 Jan 2003 22:04:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Xut0-0007tJ-00
	for ietf@ran.ietf.org; Sun, 12 Jan 2003 22:03:38 -0500
Received: from sccrmhc02.attbi.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19371
	for <ietf@ietf.org>; Sun, 12 Jan 2003 21:59:42 -0500 (EST)
Received: from attbi.com (12-234-28-165.client.attbi.com[12.234.28.165])
          by sccrmhc02.attbi.com (sccrmhc02) with SMTP
          id <20030113030300002000ik94e>; Mon, 13 Jan 2003 03:03:01 +0000
Message-ID: <3E222CC8.54FCDC36@attbi.com>
Date: Sun, 12 Jan 2003 19:04:40 -0800
From: Peter Deutsch <pdeutsch@attbi.com>
Reply-To: pdeutsch@earthlink.net
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Franck Martin <Franck@sopac.org>
CC: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
References: <F12ECEA0435AD211B5280008C7ACBC85016B474B@BIGIRON>
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

g'day,

Franck Martin wrote:
> 
> > -----Original Message-----
> > From: Steven M. Bellovin [mailto:smb@research.att.com]
> > Sent: Monday, 13 January 2003 1:38
> > To: Eliot Lear
> > Cc: Harald Tveit Alvestrand; ietf@ietf.org
> > Subject: Re: Searching for depressing moments of Internet
> > history.....
> >
> >
> > In message <3E21FF0B.3050703@cisco.com>, Eliot Lear writes:
> > >If you are looking for the first site that spoke HTTP, then I don't
> > >know.  On the other hand, as we know there has been a history of
> > >development surrounding Internet porn.  First of all, there were the
> > >various newsgroups, and the various (dis)assembly programs.  One of
> > >these was AUB and it dates back to around 1992.  Another of
> > which was
> > >FSP, the UDP-based file sharing protocol written to get
> > around TCP port
> > >filters.  That would be in the 1993 time frame.  While to
> > the best of my
> > >knowledge IRC had no attachment to sex for its development, it in
> > >combination with various hacker sites played a role in sites being
> > >hacked and becoming warez and porn sites.
> > >
> >
> > Google's archive has the first alt.sex posting as April 8, 1988.
> >
> > It's very rare that I have a work-related justification for searching
> > alt.sex...
> >
> An interesting subject for a thesis:
> 
> The Porn and The Internet.
> 
> You think I can apply for a grant to the NSF?

Nah, that would never fly. How about "An Investigation into the Utility
of Stimulus-Response Sites For Promoting Networked Growth Patterns".
Worded that way, if DARPA wont fund it, you could always send it to the
folks at NIH or whoever it is that funds the biotech stuff....

				- peterd


-- 

---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
                      Gydig Software

    "I was *that* close to getting 'download dirty pictures
        from the Internet'  added to my job description"

                             -Wally from Dilbert...

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



From owner-ietf@ietf.org  Mon Jan 13 04:57:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06276;
	Mon, 13 Jan 2003 04:57:47 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y1EH-0004Fs-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 04:50:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y1DY-0004FO-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 04:49:16 -0500
Received: from hosting.altserver.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05956
	for <ietf@ietf.org>; Mon, 13 Jan 2003 04:45:15 -0500 (EST)
Received: from lns18m-11-202.w.club-internet.fr ([212.195.146.202] helo=mine.utel.net)
	by hosting.altserver.com with esmtp (Exim 3.36 #1)
	id 18Y1Cq-0005G2-00; Mon, 13 Jan 2003 01:48:32 -0800
Message-Id: <5.1.0.14.0.20030113103944.02da6b40@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 13 Jan 2003 10:53:03 +0100
To: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: Searching for depressing moments of Internet history.....
In-Reply-To: <250226437.1042390981@localhost>
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-70A658C5; boundary="=======4F3F7713======="
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - hosting.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - utel.net
Sender: owner-ietf@ietf.org
Precedence: bulk

--=======4F3F7713=======
Content-Type: text/plain; x-avg-checked=avg-ok-70A658C5; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit

At 17:03 12/01/03, Harald Tveit Alvestrand wrote:
>Despite having lived through much recent history, I've forgotten a lot of 
>it....
>I just wonder: does anyone know/remember when the first Web porn site came 
>online?
>Wondering whether it was before or after the first official release of 
>Mosaic....

Obviously depends on what you mean "on-line".
1. as Dave said there were sex oriented "areas" on many computers.
2. I suppose the first commercial sex sites were on Minitel.
3. This means that technically they were on-line from the Internet legal 
perspective when it interconnected the public nets (84). Actually a few 
Internet private gateways existed before and some Intelmatics tests were 
probably carried in the USA as early as 1982, with protocol conversion. I 
would be surprised that no one test connected them from ARPANET. When 
people tested from abroad, I do not know why, they always did it with a 
porn site.
4.UK Universities also shared into Prestel and some where on the Internet 
(you should inquire there. They had a leading data brokering firm that 
"on-line", I Oxford (?) I think). I do not know about Paris University, but 
we can investigate.
jfc

--=======4F3F7713=======--




From owner-ietf@ietf.org  Mon Jan 13 05:05:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06565;
	Mon, 13 Jan 2003 05:05:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y1Sm-0004lI-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 05:05:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y1Sj-0004kj-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 05:04:57 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06449
	for <ietf@ietf.org>; Mon, 13 Jan 2003 05:00:56 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP id C4C5F62593
	for <ietf@ietf.org>; Mon, 13 Jan 2003 11:04:15 +0100 (CET)
Date: Mon, 13 Jan 2003 11:04:16 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
Message-ID: <127190000.1042452256@askvoll.hjemme.alvestrand.no>
In-Reply-To: <5.1.0.14.0.20030113103944.02da6b40@mail.utel.net>
References:  <5.1.0.14.0.20030113103944.02da6b40@mail.utel.net>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

just to be clear - I was thinking of porn sites using the HTTP protocol for 
access.

Best so far: Paul Hoffman thinks that the first one was called "Adult 
Action", and probably predated the official Mosaic release. But that search 
term is too general for the Internet of today (8240 hits.... sigh...)

Thanks to all who responded!

                 Harald

--On mandag, januar 13, 2003 10:53:03 +0100 jfcm <info@utel.net> wrote:

> At 17:03 12/01/03, Harald Tveit Alvestrand wrote:
>> Despite having lived through much recent history, I've forgotten a lot
>> of  it....
>> I just wonder: does anyone know/remember when the first Web porn site
>> came  online?
>> Wondering whether it was before or after the first official release of
>> Mosaic....
>
> Obviously depends on what you mean "on-line".
> 1. as Dave said there were sex oriented "areas" on many computers.
> 2. I suppose the first commercial sex sites were on Minitel.
> 3. This means that technically they were on-line from the Internet legal
> perspective when it interconnected the public nets (84). Actually a few
> Internet private gateways existed before and some Intelmatics tests were
> probably carried in the USA as early as 1982, with protocol conversion. I
> would be surprised that no one test connected them from ARPANET. When
> people tested from abroad, I do not know why, they always did it with a
> porn site. 4.UK Universities also shared into Prestel and some where on
> the Internet (you should inquire there. They had a leading data brokering
> firm that "on-line", I Oxford (?) I think). I do not know about Paris
> University, but we can investigate. jfc





From owner-ietf@ietf.org  Mon Jan 13 08:12:53 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10264;
	Mon, 13 Jan 2003 08:12:53 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y4It-0007F4-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 08:06:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y4IW-0007EY-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 08:06:36 -0500
Received: from mx1.xcite.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10157
	for <ietf@ietf.org>; Mon, 13 Jan 2003 08:02:32 -0500 (EST)
Received: from raydesk1.wellfuckit.com (cdm-66-159-23-brcs.cox-internet.com [66.76.159.23] (may be forged))
	by mx1.xcite.net (8.10.0/8.10.0) with SMTP id h0DD64222318;
	Mon, 13 Jan 2003 08:06:04 -0500
Message-Id: <200301131306.h0DD64222318@mx1.xcite.net>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
From: "support@webmastersguide.com" <support@webmastersguide.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
X-Mailer: Pronto v2.4.0 On linux/mysql
Date: Mon, 13 Jan 2003 07:04:07 -0600
Reply-To: "support@webmastersguide.com" <support@webmastersguide.com>
In-Reply-To: <127190000.1042452256@askvoll.hjemme.alvestrand.no>
References: <5.1.0.14.0.20030113103944.02da6b40@mail.utel.net>
    <127190000.1042452256@askvoll.hjemme.alvestrand.no>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

  By June and July of 1994 people were trying
adult http sites.  I'm afraid it's not clear how long 
before this these sites actually existed.
I can tell you that there were very few adult sites
in 1994.  By 1996 the formula and format for such
sites was pretty well fixed and that same formula 
and format is still used on 99% of sites today.
Why the creation of the first porn site is a 
depressing moment I'm not sure.  In the first
couple years of the web, adult sites financed it's
development.  In 1997 and 1998 90% of commerce
on the web was adult related.  Within two years 
of the first nudie pic being served via http the 
adult operators had developed workable streaming
video.	A year later, in 1997, we installed the first 
live video with audio streaming from a Dallas office.

  Adult operators also developed technologies such 
as digital watermarking, the pay per click advertising
model, and usable http payment processing gateways
long before these technologies were adopted by 
mainstream companies.  One of the biggest things to 
make the web the commercially attractive was efficient
online payment processing.  The first http 3rd party 
payment processing service was started in March 
of 1995 by my friend Laith Alsarraf.  It would be 
another TWO YEARS before mainstream sites had
a comparable online processor.


Porn sites filtered:
Date: 1994-07-08 18:37:06 PST 
http://groups.google.com/groups?q=naked+http&start=60&hl=en&lr=&ie=UTF-8&oe=UTF
-8&as_drrb=b&as_mind=1&as_minm=1&as_miny=1994&as_maxd=13&as_maxm=7&as_maxy=1994
&selm=1994Jul8.110718.18031%40umiami.ir.miami.edu&rnum=69





On Mon, 13 Jan 2003 11:04:16 +0100, Harald Tveit Alvestrand said:

> just to be clear - I was thinking of porn sites using the HTTP protocol for 
>  access.
>  
>  Best so far: Paul Hoffman thinks that the first one was called "Adult 
>  Action", and probably predated the official Mosaic release. But that search 
>  term is too general for the Internet of today (8240 hits.... sigh...)
>  
>  Thanks to all who responded!
>  
>                   Harald
>  
>  --On mandag, januar 13, 2003 10:53:03 +0100 jfcm <info@utel.net> wrote:
>  
>  > At 17:03 12/01/03, Harald Tveit Alvestrand wrote:
>  >> Despite having lived through much recent history, I've forgotten a lot
>  >> of  it....
>  >> I just wonder: does anyone know/remember when the first Web porn site
>  >> came  online?
>  >> Wondering whether it was before or after the first official release of
>  >> Mosaic....
>  >
>  > Obviously depends on what you mean "on-line".
>  > 1. as Dave said there were sex oriented "areas" on many computers.
>  > 2. I suppose the first commercial sex sites were on Minitel.
>  > 3. This means that technically they were on-line from the Internet legal
>  > perspective when it interconnected the public nets (84). Actually a few
>  > Internet private gateways existed before and some Intelmatics tests were
>  > probably carried in the USA as early as 1982, with protocol conversion. I
>  > would be surprised that no one test connected them from ARPANET. When
>  > people tested from abroad, I do not know why, they always did it with a
>  > porn site. 4.UK Universities also shared into Prestel and some where on
>  > the Internet (you should inquire there. They had a leading data brokering
>  > firm that "on-line", I Oxford (?) I think). I do not know about Paris
>  > University, but we can investigate. jfc
>  
>  
>  

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ray B. Morris
support@webmastersguide.com
http://www.WebmastersGuide.com





From owner-ietf@ietf.org  Mon Jan 13 09:01:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11040;
	Mon, 13 Jan 2003 09:01:29 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y57E-0008C2-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 08:59:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y56f-0008Ai-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 08:58:25 -0500
Received: from tx2.wvinternetservices.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10937
	for <ietf@ietf.org>; Mon, 13 Jan 2003 08:54:23 -0500 (EST)
Received: from a (63-144-68-19.citynet.net [63.144.68.19])
	by tx2.wvinternetservices.com (8.12.6/8.12.6=Outbound) with SMTP id h0DDpAqw006253
	for <ietf@ietf.org>; Mon, 13 Jan 2003 08:51:10 -0500
Message-ID: <001401c2bb0b$751c0480$1344903f@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: <ietf@ietf.org>
Subject: Porn sites
Date: Mon, 13 Jan 2003 08:55:39 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Why are pornsites depressing? Adults have a choice as to whether on not they
want to visit these sites, the only bad thing is that if you enter your
email address, you'll be hit by spam like never before.




From owner-ietf@ietf.org  Mon Jan 13 10:08:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12683;
	Mon, 13 Jan 2003 10:08:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y696-00028Y-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 10:05:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y68R-00023A-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 10:04:19 -0500
Received: from bowl.fysh.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12496
	for <ietf@ietf.org>; Mon, 13 Jan 2003 10:00:12 -0500 (EST)
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 18Y67T-0005cX-00
	for <ietf@ietf.org>; Mon, 13 Jan 2003 15:03:19 +0000
Date: Mon, 13 Jan 2003 15:03:19 +0000
To: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
Message-ID: <20030113150319.GA18089@fysh.org>
References: <5.1.0.14.0.20030113103944.02da6b40@mail.utel.net> <127190000.1042452256@askvoll.hjemme.alvestrand.no> <200301131306.h0DD64222318@mx1.xcite.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200301131306.h0DD64222318@mx1.xcite.net>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

support@webmastersguide.com wrote:
>Why the creation of the first porn site is a 
>depressing moment I'm not sure.

A few years ago I found myself wondering why most commercial websites
are so garish, flashy, fragmented, and awkward to navigate.  I came to
the conclusion that they'd all taken their stylistic lead from the very
first commercial websites: the porn sites.  Is it not depressing that
porn-pushing techniques have been adopted into, and come to dominate,
mainstream commerce?

(Happy lynx user here, it's not often that I'm forced to see how visually
appalling these sites have been designed to be.)

-zefram



From owner-ietf@ietf.org  Mon Jan 13 10:33:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13455;
	Mon, 13 Jan 2003 10:33:13 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y6YQ-00031s-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 10:31:10 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18W3yi-0004ia-00
	for ietf@ran.ietf.org; Tue, 07 Jan 2003 19:21:53 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02890
	for <ietf@ietf.org>; Tue, 7 Jan 2003 18:18:57 -0500 (EST)
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18W32t-0000j7-00; Tue, 07 Jan 2003 18:22:07 -0500
Date: Tue, 07 Jan 2003 18:22:06 -0500
From: John C Klensin <john+ietf@jck.com>
To: Doug <Dougxx2@carolina.rr.com>, "ietf@ietf.org" <ietf@ietf.org>
cc: Lloyd Wood <l.wood@eim.surrey.ac.uk>
Subject: Re: email and spam (was: Re: namedroppers, continued)
Message-ID: <33549559.1041963726@P2>
In-Reply-To: <009e01c2b67b$45926590$0701a8c0@nailed.org>
References:  <009e01c2b67b$45926590$0701a8c0@nailed.org>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Tuesday, 07 January, 2003 13:33 -0500 Doug
<Dougxx2@carolina.rr.com> wrote:

>> Doug has rediscovered the idea of closing open mail relays to
> prevent
>> unauthorised use by outsiders sending to outsiders. This was
>> a big thing in the early 90s when email became popular.
> 
> This may seem to be a bit basic for some of the people who
> have worked on this problem for years. My intention was not to
> prove that I had the latest and greatest solution to the spam
> problem. It was to get the ball rolling in an open discussion
> forum and present my ideas on the topic in the hopes that
> someone who knew more than me on the topic would as well.
>...

Ok, Doug.  Let me take a shot at simultaneously explaining the
problem here and  why your suggested solutions are getting such
resistance.  Perhaps a different approach may succeed where
Lloyd's didn't (not his fault, I'm sure).

Almost all of the measures you have suggested have serious
side-effects or critical prerequisites.  In the last analysis,
most of us would rather put up with a little spam than pay the
prices involved.  Others are sufficiently fed up with spam that
they are willing to consider some very radical changes to how we
use email.  But, regardless of how that comes out, the decisions
have been fairly explicit: people have thought of your
suggestions, and others, and their impact, and have made fairly
explicit decisions about preferences.  My comment about X.400 of
a few weeks ago was intended to address those issues, but
apparently made a reference too far in the past, or too subtle,
for some of the people who have been participating in the
discussion.

The people who have been through it are reluctant to start the
discussion again because the dead horse has been kicked into an
unrecognizable pulp. There has been a good deal of discussion,
in many archives, that it would be good for you to read.  If you
then come up with a _new_ idea that doesn't revisit the old
problems, many of us would be enthused about listening.  It is
only the old and discredited proposals that are met with
intolerance.

Let me take a closely-related pair of examples from your note.
As I understand it, you would like ISPs (really email providers)
to take responsibility for authenticating their customers.  And
you would like IP addresses shown in mail header traces to be
reliable.  Ok.  Those two things turn out to be much more about
trust relationships than they are about protocols: one can make
major changes to protocols without changing the trust
relationships at all, and can accomplish those things without
any changes in the protocols.  But, assuming that you aren't
willing to trust anyone who can operate a mail-sending protocol,
there are only a few ways that you can trust the source and
origins of email.  

For example, we could, as a society, start licensing email
providers, require each licensed provider to accept mail only
from other licensed providers and from users they can
authenticate (with severe penalties for violating those rules).
That would make folks who would like to go back to business
models in which they charge for every item of mail very happy.
It would make many of the rest of us unhappy.  But it would
work... and, while some protocol enhancements might make it
easier to support, nothing is really required beyond SMTP as it
exists today.

Similarly, you could decide to work with an email mailbox
provider who would refuse to accept mail from any site with
which it didn't have an agreement about user authentication and
traffic and which, were relaying permitted, would insist that
any site from which it accepted a relayed message impose the
same requirements on its users.  With some prototype agreement
forms, this could be a way to build up a trust web similar to
the licensing one, using a web of bilateral agreements rather
than governmental action.  

But either of those approaches would result in less legitimate
mail getting through.  For instance, I run my own mail servers
and, as far as I know, can authenticate anyone who originates
mail here.  But I have neither the resources nor the inclination
to participate in a large collection of bilateral contractual
agreements, nor to start applying for licenses.

The issues with those bad IP addresses are similar.  Most are
spoofed.  You can trust the information in Received headers only
as far back as the last mail host you trust to report
information accurately.  If there is a spammer deliberately
deciding to deceive you, anything earlier is likely to be trash,
not because the wrong information is in the Whois tables, but
because the data in the Received fields is being made up (either
at random or in the hope of pinning the spam on someone else).
And, again, formalizing  the trust relationships through
contracts or licenses would help a great deal, and might be the
only solution, but those options carry a high price in terms of
generally accessibility and usability of email.

regards,
    john

p.s.

> Asking questions, presenting possible solutions, and learning
> from mistakes is how we get solutions.

And learning what has been done and discussed in the past,
before asking your questions of thousands of people, is usually
considered, at least, polite.






From owner-ietf@ietf.org  Mon Jan 13 10:33:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13453;
	Mon, 13 Jan 2003 10:33:13 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y6aC-00035S-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 10:33:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WK0x-0005Fl-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 12:29:16 -0500
Received: from zcars04f.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26262;
	Wed, 8 Jan 2003 12:20:41 -0500 (EST)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h08HNpT22285;
	Wed, 8 Jan 2003 12:23:51 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <ZC6RWFY1>; Wed, 8 Jan 2003 12:23:51 -0500
Message-ID: <710197BD5AF9D4119E4400508BCFA13606537B65@zcard04u.ca.nortel.com>
From: "Osama Aboul-Magd" <osama@nortelnetworks.com>
To: Adrian Farrel <afarrel@movaz.com>, Loa Andersson <loa@pi.se>
Cc: iesg@ietf.org, ietf@ietf.org,
        "Steve Trowbridge (E-mail)"
	 <sjtrowbridge@lucent.com>
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informat
	ional
Date: Wed, 8 Jan 2003 12:23:51 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2B73A.B6345C8A"
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_01C2B73A.B6345C8A
Content-Type: text/plain

Hi Adrian,

The ITU is scheduled to consent G.7713.3 by the end of the month. In order
for this to happen we need the IANA code points, and this is the only
purpose of this draft.

I hope now you see the urgency of this draft.

Regards;

Osama Aboul-Magd
ATI Strategic Standards and Protocols
Nortel Networks
P.O. Box 3511, Station C
Ottawa, Ontario, Canada
K1Y-4H7
Tel: +1 613 763 5827
e.mail:osama@nortelnetworks.com


-----Original Message-----
From: Adrian Farrel [mailto:afarrel@movaz.com] 
Sent: Wednesday, January 08, 2003 12:20 PM
To: Loa Andersson
Cc: iesg@ietf.org; Aboul-Magd, Osama [CAR:1A00:EXCH]; ietf@ietf.org
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to
Informational

> trying to understand what you are saying - it seems like you are
> implying that there is no consensus with in ITU on how to progress
> this, and that therefore would be premature for IETF to publish
> this as an informational RFC. Correct?

I'm not quite saying that.
I am saying that it sounds to me from the discussion that the ITU has not
yet
reached consent. It seemed to me that if the draft is intended to document
the
ITU preferences as informational, it would be as well to wait until the ITU
has
fully signed off. I don't see any rush for this.

> Anyhow - I think it would be appropriate to add a note clarifying that
> IETF will not progress cr-ldp beyond Proposed Standard.

Adrian



------_=_NextPart_001_01C2B73A.B6345C8A
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to =
Informational</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi Adrian,</FONT>
</P>

<P><FONT SIZE=3D2>The ITU is scheduled to consent G.7713.3 by the end =
of the month. In order for this to happen we need the IANA code points, =
and this is the only purpose of this draft.</FONT></P>

<P><FONT SIZE=3D2>I hope now you see the urgency of this draft.</FONT>
</P>

<P><FONT SIZE=3D2>Regards;</FONT>
</P>

<P><FONT SIZE=3D2>Osama Aboul-Magd</FONT>
<BR><FONT SIZE=3D2>ATI Strategic Standards and Protocols</FONT>
<BR><FONT SIZE=3D2>Nortel Networks</FONT>
<BR><FONT SIZE=3D2>P.O. Box 3511, Station C</FONT>
<BR><FONT SIZE=3D2>Ottawa, Ontario, Canada</FONT>
<BR><FONT SIZE=3D2>K1Y-4H7</FONT>
<BR><FONT SIZE=3D2>Tel: +1 613 763 5827</FONT>
<BR><FONT SIZE=3D2>e.mail:osama@nortelnetworks.com</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Adrian Farrel [<A =
HREF=3D"mailto:afarrel@movaz.com">mailto:afarrel@movaz.com</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, January 08, 2003 12:20 PM</FONT>
<BR><FONT SIZE=3D2>To: Loa Andersson</FONT>
<BR><FONT SIZE=3D2>Cc: iesg@ietf.org; Aboul-Magd, Osama =
[CAR:1A00:EXCH]; ietf@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: CORRECTION: Last Call: CR-LDP =
Extensions for ASON to Informational</FONT>
</P>

<P><FONT SIZE=3D2>&gt; trying to understand what you are saying - it =
seems like you are</FONT>
<BR><FONT SIZE=3D2>&gt; implying that there is no consensus with in ITU =
on how to progress</FONT>
<BR><FONT SIZE=3D2>&gt; this, and that therefore would be premature for =
IETF to publish</FONT>
<BR><FONT SIZE=3D2>&gt; this as an informational RFC. Correct?</FONT>
</P>

<P><FONT SIZE=3D2>I'm not quite saying that.</FONT>
<BR><FONT SIZE=3D2>I am saying that it sounds to me from the discussion =
that the ITU has not yet</FONT>
<BR><FONT SIZE=3D2>reached consent. It seemed to me that if the draft =
is intended to document the</FONT>
<BR><FONT SIZE=3D2>ITU preferences as informational, it would be as =
well to wait until the ITU has</FONT>
<BR><FONT SIZE=3D2>fully signed off. I don't see any rush for =
this.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; Anyhow - I think it would be appropriate to add =
a note clarifying that</FONT>
<BR><FONT SIZE=3D2>&gt; IETF will not progress cr-ldp beyond Proposed =
Standard.</FONT>
</P>

<P><FONT SIZE=3D2>Adrian</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C2B73A.B6345C8A--





From owner-ietf@ietf.org  Mon Jan 13 10:41:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13865;
	Mon, 13 Jan 2003 10:41:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y6f4-0003UC-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 10:38:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WK6m-0007uV-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 12:35:17 -0500
Received: from maila.telia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26867;
	Wed, 8 Jan 2003 12:26:42 -0500 (EST)
Received: from d1o888.telia.com (d1o888.telia.com [213.67.172.241])
	by maila.telia.com (8.12.5/8.12.5) with ESMTP id h08HTpCN008052;
	Wed, 8 Jan 2003 18:29:51 +0100 (CET)
X-Original-Recipient: iesg@ietf.org
Received: from pi.se (h70n2fls31o888.telia.com [213.64.120.70])
	by d1o888.telia.com (8.10.2/8.10.1) with ESMTP id h08HTp228055;
	Wed, 8 Jan 2003 18:29:51 +0100 (CET)
Message-ID: <3E1C5F30.3030706@pi.se>
Date: Wed, 08 Jan 2003 18:26:08 +0100
From: Loa Andersson <loa@pi.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Osama Aboul-Magd <osama@nortelnetworks.com>
CC: Adrian Farrel <afarrel@movaz.com>, iesg@ietf.org, ietf@ietf.org,
        "Steve
 Trowbridge (E-mail)" <sjtrowbridge@lucent.com>
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informat
 ional
References: <710197BD5AF9D4119E4400508BCFA13606537B65@zcard04u.ca.nortel.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

Osama,

sorry our mails crossed each other on the wire. I see your
point, but doi not really understand why you need the actual
code points to reach consensus - as long as you know you will
get them?

But, I will not try to stop publishing the draft - as long as the
note on cr-ldp not scheduled for further development is added.

/Loa

Osama Aboul-Magd wrote:
> Hi Adrian,
> 
> The ITU is scheduled to consent G.7713.3 by the end of the month. In 
> order for this to happen we need the IANA code points, and this is the 
> only purpose of this draft.
> 
> I hope now you see the urgency of this draft.
> 
> Regards;
> 
> Osama Aboul-Magd
> ATI Strategic Standards and Protocols
> Nortel Networks
> P.O. Box 3511, Station C
> Ottawa, Ontario, Canada
> K1Y-4H7
> Tel: +1 613 763 5827
> e.mail:osama@nortelnetworks.com
> 
> 
> -----Original Message-----
> From: Adrian Farrel [mailto:afarrel@movaz.com]
> Sent: Wednesday, January 08, 2003 12:20 PM
> To: Loa Andersson
> Cc: iesg@ietf.org; Aboul-Magd, Osama [CAR:1A00:EXCH]; ietf@ietf.org
> Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to 
> Informational
> 
>  > trying to understand what you are saying - it seems like you are
>  > implying that there is no consensus with in ITU on how to progress
>  > this, and that therefore would be premature for IETF to publish
>  > this as an informational RFC. Correct?
> 
> I'm not quite saying that.
> I am saying that it sounds to me from the discussion that the ITU has 
> not yet
> reached consent. It seemed to me that if the draft is intended to 
> document the
> ITU preferences as informational, it would be as well to wait until the 
> ITU has
> fully signed off. I don't see any rush for this.
> 
>  > Anyhow - I think it would be appropriate to add a note clarifying that
>  > IETF will not progress cr-ldp beyond Proposed Standard.
> 
> Adrian
> 
> 


-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se







From owner-ietf@ietf.org  Mon Jan 13 10:44:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14010;
	Mon, 13 Jan 2003 10:44:47 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y6f5-0003US-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 10:38:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WK8G-00005u-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 12:36:48 -0500
Received: from zcars04f.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26986;
	Wed, 8 Jan 2003 12:28:14 -0500 (EST)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h08HVPT22812;
	Wed, 8 Jan 2003 12:31:25 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <ZC6RWF79>; Wed, 8 Jan 2003 12:31:25 -0500
Message-ID: <710197BD5AF9D4119E4400508BCFA13606537B83@zcard04u.ca.nortel.com>
From: "Osama Aboul-Magd" <osama@nortelnetworks.com>
To: Loa Andersson <loa@pi.se>, Adrian Farrel <afarrel@movaz.com>
Cc: iesg@ietf.org, ietf@ietf.org
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informat
	ional
Date: Wed, 8 Jan 2003 12:31:23 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2B73B.C3863F06"
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_01C2B73B.C3863F06
Content-Type: text/plain

Loa,

I've just sent a response to Adrian. ITU is scheduled to consent this draft
at the end of the month. Therefore this draft is very urgent.

Regards;

Osama Aboul-Magd
ATI Strategic Standards and Protocols
Nortel Networks
P.O. Box 3511, Station C
Ottawa, Ontario, Canada
K1Y-4H7
Tel: +1 613 763 5827
e.mail:osama@nortelnetworks.com


-----Original Message-----
From: Loa Andersson [mailto:loa@pi.se] 
Sent: Wednesday, January 08, 2003 12:23 PM
To: Adrian Farrel
Cc: iesg@ietf.org; Aboul-Magd, Osama [CAR:1A00:EXCH]; ietf@ietf.org
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to
Informational

Adrian,


Adrian Farrel wrote:
>>trying to understand what you are saying - it seems like you are
>>implying that there is no consensus with in ITU on how to progress
>>this, and that therefore would be premature for IETF to publish
>>this as an informational RFC. Correct?
> 
> 
> I'm not quite saying that.
> I am saying that it sounds to me from the discussion that the ITU has not
yet
> reached consent. It seemed to me that if the draft is intended to document
the
> ITU preferences as informational, it would be as well to wait until the
ITU has
> fully signed off. I don't see any rush for this.

ok - I can see the difference - and it seems that you are correct. If
the ITU discussion still has some way to go before the discussion
settles and the preferences better known - wouldn't it be appropriate to 
wait until this happens?

Osama, care to comment?

/Loa

> 
> 
>>Anyhow - I think it would be appropriate to add a note clarifying that
>>IETF will not progress cr-ldp beyond Proposed Standard.
> 
> 
> Adrian
> 
> 
> 
> 


-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se



------_=_NextPart_001_01C2B73B.C3863F06
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to =
Informational</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Loa,</FONT>
</P>

<P><FONT SIZE=3D2>I've just sent a response to Adrian. ITU is scheduled =
to consent this draft at the end of the month. Therefore this draft is =
very urgent.</FONT></P>

<P><FONT SIZE=3D2>Regards;</FONT>
</P>

<P><FONT SIZE=3D2>Osama Aboul-Magd</FONT>
<BR><FONT SIZE=3D2>ATI Strategic Standards and Protocols</FONT>
<BR><FONT SIZE=3D2>Nortel Networks</FONT>
<BR><FONT SIZE=3D2>P.O. Box 3511, Station C</FONT>
<BR><FONT SIZE=3D2>Ottawa, Ontario, Canada</FONT>
<BR><FONT SIZE=3D2>K1Y-4H7</FONT>
<BR><FONT SIZE=3D2>Tel: +1 613 763 5827</FONT>
<BR><FONT SIZE=3D2>e.mail:osama@nortelnetworks.com</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Loa Andersson [<A =
HREF=3D"mailto:loa@pi.se">mailto:loa@pi.se</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, January 08, 2003 12:23 PM</FONT>
<BR><FONT SIZE=3D2>To: Adrian Farrel</FONT>
<BR><FONT SIZE=3D2>Cc: iesg@ietf.org; Aboul-Magd, Osama =
[CAR:1A00:EXCH]; ietf@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: CORRECTION: Last Call: CR-LDP =
Extensions for ASON to Informational</FONT>
</P>

<P><FONT SIZE=3D2>Adrian,</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Adrian Farrel wrote:</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;trying to understand what you are saying - =
it seems like you are</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;implying that there is no consensus with in =
ITU on how to progress</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;this, and that therefore would be premature =
for IETF to publish</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;this as an informational RFC. =
Correct?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I'm not quite saying that.</FONT>
<BR><FONT SIZE=3D2>&gt; I am saying that it sounds to me from the =
discussion that the ITU has not yet</FONT>
<BR><FONT SIZE=3D2>&gt; reached consent. It seemed to me that if the =
draft is intended to document the</FONT>
<BR><FONT SIZE=3D2>&gt; ITU preferences as informational, it would be =
as well to wait until the ITU has</FONT>
<BR><FONT SIZE=3D2>&gt; fully signed off. I don't see any rush for =
this.</FONT>
</P>

<P><FONT SIZE=3D2>ok - I can see the difference - and it seems that you =
are correct. If</FONT>
<BR><FONT SIZE=3D2>the ITU discussion still has some way to go before =
the discussion</FONT>
<BR><FONT SIZE=3D2>settles and the preferences better known - wouldn't =
it be appropriate to </FONT>
<BR><FONT SIZE=3D2>wait until this happens?</FONT>
</P>

<P><FONT SIZE=3D2>Osama, care to comment?</FONT>
</P>

<P><FONT SIZE=3D2>/Loa</FONT>
</P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&gt;Anyhow - I think it would be appropriate to =
add a note clarifying that</FONT>
<BR><FONT SIZE=3D2>&gt;&gt;IETF will not progress cr-ldp beyond =
Proposed Standard.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Adrian</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Loa Andersson</FONT>
</P>

<P><FONT =
SIZE=3D2>Mobile&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+46 739 81 21 64</FONT>
<BR><FONT =
SIZE=3D2>Email&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; loa@pi.se</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C2B73B.C3863F06--





From owner-ietf@ietf.org  Mon Jan 13 10:44:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14009;
	Mon, 13 Jan 2003 10:44:47 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y6f6-0003Ug-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 10:38:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WKB7-0000Jb-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 12:39:45 -0500
Received: from zcars04f.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27114;
	Wed, 8 Jan 2003 12:31:11 -0500 (EST)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h08HYMT23021;
	Wed, 8 Jan 2003 12:34:22 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <ZC6RWF0B>; Wed, 8 Jan 2003 12:34:22 -0500
Message-ID: <710197BD5AF9D4119E4400508BCFA13606537B92@zcard04u.ca.nortel.com>
From: "Osama Aboul-Magd" <osama@nortelnetworks.com>
To: Loa Andersson <loa@pi.se>
Cc: Adrian Farrel <afarrel@movaz.com>, iesg@ietf.org, ietf@ietf.org,
        "Steve Trowbridge (E-mail)" <sjtrowbridge@lucent.com>
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informan
	t ional
Date: Wed, 8 Jan 2003 12:34:19 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2B73C.2CE74EF4"
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_01C2B73C.2CE74EF4
Content-Type: text/plain

Because the ITU cannot consent the draft without the code points.

The ITU knows exactly that the standard work on CR-LDP is discontinued.
Steve may correct me if I am mistaken.

Regards;

Osama Aboul-Magd
ATI Strategic Standards and Protocols
Nortel Networks
P.O. Box 3511, Station C
Ottawa, Ontario, Canada
K1Y-4H7
Tel: +1 613 763 5827
e.mail:osama@nortelnetworks.com


-----Original Message-----
From: Loa Andersson [mailto:loa@pi.se] 
Sent: Wednesday, January 08, 2003 12:26 PM
To: Aboul-Magd, Osama [CAR:1A00:EXCH]
Cc: Adrian Farrel; iesg@ietf.org; ietf@ietf.org; Steve Trowbridge (E-mail)
Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informat
ional

Osama,

sorry our mails crossed each other on the wire. I see your
point, but doi not really understand why you need the actual
code points to reach consensus - as long as you know you will
get them?

But, I will not try to stop publishing the draft - as long as the
note on cr-ldp not scheduled for further development is added.

/Loa

Osama Aboul-Magd wrote:
> Hi Adrian,
> 
> The ITU is scheduled to consent G.7713.3 by the end of the month. In 
> order for this to happen we need the IANA code points, and this is the 
> only purpose of this draft.
> 
> I hope now you see the urgency of this draft.
> 
> Regards;
> 
> Osama Aboul-Magd
> ATI Strategic Standards and Protocols
> Nortel Networks
> P.O. Box 3511, Station C
> Ottawa, Ontario, Canada
> K1Y-4H7
> Tel: +1 613 763 5827
> e.mail:osama@nortelnetworks.com
> 
> 
> -----Original Message-----
> From: Adrian Farrel [mailto:afarrel@movaz.com]
> Sent: Wednesday, January 08, 2003 12:20 PM
> To: Loa Andersson
> Cc: iesg@ietf.org; Aboul-Magd, Osama [CAR:1A00:EXCH]; ietf@ietf.org
> Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to 
> Informational
> 
>  > trying to understand what you are saying - it seems like you are
>  > implying that there is no consensus with in ITU on how to progress
>  > this, and that therefore would be premature for IETF to publish
>  > this as an informational RFC. Correct?
> 
> I'm not quite saying that.
> I am saying that it sounds to me from the discussion that the ITU has 
> not yet
> reached consent. It seemed to me that if the draft is intended to 
> document the
> ITU preferences as informational, it would be as well to wait until the 
> ITU has
> fully signed off. I don't see any rush for this.
> 
>  > Anyhow - I think it would be appropriate to add a note clarifying that
>  > IETF will not progress cr-ldp beyond Proposed Standard.
> 
> Adrian
> 
> 


-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se



------_=_NextPart_001_01C2B73C.2CE74EF4
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2655.35">
<TITLE>RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informant ional</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Because the ITU cannot consent the draft without the code points.</FONT>
</P>

<P><FONT SIZE=2>The ITU knows exactly that the standard work on CR-LDP is discontinued. Steve may correct me if I am mistaken.</FONT>
</P>

<P><FONT SIZE=2>Regards;</FONT>
</P>

<P><FONT SIZE=2>Osama Aboul-Magd</FONT>
<BR><FONT SIZE=2>ATI Strategic Standards and Protocols</FONT>
<BR><FONT SIZE=2>Nortel Networks</FONT>
<BR><FONT SIZE=2>P.O. Box 3511, Station C</FONT>
<BR><FONT SIZE=2>Ottawa, Ontario, Canada</FONT>
<BR><FONT SIZE=2>K1Y-4H7</FONT>
<BR><FONT SIZE=2>Tel: +1 613 763 5827</FONT>
<BR><FONT SIZE=2>e.mail:osama@nortelnetworks.com</FONT>
</P>
<BR>

<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Loa Andersson [<A HREF="mailto:loa@pi.se">mailto:loa@pi.se</A>] </FONT>
<BR><FONT SIZE=2>Sent: Wednesday, January 08, 2003 12:26 PM</FONT>
<BR><FONT SIZE=2>To: Aboul-Magd, Osama [CAR:1A00:EXCH]</FONT>
<BR><FONT SIZE=2>Cc: Adrian Farrel; iesg@ietf.org; ietf@ietf.org; Steve Trowbridge (E-mail)</FONT>
<BR><FONT SIZE=2>Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informat ional</FONT>
</P>

<P><FONT SIZE=2>Osama,</FONT>
</P>

<P><FONT SIZE=2>sorry our mails crossed each other on the wire. I see your</FONT>
<BR><FONT SIZE=2>point, but doi not really understand why you need the actual</FONT>
<BR><FONT SIZE=2>code points to reach consensus - as long as you know you will</FONT>
<BR><FONT SIZE=2>get them?</FONT>
</P>

<P><FONT SIZE=2>But, I will not try to stop publishing the draft - as long as the</FONT>
<BR><FONT SIZE=2>note on cr-ldp not scheduled for further development is added.</FONT>
</P>

<P><FONT SIZE=2>/Loa</FONT>
</P>

<P><FONT SIZE=2>Osama Aboul-Magd wrote:</FONT>
<BR><FONT SIZE=2>&gt; Hi Adrian,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; The ITU is scheduled to consent G.7713.3 by the end of the month. In </FONT>
<BR><FONT SIZE=2>&gt; order for this to happen we need the IANA code points, and this is the </FONT>
<BR><FONT SIZE=2>&gt; only purpose of this draft.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I hope now you see the urgency of this draft.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Regards;</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Osama Aboul-Magd</FONT>
<BR><FONT SIZE=2>&gt; ATI Strategic Standards and Protocols</FONT>
<BR><FONT SIZE=2>&gt; Nortel Networks</FONT>
<BR><FONT SIZE=2>&gt; P.O. Box 3511, Station C</FONT>
<BR><FONT SIZE=2>&gt; Ottawa, Ontario, Canada</FONT>
<BR><FONT SIZE=2>&gt; K1Y-4H7</FONT>
<BR><FONT SIZE=2>&gt; Tel: +1 613 763 5827</FONT>
<BR><FONT SIZE=2>&gt; e.mail:osama@nortelnetworks.com</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: Adrian Farrel [<A HREF="mailto:afarrel@movaz.com">mailto:afarrel@movaz.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Wednesday, January 08, 2003 12:20 PM</FONT>
<BR><FONT SIZE=2>&gt; To: Loa Andersson</FONT>
<BR><FONT SIZE=2>&gt; Cc: iesg@ietf.org; Aboul-Magd, Osama [CAR:1A00:EXCH]; ietf@ietf.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: Re: CORRECTION: Last Call: CR-LDP Extensions for ASON to </FONT>
<BR><FONT SIZE=2>&gt; Informational</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt;&nbsp; &gt; trying to understand what you are saying - it seems like you are</FONT>
<BR><FONT SIZE=2>&gt;&nbsp; &gt; implying that there is no consensus with in ITU on how to progress</FONT>
<BR><FONT SIZE=2>&gt;&nbsp; &gt; this, and that therefore would be premature for IETF to publish</FONT>
<BR><FONT SIZE=2>&gt;&nbsp; &gt; this as an informational RFC. Correct?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I'm not quite saying that.</FONT>
<BR><FONT SIZE=2>&gt; I am saying that it sounds to me from the discussion that the ITU has </FONT>
<BR><FONT SIZE=2>&gt; not yet</FONT>
<BR><FONT SIZE=2>&gt; reached consent. It seemed to me that if the draft is intended to </FONT>
<BR><FONT SIZE=2>&gt; document the</FONT>
<BR><FONT SIZE=2>&gt; ITU preferences as informational, it would be as well to wait until the </FONT>
<BR><FONT SIZE=2>&gt; ITU has</FONT>
<BR><FONT SIZE=2>&gt; fully signed off. I don't see any rush for this.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt;&nbsp; &gt; Anyhow - I think it would be appropriate to add a note clarifying that</FONT>
<BR><FONT SIZE=2>&gt;&nbsp; &gt; IETF will not progress cr-ldp beyond Proposed Standard.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Adrian</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>
<BR>

<P><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>Loa Andersson</FONT>
</P>

<P><FONT SIZE=2>Mobile&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +46 739 81 21 64</FONT>
<BR><FONT SIZE=2>Email&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; loa@pi.se</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C2B73C.2CE74EF4--





From owner-ietf@ietf.org  Mon Jan 13 10:49:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14278;
	Mon, 13 Jan 2003 10:49:15 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y6ok-0006Ym-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 10:48:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Wmbe-0002TW-00
	for ietf@ran.ietf.org; Thu, 09 Jan 2003 19:01:02 -0500
Received: from zcars04f.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00677;
	Thu, 9 Jan 2003 18:52:07 -0500 (EST)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h09NtLw18706;
	Thu, 9 Jan 2003 18:55:21 -0500 (EST)
Received: from zcard04k.ca.nortel.com ([47.129.242.84]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id ZC6RW0Y0; Thu, 9 Jan 2003 18:55:23 -0500
Received: from [47.81.5.115] (asc4t1j9.us.nortel.com [47.81.5.115]) by zcard04k.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id ZJP6M275; Thu, 9 Jan 2003 18:55:21 -0500
User-Agent: Microsoft-Entourage/9.0.2.4011
Date: Thu, 09 Jan 2003 18:54:41 -0500
Subject: November meeting overlaps with IEEE 802
X-Sybari-Space: 00000000 00000000 00000000
From: Glenn Parsons <gparsons@nortelnetworks.com>
To: <ietf-secretariat@ietf.org>, <chair@ietf.org>
CC: <ietf@ietf.org>
Message-ID: <BA4375F1.10E9B%gparsons@nortelnetworks.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

Folks,

I just noticed that the November meeting date appears to have firmed up to
November 9-14.
http://ietf.org/meetings/0mtg-sites.txt

This conflicts with the IEEE 802 plenary.
http://ieee802.org/meeting/future_meetings.html

I think there are many people who would like to attend both.  Is there any
chance to shift the meeting at this point so as to not overlap with IEEE
802?

Cheers,
Glenn.






From owner-ietf@ietf.org  Mon Jan 13 10:49:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14323;
	Mon, 13 Jan 2003 10:49:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y6f7-0003VW-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 10:38:05 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18WNgy-0007Sb-00
	for ietf@ran.ietf.org; Wed, 08 Jan 2003 16:24:59 -0500
Received: from hoemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07614;
	Wed, 8 Jan 2003 16:15:46 -0500 (EST)
Received: from nj7460exch002h.wins.lucent.com (h135-17-42-35.lucent.com [135.17.42.35])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h08LJ1R23900;
	Wed, 8 Jan 2003 16:19:01 -0500 (EST)
Received: by nj7460exch002h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YSRTQ97T>; Wed, 8 Jan 2003 16:19:00 -0500
Message-ID: <D3F8FD817CC7DA408AEB2CAC631C042A98E5B4@nj7460exch012u.ho.lucent.com>
From: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
To: "'Ash, Gerald R (Jerry), ALASO'" <gash@att.com>,
        Loa Andersson
	 <loa@pi.se>, Adrian Farrel <afarrel@movaz.com>
Cc: iesg@ietf.org, Osama Aboul-Magd <osama@nortelnetworks.com>, ietf@ietf.org,
        "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Monica Lazer (E-mail)"
	 <mlazer@att.com>,
        "Varma, Eve L (Eve)" <evarma@lucent.com>,
        "Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to Informat
	ional
Date: Wed, 8 Jan 2003 16:18:59 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Gerry,

Happy new year.

In terms of where the liaisons are, not sure. I checked the link as well, and couldn't find any of the liaisons that was sent from ITU-T Q.14/15 to IETF CCAMP WG.

In terms of the intentions of the draft Recommendations G.7713.x series, these draft Recommendations are targetted to support the ASON control plane network. There is a difference between what IETF is working on and what ITU is working on, and these are mainly targeted for large incumbent carriers such as your company (and many of these requirements are driven by large carriers). For example, one obvious difference is the support of only IP addressing within the GMPLS. In the ITU ASON extensions, the G.7713.x protocols include support for not only the IP addresses, but also NSAP addresses.

Another obvious difference is that when ITU was developing ASON and IETF developing GMPLS, there was a position within CCAMP (during GMPLS development) that there is an inherent sharing of information between a user of the network and the network itself (the overlay vs. peer discussion). The ITU has always taken the approach that we need to support a range of information sharing, from fully sharing info (the I-NNI interface) to flexible info sharing (the E-NNI interface) to no sharing of info (the UNI interface). The majority of the extensions (NOTE these are extensions and not competing protocols) are to support these fundamental network design decisions.

Another example of the difference in design philosophy is in the area of routing. Within the CCAMP, routing extensions are made to the existing protocols to support additional link attributes for GMPLS. However, the concept of multiple domains and hierarchies are not really provided (not beyond what the existing protocol provides). These concepts (domains and hierarchies) are again driven by the large carriers (such as AT&T and BT). What we (as ITU-T participants) did were to listen to these requirements and added extensions that supports the carriers' requirements.

In terms of your question about interoperability, the protocol extensions from the ITU is designed as optional/additional "tools" as part of the GMPLS toolkit. If a vendor chooses to support the ITU's ASON application, they will implement. Otherwise they will only implement the core GMPLS and no more. Which vendor decides to implement what really depends on what carriers (such as your company) are going to ask for. The carriers have set the requirements in ITU and those requirements have driven the protocol extensions. The protocol design within the IETF were driven from a different direction (or a different set of companies -- more the enterprise customers).

Hope this answers your questions and concerns, and hope others will chime in with their opinion on this...

Zhi




-----Original Message-----
From: Ash, Gerald R (Jerry), ALASO [mailto:gash@att.com]
Sent: Wednesday, January 08, 2003 3:48 PM
To: Loa Andersson; Adrian Farrel
Cc: Ash, Gerald R (Jerry), ALASO; iesg@ietf.org; Osama Aboul-Magd;
ietf@ietf.org; Lin, Zhi-Wei (Zhi); hklam@lucent.com
Subject: RE: CORRECTION: Last Call: CR-LDP Extensions for ASON to
Informational


Adrian> I am saying that it sounds to me from the discussion that 
Adrian> the ITU has not yet reached consent. It seemed to me that 
Adrian> if the draft is intended to document the ITU preferences as 
Adrian> informational, it would be as well to wait until the ITU has
Adrian> fully signed off. I don't see any rush for this.

Loa> ok - I can see the difference - and it seems that you are correct. If
Loa> the ITU discussion still has some way to go before the discussion
Loa> settles and the preferences better known - wouldn't it be 
Loa> appropriate to wait until this happens?

ASON Signaling Recommendations G.7713.2 (GMPLS RSVP-TE) and G.7713.3 (GMPLS CR-LDP) are proposed for consent at the upcoming SG15 meeting, 20-31 January (Geneva).  A Liaison was sent to the IETF containing Recommendation text, but I can't find it on http://www.ietf.org/IESG/LIAISON/.

Both documents propose detailed protocol specifications including new TLVs (e.g., crankback TLV in G.7713.3).  The intent of these Recommendations is unclear.  

If these are statements of 'ITU preferences/requirements' which are made known to the IETF through the Informational RFCs, such as Osama's and Zhi's, then fine.  IETF can then take up the 'preferences/requirements' and consider them for upgrading RSVP-TE and CR-LDP protocols (although CR-LDP is capped).  

However, if they are intended as alternative protocol specs competing with the IETF specs, then that's a problem.  Which spec does a vendor implement and an operator use, given interoperability needs, etc.?  It would be analogous to the IETF specifying their version of G.709.

A clarification of the intent of these Recs. would be helpful.

Jerry Ash





From owner-ietf@ietf.org  Mon Jan 13 10:49:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14371;
	Mon, 13 Jan 2003 10:49:40 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y6ok-0006Ys-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 10:48:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18X3uT-00032c-00
	for ietf@ran.ietf.org; Fri, 10 Jan 2003 13:29:37 -0500
Received: from vorpal.notabug.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA09121
	for <ietf@ietf.org>; Fri, 10 Jan 2003 13:26:16 -0500 (EST)
Received: (qmail 30500 invoked from network); 10 Jan 2003 18:29:32 -0000
Received: from 12-249-96-16.client.attbi.com (HELO aaronsw.com) (12.249.96.16)
  by 0 with SMTP; 10 Jan 2003 18:29:32 -0000
Date: Fri, 10 Jan 2003 12:29:32 -0600
Subject: Re: Dan Bernstein's issues about namedroppers list operation
Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: namedroppers <namedroppers@ops.ietf.org>, iesg@ietf.org, ietf@ietf.org,
        "D. J. Bernstein" <djb@cr.yp.to>
To: Thomas Narten <narten@us.ibm.com>
From: Aaron Swartz <me@aaronsw.com>
In-Reply-To: <200301101624.h0AGOqL09468@rotala.raleigh.ibm.com>
Message-Id: <7661B517-24C9-11D7-9721-0003936780B2@aaronsw.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thomas Narten wrote:
> Namedroppers is a posters-only mailing list that is run in conformance
> with the policies outlined in
> http://www.ietf.cnri.reston.va.us/IESG/STATEMENTS/mail-submit- 
> policy.txt.

This states:
"""
4) Any held message that is later approved for distribution on the
    mailing list should appear on the list as a normal posting (e.g.,
    with the proper sender in the From address, etc.).
"""

Later, however, you write:
>>       [...] However, in
>>       the second message, he manually inserted my subscription  
>> address,
>>       despite my previous comments about private subscription  
>> addresses
>>       and forged unsubscription requests. (Was this malicious, or was  
>> it
>>       just mind-bogglingly stupid?)
>
> Or perhaps, it was to make it clear to the poster which address the
> posting was coming from, since there seems to be confusion at times
> about whether someone is posting from the same address to which they
> are subscribed.

Including someone's private subscription address is not done for a  
normal posting. Doing it for a held message is a violation of the rule  
above, no?

-- 
Aaron Swartz [http://www.aaronsw.com/]






From owner-ietf@ietf.org  Mon Jan 13 10:51:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14555;
	Mon, 13 Jan 2003 10:51:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y6om-0006aA-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 10:48:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18XukD-0007pL-00
	for ietf@ran.ietf.org; Sun, 12 Jan 2003 21:54:33 -0500
Received: from net.cc.swin.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19292
	for <ietf@ietf.org>; Sun, 12 Jan 2003 21:50:36 -0500 (EST)
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by net.cc.swin.edu.au (8.9.3/8.9.3) with ESMTP id NAA19842;
	Mon, 13 Jan 2003 13:53:53 +1100 (AEDT)
Message-ID: <3E222A40.6A472571@swin.edu.au>
Date: Mon, 13 Jan 2003 13:53:52 +1100
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: Searching for depressing moments of Internet history.....
References: <F12ECEA0435AD211B5280008C7ACBC85016B474B@BIGIRON>
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


Franck Martin wrote:
	[..]
> An interesting subject for a thesis:
> 
> The Porn and The Internet.

Sub-titled The Beauties and The Beasts ?

cheers,
gja





From owner-ietf@ietf.org  Mon Jan 13 10:51:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14556;
	Mon, 13 Jan 2003 10:51:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y6ol-0006Yy-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 10:48:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18X4BP-0008Qq-00
	for ietf@ran.ietf.org; Fri, 10 Jan 2003 13:47:07 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10770;
	Fri, 10 Jan 2003 13:43:45 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id NAA10067;
	Fri, 10 Jan 2003 13:40:43 -0500
Date: Fri, 10 Jan 2003 13:41:06 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Thomas Narten <narten@us.ibm.com>
cc: "D. J. Bernstein" <djb@cr.yp.to>, <ietf@ietf.org>, <iesg@ietf.org>,
        namedroppers <namedroppers@ops.ietf.org>
Subject: Re: Dan Bernstein's issues about namedroppers list operation
In-Reply-To: <200301101624.h0AGOqL09468@rotala.raleigh.ibm.com>
Message-ID: <Pine.LNX.4.44.0301101337570.16971-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

This isn't true. We have been examining the issue, and have found clear
evidence that Bernstein's email has been censored and handled differently
from other email to namedroppers in recent months, and in the past, prior
to changes in the adminstration of namedroppers.  We are not yet ready to
summarize this evidence.

However, it cannot be concluded that there is no such evidence.

Dean Anderson

On Fri, 10 Jan 2003, Thomas Narten wrote:

> Dan Bernstein has been making repeated claims that Randy is censoring
> his postings to namedroppers. I took a look at the claims he has made
> and here is how I see things.
>
> Executive summary: I see no evidence that Randy is censoring postings
> from Dan. It is the case that some of his messages do not appear to
> have made it out on namedroppers, but it is unclear why this is.
> Furthermore, given that most of these missing messages were cc'ed to
> other lists (i.e., the ietf and iesg lists), there is no evidence of
> censorship.
>
> Namedroppers is a posters-only mailing list that is run in conformance
> with the policies outlined in
> http://www.ietf.cnri.reston.va.us/IESG/STATEMENTS/mail-submit-policy.txt.
>
> Specifically, all mail sent to namedroppers is:
>
> 1) first run through spamassassin. Mail that is rejected here is not
>    archived, as the number of such messages is large. All mail sent to
>    mailing lists on the server hosting namedroppers is run though
>    spamassassin, so this is not a namedroppers-specific procedure.
>
> 2) if sent by a subscriber to the mailing list (or by someone in the
>    known posters list), the message is sent immediately.
>
> 3) Otherwise, it is queued waiting for approval (or rejection) by the
>    maling list operators. Both Randy and Mark Kosters see these
>    rejected postings. Mark has indicated that he has seen no rejected
>    postings that were not forwarded to the namedroppers mailing list
>    that should have been.
>
> It does appear that *some* of the message that Dan has sent to
> namedroppers have not appeared on the namedroppers mailing list. But
> it is unclear why that happened. At the time of these postings, some
> of his other messages have gone through. Also, most of the messages
> that didn't appear did appear on other mailing lists that were
> cc'ed. It is unclear why those messages did not make it to
> namedroppers, but now that Dan's posting address is in the the list of
> know posters for namedroppers, and his mail seems to be getting
> through, it seems best to just keep an eye on further problems and
> investigate them as soon as they happen (e.g, when relevant logs are
> available). I see no evidence that Randy (or anyone else) is singling
> out anyone's postings for rejection.
>
> Details on specifics follow.
>
> "D. J. Bernstein" <djb@cr.yp.to> writes:
>
> > Bush imposed his mailing-list control methods without IESG approval, in
> > violation of RFC 2418, section 3.2. He has been caught engaging in
> > content-based censorship several times:
>
> >    http://cr.yp.to/djbdns/namedroppers.html
>
> >     Background
> >
> > The DNS protocol is covered by various IETF specifications.
> > Unfortunately, obeying those specifications is not sufficient to ensure
> > interoperability with BIND, in part because the specifications are
> > ambiguous or otherwise flawed, and in part because BIND violates the
> > specifications in many ways.
> >
> > These facts have hurt competition, and contributed to BIND's market
> > share, at the expense of the users. For example, one site using lbnamed,
> > a special-purpose DNS implementation, has had interoperability problems
> > with BIND, and has been planning to abandon lbnamed in favor of BIND,
> > even though this means giving up some useful features.
> >
> > In late 1999, after yet another BIND security hole was announced, I
> > wrote a free BIND replacement. Interoperability among DNS
> > implementations is, of course, essential. I found the IETF
> > specifications horribly inadequate.
> >
> >
> >     The namedroppers mailing list
> >
> > IETF carries out its DNS protocol standardization activities within the
> > DNSEXT working group. The DNSEXT mailing list is
> > namedroppers@internic.net, also known as comp.protocols.dns.std.
>
> This is old and incorrect, for quite some time. The mailing list is
> namedroppers@ops.ietf.org. Mail from the mailing list may be gatewayed
> one-way to usenet, but the reverse is not true. [Actually, I've been
> told that usenet mail is selectively being forwarded back to the list
> by someone, but it seems "very selectively", as this has happened to
> only a handful of messages in several months.]
>
> > ``Within the scope of this WG are protocol issues, including message
> > formats, message handling, and data formats,'' the DNSEXT charter says.
> > Several specific issues have been identified as work items, but other
> > DNS protocol issues remain clearly within the charter. In particular,
> > namedroppers is obviously the right forum for implementors to discuss
> > current and future DNS interoperability problems.
> >
> > Unfortunately, namedroppers is being run in a way that slows down, and
> > sometimes prevents, public communication among DNS implementors.
> >
> > Messages to namedroppers are not forwarded directly to subscribers. They
> > are first sent to Randy Bush. They wait for Bush's review. Bush
> > discards, edits, or misdirects messages that he doesn't like, and passes
> > along what's left.
> >
> > Here are some specific examples. Many of these incidents involved
> > opsmail.internic.net, which used some painfully slow, creaky, obsolete
> > software to distribute messages to subscribers.
> >
> >     * 1998-12: Bush discarded a message from Richard Sexton commenting
> >       on a proposed extension to MX records, a DNS protocol element.
> >     * 1998-12: Bush edited a message of mine, unilaterally removing a
> >       paragraph at the top that asked why opsmail was so slow. How is
> >       someone supposed to find out what the namedroppers subscribers
> >       think of how the mailing list is run, if complaints to the list
> >       are censored?
> >     * 1999-01: Bush discarded a message from Richard Sexton about client
> >       interpretation of the AA bit, a DNS protocol element, by NSI, the
> >       operators of some well-known DNS TLDs.
> >     * 1999-12: Bush discarded a message of mine
> >       <namedroppers/19991219005223-16101-qmail@cr-yp-to> concerning yet
> >       another DNS protocol violation by BIND. ``This belongs in
> >       bind-users@isc.org, not namedroppers,'' Bush told me
> >       <namedroppers/e11zwx7-0000lb-00@roam-psg-com>, incorrectly.
> >     * 1999-12-31: opsmail finally sent a message that it had received on
> >       1999-11-04, nearly two months earlier, to a namedroppers
> >       subscription address that had been removed from the list on
> >       1999-11-25.
> >     * 1999-12-31: I sent an urgent message
> >       <namedroppers/19991231010737-16203-qmail@cr-yp-to> to namedroppers
> >       attempting to confirm rumors of a DNS server bug that, if true,
> >       would have been triggered on occasion by my new DNS cache. Someone
> >       else sent a message to namedroppers 14 hours later, and then
> >       another message 4 hours after that; 12 minutes later, Bush sent
> >       those two messages to opsmail; several hours later, opsmail
> >       finally forwarded the messages to me. A day later, I asked Bush
> >       why my message hadn't appeared yet. He finally sent my message to
> >       opsmail three days after I had sent it. I saw a copy from opsmail
> >       several hours after that.
> >     * 2000-01-12: I sent another message
> >       <namedroppers/20000113013505-28147-qmail@cr-yp-to> to namedroppers
> >       pointing out a security problem that I had described on bugtraq,
> >       and asking DNSEXT to fix the relevant RFC, which had been
> >       co-written by Bush. My message never appeared on namedroppers.
> >       Bush didn't send me an explanation. I learned much later that Bush
> >       had deliberately misdirected
> >       <namedroppers/20000123065236-2897-qmail@cr-yp-to> my message,
> >       sending it to the dnsop mailing list.
> >     * 2000-01-28: I sent a message
> >       <namedroppers/20000128015807-6574-qmail@cr-yp-to> to namedroppers
> >       pointing out how Bush's censorship activities had biased DNSEXT
> >       discussions, and a message
> >       <namedroppers/20000129035223-3523-qmail@cr-yp-to> to namedroppers
> >       criticizing Bush's unilateral statement of the namedroppers scope.
> >       These messages were direct responses to recent namedroppers
> >       messages, the first by Thomas Narten, the second by Bush. Bush
> >       sent both messages back to me, without saying explicitly what he
> >       had done with them.
> >     * 2000-02-20: I pointed out
> >       <namedroppers/20000220195445-21265-qmail@cr-yp-to> on namedroppers
> >       that thousands of system administrators were using dotted-decimal
> >       domain names in MX records. There was some discussion on
> >       namedroppers. Rob Austein and Bill Manning asked for evidence;
> >       Bush claimed that he couldn't find even a single example ``in
> >       almost twenty thousand zones secondaried here from all over the
> >       world.'' A few days later, I sent survey results
> >       <namedroppers/20000225221016-31751-qmail@cr-yp-to> to namedroppers
> >       showing that there were approximately fifteen /thousand/
> >       second-level .com domains with dotted-decimal domain names in
> >       their MX records, usually with no other MX records. My message
> >       never appeared on namedroppers. ``Please report bugs in peoples
> >       zone files to the people with the bugs, not namedroppers,'' Bush
> >       told me.
> >     * 2000-02-21: Bush discarded a message from Dean Anderson
> >       <namedroppers/3-0-32-20000221220332-01705a94@odie-av8-com>
> >       supporting expansion of the MX protocol definition to allow
> >       dotted-decimal domain names.
> >     * 2000-02-23: I sent another message
> >       <namedroppers/20000223081350-27092-qmail@cr-yp-to> to namedroppers
> >       objecting to Bush's censorship. Bush discarded my message.
> >     * 2000-03-12: I sent a message
> >       <namedroppers/20000312222447-11277-qmail@cr-yp-to> to namedroppers
> >       asking about DNS query transmission strategy. Bush wrote back:
> >       ``if your question is about the protocol, then fine. if it is
> >       about how the dns operates and how folk's implementations effect
> >       that, then post it to the mailing list for that implementation or
> >       to the dnsop list. i.e. keep your bind bashing off this list.'' I
> >       responded: ``My message asks about an efficiency problem in the
> >       DNS protocol, and gives some illustrative examples. Are you going
> >       to pass my message along to the list, or not?'' Bush discarded my
> >       messages without further comment.
> >     * 2001-03-17: I sent a message
> >       <namedroppers/20010317134602-7103-qmail@cr-yp-to> to namedroppers
> >       objecting to a BIND company proposal to modify the DNS protocol.
> >       Bush discarded my message without comment.
>
> All of the above is so old there is no point in discussing again. See,
> for example, http://www.iab.org/Documents/BernsteinAppealResponse.txt
>
> >     * 2002.11.17: I sent a message
> >       <namedroppers/20021117174553-55961-qmail@cr-yp-to> to namedroppers
> >       objecting to Bush and Gudmundsson sending the axfr-clarify
> >       <axfr-clarify.html> document to the IESG, and summarizing ten
> >       problems with that document. Bush silently discarded my
> >     message.
>
> This message was sent to the iesg, ietf and namedroppers mailing
> list. The message did make it out on at least the iesg mailing list
> (where I saw a copy), but I do not see it in the namedroppers archive.
>
> >     * 2002.11.20: I sent a message
> >       <namedroppers/20021120084916-34961-qmail@cr-yp-to> to namedroppers
> >       discussing the lack of consensus behind axfr-clarify and
> >       complaining about Bush's censorship. Bush silently discarded my
> >       message.
>
> Again, this message was posted to the ietf, iesg and namedroppers
> list. I see this message did get posted to the iesg list; I do not see
> it in the namedroppers archive.
>
> >     * 2002.11.20, continued: I sent a message
> >       <namedroppers/20021120103907-63440-qmail@cr-yp-to> to namedroppers
> >       discussing the interoperability problems in axfr-clarify. Bush
> >       silently discarded my message. After Bush wrote (on another list)
> >       ``it is easy to miss and therefore delete mis-posts,'' I sent a
> >       message <namedroppers/20021120202122-31601-qmail@cr-yp-to> to
> >       namedroppers saying ``Funny how this happens so often for people
> >       you disagree with'' and reminding Bush that he was causing
> >       problems for newsgroup readers, sublist readers, and ``readers
> >       with private subscription addresses''; Bush allowed that message
> >       through.
>
> Again, this message was posted to the ietf, iesg and namedroppers
> list. I see this message made it do the iesg list; I do not see it in
> the namedroppers archive.
>
> >     * 2002.11.20, continued: I sent a message
> >       <namedroppers/20021120203439-43796-qmail@cr-yp-to> to namedroppers
> >       discussing the use of separate TCP/UDP ports. Bush silently
> >       discarded my message.
>
> This note was allegedely sent to namedroppers (and no where else). It
> is not in the namedroppers archive. It is noted, however, that other
> messages from Dan did appear on namedroppers that day.
>
> >       My subscription address stopped receiving messages from the
> >       namedroppers mailing list. About 40 hours later, I asked Bush what
> >       was going on:
> >
> >           Is that address still on the list? If not, why not? Does your
> >           software reveal subscription addresses? Does it allow
> >           unconfirmed unsubscription requests? Does it use
> >           non-cryptographic cookies in confirmation notices? If the
> >           address is still on the list, why aren't the outgoing messages
> >           being delivered? Is there some general problem with all
> >           addresses?
> >
> >       Suddenly the messages all came through.
>
> Can't say what this was all about. Temporary mail problems?
>
> >     * 2002.11.23: I sent a message
> >       <namedroppers/20021123061646-22603-qmail@cr-yp-to> and another
> >       message <namedroppers/20021123172816-71385-qmail@cr-yp-to> to
> >       namedroppers. Bush promptly forwarded both messages. However, in
> >       the second message, he manually inserted my subscription address,
> >       despite my previous comments about private subscription addresses
> >       and forged unsubscription requests. (Was this malicious, or was it
> >       just mind-bogglingly stupid?)
>
> Or perhaps, it was to make it clear to the poster which address the
> posting was coming from, since there seems to be confusion at times
> about whether someone is posting from the same address to which they
> are subscribed.
>
> "D. J. Bernstein" <djb@cr.yp.to> writes:
>
> >     * 2002.11.25: I sent a message
> > From: "D. J. Bernstein" <djb@cr.yp.to>
> > To: namedroppers@ops.ietf.org
> > Cc: sob@harvard.edu
> > Date: 15 Dec 2002 03:18:14 -0000
> > Subject: Re: repeating records
> > Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
>
> > I've noticed that Randy Bush discarded Len Budney's note on this topic:
> > http://groups.google.com/groups?selm=asnul4%24640g%241%40isrv4.isc.org
>
> Not so.  Len's note was posted to usenet, not to the namedroppers
> mailing list. Mail from usenet cannot be assumed to get gatewayed back
> to the mailing list.
>
> Thomas
>
> --
> to unsubscribe send a message to namedroppers-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/namedroppers/>
>






From owner-ietf@ietf.org  Mon Jan 13 11:07:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15256;
	Mon, 13 Jan 2003 11:07:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y74E-0001EW-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 11:04:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y6qT-0006tr-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 10:49:49 -0500
Received: from ginger.lcs.mit.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14104
	for <ietf@ietf.org>; Mon, 13 Jan 2003 10:45:43 -0500 (EST)
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.6/8.12.6) with ESMTP id h0DFmvMY011848;
	Mon, 13 Jan 2003 10:48:57 -0500
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.6/8.12.6/Submit) id h0DFmumg011846;
	Mon, 13 Jan 2003 10:48:56 -0500
Date: Mon, 13 Jan 2003 10:48:56 -0500
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200301131548.h0DFmumg011846@ginger.lcs.mit.edu>
To: ietf@ietf.org, internet-history@postel.org
Subject: Cluster Addressing and CIDR
Cc: jnc@ginger.lcs.mit.edu, roki@cosy.sbg.ac.at
Sender: owner-ietf@ietf.org
Precedence: bulk

I was reading a paper by Paul Francis and Ramakrishna Gummadi, and a
reference caused me to re-read an interesting-sounding old paper they
referenced (RFC-1380, "IESG Deliberations on Routing and Addressing") to
refresh my memory of it, and further to read similar documents it referenced
(e.g. RFC-1287, "Towards the Future Internet Architecture").

In so doing, I was upset to see that the references included no mention of
the work of Carl-Herbert Rokitansky, whose "cluster addressing" scheme was
the first case I can recall of someone proposing to group a number of IP
network numbers together, and treat them as a single entity - the idea which
later became the key concept behind CIDR.

Granted, the original cluster addressing scheme had a different goal entirely
(it had to do with getting routing to work correctly with multiple X.25
networks) - but still, it put the thought of that mechanism in the heads of
everyone who was around at the time.

So, if anyone writes about CIDR in the future, can they please include a
reference to the cluster addressing work? Thanks.

	Noel





From owner-ietf@ietf.org  Mon Jan 13 11:33:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15980;
	Mon, 13 Jan 2003 11:33:23 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y7TP-0002JJ-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 11:30:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y7LJ-00029z-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 11:21:41 -0500
Received: from hosting.altserver.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15550
	for <ietf@ietf.org>; Mon, 13 Jan 2003 11:17:36 -0500 (EST)
Received: from lns18m-11-202.w.club-internet.fr ([212.195.146.202] helo=mine.utel.net)
	by hosting.altserver.com with esmtp (Exim 3.36 #1)
	id 18Y7KS-0007S5-00
	for ietf@ietf.org; Mon, 13 Jan 2003 08:20:48 -0800
Message-Id: <5.1.0.14.0.20030113171348.02c3f8c0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 13 Jan 2003 17:23:44 +0100
To: ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: email and spam (was: Re: namedroppers, continued)
In-Reply-To: <33549559.1041963726@P2>
References: <009e01c2b67b$45926590$0701a8c0@nailed.org>
 <009e01c2b67b$45926590$0701a8c0@nailed.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-3175290A; boundary="=======13C61120======="
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - hosting.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - utel.net
Sender: owner-ietf@ietf.org
Precedence: bulk

--=======13C61120=======
Content-Type: text/plain; x-avg-checked=avg-ok-3175290A; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit

Dear John,
I am afraid that at this stage (e-mail + 40 or so years) telling someone to 
read the archives has no meaning. And telling him to post if he has a 
_new_idea either.

Could we not think of an FPS (frequently proposed solutions) where each 
defeated "solutions" would be listed and quickly discussed. There would be 
two good reasons:

1. to provide a true list of what has been proposed. It would save time to 
all and provide a good negative check list for those with an idea. At least 
it would be new to the FPS: it would be added or used.

2. very often the roots of the true solution is something which has been 
half thought and overlooked. Or something triggered in someone's mind by 
another idea.

jfc

PS. From what you quote, you seem to consider that SPAM=spoofing? Are there 
statistics and trends about that?



On 00:22 08/01/03, John C Klensin said:

>--On Tuesday, 07 January, 2003 13:33 -0500 Doug
><Dougxx2@carolina.rr.com> wrote:
>
> >> Doug has rediscovered the idea of closing open mail relays to
> > prevent
> >> unauthorised use by outsiders sending to outsiders. This was
> >> a big thing in the early 90s when email became popular.
> >
> > This may seem to be a bit basic for some of the people who
> > have worked on this problem for years. My intention was not to
> > prove that I had the latest and greatest solution to the spam
> > problem. It was to get the ball rolling in an open discussion
> > forum and present my ideas on the topic in the hopes that
> > someone who knew more than me on the topic would as well.
> >...
>
>Ok, Doug.  Let me take a shot at simultaneously explaining the
>problem here and  why your suggested solutions are getting such
>resistance.  Perhaps a different approach may succeed where
>Lloyd's didn't (not his fault, I'm sure).
>
>Almost all of the measures you have suggested have serious
>side-effects or critical prerequisites.  In the last analysis,
>most of us would rather put up with a little spam than pay the
>prices involved.  Others are sufficiently fed up with spam that
>they are willing to consider some very radical changes to how we
>use email.  But, regardless of how that comes out, the decisions
>have been fairly explicit: people have thought of your
>suggestions, and others, and their impact, and have made fairly
>explicit decisions about preferences.  My comment about X.400 of
>a few weeks ago was intended to address those issues, but
>apparently made a reference too far in the past, or too subtle,
>for some of the people who have been participating in the
>discussion.
>
>The people who have been through it are reluctant to start the
>discussion again because the dead horse has been kicked into an
>unrecognizable pulp. There has been a good deal of discussion,
>in many archives, that it would be good for you to read.  If you
>then come up with a _new_ idea that doesn't revisit the old
>problems, many of us would be enthused about listening.  It is
>only the old and discredited proposals that are met with
>intolerance.
>
>Let me take a closely-related pair of examples from your note.
>As I understand it, you would like ISPs (really email providers)
>to take responsibility for authenticating their customers.  And
>you would like IP addresses shown in mail header traces to be
>reliable.  Ok.  Those two things turn out to be much more about
>trust relationships than they are about protocols: one can make
>major changes to protocols without changing the trust
>relationships at all, and can accomplish those things without
>any changes in the protocols.  But, assuming that you aren't
>willing to trust anyone who can operate a mail-sending protocol,
>there are only a few ways that you can trust the source and
>origins of email.
>
>For example, we could, as a society, start licensing email
>providers, require each licensed provider to accept mail only
>from other licensed providers and from users they can
>authenticate (with severe penalties for violating those rules).
>That would make folks who would like to go back to business
>models in which they charge for every item of mail very happy.
>It would make many of the rest of us unhappy.  But it would
>work... and, while some protocol enhancements might make it
>easier to support, nothing is really required beyond SMTP as it
>exists today.
>
>Similarly, you could decide to work with an email mailbox
>provider who would refuse to accept mail from any site with
>which it didn't have an agreement about user authentication and
>traffic and which, were relaying permitted, would insist that
>any site from which it accepted a relayed message impose the
>same requirements on its users.  With some prototype agreement
>forms, this could be a way to build up a trust web similar to
>the licensing one, using a web of bilateral agreements rather
>than governmental action.
>
>But either of those approaches would result in less legitimate
>mail getting through.  For instance, I run my own mail servers
>and, as far as I know, can authenticate anyone who originates
>mail here.  But I have neither the resources nor the inclination
>to participate in a large collection of bilateral contractual
>agreements, nor to start applying for licenses.
>
>The issues with those bad IP addresses are similar.  Most are
>spoofed.  You can trust the information in Received headers only
>as far back as the last mail host you trust to report
>information accurately.  If there is a spammer deliberately
>deciding to deceive you, anything earlier is likely to be trash,
>not because the wrong information is in the Whois tables, but
>because the data in the Received fields is being made up (either
>at random or in the hope of pinning the spam on someone else).
>And, again, formalizing  the trust relationships through
>contracts or licenses would help a great deal, and might be the
>only solution, but those options carry a high price in terms of
>generally accessibility and usability of email.
>
>regards,
>     john
>
>p.s.
>
> > Asking questions, presenting possible solutions, and learning
> > from mistakes is how we get solutions.
>
>And learning what has been done and discussed in the past,
>before asking your questions of thousands of people, is usually
>considered, at least, polite.
>
>
>
>
>
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.427 / Virus Database: 240 - Release Date: 06/12/02

--=======13C61120=======--




From owner-ietf@ietf.org  Mon Jan 13 12:09:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17006;
	Mon, 13 Jan 2003 12:09:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y80S-0003co-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 12:04:12 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y7zm-0003bD-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 12:03:30 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16673
	for <ietf@ietf.org>; Mon, 13 Jan 2003 11:59:24 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h0DH2cb11327;
	Mon, 13 Jan 2003 09:02:38 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id RAA03175;
	Mon, 13 Jan 2003 17:02:38 GMT
Date: Mon, 13 Jan 2003 17:02:38 GMT
Message-Id: <200301131702.RAA03175@gra.isi.edu>
To: ietf@ietf.org, internet-history@postel.org, jnc@ginger.lcs.mit.edu
Subject: Re: Cluster Addressing and CIDR
Cc: roki@cosy.sbg.ac.at
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Noel Chiappa wrote:

  *> (e.g. RFC-1287, "Towards the Future Internet Architecture").
  *> 
  *> In so doing, I was upset to see that the references included no mention of
  *> the work of Carl-Herbert Rokitansky, whose "cluster addressing" scheme was
  *> the first case I can recall of someone proposing to group a number of IP
  *> network numbers together, and treat them as a single entity - the idea which
  *> later became the key concept behind CIDR.
  *> 

Noel,

You are right.  I recall seeing drafts of Roki's work, but there does
not seem to be an RFC or IEN containing his work.  Was it published
in any archival form?

Bob Braden



From owner-ietf@ietf.org  Mon Jan 13 12:56:53 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17999;
	Mon, 13 Jan 2003 12:56:53 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y8nd-0006HQ-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 12:55:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y8kP-0006Ak-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 12:51:41 -0500
Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17813
	for <ietf@ietf.org>; Mon, 13 Jan 2003 12:47:30 -0500 (EST)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0DHonX17965
	for <ietf@ietf.org>; Mon, 13 Jan 2003 12:50:49 -0500 (EST)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2653.19)
	id <WGT685LW>; Mon, 13 Jan 2003 11:50:48 -0600
Message-ID: <54E40201497DF142B06B27255953F79702AEEA49@il0015exch007u.ih.lucent.com>
From: "Vaudreuil, Greg M (Greg)" <gregv@lucent.com>
To: Bob Braden <braden@ISI.EDU>, ietf@ietf.org, internet-history@postel.org,
        jnc@ginger.lcs.mit.edu
Cc: roki@cosy.sbg.ac.at
Subject: RE: Cluster Addressing and CIDR
Date: Mon, 13 Jan 2003 11:50:45 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk


I don't recall that any of the ID's from the Public Data Networks working group were published as RFC's.  There are references to the PDN drafts in old proceedings... back when we included the list of current ID's in each issue!! I have a reference in a copy of the FIfteenth IETF - Hawaii (October 31st, 1989 to:

"Internet Cluster Addressing Scheme", by Carl-Herbert Rokitanski/Fern Uni-Hagen, August 1989 <draft-ietf-pdn-clusterscheme-00.txt>

"Application of the Cluster Addressing Scheme to X.25 Public Data Networks and Worldwide Internet Network Reachability Information Exchange", by Carl-Herbert Rokitanski/Fern Uni-Hagen, August 1989, <draft-ietf-pen=pdncluster-00.txt>

"Assignment/Reservation of Internet Network Numbers for the PDN-Cluster", by Carl-Herbert Rokitanski/Fern Uni-Hagen, July 1989, <draft-ietf-pdn-pdnclusternetassignm-00.txt>

I guess there may be some old ID archives around that may have these documents.  

Wondering why I still have old paper proceedings in my office,

Greg V.



-----Original Message-----
From: Bob Braden [mailto:braden@ISI.EDU]
Sent: Monday, January 13, 2003 11:03 AM
To: ietf@ietf.org; internet-history@postel.org; jnc@ginger.lcs.mit.edu
Cc: roki@cosy.sbg.ac.at
Subject: Re: Cluster Addressing and CIDR


Noel Chiappa wrote:

  *> (e.g. RFC-1287, "Towards the Future Internet Architecture").
  *> 
  *> In so doing, I was upset to see that the references included no mention of
  *> the work of Carl-Herbert Rokitansky, whose "cluster addressing" scheme was
  *> the first case I can recall of someone proposing to group a number of IP
  *> network numbers together, and treat them as a single entity - the idea which
  *> later became the key concept behind CIDR.
  *> 

Noel,

You are right.  I recall seeing drafts of Roki's work, but there does
not seem to be an RFC or IEN containing his work.  Was it published
in any archival form?

Bob Braden



From owner-ietf@ietf.org  Mon Jan 13 13:12:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18371;
	Mon, 13 Jan 2003 13:12:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y938-0007BY-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 13:11:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y91S-00078Z-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 13:09:18 -0500
Received: from lnscu5.lns.cornell.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18207
	for <ietf@ietf.org>; Mon, 13 Jan 2003 13:05:12 -0500 (EST)
Received: from lnxcu9.lns.cornell.edu (lnxcu9.lns.cornell.edu [128.84.46.100])
	by lnscu5.lns.cornell.edu (8.12.2/8.12.2) with ESMTP id h0DI8W4e005337;
	Mon, 13 Jan 2003 13:08:32 -0500 (EST)
Received: from lnxcu9.lns.cornell.edu (localhost.localdomain [127.0.0.1])
	by lnxcu9.lns.cornell.edu (8.12.5/8.12.2) with ESMTP id h0DI8VlC019036;
	Mon, 13 Jan 2003 13:08:31 -0500
Received: (from dsr@localhost)
	by lnxcu9.lns.cornell.edu (8.12.5/8.12.5/Submit) id h0DI8Vvi019032;
	Mon, 13 Jan 2003 13:08:31 -0500
X-Authentication-Warning: lnxcu9.lns.cornell.edu: dsr set sender to dsr@mail.lns.cornell.edu using -f
To: "support@webmastersguide.com" <support@webmastersguide.com>
Cc: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
References: <5.1.0.14.0.20030113103944.02da6b40@mail.utel.net>
	<127190000.1042452256@askvoll.hjemme.alvestrand.no>
	<200301131306.h0DD64222318@mx1.xcite.net>
From: Dan Riley <dsr@mail.lns.cornell.edu>
Date: 13 Jan 2003 13:08:31 -0500
In-Reply-To: <200301131306.h0DD64222318@mx1.xcite.net>
Message-ID: <shlm1oq5wg.fsf@lnxcu9.lns.cornell.edu>
Lines: 15
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Sender: owner-ietf@ietf.org
Precedence: bulk

"support@webmastersguide.com" <support@webmastersguide.com> writes:
> In the first couple years of the web, adult sites financed it's
> development.  In 1997 and 1998 90% of commerce on the web was adult
> related.

The first few years of the web were financed by government funded
research laboratories--initially CERN in Europe starting in 1990,
followed by NCSA and others in late 1992.  Commercial use didn't
become a significant factor until 1994--until then the Internet was
effectively ruled by the NSFNet backbone "no commercial use" policy.
(There was certainly lots of porn on the internet before then, but
not lots of money being made--most of the money-making porn was
still on BBSs.)

-dan



From owner-ietf@ietf.org  Mon Jan 13 14:02:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20000;
	Mon, 13 Jan 2003 14:02:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y9oW-00010l-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 14:00:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y9Iu-0000BF-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 13:27:20 -0500
Received: from eritrea.oit.unc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18865
	for <ietf@ietf.org>; Mon, 13 Jan 2003 13:23:13 -0500 (EST)
Received: from unc.edu (localhost [127.0.0.1])
	by eritrea.oit.unc.edu (8.12.2/8.12.2) with ESMTP id h0DIQUjh001250;
	Mon, 13 Jan 2003 13:26:31 -0500 (EST)
Message-ID: <3E2304D6.6070906@unc.edu>
Date: Mon, 13 Jan 2003 13:26:30 -0500
From: Simon Spero <ses@unc.edu>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
References: <250226437.1042390981@localhost>
In-Reply-To: <250226437.1042390981@localhost>
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

Harald Tveit Alvestrand wrote:

> I just wonder: does anyone know/remember when the first Web porn site 
> came online?

I believe Kapor's law was first stated at the January '92 Usenix (The 
first use for any new communications technology is sex).

Anyone remember the day when someone found a world-writable directory 
somewhere on the official X distribution site at MIT,which promptly got 
picked up by all the nightly mirrors (many of which then got indexed by 
archie)...






From owner-ietf@ietf.org  Mon Jan 13 14:19:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20633;
	Mon, 13 Jan 2003 14:19:01 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YA44-0001nt-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 14:16:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y9al-0000fJ-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 13:45:47 -0500
Received: from cnri.reston.va.us (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19488;
	Mon, 13 Jan 2003 13:41:37 -0500 (EST)
Received: from marcia.cnri.reston.va.us (cnri-7-204.cnri.reston.va.us [132.151.7.204])
	by cnri.reston.va.us (8.11.6+Sun/8.11.3) with ESMTP id h0DIiq813736;
	Mon, 13 Jan 2003 13:44:52 -0500 (EST)
Message-Id: <5.1.0.14.2.20030113133550.048fdd90@odin>
X-Sender: mbeaulie@odin
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 13 Jan 2003 13:40:48 -0500
To: Glenn Parsons <gparsons@nortelnetworks.com>, <ietf-secretariat@ietf.org>,
        <chair@ietf.org>
From: Marcia Beaulieu <mbeaulie@ietf.org>
Subject: Re: November meeting overlaps with IEEE 802
Cc: <ietf@ietf.org>
In-Reply-To: <BA4375F1.10E9B%gparsons@nortelnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Glenn,

Unfortunately we are unable to change the IETF dates at this time.

Marcia

At 06:54 PM 1/9/03 -0500, Glenn Parsons wrote:
>Folks,
>
>I just noticed that the November meeting date appears to have firmed up to
>November 9-14.
>http://ietf.org/meetings/0mtg-sites.txt
>
>This conflicts with the IEEE 802 plenary.
>http://ieee802.org/meeting/future_meetings.html
>
>I think there are many people who would like to attend both.  Is there any
>chance to shift the meeting at this point so as to not overlap with IEEE
>802?
>
>Cheers,
>Glenn.






From owner-ietf@ietf.org  Mon Jan 13 14:39:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21286;
	Mon, 13 Jan 2003 14:39:38 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YAOL-0004xN-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 14:37:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YABC-00028p-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 14:23:26 -0500
Received: from carwash.centivinc.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA20678
	for <ietf@ietf.org>; Mon, 13 Jan 2003 14:19:19 -0500 (EST)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003011314234919916
 for <ietf@ietf.org>; Mon, 13 Jan 2003 14:23:49 -0500
Received: from centive.com ([10.10.51.177]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 13 Jan 2003 14:20:39 -0500
Message-ID: <3E231183.4020208@centive.com>
Date: Mon, 13 Jan 2003 14:20:35 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
References: <250226437.1042390981@localhost> <3E2304D6.6070906@unc.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Jan 2003 19:20:39.0538 (UTC) FILETIME=[DB867520:01C2BB38]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Simon Spero wrote:

> I believe Kapor's law was first stated at the January '92 Usenix (The 
> first use for any new communications technology is sex).

Not exactly a new phenomenon--the oldest statues known, going back over 
20,000 years, are figures of nude women.  Objecting to it is like 
getting depressed about the fact that we still need to eat.

-- 
/=============================================\
|John Stracke      |jstracke@centive.com      |
|Principal Engineer|http://www.centive.com    |
|Centive           |My opinions are my own.   |
|=============================================|
|Cogito ergo Spud. (I think, therefore I yam.)|
\=============================================/







From owner-ietf@ietf.org  Mon Jan 13 15:09:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22095;
	Mon, 13 Jan 2003 15:09:10 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YAsM-0006xm-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 15:08:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YArQ-0006uX-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 15:07:04 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21947
	for <ietf@ietf.org>; Mon, 13 Jan 2003 15:02:56 -0500 (EST)
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18YAqV-000CbN-00; Mon, 13 Jan 2003 15:06:07 -0500
Date: Mon, 13 Jan 2003 15:06:07 -0500
From: John C Klensin <john-ietf@jck.com>
To: jfcm <info@utel.net>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: email and spam (was: Re: namedroppers, continued)
Message-ID: <52295278.1042470367@P2>
In-Reply-To: <5.1.0.14.0.20030113171348.02c3f8c0@mail.utel.net>
References: <009e01c2b67b$45926590$0701a8c0@nailed.org>
 <009e01c2b67b$45926590$0701a8c0@nailed.org>
 <5.1.0.14.0.20030113171348.02c3f8c0@mail.utel.net>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Monday, 13 January, 2003 17:23 +0100 jfcm <info@utel.net>
wrote:

> Dear John,
> I am afraid that at this stage (e-mail + 40 or so years)
> telling someone to read the archives has no meaning. And
> telling him to post if he has a _new_idea either.

You are entitled to your opinion.  I was only trying to suggest
that people who come to the IETF list, and propose the same old,
failed, ideas as if they had just received a relevation from on
high are likely to get some resistance... and to explain that
resistance.

> Could we not think of an FPS (frequently proposed solutions)
> where each defeated "solutions" would be listed and quickly
> discussed. There would be two good reasons:
> 
> 1. to provide a true list of what has been proposed. It would
> save time to all and provide a good negative check list for
> those with an idea. At least it would be new to the FPS: it
> would be added or used.
> 
> 2. very often the roots of the true solution is something
> which has been half thought and overlooked. Or something
> triggered in someone's mind by another idea.

Variations on this idea have been proposed to the IESG and IAB
several times, and have not gone anywhere.  I'll leave
explanations as to why to someone else, but  at a minimum, there
has been a shortage of volunteers to maintain a "dumb ideas
archive" (I know, that isn't quite what you said) and a shortage
of entities willing to shield such volunteers from liability.

> PS. From what you quote, you seem to consider that
> SPAM=spoofing? Are there statistics and trends about that?

There is certainly non-spoofed spam, including the many
materials that claim one has subscribed to an opt-in list or and
others that claim they are conformant to some law which never
passed.  I don't have any statistics that go beyond the
anecdotal.  But, if you look at the mass e-mailing software
packages that are frequently advertised (not exclusively by
spam), most of very proud of their capabilities to hide actual
message origins and to use the facilities of others as relaying
in supposedly-undetectable ways.  Similarly, as Doug and others
have observed, spam often comes with headers that are
sufficiently spoofed to make addresses and other data useless.
I assume --but cannot prove-- that all of these symptoms are
indications that spammers know that messages that use consistent
and accurate origin information are easily filtered out and
discarded and that most ISPs have terms and conditions of
service that prohibits using their facilities to spam.

regards,
     john




From owner-ietf@ietf.org  Mon Jan 13 15:54:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23956;
	Mon, 13 Jan 2003 15:54:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YBZt-0001xN-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 15:53:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YBZV-0001vX-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 15:52:37 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23663
	for <ietf@ietf.org>; Mon, 13 Jan 2003 15:48:30 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h0DKpXb10287;
	Mon, 13 Jan 2003 12:51:33 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id UAA03390;
	Mon, 13 Jan 2003 20:51:33 GMT
Date: Mon, 13 Jan 2003 20:51:33 GMT
Message-Id: <200301132051.UAA03390@gra.isi.edu>
To: info@utel.net, john-ietf@jck.com
Subject: Re: email and spam (was: Re: namedroppers, continued)
Cc: ietf@ietf.org, braden@ISI.EDU
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


  *> > Could we not think of an FPS (frequently proposed solutions)
  *> > where each defeated "solutions" would be listed and quickly
  *> > discussed. There would be two good reasons:
  *> > 
  *> > 1. to provide a true list of what has been proposed. It would
  *> > save time to all and provide a good negative check list for
  *> > those with an idea. At least it would be new to the FPS: it
  *> > would be added or used.
  *> > 
  *> > 2. very often the roots of the true solution is something
  *> > which has been half thought and overlooked. Or something
  *> > triggered in someone's mind by another idea.
  *> 
  *> Variations on this idea have been proposed to the IESG and IAB
  *> several times, and have not gone anywhere.  I'll leave
  *> explanations as to why to someone else, but  at a minimum, there
  *> has been a shortage of volunteers to maintain a "dumb ideas
  *> archive" (I know, that isn't quite what you said) and a shortage
  *> of entities willing to shield such volunteers from liability.

John,

True.  However, a useful, and perhaps feasible, approach would be for
a person knowledgable about the problem area to write an
Informational "review" RFC about it.  Such an RFC would review the
problem, the suggested solutions, and their up/downsides.  Such a
document would not have to be complete to be very useful; a snapshot at
a particular time would be a big step forward.

Bob Braden



From owner-ietf@ietf.org  Mon Jan 13 15:56:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22098;
	Mon, 13 Jan 2003 15:09:10 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YAnY-0006g5-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 15:03:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YAhM-0005it-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 14:56:40 -0500
Received: from prue.eim.surrey.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21617
	for <ietf@ietf.org>; Mon, 13 Jan 2003 14:52:32 -0500 (EST)
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 18YAcj-0003kp-00; Mon, 13 Jan 2003 19:51:53 +0000
Date: Mon, 13 Jan 2003 19:51:51 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: John Stracke <jstracke@centive.com>
cc: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
In-Reply-To: <3E231183.4020208@centive.com>
Message-ID: <Pine.GSO.4.50.0301131948180.29956-100000@artemis.ee.surrey.ac.uk>
References: <250226437.1042390981@localhost> <3E2304D6.6070906@unc.edu>
 <3E231183.4020208@centive.com>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-102.0 required=7.0
	tests=AWL,IN_REP_TO,NOSPAM_INC,QUOTED_EMAIL_TEXT,REFERENCES,
	      SCS_STUDY,SPAM_PHRASE_00_01,USER_AGENT_PINE,
	      USER_IN_WHITELIST
	version=2.43
X-Scanner: exiscan *18YAcj-0003kp-00*znXh7Umdrzc* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

Simon Spero wrote:
>
> I believe Kapor's law was first stated at the January '92 Usenix (The
> first use for any new communications technology is sex).

any SUCCESSFUL communications technology, surely?

Think I've just discovered why 8-track failed, and gotten new insight
into that whole VHS vs Betamax thing.

As for getting funding to study this - doesn't anyone remember Marty
Rimm?
http://www.eff.org/Publications/Declan_McCullagh/www/rimm/

(and Time Magazine showing a lack of editorial standards long before
their Apple iMac advertorials.)

L.

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



From owner-ietf@ietf.org  Mon Jan 13 16:53:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25482;
	Mon, 13 Jan 2003 16:53:40 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YCS6-0004sh-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 16:49:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YCRr-0004qn-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 16:48:47 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25178
	for <ietf@ietf.org>; Mon, 13 Jan 2003 16:44:40 -0500 (EST)
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18YCR3-000Cm5-00; Mon, 13 Jan 2003 16:47:57 -0500
Date: Mon, 13 Jan 2003 16:47:57 -0500
From: John C Klensin <john-ietf@jck.com>
To: Bob Braden <braden@ISI.EDU>, "info@utel.net" <info@utel.net>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: email and spam (was: Re: namedroppers, continued)
Message-ID: <58406748.1042476477@P2>
In-Reply-To: <200301132051.UAA03390@gra.isi.edu>
References:  <200301132051.UAA03390@gra.isi.edu>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Monday, 13 January, 2003 20:51 +0000 Bob Braden
<braden@ISI.EDU> wrote:

> 
>   *> > Could we not think of an FPS (frequently proposed
> solutions)   *> > where each defeated "solutions" would be
> listed and quickly   *> > discussed. There would be two good
> reasons:
>   *> > 
>   *> > 1. to provide a true list of what has been proposed. It
> would   *> > save time to all and provide a good negative
> check list for   *> > those with an idea. At least it would be
> new to the FPS: it   *> > would be added or used.
>   *> > 
>   *> > 2. very often the roots of the true solution is
> something   *> > which has been half thought and overlooked.
> Or something   *> > triggered in someone's mind by another
> idea.
>   *> 
>   *> Variations on this idea have been proposed to the IESG
> and IAB   *> several times, and have not gone anywhere.  I'll
> leave   *> explanations as to why to someone else, but  at a
> minimum, there   *> has been a shortage of volunteers to
> maintain a "dumb ideas   *> archive" (I know, that isn't quite
> what you said) and a shortage   *> of entities willing to
> shield such volunteers from liability.
> 
> John,
> 
> True.  However, a useful, and perhaps feasible, approach would
> be for a person knowledgable about the problem area to write an
> Informational "review" RFC about it.  Such an RFC would review
> the problem, the suggested solutions, and their up/downsides.
> Such a document would not have to be complete to be very
> useful; a snapshot at a particular time would be a big step
> forward.

Bob,

Absolutely.  But such a hypothetical author would have to be
very motivated.  Posting of an I-D would almost certainly
produce a large amount of mail.  Some would be sympathetic,
others would make useful suggestions, still others would want to
debate particular points based on more or less realistic
perceptions about how the world works, the morals of spamming.
Then the document would go to the IESG and RFC Editor.  While I
agree with your observation that completeness would not be
needed for utility, previous experience predicts that IESG
members would nit-pick the document, or just stall, until all of
the points that any IESG member considered important were
covered, and covered in a way compatible with that IESG member's
views.  If views on the IESG conflicted, the document could
easily be help up forever, and I note that there is no appeal
against IESG delay or failure to take an action.  Then, again
based on experience, the odds seem high that the RFC Editor
would delay it, requesting editorial and formatting changes that
are not covered in any written style manual, not responding to
questions about those requests for weeks or months at a time,
and so on.   

The combination of these processes could easily lead to a delay
of six to nine months or longer between the time the author
thought he or had a finished document and the time of
publication, by which time the document might well be obsolete
(producing more abuse for the author). 

So, while I agree that such a document would be useful, I would
imagine that someone would need to be either extremely motivated
or quite naive about how IETF and the publication process
functions to try writing it.  It is, unfortunately, much easier
to ignore repetitions of unworkable ideas and possibly to try to
briefly explain the problems with them.

regards,
    john




From owner-ietf@ietf.org  Mon Jan 13 17:22:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26170;
	Mon, 13 Jan 2003 17:22:08 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YCtB-0006le-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 17:17:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YCsq-0006jk-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 17:16:40 -0500
Received: from hosting.altserver.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26011
	for <ietf@ietf.org>; Mon, 13 Jan 2003 17:12:32 -0500 (EST)
Received: from lns10v-12-229.w.club-internet.fr ([213.44.239.229] helo=mine.utel.net)
	by hosting.altserver.com with esmtp (Exim 3.36 #1)
	id 18YCrr-0004bq-00; Mon, 13 Jan 2003 14:15:40 -0800
Message-Id: <5.1.0.14.0.20030113223637.04140ec0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 13 Jan 2003 22:57:12 +0100
To: John C Klensin <john-ietf@jck.com>
From: jfcm <info@utel.net>
Subject: Re: email and spam (was: Re: namedroppers, continued)
Cc: ietf@ietf.org
In-Reply-To: <52295278.1042470367@P2>
References: <5.1.0.14.0.20030113171348.02c3f8c0@mail.utel.net>
 <009e01c2b67b$45926590$0701a8c0@nailed.org>
 <009e01c2b67b$45926590$0701a8c0@nailed.org>
 <5.1.0.14.0.20030113171348.02c3f8c0@mail.utel.net>
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-14447FCD; boundary="=======53AA738======="
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - hosting.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - utel.net
Sender: owner-ietf@ietf.org
Precedence: bulk

--=======53AA738=======
Content-Type: text/plain; x-avg-checked=avg-ok-14447FCD; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit

On 21:06 13/01/03, John C Klensin said:
>--On Monday, 13 January, 2003 17:23 +0100 jfcm <info@utel.net>
>wrote:
> > Dear John,
> > I am afraid that at this stage (e-mail + 40 or so years)
> > telling someone to read the archives has no meaning. And
> > telling him to post if he has a _new_idea either.
>
>You are entitled to your opinion.  I was only trying to suggest
>that people who come to the IETF list, and propose the same old,
>failed, ideas as if they had just received a relevation from on
>high are likely to get some resistance... and to explain that
>resistance.

I know and I agree. My point is 40 years of reading is somewhat long and 
uncertain.

> > Could we not think of an FPS (frequently proposed solutions)
> > where each defeated "solutions" would be listed and quickly
> > discussed. There would be two good reasons:
> >
> > 1. to provide a true list of what has been proposed. It would
> > save time to all and provide a good negative check list for
> > those with an idea. At least it would be new to the FPS: it
> > would be added or used.
> >
> > 2. very often the roots of the true solution is something
> > which has been half thought and overlooked. Or something
> > triggered in someone's mind by another idea.
>
>Variations on this idea have been proposed to the IESG and IAB
>several times, and have not gone anywhere.  I'll leave
>explanations as to why to someone else, but  at a minimum, there
>has been a shortage of volunteers to maintain a "dumb ideas
>archive" (I know, that isn't quite what you said) and a shortage
>of entities willing to shield such volunteers from liability.

hmmmm. Let take it another way. Would it help if we set-up
a place where each proposition could be registered in a few lines
by the proposer or dead ends documented by old-timers?

Instead of flaming proposers, they could just advise them to
register their propositions first. The flaming would still be here
but the register would be built.

As to know if it would be a dumb or a too brillant ideas archive :-)
jfc








--=======53AA738=======--




From owner-ietf@ietf.org  Mon Jan 13 17:44:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26887;
	Mon, 13 Jan 2003 17:44:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YDHQ-0007w4-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 17:42:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YDGM-0007rf-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 17:40:58 -0500
Received: from fnal.gov (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26604
	for <ietf@ietf.org>; Mon, 13 Jan 2003 17:36:50 -0500 (EST)
Received: from gungnir.fnal.gov ([131.225.80.1])
 by smtp.fnal.gov (PMDF V6.0-24 #37519)
 with ESMTP id <0H8O00A8DCAXSE@smtp.fnal.gov> for ietf@ietf.org; Mon,
 13 Jan 2003 16:40:09 -0600 (CST)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.11.6+Sun/8.11.6) with ESMTP id h0DMe9H04118; Mon,
 13 Jan 2003 16:40:09 -0600 (CST)
Date: Mon, 13 Jan 2003 16:40:09 -0600
From: Matt Crawford <crawdad@fnal.gov>
Subject: Re: Searching for depressing moments of Internet history.....
In-reply-to: "13 Jan 2003 13:53:52 +1100." <3E222A40.6A472571@swin.edu.au>
To: grenville armitage <garmitage@swin.edu.au>
Cc: ietf@ietf.org
Message-id: <200301132240.h0DMe9H04118@gungnir.fnal.gov>
Sender: owner-ietf@ietf.org
Precedence: bulk

> > An interesting subject for a thesis:
> > 
> > The Porn and The Internet.
> 
> Sub-titled The Beauties and The Beasts ?

Watch it.  One fuzzball joke and I am outta here.



From owner-ietf@ietf.org  Mon Jan 13 17:58:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27335;
	Mon, 13 Jan 2003 17:58:57 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YDUv-0000MT-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 17:56:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YDTy-0000KI-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 17:55:02 -0500
Received: from sj-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27176
	for <ietf@ietf.org>; Mon, 13 Jan 2003 17:50:54 -0500 (EST)
Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0DMsDFp014980
	for <ietf@ietf.org>; Mon, 13 Jan 2003 14:54:13 -0800 (PST)
Received: from cisco.com (rtp-vpn2-448.cisco.com [10.82.241.192])
	by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with SMTP id ADN30389;
	Mon, 13 Jan 2003 14:45:29 -0800 (PST)
Received: by cisco.com (sSMTP sendmail emulation); Mon, 13 Jan 2003 17:54:13 -0500
Date: Mon, 13 Jan 2003 17:54:13 -0500
From: Scott W Brim <sbrim@cisco.com>
To: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
Message-ID: <20030113225412.GB2092@SBRIM-W2K1>
Mail-Followup-To: Scott W Brim <sbrim@cisco.com>, ietf@ietf.org
References: <250226437.1042390981@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <250226437.1042390981@localhost>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

I have a vague recollection that CU-SeeMe was used for porn in late
1993.  We were so innocent, we thought people would use it for
conferencing.  



From owner-ietf@ietf.org  Mon Jan 13 18:15:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27844;
	Mon, 13 Jan 2003 18:15:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YDlO-0001IJ-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 18:13:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YDkP-0001Eq-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 18:12:01 -0500
Received: from sopacsun.fig.net.fj (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27662
	for <ietf@ietf.org>; Mon, 13 Jan 2003 18:07:50 -0500 (EST)
Received: from flinux.sopac.org.fj (unknown [202.62.1.33])
	by sopacsun.fig.net.fj (Postfix) with ESMTP id 867F7AAC6E
	for <ietf@ietf.org>; Mon, 13 Jan 2003 18:10:25 -0500 (EST)
Received: by flinux.sopac.org.fj (Postfix, from userid 500)
	id C8437AE48B; Tue, 14 Jan 2003 11:10:19 +1200 (FJT)
Subject: Re: Searching for depressing moments of Internet history.....
From: Franck Martin <franck@sopac.org>
To: ietf@ietf.org
In-Reply-To: 
	<Pine.GSO.4.50.0301131948180.29956-100000@artemis.ee.surrey.ac.uk>
References: <250226437.1042390981@localhost> <3E2304D6.6070906@unc.edu>
	<3E231183.4020208@centive.com> 
	<Pine.GSO.4.50.0301131948180.29956-100000@artemis.ee.surrey.ac.uk>
Content-Type: multipart/alternative; boundary="=-CjZmiEZiURr0b2gfyNqs"
X-Mailer: Ximian Evolution 1.0.8-3mdk 
Date: 14 Jan 2003 11:10:19 +1200
Message-Id: <1042499419.21759.41.camel@flinux.sopac.org.fj>
Mime-Version: 1.0
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-CjZmiEZiURr0b2gfyNqs
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

On Tue, 2003-01-14 at 07:51, Lloyd Wood wrote:

    Simon Spero wrote:
    >
    > I believe Kapor's law was first stated at the January '92 Usenix (The
    > first use for any new communications technology is sex).
    
    any SUCCESSFUL communications technology, surely?
    

Well before that, the French had the minitel... France Telecom was a
long time ashamed to admit that the success of the service was entirely
due to adult services.

It has always been the case why:
The content is readily available or very quick to produce (no need to
write a thesis first)
The content is appalling to many customers

There is only one other area that has nearly the same qualities:
"VIOLENCE"

Unfortunately due to the good moral: "depressing moments" we tend now to
sell to our kids violence oriented games... no wonder that many people
in the world want to whack Irak. (I'm not neccessarily against whacking
irak, I just said it is crasy to think it will be easy and without great
pains).

Make Love not War... as they said...

How can the Internet Help?

Cheers.

--=-CjZmiEZiURr0b2gfyNqs
Content-Type: text/html; charset=utf-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/1.0.4">
</HEAD>
<BODY>
On Tue, 2003-01-14 at 07:51, Lloyd Wood wrote:
    <BLOCKQUOTE>
<PRE><FONT COLOR="#737373"><FONT SIZE="3"><I>Simon Spero wrote:</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>&gt;</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>&gt; I believe Kapor's law was first stated at the January '92 Usenix (The</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>&gt; first use for any new communications technology is sex).</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I></FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I>any SUCCESSFUL communications technology, surely?</FONT></FONT></I>
<FONT COLOR="#737373"><FONT SIZE="3"><I></FONT></FONT></I></PRE>
    </BLOCKQUOTE>
Well before that, the French had the minitel... France Telecom was a long time ashamed to admit that the success of the service was entirely due to adult services.
<BR>

<BR>
It has always been the case why:
<BR>
The content is readily available or very quick to produce (no need to write a thesis first)
<BR>
The content is appalling to many customers
<BR>

<BR>
There is only one other area that has nearly the same qualities: &quot;VIOLENCE&quot;
<BR>

<BR>
Unfortunately due to the good moral: &quot;depressing moments&quot; we tend now to sell to our kids violence oriented games... no wonder that many people in the world want to whack Irak. (I'm not neccessarily against whacking irak, I just said it is crasy to think it will be easy and without great pains).
<BR>

<BR>
Make Love not War... as they said...
<BR>

<BR>
How can the Internet Help?
<BR>

<BR>
Cheers.
</BODY>
</HTML>

--=-CjZmiEZiURr0b2gfyNqs--



From owner-ietf@ietf.org  Mon Jan 13 18:28:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28178;
	Mon, 13 Jan 2003 18:28:50 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YDxw-000254-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 18:26:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YDwD-00021v-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 18:24:13 -0500
Received: from mailman.packetdesign.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27985
	for <ietf@ietf.org>; Mon, 13 Jan 2003 18:20:04 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.12.3/8.12.3) with ESMTP id h0DNNDOM053211;
	Mon, 13 Jan 2003 15:23:13 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Mon, 13 Jan 2003 15:23:13 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: ietf@ietf.org
Subject: IETF 56 hotel code
Message-ID: <20030113151957.L12681-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

At this moment, the Group/Convention Code that the Hilton San
Francisco has in its computer is "IET" rather than "IETF" as specified
on the IETF web page.  I imagine that this may get fixed one way or
the other at some point.

                                                        -- Steve




From owner-ietf@ietf.org  Mon Jan 13 18:46:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28570;
	Mon, 13 Jan 2003 18:46:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YEFO-00030h-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 18:44:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YEEP-0002x9-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 18:43:01 -0500
Received: from netcore.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28427
	for <ietf@ietf.org>; Mon, 13 Jan 2003 18:38:51 -0500 (EST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h0DNg0M20197;
	Tue, 14 Jan 2003 01:42:00 +0200
Date: Tue, 14 Jan 2003 01:42:00 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Scott W Brim <sbrim@cisco.com>
cc: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
In-Reply-To: <20030113225412.GB2092@SBRIM-W2K1>
Message-ID: <Pine.LNX.4.44.0301140139510.20165-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 13 Jan 2003, Scott W Brim wrote:
> I have a vague recollection that CU-SeeMe was used for porn in late
> 1993.  We were so innocent, we thought people would use it for
> conferencing.  

Speaking of technologies, has porn ever been multicast?  Could have been a 
killer application in those times when bandwidth was scarce..

Perhaps that's why multicast never really kicked off..

-- 
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 Jan 13 18:49:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28701;
	Mon, 13 Jan 2003 18:49:17 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YEKD-0003Ax-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 18:49:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YEIb-00037E-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 18:47:21 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28468
	for <ietf@ietf.org>; Mon, 13 Jan 2003 18:43:10 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h0DNhbqZ001799;
	Mon, 13 Jan 2003 18:43:37 -0500
Message-Id: <200301132343.h0DNhbqZ001799@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
Cc: John Stracke <jstracke@centive.com>, ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history..... 
In-Reply-To: Your message of "Mon, 13 Jan 2003 19:51:51 GMT."
             <Pine.GSO.4.50.0301131948180.29956-100000@artemis.ee.surrey.ac.uk> 
References: <250226437.1042390981@localhost> <3E2304D6.6070906@unc.edu> <3E231183.4020208@centive.com>
            <Pine.GSO.4.50.0301131948180.29956-100000@artemis.ee.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_434405048P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 13 Jan 2003 18:43:37 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 13 Jan 2003 19:51:51 GMT, Lloyd Wood said:
> Simon Spero wrote:
> >
> > I believe Kapor's law was first stated at the January '92 Usenix (The
> > first use for any new communications technology is sex).
> 
> any SUCCESSFUL communications technology, surely?

This must mean that 3G phones are destined to be sucessful...

http://media.guardian.co.uk/newmedia/story/0,7496,872546,00.html

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

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

iD8DBQE+I08pcC3lWbTT17ARAkqAAJ96e7RRgXqubjl0FAxWyO6DRY7c1wCfS2Hj
svHGMaV/k9wDW1pKjujrKM0=
=K274
-----END PGP SIGNATURE-----

--==_Exmh_434405048P--



From owner-ietf@ietf.org  Mon Jan 13 20:33:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00972;
	Mon, 13 Jan 2003 20:33:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YFs2-0008MW-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 20:28:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YFrD-0008KA-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 20:27:11 -0500
Received: from merlot.juniper.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00724;
	Mon, 13 Jan 2003 20:23:00 -0500 (EST)
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 h0E1QKS69969;
	Mon, 13 Jan 2003 17:26:21 -0800 (PST)
	(envelope-from kireeti@juniper.net)
Received: from localhost (kireeti@localhost)
	by kummer.juniper.net (8.11.6/8.9.3) with ESMTP id h0E1QKu42803;
	Mon, 13 Jan 2003 17:26:20 -0800 (PST)
	(envelope-from kireeti@juniper.net)
X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs
Date: Mon, 13 Jan 2003 17:26:20 -0800 (PST)
From: Kireeti Kompella <kireeti@juniper.net>
To: <iesg@ietf.org>
cc: <ietf@ietf.org>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
In-Reply-To: <200212311722.MAA26085@ietf.org>
Message-ID: <20030113135014.L42168-100000@kummer.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi All,

On Tue, 31 Dec 2002, The IESG wrote:

> The IESG has received a request to consider CR-LDP Extensions for ASON
> <draft-aboulmagd-ccamp-crldp-ason-ext-02.txt> as an Informational RFC.
> This has been reviewed in the IETF but is not the product of an IETF
> Working Group.

I have two comments about this draft.

The first is that the draft calls for assignment of code points for
some new messages, TLVs and status codes.  The draft, however, fails
to say from which spaces these should come (e.g., that to be allocated
by IETF Consensus, First Come First Served, Experimental).  If this is
not specified, then I would suggest that code points from Experimental
spaces be used.

If code points are to be allocated from the space to be allocated by
IETF Consensus, I strongly suggest that a *Standards Track* document be
written, with more detail on the messages, especially their processing.
Also, more detail on what the goal is here, under what circumstances
these messages need to be sent/replied to, etc.

Kireeti.




From owner-ietf@ietf.org  Tue Jan 14 03:12:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18371;
	Tue, 14 Jan 2003 03:12:24 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YM0L-0007rx-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 03:01:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YLze-0007qQ-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 03:00:18 -0500
Received: from netcore.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18027
	for <ietf@ietf.org>; Tue, 14 Jan 2003 02:56:03 -0500 (EST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h0E7xOH22978
	for <ietf@ietf.org>; Tue, 14 Jan 2003 09:59:24 +0200
Date: Tue, 14 Jan 2003 09:59:24 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: IETF56: is Friday on the agenda?
Message-ID: <Pine.LNX.4.44.0301140955320.22964-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Hello,

When looking at IETF56 meeting dates, in particular I note that Friday is 
again included.

A lot of people are probably interested in what its status is intended to 
be when considering flights, like:

 1) use it fully
 2) use it, only morning sessions
 3) only use it if really necessary
 4) will not use it
 5) something else

What's the intent (of course, the final could change..)?  My guess would
be somewhere between 2)-3).

-- 
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 Jan 14 07:00:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22016;
	Tue, 14 Jan 2003 07:00:56 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YPdn-0006tv-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 06:53:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YPd0-0006tc-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 06:53:10 -0500
Received: from ierw.net.avaya.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21784;
	Tue, 14 Jan 2003 06:48:51 -0500 (EST)
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 GAA02916;
	Tue, 14 Jan 2003 06:49:41 -0500 (EST)
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 GAA02905;
	Tue, 14 Jan 2003 06:49:40 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: November meeting overlaps with IEEE 802
Date: Tue, 14 Jan 2003 13:52:09 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0300979A@is0004avexu1.global.avaya.com>
Thread-Topic: November meeting overlaps with IEEE 802
Thread-Index: AcK7OSh23VnnagRhQtCHcdQq8XvhsQAib21A
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Marcia Beaulieu" <mbeaulie@ietf.org>,
        "Glenn Parsons" <gparsons@nortelnetworks.com>,
        <ietf-secretariat@ietf.org>, <chair@ietf.org>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA22016

That's a very unfortunate conflict for everybody who is participating in the IEEE and IETF process, and has WG chair, and/or editor responsibilities in both organizations. This scheduling conflict was avoided at least for the last eleven years since I started to attend the IETF meetings. What happened this time?

Dan


> -----Original Message-----
> From: Marcia Beaulieu [mailto:mbeaulie@ietf.org]
> Sent: Monday, January 13, 2003 8:41 PM
> To: Glenn Parsons; ietf-secretariat@ietf.org; chair@ietf.org
> Cc: ietf@ietf.org
> Subject: Re: November meeting overlaps with IEEE 802
> 
> 
> Hi Glenn,
> 
> Unfortunately we are unable to change the IETF dates at this time.
> 
> Marcia
> 
> At 06:54 PM 1/9/03 -0500, Glenn Parsons wrote:
> >Folks,
> >
> >I just noticed that the November meeting date appears to 
> have firmed up to
> >November 9-14.
> >http://ietf.org/meetings/0mtg-sites.txt
> >
> >This conflicts with the IEEE 802 plenary.
> >http://ieee802.org/meeting/future_meetings.html
> >
> >I think there are many people who would like to attend both. 
>  Is there any
> >chance to shift the meeting at this point so as to not 
> overlap with IEEE
> >802?
> >
> >Cheers,
> >Glenn.
> 
> 
> 
> 
> 



From owner-ietf@ietf.org  Tue Jan 14 07:22:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22358;
	Tue, 14 Jan 2003 07:22:19 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YQ3v-0007OU-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 07:20:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YQ3I-0007O3-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 07:20:20 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22252;
	Tue, 14 Jan 2003 07:16:01 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 96237625AB; Tue, 14 Jan 2003 13:19:21 +0100 (CET)
Date: Tue, 14 Jan 2003 13:19:22 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>,
        Marcia Beaulieu <mbeaulie@ietf.org>,
        Glenn Parsons <gparsons@nortelnetworks.com>, ietf-secretariat@ietf.org,
        chair@ietf.org
Cc: ietf@ietf.org
Subject: RE: November meeting overlaps with IEEE 802
Message-ID: <195580000.1042546762@askvoll.hjemme.alvestrand.no>
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F0300979A@is0004avexu1.global.avaya.com>
References:  <AAB4B3D3CF0F454F98272CBE187FDE2F0300979A@is0004avexu1.global.av
 aya.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, januar 14, 2003 13:52:09 +0200 "Romascanu, Dan (Dan)" 
<dromasca@avaya.com> wrote:

> That's a very unfortunate conflict for everybody who is participating in
> the IEEE and IETF process, and has WG chair, and/or editor
> responsibilities in both organizations. This scheduling conflict was
> avoided at least for the last eleven years since I started to attend the
> IETF meetings. What happened this time?

Nobody reported the IEEE meeting to the calendar that the secretariat keeps 
at http://www.ietf.org/meetings/events.cal.html (or if anyone did, it was 
lost) - and none of the people who went looking for conflicts on that date 
knew of the IEEE dates.

They are now added...

                      Harald




From owner-ietf@ietf.org  Tue Jan 14 08:06:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23044;
	Tue, 14 Jan 2003 08:06:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YQjG-0008IU-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 08:03:42 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YQiC-0008Hy-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 08:02:36 -0500
Received: from iere.net.avaya.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22952;
	Tue, 14 Jan 2003 07:58:17 -0500 (EST)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h0ECx1808736;
	Tue, 14 Jan 2003 07:59:01 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h0ECx0n08720;
	Tue, 14 Jan 2003 07:59:00 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: November meeting overlaps with IEEE 802
Date: Tue, 14 Jan 2003 15:01:35 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0300979F@is0004avexu1.global.avaya.com>
Thread-Topic: November meeting overlaps with IEEE 802
Thread-Index: AcK7xy0+ElYfd6qQQeuuVnpEyyI7+wABVozQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Harald Tveit Alvestrand" <harald@Alvestrand.no>,
        "Marcia Beaulieu" <mbeaulie@ietf.org>,
        "Glenn Parsons" <gparsons@nortelnetworks.com>,
        <ietf-secretariat@ietf.org>, <chair@ietf.org>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA23044

Harald,

I was thinking that the IETF secretariat is looking by default at the schedule of organizations like IEEE or ITU-T, and tries to avoid conflicts with their meetings, as well as with the major networking industry shows. 

IEEE 802 meetings schedule is available at http://ieee802.org/meeting/future_meetings.html. Dates are scheduled for the IEEE 802 plenary meetings until 2005. 

Dan


> -----Original Message-----
> From: Harald Tveit Alvestrand [mailto:harald@alvestrand.no]
> Sent: Tuesday, January 14, 2003 2:19 PM
> To: Romascanu, Dan (Dan); Marcia Beaulieu; Glenn Parsons; 
> ietf-secretariat@ietf.org; chair@ietf.org
> Cc: ietf@ietf.org
> Subject: RE: November meeting overlaps with IEEE 802
> 
> 
> 
> 
> --On tirsdag, januar 14, 2003 13:52:09 +0200 "Romascanu, Dan (Dan)" 
> <dromasca@avaya.com> wrote:
> 
> > That's a very unfortunate conflict for everybody who is 
> participating in
> > the IEEE and IETF process, and has WG chair, and/or editor
> > responsibilities in both organizations. This scheduling conflict was
> > avoided at least for the last eleven years since I started 
> to attend the
> > IETF meetings. What happened this time?
> 
> Nobody reported the IEEE meeting to the calendar that the 
> secretariat keeps 
> at http://www.ietf.org/meetings/events.cal.html (or if anyone 
> did, it was 
> lost) - and none of the people who went looking for conflicts 
> on that date 
> knew of the IEEE dates.
> 
> They are now added...
> 
>                       Harald
> 
> 



From owner-ietf@ietf.org  Tue Jan 14 10:13:07 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26444;
	Tue, 14 Jan 2003 10:13:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YSfX-0003S9-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 10:07:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YSfD-0003Rq-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 10:07:39 -0500
Received: from lightwave.chromisys.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26022;
	Tue, 14 Jan 2003 10:03:21 -0500 (EST)
Received: by lightwave.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <4GJZ1JM8>; Tue, 14 Jan 2003 07:06:35 -0800
Message-ID: <9D42C6E086250248810DCADA39CE7EFC972118@nimbus>
From: John Drake <jdrake@calient.net>
To: "'Kireeti Kompella'" <kireeti@juniper.net>, iesg@ietf.org
Cc: ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Tue, 14 Jan 2003 07:06:34 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Kireeti,

Presumably your comments, which I agree with, apply to
draft-lin-ccamp-gmpls-ason-rsvpte-04.txt as well?

Thanks,

John

-----Original Message-----
From: Kireeti Kompella [mailto:kireeti@juniper.net]
Sent: Monday, January 13, 2003 5:26 PM
To: iesg@ietf.org
Cc: ietf@ietf.org
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational


Hi All,

On Tue, 31 Dec 2002, The IESG wrote:

> The IESG has received a request to consider CR-LDP Extensions for ASON
> <draft-aboulmagd-ccamp-crldp-ason-ext-02.txt> as an Informational RFC.
> This has been reviewed in the IETF but is not the product of an IETF
> Working Group.

I have two comments about this draft.

The first is that the draft calls for assignment of code points for
some new messages, TLVs and status codes.  The draft, however, fails
to say from which spaces these should come (e.g., that to be allocated
by IETF Consensus, First Come First Served, Experimental).  If this is
not specified, then I would suggest that code points from Experimental
spaces be used.

If code points are to be allocated from the space to be allocated by
IETF Consensus, I strongly suggest that a *Standards Track* document be
written, with more detail on the messages, especially their processing.
Also, more detail on what the goal is here, under what circumstances
these messages need to be sent/replied to, etc.

Kireeti.




From owner-ietf@ietf.org  Tue Jan 14 11:46:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02781;
	Tue, 14 Jan 2003 11:46:57 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YU7m-0000Fa-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 11:41:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YFFT-0006mB-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 19:48:12 -0500
Received: from plusavs01.sbg.ac.at (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA29890
	for <ietf@ietf.org>; Mon, 13 Jan 2003 19:43:23 -0500 (EST)
Received: FROM sm.sbg.ac.at BY plusavs01.sbg.ac.at ; Tue Jan 14 01:13:52 2003 +0100
Received: from tapir.cosy.sbg.ac.at ([141.201.223.63]) by sm.sbg.ac.at
          (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35)
          with ESMTP id at; Tue, 14 Jan 2003 01:29:48 +0100
Message-Id: <5.0.2.1.2.20030114011804.02eccd60@mail.cosy.sbg.ac.at>
X-Sender: roki@mail.cosy.sbg.ac.at
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 14 Jan 2003 01:21:56 +0100
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, "Bob Braden" <braden@ISI.EDU>,
        "Vaudreuil, Greg M (Greg)" <gregv@lucent.com>, <ietf@ietf.org>,
        <internet-history@postel.org>, <JimFleming@ameritech.net>,
        <steinle@smartvia.de>,
        "Elisabeth Porteneuve" <Elisabeth.Porteneuve@cetp.ipsl.fr>,
        <bortzmeyer@nic.fr>, "Vittorio Bertola" <vb@vitaminic.net>,
        <abel@able-towers.com>,
        "Joey Borda **star*walker**" <starwalker@gay.com>,
        <espresso@e-scape.net>, <jefsey@club-internet.fr>, <mgeist@uottawa.ca>,
        <harris@cabase.org.ar>, <Amadeu@nominalia.com>,
        <apisan@servidor.unam.mx>, <helmut.schink@icn.siemens.de>,
        <jcohen@shapirocohen.com>, <junsec@wide.ad.jp>,
        <censslin@ntia.doc.gov>, <chandley@ntia.doc.gov>, <DEvans@doc.gov>,
        <ellen@rony.com>, <eric@hi-tek.com>, <nvictory@ntia.doc.gov>,
        <rdesilva@ntia.doc.gov>, <RLayton@ntia.doc.gov>,
        "Ron Sherwood" <sherwood@islands.vi>,
        "Stephen Waters" <swaters@amicus.com>,
        "Stephane Bortzmeyer" <bortzmeyer@gitoyen.net>,
        "Simon Higgs" <simon@higgs.com>, <richard.hill@itu.int>,
        "Richard J. Sexton" <richard@vrx.net>, <raul@inia.org.uy>,
        <k@widgital.com>, "Jkhan" <Jkhan@MetroMgr.com>,
        "Ben Edelman" <edelman@law.harvard.edu>,
        "@quasar Internet Solutions, Inc." <shore@quasar.net>
From: "Rokitansky, Carl-Herbert" <roki@cosy.sbg.ac.at>
Subject: Re: Cluster Addressing and CIDR
Cc: <sotiris@hermesnetwork.com>,
        "Richard Henderson" <richardhenderson@ntlworld.com>,
        <micheal@beethoven.com>, <jwkckid1@ix.netcom.com>,
        <harivijapur@rediffmail.com>,
        "Bruce Young" <Bruce@barelyadequate.info>,
        "Alexander Svensson" <alexander@svensson.de>,
        "Joe Baptista" <baptista@dot-god.com>,
        "David Goldstein" <goldstein_david@yahoo.com.au>,
        <andy@navigator.co.nz>, <barrister@chambers.gen.nz>,
        <grant.forsyth@clear.co.nz>,
        "Joop Teernstra" <terastra@terabytz.co.nz>, <pdthrush@actrix.co.nz>,
        <KathrynKL@aol.com>, <yjpark@myepark.com>, <mouhamet@next.sn>,
        <saq66@umkc.edu>, <carl.rokitansky@sbg.ac.at>
In-Reply-To: <200301131548.h0DFmumg011846@ginger.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA02781

Dear Noel,
Dear Bob,
Dear Greg,

As you might understand, I am quite happy to hear from you all, and of 
course memories pop up on the work of the IETF / PDN Group in which the 
"Cluster Addressing Scheme" was discussed intensively. In fact, the main 
idea was to extend the "Subnet Addressing Scheme" but in the "other 
direction", with the intention, that not only subnets, but even several 
different Internet networks appear to be reachable "locally" e.g. by direct 
X.25 links, so that similar routing decision algorithms can be be applied, 
using an appropriate "Cluster Addressing Mask", in which only those bits of 
the IP address corresponding to the same "cluster" are set to "1".

In fact, the "Cluster Addressing Scheme" was never published as RFC or IEN, 
but was published in:
[1] Carl-Herbert Rokitansky, "Internet Cluster Addressing Scheme and its 
Application to Public Data  Networks",  Proc.  9th International Conference 
on Computer Communication  (ICCC' 88), pp. 482-491, Tel Aviv, Israel, 
Oct./Nov. 1988.

[2] Carl-Herbert Rokitansky, "Hierarchical VAN-gateway 
Algorithms  and  PDN-Cluster  Addressing Scheme for Worldwide 
Interoperation between Local TCP/IP Networks via X.25 Networks", Informatik 
Fachberichte 205, Springer Verlag Berlin, pp. 758 - 774, Feb. 1989.

and as IETF/PDN Drafts:
- Carl-Herbert Rokitansky, "Internet Cluster Addressing Scheme", PDN Draft 
for Internet Engineering Task Force (IETF), July 1989.

- Carl-Herbert Rokitansky, "Application of the Cluster Addressing Scheme to 
X.25 Public Data Networks and Worldwide Internet Reachability Information 
Exchange", PDN Draft for Internet Engineering Task Force (IETF), July 1989.

It's "only" a bit more than 13 years ago, but it seems to be an eternity, 
taking into account, what happened since then !

Bob Braden wrote:
 >Roki,
 >It's never too late to repent! The RFC Editor would be glad to
 >publish your latest Internet-Draft, even at this late date. We
 >think it is important that seminal ideas be reflected in an
 >archival document series.
 >Regards,
 >Bob Braden

Of course, I would support, if the RFC Editor would be interested to 
publish the latest internet draft of the "Cluster Addressing Scheme", etc., 
in an archival document series, but I have to check, if I have an 
electronic (and readable) copy available myself, so I would appreciate if 
some appropriate people could also check if they have an easier access to 
such copies in an electronic archive !

So, please expect subsequent message(s) on this issue.
If you need any additional information, please let me know !

Thanks for bringing this issue up,
Best regards,

Carl-Herbert Rokitansky (Roki)
=======================

PS: As far as I can recall (having currently no access to any old 
documents) the IETF (or plans for it ?) was established in 1984 in a 
meeting in Malvern, UK at RSRE, in Sept (?) 1984 (could anyone please 
confirm), in which several of us participated ! Do you have any plans 
already to celebrate the 20th anniversary of the establishment of the IETF 
! Please keep me informed. Thanks ! Roki.
==================================================================

Am 10:48 13.01.03 -0500 schrieben Sie:
>I was reading a paper by Paul Francis and Ramakrishna Gummadi, and a
>reference caused me to re-read an interesting-sounding old paper they
>referenced (RFC-1380, "IESG Deliberations on Routing and Addressing") to
>refresh my memory of it, and further to read similar documents it referenced
>(e.g. RFC-1287, "Towards the Future Internet Architecture").
>
>In so doing, I was upset to see that the references included no mention of
>the work of Carl-Herbert Rokitansky, whose "cluster addressing" scheme was
>the first case I can recall of someone proposing to group a number of IP
>network numbers together, and treat them as a single entity - the idea which
>later became the key concept behind CIDR.
>
>Granted, the original cluster addressing scheme had a different goal entirely
>(it had to do with getting routing to work correctly with multiple X.25
>networks) - but still, it put the thought of that mechanism in the heads of
>everyone who was around at the time.
>
>So, if anyone writes about CIDR in the future, can they please include a
>reference to the cluster addressing work? Thanks.
>
>         Noel

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

H.-Prof. Dr. Carl-Herbert Rokitansky

Universität Salzburg
Inst. f. Computerwissenschaften
(Computer Science Institute)
Jakob-Haringerstr. 2
A-5020 Salzburg, Austria

Tel.: +49-172-241 04 71 (GSM)
Fax: +49-172-50-241 04 71 or +43-662-8044-611 or +43-662-64 69 90 18
EMail: <roki@cosy.sbg.ac.at> or <carl.rokitansky@sbg.ac.at>
======================================================






From owner-ietf@ietf.org  Tue Jan 14 11:47:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02814;
	Tue, 14 Jan 2003 11:47:33 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YU7n-0000Gk-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 11:41:15 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YIar-0001e8-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 23:22:30 -0500
Received: from ns1.vrx.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04381
	for <ietf@ietf.org>; Mon, 13 Jan 2003 23:18:12 -0500 (EST)
Received: from panchax (mbv3-pl-ri14.kos.net [216.191.189.110])
	by ns1.vrx.net (Postfix) with SMTP
	id AD2A0D2A2; Mon, 13 Jan 2003 23:21:13 -0500 (EST)
X-Sender: richard@vrx.net
X-Mailer: Windows Eudora Light Version 1.5.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: "Rokitansky, Carl-Herbert" <roki@cosy.sbg.ac.at>
From: "Richard J. Sexton  Ph.D. J.D." <rich@rd.vrx.net>
Subject: Re: Cluster Addressing and CIDR
Cc: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, "Bob Braden" <braden@ISI.EDU>,
        "Vaudreuil, Greg M (Greg)" <gregv@lucent.com>, <ietf@ietf.org>,
        <internet-history@postel.org>, <JimFleming@ameritech.net>,
        <steinle@smartvia.de>,
        "Elisabeth Porteneuve" <Elisabeth.Porteneuve@cetp.ipsl.fr>,
        <bortzmeyer@nic.fr>, "Vittorio Bertola" <vb@vitaminic.net>,
        <abel@able-towers.com>,
        "Joey Borda **star*walker**" <starwalker@gay.com>,
        <espresso@e-scape.net>, <jefsey@club-internet.fr>, <mgeist@uottawa.ca>,
        <harris@cabase.org.ar>, <Amadeu@nominalia.com>,
        <apisan@servidor.unam.mx>, <helmut.schink@icn.siemens.de>,
        <jcohen@shapirocohen.com>, <junsec@wide.ad.jp>,
        <censslin@ntia.doc.gov>, <chandley@ntia.doc.gov>, <DEvans@doc.gov>,
        <ellen@rony.com>, <eric@hi-tek.com>, <nvictory@ntia.doc.gov>,
        <rdesilva@ntia.doc.gov>, <RLayton@ntia.doc.gov>,
        "Ron Sherwood" <sherwood@islands.vi>,
        "Stephen Waters" <swaters@amicus.com>,
        "Stephane Bortzmeyer" <bortzmeyer@gitoyen.net>,
        "Simon Higgs" <simon@higgs.com>, <richard.hill@itu.int>,
        <raul@inia.org.uy>, <k@widgital.com>, "Jkhan" <Jkhan@MetroMgr.com>,
        "Ben Edelman" <edelman@law.harvard.edu>,
        "@quasar Internet Solutions, Inc." <shore@quasar.net>,
        <sotiris@hermesnetwork.com>,
        "Richard Henderson" <richardhenderson@ntlworld.com>,
        <micheal@beethoven.com>, <jwkckid1@ix.netcom.com>,
        <harivijapur@rediffmail.com>,
        "Bruce Young" <Bruce@barelyadequate.info>,
        "Alexander Svensson" <alexander@svensson.de>,
        "Joe Baptista" <baptista@dot-god.com>,
        "David Goldstein" <goldstein_david@yahoo.com.au>,
        <andy@navigator.co.nz>, <barrister@chambers.gen.nz>,
        <grant.forsyth@clear.co.nz>,
        "Joop Teernstra" <terastra@terabytz.co.nz>, <pdthrush@actrix.co.nz>,
        <KathrynKL@aol.com>, <yjpark@myepark.com>, <mouhamet@next.sn>,
        <saq66@umkc.edu>, <carl.rokitansky@sbg.ac.at>
Message-Id: <20030114042113.AD2A0D2A2@ns1.vrx.net>
Date: Mon, 13 Jan 2003 23:21:13 -0500 (EST)
Sender: owner-ietf@ietf.org
Precedence: bulk

How does this relate to Postels catanet work?



--

 /"\  ASCII RIBBON      / richard@vrx.net sexton@mejac.palo-alto.ca.us
 \ /  CAMPAIGN AGAINST / http://open-rsc.org http://cr.yp.to/dnsroot.html
  X   HTML MAIL       / NEW -->   http://watches.mbz.org     http://mbz.org
 / \  AND POSTINGS   / http://font.gallery http://dnso.com http://watch.prices


 






From owner-ietf@ietf.org  Tue Jan 14 12:42:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04372;
	Tue, 14 Jan 2003 12:42:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YV2e-0005tc-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 12:40:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YV1Y-0005pt-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 12:38:52 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04203
	for <ietf@ietf.org>; Tue, 14 Jan 2003 12:34:32 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id JAA06291
	for <ietf@ietf.org>; Tue, 14 Jan 2003 09:37:36 -0800
Date: Tue, 14 Jan 2003 09:34:40 -0800
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.62 Christmas Edition) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <149138450301.20030114093440@brandenburg.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: email and spam (was: Re: namedroppers, continued)
In-Reply-To: <58406748.1042476477@P2>
References: <200301132051.UAA03390@gra.isi.edu> <58406748.1042476477@P2>
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,

Monday, January 13, 2003, 1:47:57 PM, you wrote:
>>   *> > Could we not think of an FPS (frequently proposed
>> solutions)

John> Absolutely.  But such a hypothetical author would have to be
John> very motivated.

Would there be some benefit in taking the first step of simply listing FPSs,
without doing their detailed documentation?



d/
-- 
 Dave <mailto:dhc2@dcrocker.net>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 t +1.408.246.8253; f +1.408.850.1850




From owner-ietf@ietf.org  Tue Jan 14 14:57:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09553;
	Tue, 14 Jan 2003 14:57:10 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YX6N-0000gM-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 14:51:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YX6G-0000fj-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 14:51:52 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09193
	for <ietf@ietf.org>; Tue, 14 Jan 2003 14:47:30 -0500 (EST)
Received: from GK-VAIO.ninebynine.org (IDENT:root@localhost [127.0.0.1])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id LAA13395;
	Tue, 14 Jan 2003 11:50:29 -0800
Message-Id: <5.1.0.14.2.20030114181156.00a43c50@127.0.0.1>
X-Sender: gk-bulk@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 14 Jan 2003 18:14:13 +0000
To: Dave Crocker <dhc2@dcrocker.net>
From: Graham Klyne <GK@ninebynine.org>
Subject: Frequently proposed solutions (was: Re: email and spam ...)
Cc: "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <149138450301.20030114093440@brandenburg.com>
References: <58406748.1042476477@P2>
 <200301132051.UAA03390@gra.isi.edu>
 <58406748.1042476477@P2>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 09:34 AM 1/14/03 -0800, Dave Crocker wrote:
>Folks,
>
>Monday, January 13, 2003, 1:47:57 PM, you wrote:
> >>   *> > Could we not think of an FPS (frequently proposed
> >> solutions)
>
>John> Absolutely.  But such a hypothetical author would have to be
>John> very motivated.
>
>Would there be some benefit in taking the first step of simply listing FPSs,
>without doing their detailed documentation?

A small additional step might be FPS list + URL (of archived mailing list 
proposal).  The discussion thread should be easy enough to find from that.

Also, I've found that if a mailing list is archived with simple web access 
for each message, Google can be remarkably good at finding old messages.

#g


-------------------
Graham Klyne
<GK@NineByNine.org>




From owner-ietf@ietf.org  Tue Jan 14 16:11:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11907;
	Tue, 14 Jan 2003 16:11:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YYG0-0005pD-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 16:06:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YYFu-0005oO-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 16:05:54 -0500
Received: from darkwing.uoregon.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11526
	for <ietf@ietf.org>; Tue, 14 Jan 2003 16:01:31 -0500 (EST)
Received: from twin.uoregon.edu (twin.uoregon.edu [128.223.214.27])
	by darkwing.uoregon.edu (8.12.7/8.12.7) with ESMTP id h0EL4AE9021385
	for <ietf@ietf.org>; Tue, 14 Jan 2003 13:04:31 -0800 (PST)
Date: Tue, 14 Jan 2003 13:04:05 -0800 (PST)
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
X-X-Sender: joelja@twin.uoregon.edu
To: ietf@ietf.org
Subject: ietf55 videos available.
Message-ID: <Pine.LNX.4.44.0301141301390.9676-100000@twin.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

we completed the webpage to other dy so all the files are now available 
with titles.

http://videolab.uoregon.edu/events/ietf/ietf55.html#archive

-- 
-------------------------------------------------------------------------- 
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  Tue Jan 14 16:11:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11929;
	Tue, 14 Jan 2003 16:11:34 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YYFz-0005p7-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 16:05:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YYFq-0005oM-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 16:05:50 -0500
Received: from e35.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11522
	for <ietf@ietf.org>; Tue, 14 Jan 2003 16:01:26 -0500 (EST)
Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.194.24])
	by e35.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id h0EL4keP106190;
	Tue, 14 Jan 2003 16:04:46 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.12.14])
	by westrelay03.boulder.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id h0EL3TsK111014;
	Tue, 14 Jan 2003 14:03:29 -0700
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id h0EL2oV30388;
	Tue, 14 Jan 2003 16:02:50 -0500
Message-Id: <200301142102.h0EL2oV30388@rotala.raleigh.ibm.com>
To: "D. J. Bernstein" <djb@cr.yp.to>, ietf@ietf.org, iesg@ietf.org,
        namedroppers <namedroppers@ops.ietf.org>
Subject: Re: Dan Bernstein's issues about namedroppers list operation 
In-Reply-To: Message from narten@us.ibm.com
   of "Fri, 10 Jan 2003 11:24:52 EST." <200301101624.h0AGOqL09468@rotala.raleigh.ibm.com> 
Date: Tue, 14 Jan 2003 16:02:50 -0500
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

To clarify a bit, based on followup mail.

AD hat was on in previous message, same here. I am not speaking for
the full IESG, however.

It was not my intent to imply that if messages did not get forwarded
to one list, but did on another, that this somehow was OK and couldn't
be censorship. It is not OK. The messages at issue should have made it
out onto namedroppers. 

Regarding namedroppers mail processing:

>     1) first run through spamassassin. Mail that is rejected here is not
>        archived, as the number of such messages is large. All mail sent to
>        mailing lists on the server hosting namedroppers is run though
>        spamassassin, so this is not a namedroppers-specific
>     procedure.

Strictly speaking, the above is not permitted by the published spam
filtering guidelines. The issue isn't the use of spamassassin in front
of the list, but post-processing of rejected messages. The current
guidelines call for a human to manually approve the improperly flagged
rejections. I have started a process to see what can be done to
address the problem of rejections from spamassassin not being reviewed
by a human when sent to namedroppers.

In the case at issue, however, I do not believe that the use of
spamassassin is the problem with the messages at issue.  The
explanation I find most likely is that the messages were deleted in
haste rather than forwarded as they should have been after having been
flagged as possible spam since they came from a non-subscriber.

Of course, it is also not possible to prove intention in this case.
Given that I have seen no compelling evidence that suggests a desire
or intent to censor anyone on the list, I chose not to read such an
intent in the cases at issue here. But of course, there is no way to
prove one way or the other.

Thomas



From owner-ietf@ietf.org  Tue Jan 14 16:26:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12293;
	Tue, 14 Jan 2003 16:26:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YYYV-0006o1-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 16:25:07 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YYXx-0006l9-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 16:24:33 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12191
	for <ietf@ietf.org>; Tue, 14 Jan 2003 16:20:12 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 9C00B61ECB; Tue, 14 Jan 2003 22:23:31 +0100 (CET)
Date: Tue, 14 Jan 2003 22:23:31 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Pekka Savola <pekkas@netcore.fi>, ietf@ietf.org
Subject: Re: IETF56: is Friday on the agenda?
Message-ID: <238480000.1042579411@askvoll.hjemme.alvestrand.no>
In-Reply-To: <Pine.LNX.4.44.0301140955320.22964-100000@netcore.fi>
References:  <Pine.LNX.4.44.0301140955320.22964-100000@netcore.fi>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, januar 14, 2003 09:59:24 +0200 Pekka Savola 
<pekkas@netcore.fi> wrote:

> Hello,
>
> When looking at IETF56 meeting dates, in particular I note that Friday is
> again included.
>
> A lot of people are probably interested in what its status is intended to
> be when considering flights, like:
>
>  1) use it fully
>  2) use it, only morning sessions
>  3) only use it if really necessary
>  4) will not use it
>  5) something else
>
> What's the intent (of course, the final could change..)?  My guess would
> be somewhere between 2)-3).

Use it, only morning sessions.

A bit fewer parallel sessions (4-5 rather than 7-8) than the rest of the 
week - another meeting is moving in.

                  Harald




From owner-ietf@ietf.org  Tue Jan 14 16:47:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12863;
	Tue, 14 Jan 2003 16:47:15 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YYsq-0007WL-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 16:46:08 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YYsg-0007VB-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 16:45:58 -0500
Received: from e34.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12596
	for <ietf@ietf.org>; Tue, 14 Jan 2003 16:41:36 -0500 (EST)
Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.194.24])
	by e34.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id h0ELih99025302;
	Tue, 14 Jan 2003 16:44:43 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.12.14])
	by westrelay03.boulder.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id h0ELigsK103400;
	Tue, 14 Jan 2003 14:44:42 -0700
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id h0ELi3O30583;
	Tue, 14 Jan 2003 16:44:03 -0500
Message-Id: <200301142144.h0ELi3O30583@rotala.raleigh.ibm.com>
To: Aaron Swartz <me@aaronsw.com>
cc: namedroppers <namedroppers@ops.ietf.org>, iesg@ietf.org, ietf@ietf.org,
        "D. J. Bernstein" <djb@cr.yp.to>
Subject: Re: Dan Bernstein's issues about namedroppers list operation 
In-Reply-To: Message from me@aaronsw.com
   of "Fri, 10 Jan 2003 12:29:32 CST." <7661B517-24C9-11D7-9721-0003936780B2@aaronsw.com> 
Date: Tue, 14 Jan 2003 16:44:03 -0500
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

Aaron Swartz <me@aaronsw.com> writes:

> 4) Any held message that is later approved for distribution on the
>     mailing list should appear on the list as a normal posting (e.g.,
>     with the proper sender in the From address, etc.).
> """

> Later, however, you write:
> >>       [...] However, in
> >>       the second message, he manually inserted my subscription  
> >> address,
> >>       despite my previous comments about private subscription  
> >> addresses
> >>       and forged unsubscription requests. (Was this malicious, or was  
> >> it
> >>       just mind-bogglingly stupid?)
> >
> > Or perhaps, it was to make it clear to the poster which address the
> > posting was coming from, since there seems to be confusion at times
> > about whether someone is posting from the same address to which they
> > are subscribed.

> Including someone's private subscription address is not done for a  
> normal posting. Doing it for a held message is a violation of the rule  
> above, no?

My recollection of the intent of the spam guidelines cited is two
things:

1) it wasn't good enough to just resend the message to the list such
   that the message now appeared to have come from the person who
   forwarded it. This makes it hard to quote authors appropriately in
   followups, find specific messages (e.g., to search for the message
   by the original poster). That sort of thing.

2) It wasn't appropriate to edit the message in a way that might lead
   someone to claim that the message had been edited to alter its
   intent.

Namedropper's mail that is manually forwarded has (for as long as I
can remember) included a line indicating it has been forwarded. The
current message (which was improved as a result of the recent
attention) is:

[ post by non-subscriber.  with the massive amount of spam, it is easy to miss
  and therefore delete posts by non-subscribers.  if you wish to regularly
  post from an address that is not subscribed to this mailing list, send a
  message to <listname>-owner@ops.ietf.org and ask to have the alternate
  address added to the list of addresses from which submissions are
  automatically accepted. ]

This seems like a reasonable thing to add to such messages. I would
not want the guidelines cited to mean this is not permissable or that
no other modification was permissible (e.g., adding a header line).

One can debate whether including the specific information cited above
was the right thing to do, but I don't see it as breach of the
guidelines.

Thomas



From owner-ietf@ietf.org  Tue Jan 14 18:07:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15290;
	Tue, 14 Jan 2003 18:07:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Ya6C-0001Ys-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 18:04:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Ya4G-0001W8-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 18:02:00 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14876;
	Tue, 14 Jan 2003 17:57:31 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h0EN0pb08590;
	Tue, 14 Jan 2003 15:00:51 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id XAA04045;
	Tue, 14 Jan 2003 23:00:51 GMT
Date: Tue, 14 Jan 2003 23:00:51 GMT
Message-Id: <200301142300.XAA04045@gra.isi.edu>
To: iesg@ietf.org, kireeti@juniper.net
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

  *> 
  *> > The IESG has received a request to consider CR-LDP Extensions for ASON
  *> > <draft-aboulmagd-ccamp-crldp-ason-ext-02.txt> as an Informational RFC.
  *> > This has been reviewed in the IETF but is not the product of an IETF
  *> > Working Group.
  *> 
  *> I have two comments about this draft.
  *> 
  *> The first is that the draft calls for assignment of code points for
  *> some new messages, TLVs and status codes.  The draft, however, fails
  *> to say from which spaces these should come (e.g., that to be allocated
  *> by IETF Consensus, First Come First Served, Experimental).  If this is
  *> not specified, then I would suggest that code points from Experimental
  *> spaces be used.
  *> 


According to the IANA assignment rules for RSVP values, the only two
options are IETF consensus and FCFS.

  *> If code points are to be allocated from the space to be allocated by
  *> IETF Consensus, I strongly suggest that a *Standards Track* document be
  *> written, with more detail on the messages, especially their processing.

Indeed, that is what "IETF consensus" means, isn't it?

Bob Braden

  *> Also, more detail on what the goal is here, under what circumstances
  *> these messages need to be sent/replied to, etc.
  *> 
  *> Kireeti.
  *> 
  *> 



From owner-ietf@ietf.org  Tue Jan 14 19:47:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17580;
	Tue, 14 Jan 2003 19:47:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Ybd4-00057x-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 19:42:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Ybcl-00056b-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 19:41:43 -0500
Received: from merlot.juniper.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17365;
	Tue, 14 Jan 2003 19:37:18 -0500 (EST)
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 h0F0edS64452;
	Tue, 14 Jan 2003 16:40:39 -0800 (PST)
	(envelope-from kireeti@juniper.net)
Received: from localhost (kireeti@localhost)
	by kummer.juniper.net (8.11.6/8.9.3) with ESMTP id h0F0ed546836;
	Tue, 14 Jan 2003 16:40:39 -0800 (PST)
	(envelope-from kireeti@juniper.net)
X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs
Date: Tue, 14 Jan 2003 16:40:39 -0800 (PST)
From: Kireeti Kompella <kireeti@juniper.net>
To: Bob Braden <braden@ISI.EDU>
cc: <iesg@ietf.org>, <ietf@ietf.org>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
In-Reply-To: <200301142300.XAA04045@gra.isi.edu>
Message-ID: <20030114163836.T46812-100000@kummer.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Tue, 14 Jan 2003, Bob Braden wrote:

> According to the IANA assignment rules for RSVP values, the only two
> options are IETF consensus and FCFS.

The document in question is the *CR-LDP* Extensions.  I am (sadly)
aware of the RSVP assignment status.

>   *> If code points are to be allocated from the space to be allocated by
>   *> IETF Consensus, I strongly suggest that a *Standards Track* document be
>   *> written, with more detail on the messages, especially their processing.
>
> Indeed, that is what "IETF consensus" means, isn't it?

Is it?  That's good.  Currently, the document is Informational, and
is being processed as such.  Can this be changed?

Kireeti.




From owner-ietf@ietf.org  Tue Jan 14 21:23:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19274;
	Tue, 14 Jan 2003 21:23:09 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Yd8L-0008Ez-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 21:18:25 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Yd7t-0008Dq-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 21:17:57 -0500
Received: from relay-1v.club-internet.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19106
	for <ietf@ietf.org>; Tue, 14 Jan 2003 21:13:18 -0500 (EST)
Received: from mine.club-internet.fr (lns10v-12-135.w.club-internet.fr [213.44.239.135])
	by relay-1v.club-internet.fr (Postfix) with ESMTP
	id 42D451688; Wed, 15 Jan 2003 03:15:46 +0100 (CET)
Message-Id: <5.1.0.14.0.20030115023521.02c2ea00@mail.club-internet.fr>
X-Sender: jefsey@mail.club-internet.fr
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 15 Jan 2003 02:59:09 +0100
To: pouzin@email.enst.fr
From: "J-F C. (Jefsey)  Morfin" <jefsey@club-internet.fr>
Subject: Re: Cluster Addressing and CIDR
Cc: Jean-Louis.Grange@eurolinc.org, "vinton g. cerf" <vinton.g.cerf@wcom.com>,
        "Richard J. Sexton  Ph.D. J.D." <rich@rd.vrx.net>,
        "Rokitansky, Carl-Herbert" <roki@cosy.sbg.ac.at>,
        "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>,
        Bob Braden <braden@ISI.EDU>,
        "Vaudreuil, Greg M (Greg)" <gregv@lucent.com>, ietf@ietf.org,
        internet-history@postel.org, JimFleming@ameritech.net,
        steinle@smartvia.de,
        Elisabeth Porteneuve <Elisabeth.Porteneuve@cetp.ipsl.fr>,
        bortzmeyer@nic.fr, abel@able-towers.com, Simon Higgs <simon@higgs.com>,
        richard.hill@itu.int, k@widgital.com,
        Bruce Young <Bruce@barelyadequate.info>,
        Alexander Svensson <alexander@svensson.de>,
        Joe Baptista <baptista@dot-god.com>,
        David Goldstein <goldstein_david@yahoo.com.au>,
        Joop Teernstra <terastra@terabytz.co.nz>, yjpark@myepark.com
In-Reply-To: <5.1.1.6.2.20030114180456.023bbdd0@pop.wcomnet.com>
References: <20030114042113.AD2A0D2A2@ns1.vrx.net>
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-39295B27; boundary="=======16E22A0D======="
Sender: owner-ietf@ietf.org
Precedence: bulk

--=======16E22A0D=======
Content-Type: text/plain; x-avg-checked=avg-ok-39295B27; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit

Louis, some old pre-IETFquestions. What was "cata" standing for?

FYI this thread started asking to remember Carl-Herbert Rokitansky's 
Cluster Adressing Scheme. He then recalled that IETF had probably orignated 
in 1984 in UK. in a meeting he attented. jfc

PS. Vint, when was the name Internet used for the first time? When you say 
'multiple net systems' did  you refer by then to mutiple networks, to 
multiple technologies or both?

At 00:06 15/01/03, vinton g. cerf wrote:
>"catanet" was a term invented by Louis Pouzin, a French researcher 
>responsible for the design and construction of the Cyclades system that 
>included the Cigale pure datagram network. The term appeared in Internet 
>Experiment Note #48 but as I recall was not used thereafter, when the term 
>"Internet" became the preferred description name of the multiple network 
>system sponsored by ARPA.
>
>Vint
>
>At 11:21 PM 1/13/2003 -0500, Richard J. Sexton  Ph.D. J.D. wrote:
> >How does this relate to Postels catanet work?
>
>Vint Cerf
>SVP Architecture & Technology
>WorldCom
>22001 Loudoun County Parkway, F2-4115
>Ashburn, VA 20147
>703 886 1690 (v806 1690)
>703 886 0047 fax
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.427 / Virus Database: 240 - Release Date: 06/12/02

--=======16E22A0D=======--




From owner-ietf@ietf.org  Tue Jan 14 22:14:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20413;
	Tue, 14 Jan 2003 22:14:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YdzB-0004xY-00
	for ietf-list@ran.ietf.org; Tue, 14 Jan 2003 22:13:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YdyU-0004wI-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 22:12:18 -0500
Received: from merlot.juniper.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20277;
	Tue, 14 Jan 2003 22:07:50 -0500 (EST)
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 h0F3BCS74366;
	Tue, 14 Jan 2003 19:11:12 -0800 (PST)
	(envelope-from kireeti@juniper.net)
Received: from localhost (kireeti@localhost)
	by kummer.juniper.net (8.11.6/8.9.3) with ESMTP id h0F3BCQ47376;
	Tue, 14 Jan 2003 19:11:12 -0800 (PST)
	(envelope-from kireeti@juniper.net)
X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs
Date: Tue, 14 Jan 2003 19:11:12 -0800 (PST)
From: Kireeti Kompella <kireeti@juniper.net>
To: Bob Braden <braden@ISI.EDU>
cc: <iesg@ietf.org>, <ietf@ietf.org>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
In-Reply-To: <20030114163836.T46812-100000@kummer.juniper.net>
Message-ID: <20030114183719.I47224-100000@kummer.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 14 Jan 2003, Kireeti Kompella wrote:

> On Tue, 14 Jan 2003, Bob Braden wrote:

> > Indeed, that is what "IETF consensus" means, isn't it?

Having wisely been advised to reread RFC2434 for the definition of
'IETF Consensus', I did so:

"Specifically, new assignments are made via RFCs approved by the IESG."

The RFC doesn't have to be Standards Track; however, I assume that the
RFC needs IETF consensus for publication.

If the assignments requested are from the IETF Consensus space, I do
not consider the current document ready for publication.

If the assignments are from the vendor private or experimental space,
this document is not needed; indeed, as I understand RFC 3036, IANA
management of these spaces is not needed either.

Kireeti.




From owner-ietf@ietf.org  Wed Jan 15 02:49:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18984;
	Wed, 15 Jan 2003 02:49:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YiAY-0005DK-00
	for ietf-list@ran.ietf.org; Wed, 15 Jan 2003 02:41:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Yi9h-0005CQ-00
	for ietf@ran.ietf.org; Wed, 15 Jan 2003 02:40:09 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18731;
	Wed, 15 Jan 2003 02:35:39 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id E8A2A625BE; Wed, 15 Jan 2003 08:38:59 +0100 (CET)
Date: Wed, 15 Jan 2003 08:38:59 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Bob Braden <braden@ISI.EDU>, iesg@ietf.org, kireeti@juniper.net
Cc: ietf@ietf.org
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
Message-ID: <253710000.1042616339@askvoll.hjemme.alvestrand.no>
In-Reply-To: <200301142300.XAA04045@gra.isi.edu>
References:  <200301142300.XAA04045@gra.isi.edu>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, januar 14, 2003 23:00:51 +0000 Bob Braden <braden@ISI.EDU> 
wrote:

>   *> If code points are to be allocated from the space to be allocated by
>   *> IETF Consensus, I strongly suggest that a *Standards Track* document
> be   *> written, with more detail on the messages, especially their
> processing.
>
> Indeed, that is what "IETF consensus" means, isn't it?
>

Bob,
as I said when we discussed this a bit earlier:

RFC 2434 defines this term, and it says, in extenso:

      IETF Consensus - New values are assigned through the IETF
           consensus process. Specifically, new assignments are made via
           RFCs approved by the IESG. Typically, the IESG will seek
           input on prospective assignments from appropriate persons
           (e.g., a relevant Working Group if one exists).

           Examples: SMTP extensions [SMTP-EXT], BGP Subsequent Address
           Family Identifiers [BGP4-EXT].

Quoting from the references: [SMTP-EXT] is RFC 1869:

   The IANA maintains a registry of SMTP service extensions.  Associated
   with each such extension is a corresponding EHLO keyword value. Each
   service extension registered with the IANA must be defined in an RFC.
   Such RFCs must either be on the standards-track or must define an
   IESG-approved experimental protocol.

[BGP4-EXT] is RFC 2283:

   Subsequent Address Family Identifiers (other than those reserved for
   vendor specific use) are assigned only by the IETF consensus process
   and IESG approval.

There are circumstances (IS-IS standardization is one; experiments are 
another; other non-IETF-managed extensions are a third) where it makes 
sense to have non-standards-track documents allocate values in registries 
where the IETF intends to keep some kind of control.

The IESG has made some use of the Last Call mechanism for these documents; 
that seems to be one way to implement "the IESG will seek input".

RFC 2434 reserves the term "standards action" for the case where a 
standards-track RFC is required; there is a reason why it defines two 
terms, not one.

                         Harald





From owner-ietf@ietf.org  Wed Jan 15 03:19:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19612;
	Wed, 15 Jan 2003 03:19:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YiZk-00060J-00
	for ietf-list@ran.ietf.org; Wed, 15 Jan 2003 03:07:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YiZV-0005yy-00
	for ietf@ran.ietf.org; Wed, 15 Jan 2003 03:06:50 -0500
Received: from pmesmtp02.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19221
	for <ietf@ietf.org>; Wed, 15 Jan 2003 03:02:18 -0500 (EST)
Received: from dgismtp02.wcomnet.com ([166.38.58.142])
 by firewall.wcom.com (Iplanet MTA )
 with ESMTP id <0H8Q00A4BX47MD@firewall.wcom.com> for ietf@ietf.org; Wed,
 15 Jan 2003 08:04:55 +0000 (GMT)
Received: from dgismtp02.wcomnet.com by dgismtp02.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0H8Q00301X4695@dgismtp02.wcomnet.com>; Wed,
 15 Jan 2003 08:04:55 +0000 (GMT)
Received: from vint.wcom.com ([166.60.14.49])
 by dgismtp02.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0H8Q00228X3EVB@dgismtp02.wcomnet.com>; Wed,
 15 Jan 2003 08:04:54 +0000 (GMT)
Date: Wed, 15 Jan 2003 03:04:21 -0500
From: "vinton g. cerf" <vinton.g.cerf@wcom.com>
Subject: Re: Cluster Addressing and CIDR
In-reply-to: <5.1.0.14.0.20030115023521.02c2ea00@mail.club-internet.fr>
X-Sender: vcerf@pop.wcomnet.com
To: "J-F C. (Jefsey)  Morfin" <jefsey@club-internet.fr>, pouzin@email.enst.fr
Cc: Jean-Louis.Grange@eurolinc.org,
        "Richard J. Sexton  Ph.D. J.D." <rich@rd.vrx.net>,
        "Rokitansky, Carl-Herbert" <roki@cosy.sbg.ac.at>,
        "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>,
        Bob Braden <braden@ISI.EDU>,
        "Vaudreuil, Greg M (Greg)" <gregv@lucent.com>, ietf@ietf.org,
        internet-history@postel.org, JimFleming@ameritech.net,
        steinle@smartvia.de,
        Elisabeth Porteneuve <Elisabeth.Porteneuve@cetp.ipsl.fr>,
        bortzmeyer@nic.fr, abel@able-towers.com, Simon Higgs <simon@higgs.com>,
        richard.hill@itu.int, k@widgital.com,
        Bruce Young <Bruce@barelyadequate.info>,
        Alexander Svensson <alexander@svensson.de>,
        Joe Baptista <baptista@dot-god.com>,
        David Goldstein <goldstein_david@yahoo.com.au>,
        Joop Teernstra <terastra@terabytz.co.nz>, yjpark@myepark.com,
        rkahn@cnri.reston.va.us
Message-id: <5.1.1.6.2.20030115030238.01720260@pop.wcomnet.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Content-type: text/plain; charset=us-ascii
References: <5.1.1.6.2.20030114180456.023bbdd0@pop.wcomnet.com>
 <20030114042113.AD2A0D2A2@ns1.vrx.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

My first recollection of the documented use of the term "Internet" was in RFC 675 the specification of the Internet Transmission Control Protocol.

ARPA called the project "Internetting" starting in 1973, I believe.

Bob Kahn you know that point for sure.

vint

At 02:59 AM 1/15/2003 +0100, J-F C. (Jefsey)  Morfin wrote:
>PS. Vint, when was the name Internet used for the first time? When you say 'multiple net systems' did  you refer by then to mutiple networks, to multiple technologies or both?

Vint Cerf
SVP Architecture & Technology
WorldCom
22001 Loudoun County Parkway, F2-4115
Ashburn, VA 20147
703 886 1690 (v806 1690)
703 886 0047 fax




From owner-ietf@ietf.org  Wed Jan 15 12:07:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03458;
	Wed, 15 Jan 2003 12:07:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YqwN-0001zl-00
	for ietf-list@ran.ietf.org; Wed, 15 Jan 2003 12:02:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Yqvt-0001yg-00
	for ietf@ran.ietf.org; Wed, 15 Jan 2003 12:02:29 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03183;
	Wed, 15 Jan 2003 11:57:55 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h0FH1Eb05721;
	Wed, 15 Jan 2003 09:01:15 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id RAA04257;
	Wed, 15 Jan 2003 17:01:14 GMT
Date: Wed, 15 Jan 2003 17:01:14 GMT
Message-Id: <200301151701.RAA04257@gra.isi.edu>
To: braden@ISI.EDU, kireeti@juniper.net
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
Cc: iesg@ietf.org, ietf@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

  *> 
  *> >   *> If code points are to be allocated from the space to be allocated by
  *> >   *> IETF Consensus, I strongly suggest that a *Standards Track* document be
  *> >   *> written, with more detail on the messages, especially their processing.
  *> >
  *> > Indeed, that is what "IETF consensus" means, isn't it?
  *> 

Kireeti,

Following Randy Bush's suggestion, I did a "quick reread of RFC 2434",
and I realized that my comment above was incorrect. I had interpreted
"standards track" as meaning "by IETF process", but RFC 2434 does
distinguish standards track from IETF-approved Informational.  But then
I don't grok why it is particularly desirable to make the documentation
standards track, since in either case formal IETF action is involved.

Bob Braden

  *> Is it?  That's good.  Currently, the document is Informational, and
  *> is being processed as such.  Can this be changed?
  *> 
  *> Kireeti.
  *> 



From owner-ietf@ietf.org  Wed Jan 15 20:10:07 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16861;
	Wed, 15 Jan 2003 20:10:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YyOx-0007Cz-00
	for ietf-list@ran.ietf.org; Wed, 15 Jan 2003 20:00:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YyOF-0007Cd-00
	for ietf@ran.ietf.org; Wed, 15 Jan 2003 20:00:15 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA16537
	for <ietf@ietf.org>; Wed, 15 Jan 2003 19:55:35 -0500 (EST)
Received: (qmail 5504 invoked by uid 1016); 16 Jan 2003 00:59:20 -0000
Date: 16 Jan 2003 00:59:20 -0000
Message-ID: <20030116005920.5503.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: namedroppers@ops.ietf.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: Dan Bernstein's issues about namedroppers list operation
References: <7661B517-24C9-11D7-9721-0003936780B2@aaronsw.com> <200301142144.h0ELi3O30583@rotala.raleigh.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Thomas Narten writes:
> One can debate whether including the specific information cited above
> was the right thing to do

That's the paragraph Bush added to other people's messages.

Bush added a different paragraph to my messages. (The ones he didn't
throw away, that is.) In that paragraph, he specifically included my
private subscription address, which hadn't appeared anywhere in the
messages I actually sent.

Unintentional, eh?

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Wed Jan 15 21:23:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18221;
	Wed, 15 Jan 2003 21:23:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YzcR-0008B9-00
	for ietf-list@ran.ietf.org; Wed, 15 Jan 2003 21:18:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YzcL-0008Ag-00
	for ietf@ran.ietf.org; Wed, 15 Jan 2003 21:18:53 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18054
	for <ietf@ietf.org>; Wed, 15 Jan 2003 21:14:12 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id SAA24456;
	Wed, 15 Jan 2003 18:17:15 -0800
Date: Wed, 15 Jan 2003 18:17:24 -0800
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.62 Christmas Edition) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <6519918971.20030115181724@brandenburg.com>
To: John C Klensin <john+ietf@jck.com>
CC: Doug <Dougxx2@carolina.rr.com>, "ietf@ietf.org" <ietf@ietf.org>,
        Lloyd Wood <l.wood@eim.surrey.ac.uk>
Subject: Re: email and spam (was: Re: namedroppers, continued)
In-Reply-To: <33549559.1041963726@P2>
References: <009e01c2b67b$45926590$0701a8c0@nailed.org> <33549559.1041963726@P2>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

Before someone makes suggestions about the magic bullet that will solve
spam problems, they should at least familiarize themselves with the
rather interesting range of startup company approaches to handling the
problem.  Everything ranging from keyword filtering by a commercial
version of spamassassin, to patenting a haiku.

And they should become familiar with the public policy and politics
debates on the topic.

This is a multifaceted problem, including the minor fact that people's
definition of "spam" is highly variable.  At this stage it appears clear
that no single magic bullet is possible and that we should start viewing
spam the way we view roaches.  We don't like them.  They are bad.  We do
a range of things to get rid of them.  It all helps.  But we do not
eliminate them.  We simply reduce them to a tolerable level.

d/

Tuesday, January 7, 2003, 3:22:06 PM, you wrote:
John> Almost all of the measures you have suggested have serious
John> side-effects or critical prerequisites.  In the last analysis,
John> most of us would rather put up with a little spam than pay the
John> prices involved.  Others are sufficiently fed up with spam that
John> they are willing to consider some very radical changes to how we
John> use email.  But, regardless of how that comes out, the decisions
John> have been fairly explicit: people have thought of your
John> suggestions, and others, and their impact, and have made fairly
John> explicit decisions about preferences.  My comment about X.400 of
John> a few weeks ago was intended to address those issues, but
John> apparently made a reference too far in the past, or too subtle,
John> for some of the people who have been participating in the
John> discussion.


d/
-- 
 Dave <mailto:dhc2@dcrocker.net>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 t +1.408.246.8253; f +1.408.850.1850




From owner-ietf@ietf.org  Thu Jan 16 01:33:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22782;
	Thu, 16 Jan 2003 01:33:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Z3VP-0000u7-00
	for ietf-list@ran.ietf.org; Thu, 16 Jan 2003 01:27:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Z3Ur-0000tj-00
	for ietf@ran.ietf.org; Thu, 16 Jan 2003 01:27:25 -0500
Received: from rwcrmhc51.attbi.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22579;
	Thu, 16 Jan 2003 01:22:42 -0500 (EST)
Received: from billsbox (12-211-30-155.client.attbi.com[12.211.30.155])
          by rwcrmhc51.attbi.com (rwcrmhc51) with SMTP
          id <2003011606260305100pllg0e>; Thu, 16 Jan 2003 06:26:03 +0000
Reply-To: <bill@strahm.net>
From: "Bill Strahm" <bill@strahm.net>
To: "'D. J. Bernstein'" <djb@cr.yp.to>, <namedroppers@ops.ietf.org>,
        <iesg@ietf.org>, <ietf@ietf.org>
Subject: RE: Dan Bernstein's issues about namedroppers list operation
Date: Wed, 15 Jan 2003 22:25:56 -0800
Message-ID: <000001c2bd28$20c5ca50$6501a8c0@billsbox>
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
Importance: Normal
In-Reply-To: <20030116005920.5503.qmail@cr.yp.to>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of D.
J. Bernstein
Sent: Wednesday, January 15, 2003 4:59 PM
To: namedroppers@ops.ietf.org; iesg@ietf.org; ietf@ietf.org
Subject: Re: Dan Bernstein's issues about namedroppers list operation


Thomas Narten writes:
> One can debate whether including the specific information cited above 
> was the right thing to do

That's the paragraph Bush added to other people's messages.

Bush added a different paragraph to my messages. (The ones he didn't
throw away, that is.) In that paragraph, he specifically included my
private subscription address, which hadn't appeared anywhere in the
messages I actually sent.

Unintentional, eh?

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago




From owner-ietf@ietf.org  Thu Jan 16 09:03:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11229;
	Thu, 16 Jan 2003 09:03:22 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZAYz-0004RZ-00
	for ietf-list@ran.ietf.org; Thu, 16 Jan 2003 09:00:09 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ZABY-0006iq-00
	for ietf@ran.ietf.org; Thu, 16 Jan 2003 08:35:56 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10152
	for <ietf@ietf.org>; Thu, 16 Jan 2003 08:31:09 -0500 (EST)
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18ZA9w-000Iet-00; Thu, 16 Jan 2003 08:34:16 -0500
Date: Thu, 16 Jan 2003 08:34:16 -0500
From: John C Klensin <klensin@jck.com>
To: Dave Crocker <dhc2@dcrocker.net>
cc: Doug <Dougxx2@carolina.rr.com>, "ietf@ietf.org" <ietf@ietf.org>,
        Lloyd Wood <l.wood@eim.surrey.ac.uk>
Subject: Re: email and spam (was: Re: namedroppers, continued)
Message-ID: <288018394.1042706056@P2>
In-Reply-To: <6519918971.20030115181724@brandenburg.com>
References: <009e01c2b67b$45926590$0701a8c0@nailed.org>
 <33549559.1041963726@P2>
 <6519918971.20030115181724@brandenburg.com>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Wednesday, 15 January, 2003 18:17 -0800 Dave Crocker
<dhc2@dcrocker.net> wrote:

> John,
> 
> Before someone makes suggestions about the magic bullet that
> will solve spam problems, they should at least familiarize
> themselves with the rather interesting range of startup
> company approaches to handling the problem.  Everything
> ranging from keyword filtering by a commercial version of
> spamassassin, to patenting a haiku.
> 
> And they should become familiar with the public policy and
> politics debates on the topic.
> 
> This is a multifaceted problem, including the minor fact that
> people's definition of "spam" is highly variable.  At this
> stage it appears clear that no single magic bullet is possible
> and that we should start viewing spam the way we view roaches.
> We don't like them.  They are bad.  We do a range of things to
> get rid of them.  It all helps.  But we do not eliminate them.
> We simply reduce them to a tolerable level.

Is there some part of this with which you assume I disagree?

     john






From owner-ietf@ietf.org  Thu Jan 16 12:04:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16262;
	Thu, 16 Jan 2003 12:04:48 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZDPM-0003Qd-00
	for ietf-list@ran.ietf.org; Thu, 16 Jan 2003 12:02:24 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YZIq-0000br-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 17:13:00 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13492;
	Tue, 14 Jan 2003 17:08:37 -0500 (EST)
Received: from news.av8.net (news.av8.net [198.3.136.138])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA23872;
	Tue, 14 Jan 2003 17:08:38 -0500
Date: Tue, 14 Jan 2003 17:09:16 -0500 (EST)
From: Dean Anderson <dean@av8.net>
To: Thomas Narten <narten@us.ibm.com>
cc: "D. J. Bernstein" <djb@cr.yp.to>, <ietf@ietf.org>, <iesg@ietf.org>,
        namedroppers <namedroppers@ops.ietf.org>
Subject: Re: Dan Bernstein's issues about namedroppers list operation 
In-Reply-To: <200301142102.h0EL2oV30388@rotala.raleigh.ibm.com>
Message-ID: <Pine.LNX.4.33.0301141705070.23170-100000@news.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Perhaps it would be helpful to consider that other lists have multiple
persons who can handle such processing, and that all of those persons get
the flagged message. Anyone in the administrative group can approve the
message. An audit trail might be helpful, in this case. Such an audit
trail would have to be read-only to the persons doing the administration,
as well as readable to the public, who might wish to see that the
administrators are properly handling messages.

		--Dean

On Tue, 14 Jan 2003, Thomas Narten wrote:

> To clarify a bit, based on followup mail.
>
> AD hat was on in previous message, same here. I am not speaking for
> the full IESG, however.
>
> It was not my intent to imply that if messages did not get forwarded
> to one list, but did on another, that this somehow was OK and couldn't
> be censorship. It is not OK. The messages at issue should have made it
> out onto namedroppers.
>
> Regarding namedroppers mail processing:
>
> >     1) first run through spamassassin. Mail that is rejected here is not
> >        archived, as the number of such messages is large. All mail sent to
> >        mailing lists on the server hosting namedroppers is run though
> >        spamassassin, so this is not a namedroppers-specific
> >     procedure.
>
> Strictly speaking, the above is not permitted by the published spam
> filtering guidelines. The issue isn't the use of spamassassin in front
> of the list, but post-processing of rejected messages. The current
> guidelines call for a human to manually approve the improperly flagged
> rejections. I have started a process to see what can be done to
> address the problem of rejections from spamassassin not being reviewed
> by a human when sent to namedroppers.
>
> In the case at issue, however, I do not believe that the use of
> spamassassin is the problem with the messages at issue.  The
> explanation I find most likely is that the messages were deleted in
> haste rather than forwarded as they should have been after having been
> flagged as possible spam since they came from a non-subscriber.
>
> Of course, it is also not possible to prove intention in this case.
> Given that I have seen no compelling evidence that suggests a desire
> or intent to censor anyone on the list, I chose not to read such an
> intent in the cases at issue here. But of course, there is no way to
> prove one way or the other.
>
> Thomas
>
> --
> to unsubscribe send a message to namedroppers-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/namedroppers/>
>






From owner-ietf@ietf.org  Thu Jan 16 12:04:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16265;
	Thu, 16 Jan 2003 12:04:48 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZDPw-0003bZ-00
	for ietf-list@ran.ietf.org; Thu, 16 Jan 2003 12:03:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YaEl-00020o-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 18:12:52 -0500
Received: from pmesmtp01.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15358
	for <ietf@ietf.org>; Tue, 14 Jan 2003 18:08:18 -0500 (EST)
Received: from dgismtp03.wcomnet.com ([166.38.58.143])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0H8Q009268AGOR@firewall.wcom.com> for ietf@ietf.org; Tue,
 14 Jan 2003 23:08:41 +0000 (GMT)
Received: from dgismtp03.wcomnet.com by dgismtp03.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0H8Q0080189WHZ@dgismtp03.wcomnet.com>; Tue,
 14 Jan 2003 23:08:40 +0000 (GMT)
Received: from vint.wcom.com ([166.60.14.60])
 by dgismtp03.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0H8Q007FY890RO@dgismtp03.wcomnet.com>; Tue,
 14 Jan 2003 23:08:32 +0000 (GMT)
Date: Tue, 14 Jan 2003 18:06:58 -0500
From: "vinton g. cerf" <vinton.g.cerf@wcom.com>
Subject: Re: Cluster Addressing and CIDR
In-reply-to: <20030114042113.AD2A0D2A2@ns1.vrx.net>
X-Sender: vcerf@pop.wcomnet.com
To: "Richard J. Sexton  Ph.D. J.D." <rich@rd.vrx.net>,
        "Rokitansky, Carl-Herbert" <roki@cosy.sbg.ac.at>
Cc: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, Bob Braden <braden@ISI.EDU>,
        "Vaudreuil, Greg M (Greg)" <gregv@lucent.com>, ietf@ietf.org,
        internet-history@postel.org, JimFleming@ameritech.net,
        steinle@smartvia.de,
        Elisabeth Porteneuve <Elisabeth.Porteneuve@cetp.ipsl.fr>,
        bortzmeyer@nic.fr, Vittorio Bertola <vb@vitaminic.net>,
        abel@able-towers.com, Joey Borda **star*walker** <starwalker@gay.com>,
        espresso@e-scape.net, jefsey@club-internet.fr, mgeist@uottawa.ca,
        harris@cabase.org.ar, Amadeu@nominalia.com, apisan@servidor.unam.mx,
        helmut.schink@icn.siemens.de, jcohen@shapirocohen.com,
        junsec@wide.ad.jp, censslin@ntia.doc.gov, chandley@ntia.doc.gov,
        DEvans@doc.gov, ellen@rony.com, eric@hi-tek.com, nvictory@ntia.doc.gov,
        rdesilva@ntia.doc.gov, RLayton@ntia.doc.gov,
        Ron Sherwood <sherwood@islands.vi>,
        Stephen Waters <swaters@amicus.com>,
        Stephane Bortzmeyer <bortzmeyer@gitoyen.net>,
        Simon Higgs <simon@higgs.com>, richard.hill@itu.int, raul@inia.org.uy,
        k@widgital.com, Jkhan <Jkhan@MetroMgr.com>,
        Ben Edelman <edelman@law.harvard.edu>,
        "@quasar Internet Solutions, Inc." <shore@quasar.net>,
        sotiris@hermesnetwork.com,
        Richard Henderson <richardhenderson@ntlworld.com>,
        micheal@beethoven.com, jwkckid1@ix.netcom.com,
        harivijapur@rediffmail.com, Bruce Young <Bruce@barelyadequate.info>,
        Alexander Svensson <alexander@svensson.de>,
        Joe Baptista <baptista@dot-god.com>,
        David Goldstein <goldstein_david@yahoo.com.au>, andy@navigator.co.nz,
        barrister@chambers.gen.nz, grant.forsyth@clear.co.nz,
        Joop Teernstra <terastra@terabytz.co.nz>, pdthrush@actrix.co.nz,
        KathrynKL@aol.com, yjpark@myepark.com, mouhamet@next.sn,
        saq66@umkc.edu, carl.rokitansky@sbg.ac.at
Message-id: <5.1.1.6.2.20030114180456.023bbdd0@pop.wcomnet.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Content-type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

"catanet" was a term invented by Louis Pouzin, a French researcher responsible for the design and construction of the Cyclades system that included the Cigale pure datagram network. The term appeared in Internet Experiment Note #48 but as I recall was not used thereafter, when the term "Internet" became the preferred descriptive name of the multiple network system sponsored by ARPA.

Vint

At 11:21 PM 1/13/2003 -0500, Richard J. Sexton  Ph.D. J.D. wrote:
>How does this relate to Postels catanet work?

Vint Cerf
SVP Architecture & Technology
WorldCom
22001 Loudoun County Parkway, F2-4115
Ashburn, VA 20147
703 886 1690 (v806 1690)
703 886 0047 fax






From owner-ietf@ietf.org  Thu Jan 16 13:28:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19328;
	Thu, 16 Jan 2003 13:28:29 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZEjF-0000xZ-00
	for ietf-list@ran.ietf.org; Thu, 16 Jan 2003 13:27:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YeZ0-0007NC-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 22:50:02 -0500
Received: from smtp2.enst.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21504
	for <ietf@ietf.org>; Tue, 14 Jan 2003 22:45:35 -0500 (EST)
Received: from ares.enst.fr (ares.enst.fr [137.194.34.9])
	by smtp2.enst.fr (Postfix) with ESMTP
	id 15BBC53AB6; Wed, 15 Jan 2003 04:48:34 +0100 (CET)
Received: from ares.enst.fr (localhost [IPv6:::1])
	by ares.enst.fr (8.12.2+Sun/8.12.2) with ESMTP id h0F3mRK5008535;
	Wed, 15 Jan 2003 04:48:27 +0100 (MET)
Received: (from pouzin@localhost)
	by ares.enst.fr (8.12.2+Sun/8.12.2/Submit) id h0F3mJ6v008534;
	Wed, 15 Jan 2003 04:48:19 +0100 (MET)
Date: Wed, 15 Jan 2003 04:48:19 +0100 (MET)
Message-Id: <200301150348.h0F3mJ6v008534@ares.enst.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
From: Louis Pouzin <pouzin@email.enst.fr>
To: "J-F C. (Jefsey) Morfin" <jefsey@club-internet.fr>
Cc: Jean-Louis.Grange@eurolinc.org, "vinton g. cerf" <vinton.g.cerf@wcom.com>,
        "Richard J. Sexton  Ph.D. J.D." <rich@rd.vrx.net>,
        "Rokitansky, Carl-Herbert" <roki@cosy.sbg.ac.at>,
        "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>,
        Bob Braden <braden@ISI.EDU>,
        "Vaudreuil, Greg M (Greg)" <gregv@lucent.com>, ietf@ietf.org,
        internet-history@postel.org, JimFleming@ameritech.net,
        steinle@smartvia.de,
        Elisabeth Porteneuve <Elisabeth.Porteneuve@cetp.ipsl.fr>,
        bortzmeyer@nic.fr, abel@able-towers.com, Simon Higgs <simon@higgs.com>,
        richard.hill@itu.int, k@widgital.com,
        Bruce Young <Bruce@barelyadequate.info>,
        Alexander Svensson <alexander@svensson.de>,
        Joe Baptista <baptista@dot-god.com>,
        David Goldstein <goldstein_david@yahoo.com.au>,
        Joop Teernstra <terastra@terabytz.co.nz>, yjpark@myepark.com
Subject: re: Cluster Addressing and CIDR
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA19328

On Wed, 15 Jan 2003 02:59:09 +0100, J-F C. (Jefsey) Morfin wrote:

>Louis, some old pre-IETFquestions. What was "cata" standing for?

It's mispelled. The word is "catenet". Obvious origin: latin catena -> chain; french: caténaire; english: catena, catenation.

Cheers





From owner-ietf@ietf.org  Thu Jan 16 13:28:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19358;
	Thu, 16 Jan 2003 13:28:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZEjE-0000xB-00
	for ietf-list@ran.ietf.org; Thu, 16 Jan 2003 13:27:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YdyP-0004wG-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 22:12:13 -0500
Received: from bluejay.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20273
	for <ietf@ietf.org>; Tue, 14 Jan 2003 22:07:36 -0500 (EST)
Received: from pcp802197pcs.nrockv01.md.comcast.net ([68.48.86.43] helo=STJOHNS-LAPTOP.mindspring.com)
	by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:DES-CBC3-SHA:168)
	(Exim 3.33 #1)
	id 18Ydx4-0007Gt-00; Tue, 14 Jan 2003 19:10:50 -0800
Message-Id: <5.1.0.14.2.20030114215708.0475ef68@pop.mindspring.com>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 14 Jan 2003 22:08:32 -0500
To: "Rokitansky, Carl-Herbert" <roki@cosy.sbg.ac.at>,
        "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>,
        "Bob Braden" <braden@ISI.EDU>,
        "Vaudreuil, Greg M (Greg)" <gregv@lucent.com>, <ietf@ietf.org>,
        <internet-history@postel.org>, <JimFleming@ameritech.net>,
        <steinle@smartvia.de>,
        "Elisabeth Porteneuve" <Elisabeth.Porteneuve@cetp.ipsl.fr>,
        <bortzmeyer@nic.fr>, "Vittorio Bertola" <vb@vitaminic.net>,
        <abel@able-towers.com>,
        "Joey Borda **star*walker**" <starwalker@gay.com>,
        <espresso@e-scape.net>, <jefsey@club-internet.fr>, <mgeist@uottawa.ca>,
        <harris@cabase.org.ar>, <Amadeu@nominalia.com>,
        <apisan@servidor.unam.mx>, <helmut.schink@icn.siemens.de>,
        <jcohen@shapirocohen.com>, <junsec@wide.ad.jp>,
        <censslin@ntia.doc.gov>, <chandley@ntia.doc.gov>, <DEvans@doc.gov>,
        <ellen@rony.com>, <eric@hi-tek.com>, <nvictory@ntia.doc.gov>,
        <rdesilva@ntia.doc.gov>, <RLayton@ntia.doc.gov>,
        "Ron Sherwood" <sherwood@islands.vi>,
        "Stephen Waters" <swaters@amicus.com>,
        "Stephane Bortzmeyer" <bortzmeyer@gitoyen.net>,
        "Simon Higgs" <simon@higgs.com>, <richard.hill@itu.int>,
        "Richard J. Sexton" <richard@vrx.net>, <raul@inia.org.uy>,
        <k@widgital.com>, "Jkhan" <Jkhan@MetroMgr.com>,
        "Ben Edelman" <edelman@law.harvard.edu>,
        "@quasar Internet Solutions, Inc." <shore@quasar.net>
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: Cluster Addressing and CIDR
Cc: <sotiris@hermesnetwork.com>,
        "Richard Henderson" <richardhenderson@ntlworld.com>,
        <micheal@beethoven.com>, <jwkckid1@ix.netcom.com>,
        <harivijapur@rediffmail.com>,
        "Bruce Young" <Bruce@barelyadequate.info>,
        "Alexander Svensson" <alexander@svensson.de>,
        "Joe Baptista" <baptista@dot-god.com>,
        "David Goldstein" <goldstein_david@yahoo.com.au>,
        <andy@navigator.co.nz>, <barrister@chambers.gen.nz>,
        <grant.forsyth@clear.co.nz>,
        "Joop Teernstra" <terastra@terabytz.co.nz>, <pdthrush@actrix.co.nz>,
        <KathrynKL@aol.com>, <yjpark@myepark.com>, <mouhamet@next.sn>,
        <saq66@umkc.edu>, <carl.rokitansky@sbg.ac.at>
In-Reply-To: <5.0.2.1.2.20030114011804.02eccd60@mail.cosy.sbg.ac.at>
References: <200301131548.h0DFmumg011846@ginger.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-ELNK-Trace: 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4d1c79782c846520c302839a620d3fe1a0350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
Sender: owner-ietf@ietf.org
Precedence: bulk

At 01:21 AM 1/14/2003 +0100, Rokitansky, Carl-Herbert wrote:
>PS: As far as I can recall (having currently no access to any old 
>documents) the IETF (or plans for it ?) was established in 1984 in a 
>meeting in Malvern, UK at RSRE, in Sept (?) 1984 (could anyone please 
>confirm), in which several of us participated ! Do you have any plans 
>already to celebrate the 20th anniversary of the establishment of the IETF 
>! Please keep me informed. Thanks ! Roki.
>==================================================================

Hi Roki -

Sorry - wrong date.  The IETF was established as the result of an IAB 
meeting held just immediately before the 1st IETF meeting - which 
incidentally was actually the last GADS (Gateway Architecture and Data 
Structures) meeting.  Mike Corrigan (my boss and the Technical Manager for 
the Defense Data Network) came in late in the day on the first day of the 
meeting and informed us the IAB had decided to split GADS into the INENG 
and the INARC (Internet Engineering and Internet Architecture) and that the 
GADS chair (Dave Mills) was now the chair of INARC.  Mike Corrigan took 
over as the first chair of the INENG which pretty immediately became the 
IETF (it was easier on the tongue).

We spent about 1/2 of the 2nd day on engineering issues and I would really 
call that specific day the first IETF meeting.  According to the IETF 
website, that was January 17th, 1986 - so we've got a few years yet until 
the 20th anniversary.

Later, Mike






From owner-ietf@ietf.org  Thu Jan 16 13:29:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19408;
	Thu, 16 Jan 2003 13:29:04 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZEn6-00014b-00
	for ietf-list@ran.ietf.org; Thu, 16 Jan 2003 13:31:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YekM-0007ai-00
	for ietf@ran.ietf.org; Tue, 14 Jan 2003 23:01:46 -0500
Received: from mailhost.chi1.ameritech.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21647
	for <ietf@ietf.org>; Tue, 14 Jan 2003 22:57:19 -0500 (EST)
Received: from repligate ([67.36.182.220]) by mailhost.chi1.ameritech.net
          (InterMail vM.4.01.02.17 201-229-119) with SMTP
          id <20030115040039.JOSL17930.mailhost.chi1.ameritech.net@repligate>;
          Tue, 14 Jan 2003 22:00:39 -0600
Message-ID: <088801c2bc4a$b266ab70$8500a8c0@repligate>
Reply-To: "Techno.C@T" <Techno.C@T.vrx.net>
From: "Techno.C@T" <JimFleming@ameritech.net>
To: "Louis Pouzin" <pouzin@email.enst.fr>,
        "J-F C. \(Jefsey\) Morfin" <jefsey@club-internet.fr>
Cc: <Jean-Louis.Grange@eurolinc.org>,
        "vinton g. cerf" <vinton.g.cerf@wcom.com>,
        "Richard J. Sexton  Ph.D. J.D." <rich@rd.vrx.net>,
        "Rokitansky, Carl-Herbert" <roki@cosy.sbg.ac.at>,
        "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>,
        "Bob Braden" <braden@ISI.EDU>,
        "Vaudreuil, Greg M \(Greg\)" <gregv@lucent.com>, <ietf@ietf.org>,
        <internet-history@postel.org>, <steinle@smartvia.de>,
        "Elisabeth Porteneuve" <Elisabeth.Porteneuve@cetp.ipsl.fr>,
        <bortzmeyer@nic.fr>, <abel@able-towers.com>,
        "Simon Higgs" <simon@higgs.com>, <richard.hill@itu.int>,
        <k@widgital.com>, "Bruce Young" <Bruce@barelyadequate.info>,
        "Alexander Svensson" <alexander@svensson.de>,
        "Joe Baptista" <baptista@dot-god.com>,
        "David Goldstein" <goldstein_david@yahoo.com.au>,
        "Joop Teernstra" <terastra@terabytz.co.nz>, <yjpark@myepark.com>
References: <200301150348.h0F3mJ6v008534@ares.enst.fr>
Subject: Re: Cluster Addressing and CIDR
Date: Tue, 14 Jan 2003 22:00:50 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id WAA21648
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA19408

----- Original Message -----
From: "Louis Pouzin" <pouzin@email.enst.fr>
Sent: Tuesday, January 14, 2003 9:48 PM
Subject: re: Cluster Addressing and CIDR


On Wed, 15 Jan 2003 02:59:09 +0100, J-F C. (Jefsey) Morfin wrote:

>Louis, some old pre-IETFquestions. What was "cata" standing for?

It's mispelled. The word is "catenet". Obvious origin: latin catena -> chain; french: caténaire; english: catena, catenation.
=====

Thanks for the name...we partly named a programming language after it....C@T

http://www.ddj.com/articles/1993/9310/
http://www.computer.org/software/so1991/s3073abs.htm

C@T is also aka CALICO as in a C@T of Many Colors...
...and also C+@ because of the addition of the @ operator from Smalltalk to C...

Someday I may tell people the whole story behind it...
...but, 8 years of work resulted in Sun "studying it" and announcing Java...
...and now we have Microsoft with C#...
...instead of Go-Mono....maybe it should be Go Figure...
http://www.go-mono.com






From owner-ietf@ietf.org  Thu Jan 16 13:33:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19676;
	Thu, 16 Jan 2003 13:33:41 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZEr7-0001vc-00
	for ietf-list@ran.ietf.org; Thu, 16 Jan 2003 13:35:09 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YzSC-00084i-00
	for ietf@ran.ietf.org; Wed, 15 Jan 2003 21:08:25 -0500
Received: from aland.bbn.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17916
	for <ietf@ietf.org>; Wed, 15 Jan 2003 21:03:32 -0500 (EST)
Received: from aland.bbn.com (localhost [127.0.0.1])
	by aland.bbn.com (8.12.5/8.11.6) with ESMTP id h0G21c7f044136;
	Wed, 15 Jan 2003 21:01:38 -0500 (EST)
	(envelope-from craig@aland.bbn.com)
Message-Id: <200301160201.h0G21c7f044136@aland.bbn.com>
To: Michael StJohns <mstjohns@mindspring.com>
cc: "Rokitansky, Carl-Herbert" <roki@cosy.sbg.ac.at>,
        "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>,
        "Bob Braden" <braden@ISI.EDU>,
        "Vaudreuil,
    Greg M (Greg)" <gregv@lucent.com>, ietf@ietf.org,
        internet-history@postel.org, JimFleming@ameritech.net,
        steinle@smartvia.de,
        "Elisabeth Porteneuve" <Elisabeth.Porteneuve@cetp.ipsl.fr>,
        bortzmeyer@nic.fr, "Vittorio Bertola" <vb@vitaminic.net>,
        abel@able-towers.com,
        "Joey Borda **star*walker**" <starwalker@gay.com>,
        espresso@e-scape.net, jefsey@club-internet.fr, mgeist@uottawa.ca,
        harris@cabase.org.ar, Amadeu@nominalia.com, apisan@servidor.unam.mx,
        helmut.schink@icn.siemens.de, jcohen@shapirocohen.com,
        junsec@wide.ad.jp, censslin@ntia.doc.gov, chandley@ntia.doc.gov,
        DEvans@doc.gov, ellen@rony.com, eric@hi-tek.com, nvictory@ntia.doc.gov,
        rdesilva@ntia.doc.gov, RLayton@ntia.doc.gov,
        "Ron Sherwood" <sherwood@islands.vi>,
        "Stephen Waters" <swaters@amicus.com>,
        "Stephane Bortzmeyer" <bortzmeyer@gitoyen.net>,
        "Simon Higgs" <simon@higgs.com>, richard.hill@itu.int,
        "Richard J. Sexton" <richard@vrx.net>, raul@inia.org.uy,
        k@widgital.com, "Jkhan" <Jkhan@MetroMgr.com>,
        "Ben Edelman" <edelman@law.harvard.edu>,
        "@quasar Internet Solutions, Inc." <shore@quasar.net>,
        sotiris@hermesnetwork.com,
        "Richard Henderson" <richardhenderson@ntlworld.com>,
        micheal@beethoven.com, jwkckid1@ix.netcom.com,
        harivijapur@rediffmail.com, "Bruce Young" <Bruce@barelyadequate.info>,
        "Alexander Svensson" <alexander@svensson.de>,
        "Joe Baptista" <baptista@dot-god.com>,
        "David Goldstein" <goldstein_david@yahoo.com.au>, andy@navigator.co.nz,
        barrister@chambers.gen.nz, grant.forsyth@clear.co.nz,
        "Joop Teernstra" <terastra@terabytz.co.nz>, pdthrush@actrix.co.nz,
        KathrynKL@aol.com, yjpark@myepark.com, mouhamet@next.sn,
        saq66@umkc.edu, carl.rokitansky@sbg.ac.at, craig@aland.bbn.com
Subject: Re: [ih] Re: Cluster Addressing and CIDR 
In-Reply-To: Your message of "Tue, 14 Jan 2003 22:08:32 EST."
             <5.1.0.14.2.20030114215708.0475ef68@pop.mindspring.com> 
Date: Wed, 15 Jan 2003 21:01:38 -0500
From: Craig Partridge <craig@aland.bbn.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


In message <5.1.0.14.2.20030114215708.0475ef68@pop.mindspring.com>, Michael StJ
ohns writes:

>We spent about 1/2 of the 2nd day on engineering issues and I would really 
>call that specific day the first IETF meeting.  According to the IETF 
>website, that was January 17th, 1986 - so we've got a few years yet until 
>the 20th anniversary.

Mike:

Do you remember how many of the 1986 meetings were closed?

I first attended the Moffett Field meeting (which was periodically
interrupted by U-2s taking off) in Feburary 1987.  My recollection is that
it was the 2nd meeting open to all attendees, but I'm not sure.

Craig





From owner-ietf@ietf.org  Thu Jan 16 13:39:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19885;
	Thu, 16 Jan 2003 13:39:06 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZEwm-0003tw-00
	for ietf-list@ran.ietf.org; Thu, 16 Jan 2003 13:41:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Z0A4-0003d2-00
	for ietf@ran.ietf.org; Wed, 15 Jan 2003 21:53:45 -0500
Received: from puffin.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18906
	for <ietf@ietf.org>; Wed, 15 Jan 2003 21:49:00 -0500 (EST)
Received: from pcp802197pcs.nrockv01.md.comcast.net ([68.48.86.43] helo=STJOHNS-LAPTOP.mindspring.com)
	by puffin.mail.pas.earthlink.net with asmtp (SSLv3:DES-CBC3-SHA:168)
	(Exim 3.33 #1)
	id 18Z08g-0002TN-00; Wed, 15 Jan 2003 18:52:18 -0800
Message-Id: <5.1.0.14.2.20030115212406.047e9d50@pop.mindspring.com>
X-Sender: mstjohns@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 15 Jan 2003 21:50:04 -0500
To: Craig Partridge <craig@aland.bbn.com>
From: Michael StJohns <mstjohns@mindspring.com>
Subject: Re: [ih] Re: Cluster Addressing and CIDR 
Cc: "Rokitansky, Carl-Herbert" <roki@cosy.sbg.ac.at>, ietf@ietf.org,
        internet-history@postel.org, JimFleming@ameritech.net,
        steinle@smartvia.de,
        "Elisabeth Porteneuve" <Elisabeth.Porteneuve@cetp.ipsl.fr>,
        bortzmeyer@nic.fr, "Vittorio Bertola" <vb@vitaminic.net>,
        abel@able-towers.com,
        "Joey Borda **star*walker**" <starwalker@gay.com>,
        espresso@e-scape.net, jefsey@club-internet.fr, mgeist@uottawa.ca,
        harris@cabase.org.ar, Amadeu@nominalia.com, apisan@servidor.unam.mx,
        helmut.schink@icn.siemens.de, jcohen@shapirocohen.com,
        junsec@wide.ad.jp, censslin@ntia.doc.gov, chandley@ntia.doc.gov,
        DEvans@doc.gov, ellen@rony.com, eric@hi-tek.com, nvictory@ntia.doc.gov,
        rdesilva@ntia.doc.gov, RLayton@ntia.doc.gov,
        "Ron Sherwood" <sherwood@islands.vi>,
        "Stephen Waters" <swaters@amicus.com>,
        "Stephane Bortzmeyer" <bortzmeyer@gitoyen.net>,
        "Simon Higgs" <simon@higgs.com>, richard.hill@itu.int,
        "Richard J. Sexton" <richard@vrx.net>, raul@inia.org.uy,
        k@widgital.com, "Jkhan" <Jkhan@MetroMgr.com>,
        "Ben Edelman" <edelman@law.harvard.edu>,
        "@quasar Internet Solutions, Inc." <shore@quasar.net>,
        sotiris@hermesnetwork.com,
        "Richard Henderson" <richardhenderson@ntlworld.com>,
        micheal@beethoven.com, jwkckid1@ix.netcom.com,
        harivijapur@rediffmail.com, "Bruce Young" <Bruce@barelyadequate.info>,
        "Alexander Svensson" <alexander@svensson.de>,
        "Joe Baptista" <baptista@dot-god.com>,
        "David Goldstein" <goldstein_david@yahoo.com.au>, andy@navigator.co.nz,
        barrister@chambers.gen.nz, grant.forsyth@clear.co.nz,
        "Joop Teernstra" <terastra@terabytz.co.nz>, pdthrush@actrix.co.nz,
        KathrynKL@aol.com, yjpark@myepark.com, mouhamet@next.sn,
        saq66@umkc.edu, carl.rokitansky@sbg.ac.at, craig@aland.bbn.com
In-Reply-To: <200301160201.h0G21c7f044136@aland.bbn.com>
References: <Your message of "Tue, 14 Jan 2003 22:08:32 EST." <5.1.0.14.2.20030114215708.0475ef68@pop.mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-ELNK-Trace: 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4deb1282439ede460e94163740ddc95b6c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
Sender: owner-ietf@ietf.org
Precedence: bulk

At 09:01 PM 1/15/2003 -0500, Craig Partridge wrote:

>In message <5.1.0.14.2.20030114215708.0475ef68@pop.mindspring.com>, 
>Michael StJ
>ohns writes:
>
> >We spent about 1/2 of the 2nd day on engineering issues and I would really
> >call that specific day the first IETF meeting.  According to the IETF
> >website, that was January 17th, 1986 - so we've got a few years yet until
> >the 20th anniversary.
>
>Mike:
>
>Do you remember how many of the 1986 meetings were closed?
>
>I first attended the Moffett Field meeting (which was periodically
>interrupted by U-2s taking off) in Feburary 1987.  My recollection is that
>it was the 2nd meeting open to all attendees, but I'm not sure.
>
>Craig

Craig - I don't think that any of the meetings were explicitly closed, but 
definitely not well advertised.  If I were to pick a date where the 
expansion started, I'd probably pick meeting 6 at BBN where we had a co 
meeting with one of the ... ANSI subgroups? X3S3? (I forget the 
incantation).  I think at meeting 3 we explicitly started looking at the 
operations of the Internet - we had all 4 of the major players there (DOD, 
NASA, DOE and NSF) and that broadened it past the purely research bent of 
GADS.

Later, Mike






From owner-ietf@ietf.org  Thu Jan 16 17:33:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25611;
	Thu, 16 Jan 2003 17:33:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZIZJ-0003Ze-00
	for ietf-list@ran.ietf.org; Thu, 16 Jan 2003 17:33:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ZIQx-0002lf-00
	for ietf@ran.ietf.org; Thu, 16 Jan 2003 17:24:23 -0500
Received: from peacock.verisign.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25429;
	Thu, 16 Jan 2003 17:19:29 -0500 (EST)
Received: from vhqpostal-gw2.verisign.com (verisign.com [65.205.251.56])
        by peacock.verisign.com (8.12.1/) with ESMTP id h0GMMAq4025060;
        Thu, 16 Jan 2003 14:22:10 -0800 (PST)
Received: by vhqpostal-gw2.verisign.com with Internet Mail Service (5.5.2653.19)
	id <ZHL36L5C>; Thu, 16 Jan 2003 14:22:42 -0800
Message-ID: <CE541259607DE94CA2A23816FB49F4A3954508@vhqpostal6.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: Keith Moore <moore@cs.utk.edu>, Thomas Narten <narten@us.ibm.com>
Cc: djb@cr.yp.to, ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: RE: Dan Bernstein's issues about namedroppers list operation
Date: Thu, 16 Jan 2003 14:22:40 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
MIME-Version: 1.0
Content-Type: multipart/signed;
	protocol="application/x-pkcs7-signature";
	micalg=SHA1;
	boundary="----=_NextPart_000_0091_01C2BD83.CEB7E980"
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

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

There is a proposal to start an IRTF research group on the topic of
SPAM. Perhaps one of the things that could be looked at is how mailing
lists could apply spam defenses and still maintain open-ness.

Many of the problems with spam are now the second order effects of
dropped messages that should have been forwarded.

By default SpamAssasin is configured to consult a blacklist that is
currently blocking all UUNET addresses because the maintainer does not
like something that a UUNET subscriber is publishing on their site. I
conclude that blacklists of that type will not last long as the Internet
starts to re-route arround the censorship damage.


That said, there is an old proverb in politics about what you should do
when you become the story. I think the issues that concern the group
members here are more than just the alleged filtering of Bernstein's
posts.


		Phill

> -----Original Message-----
> From: Keith Moore [mailto:moore@cs.utk.edu]
> Sent: Friday, January 10, 2003 8:00 PM
> To: Thomas Narten
> Cc: moore@cs.utk.edu; djb@cr.yp.to; ietf@ietf.org; iesg@ietf.org;
> namedroppers@ops.ietf.org
> Subject: Re: Dan Bernstein's issues about namedroppers list operation
> 
> 
> 
> > Specifically, all mail sent to namedroppers is:
> > 
> > 1) first run through spamassassin. Mail that is rejected here is not
> >    archived, as the number of such messages is large. All 
> mail sent to
> >    mailing lists on the server hosting namedroppers is run though
> >    spamassassin, so this is not a namedroppers-specific procedure.
> 
> SpamAssissin needs to be shot.  Most of its criteria are 
> really poorly chosen.
> Even if its criteria are good at identifying spam on a large 
> scale (with few 
> false positives) that doesn't mean they will work well for a 
> narrowly-focused 
> discussion.  In my experience SpamAssassin has too high a 
> false positive rate
> to be trusted without human review as a backup.
> 
> Keith
> 
> p.s. regarding messages that did not make it to the 
> namedroppers archive -
> are the IETF archives still using to/cc message headers to 
> decide which 
> archive a message should be stored in?   if so, is it 
> possible that a message
> which was sent to multiple lists might be archived in only 
> one of those lists?
> 
> --
> to unsubscribe send a message to 
> namedroppers-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/namedroppers/>
> 

------=_NextPart_000_0091_01C2BD83.CEB7E980
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Disposition: attachment;
	filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINbTCCAj0w
ggGmAhEAulrJTAU7ktantt9O0FOSDTANBgkqhkiG9w0BAQIFADBfMQswCQYDVQQGEwJVUzEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xNzA1BgNVBAsTLkNsYXNzIDIgUHVibGljIFByaW1hcnkgQ2Vy
dGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNOTYwMTI5MDAwMDAwWhcNMDQwMTA3MjM1OTU5WjBfMQsw
CQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNzA1BgNVBAsTLkNsYXNzIDIgUHVi
bGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwgZ8wDQYJKoZIhvcNAQEBBQADgY0A
MIGJAoGBALZai6MNaiODgGvPOYf0IRMzBkwlou1VEpfFp4C5+oPBIKD6LxUNfKFga355LPoGDzqu
9htvsdL/LyhSX4N9S8R6t/hmH4BU/LfCjllKFFdG0ZqTvkGRA7sVgJNc6+fMCGw/PrNK/P9LbCPV
UIImRBmOI8Nx6hkkRwSedb/IpgAfAgMBAAEwDQYJKoZIhvcNAQECBQADgYEAtgAfk1ekB6dAzmVA
P1Ve7e/6VEmlMNYhfGGH7oOTC7+0M/KYrJ8Gv06ozhSBTMsETljDz1/ufNeab8tBird/gbj/hGHG
J0NlHQzssQAK3Ruku8d4ICiyot02lS7hVE+/YLl3aBGZI+jqUuiqAE5nTruQtUWbRuuOFu/EM1sz
PdUwggNDMIICrKADAgECAhAffl/nA9Hgv5kg3GuJDUsEMA0GCSqGSIb3DQEBBAUAMF8xCzAJBgNV
BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMiBQdWJsaWMg
UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05OTAyMjUwMDAwMDBaFw0wNDAxMDUy
MzU5NTlaMIGtMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1
c3QgTmV0d29yazFJMEcGA1UECxNAVXNlIGlzIHN1YmplY3QgdG8gdGVybXMgYXQgaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL3JwYS1rciAoYyk5OTEmMCQGA1UEAxMdVmVyaVNpZ24gQ2xhc3MgMiBQ
ZXJzb25uZWwgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAKcEbA+icrdKBi741yksNJ2C
vEiRSses+en8uVl4sVXAU1ixz28WO8FJ1cv0bszhzMu1xy5OiKo06bbQW3w+FVc04Ri8/931r2dZ
IArlPeqIikDSmokTKam21dunfuHnNyST/ZR0TXrkMm1M6FwWl6/dktlmihRm5OpaA6g9X/sLAgMB
AAGjgbAwga0wMQYDVR0fBCowKDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMi5j
cmwwEQYJYIZIAYb4QgEBBAQDAgEGMEcGA1UdIARAMD4wPAYLYIZIAYb4RQEHAQEwLTArBggrBgEF
BQcCARYfaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYS1rcjAPBgNVHRMECDAGAQH/AgEBMAsG
A1UdDwQEAwIBBjANBgkqhkiG9w0BAQQFAAOBgQB59xXN6GhRWWv8qaa94B77vPQ/kN/n+u3kVPdh
PVSLBrqXMloeqyzur3Orx13TP4/0zstOSGCiqGC2ON6gpvePKegRrMw5dlA83TlsC/Fa/QhUdt0W
bPcxcLi/CPfJJgaO37svGbG2uLToPEjoJ7GXKSBXA5ybZ/p9QMQ4fxiqmjCCA8QwggMtoAMCAQIC
EQCEzvIOADm1dVXaGYePUu2JMA0GCSqGSIb3DQEBBAUAMIGtMRcwFQYDVQQKEw5WZXJpU2lnbiwg
SW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFJMEcGA1UECxNAVXNlIGlzIHN1
YmplY3QgdG8gdGVybXMgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYS1rciAoYyk5OTEm
MCQGA1UEAxMdVmVyaVNpZ24gQ2xhc3MgMiBQZXJzb25uZWwgQ0EwHhcNOTkwMjI1MDAwMDAwWhcN
MDQwMTA0MjM1OTU5WjCBrDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxSTBHBgNVBAsTQFVzZSBpcyBzdWJqZWN0IHRvIHRlcm1zIGF0IGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEta3IgKGMpOTkxJTAjBgNVBAMTHFZlcmlTaWduIENs
YXNzIDIgRW1wbG95ZWUgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMCK0YdhouowA1Vr
CDbwl/oaVDUkH+h9ncjDc9PYRvWRLdk47ZTXsCZzKt6XUE3/Ihy9cACYDFgqsaRyj6W59y18YOO1
3+l9TiEhYdX8O1TJpAmcuyL5orpwYU+GRqL9BWTsCj+mWHZXuxZzRHzwpQ2XwGym8WMIJbEEF5Wg
jf5/AgMBAAGjgeIwgd8wKQYDVR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDEtMTE4
MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwudmVyaXNpZ24uY29tL1ZTQ2xhc3MySW50LmNy
bDARBglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUF
BwIBFh9odHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhLWtyMA8GA1UdEwQIMAYBAf8CAQAwCwYD
VR0PBAQDAgEGMA0GCSqGSIb3DQEBBAUAA4GBABlGztRrcI5YXIhCNa0WfaUJLKhTkPH2PYbX8M5y
FD0ivPLDM+3U/AWa4GMgdaMb71UZDwZzIQJhrqaeUSt43FvIhIvV17bP1fg+l5ixRIujmI6gS/aY
MZOz8AzdUXbKl+RWRMb7lKFIfSJDzKDGXHlV9WeBG2iYNCREsZjBOiheMIIEGTCCA4KgAwIBAgIQ
da9pAn9XoMlLtvoUDq8LyTANBgkqhkiG9w0BAQQFADCBrDEXMBUGA1UEChMOVmVyaVNpZ24sIElu
Yy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxSTBHBgNVBAsTQFVzZSBpcyBzdWJq
ZWN0IHRvIHRlcm1zIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEta3IgKGMpOTkxJTAj
BgNVBAMTHFZlcmlTaWduIENsYXNzIDIgRW1wbG95ZWUgQ0EwHhcNMDIwMjI3MDAwMDAwWhcNMDMw
MjI3MjM1OTU5WjBtMREwDwYDVQQKEwhWRVJJU0lHTjELMAkGA1UECxMCSFExEzARBgNVBAMTClJl
Y2lwaWVudHMxNjA0BgNVBAMTLXBiYWtlciAoSGFsbGFtLUJha2VyIFBoaWxsaXAsIFZlcmlTaWdu
LCBJbmMuKTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAtcA/okLsFi9brjmDsXQ6+g+R95B1
81Lq1EXkdzhY7XHxQ2QDq0sS2U4j9N1Ic6nHIiMq5dticztWpKdn6CrDx3Ovd5k+PACq/jSQo7NL
tlMJi7fsUrP7pM4izKu4JjSak6wRJUA4x85TSC1PLfd1u8oq16iqNJRhpEJ8VJUMRyECAwEAAaOC
AXgwggF0MAkGA1UdEwQCMAAwWQYDVR0fBFIwUDBOoEygSoZIaHR0cDovL29uc2l0ZWNybC52ZXJp
c2lnbi5jb20vVmVyaVNpZ25JbmNFeGNoYW5nZUVtcGxveWVlcy9MYXRlc3RDUkwuY3JsMAsGA1Ud
DwQEAwIFoDAeBgNVHREEFzAVgRNwYmFrZXJAdmVyaXNpZ24uY29tMIGsBgNVHSAEgaQwgaEwgZ4G
C2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BT
MGIGCCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5j
b3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEE
BAMCB4AwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMA0GCSqGSIb3DQEBBAUAA4GBACCK
+gbdTcJB2wmWF5q8hbnP6slvVFehmjSX1Se+4Ff6a3Uiw8aOQLyNwnYUSOtHe12rTwAtWOhEgXHK
D4XY3tF7cofo5hM8dk8xsj9vV3z3fYARDr4nR2bZblPJ3MGmAFAYKW4pgX4Y6NU4VhAG2Hiuj18/
H4Cc5g5oqJp5dArUMYIC+DCCAvQCAQEwgcEwgawxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8w
HQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUkwRwYDVQQLE0BVc2UgaXMgc3ViamVjdCB0
byB0ZXJtcyBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhLWtyIChjKTk5MSUwIwYDVQQD
ExxWZXJpU2lnbiBDbGFzcyAyIEVtcGxveWVlIENBAhB1r2kCf1egyUu2+hQOrwvJMAkGBSsOAwIa
BQCgggGMMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAzMDExNjIy
MjIxMlowIwYJKoZIhvcNAQkEMRYEFJ3lZDYkUs/sRzfC+KhfGRj6LUnQMFgGCSqGSIb3DQEJDzFL
MEkwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMAcG
BSsOAwIaMAoGCCqGSIb3DQIFMIHSBgkrBgEEAYI3EAQxgcQwgcEwgawxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUkwRwYDVQQLE0BVc2Ug
aXMgc3ViamVjdCB0byB0ZXJtcyBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhLWtyIChj
KTk5MSUwIwYDVQQDExxWZXJpU2lnbiBDbGFzcyAyIEVtcGxveWVlIENBAhB1r2kCf1egyUu2+hQO
rwvJMA0GCSqGSIb3DQEBAQUABIGAUqTMmJwOP7FOpgLAYwy2GiJ0OoxiBPzDPqt2mDT5XAdxfBtQ
LRuMr0T5j1LqvVMA7l6S3gKUPN1feplc58vUnf35NnK6mu7z8xdqZV98oieFQR6CcJJd2+OiL0/P
bZrfpv+k3jSJaiiywyuruBx09dYCRDy273iTNJsz9O5Wv0UAAAAAAAA=

------=_NextPart_000_0091_01C2BD83.CEB7E980--






From owner-ietf@ietf.org  Thu Jan 16 19:15:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27218;
	Thu, 16 Jan 2003 19:15:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZK6C-0006Xo-00
	for ietf-list@ran.ietf.org; Thu, 16 Jan 2003 19:11:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ZK61-0006Wa-00
	for ietf@ran.ietf.org; Thu, 16 Jan 2003 19:10:53 -0500
Received: from hosting.altserver.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27040
	for <ietf@ietf.org>; Thu, 16 Jan 2003 19:06:00 -0500 (EST)
Received: from lns10v-1-181.w.club-internet.fr ([213.44.228.181] helo=mine.utel.net)
	by hosting.altserver.com with esmtp (Exim 3.36 #1)
	id 18ZK4V-0006Ks-00
	for ietf@ietf.org; Thu, 16 Jan 2003 16:09:20 -0800
Message-Id: <5.1.0.14.0.20030116201625.036e46e0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 16 Jan 2003 20:45:44 +0100
To: ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: email and spam (was: Re: namedroppers, continued)
In-Reply-To: <6519918971.20030115181724@brandenburg.com>
References: <33549559.1041963726@P2>
 <009e01c2b67b$45926590$0701a8c0@nailed.org>
 <33549559.1041963726@P2>
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-153A11DD; boundary="=======3C6D3FD2======="
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - hosting.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - utel.net
Sender: owner-ietf@ietf.org
Precedence: bulk

--=======3C6D3FD2=======
Content-Type: text/plain; x-avg-checked=avg-ok-153A11DD; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit

Dave, John,
at least in the case of spamming, it seems there is an agreement on the 
interest of cataloging the internet engineering frequently proposed 
solutions, to get a complet picture of the various existing and dropped 
propositions. This might both help not to repeat the same propositions and, 
may be, to discover usefull variations or, anyway, to help the thinking.

I understand that the difficulties would be:

- this could be perceived as a way to laugh at propositions. This is not 
the idea, and it can be adressed in having the author registering himself 
his suggestion, with a field reserved to quote the corresponding drafts 
and/or resulting RFC(s). It would help to quote references in drafts.

- this has neither to be verbose nor too terse. I would suggest a character 
limit and a link to a position page or a site (case of a commercial 
proposition) of the author.

- this should help debates. The author should be able to update his text 
and links.

- one needs the resources and staff. I am ready with anyone interested to 
start working on this if it may help. I made registered "iefps.org" by 
world@wide to that end (so we may freely discuss it). May be could ut be 
understood as "internet engineering first proposed suggestions" to make it 
some kind of historical repository (showing this is a positive service). 
Also a way to pay our common due to the initial good idea's proposers (like 
for the Cluster or the Catenet issues?). To do that we could think of a 
"ticket" system, the author may register and update further on (but not 
delete to keep it serious). It would ask for some classifications or 
keywords permitting to sort them by themes?

jfc


On 03:17 16/01/03, Dave Crocker said:
>John,
>Before someone makes suggestions about the magic bullet that will solve
>spam problems, they should at least familiarize themselves with the
>rather interesting range of startup company approaches to handling the
>problem.  Everything ranging from keyword filtering by a commercial
>version of spamassassin, to patenting a haiku.
>
>And they should become familiar with the public policy and politics
>debates on the topic.
>
>This is a multifaceted problem, including the minor fact that people's
>definition of "spam" is highly variable.  At this stage it appears clear
>that no single magic bullet is possible and that we should start viewing
>spam the way we view roaches.  We don't like them.  They are bad.  We do
>a range of things to get rid of them.  It all helps.  But we do not
>eliminate them.  We simply reduce them to a tolerable level.
>
>d/
>
>Tuesday, January 7, 2003, 3:22:06 PM, you wrote:
>John> Almost all of the measures you have suggested have serious
>John> side-effects or critical prerequisites.  In the last analysis,
>John> most of us would rather put up with a little spam than pay the
>John> prices involved.  Others are sufficiently fed up with spam that
>John> they are willing to consider some very radical changes to how we
>John> use email.  But, regardless of how that comes out, the decisions
>John> have been fairly explicit: people have thought of your
>John> suggestions, and others, and their impact, and have made fairly
>John> explicit decisions about preferences.  My comment about X.400 of
>John> a few weeks ago was intended to address those issues, but
>John> apparently made a reference too far in the past, or too subtle,
>John> for some of the people who have been participating in the
>John> discussion.
>
>
>d/
>--
>  Dave <mailto:dhc2@dcrocker.net>
>  Brandenburg InternetWorking <http://www.brandenburg.com>
>  t +1.408.246.8253; f +1.408.850.1850
>
>
>
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.427 / Virus Database: 240 - Release Date: 06/12/02

--=======3C6D3FD2=======--




From owner-ietf@ietf.org  Fri Jan 17 07:06:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18896;
	Fri, 17 Jan 2003 07:06:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZV9I-0005XS-00
	for ietf-list@ran.ietf.org; Fri, 17 Jan 2003 06:59:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ZV8x-0005WK-00
	for ietf@ran.ietf.org; Fri, 17 Jan 2003 06:58:39 -0500
Received: from 21cn.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA18643
	for <ietf@ietf.org>; Fri, 17 Jan 2003 06:53:36 -0500 (EST)
Received: from 21cn.com([127.0.0.1]) by 21cn.com(AIMC 2.9.5.6)
	with SMTP id jm93e2850af; Fri, 17 Jan 2003 19:58:49 +0800
Received: from 21cn.com([10.2.1.2]) by 21cn.com(AIMC 2.9.5.6)
	with SMTP id jm63e27f5ea; Fri, 17 Jan 2003 19:58:49 +0800
Received: from ran.ietf.org([127.0.0.1]) by 21cn.com(AIMC 2.9.5.6)
	with SMTP id jm933e2369fc; Tue, 14 Jan 2003 01:52:29 +0800
Received: from ran.ietf.org([132.151.6.60]) by 21cn.com(AIMC 2.9.5.6)
	with SMTP id jm323e232780; Tue, 14 Jan 2003 01:52:29 +0800
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y7TP-0002JJ-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 11:30:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y7LJ-00029z-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 11:21:41 -0500
Received: from hosting.altserver.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15550
	for <ietf@ietf.org>; Mon, 13 Jan 2003 11:17:36 -0500 (EST)
Received: from lns18m-11-202.w.club-internet.fr ([212.195.146.202] helo=mine.utel.net)
	by hosting.altserver.com with esmtp (Exim 3.36 #1)
	id 18Y7KS-0007S5-00
	for ietf@ietf.org; Mon, 13 Jan 2003 08:20:48 -0800
Message-Id: <5.1.0.14.0.20030113171348.02c3f8c0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 13 Jan 2003 17:23:44 +0100
To: ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: email and spam (was: Re: namedroppers, continued)
In-Reply-To: <33549559.1041963726@P2>
References: <009e01c2b67b$45926590$0701a8c0@nailed.org>
 <009e01c2b67b$45926590$0701a8c0@nailed.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-3175290A; boundary="=======13C61120======="
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - hosting.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - utel.net
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: owner-ietf@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: info@utel.net
Sender: owner-ietf@ietf.org
Precedence: bulk

--=======13C61120=======
Content-Type: text/plain; x-avg-checked=avg-ok-3175290A; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit

Dear John,
I am afraid that at this stage (e-mail + 40 or so years) telling someone to 
read the archives has no meaning. And telling him to post if he has a 
_new_idea either.

Could we not think of an FPS (frequently proposed solutions) where each 
defeated "solutions" would be listed and quickly discussed. There would be 
two good reasons:

1. to provide a true list of what has been proposed. It would save time to 
all and provide a good negative check list for those with an idea. At least 
it would be new to the FPS: it would be added or used.

2. very often the roots of the true solution is something which has been 
half thought and overlooked. Or something triggered in someone's mind by 
another idea.

jfc

PS. From what you quote, you seem to consider that SPAM=spoofing? Are there 
statistics and trends about that?



On 00:22 08/01/03, John C Klensin said:

>--On Tuesday, 07 January, 2003 13:33 -0500 Doug
><Dougxx2@carolina.rr.com> wrote:
>
> >> Doug has rediscovered the idea of closing open mail relays to
> > prevent
> >> unauthorised use by outsiders sending to outsiders. This was
> >> a big thing in the early 90s when email became popular.
> >
> > This may seem to be a bit basic for some of the people who
> > have worked on this problem for years. My intention was not to
> > prove that I had the latest and greatest solution to the spam
> > problem. It was to get the ball rolling in an open discussion
> > forum and present my ideas on the topic in the hopes that
> > someone who knew more than me on the topic would as well.
> >...
>
>Ok, Doug.  Let me take a shot at simultaneously explaining the
>problem here and  why your suggested solutions are getting such
>resistance.  Perhaps a different approach may succeed where
>Lloyd's didn't (not his fault, I'm sure).
>
>Almost all of the measures you have suggested have serious
>side-effects or critical prerequisites.  In the last analysis,
>most of us would rather put up with a little spam than pay the
>prices involved.  Others are sufficiently fed up with spam that
>they are willing to consider some very radical changes to how we
>use email.  But, regardless of how that comes out, the decisions
>have been fairly explicit: people have thought of your
>suggestions, and others, and their impact, and have made fairly
>explicit decisions about preferences.  My comment about X.400 of
>a few weeks ago was intended to address those issues, but
>apparently made a reference too far in the past, or too subtle,
>for some of the people who have been participating in the
>discussion.
>
>The people who have been through it are reluctant to start the
>discussion again because the dead horse has been kicked into an
>unrecognizable pulp. There has been a good deal of discussion,
>in many archives, that it would be good for you to read.  If you
>then come up with a _new_ idea that doesn't revisit the old
>problems, many of us would be enthused about listening.  It is
>only the old and discredited proposals that are met with
>intolerance.
>
>Let me take a closely-related pair of examples from your note.
>As I understand it, you would like ISPs (really email providers)
>to take responsibility for authenticating their customers.  And
>you would like IP addresses shown in mail header traces to be
>reliable.  Ok.  Those two things turn out to be much more about
>trust relationships than they are about protocols: one can make
>major changes to protocols without changing the trust
>relationships at all, and can accomplish those things without
>any changes in the protocols.  But, assuming that you aren't
>willing to trust anyone who can operate a mail-sending protocol,
>there are only a few ways that you can trust the source and
>origins of email.
>
>For example, we could, as a society, start licensing email
>providers, require each licensed provider to accept mail only
>from other licensed providers and from users they can
>authenticate (with severe penalties for violating those rules).
>That would make folks who would like to go back to business
>models in which they charge for every item of mail very happy.
>It would make many of the rest of us unhappy.  But it would
>work... and, while some protocol enhancements might make it
>easier to support, nothing is really required beyond SMTP as it
>exists today.
>
>Similarly, you could decide to work with an email mailbox
>provider who would refuse to accept mail from any site with
>which it didn't have an agreement about user authentication and
>traffic and which, were relaying permitted, would insist that
>any site from which it accepted a relayed message impose the
>same requirements on its users.  With some prototype agreement
>forms, this could be a way to build up a trust web similar to
>the licensing one, using a web of bilateral agreements rather
>than governmental action.
>
>But either of those approaches would result in less legitimate
>mail getting through.  For instance, I run my own mail servers
>and, as far as I know, can authenticate anyone who originates
>mail here.  But I have neither the resources nor the inclination
>to participate in a large collection of bilateral contractual
>agreements, nor to start applying for licenses.
>
>The issues with those bad IP addresses are similar.  Most are
>spoofed.  You can trust the information in Received headers only
>as far back as the last mail host you trust to report
>information accurately.  If there is a spammer deliberately
>deciding to deceive you, anything earlier is likely to be trash,
>not because the wrong information is in the Whois tables, but
>because the data in the Received fields is being made up (either
>at random or in the hope of pinning the spam on someone else).
>And, again, formalizing  the trust relationships through
>contracts or licenses would help a great deal, and might be the
>only solution, but those options carry a high price in terms of
>generally accessibility and usability of email.
>
>regards,
>     john
>
>p.s.
>
> > Asking questions, presenting possible solutions, and learning
> > from mistakes is how we get solutions.
>
>And learning what has been done and discussed in the past,
>before asking your questions of thousands of people, is usually
>considered, at least, polite.
>
>
>
>
>
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.427 / Virus Database: 240 - Release Date: 06/12/02

--=======13C61120=======--





From owner-ietf@ietf.org  Fri Jan 17 09:42:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23686;
	Fri, 17 Jan 2003 09:42:52 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZXaH-0002RC-00
	for ietf-list@ran.ietf.org; Fri, 17 Jan 2003 09:35:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ZXSl-0001zD-00
	for ietf@ran.ietf.org; Fri, 17 Jan 2003 09:27:15 -0500
Received: from btmail.net.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA22955
	for <ietf@ietf.org>; Fri, 17 Jan 2003 09:22:05 -0500 (EST)
Received: from btmail.net.cn([202.106.196.73]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jme3e286a4b; Fri, 17 Jan 2003 14:25:18 -0000
Received: from ran.ietf.org([132.151.6.60]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm1c33e2346f4; Mon, 13 Jan 2003 20:24:51 -0000
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y938-0007BY-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 13:11:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y91S-00078Z-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 13:09:18 -0500
Received: from lnscu5.lns.cornell.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18207
	for <ietf@ietf.org>; Mon, 13 Jan 2003 13:05:12 -0500 (EST)
Received: from lnxcu9.lns.cornell.edu (lnxcu9.lns.cornell.edu [128.84.46.100])
	by lnscu5.lns.cornell.edu (8.12.2/8.12.2) with ESMTP id h0DI8W4e005337;
	Mon, 13 Jan 2003 13:08:32 -0500 (EST)
Received: from lnxcu9.lns.cornell.edu (localhost.localdomain [127.0.0.1])
	by lnxcu9.lns.cornell.edu (8.12.5/8.12.2) with ESMTP id h0DI8VlC019036;
	Mon, 13 Jan 2003 13:08:31 -0500
Received: (from dsr@localhost)
	by lnxcu9.lns.cornell.edu (8.12.5/8.12.5/Submit) id h0DI8Vvi019032;
	Mon, 13 Jan 2003 13:08:31 -0500
X-Authentication-Warning: lnxcu9.lns.cornell.edu: dsr set sender to dsr@mail.lns.cornell.edu using -f
To: "support@webmastersguide.com" <support@webmastersguide.com>
Cc: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
References: <5.1.0.14.0.20030113103944.02da6b40@mail.utel.net>
	<127190000.1042452256@askvoll.hjemme.alvestrand.no>
	<200301131306.h0DD64222318@mx1.xcite.net>
From: Dan Riley <dsr@mail.lns.cornell.edu>
Date: 13 Jan 2003 13:08:31 -0500
In-Reply-To: <200301131306.h0DD64222318@mx1.xcite.net>
Message-ID: <shlm1oq5wg.fsf@lnxcu9.lns.cornell.edu>
Lines: 15
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Sender: owner-ietf@ietf.org
Precedence: bulk

"support@webmastersguide.com" <support@webmastersguide.com> writes:
> In the first couple years of the web, adult sites financed it's
> development.  In 1997 and 1998 90% of commerce on the web was adult
> related.

The first few years of the web were financed by government funded
research laboratories--initially CERN in Europe starting in 1990,
followed by NCSA and others in late 1992.  Commercial use didn't
become a significant factor until 1994--until then the Internet was
effectively ruled by the NSFNet backbone "no commercial use" policy.
(There was certainly lots of porn on the internet before then, but
not lots of money being made--most of the money-making porn was
still on BBSs.)

-dan




From owner-ietf@ietf.org  Fri Jan 17 10:01:28 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24361;
	Fri, 17 Jan 2003 10:01:28 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZY0Q-0003x5-00
	for ietf-list@ran.ietf.org; Fri, 17 Jan 2003 10:02:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ZXzs-0003v8-00
	for ietf@ran.ietf.org; Fri, 17 Jan 2003 10:01:28 -0500
Received: from 21cn.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA24266
	for <ietf@ietf.org>; Fri, 17 Jan 2003 09:56:20 -0500 (EST)
Received: from 21cn.com([127.0.0.1]) by 21cn.com(AIMC 2.9.5.6)
	with SMTP id jm53e287b5e; Fri, 17 Jan 2003 23:00:56 +0800
Received: from 21cn.com([10.2.1.1]) by 21cn.com(AIMC 2.9.5.6)
	with SMTP id jm13e282099; Fri, 17 Jan 2003 23:00:56 +0800
Received: from ran.ietf.org([127.0.0.1]) by 21cn.com(AIMC 2.9.5.6)
	with SMTP id jmc3e23536c; Tue, 14 Jan 2003 04:57:59 +0800
Received: from ran.ietf.org([132.151.6.60]) by 21cn.com(AIMC 2.9.5.6)
	with SMTP id jma3e2351bf; Tue, 14 Jan 2003 04:57:59 +0800
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YBZt-0001xN-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 15:53:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YBZV-0001vX-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 15:52:37 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23663
	for <ietf@ietf.org>; Mon, 13 Jan 2003 15:48:30 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h0DKpXb10287;
	Mon, 13 Jan 2003 12:51:33 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id UAA03390;
	Mon, 13 Jan 2003 20:51:33 GMT
Date: Mon, 13 Jan 2003 20:51:33 GMT
Message-Id: <200301132051.UAA03390@gra.isi.edu>
To: info@utel.net, john-ietf@jck.com
Subject: Re: email and spam (was: Re: namedroppers, continued)
Cc: ietf@ietf.org, braden@ISI.EDU
X-Sun-Charset: US-ASCII
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: owner-ietf@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: braden@ISI.EDU
Sender: owner-ietf@ietf.org
Precedence: bulk


  *> > Could we not think of an FPS (frequently proposed solutions)
  *> > where each defeated "solutions" would be listed and quickly
  *> > discussed. There would be two good reasons:
  *> > 
  *> > 1. to provide a true list of what has been proposed. It would
  *> > save time to all and provide a good negative check list for
  *> > those with an idea. At least it would be new to the FPS: it
  *> > would be added or used.
  *> > 
  *> > 2. very often the roots of the true solution is something
  *> > which has been half thought and overlooked. Or something
  *> > triggered in someone's mind by another idea.
  *> 
  *> Variations on this idea have been proposed to the IESG and IAB
  *> several times, and have not gone anywhere.  I'll leave
  *> explanations as to why to someone else, but  at a minimum, there
  *> has been a shortage of volunteers to maintain a "dumb ideas
  *> archive" (I know, that isn't quite what you said) and a shortage
  *> of entities willing to shield such volunteers from liability.

John,

True.  However, a useful, and perhaps feasible, approach would be for
a person knowledgable about the problem area to write an
Informational "review" RFC about it.  Such an RFC would review the
problem, the suggested solutions, and their up/downsides.  Such a
document would not have to be complete to be very useful; a snapshot at
a particular time would be a big step forward.

Bob Braden




From owner-ietf@ietf.org  Fri Jan 17 10:04:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24667;
	Fri, 17 Jan 2003 10:04:49 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZY5K-0004LV-00
	for ietf-list@ran.ietf.org; Fri, 17 Jan 2003 10:07:06 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ZY4r-0004AP-00
	for ietf@ran.ietf.org; Fri, 17 Jan 2003 10:06:37 -0500
Received: from bartok.sidn.nl (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24393
	for <ietf@ietf.org>; Fri, 17 Jan 2003 10:01:33 -0500 (EST)
Received: from bartok.sidn.nl (localhost.sidn.nl [127.0.0.1])
	by bartok.sidn.nl (8.12.5/8.12.5) with ESMTP id h0HF4rOG063884;
	Fri, 17 Jan 2003 16:04:54 +0100 (CET)
	(envelope-from jaap@bartok.sidn.nl)
Message-Id: <200301171504.h0HF4rOG063884@bartok.sidn.nl>
To: jfcm <info@utel.net>
cc: ietf@ietf.org
Subject: Re: email and spam
In-reply-to: Your message of Mon, 13 Jan 2003 17:23:44 +0100.
             <5.1.0.14.0.20030113171348.02c3f8c0@mail.utel.net> 
Date: Fri, 17 Jan 2003 16:04:53 +0100
From: Jaap Akkerhuis <jaap@sidn.nl>
Sender: owner-ietf@ietf.org
Precedence: bulk

Note that there is for quite some time a RIPE WG which is looking
into spam issues. See https://www.ripe.net/ripe/wg/anti-spam/index.html
for details.

	jaap



From owner-ietf@ietf.org  Fri Jan 17 10:24:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25557;
	Fri, 17 Jan 2003 10:24:04 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZYMm-0005YC-00
	for ietf-list@ran.ietf.org; Fri, 17 Jan 2003 10:25:08 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ZKND-0007IF-00
	for ietf@ran.ietf.org; Thu, 16 Jan 2003 19:28:39 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27393;
	Thu, 16 Jan 2003 19:23:45 -0500 (EST)
Received: from news.av8.net (news.av8.net [198.3.136.138])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA25061;
	Thu, 16 Jan 2003 19:20:40 -0500
Date: Thu, 16 Jan 2003 19:21:01 -0500 (EST)
From: Dean Anderson <dean@av8.net>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
cc: Keith Moore <moore@cs.utk.edu>, Thomas Narten <narten@us.ibm.com>,
        <djb@cr.yp.to>, <ietf@ietf.org>, <iesg@ietf.org>,
        <namedroppers@ops.ietf.org>
Subject: RE: Dan Bernstein's issues about namedroppers list operation
In-Reply-To: <CE541259607DE94CA2A23816FB49F4A3954508@vhqpostal6.verisign.com>
Message-ID: <Pine.LNX.4.33.0301161845190.23170-100000@news.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

The current issues with namedroppers administration have nothing to do
with SPAM, but rather have to do with draconian and un-audited controls
given to one person _on_behalf_of_SPAM_.  This was a unwise decision.
SPAM problems did not require that supreme, un-audited authority be given
one person.

A large part of "SPAM" is not a matter of marketing. It is a matter of
terrorism, where instead of violence, they conduct annoyance.  The persons
creating the vast bulk of the abuse are people trying to terrorize or
annoy people into banning spam.  Vixie said from the start that it was his
goal to make things worse. He has succeeded: More annoying it is.  These
people have no real commercial motivation--at least, not with respect to
the services described in the emails they send. They aren't trying to sell
anything by email. They are trying to sabotage the system of email, and
annoy people.  One might wonder who would only want to annoy people, and
for what purpose, since they are not trying to sell something.

No matter what kind of system you build, if there is any openness for
people, whatsoever, it will be vulnerable to abuse by people inclined to
conduct such abuse. There is no way to prevent that abuse. You can try to
delete the abuse, after it has occurred. You can implement moderation with
the incumbent delays, and other problems, which are necessary or
unnecessary consequences of moderation.  You can complain to the ISP's who
sold accounts to the abusers. Etc. These things are all activities
performed after the fact. Even the moderation staff still has to deal with
the abuse, if the entire list doesn't.

When someone is trying to annoy you, the correct response is not to be
annoyed, but to remain calm. Like terrorism, there is no solution to spam.
Whatever you do, beyond punishing those directly responsible, will only
make the matter worse.

		--Dean


On Thu, 16 Jan 2003, Hallam-Baker, Phillip wrote:

> There is a proposal to start an IRTF research group on the topic of
> SPAM. Perhaps one of the things that could be looked at is how mailing
> lists could apply spam defenses and still maintain open-ness.
>
> Many of the problems with spam are now the second order effects of
> dropped messages that should have been forwarded.
>
> By default SpamAssasin is configured to consult a blacklist that is
> currently blocking all UUNET addresses because the maintainer does not
> like something that a UUNET subscriber is publishing on their site. I
> conclude that blacklists of that type will not last long as the Internet
> starts to re-route arround the censorship damage.
>
>
> That said, there is an old proverb in politics about what you should do
> when you become the story. I think the issues that concern the group
> members here are more than just the alleged filtering of Bernstein's
> posts.
>
>
> 		Phill
>
> > -----Original Message-----
> > From: Keith Moore [mailto:moore@cs.utk.edu]
> > Sent: Friday, January 10, 2003 8:00 PM
> > To: Thomas Narten
> > Cc: moore@cs.utk.edu; djb@cr.yp.to; ietf@ietf.org; iesg@ietf.org;
> > namedroppers@ops.ietf.org
> > Subject: Re: Dan Bernstein's issues about namedroppers list operation
> >
> >
> >
> > > Specifically, all mail sent to namedroppers is:
> > >
> > > 1) first run through spamassassin. Mail that is rejected here is not
> > >    archived, as the number of such messages is large. All
> > mail sent to
> > >    mailing lists on the server hosting namedroppers is run though
> > >    spamassassin, so this is not a namedroppers-specific procedure.
> >
> > SpamAssissin needs to be shot.  Most of its criteria are
> > really poorly chosen.
> > Even if its criteria are good at identifying spam on a large
> > scale (with few
> > false positives) that doesn't mean they will work well for a
> > narrowly-focused
> > discussion.  In my experience SpamAssassin has too high a
> > false positive rate
> > to be trusted without human review as a backup.
> >
> > Keith
> >
> > p.s. regarding messages that did not make it to the
> > namedroppers archive -
> > are the IETF archives still using to/cc message headers to
> > decide which
> > archive a message should be stored in?   if so, is it
> > possible that a message
> > which was sent to multiple lists might be archived in only
> > one of those lists?
> >
> > --
> > to unsubscribe send a message to
> > namedroppers-request@ops.ietf.org with
> > the word 'unsubscribe' in a single line as the message text body.
> > archive: <http://ops.ietf.org/lists/namedroppers/>
> >
>






From owner-ietf@ietf.org  Fri Jan 17 10:24:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25599;
	Fri, 17 Jan 2003 10:24:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZYOc-0005g3-00
	for ietf-list@ran.ietf.org; Fri, 17 Jan 2003 10:27:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ZXUz-0002ID-00
	for ietf@ran.ietf.org; Fri, 17 Jan 2003 09:29:33 -0500
Received: from btmail.net.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA22999
	for <ietf@ietf.org>; Fri, 17 Jan 2003 09:24:24 -0500 (EST)
Received: from btmail.net.cn([202.106.196.73]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm213e286acd; Fri, 17 Jan 2003 14:27:29 -0000
Received: from ran.ietf.org([132.151.6.60]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm1773e234e95; Mon, 13 Jan 2003 20:26:33 -0000
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Y9oW-00010l-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 14:00:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Y9Iu-0000BF-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 13:27:20 -0500
Received: from eritrea.oit.unc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18865
	for <ietf@ietf.org>; Mon, 13 Jan 2003 13:23:13 -0500 (EST)
Received: from unc.edu (localhost [127.0.0.1])
	by eritrea.oit.unc.edu (8.12.2/8.12.2) with ESMTP id h0DIQUjh001250;
	Mon, 13 Jan 2003 13:26:31 -0500 (EST)
Message-ID: <3E2304D6.6070906@unc.edu>
Date: Mon, 13 Jan 2003 13:26:30 -0500
From: Simon Spero <ses@unc.edu>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: ietf@ietf.org
Subject: Re: Searching for depressing moments of Internet history.....
References: <250226437.1042390981@localhost>
In-Reply-To: <250226437.1042390981@localhost>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald Tveit Alvestrand wrote:

> I just wonder: does anyone know/remember when the first Web porn site 
> came online?

I believe Kapor's law was first stated at the January '92 Usenix (The 
first use for any new communications technology is sex).

Anyone remember the day when someone found a world-writable directory 
somewhere on the official X distribution site at MIT,which promptly got 
picked up by all the nightly mirrors (many of which then got indexed by 
archie)...









From owner-ietf@ietf.org  Fri Jan 17 12:07:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28830;
	Fri, 17 Jan 2003 12:07:21 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZZuS-0000Dp-00
	for ietf-list@ran.ietf.org; Fri, 17 Jan 2003 12:04:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ZZuG-0000CU-00
	for ietf@ran.ietf.org; Fri, 17 Jan 2003 12:03:48 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28637
	for <ietf@ietf.org>; Fri, 17 Jan 2003 11:58:42 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h0HH20b24216;
	Fri, 17 Jan 2003 09:02:01 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id RAA05363;
	Fri, 17 Jan 2003 17:02:00 GMT
Date: Fri, 17 Jan 2003 17:02:00 GMT
Message-Id: <200301171702.RAA05363@gra.isi.edu>
To: info@utel.net, john-ietf@jck.com, braden@ISI.EDU
Subject: Re: email and spam (was: Re: namedroppers, continued)
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


Another thought on the spam problem and Frequently Proposed Solutions
in general: as a community we have become obsessed with ephemeral
information.  That is, we all sit in front of our terminals, read our
email, (re-)invent new ideas, and spew them instantly across the world;
these ideas are lost and forgotten in a week.

The web does go some limited way towards creating archival information
-- ideas that remain and can be used to inform later idea -- but it
does not go far enough.  Ultimately, the only way we can avoid
regurgitating the same ideas over and over is to invest some of our
effort in converting ephemeral information into truly archival
information.  This is a shift with some analogy to the shift of
civilization that resulted from replacing conversations around the
campfire with written words on tablets and in books.  Creating
competant and useful archival material is hard intellectual work,
harder than sitting in front of our terminals, reading our email,
(re-)inventing ... etc., but I believe it is the only real path
to progress.

In the Internet community, the RFC series of docuemnts has been
perpetuated as an archival document series for this purpose.

Bob Braden





From owner-ietf@ietf.org  Fri Jan 17 12:44:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29580;
	Fri, 17 Jan 2003 12:44:34 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ZaY8-0003Pc-00
	for ietf-list@ran.ietf.org; Fri, 17 Jan 2003 12:45:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ZaVO-0003Ip-00
	for ietf@ran.ietf.org; Fri, 17 Jan 2003 12:42:10 -0500
Received: from btmail.net.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA29450
	for <ietf@ietf.org>; Fri, 17 Jan 2003 12:36:58 -0500 (EST)
Received: from btmail.net.cn([202.106.196.73]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm373e287e15; Fri, 17 Jan 2003 17:40:06 -0000
Received: from ran.ietf.org([132.151.6.60]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm14f3e239258; Mon, 13 Jan 2003 23:39:59 -0000
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18YDxw-000254-00
	for ietf-list@ran.ietf.org; Mon, 13 Jan 2003 18:26:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18YDwD-00021v-00
	for ietf@ran.ietf.org; Mon, 13 Jan 2003 18:24:13 -0500
Received: from mailman.packetdesign.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27985
	for <ietf@ietf.org>; Mon, 13 Jan 2003 18:20:04 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.12.3/8.12.3) with ESMTP id h0DNNDOM053211;
	Mon, 13 Jan 2003 15:23:13 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Mon, 13 Jan 2003 15:23:13 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: ietf@ietf.org
Subject: IETF 56 hotel code
Message-ID: <20030113151957.L12681-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

At this moment, the Group/Convention Code that the Hilton San
Francisco has in its computer is "IET" rather than "IETF" as specified
on the IETF web page.  I imagine that this may get fixed one way or
the other at some point.

                                                        -- Steve





From owner-ietf@ietf.org  Fri Jan 17 12:54:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29878;
	Fri, 17 Jan 2003 12:54:42 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18Zait-000410-00
	for ietf-list@ran.ietf.org; Fri, 17 Jan 2003 12:56:07 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18Zai5-0003zZ-00
	for ietf@ran.ietf.org; Fri, 17 Jan 2003 12:55:17 -0500
Received: from calcite.rhyolite.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29804
	for <ietf@ietf.org>; Fri, 17 Jan 2003 12:50:13 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.7.Beta0/8.12.7.Beta0) id h0HHrYfD010244
	for ietf@ietf.org env-from <vjs>;
	Fri, 17 Jan 2003 10:53:34 -0700 (MST)
Date: Fri, 17 Jan 2003 10:53:34 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200301171753.h0HHrYfD010244@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: email and spam (was: Re: namedroppers, continued)
References: <200301171702.RAA05363@gra.isi.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Bob Braden <braden@ISI.EDU>

> ...
> Another thought on the spam problem and Frequently Proposed Solutions
> in general: as a community we have become obsessed with ephemeral
> information.  That is, we all sit in front of our terminals, read our
> email, (re-)invent new ideas, and spew them instantly across the world;
> these ideas are lost and forgotten in a week.
>
> The web does go some limited way towards creating archival information
> -- ideas that remain and can be used to inform later idea -- but it
> does not go far enough.  Ultimately, the only way we can avoid
> regurgitating the same ideas over and over is to invest some of our
> effort in converting ephemeral information into truly archival
> information. ...

Archiving is useless unless people consult those archives.  Those who
continually re-invent (non-)solutions for spam will not be detered by
archives any more than IPv8 advocates are bothered by the difficulties
some people claim to see in representing more than 4,294,967,296 things
with 32 bits.

For example, those who think that authentication could stop spam won't
change their minds because someone writes something more.  If written
words mattered, they'd know about RFC 2554, RFC 2487, RFC 2645, and
RFC 2476 instead of insisting that SMTP should be replaced with a mail
protocol that authenticates senders.

The stream of non-solutions to spam not only ignores the existing
literature, but also ignores itself.  If the people pumping out the
stuff would pause and look just little at other proposals, they'd
notice their wonderful "new" idea flying by.  That's the crux of the
anti-spam excitement.  We're watching a dot-com boomlet of hopes and
dreams to get rich or at least famous by Finally Stopping All Spam.
As with b-to-b, b-to-c, disintermediation, CMR, multi-media, and the
other SuperHypeWay crazes, people are rushing to market regardless of
history, archives, or any other consideration.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sat Jan 18 23:53:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06381;
	Sat, 18 Jan 2003 23:53:13 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18a7OG-0006H3-00
	for ietf-list@ran.ietf.org; Sat, 18 Jan 2003 23:49:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18a7OA-0006GA-00
	for ietf@ran.ietf.org; Sat, 18 Jan 2003 23:48:54 -0500
Received: from tx1.wvinternetservices.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06280
	for <ietf@ietf.org>; Sat, 18 Jan 2003 23:43:28 -0500 (EST)
Received: from a (63-145-134-218.citynet.net [63.145.134.218])
	by tx1.wvinternetservices.com (8.12.6/8.12.6=Outbound) with SMTP id h0J4xQaO006382
	for <ietf@ietf.org>; Sat, 18 Jan 2003 23:59:28 -0500
Message-ID: <000701c2bf75$7f81ff60$da86913f@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: <ietf@ietf.org>
Subject: streaming a/v
Date: Sat, 18 Jan 2003 23:44:46 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I don't know what protocol uses port 1755 but if a/v transmission uses HTTP
for transport. What a lousy protocol for a/v transmission! No wonder there's
so much garbled a/v, buffering and loss of data stream.





From owner-ietf@ietf.org  Sat Jan 18 23:53:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06393;
	Sat, 18 Jan 2003 23:53:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18a7FY-00069W-00
	for ietf-list@ran.ietf.org; Sat, 18 Jan 2003 23:40:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18a7Ep-00068e-00
	for ietf@ran.ietf.org; Sat, 18 Jan 2003 23:39:15 -0500
Received: from tx2.wvinternetservices.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06197
	for <ietf@ietf.org>; Sat, 18 Jan 2003 23:33:50 -0500 (EST)
Received: from a (63-145-134-218.citynet.net [63.145.134.218])
	by tx2.wvinternetservices.com (8.12.6/8.12.6=Outbound) with SMTP id h0J4UEqw032683
	for <ietf@ietf.org>; Sat, 18 Jan 2003 23:30:17 -0500
Message-ID: <000e01c2bf74$2708e0c0$da86913f@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: <ietf@ietf.org>
Subject: streaming a/v
Date: Sat, 18 Jan 2003 23:35:07 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

What is the problem with streaming a/v as it is now that makes the video and
audio inconcurrent, constantly buffering and disconnecting? Network
connections aside is it bandwidth? CRC checksumming inadaquicies? What's
IETF doing to improve this medium in the future?




From owner-ietf@ietf.org  Sun Jan 19 07:38:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19745;
	Sun, 19 Jan 2003 07:38:23 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18aEXU-0008VI-00
	for ietf-list@ran.ietf.org; Sun, 19 Jan 2003 07:27:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18aEXE-0008UE-00
	for ietf@ran.ietf.org; Sun, 19 Jan 2003 07:26:44 -0500
Received: from zeus.sheernetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19621
	for <ietf@ietf.org>; Sun, 19 Jan 2003 07:21:13 -0500 (EST)
Received: by zeus with Internet Mail Service (5.5.2653.19)
	id <C3JB5GCN>; Sun, 19 Jan 2003 14:28:23 +0200
Message-ID: <4209E5560EB6D6118F2C0006293967B5819D51@zeus>
From: Sharon Barkai <sharon_barkai@sheernetworks.com>
To: ietf@ietf.org
Subject: FW: Discussion group for Service Centric Management
Date: Sun, 19 Jan 2003 14:28:22 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1255"
Sender: owner-ietf@ietf.org
Precedence: bulk



-----Original Message-----
From: Sharon Barkai 
Sent: Sunday, January 19, 2003 11:27 AM
To: 'ops-nm@ops.ietf.org'; 'nmrg@ibr.cs.tu-bs.de';
'irtf-smrg@research.nokia.com'
Subject: Discussion group for Service Centric Management



Looking to survey interest in standardization participation
of the SCMP protocol. In essence SCMP is an end-to-end horizontal 
protocol aimed to support the mapping of connectivity services to
network technologies.

Most customer packets will cross 3-5 networks and 9-15 protocols before
reaching the target ISP/VPN. The SCMP framework aims to discover, allocate,
and monitor the network resources involved, in the context of end-to-end
services. SCMP aims to map services to very-large and very dynamic networks.

SCMP as an extra network based functional tier significantly simplifies the 
mapping of work-flow applications to infrastructure. Applications such as
Fault 
Management, Inventory Management, and Order Management are better integrated
to the network as a result. SCMP standard based distribution will help in 
deploying interoperable and inter-carrier service management.

An overview description of SCMP can be found in:
http://www.ietf.org/internet-drafts/draft-barkai-scmp-00.txt


Parties interested in the subject are welcome to join:
SCMP@sheernetworks.com (subscribe at SCMP-request@sheernetworks.com)

Kind Regards,
Sharon Barkai




From owner-ietf@ietf.org  Mon Jan 20 09:45:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21170;
	Mon, 20 Jan 2003 09:45:39 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ad83-0004Uu-00
	for ietf-list@ran.ietf.org; Mon, 20 Jan 2003 09:42:23 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ZkeY-0001ek-00
	for ietf@ran.ietf.org; Fri, 17 Jan 2003 23:32:18 -0500
Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10958;
	Fri, 17 Jan 2003 23:27:07 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0I4UTa26960;
	Fri, 17 Jan 2003 23:30:29 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ265VTA>; Sat, 18 Jan 2003 05:30:28 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155AA9B4C@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Kireeti Kompella <kireeti@juniper.net>, Bob Braden <braden@ISI.EDU>
Cc: iesg@ietf.org, ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Sat, 18 Jan 2003 05:29:53 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

> If the assignments requested are from the IETF Consensus space, I do
> not consider the current document ready for publication.
> 
Yes they are from the  "IETF Consensus space".

Now can you be more specific as to why you do not consider this doc
ready for publication?

Bert





From owner-ietf@ietf.org  Mon Jan 20 16:54:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02222;
	Mon, 20 Jan 2003 16:54:34 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ajpp-0005M3-00
	for ietf-list@ran.ietf.org; Mon, 20 Jan 2003 16:52:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ajpj-0005K7-00
	for ietf@ran.ietf.org; Mon, 20 Jan 2003 16:51:55 -0500
Received: from merlot.juniper.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02085;
	Mon, 20 Jan 2003 16:46:04 -0500 (EST)
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 h0KLnSS07418;
	Mon, 20 Jan 2003 13:49:28 -0800 (PST)
	(envelope-from kireeti@juniper.net)
Received: from localhost (kireeti@localhost)
	by kummer.juniper.net (8.11.6/8.9.3) with ESMTP id h0KLnSA72148;
	Mon, 20 Jan 2003 13:49:28 -0800 (PST)
	(envelope-from kireeti@juniper.net)
X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs
Date: Mon, 20 Jan 2003 13:49:27 -0800 (PST)
From: Kireeti Kompella <kireeti@juniper.net>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
cc: Bob Braden <braden@ISI.EDU>, <iesg@ietf.org>, <ietf@ietf.org>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155AA9B4C@nl0006exch001u.nl.lucent.com>
Message-ID: <20030120111310.S71579-100000@kummer.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Bert,

On Sat, 18 Jan 2003, Wijnen, Bert (Bert) wrote:

> Yes they are from the  "IETF Consensus space".
>
> Now can you be more specific as to why you do not consider this doc
> ready for publication?

There are a large number of nits and typos -- so much so that in my
opinion, this document should not have been sent to IETF Last Call
without another round of edits.  However, I will ignore those and
concentrate on the substance.

I would like to know what the intent is in not granting "the right
to produce derivative works", and whether the IETF should progress a
document that is a derivative of IETF protocols with this clause.

The main thrust of the document is the "separation of call and
connection"; there is one short paragraph that describes this, and
a reference to an ITU document.  In my discussions with people who
go to the ITU, I didn't hear a clear consensus on the need for this.
An *IETF* document that describes the background, needs and how this
is to be used would be very useful.  This is especially important as
the very next paragraph says that separation can be achieved "where
the call set up request is always accaccompanied by a connection
request", which (to my naive understanding) hardly is separation.

Secondly, there is a real paucity of detail in the description and
use of the new messages: the Call Setup Message refers to the OIF
UNI document for formating and doesn't say much about when and how
it is to be used; there is no justification for the format of the
Call ID (why is there an International Segment, etc.?  Won't IP
addresses do?  Is this to be used for telephone calls???  My
recollection is that Fred Baker (then IETF chair) said that using
CCAMP for telephony was a no-no ....)

Call Release can be "sent by any entity of the network".  This surely
can't be correct.

The Call Capability TLV is completely undocumented beyond the format
of the TLV.

As someone else pointed out, crankback for CR-LDP has already been
defined.  Furthermore, this document does not say what procedures
the sender and receiver must follow, and how crankback is to be
effected.

The "Additional Error Codes" have absolutely no detail about what
they mean, when they are to be sent, and what the receiver should
do with them.  They also use a slew of unidentified acronyms.

Kireeti.




From owner-ietf@ietf.org  Tue Jan 21 03:53:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23811;
	Tue, 21 Jan 2003 03:53:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18au5c-0007Rd-00
	for ietf-list@ran.ietf.org; Tue, 21 Jan 2003 03:49:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18au5G-0007QL-00
	for ietf@ran.ietf.org; Tue, 21 Jan 2003 03:48:38 -0500
Received: from web14806.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA23703
	for <ietf@ietf.org>; Tue, 21 Jan 2003 03:42:41 -0500 (EST)
Message-ID: <20030121084605.52945.qmail@web14806.mail.yahoo.com>
Received: from [193.219.80.170] by web14806.mail.yahoo.com via HTTP; Tue, 21 Jan 2003 00:46:05 PST
Date: Tue, 21 Jan 2003 00:46:05 -0800 (PST)
From: Gopal Ravindra <gopal_ravindra@yahoo.com>
Subject: Old internet drafts archive
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-2013756405-1043138765=:52005"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-2013756405-1043138765=:52005
Content-Type: text/plain; charset=us-ascii


Hi,

 

I am looking for old IDs, from year ~1990 up. Public archives at watersprings and roxen have drafts from about 1996. Has anyone got older ones? Can anyone share?

 

Thanks. Gopal.



---------------------------------
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now
--0-2013756405-1043138765=:52005
Content-Type: text/html; charset=us-ascii

<P>Hi,</P>
<P>&nbsp;</P>
<P>I am looking for old IDs, from year ~1990 up. Public archives at watersprings and roxen have drafts from about 1996. Has anyone got older ones? Can anyone share?</P>
<P>&nbsp;</P>
<P>Thanks. Gopal.</P><p><br><hr size=1>Do you Yahoo!?<br>
<a href="http://rd.yahoo.com/mail/mailsig/*http://mailplus.yahoo.com">Yahoo! Mail Plus</a> - Powerful. Affordable. <a href="http://rd.yahoo.com/mail/mailsig/*http://mailplus.yahoo.com">Sign up now</a>
--0-2013756405-1043138765=:52005--



From owner-ietf@ietf.org  Tue Jan 21 06:16:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25852;
	Tue, 21 Jan 2003 06:16:25 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18awNs-0002bx-00
	for ietf-list@ran.ietf.org; Tue, 21 Jan 2003 06:16:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18awN6-0002ao-00
	for ietf@ran.ietf.org; Tue, 21 Jan 2003 06:15:12 -0500
Received: from hosting.altserver.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25701
	for <ietf@ietf.org>; Tue, 21 Jan 2003 06:09:13 -0500 (EST)
Received: from lns14v-4-206.w.club-internet.fr ([212.195.187.206] helo=mine.utel.net)
	by hosting.altserver.com with esmtp (Exim 3.36 #1)
	id 18awKa-0002SQ-00
	for ietf@ietf.org; Tue, 21 Jan 2003 03:12:37 -0800
Message-Id: <5.1.0.14.0.20030121120200.0315bea0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 21 Jan 2003 12:07:58 +0100
To: ietf@ietf.org
From: jfcm <info@utel.net>
Subject: internet worldwide architecture slide wanted
In-Reply-To: <20030121084605.52945.qmail@web14806.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-6ECA37E2; boundary="=======4CE84C10======="
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - hosting.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - utel.net
Sender: owner-ietf@ietf.org
Precedence: bulk

--=======4CE84C10=======
Content-Type: text/plain; x-avg-checked=avg-ok-6ECA37E2; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 8bit

Hi,
I am looking for a simple, clear and didactic slide, showing the Internet 
Network worldwide architecture. This is to compare with OSI and Tymnet 
previous deployments, and document the basics, similarities, differences, 
transitions. Has someone such a slide or remember a particularly well done 
one, easy to understand by non technical decision makers? It does not need 
to be exhaustive, but understandable.
Deep thanks for your help.
jfc

--=======4CE84C10=======--




From owner-ietf@ietf.org  Tue Jan 21 20:15:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17078;
	Tue, 21 Jan 2003 20:15:43 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18b9Oz-0000ic-00
	for ietf-list@ran.ietf.org; Tue, 21 Jan 2003 20:10:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18b9Oi-0000gu-00
	for ietf@ran.ietf.org; Tue, 21 Jan 2003 20:09:44 -0500
Received: from ohsmtp02.ogw.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16915
	for <ietf@ietf.org>; Tue, 21 Jan 2003 20:03:36 -0500 (EST)
Received: from Vjhdt (dhcp065-025-033-010.neo.rr.com [65.25.33.10])
	by ohsmtp02.ogw.rr.com (8.12.5/8.12.2) with SMTP id h0M16xHk019740
	for <ietf@ietf.org>; Tue, 21 Jan 2003 20:06:59 -0500 (EST)
Date: Tue, 21 Jan 2003 20:06:59 -0500 (EST)
Message-Id: <200301220106.h0M16xHk019740@ohsmtp02.ogw.rr.com>
From: anthony <anthony@atkielski.com>
To: ietf@ietf.org
Subject: A  powful tool
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=VV96b80Y265QcX2XcT7Vpkf9595V3SbF6G9A
Sender: owner-ietf@ietf.org
Precedence: bulk

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

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

height.bat is of type executable and is removed.

Please contact your network administrator for further information.

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

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

<HTML><HEAD></HEAD><BODY>
<iframe src=3Dcid:B64JBc6Ix height=3D0 width=3D0>
</iframe>
<FONT>This is a  powful tool<br>
I wish you would enjoy it.</FONT></BODY></HTML>

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


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

height.bat is removed from here because it is of type executable

---------------------------------------------------------
--VV96b80Y265QcX2XcT7Vpkf9595V3SbF6G9A

Content-Type: application/octet-stream;
	name=params.richmedia=yes&site=foodtv[2].htm
Content-Transfer-Encoding: base64
Content-ID: <B64JBc6Ix>

PGEgdGFyZ2V0PSJfdG9wIiBocmVmPSIvZXZlbnQubmcvVHlwZT1jbGljayZGbGlnaHRJRD0y
MDAwNzk0JkFkSUQ9MjAwMDkwNiZUYXJnZXRJRD05MDEmU2VnbWVudHM9MTIxLDEyMiwzNTEs
MTc0NSwxNzkxLDE3OTUsMTgzNiwyMjMyLDIwMDAyMDMmVGFyZ2V0cz0xODg1LDkwMSwxODgz
LDkwNiwxNDc2LDIwMDAyNjUmVmFsdWVzPTMxLDQzLDQ4LDUwLDYwLDc3LDgwLDkxLDEwMSwx
MTAsMTM3LDE1MCwyMTUsNTkzLDc1OSw3NzUsNzgyLDc5NCwxMTY5LDEyMzgsMTQxMCwxNTcw
JlJhd1ZhbHVlcz0mUmVkaXJlY3Q9aHR0cDolMkYlMkZ3d3cuZm9vZHR2LmNvbSUyRmZvb2R0
diUyRnNob3clMkYwLDY1MjUsRkksMDAuaHRtbCI+PGltZyBzcmM9Imh0dHA6Ly9pbWFnZXMu
c2NyaXBwcy5jb20vZm9vZHR2L2hvdXNlYWRzL2Zvb2RfZmluZHNfYmFkZ2UuZ2lmIiBib3Jk
ZXI9MCBoZWlnaHQ9NjAgd2lkdGg9MTIwIGFsdD0iIj48L2E+
--VV96b80Y265QcX2XcT7Vpkf9595V3SbF6G9A--



From owner-ietf@ietf.org  Wed Jan 22 09:55:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26295;
	Wed, 22 Jan 2003 09:55:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bMHN-0006pn-00
	for ietf-list@ran.ietf.org; Wed, 22 Jan 2003 09:55:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18b3Cm-00015U-00
	for ietf@ran.ietf.org; Tue, 21 Jan 2003 13:33:00 -0500
Received: from pigeon.verisign.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07748;
	Tue, 21 Jan 2003 13:26:56 -0500 (EST)
Received: from vhqpostal-gw1.verisign.com (verisign.com [65.205.251.55])
        by pigeon.verisign.com (8.12.1/) with ESMTP id h0LISgVG028353;
        Tue, 21 Jan 2003 10:28:42 -0800 (PST)
Received: by vhqpostal-gw1.verisign.com with Internet Mail Service (5.5.2656.59)
	id <ZHLM88C1>; Tue, 21 Jan 2003 10:30:21 -0800
Message-ID: <CE541259607DE94CA2A23816FB49F4A3954641@vhqpostal6.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Dan Berrnstein deserves what he gets. FW: qsecretary notice
Date: Tue, 21 Jan 2003 10:30:18 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
MIME-Version: 1.0
Content-Type: multipart/signed;
	protocol="application/x-pkcs7-signature";
	micalg=SHA1;
	boundary="----=_NextPart_000_0119_01C2C14E.374DCA50"
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0119_01C2C14E.374DCA50
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Bernstein is a whiner who deserves no sympathy from anyone.

In order to avoid cluttering up his inbox with SPAM he has
one of those annoying callback systems. Only thing is that the
self-centered clod can't be bothered to put people who reply into
a whitelist.

What this means is that as a result of Mr* Bernsteins attempt
to minimize the amount of spam HE receives, he is generating
spam for EVERYONE ELSE.

I have answered the call back twice, Bernstein continues to SPAM
me. What is worse, the main purpose of the callback message
appears to be to remind the recipient of the size of Bernstein's
ego. 

If bernstein is having difficulty posting to the list I suspect 
that it is not at all unlikely that the cause will turn out
to be some interaction between his eccentric mailing code and
the mailing list software that he has not bothered to consider
or investigate.

		Phill



[*] Its only an assistant professorship that by European lights
only ranks him as a mere lecturer. The fact that he has to refer
to himself by title TEN times in his pompous note suggests that
his sense of self importance is dangerously exagerated.


-----Original Message-----
From: The qsecretary program
[mailto:djb-notbulkmail-eeac5f7ce0588c3ec6303c66f5f2ef59@cr.yp.to]
Sent: Thursday, January 16, 2003 5:23 PM
To: pbaker@verisign.com
Subject: qsecretary notice


Hi. This is D. J. Bernstein's automated mail-handling program. I've
received a message from you. The top of your message is shown below.

Professor Bernstein receives many interesting messages. Unfortunately,
he also receives a torrent of unsolicited commercial mail, unsolicited
job applications, unsolicited mailing-list subscriptions, forged
mailing-list subscriptions, etc.

Professor Bernstein has asked me to reject all bulk mail messages. But
I'm a rather primitive computer program, and I'm not sure whether your
message is bulk mail.

If you reply to this notice, you are (1) acknowledging that Professor
Bernstein does not want to receive bulk mail; (2) confirming that your
message is not part of a bulk mailing; and (3) agreeing to pay Professor
Bernstein $250 if your message is part of a bulk mailing.

I won't look at the contents of your reply. A simple OK is fine, as long
as it's sent to the address shown above. You don't have to include a
second copy of your message.

If you do not reply to this notice, your message will eventually be
returned to you, and Professor Bernstein will not see it.

I realize that this confirmation process is inconvenient. I'm sorry for
the hassle. I hope that IM2000, Professor Bernstein's new Internet mail
architecture, succeeds in eliminating these problems. In the meantime,
we're all suffering because of a few inconsiderate people. 

Sincerely,
The qsecretary program

P.S. Professor Bernstein has asked me to convey his own apologies to you
if you're someone he knows. I'm sure he'll tell me to accept subsequent
messages from you without confirmation.

If you're replying to a message that Professor Bernstein sent you, the
problem is probably that the return address in your message isn't the
same as the address that Professor Bernstein has on file. I'll let
Professor Bernstein know that he should add your new address.

P.P.S. If you're a legitimate mailing-list manager, and you've received
what appears to be a subscription request from djb@cr.yp.to: That
request is a forgery. Professor Bernstein uses different addresses for
his mailing-list subscriptions. Please remove djb@cr.yp.to from your
mailing list. Do not reply to this message.

Note that high-quality mailing-list software confirms each subscription
request with a secure cryptographic authenticator; supports tracing by
returning a complete copy of each request, including Received fields;
and supports filtering by adding a Mailing-List field to every outgoing
message, including confirmation notices. If your software does not have
these features, upgrade!


------=_NextPart_000_0119_01C2C14E.374DCA50
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Disposition: attachment;
	filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINbTCCAj0w
ggGmAhEAulrJTAU7ktantt9O0FOSDTANBgkqhkiG9w0BAQIFADBfMQswCQYDVQQGEwJVUzEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xNzA1BgNVBAsTLkNsYXNzIDIgUHVibGljIFByaW1hcnkgQ2Vy
dGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNOTYwMTI5MDAwMDAwWhcNMDQwMTA3MjM1OTU5WjBfMQsw
CQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNzA1BgNVBAsTLkNsYXNzIDIgUHVi
bGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwgZ8wDQYJKoZIhvcNAQEBBQADgY0A
MIGJAoGBALZai6MNaiODgGvPOYf0IRMzBkwlou1VEpfFp4C5+oPBIKD6LxUNfKFga355LPoGDzqu
9htvsdL/LyhSX4N9S8R6t/hmH4BU/LfCjllKFFdG0ZqTvkGRA7sVgJNc6+fMCGw/PrNK/P9LbCPV
UIImRBmOI8Nx6hkkRwSedb/IpgAfAgMBAAEwDQYJKoZIhvcNAQECBQADgYEAtgAfk1ekB6dAzmVA
P1Ve7e/6VEmlMNYhfGGH7oOTC7+0M/KYrJ8Gv06ozhSBTMsETljDz1/ufNeab8tBird/gbj/hGHG
J0NlHQzssQAK3Ruku8d4ICiyot02lS7hVE+/YLl3aBGZI+jqUuiqAE5nTruQtUWbRuuOFu/EM1sz
PdUwggNDMIICrKADAgECAhAffl/nA9Hgv5kg3GuJDUsEMA0GCSqGSIb3DQEBBAUAMF8xCzAJBgNV
BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMiBQdWJsaWMg
UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05OTAyMjUwMDAwMDBaFw0wNDAxMDUy
MzU5NTlaMIGtMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1
c3QgTmV0d29yazFJMEcGA1UECxNAVXNlIGlzIHN1YmplY3QgdG8gdGVybXMgYXQgaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL3JwYS1rciAoYyk5OTEmMCQGA1UEAxMdVmVyaVNpZ24gQ2xhc3MgMiBQ
ZXJzb25uZWwgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAKcEbA+icrdKBi741yksNJ2C
vEiRSses+en8uVl4sVXAU1ixz28WO8FJ1cv0bszhzMu1xy5OiKo06bbQW3w+FVc04Ri8/931r2dZ
IArlPeqIikDSmokTKam21dunfuHnNyST/ZR0TXrkMm1M6FwWl6/dktlmihRm5OpaA6g9X/sLAgMB
AAGjgbAwga0wMQYDVR0fBCowKDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMi5j
cmwwEQYJYIZIAYb4QgEBBAQDAgEGMEcGA1UdIARAMD4wPAYLYIZIAYb4RQEHAQEwLTArBggrBgEF
BQcCARYfaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYS1rcjAPBgNVHRMECDAGAQH/AgEBMAsG
A1UdDwQEAwIBBjANBgkqhkiG9w0BAQQFAAOBgQB59xXN6GhRWWv8qaa94B77vPQ/kN/n+u3kVPdh
PVSLBrqXMloeqyzur3Orx13TP4/0zstOSGCiqGC2ON6gpvePKegRrMw5dlA83TlsC/Fa/QhUdt0W
bPcxcLi/CPfJJgaO37svGbG2uLToPEjoJ7GXKSBXA5ybZ/p9QMQ4fxiqmjCCA8QwggMtoAMCAQIC
EQCEzvIOADm1dVXaGYePUu2JMA0GCSqGSIb3DQEBBAUAMIGtMRcwFQYDVQQKEw5WZXJpU2lnbiwg
SW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFJMEcGA1UECxNAVXNlIGlzIHN1
YmplY3QgdG8gdGVybXMgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYS1rciAoYyk5OTEm
MCQGA1UEAxMdVmVyaVNpZ24gQ2xhc3MgMiBQZXJzb25uZWwgQ0EwHhcNOTkwMjI1MDAwMDAwWhcN
MDQwMTA0MjM1OTU5WjCBrDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxSTBHBgNVBAsTQFVzZSBpcyBzdWJqZWN0IHRvIHRlcm1zIGF0IGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEta3IgKGMpOTkxJTAjBgNVBAMTHFZlcmlTaWduIENs
YXNzIDIgRW1wbG95ZWUgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMCK0YdhouowA1Vr
CDbwl/oaVDUkH+h9ncjDc9PYRvWRLdk47ZTXsCZzKt6XUE3/Ihy9cACYDFgqsaRyj6W59y18YOO1
3+l9TiEhYdX8O1TJpAmcuyL5orpwYU+GRqL9BWTsCj+mWHZXuxZzRHzwpQ2XwGym8WMIJbEEF5Wg
jf5/AgMBAAGjgeIwgd8wKQYDVR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDEtMTE4
MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwudmVyaXNpZ24uY29tL1ZTQ2xhc3MySW50LmNy
bDARBglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUF
BwIBFh9odHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhLWtyMA8GA1UdEwQIMAYBAf8CAQAwCwYD
VR0PBAQDAgEGMA0GCSqGSIb3DQEBBAUAA4GBABlGztRrcI5YXIhCNa0WfaUJLKhTkPH2PYbX8M5y
FD0ivPLDM+3U/AWa4GMgdaMb71UZDwZzIQJhrqaeUSt43FvIhIvV17bP1fg+l5ixRIujmI6gS/aY
MZOz8AzdUXbKl+RWRMb7lKFIfSJDzKDGXHlV9WeBG2iYNCREsZjBOiheMIIEGTCCA4KgAwIBAgIQ
da9pAn9XoMlLtvoUDq8LyTANBgkqhkiG9w0BAQQFADCBrDEXMBUGA1UEChMOVmVyaVNpZ24sIElu
Yy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxSTBHBgNVBAsTQFVzZSBpcyBzdWJq
ZWN0IHRvIHRlcm1zIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEta3IgKGMpOTkxJTAj
BgNVBAMTHFZlcmlTaWduIENsYXNzIDIgRW1wbG95ZWUgQ0EwHhcNMDIwMjI3MDAwMDAwWhcNMDMw
MjI3MjM1OTU5WjBtMREwDwYDVQQKEwhWRVJJU0lHTjELMAkGA1UECxMCSFExEzARBgNVBAMTClJl
Y2lwaWVudHMxNjA0BgNVBAMTLXBiYWtlciAoSGFsbGFtLUJha2VyIFBoaWxsaXAsIFZlcmlTaWdu
LCBJbmMuKTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAtcA/okLsFi9brjmDsXQ6+g+R95B1
81Lq1EXkdzhY7XHxQ2QDq0sS2U4j9N1Ic6nHIiMq5dticztWpKdn6CrDx3Ovd5k+PACq/jSQo7NL
tlMJi7fsUrP7pM4izKu4JjSak6wRJUA4x85TSC1PLfd1u8oq16iqNJRhpEJ8VJUMRyECAwEAAaOC
AXgwggF0MAkGA1UdEwQCMAAwWQYDVR0fBFIwUDBOoEygSoZIaHR0cDovL29uc2l0ZWNybC52ZXJp
c2lnbi5jb20vVmVyaVNpZ25JbmNFeGNoYW5nZUVtcGxveWVlcy9MYXRlc3RDUkwuY3JsMAsGA1Ud
DwQEAwIFoDAeBgNVHREEFzAVgRNwYmFrZXJAdmVyaXNpZ24uY29tMIGsBgNVHSAEgaQwgaEwgZ4G
C2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BT
MGIGCCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5j
b3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEE
BAMCB4AwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMA0GCSqGSIb3DQEBBAUAA4GBACCK
+gbdTcJB2wmWF5q8hbnP6slvVFehmjSX1Se+4Ff6a3Uiw8aOQLyNwnYUSOtHe12rTwAtWOhEgXHK
D4XY3tF7cofo5hM8dk8xsj9vV3z3fYARDr4nR2bZblPJ3MGmAFAYKW4pgX4Y6NU4VhAG2Hiuj18/
H4Cc5g5oqJp5dArUMYIC+DCCAvQCAQEwgcEwgawxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8w
HQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUkwRwYDVQQLE0BVc2UgaXMgc3ViamVjdCB0
byB0ZXJtcyBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhLWtyIChjKTk5MSUwIwYDVQQD
ExxWZXJpU2lnbiBDbGFzcyAyIEVtcGxveWVlIENBAhB1r2kCf1egyUu2+hQOrwvJMAkGBSsOAwIa
BQCgggGMMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAzMDEyMTE4
MDgzOVowIwYJKoZIhvcNAQkEMRYEFDAzImeCwWkumcnGeM8UON13A59qMFgGCSqGSIb3DQEJDzFL
MEkwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMAcG
BSsOAwIaMAoGCCqGSIb3DQIFMIHSBgkrBgEEAYI3EAQxgcQwgcEwgawxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUkwRwYDVQQLE0BVc2Ug
aXMgc3ViamVjdCB0byB0ZXJtcyBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhLWtyIChj
KTk5MSUwIwYDVQQDExxWZXJpU2lnbiBDbGFzcyAyIEVtcGxveWVlIENBAhB1r2kCf1egyUu2+hQO
rwvJMA0GCSqGSIb3DQEBAQUABIGAUygU16m8TPmOAxnQOIhrB6foHy1W3Rl8YrIy7QddvlJpl33y
YuHdWjjrnB/ORffb7la+x1HIXiJXM/HNV6Ysg0H0ACy7lgx0kYZIg6ZYHuklRvk7kEiBaIxjxVUt
CvCu16Utaw/2nap0yZlFfiaW/u9cOY4DbaBkokSdCVMEwSAAAAAAAAA=

------=_NextPart_000_0119_01C2C14E.374DCA50--






From owner-ietf@ietf.org  Wed Jan 22 09:55:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26312;
	Wed, 22 Jan 2003 09:55:01 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bMDW-0006ih-00
	for ietf-list@ran.ietf.org; Wed, 22 Jan 2003 09:51:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18b0aZ-0003s5-00
	for ietf@ran.ietf.org; Tue, 21 Jan 2003 10:45:23 -0500
Received: from auemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02746;
	Tue, 21 Jan 2003 10:39:21 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0LFgjg28048;
	Tue, 21 Jan 2003 10:42:45 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ26721V>; Tue, 21 Jan 2003 16:42:43 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BADF97@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Kireeti Kompella <kireeti@juniper.net>
Cc: Bob Braden <braden@ISI.EDU>, iesg@ietf.org, ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Tue, 21 Jan 2003 16:42:17 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

Inline

> -----Original Message-----
> From: Kireeti Kompella [mailto:kireeti@juniper.net]
> Sent: maandag 20 januari 2003 22:49
> To: Wijnen, Bert (Bert)
> Cc: Bob Braden; iesg@ietf.org; ietf@ietf.org
> Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
> 
> 
> Hi Bert,
> 
> On Sat, 18 Jan 2003, Wijnen, Bert (Bert) wrote:
> 
> > Yes they are from the  "IETF Consensus space".
> >
> > Now can you be more specific as to why you do not consider this doc
> > ready for publication?
> 
> There are a large number of nits and typos -- so much so that in my
> opinion, this document should not have been sent to IETF Last Call
> without another round of edits.  However, I will ignore those and
> concentrate on the substance.
> 
It would be great if you can send a list of nits and typos to the
author and copy Scott and Myself, possibly aslo the RFC-Editor.

> I would like to know what the intent is in not granting "the right
> to produce derivative works",
Did Steve Trowbridge not answer the first question?

> and whether the IETF should progress a
> document that is a derivative of IETF protocols with this clause.
> 
I think you meant a colon after "clause" and not a priod?

> The main thrust of the document is the "separation of call and
> connection"; 

> there is one short paragraph that describes this, and
> a reference to an ITU document.

Well, the ITU document should document the details. I don't think
we just want them to copy all their documentation into RFCs, do we?

> In my discussions with people who
> go to the ITU, I didn't hear a clear consensus on the need for this.
>
Well, then they should speak up in ITU I think. The ITU-T SG15 is 
discussing this in their meeting this week, and the technology is
up for consent. Any "people who go to the ITU" (to use your words)
and who do NOT agree with it should then speak up in ITU SG15,
don't you think so?

> An *IETF* document that describes the background, needs and how this
> is to be used would be very useful.  This is especially important as
> the very next paragraph says that separation can be achieved "where
> the call set up request is always accaccompanied by a connection
> request", which (to my naive understanding) hardly is separation.
> 
Why would we need them to replicate their own documentation into an
IETF document?

> Secondly, there is a real paucity of detail in the description and
> use of the new messages: the Call Setup Message refers to the OIF
> UNI document for formating and doesn't say much about when and how
> it is to be used; there is no justification for the format of the
> Call ID (why is there an International Segment, etc.?  Won't IP
> addresses do?  Is this to be used for telephone calls???  My
> recollection is that Fred Baker (then IETF chair) said that using
> CCAMP for telephony was a no-no ....)
> 
I will leave it to the "ITU" folk to answer the details.
But your main point seems to be that you have not seen enough
documentation. ITU-T did a Liason Statement to us, and I believe
even specifically to CCAMP WG (that you co-chair) and so can you
tell me if you read their documentation that they have made
(freely) available to us to check? And after reading that, do
your points still hold. If so, then maybe we (CCAMP) should answer
the Liason Statement and explain to them how and where they should
add more detail and ask specific questions based on what they
document in their "drafts" (or documents) to which they point.

> Call Release can be "sent by any entity of the network".  This surely
> can't be correct.
> 
Will let ITU-folk answer that.

> The Call Capability TLV is completely undocumented beyond the format
> of the TLV.
> 
How about in the documents in OIF and ITU that they point to?

> As someone else pointed out, crankback for CR-LDP has already been
> defined.  Furthermore, this document does not say what procedures
> the sender and receiver must follow, and how crankback is to be
> effected.
>
What do you mean by "has already been defined" ??
And are the procedures not documented in the documents they point to?
 
> The "Additional Error Codes" have absolutely no detail about what
> they mean, when they are to be sent, and what the receiver should
> do with them.  They also use a slew of unidentified acronyms.
> 
They do in the documents they point to.

Bert
> Kireeti.
> 





From owner-ietf@ietf.org  Wed Jan 22 09:55:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26294;
	Wed, 22 Jan 2003 09:55:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bMFQ-0006li-00
	for ietf-list@ran.ietf.org; Wed, 22 Jan 2003 09:53:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18b0lI-00048g-00
	for ietf@ran.ietf.org; Tue, 21 Jan 2003 10:56:28 -0500
Received: from cnri.reston.va.us (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03092
	for <ietf@ietf.org>; Tue, 21 Jan 2003 10:50:26 -0500 (EST)
Received: from BOBLAPTOP.cnri.reston.va.us (cnri-7-94.cnri.reston.va.us [132.151.7.94])
	by cnri.reston.va.us (8.11.6+Sun/8.11.3) with ESMTP id h0LFcJN05648;
	Tue, 21 Jan 2003 10:38:19 -0500 (EST)
Message-Id: <5.1.0.14.2.20030121004500.02090eb8@newcnri.cnri.reston.va.us>
X-Sender: rkahn@newcnri.cnri.reston.va.us
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 21 Jan 2003 00:46:17 -0500
To: "vinton g. cerf" <vinton.g.cerf@wcom.com>,
        "J-F C. (Jefsey)  Morfin" <jefsey@club-internet.fr>,
        pouzin@email.enst.fr
From: Robert Kahn <rkahn@cnri.reston.va.us>
Subject: Re: Cluster Addressing and CIDR
Cc: Jean-Louis.Grange@eurolinc.org,
        "Richard J. Sexton  Ph.D. J.D." <rich@rd.vrx.net>,
        "Rokitansky, Carl-Herbert" <roki@cosy.sbg.ac.at>,
        "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>,
        Bob Braden <braden@ISI.EDU>,
        "Vaudreuil, Greg M (Greg)" <gregv@lucent.com>, ietf@ietf.org,
        internet-history@postel.org, JimFleming@ameritech.net,
        steinle@smartvia.de,
        Elisabeth Porteneuve <Elisabeth.Porteneuve@cetp.ipsl.fr>,
        bortzmeyer@nic.fr, abel@able-towers.com, Simon Higgs <simon@higgs.com>,
        richard.hill@itu.int, k@widgital.com,
        Bruce Young <Bruce@barelyadequate.info>,
        Alexander Svensson <alexander@svensson.de>,
        Joe Baptista <baptista@dot-god.com>,
        David Goldstein <goldstein_david@yahoo.com.au>,
        Joop Teernstra <terastra@terabytz.co.nz>, yjpark@myepark.com
In-Reply-To: <5.1.1.6.2.20030115030238.01720260@pop.wcomnet.com>
References: <5.1.0.14.0.20030115023521.02c2ea00@mail.club-internet.fr>
 <5.1.1.6.2.20030114180456.023bbdd0@pop.wcomnet.com>
 <20030114042113.AD2A0D2A2@ns1.vrx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

Vint,

The internetting terminology was in existence as we wrote the tcp paper in 
1973, but the internetting project got on the books formally in 1974, i 
think. I'd have to do a bit of digging to be sure.

bob

At 03:04 AM 1/15/2003 -0500, vinton g. cerf wrote:
>My first recollection of the documented use of the term "Internet" was in 
>RFC 675 the specification of the Internet Transmission Control Protocol.
>
>ARPA called the project "Internetting" starting in 1973, I believe.
>
>Bob Kahn you know that point for sure.
>
>vint
>
>At 02:59 AM 1/15/2003 +0100, J-F C. (Jefsey)  Morfin wrote:
> >PS. Vint, when was the name Internet used for the first time? When you 
> say 'multiple net systems' did  you refer by then to mutiple networks, to 
> multiple technologies or both?
>
>Vint Cerf
>SVP Architecture & Technology
>WorldCom
>22001 Loudoun County Parkway, F2-4115
>Ashburn, VA 20147
>703 886 1690 (v806 1690)
>703 886 0047 fax






From owner-ietf@ietf.org  Wed Jan 22 13:18:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02800;
	Wed, 22 Jan 2003 13:18:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bPQr-0006BZ-00
	for ietf-list@ran.ietf.org; Wed, 22 Jan 2003 13:17:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bPPv-00069m-00
	for ietf@ran.ietf.org; Wed, 22 Jan 2003 13:16:03 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02638;
	Wed, 22 Jan 2003 13:09:46 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.7.Beta0/8.12.7.Beta0) with ESMTP id h0MIDCQY007903;
	Wed, 22 Jan 2003 13:13:12 -0500
Message-Id: <200301221813.h0MIDCQY007903@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: Dan Berrnstein deserves what he gets. FW: qsecretary notice 
In-Reply-To: Your message of "Tue, 21 Jan 2003 10:30:18 PST."
             <CE541259607DE94CA2A23816FB49F4A3954641@vhqpostal6.verisign.com> 
References: <CE541259607DE94CA2A23816FB49F4A3954641@vhqpostal6.verisign.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-227804608P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 22 Jan 2003 13:13:12 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Tue, 21 Jan 2003 10:30:18 PST, "Hallam-Baker, Phillip" <pbaker@verisign.com>  said:

> [*] Its only an assistant professorship that by European lights
> only ranks him as a mere lecturer. The fact that he has to refer

And by common US practice, he has a PhD and is accorded the title Doctor.
At the place he has a professorship, the customary usage is to use the
title.  Also, in the US, there is usually a distinction made between
an assistant professor and an adjunct professor and a lecturer/instructor.




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

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

iD8DBQE+Lt84cC3lWbTT17ARAvx0AKDmHPYtgLsjUfRzefhR1MaPSFcjrgCg/JHB
WTwMFAJhvMD11YOGUac8Y1M=
=MvPu
-----END PGP SIGNATURE-----

--==_Exmh_-227804608P--



From owner-ietf@ietf.org  Wed Jan 22 16:33:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08031;
	Wed, 22 Jan 2003 16:33:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bSTY-0006Hb-00
	for ietf-list@ran.ietf.org; Wed, 22 Jan 2003 16:32:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bSSa-0006FK-00
	for ietf@ran.ietf.org; Wed, 22 Jan 2003 16:31:00 -0500
Received: from lightwave.chromisys.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07707;
	Wed, 22 Jan 2003 16:24:39 -0500 (EST)
Received: by lightwave.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <4GJZ143K>; Wed, 22 Jan 2003 13:28:03 -0800
Message-ID: <9D42C6E086250248810DCADA39CE7EFC972169@nimbus>
From: John Drake <jdrake@calient.net>
To: "'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>,
        Kireeti Kompella
	 <kireeti@juniper.net>
Cc: Bob Braden <braden@ISI.EDU>, iesg@ietf.org, ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Wed, 22 Jan 2003 13:28:02 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Bert,

I don't recall a SG15 Liason of the form 'Btw, we're planning to change a
couple of your protocols (CR-LDP, RSVP-TE), and we hope you don't mind".  

More importantly, do you really think it's a good idea to allow other
organizations to change the IETF's protocols?  As Jerry Ash pointed out,
that's the same as having the IETF develop its own version of G.709.  I
think it would have been a much better idea for the ITU to send G.7713 to
the IETF (CCAMP) and ask them to develop protocols to support it.

Thanks,

John
-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
Sent: Tuesday, January 21, 2003 7:42 AM
To: Kireeti Kompella
Cc: Bob Braden; iesg@ietf.org; ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational


Inline

> -----Original Message-----
> From: Kireeti Kompella [mailto:kireeti@juniper.net]
> Sent: maandag 20 januari 2003 22:49
> To: Wijnen, Bert (Bert)
> Cc: Bob Braden; iesg@ietf.org; ietf@ietf.org
> Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
> 
> 
> Hi Bert,
> 
> On Sat, 18 Jan 2003, Wijnen, Bert (Bert) wrote:
> 
> > Yes they are from the  "IETF Consensus space".
> >
> > Now can you be more specific as to why you do not consider this doc
> > ready for publication?
> 
> There are a large number of nits and typos -- so much so that in my
> opinion, this document should not have been sent to IETF Last Call
> without another round of edits.  However, I will ignore those and
> concentrate on the substance.
> 
It would be great if you can send a list of nits and typos to the
author and copy Scott and Myself, possibly aslo the RFC-Editor.

> I would like to know what the intent is in not granting "the right
> to produce derivative works",
Did Steve Trowbridge not answer the first question?

> and whether the IETF should progress a
> document that is a derivative of IETF protocols with this clause.
> 
I think you meant a colon after "clause" and not a priod?

> The main thrust of the document is the "separation of call and
> connection"; 

> there is one short paragraph that describes this, and
> a reference to an ITU document.

Well, the ITU document should document the details. I don't think
we just want them to copy all their documentation into RFCs, do we?

> In my discussions with people who
> go to the ITU, I didn't hear a clear consensus on the need for this.
>
Well, then they should speak up in ITU I think. The ITU-T SG15 is 
discussing this in their meeting this week, and the technology is
up for consent. Any "people who go to the ITU" (to use your words)
and who do NOT agree with it should then speak up in ITU SG15,
don't you think so?

> An *IETF* document that describes the background, needs and how this
> is to be used would be very useful.  This is especially important as
> the very next paragraph says that separation can be achieved "where
> the call set up request is always accaccompanied by a connection
> request", which (to my naive understanding) hardly is separation.
> 
Why would we need them to replicate their own documentation into an
IETF document?

> Secondly, there is a real paucity of detail in the description and
> use of the new messages: the Call Setup Message refers to the OIF
> UNI document for formating and doesn't say much about when and how
> it is to be used; there is no justification for the format of the
> Call ID (why is there an International Segment, etc.?  Won't IP
> addresses do?  Is this to be used for telephone calls???  My
> recollection is that Fred Baker (then IETF chair) said that using
> CCAMP for telephony was a no-no ....)
> 
I will leave it to the "ITU" folk to answer the details.
But your main point seems to be that you have not seen enough
documentation. ITU-T did a Liason Statement to us, and I believe
even specifically to CCAMP WG (that you co-chair) and so can you
tell me if you read their documentation that they have made
(freely) available to us to check? And after reading that, do
your points still hold. If so, then maybe we (CCAMP) should answer
the Liason Statement and explain to them how and where they should
add more detail and ask specific questions based on what they
document in their "drafts" (or documents) to which they point.

> Call Release can be "sent by any entity of the network".  This surely
> can't be correct.
> 
Will let ITU-folk answer that.

> The Call Capability TLV is completely undocumented beyond the format
> of the TLV.
> 
How about in the documents in OIF and ITU that they point to?

> As someone else pointed out, crankback for CR-LDP has already been
> defined.  Furthermore, this document does not say what procedures
> the sender and receiver must follow, and how crankback is to be
> effected.
>
What do you mean by "has already been defined" ??
And are the procedures not documented in the documents they point to?
 
> The "Additional Error Codes" have absolutely no detail about what
> they mean, when they are to be sent, and what the receiver should
> do with them.  They also use a slew of unidentified acronyms.
> 
They do in the documents they point to.

Bert
> Kireeti.
> 





From owner-ietf@ietf.org  Wed Jan 22 16:44:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08487;
	Wed, 22 Jan 2003 16:44:38 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bSi4-0006xi-00
	for ietf-list@ran.ietf.org; Wed, 22 Jan 2003 16:47:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bShE-0006vF-00
	for ietf@ran.ietf.org; Wed, 22 Jan 2003 16:46:08 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08247
	for <ietf@ietf.org>; Wed, 22 Jan 2003 16:39:47 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h0MLhEb20886
	for <ietf@ietf.org>; Wed, 22 Jan 2003 13:43:14 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id VAA00940
	for ietf@ietf.org; Wed, 22 Jan 2003 21:43:14 GMT
Date: Wed, 22 Jan 2003 21:43:14 GMT
Message-Id: <200301222143.VAA00940@gra.isi.edu>
To: ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



Not liking to create unnecessary noise on large public lists (really!),
I trimmed the IETF off the following message. Bert W. has suggested that
this was inappropriate, as the issue is a general IETF issue.

Bob Braden for the RFC Editor

----- Begin Included Message -----

From braden@ISI.EDU  Tue Jan 21 13:59:39 2003
From: Bob Braden <braden@ISI.EDU>
Date: Tue, 21 Jan 2003 21:59:32 GMT
To: bwijnen@lucent.com, kireeti@juniper.net
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Cc: braden@ISI.EDU, iesg@ietf.org
X-AntiVirus: scanned by AMaViS 0.2.1

  *> 
  *> Hi Bert,
  *> 
  *> On Sat, 18 Jan 2003, Wijnen, Bert (Bert) wrote:
  *> 
  *> > Yes they are from the  "IETF Consensus space".
  *> >
  *> > Now can you be more specific as to why you do not consider this doc
  *> > ready for publication?

Just for the record, although I am not technically competant to pass
detailed judgment, many of Mr. Kompella's comments fit my prejudices
about this document.

  *> 
  *> There are a large number of nits and typos -- so much so that in my
  *> opinion, this document should not have been sent to IETF Last Call
  *> without another round of edits.  However, I will ignore those and
  *> concentrate on the substance.

This saddens me.  I will go reread it.  The RFC Editor DID go one round
with the author (you should have seen the FIRST version!), and we
judged that the result was "good enough".  We are now both pleased and
embarrassed when someone from the community tells us that it was
NOT good enough!  But we do appreciate such feedback, really.  ;-)

...

  *> 
  *> The main thrust of the document is the "separation of call and
  *> connection"; there is one short paragraph that describes this, and
  *> a reference to an ITU document.  In my discussions with people who
  *> go to the ITU, I didn't hear a clear consensus on the need for this.

Our gripe was that the document did not even TRY to explain what this
distinction MEANS.

  *> An *IETF* document that describes the background, needs and how this
  *> is to be used would be very useful.  This is especially important as
  *> the very next paragraph says that separation can be achieved "where
  *> the call set up request is always accaccompanied by a connection
  *> request", which (to my naive understanding) hardly is separation.
  *> 

This is an important and sticky point... what are the IETF's rights and
duties with respect to the work of other standards bodies?  One of the
reasons the RFC Editor did not press harder was that the protocol was
essentially a fait accompli and presumably documented completely and
clearly by ITU-T.  The only purpose of the RFC was to document the IANA
registration, so fragmentary description without explanation seemed all
we could expect.  The RFC Editor rather hates to publish documents like
this, but of course there are political realities to be served, and we
understand Bert's point about duplication.

Bob Braden for the RFC Editor
 


----- End Included Message -----




From owner-ietf@ietf.org  Wed Jan 22 17:21:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09662;
	Wed, 22 Jan 2003 17:21:21 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bTGw-00043q-00
	for ietf-list@ran.ietf.org; Wed, 22 Jan 2003 17:23:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bTG8-0001wh-00
	for ietf@ran.ietf.org; Wed, 22 Jan 2003 17:22:12 -0500
Received: from cobalt.sopac.org.fj (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09436;
	Wed, 22 Jan 2003 17:15:37 -0500 (EST)
Received: by cobalt.sopac.org.fj (Postfix, from userid 416)
	id 7CC2117C17; Wed, 22 Jan 2003 22:18:39 +0000 (UTC)
Received: from bigiron.sopac.org.fj (unknown [10.0.0.180])
	by cobalt.sopac.org.fj (Postfix) with ESMTP
	id 20D1A17C04; Wed, 22 Jan 2003 22:18:39 +0000 (UTC)
Received: by BIGIRON with Internet Mail Service (5.5.2650.21)
	id <CYRCTTL3>; Thu, 23 Jan 2003 10:18:55 +1200
Message-ID: <F12ECEA0435AD211B5280008C7ACBC85016B47B1@BIGIRON>
From: Franck Martin <Franck@sopac.org>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, ietf@ietf.org,
        iesg@ietf.org, namedroppers@ops.ietf.org
Subject: RE: Dan Berrnstein deserves what he gets. FW: qsecretary notice
Date: Thu, 23 Jan 2003 10:18:45 +1200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
MIME-Version: 1.0
Content-Type: multipart/signed;
	micalg=SHA1;
	boundary="----=_NextPart_000_0026_01C2C2C8.D7AB7120";
	protocol="application/x-pkcs7-signature"
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

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

Why don't he uses TMDA.sourceforge.net?

Franck Martin
ICT Specialist - EU/EDF8 Project


> -----Original Message-----
> From: Hallam-Baker, Phillip [mailto:pbaker@verisign.com]
> Sent: Wednesday, 22 January 2003 6:30 
> To: ietf@ietf.org; iesg@ietf.org; namedroppers@ops.ietf.org
> Subject: Dan Berrnstein deserves what he gets. FW: qsecretary notice
> 
> 
> Bernstein is a whiner who deserves no sympathy from anyone.
> 
> In order to avoid cluttering up his inbox with SPAM he has
> one of those annoying callback systems. Only thing is that the
> self-centered clod can't be bothered to put people who reply into
> a whitelist.
> 

------=_NextPart_000_0026_01C2C2C8.D7AB7120
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Disposition: attachment;
	filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKVzCCBSQw
ggSNoAMCAQICAQIwDQYJKoZIhvcNAQEFBQAwgYkxCzAJBgNVBAYTAkZKMQ0wCwYDVQQIEwRGaWpp
MQ0wCwYDVQQHEwRTdXZhMQ4wDAYDVQQKEwVTT1BBQzEMMAoGA1UECxMDSVRVMRYwFAYDVQQDEw1T
T1BBQyBSb290IENBMSYwJAYJKoZIhvcNAQkBFhdhZG1pbmlzdHJhdG9yQHNvcGFjLm9yZzAeFw0w
MjA1MDkyMjEwMDZaFw0wMzA1MDkyMjEwMDZaMIGFMQswCQYDVQQGEwJGSjENMAsGA1UECBMERmlq
aTENMAsGA1UEBxMEU3V2YTEOMAwGA1UEChMFU09QQUMxDDAKBgNVBAsTA0lUVTEZMBcGA1UEAxQQ
ZnJhbmNrQHNvcGFjLm9yZzEfMB0GCSqGSIb3DQEJARYQZnJhbmNrQHNvcGFjLm9yZzCBnzANBgkq
hkiG9w0BAQEFAAOBjQAwgYkCgYEA0soRghfaBJ3B6+yxHxEkHbtCF4a/ZNNUs9Sn38pBwXT0D/R6
iqhC+CCxjO/7mCe4F6pRZMTuN0Rv84ZMa77aNDBcVWiSsssoUS+64yxTefwnq3+gifNO7mVxE8yr
a/LvvwKIGmr0R0Hz8kTidyUzcoQROFHfD27FJpjEsVFtOmcCAwEAAaOCApwwggKYMAkGA1UdEwQC
MAAwPwYJYIZIAYb4QgENBDIWMENlcnRpZmljYXRlIGlzc3VlZCBieSBodHRwczovL3d3dy5zb3Bh
Yy5vcmcvc3NsLzAdBgNVHQ4EFgQUukKEVhwnVd3F4n9WW26fA4c6wBEwgbYGA1UdIwSBrjCBq4AU
OqATltJqhrl/LVS+UDvT8aTsUa+hgY+kgYwwgYkxCzAJBgNVBAYTAkZKMQ0wCwYDVQQIEwRGaWpp
MQ0wCwYDVQQHEwRTdXZhMQ4wDAYDVQQKEwVTT1BBQzEMMAoGA1UECxMDSVRVMRYwFAYDVQQDEw1T
T1BBQyBSb290IENBMSYwJAYJKoZIhvcNAQkBFhdhZG1pbmlzdHJhdG9yQHNvcGFjLm9yZ4IBADAp
BglghkgBhvhCAQIEHBYaaHR0cHM6Ly93d3cuc29wYWMub3JnL3NzbC8wNQYJYIZIAYb4QgEEBCgW
Jmh0dHBzOi8vd3d3LnNvcGFjLm9yZy9zc2wvc29wYWMtY2EuY3JsMDkGCWCGSAGG+EIBAwQsFipo
dHRwczovL3d3dy5zb3BhYy5vcmcvc3NsL3Jldm9jYXRpb24uaHRtbD8wNgYJYIZIAYb4QgEHBCkW
J2h0dHBzOi8vd3d3LnNvcGFjLm9yZy9zc2wvcmVuZXdhbC5odG1sPzA0BglghkgBhvhCAQgEJxYl
aHR0cHM6Ly93d3cuc29wYWMub3JnL3NzbC9wb2xpY3kuaHRtbDAuBgNVHRIEJzAlhiNodHRwczov
L3d3dy5zb3BhYy5vcmcvc3NsL3NvcGFjLmNydDA3BgNVHR8EMDAuMCygKqAohiZodHRwczovL3d3
dy5zb3BhYy5vcmcvc3NsL3NvcGFjLWNhLmNybDANBgkqhkiG9w0BAQUFAAOBgQB+4WRRdMulWDp2
MNawJy9mksHVGL2l5BN6eBOcRcoi1cLgOvISZwoAp7C/vE/37lQRqbHcHATn4FU+bGjuxMu/YBYH
ax5TYWV9G3/Gc0HA4UhPuvDLS1Z7woFsI5Ra2mJGyJgE8IWxt2HfRjR5fBEY/+PHVumXaRyxi6Fj
em+AaTCCBSswggSUoAMCAQICAQAwDQYJKoZIhvcNAQEFBQAwgYkxCzAJBgNVBAYTAkZKMQ0wCwYD
VQQIEwRGaWppMQ0wCwYDVQQHEwRTdXZhMQ4wDAYDVQQKEwVTT1BBQzEMMAoGA1UECxMDSVRVMRYw
FAYDVQQDEw1TT1BBQyBSb290IENBMSYwJAYJKoZIhvcNAQkBFhdhZG1pbmlzdHJhdG9yQHNvcGFj
Lm9yZzAeFw0wMjA1MDkwNDUxMDlaFw0xMjA1MDYwNDUxMDlaMIGJMQswCQYDVQQGEwJGSjENMAsG
A1UECBMERmlqaTENMAsGA1UEBxMEU3V2YTEOMAwGA1UEChMFU09QQUMxDDAKBgNVBAsTA0lUVTEW
MBQGA1UEAxMNU09QQUMgUm9vdCBDQTEmMCQGCSqGSIb3DQEJARYXYWRtaW5pc3RyYXRvckBzb3Bh
Yy5vcmcwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJ/G829ctvoXf2qH0/THNKgdgTHjqOoJ
8M6B4jDu/t5kv3EQFXz65b8bAt3DnWtL29gSgmZ2Og4f5J1GjmqFRlzH8BJFGArWi6MmLuLmSvl3
ltM211jm66wxU+ePB2v4lledogiLRkIlAlZzzpLrdm6SlWPoxrZUE4juSKucSK/dAgMBAAGjggKf
MIICmzAdBgNVHQ4EFgQUOqATltJqhrl/LVS+UDvT8aTsUa8wgbYGA1UdIwSBrjCBq4AUOqATltJq
hrl/LVS+UDvT8aTsUa+hgY+kgYwwgYkxCzAJBgNVBAYTAkZKMQ0wCwYDVQQIEwRGaWppMQ0wCwYD
VQQHEwRTdXZhMQ4wDAYDVQQKEwVTT1BBQzEMMAoGA1UECxMDSVRVMRYwFAYDVQQDEw1TT1BBQyBS
b290IENBMSYwJAYJKoZIhvcNAQkBFhdhZG1pbmlzdHJhdG9yQHNvcGFjLm9yZ4IBADAMBgNVHRME
BTADAQH/MD8GCWCGSAGG+EIBDQQyFjBDZXJ0aWZpY2F0ZSBpc3N1ZWQgYnkgaHR0cHM6Ly93d3cu
c29wYWMub3JnL3NzbC8wKQYJYIZIAYb4QgECBBwWGmh0dHBzOi8vd3d3LnNvcGFjLm9yZy9zc2wv
MDUGCWCGSAGG+EIBBAQoFiZodHRwczovL3d3dy5zb3BhYy5vcmcvc3NsL3NvcGFjLWNhLmNybDA5
BglghkgBhvhCAQMELBYqaHR0cHM6Ly93d3cuc29wYWMub3JnL3NzbC9yZXZvY2F0aW9uLmh0bWw/
MDYGCWCGSAGG+EIBBwQpFidodHRwczovL3d3dy5zb3BhYy5vcmcvc3NsL3JlbmV3YWwuaHRtbD8w
NAYJYIZIAYb4QgEIBCcWJWh0dHBzOi8vd3d3LnNvcGFjLm9yZy9zc2wvcG9saWN5Lmh0bWwwLgYD
VR0SBCcwJYYjaHR0cHM6Ly93d3cuc29wYWMub3JnL3NzbC9zb3BhYy5jcnQwNwYDVR0fBDAwLjAs
oCqgKIYmaHR0cHM6Ly93d3cuc29wYWMub3JnL3NzbC9zb3BhYy1jYS5jcmwwDQYJKoZIhvcNAQEF
BQADgYEAVgR9VJL3PAR6ljg8PVSyGIJ+t+yvhtU6q6cEuONs1EILhhLae4XmajjVeXud9t/U+jNm
4IZi3XqWymeLV1oj/exU7Lcnog5CeA9QirpH+xlzHd2ByMW1RvbSmhgsbv8nQ7Y21Foxdx3lkAfi
V2ya75RUFFATHjfddz5R2osj7yAxggKUMIICkAIBATCBjzCBiTELMAkGA1UEBhMCRkoxDTALBgNV
BAgTBEZpamkxDTALBgNVBAcTBFN1dmExDjAMBgNVBAoTBVNPUEFDMQwwCgYDVQQLEwNJVFUxFjAU
BgNVBAMTDVNPUEFDIFJvb3QgQ0ExJjAkBgkqhkiG9w0BCQEWF2FkbWluaXN0cmF0b3JAc29wYWMu
b3JnAgECMAkGBSsOAwIaBQCgggFaMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTAzMDEyMjIyMTg1OFowIwYJKoZIhvcNAQkEMRYEFPr7n8cxZ1yVRFoPjXA3F3N6o6gz
MFgGCSqGSIb3DQEJDzFLMEkwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIHMA0G
CCqGSIb3DQMCAgEoMAcGBSsOAwIaMAoGCCqGSIb3DQIFMIGgBgkrBgEEAYI3EAQxgZIwgY8wgYkx
CzAJBgNVBAYTAkZKMQ0wCwYDVQQIEwRGaWppMQ0wCwYDVQQHEwRTdXZhMQ4wDAYDVQQKEwVTT1BB
QzEMMAoGA1UECxMDSVRVMRYwFAYDVQQDEw1TT1BBQyBSb290IENBMSYwJAYJKoZIhvcNAQkBFhdh
ZG1pbmlzdHJhdG9yQHNvcGFjLm9yZwIBAjANBgkqhkiG9w0BAQEFAASBgK9Ps5lASM2xRPzZSaV9
H+28MXw1Y3ILTXvTblgkyQpDai/OB3+LovQA1f9AopSij4p1Vo5jJap0obSi7bMJTWKrwmwGlNab
6p2wUrkfojsm+2+DIFH4dRypmmXQZqf/cixwzOSOzWqQBZ4WU8wxyma8ExQRJM5Qd3V6MWUqSOkc
AAAAAAAA

------=_NextPart_000_0026_01C2C2C8.D7AB7120--




From owner-ietf@ietf.org  Wed Jan 22 21:58:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14959;
	Wed, 22 Jan 2003 21:58:38 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bXTF-0000QE-00
	for ietf-list@ran.ietf.org; Wed, 22 Jan 2003 21:52:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bXSr-0000Op-00
	for ietf@ran.ietf.org; Wed, 22 Jan 2003 21:51:37 -0500
Received: from lightwave.chromisys.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14691;
	Wed, 22 Jan 2003 21:45:12 -0500 (EST)
Received: by lightwave.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <4GJZ149G>; Wed, 22 Jan 2003 18:48:35 -0800
Message-ID: <9D42C6E086250248810DCADA39CE7EFC972171@nimbus>
From: John Drake <jdrake@calient.net>
To: "'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>,
        Kireeti Kompella
	 <kireeti@juniper.net>
Cc: Bob Braden <braden@ISI.EDU>, iesg@ietf.org, ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Wed, 22 Jan 2003 18:48:34 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk



In spite of the subject line my comments are primarily on
draft-lin-ccamp-gmpls-ason-rsvpte-04.txt               


-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
Sent: Wednesday, January 22, 2003 4:19 PM
To: John Drake; Kireeti Kompella
Cc: Bob Braden; iesg@ietf.org; ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational


Inline

> -----Original Message-----
> From: John Drake [mailto:jdrake@calient.net]
> Sent: woensdag 22 januari 2003 22:28
> To: 'Wijnen, Bert (Bert)'; Kireeti Kompella
> Cc: Bob Braden; iesg@ietf.org; ietf@ietf.org
> Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
> 
> 
> Bert,
> 
> I don't recall a SG15 Liason of the form 'Btw, we're planning 
> to change a couple of your protocols (CR-LDP, RSVP-TE),
> and we hope you don't mind".  
> 
Well... they did not word it as you are doing, but... the LIASON
statements that have been sent to CCAMP and that have been available
on the IETF web pages DO point to documents where that is described.

Also... I believe that an ITU SG-15 person was speakeing at every
CCAMP WG meeting since London or so to talk about the things they
were doing.

So don't give me the crap that the CCAMP WG members are not aware
of this for quite a long time. If you are not aware, then I can
only conclude that you have payed no attention.


JD:  The last liason statement on this topic that I've seen on the
IETF liason web page is:  http://www.ietf.org/IESG/LIAISON/ITU-OIF.html
end JD:

> More importantly, do you really think it's a good idea to allow
> other organizations to change the IETF's protocols?

Now... the question is: are they indeed CHANGING an IETF protocol?


JD:  They wish to deprecate ResvErr and ResvTear, as well as the FILTER_SPEC
and LABEL objects.  They wish to use the Generalized UNI object to identify
the RSVP session endpoints and the parameters of the LSP.  
end JD:

First, we have defined a few namespaces (for RSVP and for LDP) 
so that the protocols are extensible. We have split up those
name spaces, such that people or organisations can ask for 
code points in IETF-consensus-required section or in a FCFS section
(First Come First Served, formally no documentation required I think)

As you can see, in the RSVP space, there is a lot of FCFS code points.
For the RSVP solution, they (ITU/OIF) are mainly asking for code
points in the FCFS space. So what was our intention for that namespace
when we defined it?

My feeling is from all the discussions, that the biggest problem
is not so much on how RSVP or CR-LDP code points are added (the 
protocol is still the same, there are just more Objects and/or TLVs).


JD:  See my comment above.  


I'll admit that some comments have been received on if the way the
TLVs and Objects/Classes have been organized is very clean or ideal,
but that seems also a bit of a detail to me.

Rather the problem is that they talk about and want to provide:
- call and connection separation
- that they add NSAP addresses
- that they define a UNI interface (which we, IETF forcefully
  rejected to be worked on in IETF a few years back)

Now... if those are the 3 issues, then I think we have only seen
a few people object. But the objections are more of the form
that people don't like this (which is OK, this is one of the
reasons why we did not want to do this work in IETF), but I 
still fail to see any mention of the real technical problems
of what they are doing. But then, I am not a control-plabe
or data-plane (or MPLS or GMPLS for that matter) expert.

> As Jerry Ash pointed out, that's the same as having the IETF
> develop its own version of G.709.  I think it would have been
> a much better idea for the ITU to send G.7713 to the IETF
> (CCAMP) and ask them to develop protocols to support it.
> 
I believe that at least for teh UNI, they have done so in
the past and we told them to go away.

I believe that NSAP was also disliked and we did send them away.
I am not 100% clear on call and connection separation.


JD:  You're confusing a couple of different 'theys'.  UNI and NSAP
were OIF, and they're back:
http://www.ietf.org/internet-drafts/draft-bala-uni-ldp-rsvp-extensions-04.tx
t
What you're calling call and connection separation is actually a bit more
than just that, as described in G.7713, and that 'they' is ITU.  You didn't
actually address my point, which is why is it okay for ITU to change RSVP
when
it's not okay for the IETF to change G.709.
end JD:


Hope this can help to bring the discussion to either consensus
to approve, or to show us what the real technical issues are
by those who have raised objections sofar.


JD:  I don't see any reason to deprecate ResvErr and ResvTear, or
FILTER_SPEC
and LABEL objects.  

I don't see any reason to use the Generalized UNI object to identify
the RSVP session endpoints and the parameters of the LSP.

I don't see any reason to use the Generalized UNI object to
support Soft Permanent Connections, since as the draft acknowledges,
GMPLS signalling has an existing mechanism.

As the draft acknowledges, the details of call/connection separation
have not been completely thought out, so why is a call identifier introduced
when we don't know if it is either necessary or sufficient?  I also think
its format is unnessarilly complex.

The processing of a call is said to be different than that of a connection,
but these differences are not detailed.

And by the way, if you read G.7713.2, it doesn't have any more explanation
for
how these TLVs are used than draft-lin-ccamp-gmpls-ason-rsvpte-04.txt does,
and
I think that is my primary objection to both.
end JD: 

Bert
> Thanks,
> 
> John



From owner-ietf@ietf.org  Thu Jan 23 03:30:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29875;
	Thu, 23 Jan 2003 03:30:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bciO-0001H0-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 03:28:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bchZ-0001Fm-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 03:27:09 -0500
Received: from hoemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29800;
	Thu, 23 Jan 2003 03:20:40 -0500 (EST)
Received: from nj7460exch002h.wins.lucent.com (h135-17-42-35.lucent.com [135.17.42.35])
	by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0N8O5A06789;
	Thu, 23 Jan 2003 03:24:05 -0500 (EST)
Received: by nj7460exch002h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YSRT0RKM>; Thu, 23 Jan 2003 03:24:05 -0500
Message-ID: <D3F8FD817CC7DA408AEB2CAC631C042A98E5F3@nj7460exch012u.ho.lucent.com>
From: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)"
	 <sob@harvard.edu>,
        "'iesg@ietf.org'" <iesg@ietf.org>, "'ietf@ietf.org'"
	 <ietf@ietf.org>,
        "'kireeti@juniper.net'" <kireeti@juniper.net>
Cc: "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Malcolm Betts (E-mail)"
	 <betts01@nortelnetworks.com>,
        "Stephen Shew (E-mail)"
	 <sdshew@nortelnetworks.com>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Trowbridge, Stephen J (Steve)" <sjtrowbr@ihmail.ih.lucent.com>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 03:24:04 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

Please see below for some responses...


-----Original Message-----
From: John Drake [mailto:jdrake@calient.net]
Sent: donderdag 23 januari 2003 3:49
To: 'Wijnen, Bert (Bert)'; Kireeti Kompella
Cc: Bob Braden; iesg@ietf.org; ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational




In spite of the subject line my comments are primarily on
draft-lin-ccamp-gmpls-ason-rsvpte-04.txt               


-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
Sent: Wednesday, January 22, 2003 4:19 PM
To: John Drake; Kireeti Kompella
Cc: Bob Braden; iesg@ietf.org; ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational


Inline

> -----Original Message-----
> From: John Drake [mailto:jdrake@calient.net]
> Sent: woensdag 22 januari 2003 22:28
> To: 'Wijnen, Bert (Bert)'; Kireeti Kompella
> Cc: Bob Braden; iesg@ietf.org; ietf@ietf.org
> Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
> 
> 
> Bert,
> 
> I don't recall a SG15 Liason of the form 'Btw, we're planning 
> to change a couple of your protocols (CR-LDP, RSVP-TE),
> and we hope you don't mind".  
> 
Well... they did not word it as you are doing, but... the LIASON
statements that have been sent to CCAMP and that have been available
on the IETF web pages DO point to documents where that is described.

Also... I believe that an ITU SG-15 person was speakeing at every
CCAMP WG meeting since London or so to talk about the things they
were doing.

So don't give me the crap that the CCAMP WG members are not aware
of this for quite a long time. If you are not aware, then I can
only conclude that you have payed no attention.


JD:  The last liason statement on this topic that I've seen on the
IETF liason web page is:  http://www.ietf.org/IESG/LIAISON/ITU-OIF.html
end JD:

<zhi>Kam sent out an email that points to the liaisons. Also Wesam and Steve provides an update at many meetings. Let's not dwell on this issue anymore...</zhi>


> More importantly, do you really think it's a good idea to allow
> other organizations to change the IETF's protocols?

Now... the question is: are they indeed CHANGING an IETF protocol?


JD:  They wish to deprecate ResvErr and ResvTear, as well as the FILTER_SPEC
and LABEL objects.  They wish to use the Generalized UNI object to identify
the RSVP session endpoints and the parameters of the LSP.  
end JD:

<zhi> Where do you see that we deprecate ResvErr and ResvTear? (for the record: these are not deprecated)
Where do you see that we deprecate FILTER_SPEC and LABEL objects? (for the record: these are not deprecated)
Also, where do you see that we wish to identify the RSVP session endpoints with GENERALIZED_UNI? (for the record: the RSVP session is still SESSION object)
</zhi>


First, we have defined a few namespaces (for RSVP and for LDP) 
so that the protocols are extensible. We have split up those
name spaces, such that people or organisations can ask for 
code points in IETF-consensus-required section or in a FCFS section
(First Come First Served, formally no documentation required I think)

As you can see, in the RSVP space, there is a lot of FCFS code points.
For the RSVP solution, they (ITU/OIF) are mainly asking for code
points in the FCFS space. So what was our intention for that namespace
when we defined it?

My feeling is from all the discussions, that the biggest problem
is not so much on how RSVP or CR-LDP code points are added (the 
protocol is still the same, there are just more Objects and/or TLVs).


JD:  See my comment above.  


I'll admit that some comments have been received on if the way the
TLVs and Objects/Classes have been organized is very clean or ideal,
but that seems also a bit of a detail to me.

Rather the problem is that they talk about and want to provide:
- call and connection separation
- that they add NSAP addresses
- that they define a UNI interface (which we, IETF forcefully
  rejected to be worked on in IETF a few years back)

Now... if those are the 3 issues, then I think we have only seen
a few people object. But the objections are more of the form
that people don't like this (which is OK, this is one of the
reasons why we did not want to do this work in IETF), but I 
still fail to see any mention of the real technical problems
of what they are doing. But then, I am not a control-plabe
or data-plane (or MPLS or GMPLS for that matter) expert.

> As Jerry Ash pointed out, that's the same as having the IETF
> develop its own version of G.709.  I think it would have been
> a much better idea for the ITU to send G.7713 to the IETF
> (CCAMP) and ask them to develop protocols to support it.
> 
I believe that at least for teh UNI, they have done so in
the past and we told them to go away.

I believe that NSAP was also disliked and we did send them away.
I am not 100% clear on call and connection separation.


JD:  You're confusing a couple of different 'theys'.  UNI and NSAP
were OIF, and they're back:
http://www.ietf.org/internet-drafts/draft-bala-uni-ldp-rsvp-extensions-04.tx
t
What you're calling call and connection separation is actually a bit more
than just that, as described in G.7713, and that 'they' is ITU.  You didn't
actually address my point, which is why is it okay for ITU to change RSVP
when
it's not okay for the IETF to change G.709.
end JD:

<zhi>The statement above about G.709 is irrelevant to the discussion. In terms of sending G.7713 to IETF and asking to develop protocol...that's what was done. Back on 2001 discussions were started on what requirements and architectures are needed to support G.8080. Individuals (who happens to participate in both IETF and ITU) then started submitting protocol extensions. People either choose to ignore these or expressed opposition to making these extensions simply because it went beyond the traditional IP services.</zhi>
 

Hope this can help to bring the discussion to either consensus
to approve, or to show us what the real technical issues are
by those who have raised objections sofar.


JD:  I don't see any reason to deprecate ResvErr and ResvTear, or
FILTER_SPEC
and LABEL objects.  

<zhi>See above</zhi>

I don't see any reason to use the Generalized UNI object to identify
the RSVP session endpoints and the parameters of the LSP.

<zhi>see above</zhi>

I don't see any reason to use the Generalized UNI object to
support Soft Permanent Connections, since as the draft acknowledges,
GMPLS signalling has an existing mechanism.

<zhi>Existing mechanisms we mentioned may be used, but the preference would be to use GEN_UNI for SPC (and this is in fact what we use for the ASON specification). This is because (again) of the architecture assumptions made in G.8080. An ASON network is assumed to be composed of multiple domains. In the vision of a global ASON network you might have multiple carriers connecting together (but also multiple domains within a single carrier network). The interfaces defined for these inter-domain signaling is the E-NNI interface. However, across an E-NNI the ERO object is an optional object, and in certain instances the information may not be passed due to policies that carriers may impose on the inter-domain interface.

If we were to use the ERO to carry the SPC information, then conceivably there are cases where this information would not pass the interface.</zhi>


As the draft acknowledges, the details of call/connection separation
have not been completely thought out, so why is a call identifier introduced
when we don't know if it is either necessary or sufficient?  I also think
its format is unnessarilly complex.

<zhi>The reason the draft does not include explanations of the call/connection separation is because when the initial version of the draft was submitted, I was told to break the document into two documents: one on requirements and one on just the protocol extensions. So if you want more explanations, G.8080 and G.7713 has much architectural descriptions and requirements for ASON. Also, the companion document (draft-lin-ccamp-gmpls-ason-rqts-00.txt) should still be available (it expires in Feb. 2003). This document was created as a result of breaking up an earlier version of the protocol extension document to a "just protocol extension" and a "requirements" document. This action was SUGGESTED by the members of the ccamp group in one of the earlier meetings, and that's what I did...
In terms of just explaining what is the call and connection separation, I believe most people should understand what the difference is between call and connection. After all in telecom this concept is not new (ATM and ISDN both have these concepts). Now to give a brief explanation, section 3.4 of the above mentioned document has this to say:
   A call may be simply described as: "An association between endpoints 
   that supports an instance of a service" [G8080]. Thus a call can be 
   considered as a service provided to the user endpoints, where 
   multiple calls may exist between any two endpoints. Each call may 
   have multiple connections. The call concept provides an abstract 
   relationship between two users, where this relationship describes (or 
   verifies) the extent to which the users are willing to offer (or 
   accept) service to each other. A call therefore does not provide the 
   actual connectivity for transmitting user traffic, but only builds a 
   relationship by which future connections may be made. 
    
   A property of a call is its ability to contain multiple connections, 
   where each connection may be of a different type and where each 
   connection may exist independently of other connections within the 
   call, i.e., each connection is setup and released with separate 
   Path/Resv messages. For example, a call may contain a mix of basic 
   connection, virtual concatenated connections and contiguous 
   concatenated connections (see [GMPLS-SDHSONET] for corresponding 
   connection signaling extensions). 
    
   The concept of the call allows for a better flexibility in how users 
   set up connections and how network offers services to users. In 
   essence, a call allows: 
    
   -    Support for virtual concatenation where each connection can 
        travel on different diverse paths 
   -    allows the use of a public and private addressing space (hosts 
        using public space while network using only internal private 
        addressing space) 
   -    Better upgrading strategy for service provider control plane 
        operation, where a call control (service provisioning) may be 
        separate from switches and connections (where the connection 
        control may reside) 
   -    Verification and authentication of a call (with both network 
        call controller as well as destination user) prior to 
        connection, which may result in less wasted resources 
   -    General treatment of multiple connections which may be 
        associated for the purpose of recovery; for example a pair of 
        primary and backup connections may belong to the same call. 

</zhi>
 


The processing of a call is said to be different than that of a connection,
but these differences are not detailed.

And by the way, if you read G.7713.2, it doesn't have any more explanation
for
how these TLVs are used than draft-lin-ccamp-gmpls-ason-rsvpte-04.txt does,
and
I think that is my primary objection to both.

<zhi>The explanations for the protocol extensions are in G.7713, which is the protocol neutral document. Yes, there is some indirection and pointers, but that's true for many documents structured in a hierarchical manner, i.e., 

G.807 is the "base" requirements document
G.8080 builds on the G.807 requirements and adds the architectural components associated with control plane
G.7713 builds on the G.807 requirements and G.8080 architectures, and specifies a protocol neutral way of supporting the call and connection controller (this is the signaling part)
G.7715 builds on the G.807 requirements and G.8080 architectures, and specifies a protocol neutral way of supporting the routing controller (this is the routing part)

After these "framework" documents are in place, the "dot" series of Recommendations are specified for the protocol specific support of ASON control plane (below are just signaling):
G.7713.1 is the PNNI extensions to support the G.7713 protocol neutral signaling specification
G.7713.2 is the RSVP-TE extensions to support the G.7713 protocol neutral signaling specification
G.7713.3 is the CR-LDP extensions to support the G.7713 protocol neutral signaling specification
</zhi>


I hope this helps to explain the issues expressed by John (of course I expected John to understand call/connection as he was a member of ATM Forum in developing the PNNI specification...)

Zhi



From owner-ietf@ietf.org  Thu Jan 23 06:00:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02797;
	Thu, 23 Jan 2003 06:00:20 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bf1c-0004z7-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 05:56:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bf1F-0004xq-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 05:55:37 -0500
Received: from net.cc.swin.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02673
	for <ietf@ietf.org>; Thu, 23 Jan 2003 05:49:08 -0500 (EST)
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by net.cc.swin.edu.au (8.9.3/8.9.3) with ESMTP id VAA18083;
	Thu, 23 Jan 2003 21:52:32 +1100 (AEDT)
Message-ID: <3E2FC970.CD809EB9@swin.edu.au>
Date: Thu, 23 Jan 2003 21:52:32 +1100
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: Last Call: CR-LDP Extensions for ASON to Informational
References: <9D42C6E086250248810DCADA39CE7EFC972171@nimbus>
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


...speaking of deprecating things, apparently the convention of
using ">" to mark lines of quoted text has also been deprecated.

gja



From owner-ietf@ietf.org  Thu Jan 23 07:13:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03849;
	Thu, 23 Jan 2003 07:13:49 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bgBE-0006uv-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 07:10:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bgAY-0006tg-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 07:09:18 -0500
Received: from maile.telia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03651;
	Thu, 23 Jan 2003 07:02:48 -0500 (EST)
Received: from d1o888.telia.com (d1o888.telia.com [213.67.172.241])
	by maile.telia.com (8.12.5/8.12.5) with ESMTP id h0NC60Yo006302;
	Thu, 23 Jan 2003 13:06:00 +0100 (CET)
X-Original-Recipient: iesg@ietf.org
Received: from pi.se (h70n2fls31o888.telia.com [213.64.120.70])
	by d1o888.telia.com (8.10.2/8.10.1) with ESMTP id h0NC5w220814;
	Thu, 23 Jan 2003 13:05:58 +0100 (CET)
Message-ID: <3E2FD911.9010304@pi.se>
Date: Thu, 23 Jan 2003 12:59:13 +0100
From: Loa Andersson <loa@pi.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
CC: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)"
 <sob@harvard.edu>,
        "'iesg@ietf.org'" <iesg@ietf.org>, "'ietf@ietf.org'"
 <ietf@ietf.org>,
        "'kireeti@juniper.net'" <kireeti@juniper.net>,
        "Lam, Hing-Kam
 (Kam)" <hklam@lucent.com>,
        "Malcolm Betts (E-mail)"
 <betts01@nortelnetworks.com>,
        "Stephen Shew (E-mail)"
 <sdshew@nortelnetworks.com>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Alan
 McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Trowbridge, Stephen J (Steve)"
 <sjtrowbr@ihmail.ih.lucent.com>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
References: <D3F8FD817CC7DA408AEB2CAC631C042A98E5F3@nj7460exch012u.ho.lucent.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

All,

taking a step back - I think we are discussing several issues in a mix
that makes it very hard to sort this out.

1. What other organizations may do to IETF (in this context (G)MPLS)
    protocols

    This won't be sorted out in this thread - and the only opinion so far
    is that it is a bad idea to let anyone else change or extend IETF
    protocols.

    This will require at statement from involved wg chairs and ADs and an
    approval from the IESG. I will push for such a statement.

2. Have the IETF protocols been changed

    This is is a matter of how "changed" is defined. Clearly the OIF
    UNI signaling spec extends the LDP protocol, message and new TLV.
    This is referenced by a normative reference in the three drafts
    discussed here

       draft-lin-ccamp-gmpls-ason-rsvpte-04.txt
       draft-aboulmagd-ccamp-crldp-ason-ext-02.txt
       draft-bala-uni-ldp-rsvp-extensions-04.txt

    I understand that the IESG wants to treat those as a packet, and that
    the last call on the CR-LDP Extensions for ASON to Informational in
    fact is a last call on all three of them. Further this could be
    construed to be seen as an "last call" on normative references -
    after all normative references are considered to necessary for
    implementing a spec.

    Also, the ITU work extends the IETF protocols, new objects, new TLVs
    and new error codes, that is why the drafts were written - to make it
    possible for IANA to approve the needed code points.

    In our normal use of terms change includes extends, but we should
    probably make that clear.

    The consequence of approving the drafts will be that the extensions
    by OIF and ITU will be approved by the IETF. I'm not sure that this
    has been in the open.

    However, not having a change process that relates to these protocols
    I'm not sure if the IESG can do anything else than approving that the
    IANA allocate the code points.

3. The quality of the drafts

    In my opinion (if I were to review them as a wg chair, but I'm not
    sure that those criteria apply to informational documents) we have a
    problem here.

    The draft-lin-ccamp-gmpls-ason-rsvpte-04.txt and the
    draft-bala-uni-ldp-rsvp-extensions-04.txt is an a shape such that I
    would (reluctantly) request publishing.

    But the draft-aboulmagd-ccamp-crldp-ason-ext-02.txt is not, there is
    a long series of points that needs to be updated. References, TLV
    description, un-expanded acronyms, etc. Would have returned this to
    the author for further work. Aside from that I have a couple of
    technical issues.

    Now, if the IESG considers them to be a package, this would effect
    all of them. I guess that it would be possible to weed the draft
    after it has been approved, but it deviates from normal practice.

My belief is that we should try to separate these issues from each
other.

/Loa



-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se





From owner-ietf@ietf.org  Thu Jan 23 08:47:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07375;
	Thu, 23 Jan 2003 08:47:47 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bhaR-00015N-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 08:40:07 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bhYs-000127-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 08:38:30 -0500
Received: from hoemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06957;
	Thu, 23 Jan 2003 08:32:00 -0500 (EST)
Received: from nj7460exch001h.wins.lucent.com (h135-17-42-36.lucent.com [135.17.42.36])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0NDZQ620344;
	Thu, 23 Jan 2003 08:35:26 -0500 (EST)
Received: by nj7460exch001h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <ZFGVQNWS>; Thu, 23 Jan 2003 08:35:25 -0500
Message-ID: <D3F8FD817CC7DA408AEB2CAC631C042A98E5F5@nj7460exch012u.ho.lucent.com>
From: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
To: Loa Andersson <loa@pi.se>, "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)"
	 <sob@harvard.edu>,
        "'iesg@ietf.org'" <iesg@ietf.org>, "'ietf@ietf.org'"
	 <ietf@ietf.org>,
        "'kireeti@juniper.net'" <kireeti@juniper.net>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Malcolm Betts (E-mail)"
	 <betts01@nortelnetworks.com>,
        "Stephen Shew (E-mail)"
	 <sdshew@nortelnetworks.com>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Trowbridge, Stephen J (Steve)" <sjtrowbr@ihmail.ih.lucent.com>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 08:35:24 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Loa,

See comments below...I guess none of these comments are technical, but more procedural...

-----Original Message-----
From: Loa Andersson [mailto:loa@pi.se]
Sent: Thursday, January 23, 2003 6:59 AM
To: Lin, Zhi-Wei (Zhi)
Cc: Wijnen, Bert (Bert); Scott Bradner (E-mail); 'iesg@ietf.org';
'ietf@ietf.org'; 'kireeti@juniper.net'; Lam, Hing-Kam (Kam); Malcolm
Betts (E-mail); Stephen Shew (E-mail); Lyndon Ong (E-mail); Alan McGuire
(E-mail); Trowbridge, Stephen J (Steve)
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational


All,

taking a step back - I think we are discussing several issues in a mix
that makes it very hard to sort this out.

1. What other organizations may do to IETF (in this context (G)MPLS)
    protocols

    This won't be sorted out in this thread - and the only opinion so far
    is that it is a bad idea to let anyone else change or extend IETF
    protocols.

<zhi>Last time I checked, the IETF didn't change the protocols, individuals did through contributions.  The extensions requested for Call/Connection control were submitted by an individual.  The fact the ITU weighed in requesting approval of the changes is a separate issue.</zhi>


    This will require at statement from involved wg chairs and ADs and an
    approval from the IESG. I will push for such a statement.

2. Have the IETF protocols been changed

    This is is a matter of how "changed" is defined. Clearly the OIF
    UNI signaling spec extends the LDP protocol, message and new TLV.
    This is referenced by a normative reference in the three drafts
    discussed here

       draft-lin-ccamp-gmpls-ason-rsvpte-04.txt
       draft-aboulmagd-ccamp-crldp-ason-ext-02.txt
       draft-bala-uni-ldp-rsvp-extensions-04.txt

    I understand that the IESG wants to treat those as a packet, and that
    the last call on the CR-LDP Extensions for ASON to Informational in
    fact is a last call on all three of them. Further this could be
    construed to be seen as an "last call" on normative references -
    after all normative references are considered to necessary for
    implementing a spec.

    Also, the ITU work extends the IETF protocols, new objects, new TLVs
    and new error codes, that is why the drafts were written - to make it
    possible for IANA to approve the needed code points.

    In our normal use of terms change includes extends, but we should
    probably make that clear.

    The consequence of approving the drafts will be that the extensions
    by OIF and ITU will be approved by the IETF. I'm not sure that this
    has been in the open.

<zhi>This has been presented at the last few IETF ccamp meetings. I don't know how else to make it more clear the intention.</zhi>


    However, not having a change process that relates to these protocols
    I'm not sure if the IESG can do anything else than approving that the
    IANA allocate the code points.

3. The quality of the drafts

    In my opinion (if I were to review them as a wg chair, but I'm not
    sure that those criteria apply to informational documents) we have a
    problem here.

    The draft-lin-ccamp-gmpls-ason-rsvpte-04.txt and the
    draft-bala-uni-ldp-rsvp-extensions-04.txt is an a shape such that I
    would (reluctantly) request publishing.

    But the draft-aboulmagd-ccamp-crldp-ason-ext-02.txt is not, there is
    a long series of points that needs to be updated. References, TLV
    description, un-expanded acronyms, etc. Would have returned this to
    the author for further work. Aside from that I have a couple of
    technical issues.

    Now, if the IESG considers them to be a package, this would effect
    all of them. I guess that it would be possible to weed the draft
    after it has been approved, but it deviates from normal practice.

My belief is that we should try to separate these issues from each
other.

/Loa



-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se




From owner-ietf@ietf.org  Thu Jan 23 09:44:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09104;
	Thu, 23 Jan 2003 09:44:46 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bicD-0003gC-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 09:46:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bQIT-0001oJ-00
	for ietf@ran.ietf.org; Wed, 22 Jan 2003 14:12:25 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03759;
	Wed, 22 Jan 2003 14:06:00 -0500 (EST)
Received: from nj7460exch001h.wins.lucent.com (h135-17-42-36.lucent.com [135.17.42.36])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0MJ9PG29904;
	Wed, 22 Jan 2003 14:09:25 -0500 (EST)
Received: by nj7460exch001h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <ZFGV398X>; Wed, 22 Jan 2003 14:09:25 -0500
Message-ID: <D3F8FD817CC7DA408AEB2CAC631C042A98E5F0@nj7460exch012u.ho.lucent.com>
From: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
To: "'iesg@ietf.org'" <iesg@ietf.org>, "'ietf@ietf.org'" <ietf@ietf.org>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)"
	 <sob@harvard.edu>,
        "'kireeti@juniper.net'" <kireeti@juniper.net>
Cc: "Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Malcolm Betts (E-mail)"
	 <betts01@nortelnetworks.com>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Lin, Zhi-Wei (Zhi)"
	 <zwlin@lucent.com>,
        "'sjtrowbridge@lucent.com'"
	 <sjtrowbridge@lucent.com>,
        "Dimitrios Pendarakis (E-mail)"
	 <DPendarakis@tellium.com>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Wed, 22 Jan 2003 14:09:23 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2C249.C402ADCA"
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_01C2C249.C402ADCA
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,
 
I wanted to respond to some of the comments raised by Kireeti.

With respect to the issue re call and connection separation, call and connection separation is an architectural requirement that is fully documented within Rec. G.8080.  Rec. G.8080 was liaised to the IETF quite some time ago (it was Approved end  '01; Consented Oct. '01), and at every meeting of the IETF for the past few meetings, there have been status updates provided on associated ITU-T work efforts.    As you may recall, Kam sent out an email earlier in reply to some other comments on where these documents can be obtained.  Rec. G.7713, which also reflects call and connection separation, was also sent to the IETF almost a year ago upon it's Approval end of  '01

To find the information that has been transmitted from ITU-T to IETF on this subject (from 26 October 2001), see:

ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15opticaltransport/COMMUNICATIONS/index.html <ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15opticaltransport/COMMUNICATIONS/index.html> 

In terms of the formatting of the CALL_ID, Kireeti raised a question as to why IP addresses only were not sufficient.   The answer to this illustrates one  difference between the IETF and ITU-T scope.   The focus of the IETF is upon IP-based client services while ITU-T has a multi-service focus, including not only IP but also other types of services (such as ATM). As such, it cannot be assumed that all NEs have IP addresses associated with them. In addition, it cannot be assumed that, even if the NE has an IP address, that those IP addresses are globally unique. As such, it was necessary to come up with a identifier format that does not assume the global uniqueness of an address.   The selected approach was to re-use existing identifier formats (e.g., from the TTI format such as G.709) that provides "free" globally unique identifiers.

As mentioned in the documentation for G.7713.x, the CALL_ID IS and NS is used only when "global" uniqueness is needed. In the event that networks are just been deployed or it's a single carrier's network where their addressing space is unique, then they can use the "operator specific" CALL_ID format. In this format the CALL_ID is essentially the IP address (if the type is 4-byte or 16-byte variety).

In terms of the "didn't hear a clear consensus on the need for this", the text was published in Report COM15-24 (Part IIA of the report of WP 3/15). According to ITU-T practice, inclusion in part IIA indicates that the text is "agreed", although not at the point of "consent" ready to issue for a Last Call. The agreement to place text in part IIA of a report occurs at the final plenary of the Study Group meeting. This meeting was attended by approximately 300 participants. The reason that the text was not put for consent at the May 2002 meeting of Study Group 15 was to provide time for comments on the text in response to liaisons sent to IETF ccamp and the ATM forum, and to allow IANA assigned codepoints to be included in the document. A clear U.K. national position paper was contributed to the meeting currently underway (delayed contribution 483), supporting that all three of the ASON signaling Recommendations should be put for consent at this meeting.

Hope this helps...

Zhi

 

-----Original Message-----

From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]

Sent: dinsdag 21 januari 2003 16:42

To: Kireeti Kompella

Cc: Bob Braden; iesg@ietf.org; ietf@ietf.org

Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational

 

Inline

> -----Original Message-----

> From: Kireeti Kompella [mailto:kireeti@juniper.net]

> Sent: maandag 20 januari 2003 22:49

> To: Wijnen, Bert (Bert)

> Cc: Bob Braden; iesg@ietf.org; ietf@ietf.org

> Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational

> 

> 

> Hi Bert,

> 

> On Sat, 18 Jan 2003, Wijnen, Bert (Bert) wrote:

> 

> > Yes they are from the "IETF Consensus space".

> >

> > Now can you be more specific as to why you do not consider this doc

> > ready for publication?

> 

> There are a large number of nits and typos -- so much so that in my

> opinion, this document should not have been sent to IETF Last Call

> without another round of edits. However, I will ignore those and

> concentrate on the substance.

> 

It would be great if you can send a list of nits and typos to the

author and copy Scott and Myself, possibly aslo the RFC-Editor.

> I would like to know what the intent is in not granting "the right

> to produce derivative works",

Did Steve Trowbridge not answer the first question?

> and whether the IETF should progress a

> document that is a derivative of IETF protocols with this clause.

> 

I think you meant a colon after "clause" and not a priod?

> The main thrust of the document is the "separation of call and

> connection"; 

> there is one short paragraph that describes this, and

> a reference to an ITU document.

Well, the ITU document should document the details. I don't think

we just want them to copy all their documentation into RFCs, do we?

> In my discussions with people who

> go to the ITU, I didn't hear a clear consensus on the need for this.

>

Well, then they should speak up in ITU I think. The ITU-T SG15 is 

discussing this in their meeting this week, and the technology is

up for consent. Any "people who go to the ITU" (to use your words)

and who do NOT agree with it should then speak up in ITU SG15,

don't you think so?

> An *IETF* document that describes the background, needs and how this

> is to be used would be very useful. This is especially important as

> the very next paragraph says that separation can be achieved "where

> the call set up request is always accaccompanied by a connection

> request", which (to my naive understanding) hardly is separation.

> 

Why would we need them to replicate their own documentation into an

IETF document?

> Secondly, there is a real paucity of detail in the description and

> use of the new messages: the Call Setup Message refers to the OIF

> UNI document for formating and doesn't say much about when and how

> it is to be used; there is no justification for the format of the

> Call ID (why is there an International Segment, etc.? Won't IP

> addresses do? Is this to be used for telephone calls??? My

> recollection is that Fred Baker (then IETF chair) said that using

> CCAMP for telephony was a no-no ....)

> 

I will leave it to the "ITU" folk to answer the details.

But your main point seems to be that you have not seen enough

documentation. ITU-T did a Liason Statement to us, and I believe

even specifically to CCAMP WG (that you co-chair) and so can you

tell me if you read their documentation that they have made

(freely) available to us to check? And after reading that, do

your points still hold. If so, then maybe we (CCAMP) should answer

the Liason Statement and explain to them how and where they should

add more detail and ask specific questions based on what they

document in their "drafts" (or documents) to which they point.

> Call Release can be "sent by any entity of the network". This surely

> can't be correct.

> 

Will let ITU-folk answer that.

> The Call Capability TLV is completely undocumented beyond the format

> of the TLV.

> 

How about in the documents in OIF and ITU that they point to?

> As someone else pointed out, crankback for CR-LDP has already been

> defined. Furthermore, this document does not say what procedures

> the sender and receiver must follow, and how crankback is to be

> effected.

>

What do you mean by "has already been defined" ??

And are the procedures not documented in the documents they point to?

> The "Additional Error Codes" have absolutely no detail about what

> they mean, when they are to be sent, and what the receiver should

> do with them. They also use a slew of unidentified acronyms.

> 

They do in the documents they point to.

Bert

> Kireeti.

> 


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

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


<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D251425817-22012003>Hi,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D251425817-22012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D251425817-22012003>I =
wanted to respond=20
to some of the comments raised by Kireeti.</SPAN></FONT></DIV>
<DIV>
<P><FONT size=3D2><SPAN class=3D251425817-22012003>With respect to the =
issue re call=20
and connection separation, call and connection separation is an =
architectural=20
requirement that is fully documented within Rec. G.8080.&nbsp; Rec. =
G.8080 was=20
liaised&nbsp;to the&nbsp;IETF quite some time ago (it was&nbsp;Approved =
end=20
&nbsp;'01; Consented Oct. '01), and at every meeting of the IETF for =
the past=20
few meetings, there have been status updates provided=20
on&nbsp;associated&nbsp;ITU-T work efforts.&nbsp;&nbsp;&nbsp; As you =
may recall,=20
Kam sent out an email earlier in reply to some other comments on where =
these=20
documents can be obtained.&nbsp; Rec. G.7713, which also =
reflects&nbsp;call and=20
connection separation,&nbsp;was also sent to the IETF almost a year ago =
upon=20
it's Approval end of &nbsp;'01</SPAN></FONT></P>
<P><FONT size=3D2><SPAN class=3D251425817-22012003>To find the =
information that has=20
been transmitted from ITU-T to IETF on this subject (from 26 October =
2001),=20
see:</SPAN></FONT></P>
<P><FONT size=3D2><SPAN class=3D251425817-22012003><A=20
href=3D"ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15opticaltransport/C=
OMMUNICATIONS/index.html">ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15=
opticaltransport/COMMUNICATIONS/index.html</A></SPAN></FONT></P>
<P><FONT><SPAN class=3D251425817-22012003></SPAN></FONT><FONT =
size=3D2>In terms of=20
the formatting of the CALL_ID<SPAN class=3D251425817-22012003>,=20
</SPAN>Kireeti<SPAN class=3D251425817-22012003> raised =
a&nbsp;question&nbsp;as=20
to&nbsp;why </SPAN>IP addresses<SPAN class=3D251425817-22012003> only =
were not=20
sufficient</SPAN>.&nbsp;<SPAN class=3D251425817-22012003>&nbsp; The =
answer to=20
this&nbsp;illustrates one&nbsp;</SPAN>&nbsp;difference<SPAN=20
class=3D251425817-22012003> between the </SPAN>IETF and ITU<SPAN=20
class=3D251425817-22012003>-T scope</SPAN>.&nbsp;<SPAN=20
class=3D251425817-22012003>&nbsp; The focus of the =
</SPAN>IETF&nbsp;<SPAN=20
class=3D251425817-22012003>is up</SPAN>on IP-based client services =
while ITU<SPAN=20
class=3D251425817-22012003>-T has a multi-service =
focus,</SPAN>&nbsp;includ<SPAN=20
class=3D251425817-22012003>ing</SPAN> not only IP but also other types =
of services=20
(such as ATM). As such<SPAN class=3D251425817-22012003>,&nbsp;it</SPAN> =

cannot&nbsp;<SPAN class=3D251425817-22012003>be </SPAN>assume<SPAN=20
class=3D251425817-22012003>d</SPAN> that all NEs have IP addresses =
associated with=20
them. In addition<SPAN class=3D251425817-22012003>,</SPAN>&nbsp;<SPAN=20
class=3D251425817-22012003>it</SPAN> cannot&nbsp;<SPAN =
class=3D251425817-22012003>be=20
</SPAN>assume<SPAN class=3D251425817-22012003>d</SPAN> that, even if =
the NE has an=20
IP address, that those IP addresses are globally unique. As such<SPAN=20
class=3D251425817-22012003>, it was necessary</SPAN> to come up with a =
identifier=20
format that does not assume the global uniqueness of an =
address.&nbsp;<SPAN=20
class=3D251425817-22012003>&nbsp; The selected approach </SPAN>was to =
re-use=20
existing identifier formats (<SPAN class=3D251425817-22012003>e.g., =
</SPAN>from=20
the TTI format such as G.709) that provides "free" globally unique=20
identifiers.</FONT></P>
<P><FONT size=3D2>As mentioned in the documentation for G.7713.x, the =
CALL_ID IS=20
and NS is used only when "global" uniqueness is needed. In the event =
that=20
networks are just been deployed or it's a single carrier's network =
where their=20
addressing space is unique, then they can use the "operator specific" =
CALL_ID=20
format. In this format the CALL_ID is essentially the IP address (if =
the type is=20
4-byte or 16-byte variety).</FONT></P>
<P><SPAN class=3D251425817-22012003><FONT size=3D2>In terms of the =
"didn't hear a=20
clear consensus on the need for this", the text was published in Report =
COM15-24=20
(Part IIA of the report of WP 3/15). According to ITU-T practice, =
inclusion in=20
part IIA indicates that the text is "agreed", although not at the point =
of=20
"consent" ready to issue for a Last Call. The agreement to place text =
in part=20
IIA of a report occurs at the final plenary of the Study Group meeting. =
This=20
meeting was attended by approximately 300 =
participants.&nbsp;</FONT></SPAN><SPAN=20
class=3D251425817-22012003><FONT size=3D2>The reason that the text was =
not put for=20
consent at the May 2002 meeting of Study Group 15 was to provide time =
for=20
comments on the text in response to liaisons sent to IETF ccamp and the =
ATM=20
forum, and to allow IANA assigned codepoints to be included in the=20
document.&nbsp;A clear U.K. national position paper was contributed to =
the=20
meeting currently underway (delayed contribution 483), supporting that =
all three=20
of the ASON signaling Recommendations should be put for consent at this =

meeting.</FONT></SPAN></P>
<P><SPAN class=3D251425817-22012003></SPAN><FONT size=3D2>Hope this=20
helps...</FONT></P>
<P><SPAN class=3D251425817-22012003><FONT =
size=3D2>Zhi</FONT></SPAN></P>
<P><SPAN class=3D251425817-22012003><FONT =
size=3D2></FONT></SPAN>&nbsp;</P></DIV>
<DIV><FONT face=3DArial><FONT face=3DArial>
<P><FONT size=3D2>-----Original Message-----</FONT></P>
<P><FONT size=3D2>From: Wijnen, Bert (Bert) =
[mailto:bwijnen@lucent.com]</FONT></P>
<P><FONT size=3D2>Sent: dinsdag 21 januari 2003 16:42</FONT></P>
<P><FONT size=3D2>To: Kireeti Kompella</FONT></P>
<P><FONT size=3D2>Cc: Bob Braden; iesg@ietf.org; =
ietf@ietf.org</FONT></P>
<P><FONT size=3D2>Subject: RE: Last Call: CR-LDP Extensions for ASON to =

Informational</FONT></P>
<P><FONT size=3D2></FONT>&nbsp;</P>
<P><FONT size=3D2>Inline</FONT></P>
<P><FONT size=3D2>&gt; -----Original Message-----</FONT></P>
<P><FONT size=3D2>&gt; From: Kireeti Kompella=20
[mailto:kireeti@juniper.net]</FONT></P>
<P><FONT size=3D2>&gt; Sent: maandag 20 januari 2003 22:49</FONT></P>
<P><FONT size=3D2>&gt; To: Wijnen, Bert (Bert)</FONT></P>
<P><FONT size=3D2>&gt; Cc: Bob Braden; iesg@ietf.org; =
ietf@ietf.org</FONT></P>
<P><FONT size=3D2>&gt; Subject: RE: Last Call: CR-LDP Extensions for =
ASON to=20
Informational</FONT></P>
<P><FONT size=3D2>&gt; </FONT></P>
<P><FONT size=3D2>&gt; </FONT></P>
<P><FONT size=3D2>&gt; Hi Bert,</FONT></P>
<P><FONT size=3D2>&gt; </FONT></P>
<P><FONT size=3D2>&gt; On Sat, 18 Jan 2003, Wijnen, Bert (Bert) =
wrote:</FONT></P>
<P><FONT size=3D2>&gt; </FONT></P>
<P><FONT size=3D2>&gt; &gt; Yes they are from the "IETF Consensus=20
space".</FONT></P>
<P><FONT size=3D2>&gt; &gt;</FONT></P>
<P><FONT size=3D2>&gt; &gt; Now can you be more specific as to why you =
do not=20
consider this doc</FONT></P>
<P><FONT size=3D2>&gt; &gt; ready for publication?</FONT></P>
<P><FONT size=3D2>&gt; </FONT></P>
<P><FONT size=3D2>&gt; There are a large number of nits and typos -- so =
much so=20
that in my</FONT></P>
<P><FONT size=3D2>&gt; opinion, this document should not have been sent =
to IETF=20
Last Call</FONT></P>
<P><FONT size=3D2>&gt; without another round of edits. However, I will =
ignore=20
those and</FONT></P>
<P><FONT size=3D2>&gt; concentrate on the substance.</FONT></P>
<P><FONT size=3D2>&gt; </FONT></P>
<P><FONT size=3D2>It would be great if you can send a list of nits and =
typos to=20
the</FONT></P>
<P><FONT size=3D2>author and copy Scott and Myself, possibly aslo the=20
RFC-Editor.</FONT></P>
<P><FONT size=3D2>&gt; I would like to know what the intent is in not =
granting=20
"the right</FONT></P>
<P><FONT size=3D2>&gt; to produce derivative works",</FONT></P>
<P><FONT size=3D2>Did Steve Trowbridge not answer the first =
question?</FONT></P>
<P><FONT size=3D2>&gt; and whether the IETF should progress =
a</FONT></P>
<P><FONT size=3D2>&gt; document that is a derivative of IETF protocols =
with this=20
clause.</FONT></P>
<P><FONT size=3D2>&gt; </FONT></P>
<P><FONT size=3D2>I think you meant a colon after "clause" and not a=20
priod?</FONT></P>
<P><FONT size=3D2>&gt; The main thrust of the document is the =
"separation of call=20
and</FONT></P>
<P><FONT size=3D2>&gt; connection"; </FONT></P>
<P><FONT size=3D2>&gt; there is one short paragraph that describes =
this,=20
and</FONT></P>
<P><FONT size=3D2>&gt; a reference to an ITU document.</FONT></P>
<P><FONT size=3D2>Well, the ITU document should document the details. I =
don't=20
think</FONT></P>
<P><FONT size=3D2>we just want them to copy all their documentation =
into RFCs, do=20
we?</FONT></P>
<P><FONT size=3D2>&gt; In my discussions with people who</FONT></P>
<P><FONT size=3D2>&gt; go to the ITU, I didn't hear a clear consensus =
on the need=20
for this.</FONT></P>
<P><FONT size=3D2>&gt;</FONT></P>
<P><FONT size=3D2>Well, then they should speak up in ITU I think. The =
ITU-T SG15=20
is </FONT></P>
<P><FONT size=3D2>discussing this in their meeting this week, and the =
technology=20
is</FONT></P>
<P><FONT size=3D2>up for consent. Any "people who go to the ITU" (to =
use your=20
words)</FONT></P>
<P><FONT size=3D2>and who do NOT agree with it should then speak up in =
ITU=20
SG15,</FONT></P>
<P><FONT size=3D2>don't you think so?</FONT></P>
<P><FONT size=3D2>&gt; An *IETF* document that describes the =
background, needs and=20
how this</FONT></P>
<P><FONT size=3D2>&gt; is to be used would be very useful. This is =
especially=20
important as</FONT></P>
<P><FONT size=3D2>&gt; the very next paragraph says that separation can =
be=20
achieved "where</FONT></P>
<P><FONT size=3D2>&gt; the call set up request is always accaccompanied =
by a=20
connection</FONT></P>
<P><FONT size=3D2>&gt; request", which (to my naive understanding) =
hardly is=20
separation.</FONT></P>
<P><FONT size=3D2>&gt; </FONT></P>
<P><FONT size=3D2>Why would we need them to replicate their own =
documentation into=20
an</FONT></P>
<P><FONT size=3D2>IETF document?</FONT></P>
<P><FONT size=3D2>&gt; Secondly, there is a real paucity of detail in =
the=20
description and</FONT></P>
<P><FONT size=3D2>&gt; use of the new messages: the Call Setup Message =
refers to=20
the OIF</FONT></P>
<P><FONT size=3D2>&gt; UNI document for formating and doesn't say much =
about when=20
and how</FONT></P>
<P><FONT size=3D2>&gt; it is to be used; there is no justification for =
the format=20
of the</FONT></P>
<P><FONT size=3D2>&gt; Call ID (why is there an International Segment, =
etc.? Won't=20
IP</FONT></P>
<P><FONT size=3D2>&gt; addresses do? Is this to be used for telephone =
calls???=20
My</FONT></P>
<P><FONT size=3D2>&gt; recollection is that Fred Baker (then IETF =
chair) said that=20
using</FONT></P>
<P><FONT size=3D2>&gt; CCAMP for telephony was a no-no ....)</FONT></P>
<P><FONT size=3D2>&gt; </FONT></P>
<P><FONT size=3D2>I will leave it to the "ITU" folk to answer the=20
details.</FONT></P>
<P><FONT size=3D2>But your main point seems to be that you have not =
seen=20
enough</FONT></P>
<P><FONT size=3D2>documentation. ITU-T did a Liason Statement to us, =
and I=20
believe</FONT></P>
<P><FONT size=3D2>even specifically to CCAMP WG (that you co-chair) and =
so can=20
you</FONT></P>
<P><FONT size=3D2>tell me if you read their documentation that they =
have=20
made</FONT></P>
<P><FONT size=3D2>(freely) available to us to check? And after reading =
that,=20
do</FONT></P>
<P><FONT size=3D2>your points still hold. If so, then maybe we (CCAMP) =
should=20
answer</FONT></P>
<P><FONT size=3D2>the Liason Statement and explain to them how and =
where they=20
should</FONT></P>
<P><FONT size=3D2>add more detail and ask specific questions based on =
what=20
they</FONT></P>
<P><FONT size=3D2>document in their "drafts" (or documents) to which =
they=20
point.</FONT></P>
<P><FONT size=3D2>&gt; Call Release can be "sent by any entity of the =
network".=20
This surely</FONT></P>
<P><FONT size=3D2>&gt; can't be correct.</FONT></P>
<P><FONT size=3D2>&gt; </FONT></P>
<P><FONT size=3D2>Will let ITU-folk answer that.</FONT></P>
<P><FONT size=3D2>&gt; The Call Capability TLV is completely =
undocumented beyond=20
the format</FONT></P>
<P><FONT size=3D2>&gt; of the TLV.</FONT></P>
<P><FONT size=3D2>&gt; </FONT></P>
<P><FONT size=3D2>How about in the documents in OIF and ITU that they =
point=20
to?</FONT></P>
<P><FONT size=3D2>&gt; As someone else pointed out, crankback for =
CR-LDP has=20
already been</FONT></P>
<P><FONT size=3D2>&gt; defined. Furthermore, this document does not say =
what=20
procedures</FONT></P>
<P><FONT size=3D2>&gt; the sender and receiver must follow, and how =
crankback is=20
to be</FONT></P>
<P><FONT size=3D2>&gt; effected.</FONT></P>
<P><FONT size=3D2>&gt;</FONT></P>
<P><FONT size=3D2>What do you mean by "has already been defined" =
??</FONT></P>
<P><FONT size=3D2>And are the procedures not documented in the =
documents they=20
point to?</FONT></P>
<P><FONT size=3D2></FONT></P>
<P><FONT size=3D2>&gt; The "Additional Error Codes" have absolutely no =
detail=20
about what</FONT></P>
<P><FONT size=3D2>&gt; they mean, when they are to be sent, and what =
the receiver=20
should</FONT></P>
<P><FONT size=3D2>&gt; do with them. They also use a slew of =
unidentified=20
acronyms.</FONT></P>
<P><FONT size=3D2>&gt; </FONT></P>
<P><FONT size=3D2>They do in the documents they point to.</FONT></P>
<P><FONT size=3D2>Bert</FONT></P>
<P><FONT size=3D2>&gt; Kireeti.</FONT></P>
<P><FONT size=3D2>&gt; </FONT></P></FONT></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C2C249.C402ADCA--





From owner-ietf@ietf.org  Thu Jan 23 10:27:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10038;
	Thu, 23 Jan 2003 10:27:06 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bjA5-0006t2-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 10:21:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bj9M-0006rY-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 10:20:16 -0500
Received: from c2bapps5.btconnect.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA09852;
	Thu, 23 Jan 2003 10:13:40 -0500 (EST)
Received: from designintel (actually host host213-123-57-198.in-addr.btopenworld.com) by c2bapps5 with SMTP (XT-PP) with ESMTP; Thu, 23 Jan 2003 15:16:57 +0000
Reply-To: <cdel@firsthand.net>
From: "Christian de Larrinaga" <cdel@firsthand.net>
To: "Lin, Zhi-Wei \(Zhi\)" <zwlin@lucent.com>, <iesg@ietf.org>,
        <ietf@ietf.org>, "Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>,
        "Scott Bradner \(E-mail\)" <sob@harvard.edu>, <kireeti@juniper.net>
Cc: "Stephen Shew \(E-mail\)" <sdshew@nortelnetworks.com>,
        "Lyndon Ong \(E-mail\)" <lyong@ciena.com>,
        "Malcolm Betts \(E-mail\)" <betts01@nortelnetworks.com>,
        "Lam, Hing-Kam \(Kam\)" <hklam@lucent.com>,
        "Alan McGuire \(E-mail\)" <alan.mcguire@bt.com>,
        <sjtrowbridge@lucent.com>,
        "Dimitrios Pendarakis \(E-mail\)" <DPendarakis@tellium.com>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 15:16:48 -0000
Message-ID: <MABBIEBOAFJNELEGFHCKKEHPHFAA.cdel@firsthand.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <D3F8FD817CC7DA408AEB2CAC631C042A98E5F0@nj7460exch012u.ho.lucent.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Lin Zhi-Wei

You mention a UK national position paper. Can you give me the references and
what made this "national"?

many thanks,

Christian de Larrinaga


> A clear U.K. national position paper was
>contributed to the meeting currently underway
>(delayed contribution 483), supporting that all
>three of the ASON signaling Recommendations
>should be put for consent at this meeting.
>Hope this helps...
>Zhi




From owner-ietf@ietf.org  Thu Jan 23 10:57:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11044;
	Thu, 23 Jan 2003 10:57:21 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bjks-00083M-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 10:59:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bjif-0007zK-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 10:56:45 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10819;
	Thu, 23 Jan 2003 10:50:12 -0500 (EST)
Received: from nj7460exch001h.wins.lucent.com (h135-17-42-36.lucent.com [135.17.42.36])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0NFrcG08605;
	Thu, 23 Jan 2003 10:53:39 -0500 (EST)
Received: by nj7460exch001h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <ZFGVQZ44>; Thu, 23 Jan 2003 10:53:38 -0500
Message-ID: <D3F8FD817CC7DA408AEB2CAC631C042A98E5FD@nj7460exch012u.ho.lucent.com>
From: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
To: cdel@firsthand.net, "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>, iesg@ietf.org,
        ietf@ietf.org, "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)" <sob@harvard.edu>, kireeti@juniper.net
Cc: "Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Malcolm Betts (E-mail)"
	 <betts01@nortelnetworks.com>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>, sjtrowbridge@lucent.com,
        "Dimitrios Pendarakis (E-mail)" <DPendarakis@tellium.com>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 10:53:36 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Christian,

This is one of the processes within the ITU-T standards body. The documents that is submitted into these documents can have multiple levels of "status". I'm not sure what the process is within the UK, but I have some idea of the process within the USA. Maybe Stephen Trowbridge or others more familiar with the procedures can comment (I typically try to stay away from these and stick my head into the technical stuff).

The lowest status is that a document is sent by a company. In this case only that company is known to support this. A document may also have multiple company names as contributors, in which case these companies are active proponents.
The next level status is a country document. A country document (e.g., USA or UK) means that the document has undergone a national standards process, and that ALL the companies represented within that country will support the position stated by the document.

This is of course much different from the IETF process, where all documents are by individual basis (theoretically it should not even have company affiliation but only represents the views of the individuals in the author list, but of course practically most people who attends and submits documents are actually representing a company view)...please don't flame me, just giving an observation based on my limited exposure to the IETF process...

Hope this helps

Zhi



-----Original Message-----
From: Christian de Larrinaga [mailto:cdel@firsthand.net]
Sent: Thursday, January 23, 2003 10:17 AM
To: Lin, Zhi-Wei (Zhi); iesg@ietf.org; ietf@ietf.org; Wijnen, Bert
(Bert); Scott Bradner (E-mail); kireeti@juniper.net
Cc: Stephen Shew (E-mail); Lyndon Ong (E-mail); Malcolm Betts (E-mail);
Lam, Hing-Kam (Kam); Alan McGuire (E-mail); sjtrowbridge@lucent.com;
Dimitrios Pendarakis (E-mail)
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational


Lin Zhi-Wei

You mention a UK national position paper. Can you give me the references and
what made this "national"?

many thanks,

Christian de Larrinaga


> A clear U.K. national position paper was
>contributed to the meeting currently underway
>(delayed contribution 483), supporting that all
>three of the ASON signaling Recommendations
>should be put for consent at this meeting.
>Hope this helps...
>Zhi



From owner-ietf@ietf.org  Thu Jan 23 11:10:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11499;
	Thu, 23 Jan 2003 11:10:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bjxR-0000Lu-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 11:12:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bWbK-0002C3-00
	for ietf@ran.ietf.org; Wed, 22 Jan 2003 20:56:18 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13640;
	Wed, 22 Jan 2003 20:49:52 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0N1rGU09540;
	Wed, 22 Jan 2003 20:53:17 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ268HNJ>; Thu, 23 Jan 2003 02:53:15 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE374@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: ietf@ietf.org
Cc: "Iesg (E-mail)" <iesg@ietf.org>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 02:51:57 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

In response to some questions that were not yet
answered in the below discussion

> -----Original Message-----
> From: <IETF-participant>
> Sent: donderdag 23 januari 2003 1:04
> To: Wijnen, Bert (Bert)
> Cc: Scott Bradner
> Subject: Re: [Fwd: quick review of the ason cr-ldp draft]
> 
> < snip >
> 
> >>My documented concerns are on the cr-ldp draft, there are a bunch of
> >>things that are just documentation, but some other things
> >>
> >>- the use of mpls for b-isdn (Kireeti called telephony)
> > 
> > Well, the fact that they use "call" terminology, does that really mean
> > that they are doing what you claim here?
> 
> this is tricky, I guess that you could claim they are not, but I was
> deeply involved in some of the ISDN work, and it looks disturbingly
> familiar. but you are right it needs to be proven that they don't, and
> that has not been done
> 
> >>- use of non-IP addresses
> > 
> > 
> > I understand that we IP-biggots want everything in the whole world
> > to be IP based. But can we actually prescribe that to the world?
> > 
> 
> oh, but we have had it as an architectural principal that mpls follows
> ip routing, it is even true when you have constraint based routed LSPs,
> it is the routing protocol that describes the network
> this wouldn't be an issue if they just were transferring non-IP addresses
> across the cloud, but they talk about "Call Release message is sent by
> any entity of the network" and it is not entirely clear that this is
> the case.
> 
Can the ITU folk answer this one please?

> > 
> >>- UNI/NNI fuzziness
> > 
> > 
> > Is that a matter of cleaning up the text?
> 
> possibly - I'm through the better part of the OIF document
> 
OK, eager to see where we get when you have read it all

> > Have you read the OIF spec(s)? Is it still fuzzy after that?
> > I also understand that most of the OIF UNI/NNI stuff has been worked
> > on by many (if not all) of the same people that are actibe in IETF.
> > Besides, a few years back, (I believe Rob Coltun was still RTG AD
> > and MPLS and such was all in RTG area), we (IETF) did send UNI folk
> > away stating that we did not want to work on it and so they did their
> > thing in OIF. The fact that most IETF-ers are participating there,
> > made me feel that they wanted it anyway, even though we in purists
> > land did not want to deal with it.
> > I believe OIF has approved UNI (and maybe also NNI, not sure) and that
> > vendors actually have products that comply with the UNI spec. I suspect
> > that they (these products) in fact already use the numbers that people
> > now ask IANA to assign. I know that such is a violation... but what
> > can we do?
> 
> we could at least understand what is going on and try to stop further
> "damage" ;)
> 
The damage has been done if they indeed have used such numbers in
any products. But I do know that OIF was using numbers out of the
LDP number space and RSVP number space a year or more ago, and I 
just happened to run into one of their documents and then started
to reaise concerns. That then actually made bala send a I-D that
requested for assigments (I think he did so early 2002 or probably
already in 2001). It got delayed and delayed and revised and delayed
etc... And then OIF approved their UNI 1.0 in Oct 2001, so I would
be surprised if there are not yet already products on the market
that use those code-points they originally wanted.

Maybe Bala or someone else can react to this.

It is in fact also very interesting to see that some of the people
who now are objecting are on the contributors list of the OIF document:
   John Drake
   Kireeeti Kompella

But if you read the page 2 (contributors list) of the OIF document
then you see that many (like 10+ or so) of the major players in
our CCAMP and MPLS WGs were actually contributing to the OIF
LDP and RSVP specs for UNI.

> > 
> > 
> >>- the level violation
> >>
> > 
> > 
> >>do concern me quite a bit, if ITU go and do this the risk is high that
> >>ldp starting to developing away from being an ietf protocol.
> >>
> > 
> > When we make things extensible, then that is always a risk. And how
> > do we control that. 
> > 
> > 
> >>Jerry Ash and John Drake sent as comments much to the same effect
> >>during the last call.
> >>
> > 
> > But I think that Steve Trowbridge (and possibly others) refuted that
> > did they not? If it is indeed such a SERIOUS and BAD violation,
> > why not did MOST or ALL of the IETF-folk object and speak up, or
> > at least support the statements from Jerry and John?
> 
> I know why I didn't - part of this was outside my horizon and 
> it became visible only after I started to review it
> 
Ok, but as I said above, many of our IETF folk were actively
participating in OIF... and I believe quite a few are also 
active in ITU. So if it is such a technical issue, I would
have expected alarm bells to have gone off much much earlier.

> > 
> > 
> >>If you ask me today I would object to let ITU go away and do this.
> >>It is possible that some/most/all of the would go away if it were
> >>better documented.
> >>
> > 
> > Well, did you read the ITU specs they pointed to?
> 
> nope -started with the OIF  - since that was easier to find, the
> ITU specs are on my list
> 
Great, thanks for investing the time and doing a serious and
detailed review. 

> > I do not believe that we MUST REQUIRE that all is documented in RFCs.
> > Are the ITU specs not clear enough?
> > Is Jerry Ash and others (who also participate in ITU) speaking up
> > there to BLOCK the achievement of CONSENT on thes documents?
> > 
> > You know, when people in ITU make trouble about our documents, we
> > often tell ITU: why don't you make your people participate in 
> > IETF WGs and speak up there. We can do similar thing in the
> > otehr direction. Kireeti in fact mentioned that various ITU-goers 
> > he knows claim that ITU does NOT have CONSENSUS on this. If this
> > is the case, then I guess there is no problem, cause those
> > people will then BLOCK the CONSENT in ITU, no?
> 
> well, I guess so - but I'm concerned about that IESG is about to
> approve a document that are not up to the quality that
> we've pushing on other authors, if I sent this to IESG - it would
> have been bounced on the nits within 10 minutes
> 
> (note - the only informational document I've first hand experience
> with is the documenation of the cr-ldp decission, but I've the
> feeling that similar problems actually held that document until they
> were taken care of)
> 
> I'm not counting on internal ITU politics to do our job
> 
And we should not. That is why we did the IETF Last Call when it
turned out that they want assignments in the IETF-Consensus needed
name space.

> > Or are those ITU-goers a very small minority in ITU and are they
> > trying to do an end-run around the ITU process and trying to block
> > things by convincing us (IESG) to not approve assignment of 
> > the reuqired numbers in RSVP and LDP namespaces?
> 
> have no idea - don't go to ITU, don't want to block good standards,
> but want to have proper documents
> 
We agree

> > 
> > 
> >>I'm also a bit concerned with the statements on the possibility
> >>to document after approval - seems to be a queer process, and not
> >>something that I've seen before.
> >>
> > 
> > When technical changes are expected, then we should indeed not go
> > that path. When it is a matter of clarifications that we can
> > identify, then I have seen that happen many times, even at 48-hour
> > author-call from RFC-Editor.
> 
> so this is the formula you could use to do something along the lines
> I proposed in an earlier mail
> 
OK, there you suggested:

  As Bert has demonstrated below thaer are things in at least the
  cr-ldp draft that does not meet the (formal) critiera for be
  an RFC.

All I know of now are some typos-type things that can be done
during editorial process.
I also know about the incorrect ref to the OIF document (see below)
we will fix that. When other people see more specific things, pls
point them out and be specific.

  How would the IESG react to something like this?

  - a statement that we understand the time constraints that ITU
    are in and recognize that they need the code points
  - inform the ITU that we are preparing a (g)mpls change process
  - request that ITU submit their changes to the (g)mpls protocols
    to us according this change process, in the same message inform
    them that they will get their code points as requested
  - a statement (in that same message) that this does not imply that
    we are accepting changes to LDP or any other IETF protocol
    by indirection
  - a request to IANA to give ITU their code points
  - inform other "potential (g)mpls protocol extenders" that we are
    working on the change process

  If this could be handled this way (or similar), it would work for me.
  Otherwise I would object to approving the three drafts. Mostly based
  on the fact that I don't understand where the LDP protocol are going.

Well, Scott and I have actually been talking with a few SUB-IP WG
chairs that we need to document something about (G)MPLS change process.

As a result of the ITU requests for assigments in RSVP namespace, we
also think that we probably need better and approved/published 
IANA considerations/guidelines for RSVP paramter assignments.

Once we have that in-place, it seems obvious that we should tell 
other people (organizations) what our (new or now documented) rules
are for making changes/ectensions/assignments. And of course we will
follow those in the future.

I am not sure it behooves us to now stall the ITU request and let them
wait till we get our act together. Not sure if that is what you meant?

> > 
> > 
> >>As for rsvp I've not reviewed it carefully enough, but at least if
> >>the use of non-IP addresses are in there I guess it should be a no.
> >>
> > 
> > They are. Funny thing here is that they ask for assignments mostly
> > in FCFS space (and the one or 2 code points that are not in FCFS
> > space could easily be moved into FCFS space), and so I do not see
> > how IANA (or we) can actually block/reject such assignments.
> > 
> > 
> >>But just to point on the complexity here, the Bala and Lin drafts
> >>includes normative references to
> >>"OIF-UNI-01.0, User Network Interface (UNI) 1.0 Signaling 
> >>Specification"
> >>that specification specifies at least one new LDP message (Status
> >>Enquiry Message) and several TLVs. I'm not aware of that we have 
> >>approved those, they are not in the IANA registry.
> >>
> > 
> > Scott and I noticed that when evaluating over the last weekend.
> > Since the ASON CR-LDP doc that we Last Called indeed has a normative
> > reference to the bala document, and since it makes sub-assignments
> > udnerneath some of the code point of the bala document, it seemed
> > that we more-or-less did an implicit Last Call for the bala doc.
> 
> I can only speak for myself - and I was not aware of this - if for no
> other reason the ason cr-ldp doc do not separate into normative and
> non-normative references
> 

Although I personally like it that even informational documents split
their normative and informative references, I normally leave it to
the RFC-Editor to push back when they come in as individual submissions
via the RFC-Editor, and that is what happened with these docs.

Now that the BALA doc is normative should be very clear, cause
the cr-ldp-extensions-for-ason doc does in fact use the Source ID TLV
and the Dest ID TLV (sections 3.1 and 3.2) as specified in ref 07
And ref 07 is the BALA document.

> > In any event, no one brought this up yet except you do at this point.
> > So we assumed that by having IETF consensus on the ASON CRLDP doc
> > we can defend that it also approves the bala doc. This is possibly
> > a trouble-some assumption... Scott and I understand that. And we
> > have presented the issue in similar wording to the IESG, so the
> > whole IESG is aware and can decide on this.
> > 
> > Do you see our reasoning as seriously flawed here?
> 
> you might get away with that reasoning, but I really would like it
> out in the open, it would have been possible to last call all three
> documents together
> 
Well, with the posting of this discussion it is.
In fact Scott was going to post it anyway, but I suspect he has
not found the time yet.

> > 
> > 
> >>If the IESG go about approving those drafts does this come to that
> >>the LDP extensions in the normative references are approved?
> >>
> > 
> > See above. The answer is yes. the 3 docs:
> >   draft-lin-ccamp-gmpls-ason-rsvpte-04.txt
> >   draft-aboulmagd-ccamp-crldp-ason-ext-02.txt
> >   draft-bala-uni-ldp-rsvp-extensions-04.txt
> > basically go together. They document (with ptrs to OIF and ITU docs
> > for details) the RSVP and CR-LDP code points requested for ASON
> > stuff. ITU has asked (cia a liason statement) back in May 2002
> > (I thijnk that was the month) that we review their docs and 
> > approve the request to IANA for assignments. 
> 
> this concerns me - how far do the indirection go? ptr to a doc with a
> ptr to a doc with a ptr to a doc ....
> 
I don't think it is any worse then when we use our own RFCs.
You should try to find something in our RFC-Series. Specifically
in the area of MPLS, GMPLS, CR-LDP and RSVP-TE... I know from
experiences that you keep getting pointed to yet more RFCs or
I-Ds all the time.

The tradeoff I think is that we want some RFC that documents where
we can find the details in the documents of the other organization.
We should not need to have them reproduce all the documents in
RFC-form.

> was that liaison sent to SubIP, ccamp or the mpls wg?
> 
I believe there where several, and they were to CCAMP mainly.
They are all accessible from the IETF web pages:
   http://www.ietf.org/IESG/liaison.html
And ITU SG 15 has been giving ptrs and summaries at the last 4-5
CCAMP meetings at least.

> > 
> > 
> >>The ason cr-ldp draft references the
> >>       B. Rajagopalan, User Network Interface (UNI) 1.0 Signaling
> >>       Specification, OIF-UNI-01.1, October 2001.
> >>
> >>if this is not the (and it shouldn't if there is any meaning to the
> >>OIF-UNI-01.0 vs. OIF-UNI-01.1 I can't find it on the OIF page, but I
> >>guess that it will include the same extensions to LDP.
> >>
> > 
> > So it seems we need to clarify the exact reference. I am sending
> > then a question about this.
> 
> saw the answer - and it just strengthen the feeling I've on that the
> ason cr-ldp is not very well thought through and reviewed
> 
Right, The answer from the authors was that there is just one
spec and that is UNI 1.0. So this is a typo that needs fixing.

> > 
> > 
> >>I guess I'm confused and in need of the (G)MPLS change process.
> >>
> > 
> > We should have had proper IANA Considerations for RSVP (which 
> > would have caused an earlier IETF Last Call on the RSVP doc
> > which now passed without IETF Last Call) and indeed we should
> > have had proper "(G)MPLS change control documentation". 
> > We cannot say that we have not seen this coming... ITU has been
> > working on this for more than a year. So I guess we have to 
> > (at least partly) blame ourselves.
> 
> agreed - I should have reviewed the ITU work back in May
> 
Bingo.

> > 
> > Thanks for your continued input and review. It is appreciated,
> > even though it causes us some trouble at this late time.
> > 
> > Main question I want answered from this email:
> >   - if you read the OIF and ITU documents, does that more or less
> >     make the stuff acceptable (let us say at least to the point
> >     that things are properly documented).
> 
> So far I think the OIF document is pretty good as far as documentation
> goes, but it contained stuff that I'm not entirely happy with
> technically and that I was not aware of before this - part of the
> problem is that it is not an open process that we can
> influence, if the ITU docs are of the same quality that would be good,
> but it would still leave the ason cr-ldp as severely sub-quality
> 
> > But answer/reaction to all of my statements above would be helpful
> > too.
> 
> ok - I've tried :)
> 
Thanks for trying. And we all appreciate the serious review you
are doing.

> <IETF-participant>
> 
Bert





From owner-ietf@ietf.org  Thu Jan 23 11:10:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11505;
	Thu, 23 Jan 2003 11:10:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bjxQ-0000Lh-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 11:12:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bVjJ-0000tS-00
	for ietf@ran.ietf.org; Wed, 22 Jan 2003 20:00:29 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12899;
	Wed, 22 Jan 2003 19:54:06 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0N0vUU19104;
	Wed, 22 Jan 2003 19:57:30 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ268HGA>; Thu, 23 Jan 2003 01:57:29 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE36E@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: ietf@ietf.org
Cc: "Iesg (E-mail)" <iesg@ietf.org>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 01:56:57 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk



As you may all know, when an IETF Last Call is issued,
people can send comments to IETF and/or IESG mailing lists.

Here is a comment (with some back and forth discussionbs)
that was only sent to Scott Bradner and myself, but that 
deserves publicity. It is from a constructive and conscientious 
participant in the IETF in the Sub_IP area. For various
reasons, the person does not want to go public him/herself.

So I am forwarding without revealing the originators name. 

Bert 

-----Original Message-----
From: <IETF-participant>
Sent: donderdag 23 januari 2003 1:04
To: Wijnen, Bert (Bert)
Cc: Scott Bradner
Subject: Re: [Fwd: quick review of the ason cr-ldp draft]


Bert,


Wijnen, Bert (Bert) wrote:
< snip >
> Last weekend, Scott and I evaluated the comments and documents and
> based on that we recommended to IESG that approval seemed OK.
> We also informed ITU SG15 that we made a positive recomendation
> (they need the assignments this week), but that IESG still had
> to decide in their upcoming telechat.
> So if we have to retract based in this continued discussion, that
> looks ugly. But we have to do what needs to be done.
> 

< snip >

> Also... not having these comments in the open, does not show to
> ITU people (or anyone) who is following the Last Call that this
> is happening and what the arguments are.
> Possibly Scott or I should post this to ietf list as coming from
> an anonymous commenter. So that at least the issues are on the table.

I guess that is OK

< snip >

>>My documented concerns are on the cr-ldp draft, there are a bunch of
>>things that are just documentation, but some other things
>>
>>- the use of mpls for b-isdn (Kireeti called telephony)
> 
> Well, the fact that they use "call" terminology, does that really mean
> that they are doing what you claim here?

this is tricky, I guess that you could claim they are not, but I was
deeply involved in some of the ISDN work, and it looks disturbingly
familiar. but you are right it needs to be proven that they don't, and
that has not been done

>>- use of non-IP addresses
> 
> 
> I understand that we IP-biggots want everything in the whole world
> to be IP based. But can we actually prescribe that to the world?
> 

oh, but we have had it as an architectural principal that mpls follows
ip routing, it is even true when you have constraint based routed LSPs,
it is the routing protocol that describes the network
this wouldn't be an issue if they just were transferring non-IP addresses
across the cloud, but they talk about "Call Release message is sent by
any entity of the network" and it is not entirely clear that this is
the case

> 
>>- UNI/NNI fuzziness
> 
> 
> Is that a matter of cleaning up th text?

possibly - I'm through the better part of the OIF document

> Have you read the OIF spec(s)? Is it still fuzzy after that?
> I also understand that most of the OIF UNI/NNI stuff has been worked
> on by many (if not all) of the same people that are actibe in IETF.
> Besides, a few years back, (I believe Rob Coltun was still RTG AD
> and MPLS and such was all in RTG area), we (IETF) did send UNI folk
> away stating that we did not want to work on it and so they did their
> thing in OIF. The fact that most IETF-ers are participating there,
> made me feel that they wanted it anyway, even though we in purists
> land did not want to deal with it.
> I believe OIF has approved UNI (and maybe also NNI, not sure) and that
> vendors actually have products that comply with the UNI spec. I suspect
> that they (these products) in fact already use the numbers that people
> now ask IANA to assign. I know that such is a violation... but what
> can we do?

we could at least understand what is going on and try to stop further
"damage" ;)

> 
> 
>>- the level violation
>>
> 
> 
>>do concern me quite a bit, if ITU go and do this the risk is high that
>>ldp starting to developing away from being an ietf protocol.
>>
> 
> When we make things extensible, then that is always a risk. And how
> do we control that. 
> 
> 
>>Jerry Ash and John Drake sent as comments much to the same effect
>>during the last call.
>>
> 
> But I think that Steve Trowbridge (and possibly others) refuted that
> did they not? If it is indeed such a SERIOUS and BAD violation,
> why not did MOST or ALL of the IETF-folk object and speak up, or
> at least support the statements from Jerry and John?

I know why I didn't - part of this was outside my horizon and it became
visible only after I started to review it

> 
> 
>>If you ask me today I would object to let ITU go away and do this.
>>It is possible that some/most/all of the would go away if it were
>>better documented.
>>
> 
> Well, did you read the ITU specs they pointed to?

nope -started with the OIF  - since that was easier to find, the
ITU specs are on my list

> I do not believe that we MUST REQUIRE that all is documented in RFCs.
> Are the ITU specs not clear enough?
> Is Jerry Ash and others (who also participate in ITU) speaking up
> there to BLOCK the achievement of CONSENT on thes documents?
> 
> You know, when people in ITU make trouble about our documents, we
> often tell ITU: why don't you make your people participate in 
> IETF WGs and speak up there. We can do similar thing in the
> otehr direction. Kireeti in fact mentioned that various ITU-goers 
> he knows claim that ITU does NOT have CONSENSUS on this. If this
> is the case, then I guess there is no problem, cause those
> people will then BLOCK the CONSENT in ITU, no?

well, I guess so - but I'm concerned about that IESG is about to
approve a document that are not up to the quality that
we've pushing on other authors, if I sent this to IESG - it would
have been bounced on the nits within 10 minutes

(note - the only informational document I've first hand experience
with is the documenation of the cr-ldp decission, but I've the
feeling that similar problems actually held that document until they
were taken care of)

I'm not counting on internal ITU politics to do our job

> Or are those ITU-goers a very small minority in ITU and are they
> trying to do an end-run around the ITU process and trying to block
> things by convincing us (IESG) to not approve assignment of 
> the reuqired numbers in RSVP and LDP namespaces?

have no idea - don't go to ITU, don't want to block good standards,
but want to have proper documents

> 
> 
>>I'm also a bit concerned with the statements on the possibility
>>to document after approval - seems to be a queer process, and not
>>something that I've seen before.
>>
> 
> When technical changes are expected, then we should indeed not go
> that path. When it is a matter of clarifications that we can
> identify, then I have seen that happen many times, even at 48-hour
> author-call from RFC-Editor.

so this is the formula you could use to do something along the lines
I proposed in an earlier mail

> 
> 
>>As for rsvp I've not reviewed it carefully enough, but at least if
>>the use of non-IP addresses are in there I guess it should be a no.
>>
> 
> They are. Funny thing here is that they ask for assignments mostly
> in FCFS space (and the one or 2 code points that are not in FCFS
> space could easily be moved into FCFS space), and so I do not see
> how IANA (or we) can actually block/reject such assignments.
> 
> 
>>But just to point on the complexity here, the Bala and Lin drafts
>>includes normative references to
>>"OIF-UNI-01.0, User Network Interface (UNI) 1.0 Signaling 
>>Specification"
>>that specification specifies at least one new LDP message (Status
>>Enquiry Message) and several TLVs. I'm not aware of that we have 
>>approved those, they are not in the IANA registry.
>>
> 
> Scott and I noticed that when evaluating over the last weekend.
> Since the ASON CR-LDP doc that we Last Called indeed has a normative
> reference to the bala document, and since it makes sub-assignments
> udnerneath some of the code point of the bala document, it seemed
> that we more-or-less did an implicit Last Call for the bala doc.

I can only speak for myself - and I was not aware of this - if for no
other reason the ason cr-ldp doc do not separate into normative and
non-normative references

> In any event, no one brought this up yet except you do at this point.
> So we assumed that by having IETF consensus on the ASON CRLDP doc
> we can defend that it also approves the bala doc. This is possibly
> a trouble-some assumption... Scott and I understand that. And we
> have presented the issue in similar wording to the IESG, so the
> whole IESG is aware and can decide on this.
> 
> Do you see our reasoning as seriously flawed here?

you might get away with that reasoning, but I really would like it
out in the open, it would have been possible to last call all three
documents together

> 
> 
>>If the IESG go about approving those drafts does this come to that
>>the LDP extensions in the normative references are approved?
>>
> 
> See above. The answer is yes. the 3 docs:
>   draft-lin-ccamp-gmpls-ason-rsvpte-04.txt
>   draft-aboulmagd-ccamp-crldp-ason-ext-02.txt
>   draft-bala-uni-ldp-rsvp-extensions-04.txt
> basically go together. They document (with ptrs to OIF and ITU docs
> for details) the RSVP and CR-LDP code points requested for ASON
> stuff. ITU has asked (cia a liason statement) back in May 2002
> (I thijnk that was the month) that we review their docs and 
> approve the request to IANA for assignments. 

this concerns me - how far do the indirection go? ptr to a doc with a
ptr to a doc with a ptr to a doc ....

was that liaison sent to SubIP, ccamp or the mpls wg?

> 
> 
>>The ason cr-ldp draft references the
>>       B. Rajagopalan, User Network Interface (UNI) 1.0 Signaling
>>       Specification, OIF-UNI-01.1, October 2001.
>>
>>if this is not the (and it shouldn't if there is any meaning to the
>>OIF-UNI-01.0 vs. OIF-UNI-01.1 I can't find it on the OIF page, but I
>>guess that it will include the same extensions to LDP.
>>
> 
> So it seems we need to clarify the exact reference. I am sending
> then a question about this.

saw the answer - and it just strengthen the feeling I've on that the
ason cr-ldp is not very well thought through and reviewed

> 
> 
>>I guess I'm confused and in need of the (G)MPLS change process.
>>
> 
> We should have had proper IANA Considerations for RSVP (which 
> would have caused an earlier IETF Last Call on the RSVP doc
> which now passed without IETF Last Call) and indeed we should
> have had proper "(G)MPLS change control documentation". 
> We cannot say that we have not seen this coming... ITU has been
> working on this for more than a year. So I guess we have to 
> (at least partly) blame ourselves.

agreed - I should have reviewed the ITU work back in May

> 
> Thanks for your continued input and review. It is appreciated,
> even though it causes us some trouble at this late time.
> 
> Main question I want answered from this email:
>   - if you read the OIF and ITU documents, does that more or less
>     make the stuff acceptable (let us say at least to the point
>     that things are properly documented).

So far I think the OIF document is pretty good as far as documentation
goes, but it contained stuff that I'm not entirely happy with
technically and that I was not aware of before this - part of the
problem is that it is not an open process that we can
influence, if the ITU docs are of the same quality that would be good,
but it would still leave the ason cr-ldp as severely sub-quality

> But answer/reaction to all of my statements above would be helpful
> too.

ok - I've tried :)

<IETF-participant>





From owner-ietf@ietf.org  Thu Jan 23 11:13:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11726;
	Thu, 23 Jan 2003 11:13:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bk1s-0000U6-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 11:16:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bgnf-0000sm-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 07:49:43 -0500
Received: from auemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04525;
	Thu, 23 Jan 2003 07:43:14 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0NCkdW13196;
	Thu, 23 Jan 2003 07:46:39 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ268SR9>; Thu, 23 Jan 2003 13:46:38 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE4B4@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        Kireeti Kompella
	 <kireeti@juniper.net>
Cc: Bob Braden <braden@ISI.EDU>, iesg@ietf.org, ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 13:46:25 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

I noticed today that I gave an incorrect answer to one of
Kireeti's points. He asked and I answered:

> > I would like to know what the intent is in not granting
> > "the right to produce derivative works",
> Did Steve Trowbridge not answer the first question?
> 
This is in the Draft-aboulmagd-crldp-ason-ext-02.txt document.
It states:

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026 except that the right to
   produce derivative works is not granted.

But this is OK since this is documenting ITU material.

Bert and Scott





From owner-ietf@ietf.org  Thu Jan 23 11:34:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12450;
	Thu, 23 Jan 2003 11:34:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bkJh-0003KL-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 11:35:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bkJH-0003CJ-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 11:34:35 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12241;
	Thu, 23 Jan 2003 11:28:00 -0500 (EST)
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0NGTuG00879;
	Thu, 23 Jan 2003 11:29:56 -0500 (EST)
Received: from lucent.com (sjtrowbridge.lra.lucent.com [135.248.252.19]) by ihmail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id KAA21032; Thu, 23 Jan 2003 10:29:41 -0600 (CST)
Message-ID: <3E301869.A3D7E7C4@lucent.com>
Date: Thu, 23 Jan 2003 09:29:29 -0700
From: Stephen Trowbridge <sjtrowbridge@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD EMS-1.5  (Windows NT 5.0; U)
X-Accept-Language: en,zh
MIME-Version: 1.0
To: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
CC: cdel@firsthand.net, iesg@ietf.org, ietf@ietf.org,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)" <sob@harvard.edu>, kireeti@juniper.net,
        "Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Malcolm Betts (E-mail)" <betts01@nortelnetworks.com>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Dimitrios Pendarakis (E-mail)" <DPendarakis@tellium.com>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
References: <D3F8FD817CC7DA408AEB2CAC631C042A98E5FD@nj7460exch012u.ho.lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Christian,
Zhi has captured the essence.
ITU-T has several classes of membership:
- The highest, since ITU is an organization under the umbrella of the United
  Nations, are "member states". This consists of the 190 or so countries that
  are members of the United Nations. In study groups that deal with regulatory
  and tariff issues, the governments are often sources of some of the material
  to be considered. In a more technical study group (like Study Group 15),
  governments tend to fill the role of determining if there is consensus of
  industry within the country, and forwarding that as a national position.
- The next class of membership is Recognized Operating Agencies. These are
  network operators.
- The next class (equivalent in rights to the operators) is called Scientific
  and Industrial Organizations. While any such organization can join, these
  are generally equipment or component vendors.
- The final class are called "Associates", who pay a lower level of dues to
  participate in a single Study Group.
Each country can determine their own national process through which national
positions are determined. In the US, it is customary to take proposed national
positions first to a related US standards organization (ANSI committee T1X1
for most of ITU-T Study Group 15) to develop the industry consensus, and then
to a US State Department committee (US Study Group B is the one which feeds
Study Group 15) which generally (not always) follows the recommendation of the
US standards organization in whether something should be forwarded as a national
position under the "member state" membership. Since in most cases, the national
standards organizations have looked at these documents first, the meetings of
the US State Department committees tend to be relatively short (1/2 day or so,
often by conference call).

As far as I understand the UK process, they have a national committee per
ITU-T Study Group which can approve national positions when there is industry
consensus. Since the UK does not have similar national standards organizations,
they must also look into the technical details of the contributions. This
results in a longer meeting (I think a couple of days, from what I have heard)
to develop any UK national positions for ITU-T Study Group 15.

Getting a national position in countries with significant industrial participation
is no small feat, so contributions such as this are generally taken very seriously.
Hope this helps.
Steve

"Lin, Zhi-Wei (Zhi)" wrote:
> 
> Hi Christian,
> 
> This is one of the processes within the ITU-T standards body. The documents that is submitted into these documents can have multiple levels of "status". I'm not sure what the process is within the UK, but I have some idea of the process within the USA. Maybe Stephen Trowbridge or others more familiar with the procedures can comment (I typically try to stay away from these and stick my head into the technical stuff).
> 
> The lowest status is that a document is sent by a company. In this case only that company is known to support this. A document may also have multiple company names as contributors, in which case these companies are active proponents.
> The next level status is a country document. A country document (e.g., USA or UK) means that the document has undergone a national standards process, and that ALL the companies represented within that country will support the position stated by the document.
> 
> This is of course much different from the IETF process, where all documents are by individual basis (theoretically it should not even have company affiliation but only represents the views of the individuals in the author list, but of course practically most people who attends and submits documents are actually representing a company view)...please don't flame me, just giving an observation based on my limited exposure to the IETF process...
> 
> Hope this helps
> 
> Zhi
> 
> -----Original Message-----
> From: Christian de Larrinaga [mailto:cdel@firsthand.net]
> Sent: Thursday, January 23, 2003 10:17 AM
> To: Lin, Zhi-Wei (Zhi); iesg@ietf.org; ietf@ietf.org; Wijnen, Bert
> (Bert); Scott Bradner (E-mail); kireeti@juniper.net
> Cc: Stephen Shew (E-mail); Lyndon Ong (E-mail); Malcolm Betts (E-mail);
> Lam, Hing-Kam (Kam); Alan McGuire (E-mail); sjtrowbridge@lucent.com;
> Dimitrios Pendarakis (E-mail)
> Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
> 
> Lin Zhi-Wei
> 
> You mention a UK national position paper. Can you give me the references and
> what made this "national"?
> 
> many thanks,
> 
> Christian de Larrinaga
> 
> > A clear U.K. national position paper was
> >contributed to the meeting currently underway
> >(delayed contribution 483), supporting that all
> >three of the ASON signaling Recommendations
> >should be put for consent at this meeting.
> >Hope this helps...
> >Zhi



From owner-ietf@ietf.org  Thu Jan 23 11:43:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12801;
	Thu, 23 Jan 2003 11:43:37 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bkUM-0003yI-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 11:46:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bkTC-0003tA-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 11:44:50 -0500
Received: from mailb.telia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12638;
	Thu, 23 Jan 2003 11:38:15 -0500 (EST)
Received: from d1o888.telia.com (d1o888.telia.com [213.67.172.241])
	by mailb.telia.com (8.12.5/8.12.5) with ESMTP id h0NGfOEI007399;
	Thu, 23 Jan 2003 17:41:25 +0100 (CET)
X-Original-Recipient: iesg@ietf.org
Received: from pi.se (h70n2fls31o888.telia.com [213.64.120.70])
	by d1o888.telia.com (8.10.2/8.10.1) with ESMTP id h0NGfO208635;
	Thu, 23 Jan 2003 17:41:24 +0100 (CET)
Message-ID: <3E30199F.7060200@pi.se>
Date: Thu, 23 Jan 2003 17:34:39 +0100
From: Loa Andersson <loa@pi.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
CC: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)"
 <sob@harvard.edu>,
        "'iesg@ietf.org'" <iesg@ietf.org>, "'ietf@ietf.org'"
 <ietf@ietf.org>,
        "'kireeti@juniper.net'" <kireeti@juniper.net>,
        "Lam, Hing-Kam
 (Kam)" <hklam@lucent.com>,
        "Malcolm Betts (E-mail)"
 <betts01@nortelnetworks.com>,
        "Stephen Shew (E-mail)"
 <sdshew@nortelnetworks.com>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Alan
 McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Trowbridge, Stephen J (Steve)"
 <sjtrowbr@ihmail.ih.lucent.com>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
References: <D3F8FD817CC7DA408AEB2CAC631C042A98E5F5@nj7460exch012u.ho.lucent.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

All,

Zhi-Wei is right this is procedural and intentionally so.

I do not criticize "ITU" or people that are active in the ITU for not
following the IETF procedures, especially since there is a big hole in
the procedural framework here.

The only one to blame for the lack in procedure are ourselves :(, but we
can't cry over spilled milk, but need to do something about it.

What I'm saying is that what happened here very acutely demonstrates
this need to document such a  procedure.

/Loa

Lin, Zhi-Wei (Zhi) wrote:
> Hi Loa,
> 
> See comments below...I guess none of these comments are technical, but more procedural...
> 
> -----Original Message-----
> From: Loa Andersson [mailto:loa@pi.se]
> Sent: Thursday, January 23, 2003 6:59 AM
> To: Lin, Zhi-Wei (Zhi)
> Cc: Wijnen, Bert (Bert); Scott Bradner (E-mail); 'iesg@ietf.org';
> 'ietf@ietf.org'; 'kireeti@juniper.net'; Lam, Hing-Kam (Kam); Malcolm
> Betts (E-mail); Stephen Shew (E-mail); Lyndon Ong (E-mail); Alan McGuire
> (E-mail); Trowbridge, Stephen J (Steve)
> Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
> 
> 
> All,
> 
> taking a step back - I think we are discussing several issues in a mix
> that makes it very hard to sort this out.
> 
> 1. What other organizations may do to IETF (in this context (G)MPLS)
>     protocols
> 
>     This won't be sorted out in this thread - and the only opinion so far
>     is that it is a bad idea to let anyone else change or extend IETF
>     protocols.
> 
> <zhi>Last time I checked, the IETF didn't change the protocols, individuals did through contributions.  The extensions requested for Call/Connection control were submitted by an individual.  The fact the ITU weighed in requesting approval of the changes is a separate issue.</zhi>
> 
> 
>     This will require at statement from involved wg chairs and ADs and an
>     approval from the IESG. I will push for such a statement.
> 
> 2. Have the IETF protocols been changed
> 
>     This is is a matter of how "changed" is defined. Clearly the OIF
>     UNI signaling spec extends the LDP protocol, message and new TLV.
>     This is referenced by a normative reference in the three drafts
>     discussed here
> 
>        draft-lin-ccamp-gmpls-ason-rsvpte-04.txt
>        draft-aboulmagd-ccamp-crldp-ason-ext-02.txt
>        draft-bala-uni-ldp-rsvp-extensions-04.txt
> 
>     I understand that the IESG wants to treat those as a packet, and that
>     the last call on the CR-LDP Extensions for ASON to Informational in
>     fact is a last call on all three of them. Further this could be
>     construed to be seen as an "last call" on normative references -
>     after all normative references are considered to necessary for
>     implementing a spec.
> 
>     Also, the ITU work extends the IETF protocols, new objects, new TLVs
>     and new error codes, that is why the drafts were written - to make it
>     possible for IANA to approve the needed code points.
> 
>     In our normal use of terms change includes extends, but we should
>     probably make that clear.
> 
>     The consequence of approving the drafts will be that the extensions
>     by OIF and ITU will be approved by the IETF. I'm not sure that this
>     has been in the open.
> 
> <zhi>This has been presented at the last few IETF ccamp meetings. I don't know how else to make it more clear the intention.</zhi>
> 
> 
>     However, not having a change process that relates to these protocols
>     I'm not sure if the IESG can do anything else than approving that the
>     IANA allocate the code points.
> 
> 3. The quality of the drafts
> 
>     In my opinion (if I were to review them as a wg chair, but I'm not
>     sure that those criteria apply to informational documents) we have a
>     problem here.
> 
>     The draft-lin-ccamp-gmpls-ason-rsvpte-04.txt and the
>     draft-bala-uni-ldp-rsvp-extensions-04.txt is an a shape such that I
>     would (reluctantly) request publishing.
> 
>     But the draft-aboulmagd-ccamp-crldp-ason-ext-02.txt is not, there is
>     a long series of points that needs to be updated. References, TLV
>     description, un-expanded acronyms, etc. Would have returned this to
>     the author for further work. Aside from that I have a couple of
>     technical issues.
> 
>     Now, if the IESG considers them to be a package, this would effect
>     all of them. I guess that it would be possible to weed the draft
>     after it has been approved, but it deviates from normal practice.
> 
> My belief is that we should try to separate these issues from each
> other.
> 
> /Loa
> 
> 
> 


-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se





From owner-ietf@ietf.org  Thu Jan 23 12:25:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13943;
	Thu, 23 Jan 2003 12:25:49 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bl73-0005UT-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 12:26:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bl6u-0005SY-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 12:25:52 -0500
Received: from lightwave.chromisys.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13843;
	Thu, 23 Jan 2003 12:19:20 -0500 (EST)
Received: by lightwave.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <4GJZ1V72>; Thu, 23 Jan 2003 09:22:33 -0800
Message-ID: <9D42C6E086250248810DCADA39CE7EFC972174@nimbus>
From: John Drake <jdrake@calient.net>
To: "'Lin, Zhi-Wei (Zhi)'" <zwlin@lucent.com>,
        "Wijnen, Bert (Bert)"
	 <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)" <sob@harvard.edu>,
        "'iesg@ietf.org'" <iesg@ietf.org>, "'ietf@ietf.org'" <ietf@ietf.org>,
        "'kireeti@juniper.net'" <kireeti@juniper.net>
Cc: "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Malcolm Betts (E-mail)"
	 <betts01@nortelnetworks.com>,
        "Stephen Shew (E-mail)"
	 <sdshew@nortelnetworks.com>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Trowbridge, Stephen J (Steve)" <sjtrowbr@ihmail.ih.lucent.com>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 09:22:32 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Snipped

-----Original Message-----
From: Lin, Zhi-Wei (Zhi) [mailto:zwlin@lucent.com]
Sent: Thursday, January 23, 2003 12:24 AM
To: Wijnen, Bert (Bert); Scott Bradner (E-mail); 'iesg@ietf.org';
'ietf@ietf.org'; 'kireeti@juniper.net'
Cc: Lam, Hing-Kam (Kam); Malcolm Betts (E-mail); Stephen Shew (E-mail);
Lyndon Ong (E-mail); Alan McGuire (E-mail); Trowbridge, Stephen J
(Steve)
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational




<zhi> Where do you see that we deprecate ResvErr and ResvTear? (for the
record: these are not deprecated)
Where do you see that we deprecate FILTER_SPEC and LABEL objects? (for the
record: these are not deprecated)
Also, where do you see that we wish to identify the RSVP session endpoints
with GENERALIZED_UNI? (for the record: the RSVP session is still SESSION
object)
</zhi>


============================================================================
====================================
JD:  I've obviously misread the follwing text:

"Note that from the perspective of the ASON model ResvErr and ResvTear
messages are not used. For backwards compatibility, when an ASON-compliant
GMPLS node receives either a ResvErr or ResvTear as a response during the
setup phase of message exchange, the GMPLS-ASON node should instead issue a
PathTear message downstream and a PathErr (with Path_State_Removed flag set)
message upstream. This is so that RSVP states are immediately removed upon
error during the setup process." 

"... the SPC services support for the ASON model uses the GENERALIZED_UNI
object for this extension to help    align the model for both switched
connection and soft permanent connection, as well as to use the service
level and diversity attributes of the GENERALIZED_UNI object"

"Note that although the GENERALIZED_UNI and CALL_ID objects are optional for
GMPLS signaling, these objects are mandatory for ASON-compliant networks,
i.e., the Path message MUST include both GENERALIZED_UNI and CALL_ID
objects." 

"Note that LABEL_REQUEST, SENDER_TSPEC and UPSTREAM_LABEL are not required
for a call; however these are mandatory objects. As such, for backwards
compatibility purposes processing of these objects for a call follows the
following rules: 
    
   -    These objects are ignored on receipt; however, a valid-formatted 
        object (e.g., by using the received valid object in the 
        transmitted message) must be included in the generated message." 
============================================================================
====================================   


<zhi>The statement above about G.709 is irrelevant to the discussion. In
terms of sending G.7713 to IETF and asking to develop protocol...that's what
was done. Back on 2001 discussions were started on what requirements and
architectures are needed to support G.8080. Individuals (who happens to
participate in both IETF and ITU) then started submitting protocol
extensions. People either choose to ignore these or expressed opposition to
making these extensions simply because it went beyond the traditional IP
services.</zhi>


JD:  What you saying is not the same as what I am saying.  I am asking for
G.7713 to be sent as a formal liason to the IETF (CCAMP).  I am not asking
for individuals' interpretations of ITU specs.


<zhi>Existing mechanisms we mentioned may be used, but the preference would
be to use GEN_UNI for SPC (and this is in fact what we use for the ASON
specification). This is because (again) of the architecture assumptions made
in G.8080. An ASON network is assumed to be composed of multiple domains. In
the vision of a global ASON network you might have multiple carriers
connecting together (but also multiple domains within a single carrier
network). The interfaces defined for these inter-domain signaling is the
E-NNI interface. However, across an E-NNI the ERO object is an optional
object, and in certain instances the information may not be passed due to
policies that carriers may impose on the inter-domain interface.

If we were to use the ERO to carry the SPC information, then conceivably
there are cases where this information would not pass the interface.</zhi>


JD:  What standards body has defined the E-NNI? 


<zhi>I hope this helps to explain the issues expressed by John (of course I
expected John to understand call/connection as he was a member of ATM Forum
in developing the PNNI specification...)


JD:  During my time at the ATM Forum we were never able to get
call/connection to work.



From owner-ietf@ietf.org  Thu Jan 23 13:49:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16361;
	Thu, 23 Jan 2003 13:49:25 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bmPW-0004RP-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 13:49:10 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bmMB-0004Jc-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 13:45:43 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16122;
	Thu, 23 Jan 2003 13:39:09 -0500 (EST)
Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.6) with ESMTP id h0NIgGB6021475;
	Thu, 23 Jan 2003 10:42:16 -0800 (PST)
Received: from cisco.com (sjc-vpn2-769.cisco.com [10.21.115.1])
	by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with SMTP id ADT05715;
	Thu, 23 Jan 2003 10:31:32 -0800 (PST)
Received: by cisco.com (sSMTP sendmail emulation); Thu, 23 Jan 2003 13:42:15 -0500
Date: Thu, 23 Jan 2003 13:42:15 -0500
From: Scott W Brim <sbrim@cisco.com>
To: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
Cc: Loa Andersson <loa@pi.se>, "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)" <sob@harvard.edu>,
        "'iesg@ietf.org'" <iesg@ietf.org>, "'ietf@ietf.org'" <ietf@ietf.org>,
        "'kireeti@juniper.net'" <kireeti@juniper.net>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Malcolm Betts (E-mail)" <betts01@nortelnetworks.com>,
        "Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Trowbridge, Stephen J (Steve)" <sjtrowbr@ihmail.ih.lucent.com>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
Message-ID: <20030123184215.GK2000@SBRIM-W2K1>
Mail-Followup-To: Scott W Brim <sbrim@cisco.com>,
	"Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>, Loa Andersson <loa@pi.se>,
	"Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
	"Scott Bradner (E-mail)" <sob@harvard.edu>,
	"'iesg@ietf.org'" <iesg@ietf.org>,
	"'ietf@ietf.org'" <ietf@ietf.org>,
	"'kireeti@juniper.net'" <kireeti@juniper.net>,
	"Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
	"Malcolm Betts (E-mail)" <betts01@nortelnetworks.com>,
	"Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
	"Lyndon Ong (E-mail)" <lyong@ciena.com>,
	"Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
	"Trowbridge, Stephen J (Steve)" <sjtrowbr@ihmail.ih.lucent.com>
References: <D3F8FD817CC7DA408AEB2CAC631C042A98E5F5@nj7460exch012u.ho.lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D3F8FD817CC7DA408AEB2CAC631C042A98E5F5@nj7460exch012u.ho.lucent.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, Jan 23, 2003 08:35:24AM -0500, Lin, Zhi-Wei (Zhi) allegedly wrote:
> 1. What other organizations may do to IETF (in this context (G)MPLS)
>    protocols 
> 
>     This won't be sorted out in this thread - and the only opinion so
>     far is that it is a bad idea to let anyone else change or extend
>     IETF protocols.
> 
> <zhi>Last time I checked, the IETF didn't change the protocols, individuals did through contributions.  The extensions requested for Call/Connection control were submitted by an individual.  The fact the ITU weighed in requesting approval of the changes is a separate issue.</zhi>

Individuals bring in contributions (e-mail, drafts, opinions), but
whenever a "contribution" impacts standards or standards-track ideas,
the IETF structure decides what goes into standards and assigned
numbers.  

At the time of the creation of the "sub-IP" area, a lot of thought went
into what the IETF should try to control and what it shouldn't.  It's
evolved some but basically any changes to the IP protocols themselves
are closely controlled, or the situation gets out of hand.  Things which
use those protocols do not have to be.  This is a well-established
principle.




From owner-ietf@ietf.org  Thu Jan 23 14:09:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16860;
	Thu, 23 Jan 2003 14:09:06 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bml6-0005kS-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 14:11:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bk2M-0000aA-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 11:17:06 -0500
Received: from w2ksjexg01.ciena.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11561;
	Thu, 23 Jan 2003 11:10:33 -0500 (EST)
Received: from wntcsdexg01.csd.ciena.com ([10.34.31.31]) by w2ksjexg01.ciena.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id C2BQNJQL; Thu, 23 Jan 2003 08:13:47 -0800
Received: by webdev-llnt.oni.com with Internet Mail Service (5.5.2653.19)
	id <Y5W9M1CD>; Thu, 23 Jan 2003 08:13:59 -0800
Message-ID: <2135200C183FD5119588009027DE572302836BF3@webdev-owa.oni.com>
From: "Ong, Lyndon" <LyOng@ciena.com>
To: "'Loa Andersson'" <loa@pi.se>, "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)"
	 <sob@harvard.edu>,
        "'iesg@ietf.org'" <iesg@ietf.org>, "'ietf@ietf.org'"
	 <ietf@ietf.org>,
        "'kireeti@juniper.net'" <kireeti@juniper.net>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Malcolm Betts (E-mail)"
	 <betts01@nortelnetworks.com>,
        "Stephen Shew (E-mail)"
	 <sdshew@nortelnetworks.com>,
        "Alan McGuire (E-mail)"
	 <alan.mcguire@bt.com>,
        "Trowbridge, Stephen J (Steve)"
	 <sjtrowbr@ihmail.ih.lucent.com>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 08:13:55 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Folks,

I can reaffirm Zhi's comment that call and connection separation 
goes back to G.8080, an already approved ITU specification of
the G.ASON architecture.

I'm a bit puzzled by the argument that no one but IETF should be
allowed to extend an IETF protocol - I would think that extensions
are generally allowed if they don't cause a limitation on 
the available codepoints and are documented to allow people
to use them.  Aren't some codepoint 
partitions designed for people to do this, without having to 
force all extension work through a WG?

Also, I would think that approving the drafts is just that,
approving the drafts and their contents as Informational
documents, it is not being asked that these become IETF Standards.
  

Cheers,

Lyndon Ong  



-----Original Message-----
From: Loa Andersson [mailto:loa@pi.se]
Sent: Thursday, January 23, 2003 3:59 AM
To: Lin, Zhi-Wei (Zhi)
Cc: Wijnen, Bert (Bert); Scott Bradner (E-mail); 'iesg@ietf.org';
'ietf@ietf.org'; 'kireeti@juniper.net'; Lam, Hing-Kam (Kam); Malcolm
Betts (E-mail); Stephen Shew (E-mail); Ong, Lyndon; Alan McGuire
(E-mail); Trowbridge, Stephen J (Steve)
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational


All,

taking a step back - I think we are discussing several issues in a mix
that makes it very hard to sort this out.

1. What other organizations may do to IETF (in this context (G)MPLS)
    protocols

    This won't be sorted out in this thread - and the only opinion so far
    is that it is a bad idea to let anyone else change or extend IETF
    protocols.

    This will require at statement from involved wg chairs and ADs and an
    approval from the IESG. I will push for such a statement.

2. Have the IETF protocols been changed

    This is is a matter of how "changed" is defined. Clearly the OIF
    UNI signaling spec extends the LDP protocol, message and new TLV.
    This is referenced by a normative reference in the three drafts
    discussed here

       draft-lin-ccamp-gmpls-ason-rsvpte-04.txt
       draft-aboulmagd-ccamp-crldp-ason-ext-02.txt
       draft-bala-uni-ldp-rsvp-extensions-04.txt

    I understand that the IESG wants to treat those as a packet, and that
    the last call on the CR-LDP Extensions for ASON to Informational in
    fact is a last call on all three of them. Further this could be
    construed to be seen as an "last call" on normative references -
    after all normative references are considered to necessary for
    implementing a spec.

    Also, the ITU work extends the IETF protocols, new objects, new TLVs
    and new error codes, that is why the drafts were written - to make it
    possible for IANA to approve the needed code points.

    In our normal use of terms change includes extends, but we should
    probably make that clear.

    The consequence of approving the drafts will be that the extensions
    by OIF and ITU will be approved by the IETF. I'm not sure that this
    has been in the open.

    However, not having a change process that relates to these protocols
    I'm not sure if the IESG can do anything else than approving that the
    IANA allocate the code points.

3. The quality of the drafts

    In my opinion (if I were to review them as a wg chair, but I'm not
    sure that those criteria apply to informational documents) we have a
    problem here.

    The draft-lin-ccamp-gmpls-ason-rsvpte-04.txt and the
    draft-bala-uni-ldp-rsvp-extensions-04.txt is an a shape such that I
    would (reluctantly) request publishing.

    But the draft-aboulmagd-ccamp-crldp-ason-ext-02.txt is not, there is
    a long series of points that needs to be updated. References, TLV
    description, un-expanded acronyms, etc. Would have returned this to
    the author for further work. Aside from that I have a couple of
    technical issues.

    Now, if the IESG considers them to be a package, this would effect
    all of them. I guess that it would be possible to weed the draft
    after it has been approved, but it deviates from normal practice.

My belief is that we should try to separate these issues from each
other.

/Loa



-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se







From owner-ietf@ietf.org  Thu Jan 23 14:09:07 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16863;
	Thu, 23 Jan 2003 14:09:06 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bml7-0005kY-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 14:11:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bkXH-00045N-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 11:49:03 -0500
Received: from zcars0m9.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12745;
	Thu, 23 Jan 2003 11:42:27 -0500 (EST)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h0NGjo020271;
	Thu, 23 Jan 2003 11:45:50 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <DPZ2NZP5>; Thu, 23 Jan 2003 11:45:50 -0500
Message-ID: <0D7FC1D8D861D511AEA70002A52CE5E604343B6D@zcard0ke.ca.nortel.com>
From: "Stephen Shew" <sdshew@nortelnetworks.com>
To: "'Lin, Zhi-Wei (Zhi)'" <zwlin@lucent.com>,
        "'iesg@ietf.org'"
	 <iesg@ietf.org>, "'ietf@ietf.org'" <ietf@ietf.org>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)"
	 <sob@harvard.edu>,
        "'kireeti@juniper.net'" <kireeti@juniper.net>
Cc: "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Malcolm Betts" <betts01@nortelnetworks.com>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "'sjtrowbridge@lucent.com'" <sjtrowbridge@lucent.com>,
        "Dimitrios Pendarakis (E-mail)" <DPendarakis@tellium.com>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 11:45:49 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2C2FE.E145F418"
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_01C2C2FE.E145F418
Content-Type: text/plain

I agree with Zhi-Wei's points below.  On the matter of concensus I think the
original email implied "agreement" as opposed to the ITU-T meaning of
"consent".  The existence of the G.8080 and G.7713 (which are ITU-T
"consented") do mean that call and connection separation are agreed to in
the ITU-T.  This is why the notion is contained in all three signalling
draft recommendations (G.7713.x).  The call/connection architecture is well
established in ISDN and B-ISDN documents and so I think there is very wide
agreement on this concept.
 
As far as the call being carried by the connection, this is one of two call
setup models and has been called "logical separation".  In the second model,
the call is in fact separated from connection setup.  In either case, the
separation is useful for ASON services in that allows the transport network
to support calls with capabilities like redialing for restoration and setup
of diverse virtually concatenated connections.

-----Original Message-----
From: Lin, Zhi-Wei (Zhi) [mailto:zwlin@lucent.com] 
Sent: Wednesday, January 22, 2003 14:09
To: 'iesg@ietf.org'; 'ietf@ietf.org'; Wijnen, Bert (Bert); Scott Bradner
(E-mail); 'kireeti@juniper.net'
Cc: Shew, Stephen [SKY:QW33:EXCH]; Lyndon Ong (E-mail); Betts, Malcolm
[SKY:1ID0:EXCH]; Lam, Hing-Kam (Kam); Alan McGuire (E-mail); Lin, Zhi-Wei
(Zhi); 'sjtrowbridge@lucent.com'; Dimitrios Pendarakis (E-mail)
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational


Hi,
 
I wanted to respond to some of the comments raised by Kireeti.

With respect to the issue re call and connection separation, call and
connection separation is an architectural requirement that is fully
documented within Rec. G.8080.  Rec. G.8080 was liaised to the IETF quite
some time ago (it was Approved end  '01; Consented Oct. '01), and at every
meeting of the IETF for the past few meetings, there have been status
updates provided on associated ITU-T work efforts.    As you may recall, Kam
sent out an email earlier in reply to some other comments on where these
documents can be obtained.  Rec. G.7713, which also reflects call and
connection separation, was also sent to the IETF almost a year ago upon it's
Approval end of  '01

To find the information that has been transmitted from ITU-T to IETF on this
subject (from 26 October 2001), see:

ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15opticaltransport/COMMUNICATION
S/index.html
<ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15opticaltransport/COMMUNICATIO
NS/index.html> 

In terms of the formatting of the CALL_ID, Kireeti raised a question as to
why IP addresses only were not sufficient.   The answer to this illustrates
one  difference between the IETF and ITU-T scope.   The focus of the IETF is
upon IP-based client services while ITU-T has a multi-service focus,
including not only IP but also other types of services (such as ATM). As
such, it cannot be assumed that all NEs have IP addresses associated with
them. In addition, it cannot be assumed that, even if the NE has an IP
address, that those IP addresses are globally unique. As such, it was
necessary to come up with a identifier format that does not assume the
global uniqueness of an address.   The selected approach was to re-use
existing identifier formats (e.g., from the TTI format such as G.709) that
provides "free" globally unique identifiers.

As mentioned in the documentation for G.7713.x, the CALL_ID IS and NS is
used only when "global" uniqueness is needed. In the event that networks are
just been deployed or it's a single carrier's network where their addressing
space is unique, then they can use the "operator specific" CALL_ID format.
In this format the CALL_ID is essentially the IP address (if the type is
4-byte or 16-byte variety).

In terms of the "didn't hear a clear consensus on the need for this", the
text was published in Report COM15-24 (Part IIA of the report of WP 3/15).
According to ITU-T practice, inclusion in part IIA indicates that the text
is "agreed", although not at the point of "consent" ready to issue for a
Last Call. The agreement to place text in part IIA of a report occurs at the
final plenary of the Study Group meeting. This meeting was attended by
approximately 300 participants. The reason that the text was not put for
consent at the May 2002 meeting of Study Group 15 was to provide time for
comments on the text in response to liaisons sent to IETF ccamp and the ATM
forum, and to allow IANA assigned codepoints to be included in the document.
A clear U.K. national position paper was contributed to the meeting
currently underway (delayed contribution 483), supporting that all three of
the ASON signaling Recommendations should be put for consent at this
meeting.

Hope this helps...

Zhi

 

-----Original Message-----

From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]

Sent: dinsdag 21 januari 2003 16:42

To: Kireeti Kompella

Cc: Bob Braden; iesg@ietf.org; ietf@ietf.org

Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational

 

Inline

> -----Original Message-----

> From: Kireeti Kompella [mailto:kireeti@juniper.net]

> Sent: maandag 20 januari 2003 22:49

> To: Wijnen, Bert (Bert)

> Cc: Bob Braden; iesg@ietf.org; ietf@ietf.org

> Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational

> 

> 

> Hi Bert,

> 

> On Sat, 18 Jan 2003, Wijnen, Bert (Bert) wrote:

> 

> > Yes they are from the "IETF Consensus space".

> >

> > Now can you be more specific as to why you do not consider this doc

> > ready for publication?

> 

> There are a large number of nits and typos -- so much so that in my

> opinion, this document should not have been sent to IETF Last Call

> without another round of edits. However, I will ignore those and

> concentrate on the substance.

> 

It would be great if you can send a list of nits and typos to the

author and copy Scott and Myself, possibly aslo the RFC-Editor.

> I would like to know what the intent is in not granting "the right

> to produce derivative works",

Did Steve Trowbridge not answer the first question?

> and whether the IETF should progress a

> document that is a derivative of IETF protocols with this clause.

> 

I think you meant a colon after "clause" and not a priod?

> The main thrust of the document is the "separation of call and

> connection"; 

> there is one short paragraph that describes this, and

> a reference to an ITU document.

Well, the ITU document should document the details. I don't think

we just want them to copy all their documentation into RFCs, do we?

> In my discussions with people who

> go to the ITU, I didn't hear a clear consensus on the need for this.

>

Well, then they should speak up in ITU I think. The ITU-T SG15 is 

discussing this in their meeting this week, and the technology is

up for consent. Any "people who go to the ITU" (to use your words)

and who do NOT agree with it should then speak up in ITU SG15,

don't you think so?

> An *IETF* document that describes the background, needs and how this

> is to be used would be very useful. This is especially important as

> the very next paragraph says that separation can be achieved "where

> the call set up request is always accaccompanied by a connection

> request", which (to my naive understanding) hardly is separation.

> 

Why would we need them to replicate their own documentation into an

IETF document?

> Secondly, there is a real paucity of detail in the description and

> use of the new messages: the Call Setup Message refers to the OIF

> UNI document for formating and doesn't say much about when and how

> it is to be used; there is no justification for the format of the

> Call ID (why is there an International Segment, etc.? Won't IP

> addresses do? Is this to be used for telephone calls??? My

> recollection is that Fred Baker (then IETF chair) said that using

> CCAMP for telephony was a no-no ....)

> 

I will leave it to the "ITU" folk to answer the details.

But your main point seems to be that you have not seen enough

documentation. ITU-T did a Liason Statement to us, and I believe

even specifically to CCAMP WG (that you co-chair) and so can you

tell me if you read their documentation that they have made

(freely) available to us to check? And after reading that, do

your points still hold. If so, then maybe we (CCAMP) should answer

the Liason Statement and explain to them how and where they should

add more detail and ask specific questions based on what they

document in their "drafts" (or documents) to which they point.

> Call Release can be "sent by any entity of the network". This surely

> can't be correct.

> 

Will let ITU-folk answer that.

> The Call Capability TLV is completely undocumented beyond the format

> of the TLV.

> 

How about in the documents in OIF and ITU that they point to?

> As someone else pointed out, crankback for CR-LDP has already been

> defined. Furthermore, this document does not say what procedures

> the sender and receiver must follow, and how crankback is to be

> effected.

>

What do you mean by "has already been defined" ??

And are the procedures not documented in the documents they point to?



> The "Additional Error Codes" have absolutely no detail about what

> they mean, when they are to be sent, and what the receiver should

> do with them. They also use a slew of unidentified acronyms.

> 

They do in the documents they point to.

Bert

> Kireeti.

> 


------_=_NextPart_001_01C2C2FE.E145F418
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

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

<META content=3D"MSHTML 5.50.4913.1100" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D416432416-23012003><FONT color=3D#008080 size=3D2>I =
agree with=20
Zhi-Wei's points below.&nbsp; On the matter of concensus I think the =
original=20
email implied "agreement" as opposed to the ITU-T meaning of =
"consent".&nbsp;=20
The existence of the G.8080 and G.7713 (which are ITU-T "consented") do =
mean=20
that call and connection separation are agreed to in the ITU-T.&nbsp; =
This is=20
why the notion is contained in all three signalling draft =
recommendations=20
(G.7713.x).&nbsp; The call/connection architecture is well established =
in ISDN=20
and B-ISDN documents and so I think there is very wide agreement on =
this=20
concept.</FONT></SPAN></DIV>
<DIV><SPAN class=3D416432416-23012003><FONT color=3D#008080=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D416432416-23012003><FONT color=3D#008080 size=3D2>As =
far as the=20
call being carried by the connection, this is one of two call setup =
models and=20
has been called "logical separation".&nbsp; In the second model, the =
call is in=20
fact separated from connection setup.&nbsp; In either case, the =
separation is=20
useful for ASON services in that allows the transport network to =
support calls=20
with capabilities like redialing for restoration and setup of diverse =
virtually=20
concatenated connections.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
Lin, Zhi-Wei=20
  (Zhi) [mailto:zwlin@lucent.com] <BR><B>Sent:</B> Wednesday, January =
22, 2003=20
  14:09<BR><B>To:</B> 'iesg@ietf.org'; 'ietf@ietf.org'; Wijnen, Bert =
(Bert);=20
  Scott Bradner (E-mail); 'kireeti@juniper.net'<BR><B>Cc:</B> Shew, =
Stephen=20
  [SKY:QW33:EXCH]; Lyndon Ong (E-mail); Betts, Malcolm [SKY:1ID0:EXCH]; =
Lam,=20
  Hing-Kam (Kam); Alan McGuire (E-mail); Lin, Zhi-Wei (Zhi);=20
  'sjtrowbridge@lucent.com'; Dimitrios Pendarakis =
(E-mail)<BR><B>Subject:</B>=20
  RE: Last Call: CR-LDP Extensions for ASON to=20
Informational<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D251425817-22012003>Hi,</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D251425817-22012003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN class=3D251425817-22012003>I =
wanted to=20
  respond to some of the comments raised by =
Kireeti.</SPAN></FONT></DIV>
  <DIV>
  <P><FONT size=3D2><SPAN class=3D251425817-22012003>With respect to =
the issue re=20
  call and connection separation, call and connection separation is an=20
  architectural requirement that is fully documented within Rec. =
G.8080.&nbsp;=20
  Rec. G.8080 was liaised&nbsp;to the&nbsp;IETF quite some time ago (it =

  was&nbsp;Approved end &nbsp;'01; Consented Oct. '01), and at every =
meeting of=20
  the IETF for the past few meetings, there have been status updates =
provided=20
  on&nbsp;associated&nbsp;ITU-T work efforts.&nbsp;&nbsp;&nbsp; As you =
may=20
  recall, Kam sent out an email earlier in reply to some other comments =
on where=20
  these documents can be obtained.&nbsp; Rec. G.7713, which also=20
  reflects&nbsp;call and connection separation,&nbsp;was also sent to =
the IETF=20
  almost a year ago upon it's Approval end of =
&nbsp;'01</SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D251425817-22012003>To find the =
information that=20
  has been transmitted from ITU-T to IETF on this subject (from 26 =
October=20
  2001), see:</SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D251425817-22012003><A=20
  =
href=3D"ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15opticaltransport/C=
OMMUNICATIONS/index.html">ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15=
opticaltransport/COMMUNICATIONS/index.html</A></SPAN></FONT></P>
  <P><FONT size=3D+0><SPAN =
class=3D251425817-22012003></SPAN></FONT><FONT size=3D2>In=20
  terms of the formatting of the CALL_ID<SPAN =
class=3D251425817-22012003>,=20
  </SPAN>Kireeti<SPAN class=3D251425817-22012003> raised =
a&nbsp;question&nbsp;as=20
  to&nbsp;why </SPAN>IP addresses<SPAN class=3D251425817-22012003> only =
were not=20
  sufficient</SPAN>.&nbsp;<SPAN class=3D251425817-22012003>&nbsp; The =
answer to=20
  this&nbsp;illustrates one&nbsp;</SPAN>&nbsp;difference<SPAN=20
  class=3D251425817-22012003> between the </SPAN>IETF and ITU<SPAN=20
  class=3D251425817-22012003>-T scope</SPAN>.&nbsp;<SPAN=20
  class=3D251425817-22012003>&nbsp; The focus of the =
</SPAN>IETF&nbsp;<SPAN=20
  class=3D251425817-22012003>is up</SPAN>on IP-based client services =
while=20
  ITU<SPAN class=3D251425817-22012003>-T has a multi-service=20
  focus,</SPAN>&nbsp;includ<SPAN class=3D251425817-22012003>ing</SPAN> =
not only IP=20
  but also other types of services (such as ATM). As such<SPAN=20
  class=3D251425817-22012003>,&nbsp;it</SPAN> cannot&nbsp;<SPAN=20
  class=3D251425817-22012003>be </SPAN>assume<SPAN=20
  class=3D251425817-22012003>d</SPAN> that all NEs have IP addresses =
associated=20
  with them. In addition<SPAN =
class=3D251425817-22012003>,</SPAN>&nbsp;<SPAN=20
  class=3D251425817-22012003>it</SPAN> cannot&nbsp;<SPAN=20
  class=3D251425817-22012003>be </SPAN>assume<SPAN=20
  class=3D251425817-22012003>d</SPAN> that, even if the NE has an IP =
address, that=20
  those IP addresses are globally unique. As such<SPAN=20
  class=3D251425817-22012003>, it was necessary</SPAN> to come up with =
a=20
  identifier format that does not assume the global uniqueness of an=20
  address.&nbsp;<SPAN class=3D251425817-22012003>&nbsp; The selected =
approach=20
  </SPAN>was to re-use existing identifier formats (<SPAN=20
  class=3D251425817-22012003>e.g., </SPAN>from the TTI format such as =
G.709) that=20
  provides "free" globally unique identifiers.</FONT></P>
  <P><FONT size=3D2>As mentioned in the documentation for G.7713.x, the =
CALL_ID IS=20
  and NS is used only when "global" uniqueness is needed. In the event =
that=20
  networks are just been deployed or it's a single carrier's network =
where their=20
  addressing space is unique, then they can use the "operator specific" =
CALL_ID=20
  format. In this format the CALL_ID is essentially the IP address (if =
the type=20
  is 4-byte or 16-byte variety).</FONT></P>
  <P><SPAN class=3D251425817-22012003><FONT size=3D2>In terms of the =
"didn't hear a=20
  clear consensus on the need for this", the text was published in =
Report=20
  COM15-24 (Part IIA of the report of WP 3/15). According to ITU-T =
practice,=20
  inclusion in part IIA indicates that the text is "agreed", although =
not at the=20
  point of "consent" ready to issue for a Last Call. The agreement to =
place text=20
  in part IIA of a report occurs at the final plenary of the Study =
Group=20
  meeting. This meeting was attended by approximately 300=20
  participants.&nbsp;</FONT></SPAN><SPAN =
class=3D251425817-22012003><FONT=20
  size=3D2>The reason that the text was not put for consent at the May =
2002=20
  meeting of Study Group 15 was to provide time for comments on the =
text in=20
  response to liaisons sent to IETF ccamp and the ATM forum, and to =
allow IANA=20
  assigned codepoints to be included in the document.&nbsp;A clear U.K. =
national=20
  position paper was contributed to the meeting currently underway =
(delayed=20
  contribution 483), supporting that all three of the ASON signaling=20
  Recommendations should be put for consent at this =
meeting.</FONT></SPAN></P>
  <P><SPAN class=3D251425817-22012003></SPAN><FONT size=3D2>Hope this=20
  helps...</FONT></P>
  <P><SPAN class=3D251425817-22012003><FONT =
size=3D2>Zhi</FONT></SPAN></P>
  <P><SPAN class=3D251425817-22012003><FONT =
size=3D2></FONT></SPAN>&nbsp;</P></DIV>
  <DIV><FONT face=3DArial><FONT face=3DArial>
  <P><FONT size=3D2>-----Original Message-----</FONT></P>
  <P><FONT size=3D2>From: Wijnen, Bert (Bert)=20
  [mailto:bwijnen@lucent.com]</FONT></P>
  <P><FONT size=3D2>Sent: dinsdag 21 januari 2003 16:42</FONT></P>
  <P><FONT size=3D2>To: Kireeti Kompella</FONT></P>
  <P><FONT size=3D2>Cc: Bob Braden; iesg@ietf.org; =
ietf@ietf.org</FONT></P>
  <P><FONT size=3D2>Subject: RE: Last Call: CR-LDP Extensions for ASON =
to=20
  Informational</FONT></P>
  <P><FONT size=3D2></FONT>&nbsp;</P>
  <P><FONT size=3D2>Inline</FONT></P>
  <P><FONT size=3D2>&gt; -----Original Message-----</FONT></P>
  <P><FONT size=3D2>&gt; From: Kireeti Kompella=20
  [mailto:kireeti@juniper.net]</FONT></P>
  <P><FONT size=3D2>&gt; Sent: maandag 20 januari 2003 22:49</FONT></P>
  <P><FONT size=3D2>&gt; To: Wijnen, Bert (Bert)</FONT></P>
  <P><FONT size=3D2>&gt; Cc: Bob Braden; iesg@ietf.org; =
ietf@ietf.org</FONT></P>
  <P><FONT size=3D2>&gt; Subject: RE: Last Call: CR-LDP Extensions for =
ASON to=20
  Informational</FONT></P>
  <P><FONT size=3D2>&gt; </FONT></P>
  <P><FONT size=3D2>&gt; </FONT></P>
  <P><FONT size=3D2>&gt; Hi Bert,</FONT></P>
  <P><FONT size=3D2>&gt; </FONT></P>
  <P><FONT size=3D2>&gt; On Sat, 18 Jan 2003, Wijnen, Bert (Bert)=20
wrote:</FONT></P>
  <P><FONT size=3D2>&gt; </FONT></P>
  <P><FONT size=3D2>&gt; &gt; Yes they are from the "IETF Consensus=20
  space".</FONT></P>
  <P><FONT size=3D2>&gt; &gt;</FONT></P>
  <P><FONT size=3D2>&gt; &gt; Now can you be more specific as to why =
you do not=20
  consider this doc</FONT></P>
  <P><FONT size=3D2>&gt; &gt; ready for publication?</FONT></P>
  <P><FONT size=3D2>&gt; </FONT></P>
  <P><FONT size=3D2>&gt; There are a large number of nits and typos -- =
so much so=20
  that in my</FONT></P>
  <P><FONT size=3D2>&gt; opinion, this document should not have been =
sent to IETF=20
  Last Call</FONT></P>
  <P><FONT size=3D2>&gt; without another round of edits. However, I =
will ignore=20
  those and</FONT></P>
  <P><FONT size=3D2>&gt; concentrate on the substance.</FONT></P>
  <P><FONT size=3D2>&gt; </FONT></P>
  <P><FONT size=3D2>It would be great if you can send a list of nits =
and typos to=20
  the</FONT></P>
  <P><FONT size=3D2>author and copy Scott and Myself, possibly aslo the =

  RFC-Editor.</FONT></P>
  <P><FONT size=3D2>&gt; I would like to know what the intent is in not =
granting=20
  "the right</FONT></P>
  <P><FONT size=3D2>&gt; to produce derivative works",</FONT></P>
  <P><FONT size=3D2>Did Steve Trowbridge not answer the first =
question?</FONT></P>
  <P><FONT size=3D2>&gt; and whether the IETF should progress =
a</FONT></P>
  <P><FONT size=3D2>&gt; document that is a derivative of IETF =
protocols with this=20
  clause.</FONT></P>
  <P><FONT size=3D2>&gt; </FONT></P>
  <P><FONT size=3D2>I think you meant a colon after "clause" and not a=20
  priod?</FONT></P>
  <P><FONT size=3D2>&gt; The main thrust of the document is the =
"separation of=20
  call and</FONT></P>
  <P><FONT size=3D2>&gt; connection"; </FONT></P>
  <P><FONT size=3D2>&gt; there is one short paragraph that describes =
this,=20
  and</FONT></P>
  <P><FONT size=3D2>&gt; a reference to an ITU document.</FONT></P>
  <P><FONT size=3D2>Well, the ITU document should document the details. =
I don't=20
  think</FONT></P>
  <P><FONT size=3D2>we just want them to copy all their documentation =
into RFCs,=20
  do we?</FONT></P>
  <P><FONT size=3D2>&gt; In my discussions with people who</FONT></P>
  <P><FONT size=3D2>&gt; go to the ITU, I didn't hear a clear consensus =
on the=20
  need for this.</FONT></P>
  <P><FONT size=3D2>&gt;</FONT></P>
  <P><FONT size=3D2>Well, then they should speak up in ITU I think. The =
ITU-T SG15=20
  is </FONT></P>
  <P><FONT size=3D2>discussing this in their meeting this week, and the =
technology=20
  is</FONT></P>
  <P><FONT size=3D2>up for consent. Any "people who go to the ITU" (to =
use your=20
  words)</FONT></P>
  <P><FONT size=3D2>and who do NOT agree with it should then speak up =
in ITU=20
  SG15,</FONT></P>
  <P><FONT size=3D2>don't you think so?</FONT></P>
  <P><FONT size=3D2>&gt; An *IETF* document that describes the =
background, needs=20
  and how this</FONT></P>
  <P><FONT size=3D2>&gt; is to be used would be very useful. This is =
especially=20
  important as</FONT></P>
  <P><FONT size=3D2>&gt; the very next paragraph says that separation =
can be=20
  achieved "where</FONT></P>
  <P><FONT size=3D2>&gt; the call set up request is always =
accaccompanied by a=20
  connection</FONT></P>
  <P><FONT size=3D2>&gt; request", which (to my naive understanding) =
hardly is=20
  separation.</FONT></P>
  <P><FONT size=3D2>&gt; </FONT></P>
  <P><FONT size=3D2>Why would we need them to replicate their own =
documentation=20
  into an</FONT></P>
  <P><FONT size=3D2>IETF document?</FONT></P>
  <P><FONT size=3D2>&gt; Secondly, there is a real paucity of detail in =
the=20
  description and</FONT></P>
  <P><FONT size=3D2>&gt; use of the new messages: the Call Setup =
Message refers to=20
  the OIF</FONT></P>
  <P><FONT size=3D2>&gt; UNI document for formating and doesn't say =
much about=20
  when and how</FONT></P>
  <P><FONT size=3D2>&gt; it is to be used; there is no justification =
for the=20
  format of the</FONT></P>
  <P><FONT size=3D2>&gt; Call ID (why is there an International =
Segment, etc.?=20
  Won't IP</FONT></P>
  <P><FONT size=3D2>&gt; addresses do? Is this to be used for telephone =
calls???=20
  My</FONT></P>
  <P><FONT size=3D2>&gt; recollection is that Fred Baker (then IETF =
chair) said=20
  that using</FONT></P>
  <P><FONT size=3D2>&gt; CCAMP for telephony was a no-no =
....)</FONT></P>
  <P><FONT size=3D2>&gt; </FONT></P>
  <P><FONT size=3D2>I will leave it to the "ITU" folk to answer the=20
  details.</FONT></P>
  <P><FONT size=3D2>But your main point seems to be that you have not =
seen=20
  enough</FONT></P>
  <P><FONT size=3D2>documentation. ITU-T did a Liason Statement to us, =
and I=20
  believe</FONT></P>
  <P><FONT size=3D2>even specifically to CCAMP WG (that you co-chair) =
and so can=20
  you</FONT></P>
  <P><FONT size=3D2>tell me if you read their documentation that they =
have=20
  made</FONT></P>
  <P><FONT size=3D2>(freely) available to us to check? And after =
reading that,=20
  do</FONT></P>
  <P><FONT size=3D2>your points still hold. If so, then maybe we =
(CCAMP) should=20
  answer</FONT></P>
  <P><FONT size=3D2>the Liason Statement and explain to them how and =
where they=20
  should</FONT></P>
  <P><FONT size=3D2>add more detail and ask specific questions based on =
what=20
  they</FONT></P>
  <P><FONT size=3D2>document in their "drafts" (or documents) to which =
they=20
  point.</FONT></P>
  <P><FONT size=3D2>&gt; Call Release can be "sent by any entity of the =
network".=20
  This surely</FONT></P>
  <P><FONT size=3D2>&gt; can't be correct.</FONT></P>
  <P><FONT size=3D2>&gt; </FONT></P>
  <P><FONT size=3D2>Will let ITU-folk answer that.</FONT></P>
  <P><FONT size=3D2>&gt; The Call Capability TLV is completely =
undocumented beyond=20
  the format</FONT></P>
  <P><FONT size=3D2>&gt; of the TLV.</FONT></P>
  <P><FONT size=3D2>&gt; </FONT></P>
  <P><FONT size=3D2>How about in the documents in OIF and ITU that they =
point=20
  to?</FONT></P>
  <P><FONT size=3D2>&gt; As someone else pointed out, crankback for =
CR-LDP has=20
  already been</FONT></P>
  <P><FONT size=3D2>&gt; defined. Furthermore, this document does not =
say what=20
  procedures</FONT></P>
  <P><FONT size=3D2>&gt; the sender and receiver must follow, and how =
crankback is=20
  to be</FONT></P>
  <P><FONT size=3D2>&gt; effected.</FONT></P>
  <P><FONT size=3D2>&gt;</FONT></P>
  <P><FONT size=3D2>What do you mean by "has already been defined" =
??</FONT></P>
  <P><FONT size=3D2>And are the procedures not documented in the =
documents they=20
  point to?</FONT></P>
  <P><FONT size=3D2></FONT></P>
  <P><FONT size=3D2>&gt; The "Additional Error Codes" have absolutely =
no detail=20
  about what</FONT></P>
  <P><FONT size=3D2>&gt; they mean, when they are to be sent, and what =
the=20
  receiver should</FONT></P>
  <P><FONT size=3D2>&gt; do with them. They also use a slew of =
unidentified=20
  acronyms.</FONT></P>
  <P><FONT size=3D2>&gt; </FONT></P>
  <P><FONT size=3D2>They do in the documents they point to.</FONT></P>
  <P><FONT size=3D2>Bert</FONT></P>
  <P><FONT size=3D2>&gt; Kireeti.</FONT></P>
  <P><FONT size=3D2>&gt; =
</FONT></P></FONT></FONT></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2C2FE.E145F418--





From owner-ietf@ietf.org  Thu Jan 23 14:09:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16908;
	Thu, 23 Jan 2003 14:09:15 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bml7-0005ke-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 14:11:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bkkT-0004oJ-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 12:02:41 -0500
Received: from zcars04f.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13168;
	Thu, 23 Jan 2003 11:56:09 -0500 (EST)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h0NGxJH10815;
	Thu, 23 Jan 2003 11:59:19 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <DPZ2N5B6>; Thu, 23 Jan 2003 11:59:19 -0500
Message-ID: <0D7FC1D8D861D511AEA70002A52CE5E604343B6E@zcard0ke.ca.nortel.com>
From: "Stephen Shew" <sdshew@nortelnetworks.com>
To: "'Loa Andersson'" <loa@pi.se>, "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)" <sob@harvard.edu>,
        "'iesg@ietf.org'" <iesg@ietf.org>, "'ietf@ietf.org'" <ietf@ietf.org>,
        "'kireeti@juniper.net'" <kireeti@juniper.net>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Malcolm Betts" <betts01@nortelnetworks.com>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Trowbridge, Stephen J (Steve)" <sjtrowbr@ihmail.ih.lucent.com>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 11:59:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2C300.C24F88A6"
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_01C2C300.C24F88A6
Content-Type: text/plain

On the separation of issues, I think that's helpful.  On issue 1, I think
that there is definitely precedent on use of IETF protocols by the ITU-T (I
think it was in the OAM area and SG13).  SG15's use of GMPLS protocols has
to do with extensions that enable them to fit into the ASON architecture.

I would like to point out that for G.7713.1 (PNNI based ASON signalling),
the ATM Forum has been very helpful in enabling the work and liaising back
to SG15.

-----Original Message-----
From: Loa Andersson [mailto:loa@pi.se] 
Sent: Thursday, January 23, 2003 06:59
To: Lin, Zhi-Wei (Zhi)
Cc: Wijnen, Bert (Bert); Scott Bradner (E-mail); 'iesg@ietf.org';
'ietf@ietf.org'; 'kireeti@juniper.net'; Lam, Hing-Kam (Kam); Betts, Malcolm
[SKY:1ID0:EXCH]; Shew, Stephen [SKY:QW33:EXCH]; Lyndon Ong (E-mail); Alan
McGuire (E-mail); Trowbridge, Stephen J (Steve)
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational


All,

taking a step back - I think we are discussing several issues in a mix that
makes it very hard to sort this out.

1. What other organizations may do to IETF (in this context (G)MPLS)
    protocols

    This won't be sorted out in this thread - and the only opinion so far
    is that it is a bad idea to let anyone else change or extend IETF
    protocols.

    This will require at statement from involved wg chairs and ADs and an
    approval from the IESG. I will push for such a statement.

2. Have the IETF protocols been changed

    This is is a matter of how "changed" is defined. Clearly the OIF
    UNI signaling spec extends the LDP protocol, message and new TLV.
    This is referenced by a normative reference in the three drafts
    discussed here

       draft-lin-ccamp-gmpls-ason-rsvpte-04.txt
       draft-aboulmagd-ccamp-crldp-ason-ext-02.txt
       draft-bala-uni-ldp-rsvp-extensions-04.txt

    I understand that the IESG wants to treat those as a packet, and that
    the last call on the CR-LDP Extensions for ASON to Informational in
    fact is a last call on all three of them. Further this could be
    construed to be seen as an "last call" on normative references -
    after all normative references are considered to necessary for
    implementing a spec.

    Also, the ITU work extends the IETF protocols, new objects, new TLVs
    and new error codes, that is why the drafts were written - to make it
    possible for IANA to approve the needed code points.

    In our normal use of terms change includes extends, but we should
    probably make that clear.

    The consequence of approving the drafts will be that the extensions
    by OIF and ITU will be approved by the IETF. I'm not sure that this
    has been in the open.

    However, not having a change process that relates to these protocols
    I'm not sure if the IESG can do anything else than approving that the
    IANA allocate the code points.

3. The quality of the drafts

    In my opinion (if I were to review them as a wg chair, but I'm not
    sure that those criteria apply to informational documents) we have a
    problem here.

    The draft-lin-ccamp-gmpls-ason-rsvpte-04.txt and the
    draft-bala-uni-ldp-rsvp-extensions-04.txt is an a shape such that I
    would (reluctantly) request publishing.

    But the draft-aboulmagd-ccamp-crldp-ason-ext-02.txt is not, there is
    a long series of points that needs to be updated. References, TLV
    description, un-expanded acronyms, etc. Would have returned this to
    the author for further work. Aside from that I have a couple of
    technical issues.

    Now, if the IESG considers them to be a package, this would effect
    all of them. I guess that it would be possible to weed the draft
    after it has been approved, but it deviates from normal practice.

My belief is that we should try to separate these issues from each other.

/Loa



-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se



------_=_NextPart_001_01C2C300.C24F88A6
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: Last Call: CR-LDP Extensions for ASON to =
Informational</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>On the separation of issues, I think that's =
helpful.&nbsp; On issue 1, I think that there is definitely precedent =
on use of IETF protocols by the ITU-T (I think it was in the OAM area =
and SG13).&nbsp; SG15's use of GMPLS protocols has to do with =
extensions that enable them to fit into the ASON =
architecture.</FONT></P>

<P><FONT SIZE=3D2>I would like to point out that for G.7713.1 (PNNI =
based ASON signalling), the ATM Forum has been very helpful in enabling =
the work and liaising back to SG15.</FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Loa Andersson [<A =
HREF=3D"mailto:loa@pi.se">mailto:loa@pi.se</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, January 23, 2003 06:59</FONT>
<BR><FONT SIZE=3D2>To: Lin, Zhi-Wei (Zhi)</FONT>
<BR><FONT SIZE=3D2>Cc: Wijnen, Bert (Bert); Scott Bradner (E-mail); =
'iesg@ietf.org'; 'ietf@ietf.org'; 'kireeti@juniper.net'; Lam, Hing-Kam =
(Kam); Betts, Malcolm [SKY:1ID0:EXCH]; Shew, Stephen [SKY:QW33:EXCH]; =
Lyndon Ong (E-mail); Alan McGuire (E-mail); Trowbridge, Stephen J =
(Steve)</FONT></P>

<P><FONT SIZE=3D2>Subject: Re: Last Call: CR-LDP Extensions for ASON to =
Informational</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>All,</FONT>
</P>

<P><FONT SIZE=3D2>taking a step back - I think we are discussing =
several issues in a mix that makes it very hard to sort this =
out.</FONT>
</P>

<P><FONT SIZE=3D2>1. What other organizations may do to IETF (in this =
context (G)MPLS)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; protocols</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; This won't be sorted out in this =
thread - and the only opinion so far</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; is that it is a bad idea to let =
anyone else change or extend IETF</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; protocols.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; This will require at statement =
from involved wg chairs and ADs and an</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; approval from the IESG. I will =
push for such a statement.</FONT>
</P>

<P><FONT SIZE=3D2>2. Have the IETF protocols been changed</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; This is is a matter of how =
&quot;changed&quot; is defined. Clearly the OIF</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; UNI signaling spec extends the =
LDP protocol, message and new TLV.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; This is referenced by a normative =
reference in the three drafts</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; discussed here</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft-lin-ccamp-gmpls-ason-rsvpte-04.txt</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft-aboulmagd-ccamp-crldp-ason-ext-02.txt</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft-bala-uni-ldp-rsvp-extensions-04.txt</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; I understand that the IESG wants =
to treat those as a packet, and that</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; the last call on the CR-LDP =
Extensions for ASON to Informational in</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; fact is a last call on all three =
of them. Further this could be</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; construed to be seen as an =
&quot;last call&quot; on normative references -</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; after all normative references =
are considered to necessary for</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; implementing a spec.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; Also, the ITU work extends the =
IETF protocols, new objects, new TLVs</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; and new error codes, that is why =
the drafts were written - to make it</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; possible for IANA to approve the =
needed code points.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; In our normal use of terms change =
includes extends, but we should</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; probably make that clear.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; The consequence of approving the =
drafts will be that the extensions</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; by OIF and ITU will be approved =
by the IETF. I'm not sure that this</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; has been in the open.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; However, not having a change =
process that relates to these protocols</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; I'm not sure if the IESG can do =
anything else than approving that the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; IANA allocate the code =
points.</FONT>
</P>

<P><FONT SIZE=3D2>3. The quality of the drafts</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; In my opinion (if I were to review =
them as a wg chair, but I'm not</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; sure that those criteria apply to =
informational documents) we have a</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; problem here.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; The =
draft-lin-ccamp-gmpls-ason-rsvpte-04.txt and the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; =
draft-bala-uni-ldp-rsvp-extensions-04.txt is an a shape such that =
I</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; would (reluctantly) request =
publishing.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; But the =
draft-aboulmagd-ccamp-crldp-ason-ext-02.txt is not, there is</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; a long series of points that =
needs to be updated. References, TLV</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; description, un-expanded =
acronyms, etc. Would have returned this to</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; the author for further work. =
Aside from that I have a couple of</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; technical issues.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; Now, if the IESG considers them to =
be a package, this would effect</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; all of them. I guess that it =
would be possible to weed the draft</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; after it has been approved, but =
it deviates from normal practice.</FONT>
</P>

<P><FONT SIZE=3D2>My belief is that we should try to separate these =
issues from each other.</FONT>
</P>

<P><FONT SIZE=3D2>/Loa</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Loa Andersson</FONT>
</P>

<P><FONT =
SIZE=3D2>Mobile&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+46 739 81 21 64</FONT>
<BR><FONT =
SIZE=3D2>Email&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; loa@pi.se</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C2C300.C24F88A6--





From owner-ietf@ietf.org  Thu Jan 23 14:10:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16959;
	Thu, 23 Jan 2003 14:10:22 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bmlu-0005nz-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 14:12:18 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bl3Y-0005OD-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 12:22:24 -0500
Received: from host19.ipowerweb.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13747;
	Thu, 23 Jan 2003 12:15:52 -0500 (EST)
Received: from h00a0ccd1a9ec.ne.client2.attbi.com ([24.128.219.249] helo=GraIyMage.com)
	by host19.ipowerweb.com with asmtp (Exim 3.36 #1)
	id 18bkzl-0004rN-00; Thu, 23 Jan 2003 09:18:29 -0800
Message-ID: <3E3023D1.4CED192B@GraIyMage.com>
Date: Thu, 23 Jan 2003 12:18:09 -0500
From: Eric Gray <ewgray@graiymage.com>
Reply-To: GraIyMag@graiymage.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD NSCPCD47  (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
CC: Kireeti Kompella <kireeti@juniper.net>, Bob Braden <braden@ISI.EDU>,
        iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
References: <7D5D48D2CAA3D84C813F5B154F43B155BAE4B4@nl0006exch001u.nl.lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host19.ipowerweb.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - graiymage.com
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bert,

    A common example of useful "derivative" work is to modify the
document
such that references include URLs and include it in web-sites. There are
any
number of private, or semi-private - and maybe one or two public - web
sites
that have provided hyper-linked versions of Internet Drafts in just this
way.

    Because this document explicitly excludes derivative works, this
precludes
doing this for this (eventual) RFC - or, more likely, sets someone up for
legal
trouble if they have already done so.

    I'm not sure why an RFC might be granted perpetual unrestricted
copyright
but not allowed in derivative works. Is the intent to include copies as
derivative
works?

    It seems a good idea to provide justification - or at least and
explanation -
if an intended RFC is no in complete compliance with RFC 2026.

"Wijnen, Bert (Bert)" wrote:

> I noticed today that I gave an incorrect answer to one of
> Kireeti's points. He asked and I answered:
>
> > > I would like to know what the intent is in not granting
> > > "the right to produce derivative works",
> > Did Steve Trowbridge not answer the first question?
> >
> This is in the Draft-aboulmagd-crldp-ason-ext-02.txt document.
> It states:
>
>    This document is an Internet-Draft and is in full conformance with
>    all provisions of Section 10 of RFC2026 except that the right to
>    produce derivative works is not granted.
>
> But this is OK since this is documenting ITU material.
>
> Bert and Scott







From owner-ietf@ietf.org  Thu Jan 23 14:15:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17146;
	Thu, 23 Jan 2003 14:15:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bmlv-0005oX-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 14:12:19 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bmIV-00048j-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 13:41:55 -0500
Received: from hoemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16020;
	Thu, 23 Jan 2003 13:35:22 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0NIclm17784;
	Thu, 23 Jan 2003 13:38:47 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ2686Z8>; Thu, 23 Jan 2003 19:38:41 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE5D8@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: GraIyMag@graiymage.com, "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Cc: Kireeti Kompella <kireeti@juniper.net>, Bob Braden <braden@ISI.EDU>,
        iesg@ietf.org, ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 19:38:31 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

We had already found one incorrect reference, and we
checked with the author, and he agrees it is incorrect
and that we should fix it. (UNI 1.0 instead of 1.1)

The document references ITU documents G.7713 and G.8080
Thos as clear references (I think) to documents as they
are known in ITU. So I see no issue.

It probably should also reference G7713.3, which I think is
still missing. I am checking with the author as we speak.
It is quite possible that in ITU process it is OK to refer
to G7713 and that that automatically includes the G7713.x
documents. Can ITU folk explain.

In any event, when a document is being prepared by RFC-Editor
for final publication, they always check the references and
check with the authors if anything seems incorrect or
incomplete. 

Thanks,
Bert 

> -----Original Message-----
> From: Eric Gray [mailto:ewgray@graiymage.com]
> Sent: donderdag 23 januari 2003 18:18
> To: Wijnen, Bert (Bert)
> Cc: Kireeti Kompella; Bob Braden; iesg@ietf.org; ietf@ietf.org
> Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
> 
> 
> Bert,
> 
>     A common example of useful "derivative" work is to modify the
> document such that references include URLs and include it in 
> web-sites. There are any number of private, or semi-private 
> - and maybe one or two public - web sites that have provided
> hyper-linked versions of Internet Drafts in just this way.
> 
>     Because this document explicitly excludes derivative works, this
> precludes
> doing this for this (eventual) RFC - or, more likely, sets 
> someone up for
> legal
> trouble if they have already done so.
> 
>     I'm not sure why an RFC might be granted perpetual unrestricted
> copyright but not allowed in derivative works. Is the intent to
> include copies as derivative works?
> 
>     It seems a good idea to provide justification - or at least and
> explanation - if an intended RFC is no in complete compliance with
> RFC 2026.
> 
> "Wijnen, Bert (Bert)" wrote:
> 
> > I noticed today that I gave an incorrect answer to one of
> > Kireeti's points. He asked and I answered:
> >
> > > > I would like to know what the intent is in not granting
> > > > "the right to produce derivative works",
> > > Did Steve Trowbridge not answer the first question?
> > >
> > This is in the Draft-aboulmagd-crldp-ason-ext-02.txt document.
> > It states:
> >
> >    This document is an Internet-Draft and is in full 
> conformance with
> >    all provisions of Section 10 of RFC2026 except that the right to
> >    produce derivative works is not granted.
> >
> > But this is OK since this is documenting ITU material.
> >
> > Bert and Scott
> 
> 





From owner-ietf@ietf.org  Thu Jan 23 14:15:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17147;
	Thu, 23 Jan 2003 14:15:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bmlu-0005o5-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 14:12:18 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18blIK-0006Cw-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 12:37:40 -0500
Received: from host19.ipowerweb.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14104;
	Thu, 23 Jan 2003 12:31:07 -0500 (EST)
Received: from h00a0ccd1a9ec.ne.client2.attbi.com ([24.128.219.249] helo=GraIyMage.com)
	by host19.ipowerweb.com with asmtp (Exim 3.36 #1)
	id 18blEb-0000UJ-00; Thu, 23 Jan 2003 09:33:49 -0800
Message-ID: <3E302767.94F2FDDD@GraIyMage.com>
Date: Thu, 23 Jan 2003 12:33:27 -0500
From: Eric Gray <ewgray@graiymage.com>
Reply-To: GraIyMag@graiymage.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD NSCPCD47  (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Stephen Trowbridge <sjtrowbridge@lucent.com>
CC: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>, cdel@firsthand.net, iesg@ietf.org,
        ietf@ietf.org, "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)" <sob@harvard.edu>, kireeti@juniper.net,
        "Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Malcolm Betts (E-mail)" <betts01@nortelnetworks.com>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Dimitrios Pendarakis (E-mail)" <DPendarakis@tellium.com>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
References: <D3F8FD817CC7DA408AEB2CAC631C042A98E5FD@nj7460exch012u.ho.lucent.com> <3E301869.A3D7E7C4@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host19.ipowerweb.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - graiymage.com
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Stephen,

    As a clarification question, what typically is the role assumed by the
class of member that includes scientific and industrial organizations?

Stephen Trowbridge wrote:

> Christian,
> Zhi has captured the essence.
> ITU-T has several classes of membership:
> - The highest, since ITU is an organization under the umbrella of the United
>   Nations, are "member states". This consists of the 190 or so countries that
>   are members of the United Nations. In study groups that deal with regulatory
>   and tariff issues, the governments are often sources of some of the material
>   to be considered. In a more technical study group (like Study Group 15),
>   governments tend to fill the role of determining if there is consensus of
>   industry within the country, and forwarding that as a national position.
> - The next class of membership is Recognized Operating Agencies. These are
>   network operators.
> - The next class (equivalent in rights to the operators) is called Scientific
>   and Industrial Organizations. While any such organization can join, these
>   are generally equipment or component vendors.
> - The final class are called "Associates", who pay a lower level of dues to
>   participate in a single Study Group.
> Each country can determine their own national process through which national
> positions are determined. In the US, it is customary to take proposed national
> positions first to a related US standards organization (ANSI committee T1X1
> for most of ITU-T Study Group 15) to develop the industry consensus, and then
> to a US State Department committee (US Study Group B is the one which feeds
> Study Group 15) which generally (not always) follows the recommendation of the
> US standards organization in whether something should be forwarded as a national
> position under the "member state" membership. Since in most cases, the national
> standards organizations have looked at these documents first, the meetings of
> the US State Department committees tend to be relatively short (1/2 day or so,
> often by conference call).
>
> As far as I understand the UK process, they have a national committee per
> ITU-T Study Group which can approve national positions when there is industry
> consensus. Since the UK does not have similar national standards organizations,
> they must also look into the technical details of the contributions. This
> results in a longer meeting (I think a couple of days, from what I have heard)
> to develop any UK national positions for ITU-T Study Group 15.
>
> Getting a national position in countries with significant industrial participation
> is no small feat, so contributions such as this are generally taken very seriously.
> Hope this helps.
> Steve
>
> "Lin, Zhi-Wei (Zhi)" wrote:
> >
> > Hi Christian,
> >
> > This is one of the processes within the ITU-T standards body. The documents that is submitted into these documents can have multiple levels of "status". I'm not sure what the process is within the UK, but I have some idea of the process within the USA. Maybe Stephen Trowbridge or others more familiar with the procedures can comment (I typically try to stay away from these and stick my head into the technical stuff).
> >
> > The lowest status is that a document is sent by a company. In this case only that company is known to support this. A document may also have multiple company names as contributors, in which case these companies are active proponents.
> > The next level status is a country document. A country document (e.g., USA or UK) means that the document has undergone a national standards process, and that ALL the companies represented within that country will support the position stated by the document.
> >
> > This is of course much different from the IETF process, where all documents are by individual basis (theoretically it should not even have company affiliation but only represents the views of the individuals in the author list, but of course practically most people who attends and submits documents are actually representing a company view)...please don't flame me, just giving an observation based on my limited exposure to the IETF process...
> >
> > Hope this helps
> >
> > Zhi
> >
> > -----Original Message-----
> > From: Christian de Larrinaga [mailto:cdel@firsthand.net]
> > Sent: Thursday, January 23, 2003 10:17 AM
> > To: Lin, Zhi-Wei (Zhi); iesg@ietf.org; ietf@ietf.org; Wijnen, Bert
> > (Bert); Scott Bradner (E-mail); kireeti@juniper.net
> > Cc: Stephen Shew (E-mail); Lyndon Ong (E-mail); Malcolm Betts (E-mail);
> > Lam, Hing-Kam (Kam); Alan McGuire (E-mail); sjtrowbridge@lucent.com;
> > Dimitrios Pendarakis (E-mail)
> > Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
> >
> > Lin Zhi-Wei
> >
> > You mention a UK national position paper. Can you give me the references and
> > what made this "national"?
> >
> > many thanks,
> >
> > Christian de Larrinaga
> >
> > > A clear U.K. national position paper was
> > >contributed to the meeting currently underway
> > >(delayed contribution 483), supporting that all
> > >three of the ASON signaling Recommendations
> > >should be put for consent at this meeting.
> > >Hope this helps...
> > >Zhi







From owner-ietf@ietf.org  Thu Jan 23 14:42:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18188;
	Thu, 23 Jan 2003 14:42:09 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bnGn-00031s-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 14:44:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bnEM-0002vy-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 14:41:42 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18036;
	Thu, 23 Jan 2003 14:35:07 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.8.Alpha0/8.12.8.Alpha0) with ESMTP id h0NJcQ75012548;
	Thu, 23 Jan 2003 14:38:26 -0500
Message-Id: <200301231938.h0NJcQ75012548@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: GraIyMag@graiymage.com
Cc: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational 
In-Reply-To: Your message of "Thu, 23 Jan 2003 12:18:09 EST."
             <3E3023D1.4CED192B@GraIyMage.com> 
References: <7D5D48D2CAA3D84C813F5B154F43B155BAE4B4@nl0006exch001u.nl.lucent.com>
            <3E3023D1.4CED192B@GraIyMage.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-327977209P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 23 Jan 2003 14:38:25 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Thu, 23 Jan 2003 12:18:09 EST, Eric Gray said:

>     I'm not sure why an RFC might be granted perpetual unrestricted
> copyright
> but not allowed in derivative works. Is the intent to include copies as
> derivative
> works?

I think the goal is to prevent the creation of non-canonical versions that
possibly have errata in them.  If I create a derivative work by adding hyperlinks
and the like, and accidentally change a 3 to a 4 or something like that, all
sorts of mischief will result....
-- 
				Valdis Kletnieks
				Computer Systems Senior Engineer
				Virginia Tech


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

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

iD8DBQE+MESxcC3lWbTT17ARAkMdAJ0Uxix7AJSurYiZbKonY6c66lHXvgCfRL3w
hUnwMYXRqtWmBasiQ5++1bA=
=i9Vf
-----END PGP SIGNATURE-----

--==_Exmh_-327977209P--



From owner-ietf@ietf.org  Thu Jan 23 17:07:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21627;
	Thu, 23 Jan 2003 17:07:40 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bpVx-0004DW-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 17:08:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bpV6-0004BS-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 17:07:08 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21462;
	Thu, 23 Jan 2003 17:00:31 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.8.Alpha0/8.12.8.Alpha0) with ESMTP id h0NM3p75014231;
	Thu, 23 Jan 2003 17:03:51 -0500
Message-Id: <200301232203.h0NM3p75014231@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: ewgray@graiymage.com
Cc: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational 
In-Reply-To: Your message of "Thu, 23 Jan 2003 15:08:32 EST."
             <3E304BC0.8C6E051A@GraIyMage.com> 
References: <7D5D48D2CAA3D84C813F5B154F43B155BAE4B4@nl0006exch001u.nl.lucent.com> <3E3023D1.4CED192B@GraIyMage.com> <200301231938.h0NJcQ75012548@turing-police.cc.vt.edu>
            <3E304BC0.8C6E051A@GraIyMage.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1522866796P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 23 Jan 2003 17:03:50 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Thu, 23 Jan 2003 15:08:32 EST, Eric Gray said:
>     I believe this concern is dealt with by the fact that there is an IETF
> official site and various similarly official reflectors.  If an error exist a
t
> an official site, the IETF community has a responsibility to point it out.

You know that, I know that, most of the IETF knows that.  However, unless
I'm severely confused (which is always possible), the prohibition against
derivative works came from the ITU side of the fence, which has often been
accused of Just Not Getting It (see its long-standing policy of charging for
copies of standards, etc).  The ITU is driven a lot more by politics and
lawyers than the IETF is, so the IETF-style "if we find a broken copy we'll
fix it and smack the offender upside the head" doesn't go over very well...

Remember, we're talking about the same cultural difference that lead to
MIME and X.400.....
-- 
				Valdis Kletnieks
				Computer Systems Senior Engineer
				Virginia Tech


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

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

iD8DBQE+MGbGcC3lWbTT17ARAmoLAJ935WM+v6/bW9lSp8VoezrFVtrYuwCg+zXV
kYJAHxrs0SSE2T9ugPa/pck=
=Susx
-----END PGP SIGNATURE-----

--==_Exmh_-1522866796P--



From owner-ietf@ietf.org  Thu Jan 23 17:51:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22931;
	Thu, 23 Jan 2003 17:51:40 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bqDV-0006oR-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 17:53:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bqDR-0006mK-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 17:52:57 -0500
Received: from merlot.juniper.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22733;
	Thu, 23 Jan 2003 17:46:21 -0500 (EST)
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 h0NMnnS88093;
	Thu, 23 Jan 2003 14:49:49 -0800 (PST)
	(envelope-from kireeti@juniper.net)
Received: from localhost (kireeti@localhost)
	by kummer.juniper.net (8.11.6/8.9.3) with ESMTP id h0NMnmS85518;
	Thu, 23 Jan 2003 14:49:49 -0800 (PST)
	(envelope-from kireeti@juniper.net)
X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs
Date: Thu, 23 Jan 2003 14:49:48 -0800 (PST)
From: Kireeti Kompella <kireeti@juniper.net>
To: <ietf@ietf.org>
cc: Bob Braden <braden@ISI.EDU>, <iesg@ietf.org>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155BAE5D8@nl0006exch001u.nl.lucent.com>
Message-ID: <20030123143610.L85460-100000@kummer.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

I just saw the message that this document has been approved.  I
have a question about the process.

Definition in RFC 2434, "IETF Consensus - New values are assigned through
the IETF consensus process".  The CR-LDP code points are clearly marked
as "IETF Consensus", not IESG Approval.

I have heard repeatedly, from at least 5 different ADs that three people
for and one against does *not* constitute a consensus -- in fact, this
was repeated in the TE WG list a couple of days ago.

There were several people that raised various objections, from nits
to technical issues.  Many remain unanswered.

Am I to understand that the IESG inferred consensus from the discussions
that have taken place (and are still under way)?

Kireeti.




From owner-ietf@ietf.org  Thu Jan 23 17:55:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23129;
	Thu, 23 Jan 2003 17:55:09 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bqIL-00070R-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 17:58:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bqHd-0006yO-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 17:57:17 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22898;
	Thu, 23 Jan 2003 17:50:41 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h0NMs8b17246;
	Thu, 23 Jan 2003 14:54:08 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id WAA02326;
	Thu, 23 Jan 2003 22:54:08 GMT
Date: Thu, 23 Jan 2003 22:54:08 GMT
Message-Id: <200301232254.WAA02326@gra.isi.edu>
To: ietf@ietf.org, kireeti@juniper.net
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Cc: braden@ISI.EDU, iesg@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


  *> 
  *> Hi,
  *> 
  *> I just saw the message that this document has been approved.  I
  *> have a question about the process.
  *> 
  *> Definition in RFC 2434, "IETF Consensus - New values are assigned through
  *> the IETF consensus process".  The CR-LDP code points are clearly marked
  *> as "IETF Consensus", not IESG Approval.
  *> 
  *> I have heard repeatedly, from at least 5 different ADs that three people
  *> for and one against does *not* constitute a consensus -- in fact, this
  *> was repeated in the TE WG list a couple of days ago.
  *> 
  *> There were several people that raised various objections, from nits
  *> to technical issues.  Many remain unanswered.
  *> 
  *> Am I to understand that the IESG inferred consensus from the discussions
  *> that have taken place (and are still under way)?
  *> 
  *> Kireeti.
  *> 

Since I was CC'd, I will note that in my role as IANA designated expert
for RSVP, I interpret "IETF consensus" as meaning that at least a Last
Call was conducted.  To use any other interpretation seems to me to
be dishonest.  I guess I am agreeing with Kireeti.

Bob Braden



From owner-ietf@ietf.org  Thu Jan 23 17:56:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23203;
	Thu, 23 Jan 2003 17:56:21 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bqKJ-0007QV-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 18:00:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bqIY-00070T-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 17:58:14 -0500
Received: from ihemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22925;
	Thu, 23 Jan 2003 17:51:37 -0500 (EST)
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0NMp6J02384;
	Thu, 23 Jan 2003 17:51:06 -0500 (EST)
Received: from lucent.com ([135.248.116.65]) by ihmail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id QAA22201; Thu, 23 Jan 2003 16:50:58 -0600 (CST)
Message-ID: <3E30717C.667B70E4@lucent.com>
Date: Thu, 23 Jan 2003 15:49:32 -0700
From: Stephen Trowbridge <sjtrowbridge@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD EMS-1.5  (Windows NT 5.0; U)
X-Accept-Language: en,zh
MIME-Version: 1.0
To: GraIyMag@graiymage.com
CC: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>, cdel@firsthand.net, iesg@ietf.org,
        ietf@ietf.org, "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Scott Bradner (E-mail)" <sob@harvard.edu>, kireeti@juniper.net,
        "Stephen Shew (E-mail)" <sdshew@nortelnetworks.com>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>,
        "Malcolm Betts (E-mail)" <betts01@nortelnetworks.com>,
        "Lam, Hing-Kam (Kam)" <hklam@lucent.com>,
        "Alan McGuire (E-mail)" <alan.mcguire@bt.com>,
        "Dimitrios Pendarakis (E-mail)" <DPendarakis@tellium.com>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
References: <D3F8FD817CC7DA408AEB2CAC631C042A98E5FD@nj7460exch012u.ho.lucent.com> <3E301869.A3D7E7C4@lucent.com> <3E302767.94F2FDDD@GraIyMage.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

Eric,
I'll restrict my answer to the role in a purely technical study group (like
Study Group 15). The answers vary when getting into work that deals with
tariff & regulatory matters.

In these study groups, virtually all of the input contributions (which are
written and submitted in advance of the meeting) are submitted by the two
classes of members:
- recognized operating agencies
- scientific and industrial organizations
Those who wrote the contributions are generally the ones who also attend
the meetings to present the contributions and negotiate for agreements for
text based on those contributions to be included in the draft Recommendations
under development.

In a technical study group, generally even contributions that appear to
come from governments (because they are submitted by a member state) were
actually authored by delegates from either recognized operating agencies
or scientific and industrial organizations who are based in countries that
have a national process whereby national positions can be forumulated and
agreed between the industry members within that country. The interest of
governments in purely technical study groups tends to be that:
- what gets put forward as a national position is reasonable
- that even individual company contributions from within a country do
  not contradict previously agreed national positions.
- not enforceable, but I think many governments prefer that their
  country delegates do most of the squabbling amongst themselves in
  a national forum instead of at ITU-T.

In terms of approvals, everyone gets a voice at approval meetings. Nearly
everything that is approved is unopposed (difficult to believe with the
diversity of interest represented at these meetings, but we actually
accomplish this almost all of the time). If push comes to shove (this
almost never happens) and there is a need to approve something in
spite of objections, only the voices of the administrations (governments)
count. As most administrations will abstain if there is disagreement
among the operators/scientific&industrial organizations within their
countries, an individual company cannot stop approval. Since everyone
know that going in, they are looking for something that can be agreed
unopposed, and that a single company at the end of the day cannot
stop something, everyone goes in with a view toward cooperation and
compromise, and agreements are reached.

Hope this helps.
Steve

Eric Gray wrote:
> 
> Stephen,
> 
>     As a clarification question, what typically is the role assumed by the
> class of member that includes scientific and industrial organizations?
> 
> Stephen Trowbridge wrote:
> 
> > Christian,
> > Zhi has captured the essence.
> > ITU-T has several classes of membership:
> > - The highest, since ITU is an organization under the umbrella of the United
> >   Nations, are "member states". This consists of the 190 or so countries that
> >   are members of the United Nations. In study groups that deal with regulatory
> >   and tariff issues, the governments are often sources of some of the material
> >   to be considered. In a more technical study group (like Study Group 15),
> >   governments tend to fill the role of determining if there is consensus of
> >   industry within the country, and forwarding that as a national position.
> > - The next class of membership is Recognized Operating Agencies. These are
> >   network operators.
> > - The next class (equivalent in rights to the operators) is called Scientific
> >   and Industrial Organizations. While any such organization can join, these
> >   are generally equipment or component vendors.
> > - The final class are called "Associates", who pay a lower level of dues to
> >   participate in a single Study Group.
> > Each country can determine their own national process through which national
> > positions are determined. In the US, it is customary to take proposed national
> > positions first to a related US standards organization (ANSI committee T1X1
> > for most of ITU-T Study Group 15) to develop the industry consensus, and then
> > to a US State Department committee (US Study Group B is the one which feeds
> > Study Group 15) which generally (not always) follows the recommendation of the
> > US standards organization in whether something should be forwarded as a national
> > position under the "member state" membership. Since in most cases, the national
> > standards organizations have looked at these documents first, the meetings of
> > the US State Department committees tend to be relatively short (1/2 day or so,
> > often by conference call).
> >
> > As far as I understand the UK process, they have a national committee per
> > ITU-T Study Group which can approve national positions when there is industry
> > consensus. Since the UK does not have similar national standards organizations,
> > they must also look into the technical details of the contributions. This
> > results in a longer meeting (I think a couple of days, from what I have heard)
> > to develop any UK national positions for ITU-T Study Group 15.
> >
> > Getting a national position in countries with significant industrial participation
> > is no small feat, so contributions such as this are generally taken very seriously.
> > Hope this helps.
> > Steve
> >
> > "Lin, Zhi-Wei (Zhi)" wrote:
> > >
> > > Hi Christian,
> > >
> > > This is one of the processes within the ITU-T standards body. The documents that is submitted into these documents can have multiple levels of "status". I'm not sure what the process is within the UK, but I have some idea of the process within the USA. Maybe Stephen Trowbridge or others more familiar with the procedures can comment (I typically try to stay away from these and stick my head into the technical stuff).
> > >
> > > The lowest status is that a document is sent by a company. In this case only that company is known to support this. A document may also have multiple company names as contributors, in which case these companies are active proponents.
> > > The next level status is a country document. A country document (e.g., USA or UK) means that the document has undergone a national standards process, and that ALL the companies represented within that country will support the position stated by the document.
> > >
> > > This is of course much different from the IETF process, where all documents are by individual basis (theoretically it should not even have company affiliation but only represents the views of the individuals in the author list, but of course practically most people who attends and submits documents are actually representing a company view)...please don't flame me, just giving an observation based on my limited exposure to the IETF process...
> > >
> > > Hope this helps
> > >
> > > Zhi
> > >
> > > -----Original Message-----
> > > From: Christian de Larrinaga [mailto:cdel@firsthand.net]
> > > Sent: Thursday, January 23, 2003 10:17 AM
> > > To: Lin, Zhi-Wei (Zhi); iesg@ietf.org; ietf@ietf.org; Wijnen, Bert
> > > (Bert); Scott Bradner (E-mail); kireeti@juniper.net
> > > Cc: Stephen Shew (E-mail); Lyndon Ong (E-mail); Malcolm Betts (E-mail);
> > > Lam, Hing-Kam (Kam); Alan McGuire (E-mail); sjtrowbridge@lucent.com;
> > > Dimitrios Pendarakis (E-mail)
> > > Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
> > >
> > > Lin Zhi-Wei
> > >
> > > You mention a UK national position paper. Can you give me the references and
> > > what made this "national"?
> > >
> > > many thanks,
> > >
> > > Christian de Larrinaga
> > >
> > > > A clear U.K. national position paper was
> > > >contributed to the meeting currently underway
> > > >(delayed contribution 483), supporting that all
> > > >three of the ASON signaling Recommendations
> > > >should be put for consent at this meeting.
> > > >Hope this helps...
> > > >Zhi



From owner-ietf@ietf.org  Thu Jan 23 18:22:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24024;
	Thu, 23 Jan 2003 18:22:56 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bqhZ-0000cp-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 18:24:05 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bqhI-0000Yr-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 18:23:48 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23896
	for <ietf@ietf.org>; Thu, 23 Jan 2003 18:17:13 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h0NNKcb04745;
	Thu, 23 Jan 2003 15:20:38 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id XAA02376;
	Thu, 23 Jan 2003 23:20:38 GMT
Date: Thu, 23 Jan 2003 23:20:38 GMT
Message-Id: <200301232320.XAA02376@gra.isi.edu>
To: ietf@ietf.org
Subject: Re: Document Action: LDP and RSVP Extensions for Optical UNI 
	   Signaling to Informational
Cc: rfc-editor@ISI.EDU, iab@iab.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


  *> From owner-ietf-announce@ietf.org  Thu Jan 23 13:42:03 2003
  *> To: IETF-Announce: ;
  *> Cc: RFC Editor <rfc-editor@ISI.EDU>, Internet Architecture Board <iab@iab.org>
  *> From: The IESG <iesg-secretary@ietf.org>
  *> Subject: Document Action: LDP and RSVP Extensions for Optical UNI 
  *> 	   Signaling to Informational
  *> Date: Thu, 23 Jan 2003 16:23:42 -0500
  *> X-AntiVirus: scanned by AMaViS 0.2.1
  *> 
  *> 
  *> The IESG has approved the Internet-Draft 'LDP and RSVP Extensions for 
  *> Optical UNI Signaling' <draft-bala-uni-ldp-rsvp-extensions-04.txt> as 
  *> an Informational RFC.  This has been reviewed in the IETF but is not the 
  *> product of an IETF Working Group.
  *> 
  *> The IESG contact person is Scott Bradner.
  *> 

Should that title be: 'LDP and RSVP-TE Extensions for Optical UNI Signaling'?
RSVP-TE is not RSVP.

Bob Braden



From owner-ietf@ietf.org  Thu Jan 23 19:53:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26164;
	Thu, 23 Jan 2003 19:53:39 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bs5h-0004Ic-00
	for ietf-list@ran.ietf.org; Thu, 23 Jan 2003 19:53:05 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bs5F-0004GK-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 19:52:37 -0500
Received: from kcmso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26003;
	Thu, 23 Jan 2003 19:46:00 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0O0hghi027671;
	Thu, 23 Jan 2003 18:49:28 -0600 (CST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E01884050; Thu, 23 Jan 2003 19:49:26 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Thu, 23 Jan 2003 19:49:24 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704A17692@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: IANA Considerations for RSVP
Thread-Index: AcLDBCn2W/PWvwAiR3ySy1GWBi6Y2AAHM10A
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: <iesg@ietf.org>, <ietf@ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Stephen Trowbridge" <sjtrowbridge@lucent.com>,
        "David Charlap" <David.Charlap@marconi.com>,
        "Loa Andersson" <loa@pi.se>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA26164

Parallel discussions on the thread 'IANA considerations for RSVP' (postings by Steve Trowbridge and David Charlap) and this thread (Loa Andersson) have shed some light on a) how extensions to GMPLS protocols to satisfy ASON requirements shifted from IETF to ITU, and b) the consequences:

steve> - On February 19, 2002, ITU-T sent IETF ccamp a liaison statement regarding
steve>   the gaps that had been identified between the ITU-T requirements (sent
steve>   earlier) and what seemed to be implemented by the GMPLS protocols.
steve>   Specifically,
steve>   1. Call & Connection separation, e.g., a call provides the service
steve>      relationship, which may support connection operations as part of a 
steve>      call. 
steve>   2. Additional error codes/values, for example, for connection rejection
steve>      (invalid connection ID). 
steve>   3. Restart mechanisms: Depending on the introduction by the ITU of 
steve>      additional control plane resiliency requirements, enhancements of the 
steve>      protocol (RSVP-TE, CR-LDP) "graceful restart" mechanisms may be 
steve>      required. 
steve>   4. Protocol enhancements in CR-LDP for support of crankback capability 
steve>      from intermediate nodes. 
steve>   This liaison was presented in the Minneapolis IETF meeting during the 
steve>   ccamp working group and posted on the IESG web site. The liaison requested
steve>   assistance in closing these gaps and invited input from IETF on our work
steve>   in ITU-T.

I recall this discussion and understood that the intent was to have extensions made by CCAMP to GMPLS protocols based on these ASON requirements and thus close the 'gaps'.

steve> - At the April/May 2002 meeting of ITU-T Study Group 15 meeting,
steve> contributions were considered to close these gaps, resulting in text for
steve> draft Recommendations G.7713.2 (our rsvp-te document) and G.7713.3 
steve> (our cr-ldp document). Again, we sent a liaison (dated May 10, 2002) to ask
steve> for comments on our draft Recommendations (made available on the ftp site),
steve> to request alignment, and to ask for IANA code point assignments. To quote
steve> from that liaison:
steve> "Please consider including the proposed solutions provided in G.7713.2 and 
steve> G.7713.3 to update the existing GMPLS signaling work in support of ASON 
steve> requirements.

I think this is consistent with the understanding that the intent was to have extensions made by CCAMP to GMPLS protocols based on the ASON requirements and thus close the 'gaps'.

steve> To hear now that someone thinks that the ASON work in ITU-T is some kind
steve> of secret end-run around IETF, and not involved with or related to the
steve> work being done internally in IETF is absurd. At every stage of the work,
steve> IETF was kept informed of the work and invited to participate. At the
steve> invitation for help to address the additional ITU-T requirements, there
steve> was no response. As ITU-T progressed this work and invited further comments
steve> and alignment of the base GMPLS protocols, again no response. And to the
steve> final pleas for comments and codepoint assignments, no response.
steve> ...
steve> After some private communication with the Area directors, we received some
steve> advice that one tool that might be used to finally get the IANA codepoint
steve> assignment complete would be to publish what we were doing in ITU-T as
steve> informational RFCs. This is the stage we are at today, and given the
steve> history I describe above, I do not think anybody can say that we are
steve> at this point because any of us did not do everything possible to
steve> do this work (a) in IETF, with the initial communication of requirements;
steve> or (b) in cooperation between ITU-T and IETF, once this work had
steve> progressed in ITU-T.
steve> 
steve> But this is all water under the bridge. We are at the point of trying
steve> to get some codepoints assigned for ITU-T documents we are trying to
steve> complete. Nobody should say "no" at this point because they think we
steve> didn't try to work this IN or WITH IETF first. It should be clear to
steve> all that this is not the case.

I can understand the frustration in not getting cooperation and follow-up on the ITU/ASON requirements.  However, the 'private communication with ADs' left most of us in the dark as to what was (is) going on.  

The concern still is (drawing from posts by Loa Andersson and David Charlap):

loa> The consequence of approving the drafts will be that the extensions
loa> by OIF and ITU will be approved by the IETF. I'm not sure that this
loa> has been in the open.

david> I'm far more concerned with non-IETF groups (like ITU, ATM Forum and 
david> others) deciding to develop their own incompatible extensions without 
david> even informing any IETF groups of their actions.
david> Groups like these should not be extending IETF protocols without 
david> consulting with the relevant IETF working groups.  Otherwise 
david> we end up with extensions that duplicate existing IETF functionality, 
david> don't coexist gracefully, and/or break interoperability.  And if these 
david> extensions become popular in products, the IETF will be forced to 
david> include them in the standards in order to prevent future IETF work from 
david> breaking them.

I agree.  

To give one concrete example of the consequences of not doing as David suggests: Now that the subject ID http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.txt has been approved, the crankback TLV defined in Section 4.3 becomes the de-facto crankback TLV, no?  Further discussion/debate in IETF on other proposals (e.g., as proposed in http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt) becomes moot.  This doesn't seem to be the right process to arrive at this technical conclusion.

Jerry Ash 



From owner-ietf@ietf.org  Fri Jan 24 03:06:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12427;
	Fri, 24 Jan 2003 03:06:59 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18bylq-0004ZS-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 03:01:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18byl1-0004Xy-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 03:00:11 -0500
Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12270;
	Fri, 24 Jan 2003 02:53:30 -0500 (EST)
Received: from nj7460exch002h.wins.lucent.com (h135-17-42-35.lucent.com [135.17.42.35])
	by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0O7uvm27975;
	Fri, 24 Jan 2003 02:56:57 -0500 (EST)
Received: by nj7460exch002h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YSR4A92C>; Fri, 24 Jan 2003 02:56:56 -0500
Message-ID: <D3F8FD817CC7DA408AEB2CAC631C042A98E611@nj7460exch012u.ho.lucent.com>
From: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, iesg@ietf.org,
        ietf@ietf.org
Cc: Stephen Trowbridge <sjtrowbridge@lucent.com>,
        David Charlap
	 <David.Charlap@marconi.com>, Loa Andersson <loa@pi.se>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Fri, 24 Jan 2003 02:56:55 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Jerry,

I'm not sure how long you've followed the entire GMPLS and ASON work, but I'm assuming here that you weren't part of the original discussions over the last 1.5 to 2 years on this matter. That's understandable as this wasn't your original area of interest.

However, if you talk with some folks involved since the beginning, you would realize (and also reading Steve's email on the history, or simply going back to the email archives in both MPLS and CCAMP) that
(a) ITU-T tried to get the work done in IETF (I believe Steve mentioned Oct. 21, 2001)
(b) IETF never actually started/initiated work to fill these gaps. So a set of individuals who happens to attend IETF, OIF and ITU decided that they would work towards a solution
(c) This solution was submitted into IETF, OIF, and ITU -- with clear intention of trying to get feedback from the "true" RSVP experts
(d) I (and Bala) created I-Ds in IETF (Bala actually started this I think sometime in early 2002? -- Bala you can confirm or correct -- while I submitted my I-D in June 2002)
(e) These documents were never taken seriously (This is the first email I sent: http://ops.ietf.org/lists/ccamp/ccamp.2002/msg00918.html -- but of course no one responded)
(f) ITU-T requests which were publicly presented in CCAMP meetings by Wesam and Steve (see Steve's email to see how many requests were made) were never taken seriously

The ITU-T delayed their process by several months in order for RSVP experts (I guess Bob Braden would call folks who's done this work "non-RSVP experts") to review. Of course no comments were ever provided by the "true" RSVP experts.

Several individuals tried very hard to try and get a good relationship and collaboration going amongst the three organizations. The break-down is not for lack of trying or exposing the work to the RSVP experts.

As such, although I agree that the original intent of all the individuals who came into this work expecting to collaborate and do the work in IETF CCAMP WG, the actual situation is very much different, and is a result of certain members of the CCAMP WG community deciding not to bother with paying attention to the work. Again I can understand the perception that you get since you weren't involved from the beginning. But a casual perusal of the email archives (too much work for me, if you're interested you should take a look at the history first) would give you a much better and accurate history of the discussions (see http://ops.ietf.org/lists/ccamp for the CCAMP email archive, and http://cell.onecall.net/cell-relay/archives/mpls/mpls.index.html for the MPLS email archive).

Thanks
Zhi


-----Original Message-----
From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
Sent: Thursday, January 23, 2003 7:49 PM
To: iesg@ietf.org; ietf@ietf.org
Cc: Ash, Gerald R (Jerry), ALABS; Stephen Trowbridge; David Charlap; Loa
Andersson
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational


Parallel discussions on the thread 'IANA considerations for RSVP' (postings by Steve Trowbridge and David Charlap) and this thread (Loa Andersson) have shed some light on a) how extensions to GMPLS protocols to satisfy ASON requirements shifted from IETF to ITU, and b) the consequences:

steve> - On February 19, 2002, ITU-T sent IETF ccamp a liaison statement regarding
steve>   the gaps that had been identified between the ITU-T requirements (sent
steve>   earlier) and what seemed to be implemented by the GMPLS protocols.
steve>   Specifically,
steve>   1. Call & Connection separation, e.g., a call provides the service
steve>      relationship, which may support connection operations as part of a 
steve>      call. 
steve>   2. Additional error codes/values, for example, for connection rejection
steve>      (invalid connection ID). 
steve>   3. Restart mechanisms: Depending on the introduction by the ITU of 
steve>      additional control plane resiliency requirements, enhancements of the 
steve>      protocol (RSVP-TE, CR-LDP) "graceful restart" mechanisms may be 
steve>      required. 
steve>   4. Protocol enhancements in CR-LDP for support of crankback capability 
steve>      from intermediate nodes. 
steve>   This liaison was presented in the Minneapolis IETF meeting during the 
steve>   ccamp working group and posted on the IESG web site. The liaison requested
steve>   assistance in closing these gaps and invited input from IETF on our work
steve>   in ITU-T.

I recall this discussion and understood that the intent was to have extensions made by CCAMP to GMPLS protocols based on these ASON requirements and thus close the 'gaps'.

steve> - At the April/May 2002 meeting of ITU-T Study Group 15 meeting,
steve> contributions were considered to close these gaps, resulting in text for
steve> draft Recommendations G.7713.2 (our rsvp-te document) and G.7713.3 
steve> (our cr-ldp document). Again, we sent a liaison (dated May 10, 2002) to ask
steve> for comments on our draft Recommendations (made available on the ftp site),
steve> to request alignment, and to ask for IANA code point assignments. To quote
steve> from that liaison:
steve> "Please consider including the proposed solutions provided in G.7713.2 and 
steve> G.7713.3 to update the existing GMPLS signaling work in support of ASON 
steve> requirements.

I think this is consistent with the understanding that the intent was to have extensions made by CCAMP to GMPLS protocols based on the ASON requirements and thus close the 'gaps'.

steve> To hear now that someone thinks that the ASON work in ITU-T is some kind
steve> of secret end-run around IETF, and not involved with or related to the
steve> work being done internally in IETF is absurd. At every stage of the work,
steve> IETF was kept informed of the work and invited to participate. At the
steve> invitation for help to address the additional ITU-T requirements, there
steve> was no response. As ITU-T progressed this work and invited further comments
steve> and alignment of the base GMPLS protocols, again no response. And to the
steve> final pleas for comments and codepoint assignments, no response.
steve> ...
steve> After some private communication with the Area directors, we received some
steve> advice that one tool that might be used to finally get the IANA codepoint
steve> assignment complete would be to publish what we were doing in ITU-T as
steve> informational RFCs. This is the stage we are at today, and given the
steve> history I describe above, I do not think anybody can say that we are
steve> at this point because any of us did not do everything possible to
steve> do this work (a) in IETF, with the initial communication of requirements;
steve> or (b) in cooperation between ITU-T and IETF, once this work had
steve> progressed in ITU-T.
steve> 
steve> But this is all water under the bridge. We are at the point of trying
steve> to get some codepoints assigned for ITU-T documents we are trying to
steve> complete. Nobody should say "no" at this point because they think we
steve> didn't try to work this IN or WITH IETF first. It should be clear to
steve> all that this is not the case.

I can understand the frustration in not getting cooperation and follow-up on the ITU/ASON requirements.  However, the 'private communication with ADs' left most of us in the dark as to what was (is) going on.  

The concern still is (drawing from posts by Loa Andersson and David Charlap):

loa> The consequence of approving the drafts will be that the extensions
loa> by OIF and ITU will be approved by the IETF. I'm not sure that this
loa> has been in the open.

david> I'm far more concerned with non-IETF groups (like ITU, ATM Forum and 
david> others) deciding to develop their own incompatible extensions without 
david> even informing any IETF groups of their actions.
david> Groups like these should not be extending IETF protocols without 
david> consulting with the relevant IETF working groups.  Otherwise 
david> we end up with extensions that duplicate existing IETF functionality, 
david> don't coexist gracefully, and/or break interoperability.  And if these 
david> extensions become popular in products, the IETF will be forced to 
david> include them in the standards in order to prevent future IETF work from 
david> breaking them.

I agree.  

To give one concrete example of the consequences of not doing as David suggests: Now that the subject ID http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.txt has been approved, the crankback TLV defined in Section 4.3 becomes the de-facto crankback TLV, no?  Further discussion/debate in IETF on other proposals (e.g., as proposed in http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt) becomes moot.  This doesn't seem to be the right process to arrive at this technical conclusion.

Jerry Ash 



From owner-ietf@ietf.org  Fri Jan 24 06:56:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16298;
	Fri, 24 Jan 2003 06:56:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c2RE-0002xB-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 06:56:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c2Qg-0002vk-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 06:55:26 -0500
Received: from maile.telia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16169;
	Fri, 24 Jan 2003 06:48:43 -0500 (EST)
Received: from d1o888.telia.com (d1o888.telia.com [213.67.172.241])
	by maile.telia.com (8.12.5/8.12.5) with ESMTP id h0OBq6j2022582;
	Fri, 24 Jan 2003 12:52:06 +0100 (CET)
X-Original-Recipient: iesg@ietf.org
Received: from pi.se (h70n2fls31o888.telia.com [213.64.120.70])
	by d1o888.telia.com (8.10.2/8.10.1) with ESMTP id h0OBq5210742;
	Fri, 24 Jan 2003 12:52:05 +0100 (CET)
Message-ID: <3E31273C.4040903@pi.se>
Date: Fri, 24 Jan 2003 12:45:00 +0100
From: Loa Andersson <loa@pi.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
CC: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, iesg@ietf.org,
        ietf@ietf.org, Stephen Trowbridge <sjtrowbridge@lucent.com>,
        David Charlap
 <David.Charlap@marconi.com>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
References: <7D5D48D2CAA3D84C813F5B154F43B155BAE781@nl0006exch001u.nl.lucent.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

Bert,

my bad - what I meant was that the extensions in the normative
references would be ietf approved by indirection, when the
documents asking for code points were approved was not obvious
to people reviewing (at least it was not obvious to me,
not that anyone tried to run a secret process

and I'm concerned that the OIF has specified extension to LDP,
and preliminary allocated message names from the IETF concnsus space
more than a year ago and that this does not show in the IANA
registry yet. there are (I believe) implementations of the UNI spec
deployed.

/Loa

Wijnen, Bert (Bert) wrote:

>>loa> The consequence of approving the drafts will be that the 
>>extensions
>>loa> by OIF and ITU will be approved by the IETF. I'm not 
>>sure that this
>>loa> has been in the open.
>>
> 
> Two points:
> - the extensions to LDP were found to be in space that requires
>   IETF Consensus, and so Scott and I asked for an IETF Last Call
>   on the document. That is an explicit OPEN process

> Bert
> 
> 


-- 
Loa Andersson

Mobile          +46 739 81 21 64
Email           loa@pi.se





From owner-ietf@ietf.org  Fri Jan 24 09:21:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20207;
	Fri, 24 Jan 2003 09:21:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c4gf-0004d5-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 09:20:05 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c4ez-0004Yk-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 09:18:21 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19797;
	Fri, 24 Jan 2003 09:11:36 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id h0OEF3kI000537;
	Fri, 24 Jan 2003 09:15:03 -0500 (EST)
Date: Fri, 24 Jan 2003 09:15:03 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200301241415.h0OEF3kI000537@newdev.harvard.edu>
To: ewgray@graiymage.com, Valdis.Kletnieks@vt.edu
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
Cc: iesg@ietf.org, ietf@ietf.org
In-Reply-To: <200301232203.h0NM3p75014231@turing-police.cc.vt.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

> However, unless
> I'm severely confused (which is always possible), the prohibition against
> derivative works came from the ITU side of the fence,

the prohibition is more not used all that often - two main cases where
is is
	1/ vendor work publish for the information of the community
	2/ republishing a standard from another SDO 

just like we would not want the ITU "fixing" an IETF standard w/o our
input it seems a reasonable desire to not have the IETF "fix" an ITU
(or ETSI etc) standard w/o their involvement

Scott



From owner-ietf@ietf.org  Fri Jan 24 09:34:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20764;
	Fri, 24 Jan 2003 09:34:26 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c4sG-0005rg-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 09:32:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c4rs-0005jm-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 09:31:40 -0500
Received: from almso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20489;
	Fri, 24 Jan 2003 09:24:54 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0OEEJIO010017;
	Fri, 24 Jan 2003 09:28:22 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E018D500C; Fri, 24 Jan 2003 09:28:21 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Fri, 24 Jan 2003 09:28:20 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704A17697@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: Last Call: CR-LDP Extensions for ASON to Informational
Thread-Index: AcLDfizY6Ot/njCKTeqHznP+n8sVFgALi1AA
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>, <iesg@ietf.org>, <ietf@ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Stephen Trowbridge" <sjtrowbridge@lucent.com>,
        "David Charlap" <David.Charlap@marconi.com>,
        "Loa Andersson" <loa@pi.se>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA20764

Zhi,

I have followed the ASON and CCAMP work quite closely over the last couple of years.  I am quite familiar and mostly in agreement with your summary of events below.  

What was not well communicated is that the ITU decided (recently) to do the GMPLS/ASON extensions themselves.  I think many of the postings on this thread indicate that people were not aware of, and disagree with, this approach.

I can understand the frustration of not getting attention to the needed ASON requirements in IETF/CCAMP.  IETF/CCAMP had been saying (quoting statements made by chairs and ADs) they need to 'close the gaps' to meet ASON requirements as far back as IETF-53/Minneapolis (March).  CCAMP charter extensions to address same were suggested(IETF-54/Yokohama CCAMP meeting minutes say "The charter update is way overdue. Items may be added - protection/restoration, crankback and multi-area operations."), but CCAMP charter extensions are still pending even to this day.  

However, the answer is not for the ITU (or any other standards body) to extend IETF protocols, and visa versa.  This leads to interoperability problems, I believe, wherein we have 'ITU-TLVs', 'IETF-TLVs', 'OIF-TLVs', etc. for GMPLS protocols.  Furthermore, we are now inheriting many 'ITU-TLVs' for RSVP-TE and CRLDP.  This precludes, or at least inhibits, proper technical discussion to arrive at the best technical approach.  Further discussion on 'ITU-TLVs' (e.g., call control, crankback, etc.) is now moot.

Perhaps we can learn from this and improve the process, e.g.:

a) Bert has proposed a (G)MPLS change process (seems like a good idea),
b) better communication and responsiveness, especially from WG chairs on direct queries (e.g., 'where is the CCAMP charter update?' has been asked many times, but there is no response, still pending).

Regards,
Jerry

> -----Original Message-----
> From: Lin, Zhi-Wei (Zhi) [mailto:zwlin@lucent.com]
> Sent: Friday, January 24, 2003 2:57 AM
> To: Ash, Gerald R (Jerry), ALABS; iesg@ietf.org; ietf@ietf.org
> Cc: Stephen Trowbridge; David Charlap; Loa Andersson
> Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
> 
> Hi Jerry,
> 
> I'm not sure how long you've followed the entire GMPLS and 
> ASON work, but I'm assuming here that you weren't part of the 
> original discussions over the last 1.5 to 2 years on this 
> matter. That's understandable as this wasn't your original 
> area of interest.
> 
> However, if you talk with some folks involved since the 
> beginning, you would realize (and also reading Steve's email 
> on the history, or simply going back to the email archives in 
> both MPLS and CCAMP) that
> (a) ITU-T tried to get the work done in IETF (I believe Steve 
> mentioned Oct. 21, 2001)
> (b) IETF never actually started/initiated work to fill these 
> gaps. So a set of individuals who happens to attend IETF, OIF 
> and ITU decided that they would work towards a solution
> (c) This solution was submitted into IETF, OIF, and ITU -- 
> with clear intention of trying to get feedback from the 
> "true" RSVP experts
> (d) I (and Bala) created I-Ds in IETF (Bala actually started 
> this I think sometime in early 2002? -- Bala you can confirm 
> or correct -- while I submitted my I-D in June 2002)
> (e) These documents were never taken seriously (This is the 
> first email I sent: 
> http://ops.ietf.org/lists/ccamp/ccamp.2002/msg00918.html -- 
> but of course no one responded)
> (f) ITU-T requests which were publicly presented in CCAMP 
> meetings by Wesam and Steve (see Steve's email to see how 
> many requests were made) were never taken seriously
> 
> The ITU-T delayed their process by several months in order 
> for RSVP experts (I guess Bob Braden would call folks who's 
> done this work "non-RSVP experts") to review. Of course no 
> comments were ever provided by the "true" RSVP experts.
> 
> Several individuals tried very hard to try and get a good 
> relationship and collaboration going amongst the three 
> organizations. The break-down is not for lack of trying or 
> exposing the work to the RSVP experts.
> 
> As such, although I agree that the original intent of all the 
> individuals who came into this work expecting to collaborate 
> and do the work in IETF CCAMP WG, the actual situation is 
> very much different, and is a result of certain members of 
> the CCAMP WG community deciding not to bother with paying 
> attention to the work. Again I can understand the perception 
> that you get since you weren't involved from the beginning. 
> But a casual perusal of the email archives (too much work for 
> me, if you're interested you should take a look at the 
> history first) would give you a much better and accurate 
> history of the discussions (see 
> http://ops.ietf.org/lists/ccamp for the CCAMP email archive, 
> and 
> http://cell.onecall.net/cell-relay/archives/mpls/mpls.index.html 
> for the MPLS email archive).
> 
> Thanks
> Zhi



From owner-ietf@ietf.org  Fri Jan 24 09:57:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21395;
	Fri, 24 Jan 2003 09:57:43 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c5KY-000770-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 10:01:18 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bokA-0001xY-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 16:18:38 -0500
Received: from vmmr7.verisignmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20079;
	Thu, 23 Jan 2003 16:12:03 -0500 (EST)
Received: from vmms6.verisignmail.com (vmms6.verisignmail.com [216.168.230.148] (may be forged))
	by vmmr7.verisignmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id OQT34432;
	Thu, 23 Jan 2003 14:46:28 -0500 (EST)
Received: from BOB.AppliedSNMP.com (pcp830034pcs.nrockv01.md.comcast.net [68.50.129.39])
	by vmms6.verisignmail.com (Mirapoint Messaging Server MOS 2.9.3.2)
	with ESMTP id PSW45685;
	Thu, 23 Jan 2003 14:46:25 -0500 (EST)
Message-Id: <5.1.0.14.2.20030123142505.020c53a0@mail.AppliedSNMP.com>
X-Sender: Bob.Natale@AppliedSNMP.com@mail.AppliedSNMP.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 23 Jan 2003 14:48:24 -0500
To: iesg@ietf.org
From: Bob Natale <Bob.Natale@AppliedSNMP.com>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Cc: ietf@ietf.org
In-Reply-To: <2135200C183FD5119588009027DE572302836BF3@webdev-owa.oni.co
 m>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 1/23/2003:11:13 AM, Ong, Lyndon wrote:

Hi all,

[I hope no one minds that I've trimmed the numerous individual
recipient names from the address headers on this thread! :-]

FWIW, I'd like to "second" the comments made by Lyndon below,
in all three parts of his message.

Furthermore, I'd like to add that the IETF leadership should
proceed along the lines of developing more positive and proactive
procedural relationships (quantitatively and qualitatively) with
related external SDOs, especially the OIF and ITU-T in the GMPLS
domain, for the purpose of maximizing overall solution quality
(i.e., how well our protocols play in the real world).  The bottom
line is that we need the benefit of the large-carrier requirements
gathering and specification tasks performed well by the ITU-T and
we can generally leverage the interworking applications analysis
and specification tasks being spearheaded by the OIF.  True, the
IETF does those same tasks at times, sometimes to a large degree
and sometimes to a very limited degree, sometimes successfully
and sometimes not.  Ideally, things will progress (over time) to
the point where formal work plans (divisions of labor) among the
IETF and relevant SDOs can be worked into WG charters and milestones.
There is really no sense in pretending that we can do otherwise
(or need to do so), in the general case, any longer.  [These
comments were intended as much for the "problem-statement"
topic as for this specific thread.]

Cheers,

BobN
- - - - -
>Hi Folks,
>
>I can reaffirm Zhi's comment that call and connection separation 
>goes back to G.8080, an already approved ITU specification of
>the G.ASON architecture.
>
>I'm a bit puzzled by the argument that no one but IETF should be
>allowed to extend an IETF protocol - I would think that extensions
>are generally allowed if they don't cause a limitation on the available
>codepoints and are documented to allow people to use them.  Aren't some
>codepoint partitions designed for people to do this, without having to 
>force all extension work through a WG?
>
>Also, I would think that approving the drafts is just that,
>approving the drafts and their contents as Informational
>documents, it is not being asked that these become IETF Standards.
>  
>Cheers,
>
>Lyndon Ong  






From owner-ietf@ietf.org  Fri Jan 24 09:57:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21418;
	Fri, 24 Jan 2003 09:57:47 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c5CY-0006uf-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 09:53:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bnig-0005Mr-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 15:13:02 -0500
Received: from host19.ipowerweb.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18776;
	Thu, 23 Jan 2003 15:06:27 -0500 (EST)
Received: from h00a0ccd1a9ec.ne.client2.attbi.com ([24.128.219.249] helo=GraIyMage.com)
	by host19.ipowerweb.com with asmtp (Exim 3.36 #1)
	id 18bnel-0006pb-00; Thu, 23 Jan 2003 12:08:59 -0800
Message-ID: <3E304BC0.8C6E051A@GraIyMage.com>
Date: Thu, 23 Jan 2003 15:08:32 -0500
From: Eric Gray <ewgray@graiymage.com>
Reply-To: ewgray@graiymage.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD NSCPCD47  (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
References: <7D5D48D2CAA3D84C813F5B154F43B155BAE4B4@nl0006exch001u.nl.lucent.com>
	            <3E3023D1.4CED192B@GraIyMage.com> <200301231938.h0NJcQ75012548@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host19.ipowerweb.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - graiymage.com
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Valdis,

    This would be a fair concern, but is the business of the standard's
organization to whom a proposal is offered.  The IETF specifically
asks for the right to produce derivative works, in spite of the fact that
the concern you mention applies universally.

    I believe this concern is dealt with by the fact that there is an IETF
official site and various similarly official reflectors.  If an error exist at
an official site, the IETF community has a responsibility to point it out.

Valdis.Kletnieks@vt.edu wrote:

> On Thu, 23 Jan 2003 12:18:09 EST, Eric Gray said:
>
> >     I'm not sure why an RFC might be granted perpetual unrestricted
> > copyright
> > but not allowed in derivative works. Is the intent to include copies as
> > derivative
> > works?
>
> I think the goal is to prevent the creation of non-canonical versions that
> possibly have errata in them.  If I create a derivative work by adding hyperlinks
> and the like, and accidentally change a 3 to a 4 or something like that, all
> sorts of mischief will result....
> --
>                                 Valdis Kletnieks
>                                 Computer Systems Senior Engineer
>                                 Virginia Tech
>
>   ------------------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature







From owner-ietf@ietf.org  Fri Jan 24 09:57:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21421;
	Fri, 24 Jan 2003 09:57:47 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c5CY-0006uZ-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 09:53:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18bn31-0002JV-00
	for ietf@ran.ietf.org; Thu, 23 Jan 2003 14:29:59 -0500
Received: from host19.ipowerweb.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17441;
	Thu, 23 Jan 2003 14:23:25 -0500 (EST)
Received: from h00a0ccd1a9ec.ne.client2.attbi.com ([24.128.219.249] helo=GraIyMage.com)
	by host19.ipowerweb.com with asmtp (Exim 3.36 #1)
	id 18bmzD-0003eO-00; Thu, 23 Jan 2003 11:26:03 -0800
Message-ID: <3E3041B2.96C391D8@GraIyMage.com>
Date: Thu, 23 Jan 2003 14:25:38 -0500
From: Eric Gray <ewgray@graiymage.com>
Reply-To: ewgray@graiymage.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD NSCPCD47  (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
CC: GraIyMag@graiymage.com, Kireeti Kompella <kireeti@juniper.net>,
        Bob Braden <braden@ISI.EDU>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
References: <7D5D48D2CAA3D84C813F5B154F43B155BAE5D8@nl0006exch001u.nl.lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host19.ipowerweb.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - graiymage.com
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bert,

    My comment had nothing to do with the accuracy of references.
It was in reply to what looks like your comment that exclusion of the
right to produce derivative works is "OK since this is documenting
ITU material".  I thought my point was clear, and apologize for any
confusion it may have caused.

    To repeat, hopefully making it clearer this time: it seems somewhat
of a problem when unrestricted copyright is granted without the right
to produce derivative works. If the intent is to include copies as a
form of derivative work, then there are worse problems.  What is the
intent of the restriction in this draft?

    To further clarify what I meant by derivative works, check out these
public sites:

    http://www.faqs.org/rfcs/rfc2026.html
    http://rfc.sunsite.dk/rfc/rfc2026.html

These are good examples of what I was talking about as possible
"derivative works".  They are not exact copies, especially in the second
case which includes hyper-links to at least some referenced material (e.g.
- RFC references).

--
Eric Gray

"Wijnen, Bert (Bert)" wrote:

> We had already found one incorrect reference, and we
> checked with the author, and he agrees it is incorrect
> and that we should fix it. (UNI 1.0 instead of 1.1)
>
> The document references ITU documents G.7713 and G.8080
> Thos as clear references (I think) to documents as they
> are known in ITU. So I see no issue.
>
> It probably should also reference G7713.3, which I think is
> still missing. I am checking with the author as we speak.
> It is quite possible that in ITU process it is OK to refer
> to G7713 and that that automatically includes the G7713.x
> documents. Can ITU folk explain.
>
> In any event, when a document is being prepared by RFC-Editor
> for final publication, they always check the references and
> check with the authors if anything seems incorrect or
> incomplete.
>
> Thanks,
> Bert
>
> > -----Original Message-----
> > From: Eric Gray [mailto:ewgray@graiymage.com]
> > Sent: donderdag 23 januari 2003 18:18
> > To: Wijnen, Bert (Bert)
> > Cc: Kireeti Kompella; Bob Braden; iesg@ietf.org; ietf@ietf.org
> > Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
> >
> >
> > Bert,
> >
> >     A common example of useful "derivative" work is to modify the
> > document such that references include URLs and include it in
> > web-sites. There are any number of private, or semi-private
> > - and maybe one or two public - web sites that have provided
> > hyper-linked versions of Internet Drafts in just this way.
> >
> >     Because this document explicitly excludes derivative works, this
> > precludes
> > doing this for this (eventual) RFC - or, more likely, sets
> > someone up for
> > legal
> > trouble if they have already done so.
> >
> >     I'm not sure why an RFC might be granted perpetual unrestricted
> > copyright but not allowed in derivative works. Is the intent to
> > include copies as derivative works?
> >
> >     It seems a good idea to provide justification - or at least and
> > explanation - if an intended RFC is no in complete compliance with
> > RFC 2026.
> >
> > "Wijnen, Bert (Bert)" wrote:
> >
> > > I noticed today that I gave an incorrect answer to one of
> > > Kireeti's points. He asked and I answered:
> > >
> > > > > I would like to know what the intent is in not granting
> > > > > "the right to produce derivative works",
> > > > Did Steve Trowbridge not answer the first question?
> > > >
> > > This is in the Draft-aboulmagd-crldp-ason-ext-02.txt document.
> > > It states:
> > >
> > >    This document is an Internet-Draft and is in full
> > conformance with
> > >    all provisions of Section 10 of RFC2026 except that the right to
> > >    produce derivative works is not granted.
> > >
> > > But this is OK since this is documenting ITU material.
> > >
> > > Bert and Scott
> >
> >







From owner-ietf@ietf.org  Fri Jan 24 09:59:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21531;
	Fri, 24 Jan 2003 09:59:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c5KY-00077B-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 10:01:18 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c0HJ-0007xT-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 04:37:37 -0500
Received: from shell.nominum.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14072;
	Fri, 24 Jan 2003 04:30:54 -0500 (EST)
Received: from shell.nominum.com (localhost [127.0.0.1])
	by shell.nominum.com (Postfix) with ESMTP
	id C6BE3137F02; Fri, 24 Jan 2003 01:34:22 -0800 (PST)
To: Valdis.Kletnieks@vt.edu
Cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>, ietf@ietf.org,
        iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: Dan Berrnstein deserves what he gets. FW: qsecretary notice 
In-Reply-To: Message from Valdis.Kletnieks@vt.edu 
   of "Wed, 22 Jan 2003 13:13:12 EST." <200301221813.h0MIDCQY007903@turing-police.cc.vt.edu> 
Date: Fri, 24 Jan 2003 01:34:22 -0800
Message-ID: <50041.1043400862@shell.nominum.com>
From: Jim Reid <Jim.Reid@nominum.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

Please take this debate about academic titles somewhere else. It's not
relevant to any of the lists above.





From owner-ietf@ietf.org  Fri Jan 24 10:01:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21726;
	Fri, 24 Jan 2003 10:01:52 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c5LH-000797-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 10:02:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c2Fo-0002fk-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 06:44:12 -0500
Received: from hoemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15976;
	Fri, 24 Jan 2003 06:37:29 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0OBetn24848;
	Fri, 24 Jan 2003 06:40:55 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ269HJB>; Fri, 24 Jan 2003 12:40:51 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE781@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, iesg@ietf.org,
        ietf@ietf.org
Cc: Stephen Trowbridge <sjtrowbridge@lucent.com>,
        David Charlap
	 <David.Charlap@marconi.com>, Loa Andersson <loa@pi.se>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Fri, 24 Jan 2003 12:40:48 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

.. snip ..

> steve> To hear now that someone thinks that the ASON work in 
> ITU-T is some kind
> steve> of secret end-run around IETF, and not involved with 
> or related to the
> steve> work being done internally in IETF is absurd. At every 
> stage of the work,
> steve> IETF was kept informed of the work and invited to 
> participate. At the
> steve> invitation for help to address the additional ITU-T 
> requirements, there
> steve> was no response. As ITU-T progressed this work and 
> invited further comments
> steve> and alignment of the base GMPLS protocols, again no 
> response. And to the
> steve> final pleas for comments and codepoint assignments, no 
> response.
> steve> ...
> steve> After some private communication with the Area 
> directors, we received some
> steve> advice that one tool that might be used to finally get 
> the IANA codepoint
> steve> assignment complete would be to publish what we were 
> doing in ITU-T as
> steve> informational RFCs. This is the stage we are at today, 
> and given the
> steve> history I describe above, I do not think anybody can 
> say that we are
> steve> at this point because any of us did not do everything 
> possible to
> steve> do this work (a) in IETF, with the initial 
> communication of requirements;
> steve> or (b) in cooperation between ITU-T and IETF, once 
> this work had
> steve> progressed in ITU-T.
> steve> 
> steve> But this is all water under the bridge. We are at the 
> point of trying
> steve> to get some codepoints assigned for ITU-T documents we 
> are trying to
> steve> complete. Nobody should say "no" at this point because 
> they think we
> steve> didn't try to work this IN or WITH IETF first. It 
> should be clear to
> steve> all that this is not the case.
> 
> I can understand the frustration in not getting cooperation 
> and follow-up on the ITU/ASON requirements.  However, the 
> 'private communication with ADs' left most of us in the dark 
> as to what was (is) going on.  
> 

Jerry, there is nothing secret on this private communication here.
What Steve is saying is that the ITU people had been sending
emails to IANA to ask for RSVP and LDP code point assignments.
And that did not go smooth. So they asked teh ADs if we could
motivate IANA to take action. That is where we suggested to
write an individual I-D for publication as informational
RFC and to submit that to the RFC-Editor. That way one
achives two things:
- a timer starts ticking on the request to publish I-D as RFC
- RFC-Editor and IANA have documented material to review
  the request

> The concern still is (drawing from posts by Loa Andersson and 
> David Charlap):
> 
> loa> The consequence of approving the drafts will be that the 
> extensions
> loa> by OIF and ITU will be approved by the IETF. I'm not 
> sure that this
> loa> has been in the open.
> 
Two points:
- the extensions to LDP were found to be in space that requires
  IETF Consensus, and so Scott and I asked for an IETF Last Call
  on the document. That is an explicit OPEN process
- the extensions to RSVP are mainly in FCFS space and in such 
  space the IANA can actually assign without any public
  documentation. However IANA decided to ask for documentation
  (and that got supported by teh ADs as per above) and so 
  Zhi and Bala submitted I-Ds. Thes I-Ds have been around
  in various versions for quite a while, and the Zhi document
  was actually discussed in CCAMP meeting a few times, so 
  I do not think it is fair to question if this was possibly
  done in the dark (or closed) rooms.

... snip 

Bert





From owner-ietf@ietf.org  Fri Jan 24 10:42:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22848;
	Fri, 24 Jan 2003 10:42:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c5w1-0002UH-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 10:40:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c5vT-0002OB-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 10:39:27 -0500
Received: from merlot.juniper.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22590;
	Fri, 24 Jan 2003 10:32:41 -0500 (EST)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h0OFZrS40071;
	Fri, 24 Jan 2003 07:35:53 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200301241535.h0OFZrS40071@merlot.juniper.net>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, iesg@ietf.org,
        ietf@ietf.org, Stephen Trowbridge <sjtrowbridge@lucent.com>,
        David Charlap <David.Charlap@marconi.com>, Loa Andersson <loa@pi.se>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational 
In-Reply-To: Your message of "Fri, 24 Jan 2003 12:40:48 +0100."
             <7D5D48D2CAA3D84C813F5B154F43B155BAE781@nl0006exch001u.nl.lucent.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <71514.1043422553.1@juniper.net>
Date: Fri, 24 Jan 2003 07:35:53 -0800
From: Yakov Rekhter <yakov@juniper.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

Bert,

[clipped...]

> Two points:
> - the extensions to LDP were found to be in space that requires
>   IETF Consensus, and so Scott and I asked for an IETF Last Call
>   on the document. That is an explicit OPEN process

Quoting from the e-mail you sent recently:

  If not enough people (and 10 is the absolute minumum, but having seen
  the attendence of TWEG sessions, I'd expect 25 or more) can speak up
  to state one of:
  
   - I read it and I am positive, it is good stuff
   - I read it and I see no problems or objections
   - I read it but I cannot determine if it is bad, but I can see that
     what has been discussed in the WG is indeed in the document
   - I read it and I have these nits/objections...
   - I did not read it cause this is not relevant to my xxx job/work/function
   - I did not read it cause I think this is nonsense 
  
  Then I get the feeling that we're just allowing a small group of
  people push their petty-project through the process. That seems NOT
  good to me. We need serious WG participation in reading and commenting
  in one of these forums above, before we can declare that we have WG
  consensus on a document to be presented to IESG for approval as RFC
  (in whatever form).

Since (as you said) the extensions required IETF consensus, and
with the above in mind could you please share with the rest of
us the information on how many people spoke up about the draft
to state one of:

   - I read it and I am positive, it is good stuff
   - I read it and I see no problems or objections
   - I read it but I cannot determine if it is bad, but I can see that
     what has been discussed in the WG is indeed in the document
   - I read it and I have these nits/objections...
   - I did not read it cause this is not relevant to my xxx job/work/function
   - I did not read it cause I think this is nonsense

Yakov.



From owner-ietf@ietf.org  Fri Jan 24 10:42:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22871;
	Fri, 24 Jan 2003 10:42:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c5uA-0002MX-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 10:38:06 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c5tf-0002KT-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 10:37:35 -0500
Received: from ihemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22513;
	Fri, 24 Jan 2003 10:30:48 -0500 (EST)
Received: from nj7460exch001h.wins.lucent.com (h135-17-42-36.lucent.com [135.17.42.36])
	by ihemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0OFYFd25515;
	Fri, 24 Jan 2003 10:34:15 -0500 (EST)
Received: by nj7460exch001h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <ZFGVTMK9>; Fri, 24 Jan 2003 10:34:15 -0500
Message-ID: <61B49BC6DA0DDE40957FB499E1835E37056281EF@nj7460exch010u.ho.lucent.com>
From: "Varma, Eve L (Eve)" <evarma@lucent.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Lin, Zhi-Wei (Zhi)"
	 <zwlin@lucent.com>, iesg@ietf.org,
        ietf@ietf.org
Cc: Stephen Trowbridge <sjtrowbridge@lucent.com>,
        David Charlap
	 <David.Charlap@marconi.com>, Loa Andersson <loa@pi.se>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Fri, 24 Jan 2003 10:34:12 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Gerry,

In your email, below, you indicate that "What was not well communicated is the the ITU decided (recently) to do the GMPLS/ASON extnesions themselves.  I think many of the postings on this thread indicate that people were not aware of,
and disagree with, this approach".

Quoting from an earlier message from Steve Trowbridge (see below), you can see that proposed extensions were communicated
to ccamp via a May 10, 2002 liaison, and presented at the following Yokohama IETF meeting.  This was subsequent to the Feb. 19, 2001 liaison identifying the gaps that had been identified and requesting support.

 "On February 19, 2002, ITU-T sent IETF ccamp a liaison statement regarding
  the gaps that had been identified between the ITU-T requirements (sent
  earlier) and what seemed to be implemented by the GMPLS protocols. Specifically,
  1. Call & Connection separation, e.g., a call provides the service
     relationship, which may support connection operations as part of a call. 
  2. Additional error codes/values, for example, for connection rejection
     (invalid connection ID). 
  3. Restart mechanisms: Depending on the introduction by the ITU of additional
     control plane resiliency requirements, enhancements of the protocol
     (RSVP-TE, CR-LDP) "graceful restart" mechanisms may be required. 
  4. Protocol enhancements in CR-LDP for support of crankback capability from
     intermediate nodes. 
  This liaison was presented in the Minneapolis IETF meeting during the ccamp
  working group and posted on the IESG web site. The liaison requested
  assistance in closing these gaps and invited input from IETF on our work
  in ITU-T.
- At the April/May 2002 meeting of ITU-T Study Group 15 meeting, contributions
  were considered to close these gaps, resulting in text for draft Recommendations
  G.7713.2 (our rsvp-te document) and G.7713.3 (our cr-ldp document). Again,
  we sent a liaison (dated May 10, 2002) to ask for comments on our draft
  Recommendations (made available on the ftp site), to request alignment, and
  to ask for IANA code point assignments. To quote from that liaison:
"Please consider including the proposed solutions provided in G.7713.2 and G.7713.3
to update the existing GMPLS signaling work in support of ASON requirements.
We hope that you can help expedite the assignment of appropriate additional
error codes/values by IANA.  These are needed for both RSVP-TE and CR-LDP."
  This liaison was presented at the Yokohama IETF ccamp meeting."

Best regards,
Eve

-----Original Message-----
From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
Sent: Friday, January 24, 2003 9:28 AM
To: Lin, Zhi-Wei (Zhi); iesg@ietf.org; ietf@ietf.org
Cc: Ash, Gerald R (Jerry), ALABS; Stephen Trowbridge; David Charlap; Loa
Andersson; Wijnen, Bert (Bert)
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational


Zhi,

I have followed the ASON and CCAMP work quite closely over the last couple of years.  I am quite familiar and mostly in agreement with your summary of events below.  

What was not well communicated is that the ITU decided (recently) to do the GMPLS/ASON extensions themselves.  I think many of the postings on this thread indicate that people were not aware of, and disagree with, this approach.

I can understand the frustration of not getting attention to the needed ASON requirements in IETF/CCAMP.  IETF/CCAMP had been saying (quoting statements made by chairs and ADs) they need to 'close the gaps' to meet ASON requirements as far back as IETF-53/Minneapolis (March).  CCAMP charter extensions to address same were suggested(IETF-54/Yokohama CCAMP meeting minutes say "The charter update is way overdue. Items may be added - protection/restoration, crankback and multi-area operations."), but CCAMP charter extensions are still pending even to this day.  

However, the answer is not for the ITU (or any other standards body) to extend IETF protocols, and visa versa.  This leads to interoperability problems, I believe, wherein we have 'ITU-TLVs', 'IETF-TLVs', 'OIF-TLVs', etc. for GMPLS protocols.  Furthermore, we are now inheriting many 'ITU-TLVs' for RSVP-TE and CRLDP.  This precludes, or at least inhibits, proper technical discussion to arrive at the best technical approach.  Further discussion on 'ITU-TLVs' (e.g., call control, crankback, etc.) is now moot.

Perhaps we can learn from this and improve the process, e.g.:

a) Bert has proposed a (G)MPLS change process (seems like a good idea),
b) better communication and responsiveness, especially from WG chairs on direct queries (e.g., 'where is the CCAMP charter update?' has been asked many times, but there is no response, still pending).

Regards,
Jerry

> -----Original Message-----
> From: Lin, Zhi-Wei (Zhi) [mailto:zwlin@lucent.com]
> Sent: Friday, January 24, 2003 2:57 AM
> To: Ash, Gerald R (Jerry), ALABS; iesg@ietf.org; ietf@ietf.org
> Cc: Stephen Trowbridge; David Charlap; Loa Andersson
> Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
> 
> Hi Jerry,
> 
> I'm not sure how long you've followed the entire GMPLS and 
> ASON work, but I'm assuming here that you weren't part of the 
> original discussions over the last 1.5 to 2 years on this 
> matter. That's understandable as this wasn't your original 
> area of interest.
> 
> However, if you talk with some folks involved since the 
> beginning, you would realize (and also reading Steve's email 
> on the history, or simply going back to the email archives in 
> both MPLS and CCAMP) that
> (a) ITU-T tried to get the work done in IETF (I believe Steve 
> mentioned Oct. 21, 2001)
> (b) IETF never actually started/initiated work to fill these 
> gaps. So a set of individuals who happens to attend IETF, OIF 
> and ITU decided that they would work towards a solution
> (c) This solution was submitted into IETF, OIF, and ITU -- 
> with clear intention of trying to get feedback from the 
> "true" RSVP experts
> (d) I (and Bala) created I-Ds in IETF (Bala actually started 
> this I think sometime in early 2002? -- Bala you can confirm 
> or correct -- while I submitted my I-D in June 2002)
> (e) These documents were never taken seriously (This is the 
> first email I sent: 
> http://ops.ietf.org/lists/ccamp/ccamp.2002/msg00918.html -- 
> but of course no one responded)
> (f) ITU-T requests which were publicly presented in CCAMP 
> meetings by Wesam and Steve (see Steve's email to see how 
> many requests were made) were never taken seriously
> 
> The ITU-T delayed their process by several months in order 
> for RSVP experts (I guess Bob Braden would call folks who's 
> done this work "non-RSVP experts") to review. Of course no 
> comments were ever provided by the "true" RSVP experts.
> 
> Several individuals tried very hard to try and get a good 
> relationship and collaboration going amongst the three 
> organizations. The break-down is not for lack of trying or 
> exposing the work to the RSVP experts.
> 
> As such, although I agree that the original intent of all the 
> individuals who came into this work expecting to collaborate 
> and do the work in IETF CCAMP WG, the actual situation is 
> very much different, and is a result of certain members of 
> the CCAMP WG community deciding not to bother with paying 
> attention to the work. Again I can understand the perception 
> that you get since you weren't involved from the beginning. 
> But a casual perusal of the email archives (too much work for 
> me, if you're interested you should take a look at the 
> history first) would give you a much better and accurate 
> history of the discussions (see 
> http://ops.ietf.org/lists/ccamp for the CCAMP email archive, 
> and 
> http://cell.onecall.net/cell-relay/archives/mpls/mpls.index.html 
> for the MPLS email archive).
> 
> Thanks
> Zhi



From owner-ietf@ietf.org  Fri Jan 24 11:06:53 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23467;
	Fri, 24 Jan 2003 11:06:53 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c6Nh-0004LU-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 11:08:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c6GI-00045l-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 11:00:58 -0500
Received: from kcmso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23152;
	Fri, 24 Jan 2003 10:54:12 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0OEEJoQ020083;
	Fri, 24 Jan 2003 09:57:31 -0600 (CST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E018E13AE; Fri, 24 Jan 2003 10:57:24 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Fri, 24 Jan 2003 10:57:23 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704CB86E3@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: new draft: GMPLS for ASON
Thread-Index: AcIW1lzxXKzzuYFYSe2SpIqvwd7pYwAD2atwKzYZzWA=
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Zhi-Wei Lin" <zwlin@lucent.com>, <iesg@ietf.org>, <ietf@ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Adrian Farrel" <afarrel@movaz.com>,
        "Stephen Trowbridge" <sjtrowbridge@lucent.com>,
        "David Charlap" <David.Charlap@marconi.com>,
        "Loa Andersson" <loa@pi.se>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA23467

Zhi,

> (e) These documents were never taken seriously (This is the first email I
> sent: http://ops.ietf.org/lists/ccamp/ccamp.2002/msg00918.html -- but of
> course no one responded)

Reminder, I responded to your email on June 18, very shortly after you posted (my email to you is attached below).  That I did this off the list was probably a mistake.   We (you, your co-authors, Adrian and I) then had a prolonged exchange of emails about the draft.  Adrian sent you extensive comments on the draft highlighting concerns, suggesting text, and pointing out nits. That you have a reasonably long list of acknowledgements and contributors suggests that the draft was not ignored.

As I commented in the attached email to you, "Would it be worthwhile to somehow 'package' the needed ASON extensions into a proposed GMPLS upgrade and presented to CCAMP as such?"  I still maintain that this would be the correct way to handle this: bring the requirements to CCAMP as a requirements draft, thrash them out, and get the necessary extensions adopted in CCAMP.  Rather, the ITU has developed protocol extensions for GMPLS, something outside the charter of the ITU I believe.

Jerry

-----Original Message-----
From: Ash, Gerald R (Jerry), ALASO 
Sent: Tuesday, June 18, 2002 12:58 PM
To: 'Zhi-Wei Lin'
Cc: Ash, Gerald R (Jerry), ALASO; 'Adrian Farrel'
Subject: RE: new draft: GMPLS for ASON

Hi Zhi,

> I've uploaded a new draft covering the GMPLS usage and extensions to 
> support the ASON requirements. This document proposes appropriate 
> extensions towards the resolution of additional requirements identified 
> and communicated by the ITU-T in support of ITU's ASON standardization 
> effort, and only provides the extensions for RSVP-TE signaling. Among 
> the major extensions include support for the concept of "call", as well 
> as support for setting up soft permanent connections.
> 
> http://www.ietf.org/internet-drafts/draft-lin-ccamp-gmpls-ason-rsvpte-00.txt

Looks good.  

I've attached some excerpts below from the (unpublished) IETF-54/CCAMP meeting minutes.  These also identify crankback, restart, etc. as 'gaps' needing to be filled.  I guess most of these are being worked on, including restart and crankback http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-03.txt (Adrian is currently providing a significant extension for the 04 version of the crankback draft).

Would it be worthwhile to somehow 'package' the needed ASON extensions into a proposed GMPLS upgrade and presented to CCAMP as such?  

Your comments/suggestions are appreciated.

Thanks,
Regards,
Jerry 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Steve Trowbridge

Outlined a variety of "gaps" in the current work:
  - Call and connection separation
  - Additional error codes/value
  - Restart mechanisms
  - Support for crankback
  - Support for soft permanent connection

See proceedings for details.

Eric Mannie: Referring to slide "Identified Gaps".  Gaps seem to be
very small.  Most of the points are solved, can be easily solved, or
are in the process of being solved.

Trowbridge: This was a preliminary scan.  Further review, might turn up
more issues.  Technologies are similar, so lets identify and minimize
gaps.

Dimitri: ITU requirements precede much of IETF work.  Preliminary
discussions indicate that the current gaps are covered by existing
protocol work.  Areas where additional work will be required are
probably minimal, but need to be looked at.  IETF may gain final
improvements by looking at ITU work.

Yong Xue: ITU is working on v2 ASON document so more things could turn
up as "gaps".  Further communication between ITU and IETF should
continue.

Trowbridge: Technology will evolve within both organizations.  Should
expend effort to make sure that they evolve together.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Osama Aboul-Magd -- draft-aboulmagd-ccamp-call-conn-separation-00.txt.

Draft addresses one of the issues that Tolbridge highlighted in his
talk - call and connection control separation.

Kireeti: There is an explicit statement from ITU requiring this.
There is nothing in the charter about this.  This is good stuff.  Ron
and I will go through a charter revision with Ads and discuss putting
this in the charter.  Also need to address other gaps that were raised
by ITU.

Scott: When you propose to add something to WG, it would be helpful to
state where it fits in the existing charter OR how and why charter
should be extended.

Eva: I think that it fits into the character as a requirement to the
signaling protocols.

Scott: OK - that is a good clean explanation that might save chairs
some time.

Yong: I second Eva's comment.

Kireeti: Need to figure out how to address other issues as well.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%



From owner-ietf@ietf.org  Fri Jan 24 11:11:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23645;
	Fri, 24 Jan 2003 11:11:25 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c6T2-0004nt-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 11:14:08 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c6Rj-0004a8-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 11:12:47 -0500
Received: from pmesmtp02.wcom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23440;
	Fri, 24 Jan 2003 11:06:01 -0500 (EST)
Received: from pmismtp06.wcomnet.com ([166.38.62.54])
 by firewall.wcom.com (Iplanet MTA )
 with ESMTP id <0H9800L5O7G9MI@firewall.wcom.com>; Fri,
 24 Jan 2003 16:07:21 +0000 (GMT)
Received: from pmismtp06.wcomnet.com by pmismtp06.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0H9800C017AN0D@pmismtp06.wcomnet.com>; Fri,
 24 Jan 2003 16:07:21 +0000 (GMT)
Received: from vint.wcom.com ([166.60.14.48])
 by pmismtp06.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0H9800BLJ7EFLT@pmismtp06.wcomnet.com>; Fri,
 24 Jan 2003 16:06:17 +0000 (GMT)
Date: Fri, 24 Jan 2003 11:06:12 -0500
From: "vinton g. cerf" <vinton.g.cerf@wcom.com>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
In-reply-to: <200301241415.h0OEF3kI000537@newdev.harvard.edu>
X-Sender: vcerf@pop.wcomnet.com
To: Scott Bradner <sob@harvard.edu>, ewgray@graiymage.com,
        Valdis.Kletnieks@vt.edu
Cc: iesg@ietf.org, ietf@ietf.org
Message-id: <5.1.1.6.2.20030124110504.06130ca8@pop.wcomnet.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Content-type: text/plain; charset=us-ascii
References: <200301232203.h0NM3p75014231@turing-police.cc.vt.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

the reason for copyrighting the standards produced by IETF is precisely
to simultaneously allow IETF to derive new standards documents from the
older ones and to have the ability to prohibit others from doing so without
specific authorization.

Vint

At 09:15 AM 1/24/2003 -0500, Scott Bradner wrote:
>> However, unless
>> I'm severely confused (which is always possible), the prohibition against
>> derivative works came from the ITU side of the fence,
>
>the prohibition is more not used all that often - two main cases where
>is is
>        1/ vendor work publish for the information of the community
>        2/ republishing a standard from another SDO 
>
>just like we would not want the ITU "fixing" an IETF standard w/o our
>input it seems a reasonable desire to not have the IETF "fix" an ITU
>(or ETSI etc) standard w/o their involvement
>
>Scott

Vint Cerf
SVP Architecture & Technology
WorldCom
22001 Loudoun County Parkway, F2-4115
Ashburn, VA 20147
703 886 1690 (v806 1690)
703 886 0047 fax




From owner-ietf@ietf.org  Fri Jan 24 11:27:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24115;
	Fri, 24 Jan 2003 11:27:46 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c6iP-00064x-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 11:30:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c6hS-00060b-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 11:29:02 -0500
Received: from ihemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23974;
	Fri, 24 Jan 2003 11:22:15 -0500 (EST)
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0OGPfd26365;
	Fri, 24 Jan 2003 11:25:41 -0500 (EST)
Received: from lucent.com (sjtrowbridge.lra.lucent.com [135.248.252.10]) by ihmail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id KAA19681; Fri, 24 Jan 2003 10:25:29 -0600 (CST)
Message-ID: <3E3168F0.5375E986@lucent.com>
Date: Fri, 24 Jan 2003 09:25:20 -0700
From: Stephen Trowbridge <sjtrowbridge@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD EMS-1.5  (Windows NT 5.0; U)
X-Accept-Language: en,zh
MIME-Version: 1.0
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
CC: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>, iesg@ietf.org, ietf@ietf.org,
        David Charlap <David.Charlap@marconi.com>, Loa Andersson <loa@pi.se>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
References: <28F05913385EAC43AF019413F674A01704A17697@OCCLUST04EVS1.ugd.att.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

Jerry,
Lets be clear on the timeline and what you consider to be "recent".
- The ASON requirements were communicated October 2001 -
  request for help from ccamp (no response)
- Analysis of ASON requirements against GMPLS protocols, identifying gaps,
  completed Febrary 2002 - request ccamp to help close gaps (no response)
- Proposals into ITU-T agreed about how to close gaps communicated May 2002,
  with request now to align the GMPLS documents with ITU-T work (again, no
  response)
- Final request for comments, October 2002, (again no response)

So the beginning of the actual protocol work in ITU-T dates from eight
months ago. This was seven months AFTER we first communicated the ITU-T
requirements to IETF and started asking for IETF help to develop the
solutions (without getting much interest from the IETF in doing so).

From eight months ago, ITU-T proceeded with the protocol work, all the
while communicating to IETF what we were doing, suggesting that IETF
consider aligning their specifications with the ASON extensions, and
requesting input and comments - again, not much interest from the IETF
to do this. Not much interest until THE DAY that the informational RFCs
are to be published and the codepoints assigned, when we are told we
should have come to IETF first. If only we could have gotten this much
interest in the ASON requirements in October 2001 ...

Regards,
Steve

"Ash, Gerald R (Jerry), ALABS" wrote:
> 
> Zhi,
> 
> I have followed the ASON and CCAMP work quite closely over the last couple of years.  I am quite familiar and mostly in agreement with your summary of events below.
> 
> What was not well communicated is that the ITU decided (recently) to do the GMPLS/ASON extensions themselves.  I think many of the postings on this thread indicate that people were not aware of, and disagree with, this approach.
> 
> I can understand the frustration of not getting attention to the needed ASON requirements in IETF/CCAMP.  IETF/CCAMP had been saying (quoting statements made by chairs and ADs) they need to 'close the gaps' to meet ASON requirements as far back as IETF-53/Minneapolis (March).  CCAMP charter extensions to address same were suggested(IETF-54/Yokohama CCAMP meeting minutes say "The charter update is way overdue. Items may be added - protection/restoration, crankback and multi-area operations."), but CCAMP charter extensions are still pending even to this day.
> 
> However, the answer is not for the ITU (or any other standards body) to extend IETF protocols, and visa versa.  This leads to interoperability problems, I believe, wherein we have 'ITU-TLVs', 'IETF-TLVs', 'OIF-TLVs', etc. for GMPLS protocols.  Furthermore, we are now inheriting many 'ITU-TLVs' for RSVP-TE and CRLDP.  This precludes, or at least inhibits, proper technical discussion to arrive at the best technical approach.  Further discussion on 'ITU-TLVs' (e.g., call control, crankback, etc.) is now moot.
> 
> Perhaps we can learn from this and improve the process, e.g.:
> 
> a) Bert has proposed a (G)MPLS change process (seems like a good idea),
> b) better communication and responsiveness, especially from WG chairs on direct queries (e.g., 'where is the CCAMP charter update?' has been asked many times, but there is no response, still pending).
> 
> Regards,
> Jerry
> 
> > -----Original Message-----
> > From: Lin, Zhi-Wei (Zhi) [mailto:zwlin@lucent.com]
> > Sent: Friday, January 24, 2003 2:57 AM
> > To: Ash, Gerald R (Jerry), ALABS; iesg@ietf.org; ietf@ietf.org
> > Cc: Stephen Trowbridge; David Charlap; Loa Andersson
> > Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
> >
> > Hi Jerry,
> >
> > I'm not sure how long you've followed the entire GMPLS and
> > ASON work, but I'm assuming here that you weren't part of the
> > original discussions over the last 1.5 to 2 years on this
> > matter. That's understandable as this wasn't your original
> > area of interest.
> >
> > However, if you talk with some folks involved since the
> > beginning, you would realize (and also reading Steve's email
> > on the history, or simply going back to the email archives in
> > both MPLS and CCAMP) that
> > (a) ITU-T tried to get the work done in IETF (I believe Steve
> > mentioned Oct. 21, 2001)
> > (b) IETF never actually started/initiated work to fill these
> > gaps. So a set of individuals who happens to attend IETF, OIF
> > and ITU decided that they would work towards a solution
> > (c) This solution was submitted into IETF, OIF, and ITU --
> > with clear intention of trying to get feedback from the
> > "true" RSVP experts
> > (d) I (and Bala) created I-Ds in IETF (Bala actually started
> > this I think sometime in early 2002? -- Bala you can confirm
> > or correct -- while I submitted my I-D in June 2002)
> > (e) These documents were never taken seriously (This is the
> > first email I sent:
> > http://ops.ietf.org/lists/ccamp/ccamp.2002/msg00918.html --
> > but of course no one responded)
> > (f) ITU-T requests which were publicly presented in CCAMP
> > meetings by Wesam and Steve (see Steve's email to see how
> > many requests were made) were never taken seriously
> >
> > The ITU-T delayed their process by several months in order
> > for RSVP experts (I guess Bob Braden would call folks who's
> > done this work "non-RSVP experts") to review. Of course no
> > comments were ever provided by the "true" RSVP experts.
> >
> > Several individuals tried very hard to try and get a good
> > relationship and collaboration going amongst the three
> > organizations. The break-down is not for lack of trying or
> > exposing the work to the RSVP experts.
> >
> > As such, although I agree that the original intent of all the
> > individuals who came into this work expecting to collaborate
> > and do the work in IETF CCAMP WG, the actual situation is
> > very much different, and is a result of certain members of
> > the CCAMP WG community deciding not to bother with paying
> > attention to the work. Again I can understand the perception
> > that you get since you weren't involved from the beginning.
> > But a casual perusal of the email archives (too much work for
> > me, if you're interested you should take a look at the
> > history first) would give you a much better and accurate
> > history of the discussions (see
> > http://ops.ietf.org/lists/ccamp for the CCAMP email archive,
> > and
> > http://cell.onecall.net/cell-relay/archives/mpls/mpls.index.html
> > for the MPLS email archive).
> >
> > Thanks
> > Zhi



From owner-ietf@ietf.org  Fri Jan 24 11:34:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24300;
	Fri, 24 Jan 2003 11:34:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c6oI-0006ig-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 11:36:06 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c6nH-0006Tr-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 11:35:03 -0500
Received: from LON2FP-SMTP01.radianz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24159;
	Fri, 24 Jan 2003 11:28:13 -0500 (EST)
Received: from ran.ietf.org ([132.151.6.60])
          by LON2FP-SMTP01.radianz.com (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003012416155777:3468 ;
          Fri, 24 Jan 2003 16:15:57 +0000 
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c6Nh-0004LU-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 11:08:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c6GI-00045l-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 11:00:58 -0500
Received: from kcmso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23152;
	Fri, 24 Jan 2003 10:54:12 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0OEEJoQ020083;
	Fri, 24 Jan 2003 09:57:31 -0600 (CST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E018E13AE; Fri, 24 Jan 2003 10:57:24 -0500
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Thread-Topic: new draft: GMPLS for ASON
Thread-Index: AcIW1lzxXKzzuYFYSe2SpIqvwd7pYwAD2atwKzYZzWA=
X-MIMETrack: Itemize by SMTP Server on LON2FP-SMTP01/UK-Serv/RadianzExt(Release 5.0.9a |January
 7, 2002) at 24/01/2003 16:15:58,
	Serialize by Router on LON2FP-SMTP01/UK-Serv/RadianzExt(Release 5.0.9a |January
 7, 2002) at 24/01/2003 16:36:07,
	Serialize complete at 24/01/2003 16:36:07
To: "Zhi-Wei Lin" <zwlin@lucent.com>, <iesg@ietf.org>, <ietf@ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Adrian Farrel" <afarrel@movaz.com>,
        "Stephen Trowbridge" <sjtrowbridge@lucent.com>,
        "David Charlap" <David.Charlap@marconi.com>,
        "Loa Andersson" <loa@pi.se>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Message-ID: <OF229E5757.06459FA0-ON80256CB8.00595A72-80256CB8.005AC945@radianz.com>
Date: Fri, 24 Jan 2003 16:31:37 +0000
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA24300

Zhi,

> (e) These documents were never taken seriously (This is the first email I
> sent: http://ops.ietf.org/lists/ccamp/ccamp.2002/msg00918.html -- but of
> course no one responded)

Reminder, I responded to your email on June 18, very shortly after you posted (my email to you is attached below).  That I did this off the list was probably a mistake.   We (you, your co-authors, Adrian and I) then had a prolonged exchange of emails about the draft.  Adrian sent you extensive comments on the draft highlighting concerns, suggesting text, and pointing out nits. That you have a reasonably long list of acknowledgements and contributors suggests that the draft was not ignored.

As I commented in the attached email to you, "Would it be worthwhile to somehow 'package' the needed ASON extensions into a proposed GMPLS upgrade and presented to CCAMP as such?"  I still maintain that this would be the correct way to handle this: bring the requirements to CCAMP as a requirements draft, thrash them out, and get the necessary extensions adopted in CCAMP.  Rather, the ITU has developed protocol extensions for GMPLS, something outside the charter of the ITU I believe.

Jerry

-----Original Message-----
From: Ash, Gerald R (Jerry), ALASO 
Sent: Tuesday, June 18, 2002 12:58 PM
To: 'Zhi-Wei Lin'
Cc: Ash, Gerald R (Jerry), ALASO; 'Adrian Farrel'
Subject: RE: new draft: GMPLS for ASON

Hi Zhi,

> I've uploaded a new draft covering the GMPLS usage and extensions to 
> support the ASON requirements. This document proposes appropriate 
> extensions towards the resolution of additional requirements identified 
> and communicated by the ITU-T in support of ITU's ASON standardization 
> effort, and only provides the extensions for RSVP-TE signaling. Among 
> the major extensions include support for the concept of "call", as well 
> as support for setting up soft permanent connections.
> 
> http://www.ietf.org/internet-drafts/draft-lin-ccamp-gmpls-ason-rsvpte-00.txt

Looks good.  

I've attached some excerpts below from the (unpublished) IETF-54/CCAMP meeting minutes.  These also identify crankback, restart, etc. as 'gaps' needing to be filled.  I guess most of these are being worked on, including restart and crankback http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-03.txt (Adrian is currently providing a significant extension for the 04 version of the crankback draft).

Would it be worthwhile to somehow 'package' the needed ASON extensions into a proposed GMPLS upgrade and presented to CCAMP as such?  

Your comments/suggestions are appreciated.

Thanks,
Regards,
Jerry 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Steve Trowbridge

Outlined a variety of "gaps" in the current work:
  - Call and connection separation
  - Additional error codes/value
  - Restart mechanisms
  - Support for crankback
  - Support for soft permanent connection

See proceedings for details.

Eric Mannie: Referring to slide "Identified Gaps".  Gaps seem to be
very small.  Most of the points are solved, can be easily solved, or
are in the process of being solved.

Trowbridge: This was a preliminary scan.  Further review, might turn up
more issues.  Technologies are similar, so lets identify and minimize
gaps.

Dimitri: ITU requirements precede much of IETF work.  Preliminary
discussions indicate that the current gaps are covered by existing
protocol work.  Areas where additional work will be required are
probably minimal, but need to be looked at.  IETF may gain final
improvements by looking at ITU work.

Yong Xue: ITU is working on v2 ASON document so more things could turn
up as "gaps".  Further communication between ITU and IETF should
continue.

Trowbridge: Technology will evolve within both organizations.  Should
expend effort to make sure that they evolve together.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Osama Aboul-Magd -- draft-aboulmagd-ccamp-call-conn-separation-00.txt.

Draft addresses one of the issues that Tolbridge highlighted in his
talk - call and connection control separation.

Kireeti: There is an explicit statement from ITU requiring this.
There is nothing in the charter about this.  This is good stuff.  Ron
and I will go through a charter revision with Ads and discuss putting
this in the charter.  Also need to address other gaps that were raised
by ITU.

Scott: When you propose to add something to WG, it would be helpful to
state where it fits in the existing charter OR how and why charter
should be extended.

Eva: I think that it fits into the character as a requirement to the
signaling protocols.

Scott: OK - that is a good clean explanation that might save chairs
some time.

Yong: I second Eva's comment.

Kireeti: Need to figure out how to address other issues as well.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%




From owner-ietf@ietf.org  Fri Jan 24 12:41:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26139;
	Fri, 24 Jan 2003 12:41:04 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c7p7-0001ba-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 12:41:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c7oE-0001ZM-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 12:40:06 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25852;
	Fri, 24 Jan 2003 12:33:18 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id 2388967103; Fri, 24 Jan 2003 12:44:35 -0500 (EST)
Date: Fri, 24 Jan 2003 12:36:45 -0500
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: ietf@ietf.org, kireeti@juniper.net, iesg@ietf.org
To: Bob Braden <braden@ISI.EDU>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200301232254.WAA02326@gra.isi.edu>
Message-Id: <68912DAE-2FC2-11D7-A11A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Thursday, Jan 23, 2003, at 17:54 America/Montreal, Bob Braden wrote:
> I interpret "IETF consensus" as meaning that at least a Last
> Call was conducted.  To use any other interpretation seems to me to
> be dishonest.  I guess I am agreeing with Kireeti.

[IAB hat off]

I agree with the above.   IESG approval is not identical to IETF 
consensus.
If it were, the IETF community would not be giving such vocal feedback
about concerns with the IESG at the last 2 meetings and on the 
ietf-problems
mailing list, IMHO.

I don't see how I could support the IESG if such a decision were 
appealed
to the IAB and no *successful* (meaning no substantive negative comments
received) Last Call were held per the usual IETF procedures.

Ran Atkinson
rja@extremenetworks.com




From owner-ietf@ietf.org  Fri Jan 24 13:23:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27550;
	Fri, 24 Jan 2003 13:23:52 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c8WA-0003WX-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 13:25:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c8QO-0003Ng-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 13:19:32 -0500
Received: from prue.eim.surrey.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27116;
	Fri, 24 Jan 2003 13:12:45 -0500 (EST)
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 18c8Mx-0001Ib-00; Fri, 24 Jan 2003 18:15:59 +0000
Date: Fri, 24 Jan 2003 18:15:57 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: RJ Atkinson <rja@extremenetworks.com>
cc: Bob Braden <braden@ISI.EDU>, "" <ietf@ietf.org>, "" <kireeti@juniper.net>,
        "" <iesg@ietf.org>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
In-Reply-To: <68912DAE-2FC2-11D7-A11A-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.50.0301241815190.27937-100000@artemis.ee.surrey.ac.uk>
References: <68912DAE-2FC2-11D7-A11A-00039357A82A@extremenetworks.com>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-103.3 required=7.0
	tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,NOSPAM_INC,
	      QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,
	      USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.43
X-Scanner: exiscan *18c8Mx-0001Ib-00*uChaKBz6.bA* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 24 Jan 2003, RJ Atkinson wrote:

> On Thursday, Jan 23, 2003, at 17:54 America/Montreal, Bob Braden wrote:
> > I interpret "IETF consensus" as meaning that at least a Last
> > Call was conducted.  To use any other interpretation seems to me to
> > be dishonest.  I guess I am agreeing with Kireeti.
>
> [IAB hat off]
>
> I agree with the above.  IESG approval is not identical to IETF
> consensus. If it were, the IETF community would not be giving such
> vocal feedback about concerns with the IESG at the last 2 meetings
> and on the ietf-problems mailing list, IMHO.

Can you give a pointer to this ietf-problems mailing list, please?

L.

> I don't see how I could support the IESG if such a decision were
> appealed to the IAB and no *successful* (meaning no substantive
> negative comments received) Last Call were held per the usual IETF
> procedures.
>
> Ran Atkinson
> rja@extremenetworks.com

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



From owner-ietf@ietf.org  Fri Jan 24 14:33:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29920;
	Fri, 24 Jan 2003 14:33:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18c9aS-0005zv-00
	for ietf-list@ran.ietf.org; Fri, 24 Jan 2003 14:34:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c9Zy-0005xb-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 14:33:30 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29654;
	Fri, 24 Jan 2003 14:26:42 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 7B277621FA; Fri, 24 Jan 2003 20:30:09 +0100 (CET)
Date: Fri, 24 Jan 2003 20:30:09 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>,
        RJ Atkinson <rja@extremenetworks.com>
Cc: Bob Braden <braden@ISI.EDU>, ietf@ietf.org, kireeti@juniper.net,
        iesg@ietf.org
Subject: Problem-statement (Re: Last Call: CR-LDP Extensions for ASON to
 Informational)
Message-ID: <260010000.1043436609@askvoll.hjemme.alvestrand.no>
In-Reply-To: <Pine.GSO.4.50.0301241815190.27937-100000@artemis.ee.surrey.ac.uk>
References: <68912DAE-2FC2-11D7-A11A-00039357A82A@extremenetworks.com>
 <Pine.GSO.4.50.0301241815190.27937-100000@artemis.ee.surrey.ac.uk>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On fredag, januar 24, 2003 18:15:57 +0000 Lloyd Wood 
<l.wood@eim.surrey.ac.uk> wrote:

> On Fri, 24 Jan 2003, RJ Atkinson wrote:
>
>> On Thursday, Jan 23, 2003, at 17:54 America/Montreal, Bob Braden wrote:
>> > I interpret "IETF consensus" as meaning that at least a Last
>> > Call was conducted.  To use any other interpretation seems to me to
>> > be dishonest.  I guess I am agreeing with Kireeti.
>>
>> [IAB hat off]
>>
>> I agree with the above.  IESG approval is not identical to IETF
>> consensus. If it were, the IETF community would not be giving such
>> vocal feedback about concerns with the IESG at the last 2 meetings
>> and on the ietf-problems mailing list, IMHO.
>
> Can you give a pointer to this ietf-problems mailing list, please?

problem-statement@alvestrand.no - use the "-request" convention to 
subscribe.

This list was set up in conjunction with the IESG plenary in Atlanta, and 
has been used to continue the discussion from there. A working group 
charter is being discussed.

                Harald

>
> L.
>
>> I don't see how I could support the IESG if such a decision were
>> appealed to the IAB and no *successful* (meaning no substantive
>> negative comments received) Last Call were held per the usual IETF
>> procedures.
>>
>> Ran Atkinson
>> rja@extremenetworks.com
>
> <http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which
> is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on
> what to pass are made solely by Raffaele D'Albenzio.
>





From owner-ietf@ietf.org  Mon Jan 27 09:52:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16691;
	Mon, 27 Jan 2003 09:52:58 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dAXM-0008FJ-00
	for ietf-list@ran.ietf.org; Mon, 27 Jan 2003 09:47:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c6Qn-0004XH-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 11:11:49 -0500
Received: from pigeon.verisign.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23423;
	Fri, 24 Jan 2003 11:05:02 -0500 (EST)
Received: from vhqpostal-gw1.verisign.com (verisign.com [65.205.251.55])
        by pigeon.verisign.com (8.12.1/) with ESMTP id h0OG6l3k001220;
        Fri, 24 Jan 2003 08:06:47 -0800 (PST)
Received: by vhqpostal-gw1.verisign.com with Internet Mail Service (5.5.2656.59)
	id <ZHLNHK27>; Fri, 24 Jan 2003 08:08:29 -0800
Message-ID: <CE541259607DE94CA2A23816FB49F4A3954871@vhqpostal6.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: Jim Reid <Jim.Reid@nominum.com>, Valdis.Kletnieks@vt.edu
Cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>, ietf@ietf.org,
        iesg@ietf.org, namedroppers@ops.ietf.org
Subject: RE: Dan Berrnstein deserves what he gets. FW: qsecretary notice 
Date: Fri, 24 Jan 2003 08:08:26 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
MIME-Version: 1.0
Content-Type: multipart/signed;
	protocol="application/x-pkcs7-signature";
	boundary="----=_NextPart_000_009C_01C2C398.CCFBE220";
	micalg=SHA1
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

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

My objective was to try to put an end to the Bernstein thread, not to 
start yet another.

I appologise for paying insufficient respect to the decorations and
titles of the New World.

I did not realise that it was the custom in these parts for the holders 
of academic titles to address themselves in the third person.

    Phill

    Dr. Phillip M. Hallam-Baker, B.Sc(Soton), D.Phil(Oxon), C.Eng, FBCS

> -----Original Message-----
> From: Jim Reid [mailto:Jim.Reid@nominum.com]
> Sent: Friday, January 24, 2003 4:34 AM
> To: Valdis.Kletnieks@vt.edu
> Cc: Hallam-Baker, Phillip; ietf@ietf.org; iesg@ietf.org;
> namedroppers@ops.ietf.org
> Subject: Re: Dan Berrnstein deserves what he gets. FW: 
> qsecretary notice
> 
> 
> 
> Please take this debate about academic titles somewhere else. It's not
> relevant to any of the lists above.
> 

------=_NextPart_000_009C_01C2C398.CCFBE220
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Disposition: attachment;
	filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINbTCCAj0w
ggGmAhEAulrJTAU7ktantt9O0FOSDTANBgkqhkiG9w0BAQIFADBfMQswCQYDVQQGEwJVUzEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xNzA1BgNVBAsTLkNsYXNzIDIgUHVibGljIFByaW1hcnkgQ2Vy
dGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNOTYwMTI5MDAwMDAwWhcNMDQwMTA3MjM1OTU5WjBfMQsw
CQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNzA1BgNVBAsTLkNsYXNzIDIgUHVi
bGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwgZ8wDQYJKoZIhvcNAQEBBQADgY0A
MIGJAoGBALZai6MNaiODgGvPOYf0IRMzBkwlou1VEpfFp4C5+oPBIKD6LxUNfKFga355LPoGDzqu
9htvsdL/LyhSX4N9S8R6t/hmH4BU/LfCjllKFFdG0ZqTvkGRA7sVgJNc6+fMCGw/PrNK/P9LbCPV
UIImRBmOI8Nx6hkkRwSedb/IpgAfAgMBAAEwDQYJKoZIhvcNAQECBQADgYEAtgAfk1ekB6dAzmVA
P1Ve7e/6VEmlMNYhfGGH7oOTC7+0M/KYrJ8Gv06ozhSBTMsETljDz1/ufNeab8tBird/gbj/hGHG
J0NlHQzssQAK3Ruku8d4ICiyot02lS7hVE+/YLl3aBGZI+jqUuiqAE5nTruQtUWbRuuOFu/EM1sz
PdUwggNDMIICrKADAgECAhAffl/nA9Hgv5kg3GuJDUsEMA0GCSqGSIb3DQEBBAUAMF8xCzAJBgNV
BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMiBQdWJsaWMg
UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05OTAyMjUwMDAwMDBaFw0wNDAxMDUy
MzU5NTlaMIGtMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1
c3QgTmV0d29yazFJMEcGA1UECxNAVXNlIGlzIHN1YmplY3QgdG8gdGVybXMgYXQgaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL3JwYS1rciAoYyk5OTEmMCQGA1UEAxMdVmVyaVNpZ24gQ2xhc3MgMiBQ
ZXJzb25uZWwgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAKcEbA+icrdKBi741yksNJ2C
vEiRSses+en8uVl4sVXAU1ixz28WO8FJ1cv0bszhzMu1xy5OiKo06bbQW3w+FVc04Ri8/931r2dZ
IArlPeqIikDSmokTKam21dunfuHnNyST/ZR0TXrkMm1M6FwWl6/dktlmihRm5OpaA6g9X/sLAgMB
AAGjgbAwga0wMQYDVR0fBCowKDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMi5j
cmwwEQYJYIZIAYb4QgEBBAQDAgEGMEcGA1UdIARAMD4wPAYLYIZIAYb4RQEHAQEwLTArBggrBgEF
BQcCARYfaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYS1rcjAPBgNVHRMECDAGAQH/AgEBMAsG
A1UdDwQEAwIBBjANBgkqhkiG9w0BAQQFAAOBgQB59xXN6GhRWWv8qaa94B77vPQ/kN/n+u3kVPdh
PVSLBrqXMloeqyzur3Orx13TP4/0zstOSGCiqGC2ON6gpvePKegRrMw5dlA83TlsC/Fa/QhUdt0W
bPcxcLi/CPfJJgaO37svGbG2uLToPEjoJ7GXKSBXA5ybZ/p9QMQ4fxiqmjCCA8QwggMtoAMCAQIC
EQCEzvIOADm1dVXaGYePUu2JMA0GCSqGSIb3DQEBBAUAMIGtMRcwFQYDVQQKEw5WZXJpU2lnbiwg
SW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFJMEcGA1UECxNAVXNlIGlzIHN1
YmplY3QgdG8gdGVybXMgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYS1rciAoYyk5OTEm
MCQGA1UEAxMdVmVyaVNpZ24gQ2xhc3MgMiBQZXJzb25uZWwgQ0EwHhcNOTkwMjI1MDAwMDAwWhcN
MDQwMTA0MjM1OTU5WjCBrDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxSTBHBgNVBAsTQFVzZSBpcyBzdWJqZWN0IHRvIHRlcm1zIGF0IGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEta3IgKGMpOTkxJTAjBgNVBAMTHFZlcmlTaWduIENs
YXNzIDIgRW1wbG95ZWUgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMCK0YdhouowA1Vr
CDbwl/oaVDUkH+h9ncjDc9PYRvWRLdk47ZTXsCZzKt6XUE3/Ihy9cACYDFgqsaRyj6W59y18YOO1
3+l9TiEhYdX8O1TJpAmcuyL5orpwYU+GRqL9BWTsCj+mWHZXuxZzRHzwpQ2XwGym8WMIJbEEF5Wg
jf5/AgMBAAGjgeIwgd8wKQYDVR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDEtMTE4
MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwudmVyaXNpZ24uY29tL1ZTQ2xhc3MySW50LmNy
bDARBglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUF
BwIBFh9odHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhLWtyMA8GA1UdEwQIMAYBAf8CAQAwCwYD
VR0PBAQDAgEGMA0GCSqGSIb3DQEBBAUAA4GBABlGztRrcI5YXIhCNa0WfaUJLKhTkPH2PYbX8M5y
FD0ivPLDM+3U/AWa4GMgdaMb71UZDwZzIQJhrqaeUSt43FvIhIvV17bP1fg+l5ixRIujmI6gS/aY
MZOz8AzdUXbKl+RWRMb7lKFIfSJDzKDGXHlV9WeBG2iYNCREsZjBOiheMIIEGTCCA4KgAwIBAgIQ
da9pAn9XoMlLtvoUDq8LyTANBgkqhkiG9w0BAQQFADCBrDEXMBUGA1UEChMOVmVyaVNpZ24sIElu
Yy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxSTBHBgNVBAsTQFVzZSBpcyBzdWJq
ZWN0IHRvIHRlcm1zIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEta3IgKGMpOTkxJTAj
BgNVBAMTHFZlcmlTaWduIENsYXNzIDIgRW1wbG95ZWUgQ0EwHhcNMDIwMjI3MDAwMDAwWhcNMDMw
MjI3MjM1OTU5WjBtMREwDwYDVQQKEwhWRVJJU0lHTjELMAkGA1UECxMCSFExEzARBgNVBAMTClJl
Y2lwaWVudHMxNjA0BgNVBAMTLXBiYWtlciAoSGFsbGFtLUJha2VyIFBoaWxsaXAsIFZlcmlTaWdu
LCBJbmMuKTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAtcA/okLsFi9brjmDsXQ6+g+R95B1
81Lq1EXkdzhY7XHxQ2QDq0sS2U4j9N1Ic6nHIiMq5dticztWpKdn6CrDx3Ovd5k+PACq/jSQo7NL
tlMJi7fsUrP7pM4izKu4JjSak6wRJUA4x85TSC1PLfd1u8oq16iqNJRhpEJ8VJUMRyECAwEAAaOC
AXgwggF0MAkGA1UdEwQCMAAwWQYDVR0fBFIwUDBOoEygSoZIaHR0cDovL29uc2l0ZWNybC52ZXJp
c2lnbi5jb20vVmVyaVNpZ25JbmNFeGNoYW5nZUVtcGxveWVlcy9MYXRlc3RDUkwuY3JsMAsGA1Ud
DwQEAwIFoDAeBgNVHREEFzAVgRNwYmFrZXJAdmVyaXNpZ24uY29tMIGsBgNVHSAEgaQwgaEwgZ4G
C2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BT
MGIGCCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5j
b3JwLiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEE
BAMCB4AwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMA0GCSqGSIb3DQEBBAUAA4GBACCK
+gbdTcJB2wmWF5q8hbnP6slvVFehmjSX1Se+4Ff6a3Uiw8aOQLyNwnYUSOtHe12rTwAtWOhEgXHK
D4XY3tF7cofo5hM8dk8xsj9vV3z3fYARDr4nR2bZblPJ3MGmAFAYKW4pgX4Y6NU4VhAG2Hiuj18/
H4Cc5g5oqJp5dArUMYIC+DCCAvQCAQEwgcEwgawxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8w
HQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUkwRwYDVQQLE0BVc2UgaXMgc3ViamVjdCB0
byB0ZXJtcyBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhLWtyIChjKTk5MSUwIwYDVQQD
ExxWZXJpU2lnbiBDbGFzcyAyIEVtcGxveWVlIENBAhB1r2kCf1egyUu2+hQOrwvJMAkGBSsOAwIa
BQCgggGMMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAzMDEyNDE2
MDczNlowIwYJKoZIhvcNAQkEMRYEFOAzEvkVm4WM893rsuvCV8x+y293MFgGCSqGSIb3DQEJDzFL
MEkwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMAcG
BSsOAwIaMAoGCCqGSIb3DQIFMIHSBgkrBgEEAYI3EAQxgcQwgcEwgawxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUkwRwYDVQQLE0BVc2Ug
aXMgc3ViamVjdCB0byB0ZXJtcyBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhLWtyIChj
KTk5MSUwIwYDVQQDExxWZXJpU2lnbiBDbGFzcyAyIEVtcGxveWVlIENBAhB1r2kCf1egyUu2+hQO
rwvJMA0GCSqGSIb3DQEBAQUABIGAIAaKCkFIJ86z3laggDWtf8o1NGZOMnOgfUJxqQSINADvkmbY
o6rEia8FQyrUDESW/RgKD/5FP8+uwnBUU5NJ21yPuj6gSVYKof8VuW7S7h6LnRTliV0GOftr2I5f
aWJpRomQGnZlbqs0+8Cqp5ukAUAkiXm+3GoLHAkLpkX0EYkAAAAAAAA=

------=_NextPart_000_009C_01C2C398.CCFBE220--






From owner-ietf@ietf.org  Mon Jan 27 09:53:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16721;
	Mon, 27 Jan 2003 09:53:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dAaK-0008Kr-00
	for ietf-list@ran.ietf.org; Mon, 27 Jan 2003 09:50:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18cExh-0007No-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 20:18:21 -0500
Received: from mail.alcatel.be (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06770;
	Fri, 24 Jan 2003 20:11:29 -0500 (EST)
Received: from bemail05.net.alcatel.be (localhost [127.0.0.1])
	by mail.alcatel.be (8.10.1/8.11.4) with ESMTP id h0P1Eq007220;
	Sat, 25 Jan 2003 02:14:52 +0100 (MET)
Received: from alcatel.be ([149.204.0.178])
          by bemail05.net.alcatel.be (Lotus Domino Release 5.0.11)
          with ESMTP id 2003012502144839:235 ;
          Sat, 25 Jan 2003 02:14:48 +0100 
Message-ID: <3E31E4E8.26E4B810@alcatel.be>
Date: Sat, 25 Jan 2003 02:14:16 +0100
From: Dimitri.Papadimitriou@alcatel.be
Organization: Optical Network Architecture (NTA - Antwerpen)
X-Mailer: Mozilla 4.79 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: Zhi-Wei Lin <zwlin@lucent.com>, iesg@ietf.org, ietf@ietf.org,
        Adrian Farrel <afarrel@movaz.com>,
        Stephen Trowbridge <sjtrowbridge@lucent.com>,
        David Charlap <David.Charlap@marconi.com>, Loa Andersson <loa@pi.se>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
References: <OF229E5757.06459FA0-ON80256CB8.00595A72-80256CB8.005AC945@radianz.com>
X-MIMETrack: Itemize by SMTP Server on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 01/25/2003 02:14:49,
	Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 01/25/2003 02:14:51,
	Serialize complete at 01/25/2003 02:14:51
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

jerry, all,

very simply i would imho recommend that involved 
parties (re-)consider your proposal "Would it be 
worthwhile to somehow 'package' the needed ASON 
extensions into a proposed GMPLS upgrade and 
presented to CCAMP as such?" this is the only
way i can see (today) to achieve a (hopefully)
satisfactory result from both involved sides.

yes, jerry i agree with you it is imho the 
right way to handle this.

thanks,
- dimitri.

"Ash, Gerald R (Jerry), ALABS" wrote:
> 
> Zhi,
> 
> > (e) These documents were never taken seriously (This is the first email I
> > sent: http://ops.ietf.org/lists/ccamp/ccamp.2002/msg00918.html -- but of
> > course no one responded)
> 
> Reminder, I responded to your email on June 18, very shortly after you posted (my email to you is attached below).  That I did this off the list was probably a mistake.   We (you, your co-authors, Adrian and I) then had a prolonged exchange of emails about the draft.  Adrian sent you extensive comments on the draft highlighting concerns, suggesting text, and pointing out nits. That you have a reasonably long list of acknowledgements and contributors suggests that the draft was not ignored.
> 
> As I commented in the attached email to you, "Would it be worthwhile to somehow 'package' the needed ASON extensions into a proposed GMPLS upgrade and presented to CCAMP as such?"  I still maintain that this would be the correct way to handle this: bring the requirements to CCAMP as a requirements draft, thrash them out, and get the necessary extensions adopted in CCAMP.  Rather, the ITU has developed protocol extensions for GMPLS, something outside the charter of the ITU I believe.
> 
> Jerry
> 
> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALASO
> Sent: Tuesday, June 18, 2002 12:58 PM
> To: 'Zhi-Wei Lin'
> Cc: Ash, Gerald R (Jerry), ALASO; 'Adrian Farrel'
> Subject: RE: new draft: GMPLS for ASON
> 
> Hi Zhi,
> 
> > I've uploaded a new draft covering the GMPLS usage and extensions to
> > support the ASON requirements. This document proposes appropriate
> > extensions towards the resolution of additional requirements identified
> > and communicated by the ITU-T in support of ITU's ASON standardization
> > effort, and only provides the extensions for RSVP-TE signaling. Among
> > the major extensions include support for the concept of "call", as well
> > as support for setting up soft permanent connections.
> >
> > http://www.ietf.org/internet-drafts/draft-lin-ccamp-gmpls-ason-rsvpte-00.txt
> 
> Looks good.
> 
> I've attached some excerpts below from the (unpublished) IETF-54/CCAMP meeting minutes.  These also identify crankback, restart, etc. as 'gaps' needing to be filled.  I guess most of these are being worked on, including restart and crankback http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-03.txt (Adrian is currently providing a significant extension for the 04 version of the crankback draft).
> 
> Would it be worthwhile to somehow 'package' the needed ASON extensions into a proposed GMPLS upgrade and presented to CCAMP as such?
> 
> Your comments/suggestions are appreciated.
> 
> Thanks,
> Regards,
> Jerry
> 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> Steve Trowbridge
> 
> Outlined a variety of "gaps" in the current work:
>   - Call and connection separation
>   - Additional error codes/value
>   - Restart mechanisms
>   - Support for crankback
>   - Support for soft permanent connection
> 
> See proceedings for details.
> 
> Eric Mannie: Referring to slide "Identified Gaps".  Gaps seem to be
> very small.  Most of the points are solved, can be easily solved, or
> are in the process of being solved.
> 
> Trowbridge: This was a preliminary scan.  Further review, might turn up
> more issues.  Technologies are similar, so lets identify and minimize
> gaps.
> 
> Dimitri: ITU requirements precede much of IETF work.  Preliminary
> discussions indicate that the current gaps are covered by existing
> protocol work.  Areas where additional work will be required are
> probably minimal, but need to be looked at.  IETF may gain final
> improvements by looking at ITU work.
> 
> Yong Xue: ITU is working on v2 ASON document so more things could turn
> up as "gaps".  Further communication between ITU and IETF should
> continue.
> 
> Trowbridge: Technology will evolve within both organizations.  Should
> expend effort to make sure that they evolve together.
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> % Osama Aboul-Magd -- draft-aboulmagd-ccamp-call-conn-separation-00.txt.
> 
> Draft addresses one of the issues that Tolbridge highlighted in his
> talk - call and connection control separation.
> 
> Kireeti: There is an explicit statement from ITU requiring this.
> There is nothing in the charter about this.  This is good stuff.  Ron
> and I will go through a charter revision with Ads and discuss putting
> this in the charter.  Also need to address other gaps that were raised
> by ITU.
> 
> Scott: When you propose to add something to WG, it would be helpful to
> state where it fits in the existing charter OR how and why charter
> should be extended.
> 
> Eva: I think that it fits into the character as a requirement to the
> signaling protocols.
> 
> Scott: OK - that is a good clean explanation that might save chairs
> some time.
> 
> Yong: I second Eva's comment.
> 
> Kireeti: Need to figure out how to address other issues as well.
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
> _______________________________________________
> 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.

-- 
Papadimitriou Dimitri 
E-mail : dimitri.papadimitriou@alcatel.be 
Private: http://www.rc.bel.alcatel.be/~papadimd/index.html
E-mail : dpapadimitriou@psg.com
Public : http://psg.com/~dpapadimitriou/
Address: Fr. Wellesplein 1, B-2018 Antwerpen, Belgium
Phone  : Work: +32 3 2408491 - Home: +32 2 3434361





From owner-ietf@ietf.org  Mon Jan 27 09:53:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16722;
	Mon, 27 Jan 2003 09:53:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dAaJ-0008Ka-00
	for ietf-list@ran.ietf.org; Mon, 27 Jan 2003 09:50:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18cCgZ-0003fT-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 17:52:31 -0500
Received: from hoemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04592;
	Fri, 24 Jan 2003 17:45:40 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0OMn7x24469;
	Fri, 24 Jan 2003 17:49:07 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ269S9G>; Fri, 24 Jan 2003 23:49:02 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE8E1@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Yakov Rekhter <yakov@juniper.net>,
        "Wijnen, Bert (Bert)"
	 <bwijnen@lucent.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, iesg@ietf.org,
        ietf@ietf.org, Stephen Trowbridge <sjtrowbridge@lucent.com>,
        David Charlap <David.Charlap@marconi.com>, Loa Andersson <loa@pi.se>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational 
Date: Fri, 24 Jan 2003 23:47:32 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

Yakov... good to see that you read all my postings ;-)

I think you are taking a few things out of context here.
When I was speaking up in the TE-WG, I was speaking up 
because I feel that the WGs under my responsibility would
work MUCH better if we can motivate as many people as
possible to actually read and comment on documents in the
WG. And when new work needs to get done in an IETF WG,
then I feel that we need to have many people to be willing
to contribute (at least read and comment).

I feel that we would also want that when we do an IETF
Last Call for work that originates in the IETF, that is
when we do an IETF Last Call for a document that comes
out of a WG. And in fact, for many IETF originated work
(even out of WGs), very few IETF Last Calls do generate
a lot of feedback. I will admit that in most cases, all of
us on the IESG would want to have lots more comment, also
positive comment in the form "I read it and it is good"
or some of the other forms I posted to the TE-WG mailing 
list.

When we need consensus from the IETF for code point 
assignments in a IANA controlled registry, and when we
need those for work that has been standardized (or is
being standardized elsewhere), so in this case in OIF 
and ITU-T, then I do not see that we really need to
have a lot of positive feedback from the IETF community.
In my view, what we are looking for is to find out if
the other organisation (or person) is not violating
the protocols such that it hurts or does harm.

In fact, several of the things that the drafts under
discussion request assignment for are things that most
of us in the IETF decided we did not want to work on.
ANd part of that was that many IETF-ers did not like
the approach, part of it was that we felt it was not
our competence or the area that we felt needed to be
addressed. So we send those people away, and they
found other places to do their work. 

We still do not have to like it.
But I do not see why we need to block code point assignments
as long as their work does not harm/hurt our own use of
the protocols in which they ask for code points.

Hope this helps and explains.
Bert 

Thanks,
Bert 

> -----Original Message-----
> From: Yakov Rekhter [mailto:yakov@juniper.net]
> Sent: vrijdag 24 januari 2003 16:36
> To: Wijnen, Bert (Bert)
> Cc: Ash, Gerald R (Jerry), ALABS; iesg@ietf.org; 
> ietf@ietf.org; Stephen
> Trowbridge; David Charlap; Loa Andersson
> Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational 
> 
> 
> Bert,
> 
> [clipped...]
> 
> > Two points:
> > - the extensions to LDP were found to be in space that requires
> >   IETF Consensus, and so Scott and I asked for an IETF Last Call
> >   on the document. That is an explicit OPEN process
> 
> Quoting from the e-mail you sent recently:
> 
>   If not enough people (and 10 is the absolute minumum, but 
> having seen
>   the attendence of TWEG sessions, I'd expect 25 or more) can speak up
>   to state one of:
>   
>    - I read it and I am positive, it is good stuff
>    - I read it and I see no problems or objections
>    - I read it but I cannot determine if it is bad, but I can see that
>      what has been discussed in the WG is indeed in the document
>    - I read it and I have these nits/objections...
>    - I did not read it cause this is not relevant to my xxx 
> job/work/function
>    - I did not read it cause I think this is nonsense 
>   
>   Then I get the feeling that we're just allowing a small group of
>   people push their petty-project through the process. That seems NOT
>   good to me. We need serious WG participation in reading and 
> commenting
>   in one of these forums above, before we can declare that we have WG
>   consensus on a document to be presented to IESG for approval as RFC
>   (in whatever form).
> 
> Since (as you said) the extensions required IETF consensus, and
> with the above in mind could you please share with the rest of
> us the information on how many people spoke up about the draft
> to state one of:
> 
>    - I read it and I am positive, it is good stuff
>    - I read it and I see no problems or objections
>    - I read it but I cannot determine if it is bad, but I can see that
>      what has been discussed in the WG is indeed in the document
>    - I read it and I have these nits/objections...
>    - I did not read it cause this is not relevant to my xxx 
> job/work/function
>    - I did not read it cause I think this is nonsense
> 
> Yakov.
> 





From owner-ietf@ietf.org  Mon Jan 27 09:53:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16718;
	Mon, 27 Jan 2003 09:53:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dAXL-0008FD-00
	for ietf-list@ran.ietf.org; Mon, 27 Jan 2003 09:46:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18c5Sf-0000j6-00
	for ietf@ran.ietf.org; Fri, 24 Jan 2003 10:09:41 -0500
Received: from hoemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21820;
	Fri, 24 Jan 2003 10:02:55 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0OF6Me08220;
	Fri, 24 Jan 2003 10:06:22 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ269NCY>; Fri, 24 Jan 2003 16:06:20 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE869@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Scott  Bradner <sob@harvard.edu>, ewgray@graiymage.com,
        Valdis.Kletnieks@vt.edu
Cc: iesg@ietf.org, ietf@ietf.org
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational
Date: Fri, 24 Jan 2003 16:06:12 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

By the way, the author (Aboulmagd) has in the meantime
informed the RFC-Editor that the "no derivitive work"
clause can be removed. So this doc now has the same
provisions as the on Bala adn Lin documents.

Thanks,
Bert 

> -----Original Message-----
> From: Scott Bradner [mailto:sob@harvard.edu]
> Sent: vrijdag 24 januari 2003 15:15
> To: ewgray@graiymage.com; Valdis.Kletnieks@vt.edu
> Cc: iesg@ietf.org; ietf@ietf.org
> Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational
> 
> 
> > However, unless
> > I'm severely confused (which is always possible), the 
> prohibition against
> > derivative works came from the ITU side of the fence,
> 
> the prohibition is more not used all that often - two main cases where
> is is
> 	1/ vendor work publish for the information of the community
> 	2/ republishing a standard from another SDO 
> 
> just like we would not want the ITU "fixing" an IETF standard w/o our
> input it seems a reasonable desire to not have the IETF "fix" an ITU
> (or ETSI etc) standard w/o their involvement
> 
> Scott
> 





From owner-ietf@ietf.org  Mon Jan 27 13:05:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21257;
	Mon, 27 Jan 2003 13:05:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dDc2-00069u-00
	for ietf-list@ran.ietf.org; Mon, 27 Jan 2003 13:04:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dDbg-00068R-00
	for ietf@ran.ietf.org; Mon, 27 Jan 2003 13:03:40 -0500
Received: from smtp02.mrf.mail.rcn.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20946
	for <ietf@ietf.org>; Mon, 27 Jan 2003 12:56:09 -0500 (EST)
Received: from 208-58-89-66.c3-0.crm-ubr2.crm.ny.cable.rcn.com ([208.58.89.66] helo=talisman.cable.rcn.com)
	by smtp02.mrf.mail.rcn.net with esmtp (Exim 3.35 #4)
	id 18dDXn-000732-00; Mon, 27 Jan 2003 12:59:39 -0500
Received: (from prasad@localhost)
	by talisman.cable.rcn.com (8.11.6/8.11.6) id h0RHxRj05786;
	Mon, 27 Jan 2003 12:59:27 -0500
Date: Mon, 27 Jan 2003 12:59:27 -0500
From: V Guruprasad <vg96@columbia.edu>
To: deering@cisco.com
Cc: ietf@ietf.org
Subject: The original NSAP variable length addresses
Message-ID: <20030127175927.GA5475@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk



On 25 Apr 2000, you'd written:

> One interesting example:  OSI NSAP addresses are variable length, with a
> theoretical limit of 255 bytes I believe (perhaps there's an escape
> mechanism to grow them longer?).  There was an "implementors'
> agreement" to limit the maximum length in actual use to 20 bytes "for now",
> to make implementations practical.  Two things happened:
> 
>         (1) Almost all of the addressing plans designed for NSAPAs
>             produced addresses that were *exactly* 20 bytes long, in
>             some cases inserting padding in the middle of the address
>             to fill it out to 20 bytes!  I suspect that was done to
>             make the address allocation job easier, e.g., making
>             sure delegation boundaries fell on byte boundaries.
> 
>         (2) Many of the implementations ended up with the 20-byte limit
>             wired into them, such that the use of addresses longer than
>             20 bytes would have required updating most of the installed
>             base (the changes being of a similar nature to those required
>             to modify an IPv4 application or protocol to support IPv6).


I'd like to cite this in my thesis, and am looking for a published
reference that states the reduction.

My search to date has turned up documents, like the ATM UNI, that spec
only the 20 byte max length. Maybe I'm not looking in the right places...

Could you or anyone else possibly give me a pointer?? I'd be greatly obliged.


thanks,
-prasad.
-------------------
V. Guruprasad,
Inspired Research LLC.
http://www.columbia.edu/~vg96/papers.




From owner-ietf@ietf.org  Mon Jan 27 16:22:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27249;
	Mon, 27 Jan 2003 16:22:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dGic-0007yO-00
	for ietf-list@ran.ietf.org; Mon, 27 Jan 2003 16:23:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dFvd-0004pR-00
	for ietf@ran.ietf.org; Mon, 27 Jan 2003 15:32:25 -0500
Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25544
	for <ietf@ietf.org>; Mon, 27 Jan 2003 15:24:54 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 27 Jan 2003 12:28:22 -0800
X-Originating-IP: [203.124.140.20]
From: "Bruce" <bruce_reid202@hotmail.com>
To: <ietf@ietf.org>
Subject: queries:draft-aboulmagd-ccamp-crldp-ason-ext-02.txt
Date: Tue, 28 Jan 2003 02:05:58 +0530
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Message-ID: <OE45EqxGGmNN79xavjr0000063c@hotmail.com>
X-OriginalArrivalTime: 27 Jan 2003 20:28:22.0951 (UTC) FILETIME=[A34A9370:01C2C642]
Sender: owner-ietf@ietf.org
Precedence: bulk

hello,


http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.
txt



what is:

1: defination of a call (SIP WG exists in ietf, but this query is specific
to a "PCM"  person's area.......)
2: if its a generalised protocol limited to TLV based specs,  why is it
limited to CRLDP?
3. elaborating point 2, if one doesnt have a standard for signalling
protocol as of date, how does the signalling protocol even matter to the
this draft except for conflicts in number space...why cant one realise the
basic algorithm proposed in the draft



-B






From owner-ietf@ietf.org  Mon Jan 27 16:22:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27248;
	Mon, 27 Jan 2003 16:22:53 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dGic-0007yU-00
	for ietf-list@ran.ietf.org; Mon, 27 Jan 2003 16:23:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dGFB-0005iv-00
	for ietf@ran.ietf.org; Mon, 27 Jan 2003 15:52:37 -0500
Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26004
	for <ietf@ietf.org>; Mon, 27 Jan 2003 15:45:05 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 27 Jan 2003 12:48:34 -0800
X-Originating-IP: [203.124.140.20]
From: "Bruce" <bruce_reid202@hotmail.com>
To: <ietf@ietf.org>
Subject: Re: queries:draft-aboulmagd-ccamp-crldp-ason-ext-02.txt
Date: Tue, 28 Jan 2003 02:26:10 +0530
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Message-ID: <OE59XuU8wntY3rA6Kco000031ea@hotmail.com>
X-OriginalArrivalTime: 27 Jan 2003 20:48:34.0485 (UTC) FILETIME=[756BFE50:01C2C645]
Sender: owner-ietf@ietf.org
Precedence: bulk

to add to this:

does the following mentioned in the draft....seem to make sense to anyone
placing an ISD call somewhere:::

International Segment (IS):
        To be coded according to ITU-T recommendation T.50. The
        International Segment (IS) field provides a 3 character ISO
        3166 Geographic/Political Country Code. The country code is
        based on the three-character uppercase alphabetic ISO 3166
        Country Code (e.g., USA, FRA)..


        The National Segment (NS) field consists of two sub-fields: the
        ITU Carrier Code followed by a Unique Access Point Code. The
        ITU Carrier Code is a code assigned to a network
        operator/service provider, maintained by the ITU-T
        Telecommunication Service Bureau in association with
        Recommendation M.1400. This code shall consist of 1-6 left-
        justified characters, alphabetic, or leading alphabetic with
        trailing numeric. The unique access point code is a matter for
        the organization to which the country code and ITU carrier code
        have been assigned, provided that uniqueness is guaranteed.
        This code shall consist of 6-11 characters, with trailing NULL,
        completing the 12-character National Segment



are these parameters to be ignored? is ietf planning to redefine these
parameters? and their values?


to the writers:
why is all this being mentioned under an "ASON" draft?? why not under a
signalling draft?

and the TLV and point 3 below still holds...





----- Original Message -----
From: Bruce <bruce_reid202@hotmail.com>
To: <ietf@ietf.org>
Sent: Tuesday, January 28, 2003 2:05 AM
Subject: queries:draft-aboulmagd-ccamp-crldp-ason-ext-02.txt


> hello,
>
>
>
http://www.ietf.org/internet-drafts/draft-aboulmagd-ccamp-crldp-ason-ext-02.
> txt
>
>
>
> what is:
>
> 1: defination of a call (SIP WG exists in ietf, but this query is specific
> to a "PCM"  person's area.......)
> 2: if its a generalised protocol limited to TLV based specs,  why is it
> limited to CRLDP?
> 3. elaborating point 2, if one doesnt have a standard for signalling
> protocol as of date, how does the signalling protocol even matter to the
> this draft except for conflicts in number space...why cant one realise the
> basic algorithm proposed in the draft
>
>
>
> -B
>
>






From owner-ietf@ietf.org  Tue Jan 28 08:15:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25186;
	Tue, 28 Jan 2003 08:15:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dVa1-0001h8-00
	for ietf-list@ran.ietf.org; Tue, 28 Jan 2003 08:15:09 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dVX2-0001QO-00
	for ietf@ran.ietf.org; Tue, 28 Jan 2003 08:12:04 -0500
Received: from lightwave.chromisys.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24619;
	Tue, 28 Jan 2003 08:04:18 -0500 (EST)
Received: by lightwave.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <4GJZ17HG>; Tue, 28 Jan 2003 05:07:44 -0800
Message-ID: <9D42C6E086250248810DCADA39CE7EFC97219F@nimbus>
From: John Drake <jdrake@calient.net>
To: "'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>,
        Yakov Rekhter
	 <yakov@juniper.net>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, iesg@ietf.org,
        ietf@ietf.org, Stephen Trowbridge <sjtrowbridge@lucent.com>,
        David Charlap <David.Charlap@marconi.com>, Loa Andersson <loa@pi.se>
Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational 
Date: Tue, 28 Jan 2003 05:07:43 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk


> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> Sent: Friday, January 24, 2003 2:48 PM
> To: Yakov Rekhter; Wijnen, Bert (Bert)
> Cc: Ash, Gerald R (Jerry), ALABS; iesg@ietf.org; 
> ietf@ietf.org; Stephen
> Trowbridge; David Charlap; Loa Andersson
> Subject: RE: Last Call: CR-LDP Extensions for ASON to Informational 
> 
> 
> Yakov... good to see that you read all my postings ;-)
> 
> I think you are taking a few things out of context here.
> When I was speaking up in the TE-WG, I was speaking up 
> because I feel that the WGs under my responsibility would
> work MUCH better if we can motivate as many people as
> possible to actually read and comment on documents in the
> WG. And when new work needs to get done in an IETF WG,
> then I feel that we need to have many people to be willing
> to contribute (at least read and comment).
> 
> I feel that we would also want that when we do an IETF
> Last Call for work that originates in the IETF, that is
> when we do an IETF Last Call for a document that comes
> out of a WG. And in fact, for many IETF originated work
> (even out of WGs), very few IETF Last Calls do generate
> a lot of feedback. I will admit that in most cases, all of
> us on the IESG would want to have lots more comment, also
> positive comment in the form "I read it and it is good"
> or some of the other forms I posted to the TE-WG mailing 
> list.
> 
> When we need consensus from the IETF for code point 
> assignments in a IANA controlled registry, and when we
> need those for work that has been standardized (or is
> being standardized elsewhere), so in this case in OIF 
> and ITU-T, then I do not see that we really need to
> have a lot of positive feedback from the IETF community.
> In my view, what we are looking for is to find out if
> the other organisation (or person) is not violating
> the protocols such that it hurts or does harm.


JD:  Given that these documents don't go through a working
group last call, why is an absence of positive feedback a
an unnecessary (or bad) thing?  What is the mechanism to ensure
that a given document doesn't hurt or harm?


> 
> In fact, several of the things that the drafts under
> discussion request assignment for are things that most
> of us in the IETF decided we did not want to work on.
> ANd part of that was that many IETF-ers did not like
> the approach, part of it was that we felt it was not
> our competence or the area that we felt needed to be
> addressed. So we send those people away, and they
> found other places to do their work. 


JD:  Okay, I guess that's your story and you're sticking to it.  However,
that's not the impression I get from the Yokohama CCAMP minutes: 

"Minute takers were volunteered (Josh Broch and Eric Gray) 

Snipped...

Osama Aboul-Magd presented status on his draft on ASON extensions to CR-LDP.

He asked if the WG would accept this as a WG draft. 

Kireeti pointed out that there is a meta discussion on the issue of
progressing both CR-LDP and RSVP-TE in the MPLS working group tomorrow and
suggested that the discussion should be taken to the mailing list after that
has been addressed. 

Snipped...

Dimitri Papadimitriou discussed work on ASON extensions to RSVP-TE. He asked
if the WG believes this to be valuable work and should eventually be put
forward to the ITU. 

Kireeti talked about the need to work out the relationship with the ITU on
these issues. 

Choy asked why the work does nt include call/connection information. 

Kireeti said that the functional specification should first capture the
solution independent requirements. 

Stephen Trowbridge asked what further information the IETF requires. 

Dimitri and Kireeti answered the question in detail."


> 
> We still do not have to like it.
> But I do not see why we need to block code point assignments
> as long as their work does not harm/hurt our own use of
> the protocols in which they ask for code points.


JD:  There are still unanswered technical issues.


> 
> Hope this helps and explains.
> Bert 
> 
> Thanks,
> Bert 
> 
> > -----Original Message-----
> > From: Yakov Rekhter [mailto:yakov@juniper.net]
> > Sent: vrijdag 24 januari 2003 16:36
> > To: Wijnen, Bert (Bert)
> > Cc: Ash, Gerald R (Jerry), ALABS; iesg@ietf.org; 
> > ietf@ietf.org; Stephen
> > Trowbridge; David Charlap; Loa Andersson
> > Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational 
> > 
> > 
> > Bert,
> > 
> > [clipped...]
> > 
> > > Two points:
> > > - the extensions to LDP were found to be in space that requires
> > >   IETF Consensus, and so Scott and I asked for an IETF Last Call
> > >   on the document. That is an explicit OPEN process
> > 
> > Quoting from the e-mail you sent recently:
> > 
> >   If not enough people (and 10 is the absolute minumum, but 
> > having seen
> >   the attendence of TWEG sessions, I'd expect 25 or more) 
> can speak up
> >   to state one of:
> >   
> >    - I read it and I am positive, it is good stuff
> >    - I read it and I see no problems or objections
> >    - I read it but I cannot determine if it is bad, but I 
> can see that
> >      what has been discussed in the WG is indeed in the document
> >    - I read it and I have these nits/objections...
> >    - I did not read it cause this is not relevant to my xxx 
> > job/work/function
> >    - I did not read it cause I think this is nonsense 
> >   
> >   Then I get the feeling that we're just allowing a small group of
> >   people push their petty-project through the process. That 
> seems NOT
> >   good to me. We need serious WG participation in reading and 
> > commenting
> >   in one of these forums above, before we can declare that 
> we have WG
> >   consensus on a document to be presented to IESG for 
> approval as RFC
> >   (in whatever form).
> > 
> > Since (as you said) the extensions required IETF consensus, and
> > with the above in mind could you please share with the rest of
> > us the information on how many people spoke up about the draft
> > to state one of:
> > 
> >    - I read it and I am positive, it is good stuff
> >    - I read it and I see no problems or objections
> >    - I read it but I cannot determine if it is bad, but I 
> can see that
> >      what has been discussed in the WG is indeed in the document
> >    - I read it and I have these nits/objections...
> >    - I did not read it cause this is not relevant to my xxx 
> > job/work/function
> >    - I did not read it cause I think this is nonsense
> > 
> > Yakov.
> > 
> 
> 
> 



From owner-ietf@ietf.org  Tue Jan 28 09:48:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26865;
	Tue, 28 Jan 2003 09:48:19 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dX0z-0008Ey-00
	for ietf-list@ran.ietf.org; Tue, 28 Jan 2003 09:47:05 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dWQ3-00060S-00
	for ietf@ran.ietf.org; Tue, 28 Jan 2003 09:08:55 -0500
Received: from maild.telia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26018;
	Tue, 28 Jan 2003 09:01:09 -0500 (EST)
Received: from d1o888.telia.com (d1o888.telia.com [213.67.172.241])
	by maild.telia.com (8.12.5/8.12.5) with ESMTP id h0SE4Wgm027474;
	Tue, 28 Jan 2003 15:04:32 +0100 (CET)
X-Original-Recipient: iesg@ietf.org
Received: from post.utfors.se (h70n2fls31o888.telia.com [213.64.120.70])
	by d1o888.telia.com (8.10.2/8.10.1) with ESMTP id h0SE4V218826;
	Tue, 28 Jan 2003 15:04:31 +0100 (CET)
Message-ID: <3E368D3E.2080704@post.utfors.se>
Date: Tue, 28 Jan 2003 15:01:34 +0100
From: Loa Andersson <loa@post.utfors.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020605
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Loa Andersson <loa@pi.se>, "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>,
        iesg@ietf.org, ietf@ietf.org,
        David Charlap <David.Charlap@marconi.com>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        Scott Bradner
 <sob@harvard.edu>, gash@att.com,
        Stephen Trowbridge
 <sjtrowbridge@lucent.com>
Subject: Re: Last Call: CR-LDP Extensions for ASON to Informational]
References: <3E31ACD3.3010401@pi.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

   Steve,

it appears to me that you decribes a situation that many of us we are 
very familiar
with, most of us have sent -00.txt IDs to working groups, and have been 
met by a
complete lack of interest.
In retrospect I have to say that most of the time the wg was right - bad 
idea.

To bring work into the working group(s) you have to generate interest 
and discussion,
lack of interest signifies end of the road.

What you say is that you had (have) very little interest for the work 
you proposed,
so under normal circumstances this would just have been dropped. Given 
current
circumstances - with a great deal of interest elsewhere this came back 
again and
again and we now even have the IESG taken a decision to approve work 
(that require
IETF consensus) on very shaky grounds.

For my part that is history! But it seems to me that putting the blame 
on the ietf
when one fail to create interest for a work is self-defeating.

What we need to do now is looking in to to things
- how codepoints for the (G)MPLS namespace are allocated and make 
certain that we
  have a   "uniform" approach to this and common guidelines for the 
whole namespace
- how wi handle requirements on extensions/changes in the protocols 
specified for
  (G)MPLS and come up with a process that guarantee that IETF acts 
correctly and
  timely when other organizations request such changes/extensions, but 
also that
  the IETF is in control of what is happening to the (G)MPLS and that 
such a process
  is accepted and used by parties asking for extensions/changes.

I sincerly hope to get your support for such a process, I'm working on a
-00.txt version and would hate to get into a "no response" siutation ;)

/Loa

>
> Jerry,
> Lets be clear on the timeline and what you consider to be "recent".
> - The ASON requirements were communicated October 2001 -
>   request for help from ccamp (no response)
> - Analysis of ASON requirements against GMPLS protocols, identifying 
> gaps,
>   completed Febrary 2002 - request ccamp to help close gaps (no response)
> - Proposals into ITU-T agreed about how to close gaps communicated May 
> 2002,
>   with request now to align the GMPLS documents with ITU-T work 
> (again, no
>   response)
> - Final request for comments, October 2002, (again no response)
>
>








From owner-ietf@ietf.org  Wed Jan 29 06:32:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16242;
	Wed, 29 Jan 2003 06:32:24 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dqJ3-00078e-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 06:23:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dqIG-00077F-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 06:22:12 -0500
Received: from ratree.psu.ac.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15938
	for <ietf@ietf.org>; Wed, 29 Jan 2003 06:14:14 -0500 (EST)
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 h0TBGQ027424;
	Wed, 29 Jan 2003 18:16:29 +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 h0TBDSV07858;
	Wed, 29 Jan 2003 18:13:28 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: ietf@ietf.org, Glenn Parsons <gparsons@nortelnetworks.com>,
        Eric Burger <eburger@snowshore.com>
Subject: Re: WG Review: Enhancements to Internet email to support diverse service environments (lemonade) 
In-Reply-To: <200301282312.SAA11118@ietf.org> 
References: <200301282312.SAA11118@ietf.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 29 Jan 2003 18:13:27 +0700
Message-ID: <7856.1043838807@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Tue, 28 Jan 2003 18:12:05 -0500
    From:        Jacqueline Hargest <jhargest@ietf.org>
    Message-ID:  <200301282312.SAA11118@ietf.org>

  | A new IETF working group has been proposed in the Applications Area. 
[...]
  | Enhancements to Internet email to support diverse service environments
  | (lemonade)

  | 1.  An informational RFC will be produced on LEMONADE requiremens.

Fine.

  | 2.  Enhance the existing IMAP4 message retrieval protocol to satisfy
  |     the requirements for streaming playback of multimedia content.

What a horrid idea?   How do "streaming playback" and "message retrieval"
possibly fit together at all?   Is this yet another attempt to pervert
a protocol into meeting some other quite unrelated need, for the sole
purpose of getting through firewalls or similar?   Drop this nonsense.

  | 3.  Enhance the exsiting IMAP4 message retrieval protocol to facilitate
  |     its use with devices that have limited capabilities such as mobile
  |     endpoints.

Fine.

  | 3.  Create a message notification protocol for the specific purpose of
  |     servers reporting message status information to other servers.

A second #3 ...   This one looks more like a proposal for a solution,
than a work item.   If the solution is already known, a WG isn't needed,
just publish it.   Otherwise, indicate what problem needs to be solved,
for which this might be one solution, and see what alternatives are
offered.

  | 4.  Create a specification describing the use of Internet message
  |     services in environments where message delivery may take place
  |     using either Internet protocols or external protocols such as SMS.

Fine.

kre




From owner-ietf@ietf.org  Wed Jan 29 10:03:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20856;
	Wed, 29 Jan 2003 10:03:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dtfe-0002Ir-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 09:58:34 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dpB7-0004vC-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 05:10:45 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14583
	for <ietf@ietf.org>; Wed, 29 Jan 2003 05:02:51 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id E61C9622B1
	for <ietf@ietf.org>; Wed, 29 Jan 2003 11:06:19 +0100 (CET)
Date: Wed, 29 Jan 2003 09:43:10 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Re: Problem-statement (Re: Last Call: CR-LDP Extensions for ASON to
 Informational)
Message-ID: <746187020.1043833390@localhost>
In-Reply-To: <260010000.1043436609@askvoll.hjemme.alvestrand.no>
References: <68912DAE-2FC2-11D7-A11A-00039357A82A@extremenetworks.com>
 <Pine.GSO.4.50.0301241815190.27937-100000@artemis.ee.surrey.ac.uk>
 <260010000.1043436609@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/3.0.0 (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

and I forgot....
the archives are at
http://eikenes.alvestrand.no/pipermail/problem-statement/

--On 24. januar 2003 20:30 +0100 Harald Tveit Alvestrand 
<harald@alvestrand.no> wrote:

> problem-statement@alvestrand.no - use the "-request" convention to
> subscribe.
>
> This list was set up in conjunction with the IESG plenary in Atlanta, and
> has been used to continue the discussion from there. A working group
> charter is being discussed.
>
>                 Harald
>







From owner-ietf@ietf.org  Wed Jan 29 13:42:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25744;
	Wed, 29 Jan 2003 13:42:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dxCm-0001SR-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 13:45:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dxCQ-0001Re-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 13:44:38 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25598;
	Wed, 29 Jan 2003 13:36:37 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18dx84-000PaQ-00; Wed, 29 Jan 2003 13:40:08 -0500
Date: Wed, 29 Jan 2003 13:40:08 -0500
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org, iesg@ietf.org
Subject: Re: WG Review: Enhancements to Internet email to support
 diverse 	   service environments (lemonade)
Message-ID: <169878963.1043847608@p3.JCK.COM>
In-Reply-To: <200301282312.SAA11118@ietf.org>
References:  <200301282312.SAA11118@ietf.org>
X-Mailer: Mulberry/3.0.0 (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 Tuesday, 28 January, 2003 18:12 -0500 Jacqueline Hargest 
<jhargest@ietf.org> wrote:

> A new IETF working group has been proposed in the Applications
> Area.  The IESG has not made any determination as yet.
>
> The following description was submitted, and is provided for
> informational purposes only.
>
>
> Enhancements to Internet email to support diverse service
> environments (lemonade)
> --------------------------------------------------------------
> ----
>
> Current Status: Proposed Working Group
>
> Description of Working Group:
>
> Lemonade brings together a body of work related to Internet
> messaging, in particular work done by the VPIM, FAX, IMAPEXT<
> and other IETF working groups. The goal is to provide a set of
> enhancements and profiles of Internet email submission,
> transport, and retrieval protocols to facilitate operation in
> environments which use Internet-based technologies but which
> have link characteristics, device characteristics, or service
> environments that are significantly different from those
> common on the Internet.  A primary goal of this work is to
> ensure that those profiles and enhancements continue to
> interoperate with the existing Internet email protocols in use
> on the Internet, so that these environments and more
> traditional Internet users have access to a seamless service.
>...

Hi.

I'm finding this proposal deeply troubling and have been 
wondering whether to speak up.  Kre's note convinced me that I 
should.

There is a rather fundamental architectural question underlying 
this proposal.  The proposed charter assumes a particular answer 
to that question.  I believe that the community has reviewed the 
general question on a number of occasions and that it has 
usually come to the opposite answer.  It would be good, I think, 
to address that architectural question seriously in this case 
and to be sure that the solution-set proposed is the one we 
want.  And I don't think that can be done by a WG, or proto-WG, 
that is anxious to charge ahead on a particular path: I think it 
has to be an IAB or IESG task, or one delegated by them and 
responsible to them.

Details:  It has long been the conventional wisdom in the 
community that protocols that are low-complexity and that have 
few options will generally deploy more rapidly and widely, 
interwork better, and cause fewer problems than protocols that 
are highly complex in operation or that have very extensive or 
complex combinations of options and variations.  We have 
believed that principle strongly enough to include it explicitly 
in a number of Standard-level protocol documents (e.g., see the 
introduction to STD10/RFC1869), so there is reason to assume 
community consensus about it.   It has also been the 
conventional wisdom, backed by considerable bad experience, that 
adding functionality that is not obviously relevant to a 
protocol, simply because that protocol is there and available, 
is not a good idea.

It is widely believed that IMAP is already too complex, that it 
has too many options and variations, and that those factors have 
contributed to a shortage of implementations.  While it is hard 
to quantify that belief in protocol terms, it has often been 
observed that there are many implementations of POP3 servers 
that are suitable for use on home or small business servers. 
While there are a number of IMAP implementations that are 
suitable for enterprise use, with multiple server complexes and 
dedicated and/or expert support staff, estimates of the number 
of conforming servers suitable for SOHO situations and with any 
conforming client range between zero and one.  That is not a 
good situation, and there have been discussions within the IETF 
about starting "IMAP lite" efforts.

Now we have a WG proposal which seems to have a major theme of 
adding more capabilities and options to IMAP, including some 
capabilities (like streaming) that are not obviously connected 
with IMAP's core purpose or definition.  Architecturally, there 
are many other options for accomodating those capabilities, 
including designing a multi-protocol framework that would permit 
specialized protocols for streaming to interwork well with IMAP 
but without adding significant complexity or options to IMAP 
itself.  I am not sure whether one of those approaches would be 
better than proposals for additional IMAP capabilities.  But I 
believe that we should address those possibilities --and the 
costs of add more bulk and complexity to IMAP-- in a serious way 
before launching a WG to figure out how to put these things into 
IMAP.

As part of that effort, I think we should make a definite 
decision about the "IMAP Lite" discussions. If we want, or need, 
to move in that direction, than "IMAP-even-bigger" is not 
rational; if "IMAP Lite" would be a good idea (or is necessary 
to get serious deployment), then a proposal like this one is 
nearly incomprehensible.

     john




From owner-ietf@ietf.org  Wed Jan 29 13:47:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25969;
	Wed, 29 Jan 2003 13:47:59 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dxJY-0001rN-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 13:52:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dxHO-0001VL-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 13:49:46 -0500
Received: from episteme-software.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25694
	for <ietf@ietf.org>; Wed, 29 Jan 2003 13:41:44 -0500 (EST)
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server 3.2b4);
 Wed, 29 Jan 2003 12:45:12 -0600
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p0600010cba5dc6d587ee@[216.43.25.67]>
In-Reply-To: <7856.1043838807@munnari.OZ.AU>
References: <200301282312.SAA11118@ietf.org>
 <7856.1043838807@munnari.OZ.AU>
X-Mailer: Eudora [Macintosh version 6.0a1]
Date: Wed, 29 Jan 2003 12:45:12 -0600
To: Robert Elz <kre@munnari.oz.au>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: WG Review: Enhancements to Internet email to support diverse
 service environments (lemonade)
Cc: ietf@ietf.org, Glenn Parsons <gparsons@nortelnetworks.com>,
        Eric Burger <eburger@snowshore.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

On 1/29/03 at 6:13 PM +0700, Robert Elz wrote:

>>A new IETF working group has been proposed in the Applications Area.
>[...]
>>Enhancements to Internet email to support diverse service 
>>environments (lemonade)
>[...]
>>2.  Enhance the existing IMAP4 message retrieval protocol to 
>>satisfy the requirements for streaming playback of multimedia 
>>content.
>
>What a horrid idea?   How do "streaming playback" and "message 
>retrieval" possibly fit together at all?   Is this yet another 
>attempt to pervert a protocol into meeting some other quite 
>unrelated need, for the sole purpose of getting through firewalls or 
>similar?

No, that's not what this means. Actually, it's probably just the 
opposite of what you fear. For example, let's say you have some data 
in a message store which is a nice long hunk of sound. Instead of 
using IMAP to download the entire sound in order to play it, it might 
be much more intelligent to use an RTSP client to receive the data 
and play it directly. The envisioned mechanism would make it possible 
for the client to ask the server, "Can I get this back via RTSP, and 
if so, where do I connect up?" and the server can tell the client how 
to retrieve it.

>>3.  Create a message notification protocol for the specific purpose 
>>of servers reporting message status information to other servers.
>
>A second #3 ...

A typo.

>This one looks more like a proposal for a solution, than a work 
>item. If the solution is already known, a WG isn't needed, just 
>publish it. Otherwise, indicate what problem needs to be solved, for 
>which this might be one solution, and see what alternatives are 
>offered.

The solution is not known. The problem is that there is currently no 
standard mechanism for mail servers to announce the existence of new 
mail. Current protocols rely on polling or a constant connection to 
the mail server. The work item is to come up with a protocol that 
does notifications. Does the above not describe that work item 
appropriately?

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



From owner-ietf@ietf.org  Wed Jan 29 14:30:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27272;
	Wed, 29 Jan 2003 14:30:59 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dxyI-0004HW-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 14:34:06 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dxxK-0004F9-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 14:33:06 -0500
Received: from episteme-software.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27102;
	Wed, 29 Jan 2003 14:25:04 -0500 (EST)
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server 3.2b4);
 Wed, 29 Jan 2003 13:28:32 -0600
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p0600010dba5dd6b34009@[216.43.25.67]>
In-Reply-To: <169878963.1043847608@p3.JCK.COM>
References: <200301282312.SAA11118@ietf.org>
 <169878963.1043847608@p3.JCK.COM>
X-Mailer: Eudora [Macintosh version 6.0a1]
Date: Wed, 29 Jan 2003 13:28:32 -0600
To: John C Klensin <john-ietf@jck.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: WG Review: Enhancements to Internet email to support diverse
 service environments (lemonade)
Cc: ietf@ietf.org, iesg@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

On 1/29/03 at 1:40 PM -0500, John C Klensin wrote:

>Now we have a WG proposal which seems to have a major theme of 
>adding more capabilities and options to IMAP

Before everyone ends up latching onto this: You quite conveniently 
ignore something very important in the first statement of purpose in 
the charter: "The goal is to provide a set of enhancements AND 
PROFILES" (my emphasis). One of the major themes, at least in my 
mind, is to profile down IMAP for the purposes of these more limited 
environments. Yes, it is certainly true that there are a couple of 
extensions to IMAP being proposed, and I don't doubt that they should 
be met with scrutiny. (More on this in my earlier response to kre and 
below.) But I think the more important thing for this group to do is 
to find a way to avoid much of the huge complexity IMAP. One of the 
sources of this complexity is that there are so many optional 
extensions to IMAP that are implemented to such varying degrees by 
servers (and with such huge impacts on functionality) that no client 
has any reasonable chance of interoperating without being terribly 
complex. One of the primary outcomes of this working group should be 
a profile of IMAP that is devoid of options, that removes features 
who's primary purpose is to support particular implementations 
choices at the expense of interoperability, and gives folks in 
low-capability environments a chance to produce a decent 
implementation.

If this is what you mean by "IMAP Lite", I would contend that this is 
the architectural choice that this particular proposed WG has made.

>including some capabilities (like streaming) that are not obviously 
>connected with IMAP's core purpose or definition.  Architecturally, 
>there are many other options for accomodating those capabilities, 
>including designing a multi-protocol framework that would permit 
>specialized protocols for streaming to interwork well with IMAP but 
>without adding significant complexity or options to IMAP itself.

If I understand you correctly, at least one of the proposals on the 
table (CHANNEL) does exactly this kind of thing: Instead of providing 
some sort of specialized streaming in IMAP, it instead introduces a 
referral mechanism, where a client can ask the server for a referral 
to a different protocol to stream the data. Whether this is a good 
idea or not can be debated, but this particular item is not an 
example of bloating IMAP with wild new features.

I think there should be a great deal of pressure on this group to 
*not* bloat IMAP, and in fact rather to shrink it. However, there is 
nothing in the proposed charter (or in the mind of this particular 
member of that proposed WG) that should give you the impression that 
the intention is otherwise.

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



From owner-ietf@ietf.org  Wed Jan 29 15:09:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28346;
	Wed, 29 Jan 2003 15:09:50 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dyY0-0006L9-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 15:11:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dyXu-0006Jn-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 15:10:54 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28062;
	Wed, 29 Jan 2003 15:02:51 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18dyTW-000Pjs-00; Wed, 29 Jan 2003 15:06:22 -0500
Date: Wed, 29 Jan 2003 15:06:22 -0500
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qualcomm.com>
cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: WG Review: Enhancements to Internet email to support
 diverse service environments (lemonade)
Message-ID: <175052472.1043852782@p3.JCK.COM>
In-Reply-To: <p0600010dba5dd6b34009@[216.43.25.67]>
References: <200301282312.SAA11118@ietf.org>
 <169878963.1043847608@p3.JCK.COM>
 <p0600010dba5dd6b34009@[216.43.25.67]>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Wednesday, 29 January, 2003 13:28 -0600 Pete Resnick 
<presnick@qualcomm.com> wrote:

> On 1/29/03 at 1:40 PM -0500, John C Klensin wrote:
>
>> Now we have a WG proposal which seems to have a major theme
>> of  adding more capabilities and options to IMAP
>
> Before everyone ends up latching onto this: You quite
> conveniently ignore something very important in the first
> statement of purpose in the charter: "The goal is to provide a
> set of enhancements AND PROFILES" (my emphasis). One of the
> major themes, at least in my mind, is to profile down IMAP for
> the purposes of these more limited environments.
>...

But, Pete, for reasons you presumably understand, "profiles" 
(note plural) gives me as much anxiety as "lets add lots more 
excrement to this protocol".  Granted that it would be harder to 
make a complete mess of a mail-retrieval protocol than of a 
transport one, but "we will develop a minimal profile for this 
specific/ limited environment" and then "we will develop a 
minimal profile for that other specific/ limited environment" 
are the traditional signposts along the route to profiles that 
don't interoperate and a need to reply to email by picking up 
the phone.

> Yes, it is
> certainly true that there are a couple of extensions to IMAP
> being proposed, and I don't doubt that they should be met with
> scrutiny. (More on this in my earlier response to kre and
> below.)

One of them is potentially very heavyweight.  As you point out, 
there are other solutions to it, but the charter doesn't appear 
to prevent the WG from inventing some wildly new, and complex, 
way to handle the issue.    If it has already been decided that 
the WG won't go down that path, then the charter should say so. 
If it has been agreed that the WG isn't going to do that unless 
it turns out to be absolutely necessary, then the decision point 
about "absolutely necessary", and another opportunity for 
community review if it is determined to be necessary, should be 
reflected in the milestones.

> But I think the more important thing for this group to
> do is to find a way to avoid much of the huge complexity IMAP.
> One of the sources of this complexity is that there are so
> many optional extensions to IMAP that are implemented to such
> varying degrees by servers (and with such huge impacts on
> functionality) that no client has any reasonable chance of
> interoperating without being terribly complex. One of the
> primary outcomes of this working group should be a profile of
> IMAP that is devoid of options, that removes features who's
> primary purpose is to support particular implementations
> choices at the expense of interoperability, and gives folks in
> low-capability environments a chance to produce a decent
> implementation.

Well, we agree, but it is hard to figure that out from the draft 
charter.

> If this is what you mean by "IMAP Lite", I would contend that
> this is the architectural choice that this particular proposed
> WG has made.

See below.

>> including some capabilities (like streaming) that are not
>> obviously  connected with IMAP's core purpose or definition.
>> Architecturally,  there are many other options for
>> accomodating those capabilities,  including designing a
>> multi-protocol framework that would permit  specialized
>> protocols for streaming to interwork well with IMAP but
>> without adding significant complexity or options to IMAP
>> itself.
>
> If I understand you correctly, at least one of the proposals
> on the table (CHANNEL) does exactly this kind of thing:
> Instead of providing some sort of specialized streaming in
> IMAP, it instead introduces a referral mechanism, where a
> client can ask the server for a referral to a different
> protocol to stream the data. Whether this is a good idea or
> not can be debated, but this particular item is not an example
> of bloating IMAP with wild new features.

As the charter is written, it could be, even if it is your 
intent to avoid that particular path.

> I think there should be a great deal of pressure on this group
> to *not* bloat IMAP, and in fact rather to shrink it. However,
> there is nothing in the proposed charter (or in the mind of
> this particular member of that proposed WG) that should give
> you the impression that the intention is otherwise.

Pete, my difficulty here is that there has been a lot of 
discussion the community in the last few months about basic IETF 
problems.  Two of the issues that have come up many times 
involve the IESG second-guessing the outputs of WGs and our 
having significant architectural/design issues raised only after 
the WG thinks it is finished.  I think there is general 
agreement that it is very bad situation if a WG goes off and 
produces a piece of work that falls within its charter, only to 
be confronted with arguments during Last Call that the result is 
just too complex and that the WG should be sent back to the 
drawing board.

The charter draft, as written, pretty clearly would permit the 
WG to consider and adopt some strategies that I won't find 
architecturally acceptable and that, I gather, you wouldn't 
either.  If no one intends to go in those directions, let's 
rewrite the charter to make that clear.  If the WG needs to look 
in those directions without expecting to go there, then let's 
put that in the charter, with provision for a plenary discussion 
or an IETF Last Call _before_ the in-depth protocol work has 
been done, so we don't end up with late-breaking "surprise" 
effects.

Finally, if the intent is really to prune, then I'd expect 
pruning to appear prominently in the description.  Instead, both 
the title and the text seem to point mostly to enhancements. 
And, for whatever it is worth, I seem to recall discussions when 
the IMAPEXT WG was chartered that there would be no work on 
major enhancements until/unless there was a "strip it down" 
effort first.  If the plan here were to emit a lighter-weight, 
fewer-options, version of IMAP (one, not a family of profiles) 
and then to start work on streaming and notification, I would be 
much happier than if --by intent or appearance-- the idea is to 
have some profiling emerge from an effort to move IMAP into 
previously untrod ground.

      john




From owner-ietf@ietf.org  Wed Jan 29 15:43:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29301;
	Wed, 29 Jan 2003 15:43:43 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dz5t-0007Sf-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 15:46:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dz51-0007RL-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 15:45:07 -0500
Received: from episteme-software.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29124;
	Wed, 29 Jan 2003 15:37:03 -0500 (EST)
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server 3.2b4);
 Wed, 29 Jan 2003 14:40:32 -0600
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p06000111ba5de5b9c58d@[216.43.25.67]>
In-Reply-To: <175052472.1043852782@p3.JCK.COM>
References: <200301282312.SAA11118@ietf.org>
 <169878963.1043847608@p3.JCK.COM> <p0600010dba5dd6b34009@[216.43.25.67]>
 <175052472.1043852782@p3.JCK.COM>
X-Mailer: Eudora [Macintosh version 6.0a1]
Date: Wed, 29 Jan 2003 14:40:31 -0600
To: John C Klensin <john-ietf@jck.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: WG Review: Enhancements to Internet email to support  diverse
 service environments (lemonade)
Cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

John and I are in a great deal more agreement that I first suspected.

On 1/29/03 at 3:06 PM -0500, John C Klensin wrote:

>But, Pete, for reasons you presumably understand, "profiles" (note 
>plural) gives me as much anxiety as "lets add lots more excrement to 
>this protocol".

Yes, if the result of this WG is multiple different profiles of IMAP, 
I too would consider that a bad thing.

>>Yes, it is certainly true that there are a couple of extensions to 
>>IMAP being proposed, and I don't doubt that they should be met with 
>>scrutiny.
>
>One of them is potentially very heavyweight.  As you point out, 
>there are other solutions to it, but the charter doesn't appear to 
>prevent the WG from inventing some wildly new, and complex, way to 
>handle the issue.    If it has already been decided that the WG 
>won't go down that path, then the charter should say so. If it has 
>been agreed that the WG isn't going to do that unless it turns out 
>to be absolutely necessary, then the decision point about 
>"absolutely necessary", and another opportunity for community review 
>if it is determined to be necessary, should be reflected in the 
>milestones.

I think I agree. I don't know that the solution I referred to is a 
done-deal, so I think spelling out the constraints in the charter is 
important.

In that vein, I want to take back something I said earlier:

>>I think there should be a great deal of pressure on this group to 
>>*not* bloat IMAP, and in fact rather to shrink it. However, there 
>>is nothing in the proposed charter (or in the mind of this 
>>particular member of that proposed WG) that should give you the 
>>impression that the intention is otherwise.

I now see that the charter *as posted* might very well leave that impression.

>The charter draft, as written, pretty clearly would permit the WG to 
>consider and adopt some strategies that I won't find architecturally 
>acceptable and that, I gather, you wouldn't either.

I agree. And unfortunately, I think this is due to a serious problem 
about which I'm quite distressed:

The proposed charter contained in the announcement is *not* the 
proposed charter worked out on the LEMONADE BOF mailing list. Not 
even close. The one on the list went through several revisions to 
include specific language in the work items about profiling of 
existing protocols, and that language has been removed in what was 
posted here. The one on the list was tailored specifically to avoid 
having the working group add to existing protocols (with IMAP as only 
one example) unless absolutely necessary, but rather to profile 
existing protocols if that solved the problem. The present charter 
gives the incorrect impression that the desire of the group is simply 
to add extensions, specifically to IMAP.

First, a process point: If these significant changes were made by the 
IESG to what was submitted, these should have been brought back to 
the list for approval. Though RFC 2418 says that charter review is 
only between the prospective chairs and the IESG, it also says that a 
charter is a contract between the working group and the IETF. As a 
member of this proposed WG, I'd like to know what I'm being asked to 
be involved in. I think it was irresponsible to post this charter 
without buy-in of the folks who are supposed to be working on this.

Second, I think John's concerns are right on the money, and that's 
why I pushed as hard as I did to include the profiling language in 
the work items. If we can solve the problems without extending, 
that's what we should do. If we need extensions to solve a particular 
problem, that better end up being part of a required profile.

>If no one intends to go in those directions, let's rewrite the 
>charter to make that clear.  If the WG needs to look in those 
>directions without expecting to go there, then let's put that in the 
>charter, with provision for a plenary discussion or an IETF Last 
>Call _before_ the in-depth protocol work has been done, so we don't 
>end up with late-breaking "surprise" effects.

Yup. And I think I will join in voicing objection to the charter as written.

>Finally, if the intent is really to prune, then I'd expect pruning 
>to appear prominently in the description.  Instead, both the title 
>and the text seem to point mostly to enhancements.

I want to be careful here: The *intent* of the proposed WG is to fix 
some problems with using the current protocols in particular 
operating environments. To accomplish this, it is my sincere belief 
that pruning current protocols (and more specifically, IMAP) is part 
of the solution. That doesn't mean that "pruning" needs to be in the 
title, though it certainly should appear in the work items. For that 
matter, it doesn't mean that IMAP should really appear at all in the 
charter, as far as I am concerned. The charter that I was part of 
creating didn't mention IMAP in the work items, in my mind because 
the WG should not be required to use IMAP if POP or some other 
existing protocol would do.

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



From owner-ietf@ietf.org  Wed Jan 29 15:51:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29549;
	Wed, 29 Jan 2003 15:51:37 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dzFZ-00082D-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 15:56:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dyM7-0005BE-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 14:58:43 -0500
Received: from MAIL.cynetanetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27781;
	Wed, 29 Jan 2003 14:50:40 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: WG Review: Enhancements to Internet email to support diverse service environments (lemonade)
Date: Wed, 29 Jan 2003 13:54:09 -0600
Message-ID: <9255B6CD76A88943A3062F7D4E6432F543BAAE@mail.cynetanetworks.com>
Thread-Topic: WG Review: Enhancements to Internet email to support diverse service environments (lemonade)
Thread-Index: AcLHzos7aTXaqDVGTgaUG84WK99CngAAJGOw
From: "Spencer Dawkins" <sdawkins@cynetanetworks.com>
To: "Pete Resnick" <presnick@qualcomm.com>
Cc: <ietf@ietf.org>, <iesg@ietf.org>, "John C Klensin" <john-ietf@jck.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA29549

Hi, Pete,

I've been looking at the BOF announcements for LEMONADE previously,
and this wasn't the impression I had, at all. Thank you for clarifying.
The clarification makes it more obvious this may be the right thing to do.

But...

If this proposed working group is, indeed, trimming down IMAP4 (bravo!),
it seems wildly misnamed. The convention seems to be "(x)ext" for working
groups EXTENDING an existing protocol, but what's an obvious name for
a working group PRUNING IMAP4?

"minIMAP4rev1"? "IMAP4rev1minus"?...

Spencer

> -----Original Message-----
> From: Pete Resnick [mailto:presnick@qualcomm.com]
> Sent: Wednesday, January 29, 2003 1:29 PM
> To: John C Klensin
> Cc: ietf@ietf.org; iesg@ietf.org
> Subject: Re: WG Review: Enhancements to Internet email to support
> diverse service environments (lemonade)
> 
> 
> On 1/29/03 at 1:40 PM -0500, John C Klensin wrote:
> 
> >Now we have a WG proposal which seems to have a major theme of 
> >adding more capabilities and options to IMAP
> 
> Before everyone ends up latching onto this: You quite conveniently 
> ignore something very important in the first statement of purpose in 
> the charter: "The goal is to provide a set of enhancements AND 
> PROFILES" (my emphasis). One of the major themes, at least in my 
> mind, is to profile down IMAP for the purposes of these more limited 
> environments. Yes, it is certainly true that there are a couple of 
> extensions to IMAP being proposed, and I don't doubt that they should 
> be met with scrutiny. (More on this in my earlier response to kre and 
> below.) But I think the more important thing for this group to do is 
> to find a way to avoid much of the huge complexity IMAP. One of the 
> sources of this complexity is that there are so many optional 
> extensions to IMAP that are implemented to such varying degrees by 
> servers (and with such huge impacts on functionality) that no client 
> has any reasonable chance of interoperating without being terribly 
> complex. One of the primary outcomes of this working group should be 
> a profile of IMAP that is devoid of options, that removes features 
> who's primary purpose is to support particular implementations 
> choices at the expense of interoperability, and gives folks in 
> low-capability environments a chance to produce a decent 
> implementation.
> 
> If this is what you mean by "IMAP Lite", I would contend that this is 
> the architectural choice that this particular proposed WG has made.
> 
> I think there should be a great deal of pressure on this group to 
> *not* bloat IMAP, and in fact rather to shrink it. However, there is 
> nothing in the proposed charter (or in the mind of this particular 
> member of that proposed WG) that should give you the impression that 
> the intention is otherwise.
 





From owner-ietf@ietf.org  Wed Jan 29 16:20:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00203;
	Wed, 29 Jan 2003 16:20:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18dzej-0000ce-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 16:22:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18dzdr-0000at-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 16:21:07 -0500
Received: from mauve.mrochek.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00057;
	Wed, 29 Jan 2003 16:13:02 -0500 (EST)
From: ned.freed@mrochek.com
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01KRSZYL6PGG002DEU@mauve.mrochek.com>; Wed,
 29 Jan 2003 13:16:32 -0800 (PST)
Date: Wed, 29 Jan 2003 13:06:39 -0800 (PST)
Subject: Re: WG Review: Enhancements to Internet email to support  diverse
 service environments (lemonade)
In-reply-to: "Your message dated Wed, 29 Jan 2003 14:40:31 -0600"
 <p06000111ba5de5b9c58d@[216.43.25.67]>
To: Pete Resnick <presnick@qualcomm.com>
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org" <ietf@ietf.org>,
        "iesg@ietf.org" <iesg@ietf.org>
Message-id: <01KRT49TEUKI002DEU@mauve.mrochek.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_UVevbSQno9NfSOlfUmv3MA)"
References: <200301282312.SAA11118@ietf.org> <169878963.1043847608@p3.JCK.COM>
 <p0600010dba5dd6b34009@[216.43.25.67]> <175052472.1043852782@p3.JCK.COM>
 <p06000111ba5de5b9c58d@[216.43.25.67]>
Sender: owner-ietf@ietf.org
Precedence: bulk


--Boundary_(ID_UVevbSQno9NfSOlfUmv3MA)
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Content-Transfer-Encoding: 7BIT

> I agree. And unfortunately, I think this is due to a serious problem
> about which I'm quite distressed:

> The proposed charter contained in the announcement is *not* the
> proposed charter worked out on the LEMONADE BOF mailing list. Not
> even close. The one on the list went through several revisions to
> include specific language in the work items about profiling of
> existing protocols, and that language has been removed in what was
> posted here. The one on the list was tailored specifically to avoid
> having the working group add to existing protocols (with IMAP as only
> one example) unless absolutely necessary, but rather to profile
> existing protocols if that solved the problem. The present charter
> gives the incorrect impression that the desire of the group is simply
> to add extensions, specifically to IMAP.

Well, as it happens the charter that was posted to ietf-announce wasn't
the one the IESG approved either. It is one from quite a few versions
back.

I've attached the current charter below.

> First, a process point: If these significant changes were made by the
> IESG to what was submitted, these should have been brought back to
> the list for approval.

I regard this as being up to the chair of the group. The charter that
wasn't posted was iterated on by both the chairs and the IESG.

				Ned

--Boundary_(ID_UVevbSQno9NfSOlfUmv3MA)
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Content-Transfer-Encoding: 7BIT

Enhancements to Internet email to support diverse service environments
(lemonade)

Proposed Charter
================

Lemonade is tasked to provide a set of enhancements and profiles of Internet
email submission, transport, and retrieval protocols to facilitate operation in
environments which use Internet-based technologies but which have link
characteristics, device characteristics, or service environments that are
significantly different from those common on the Internet.  A primary goal of
this work is to ensure that those profiles and enhancements continue to
interoperate with the existing Internet email protocols in use on the Internet,
so that these environments and more traditional Internet users have access to a
seamless service.

Lemonade's work is at the crossroads of a body of work related to Internet 
messaging, in particular work done by the VPIM, FAX, IMAPEXT and other IETF 
working groups.  Given the potentially broad scope of activities this group
could engage in, the group will focus specifically on the following work items:

     0.  An informational RFC will be produced on LEMONADE requirements.

     1.  Enhance the existing IMAP4 message retrieval protocol to satisfy the
         requirements for streaming playback of multimedia content. 
         
     2.  Enhance the exsiting IMAP4 message retrieval protocol to facilitate
         its use with devices that have limited capabilities such as mobile
         endpoints. The existing standards-track CONNEG framework will be used
         if content negotiation capabilities are needed.

     3.  Create a message notification protocol for the specific purpose of
         servers reporting message status information to other servers.

     4.  Create a specification describing the use of Internet message
         services in environments where message delivery may take place using
         either Internet protocols or through an MMS server using
         WAP to communicate with the receiving user agent.

Any protocols defined by this working group will include appopriate security
mechanisms, including authentication, privacy, and access control.
Mandatory-to-implement security mechanisms will be specified as needed in order
to guarantee secure protocol interoperability.

The transport area will be consulted to deal with any transport-related
issues that arise, especially in regards to items 1-4 above.
             
The working group is aware of several related activities in other groups:

  - 3GPP TSG T WG2 SWG3 Messaging  <http://www.3gpp.org/TB/T/T2/T2.htm>
  - W3C Mulitmodal interaction Activity <http://www.w3.org/2002/mmi/>
  - Open Mobile Alliance <http://www.openmobilealliance.org/>
  - 3GPP2 TSG-P <http://3gpp2.org/Public_html/P/index.cfm>
  - 3GPP2 TSG-N <http://3gpp2.org/Public_html/N/index.cfm>

The goal is to coordinate efforts with at least these groups as required.

While there is obvious synergy, given the end-of-life of the VPIM and FAX work
groups and the similar membership, the working group does not expect to
coordinate with these other groups.


Milestones  (document completion)
==========

Feb 2003 - LEMONADE Requirements

May 2003 - Server to server notification protocol

Jul 2003 - IMAP4 extensions for VM playback

Sep 2003 - IMAP4 extensions for mobile devices

Jan 2004 - Translation to and from other messaging systems


Drafts to be used as input for working group
deliverables (grouped per milestone)
====================================

   LEMONADE requirements

     - draft-vaudreuil-um-issues-00.txt
     - draft-burger-um-reqts-00.txt
     - draft-wong-umcli-00.txt

   Server to server notification protocol

     - draft-shapira-snap-04.txt

   IMAP4 extensions for VM playback

     - draft-burger-imap-chanuse-00.txt
     - draft-nerenberg-imap-channel-01.txt

   IMAP4 extensions for mobile devices

     - draft-neystadt-imap-status-counters-00.txt
     - draft-shveidel-mediasize-00.txt

   Translation to and from other messaging systems

     - draft-vaudreuil-futuredelivery-00.txt


--Boundary_(ID_UVevbSQno9NfSOlfUmv3MA)--



From owner-ietf@ietf.org  Wed Jan 29 16:46:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01007;
	Wed, 29 Jan 2003 16:46:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18e04r-0001i2-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 16:49:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18e04X-0001gU-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 16:48:41 -0500
Received: from mtiwmhc11.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00922
	for <ietf@ietf.org>; Wed, 29 Jan 2003 16:40:38 -0500 (EST)
From: dja2001@att.net
Received: from mtiwebc18 ([204.127.135.57]) by mtiwmhc11.worldnet.att.net
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with SMTP
          id <20030129214411.SQOG5675.mtiwmhc11.worldnet.att.net@mtiwebc18>
          for <ietf@ietf.org>; Wed, 29 Jan 2003 21:44:11 +0000
Received: from [66.92.168.196] by mtiwebc18;
	Wed, 29 Jan 2003 21:44:10 +0000
To: ietf@ietf.org
Subject: RE: WG Review: Enhancements to Internet email to support diverse service environments (lemonade)
Date: Wed, 29 Jan 2003 21:44:10 +0000
X-Mailer: AT&T Message Center Version 1 (Nov 25 2002)
X-Authenticated-Sender: ZGphMjAwMUBhdHQubmV0
Message-Id: <20030129214411.SQOG5675.mtiwmhc11.worldnet.att.net@mtiwebc18>
Sender: owner-ietf@ietf.org
Precedence: bulk

"Spencer Dawkins" <sdawkins@cynetanetworks.com> writes:

> what's an obvious name for a working group PRUNING IMAP4?
> 
> "minIMAP4rev1"? "IMAP4rev1minus"?...

MAPLET -- Message Access Protocol Limited to Efficient Tasks?

-- 
David J. Aronson, Software Engineer for hire in Washington DC area.
See http://dja2001.home.att.net for online resume, references, etc.



From owner-ietf@ietf.org  Wed Jan 29 17:02:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01771;
	Wed, 29 Jan 2003 17:02:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18e0LJ-0002iv-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 17:06:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18e0LF-0002hP-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 17:05:57 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01482;
	Wed, 29 Jan 2003 16:57:52 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18e0Gm-000Puo-00; Wed, 29 Jan 2003 17:01:20 -0500
Date: Wed, 29 Jan 2003 17:01:19 -0500
From: John C Klensin <john-ietf@jck.com>
To: "ned.freed@mrochek.com" <ned.freed@mrochek.com>,
        Pete Resnick <presnick@qualcomm.com>
cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: WG Review: Enhancements to Internet email to support
  diverse service environments (lemonade)
Message-ID: <181950110.1043859679@p3.JCK.COM>
In-Reply-To: <01KRT49TEUKI002DEU@mauve.mrochek.com>
References: <200301282312.SAA11118@ietf.org>
 <169878963.1043847608@p3.JCK.COM>
 <p0600010dba5dd6b34009@[216.43.25.67]>
 <175052472.1043852782@p3.JCK.COM>
 <p06000111ba5de5b9c58d@[216.43.25.67]>
 <01KRT49TEUKI002DEU@mauve.mrochek.com>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Wednesday, 29 January, 2003 13:06 -0800 
"ned.freed@mrochek.com" <ned.freed@mrochek.com> wrote:

>> I agree. And unfortunately, I think this is due to a serious
>> problem about which I'm quite distressed:
>
>> The proposed charter contained in the announcement is *not*
>> the proposed charter worked out on the LEMONADE BOF mailing
>> list. Not even close. The one on the list went through
>> several revisions to include specific language in the work
>> items about profiling of existing protocols, and that
>> language has been removed in what was posted here. The one on
>> the list was tailored specifically to avoid having the
>> working group add to existing protocols (with IMAP as only
>> one example) unless absolutely necessary, but rather to
>> profile existing protocols if that solved the problem. The
>> present charter gives the incorrect impression that the
>> desire of the group is simply to add extensions, specifically
>> to IMAP.
>
> Well, as it happens the charter that was posted to
> ietf-announce wasn't the one the IESG approved either. It is
> one from quite a few versions back.
>
> I've attached the current charter below.

Ned, this one is _lots_ better.  I'll leave sorting out how the 
wrong version got posted to the IESG and the Secretariat.  But 
my primary concern (and one of those on which Pete and I are 
apparently in agreement) remains:  when I read "enhance...IMAP", 
I don't infer "narrow the protocol for use in this environment" 
or "specify a way to use the existing protocol to accomodate 
these needs".  Instead, I infer "new feature", "new capability", 
and "putting more stuff into the protocol".  I think there is 
considerable resistance in the community to making IMAP bigger 
-- while the four messages that have shown up on the list are 
not much of a sample, I observe that at least three of them have 
included "make it smaller, not larger" positions.

If the community believes all that has been said in Atlanta and 
on the "problem-statement" list about raising architectural 
issues early in the life of a WG rather than hitting the WG 
during Last Call (and you can be assured that several of us will 
scream loudly if this WG emits large extensions to IMAP without 
really clear justification), then charter-time is the time to 
fix this one.  If the intent that all of us have is the same 
--which I suspect to be the case-- then all that is needed is to 
fix text to make that intent clear to the community and to WG 
members who have not participated in the previous discussions. 
That should be helpful for the Chair(s), for the ADs and for the 
community.

>> First, a process point: If these significant changes were
>> made by the IESG to what was submitted, these should have
>> been brought back to the list for approval.
>
> I regard this as being up to the chair of the group. The
> charter that wasn't posted was iterated on by both the chairs
> and the IESG.

Then this is an objection to the textual form of the charter 
version you posted as well as to the form the Secretariat 
posted.  If the "extend IMAP" issues are settled, then let's get 
that fact  documented in the charter to prevent later surprises 
and unpleasantness.   If they are not, then let's either

	* Hold a review of those issues by some body whose
	responsibility is to the Internet, and Internet mail,
	infrastructure is taken broadly, not just accomodating a
	few new capabilities.  Have that review before the WG is
	initiated, and make its conclusions binding on the WG.
	
	* Provide, in the charter, a community review point at
	the initiation of significant extension work on IMAP or
	anything else(were such work to be initiated), so that
	we don't get a pushback situation well into the 11th
	hour.

regards,
    john




From owner-ietf@ietf.org  Wed Jan 29 20:46:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05414;
	Wed, 29 Jan 2003 20:46:09 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18e3lQ-0001NU-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 20:45:12 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18e3he-0001K3-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 20:41:18 -0500
Received: from cichlid.adsl.duke.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05270;
	Wed, 29 Jan 2003 20:33:12 -0500 (EST)
Received: from cichlid.adsl.duke.edu (narten@localhost)
	by cichlid.adsl.duke.edu (8.11.6/8.9.3) with ESMTP id h0U1KQo02850;
	Wed, 29 Jan 2003 20:20:27 -0500
Message-Id: <200301300120.h0U1KQo02850@cichlid.adsl.duke.edu>
To: RJ Atkinson <rja@extremenetworks.com>
cc: Bob Braden <braden@ISI.EDU>, ietf@ietf.org, kireeti@juniper.net,
        iesg@ietf.org
Subject: "IETF consensus"  in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ]
In-Reply-To: Message from rja@extremenetworks.com
   of "Fri, 24 Jan 2003 12:36:45 EST." <68912DAE-2FC2-11D7-A11A-00039357A82A@extremenetworks.com> 
Date: Wed, 29 Jan 2003 20:20:26 -0500
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

RJ Atkinson <rja@extremenetworks.com> writes:

> On Thursday, Jan 23, 2003, at 17:54 America/Montreal, Bob Braden wrote:
> > I interpret "IETF consensus" as meaning that at least a Last
> > Call was conducted.  To use any other interpretation seems to me to
> > be dishonest.  I guess I am agreeing with Kireeti.

> [IAB hat off]

> I agree with the above.  IESG approval is not identical to IETF
> consensus.  If it were, the IETF community would not be giving such
> vocal feedback about concerns with the IESG at the last 2 meetings
> and on the ietf-problems mailing list, IMHO.

As one of the authors of RFC 2434 "Guidelines for Writing an IANA
Considerations Section in RFCs", I have long regretted defining the term
"IETF Consensus" as it is in that document. 2434 says:

>       IETF Consensus - New values are assigned through the IETF
>            consensus process. Specifically, new assignments are made via
>            RFCs approved by the IESG. Typically, the IESG will seek
>            input on prospective assignments from appropriate persons
>            (e.g., a relevant Working Group if one exists).
> 
>            Examples: SMTP extensions [SMTP-EXT], BGP Subsequent Address
>            Family Identifiers [BGP4-EXT].

The intent of the above wording was to provide a way for documents to
request that IANA only assign code points when there exists a document
that gets published as an RFC. The wording above specifically does not
say "Standards Track" RFC and was intented to include informational
and experimental documents, whether from a WG or not. There is an
alternate definition - "Standards Action" - that can be cited if IANA
assignments are only to be made for Standards Track documents.

I think intent of the above definition is fine. But naming the term
"IETF Consensus" is obviously problematical and confusing, as there
are many Info and Experimental RFCs for which there is nothing close
to IETF consensus on, and no one would claim so.

So, let's be clear that in the context of most of the discussion on
this thread, folks seem to be applying their own definition of what
"IETF Consensus" means when in fact the 2434 definition is what should
be used, as is cited in the relevant IANA considerations section.

I don't know what can be done a this point to change the terminology
in 2434. It's been in use for some 4 years now...

I'm reminded of another great choice of terms, the Best Current
Practice, where we have had numerous threads about whether something
was actually "best" or a "currently practice". There too, the actual
definition as defined in the RFC is not quite the same as the what the
literal term might suggest.

Thomas



From owner-ietf@ietf.org  Wed Jan 29 20:51:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05497;
	Wed, 29 Jan 2003 20:51:33 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18e3vt-0001xH-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 20:56:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18e3v4-0001pX-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 20:55:10 -0500
Received: from mtiwmhc13.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05448
	for <ietf@ietf.org>; Wed, 29 Jan 2003 20:47:05 -0500 (EST)
From: dja2001@att.net
Message-Id: <200301300147.UAA05448@ietf.org>
Received: from mtiwebc16 (mtiwebc16.worldnet.att.net[204.127.135.42])
          by mtiwmhc13.worldnet.att.net (mtiwmhc13) with SMTP
          id <2003013001503611300g5vs1e>; Thu, 30 Jan 2003 01:50:36 +0000
Received: from [66.92.168.196] by mtiwebc16;
	Thu, 30 Jan 2003 01:50:35 +0000
To: ietf@ietf.org
Subject: RE: WG Review: Enhancements to Internet email to support diverse service environments (lemonade)
Date: Thu, 30 Jan 2003 01:50:35 +0000
X-Mailer: AT&T Message Center Version 1 (Nov 25 2002)
X-Authenticated-Sender: ZGphMjAwMUBhdHQubmV0
Sender: owner-ietf@ietf.org
Precedence: bulk

"Spencer Dawkins" <sdawkins@cynetanetworks.com> wrote:

> David, you're a genius!

Thanks.  Can I use you for a reference?  B-)  (See signature.)

> Glenn Parson told me he was VERY proud of the LEMONADE acronymn,

Yes, and now that I've gone and looked up what it is and all that (hey, I was 
away from IETF stuff for a long time, and VPIM/IVM even longer), I too am 
impressed.  Well done, Glenn!  That sure beats my Tonnage Overhead Reduction 
Protocol with Enhanced Depth Options, from back when this list was much 
chattier (and sillier) than it seems to be now.

See y'all on the UM list, which I just joined.

--
David J. Aronson, Software Engineer for hire in Washington DC area.
See http://dja2001.home.att.net for online resume, references, etc.



From owner-ietf@ietf.org  Wed Jan 29 21:13:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05826;
	Wed, 29 Jan 2003 21:13:59 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18e4HC-00033x-00
	for ietf-list@ran.ietf.org; Wed, 29 Jan 2003 21:18:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18e4GU-000322-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 21:17:18 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05764;
	Wed, 29 Jan 2003 21:09:11 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18e4Bw-0000Js-00; Wed, 29 Jan 2003 21:12:36 -0500
Date: Wed, 29 Jan 2003 21:12:36 -0500
From: John C Klensin <john-ietf@jck.com>
To: Thomas Narten <narten@us.ibm.com>, RJ Atkinson <rja@extremenetworks.com>
cc: Bob Braden <braden@ISI.EDU>, "ietf@ietf.org" <ietf@ietf.org>,
        "kireeti@juniper.net" <kireeti@juniper.net>,
        "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: "IETF consensus"  in IANA considerations [was Re:
 Last Call: CR-LDP Extensions for ASON to Informational ]
Message-ID: <197026338.1043874756@p3.JCK.COM>
In-Reply-To: <200301300120.h0U1KQo02850@cichlid.adsl.duke.edu>
References:  <200301300120.h0U1KQo02850@cichlid.adsl.duke.edu>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Wednesday, 29 January, 2003 20:20 -0500 Thomas Narten 
<narten@us.ibm.com> wrote:

>...
> As one of the authors of RFC 2434 "Guidelines for Writing an
> IANA Considerations Section in RFCs", I have long regretted
> defining the term "IETF Consensus" as it is in that document.
> 2434 says:
>
>>       IETF Consensus - New values are assigned through the
>>       IETF consensus process. Specifically, new assignments
>>            are made via RFCs approved by the IESG. Typically,
>>            the IESG will seek input on prospective
>>            assignments from appropriate persons (e.g., a
>>            relevant Working Group if one exists).
>>
>>            Examples: SMTP extensions [SMTP-EXT], BGP
>>            Subsequent Address Family Identifiers [BGP4-EXT].
>
> The intent of the above wording was to provide a way for
> documents to request that IANA only assign code points when
> there exists a document that gets published as an RFC. The
> wording above specifically does not say "Standards Track" RFC
> and was intented to include informational and experimental
> documents, whether from a WG or not. There is an alternate
> definition - "Standards Action" - that can be cited if IANA
> assignments are only to be made for Standards Track documents.
>
> I think intent of the above definition is fine. But naming the
> term "IETF Consensus" is obviously problematical and
> confusing, as there are many Info and Experimental RFCs for
> which there is nothing close to IETF consensus on, and no one
> would claim so.

Thomas, not to be splitting hairs, but the intent --at least in 
SMTP-EXT (STD10/RFC1869), which was cited as an example-- was 
somewhat more than simple publication as an RFC (or, in your 
words, "a document that gets published as an RFC").  While, 
clearly, "standards track" was not intended, we did intend that 
the IESG make a formal decision that the request was consistent 
with community consensus (as well as having a published 
document).  We didn't specify what steps the IESG would go 
through in reaching that conclusion, but, other than the 2026 
requirement for a Last Call for standards-track documents, 
nothing else does either.  The simple ability to convince the 
RFC Editor to publish an informational or experimental document 
was not intended to be sufficient, even with IESG agreement that 
the document wasn't likely to be severely harmful.

> So, let's be clear that in the context of most of the
> discussion on this thread, folks seem to be applying their own
> definition of what "IETF Consensus" means when in fact the
> 2434 definition is what should be used, as is cited in the
> relevant IANA considerations section.
>
> I don't know what can be done a this point to change the
> terminology in 2434. It's been in use for some 4 years now...

I don't see that there is a problem.  Especially to the extent 
that you can argue that 2434 modifies or clarifies the 
procedures that 1869 calls for, I can imagine nothing that would 
prevent revising and reissuing 2434 if you think clarification 
is needed.  Or, if it were preferred, one could modify the I-D 
IESG procedures document to "update" 2434 and specify exactly 
what the IESG does in those situations going forward.

IMnvHO, ambiguous procedures documents that confuse the readers 
and the community, and that then encourage or require IESG to 
make ad hoc decisions about how to interpret them, get us into 
far more trouble than issuing RFC-quality clarifications or 
replacements.  Even when the older documents have been around 
much longer than four years.

regards,
   john




From owner-ietf@ietf.org  Thu Jan 30 09:50:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00087;
	Thu, 30 Jan 2003 09:50:29 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eFz1-0007fU-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 09:48:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eFrO-0007Ch-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 09:40:10 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29574;
	Thu, 30 Jan 2003 09:31:56 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by gnat.inet.org (Postfix) with ESMTP
	id ABBF667103; Thu, 30 Jan 2003 09:44:19 -0500 (EST)
Date: Thu, 30 Jan 2003 09:35:26 -0500
Subject: Re: "IETF consensus"  in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: Bob Braden <braden@ISI.EDU>, ietf@ietf.org, kireeti@juniper.net,
        iesg@ietf.org
To: Thomas Narten <narten@us.ibm.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200301300120.h0U1KQo02850@cichlid.adsl.duke.edu>
Message-Id: <1261B871-3460-11D7-AE59-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Wednesday, Jan 29, 2003, at 20:20 America/Montreal, Thomas Narten 
wrote:
> I don't know what can be done a this point to change the terminology
> in 2434. It's been in use for some 4 years now...

It would seem quite simple for you to take the text of RFC-2434,
edit the text appropriately to pick a more clear and accurate
term, then run it past the community for BCP.

If you think that process is too heavyweight to fix this, then that
would be an existence-proof that even IESG members believe the IETF
processes have become too cumbersome.

Please do fix.

Ran
rja@extremenetworks.com




From owner-ietf@ietf.org  Thu Jan 30 10:08:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00550;
	Thu, 30 Jan 2003 10:08:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eGLP-0001Hs-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 10:11:11 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18e0Zo-0003XN-00
	for ietf@ran.ietf.org; Wed, 29 Jan 2003 17:21:00 -0500
Received: from MAIL.cynetanetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02087
	for <ietf@ietf.org>; Wed, 29 Jan 2003 17:12:58 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: WG Review: Enhancements to Internet email to support diverse service environments (lemonade)
Date: Wed, 29 Jan 2003 16:16:28 -0600
Message-ID: <9255B6CD76A88943A3062F7D4E6432F543BAB1@mail.cynetanetworks.com>
Thread-Topic: WG Review: Enhancements to Internet email to support diverse service environments (lemonade)
Thread-Index: AcLH4ZaKuD6JgVL1QM6yHd8+bafQ+AAAeK4Q
From: "Spencer Dawkins" <sdawkins@cynetanetworks.com>
To: <dja2001@att.net>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA00550

David, you're a genius!

Glenn Parson told me he was VERY proud of the LEMONADE acronymn, 
so we probably need something more clever than MinIMAP...

Spencer

... and I like dropping the "I", because there's no such thing
as NON-Internet Messaging. This morning, I snail-mailed a personal
recommendation to a VERY low-tech office - but they're on the
Internet, and I e-mailed the recommendation this afternoon ...

> -----Original Message-----
> From: dja2001@att.net [mailto:dja2001@att.net]
> 
> 
> "Spencer Dawkins" <sdawkins@cynetanetworks.com> writes:
> 
> > what's an obvious name for a working group PRUNING IMAP4?
> > 
> > "minIMAP4rev1"? "IMAP4rev1minus"?...
> 
> MAPLET -- Message Access Protocol Limited to Efficient Tasks? 





From owner-ietf@ietf.org  Thu Jan 30 10:27:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01008;
	Thu, 30 Jan 2003 10:27:09 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eGdg-0005cW-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 10:30:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eGd7-0005Y5-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 10:29:29 -0500
Received: from e32.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00844
	for <ietf@ietf.org>; Thu, 30 Jan 2003 10:21:14 -0500 (EST)
Received: from westrelay01.boulder.ibm.com (westrelay01.boulder.ibm.com [9.17.194.22])
	by e32.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id h0UFOkU8012480;
	Thu, 30 Jan 2003 10:24:46 -0500
Received: from cichlid.adsl.duke.edu (sig-9-65-216-210.mts.ibm.com [9.65.216.210])
	by westrelay01.boulder.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id h0UFOic1076034;
	Thu, 30 Jan 2003 08:24:44 -0700
Received: from cichlid.adsl.duke.edu (narten@localhost)
	by cichlid.adsl.duke.edu (8.11.6/8.9.3) with ESMTP id h0UFMiT02380;
	Thu, 30 Jan 2003 10:22:44 -0500
Message-Id: <200301301522.h0UFMiT02380@cichlid.adsl.duke.edu>
To: RJ Atkinson <rja@extremenetworks.com>
cc: Bob Braden <braden@ISI.EDU>, ietf@ietf.org, kireeti@juniper.net,
        iesg@ietf.org
Subject: Re: "IETF consensus" in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ] 
In-Reply-To: Message from rja@extremenetworks.com
   of "Thu, 30 Jan 2003 09:35:26 EST." <1261B871-3460-11D7-AE59-00039357A82A@extremenetworks.com> 
Date: Thu, 30 Jan 2003 10:22:44 -0500
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> It would seem quite simple for you to take the text of RFC-2434,
> edit the text appropriately to pick a more clear and accurate
> term, then run it past the community for BCP.

Sure, this is easy. The harder part is that there are many many RFCs
that use the "IETF Consensus" terminology in their IANA considerations
(e.g., the documents that sparked the original thread). I suspect that
the confusion will remain as long as folks read those RFCs and just
assume they know what the term is supposed to mean. But I agree it
makes sense to update the document for future usage.

Thomas



From owner-ietf@ietf.org  Thu Jan 30 10:38:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01544;
	Thu, 30 Jan 2003 10:38:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eGiV-0005y7-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 10:35:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eGhW-0005tS-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 10:34:02 -0500
Received: from psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00978;
	Thu, 30 Jan 2003 10:25:48 -0500 (EST)
Received: from roam.psg.com ([193.0.9.124])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18eGcu-000A2T-00; Thu, 30 Jan 2003 07:29:17 -0800
Received: from randy by roam.psg.com with local (Exim 4.12)
	id 18eGct-0000cB-00; Thu, 30 Jan 2003 16:29:15 +0100
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Thomas Narten <narten@us.ibm.com>
Cc: RJ Atkinson <rja@extremenetworks.com>, Bob Braden <braden@ISI.EDU>,
        ietf@ietf.org, kireeti@juniper.net, iesg@ietf.org
Subject: Re: "IETF consensus" in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ] 
References: <1261B871-3460-11D7-AE59-00039357A82A@extremenetworks.com>
	<200301301522.h0UFMiT02380@cichlid.adsl.duke.edu>
Message-Id: <E18eGct-0000cB-00@roam.psg.com>
Date: Thu, 30 Jan 2003 16:29:15 +0100
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>> It would seem quite simple for you to take the text of RFC-2434,
>> edit the text appropriately to pick a more clear and accurate
>> term, then run it past the community for BCP.
> Sure, this is easy. The harder part is that there are many many RFCs
> that use the "IETF Consensus" terminology in their IANA considerations

and they meant the current 2434 definition



From owner-ietf@ietf.org  Thu Jan 30 10:38:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01599;
	Thu, 30 Jan 2003 10:38:45 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eGqX-00070d-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 10:43:21 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eGjG-0006KR-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 10:35:50 -0500
Received: from klutz.cs.utk.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01049;
	Thu, 30 Jan 2003 10:27:35 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id B520913FB9; Thu, 30 Jan 2003 10:31:08 -0500 (EST)
Received: from klutz.cs.utk.edu ([127.0.0.1]) by localhost (klutz [127.0.0.1]) (amavisd-new) with ESMTP id 01085-09; Thu, 30 Jan 2003 10:31:08 -0000 (EST)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with SMTP
	id 1A930140A7; Thu, 30 Jan 2003 10:31:08 -0500 (EST)
Date: Thu, 30 Jan 2003 10:31:07 -0500
From: Keith Moore <moore@cs.utk.edu>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: moore@cs.utk.edu, narten@us.ibm.com, braden@isi.edu, ietf@ietf.org,
        kireeti@juniper.net, iesg@ietf.org
Subject: Re: "IETF consensus"  in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ]
Message-Id: <20030130103107.305bb5fd.moore@cs.utk.edu>
In-Reply-To: <1261B871-3460-11D7-AE59-00039357A82A@extremenetworks.com>
References: <200301300120.h0U1KQo02850@cichlid.adsl.duke.edu>
	<1261B871-3460-11D7-AE59-00039357A82A@extremenetworks.com>
X-Mailer: Sylpheed version 0.8.5claws (GTK+ 1.2.10; )
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new amavisd-new-20020630 with ClamAV
X-Razor-id: 50b238bb42e937701f7caf8b786e4cff35873c40
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > I don't know what can be done a this point to change the terminology
> > in 2434. It's been in use for some 4 years now...
> 
> It would seem quite simple for you to take the text of RFC-2434,
> edit the text appropriately to pick a more clear and accurate
> term, then run it past the community for BCP.

well, the phrase "IETF Consensus" would still be embedded in several 
other documents.  are you claiming that it's simple to update these
also?
 



From owner-ietf@ietf.org  Thu Jan 30 10:39:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01636;
	Thu, 30 Jan 2003 10:39:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eGrg-00075G-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 10:44:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eGm7-0006bE-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 10:38:47 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01183;
	Thu, 30 Jan 2003 10:30:33 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id h0UFY55x001401;
	Thu, 30 Jan 2003 10:34:05 -0500 (EST)
Date: Thu, 30 Jan 2003 10:34:05 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200301301534.h0UFY55x001401@newdev.harvard.edu>
To: narten@us.ibm.com, randy@psg.com
Subject: Re: "IETF consensus" in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ]
Cc: braden@isi.edu, iesg@ietf.org, ietf@ietf.org, kireeti@juniper.net,
        rja@extremenetworks.com
In-Reply-To: <E18eGct-0000cB-00@roam.psg.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> and they meant the current 2434 definition

or they misread 2434 (or did not read 2434) and thought they knew 
what "IETF consensus" means

Scott



From owner-ietf@ietf.org  Thu Jan 30 10:54:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02322;
	Thu, 30 Jan 2003 10:54:40 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eH2p-0000jI-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 10:56:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eGxk-0000Ro-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 10:50:48 -0500
Received: from prue.eim.surrey.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01843
	for <ietf@ietf.org>; Thu, 30 Jan 2003 10:42:33 -0500 (EST)
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 18eGsx-0001bD-00; Thu, 30 Jan 2003 15:45:51 +0000
Date: Thu, 30 Jan 2003 15:45:49 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Spencer Dawkins <sdawkins@cynetanetworks.com>
cc: dja2001@att.net, "" <ietf@ietf.org>
Subject: RE: WG Review: Enhancements to Internet email to support diverse
 service environments (lemonade)
In-Reply-To: <9255B6CD76A88943A3062F7D4E6432F543BAB1@mail.cynetanetworks.com>
Message-ID: <Pine.GSO.4.50.0301301542490.13475-100000@artemis.ee.surrey.ac.uk>
References: <9255B6CD76A88943A3062F7D4E6432F543BAB1@mail.cynetanetworks.com>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-102.9 required=7.0
	tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,NOSPAM_INC,
	      QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,
	      USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.43
X-Scanner: exiscan *18eGsx-0001bD-00*y.20DkrgAs.* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 29 Jan 2003, Spencer Dawkins wrote:

> David, you're a genius!

If only as much time was spent considering architectures as
considering acronyms.


> Glenn Parson told me he was VERY proud of the LEMONADE acronymn,
> so we probably need something more clever than MinIMAP...
>
> Spencer
>
> ... and I like dropping the "I", because there's no such thing
> as NON-Internet Messaging.

SMS? paging? fax? voicemail? telex?

L.

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



From owner-ietf@ietf.org  Thu Jan 30 10:58:07 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02462;
	Thu, 30 Jan 2003 10:58:06 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eHAJ-0001H5-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 11:03:47 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eH5u-0000wS-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 10:59:14 -0500
Received: from klutz.cs.utk.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02176;
	Thu, 30 Jan 2003 10:50:59 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 4EAAC13FB9; Thu, 30 Jan 2003 10:54:32 -0500 (EST)
Received: from klutz.cs.utk.edu ([127.0.0.1]) by localhost (klutz [127.0.0.1]) (amavisd-new) with ESMTP id 04377-10; Thu, 30 Jan 2003 10:54:31 -0000 (EST)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with SMTP
	id AC44613FA9; Thu, 30 Jan 2003 10:54:31 -0500 (EST)
Date: Thu, 30 Jan 2003 10:54:31 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Scott Bradner <sob@harvard.edu>
Cc: moore@cs.utk.edu, narten@us.ibm.com, randy@psg.com, braden@isi.edu,
        iesg@ietf.org, ietf@ietf.org, kireeti@juniper.net,
        rja@extremenetworks.com
Subject: Re: "IETF consensus" in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ]
Message-Id: <20030130105431.4bbef02f.moore@cs.utk.edu>
In-Reply-To: <200301301534.h0UFY55x001401@newdev.harvard.edu>
References: <E18eGct-0000cB-00@roam.psg.com>
	<200301301534.h0UFY55x001401@newdev.harvard.edu>
X-Mailer: Sylpheed version 0.8.5claws (GTK+ 1.2.10; )
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new amavisd-new-20020630 with ClamAV
X-Razor-id: 8cb86f1bf5109c141bb3bb328026c35eb0edd2ed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > and they meant the current 2434 definition
> 
> or they misread 2434 (or did not read 2434) and thought they knew 
> what "IETF consensus" means

which means that it's not simply a matter of revising text, but
of asking again what was intended, and perhaps reopening the debate.

so perhaps we should assume that they meant what was written in 2434
unless we have a good reason to believe otherwise.




From owner-ietf@ietf.org  Thu Jan 30 12:54:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05565;
	Thu, 30 Jan 2003 12:54:59 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eIu2-0006ZT-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 12:55:06 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eItP-0006Wy-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 12:54:27 -0500
Received: from mauve.mrochek.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05354
	for <ietf@ietf.org>; Thu, 30 Jan 2003 12:46:13 -0500 (EST)
From: ned.freed@mrochek.com
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01KRTMOLC35S002DEU@mauve.mrochek.com> for ietf@ietf.org; Thu,
 30 Jan 2003 09:49:43 -0800 (PST)
Date: Thu, 30 Jan 2003 09:49:15 -0800 (PST)
Subject: RE: WG Review: Enhancements to Internet email to support diverse
 service environments (lemonade)
In-reply-to: "Your message dated Thu, 30 Jan 2003 15:45:49 +0000 (GMT)"
 <Pine.GSO.4.50.0301301542490.13475-100000@artemis.ee.surrey.ac.uk>
To: Lloyd Wood <l.wood@eim.surrey.ac.uk>
Cc: Spencer Dawkins <sdawkins@cynetanetworks.com>, dja2001@att.net,
        ietf@ietf.org
Message-id: <01KRUBBQQ0A8002DEU@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Content-transfer-encoding: 7BIT
References: <9255B6CD76A88943A3062F7D4E6432F543BAB1@mail.cynetanetworks.com>
 <Pine.GSO.4.50.0301301542490.13475-100000@artemis.ee.surrey.ac.uk>
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

> On Wed, 29 Jan 2003, Spencer Dawkins wrote:

> > David, you're a genius!

> If only as much time was spent considering architectures as
> considering acronyms.


> > Glenn Parson told me he was VERY proud of the LEMONADE acronymn,
> > so we probably need something more clever than MinIMAP...
> >
> > Spencer
> >
> > ... and I like dropping the "I", because there's no such thing
> > as NON-Internet Messaging.

> SMS? paging? fax? voicemail? telex?

Er, exactly. This is exactly why the constraint to Internet messaging
was added, and is not likely to be removed.

				Ned



From owner-ietf@ietf.org  Thu Jan 30 13:08:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05811;
	Thu, 30 Jan 2003 13:08:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eJ8V-0007Wg-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 13:10:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eJ8L-0007UJ-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 13:09:53 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05731;
	Thu, 30 Jan 2003 13:01:37 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: WG Review: Enhancements to Internet email to support  diverse service environments (lemonade)
Date: Thu, 30 Jan 2003 13:05:11 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D097BFB@zoe.office.snowshore.com>
Thread-Topic: WG Review: Enhancements to Internet email to support  diverse service environments (lemonade)
Thread-Index: AcLH4rs0zhQ4GN41RRWWoVbnEEO+NQAo85iw
From: "Eric Burger" <eburger@snowshore.com>
To: "John C Klensin" <john-ietf@jck.com>, <ned.freed@mrochek.com>,
        "Pete Resnick" <presnick@qualcomm.com>
Cc: <ietf@ietf.org>, <iesg@ietf.org>,
        "IETF LEMONADE (E-mail)" <um@snowshore.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA05811

Executive Summary: Accept John's second proposal.  That is, take the charter as is, and insert a May 2003 deliverable of "lemonade Architecture, IESG and IETF Review, and Possible Rechartering".





Now that I'm clearing out my mailbox...

1) When I saw the flood of messages, and the nature of the objections, I wondered if anyone actually read the charter.  When I saw that a very old draft got posted, my faith in people was restored.

2) Pete - I'll take the fall for not posting the last revision for review.  There were about 4 changes from the last, publicly reviewed charter to the one submitted to the IESG in the last go round.  Each of those changes seemed minor (like what the acronym meant).  However, taken collectively, they are a larger leap.

Mea Culpa :-(


3) Initially, we were a bit leery about putting any changes to IMAP within the lemonade charter.  If we get more participation from the broader IMAP community, then I would be more comfortable with the idea.  That said, negotiable profiles do seem sensible.

4) Our original thoughts vis-a-vis IMAP was NOT to formally trim IMAP.  It was to (gulp) add a method for alternate retrieval (CHANNEL) and to have more relevant status information (e.g., media size).

5) For better or worse, lemonade has provided a forum (and one could say an impetus) for the discussion of some taboo topics.  For example, what started as a very limited scope need, server-to-server bulk notifications, has gotten people to actually WRITE the requirements, protocol issues, security issues, and privacy issues around notification in general.  This helps get the discussion out of the darkness of "doing that is bad, trust me; if you were knowledgeable you would understand" into the light of "read this paper - it explains the issues."  That alone is worth its weight in gold.

6) I have no problem narrowing the scope of the charter.  I have no problem expanding the text of the charter to more accurately reflect the scope (e.g., refine the language of bullet 4 to explicitly say "IMAP Profile").  I am leery of adding IMAPv5 or IMAPlite to the charter.  I really would like to the work group finish in a bounded time period.

7) As we are approaching our second year of BOF's and planning for the work of the WG, I think that we can make progress by taking John's second proposal.  In short, take the charter as is, and insert a May 2003 deliverable of "lemonade Architecture, IESG and IETF Review, and Possible Rechartering".  I would offer that starting with the architecture, instead of the requirements, would most likely result in a poor result.  We should push out the subsequent milestones appropriately, and mark them as tentative.

--
- Eric Burger
Co-chair, lemonade BOF

> -----Original Message-----
> From: John C Klensin [mailto:john-ietf@jck.com]
> Sent: Wednesday, January 29, 2003 5:01 PM
> To: ned.freed@mrochek.com; Pete Resnick
> Cc: ietf@ietf.org; iesg@ietf.org
> Subject: Re: WG Review: Enhancements to Internet email to support
> diverse service environments (lemonade)
> 
> 
> 
> 
> --On Wednesday, 29 January, 2003 13:06 -0800 
> "ned.freed@mrochek.com" <ned.freed@mrochek.com> wrote:
> 
> >> I agree. And unfortunately, I think this is due to a serious
> >> problem about which I'm quite distressed:
> >
> >> The proposed charter contained in the announcement is *not*
> >> the proposed charter worked out on the LEMONADE BOF mailing
> >> list. Not even close. The one on the list went through
> >> several revisions to include specific language in the work
> >> items about profiling of existing protocols, and that
> >> language has been removed in what was posted here. The one on
> >> the list was tailored specifically to avoid having the
> >> working group add to existing protocols (with IMAP as only
> >> one example) unless absolutely necessary, but rather to
> >> profile existing protocols if that solved the problem. The
> >> present charter gives the incorrect impression that the
> >> desire of the group is simply to add extensions, specifically
> >> to IMAP.
> >
> > Well, as it happens the charter that was posted to
> > ietf-announce wasn't the one the IESG approved either. It is
> > one from quite a few versions back.
> >
> > I've attached the current charter below.
> 
> Ned, this one is _lots_ better.  I'll leave sorting out how the 
> wrong version got posted to the IESG and the Secretariat.  But 
> my primary concern (and one of those on which Pete and I are 
> apparently in agreement) remains:  when I read "enhance...IMAP", 
> I don't infer "narrow the protocol for use in this environment" 
> or "specify a way to use the existing protocol to accomodate 
> these needs".  Instead, I infer "new feature", "new capability", 
> and "putting more stuff into the protocol".  I think there is 
> considerable resistance in the community to making IMAP bigger 
> -- while the four messages that have shown up on the list are 
> not much of a sample, I observe that at least three of them have 
> included "make it smaller, not larger" positions.
> 
> If the community believes all that has been said in Atlanta and 
> on the "problem-statement" list about raising architectural 
> issues early in the life of a WG rather than hitting the WG 
> during Last Call (and you can be assured that several of us will 
> scream loudly if this WG emits large extensions to IMAP without 
> really clear justification), then charter-time is the time to 
> fix this one.  If the intent that all of us have is the same 
> --which I suspect to be the case-- then all that is needed is to 
> fix text to make that intent clear to the community and to WG 
> members who have not participated in the previous discussions. 
> That should be helpful for the Chair(s), for the ADs and for the 
> community.
> 
> >> First, a process point: If these significant changes were
> >> made by the IESG to what was submitted, these should have
> >> been brought back to the list for approval.
> >
> > I regard this as being up to the chair of the group. The
> > charter that wasn't posted was iterated on by both the chairs
> > and the IESG.
> 
> Then this is an objection to the textual form of the charter 
> version you posted as well as to the form the Secretariat 
> posted.  If the "extend IMAP" issues are settled, then let's get 
> that fact  documented in the charter to prevent later surprises 
> and unpleasantness.   If they are not, then let's either
> 
> 	* Hold a review of those issues by some body whose
> 	responsibility is to the Internet, and Internet mail,
> 	infrastructure is taken broadly, not just accomodating a
> 	few new capabilities.  Have that review before the WG is
> 	initiated, and make its conclusions binding on the WG.
> 	
> 	* Provide, in the charter, a community review point at
> 	the initiation of significant extension work on IMAP or
> 	anything else(were such work to be initiated), so that
> 	we don't get a pushback situation well into the 11th
> 	hour.
> 
> regards,
>     john
> 
> 
> 



From owner-ietf@ietf.org  Thu Jan 30 15:15:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09283;
	Thu, 30 Jan 2003 15:15:24 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eL6Q-0005ty-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 15:16:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eKzk-0005jN-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 15:09:08 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08988;
	Thu, 30 Jan 2003 15:00:51 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18eKuy-0002BH-00; Thu, 30 Jan 2003 15:04:12 -0500
Date: Thu, 30 Jan 2003 15:04:12 -0500
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>, Thomas Narten <narten@us.ibm.com>
cc: RJ Atkinson <rja@extremenetworks.com>, Bob Braden <braden@ISI.EDU>,
        "ietf@ietf.org" <ietf@ietf.org>,
        "kireeti@juniper.net" <kireeti@juniper.net>,
        "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: "IETF consensus" in IANA considerations [was Re:
 Last Call: CR-LDP Extensions for ASON to Informational ]
Message-ID: <24924950.1043939052@p3.JCK.COM>
In-Reply-To: <E18eGct-0000cB-00@roam.psg.com>
References: <1261B871-3460-11D7-AE59-00039357A82A@extremenetworks.
 com>	<200301301522.h0UFMiT02380@cichlid.adsl.duke.edu>
 <E18eGct-0000cB-00@roam.psg.com>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Thursday, 30 January, 2003 16:29 +0100 Randy Bush 
<randy@psg.com> wrote:

>>> It would seem quite simple for you to take the text of
>>> RFC-2434, edit the text appropriately to pick a more clear
>>> and accurate term, then run it past the community for BCP.
>> Sure, this is easy. The harder part is that there are many
>> many RFCs that use the "IETF Consensus" terminology in their
>> IANA considerations
>
> and they meant the current 2434 definition

Except, perhaps, for the documents that were written before 2434 
with a rather specific definition --discussed with the IESG at 
the time-- in mind.  If 2434 modifies them, then 2434 can be 
updated and the update can update all of the earlier documents 
as well.   If 2434 doesn't modify them, then we are, for better 
or worse, back into the situation we were in with 2119 -- 
documents could either use it or could not refer to it but, 
instead, make up their own defintions.

The fact that there has been significant traffic on this 
probably justifies an update / clarification.  For the record, I 
don't care what that clarification is although:

	* I think pushing all of these things toward standards
	track would be a mistake.
	
	* I think that an intermediate position between
	"standards track document" and "RFC publication" is a
	desirable thing to have, when the WG's position is
	really that some determination of consensus and
	reasonableness by the IETF (not just by IANA) is
	desirable.

  john




From owner-ietf@ietf.org  Thu Jan 30 16:07:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10469;
	Thu, 30 Jan 2003 16:07:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eLdV-0007yi-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 15:50:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eLak-0007s3-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 15:47:22 -0500
Received: from e33.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10030;
	Thu, 30 Jan 2003 15:43:44 -0500 (EST)
Received: from westrelay01.boulder.ibm.com (westrelay01.boulder.ibm.com [9.17.194.22])
	by e33.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id h0UKlFIS069018;
	Thu, 30 Jan 2003 15:47:15 -0500
Received: from cichlid.adsl.duke.edu (sig-9-65-241-247.mts.ibm.com [9.65.241.247])
	by westrelay01.boulder.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id h0UKlDGa046602;
	Thu, 30 Jan 2003 13:47:13 -0700
Received: from cichlid.adsl.duke.edu (narten@localhost)
	by cichlid.adsl.duke.edu (8.11.6/8.9.3) with ESMTP id h0UKjDF05128;
	Thu, 30 Jan 2003 15:45:13 -0500
Message-Id: <200301302045.h0UKjDF05128@cichlid.adsl.duke.edu>
To: John C Klensin <john-ietf@jck.com>
cc: RJ Atkinson <rja@extremenetworks.com>, Bob Braden <braden@ISI.EDU>,
        "ietf@ietf.org" <ietf@ietf.org>,
        "kireeti@juniper.net" <kireeti@juniper.net>,
        "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: "IETF consensus" in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ] 
In-Reply-To: Message from john-ietf@jck.com
   of "Wed, 29 Jan 2003 21:12:36 EST." <197026338.1043874756@p3.JCK.COM> 
Date: Thu, 30 Jan 2003 15:45:13 -0500
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

John,

> Thomas, not to be splitting hairs, but the intent --at least in 
> SMTP-EXT (STD10/RFC1869), which was cited as an example-- was 
> somewhat more than simple publication as an RFC (or, in your 
> words, "a document that gets published as an RFC").

Agreed, now that I have gone and looked at RFC 1869. Some relevant
wording from 1869 would seem to be:

   Any keyword values presented in the EHLO response that do not begin
   with "X" must correspond to a standard, standards-track, or IESG-
   approved experimental SMTP service extension registered with IANA.  A
   conforming server must not offer non "X" prefixed keyword values that
   are not described in a registered extension.

By my read, it would seem that informational documents can't be used
to assign such code points.
   
> While, clearly, "standards track" was not intended, we did intend
> that the IESG make a formal decision that the request was consistent
> with community consensus (as well as having a published document).
> We didn't specify what steps the IESG would go through in reaching
> that conclusion, but, other than the 2026 requirement for a Last
> Call for standards-track documents, nothing else does either.  The
> simple ability to convince the RFC Editor to publish an
> informational or experimental document was not intended to be
> sufficient, even with IESG agreement that the document wasn't likely
> to be severely harmful.

I should clarify a bit, as I also agree that just convincing the RFC
editor to publish is not good enough. When the IESG reviews non-WG
documents, ADs always have the chance to review them to see if there
is some reason to comment or otherwise hold up publication. In the
case of something like an SMTP extension, I can't imagine that the
document would get approved without a relevant AD first consulting
with some mail knowledgable folk first. The details of how that are
done are not written down, but in practice broken proposals would not
get approval without some discussion first.

In practice, "IETF Consensus" (as defined in 2434) means that
procedurally the IESG has to sign off on a document before IANA
assigns code points for it. And for something that relates to an
existing IETF protocol, we almost always check with some knowledgable
folk as to whether the document conflicts with that protocol or
otherwise is problematical before approving. So, I suspect that in
fact, the review you are saying is supposed to be happening would
happen in practice in this case (and in other similar cases).

> > So, let's be clear that in the context of most of the
> > discussion on this thread, folks seem to be applying their own
> > definition of what "IETF Consensus" means when in fact the
> > 2434 definition is what should be used, as is cited in the
> > relevant IANA considerations section.
> >
> > I don't know what can be done a this point to change the
> > terminology in 2434. It's been in use for some 4 years now...

> I don't see that there is a problem.  Especially to the extent 
> that you can argue that 2434 modifies or clarifies the 
> procedures that 1869 calls for, I can imagine nothing that would 
> prevent revising and reissuing 2434 if you think clarification 
> is needed.

I don't claim 2434 updates 1869; in fact, I'd argue otherwise. 1869
was cited as a specific example, but you've pointed out that it is an
incorrect example.

> Or, if it were preferred, one could modify the I-D 
> IESG procedures document to "update" 2434 and specify exactly 
> what the IESG does in those situations going forward.

I think the wording in 2434 is quite clear. When someone says "IETF
Consensus, as defined in [RFC 2434]" (which is the type of language I
like to see in documents because it is VERY clear), IANA doesn't
assign code points until the document is approved for publication as
an RFC. As the IESG approval is one of those steps, IESG has a chance
to review.  If folks actually want a different criteria, there are a
number of other choices to choose from in 2434, or they could write a
very specific one (subject to it being something IANA can actually
deal with).

Thomas



From owner-ietf@ietf.org  Thu Jan 30 16:23:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10823;
	Thu, 30 Jan 2003 16:23:37 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eLl0-0008Ii-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 15:57:58 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eLiM-0008Ca-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 15:55:14 -0500
Received: from e34.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10177;
	Thu, 30 Jan 2003 15:51:36 -0500 (EST)
Received: from westrelay01.boulder.ibm.com (westrelay01.boulder.ibm.com [9.17.194.22])
	by e34.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id h0UKt8JV043138;
	Thu, 30 Jan 2003 15:55:08 -0500
Received: from cichlid.adsl.duke.edu (sig-9-65-241-247.mts.ibm.com [9.65.241.247])
	by westrelay01.boulder.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id h0UKt6Ga041040;
	Thu, 30 Jan 2003 13:55:07 -0700
Received: from cichlid.adsl.duke.edu (narten@localhost)
	by cichlid.adsl.duke.edu (8.11.6/8.9.3) with ESMTP id h0UKr7805147;
	Thu, 30 Jan 2003 15:53:07 -0500
Message-Id: <200301302053.h0UKr7805147@cichlid.adsl.duke.edu>
To: John C Klensin <john-ietf@jck.com>
cc: Randy Bush <randy@psg.com>, RJ Atkinson <rja@extremenetworks.com>,
        Bob Braden <braden@ISI.EDU>, "ietf@ietf.org" <ietf@ietf.org>,
        "kireeti@juniper.net" <kireeti@juniper.net>,
        "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: "IETF consensus" in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ] 
In-Reply-To: Message from john-ietf@jck.com
   of "Thu, 30 Jan 2003 15:04:12 EST." <24924950.1043939052@p3.JCK.COM> 
Date: Thu, 30 Jan 2003 15:53:07 -0500
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

John,

> > and they meant the current 2434 definition

> Except, perhaps, for the documents that were written before 2434 
> with a rather specific definition --discussed with the IESG at 
> the time-- in mind.  If 2434 modifies them, then 2434 can be 
> updated and the update can update all of the earlier documents 
> as well.

RFC 2434 doesn't update any IANA instructions that exist in RFCs that
predate 2434 - I'd encourage folk to go and read the document... I'd
like to think it's a useful read :-)

> If 2434 doesn't modify them, then we are, for better 
> or worse, back into the situation we were in with 2119 -- 
> documents could either use it or could not refer to it but, 
> instead, make up their own defintions.

That has always been and continues to be an option.  But for the
majority of documents, chosing from a menu of well-defined choices
seems to be simpler for everyone. IANA also has to be able to
understand what needs to happen, for instance, and the burden on IANA
shouldn't be excessive either. Sticking to well-known definitions when
possible seems to help here.

> The fact that there has been significant traffic on this 
> probably justifies an update / clarification.  For the record, I 
> don't care what that clarification is although:

> 	* I think pushing all of these things toward standards
> 	track would be a mistake.

I agree. That is why there are categories like "expert review", or
"First Come First Served"

> 	* I think that an intermediate position between
> 	"standards track document" and "RFC publication" is a
> 	desirable thing to have, when the WG's position is
> 	really that some determination of consensus and
> 	reasonableness by the IETF (not just by IANA) is
> 	desirable.

The menu choice out of 2434 that I suggest to people for the above is
"Expert Review".

Thomas



From owner-ietf@ietf.org  Thu Jan 30 16:58:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11580;
	Thu, 30 Jan 2003 16:57:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eMMu-0002KG-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 16:37:08 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eMJ4-0001rG-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 16:33:18 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10910;
	Thu, 30 Jan 2003 16:29:11 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18eMIb-0002Mr-00; Thu, 30 Jan 2003 16:32:41 -0500
Date: Thu, 30 Jan 2003 16:32:41 -0500
From: John C Klensin <john-ietf@jck.com>
To: Thomas Narten <narten@us.ibm.com>
cc: RJ Atkinson <rja@extremenetworks.com>, Bob Braden <braden@ISI.EDU>,
        "ietf@ietf.org" <ietf@ietf.org>,
        "kireeti@juniper.net" <kireeti@juniper.net>,
        "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: "IETF consensus" in IANA considerations [was Re:
 Last Call: CR-LDP Extensions for ASON to Informational ]
Message-ID: <30233623.1043944361@p3.JCK.COM>
In-Reply-To: <200301302045.h0UKjDF05128@cichlid.adsl.duke.edu>
References:  <200301302045.h0UKjDF05128@cichlid.adsl.duke.edu>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Thursday, 30 January, 2003 15:45 -0500 Thomas Narten 
<narten@us.ibm.com> wrote:

> John,
>
>> Thomas, not to be splitting hairs, but the intent --at least
>> in  SMTP-EXT (STD10/RFC1869), which was cited as an example--
>> was  somewhat more than simple publication as an RFC (or, in
>> your  words, "a document that gets published as an RFC").
>
> Agreed, now that I have gone and looked at RFC 1869. Some
> relevant wording from 1869 would seem to be:
>
>    Any keyword values presented in the EHLO response that do
> not begin    with "X" must correspond to a standard,
> standards-track, or IESG-    approved experimental SMTP
> service extension registered with IANA.  A    conforming
> server must not offer non "X" prefixed keyword values that
> are not described in a registered extension.
>
> By my read, it would seem that informational documents can't
> be used to assign such code points.

That was the conclusion of the WG.  I don't exactly remember the 
reasoning, but it might have had something to do with a 
conviction that we wanted the barrier to be fairly high and 
serious and that even Experimental was an escape clause.

>> While, clearly, "standards track" was not intended, we did
>> intend that the IESG make a formal decision that the request
>> was consistent with community consensus (as well as having a
>> published document). We didn't specify what steps the IESG
>> would go through in reaching that conclusion, but, other than
>> the 2026 requirement for a Last Call for standards-track
>> documents, nothing else does either.  The simple ability to
>> convince the RFC Editor to publish an informational or
>> experimental document was not intended to be sufficient, even
>> with IESG agreement that the document wasn't likely to be
>> severely harmful.
>
> I should clarify a bit, as I also agree that just convincing
> the RFC editor to publish is not good enough. When the IESG
> reviews non-WG documents, ADs always have the chance to review
> them to see if there is some reason to comment or otherwise
> hold up publication. In the case of something like an SMTP
> extension, I can't imagine that the document would get
> approved without a relevant AD first consulting with some mail
> knowledgable folk first. The details of how that are done are
> not written down, but in practice broken proposals would not
> get approval without some discussion first.

Yes, but part of the discussion in Atlanta and on the 
problem-statement list is whether the type of review you are 
describing is an abuse of IESG authority and discretion. 
RFC2026, at least as I read it, permits IESG to hold up an 
informational or experimental document that was submitted to the 
RFC Editor _only_ to prevent or annotate end-runs and things 
that would be harmful to the infrastructure.  "Not harmful" is a 
much lower threshold than "IETF Consensus".   So, if you expect 
IESG review to "hold up" anything that does not originate from 
within the IETF, or to comment on any such documents, you had 
best seek a procedural authorization for doing so.  I can't 
speak for the community, but my impression is that tolerance for 
IESG "holding things up" --and I am astonished that you are 
willing to use those words-- is rapidly diminishing.

> In practice, "IETF Consensus" (as defined in 2434) means that
> procedurally the IESG has to sign off on a document before IANA
> assigns code points for it. And for something that relates to
> an existing IETF protocol, we almost always check with some
> knowledgable folk as to whether the document conflicts with
> that protocol or otherwise is problematical before approving.
> So, I suspect that in fact, the review you are saying is
> supposed to be happening would happen in practice in this case
> (and in other similar cases).

Yes, but see above.

>> > So, let's be clear that in the context of most of the
>> > discussion on this thread, folks seem to be applying their
>> > own definition of what "IETF Consensus" means when in fact
>> > the 2434 definition is what should be used, as is cited in
>> > the relevant IANA considerations section.
>> >
>> > I don't know what can be done a this point to change the
>> > terminology in 2434. It's been in use for some 4 years
>> > now...
>
>> I don't see that there is a problem.  Especially to the
>> extent  that you can argue that 2434 modifies or clarifies
>> the  procedures that 1869 calls for, I can imagine nothing
>> that would  prevent revising and reissuing 2434 if you think
>> clarification  is needed.
>
> I don't claim 2434 updates 1869; in fact, I'd argue otherwise.
> 1869 was cited as a specific example, but you've pointed out
> that it is an incorrect example.

Ok.  Then we need to add to the oral tradition that, if a WG 
wants serious review, they should not use the term "IETF 
Consensus", but should replicate the 1869 text, with or without 
inclusion of informational documents as they think appropriate.

>> Or, if it were preferred, one could modify the I-D
>> IESG procedures document to "update" 2434 and specify exactly
>> what the IESG does in those situations going forward.
>
> I think the wording in 2434 is quite clear. When someone says
> "IETF Consensus, as defined in [RFC 2434]" (which is the type
> of language I like to see in documents because it is VERY
> clear), IANA doesn't assign code points until the document is
> approved for publication as an RFC. As the IESG approval is
> one of those steps, IESG has a chance to review.  If folks
> actually want a different criteria, there are a number of
> other choices to choose from in 2434, or they could write a
> very specific one (subject to it being something IANA can
> actually deal with).

Ok, modulo the observations above.

   john




From owner-ietf@ietf.org  Thu Jan 30 16:58:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11588;
	Thu, 30 Jan 2003 16:57:39 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eMME-0002GG-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 16:36:26 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eMHa-0001j6-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 16:31:42 -0500
Received: from iserver.sj.symbol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10896
	for <ietf@ietf.org>; Thu, 30 Jan 2003 16:27:44 -0500 (EST)
Received: from gwianameserver.sj.symbol.com (symsjdmz.sj.symbol.com [63.145.233.50])
	by iserver.sj.symbol.com (8.12.2/8.12.2) with SMTP id h0ULS1qQ000018
	for <ietf@ietf.org>; Thu, 30 Jan 2003 13:28:01 -0800 (PST)
Received: from SJ-DOM-Message_Server by gwianameserver.sj.symbol.com
	with Novell_GroupWise; Thu, 30 Jan 2003 13:31:10 -0800
Message-Id: <se39291e.068@gwianameserver.sj.symbol.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.7.1 Beta
Date: Thu, 30 Jan 2003 13:31:11 -0800
From: "Clint Chaplin" <cchaplin@sj.symbol.com>
To: <sdawkins@cynetanetworks.com>, <L.Wood@eim.surrey.ac.uk>, <ietf@ietf.org>
Cc: <dja2001@att.net>
Subject: RE: WG Review: Enhancements to Internet email to support
	diverseservice environments (lemonade)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA11588

I thought that the first milestone of any project was thinking up the acronym.

The second was designing the T-shirt.

Clint (JOATMON) Chaplin

>>> Lloyd Wood <l.wood@eim.surrey.ac.uk> 1/30/03 07:45:49 >>>
On Wed, 29 Jan 2003, Spencer Dawkins wrote:

> David, you're a genius!

If only as much time was spent considering architectures as
considering acronyms.


> Glenn Parson told me he was VERY proud of the LEMONADE acronymn,
> so we probably need something more clever than MinIMAP...
>
> Spencer
>
> ... and I like dropping the "I", because there's no such thing
> as NON-Internet Messaging.

SMS? paging? fax? voicemail? telex?

L.

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





From owner-ietf@ietf.org  Thu Jan 30 17:21:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12025;
	Thu, 30 Jan 2003 17:21:06 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eMTN-0002fM-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 16:43:49 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eMP5-0002TP-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 16:39:23 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11106;
	Thu, 30 Jan 2003 16:35:43 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18eMOu-0002NB-00; Thu, 30 Jan 2003 16:39:12 -0500
Date: Thu, 30 Jan 2003 16:39:12 -0500
From: John C Klensin <john-ietf@jck.com>
To: Thomas Narten <narten@us.ibm.com>, John C Klensin <john-ietf@jck.com>
cc: Randy Bush <randy@psg.com>, RJ Atkinson <rja@extremenetworks.com>,
        Bob Braden <braden@ISI.EDU>, "ietf@ietf.org" <ietf@ietf.org>,
        "kireeti@juniper.net" <kireeti@juniper.net>,
        "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: "IETF consensus" in IANA considerations [was Re:
 Last Call: CR-LDP Extensions for ASON to Informational ]
Message-ID: <30625166.1043944752@p3.JCK.COM>
In-Reply-To: <200301302053.h0UKr7805147@cichlid.adsl.duke.edu>
References:  <200301302053.h0UKr7805147@cichlid.adsl.duke.edu>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Thursday, 30 January, 2003 15:53 -0500 Thomas Narten 
<narten@us.ibm.com> wrote:

>> If 2434 doesn't modify them, then we are, for better
>> or worse, back into the situation we were in with 2119 --
>> documents could either use it or could not refer to it but,
>> instead, make up their own defintions.
>
> That has always been and continues to be an option.  But for
> the majority of documents, chosing from a menu of well-defined
> choices seems to be simpler for everyone. IANA also has to be
> able to understand what needs to happen, for instance, and the
> burden on IANA shouldn't be excessive either. Sticking to
> well-known definitions when possible seems to help here.

Absolutely.  Otherwise, this discussion wouldn't be worth the 
trouble.  But, if you are going to define "IETF Consensus" as 
"Publication as an RFC" then

	- We don't need the added term to add confusion.
	
	- We open up a loophole case in which a document comes
	to the RFC Editor, then to the IESG.  The IESG decides
	it is a bad idea, and puts a disclaimer on it that says
	"this is a terrible idea".  The RFC Editor decides to
	publish it anyway.  We now have an RFC that, regardless
	of its other properties, clearly does not represent IESG
	consensus that it is a good idea.  But whatever it calls
	for is eligible for registration.

>> The fact that there has been significant traffic on this
>> probably justifies an update / clarification.  For the
>> record, I  don't care what that clarification is although:
>
>> 	* I think pushing all of these things toward standards
>> 	track would be a mistake.
>
> I agree. That is why there are categories like "expert
> review", or "First Come First Served"

But the "expert review" is, in my experience in most cases, a 
sanity check by one person, not the judgement of the community 
that something is appropriate.  So it responds to one of the 
possible cases, but not the others.

>> 	* I think that an intermediate position between
>> 	"standards track document" and "RFC publication" is a
>> 	desirable thing to have, when the WG's position is
>> 	really that some determination of consensus and
>> 	reasonableness by the IETF (not just by IANA) is
>> 	desirable.
>
> The menu choice out of 2434 that I suggest to people for the
> above is "Expert Review".

See above.

    john




From owner-ietf@ietf.org  Thu Jan 30 17:45:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12447;
	Thu, 30 Jan 2003 17:45:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eMr6-0003pJ-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 17:08:20 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eMgL-0003N3-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 16:57:15 -0500
Received: from numenor.qualcomm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11394;
	Thu, 30 Jan 2003 16:53:35 -0500 (EST)
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.12.3/8.12.5/1.0) with ESMTP id h0ULv52d029019
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 30 Jan 2003 13:57:06 -0800 (PST)
Received: from [129.46.74.134] (loud.qualcomm.com [129.46.74.134])
	by neophyte.qualcomm.com (8.12.3/8.12.5/1.0) with ESMTP id h0ULuwsd000179;
	Thu, 30 Jan 2003 13:56:59 -0800 (PST)
Mime-Version: 1.0
Message-Id: <a06000248ba5f4e3b144d@[129.46.74.134]>
In-Reply-To: <181950110.1043859679@p3.JCK.COM>
References: <200301282312.SAA11118@ietf.org>
 <169878963.1043847608@p3.JCK.COM>
 <p0600010dba5dd6b34009@[216.43.25.67]>
 <175052472.1043852782@p3.JCK.COM>
 <p06000111ba5de5b9c58d@[216.43.25.67]>
 <01KRT49TEUKI002DEU@mauve.mrochek.com>
 <181950110.1043859679@p3.JCK.COM>
X-Mailer: Eudora for Mac OS X v6.0a
Date: Thu, 30 Jan 2003 13:56:53 -0800
To: John C Klensin <john-ietf@jck.com>,
        "ned.freed@mrochek.com" <ned.freed@mrochek.com>,
        Pete Resnick <presnick@qualcomm.com>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: WG Review: Enhancements to Internet email to support  
 diverse service environments (lemonade)
Cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>,
        um@snowshore.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b25
Sender: owner-ietf@ietf.org
Precedence: bulk

At 5:01 PM -0500 1/29/03, John C Klensin wrote:

>   But my primary concern (and one of those on which Pete and I are 
> apparently in agreement) remains:  when I read "enhance...IMAP", I 
> don't infer "narrow the protocol for use in this environment" or 
> "specify a way to use the existing protocol to accomodate these 
> needs".  Instead, I infer "new feature", "new capability", and 
> "putting more stuff into the protocol".  I think there is 
> considerable resistance in the community to making IMAP bigger -- 
> while the four messages that have shown up on the list are not much 
> of a sample, I observe that at least three of them have included 
> "make it smaller, not larger" positions.

This raises an interesting point that may be in danger of being 
obscured.  I think there is general agreement that IMAP is too 
complex.  However, concepts such as "IMAP lite" (or even "IMAP 
light"), simplification, pruning, etc. can be understood in very 
different ways.  It could mean simplifying interoperability by 
reducing options and eliminating permitted behavioral differences 
(especially among servers).  It could also mean taking out commands 
and responses.

The former can be accomplished in an interoperable way; a new IMAP 
revision or capability could be defined which includes a number of 
previous options, and specifies varies behavioral aspects (along the 
lines of RFC 1123).  Clients written to previous versions of IMAP 
would be able to interoperate with a new server just fine.

The latter, while making the protocol simpler and easier to 
understand and implement, risks being non-interoperable with previous 
versions.
-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly-selected tag: ---------------
A server is only as secure as its dumbest administrator
                                         --Steve Dorner



From owner-ietf@ietf.org  Thu Jan 30 18:29:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13270;
	Thu, 30 Jan 2003 18:28:47 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eNkX-0000Tv-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 18:05:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eNe8-0000Dw-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 17:59:00 -0500
Received: from iagu.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12730
	for <ietf@ietf.org>; Thu, 30 Jan 2003 17:55:14 -0500 (EST)
Received: from [203.32.153.90] (andrewr@localhost.iagu.net [127.0.0.1])
	by iagu.net (8.12.3/8.12.4) with ESMTP id h0UMwjCt020833;
	Fri, 31 Jan 2003 09:28:45 +1030 (CST)
	(envelope-from andrewr@iagu.net)
Mime-Version: 1.0
X-Sender: andrewr@127.0.0.1
Message-Id: <p05200f00ba5f55d5653e@[203.32.153.90]>
In-Reply-To: <7856.1043838807@munnari.OZ.AU>
References: <200301282312.SAA11118@ietf.org>
 <7856.1043838807@munnari.OZ.AU>
Date: Fri, 31 Jan 2003 09:29:13 +1030
To: Robert Elz <kre@munnari.OZ.AU>, ietf@ietf.org
From: Andrew Rutherford <andrewr@iagu.net>
Subject: Re: WG Review: Enhancements to Internet email to support diverse
 service environments (lemonade)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 6:13 PM +0700 29/1/03, Robert Elz wrote:

>   | 2.  Enhance the existing IMAP4 message retrieval protocol to satisfy
>   |     the requirements for streaming playback of multimedia content.
>
>What a horrid idea?   How do "streaming playback" and "message retrieval"
>possibly fit together at all?

Voice Mail. A number of ISDN access devices without significant local
storage are capable of converting an incoming call to an SMTP stream
on the fly and spooling it to a mail server. Pretty much everyone who
is implementing this is doing it the same way, so there's no need for
the IETF to step in.

Retrieval is then easy for someone with an IMAP client on their primary
system if it's capable of playing audio, but it's more complicated if
the user wishes to retrieve the message from a phone. Currently there
are a number of different approaches to this problem - the ones I have
come across include:

1) An application between the IMAP server and the voice gateway that
retrieves the whole message, then delivers it via RTSP at the correct
rate.

2) Some other interface directly to the mail store that bypasses the 
IMAP server.

3) The voice gateway directly accessing the IMAP server and plays with
TCP window sizes and delaying acknowledgements to limit the amount of
the voice mail  stored in memory in the voice gateway at any point in
time.

In cases 1 & 2, almost always some form of proprietary signalling
protocol then runs between the access device and intermediate
application (1) or the message store (2).

My view is that whenever there are different groups trying to solve the
same problem and coming up with different, non-interoperable solutions
based on IETF-defined standards then it really is in the IETF's court
to at least consider some form of standard or informational RFC.
Lemonade seems to fit the bill.

>Is this yet another attempt to pervert
>a protocol into meeting some other quite unrelated need, for the sole
>purpose of getting through firewalls or similar?   Drop this nonsense.



From owner-ietf@ietf.org  Thu Jan 30 21:14:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16325;
	Thu, 30 Jan 2003 21:13:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eQMN-00028N-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 20:52:51 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eQLM-00025c-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 20:51:48 -0500
Received: from merlot.juniper.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16012;
	Thu, 30 Jan 2003 20:48:05 -0500 (EST)
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 h0V1paS74086;
	Thu, 30 Jan 2003 17:51:36 -0800 (PST)
	(envelope-from kireeti@juniper.net)
Received: from localhost (kireeti@localhost)
	by kummer.juniper.net (8.11.6/8.9.3) with ESMTP id h0V1pam13895;
	Thu, 30 Jan 2003 17:51:36 -0800 (PST)
	(envelope-from kireeti@juniper.net)
X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs
Date: Thu, 30 Jan 2003 17:51:36 -0800 (PST)
From: Kireeti Kompella <kireeti@juniper.net>
To: Thomas Narten <narten@us.ibm.com>
cc: Bob Braden <braden@ISI.EDU>, "ietf@ietf.org" <ietf@ietf.org>,
        "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: "IETF consensus" in IANA considerations [was Re: Last Call:
 CR-LDP Extensions for ASON to Informational ] 
In-Reply-To: <200301302045.h0UKjDF05128@cichlid.adsl.duke.edu>
Message-ID: <20030130171430.B13746-100000@kummer.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Thomas,

On Thu, 30 Jan 2003, Thomas Narten wrote:

> In practice, "IETF Consensus" (as defined in 2434) means that
> procedurally the IESG has to sign off on a document before IANA
> assigns code points for it.

RFC 2434 has (among others) these two definitions:

      IESG Approval - New assignments must be approved by the IESG, but
           there is no requirement that the request be documented in an
           RFC (...)

      IETF Consensus - New values are assigned through the IETF
           consensus process. Specifically, new assignments are made via
           RFCs approved by the IESG.  (...)

I understand the first: it's completely within the IESG, and no RFC is
required.

For the latter, clearly IESG approval and an RFC are necessary.  And
your note above seems to indicate that these are sufficient.  In that
case, what does the phrase "through the IETF consensus process" mean?

And, if your note is correct, why was an IETF-wide Last Call issued?
Finally, why, when there was an active debate with no consensus (IMHO),
was the document summarily approved?

If the IESG saw rough consensus in the debate, that would be useful
information.  If on the other hand the IESG issued the Last Call as a
formality, that would be useful to know as well.

> I think the wording in 2434 is quite clear.  When someone says "IETF
> Consensus, as defined in [RFC 2434]" (which is the type of language I
> like to see in documents because it is VERY clear), IANA doesn't
> assign code points until the document is approved for publication as
> an RFC.

Perhaps "IETF Consensus" being defined to mean "an RFC with IESG
approval" is clear to you.  For my part, I see neither 'IETF' nor
'consensus' in "an RFC with IESG approval".  If the category were
called "IESG Approval documented in an RFC", I wouldn't be having
this discussion.

Kireeti.




From owner-ietf@ietf.org  Thu Jan 30 22:41:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17342;
	Thu, 30 Jan 2003 22:41:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eRli-0006R5-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 22:23:06 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eRkC-0006ME-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 22:21:33 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17078
	for <ietf@ietf.org>; Thu, 30 Jan 2003 22:17:48 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.8.Alpha0/8.12.8.Alpha0) with ESMTP id h0V3L46g027231;
	Thu, 30 Jan 2003 22:21:04 -0500
Message-Id: <200301310321.h0V3L46g027231@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4+dev
To: Andrew Rutherford <andrewr@iagu.net>
Cc: Robert Elz <kre@munnari.OZ.AU>, ietf@ietf.org
Subject: Re: WG Review: Enhancements to Internet email to support diverse service environments (lemonade) 
In-Reply-To: Your message of "Fri, 31 Jan 2003 09:29:13 +1030."
             <p05200f00ba5f55d5653e@[203.32.153.90]> 
References: <200301282312.SAA11118@ietf.org> <7856.1043838807@munnari.OZ.AU>
            <p05200f00ba5f55d5653e@[203.32.153.90]>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_2078329910P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 30 Jan 2003 22:21:03 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Fri, 31 Jan 2003 09:29:13 +1030, Andrew Rutherford <andrewr@iagu.net>  said:

> Voice Mail. A number of ISDN access devices without significant local
> storage are capable of converting an incoming call to an SMTP stream
> on the fly and spooling it to a mail server. Pretty much everyone who
> is implementing this is doing it the same way, so there's no need for
> the IETF to step in.

Life sucks if the mail server 421's you when you don't have local storage.....

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

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

iD8DBQE+OeufcC3lWbTT17ARAjrTAJ40MhRa6jnFAYoMTYXrm3KLtNcwowCbBlZ1
8zwZkTVEFBquIrpNphpMohw=
=6TjH
-----END PGP SIGNATURE-----

--==_Exmh_2078329910P--



From owner-ietf@ietf.org  Thu Jan 30 23:55:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18925;
	Thu, 30 Jan 2003 23:54:38 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eSzk-0002WG-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 23:41:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eSyf-0002SE-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 23:40:36 -0500
Received: from numenor.qualcomm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18534;
	Thu, 30 Jan 2003 23:36:48 -0500 (EST)
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.12.3/8.12.5/1.0) with ESMTP id h0V4eJ2d019602
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 30 Jan 2003 20:40:19 -0800 (PST)
Received: from [129.46.74.134] (vpn-10-50-0-11.qualcomm.com [10.50.0.11])
	by crowley.qualcomm.com (8.12.3/8.12.5/1.0) with ESMTP id h0V4eD5O021423;
	Thu, 30 Jan 2003 20:40:13 -0800 (PST)
Mime-Version: 1.0
Message-Id: <a06000251ba5fac7e895f@[129.46.74.134]>
In-Reply-To: <43117369.1043957244@p3.JCK.COM>
References: <200301282312.SAA11118@ietf.org>
 <169878963.1043847608@p3.JCK.COM>
 <p0600010dba5dd6b34009@[216.43.25.67]>
 <175052472.1043852782@p3.JCK.COM>
 <p06000111ba5de5b9c58d@[216.43.25.67]>
 <01KRT49TEUKI002DEU@mauve.mrochek.com>
 <181950110.1043859679@p3.JCK.COM>
 <a06000248ba5f4e3b144d@[129.46.74.134]>
 <43117369.1043957244@p3.JCK.COM>
X-Mailer: Eudora for Mac OS X v6.0a
Date: Thu, 30 Jan 2003 20:39:27 -0800
To: John C Klensin <john@jck.com>, Randall Gellens <randy@qualcomm.com>,
        John C Klensin <john-ietf@jck.com>,
        "ned.freed@mrochek.com" <ned.freed@mrochek.com>,
        Pete Resnick <presnick@qualcomm.com>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: WG Review: Enhancements to Internet email to support   
 diverse service environments (lemonade)
Cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>,
        "um@snowshore.com" <um@snowshore.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b25
Sender: owner-ietf@ietf.org
Precedence: bulk

At 8:07 PM -0500 1/30/03, John C Klensin wrote:

>  This really isn't worth much discussion unless someone is really 
> going to launch such an effort, but I don't see the distinction as 
> clearly as you do.

One concern I had was that there would appear to be agreement that 
lemonade would "simplify IMAP", but in reality people expected 
different things, and would then object when the WG produced 
something different.  "Simplifying" can mean different things.

>   We already have a situation in which some clients won't 
> interoperate well with some servers because the clients think they 
> need certain capabilities that those servers don't support.  And we 
> have other server authors that have refused to implement certain 
> features because they (the authors) are convinced those features 
> are brain-damaged.

True.

>  I'd like to see a WG give careful consideration to the question of 
> the damage that would be done by pulling commands and replacing 
> them with better/ cleaner designs as well as the type of revision I 
> think you anticipate with the first case.

IMAP does a lot of things.  It provides access to messages, 
information about those messages, various mailbox management things, 
access to information about mailboxes, creation of messages, and so 
on.  There's been suggestions over the years that this is really too 
much for one protocol, that, for example, mailbox management should 
be a different protocol.  There was some interest a while back in 
using ACAP to provide information about mailboxes and messages, 
leaving IMAP to just offer access to the messages.

On the other hand, one of the complaints by people implementing 
Internet mail clients on handsets and palm devices is that there are 
too many protocols, each with its own syntax.  SMTP, IMAP, MIME and 
so on all require different parsers.  Adding still more protocols 
would make this aspect worse.

>  But, in the last analysis, IMAP4bis is still at Proposed.  Like 
> you, I'd prefer something easier to implement and deploy that is 
> fully compatible with IMAP4bis.  But, if that isn't possible, then 
> I think it would be rational to consider other alternatives, with 
> the understanding that some implementations would try to be 
> conforming to both the older and newer versions and that it would 
> be wise to design things so as to make that possible.

I think people have tended to be scared of this approach.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly-selected tag: ---------------
Support the League of Winged Voters              --Firesign Theatre



From owner-ietf@ietf.org  Thu Jan 30 23:56:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18936;
	Thu, 30 Jan 2003 23:55:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eSts-0002DU-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 23:35:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eStL-0002An-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 23:35:03 -0500
Received: from iagu.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18415
	for <ietf@ietf.org>; Thu, 30 Jan 2003 23:31:18 -0500 (EST)
Received: from [203.32.153.90] (andrewr@localhost.iagu.net [127.0.0.1])
	by iagu.net (8.12.3/8.12.4) with ESMTP id h0V4YnCt026280;
	Fri, 31 Jan 2003 15:04:49 +1030 (CST)
	(envelope-from andrewr@iagu.net)
Mime-Version: 1.0
X-Sender: andrewr@127.0.0.1
Message-Id: <p05200f02ba5fa9a1092d@[203.32.153.90]>
In-Reply-To: <200301310321.h0V3L46g027231@turing-police.cc.vt.edu>
References: <200301282312.SAA11118@ietf.org>
 <7856.1043838807@munnari.OZ.AU>           
 <p05200f00ba5f55d5653e@[203.32.153.90]>
 <200301310321.h0V3L46g027231@turing-police.cc.vt.edu>
Date: Fri, 31 Jan 2003 15:05:17 +1030
To: Valdis.Kletnieks@vt.edu
From: Andrew Rutherford <andrewr@iagu.net>
Subject: Re: WG Review: Enhancements to Internet email to support diverse
 service environments (lemonade)
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:21 PM -0500 30/1/03, Valdis.Kletnieks@vt.edu wrote:

>Life sucks if the mail server 421's you when you don't have local storage.....

Agreed. :-) Hopefully the gateway in question has:

(1) Got the SMTP conversation up to DATA / 354 before giving off the
"beep" that everyone expects before leaving a message - preferably even
before playing the initial greeting, so 421's from load, etc, can be
caught as early as possible.

(2) Some form of "System error" message it can then play at the person
trying to leave the message.




From owner-ietf@ietf.org  Fri Jan 31 07:20:28 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04405;
	Fri, 31 Jan 2003 07:20:22 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eZrU-0000yJ-00
	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 07:01:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eZqS-0000w1-00
	for ietf@ran.ietf.org; Fri, 31 Jan 2003 07:00:33 -0500
Received: from ratree.psu.ac.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04132
	for <ietf@ietf.org>; Fri, 31 Jan 2003 06:56:45 -0500 (EST)
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 h0VBxX008193;
	Fri, 31 Jan 2003 18:59:34 +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 h0VBuqb20261;
	Fri, 31 Jan 2003 18:56:53 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Pete Resnick <presnick@qualcomm.com>
cc: ietf@ietf.org, Glenn Parsons <gparsons@nortelnetworks.com>,
        Eric Burger <eburger@snowshore.com>
Subject: Re: WG Review: Enhancements to Internet email to support diverse service environments (lemonade) 
In-Reply-To: <p0600010cba5dc6d587ee@[216.43.25.67]> 
References: <p0600010cba5dc6d587ee@[216.43.25.67]>  <200301282312.SAA11118@ietf.org> <7856.1043838807@munnari.OZ.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 31 Jan 2003 18:56:52 +0700
Message-ID: <20259.1044014212@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Wed, 29 Jan 2003 12:45:12 -0600
    From:        Pete Resnick <presnick@qualcomm.com>
    Message-ID:  <p0600010cba5dc6d587ee@[216.43.25.67]>

First, I have now seen that the draft charter I was commenting on was
not the correct one, but for the two things I was most concerned about,
there doesn't seem to be much difference of substance...

  | No, that's not what this means. Actually, it's probably just the 
  | opposite of what you fear.

OK.   That's much more reasonable.   Now, what is needed is for the
charter to actually say that, instead of implying that (one possible)
result would be to use IMAP as a streaming video source...

Perhaps rather that the rather specific (yet imprecise) "satisfy the
requirements for streaming playback of multimedia content" what it
should be saying is something more like "allow referrals to more
appropriate protocols for retrieval of content" (or something).

  | The solution is not known. The problem is that there is currently no 
  | standard mechanism for mail servers to announce the existence of new 
  | mail. Current protocols rely on polling or a constant connection to 
  | the mail server. The work item is to come up with a protocol that 
  | does notifications. Does the above not describe that work item 
  | appropriately?

It presumes that such a protocol is the answer to something, and can
necessarily be delivered.

This looks to me to be not unrelated (in some ways) to what the msgtrack
people were working on.

If all you really want is to formalise a (rational) method to implement
biff, then that's fine, but "message status information" might be much
more than that.   As written it suggests more like a way for servers to
let other servers know when messages have been delivered, read, ... (etc).

If "announce the existence of new mail" is really the objective here,
then how about something more like

	Provide a mechanism that allows mail arrival to be detected
	without requiring polling.

kre




From owner-ietf@ietf.org  Fri Jan 31 09:48:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08476;
	Fri, 31 Jan 2003 09:48:39 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ecQ3-0005DB-00
	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 09:45:27 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ePek-0000Ls-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 20:07:47 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15298;
	Thu, 30 Jan 2003 20:04:05 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18ePeO-0002n0-00; Thu, 30 Jan 2003 20:07:24 -0500
Date: Thu, 30 Jan 2003 20:07:24 -0500
From: John C Klensin <john@jck.com>
To: Randall Gellens <randy@qualcomm.com>, John C Klensin <john-ietf@jck.com>,
        "ned.freed@mrochek.com" <ned.freed@mrochek.com>,
        Pete Resnick <presnick@qualcomm.com>
cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>,
        "um@snowshore.com" <um@snowshore.com>
Subject: Re: WG Review: Enhancements to Internet email to support
   diverse service environments (lemonade)
Message-ID: <43117369.1043957244@p3.JCK.COM>
In-Reply-To: <a06000248ba5f4e3b144d@[129.46.74.134]>
References: <200301282312.SAA11118@ietf.org>
 <169878963.1043847608@p3.JCK.COM>
 <p0600010dba5dd6b34009@[216.43.25.67]>
 <175052472.1043852782@p3.JCK.COM>
 <p06000111ba5de5b9c58d@[216.43.25.67]>
 <01KRT49TEUKI002DEU@mauve.mrochek.com>
 <181950110.1043859679@p3.JCK.COM>
 <a06000248ba5f4e3b144d@[129.46.74.134]>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Thursday, 30 January, 2003 13:56 -0800 Randall Gellens 
<randy@qualcomm.com> wrote:

> This raises an interesting point that may be in danger of
> being obscured.  I think there is general agreement that IMAP
> is too complex.  However, concepts such as "IMAP lite" (or
> even "IMAP light"), simplification, pruning, etc. can be
> understood in very different ways.  It could mean simplifying
> interoperability by reducing options and eliminating permitted
> behavioral differences (especially among servers).  It could
> also mean taking out commands and responses.
>
> The former can be accomplished in an interoperable way; a new
> IMAP revision or capability could be defined which includes a
> number of previous options, and specifies varies behavioral
> aspects (along the lines of RFC 1123).  Clients written to
> previous versions of IMAP would be able to interoperate with a
> new server just fine.
>
> The latter, while making the protocol simpler and easier to
> understand and implement, risks being non-interoperable with
> previous versions.

This really isn't worth much discussion unless someone is really 
going to launch such an effort, but I don't see the distinction 
as clearly as you do.  We already have a situation in which some 
clients won't interoperate well with some servers because the 
clients think they need certain capabilities that those servers 
don't support.  And we have other server authors that have 
refused to implement certain features because they (the authors) 
are convinced those features are brain-damaged.  I'd like to see 
a WG give careful consideration to the question of the damage 
that would be done by pulling commands and replacing them with 
better/ cleaner designs as well as the type of revision I think 
you anticipate with the first case.

But, in the last analysis, IMAP4bis is still at Proposed.  Like 
you, I'd prefer something easier to implement and deploy that is 
fully compatible with IMAP4bis.  But, if that isn't possible, 
then I think it would be rational to consider other 
alternatives, with the understanding that some implementations 
would try to be conforming to both the older and newer versions 
and that it would be wise to design things so as to make that 
possible.

     john






From owner-ietf@ietf.org  Fri Jan 31 15:24:53 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17813;
	Fri, 31 Jan 2003 15:24:53 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ehd3-0006cy-00
	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 15:19:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ehcu-0006br-00
	for ietf@ran.ietf.org; Fri, 31 Jan 2003 15:19:04 -0500
Received: from numenor.qualcomm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17542
	for <ietf@ietf.org>; Fri, 31 Jan 2003 15:15:14 -0500 (EST)
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.12.3/8.12.5/1.0) with ESMTP id h0VKIh2d029128
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 31 Jan 2003 12:18:43 -0800 (PST)
Received: from [129.46.74.134] (loud.qualcomm.com [129.46.74.134])
	by crowley.qualcomm.com (8.12.3/8.12.5/1.0) with ESMTP id h0VKIZ5O001402;
	Fri, 31 Jan 2003 12:18:37 -0800 (PST)
Mime-Version: 1.0
Message-Id: <a06000257ba608a451751@[129.46.74.134]>
In-Reply-To: <20259.1044014212@munnari.OZ.AU>
References: <p0600010cba5dc6d587ee@[216.43.25.67]> 
 <200301282312.SAA11118@ietf.org> <7856.1043838807@munnari.OZ.AU>
 <20259.1044014212@munnari.OZ.AU>
X-Mailer: Eudora for Mac OS X v6.0a
Date: Fri, 31 Jan 2003 12:18:26 -0800
To: Robert Elz <kre@munnari.oz.au>, Pete Resnick <presnick@qualcomm.com>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: WG Review: Enhancements to Internet email to support
 diverse service environments (lemonade)
Cc: ietf@ietf.org, Glenn Parsons <gparsons@nortelnetworks.com>,
        Eric Burger <eburger@snowshore.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b25
Sender: owner-ietf@ietf.org
Precedence: bulk

At 6:56 PM +0700 1/31/03, Robert Elz wrote:

>  If all you really want is to formalise a (rational) method to implement
>  biff, then that's fine, but "message status information" might be much
>  more than that.   As written it suggests more like a way for servers to
>  let other servers know when messages have been delivered, read, ... (etc).

This is exactly what one proposal (SNAP) does: it allows one server 
to communicate status change events to another.
-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly-selected tag: ---------------
Quick!!  Act as if nothing has happened!



From owner-ietf@ietf.org  Fri Jan 31 16:11:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19059;
	Fri, 31 Jan 2003 16:11:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eiPS-0002O6-00
	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 16:09:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eiPH-0002Mu-00
	for ietf@ran.ietf.org; Fri, 31 Jan 2003 16:09:03 -0500
Received: from e33.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18907;
	Fri, 31 Jan 2003 16:05:12 -0500 (EST)
Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.194.24])
	by e33.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id h0VL8eE0048924;
	Fri, 31 Jan 2003 16:08:40 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.12.14])
	by westrelay03.boulder.ibm.com (8.12.3/NCO/VER6.5) with ESMTP id h0VL8cPc066686;
	Fri, 31 Jan 2003 14:08:39 -0700
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id h0VL6gt00339;
	Fri, 31 Jan 2003 16:06:43 -0500
Message-Id: <200301312106.h0VL6gt00339@rotala.raleigh.ibm.com>
To: John C Klensin <john-ietf@jck.com>
cc: Randy Bush <randy@psg.com>, RJ Atkinson <rja@extremenetworks.com>,
        Bob Braden <braden@ISI.EDU>, "ietf@ietf.org" <ietf@ietf.org>,
        "kireeti@juniper.net" <kireeti@juniper.net>,
        "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: "IETF consensus" in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ] 
In-Reply-To: Message from john-ietf@jck.com
   of "Thu, 30 Jan 2003 16:39:12 EST." <30625166.1043944752@p3.JCK.COM> 
Date: Fri, 31 Jan 2003 16:06:42 -0500
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> Absolutely.  Otherwise, this discussion wouldn't be worth the 
> trouble.  But, if you are going to define "IETF Consensus" as 
> "Publication as an RFC" then

Since I don't seem to be able to make this clear enough, once again, I
do not and have never intended "IETF Consensus", in the literal sense,
to be defined as "Publication as an RFC". We all know that the two are
not the same. That term was used as a shorthand way in RFC 2434 to
indicate RFC publication was required.

If I could go back in time, I would leave the defintion as it is, but
give it a different name. I probably wouldn't have tried to define
"IETF Consensus" at all, as I'm not sure how that would be done in a
way that encompasses both standards track and non-standards track
documents (or that such a definition would even be useful).

> 	- We don't need the added term to add confusion.
> 	
> 	- We open up a loophole case in which a document comes
> 	to the RFC Editor, then to the IESG.  The IESG decides
> 	it is a bad idea, and puts a disclaimer on it that says
> 	"this is a terrible idea".  The RFC Editor decides to
> 	publish it anyway.  We now have an RFC that, regardless
> 	of its other properties, clearly does not represent IESG
> 	consensus that it is a good idea.  But whatever it calls
> 	for is eligible for registration.

What this points out is that the relationship between IESG review,
IANA assignments and RFC editor independence is both complex and
subtle. Not suprisingly, it has evolved over time in a way that no
longer matches the exact words in (say) 2026. A literal intepretation
of some of these words could easily lead us into situations that we
probably don't want to be in.  I agree that it would be good to
clarify and update the written words.

Thomas	



From owner-ietf@ietf.org  Fri Jan 31 17:13:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20419;
	Fri, 31 Jan 2003 17:13:16 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ejMT-0006hp-00
	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 17:10:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ejLl-0006fq-00
	for ietf@ran.ietf.org; Fri, 31 Jan 2003 17:09:29 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20244
	for <IETF@ietf.org>; Fri, 31 Jan 2003 17:05:38 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id OAA32376
	for <IETF@ietf.org>; Fri, 31 Jan 2003 14:08:55 -0800
Date: Fri, 31 Jan 2003 14:09:09 -0800
From: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <41628837320.20030131140909@brandenburg.com>
To: IETF@ietf.org
Subject: "Written patent policy with clear guidance"
In-Reply-To: <0DC042C355EBD6118C5600105A5B9AD224526D@PANTEMERGENCY>
References: <0DC042C355EBD6118C5600105A5B9AD224526D@PANTEMERGENCY>
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,

Norm Beamer is a partner at Fish & Neave, which specializes in
intellectual property law.  They did the patent for the Wright Brothers.

I am forwarding his note at his request. This is not intended to state a
concern that the IETF's current efforts regarding intellectual property
are inadequate -- my non-expert guess is that we currently have pretty
good policies and communicate them well.

However it seems worthwhile to take note of a case and a warning that an
expert thinks is relevant to us.

d/
----- 
 Dave <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 t +1.408.246.8253; f +1.408.850.1850

 
==============Forwarded message===============
From: Beamer, Norman H. <NBeamer@fishneave.com>
To: "Dave Crocker (E-mail)" <dcrocker@brandenburg.com>
Date: Friday, January 31, 2003, 12:25:11 PM


I suggest you pass this on to IETF colleagues   

On Wednesday, the Court of Appeals of the Federal Circuit ruled that
Rambus did not commit fraud when it was filing patents while Rambus
employees where on a standards committee for high speed memory chips.
Rmabus will be seeking $840 million in royalties from companies such
as Infineon, Hynix (which last I heard had no money) and Micron 
(Rambus collects a 3% royalty for its chip, and this chip market is
a $28 billion industry, resulting in the 840 figure). On this news,
Rambus stock rose 57%, or 4.25, to 11.69 dollars a share.

To me there is a blunt message in the decision: that it is time that
all engineering standards committees mature in their handling of patent
issues.  The stakes are ever increasing with these standards, and
everyone knows that everyone is playing patent games.  Any committee
with less than clear and explicit rules about disclosure for patent
activities by committee members should not whine later on.  In the eyes
of the CAFC, the committee that Rambus employees was on didn't clearly
define the rules, so that Rambus' actions were not sanctionable.  For
example, in the ruling, we see language such as:

    "In this case there is a staggering lack of defining details
    in the ... patent policy" ..... "When competitors participate
    in an open standards committee, their work necessitates a
    written patent policy with clear guidance on the committee's
    intellectual property position."

===========End of original message text===========




From owner-ietf@ietf.org  Fri Jan 31 17:32:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20716;
	Fri, 31 Jan 2003 17:32:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ejhl-0007T4-00
	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 17:32:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ejh9-0007Rv-00
	for ietf@ran.ietf.org; Fri, 31 Jan 2003 17:31:35 -0500
Received: from mail-blue.research.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20664
	for <IETF@ietf.org>; Fri, 31 Jan 2003 17:27:43 -0500 (EST)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 41BB94CE24; Fri, 31 Jan 2003 17:31:17 -0500 (EST)
Received: from berkshire.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id RAA18467;
	Fri, 31 Jan 2003 17:31:16 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id CBC797B4D; Fri, 31 Jan 2003 17:31:15 -0500 (EST)
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: IETF@ietf.org
Subject: Re: "Written patent policy with clear guidance" 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 31 Jan 2003 17:31:15 -0500
Message-Id: <20030131223115.CBC797B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <41628837320.20030131140909@brandenburg.com>, Dave Crocker writes:
>Folks,
>
>Norm Beamer is a partner at Fish & Neave, which specializes in
>intellectual property law.  They did the patent for the Wright Brothers.
>
>I am forwarding his note at his request. This is not intended to state a
>concern that the IETF's current efforts regarding intellectual property
>are inadequate -- my non-expert guess is that we currently have pretty
>good policies and communicate them well.
>
>However it seems worthwhile to take note of a case and a warning that an
>expert thinks is relevant to us.

Thanks.  This case has already been mentioned on the IPR wg's mailing 
list.  I do feel that our requirements are explicit now; we're making 
sure that they're clear enough in IPR.

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





From owner-ietf@ietf.org  Fri Jan 31 20:28:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24403;
	Fri, 31 Jan 2003 20:28:38 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18emOD-0003xP-00
	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 20:24:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18emNz-0003wI-00
	for ietf@ran.ietf.org; Fri, 31 Jan 2003 20:23:59 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24308
	for <IETF@ietf.org>; Fri, 31 Jan 2003 20:20:07 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id RAA08498;
	Fri, 31 Jan 2003 17:23:08 -0800
Date: Fri, 31 Jan 2003 17:02:25 -0800
From: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <98639233839.20030131170225@brandenburg.com>
To: "Steven M. Bellovin" <smb@research.att.com>
CC: IETF@ietf.org
Subject: Re: "Written patent policy with clear guidance"
In-Reply-To: <20030131223115.CBC797B4D@berkshire.research.att.com>
References: <20030131223115.CBC797B4D@berkshire.research.att.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

Steven,


SMB> Thanks.  This case has already been mentioned on the IPR wg's mailing
SMB> list.

excellent. thanks.

alas, so many wgs, so little time...

d/
-- 
 Dave <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 t +1.408.246.8253; f +1.408.850.1850




