From owner-ietf-outbound  Mon Jan  3 04:14:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA28303
	for ietf-outbound.10@ietf.org; Mon, 3 Jan 2000 04:10:01 -0500 (EST)
Received: from ban-server.banyan.tenet.res.in (banyan.tenet.res.in [206.103.12.155])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28279
	for <ietf@ietf.org>; Mon, 3 Jan 2000 04:08:11 -0500 (EST)
Received: from localhost (minti@localhost) by ban-server.banyan.tenet.res.in (8.8.7/8.8.3) with SMTP id OAA25738 for <ietf@ietf.org>; Mon, 3 Jan 2000 14:12:37 +0530
Date: Mon, 3 Jan 2000 14:12:37 +0530 (IST)
From: Minti <minti@banyanNetworks.com>
To: ietf@ietf.org
Subject: Clarification regarding RFC 1406 and RFC 2495 
Message-ID: <Pine.LNX.3.96.1000103141219.25591A-100000@ban-server.banyan.tenet.res.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



Hello,

I am currently responsible for maintaining the E1 MIB as part of a
module I am working on.
With respect to this, I needed the current status of RFC 2495(dated Jan
'99) - it has been listed as a proposed standard, while RFC 1406 is an
Internet standard (dated Jan '93). 
Which RFC should I follow for my implementation?

I would really appreciate any help in this regard.
Thanks,
Minti







From owner-ietf-outbound@ietf.org  Mon Jan  3 04:18:16 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28372
	for <ietf-web-archive@odin.ietf.org>; Mon, 3 Jan 2000 04:18:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id EAA24687;
	Mon, 3 Jan 2000 04:17:09 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id EAA28303
	for ietf-outbound.10@ietf.org; Mon, 3 Jan 2000 04:10:01 -0500 (EST)
Received: from ban-server.banyan.tenet.res.in (banyan.tenet.res.in [206.103.12.155])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28279
	for <ietf@ietf.org>; Mon, 3 Jan 2000 04:08:11 -0500 (EST)
Received: from localhost (minti@localhost) by ban-server.banyan.tenet.res.in (8.8.7/8.8.3) with SMTP id OAA25738 for <ietf@ietf.org>; Mon, 3 Jan 2000 14:12:37 +0530
Date: Mon, 3 Jan 2000 14:12:37 +0530 (IST)
From: Minti <minti@banyanNetworks.com>
To: ietf@ietf.org
Subject: Clarification regarding RFC 1406 and RFC 2495 
Message-ID: <Pine.LNX.3.96.1000103141219.25591A-100000@ban-server.banyan.tenet.res.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



Hello,

I am currently responsible for maintaining the E1 MIB as part of a
module I am working on.
With respect to this, I needed the current status of RFC 2495(dated Jan
'99) - it has been listed as a proposed standard, while RFC 1406 is an
Internet standard (dated Jan '93). 
Which RFC should I follow for my implementation?

I would really appreciate any help in this regard.
Thanks,
Minti







From owner-ietf-outbound  Mon Jan  3 05:21:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA28708
	for ietf-outbound.10@ietf.org; Mon, 3 Jan 2000 05:20:02 -0500 (EST)
Received: from e33.esmtp.ibm.com (e33.co.us.ibm.com [32.97.110.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28640
	for <ietf@ietf.org>; Mon, 3 Jan 2000 05:13:50 -0500 (EST)
Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.99.132.206])
	by e33.esmtp.ibm.com (8.9.3/8.9.3) with ESMTP id EAA18614
	for <ietf@ietf.org>; Mon, 3 Jan 2000 04:05:57 -0600
Received: from BLDVMA.boulder.ibm.com (bldvma.boulder.ibm.com [9.99.64.30])
	by westrelay03.boulder.ibm.com (8.8.8m2/NCO v2.06) with SMTP id DAA198208
	for <ietf%ietf.org@relay.us.ibm.com>; Mon, 3 Jan 2000 03:13:49 -0700
Message-Id: <200001031013.DAA198208@westrelay03.boulder.ibm.com>
Received:  by BLDVMA.boulder.ibm.com (IBM VM SMTP Level 310) via spool with SMTP id 4339 ; Mon, 03 Jan 2000 03:12:43 MST
Date: Mon, 3 Jan 00 11:13:55 CET
From: "Bert Wijnen" <WIJNEN@vnet.ibm.com>
To: minti@banyanNetworks.com, ietf@ietf.org
Subject: Clarification regarding RFC 1406 and RFC 2495

Ref:  Your note of Mon, 3 Jan 2000 14:12:37 +0530 (IST)

Subject: Re:   Clarification regarding RFC 1406 and RFC 2495

Minti writes/asks:
>
> I am currently responsible for maintaining the E1 MIB as part of a
> module I am working on.
> With respect to this, I needed the current status of RFC 2495(dated Jan
> '99) - it has been listed as a proposed standard, while RFC 1406 is an
> Internet standard (dated Jan '93).
> Which RFC should I follow for my implementation?
>
Mmmm... what makes you think that RFC1406 was at a more advanced
standards level than RFC2495? The rfc-index.txt file states:

1406 Definitions of Managed Objects for the DS1 and E1 Interface
     Types. F. Baker, J. Watt, Editors. January 1993. (Format: TXT=97559
     bytes) (Obsoletes RFC1232) (Obsoleted by RFC2495) (Status: PROPOSED
     STANDARD)

2495 Definitions of Managed Objects for the DS1, E1, DS2 and E2
     Interface Types. D. Fowler, Ed. January 1999. (Format: TXT=155560
     bytes) (Obsoletes RFC1406) (Status: PROPOSED STANDARD)

So they both made it to Proposed Standard and not yet any further.
The second edition was recycled at proposed I assume because the
authors/editors and implementers found some problems and needed to
make some changes that prevented the MIB to advance to the next
level on the stadards track. You can actully see in section 1.1
what sort of changes were made and that caused the doc to recycle
at proposed.

You should implement RFC2495 if you want to claim compliance with the
current Proposed Standard in this area.

Hope this helps,
Bert



From owner-ietf-outbound@ietf.org  Mon Jan  3 05:22:49 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28755
	for <ietf-web-archive@odin.ietf.org>; Mon, 3 Jan 2000 05:22:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id FAA13351;
	Mon, 3 Jan 2000 05:21:43 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id FAA28708
	for ietf-outbound.10@ietf.org; Mon, 3 Jan 2000 05:20:02 -0500 (EST)
Received: from e33.esmtp.ibm.com (e33.co.us.ibm.com [32.97.110.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28640
	for <ietf@ietf.org>; Mon, 3 Jan 2000 05:13:50 -0500 (EST)
Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.99.132.206])
	by e33.esmtp.ibm.com (8.9.3/8.9.3) with ESMTP id EAA18614
	for <ietf@ietf.org>; Mon, 3 Jan 2000 04:05:57 -0600
Received: from BLDVMA.boulder.ibm.com (bldvma.boulder.ibm.com [9.99.64.30])
	by westrelay03.boulder.ibm.com (8.8.8m2/NCO v2.06) with SMTP id DAA198208
	for <ietf%ietf.org@relay.us.ibm.com>; Mon, 3 Jan 2000 03:13:49 -0700
Message-Id: <200001031013.DAA198208@westrelay03.boulder.ibm.com>
Received:  by BLDVMA.boulder.ibm.com (IBM VM SMTP Level 310) via spool with SMTP id 4339 ; Mon, 03 Jan 2000 03:12:43 MST
Date: Mon, 3 Jan 00 11:13:55 CET
From: "Bert Wijnen" <WIJNEN@vnet.ibm.com>
To: minti@banyanNetworks.com, ietf@ietf.org
Subject: Clarification regarding RFC 1406 and RFC 2495

Ref:  Your note of Mon, 3 Jan 2000 14:12:37 +0530 (IST)

Subject: Re:   Clarification regarding RFC 1406 and RFC 2495

Minti writes/asks:
>
> I am currently responsible for maintaining the E1 MIB as part of a
> module I am working on.
> With respect to this, I needed the current status of RFC 2495(dated Jan
> '99) - it has been listed as a proposed standard, while RFC 1406 is an
> Internet standard (dated Jan '93).
> Which RFC should I follow for my implementation?
>
Mmmm... what makes you think that RFC1406 was at a more advanced
standards level than RFC2495? The rfc-index.txt file states:

1406 Definitions of Managed Objects for the DS1 and E1 Interface
     Types. F. Baker, J. Watt, Editors. January 1993. (Format: TXT=97559
     bytes) (Obsoletes RFC1232) (Obsoleted by RFC2495) (Status: PROPOSED
     STANDARD)

2495 Definitions of Managed Objects for the DS1, E1, DS2 and E2
     Interface Types. D. Fowler, Ed. January 1999. (Format: TXT=155560
     bytes) (Obsoletes RFC1406) (Status: PROPOSED STANDARD)

So they both made it to Proposed Standard and not yet any further.
The second edition was recycled at proposed I assume because the
authors/editors and implementers found some problems and needed to
make some changes that prevented the MIB to advance to the next
level on the stadards track. You can actully see in section 1.1
what sort of changes were made and that caused the doc to recycle
at proposed.

You should implement RFC2495 if you want to claim compliance with the
current Proposed Standard in this area.

Hope this helps,
Bert



From owner-ietf-outbound  Mon Jan  3 08:31:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA00144
	for ietf-outbound.10@ietf.org; Mon, 3 Jan 2000 08:30:02 -0500 (EST)
Received: from sdp.ee.tsinghua.edu.cn (sdp.ee.tsinghua.edu.cn [166.111.64.222])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00033
	for <ietf@ietf.org>; Mon, 3 Jan 2000 08:22:35 -0500 (EST)
Received: from Zhengyq ([166.111.64.236]) by sdp.ee.tsinghua.edu.cn
          (Netscape Mail Server v2.02) with SMTP id AAA203
          for <ietf@ietf.org>; Mon, 3 Jan 2000 21:32:27 +0800
Message-ID: <000b01bf55ed$ed55da60$ec406fa6@Zhengyq.sdt>
From: zhengyq@sdp.ee.tsinghua.edu.cn (Zheng Youquan)
To: <ietf@ietf.org>
Subject: Who can give me the document of IEEE802.lp ?
Date: Mon, 3 Jan 2000 21:24:55 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0008_01BF5630.FAEB3240"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

This is a multi-part message in MIME format.

------=_NextPart_000_0008_01BF5630.FAEB3240
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

It seems like a QoS standard, who can give me some documents about it?
Thank you very much!

------=_NextPart_000_0008_01BF5630.FAEB3240
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Dgb2312 http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#fff8f0>
<DIV><FONT color=3D#000000 size=3D2>It seems like a QoS standard, who =
can give me=20
some documents about it?</FONT></DIV>
<DIV><FONT size=3D2>Thank you very much!</FONT></DIV></BODY></HTML>

------=_NextPart_000_0008_01BF5630.FAEB3240--



From owner-ietf-outbound@ietf.org  Mon Jan  3 08:34:09 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00307
	for <ietf-web-archive@odin.ietf.org>; Mon, 3 Jan 2000 08:34:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id IAA06806;
	Mon, 3 Jan 2000 08:32:48 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA00144
	for ietf-outbound.10@ietf.org; Mon, 3 Jan 2000 08:30:02 -0500 (EST)
Received: from sdp.ee.tsinghua.edu.cn (sdp.ee.tsinghua.edu.cn [166.111.64.222])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00033
	for <ietf@ietf.org>; Mon, 3 Jan 2000 08:22:35 -0500 (EST)
Received: from Zhengyq ([166.111.64.236]) by sdp.ee.tsinghua.edu.cn
          (Netscape Mail Server v2.02) with SMTP id AAA203
          for <ietf@ietf.org>; Mon, 3 Jan 2000 21:32:27 +0800
Message-ID: <000b01bf55ed$ed55da60$ec406fa6@Zhengyq.sdt>
From: zhengyq@sdp.ee.tsinghua.edu.cn (Zheng Youquan)
To: <ietf@ietf.org>
Subject: Who can give me the document of IEEE802.lp ?
Date: Mon, 3 Jan 2000 21:24:55 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0008_01BF5630.FAEB3240"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

This is a multi-part message in MIME format.

------=_NextPart_000_0008_01BF5630.FAEB3240
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

It seems like a QoS standard, who can give me some documents about it?
Thank you very much!

------=_NextPart_000_0008_01BF5630.FAEB3240
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Dgb2312 http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#fff8f0>
<DIV><FONT color=3D#000000 size=3D2>It seems like a QoS standard, who =
can give me=20
some documents about it?</FONT></DIV>
<DIV><FONT size=3D2>Thank you very much!</FONT></DIV></BODY></HTML>

------=_NextPart_000_0008_01BF5630.FAEB3240--



From owner-ietf-outbound  Mon Jan  3 10:01:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02110
	for ietf-outbound.10@ietf.org; Mon, 3 Jan 2000 10:00:02 -0500 (EST)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01777
	for <ietf@ietf.org>; Mon, 3 Jan 2000 09:50:17 -0500 (EST)
Received: from alden (alden.maxware.no [10.128.1.21])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id PAA14052;
	Mon, 3 Jan 2000 15:50:06 +0100
Message-Id: <4.2.0.58.20000103154629.039ce7f0@dokka.maxware.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 03 Jan 2000 15:47:08 +0100
To: zhengyq@sdp.ee.tsinghua.edu.cn (Zheng Youquan), <ietf@ietf.org>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: Who can give me the document of IEEE802.lp ?
In-Reply-To: <000b01bf55ed$ed55da60$ec406fa6@Zhengyq.sdt>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 21:24 03.01.00 +0800, Zheng Youquan wrote:
>It seems like a QoS standard, who can give me some documents about it?
>Thank you very much!

try 
http://shop.ieee.org/store/results.asp?mscssid=AK3X4BHNQRSH2HJA000UMU56107V0 
6N2&CID_LDAP=&BUYER_TYPE=&account_type=&member_grade=&hftype=&AUTH=

or rather - just start at http://www.ieee.org/ - this is the definitive 
place to start when searching for info on IEEE standards.

                           Harald A

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound@ietf.org  Mon Jan  3 10:02:48 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02241
	for <ietf-web-archive@odin.ietf.org>; Mon, 3 Jan 2000 10:02:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id KAA25569;
	Mon, 3 Jan 2000 10:01:39 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02110
	for ietf-outbound.10@ietf.org; Mon, 3 Jan 2000 10:00:02 -0500 (EST)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01777
	for <ietf@ietf.org>; Mon, 3 Jan 2000 09:50:17 -0500 (EST)
Received: from alden (alden.maxware.no [10.128.1.21])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id PAA14052;
	Mon, 3 Jan 2000 15:50:06 +0100
Message-Id: <4.2.0.58.20000103154629.039ce7f0@dokka.maxware.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 03 Jan 2000 15:47:08 +0100
To: zhengyq@sdp.ee.tsinghua.edu.cn (Zheng Youquan), <ietf@ietf.org>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: Who can give me the document of IEEE802.lp ?
In-Reply-To: <000b01bf55ed$ed55da60$ec406fa6@Zhengyq.sdt>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 21:24 03.01.00 +0800, Zheng Youquan wrote:
>It seems like a QoS standard, who can give me some documents about it?
>Thank you very much!

try 
http://shop.ieee.org/store/results.asp?mscssid=AK3X4BHNQRSH2HJA000UMU56107V0 
6N2&CID_LDAP=&BUYER_TYPE=&account_type=&member_grade=&hftype=&AUTH=

or rather - just start at http://www.ieee.org/ - this is the definitive 
place to start when searching for info on IEEE standards.

                           Harald A

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Mon Jan  3 15:43:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA07290
	for ietf-outbound.10@ietf.org; Mon, 3 Jan 2000 15:40:02 -0500 (EST)
Received: from sentry (firewall-user@sentry.gw.tislabs.com [192.94.214.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07156
	for <ietf@ietf.org>; Mon, 3 Jan 2000 15:34:59 -0500 (EST)
Received: by sentry; id PAA28436; Mon, 3 Jan 2000 15:36:09 -0500 (EST)
Received: from clipper.gw.tislabs.com(10.33.1.2) by sentry.gw.tislabs.com via smap (V5.5)
	id xma028427; Mon, 3 Jan 00 15:35:24 -0500
Received: (from balenson@localhost)
	by clipper.gw.tislabs.com (8.9.3/8.9.1) id PAA00873
	for ietf@ietf.org; Mon, 3 Jan 2000 15:34:09 -0500 (EST)
Date: Mon, 3 Jan 2000 15:34:09 -0500 (EST)
From: "David M. Balenson" <balenson@tislabs.com>
Message-Id: <200001032034.PAA00873@clipper.gw.tislabs.com>
To: ietf@ietf.org
Subject: Jan. 6th early registration deadline for ISOC Netw. & Distr. Sys. Security Symp. (NDSS 2000)


S A V E   $ 7 0   O F F   R E G I S T R A T I O N   F E E ! !
R E G I S T E R   B Y   J A N U A R Y   6 ,   2 0 0 0 

THE INTERNET SOCIETY'S
Year 2000 NETWORK AND DISTRIBUTED SYSTEM SECURITY (NDSS) SYMPOSIUM
February 2-4, 2000
Catamaran Resort Hotel, San Diego, California
General Chair:   Steve Welke, Trusted Computer Solutions
Program Chairs:  Gene Tsudik, USC/Information Sciences Institute
		 Avi Rubin, AT&T Labs - Research

ONLINE INFORMATION AND REGISTRATION:  http://www.isoc.org/ndss2000
EARLY REGISTRATION DISCOUNT DEADLINE:  January 6, 2000

The 7th annual NDSS Symposium brings together researchers,
implementers, and users of network and distributed system security
technologies to discuss today's important security issues and
challenges.  The Symposium provides a mix of technical papers and
panel presentations that describe promising new approaches to
security problems that are practical and, to the extent possible,
have been implemented.  NDSS fosters the exchange of technical
information and encourages the Internet community to deploy available
security technologies and develop new solutions to unsolved problems.

KEYNOTE SPEAKER: Gene Spafford, Professor of Computer Sciences at
Purdue University, an expert in information security, computer crime
investigation and information ethics.  Spaf (as he is known to his
friends, colleagues, and students) is director of the Purdue CERIAS
(Center for Education and Research in Information Assurance and
Security), and was the founder and director of the (now superseded)
COAST Laboratory. 

THIS YEAR'S TOPICS INCLUDE:
- Automated Detection of Buffer Overrun Vulnerabilities
- User-Level Infrastructure for System Call Interposition
- Optimized Group Rekey for Group Communication Systems
- IPSec-based Host Architecture for Secure  Internet Multicast
- The Economics of Security
- Automatic Generation of Security Protocols
- Security Protocols for SPKI-based Delegation Systems
- Secure Border Gateway Protocol (S-BGP)
- Analysis of a Fair Exchange Protocol
- Secure Password-Based Protocols for TLS
- Chameleon Signatures
- Lightweight Tool for Detecting Web Server Attacks
- Adaptive and Agile Applications Using Intrusion Detection
- Secure Virtual Enclaves
- Encrypted rlogin Connections Created With Kerberos IV
- Accountability and Control of Process Creation in Metasystems
- Red Teaming and Network Security

PRE-CONFERENCE TECHNICAL TUTORIALS:
- Network Security Protocol Standards, Dr. Stephen T. Kent
- Deployed and Emerging Security Systems for the Internet, Dr. Radia
  Perlman and Charlie Kaufman
- Mobile Code Security and Java 2 Architecture, Dr. Gary McGraw
- Cryptography 101, Dr. Aviel D. Rubin
- Public Key Infrastructure - The Truth and How to Find It, Dr. Daniel
  E. Geer, Jr.
- An Introduction to Intrusion Detection Technology, Mr. Mark Wood 

FOR MORE INFORMATION contact the Internet Society:
  Internet Society, 11150 Sunset Hills Road, Reston, VA, 20190 USA
  Phone: +1-703-326-9880         Fax: +1-703-326-9881
  E-mail: ndss2000reg@isoc.org   URL: http://www.isoc.org/ndss2000/

SPONSORSHIP OPPORTUNITIES AVAILABLE!  Take advantage of this high
visibility event.  Contact Carla Rosenfeld at the Internet Society
at +1-703-326-9880 or send e-mail to carla@isoc.org.

THE INTERNET SOCIETY is a non-governmental organization for global
cooperation and coordination for the Internet and its
internetworking technologies and applications.



From owner-ietf-outbound@ietf.org  Mon Jan  3 15:46:10 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07494
	for <ietf-web-archive@odin.ietf.org>; Mon, 3 Jan 2000 15:46:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id PAA27680;
	Mon, 3 Jan 2000 15:45:08 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA07290
	for ietf-outbound.10@ietf.org; Mon, 3 Jan 2000 15:40:02 -0500 (EST)
Received: from sentry (firewall-user@sentry.gw.tislabs.com [192.94.214.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07156
	for <ietf@ietf.org>; Mon, 3 Jan 2000 15:34:59 -0500 (EST)
Received: by sentry; id PAA28436; Mon, 3 Jan 2000 15:36:09 -0500 (EST)
Received: from clipper.gw.tislabs.com(10.33.1.2) by sentry.gw.tislabs.com via smap (V5.5)
	id xma028427; Mon, 3 Jan 00 15:35:24 -0500
Received: (from balenson@localhost)
	by clipper.gw.tislabs.com (8.9.3/8.9.1) id PAA00873
	for ietf@ietf.org; Mon, 3 Jan 2000 15:34:09 -0500 (EST)
Date: Mon, 3 Jan 2000 15:34:09 -0500 (EST)
From: "David M. Balenson" <balenson@tislabs.com>
Message-Id: <200001032034.PAA00873@clipper.gw.tislabs.com>
To: ietf@ietf.org
Subject: Jan. 6th early registration deadline for ISOC Netw. & Distr. Sys. Security Symp. (NDSS 2000)


S A V E   $ 7 0   O F F   R E G I S T R A T I O N   F E E ! !
R E G I S T E R   B Y   J A N U A R Y   6 ,   2 0 0 0 

THE INTERNET SOCIETY'S
Year 2000 NETWORK AND DISTRIBUTED SYSTEM SECURITY (NDSS) SYMPOSIUM
February 2-4, 2000
Catamaran Resort Hotel, San Diego, California
General Chair:   Steve Welke, Trusted Computer Solutions
Program Chairs:  Gene Tsudik, USC/Information Sciences Institute
		 Avi Rubin, AT&T Labs - Research

ONLINE INFORMATION AND REGISTRATION:  http://www.isoc.org/ndss2000
EARLY REGISTRATION DISCOUNT DEADLINE:  January 6, 2000

The 7th annual NDSS Symposium brings together researchers,
implementers, and users of network and distributed system security
technologies to discuss today's important security issues and
challenges.  The Symposium provides a mix of technical papers and
panel presentations that describe promising new approaches to
security problems that are practical and, to the extent possible,
have been implemented.  NDSS fosters the exchange of technical
information and encourages the Internet community to deploy available
security technologies and develop new solutions to unsolved problems.

KEYNOTE SPEAKER: Gene Spafford, Professor of Computer Sciences at
Purdue University, an expert in information security, computer crime
investigation and information ethics.  Spaf (as he is known to his
friends, colleagues, and students) is director of the Purdue CERIAS
(Center for Education and Research in Information Assurance and
Security), and was the founder and director of the (now superseded)
COAST Laboratory. 

THIS YEAR'S TOPICS INCLUDE:
- Automated Detection of Buffer Overrun Vulnerabilities
- User-Level Infrastructure for System Call Interposition
- Optimized Group Rekey for Group Communication Systems
- IPSec-based Host Architecture for Secure  Internet Multicast
- The Economics of Security
- Automatic Generation of Security Protocols
- Security Protocols for SPKI-based Delegation Systems
- Secure Border Gateway Protocol (S-BGP)
- Analysis of a Fair Exchange Protocol
- Secure Password-Based Protocols for TLS
- Chameleon Signatures
- Lightweight Tool for Detecting Web Server Attacks
- Adaptive and Agile Applications Using Intrusion Detection
- Secure Virtual Enclaves
- Encrypted rlogin Connections Created With Kerberos IV
- Accountability and Control of Process Creation in Metasystems
- Red Teaming and Network Security

PRE-CONFERENCE TECHNICAL TUTORIALS:
- Network Security Protocol Standards, Dr. Stephen T. Kent
- Deployed and Emerging Security Systems for the Internet, Dr. Radia
  Perlman and Charlie Kaufman
- Mobile Code Security and Java 2 Architecture, Dr. Gary McGraw
- Cryptography 101, Dr. Aviel D. Rubin
- Public Key Infrastructure - The Truth and How to Find It, Dr. Daniel
  E. Geer, Jr.
- An Introduction to Intrusion Detection Technology, Mr. Mark Wood 

FOR MORE INFORMATION contact the Internet Society:
  Internet Society, 11150 Sunset Hills Road, Reston, VA, 20190 USA
  Phone: +1-703-326-9880         Fax: +1-703-326-9881
  E-mail: ndss2000reg@isoc.org   URL: http://www.isoc.org/ndss2000/

SPONSORSHIP OPPORTUNITIES AVAILABLE!  Take advantage of this high
visibility event.  Contact Carla Rosenfeld at the Internet Society
at +1-703-326-9880 or send e-mail to carla@isoc.org.

THE INTERNET SOCIETY is a non-governmental organization for global
cooperation and coordination for the Internet and its
internetworking technologies and applications.



From owner-ietf-outbound  Mon Jan  3 18:21:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA08867
	for ietf-outbound.10@ietf.org; Mon, 3 Jan 2000 18:20:02 -0500 (EST)
Received: from mobile.webweaving.org (d4.NL.EU.net [193.242.91.68])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08768
	for <ietf@ietf.org>; Mon, 3 Jan 2000 18:11:41 -0500 (EST)
Received: (from dirkx@localhost)
	by mobile.webweaving.org (8.9.3/8.9.3) id XAA01371;
	Mon, 3 Jan 2000 23:53:04 +0100 (CET)
	(envelope-from dirkx)
Date: Mon, 3 Jan 2000 23:53:04 +0100 (CET)
From: Dirk-Willem van Gulik <dirkx@WEBWEAVING.ORG>
To: Zheng Youquan <zhengyq@sdp.ee.tsinghua.edu.cn>
cc: ietf@ietf.org
Subject: Re: Who can give me the document of IEEE802.lp ?
In-Reply-To: <000b01bf55ed$ed55da60$ec406fa6@Zhengyq.sdt>
Message-ID: <Pine.BSF.4.10.10001032351450.1347-100000@mobile.webweaving.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 3 Jan 2000, Zheng Youquan wrote:

> It seems like a QoS standard, who can give me some documents about it?
> Thank you very much!

http://www.ieee.org and simply do a search. Unless I am very mistaken,
from previous contacts with someone at your institution I recall that
your library has a substancial subset of the documents.

Dw



From owner-ietf-outbound@ietf.org  Mon Jan  3 18:23:56 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08916
	for <ietf-web-archive@odin.ietf.org>; Mon, 3 Jan 2000 18:23:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id SAA00160;
	Mon, 3 Jan 2000 18:22:55 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id SAA08867
	for ietf-outbound.10@ietf.org; Mon, 3 Jan 2000 18:20:02 -0500 (EST)
Received: from mobile.webweaving.org (d4.NL.EU.net [193.242.91.68])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08768
	for <ietf@ietf.org>; Mon, 3 Jan 2000 18:11:41 -0500 (EST)
Received: (from dirkx@localhost)
	by mobile.webweaving.org (8.9.3/8.9.3) id XAA01371;
	Mon, 3 Jan 2000 23:53:04 +0100 (CET)
	(envelope-from dirkx)
Date: Mon, 3 Jan 2000 23:53:04 +0100 (CET)
From: Dirk-Willem van Gulik <dirkx@WEBWEAVING.ORG>
To: Zheng Youquan <zhengyq@sdp.ee.tsinghua.edu.cn>
cc: ietf@ietf.org
Subject: Re: Who can give me the document of IEEE802.lp ?
In-Reply-To: <000b01bf55ed$ed55da60$ec406fa6@Zhengyq.sdt>
Message-ID: <Pine.BSF.4.10.10001032351450.1347-100000@mobile.webweaving.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 3 Jan 2000, Zheng Youquan wrote:

> It seems like a QoS standard, who can give me some documents about it?
> Thank you very much!

http://www.ieee.org and simply do a search. Unless I am very mistaken,
from previous contacts with someone at your institution I recall that
your library has a substancial subset of the documents.

Dw



From owner-ietf-outbound  Tue Jan  4 12:31:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA02858
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 12:30:02 -0500 (EST)
Received: from chiark.greenend.org.uk (mail@chiark.greenend.org.uk [195.224.76.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02693;
	Tue, 4 Jan 2000 12:21:55 -0500 (EST)
Received: from ijackson by chiark.greenend.org.uk with local (Exim 2.05 #1)
	id 125Xea-00064D-00 (Debian); Tue, 4 Jan 2000 17:21:52 +0000
From: Ian Jackson <ijackson@chiark.greenend.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14450.11312.813608.730985@chiark.greenend.org.uk>
Date: Tue, 4 Jan 2000 17:21:52 +0000 (GMT)
To: iesg@ietf.org
Cc: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to
	 Informational
Newsgroups: chiark.mail.ietf.announce
In-Reply-To: <199912301922.OAA03462@ietf.org>
References: <199912301922.OAA03462@ietf.org>
X-Mailer: VM 6.62 under Emacs 19.34.1
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The IESG writes ("Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 	 Informational"):
> 
> The IESG has received a request to consider Registry Registrar Protocol
> (RRP) Version 1.1.0 <draft-hollenbeck-rrp-00.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 January 13, 2000.

I can see at least the following problems with this protocol, in
addition to those described in it:

* The TRANSFER command, when used to approve a transfer, does not
specify to which registrar the domain is to be transferred.  The
document says that the details of transfer arrangements should be
handled out-of-band by eg electronic mail.  However, that would not
prevent a domain mistakenly or maliciously being transferred to the
wrong new registrar.  It is essential that this deficiency in the
protocol is corrected or worked around forthwith, as currently a
malicious registrar who is able to manipulate unsecured out-of-band
email may be able to cause the domain to be transferred to themselves
instead of to the intended recipient registrar.

A workaround would be for the intended recipient to send (via another
protocol) to the donor an authenticated confirmation to the that it
had successfully lodged the transfer request, so that if the donor is
willing to transfer to that registrar it can safely approve the
transfer.  However, the technical integrity of this scheme depends on
the registry never unexpectedly losing or timing out transfer
requests, and on donors to keep a record of all recent transfer
requests to ensure that the right request is accepted; the sociolegal
integrity of such a workaround may depend on extremely complicated
contractual issues, which is not my field of expertise.  In any case
this caveat should be addressed in any Information RFC.

* The use of passwords for identifying registrars rather than the
certificate information corresponding to the SSL session is very
unwise.  The secret(s) which identify a registrar should never leave
that registrar.  For example, a security compromise at the registry
would require all the registrars' passwords to be changed, and
redistributed via secure out-of-band channels.  Furthermore, the use
of passwords makes it impossible to use secure hardware to store the
critical key material.  This misfeature should be fixed in future
versions and implementations.

* The use of registry local time in time stamps is absurd (and will
likely lead to daylight saving change bugs etc.).  The time used
should be in UTC, or preferably elapsed civil time measured as the
number of non-leap seconds since a suitable epoch.  This misfeature
should be fixed in a future protocol version.

* The use of SSL, rather than individually authenticating requests and
responses (or batches of them), means that there is no audit trail,
verifiable by a third party, for resolving disputes.  This bug should
be fixed in a future protocol version.

I think that any Informational RFC describing this protocol should at
the very least mention these deficiencies as well as those it already
lists.

Ian.



From owner-ietf-outbound@ietf.org  Tue Jan  4 12:34:19 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03002
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 12:34:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id MAA29560;
	Tue, 4 Jan 2000 12:32:52 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA02858
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 12:30:02 -0500 (EST)
Received: from chiark.greenend.org.uk (mail@chiark.greenend.org.uk [195.224.76.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02693;
	Tue, 4 Jan 2000 12:21:55 -0500 (EST)
Received: from ijackson by chiark.greenend.org.uk with local (Exim 2.05 #1)
	id 125Xea-00064D-00 (Debian); Tue, 4 Jan 2000 17:21:52 +0000
From: Ian Jackson <ijackson@chiark.greenend.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14450.11312.813608.730985@chiark.greenend.org.uk>
Date: Tue, 4 Jan 2000 17:21:52 +0000 (GMT)
To: iesg@ietf.org
Cc: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to
	 Informational
Newsgroups: chiark.mail.ietf.announce
In-Reply-To: <199912301922.OAA03462@ietf.org>
References: <199912301922.OAA03462@ietf.org>
X-Mailer: VM 6.62 under Emacs 19.34.1
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The IESG writes ("Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 	 Informational"):
> 
> The IESG has received a request to consider Registry Registrar Protocol
> (RRP) Version 1.1.0 <draft-hollenbeck-rrp-00.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 January 13, 2000.

I can see at least the following problems with this protocol, in
addition to those described in it:

* The TRANSFER command, when used to approve a transfer, does not
specify to which registrar the domain is to be transferred.  The
document says that the details of transfer arrangements should be
handled out-of-band by eg electronic mail.  However, that would not
prevent a domain mistakenly or maliciously being transferred to the
wrong new registrar.  It is essential that this deficiency in the
protocol is corrected or worked around forthwith, as currently a
malicious registrar who is able to manipulate unsecured out-of-band
email may be able to cause the domain to be transferred to themselves
instead of to the intended recipient registrar.

A workaround would be for the intended recipient to send (via another
protocol) to the donor an authenticated confirmation to the that it
had successfully lodged the transfer request, so that if the donor is
willing to transfer to that registrar it can safely approve the
transfer.  However, the technical integrity of this scheme depends on
the registry never unexpectedly losing or timing out transfer
requests, and on donors to keep a record of all recent transfer
requests to ensure that the right request is accepted; the sociolegal
integrity of such a workaround may depend on extremely complicated
contractual issues, which is not my field of expertise.  In any case
this caveat should be addressed in any Information RFC.

* The use of passwords for identifying registrars rather than the
certificate information corresponding to the SSL session is very
unwise.  The secret(s) which identify a registrar should never leave
that registrar.  For example, a security compromise at the registry
would require all the registrars' passwords to be changed, and
redistributed via secure out-of-band channels.  Furthermore, the use
of passwords makes it impossible to use secure hardware to store the
critical key material.  This misfeature should be fixed in future
versions and implementations.

* The use of registry local time in time stamps is absurd (and will
likely lead to daylight saving change bugs etc.).  The time used
should be in UTC, or preferably elapsed civil time measured as the
number of non-leap seconds since a suitable epoch.  This misfeature
should be fixed in a future protocol version.

* The use of SSL, rather than individually authenticating requests and
responses (or batches of them), means that there is no audit trail,
verifiable by a third party, for resolving disputes.  This bug should
be fixed in a future protocol version.

I think that any Informational RFC describing this protocol should at
the very least mention these deficiencies as well as those it already
lists.

Ian.



From owner-ietf-outbound  Tue Jan  4 13:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA03278
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 13:00:03 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03198;
	Tue, 4 Jan 2000 12:56:41 -0500 (EST)
Received: from 192.168.111.25 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id SAA03245; 
          Tue, 4 Jan 2000 18:54:50 +0100 (MET)
Date: Tue, 04 Jan 2000 18:54:48 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@NETSOL.COM>
cc: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
Message-ID: <625862.3156000888@[192.168.111.25]>
In-Reply-To: <14450.11312.813608.730985@chiark.greenend.org.uk>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

--On 2000-01-04 17.21 +0000, Ian Jackson <ijackson@chiark.greenend.org.uk> 
wrote:

> * The TRANSFER command, when used to approve a transfer, does not
> specify to which registrar the domain is to be transferred.

If I remember correctly from a presentation NSI have had for me, the 
transfer is always to the registrar issuing the command, but I might be 
wrong.

Regardless, thanks for the comments. They are taken into consideration.

   paf





From owner-ietf-outbound@ietf.org  Tue Jan  4 13:02:54 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03400
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 13:02:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id NAA00061;
	Tue, 4 Jan 2000 13:01:28 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA03278
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 13:00:03 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03198;
	Tue, 4 Jan 2000 12:56:41 -0500 (EST)
Received: from 192.168.111.25 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id SAA03245; 
          Tue, 4 Jan 2000 18:54:50 +0100 (MET)
Date: Tue, 04 Jan 2000 18:54:48 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@NETSOL.COM>
cc: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
Message-ID: <625862.3156000888@[192.168.111.25]>
In-Reply-To: <14450.11312.813608.730985@chiark.greenend.org.uk>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

--On 2000-01-04 17.21 +0000, Ian Jackson <ijackson@chiark.greenend.org.uk> 
wrote:

> * The TRANSFER command, when used to approve a transfer, does not
> specify to which registrar the domain is to be transferred.

If I remember correctly from a presentation NSI have had for me, the 
transfer is always to the registrar issuing the command, but I might be 
wrong.

Regardless, thanks for the comments. They are taken into consideration.

   paf





From owner-ietf-outbound  Tue Jan  4 14:50:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA04984
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 14:50:02 -0500 (EST)
Received: from ml.media.mit.edu (ml.media.mit.edu [18.85.13.107])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04945
	for <ietf@ietf.org>; Tue, 4 Jan 2000 14:47:44 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by ml.media.mit.edu (8.8.8/8.8.7) with SMTP id OAA25197;
	Tue, 4 Jan 2000 14:47:42 -0500 (EST)
From: Alan Blount <blount@media.mit.edu>
Message-Id: <200001041947.OAA25197@ml.media.mit.edu>
X-Authentication-Warning: ml.media.mit.edu: localhost [127.0.0.1] didn't use HELO protocol
To: ietf@ietf.org
cc: blount@media.mit.edu
Subject: I-D nroff macros
Date: Tue, 04 Jan 2000 14:47:42 -0500
X-Mts: smtp

I've been using the simple set of nroff macros, as described by

  http://www.ietf.org/internet-drafts/2-nroff.template

While this works, I'd like to be able to autogenerate section numbers
and table of contents entries.  This draft doesn't give any guidance.
I tried the -ms macros, as described by

  http://www.cs.berkeley.edu/%7Ejanp/Help/textms.html

but the header macro .NH creates the header in boldface, which is a
no-no according to RFC 2223.  

I imagine there is a way to do this, but I am ignorant of the
necessary kung-fu.  Does anyone have a sample nroff file, perhaps a
draft they've written, that generates heading numbers and a toc?

Thanks,
Alan Blount
blount@media.mit.edu



From owner-ietf-outbound@ietf.org  Tue Jan  4 14:53:36 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05072
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 14:53:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id OAA01970;
	Tue, 4 Jan 2000 14:52:12 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA04984
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 14:50:02 -0500 (EST)
Received: from ml.media.mit.edu (ml.media.mit.edu [18.85.13.107])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04945
	for <ietf@ietf.org>; Tue, 4 Jan 2000 14:47:44 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by ml.media.mit.edu (8.8.8/8.8.7) with SMTP id OAA25197;
	Tue, 4 Jan 2000 14:47:42 -0500 (EST)
From: Alan Blount <blount@media.mit.edu>
Message-Id: <200001041947.OAA25197@ml.media.mit.edu>
X-Authentication-Warning: ml.media.mit.edu: localhost [127.0.0.1] didn't use HELO protocol
To: ietf@ietf.org
cc: blount@media.mit.edu
Subject: I-D nroff macros
Date: Tue, 04 Jan 2000 14:47:42 -0500
X-Mts: smtp

I've been using the simple set of nroff macros, as described by

  http://www.ietf.org/internet-drafts/2-nroff.template

While this works, I'd like to be able to autogenerate section numbers
and table of contents entries.  This draft doesn't give any guidance.
I tried the -ms macros, as described by

  http://www.cs.berkeley.edu/%7Ejanp/Help/textms.html

but the header macro .NH creates the header in boldface, which is a
no-no according to RFC 2223.  

I imagine there is a way to do this, but I am ignorant of the
necessary kung-fu.  Does anyone have a sample nroff file, perhaps a
draft they've written, that generates heading numbers and a toc?

Thanks,
Alan Blount
blount@media.mit.edu



From owner-ietf-outbound  Tue Jan  4 15:41:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA05971
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 15:40:03 -0500 (EST)
Received: from Mail.MeepZor.Com (IDENT:root@i.meepzor.com [204.146.167.214])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05722
	for <ietf@ietf.org>; Tue, 4 Jan 2000 15:25:36 -0500 (EST)
Received: from Golux.Com (ss08.nc.us.ibm.com [32.97.136.238])
	by Mail.MeepZor.Com (8.8.7/8.8.7) with ESMTP id PAA22431;
	Tue, 4 Jan 2000 15:26:55 -0500
Message-ID: <38725721.5A83E78E@Golux.Com>
Date: Tue, 04 Jan 2000 15:25:05 -0500
From: Rodent of Unusual Size <Ken.Coar@Golux.Com>
Organization: The Apache Software Foundation
X-Mailer: Mozilla 4.06 [en] (WinNT; U)
MIME-Version: 1.0
To: Alan Blount <blount@media.mit.edu>
CC: ietf@ietf.org
Subject: Re: I-D nroff macros
References: <200001041947.OAA25197@ml.media.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I maintain my drafts (such as they are) in HTML, and I use
a couple of Perl scripts to turn the Lynx output into something
digestible for the I-D directories, including TOC generation and
pagination.

FWIW..
-- 
#ken    P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Software Foundation  <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>

Come to the first official Apache Software Foundation
Conference!  <http://ApacheCon.Com/>



From owner-ietf-outbound@ietf.org  Tue Jan  4 15:47:12 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06199
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 15:47:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id PAA03056;
	Tue, 4 Jan 2000 15:45:47 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA05971
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 15:40:03 -0500 (EST)
Received: from Mail.MeepZor.Com (IDENT:root@i.meepzor.com [204.146.167.214])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05722
	for <ietf@ietf.org>; Tue, 4 Jan 2000 15:25:36 -0500 (EST)
Received: from Golux.Com (ss08.nc.us.ibm.com [32.97.136.238])
	by Mail.MeepZor.Com (8.8.7/8.8.7) with ESMTP id PAA22431;
	Tue, 4 Jan 2000 15:26:55 -0500
Message-ID: <38725721.5A83E78E@Golux.Com>
Date: Tue, 04 Jan 2000 15:25:05 -0500
From: Rodent of Unusual Size <Ken.Coar@Golux.Com>
Organization: The Apache Software Foundation
X-Mailer: Mozilla 4.06 [en] (WinNT; U)
MIME-Version: 1.0
To: Alan Blount <blount@media.mit.edu>
CC: ietf@ietf.org
Subject: Re: I-D nroff macros
References: <200001041947.OAA25197@ml.media.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I maintain my drafts (such as they are) in HTML, and I use
a couple of Perl scripts to turn the Lynx output into something
digestible for the I-D directories, including TOC generation and
pagination.

FWIW..
-- 
#ken    P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Software Foundation  <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>

Come to the first official Apache Software Foundation
Conference!  <http://ApacheCon.Com/>



From owner-ietf-outbound  Tue Jan  4 16:20:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA06819
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 16:20:02 -0500 (EST)
Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06727;
	Tue, 4 Jan 2000 16:19:06 -0500 (EST)
Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net)
	by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7)
	id 125bM9-0003V1-00; Tue, 04 Jan 2000 21:19:05 +0000
Received: from [209.21.28.101] (helo=nma.com)
	by dfw-mmp4.email.verio.net with esmtp (Exim 3.12 #7)
	id 125bM0-00014V-00; Tue, 04 Jan 2000 21:18:56 +0000
Message-ID: <38726401.DF6EA534@nma.com>
Date: Tue, 04 Jan 2000 13:20:01 -0800
From: Ed Gerck <egerck@safevote.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>
CC: Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
References: <625862.3156000888@[192.168.111.25]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



Patrik Fältström wrote:

> --On 2000-01-04 17.21 +0000, Ian Jackson <ijackson@chiark.greenend.org.uk>
> wrote:
>
> > * The TRANSFER command, when used to approve a transfer, does not
> > specify to which registrar the domain is to be transferred.
>
> If I remember correctly from a presentation NSI have had for me, the
> transfer is always to the registrar issuing the command, but I might be
> wrong.
>
> Regardless, thanks for the comments. They are taken into consideration.
>
>    paf

Patrik:

"If I remember correctly from a presentation NSI have had for me" is
a good name for the RAB [1] meetings we attended I presume, in the
euphemisms that these discussions have turned into.

However, IMO it would be unfitting to the IETF to proceed discussions
on NSI's proposed RFC without NSI disclosing and making public all
the RAB meeting minutes, as "supporting" documentation.

Further, reading NSI's RFC and Karl's comments here, I am grateful that
neither the RAB  nor its members were mentioned in the RFC, nor a
cknowledged, even though the RFC is on the very same Shared
Registry Protocol we were called to help verify and provide free but
otherwise professional advice.

You will recognize in Karl's comments a rerun of some of my
own comments and also of Stef's and Steve's, I am sure, just
to cite a few. Race conditions, log traces, actions on log
traces, reliable timestamps, the need for well-defined states
with well-defined variables, slamming precautions, transfer
problems, correct internationalization, UTC time, message
text limit, etc. were also all mentioned and advised about
more than once; and they are in the RAB Minutes.  They
need to be made public since NSI is requesting public
comments.  They are also part of the mandates of Amendment
11, which I wish to interpret technically -- no politically by
euphemisms of  a "presentation NSI have had for me".

Cheers,

Ed Gerck

[1] http://www.nsiregistry.com/history/rab.html :

 Mission Statement The Network Solutions Registry Advisory Board (RAB) was formed to provide Network
   Solutions with independent external advisory review of the design and testing of the NSI Shared Registration
   System. Members of the RAB were selected to provide a balance of diverse technology and regional
   perspectives. The Board existed through 30 September 1999 to review, participate, and advise in testing of
   the technology aspects of the Shared Registration System, and to suggest improvements to Network Solutions
   to better meet the mandates of Amendment 11.

   Members

          External Members
          David Conrad
          Patrik Fältström
          Katherine Fithen
          Dr. Edgardo Gerck
          Dr. Johan Hjelm
          Michael Rotert
          Einar "Stef" Stefferud
          Dr. Stephen Wolff

                         NSI Members
                         David Holtzmann
                         Aristotle Balogh
                         Scott Hollenbeck
                         Neeran Saraf



From owner-ietf-outbound@ietf.org  Tue Jan  4 16:22:07 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06872
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 16:22:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id QAA03656;
	Tue, 4 Jan 2000 16:20:43 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA06819
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 16:20:02 -0500 (EST)
Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06727;
	Tue, 4 Jan 2000 16:19:06 -0500 (EST)
Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net)
	by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7)
	id 125bM9-0003V1-00; Tue, 04 Jan 2000 21:19:05 +0000
Received: from [209.21.28.101] (helo=nma.com)
	by dfw-mmp4.email.verio.net with esmtp (Exim 3.12 #7)
	id 125bM0-00014V-00; Tue, 04 Jan 2000 21:18:56 +0000
Message-ID: <38726401.DF6EA534@nma.com>
Date: Tue, 04 Jan 2000 13:20:01 -0800
From: Ed Gerck <egerck@safevote.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>
CC: Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
References: <625862.3156000888@[192.168.111.25]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



Patrik Fältström wrote:

> --On 2000-01-04 17.21 +0000, Ian Jackson <ijackson@chiark.greenend.org.uk>
> wrote:
>
> > * The TRANSFER command, when used to approve a transfer, does not
> > specify to which registrar the domain is to be transferred.
>
> If I remember correctly from a presentation NSI have had for me, the
> transfer is always to the registrar issuing the command, but I might be
> wrong.
>
> Regardless, thanks for the comments. They are taken into consideration.
>
>    paf

Patrik:

"If I remember correctly from a presentation NSI have had for me" is
a good name for the RAB [1] meetings we attended I presume, in the
euphemisms that these discussions have turned into.

However, IMO it would be unfitting to the IETF to proceed discussions
on NSI's proposed RFC without NSI disclosing and making public all
the RAB meeting minutes, as "supporting" documentation.

Further, reading NSI's RFC and Karl's comments here, I am grateful that
neither the RAB  nor its members were mentioned in the RFC, nor a
cknowledged, even though the RFC is on the very same Shared
Registry Protocol we were called to help verify and provide free but
otherwise professional advice.

You will recognize in Karl's comments a rerun of some of my
own comments and also of Stef's and Steve's, I am sure, just
to cite a few. Race conditions, log traces, actions on log
traces, reliable timestamps, the need for well-defined states
with well-defined variables, slamming precautions, transfer
problems, correct internationalization, UTC time, message
text limit, etc. were also all mentioned and advised about
more than once; and they are in the RAB Minutes.  They
need to be made public since NSI is requesting public
comments.  They are also part of the mandates of Amendment
11, which I wish to interpret technically -- no politically by
euphemisms of  a "presentation NSI have had for me".

Cheers,

Ed Gerck

[1] http://www.nsiregistry.com/history/rab.html :

 Mission Statement The Network Solutions Registry Advisory Board (RAB) was formed to provide Network
   Solutions with independent external advisory review of the design and testing of the NSI Shared Registration
   System. Members of the RAB were selected to provide a balance of diverse technology and regional
   perspectives. The Board existed through 30 September 1999 to review, participate, and advise in testing of
   the technology aspects of the Shared Registration System, and to suggest improvements to Network Solutions
   to better meet the mandates of Amendment 11.

   Members

          External Members
          David Conrad
          Patrik Fältström
          Katherine Fithen
          Dr. Edgardo Gerck
          Dr. Johan Hjelm
          Michael Rotert
          Einar "Stef" Stefferud
          Dr. Stephen Wolff

                         NSI Members
                         David Holtzmann
                         Aristotle Balogh
                         Scott Hollenbeck
                         Neeran Saraf



From owner-ietf-outbound  Tue Jan  4 16:40:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA07316
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 16:40:03 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07154;
	Tue, 4 Jan 2000 16:34:11 -0500 (EST)
Received: from 192.168.111.25 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id WAA10230; 
          Tue, 4 Jan 2000 22:32:18 +0100 (MET)
Date: Tue, 04 Jan 2000 22:32:09 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Ed Gerck <egerck@safevote.com>
cc: Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
Message-ID: <1410228.3156013929@[192.168.111.25]>
In-Reply-To: <38726401.DF6EA534@nma.com>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA07154
Content-Transfer-Encoding: 8bit

--On 2000-01-04 13.20 -0800, Ed Gerck <egerck@safevote.com> wrote:

> Further, reading NSI's RFC and Karl's comments here, I am grateful that
> neither the RAB  nor its members were mentioned in the RFC, nor a
> cknowledged, even though the RFC is on the very same Shared
> Registry Protocol we were called to help verify and provide free but
> otherwise professional advice.

If RAB was mentioned, I would have been more careful with the document, but 
as the RAB only had limited input to the actual design of the protocol, the 
RAB should not, and is not, mentioned.

In this case though, the document will specify "the NSI R-R protocol", 
nothing else. It is often organizations do present and make specifications 
available of their private inventions through publications of Informational 
RFCs, so this is nothing special.

The IETF in this case must differentiate between input to the NSI on 
whether the protocol is good or bad, and maybe on how to make the protocol 
better in the future, and whether the document specifies what is currently 
in use.

The last call in the IETF is regarding the latter, not the quality of the 
protocol.

The IESG can still make a recommendation to NOT publish the (private) 
protocol as informational RFC, for example if the protocol damages the 
functionality of the Internet. In this case, where we talk about one 
specific application, that is probably not the case.

So, you are talking about (like we did in the RAB) the quality of the 
protocol, while I now as AD and member of the IESG is asking whether this 
document is correctly describing what is in use.

I ask you Ed, and all others, to please differentiate between those two 
issues, and come with comments on the correctness of the document. Comments 
on the protocol can be sent directly to NSI.


    Patrik Fältström
    Area Director, Applications Area





From owner-ietf-outbound@ietf.org  Tue Jan  4 16:41:45 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07392
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 16:41:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id QAA03992;
	Tue, 4 Jan 2000 16:40:20 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA07316
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 16:40:03 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07154;
	Tue, 4 Jan 2000 16:34:11 -0500 (EST)
Received: from 192.168.111.25 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id WAA10230; 
          Tue, 4 Jan 2000 22:32:18 +0100 (MET)
Date: Tue, 04 Jan 2000 22:32:09 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Ed Gerck <egerck@safevote.com>
cc: Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
Message-ID: <1410228.3156013929@[192.168.111.25]>
In-Reply-To: <38726401.DF6EA534@nma.com>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA07154
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

--On 2000-01-04 13.20 -0800, Ed Gerck <egerck@safevote.com> wrote:

> Further, reading NSI's RFC and Karl's comments here, I am grateful that
> neither the RAB  nor its members were mentioned in the RFC, nor a
> cknowledged, even though the RFC is on the very same Shared
> Registry Protocol we were called to help verify and provide free but
> otherwise professional advice.

If RAB was mentioned, I would have been more careful with the document, but 
as the RAB only had limited input to the actual design of the protocol, the 
RAB should not, and is not, mentioned.

In this case though, the document will specify "the NSI R-R protocol", 
nothing else. It is often organizations do present and make specifications 
available of their private inventions through publications of Informational 
RFCs, so this is nothing special.

The IETF in this case must differentiate between input to the NSI on 
whether the protocol is good or bad, and maybe on how to make the protocol 
better in the future, and whether the document specifies what is currently 
in use.

The last call in the IETF is regarding the latter, not the quality of the 
protocol.

The IESG can still make a recommendation to NOT publish the (private) 
protocol as informational RFC, for example if the protocol damages the 
functionality of the Internet. In this case, where we talk about one 
specific application, that is probably not the case.

So, you are talking about (like we did in the RAB) the quality of the 
protocol, while I now as AD and member of the IESG is asking whether this 
document is correctly describing what is in use.

I ask you Ed, and all others, to please differentiate between those two 
issues, and come with comments on the correctness of the document. Comments 
on the protocol can be sent directly to NSI.


    Patrik Fältström
    Area Director, Applications Area





From owner-ietf-outbound  Tue Jan  4 17:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA07863
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 17:10:02 -0500 (EST)
Received: from dfw-smtpout3.email.verio.net (dfw-smtpout3.email.verio.net [129.250.36.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07665;
	Tue, 4 Jan 2000 17:00:30 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125c0C-0001ta-00; Tue, 04 Jan 2000 22:00:28 +0000
Received: from [209.21.28.101] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125bzW-0005Zj-00; Tue, 04 Jan 2000 21:59:47 +0000
Message-ID: <38726DB8.19F0D36@nma.com>
Date: Tue, 04 Jan 2000 14:01:28 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        Ian Jackson 
	<ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck 
	<shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


[resent from subscribed address, my apologies
if the TO list receives it twice]

Patrik Fältström wrote:

> --On 2000-01-04 17.21 +0000, Ian Jackson <ijackson@chiark.greenend.org.uk>
> wrote:
>
> > * The TRANSFER command, when used to approve a transfer, does not
> > specify to which registrar the domain is to be transferred.
>
> If I remember correctly from a presentation NSI have had for me, the
> transfer is always to the registrar issuing the command, but I might be
> wrong.
>
> Regardless, thanks for the comments. They are taken into consideration.
>
>    paf

Patrik:

"If I remember correctly from a presentation NSI have had for me" is
a good name for the RAB [1] meetings we attended I presume, in the
euphemisms that these discussions have turned into.

However, IMO it would be unfitting to the IETF to proceed discussions
on NSI's proposed RFC without NSI disclosing and making public all
the RAB meeting minutes, as "supporting" documentation.

Further, reading NSI's RFC and Karl's comments here, I am grateful that
neither the RAB  nor its members were mentioned in the RFC, nor a
cknowledged, even though the RFC is on the very same Shared
Registry Protocol we were called to help verify and provide free but
otherwise professional advice.

You will recognize in Karl's comments a rerun of some of my
own comments and also of Stef's and Steve's, I am sure, just
to cite a few. Race conditions, log traces, actions on log
traces, reliable timestamps, the need for well-defined states
with well-defined variables, slamming precautions, transfer
problems, correct internationalization, UTC time, message
text limit, etc. were also all mentioned and advised about
more than once; and they are in the RAB Minutes.  They
need to be made public since NSI is requesting public
comments.  They are also part of the mandates of Amendment
11, which I wish to interpret technically -- no politically by
euphemisms of  a "presentation NSI have had for me".

Cheers,

Ed Gerck

[1] http://www.nsiregistry.com/history/rab.html :

 Mission Statement The Network Solutions Registry Advisory Board (RAB) was formed to provide Network
   Solutions with independent external advisory review of the design and testing of the NSI Shared Registration
   System. Members of the RAB were selected to provide a balance of diverse technology and regional
   perspectives. The Board existed through 30 September 1999 to review, participate, and advise in testing of
   the technology aspects of the Shared Registration System, and to suggest improvements to Network Solutions
   to better meet the mandates of Amendment 11.

   Members

          External Members
          David Conrad
          Patrik Fältström
          Katherine Fithen
          Dr. Edgardo Gerck
          Dr. Johan Hjelm
          Michael Rotert
          Einar "Stef" Stefferud
          Dr. Stephen Wolff

                         NSI Members
                         David Holtzmann
                         Aristotle Balogh
                         Scott Hollenbeck
                         Neeran Saraf



From owner-ietf-outbound@ietf.org  Tue Jan  4 17:11:59 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07957
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 17:11:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id RAA04530;
	Tue, 4 Jan 2000 17:10:33 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA07863
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 17:10:02 -0500 (EST)
Received: from dfw-smtpout3.email.verio.net (dfw-smtpout3.email.verio.net [129.250.36.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07665;
	Tue, 4 Jan 2000 17:00:30 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125c0C-0001ta-00; Tue, 04 Jan 2000 22:00:28 +0000
Received: from [209.21.28.101] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125bzW-0005Zj-00; Tue, 04 Jan 2000 21:59:47 +0000
Message-ID: <38726DB8.19F0D36@nma.com>
Date: Tue, 04 Jan 2000 14:01:28 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        Ian Jackson 
	<ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck 
	<shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


[resent from subscribed address, my apologies
if the TO list receives it twice]

Patrik Fältström wrote:

> --On 2000-01-04 17.21 +0000, Ian Jackson <ijackson@chiark.greenend.org.uk>
> wrote:
>
> > * The TRANSFER command, when used to approve a transfer, does not
> > specify to which registrar the domain is to be transferred.
>
> If I remember correctly from a presentation NSI have had for me, the
> transfer is always to the registrar issuing the command, but I might be
> wrong.
>
> Regardless, thanks for the comments. They are taken into consideration.
>
>    paf

Patrik:

"If I remember correctly from a presentation NSI have had for me" is
a good name for the RAB [1] meetings we attended I presume, in the
euphemisms that these discussions have turned into.

However, IMO it would be unfitting to the IETF to proceed discussions
on NSI's proposed RFC without NSI disclosing and making public all
the RAB meeting minutes, as "supporting" documentation.

Further, reading NSI's RFC and Karl's comments here, I am grateful that
neither the RAB  nor its members were mentioned in the RFC, nor a
cknowledged, even though the RFC is on the very same Shared
Registry Protocol we were called to help verify and provide free but
otherwise professional advice.

You will recognize in Karl's comments a rerun of some of my
own comments and also of Stef's and Steve's, I am sure, just
to cite a few. Race conditions, log traces, actions on log
traces, reliable timestamps, the need for well-defined states
with well-defined variables, slamming precautions, transfer
problems, correct internationalization, UTC time, message
text limit, etc. were also all mentioned and advised about
more than once; and they are in the RAB Minutes.  They
need to be made public since NSI is requesting public
comments.  They are also part of the mandates of Amendment
11, which I wish to interpret technically -- no politically by
euphemisms of  a "presentation NSI have had for me".

Cheers,

Ed Gerck

[1] http://www.nsiregistry.com/history/rab.html :

 Mission Statement The Network Solutions Registry Advisory Board (RAB) was formed to provide Network
   Solutions with independent external advisory review of the design and testing of the NSI Shared Registration
   System. Members of the RAB were selected to provide a balance of diverse technology and regional
   perspectives. The Board existed through 30 September 1999 to review, participate, and advise in testing of
   the technology aspects of the Shared Registration System, and to suggest improvements to Network Solutions
   to better meet the mandates of Amendment 11.

   Members

          External Members
          David Conrad
          Patrik Fältström
          Katherine Fithen
          Dr. Edgardo Gerck
          Dr. Johan Hjelm
          Michael Rotert
          Einar "Stef" Stefferud
          Dr. Stephen Wolff

                         NSI Members
                         David Holtzmann
                         Aristotle Balogh
                         Scott Hollenbeck
                         Neeran Saraf



From owner-ietf-outbound  Tue Jan  4 17:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA08079
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 17:20:02 -0500 (EST)
Received: from dfw-smtpout2.email.verio.net (dfw-smtpout2.email.verio.net [129.250.36.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07922;
	Tue, 4 Jan 2000 17:11:03 -0500 (EST)
Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net)
	by dfw-smtpout2.email.verio.net with esmtp (Exim 3.12 #7)
	id 125cAR-0000bJ-00; Tue, 04 Jan 2000 22:11:03 +0000
Received: from [209.21.28.101] (helo=nma.com)
	by dfw-mmp4.email.verio.net with esmtp (Exim 3.12 #7)
	id 125cAM-0004S8-00; Tue, 04 Jan 2000 22:10:59 +0000
Message-ID: <38727013.DAF0AE16@nma.com>
Date: Tue, 04 Jan 2000 14:11:31 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>
CC: Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
References: <1410228.3156013929@[192.168.111.25]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



Patrik Fältström wrote:

> So, you are talking about (like we did in the RAB) the quality of the
> protocol, while I now as AD and member of the IESG is asking whether this
> document is correctly describing what is in use.
>
> I ask you Ed, and all others, to please differentiate between those two
> issues, and come with comments on the correctness of the document. Comments
> on the protocol can be sent directly to NSI.

IMO you  are following a very slippery slope here.  You seem
now to be moving into "explanation mode" in order to say that 
the  protocol's effectiveness is not important, just its perfunctory 
functions.

In other words, you as AD and member of the IESG are saying
that protocols are to be published as RFCs even if knowingly
technically wrong, inefficient, outdated and insecure -- provided
they are "in use".

Well, I may be a little less pragmatic than you and I question exactly
the correctness of the document, as well as its effectiveness.

And, since our names are still in NSI's page for the Registry Advisory
Board (RAB) and we were involved with it, I also think that the IETF
should know that the SRP being proposed by NSI as an RFC and
being followed through IETF under yours (a former member of the
RAB) apparent approval is not what the RAB discussed and
formally requested to change as documented in the RAB minutes locked
under NDA. The RAB in Ammendment 11 has thus become a mock review 
process locked under NDA, even though the RAB was officially called by 
the USG to "review, participate, and advise in testing of the technology
aspects of the Shared  Registration System, and to suggest improvements
to Network Solutions to better meet the mandates of Amendment 11."

The least I suggest is to make the RAB Metting Minutes, together with
its Action Plan, public -- before furthering this RFC in the IETF. Why
should other people need to reinvent the same comments again?  The hope
that some will not be reinvented is IMO ill-founded as security
experience shows all the time -- obscurity is not a basis for
security.

Now, of course, if NSI wants to keep the protocol private then I
have no further comments.

Cheers,

Ed Gerck



From owner-ietf-outbound@ietf.org  Tue Jan  4 17:21:26 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08123
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 17:21:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id RAA04679;
	Tue, 4 Jan 2000 17:19:58 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA08079
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 17:20:02 -0500 (EST)
Received: from dfw-smtpout2.email.verio.net (dfw-smtpout2.email.verio.net [129.250.36.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07922;
	Tue, 4 Jan 2000 17:11:03 -0500 (EST)
Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net)
	by dfw-smtpout2.email.verio.net with esmtp (Exim 3.12 #7)
	id 125cAR-0000bJ-00; Tue, 04 Jan 2000 22:11:03 +0000
Received: from [209.21.28.101] (helo=nma.com)
	by dfw-mmp4.email.verio.net with esmtp (Exim 3.12 #7)
	id 125cAM-0004S8-00; Tue, 04 Jan 2000 22:10:59 +0000
Message-ID: <38727013.DAF0AE16@nma.com>
Date: Tue, 04 Jan 2000 14:11:31 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>
CC: Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
References: <1410228.3156013929@[192.168.111.25]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



Patrik Fältström wrote:

> So, you are talking about (like we did in the RAB) the quality of the
> protocol, while I now as AD and member of the IESG is asking whether this
> document is correctly describing what is in use.
>
> I ask you Ed, and all others, to please differentiate between those two
> issues, and come with comments on the correctness of the document. Comments
> on the protocol can be sent directly to NSI.

IMO you  are following a very slippery slope here.  You seem
now to be moving into "explanation mode" in order to say that 
the  protocol's effectiveness is not important, just its perfunctory 
functions.

In other words, you as AD and member of the IESG are saying
that protocols are to be published as RFCs even if knowingly
technically wrong, inefficient, outdated and insecure -- provided
they are "in use".

Well, I may be a little less pragmatic than you and I question exactly
the correctness of the document, as well as its effectiveness.

And, since our names are still in NSI's page for the Registry Advisory
Board (RAB) and we were involved with it, I also think that the IETF
should know that the SRP being proposed by NSI as an RFC and
being followed through IETF under yours (a former member of the
RAB) apparent approval is not what the RAB discussed and
formally requested to change as documented in the RAB minutes locked
under NDA. The RAB in Ammendment 11 has thus become a mock review 
process locked under NDA, even though the RAB was officially called by 
the USG to "review, participate, and advise in testing of the technology
aspects of the Shared  Registration System, and to suggest improvements
to Network Solutions to better meet the mandates of Amendment 11."

The least I suggest is to make the RAB Metting Minutes, together with
its Action Plan, public -- before furthering this RFC in the IETF. Why
should other people need to reinvent the same comments again?  The hope
that some will not be reinvented is IMO ill-founded as security
experience shows all the time -- obscurity is not a basis for
security.

Now, of course, if NSI wants to keep the protocol private then I
have no further comments.

Cheers,

Ed Gerck



From owner-ietf-outbound  Tue Jan  4 18:11:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA08897
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 18:10:02 -0500 (EST)
Received: from ibd.ar.com (adsl-63-194-205-76.dsl.snfc21.pacbell.net [63.194.205.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08853;
	Tue, 4 Jan 2000 18:06:05 -0500 (EST)
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id PAA01821;
	Tue, 4 Jan 2000 15:05:48 -0800 (PST)
Date: Tue, 4 Jan 2000 15:05:49 -0800 (PST)
From: Rick H Wesson <wessorh@ar.com>
To: Ed Gerck <egerck@nma.com>
cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
In-Reply-To: <38727013.DAF0AE16@nma.com>
Message-ID: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8BIT
Content-Transfer-Encoding: 8BIT
Content-Transfer-Encoding: 8BIT


IESG:

I hate to add a "me too" but I must. I believe that the RAB minutes would
be very useful if they were published. Having participated with many
Registrars and participated in changes and suggestions to the RRP protocol
through the ICANN Testbed process I welcome Ed's comments.

I am glad that NSI has published the I-D for their protocol, now does it
need to go beyond that and become an RFC, IMHO, no.

The IETF does not need to publish broken implementations of one companies 
view of the shared gTLD registration process. Having an AD that sat on the
RAB  promote the I-D and offer no reasoning as to why it
*should be* published as an Informational RFC reminds me of the bad taste
left by the IAHC and all the processes related.

I would request that the IESG let this draft expire and create a WG to
tackle the problem. I would be interested in hearing just why the IESG
thinks this document should be published. The document exists as an I-D,
the cat is out of the bag, why should it be an RFC? Its broken and of bad
design we don't need that kind of thing published any further than it has
been.

regards,

-rick




On Tue, 4 Jan 2000, Ed Gerck wrote:

> 
> 
> Patrik Fältström wrote:
> 
> > So, you are talking about (like we did in the RAB) the quality of the
> > protocol, while I now as AD and member of the IESG is asking whether this
> > document is correctly describing what is in use.
> >
> > I ask you Ed, and all others, to please differentiate between those two
> > issues, and come with comments on the correctness of the document. Comments
> > on the protocol can be sent directly to NSI.
> 
> IMO you  are following a very slippery slope here.  You seem
> now to be moving into "explanation mode" in order to say that 
> the  protocol's effectiveness is not important, just its perfunctory 
> functions.
> 
> In other words, you as AD and member of the IESG are saying
> that protocols are to be published as RFCs even if knowingly
> technically wrong, inefficient, outdated and insecure -- provided
> they are "in use".
> 
> Well, I may be a little less pragmatic than you and I question exactly
> the correctness of the document, as well as its effectiveness.
> 
> And, since our names are still in NSI's page for the Registry Advisory
> Board (RAB) and we were involved with it, I also think that the IETF
> should know that the SRP being proposed by NSI as an RFC and
> being followed through IETF under yours (a former member of the
> RAB) apparent approval is not what the RAB discussed and
> formally requested to change as documented in the RAB minutes locked
> under NDA. The RAB in Ammendment 11 has thus become a mock review 
> process locked under NDA, even though the RAB was officially called by 
> the USG to "review, participate, and advise in testing of the technology
> aspects of the Shared  Registration System, and to suggest improvements
> to Network Solutions to better meet the mandates of Amendment 11."
> 
> The least I suggest is to make the RAB Metting Minutes, together with
> its Action Plan, public -- before furthering this RFC in the IETF. Why
> should other people need to reinvent the same comments again?  The hope
> that some will not be reinvented is IMO ill-founded as security
> experience shows all the time -- obscurity is not a basis for
> security.
> 
> Now, of course, if NSI wants to keep the protocol private then I
> have no further comments.
> 
> Cheers,
> 
> Ed Gerck
> 



From owner-ietf-outbound@ietf.org  Tue Jan  4 18:12:51 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08963
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 18:12:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id SAA05506;
	Tue, 4 Jan 2000 18:11:30 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id SAA08897
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 18:10:02 -0500 (EST)
Received: from ibd.ar.com (adsl-63-194-205-76.dsl.snfc21.pacbell.net [63.194.205.76])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08853;
	Tue, 4 Jan 2000 18:06:05 -0500 (EST)
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id PAA01821;
	Tue, 4 Jan 2000 15:05:48 -0800 (PST)
Date: Tue, 4 Jan 2000 15:05:49 -0800 (PST)
From: Rick H Wesson <wessorh@ar.com>
To: Ed Gerck <egerck@nma.com>
cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
In-Reply-To: <38727013.DAF0AE16@nma.com>
Message-ID: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8BIT
Content-Transfer-Encoding: 8BIT
Content-Transfer-Encoding: 8BIT
Content-Transfer-Encoding: 8BIT


IESG:

I hate to add a "me too" but I must. I believe that the RAB minutes would
be very useful if they were published. Having participated with many
Registrars and participated in changes and suggestions to the RRP protocol
through the ICANN Testbed process I welcome Ed's comments.

I am glad that NSI has published the I-D for their protocol, now does it
need to go beyond that and become an RFC, IMHO, no.

The IETF does not need to publish broken implementations of one companies 
view of the shared gTLD registration process. Having an AD that sat on the
RAB  promote the I-D and offer no reasoning as to why it
*should be* published as an Informational RFC reminds me of the bad taste
left by the IAHC and all the processes related.

I would request that the IESG let this draft expire and create a WG to
tackle the problem. I would be interested in hearing just why the IESG
thinks this document should be published. The document exists as an I-D,
the cat is out of the bag, why should it be an RFC? Its broken and of bad
design we don't need that kind of thing published any further than it has
been.

regards,

-rick




On Tue, 4 Jan 2000, Ed Gerck wrote:

> 
> 
> Patrik Fältström wrote:
> 
> > So, you are talking about (like we did in the RAB) the quality of the
> > protocol, while I now as AD and member of the IESG is asking whether this
> > document is correctly describing what is in use.
> >
> > I ask you Ed, and all others, to please differentiate between those two
> > issues, and come with comments on the correctness of the document. Comments
> > on the protocol can be sent directly to NSI.
> 
> IMO you  are following a very slippery slope here.  You seem
> now to be moving into "explanation mode" in order to say that 
> the  protocol's effectiveness is not important, just its perfunctory 
> functions.
> 
> In other words, you as AD and member of the IESG are saying
> that protocols are to be published as RFCs even if knowingly
> technically wrong, inefficient, outdated and insecure -- provided
> they are "in use".
> 
> Well, I may be a little less pragmatic than you and I question exactly
> the correctness of the document, as well as its effectiveness.
> 
> And, since our names are still in NSI's page for the Registry Advisory
> Board (RAB) and we were involved with it, I also think that the IETF
> should know that the SRP being proposed by NSI as an RFC and
> being followed through IETF under yours (a former member of the
> RAB) apparent approval is not what the RAB discussed and
> formally requested to change as documented in the RAB minutes locked
> under NDA. The RAB in Ammendment 11 has thus become a mock review 
> process locked under NDA, even though the RAB was officially called by 
> the USG to "review, participate, and advise in testing of the technology
> aspects of the Shared  Registration System, and to suggest improvements
> to Network Solutions to better meet the mandates of Amendment 11."
> 
> The least I suggest is to make the RAB Metting Minutes, together with
> its Action Plan, public -- before furthering this RFC in the IETF. Why
> should other people need to reinvent the same comments again?  The hope
> that some will not be reinvented is IMO ill-founded as security
> experience shows all the time -- obscurity is not a basis for
> security.
> 
> Now, of course, if NSI wants to keep the protocol private then I
> have no further comments.
> 
> Cheers,
> 
> Ed Gerck
> 



From owner-ietf-outbound  Tue Jan  4 18:21:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA09065
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 18:20:02 -0500 (EST)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08937
	for <ietf@ietf.org>; Tue, 4 Jan 2000 18:11:07 -0500 (EST)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id RAA03496;
	Tue, 4 Jan 2000 17:11:02 -0600 (CST)
Message-Id: <200001042311.RAA03496@gungnir.fnal.gov>
To: Alan Blount <blount@media.mit.edu>
Cc: ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: I-D nroff macros 
In-reply-to: Your message of Tue, 04 Jan 2000 14:47:42 EST.
             <200001041947.OAA25197@ml.media.mit.edu> 
Date: Tue, 04 Jan 2000 17:11:02 -0600
Sender: crawdad@gungnir.fnal.gov

Alan,

  I'll send you my internet-draft nroff macros under separate cover.
(There's probably some internet obscenity law forbidding the
unsolicited transmission of nroff source.)

				Matt



From owner-ietf-outbound@ietf.org  Tue Jan  4 18:22:21 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09182
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 18:22:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id SAA05695;
	Tue, 4 Jan 2000 18:20:58 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id SAA09065
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 18:20:02 -0500 (EST)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08937
	for <ietf@ietf.org>; Tue, 4 Jan 2000 18:11:07 -0500 (EST)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id RAA03496;
	Tue, 4 Jan 2000 17:11:02 -0600 (CST)
Message-Id: <200001042311.RAA03496@gungnir.fnal.gov>
To: Alan Blount <blount@media.mit.edu>
Cc: ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: I-D nroff macros 
In-reply-to: Your message of Tue, 04 Jan 2000 14:47:42 EST.
             <200001041947.OAA25197@ml.media.mit.edu> 
Date: Tue, 04 Jan 2000 17:11:02 -0600
Sender: crawdad@gungnir.fnal.gov

Alan,

  I'll send you my internet-draft nroff macros under separate cover.
(There's probably some internet obscenity law forbidding the
unsolicited transmission of nroff source.)

				Matt



From owner-ietf-outbound  Tue Jan  4 18:41:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA09583
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 18:40:01 -0500 (EST)
Received: from npax.cavebear.com (IDENT:karl@npax.cavebear.com [192.203.17.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09525;
	Tue, 4 Jan 2000 18:35:09 -0500 (EST)
Received: from localhost (karl@localhost)
	by npax.cavebear.com (8.9.3/8.9.3) with ESMTP id PAA04238;
	Tue, 4 Jan 2000 15:34:23 -0800
Date: Tue, 4 Jan 2000 15:34:23 -0800 (PST)
From: Karl Auerbach <karl@CaveBear.com>
Reply-To: Karl Auerbach <karl@CaveBear.com>
To: Rick H Wesson <wessorh@ar.com>
cc: Ed Gerck <egerck@nma.com>,
        Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
In-Reply-To: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
Message-ID: <Pine.LNX.4.10.10001041522220.3751-100000@npax.cavebear.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

 
> I am glad that NSI has published the I-D for their protocol, now does it
> need to go beyond that and become an RFC, IMHO, no.

Since I-Ds still officially vanish after a while, we need to move it to
RFC to maintain its visibility.  <Let's defer comments on the I-D fade out
policy.>

> The IETF does not need to publish broken implementations of one companies 
> view of the shared gTLD registration process.

We can learn from the flaws of the past.  And this RRP certainly gives us
a lot to learn from.

I would hope that having an Informational RFC on the RRP would motivate
some folks to think up, write down, and publish "A Better RRP".  Your own
work on the representing the whois data using XML is perhaps a good start.

(I can imagine that many sites with big zone files might find it useful to
have a tool using "A Better RRP" to distribute the administration of their
zone.)

By-the-way, I think that the IETF has already jumped through enough hoops
regarding the mis-perception by some that the letters "RFC" are some sort
of seal of approval.

		--karl--




From owner-ietf-outbound@ietf.org  Tue Jan  4 18:42:18 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09655
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 18:42:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id SAA06043;
	Tue, 4 Jan 2000 18:40:53 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id SAA09583
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 18:40:01 -0500 (EST)
Received: from npax.cavebear.com (IDENT:karl@npax.cavebear.com [192.203.17.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09525;
	Tue, 4 Jan 2000 18:35:09 -0500 (EST)
Received: from localhost (karl@localhost)
	by npax.cavebear.com (8.9.3/8.9.3) with ESMTP id PAA04238;
	Tue, 4 Jan 2000 15:34:23 -0800
Date: Tue, 4 Jan 2000 15:34:23 -0800 (PST)
From: Karl Auerbach <karl@CaveBear.com>
Reply-To: Karl Auerbach <karl@CaveBear.com>
To: Rick H Wesson <wessorh@ar.com>
cc: Ed Gerck <egerck@nma.com>,
        Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
In-Reply-To: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
Message-ID: <Pine.LNX.4.10.10001041522220.3751-100000@npax.cavebear.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

 
> I am glad that NSI has published the I-D for their protocol, now does it
> need to go beyond that and become an RFC, IMHO, no.

Since I-Ds still officially vanish after a while, we need to move it to
RFC to maintain its visibility.  <Let's defer comments on the I-D fade out
policy.>

> The IETF does not need to publish broken implementations of one companies 
> view of the shared gTLD registration process.

We can learn from the flaws of the past.  And this RRP certainly gives us
a lot to learn from.

I would hope that having an Informational RFC on the RRP would motivate
some folks to think up, write down, and publish "A Better RRP".  Your own
work on the representing the whois data using XML is perhaps a good start.

(I can imagine that many sites with big zone files might find it useful to
have a tool using "A Better RRP" to distribute the administration of their
zone.)

By-the-way, I think that the IETF has already jumped through enough hoops
regarding the mis-perception by some that the letters "RFC" are some sort
of seal of approval.

		--karl--




From owner-ietf-outbound  Tue Jan  4 18:51:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA09791
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 18:50:02 -0500 (EST)
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09540;
	Tue, 4 Jan 2000 18:35:31 -0500 (EST)
Received: from v4j31 (ip12.proper.com [165.227.249.12])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id PAA16020;
	Tue, 4 Jan 2000 15:35:24 -0800 (PST)
Message-Id: <4.2.1.20000104152158.00a867e0@mail.imc.org>
X-Sender: phoffman@mail.imc.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 
Date: Tue, 04 Jan 2000 15:35:42 -0800
To: Rick H Wesson <wessorh@ar.com>, Ed Gerck <egerck@nma.com>
From: Paul Hoffman / IMC <phoffman@IMC.ORG>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0
  to  Informational
Cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
In-Reply-To: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
References: <38727013.DAF0AE16@nma.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 03:05 PM 1/4/00 -0800, Rick H Wesson wrote:
>The IETF does not need to publish broken implementations of one companies
>view of the shared gTLD registration process.

True. They don't need to do anything. They have the *option* of continuing 
the tradition of approving publication of Informational RFCs that document 
interesting (for some value of interesting) protocols that were not 
developed in the IETF but are of interest to the Internet community. In my 
mind NSI's RRP certainly qualifies. As long as the protocol does not 
directly harm the Internet on a technical level (not a political level; 
they all do that), the IESG might want to see it published.

Given the somewhat obvious nature of the protocol's faults, I would think 
that the community would welcome it being published openly and permanently; 
that way they can always refer to in while improving it.

>  Having an AD that sat on the
>RAB  promote the I-D

Sorry, but this is garbage. Nothing that Patrik said promotes the protocol.

>  and offer no reasoning as to why it
>*should be* published as an Informational RFC

He said that about three times; please re-read the past few messages with 
slightly clearer eyes.

>I would request that the IESG let this draft expire and create a WG to
>tackle the problem.

It is not clear that the IETF is the proper place to tackle this problem. 
 From the number of mistakes in the NSI RRP, I believe that a better way to 
create such a protocol is to start with a requirements document. A few 
folks have kicked around the idea of creating an IETF WG, but it became 
clear that the expertise to set down the *requirements* are more likely to 
be in the ICANN DNSO, not the IETF. That is, ask the registrars and 
registries, not a bunch of protocol-writers. After the requirements are 
settled, the IETF could probably help write the protocol.

Having those directly involved in the field set down the requirements first 
will delay the shipment of the new protocol, but it is very likely to cause 
the outcome to be much better for all involved. This has been shown again 
and again (with both positive and negative examples) in the IETF.

>The document exists as an I-D,
>the cat is out of the bag, why should it be an RFC?

To make it permanently and easily and freely accessible to the entire 
Internet community forever. There are many Informational RFCs that have 
been published for these reasons.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf-outbound@ietf.org  Tue Jan  4 18:52:03 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09841
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 18:52:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id SAA06187;
	Tue, 4 Jan 2000 18:50:42 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id SAA09791
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 18:50:02 -0500 (EST)
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09540;
	Tue, 4 Jan 2000 18:35:31 -0500 (EST)
Received: from v4j31 (ip12.proper.com [165.227.249.12])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id PAA16020;
	Tue, 4 Jan 2000 15:35:24 -0800 (PST)
Message-Id: <4.2.1.20000104152158.00a867e0@mail.imc.org>
X-Sender: phoffman@mail.imc.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 
Date: Tue, 04 Jan 2000 15:35:42 -0800
To: Rick H Wesson <wessorh@ar.com>, Ed Gerck <egerck@nma.com>
From: Paul Hoffman / IMC <phoffman@IMC.ORG>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0
  to  Informational
Cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
In-Reply-To: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
References: <38727013.DAF0AE16@nma.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 03:05 PM 1/4/00 -0800, Rick H Wesson wrote:
>The IETF does not need to publish broken implementations of one companies
>view of the shared gTLD registration process.

True. They don't need to do anything. They have the *option* of continuing 
the tradition of approving publication of Informational RFCs that document 
interesting (for some value of interesting) protocols that were not 
developed in the IETF but are of interest to the Internet community. In my 
mind NSI's RRP certainly qualifies. As long as the protocol does not 
directly harm the Internet on a technical level (not a political level; 
they all do that), the IESG might want to see it published.

Given the somewhat obvious nature of the protocol's faults, I would think 
that the community would welcome it being published openly and permanently; 
that way they can always refer to in while improving it.

>  Having an AD that sat on the
>RAB  promote the I-D

Sorry, but this is garbage. Nothing that Patrik said promotes the protocol.

>  and offer no reasoning as to why it
>*should be* published as an Informational RFC

He said that about three times; please re-read the past few messages with 
slightly clearer eyes.

>I would request that the IESG let this draft expire and create a WG to
>tackle the problem.

It is not clear that the IETF is the proper place to tackle this problem. 
 From the number of mistakes in the NSI RRP, I believe that a better way to 
create such a protocol is to start with a requirements document. A few 
folks have kicked around the idea of creating an IETF WG, but it became 
clear that the expertise to set down the *requirements* are more likely to 
be in the ICANN DNSO, not the IETF. That is, ask the registrars and 
registries, not a bunch of protocol-writers. After the requirements are 
settled, the IETF could probably help write the protocol.

Having those directly involved in the field set down the requirements first 
will delay the shipment of the new protocol, but it is very likely to cause 
the outcome to be much better for all involved. This has been shown again 
and again (with both positive and negative examples) in the IETF.

>The document exists as an I-D,
>the cat is out of the bag, why should it be an RFC?

To make it permanently and easily and freely accessible to the entire 
Internet community forever. There are many Informational RFCs that have 
been published for these reasons.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf-outbound  Tue Jan  4 19:01:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA09931
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 19:00:05 -0500 (EST)
Received: from ibd.ar.com (adsl-63-194-205-77.dsl.snfc21.pacbell.net [63.194.205.77])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09884
	for <ietf@ietf.org>; Tue, 4 Jan 2000 18:58:40 -0500 (EST)
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id PAA01905;
	Tue, 4 Jan 2000 15:58:35 -0800 (PST)
Date: Tue, 4 Jan 2000 15:58:37 -0800 (PST)
From: Rick H Wesson <wessorh@ar.com>
To: Paul Hoffman / IMC <phoffman@IMC.ORG>
cc: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0  to
  Informational
In-Reply-To: <4.2.1.20000104152158.00a867e0@mail.imc.org>
Message-ID: <Pine.LNX.4.10.10001041549290.28714-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Paul,

In short you are suggesting that the I-D be published to document a
bad but current practice? It seems counter-intutative but I am certainly
not "in the know" as to how these things work.

think the IESG could at least put a "bad bad protocol" sitcker on it when
they its published, or better yet give it a negative RFC number starting with 
negative RFC numbers would at least put it firmly into the minds of
readers that the RFc should *not* be followed.

I doubt I'd implement RFC -1 ;-)

regards,

-rick


On Tue, 4 Jan 2000, Paul Hoffman / IMC wrote:

> At 03:05 PM 1/4/00 -0800, Rick H Wesson wrote:
> >The IETF does not need to publish broken implementations of one companies
> >view of the shared gTLD registration process.
> 
> True. They don't need to do anything. They have the *option* of continuing 
> the tradition of approving publication of Informational RFCs that document 
> interesting (for some value of interesting) protocols that were not 
> developed in the IETF but are of interest to the Internet community. In my 
> mind NSI's RRP certainly qualifies. As long as the protocol does not 
> directly harm the Internet on a technical level (not a political level; 
> they all do that), the IESG might want to see it published.



From owner-ietf-outbound@ietf.org  Tue Jan  4 19:02:19 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10044
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 19:02:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id TAA06415;
	Tue, 4 Jan 2000 19:00:53 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA09931
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 19:00:05 -0500 (EST)
Received: from ibd.ar.com (adsl-63-194-205-77.dsl.snfc21.pacbell.net [63.194.205.77])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09884
	for <ietf@ietf.org>; Tue, 4 Jan 2000 18:58:40 -0500 (EST)
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id PAA01905;
	Tue, 4 Jan 2000 15:58:35 -0800 (PST)
Date: Tue, 4 Jan 2000 15:58:37 -0800 (PST)
From: Rick H Wesson <wessorh@ar.com>
To: Paul Hoffman / IMC <phoffman@IMC.ORG>
cc: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0  to
  Informational
In-Reply-To: <4.2.1.20000104152158.00a867e0@mail.imc.org>
Message-ID: <Pine.LNX.4.10.10001041549290.28714-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Paul,

In short you are suggesting that the I-D be published to document a
bad but current practice? It seems counter-intutative but I am certainly
not "in the know" as to how these things work.

think the IESG could at least put a "bad bad protocol" sitcker on it when
they its published, or better yet give it a negative RFC number starting with 
negative RFC numbers would at least put it firmly into the minds of
readers that the RFc should *not* be followed.

I doubt I'd implement RFC -1 ;-)

regards,

-rick


On Tue, 4 Jan 2000, Paul Hoffman / IMC wrote:

> At 03:05 PM 1/4/00 -0800, Rick H Wesson wrote:
> >The IETF does not need to publish broken implementations of one companies
> >view of the shared gTLD registration process.
> 
> True. They don't need to do anything. They have the *option* of continuing 
> the tradition of approving publication of Informational RFCs that document 
> interesting (for some value of interesting) protocols that were not 
> developed in the IETF but are of interest to the Internet community. In my 
> mind NSI's RRP certainly qualifies. As long as the protocol does not 
> directly harm the Internet on a technical level (not a political level; 
> they all do that), the IESG might want to see it published.



From owner-ietf-outbound  Tue Jan  4 19:11:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA10184
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 19:10:03 -0500 (EST)
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10148
	for <ietf@ietf.org>; Tue, 4 Jan 2000 19:09:38 -0500 (EST)
Received: from v4j31 (ip12.proper.com [165.227.249.12])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id QAA16394;
	Tue, 4 Jan 2000 16:09:38 -0800 (PST)
Message-Id: <4.2.1.20000104160631.00a962a0@mail.imc.org>
X-Sender: phoffman@mail.imc.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 
Date: Tue, 04 Jan 2000 16:09:56 -0800
To: Rick H Wesson <wessorh@ar.com>
From: Paul Hoffman / IMC <phoffman@IMC.ORG>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0
   to Informational
Cc: ietf@ietf.org
In-Reply-To: <Pine.LNX.4.10.10001041549290.28714-100000@loki.ar.com>
References: <4.2.1.20000104152158.00a867e0@mail.imc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 03:58 PM 1/4/00 -0800, Rick H Wesson wrote:
>In short you are suggesting that the I-D be published to document a
>bad but current practice?

A review of the Informational RFCs issued in the past few years would 
reveal a few RFCs that match that description quite well.

>  It seems counter-intutative but I am certainly
>not "in the know" as to how these things work.

It is a bit counter-intuitive until you look at the alternative. There 
isn't a good, central, free, open repository for these things other than 
RFCs. This isn't to say that every protocol should go there. I would say 
that only "important" (either due to politics or the number of 
implementations using the protocol) protocols should qualify.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf-outbound@ietf.org  Tue Jan  4 19:12:33 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10253
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 19:12:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id TAA06829;
	Tue, 4 Jan 2000 19:11:09 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA10184
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 19:10:03 -0500 (EST)
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10148
	for <ietf@ietf.org>; Tue, 4 Jan 2000 19:09:38 -0500 (EST)
Received: from v4j31 (ip12.proper.com [165.227.249.12])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id QAA16394;
	Tue, 4 Jan 2000 16:09:38 -0800 (PST)
Message-Id: <4.2.1.20000104160631.00a962a0@mail.imc.org>
X-Sender: phoffman@mail.imc.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 
Date: Tue, 04 Jan 2000 16:09:56 -0800
To: Rick H Wesson <wessorh@ar.com>
From: Paul Hoffman / IMC <phoffman@IMC.ORG>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0
   to Informational
Cc: ietf@ietf.org
In-Reply-To: <Pine.LNX.4.10.10001041549290.28714-100000@loki.ar.com>
References: <4.2.1.20000104152158.00a867e0@mail.imc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 03:58 PM 1/4/00 -0800, Rick H Wesson wrote:
>In short you are suggesting that the I-D be published to document a
>bad but current practice?

A review of the Informational RFCs issued in the past few years would 
reveal a few RFCs that match that description quite well.

>  It seems counter-intutative but I am certainly
>not "in the know" as to how these things work.

It is a bit counter-intuitive until you look at the alternative. There 
isn't a good, central, free, open repository for these things other than 
RFCs. This isn't to say that every protocol should go there. I would say 
that only "important" (either due to politics or the number of 
implementations using the protocol) protocols should qualify.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf-outbound  Tue Jan  4 19:41:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA10560
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 19:40:03 -0500 (EST)
Received: from ib.rc.vix.com (ib.rc.vix.com [204.152.187.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10369;
	Tue, 4 Jan 2000 19:30:09 -0500 (EST)
Received: from bb.rc.vix.com (bb.rc.vix.com [204.152.187.11]) 
	by ib.rc.vix.com (8.9.1/8.9.1) via ESMTP id QAA04299; Tue, 4 Jan 2000 16:29:33 -0800 (PST)
	env-from (David.Conrad@iengines.com)
Received: from iengines.com (bb.rc.vix.com [204.152.187.11]) 
	by bb.rc.vix.com (8.9.1/8.9.1) via ESMTP id QAA04355; Tue, 4 Jan 2000 16:29:33 -0800 (PST)
	env-from (David.Conrad@iengines.com)
Message-ID: <3872906C.C861FDDF@iengines.com>
Date: Tue, 04 Jan 2000 16:29:32 -0800
From: "David R. Conrad" <David.Conrad@iengines.com>
Organization: Internet Engines, Inc.
X-Mailer: Mozilla 4.61 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: Rick H Wesson <wessorh@ar.com>
CC: Ed Gerck <egerck@nma.com>,
        "Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=" 
	<paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
References: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Rick,

> I hate to add a "me too" but I must. I believe that the RAB minutes would
> be very useful if they were published. 

Has any other organization interested in publishing an informational RFC
needed to also publish the internal discussions that led to the implementation
of their proprietary protocol?

> I am glad that NSI has published the I-D for their protocol, now does it
> need to go beyond that and become an RFC, IMHO, no.

I-Ds expire.
 
> The IETF does not need to publish broken implementations of one companies
> view of the shared gTLD registration process. 

Then you were unhappy that (oh, say) Cisco submitted RFC 2281 as an
informational RFC (not saying HSRP is "broken", but I'm sure someone would).

> Having an AD that sat on the
> RAB  promote the I-D and offer no reasoning as to why it
> *should be* published as an Informational RFC reminds me of the bad taste
> left by the IAHC and all the processes related.

I find this offensive.  I was among those who encouraged NSI to publish the
RRP as an informational RFC as I felt it would be in the best interests of
everybody to have the RRP protocol publically examined and I feel NSI should
be commended for documenting their protocol.  However, INFORMATIONAL RFCS DO
NOT IMPLY ENDORSEMENT.  The draft is a representation of an existing, in use
proprietary protocol.  No further justification should be necessary for
documenting it as an informational RFC.
 
Rgds,
-drc



From owner-ietf-outbound@ietf.org  Tue Jan  4 19:42:28 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10626
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 19:42:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id TAA08344;
	Tue, 4 Jan 2000 19:41:01 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA10560
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 19:40:03 -0500 (EST)
Received: from ib.rc.vix.com (ib.rc.vix.com [204.152.187.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10369;
	Tue, 4 Jan 2000 19:30:09 -0500 (EST)
Received: from bb.rc.vix.com (bb.rc.vix.com [204.152.187.11]) 
	by ib.rc.vix.com (8.9.1/8.9.1) via ESMTP id QAA04299; Tue, 4 Jan 2000 16:29:33 -0800 (PST)
	env-from (David.Conrad@iengines.com)
Received: from iengines.com (bb.rc.vix.com [204.152.187.11]) 
	by bb.rc.vix.com (8.9.1/8.9.1) via ESMTP id QAA04355; Tue, 4 Jan 2000 16:29:33 -0800 (PST)
	env-from (David.Conrad@iengines.com)
Message-ID: <3872906C.C861FDDF@iengines.com>
Date: Tue, 04 Jan 2000 16:29:32 -0800
From: "David R. Conrad" <David.Conrad@iengines.com>
Organization: Internet Engines, Inc.
X-Mailer: Mozilla 4.61 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: Rick H Wesson <wessorh@ar.com>
CC: Ed Gerck <egerck@nma.com>,
        "Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=" 
	<paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
References: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Rick,

> I hate to add a "me too" but I must. I believe that the RAB minutes would
> be very useful if they were published. 

Has any other organization interested in publishing an informational RFC
needed to also publish the internal discussions that led to the implementation
of their proprietary protocol?

> I am glad that NSI has published the I-D for their protocol, now does it
> need to go beyond that and become an RFC, IMHO, no.

I-Ds expire.
 
> The IETF does not need to publish broken implementations of one companies
> view of the shared gTLD registration process. 

Then you were unhappy that (oh, say) Cisco submitted RFC 2281 as an
informational RFC (not saying HSRP is "broken", but I'm sure someone would).

> Having an AD that sat on the
> RAB  promote the I-D and offer no reasoning as to why it
> *should be* published as an Informational RFC reminds me of the bad taste
> left by the IAHC and all the processes related.

I find this offensive.  I was among those who encouraged NSI to publish the
RRP as an informational RFC as I felt it would be in the best interests of
everybody to have the RRP protocol publically examined and I feel NSI should
be commended for documenting their protocol.  However, INFORMATIONAL RFCS DO
NOT IMPLY ENDORSEMENT.  The draft is a representation of an existing, in use
proprietary protocol.  No further justification should be necessary for
documenting it as an informational RFC.
 
Rgds,
-drc



From owner-ietf-outbound  Tue Jan  4 20:40:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA11067
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 20:40:02 -0500 (EST)
Received: from dfw-smtpout3.email.verio.net (dfw-smtpout3.email.verio.net [129.250.36.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11015;
	Tue, 4 Jan 2000 20:36:52 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125fNX-0006B8-00; Wed, 05 Jan 2000 01:36:47 +0000
Received: from [209.21.28.113] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125fMs-0004wZ-00; Wed, 05 Jan 2000 01:36:07 +0000
Message-ID: <3872A06C.886EF997@nma.com>
Date: Tue, 04 Jan 2000 17:37:48 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "David R. Conrad" <David.Conrad@iengines.com>
CC: Rick H Wesson <wessorh@ar.com>,
        "Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=" 
	<paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
References: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com> <3872906C.C861FDDF@iengines.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



"David R. Conrad" wrote:

> I was among those who encouraged NSI to publish the
> RRP as an informational RFC as I felt it would be in the best interests of
> everybody to have the RRP protocol publically examined and I feel NSI should
> be commended for documenting their protocol.

I too encouraged NSI to publish the RRP protocol, and I believe I was actually
the first that said so to NSI.  This is however IMO irrelevant here -- the issue is what
is being presented by NSI to be an informational IETF RFC, not whether we should
commend  NSI for doing or not doing anything in their own benefit.  This is yet not
the Internet Marketing Study Group.

Given the secret (but not private) nature of the RAB Meeting Minutes, I am effectively
barred to comment further  -- even though I would just be repeating my own comments.
However, to anyone versed in technical work it is clear that if the references to a work
are missing, and if those references actually *deny* the work being presented, then
there is  something basically wrong with the entire process. This is what happens here
and that is why I am not convinced that the NSI RFC should be published by the IETF
unless the very references to that work which resulted from a US Government contract
be made available and public as well, as "supporting" documentation missing in the
RFC.

Note also that the RAB, its meeting Minutes and its Action Points are also not the
result of an NSI private initiative as we know, Conrad, but an obligation upon NSI by
an  oversight body and a regulating US agency in a legal contract.  I imagine that the
Freedom of Information Act could be used to make those notes public since they
were mandated by the direct act of a US agency, who also has copies of them.  And I
see no benefit to the Internet community if they continue to be secret to some (RAB,
NSI, USG, ICANN) while the  RRP that they comment on intends to be published by
the IETF -- without the comments!  So, on a more humorous tone, this is not a RFC as a
"Request For Comments" ...  this is a "Requiem For Comments" ;-)

Cheers,

Ed Gerck



From owner-ietf-outbound@ietf.org  Tue Jan  4 20:41:49 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11123
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 20:41:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id UAA10211;
	Tue, 4 Jan 2000 20:40:23 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id UAA11067
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 20:40:02 -0500 (EST)
Received: from dfw-smtpout3.email.verio.net (dfw-smtpout3.email.verio.net [129.250.36.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11015;
	Tue, 4 Jan 2000 20:36:52 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125fNX-0006B8-00; Wed, 05 Jan 2000 01:36:47 +0000
Received: from [209.21.28.113] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125fMs-0004wZ-00; Wed, 05 Jan 2000 01:36:07 +0000
Message-ID: <3872A06C.886EF997@nma.com>
Date: Tue, 04 Jan 2000 17:37:48 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "David R. Conrad" <David.Conrad@iengines.com>
CC: Rick H Wesson <wessorh@ar.com>,
        "Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=" 
	<paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
References: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com> <3872906C.C861FDDF@iengines.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



"David R. Conrad" wrote:

> I was among those who encouraged NSI to publish the
> RRP as an informational RFC as I felt it would be in the best interests of
> everybody to have the RRP protocol publically examined and I feel NSI should
> be commended for documenting their protocol.

I too encouraged NSI to publish the RRP protocol, and I believe I was actually
the first that said so to NSI.  This is however IMO irrelevant here -- the issue is what
is being presented by NSI to be an informational IETF RFC, not whether we should
commend  NSI for doing or not doing anything in their own benefit.  This is yet not
the Internet Marketing Study Group.

Given the secret (but not private) nature of the RAB Meeting Minutes, I am effectively
barred to comment further  -- even though I would just be repeating my own comments.
However, to anyone versed in technical work it is clear that if the references to a work
are missing, and if those references actually *deny* the work being presented, then
there is  something basically wrong with the entire process. This is what happens here
and that is why I am not convinced that the NSI RFC should be published by the IETF
unless the very references to that work which resulted from a US Government contract
be made available and public as well, as "supporting" documentation missing in the
RFC.

Note also that the RAB, its meeting Minutes and its Action Points are also not the
result of an NSI private initiative as we know, Conrad, but an obligation upon NSI by
an  oversight body and a regulating US agency in a legal contract.  I imagine that the
Freedom of Information Act could be used to make those notes public since they
were mandated by the direct act of a US agency, who also has copies of them.  And I
see no benefit to the Internet community if they continue to be secret to some (RAB,
NSI, USG, ICANN) while the  RRP that they comment on intends to be published by
the IETF -- without the comments!  So, on a more humorous tone, this is not a RFC as a
"Request For Comments" ...  this is a "Requiem For Comments" ;-)

Cheers,

Ed Gerck



From owner-ietf-outbound  Tue Jan  4 20:50:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA11213
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 20:50:02 -0500 (EST)
Received: from mx.seanet.com (dns2.seanet.com [199.181.164.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11030
	for <ietf@ietf.org>; Tue, 4 Jan 2000 20:37:38 -0500 (EST)
Received: from gwz (p21.dialup.seanet.com [207.12.130.117]) by mx.seanet.com (8.9.3/Seanet-8.7.3) with SMTP id RAA22481; Tue, 4 Jan 2000 17:37:26 -0800 (PST)
Message-ID: <000d01bf571d$a112dfa0$6665a8c0@seanet.com>
From: "Glen Zorn" <gwz@seanet.com>
To: "Alan Blount" <blount@media.mit.edu>, <ietf@ietf.org>
Cc: <blount@media.mit.edu>
References: <200001041947.OAA25197@ml.media.mit.edu>
Subject: Re: I-D nroff macros
Date: Tue, 4 Jan 2000 17:38:54 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Alan Blount <blount@media.mit.edu> writes:

> I've been using the simple set of nroff macros, as described by
>
>   http://www.ietf.org/internet-drafts/2-nroff.template
>
> While this works, I'd like to be able to autogenerate section numbers
> and table of contents entries.  This draft doesn't give any guidance.
> I tried the -ms macros, as described by
>
>   http://www.cs.berkeley.edu/%7Ejanp/Help/textms.html
>
> but the header macro .NH creates the header in boldface, which is a
> no-no according to RFC 2223.
>
> I imagine there is a way to do this, but I am ignorant of the
> necessary kung-fu.  Does anyone have a sample nroff file, perhaps a
> draft they've written, that generates heading numbers and a toc?

There are a couple of ways to do it, either by rolling your own macros or by
making a minor change to the ms macros themselves (the approach I took).  I
can send you my macro package if you like; however, it doesn't do automatic
TOC processing.

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



From owner-ietf-outbound@ietf.org  Tue Jan  4 20:51:22 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11261
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 20:51:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id UAA10390;
	Tue, 4 Jan 2000 20:49:56 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id UAA11213
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 20:50:02 -0500 (EST)
Received: from mx.seanet.com (dns2.seanet.com [199.181.164.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11030
	for <ietf@ietf.org>; Tue, 4 Jan 2000 20:37:38 -0500 (EST)
Received: from gwz (p21.dialup.seanet.com [207.12.130.117]) by mx.seanet.com (8.9.3/Seanet-8.7.3) with SMTP id RAA22481; Tue, 4 Jan 2000 17:37:26 -0800 (PST)
Message-ID: <000d01bf571d$a112dfa0$6665a8c0@seanet.com>
From: "Glen Zorn" <gwz@seanet.com>
To: "Alan Blount" <blount@media.mit.edu>, <ietf@ietf.org>
Cc: <blount@media.mit.edu>
References: <200001041947.OAA25197@ml.media.mit.edu>
Subject: Re: I-D nroff macros
Date: Tue, 4 Jan 2000 17:38:54 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Alan Blount <blount@media.mit.edu> writes:

> I've been using the simple set of nroff macros, as described by
>
>   http://www.ietf.org/internet-drafts/2-nroff.template
>
> While this works, I'd like to be able to autogenerate section numbers
> and table of contents entries.  This draft doesn't give any guidance.
> I tried the -ms macros, as described by
>
>   http://www.cs.berkeley.edu/%7Ejanp/Help/textms.html
>
> but the header macro .NH creates the header in boldface, which is a
> no-no according to RFC 2223.
>
> I imagine there is a way to do this, but I am ignorant of the
> necessary kung-fu.  Does anyone have a sample nroff file, perhaps a
> draft they've written, that generates heading numbers and a toc?

There are a couple of ways to do it, either by rolling your own macros or by
making a minor change to the ms macros themselves (the approach I took).  I
can send you my macro package if you like; however, it doesn't do automatic
TOC processing.

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



From owner-ietf-outbound  Tue Jan  4 21:00:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA11329
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 21:00:02 -0500 (EST)
Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11150;
	Tue, 4 Jan 2000 20:42:58 -0500 (EST)
Received: from [192.168.0.1] (ipa53.trenton2.nj.pub-ip.psi.net [38.26.139.53])
	by eagle.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id RAA08970;
	Tue, 4 Jan 2000 17:42:45 -0800 (PST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <v04210102b49844c2f1c5@[192.168.0.1]>
In-Reply-To: <4.2.1.20000104152158.00a867e0@mail.imc.org>
References: <38727013.DAF0AE16@nma.com>
 <4.2.1.20000104152158.00a867e0@mail.imc.org>
Date: Tue, 4 Jan 2000 20:43:21 -0500
To: Paul Hoffman / IMC <phoffman@IMC.ORG>
From: Gordon Cook <cook@cookreport.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0  
 to  Informational
Cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@CAVEBEAR.COM>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

OK Paul, lets give you the benefit of the doubt and say that your 
assertions below are absolutely right.  Please explain then why it 
should become an informational RFC without having the comments of the 
RAB members attached to it? (Even though as Patrick said it is not 
common practice to do this with an informational rfc). Isn't this 
such an egregious and high profile example that the IESG out to 
choose to excercise some consumer protection here?  NSI's own panel 
of experts, its own RAB said the protocol was broken did they not? 
Yet NSI went ahead and implemented it anyway.  NSI is operating a 
flawed protocol to handle a registration process for  names that can 
now command huge sums of money?  The protocol is now under the 
stewardship of ICANN which so far is allowing something to operate 
which has a major potential to bring law suits down on its head .

Patrick who is now a member of the ICANN board and was a member of 
the RAB and thus has ample reason to know how badly the protocol has 
been designed is saying that the protocol should be published albeit 
as a LOWLY INFORMATIONAL RFC with nothing in the packaging to 
indicate that trouble lurks within?

Is it really the position of the IESG that they have NO obligation to 
do anything to inform the unwary that this protocol is an invitation 
for lawsuits against NSI, against ICANN, and possibly against the 
IETF on the grounds that the RFC publication was perceived by the 
clueless party  as an endorsement?

I just saw David Conrads statement and I understand the point he 
makes.  Still I wonder how wise the insistence is on hewing to old 
traditions in this case.  Where do Patrick's obligations fall?  To 
the IESG in holding his nose in saying we won't break precedent and 
even though we all undestand this is a series of disasters waiting to 
happen we will publish the sucker as we always to without further 
explanation?  Or as an ICANN Board  member does he have a legal and 
fiduciary duty to ICANN as a corporation to act in such a way to see 
thatin the future no internet ignorant corporation could  ever step 
forward and claim that - having been involved in the creation of a 
flawed product - he had a duty to ICANN to label it as flawed and 
should he chose not to he could find lawyers going after him.  How 
many ICANN board members understand what their personal legal 
liability is?





>At 03:05 PM 1/4/00 -0800, Rick H Wesson wrote:
>>The IETF does not need to publish broken implementations of one companies
>>view of the shared gTLD registration process.
>
>True. They don't need to do anything. They have the *option* of 
>continuing the tradition of approving publication of Informational 
>RFCs that document interesting (for some value of interesting) 
>protocols that were not developed in the IETF but are of interest to 
>the Internet community. In my mind NSI's RRP certainly qualifies. As 
>long as the protocol does not directly harm the Internet on a 
>technical level (not a political level; they all do that), the IESG 
>might want to see it published.
>
>Given the somewhat obvious nature of the protocol's faults, I would 
>think that the community would welcome it being published openly and 
>permanently; that way they can always refer to in while improving it.
>
>>Having an AD that sat on the
>>RAB  promote the I-D
>
>Sorry, but this is garbage. Nothing that Patrik said promotes the protocol.
>
>>and offer no reasoning as to why it
>>*should be* published as an Informational RFC
>
>He said that about three times; please re-read the past few messages 
>with slightly clearer eyes.
>
>>I would request that the IESG let this draft expire and create a WG to
>>tackle the problem.
>
>It is not clear that the IETF is the proper place to tackle this 
>problem. From the number of mistakes in the NSI RRP, I believe that 
>a better way to create such a protocol is to start with a 
>requirements document. A few folks have kicked around the idea of 
>creating an IETF WG, but it became clear that the expertise to set 
>down the *requirements* are more likely to be in the ICANN DNSO, not 
>the IETF. That is, ask the registrars and registries, not a bunch of 
>protocol-writers. After the requirements are settled, the IETF could 
>probably help write the protocol.
>
>Having those directly involved in the field set down the 
>requirements first will delay the shipment of the new protocol, but 
>it is very likely to cause the outcome to be much better for all 
>involved. This has been shown again and again (with both positive 
>and negative examples) in the IETF.
>
>>The document exists as an I-D,
>>the cat is out of the bag, why should it be an RFC?
>
>To make it permanently and easily and freely accessible to the 
>entire Internet community forever. There are many Informational RFCs 
>that have been published for these reasons.
>
>--Paul Hoffman, Director
>--Internet Mail Consortium

****************************************************************
The COOK Report on Internet            Index to seven years of the COOK Report
431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
(609) 882-2572 (phone & fax)            Is ICANN an IBM e-business ?
cook@cookreport.com                     See also Lessig's Code: and
Other  Laws of Cyberspace  http://cookreport.com/lessigbook.shtml
****************************************************************



From owner-ietf-outbound@ietf.org  Tue Jan  4 21:01:09 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11426
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 21:01:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id UAA10543;
	Tue, 4 Jan 2000 20:59:42 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA11329
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 21:00:02 -0500 (EST)
Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11150;
	Tue, 4 Jan 2000 20:42:58 -0500 (EST)
Received: from [192.168.0.1] (ipa53.trenton2.nj.pub-ip.psi.net [38.26.139.53])
	by eagle.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id RAA08970;
	Tue, 4 Jan 2000 17:42:45 -0800 (PST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <v04210102b49844c2f1c5@[192.168.0.1]>
In-Reply-To: <4.2.1.20000104152158.00a867e0@mail.imc.org>
References: <38727013.DAF0AE16@nma.com>
 <4.2.1.20000104152158.00a867e0@mail.imc.org>
Date: Tue, 4 Jan 2000 20:43:21 -0500
To: Paul Hoffman / IMC <phoffman@IMC.ORG>
From: Gordon Cook <cook@cookreport.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0  
 to  Informational
Cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@CAVEBEAR.COM>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

OK Paul, lets give you the benefit of the doubt and say that your 
assertions below are absolutely right.  Please explain then why it 
should become an informational RFC without having the comments of the 
RAB members attached to it? (Even though as Patrick said it is not 
common practice to do this with an informational rfc). Isn't this 
such an egregious and high profile example that the IESG out to 
choose to excercise some consumer protection here?  NSI's own panel 
of experts, its own RAB said the protocol was broken did they not? 
Yet NSI went ahead and implemented it anyway.  NSI is operating a 
flawed protocol to handle a registration process for  names that can 
now command huge sums of money?  The protocol is now under the 
stewardship of ICANN which so far is allowing something to operate 
which has a major potential to bring law suits down on its head .

Patrick who is now a member of the ICANN board and was a member of 
the RAB and thus has ample reason to know how badly the protocol has 
been designed is saying that the protocol should be published albeit 
as a LOWLY INFORMATIONAL RFC with nothing in the packaging to 
indicate that trouble lurks within?

Is it really the position of the IESG that they have NO obligation to 
do anything to inform the unwary that this protocol is an invitation 
for lawsuits against NSI, against ICANN, and possibly against the 
IETF on the grounds that the RFC publication was perceived by the 
clueless party  as an endorsement?

I just saw David Conrads statement and I understand the point he 
makes.  Still I wonder how wise the insistence is on hewing to old 
traditions in this case.  Where do Patrick's obligations fall?  To 
the IESG in holding his nose in saying we won't break precedent and 
even though we all undestand this is a series of disasters waiting to 
happen we will publish the sucker as we always to without further 
explanation?  Or as an ICANN Board  member does he have a legal and 
fiduciary duty to ICANN as a corporation to act in such a way to see 
thatin the future no internet ignorant corporation could  ever step 
forward and claim that - having been involved in the creation of a 
flawed product - he had a duty to ICANN to label it as flawed and 
should he chose not to he could find lawyers going after him.  How 
many ICANN board members understand what their personal legal 
liability is?





>At 03:05 PM 1/4/00 -0800, Rick H Wesson wrote:
>>The IETF does not need to publish broken implementations of one companies
>>view of the shared gTLD registration process.
>
>True. They don't need to do anything. They have the *option* of 
>continuing the tradition of approving publication of Informational 
>RFCs that document interesting (for some value of interesting) 
>protocols that were not developed in the IETF but are of interest to 
>the Internet community. In my mind NSI's RRP certainly qualifies. As 
>long as the protocol does not directly harm the Internet on a 
>technical level (not a political level; they all do that), the IESG 
>might want to see it published.
>
>Given the somewhat obvious nature of the protocol's faults, I would 
>think that the community would welcome it being published openly and 
>permanently; that way they can always refer to in while improving it.
>
>>Having an AD that sat on the
>>RAB  promote the I-D
>
>Sorry, but this is garbage. Nothing that Patrik said promotes the protocol.
>
>>and offer no reasoning as to why it
>>*should be* published as an Informational RFC
>
>He said that about three times; please re-read the past few messages 
>with slightly clearer eyes.
>
>>I would request that the IESG let this draft expire and create a WG to
>>tackle the problem.
>
>It is not clear that the IETF is the proper place to tackle this 
>problem. From the number of mistakes in the NSI RRP, I believe that 
>a better way to create such a protocol is to start with a 
>requirements document. A few folks have kicked around the idea of 
>creating an IETF WG, but it became clear that the expertise to set 
>down the *requirements* are more likely to be in the ICANN DNSO, not 
>the IETF. That is, ask the registrars and registries, not a bunch of 
>protocol-writers. After the requirements are settled, the IETF could 
>probably help write the protocol.
>
>Having those directly involved in the field set down the 
>requirements first will delay the shipment of the new protocol, but 
>it is very likely to cause the outcome to be much better for all 
>involved. This has been shown again and again (with both positive 
>and negative examples) in the IETF.
>
>>The document exists as an I-D,
>>the cat is out of the bag, why should it be an RFC?
>
>To make it permanently and easily and freely accessible to the 
>entire Internet community forever. There are many Informational RFCs 
>that have been published for these reasons.
>
>--Paul Hoffman, Director
>--Internet Mail Consortium

****************************************************************
The COOK Report on Internet            Index to seven years of the COOK Report
431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
(609) 882-2572 (phone & fax)            Is ICANN an IBM e-business ?
cook@cookreport.com                     See also Lessig's Code: and
Other  Laws of Cyberspace  http://cookreport.com/lessigbook.shtml
****************************************************************



From owner-ietf-outbound  Tue Jan  4 21:10:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA11524
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 21:10:02 -0500 (EST)
Received: from postman.bayarea.net (postman.bayarea.net [205.219.84.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11467;
	Tue, 4 Jan 2000 21:05:03 -0500 (EST)
Received: from dcrocker (free.88.106.bayarea.net [205.219.88.106])
	by postman.bayarea.net (8.9.3/8.9.3) with ESMTP id SAA63751;
	Tue, 4 Jan 2000 18:04:52 -0800 (PST)
	(envelope-from dcrocker@brandenburg.com)
Message-Id: <4.2.2.20000104174951.00b36520@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 04 Jan 2000 17:52:43 -0800
To: "David R. Conrad" <David.Conrad@iengines.com>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0
  to  Informational
Cc: Rick H Wesson <wessorh@ar.com>, Ed Gerck <egerck@nma.com>,
        "Patrik Fältström"  <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@CAVEBEAR.COM>
In-Reply-To: <3872906C.C861FDDF@iengines.com>
References: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 04:29 PM 1/4/2000 , David R. Conrad wrote:
> > I hate to add a "me too" but I must. I believe that the RAB minutes would
> > be very useful if they were published.
>Has any other organization interested in publishing an informational RFC
>needed to also publish the internal discussions that led to the implementation
>of their proprietary protocol?

No.

Informational RFCs for proprietary protocols have been published many 
times.  The IETF portion of the process to publish such documents is simply 
to ensure that we avoid confusion with IETF work.  That is amply obtained 
through the suggested title change.

The topic really does not warrant nearly as much discussion as it is getting.

d/

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA 



From owner-ietf-outbound@ietf.org  Tue Jan  4 21:11:35 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11579
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 21:11:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id VAA10847;
	Tue, 4 Jan 2000 21:10:09 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA11524
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 21:10:02 -0500 (EST)
Received: from postman.bayarea.net (postman.bayarea.net [205.219.84.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11467;
	Tue, 4 Jan 2000 21:05:03 -0500 (EST)
Received: from dcrocker (free.88.106.bayarea.net [205.219.88.106])
	by postman.bayarea.net (8.9.3/8.9.3) with ESMTP id SAA63751;
	Tue, 4 Jan 2000 18:04:52 -0800 (PST)
	(envelope-from dcrocker@brandenburg.com)
Message-Id: <4.2.2.20000104174951.00b36520@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 04 Jan 2000 17:52:43 -0800
To: "David R. Conrad" <David.Conrad@iengines.com>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0
  to  Informational
Cc: Rick H Wesson <wessorh@ar.com>, Ed Gerck <egerck@nma.com>,
        "Patrik Fältström"  <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@CAVEBEAR.COM>
In-Reply-To: <3872906C.C861FDDF@iengines.com>
References: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 04:29 PM 1/4/2000 , David R. Conrad wrote:
> > I hate to add a "me too" but I must. I believe that the RAB minutes would
> > be very useful if they were published.
>Has any other organization interested in publishing an informational RFC
>needed to also publish the internal discussions that led to the implementation
>of their proprietary protocol?

No.

Informational RFCs for proprietary protocols have been published many 
times.  The IETF portion of the process to publish such documents is simply 
to ensure that we avoid confusion with IETF work.  That is amply obtained 
through the suggested title change.

The topic really does not warrant nearly as much discussion as it is getting.

d/

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA 



From owner-ietf-outbound  Tue Jan  4 21:41:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA11929
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 21:40:03 -0500 (EST)
Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11890;
	Tue, 4 Jan 2000 21:38:32 -0500 (EST)
Received: from [192.168.0.1] (ipa85.trenton2.nj.pub-ip.psi.net [38.26.139.85])
	by eagle.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id SAA16665;
	Tue, 4 Jan 2000 18:38:22 -0800 (PST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <v04210106b4985c8a883b@[192.168.0.1]>
Date: Tue, 4 Jan 2000 21:38:56 -0500
To: Paul Hoffman / IMC <phoffman@IMC.ORG>
From: Gordon Cook <cook@cookreport.com>
Subject: oh merde!  <blush>  Patrick F. and ICANN board error
Cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=   <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@CAVEBEAR.COM>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

Wiping red face.....

   I carry a lot of ICANN data around in my head and I am generally 
pretty good at it.  However my attention has been called to the fact 
that I screwed up on my association with Patrick as an ICANN board 
member.  Following a few URL trails I see that he and Goeff Huston 
were IETF nominees but that ETSI and W3C placed their folk on the 
board and IETF would up with only Vint.

So apologies to Patrick for placing him on a hook where he does not belong.

Since Vint  as the IETF board member wasn't involved with creating 
the protocol, I'd imagine that it would be a lot harder for a lawyer 
to come after him....  Still I would think that he might have an 
interest in how this is handled.  ICANN may feel that it gets off 
scot free on this one but from my reading of some of the domain 
lists, a lot of people are beginning to ask what the hell ICANN is 
good for if it does nothing to police the screw ups from NSI's 
defective shared registry design.
****************************************************************
The COOK Report on Internet            Index to seven years of the COOK Report
431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
(609) 882-2572 (phone & fax)            Is ICANN an IBM e-business ?
cook@cookreport.com                     See also Lessig's Code: and
Other  Laws of Cyberspace  http://cookreport.com/lessigbook.shtml
****************************************************************



From owner-ietf-outbound@ietf.org  Tue Jan  4 21:43:45 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12219
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 21:43:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id VAA11522;
	Tue, 4 Jan 2000 21:42:21 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA11929
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 21:40:03 -0500 (EST)
Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11890;
	Tue, 4 Jan 2000 21:38:32 -0500 (EST)
Received: from [192.168.0.1] (ipa85.trenton2.nj.pub-ip.psi.net [38.26.139.85])
	by eagle.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id SAA16665;
	Tue, 4 Jan 2000 18:38:22 -0800 (PST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <v04210106b4985c8a883b@[192.168.0.1]>
Date: Tue, 4 Jan 2000 21:38:56 -0500
To: Paul Hoffman / IMC <phoffman@IMC.ORG>
From: Gordon Cook <cook@cookreport.com>
Subject: oh merde!  <blush>  Patrick F. and ICANN board error
Cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=   <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@CAVEBEAR.COM>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

Wiping red face.....

   I carry a lot of ICANN data around in my head and I am generally 
pretty good at it.  However my attention has been called to the fact 
that I screwed up on my association with Patrick as an ICANN board 
member.  Following a few URL trails I see that he and Goeff Huston 
were IETF nominees but that ETSI and W3C placed their folk on the 
board and IETF would up with only Vint.

So apologies to Patrick for placing him on a hook where he does not belong.

Since Vint  as the IETF board member wasn't involved with creating 
the protocol, I'd imagine that it would be a lot harder for a lawyer 
to come after him....  Still I would think that he might have an 
interest in how this is handled.  ICANN may feel that it gets off 
scot free on this one but from my reading of some of the domain 
lists, a lot of people are beginning to ask what the hell ICANN is 
good for if it does nothing to police the screw ups from NSI's 
defective shared registry design.
****************************************************************
The COOK Report on Internet            Index to seven years of the COOK Report
431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
(609) 882-2572 (phone & fax)            Is ICANN an IBM e-business ?
cook@cookreport.com                     See also Lessig's Code: and
Other  Laws of Cyberspace  http://cookreport.com/lessigbook.shtml
****************************************************************



From owner-ietf-outbound  Tue Jan  4 21:51:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA12972
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 21:50:02 -0500 (EST)
Received: from ibd.ar.com (adsl-63-194-205-77.dsl.snfc21.pacbell.net [63.194.205.77])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11907
	for <ietf@ietf.org>; Tue, 4 Jan 2000 21:38:54 -0500 (EST)
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id SAA02154;
	Tue, 4 Jan 2000 18:38:50 -0800 (PST)
Date: Tue, 4 Jan 2000 18:38:51 -0800 (PST)
From: Rick H Wesson <wessorh@ar.com>
To: "David R. Conrad" <David.Conrad@iengines.com>
cc: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
In-Reply-To: <3872906C.C861FDDF@iengines.com>
Message-ID: <Pine.LNX.4.10.10001041656180.28714-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


David,

I appologise if you found my comments offensive, they were not intend to
be. I'm gald you encouraged NSI to publish RRP, I'm gald they published
it. I also needed to discuss with the RAB issues about RRP durring the
testbed but was prevented by NSI by NDA. Remember in Berlin I asked if I
could talk to the RAB and that the testbed registrars have some problems
with RRP?

We all know that the entire development of rrp was sub-optimal and yes
Informational does not implay Endorsement but that is a fact that most of
the world does not understand and is an entirely different thread.

I have atempted as have others to outline many issues we have had with the
RRP protocol and its developemnt. I realy can't do more than that. 

-rick


On Tue, 4 Jan 2000, David R. Conrad wrote:

> I find this offensive.  I was among those who encouraged NSI to publish the
> RRP as an informational RFC as I felt it would be in the best interests of
> everybody to have the RRP protocol publically examined and I feel NSI should
> be commended for documenting their protocol.  However, INFORMATIONAL RFCS DO
> NOT IMPLY ENDORSEMENT.  The draft is a representation of an existing, in use
> proprietary protocol.  No further justification should be necessary for
> documenting it as an informational RFC.






From owner-ietf-outbound@ietf.org  Tue Jan  4 21:52:50 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13048
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 21:52:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id VAA11695;
	Tue, 4 Jan 2000 21:51:26 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA12972
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 21:50:02 -0500 (EST)
Received: from ibd.ar.com (adsl-63-194-205-77.dsl.snfc21.pacbell.net [63.194.205.77])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11907
	for <ietf@ietf.org>; Tue, 4 Jan 2000 21:38:54 -0500 (EST)
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id SAA02154;
	Tue, 4 Jan 2000 18:38:50 -0800 (PST)
Date: Tue, 4 Jan 2000 18:38:51 -0800 (PST)
From: Rick H Wesson <wessorh@ar.com>
To: "David R. Conrad" <David.Conrad@iengines.com>
cc: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
In-Reply-To: <3872906C.C861FDDF@iengines.com>
Message-ID: <Pine.LNX.4.10.10001041656180.28714-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


David,

I appologise if you found my comments offensive, they were not intend to
be. I'm gald you encouraged NSI to publish RRP, I'm gald they published
it. I also needed to discuss with the RAB issues about RRP durring the
testbed but was prevented by NSI by NDA. Remember in Berlin I asked if I
could talk to the RAB and that the testbed registrars have some problems
with RRP?

We all know that the entire development of rrp was sub-optimal and yes
Informational does not implay Endorsement but that is a fact that most of
the world does not understand and is an entirely different thread.

I have atempted as have others to outline many issues we have had with the
RRP protocol and its developemnt. I realy can't do more than that. 

-rick


On Tue, 4 Jan 2000, David R. Conrad wrote:

> I find this offensive.  I was among those who encouraged NSI to publish the
> RRP as an informational RFC as I felt it would be in the best interests of
> everybody to have the RRP protocol publically examined and I feel NSI should
> be commended for documenting their protocol.  However, INFORMATIONAL RFCS DO
> NOT IMPLY ENDORSEMENT.  The draft is a representation of an existing, in use
> proprietary protocol.  No further justification should be necessary for
> documenting it as an informational RFC.






From owner-ietf-outbound  Tue Jan  4 22:31:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA13462
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 22:30:03 -0500 (EST)
Received: from isrv3.isc.org (isrv3.isc.org [204.152.184.87])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13422;
	Tue, 4 Jan 2000 22:29:02 -0500 (EST)
Received: from bb.rc.vix.com (bb.rc.vix.com [204.152.187.11]) 
	by isrv3.isc.org (8.9.1/8.9.1) via ESMTP id TAA10600; Tue, 4 Jan 2000 19:28:29 -0800 (PST)
	env-from (David.Conrad@iengines.com)
Received: from iengines.com (bb.rc.vix.com [204.152.187.11]) 
	by bb.rc.vix.com (8.9.1/8.9.1) via ESMTP id TAA17072; Tue, 4 Jan 2000 19:28:27 -0800 (PST)
	env-from (David.Conrad@iengines.com)
Message-ID: <3872BA5A.CDC2E1A1@iengines.com>
Date: Tue, 04 Jan 2000 19:28:26 -0800
From: "David R. Conrad" <David.Conrad@iengines.com>
Organization: Internet Engines, Inc.
X-Mailer: Mozilla 4.61 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: Ed Gerck <egerck@nma.com>
CC: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson 
	<wessorh@ar.com>,
        Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott 
	Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach 
	<karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
References: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com> <3872906C.C861FDDF@iengines.com> <3872A06C.886EF997@nma.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Ed,

> the issue is what
> is being presented by NSI to be an informational IETF RFC, not whether 
> we should commend  NSI for doing or not doing anything in their own 
> benefit.  This is yet not the Internet Marketing Study Group.

Nor is it the Internet Inquisition ("No one expects the Internet
Inquistion...").  NSI was under no obligation to publish the RRP.  That they
have done so is to the benefit of folks who are interested in this sort of
thing.  Requiring anyone who submits a proprietary protocol to the IETF for
publication as an informational RFC to also publish the minutes of internal
discussions that led to the development of that protocol sounds like a really
good way to keep anyone from publishing proprietary protocols.

NSI should be treated no differently than others who publish proprietary
protocols as an informational RFC.
 
> However, to anyone versed in technical work it is clear that if the 
> references to a work are missing, and if those references actually 
> *deny* the work being presented, then there is  something basically 
> wrong with the entire process. 

You might want to acquaint yourself with the process before declaring it
"wrong".

> Note also that the RAB, its meeting Minutes and its Action Points are also 
> not the result of an NSI private initiative as we know, Conrad, but an 
> obligation upon NSI by an  oversight body and a regulating US agency in a 
> legal contract.  

While it is true, Gerck, that the RRP is a requirement of the Amendment 11, I
do not believe NSI was under any obligation to publish _anything_ outside of a
license agreement with NSI and, in fact, the USG is required "to protect the
confidentiality of such data, software and documentation so delivered".

Rgds,
-drc



From owner-ietf-outbound@ietf.org  Tue Jan  4 22:32:29 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14217
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 22:32:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id WAA12552;
	Tue, 4 Jan 2000 22:31:06 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id WAA13462
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 22:30:03 -0500 (EST)
Received: from isrv3.isc.org (isrv3.isc.org [204.152.184.87])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13422;
	Tue, 4 Jan 2000 22:29:02 -0500 (EST)
Received: from bb.rc.vix.com (bb.rc.vix.com [204.152.187.11]) 
	by isrv3.isc.org (8.9.1/8.9.1) via ESMTP id TAA10600; Tue, 4 Jan 2000 19:28:29 -0800 (PST)
	env-from (David.Conrad@iengines.com)
Received: from iengines.com (bb.rc.vix.com [204.152.187.11]) 
	by bb.rc.vix.com (8.9.1/8.9.1) via ESMTP id TAA17072; Tue, 4 Jan 2000 19:28:27 -0800 (PST)
	env-from (David.Conrad@iengines.com)
Message-ID: <3872BA5A.CDC2E1A1@iengines.com>
Date: Tue, 04 Jan 2000 19:28:26 -0800
From: "David R. Conrad" <David.Conrad@iengines.com>
Organization: Internet Engines, Inc.
X-Mailer: Mozilla 4.61 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: Ed Gerck <egerck@nma.com>
CC: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson 
	<wessorh@ar.com>,
        Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott 
	Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach 
	<karl@cavebear.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
References: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com> <3872906C.C861FDDF@iengines.com> <3872A06C.886EF997@nma.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Ed,

> the issue is what
> is being presented by NSI to be an informational IETF RFC, not whether 
> we should commend  NSI for doing or not doing anything in their own 
> benefit.  This is yet not the Internet Marketing Study Group.

Nor is it the Internet Inquisition ("No one expects the Internet
Inquistion...").  NSI was under no obligation to publish the RRP.  That they
have done so is to the benefit of folks who are interested in this sort of
thing.  Requiring anyone who submits a proprietary protocol to the IETF for
publication as an informational RFC to also publish the minutes of internal
discussions that led to the development of that protocol sounds like a really
good way to keep anyone from publishing proprietary protocols.

NSI should be treated no differently than others who publish proprietary
protocols as an informational RFC.
 
> However, to anyone versed in technical work it is clear that if the 
> references to a work are missing, and if those references actually 
> *deny* the work being presented, then there is  something basically 
> wrong with the entire process. 

You might want to acquaint yourself with the process before declaring it
"wrong".

> Note also that the RAB, its meeting Minutes and its Action Points are also 
> not the result of an NSI private initiative as we know, Conrad, but an 
> obligation upon NSI by an  oversight body and a regulating US agency in a 
> legal contract.  

While it is true, Gerck, that the RRP is a requirement of the Amendment 11, I
do not believe NSI was under any obligation to publish _anything_ outside of a
license agreement with NSI and, in fact, the USG is required "to protect the
confidentiality of such data, software and documentation so delivered".

Rgds,
-drc



From owner-ietf-outbound  Tue Jan  4 23:11:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA14833
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 23:10:02 -0500 (EST)
Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14808
	for <ietf@ietf.org>; Tue, 4 Jan 2000 23:05:23 -0500 (EST)
Received: from dns.maillennium.att.com ([135.25.114.99])
	by almso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id XAA01792
	for <ietf@ietf.org>; Tue, 4 Jan 2000 23:04:52 -0500 (EST)
Received: from att.com ([135.197.86.61])
          by maillennium.att.com (labmail) with SMTP
          id <20000105040231099244725ne>; Wed, 5 Jan 2000 04:02:32 +0000
Message-ID: <3872C28A.537C118@att.com>
Date: Tue, 04 Jan 2000 23:03:22 -0500
From: Tony Hansen <tony@att.com>
Organization: AT&T Laboratories
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Glen Zorn <gwz@seanet.com>
CC: Alan Blount <blount@media.mit.edu>, ietf@ietf.org
Subject: Re: I-D nroff macros
References: <200001041947.OAA25197@ml.media.mit.edu> <000d01bf571d$a112dfa0$6665a8c0@seanet.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
> 
> Alan Blount <blount@media.mit.edu> writes:
> 
> > I've been using the simple set of nroff macros, as described by
> >
> >   http://www.ietf.org/internet-drafts/2-nroff.template
> >
> > While this works, I'd like to be able to autogenerate section numbers
> > and table of contents entries.  This draft doesn't give any guidance.
> > I tried the -ms macros, as described by
> >
> >   http://www.cs.berkeley.edu/%7Ejanp/Help/textms.html
> >
> > but the header macro .NH creates the header in boldface, which is a
> > no-no according to RFC 2223.
> >
> > I imagine there is a way to do this, but I am ignorant of the
> > necessary kung-fu.  Does anyone have a sample nroff file, perhaps a
> > draft they've written, that generates heading numbers and a toc?
> 
> There are a couple of ways to do it, either by rolling your own macros or by
> making a minor change to the ms macros themselves (the approach I took).  I
> can send you my macro package if you like; however, it doesn't do automatic
> TOC processing.

If you send your nroff input file to the RFC editor as well as the
nroff'd output file, which is the recommended practice, then modifying
the ms macros themselves is not an option.

Automatic TOC processing cannot be done directly within nroff unless you
are willing to accept the TOC at the end of the document. To place the
TOC at the beginning of the document usually requires two passes. The
first pass is used to generate the TOC, which is then sourced (.so'd)
into the document for the second pass.

	Tony Hansen
	tony@att.com



From owner-ietf-outbound@ietf.org  Tue Jan  4 23:12:50 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14885
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 23:12:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id XAA13715;
	Tue, 4 Jan 2000 23:11:25 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id XAA14833
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 23:10:02 -0500 (EST)
Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14808
	for <ietf@ietf.org>; Tue, 4 Jan 2000 23:05:23 -0500 (EST)
Received: from dns.maillennium.att.com ([135.25.114.99])
	by almso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id XAA01792
	for <ietf@ietf.org>; Tue, 4 Jan 2000 23:04:52 -0500 (EST)
Received: from att.com ([135.197.86.61])
          by maillennium.att.com (labmail) with SMTP
          id <20000105040231099244725ne>; Wed, 5 Jan 2000 04:02:32 +0000
Message-ID: <3872C28A.537C118@att.com>
Date: Tue, 04 Jan 2000 23:03:22 -0500
From: Tony Hansen <tony@att.com>
Organization: AT&T Laboratories
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Glen Zorn <gwz@seanet.com>
CC: Alan Blount <blount@media.mit.edu>, ietf@ietf.org
Subject: Re: I-D nroff macros
References: <200001041947.OAA25197@ml.media.mit.edu> <000d01bf571d$a112dfa0$6665a8c0@seanet.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
> 
> Alan Blount <blount@media.mit.edu> writes:
> 
> > I've been using the simple set of nroff macros, as described by
> >
> >   http://www.ietf.org/internet-drafts/2-nroff.template
> >
> > While this works, I'd like to be able to autogenerate section numbers
> > and table of contents entries.  This draft doesn't give any guidance.
> > I tried the -ms macros, as described by
> >
> >   http://www.cs.berkeley.edu/%7Ejanp/Help/textms.html
> >
> > but the header macro .NH creates the header in boldface, which is a
> > no-no according to RFC 2223.
> >
> > I imagine there is a way to do this, but I am ignorant of the
> > necessary kung-fu.  Does anyone have a sample nroff file, perhaps a
> > draft they've written, that generates heading numbers and a toc?
> 
> There are a couple of ways to do it, either by rolling your own macros or by
> making a minor change to the ms macros themselves (the approach I took).  I
> can send you my macro package if you like; however, it doesn't do automatic
> TOC processing.

If you send your nroff input file to the RFC editor as well as the
nroff'd output file, which is the recommended practice, then modifying
the ms macros themselves is not an option.

Automatic TOC processing cannot be done directly within nroff unless you
are willing to accept the TOC at the end of the document. To place the
TOC at the beginning of the document usually requires two passes. The
first pass is used to generate the TOC, which is then sourced (.so'd)
into the document for the second pass.

	Tony Hansen
	tony@att.com



From owner-ietf-outbound  Tue Jan  4 23:31:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA15041
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 23:30:01 -0500 (EST)
Received: from dfw-smtpout2.email.verio.net (dfw-smtpout2.email.verio.net [129.250.36.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14974;
	Tue, 4 Jan 2000 23:23:52 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout2.email.verio.net with esmtp (Exim 3.12 #7)
	id 125hzC-00019d-00; Wed, 05 Jan 2000 04:23:50 +0000
Received: from [209.21.28.109] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125hyY-0006AH-00; Wed, 05 Jan 2000 04:23:10 +0000
Message-ID: <3872C793.420FDDA7@nma.com>
Date: Tue, 04 Jan 2000 20:24:51 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "David R. Conrad" <David.Conrad@iengines.com>
CC: Rick H Wesson <wessorh@ar.com>,
        "Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=" 
	<paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
References: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com> <3872906C.C861FDDF@iengines.com> <3872A06C.886EF997@nma.com> <3872BA5A.CDC2E1A1@iengines.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



"David R. Conrad" wrote:

> NSI should be treated no differently than others who publish proprietary
> protocols as an informational RFC.

Conrad:

Of course.  The IETF process is IMO actually a way of providing for
controlled release of private  information into public knowledge and use --
thus, a good thing.

However, I regret that this whole DNS area is so politicized and polarized that
instead of simply saying "I know this from the review work with NSI" even an
IETF AD such as Patrik has to say round-about things like "If I remember
correctly from a presentation NSI have had for me" and others like you feel
compelled to say that NSI "should be commended for documenting their
protocol."

Gosh, if this is really a 'call' and the IETF really wants the opinion of those
that help "make the Internet" ... and suffer with it, then can we please stay
on the technical  aspects?

The technical aspect here is that the RRP protocol documented in the
RFC proposed by NSI to the IETF is *not* what is being used by NSI
and is also *not* what should be used.

Thus, my viewpoint is that this is a "show stopper" in regard to the very
purposes of informational RFCs (pls insert copy and paste from IETF
charter) and the IETF should thus send NSI back to the drawing board.

IETF RFCs, even informational and even not more than a bag of bytes in
a server, should not be bureaucratic milestones in a chart but real
contributions -- where it is OK to be wrong since in Science a NO is
also an answer.  But, an RFC should not be fictional or clearly wrong.

Regarding your personal comment -- You might want to acquaint yourself
with the process before declaring it "wrong" -- I take it as a compliment,
because the only reason why I decided to say something here (after
a week-old message to Scott when he did release the proposed RFC)
is exactly because I am acquainted with the process but not as comfortable
with it as you seem to be.

Cheers,

Ed Gerck



From owner-ietf-outbound@ietf.org  Tue Jan  4 23:34:03 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15513
	for <ietf-web-archive@odin.ietf.org>; Tue, 4 Jan 2000 23:34:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id XAA14102;
	Tue, 4 Jan 2000 23:32:40 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id XAA15041
	for ietf-outbound.10@ietf.org; Tue, 4 Jan 2000 23:30:01 -0500 (EST)
Received: from dfw-smtpout2.email.verio.net (dfw-smtpout2.email.verio.net [129.250.36.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14974;
	Tue, 4 Jan 2000 23:23:52 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout2.email.verio.net with esmtp (Exim 3.12 #7)
	id 125hzC-00019d-00; Wed, 05 Jan 2000 04:23:50 +0000
Received: from [209.21.28.109] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125hyY-0006AH-00; Wed, 05 Jan 2000 04:23:10 +0000
Message-ID: <3872C793.420FDDA7@nma.com>
Date: Tue, 04 Jan 2000 20:24:51 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "David R. Conrad" <David.Conrad@iengines.com>
CC: Rick H Wesson <wessorh@ar.com>,
        "Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=" 
	<paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
References: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com> <3872906C.C861FDDF@iengines.com> <3872A06C.886EF997@nma.com> <3872BA5A.CDC2E1A1@iengines.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



"David R. Conrad" wrote:

> NSI should be treated no differently than others who publish proprietary
> protocols as an informational RFC.

Conrad:

Of course.  The IETF process is IMO actually a way of providing for
controlled release of private  information into public knowledge and use --
thus, a good thing.

However, I regret that this whole DNS area is so politicized and polarized that
instead of simply saying "I know this from the review work with NSI" even an
IETF AD such as Patrik has to say round-about things like "If I remember
correctly from a presentation NSI have had for me" and others like you feel
compelled to say that NSI "should be commended for documenting their
protocol."

Gosh, if this is really a 'call' and the IETF really wants the opinion of those
that help "make the Internet" ... and suffer with it, then can we please stay
on the technical  aspects?

The technical aspect here is that the RRP protocol documented in the
RFC proposed by NSI to the IETF is *not* what is being used by NSI
and is also *not* what should be used.

Thus, my viewpoint is that this is a "show stopper" in regard to the very
purposes of informational RFCs (pls insert copy and paste from IETF
charter) and the IETF should thus send NSI back to the drawing board.

IETF RFCs, even informational and even not more than a bag of bytes in
a server, should not be bureaucratic milestones in a chart but real
contributions -- where it is OK to be wrong since in Science a NO is
also an answer.  But, an RFC should not be fictional or clearly wrong.

Regarding your personal comment -- You might want to acquaint yourself
with the process before declaring it "wrong" -- I take it as a compliment,
because the only reason why I decided to say something here (after
a week-old message to Scott when he did release the proposed RFC)
is exactly because I am acquainted with the process but not as comfortable
with it as you seem to be.

Cheers,

Ed Gerck



From owner-ietf-outbound  Wed Jan  5 01:01:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA16202
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 01:00:02 -0500 (EST)
Received: from mage.qualcomm.com (mage.qualcomm.com [129.46.65.64])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16142;
	Wed, 5 Jan 2000 00:55:49 -0500 (EST)
Received: from [199.106.106.131] (xing.qualcomm.com [129.46.2.42]) by mage.qualcomm.com (8.8.5/1.4/8.7.2/1.15) with ESMTP id VAA03465; Tue, 4 Jan 2000 21:54:28 -0800 (PST)
Mime-Version: 1.0
X-Sender: jwn2@127.0.0.1 (Unverified)
Message-Id: <a04300e02b49889eaaac5@[129.46.222.73]>
In-Reply-To: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
References: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
X-Mailer: Eudora [Macintosh version 4.3b14-01.00]
X-PGP-RSA-Fingerprint: EA53 01A6 C076 F9C2  09E8 9480 645A 8857
X-PGP-DH-Fingerprint: 4F5E 56C9 BD4D 0227 331F 6AEE 9590 24F9 6FD7 04F8
Date: Tue, 4 Jan 2000 21:49:25 -0800
To: Rick H Wesson <wessorh@ar.com>
From: "John  W. Noerenberg" <jwn2@qualcomm.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to
   Informational
Cc: Ed Gerck <egerck@NMA.COM>,
        Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

At 3:05 PM -0800 1/4/00, Rick H Wesson wrote:
>The document exists as an I-D,
>the cat is out of the bag, why should it be an RFC?

Well, to continue the Request For Comment, I suppose.

The ideas in an RFC are not cast in stone.  The words may not change, 
but that doesn't mean the ideas can't evolve and be improved.
-- 

john noerenberg
jwn2@qualcomm.com
   ----------------------------------------------------------------------
   But now I know our world is no more permanent
   than a wave rising on the ocean.
   -- Arthur Golden, "Memoirs of a Geisha", 1997
   ----------------------------------------------------------------------



From owner-ietf-outbound@ietf.org  Wed Jan  5 01:02:58 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16338
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 01:02:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id BAA16826;
	Wed, 5 Jan 2000 01:01:31 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id BAA16202
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 01:00:02 -0500 (EST)
Received: from mage.qualcomm.com (mage.qualcomm.com [129.46.65.64])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16142;
	Wed, 5 Jan 2000 00:55:49 -0500 (EST)
Received: from [199.106.106.131] (xing.qualcomm.com [129.46.2.42]) by mage.qualcomm.com (8.8.5/1.4/8.7.2/1.15) with ESMTP id VAA03465; Tue, 4 Jan 2000 21:54:28 -0800 (PST)
Mime-Version: 1.0
X-Sender: jwn2@127.0.0.1 (Unverified)
Message-Id: <a04300e02b49889eaaac5@[129.46.222.73]>
In-Reply-To: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
References: <Pine.LNX.4.10.10001041454310.28714-100000@loki.ar.com>
X-Mailer: Eudora [Macintosh version 4.3b14-01.00]
X-PGP-RSA-Fingerprint: EA53 01A6 C076 F9C2  09E8 9480 645A 8857
X-PGP-DH-Fingerprint: 4F5E 56C9 BD4D 0227 331F 6AEE 9590 24F9 6FD7 04F8
Date: Tue, 4 Jan 2000 21:49:25 -0800
To: Rick H Wesson <wessorh@ar.com>
From: "John  W. Noerenberg" <jwn2@qualcomm.com>
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to
   Informational
Cc: Ed Gerck <egerck@NMA.COM>,
        Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

At 3:05 PM -0800 1/4/00, Rick H Wesson wrote:
>The document exists as an I-D,
>the cat is out of the bag, why should it be an RFC?

Well, to continue the Request For Comment, I suppose.

The ideas in an RFC are not cast in stone.  The words may not change, 
but that doesn't mean the ideas can't evolve and be improved.
-- 

john noerenberg
jwn2@qualcomm.com
   ----------------------------------------------------------------------
   But now I know our world is no more permanent
   than a wave rising on the ocean.
   -- Arthur Golden, "Memoirs of a Geisha", 1997
   ----------------------------------------------------------------------



From owner-ietf-outbound  Wed Jan  5 04:11:56 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA29636
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 04:10:02 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29592;
	Wed, 5 Jan 2000 04:08:12 -0500 (EST)
Received: from 192.168.111.25 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id KAA27529; 
          Wed, 5 Jan 2000 10:05:46 +0100 (MET)
Date: Wed, 05 Jan 2000 10:05:39 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Ed Gerck <egerck@nma.com>, "David R. Conrad" <David.Conrad@iengines.com>
cc: Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
Message-ID: <1630979.3156055539@[192.168.111.25]>
In-Reply-To: <3872C793.420FDDA7@nma.com>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA29592
Content-Transfer-Encoding: 8bit

--On 2000-01-04 20.24 -0800, Ed Gerck <egerck@nma.com> wrote:

> The technical aspect here is that the RRP protocol documented in the
> RFC proposed by NSI to the IETF is *not* what is being used by NSI
> and is also *not* what should be used.

If this is your view, please let me know, as AD, what the differences and 
errors are in the document.

As you say, this is the showstopper, nothing else.

The whole RRP process and many others that NSI has had (with USG, 
Registrars etc) led to a protocol which NSI has designed, and one which do 
(I claim) contain architectual mistakes, bugs, security flaws and what not.

The process is though completely irrelevant at this stage in time. Can 
people _please_ try to understand that.

NSI have approached the IETF and asks for publication of an informational 
RFC specifying their private Registry-Registrar protocol.

To be sure (I could, as AD, skipped this step!) that the protocol specified 
is what is in use, I asked for a last call to explain exactly this.

I therefore ask for input on this last question:

- Do the specification specify the protocol which NSI is using?

All responses so far has been "yes" until I found this sentence in an email 
by Ed, with no explanation at all.

I thereofore ask Ed to come with explicit references to paragraphs in the 
specification which is wrong, explanation what is happening in the protocol 
which is in use, and suggested new wording which explains the way the 
protocol works.

Without this input, I have to ignore the mail from Ed.

All other discussions is completely irrelevant, and will be ignored.

As Paul wrote, there are some ideas (separated from this discussion) on how 
to come up with _THE_ RRP which IETF endorses, and the process for that is 
to ask relevant organisations to create a buissness level functional 
requirement on such a protocol, and then develop the protocol in the IETF. 
That work has been initiated, and I see a lot of discussions here, now, 
have to do with design of a protocol, and not review of a soon-to-be 
informational RFC.

Because of that, please hold your horses!

As Dave Crocker wrote, this discussion has taken just far to much bandwidth 
already with irrelevant stuff.

We are neither discussing the quality of the NSI RRP, nor are we discussing 
how NSI ended up with that version of the protocol.

    Patrik Fältström
    Area Director, Applications Area, IETF





From owner-ietf-outbound@ietf.org  Wed Jan  5 04:14:39 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29711
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 04:14:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id EAA27338;
	Wed, 5 Jan 2000 04:13:09 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id EAA29636
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 04:10:02 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29592;
	Wed, 5 Jan 2000 04:08:12 -0500 (EST)
Received: from 192.168.111.25 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id KAA27529; 
          Wed, 5 Jan 2000 10:05:46 +0100 (MET)
Date: Wed, 05 Jan 2000 10:05:39 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Ed Gerck <egerck@nma.com>, "David R. Conrad" <David.Conrad@iengines.com>
cc: Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
Message-ID: <1630979.3156055539@[192.168.111.25]>
In-Reply-To: <3872C793.420FDDA7@nma.com>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA29592
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

--On 2000-01-04 20.24 -0800, Ed Gerck <egerck@nma.com> wrote:

> The technical aspect here is that the RRP protocol documented in the
> RFC proposed by NSI to the IETF is *not* what is being used by NSI
> and is also *not* what should be used.

If this is your view, please let me know, as AD, what the differences and 
errors are in the document.

As you say, this is the showstopper, nothing else.

The whole RRP process and many others that NSI has had (with USG, 
Registrars etc) led to a protocol which NSI has designed, and one which do 
(I claim) contain architectual mistakes, bugs, security flaws and what not.

The process is though completely irrelevant at this stage in time. Can 
people _please_ try to understand that.

NSI have approached the IETF and asks for publication of an informational 
RFC specifying their private Registry-Registrar protocol.

To be sure (I could, as AD, skipped this step!) that the protocol specified 
is what is in use, I asked for a last call to explain exactly this.

I therefore ask for input on this last question:

- Do the specification specify the protocol which NSI is using?

All responses so far has been "yes" until I found this sentence in an email 
by Ed, with no explanation at all.

I thereofore ask Ed to come with explicit references to paragraphs in the 
specification which is wrong, explanation what is happening in the protocol 
which is in use, and suggested new wording which explains the way the 
protocol works.

Without this input, I have to ignore the mail from Ed.

All other discussions is completely irrelevant, and will be ignored.

As Paul wrote, there are some ideas (separated from this discussion) on how 
to come up with _THE_ RRP which IETF endorses, and the process for that is 
to ask relevant organisations to create a buissness level functional 
requirement on such a protocol, and then develop the protocol in the IETF. 
That work has been initiated, and I see a lot of discussions here, now, 
have to do with design of a protocol, and not review of a soon-to-be 
informational RFC.

Because of that, please hold your horses!

As Dave Crocker wrote, this discussion has taken just far to much bandwidth 
already with irrelevant stuff.

We are neither discussing the quality of the NSI RRP, nor are we discussing 
how NSI ended up with that version of the protocol.

    Patrik Fältström
    Area Director, Applications Area, IETF





From owner-ietf-outbound  Wed Jan  5 04:31:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA29817
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 04:30:03 -0500 (EST)
Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29787;
	Wed, 5 Jan 2000 04:29:00 -0500 (EST)
Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net)
	by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7)
	id 125mkO-00057i-00; Wed, 05 Jan 2000 09:28:52 +0000
Received: from [209.21.28.86] (helo=nma.com)
	by dfw-mmp4.email.verio.net with esmtp (Exim 3.12 #7)
	id 125mkK-0001Fn-00; Wed, 05 Jan 2000 09:28:48 +0000
Message-ID: <38730F10.CCF092BB@nma.com>
Date: Wed, 05 Jan 2000 01:29:52 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>
CC: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
References: <1630979.3156055539@[192.168.111.25]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



Patrik Fältström wrote:

> --On 2000-01-04 20.24 -0800, Ed Gerck <egerck@nma.com> wrote:
>
> > The technical aspect here is that the RRP protocol documented in the
> > RFC proposed by NSI to the IETF is *not* what is being used by NSI
> > and is also *not* what should be used.
>
> If this is your view, please let me know, as AD, what the differences and
> errors are in the document.
>
> As you say, this is the showstopper, nothing else.

Yes. There are two separate points in this issue.

1. The proposed RFC is not what is being used as NSI's RRP:
Catch22 -- if I point it out I may be seen to be infringing NSI's
NDA, even though I would be mostly quoting myself.  To solve
this potential problem and to avoid controversy, I just resent to
NSI the following request which intends to allow me to freely
answer your question:

 On ocasion of NSI's publication of the RFC with the
 Shared Registry Protocol, per enclosed copies, I
 hereby request my formal release from any Non-Disclosure
 obligations to NSI.  Please send me the release declaration
 by mail, and confirm by email.

Alternatively, you may verify your mailbox of RAB messages and
decide by yourself.  Also, NSI may verify the discrepancies by
themselves.

2. The proposed RFC is not what should be used:
This has become rather obvious here.  But, alternatively, I may be
released of the NDA and then comment, or you may verify your
RAB mailbox and decide by yourself, or NSI may verify it by
themselves.

I hope thus to have answered the question to your satisfaction.

Cheers,

Ed Gerck




From owner-ietf-outbound@ietf.org  Wed Jan  5 04:32:14 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29937
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 04:32:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id EAA27792;
	Wed, 5 Jan 2000 04:30:46 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id EAA29817
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 04:30:03 -0500 (EST)
Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29787;
	Wed, 5 Jan 2000 04:29:00 -0500 (EST)
Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net)
	by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7)
	id 125mkO-00057i-00; Wed, 05 Jan 2000 09:28:52 +0000
Received: from [209.21.28.86] (helo=nma.com)
	by dfw-mmp4.email.verio.net with esmtp (Exim 3.12 #7)
	id 125mkK-0001Fn-00; Wed, 05 Jan 2000 09:28:48 +0000
Message-ID: <38730F10.CCF092BB@nma.com>
Date: Wed, 05 Jan 2000 01:29:52 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>
CC: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
References: <1630979.3156055539@[192.168.111.25]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



Patrik Fältström wrote:

> --On 2000-01-04 20.24 -0800, Ed Gerck <egerck@nma.com> wrote:
>
> > The technical aspect here is that the RRP protocol documented in the
> > RFC proposed by NSI to the IETF is *not* what is being used by NSI
> > and is also *not* what should be used.
>
> If this is your view, please let me know, as AD, what the differences and
> errors are in the document.
>
> As you say, this is the showstopper, nothing else.

Yes. There are two separate points in this issue.

1. The proposed RFC is not what is being used as NSI's RRP:
Catch22 -- if I point it out I may be seen to be infringing NSI's
NDA, even though I would be mostly quoting myself.  To solve
this potential problem and to avoid controversy, I just resent to
NSI the following request which intends to allow me to freely
answer your question:

 On ocasion of NSI's publication of the RFC with the
 Shared Registry Protocol, per enclosed copies, I
 hereby request my formal release from any Non-Disclosure
 obligations to NSI.  Please send me the release declaration
 by mail, and confirm by email.

Alternatively, you may verify your mailbox of RAB messages and
decide by yourself.  Also, NSI may verify the discrepancies by
themselves.

2. The proposed RFC is not what should be used:
This has become rather obvious here.  But, alternatively, I may be
released of the NDA and then comment, or you may verify your
RAB mailbox and decide by yourself, or NSI may verify it by
themselves.

I hope thus to have answered the question to your satisfaction.

Cheers,

Ed Gerck




From owner-ietf-outbound  Wed Jan  5 04:51:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA00194
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 04:50:03 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00128;
	Wed, 5 Jan 2000 04:49:36 -0500 (EST)
Received: from 192.168.111.25 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id KAA29283; 
          Wed, 5 Jan 2000 10:47:43 +0100 (MET)
Date: Wed, 05 Jan 2000 10:47:44 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Ed Gerck <egerck@nma.com>
cc: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
Message-ID: <66653.3156058064@[192.168.111.25]>
In-Reply-To: <38730F10.CCF092BB@nma.com>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

--On 2000-01-05 01.29 -0800, Ed Gerck <egerck@nma.com> wrote:

> Alternatively, you may verify your mailbox of RAB messages and
> decide by yourself.  Also, NSI may verify the discrepancies by
> themselves.

As the I-D didn't exist when the RAB existed (the date of the I-D is 
December of 1999), it is plain impossible to have discussed where the I-D 
differs from what was in use.

Please try again.

   paf



From owner-ietf-outbound@ietf.org  Wed Jan  5 04:52:23 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00314
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 04:52:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id EAA29227;
	Wed, 5 Jan 2000 04:50:57 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id EAA00194
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 04:50:03 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00128;
	Wed, 5 Jan 2000 04:49:36 -0500 (EST)
Received: from 192.168.111.25 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id KAA29283; 
          Wed, 5 Jan 2000 10:47:43 +0100 (MET)
Date: Wed, 05 Jan 2000 10:47:44 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Ed Gerck <egerck@nma.com>
cc: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
Message-ID: <66653.3156058064@[192.168.111.25]>
In-Reply-To: <38730F10.CCF092BB@nma.com>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

--On 2000-01-05 01.29 -0800, Ed Gerck <egerck@nma.com> wrote:

> Alternatively, you may verify your mailbox of RAB messages and
> decide by yourself.  Also, NSI may verify the discrepancies by
> themselves.

As the I-D didn't exist when the RAB existed (the date of the I-D is 
December of 1999), it is plain impossible to have discussed where the I-D 
differs from what was in use.

Please try again.

   paf



From owner-ietf-outbound  Wed Jan  5 05:41:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA00775
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 05:40:03 -0500 (EST)
Received: from dfw-smtpout3.email.verio.net (dfw-smtpout3.email.verio.net [129.250.36.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00736;
	Wed, 5 Jan 2000 05:36:24 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125nng-0005re-00; Wed, 05 Jan 2000 10:36:20 +0000
Received: from [209.21.28.112] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125nn1-0003zn-00; Wed, 05 Jan 2000 10:35:40 +0000
Message-ID: <38731EE3.AE81865C@nma.com>
Date: Wed, 05 Jan 2000 02:37:23 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>
CC: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
References: <66653.3156058064@[192.168.111.25]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



Patrik Fältström wrote:

> --On 2000-01-05 01.29 -0800, Ed Gerck <egerck@nma.com> wrote:
>
> > Alternatively, you may verify your mailbox of RAB messages and
> > decide by yourself.  Also, NSI may verify the discrepancies by
> > themselves.
>
> As the I-D didn't exist when the RAB existed (the date of the I-D is
> December of 1999), it is plain impossible to have discussed where the I-D
> differs from what was in use.
>
> Please try again.

Try again?  No, pls just follow what I suggested -- compare the December
1999 I-D (which you have, let me call this "Evidence A") with the RAB
archives and documents from March 1999 to October 1999 (which you
also have, let me call this "Evidence B").  Then, comparing Evidence A
with Evidence B you may draw your own conclusions about Evidence A
being actually *outdated* (time warp?) when compared with Evidence B
even though Evidence B was issued much *earlier*.  What we have in the
proposed RFC is thus an outdated spec -- problems that were actually
reported *solved* in the March-October 1999 timeframe appear again
*unsolved* in the December 1999 timeframe.

Regarding  Evidence C (what is actually used today), it is thus quite possible
to infer that it does differ from Evidence A (the proposed RFC), since Evidence
A is outdated even when compared to Evidence B which predates Evidence C.
In other words, the proposed RFC and the actual RRP protocol seem to have a
larger distance than even that between the proposed RFC and the RAB
Minutes/Documents -- which is probably not zero as you yourself say above.

Cheers,

Ed Gerck




From owner-ietf-outbound@ietf.org  Wed Jan  5 05:42:28 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00852
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 05:42:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id FAA00938;
	Wed, 5 Jan 2000 05:41:00 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id FAA00775
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 05:40:03 -0500 (EST)
Received: from dfw-smtpout3.email.verio.net (dfw-smtpout3.email.verio.net [129.250.36.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00736;
	Wed, 5 Jan 2000 05:36:24 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125nng-0005re-00; Wed, 05 Jan 2000 10:36:20 +0000
Received: from [209.21.28.112] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125nn1-0003zn-00; Wed, 05 Jan 2000 10:35:40 +0000
Message-ID: <38731EE3.AE81865C@nma.com>
Date: Wed, 05 Jan 2000 02:37:23 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>
CC: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
References: <66653.3156058064@[192.168.111.25]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



Patrik Fältström wrote:

> --On 2000-01-05 01.29 -0800, Ed Gerck <egerck@nma.com> wrote:
>
> > Alternatively, you may verify your mailbox of RAB messages and
> > decide by yourself.  Also, NSI may verify the discrepancies by
> > themselves.
>
> As the I-D didn't exist when the RAB existed (the date of the I-D is
> December of 1999), it is plain impossible to have discussed where the I-D
> differs from what was in use.
>
> Please try again.

Try again?  No, pls just follow what I suggested -- compare the December
1999 I-D (which you have, let me call this "Evidence A") with the RAB
archives and documents from March 1999 to October 1999 (which you
also have, let me call this "Evidence B").  Then, comparing Evidence A
with Evidence B you may draw your own conclusions about Evidence A
being actually *outdated* (time warp?) when compared with Evidence B
even though Evidence B was issued much *earlier*.  What we have in the
proposed RFC is thus an outdated spec -- problems that were actually
reported *solved* in the March-October 1999 timeframe appear again
*unsolved* in the December 1999 timeframe.

Regarding  Evidence C (what is actually used today), it is thus quite possible
to infer that it does differ from Evidence A (the proposed RFC), since Evidence
A is outdated even when compared to Evidence B which predates Evidence C.
In other words, the proposed RFC and the actual RRP protocol seem to have a
larger distance than even that between the proposed RFC and the RAB
Minutes/Documents -- which is probably not zero as you yourself say above.

Cheers,

Ed Gerck




From owner-ietf-outbound  Wed Jan  5 05:51:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA00938
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 05:50:03 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00887;
	Wed, 5 Jan 2000 05:46:06 -0500 (EST)
Received: from 192.168.124.51 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id LAA01400; 
          Wed, 5 Jan 2000 11:44:15 +0100 (MET)
Date: Wed, 05 Jan 2000 11:44:15 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Ed Gerck <egerck@nma.com>
cc: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
Message-ID: <140863.3156061455@[192.168.124.51]>
In-Reply-To: <38731EE3.AE81865C@nma.com>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

--On 2000-01-05 02.37 -0800, Ed Gerck <egerck@nma.com> wrote:

> What we have in the
> proposed RFC is thus an outdated spec -- problems that were actually
> reported *solved* in the March-October 1999 timeframe appear again
> *unsolved* in the December 1999 timeframe.

In real life, I have not checked whether NSI really _uses_ what we talked 
about in the timeframe March-October, and in some cases (timestamps for 
example) it is already clear that they use what is specified in the I-D and 
NOT what the RAB proposed, i.e. what is in the email archives of RAB.

So, in what order the specifications were created have nothing to do with 
what we are checking today. We are checking the I-D with what is used. 
Nothing else.

Have you been using the protocol that is in use today?

If not, I ask myself how you can state that the protocol is different from 
what is specified in the I-D.

    paf



From owner-ietf-outbound@ietf.org  Wed Jan  5 05:52:50 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01006
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 05:52:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id FAA01121;
	Wed, 5 Jan 2000 05:50:48 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id FAA00938
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 05:50:03 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00887;
	Wed, 5 Jan 2000 05:46:06 -0500 (EST)
Received: from 192.168.124.51 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id LAA01400; 
          Wed, 5 Jan 2000 11:44:15 +0100 (MET)
Date: Wed, 05 Jan 2000 11:44:15 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Ed Gerck <egerck@nma.com>
cc: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
Message-ID: <140863.3156061455@[192.168.124.51]>
In-Reply-To: <38731EE3.AE81865C@nma.com>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

--On 2000-01-05 02.37 -0800, Ed Gerck <egerck@nma.com> wrote:

> What we have in the
> proposed RFC is thus an outdated spec -- problems that were actually
> reported *solved* in the March-October 1999 timeframe appear again
> *unsolved* in the December 1999 timeframe.

In real life, I have not checked whether NSI really _uses_ what we talked 
about in the timeframe March-October, and in some cases (timestamps for 
example) it is already clear that they use what is specified in the I-D and 
NOT what the RAB proposed, i.e. what is in the email archives of RAB.

So, in what order the specifications were created have nothing to do with 
what we are checking today. We are checking the I-D with what is used. 
Nothing else.

Have you been using the protocol that is in use today?

If not, I ask myself how you can state that the protocol is different from 
what is specified in the I-D.

    paf



From owner-ietf-outbound  Wed Jan  5 06:01:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA01098
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 06:00:03 -0500 (EST)
Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01018;
	Wed, 5 Jan 2000 05:53:17 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7)
	id 125o41-0007cZ-00; Wed, 05 Jan 2000 10:53:13 +0000
Received: from [209.21.28.112] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125o3M-0004U5-00; Wed, 05 Jan 2000 10:52:33 +0000
Message-ID: <387322D9.2C87F0F7@nma.com>
Date: Wed, 05 Jan 2000 02:54:17 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>
CC: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
References: <140863.3156061455@[192.168.124.51]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



Patrik Fältström wrote:

> --On 2000-01-05 02.37 -0800, Ed Gerck <egerck@nma.com> wrote:
>
> > What we have in the
> > proposed RFC is thus an outdated spec -- problems that were actually
> > reported *solved* in the March-October 1999 timeframe appear again
> > *unsolved* in the December 1999 timeframe.
>
> In real life, I have not checked whether NSI really _uses_ what we talked
> about in the timeframe March-October, and in some cases (timestamps for
> example) it is already clear that they use what is specified in the I-D and
> NOT what the RAB proposed, i.e. what is in the email archives of RAB.

How can you say " in some cases (timestamps for example) it is already
clear that they use what is specified in the I-D"?  Did you test it? Have you
been using the protocol that is in use today?

If not, I ask myself how you can state that the protocol is what is specified
in the I-D.

Cheers,

Ed Gerck




From owner-ietf-outbound@ietf.org  Wed Jan  5 06:02:07 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01211
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 06:02:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id GAA01389;
	Wed, 5 Jan 2000 06:00:40 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id GAA01098
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 06:00:03 -0500 (EST)
Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01018;
	Wed, 5 Jan 2000 05:53:17 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7)
	id 125o41-0007cZ-00; Wed, 05 Jan 2000 10:53:13 +0000
Received: from [209.21.28.112] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125o3M-0004U5-00; Wed, 05 Jan 2000 10:52:33 +0000
Message-ID: <387322D9.2C87F0F7@nma.com>
Date: Wed, 05 Jan 2000 02:54:17 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>
CC: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
References: <140863.3156061455@[192.168.124.51]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



Patrik Fältström wrote:

> --On 2000-01-05 02.37 -0800, Ed Gerck <egerck@nma.com> wrote:
>
> > What we have in the
> > proposed RFC is thus an outdated spec -- problems that were actually
> > reported *solved* in the March-October 1999 timeframe appear again
> > *unsolved* in the December 1999 timeframe.
>
> In real life, I have not checked whether NSI really _uses_ what we talked
> about in the timeframe March-October, and in some cases (timestamps for
> example) it is already clear that they use what is specified in the I-D and
> NOT what the RAB proposed, i.e. what is in the email archives of RAB.

How can you say " in some cases (timestamps for example) it is already
clear that they use what is specified in the I-D"?  Did you test it? Have you
been using the protocol that is in use today?

If not, I ask myself how you can state that the protocol is what is specified
in the I-D.

Cheers,

Ed Gerck




From owner-ietf-outbound  Wed Jan  5 07:21:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA02325
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 07:20:02 -0500 (EST)
Received: from chiark.greenend.org.uk (mail@chiark.greenend.org.uk [195.224.76.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02185;
	Wed, 5 Jan 2000 07:17:27 -0500 (EST)
Received: from ijackson by chiark.greenend.org.uk with local (Exim 2.05 #1)
	id 125pNR-000219-00 (Debian); Wed, 5 Jan 2000 12:17:21 +0000
From: Ian Jackson <ijackson@chiark.greenend.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Message-ID: <14451.13905.185888.671135@chiark.greenend.org.uk>
Date: Wed, 5 Jan 2000 12:17:21 +0000 (GMT)
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
Cc: iesg@ietf.org, Scott Hollenbeck <shollenb@NETSOL.COM>, ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
In-Reply-To: <625862.3156000888@[192.168.111.25]>
References: <14450.11312.813608.730985@chiark.greenend.org.uk>
	<625862.3156000888@[192.168.111.25]>
X-Mailer: VM 6.62 under Emacs 19.34.1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA02185
Content-Transfer-Encoding: 8bit

Patrik Fältström writes ("Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to   Informational"):
> --On 2000-01-04 17.21 +0000, Ian Jackson <ijackson@chiark.greenend.org.uk> 
> wrote:
> > * The TRANSFER command, when used to approve a transfer, does not
> > specify to which registrar the domain is to be transferred.
> 
> If I remember correctly from a presentation NSI have had for me, the 
> transfer is always to the registrar issuing the command, but I might be 
> wrong.

That's right, but the command I was talking about was the transfer
_approval_, which is also performed with the TRANSFER command with a
different syntax.  The transfer is approved by the donor, but there is
no way to find out or specify the intended recipient.

Ian.



From owner-ietf-outbound@ietf.org  Wed Jan  5 07:22:38 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02409
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 07:22:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id HAA03001;
	Wed, 5 Jan 2000 07:21:11 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id HAA02325
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 07:20:02 -0500 (EST)
Received: from chiark.greenend.org.uk (mail@chiark.greenend.org.uk [195.224.76.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02185;
	Wed, 5 Jan 2000 07:17:27 -0500 (EST)
Received: from ijackson by chiark.greenend.org.uk with local (Exim 2.05 #1)
	id 125pNR-000219-00 (Debian); Wed, 5 Jan 2000 12:17:21 +0000
From: Ian Jackson <ijackson@chiark.greenend.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Message-ID: <14451.13905.185888.671135@chiark.greenend.org.uk>
Date: Wed, 5 Jan 2000 12:17:21 +0000 (GMT)
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
Cc: iesg@ietf.org, Scott Hollenbeck <shollenb@NETSOL.COM>, ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to 
 Informational
In-Reply-To: <625862.3156000888@[192.168.111.25]>
References: <14450.11312.813608.730985@chiark.greenend.org.uk>
	<625862.3156000888@[192.168.111.25]>
X-Mailer: VM 6.62 under Emacs 19.34.1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA02185
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Patrik Fältström writes ("Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to   Informational"):
> --On 2000-01-04 17.21 +0000, Ian Jackson <ijackson@chiark.greenend.org.uk> 
> wrote:
> > * The TRANSFER command, when used to approve a transfer, does not
> > specify to which registrar the domain is to be transferred.
> 
> If I remember correctly from a presentation NSI have had for me, the 
> transfer is always to the registrar issuing the command, but I might be 
> wrong.

That's right, but the command I was talking about was the transfer
_approval_, which is also performed with the TRANSFER command with a
different syntax.  The transfer is approved by the donor, but there is
no way to find out or specify the intended recipient.

Ian.



From owner-ietf-outbound  Wed Jan  5 09:11:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05255
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 09:10:02 -0500 (EST)
Received: from torque.pothole.com ([209.94.126.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05054
	for <ietf@ietf.org>; Wed, 5 Jan 2000 09:01:32 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id JAA32072
	for ietf@ietf.org; Wed, 5 Jan 2000 09:01:28 -0500 (EST)
Message-Id: <200001051401.JAA32072@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to Informational 
In-reply-to: Your message of "Tue, 04 Jan 2000 20:43:21 EST."
             <v04210102b49844c2f1c5@[192.168.0.1]> 
Date: Wed, 05 Jan 2000 09:01:28 -0500
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp


I think it is important to the openness of the process to maintain the
tradition of a relatively light editorial hand on Informational RFCs
that document non-IETF protocols.  The minimal substantive part of
this review increasingly seems to be done by the IESG instead of the
RFC Editor.

From:  Gordon Cook <cook@cookreport.com>
Message-Id:  <v04210102b49844c2f1c5@[192.168.0.1]>
In-Reply-To:  <4.2.1.20000104152158.00a867e0@mail.imc.org>
References:  <38727013.DAF0AE16@nma.com>
	     <4.2.1.20000104152158.00a867e0@mail.imc.org>
Date:  Tue, 4 Jan 2000 20:43:21 -0500

>OK Paul, lets give you the benefit of the doubt and say that your 
>assertions below are absolutely right.  Please explain then why it 
>should become an informational RFC without having the comments of the 
>RAB members attached to it? (Even though as Patrick said it is not 
>common practice to do this with an informational rfc). ....

Although extremely brief RFC-Editor/IESG comments (as in one or two
sentences) are sometimes included in a non-IETF Informational RFC, I
know of no case in which some third party's general comments have been
included.  Such third parties can write up their comments as a
separate Informational document and submit it to the RFC Editor for
publication if they want.

>Is it really the position of the IESG that they have NO obligation to 
>do anything to inform the unwary that this protocol is an invitation 
>for lawsuits against NSI, against ICANN, and possibly against the 
>IETF on the grounds that the RFC publication was perceived by the 
>clueless party  as an endorsement?

To the extent that the IESG undertook to do a detailed quality review
of non-IETF Informational RFC protocols and includes the results of
such a review in the RFC, it would thereby assume legal liability.
The way to avoid such liability is maintain as minimal a review as
possible.

> ....

Donald
===================================================================
 Donald E. Eastlake 3rd   +1 914-276-2668   dee3@torque.pothole.com
 65 Shindegan Hill Rd, RR#1
 Carmel, NY 10512 USA



From owner-ietf-outbound@ietf.org  Wed Jan  5 09:12:57 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05369
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 09:12:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id JAA05758;
	Wed, 5 Jan 2000 09:11:29 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05255
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 09:10:02 -0500 (EST)
Received: from torque.pothole.com ([209.94.126.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05054
	for <ietf@ietf.org>; Wed, 5 Jan 2000 09:01:32 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id JAA32072
	for ietf@ietf.org; Wed, 5 Jan 2000 09:01:28 -0500 (EST)
Message-Id: <200001051401.JAA32072@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to Informational 
In-reply-to: Your message of "Tue, 04 Jan 2000 20:43:21 EST."
             <v04210102b49844c2f1c5@[192.168.0.1]> 
Date: Wed, 05 Jan 2000 09:01:28 -0500
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp


I think it is important to the openness of the process to maintain the
tradition of a relatively light editorial hand on Informational RFCs
that document non-IETF protocols.  The minimal substantive part of
this review increasingly seems to be done by the IESG instead of the
RFC Editor.

From:  Gordon Cook <cook@cookreport.com>
Message-Id:  <v04210102b49844c2f1c5@[192.168.0.1]>
In-Reply-To:  <4.2.1.20000104152158.00a867e0@mail.imc.org>
References:  <38727013.DAF0AE16@nma.com>
	     <4.2.1.20000104152158.00a867e0@mail.imc.org>
Date:  Tue, 4 Jan 2000 20:43:21 -0500

>OK Paul, lets give you the benefit of the doubt and say that your 
>assertions below are absolutely right.  Please explain then why it 
>should become an informational RFC without having the comments of the 
>RAB members attached to it? (Even though as Patrick said it is not 
>common practice to do this with an informational rfc). ....

Although extremely brief RFC-Editor/IESG comments (as in one or two
sentences) are sometimes included in a non-IETF Informational RFC, I
know of no case in which some third party's general comments have been
included.  Such third parties can write up their comments as a
separate Informational document and submit it to the RFC Editor for
publication if they want.

>Is it really the position of the IESG that they have NO obligation to 
>do anything to inform the unwary that this protocol is an invitation 
>for lawsuits against NSI, against ICANN, and possibly against the 
>IETF on the grounds that the RFC publication was perceived by the 
>clueless party  as an endorsement?

To the extent that the IESG undertook to do a detailed quality review
of non-IETF Informational RFC protocols and includes the results of
such a review in the RFC, it would thereby assume legal liability.
The way to avoid such liability is maintain as minimal a review as
possible.

> ....

Donald
===================================================================
 Donald E. Eastlake 3rd   +1 914-276-2668   dee3@torque.pothole.com
 65 Shindegan Hill Rd, RR#1
 Carmel, NY 10512 USA



From owner-ietf-outbound  Wed Jan  5 09:21:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05451
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 09:20:02 -0500 (EST)
Received: from a4.jck.com (ns.jck.com [63.65.7.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05097;
	Wed, 5 Jan 2000 09:02:28 -0500 (EST)
Received: from p2.jck.com ("port 1142"@[63.65.7.138])
 by a4.jck.com (PMDF V5.1-11 #C4036) with ESMTP id <0FNV002218A9HR@a4.jck.com>;
 Wed,  5 Jan 2000 09:01:23 -0500 (EST)
Date: Wed, 05 Jan 2000 09:00:06 -0500
From: John C Klensin <klensin@mci.net>
Subject: Re: Back to the drawing board,
 was Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to
 Informational
To: Ed Gerck <egerck@nma.com>
Cc: iesg@ietf.org, Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
Message-id: <2170001740.947062806@p2.jck.com>
MIME-version: 1.0
X-Mailer: Mulberry (Win32) [2.0.0b6, s/n U-301227]
Content-type: text/plain; charset=us-ascii; format=flowed; format=flowed
Content-disposition: inline
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I've trimmed most of the cc's on the theory that everyone 
relevant except possibly Scott are on the IETF or IESG lists.

Ed, I've followed your comments very carefully, but, applying 
your reasoning to what I see as long-standing principles for 
handling Info RFCs, I reach nearly opposite conclusions. Please 
forgive the length of this note; I think it is important that we 
review and return to some principles here.

I don't have RFC 2223 in front of me and hope we can avoid 
hair-splitting and protocol-lawyering over this, but, in 
general, the RFC Editor has chosen to publish (and the IESG has 
chosen to not recommend otherwise) when

* The proposed document covers material that is at least 
potentially relevant and of interest to some reasonable fraction 
of the internet community.   E.g., a document that described the 
operation of a toaster that was not designed for connection to 
the network might well not be published.

* If the document covers a protocol or discussion about how to 
perform some protocol-related act, it isn't likely to create 
confusion with existing standards or standards-work-in-progress 
or reasonable ways to implement them.  E.g.,  a document that 
described itself as "HTTP 1.3", but was not compatible with HTTP 
1.1, and had not been through the standards process, would be 
unlikely to be published (at least under that name and without a 
lot of disclaimers).

* Whatever the document contains, it is not egregiously stupid. 
My impression is that, while this principle --rejecting drafts 
for publication on the basis of utter stupidity-- is discussed a 
lot, it is rarely actually applied.

More recently, there has been a lot of thought given to whether 
a particular document is part of a marketing plan to publish 
something as informaitional and then present it to customers as 
"an RFC" in a way that implies IETF approval and probably 
standardization.  My impression is that rejecting documents on 
this basis is, like the "no stupidity" criterion often 
discussed, but rarely applied.  These documents often go through 
with significant disclaimers attached, but they mostly go 
through.

By contrast, IETF has (I believe wisely) always steered clear of 
the certification process.   We never make statements --even for 
full Internet Standards-- that a given implementation works, or 
that a particular implementation faithfully reflects a given 
specification.   People and companies make those assertions, we 
don't try to stop them; we hope that the marketplace will 
appropriately reward those who lie (intentionally or otherwise). 
Usually that works, sometimes it doesn't, but, as you know, the 
IETF-authorized "protocol police" have always been a myth.

Now, in the case of this draft document, I was a little 
surprised that the IESG chose to Last Call this doc before 
letting it go to the RFC Editor.  They generally don't for 
informational documents (for which I think we must be thankful). 
I believe that the issues this has raised demonstrates that 
their decison was wise, even though many of the comments  have 
contained more heat than light.  But, if we look at the doc, it 
is a protocol description, supplied by one organization.    It 
doesn't make that clear enough, and it should, but that point 
was made and accepted long ago.  It is arguably not quite clear 
what NSI claims it describes, e.g.,

   * the protocol they are running today
   * the protocol they ran at one time
   * the protocol they wish they were running
   * the protocol they wish someone else were running, but have 
no intention of running themselves.

If that isn't clear to all reasonable readers, it ought to be 
fixed.   Within the traditional domain of info RFCs, any of 
those four (and others) are publishable, but we try to avoid 
confusion, especially in the case of the fourth.

But, I think an argument about whether or not the document 
actually conforms to some piece of code and making a decision to 
publish or not publish on that basis is *very* dangerous for us. 
As suggested above, we don't try to do that even for 
standards-track protocols and putatively-comforming programs.

If, as you suggest has happened here, NSI (or someone else) has 
submitted a document for info RFC publication, and it suggested 
things that aren't true, that is a problem... but it is a 
problem between NSI (again for example) and whomever tries to 
implement the thing, not an IETF problem.   I would expect that, 
if such a situation occurred, registrars who implemented the 
protocol as described in the RFC and then discovered that they 
needed to do something rather different to make it work, would 
be very annoyed.  They might rationally express that annoyance by
     * contacting their lawyers
     * contacting the press
     * writing proposed info RFCs with titles like "NSI RRP
       description considered harmful"
Just a personal opinion here, but I can't imagine the RFC Editor 
declining to publish documents of the latter type if they were 
technically coherent and well-reasoned.

In summary, I believe that our advice to the IESG should be

"make certain this document is clear about what it is and what 
it proports to be, and that the authors (or author organization) 
take responsibility for that being true.  Make certain that, 
should a RRP WG effort be launched, this document doesn't 
unreasonaby constrain it.   If areas are identified in which the 
document isn't clear about what it calls for, get those fixed. 
Consider attaching a disclaimer that indicates the list of 
unresolved issues contains some fairly serious problems and that 
there may be equally serious issues not on that list.   Then, 
since it is relevant and not obviously stupid, go ahead and 
publish the thing."

regards,
     john

Disclaimer:  I wasn't a member of the review committee (I was 
invited, but couldn't agree to the NDA in use at the time).   I 
did have a chance to look at a draft of this doc that preceeded 
the I-D.  My personal opinion is that, as a example of protocol 
design work, the I-D gets no better than a C- and that it may be 
an excellent example of why it is better to do protocol design 
in the open, rather than in closed groups tied up in NDAs.  But 
I can't get to "don't publish" from finding the thing a little 
distasteful: there are standards-track protocols I find a little 
distasteful and I believe the long-standing tradition of freedom 
to publish things that might be of use or interest is pretty 
important.



From owner-ietf-outbound@ietf.org  Wed Jan  5 09:22:23 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05506
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 09:22:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id JAA06044;
	Wed, 5 Jan 2000 09:20:57 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05451
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 09:20:02 -0500 (EST)
Received: from a4.jck.com (ns.jck.com [63.65.7.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05097;
	Wed, 5 Jan 2000 09:02:28 -0500 (EST)
Received: from p2.jck.com ("port 1142"@[63.65.7.138])
 by a4.jck.com (PMDF V5.1-11 #C4036) with ESMTP id <0FNV002218A9HR@a4.jck.com>;
 Wed,  5 Jan 2000 09:01:23 -0500 (EST)
Date: Wed, 05 Jan 2000 09:00:06 -0500
From: John C Klensin <klensin@mci.net>
Subject: Re: Back to the drawing board,
 was Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to
 Informational
To: Ed Gerck <egerck@nma.com>
Cc: iesg@ietf.org, Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
Message-id: <2170001740.947062806@p2.jck.com>
MIME-version: 1.0
X-Mailer: Mulberry (Win32) [2.0.0b6, s/n U-301227]
Content-type: text/plain; charset=us-ascii; format=flowed; format=flowed
Content-disposition: inline
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I've trimmed most of the cc's on the theory that everyone 
relevant except possibly Scott are on the IETF or IESG lists.

Ed, I've followed your comments very carefully, but, applying 
your reasoning to what I see as long-standing principles for 
handling Info RFCs, I reach nearly opposite conclusions. Please 
forgive the length of this note; I think it is important that we 
review and return to some principles here.

I don't have RFC 2223 in front of me and hope we can avoid 
hair-splitting and protocol-lawyering over this, but, in 
general, the RFC Editor has chosen to publish (and the IESG has 
chosen to not recommend otherwise) when

* The proposed document covers material that is at least 
potentially relevant and of interest to some reasonable fraction 
of the internet community.   E.g., a document that described the 
operation of a toaster that was not designed for connection to 
the network might well not be published.

* If the document covers a protocol or discussion about how to 
perform some protocol-related act, it isn't likely to create 
confusion with existing standards or standards-work-in-progress 
or reasonable ways to implement them.  E.g.,  a document that 
described itself as "HTTP 1.3", but was not compatible with HTTP 
1.1, and had not been through the standards process, would be 
unlikely to be published (at least under that name and without a 
lot of disclaimers).

* Whatever the document contains, it is not egregiously stupid. 
My impression is that, while this principle --rejecting drafts 
for publication on the basis of utter stupidity-- is discussed a 
lot, it is rarely actually applied.

More recently, there has been a lot of thought given to whether 
a particular document is part of a marketing plan to publish 
something as informaitional and then present it to customers as 
"an RFC" in a way that implies IETF approval and probably 
standardization.  My impression is that rejecting documents on 
this basis is, like the "no stupidity" criterion often 
discussed, but rarely applied.  These documents often go through 
with significant disclaimers attached, but they mostly go 
through.

By contrast, IETF has (I believe wisely) always steered clear of 
the certification process.   We never make statements --even for 
full Internet Standards-- that a given implementation works, or 
that a particular implementation faithfully reflects a given 
specification.   People and companies make those assertions, we 
don't try to stop them; we hope that the marketplace will 
appropriately reward those who lie (intentionally or otherwise). 
Usually that works, sometimes it doesn't, but, as you know, the 
IETF-authorized "protocol police" have always been a myth.

Now, in the case of this draft document, I was a little 
surprised that the IESG chose to Last Call this doc before 
letting it go to the RFC Editor.  They generally don't for 
informational documents (for which I think we must be thankful). 
I believe that the issues this has raised demonstrates that 
their decison was wise, even though many of the comments  have 
contained more heat than light.  But, if we look at the doc, it 
is a protocol description, supplied by one organization.    It 
doesn't make that clear enough, and it should, but that point 
was made and accepted long ago.  It is arguably not quite clear 
what NSI claims it describes, e.g.,

   * the protocol they are running today
   * the protocol they ran at one time
   * the protocol they wish they were running
   * the protocol they wish someone else were running, but have 
no intention of running themselves.

If that isn't clear to all reasonable readers, it ought to be 
fixed.   Within the traditional domain of info RFCs, any of 
those four (and others) are publishable, but we try to avoid 
confusion, especially in the case of the fourth.

But, I think an argument about whether or not the document 
actually conforms to some piece of code and making a decision to 
publish or not publish on that basis is *very* dangerous for us. 
As suggested above, we don't try to do that even for 
standards-track protocols and putatively-comforming programs.

If, as you suggest has happened here, NSI (or someone else) has 
submitted a document for info RFC publication, and it suggested 
things that aren't true, that is a problem... but it is a 
problem between NSI (again for example) and whomever tries to 
implement the thing, not an IETF problem.   I would expect that, 
if such a situation occurred, registrars who implemented the 
protocol as described in the RFC and then discovered that they 
needed to do something rather different to make it work, would 
be very annoyed.  They might rationally express that annoyance by
     * contacting their lawyers
     * contacting the press
     * writing proposed info RFCs with titles like "NSI RRP
       description considered harmful"
Just a personal opinion here, but I can't imagine the RFC Editor 
declining to publish documents of the latter type if they were 
technically coherent and well-reasoned.

In summary, I believe that our advice to the IESG should be

"make certain this document is clear about what it is and what 
it proports to be, and that the authors (or author organization) 
take responsibility for that being true.  Make certain that, 
should a RRP WG effort be launched, this document doesn't 
unreasonaby constrain it.   If areas are identified in which the 
document isn't clear about what it calls for, get those fixed. 
Consider attaching a disclaimer that indicates the list of 
unresolved issues contains some fairly serious problems and that 
there may be equally serious issues not on that list.   Then, 
since it is relevant and not obviously stupid, go ahead and 
publish the thing."

regards,
     john

Disclaimer:  I wasn't a member of the review committee (I was 
invited, but couldn't agree to the NDA in use at the time).   I 
did have a chance to look at a draft of this doc that preceeded 
the I-D.  My personal opinion is that, as a example of protocol 
design work, the I-D gets no better than a C- and that it may be 
an excellent example of why it is better to do protocol design 
in the open, rather than in closed groups tied up in NDAs.  But 
I can't get to "don't publish" from finding the thing a little 
distasteful: there are standards-track protocols I find a little 
distasteful and I believe the long-standing tradition of freedom 
to publish things that might be of use or interest is pretty 
important.



From owner-ietf-outbound  Wed Jan  5 09:31:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05609
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 09:30:02 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05577;
	Wed, 5 Jan 2000 09:29:22 -0500 (EST)
Received: from 192.168.124.51 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id PAA11467; 
          Wed, 5 Jan 2000 15:27:29 +0100 (MET)
Date: Wed, 05 Jan 2000 15:27:30 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Ed Gerck <egerck@nma.com>
cc: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
Message-ID: <946543.3156074850@[192.168.124.51]>
In-Reply-To: <387322D9.2C87F0F7@nma.com>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA05577
Content-Transfer-Encoding: 8bit

--On 2000-01-05 02.54 -0800, Ed Gerck <egerck@nma.com> wrote:

> How can you say " in some cases (timestamps for example) it is already
> clear that they use what is specified in the I-D"?  Did you test it? Have
> you been using the protocol that is in use today?

Because I have already received some comments on the last-call from some 
parties which definitely _are_ using the RRP today, and it is confirmed 
with NSI.

All comments are not sent in public, you know, but most do answer the 
question I, as AD, asks according to the process in the IETF.

    Patrik Fältström
    Area Director, Applications Area, IETF




From owner-ietf-outbound@ietf.org  Wed Jan  5 09:32:42 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05760
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 09:32:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id JAA06457;
	Wed, 5 Jan 2000 09:31:13 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05609
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 09:30:02 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05577;
	Wed, 5 Jan 2000 09:29:22 -0500 (EST)
Received: from 192.168.124.51 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id PAA11467; 
          Wed, 5 Jan 2000 15:27:29 +0100 (MET)
Date: Wed, 05 Jan 2000 15:27:30 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Ed Gerck <egerck@nma.com>
cc: "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
Message-ID: <946543.3156074850@[192.168.124.51]>
In-Reply-To: <387322D9.2C87F0F7@nma.com>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA05577
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

--On 2000-01-05 02.54 -0800, Ed Gerck <egerck@nma.com> wrote:

> How can you say " in some cases (timestamps for example) it is already
> clear that they use what is specified in the I-D"?  Did you test it? Have
> you been using the protocol that is in use today?

Because I have already received some comments on the last-call from some 
parties which definitely _are_ using the RRP today, and it is confirmed 
with NSI.

All comments are not sent in public, you know, but most do answer the 
question I, as AD, asks according to the process in the IETF.

    Patrik Fältström
    Area Director, Applications Area, IETF




From owner-ietf-outbound  Wed Jan  5 09:42:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05899
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 09:40:03 -0500 (EST)
Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05663;
	Wed, 5 Jan 2000 09:31:02 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout4.email.verio.net with esmtp (Exim 3.12 #7)
	id 125rSl-0007Vo-00; Wed, 05 Jan 2000 14:30:59 +0000
Received: from [209.21.28.65] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125rS6-0004ag-00; Wed, 05 Jan 2000 14:30:18 +0000
Message-ID: <387355E2.78B4830C@nma.com>
Date: Wed, 05 Jan 2000 06:32:02 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: John C Klensin <klensin@mci.net>
CC: iesg@ietf.org, Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
Subject: Re: Back to the drawing board,was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 toInformational
References: <2170001740.947062806@p2.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



John C Klensin wrote:

> Ed, I've followed your comments very carefully, but, applying
> your reasoning to what I see as long-standing principles for
> handling Info RFCs, I reach nearly opposite conclusions.

Then, we have gone full circle because your reasoning is exactly
mine in its gist -- as I wrote in the subject line, NSI should go back
with the proposed RFC and make it clear before it is accepted to
be published as an info RFC.

I think your review is also very useful for future uses and it
helps IMO to stress the IETF role as a third-party in the process.
I am snipping it off for clarity here, not for lack of importance.

> In summary, I believe that our advice to the IESG should be
>
> "make certain this document is clear about what it is and what
> it proports to be, and that the authors (or author organization)
> take responsibility for that being true.  Make certain that,
> should a RRP WG effort be launched, this document doesn't
> unreasonaby constrain it.   If areas are identified in which the
> document isn't clear about what it calls for, get those fixed.
> Consider attaching a disclaimer that indicates the list of
> unresolved issues contains some fairly serious problems and that
> there may be equally serious issues not on that list.   Then,
> since it is relevant and not obviously stupid, go ahead and
> publish the thing."

Yes, but IMO IETF RFCs, even informational, should not be
bureaucratic milestones in a chart but real contributions -- where
it is OK to be wrong since in Science a NO is also an answer.
So, an RFC should not be fictional or clearly wrong.

And this has nothing to do with "freedom of press" but with
old accepted rules of technical publication in whatever forum.

Cheers,

Ed Gerck



From owner-ietf-outbound@ietf.org  Wed Jan  5 09:43:33 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06057
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 09:43:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id JAA06831;
	Wed, 5 Jan 2000 09:42:07 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05899
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 09:40:03 -0500 (EST)
Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05663;
	Wed, 5 Jan 2000 09:31:02 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout4.email.verio.net with esmtp (Exim 3.12 #7)
	id 125rSl-0007Vo-00; Wed, 05 Jan 2000 14:30:59 +0000
Received: from [209.21.28.65] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 125rS6-0004ag-00; Wed, 05 Jan 2000 14:30:18 +0000
Message-ID: <387355E2.78B4830C@nma.com>
Date: Wed, 05 Jan 2000 06:32:02 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: John C Klensin <klensin@mci.net>
CC: iesg@ietf.org, Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
Subject: Re: Back to the drawing board,was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 toInformational
References: <2170001740.947062806@p2.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



John C Klensin wrote:

> Ed, I've followed your comments very carefully, but, applying
> your reasoning to what I see as long-standing principles for
> handling Info RFCs, I reach nearly opposite conclusions.

Then, we have gone full circle because your reasoning is exactly
mine in its gist -- as I wrote in the subject line, NSI should go back
with the proposed RFC and make it clear before it is accepted to
be published as an info RFC.

I think your review is also very useful for future uses and it
helps IMO to stress the IETF role as a third-party in the process.
I am snipping it off for clarity here, not for lack of importance.

> In summary, I believe that our advice to the IESG should be
>
> "make certain this document is clear about what it is and what
> it proports to be, and that the authors (or author organization)
> take responsibility for that being true.  Make certain that,
> should a RRP WG effort be launched, this document doesn't
> unreasonaby constrain it.   If areas are identified in which the
> document isn't clear about what it calls for, get those fixed.
> Consider attaching a disclaimer that indicates the list of
> unresolved issues contains some fairly serious problems and that
> there may be equally serious issues not on that list.   Then,
> since it is relevant and not obviously stupid, go ahead and
> publish the thing."

Yes, but IMO IETF RFCs, even informational, should not be
bureaucratic milestones in a chart but real contributions -- where
it is OK to be wrong since in Science a NO is also an answer.
So, an RFC should not be fictional or clearly wrong.

And this has nothing to do with "freedom of press" but with
old accepted rules of technical publication in whatever forum.

Cheers,

Ed Gerck



From owner-ietf-outbound  Wed Jan  5 09:51:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA06188
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 09:50:03 -0500 (EST)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05901
	for <ietf@ietf.org>; Wed, 5 Jan 2000 09:40:02 -0500 (EST)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id IAA05745
	for <ietf@ietf.org>; Wed, 5 Jan 2000 08:39:59 -0600 (CST)
Message-Id: <200001051439.IAA05745@gungnir.fnal.gov>
To: ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: I-D nroff macros 
In-reply-to: Your message of Tue, 04 Jan 2000 23:03:22 EST.
             <3872C28A.537C118@att.com> 
Date: Wed, 05 Jan 2000 08:39:59 -0600
Sender: crawdad@gungnir.fnal.gov

> If you send your nroff input file to the RFC editor as well as the
> nroff'd output file, which is the recommended practice, then modifying
> the ms macros themselves is not an option.

Well, sort of.  You can .rm an existing macro and .de it differently.
I do that for the SH, H, XS, XA, XE, XE and TC requests, then use
soelim to put my macros into the nroff source I send to rfced.  So
far no feedback from that quarter, positive or negative.

> Automatic TOC processing cannot be done directly within nroff unless you
> are willing to accept the TOC at the end of the document. To place the
> TOC at the beginning of the document usually requires two passes. The
> first pass is used to generate the TOC, which is then sourced (.so'd)
> into the document for the second pass.

That's the LaTeX-like way.  What I do is start a draft-with-TOC with

	.so tmac.idt
	.pi ./fixtoc.sh

where fixtoc is Postel's fix.sh with the added function of moving the
TOC from the end to a marked point near the front.

				Matt

(But the fun part was computing the six-months-plus-five-days
expiration date in nroff.)



From owner-ietf-outbound@ietf.org  Wed Jan  5 09:52:50 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06258
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 09:52:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id JAA07108;
	Wed, 5 Jan 2000 09:51:23 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA06188
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 09:50:03 -0500 (EST)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05901
	for <ietf@ietf.org>; Wed, 5 Jan 2000 09:40:02 -0500 (EST)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id IAA05745
	for <ietf@ietf.org>; Wed, 5 Jan 2000 08:39:59 -0600 (CST)
Message-Id: <200001051439.IAA05745@gungnir.fnal.gov>
To: ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: I-D nroff macros 
In-reply-to: Your message of Tue, 04 Jan 2000 23:03:22 EST.
             <3872C28A.537C118@att.com> 
Date: Wed, 05 Jan 2000 08:39:59 -0600
Sender: crawdad@gungnir.fnal.gov

> If you send your nroff input file to the RFC editor as well as the
> nroff'd output file, which is the recommended practice, then modifying
> the ms macros themselves is not an option.

Well, sort of.  You can .rm an existing macro and .de it differently.
I do that for the SH, H, XS, XA, XE, XE and TC requests, then use
soelim to put my macros into the nroff source I send to rfced.  So
far no feedback from that quarter, positive or negative.

> Automatic TOC processing cannot be done directly within nroff unless you
> are willing to accept the TOC at the end of the document. To place the
> TOC at the beginning of the document usually requires two passes. The
> first pass is used to generate the TOC, which is then sourced (.so'd)
> into the document for the second pass.

That's the LaTeX-like way.  What I do is start a draft-with-TOC with

	.so tmac.idt
	.pi ./fixtoc.sh

where fixtoc is Postel's fix.sh with the added function of moving the
TOC from the end to a marked point near the front.

				Matt

(But the fun part was computing the six-months-plus-five-days
expiration date in nroff.)



From owner-ietf-outbound  Wed Jan  5 10:01:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA06595
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 10:00:02 -0500 (EST)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06007;
	Wed, 5 Jan 2000 09:42:27 -0500 (EST)
Received: from randy by rip.psg.com with local (Exim 3.12 #1)
	id 125rdc-00066h-00; Wed, 05 Jan 2000 06:42:12 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Ed Gerck <egerck@nma.com>
Cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
References: <1630979.3156055539@[192.168.111.25]>
	<38730F10.CCF092BB@nma.com>
Message-Id: <E125rdc-00066h-00@rip.psg.com>
Date: Wed, 05 Jan 2000 06:42:12 -0800
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> 2. The proposed RFC is not what should be used:

this is not relevant to the publication of *this* rfc, the intent of which
is to document what IS used not what SHOULD BE used.

randy



From owner-ietf-outbound@ietf.org  Wed Jan  5 10:04:17 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06810
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 10:04:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id KAA07659;
	Wed, 5 Jan 2000 10:02:49 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA06595
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 10:00:02 -0500 (EST)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06007;
	Wed, 5 Jan 2000 09:42:27 -0500 (EST)
Received: from randy by rip.psg.com with local (Exim 3.12 #1)
	id 125rdc-00066h-00; Wed, 05 Jan 2000 06:42:12 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Ed Gerck <egerck@nma.com>
Cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        "David R. Conrad" <David.Conrad@iengines.com>,
        Rick H Wesson <wessorh@ar.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
References: <1630979.3156055539@[192.168.111.25]>
	<38730F10.CCF092BB@nma.com>
Message-Id: <E125rdc-00066h-00@rip.psg.com>
Date: Wed, 05 Jan 2000 06:42:12 -0800
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> 2. The proposed RFC is not what should be used:

this is not relevant to the publication of *this* rfc, the intent of which
is to document what IS used not what SHOULD BE used.

randy



From owner-ietf-outbound  Wed Jan  5 10:17:55 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07206
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 10:16:26 -0500 (EST)
Received: from embelia.wanadoo.fr (smtp-rt-7.wanadoo.fr [193.252.19.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06839
	for <ietf@ietf.org>; Wed, 5 Jan 2000 10:05:07 -0500 (EST)
Received: from antholoma.wanadoo.fr (193.252.19.153) by embelia.wanadoo.fr; 5 Jan 2000 16:05:00 +0100
Received: from ftid33tp9h (193.250.228.30) by antholoma.wanadoo.fr; 5 Jan 2000 16:03:03 +0100
Message-ID: <00c301bf578d$edfab8e0$0100007f@ftid33tp9h>
From: "adies" <adies@wanadoo.fr>
To: <jeff.hodges@oblix.com>, <jeff.hodges@kingsmountain.com>,
        <dkbrown@acs.ucalgary.ca>, <rlist@anon.lcs.mit.edu>,
        <kelsey@counterpane.com>, <jsyoung@jsyoung.com>,
        <jonkatz@slashdot.org>, <senator@mcconnell.senate.gov>,
        <cryptography@c2.net>, <jd@well.com>, <ietf@ietf.org>,
        <request@ai.mit.edu>, <saitar@nb.sympatico.ca>
Subject: jurisprudence
Date: Wed, 5 Jan 2000 15:53:36 +0100
MIME-Version: 1.0
Content-Type: multipart/related;
	boundary="----=_NextPart_000_0083_01BF5795.06C3C4A0";
	type="multipart/alternative"
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

This is a multi-part message in MIME format.

------=_NextPart_000_0083_01BF5795.06C3C4A0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0084_01BF5795.06C3C4A0"


------=_NextPart_001_0084_01BF5795.06C3C4A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Vous constatez r=E9guli=E8rement

    =20
    =20
      =20
    =20

Vous constatez r=E9guli=E8rement :


     qu'il est difficile de disposer de temps pour r=E9unir la =
documentation n=E9cessaire =E0 la constitution de vos dossiers ou =
simplement y acc=E9der.
    =20

     que l'acquisition et le maintien d'un fonds documentaire exhaustif =
et actualis=E9 repr=E9sente un investissement important
    =20

     que ces deux contraintes nuisent au d=E9veloppement de votre =
activit=E9
    =20

Accessible par Internet, fax ou courrier, ADI=E9S se propose de prendre =
en charge vos recherches documentaires de tout ordre dans des d=E9lais =
rapides, AVEC OU SANS ABONNEMENT, et vous permet ainsi lib=E9rer du =
temps pour vous consacrer =E0 l'essentiel de votre m=E9tier ou =E0 de =
nouveaux dossiers.

ADI=E9S s'adresse =E0 tous les secteurs d'activit=E9, dispose notamment =
d'un fonds documentaire actualis=E9 quotidiennement et constitu=E9 de =
1,2 million de r=E9f=E9rences juridiques et l=E9gislatives =
(jurisprudence, lois, d=E9crets, directives europ=E9ennes...) et fournit =
=E9galement un service de veille th=E9matique personnalis=E9.



=20

Agence de Documentation et d'Intelligence =C9conomique du Sud

Technopole HELIOPARC-B=E2timent Einstein

2, av. du Pdt.-P.Angot

64000 PAU

Tel : 05 59 14 71 11

Fax : 05 59 14 71 14

Website : http://www.vmgnet.com/adies

e-mail:adies@wanadoo.fr

=20


------=_NextPart_001_0084_01BF5795.06C3C4A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:v =3D "urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:dt =3D=20
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"><HEAD><TITLE>Vous constatez =
r=E9guli=E8rement</TITLE>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type><BASE=20
href=3D"file://C:\ADIES\mailing adies\">
<META content=3D"strtedge 010" name=3D"Microsoft Theme">
<META content=3DWord.Document name=3DProgId>
<META content=3D"Microsoft Word 9" name=3DGenerator>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"./mailing%20adies_fichiers/filelist.xml" rel=3DFile-List><LINK=20
href=3D"./mailing%20adies_fichiers/editdata.mso" =
rel=3DEdit-Time-Data><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:HyphenationZone>21</w:HyphenationZone>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>
<!--
 /* Font Definitions */
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:16792199 0 0 0 65791 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	color:black;}
a:link, span.MsoHyperlink
	{color:#660000;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:#003399;
	text-decoration:underline;
	text-underline:single;}
p
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	color:black;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</STYLE>

<SCRIPT language=3DJavaScript>
<!--
function MM_swapImgRestore() { //v2.0
  if (document.MM_swapImgData !=3D null)
    for (var i=3D0; i<(document.MM_swapImgData.length-1); i+=3D2)
      document.MM_swapImgData[i].src =3D document.MM_swapImgData[i+1];
}

function MM_preloadImages() { //v2.0
  if (document.images) {
    var imgFiles =3D MM_preloadImages.arguments;
    if (document.preloadArray=3D=3Dnull) document.preloadArray =3D new =
Array();
    var i =3D document.preloadArray.length;
    with (document) for (var j=3D0; j<imgFiles.length; j++) if =
(imgFiles[j].charAt(0)!=3D"#"){
      preloadArray[i] =3D new Image;
      preloadArray[i++].src =3D imgFiles[j];
  } }
}

function MM_swapImage() { //v2.0
  var i,j=3D0,objStr,obj,swapArray=3Dnew =
Array,oldArray=3Ddocument.MM_swapImgData;
  for (i=3D0; i < (MM_swapImage.arguments.length-2); i+=3D3) {
    objStr =3D MM_swapImage.arguments[(navigator.appName =3D=3D =
'Netscape')?i:i+1];
    if ((objStr.indexOf('document.layers[')=3D=3D0 && =
document.layers=3D=3Dnull) ||
        (objStr.indexOf('document.all[')   =3D=3D0 && document.all   =
=3D=3Dnull))
      objStr =3D =
'document'+objStr.substring(objStr.lastIndexOf('.'),objStr.length);
    obj =3D eval(objStr);
    if (obj !=3D null) {
      swapArray[j++] =3D obj;
      swapArray[j++] =3D (oldArray=3D=3Dnull || =
oldArray[j-1]!=3Dobj)?obj.src:oldArray[j];
      obj.src =3D MM_swapImage.arguments[i+2];
  } }
  document.MM_swapImgData =3D swapArray; //used for restore
}
//-->
</SCRIPT>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1027"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1"/>
 </o:shapelayout></xml><![endif]-->
<META content=3Dfr http-equiv=3DContent-Language>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR></HEAD>
<BODY aLink=3D#999933 bgColor=3Dwhite lang=3DFR link=3D#660000=20
onload=3D"MM_preloadImages('jurisrouge.jpg','#945434730600')"=20
style=3D"tab-interval: 35.4pt" vLink=3D#003399>
<DIV>&nbsp;</DIV><!--mstheme-->
<DIV class=3DSection1>
<TABLE border=3D0 cellPadding=3D0 height=3D78=20
style=3D"WIDTH: 55%; mso-cellspacing: 1.5pt; mso-padding-alt: 0cm 0cm =
0cm 0cm"=20
width=3D"55%">
  <TBODY>
  <TR>
    <TD=20
    style=3D"PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; =
PADDING-RIGHT: 0.75pt; PADDING-TOP: 0.75pt; WIDTH: 11%"=20
    width=3D"11%"><!--mstheme-->
      <P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: Arial"><A=20
      href=3D"http://www.vmgnet.com/adies"><!--mstheme--><SPAN=20
      style=3D"TEXT-DECORATION: none; text-underline: none"><IMG =
border=3D0=20
      height=3D89 id=3D_x0000_i1043=20
      src=3D"cid:007e01bf578c$a4ee93c0$0100007f@ftid33tp9h"=20
      width=3D89></SPAN></A></SPAN><o:p></o:p></P></TD><!--mstheme-->
    <TD rowSpan=3D2=20
    style=3D"PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; =
PADDING-RIGHT: 0.75pt; PADDING-TOP: 0.75pt; WIDTH: 89%"=20
    width=3D"89%"><!--mstheme-->
      <P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: Arial"><A=20
      href=3D"http://www.vmgnet.com/adies"><SPAN=20
      style=3D"TEXT-DECORATION: none; text-underline: none"><IMG =
border=3D0=20
      height=3D61 id=3D_x0000_i1040=20
      src=3D"cid:007f01bf578c$a4ee93c0$0100007f@ftid33tp9h"=20
      width=3D450></SPAN></A></SPAN></P></TD></TR><!--mstheme-->
  <TR>
    <TD=20
    style=3D"PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; =
PADDING-RIGHT: 0.75pt; PADDING-TOP: 0.75pt">
      <P=20
      class=3DMsoNormal><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></P></TD></TR></TBODY></TA=
BLE>
<P><SPAN style=3D"FONT-FAMILY: Arial"><!--mstheme-->Vous constatez =
r=E9guli=E8rement=20
:<o:p></o:p></SPAN></P>
<TABLE border=3D0 cellPadding=3D0 cellSpacing=3D0=20
style=3D"WIDTH: 100%; mso-cellspacing: 0cm; mso-padding-alt: 0cm 0cm 0cm =
0cm"=20
width=3D"100%"><!--msthemelist-->
  <TBODY>
  <TR>
    <TD=20
    style=3D"PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; =
PADDING-TOP: 0cm; WIDTH: 31.5pt"=20
    vAlign=3Dtop width=3D42>
      <P class=3DMsoNormal><!--mstheme--><!--msthemelist--><IMG =
border=3D0 height=3D15=20
      hspace=3D13 id=3D_x0000_i1027=20
      src=3D"cid:008001bf578c$a4ee93c0$0100007f@ftid33tp9h"=20
      width=3D15><o:p></o:p></P></TD>
    <TD=20
    style=3D"PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; =
PADDING-TOP: 0cm; WIDTH: 100%"=20
    vAlign=3Dtop width=3D"100%"><!--mstheme-->
      <P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: Arial">qu'il est =
difficile de=20
      disposer de temps pour r=E9unir la documentation n=E9cessaire =E0 =
la=20
      constitution de vos dossiers ou simplement y =
acc=E9der.</SPAN></P></TD></TR><!--msthemelist--><!--mstheme-->
  <TR>
    <TD=20
    style=3D"PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; =
PADDING-TOP: 0cm; WIDTH: 31.5pt"=20
    vAlign=3Dtop width=3D42>
      <P class=3DMsoNormal><IMG border=3D0 height=3D15 hspace=3D13 =
id=3D_x0000_i1028=20
      src=3D"cid:008001bf578c$a4ee93c0$0100007f@ftid33tp9h"=20
      width=3D15><o:p></o:p></P></TD>
    <TD=20
    style=3D"PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; =
PADDING-TOP: 0cm; WIDTH: 100%"=20
    vAlign=3Dtop width=3D"100%"><!--mstheme-->
      <P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: Arial">que =
l'acquisition et=20
      le maintien d'un fonds documentaire exhaustif et actualis=E9 =
repr=E9sente un=20
      investissement =
important</SPAN></P></TD></TR><!--msthemelist--><!--mstheme-->
  <TR>
    <TD=20
    style=3D"PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; =
PADDING-TOP: 0cm; WIDTH: 31.5pt"=20
    vAlign=3Dtop width=3D42>
      <P class=3DMsoNormal><IMG border=3D0 height=3D15 hspace=3D13 =
id=3D_x0000_i1029=20
      src=3D"cid:008001bf578c$a4ee93c0$0100007f@ftid33tp9h"=20
      width=3D15><o:p></o:p></P></TD>
    <TD=20
    style=3D"PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; =
PADDING-TOP: 0cm; WIDTH: 100%"=20
    vAlign=3Dtop width=3D"100%"><!--mstheme-->
      <P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: Arial">que ces =
deux=20
      contraintes nuisent au d=E9veloppement de votre =
activit=E9</SPAN></P></TD></TR><!--msthemelist--><!--mstheme--></TBODY></=
TABLE>
<P><SPAN style=3D"FONT-FAMILY: Arial"><!--mstheme-->Accessible <A=20
href=3D"http://www.adies.com/"><SPAN style=3D"COLOR: black">par =
Internet</SPAN></A>,=20
fax<!--05 59 27 49 57 --><!--05 59 27 49 57 --> ou courrier,<B> =
ADI<I>=E9</I>S</B>=20
se propose de prendre en charge vos recherches documentaires de tout =
ordre dans=20
des d=E9lais rapides, </SPAN><B><SPAN=20
style=3D"COLOR: red; FONT-FAMILY: Arial; FONT-SIZE: 10pt">AVEC =
</SPAN></B><SPAN=20
style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt">OU</SPAN><SPAN=20
style=3D"FONT-FAMILY: Arial"> </SPAN><B><SPAN=20
style=3D"COLOR: red; FONT-FAMILY: Arial; FONT-SIZE: 10pt">SANS=20
ABONNEMENT</SPAN></B><SPAN style=3D"FONT-FAMILY: Arial">, et vous permet =
ainsi=20
lib=E9rer du temps pour vous consacrer =E0 l'essentiel de votre m=E9tier =
ou =E0 de=20
nouveaux dossiers.<o:p></o:p></SPAN></P>
<P><B><SPAN style=3D"FONT-FAMILY: Arial">ADI<I>=E9</I>S</SPAN></B><SPAN=20
style=3D"FONT-FAMILY: Arial"> s'adresse =E0 tous les secteurs =
d'activit=E9, dispose=20
notamment d'un fonds documentaire actualis=E9 quotidiennement et =
constitu=E9 de=20
</SPAN><B><SPAN style=3D"COLOR: red; FONT-FAMILY: Arial">1,2 million=20
</SPAN></B><SPAN style=3D"FONT-FAMILY: Arial">de r=E9f=E9rences =
juridiques et=20
l=E9gislatives (jurisprudence, lois, d=E9crets, directives =
europ=E9ennes...) et=20
fournit =E9galement un service de veille th=E9matique=20
personnalis=E9.<o:p></o:p></SPAN></P>
<P><SPAN style=3D"FONT-FAMILY: Arial"><!--msthemeseparator--><IMG =
border=3D0=20
height=3D10 id=3D_x0000_i1030 =
src=3D"cid:008101bf578c$a4ee93c0$0100007f@ftid33tp9h"=20
width=3D600><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN=20
style=3D"FONT-FAMILY: Arial">&nbsp;<o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><B><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial">Agence de Documentation et=20
d'Intelligence =C9conomique du Sud</SPAN></B><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial"><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Technopole =

HELIOPARC-B=E2timent Einstein<o:p></o:p></SPAN></P>
<P><SPAN style=3D"COLOR: #003366; FONT-FAMILY: Arial; FONT-SIZE: =
10pt">2, av. du=20
Pdt.-P.Angot</SPAN><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial"><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial; FONT-SIZE: 10pt">64000=20
PAU</SPAN><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial"><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Tel : 05 =
59 14 71=20
11</SPAN><SPAN style=3D"COLOR: #003366; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Fax : 05 =
59 14 71=20
14</SPAN><SPAN style=3D"COLOR: #003366; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN lang=3DNL=20
style=3D"COLOR: #003366; FONT-FAMILY: Tahoma; FONT-SIZE: 9pt; =
mso-bidi-font-size: 10.0pt; mso-ansi-language: NL">Website=20
</SPAN><SPAN lang=3DNL=20
style=3D"COLOR: #003366; FONT-FAMILY: Tahoma; FONT-SIZE: 8pt; =
mso-bidi-font-size: 10.0pt; mso-ansi-language: NL">:=20
<A href=3D"http://www.vmgnet.com/adies"><SPAN=20
style=3D"COLOR: #003366; FONT-SIZE: 11pt; mso-bidi-font-size: =
12.0pt">http://www.vmgnet.com/adies</SPAN></A></SPAN><SPAN=20
lang=3DNL=20
style=3D"COLOR: #003366; FONT-FAMILY: Tahoma; FONT-SIZE: 11pt; =
mso-bidi-font-size: 12.0pt; mso-ansi-language: =
NL"><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN lang=3DDE=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial; FONT-SIZE: 9pt; =
mso-bidi-font-size: 10.0pt; mso-ansi-language: DE"><A=20
href=3D"mailto:adies@wanadoo.fr"><SPAN lang=3DNL=20
style=3D"COLOR: #003366; FONT-SIZE: 11pt; TEXT-DECORATION: none; =
text-underline: none; mso-bidi-font-size: 12.0pt; mso-ansi-language: =
NL">e-mail:adies@wanadoo.fr</SPAN></A></SPAN><SPAN=20
lang=3DNL=20
style=3D"COLOR: navy; FONT-FAMILY: Arial; mso-ansi-language: =
NL"><o:p></o:p></SPAN></P>
<P><SPAN lang=3DNL=20
style=3D"FONT-FAMILY: Arial; mso-ansi-language: =
NL">&nbsp;<o:p></o:p></SPAN></P></DIV><!--mstheme--></BODY></HTML>

------=_NextPart_001_0084_01BF5795.06C3C4A0--

------=_NextPart_000_0083_01BF5795.06C3C4A0
Content-Type: application/octet-stream;
	name="logoadies_copier.jpg"
Content-Transfer-Encoding: base64
Content-ID: <007e01bf578c$a4ee93c0$0100007f@ftid33tp9h>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAgEAlgCWAAD/7Q7YUGhvdG9zaG9wIDMuMAA4QklNA+0AAAAAABAAlgAAAAEA
AgCWAAAAAQACOEJJTQQNAAAAAAAEAAAAeDhCSU0D8wAAAAAACAAAAAAAAAAAOEJJTQQKAAAAAAAB
AAA4QklNJxAAAAAAAAoAAQAAAAAAAAACOEJJTQP1AAAAAABIAC9mZgABAGxmZgAGAAAAAAABAC9m
ZgABAKGZmgAGAAAAAAABADIAAAABAFoAAAAGAAAAAAABADUAAAABAC0AAAAGAAAAAAABOEJJTQP4
AAAAAABwAAD/////////////////////////////A+gAAAAA////////////////////////////
/wPoAAAAAP////////////////////////////8D6AAAAAD/////////////////////////////
A+gAADhCSU0ECAAAAAAAEAAAAAEAAAJAAAACQAAAAAA4QklNBBQAAAAAAAQAAAADOEJJTQQMAAAA
AA1IAAAAAQAAAHAAAABwAAABUAAAkwAAAA0sABgAAf/Y/+AAEEpGSUYAAQIBAEgASAAA//4AJkZp
bGUgd3JpdHRlbiBieSBBZG9iZSBQaG90b3Nob3CoIDUuMP/uAA5BZG9iZQBkgAAAAAH/2wCEAAwI
CAgJCAwJCQwRCwoLERUPDAwPFRgTExUTExgRDAwMDAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwM
DAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4ODg4UEQwMDAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwM
DAwMDAwMDAwMDAwMDP/AABEIAHAAcAMBIgACEQEDEQH/3QAEAAf/xAE/AAABBQEBAQEBAQAAAAAA
AAADAAECBAUGBwgJCgsBAAEFAQEBAQEBAAAAAAAAAAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggF
AwwzAQACEQMEIRIxBUFRYRMicYEyBhSRobFCIyQVUsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNU
ZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSFtJXE1OT0pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH
1+f3EQACAgECBAQDBAUGBwcGBTUBAAIRAyExEgRBUWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNT
FWNzNPElBhaisoMHJjXC0kSTVKMXZEVVNnRl4vKzhMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaW
prbG1ub2JzdHV2d3h5ent8f/2gAMAwEAAhEDEQA/APVUkkF+QxrzWwGy0alje39dxhjP7bkFJkKz
IrrOyd1kT6bdXf5oUfTvt/nX+mwjWus6/wBq7R3/AG36aJXVXWIraGzzHc+Lv3kVNXMtzG41trSK
A1ssGjnzP5/Nbf8AwT+uidPzGZ+FTmMBa29oeAeRKr9as20V1A/zjxI8m+7/AKrYofVgz0DBj/RD
8pSU6iSSSClJINuZi0uDLLWtc4hobMmT5BGSUpJJJJSkkkklP//Q9VQaObf+MP5GoyFR9O7/AIz/
AL6xBSVJVuodRwem4zsvOuZj0M5e8xJidjB9Kyx0e2tnvXnPX/8AGTnZu7H6OHYOOdDe6De4Efmt
9zMb/p3f8UkkC3s+sWh2c1k6VNAPkXHc7/o+mn+reUxnRMWoMe61jCHVtaZHudo4u2sZ/bcgfU3A
xHfV3AyLGerdbX6lj7CXkvc5znvd6m7c7cuhRQgLs2yNjWUDuX+93+ZWWs/8FQ766aq3XZdr7GAa
tJhp/kiuvY139pXFjXY+d1Ii9pYyg/zTHOMgcbnBrXe9ySnOzbzayxzGiqtjHmqtoDQ3Qn838/8A
eW/0p7rOl4ljyXOdTWXE8kloVEdAe9hbbeBuBaQ1s6EbfpFyuY3T7MeivHblWenU1rGABg0aNolx
Y5yCm6mJAEnQDugnDqIh7rH+M2OE/wBlrmtQ7KOnYrPVtrraB+c4bjP8mdzkVJH5+EzR17J8A4E/
5oU6b6b2b6XB7ZiR4hYeX1J9wNdDfQp4IEBzh/Kj6CX1fss/amZSXH0hTS9rOwcTa1zv+igp/9H1
VVXXGmvNuDdxqJcGkwDtqrfyrSpXx9n6ju490/D0a0FPivVOt9S63kDN6habX81VDSusO/Moq/N/
4z+ds/wj0/Ruh9V61ca+m45tDSBZaTtrZP8ApLT/ANQz9Iuo+qP+Lq7Lqpzeuh1GPtaWYX0bHwP+
1P51Nf8AwTf03/Fr0nHxsfFoZj41TKaaxDK62hrQP5LW+1KlxPZofVrCt6d0TF6fc5r7cRpqseyd
pLSdWbvcreb1HA6fUbs7IrxqxrutcGD5bl5r9fvrX13B6zk9Hwcg4mNXss30+21xsY21wddrtZu/
0S87ybbLrjda51tjjLrbCXuJ8XPsLnJKEbfZ87/Gp9U8YO+z225z2zDaKnAEj/hb/RrXSdIcH9Mx
bBoLKm2AHkB49QA/5y+cJPJ18V1XTP8AGZ9aem0VY7LqciihoYyu6sE7WjaxnqVuqsdtStJh2fcU
l5h0/wDx0AQ3qnTT/KsxXz91GRs/8/rsui/Xb6tdb2Mws1gyH6DGu/R2yfzG12fzv/WfUSWmJDpd
QzvsdYIbve8kMHaR3csG6+2+z1Lnb3dvAeTG/mrU69/N0f1j+RZCSFKx9X5/bmZ4fZaNP7d6ro/Q
dOvZA192JV8NLLklP//S9VVOwbqs9vjP41MVxVa2b7cys6B5An41tagp8s6F/jI690+muvNI6nVt
b/PHZaNB/wBqWNd6n/Xq7LP+FXX4H+M76tZJazJdbgPdz6zJYD/x1Pqs/wA9cX1r/F713pA3Y7P2
jiMGltDf0gA/0uLLrP8Atj1VzQEPc06OGhaRDgf6p9yGq6gXpvrR07N+s/1tyr+g0nOx3Cpoyq/5
iW1ta8faj+h9v9ZW8f8AxS2U49mZ1zqTMWilpstbjtLoY0b7d192zZtaPzal1/8Ai4/8SWKIgh9s
/H1Hqj/jby7qPqs2mslrcvJrptIJHsiy7Zp++6pqKrOz5P1V/R33x0jHsoxGTtfkP33W/wDCWx+j
p/k11rNcY7SU7i7WEgyddHT9yDIET3Dgfjyozx5ceS6T6rdXwumZgq6niUdQ6XkOa3Jrura81jj7
Rj2PDnVur3fpGf4Vi9H6t/ii+rWc19nT7Len2v8Acz0z6lOv/AWe7Z/xd1aKDKjqNHk/8XnX+sZ2
Zb0zNy7MnFoxnXUstO9zXiymv23O/S7Nljv0e/Yu6XJ/V76l9Y+q31lf9rAuw7sWxlWZX9Bzt1Vn
p2N+lTZ7fz/p/wCDXWJMcqvRSN0Of2/b4fY2f+fbUFG6Kf8AsgcP+6Y/8+vSQ//T9VVej+lZI82H
/ohWFWo/pmUP+L/6lBTZVHqPROkdUbHUMOrJMQHPaC8Dn2W/zjP7DleWf1frvSujU+r1DIbTIllf
0rH+VVLf0liSnKwurfVj6uZVn1eN/wBi9J3q1C8n04u/SbGZFnt9rt/869WPrb0Vn1l+rt2Jjva6
xwF2JY0gtNjPdX7/ANyz+bXmX1x6izqnWj1BlVlFeRTXsrtEP2tNlYc5vu/nNu9YmN1DOwLfU6fk
24rx/obHMB/rMB9P/opWuAc3JxbaLrKbWOrtqcWW1vEPa4GHMeP3moUOaZjtotXqvVc7ql32rqdo
vvDAz1NrWOLW/Q9T0ms3u/lrLc7UxoECyBf8wz4FfR3R2WV9IwWW/wA4zHqa+f3gxocvDvqr0npe
bk/bOtZtGD0rGIdaLLA224t932eimfVc3/SvYz/i13XXP8cfRsZpr6LQ/qFpGltgNNI00Pvb9os/
qenV/wAaiFktdA9f14H0Kj236/5rljrifqx9a+tfWL60h/U799bMe8049Y2VMMN+jX+e7/hLfUsX
bJLSKNKRuig/84Cexw/yWuQUXpH/AIoGeeI7/wA+JIf/1PVVmZfVOn9LuysjqF7MakNq9zzEzvbt
Y36djv5LFprO6l0HpnVbqLs6r1TjEmtp4k/vIKecs+s/1h6/Y7H+rWIcbFna7qOS3Uj96ml230/+
u7/+KV3o/wBRsHEu+3dSsd1PqDjLr7zu1/t7l0tdddTBXW0MY3QNAgBSRU811r6ldI69kXX3+pRl
V7amXVOiGtYxzGOqduqcxrrHfmrjep/4reuY7i7Csqz6/wA0fzNnzbYX1f8Agi9SpEWX+bwf+hWm
ycvEw6jdl3V49Q5fa4Mb/nPLUE2XwbP+rvWsMluZgZFXiTW5zfk+r1Gf9JYz6HMJEERpDhB+bSvc
Mv8AxhdEY809NZd1W/8ANGMwlk/uuvs2s/7b9Rcl1H6nfWP6ydWv6rXi14dWYWOPr2AFjgxldlbm
1tfY7Y+v/RpUuE+75q+vUkj5pjX+J+ZPkvWcH/E/QYd1TOJ8a8ZobrP+muD/APzyuu6P9T/q70Zw
swcNgvH/AGos/SWz4+pZu2f9bSpPHWz5j9Qfqx1vDzG9aysc4+C6uylht9tjy8e0soP6TZ7fpvXd
rb65/RGf8YPyOWIksJs2VIvSP/FBX/4Uf/58CEidI3H6xNHZuGT5+6w/+QSQ/wD/1fVUkkkFKSSS
SU4XXcL6y5FzK+jZjcKizXIsLWufMbP0e/dt+is/F/xd9MNv2nquRd1PJOrn3PJE/wBouXWpIqa2
J07BwmBmLQypo/dGv3rIz/rZ0nomRZh5vrHILnWNrrqc+WvO5h3sGxdAhPxcayz1LKmPs43OaCfv
KSnl3/X/ANTTA6Pm5R/NJb6Y/wCnud/0VD/nH9d8kxi9BZSDw660n74ZUuva1rRDQAPLROkp5Hf9
cLHh3WmY1eF2ZTO8Wf4M7i93t+kpAEmBqT2W19YLG1dNfe+fTpIe/aNx2j91o+kuRxem9c+tB9zX
9L6K7lp0vuH/AArm/wCDd/omez/jElMb+r5GVk/s76v1jNzJIsyOaKfPd9DIf/a9JdJ9Wfqz+x/V
ysm9+V1DLg5Fzj89rf5LVo9L6R0/pOM3HwaW1MAgkDU/1nK6gp//2ThCSU0EBgAAAAAABwAFAQEA
AQEA/+IMWElDQ19QUk9GSUxFAAEBAAAMSExpbm8CEAAAbW50clJHQiBYWVogB84AAgAJAAYAMQAA
YWNzcE1TRlQAAAAASUVDIHNSR0IAAAAAAAAAAAAAAAAAAPbWAAEAAAAA0y1IUCAgAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARY3BydAAAAVAAAAAzZGVzYwAA
AYQAAABsd3RwdAAAAfAAAAAUYmtwdAAAAgQAAAAUclhZWgAAAhgAAAAUZ1hZWgAAAiwAAAAUYlhZ
WgAAAkAAAAAUZG1uZAAAAlQAAABwZG1kZAAAAsQAAACIdnVlZAAAA0wAAACGdmlldwAAA9QAAAAk
bHVtaQAAA/gAAAAUbWVhcwAABAwAAAAkdGVjaAAABDAAAAAMclRSQwAABDwAAAgMZ1RSQwAABDwA
AAgMYlRSQwAABDwAAAgMdGV4dAAAAABDb3B5cmlnaHQgKGMpIDE5OTggSGV3bGV0dC1QYWNrYXJk
IENvbXBhbnkAAGRlc2MAAAAAAAAAEnNSR0IgSUVDNjE5NjYtMi4xAAAAAAAAAAAAAAASc1JHQiBJ
RUM2MTk2Ni0yLjEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAFhZWiAAAAAAAADzUQABAAAAARbMWFlaIAAAAAAAAAAAAAAAAAAAAABYWVogAAAAAAAAb6IA
ADj1AAADkFhZWiAAAAAAAABimQAAt4UAABjaWFlaIAAAAAAAACSgAAAPhAAAts9kZXNjAAAAAAAA
ABZJRUMgaHR0cDovL3d3dy5pZWMuY2gAAAAAAAAAAAAAABZJRUMgaHR0cDovL3d3dy5pZWMuY2gA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAZGVzYwAAAAAAAAAu
SUVDIDYxOTY2LTIuMSBEZWZhdWx0IFJHQiBjb2xvdXIgc3BhY2UgLSBzUkdCAAAAAAAAAAAAAAAu
SUVDIDYxOTY2LTIuMSBEZWZhdWx0IFJHQiBjb2xvdXIgc3BhY2UgLSBzUkdCAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAGRlc2MAAAAAAAAALFJlZmVyZW5jZSBWaWV3aW5nIENvbmRpdGlvbiBpbiBJRUM2
MTk2Ni0yLjEAAAAAAAAAAAAAACxSZWZlcmVuY2UgVmlld2luZyBDb25kaXRpb24gaW4gSUVDNjE5
NjYtMi4xAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB2aWV3AAAAAAATpP4AFF8uABDPFAAD7cwA
BBMLAANcngAAAAFYWVogAAAAAABMCVYAUAAAAFcf521lYXMAAAAAAAAAAQAAAAAAAAAAAAAAAAAA
AAAAAAKPAAAAAnNpZyAAAAAAQ1JUIGN1cnYAAAAAAAAEAAAAAAUACgAPABQAGQAeACMAKAAtADIA
NwA7AEAARQBKAE8AVABZAF4AYwBoAG0AcgB3AHwAgQCGAIsAkACVAJoAnwCkAKkArgCyALcAvADB
AMYAywDQANUA2wDgAOUA6wDwAPYA+wEBAQcBDQETARkBHwElASsBMgE4AT4BRQFMAVIBWQFgAWcB
bgF1AXwBgwGLAZIBmgGhAakBsQG5AcEByQHRAdkB4QHpAfIB+gIDAgwCFAIdAiYCLwI4AkECSwJU
Al0CZwJxAnoChAKOApgCogKsArYCwQLLAtUC4ALrAvUDAAMLAxYDIQMtAzgDQwNPA1oDZgNyA34D
igOWA6IDrgO6A8cD0wPgA+wD+QQGBBMEIAQtBDsESARVBGMEcQR+BIwEmgSoBLYExATTBOEE8AT+
BQ0FHAUrBToFSQVYBWcFdwWGBZYFpgW1BcUF1QXlBfYGBgYWBicGNwZIBlkGagZ7BowGnQavBsAG
0QbjBvUHBwcZBysHPQdPB2EHdAeGB5kHrAe/B9IH5Qf4CAsIHwgyCEYIWghuCIIIlgiqCL4I0gjn
CPsJEAklCToJTwlkCXkJjwmkCboJzwnlCfsKEQonCj0KVApqCoEKmAquCsUK3ArzCwsLIgs5C1EL
aQuAC5gLsAvIC+EL+QwSDCoMQwxcDHUMjgynDMAM2QzzDQ0NJg1ADVoNdA2ODakNww3eDfgOEw4u
DkkOZA5/DpsOtg7SDu4PCQ8lD0EPXg96D5YPsw/PD+wQCRAmEEMQYRB+EJsQuRDXEPURExExEU8R
bRGMEaoRyRHoEgcSJhJFEmQShBKjEsMS4xMDEyMTQxNjE4MTpBPFE+UUBhQnFEkUahSLFK0UzhTw
FRIVNBVWFXgVmxW9FeAWAxYmFkkWbBaPFrIW1hb6Fx0XQRdlF4kXrhfSF/cYGxhAGGUYihivGNUY
+hkgGUUZaxmRGbcZ3RoEGioaURp3Gp4axRrsGxQbOxtjG4obshvaHAIcKhxSHHscoxzMHPUdHh1H
HXAdmR3DHeweFh5AHmoelB6+HukfEx8+H2kflB+/H+ogFSBBIGwgmCDEIPAhHCFIIXUhoSHOIfsi
JyJVIoIiryLdIwojOCNmI5QjwiPwJB8kTSR8JKsk2iUJJTglaCWXJccl9yYnJlcmhya3JugnGCdJ
J3onqyfcKA0oPyhxKKIo1CkGKTgpaymdKdAqAio1KmgqmyrPKwIrNitpK50r0SwFLDksbiyiLNct
DC1BLXYtqy3hLhYuTC6CLrcu7i8kL1ovkS/HL/4wNTBsMKQw2zESMUoxgjG6MfIyKjJjMpsy1DMN
M0YzfzO4M/E0KzRlNJ402DUTNU01hzXCNf02NzZyNq426TckN2A3nDfXOBQ4UDiMOMg5BTlCOX85
vDn5OjY6dDqyOu87LTtrO6o76DwnPGU8pDzjPSI9YT2hPeA+ID5gPqA+4D8hP2E/oj/iQCNAZECm
QOdBKUFqQaxB7kIwQnJCtUL3QzpDfUPARANER0SKRM5FEkVVRZpF3kYiRmdGq0bwRzVHe0fASAVI
S0iRSNdJHUljSalJ8Eo3Sn1KxEsMS1NLmkviTCpMcky6TQJNSk2TTdxOJU5uTrdPAE9JT5NP3VAn
UHFQu1EGUVBRm1HmUjFSfFLHUxNTX1OqU/ZUQlSPVNtVKFV1VcJWD1ZcVqlW91dEV5JX4FgvWH1Y
y1kaWWlZuFoHWlZaplr1W0VblVvlXDVchlzWXSddeF3JXhpebF69Xw9fYV+zYAVgV2CqYPxhT2Gi
YfViSWKcYvBjQ2OXY+tkQGSUZOllPWWSZedmPWaSZuhnPWeTZ+loP2iWaOxpQ2maafFqSGqfavdr
T2una/9sV2yvbQhtYG25bhJua27Ebx5veG/RcCtwhnDgcTpxlXHwcktypnMBc11zuHQUdHB0zHUo
dYV14XY+dpt2+HdWd7N4EXhueMx5KnmJeed6RnqlewR7Y3vCfCF8gXzhfUF9oX4BfmJ+wn8jf4R/
5YBHgKiBCoFrgc2CMIKSgvSDV4O6hB2EgITjhUeFq4YOhnKG14c7h5+IBIhpiM6JM4mZif6KZIrK
izCLlov8jGOMyo0xjZiN/45mjs6PNo+ekAaQbpDWkT+RqJIRknqS45NNk7aUIJSKlPSVX5XJljSW
n5cKl3WX4JhMmLiZJJmQmfyaaJrVm0Kbr5wcnImc951kndKeQJ6unx2fi5/6oGmg2KFHobaiJqKW
owajdqPmpFakx6U4pammGqaLpv2nbqfgqFKoxKk3qamqHKqPqwKrdavprFys0K1ErbiuLa6hrxav
i7AAsHWw6rFgsdayS7LCszizrrQltJy1E7WKtgG2ebbwt2i34LhZuNG5SrnCuju6tbsuu6e8Ibyb
vRW9j74KvoS+/796v/XAcMDswWfB48JfwtvDWMPUxFHEzsVLxcjGRsbDx0HHv8g9yLzJOsm5yjjK
t8s2y7bMNcy1zTXNtc42zrbPN8+40DnQutE80b7SP9LB00TTxtRJ1MvVTtXR1lXW2Ndc1+DYZNjo
2WzZ8dp22vvbgNwF3IrdEN2W3hzeot8p36/gNuC94UThzOJT4tvjY+Pr5HPk/OWE5g3mlucf56no
Mui86Ubp0Opb6uXrcOv77IbtEe2c7ijutO9A78zwWPDl8XLx//KM8xnzp/Q09ML1UPXe9m32+/eK
+Bn4qPk4+cf6V/rn+3f8B/yY/Sn9uv5L/tz/bf////4AJkZpbGUgd3JpdHRlbiBieSBBZG9iZSBQ
aG90b3Nob3CoIDUuMP/uACFBZG9iZQBkQAAAAAEDABADAgMGAAAAAAAAAAAAAAAA/9sAhAAEAwMD
AwMEAwMEBgQDBAYHBQQEBQcIBgYHBgYICggJCQkJCAoKDAwMDAwKDAwMDAwMDAwMDAwMDAwMDAwM
DAwMAQQFBQgHCA8KCg8UDg4OFBQODg4OFBEMDAwMDBERDAwMDAwMEQwMDAwMDAwMDAwMDAwMDAwM
DAwMDAwMDAwMDAz/wgARCAEhASADAREAAhEBAxEB/8QA0gABAAEEAwEAAAAAAAAAAAAAAAYEBQcI
AgMJAQEBAQEBAQEAAAAAAAAAAAAAAAECAwQFEAABAgYBAwMCBAUFAQEAAAABAAIRAwQFBgcIECAS
QCExMBMiMjU2UDQVFiZwgEEzFCU3EQACAQMCAgUGCQkFBwMFAAABAgMAEQQhBTESIEFREwZhcZGx
IhQQgaHBMlJicrIwQoKSI3OzJBVA0aIzdFBDU2Ojw2Thg5NEJXUWJhIAAQIGAwEBAAAAAAAAAAAA
IQBQECAwQAExYIARcXD/2gAMAwEBAhEDEQAAAN/sgAAAAOgjxJz6AAAAAAAAAAAAAAAURZDtMfk0
JeAAAAAAAAAAAAAAW0tJVl9BrMZFMqAAAAAAAAAAAAAFmKAuRdgC3mtRlEyoAAAAAAAAAAAAWApS
7lyAAIaYNMjmXQAAcS1FiJmfQAAAAAAfCMEoAAAMWGMTIJmAA4FgKI+EcIIZLMhgAAAAAA+EaJMA
AAYNIyTAzAR86DmXwuBEzE5bSSGcgAAAAAACLkoAABjuXHtglJMiRFSARUxOcSiL2Z2AOgtxbTqB
xIUTklh9AIuSgAEZl0/nbHsb/b4SQ7gACNmIzrBxLsZBOJzO0uRXlQW8xcRwsJs+cwCKkqB0mtmO
mmvPtYujNFx6Ma4AAAYxJAV5cyqOQAABDjGhTgiVbXRzAIsSkjC6J8O+Db0ptZ7ssz9MekOuAAAE
PJgAAAAURjEiwAInW1kdgBFS4r5i8PVC7Os6179TYfXL0B1yAAp1gWd1msTlAAABFzF5RgAEJNtT
tAIkc18qOHqprFmSdc90OnPJ0kjOJDprAme2A+fTC2ulkuvVfp8/K7IAAAwOUYAAIhW1sdwBEioX
ym4+moudw+/HafOawjxgPn01Xz6cIOlq656ZeM3UybXZ5Z1uMoXlkTfO42AAYIKIAAELrbGO8Aip
Ur5wTrvdrllKQCLr5FcvbaN6tpQY39mvronKojknO2Sxl7XHZjXLYjfnkdgwQUQAAIZW10VIBFDv
WHy5UuQBGl8guXvtmtW6OOdUvLTefjfSn2OC8euOletZBNbazz7jdPFD9YpwAAQitsIqwCJlevlL
y9OeWdld88v6xVJHJfILl7aK9bzvnmnXDKVxqp5fbjXHSl6Pmp03PC7pddOOc/GOU6XOT0T6/NyH
eIAAglbZxWAESLmvktz9NBl9kksuXuknNxiLU2fuM93NZL5Z8ffhLO6fF6dW376cNXhM9Rxc/tqT
636K7+flXXAAAQg2vKwAiJdl8mefptmZ1ydE7VmuV/t9Y+vlrga257eYmfVRt8M54X08LjnE9nHc
f0+LGed68Z9kG59U36Bdvm5heYAAQc2tK8AiJKTWpvUfPWA89dLXK5kyesPXz1qDz1z69Op6KCb6
JanLs1nuznv1Nh7j0+6eGls16vTTHPqz5PPmO8QABAza8uIBFCVgozAzWuzWF89Lhh6r9eFeg0Fe
nS3Peim+KsXvmO6Xn0leesm/Bli4FKYBXsQAAQGtsYuIBFiUgAFmrE9uYsyvBgedPLue20avRy3y
k563yxmo6YqD0r14dmLzAwaW0AAEArbKLiARUlQAALWaac+2wu8ZSuSedM9OrufTRY18w6Om/vO1
N51PSepW/n54uAMHFsAABBK2ui4gEWJSAAC2nk5y9VnzZnJmLWslb4aYz1Y7x1p856sXjt31KO09
dtfOlSda4E598eXE+3yAAEGramLoARYlIABTGGTz44+qxlM1Ru3Rm8Ol6i2YlE123N03z9DOvi2X
w1yz3095erBzvvB3+dna+YAAQStqYuwBFSVAHUYjNS6qzDXL0xuW3zfTOqumrNdUWb8OOpkqZnTO
Db1jTrxy7LreXp83YC+UAAQI2qLuARclBxMbGplWA2ojK5rBda956Yw5dKeWl10pm7fbapes4bdW
bT3fXdsTrs53e79+bsNrygACBG1RdwCJFKal1AzZ2M5l2KEoS8GNdXBcYRm8W562GbtF6UWVPdU9
da/TjrfbeeYnHbqeWasgACBm1BeADFhpZWwpsHF9PoKEoC+gHEsekSmtP89dYOfp6LqkXo3m7XGd
+vDaXPHYHExWR8AAEENpy8AFvLaSA5AApS1l+ABSmMzVrPbXLHWR9M5X1zzfZnBzl+QGHyNgAAxv
W2kXgAAAAHQWkvpSGMDA1YnL6ZxXMNTWTvgAAYfI2AADG1beRcQAAAAdBh0wdWLCSmbjMMS8ixMw
AdRbSzEXIwdQAKcwRV2N5IqQAAAAfDXkpjLpKioPoMckYIOQ+osR8pjvJIZSiTAEcNdqzqbRxdz6
AAAAAcT6fQACBmrdSYmkSokpdy5lSYnIufDD1Y8NwIzGdwAAAAAAAAAPh8Pp9AABiQx4a71kU23i
Un0AAAAAAAAAAAAAAGHDTitqIzwVQAAAAAAAAAAAAAAAMbGNq2LjvAAB/9oACAECAAEFAP8AYNH+
BRUUB/AS5EE9B/APIlD2UUCh68+5Xwh7rwTQR3+Q9R/yg2KayCj2EgIuX4ivBNYPUQTWkr47PNFr
imsghAI/l/4XkUJi+4FH0gCj2ge8OjvYeXsSorzUQjBAIv8AFB4QIPoQe4fJ6OKB6loXigOh6eME
HEIOH14IOKDo9SmqJKAKDAnFgT3xTUFCKggew9B6A9PIoOivABQAUenyh0BKEUTBQXuo9Copvx9c
9R89XFAINigxQUYJwimkoEQ8AUWqB9BAItCgoI+yaffq4dA6CBKJKiiV8oe3SKivAFAQ9AfdQCc1
Nb2O+IIiCaUSnFAKCIQ9NFA9hRcgYgIr5R6j1AcVEdS2PRqBRICKJ6D1BUF8LyKE0IuBTUYIRQRC
aI9jnwTSSPRn56+3QrxARCAQBci3xRcAi5EkpoigIekcoqKj0Hb5ELyKhFHoBBAx9J4tKLAvAqC9
kOkEAjAI+yj5LxK9ug900Q9N5FQBRlheLkQUQooiK+V9teBXiF4JrQPVeRR904oKKJUShFGC8vWk
RQY5CS4rxaogLyPrwV5FR/1o/9oACAEDAAEFAP8AZSGBO9h/AGsigIdH/HrwwDsf8eugAEAvZEhO
d3iW4+nHyfhRCLu0NJQklCUAhAL5Tvn0wRKJ7PBBrVEBOJQCh7BPpySZBRlOHpS4hEx7QPZR9y0F
EAIQAgF7qBR9kYFGSCjIciCPQkHtHy34jFBqMUPgGKaAor5RHTxK90YOUyQE5jm/WHy74LQU6WR2
NdAEhfcATpxQLypbPAJ3yopogiUCE50CnNDlNaGv+r8ooEhQijLagxF5CLiestgao9PlCATmhCKL
fJBsOgJQU78/1QiggF7o/HWU2JJJXjBe6Yz2cIEGKmMKJe1MnEJtQ0ouDk2Cqfz/AFQ4hAhABecO
h+OshNKBXsEXleUUSmlTWxHQPITJynGLvr+RXmVEKIh1klNRChFFFQTnIe6eIO6kx9GDDsYYFAlR
PSARCc1NCmfm9P4BeJ6smIHq1OgiYoJ/5vURXiCjJC+0UyPUdGiKcQ0ExPRshxU1oa70rRFEwUes
EEUXeIdM8yASmyCUySGIElVH5/RtKAQ9kT1HYWeSbJaEGgdQqn8/o/IhCYvJeaBPQFRUUVFNgopo
RBQVQYu9KCooTChMCDunuj0ioleft92CdPKc6J9SDBSnFeSCMFEBGYE6d5KJPrZZUQvuwX3Ci8o+
/rwf9av/2gAIAQEAAQUA+nUVVNSSqbOLPWXOMf4BX3Ogtkr+uXm8OpcUpzO2reJeO1+v8jdkdn9b
cL3bLYhW5LexRYxb6ab03BVuuNn0cCMW9XcMitlvmfbyi9K3Y/bLc7reqw0FpzkeWI6Of5Yt6mty
mikz/wCmZBelbbLbrVL7djVpkWfN/bENCvLsX7iQBcMkslsFPsS31NeHBw+vhUtjaHv2PV/evGZy
XT8S0H+1+r3sltuGaWCgX9dyi6r+1Lxc25SMctFPcKt9BQaqyudlFm+vhT/Oi78hqjW3zIm+WP8A
Hud9zGaiqpaRlRnFoa7/ANmbXYMwsVTqCzWq2BZblkuzynOc92Qj/wCBx0fHHPr4V/L92cbaw/FZ
IIcJlnqL9S4LrrI8cttNglsE6koaOhl9ctyuXZJM2bNnzFeP0nji8HHus6qpqds/KMephO2BjkpO
zadPa69ZpPBZsCpFyyK+y6rEMmbc6Lsww/g7MvzvF8Gt+0OWOR352m6CZlGwbbgljoRKpqenHble
TS7DSz586qndJ9tqLnRawxvLMKtYfsKoY2x5pUtOE/fZKwDHJak4zj8gMo6SUFc7tb7RIyPMa69l
YbeKyVtOWYy+uGAtd0nTpNPK3FyptOMNynM75l1zE8Q43uAzzvtOOHLqmRruwShT4bjdMqe2W6la
AGjvyDOqK3Cur6y5VHTFZBlbglf9XXESf/Us0zvGsCtO5eSOQ7FnzHuLWl0xzXknjhOc7YXfr/8A
lPo3C50NrkZBm1wur+yxvMnbsgxk9cSI/qOUXh2P47sPY2UbAuzpkXGe0Bv4zKkzHTtB4Flloynt
qqylopeS7u1vi8nWNXJuNl+hkeZUVmFyutwu8/ttDZo3FTfy/XE5fjedjua3A54d5kRY6QHDW2lc
z2DXa54xYJhIy2VKk44iQBk+08BxGTmfOLA7S3Luauz75Lum18+vCkV5qpvHR7X6n+hdwRdu6gc6
XtymMafriwhkGfta7B6kO8rNZrjeqzUPFClkMt9toLVSrNHfaxrOOZOGY9Jzjk7tPLVcLhV1Tp09
xeaolGa4PlTQw6c5eP11jlo5xa3rHY3yG1Xk5or5ZrkztvP6v3Mlz5W26MxpeuNwGR5y5jML1/rH
Idi3nVej8T1jS9djGGB3GY4Tqia5ynzBNmTJjjMd4Pc4h6DHtDZgam1U4llxJbZdoZnjzcN5o7Vx
uZgnOHX+QuxvOcUy6n6Xog3juq532tpW8+VH1x0/5LnglnDNM5JrWpxjs2CI4PdHH/0zWgsLCEZL
SZjWh0sEtf5xdAKL/Ez/ALYmPY1PfMlTG1PkbFneU4u/UfO25WaRr7euu9kUdwniqr+66kDZlsMa
Drj5H905kI4jIuVbbqvBeXGfWBYPyc1rmTqG4UFzp1nhDcKugYamVTlzbTr3KL9PxPhrsi/tn8SN
V4JZ9m5ZiV4Ez8KjF73MYi2VVGoeGMLjAQgXgEFWe/XjHqvRl9uuS6r7rx/+m2v+Q62E/wCX5cPL
FKwBlUZri77kTj2yc4xZYzzI2hZVf+ZtNkuLYLxm2Jm03AuH2DY4rRi+P2KTca+mtVv5H7ou+zcy
mOa11U/ya+X4SXNiGse1PJmIjya1pCgSfxNRXG9wdpjuvLQ3Y9r/AJDrZAW5plQLsYu0gmsmNDD+
GDw3y8CWYFJ/9uXWiQ2mtXTmLsSrw3X86c9z3z3eTqgNL58HS5bZqMhrTre84vQ3uRxE1Hs21bA4
I5tYpOW6h2Dhb5tO9pEoCXxhmF2nu7I3eGe2cxtvW1RGdTZUudL2jxIsGSvzfUeb4FUOkEo0vm5p
cxYC7xzC1Em19Odd6qp2bVJHlMlF76iP3JcgNXgFJpzBsuWBxa3Lc9f5dTVEmrp7hZbPdmbE4Y6z
zJ24+LGb6ymcYh46o7sqMM7sn6X1t4hnXSvt1BdaXN+JOvsiGZ8SdkYzLu+NXyyPwxkqXk1lj/R+
nOvHJ39yVUiDvgPLfGUHNbLPmZxcGyotFtn1Eidx3yidlOr+ldQ0lypf7as+KVvdlTI5/ZP0vrRN
hnHbfMWx3JZOVcbdcTVZ2htp6cqtfT851xW2uoYJsnxLmCZ0Y6DXTHuDXNIp2Pc7hXMmv1r1yOP9
e7sqJGeWP9L60/7+7shb5WHF+Wt5xqvwvkRrrMmU1XS1kuqpaetpuUOjKjAr1OlMLplLAikH2gx7
AGn7gliWqf3ncTrKbTqvrkpjkHdlkp397WP9L6ygBn/dkH6FkbpjL6Jz/LHNx7DxBYrzeyygmT+V
Gps+t2z7Hilsv9TJcHzA5i/CQP8AuLHudiGOVeR33XeOvxXClNmy5MvbfK/XetabUuyLntSwd2aT
Pt5Pj7vK09W+2wO2qq6aik53yBwi2VGS+QvxYYTHuaXOmAzn/ea4uIqJ4ltnzi5EAmSXNVrttxu9
fxi46Mws3jKscsFPsbnHrLFpWyuV+ztg1NTPmzTxNntnav7s6P8AkWN+9n6uBbn/AFmTZclmxuQe
GYNIzXduwtl1WCaTvdZPzSn+1k81rwJhnRDneUDGefesnzPJzi4kRUXQ1Zs+z62qMu5s7Rv1Ffs+
zbIwQWmJUskHiR7YD3Z5+4cZ/Rus/wBs8RIYM93ZhWB02dckc7zmfhunciyyswHQlnscuptFHbbH
kXE+TltuzbRWwMGn1cqbSzBR+U2dLcx86U6WZ9M2YJlPMlnxIUIp/nLmT5QYhLLw+VLY0tIDWuLe
Ij/8G7s7H+QYz+jda2YZefZptPDsFpNkcoMly52N6vyvNq/X/Hq22uXacctlnlAQV69rRh/7amyZ
M9mX6E1tmYyjhRKmPyvjXsrHJ1xxS9259RTS5RqpL3NfTPaplO0mdKa0lpJ+2GtbTMJbSumHVHGf
Ndo1Wu9R02n6Xuzv9wYz+i9dwSKuTQNwbMM7yDXnHOkohZMUtVkkgADpefe0Yf8Atrq5rXCvw3FL
o2v0Jqi4TOVGocYwCunUjnvm25swf094TrZOebdhtyu1Rg/DvY2THWnDzXuFq12e12Slzlnhk/dn
hhesYMbL1u1pp7tItOG2a0Oa1rB2V7Q+iw39s9lXXUdBLzDkFrjD28ic6kbOsUqhn1JtGq8yvLLD
w52Jc5WL8McLoBjmscHxWR1z39zd2ePnPzLGGltm+lVfyuHftpVtxoLdKy3kTrTEzlvMO+3A3PJN
s7BqcY4+366OwvR9hYLTp7XVlNPTU1Kzuz2P9y92R11FW7HsQDbX9KpBNPXbrxbXWOZVzAym6trb
rtbPanF+PN8uZxTjRb6RWPV+OWdlPb6Ola8Q2L2TZ8iQ2fk2P07a7ZuH29XPkBgVvFVlNDmM/srK
2kt9Pnu6aq5TdHa1vVReKCSaek+k4RbtbUNVmdzxbjZa6IWXW2PWdkigpKYdcpvUnGctuXJrX9E2
68xMdki58wL1NFy5KbOuYnbE3JdDOp9uX4UWj8susyj413yasHwufgdo65dm9hwuiveR5jtW46o4
+BismPW+yU31PFpPds7F52TWY8ZLlUVVp4uMAt3GmyyFQ6HxilNJq/GaUSMOsVOpNqt8gCRJatgN
DciTnNa3Pd3UVqdimusnz26a00ta8bppFPKppfpCAUGMCgB37C/cOR5TYsVoss2Nk+xqjVvH6qr3
4thNqxulAAHrtzGttcmlxLMdi3/WGiLfZJNFQU1BK/gG3v0TU/8AM0v/AFd3/9oACAECAgY/AOpY
4WeCiYzFg84OYDhGZTDdmPxoQFAI3GqIYjclBnC1MJCxhhHQr//aAAgBAwIGPwDt6EYaYQ2agGXS
COLAUAhlfaAjnGLQUxLm6CMRlbRgIZYy+ihlkzdFCBmMvmL/AOQK92w64EaJYwjfjoZ//9oACAEB
AQY/APyZnypUhhXi8jBV9JqLbMXvHEx5FyOXlQsRoADr8laf7A77PyEgTq5j7R8wGp+KjFsGAYcf
gdxzQUTr1ROLUuZvORJumaNeabSJTofYjGg4V/VYAE/p2LE1lAUAiViNPM1RZr8XUH0/27ly51Ex
F0gW7yt5lW5of0+AbVgtb+YyRzTspsfZTUDQ9dDLy+bP3DTmysk87XtbQG4A+HxJkji/0fuJIqj/
AArWPf6g9X9s93LnIzDouNjjvJLnhcDQceugZXGy4RH0Y/byWvfrNuXqoyxRd5lE8z5Mx7yUt28x
8/QzMxfpxRMUvp7RFh8preOq2O5/V1+asf7g/tT4WAj7huC6dzjjmAbXRm4DhQbd8r3DEuD7niGz
MLg2Z6CYcCo350p9qRjaxJY669KLEUi+VKA46+SP2vxctb2f/El/DUH3B0ySbAakmj71mJzi37JD
zub8PZW9Q4iY0iQzOIxO7AEFjYHlF9Pjq6m48n9gzXCgSNmzhmA1PKRa58n5CDFHDGhBOv50hufk
Are0U2PuU7C/2EY/NUH3B0C0jBEGpZjYD4zRUZHvU3VHjjvLns5h7Py1y7RtHukRNvec08oAPXya
H0c1f/0G8yOhBHu+LZE18pAv8a02z7VipJntyjIyHvI0fLrYMb2Y9fLWVnRn9pjQyTLftiUsPVUe
VMbsy3/sG4ra3JuGQv4T8/5DPyDwaZlW2vsoeQfIK3ZfrYeQPTEwqEdi13mVNHBHwDSsEF/OSKMO
3JPuORY2THjYi47SbfIDVsbEh2iBrftJz3kuvYCPWlCTftyyNyYEkRFjHEL+QEkfERX8jiRwtaxd
Vu5HlY3J9PwNg4TB9zkFtNRECOJ8vYKLuxZ2N2Ym5JPaa3Ww1OHkW8/dNUQ+z/YN2/8AyeT6k6cu
BJucM2+S/sYcGFhJIHa4u3KbC3WL3oEcCL1k7XjxSS+9QvA/dKWIWVSt9PIaXbsbPbAxOWxd+Vp7
cLewND5mFHI3KebcZyQeadza443sbm/lNd1hwRwR/VjULx83Q91xbSblKPZHERg/nN5ewU00ztJK
5LO7G7EnrJPwZ/8Appv4ZqIfZ6HNkTRxL2yMFHymrybjAfJG3eHTyJev2cksx/5cZH4+Wgdt2TNy
SeBZORfSoer4mwpF+/lB9bR1d5sPAS12IAYqPjEnCnhXeJJ1ja3ewnu0JHZy2uKTHy5Q+4REpKT9
Jhe6k/EejvIHAbpkn08vRbcPEu4R4iBS0cJIM0lupUv8Vz7PlrJ2jwajbXtjXQZkZHfsp01bUj9G
1Ycu6ztmTxXyO9lJY94luX/ERSvOjZk4+kZjdL+RQALeerY8KRDhZFC+odLu4bPuMwPcodQo+sw7
KfIyHMk0hLO7G5JPw5GNHFIyTRvC0kaMxHeKR1dYpMPG285rAaTSgwKficj10f2eFiE8LnmYeguK
/nN9WG/VAl9POFjrlzt5zsgnj+0sv6rc1e3FLMesyStc/q8tBU22A24F0Eh9L3NBY4I0UcAqKAPQ
PgM+fMsS68i8XYjqVeJpseG+NtwPsxA+244e2R6hp8G5beHPu4GOQl9BeGO9Ke0Dob2hFiNymPpt
8Lz5EixQxjmkkchVUDrJOgqTZfArJuO7j2Zc1gTDHf6l+JHaf/Wp9z8Q5j5U07F2DklQSb6casvs
g9fUaUHi0RN/M6fkNw3Tcsp0YTtFyRgXuoB4m9gAbDSj3pnnv9dwtv1AtezgI57ZS0nyMSK5cbEh
hXrCRqvqFWAsBwA/IPjbYVy83hzg80KHykH2j5BTZWbM00zfnMdAONgOAHkHw7i//GTGkHxQonrW
k8w9XQ35eobhIfT8D7t4jzExowGMMRYd7Kyi9kFHbNm7za/C41WFHIkc8LuRa5rmJu31iSWPnvXt
HQUOsDqqJSLAwP8AIyfkNy/1j/hH5I5OfMsMYva/0mI6lHEnzU8GCzYm36ryqbSODp7RHC/1R0Xs
f8zGga3pHzVGfsjoeIVHEZrE/GWrc96jj76TBx5JkjPBmUaX4aX41NuHiHNkmQOwhxibIoDGwCgA
ACi1/NR5hdj8tXXifzeulWIXZzYKNfVWN4l3HbZ4tjkjaNMt0YIWZlFrkW4i3HpGbMnjx4hxeVgi
+kkUz5++Y/ei4SNWBu3AA9mtZO5YzCTEy8gywyLqrBlU6Hr/ACL42PbJ3Ead0D7CH7ZHqr3jcJjK
4vyLwRAepVGg6Ut/otBjlPNy29YNR/dHQ8SP+c2So8lgXI9deIi4LD3GYWHG5WwPxHWpG6ldrX4n
U1fh20NPNbjUKbbt7x7fde9zJByRqp4ksfJUWZuEZ3ndVGrZH+SrXvonX8dSpEnJFFJj8kcY5bDv
kFgBbt+C5Nh2mml3ve8aJlveJJFeTTQ6A1JH4ZxpdxnW4V5UIQkdlm7fLT4+1iHacduDRrZuFtDx
+WmXcPEGTIkt+dFYqPkNBsiV8hyRcynmPHy1snIeYBSCfLp+Rzgx5mGRKC3bZz04edSA+HAVJGhA
eQaeioj9kdDxMv8AzoT6e9rxEGFx/T8k248ImNSOouC7afpGkxNuxXy8mYhUgiUuQTpwFY3iDx/7
eRcPFtYFrLb/AHh6vNUeFt2NHi4kQCpDCgRQALcB8GbNcKIe6lZiQAFjlRiTfTQCvddixn3XdLMr
OhXuVcXHbfjU0M+6jB299Fhxbrb4wBTS5ubNPI5uTNI739JNBWUcnURQUe0B20OoVzA66aisTwxu
O3PmYWNfkkBW5J89jUce4YOVhux9t2K8oHy3oLhb5DExtpO6pa/nNK+Bn4+Sr6r3UqOfQD0tw/1M
38Q9PClduaOXCi7oa+yFkkBHp1qE/ZHQ8S2/4sH4ZK8QtILoNuyuYeTuWqPA2XGf3eaY8+U4PdRp
zG5YgaWApZsaBMzf2H7bcXBNj2Rg3t5+PQ8REi49wn0/QNZFtFErm36RoG/KvGwrQcOJ7a8o4dlc
OUDsrt9damw7OurXBt8lFuf2V4dtFnvdToaA2LxDl4lv90JLr6CDUcW8ZJ3fDUqORgnecqixALAi
kxvEcL7PlEDm5ypW506yBx8tJk+Ht0hzY3F17thfT4dwI4HJmI/+Runs32sNR/1pKhPag6HiQf8A
Mx/wvW+94SIhhzGTl4lAt2GnaNKw9t8GZOPDKEHvWKTyTNPwcnmsW1vw6PiAWv8AyE+n6BrLIYW7
2QW/TNG4ueq1EkWPZXOBfttTAG57OulKIefqNWfRhV1vc8a5Qda5ZLUrAcwP51d4Gup4C9HvwH7N
NfTSSeHd2nweTUQo37P0HSoto8f43vOMhULlxIWblt7XAi2vnpcnw/uatMQC2MwPeAm+lgOq1ZWS
BYTTSSAD7bE/P09i8uLb/qtUB+wOh4jHa0B9Cmt+F7f/AG/K1/8AZapMjAypcfIjlciSNivByeo1
Bjb6sW8bXEArmW4m5R2Px4dtDHnyzs2abfs81lEZNrmzj5wKXK27Kiy8Z9VmgdZEPxqSPg38kXHu
GRp54zWVZdO+k/Ga5APbPBeJpRtm05E5Ygc/dtygmkydxK4GNKFYB1KnlbX863VTbv4zzDz4q8+R
PKyqrMBzWA5uuhtHgvblxcbHkIXJAALqDoRbyUC4vfQny1pwq5a1uqrDiK7pdbVqfgsBQN7G3Gkz
9kzpsDLTg8Llb27QDXh7e97yXy90ylyTkZEhuz93lzRrcnsVQOnsX+l+XvWqD7g6HiIdpgPoUVvi
9u35X8Fqye0Sycfvmua+lXvYUo8N77lYCqRaOKQhTbhcUkW9CHeoFsCZI0STj9ZbE+ms/YYvDcsG
7bjA2NHL3qtGDILE8up+Wo8mbF9y23Kbve/luBZyTxtbgajyfEIG65idpYr29dvVSwbTtsGLGn0e
RAW/WNzWTuWWeXGxYmmlP2UFzWdh4+bInhXDk5IMRSFViBy6240vdDRbG3ZR5dGPEdVBgw7w/m1z
yjXqrvIvjFGSxv8AJR5SL1Y8K5VFzRBoW0rwwASeVMoXPb75Men4fk7cdx+rJf56g+4Ohv6nrWFv
Sqn563pRqTgZQt/7LVldX7WTj981ynSjpfSkANm6xXPxPV1VtGOwBRslAQdBxrBx0Flix4kAH2UA
+H+k7c4XM3kPG415uQWAtbq40e8tf6RI628tAyOeZqsTcnqPGuVdWHWau7E2+kK5omIXy1BB4ywl
n2ab2ZXXQr5Taod08H5bYSTxmRJIXDq3Dj7PVeu/8JTJvEYuOQkB+FxpYH5K5N/2OeC3F1BZfkrl
cFWGhUixvV2Bv1VtCH/dT5af9d2+fp+GT2xzfI6f31jn7A6G9DqaCJvQsYp4ZVDxOpR1PAqwsQay
948IT/0/c5AXTBcDuS5N/Za4t5j+tTY+/wC2yBNSssaMyEDrDWII04iuAFuo6EV7QNxwNANqLVsz
R6fzKXPx1gkm5OPFc9vsD4cDZ5HPucGN3iC5sGNr+urjrpRSgDUaXrmPtGuFi1WbhRXluh4GsTZc
vId9h3SdIpkkYlUFuUWBNhUWVjsHgmRZI3HAqwuDRTc8DHzFIsRPEkmn6QNTZm2Idp3GS7AxqO7L
E3HCxFqkysaBtz2ZSxSWFGb2V69PJWHEV5Hjy8pXXUG/ODrfz9Pwv9yf8cdY/wBwerobr5cWM/gH
wvh7ljR5eJJ9OGZA6n4j11Nk7EZNn3CS7WBMkJPULfSHn9qnzNrCb1iJc8uOxLgDtBF/koxbvt8u
K6GxLC4raeRgCcmO2uvGtvvx92h/hr8O270RbHmh5OfzW+cUQpuE41zeiurvD217XGghFzxFexoe
urtr10JcY8siMHRhoQR1itnycjWfGiWF26zYX1+GTCzoVnxZlKSROLghhY1uW07FjLi4AzJ5BCpJ
UMzWNrk24dPwuw4mOYH4nj/vrH+4PV0NyP1sOM/4lHzdI4++7bBnRn/ioC3C2jCzD01/XNmwm2vc
MH9uiwMWibu7k3DXP+KsFAbhceJb/dQD4Z3w15svaw86gAFiLA9fmqU8pTu2s4OhFjwNez16kVfr
FW6+yvZ+lQj9JrlBuRQ5DYXsamEl7JKgW/Z7fDobnfj7zL+M9Pwtb6k/8SKsb7g9XQyfLtw/ip09
zH/izH0ITWRtm/7ek+1Y8zxIIybhQ5Gha9tB5qRY89cDKf8A3OQwHXbjp6qEuJPHPGeDxMHHpBNS
4mVGJcadDHLG3BlYWIqTf9ijebYdyYyyKqG0ZtcjTy1zDXm6uyrDQ0zg+1QJ66t20D1njQI+iLVh
yMpVsrlfXTQAn5+huWt/5iT8R6fhSfTkYZKAdd1aE/PWN9weroTW69tF/wD5R09z/wBJP/DatzQr
3ZGTMeTqHttQkDNFIv0XQ2IoNsu8yFRxil9saC3aKih8T7amdCoCs0QVSbaX01o7R4khfAWZWjdc
mMuoLi2hFrVK/hPMXM22YlwwN+XXQUHANjXKwIvxtQBPxUNKGlxwI/urB2HAj5svLkVFHYDWy7DM
oXIw8ZEmC6+3xNz1/A0srBIkBZ3Y2AA6yanx8XKG775HdRi445lDDTUgjrrO8W7njrjPNuORFDGo
se7UI121OpLHh0/CR7ZMr/sVjH7A9XQfy7aP4vSORlyrDCvF3Nh2/HX/AOrwZglzs/8AlSY1MhHf
+yNE5rBr8TpW6AsQxyZiATzkAyNoWsLkdtqv1ddMF4eahy6dprkYBmvdja9AhbJw5evTtq41PZQL
G5q99eqi0h06qxsDbYWnysg8sMcY5mJNDxZ4pCybyQj48L8vNESvXbhY+Wnyt33KDFgjv3jO405R
c3AueApofC0g8Qbkps0cYbux5yLeusiOHcDtGzzAj3KBnAsTccTpYaU+TPIZsiQkvK5LMSes3qRQ
bum45AbW/FY7dPwmeybJ/wC1WN9weroI3U+3W9Eh6DSzOsca6s7kKo85NSRjIGXuBVu6hj9ouRce
yBx1HKSdFP0qfEwGkwNtc2VISe/IuSLuPo8eCW85qHeMuNlGO65JZgb3jPPck+at2jU//VTH/GaI
J462o3GnVViKB5bVp8lW4Crn4LdVPu2TtX9T3VdMZXA5V18tPt21QwbMjgr3sBYygE6WNE774izs
8OSWjeZuXXyCwq9/pak8aB6+3toNJcoaz0T/ACBnM0Z67lRf1dPwp++yP+1WL9weroY3lwGH+Nj8
BZiAoFyToABTPn5yS5VyqQoea7DiAFuSRcGw6qkwvDsZ27b2Y93IBebluCtl1VSNRf2r/Z4V75uA
lkeZuaWaUlnY9pY3JqObLhVpRYm466zY8SJUK48ltOvkNN4h2HcTFuOc0kzY8zErcsfonhxp49x2
18mBfo5EJ5lItfq40IsmMxPws4t66uLMOJsaZCLL1HhQCm/MKsPpVqK1FWGgoNchTpaudOvr66Fj
6a0a7dg4VfqNW1NbjFf6GUCVtwLBv7un4U8k2R8vdVi/dHq6G2La4lxZEv2WDt81SZO858YkQaQq
wuWI0W4vYmxtT7T4NibDwW9k5LCzNroUTiOAILntVkr37c2myZpiDJPOWdiOPFqjn3CINILE3FLF
iwqvKLXArSs//Ty/gNbf9xvxtRimjWWNtGR1DKfODTPuG1JBkm/LNjhUsSb8LEVJJ4Y3URhrlUkA
U+bXT5alj/pb50CaiaMAggC+hBsaZc7bZ4CmjFkNh8dE2PN1ixogLagDwNcp0oa8x+rRDgBR21fQ
A0Aq69VCPkvfQWFL7tjSYG3Hlb3yZAsfJfU3J7PJWfsEOVJlTTTK85kCrylQbW5Sb/S6fhT9/kf9
qsX7o9XQ/q2Cf5mCIoqFeYHW4vwqSfcnmyWLnlaS/KoPEKosFGnUKiydyjBYWJBFLHiwKpUWuAKs
BYfDnj/x5fwGtv8A3Z/G3QKsAQeIOoornbNiTBtWJhUE+cqAaaSfw7jgt9IKumvXretvn8M4wxIM
vjCg0tY8fRRDix6qsOI66KhdRwNAsPPUeLtmLLkzSWFlRmFybDgKifcsQ7Xt7rfv5RyvbycxFe8b
3Gu+ZnMGHer7AIFuJNz20uFtGHDhYqABYoECLpp1cazexu6bT90vT8Kn/wAif1R1i/cHq6Bx8lQy
HQg0Xx4EDHW9hVlFh0clSLgxuCDwIINbd+6P426Pe5k8cEf1pGC381+NFcrclycrlDLBDcsQxsCA
AXI/RravFO0yA7WmQ+Iq8hiYSRrzWPPrrfsqyQs7sbAKLkmv5TapgGtysykDX4qgyMwRYcMmrB3H
MB5RofkqCfxBlS5eUn+YkLEIfMT/AHVFDs+zQRNEABM688h5esk9DJ+5F/DHT8K46n9iBPJy2/OL
xAn0VjA/VHq/Jzfu3/DW3/uz+NvgM2dkx40QF+aVggsPPxqSGfc1ycyO37CLmLe1wNlDPby8tPi+
DtsMKMGUZMw5GvwVgoLk9v0kotnbjld3Ib9zjlok4WtdTzEfeZqR8iJlVuNxUfgvxHj9/i98+5AD
Rg5iVNL3GvL2UjYexwF4zzK0gDm48nChHjQpDGosqRqEAA8gA6eT5Uit+oOnsWFBMks+EjrkxqQW
jaR1IDW8grGA+oPV+TmA4lGA9FYuNvKynMgXlMSj6zFgbC5tY9lNjeENs9yV1sJ5rc4a/YpYnTsZ
KaTcNxy3WVie7iZols/EHlsWHkYtSNkxMqntFJJmoGIsTcUojxkLL5BQWGJVA4WFRAaD3P5m6Jea
VI0HFnYKPSa5pNyxyB1RuJD6EuaPe5wYj6QA5LdevelKv7/i2vY99lwRkE+RWc0+/wC3SxzYmRZY
mhcSrZABbmGnV2dF8vNmSDFiBZ5ZCFUAC5qbYPA4Pcse7l3W3tOOBEYPUfrGo93zFduZ+8eR7szG
9ySTqTUUJ4qoH5MjtFCVR7BOvppHzEDMONxSiLGS6+QUFhiVQOwdCLe85f5FMQK73Cj8++p0vwp3
iz8R1S/s+8hpbjq5I1Y/LTvtsT5NrckUeM4J/SlaMfJR/pO2ZLsdB3xhhUfEiSX9NFNuxPdgxu3e
yz5Fx2WBjHyUTFlDGD2uIMaK/wCs6O3y0I8vdM9kJvyRu0Iv5o+UV3+UkskrcZJCWY+cnWgZIyKl
2LIFnOQ89vsyIg+boHJ3jIAndS+LhprNMRYWVerU8TpXu1mh2jnvBgRXCAcxIL2+kahzt1i7Gswp
IMWJV5QBcDs/K3sL9OTDhF2ZbU8jLozE8KU5A+SlMqA243oEwIbeSgFxk0+yKHJipp5BVo4FHxVp
Go+KmAFgYo/n+AsxCqouSdAAKbavCHJuG6nRswWaCI9Yt+cfJXv+5NNkyztzSTTEsTzG549VzwFR
TZMKtOADqOuhHEoVRoAP7LYi9aKPRWnTb9xH89Nnb1lpjxqLrHcGVz9hL3PDqr+lbPFJgbITYQRk
97Lc8ZGB+KwqHM3OIiPQ2YVHFjwqHUDW1WHD+3zb3hAPMMcRorXIDqSQSOsa02Rusk2U3OVVpL8q
KTwVeAHmqLKzog0wAOo66WHHQIqi2g/2C/3aP3qXzdP/2Q==

------=_NextPart_000_0083_01BF5795.06C3C4A0
Content-Type: application/octet-stream;
	name="anim2.GIF"
Content-Transfer-Encoding: base64
Content-ID: <007f01bf578c$a4ee93c0$0100007f@ftid33tp9h>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhwgE9APf0AN8YH98aIN8fL98fON8gIN0qNe8ACO8PD+APEOAPH+8AEOkAHO8PEO8PH+8Q
D+AQEOAQH+AfGe8QEO8QH+8fEO8fH/AAD/APD/8AD/8PD/AAEPAAH/APEPAPH/8AEP8AH/8PEP8P
H/AQD/wQBvAQEPAQH/AfEPAfH/8QEP8QH/8fH+APIO8PIO8PL+8PMOAQIOAQL+AfIOAfL+8QIO8Q
L+8fIO8fL+AfMO0QNe8fMPAAIPAPIPAPL/8AIPgAL/8PIP8PL/AQIPAQL/AfIPAfL/8QIP8QL/8f
IP8fL/YUNvAfMP8fMOAgEOkgK+AgMO8gMO8gP+suOew2P/AgL/cjN/AgP/AvP/8gMPkyO98wQPUf
QOUqQO8vQOs1RvsrQPgoUPY1SfA/T/8/QP8/T/A/UN9AQOZMTO9AT+ZGVO9PUOhQWO9QX/hATPBP
UPBPX/lAVv9PUP9PX/BQX/BYWP9QUP9QX+9PYP9PYPhPa/BfYPBfb/9fYP9fb/9fcO1oau1rdO9w
b+9wf/lka/9vb/Zmd/9vcP9vf/Bwb/Bwf/N6cPB/f/9wcP9wf/9/f/BvgPB/gPB/j/9wgPhwiP9/
gP9/j++AcPSAe++Aj++bm/CAgPCAj/WPiv+AgP+Aj/+Pj/WIk/+PkP+Qj/Cfn/iSkv+Qn/+fn/+f
oPifq++qmv2gnf+wn++goO+/v/ClqP+goP+gr/+voP+vr/u0pP+wr/+/r/CwsPC/sPC/v/+wsP+w
v/+/sP+/v/C/wP+1xf+/wO/Av/XFs/DAv//AsP/Av//WvO/AyO/Qz/TFxv/AwP/PwP/Pz//J0P/Q
wP/Qz/nZwP/fz/PZ1v/Q0P/f0P/f3//f5P/jzPDr3//g0P/g3//v3/313+/o7+//7+D//+/w8O//
8O////Xq7f/g4P/v4P/v7//v8P/v//Dz6vD/7//w4P/w7///4P//7/Dw8PDw//D/8PD////w8P/w
////8P///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH/C05FVFNDQVBFMi4wAwEA
AAAh/nlWZXJzaW9uIGZyYW7nYWlzZSBERU1POiBS6WFsaXPpIGF2ZWMgdW5lIGNvcGllIE5PTiBF
TlJFR0lTVFLJIGRlIEdJRiBNb3ZpZSBHZWFyIDIuNiAtLSBodHRwOi8vd3d3LnZpc2ljLmNvbS9H
aWZNb3ZpZUdlYXIvACH5BABkAPUALAAAAADCAT0AAAj+AEsIHEiwoMGDCBMqXMiwocOHECNKnEix
osWLGDNq3Mixo8ePIEOKHEmypMmTKFOqXMmypcuXMGPKnEmzps2bOHPq3Mmzp8+fQIMKHUq0qNGj
SJMqXcq0qdOnUKNKnUq1qtWrWLNq3cq1q9evYMOKHUu2rNmzTouU6FAkxIkSJNbOCBFkQggOQYJI
QAHiR4gJJUCgYPsX4Yy8JBLHLZFiAooZIIKQ6EC5cuUgDTALBMGhg0AOAgFnEPFjBmMOMyjfTbHW
suUQHkIwCPKjg4TKbUO09pzC89oQwEP/Jgi8tsAOrCvLrlDiAuC7JJwP9m1wwgQGnjsAB223td7A
ag/+FH4YosIDEAJ1Gw4BAgTdvxMcsJ4gATTCvyQkJC4xwbXr0AwMVFcDbTUAVwk77MCYBClQcEFj
cHGgFkRqEfZWCcCpx0Fv/nXQQxAlSADCDkFop1sQoAHXgGohdBDEDh00QFcDdlF31Ikp3BViCnul
AEJcHaDwogfu/eVXBSDkGNxBLeaYAge6sQVBCoAEIVhC7IHQwAwTbMjBl08yMEQhgZnm2QnBdbCf
QompAOUQBFHWm0BFUAZiYqDlSNlnrikWV4lsrVUEawykkEJpEwwRAgsdCPHDfSXA2RlresrIAWAY
/sVWCg9AFIIGg4JqY0E5BliBBw8c8UMKDnxgKHr+kMLGHoYI5Qhlhu0JlgIDNdhFQggfdGAdYxTk
OFCLnpYQhK0hHnfpW/YZhAIJHKCwQRh3/ADBBD38cERonO1waQkcuOejhMKylhQIEjDAwQ8wAqFD
EOyFIAGGGYQww77D8sACkUM8hxAIGTxQQ4IwBlGEXergwUNqHaLoo4vD8jcBiEOIQY8RH8gWhBAN
uLdWbT/01+EOpilQAwSKfcZYug3AGUIR7hkohBVuFNJII5NMwogbVmA2gY9tRdpACvTCWldqG/g1
hAgkZHBfZ4ytNYEGOyzBQgh8pUDDB0K8GEQGiznEwRAN7KBtgAiNEFleIQyxgRMbGBoi1QclNrP+
DSwY0UOHwipbp4lBDKEBuwwwEMOGC5fggRE+hOBDAhUkhsK9D4GQuIQlAtEBnI1z2KEEExzRQRWm
WNIpA0X8oAFtP3DghB+dUMIIHR2cUC6HJ2CgVOFB2EAMO9/A8w42iyTwaAk/yPDMPPKA880882ij
ipnvIcRCDs+bA8482WAxbRHvxDPPO/Skr3768LSvvjzpw0+P/PDMUwIKjTnzzjztgwOPOfCgRwDX
p753/AIXkxjDXPIVLYGsaDMuYgELDIEKaLxjgMabRzvalw1XFEKCJYJV4ChzBA0UgBjqEOA3sHGI
ABiISYYCjgWaYAn+mYMe6whEC64xj3ik7xv+0nADCyACixTK4x3rgAUNEFIEF4ijePMgBz2qYQYH
tCUxoxqIX2TADHaA44gEJKD8zGGObejiEVzgkgJkowIJaAAwMSAGN77IjWskIggbmJBDCrcD4REv
gPBohwDDGMZ3GDKAj7ifiEBgAtQUohjmM9/+whEKJ5RAA8LSgLqQwoEMWGAINMjFPNKHB5QVQQOo
AYENavEOd9BDkMfAQXmw04EGEmRaO8AFON6RjiT4Zgfukwf1hjlMAbrPfewgJj3Y0b7Y+egGvZgf
Pag3SGJaE34BjIct8mCiEHGmRDtwDAoYoARJjMN/BOQfAds3DkkogQEoyMAEFLQntvzgA8P+SN87
7lAED1zoIAiwztE+94gezgMODagAD2LxjS+OwwkfQAFEflALcCyTEadCyAU6oIV3CBIe37gDigTy
qyyS9AJBgEEu4tE+a7qUmOiLxztEsQQghAw0Q2jPDlqwC33GAVgnuABELgACDYBSlPSwKDWn+VLq
yeOp8YCfIkxAghgUgQQNYAMrbyjTQ8IjHs04w6M8ox6kYOoDPOjEKOehBA7cSwUp2AEIJkAJ+MlP
HV8Awl3QtMmCRKcIj4DfLlbFGiF8gxq++IUvFsvYxS6jffBYRi520Ytb3IIXvPDFLYqBDXq0IAU1
wAARIME/eEzWF8vwxS4ay1pqwk8djoj+gWcYkKYf1MA9h+DhF6eZjmCI4hGMWAQnXIGMcaivftcA
RAgyUAG/IIcy9yxADY0HA5q90CC7Ss9fInAH/r2jBg1wQNaMC49soMgBEJnAKeBXCyNgQAUIIQEL
+IA+9jlCCHOlD94M4qIQCIG06WMtY1mBWV6w4hjYUAcAkyoOMhxtLVAqwQZ4MIkAouMGLZpBXxkC
mCCgVa306EYvcmELX2QWGQJeLDJqcQtkKCMemugBibwAA0d0lh7jgMQXjBCEMbxilOBohhI80x+l
3CUCKCiCItbxDnawQKIaSMyjZgCJ6CU1fcqwAVxIUOSDhDMIjxBgLoQArCbs4BpOQNn+QTowh3TI
Ix53qGWNKNOWDhwhGzQoGQUswAh00CMbU7COaWw5EJRBARTjuCA9/LA1BmmqAhrIASnUUV9sbCIN
NghUB35QhDoRQQ6iuPE71EEKG1igAnbRDeMsoAl2JFMHIQKRQvZUggbcwZircgAQZmAKqNpBCBHR
gjgCyAgaYcogEhCCL+AhD2bLIxo58Cdy6pQQB4WgEcm0X0KQwx/+CEIX0IOHNApwlx/U5gEhMAIj
2LFMCEBtAmVrSAgugGQlr+Mb41gCCOTT5TXTiwNEYEQjZrADJMAiG82OhzGsoGG3NsAGgogeOkDB
AtCYdCjIkUAIgHCJ+c2DBu8CQoj+5DoERbCDG7l4BTfgwY5UkItBxy7IXa6dVF3ImgQi6MIiM8Tz
ELRhlPBwg49q1BrdTEAM5QLNDjrRbHb0IEqZ6jlwQAA1DZxhHAEkhg16UDktlUAERCAF++YBiSuY
Zj+ZgRG54jKBK5DWovQotQiWFaD5dIAS6ZtHEBhgguUZZEMDgW4czkcPD5BgBJKxAvTeUQu/QKQQ
7H7GBERAAb8XBAVtSKY0HMHueeQhBQ9ai6wN8qi4aGKU8pD6kpCzSZRGotnqsIRnaGOdv1RCmjyA
0g/izZCMb7zj8viGD35AAfSsSvVG59oBnoAFuISgCsb4YjOWgCycyigYKcxGAHz+dF2kuMgzYU5f
CMo2mRmQQBGjZEUBaCHAiYeTeaZZC+kQ5BkSTCJ9u7g4QuCgvjjofy3HUgL3lz7HQSv3kRk10AOH
gA7ywA2FMAMEoh0IsAOiIEDz4AxsMHoN0QFiUA2j5A6n4Bf1MQRBIgE/MID0QH8R0Qbqox2TwRau
EA/+YwUgQBjpkRk/8AA5MgFJsgPQUD+HwBaYwhn8QW0hEAsWtQghkA4CtAsgcin9xl8CMQlrhRC0
dmxzFQSw0FDQ8AP0MhAksAPhRw/jB4AR8X0lMIZlSFKV0W38oYEEwYMkoATMMA9q0AHooRpvOAh+
Rg9jcAAotRRoqIbk1wFypQj+AbYABdBZLBeEopMhx1F/A5h/EMF/6eN/sxaAKFiAZWUQuqEjQmAN
6eMJK9IAtFUCiMAOAJQMUVACbOMQwuIEynBD7MAHvEEZJMAAJ6g+KggRLJg+LpgdcjAP7hAPkwCA
vhElheEbHSAINzQNVlBrtUQu9oIhFRACXJBC4vAEM4AI6aMOctAAtdF9UiiAVXgQGyYcIRAG7KYO
QVNWYUiIZggRg6g+awgX3URbHIIQE1AEEhAEBcAMdvAo6vEka+EG7yAP5uAGuCSIJZKG9liIO0Bz
8DBYJXAG55BU6BAGJVAEKQIcvYEs9od//2cQlkgPmLhtmsiLANiJMid6KdD+A77wRbNwbB2gBFKE
Y1sAeumoEBlwASFQAFhHD+IABcixIdQSBJuodr7YguNXS0UwA9EwP9vILpjiGVDyhOwyA7pwRJDw
AfxhKGSlcRxQAR2wCvMADpfAFkQgDu7wDrPwA1uTAuQYJ1N4jmvGbXLiGSAABAk5D2nwhSQlhhE5
jw9Rj+JXiBaXIWtSHeiRAjNwBl0gLJ9DLrrzA4bADcsUBmgCh0aBmGRYiIOCiPAADCHAGn2QkH82
BtfVHyUyGHAxiSVZECeZkla4kgTYkttWF+cxBLpED8gQMq1BCQHEDnqwAYEhERlwAiwQB+zQbJOw
Aad5VQiylLNZEL9ID8H+yAFuYgjg4D2A8COAoXadESMkgAIcYAejxA5eABz9YR98uRZRsFZWMDGg
0D7sAAaaRGh2aY7TdJuM0SJysiFGMEfzIAeCCReEmZiGCYsPqYaYg4+YUicMoB8J0RgpEJUQYxfs
QjpFEE04xgMMUpdFAZr3+IIloAg+FAwk4AAZ0AHe2GzNAAU6gmr0MhmxSZKV2H//Rx26sYm6yY8z
IxA6IA0C9ApjU2s5IA7TpAsw8gBFQKLbBhgT8APAAD3TkAOe0QAkkCPWuYJOORk82AFUcA7tMw01
cJTwciBeeD89gAsChAofQFs7cARxEQIGsiE9sAkWVQqv2QFdAD/fUAr+jxJhAEqF/zlrVxgYZ0CM
8+AFCRqPhXmdBWGihViAgJECvHcs1HYAbtI6/fEDElAELBBxxkMJLEAtm1qiD1qYbLh7mjA/u4Ae
F5BkpNBSuqAEG4Ae8/SUOUoPlPgQtdmjuJmCQVodc5ECH7ABb5BC7yAIQYCeQaAH67kH1wgilscQ
Aooce8Bu72AHFpMeX9qUwPiUjhECO8Cn5UAPaaAd76IgWLRlX5BC8xAGtbQnzwEYvwIFTDoPVeCP
uVgCP1Y/XPCEKumf2maFtCYjHwAEqDA/2PAh8LigodmgG9iqDMqGrUE65hZ//IUibyEBurMnRaCL
Z3AN9PANvkADcCL+VA4Jfq6Kj0VwAOG3Cy3ikSAgBLvgQ++gCVbgASjQqzg6ksBKqQIxrJmYHgLI
kmTFj3bRAC/ABcjAP9NABQoiARQ4P9lgBBNwjXgIEU/yA0jCAuuQVKBQIstCGeP6ENkZjNxWAl/A
hPIACzmwe3TRJUIiEEFQCsxGCx1wAJsxGyVVAXF1evKgC49iF0OQAWegDvAADpvgsYeKl2umGzRS
AyxwA5SQlvQQCCSwLGBIsWVotIGHsRXLhoPCIzGZA4DAj0/SGFEKgBywA9szk/GADV5wVdnxshCZ
sRJqf/BzC8ICbPkBBcqQPuwACEM3kQBItMHqEEh7sLQCpE17ELX+xwB0MAzqBAl1wwAn8AO3IEC4
ADIu8gAS9RAi8AAmQgO70D66gCGA0gFr6xBt66vs8SKpwGzzwAWiihcgEhkvUARUwEzw4AfakWoY
kqHlga431gbwRgI9YH5BEAzMlg1EQGtrdpeJqrD8MQVsYAnSMA/TcwpAMHcTK4+kexyme6KVMS2H
sgbaYIWs0wFG4Hhr0Vw/gAvfQA/ocAYlkAEogIO8K48aK7+jtAtb1hsnAAJWgA3opAfW8SSfSAI1
25MJEb0AOr3TJA+QQAmSwAiZMAmZ8AiUEAmZkAiWYAmPgAvUAEjzAApGZxshMEr0kAmeURvd8RA8
0pES4AGbAD/+43BVgKEd89sQ9TsZoJG6aQA984AJM6A7RiJnIaAJFiUNB6EXIDJOBUUPwDAFPZCv
V7UG86OWISACH1AncKMevoGodExIroy8i4AkRfCQ+voD3sigKSx6MOtxOyxNnBs/9LA/ELFAE4AJ
ARQ+JwC4epLLOWGpYJgdiIrEQHIXFTADdjBs8ZANYeAxrME1NUu6WJzBSnt/4PA93nVBTzVA8fMN
PhQP7HANe0AvvkECP6BOikAuc7KqCdGlmzEDnfCNuwdvhMyLTMm2YaodgkICToAMAUQNSdAd2qEd
DHAFNxYIl/wo7JIDU0kPVcIjKBAlHCAE0fBU2CAu1NEfqqz+wa0cRvLDPlfGxVUQAiUUqUXACZMq
EYj5PfpkgeXsP8EEEQ3AAScwBuUQSGhwAleJwUnhzEUczXAxGDfKATpgCPHAUtKwBJ5xL96cPrcQ
EeFcjlosQMm0xdNkgT7EbOBQDs6QCofwAj+ySe9Cx4xALkqbXkYXGbc8D4nbGoXMEIdMZKrRAX6A
Pu8wCXiocWpySpHAbNhwBZc8A/20A4SQPtHQBB7AI+3xJCiwA4vAP+CACJJxL8y4uwirC6Z92qYd
DJYVDKzwC8+QDerADvuTDXmwAxUwkfO8Ayg4ujiNsd1QC7iwC7qwC8TdC8RNWcjwRGBbg69gUY8Q
Agcw2k3+wdT4uBZOrTcxc9nMQwnF8w7KsAMalzQ169U8mrRaPA/lkAdyYAdtkAZtEAdykAbunQfT
0EOfwAKaJI6xIyN2AQT0CscS5WES8QF6MRinx3I9IBC9QbQpWND0e9DZoYs/oAQo2w7RoAQh0h+3
YQTS0GyawJ9BMAO7ZwTRNA+Z4Cp10RuIEQEd8AzMNg1GECFd2oarvFbWceM3niGG8iUlYAWT0Fm7
NAhhKKCssQOIiMu9vcvkoKUw0gE80AFAAAQ/0ADy0gXPABEiQgT8Mw48gCytUYBKQd04asTAeiAp
sAGA8SNasgqDhAoKYxcpULMxxxBfXakruT9ytVwkUIP+cnLmjFC26RAGYvkDK5AigAEEFDwPu7AB
+/G2DpECbxQXG6AL9OAOyZDgZtjXC/HXHcmlStcI+qsHg6JxGGIIf2kF+qwgFTB49CANTiCqM2Af
z+EXxBnMjvi6GwIiNT5NgJMX0GVuCjMDSaAMT6UOZ5C6eyK6QJLkvTsPK5Akme0lKOAAJVUG6QUC
eYA+rrAjbegUYg7NRwwXKN0BFeAuzNEDx8tynbADEIAck0jel0is42yBIKIgyDgEhRICAkALX2QL
NKAmbrh7zOMJ6TMONwBvHemSC+GenJID1JA+oFB69q7pCsHplHIpHfAE61qRsIbYO2AM7TAPpVA1
6Nj+AVwZSLqgBnSQBnYAB21QB3LQBnLABndACN5gPM3wAu5KLtS26/MAOAEFLYk8AxLwAGcgg/SA
C7GeHGF45BWby6DJA40BGgrjinFBAhoQAkgAETDCCAIkCOlBa3IyxDE75tctKOpxAoVCAkvQDKME
W2jjvPCOkvIe1vKAIiiTILoDGBvSAWegv5QAGUxgceLCPHWwVoAQ1AZIIUHSAH7AyHWgFmE4hQSd
wn8N51CyMCFgCqMUD2CQ7x2wBuijDmNgsQq+jkCnDikURvOADugQRd/wDeWzBsoTiaTNyn7iJwfx
jwzyA66wQfQwBAigLGqi2zd9hqYrV/1xHQ+kMDP+I/z0SASPEEB2sHcYrIdhvsKXSubSnB65LoT6
MQbi0A04hgUo8s07Gu/m/aMWyDUlQAEckB9F0x66SAqynQ1OABv8MTMgYJZEIIoAQQ/XDhBFPFQo
kVDhQoYlSIQIgSIILnr0rNloIAHEjoSTKtIrsaNDQ5IL23zsEIJEhwkgUnAI8WFCCDLs6L0rxWJG
hx3C5sHb1aDED5IdDnRARU9eRXAfnSoF5w6eOXrz6MES0COFw5Eluk6yOq8kRLIcOAQJ8gPFDkFW
6bE5McEriR2PPqr0WlKv1yAj7VZtIKJEiIQkSmxtUCQEh617GQahc60iLCl9E45MAdHxZs6dPev+
HSm0xF96DQxP6ArxkdVdHUCUfJnZzDpw8shp+VHJ6i+inuV8rNNVbwgJChVVjKewQ/GSRCSDizWB
xAQGg0Ok8DBkETx47PSwSMETNdkQHYoUSUmWJd8dd9iBgzeoSQP6CVOApQePRwa65Tv8J4sEEDSb
QS462unuhRQ+YK6hDoQpB5x2lNghAzLoMWeePcILgjC5yjssgy+4m8eTRip5JEUVU1QkkkkaiQQX
7ugBo4aVzBupg/AQ+UgvDg4zq4QfFXLjp3noACC9lRqBJz8WfgBBAhRKIgGFFEgggTniQupgkne6
K+E1nkAwjKSHejjsgyD0+iERTh655JFDPvj+rE4779zMsh8p+SiIKQfzirHV6LlFyJJYcukFRNSB
R55khFBkHnlsEa2z3/Jzg6jqSGqAsBRSCCKTj4oQcjm9gthjHnPimcM+xRDtIApx8ssmBw/i+oEl
CSQA0L9dUfthAgo8WCKbRrGJIoHMREuhkJ/aYcMEEmbAMksJ5Bpsq5g66JCRirAJAtuSgvDjJ3oa
8aAEU+hxRxkWButwggk4yJEBClLJDxcYgoBgB3//9TeIGRoAYIIwxqnIFBYOCK+BcHUswqOKAAa4
iIrPC8IDLPOYpyk2JghPpQ6Om+edNTtAiOJ/0eLpvB1yJSEIUiWeRzGv3g1J5R1iJuKBCor+aOC1
kkAOFjM8j0b6zv+CoPcveYIAYSTCuhq00DIbWnPAD4QAhR143olFk3jgGWZNz06qqI0fGuOUsME6
4CQepQItYqVDd6CInmuegGhpuUC4wA9ymmTmCQ5IyGyxEoZIPIUhhCSrpRqYkQcedPjoVLMSLghh
DHSqOiTLxa7G7IdwNQIVglcaDaqEefXaQRrupAFiC5vAQSSE1zq8TC7GnEhHHnbq+OADMqtFPoQJ
PDhio1k+X4cLAYtAzav/7HKHHuSRb7CEXSV4XAQSPGGXnilSSmmlTOApuQgOXvtge/kNIyuIFBhg
oEtzd2jggRQKZMD8HtIXCTxkCFdjiI7+DicBBuQqaQ+E4F5SEhtH9ChqJSBVQjiQCasEowFDwhpE
GBAeGIyiIuggh1J0AULOnGQpbfgP2xoyNdWgJDykEg5DUHACK6jDHeDoxM5KILP1DKYUjdJbGHZg
FhSQYEjy0mCVOMAAFoTBGfKQhztcoSOIVCoFQsiG3Gj3AbdZ7z9D0ZVhEICFwcEDER3K4ULQxyf2
RYIUTbGGEkKAgSN0AHHcEhIIOECJecRjGA14yQnGNQMGgAAELMDDT76RCt2xhDCL6QBpPBMEDQzB
A0/IBhaV0QAd/Ycuj2DfOzpwuBOU0UeEacALrnOYSHFHKwKa4F4OlwINtORQitFAZvL+EkFiFlOE
HCgCaSCWGMPoSBNWGUYKhNaQBkDJeyVgwBN6QY+mLEUXR/jMb5aSqVUOxyspKMJxKkJEo5GkgF1q
kjrOMMIJVDNcE0DBBlaRH3rEgxJXmMEMdAcirwx0iFeARDzk0RRT7OBPXalOeDoxtniYIgovsB46
tyKvl/BKB2jQBTjAMY0ckNKVDOHABJ4wq3kUY1b0uIQfL2OYDWStCE8IB/v0MBLqHSpYgtyBC3bR
JHYowX28K08yKyIWkmRmQJ/qAOdCkIRVgMMc3yiE2fpCgiI0oirz0F1cTqoQzZBlcWcIUibDsgHi
RI2FDBnh+zBAAzZMkyEn8AALukD+ByJYQJHFBOwDdRRADpDmg0BzX0H/cgtpHgpbjDkCCbigjCY1
aRh08kwaKgIPN4SgbnoR01YiVZHX5UgviONBNPKjC0aCgAEhyFUILnCCHayLHt34hjhWoYYcvMx1
cvnBDnKgBlFgYx7dqIgrdnCCCywEW/95QjP4OY5M5IAIAwPQGXdgBDKcIoXgyEYjGvDaInTPuV6x
LTxqow4rSDMIneJAYjigghDMYBLcUYYSRuJA2HivODvYw1LmQQkWfOiMo3lHRX6wYAYvmCc/KEJf
RhIFQFxDUvQARgWYVh0d/eA48ShHDgT2pAaXWGCIZAkbYvG499rFNkswwgoctoP+GZSYwUYAQgN2
wAM/pKIGJfFAEGqRDXYUQ4+BRfLRdJQQBnSiSe6Ywmkw6RVNVKQY0ilJT9HHLRRcKMFAMZulKhsc
x0zNdaD40jyQUB0c9hcmdpAbOxhhA5EByDAMKMIdsuGWecwjHcMoBSUiEQlKlGIY6egzctJhhxkc
ZiE/KkJjNDCGZEgKHPNYhzSAIQpNTGLQnHBFMBAtN3qUYxK+3EGYsSYkPbyjck06Bj5J0AAjwGQC
RzgcB7IQDXjEwxHEyd8RyEOeG0UEJiWgRkXEkYWWnEwCDfBEgumxC2pXm9q3QEYwbsEKViRjGohm
3zyS8YQMrDJm5WnAJr7xDnD+4KLat7B2vG+h7V3cohjq0EUCEpLueMQDHLOgti52oQt4x5vatji4
L9RBDJzNMAzqOKEgMphkinsGPQ4pweq4I4a/XoclQ4gFd7BBhL2EgAETQE9aRsCDZXxDodmYwme2
w51CkAqBDCkjyGckBoVIQIYLKU8BZ6CMpmQjDDoyDEISooIMpMAGkGjjUp9SFabAox2UsEGYMPhB
xvStOoz5ZCu4OfX8NOkjIqUHNf7QAsAFgQW8I0kPJBACPiRYUvBQxg/4M4P4wfIEBzgCKMKyUxQg
8yxoQTxahhiEHoQAAbJVRsfiQQokXCshExiCxsm+ebdMZRyUEEIPVrKVM9r+ABdWufRHzE52iCtl
KfAIxgyKoIEghJybXqvI6zffFKqTrTcNIUEavPa1RsSx4scfzgcKQAx0FPId4wBEAKTZgRnAQBqF
jMc7sgGGTQ7AFD/hDjvSgYUTRNQ/97OOAgiwiXiAXx2kyMpY5PIBGSDjJ++YxzgCIYAfaIxK5SmA
TZiHb6CHb0gHT3ACmLArhgAEV5iGAcQ/pciPS5uGVwiEz+iKYJGCSqCFPuuzd5A2c6iceZAGV7gD
VduMEIiBQBiHjsE/9kEGGaCTmVCeEqA/+/ua/Nu//rs5haieB7DBG+hAq2CfZzADHkCLAog81Nu8
1UMOb8AFUBCEKMicoXj+iRDYgAJghs/ZPLJbCtejB28AB1oYGBtwhj7jwi6cum8opJsIBiAoCRAQ
AmX4lipAvjvcjNkjghUAAh5wASN4FxUYogawgCFItSBggBrYlM7goxnYgB5ItRSIi8s4o5fwCgiD
gBgwgh1jASEoAgb4E6zZlRSwACR4gRbggU7cATIqAQooCV7ZoxAAAhbwQyEQiU9xnZL4gB2wgS2w
A0aYhElQhEYoBDmwAhtIic+4pxpTExq4AS64g0KYBE7IhEeYBD9wAzDIgQLpwb3IgAzgACFQxR9o
gRdAAgtIgV1Bi1EsxVNMRVtkRVckiQ5xmx9AACeYgLTQgQY4AQNAASn+0QBTfJn0GLbySBzYigka
oIEOcYnLyAifswAjcIGCpMj6aQAImIH3moI90AVP/KS0UIyKpEgdkBkgwAFFkAVxYYgMmAAoQARG
4IIaaC48pEk5kpdVOpyH8ADGwJ8i+IEh4IDe+AEOqAGO6AxFMo+UiyrlSA3l8CwLEIEL+JQfqQAg
JAkRcogDYIwm2pTiUEm40iAOuAAS+AAPuA4sESaSQAEUECTzuAwMwsm1/Az++hSfHBA5WgyzwMkr
+YwHOAEncgm05IADuDPyqA4S0MoU4MqE8MpDmSDG+IH48Qr0IJUg8DmIOBwU4A8Bkp/w8CMREIz/
wJbDhAnONM0qQQH+BqiAQWgACrhCEBCf00QezfzGD3iCQfhKhUjHEEALBunGmkS++0mJHxAKCnAA
xLkOUAmYZEwJFCw5iJiA4ggPpryMH9mUDvgBt5GXfDSC32OIB3gchxmJufPM/7CZpjowRztOIWGM
n1uIAFII0QARxBumzgCRaimBCvgV3byO19iKNakUznAwhigObhGKIXgA8CwB8fQej/sP8xirhFC8
KxmSSKuO/AmCVMPOVBuYzkhPEojKB+WwtDSvMrsMzxqJDtGIEjCCDoiBz2iA6KyAFKipCC0BgfKe
6uBN4OTRFBVNP/mRpRmimUDNY/sMucgSAeEAn3tQTjnRzLgAKzH+LfTsgB5gMNgSCW5p0qL4FADd
gYgozw44uSxDN+UojBvBRc/wEPtYDPWQI+zMTthyTgkaCSyxEohgsB6IIc+00gXD0qXZUmpiTFx8
AIhwCRBoosbwj5EYggd1VByBmOwii+k8jBQQTwijl0fVVEfNRUp0uwKR0A9Aj00lVaK4QlMZF6C5
jODiUeAcEmkSkHrKRwChngibAAhAudzcix04j4QoDzjqihhKCFJZxE79kbScITYjDFBsIof4kQZ4
HB/5kfdBjHw8D2TVi4M0VKGBIs+QoWp5UPIAAdNxHQmACRuFjan0wdQcDGLFSpthVsNwogWN1qtU
VMIIKKE4mRD+SIypwdYE2lSWCQ3dHKJDnFPH0FT0eCJDwcDX0AzjKwzGsI8gaVU8RB+YMIuoSQnF
AKH80YwSRVgmQ7kcEQ4AsUSFmKLstJheybKwzBJYxRIgKdY3/RRpgsyy8Lix0B1BGpIzetAF+wzL
sx6V9KMyWROzAFcM3NBRXZsCotheZc+XPR7DeImZfTQfJajLw5YMZQmUKw/TzMmYRdHLaBgNOkjZ
3B74xCbD2KUJIlK0xRL0Cai0gFhHG5If+c2KDaxZ6guB6Qv3CaAymZL0tNq9cCJQyc4pxYxJ1aDk
nNclU1sH0SD08BdyPVEb7YtccZiAWoiYBY3CkFDh8Fxdzdauh+ibOHLU+1zVzygToUA6fzGPnu0K
ZOKJlwmz9CgJiRXPcMGSm0UPFBjL3g1SUi3ZOnWiBw2P7HQIJ2om4tXUxjHPX3UwoEEN533UFIAA
ug0T96REEOkpvQXf8BXf8SXf8jXf80Xf9FXf9WXf9nXf94Xf+JXf+aXf+rXf+8Xf/NXf/eXf/vXf
/wXgABbgASbgAjbgA0bgBFbgBWbgBnbgB4bgCJbgCabgCrZgmgwIACH5BABkAOkALAAAAADCAT0A
hy8vPyUwPxAvTx8vQB8vTxAvUBAvXx8gUB8vUB8vXx8wTx8wUB8wXx8/UB8/Xx8vYB8wYB81aiAv
QCAvTyAvUCAvXy8vUC8vXyAwQCAwTyA/Ty8wQC8wTy8/TyAwUCAwXyA/UCA/Xy8wUC8wXy8/UC8/
XzA/UDA/XyAvYCAvbyAwYCAwbyA/YCA/by8wYC8wby8/YC8/bzA/YDBAUDBAXzBPXz9AXz9PXzBA
YDBAbzBPYD9AYD9PYD9Pbz9PcEBIWEBAb0BPYEBPb09PcEBQYEBQb09Qb0hYaE9fb0BQcEBQf09Q
cE9fcE9ff1Bfb1BfcFBff1VlcFBgf19gf19vf2Bgf2Bvf1BfgE9ggFBggFBgj19ggF9vgF9vj2Bv
gGBvj2pqgG9vj29wgG9wj29/j29wkG9/kG9/n3B/kHh/mG9/oG+AkHCAn3CImH+AkH+An3+Pn3+Q
mHCAoH+PoHiKqH+PsH+Qr3+QsICPn4+Pn4+Qj4WQkICQn4+Qn4CAoICPoICPr4+PoI+Pr4CQoICQ
r4+QoI+Qr4+fqJCfr5+fr5CfsJCfv4+gv5+gqpCgsJ+gsJ+gv5iou6Wlv6CvsKCvv6+vsKiwv5Cg
yp+vwJ+wwKCvwKivyK+wwK+wz6+41LCwwLC/wLC/z7+/z7DAwLDAz7/Az7/Pz7DE2b/A0L/A37/P
0L/P37/P4MC/v8DAz8DPz8DA0MDA38DP0MDP38/P38/Q39DV2sDP4M/P4MDQ4M/Q4M/Q78/f4M/f
78/f8M/f/9DQ4NDf4NDf79/f4N/f79/g39/g4N/g79jo79Dg/9/g8N/g/9/v8N/v/+Dg7+To6+/v
7+Dg8ODv8ODv/+rg/+/v8O/v/+Dw/+D//+/w8O/w/+////Dv7/Dw7/D/7//w7///7/Dw8PDw//D/
8PD////w8P/w////8P///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAj+AD8IHEiwoMGDCBMqXMiwocOHECNKnEixosWL
GDNq3Mixo8ePIEOKHEmypMmTKFOqXMmypcuXMGPKnEmzps2bOHPq3Mmzp8+fQFsuCPFhQdCjSJMq
XVpyAQKBC4wy5YhA6tSrWLNq3cq1q9evIK2CHUu2rFmMT8+qXcuW7dO0bRtGxcngoIq4be+qrQoD
LkYGgOterUr0puCCevGqTXzWh5a+GgMfXmrUsUoXFT6MoOBBBIUNUR0sgEBAwwcPEzx8gAAhc0Kj
gBdE+JCBQ4YPIQyowKyZs2cPDBYouL2ggYfjyI+n/hBcNQUEKlgQ+FBBRIAEwytUWAD8A4IQsFX+
QFihooKHJVMMBVofCM2VEhRcgw+RlsHxqB44APCwgEGI4fwll1wGqsU2UFoVUMDBBvz5ByB3Ah5X
lGCArRaChKfdhppqrC1k1XcqUCDCbbmVx9wHIiwX4X1RzQVYZlEVUJdqRQmUlnGdpZXaijz+0Akh
FdoXAQMgZACChAQWVcJ0jBEUgQA0VIehXwKN8FRgKpg4whBf/CFIIIb84YUQF1SAwgOqZckdBcyx
mN9+/f1HIIQRUjDCZhPs8KNKCJTgQQbJkCMoOdvQUYADCMDgCzbkjENoGxgi9BQOCORwyTaDYrPG
hX3+Gaig5qBDDjqkCkrqqafKgoofS5BAgAf+KoSQwHcC/TIoOdbQAYIC/Xl3mnceBIGHKreiOmgt
jyzhwXSunVjUAraWKuqoqFaLDjCx/CFFBrd5d6EHJSyDqajTWlstOaisUkgRBALXHGYeJMOoo9tA
SqOkH7BQ6aWZbgouf8lgaqq51VbjSiWG3JABdHdNVxALHwhDbbkEE2wNOXgU+AEFFkg8TqnjbNOJ
jfQlpMAMvZCjjaDNKAFDQQtkUAJcGQjRRykrDzytoLLAccRxaQ1V4bPRkqszwbeqTI4eKt0HAgej
kHMOOVLw1599r5xzjjhWeEABmwoF9tQeH4/jRbdOQy31N6RqHeo5FYeKTildo2DUt6ehgs7+ON5Y
MYECIEQVAgMwEJBBEJSMo/U5H4uqOOOLO6qMIUFMkEMPHkDMpn16fwM3OotXfKo4tVhBwF0eXEiA
CKSQ43nbWou+N6moTNEtQcdlvXXXnDkEHdl7n21jcBqAonXj5sqtvKOweEHBXWJV5d0JooD+uezm
kgMHgU+FKAIs1fJCYAL5igUzARyUQqo2JnhHpVUU2EBJo8ebqzU44HgzCxfcgkBAf5prU+c+FzqC
jUNxBxwV01ICmBggwAOFkBo5TIAAGjAgAfbJg9wsgALyIMQpzEFAhapwqvi8AAUNfGAE4VYKVKhC
FrBARSlMQcMa0hBVU5tD76qiGg8MglT+4uBABTAIAQ+kBYLiMNYxUFGIPxRiEI+QhTRMBbePWSIX
/AuSffAAOnSIwoUthIUNbViNtomKDQMZCgFI0AepeRGMqBDjGGn4ilGVo1RuABoLLngaDZKKgx48
CAh9xZwtlLACJ1TBjAKBjjvOkYalKIUsInkMnYkjFCdw1oEEcgBFJJEcpFgFKh5JSlPQYhuI6Fb3
KDCIiaFDGj/wAAxUgMF7FWQFKBgBI8WRihHMBTxwMcoEDDEquI3qGKEoBB6aiAhUVINa3hCUMqyA
gTPgIDDM2WIXv6iKMJKyFN2UhSxqoY0+rOSCEPiAIUqVgV65hpHhIIcIGCDChEjPfTD+8AI6xEGO
EvSKOQlI5zrRoY0TPDADnAEBQjzQg0KUUVBkMCJ4PGCeQYRKni5gjgoU6gIKKIJa5NCFIYQwAerQ
UiDHEcIbOtG2aKriVQnQVy35ICptkIA/CohUQTxAgz9kY1TkGENmMKgCD3BRZTcVjk5x5wEjOPST
ZaARC1RgFHjKk56TKcg9EZAoffLTn3URj30CkUR0NKRPWVCENE41CxwQxC8qmIPUtNGBJD2EA4So
w8Z8ZR8+KM5x5ODFDBCwx+Ag5AFF5eLcbEmQ4MgAFRPzxUhTA7aBiGAJhpDYqcJxjFuoJqYImGlN
k5pTxhaEMwQoASEIoRICDI4BFPj+AzuZIxUG/AGoGXDQQuCCgCngtj8KcC1gYluqCdTyA1TlEQTq
YgRtiMoYqkGAQlnAyuJ+h1fOKcOoxFGNOdAgNSxIgCIVSb7THEdYOXvCBx5An7tIR7HkmE6FOLOi
kwZhreQYhkDEU9RClEq+daFvhFiTAAo8IRqgE0a3ZCSQ24oqt//Z7YF8+2DgHuc//iUVj8w7lGWp
5gSfOAc40NFWKtWIi3ArqXl5tKIc+CAzKnhgeWR7DlFwwlSUIMERERKbQihOFab11QmCcSpprGFJ
TyksBGiZljV+oRaj80JJ25svAsAXwBvjUZbqAh4c9KBp3soATR+sSKusU1AeWIH+fRgCMYF84b8M
MMCFwjxmcnAgBmumKo9n9AZqyUE1CvhAAnwIOnJoqEEJEAGC4/mEKRkoOIXxz8aCMA1NTEAFEYgK
LfvbxUtXaAQfZEBRx1DWPw+OuitEh6frAuqDxBQCg35Dqd6wOamcmRxpXvNC2vyBN4uKAHFW3X9a
qTWGlPdEGaAEuRJByIL4N1QXMNFD6MlrG32gEHCLhQh4UWhH0Mh8BMHgHEi1CnDnKwOioFYtaFAj
qMxlKIMTyKs4gIdRUaKkwTGKeCHYaUWy2kNQCfJITLQAEMD30hCQygJQbGftCHyTUiHh3tIEKxgZ
vFQigEABQFBPhNhVBNMg1SL+kCPoD/xwahmANXJFvQTQjWMQ92IAC5LzK/LVpS4T2EUQ+POABxbI
qIW+jcyzSpAkVccajcREBhQAGA/0IejM2WNCOKCxDDiXHIgAzn9Uw3AhmkfCESfVOChegZM6eBwf
hA1ssOkBvcFNC82Gio+nxp8GQEQ0hs1mXW5LjlR4oAbcmNYbjChwGq3zHKgQeL1JZQsTeCCdJzIK
chw2GQ8g4hqOFw+E2sRwoUt9oVY5dko05kNqAefbH5AtqWr08INwgVrtJn0rRTUCLHmgAZKRTEkV
CYLWIb6y9vmhhpHrrtLvMwj2WSrM0pQAGGSBPqSnUYbJ0aJf5T4wafqAAoj+dQ5S3G4BfzBm9Qt0
fdhOiAHfQ4c5ZCFfgdj2VKyHyOtXL5a9dxEiQxFID65BqlAQKPnMAQGEcCoiIHk8cjcPFDYfAAig
k3gMsAQhBzdPIEJUokXChwonggAZ9QETEASBRw65QAMeIHoPcQd1UDK9giHTxysVQlVEIRXkJxDk
k4CjdyLGhw6nBxWpB3+SJ3+wB4M2OHvoYAGDhlLmdhoIsFwZoAq0IwLudxrCh4PENyM/FA7okFvl
5RQQAheo9wECwB8DMSPSVyoB8isLlU1LSCqkYEvTV4YPNwLukjekUgoa02A8aIYOMX9mVX87CDf4
NxCW10jiYAQLUG0MQAj+cJMNJPBPBlFeD0QfJBiGC9iAp0cGXRQNUPABkGEQgHGBtLVfp0EJcKMN
TPAqEyEASFgU3aGCpRI4AZZGb0V0KyF7pqdrRqF6e4iHDaGHsReE1OKEquEaPDI4d5EBxxAqmkAj
VHgqFCdqHgAHpGINRoBcT/gsCKEAIXAkViGGAuFfcEMjKlBSGwYdH9ABxEAqyfiE2PaN+yWOK9I7
e0QAzPAxlDAzBIGL8fcQvMiHNGZWDwEe8lYE1AIHrsWFeGBM7SSLH9AC5AMet3MQdcGAiHd6BOAG
QAUMJ0AB+mIjLsIAnugdVlIUPKANW9MJDkMRgxR93dhFtxFjA+Ea2oH+OhOySTVIhbWIevjYg/r4
gyjli6LCJv0hjCsiaqdhBKeCBgUiebjYjEXFBORghf7XWHPRcYKRAIPDiDY4huyoJskXIRVCAE5w
KmYQg3/wV2lCVV0pIPtFPkjgRkgJF+9Hf7rIEPvYWH3ojw9hFROgC/s0C9H1c2VpDuTgfjyCWHOh
gxA5iRMpcxx4Y6TiCqrhFIbokbTTJqBoiVOzBNR4hPb0VsfBjdfWacjlb25yHxlwkloIZjapYba4
g3LZegZRl9YHhUBFAYZ1FwopXghgA1CGDtXAA08xFx4wgMNXVIKRAaEAOtswCTjgYQMRK1pUF+J1
UpLIioICbKK2AA7+wGMwICK1MCrQoAPBaX/XCRhUtZ0QmSXxA2XeMA3AOSNFkZNzuRCy+YT9CBHN
AR0T8AizlRgIQJzk8BwK4QEgQAdMl1M8ppgOWCETIAtlpQl2BYCdWJkCsTkeoGznoA1sgkHtBhFc
ZZesKCqw4m5EuXLiBQfKOEg1SZusiZN3CJsFIZu0KKILoAE0dxBLEga6sA0EVQiBRlWSR5xSaJzB
GQXOdUDNEAp/MAZQ0AMpwi1Qihy8kRirOIbosA1+chzttFAT8AWzMC198KO9onpYihxbKkgLIAJT
wJek8gdxKCHyCaMEUZ8ncp/4VyAhIGtTw26SOG77lCI3tSIjQgX+21B8CSqRDhhep2ECRCYqbrCl
tJJNnhhzGTALoUKH/vkX5rWSBHVTE2AkpTV5JZAFNoVBBccSM4qDrRmnPiiXs3mDhjAIccAHeNAH
TlQIuJqrhcAJCLY+3gYrQAqFzDiFRFEACPAGSDc6ILUzxzALs/AJhYAGRXAcQJmVnEoOhoAHeBAI
fUAIuqqroNCboqIJ/+NuH8BIopKt29qt36qrnEAMoxJPirCIUndhrLqTrmqf9/cQRaUxXiBBUhCG
TmEIjbMy/JQ0pjIoFKVniYmowPEdkicE07BdaNAtazah6ICBZmgfV1cIbPJAnMkQ27ipoTmKIIWw
jSIoE1ABLdD+HM1yEqmagzVyr3nIk686e+AgmN6APY1zDsYgBqPxWQA5icV5egvQAiESBJYgNYvT
tAV0KoKCClxAfqCZYeQCtQQTO1bYBwTQAp+lilbrSq5kPz4rBqiRTb8Cfi/aqrkoiXbqEOSjGmr2
elPDBXYZfufQDWZUMeewDUKXEBFJiTNSiPbxBNIAN9PQBLDhfpSZsRWKhuRQDuTgsUVxJBFhFOZT
tdYDO6QiN6gimC3JHdSoEhVygzJrFASbrw9hSN8IhKsJDvy0s9ICVNQyNboQCX/GiP9EaEULgICI
A25ACRKzrDikNfGKDolAdYpEsv5VDlszttmzDbMAB0VwNZr+67z8dC5XK2KiMguZwAZ1aBCp27YQ
wbo4yI/7Cre/MrcS5AVw+QGCcA53FAqrcApfhAr4m79xNLHcwpmBu5g1grkwoAZiFwwnQJqqoXqo
EGibwwAZELnogAdXI7oQkRkQq4zMiw6eEwqzQAqp0EL6qyqyMLED0CAvsZqqipONMyGV1RBvdkdg
+HWraQ5hsAVUQAVTYAVeMAVTcMNiEA1SgwcMIhAimEaCwbtD2h2Yq4p00hlBMAVe4AVbUAZO9AeQ
cAs68wino7n79AU3nMNbwAViPMZiLAG2QXKla6Xi4MU4bAVhvAVTwAVb4AUIZg59gAHUqkkFUZb0
Z34P8cL+50sd+uqH/CohdfGvoiIFRLE5Jgc30GAC7bIiHCABNtAMqUWODSu4HeqFMBBBoqIL96JC
6BAOs6BQyugBzmUOj9AdFqGiXGwNS0IAFBDJAoIDy3ACYKiQJoHCp+uauIaVDWG+YHizQFUBRCIQ
GcCh8tZnH/MEGVVUBLG7UdiMT/gW+ZJNJgaIH1AEkDAqjuIF1hqaP0kjrIwQopeCVhqg5EyUREkA
cDAq5jCNWyZwqvfLuowQwoy+hJyXeCprokIDRlFrg/A5E7Bq12cjWdA9KHCommwQMTM/pEIJ3LNH
ipV4lGqpJLbFJOsQDZJkUcHFuCZzDyBoFCKDHyAFAHb+zyZhuq05gHBDASGLz6bnuiwaoODBzqyx
ZBxILF70PNYIFUc8zVM4EAXwMuTTIvmGVU/4gn1CbOhACVW6kvEUaNnpAOUnalmCtuHsX1OtUdpJ
W/mXAaRwR35pqgLn0ugA0xKxBTN9t+nbEPkZjvxJUBwnsAQbT5911TfXPaPLiQqqxAfhAcIgDnDj
sTDAAAUwCB+jsXtlH8r2p9Soaw6haUYtNBk8Nbyik4zrfmyyvHWRzSMRs6vKjAENEV8gQb24mrjm
hT2ZGCHyBCn7B8IVzUE9rMZZch9wkiRHwcmBHyFASyBQC1pzDFFdslIoXkx3gFcjgxzKiuyI3Pah
OpL+1wTg4CgwVxcnucekvVd/jNr6jJeTPRB7SSp+CYsLIHyrXUQrkk0TpXxP6LCC4Re9cgK0MMri
8AdP4QDElgqWSY2YiQ5o8Dwy+Y9GgQCugc4riXJgWKUkRyNcVRcxDRKijXqEgNoFwN0OwdauOqMB
ul8LvWLUMQITAAmMIw0zYMJAjVJCbZwz+C8Q4TU2MtDdENIZTCpOmCUjehBHQnJPGKLocONFVR4S
kiUuQACN8DHZ0D6g/QEVPjUfcOEtzBAaTr51+tYMMbQEIJCk8gYEUG0hEH4i2tcw4x8QMmeZDMDW
FobdabikgomuBY0ZG10huQAjSSq0oGNNd6c40Jz+kXm9UvgBKGBaL2uXLDEjVtvLNCYOMhDhBnHa
opLaLIoOI3AXDzDSM2KKAlECw0Aqn7CyziLNts3KOWUH2Q2RJR3kKmAI4eDkIA2G5NMkadRDPbTV
ZKhvyJVR+XdSHTCP6MAJsBKJdrg1iy4Rjj6Y3/2HKIUIgkiIh5HAxvS1H2TNS/6/DihCEP4sRnQa
bZlE0WADBDAISSQKwCEVqPPYEVwCzYGfH5AFu8ABKsbFOPjqy13S+WY1Jv0RKj0jA5XCOthnpJIE
8QYR4xYOzpAWvcPLxVEXCqAAIx04yz0G2xUGAaVwtd275kUIjACGCtcitUUhDrwaLHUOyoDg4mz+
aJZLH1dtIsJI8tNnJKpRMtrXAILDdGXQRVugEP6ODgCv0gYx8AX/uFW+z3JRGPtHKrAgAbJCsusU
KhOgUBzP8QYB834N396RVamj8G7QRbqAA7IlDrOQW96xgR14KtZQBAE/bR7A1pRAdbTet68V80MB
9S0iIYyOfyqgAAGQCTQAeazHH8o7aHqDDr6gUwvgBNTiBsxh1QbS3v1xUuRTCaICC6kRHAR3cQ/W
k5tMECjAClJzDNd0xEcskYamciqwAh8wA81QCzPAACswJRGyxB+wAhUQBF0E1ZunTXAjAgjQAEcC
6wpx+0CX+7vf+zwm1o00DBaEmBekAoZPKoj+zwCKb1iML2rk8/iRP/kLUHbkc3agh7lDZ9WAfypw
9z5z98t2N20ggIqCUXYegK4LOjSS+NkkUAiYsg2gEAiYAmQI4cnnAA1O8HgAoeLDhwQDF3jwsOAD
A4YDPVCphg4dnwUQDnpY6AEPunPkMixkwWDgSJIfPCAgOJBCSZYtXX5QkSADkW00MCJQGGIBgxAJ
EggkQo4jJoQjFywQcY3cOWAUKjAoOBLhiAU6FSLkUY0cOTweVDA4+AFBiAx8JJIT8SHs2Jc3pJ3b
VoiAw4EiPRDi6NFkwgoeKG1Dp23ORwYqvvJECdZq1Q8ngp07h86LWoU/PRTiiG7lBwUeWLz+bHmU
oIrLmTd3/tyyYBFp5tD9UVBBoMiRSZc2XRjVoQeqVvdm3dr160ECIRQMWnoONEsGCEhQCjcOXSKx
LTG7vqCiwvKSKgSEKIzAw1MCfSSiykBjIW2SIhPAyEDCUeZn6KqJutCSxYRUEtFZ4wIhxhpaaDQV
WCBggUKEOqsMykYrLbIJDvtgBJcKMkylErjjcKCvMniEnFqsKKoyCApTAQEaavEvC4yMCuGDP5ZC
RxIgLnCBJIEWusqDAYjIRaJpbGrOg+IYouAP/ya4yCCXQMigEG3GIeeJ7RKSCi90yJlgLAUOmkIo
cCQy5owSVjrsqwwdIsAJXWicxIMEQkD+QCAEN5LIqQ9CwLLDPev84E7/9ORToZYE8kBJdMR5YqAE
elRoxsgkiQFHHevq8ccg0RnSgyIRMg4ziRAildSjEkKIAIxO4AQydG7ZAaWSFNpIwt1KxRVXFDxo
AgHdIPAAOXJU8cAAl8CCIQHxCKABGHEkKgedWFBoCaUT3jxLERwwUogBFhIQSaAJJhhjF3TCWRQY
NxaZgE47CcCTnLkaoiBXhAz7Si0PitjRzwsFokEa/1g5g4YJNpQNoTGG4UgcWUooyqCedmBRImoC
2QHik+oyiYIMjOBkq8De8BTR3CD4wJCzONB3IBBcWsAFCqiRSJQRBJRqDtfQyrGwDHr+caQU/zpi
5hEvJqAABtlQ8mACEb7QZEuJgjnhAwgSYMFXBjwwqyMRXLDrxQ6x1prrvL4O26XtPpggmmdBqRc8
tRAoIYEdaPHv4owRktUuj0EWWRuSCzNJhRM9CORZdFxKcbcSsFBEG/9o2YE9WT2cYyltOshAbA4t
ECMUGARKzOxxSvEUZs9vpgEZdLg5Z5xQXmIABhJQ2XKraxRZYoKIPRAhAxPcgEXyyMRRJHgPMiAb
XLPJ0YaEhDrzvCSwUuXilH79ZSnFBQhh0D+HHynkjz8+EZijcHw5oUmRjmJhASKMEUeojqRBhZJB
8BhkkD84wcWzFEeOQnjKAHZhSAz+xLOgjrDsKAIxFEvA4wIvjEM6eOjcScQ1CImIg2XgsgjERACG
UmyDHOCInURm0Yk/GKIQeKCELIRywi1xYgeeYohIGKIRdICDHBi4SfW405AdbsSHQBSLEKWSkSj4
xxATOFJhsCY/+tmPHPjTH//8B0ABnqWADDhg4ewSCHREyxRnROMZUYEKWZRCFtLYCjmkI45O7KBA
JJHVARTxLHKQYhWoSGMgBWmK4pkiAygBzwsogCdUiABlLkldvyDABKGgSxVHyckC+oYSERjCeLlz
BioK4YZCBIITwWCQq47hBYzwBIfr4WFkRIEKVZQCFbAYpClK4UZVhKIW05AF917+8p4FeGIMaQCG
HCEjnchkZlHoCMWGOGaUq7BqK+OATDP9cxZ0jANdxSDDBEAClr0sAAQcGMVSyMGFD6gKJREsSQMQ
QAEJ2AIc45AGEjxQAkCRIBTdHIcXCKAAECygAN9SlgJ6wIiIiCl83exm7KQTDDKIbQGfWcnWcEcl
EiHgM5fjEEYzslFydPQz8CRJQviEgfqQYxpOyABhDFPNkCnTVdvkpjfRAU5xeoucCACLBkCxTJxu
0zXoOKo5qIQKL1SgAjjBo0IQcAJRcESbRcXqNoc1AQthhAIcgIVErNG+R9LOUWyrGDqkYQOxgHQg
dUqAB4IwCXJ4I3bdaKZ0pOb+n2oMgkg59NYHMuoB3H2jmdnMqlXPES2JtEKYkBwLaTygACY8whYi
06o1NEEFEiSGIVd5KwsEQgEe8EEVHcRpHLcxDU6IgQMYaRyW6La8ZGwFMNqgQ1hMArOBbCKOW2HE
hAryi22YkBzWoAMIvuSuBERghyc4Qyi0gdmzxJEZo0ADCQjwLdrQ5ii/mCE5riEHjOimQ95dAHhz
N97yvgQjBfBAJKxBDhNu4xILaZxHR1va0z5Tq7ZlrWthyzSFQGwByTDuQ/97Fme4ohJv4EEGCBCT
3ZbkM8IIH3UTm9phvegoGcCwHMnBjCOUlSVhaUgGQCEyKklDCTCY1QdgIID+jHhACIeoRRz/Cz1O
hEEE7xsJeNCrXqlpGKsPfZYrHtuSzUAAXwyggAt6sIU/BCIQhVhDgFI1TYV0y1FrWl4SuvCHQRCC
zIXwgheCANsUFAYFKqjXTlywnRHUSwQI2IAj1eKkljhZLBQQQfAy0K46ISADAZBJBrZzEAYoQCfK
osFcEJWBG1ghDX/Ig5UNsYUk1FkgX0nNUwR0EA4AwAIWEEF58+WnrSWE1KZGtapBQ7gJcIADCghA
51Dyzi/vKMxjLvOZ07xmmLRZBW+OMwO2IxIR+G4vuTLnqXbCAGotwAE7/Mieq/OBBiDkzgPxnb3E
zYFAnAImW7PaXjpHON7+qgUsDCmoSj6QI7e+dT1Q+UBfRrCFMlQ5EHzgAxVucC/DFaRp/KzxqUqd
EJ4ooHMXydWeE0KCOZh7yRfHeMZn/VgTL2dtGgd5yEU+cpKXvEMwUENqUGpylpe8y2qBgRxaPnOa
+wkCHX+JU2u+c5733Occ0mQOLrfynxe93QMRAA62Z3SmN93pT4d61DlUb6lXXdtWx3rWtb51rk+9
60Un+tfFPnayl53lohlIjMxOc3iGfe1vh3vc5T73s9Pd7nfHu9Wlyue8XzyCXXZ73wU/eMJnfNeF
F2bgEb94xjfe8Y+HfOQlP3nKV97yl8d85jW/ec533vOfB33oRT960pcU3vSnR33qVb961rfe9a+H
feyNHhAAOw==

------=_NextPart_000_0083_01BF5795.06C3C4A0
Content-Type: application/octet-stream;
	name="astrbul1e.gif"
Content-Transfer-Encoding: base64
Content-ID: <008001bf578c$a4ee93c0$0100007f@ftid33tp9h>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhDwAPAHcAACH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAY
AAAADG1zT1BNU09GRklDRTkuMALxmbSWACH/C01TT0ZGSUNFOS4wGAAAAAxjbVBQSkNtcDA3MTIC
AAAGkmNPuAAh+QQBAAAAACwAAAAADwAPAIHAwMAAM2YBAgMBAgMCG4SPqcvtHcIzMb5aIc5q7+R9
R8iN4eJplrMuBQA7

------=_NextPart_000_0083_01BF5795.06C3C4A0
Content-Type: application/octet-stream;
	name="strrulee.gif"
Content-Transfer-Encoding: base64
Content-ID: <008101bf578c$a4ee93c0$0100007f@ftid33tp9h>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhWAIKAHcAACH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAY
AAAADG1zT1BNU09GRklDRTkuMAQY+hGjACH/C01TT0ZGSUNFOS4wGAAAAAxjbVBQSkNtcDA3MTIC
AAAH5WR/LgAh+QQBAAAAACwAAAAAWAIKAILAwMDMzJkAM2YAAAABAgMBAgMBAgMBAgMCm4SPqcvt
D6OctNqLs968+w+G4kiW5omm6sq27gvH8kzX9o3n+s73/i8SCIfEovEoDCiXzKbzCY1Kp9Sq9YrN
arfcrvcLDovH5LL5jKYi1+y2m52Oy+f0uv2Oz+v3/PT7DxiY1EdYaHiImKi4yBgn+Ahp1DhJWWl5
iZmpGckJqfkJGio6SlraiQSUqrrK2ur6ChsrO0tba3uLC1MAADs=

------=_NextPart_000_0083_01BF5795.06C3C4A0--



From owner-ietf-outbound@ietf.org  Wed Jan  5 10:20:05 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07319
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 10:20:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id KAA08185;
	Wed, 5 Jan 2000 10:18:29 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07206
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 10:16:26 -0500 (EST)
Received: from embelia.wanadoo.fr (smtp-rt-7.wanadoo.fr [193.252.19.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06839
	for <ietf@ietf.org>; Wed, 5 Jan 2000 10:05:07 -0500 (EST)
Received: from antholoma.wanadoo.fr (193.252.19.153) by embelia.wanadoo.fr; 5 Jan 2000 16:05:00 +0100
Received: from ftid33tp9h (193.250.228.30) by antholoma.wanadoo.fr; 5 Jan 2000 16:03:03 +0100
Message-ID: <00c301bf578d$edfab8e0$0100007f@ftid33tp9h>
From: "adies" <adies@wanadoo.fr>
To: <jeff.hodges@oblix.com>, <jeff.hodges@kingsmountain.com>,
        <dkbrown@acs.ucalgary.ca>, <rlist@anon.lcs.mit.edu>,
        <kelsey@counterpane.com>, <jsyoung@jsyoung.com>,
        <jonkatz@slashdot.org>, <senator@mcconnell.senate.gov>,
        <cryptography@c2.net>, <jd@well.com>, <ietf@ietf.org>,
        <request@ai.mit.edu>, <saitar@nb.sympatico.ca>
Subject: jurisprudence
Date: Wed, 5 Jan 2000 15:53:36 +0100
MIME-Version: 1.0
Content-Type: multipart/related;
	boundary="----=_NextPart_000_0083_01BF5795.06C3C4A0";
	type="multipart/alternative"
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

This is a multi-part message in MIME format.

------=_NextPart_000_0083_01BF5795.06C3C4A0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0084_01BF5795.06C3C4A0"


------=_NextPart_001_0084_01BF5795.06C3C4A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Vous constatez r=E9guli=E8rement

    =20
    =20
      =20
    =20

Vous constatez r=E9guli=E8rement :


     qu'il est difficile de disposer de temps pour r=E9unir la =
documentation n=E9cessaire =E0 la constitution de vos dossiers ou =
simplement y acc=E9der.
    =20

     que l'acquisition et le maintien d'un fonds documentaire exhaustif =
et actualis=E9 repr=E9sente un investissement important
    =20

     que ces deux contraintes nuisent au d=E9veloppement de votre =
activit=E9
    =20

Accessible par Internet, fax ou courrier, ADI=E9S se propose de prendre =
en charge vos recherches documentaires de tout ordre dans des d=E9lais =
rapides, AVEC OU SANS ABONNEMENT, et vous permet ainsi lib=E9rer du =
temps pour vous consacrer =E0 l'essentiel de votre m=E9tier ou =E0 de =
nouveaux dossiers.

ADI=E9S s'adresse =E0 tous les secteurs d'activit=E9, dispose notamment =
d'un fonds documentaire actualis=E9 quotidiennement et constitu=E9 de =
1,2 million de r=E9f=E9rences juridiques et l=E9gislatives =
(jurisprudence, lois, d=E9crets, directives europ=E9ennes...) et fournit =
=E9galement un service de veille th=E9matique personnalis=E9.



=20

Agence de Documentation et d'Intelligence =C9conomique du Sud

Technopole HELIOPARC-B=E2timent Einstein

2, av. du Pdt.-P.Angot

64000 PAU

Tel : 05 59 14 71 11

Fax : 05 59 14 71 14

Website : http://www.vmgnet.com/adies

e-mail:adies@wanadoo.fr

=20


------=_NextPart_001_0084_01BF5795.06C3C4A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:v =3D "urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:dt =3D=20
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"><HEAD><TITLE>Vous constatez =
r=E9guli=E8rement</TITLE>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type><BASE=20
href=3D"file://C:\ADIES\mailing adies\">
<META content=3D"strtedge 010" name=3D"Microsoft Theme">
<META content=3DWord.Document name=3DProgId>
<META content=3D"Microsoft Word 9" name=3DGenerator>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"./mailing%20adies_fichiers/filelist.xml" rel=3DFile-List><LINK=20
href=3D"./mailing%20adies_fichiers/editdata.mso" =
rel=3DEdit-Time-Data><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:HyphenationZone>21</w:HyphenationZone>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>
<!--
 /* Font Definitions */
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:16792199 0 0 0 65791 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	color:black;}
a:link, span.MsoHyperlink
	{color:#660000;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:#003399;
	text-decoration:underline;
	text-underline:single;}
p
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	color:black;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</STYLE>

<SCRIPT language=3DJavaScript>
<!--
function MM_swapImgRestore() { //v2.0
  if (document.MM_swapImgData !=3D null)
    for (var i=3D0; i<(document.MM_swapImgData.length-1); i+=3D2)
      document.MM_swapImgData[i].src =3D document.MM_swapImgData[i+1];
}

function MM_preloadImages() { //v2.0
  if (document.images) {
    var imgFiles =3D MM_preloadImages.arguments;
    if (document.preloadArray=3D=3Dnull) document.preloadArray =3D new =
Array();
    var i =3D document.preloadArray.length;
    with (document) for (var j=3D0; j<imgFiles.length; j++) if =
(imgFiles[j].charAt(0)!=3D"#"){
      preloadArray[i] =3D new Image;
      preloadArray[i++].src =3D imgFiles[j];
  } }
}

function MM_swapImage() { //v2.0
  var i,j=3D0,objStr,obj,swapArray=3Dnew =
Array,oldArray=3Ddocument.MM_swapImgData;
  for (i=3D0; i < (MM_swapImage.arguments.length-2); i+=3D3) {
    objStr =3D MM_swapImage.arguments[(navigator.appName =3D=3D =
'Netscape')?i:i+1];
    if ((objStr.indexOf('document.layers[')=3D=3D0 && =
document.layers=3D=3Dnull) ||
        (objStr.indexOf('document.all[')   =3D=3D0 && document.all   =
=3D=3Dnull))
      objStr =3D =
'document'+objStr.substring(objStr.lastIndexOf('.'),objStr.length);
    obj =3D eval(objStr);
    if (obj !=3D null) {
      swapArray[j++] =3D obj;
      swapArray[j++] =3D (oldArray=3D=3Dnull || =
oldArray[j-1]!=3Dobj)?obj.src:oldArray[j];
      obj.src =3D MM_swapImage.arguments[i+2];
  } }
  document.MM_swapImgData =3D swapArray; //used for restore
}
//-->
</SCRIPT>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1027"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1"/>
 </o:shapelayout></xml><![endif]-->
<META content=3Dfr http-equiv=3DContent-Language>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR></HEAD>
<BODY aLink=3D#999933 bgColor=3Dwhite lang=3DFR link=3D#660000=20
onload=3D"MM_preloadImages('jurisrouge.jpg','#945434730600')"=20
style=3D"tab-interval: 35.4pt" vLink=3D#003399>
<DIV>&nbsp;</DIV><!--mstheme-->
<DIV class=3DSection1>
<TABLE border=3D0 cellPadding=3D0 height=3D78=20
style=3D"WIDTH: 55%; mso-cellspacing: 1.5pt; mso-padding-alt: 0cm 0cm =
0cm 0cm"=20
width=3D"55%">
  <TBODY>
  <TR>
    <TD=20
    style=3D"PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; =
PADDING-RIGHT: 0.75pt; PADDING-TOP: 0.75pt; WIDTH: 11%"=20
    width=3D"11%"><!--mstheme-->
      <P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: Arial"><A=20
      href=3D"http://www.vmgnet.com/adies"><!--mstheme--><SPAN=20
      style=3D"TEXT-DECORATION: none; text-underline: none"><IMG =
border=3D0=20
      height=3D89 id=3D_x0000_i1043=20
      src=3D"cid:007e01bf578c$a4ee93c0$0100007f@ftid33tp9h"=20
      width=3D89></SPAN></A></SPAN><o:p></o:p></P></TD><!--mstheme-->
    <TD rowSpan=3D2=20
    style=3D"PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; =
PADDING-RIGHT: 0.75pt; PADDING-TOP: 0.75pt; WIDTH: 89%"=20
    width=3D"89%"><!--mstheme-->
      <P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: Arial"><A=20
      href=3D"http://www.vmgnet.com/adies"><SPAN=20
      style=3D"TEXT-DECORATION: none; text-underline: none"><IMG =
border=3D0=20
      height=3D61 id=3D_x0000_i1040=20
      src=3D"cid:007f01bf578c$a4ee93c0$0100007f@ftid33tp9h"=20
      width=3D450></SPAN></A></SPAN></P></TD></TR><!--mstheme-->
  <TR>
    <TD=20
    style=3D"PADDING-BOTTOM: 0.75pt; PADDING-LEFT: 0.75pt; =
PADDING-RIGHT: 0.75pt; PADDING-TOP: 0.75pt">
      <P=20
      class=3DMsoNormal><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></P></TD></TR></TBODY></TA=
BLE>
<P><SPAN style=3D"FONT-FAMILY: Arial"><!--mstheme-->Vous constatez =
r=E9guli=E8rement=20
:<o:p></o:p></SPAN></P>
<TABLE border=3D0 cellPadding=3D0 cellSpacing=3D0=20
style=3D"WIDTH: 100%; mso-cellspacing: 0cm; mso-padding-alt: 0cm 0cm 0cm =
0cm"=20
width=3D"100%"><!--msthemelist-->
  <TBODY>
  <TR>
    <TD=20
    style=3D"PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; =
PADDING-TOP: 0cm; WIDTH: 31.5pt"=20
    vAlign=3Dtop width=3D42>
      <P class=3DMsoNormal><!--mstheme--><!--msthemelist--><IMG =
border=3D0 height=3D15=20
      hspace=3D13 id=3D_x0000_i1027=20
      src=3D"cid:008001bf578c$a4ee93c0$0100007f@ftid33tp9h"=20
      width=3D15><o:p></o:p></P></TD>
    <TD=20
    style=3D"PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; =
PADDING-TOP: 0cm; WIDTH: 100%"=20
    vAlign=3Dtop width=3D"100%"><!--mstheme-->
      <P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: Arial">qu'il est =
difficile de=20
      disposer de temps pour r=E9unir la documentation n=E9cessaire =E0 =
la=20
      constitution de vos dossiers ou simplement y =
acc=E9der.</SPAN></P></TD></TR><!--msthemelist--><!--mstheme-->
  <TR>
    <TD=20
    style=3D"PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; =
PADDING-TOP: 0cm; WIDTH: 31.5pt"=20
    vAlign=3Dtop width=3D42>
      <P class=3DMsoNormal><IMG border=3D0 height=3D15 hspace=3D13 =
id=3D_x0000_i1028=20
      src=3D"cid:008001bf578c$a4ee93c0$0100007f@ftid33tp9h"=20
      width=3D15><o:p></o:p></P></TD>
    <TD=20
    style=3D"PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; =
PADDING-TOP: 0cm; WIDTH: 100%"=20
    vAlign=3Dtop width=3D"100%"><!--mstheme-->
      <P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: Arial">que =
l'acquisition et=20
      le maintien d'un fonds documentaire exhaustif et actualis=E9 =
repr=E9sente un=20
      investissement =
important</SPAN></P></TD></TR><!--msthemelist--><!--mstheme-->
  <TR>
    <TD=20
    style=3D"PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; =
PADDING-TOP: 0cm; WIDTH: 31.5pt"=20
    vAlign=3Dtop width=3D42>
      <P class=3DMsoNormal><IMG border=3D0 height=3D15 hspace=3D13 =
id=3D_x0000_i1029=20
      src=3D"cid:008001bf578c$a4ee93c0$0100007f@ftid33tp9h"=20
      width=3D15><o:p></o:p></P></TD>
    <TD=20
    style=3D"PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; =
PADDING-TOP: 0cm; WIDTH: 100%"=20
    vAlign=3Dtop width=3D"100%"><!--mstheme-->
      <P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: Arial">que ces =
deux=20
      contraintes nuisent au d=E9veloppement de votre =
activit=E9</SPAN></P></TD></TR><!--msthemelist--><!--mstheme--></TBODY></=
TABLE>
<P><SPAN style=3D"FONT-FAMILY: Arial"><!--mstheme-->Accessible <A=20
href=3D"http://www.adies.com/"><SPAN style=3D"COLOR: black">par =
Internet</SPAN></A>,=20
fax<!--05 59 27 49 57 --><!--05 59 27 49 57 --> ou courrier,<B> =
ADI<I>=E9</I>S</B>=20
se propose de prendre en charge vos recherches documentaires de tout =
ordre dans=20
des d=E9lais rapides, </SPAN><B><SPAN=20
style=3D"COLOR: red; FONT-FAMILY: Arial; FONT-SIZE: 10pt">AVEC =
</SPAN></B><SPAN=20
style=3D"FONT-FAMILY: Arial; FONT-SIZE: 10pt">OU</SPAN><SPAN=20
style=3D"FONT-FAMILY: Arial"> </SPAN><B><SPAN=20
style=3D"COLOR: red; FONT-FAMILY: Arial; FONT-SIZE: 10pt">SANS=20
ABONNEMENT</SPAN></B><SPAN style=3D"FONT-FAMILY: Arial">, et vous permet =
ainsi=20
lib=E9rer du temps pour vous consacrer =E0 l'essentiel de votre m=E9tier =
ou =E0 de=20
nouveaux dossiers.<o:p></o:p></SPAN></P>
<P><B><SPAN style=3D"FONT-FAMILY: Arial">ADI<I>=E9</I>S</SPAN></B><SPAN=20
style=3D"FONT-FAMILY: Arial"> s'adresse =E0 tous les secteurs =
d'activit=E9, dispose=20
notamment d'un fonds documentaire actualis=E9 quotidiennement et =
constitu=E9 de=20
</SPAN><B><SPAN style=3D"COLOR: red; FONT-FAMILY: Arial">1,2 million=20
</SPAN></B><SPAN style=3D"FONT-FAMILY: Arial">de r=E9f=E9rences =
juridiques et=20
l=E9gislatives (jurisprudence, lois, d=E9crets, directives =
europ=E9ennes...) et=20
fournit =E9galement un service de veille th=E9matique=20
personnalis=E9.<o:p></o:p></SPAN></P>
<P><SPAN style=3D"FONT-FAMILY: Arial"><!--msthemeseparator--><IMG =
border=3D0=20
height=3D10 id=3D_x0000_i1030 =
src=3D"cid:008101bf578c$a4ee93c0$0100007f@ftid33tp9h"=20
width=3D600><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN=20
style=3D"FONT-FAMILY: Arial">&nbsp;<o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><B><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial">Agence de Documentation et=20
d'Intelligence =C9conomique du Sud</SPAN></B><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial"><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Technopole =

HELIOPARC-B=E2timent Einstein<o:p></o:p></SPAN></P>
<P><SPAN style=3D"COLOR: #003366; FONT-FAMILY: Arial; FONT-SIZE: =
10pt">2, av. du=20
Pdt.-P.Angot</SPAN><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial"><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial; FONT-SIZE: 10pt">64000=20
PAU</SPAN><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial"><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Tel : 05 =
59 14 71=20
11</SPAN><SPAN style=3D"COLOR: #003366; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial; FONT-SIZE: 10pt">Fax : 05 =
59 14 71=20
14</SPAN><SPAN style=3D"COLOR: #003366; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN lang=3DNL=20
style=3D"COLOR: #003366; FONT-FAMILY: Tahoma; FONT-SIZE: 9pt; =
mso-bidi-font-size: 10.0pt; mso-ansi-language: NL">Website=20
</SPAN><SPAN lang=3DNL=20
style=3D"COLOR: #003366; FONT-FAMILY: Tahoma; FONT-SIZE: 8pt; =
mso-bidi-font-size: 10.0pt; mso-ansi-language: NL">:=20
<A href=3D"http://www.vmgnet.com/adies"><SPAN=20
style=3D"COLOR: #003366; FONT-SIZE: 11pt; mso-bidi-font-size: =
12.0pt">http://www.vmgnet.com/adies</SPAN></A></SPAN><SPAN=20
lang=3DNL=20
style=3D"COLOR: #003366; FONT-FAMILY: Tahoma; FONT-SIZE: 11pt; =
mso-bidi-font-size: 12.0pt; mso-ansi-language: =
NL"><o:p></o:p></SPAN></P>
<P style=3D"MARGIN-TOP: -20px"><SPAN lang=3DDE=20
style=3D"COLOR: #003366; FONT-FAMILY: Arial; FONT-SIZE: 9pt; =
mso-bidi-font-size: 10.0pt; mso-ansi-language: DE"><A=20
href=3D"mailto:adies@wanadoo.fr"><SPAN lang=3DNL=20
style=3D"COLOR: #003366; FONT-SIZE: 11pt; TEXT-DECORATION: none; =
text-underline: none; mso-bidi-font-size: 12.0pt; mso-ansi-language: =
NL">e-mail:adies@wanadoo.fr</SPAN></A></SPAN><SPAN=20
lang=3DNL=20
style=3D"COLOR: navy; FONT-FAMILY: Arial; mso-ansi-language: =
NL"><o:p></o:p></SPAN></P>
<P><SPAN lang=3DNL=20
style=3D"FONT-FAMILY: Arial; mso-ansi-language: =
NL">&nbsp;<o:p></o:p></SPAN></P></DIV><!--mstheme--></BODY></HTML>

------=_NextPart_001_0084_01BF5795.06C3C4A0--

------=_NextPart_000_0083_01BF5795.06C3C4A0
Content-Type: application/octet-stream;
	name="logoadies_copier.jpg"
Content-Transfer-Encoding: base64
Content-ID: <007e01bf578c$a4ee93c0$0100007f@ftid33tp9h>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAgEAlgCWAAD/7Q7YUGhvdG9zaG9wIDMuMAA4QklNA+0AAAAAABAAlgAAAAEA
AgCWAAAAAQACOEJJTQQNAAAAAAAEAAAAeDhCSU0D8wAAAAAACAAAAAAAAAAAOEJJTQQKAAAAAAAB
AAA4QklNJxAAAAAAAAoAAQAAAAAAAAACOEJJTQP1AAAAAABIAC9mZgABAGxmZgAGAAAAAAABAC9m
ZgABAKGZmgAGAAAAAAABADIAAAABAFoAAAAGAAAAAAABADUAAAABAC0AAAAGAAAAAAABOEJJTQP4
AAAAAABwAAD/////////////////////////////A+gAAAAA////////////////////////////
/wPoAAAAAP////////////////////////////8D6AAAAAD/////////////////////////////
A+gAADhCSU0ECAAAAAAAEAAAAAEAAAJAAAACQAAAAAA4QklNBBQAAAAAAAQAAAADOEJJTQQMAAAA
AA1IAAAAAQAAAHAAAABwAAABUAAAkwAAAA0sABgAAf/Y/+AAEEpGSUYAAQIBAEgASAAA//4AJkZp
bGUgd3JpdHRlbiBieSBBZG9iZSBQaG90b3Nob3CoIDUuMP/uAA5BZG9iZQBkgAAAAAH/2wCEAAwI
CAgJCAwJCQwRCwoLERUPDAwPFRgTExUTExgRDAwMDAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwM
DAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4ODg4UEQwMDAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwM
DAwMDAwMDAwMDAwMDP/AABEIAHAAcAMBIgACEQEDEQH/3QAEAAf/xAE/AAABBQEBAQEBAQAAAAAA
AAADAAECBAUGBwgJCgsBAAEFAQEBAQEBAAAAAAAAAAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggF
AwwzAQACEQMEIRIxBUFRYRMicYEyBhSRobFCIyQVUsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNU
ZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSFtJXE1OT0pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH
1+f3EQACAgECBAQDBAUGBwcGBTUBAAIRAyExEgRBUWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNT
FWNzNPElBhaisoMHJjXC0kSTVKMXZEVVNnRl4vKzhMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaW
prbG1ub2JzdHV2d3h5ent8f/2gAMAwEAAhEDEQA/APVUkkF+QxrzWwGy0alje39dxhjP7bkFJkKz
IrrOyd1kT6bdXf5oUfTvt/nX+mwjWus6/wBq7R3/AG36aJXVXWIraGzzHc+Lv3kVNXMtzG41trSK
A1ssGjnzP5/Nbf8AwT+uidPzGZ+FTmMBa29oeAeRKr9as20V1A/zjxI8m+7/AKrYofVgz0DBj/RD
8pSU6iSSSClJINuZi0uDLLWtc4hobMmT5BGSUpJJJJSkkkklP//Q9VQaObf+MP5GoyFR9O7/AIz/
AL6xBSVJVuodRwem4zsvOuZj0M5e8xJidjB9Kyx0e2tnvXnPX/8AGTnZu7H6OHYOOdDe6De4Efmt
9zMb/p3f8UkkC3s+sWh2c1k6VNAPkXHc7/o+mn+reUxnRMWoMe61jCHVtaZHudo4u2sZ/bcgfU3A
xHfV3AyLGerdbX6lj7CXkvc5znvd6m7c7cuhRQgLs2yNjWUDuX+93+ZWWs/8FQ766aq3XZdr7GAa
tJhp/kiuvY139pXFjXY+d1Ii9pYyg/zTHOMgcbnBrXe9ySnOzbzayxzGiqtjHmqtoDQ3Qn838/8A
eW/0p7rOl4ljyXOdTWXE8kloVEdAe9hbbeBuBaQ1s6EbfpFyuY3T7MeivHblWenU1rGABg0aNolx
Y5yCm6mJAEnQDugnDqIh7rH+M2OE/wBlrmtQ7KOnYrPVtrraB+c4bjP8mdzkVJH5+EzR17J8A4E/
5oU6b6b2b6XB7ZiR4hYeX1J9wNdDfQp4IEBzh/Kj6CX1fss/amZSXH0hTS9rOwcTa1zv+igp/9H1
VVXXGmvNuDdxqJcGkwDtqrfyrSpXx9n6ju490/D0a0FPivVOt9S63kDN6habX81VDSusO/Moq/N/
4z+ds/wj0/Ruh9V61ca+m45tDSBZaTtrZP8ApLT/ANQz9Iuo+qP+Lq7Lqpzeuh1GPtaWYX0bHwP+
1P51Nf8AwTf03/Fr0nHxsfFoZj41TKaaxDK62hrQP5LW+1KlxPZofVrCt6d0TF6fc5r7cRpqseyd
pLSdWbvcreb1HA6fUbs7IrxqxrutcGD5bl5r9fvrX13B6zk9Hwcg4mNXss30+21xsY21wddrtZu/
0S87ybbLrjda51tjjLrbCXuJ8XPsLnJKEbfZ87/Gp9U8YO+z225z2zDaKnAEj/hb/RrXSdIcH9Mx
bBoLKm2AHkB49QA/5y+cJPJ18V1XTP8AGZ9aem0VY7LqciihoYyu6sE7WjaxnqVuqsdtStJh2fcU
l5h0/wDx0AQ3qnTT/KsxXz91GRs/8/rsui/Xb6tdb2Mws1gyH6DGu/R2yfzG12fzv/WfUSWmJDpd
QzvsdYIbve8kMHaR3csG6+2+z1Lnb3dvAeTG/mrU69/N0f1j+RZCSFKx9X5/bmZ4fZaNP7d6ro/Q
dOvZA192JV8NLLklP//S9VVOwbqs9vjP41MVxVa2b7cys6B5An41tagp8s6F/jI690+muvNI6nVt
b/PHZaNB/wBqWNd6n/Xq7LP+FXX4H+M76tZJazJdbgPdz6zJYD/x1Pqs/wA9cX1r/F713pA3Y7P2
jiMGltDf0gA/0uLLrP8Atj1VzQEPc06OGhaRDgf6p9yGq6gXpvrR07N+s/1tyr+g0nOx3Cpoyq/5
iW1ta8faj+h9v9ZW8f8AxS2U49mZ1zqTMWilpstbjtLoY0b7d192zZtaPzal1/8Ai4/8SWKIgh9s
/H1Hqj/jby7qPqs2mslrcvJrptIJHsiy7Zp++6pqKrOz5P1V/R33x0jHsoxGTtfkP33W/wDCWx+j
p/k11rNcY7SU7i7WEgyddHT9yDIET3Dgfjyozx5ceS6T6rdXwumZgq6niUdQ6XkOa3Jrura81jj7
Rj2PDnVur3fpGf4Vi9H6t/ii+rWc19nT7Len2v8Acz0z6lOv/AWe7Z/xd1aKDKjqNHk/8XnX+sZ2
Zb0zNy7MnFoxnXUstO9zXiymv23O/S7Nljv0e/Yu6XJ/V76l9Y+q31lf9rAuw7sWxlWZX9Bzt1Vn
p2N+lTZ7fz/p/wCDXWJMcqvRSN0Of2/b4fY2f+fbUFG6Kf8AsgcP+6Y/8+vSQ//T9VVej+lZI82H
/ohWFWo/pmUP+L/6lBTZVHqPROkdUbHUMOrJMQHPaC8Dn2W/zjP7DleWf1frvSujU+r1DIbTIllf
0rH+VVLf0liSnKwurfVj6uZVn1eN/wBi9J3q1C8n04u/SbGZFnt9rt/869WPrb0Vn1l+rt2Jjva6
xwF2JY0gtNjPdX7/ANyz+bXmX1x6izqnWj1BlVlFeRTXsrtEP2tNlYc5vu/nNu9YmN1DOwLfU6fk
24rx/obHMB/rMB9P/opWuAc3JxbaLrKbWOrtqcWW1vEPa4GHMeP3moUOaZjtotXqvVc7ql32rqdo
vvDAz1NrWOLW/Q9T0ms3u/lrLc7UxoECyBf8wz4FfR3R2WV9IwWW/wA4zHqa+f3gxocvDvqr0npe
bk/bOtZtGD0rGIdaLLA224t932eimfVc3/SvYz/i13XXP8cfRsZpr6LQ/qFpGltgNNI00Pvb9os/
qenV/wAaiFktdA9f14H0Kj236/5rljrifqx9a+tfWL60h/U799bMe8049Y2VMMN+jX+e7/hLfUsX
bJLSKNKRuig/84Cexw/yWuQUXpH/AIoGeeI7/wA+JIf/1PVVmZfVOn9LuysjqF7MakNq9zzEzvbt
Y36djv5LFprO6l0HpnVbqLs6r1TjEmtp4k/vIKecs+s/1h6/Y7H+rWIcbFna7qOS3Uj96ml230/+
u7/+KV3o/wBRsHEu+3dSsd1PqDjLr7zu1/t7l0tdddTBXW0MY3QNAgBSRU811r6ldI69kXX3+pRl
V7amXVOiGtYxzGOqduqcxrrHfmrjep/4reuY7i7Csqz6/wA0fzNnzbYX1f8Agi9SpEWX+bwf+hWm
ycvEw6jdl3V49Q5fa4Mb/nPLUE2XwbP+rvWsMluZgZFXiTW5zfk+r1Gf9JYz6HMJEERpDhB+bSvc
Mv8AxhdEY809NZd1W/8ANGMwlk/uuvs2s/7b9Rcl1H6nfWP6ydWv6rXi14dWYWOPr2AFjgxldlbm
1tfY7Y+v/RpUuE+75q+vUkj5pjX+J+ZPkvWcH/E/QYd1TOJ8a8ZobrP+muD/APzyuu6P9T/q70Zw
swcNgvH/AGos/SWz4+pZu2f9bSpPHWz5j9Qfqx1vDzG9aysc4+C6uylht9tjy8e0soP6TZ7fpvXd
rb65/RGf8YPyOWIksJs2VIvSP/FBX/4Uf/58CEidI3H6xNHZuGT5+6w/+QSQ/wD/1fVUkkkFKSSS
SU4XXcL6y5FzK+jZjcKizXIsLWufMbP0e/dt+is/F/xd9MNv2nquRd1PJOrn3PJE/wBouXWpIqa2
J07BwmBmLQypo/dGv3rIz/rZ0nomRZh5vrHILnWNrrqc+WvO5h3sGxdAhPxcayz1LKmPs43OaCfv
KSnl3/X/ANTTA6Pm5R/NJb6Y/wCnud/0VD/nH9d8kxi9BZSDw660n74ZUuva1rRDQAPLROkp5Hf9
cLHh3WmY1eF2ZTO8Wf4M7i93t+kpAEmBqT2W19YLG1dNfe+fTpIe/aNx2j91o+kuRxem9c+tB9zX
9L6K7lp0vuH/AArm/wCDd/omez/jElMb+r5GVk/s76v1jNzJIsyOaKfPd9DIf/a9JdJ9Wfqz+x/V
ysm9+V1DLg5Fzj89rf5LVo9L6R0/pOM3HwaW1MAgkDU/1nK6gp//2ThCSU0EBgAAAAAABwAFAQEA
AQEA/+IMWElDQ19QUk9GSUxFAAEBAAAMSExpbm8CEAAAbW50clJHQiBYWVogB84AAgAJAAYAMQAA
YWNzcE1TRlQAAAAASUVDIHNSR0IAAAAAAAAAAAAAAAAAAPbWAAEAAAAA0y1IUCAgAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARY3BydAAAAVAAAAAzZGVzYwAA
AYQAAABsd3RwdAAAAfAAAAAUYmtwdAAAAgQAAAAUclhZWgAAAhgAAAAUZ1hZWgAAAiwAAAAUYlhZ
WgAAAkAAAAAUZG1uZAAAAlQAAABwZG1kZAAAAsQAAACIdnVlZAAAA0wAAACGdmlldwAAA9QAAAAk
bHVtaQAAA/gAAAAUbWVhcwAABAwAAAAkdGVjaAAABDAAAAAMclRSQwAABDwAAAgMZ1RSQwAABDwA
AAgMYlRSQwAABDwAAAgMdGV4dAAAAABDb3B5cmlnaHQgKGMpIDE5OTggSGV3bGV0dC1QYWNrYXJk
IENvbXBhbnkAAGRlc2MAAAAAAAAAEnNSR0IgSUVDNjE5NjYtMi4xAAAAAAAAAAAAAAASc1JHQiBJ
RUM2MTk2Ni0yLjEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAFhZWiAAAAAAAADzUQABAAAAARbMWFlaIAAAAAAAAAAAAAAAAAAAAABYWVogAAAAAAAAb6IA
ADj1AAADkFhZWiAAAAAAAABimQAAt4UAABjaWFlaIAAAAAAAACSgAAAPhAAAts9kZXNjAAAAAAAA
ABZJRUMgaHR0cDovL3d3dy5pZWMuY2gAAAAAAAAAAAAAABZJRUMgaHR0cDovL3d3dy5pZWMuY2gA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAZGVzYwAAAAAAAAAu
SUVDIDYxOTY2LTIuMSBEZWZhdWx0IFJHQiBjb2xvdXIgc3BhY2UgLSBzUkdCAAAAAAAAAAAAAAAu
SUVDIDYxOTY2LTIuMSBEZWZhdWx0IFJHQiBjb2xvdXIgc3BhY2UgLSBzUkdCAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAGRlc2MAAAAAAAAALFJlZmVyZW5jZSBWaWV3aW5nIENvbmRpdGlvbiBpbiBJRUM2
MTk2Ni0yLjEAAAAAAAAAAAAAACxSZWZlcmVuY2UgVmlld2luZyBDb25kaXRpb24gaW4gSUVDNjE5
NjYtMi4xAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB2aWV3AAAAAAATpP4AFF8uABDPFAAD7cwA
BBMLAANcngAAAAFYWVogAAAAAABMCVYAUAAAAFcf521lYXMAAAAAAAAAAQAAAAAAAAAAAAAAAAAA
AAAAAAKPAAAAAnNpZyAAAAAAQ1JUIGN1cnYAAAAAAAAEAAAAAAUACgAPABQAGQAeACMAKAAtADIA
NwA7AEAARQBKAE8AVABZAF4AYwBoAG0AcgB3AHwAgQCGAIsAkACVAJoAnwCkAKkArgCyALcAvADB
AMYAywDQANUA2wDgAOUA6wDwAPYA+wEBAQcBDQETARkBHwElASsBMgE4AT4BRQFMAVIBWQFgAWcB
bgF1AXwBgwGLAZIBmgGhAakBsQG5AcEByQHRAdkB4QHpAfIB+gIDAgwCFAIdAiYCLwI4AkECSwJU
Al0CZwJxAnoChAKOApgCogKsArYCwQLLAtUC4ALrAvUDAAMLAxYDIQMtAzgDQwNPA1oDZgNyA34D
igOWA6IDrgO6A8cD0wPgA+wD+QQGBBMEIAQtBDsESARVBGMEcQR+BIwEmgSoBLYExATTBOEE8AT+
BQ0FHAUrBToFSQVYBWcFdwWGBZYFpgW1BcUF1QXlBfYGBgYWBicGNwZIBlkGagZ7BowGnQavBsAG
0QbjBvUHBwcZBysHPQdPB2EHdAeGB5kHrAe/B9IH5Qf4CAsIHwgyCEYIWghuCIIIlgiqCL4I0gjn
CPsJEAklCToJTwlkCXkJjwmkCboJzwnlCfsKEQonCj0KVApqCoEKmAquCsUK3ArzCwsLIgs5C1EL
aQuAC5gLsAvIC+EL+QwSDCoMQwxcDHUMjgynDMAM2QzzDQ0NJg1ADVoNdA2ODakNww3eDfgOEw4u
DkkOZA5/DpsOtg7SDu4PCQ8lD0EPXg96D5YPsw/PD+wQCRAmEEMQYRB+EJsQuRDXEPURExExEU8R
bRGMEaoRyRHoEgcSJhJFEmQShBKjEsMS4xMDEyMTQxNjE4MTpBPFE+UUBhQnFEkUahSLFK0UzhTw
FRIVNBVWFXgVmxW9FeAWAxYmFkkWbBaPFrIW1hb6Fx0XQRdlF4kXrhfSF/cYGxhAGGUYihivGNUY
+hkgGUUZaxmRGbcZ3RoEGioaURp3Gp4axRrsGxQbOxtjG4obshvaHAIcKhxSHHscoxzMHPUdHh1H
HXAdmR3DHeweFh5AHmoelB6+HukfEx8+H2kflB+/H+ogFSBBIGwgmCDEIPAhHCFIIXUhoSHOIfsi
JyJVIoIiryLdIwojOCNmI5QjwiPwJB8kTSR8JKsk2iUJJTglaCWXJccl9yYnJlcmhya3JugnGCdJ
J3onqyfcKA0oPyhxKKIo1CkGKTgpaymdKdAqAio1KmgqmyrPKwIrNitpK50r0SwFLDksbiyiLNct
DC1BLXYtqy3hLhYuTC6CLrcu7i8kL1ovkS/HL/4wNTBsMKQw2zESMUoxgjG6MfIyKjJjMpsy1DMN
M0YzfzO4M/E0KzRlNJ402DUTNU01hzXCNf02NzZyNq426TckN2A3nDfXOBQ4UDiMOMg5BTlCOX85
vDn5OjY6dDqyOu87LTtrO6o76DwnPGU8pDzjPSI9YT2hPeA+ID5gPqA+4D8hP2E/oj/iQCNAZECm
QOdBKUFqQaxB7kIwQnJCtUL3QzpDfUPARANER0SKRM5FEkVVRZpF3kYiRmdGq0bwRzVHe0fASAVI
S0iRSNdJHUljSalJ8Eo3Sn1KxEsMS1NLmkviTCpMcky6TQJNSk2TTdxOJU5uTrdPAE9JT5NP3VAn
UHFQu1EGUVBRm1HmUjFSfFLHUxNTX1OqU/ZUQlSPVNtVKFV1VcJWD1ZcVqlW91dEV5JX4FgvWH1Y
y1kaWWlZuFoHWlZaplr1W0VblVvlXDVchlzWXSddeF3JXhpebF69Xw9fYV+zYAVgV2CqYPxhT2Gi
YfViSWKcYvBjQ2OXY+tkQGSUZOllPWWSZedmPWaSZuhnPWeTZ+loP2iWaOxpQ2maafFqSGqfavdr
T2una/9sV2yvbQhtYG25bhJua27Ebx5veG/RcCtwhnDgcTpxlXHwcktypnMBc11zuHQUdHB0zHUo
dYV14XY+dpt2+HdWd7N4EXhueMx5KnmJeed6RnqlewR7Y3vCfCF8gXzhfUF9oX4BfmJ+wn8jf4R/
5YBHgKiBCoFrgc2CMIKSgvSDV4O6hB2EgITjhUeFq4YOhnKG14c7h5+IBIhpiM6JM4mZif6KZIrK
izCLlov8jGOMyo0xjZiN/45mjs6PNo+ekAaQbpDWkT+RqJIRknqS45NNk7aUIJSKlPSVX5XJljSW
n5cKl3WX4JhMmLiZJJmQmfyaaJrVm0Kbr5wcnImc951kndKeQJ6unx2fi5/6oGmg2KFHobaiJqKW
owajdqPmpFakx6U4pammGqaLpv2nbqfgqFKoxKk3qamqHKqPqwKrdavprFys0K1ErbiuLa6hrxav
i7AAsHWw6rFgsdayS7LCszizrrQltJy1E7WKtgG2ebbwt2i34LhZuNG5SrnCuju6tbsuu6e8Ibyb
vRW9j74KvoS+/796v/XAcMDswWfB48JfwtvDWMPUxFHEzsVLxcjGRsbDx0HHv8g9yLzJOsm5yjjK
t8s2y7bMNcy1zTXNtc42zrbPN8+40DnQutE80b7SP9LB00TTxtRJ1MvVTtXR1lXW2Ndc1+DYZNjo
2WzZ8dp22vvbgNwF3IrdEN2W3hzeot8p36/gNuC94UThzOJT4tvjY+Pr5HPk/OWE5g3mlucf56no
Mui86Ubp0Opb6uXrcOv77IbtEe2c7ijutO9A78zwWPDl8XLx//KM8xnzp/Q09ML1UPXe9m32+/eK
+Bn4qPk4+cf6V/rn+3f8B/yY/Sn9uv5L/tz/bf////4AJkZpbGUgd3JpdHRlbiBieSBBZG9iZSBQ
aG90b3Nob3CoIDUuMP/uACFBZG9iZQBkQAAAAAEDABADAgMGAAAAAAAAAAAAAAAA/9sAhAAEAwMD
AwMEAwMEBgQDBAYHBQQEBQcIBgYHBgYICggJCQkJCAoKDAwMDAwKDAwMDAwMDAwMDAwMDAwMDAwM
DAwMAQQFBQgHCA8KCg8UDg4OFBQODg4OFBEMDAwMDBERDAwMDAwMEQwMDAwMDAwMDAwMDAwMDAwM
DAwMDAwMDAwMDAz/wgARCAEhASADAREAAhEBAxEB/8QA0gABAAEEAwEAAAAAAAAAAAAAAAYEBQcI
AgMJAQEBAQEBAQEAAAAAAAAAAAAAAAECAwQFEAABAgYBAwMCBAUFAQEAAAABAAIRAwQFBgcIECAS
QCExMBMiMjU2UDQVFiZwgEEzFCU3EQACAQMCAgUGCQkFBwMFAAABAgMAEQQhBTESIEFREwZhcZGx
IhQQgaHBMlJicrIwQoKSI3OzJBVA0aIzdFBDU2Ojw2Thg5NEJXUWJhIAAQIGAwEBAAAAAAAAAAAA
IQBQECAwQAExYIARcXD/2gAMAwEBAhEDEQAAAN/sgAAAAOgjxJz6AAAAAAAAAAAAAAAURZDtMfk0
JeAAAAAAAAAAAAAAW0tJVl9BrMZFMqAAAAAAAAAAAAAFmKAuRdgC3mtRlEyoAAAAAAAAAAAAWApS
7lyAAIaYNMjmXQAAcS1FiJmfQAAAAAAfCMEoAAAMWGMTIJmAA4FgKI+EcIIZLMhgAAAAAA+EaJMA
AAYNIyTAzAR86DmXwuBEzE5bSSGcgAAAAAACLkoAABjuXHtglJMiRFSARUxOcSiL2Z2AOgtxbTqB
xIUTklh9AIuSgAEZl0/nbHsb/b4SQ7gACNmIzrBxLsZBOJzO0uRXlQW8xcRwsJs+cwCKkqB0mtmO
mmvPtYujNFx6Ma4AAAYxJAV5cyqOQAABDjGhTgiVbXRzAIsSkjC6J8O+Db0ptZ7ssz9MekOuAAAE
PJgAAAAURjEiwAInW1kdgBFS4r5i8PVC7Os6179TYfXL0B1yAAp1gWd1msTlAAABFzF5RgAEJNtT
tAIkc18qOHqprFmSdc90OnPJ0kjOJDprAme2A+fTC2ulkuvVfp8/K7IAAAwOUYAAIhW1sdwBEioX
ym4+moudw+/HafOawjxgPn01Xz6cIOlq656ZeM3UybXZ5Z1uMoXlkTfO42AAYIKIAAELrbGO8Aip
Ur5wTrvdrllKQCLr5FcvbaN6tpQY39mvronKojknO2Sxl7XHZjXLYjfnkdgwQUQAAIZW10VIBFDv
WHy5UuQBGl8guXvtmtW6OOdUvLTefjfSn2OC8euOletZBNbazz7jdPFD9YpwAAQitsIqwCJlevlL
y9OeWdld88v6xVJHJfILl7aK9bzvnmnXDKVxqp5fbjXHSl6Pmp03PC7pddOOc/GOU6XOT0T6/NyH
eIAAglbZxWAESLmvktz9NBl9kksuXuknNxiLU2fuM93NZL5Z8ffhLO6fF6dW376cNXhM9Rxc/tqT
636K7+flXXAAAQg2vKwAiJdl8mefptmZ1ydE7VmuV/t9Y+vlrga257eYmfVRt8M54X08LjnE9nHc
f0+LGed68Z9kG59U36Bdvm5heYAAQc2tK8AiJKTWpvUfPWA89dLXK5kyesPXz1qDz1z69Op6KCb6
JanLs1nuznv1Nh7j0+6eGls16vTTHPqz5PPmO8QABAza8uIBFCVgozAzWuzWF89Lhh6r9eFeg0Fe
nS3Peim+KsXvmO6Xn0leesm/Bli4FKYBXsQAAQGtsYuIBFiUgAFmrE9uYsyvBgedPLue20avRy3y
k563yxmo6YqD0r14dmLzAwaW0AAEArbKLiARUlQAALWaac+2wu8ZSuSedM9OrufTRY18w6Om/vO1
N51PSepW/n54uAMHFsAABBK2ui4gEWJSAAC2nk5y9VnzZnJmLWslb4aYz1Y7x1p856sXjt31KO09
dtfOlSda4E598eXE+3yAAEGramLoARYlIABTGGTz44+qxlM1Ru3Rm8Ol6i2YlE123N03z9DOvi2X
w1yz3095erBzvvB3+dna+YAAQStqYuwBFSVAHUYjNS6qzDXL0xuW3zfTOqumrNdUWb8OOpkqZnTO
Db1jTrxy7LreXp83YC+UAAQI2qLuARclBxMbGplWA2ojK5rBda956Yw5dKeWl10pm7fbapes4bdW
bT3fXdsTrs53e79+bsNrygACBG1RdwCJFKal1AzZ2M5l2KEoS8GNdXBcYRm8W562GbtF6UWVPdU9
da/TjrfbeeYnHbqeWasgACBm1BeADFhpZWwpsHF9PoKEoC+gHEsekSmtP89dYOfp6LqkXo3m7XGd
+vDaXPHYHExWR8AAEENpy8AFvLaSA5AApS1l+ABSmMzVrPbXLHWR9M5X1zzfZnBzl+QGHyNgAAxv
W2kXgAAAAHQWkvpSGMDA1YnL6ZxXMNTWTvgAAYfI2AADG1beRcQAAAAdBh0wdWLCSmbjMMS8ixMw
AdRbSzEXIwdQAKcwRV2N5IqQAAAAfDXkpjLpKioPoMckYIOQ+osR8pjvJIZSiTAEcNdqzqbRxdz6
AAAAAcT6fQACBmrdSYmkSokpdy5lSYnIufDD1Y8NwIzGdwAAAAAAAAAPh8Pp9AABiQx4a71kU23i
Un0AAAAAAAAAAAAAAGHDTitqIzwVQAAAAAAAAAAAAAAAMbGNq2LjvAAB/9oACAECAAEFAP8AYNH+
BRUUB/AS5EE9B/APIlD2UUCh68+5Xwh7rwTQR3+Q9R/yg2KayCj2EgIuX4ivBNYPUQTWkr47PNFr
imsghAI/l/4XkUJi+4FH0gCj2ge8OjvYeXsSorzUQjBAIv8AFB4QIPoQe4fJ6OKB6loXigOh6eME
HEIOH14IOKDo9SmqJKAKDAnFgT3xTUFCKggew9B6A9PIoOivABQAUenyh0BKEUTBQXuo9Copvx9c
9R89XFAINigxQUYJwimkoEQ8AUWqB9BAItCgoI+yaffq4dA6CBKJKiiV8oe3SKivAFAQ9AfdQCc1
Nb2O+IIiCaUSnFAKCIQ9NFA9hRcgYgIr5R6j1AcVEdS2PRqBRICKJ6D1BUF8LyKE0IuBTUYIRQRC
aI9jnwTSSPRn56+3QrxARCAQBci3xRcAi5EkpoigIekcoqKj0Hb5ELyKhFHoBBAx9J4tKLAvAqC9
kOkEAjAI+yj5LxK9ug900Q9N5FQBRlheLkQUQooiK+V9teBXiF4JrQPVeRR904oKKJUShFGC8vWk
RQY5CS4rxaogLyPrwV5FR/1o/9oACAEDAAEFAP8AZSGBO9h/AGsigIdH/HrwwDsf8eugAEAvZEhO
d3iW4+nHyfhRCLu0NJQklCUAhAL5Tvn0wRKJ7PBBrVEBOJQCh7BPpySZBRlOHpS4hEx7QPZR9y0F
EAIQAgF7qBR9kYFGSCjIciCPQkHtHy34jFBqMUPgGKaAor5RHTxK90YOUyQE5jm/WHy74LQU6WR2
NdAEhfcATpxQLypbPAJ3yopogiUCE50CnNDlNaGv+r8ooEhQijLagxF5CLiestgao9PlCATmhCKL
fJBsOgJQU78/1QiggF7o/HWU2JJJXjBe6Yz2cIEGKmMKJe1MnEJtQ0ouDk2Cqfz/AFQ4hAhABecO
h+OshNKBXsEXleUUSmlTWxHQPITJynGLvr+RXmVEKIh1klNRChFFFQTnIe6eIO6kx9GDDsYYFAlR
PSARCc1NCmfm9P4BeJ6smIHq1OgiYoJ/5vURXiCjJC+0UyPUdGiKcQ0ExPRshxU1oa70rRFEwUes
EEUXeIdM8yASmyCUySGIElVH5/RtKAQ9kT1HYWeSbJaEGgdQqn8/o/IhCYvJeaBPQFRUUVFNgopo
RBQVQYu9KCooTChMCDunuj0ioleft92CdPKc6J9SDBSnFeSCMFEBGYE6d5KJPrZZUQvuwX3Ci8o+
/rwf9av/2gAIAQEAAQUA+nUVVNSSqbOLPWXOMf4BX3Ogtkr+uXm8OpcUpzO2reJeO1+v8jdkdn9b
cL3bLYhW5LexRYxb6ab03BVuuNn0cCMW9XcMitlvmfbyi9K3Y/bLc7reqw0FpzkeWI6Of5Yt6mty
mikz/wCmZBelbbLbrVL7djVpkWfN/bENCvLsX7iQBcMkslsFPsS31NeHBw+vhUtjaHv2PV/evGZy
XT8S0H+1+r3sltuGaWCgX9dyi6r+1Lxc25SMctFPcKt9BQaqyudlFm+vhT/Oi78hqjW3zIm+WP8A
Hud9zGaiqpaRlRnFoa7/ANmbXYMwsVTqCzWq2BZblkuzynOc92Qj/wCBx0fHHPr4V/L92cbaw/FZ
IIcJlnqL9S4LrrI8cttNglsE6koaOhl9ctyuXZJM2bNnzFeP0nji8HHus6qpqds/KMephO2BjkpO
zadPa69ZpPBZsCpFyyK+y6rEMmbc6Lsww/g7MvzvF8Gt+0OWOR352m6CZlGwbbgljoRKpqenHble
TS7DSz586qndJ9tqLnRawxvLMKtYfsKoY2x5pUtOE/fZKwDHJak4zj8gMo6SUFc7tb7RIyPMa69l
YbeKyVtOWYy+uGAtd0nTpNPK3FyptOMNynM75l1zE8Q43uAzzvtOOHLqmRruwShT4bjdMqe2W6la
AGjvyDOqK3Cur6y5VHTFZBlbglf9XXESf/Us0zvGsCtO5eSOQ7FnzHuLWl0xzXknjhOc7YXfr/8A
lPo3C50NrkZBm1wur+yxvMnbsgxk9cSI/qOUXh2P47sPY2UbAuzpkXGe0Bv4zKkzHTtB4Flloynt
qqylopeS7u1vi8nWNXJuNl+hkeZUVmFyutwu8/ttDZo3FTfy/XE5fjedjua3A54d5kRY6QHDW2lc
z2DXa54xYJhIy2VKk44iQBk+08BxGTmfOLA7S3Luauz75Lum18+vCkV5qpvHR7X6n+hdwRdu6gc6
XtymMafriwhkGfta7B6kO8rNZrjeqzUPFClkMt9toLVSrNHfaxrOOZOGY9Jzjk7tPLVcLhV1Tp09
xeaolGa4PlTQw6c5eP11jlo5xa3rHY3yG1Xk5or5ZrkztvP6v3Mlz5W26MxpeuNwGR5y5jML1/rH
Idi3nVej8T1jS9djGGB3GY4Tqia5ynzBNmTJjjMd4Pc4h6DHtDZgam1U4llxJbZdoZnjzcN5o7Vx
uZgnOHX+QuxvOcUy6n6Xog3juq532tpW8+VH1x0/5LnglnDNM5JrWpxjs2CI4PdHH/0zWgsLCEZL
SZjWh0sEtf5xdAKL/Ez/ALYmPY1PfMlTG1PkbFneU4u/UfO25WaRr7euu9kUdwniqr+66kDZlsMa
Drj5H905kI4jIuVbbqvBeXGfWBYPyc1rmTqG4UFzp1nhDcKugYamVTlzbTr3KL9PxPhrsi/tn8SN
V4JZ9m5ZiV4Ez8KjF73MYi2VVGoeGMLjAQgXgEFWe/XjHqvRl9uuS6r7rx/+m2v+Q62E/wCX5cPL
FKwBlUZri77kTj2yc4xZYzzI2hZVf+ZtNkuLYLxm2Jm03AuH2DY4rRi+P2KTca+mtVv5H7ou+zcy
mOa11U/ya+X4SXNiGse1PJmIjya1pCgSfxNRXG9wdpjuvLQ3Y9r/AJDrZAW5plQLsYu0gmsmNDD+
GDw3y8CWYFJ/9uXWiQ2mtXTmLsSrw3X86c9z3z3eTqgNL58HS5bZqMhrTre84vQ3uRxE1Hs21bA4
I5tYpOW6h2Dhb5tO9pEoCXxhmF2nu7I3eGe2cxtvW1RGdTZUudL2jxIsGSvzfUeb4FUOkEo0vm5p
cxYC7xzC1Em19Odd6qp2bVJHlMlF76iP3JcgNXgFJpzBsuWBxa3Lc9f5dTVEmrp7hZbPdmbE4Y6z
zJ24+LGb6ymcYh46o7sqMM7sn6X1t4hnXSvt1BdaXN+JOvsiGZ8SdkYzLu+NXyyPwxkqXk1lj/R+
nOvHJ39yVUiDvgPLfGUHNbLPmZxcGyotFtn1Eidx3yidlOr+ldQ0lypf7as+KVvdlTI5/ZP0vrRN
hnHbfMWx3JZOVcbdcTVZ2htp6cqtfT851xW2uoYJsnxLmCZ0Y6DXTHuDXNIp2Pc7hXMmv1r1yOP9
e7sqJGeWP9L60/7+7shb5WHF+Wt5xqvwvkRrrMmU1XS1kuqpaetpuUOjKjAr1OlMLplLAikH2gx7
AGn7gliWqf3ncTrKbTqvrkpjkHdlkp397WP9L6ygBn/dkH6FkbpjL6Jz/LHNx7DxBYrzeyygmT+V
Gps+t2z7Hilsv9TJcHzA5i/CQP8AuLHudiGOVeR33XeOvxXClNmy5MvbfK/XetabUuyLntSwd2aT
Pt5Pj7vK09W+2wO2qq6aik53yBwi2VGS+QvxYYTHuaXOmAzn/ea4uIqJ4ltnzi5EAmSXNVrttxu9
fxi46Mws3jKscsFPsbnHrLFpWyuV+ztg1NTPmzTxNntnav7s6P8AkWN+9n6uBbn/AFmTZclmxuQe
GYNIzXduwtl1WCaTvdZPzSn+1k81rwJhnRDneUDGefesnzPJzi4kRUXQ1Zs+z62qMu5s7Rv1Ffs+
zbIwQWmJUskHiR7YD3Z5+4cZ/Rus/wBs8RIYM93ZhWB02dckc7zmfhunciyyswHQlnscuptFHbbH
kXE+TltuzbRWwMGn1cqbSzBR+U2dLcx86U6WZ9M2YJlPMlnxIUIp/nLmT5QYhLLw+VLY0tIDWuLe
Ij/8G7s7H+QYz+jda2YZefZptPDsFpNkcoMly52N6vyvNq/X/Hq22uXacctlnlAQV69rRh/7amyZ
M9mX6E1tmYyjhRKmPyvjXsrHJ1xxS9259RTS5RqpL3NfTPaplO0mdKa0lpJ+2GtbTMJbSumHVHGf
Ndo1Wu9R02n6Xuzv9wYz+i9dwSKuTQNwbMM7yDXnHOkohZMUtVkkgADpefe0Yf8Atrq5rXCvw3FL
o2v0Jqi4TOVGocYwCunUjnvm25swf094TrZOebdhtyu1Rg/DvY2THWnDzXuFq12e12Slzlnhk/dn
hhesYMbL1u1pp7tItOG2a0Oa1rB2V7Q+iw39s9lXXUdBLzDkFrjD28ic6kbOsUqhn1JtGq8yvLLD
w52Jc5WL8McLoBjmscHxWR1z39zd2ePnPzLGGltm+lVfyuHftpVtxoLdKy3kTrTEzlvMO+3A3PJN
s7BqcY4+366OwvR9hYLTp7XVlNPTU1Kzuz2P9y92R11FW7HsQDbX9KpBNPXbrxbXWOZVzAym6trb
rtbPanF+PN8uZxTjRb6RWPV+OWdlPb6Ola8Q2L2TZ8iQ2fk2P07a7ZuH29XPkBgVvFVlNDmM/srK
2kt9Pnu6aq5TdHa1vVReKCSaek+k4RbtbUNVmdzxbjZa6IWXW2PWdkigpKYdcpvUnGctuXJrX9E2
68xMdki58wL1NFy5KbOuYnbE3JdDOp9uX4UWj8susyj413yasHwufgdo65dm9hwuiveR5jtW46o4
+BismPW+yU31PFpPds7F52TWY8ZLlUVVp4uMAt3GmyyFQ6HxilNJq/GaUSMOsVOpNqt8gCRJatgN
DciTnNa3Pd3UVqdimusnz26a00ta8bppFPKppfpCAUGMCgB37C/cOR5TYsVoss2Nk+xqjVvH6qr3
4thNqxulAAHrtzGttcmlxLMdi3/WGiLfZJNFQU1BK/gG3v0TU/8AM0v/AFd3/9oACAECAgY/AOpY
4WeCiYzFg84OYDhGZTDdmPxoQFAI3GqIYjclBnC1MJCxhhHQr//aAAgBAwIGPwDt6EYaYQ2agGXS
COLAUAhlfaAjnGLQUxLm6CMRlbRgIZYy+ihlkzdFCBmMvmL/AOQK92w64EaJYwjfjoZ//9oACAEB
AQY/APyZnypUhhXi8jBV9JqLbMXvHEx5FyOXlQsRoADr8laf7A77PyEgTq5j7R8wGp+KjFsGAYcf
gdxzQUTr1ROLUuZvORJumaNeabSJTofYjGg4V/VYAE/p2LE1lAUAiViNPM1RZr8XUH0/27ly51Ex
F0gW7yt5lW5of0+AbVgtb+YyRzTspsfZTUDQ9dDLy+bP3DTmysk87XtbQG4A+HxJkji/0fuJIqj/
AArWPf6g9X9s93LnIzDouNjjvJLnhcDQceugZXGy4RH0Y/byWvfrNuXqoyxRd5lE8z5Mx7yUt28x
8/QzMxfpxRMUvp7RFh8preOq2O5/V1+asf7g/tT4WAj7huC6dzjjmAbXRm4DhQbd8r3DEuD7niGz
MLg2Z6CYcCo350p9qRjaxJY669KLEUi+VKA46+SP2vxctb2f/El/DUH3B0ySbAakmj71mJzi37JD
zub8PZW9Q4iY0iQzOIxO7AEFjYHlF9Pjq6m48n9gzXCgSNmzhmA1PKRa58n5CDFHDGhBOv50hufk
Are0U2PuU7C/2EY/NUH3B0C0jBEGpZjYD4zRUZHvU3VHjjvLns5h7Py1y7RtHukRNvec08oAPXya
H0c1f/0G8yOhBHu+LZE18pAv8a02z7VipJntyjIyHvI0fLrYMb2Y9fLWVnRn9pjQyTLftiUsPVUe
VMbsy3/sG4ra3JuGQv4T8/5DPyDwaZlW2vsoeQfIK3ZfrYeQPTEwqEdi13mVNHBHwDSsEF/OSKMO
3JPuORY2THjYi47SbfIDVsbEh2iBrftJz3kuvYCPWlCTftyyNyYEkRFjHEL+QEkfERX8jiRwtaxd
Vu5HlY3J9PwNg4TB9zkFtNRECOJ8vYKLuxZ2N2Ym5JPaa3Ww1OHkW8/dNUQ+z/YN2/8AyeT6k6cu
BJucM2+S/sYcGFhJIHa4u3KbC3WL3oEcCL1k7XjxSS+9QvA/dKWIWVSt9PIaXbsbPbAxOWxd+Vp7
cLewND5mFHI3KebcZyQeadza443sbm/lNd1hwRwR/VjULx83Q91xbSblKPZHERg/nN5ewU00ztJK
5LO7G7EnrJPwZ/8Appv4ZqIfZ6HNkTRxL2yMFHymrybjAfJG3eHTyJev2cksx/5cZH4+Wgdt2TNy
SeBZORfSoer4mwpF+/lB9bR1d5sPAS12IAYqPjEnCnhXeJJ1ja3ewnu0JHZy2uKTHy5Q+4REpKT9
Jhe6k/EejvIHAbpkn08vRbcPEu4R4iBS0cJIM0lupUv8Vz7PlrJ2jwajbXtjXQZkZHfsp01bUj9G
1Ycu6ztmTxXyO9lJY94luX/ERSvOjZk4+kZjdL+RQALeerY8KRDhZFC+odLu4bPuMwPcodQo+sw7
KfIyHMk0hLO7G5JPw5GNHFIyTRvC0kaMxHeKR1dYpMPG285rAaTSgwKficj10f2eFiE8LnmYeguK
/nN9WG/VAl9POFjrlzt5zsgnj+0sv6rc1e3FLMesyStc/q8tBU22A24F0Eh9L3NBY4I0UcAqKAPQ
PgM+fMsS68i8XYjqVeJpseG+NtwPsxA+244e2R6hp8G5beHPu4GOQl9BeGO9Ke0Dob2hFiNymPpt
8Lz5EixQxjmkkchVUDrJOgqTZfArJuO7j2Zc1gTDHf6l+JHaf/Wp9z8Q5j5U07F2DklQSb6casvs
g9fUaUHi0RN/M6fkNw3Tcsp0YTtFyRgXuoB4m9gAbDSj3pnnv9dwtv1AtezgI57ZS0nyMSK5cbEh
hXrCRqvqFWAsBwA/IPjbYVy83hzg80KHykH2j5BTZWbM00zfnMdAONgOAHkHw7i//GTGkHxQonrW
k8w9XQ35eobhIfT8D7t4jzExowGMMRYd7Kyi9kFHbNm7za/C41WFHIkc8LuRa5rmJu31iSWPnvXt
HQUOsDqqJSLAwP8AIyfkNy/1j/hH5I5OfMsMYva/0mI6lHEnzU8GCzYm36ryqbSODp7RHC/1R0Xs
f8zGga3pHzVGfsjoeIVHEZrE/GWrc96jj76TBx5JkjPBmUaX4aX41NuHiHNkmQOwhxibIoDGwCgA
ACi1/NR5hdj8tXXifzeulWIXZzYKNfVWN4l3HbZ4tjkjaNMt0YIWZlFrkW4i3HpGbMnjx4hxeVgi
+kkUz5++Y/ei4SNWBu3AA9mtZO5YzCTEy8gywyLqrBlU6Hr/ACL42PbJ3Ead0D7CH7ZHqr3jcJjK
4vyLwRAepVGg6Ut/otBjlPNy29YNR/dHQ8SP+c2So8lgXI9deIi4LD3GYWHG5WwPxHWpG6ldrX4n
U1fh20NPNbjUKbbt7x7fde9zJByRqp4ksfJUWZuEZ3ndVGrZH+SrXvonX8dSpEnJFFJj8kcY5bDv
kFgBbt+C5Nh2mml3ve8aJlveJJFeTTQ6A1JH4ZxpdxnW4V5UIQkdlm7fLT4+1iHacduDRrZuFtDx
+WmXcPEGTIkt+dFYqPkNBsiV8hyRcynmPHy1snIeYBSCfLp+Rzgx5mGRKC3bZz04edSA+HAVJGhA
eQaeioj9kdDxMv8AzoT6e9rxEGFx/T8k248ImNSOouC7afpGkxNuxXy8mYhUgiUuQTpwFY3iDx/7
eRcPFtYFrLb/AHh6vNUeFt2NHi4kQCpDCgRQALcB8GbNcKIe6lZiQAFjlRiTfTQCvddixn3XdLMr
OhXuVcXHbfjU0M+6jB299Fhxbrb4wBTS5ubNPI5uTNI739JNBWUcnURQUe0B20OoVzA66aisTwxu
O3PmYWNfkkBW5J89jUce4YOVhux9t2K8oHy3oLhb5DExtpO6pa/nNK+Bn4+Sr6r3UqOfQD0tw/1M
38Q9PClduaOXCi7oa+yFkkBHp1qE/ZHQ8S2/4sH4ZK8QtILoNuyuYeTuWqPA2XGf3eaY8+U4PdRp
zG5YgaWApZsaBMzf2H7bcXBNj2Rg3t5+PQ8REi49wn0/QNZFtFErm36RoG/KvGwrQcOJ7a8o4dlc
OUDsrt9damw7OurXBt8lFuf2V4dtFnvdToaA2LxDl4lv90JLr6CDUcW8ZJ3fDUqORgnecqixALAi
kxvEcL7PlEDm5ypW506yBx8tJk+Ht0hzY3F17thfT4dwI4HJmI/+Runs32sNR/1pKhPag6HiQf8A
Mx/wvW+94SIhhzGTl4lAt2GnaNKw9t8GZOPDKEHvWKTyTNPwcnmsW1vw6PiAWv8AyE+n6BrLIYW7
2QW/TNG4ueq1EkWPZXOBfttTAG57OulKIefqNWfRhV1vc8a5Qda5ZLUrAcwP51d4Gup4C9HvwH7N
NfTSSeHd2nweTUQo37P0HSoto8f43vOMhULlxIWblt7XAi2vnpcnw/uatMQC2MwPeAm+lgOq1ZWS
BYTTSSAD7bE/P09i8uLb/qtUB+wOh4jHa0B9Cmt+F7f/AG/K1/8AZapMjAypcfIjlciSNivByeo1
Bjb6sW8bXEArmW4m5R2Px4dtDHnyzs2abfs81lEZNrmzj5wKXK27Kiy8Z9VmgdZEPxqSPg38kXHu
GRp54zWVZdO+k/Ga5APbPBeJpRtm05E5Ygc/dtygmkydxK4GNKFYB1KnlbX863VTbv4zzDz4q8+R
PKyqrMBzWA5uuhtHgvblxcbHkIXJAALqDoRbyUC4vfQny1pwq5a1uqrDiK7pdbVqfgsBQN7G3Gkz
9kzpsDLTg8Llb27QDXh7e97yXy90ylyTkZEhuz93lzRrcnsVQOnsX+l+XvWqD7g6HiIdpgPoUVvi
9u35X8Fqye0Sycfvmua+lXvYUo8N77lYCqRaOKQhTbhcUkW9CHeoFsCZI0STj9ZbE+ms/YYvDcsG
7bjA2NHL3qtGDILE8up+Wo8mbF9y23Kbve/luBZyTxtbgajyfEIG65idpYr29dvVSwbTtsGLGn0e
RAW/WNzWTuWWeXGxYmmlP2UFzWdh4+bInhXDk5IMRSFViBy6240vdDRbG3ZR5dGPEdVBgw7w/m1z
yjXqrvIvjFGSxv8AJR5SL1Y8K5VFzRBoW0rwwASeVMoXPb75Men4fk7cdx+rJf56g+4Ohv6nrWFv
Sqn563pRqTgZQt/7LVldX7WTj981ynSjpfSkANm6xXPxPV1VtGOwBRslAQdBxrBx0Flix4kAH2UA
+H+k7c4XM3kPG415uQWAtbq40e8tf6RI628tAyOeZqsTcnqPGuVdWHWau7E2+kK5omIXy1BB4ywl
n2ab2ZXXQr5Taod08H5bYSTxmRJIXDq3Dj7PVeu/8JTJvEYuOQkB+FxpYH5K5N/2OeC3F1BZfkrl
cFWGhUixvV2Bv1VtCH/dT5af9d2+fp+GT2xzfI6f31jn7A6G9DqaCJvQsYp4ZVDxOpR1PAqwsQay
948IT/0/c5AXTBcDuS5N/Za4t5j+tTY+/wC2yBNSssaMyEDrDWII04iuAFuo6EV7QNxwNANqLVsz
R6fzKXPx1gkm5OPFc9vsD4cDZ5HPucGN3iC5sGNr+urjrpRSgDUaXrmPtGuFi1WbhRXluh4GsTZc
vId9h3SdIpkkYlUFuUWBNhUWVjsHgmRZI3HAqwuDRTc8DHzFIsRPEkmn6QNTZm2Idp3GS7AxqO7L
E3HCxFqkysaBtz2ZSxSWFGb2V69PJWHEV5Hjy8pXXUG/ODrfz9Pwv9yf8cdY/wBwerobr5cWM/gH
wvh7ljR5eJJ9OGZA6n4j11Nk7EZNn3CS7WBMkJPULfSHn9qnzNrCb1iJc8uOxLgDtBF/koxbvt8u
K6GxLC4raeRgCcmO2uvGtvvx92h/hr8O270RbHmh5OfzW+cUQpuE41zeiurvD217XGghFzxFexoe
urtr10JcY8siMHRhoQR1itnycjWfGiWF26zYX1+GTCzoVnxZlKSROLghhY1uW07FjLi4AzJ5BCpJ
UMzWNrk24dPwuw4mOYH4nj/vrH+4PV0NyP1sOM/4lHzdI4++7bBnRn/ioC3C2jCzD01/XNmwm2vc
MH9uiwMWibu7k3DXP+KsFAbhceJb/dQD4Z3w15svaw86gAFiLA9fmqU8pTu2s4OhFjwNez16kVfr
FW6+yvZ+lQj9JrlBuRQ5DYXsamEl7JKgW/Z7fDobnfj7zL+M9Pwtb6k/8SKsb7g9XQyfLtw/ip09
zH/izH0ITWRtm/7ek+1Y8zxIIybhQ5Gha9tB5qRY89cDKf8A3OQwHXbjp6qEuJPHPGeDxMHHpBNS
4mVGJcadDHLG3BlYWIqTf9ijebYdyYyyKqG0ZtcjTy1zDXm6uyrDQ0zg+1QJ66t20D1njQI+iLVh
yMpVsrlfXTQAn5+huWt/5iT8R6fhSfTkYZKAdd1aE/PWN9weroTW69tF/wD5R09z/wBJP/DatzQr
3ZGTMeTqHttQkDNFIv0XQ2IoNsu8yFRxil9saC3aKih8T7amdCoCs0QVSbaX01o7R4khfAWZWjdc
mMuoLi2hFrVK/hPMXM22YlwwN+XXQUHANjXKwIvxtQBPxUNKGlxwI/urB2HAj5svLkVFHYDWy7DM
oXIw8ZEmC6+3xNz1/A0srBIkBZ3Y2AA6yanx8XKG775HdRi445lDDTUgjrrO8W7njrjPNuORFDGo
se7UI121OpLHh0/CR7ZMr/sVjH7A9XQfy7aP4vSORlyrDCvF3Nh2/HX/AOrwZglzs/8AlSY1MhHf
+yNE5rBr8TpW6AsQxyZiATzkAyNoWsLkdtqv1ddMF4eahy6dprkYBmvdja9AhbJw5evTtq41PZQL
G5q99eqi0h06qxsDbYWnysg8sMcY5mJNDxZ4pCybyQj48L8vNESvXbhY+Wnyt33KDFgjv3jO405R
c3AueApofC0g8Qbkps0cYbux5yLeusiOHcDtGzzAj3KBnAsTccTpYaU+TPIZsiQkvK5LMSes3qRQ
bum45AbW/FY7dPwmeybJ/wC1WN9weroI3U+3W9Eh6DSzOsca6s7kKo85NSRjIGXuBVu6hj9ouRce
yBx1HKSdFP0qfEwGkwNtc2VISe/IuSLuPo8eCW85qHeMuNlGO65JZgb3jPPck+at2jU//VTH/GaI
J462o3GnVViKB5bVp8lW4Crn4LdVPu2TtX9T3VdMZXA5V18tPt21QwbMjgr3sBYygE6WNE774izs
8OSWjeZuXXyCwq9/pak8aB6+3toNJcoaz0T/ACBnM0Z67lRf1dPwp++yP+1WL9weroY3lwGH+Nj8
BZiAoFyToABTPn5yS5VyqQoea7DiAFuSRcGw6qkwvDsZ27b2Y93IBebluCtl1VSNRf2r/Z4V75uA
lkeZuaWaUlnY9pY3JqObLhVpRYm466zY8SJUK48ltOvkNN4h2HcTFuOc0kzY8zErcsfonhxp49x2
18mBfo5EJ5lItfq40IsmMxPws4t66uLMOJsaZCLL1HhQCm/MKsPpVqK1FWGgoNchTpaudOvr66Fj
6a0a7dg4VfqNW1NbjFf6GUCVtwLBv7un4U8k2R8vdVi/dHq6G2La4lxZEv2WDt81SZO858YkQaQq
wuWI0W4vYmxtT7T4NibDwW9k5LCzNroUTiOAILntVkr37c2myZpiDJPOWdiOPFqjn3CINILE3FLF
iwqvKLXArSs//Ty/gNbf9xvxtRimjWWNtGR1DKfODTPuG1JBkm/LNjhUsSb8LEVJJ4Y3URhrlUkA
U+bXT5alj/pb50CaiaMAggC+hBsaZc7bZ4CmjFkNh8dE2PN1ixogLagDwNcp0oa8x+rRDgBR21fQ
A0Aq69VCPkvfQWFL7tjSYG3Hlb3yZAsfJfU3J7PJWfsEOVJlTTTK85kCrylQbW5Sb/S6fhT9/kf9
qsX7o9XQ/q2Cf5mCIoqFeYHW4vwqSfcnmyWLnlaS/KoPEKosFGnUKiydyjBYWJBFLHiwKpUWuAKs
BYfDnj/x5fwGtv8A3Z/G3QKsAQeIOoornbNiTBtWJhUE+cqAaaSfw7jgt9IKumvXretvn8M4wxIM
vjCg0tY8fRRDix6qsOI66KhdRwNAsPPUeLtmLLkzSWFlRmFybDgKifcsQ7Xt7rfv5RyvbycxFe8b
3Gu+ZnMGHer7AIFuJNz20uFtGHDhYqABYoECLpp1cazexu6bT90vT8Kn/wAif1R1i/cHq6Bx8lQy
HQg0Xx4EDHW9hVlFh0clSLgxuCDwIINbd+6P426Pe5k8cEf1pGC381+NFcrclycrlDLBDcsQxsCA
AXI/RravFO0yA7WmQ+Iq8hiYSRrzWPPrrfsqyQs7sbAKLkmv5TapgGtysykDX4qgyMwRYcMmrB3H
MB5RofkqCfxBlS5eUn+YkLEIfMT/AHVFDs+zQRNEABM688h5esk9DJ+5F/DHT8K46n9iBPJy2/OL
xAn0VjA/VHq/Jzfu3/DW3/uz+NvgM2dkx40QF+aVggsPPxqSGfc1ycyO37CLmLe1wNlDPby8tPi+
DtsMKMGUZMw5GvwVgoLk9v0kotnbjld3Ib9zjlok4WtdTzEfeZqR8iJlVuNxUfgvxHj9/i98+5AD
Rg5iVNL3GvL2UjYexwF4zzK0gDm48nChHjQpDGosqRqEAA8gA6eT5Uit+oOnsWFBMks+EjrkxqQW
jaR1IDW8grGA+oPV+TmA4lGA9FYuNvKynMgXlMSj6zFgbC5tY9lNjeENs9yV1sJ5rc4a/YpYnTsZ
KaTcNxy3WVie7iZols/EHlsWHkYtSNkxMqntFJJmoGIsTcUojxkLL5BQWGJVA4WFRAaD3P5m6Jea
VI0HFnYKPSa5pNyxyB1RuJD6EuaPe5wYj6QA5LdevelKv7/i2vY99lwRkE+RWc0+/wC3SxzYmRZY
mhcSrZABbmGnV2dF8vNmSDFiBZ5ZCFUAC5qbYPA4Pcse7l3W3tOOBEYPUfrGo93zFduZ+8eR7szG
9ySTqTUUJ4qoH5MjtFCVR7BOvppHzEDMONxSiLGS6+QUFhiVQOwdCLe85f5FMQK73Cj8++p0vwp3
iz8R1S/s+8hpbjq5I1Y/LTvtsT5NrckUeM4J/SlaMfJR/pO2ZLsdB3xhhUfEiSX9NFNuxPdgxu3e
yz5Fx2WBjHyUTFlDGD2uIMaK/wCs6O3y0I8vdM9kJvyRu0Iv5o+UV3+UkskrcZJCWY+cnWgZIyKl
2LIFnOQ89vsyIg+boHJ3jIAndS+LhprNMRYWVerU8TpXu1mh2jnvBgRXCAcxIL2+kahzt1i7Gswp
IMWJV5QBcDs/K3sL9OTDhF2ZbU8jLozE8KU5A+SlMqA243oEwIbeSgFxk0+yKHJipp5BVo4FHxVp
Go+KmAFgYo/n+AsxCqouSdAAKbavCHJuG6nRswWaCI9Yt+cfJXv+5NNkyztzSTTEsTzG549VzwFR
TZMKtOADqOuhHEoVRoAP7LYi9aKPRWnTb9xH89Nnb1lpjxqLrHcGVz9hL3PDqr+lbPFJgbITYQRk
97Lc8ZGB+KwqHM3OIiPQ2YVHFjwqHUDW1WHD+3zb3hAPMMcRorXIDqSQSOsa02Rusk2U3OVVpL8q
KTwVeAHmqLKzog0wAOo66WHHQIqi2g/2C/3aP3qXzdP/2Q==

------=_NextPart_000_0083_01BF5795.06C3C4A0
Content-Type: application/octet-stream;
	name="anim2.GIF"
Content-Transfer-Encoding: base64
Content-ID: <007f01bf578c$a4ee93c0$0100007f@ftid33tp9h>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhwgE9APf0AN8YH98aIN8fL98fON8gIN0qNe8ACO8PD+APEOAPH+8AEOkAHO8PEO8PH+8Q
D+AQEOAQH+AfGe8QEO8QH+8fEO8fH/AAD/APD/8AD/8PD/AAEPAAH/APEPAPH/8AEP8AH/8PEP8P
H/AQD/wQBvAQEPAQH/AfEPAfH/8QEP8QH/8fH+APIO8PIO8PL+8PMOAQIOAQL+AfIOAfL+8QIO8Q
L+8fIO8fL+AfMO0QNe8fMPAAIPAPIPAPL/8AIPgAL/8PIP8PL/AQIPAQL/AfIPAfL/8QIP8QL/8f
IP8fL/YUNvAfMP8fMOAgEOkgK+AgMO8gMO8gP+suOew2P/AgL/cjN/AgP/AvP/8gMPkyO98wQPUf
QOUqQO8vQOs1RvsrQPgoUPY1SfA/T/8/QP8/T/A/UN9AQOZMTO9AT+ZGVO9PUOhQWO9QX/hATPBP
UPBPX/lAVv9PUP9PX/BQX/BYWP9QUP9QX+9PYP9PYPhPa/BfYPBfb/9fYP9fb/9fcO1oau1rdO9w
b+9wf/lka/9vb/Zmd/9vcP9vf/Bwb/Bwf/N6cPB/f/9wcP9wf/9/f/BvgPB/gPB/j/9wgPhwiP9/
gP9/j++AcPSAe++Aj++bm/CAgPCAj/WPiv+AgP+Aj/+Pj/WIk/+PkP+Qj/Cfn/iSkv+Qn/+fn/+f
oPifq++qmv2gnf+wn++goO+/v/ClqP+goP+gr/+voP+vr/u0pP+wr/+/r/CwsPC/sPC/v/+wsP+w
v/+/sP+/v/C/wP+1xf+/wO/Av/XFs/DAv//AsP/Av//WvO/AyO/Qz/TFxv/AwP/PwP/Pz//J0P/Q
wP/Qz/nZwP/fz/PZ1v/Q0P/f0P/f3//f5P/jzPDr3//g0P/g3//v3/313+/o7+//7+D//+/w8O//
8O////Xq7f/g4P/v4P/v7//v8P/v//Dz6vD/7//w4P/w7///4P//7/Dw8PDw//D/8PD////w8P/w
////8P///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH/C05FVFNDQVBFMi4wAwEA
AAAh/nlWZXJzaW9uIGZyYW7nYWlzZSBERU1POiBS6WFsaXPpIGF2ZWMgdW5lIGNvcGllIE5PTiBF
TlJFR0lTVFLJIGRlIEdJRiBNb3ZpZSBHZWFyIDIuNiAtLSBodHRwOi8vd3d3LnZpc2ljLmNvbS9H
aWZNb3ZpZUdlYXIvACH5BABkAPUALAAAAADCAT0AAAj+AEsIHEiwoMGDCBMqXMiwocOHECNKnEix
osWLGDNq3Mixo8ePIEOKHEmypMmTKFOqXMmypcuXMGPKnEmzps2bOHPq3Mmzp8+fQIMKHUq0qNGj
SJMqXcq0qdOnUKNKnUq1qtWrWLNq3cq1q9evYMOKHUu2rNmzTouU6FAkxIkSJNbOCBFkQggOQYJI
QAHiR4gJJUCgYPsX4Yy8JBLHLZFiAooZIIKQ6EC5cuUgDTALBMGhg0AOAgFnEPFjBmMOMyjfTbHW
suUQHkIwCPKjg4TKbUO09pzC89oQwEP/Jgi8tsAOrCvLrlDiAuC7JJwP9m1wwgQGnjsAB223td7A
ag/+FH4YosIDEAJ1Gw4BAgTdvxMcsJ4gATTCvyQkJC4xwbXr0AwMVFcDbTUAVwk77MCYBClQcEFj
cHGgFkRqEfZWCcCpx0Fv/nXQQxAlSADCDkFop1sQoAHXgGohdBDEDh00QFcDdlF31Ikp3BViCnul
AEJcHaDwogfu/eVXBSDkGNxBLeaYAge6sQVBCoAEIVhC7IHQwAwTbMjBl08yMEQhgZnm2QnBdbCf
QompAOUQBFHWm0BFUAZiYqDlSNlnrikWV4lsrVUEawykkEJpEwwRAgsdCPHDfSXA2RlresrIAWAY
/sVWCg9AFIIGg4JqY0E5BliBBw8c8UMKDnxgKHr+kMLGHoYI5Qhlhu0JlgIDNdhFQggfdGAdYxTk
OFCLnpYQhK0hHnfpW/YZhAIJHKCwQRh3/ADBBD38cERonO1waQkcuOejhMKylhQIEjDAwQ8wAqFD
EOyFIAGGGYQww77D8sACkUM8hxAIGTxQQ4IwBlGEXergwUNqHaLoo4vD8jcBiEOIQY8RH8gWhBAN
uLdWbT/01+EOpilQAwSKfcZYug3AGUIR7hkohBVuFNJII5NMwogbVmA2gY9tRdpACvTCWldqG/g1
hAgkZHBfZ4ytNYEGOyzBQgh8pUDDB0K8GEQGiznEwRAN7KBtgAiNEFleIQyxgRMbGBoi1QclNrP+
DSwY0UOHwipbp4lBDKEBuwwwEMOGC5fggRE+hOBDAhUkhsK9D4GQuIQlAtEBnI1z2KEEExzRQRWm
WNIpA0X8oAFtP3DghB+dUMIIHR2cUC6HJ2CgVOFB2EAMO9/A8w42iyTwaAk/yPDMPPKA880882ij
ipnvIcRCDs+bA8482WAxbRHvxDPPO/Skr3768LSvvjzpw0+P/PDMUwIKjTnzzjztgwOPOfCgRwDX
p753/AIXkxjDXPIVLYGsaDMuYgELDIEKaLxjgMabRzvalw1XFEKCJYJV4ChzBA0UgBjqEOA3sHGI
ABiISYYCjgWaYAn+mYMe6whEC64xj3ik7xv+0nADCyACixTK4x3rgAUNEFIEF4ijePMgBz2qYQYH
tCUxoxqIX2TADHaA44gEJKD8zGGObejiEVzgkgJkowIJaAAwMSAGN77IjWskIggbmJBDCrcD4REv
gPBohwDDGMZ3GDKAj7ifiEBgAtQUohjmM9/+whEKJ5RAA8LSgLqQwoEMWGAINMjFPNKHB5QVQQOo
AYENavEOd9BDkMfAQXmw04EGEmRaO8AFON6RjiT4Zgfukwf1hjlMAbrPfewgJj3Y0b7Y+egGvZgf
Pag3SGJaE34BjIct8mCiEHGmRDtwDAoYoARJjMN/BOQfAds3DkkogQEoyMAEFLQntvzgA8P+SN87
7lAED1zoIAiwztE+94gezgMODagAD2LxjS+OwwkfQAFEflALcCyTEadCyAU6oIV3CBIe37gDigTy
qyyS9AJBgEEu4tE+a7qUmOiLxztEsQQghAw0Q2jPDlqwC33GAVgnuABELgACDYBSlPSwKDWn+VLq
yeOp8YCfIkxAghgUgQQNYAMrbyjTQ8IjHs04w6M8ox6kYOoDPOjEKOehBA7cSwUp2AEIJkAJ+MlP
HV8Awl3QtMmCRKcIj4DfLlbFGiF8gxq++IUvFsvYxS6jffBYRi520Ytb3IIXvPDFLYqBDXq0IAU1
wAARIME/eEzWF8vwxS4ay1pqwk8djoj+gWcYkKYf1MA9h+DhF6eZjmCI4hGMWAQnXIGMcaivftcA
RAgyUAG/IIcy9yxADY0HA5q90CC7Ss9fInAH/r2jBg1wQNaMC49soMgBEJnAKeBXCyNgQAUIIQEL
+IA+9jlCCHOlD94M4qIQCIG06WMtY1mBWV6w4hjYUAcAkyoOMhxtLVAqwQZ4MIkAouMGLZpBXxkC
mCCgVa306EYvcmELX2QWGQJeLDJqcQtkKCMemugBibwAA0d0lh7jgMQXjBCEMbxilOBohhI80x+l
3CUCKCiCItbxDnawQKIaSMyjZgCJ6CU1fcqwAVxIUOSDhDMIjxBgLoQArCbs4BpOQNn+QTowh3TI
Ix53qGWNKNOWDhwhGzQoGQUswAh00CMbU7COaWw5EJRBARTjuCA9/LA1BmmqAhrIASnUUV9sbCIN
NghUB35QhDoRQQ6iuPE71EEKG1igAnbRDeMsoAl2JFMHIQKRQvZUggbcwZircgAQZmAKqNpBCBHR
gjgCyAgaYcogEhCCL+AhD2bLIxo58Cdy6pQQB4WgEcm0X0KQwx/+CEIX0IOHNApwlx/U5gEhMAIj
2LFMCEBtAmVrSAgugGQlr+Mb41gCCOTT5TXTiwNEYEQjZrADJMAiG82OhzGsoGG3NsAGgogeOkDB
AtCYdCjIkUAIgHCJ+c2DBu8CQoj+5DoERbCDG7l4BTfgwY5UkItBxy7IXa6dVF3ImgQi6MIiM8Tz
ELRhlPBwg49q1BrdTEAM5QLNDjrRbHb0IEqZ6jlwQAA1DZxhHAEkhg16UDktlUAERCAF++YBiSuY
Zj+ZgRG54jKBK5DWovQotQiWFaD5dIAS6ZtHEBhgguUZZEMDgW4czkcPD5BgBJKxAvTeUQu/QKQQ
7H7GBERAAb8XBAVtSKY0HMHueeQhBQ9ai6wN8qi4aGKU8pD6kpCzSZRGotnqsIRnaGOdv1RCmjyA
0g/izZCMb7zj8viGD35AAfSsSvVG59oBnoAFuISgCsb4YjOWgCycyigYKcxGAHz+dF2kuMgzYU5f
CMo2mRmQQBGjZEUBaCHAiYeTeaZZC+kQ5BkSTCJ9u7g4QuCgvjjofy3HUgL3lz7HQSv3kRk10AOH
gA7ywA2FMAMEoh0IsAOiIEDz4AxsMHoN0QFiUA2j5A6n4Bf1MQRBIgE/MID0QH8R0Qbqox2TwRau
EA/+YwUgQBjpkRk/8AA5MgFJsgPQUD+HwBaYwhn8QW0hEAsWtQghkA4CtAsgcin9xl8CMQlrhRC0
dmxzFQSw0FDQ8AP0MhAksAPhRw/jB4AR8X0lMIZlSFKV0W38oYEEwYMkoATMMA9q0AHooRpvOAh+
Rg9jcAAotRRoqIbk1wFypQj+AbYABdBZLBeEopMhx1F/A5h/EMF/6eN/sxaAKFiAZWUQuqEjQmAN
6eMJK9IAtFUCiMAOAJQMUVACbOMQwuIEynBD7MAHvEEZJMAAJ6g+KggRLJg+LpgdcjAP7hAPkwCA
vhElheEbHSAINzQNVlBrtUQu9oIhFRACXJBC4vAEM4AI6aMOctAAtdF9UiiAVXgQGyYcIRAG7KYO
QVNWYUiIZggRg6g+awgX3URbHIIQE1AEEhAEBcAMdvAo6vEka+EG7yAP5uAGuCSIJZKG9liIO0Bz
8DBYJXAG55BU6BAGJVAEKQIcvYEs9od//2cQlkgPmLhtmsiLANiJMid6KdD+A77wRbNwbB2gBFKE
Y1sAeumoEBlwASFQAFhHD+IABcixIdQSBJuodr7YguNXS0UwA9EwP9vILpjiGVDyhOwyA7pwRJDw
AfxhKGSlcRxQAR2wCvMADpfAFkQgDu7wDrPwA1uTAuQYJ1N4jmvGbXLiGSAABAk5D2nwhSQlhhE5
jw9Rj+JXiBaXIWtSHeiRAjNwBl0gLJ9DLrrzA4bADcsUBmgCh0aBmGRYiIOCiPAADCHAGn2QkH82
BtfVHyUyGHAxiSVZECeZkla4kgTYkttWF+cxBLpED8gQMq1BCQHEDnqwAYEhERlwAiwQB+zQbJOw
Aad5VQiylLNZEL9ID8H+yAFuYgjg4D2A8COAoXadESMkgAIcYAejxA5eABz9YR98uRZRsFZWMDGg
0D7sAAaaRGh2aY7TdJuM0SJysiFGMEfzIAeCCReEmZiGCYsPqYaYg4+YUicMoB8J0RgpEJUQYxfs
QjpFEE04xgMMUpdFAZr3+IIloAg+FAwk4AAZ0AHe2GzNAAU6gmr0MhmxSZKV2H//Rx26sYm6yY8z
IxA6IA0C9ApjU2s5IA7TpAsw8gBFQKLbBhgT8APAAD3TkAOe0QAkkCPWuYJOORk82AFUcA7tMw01
cJTwciBeeD89gAsChAofQFs7cARxEQIGsiE9sAkWVQqv2QFdAD/fUAr+jxJhAEqF/zlrVxgYZ0CM
8+AFCRqPhXmdBWGihViAgJECvHcs1HYAbtI6/fEDElAELBBxxkMJLEAtm1qiD1qYbLh7mjA/u4Ae
F5BkpNBSuqAEG4Ae8/SUOUoPlPgQtdmjuJmCQVodc5ECH7ABb5BC7yAIQYCeQaAH67kH1wgilscQ
Aooce8Bu72AHFpMeX9qUwPiUjhECO8Cn5UAPaaAd76IgWLRlX5BC8xAGtbQnzwEYvwIFTDoPVeCP
uVgCP1Y/XPCEKumf2maFtCYjHwAEqDA/2PAh8LigodmgG9iqDMqGrUE65hZ//IUibyEBurMnRaCL
Z3AN9PANvkADcCL+VA4Jfq6Kj0VwAOG3Cy3ikSAgBLvgQ++gCVbgASjQqzg6ksBKqQIxrJmYHgLI
kmTFj3bRAC/ABcjAP9NABQoiARQ4P9lgBBNwjXgIEU/yA0jCAuuQVKBQIstCGeP6ENkZjNxWAl/A
hPIACzmwe3TRJUIiEEFQCsxGCx1wAJsxGyVVAXF1evKgC49iF0OQAWegDvAADpvgsYeKl2umGzRS
AyxwA5SQlvQQCCSwLGBIsWVotIGHsRXLhoPCIzGZA4DAj0/SGFEKgBywA9szk/GADV5wVdnxshCZ
sRJqf/BzC8ICbPkBBcqQPuwACEM3kQBItMHqEEh7sLQCpE17ELX+xwB0MAzqBAl1wwAn8AO3IEC4
ADIu8gAS9RAi8AAmQgO70D66gCGA0gFr6xBt66vs8SKpwGzzwAWiihcgEhkvUARUwEzw4AfakWoY
kqHlga431gbwRgI9YH5BEAzMlg1EQGtrdpeJqrD8MQVsYAnSMA/TcwpAMHcTK4+kexyme6KVMS2H
sgbaYIWs0wFG4Hhr0Vw/gAvfQA/ocAYlkAEogIO8K48aK7+jtAtb1hsnAAJWgA3opAfW8SSfSAI1
25MJEb0AOr3TJA+QQAmSwAiZMAmZ8AiUEAmZkAiWYAmPgAvUAEjzAApGZxshMEr0kAmeURvd8RA8
0pES4AGbAD/+43BVgKEd89sQ9TsZoJG6aQA984AJM6A7RiJnIaAJFiUNB6EXIDJOBUUPwDAFPZCv
V7UG86OWISACH1AncKMevoGodExIroy8i4AkRfCQ+voD3sigKSx6MOtxOyxNnBs/9LA/ELFAE4AJ
ARQ+JwC4epLLOWGpYJgdiIrEQHIXFTADdjBs8ZANYeAxrME1NUu6WJzBSnt/4PA93nVBTzVA8fMN
PhQP7HANe0AvvkECP6BOikAuc7KqCdGlmzEDnfCNuwdvhMyLTMm2YaodgkICToAMAUQNSdAd2qEd
DHAFNxYIl/wo7JIDU0kPVcIjKBAlHCAE0fBU2CAu1NEfqqz+wa0cRvLDPlfGxVUQAiUUqUXACZMq
EYj5PfpkgeXsP8EEEQ3AAScwBuUQSGhwAleJwUnhzEUczXAxGDfKATpgCPHAUtKwBJ5xL96cPrcQ
EeFcjlosQMm0xdNkgT7EbOBQDs6QCofwAj+ySe9Cx4xALkqbXkYXGbc8D4nbGoXMEIdMZKrRAX6A
Pu8wCXiocWpySpHAbNhwBZc8A/20A4SQPtHQBB7AI+3xJCiwA4vAP+CACJJxL8y4uwirC6Z92qYd
DJYVDKzwC8+QDerADvuTDXmwAxUwkfO8Ayg4ujiNsd1QC7iwC7qwC8TdC8RNWcjwRGBbg69gUY8Q
Agcw2k3+wdT4uBZOrTcxc9nMQwnF8w7KsAMalzQ169U8mrRaPA/lkAdyYAdtkAZtEAdykAbunQfT
0EOfwAKaJI6xIyN2AQT0CscS5WES8QF6MRinx3I9IBC9QbQpWND0e9DZoYs/oAQo2w7RoAQh0h+3
YQTS0GyawJ9BMAO7ZwTRNA+Z4Cp10RuIEQEd8AzMNg1GECFd2oarvFbWceM3niGG8iUlYAWT0Fm7
NAhhKKCssQOIiMu9vcvkoKUw0gE80AFAAAQ/0ADy0gXPABEiQgT8Mw48gCytUYBKQd04asTAeiAp
sAGA8SNasgqDhAoKYxcpULMxxxBfXakruT9ytVwkUIP+cnLmjFC26RAGYvkDK5AigAEEFDwPu7AB
+/G2DpECbxQXG6AL9OAOyZDgZtjXC/HXHcmlStcI+qsHg6JxGGIIf2kF+qwgFTB49CANTiCqM2Af
z+EXxBnMjvi6GwIiNT5NgJMX0GVuCjMDSaAMT6UOZ5C6eyK6QJLkvTsPK5Akme0lKOAAJVUG6QUC
eYA+rrAjbegUYg7NRwwXKN0BFeAuzNEDx8tynbADEIAck0jel0is42yBIKIgyDgEhRICAkALX2QL
NKAmbrh7zOMJ6TMONwBvHemSC+GenJID1JA+oFB69q7pCsHplHIpHfAE61qRsIbYO2AM7TAPpVA1
6Nj+AVwZSLqgBnSQBnYAB21QB3LQBnLABndACN5gPM3wAu5KLtS26/MAOAEFLYk8AxLwAGcgg/SA
C7GeHGF45BWby6DJA40BGgrjinFBAhoQAkgAETDCCAIkCOlBa3IyxDE75tctKOpxAoVCAkvQDKME
W2jjvPCOkvIe1vKAIiiTILoDGBvSAWegv5QAGUxgceLCPHWwVoAQ1AZIIUHSAH7AyHWgFmE4hQSd
wn8N51CyMCFgCqMUD2CQ7x2wBuijDmNgsQq+jkCnDikURvOADugQRd/wDeWzBsoTiaTNyn7iJwfx
jwzyA66wQfQwBAigLGqi2zd9hqYrV/1xHQ+kMDP+I/z0SASPEEB2sHcYrIdhvsKXSubSnB65LoT6
MQbi0A04hgUo8s07Gu/m/aMWyDUlQAEckB9F0x66SAqynQ1OABv8MTMgYJZEIIoAQQ/XDhBFPFQo
kVDhQoYlSIQIgSIILnr0rNloIAHEjoSTKtIrsaNDQ5IL23zsEIJEhwkgUnAI8WFCCDLs6L0rxWJG
hx3C5sHb1aDED5IdDnRARU9eRXAfnSoF5w6eOXrz6MES0COFw5Eluk6yOq8kRLIcOAQJ8gPFDkFW
6bE5McEriR2PPqr0WlKv1yAj7VZtIKJEiIQkSmxtUCQEh617GQahc60iLCl9E45MAdHxZs6dPev+
HSm0xF96DQxP6ArxkdVdHUCUfJnZzDpw8shp+VHJ6i+inuV8rNNVbwgJChVVjKewQ/GSRCSDizWB
xAQGg0Ok8DBkETx47PSwSMETNdkQHYoUSUmWJd8dd9iBgzeoSQP6CVOApQePRwa65Tv8J4sEEDSb
QS462unuhRQ+YK6hDoQpB5x2lNghAzLoMWeePcILgjC5yjssgy+4m8eTRip5JEUVU1QkkkkaiQQX
7ugBo4aVzBupg/AQ+UgvDg4zq4QfFXLjp3noACC9lRqBJz8WfgBBAhRKIgGFFEgggTniQupgkne6
K+E1nkAwjKSHejjsgyD0+iERTh655JFDPvj+rE4779zMsh8p+SiIKQfzirHV6LlFyJJYcukFRNSB
R55khFBkHnlsEa2z3/Jzg6jqSGqAsBRSCCKTj4oQcjm9gthjHnPimcM+xRDtIApx8ssmBw/i+oEl
CSQA0L9dUfthAgo8WCKbRrGJIoHMREuhkJ/aYcMEEmbAMksJ5Bpsq5g66JCRirAJAtuSgvDjJ3oa
8aAEU+hxRxkWButwggk4yJEBClLJDxcYgoBgB3//9TeIGRoAYIIwxqnIFBYOCK+BcHUswqOKAAa4
iIrPC8IDLPOYpyk2JghPpQ6Om+edNTtAiOJ/0eLpvB1yJSEIUiWeRzGv3g1J5R1iJuKBCor+aOC1
kkAOFjM8j0b6zv+CoPcveYIAYSTCuhq00DIbWnPAD4QAhR143olFk3jgGWZNz06qqI0fGuOUsME6
4CQepQItYqVDd6CInmuegGhpuUC4wA9ymmTmCQ5IyGyxEoZIPIUhhCSrpRqYkQcedPjoVLMSLghh
DHSqOiTLxa7G7IdwNQIVglcaDaqEefXaQRrupAFiC5vAQSSE1zq8TC7GnEhHHnbq+OADMqtFPoQJ
PDhio1k+X4cLAYtAzav/7HKHHuSRb7CEXSV4XAQSPGGXnilSSmmlTOApuQgOXvtge/kNIyuIFBhg
oEtzd2jggRQKZMD8HtIXCTxkCFdjiI7+DicBBuQqaQ+E4F5SEhtH9ChqJSBVQjiQCasEowFDwhpE
GBAeGIyiIuggh1J0AULOnGQpbfgP2xoyNdWgJDykEg5DUHACK6jDHeDoxM5KILP1DKYUjdJbGHZg
FhSQYEjy0mCVOMAAFoTBGfKQhztcoSOIVCoFQsiG3Gj3AbdZ7z9D0ZVhEICFwcEDER3K4ULQxyf2
RYIUTbGGEkKAgSN0AHHcEhIIOECJecRjGA14yQnGNQMGgAAELMDDT76RCt2xhDCL6QBpPBMEDQzB
A0/IBhaV0QAd/Ycuj2DfOzpwuBOU0UeEacALrnOYSHFHKwKa4F4OlwINtORQitFAZvL+EkFiFlOE
HCgCaSCWGMPoSBNWGUYKhNaQBkDJeyVgwBN6QY+mLEUXR/jMb5aSqVUOxyspKMJxKkJEo5GkgF1q
kjrOMMIJVDNcE0DBBlaRH3rEgxJXmMEMdAcirwx0iFeARDzk0RRT7OBPXalOeDoxtniYIgovsB46
tyKvl/BKB2jQBTjAMY0ckNKVDOHABJ4wq3kUY1b0uIQfL2OYDWStCE8IB/v0MBLqHSpYgtyBC3bR
JHYowX28K08yKyIWkmRmQJ/qAOdCkIRVgMMc3yiE2fpCgiI0oirz0F1cTqoQzZBlcWcIUibDsgHi
RI2FDBnh+zBAAzZMkyEn8AALukD+ByJYQJHFBOwDdRRADpDmg0BzX0H/cgtpHgpbjDkCCbigjCY1
aRh08kwaKgIPN4SgbnoR01YiVZHX5UgviONBNPKjC0aCgAEhyFUILnCCHayLHt34hjhWoYYcvMx1
cvnBDnKgBlFgYx7dqIgrdnCCCywEW/95QjP4OY5M5IAIAwPQGXdgBDKcIoXgyEYjGvDaInTPuV6x
LTxqow4rSDMIneJAYjigghDMYBLcUYYSRuJA2HivODvYw1LmQQkWfOiMo3lHRX6wYAYvmCc/KEJf
RhIFQFxDUvQARgWYVh0d/eA48ShHDgT2pAaXWGCIZAkbYvG499rFNkswwgoctoP+GZSYwUYAQgN2
wAM/pKIGJfFAEGqRDXYUQ4+BRfLRdJQQBnSiSe6Ywmkw6RVNVKQY0ilJT9HHLRRcKMFAMZulKhsc
x0zNdaD40jyQUB0c9hcmdpAbOxhhA5EByDAMKMIdsuGWecwjHcMoBSUiEQlKlGIY6egzctJhhxkc
ZiE/KkJjNDCGZEgKHPNYhzSAIQpNTGLQnHBFMBAtN3qUYxK+3EGYsSYkPbyjck06Bj5J0AAjwGQC
RzgcB7IQDXjEwxHEyd8RyEOeG0UEJiWgRkXEkYWWnEwCDfBEgumxC2pXm9q3QEYwbsEKViRjGohm
3zyS8YQMrDJm5WnAJr7xDnD+4KLat7B2vG+h7V3cohjq0EUCEpLueMQDHLOgti52oQt4x5vatji4
L9RBDJzNMAzqOKEgMphkinsGPQ4pweq4I4a/XoclQ4gFd7BBhL2EgAETQE9aRsCDZXxDodmYwme2
w51CkAqBDCkjyGckBoVIQIYLKU8BZ6CMpmQjDDoyDEISooIMpMAGkGjjUp9SFabAox2UsEGYMPhB
xvStOoz5ZCu4OfX8NOkjIqUHNf7QAsAFgQW8I0kPJBACPiRYUvBQxg/4M4P4wfIEBzgCKMKyUxQg
8yxoQTxahhiEHoQAAbJVRsfiQQokXCshExiCxsm+ebdMZRyUEEIPVrKVM9r+ABdWufRHzE52iCtl
KfAIxgyKoIEghJybXqvI6zffFKqTrTcNIUEavPa1RsSx4scfzgcKQAx0FPId4wBEAKTZgRnAQBqF
jMc7sgGGTQ7AFD/hDjvSgYUTRNQ/97OOAgiwiXiAXx2kyMpY5PIBGSDjJ++YxzgCIYAfaIxK5SmA
TZiHb6CHb0gHT3ACmLArhgAEV5iGAcQ/pciPS5uGVwiEz+iKYJGCSqCFPuuzd5A2c6iceZAGV7gD
VduMEIiBQBiHjsE/9kEGGaCTmVCeEqA/+/ua/Nu//rs5haieB7DBG+hAq2CfZzADHkCLAog81Nu8
1UMOb8AFUBCEKMicoXj+iRDYgAJghs/ZPLJbCtejB28AB1oYGBtwhj7jwi6cum8opJsIBiAoCRAQ
AmX4lipAvjvcjNkjghUAAh5wASN4FxUYogawgCFItSBggBrYlM7goxnYgB5ItRSIi8s4o5fwCgiD
gBgwgh1jASEoAgb4E6zZlRSwACR4gRbggU7cATIqAQooCV7ZoxAAAhbwQyEQiU9xnZL4gB2wgS2w
A0aYhElQhEYoBDmwAhtIic+4pxpTExq4AS64g0KYBE7IhEeYBD9wAzDIgQLpwb3IgAzgACFQxR9o
gRdAAgtIgV1Bi1EsxVNMRVtkRVckiQ5xmx9AACeYgLTQgQY4AQNAASn+0QBTfJn0GLbySBzYigka
oIEOcYnLyAifswAjcIGCpMj6aQAImIH3moI90AVP/KS0UIyKpEgdkBkgwAFFkAVxYYgMmAAoQARG
4IIaaC48pEk5kpdVOpyH8ADGwJ8i+IEh4IDe+AEOqAGO6AxFMo+UiyrlSA3l8CwLEIEL+JQfqQAg
JAkRcogDYIwm2pTiUEm40iAOuAAS+AAPuA4sESaSQAEUECTzuAwMwsm1/Az++hSfHBA5WgyzwMkr
+YwHOAEncgm05IADuDPyqA4S0MoU4MqE8MpDmSDG+IH48Qr0IJUg8DmIOBwU4A8Bkp/w8CMREIz/
wJbDhAnONM0qQQH+BqiAQWgACrhCEBCf00QezfzGD3iCQfhKhUjHEEALBunGmkS++0mJHxAKCnAA
xLkOUAmYZEwJFCw5iJiA4ggPpryMH9mUDvgBt5GXfDSC32OIB3gchxmJufPM/7CZpjowRztOIWGM
n1uIAFII0QARxBumzgCRaimBCvgV3byO19iKNakUznAwhigObhGKIXgA8CwB8fQej/sP8xirhFC8
KxmSSKuO/AmCVMPOVBuYzkhPEojKB+WwtDSvMrsMzxqJDtGIEjCCDoiBz2iA6KyAFKipCC0BgfKe
6uBN4OTRFBVNP/mRpRmimUDNY/sMucgSAeEAn3tQTjnRzLgAKzH+LfTsgB5gMNgSCW5p0qL4FADd
gYgozw44uSxDN+UojBvBRc/wEPtYDPWQI+zMTthyTgkaCSyxEohgsB6IIc+00gXD0qXZUmpiTFx8
AIhwCRBoosbwj5EYggd1VByBmOwii+k8jBQQTwijl0fVVEfNRUp0uwKR0A9Aj00lVaK4QlMZF6C5
jODiUeAcEmkSkHrKRwChngibAAhAudzcix04j4QoDzjqihhKCFJZxE79kbScITYjDFBsIof4kQZ4
HB/5kfdBjHw8D2TVi4M0VKGBIs+QoWp5UPIAAdNxHQmACRuFjan0wdQcDGLFSpthVsNwogWN1qtU
VMIIKKE4mRD+SIypwdYE2lSWCQ3dHKJDnFPH0FT0eCJDwcDX0AzjKwzGsI8gaVU8RB+YMIuoSQnF
AKH80YwSRVgmQ7kcEQ4AsUSFmKLstJheybKwzBJYxRIgKdY3/RRpgsyy8Lix0B1BGpIzetAF+wzL
sx6V9KMyWROzAFcM3NBRXZsCotheZc+XPR7DeImZfTQfJajLw5YMZQmUKw/TzMmYRdHLaBgNOkjZ
3B74xCbD2KUJIlK0xRL0Cai0gFhHG5If+c2KDaxZ6guB6Qv3CaAymZL0tNq9cCJQyc4pxYxJ1aDk
nNclU1sH0SD08BdyPVEb7YtccZiAWoiYBY3CkFDh8Fxdzdauh+ibOHLU+1zVzygToUA6fzGPnu0K
ZOKJlwmz9CgJiRXPcMGSm0UPFBjL3g1SUi3ZOnWiBw2P7HQIJ2om4tXUxjHPX3UwoEEN533UFIAA
ug0T96REEOkpvQXf8BXf8SXf8jXf80Xf9FXf9WXf9nXf94Xf+JXf+aXf+rXf+8Xf/NXf/eXf/vXf
/wXgABbgASbgAjbgA0bgBFbgBWbgBnbgB4bgCJbgCabgCrZgmgwIACH5BABkAOkALAAAAADCAT0A
hy8vPyUwPxAvTx8vQB8vTxAvUBAvXx8gUB8vUB8vXx8wTx8wUB8wXx8/UB8/Xx8vYB8wYB81aiAv
QCAvTyAvUCAvXy8vUC8vXyAwQCAwTyA/Ty8wQC8wTy8/TyAwUCAwXyA/UCA/Xy8wUC8wXy8/UC8/
XzA/UDA/XyAvYCAvbyAwYCAwbyA/YCA/by8wYC8wby8/YC8/bzA/YDBAUDBAXzBPXz9AXz9PXzBA
YDBAbzBPYD9AYD9PYD9Pbz9PcEBIWEBAb0BPYEBPb09PcEBQYEBQb09Qb0hYaE9fb0BQcEBQf09Q
cE9fcE9ff1Bfb1BfcFBff1VlcFBgf19gf19vf2Bgf2Bvf1BfgE9ggFBggFBgj19ggF9vgF9vj2Bv
gGBvj2pqgG9vj29wgG9wj29/j29wkG9/kG9/n3B/kHh/mG9/oG+AkHCAn3CImH+AkH+An3+Pn3+Q
mHCAoH+PoHiKqH+PsH+Qr3+QsICPn4+Pn4+Qj4WQkICQn4+Qn4CAoICPoICPr4+PoI+Pr4CQoICQ
r4+QoI+Qr4+fqJCfr5+fr5CfsJCfv4+gv5+gqpCgsJ+gsJ+gv5iou6Wlv6CvsKCvv6+vsKiwv5Cg
yp+vwJ+wwKCvwKivyK+wwK+wz6+41LCwwLC/wLC/z7+/z7DAwLDAz7/Az7/Pz7DE2b/A0L/A37/P
0L/P37/P4MC/v8DAz8DPz8DA0MDA38DP0MDP38/P38/Q39DV2sDP4M/P4MDQ4M/Q4M/Q78/f4M/f
78/f8M/f/9DQ4NDf4NDf79/f4N/f79/g39/g4N/g79jo79Dg/9/g8N/g/9/v8N/v/+Dg7+To6+/v
7+Dg8ODv8ODv/+rg/+/v8O/v/+Dw/+D//+/w8O/w/+////Dv7/Dw7/D/7//w7///7/Dw8PDw//D/
8PD////w8P/w////8P///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAj+AD8IHEiwoMGDCBMqXMiwocOHECNKnEixosWL
GDNq3Mixo8ePIEOKHEmypMmTKFOqXMmypcuXMGPKnEmzps2bOHPq3Mmzp8+fQFsuCPFhQdCjSJMq
XVpyAQKBC4wy5YhA6tSrWLNq3cq1q9evIK2CHUu2rFmMT8+qXcuW7dO0bRtGxcngoIq4be+qrQoD
LkYGgOterUr0puCCevGqTXzWh5a+GgMfXmrUsUoXFT6MoOBBBIUNUR0sgEBAwwcPEzx8gAAhc0Kj
gBdE+JCBQ4YPIQyowKyZs2cPDBYouL2ggYfjyI+n/hBcNQUEKlgQ+FBBRIAEwytUWAD8A4IQsFX+
QFihooKHJVMMBVofCM2VEhRcgw+RlsHxqB44APCwgEGI4fwll1wGqsU2UFoVUMDBBvz5ByB3Ah5X
lGCArRaChKfdhppqrC1k1XcqUCDCbbmVx9wHIiwX4X1RzQVYZlEVUJdqRQmUlnGdpZXaijz+0Akh
FdoXAQMgZACChAQWVcJ0jBEUgQA0VIehXwKN8FRgKpg4whBf/CFIIIb84YUQF1SAwgOqZckdBcyx
mN9+/f1HIIQRUjDCZhPs8KNKCJTgQQbJkCMoOdvQUYADCMDgCzbkjENoGxgi9BQOCORwyTaDYrPG
hX3+Gaig5qBDDjqkCkrqqafKgoofS5BAgAf+KoSQwHcC/TIoOdbQAYIC/Xl3mnceBIGHKreiOmgt
jyzhwXSunVjUAraWKuqoqFaLDjCx/CFFBrd5d6EHJSyDqajTWlstOaisUkgRBALXHGYeJMOoo9tA
SqOkH7BQ6aWZbgouf8lgaqq51VbjSiWG3JABdHdNVxALHwhDbbkEE2wNOXgU+AEFFkg8TqnjbNOJ
jfQlpMAMvZCjjaDNKAFDQQtkUAJcGQjRRykrDzytoLLAccRxaQ1V4bPRkqszwbeqTI4eKt0HAgej
kHMOOVLw1599r5xzjjhWeEABmwoF9tQeH4/jRbdOQy31N6RqHeo5FYeKTildo2DUt6ehgs7+ON5Y
MYECIEQVAgMwEJBBEJSMo/U5H4uqOOOLO6qMIUFMkEMPHkDMpn16fwM3OotXfKo4tVhBwF0eXEiA
CKSQ43nbWou+N6moTNEtQcdlvXXXnDkEHdl7n21jcBqAonXj5sqtvKOweEHBXWJV5d0JooD+uezm
kgMHgU+FKAIs1fJCYAL5igUzARyUQqo2JnhHpVUU2EBJo8ebqzU44HgzCxfcgkBAf5prU+c+FzqC
jUNxBxwV01ICmBggwAOFkBo5TIAAGjAgAfbJg9wsgALyIMQpzEFAhapwqvi8AAUNfGAE4VYKVKhC
FrBARSlMQcMa0hBVU5tD76qiGg8MglT+4uBABTAIAQ+kBYLiMNYxUFGIPxRiEI+QhTRMBbePWSIX
/AuSffAAOnSIwoUthIUNbViNtomKDQMZCgFI0AepeRGMqBDjGGn4ilGVo1RuABoLLngaDZKKgx48
CAh9xZwtlLACJ1TBjAKBjjvOkYalKIUsInkMnYkjFCdw1oEEcgBFJJEcpFgFKh5JSlPQYhuI6Fb3
KDCIiaFDGj/wAAxUgMF7FWQFKBgBI8WRihHMBTxwMcoEDDEquI3qGKEoBB6aiAhUVINa3hCUMqyA
gTPgIDDM2WIXv6iKMJKyFN2UhSxqoY0+rOSCEPiAIUqVgV65hpHhIIcIGCDChEjPfTD+8AI6xEGO
EvSKOQlI5zrRoY0TPDADnAEBQjzQg0KUUVBkMCJ4PGCeQYRKni5gjgoU6gIKKIJa5NCFIYQwAerQ
UiDHEcIbOtG2aKriVQnQVy35ICptkIA/CohUQTxAgz9kY1TkGENmMKgCD3BRZTcVjk5x5wEjOPST
ZaARC1RgFHjKk56TKcg9EZAoffLTn3URj30CkUR0NKRPWVCENE41CxwQxC8qmIPUtNGBJD2EA4So
w8Z8ZR8+KM5x5ODFDBCwx+Ag5AFF5eLcbEmQ4MgAFRPzxUhTA7aBiGAJhpDYqcJxjFuoJqYImGlN
k5pTxhaEMwQoASEIoRICDI4BFPj+AzuZIxUG/AGoGXDQQuCCgCngtj8KcC1gYluqCdTyA1TlEQTq
YgRtiMoYqkGAQlnAyuJ+h1fOKcOoxFGNOdAgNSxIgCIVSb7THEdYOXvCBx5An7tIR7HkmE6FOLOi
kwZhreQYhkDEU9RClEq+daFvhFiTAAo8IRqgE0a3ZCSQ24oqt//Z7YF8+2DgHuc//iUVj8w7lGWp
5gSfOAc40NFWKtWIi3ArqXl5tKIc+CAzKnhgeWR7DlFwwlSUIMERERKbQihOFab11QmCcSpprGFJ
TyksBGiZljV+oRaj80JJ25svAsAXwBvjUZbqAh4c9KBp3soATR+sSKusU1AeWIH+fRgCMYF84b8M
MMCFwjxmcnAgBmumKo9n9AZqyUE1CvhAAnwIOnJoqEEJEAGC4/mEKRkoOIXxz8aCMA1NTEAFEYgK
LfvbxUtXaAQfZEBRx1DWPw+OuitEh6frAuqDxBQCg35Dqd6wOamcmRxpXvNC2vyBN4uKAHFW3X9a
qTWGlPdEGaAEuRJByIL4N1QXMNFD6MlrG32gEHCLhQh4UWhH0Mh8BMHgHEi1CnDnKwOioFYtaFAj
qMxlKIMTyKs4gIdRUaKkwTGKeCHYaUWy2kNQCfJITLQAEMD30hCQygJQbGftCHyTUiHh3tIEKxgZ
vFQigEABQFBPhNhVBNMg1SL+kCPoD/xwahmANXJFvQTQjWMQ92IAC5LzK/LVpS4T2EUQ+POABxbI
qIW+jcyzSpAkVccajcREBhQAGA/0IejM2WNCOKCxDDiXHIgAzn9Uw3AhmkfCESfVOChegZM6eBwf
hA1ssOkBvcFNC82Gio+nxp8GQEQ0hs1mXW5LjlR4oAbcmNYbjChwGq3zHKgQeL1JZQsTeCCdJzIK
chw2GQ8g4hqOFw+E2sRwoUt9oVY5dko05kNqAefbH5AtqWr08INwgVrtJn0rRTUCLHmgAZKRTEkV
CYLWIb6y9vmhhpHrrtLvMwj2WSrM0pQAGGSBPqSnUYbJ0aJf5T4wafqAAoj+dQ5S3G4BfzBm9Qt0
fdhOiAHfQ4c5ZCFfgdj2VKyHyOtXL5a9dxEiQxFID65BqlAQKPnMAQGEcCoiIHk8cjcPFDYfAAig
k3gMsAQhBzdPIEJUokXChwonggAZ9QETEASBRw65QAMeIHoPcQd1UDK9giHTxysVQlVEIRXkJxDk
k4CjdyLGhw6nBxWpB3+SJ3+wB4M2OHvoYAGDhlLmdhoIsFwZoAq0IwLudxrCh4PENyM/FA7okFvl
5RQQAheo9wECwB8DMSPSVyoB8isLlU1LSCqkYEvTV4YPNwLukjekUgoa02A8aIYOMX9mVX87CDf4
NxCW10jiYAQLUG0MQAj+cJMNJPBPBlFeD0QfJBiGC9iAp0cGXRQNUPABkGEQgHGBtLVfp0EJcKMN
TPAqEyEASFgU3aGCpRI4AZZGb0V0KyF7pqdrRqF6e4iHDaGHsReE1OKEquEaPDI4d5EBxxAqmkAj
VHgqFCdqHgAHpGINRoBcT/gsCKEAIXAkViGGAuFfcEMjKlBSGwYdH9ABxEAqyfiE2PaN+yWOK9I7
e0QAzPAxlDAzBIGL8fcQvMiHNGZWDwEe8lYE1AIHrsWFeGBM7SSLH9AC5AMet3MQdcGAiHd6BOAG
QAUMJ0AB+mIjLsIAnugdVlIUPKANW9MJDkMRgxR93dhFtxFjA+Ea2oH+OhOySTVIhbWIevjYg/r4
gyjli6LCJv0hjCsiaqdhBKeCBgUiebjYjEXFBORghf7XWHPRcYKRAIPDiDY4huyoJskXIRVCAE5w
KmYQg3/wV2lCVV0pIPtFPkjgRkgJF+9Hf7rIEPvYWH3ojw9hFROgC/s0C9H1c2VpDuTgfjyCWHOh
gxA5iRMpcxx4Y6TiCqrhFIbokbTTJqBoiVOzBNR4hPb0VsfBjdfWacjlb25yHxlwkloIZjapYba4
g3LZegZRl9YHhUBFAYZ1FwopXghgA1CGDtXAA08xFx4wgMNXVIKRAaEAOtswCTjgYQMRK1pUF+J1
UpLIioICbKK2AA7+wGMwICK1MCrQoAPBaX/XCRhUtZ0QmSXxA2XeMA3AOSNFkZNzuRCy+YT9CBHN
AR0T8AizlRgIQJzk8BwK4QEgQAdMl1M8ppgOWCETIAtlpQl2BYCdWJkCsTkeoGznoA1sgkHtBhFc
ZZesKCqw4m5EuXLiBQfKOEg1SZusiZN3CJsFIZu0KKILoAE0dxBLEga6sA0EVQiBRlWSR5xSaJzB
GQXOdUDNEAp/MAZQ0AMpwi1Qihy8kRirOIbosA1+chzttFAT8AWzMC198KO9onpYihxbKkgLIAJT
wJek8gdxKCHyCaMEUZ8ncp/4VyAhIGtTw26SOG77lCI3tSIjQgX+21B8CSqRDhhep2ECRCYqbrCl
tJJNnhhzGTALoUKH/vkX5rWSBHVTE2AkpTV5JZAFNoVBBccSM4qDrRmnPiiXs3mDhjAIccAHeNAH
TlQIuJqrhcAJCLY+3gYrQAqFzDiFRFEACPAGSDc6ILUzxzALs/AJhYAGRXAcQJmVnEoOhoAHeBAI
fUAIuqqroNCboqIJ/+NuH8BIopKt29qt36qrnEAMoxJPirCIUndhrLqTrmqf9/cQRaUxXiBBUhCG
TmEIjbMy/JQ0pjIoFKVniYmowPEdkicE07BdaNAtazah6ICBZmgfV1cIbPJAnMkQ27ipoTmKIIWw
jSIoE1ABLdD+HM1yEqmagzVyr3nIk686e+AgmN6APY1zDsYgBqPxWQA5icV5egvQAiESBJYgNYvT
tAV0KoKCClxAfqCZYeQCtQQTO1bYBwTQAp+lilbrSq5kPz4rBqiRTb8Cfi/aqrkoiXbqEOSjGmr2
elPDBXYZfufQDWZUMeewDUKXEBFJiTNSiPbxBNIAN9PQBLDhfpSZsRWKhuRQDuTgsUVxJBFhFOZT
tdYDO6QiN6gimC3JHdSoEhVygzJrFASbrw9hSN8IhKsJDvy0s9ICVNQyNboQCX/GiP9EaEULgICI
A25ACRKzrDikNfGKDolAdYpEsv5VDlszttmzDbMAB0VwNZr+67z8dC5XK2KiMguZwAZ1aBCp27YQ
wbo4yI/7Cre/MrcS5AVw+QGCcA53FAqrcApfhAr4m79xNLHcwpmBu5g1grkwoAZiFwwnQJqqoXqo
EGibwwAZELnogAdXI7oQkRkQq4zMiw6eEwqzQAqp0EL6qyqyMLED0CAvsZqqipONMyGV1RBvdkdg
+HWraQ5hsAVUQAVTYAVeMAVTcMNiEA1SgwcMIhAimEaCwbtD2h2Yq4p00hlBMAVe4AVbUAZO9AeQ
cAs68wino7n79AU3nMNbwAViPMZiLAG2QXKla6Xi4MU4bAVhvAVTwAVb4AUIZg59gAHUqkkFUZb0
Z34P8cL+50sd+uqH/CohdfGvoiIFRLE5Jgc30GAC7bIiHCABNtAMqUWODSu4HeqFMBBBoqIL96JC
6BAOs6BQyugBzmUOj9AdFqGiXGwNS0IAFBDJAoIDy3ACYKiQJoHCp+uauIaVDWG+YHizQFUBRCIQ
GcCh8tZnH/MEGVVUBLG7UdiMT/gW+ZJNJgaIH1AEkDAqjuIF1hqaP0kjrIwQopeCVhqg5EyUREkA
cDAq5jCNWyZwqvfLuowQwoy+hJyXeCprokIDRlFrg/A5E7Bq12cjWdA9KHCommwQMTM/pEIJ3LNH
ipV4lGqpJLbFJOsQDZJkUcHFuCZzDyBoFCKDHyAFAHb+zyZhuq05gHBDASGLz6bnuiwaoODBzqyx
ZBxILF70PNYIFUc8zVM4EAXwMuTTIvmGVU/4gn1CbOhACVW6kvEUaNnpAOUnalmCtuHsX1OtUdpJ
W/mXAaRwR35pqgLn0ugA0xKxBTN9t+nbEPkZjvxJUBwnsAQbT5911TfXPaPLiQqqxAfhAcIgDnDj
sTDAAAUwCB+jsXtlH8r2p9Soaw6haUYtNBk8Nbyik4zrfmyyvHWRzSMRs6vKjAENEV8gQb24mrjm
hT2ZGCHyBCn7B8IVzUE9rMZZch9wkiRHwcmBHyFASyBQC1pzDFFdslIoXkx3gFcjgxzKiuyI3Pah
OpL+1wTg4CgwVxcnucekvVd/jNr6jJeTPRB7SSp+CYsLIHyrXUQrkk0TpXxP6LCC4Re9cgK0MMri
8AdP4QDElgqWSY2YiQ5o8Dwy+Y9GgQCugc4riXJgWKUkRyNcVRcxDRKijXqEgNoFwN0OwdauOqMB
ul8LvWLUMQITAAmMIw0zYMJAjVJCbZwz+C8Q4TU2MtDdENIZTCpOmCUjehBHQnJPGKLocONFVR4S
kiUuQACN8DHZ0D6g/QEVPjUfcOEtzBAaTr51+tYMMbQEIJCk8gYEUG0hEH4i2tcw4x8QMmeZDMDW
FobdabikgomuBY0ZG10huQAjSSq0oGNNd6c40Jz+kXm9UvgBKGBaL2uXLDEjVtvLNCYOMhDhBnHa
opLaLIoOI3AXDzDSM2KKAlECw0Aqn7CyziLNts3KOWUH2Q2RJR3kKmAI4eDkIA2G5NMkadRDPbTV
ZKhvyJVR+XdSHTCP6MAJsBKJdrg1iy4Rjj6Y3/2HKIUIgkiIh5HAxvS1H2TNS/6/DihCEP4sRnQa
bZlE0WADBDAISSQKwCEVqPPYEVwCzYGfH5AFu8ABKsbFOPjqy13S+WY1Jv0RKj0jA5XCOthnpJIE
8QYR4xYOzpAWvcPLxVEXCqAAIx04yz0G2xUGAaVwtd275kUIjACGCtcitUUhDrwaLHUOyoDg4mz+
aJZLH1dtIsJI8tNnJKpRMtrXAILDdGXQRVugEP6ODgCv0gYx8AX/uFW+z3JRGPtHKrAgAbJCsusU
KhOgUBzP8QYB834N396RVamj8G7QRbqAA7IlDrOQW96xgR14KtZQBAE/bR7A1pRAdbTet68V80MB
9S0iIYyOfyqgAAGQCTQAeazHH8o7aHqDDr6gUwvgBNTiBsxh1QbS3v1xUuRTCaICC6kRHAR3cQ/W
k5tMECjAClJzDNd0xEcskYamciqwAh8wA81QCzPAACswJRGyxB+wAhUQBF0E1ZunTXAjAgjQAEcC
6wpx+0CX+7vf+zwm1o00DBaEmBekAoZPKoj+zwCKb1iML2rk8/iRP/kLUHbkc3agh7lDZ9WAfypw
9z5z98t2N20ggIqCUXYegK4LOjSS+NkkUAiYsg2gEAiYAmQI4cnnAA1O8HgAoeLDhwQDF3jwsOAD
A4YDPVCphg4dnwUQDnpY6AEPunPkMixkwWDgSJIfPCAgOJBCSZYtXX5QkSADkW00MCJQGGIBgxAJ
EggkQo4jJoQjFywQcY3cOWAUKjAoOBLhiAU6FSLkUY0cOTweVDA4+AFBiAx8JJIT8SHs2Jc3pJ3b
VoiAw4EiPRDi6NFkwgoeKG1Dp23ORwYqvvJECdZq1Q8ngp07h86LWoU/PRTiiG7lBwUeWLz+bHmU
oIrLmTd3/tyyYBFp5tD9UVBBoMiRSZc2XRjVoQeqVvdm3dr160ECIRQMWnoONEsGCEhQCjcOXSKx
LTG7vqCiwvKSKgSEKIzAw1MCfSSiykBjIW2SIhPAyEDCUeZn6KqJutCSxYRUEtFZ4wIhxhpaaDQV
WCBggUKEOqsMykYrLbIJDvtgBJcKMkylErjjcKCvMniEnFqsKKoyCApTAQEaavEvC4yMCuGDP5ZC
RxIgLnCBJIEWusqDAYjIRaJpbGrOg+IYouAP/ya4yCCXQMigEG3GIeeJ7RKSCi90yJlgLAUOmkIo
cCQy5owSVjrsqwwdIsAJXWicxIMEQkD+QCAEN5LIqQ9CwLLDPev84E7/9ORToZYE8kBJdMR5YqAE
elRoxsgkiQFHHevq8ccg0RnSgyIRMg4ziRAildSjEkKIAIxO4AQydG7ZAaWSFNpIwt1KxRVXFDxo
AgHdIPAAOXJU8cAAl8CCIQHxCKABGHEkKgedWFBoCaUT3jxLERwwUogBFhIQSaAJJhhjF3TCWRQY
NxaZgE47CcCTnLkaoiBXhAz7Si0PitjRzwsFokEa/1g5g4YJNpQNoTGG4UgcWUooyqCedmBRImoC
2QHik+oyiYIMjOBkq8De8BTR3CD4wJCzONB3IBBcWsAFCqiRSJQRBJRqDtfQyrGwDHr+caQU/zpi
5hEvJqAABtlQ8mACEb7QZEuJgjnhAwgSYMFXBjwwqyMRXLDrxQ6x1prrvL4O26XtPpggmmdBqRc8
tRAoIYEdaPHv4owRktUuj0EWWRuSCzNJhRM9CORZdFxKcbcSsFBEG/9o2YE9WT2cYyltOshAbA4t
ECMUGARKzOxxSvEUZs9vpgEZdLg5Z5xQXmIABhJQ2XKraxRZYoKIPRAhAxPcgEXyyMRRJHgPMiAb
XLPJ0YaEhDrzvCSwUuXilH79ZSnFBQhh0D+HHynkjz8+EZijcHw5oUmRjmJhASKMEUeojqRBhZJB
8BhkkD84wcWzFEeOQnjKAHZhSAz+xLOgjrDsKAIxFEvA4wIvjEM6eOjcScQ1CImIg2XgsgjERACG
UmyDHOCInURm0Yk/GKIQeKCELIRywi1xYgeeYohIGKIRdICDHBi4SfW405AdbsSHQBSLEKWSkSj4
xxATOFJhsCY/+tmPHPjTH//8B0ABnqWADDhg4ewSCHREyxRnROMZUYEKWZRCFtLYCjmkI45O7KBA
JJHVARTxLHKQYhWoSGMgBWmK4pkiAygBzwsogCdUiABlLkldvyDABKGgSxVHyckC+oYSERjCeLlz
BioK4YZCBIITwWCQq47hBYzwBIfr4WFkRIEKVZQCFbAYpClK4UZVhKIW05AF917+8p4FeGIMaQCG
HCEjnchkZlHoCMWGOGaUq7BqK+OATDP9cxZ0jANdxSDDBEAClr0sAAQcGMVSyMGFD6gKJREsSQMQ
QAEJ2AIc45AGEjxQAkCRIBTdHIcXCKAAECygAN9SlgJ6wIiIiCl83exm7KQTDDKIbQGfWcnWcEcl
EiHgM5fjEEYzslFydPQz8CRJQviEgfqQYxpOyABhDFPNkCnTVdvkpjfRAU5xeoucCACLBkCxTJxu
0zXoOKo5qIQKL1SgAjjBo0IQcAJRcESbRcXqNoc1AQthhAIcgIVErNG+R9LOUWyrGDqkYQOxgHQg
dUqAB4IwCXJ4I3bdaKZ0pOb+n2oMgkg59NYHMuoB3H2jmdnMqlXPES2JtEKYkBwLaTygACY8whYi
06o1NEEFEiSGIVd5KwsEQgEe8EEVHcRpHLcxDU6IgQMYaRyW6La8ZGwFMNqgQ1hMArOBbCKOW2HE
hAryi22YkBzWoAMIvuSuBERghyc4Qyi0gdmzxJEZo0ADCQjwLdrQ5ii/mCE5riEHjOimQ95dAHhz
N97yvgQjBfBAJKxBDhNu4xILaZxHR1va0z5Tq7ZlrWthyzSFQGwByTDuQ/97Fme4ohJv4EEGCBCT
3ZbkM8IIH3UTm9phvegoGcCwHMnBjCOUlSVhaUgGQCEyKklDCTCY1QdgIID+jHhACIeoRRz/Cz1O
hEEE7xsJeNCrXqlpGKsPfZYrHtuSzUAAXwyggAt6sIU/BCIQhVhDgFI1TYV0y1FrWl4SuvCHQRCC
zIXwgheCANsUFAYFKqjXTlywnRHUSwQI2IAj1eKkljhZLBQQQfAy0K46ISADAZBJBrZzEAYoQCfK
osFcEJWBG1ghDX/Ig5UNsYUk1FkgX0nNUwR0EA4AwAIWEEF58+WnrSWE1KZGtapBQ7gJcIADCghA
51Dyzi/vKMxjLvOZ07xmmLRZBW+OMwO2IxIR+G4vuTLnqXbCAGotwAE7/Mieq/OBBiDkzgPxnb3E
zYFAnAImW7PaXjpHON7+qgUsDCmoSj6QI7e+dT1Q+UBfRrCFMlQ5EHzgAxVucC/DFaRp/KzxqUqd
EJ4ooHMXydWeE0KCOZh7yRfHeMZn/VgTL2dtGgd5yEU+cpKXvEMwUENqUGpylpe8y2qBgRxaPnOa
+wkCHX+JU2u+c5733Occ0mQOLrfynxe93QMRAA62Z3SmN93pT4d61DlUb6lXXdtWx3rWtb51rk+9
60Un+tfFPnayl53lohlIjMxOc3iGfe1vh3vc5T73s9Pd7nfHu9Wlyue8XzyCXXZ73wU/eMJnfNeF
F2bgEb94xjfe8Y+HfOQlP3nKV97yl8d85jW/ec533vOfB33oRT960pcU3vSnR33qVb961rfe9a+H
feyNHhAAOw==

------=_NextPart_000_0083_01BF5795.06C3C4A0
Content-Type: application/octet-stream;
	name="astrbul1e.gif"
Content-Transfer-Encoding: base64
Content-ID: <008001bf578c$a4ee93c0$0100007f@ftid33tp9h>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhDwAPAHcAACH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAY
AAAADG1zT1BNU09GRklDRTkuMALxmbSWACH/C01TT0ZGSUNFOS4wGAAAAAxjbVBQSkNtcDA3MTIC
AAAGkmNPuAAh+QQBAAAAACwAAAAADwAPAIHAwMAAM2YBAgMBAgMCG4SPqcvtHcIzMb5aIc5q7+R9
R8iN4eJplrMuBQA7

------=_NextPart_000_0083_01BF5795.06C3C4A0
Content-Type: application/octet-stream;
	name="strrulee.gif"
Content-Transfer-Encoding: base64
Content-ID: <008101bf578c$a4ee93c0$0100007f@ftid33tp9h>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhWAIKAHcAACH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAY
AAAADG1zT1BNU09GRklDRTkuMAQY+hGjACH/C01TT0ZGSUNFOS4wGAAAAAxjbVBQSkNtcDA3MTIC
AAAH5WR/LgAh+QQBAAAAACwAAAAAWAIKAILAwMDMzJkAM2YAAAABAgMBAgMBAgMBAgMCm4SPqcvt
D6OctNqLs968+w+G4kiW5omm6sq27gvH8kzX9o3n+s73/i8SCIfEovEoDCiXzKbzCY1Kp9Sq9YrN
arfcrvcLDovH5LL5jKYi1+y2m52Oy+f0uv2Oz+v3/PT7DxiY1EdYaHiImKi4yBgn+Ahp1DhJWWl5
iZmpGckJqfkJGio6SlraiQSUqrrK2ur6ChsrO0tba3uLC1MAADs=

------=_NextPart_000_0083_01BF5795.06C3C4A0--



From owner-ietf-outbound  Wed Jan  5 10:21:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07312
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 10:20:03 -0500 (EST)
Received: from ibd.ar.com (adsl-63-194-205-75.dsl.snfc21.pacbell.net [63.194.205.75])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06851;
	Wed, 5 Jan 2000 10:05:17 -0500 (EST)
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id HAA02886;
	Wed, 5 Jan 2000 07:04:56 -0800 (PST)
Date: Wed, 5 Jan 2000 07:04:58 -0800 (PST)
From: Rick H Wesson <wessorh@ar.com>
To: Randy Bush <randy@psg.com>
cc: Ed Gerck <egerck@nma.com>,
        Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        "David R. Conrad" <David.Conrad@iengines.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar
  Protocol (RRP) Version 1.1.0 to Informational
In-Reply-To: <E125rdc-00066h-00@rip.psg.com>
Message-ID: <Pine.LNX.4.10.10001050703120.15642-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


randy,

the RFC is what will be used, RRP version 1.1.0 is in the OT&E (test
environemnt) slated to be put into general availability on Jan 15th.

The current version in production is RRP 1.0.6

-rick

On Wed, 5 Jan 2000, Randy Bush wrote:

> > 2. The proposed RFC is not what should be used:
> 
> this is not relevant to the publication of *this* rfc, the intent of which
> is to document what IS used not what SHOULD BE used.
> 
> randy
> 



From owner-ietf-outbound@ietf.org  Wed Jan  5 10:22:59 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07512
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 10:22:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id KAA08243;
	Wed, 5 Jan 2000 10:21:31 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07312
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 10:20:03 -0500 (EST)
Received: from ibd.ar.com (adsl-63-194-205-75.dsl.snfc21.pacbell.net [63.194.205.75])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06851;
	Wed, 5 Jan 2000 10:05:17 -0500 (EST)
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id HAA02886;
	Wed, 5 Jan 2000 07:04:56 -0800 (PST)
Date: Wed, 5 Jan 2000 07:04:58 -0800 (PST)
From: Rick H Wesson <wessorh@ar.com>
To: Randy Bush <randy@psg.com>
cc: Ed Gerck <egerck@nma.com>,
        Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>,
        "David R. Conrad" <David.Conrad@iengines.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar
  Protocol (RRP) Version 1.1.0 to Informational
In-Reply-To: <E125rdc-00066h-00@rip.psg.com>
Message-ID: <Pine.LNX.4.10.10001050703120.15642-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


randy,

the RFC is what will be used, RRP version 1.1.0 is in the OT&E (test
environemnt) slated to be put into general availability on Jan 15th.

The current version in production is RRP 1.0.6

-rick

On Wed, 5 Jan 2000, Randy Bush wrote:

> > 2. The proposed RFC is not what should be used:
> 
> this is not relevant to the publication of *this* rfc, the intent of which
> is to document what IS used not what SHOULD BE used.
> 
> randy
> 



From owner-ietf-outbound  Wed Jan  5 10:31:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07689
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 10:30:02 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07265;
	Wed, 5 Jan 2000 10:19:18 -0500 (EST)
Received: from 192.168.124.51 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id QAA13913; 
          Wed, 5 Jan 2000 16:17:15 +0100 (MET)
Date: Wed, 05 Jan 2000 16:17:15 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Rick H Wesson <wessorh@ar.com>, Randy Bush <randy@psg.com>
cc: Ed Gerck <egerck@nma.com>, "David R. Conrad" <David.Conrad@iengines.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
Message-ID: <1126093.3156077835@[192.168.124.51]>
In-Reply-To: <Pine.LNX.4.10.10001050703120.15642-100000@loki.ar.com>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA07265
Content-Transfer-Encoding: 8bit

--On 2000-01-05 07.04 -0800, Rick H Wesson <wessorh@ar.com> wrote:

> the RFC is what will be used, RRP version 1.1.0 is in the OT&E (test
> environemnt) slated to be put into general availability on Jan 15th.
>
> The current version in production is RRP 1.0.6

The I-D in question states in the first sentence of section 1:

    This document describes the specifications for the Registry Registrar
    Protocol (RRP) version 1.1.0

That is enough for me, as John points out.

    Patrik Fältström
    Area Director, Applications Area, IETF





From owner-ietf-outbound@ietf.org  Wed Jan  5 10:33:48 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07832
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 10:33:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id KAA08572;
	Wed, 5 Jan 2000 10:32:19 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07689
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 10:30:02 -0500 (EST)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07265;
	Wed, 5 Jan 2000 10:19:18 -0500 (EST)
Received: from 192.168.124.51 (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id QAA13913; 
          Wed, 5 Jan 2000 16:17:15 +0100 (MET)
Date: Wed, 05 Jan 2000 16:17:15 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@swip.net>
To: Rick H Wesson <wessorh@ar.com>, Randy Bush <randy@psg.com>
cc: Ed Gerck <egerck@nma.com>, "David R. Conrad" <David.Conrad@iengines.com>,
        Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org,
        Karl Auerbach <karl@cavebear.com>
Subject: Re: Back to the drawing board, was Re: Last Call: Registry Registrar 
 Protocol (RRP) Version 1.1.0 to Informational
Message-ID: <1126093.3156077835@[192.168.124.51]>
In-Reply-To: <Pine.LNX.4.10.10001050703120.15642-100000@loki.ar.com>
X-Mailer: Mulberry (MacOS) [2.0.0b7, s/n U-301169]
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA07265
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

--On 2000-01-05 07.04 -0800, Rick H Wesson <wessorh@ar.com> wrote:

> the RFC is what will be used, RRP version 1.1.0 is in the OT&E (test
> environemnt) slated to be put into general availability on Jan 15th.
>
> The current version in production is RRP 1.0.6

The I-D in question states in the first sentence of section 1:

    This document describes the specifications for the Registry Registrar
    Protocol (RRP) version 1.1.0

That is enough for me, as John points out.

    Patrik Fältström
    Area Director, Applications Area, IETF





From owner-ietf-outbound  Wed Jan  5 10:41:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08206
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 10:40:02 -0500 (EST)
Received: from a4.jck.com (ns.jck.com [63.65.7.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07655;
	Wed, 5 Jan 2000 10:29:47 -0500 (EST)
Received: from p2.jck.com ("port 1144"@[63.65.7.138])
 by a4.jck.com (PMDF V5.1-11 #C4036) with ESMTP id <0FNV0022LCAOHR@a4.jck.com>;
 Wed,  5 Jan 2000 10:28:00 -0500 (EST)
Date: Wed, 05 Jan 2000 10:21:03 -0500
From: John C Klensin <klensin@mci.net>
Subject: Re: Back to the drawing board,was Re: Last Call: Registry Registrar
 Protocol (RRP) Version 1.1.0 toInformational
In-reply-to: <387355E2.78B4830C@nma.com>
To: Ed Gerck <egerck@nma.com>
Cc: iesg@ietf.org, Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
Message-id: <2174858860.947067663@p2.jck.com>
MIME-version: 1.0
X-Mailer: Mulberry (Win32) [2.0.0b6, s/n U-301227]
Content-type: text/plain; charset=us-ascii; format=flowed
Content-disposition: inline
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

--On Wednesday, 05 January, 2000 06:32 -0800 Ed Gerck 
<egerck@nma.com> wrote:

> Yes, but IMO IETF RFCs, even informational, should not be
> bureaucratic milestones in a chart but real contributions --
> where it is OK to be wrong since in Science a NO is also an
> answer. So, an RFC should not be fictional or clearly wrong.

Ed,

Assuming for purposes of argument that I agree with this 
distinction, the hypothetical chart and its milestones are a 
strawman.   I'm not especially attracted to the reasons some 
people participate in the IETF, but I think we need to judge the 
quality of the output almost independent of our guesses about 
the psychology of its sources.  Moreover, there has always been 
a distinction between Informational RFCs --which are expected to 
be an explanation or statement about something-- versus 
Experimental ones.   The latter should be subject to the 
scientific criteria you suggest.  Indeed, I've often felt that 
we would be better off if the authors of Experimental RFCs 
assumed an obligation to come back after a reasonable amount of 
time and write a new RFC explaining how the experiment came out 
and proposing the next experiment if appropriate.

If something is an opinion about how something should be done, 
one might disagree with it and it might even  be wrong 
technically, but that doesn't make it an invalid statement about 
that opinion.   And, if someone asserts that something they want 
to publish describes a partcular process, then I believe that we 
should publish that assertion along with the description.  But 
going further than that takes us dangerously close to certifying 
that the document and the implementation match, and that just 
isn't a good idea.

> And this has nothing to do with "freedom of press" but with
> old accepted rules of technical publication in whatever forum.

When I review things for a journal, I review them differently, 
and apply different criteria, depending on whether they 
represent opinion pieces or description on the one hand or, 
e.g., experimental results.

Let me try a strawman out on you: Suppose I came to the RFC 
Editor with a document entitled "a review of operational 
experience with the foobar protocol" that I wanted published as 
informational.   It would be entirely rational for the RFC 
Editor (or the IESG) to issue a Last Call whose key question was 
"does this description agree with the experience of others". 
Now, for many scientific publications, if the answer came back 
"no", the paper would go back to the authors, with a note that 
said "talk with these other folks and revise".  The tradition in 
the RFC series (and with some journals) has been that such 
things are suggested but, when the fail, the document is 
published, sometimes with an "opinions differ" disclaimer and 
the commenters are encouraged to write their own critiques. 
Either approach is scientifically reasonable and can be quite 
effective and illuminating; the second is arguably better at 
spreading knowledge of negative results.

But this document is, I believe, an NSI statement of what they 
think the protocol is, or would like the protocol to be,  or 
want people to think the protocol is (again, I think that needs 
to be clear).  To the extent that it is an accurate statement of 
their views in one of those categories, it can't be "fictional" 
or "clearly wrong".  To the extent that they claim it reflects 
the protocol and you believe it doesn't, your best recourse is 
to drop NSI a note that says, more or less, "if you publish that 
as if it were the protocol, I'll round up a bunch of registrars 
and sue you... partially on the theory that the Judge can lift 
the NDA that prevents our making the problems public".  But that 
isn't an IETF problem, and we put the IETF at risk by tryng to 
make it one.

     john



From owner-ietf-outbound@ietf.org  Wed Jan  5 10:42:56 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08324
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 10:42:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id KAA08805;
	Wed, 5 Jan 2000 10:41:29 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08206
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 10:40:02 -0500 (EST)
Received: from a4.jck.com (ns.jck.com [63.65.7.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07655;
	Wed, 5 Jan 2000 10:29:47 -0500 (EST)
Received: from p2.jck.com ("port 1144"@[63.65.7.138])
 by a4.jck.com (PMDF V5.1-11 #C4036) with ESMTP id <0FNV0022LCAOHR@a4.jck.com>;
 Wed,  5 Jan 2000 10:28:00 -0500 (EST)
Date: Wed, 05 Jan 2000 10:21:03 -0500
From: John C Klensin <klensin@mci.net>
Subject: Re: Back to the drawing board,was Re: Last Call: Registry Registrar
 Protocol (RRP) Version 1.1.0 toInformational
In-reply-to: <387355E2.78B4830C@nma.com>
To: Ed Gerck <egerck@nma.com>
Cc: iesg@ietf.org, Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
Message-id: <2174858860.947067663@p2.jck.com>
MIME-version: 1.0
X-Mailer: Mulberry (Win32) [2.0.0b6, s/n U-301227]
Content-type: text/plain; charset=us-ascii; format=flowed
Content-disposition: inline
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

--On Wednesday, 05 January, 2000 06:32 -0800 Ed Gerck 
<egerck@nma.com> wrote:

> Yes, but IMO IETF RFCs, even informational, should not be
> bureaucratic milestones in a chart but real contributions --
> where it is OK to be wrong since in Science a NO is also an
> answer. So, an RFC should not be fictional or clearly wrong.

Ed,

Assuming for purposes of argument that I agree with this 
distinction, the hypothetical chart and its milestones are a 
strawman.   I'm not especially attracted to the reasons some 
people participate in the IETF, but I think we need to judge the 
quality of the output almost independent of our guesses about 
the psychology of its sources.  Moreover, there has always been 
a distinction between Informational RFCs --which are expected to 
be an explanation or statement about something-- versus 
Experimental ones.   The latter should be subject to the 
scientific criteria you suggest.  Indeed, I've often felt that 
we would be better off if the authors of Experimental RFCs 
assumed an obligation to come back after a reasonable amount of 
time and write a new RFC explaining how the experiment came out 
and proposing the next experiment if appropriate.

If something is an opinion about how something should be done, 
one might disagree with it and it might even  be wrong 
technically, but that doesn't make it an invalid statement about 
that opinion.   And, if someone asserts that something they want 
to publish describes a partcular process, then I believe that we 
should publish that assertion along with the description.  But 
going further than that takes us dangerously close to certifying 
that the document and the implementation match, and that just 
isn't a good idea.

> And this has nothing to do with "freedom of press" but with
> old accepted rules of technical publication in whatever forum.

When I review things for a journal, I review them differently, 
and apply different criteria, depending on whether they 
represent opinion pieces or description on the one hand or, 
e.g., experimental results.

Let me try a strawman out on you: Suppose I came to the RFC 
Editor with a document entitled "a review of operational 
experience with the foobar protocol" that I wanted published as 
informational.   It would be entirely rational for the RFC 
Editor (or the IESG) to issue a Last Call whose key question was 
"does this description agree with the experience of others". 
Now, for many scientific publications, if the answer came back 
"no", the paper would go back to the authors, with a note that 
said "talk with these other folks and revise".  The tradition in 
the RFC series (and with some journals) has been that such 
things are suggested but, when the fail, the document is 
published, sometimes with an "opinions differ" disclaimer and 
the commenters are encouraged to write their own critiques. 
Either approach is scientifically reasonable and can be quite 
effective and illuminating; the second is arguably better at 
spreading knowledge of negative results.

But this document is, I believe, an NSI statement of what they 
think the protocol is, or would like the protocol to be,  or 
want people to think the protocol is (again, I think that needs 
to be clear).  To the extent that it is an accurate statement of 
their views in one of those categories, it can't be "fictional" 
or "clearly wrong".  To the extent that they claim it reflects 
the protocol and you believe it doesn't, your best recourse is 
to drop NSI a note that says, more or less, "if you publish that 
as if it were the protocol, I'll round up a bunch of registrars 
and sue you... partially on the theory that the Judge can lift 
the NDA that prevents our making the problems public".  But that 
isn't an IETF problem, and we put the IETF at risk by tryng to 
make it one.

     john



From owner-ietf-outbound  Wed Jan  5 11:21:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA09478
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 11:20:02 -0500 (EST)
Received: from mauve.innosoft.com (mauve.innosoft.com.253.160.192.IN-ADDR.ARPA [192.160.253.247] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09070;
	Wed, 5 Jan 2000 11:11:35 -0500 (EST)
From: ned.freed@innosoft.com
Received: from MAUVE.INNOSOFT.COM by MAUVE.INNOSOFT.COM (PMDF V6.0-17 #35243)
 id <01JKBMNKQYUO0001Q6@MAUVE.INNOSOFT.COM>; Wed,
 05 Jan 2000 12:53:11 -0800 (PST)
Date: Wed, 05 Jan 2000 12:23:50 -0800 (PST)
Subject: Re: Back to the drawing board,
 was Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to
 Informational
In-reply-to: "Your message dated Wed, 05 Jan 2000 09:00:06 -0500"
 <2170001740.947062806@p2.jck.com>
To: John C Klensin <klensin@mci.net>
Cc: Ed Gerck <egerck@nma.com>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
Message-id: <01JKCH21R6VW0001Q6@MAUVE.INNOSOFT.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; format=flowed; charset=us-ascii

John Klensin wrote, in part:

> In summary, I believe that our advice to the IESG should be

> "make certain this document is clear about what it is and what
> it proports to be, and that the authors (or author organization)
> take responsibility for that being true.  Make certain that,
> should a RRP WG effort be launched, this document doesn't
> unreasonaby constrain it.   If areas are identified in which the
> document isn't clear about what it calls for, get those fixed.
> Consider attaching a disclaimer that indicates the list of
> unresolved issues contains some fairly serious problems and that
> there may be equally serious issues not on that list.   Then,
> since it is relevant and not obviously stupid, go ahead and
> publish the thing."

I am in complete agreement with John on all of this. However, I would
like to add a couple of additional points:

(1) While it is true that publication as informational is sometimes
    misinterpreted as an endorsement, this is also something that is
    discussed a lot more than it actually happens. The RFC series
    contains many hundreds of documents describing protocols of dubious
    value and which don't receive a second glance by anybody, in some
    cases in spite of considerable marketing muscle being used to promote
    them.

    It isn't entirely clear why the publication == endorsement error
    happens in some cases, but it often involves some combination of people
    with no IETF standards experience, poor document labelling, a lack of
    a visible standards-track alternative or visible work underway on a
    standards-track alternative. In the present situation the first of these
    factors shouldn't apply and the second and third are things we control, so
    we should be able to minimize the risk of something bad happening.

(2) The publication of protocol specifications in order to document the
    history of Internet protocol evolution is actually pretty important when
    you're actually doing protocol development work. I find it incredibly
    useful, for example, to refer to RFC 733, RFC 788, RFC 1049, RFC 1154,
    FIPS PUB 98, and many other documents when tring to figure out why
    Internet mail has ended up where it has and what makes sense for the
    future.

(3) An alternative to putting a lot of comments about unresolved issues in
    given protocol document is to write a separate document critiquing the
    first and publish it as well. This approach used to be use quite a bit
    in the RFC series but has fallen into disuse in more recent times (probably
    because things move so fast these days). Perhaps this is an instance where
    the practice ought to be revived.

				Ned



From owner-ietf-outbound@ietf.org  Wed Jan  5 11:23:39 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09580
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 11:23:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id LAA09821;
	Wed, 5 Jan 2000 11:22:12 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id LAA09478
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 11:20:02 -0500 (EST)
Received: from mauve.innosoft.com (mauve.innosoft.com.253.160.192.IN-ADDR.ARPA [192.160.253.247] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09070;
	Wed, 5 Jan 2000 11:11:35 -0500 (EST)
From: ned.freed@innosoft.com
Received: from MAUVE.INNOSOFT.COM by MAUVE.INNOSOFT.COM (PMDF V6.0-17 #35243)
 id <01JKBMNKQYUO0001Q6@MAUVE.INNOSOFT.COM>; Wed,
 05 Jan 2000 12:53:11 -0800 (PST)
Date: Wed, 05 Jan 2000 12:23:50 -0800 (PST)
Subject: Re: Back to the drawing board,
 was Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to
 Informational
In-reply-to: "Your message dated Wed, 05 Jan 2000 09:00:06 -0500"
 <2170001740.947062806@p2.jck.com>
To: John C Klensin <klensin@mci.net>
Cc: Ed Gerck <egerck@nma.com>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
Message-id: <01JKCH21R6VW0001Q6@MAUVE.INNOSOFT.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; format=flowed; charset=us-ascii

John Klensin wrote, in part:

> In summary, I believe that our advice to the IESG should be

> "make certain this document is clear about what it is and what
> it proports to be, and that the authors (or author organization)
> take responsibility for that being true.  Make certain that,
> should a RRP WG effort be launched, this document doesn't
> unreasonaby constrain it.   If areas are identified in which the
> document isn't clear about what it calls for, get those fixed.
> Consider attaching a disclaimer that indicates the list of
> unresolved issues contains some fairly serious problems and that
> there may be equally serious issues not on that list.   Then,
> since it is relevant and not obviously stupid, go ahead and
> publish the thing."

I am in complete agreement with John on all of this. However, I would
like to add a couple of additional points:

(1) While it is true that publication as informational is sometimes
    misinterpreted as an endorsement, this is also something that is
    discussed a lot more than it actually happens. The RFC series
    contains many hundreds of documents describing protocols of dubious
    value and which don't receive a second glance by anybody, in some
    cases in spite of considerable marketing muscle being used to promote
    them.

    It isn't entirely clear why the publication == endorsement error
    happens in some cases, but it often involves some combination of people
    with no IETF standards experience, poor document labelling, a lack of
    a visible standards-track alternative or visible work underway on a
    standards-track alternative. In the present situation the first of these
    factors shouldn't apply and the second and third are things we control, so
    we should be able to minimize the risk of something bad happening.

(2) The publication of protocol specifications in order to document the
    history of Internet protocol evolution is actually pretty important when
    you're actually doing protocol development work. I find it incredibly
    useful, for example, to refer to RFC 733, RFC 788, RFC 1049, RFC 1154,
    FIPS PUB 98, and many other documents when tring to figure out why
    Internet mail has ended up where it has and what makes sense for the
    future.

(3) An alternative to putting a lot of comments about unresolved issues in
    given protocol document is to write a separate document critiquing the
    first and publish it as well. This approach used to be use quite a bit
    in the RFC series but has fallen into disuse in more recent times (probably
    because things move so fast these days). Perhaps this is an instance where
    the practice ought to be revived.

				Ned



From owner-ietf-outbound  Wed Jan  5 12:53:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA11825
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 12:50:02 -0500 (EST)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11598;
	Wed, 5 Jan 2000 12:42:05 -0500 (EST)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id JAA11707;
	Wed, 5 Jan 2000 09:35:19 -0800 (PST)
Received: from p7020-img-nt (fred-hm-dhcp2.cisco.com [171.69.128.117]) by rhino (SMI-8.6/CISCO.WS.1.1) with SMTP id JAA21798; Wed, 5 Jan 2000 09:46:31 -0800
Message-Id: <4.1.20000105091321.01e92c50@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 05 Jan 2000 09:17:10 -0800
To: Gordon Cook <cook@cookreport.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: oh merde!  <blush>  Patrick F. and ICANN board error
Cc: Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
In-Reply-To: <v04210106b4985c8a883b@[192.168.0.1]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 09:38 PM 1/4/00 -0500, Gordon Cook wrote:
>   I carry a lot of ICANN data around in my head and I am generally 
>pretty good at it.  However my attention has been called to the fact 
>that I screwed up on my association with Patrick as an ICANN board 
>member.  Following a few URL trails I see that he and Goeff Huston 
>were IETF nominees but that ETSI and W3C placed their folk on the 
>board and IETF would up with only Vint.

For the record, there is a PSO in the middle of that. IETF, ETSI, ITU, and
W3C (the members of the PSO) each nominated various and sundry for the
three board seats alloted to the PSO, and nominees from ETSI, W3C, and IETF
were selected. ITU was, er, displeased.

>Wiping red face.....

For all you talk about ICANN, if the PSO involvement escaped you, your face
deserves to be red.



From owner-ietf-outbound@ietf.org  Wed Jan  5 12:55:35 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11996
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 12:55:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id MAA12651;
	Wed, 5 Jan 2000 12:54:05 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA11825
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 12:50:02 -0500 (EST)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11598;
	Wed, 5 Jan 2000 12:42:05 -0500 (EST)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id JAA11707;
	Wed, 5 Jan 2000 09:35:19 -0800 (PST)
Received: from p7020-img-nt (fred-hm-dhcp2.cisco.com [171.69.128.117]) by rhino (SMI-8.6/CISCO.WS.1.1) with SMTP id JAA21798; Wed, 5 Jan 2000 09:46:31 -0800
Message-Id: <4.1.20000105091321.01e92c50@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 05 Jan 2000 09:17:10 -0800
To: Gordon Cook <cook@cookreport.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: oh merde!  <blush>  Patrick F. and ICANN board error
Cc: Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
In-Reply-To: <v04210106b4985c8a883b@[192.168.0.1]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 09:38 PM 1/4/00 -0500, Gordon Cook wrote:
>   I carry a lot of ICANN data around in my head and I am generally 
>pretty good at it.  However my attention has been called to the fact 
>that I screwed up on my association with Patrick as an ICANN board 
>member.  Following a few URL trails I see that he and Goeff Huston 
>were IETF nominees but that ETSI and W3C placed their folk on the 
>board and IETF would up with only Vint.

For the record, there is a PSO in the middle of that. IETF, ETSI, ITU, and
W3C (the members of the PSO) each nominated various and sundry for the
three board seats alloted to the PSO, and nominees from ETSI, W3C, and IETF
were selected. ITU was, er, displeased.

>Wiping red face.....

For all you talk about ICANN, if the PSO involvement escaped you, your face
deserves to be red.



From owner-ietf-outbound  Wed Jan  5 13:42:58 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA12960
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 13:40:02 -0500 (EST)
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12936
	for <ietf@ietf.org>; Wed, 5 Jan 2000 13:39:55 -0500 (EST)
Received: from world.std.com (brunner@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id NAA13528;
	Wed, 5 Jan 2000 13:39:48 -0500 (EST)
Received: from localhost (brunner@localhost)
	by world.std.com (8.9.3/8.9.3) with SMTP id NAA24826;
	Wed, 5 Jan 2000 13:39:47 -0500 (EST)
Message-Id: <200001051839.NAA24826@world.std.com>
X-Authentication-Warning: world.std.com: brunner@localhost didn't use HELO protocol
To: cook@cookreport.com
cc: ietf@ietf.org
Subject: Re: merde!  <blush>  Patrick F. and ICANN board error
Date: Wed, 05 Jan 2000 13:39:47 -0500
From: Eric Brunner <brunner@world.std.com>

Normally I ignore Cook, and am grateful to have missed the original screed.

Technical contributions on the content of the draft-hollenbeck-rrp-00.txt
are nice, but deviations from content analysis are awkward.

Eric



From owner-ietf-outbound@ietf.org  Wed Jan  5 13:46:46 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13087
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 13:46:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id NAA15383;
	Wed, 5 Jan 2000 13:45:15 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA12960
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 13:40:02 -0500 (EST)
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12936
	for <ietf@ietf.org>; Wed, 5 Jan 2000 13:39:55 -0500 (EST)
Received: from world.std.com (brunner@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id NAA13528;
	Wed, 5 Jan 2000 13:39:48 -0500 (EST)
Received: from localhost (brunner@localhost)
	by world.std.com (8.9.3/8.9.3) with SMTP id NAA24826;
	Wed, 5 Jan 2000 13:39:47 -0500 (EST)
Message-Id: <200001051839.NAA24826@world.std.com>
X-Authentication-Warning: world.std.com: brunner@localhost didn't use HELO protocol
To: cook@cookreport.com
cc: ietf@ietf.org
Subject: Re: merde!  <blush>  Patrick F. and ICANN board error
Date: Wed, 05 Jan 2000 13:39:47 -0500
From: Eric Brunner <brunner@world.std.com>

Normally I ignore Cook, and am grateful to have missed the original screed.

Technical contributions on the content of the draft-hollenbeck-rrp-00.txt
are nice, but deviations from content analysis are awkward.

Eric



From owner-ietf-outbound  Wed Jan  5 13:52:51 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA13166
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 13:50:02 -0500 (EST)
Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13007;
	Wed, 5 Jan 2000 13:42:22 -0500 (EST)
Received: from [192.168.0.1] (ipa184.trenton2.nj.pub-ip.psi.net [38.26.139.184])
	by eagle.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id KAA21059;
	Wed, 5 Jan 2000 10:40:33 -0800 (PST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <v04210108b49936652d2f@[192.168.0.1]>
In-Reply-To: <4.1.20000105091321.01e92c50@flipper.cisco.com>
References: <4.1.20000105091321.01e92c50@flipper.cisco.com>
Date: Wed, 5 Jan 2000 13:11:37 -0500
To: Fred Baker <fred@cisco.com>
From: Gordon Cook <cook@cookreport.com>
Subject: Re: oh merde!  <blush>  Patrick F. and ICANN board error
Cc: Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

>At 09:38 PM 1/4/00 -0500, Gordon Cook wrote:
> >   I carry a lot of ICANN data around in my head and I am generally
> >pretty good at it.  However my attention has been called to the fact
> >that I screwed up on my association with Patrick as an ICANN board
> >member.  Following a few URL trails I see that he and Goeff Huston
> >were IETF nominees but that ETSI and W3C placed their folk on the
> >board and IETF would up with only Vint.
>
>For the record, there is a PSO in the middle of that. IETF, ETSI, ITU, and
>W3C (the members of the PSO) each nominated various and sundry for the
>three board seats alloted to the PSO, and nominees from ETSI, W3C, and IETF
>were selected. ITU was, er, displeased.
>
> >Wiping red face.....
>
>For all you talk about ICANN, if the PSO involvement escaped you, your face
>deserves to be red.

I am well aware of the PSO and that aspect did not escape me.....what 
did  escape me (in part i suppose because I was in nepal from oct 13 
to nov 6 and totally off net from roughly the 18th of oct to november 
3 (trekking near everest)) was that nomination by IETF of Cerf, 
Falstrom and Huston was not tantamount to election.

please see  http://cookreport.com/neptibalb.shtml

for short photo essay and satire (the masked dancing of the monks at 
the tengboche monastery reminded me of ICANN).

****************************************************************
The COOK Report on Internet            Index to seven years of the COOK Report
431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
(609) 882-2572 (phone & fax)            Is ICANN an IBM e-business ?
cook@cookreport.com                     See also Lessig's Code: and
Other  Laws of Cyberspace  http://cookreport.com/lessigbook.shtml
****************************************************************



From owner-ietf-outbound@ietf.org  Wed Jan  5 13:55:16 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13291
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 13:55:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id NAA16011;
	Wed, 5 Jan 2000 13:53:49 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA13166
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 13:50:02 -0500 (EST)
Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13007;
	Wed, 5 Jan 2000 13:42:22 -0500 (EST)
Received: from [192.168.0.1] (ipa184.trenton2.nj.pub-ip.psi.net [38.26.139.184])
	by eagle.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id KAA21059;
	Wed, 5 Jan 2000 10:40:33 -0800 (PST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <v04210108b49936652d2f@[192.168.0.1]>
In-Reply-To: <4.1.20000105091321.01e92c50@flipper.cisco.com>
References: <4.1.20000105091321.01e92c50@flipper.cisco.com>
Date: Wed, 5 Jan 2000 13:11:37 -0500
To: Fred Baker <fred@cisco.com>
From: Gordon Cook <cook@cookreport.com>
Subject: Re: oh merde!  <blush>  Patrick F. and ICANN board error
Cc: Ian Jackson <ijackson@chiark.greenend.org.uk>, iesg@ietf.org,
        Scott Hollenbeck <shollenb@netsol.com>, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

>At 09:38 PM 1/4/00 -0500, Gordon Cook wrote:
> >   I carry a lot of ICANN data around in my head and I am generally
> >pretty good at it.  However my attention has been called to the fact
> >that I screwed up on my association with Patrick as an ICANN board
> >member.  Following a few URL trails I see that he and Goeff Huston
> >were IETF nominees but that ETSI and W3C placed their folk on the
> >board and IETF would up with only Vint.
>
>For the record, there is a PSO in the middle of that. IETF, ETSI, ITU, and
>W3C (the members of the PSO) each nominated various and sundry for the
>three board seats alloted to the PSO, and nominees from ETSI, W3C, and IETF
>were selected. ITU was, er, displeased.
>
> >Wiping red face.....
>
>For all you talk about ICANN, if the PSO involvement escaped you, your face
>deserves to be red.

I am well aware of the PSO and that aspect did not escape me.....what 
did  escape me (in part i suppose because I was in nepal from oct 13 
to nov 6 and totally off net from roughly the 18th of oct to november 
3 (trekking near everest)) was that nomination by IETF of Cerf, 
Falstrom and Huston was not tantamount to election.

please see  http://cookreport.com/neptibalb.shtml

for short photo essay and satire (the masked dancing of the monks at 
the tengboche monastery reminded me of ICANN).

****************************************************************
The COOK Report on Internet            Index to seven years of the COOK Report
431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
(609) 882-2572 (phone & fax)            Is ICANN an IBM e-business ?
cook@cookreport.com                     See also Lessig's Code: and
Other  Laws of Cyberspace  http://cookreport.com/lessigbook.shtml
****************************************************************



From owner-ietf-outbound  Wed Jan  5 14:42:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA14373
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 14:40:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14213
	for <ietf@ietf.org>; Wed, 5 Jan 2000 14:32:06 -0500 (EST)
Received: from black-ice.cc.vt.edu (LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id e05JW0D13176;
	Wed, 5 Jan 2000 14:32:00 -0500
Message-Id: <200001051932.e05JW0D13176@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Rick H Wesson <wessorh@ar.com>
Cc: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to Informational 
In-Reply-To: Your message of "Tue, 04 Jan 2000 15:58:37 PST."
             <Pine.LNX.4.10.10001041549290.28714-100000@loki.ar.com> 
From: Valdis.Kletnieks@vt.edu
X-Url: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <Pine.LNX.4.10.10001041549290.28714-100000@loki.ar.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1218962322P";
	 micalg=pgp-md5; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 05 Jan 2000 14:31:59 -0500

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

On Tue, 04 Jan 2000 15:58:37 PST, Rick H Wesson said:
> think the IESG could at least put a "bad bad protocol" sitcker on it when
> they its published, or better yet give it a negative RFC number starting with 
> negative RFC numbers would at least put it firmly into the minds of
> readers that the RFc should *not* be followed.

For a moment, I thought "but you can do that now..."

Then I took a look at RFC2026 in closer detail, and section 3.3 (e)
defines a "Not Recommended" status, just like I remembered.

Unfortunately, that seems to be strictly applicable to standards-track
documents only, not 'informational'.  Whether this is a bug or a feature
I'll let others decide - it looks like a giant economy sized can-o-worms.

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP MESSAGE-----
Version: 2.6.2

iQCVAwUBOHOcL9QBOOoptg9JAQFI9QP/U7kZrIrLOp2JRHshbNUhEq1GhlkCVJUl
hMeJH021yC4FEalFyDqTIa/5oz83oA3OLTuyz47dP6A7WTJZUON/ISCPJvMFD01B
S1+pwbKzCpgdKvq7sFJE/90Tx43YxRQPVSZjFL45zydxbi1lpBHztZxBLFc/X5b3
QuDluRem2OI=
=arcz
-----END PGP MESSAGE-----

--==_Exmh_-1218962322P--



From owner-ietf-outbound@ietf.org  Wed Jan  5 14:44:11 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14499
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 14:44:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id OAA17312;
	Wed, 5 Jan 2000 14:42:41 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA14373
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 14:40:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14213
	for <ietf@ietf.org>; Wed, 5 Jan 2000 14:32:06 -0500 (EST)
Received: from black-ice.cc.vt.edu (LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id e05JW0D13176;
	Wed, 5 Jan 2000 14:32:00 -0500
Message-Id: <200001051932.e05JW0D13176@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Rick H Wesson <wessorh@ar.com>
Cc: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to Informational 
In-Reply-To: Your message of "Tue, 04 Jan 2000 15:58:37 PST."
             <Pine.LNX.4.10.10001041549290.28714-100000@loki.ar.com> 
From: Valdis.Kletnieks@vt.edu
X-Url: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <Pine.LNX.4.10.10001041549290.28714-100000@loki.ar.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1218962322P";
	 micalg=pgp-md5; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 05 Jan 2000 14:31:59 -0500

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

On Tue, 04 Jan 2000 15:58:37 PST, Rick H Wesson said:
> think the IESG could at least put a "bad bad protocol" sitcker on it when
> they its published, or better yet give it a negative RFC number starting with 
> negative RFC numbers would at least put it firmly into the minds of
> readers that the RFc should *not* be followed.

For a moment, I thought "but you can do that now..."

Then I took a look at RFC2026 in closer detail, and section 3.3 (e)
defines a "Not Recommended" status, just like I remembered.

Unfortunately, that seems to be strictly applicable to standards-track
documents only, not 'informational'.  Whether this is a bug or a feature
I'll let others decide - it looks like a giant economy sized can-o-worms.

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP MESSAGE-----
Version: 2.6.2

iQCVAwUBOHOcL9QBOOoptg9JAQFI9QP/U7kZrIrLOp2JRHshbNUhEq1GhlkCVJUl
hMeJH021yC4FEalFyDqTIa/5oz83oA3OLTuyz47dP6A7WTJZUON/ISCPJvMFD01B
S1+pwbKzCpgdKvq7sFJE/90Tx43YxRQPVSZjFL45zydxbi1lpBHztZxBLFc/X5b3
QuDluRem2OI=
=arcz
-----END PGP MESSAGE-----

--==_Exmh_-1218962322P--



From owner-ietf-outbound  Wed Jan  5 17:43:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA17297
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 17:40:02 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17273
	for <ietf@ietf.org>; Wed, 5 Jan 2000 17:38:35 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id PAA11404
	for ietf@ietf.org  env-from <vjs>;
	Wed, 5 Jan 2000 15:38:31 -0700 (MST)
Date: Wed, 5 Jan 2000 15:38:31 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200001052238.PAA11404@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to Informational

> From: Valdis.Kletnieks@vt.edu

> ...
> Then I took a look at RFC2026 in closer detail, and section 3.3 (e)
> defines a "Not Recommended" status, just like I remembered.
>
> Unfortunately, that seems to be strictly applicable to standards-track
> documents only, not 'informational'.  Whether this is a bug or a feature
> I'll let others decide - it looks like a giant economy sized can-o-worms.


I've been whining about such problems with informational RFC's for years.
It's clear that for familiar bureaucratic and social or political reasons,
the IETF will not in the foreseeable future do any real filtering of
Information (or even in many cases of standards track) RFC's.  Even I
admit that real filtering would have major problems and leads inevitably
to something even more like the ANSI, IEEE, and ITU than the IETF has
already become.

There is an alternative that would be more effective and easier.  That is
to do even less filtering than is done now.  Advancing many drafts like
draft-terrell-ip-spec-ipv7-ipv8-addr-cls-*.txt would go a long way to
removing the incentive for organizations to try to misappropriate the
cachet of the IETF with Informational RFC's.  Flooding the space with
RFC's that are other than influential would be more effective than any
disclaimers, more effective than filtering, and easier than the limited
filtering currently provided by the IESG and the RFC Editor.

I suspect analogous thinking but about the academic stuffed shirt syndrome
was one of the motivations for the early April Fool's RFC's.  Today, the
audience (and many of the authors) of RFC's are not capable of inferring
such an implication of new versions of Avian Carriers.  Something less
subtle is needed.

In other words, consider the ideas behind the censoring that has gotten
some ISP's into trouble and the lack of censoring that has protected
others.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound@ietf.org  Wed Jan  5 17:44:40 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17386
	for <ietf-web-archive@odin.ietf.org>; Wed, 5 Jan 2000 17:44:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.8.8) with ESMTP id RAA21988;
	Wed, 5 Jan 2000 17:43:15 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA17297
	for ietf-outbound.10@ietf.org; Wed, 5 Jan 2000 17:40:02 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17273
	for <ietf@ietf.org>; Wed, 5 Jan 2000 17:38:35 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id PAA11404
	for ietf@ietf.org  env-from <vjs>;
	Wed, 5 Jan 2000 15:38:31 -0700 (MST)
Date: Wed, 5 Jan 2000 15:38:31 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200001052238.PAA11404@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Last Call: Registry Registrar Protocol (RRP) Version 1.1.0 to Informational

> From: Valdis.Kletnieks@vt.edu

> ...
> Then I took a look at RFC2026 in closer detail, and section 3.3 (e)
> defines a "Not Recommended" status, just like I remembered.
>
> Unfortunately, that seems to be strictly applicable to standards-track
> documents only, not 'informational'.  Whether this is a bug or a feature
> I'll let others decide - it looks like a giant economy sized can-o-worms.


I've been whining about such problems with informational RFC's for years.
It's clear that for familiar bureaucratic and social or political reasons,
the IETF will not in the foreseeable future do any real filtering of
Information (or even in many cases of standards track) RFC's.  Even I
admit that real filtering would have major problems and leads inevitably
to something even more like the ANSI, IEEE, and ITU than the IETF has
already become.

There is an alternative that would be more effective and easier.  That is
to do even less filtering than is done now.  Advancing many drafts like
draft-terrell-ip-spec-ipv7-ipv8-addr-cls-*.txt would go a long way to
removing the incentive for organizations to try to misappropriate the
cachet of the IETF with Informational RFC's.  Flooding the space with
RFC's that are other than influential would be more effective than any
disclaimers, more effective than filtering, and easier than the limited
filtering currently provided by the IESG and the RFC Editor.

I suspect analogous thinking but about the academic stuffed shirt syndrome
was one of the motivations for the early April Fool's RFC's.  Today, the
audience (and many of the authors) of RFC's are not capable of inferring
such an implication of new versions of Avian Carriers.  Something less
subtle is needed.

In other words, consider the ideas behind the censoring that has gotten
some ISP's into trouble and the lack of censoring that has protected
others.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Fri Jan  7 22:22:00 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA01485
	for ietf-outbound.10@ietf.org; Fri, 7 Jan 2000 22:20:02 -0500 (EST)
Received: from internexus.net (IDENT:qmailr@internexus.net [206.152.14.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA01416
	for <ietf@ietf.org>; Fri, 7 Jan 2000 22:14:46 -0500 (EST)
Received: (qmail 3505 invoked by uid 8079); 8 Jan 2000 02:42:02 -0000
MBOX-Line: From owner-ipng@sunroof.eng.sun.com Fri Dec 24 00:17:53 1999
Delivered-To: ry@internexus.net
Received: (qmail 19741 invoked from network); 24 Dec 1999 00:17:52 -0000
Received: from mercury.sun.com (192.9.25.1)
  by internexus.net with SMTP; 24 Dec 1999 00:17:52 -0000
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA20093;
	Thu, 23 Dec 1999 16:07:02 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA13215;
	Thu, 23 Dec 1999 16:06:52 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) id dBO03E402721
	for ipng-dist; Thu, 23 Dec 1999 16:03:14 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) with ESMTP id dBO035Y02714
	for <ipng@sunroof.eng.sun.com>; Thu, 23 Dec 1999 16:03:06 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA01267
	for <ipng@sunroof.eng.sun.com>; Thu, 23 Dec 1999 16:03:05 -0800 (PST)
Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA06829
	for <ipng@sunroof.eng.sun.com>; Thu, 23 Dec 1999 16:03:04 -0800 (PST)
Received: from ix.netcom.com (user-33qscij.dialup.mindspring.com [199.174.50.83])
	by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA10829;
	Thu, 23 Dec 1999 19:02:52 -0500 (EST)
Message-ID: <3862D206.EBB787CD@ix.netcom.com>
Date: Thu, 23 Dec 1999 17:53:11 -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: Karl Auerbach <karl@CaveBear.com>
CC: DOMAIN-POLICY@LISTS.INTERNIC.NET, IFWP <list@ifwp.org>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>,
        ISI IPv6 list <6bone@ISI.EDU>, ietf@ietf.org
Subject: Re: RRP Specs
References: <Pine.LNX.4.10.9912231525440.8256-100000@npax.cavebear.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ipng@sunroof.eng.sun.com
Precedence: bulk
Status: O
X-Keywords:                  
X-UID: 3278
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Karl and all,

Karl Auerbach wrote:

> > NSI has made an I-D of the RRP Protocol.
> >
> > http://www.ietf.cnri.reston.va.us/internet-drafts/draft-hollenbeck-rrp-00.txt
>
> Am I missing something?  I looked through that and I see neither
> transaction identifiers nor timestamps.  That alone could make
> reconcilation of logs and post-mortem review of race conditions nearly
> impossible.

  Precisely correct here Karl, and one of many deficiencies in this
design document.  But of course this is one of several I had pointed
our some time ago before this document was published.  To no avail
of course.  It reminds me of the lame leading the blind.  And I believe
I amongst a few others made this reference before as well.

>
>
> And given the absence of a clear exchange between an existing registrar
> and a new one I see a HUGE door in the transfer mechanism for registrars
> to engage in what the long distance folks call "slamming" - the silent
> transfer of customers from one long-distance company or registry to
> another.

  And we have already seen this with respect to Register.com in this
context already.  More to come I am sure.

>
>
> And text based?  Wow, that's an open inviation to attacks based on buffer
> overrun and packets split at cr-lf boundaries.

  Not to mention several other text based security attacks.  The hack in these
instances is child's play really.

>
>
> And it is text based without any concern for internationalization.

  Good point here also. And one that slipped my mind...  >;)

>
>
> And its expiration date representation, although it is measured to the
> millisecond, fails to include a reference to any time zone.

  Tisk, tisk, indeed this is a good point as well.

>
>
> Nor does it handle IPv6.

  How true.

>
>
> Seems like a rather deficient design.

  Looks like a design by committee, and a very poorly technically informed
or knowledgeable one at that.

>
>
>                 --karl--

Regards,

--
Jeffrey A. Williams
Spokesman INEGroup (Over 95k members 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:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208


--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to majordomo@sunroof.eng.sun.com
--------------------------------------------------------------------



From owner-ietf-outbound@ietf.org  Fri Jan  7 22:23:22 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01534
	for <ietf-web-archive@odin.ietf.org>; Fri, 7 Jan 2000 22:23:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA25841;
	Fri, 7 Jan 2000 22:22:20 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id WAA01485
	for ietf-outbound.10@ietf.org; Fri, 7 Jan 2000 22:20:02 -0500 (EST)
Received: from internexus.net (IDENT:qmailr@internexus.net [206.152.14.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA01416
	for <ietf@ietf.org>; Fri, 7 Jan 2000 22:14:46 -0500 (EST)
Received: (qmail 3505 invoked by uid 8079); 8 Jan 2000 02:42:02 -0000
MBOX-Line: From owner-ipng@sunroof.eng.sun.com Fri Dec 24 00:17:53 1999
Delivered-To: ry@internexus.net
Received: (qmail 19741 invoked from network); 24 Dec 1999 00:17:52 -0000
Received: from mercury.sun.com (192.9.25.1)
  by internexus.net with SMTP; 24 Dec 1999 00:17:52 -0000
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA20093;
	Thu, 23 Dec 1999 16:07:02 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA13215;
	Thu, 23 Dec 1999 16:06:52 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) id dBO03E402721
	for ipng-dist; Thu, 23 Dec 1999 16:03:14 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) with ESMTP id dBO035Y02714
	for <ipng@sunroof.eng.sun.com>; Thu, 23 Dec 1999 16:03:06 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA01267
	for <ipng@sunroof.eng.sun.com>; Thu, 23 Dec 1999 16:03:05 -0800 (PST)
Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA06829
	for <ipng@sunroof.eng.sun.com>; Thu, 23 Dec 1999 16:03:04 -0800 (PST)
Received: from ix.netcom.com (user-33qscij.dialup.mindspring.com [199.174.50.83])
	by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA10829;
	Thu, 23 Dec 1999 19:02:52 -0500 (EST)
Message-ID: <3862D206.EBB787CD@ix.netcom.com>
Date: Thu, 23 Dec 1999 17:53:11 -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: Karl Auerbach <karl@CaveBear.com>
CC: DOMAIN-POLICY@LISTS.INTERNIC.NET, IFWP <list@ifwp.org>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>,
        ISI IPv6 list <6bone@ISI.EDU>, ietf@ietf.org
Subject: Re: RRP Specs
References: <Pine.LNX.4.10.9912231525440.8256-100000@npax.cavebear.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ipng@sunroof.eng.sun.com
Precedence: bulk
Status: O
X-Keywords:                  
X-UID: 3278
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Karl and all,

Karl Auerbach wrote:

> > NSI has made an I-D of the RRP Protocol.
> >
> > http://www.ietf.cnri.reston.va.us/internet-drafts/draft-hollenbeck-rrp-00.txt
>
> Am I missing something?  I looked through that and I see neither
> transaction identifiers nor timestamps.  That alone could make
> reconcilation of logs and post-mortem review of race conditions nearly
> impossible.

  Precisely correct here Karl, and one of many deficiencies in this
design document.  But of course this is one of several I had pointed
our some time ago before this document was published.  To no avail
of course.  It reminds me of the lame leading the blind.  And I believe
I amongst a few others made this reference before as well.

>
>
> And given the absence of a clear exchange between an existing registrar
> and a new one I see a HUGE door in the transfer mechanism for registrars
> to engage in what the long distance folks call "slamming" - the silent
> transfer of customers from one long-distance company or registry to
> another.

  And we have already seen this with respect to Register.com in this
context already.  More to come I am sure.

>
>
> And text based?  Wow, that's an open inviation to attacks based on buffer
> overrun and packets split at cr-lf boundaries.

  Not to mention several other text based security attacks.  The hack in these
instances is child's play really.

>
>
> And it is text based without any concern for internationalization.

  Good point here also. And one that slipped my mind...  >;)

>
>
> And its expiration date representation, although it is measured to the
> millisecond, fails to include a reference to any time zone.

  Tisk, tisk, indeed this is a good point as well.

>
>
> Nor does it handle IPv6.

  How true.

>
>
> Seems like a rather deficient design.

  Looks like a design by committee, and a very poorly technically informed
or knowledgeable one at that.

>
>
>                 --karl--

Regards,

--
Jeffrey A. Williams
Spokesman INEGroup (Over 95k members 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:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208


--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to majordomo@sunroof.eng.sun.com
--------------------------------------------------------------------



From owner-ietf-outbound  Sat Jan  8 03:01:46 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA16393
	for ietf-outbound.10@ietf.org; Sat, 8 Jan 2000 03:00:02 -0500 (EST)
Received: from internexus.net (IDENT:qmailr@internexus.net [206.152.14.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA16347
	for <ietf@ietf.org>; Sat, 8 Jan 2000 02:56:04 -0500 (EST)
Received: (qmail 22105 invoked by uid 8079); 8 Jan 2000 07:42:56 -0000
MBOX-Line: From owner-ipng@sunroof.eng.sun.com Fri Dec 24 00:17:53 1999
Delivered-To: ry@internexus.net
Received: (qmail 19741 invoked from network); 24 Dec 1999 00:17:52 -0000
Received: from mercury.sun.com (192.9.25.1)
  by internexus.net with SMTP; 24 Dec 1999 00:17:52 -0000
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA20093;
	Thu, 23 Dec 1999 16:07:02 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA13215;
	Thu, 23 Dec 1999 16:06:52 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) id dBO03E402721
	for ipng-dist; Thu, 23 Dec 1999 16:03:14 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) with ESMTP id dBO035Y02714
	for <ipng@sunroof.eng.sun.com>; Thu, 23 Dec 1999 16:03:06 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA01267
	for <ipng@sunroof.eng.sun.com>; Thu, 23 Dec 1999 16:03:05 -0800 (PST)
Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA06829
	for <ipng@sunroof.eng.sun.com>; Thu, 23 Dec 1999 16:03:04 -0800 (PST)
Received: from ix.netcom.com (user-33qscij.dialup.mindspring.com [199.174.50.83])
	by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA10829;
	Thu, 23 Dec 1999 19:02:52 -0500 (EST)
Message-ID: <3862D206.EBB787CD@ix.netcom.com>
Date: Thu, 23 Dec 1999 17:53:11 -0800
From: Jeff Williams <jwkckid1@ix.netcom.com>
Organization: INEGroup Spokesman
X-Mailer: Mozilla 4.08 [en] (Win95; U; 16bit)
MIME-Version: 1.0
CC: DOMAIN-POLICY@LISTS.INTERNIC.NET, IFWP <list@ifwp.org>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>,
        ISI IPv6 list <6bone@ISI.EDU>, ietf@ietf.org
Subject: Re: RRP Specs
References: <Pine.LNX.4.10.9912231525440.8256-100000@npax.cavebear.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ipng@sunroof.eng.sun.com
Precedence: bulk
Status: O
X-Keywords:                  
X-UID: 3278
To: ry@tmgi.com
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Karl and all,

Karl Auerbach wrote:

> > NSI has made an I-D of the RRP Protocol.
> >
> > http://www.ietf.cnri.reston.va.us/internet-drafts/draft-hollenbeck-rrp-00.txt
>
> Am I missing something?  I looked through that and I see neither
> transaction identifiers nor timestamps.  That alone could make
> reconcilation of logs and post-mortem review of race conditions nearly
> impossible.

  Precisely correct here Karl, and one of many deficiencies in this
design document.  But of course this is one of several I had pointed
our some time ago before this document was published.  To no avail
of course.  It reminds me of the lame leading the blind.  And I believe
I amongst a few others made this reference before as well.

>
>
> And given the absence of a clear exchange between an existing registrar
> and a new one I see a HUGE door in the transfer mechanism for registrars
> to engage in what the long distance folks call "slamming" - the silent
> transfer of customers from one long-distance company or registry to
> another.

  And we have already seen this with respect to Register.com in this
context already.  More to come I am sure.

>
>
> And text based?  Wow, that's an open inviation to attacks based on buffer
> overrun and packets split at cr-lf boundaries.

  Not to mention several other text based security attacks.  The hack in these
instances is child's play really.

>
>
> And it is text based without any concern for internationalization.

  Good point here also. And one that slipped my mind...  >;)

>
>
> And its expiration date representation, although it is measured to the
> millisecond, fails to include a reference to any time zone.

  Tisk, tisk, indeed this is a good point as well.

>
>
> Nor does it handle IPv6.

  How true.

>
>
> Seems like a rather deficient design.

  Looks like a design by committee, and a very poorly technically informed
or knowledgeable one at that.

>
>
>                 --karl--

Regards,

--
Jeffrey A. Williams
Spokesman INEGroup (Over 95k members 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:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208


--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to majordomo@sunroof.eng.sun.com
--------------------------------------------------------------------



From owner-ietf-outbound@ietf.org  Sat Jan  8 03:03:15 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16532
	for <ietf-web-archive@odin.ietf.org>; Sat, 8 Jan 2000 03:03:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA06901;
	Sat, 8 Jan 2000 03:02:11 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA16393
	for ietf-outbound.10@ietf.org; Sat, 8 Jan 2000 03:00:02 -0500 (EST)
Received: from internexus.net (IDENT:qmailr@internexus.net [206.152.14.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA16347
	for <ietf@ietf.org>; Sat, 8 Jan 2000 02:56:04 -0500 (EST)
Received: (qmail 22105 invoked by uid 8079); 8 Jan 2000 07:42:56 -0000
MBOX-Line: From owner-ipng@sunroof.eng.sun.com Fri Dec 24 00:17:53 1999
Delivered-To: ry@internexus.net
Received: (qmail 19741 invoked from network); 24 Dec 1999 00:17:52 -0000
Received: from mercury.sun.com (192.9.25.1)
  by internexus.net with SMTP; 24 Dec 1999 00:17:52 -0000
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA20093;
	Thu, 23 Dec 1999 16:07:02 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA13215;
	Thu, 23 Dec 1999 16:06:52 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) id dBO03E402721
	for ipng-dist; Thu, 23 Dec 1999 16:03:14 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) with ESMTP id dBO035Y02714
	for <ipng@sunroof.eng.sun.com>; Thu, 23 Dec 1999 16:03:06 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA01267
	for <ipng@sunroof.eng.sun.com>; Thu, 23 Dec 1999 16:03:05 -0800 (PST)
Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA06829
	for <ipng@sunroof.eng.sun.com>; Thu, 23 Dec 1999 16:03:04 -0800 (PST)
Received: from ix.netcom.com (user-33qscij.dialup.mindspring.com [199.174.50.83])
	by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA10829;
	Thu, 23 Dec 1999 19:02:52 -0500 (EST)
Message-ID: <3862D206.EBB787CD@ix.netcom.com>
Date: Thu, 23 Dec 1999 17:53:11 -0800
From: Jeff Williams <jwkckid1@ix.netcom.com>
Organization: INEGroup Spokesman
X-Mailer: Mozilla 4.08 [en] (Win95; U; 16bit)
MIME-Version: 1.0
CC: DOMAIN-POLICY@LISTS.INTERNIC.NET, IFWP <list@ifwp.org>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>,
        ISI IPv6 list <6bone@ISI.EDU>, ietf@ietf.org
Subject: Re: RRP Specs
References: <Pine.LNX.4.10.9912231525440.8256-100000@npax.cavebear.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ipng@sunroof.eng.sun.com
Precedence: bulk
Status: O
X-Keywords:                  
X-UID: 3278
To: ry@tmgi.com
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Karl and all,

Karl Auerbach wrote:

> > NSI has made an I-D of the RRP Protocol.
> >
> > http://www.ietf.cnri.reston.va.us/internet-drafts/draft-hollenbeck-rrp-00.txt
>
> Am I missing something?  I looked through that and I see neither
> transaction identifiers nor timestamps.  That alone could make
> reconcilation of logs and post-mortem review of race conditions nearly
> impossible.

  Precisely correct here Karl, and one of many deficiencies in this
design document.  But of course this is one of several I had pointed
our some time ago before this document was published.  To no avail
of course.  It reminds me of the lame leading the blind.  And I believe
I amongst a few others made this reference before as well.

>
>
> And given the absence of a clear exchange between an existing registrar
> and a new one I see a HUGE door in the transfer mechanism for registrars
> to engage in what the long distance folks call "slamming" - the silent
> transfer of customers from one long-distance company or registry to
> another.

  And we have already seen this with respect to Register.com in this
context already.  More to come I am sure.

>
>
> And text based?  Wow, that's an open inviation to attacks based on buffer
> overrun and packets split at cr-lf boundaries.

  Not to mention several other text based security attacks.  The hack in these
instances is child's play really.

>
>
> And it is text based without any concern for internationalization.

  Good point here also. And one that slipped my mind...  >;)

>
>
> And its expiration date representation, although it is measured to the
> millisecond, fails to include a reference to any time zone.

  Tisk, tisk, indeed this is a good point as well.

>
>
> Nor does it handle IPv6.

  How true.

>
>
> Seems like a rather deficient design.

  Looks like a design by committee, and a very poorly technically informed
or knowledgeable one at that.

>
>
>                 --karl--

Regards,

--
Jeffrey A. Williams
Spokesman INEGroup (Over 95k members 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:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208


--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to majordomo@sunroof.eng.sun.com
--------------------------------------------------------------------



From owner-ietf-outbound  Mon Jan 10 15:42:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA11955
	for ietf-outbound.10@ietf.org; Mon, 10 Jan 2000 15:40:02 -0500 (EST)
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11873
	for <ietf@ietf.org>; Mon, 10 Jan 2000 15:34:05 -0500 (EST)
Received: from sunmail1.Sun.COM ([129.145.1.2])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA28728
	for <ietf@ietf.org>; Mon, 10 Jan 2000 13:34:05 -0700 (MST)
Received: from jurassic.eng.sun.com (jurassic.Eng.Sun.COM [129.146.82.166])
	by sunmail1.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6.1-sunmail1) with ESMTP id MAA07792
	for <ietf@ietf.org>; Mon, 10 Jan 2000 12:34:03 -0800 (PST)
Received: from gweilo (gweilo.Eng.Sun.COM [129.146.88.88])
	by jurassic.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id MAA04195
	for <ietf@ietf.org>; Mon, 10 Jan 2000 12:34:03 -0800 (PST)
Message-Id: <200001102034.MAA04195@jurassic.eng.sun.com>
Date: Mon, 10 Jan 2000 12:33:55 -0800 (PST)
From: Michael Condry <Michael.Condry@eng.sun.com>
Reply-To: Michael Condry <Michael.Condry@eng.sun.com>
Subject: Meeting for interested Parties
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: ohGngxbyXxgyJ0jAlB1eMg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4 SunOS 5.8 sun4u sparc 



We are holding an open meeting to disucss ecommerce data exchange
problems and techniques. In IETF47 there will be a BOF
on this area and material discussed will hopefully 
assist this.

The problem areas being addressed:

     Particularly in the ecommerce area, there is a rapidly growing need to
exchange data between applications. XML, as an application-neutral and
metadata-aware medium, is used to describe and express the data. For various
application areas, there are industry consortiums and other bodies defining
schema, but currently there is no common underlying protocol for transmisson
of the data. 
     Existing protocols for RPC or object invocation - such as IIOP and DCOM -
appear to have enough difficulties so that other WEB approaches need to be
evaluated. SOAP is an example technology that will be 
examined.

Our meeting will discuss this problem space and related technologies.

When: Tuesday, January 25th, 2000
Where: Netscape

       The Sputnik conference room
       Building 22, first floor
       Netscape Communications Corp.
       468 Ellis Street
       Mountain View, CA  94043

All interested parties may attend, please contact michael.condry@sun.com if
you would like to attend.




From owner-ietf-outbound@ietf.org  Mon Jan 10 15:44:38 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12051
	for <ietf-web-archive@odin.ietf.org>; Mon, 10 Jan 2000 15:44:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA15381;
	Mon, 10 Jan 2000 15:43:10 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA11955
	for ietf-outbound.10@ietf.org; Mon, 10 Jan 2000 15:40:02 -0500 (EST)
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11873
	for <ietf@ietf.org>; Mon, 10 Jan 2000 15:34:05 -0500 (EST)
Received: from sunmail1.Sun.COM ([129.145.1.2])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA28728
	for <ietf@ietf.org>; Mon, 10 Jan 2000 13:34:05 -0700 (MST)
Received: from jurassic.eng.sun.com (jurassic.Eng.Sun.COM [129.146.82.166])
	by sunmail1.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6.1-sunmail1) with ESMTP id MAA07792
	for <ietf@ietf.org>; Mon, 10 Jan 2000 12:34:03 -0800 (PST)
Received: from gweilo (gweilo.Eng.Sun.COM [129.146.88.88])
	by jurassic.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id MAA04195
	for <ietf@ietf.org>; Mon, 10 Jan 2000 12:34:03 -0800 (PST)
Message-Id: <200001102034.MAA04195@jurassic.eng.sun.com>
Date: Mon, 10 Jan 2000 12:33:55 -0800 (PST)
From: Michael Condry <Michael.Condry@eng.sun.com>
Reply-To: Michael Condry <Michael.Condry@eng.sun.com>
Subject: Meeting for interested Parties
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: ohGngxbyXxgyJ0jAlB1eMg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4 SunOS 5.8 sun4u sparc 



We are holding an open meeting to disucss ecommerce data exchange
problems and techniques. In IETF47 there will be a BOF
on this area and material discussed will hopefully 
assist this.

The problem areas being addressed:

     Particularly in the ecommerce area, there is a rapidly growing need to
exchange data between applications. XML, as an application-neutral and
metadata-aware medium, is used to describe and express the data. For various
application areas, there are industry consortiums and other bodies defining
schema, but currently there is no common underlying protocol for transmisson
of the data. 
     Existing protocols for RPC or object invocation - such as IIOP and DCOM -
appear to have enough difficulties so that other WEB approaches need to be
evaluated. SOAP is an example technology that will be 
examined.

Our meeting will discuss this problem space and related technologies.

When: Tuesday, January 25th, 2000
Where: Netscape

       The Sputnik conference room
       Building 22, first floor
       Netscape Communications Corp.
       468 Ellis Street
       Mountain View, CA  94043

All interested parties may attend, please contact michael.condry@sun.com if
you would like to attend.




From owner-ietf-outbound  Wed Jan 12 02:01:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA02267
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 02:00:03 -0500 (EST)
Received: from maxis_vw01.maxisnet.com.my (maxis-em01.maxisnet.com.my [202.190.228.101])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA01757
	for <ietf@ietf.org>; Wed, 12 Jan 2000 01:53:05 -0500 (EST)
Received: from SUBGTD-Message_Server by maxis.com.my
	with Novell_GroupWise; Wed, 12 Jan 2000 14:50:49 +0800
Message-Id: <s87c94c9.095@maxis.com.my>
X-Mailer: Novell GroupWise 5.2
Date: Wed, 12 Jan 2000 14:50:41 +0800
From: "Manohar Menon" <MMANO@maxis.com.my>
To: a.saha@acm.org, L.Wood@eim.surrey.ac.uk, eep1lw@surrey.ac.uk
Cc: ietf@ietf.org, Sathish.Nagappa@schwab.com
Subject: Re: RE: WAP
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA01757
Content-Transfer-Encoding: 8bit

dear folks

 Well as it s a fortune to join the WAP forum, and the most i can get from vendors are the marketing details and limited sets of technical details, therefore can anyone of you provide some background on how implementation of WAP and taken into consideration of future roll outs of GPRS.

 

Thanks and Best Regards

Manohar Menon
System Engineer
FNPP - DECS
Subang Hitech
Tel :+6 03  580 1697 
email: mmano@maxisnet.com.my
Fax : +6 03 580 2003

>>> Lloyd Wood <eep1lw@surrey.ac.uk> 12/16 8:14 PM >>>
On Thu, 16 Dec 1999 amlan@geektown.net wrote:

>     [ From: <eep1lw@surrey.ac.uk> ]
>     [ Date: 21:43:30 (+0000) 15 December 1999  ]
> 
>     > On Wed, 15 Dec 1999, Nagappa, Sathish wrote:
> 
>     > > More geared towards corporate
>     > > memberships than individuals, it looks like.
>     > 
>     > Well, how many individuals own cellphone manufacturing plants?
>     >  
>     > L.
> 
> Duh ! You do not need to own a cellphone manufacturing plant to
> implement the WAP standard for a WAP server, or do you ?

No. (You probably need to own a cellphone manufacturing plant to think
implementing the WAP standard for a WAP server is a good idea, though,
and so that you're less likely to be caught out by developments in
the standards. If you read the WAP documents at
http://www.wapforum.com/what/technical.htm you'll see e.g.
'Disclaimer: this document is subject to change without notice' on
(self-)approved standards. Encouraging.)


> Going by the same logic, W3C, then should start asking for $50000,
> with the reasoning that not every individual has the need for a
> webserver. 

It does, as Martin points out.


> IMNHO, any standard should be open and freely accessible to anyone
> who wants to implement it. 

ISO would beg to differ. Not free, and input is heavily constrained.

L.

there's an 'as in bloodflow to the neck' line in here somewhere.

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






From owner-ietf-outbound@ietf.org  Wed Jan 12 02:04:44 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07914
	for <ietf-web-archive@odin.ietf.org>; Wed, 12 Jan 2000 02:04:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA28561;
	Wed, 12 Jan 2000 02:03:10 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id CAA02267
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 02:00:03 -0500 (EST)
Received: from maxis_vw01.maxisnet.com.my (maxis-em01.maxisnet.com.my [202.190.228.101])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA01757
	for <ietf@ietf.org>; Wed, 12 Jan 2000 01:53:05 -0500 (EST)
Received: from SUBGTD-Message_Server by maxis.com.my
	with Novell_GroupWise; Wed, 12 Jan 2000 14:50:49 +0800
Message-Id: <s87c94c9.095@maxis.com.my>
X-Mailer: Novell GroupWise 5.2
Date: Wed, 12 Jan 2000 14:50:41 +0800
From: "Manohar Menon" <MMANO@maxis.com.my>
To: a.saha@acm.org, L.Wood@eim.surrey.ac.uk, eep1lw@surrey.ac.uk
Cc: ietf@ietf.org, Sathish.Nagappa@schwab.com
Subject: Re: RE: WAP
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA01757
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

dear folks

 Well as it s a fortune to join the WAP forum, and the most i can get from vendors are the marketing details and limited sets of technical details, therefore can anyone of you provide some background on how implementation of WAP and taken into consideration of future roll outs of GPRS.

 

Thanks and Best Regards

Manohar Menon
System Engineer
FNPP - DECS
Subang Hitech
Tel :+6 03  580 1697 
email: mmano@maxisnet.com.my
Fax : +6 03 580 2003

>>> Lloyd Wood <eep1lw@surrey.ac.uk> 12/16 8:14 PM >>>
On Thu, 16 Dec 1999 amlan@geektown.net wrote:

>     [ From: <eep1lw@surrey.ac.uk> ]
>     [ Date: 21:43:30 (+0000) 15 December 1999  ]
> 
>     > On Wed, 15 Dec 1999, Nagappa, Sathish wrote:
> 
>     > > More geared towards corporate
>     > > memberships than individuals, it looks like.
>     > 
>     > Well, how many individuals own cellphone manufacturing plants?
>     >  
>     > L.
> 
> Duh ! You do not need to own a cellphone manufacturing plant to
> implement the WAP standard for a WAP server, or do you ?

No. (You probably need to own a cellphone manufacturing plant to think
implementing the WAP standard for a WAP server is a good idea, though,
and so that you're less likely to be caught out by developments in
the standards. If you read the WAP documents at
http://www.wapforum.com/what/technical.htm you'll see e.g.
'Disclaimer: this document is subject to change without notice' on
(self-)approved standards. Encouraging.)


> Going by the same logic, W3C, then should start asking for $50000,
> with the reasoning that not every individual has the need for a
> webserver. 

It does, as Martin points out.


> IMNHO, any standard should be open and freely accessible to anyone
> who wants to implement it. 

ISO would beg to differ. Not free, and input is heavily constrained.

L.

there's an 'as in bloodflow to the neck' line in here somewhere.

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






From owner-ietf-outbound  Wed Jan 12 13:12:01 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA20993
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 13:10:02 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA20932;
	Wed, 12 Jan 2000 13:07:49 -0500 (EST)
Date: Wed, 12 Jan 2000 13:07:49 -0500 (EST)
Message-Id: <200001121807.NAA20932@ietf.org>
X-Authentication-Warning: ietf.org: majordom set sender to Majordomo-Owner@ietf.org using -f
To: mailto:ietf@ietf.org
From: Majordomo@ietf.org
Subject: Confirmation for subscribe ietf
Reply-To: Majordomo@ietf.org

--

Someone (possibly you) has requested that your email address be added
to or deleted from the mailing list "ietf@ietf.org".

If you really want this action to be taken, please send the following
commands (exactly as shown) back to "Majordomo@ietf.org":

	auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org

If you do not want this action to be taken, simply ignore this message
and the request will be disregarded.

If your mailer will not allow you to send the entire command as a single
line, you may split it using backslashes, like so:

        auth 36dbe6c3 subscribe ietf \
        mailto:ietf@ietf.org

If you have any questions about the policy of the list owner, please
contact "ietf-approval@ietf.org".

Thanks!

Majordomo@ietf.org



From owner-ietf-outbound@ietf.org  Wed Jan 12 13:16:11 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21098
	for <ietf-web-archive@odin.ietf.org>; Wed, 12 Jan 2000 13:16:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA16801;
	Wed, 12 Jan 2000 13:14:41 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA20993
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 13:10:02 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA20932;
	Wed, 12 Jan 2000 13:07:49 -0500 (EST)
Date: Wed, 12 Jan 2000 13:07:49 -0500 (EST)
Message-Id: <200001121807.NAA20932@ietf.org>
X-Authentication-Warning: ietf.org: majordom set sender to Majordomo-Owner@ietf.org using -f
To: mailto:ietf@ietf.org
From: Majordomo@ietf.org
Subject: Confirmation for subscribe ietf
Reply-To: Majordomo@ietf.org

--

Someone (possibly you) has requested that your email address be added
to or deleted from the mailing list "ietf@ietf.org".

If you really want this action to be taken, please send the following
commands (exactly as shown) back to "Majordomo@ietf.org":

	auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org

If you do not want this action to be taken, simply ignore this message
and the request will be disregarded.

If your mailer will not allow you to send the entire command as a single
line, you may split it using backslashes, like so:

        auth 36dbe6c3 subscribe ietf \
        mailto:ietf@ietf.org

If you have any questions about the policy of the list owner, please
contact "ietf-approval@ietf.org".

Thanks!

Majordomo@ietf.org



From owner-ietf-outbound  Wed Jan 12 13:50:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA21773
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 13:50:03 -0500 (EST)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21630
	for <ietf@ietf.org>; Wed, 12 Jan 2000 13:43:41 -0500 (EST)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.1b+Sun/8.9.1) with SMTP id MAA12886
	for <ietf@ietf.org>; Wed, 12 Jan 2000 12:41:20 -0600 (CST)
Message-Id: <200001121841.MAA12886@rgfsparc.cr.usgs.gov>
Date: Wed, 12 Jan 2000 12:41:20 -0600 (CST)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: Confirmation for subscribe ietf
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 4XDxrhoEP7lyDWQrEJdg/g==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 

>Someone (possibly you) has requested that your email address be added
>to or deleted from the mailing list "ietf@ietf.org".

Pretty slick trick: a mailing list asking to be added to itself.

RGF

Robert G. Ferrell
Internet Technologist
National Business Center, US DoI
Robert_G_Ferrell@nbc.gov



From owner-ietf-outbound@ietf.org  Wed Jan 12 13:53:39 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21849
	for <ietf-web-archive@odin.ietf.org>; Wed, 12 Jan 2000 13:53:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA17533;
	Wed, 12 Jan 2000 13:52:10 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA21773
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 13:50:03 -0500 (EST)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21630
	for <ietf@ietf.org>; Wed, 12 Jan 2000 13:43:41 -0500 (EST)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.1b+Sun/8.9.1) with SMTP id MAA12886
	for <ietf@ietf.org>; Wed, 12 Jan 2000 12:41:20 -0600 (CST)
Message-Id: <200001121841.MAA12886@rgfsparc.cr.usgs.gov>
Date: Wed, 12 Jan 2000 12:41:20 -0600 (CST)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: Confirmation for subscribe ietf
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 4XDxrhoEP7lyDWQrEJdg/g==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 

>Someone (possibly you) has requested that your email address be added
>to or deleted from the mailing list "ietf@ietf.org".

Pretty slick trick: a mailing list asking to be added to itself.

RGF

Robert G. Ferrell
Internet Technologist
National Business Center, US DoI
Robert_G_Ferrell@nbc.gov



From owner-ietf-outbound  Wed Jan 12 14:10:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA22230
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 14:10:02 -0500 (EST)
Received: from mlsrv1.avici.com ([208.246.215.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22113
	for <ietf@ietf.org>; Wed, 12 Jan 2000 14:05:27 -0500 (EST)
Received: from avici.com (infosys-pc6.avici.com [10.1.1.119])
          by mlsrv1.avici.com (8.8.5/8.8.4) with ESMTP
	  id OAA10915 for <ietf@ietf.org>; Wed, 12 Jan 2000 14:04:43 -0500 (EST)
Message-ID: <387CD04B.C051C53D@avici.com>
Date: Wed, 12 Jan 2000 14:04:43 -0500
From: Lakshmi <lakshmi@avici.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit






From owner-ietf-outbound@ietf.org  Wed Jan 12 14:12:47 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22301
	for <ietf-web-archive@odin.ietf.org>; Wed, 12 Jan 2000 14:12:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17976;
	Wed, 12 Jan 2000 14:11:17 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA22230
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 14:10:02 -0500 (EST)
Received: from mlsrv1.avici.com ([208.246.215.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22113
	for <ietf@ietf.org>; Wed, 12 Jan 2000 14:05:27 -0500 (EST)
Received: from avici.com (infosys-pc6.avici.com [10.1.1.119])
          by mlsrv1.avici.com (8.8.5/8.8.4) with ESMTP
	  id OAA10915 for <ietf@ietf.org>; Wed, 12 Jan 2000 14:04:43 -0500 (EST)
Message-ID: <387CD04B.C051C53D@avici.com>
Date: Wed, 12 Jan 2000 14:04:43 -0500
From: Lakshmi <lakshmi@avici.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit






From owner-ietf-outbound  Wed Jan 12 14:20:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA22441
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 14:20:02 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA22144;
	Wed, 12 Jan 2000 14:06:14 -0500 (EST)
Date: Wed, 12 Jan 2000 14:06:14 -0500 (EST)
Message-Id: <200001121906.OAA22144@ietf.org>
X-Authentication-Warning: ietf.org: majordom set sender to Majordomo-Owner@ietf.org using -f
To: mailto:ietf@ietf.org
From: Majordomo@ietf.org
Subject: Confirmation for subscribe ietf
Reply-To: Majordomo@ietf.org

--

Someone (possibly you) has requested that your email address be added
to or deleted from the mailing list "ietf@ietf.org".

If you really want this action to be taken, please send the following
commands (exactly as shown) back to "Majordomo@ietf.org":

	auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org

If you do not want this action to be taken, simply ignore this message
and the request will be disregarded.

If your mailer will not allow you to send the entire command as a single
line, you may split it using backslashes, like so:

        auth 36dbe6c3 subscribe ietf \
        mailto:ietf@ietf.org

If you have any questions about the policy of the list owner, please
contact "ietf-approval@ietf.org".

Thanks!

Majordomo@ietf.org



From owner-ietf-outbound@ietf.org  Wed Jan 12 14:23:28 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22568
	for <ietf-web-archive@odin.ietf.org>; Wed, 12 Jan 2000 14:23:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA18212;
	Wed, 12 Jan 2000 14:21:55 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA22441
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 14:20:02 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA22144;
	Wed, 12 Jan 2000 14:06:14 -0500 (EST)
Date: Wed, 12 Jan 2000 14:06:14 -0500 (EST)
Message-Id: <200001121906.OAA22144@ietf.org>
X-Authentication-Warning: ietf.org: majordom set sender to Majordomo-Owner@ietf.org using -f
To: mailto:ietf@ietf.org
From: Majordomo@ietf.org
Subject: Confirmation for subscribe ietf
Reply-To: Majordomo@ietf.org

--

Someone (possibly you) has requested that your email address be added
to or deleted from the mailing list "ietf@ietf.org".

If you really want this action to be taken, please send the following
commands (exactly as shown) back to "Majordomo@ietf.org":

	auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org

If you do not want this action to be taken, simply ignore this message
and the request will be disregarded.

If your mailer will not allow you to send the entire command as a single
line, you may split it using backslashes, like so:

        auth 36dbe6c3 subscribe ietf \
        mailto:ietf@ietf.org

If you have any questions about the policy of the list owner, please
contact "ietf-approval@ietf.org".

Thanks!

Majordomo@ietf.org



From owner-ietf-outbound  Wed Jan 12 14:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA22693
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 14:30:02 -0500 (EST)
Received: from thresher.paymentech.com (gatekeeper.paymentech.com [206.50.182.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22276
	for <ietf@ietf.org>; Wed, 12 Jan 2000 14:11:28 -0500 (EST)
Received: (from uucp@localhost)
	by thresher.paymentech.com (8.8.5/8.8.5) id NAA01849
	for <ietf@ietf.org>; Wed, 12 Jan 2000 13:09:49 -0600 (CST)
Received: from dallas(172.16.6.28) by thresher.paymentech.com via smap (V2.0)
	id xma001721; Wed, 12 Jan 00 13:09:06 -0600
Received: by dallas.paymentech.com with Internet Mail Service (5.5.2448.0)
	id <CY1Y8XX6>; Wed, 12 Jan 2000 13:10:00 -0600
Message-ID: <78AD370E1BA3D011826700AA00C9DF9102D5C399@dallas.paymentech.com>
From: "Hipp, Ben" <BHipp@Paymentech.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Date: Wed, 12 Jan 2000 13:10:00 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"

auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org <mailto:ietf@ietf.org>
<mailto:ietf@ietf.org <mailto:ietf@ietf.org> >



From owner-ietf-outbound@ietf.org  Wed Jan 12 14:32:14 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22819
	for <ietf-web-archive@odin.ietf.org>; Wed, 12 Jan 2000 14:32:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA18449;
	Wed, 12 Jan 2000 14:30:50 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA22693
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 14:30:02 -0500 (EST)
Received: from thresher.paymentech.com (gatekeeper.paymentech.com [206.50.182.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22276
	for <ietf@ietf.org>; Wed, 12 Jan 2000 14:11:28 -0500 (EST)
Received: (from uucp@localhost)
	by thresher.paymentech.com (8.8.5/8.8.5) id NAA01849
	for <ietf@ietf.org>; Wed, 12 Jan 2000 13:09:49 -0600 (CST)
Received: from dallas(172.16.6.28) by thresher.paymentech.com via smap (V2.0)
	id xma001721; Wed, 12 Jan 00 13:09:06 -0600
Received: by dallas.paymentech.com with Internet Mail Service (5.5.2448.0)
	id <CY1Y8XX6>; Wed, 12 Jan 2000 13:10:00 -0600
Message-ID: <78AD370E1BA3D011826700AA00C9DF9102D5C399@dallas.paymentech.com>
From: "Hipp, Ben" <BHipp@Paymentech.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Date: Wed, 12 Jan 2000 13:10:00 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"

auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org <mailto:ietf@ietf.org>
<mailto:ietf@ietf.org <mailto:ietf@ietf.org> >



From owner-ietf-outbound  Wed Jan 12 14:50:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA23161
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 14:50:02 -0500 (EST)
Received: from socrates.nmia.com (socrates.nmia.com [198.59.166.170])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA23109
	for <ietf@ietf.org>; Wed, 12 Jan 2000 14:48:36 -0500 (EST)
Received: from computer(really [207.66.87.143]) by socrates.nmia.com
	via sendmail with smtp
	id <m128Tks-002xe0C@socrates.nmia.com>
	for <ietf@ietf.org>; Wed, 12 Jan 2000 12:48:30 -0700 (MST)
	(Smail-3.2.0.106 1999-Mar-31 #3 built 1999-Apr-19)
Message-Id: <3.0.6.32.20000112124532.007e0210@pop.nmia.com>
X-Sender: johngee@pop.nmia.com
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Wed, 12 Jan 2000 12:45:32 -0700
To: ietf@ietf.org
From: John Geddie <johngee@nmia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

auth 36dbe6c3 subscribe ietf



From owner-ietf-outbound@ietf.org  Wed Jan 12 14:53:31 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23260
	for <ietf-web-archive@odin.ietf.org>; Wed, 12 Jan 2000 14:53:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA18891;
	Wed, 12 Jan 2000 14:52:07 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA23161
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 14:50:02 -0500 (EST)
Received: from socrates.nmia.com (socrates.nmia.com [198.59.166.170])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA23109
	for <ietf@ietf.org>; Wed, 12 Jan 2000 14:48:36 -0500 (EST)
Received: from computer(really [207.66.87.143]) by socrates.nmia.com
	via sendmail with smtp
	id <m128Tks-002xe0C@socrates.nmia.com>
	for <ietf@ietf.org>; Wed, 12 Jan 2000 12:48:30 -0700 (MST)
	(Smail-3.2.0.106 1999-Mar-31 #3 built 1999-Apr-19)
Message-Id: <3.0.6.32.20000112124532.007e0210@pop.nmia.com>
X-Sender: johngee@pop.nmia.com
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Wed, 12 Jan 2000 12:45:32 -0700
To: ietf@ietf.org
From: John Geddie <johngee@nmia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

auth 36dbe6c3 subscribe ietf



From owner-ietf-outbound  Wed Jan 12 15:10:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23710
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 15:10:02 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23567;
	Wed, 12 Jan 2000 15:02:32 -0500 (EST)
Date: Wed, 12 Jan 2000 15:02:32 -0500 (EST)
Message-Id: <200001122002.PAA23567@ietf.org>
X-Authentication-Warning: ietf.org: majordom set sender to Majordomo-Owner@ietf.org using -f
To: mailto:ietf@ietf.org
From: Majordomo@ietf.org
Subject: Confirmation for subscribe ietf
Reply-To: Majordomo@ietf.org

--

Someone (possibly you) has requested that your email address be added
to or deleted from the mailing list "ietf@ietf.org".

If you really want this action to be taken, please send the following
commands (exactly as shown) back to "Majordomo@ietf.org":

	auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org

If you do not want this action to be taken, simply ignore this message
and the request will be disregarded.

If your mailer will not allow you to send the entire command as a single
line, you may split it using backslashes, like so:

        auth 36dbe6c3 subscribe ietf \
        mailto:ietf@ietf.org

If you have any questions about the policy of the list owner, please
contact "ietf-approval@ietf.org".

Thanks!

Majordomo@ietf.org



From owner-ietf-outbound@ietf.org  Wed Jan 12 15:13:19 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23769
	for <ietf-web-archive@odin.ietf.org>; Wed, 12 Jan 2000 15:13:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19504;
	Wed, 12 Jan 2000 15:11:51 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23710
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 15:10:02 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23567;
	Wed, 12 Jan 2000 15:02:32 -0500 (EST)
Date: Wed, 12 Jan 2000 15:02:32 -0500 (EST)
Message-Id: <200001122002.PAA23567@ietf.org>
X-Authentication-Warning: ietf.org: majordom set sender to Majordomo-Owner@ietf.org using -f
To: mailto:ietf@ietf.org
From: Majordomo@ietf.org
Subject: Confirmation for subscribe ietf
Reply-To: Majordomo@ietf.org

--

Someone (possibly you) has requested that your email address be added
to or deleted from the mailing list "ietf@ietf.org".

If you really want this action to be taken, please send the following
commands (exactly as shown) back to "Majordomo@ietf.org":

	auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org

If you do not want this action to be taken, simply ignore this message
and the request will be disregarded.

If your mailer will not allow you to send the entire command as a single
line, you may split it using backslashes, like so:

        auth 36dbe6c3 subscribe ietf \
        mailto:ietf@ietf.org

If you have any questions about the policy of the list owner, please
contact "ietf-approval@ietf.org".

Thanks!

Majordomo@ietf.org



From owner-ietf-outbound  Wed Jan 12 15:20:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23939
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 15:20:02 -0500 (EST)
Received: from scoya.cnri.reston.va.us (scoya.cnri.reston.va.us [10.27.5.106])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA23621
	for <ietf@ietf.org>; Wed, 12 Jan 2000 15:07:23 -0500 (EST)
Date: Wed, 12 Jan 2000 15:08:00 -0500 (Eastern Standard Time)
From: Steve Coya <scoya@ietf.org>
To: ietf@ietf.org
Subject: Majordomo subscribe request message
Message-ID: <Pine.WNT.3.96.1000112150332.-415101Q-100000@scoya.cnri.reston.va.us>
X-X-Sender: scoya@odin.cnri.reston.va.us
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Folks,

Please do NOT respond to the message from majordomo asking to confirm
adding ietf@ietf.org to ietf@ietf.org

We're not sure where this/these messages originated, but are looking into
it right now. 

Thanks and sorry for the inconvenience.



Steve



From owner-ietf-outbound@ietf.org  Wed Jan 12 15:22:15 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24016
	for <ietf-web-archive@odin.ietf.org>; Wed, 12 Jan 2000 15:22:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19737;
	Wed, 12 Jan 2000 15:20:44 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23939
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 15:20:02 -0500 (EST)
Received: from scoya.cnri.reston.va.us (scoya.cnri.reston.va.us [10.27.5.106])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA23621
	for <ietf@ietf.org>; Wed, 12 Jan 2000 15:07:23 -0500 (EST)
Date: Wed, 12 Jan 2000 15:08:00 -0500 (Eastern Standard Time)
From: Steve Coya <scoya@ietf.org>
To: ietf@ietf.org
Subject: Majordomo subscribe request message
Message-ID: <Pine.WNT.3.96.1000112150332.-415101Q-100000@scoya.cnri.reston.va.us>
X-X-Sender: scoya@odin.cnri.reston.va.us
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Folks,

Please do NOT respond to the message from majordomo asking to confirm
adding ietf@ietf.org to ietf@ietf.org

We're not sure where this/these messages originated, but are looking into
it right now. 

Thanks and sorry for the inconvenience.



Steve



From owner-ietf-outbound  Wed Jan 12 15:30:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA24191
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 15:30:01 -0500 (EST)
Received: from caesar.acns.carleton.edu (Caesar.ACNS.Carleton.edu [137.22.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23880
	for <ietf@ietf.org>; Wed, 12 Jan 2000 15:17:39 -0500 (EST)
From: allendor@carleton.edu
Received: from macallendor.res.carleton.edu
 (macAllendoR.Res.Carleton.edu [137.22.102.40])
 by carleton.edu (PMDF V5.2-32 #40542)
 with ESMTP id <0FO8004A1OCZTL@carleton.edu> for ietf@ietf.org; Wed,
 12 Jan 2000 14:17:23 -0600 (CST)
Date: Wed, 12 Jan 2000 14:17:03 -0600
Subject: auth 36dbe6c3 subscribe ietf
Originator-info: login-id=allendor; server=imap.carleton.edu
To: ietf@ietf.org
Message-id: <992555.3156675423@macallendor.res.carleton.edu>
MIME-version: 1.0
X-Mailer: Mulberry (MacOS) [1.4.4, s/n S-397003]
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

auth 36dbe6c3 subscribe ietf 




From owner-ietf-outbound@ietf.org  Wed Jan 12 15:32:12 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24325
	for <ietf-web-archive@odin.ietf.org>; Wed, 12 Jan 2000 15:32:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA20047;
	Wed, 12 Jan 2000 15:30:42 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA24191
	for ietf-outbound.10@ietf.org; Wed, 12 Jan 2000 15:30:01 -0500 (EST)
Received: from caesar.acns.carleton.edu (Caesar.ACNS.Carleton.edu [137.22.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23880
	for <ietf@ietf.org>; Wed, 12 Jan 2000 15:17:39 -0500 (EST)
From: allendor@carleton.edu
Received: from macallendor.res.carleton.edu
 (macAllendoR.Res.Carleton.edu [137.22.102.40])
 by carleton.edu (PMDF V5.2-32 #40542)
 with ESMTP id <0FO8004A1OCZTL@carleton.edu> for ietf@ietf.org; Wed,
 12 Jan 2000 14:17:23 -0600 (CST)
Date: Wed, 12 Jan 2000 14:17:03 -0600
Subject: auth 36dbe6c3 subscribe ietf
Originator-info: login-id=allendor; server=imap.carleton.edu
To: ietf@ietf.org
Message-id: <992555.3156675423@macallendor.res.carleton.edu>
MIME-version: 1.0
X-Mailer: Mulberry (MacOS) [1.4.4, s/n S-397003]
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

auth 36dbe6c3 subscribe ietf 




From owner-ietf-outbound  Thu Jan 13 00:32:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA01132
	for ietf-outbound.10@ietf.org; Thu, 13 Jan 2000 00:30:02 -0500 (EST)
Received: from relay1.bt.net (relay1.bt.net [194.72.6.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01100
	for <ietf@ietf.org>; Thu, 13 Jan 2000 00:26:33 -0500 (EST)
Received: from [194.74.75.47] (helo=wstaalnt544731)
	by relay1.bt.net with smtp (Exim 2.11 #1)
	id 128cmG-0005Pq-00
	for ietf@ietf.org; Thu, 13 Jan 2000 05:26:32 +0000
From: "Jim Dunn" <jim.dunn@bt.net>
To: <ietf@ietf.org>
Subject: RE: Majordomo subscribe request message
Date: Thu, 13 Jan 2000 05:28:07 -0000
Message-ID: <NDBBIPFKPKJBOCDKBOKOEEGECDAA.jim.dunn@bt.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 1 (Highest)
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <Pine.WNT.3.96.1000112150332.-415101Q-100000@scoya.cnri.reston.va.us>
Importance: High
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

I have recieved this same message three times at 18:45,19:41 & 20:32 Hrs GMT
respectively. Are any other IETF'ers seeing this pattern?

Is this a problem with majordomo or something more machivelian ?

Jim

-----Original Message-----
From: Steve Coya [mailto:scoya@ietf.org]
Sent: 12 January 2000 20:08
To: ietf@ietf.org
Subject: Majordomo subscribe request message



Folks,

Please do NOT respond to the message from majordomo asking to confirm
adding ietf@ietf.org to ietf@ietf.org

We're not sure where this/these messages originated, but are looking into
it right now.

Thanks and sorry for the inconvenience.



Steve



From owner-ietf-outbound@ietf.org  Thu Jan 13 00:34:20 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01242
	for <ietf-web-archive@odin.ietf.org>; Thu, 13 Jan 2000 00:34:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA06775;
	Thu, 13 Jan 2000 00:32:48 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id AAA01132
	for ietf-outbound.10@ietf.org; Thu, 13 Jan 2000 00:30:02 -0500 (EST)
Received: from relay1.bt.net (relay1.bt.net [194.72.6.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01100
	for <ietf@ietf.org>; Thu, 13 Jan 2000 00:26:33 -0500 (EST)
Received: from [194.74.75.47] (helo=wstaalnt544731)
	by relay1.bt.net with smtp (Exim 2.11 #1)
	id 128cmG-0005Pq-00
	for ietf@ietf.org; Thu, 13 Jan 2000 05:26:32 +0000
From: "Jim Dunn" <jim.dunn@bt.net>
To: <ietf@ietf.org>
Subject: RE: Majordomo subscribe request message
Date: Thu, 13 Jan 2000 05:28:07 -0000
Message-ID: <NDBBIPFKPKJBOCDKBOKOEEGECDAA.jim.dunn@bt.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 1 (Highest)
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <Pine.WNT.3.96.1000112150332.-415101Q-100000@scoya.cnri.reston.va.us>
Importance: High
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

I have recieved this same message three times at 18:45,19:41 & 20:32 Hrs GMT
respectively. Are any other IETF'ers seeing this pattern?

Is this a problem with majordomo or something more machivelian ?

Jim

-----Original Message-----
From: Steve Coya [mailto:scoya@ietf.org]
Sent: 12 January 2000 20:08
To: ietf@ietf.org
Subject: Majordomo subscribe request message



Folks,

Please do NOT respond to the message from majordomo asking to confirm
adding ietf@ietf.org to ietf@ietf.org

We're not sure where this/these messages originated, but are looking into
it right now.

Thanks and sorry for the inconvenience.



Steve



From owner-ietf-outbound  Thu Jan 13 11:12:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA20341
	for ietf-outbound.10@ietf.org; Thu, 13 Jan 2000 11:10:02 -0500 (EST)
Received: from mail.tobit.com ([62.52.79.114])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA20314
	for <ietf@ietf.org>; Thu, 13 Jan 2000 11:09:22 -0500 (EST)
From: tkuiper@tobit.com
Message-Id: <200001131609.LAA20314@ietf.org>
Subject: IPv6 private adresses space
To: ietf@ietf.org
Date: 13 Jan 00 16:09:26 UT
Priority: normal
X-Priority: 3 (Normal)
Importance: normal
X-Mailer: David by Tobit Software, Germany (PM-6.00a (0163))
X-David-Sym: 0
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1DD2510B41FE"


--------------1DD2510B41FE
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Is there such a thing for IPv6?

(like the 192.168.x.x and 172.10.x.x) in IPv4?

Gruss/Regards,
Thomas

Thomas Kuiper        |   tkuiper@tobit.com   |  www.tobit.com     __
Core Development     |   TK3680-RIPE         |                   /__/\
Tobit Software GmbH  |   ICQ #8345483        |  ask your server. \__\/



--------------1DD2510B41FE--



From owner-ietf-outbound@ietf.org  Thu Jan 13 11:20:13 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20540
	for <ietf-web-archive@odin.ietf.org>; Thu, 13 Jan 2000 11:20:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA00047;
	Thu, 13 Jan 2000 11:18:37 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id LAA20341
	for ietf-outbound.10@ietf.org; Thu, 13 Jan 2000 11:10:02 -0500 (EST)
Received: from mail.tobit.com ([62.52.79.114])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA20314
	for <ietf@ietf.org>; Thu, 13 Jan 2000 11:09:22 -0500 (EST)
From: tkuiper@tobit.com
Message-Id: <200001131609.LAA20314@ietf.org>
Subject: IPv6 private adresses space
To: ietf@ietf.org
Date: 13 Jan 00 16:09:26 UT
Priority: normal
X-Priority: 3 (Normal)
Importance: normal
X-Mailer: David by Tobit Software, Germany (PM-6.00a (0163))
X-David-Sym: 0
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1DD2510B41FE"


--------------1DD2510B41FE
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Is there such a thing for IPv6?

(like the 192.168.x.x and 172.10.x.x) in IPv4?

Gruss/Regards,
Thomas

Thomas Kuiper        |   tkuiper@tobit.com   |  www.tobit.com     __
Core Development     |   TK3680-RIPE         |                   /__/\
Tobit Software GmbH  |   ICQ #8345483        |  ask your server. \__\/



--------------1DD2510B41FE--



From owner-ietf-outbound  Thu Jan 13 12:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA21823
	for ietf-outbound.10@ietf.org; Thu, 13 Jan 2000 12:10:02 -0500 (EST)
Received: from zot.localdomain (IDENT:root@ip80.cvd1.rb1.bel.nwlink.com [209.20.183.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21559
	for <ietf@ietf.org>; Thu, 13 Jan 2000 12:00:41 -0500 (EST)
Received: from flash.localdomain (root@flash [10.0.0.6])
	by zot.localdomain (8.8.7/8.8.7) with ESMTP id JAA10424;
	Thu, 13 Jan 2000 09:00:40 -0800
Received: (from mark@localhost)
	by flash.localdomain (8.9.3/8.9.3) id JAA07746;
	Thu, 13 Jan 2000 09:00:51 -0800
To: tkuiper@tobit.com
Cc: ietf@ietf.org
Subject: Re: IPv6 private adresses space
References: <200001131609.LAA20314@ietf.org>
From: Mark Atwood <mra@pobox.com>
Date: 13 Jan 2000 09:00:51 -0800
In-Reply-To: tkuiper@tobit.com's message of "13 Jan 00 16:09:26 UT"
Message-ID: <m3iu0xzz24.fsf@flash.localdomain>
Lines: 14
X-Mailer: Gnus v5.5/Emacs 20.3

tkuiper@tobit.com writes:
> 
> Is there such a thing for IPv6?
> 
> (like the 192.168.x.x and 172.10.x.x) in IPv4?
> 

There's the link local and site local addresses.

-- 
Mark Atwood   | It is the hardest thing for intellectuals to understand, that
mra@pobox.com | just because they haven't thought of something, somebody else
              | might. <http://www.friesian.com/rifkin.htm>
http://www.pobox.com/~mra



From owner-ietf-outbound@ietf.org  Thu Jan 13 12:17:01 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21961
	for <ietf-web-archive@odin.ietf.org>; Thu, 13 Jan 2000 12:17:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA02164;
	Thu, 13 Jan 2000 12:15:32 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA21823
	for ietf-outbound.10@ietf.org; Thu, 13 Jan 2000 12:10:02 -0500 (EST)
Received: from zot.localdomain (IDENT:root@ip80.cvd1.rb1.bel.nwlink.com [209.20.183.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21559
	for <ietf@ietf.org>; Thu, 13 Jan 2000 12:00:41 -0500 (EST)
Received: from flash.localdomain (root@flash [10.0.0.6])
	by zot.localdomain (8.8.7/8.8.7) with ESMTP id JAA10424;
	Thu, 13 Jan 2000 09:00:40 -0800
Received: (from mark@localhost)
	by flash.localdomain (8.9.3/8.9.3) id JAA07746;
	Thu, 13 Jan 2000 09:00:51 -0800
To: tkuiper@tobit.com
Cc: ietf@ietf.org
Subject: Re: IPv6 private adresses space
References: <200001131609.LAA20314@ietf.org>
From: Mark Atwood <mra@pobox.com>
Date: 13 Jan 2000 09:00:51 -0800
In-Reply-To: tkuiper@tobit.com's message of "13 Jan 00 16:09:26 UT"
Message-ID: <m3iu0xzz24.fsf@flash.localdomain>
Lines: 14
X-Mailer: Gnus v5.5/Emacs 20.3

tkuiper@tobit.com writes:
> 
> Is there such a thing for IPv6?
> 
> (like the 192.168.x.x and 172.10.x.x) in IPv4?
> 

There's the link local and site local addresses.

-- 
Mark Atwood   | It is the hardest thing for intellectuals to understand, that
mra@pobox.com | just because they haven't thought of something, somebody else
              | might. <http://www.friesian.com/rifkin.htm>
http://www.pobox.com/~mra



From owner-ietf-outbound  Thu Jan 13 12:20:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA22012
	for ietf-outbound.10@ietf.org; Thu, 13 Jan 2000 12:20:02 -0500 (EST)
Received: from fw-es06.hac.com (fw-es06.HAC.COM [128.152.1.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21914
	for <ietf@ietf.org>; Thu, 13 Jan 2000 12:13:46 -0500 (EST)
From: Mark.Abinante@HSC.COM
Received: from ishs01.hsc.com (ishs01.hsc.com [147.20.2.20])
	by fw-es06.hac.com (8.9.1/8.9.1) with ESMTP id JAA21448
	for <ietf@ietf.org>; Thu, 13 Jan 2000 09:14:33 -0800 (PST)
Received: from Hughes.com (es-s25-mta5.HUGHES.COM [147.20.30.24])
	by ishs01.hsc.com (8.9.1/8.9.1) with SMTP id JAA19798
	for <ietf@ietf.org>; Thu, 13 Jan 2000 09:13:44 -0800 (PST)
Received: by Hughes.com(Lotus SMTP MTA v4.6.6  (890.1 7-16-1999))  id 88256865.005E989C ; Thu, 13 Jan 2000 09:13:14 -0800
X-Lotus-FromDomain: HUGHES
To: ietf@ietf.org
Message-ID: <88256865.005E97D7.00@Hughes.com>
Date: Thu, 13 Jan 2000 09:11:42 -0800
Subject: RE: Majordomo subscribe request message
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline




>Folks,
>I have recieved this same message three times at 18:45,19:41 & 20:32 Hrs GMT
>respectively. Are any other IETF'ers seeing this pattern?
>Is this a problem with majordomo or something more machivelian ?
>Jim

I received same messages.  It is either a bug or system-wide hack.  Nothing
against you personally...
-Mark




From owner-ietf-outbound@ietf.org  Thu Jan 13 12:26:58 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22208
	for <ietf-web-archive@odin.ietf.org>; Thu, 13 Jan 2000 12:26:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA02436;
	Thu, 13 Jan 2000 12:25:29 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA22012
	for ietf-outbound.10@ietf.org; Thu, 13 Jan 2000 12:20:02 -0500 (EST)
Received: from fw-es06.hac.com (fw-es06.HAC.COM [128.152.1.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21914
	for <ietf@ietf.org>; Thu, 13 Jan 2000 12:13:46 -0500 (EST)
From: Mark.Abinante@HSC.COM
Received: from ishs01.hsc.com (ishs01.hsc.com [147.20.2.20])
	by fw-es06.hac.com (8.9.1/8.9.1) with ESMTP id JAA21448
	for <ietf@ietf.org>; Thu, 13 Jan 2000 09:14:33 -0800 (PST)
Received: from Hughes.com (es-s25-mta5.HUGHES.COM [147.20.30.24])
	by ishs01.hsc.com (8.9.1/8.9.1) with SMTP id JAA19798
	for <ietf@ietf.org>; Thu, 13 Jan 2000 09:13:44 -0800 (PST)
Received: by Hughes.com(Lotus SMTP MTA v4.6.6  (890.1 7-16-1999))  id 88256865.005E989C ; Thu, 13 Jan 2000 09:13:14 -0800
X-Lotus-FromDomain: HUGHES
To: ietf@ietf.org
Message-ID: <88256865.005E97D7.00@Hughes.com>
Date: Thu, 13 Jan 2000 09:11:42 -0800
Subject: RE: Majordomo subscribe request message
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline




>Folks,
>I have recieved this same message three times at 18:45,19:41 & 20:32 Hrs GMT
>respectively. Are any other IETF'ers seeing this pattern?
>Is this a problem with majordomo or something more machivelian ?
>Jim

I received same messages.  It is either a bug or system-wide hack.  Nothing
against you personally...
-Mark




From owner-ietf-outbound  Thu Jan 13 12:50:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA22660
	for ietf-outbound.10@ietf.org; Thu, 13 Jan 2000 12:50:01 -0500 (EST)
Received: from snark.piermont.com (snark.piermont.com [206.1.51.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22585
	for <ietf@ietf.org>; Thu, 13 Jan 2000 12:44:59 -0500 (EST)
Received: by snark.piermont.com (Postfix, from userid 1000)
	id 1AAD91E00E3; Thu, 13 Jan 2000 12:44:59 -0500 (EST)
To: tkuiper@tobit.com
Cc: ietf@ietf.org
Subject: Re: IPv6 private adresses space
References: <200001131609.LAA20314@ietf.org>
From: "Perry E. Metzger" <perry@piermont.com>
Date: 13 Jan 2000 12:44:59 -0500
In-Reply-To: tkuiper@tobit.com's message of "13 Jan 00 16:09:26 UT"
Message-ID: <871z7lx3vo.fsf@snark.piermont.com>
Lines: 11
X-Mailer: Gnus v5.5/Emacs 20.3


tkuiper@tobit.com writes:
> Is there such a thing for IPv6?
> 
> (like the 192.168.x.x and 172.10.x.x) in IPv4?

The answer is that there have been proposals for such things, but Why
Would You Want Such An Abomination? You don't need it. There's no
shortage of space in v6 world.

Perry



From owner-ietf-outbound@ietf.org  Thu Jan 13 12:56:55 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22836
	for <ietf-web-archive@odin.ietf.org>; Thu, 13 Jan 2000 12:56:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA03458;
	Thu, 13 Jan 2000 12:55:23 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA22660
	for ietf-outbound.10@ietf.org; Thu, 13 Jan 2000 12:50:01 -0500 (EST)
Received: from snark.piermont.com (snark.piermont.com [206.1.51.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22585
	for <ietf@ietf.org>; Thu, 13 Jan 2000 12:44:59 -0500 (EST)
Received: by snark.piermont.com (Postfix, from userid 1000)
	id 1AAD91E00E3; Thu, 13 Jan 2000 12:44:59 -0500 (EST)
To: tkuiper@tobit.com
Cc: ietf@ietf.org
Subject: Re: IPv6 private adresses space
References: <200001131609.LAA20314@ietf.org>
From: "Perry E. Metzger" <perry@piermont.com>
Date: 13 Jan 2000 12:44:59 -0500
In-Reply-To: tkuiper@tobit.com's message of "13 Jan 00 16:09:26 UT"
Message-ID: <871z7lx3vo.fsf@snark.piermont.com>
Lines: 11
X-Mailer: Gnus v5.5/Emacs 20.3


tkuiper@tobit.com writes:
> Is there such a thing for IPv6?
> 
> (like the 192.168.x.x and 172.10.x.x) in IPv4?

The answer is that there have been proposals for such things, but Why
Would You Want Such An Abomination? You don't need it. There's no
shortage of space in v6 world.

Perry



From owner-ietf-outbound  Thu Jan 13 13:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA22909
	for ietf-outbound.10@ietf.org; Thu, 13 Jan 2000 13:00:03 -0500 (EST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22796
	for <ietf@ietf.org>; Thu, 13 Jan 2000 12:55:45 -0500 (EST)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id RAA26130; Thu, 13 Jan 2000 17:55:11 GMT
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id RAA23460; Thu, 13 Jan 2000 17:55:09 GMT
Message-ID: <387E1070.F8F8CCF8@hursley.ibm.com>
Date: Thu, 13 Jan 2000 11:50:40 -0600
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: tkuiper@tobit.com
CC: ietf@ietf.org
Subject: Re: IPv6 private adresses space
References: <200001131609.LAA20314@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Fortunately not, although link-local and site-local address formats 
are defined. I suggest that you read one of the IPv6 text books.

   Brian

tkuiper@tobit.com wrote:
> 
> Is there such a thing for IPv6?
> 
> (like the 192.168.x.x and 172.10.x.x) in IPv4?
> 
> Gruss/Regards,
> Thomas
> 
> Thomas Kuiper        |   tkuiper@tobit.com   |  www.tobit.com     __
> Core Development     |   TK3680-RIPE         |                   /__/\
> Tobit Software GmbH  |   ICQ #8345483        |  ask your server. \__\/



From owner-ietf-outbound@ietf.org  Thu Jan 13 13:06:15 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23093
	for <ietf-web-archive@odin.ietf.org>; Thu, 13 Jan 2000 13:06:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA03802;
	Thu, 13 Jan 2000 13:04:43 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA22909
	for ietf-outbound.10@ietf.org; Thu, 13 Jan 2000 13:00:03 -0500 (EST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22796
	for <ietf@ietf.org>; Thu, 13 Jan 2000 12:55:45 -0500 (EST)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id RAA26130; Thu, 13 Jan 2000 17:55:11 GMT
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id RAA23460; Thu, 13 Jan 2000 17:55:09 GMT
Message-ID: <387E1070.F8F8CCF8@hursley.ibm.com>
Date: Thu, 13 Jan 2000 11:50:40 -0600
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: tkuiper@tobit.com
CC: ietf@ietf.org
Subject: Re: IPv6 private adresses space
References: <200001131609.LAA20314@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Fortunately not, although link-local and site-local address formats 
are defined. I suggest that you read one of the IPv6 text books.

   Brian

tkuiper@tobit.com wrote:
> 
> Is there such a thing for IPv6?
> 
> (like the 192.168.x.x and 172.10.x.x) in IPv4?
> 
> Gruss/Regards,
> Thomas
> 
> Thomas Kuiper        |   tkuiper@tobit.com   |  www.tobit.com     __
> Core Development     |   TK3680-RIPE         |                   /__/\
> Tobit Software GmbH  |   ICQ #8345483        |  ask your server. \__\/



From owner-ietf-outbound  Fri Jan 14 17:11:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA23028
	for ietf-outbound.10@ietf.org; Fri, 14 Jan 2000 17:10:02 -0500 (EST)
Received: from musicyo2.musicyo.com (host-208-53-49-34.bluestar.net [208.53.49.34] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22938
	for <ietf@ietf.org>; Fri, 14 Jan 2000 17:04:06 -0500 (EST)
From: DocYo@musicyo.com
Received: from mail pickup service by musicyo2.musicyo.com with Microsoft SMTPSVC;
	 Fri, 14 Jan 2000 14:47:58 -0600
To: <ietf@ietf.org>
Subject: Greetings for MusicYo.com!
Date: Fri, 14 Jan 2000 14:47:58 -0600
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <03e5d5847200e10MUSICYO2@musicyo2.musicyo.com>

Dear ietf@ietf.org,

Greetings from www.MusicYo.com! Your only source for brand-name, brand-new
gear at factory-direct prices!

In case you haven't visited us lately, here's what's new!

WIN A KRAMER GUITAR!
--------------------
	* Stop by and enter to WIN a Kramer Baretta FX-404S guitar!
	  http://www.musicyo.com/freestuf.asp?target=freesuf%2Easp

PRODUCT NEWS!
-------------
On the product front we've now got IN STOCK AND READY FOR IMMEDIATE
PURCHASE...

	* Slingerland 5-pc Jam Session Drum Kits for $229
	  http://www.musicyo.com/product.asp?dept%5Fid=2&pf%5Fid=017


	* MusicYo Personal Guitar Amplifiers for $17.99
	  http://www.musicyo.com/product.asp?dept%5Fid=4&pf%5Fid=223


	* Celestion G12T-75 Speakers for $49.99
	  http://www.musicyo.com/product.asp?dept%5Fid=4&pf%5Fid=224


	* Kramer Vanguards for $179
	  http://www.musicyo.com/product.asp?dept%5Fid=1&pf%5Fid=014


	* MusicYo Gigbags for $7.99
	  http://www.musicyo.com/product.asp?dept%5Fid=4&pf%5Fid=100

YO PLANET!
----------
	* Check out our new section called 'Yo Planet'. In it you will find
instructions on the set-up and maintenance of your instrument as well as
product reviews and more!
	  http://www.musicyo.com/yoplanet.asp

	* You can even download 'Rock-Hard' - our exclusive Kramer ScreenMate -
for FREE! He walks... he talks... he gets down!
	  http://www.musicyo.com/yoplanet.asp

Thanks a lot and thanks for visiting www.MusicYo.com!

Doc Yo
MusicYo.com
'What Will I Play Today?'


_____________________________________________________________________
Further transmissions to you by the sender of this e-mail may be stopped
at no cost to you by visiting http://www.musicyo.com/mailinglist.asp. If
you wish to change your mailing list options, such as request future
mailings in HTML format, please visit
http://www.musicyo.com/mailinglist.asp.



From owner-ietf-outbound@ietf.org  Fri Jan 14 17:13:02 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23073
	for <ietf-web-archive@odin.ietf.org>; Fri, 14 Jan 2000 17:13:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23208;
	Fri, 14 Jan 2000 17:11:29 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA23028
	for ietf-outbound.10@ietf.org; Fri, 14 Jan 2000 17:10:02 -0500 (EST)
Received: from musicyo2.musicyo.com (host-208-53-49-34.bluestar.net [208.53.49.34] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22938
	for <ietf@ietf.org>; Fri, 14 Jan 2000 17:04:06 -0500 (EST)
From: DocYo@musicyo.com
Received: from mail pickup service by musicyo2.musicyo.com with Microsoft SMTPSVC;
	 Fri, 14 Jan 2000 14:47:58 -0600
To: <ietf@ietf.org>
Subject: Greetings for MusicYo.com!
Date: Fri, 14 Jan 2000 14:47:58 -0600
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <03e5d5847200e10MUSICYO2@musicyo2.musicyo.com>

Dear ietf@ietf.org,

Greetings from www.MusicYo.com! Your only source for brand-name, brand-new
gear at factory-direct prices!

In case you haven't visited us lately, here's what's new!

WIN A KRAMER GUITAR!
--------------------
	* Stop by and enter to WIN a Kramer Baretta FX-404S guitar!
	  http://www.musicyo.com/freestuf.asp?target=freesuf%2Easp

PRODUCT NEWS!
-------------
On the product front we've now got IN STOCK AND READY FOR IMMEDIATE
PURCHASE...

	* Slingerland 5-pc Jam Session Drum Kits for $229
	  http://www.musicyo.com/product.asp?dept%5Fid=2&pf%5Fid=017


	* MusicYo Personal Guitar Amplifiers for $17.99
	  http://www.musicyo.com/product.asp?dept%5Fid=4&pf%5Fid=223


	* Celestion G12T-75 Speakers for $49.99
	  http://www.musicyo.com/product.asp?dept%5Fid=4&pf%5Fid=224


	* Kramer Vanguards for $179
	  http://www.musicyo.com/product.asp?dept%5Fid=1&pf%5Fid=014


	* MusicYo Gigbags for $7.99
	  http://www.musicyo.com/product.asp?dept%5Fid=4&pf%5Fid=100

YO PLANET!
----------
	* Check out our new section called 'Yo Planet'. In it you will find
instructions on the set-up and maintenance of your instrument as well as
product reviews and more!
	  http://www.musicyo.com/yoplanet.asp

	* You can even download 'Rock-Hard' - our exclusive Kramer ScreenMate -
for FREE! He walks... he talks... he gets down!
	  http://www.musicyo.com/yoplanet.asp

Thanks a lot and thanks for visiting www.MusicYo.com!

Doc Yo
MusicYo.com
'What Will I Play Today?'


_____________________________________________________________________
Further transmissions to you by the sender of this e-mail may be stopped
at no cost to you by visiting http://www.musicyo.com/mailinglist.asp. If
you wish to change your mailing list options, such as request future
mailings in HTML format, please visit
http://www.musicyo.com/mailinglist.asp.



From owner-ietf-outbound  Sun Jan 16 08:54:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA08503
	for ietf-outbound.10@ietf.org; Sun, 16 Jan 2000 08:50:02 -0500 (EST)
Received: from mailhost1.dircon.co.uk (mailhost1.dircon.co.uk [194.112.32.65])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08423
	for <ietf@ietf.org>; Sun, 16 Jan 2000 08:42:05 -0500 (EST)
Received: from mailserver.spectrumsc.co.uk (spectsc1.dircon.co.uk [194.112.44.20])
	by mailhost1.dircon.co.uk (8.9.1/8.8.7) with ESMTP id NAA20654
	for <ietf@ietf.org>; Sun, 16 Jan 2000 13:42:00 GMT
Received: by host105.spectrum.u-net.com with Internet Mail Service (5.5.2650.10)
	id <CV3AQNF1>; Sun, 16 Jan 2000 13:35:40 -0000
Message-ID: <1B58104B255BD311BC700000E891322422F0DD@host105.spectrum.u-net.com>
From: Jon Watts <jon.watts@SPECTRUMSC.CO.UK>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: auth 36dbe6c3 subscribe ietf
Date: Sun, 16 Jan 2000 13:35:39 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain

auth 36dbe6c3 subscribe ietf



From owner-ietf-outbound@ietf.org  Sun Jan 16 08:56:55 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08608
	for <ietf-web-archive@odin.ietf.org>; Sun, 16 Jan 2000 08:56:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA13462;
	Sun, 16 Jan 2000 08:55:21 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA08503
	for ietf-outbound.10@ietf.org; Sun, 16 Jan 2000 08:50:02 -0500 (EST)
Received: from mailhost1.dircon.co.uk (mailhost1.dircon.co.uk [194.112.32.65])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08423
	for <ietf@ietf.org>; Sun, 16 Jan 2000 08:42:05 -0500 (EST)
Received: from mailserver.spectrumsc.co.uk (spectsc1.dircon.co.uk [194.112.44.20])
	by mailhost1.dircon.co.uk (8.9.1/8.8.7) with ESMTP id NAA20654
	for <ietf@ietf.org>; Sun, 16 Jan 2000 13:42:00 GMT
Received: by host105.spectrum.u-net.com with Internet Mail Service (5.5.2650.10)
	id <CV3AQNF1>; Sun, 16 Jan 2000 13:35:40 -0000
Message-ID: <1B58104B255BD311BC700000E891322422F0DD@host105.spectrum.u-net.com>
From: Jon Watts <jon.watts@SPECTRUMSC.CO.UK>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: auth 36dbe6c3 subscribe ietf
Date: Sun, 16 Jan 2000 13:35:39 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain

auth 36dbe6c3 subscribe ietf



From owner-ietf-outbound  Mon Jan 17 10:12:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02233
	for ietf-outbound.10@ietf.org; Mon, 17 Jan 2000 10:10:02 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02177;
	Mon, 17 Jan 2000 10:05:28 -0500 (EST)
Date: Mon, 17 Jan 2000 10:05:28 -0500 (EST)
Message-Id: <200001171505.KAA02177@ietf.org>
X-Authentication-Warning: ietf.org: majordom set sender to Majordomo-Owner@ietf.org using -f
To: mailto:ietf@ietf.org
From: Majordomo@ietf.org
Subject: Confirmation for subscribe ietf
Reply-To: Majordomo@ietf.org

--

Someone (possibly you) has requested that your email address be added
to or deleted from the mailing list "ietf@ietf.org".

If you really want this action to be taken, please send the following
commands (exactly as shown) back to "Majordomo@ietf.org":

	auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org

If you do not want this action to be taken, simply ignore this message
and the request will be disregarded.

If your mailer will not allow you to send the entire command as a single
line, you may split it using backslashes, like so:

        auth 36dbe6c3 subscribe ietf \
        mailto:ietf@ietf.org

If you have any questions about the policy of the list owner, please
contact "ietf-approval@ietf.org".

Thanks!

Majordomo@ietf.org



From owner-ietf-outbound@ietf.org  Mon Jan 17 10:16:57 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02425
	for <ietf-web-archive@odin.ietf.org>; Mon, 17 Jan 2000 10:16:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18748;
	Mon, 17 Jan 2000 10:15:25 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02233
	for ietf-outbound.10@ietf.org; Mon, 17 Jan 2000 10:10:02 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02177;
	Mon, 17 Jan 2000 10:05:28 -0500 (EST)
Date: Mon, 17 Jan 2000 10:05:28 -0500 (EST)
Message-Id: <200001171505.KAA02177@ietf.org>
X-Authentication-Warning: ietf.org: majordom set sender to Majordomo-Owner@ietf.org using -f
To: mailto:ietf@ietf.org
From: Majordomo@ietf.org
Subject: Confirmation for subscribe ietf
Reply-To: Majordomo@ietf.org

--

Someone (possibly you) has requested that your email address be added
to or deleted from the mailing list "ietf@ietf.org".

If you really want this action to be taken, please send the following
commands (exactly as shown) back to "Majordomo@ietf.org":

	auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org

If you do not want this action to be taken, simply ignore this message
and the request will be disregarded.

If your mailer will not allow you to send the entire command as a single
line, you may split it using backslashes, like so:

        auth 36dbe6c3 subscribe ietf \
        mailto:ietf@ietf.org

If you have any questions about the policy of the list owner, please
contact "ietf-approval@ietf.org".

Thanks!

Majordomo@ietf.org



From owner-ietf-outbound  Mon Jan 17 10:20:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02500
	for ietf-outbound.10@ietf.org; Mon, 17 Jan 2000 10:20:02 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02365;
	Mon, 17 Jan 2000 10:16:28 -0500 (EST)
Date: Mon, 17 Jan 2000 10:16:28 -0500 (EST)
Message-Id: <200001171516.KAA02365@ietf.org>
X-Authentication-Warning: ietf.org: majordom set sender to Majordomo-Owner@ietf.org using -f
To: mailto:ietf@ietf.org
From: Majordomo@ietf.org
Subject: Confirmation for subscribe ietf
Reply-To: Majordomo@ietf.org

--

Someone (possibly you) has requested that your email address be added
to or deleted from the mailing list "ietf@ietf.org".

If you really want this action to be taken, please send the following
commands (exactly as shown) back to "Majordomo@ietf.org":

	auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org

If you do not want this action to be taken, simply ignore this message
and the request will be disregarded.

If your mailer will not allow you to send the entire command as a single
line, you may split it using backslashes, like so:

        auth 36dbe6c3 subscribe ietf \
        mailto:ietf@ietf.org

If you have any questions about the policy of the list owner, please
contact "ietf-approval@ietf.org".

Thanks!

Majordomo@ietf.org



From owner-ietf-outbound@ietf.org  Mon Jan 17 10:21:21 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02563
	for <ietf-web-archive@odin.ietf.org>; Mon, 17 Jan 2000 10:21:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18860;
	Mon, 17 Jan 2000 10:19:52 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02500
	for ietf-outbound.10@ietf.org; Mon, 17 Jan 2000 10:20:02 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02365;
	Mon, 17 Jan 2000 10:16:28 -0500 (EST)
Date: Mon, 17 Jan 2000 10:16:28 -0500 (EST)
Message-Id: <200001171516.KAA02365@ietf.org>
X-Authentication-Warning: ietf.org: majordom set sender to Majordomo-Owner@ietf.org using -f
To: mailto:ietf@ietf.org
From: Majordomo@ietf.org
Subject: Confirmation for subscribe ietf
Reply-To: Majordomo@ietf.org

--

Someone (possibly you) has requested that your email address be added
to or deleted from the mailing list "ietf@ietf.org".

If you really want this action to be taken, please send the following
commands (exactly as shown) back to "Majordomo@ietf.org":

	auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org

If you do not want this action to be taken, simply ignore this message
and the request will be disregarded.

If your mailer will not allow you to send the entire command as a single
line, you may split it using backslashes, like so:

        auth 36dbe6c3 subscribe ietf \
        mailto:ietf@ietf.org

If you have any questions about the policy of the list owner, please
contact "ietf-approval@ietf.org".

Thanks!

Majordomo@ietf.org



From owner-ietf-outbound  Mon Jan 17 12:00:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA03927
	for ietf-outbound.10@ietf.org; Mon, 17 Jan 2000 12:00:02 -0500 (EST)
Received: from relay2.smtp.psi.ca (relay2.smtp.psi.ca [154.11.137.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03804
	for <ietf@ietf.org>; Mon, 17 Jan 2000 11:50:57 -0500 (EST)
Received: from [207.219.70.31] (helo=ghazint)
	by relay2.smtp.psi.ca with smtp (Exim 1.90 #1)
	for ietf@ietf.org
	id 12AFMb-0002Cz-00; Mon, 17 Jan 2000 11:50:46 -0500
From: "Ghazi Wadi [DUNDAS]" <ghaziw@dundas.com>
To: <ietf@ietf.org>
Subject: RE: Majordomo subscribe request message
Date: Mon, 17 Jan 2000 11:49:26 -0000
Message-ID: <000001bf60e0$e7fb7360$1f46dbcf@DUNDAS>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <88256865.005E97D7.00@Hughes.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yep!
I have been receiving the same message too all week!
I believe Steve Coya had addressed this message and promised some solution
for this hack <g> (I think).

BTW: I got two of them this morning too.

Ghazi H. Wadi
Product Manager
Ultimate TCP/IP team
 /****************************************
 ghaziw@dundas.com
 Dundas Software
 http://www.dundas.com
 "
     We found Ultimate TCP/IP to be a solid
     package that performs very well and
     provides excellent value. ... Every
     aspect of Ultimate TCP/IP, in fact,
     seems geared toward making life
     easier for developers."
     -PC Magazine December 15, 1998
     -Editors' Choice Award
*****************************************/

-----Original Message-----
From: Mark.Abinante@HSC.COM [mailto:Mark.Abinante@HSC.COM]
Sent: Thursday, January 13, 2000 5:12 PM
To: ietf@ietf.org
Subject: RE: Majordomo subscribe request message





>Folks,
>I have recieved this same message three times at 18:45,19:41 & 20:32 Hrs
GMT
>respectively. Are any other IETF'ers seeing this pattern?
>Is this a problem with majordomo or something more machivelian ?
>Jim

I received same messages.  It is either a bug or system-wide hack.  Nothing
against you personally...
-Mark




From owner-ietf-outbound@ietf.org  Mon Jan 17 12:02:11 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04071
	for <ietf-web-archive@odin.ietf.org>; Mon, 17 Jan 2000 12:02:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA21944;
	Mon, 17 Jan 2000 12:00:36 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA03927
	for ietf-outbound.10@ietf.org; Mon, 17 Jan 2000 12:00:02 -0500 (EST)
Received: from relay2.smtp.psi.ca (relay2.smtp.psi.ca [154.11.137.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03804
	for <ietf@ietf.org>; Mon, 17 Jan 2000 11:50:57 -0500 (EST)
Received: from [207.219.70.31] (helo=ghazint)
	by relay2.smtp.psi.ca with smtp (Exim 1.90 #1)
	for ietf@ietf.org
	id 12AFMb-0002Cz-00; Mon, 17 Jan 2000 11:50:46 -0500
From: "Ghazi Wadi [DUNDAS]" <ghaziw@dundas.com>
To: <ietf@ietf.org>
Subject: RE: Majordomo subscribe request message
Date: Mon, 17 Jan 2000 11:49:26 -0000
Message-ID: <000001bf60e0$e7fb7360$1f46dbcf@DUNDAS>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <88256865.005E97D7.00@Hughes.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yep!
I have been receiving the same message too all week!
I believe Steve Coya had addressed this message and promised some solution
for this hack <g> (I think).

BTW: I got two of them this morning too.

Ghazi H. Wadi
Product Manager
Ultimate TCP/IP team
 /****************************************
 ghaziw@dundas.com
 Dundas Software
 http://www.dundas.com
 "
     We found Ultimate TCP/IP to be a solid
     package that performs very well and
     provides excellent value. ... Every
     aspect of Ultimate TCP/IP, in fact,
     seems geared toward making life
     easier for developers."
     -PC Magazine December 15, 1998
     -Editors' Choice Award
*****************************************/

-----Original Message-----
From: Mark.Abinante@HSC.COM [mailto:Mark.Abinante@HSC.COM]
Sent: Thursday, January 13, 2000 5:12 PM
To: ietf@ietf.org
Subject: RE: Majordomo subscribe request message





>Folks,
>I have recieved this same message three times at 18:45,19:41 & 20:32 Hrs
GMT
>respectively. Are any other IETF'ers seeing this pattern?
>Is this a problem with majordomo or something more machivelian ?
>Jim

I received same messages.  It is either a bug or system-wide hack.  Nothing
against you personally...
-Mark




From owner-ietf-outbound  Mon Jan 17 12:20:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA04358
	for ietf-outbound.10@ietf.org; Mon, 17 Jan 2000 12:20:02 -0500 (EST)
Received: from p-voyageur.issy.cnet.fr (p-voyageur.issy.cnet.fr [139.100.0.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04247
	for <ietf@ietf.org>; Mon, 17 Jan 2000 12:15:01 -0500 (EST)
Received: by p-voyageur.issy.cnet.fr with Internet Mail Service (5.5.2448.0)
	id <C17GAVPM>; Mon, 17 Jan 2000 18:15:13 +0100
Message-ID: <98388C05D464D111B61800805F1504160123E485@p-ibis.issy.cnet.fr>
From: BARNOLE Valerie CNET/DAC/ISS <valerie.barnole@cnet.francetelecom.fr>
To: "'Ghazi Wadi [DUNDAS]'" <ghaziw@dundas.com>, ietf@ietf.org
Subject: RE: Majordomo subscribe request message
Date: Mon, 17 Jan 2000 18:15:12 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA04247
Content-Transfer-Encoding: 8bit

So did I !


end of message
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

Valérie Barnole
FT.BD/CNET/DAC/ARS
tel. : + 33 1 45 29 58 39
fax : + 33 1 46 29 31 42

valerie.barnole@cnet.francetelecom.fr



-----Message d'origine-----
De: Ghazi Wadi [DUNDAS] [mailto:ghaziw@dundas.com]
Date: lundi 17 janvier 2000 12:49
À: ietf@ietf.org
Objet: RE: Majordomo subscribe request message


Yep!
I have been receiving the same message too all week!
I believe Steve Coya had addressed this message and promised some solution
for this hack <g> (I think).

BTW: I got two of them this morning too.

Ghazi H. Wadi
Product Manager
Ultimate TCP/IP team
 /****************************************
 ghaziw@dundas.com
 Dundas Software
 http://www.dundas.com
 "
     We found Ultimate TCP/IP to be a solid
     package that performs very well and
     provides excellent value. ... Every
     aspect of Ultimate TCP/IP, in fact,
     seems geared toward making life
     easier for developers."
     -PC Magazine December 15, 1998
     -Editors' Choice Award
*****************************************/

-----Original Message-----
From: Mark.Abinante@HSC.COM [mailto:Mark.Abinante@HSC.COM]
Sent: Thursday, January 13, 2000 5:12 PM
To: ietf@ietf.org
Subject: RE: Majordomo subscribe request message





>Folks,
>I have recieved this same message three times at 18:45,19:41 & 20:32 Hrs
GMT
>respectively. Are any other IETF'ers seeing this pattern?
>Is this a problem with majordomo or something more machivelian ?
>Jim

I received same messages.  It is either a bug or system-wide hack.  Nothing
against you personally...
-Mark



From owner-ietf-outbound@ietf.org  Mon Jan 17 12:21:56 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04429
	for <ietf-web-archive@odin.ietf.org>; Mon, 17 Jan 2000 12:21:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA22697;
	Mon, 17 Jan 2000 12:20:19 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA04358
	for ietf-outbound.10@ietf.org; Mon, 17 Jan 2000 12:20:02 -0500 (EST)
Received: from p-voyageur.issy.cnet.fr (p-voyageur.issy.cnet.fr [139.100.0.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04247
	for <ietf@ietf.org>; Mon, 17 Jan 2000 12:15:01 -0500 (EST)
Received: by p-voyageur.issy.cnet.fr with Internet Mail Service (5.5.2448.0)
	id <C17GAVPM>; Mon, 17 Jan 2000 18:15:13 +0100
Message-ID: <98388C05D464D111B61800805F1504160123E485@p-ibis.issy.cnet.fr>
From: BARNOLE Valerie CNET/DAC/ISS <valerie.barnole@cnet.francetelecom.fr>
To: "'Ghazi Wadi [DUNDAS]'" <ghaziw@dundas.com>, ietf@ietf.org
Subject: RE: Majordomo subscribe request message
Date: Mon, 17 Jan 2000 18:15:12 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA04247
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

So did I !


end of message
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

Valérie Barnole
FT.BD/CNET/DAC/ARS
tel. : + 33 1 45 29 58 39
fax : + 33 1 46 29 31 42

valerie.barnole@cnet.francetelecom.fr



-----Message d'origine-----
De: Ghazi Wadi [DUNDAS] [mailto:ghaziw@dundas.com]
Date: lundi 17 janvier 2000 12:49
À: ietf@ietf.org
Objet: RE: Majordomo subscribe request message


Yep!
I have been receiving the same message too all week!
I believe Steve Coya had addressed this message and promised some solution
for this hack <g> (I think).

BTW: I got two of them this morning too.

Ghazi H. Wadi
Product Manager
Ultimate TCP/IP team
 /****************************************
 ghaziw@dundas.com
 Dundas Software
 http://www.dundas.com
 "
     We found Ultimate TCP/IP to be a solid
     package that performs very well and
     provides excellent value. ... Every
     aspect of Ultimate TCP/IP, in fact,
     seems geared toward making life
     easier for developers."
     -PC Magazine December 15, 1998
     -Editors' Choice Award
*****************************************/

-----Original Message-----
From: Mark.Abinante@HSC.COM [mailto:Mark.Abinante@HSC.COM]
Sent: Thursday, January 13, 2000 5:12 PM
To: ietf@ietf.org
Subject: RE: Majordomo subscribe request message





>Folks,
>I have recieved this same message three times at 18:45,19:41 & 20:32 Hrs
GMT
>respectively. Are any other IETF'ers seeing this pattern?
>Is this a problem with majordomo or something more machivelian ?
>Jim

I received same messages.  It is either a bug or system-wide hack.  Nothing
against you personally...
-Mark



From owner-ietf-outbound  Mon Jan 17 13:50:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA05563
	for ietf-outbound.10@ietf.org; Mon, 17 Jan 2000 13:50:02 -0500 (EST)
Received: from external.rsc.rockwell.com (firewall-user@external.rsc.rockwell.com [130.50.23.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05429
	for <ietf@ietf.org>; Mon, 17 Jan 2000 13:46:46 -0500 (EST)
From: vslin@rsc.rockwell.com
Received: by external.rsc.rockwell.com; id KAA06386; Mon, 17 Jan 2000 10:46:45 -0800 (PST)
Received: from dns.risc.rockwell.com(130.50.4.15) by external.rsc.rockwell.com via smap (V4.2)
	id xma006368; Mon, 17 Jan 00 10:46:44 -0800
Received: from rsctonotes01.rsc.rockwell.com (rsctonotes01.risc.rockwell.com [130.50.4.71]) by dns.risc.rockwell.com (8.9.0/8.6.9) with SMTP id KAA26813 for <ietf@ietf.org>; Mon, 17 Jan 2000 10:46:43 -0800 (PST)
Received: by rsctonotes01.rsc.rockwell.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 88256869.00671F9F ; Mon, 17 Jan 2000 10:46:23 -0800
X-Lotus-FromDomain: ROCKWELL
Sender: vslin@rsc.rockwell.com
To: ietf@ietf.org
Message-ID: <88256869.00671E0E.00@rsctonotes01.rsc.rockwell.com>
Date: Mon, 17 Jan 2000 10:45:59 -0800
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline

auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org




From owner-ietf-outbound@ietf.org  Mon Jan 17 13:51:58 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05653
	for <ietf-web-archive@odin.ietf.org>; Mon, 17 Jan 2000 13:51:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA25058;
	Mon, 17 Jan 2000 13:50:30 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA05563
	for ietf-outbound.10@ietf.org; Mon, 17 Jan 2000 13:50:02 -0500 (EST)
Received: from external.rsc.rockwell.com (firewall-user@external.rsc.rockwell.com [130.50.23.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05429
	for <ietf@ietf.org>; Mon, 17 Jan 2000 13:46:46 -0500 (EST)
From: vslin@rsc.rockwell.com
Received: by external.rsc.rockwell.com; id KAA06386; Mon, 17 Jan 2000 10:46:45 -0800 (PST)
Received: from dns.risc.rockwell.com(130.50.4.15) by external.rsc.rockwell.com via smap (V4.2)
	id xma006368; Mon, 17 Jan 00 10:46:44 -0800
Received: from rsctonotes01.rsc.rockwell.com (rsctonotes01.risc.rockwell.com [130.50.4.71]) by dns.risc.rockwell.com (8.9.0/8.6.9) with SMTP id KAA26813 for <ietf@ietf.org>; Mon, 17 Jan 2000 10:46:43 -0800 (PST)
Received: by rsctonotes01.rsc.rockwell.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 88256869.00671F9F ; Mon, 17 Jan 2000 10:46:23 -0800
X-Lotus-FromDomain: ROCKWELL
Sender: vslin@rsc.rockwell.com
To: ietf@ietf.org
Message-ID: <88256869.00671E0E.00@rsctonotes01.rsc.rockwell.com>
Date: Mon, 17 Jan 2000 10:45:59 -0800
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline

auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org




From owner-ietf-outbound  Mon Jan 17 14:20:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA06091
	for ietf-outbound.10@ietf.org; Mon, 17 Jan 2000 14:20:02 -0500 (EST)
Received: from venus.symon.com (mail.symon.com [4.22.141.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05954
	for <ietf@ietf.org>; Mon, 17 Jan 2000 14:10:46 -0500 (EST)
Received: from zaphod ([4.22.141.43]) by venus.symon.com
          (Post.Office MTA v3.1.2 release (PO205-101c)
          ID# 569-43960U100L2S100) with SMTP id AAA246 for <ietf@ietf.org>;
          Mon, 17 Jan 2000 13:10:29 -0600
Return-Receipt-To: "Raymond Rogers" <rerogers@symon.com>
Reply-To: <rerogers@symon.com>
From: rerogers@symon.com (Raymond Rogers)
To: <ietf@ietf.org>
Subject: auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org
Date: Mon, 17 Jan 2000 13:05:16 -0700
Message-ID: <005601bf6126$2c735270$2b8d1604@symon.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Disposition-Notification-To: "Raymond Rogers" <rerogers@symon.com>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org



From owner-ietf-outbound@ietf.org  Mon Jan 17 14:21:48 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06277
	for <ietf-web-archive@odin.ietf.org>; Mon, 17 Jan 2000 14:21:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA25873;
	Mon, 17 Jan 2000 14:20:11 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA06091
	for ietf-outbound.10@ietf.org; Mon, 17 Jan 2000 14:20:02 -0500 (EST)
Received: from venus.symon.com (mail.symon.com [4.22.141.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05954
	for <ietf@ietf.org>; Mon, 17 Jan 2000 14:10:46 -0500 (EST)
Received: from zaphod ([4.22.141.43]) by venus.symon.com
          (Post.Office MTA v3.1.2 release (PO205-101c)
          ID# 569-43960U100L2S100) with SMTP id AAA246 for <ietf@ietf.org>;
          Mon, 17 Jan 2000 13:10:29 -0600
Return-Receipt-To: "Raymond Rogers" <rerogers@symon.com>
Reply-To: <rerogers@symon.com>
From: rerogers@symon.com (Raymond Rogers)
To: <ietf@ietf.org>
Subject: auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org
Date: Mon, 17 Jan 2000 13:05:16 -0700
Message-ID: <005601bf6126$2c735270$2b8d1604@symon.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Disposition-Notification-To: "Raymond Rogers" <rerogers@symon.com>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org



From owner-ietf-outbound  Tue Jan 18 08:41:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA29189
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 08:40:02 -0500 (EST)
Received: from d12lmsgate-2.de.ibm.com (d12lmsgate-2.de.ibm.com [195.212.91.200])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29153
	for <ietf@ietf.org>; Tue, 18 Jan 2000 08:39:57 -0500 (EST)
From: shaih@il.ibm.com
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-2.de.ibm.com (1.0.0) with ESMTP id OAA117834;
	Tue, 18 Jan 2000 14:39:25 +0100
Received: from d12mta02.de.ibm.com (d12mta01_cs0 [9.165.222.237])
	by d12relay02.de.ibm.com (8.8.8m2/NCO v2.06) with SMTP id OAA14912;
	Tue, 18 Jan 2000 14:39:25 +0100
Received: by d12mta02.de.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id C125686A.004B0304 ; Tue, 18 Jan 2000 14:39:19 +0100
X-Lotus-FromDomain: IBMIL@IBMDE
To: vslin@rsc.rockwell.com
cc: ietf@ietf.org
Message-ID: <C125686A.004B014F.00@d12mta02.de.ibm.com>
Date: Tue, 18 Jan 2000 10:03:06 +0200
Subject: Re:
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline



Please respond to vslin@rsc.rockwell.com

To:   ietf@ietf.org
cc:    (bcc: Shai Haimovich/Israel/Contr/IBM)
Subject:




auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org







From owner-ietf-outbound@ietf.org  Tue Jan 18 08:43:41 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29296
	for <ietf-web-archive@odin.ietf.org>; Tue, 18 Jan 2000 08:43:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA29500;
	Tue, 18 Jan 2000 08:42:09 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA29189
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 08:40:02 -0500 (EST)
Received: from d12lmsgate-2.de.ibm.com (d12lmsgate-2.de.ibm.com [195.212.91.200])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29153
	for <ietf@ietf.org>; Tue, 18 Jan 2000 08:39:57 -0500 (EST)
From: shaih@il.ibm.com
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-2.de.ibm.com (1.0.0) with ESMTP id OAA117834;
	Tue, 18 Jan 2000 14:39:25 +0100
Received: from d12mta02.de.ibm.com (d12mta01_cs0 [9.165.222.237])
	by d12relay02.de.ibm.com (8.8.8m2/NCO v2.06) with SMTP id OAA14912;
	Tue, 18 Jan 2000 14:39:25 +0100
Received: by d12mta02.de.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id C125686A.004B0304 ; Tue, 18 Jan 2000 14:39:19 +0100
X-Lotus-FromDomain: IBMIL@IBMDE
To: vslin@rsc.rockwell.com
cc: ietf@ietf.org
Message-ID: <C125686A.004B014F.00@d12mta02.de.ibm.com>
Date: Tue, 18 Jan 2000 10:03:06 +0200
Subject: Re:
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline



Please respond to vslin@rsc.rockwell.com

To:   ietf@ietf.org
cc:    (bcc: Shai Haimovich/Israel/Contr/IBM)
Subject:




auth 36dbe6c3 subscribe ietf mailto:ietf@ietf.org







From owner-ietf-outbound  Tue Jan 18 09:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA29701
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 09:10:02 -0500 (EST)
Received: from prosyst.com (server.prosyst.com [195.14.248.34] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29655
	for <ietf@ietf.org>; Tue, 18 Jan 2000 09:07:01 -0500 (EST)
Message-ID: <3884734D.B1348D23@prosyst.com>
Date: Tue, 18 Jan 2000 16:06:05 +0200
From: plamen kosseff <p_kosseff@prosyst.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: bg,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: auth 36dbe6c3 subscribe ietf
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

auth 36dbe6c3 subscribe ietf



From owner-ietf-outbound@ietf.org  Tue Jan 18 09:11:47 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29788
	for <ietf-web-archive@odin.ietf.org>; Tue, 18 Jan 2000 09:11:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00077;
	Tue, 18 Jan 2000 09:10:12 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA29701
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 09:10:02 -0500 (EST)
Received: from prosyst.com (server.prosyst.com [195.14.248.34] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29655
	for <ietf@ietf.org>; Tue, 18 Jan 2000 09:07:01 -0500 (EST)
Message-ID: <3884734D.B1348D23@prosyst.com>
Date: Tue, 18 Jan 2000 16:06:05 +0200
From: plamen kosseff <p_kosseff@prosyst.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: bg,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: auth 36dbe6c3 subscribe ietf
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

auth 36dbe6c3 subscribe ietf



From owner-ietf-outbound  Tue Jan 18 09:30:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA29916
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 09:30:02 -0500 (EST)
Received: from norted.core.afcc.com (norted.afcc.com [204.167.220.150])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29846
	for <ietf@ietf.org>; Tue, 18 Jan 2000 09:24:34 -0500 (EST)
Received: from mcfeely.core.afcc.com by norted.core.afcc.com
          via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 18 Jan 2000 14:24:35 UT
Received: by afcc.com (SMI-8.6/SMI-SVR4)
	id IAA07462; Tue, 18 Jan 2000 08:24:34 -0600
Received: from norteddmz(192.168.7.150), claiming to be "norteddmz.core.afcc.com"
 via SMTP by mcfeely, id smtpdAAAMfC3g_; Tue Jan 18 08:24:28 2000
Received: from [10.96.1.88] by norteddmz.core.afcc.com
          via smtpd (for mcfeely.core.afcc.com [192.168.7.1]) with SMTP; 18 Jan 2000 14:24:28 UT
X-Server-Uuid: f7186388-6a25-11d3-b7c9-0008c7b961c2
Message-ID: <1914631461D6D211991A00902736A469C227E1@Z1111223.core.afcc.com>
From: "Tobin, Brian" <Brian_Tobin@AFCC.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Date: Tue, 18 Jan 2000 08:24:19 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
X-WSS-ID: 149AA8118855779-01-02
Content-Type: text/plain; 
 charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

auth 36dbe6c3 subscribe ietf



From owner-ietf-outbound@ietf.org  Tue Jan 18 09:31:55 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00041
	for <ietf-web-archive@odin.ietf.org>; Tue, 18 Jan 2000 09:31:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00656;
	Tue, 18 Jan 2000 09:30:25 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA29916
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 09:30:02 -0500 (EST)
Received: from norted.core.afcc.com (norted.afcc.com [204.167.220.150])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29846
	for <ietf@ietf.org>; Tue, 18 Jan 2000 09:24:34 -0500 (EST)
Received: from mcfeely.core.afcc.com by norted.core.afcc.com
          via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 18 Jan 2000 14:24:35 UT
Received: by afcc.com (SMI-8.6/SMI-SVR4)
	id IAA07462; Tue, 18 Jan 2000 08:24:34 -0600
Received: from norteddmz(192.168.7.150), claiming to be "norteddmz.core.afcc.com"
 via SMTP by mcfeely, id smtpdAAAMfC3g_; Tue Jan 18 08:24:28 2000
Received: from [10.96.1.88] by norteddmz.core.afcc.com
          via smtpd (for mcfeely.core.afcc.com [192.168.7.1]) with SMTP; 18 Jan 2000 14:24:28 UT
X-Server-Uuid: f7186388-6a25-11d3-b7c9-0008c7b961c2
Message-ID: <1914631461D6D211991A00902736A469C227E1@Z1111223.core.afcc.com>
From: "Tobin, Brian" <Brian_Tobin@AFCC.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Date: Tue, 18 Jan 2000 08:24:19 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
X-WSS-ID: 149AA8118855779-01-02
Content-Type: text/plain; 
 charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

auth 36dbe6c3 subscribe ietf



From owner-ietf-outbound  Tue Jan 18 10:12:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA00441
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 10:10:02 -0500 (EST)
Received: from apollo.nbase.co.il (apollo.nbase.co.il [194.90.137.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00376
	for <ietf@ietf.org>; Tue, 18 Jan 2000 10:06:41 -0500 (EST)
Received: from nbase.co.il ([194.90.137.185]) by apollo.nbase.co.il
          (Post.Office MTA v3.1.2 release (PO205-101c)
          ID# 0-44418U200L2S100) with ESMTP id AAA168 for <ietf@ietf.org>;
          Tue, 18 Jan 2000 17:02:27 +0200
Message-ID: <38848240.386ED9C2@nbase.co.il>
Date: Tue, 18 Jan 2000 17:09:52 +0200
From: marcello@nbase.co.il (Marcello Bracha)
Organization: NBASE Communications LTD
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: IEEE 802.1q VLAN Tagging
Content-Type: multipart/alternative;
 boundary="------------FC63E2C616D9A9B0CA2FE348"


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

Sir,

I would like to know when the above standard has been finalized
Same for the Routing Support of Tagged Vlans

Thanking you in advance

Marcello Braha
Application Engineer
NBASE-XYPLEX
Yokneam Israel
e-mail : marcello@nbase-xyplex.com

--------------FC63E2C616D9A9B0CA2FE348
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<b>Sir,</b><b></b>
<p><b>I would like to know when the above standard has been finalized</b>
<br><b>Same for the Routing Support of Tagged Vlans</b><b></b>
<p><b>Thanking you in advance</b><b></b>
<p><b>Marcello Braha</b>
<br><b>Application Engineer</b>
<br><b>NBASE-XYPLEX</b>
<br><b>Yokneam Israel</b>
<br><b>e-mail : marcello@nbase-xyplex.com</b></html>

--------------FC63E2C616D9A9B0CA2FE348--



From owner-ietf-outbound@ietf.org  Tue Jan 18 10:14:43 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00548
	for <ietf-web-archive@odin.ietf.org>; Tue, 18 Jan 2000 10:14:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA02252;
	Tue, 18 Jan 2000 10:13:09 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA00441
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 10:10:02 -0500 (EST)
Received: from apollo.nbase.co.il (apollo.nbase.co.il [194.90.137.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00376
	for <ietf@ietf.org>; Tue, 18 Jan 2000 10:06:41 -0500 (EST)
Received: from nbase.co.il ([194.90.137.185]) by apollo.nbase.co.il
          (Post.Office MTA v3.1.2 release (PO205-101c)
          ID# 0-44418U200L2S100) with ESMTP id AAA168 for <ietf@ietf.org>;
          Tue, 18 Jan 2000 17:02:27 +0200
Message-ID: <38848240.386ED9C2@nbase.co.il>
Date: Tue, 18 Jan 2000 17:09:52 +0200
From: marcello@nbase.co.il (Marcello Bracha)
Organization: NBASE Communications LTD
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: IEEE 802.1q VLAN Tagging
Content-Type: multipart/alternative;
 boundary="------------FC63E2C616D9A9B0CA2FE348"


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

Sir,

I would like to know when the above standard has been finalized
Same for the Routing Support of Tagged Vlans

Thanking you in advance

Marcello Braha
Application Engineer
NBASE-XYPLEX
Yokneam Israel
e-mail : marcello@nbase-xyplex.com

--------------FC63E2C616D9A9B0CA2FE348
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<b>Sir,</b><b></b>
<p><b>I would like to know when the above standard has been finalized</b>
<br><b>Same for the Routing Support of Tagged Vlans</b><b></b>
<p><b>Thanking you in advance</b><b></b>
<p><b>Marcello Braha</b>
<br><b>Application Engineer</b>
<br><b>NBASE-XYPLEX</b>
<br><b>Yokneam Israel</b>
<br><b>e-mail : marcello@nbase-xyplex.com</b></html>

--------------FC63E2C616D9A9B0CA2FE348--



From owner-ietf-outbound  Tue Jan 18 10:51:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA01176
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 10:50:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01059
	for <ietf@ietf.org>; Tue, 18 Jan 2000 10:41:48 -0500 (EST)
Received: from black-ice.cc.vt.edu (LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta11/8.10.0.Beta11) with ESMTP id e0IFfXp13502
	for <ietf@ietf.org>; Tue, 18 Jan 2000 10:41:34 -0500
Message-Id: <200001181541.e0IFfXp13502@black-ice.cc.vt.edu>
To: ietf@ietf.org
Subject: Is anybody else suspicious about this?
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face-Viewer: See ftp://cs.indiana.edu/pub/faces/index.html to decode picture
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
Date: Tue, 18 Jan 2000 10:41:33 -0500

Last 3 e-mails to the list, from:

From:    plamen kosseff <p_kosseff@prosyst.com>
From:    "Tobin, Brian" <Brian_Tobin@AFCC.com>
From:    marcello@nbase.co.il (Marcello Bracha)

All had "auth 36dbe6c3 subscribe ietf" in either the body or Subject:.

Is this rampant cluelessness, or is that 36dbe6c3 cookie being
regenerated by a broken HTML page or something?

In the meantime, can we fix the Majordomo filter so 'auth' gets trapped
as well as 'subscribe' so we can return to our usual silence/flaming cycle? ;)

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound@ietf.org  Tue Jan 18 10:53:21 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01339
	for <ietf-web-archive@odin.ietf.org>; Tue, 18 Jan 2000 10:53:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA03271;
	Tue, 18 Jan 2000 10:51:48 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA01176
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 10:50:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01059
	for <ietf@ietf.org>; Tue, 18 Jan 2000 10:41:48 -0500 (EST)
Received: from black-ice.cc.vt.edu (LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta11/8.10.0.Beta11) with ESMTP id e0IFfXp13502
	for <ietf@ietf.org>; Tue, 18 Jan 2000 10:41:34 -0500
Message-Id: <200001181541.e0IFfXp13502@black-ice.cc.vt.edu>
To: ietf@ietf.org
Subject: Is anybody else suspicious about this?
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face-Viewer: See ftp://cs.indiana.edu/pub/faces/index.html to decode picture
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
Date: Tue, 18 Jan 2000 10:41:33 -0500

Last 3 e-mails to the list, from:

From:    plamen kosseff <p_kosseff@prosyst.com>
From:    "Tobin, Brian" <Brian_Tobin@AFCC.com>
From:    marcello@nbase.co.il (Marcello Bracha)

All had "auth 36dbe6c3 subscribe ietf" in either the body or Subject:.

Is this rampant cluelessness, or is that 36dbe6c3 cookie being
regenerated by a broken HTML page or something?

In the meantime, can we fix the Majordomo filter so 'auth' gets trapped
as well as 'subscribe' so we can return to our usual silence/flaming cycle? ;)

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Tue Jan 18 12:00:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA02638
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 12:00:02 -0500 (EST)
Received: from relay.cwplc.com ([194.6.6.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02464
	for <ietf@ietf.org>; Tue, 18 Jan 2000 11:52:29 -0500 (EST)
Received: from gb-cwc-wtn-msw4 ([148.185.175.64])
	by relay.cwplc.com (Pro-8.9.3/8.9.3) with ESMTP id QAA09579
	for <ietf@ietf.org>; Tue, 18 Jan 2000 16:52:23 GMT
Received: from gb-cwc-wtn-i02.isops.mercury.co.uk (unverified) by gb-cwc-wtn-msw4
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001687132@gb-cwc-wtn-msw4> for <ietf@ietf.org>;
 Tue, 18 Jan 2000 16:48:24 +0000
Received: by gb-cwc-wtn-io2.isops.cwcom.co.uk with Internet Mail Service (5.5.2650.21)
	id <CLMHZK4F>; Tue, 18 Jan 2000 16:38:43 -0000
Message-Id: <A989508D4E92D111AA8F0000F80687AF080AD2AF@gbcwcbrtm001.isops.mercury.co.uk>
From: "Monaghan, Alan" <Alan.Monaghan@CWCOM.CO.UK>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Recall: 
Date: Tue, 18 Jan 2000 16:49:10 -0000
Expiry-Date: Thu, 20 Jan 2000 16:45:01 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain

Monaghan, Alan would like to recall the message, "".



From owner-ietf-outbound@ietf.org  Tue Jan 18 12:04:06 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02850
	for <ietf-web-archive@odin.ietf.org>; Tue, 18 Jan 2000 12:04:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA05578;
	Tue, 18 Jan 2000 12:02:28 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA02638
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 12:00:02 -0500 (EST)
Received: from relay.cwplc.com ([194.6.6.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02464
	for <ietf@ietf.org>; Tue, 18 Jan 2000 11:52:29 -0500 (EST)
Received: from gb-cwc-wtn-msw4 ([148.185.175.64])
	by relay.cwplc.com (Pro-8.9.3/8.9.3) with ESMTP id QAA09579
	for <ietf@ietf.org>; Tue, 18 Jan 2000 16:52:23 GMT
Received: from gb-cwc-wtn-i02.isops.mercury.co.uk (unverified) by gb-cwc-wtn-msw4
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001687132@gb-cwc-wtn-msw4> for <ietf@ietf.org>;
 Tue, 18 Jan 2000 16:48:24 +0000
Received: by gb-cwc-wtn-io2.isops.cwcom.co.uk with Internet Mail Service (5.5.2650.21)
	id <CLMHZK4F>; Tue, 18 Jan 2000 16:38:43 -0000
Message-Id: <A989508D4E92D111AA8F0000F80687AF080AD2AF@gbcwcbrtm001.isops.mercury.co.uk>
From: "Monaghan, Alan" <Alan.Monaghan@CWCOM.CO.UK>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Recall: 
Date: Tue, 18 Jan 2000 16:49:10 -0000
Expiry-Date: Thu, 20 Jan 2000 16:45:01 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain

Monaghan, Alan would like to recall the message, "".



From owner-ietf-outbound  Tue Jan 18 12:10:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA02956
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 12:10:03 -0500 (EST)
Received: from relay1.bt.net (relay1.bt.net [194.72.6.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02495
	for <ietf@ietf.org>; Tue, 18 Jan 2000 11:54:55 -0500 (EST)
Received: from [194.74.75.47] (helo=wstaalnt544731)
	by relay1.bt.net with smtp (Exim 2.11 #1)
	id 12AbuB-0006qF-00; Tue, 18 Jan 2000 16:54:55 +0000
From: "Jim Dunn" <jim.dunn@bt.net>
To: <Valdis.Kletnieks@vt.edu>, <ietf@ietf.org>
Subject: RE: Is anybody else suspicious about this?
Date: Tue, 18 Jan 2000 16:56:35 -0000
Message-ID: <NDBBIPFKPKJBOCDKBOKOKEIOCDAA.jim.dunn@bt.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)
In-Reply-To: <200001181541.e0IFfXp13502@black-ice.cc.vt.edu>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I have noticed that the Auth code is the same everytime I have been mailed
by Majordomo or someone has replied to the mail.( About 25 instances so
far )

Steve Coya has sent a message asking people not to respond to these
messages.
See below for original message from Steve.

Regards

Jim
-----Original Message-----
From: Steve Coya [mailto:scoya@ietf.org]
Sent: 12 January 2000 20:08
To: ietf@ietf.org
Subject: Majordomo subscribe request message



Folks,

Please do NOT respond to the message from majordomo asking to confirm
adding ietf@ietf.org to ietf@ietf.org

We're not sure where this/these messages originated, but are looking into
it right now.

Thanks and sorry for the inconvenience.



Steve

-----Original Message-----
From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
Sent: 18 January 2000 15:42
To: ietf@ietf.org
Subject: Is anybody else suspicious about this?


Last 3 e-mails to the list, from:

From:    plamen kosseff <p_kosseff@prosyst.com>
From:    "Tobin, Brian" <Brian_Tobin@AFCC.com>
From:    marcello@nbase.co.il (Marcello Bracha)

All had "auth 36dbe6c3 subscribe ietf" in either the body or Subject:.

Is this rampant cluelessness, or is that 36dbe6c3 cookie being
regenerated by a broken HTML page or something?

In the meantime, can we fix the Majordomo filter so 'auth' gets trapped
as well as 'subscribe' so we can return to our usual silence/flaming cycle?
;)

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound@ietf.org  Tue Jan 18 12:11:56 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03026
	for <ietf-web-archive@odin.ietf.org>; Tue, 18 Jan 2000 12:11:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA05777;
	Tue, 18 Jan 2000 12:10:21 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA02956
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 12:10:03 -0500 (EST)
Received: from relay1.bt.net (relay1.bt.net [194.72.6.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02495
	for <ietf@ietf.org>; Tue, 18 Jan 2000 11:54:55 -0500 (EST)
Received: from [194.74.75.47] (helo=wstaalnt544731)
	by relay1.bt.net with smtp (Exim 2.11 #1)
	id 12AbuB-0006qF-00; Tue, 18 Jan 2000 16:54:55 +0000
From: "Jim Dunn" <jim.dunn@bt.net>
To: <Valdis.Kletnieks@vt.edu>, <ietf@ietf.org>
Subject: RE: Is anybody else suspicious about this?
Date: Tue, 18 Jan 2000 16:56:35 -0000
Message-ID: <NDBBIPFKPKJBOCDKBOKOKEIOCDAA.jim.dunn@bt.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)
In-Reply-To: <200001181541.e0IFfXp13502@black-ice.cc.vt.edu>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I have noticed that the Auth code is the same everytime I have been mailed
by Majordomo or someone has replied to the mail.( About 25 instances so
far )

Steve Coya has sent a message asking people not to respond to these
messages.
See below for original message from Steve.

Regards

Jim
-----Original Message-----
From: Steve Coya [mailto:scoya@ietf.org]
Sent: 12 January 2000 20:08
To: ietf@ietf.org
Subject: Majordomo subscribe request message



Folks,

Please do NOT respond to the message from majordomo asking to confirm
adding ietf@ietf.org to ietf@ietf.org

We're not sure where this/these messages originated, but are looking into
it right now.

Thanks and sorry for the inconvenience.



Steve

-----Original Message-----
From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
Sent: 18 January 2000 15:42
To: ietf@ietf.org
Subject: Is anybody else suspicious about this?


Last 3 e-mails to the list, from:

From:    plamen kosseff <p_kosseff@prosyst.com>
From:    "Tobin, Brian" <Brian_Tobin@AFCC.com>
From:    marcello@nbase.co.il (Marcello Bracha)

All had "auth 36dbe6c3 subscribe ietf" in either the body or Subject:.

Is this rampant cluelessness, or is that 36dbe6c3 cookie being
regenerated by a broken HTML page or something?

In the meantime, can we fix the Majordomo filter so 'auth' gets trapped
as well as 'subscribe' so we can return to our usual silence/flaming cycle?
;)

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Tue Jan 18 12:40:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA03501
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 12:40:02 -0500 (EST)
Received: from www.7ways.org (ns7w.7ways.net [195.154.101.73])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03461
	for <ietf@ietf.org>; Tue, 18 Jan 2000 12:38:41 -0500 (EST)
Received: from FLC ([195.154.222.1])
	by www.7ways.org (8.9.3/8.9.3) with SMTP id SAA21231;
	Tue, 18 Jan 2000 18:40:35 +0100
Message-ID: <029e01bf61db$2d4211e0$0a01a8c0@FLC>
From: "7ways" <collignon@7ways.net>
To: "Jim Dunn" <jim.dunn@BT.NET>, <Valdis.Kletnieks@vt.edu>, <ietf@ietf.org>
Subject: Re: Is anybody else suspicious about this?
Date: Tue, 18 Jan 2000 18:40:57 +0100
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 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I believe that is my auth, I dont understand what is happen.

Francois

-----Original Message-----
From: Jim Dunn <jim.dunn@BT.NET>
To: Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu>; ietf@ietf.org
<ietf@ietf.org>
Date: Tuesday, January 18, 2000 6:36 PM
Subject: RE: Is anybody else suspicious about this?


>I have noticed that the Auth code is the same everytime I have been mailed
>by Majordomo or someone has replied to the mail.( About 25 instances so
>far )
>
>Steve Coya has sent a message asking people not to respond to these
>messages.
>See below for original message from Steve.
>
>Regards
>
>Jim
>-----Original Message-----
>From: Steve Coya [mailto:scoya@ietf.org]
>Sent: 12 January 2000 20:08
>To: ietf@ietf.org
>Subject: Majordomo subscribe request message
>
>
>
>Folks,
>
>Please do NOT respond to the message from majordomo asking to confirm
>adding ietf@ietf.org to ietf@ietf.org
>
>We're not sure where this/these messages originated, but are looking into
>it right now.
>
>Thanks and sorry for the inconvenience.
>
>
>
>Steve
>
>-----Original Message-----
>From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
>Sent: 18 January 2000 15:42
>To: ietf@ietf.org
>Subject: Is anybody else suspicious about this?
>
>
>Last 3 e-mails to the list, from:
>
>From:    plamen kosseff <p_kosseff@prosyst.com>
>From:    "Tobin, Brian" <Brian_Tobin@AFCC.com>
>From:    marcello@nbase.co.il (Marcello Bracha)
>
>All had "auth 36dbe6c3 subscribe ietf" in either the body or Subject:.
>
>Is this rampant cluelessness, or is that 36dbe6c3 cookie being
>regenerated by a broken HTML page or something?
>
>In the meantime, can we fix the Majordomo filter so 'auth' gets trapped
>as well as 'subscribe' so we can return to our usual silence/flaming cycle?
>;)
>
> Valdis Kletnieks
> Operating Systems Analyst
> Virginia Tech



From owner-ietf-outbound@ietf.org  Tue Jan 18 12:42:00 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03555
	for <ietf-web-archive@odin.ietf.org>; Tue, 18 Jan 2000 12:42:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA06467;
	Tue, 18 Jan 2000 12:40:26 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA03501
	for ietf-outbound.10@ietf.org; Tue, 18 Jan 2000 12:40:02 -0500 (EST)
Received: from www.7ways.org (ns7w.7ways.net [195.154.101.73])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03461
	for <ietf@ietf.org>; Tue, 18 Jan 2000 12:38:41 -0500 (EST)
Received: from FLC ([195.154.222.1])
	by www.7ways.org (8.9.3/8.9.3) with SMTP id SAA21231;
	Tue, 18 Jan 2000 18:40:35 +0100
Message-ID: <029e01bf61db$2d4211e0$0a01a8c0@FLC>
From: "7ways" <collignon@7ways.net>
To: "Jim Dunn" <jim.dunn@BT.NET>, <Valdis.Kletnieks@vt.edu>, <ietf@ietf.org>
Subject: Re: Is anybody else suspicious about this?
Date: Tue, 18 Jan 2000 18:40:57 +0100
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 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I believe that is my auth, I dont understand what is happen.

Francois

-----Original Message-----
From: Jim Dunn <jim.dunn@BT.NET>
To: Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu>; ietf@ietf.org
<ietf@ietf.org>
Date: Tuesday, January 18, 2000 6:36 PM
Subject: RE: Is anybody else suspicious about this?


>I have noticed that the Auth code is the same everytime I have been mailed
>by Majordomo or someone has replied to the mail.( About 25 instances so
>far )
>
>Steve Coya has sent a message asking people not to respond to these
>messages.
>See below for original message from Steve.
>
>Regards
>
>Jim
>-----Original Message-----
>From: Steve Coya [mailto:scoya@ietf.org]
>Sent: 12 January 2000 20:08
>To: ietf@ietf.org
>Subject: Majordomo subscribe request message
>
>
>
>Folks,
>
>Please do NOT respond to the message from majordomo asking to confirm
>adding ietf@ietf.org to ietf@ietf.org
>
>We're not sure where this/these messages originated, but are looking into
>it right now.
>
>Thanks and sorry for the inconvenience.
>
>
>
>Steve
>
>-----Original Message-----
>From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
>Sent: 18 January 2000 15:42
>To: ietf@ietf.org
>Subject: Is anybody else suspicious about this?
>
>
>Last 3 e-mails to the list, from:
>
>From:    plamen kosseff <p_kosseff@prosyst.com>
>From:    "Tobin, Brian" <Brian_Tobin@AFCC.com>
>From:    marcello@nbase.co.il (Marcello Bracha)
>
>All had "auth 36dbe6c3 subscribe ietf" in either the body or Subject:.
>
>Is this rampant cluelessness, or is that 36dbe6c3 cookie being
>regenerated by a broken HTML page or something?
>
>In the meantime, can we fix the Majordomo filter so 'auth' gets trapped
>as well as 'subscribe' so we can return to our usual silence/flaming cycle?
>;)
>
> Valdis Kletnieks
> Operating Systems Analyst
> Virginia Tech



From owner-ietf-outbound  Wed Jan 19 05:20:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA25309
	for ietf-outbound.10@ietf.org; Wed, 19 Jan 2000 05:20:02 -0500 (EST)
Received: from prosyst.com (server.prosyst.com [195.14.248.34] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA25287
	for <ietf@ietf.org>; Wed, 19 Jan 2000 05:18:37 -0500 (EST)
Message-ID: <38858F44.554648D7@prosyst.com>
Date: Wed, 19 Jan 2000 12:17:40 +0200
From: plamen kosseff <p_kosseff@prosyst.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: bg,en
MIME-Version: 1.0
To: 7ways <collignon@7ways.net>
CC: Jim Dunn <jim.dunn@BT.NET>, Valdis.Kletnieks@vt.edu, ietf@ietf.org
Subject: Re: Is anybody else suspicious about this?
References: <029e01bf61db$2d4211e0$0a01a8c0@FLC>
Content-Type: multipart/alternative;
 boundary="------------75184BEC2F1C68FC5D5B3CD2"


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





interesting i havent sended
      "auth 36dbe6c3 subscribe ietf"
first time i look at my mail it today
realy interesting


7ways wrote:

> I believe that is my auth, I dont understand what is happen.
>
> Francois
>
> -----Original Message-----
> From: Jim Dunn <jim.dunn@BT.NET>
> To: Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu>; ietf@ietf.org
> <ietf@ietf.org>
> Date: Tuesday, January 18, 2000 6:36 PM
> Subject: RE: Is anybody else suspicious about this?
>
> >I have noticed that the Auth code is the same everytime I have been mailed
> >by Majordomo or someone has replied to the mail.( About 25 instances so
> >far )
> >
> >Steve Coya has sent a message asking people not to respond to these
> >messages.
> >See below for original message from Steve.
> >
> >Regards
> >
> >Jim
> >-----Original Message-----
> >From: Steve Coya [mailto:scoya@ietf.org]
> >Sent: 12 January 2000 20:08
> >To: ietf@ietf.org
> >Subject: Majordomo subscribe request message
> >
> >
> >
> >Folks,
> >
> >Please do NOT respond to the message from majordomo asking to confirm
> >adding ietf@ietf.org to ietf@ietf.org
> >
> >We're not sure where this/these messages originated, but are looking into
> >it right now.
> >
> >Thanks and sorry for the inconvenience.
> >
> >
> >
> >Steve
> >
> >-----Original Message-----
> >From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
> >Sent: 18 January 2000 15:42
> >To: ietf@ietf.org
> >Subject: Is anybody else suspicious about this?
> >
> >
> >Last 3 e-mails to the list, from:
> >
> >From:    plamen kosseff <p_kosseff@prosyst.com>
> >From:    "Tobin, Brian" <Brian_Tobin@AFCC.com>
> >From:    marcello@nbase.co.il (Marcello Bracha)
> >
> >All had "auth 36dbe6c3 subscribe ietf" in either the body or Subject:.
> >
> >Is this rampant cluelessness, or is that 36dbe6c3 cookie being
> >regenerated by a broken HTML page or something?
> >
> >In the meantime, can we fix the Majordomo filter so 'auth' gets trapped
> >as well as 'subscribe' so we can return to our usual silence/flaming cycle?
> >;)
> >
> > Valdis Kletnieks
> > Operating Systems Analyst
> > Virginia Tech

--------------75184BEC2F1C68FC5D5B3CD2
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>&nbsp;
<br>&nbsp;
<p>interesting i havent sended
<br><font size=+1>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "auth 36dbe6c3 subscribe
ietf"</font>
<br>first time i look at my mail it today
<br>realy interesting
<br>&nbsp;
<p>7ways wrote:
<blockquote TYPE=CITE>I believe that is my auth, I dont understand what
is happen.
<p>Francois
<p>-----Original Message-----
<br>From: Jim Dunn &lt;jim.dunn@BT.NET>
<br>To: Valdis.Kletnieks@vt.edu &lt;Valdis.Kletnieks@vt.edu>; ietf@ietf.org
<br>&lt;ietf@ietf.org>
<br>Date: Tuesday, January 18, 2000 6:36 PM
<br>Subject: RE: Is anybody else suspicious about this?
<p>>I have noticed that the Auth code is the same everytime I have been
mailed
<br>>by Majordomo or someone has replied to the mail.( About 25 instances
so
<br>>far )
<br>>
<br>>Steve Coya has sent a message asking people not to respond to these
<br>>messages.
<br>>See below for original message from Steve.
<br>>
<br>>Regards
<br>>
<br>>Jim
<br>>-----Original Message-----
<br>>From: Steve Coya [<a href="mailto:scoya@ietf.org">mailto:scoya@ietf.org</a>]
<br>>Sent: 12 January 2000 20:08
<br>>To: ietf@ietf.org
<br>>Subject: Majordomo subscribe request message
<br>>
<br>>
<br>>
<br>>Folks,
<br>>
<br>>Please do NOT respond to the message from majordomo asking to confirm
<br>>adding ietf@ietf.org to ietf@ietf.org
<br>>
<br>>We're not sure where this/these messages originated, but are looking
into
<br>>it right now.
<br>>
<br>>Thanks and sorry for the inconvenience.
<br>>
<br>>
<br>>
<br>>Steve
<br>>
<br>>-----Original Message-----
<br>>From: Valdis.Kletnieks@vt.edu [<a href="mailto:Valdis.Kletnieks@vt.edu">mailto:Valdis.Kletnieks@vt.edu</a>]
<br>>Sent: 18 January 2000 15:42
<br>>To: ietf@ietf.org
<br>>Subject: Is anybody else suspicious about this?
<br>>
<br>>
<br>>Last 3 e-mails to the list, from:
<br>>
<br>>From:&nbsp;&nbsp;&nbsp; plamen kosseff &lt;p_kosseff@prosyst.com>
<br>>From:&nbsp;&nbsp;&nbsp; "Tobin, Brian" &lt;Brian_Tobin@AFCC.com>
<br>>From:&nbsp;&nbsp;&nbsp; marcello@nbase.co.il (Marcello Bracha)
<br>>
<br>>All had "auth 36dbe6c3 subscribe ietf" in either the body or Subject:.
<br>>
<br>>Is this rampant cluelessness, or is that 36dbe6c3 cookie being
<br>>regenerated by a broken HTML page or something?
<br>>
<br>>In the meantime, can we fix the Majordomo filter so 'auth' gets trapped
<br>>as well as 'subscribe' so we can return to our usual silence/flaming
cycle?
<br>>;)
<br>>
<br>> Valdis Kletnieks
<br>> Operating Systems Analyst
<br>> Virginia Tech</blockquote>
</html>

--------------75184BEC2F1C68FC5D5B3CD2--



From owner-ietf-outbound@ietf.org  Wed Jan 19 05:23:34 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25390
	for <ietf-web-archive@odin.ietf.org>; Wed, 19 Jan 2000 05:23:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA14910;
	Wed, 19 Jan 2000 05:21:48 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id FAA25309
	for ietf-outbound.10@ietf.org; Wed, 19 Jan 2000 05:20:02 -0500 (EST)
Received: from prosyst.com (server.prosyst.com [195.14.248.34] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA25287
	for <ietf@ietf.org>; Wed, 19 Jan 2000 05:18:37 -0500 (EST)
Message-ID: <38858F44.554648D7@prosyst.com>
Date: Wed, 19 Jan 2000 12:17:40 +0200
From: plamen kosseff <p_kosseff@prosyst.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: bg,en
MIME-Version: 1.0
To: 7ways <collignon@7ways.net>
CC: Jim Dunn <jim.dunn@BT.NET>, Valdis.Kletnieks@vt.edu, ietf@ietf.org
Subject: Re: Is anybody else suspicious about this?
References: <029e01bf61db$2d4211e0$0a01a8c0@FLC>
Content-Type: multipart/alternative;
 boundary="------------75184BEC2F1C68FC5D5B3CD2"


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





interesting i havent sended
      "auth 36dbe6c3 subscribe ietf"
first time i look at my mail it today
realy interesting


7ways wrote:

> I believe that is my auth, I dont understand what is happen.
>
> Francois
>
> -----Original Message-----
> From: Jim Dunn <jim.dunn@BT.NET>
> To: Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu>; ietf@ietf.org
> <ietf@ietf.org>
> Date: Tuesday, January 18, 2000 6:36 PM
> Subject: RE: Is anybody else suspicious about this?
>
> >I have noticed that the Auth code is the same everytime I have been mailed
> >by Majordomo or someone has replied to the mail.( About 25 instances so
> >far )
> >
> >Steve Coya has sent a message asking people not to respond to these
> >messages.
> >See below for original message from Steve.
> >
> >Regards
> >
> >Jim
> >-----Original Message-----
> >From: Steve Coya [mailto:scoya@ietf.org]
> >Sent: 12 January 2000 20:08
> >To: ietf@ietf.org
> >Subject: Majordomo subscribe request message
> >
> >
> >
> >Folks,
> >
> >Please do NOT respond to the message from majordomo asking to confirm
> >adding ietf@ietf.org to ietf@ietf.org
> >
> >We're not sure where this/these messages originated, but are looking into
> >it right now.
> >
> >Thanks and sorry for the inconvenience.
> >
> >
> >
> >Steve
> >
> >-----Original Message-----
> >From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
> >Sent: 18 January 2000 15:42
> >To: ietf@ietf.org
> >Subject: Is anybody else suspicious about this?
> >
> >
> >Last 3 e-mails to the list, from:
> >
> >From:    plamen kosseff <p_kosseff@prosyst.com>
> >From:    "Tobin, Brian" <Brian_Tobin@AFCC.com>
> >From:    marcello@nbase.co.il (Marcello Bracha)
> >
> >All had "auth 36dbe6c3 subscribe ietf" in either the body or Subject:.
> >
> >Is this rampant cluelessness, or is that 36dbe6c3 cookie being
> >regenerated by a broken HTML page or something?
> >
> >In the meantime, can we fix the Majordomo filter so 'auth' gets trapped
> >as well as 'subscribe' so we can return to our usual silence/flaming cycle?
> >;)
> >
> > Valdis Kletnieks
> > Operating Systems Analyst
> > Virginia Tech

--------------75184BEC2F1C68FC5D5B3CD2
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>&nbsp;
<br>&nbsp;
<p>interesting i havent sended
<br><font size=+1>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "auth 36dbe6c3 subscribe
ietf"</font>
<br>first time i look at my mail it today
<br>realy interesting
<br>&nbsp;
<p>7ways wrote:
<blockquote TYPE=CITE>I believe that is my auth, I dont understand what
is happen.
<p>Francois
<p>-----Original Message-----
<br>From: Jim Dunn &lt;jim.dunn@BT.NET>
<br>To: Valdis.Kletnieks@vt.edu &lt;Valdis.Kletnieks@vt.edu>; ietf@ietf.org
<br>&lt;ietf@ietf.org>
<br>Date: Tuesday, January 18, 2000 6:36 PM
<br>Subject: RE: Is anybody else suspicious about this?
<p>>I have noticed that the Auth code is the same everytime I have been
mailed
<br>>by Majordomo or someone has replied to the mail.( About 25 instances
so
<br>>far )
<br>>
<br>>Steve Coya has sent a message asking people not to respond to these
<br>>messages.
<br>>See below for original message from Steve.
<br>>
<br>>Regards
<br>>
<br>>Jim
<br>>-----Original Message-----
<br>>From: Steve Coya [<a href="mailto:scoya@ietf.org">mailto:scoya@ietf.org</a>]
<br>>Sent: 12 January 2000 20:08
<br>>To: ietf@ietf.org
<br>>Subject: Majordomo subscribe request message
<br>>
<br>>
<br>>
<br>>Folks,
<br>>
<br>>Please do NOT respond to the message from majordomo asking to confirm
<br>>adding ietf@ietf.org to ietf@ietf.org
<br>>
<br>>We're not sure where this/these messages originated, but are looking
into
<br>>it right now.
<br>>
<br>>Thanks and sorry for the inconvenience.
<br>>
<br>>
<br>>
<br>>Steve
<br>>
<br>>-----Original Message-----
<br>>From: Valdis.Kletnieks@vt.edu [<a href="mailto:Valdis.Kletnieks@vt.edu">mailto:Valdis.Kletnieks@vt.edu</a>]
<br>>Sent: 18 January 2000 15:42
<br>>To: ietf@ietf.org
<br>>Subject: Is anybody else suspicious about this?
<br>>
<br>>
<br>>Last 3 e-mails to the list, from:
<br>>
<br>>From:&nbsp;&nbsp;&nbsp; plamen kosseff &lt;p_kosseff@prosyst.com>
<br>>From:&nbsp;&nbsp;&nbsp; "Tobin, Brian" &lt;Brian_Tobin@AFCC.com>
<br>>From:&nbsp;&nbsp;&nbsp; marcello@nbase.co.il (Marcello Bracha)
<br>>
<br>>All had "auth 36dbe6c3 subscribe ietf" in either the body or Subject:.
<br>>
<br>>Is this rampant cluelessness, or is that 36dbe6c3 cookie being
<br>>regenerated by a broken HTML page or something?
<br>>
<br>>In the meantime, can we fix the Majordomo filter so 'auth' gets trapped
<br>>as well as 'subscribe' so we can return to our usual silence/flaming
cycle?
<br>>;)
<br>>
<br>> Valdis Kletnieks
<br>> Operating Systems Analyst
<br>> Virginia Tech</blockquote>
</html>

--------------75184BEC2F1C68FC5D5B3CD2--



From owner-ietf-outbound  Wed Jan 19 06:30:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA25768
	for ietf-outbound.10@ietf.org; Wed, 19 Jan 2000 06:30:04 -0500 (EST)
Received: from prosyst.com (server.prosyst.com [195.14.248.34] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25699
	for <ietf@ietf.org>; Wed, 19 Jan 2000 06:23:25 -0500 (EST)
Message-ID: <38859E49.87E401FB@prosyst.com>
Date: Wed, 19 Jan 2000 13:21:45 +0200
From: plamen kosseff <p_kosseff@prosyst.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: bg,en
MIME-Version: 1.0
To: 7ways <collignon@7ways.net>
CC: Jim Dunn <jim.dunn@BT.NET>, Valdis.Kletnieks@vt.edu, ietf@ietf.org
Subject: Re: Is anybody else suspicious about this?
References: <018601bf6269$08e55a80$0a01a8c0@FLC>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

iv checkted my e-mail account



"auth 36dbe6c3 subscribe ietf"


realy got out of my e-mail

i think we have realy big security problem here



From owner-ietf-outbound@ietf.org  Wed Jan 19 06:32:20 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25885
	for <ietf-web-archive@odin.ietf.org>; Wed, 19 Jan 2000 06:32:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA16061;
	Wed, 19 Jan 2000 06:30:44 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id GAA25768
	for ietf-outbound.10@ietf.org; Wed, 19 Jan 2000 06:30:04 -0500 (EST)
Received: from prosyst.com (server.prosyst.com [195.14.248.34] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25699
	for <ietf@ietf.org>; Wed, 19 Jan 2000 06:23:25 -0500 (EST)
Message-ID: <38859E49.87E401FB@prosyst.com>
Date: Wed, 19 Jan 2000 13:21:45 +0200
From: plamen kosseff <p_kosseff@prosyst.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: bg,en
MIME-Version: 1.0
To: 7ways <collignon@7ways.net>
CC: Jim Dunn <jim.dunn@BT.NET>, Valdis.Kletnieks@vt.edu, ietf@ietf.org
Subject: Re: Is anybody else suspicious about this?
References: <018601bf6269$08e55a80$0a01a8c0@FLC>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

iv checkted my e-mail account



"auth 36dbe6c3 subscribe ietf"


realy got out of my e-mail

i think we have realy big security problem here



From owner-ietf-outbound  Thu Jan 20 15:21:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA14324
	for ietf-outbound.10@ietf.org; Thu, 20 Jan 2000 15:20:02 -0500 (EST)
Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14195
	for <ietf@ietf.org>; Thu, 20 Jan 2000 15:13:12 -0500 (EST)
Received: from ron ([195.121.210.225]) by smtp04.wxs.nl
          (Netscape Messaging Server 3.61)  with SMTP id AAA180B
          for <ietf@ietf.org>; Thu, 20 Jan 2000 21:12:40 +0100
Message-ID: <01b701bf6383$8d0f02a0$77d379c3@ron>
From: "Laurens Holst" <laurensh1@yahoo.com>
To: <ietf@ietf.org>
Subject: Loggin' in on an ISP
Date: Thu, 20 Jan 2000 21:15:37 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I am making an internet implementation for my MSX-computer-from-the-80s and
at the moment I am at the DUN, but there is very little information about
that (at least, I couldn't find any). So after some puzzling around with my
webserver I decided to call my MSX modem with my ISDN Analog modem
emulator, and to log what I recieved.

This is the log-data of the first packet the PC sent to the MSX. The problem
is that it adds a few bytes in the beginning (7F FF 7D 23), then sends the
PPP header (C0 21), and then sends most of the further bytes as FD 20+byte,
so a 17 becomes a FD 37, you can also look below. But at a certain moment
some bytes don't send the FD's anymore (the bytes without dashes
inbetween -0B B2 97-, which correspond with the recieved data 5A 74 5C)...
Whaa *snif* I DON'T GET IT ANYMORE!!! I'm desperate, can anybody help me???

Now take a short look at my 'logged' data and then scroll down...

;RECEIVED DATA:
; 7E FF 7D 23 C0 21 7D 21 7D 21 7D 20 7D 37 7D 22 7D 26
; 7D 20 7D 2A 7D 20 7D 20 7D 25 7D 26 7D 20 5A 74 5C 7D
; 27 7D 22 7D 28 7D 22 7D 2D 7D 23 7D 26 C8 F8 7E
;
;SENT PPP DATA (-- = nothing sent):
; -- -- -- -- c0 21 -- 01 -- 01 -- 00 -- 17 -- 02 -- 06
; -- 00 -- 0a -- 00 -- 00 -- 05 -- 06 -- 00 0b b2 97 --
; 07 -- 02 -- 08 -- 02 -- 0d -- 03 -- 06 -- --

Is there another protocol between the RS232 and PPP I missed??? I recall
some document in which they mentioned %01111110 (=#7E) as a sequencer byte
or something like that, but I didn't save the document. If anyone could
point me to an RFC containing the nessacary info I'd be glad.

Or maybe my modem-protocol settings are incorrect??? I use 8N1 (8 bits, no
parity, 1 stopbit), and as far as I know Windows uses the same settings...

Or is it just an error in the ISDN modem-emulator??? It says it is a beta,
but I can log in to BBSes with it so I think it works correctly, but
ofcourse it might have problems with only my modem... But this option seems
not very likely to me.

Thanks in advance, and if no-one of you knows how to solve my problem then
maybe you can suggest another place where I might find an answer???


~Grauw


--
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<
 email me: laurensh1@yahoo.com or ICQ: 10196372
   visit the Datax homepage at http://datax.cjb.net/
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<




From owner-ietf-outbound@ietf.org  Thu Jan 20 15:23:32 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14431
	for <ietf-web-archive@odin.ietf.org>; Thu, 20 Jan 2000 15:23:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA11640;
	Thu, 20 Jan 2000 15:21:55 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA14324
	for ietf-outbound.10@ietf.org; Thu, 20 Jan 2000 15:20:02 -0500 (EST)
Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14195
	for <ietf@ietf.org>; Thu, 20 Jan 2000 15:13:12 -0500 (EST)
Received: from ron ([195.121.210.225]) by smtp04.wxs.nl
          (Netscape Messaging Server 3.61)  with SMTP id AAA180B
          for <ietf@ietf.org>; Thu, 20 Jan 2000 21:12:40 +0100
Message-ID: <01b701bf6383$8d0f02a0$77d379c3@ron>
From: "Laurens Holst" <laurensh1@yahoo.com>
To: <ietf@ietf.org>
Subject: Loggin' in on an ISP
Date: Thu, 20 Jan 2000 21:15:37 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I am making an internet implementation for my MSX-computer-from-the-80s and
at the moment I am at the DUN, but there is very little information about
that (at least, I couldn't find any). So after some puzzling around with my
webserver I decided to call my MSX modem with my ISDN Analog modem
emulator, and to log what I recieved.

This is the log-data of the first packet the PC sent to the MSX. The problem
is that it adds a few bytes in the beginning (7F FF 7D 23), then sends the
PPP header (C0 21), and then sends most of the further bytes as FD 20+byte,
so a 17 becomes a FD 37, you can also look below. But at a certain moment
some bytes don't send the FD's anymore (the bytes without dashes
inbetween -0B B2 97-, which correspond with the recieved data 5A 74 5C)...
Whaa *snif* I DON'T GET IT ANYMORE!!! I'm desperate, can anybody help me???

Now take a short look at my 'logged' data and then scroll down...

;RECEIVED DATA:
; 7E FF 7D 23 C0 21 7D 21 7D 21 7D 20 7D 37 7D 22 7D 26
; 7D 20 7D 2A 7D 20 7D 20 7D 25 7D 26 7D 20 5A 74 5C 7D
; 27 7D 22 7D 28 7D 22 7D 2D 7D 23 7D 26 C8 F8 7E
;
;SENT PPP DATA (-- = nothing sent):
; -- -- -- -- c0 21 -- 01 -- 01 -- 00 -- 17 -- 02 -- 06
; -- 00 -- 0a -- 00 -- 00 -- 05 -- 06 -- 00 0b b2 97 --
; 07 -- 02 -- 08 -- 02 -- 0d -- 03 -- 06 -- --

Is there another protocol between the RS232 and PPP I missed??? I recall
some document in which they mentioned %01111110 (=#7E) as a sequencer byte
or something like that, but I didn't save the document. If anyone could
point me to an RFC containing the nessacary info I'd be glad.

Or maybe my modem-protocol settings are incorrect??? I use 8N1 (8 bits, no
parity, 1 stopbit), and as far as I know Windows uses the same settings...

Or is it just an error in the ISDN modem-emulator??? It says it is a beta,
but I can log in to BBSes with it so I think it works correctly, but
ofcourse it might have problems with only my modem... But this option seems
not very likely to me.

Thanks in advance, and if no-one of you knows how to solve my problem then
maybe you can suggest another place where I might find an answer???


~Grauw


--
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<
 email me: laurensh1@yahoo.com or ICQ: 10196372
   visit the Datax homepage at http://datax.cjb.net/
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<




From owner-ietf-outbound  Sun Jan 23 00:12:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA16388
	for ietf-outbound.10@ietf.org; Sun, 23 Jan 2000 00:10:01 -0500 (EST)
Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16353
	for <ietf@ietf.org>; Sun, 23 Jan 2000 00:07:43 -0500 (EST)
Received: from us.networkcs.com (us.networkcs.com [137.66.11.15])
	by marcos.networkcs.com (8.9.3/8.9.3) with ESMTP id XAA43431
	for <ietf@ietf.org>; Sat, 22 Jan 2000 23:07:43 -0600 (CST)
	(envelope-from salo@us.networkcs.com)
Received: (from salo@localhost)
	by us.networkcs.com (8.9.2/8.9.2) id XAA43341
	for ietf@ietf.org; Sat, 22 Jan 2000 23:07:43 -0600 (CST)
	(envelope-from salo)
Date: Sat, 22 Jan 2000 23:07:43 -0600 (CST)
From: Tim Salo <salo@networkcs.com>
Message-Id: <200001230507.XAA43341@us.networkcs.com>
To: ietf@ietf.org
Subject: Telemetry Protocols?

Has the IETF ever undertaken any work related to telemetry or wireless
telemetry protocols?  (Or, is some even underway that I don't know
about?)

Is this an activity better suited for some other organization, (even if
these sorts of things use IP)?

I suppose Automatic Vehicle Location (AVL) protocols could fall in this
category, as well, (something that looks like it will become Internet-
related pretty quickly).

-tjs



From owner-ietf-outbound@ietf.org  Sun Jan 23 00:13:58 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16437
	for <ietf-web-archive@odin.ietf.org>; Sun, 23 Jan 2000 00:13:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA09349;
	Sun, 23 Jan 2000 00:12:20 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id AAA16388
	for ietf-outbound.10@ietf.org; Sun, 23 Jan 2000 00:10:01 -0500 (EST)
Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16353
	for <ietf@ietf.org>; Sun, 23 Jan 2000 00:07:43 -0500 (EST)
Received: from us.networkcs.com (us.networkcs.com [137.66.11.15])
	by marcos.networkcs.com (8.9.3/8.9.3) with ESMTP id XAA43431
	for <ietf@ietf.org>; Sat, 22 Jan 2000 23:07:43 -0600 (CST)
	(envelope-from salo@us.networkcs.com)
Received: (from salo@localhost)
	by us.networkcs.com (8.9.2/8.9.2) id XAA43341
	for ietf@ietf.org; Sat, 22 Jan 2000 23:07:43 -0600 (CST)
	(envelope-from salo)
Date: Sat, 22 Jan 2000 23:07:43 -0600 (CST)
From: Tim Salo <salo@networkcs.com>
Message-Id: <200001230507.XAA43341@us.networkcs.com>
To: ietf@ietf.org
Subject: Telemetry Protocols?

Has the IETF ever undertaken any work related to telemetry or wireless
telemetry protocols?  (Or, is some even underway that I don't know
about?)

Is this an activity better suited for some other organization, (even if
these sorts of things use IP)?

I suppose Automatic Vehicle Location (AVL) protocols could fall in this
category, as well, (something that looks like it will become Internet-
related pretty quickly).

-tjs



From owner-ietf-outbound  Sun Jan 23 03:14:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA00806
	for ietf-outbound.10@ietf.org; Sun, 23 Jan 2000 03:10:02 -0500 (EST)
Received: from sj-mailhub-2.cisco.com (sj-mailhub-2.cisco.com [171.69.43.88])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00672
	for <ietf@ietf.org>; Sun, 23 Jan 2000 03:08:32 -0500 (EST)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by sj-mailhub-2.cisco.com (8.9.1a/8.9.1) with ESMTP id AAA22875;
	Sun, 23 Jan 2000 00:10:31 -0800 (PST)
Received: from p7020-img-nt (sj-dial-2-20.cisco.com [171.68.181.21]) by rhino (SMI-8.6/CISCO.WS.1.1) with SMTP id AAA23971; Sun, 23 Jan 2000 00:12:14 -0800
Message-Id: <4.1.20000123090251.01c47bb0@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Sun, 23 Jan 2000 09:07:00 +0100
To: Tim Salo <salo@networkcs.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: Telemetry Protocols?
Cc: ietf@ietf.org
In-Reply-To: <200001230507.XAA43341@us.networkcs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 11:07 PM 1/22/00 -0600, Tim Salo wrote:
>Has the IETF ever undertaken any work related to telemetry or wireless
>telemetry protocols?  (Or, is some even underway that I don't know
>about?)

not to my knowledge, other than SNMP if you view it in that light.

>Is this an activity better suited for some other organization, (even if
>these sorts of things use IP)?

maybe, maybe not. If the protocol were specific to some application -
avionics say - one could argue that there may exist an application-specific
group that would be more focused on the problem. If it were reasonably
general ("here's how you report data items, get an ASN.1 OID to identify
your favorite data item and all its attributes" or some such thing) and
especially if it used an IETF transport protocol (would SCTP be appropriate
for such things?) I could be argued the other way.

>I suppose Automatic Vehicle Location (AVL) protocols could fall in this
>category, as well, (something that looks like it will become Internet-
>related pretty quickly).

such things might, for example, use IP Multicast. Car beeps multicast
things to a satellite, the satellite funnels them to ground stations in
suitable parts of the world.



From owner-ietf-outbound@ietf.org  Sun Jan 23 03:16:15 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01340
	for <ietf-web-archive@odin.ietf.org>; Sun, 23 Jan 2000 03:16:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA18833;
	Sun, 23 Jan 2000 03:14:36 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA00806
	for ietf-outbound.10@ietf.org; Sun, 23 Jan 2000 03:10:02 -0500 (EST)
Received: from sj-mailhub-2.cisco.com (sj-mailhub-2.cisco.com [171.69.43.88])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00672
	for <ietf@ietf.org>; Sun, 23 Jan 2000 03:08:32 -0500 (EST)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by sj-mailhub-2.cisco.com (8.9.1a/8.9.1) with ESMTP id AAA22875;
	Sun, 23 Jan 2000 00:10:31 -0800 (PST)
Received: from p7020-img-nt (sj-dial-2-20.cisco.com [171.68.181.21]) by rhino (SMI-8.6/CISCO.WS.1.1) with SMTP id AAA23971; Sun, 23 Jan 2000 00:12:14 -0800
Message-Id: <4.1.20000123090251.01c47bb0@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Sun, 23 Jan 2000 09:07:00 +0100
To: Tim Salo <salo@networkcs.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: Telemetry Protocols?
Cc: ietf@ietf.org
In-Reply-To: <200001230507.XAA43341@us.networkcs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 11:07 PM 1/22/00 -0600, Tim Salo wrote:
>Has the IETF ever undertaken any work related to telemetry or wireless
>telemetry protocols?  (Or, is some even underway that I don't know
>about?)

not to my knowledge, other than SNMP if you view it in that light.

>Is this an activity better suited for some other organization, (even if
>these sorts of things use IP)?

maybe, maybe not. If the protocol were specific to some application -
avionics say - one could argue that there may exist an application-specific
group that would be more focused on the problem. If it were reasonably
general ("here's how you report data items, get an ASN.1 OID to identify
your favorite data item and all its attributes" or some such thing) and
especially if it used an IETF transport protocol (would SCTP be appropriate
for such things?) I could be argued the other way.

>I suppose Automatic Vehicle Location (AVL) protocols could fall in this
>category, as well, (something that looks like it will become Internet-
>related pretty quickly).

such things might, for example, use IP Multicast. Car beeps multicast
things to a satellite, the satellite funnels them to ground stations in
suitable parts of the world.



From owner-ietf-outbound  Sun Jan 23 03:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA02457
	for ietf-outbound.10@ietf.org; Sun, 23 Jan 2000 03:30:02 -0500 (EST)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02415
	for <ietf@ietf.org>; Sun, 23 Jan 2000 03:29:54 -0500 (EST)
Received: from randy by rip.psg.com with local (Exim 3.12 #1)
	id 12CIP6-000L3Y-00; Sun, 23 Jan 2000 00:29:48 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Tim Salo <salo@networkcs.com>
Cc: ietf@ietf.org
Subject: Re: Telemetry Protocols?
References: <200001230507.XAA43341@us.networkcs.com>
Message-Id: <E12CIP6-000L3Y-00@rip.psg.com>
Date: Sun, 23 Jan 2000 00:29:48 -0800
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

there is a nascent bof on getting location from wireless.  mailing list is
<ext-ip-location@research.nokia.com>

randy



From owner-ietf-outbound@ietf.org  Sun Jan 23 03:31:13 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02650
	for <ietf-web-archive@odin.ietf.org>; Sun, 23 Jan 2000 03:31:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA18951;
	Sun, 23 Jan 2000 03:29:33 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA02457
	for ietf-outbound.10@ietf.org; Sun, 23 Jan 2000 03:30:02 -0500 (EST)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02415
	for <ietf@ietf.org>; Sun, 23 Jan 2000 03:29:54 -0500 (EST)
Received: from randy by rip.psg.com with local (Exim 3.12 #1)
	id 12CIP6-000L3Y-00; Sun, 23 Jan 2000 00:29:48 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Tim Salo <salo@networkcs.com>
Cc: ietf@ietf.org
Subject: Re: Telemetry Protocols?
References: <200001230507.XAA43341@us.networkcs.com>
Message-Id: <E12CIP6-000L3Y-00@rip.psg.com>
Date: Sun, 23 Jan 2000 00:29:48 -0800
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

there is a nascent bof on getting location from wireless.  mailing list is
<ext-ip-location@research.nokia.com>

randy



From owner-ietf-outbound  Sun Jan 23 20:50:58 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA13121
	for ietf-outbound.10@ietf.org; Sun, 23 Jan 2000 20:50:02 -0500 (EST)
Received: from mailhub.iastate.edu (mailhub.iastate.edu [129.186.1.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13096
	for <ietf@ietf.org>; Sun, 23 Jan 2000 20:48:56 -0500 (EST)
Received: from pacific.eng.iastate.edu (pacific.eng.iastate.edu [129.186.17.23])
	by mailhub.iastate.edu (8.9.3/8.9.3) with ESMTP id TAA04825
	for <ietf@ietf.org>; Sun, 23 Jan 2000 19:48:57 -0600
Received: from telnet-2.eng.iastate.edu (telnet-2.eng.iastate.edu [129.186.23.46]) by pacific.eng.iastate.edu (8.8.5/8.8.5) with ESMTP id TAA374565 for <ietf@ietf.org>; Sun, 23 Jan 2000 19:48:57 -0600 (CST)
Received: from localhost by telnet-2.eng.iastate.edu (8.8.4) id BAA15736; Mon, 24 Jan 2000 01:48:56 GMT
Date: Sun, 23 Jan 2000 19:48:56 -0600
From: Murali K Viswanathan <muralikv@iastate.edu>
To: ietf@ietf.org
Subject: Reg. TCP/IP error response
Message-ID: <Pine.SGI.4.05.10001231947510.15018-100000@telnet-2.eng.iastate.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Hi Guys,
I had sent a question to the group some time back, but unfortunately for
me it got drowned in the discussion that was occuring then. So I am
presenting my question again hoping to find favor with someone who could
answer these.

what does the TCP standard say about response to frames received in error?
1. Is the packet just discarded?
2. Is a duplicate acknowledgmenet sent for the previous frame?
3. Or maybe it depends on individual implementations?

Thanks,
Mur
                 

Murali K Viswanathan
muralikv@iastate.edu



From owner-ietf-outbound@ietf.org  Sun Jan 23 20:52:17 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13167
	for <ietf-web-archive@odin.ietf.org>; Sun, 23 Jan 2000 20:52:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA12954;
	Sun, 23 Jan 2000 20:50:39 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id UAA13121
	for ietf-outbound.10@ietf.org; Sun, 23 Jan 2000 20:50:02 -0500 (EST)
Received: from mailhub.iastate.edu (mailhub.iastate.edu [129.186.1.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13096
	for <ietf@ietf.org>; Sun, 23 Jan 2000 20:48:56 -0500 (EST)
Received: from pacific.eng.iastate.edu (pacific.eng.iastate.edu [129.186.17.23])
	by mailhub.iastate.edu (8.9.3/8.9.3) with ESMTP id TAA04825
	for <ietf@ietf.org>; Sun, 23 Jan 2000 19:48:57 -0600
Received: from telnet-2.eng.iastate.edu (telnet-2.eng.iastate.edu [129.186.23.46]) by pacific.eng.iastate.edu (8.8.5/8.8.5) with ESMTP id TAA374565 for <ietf@ietf.org>; Sun, 23 Jan 2000 19:48:57 -0600 (CST)
Received: from localhost by telnet-2.eng.iastate.edu (8.8.4) id BAA15736; Mon, 24 Jan 2000 01:48:56 GMT
Date: Sun, 23 Jan 2000 19:48:56 -0600
From: Murali K Viswanathan <muralikv@iastate.edu>
To: ietf@ietf.org
Subject: Reg. TCP/IP error response
Message-ID: <Pine.SGI.4.05.10001231947510.15018-100000@telnet-2.eng.iastate.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Hi Guys,
I had sent a question to the group some time back, but unfortunately for
me it got drowned in the discussion that was occuring then. So I am
presenting my question again hoping to find favor with someone who could
answer these.

what does the TCP standard say about response to frames received in error?
1. Is the packet just discarded?
2. Is a duplicate acknowledgmenet sent for the previous frame?
3. Or maybe it depends on individual implementations?

Thanks,
Mur
                 

Murali K Viswanathan
muralikv@iastate.edu



From owner-ietf-outbound  Mon Jan 24 03:11:05 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA29429
	for ietf-outbound.10@ietf.org; Mon, 24 Jan 2000 03:10:02 -0500 (EST)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29393
	for <ietf@ietf.org>; Mon, 24 Jan 2000 03:01:10 -0500 (EST)
Received: from alden (alden.maxware.no [10.128.1.21])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id JAA12885;
	Mon, 24 Jan 2000 09:00:46 +0100
Message-Id: <4.2.0.58.20000124082131.062f2e30@dokka.maxware.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 24 Jan 2000 08:33:36 +0100
To: Murali K Viswanathan <muralikv@iastate.edu>, ietf@ietf.org
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: Reg. TCP/IP error response
In-Reply-To: <Pine.SGI.4.05.10001231947510.15018-100000@telnet-2.eng.ias
 tate.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 19:48 23.01.00 -0600, Murali K Viswanathan wrote:

>Hi Guys,
>I had sent a question to the group some time back, but unfortunately for
>me it got drowned in the discussion that was occuring then. So I am
>presenting my question again hoping to find favor with someone who could
>answer these.
>
>what does the TCP standard say about response to frames received in error?

what do you mean by "received in error"?
Datagrams with incorrect checksums are usually discarded at the link layer.
Datagrams with incorrect header checksums are discarded.
Datagrams with sequence numbers before the current position are discarded.
Datagrams with sequence numbers after the current position are fairly well 
discussed in the RFC.

>1. Is the packet just discarded?
>2. Is a duplicate acknowledgmenet sent for the previous frame?
>3. Or maybe it depends on individual implementations?

Get your question straight, and the answer may become obvious.

                         Harald
--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound@ietf.org  Mon Jan 24 03:19:16 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29485
	for <ietf-web-archive@odin.ietf.org>; Mon, 24 Jan 2000 03:19:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA26941;
	Mon, 24 Jan 2000 03:17:32 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA29429
	for ietf-outbound.10@ietf.org; Mon, 24 Jan 2000 03:10:02 -0500 (EST)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29393
	for <ietf@ietf.org>; Mon, 24 Jan 2000 03:01:10 -0500 (EST)
Received: from alden (alden.maxware.no [10.128.1.21])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id JAA12885;
	Mon, 24 Jan 2000 09:00:46 +0100
Message-Id: <4.2.0.58.20000124082131.062f2e30@dokka.maxware.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 24 Jan 2000 08:33:36 +0100
To: Murali K Viswanathan <muralikv@iastate.edu>, ietf@ietf.org
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: Reg. TCP/IP error response
In-Reply-To: <Pine.SGI.4.05.10001231947510.15018-100000@telnet-2.eng.ias
 tate.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 19:48 23.01.00 -0600, Murali K Viswanathan wrote:

>Hi Guys,
>I had sent a question to the group some time back, but unfortunately for
>me it got drowned in the discussion that was occuring then. So I am
>presenting my question again hoping to find favor with someone who could
>answer these.
>
>what does the TCP standard say about response to frames received in error?

what do you mean by "received in error"?
Datagrams with incorrect checksums are usually discarded at the link layer.
Datagrams with incorrect header checksums are discarded.
Datagrams with sequence numbers before the current position are discarded.
Datagrams with sequence numbers after the current position are fairly well 
discussed in the RFC.

>1. Is the packet just discarded?
>2. Is a duplicate acknowledgmenet sent for the previous frame?
>3. Or maybe it depends on individual implementations?

Get your question straight, and the answer may become obvious.

                         Harald
--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Mon Jan 24 13:00:58 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA16512
	for ietf-outbound.10@ietf.org; Mon, 24 Jan 2000 13:00:03 -0500 (EST)
Received: from sentry (firewall-user@sentry.gw.tislabs.com [192.94.214.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16369
	for <ietf@ietf.org>; Mon, 24 Jan 2000 12:55:47 -0500 (EST)
Received: by sentry; id MAA27746; Mon, 24 Jan 2000 12:57:01 -0500 (EST)
Received: from clipper.gw.tislabs.com(10.33.1.2) by sentry.gw.tislabs.com via smap (V5.5)
	id xma027729; Mon, 24 Jan 00 12:56:33 -0500
Received: (from balenson@localhost)
	by clipper.gw.tislabs.com (8.9.3/8.9.1) id MAA11473
	for ietf@ietf.org; Mon, 24 Jan 2000 12:52:23 -0500 (EST)
Date: Mon, 24 Jan 2000 12:52:23 -0500 (EST)
From: "David M. Balenson" <balenson@tislabs.com>
Message-Id: <200001241752.MAA11473@clipper.gw.tislabs.com>
To: ietf@ietf.org
Subject: Last chance to register for NDSS 2000


L A S T   C H A N C E   -  R E G I S T E R   F O R   N D S S   2 0 0 0

THE INTERNET SOCIETY'S
Year 2000 NETWORK AND DISTRIBUTED SYSTEM SECURITY (NDSS) SYMPOSIUM
February 2-4, 2000
Catamaran Resort Hotel, San Diego, California
General Chair:   Steve Welke, Trusted Computer Solutions
Program Chairs:  Gene Tsudik, USC/Information Sciences Institute
		 Avi Rubin, AT&T Labs - Research

ONLINE INFORMATION AND REGISTRATION:  http://www.isoc.org/ndss2000
REGISTER ONLINE ON OR BEFORE WEDNESDAY, JANUARY 26
REGISTER ONSITE AFTER WEDNESDAY, JANUARY 26

The 7th annual NDSS Symposium brings together researchers,
implementers, and users of network and distributed system security
technologies to discuss today's important security issues and
challenges.  The Symposium provides a mix of technical papers and
panel presentations that describe promising new approaches to
security problems that are practical and, to the extent possible,
have been implemented.  NDSS fosters the exchange of technical
information and encourages the Internet community to deploy available
security technologies and develop new solutions to unsolved problems.

KEYNOTE SPEAKER: Gene Spafford, Professor of Computer Sciences at
Purdue University, an expert in information security, computer crime
investigation and information ethics.  Spaf (as he is known to his
friends, colleagues, and students) is director of the Purdue CERIAS
(Center for Education and Research in Information Assurance and
Security), and was the founder and director of the (now superseded)
COAST Laboratory. 

THIS YEAR'S TOPICS INCLUDE:
- Automated Detection of Buffer Overrun Vulnerabilities
- User-Level Infrastructure for System Call Interposition
- Optimized Group Rekey for Group Communication Systems
- IPSec-based Host Architecture for Secure  Internet Multicast
- The Economics of Security
- Automatic Generation of Security Protocols
- Security Protocols for SPKI-based Delegation Systems
- Secure Border Gateway Protocol (S-BGP)
- Analysis of a Fair Exchange Protocol
- Secure Password-Based Protocols for TLS
- Chameleon Signatures
- Lightweight Tool for Detecting Web Server Attacks
- Adaptive and Agile Applications Using Intrusion Detection
- Secure Virtual Enclaves
- Encrypted rlogin Connections Created With Kerberos IV
- Accountability and Control of Process Creation in Metasystems
- Red Teaming and Network Security

PRE-CONFERENCE TECHNICAL TUTORIALS:
- Network Security Protocol Standards, Dr. Stephen T. Kent
- Deployed and Emerging Security Systems for the Internet, Dr. Radia
  Perlman and Charlie Kaufman
- Mobile Code Security and Java 2 Architecture, Dr. Gary McGraw
- Cryptography 101, Dr. Aviel D. Rubin
- Public Key Infrastructure - The Truth and How to Find It, Dr. Daniel
  E. Geer, Jr.
- An Introduction to Intrusion Detection Technology, Mr. Mark Wood 

FOR MORE INFORMATION contact the Internet Society:
  Internet Society, 11150 Sunset Hills Road, Reston, VA, 20190 USA
  Phone: +1-703-326-9880         Fax: +1-703-326-9881
  E-mail: ndss2000reg@isoc.org   URL: http://www.isoc.org/ndss2000/

SPONSORSHIP OPPORTUNITIES AVAILABLE!  Take advantage of this high
visibility event.  Contact Carla Rosenfeld at the Internet Society
at +1-703-326-9880 or send e-mail to carla@isoc.org.

THE INTERNET SOCIETY is a non-governmental organization for global
cooperation and coordination for the Internet and its
internetworking technologies and applications.



From owner-ietf-outbound@ietf.org  Mon Jan 24 13:02:34 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16675
	for <ietf-web-archive@odin.ietf.org>; Mon, 24 Jan 2000 13:02:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA17533;
	Mon, 24 Jan 2000 13:00:47 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA16512
	for ietf-outbound.10@ietf.org; Mon, 24 Jan 2000 13:00:03 -0500 (EST)
Received: from sentry (firewall-user@sentry.gw.tislabs.com [192.94.214.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16369
	for <ietf@ietf.org>; Mon, 24 Jan 2000 12:55:47 -0500 (EST)
Received: by sentry; id MAA27746; Mon, 24 Jan 2000 12:57:01 -0500 (EST)
Received: from clipper.gw.tislabs.com(10.33.1.2) by sentry.gw.tislabs.com via smap (V5.5)
	id xma027729; Mon, 24 Jan 00 12:56:33 -0500
Received: (from balenson@localhost)
	by clipper.gw.tislabs.com (8.9.3/8.9.1) id MAA11473
	for ietf@ietf.org; Mon, 24 Jan 2000 12:52:23 -0500 (EST)
Date: Mon, 24 Jan 2000 12:52:23 -0500 (EST)
From: "David M. Balenson" <balenson@tislabs.com>
Message-Id: <200001241752.MAA11473@clipper.gw.tislabs.com>
To: ietf@ietf.org
Subject: Last chance to register for NDSS 2000


L A S T   C H A N C E   -  R E G I S T E R   F O R   N D S S   2 0 0 0

THE INTERNET SOCIETY'S
Year 2000 NETWORK AND DISTRIBUTED SYSTEM SECURITY (NDSS) SYMPOSIUM
February 2-4, 2000
Catamaran Resort Hotel, San Diego, California
General Chair:   Steve Welke, Trusted Computer Solutions
Program Chairs:  Gene Tsudik, USC/Information Sciences Institute
		 Avi Rubin, AT&T Labs - Research

ONLINE INFORMATION AND REGISTRATION:  http://www.isoc.org/ndss2000
REGISTER ONLINE ON OR BEFORE WEDNESDAY, JANUARY 26
REGISTER ONSITE AFTER WEDNESDAY, JANUARY 26

The 7th annual NDSS Symposium brings together researchers,
implementers, and users of network and distributed system security
technologies to discuss today's important security issues and
challenges.  The Symposium provides a mix of technical papers and
panel presentations that describe promising new approaches to
security problems that are practical and, to the extent possible,
have been implemented.  NDSS fosters the exchange of technical
information and encourages the Internet community to deploy available
security technologies and develop new solutions to unsolved problems.

KEYNOTE SPEAKER: Gene Spafford, Professor of Computer Sciences at
Purdue University, an expert in information security, computer crime
investigation and information ethics.  Spaf (as he is known to his
friends, colleagues, and students) is director of the Purdue CERIAS
(Center for Education and Research in Information Assurance and
Security), and was the founder and director of the (now superseded)
COAST Laboratory. 

THIS YEAR'S TOPICS INCLUDE:
- Automated Detection of Buffer Overrun Vulnerabilities
- User-Level Infrastructure for System Call Interposition
- Optimized Group Rekey for Group Communication Systems
- IPSec-based Host Architecture for Secure  Internet Multicast
- The Economics of Security
- Automatic Generation of Security Protocols
- Security Protocols for SPKI-based Delegation Systems
- Secure Border Gateway Protocol (S-BGP)
- Analysis of a Fair Exchange Protocol
- Secure Password-Based Protocols for TLS
- Chameleon Signatures
- Lightweight Tool for Detecting Web Server Attacks
- Adaptive and Agile Applications Using Intrusion Detection
- Secure Virtual Enclaves
- Encrypted rlogin Connections Created With Kerberos IV
- Accountability and Control of Process Creation in Metasystems
- Red Teaming and Network Security

PRE-CONFERENCE TECHNICAL TUTORIALS:
- Network Security Protocol Standards, Dr. Stephen T. Kent
- Deployed and Emerging Security Systems for the Internet, Dr. Radia
  Perlman and Charlie Kaufman
- Mobile Code Security and Java 2 Architecture, Dr. Gary McGraw
- Cryptography 101, Dr. Aviel D. Rubin
- Public Key Infrastructure - The Truth and How to Find It, Dr. Daniel
  E. Geer, Jr.
- An Introduction to Intrusion Detection Technology, Mr. Mark Wood 

FOR MORE INFORMATION contact the Internet Society:
  Internet Society, 11150 Sunset Hills Road, Reston, VA, 20190 USA
  Phone: +1-703-326-9880         Fax: +1-703-326-9881
  E-mail: ndss2000reg@isoc.org   URL: http://www.isoc.org/ndss2000/

SPONSORSHIP OPPORTUNITIES AVAILABLE!  Take advantage of this high
visibility event.  Contact Carla Rosenfeld at the Internet Society
at +1-703-326-9880 or send e-mail to carla@isoc.org.

THE INTERNET SOCIETY is a non-governmental organization for global
cooperation and coordination for the Internet and its
internetworking technologies and applications.



From owner-ietf-outbound  Mon Jan 24 15:30:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23471
	for ietf-outbound.10@ietf.org; Mon, 24 Jan 2000 15:30:03 -0500 (EST)
Received: from enst.enst.fr (enst.enst.fr [137.194.2.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23297
	for <ietf@ietf.org>; Mon, 24 Jan 2000 15:25:13 -0500 (EST)
Received: from email.enst.fr (muse.enst.fr [137.194.2.33])
	by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id VAA22534
	for <ietf@ietf.org>; Mon, 24 Jan 2000 21:24:55 +0100 (MET)
Received: from enst.fr (blabla.enst.fr [137.194.160.119])
	by email.enst.fr (8.9.3/8.9.3) with ESMTP id VAA27162
	for <ietf@ietf.org>; Mon, 24 Jan 2000 21:24:54 +0100 (MET)
Message-ID: <388CB554.BEE5A1A0@enst.fr>
Date: Mon, 24 Jan 2000 21:25:56 +0100
From: "Fayçal Bennani" <Faycal.Bennani@enst.fr>
X-Mailer: Mozilla 4.08 [en] (WinNT; I)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: unsiscribe
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

unsiscribe



From owner-ietf-outbound@ietf.org  Mon Jan 24 15:32:42 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23717
	for <ietf-web-archive@odin.ietf.org>; Mon, 24 Jan 2000 15:32:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA24239;
	Mon, 24 Jan 2000 15:30:57 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23471
	for ietf-outbound.10@ietf.org; Mon, 24 Jan 2000 15:30:03 -0500 (EST)
Received: from enst.enst.fr (enst.enst.fr [137.194.2.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23297
	for <ietf@ietf.org>; Mon, 24 Jan 2000 15:25:13 -0500 (EST)
Received: from email.enst.fr (muse.enst.fr [137.194.2.33])
	by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id VAA22534
	for <ietf@ietf.org>; Mon, 24 Jan 2000 21:24:55 +0100 (MET)
Received: from enst.fr (blabla.enst.fr [137.194.160.119])
	by email.enst.fr (8.9.3/8.9.3) with ESMTP id VAA27162
	for <ietf@ietf.org>; Mon, 24 Jan 2000 21:24:54 +0100 (MET)
Message-ID: <388CB554.BEE5A1A0@enst.fr>
Date: Mon, 24 Jan 2000 21:25:56 +0100
From: "Fayçal Bennani" <Faycal.Bennani@enst.fr>
X-Mailer: Mozilla 4.08 [en] (WinNT; I)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: unsiscribe
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

unsiscribe



From owner-ietf-outbound  Mon Jan 24 17:20:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA27225
	for ietf-outbound.10@ietf.org; Mon, 24 Jan 2000 17:20:02 -0500 (EST)
Received: from orion.usno.navy.mil (dnm@orion.usno.navy.mil [192.5.41.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26937
	for <ietf@ietf.org>; Mon, 24 Jan 2000 17:15:28 -0500 (EST)
Received: (from dnm@localhost) by orion.usno.navy.mil (8.8.6 (PHNE_14041)/8.7.1) id WAA01086; Mon, 24 Jan 2000 22:15:21 GMT
From: Demetrios "N." Matsakis <dnm@orion.usno.navy.mil>
Message-Id: <200001242215.WAA01086@orion.usno.navy.mil>
Subject: Leap Second Questinnaire
To: ietf@ietf.org, sob@harvard.edu, fred@cisco.com
Date: Mon, 24 Jan 2000 22:15:21 +0000 (UTC)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Dear IETF member,

Several months ago, I sent out the following questionnaire concerning
the possibility that leap seconds might be discontinued (a discussion of
the reasons is provided at the end).  The original request asked for a response 
by January 15, but we are extending that so as to reach a larger 
constituency, such as the IETF.

I am anticipating that this will be distributed via an email exploder,
and would appreciate a response by anyone interested by February 15.

Although all responses will be tabulated, we are most interested in 
finding verifiable specific practical show-stoppers such as "system X would 
require Y million dollars to be reprogrammed, and you have our permission to 
identify it publicly".

I also would prefer to receive responses in ascii, as opposed to attachments.

Thank you,

Dr. Demetrios Matsakis

*************************************************************************



Dear Project Manager or Scientist,

It is being proposed to change the definition of Coordinated Universal
Time (UTC) regarding the insertion of leap-seconds, possibly even
eliminating their use.  The issue has been discussed in several 
timekeeping forums, and published in the Innovations Section of the 
November, 1999 issue of GPS World.  

Leap seconds are introduced so as to keep UTC synchronized (within 0.9 s) 
to the time scale determined from the Earth's rotation.  Should no new 
leap seconds be inserted, solar time will diverge from atomic time at 
the rate of about 2 seconds every 3 years, and after about a century 
|UT1-UTC| would exceed 1 minute.  Although no fundamental problems are 
anticipated, it is very likely that Y2K-like problems may result in 
software that assumes UT1=UTC, or |UT1-UTC|< some value, or whose 
input/output records use a field size that can only accommodate 
|UT1-UTC| values up to one second.
 
To gather information, an URSI Commission J Working Group was formed,
consisting of Don Backer, Wim. N. Brouw, Barry Clark, Irwin Shapiro,
Ir. E. Van Lil, and myself.
 
We would like to ask you to consult with the members of your institute
who currently deal with UT1-UTC, and give us a considered response to
the following two questions:
 
A. If the appropriate international bodies decide to eliminate the
insertion of new leap seconds, would you foresee any practical problems
for your institution/instrument/observations?
 
     no  ____

  *  yes ___
 
  *  possibly ____
 
     (* please explain any known or possible problems, but if possible 
        try to answer in ascii text instead of an attachment)
 
B. Would you be in favor of such a proposal?
 
     yes ____
 
     no  ____
 
     indifferent ___

     have better idea ___
 
     (feel free to comment)

C. Is there anyone else you would recommend we contact?
    (feel free to forward this email directly)
 
I would appreciate your assistance, and a response by January 15 to
dnm@orion.usno.navy.mil.

This questionnaire was first sent to the URSII national representatives,
a list of 931 astronomical institutions maintained by the American
Astronomical Society, and 125 prominent scientists.  It has since sent
sent to several mailing lists associated with Earth rotation.  I would 
like to apologize to anyone contacted twice, but also appreciate it if 
you would forward this email to anyone we may have missed.  We will
tabulate all responses, and are particularly interested in quantitative 
estimates from people whose systems can not easily accommodate the change.
Unix technology permitting, I will also email the report to all who have
responded.

Sincerely,
 
Demetrios Matsakis
________________________________________________________________________
Dr. Demetrios N. Matsakis            Director, Time Service Department
(202) 762-1587  DSN 762-1587         U. S. Naval Observatory
FAX (202) 762-1511                   3450 Massachusetts Avenue NW 
dnm@orion.usno.navy.mil              Washington DC, USA  20392-5420
________________________________________________________________________

**********************************************************************

Below is the "standard response" I have been giving to responders.  It
seems more appropriate to provide it in advance:


Thank you for your response, which will be tabulated.  Unix-technology
willing, we also plan to send a copy of our report all responders. 

Many people have asked me why there is a move to rethink the leap seconds,
with solutions such as (but not limited to) adding no new leap seconds.
I unfortunately edited out some of the reasons from early drafts of the 
questionnaire, because I was afraid that people would not read a long email.  
Since then, I have developed the following "standard reply":

1.)  Many high-tech navigation systems, can't handle leap seconds very well.  
GLONASS, the Russian equivalent to GPS, goes off-line for leap second 
adjustments.  Also, problems can occur in interfacing between systems that 
handle leap seconds differently.  There is also the practical problem of 
inserting a second every year and half - people often do it the wrong way.  
The response one person sent me is below, and it concerns Network Time 
Protocol (NTP), which uses the internet to transfer time.

> If leap seconds went away, the NTP community would worship the ground you
> walk on. Leap secs introduce a manual discontinuity in the NTP time scale.
> It takes a while to propagate leap secs through the hierarchy. Leap seconds 
> are a tremendous headache in the NTP world because they cannot be predicted. 
> One must set a flag to indicate that one is coming. I think it is a very
> true statement that all GPS users would vote against continuing leap seconds,
> not just NTP users. Many telecommunications circuits use GPS or atomic clocks
> to keep cellular phones in operation, and leap seconds are a nuisance to them
> as well. 

2.) I also received many comments about the effects on society when UT1
diverges.  Note that we are talking about a minute in the next century.  
Society routinely handles a one-hour switch with every daily savings time, 
and a half-hour offset if they live at the edge of a time zone.  By
the time leap seconds add up to an hour, the world will be very different.
If we have settled the solar system, a whole new scheme will probably
have evolved.  Even if we have not changed our system, society has 
enough slop in its timekeeping that people will slowly shift without even 
knowing it.  More people will start showing up to work at 9:00 AM, and less at 
8:30 AM, etc.

3) The "innovations" section in November's GPS World is on this subject,
and discusses other possibilities aside from "no new leap seconds".  These 
are inserting larger discontinuities less frequently, inserting integer
leap seconds at predefined times, simply using TAI, and redefining
the length of the second.

4) It should be pointed out that UT1-UTC is readily available on the web.
The USNO, as a subbureau of the International Rotation Service, makes
this information available via a weekly mailing and from a web page
at http://www.maia.usno.navy.mil, and other organizations also provide
this service.

5) My final comment is not to worry about any "surprise" decisions - before/if 
the international bodies all decide to do this, it will be fully debated and 
publicized.  My role, here, is simply to gather information.



From owner-ietf-outbound@ietf.org  Mon Jan 24 17:23:38 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27425
	for <ietf-web-archive@odin.ietf.org>; Mon, 24 Jan 2000 17:23:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA27879;
	Mon, 24 Jan 2000 17:21:56 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA27225
	for ietf-outbound.10@ietf.org; Mon, 24 Jan 2000 17:20:02 -0500 (EST)
Received: from orion.usno.navy.mil (dnm@orion.usno.navy.mil [192.5.41.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26937
	for <ietf@ietf.org>; Mon, 24 Jan 2000 17:15:28 -0500 (EST)
Received: (from dnm@localhost) by orion.usno.navy.mil (8.8.6 (PHNE_14041)/8.7.1) id WAA01086; Mon, 24 Jan 2000 22:15:21 GMT
From: Demetrios "N." Matsakis <dnm@orion.usno.navy.mil>
Message-Id: <200001242215.WAA01086@orion.usno.navy.mil>
Subject: Leap Second Questinnaire
To: ietf@ietf.org, sob@harvard.edu, fred@cisco.com
Date: Mon, 24 Jan 2000 22:15:21 +0000 (UTC)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Dear IETF member,

Several months ago, I sent out the following questionnaire concerning
the possibility that leap seconds might be discontinued (a discussion of
the reasons is provided at the end).  The original request asked for a response 
by January 15, but we are extending that so as to reach a larger 
constituency, such as the IETF.

I am anticipating that this will be distributed via an email exploder,
and would appreciate a response by anyone interested by February 15.

Although all responses will be tabulated, we are most interested in 
finding verifiable specific practical show-stoppers such as "system X would 
require Y million dollars to be reprogrammed, and you have our permission to 
identify it publicly".

I also would prefer to receive responses in ascii, as opposed to attachments.

Thank you,

Dr. Demetrios Matsakis

*************************************************************************



Dear Project Manager or Scientist,

It is being proposed to change the definition of Coordinated Universal
Time (UTC) regarding the insertion of leap-seconds, possibly even
eliminating their use.  The issue has been discussed in several 
timekeeping forums, and published in the Innovations Section of the 
November, 1999 issue of GPS World.  

Leap seconds are introduced so as to keep UTC synchronized (within 0.9 s) 
to the time scale determined from the Earth's rotation.  Should no new 
leap seconds be inserted, solar time will diverge from atomic time at 
the rate of about 2 seconds every 3 years, and after about a century 
|UT1-UTC| would exceed 1 minute.  Although no fundamental problems are 
anticipated, it is very likely that Y2K-like problems may result in 
software that assumes UT1=UTC, or |UT1-UTC|< some value, or whose 
input/output records use a field size that can only accommodate 
|UT1-UTC| values up to one second.
 
To gather information, an URSI Commission J Working Group was formed,
consisting of Don Backer, Wim. N. Brouw, Barry Clark, Irwin Shapiro,
Ir. E. Van Lil, and myself.
 
We would like to ask you to consult with the members of your institute
who currently deal with UT1-UTC, and give us a considered response to
the following two questions:
 
A. If the appropriate international bodies decide to eliminate the
insertion of new leap seconds, would you foresee any practical problems
for your institution/instrument/observations?
 
     no  ____

  *  yes ___
 
  *  possibly ____
 
     (* please explain any known or possible problems, but if possible 
        try to answer in ascii text instead of an attachment)
 
B. Would you be in favor of such a proposal?
 
     yes ____
 
     no  ____
 
     indifferent ___

     have better idea ___
 
     (feel free to comment)

C. Is there anyone else you would recommend we contact?
    (feel free to forward this email directly)
 
I would appreciate your assistance, and a response by January 15 to
dnm@orion.usno.navy.mil.

This questionnaire was first sent to the URSII national representatives,
a list of 931 astronomical institutions maintained by the American
Astronomical Society, and 125 prominent scientists.  It has since sent
sent to several mailing lists associated with Earth rotation.  I would 
like to apologize to anyone contacted twice, but also appreciate it if 
you would forward this email to anyone we may have missed.  We will
tabulate all responses, and are particularly interested in quantitative 
estimates from people whose systems can not easily accommodate the change.
Unix technology permitting, I will also email the report to all who have
responded.

Sincerely,
 
Demetrios Matsakis
________________________________________________________________________
Dr. Demetrios N. Matsakis            Director, Time Service Department
(202) 762-1587  DSN 762-1587         U. S. Naval Observatory
FAX (202) 762-1511                   3450 Massachusetts Avenue NW 
dnm@orion.usno.navy.mil              Washington DC, USA  20392-5420
________________________________________________________________________

**********************************************************************

Below is the "standard response" I have been giving to responders.  It
seems more appropriate to provide it in advance:


Thank you for your response, which will be tabulated.  Unix-technology
willing, we also plan to send a copy of our report all responders. 

Many people have asked me why there is a move to rethink the leap seconds,
with solutions such as (but not limited to) adding no new leap seconds.
I unfortunately edited out some of the reasons from early drafts of the 
questionnaire, because I was afraid that people would not read a long email.  
Since then, I have developed the following "standard reply":

1.)  Many high-tech navigation systems, can't handle leap seconds very well.  
GLONASS, the Russian equivalent to GPS, goes off-line for leap second 
adjustments.  Also, problems can occur in interfacing between systems that 
handle leap seconds differently.  There is also the practical problem of 
inserting a second every year and half - people often do it the wrong way.  
The response one person sent me is below, and it concerns Network Time 
Protocol (NTP), which uses the internet to transfer time.

> If leap seconds went away, the NTP community would worship the ground you
> walk on. Leap secs introduce a manual discontinuity in the NTP time scale.
> It takes a while to propagate leap secs through the hierarchy. Leap seconds 
> are a tremendous headache in the NTP world because they cannot be predicted. 
> One must set a flag to indicate that one is coming. I think it is a very
> true statement that all GPS users would vote against continuing leap seconds,
> not just NTP users. Many telecommunications circuits use GPS or atomic clocks
> to keep cellular phones in operation, and leap seconds are a nuisance to them
> as well. 

2.) I also received many comments about the effects on society when UT1
diverges.  Note that we are talking about a minute in the next century.  
Society routinely handles a one-hour switch with every daily savings time, 
and a half-hour offset if they live at the edge of a time zone.  By
the time leap seconds add up to an hour, the world will be very different.
If we have settled the solar system, a whole new scheme will probably
have evolved.  Even if we have not changed our system, society has 
enough slop in its timekeeping that people will slowly shift without even 
knowing it.  More people will start showing up to work at 9:00 AM, and less at 
8:30 AM, etc.

3) The "innovations" section in November's GPS World is on this subject,
and discusses other possibilities aside from "no new leap seconds".  These 
are inserting larger discontinuities less frequently, inserting integer
leap seconds at predefined times, simply using TAI, and redefining
the length of the second.

4) It should be pointed out that UT1-UTC is readily available on the web.
The USNO, as a subbureau of the International Rotation Service, makes
this information available via a weekly mailing and from a web page
at http://www.maia.usno.navy.mil, and other organizations also provide
this service.

5) My final comment is not to worry about any "surprise" decisions - before/if 
the international bodies all decide to do this, it will be fully debated and 
publicized.  My role, here, is simply to gather information.



From owner-ietf-outbound  Mon Jan 24 19:24:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA00655
	for ietf-outbound.10@ietf.org; Mon, 24 Jan 2000 19:24:04 -0500 (EST)
Received: from swan.prod.itd.earthlink.net (swan.prod.itd.earthlink.net [207.217.120.123])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00523
	for <ietf@ietf.org>; Mon, 24 Jan 2000 19:18:49 -0500 (EST)
Received: from [192.168.0.1] (ipa123.trenton2.nj.pub-ip.psi.net [38.26.139.123])
	by swan.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id QAA12498
	for <ietf@ietf.org>; Mon, 24 Jan 2000 16:17:03 -0800 (PST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <v04210101b4b299b39e9a@[192.168.0.1]>
Date: Mon, 24 Jan 2000 19:16:15 -0500
To: ietf@ietf.org
From: Gordon Cook <cook@cookreport.com>
Subject: IP Everywhere - state of the Internet 2000
 http://cookreport.com/ipeverywhere.shtml
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA00523
Content-Transfer-Encoding: 8bit

Published today, this is the introductory essay to:

IP Everywhere:  Riding the Internet Tsunami

The State of the Internet 2000

At the beginning of the new millennium the Internet is globally 
triumphant.  Blindly embraced by politicians who do not understand 
it, the Internet is touted as the engine that will power the economy 
of the new century.  The lover's embrace by the rich and powerful has 
helped to make it a fad which is increasingly in control of the stock 
market.  Internet companies are too often valued not out of sound 
understanding of their business models and cash flow dynamics but 
because they are Internet companies. The Internet has emerged in the 
1990s as perhaps the supreme "disruptive" technology in the sense 
popularized by Clayton Christensen in his 1997 book The Innovator's 
Dilemma.

Christensen found that "disruptive" technologies generally "under 
perform established products in mainstream markets," however they are 
generally cheaper and simpler to use than the sustaining technologies 
that they ultimately dethrone.  Examined from a slightly different 
perspective, "disruptive technologies give customers more than they 
currently need or are willing to pay for.  [Source is TeleGeography 
2000 . Review follows.] This is one reason why such technologies are 
usually commercialized first by customers serving niche markets such 
as data networks or CLECs."

Because "disruptive" technologies bring to market a such a radically 
different value proposition than was here-to-fore available, those 
practitioners of the older sustaining technologies find themselves 
unable to quickly adjust their business models and infrastructure to 
compete head-to-head with the new "disruptive" technologies.  They 
may also be constrained by the very service models which have made 
them essential to their customers.

To name just two examples central to the Internet's triumph as a 
disruptive network: in the last three years,  we have gone from the 
ancient sustaining wisdom that telecom networks must be intelligent 
at the center, to the new paradigm demanded by the Internet--that the 
intelligent devices at the edge of the network must find nothing in 
the middle that gets in the way of communication between them.  Also 
we have traveled from the certainty of knowledge that publishing is 
an activity whereby elite gate keepers package knowledge for the 
masses to a world where every computer owner can become a publisher. 
In this new "disruptive," Internet-driven world the old realities of 
our once comfortable industrial world are turned sideways if not 
inside out.  The trail that has been blazed by the new media and 
mirrored by the old media, is simply to hop on the bandwidth wagon, 
and hype processes that are not well understood yet. Jeff Bezos, the 
CEO of Amazon.com, a company that has yet to report a profit, becomes 
Time magazine's "Man of the Year."

This report will give an in depth look at reasons for the success of 
the disruptive Internet.   We have technology analysts, e-commerce 
analysts and legal experts bringing their respective expertise to 
bear as they tell their separate stories of who is winning and who is 
losing.  What we lack is a look at the larger picture of how the 
interaction of these areas will determine success and failure over 
the longer term.

This report will also examine in depth certain critical areas of 
technology change.  As it does so, it will show how the efforts of 
pre-Internet telecom entities to channel and shape the legal and 
political control of this technology no longer fit the competitive 
multiple protocol environment under which these entities must work. 
The processes developed to service the pre-Internet, circuit 
switched, telecommunications systems simply do not afford policy 
makers any way to deal fairly and harmoniously with Internet 
disruptions.  There are no longer appropriate pigeonholes and 
regulatory boxes that can sustain the old way of doing things. 
Democracy and technology no longer mix. If technology is to be 
consistent with public values, the public must understand the 
technology and be able to move from that understanding to a grasp of 
the stakes.

Understanding the stakes is difficult. Technology itself is 
increasingly complex. Point A does not always lead to Point B, even 
if Event C occurs. The impact of a new technology on is increasingly 
difficult to judge.  Consequently we are likely to find that many of 
the assumptions on the basis of which policy has been developed over 
decades are no longer valid.  For example this report will show that 
the buyer's market for bandwidth is filled the potential for 
financial peril as well as profit.  And it will show that the obscure 
debates over end-to-end network transparency can exert transformative 
influence over how the Internet is organized.

Ultimately, as the system grows sufficiently complex with fewer and 
fewer people competent or even able to direct its course, some may 
ask when does chaos set in and take control?  Or when does Internet 
coordination become merely a series  of panic stricken interventions 
where the "coordinators" lurch from one crises to the next while 
trying to keep all the "vested" interests in their same positions of 
dominance? Already technology that our political leaders do not 
understand is driving the formation of public policy.  Thus, 
democratic values independent of the technology are no longer the 
primary public policy goals. These are additional "disruptive" 
effects of the triumphant Internet.

Those who dare to assume the role of enterprise strategist in the 
midst of these changes must understand that their successful 
stewardship will depend on their grasp not only of what Gilder calls 
the ascendant technologies.  They must also develop at least two 
other skill sets.  One is an understanding that, as Lessig has shown 
so well, the success and visibility of the Internet has brought to it 
a level of attention where the legislators and the regulators will 
impact it whether the rest of us like it or not.  [For Lessig's Code: 
and Other Laws of Cyberspace  see 
http://cookreport.com/lessigbook.shtml ]

The other is a skill set that will help strategists to evaluate the 
stakes behind the questions of what will become the engineering 
agenda for the Internet.  Compromises have been made in network 
management that can spell  trouble further down the road. To scale 
network growth and cope with available IPv4 numbers, design decisions 
compromising end-to-end connectivity were made in the early 1990s. As 
the long IETF discussion published in the February 2000 COOK Report 
[and reprinted pp. 259-272 below] shows, there is a fallout from 
these decisions. The fallout is an incipient battle over how some of 
the intelligent edge devices of the network will communicate through 
the center to their intelligent counterparts at the opposite edges. 
The approaches taken now as to early implementation versus delay and 
revision of IPv6 will impact the diversity of the infrastructure of 
the future Internet. Arcane but very important debates like these 
will determine whether issues of control over end-to-end uniformity 
and network transparency take priority over everything else. Will 
time spent toward these ends mean that other more critical 
engineering concerns are ignored? A feared consequence is that the 
Internet's ability to continue to scale may be endangered.

Technology Changes

The year just ended saw a continuation of the bandwidth revolution 
begun by the real take off of WDM technologies in 1997. New 
developments in DWDM  (Dense Wave Division Multiplexing) and optical 
switching have further multiplied the bandwidth available from a 
global binge of fiber deployment. A revolutionary drop in the cost of 
data storage combined with increased network speeds is making it 
possible to deliver data across a wide area network more quickly and 
more cost effectively than across the bus on the motherboard of a 
single computer. These changes made the dream of the network becoming 
the computer - a dream that was first articulated earlier in the 
decade -seem likely to become true.  They also made possible the rise 
of a new application service provider industry.

The year also saw the full flowering of new global telecom providers 
built on the inexpensive infrastructure made possible by the new 
technology. Qwest, Level 3, Metromedia, Williams, Enron, Global 
Telesystems, Global Crossing, Next Link, Teleglobe, and Above Net to 
varying degrees are all examples of these new telecom giants. While 
Teleglobe has been around for a number of years in a rather different 
form, and Williams is a reincarnation of an earlier venture, all of 
these new players with the exception of Metromedia have been profiled 
within the pages of the COOK Report.  Questions of interconnection 
and peering are still critical.  Equinix's neutral Internet Business 
Exchanges to be built globally under contract with Bechtel will be 
the most high profile model for fitting the new backbone players 
together and enabling cost effective interconnection.

As bandwidth consumption and fiber deployment soar the purchase of 
bandwidth has become especially tricky.  Prices of bandwidth bought 
in bulk over long periods of time are plummeting and options of 
purchase are increasing.  (See Figure I  Fiber Optic Cost Trends and 
Figure X Bandwidth Market Matrix from TeleGeography 2000 on pages 2. 
and 161.)

It is a buyer's market but a dangerous one as AboveNet found out when 
14 months ago it paid over 8 million dollars for a 25 year IRU on a 
trans Atlantic STM-1 only to see the price of such an IRU plummet to 
less than 3 million a year later.  Options are available for those 
who make this kind of mistake.  MetroMedia Fiber Network (MMFN) 
bought AboveNet last year assuring it of a direct and affordable 
supply of bandwidth.  As David Isenberg pointed out in late December, 
according to MMFN's president, "a DS3 from the telco costs $3,000 a 
month, and a comparable MMFN fiber costs about $5,000. But the fiber 
can be lit at OC-12 - [a speed that is]14 times faster than DS3 - for 
$500 more per month (assuming 10-year depreciation). This works out 
to about $400 per DS3 per  month." The lesson is that as new 
companies are built on shifting assets and technology, agile fast 
moving players will find many options.  But, as the market 
solidifies, such options won't last indefinitely.

An important new business involving the sale of surplus bandwidth at 
exchanges is beginning to emerge.  We learned about RateXchange in a 
phone conversation with Ross Mayfield its CEO on December 30.  In New 
York and Los Angeles Mayfield is running what he calls The Real-Time 
Bandwidth eXchange.  He says that RTBX is a switch-based exchange 
that facilitates the entire transaction of bandwidth between 
interconnected carriers. Benefits include significantly lower 
transaction costs, anonymous trade, immediate delivery, and guarantee 
of payment. He seeks to create a win-win situation where an ISP with 
a temporary bandwidth surplus can sell bandwidth to an ISP with a 
shortage.  His ultimate goal is to commoditize trading in bandwidth 
by means of the sale of contracts for future delivery.

When Web based interfaces for creating in almost-real-time 
single-wavelength circuits between two points become common, 
Mayfield, and by then many other players, intend to have created the 
infrastructure to make this possible.  Given that the Internet for 
the past few years has been in a blind race to make enough bandwidth 
available to meet huge demands, this technology will be likely to 
give a welcome rationality to this marketplace.  For the first time 
it should offer a means of efficiently and quickly bringing available 
bandwidth into balance with demand, and thus allow venture 
entrepreneurs to build new infrastructure where it will be used 
profitably

As the February COOK Report's lead article on the state of wireless 
shows, we have many new developments in wireless reaching their 
maturity and pulling the whole structure towards more ubiquitous, 
always-on connectivity and applications.  Wireless, becoming digital 
in 1999, became also broadband.  Almost all the kinds, number and 
varieties of activities conducted via the wired Internet are now 
beginning to be carried out on the Internet in wireless form.  This 
vast growth of wireless infrastructure has fed on itself to lead to a 
continued explosion of net use and net traffic. Large growth in cable 
and DSL connectivity in 1999 also contributed to the increase in 
traffic and in the number of always-on connections.

In 1999 the Internet reached a critical mass where every player in 
commerce and business had to have a presence.  It became unthinkable 
not to have an Internet strategy.  The growth in Internet 
participation fed on itself and made possible business models which 
came to subsume every part of human economic activity. These changes 
mean that we are looking at a telecom world in which the old 
standards of evaluation fail us.

Technology Changes Divide Management into Irreconcilable Camps

The revolution has given us two opposed ways of thinking about and 
acting to achieve network organization.  One may be described as the 
Bellhead intelligent network and the other as the Nethead stupid net 
work. [See http://www.tmdenton.com/netheads3.htm and p.206 below.] In 
the first intelligence resides in expensive complex smart switches in 
the center of the telephone network linking stupid edge device 
telephones. In the second fat bit pipes linked by idiot savant 
routers connect intelligent computers on end user desks. The 
intelligent "Bellhead" network is generally organized to be run from 
the top down by an extremely rigid hierarchy.  The business model is 
a monopolist and feudal one with the lord of the manor ensconced in 
his hilltop castle.

The "Nethead" architecture is organized through the creation of 
structure by cooperating autonomous groups. In addition to being 
important mental constructs, both architectures are now grounded in 
billions of dollars of competing and not generally compatible 
infrastructures. These competing infrastructures are the foundations 
on which telecommunications, electronic  commerce and individual 
access to vast knowledge will be determined in the new century. The 
older infrastructure (the Bellhead) is inherently more subject to 
vertical integration and organization.  In the Bellhead environment, 
vertical, centralized, and rigidly-controlled hierarchies  are used 
to enable a single centrally determined and centrally priced palette 
of communication services, while the newer Nethead companies more 
often tend to be organized horizontally as companies whose market 
strength is in the delivery of one or more layers of the protocol 
stack.

This report proposes the outlines of a new business model structure 
for identifying and understanding Internet players who will prosper 
and ride the disruptive wave successfully. Growth areas in Nethead 
oriented companies are for specialists in bandwidth, interconnection, 
content hosting, application outsourcing, email.  A player here is 
either an infrastructure-providing specialist, or one who coordinates 
and manages technology specialties horizontally to provide services 
to end users. At the transport, infrastructure-providing, level you 
have the continued growth of new telecom greenfield players such as 
Level 3, Williams and GTS to name but three.  These companies are 
taking advantage of new technology and new market conditions to grow 
from nothing into billion dollar plus companies in only two or three 
years although the long term judgment of the market is not yet in as 
to their appropriate valuation.

Opposed to this new disruptive Internet business model is the old 
solid and stable vertically integrated telecom model followed in the 
United States by the ILECs. ATT, with its attempt to buy control of 
the cable industry to have a foundation from which to deliver all 
telecom services, fits into the same category.  MCI WorldCom with its 
attempt to become one of the biggest world wide integrated phone 
companies by acquiring Sprint also exhibits the telephone headed 
business strategy of a gigantic vertical integrator of dissimilar 
technologies and services.  By the same token the AOL Time Warner 
merger represents the old industrial age vertically integrated model 
of the marriage of content and a delivery mechanism for the content.

The Two Approaches to Slug it Out in 2000

We find that one battle of the year 2000 is to be between the 
horizontal versus vertically integrated business models. The 
horizontal model that is TCP/IP-based over gigabit or 10 gig Ethernet 
over fiber - a stupid network with smart peripheries where new low 
cost services can be cheaply and quickly inter connected like lego 
blocks. Internet players tend not to be vertically integrated. 
Instead they are bandwidth and transport players like Williams, 
Enron, Global Telesystems or end user aggregations of services like 
MindSpring, Earthlink, or AOL that run over someone else's 
infrastructure.

Disruptive Internet companies are nimble and quick compared to the 
older players like WorldCom that are still driven by empire building 
in search of elusive economies of scale. In a vertically integrated 
company, you may think you can cut costs by eliminating duplicative 
services, but instead you have a management nightmare of complex 
systems where glitches can mushroom into multiple week outages like 
MCI's frame relay collapse during the summer of 99.  Or ATT as it 
attempts to build what it sees as the "network of the future" out of 
CATV policy and infrastructure.  These players tend to see the 
Internet in terms of what has come before - in other words in terms 
of what is already familiar to them.  What has gone before is 
regional feudal monopolies, based on exclusive land-based rights and 
exclusive land-based responsibilities overseen by public regulators 
enforcing a social benefit/social cost analysis.  And it well may be 
that this model may be with us longer than we would like.  We should 
not think it can be so easily replaced, or that such replacement 
would have only good consequences.

Can the old vertically integrated intelligent network players 
compete? Or should they have some kind of protected quid-pro-quo 
status as the baseline common carrier? It will be much more difficult 
when wireless means cannibalization of their local loop T-1 circuit 
income rather than new income.  Look for them to engage in regulatory 
plays like ICANN.

The horizontally organized players can see the disruptions coming 
much more clearly, push the development envelope better, and achieve 
economies of scale by specializing in transport services, or storage 
services or application outsourcing. The vertical integration of MFS 
into the realm of its telephone company operators was what made the 
Network Access Points (NAPs) fail with WorldCom in the 1996 -1997 
period.  (Some maintain that with a carrier running the NAP, it was 
then put in the counter productive position of competing with its own 
customers.)

In contrast horizontal aggregation of services will enable Equinix's 
neutral exchange points.  Vertical integration is needed to make all 
the pieces of the intelligent bellhead network operate and to pay for 
relatively few and very expensive centralized switches.  To make 
vertical integration work, one needs to control as much of the 
telecom environment in which one operates as possible. Even so some 
astute observers point out that, as the Internet industry continues 
to grow, even the horizontally oriented Internet companies are likely 
to make vertical market plays if they are sufficiently cash wealthy 
and driven to expand market share. We must strive for educational 
processes that will make clear to regulators and the public alike 
what economic and policy consequences will flow from the two 
different approaches to the market.

Ignored Perils of Scalability and Architecture

The plug and play nature of Internet interoperability means that the 
over all network can be quite hierarchical, because there is room for 
many companies of many different sizes.  Consequently, the management 
of each company can be quite flat and and  be able to respond rapidly 
to changing conditions.   Internet interoperability encourages 
specialization and rapid technology development because the 
specialized pieces will fit together and work together.  However the 
Internet is now set to begin paying penalties for its success.  The 
triumph of IP in global telecom has made legacy companies believe it 
is critical to their futures to dominate the implementation of IPv6 
in order to preserve illusory and unattainable uniformity for their 
goal of continuing  in central control of network operations.

Let us summarize the argument we have just made. The Internet is 
having a disruptive impact in three areas of global importance. 
First, disruption in global commerce.  As trade of goods and services 
migrate to Internet locations, then individual economic power is 
derived from one's position within and one's subtle understanding of 
the new infrastructure.

Second, disruption in the restructuring of global telecommunication 
services to accommodate Internet requirements and efficiencies. As we 
have pointed out, the Internet is enabling new infrastructure that 
can provide all manner of telecommunication services at a tiny 
fraction of prior costs.

Third, disruption by the revolution of storage technology which 
re-enforces and amplifies the plummeting costs of bandwidth 
provision.  As a result, some computers will expand into 
configurations which look to them something like local intranets, 
with extended storage lodged on the Internet rather than inside the 
case, because in some situations, external Internet storage will be 
cheaper and safer than local storage  options.  This trend toward 
external Internet storage may shape the net into the global 
repository for information and knowledge. While the Internet was 
originally designed to be decentralized and not subject to single 
points of failure or control, its current commercial success makes 
today's Internet a target for desperate and daring stratagems to both 
obtain ownership wealth and the privileges and prerogatives of 
control, containment, restriction, and punishment.

Control Points:  Ephemeral or Real?

One view of how services in the new telecom world will be delivered 
is by an architecture of an idealized Internet where TCP /IP will 
always be able to be sent from end-to-end.  Because of a series of 
compromises involving private address numbers, corporations now sit 
behind firewalls that demand the imposition of many translation 
devices.  Thebellheads see these devices (NAT boxes) as obstacles to 
the imposition of a centrally controlled communication path like 
IPv6. The betheads don't see any of the bellhead's reasons for 
concern.  They are happy to use multiple protocols and bridges over 
otherwise non interoperable network links.  The nethead's outlook 
focuses on extensibility while the bellheads, through trying to 
influence the roll out of IPv6, focus on control.

ICANN which has garnered most of its support from bellheaded legacy 
organizations, has waged a generally successful campaign to sell 
itself to the press. The major press, having nothing other than 
ICANN's sound bytes from which to claim a clue, generally has no idea 
that anything is amiss. ICANN meanwhile is determined to error on the 
side of control concluding that it has the ability to enforce a 
uniform roll out for IPv6.

The two sides, one riding a disruptive technology and the other 
trying to extend the life span of the old sustaining technologies, 
sit in a hostile face off as they roll out competing business plans 
for the 'converged' future of voice and data.  But the Cook Report 
argues that the netheads and the bellheads are fighting about 
dominance and control issues, when there is emerging evidence that 
they must, instead, focus on scaling and inter operability issues. 
We are very sensitive to Sean Doran's concerns about scaling of 
network architecture and routing which will enable the Internet to 
cope with the coming onslaught of broadband soon to be generated by 
the increasing numbers of intelligent devices in homes and small 
businesses at the edge of the network. [See pages 150 - 152 below.] 
But in the current competitive environment this is very little talked 
about.

Therefore one must consider whether the Internet technical community 
while doing battle over the presumed uniformity necessary for IPv6 is 
actually depriving itself of the time and effort needed to face more 
intractable problems of scaling, including protocol diversity. Up to 
this point the Internet has scaled by a series of kludges like the 
use of CIDR and RFC 1597 assignment of numbers for private intranets. 
These are kludges that leave no one happy.  While the Internet is not 
likely to suddenly fall off a cliff, if these issues are not attended 
to, performance is likely to get uglier and less reliable.

Thus we predict that what is otherwise an arcane dispute among 
network engineers is likely to become a basis for an operational 
strategy attuned to the structure, economics, and philosophy of the 
vertically integrated telcos of the majority of the planet. These 
conflicting issues meet head on in the distribution of IPv6 and over 
ICANN which has placed itself in a position from which it could 
attempt to coordinate the implementation in an effort to provide the 
uniformity that the bellheads want and believe they need in order to 
stabilize their world.

We find that  a vertically integrated market strategy is usually 
telco operated and at odds with the horizontally oriented and more 
cooperative Internet market strategy.  However in the current chaotic 
period of expansion and emphasis on building market share, these 
categories do not always hold.  For the changes that we have 
chronicled in the COOK Report for the past eight years are focused on 
building market share as well as in the creation of new, successful 
businesses based on openings provided by the "disruptive" technology. 
When this happens, a business like 3Com may mature to a point where 
the MBAs looking at the balance sheets and stock prices begin to 
drive things more than the engineers.

As one astute observer confided to us: "vertical integration has 
become the way that everyone is trying to rule the Internet economy, 
and I have seen very specific presentations from 3 Com and others 
saying explicitly that this is what they are hoping to do.  It's the 
way to maximize shareholder value, but at the expense of an Internet 
that works well and that is user-friendly (by which I mean users that 
can innovate, not just click mouses). Similarly, I believe that we're 
past the nethead vs bellhead debate into something far scarier, which 
is where netheads and bellheads both realize that they're going to 
have to integrate their networks.  Moreover they may be committing to 
doing so even when they know that they don't have time to agree about 
big chunks of the end result.  In other words, while the PSTN may be 
getting dumber, intelligence is being injected into the Internet in 
some interesting and unexpected ways."

Under such conditions amazingly powerful technology will almost 
certainly run into snaffus originating with kludges in protocol 
design and IP numbering made in the first years of the take off of 
the commercial Internet.  When this happens more than web site 
performance will suffer. Also the profits of those companies which 
have marched forward fueled by nothing but blind faith in the 
continuing scalability and robustness of the Internet will take 
severe hits.

Alternatives?

So are there alternatives? Ed Gerck who has participated in some of 
these debates has some wise suggestions in a long IETF discussion 
reprinted  in the February 2000 COOK Report. Gerck advocates that the 
battle should not be thought of as either the uniform roll out of 
IPv6 or the failure of IPv6 and thus being fated to live with a 
network with some hosts blocked by firewalls or NAT boxes.   There is 
a third way marked by diverse protocols that can inter operate.

When we asked him for further comment he replied "I saw no 
counter-argument raised to it - rather, it fell like an eye-opener to 
the reality that Nature is based on diversity. Those that believe in 
an uniform Internet as the only way to achieve end-to-end security 
are actually still locked in the network paradigm of the 70's where 
network administration dictated orders to the entire network, by 
design. So, they will most naturally fight a multiple-protocol 
Internet, because they cannot intellectually cope with it."

"However, in the Internet paradigm of the 90's, now truly as networks 
of private networks in a progression over 30 years as catalogued by 
Stef,  [Einar Stefferud]we already have multiple protocols in 
coexistence at various levels - what matters, so we have learned, is 
not that there must be one unique protocol at every place and time, 
but that different protocols, at different places, at different 
times, and doing different things are indeed able to work together 
when the objectives are the same. And this, quite revealingly for the 
success of the Internet IMO, is how we humans prefer to work 
together, how commerce thrives and how we can enrich each other's 
living experience."

"So, communication protocols such as IPv6 must not be based on an 
excluding model, where they must kill any other protocol, but on an 
including model where interfaces are provided for backward and 
forward compatibility. Otherwise, even if IPv6 would be adopted by 
force on 90% of the Internet - this would still leave out 10% (which 
is projected at 40 million end-users in 2000) and would immediately 
raise questions about IPv7, IPv8 and so on. The only way to address 
the backward- and forward-looking questions without requiring the 
whole world to change standards at whatever cost at whatever time, is 
to provide for inter operation."

"Thus, that is why I wrote that tools for IPv4/IPv6 inter operation 
will be needed .... and valued, including NATs as a fundamental 
building block - even though they began as a stumbling block in 
another context," Gerck concluded.

Consequently, one must weigh whether the Internet technical community 
may be actually depriving itself of the time and effort needed to 
face more intractable problems of scaling, including protocol 
diversity.  Those who would pretend to do large scale strategic 
planning in the midst of the Internet revolution had better 
assimilate the lessons of Larry Lessig's Code and Other Laws of 
Cyberspace.   As the Internet moves into the legal and political 
arena the question for analysts to ponder is not a naïve belief in 
the unregulatability of the Internet.  They need a much clearer 
understanding that  the operation and impact of the Internet can be 
determined by the legal system, by the way in which its dominant 
protocols are coded, by the architectural environment in which it 
operates and by the local customs that determine what behavior is 
socially and commercially ethical and acceptable.

Gerck's statement about the need for inter operability tools for IPv4 
and IPv6 is a good summary of why Lessig's seemingly arcane issue of 
network architecture and control is politically very important.  For 
in Lessig's language, it offers yet another example of how the 
technical decisions that change the shape of Internet architecture 
will indeed render it more subject to legal and regulatory control.

The "disruptive" Internet is in the midst of what looks to be a 
general triumph.    During our eight years of reporting on the growth 
of the commercial Internet, the COOK Report has developed a unique 
perspective that synthesizes technology issues with their operational 
and engineering counterparts. We believe that synthesis of these 
intricate processes as described in detail in IP Everywhere, falls 
outside the scope of more specialized analysts. We also believe that 
those who become familiar with these complex  developments will be 
able to formulate more successful business strategies.  For the first 
time the technology is likely to be as much affected by policy 
decisions of network design and global regulation as by the older 
unregulated Internet frontier mentality which drove the mad rush to 
add users, scale the network, and increase market share.  Winning 
players must take into account the daily onslaught of new technology. 
They must also make the right judgments about the governance and 
standards wars, and the rapid shift in market economics. The winners 
will be those who get the  right answers to this complex mix of 
questions.

Gordon Cook January 24, 2000

****************************************************************
The COOK Report on Internet      Index to 8 years of the COOK  Report
431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
(609) 882-2572 (phone & fax)              IP Everywhere: Riding the
cook@cookreport.com                     Internet Tsunami - 392 pages
just published. See  http://cookreport.com/ipeverywhere.shtml
****************************************************************



From owner-ietf-outbound@ietf.org  Mon Jan 24 19:26:00 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00733
	for <ietf-web-archive@odin.ietf.org>; Mon, 24 Jan 2000 19:25:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA02066;
	Mon, 24 Jan 2000 19:24:16 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA00655
	for ietf-outbound.10@ietf.org; Mon, 24 Jan 2000 19:24:04 -0500 (EST)
Received: from swan.prod.itd.earthlink.net (swan.prod.itd.earthlink.net [207.217.120.123])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00523
	for <ietf@ietf.org>; Mon, 24 Jan 2000 19:18:49 -0500 (EST)
Received: from [192.168.0.1] (ipa123.trenton2.nj.pub-ip.psi.net [38.26.139.123])
	by swan.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id QAA12498
	for <ietf@ietf.org>; Mon, 24 Jan 2000 16:17:03 -0800 (PST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <v04210101b4b299b39e9a@[192.168.0.1]>
Date: Mon, 24 Jan 2000 19:16:15 -0500
To: ietf@ietf.org
From: Gordon Cook <cook@cookreport.com>
Subject: IP Everywhere - state of the Internet 2000
 http://cookreport.com/ipeverywhere.shtml
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA00523
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Published today, this is the introductory essay to:

IP Everywhere:  Riding the Internet Tsunami

The State of the Internet 2000

At the beginning of the new millennium the Internet is globally 
triumphant.  Blindly embraced by politicians who do not understand 
it, the Internet is touted as the engine that will power the economy 
of the new century.  The lover's embrace by the rich and powerful has 
helped to make it a fad which is increasingly in control of the stock 
market.  Internet companies are too often valued not out of sound 
understanding of their business models and cash flow dynamics but 
because they are Internet companies. The Internet has emerged in the 
1990s as perhaps the supreme "disruptive" technology in the sense 
popularized by Clayton Christensen in his 1997 book The Innovator's 
Dilemma.

Christensen found that "disruptive" technologies generally "under 
perform established products in mainstream markets," however they are 
generally cheaper and simpler to use than the sustaining technologies 
that they ultimately dethrone.  Examined from a slightly different 
perspective, "disruptive technologies give customers more than they 
currently need or are willing to pay for.  [Source is TeleGeography 
2000 . Review follows.] This is one reason why such technologies are 
usually commercialized first by customers serving niche markets such 
as data networks or CLECs."

Because "disruptive" technologies bring to market a such a radically 
different value proposition than was here-to-fore available, those 
practitioners of the older sustaining technologies find themselves 
unable to quickly adjust their business models and infrastructure to 
compete head-to-head with the new "disruptive" technologies.  They 
may also be constrained by the very service models which have made 
them essential to their customers.

To name just two examples central to the Internet's triumph as a 
disruptive network: in the last three years,  we have gone from the 
ancient sustaining wisdom that telecom networks must be intelligent 
at the center, to the new paradigm demanded by the Internet--that the 
intelligent devices at the edge of the network must find nothing in 
the middle that gets in the way of communication between them.  Also 
we have traveled from the certainty of knowledge that publishing is 
an activity whereby elite gate keepers package knowledge for the 
masses to a world where every computer owner can become a publisher. 
In this new "disruptive," Internet-driven world the old realities of 
our once comfortable industrial world are turned sideways if not 
inside out.  The trail that has been blazed by the new media and 
mirrored by the old media, is simply to hop on the bandwidth wagon, 
and hype processes that are not well understood yet. Jeff Bezos, the 
CEO of Amazon.com, a company that has yet to report a profit, becomes 
Time magazine's "Man of the Year."

This report will give an in depth look at reasons for the success of 
the disruptive Internet.   We have technology analysts, e-commerce 
analysts and legal experts bringing their respective expertise to 
bear as they tell their separate stories of who is winning and who is 
losing.  What we lack is a look at the larger picture of how the 
interaction of these areas will determine success and failure over 
the longer term.

This report will also examine in depth certain critical areas of 
technology change.  As it does so, it will show how the efforts of 
pre-Internet telecom entities to channel and shape the legal and 
political control of this technology no longer fit the competitive 
multiple protocol environment under which these entities must work. 
The processes developed to service the pre-Internet, circuit 
switched, telecommunications systems simply do not afford policy 
makers any way to deal fairly and harmoniously with Internet 
disruptions.  There are no longer appropriate pigeonholes and 
regulatory boxes that can sustain the old way of doing things. 
Democracy and technology no longer mix. If technology is to be 
consistent with public values, the public must understand the 
technology and be able to move from that understanding to a grasp of 
the stakes.

Understanding the stakes is difficult. Technology itself is 
increasingly complex. Point A does not always lead to Point B, even 
if Event C occurs. The impact of a new technology on is increasingly 
difficult to judge.  Consequently we are likely to find that many of 
the assumptions on the basis of which policy has been developed over 
decades are no longer valid.  For example this report will show that 
the buyer's market for bandwidth is filled the potential for 
financial peril as well as profit.  And it will show that the obscure 
debates over end-to-end network transparency can exert transformative 
influence over how the Internet is organized.

Ultimately, as the system grows sufficiently complex with fewer and 
fewer people competent or even able to direct its course, some may 
ask when does chaos set in and take control?  Or when does Internet 
coordination become merely a series  of panic stricken interventions 
where the "coordinators" lurch from one crises to the next while 
trying to keep all the "vested" interests in their same positions of 
dominance? Already technology that our political leaders do not 
understand is driving the formation of public policy.  Thus, 
democratic values independent of the technology are no longer the 
primary public policy goals. These are additional "disruptive" 
effects of the triumphant Internet.

Those who dare to assume the role of enterprise strategist in the 
midst of these changes must understand that their successful 
stewardship will depend on their grasp not only of what Gilder calls 
the ascendant technologies.  They must also develop at least two 
other skill sets.  One is an understanding that, as Lessig has shown 
so well, the success and visibility of the Internet has brought to it 
a level of attention where the legislators and the regulators will 
impact it whether the rest of us like it or not.  [For Lessig's Code: 
and Other Laws of Cyberspace  see 
http://cookreport.com/lessigbook.shtml ]

The other is a skill set that will help strategists to evaluate the 
stakes behind the questions of what will become the engineering 
agenda for the Internet.  Compromises have been made in network 
management that can spell  trouble further down the road. To scale 
network growth and cope with available IPv4 numbers, design decisions 
compromising end-to-end connectivity were made in the early 1990s. As 
the long IETF discussion published in the February 2000 COOK Report 
[and reprinted pp. 259-272 below] shows, there is a fallout from 
these decisions. The fallout is an incipient battle over how some of 
the intelligent edge devices of the network will communicate through 
the center to their intelligent counterparts at the opposite edges. 
The approaches taken now as to early implementation versus delay and 
revision of IPv6 will impact the diversity of the infrastructure of 
the future Internet. Arcane but very important debates like these 
will determine whether issues of control over end-to-end uniformity 
and network transparency take priority over everything else. Will 
time spent toward these ends mean that other more critical 
engineering concerns are ignored? A feared consequence is that the 
Internet's ability to continue to scale may be endangered.

Technology Changes

The year just ended saw a continuation of the bandwidth revolution 
begun by the real take off of WDM technologies in 1997. New 
developments in DWDM  (Dense Wave Division Multiplexing) and optical 
switching have further multiplied the bandwidth available from a 
global binge of fiber deployment. A revolutionary drop in the cost of 
data storage combined with increased network speeds is making it 
possible to deliver data across a wide area network more quickly and 
more cost effectively than across the bus on the motherboard of a 
single computer. These changes made the dream of the network becoming 
the computer - a dream that was first articulated earlier in the 
decade -seem likely to become true.  They also made possible the rise 
of a new application service provider industry.

The year also saw the full flowering of new global telecom providers 
built on the inexpensive infrastructure made possible by the new 
technology. Qwest, Level 3, Metromedia, Williams, Enron, Global 
Telesystems, Global Crossing, Next Link, Teleglobe, and Above Net to 
varying degrees are all examples of these new telecom giants. While 
Teleglobe has been around for a number of years in a rather different 
form, and Williams is a reincarnation of an earlier venture, all of 
these new players with the exception of Metromedia have been profiled 
within the pages of the COOK Report.  Questions of interconnection 
and peering are still critical.  Equinix's neutral Internet Business 
Exchanges to be built globally under contract with Bechtel will be 
the most high profile model for fitting the new backbone players 
together and enabling cost effective interconnection.

As bandwidth consumption and fiber deployment soar the purchase of 
bandwidth has become especially tricky.  Prices of bandwidth bought 
in bulk over long periods of time are plummeting and options of 
purchase are increasing.  (See Figure I  Fiber Optic Cost Trends and 
Figure X Bandwidth Market Matrix from TeleGeography 2000 on pages 2. 
and 161.)

It is a buyer's market but a dangerous one as AboveNet found out when 
14 months ago it paid over 8 million dollars for a 25 year IRU on a 
trans Atlantic STM-1 only to see the price of such an IRU plummet to 
less than 3 million a year later.  Options are available for those 
who make this kind of mistake.  MetroMedia Fiber Network (MMFN) 
bought AboveNet last year assuring it of a direct and affordable 
supply of bandwidth.  As David Isenberg pointed out in late December, 
according to MMFN's president, "a DS3 from the telco costs $3,000 a 
month, and a comparable MMFN fiber costs about $5,000. But the fiber 
can be lit at OC-12 - [a speed that is]14 times faster than DS3 - for 
$500 more per month (assuming 10-year depreciation). This works out 
to about $400 per DS3 per  month." The lesson is that as new 
companies are built on shifting assets and technology, agile fast 
moving players will find many options.  But, as the market 
solidifies, such options won't last indefinitely.

An important new business involving the sale of surplus bandwidth at 
exchanges is beginning to emerge.  We learned about RateXchange in a 
phone conversation with Ross Mayfield its CEO on December 30.  In New 
York and Los Angeles Mayfield is running what he calls The Real-Time 
Bandwidth eXchange.  He says that RTBX is a switch-based exchange 
that facilitates the entire transaction of bandwidth between 
interconnected carriers. Benefits include significantly lower 
transaction costs, anonymous trade, immediate delivery, and guarantee 
of payment. He seeks to create a win-win situation where an ISP with 
a temporary bandwidth surplus can sell bandwidth to an ISP with a 
shortage.  His ultimate goal is to commoditize trading in bandwidth 
by means of the sale of contracts for future delivery.

When Web based interfaces for creating in almost-real-time 
single-wavelength circuits between two points become common, 
Mayfield, and by then many other players, intend to have created the 
infrastructure to make this possible.  Given that the Internet for 
the past few years has been in a blind race to make enough bandwidth 
available to meet huge demands, this technology will be likely to 
give a welcome rationality to this marketplace.  For the first time 
it should offer a means of efficiently and quickly bringing available 
bandwidth into balance with demand, and thus allow venture 
entrepreneurs to build new infrastructure where it will be used 
profitably

As the February COOK Report's lead article on the state of wireless 
shows, we have many new developments in wireless reaching their 
maturity and pulling the whole structure towards more ubiquitous, 
always-on connectivity and applications.  Wireless, becoming digital 
in 1999, became also broadband.  Almost all the kinds, number and 
varieties of activities conducted via the wired Internet are now 
beginning to be carried out on the Internet in wireless form.  This 
vast growth of wireless infrastructure has fed on itself to lead to a 
continued explosion of net use and net traffic. Large growth in cable 
and DSL connectivity in 1999 also contributed to the increase in 
traffic and in the number of always-on connections.

In 1999 the Internet reached a critical mass where every player in 
commerce and business had to have a presence.  It became unthinkable 
not to have an Internet strategy.  The growth in Internet 
participation fed on itself and made possible business models which 
came to subsume every part of human economic activity. These changes 
mean that we are looking at a telecom world in which the old 
standards of evaluation fail us.

Technology Changes Divide Management into Irreconcilable Camps

The revolution has given us two opposed ways of thinking about and 
acting to achieve network organization.  One may be described as the 
Bellhead intelligent network and the other as the Nethead stupid net 
work. [See http://www.tmdenton.com/netheads3.htm and p.206 below.] In 
the first intelligence resides in expensive complex smart switches in 
the center of the telephone network linking stupid edge device 
telephones. In the second fat bit pipes linked by idiot savant 
routers connect intelligent computers on end user desks. The 
intelligent "Bellhead" network is generally organized to be run from 
the top down by an extremely rigid hierarchy.  The business model is 
a monopolist and feudal one with the lord of the manor ensconced in 
his hilltop castle.

The "Nethead" architecture is organized through the creation of 
structure by cooperating autonomous groups. In addition to being 
important mental constructs, both architectures are now grounded in 
billions of dollars of competing and not generally compatible 
infrastructures. These competing infrastructures are the foundations 
on which telecommunications, electronic  commerce and individual 
access to vast knowledge will be determined in the new century. The 
older infrastructure (the Bellhead) is inherently more subject to 
vertical integration and organization.  In the Bellhead environment, 
vertical, centralized, and rigidly-controlled hierarchies  are used 
to enable a single centrally determined and centrally priced palette 
of communication services, while the newer Nethead companies more 
often tend to be organized horizontally as companies whose market 
strength is in the delivery of one or more layers of the protocol 
stack.

This report proposes the outlines of a new business model structure 
for identifying and understanding Internet players who will prosper 
and ride the disruptive wave successfully. Growth areas in Nethead 
oriented companies are for specialists in bandwidth, interconnection, 
content hosting, application outsourcing, email.  A player here is 
either an infrastructure-providing specialist, or one who coordinates 
and manages technology specialties horizontally to provide services 
to end users. At the transport, infrastructure-providing, level you 
have the continued growth of new telecom greenfield players such as 
Level 3, Williams and GTS to name but three.  These companies are 
taking advantage of new technology and new market conditions to grow 
from nothing into billion dollar plus companies in only two or three 
years although the long term judgment of the market is not yet in as 
to their appropriate valuation.

Opposed to this new disruptive Internet business model is the old 
solid and stable vertically integrated telecom model followed in the 
United States by the ILECs. ATT, with its attempt to buy control of 
the cable industry to have a foundation from which to deliver all 
telecom services, fits into the same category.  MCI WorldCom with its 
attempt to become one of the biggest world wide integrated phone 
companies by acquiring Sprint also exhibits the telephone headed 
business strategy of a gigantic vertical integrator of dissimilar 
technologies and services.  By the same token the AOL Time Warner 
merger represents the old industrial age vertically integrated model 
of the marriage of content and a delivery mechanism for the content.

The Two Approaches to Slug it Out in 2000

We find that one battle of the year 2000 is to be between the 
horizontal versus vertically integrated business models. The 
horizontal model that is TCP/IP-based over gigabit or 10 gig Ethernet 
over fiber - a stupid network with smart peripheries where new low 
cost services can be cheaply and quickly inter connected like lego 
blocks. Internet players tend not to be vertically integrated. 
Instead they are bandwidth and transport players like Williams, 
Enron, Global Telesystems or end user aggregations of services like 
MindSpring, Earthlink, or AOL that run over someone else's 
infrastructure.

Disruptive Internet companies are nimble and quick compared to the 
older players like WorldCom that are still driven by empire building 
in search of elusive economies of scale. In a vertically integrated 
company, you may think you can cut costs by eliminating duplicative 
services, but instead you have a management nightmare of complex 
systems where glitches can mushroom into multiple week outages like 
MCI's frame relay collapse during the summer of 99.  Or ATT as it 
attempts to build what it sees as the "network of the future" out of 
CATV policy and infrastructure.  These players tend to see the 
Internet in terms of what has come before - in other words in terms 
of what is already familiar to them.  What has gone before is 
regional feudal monopolies, based on exclusive land-based rights and 
exclusive land-based responsibilities overseen by public regulators 
enforcing a social benefit/social cost analysis.  And it well may be 
that this model may be with us longer than we would like.  We should 
not think it can be so easily replaced, or that such replacement 
would have only good consequences.

Can the old vertically integrated intelligent network players 
compete? Or should they have some kind of protected quid-pro-quo 
status as the baseline common carrier? It will be much more difficult 
when wireless means cannibalization of their local loop T-1 circuit 
income rather than new income.  Look for them to engage in regulatory 
plays like ICANN.

The horizontally organized players can see the disruptions coming 
much more clearly, push the development envelope better, and achieve 
economies of scale by specializing in transport services, or storage 
services or application outsourcing. The vertical integration of MFS 
into the realm of its telephone company operators was what made the 
Network Access Points (NAPs) fail with WorldCom in the 1996 -1997 
period.  (Some maintain that with a carrier running the NAP, it was 
then put in the counter productive position of competing with its own 
customers.)

In contrast horizontal aggregation of services will enable Equinix's 
neutral exchange points.  Vertical integration is needed to make all 
the pieces of the intelligent bellhead network operate and to pay for 
relatively few and very expensive centralized switches.  To make 
vertical integration work, one needs to control as much of the 
telecom environment in which one operates as possible. Even so some 
astute observers point out that, as the Internet industry continues 
to grow, even the horizontally oriented Internet companies are likely 
to make vertical market plays if they are sufficiently cash wealthy 
and driven to expand market share. We must strive for educational 
processes that will make clear to regulators and the public alike 
what economic and policy consequences will flow from the two 
different approaches to the market.

Ignored Perils of Scalability and Architecture

The plug and play nature of Internet interoperability means that the 
over all network can be quite hierarchical, because there is room for 
many companies of many different sizes.  Consequently, the management 
of each company can be quite flat and and  be able to respond rapidly 
to changing conditions.   Internet interoperability encourages 
specialization and rapid technology development because the 
specialized pieces will fit together and work together.  However the 
Internet is now set to begin paying penalties for its success.  The 
triumph of IP in global telecom has made legacy companies believe it 
is critical to their futures to dominate the implementation of IPv6 
in order to preserve illusory and unattainable uniformity for their 
goal of continuing  in central control of network operations.

Let us summarize the argument we have just made. The Internet is 
having a disruptive impact in three areas of global importance. 
First, disruption in global commerce.  As trade of goods and services 
migrate to Internet locations, then individual economic power is 
derived from one's position within and one's subtle understanding of 
the new infrastructure.

Second, disruption in the restructuring of global telecommunication 
services to accommodate Internet requirements and efficiencies. As we 
have pointed out, the Internet is enabling new infrastructure that 
can provide all manner of telecommunication services at a tiny 
fraction of prior costs.

Third, disruption by the revolution of storage technology which 
re-enforces and amplifies the plummeting costs of bandwidth 
provision.  As a result, some computers will expand into 
configurations which look to them something like local intranets, 
with extended storage lodged on the Internet rather than inside the 
case, because in some situations, external Internet storage will be 
cheaper and safer than local storage  options.  This trend toward 
external Internet storage may shape the net into the global 
repository for information and knowledge. While the Internet was 
originally designed to be decentralized and not subject to single 
points of failure or control, its current commercial success makes 
today's Internet a target for desperate and daring stratagems to both 
obtain ownership wealth and the privileges and prerogatives of 
control, containment, restriction, and punishment.

Control Points:  Ephemeral or Real?

One view of how services in the new telecom world will be delivered 
is by an architecture of an idealized Internet where TCP /IP will 
always be able to be sent from end-to-end.  Because of a series of 
compromises involving private address numbers, corporations now sit 
behind firewalls that demand the imposition of many translation 
devices.  Thebellheads see these devices (NAT boxes) as obstacles to 
the imposition of a centrally controlled communication path like 
IPv6. The betheads don't see any of the bellhead's reasons for 
concern.  They are happy to use multiple protocols and bridges over 
otherwise non interoperable network links.  The nethead's outlook 
focuses on extensibility while the bellheads, through trying to 
influence the roll out of IPv6, focus on control.

ICANN which has garnered most of its support from bellheaded legacy 
organizations, has waged a generally successful campaign to sell 
itself to the press. The major press, having nothing other than 
ICANN's sound bytes from which to claim a clue, generally has no idea 
that anything is amiss. ICANN meanwhile is determined to error on the 
side of control concluding that it has the ability to enforce a 
uniform roll out for IPv6.

The two sides, one riding a disruptive technology and the other 
trying to extend the life span of the old sustaining technologies, 
sit in a hostile face off as they roll out competing business plans 
for the 'converged' future of voice and data.  But the Cook Report 
argues that the netheads and the bellheads are fighting about 
dominance and control issues, when there is emerging evidence that 
they must, instead, focus on scaling and inter operability issues. 
We are very sensitive to Sean Doran's concerns about scaling of 
network architecture and routing which will enable the Internet to 
cope with the coming onslaught of broadband soon to be generated by 
the increasing numbers of intelligent devices in homes and small 
businesses at the edge of the network. [See pages 150 - 152 below.] 
But in the current competitive environment this is very little talked 
about.

Therefore one must consider whether the Internet technical community 
while doing battle over the presumed uniformity necessary for IPv6 is 
actually depriving itself of the time and effort needed to face more 
intractable problems of scaling, including protocol diversity. Up to 
this point the Internet has scaled by a series of kludges like the 
use of CIDR and RFC 1597 assignment of numbers for private intranets. 
These are kludges that leave no one happy.  While the Internet is not 
likely to suddenly fall off a cliff, if these issues are not attended 
to, performance is likely to get uglier and less reliable.

Thus we predict that what is otherwise an arcane dispute among 
network engineers is likely to become a basis for an operational 
strategy attuned to the structure, economics, and philosophy of the 
vertically integrated telcos of the majority of the planet. These 
conflicting issues meet head on in the distribution of IPv6 and over 
ICANN which has placed itself in a position from which it could 
attempt to coordinate the implementation in an effort to provide the 
uniformity that the bellheads want and believe they need in order to 
stabilize their world.

We find that  a vertically integrated market strategy is usually 
telco operated and at odds with the horizontally oriented and more 
cooperative Internet market strategy.  However in the current chaotic 
period of expansion and emphasis on building market share, these 
categories do not always hold.  For the changes that we have 
chronicled in the COOK Report for the past eight years are focused on 
building market share as well as in the creation of new, successful 
businesses based on openings provided by the "disruptive" technology. 
When this happens, a business like 3Com may mature to a point where 
the MBAs looking at the balance sheets and stock prices begin to 
drive things more than the engineers.

As one astute observer confided to us: "vertical integration has 
become the way that everyone is trying to rule the Internet economy, 
and I have seen very specific presentations from 3 Com and others 
saying explicitly that this is what they are hoping to do.  It's the 
way to maximize shareholder value, but at the expense of an Internet 
that works well and that is user-friendly (by which I mean users that 
can innovate, not just click mouses). Similarly, I believe that we're 
past the nethead vs bellhead debate into something far scarier, which 
is where netheads and bellheads both realize that they're going to 
have to integrate their networks.  Moreover they may be committing to 
doing so even when they know that they don't have time to agree about 
big chunks of the end result.  In other words, while the PSTN may be 
getting dumber, intelligence is being injected into the Internet in 
some interesting and unexpected ways."

Under such conditions amazingly powerful technology will almost 
certainly run into snaffus originating with kludges in protocol 
design and IP numbering made in the first years of the take off of 
the commercial Internet.  When this happens more than web site 
performance will suffer. Also the profits of those companies which 
have marched forward fueled by nothing but blind faith in the 
continuing scalability and robustness of the Internet will take 
severe hits.

Alternatives?

So are there alternatives? Ed Gerck who has participated in some of 
these debates has some wise suggestions in a long IETF discussion 
reprinted  in the February 2000 COOK Report. Gerck advocates that the 
battle should not be thought of as either the uniform roll out of 
IPv6 or the failure of IPv6 and thus being fated to live with a 
network with some hosts blocked by firewalls or NAT boxes.   There is 
a third way marked by diverse protocols that can inter operate.

When we asked him for further comment he replied "I saw no 
counter-argument raised to it - rather, it fell like an eye-opener to 
the reality that Nature is based on diversity. Those that believe in 
an uniform Internet as the only way to achieve end-to-end security 
are actually still locked in the network paradigm of the 70's where 
network administration dictated orders to the entire network, by 
design. So, they will most naturally fight a multiple-protocol 
Internet, because they cannot intellectually cope with it."

"However, in the Internet paradigm of the 90's, now truly as networks 
of private networks in a progression over 30 years as catalogued by 
Stef,  [Einar Stefferud]we already have multiple protocols in 
coexistence at various levels - what matters, so we have learned, is 
not that there must be one unique protocol at every place and time, 
but that different protocols, at different places, at different 
times, and doing different things are indeed able to work together 
when the objectives are the same. And this, quite revealingly for the 
success of the Internet IMO, is how we humans prefer to work 
together, how commerce thrives and how we can enrich each other's 
living experience."

"So, communication protocols such as IPv6 must not be based on an 
excluding model, where they must kill any other protocol, but on an 
including model where interfaces are provided for backward and 
forward compatibility. Otherwise, even if IPv6 would be adopted by 
force on 90% of the Internet - this would still leave out 10% (which 
is projected at 40 million end-users in 2000) and would immediately 
raise questions about IPv7, IPv8 and so on. The only way to address 
the backward- and forward-looking questions without requiring the 
whole world to change standards at whatever cost at whatever time, is 
to provide for inter operation."

"Thus, that is why I wrote that tools for IPv4/IPv6 inter operation 
will be needed .... and valued, including NATs as a fundamental 
building block - even though they began as a stumbling block in 
another context," Gerck concluded.

Consequently, one must weigh whether the Internet technical community 
may be actually depriving itself of the time and effort needed to 
face more intractable problems of scaling, including protocol 
diversity.  Those who would pretend to do large scale strategic 
planning in the midst of the Internet revolution had better 
assimilate the lessons of Larry Lessig's Code and Other Laws of 
Cyberspace.   As the Internet moves into the legal and political 
arena the question for analysts to ponder is not a naïve belief in 
the unregulatability of the Internet.  They need a much clearer 
understanding that  the operation and impact of the Internet can be 
determined by the legal system, by the way in which its dominant 
protocols are coded, by the architectural environment in which it 
operates and by the local customs that determine what behavior is 
socially and commercially ethical and acceptable.

Gerck's statement about the need for inter operability tools for IPv4 
and IPv6 is a good summary of why Lessig's seemingly arcane issue of 
network architecture and control is politically very important.  For 
in Lessig's language, it offers yet another example of how the 
technical decisions that change the shape of Internet architecture 
will indeed render it more subject to legal and regulatory control.

The "disruptive" Internet is in the midst of what looks to be a 
general triumph.    During our eight years of reporting on the growth 
of the commercial Internet, the COOK Report has developed a unique 
perspective that synthesizes technology issues with their operational 
and engineering counterparts. We believe that synthesis of these 
intricate processes as described in detail in IP Everywhere, falls 
outside the scope of more specialized analysts. We also believe that 
those who become familiar with these complex  developments will be 
able to formulate more successful business strategies.  For the first 
time the technology is likely to be as much affected by policy 
decisions of network design and global regulation as by the older 
unregulated Internet frontier mentality which drove the mad rush to 
add users, scale the network, and increase market share.  Winning 
players must take into account the daily onslaught of new technology. 
They must also make the right judgments about the governance and 
standards wars, and the rapid shift in market economics. The winners 
will be those who get the  right answers to this complex mix of 
questions.

Gordon Cook January 24, 2000

****************************************************************
The COOK Report on Internet      Index to 8 years of the COOK  Report
431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
(609) 882-2572 (phone & fax)              IP Everywhere: Riding the
cook@cookreport.com                     Internet Tsunami - 392 pages
just published. See  http://cookreport.com/ipeverywhere.shtml
****************************************************************



From owner-ietf-outbound  Tue Jan 25 19:12:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA10571
	for ietf-outbound.10@ietf.org; Tue, 25 Jan 2000 19:10:04 -0500 (EST)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10494
	for <ietf@ietf.org>; Tue, 25 Jan 2000 19:06:22 -0500 (EST)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id TAA01793;
	Tue, 25 Jan 2000 19:01:15 -0500
Date: Tue, 25 Jan 2000 19:01:15 -0500
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200001260001.TAA01793@ginger.lcs.mit.edu>
To: cook@cookreport.com, ietf@ietf.org
Subject: Re:  IP Everywhere - state of the Internet 2000 http://cookreport.com/ipeverywhere.shtml
Cc: jnc@ginger.lcs.mit.edu

    > From: Gordon Cook <cook@cookreport.com>

    > two opposed ways of thinking about and acting to achieve network
    > organization.  One may be described as the Bellhead intelligent network
    > and the other as the Nethead stupid network ...
    > bellheads see these devices (NAT boxes) as obstacles to the imposition
    > of a centrally controlled communication path .. The [n]etheads don't see
    > any of the bellhead's reasons for concern.  They are happy to use
    > multiple protocols and bridges over otherwise non interoperable network
    > links.  The nethead's outlook focuses on extensibility while the
    > bellheads .. focus on control.
    > ICANN which has garnered most of its support from bellheaded legacy
    > organizations, has waged a generally successful campaign to sell itself
    > to the press.

Gordon, while there is some truth to your generalizations about two different
schools of network design, I have a couple of problems with this material.

First and foremost, the terminology for your two groups is loaded and
simplistic. I've worked with a number of 'classic voice' people who were very
intelligent and open-minded, and from who I learned a great deal. On the other
hand, I've known more than a few datagram people who were not very incisive
thinkers. Me, I've always liked the old quote (from "Poor Richard's Almanac",
IIRC, but I'm not positive):

	"There are two kinds of fool: one says 'this is old, and therefore
	good'; and the other says 'this is new, and therefore better'."

This quotation also points out that simplistic analyses are often faulty,
which leads me into my second point... A number of the areas you touch on
above are a lot more complex than your analysis paints them. For one, the
administration of the DNS is a massive problem, and many (most?) of the
parties opposing various aspects of the current arrangement aren't exactly
pure of heart. For another, a lot of the new grass-roots technologies you laud
(e.g. NAT) have major dark sides (which is not to say that some of the
alternatives are superior...)


Finally, these comments should not be taken as an overall condemnation of
this column, which contains much useful material.

	Noel



From owner-ietf-outbound@ietf.org  Tue Jan 25 19:18:07 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10710
	for <ietf-web-archive@odin.ietf.org>; Tue, 25 Jan 2000 19:18:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA23609;
	Tue, 25 Jan 2000 19:16:20 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA10571
	for ietf-outbound.10@ietf.org; Tue, 25 Jan 2000 19:10:04 -0500 (EST)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10494
	for <ietf@ietf.org>; Tue, 25 Jan 2000 19:06:22 -0500 (EST)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id TAA01793;
	Tue, 25 Jan 2000 19:01:15 -0500
Date: Tue, 25 Jan 2000 19:01:15 -0500
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200001260001.TAA01793@ginger.lcs.mit.edu>
To: cook@cookreport.com, ietf@ietf.org
Subject: Re:  IP Everywhere - state of the Internet 2000 http://cookreport.com/ipeverywhere.shtml
Cc: jnc@ginger.lcs.mit.edu

    > From: Gordon Cook <cook@cookreport.com>

    > two opposed ways of thinking about and acting to achieve network
    > organization.  One may be described as the Bellhead intelligent network
    > and the other as the Nethead stupid network ...
    > bellheads see these devices (NAT boxes) as obstacles to the imposition
    > of a centrally controlled communication path .. The [n]etheads don't see
    > any of the bellhead's reasons for concern.  They are happy to use
    > multiple protocols and bridges over otherwise non interoperable network
    > links.  The nethead's outlook focuses on extensibility while the
    > bellheads .. focus on control.
    > ICANN which has garnered most of its support from bellheaded legacy
    > organizations, has waged a generally successful campaign to sell itself
    > to the press.

Gordon, while there is some truth to your generalizations about two different
schools of network design, I have a couple of problems with this material.

First and foremost, the terminology for your two groups is loaded and
simplistic. I've worked with a number of 'classic voice' people who were very
intelligent and open-minded, and from who I learned a great deal. On the other
hand, I've known more than a few datagram people who were not very incisive
thinkers. Me, I've always liked the old quote (from "Poor Richard's Almanac",
IIRC, but I'm not positive):

	"There are two kinds of fool: one says 'this is old, and therefore
	good'; and the other says 'this is new, and therefore better'."

This quotation also points out that simplistic analyses are often faulty,
which leads me into my second point... A number of the areas you touch on
above are a lot more complex than your analysis paints them. For one, the
administration of the DNS is a massive problem, and many (most?) of the
parties opposing various aspects of the current arrangement aren't exactly
pure of heart. For another, a lot of the new grass-roots technologies you laud
(e.g. NAT) have major dark sides (which is not to say that some of the
alternatives are superior...)


Finally, these comments should not be taken as an overall condemnation of
this column, which contains much useful material.

	Noel



From owner-ietf-outbound  Wed Jan 26 07:22:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA01522
	for ietf-outbound.10@ietf.org; Wed, 26 Jan 2000 07:20:02 -0500 (EST)
Received: from mailer.primekom.de (ns1.primekom.net [62.208.43.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA01394
	for <ietf@ietf.org>; Wed, 26 Jan 2000 07:13:50 -0500 (EST)
Received: (qmail 10288 invoked from network); 26 Jan 2000 12:13:02 -0000
Received: from unknown (HELO WinProxy.anywhere) (194.59.180.235)
  by ns1.primekom.net with SMTP; 26 Jan 2000 12:13:02 -0000
Received: from 10.1.1.67 by 10.1.0.18 (WinProxy); Wed, 26 Jan 2000 13:11:55 +0100
Received: by localhost with Microsoft MAPI; Wed, 26 Jan 2000 13:12:03 +0100
Message-ID: <B17708F34D53D011872F00A0C91DA01CF29ABC@MHMAMXS1>
From: Juergen Weimer <juergen.weimer@mhm.de>
Reply-To: "juergen.weimer@mhm.de" <juergen.weimer@mhm.de>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Date: Wed, 26 Jan 2000 13:12:03 +0100
Return-Receipt-To: Juergen Weimer <juergen.weimer@mhm.de>
Organization: Michael Huber Muenchen GmbH
X-Mailer: Microsoft Internet E-Mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

auth 248cab88 subscribe ietf juergen.weimer@mhm.de





From owner-ietf-outbound@ietf.org  Wed Jan 26 07:24:53 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01837
	for <ietf-web-archive@odin.ietf.org>; Wed, 26 Jan 2000 07:24:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA27264;
	Wed, 26 Jan 2000 07:23:11 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id HAA01522
	for ietf-outbound.10@ietf.org; Wed, 26 Jan 2000 07:20:02 -0500 (EST)
Received: from mailer.primekom.de (ns1.primekom.net [62.208.43.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA01394
	for <ietf@ietf.org>; Wed, 26 Jan 2000 07:13:50 -0500 (EST)
Received: (qmail 10288 invoked from network); 26 Jan 2000 12:13:02 -0000
Received: from unknown (HELO WinProxy.anywhere) (194.59.180.235)
  by ns1.primekom.net with SMTP; 26 Jan 2000 12:13:02 -0000
Received: from 10.1.1.67 by 10.1.0.18 (WinProxy); Wed, 26 Jan 2000 13:11:55 +0100
Received: by localhost with Microsoft MAPI; Wed, 26 Jan 2000 13:12:03 +0100
Message-ID: <B17708F34D53D011872F00A0C91DA01CF29ABC@MHMAMXS1>
From: Juergen Weimer <juergen.weimer@mhm.de>
Reply-To: "juergen.weimer@mhm.de" <juergen.weimer@mhm.de>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Date: Wed, 26 Jan 2000 13:12:03 +0100
Return-Receipt-To: Juergen Weimer <juergen.weimer@mhm.de>
Organization: Michael Huber Muenchen GmbH
X-Mailer: Microsoft Internet E-Mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

auth 248cab88 subscribe ietf juergen.weimer@mhm.de





From owner-ietf-outbound  Wed Jan 26 08:21:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA03512
	for ietf-outbound.10@ietf.org; Wed, 26 Jan 2000 08:20:02 -0500 (EST)
Received: from flipper.cisco.com (flipper.cisco.com [171.69.63.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02888;
	Wed, 26 Jan 2000 07:58:37 -0500 (EST)
Received: from p7020-img-nt (ssh.cisco.com [171.69.10.34]) by flipper.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with SMTP id EAA01334; Wed, 26 Jan 2000 04:58:37 -0800 (PST)
Message-Id: <4.1.20000126094126.03df3990@flipper.cisco.com>
Message-Id: <4.1.20000126094126.03df3990@flipper.cisco.com>
X-Sender: fred@localhost (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 26 Jan 2000 09:43:01 +0100
To: avri.doria@nokia.com
From: Fred Baker <fred@cisco.com>
Subject: Re: Announcement of new IESG members
Cc: ietf@ietf.org, nomcom@ietf.org
In-Reply-To: <200001242247.RAA28183@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Thank you very much for your hard work, and that of your committee, in this
years nomination process. You have chosen a slate of which I heartily
approve, and welcome.

At 05:47 PM 1/24/00 -0500, avri.doria@nokia.com wrote:
>
>After much review and deliberation, the following individuals
>have been selected as Area Directors and members of the IESG.
>This slate was chosen by the voting members of the NomCom and
>has been approved by the IAB.
>
>-------------------------------------------------------------
>
>Applications Area:
>Ned Freed is nominated for a 2 year term.
>
>Internet Area:
>Erik Nordmark was selected for an additional 2 year term.
>
>Operations and Management Area:
>Bert Wijnen was selected for an additional 2 year term.  
>
>Routing Area:
>Rob Coltun was selected for an additional 2 year term.
>
>Security Area:
>Marcus Leech was selected for an additional 2 year term.
>
>Transport Area:
>Allison Mankin was selected for a 2 year term.
>
>User Services Area:
>April Marine was selected for an additional 2 year term.
>
>-------------------------------------------------------------
>
>I want to thank all of the folks who were willing to be 
>nominated and were willing to go through the selection process. 
>I also would like thank all those with whom the NomCom 
>consulted in making its selections.  
>
>Note: the announcement of IAB members will be made in several 
>weeks.
>
>
>Chair, NomCom
>
>a.
>-----------------------------------
>avri doria
>Office: +1 781 993 4656
>Mobile: +1 781 308 7680                
>
>



From owner-ietf-outbound@ietf.org  Wed Jan 26 08:23:38 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03658
	for <ietf-web-archive@odin.ietf.org>; Wed, 26 Jan 2000 08:23:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28757;
	Wed, 26 Jan 2000 08:21:54 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA03512
	for ietf-outbound.10@ietf.org; Wed, 26 Jan 2000 08:20:02 -0500 (EST)
Received: from flipper.cisco.com (flipper.cisco.com [171.69.63.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02888;
	Wed, 26 Jan 2000 07:58:37 -0500 (EST)
Received: from p7020-img-nt (ssh.cisco.com [171.69.10.34]) by flipper.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with SMTP id EAA01334; Wed, 26 Jan 2000 04:58:37 -0800 (PST)
Message-Id: <4.1.20000126094126.03df3990@flipper.cisco.com>
Message-Id: <4.1.20000126094126.03df3990@flipper.cisco.com>
X-Sender: fred@localhost (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 26 Jan 2000 09:43:01 +0100
To: avri.doria@nokia.com
From: Fred Baker <fred@cisco.com>
Subject: Re: Announcement of new IESG members
Cc: ietf@ietf.org, nomcom@ietf.org
In-Reply-To: <200001242247.RAA28183@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Thank you very much for your hard work, and that of your committee, in this
years nomination process. You have chosen a slate of which I heartily
approve, and welcome.

At 05:47 PM 1/24/00 -0500, avri.doria@nokia.com wrote:
>
>After much review and deliberation, the following individuals
>have been selected as Area Directors and members of the IESG.
>This slate was chosen by the voting members of the NomCom and
>has been approved by the IAB.
>
>-------------------------------------------------------------
>
>Applications Area:
>Ned Freed is nominated for a 2 year term.
>
>Internet Area:
>Erik Nordmark was selected for an additional 2 year term.
>
>Operations and Management Area:
>Bert Wijnen was selected for an additional 2 year term.  
>
>Routing Area:
>Rob Coltun was selected for an additional 2 year term.
>
>Security Area:
>Marcus Leech was selected for an additional 2 year term.
>
>Transport Area:
>Allison Mankin was selected for a 2 year term.
>
>User Services Area:
>April Marine was selected for an additional 2 year term.
>
>-------------------------------------------------------------
>
>I want to thank all of the folks who were willing to be 
>nominated and were willing to go through the selection process. 
>I also would like thank all those with whom the NomCom 
>consulted in making its selections.  
>
>Note: the announcement of IAB members will be made in several 
>weeks.
>
>
>Chair, NomCom
>
>a.
>-----------------------------------
>avri doria
>Office: +1 781 993 4656
>Mobile: +1 781 308 7680                
>
>



From owner-ietf-outbound  Wed Jan 26 19:47:56 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA13857
	for ietf-outbound.10@ietf.org; Wed, 26 Jan 2000 19:46:16 -0500 (EST)
Received: from web1806.mail.yahoo.com (web1806.mail.yahoo.com [128.11.23.49])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA13793
	for <IETF@ietf.org>; Wed, 26 Jan 2000 19:35:19 -0500 (EST)
Received: (qmail 228 invoked by uid 60001); 26 Jan 2000 23:54:01 -0000
Message-ID: <20000126235401.227.qmail@web1806.mail.yahoo.com>
Received: from [216.185.31.139] by web1806.mail.yahoo.com; Wed, 26 Jan 2000 15:54:01 PST
Date: Wed, 26 Jan 2000 15:54:01 -0800 (PST)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: Does APPLE want to be #1 in OPTICS?  Here's how....
To: marcu@apple.com
Cc: IETF@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-783368690-948930841=:29186"

--0-783368690-948930841=:29186
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline



Note: forwarded message attached.


=====
Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

 This Letter and All Contents Copyright 1999 Casey Farrell
              All Rights Reserved
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--0-783368690-948930841=:29186
Content-Type: message/rfc822

X-Apparently-To: oh_yeah_dot_net@yahoo.com via web1803.mail.yahoo.com
X-Track2: 2
X-Track: -50
Received: from law2-f165.hotmail.com (HELO hotmail.com) (216.32.181.165)
  by mta214.mail.yahoo.com with SMTP; 26 Jan 2000 23:44:03 -0000
Received: (qmail 85010 invoked by uid 0); 26 Jan 2000 23:44:01 -0000
Message-ID: <20000126234401.85009.qmail@hotmail.com>
Received: from 216.185.31.139 by www.hotmail.com with HTTP;	Wed, 26 Jan 2000 15:44:01 PST
X-Originating-IP: [216.185.31.139]
From: "Casey Farrell" <california_star@hotmail.com>
To: timj@spie.org
Cc: kerstinb@spie.org
Subject: Re: NEWS RELEASE: Electronic Imaging Conference
Date: Wed, 26 Jan 2000 15:44:01 PST
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Content-Length: 7351

Attn: Kerstin Bailey; Director of Marketing
c/o   Society of Optical Engineeers

  Dear Kerstin,

   It was fun yakking with you just now-here is a re-spin of the idea,
my computer is giving me some trouble today so I hope this arrives w/o
looping or being chopped! Forward here: The designwork is one of many
which I own, that have specialization characteristics for the FORMAT
and STORAGE of Information through colorization 'templates.' Although
the designwork and proposed use shown here is for what appears as a
recreational or 'fun' use; ones very like this are especially mapped out to 
be multi-purposeful and could perhaps compose the 'embedded'
area of the new technologies we are currently looking at as 'wearable'
or even 'smart-card' etc.

  Pleasehave Tim give me a call when he's back from the conference.

Thanks-

    Casey



Casey Farrell; Designer                             Wednesday
San Francisco, California                        Jan. 27, 2000

Dear Ms. Sweeney,

  Thanks for your attention in bringing this matter to the attention of Mr. 
Sabean. My proposal is like frosting on a cake for the GIANTS!
Please excuse the reuse of the form here my computer stuck right after
we spoke this morning; & the FAX phone apparently has a major 'glitch'
so this is about the only way I'm able to get the info out today!

  Thank you-

RE: A 'Decimalized'( 'Digital') GIANTS Logo @ PAC BELL PARK ...4Y2K?

Attn: Karen Sweeney; Chief Executive Assistant
For:  Brian Sabean; Promotions Director
c/o   China Basin Baseball Group
       6603 3rd Street
        San Francisco, California


               Dear Mr. Sabean,

     Hope I have this to your attention in time for the premiere
of the new Pac Bell Baseball Park at China Basin. The idea is for a
simple designwork to inaugurate a sports arena in the "WIRELESS AGE!"

Please see:
       http://www.slip.net/~o614275

  With a plethora of hand-held computing devices available to the
average person, the NUMBER-PAD and KEYBOARD layouts are more a feature
of the ordinary work day than ever imagined before! The idea behind an
'optical -illusion' "LOGO" composed of numerals in place of letters, is 
based the premise that there has been an almost imperceptible new
turn at the level of ADVERTISING, and as most of the ADVERTISERS will
of course be 'TECK-STOCK' and 'START-UP' and such-if the GIANTS'FANS
are themselves looking at the figures...?

  Sunday Jan. 16, 2000's Examiner Sports FrontPage on which you were
featured-had my announcement on PAGE CL52, 710 Business Opportunities
of the same date in SF Sunday Examiner & Chronicle Classified Ads: and
the complimentary ONLINE VERSION w/ HOTLINK URL had this messaging:

                 http://www.slip.net/~o614275
                Designwork for Sale! $1,500,00
                Great Sports Promotion Situation
                available for the Wireless Age!

I am offering to the GIANTS for sale my designwork titled: 614275
which will serve as another splendid example of San Francisco style
memorabilia; fitting in nicely with the MUNI symbol, Ruth Azawa's
fountain at Union Square, Ghiradelli, North Beach, Ferry Boats, Wine,
French Bread, Santana's music, KQED, etc. The whole enchilada!

  Thank you for the consideration,

  Casey Farrell

tel: (425) 664-2489

  This Letter and All Contents Copyright 2000 Casey Farrell

               All Rights Reserved


>From: Tim Johnson <timj@spie.org>
>To: campbell@ior.com, lstein@paweekly.com, davidb@techweek.com, 
>california_star@hotmail.com, Matt_Hicks@zd.com, 
>justin.mullins@lexis-nexis.com, dclaymon@sjmercury.com, hbrody@mit.edu, 
>drotman@mit.edu
>Subject: NEWS RELEASE: Electronic Imaging Conference
>Date: Wed, 19 Jan 2000 14:38:04 -0800
>
>NEWS RELEASE:
>
>Electronic Imaging 2000 Showcases Digital Color Publishing
>
>"Will our company logo be the right color with sRGB or do I need ICC
>profiles?  Will my hardcopy look better with blue-noise or with
>stochastic halftoning?"
>
>Next week, the Symposium on Electronic Imaging, January 23-28 in San
>Jose will provide the answers.  Short courses on document imaging will
>cover a range of topics including elementary color science, image
>quality factors in color reproduction, and optical document security.
>
>"Over the years the conference on Color Imaging: Device Independent
>Color, Color Hardcopy, and Graphic Arts has become the world's most
>prestigious conference on this subject and is a cornerstone of the
>Symposium. Electronic Imaging 2000 will have a day and a half of short
>courses on Color Imaging Sunday and Monday followed by four days of
>papers Tuesday through Friday.  The presenters include the best
>specialists from all over the world," said Rich Ellson of Xerox Palo
>Alto Research Center, a member of the EI Symposium Organizing Committee.
>
>The Symposium on Electronic Imaging is cosponsored by the IS&T--the
>Society for Imaging Science and Technology, and SPIE--The International
>Society for Optical Engineering.  Since its inception in 1989,
>Electronic Imaging has been based in the Bay Area.  After starting out
>in Santa Clara, the two societies moved the conference to the San Jose
>Convention Center in 1991 where it has continued to both grow in size
>and evolve in subject matter.  This year a total of 962 papers will be
>presented in 24 conferences, and the organizers expect 1500 technical
>attendees.
>
>"Understanding the emerging interests of Silicon Valley
>imaging professionals has helped make this symposium a very rapid means
>of communicating important new ideas, training people in new imaging
>disciplines, and building a community for moving technologies further"
>says EI 2000 Symposium Chair Giordano Beretta of Hewlett-Packard in Palo
>Alto.
>
>"In the past year we have seen a revolution in document imaging, moving
>beyond electronic publishing, where electronic imaging was used
>separately in each stage of the workflow.  Today we talk of digital
>publishing, an integrated process that is fully digital from end to
>end.  At any time, a color piece can be repurposed for an arbitrary
>output medium without quality loss or manual intervention.  In addition,
>spectral color imaging and advanced color management techniques open a
>whole new world to system builders" explains Gabriel Marcu of Apple
>Computer in Cupertino, one of the Conference Chairs.
>
>Other areas covered by the symposium and of interest to the color
>imaging community are capture and display, human vision, document
>recognition, optical security and anti-counterfeiting, and Internet
>imaging.
>
>Electronic Imaging 2000 will be held a the San Jose Convention Center
>from January 23-28, 2000.  Complete course and instructor descriptions
>as well as registration information can be found on-line at
>http://www.spie.org/info/ei/courses.
>
>For more information on EI 2000
>http://www.spie.org/web/meetings/programs/pw00/ei00.html
>=============================================================
>
>MEDIA: Present yourselves at the SPIE Registration desk
>for complimentary admission.
>
>---
>
>Tim Johnson, Public Information Office
>SPIE--The International Society for Optical Engineering
>VOX: 360.676.3290, EXT 574 * FAX: 360.647.1445 * E-MAIL: timj@spie.org

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


--0-783368690-948930841=:29186--



From owner-ietf-outbound@ietf.org  Wed Jan 26 19:51:07 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13912
	for <ietf-web-archive@odin.ietf.org>; Wed, 26 Jan 2000 19:51:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA19163;
	Wed, 26 Jan 2000 19:49:21 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA13857
	for ietf-outbound.10@ietf.org; Wed, 26 Jan 2000 19:46:16 -0500 (EST)
Received: from web1806.mail.yahoo.com (web1806.mail.yahoo.com [128.11.23.49])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA13793
	for <IETF@ietf.org>; Wed, 26 Jan 2000 19:35:19 -0500 (EST)
Received: (qmail 228 invoked by uid 60001); 26 Jan 2000 23:54:01 -0000
Message-ID: <20000126235401.227.qmail@web1806.mail.yahoo.com>
Received: from [216.185.31.139] by web1806.mail.yahoo.com; Wed, 26 Jan 2000 15:54:01 PST
Date: Wed, 26 Jan 2000 15:54:01 -0800 (PST)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: Does APPLE want to be #1 in OPTICS?  Here's how....
To: marcu@apple.com
Cc: IETF@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-783368690-948930841=:29186"

--0-783368690-948930841=:29186
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline



Note: forwarded message attached.


=====
Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

 This Letter and All Contents Copyright 1999 Casey Farrell
              All Rights Reserved
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--0-783368690-948930841=:29186
Content-Type: message/rfc822

X-Apparently-To: oh_yeah_dot_net@yahoo.com via web1803.mail.yahoo.com
X-Track2: 2
X-Track: -50
Received: from law2-f165.hotmail.com (HELO hotmail.com) (216.32.181.165)
  by mta214.mail.yahoo.com with SMTP; 26 Jan 2000 23:44:03 -0000
Received: (qmail 85010 invoked by uid 0); 26 Jan 2000 23:44:01 -0000
Message-ID: <20000126234401.85009.qmail@hotmail.com>
Received: from 216.185.31.139 by www.hotmail.com with HTTP;	Wed, 26 Jan 2000 15:44:01 PST
X-Originating-IP: [216.185.31.139]
From: "Casey Farrell" <california_star@hotmail.com>
To: timj@spie.org
Cc: kerstinb@spie.org
Subject: Re: NEWS RELEASE: Electronic Imaging Conference
Date: Wed, 26 Jan 2000 15:44:01 PST
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Content-Length: 7351

Attn: Kerstin Bailey; Director of Marketing
c/o   Society of Optical Engineeers

  Dear Kerstin,

   It was fun yakking with you just now-here is a re-spin of the idea,
my computer is giving me some trouble today so I hope this arrives w/o
looping or being chopped! Forward here: The designwork is one of many
which I own, that have specialization characteristics for the FORMAT
and STORAGE of Information through colorization 'templates.' Although
the designwork and proposed use shown here is for what appears as a
recreational or 'fun' use; ones very like this are especially mapped out to 
be multi-purposeful and could perhaps compose the 'embedded'
area of the new technologies we are currently looking at as 'wearable'
or even 'smart-card' etc.

  Pleasehave Tim give me a call when he's back from the conference.

Thanks-

    Casey



Casey Farrell; Designer                             Wednesday
San Francisco, California                        Jan. 27, 2000

Dear Ms. Sweeney,

  Thanks for your attention in bringing this matter to the attention of Mr. 
Sabean. My proposal is like frosting on a cake for the GIANTS!
Please excuse the reuse of the form here my computer stuck right after
we spoke this morning; & the FAX phone apparently has a major 'glitch'
so this is about the only way I'm able to get the info out today!

  Thank you-

RE: A 'Decimalized'( 'Digital') GIANTS Logo @ PAC BELL PARK ...4Y2K?

Attn: Karen Sweeney; Chief Executive Assistant
For:  Brian Sabean; Promotions Director
c/o   China Basin Baseball Group
       6603 3rd Street
        San Francisco, California


               Dear Mr. Sabean,

     Hope I have this to your attention in time for the premiere
of the new Pac Bell Baseball Park at China Basin. The idea is for a
simple designwork to inaugurate a sports arena in the "WIRELESS AGE!"

Please see:
       http://www.slip.net/~o614275

  With a plethora of hand-held computing devices available to the
average person, the NUMBER-PAD and KEYBOARD layouts are more a feature
of the ordinary work day than ever imagined before! The idea behind an
'optical -illusion' "LOGO" composed of numerals in place of letters, is 
based the premise that there has been an almost imperceptible new
turn at the level of ADVERTISING, and as most of the ADVERTISERS will
of course be 'TECK-STOCK' and 'START-UP' and such-if the GIANTS'FANS
are themselves looking at the figures...?

  Sunday Jan. 16, 2000's Examiner Sports FrontPage on which you were
featured-had my announcement on PAGE CL52, 710 Business Opportunities
of the same date in SF Sunday Examiner & Chronicle Classified Ads: and
the complimentary ONLINE VERSION w/ HOTLINK URL had this messaging:

                 http://www.slip.net/~o614275
                Designwork for Sale! $1,500,00
                Great Sports Promotion Situation
                available for the Wireless Age!

I am offering to the GIANTS for sale my designwork titled: 614275
which will serve as another splendid example of San Francisco style
memorabilia; fitting in nicely with the MUNI symbol, Ruth Azawa's
fountain at Union Square, Ghiradelli, North Beach, Ferry Boats, Wine,
French Bread, Santana's music, KQED, etc. The whole enchilada!

  Thank you for the consideration,

  Casey Farrell

tel: (425) 664-2489

  This Letter and All Contents Copyright 2000 Casey Farrell

               All Rights Reserved


>From: Tim Johnson <timj@spie.org>
>To: campbell@ior.com, lstein@paweekly.com, davidb@techweek.com, 
>california_star@hotmail.com, Matt_Hicks@zd.com, 
>justin.mullins@lexis-nexis.com, dclaymon@sjmercury.com, hbrody@mit.edu, 
>drotman@mit.edu
>Subject: NEWS RELEASE: Electronic Imaging Conference
>Date: Wed, 19 Jan 2000 14:38:04 -0800
>
>NEWS RELEASE:
>
>Electronic Imaging 2000 Showcases Digital Color Publishing
>
>"Will our company logo be the right color with sRGB or do I need ICC
>profiles?  Will my hardcopy look better with blue-noise or with
>stochastic halftoning?"
>
>Next week, the Symposium on Electronic Imaging, January 23-28 in San
>Jose will provide the answers.  Short courses on document imaging will
>cover a range of topics including elementary color science, image
>quality factors in color reproduction, and optical document security.
>
>"Over the years the conference on Color Imaging: Device Independent
>Color, Color Hardcopy, and Graphic Arts has become the world's most
>prestigious conference on this subject and is a cornerstone of the
>Symposium. Electronic Imaging 2000 will have a day and a half of short
>courses on Color Imaging Sunday and Monday followed by four days of
>papers Tuesday through Friday.  The presenters include the best
>specialists from all over the world," said Rich Ellson of Xerox Palo
>Alto Research Center, a member of the EI Symposium Organizing Committee.
>
>The Symposium on Electronic Imaging is cosponsored by the IS&T--the
>Society for Imaging Science and Technology, and SPIE--The International
>Society for Optical Engineering.  Since its inception in 1989,
>Electronic Imaging has been based in the Bay Area.  After starting out
>in Santa Clara, the two societies moved the conference to the San Jose
>Convention Center in 1991 where it has continued to both grow in size
>and evolve in subject matter.  This year a total of 962 papers will be
>presented in 24 conferences, and the organizers expect 1500 technical
>attendees.
>
>"Understanding the emerging interests of Silicon Valley
>imaging professionals has helped make this symposium a very rapid means
>of communicating important new ideas, training people in new imaging
>disciplines, and building a community for moving technologies further"
>says EI 2000 Symposium Chair Giordano Beretta of Hewlett-Packard in Palo
>Alto.
>
>"In the past year we have seen a revolution in document imaging, moving
>beyond electronic publishing, where electronic imaging was used
>separately in each stage of the workflow.  Today we talk of digital
>publishing, an integrated process that is fully digital from end to
>end.  At any time, a color piece can be repurposed for an arbitrary
>output medium without quality loss or manual intervention.  In addition,
>spectral color imaging and advanced color management techniques open a
>whole new world to system builders" explains Gabriel Marcu of Apple
>Computer in Cupertino, one of the Conference Chairs.
>
>Other areas covered by the symposium and of interest to the color
>imaging community are capture and display, human vision, document
>recognition, optical security and anti-counterfeiting, and Internet
>imaging.
>
>Electronic Imaging 2000 will be held a the San Jose Convention Center
>from January 23-28, 2000.  Complete course and instructor descriptions
>as well as registration information can be found on-line at
>http://www.spie.org/info/ei/courses.
>
>For more information on EI 2000
>http://www.spie.org/web/meetings/programs/pw00/ei00.html
>=============================================================
>
>MEDIA: Present yourselves at the SPIE Registration desk
>for complimentary admission.
>
>---
>
>Tim Johnson, Public Information Office
>SPIE--The International Society for Optical Engineering
>VOX: 360.676.3290, EXT 574 * FAX: 360.647.1445 * E-MAIL: timj@spie.org

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


--0-783368690-948930841=:29186--



From owner-ietf-outbound  Wed Jan 26 21:05:02 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA14556
	for ietf-outbound.10@ietf.org; Wed, 26 Jan 2000 21:04:29 -0500 (EST)
Received: from web1805.mail.yahoo.com (web1805.mail.yahoo.com [128.11.23.48])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA14366
	for <IETF@ietf.org>; Wed, 26 Jan 2000 20:54:41 -0500 (EST)
Received: (qmail 22348 invoked by uid 60001); 27 Jan 2000 00:01:56 -0000
Message-ID: <20000127000156.22347.qmail@web1805.mail.yahoo.com>
Received: from [216.185.31.139] by web1805.mail.yahoo.com; Wed, 26 Jan 2000 16:01:56 PST
Date: Wed, 26 Jan 2000 16:01:56 -0800 (PST)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: Mr. Marcu, you may be promoted for this! Please see;
To: marcu@apple.com
Cc: IETF@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1681692777-948931316=:21571"

--0-1681692777-948931316=:21571
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline


Dear Gabriel Marcu,

  As you see I have been invited to CONFERENCE 2000,
unfortuneately although I cannot attend this event;
I wish top thank the sponsors for their interest. I
would also ask if you might intercede with your
company-APPLE in order that they become world famous
for this 'gimmick' of the INTERNET AGE!

     Let me know if there is another I can do for you
in the near future-if APPLE cannot participate in
this-
perhaps, and may I be so bold, ( I notice an
'accent?')
if as your name suggests you may be from the Balkans,
I would very much like to work on a project for your
NATIVE language-and SCRIPT, whatever that may be, and 
provide a MODERN alternative in INFORMATION DESIGN for
your perusal sometime soon? I colorise texts according
to linguistic principles; as a designer put the new
"MAC" into FIVE DIFFERENT COLOR CHOICES...etc.
  Yours truly,

  Casey Farrell

Note: forwarded message attached.


=====
Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

 This Letter and All Contents Copyright 1999 Casey Farrell
              All Rights Reserved
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--0-1681692777-948931316=:21571
Content-Type: message/rfc822

X-Apparently-To: oh_yeah_dot_net@yahoo.com via web1803.mail.yahoo.com
X-Track2: 2
X-Track: -50
Received: from law2-f165.hotmail.com (HELO hotmail.com) (216.32.181.165)
  by mta214.mail.yahoo.com with SMTP; 26 Jan 2000 23:44:03 -0000
Received: (qmail 85010 invoked by uid 0); 26 Jan 2000 23:44:01 -0000
Message-ID: <20000126234401.85009.qmail@hotmail.com>
Received: from 216.185.31.139 by www.hotmail.com with HTTP;	Wed, 26 Jan 2000 15:44:01 PST
X-Originating-IP: [216.185.31.139]
From: "Casey Farrell" <california_star@hotmail.com>
To: timj@spie.org
Cc: kerstinb@spie.org
Subject: Re: NEWS RELEASE: Electronic Imaging Conference
Date: Wed, 26 Jan 2000 15:44:01 PST
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Content-Length: 7351

Attn: Kerstin Bailey; Director of Marketing
c/o   Society of Optical Engineeers

  Dear Kerstin,

   It was fun yakking with you just now-here is a re-spin of the idea,
my computer is giving me some trouble today so I hope this arrives w/o
looping or being chopped! Forward here: The designwork is one of many
which I own, that have specialization characteristics for the FORMAT
and STORAGE of Information through colorization 'templates.' Although
the designwork and proposed use shown here is for what appears as a
recreational or 'fun' use; ones very like this are especially mapped out to 
be multi-purposeful and could perhaps compose the 'embedded'
area of the new technologies we are currently looking at as 'wearable'
or even 'smart-card' etc.

  Pleasehave Tim give me a call when he's back from the conference.

Thanks-

    Casey



Casey Farrell; Designer                             Wednesday
San Francisco, California                        Jan. 27, 2000

Dear Ms. Sweeney,

  Thanks for your attention in bringing this matter to the attention of Mr. 
Sabean. My proposal is like frosting on a cake for the GIANTS!
Please excuse the reuse of the form here my computer stuck right after
we spoke this morning; & the FAX phone apparently has a major 'glitch'
so this is about the only way I'm able to get the info out today!

  Thank you-

RE: A 'Decimalized'( 'Digital') GIANTS Logo @ PAC BELL PARK ...4Y2K?

Attn: Karen Sweeney; Chief Executive Assistant
For:  Brian Sabean; Promotions Director
c/o   China Basin Baseball Group
       6603 3rd Street
        San Francisco, California


               Dear Mr. Sabean,

     Hope I have this to your attention in time for the premiere
of the new Pac Bell Baseball Park at China Basin. The idea is for a
simple designwork to inaugurate a sports arena in the "WIRELESS AGE!"

Please see:
       http://www.slip.net/~o614275

  With a plethora of hand-held computing devices available to the
average person, the NUMBER-PAD and KEYBOARD layouts are more a feature
of the ordinary work day than ever imagined before! The idea behind an
'optical -illusion' "LOGO" composed of numerals in place of letters, is 
based the premise that there has been an almost imperceptible new
turn at the level of ADVERTISING, and as most of the ADVERTISERS will
of course be 'TECK-STOCK' and 'START-UP' and such-if the GIANTS'FANS
are themselves looking at the figures...?

  Sunday Jan. 16, 2000's Examiner Sports FrontPage on which you were
featured-had my announcement on PAGE CL52, 710 Business Opportunities
of the same date in SF Sunday Examiner & Chronicle Classified Ads: and
the complimentary ONLINE VERSION w/ HOTLINK URL had this messaging:

                 http://www.slip.net/~o614275
                Designwork for Sale! $1,500,00
                Great Sports Promotion Situation
                available for the Wireless Age!

I am offering to the GIANTS for sale my designwork titled: 614275
which will serve as another splendid example of San Francisco style
memorabilia; fitting in nicely with the MUNI symbol, Ruth Azawa's
fountain at Union Square, Ghiradelli, North Beach, Ferry Boats, Wine,
French Bread, Santana's music, KQED, etc. The whole enchilada!

  Thank you for the consideration,

  Casey Farrell

tel: (425) 664-2489

  This Letter and All Contents Copyright 2000 Casey Farrell

               All Rights Reserved


>From: Tim Johnson <timj@spie.org>
>To: campbell@ior.com, lstein@paweekly.com, davidb@techweek.com, 
>california_star@hotmail.com, Matt_Hicks@zd.com, 
>justin.mullins@lexis-nexis.com, dclaymon@sjmercury.com, hbrody@mit.edu, 
>drotman@mit.edu
>Subject: NEWS RELEASE: Electronic Imaging Conference
>Date: Wed, 19 Jan 2000 14:38:04 -0800
>
>NEWS RELEASE:
>
>Electronic Imaging 2000 Showcases Digital Color Publishing
>
>"Will our company logo be the right color with sRGB or do I need ICC
>profiles?  Will my hardcopy look better with blue-noise or with
>stochastic halftoning?"
>
>Next week, the Symposium on Electronic Imaging, January 23-28 in San
>Jose will provide the answers.  Short courses on document imaging will
>cover a range of topics including elementary color science, image
>quality factors in color reproduction, and optical document security.
>
>"Over the years the conference on Color Imaging: Device Independent
>Color, Color Hardcopy, and Graphic Arts has become the world's most
>prestigious conference on this subject and is a cornerstone of the
>Symposium. Electronic Imaging 2000 will have a day and a half of short
>courses on Color Imaging Sunday and Monday followed by four days of
>papers Tuesday through Friday.  The presenters include the best
>specialists from all over the world," said Rich Ellson of Xerox Palo
>Alto Research Center, a member of the EI Symposium Organizing Committee.
>
>The Symposium on Electronic Imaging is cosponsored by the IS&T--the
>Society for Imaging Science and Technology, and SPIE--The International
>Society for Optical Engineering.  Since its inception in 1989,
>Electronic Imaging has been based in the Bay Area.  After starting out
>in Santa Clara, the two societies moved the conference to the San Jose
>Convention Center in 1991 where it has continued to both grow in size
>and evolve in subject matter.  This year a total of 962 papers will be
>presented in 24 conferences, and the organizers expect 1500 technical
>attendees.
>
>"Understanding the emerging interests of Silicon Valley
>imaging professionals has helped make this symposium a very rapid means
>of communicating important new ideas, training people in new imaging
>disciplines, and building a community for moving technologies further"
>says EI 2000 Symposium Chair Giordano Beretta of Hewlett-Packard in Palo
>Alto.
>
>"In the past year we have seen a revolution in document imaging, moving
>beyond electronic publishing, where electronic imaging was used
>separately in each stage of the workflow.  Today we talk of digital
>publishing, an integrated process that is fully digital from end to
>end.  At any time, a color piece can be repurposed for an arbitrary
>output medium without quality loss or manual intervention.  In addition,
>spectral color imaging and advanced color management techniques open a
>whole new world to system builders" explains Gabriel Marcu of Apple
>Computer in Cupertino, one of the Conference Chairs.
>
>Other areas covered by the symposium and of interest to the color
>imaging community are capture and display, human vision, document
>recognition, optical security and anti-counterfeiting, and Internet
>imaging.
>
>Electronic Imaging 2000 will be held a the San Jose Convention Center
>from January 23-28, 2000.  Complete course and instructor descriptions
>as well as registration information can be found on-line at
>http://www.spie.org/info/ei/courses.
>
>For more information on EI 2000
>http://www.spie.org/web/meetings/programs/pw00/ei00.html
>=============================================================
>
>MEDIA: Present yourselves at the SPIE Registration desk
>for complimentary admission.
>
>---
>
>Tim Johnson, Public Information Office
>SPIE--The International Society for Optical Engineering
>VOX: 360.676.3290, EXT 574 * FAX: 360.647.1445 * E-MAIL: timj@spie.org

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


--0-1681692777-948931316=:21571--



From owner-ietf-outbound@ietf.org  Wed Jan 26 21:07:31 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14607
	for <ietf-web-archive@odin.ietf.org>; Wed, 26 Jan 2000 21:07:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA22600;
	Wed, 26 Jan 2000 21:05:47 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA14556
	for ietf-outbound.10@ietf.org; Wed, 26 Jan 2000 21:04:29 -0500 (EST)
Received: from web1805.mail.yahoo.com (web1805.mail.yahoo.com [128.11.23.48])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA14366
	for <IETF@ietf.org>; Wed, 26 Jan 2000 20:54:41 -0500 (EST)
Received: (qmail 22348 invoked by uid 60001); 27 Jan 2000 00:01:56 -0000
Message-ID: <20000127000156.22347.qmail@web1805.mail.yahoo.com>
Received: from [216.185.31.139] by web1805.mail.yahoo.com; Wed, 26 Jan 2000 16:01:56 PST
Date: Wed, 26 Jan 2000 16:01:56 -0800 (PST)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: Mr. Marcu, you may be promoted for this! Please see;
To: marcu@apple.com
Cc: IETF@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1681692777-948931316=:21571"

--0-1681692777-948931316=:21571
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline


Dear Gabriel Marcu,

  As you see I have been invited to CONFERENCE 2000,
unfortuneately although I cannot attend this event;
I wish top thank the sponsors for their interest. I
would also ask if you might intercede with your
company-APPLE in order that they become world famous
for this 'gimmick' of the INTERNET AGE!

     Let me know if there is another I can do for you
in the near future-if APPLE cannot participate in
this-
perhaps, and may I be so bold, ( I notice an
'accent?')
if as your name suggests you may be from the Balkans,
I would very much like to work on a project for your
NATIVE language-and SCRIPT, whatever that may be, and 
provide a MODERN alternative in INFORMATION DESIGN for
your perusal sometime soon? I colorise texts according
to linguistic principles; as a designer put the new
"MAC" into FIVE DIFFERENT COLOR CHOICES...etc.
  Yours truly,

  Casey Farrell

Note: forwarded message attached.


=====
Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

 This Letter and All Contents Copyright 1999 Casey Farrell
              All Rights Reserved
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--0-1681692777-948931316=:21571
Content-Type: message/rfc822

X-Apparently-To: oh_yeah_dot_net@yahoo.com via web1803.mail.yahoo.com
X-Track2: 2
X-Track: -50
Received: from law2-f165.hotmail.com (HELO hotmail.com) (216.32.181.165)
  by mta214.mail.yahoo.com with SMTP; 26 Jan 2000 23:44:03 -0000
Received: (qmail 85010 invoked by uid 0); 26 Jan 2000 23:44:01 -0000
Message-ID: <20000126234401.85009.qmail@hotmail.com>
Received: from 216.185.31.139 by www.hotmail.com with HTTP;	Wed, 26 Jan 2000 15:44:01 PST
X-Originating-IP: [216.185.31.139]
From: "Casey Farrell" <california_star@hotmail.com>
To: timj@spie.org
Cc: kerstinb@spie.org
Subject: Re: NEWS RELEASE: Electronic Imaging Conference
Date: Wed, 26 Jan 2000 15:44:01 PST
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Content-Length: 7351

Attn: Kerstin Bailey; Director of Marketing
c/o   Society of Optical Engineeers

  Dear Kerstin,

   It was fun yakking with you just now-here is a re-spin of the idea,
my computer is giving me some trouble today so I hope this arrives w/o
looping or being chopped! Forward here: The designwork is one of many
which I own, that have specialization characteristics for the FORMAT
and STORAGE of Information through colorization 'templates.' Although
the designwork and proposed use shown here is for what appears as a
recreational or 'fun' use; ones very like this are especially mapped out to 
be multi-purposeful and could perhaps compose the 'embedded'
area of the new technologies we are currently looking at as 'wearable'
or even 'smart-card' etc.

  Pleasehave Tim give me a call when he's back from the conference.

Thanks-

    Casey



Casey Farrell; Designer                             Wednesday
San Francisco, California                        Jan. 27, 2000

Dear Ms. Sweeney,

  Thanks for your attention in bringing this matter to the attention of Mr. 
Sabean. My proposal is like frosting on a cake for the GIANTS!
Please excuse the reuse of the form here my computer stuck right after
we spoke this morning; & the FAX phone apparently has a major 'glitch'
so this is about the only way I'm able to get the info out today!

  Thank you-

RE: A 'Decimalized'( 'Digital') GIANTS Logo @ PAC BELL PARK ...4Y2K?

Attn: Karen Sweeney; Chief Executive Assistant
For:  Brian Sabean; Promotions Director
c/o   China Basin Baseball Group
       6603 3rd Street
        San Francisco, California


               Dear Mr. Sabean,

     Hope I have this to your attention in time for the premiere
of the new Pac Bell Baseball Park at China Basin. The idea is for a
simple designwork to inaugurate a sports arena in the "WIRELESS AGE!"

Please see:
       http://www.slip.net/~o614275

  With a plethora of hand-held computing devices available to the
average person, the NUMBER-PAD and KEYBOARD layouts are more a feature
of the ordinary work day than ever imagined before! The idea behind an
'optical -illusion' "LOGO" composed of numerals in place of letters, is 
based the premise that there has been an almost imperceptible new
turn at the level of ADVERTISING, and as most of the ADVERTISERS will
of course be 'TECK-STOCK' and 'START-UP' and such-if the GIANTS'FANS
are themselves looking at the figures...?

  Sunday Jan. 16, 2000's Examiner Sports FrontPage on which you were
featured-had my announcement on PAGE CL52, 710 Business Opportunities
of the same date in SF Sunday Examiner & Chronicle Classified Ads: and
the complimentary ONLINE VERSION w/ HOTLINK URL had this messaging:

                 http://www.slip.net/~o614275
                Designwork for Sale! $1,500,00
                Great Sports Promotion Situation
                available for the Wireless Age!

I am offering to the GIANTS for sale my designwork titled: 614275
which will serve as another splendid example of San Francisco style
memorabilia; fitting in nicely with the MUNI symbol, Ruth Azawa's
fountain at Union Square, Ghiradelli, North Beach, Ferry Boats, Wine,
French Bread, Santana's music, KQED, etc. The whole enchilada!

  Thank you for the consideration,

  Casey Farrell

tel: (425) 664-2489

  This Letter and All Contents Copyright 2000 Casey Farrell

               All Rights Reserved


>From: Tim Johnson <timj@spie.org>
>To: campbell@ior.com, lstein@paweekly.com, davidb@techweek.com, 
>california_star@hotmail.com, Matt_Hicks@zd.com, 
>justin.mullins@lexis-nexis.com, dclaymon@sjmercury.com, hbrody@mit.edu, 
>drotman@mit.edu
>Subject: NEWS RELEASE: Electronic Imaging Conference
>Date: Wed, 19 Jan 2000 14:38:04 -0800
>
>NEWS RELEASE:
>
>Electronic Imaging 2000 Showcases Digital Color Publishing
>
>"Will our company logo be the right color with sRGB or do I need ICC
>profiles?  Will my hardcopy look better with blue-noise or with
>stochastic halftoning?"
>
>Next week, the Symposium on Electronic Imaging, January 23-28 in San
>Jose will provide the answers.  Short courses on document imaging will
>cover a range of topics including elementary color science, image
>quality factors in color reproduction, and optical document security.
>
>"Over the years the conference on Color Imaging: Device Independent
>Color, Color Hardcopy, and Graphic Arts has become the world's most
>prestigious conference on this subject and is a cornerstone of the
>Symposium. Electronic Imaging 2000 will have a day and a half of short
>courses on Color Imaging Sunday and Monday followed by four days of
>papers Tuesday through Friday.  The presenters include the best
>specialists from all over the world," said Rich Ellson of Xerox Palo
>Alto Research Center, a member of the EI Symposium Organizing Committee.
>
>The Symposium on Electronic Imaging is cosponsored by the IS&T--the
>Society for Imaging Science and Technology, and SPIE--The International
>Society for Optical Engineering.  Since its inception in 1989,
>Electronic Imaging has been based in the Bay Area.  After starting out
>in Santa Clara, the two societies moved the conference to the San Jose
>Convention Center in 1991 where it has continued to both grow in size
>and evolve in subject matter.  This year a total of 962 papers will be
>presented in 24 conferences, and the organizers expect 1500 technical
>attendees.
>
>"Understanding the emerging interests of Silicon Valley
>imaging professionals has helped make this symposium a very rapid means
>of communicating important new ideas, training people in new imaging
>disciplines, and building a community for moving technologies further"
>says EI 2000 Symposium Chair Giordano Beretta of Hewlett-Packard in Palo
>Alto.
>
>"In the past year we have seen a revolution in document imaging, moving
>beyond electronic publishing, where electronic imaging was used
>separately in each stage of the workflow.  Today we talk of digital
>publishing, an integrated process that is fully digital from end to
>end.  At any time, a color piece can be repurposed for an arbitrary
>output medium without quality loss or manual intervention.  In addition,
>spectral color imaging and advanced color management techniques open a
>whole new world to system builders" explains Gabriel Marcu of Apple
>Computer in Cupertino, one of the Conference Chairs.
>
>Other areas covered by the symposium and of interest to the color
>imaging community are capture and display, human vision, document
>recognition, optical security and anti-counterfeiting, and Internet
>imaging.
>
>Electronic Imaging 2000 will be held a the San Jose Convention Center
>from January 23-28, 2000.  Complete course and instructor descriptions
>as well as registration information can be found on-line at
>http://www.spie.org/info/ei/courses.
>
>For more information on EI 2000
>http://www.spie.org/web/meetings/programs/pw00/ei00.html
>=============================================================
>
>MEDIA: Present yourselves at the SPIE Registration desk
>for complimentary admission.
>
>---
>
>Tim Johnson, Public Information Office
>SPIE--The International Society for Optical Engineering
>VOX: 360.676.3290, EXT 574 * FAX: 360.647.1445 * E-MAIL: timj@spie.org

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


--0-1681692777-948931316=:21571--



From owner-ietf-outbound  Thu Jan 27 12:31:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10258
	for ietf-outbound.10@ietf.org; Thu, 27 Jan 2000 12:30:02 -0500 (EST)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10138
	for <IETF@ietf.org>; Thu, 27 Jan 2000 12:22:56 -0500 (EST)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.1b+Sun/8.9.1) with SMTP id LAA00006
	for <IETF@ietf.org>; Thu, 27 Jan 2000 11:20:25 -0600 (CST)
Message-Id: <200001271720.LAA00006@rgfsparc.cr.usgs.gov>
Date: Thu, 27 Jan 2000 11:20:25 -0600 (CST)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: Mr. Marcu, you may be promoted for this! Please see;
To: IETF@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: QieC1C2+2ZkaR3W2fv6aVw==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 

> As you see I have been invited to CONFERENCE 2000,
>unfortuneately although I cannot attend this event;
>I wish top thank the sponsors for their interest.

OK, I'll bite.  What in the name of $#!*@ is this all about?  Is this some new 
and insidious multilayered spamfest, or what?

RGF

Robert G. Ferrell
Internet Technologist
National Business Center, US DoI
Robert_G_Ferrell@nbc.gov



From owner-ietf-outbound@ietf.org  Thu Jan 27 12:35:32 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10403
	for <ietf-web-archive@odin.ietf.org>; Thu, 27 Jan 2000 12:35:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA29830;
	Thu, 27 Jan 2000 12:33:46 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10258
	for ietf-outbound.10@ietf.org; Thu, 27 Jan 2000 12:30:02 -0500 (EST)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10138
	for <IETF@ietf.org>; Thu, 27 Jan 2000 12:22:56 -0500 (EST)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.1b+Sun/8.9.1) with SMTP id LAA00006
	for <IETF@ietf.org>; Thu, 27 Jan 2000 11:20:25 -0600 (CST)
Message-Id: <200001271720.LAA00006@rgfsparc.cr.usgs.gov>
Date: Thu, 27 Jan 2000 11:20:25 -0600 (CST)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: Mr. Marcu, you may be promoted for this! Please see;
To: IETF@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: QieC1C2+2ZkaR3W2fv6aVw==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 

> As you see I have been invited to CONFERENCE 2000,
>unfortuneately although I cannot attend this event;
>I wish top thank the sponsors for their interest.

OK, I'll bite.  What in the name of $#!*@ is this all about?  Is this some new 
and insidious multilayered spamfest, or what?

RGF

Robert G. Ferrell
Internet Technologist
National Business Center, US DoI
Robert_G_Ferrell@nbc.gov



From owner-ietf-outbound  Thu Jan 27 13:04:50 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA11058
	for ietf-outbound.10@ietf.org; Thu, 27 Jan 2000 13:04:26 -0500 (EST)
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10790
	for <ietf@ietf.org>; Thu, 27 Jan 2000 12:57:05 -0500 (EST)
From: stainlessonly@buystainlessonline.com
Received: from stainless.buystainlessonline.com (216-59-114-105.usa2.flashcom.net [216.59.114.105])
	by optimus.ietf.org (8.9.1a/8.9.1) with SMTP id MAA00408
	for <ietf@ietf.org>; Thu, 27 Jan 2000 12:55:32 -0500 (EST)
MIME-Version: 1.0
X-Encoding: MIME
Content-Type: multipart/alternative;
	boundary="----=_NextPart_770465784558072287"
Date: Thu, 27 Jan 2000 12:54:33 -0500
Message-Id: <boorjd.miudkiqkomfayrjtlxm@stainless.buystainlessonline.com>
Reply-To: webmaster@buystainlessonline.com
Subject: AL raises nickel surcharge; Auction Data.......
To: ietf@ietf.org

This is a multi-part message in MIME format.

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

StainlessOnly! is a weekly Stainless Steel related Electronic Magazine. We are
currently reaching:23,471 readers.

MILL INCREASE!!!! AGAIN!!!!
PITTSBURGH, Jan. 25 -- Allegheny Ludlum Corp. here said Tuesday it would attempt 
To raise prices on stainless steel sheet, strip and coiled plate by between 4 and 6 percent
Effective with shipments Feb. 7. It is the industry's second, Allegheny Ludlum-led 
Stainless steel price hike in six weeks. The company led a 4 to 6 percent increase on 
Stainless steel coiled and uncoiled plate that went into effect Jan. 4. It also has been at the 
Forefront of revising raw material surcharge triggers for nickel and chromium in the past 
Several months. The nickel surcharge trigger is set at $2 per pound while the surcharge 
Level for chromium is set at 35 cents per pound.

For your info:
Since the start of the Federal tax of imported steel (Sept ’99), US based mills have added 
A total of $20.00cwt in Nickel Surcharges. This newest mill press release indicates that 
The prices for stainless steel products will continue to climb.

Scrap Pricing (Philadelphia):
Scrap has remained constant, holding around $35.00cwt.

We currently have (17) Stainless Steel items up for auction.
If you have a surplus/overstock item that you wish to sell,
please visit www.buystainlessonline.com and click "Start an Auction"

To place an inquiry in a NON-HTML based format......
simply reply to this email with the necessary info.

TO BE REMOVED:
send a blank email to UNSUBSCRIBE@buystainlessonline.com


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-microsoft-com:office:office"
xmlns:w=3D"urn:schemas-microsoft-com:office:word"
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"./stainlessonly!_files/filelist.xml">
<link rel=3DEdit-Time-Data href=3D"./stainlessonly!_files/editdata.mso">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title> </title>
<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>75</w:Zoom>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h1
	{mso-style-next:Normal;
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:1;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:navy;
	mso-font-kerning:0pt;
	font-weight:normal;
	text-decoration:underline;
	text-underline:single;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	color:#339966;}
a:link, span.MsoHyperlink
	{color:#408080;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1"/>
 </o:shapelayout></xml><![endif]--><!--[if gte mso 9]><xml>
 <u1:DocumentProperties>
  <u1:Author>Mason</u1:Author>
  <u1:Template>Normal</u1:Template>
  <u1:LastAuthor>KSM</u1:LastAuthor>
  <u1:Revision>8</u1:Revision>
  <u1:TotalTime>30</u1:TotalTime>
  <u1:Created>1999-12-21T18:27:00Z</u1:Created>
  <u1:LastSaved>1999-12-22T17:35:00Z</u1:LastSaved>
  <u1:Pages>2</u1:Pages>
  <u1:Words>89</u1:Words>
  <u1:Characters>511</u1:Characters>
  <u1:Company>Keystone Specialty Metals</u1:Company>
  <u1:Lines>4</u1:Lines>
  <u1:Paragraphs>1</u1:Paragraphs>
  <u1:CharactersWithSpaces>627</u1:CharactersWithSpaces>
  <u1:Version>9.2720</u1:Version>
 </u1:DocumentProperties>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u2:WordDocument>
  <u2:Zoom>75</u2:Zoom>
 </u2:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u3:shapedefaults u4:ext=3D"edit" spidmax=3D"1029"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u5:shapelayout u6:ext=3D"edit">
  <u5:idmap u6:ext=3D"edit" data=3D"1"/>
 </u5:shapelayout>
</xml><![endif]-->
</head>

<body lang=3DEN-US link=3D"#408080" vlink=3Dpurple style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><u7:wrapblock><u8:shapetype id=3D"_x0000_t75" 
coordsize=3D"21600,21600" u7:spt=3D"75" u7:preferrelative=3D"t" 
path=3D"m@4@5l@4@11@9@11@9@5xe" filled=3D"f" stroked=3D"f"><u8:stroke 
joinstyle=3D"miter"/><u8:formulas><u8:f eqn=3D"if lineDrawn pixelLineWidth 
0"/><u8:f eqn=3D"sum @0 1 0"/><u8:f eqn=3D"sum 0 0 @1"/><u8:f eqn=3D"prod @2 1 
2"/><u8:f eqn=3D"prod @3 21600 pixelWidth"/><u8:f eqn=3D"prod @3 21600 
pixelHeight"/><u8:f eqn=3D"sum @0 0 1"/><u8:f eqn=3D"prod @6 1 2"/><u8:f eqn=3D"prod 
@7 21600 pixelWidth"/><u8:f eqn=3D"sum @8 21600 0"/><u8:f eqn=3D"prod @7 21600 
pixelHeight"/><u8:f eqn=3D"sum @10 21600 0"/></u8:formulas><u8:path 
u7:extrusionok=3D"f" gradientshapeok=3D"t" u7:connecttype=3D"rect"/><u7:lock 
u8:ext=3D"edit" aspectratio=3D"t"/></u8:shapetype><u8:shape id=3D"_x0000_s1028" 
type=3D"#_x0000_t75" style=3D"position:absolute;&#13;&#10;  margin-left:0;
margin-top:0;width:324pt;height:54pt;z-index:1;&#13;&#10;  
mso-position-horizontal-relative:text;
mso-position-vertical-relative:text"><u8:imagedata src=3D".
/joinlist_files/image001.gif" u7:title=3D"logo"/><u9:wrap 
type=3D"topAndBottom"/></u8:shape><img
width=3D463 height=3D81 id=3D"_x0000_i1025"
src=3D"http://buystainlessonline.com/gifs/stonlarge.gif" 
u8:shapes=3D"_x0000_s1028"></u7:wrapblock></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>StainlessOnly!
Is a weekly Stainless Steel related E Magazine<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Currently
serving 23,471 users. StainlessOnly! Is brought to <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>You
by <span style=3D'color:navy'><a href=3D"http://buystainlessonline.com/"><span
style=3D'color:navy;text-decoration:none;
text-underline:none'>BuyStainlessOnline.
</span></a></span><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'color:navy'><![if !
supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></b></p>

<p class=3DMsoNormal><b><span style=3D'color:navy'>Yet another Mill 
Surcharge:<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>PITTSBURGH,
Jan. 25 -- <u>Allegheny Ludlum Corp</u>. here said Tuesday it would attempt 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>To
raise prices on stainless steel sheet, strip and coiled plate by between 4 
and
6 percent<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Effective
with shipments Feb. 7. It is the industry's second, Allegheny Ludlum-led 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Stainless
steel price hike in six weeks. The company led a 4 to 6 percent increase on 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Stainless
steel coiled and uncoiled plate that went into effect Jan. 4. It also has 
been
at the <o:p></o:p></span></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><span style=3D'font-size:9.0pt;
mso-bidi-font-size:12.0pt'>Forefront of revising raw material surcharge
triggers for nickel and chromium in the past <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Several
months. The nickel surcharge trigger is set at $2 per pound while the 
surcharge
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Level
for chromium is set at 35 cents per pound.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:navy'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>For your info:<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Since the start of the Federal tax of imported steel (Sept 
&#8217;99),
US based mills have added <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>A total of $20.00cwt in Nickel Surcharges. This newest mill 
press
release indicates that <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>The prices for stainless steel products will continue to climb.
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Scrap Pricing (</span><span style=3D'font-size:9.0pt;
mso-bidi-font-size:
12.0pt;color:navy'>Philadelphia</span><span style=3D'font-size:9.0pt;
mso-bidi-font-size:
12.0pt;color:black'>):<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Scrap has remained constant, holding around $35.00cwt.
</span><span
style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:navy'><![if !supportEmptyParas]>&nbsp;<!
[endif]><o:p></o:p></span></p>

<h1><span style=3D'text-decoration:none;text-underline:none'><![if !
supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></h1>

<h1><span style=3D'text-decoration:none;text-underline:none'>BuyStainlessOnline.
com
Auction Statistics<o:p></o:p></span></h1>

<table border=3D1 cellpadding=3D0 width=3D"26%" style=3D'width:26.86%;
mso-cellspacing:
 1.5pt;mso-padding-alt:0in 0in 0in 0in'>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#191919;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><b><span
  style=3D'color:white'>Category</span></b><span 
style=3D'color:white'><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#191919;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><b><span
  style=3D'color:white'>Items</span></b><span 
style=3D'color:white'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?angle"><span
  style=3D'color:red;text-decoration:none;
text-underline:none'>Angle</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>1<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?coil"><span
  style=3D'color:red;text-decoration:none;
text-underline:none'>Coil</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>4<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?flat"><span
  style=3D'color:red;text-decoration:none;text-underline:none'>Flat 
Bar</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>2<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?pipe"><span
  style=3D'color:red;text-decoration:none;
text-underline:none'>Pipe</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>10<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?plate"><span
  style=3D'color:red;text-decoration:none;
text-underline:none'>Plate</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>0<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?rounds"><span
  style=3D'color:red;text-decoration:none;text-underline:none'>Round 
Bar</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>0<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?sheet"><span
  style=3D'color:red;text-decoration:none;
text-underline:none'>Sheet</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>0<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?tubing"><span
  style=3D'color:red;text-decoration:none;
text-underline:none'>Tubing</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>0<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>If
you would like to add an item to our auction,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Please
visit <b><span style=3D'color:navy'><a href=3D"http://buystainlessonline.com/"
title=3D"This takes you home!"><span style=3D'color:navy;text-decoration:none;
text-underline:none'>BuyStainlessOnline.com</span></a></span></b></span><span
style=3D'color:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><span style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt'>BuyStainlessOnline is currently 
offering<o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;

color:red'><a href=3D"http://buystainlessonline.com/inquiryform.htm"
title=3D"Click here to submit a flat bar inquiry"><span style=3D'color:red;
text-decoration:none;text-underline:none'>Flat Bar.
</span></a></span></b><b><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;color:black'> 
</span></b><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;color:black'>To find out 
more
about future plans<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
color:black'>As far as prime product is concerned, contact 
the<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
color:red'><a
href=3D"mailto:webmaster@buystainlessonline.com?
subject=3DInquiry%20about%20future%20plans"
title=3D"Click Here!"><span style=3D'color:red;text-decoration:none;
text-underline:
none'>Webmaster.</span></a><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'color:red'><![if !supportEmptyParas]>&nbsp;
<![endif]><o:p></o:p></span></b></p>

<p class=3DMsoNormal><b><span style=3D'color:red'><a
href=3D"mailto:remove@buystainlessonline.com?subject=3Dunsubscribe"
title=3D"This will remove you from the E magazine StainlessOnly!"><span
style=3D'color:red;text-decoration:none;text-underline:none'>UNSUBSCRIBE ME!
</span></a><o:p></o:p></span></b></p>

</div>

</body>

</html>

------=_NextPart_770465784558072287--



From owner-ietf-outbound@ietf.org  Thu Jan 27 13:09:09 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11150
	for <ietf-web-archive@odin.ietf.org>; Thu, 27 Jan 2000 13:09:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA00749;
	Thu, 27 Jan 2000 13:06:49 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA11058
	for ietf-outbound.10@ietf.org; Thu, 27 Jan 2000 13:04:26 -0500 (EST)
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10790
	for <ietf@ietf.org>; Thu, 27 Jan 2000 12:57:05 -0500 (EST)
From: stainlessonly@buystainlessonline.com
Received: from stainless.buystainlessonline.com (216-59-114-105.usa2.flashcom.net [216.59.114.105])
	by optimus.ietf.org (8.9.1a/8.9.1) with SMTP id MAA00408
	for <ietf@ietf.org>; Thu, 27 Jan 2000 12:55:32 -0500 (EST)
MIME-Version: 1.0
X-Encoding: MIME
Content-Type: multipart/alternative;
	boundary="----=_NextPart_770465784558072287"
Date: Thu, 27 Jan 2000 12:54:33 -0500
Message-Id: <boorjd.miudkiqkomfayrjtlxm@stainless.buystainlessonline.com>
Reply-To: webmaster@buystainlessonline.com
Subject: AL raises nickel surcharge; Auction Data.......
To: ietf@ietf.org

This is a multi-part message in MIME format.

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

StainlessOnly! is a weekly Stainless Steel related Electronic Magazine. We are
currently reaching:23,471 readers.

MILL INCREASE!!!! AGAIN!!!!
PITTSBURGH, Jan. 25 -- Allegheny Ludlum Corp. here said Tuesday it would attempt 
To raise prices on stainless steel sheet, strip and coiled plate by between 4 and 6 percent
Effective with shipments Feb. 7. It is the industry's second, Allegheny Ludlum-led 
Stainless steel price hike in six weeks. The company led a 4 to 6 percent increase on 
Stainless steel coiled and uncoiled plate that went into effect Jan. 4. It also has been at the 
Forefront of revising raw material surcharge triggers for nickel and chromium in the past 
Several months. The nickel surcharge trigger is set at $2 per pound while the surcharge 
Level for chromium is set at 35 cents per pound.

For your info:
Since the start of the Federal tax of imported steel (Sept ’99), US based mills have added 
A total of $20.00cwt in Nickel Surcharges. This newest mill press release indicates that 
The prices for stainless steel products will continue to climb.

Scrap Pricing (Philadelphia):
Scrap has remained constant, holding around $35.00cwt.

We currently have (17) Stainless Steel items up for auction.
If you have a surplus/overstock item that you wish to sell,
please visit www.buystainlessonline.com and click "Start an Auction"

To place an inquiry in a NON-HTML based format......
simply reply to this email with the necessary info.

TO BE REMOVED:
send a blank email to UNSUBSCRIBE@buystainlessonline.com


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-microsoft-com:office:office"
xmlns:w=3D"urn:schemas-microsoft-com:office:word"
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"./stainlessonly!_files/filelist.xml">
<link rel=3DEdit-Time-Data href=3D"./stainlessonly!_files/editdata.mso">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title> </title>
<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>75</w:Zoom>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h1
	{mso-style-next:Normal;
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:1;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:navy;
	mso-font-kerning:0pt;
	font-weight:normal;
	text-decoration:underline;
	text-underline:single;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	color:#339966;}
a:link, span.MsoHyperlink
	{color:#408080;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1"/>
 </o:shapelayout></xml><![endif]--><!--[if gte mso 9]><xml>
 <u1:DocumentProperties>
  <u1:Author>Mason</u1:Author>
  <u1:Template>Normal</u1:Template>
  <u1:LastAuthor>KSM</u1:LastAuthor>
  <u1:Revision>8</u1:Revision>
  <u1:TotalTime>30</u1:TotalTime>
  <u1:Created>1999-12-21T18:27:00Z</u1:Created>
  <u1:LastSaved>1999-12-22T17:35:00Z</u1:LastSaved>
  <u1:Pages>2</u1:Pages>
  <u1:Words>89</u1:Words>
  <u1:Characters>511</u1:Characters>
  <u1:Company>Keystone Specialty Metals</u1:Company>
  <u1:Lines>4</u1:Lines>
  <u1:Paragraphs>1</u1:Paragraphs>
  <u1:CharactersWithSpaces>627</u1:CharactersWithSpaces>
  <u1:Version>9.2720</u1:Version>
 </u1:DocumentProperties>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u2:WordDocument>
  <u2:Zoom>75</u2:Zoom>
 </u2:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u3:shapedefaults u4:ext=3D"edit" spidmax=3D"1029"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u5:shapelayout u6:ext=3D"edit">
  <u5:idmap u6:ext=3D"edit" data=3D"1"/>
 </u5:shapelayout>
</xml><![endif]-->
</head>

<body lang=3DEN-US link=3D"#408080" vlink=3Dpurple style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><u7:wrapblock><u8:shapetype id=3D"_x0000_t75" 
coordsize=3D"21600,21600" u7:spt=3D"75" u7:preferrelative=3D"t" 
path=3D"m@4@5l@4@11@9@11@9@5xe" filled=3D"f" stroked=3D"f"><u8:stroke 
joinstyle=3D"miter"/><u8:formulas><u8:f eqn=3D"if lineDrawn pixelLineWidth 
0"/><u8:f eqn=3D"sum @0 1 0"/><u8:f eqn=3D"sum 0 0 @1"/><u8:f eqn=3D"prod @2 1 
2"/><u8:f eqn=3D"prod @3 21600 pixelWidth"/><u8:f eqn=3D"prod @3 21600 
pixelHeight"/><u8:f eqn=3D"sum @0 0 1"/><u8:f eqn=3D"prod @6 1 2"/><u8:f eqn=3D"prod 
@7 21600 pixelWidth"/><u8:f eqn=3D"sum @8 21600 0"/><u8:f eqn=3D"prod @7 21600 
pixelHeight"/><u8:f eqn=3D"sum @10 21600 0"/></u8:formulas><u8:path 
u7:extrusionok=3D"f" gradientshapeok=3D"t" u7:connecttype=3D"rect"/><u7:lock 
u8:ext=3D"edit" aspectratio=3D"t"/></u8:shapetype><u8:shape id=3D"_x0000_s1028" 
type=3D"#_x0000_t75" style=3D"position:absolute;&#13;&#10;  margin-left:0;
margin-top:0;width:324pt;height:54pt;z-index:1;&#13;&#10;  
mso-position-horizontal-relative:text;
mso-position-vertical-relative:text"><u8:imagedata src=3D".
/joinlist_files/image001.gif" u7:title=3D"logo"/><u9:wrap 
type=3D"topAndBottom"/></u8:shape><img
width=3D463 height=3D81 id=3D"_x0000_i1025"
src=3D"http://buystainlessonline.com/gifs/stonlarge.gif" 
u8:shapes=3D"_x0000_s1028"></u7:wrapblock></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>StainlessOnly!
Is a weekly Stainless Steel related E Magazine<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Currently
serving 23,471 users. StainlessOnly! Is brought to <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>You
by <span style=3D'color:navy'><a href=3D"http://buystainlessonline.com/"><span
style=3D'color:navy;text-decoration:none;
text-underline:none'>BuyStainlessOnline.
</span></a></span><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'color:navy'><![if !
supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></b></p>

<p class=3DMsoNormal><b><span style=3D'color:navy'>Yet another Mill 
Surcharge:<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>PITTSBURGH,
Jan. 25 -- <u>Allegheny Ludlum Corp</u>. here said Tuesday it would attempt 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>To
raise prices on stainless steel sheet, strip and coiled plate by between 4 
and
6 percent<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Effective
with shipments Feb. 7. It is the industry's second, Allegheny Ludlum-led 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Stainless
steel price hike in six weeks. The company led a 4 to 6 percent increase on 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Stainless
steel coiled and uncoiled plate that went into effect Jan. 4. It also has 
been
at the <o:p></o:p></span></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><span style=3D'font-size:9.0pt;
mso-bidi-font-size:12.0pt'>Forefront of revising raw material surcharge
triggers for nickel and chromium in the past <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Several
months. The nickel surcharge trigger is set at $2 per pound while the 
surcharge
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Level
for chromium is set at 35 cents per pound.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:navy'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>For your info:<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Since the start of the Federal tax of imported steel (Sept 
&#8217;99),
US based mills have added <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>A total of $20.00cwt in Nickel Surcharges. This newest mill 
press
release indicates that <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>The prices for stainless steel products will continue to climb.
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Scrap Pricing (</span><span style=3D'font-size:9.0pt;
mso-bidi-font-size:
12.0pt;color:navy'>Philadelphia</span><span style=3D'font-size:9.0pt;
mso-bidi-font-size:
12.0pt;color:black'>):<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Scrap has remained constant, holding around $35.00cwt.
</span><span
style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:navy'><![if !supportEmptyParas]>&nbsp;<!
[endif]><o:p></o:p></span></p>

<h1><span style=3D'text-decoration:none;text-underline:none'><![if !
supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></h1>

<h1><span style=3D'text-decoration:none;text-underline:none'>BuyStainlessOnline.
com
Auction Statistics<o:p></o:p></span></h1>

<table border=3D1 cellpadding=3D0 width=3D"26%" style=3D'width:26.86%;
mso-cellspacing:
 1.5pt;mso-padding-alt:0in 0in 0in 0in'>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#191919;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><b><span
  style=3D'color:white'>Category</span></b><span 
style=3D'color:white'><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#191919;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><b><span
  style=3D'color:white'>Items</span></b><span 
style=3D'color:white'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?angle"><span
  style=3D'color:red;text-decoration:none;
text-underline:none'>Angle</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>1<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?coil"><span
  style=3D'color:red;text-decoration:none;
text-underline:none'>Coil</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>4<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?flat"><span
  style=3D'color:red;text-decoration:none;text-underline:none'>Flat 
Bar</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>2<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?pipe"><span
  style=3D'color:red;text-decoration:none;
text-underline:none'>Pipe</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>10<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?plate"><span
  style=3D'color:red;text-decoration:none;
text-underline:none'>Plate</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>0<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?rounds"><span
  style=3D'color:red;text-decoration:none;text-underline:none'>Round 
Bar</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>0<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?sheet"><span
  style=3D'color:red;text-decoration:none;
text-underline:none'>Sheet</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>0<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"46%" style=3D'width:46.56%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><span style=3D'color:red'><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?tubing"><span
  style=3D'color:red;text-decoration:none;
text-underline:none'>Tubing</span></a><o:p></o:p></span></p>
  </td>
  <td width=3D"51%" style=3D'width:51.26%;background:#F3F3F3;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>0<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>If
you would like to add an item to our auction,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Please
visit <b><span style=3D'color:navy'><a href=3D"http://buystainlessonline.com/"
title=3D"This takes you home!"><span style=3D'color:navy;text-decoration:none;
text-underline:none'>BuyStainlessOnline.com</span></a></span></b></span><span
style=3D'color:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><span style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt'>BuyStainlessOnline is currently 
offering<o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;

color:red'><a href=3D"http://buystainlessonline.com/inquiryform.htm"
title=3D"Click here to submit a flat bar inquiry"><span style=3D'color:red;
text-decoration:none;text-underline:none'>Flat Bar.
</span></a></span></b><b><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;color:black'> 
</span></b><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;color:black'>To find out 
more
about future plans<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
color:black'>As far as prime product is concerned, contact 
the<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
color:red'><a
href=3D"mailto:webmaster@buystainlessonline.com?
subject=3DInquiry%20about%20future%20plans"
title=3D"Click Here!"><span style=3D'color:red;text-decoration:none;
text-underline:
none'>Webmaster.</span></a><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'color:red'><![if !supportEmptyParas]>&nbsp;
<![endif]><o:p></o:p></span></b></p>

<p class=3DMsoNormal><b><span style=3D'color:red'><a
href=3D"mailto:remove@buystainlessonline.com?subject=3Dunsubscribe"
title=3D"This will remove you from the E magazine StainlessOnly!"><span
style=3D'color:red;text-decoration:none;text-underline:none'>UNSUBSCRIBE ME!
</span></a><o:p></o:p></span></b></p>

</div>

</body>

</html>

------=_NextPart_770465784558072287--



From owner-ietf-outbound  Fri Jan 28 01:10:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA21885
	for ietf-outbound.10@ietf.org; Fri, 28 Jan 2000 01:10:03 -0500 (EST)
Received: from pi.pair.com (pi.pair.com [209.68.1.29])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21622
	for <ietf@ietf.org>; Fri, 28 Jan 2000 01:06:44 -0500 (EST)
Received: from localhost (davidh@localhost) by pi.pair.com (8.9.1/8.6.12) with ESMTP id BAA18898 for <ietf@ietf.org>; Fri, 28 Jan 2000 01:06:40 -0500 (EST)
X-Envelope-To: <ietf@ietf.org>
Date: Fri, 28 Jan 2000 01:06:40 -0500 (EST)
From: David Herron <davidh@7gen.com>
X-Sender: davidh@pi.pair.com
To: ietf@ietf.org
Subject: DNS & funny characters
Message-ID: <Pine.BSF.4.10.10001280105570.2137-100000@pi.pair.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


http://www.cnn.com/2000/TECH/computing/01/27/forget.asci.idg/index.html

The DNS needs to be redesigned to use Unicode.

	David



From owner-ietf-outbound@ietf.org  Fri Jan 28 01:12:44 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22105
	for <ietf-web-archive@odin.ietf.org>; Fri, 28 Jan 2000 01:12:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA28537;
	Fri, 28 Jan 2000 01:10:46 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id BAA21885
	for ietf-outbound.10@ietf.org; Fri, 28 Jan 2000 01:10:03 -0500 (EST)
Received: from pi.pair.com (pi.pair.com [209.68.1.29])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21622
	for <ietf@ietf.org>; Fri, 28 Jan 2000 01:06:44 -0500 (EST)
Received: from localhost (davidh@localhost) by pi.pair.com (8.9.1/8.6.12) with ESMTP id BAA18898 for <ietf@ietf.org>; Fri, 28 Jan 2000 01:06:40 -0500 (EST)
X-Envelope-To: <ietf@ietf.org>
Date: Fri, 28 Jan 2000 01:06:40 -0500 (EST)
From: David Herron <davidh@7gen.com>
X-Sender: davidh@pi.pair.com
To: ietf@ietf.org
Subject: DNS & funny characters
Message-ID: <Pine.BSF.4.10.10001280105570.2137-100000@pi.pair.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


http://www.cnn.com/2000/TECH/computing/01/27/forget.asci.idg/index.html

The DNS needs to be redesigned to use Unicode.

	David



From owner-ietf-outbound  Fri Jan 28 06:00:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA05235
	for ietf-outbound.10@ietf.org; Fri, 28 Jan 2000 06:00:02 -0500 (EST)
Received: from monsoon.mail.pipex.net (monsoon.mail.pipex.net [158.43.128.69])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA05189
	for <ietf@ietf.org>; Fri, 28 Jan 2000 05:50:53 -0500 (EST)
Received: (qmail 15875 invoked from network); 28 Jan 2000 10:50:52 -0000
Received: from userar87.uk.uudial.com (HELO GK-SONY) (62.188.136.246)
  by smtp.dial.pipex.com with SMTP; 28 Jan 2000 10:50:52 -0000
Message-Id: <4.2.2.20000128100607.00ac1a00@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 28 Jan 2000 10:12:23 +0000
To: David Herron <davidh@7gen.com>
From: Graham Klyne <GK@Dial.pipex.com>
Subject: Re: DNS & funny characters
Cc: ietf@ietf.org
In-Reply-To: <Pine.BSF.4.10.10001280105570.2137-100000@pi.pair.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 01:06 AM 1/28/00 -0500, David Herron wrote:

>http://www.cnn.com/2000/TECH/computing/01/27/forget.asci.idg/index.html
>
>The DNS needs to be redesigned to use Unicode.

Note that _DNS_ is quite capable of supporting such names;  it's the host 
naming rules that impose constraints.  See RFC 2181, section 11.

See also the recent announcement (24-Jan-2000):

>A new IETF working group has been proposed in the Internet Area.
>The IESG has not made any determination as yet.
>
>The following Description was submitted, and is provided for
>informational purposes only:
>
>  Mailing Lists:
>      General Discussion:idn@ops.ietf.org
>      To Subscribe:      idn-request@ops.ietf.org
>      Archive:           ftp://ops.ietf.org/pub/lists/idn*
>
>Description of Working Group:
>
>The goal of the group is to investigate and specify the requirements for
>supporting internationalized domain names.
>
>The scope of the group is to investigate the possible means of doing
>this and what technical impact they will have on the users of such names
>and on other users and administrators of the domain name system.
>
>The group will not address the question of what, if any, body should
>administer or control usage of names that use this functionality.
>
>The Action Item(s) for the Working Group are
>
>  1. An Informational RFC specifying the requirements for encoding
>     International characters into DNS names and records. The document
>     should provide guidance for development solutions to this problem,
>     taking localized (e.g. writing order) and related operational issues
>    into consideration.
>
>  2. An Informational RFC or RFC's documenting the various proposals
>     and Implementations of Internationalization (i18n) of Domain Names.
>     The document(s) should also provide a technical evaluation of the
>     proposals by the Working Group.



#g


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



From owner-ietf-outbound@ietf.org  Fri Jan 28 06:02:17 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05333
	for <ietf-web-archive@odin.ietf.org>; Fri, 28 Jan 2000 06:02:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA06057;
	Fri, 28 Jan 2000 05:59:59 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id GAA05235
	for ietf-outbound.10@ietf.org; Fri, 28 Jan 2000 06:00:02 -0500 (EST)
Received: from monsoon.mail.pipex.net (monsoon.mail.pipex.net [158.43.128.69])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA05189
	for <ietf@ietf.org>; Fri, 28 Jan 2000 05:50:53 -0500 (EST)
Received: (qmail 15875 invoked from network); 28 Jan 2000 10:50:52 -0000
Received: from userar87.uk.uudial.com (HELO GK-SONY) (62.188.136.246)
  by smtp.dial.pipex.com with SMTP; 28 Jan 2000 10:50:52 -0000
Message-Id: <4.2.2.20000128100607.00ac1a00@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 28 Jan 2000 10:12:23 +0000
To: David Herron <davidh@7gen.com>
From: Graham Klyne <GK@Dial.pipex.com>
Subject: Re: DNS & funny characters
Cc: ietf@ietf.org
In-Reply-To: <Pine.BSF.4.10.10001280105570.2137-100000@pi.pair.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 01:06 AM 1/28/00 -0500, David Herron wrote:

>http://www.cnn.com/2000/TECH/computing/01/27/forget.asci.idg/index.html
>
>The DNS needs to be redesigned to use Unicode.

Note that _DNS_ is quite capable of supporting such names;  it's the host 
naming rules that impose constraints.  See RFC 2181, section 11.

See also the recent announcement (24-Jan-2000):

>A new IETF working group has been proposed in the Internet Area.
>The IESG has not made any determination as yet.
>
>The following Description was submitted, and is provided for
>informational purposes only:
>
>  Mailing Lists:
>      General Discussion:idn@ops.ietf.org
>      To Subscribe:      idn-request@ops.ietf.org
>      Archive:           ftp://ops.ietf.org/pub/lists/idn*
>
>Description of Working Group:
>
>The goal of the group is to investigate and specify the requirements for
>supporting internationalized domain names.
>
>The scope of the group is to investigate the possible means of doing
>this and what technical impact they will have on the users of such names
>and on other users and administrators of the domain name system.
>
>The group will not address the question of what, if any, body should
>administer or control usage of names that use this functionality.
>
>The Action Item(s) for the Working Group are
>
>  1. An Informational RFC specifying the requirements for encoding
>     International characters into DNS names and records. The document
>     should provide guidance for development solutions to this problem,
>     taking localized (e.g. writing order) and related operational issues
>    into consideration.
>
>  2. An Informational RFC or RFC's documenting the various proposals
>     and Implementations of Internationalization (i18n) of Domain Names.
>     The document(s) should also provide a technical evaluation of the
>     proposals by the Working Group.



#g


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



From owner-ietf-outbound  Sat Jan 29 01:11:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA05383
	for ietf-outbound.10@ietf.org; Sat, 29 Jan 2000 01:10:03 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05110
	for <ietf@ietf.org>; Sat, 29 Jan 2000 01:06:34 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id OAA52468;
	Sat, 29 Jan 2000 14:06:47 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38928323.6DF08264@oke.com>
Date: Sat, 29 Jan 2000 14:05:23 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
CC: isoc@isoc.org
Subject: 1601bis: The Charter of IAB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

To Whom It May Concern

Re: Last Call: Charter of the Internet Architecture Board (IAB) to BCP

> 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 February 9, 2000.

> Files can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-iab-rfc1601bis-02.txt


General

1. Why should the IESG approve the charter? Why not the ISOC?
2. There is no clear statement about the relationship between
   ISOC and IAB. Why?
3. There is no clear statement about relationship with RFC-Editor, 
   IESG, IETF-Sec, IANA, and ICANN. Why?

Accountability

4. As the community is not only exclusively the IETF anymore, 
   what does really "on behalf of the Internet Community" mean?
   What measurement will be used? Will the IAB publish at least
   an annual "progress report"? What/Where is the replacement of
   what IAB previously reported in the IMR?

5. How will the IAB implement "own choosing" of BCP-9:
   "The IAB shall then review the situation and attempt to resolve 
   it in a manner of its OWN CHOOSING."
   See also BCP-9:
   6.5  Conflict Resolution and Appeals
   6.5.1 Working Group Disputes
   6.5.2 Process Failures
   6.5.3 Questions of Applicable Procedure
   See also BCP-11:
   3.6  Internet Architecture Board
   3.7  Internet Assigned Numbers Authority

6. What should the IAB/ISOC do, if the IESG signs a treaty without 
   having a Last Call?



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

Enclosed is my suggested framework of 1601bis


#include <Standard_BCP-9_Headers.h>

1. The Role of the IAB
   - a brief description of the IAB
     * why it is chartered
     * by whom
     * for what
     * some other brief blah-blah-blahs.

2. Organizational Issues
2.1 The IAB chair
2.2 The ExecDir
2.3 The Current Task Forces (Arm?)
    - IRTF
    - IETF
2.4 Voting Rule
2.5 Archiving
    - directory: announcement, appeal, minutes
    - prior cases: e.g. Crocker vs. IESG(1995), Simpson vs. IESG(1999).
    - hall of fame: prior IAB members, etc.
    - who is the holder of zone iab.org, iana.org, ietf.org, and
      rfc-editors.org ?
    - etc.
2.6 The IAB Charter
    - who should approve this charter and its changes?
      the ISOC? the ISOC BOT? the IETF plenary? 
    - how? 
2.7 IAB Liability
    - any specific liability and insurance?
2.8 Funding
    - who will pay this activity?
    - who cares the accountability of all fundings?
2.9 Openness and Confidentiality
    - same as current 1601bis

3. IAB Membership and Selection
3.1 General
    - serve as individuals, non vendor's constituencies,
      but what about the liaisons and the Ex-Officios?
3.2 Fully Voting Members
    - 6/6 members for 2 years, see BCP-10.
3.3 IESG/IETF Chair
    - vote except for IESG related issues, appeals, et.al.
3.4 Ex-Officio Members
    - can be held by voting members
    - IRTF chair
    - IAB ExecDir
3.5 Liaisons
    - can not be held by voting members
    - Internet Society
    - RFC-Editor
    - IESG

4. The Role of the IAB in more detail
4.1 IESG Appointment
    - follow BCP-10
    - should have a separated charter
4.4 IRTF chair Appointment
    - follow BCP-8
4.2 RFC Series
    - its Appointment?
    - should have a separated charter    
    - no free lunch lah, someone has to pay this expensive 
      activity, but who?
4.3 IANA
    - its Appointment?
    - how is this related with ICANN?
    - who pays for this?
4.4 Appeal Process
    - openness
    - do the the party have to pay the plenary attending fee?
    - can it be done electronically, by email, chat, teleconference?
    - who will be to underwriter of this potential expensive activity?
    - how and who will handle an appeal to the IAB itself?
4.5 Appointing Liaisons
    - liaison to the IETF?
    - liaison to the ISOC?
    - liaison to ICANN PSO?
4.6 Organizing Ad-Hoc Committees
4.7 Signing Treaties
    - don't let the IESG sign treaties and MoUs, including IPR licenses.
4.8 General Oversight
    - advice to the ISOC
    - advice to the IESG re. BOF, charting new WGs.
      * Perhaps BCP-25 should deleted the term "advice from the IAB" 
        in which the IESG is perhaps not interested anyway?
        replace it with an ordinary "WG creating Last Call"?
    - how to solicit input from the community
    - how to inform the community
4.10 Accountability Oversight
    - who is taking care the funding of RFC-ed, IANA, and IETF-sec?
    - how to audit it?
4.11 Resolve issues which can not be treated within the IETF/IRTF
   - this point was in RFC 1160, but disappeared after
   - let the IESG to do want it want to do, and let the IAB do what 
     the IESG does do anyway (e.g. handling RFC-2050/BCP-12).
   - who is taking care of the IETF-SEC budget and accountability?

5. Differences and Brief Historical Backgrounds
   - compared with the prior Charter
   - refer to RFC-1160 for historical details

6. Acknowledgments
   - include a list of all prior IAB's chairs

7. References
   - BCP 8
   - BCP 9
   - BCP 10
   - RFC 1160
   - RFC 1336
   - RFC 1358
   - RFC 1601

#include <Standard_BCP-9_Footers.h>


-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- PCI Bus, VESA-L Bus, ISA Bus, VME Bus, S100 Bus, Charlotte 71 Bus



From owner-ietf-outbound@ietf.org  Sat Jan 29 01:15:20 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05743
	for <ietf-web-archive@odin.ietf.org>; Sat, 29 Jan 2000 01:15:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA18941;
	Sat, 29 Jan 2000 01:13:07 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id BAA05383
	for ietf-outbound.10@ietf.org; Sat, 29 Jan 2000 01:10:03 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05110
	for <ietf@ietf.org>; Sat, 29 Jan 2000 01:06:34 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id OAA52468;
	Sat, 29 Jan 2000 14:06:47 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38928323.6DF08264@oke.com>
Date: Sat, 29 Jan 2000 14:05:23 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
CC: isoc@isoc.org
Subject: 1601bis: The Charter of IAB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

To Whom It May Concern

Re: Last Call: Charter of the Internet Architecture Board (IAB) to BCP

> 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 February 9, 2000.

> Files can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-iab-rfc1601bis-02.txt


General

1. Why should the IESG approve the charter? Why not the ISOC?
2. There is no clear statement about the relationship between
   ISOC and IAB. Why?
3. There is no clear statement about relationship with RFC-Editor, 
   IESG, IETF-Sec, IANA, and ICANN. Why?

Accountability

4. As the community is not only exclusively the IETF anymore, 
   what does really "on behalf of the Internet Community" mean?
   What measurement will be used? Will the IAB publish at least
   an annual "progress report"? What/Where is the replacement of
   what IAB previously reported in the IMR?

5. How will the IAB implement "own choosing" of BCP-9:
   "The IAB shall then review the situation and attempt to resolve 
   it in a manner of its OWN CHOOSING."
   See also BCP-9:
   6.5  Conflict Resolution and Appeals
   6.5.1 Working Group Disputes
   6.5.2 Process Failures
   6.5.3 Questions of Applicable Procedure
   See also BCP-11:
   3.6  Internet Architecture Board
   3.7  Internet Assigned Numbers Authority

6. What should the IAB/ISOC do, if the IESG signs a treaty without 
   having a Last Call?



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

Enclosed is my suggested framework of 1601bis


#include <Standard_BCP-9_Headers.h>

1. The Role of the IAB
   - a brief description of the IAB
     * why it is chartered
     * by whom
     * for what
     * some other brief blah-blah-blahs.

2. Organizational Issues
2.1 The IAB chair
2.2 The ExecDir
2.3 The Current Task Forces (Arm?)
    - IRTF
    - IETF
2.4 Voting Rule
2.5 Archiving
    - directory: announcement, appeal, minutes
    - prior cases: e.g. Crocker vs. IESG(1995), Simpson vs. IESG(1999).
    - hall of fame: prior IAB members, etc.
    - who is the holder of zone iab.org, iana.org, ietf.org, and
      rfc-editors.org ?
    - etc.
2.6 The IAB Charter
    - who should approve this charter and its changes?
      the ISOC? the ISOC BOT? the IETF plenary? 
    - how? 
2.7 IAB Liability
    - any specific liability and insurance?
2.8 Funding
    - who will pay this activity?
    - who cares the accountability of all fundings?
2.9 Openness and Confidentiality
    - same as current 1601bis

3. IAB Membership and Selection
3.1 General
    - serve as individuals, non vendor's constituencies,
      but what about the liaisons and the Ex-Officios?
3.2 Fully Voting Members
    - 6/6 members for 2 years, see BCP-10.
3.3 IESG/IETF Chair
    - vote except for IESG related issues, appeals, et.al.
3.4 Ex-Officio Members
    - can be held by voting members
    - IRTF chair
    - IAB ExecDir
3.5 Liaisons
    - can not be held by voting members
    - Internet Society
    - RFC-Editor
    - IESG

4. The Role of the IAB in more detail
4.1 IESG Appointment
    - follow BCP-10
    - should have a separated charter
4.4 IRTF chair Appointment
    - follow BCP-8
4.2 RFC Series
    - its Appointment?
    - should have a separated charter    
    - no free lunch lah, someone has to pay this expensive 
      activity, but who?
4.3 IANA
    - its Appointment?
    - how is this related with ICANN?
    - who pays for this?
4.4 Appeal Process
    - openness
    - do the the party have to pay the plenary attending fee?
    - can it be done electronically, by email, chat, teleconference?
    - who will be to underwriter of this potential expensive activity?
    - how and who will handle an appeal to the IAB itself?
4.5 Appointing Liaisons
    - liaison to the IETF?
    - liaison to the ISOC?
    - liaison to ICANN PSO?
4.6 Organizing Ad-Hoc Committees
4.7 Signing Treaties
    - don't let the IESG sign treaties and MoUs, including IPR licenses.
4.8 General Oversight
    - advice to the ISOC
    - advice to the IESG re. BOF, charting new WGs.
      * Perhaps BCP-25 should deleted the term "advice from the IAB" 
        in which the IESG is perhaps not interested anyway?
        replace it with an ordinary "WG creating Last Call"?
    - how to solicit input from the community
    - how to inform the community
4.10 Accountability Oversight
    - who is taking care the funding of RFC-ed, IANA, and IETF-sec?
    - how to audit it?
4.11 Resolve issues which can not be treated within the IETF/IRTF
   - this point was in RFC 1160, but disappeared after
   - let the IESG to do want it want to do, and let the IAB do what 
     the IESG does do anyway (e.g. handling RFC-2050/BCP-12).
   - who is taking care of the IETF-SEC budget and accountability?

5. Differences and Brief Historical Backgrounds
   - compared with the prior Charter
   - refer to RFC-1160 for historical details

6. Acknowledgments
   - include a list of all prior IAB's chairs

7. References
   - BCP 8
   - BCP 9
   - BCP 10
   - RFC 1160
   - RFC 1336
   - RFC 1358
   - RFC 1601

#include <Standard_BCP-9_Footers.h>


-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- PCI Bus, VESA-L Bus, ISA Bus, VME Bus, S100 Bus, Charlotte 71 Bus



From owner-ietf-outbound  Sat Jan 29 21:32:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA25397
	for ietf-outbound.10@ietf.org; Sat, 29 Jan 2000 21:30:02 -0500 (EST)
Received: from smtp.email.msn.com (cpimssmtpu02.email.msn.com [207.46.181.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25341
	for <ietf@ietf.org>; Sat, 29 Jan 2000 21:21:38 -0500 (EST)
Received: from dean - 63.27.175.89 by email.msn.com with Microsoft SMTPSVC;
	 Sat, 29 Jan 2000 18:21:09 -0800
Message-ID: <000501bf6ac8$761ed9c0$0100a8c0@dean>
From: "Dean Berntsen" <berncrest1@email.msn.com>
To: <ietf@ietf.org>
Subject: how the hell do I unsubscribe to msn
Date: Sat, 29 Jan 2000 18:19:33 -0800
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







From owner-ietf-outbound@ietf.org  Sat Jan 29 21:34:08 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25508
	for <ietf-web-archive@odin.ietf.org>; Sat, 29 Jan 2000 21:34:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA21244;
	Sat, 29 Jan 2000 21:32:22 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA25397
	for ietf-outbound.10@ietf.org; Sat, 29 Jan 2000 21:30:02 -0500 (EST)
Received: from smtp.email.msn.com (cpimssmtpu02.email.msn.com [207.46.181.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25341
	for <ietf@ietf.org>; Sat, 29 Jan 2000 21:21:38 -0500 (EST)
Received: from dean - 63.27.175.89 by email.msn.com with Microsoft SMTPSVC;
	 Sat, 29 Jan 2000 18:21:09 -0800
Message-ID: <000501bf6ac8$761ed9c0$0100a8c0@dean>
From: "Dean Berntsen" <berncrest1@email.msn.com>
To: <ietf@ietf.org>
Subject: how the hell do I unsubscribe to msn
Date: Sat, 29 Jan 2000 18:19:33 -0800
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







From owner-ietf-outbound  Sun Jan 30 01:43:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA01508
	for ietf-outbound.10@ietf.org; Sun, 30 Jan 2000 01:40:03 -0500 (EST)
Received: from black-ice.cc.vt.edu (black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01376
	for <ietf@ietf.org>; Sun, 30 Jan 2000 01:36:48 -0500 (EST)
Received: from black-ice.cc.vt.edu (LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta12/8.10.0.Beta12) with ESMTP id e0U6agU17620;
	Sun, 30 Jan 2000 01:36:42 -0500
Message-Id: <200001300636.e0U6agU17620@black-ice.cc.vt.edu>
To: Dean Berntsen <berncrest1@email.msn.com>
cc: ietf@ietf.org
Subject: Re: how the hell do I unsubscribe to msn 
In-reply-to: Your message of "Sat, 29 Jan 2000 18:19:33 PST."
             <000501bf6ac8$761ed9c0$0100a8c0@dean> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <000501bf6ac8$761ed9c0$0100a8c0@dean>
Date: Sun, 30 Jan 2000 01:36:41 -0500

On Sat, 29 Jan 2000 18:19:33 PST, Dean Berntsen <berncrest1@email.msn.com>  said:

(how to unsubscribe from msn).

This is not an issue for the IETF.  I do believe however that the
Department of Justice has some activity at the moment regarding the
way Microsoft is difficult to disloge from your machine once it gets
a foothold on it.

Or you could first try calling the MSN customer service line
and discussing the situation with them....
--
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound@ietf.org  Sun Jan 30 01:45:15 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01842
	for <ietf-web-archive@odin.ietf.org>; Sun, 30 Jan 2000 01:45:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA03661;
	Sun, 30 Jan 2000 01:43:27 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id BAA01508
	for ietf-outbound.10@ietf.org; Sun, 30 Jan 2000 01:40:03 -0500 (EST)
Received: from black-ice.cc.vt.edu (black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01376
	for <ietf@ietf.org>; Sun, 30 Jan 2000 01:36:48 -0500 (EST)
Received: from black-ice.cc.vt.edu (LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta12/8.10.0.Beta12) with ESMTP id e0U6agU17620;
	Sun, 30 Jan 2000 01:36:42 -0500
Message-Id: <200001300636.e0U6agU17620@black-ice.cc.vt.edu>
To: Dean Berntsen <berncrest1@email.msn.com>
cc: ietf@ietf.org
Subject: Re: how the hell do I unsubscribe to msn 
In-reply-to: Your message of "Sat, 29 Jan 2000 18:19:33 PST."
             <000501bf6ac8$761ed9c0$0100a8c0@dean> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <000501bf6ac8$761ed9c0$0100a8c0@dean>
Date: Sun, 30 Jan 2000 01:36:41 -0500

On Sat, 29 Jan 2000 18:19:33 PST, Dean Berntsen <berncrest1@email.msn.com>  said:

(how to unsubscribe from msn).

This is not an issue for the IETF.  I do believe however that the
Department of Justice has some activity at the moment regarding the
way Microsoft is difficult to disloge from your machine once it gets
a foothold on it.

Or you could first try calling the MSN customer service line
and discussing the situation with them....
--
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Mon Jan 31 19:22:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA18827
	for ietf-outbound.10@ietf.org; Mon, 31 Jan 2000 19:20:03 -0500 (EST)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18787
	for <ietf@ietf.org>; Mon, 31 Jan 2000 19:15:04 -0500 (EST)
Received: (from hta@localhost)
	by dokka.maxware.no (8.9.3/8.9.3) id BAA03582
	for ietf@ietf.org; Tue, 1 Feb 2000 01:15:03 +0100
Date: Tue, 1 Feb 2000 01:15:03 +0100
From: Harald Tveit Alvestrand <hta@dokka.maxware.no>
Message-Id: <200002010015.BAA03582@dokka.maxware.no>
To: ietf@ietf.org
Subject: FAQ: The IETF+Censored list


                        The IETF+Censored mailing list
                                       
   At times, the IETF list is subject to debates that have little to do
   with the purposes for which the IETF list was created. Some people
   would appreciate a "quieter" forum for the relevant debates that take
   place, but the IETF's policy of openness has so far prevented the IETF
   from imposing any censorship policy on the IETF@ietf.org list.
   
   To give people an alternative, there is a list called
   "ietf+censored@alvestrand.no".
   
   This list is a sublist (that is, it gets the same messages as) the
   open IETF discussion list. However, this list will not forward all
   messages; in particular, the filters have been set so that persons and
   discussions that are, in the view of Harald Alvestrand, irrelevant to
   the IETF list are not forwarded.
   
   Because this filter is automated, the criteria include:
     * Well known troublemakers
     * Well known crosspostings
     * Subjects that have led to recent non-conclusive exchanges
     * Some ways to say "unsubscribe"
       
   To join the list, [1]send the word "subscribe" in the BODY of a
   message to ietf+censored-request@alvestrand.no (the URL here is an RFC
   2368 mailto URL that does the Right Thing).
   
   For fun, there is a special list for the rejected messages:
   ietf+censored-rejects@alvestrand.no - subscribe in the same fashion,
   by [2]mail to ietf+censored-rejects-request@alvestrand.no
   
   By public request, the current set of filters are listed at
   [3]http://www.alvestrand.no/cgi-bin/hta/ietf+censored-filters
   
   Some statistics on postings, which may be useful in getting a
   perspective on the effects of the filter, are at
   [4]posting-counts.html (started Oct 14, 1998).
   
   This page is http://www.alvestrand.no/ietf+censored.html, and is
   posted monthly in text form to ietf@ietf.org
     _________________________________________________________________
   
   Harald Tveit Alvestrand [5]< Harald@Alvestrand.no>

References

   1. mailto:ietf+censored-request@alvestrand.no?body=subscribe
   2. mailto:ietf+censored-rejects-request@alvestrand.no?body=subscribe
   3. http://www.alvestrand.no/cgi-bin/hta/ietf+censored-filters
   4. http://www.alvestrand.no/posting-counts.html
   5. mailto:harald@alvestrand.no



From owner-ietf-outbound@ietf.org  Mon Jan 31 19:24:22 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18899
	for <ietf-web-archive@odin.ietf.org>; Mon, 31 Jan 2000 19:24:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA25173;
	Mon, 31 Jan 2000 19:21:58 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA18827
	for ietf-outbound.10@ietf.org; Mon, 31 Jan 2000 19:20:03 -0500 (EST)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18787
	for <ietf@ietf.org>; Mon, 31 Jan 2000 19:15:04 -0500 (EST)
Received: (from hta@localhost)
	by dokka.maxware.no (8.9.3/8.9.3) id BAA03582
	for ietf@ietf.org; Tue, 1 Feb 2000 01:15:03 +0100
Date: Tue, 1 Feb 2000 01:15:03 +0100
From: Harald Tveit Alvestrand <hta@dokka.maxware.no>
Message-Id: <200002010015.BAA03582@dokka.maxware.no>
To: ietf@ietf.org
Subject: FAQ: The IETF+Censored list


                        The IETF+Censored mailing list
                                       
   At times, the IETF list is subject to debates that have little to do
   with the purposes for which the IETF list was created. Some people
   would appreciate a "quieter" forum for the relevant debates that take
   place, but the IETF's policy of openness has so far prevented the IETF
   from imposing any censorship policy on the IETF@ietf.org list.
   
   To give people an alternative, there is a list called
   "ietf+censored@alvestrand.no".
   
   This list is a sublist (that is, it gets the same messages as) the
   open IETF discussion list. However, this list will not forward all
   messages; in particular, the filters have been set so that persons and
   discussions that are, in the view of Harald Alvestrand, irrelevant to
   the IETF list are not forwarded.
   
   Because this filter is automated, the criteria include:
     * Well known troublemakers
     * Well known crosspostings
     * Subjects that have led to recent non-conclusive exchanges
     * Some ways to say "unsubscribe"
       
   To join the list, [1]send the word "subscribe" in the BODY of a
   message to ietf+censored-request@alvestrand.no (the URL here is an RFC
   2368 mailto URL that does the Right Thing).
   
   For fun, there is a special list for the rejected messages:
   ietf+censored-rejects@alvestrand.no - subscribe in the same fashion,
   by [2]mail to ietf+censored-rejects-request@alvestrand.no
   
   By public request, the current set of filters are listed at
   [3]http://www.alvestrand.no/cgi-bin/hta/ietf+censored-filters
   
   Some statistics on postings, which may be useful in getting a
   perspective on the effects of the filter, are at
   [4]posting-counts.html (started Oct 14, 1998).
   
   This page is http://www.alvestrand.no/ietf+censored.html, and is
   posted monthly in text form to ietf@ietf.org
     _________________________________________________________________
   
   Harald Tveit Alvestrand [5]< Harald@Alvestrand.no>

References

   1. mailto:ietf+censored-request@alvestrand.no?body=subscribe
   2. mailto:ietf+censored-rejects-request@alvestrand.no?body=subscribe
   3. http://www.alvestrand.no/cgi-bin/hta/ietf+censored-filters
   4. http://www.alvestrand.no/posting-counts.html
   5. mailto:harald@alvestrand.no



