From owner-ietf-outbound  Sat Jul  1 01:01:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA04398
	for ietf-outbound.10@ietf.org; Sat, 1 Jul 2000 01:00:03 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04343
	for <ietf@ietf.org>; Sat, 1 Jul 2000 00:55:55 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007010450.NAA08421@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id NAA08421; Sat, 1 Jul 2000 13:50:04 +0900
Subject: Re: Is WAP mobile Internet??
In-Reply-To: <395D442D.C506FEEA@msdw.com> from Renfield Kuroda at "Jul 1, 2000
 10:06:54 am"
To: Renfield Kuroda <Renfield.Kuroda@msdw.com>
Date: Sat, 1 Jul 2000 13:50:04 +0859 ()
CC: "ietf@ietf.org" <ietf@ietf.org>
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

r e n;

> I don't think WAP Mobile Internet any more than TCP/IP is Internet.

There is no such thing as WAP Mobile Internet.

> The Mobile Internet is data/communication devices you carry around with you.
> 
> Here in Japan we have 8 million non-WAP mobile internet users, plus another 2
> million WAP users, and the numbers are exploding.

They are no internet users.

Just as the Internet was not e-mail several years ago when e-mail was
the most popular application, the Internet is not web.

> But, and I know this may be the wrong mailing list for this comment,

No. It is merely that your understanding on the Internet is wrong in
any mailing list.

							Masataka Ohta



From owner-ietf-outbound  Sun Jul  2 00:22:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA26120
	for ietf-outbound.10@ietf.org; Sun, 2 Jul 2000 00:20:02 -0400 (EDT)
Received: from syd-exch1.magna.com.au (syd-exch1.magna.com.au [203.111.99.23])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26093
	for <ietf@ietf.org>; Sun, 2 Jul 2000 00:18:46 -0400 (EDT)
Received: by syd-exch1.magna.com.au with Internet Mail Service (5.5.2650.21)
	id <N2Y3TNVB>; Sun, 2 Jul 2000 14:23:58 +1000
Message-ID: <4DD6239844F3D311A198009027FC4210AE85C5@syd-exch1.magna.com.au>
From: Phillip Grasso-Nguyen <Phillip.Grasso@magna.com.au>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Cc: "'xipeng@gblx.net'" <xipeng@gblx.net>, "'alan@ivmg.net'"
	 <alan@ivmg.net>,
        "'edc@explosive.net'" <edc@explosive.net>,
        "'vern@aciri.org'" <vern@ACIRI.ORG>
Subject: RFC2873 manually setting precedence.
Date: Sun, 2 Jul 2000 14:23:52 +1000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Hi,

Since most DSCP and QoS functions are normally handled within a single
network domain, what impact would it have to manually set precedence at the
edge.

for example,
CE = customer edge, or host systems (TCP endpoints)
PE = Provider edge,
P   = Provider Core, 

CE - PE - P - PE - CE

If the provider PE edge manually sets the precedence outbound to the CE what
affect will this have on the TCP session.
the TCP RST condition should happen when their is a ["lower precedence" or
any change in precedence] if both ends where set to the same precedence by
the PE router for example precedence or dscp of "0". Does tcp security have
a specific requirement of precedence, what happens if the tcp stack
initiates a connection with a precedence of 1 and during transmission it
gets reassigned with precedence of "0" does this screw the TCP
session/connection? is manually setting precedence or DSCP to the a single
value outbound to the CE or TCP endpoints a possible work around?

Regards
	Phillip.

********************************************
Phillip Grasso-Nguyen (CCNA)
Senior Network Engineer - Core Engineering Team
Davnet Telecommunications
Level 7, Magna Data House
209 Castlereagh Street, Sydney
NSW, Australia, 2000.
Tel: +61 2 9272 9600 Fax: +61 2 9272 9605
mailto:phillipg@magna.com.au
http://www.magna.com.au
PGP Fingerprint:1083 7987 D33A C7E8 5DB2  AAD2 4F5D 6B99 CBB7 55A4
PGP Key: http://www.magna.com.au/~phillipg/phillipg.asc
Australian General Telecommunications Carrier License No 23
********************************************
Disclaimer: http://www.magna.com.au/~phillipg/disclaimer.txt
"Leave complexity at the 'edges' and keep the network 'core' simple" 



From owner-ietf-outbound  Sun Jul  2 15:03:02 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA09426
	for ietf-outbound.10@ietf.org; Sun, 2 Jul 2000 15:00:02 -0400 (EDT)
Received: from pefw00 ([209.172.73.242])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09350
	for <ietf@ietf.org>; Sun, 2 Jul 2000 14:44:13 -0400 (EDT)
Received: from pimx00.ivmg.net (pimx00.ivmg.net [192.168.0.10])
	by pefw00 (8.10.1/8.10.1) with ESMTP id e62IhN118052;
	Sun, 2 Jul 2000 18:43:23 GMT
Received: (from alan@localhost)
	by pimx00.ivmg.net (8.10.1/8.10.1) id e62IhI400239;
	Sun, 2 Jul 2000 11:43:18 -0700
Date: Sun, 2 Jul 2000 11:43:18 -0700
From: Alan Hannan <alan@ivmg.net>
To: Phillip Grasso-Nguyen <Phillip.Grasso@magna.com.au>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>, "'xipeng@gblx.net'" <xipeng@gblx.net>,
        "'edc@explosive.net'" <edc@explosive.net>,
        "'vern@aciri.org'" <vern@ACIRI.ORG>
Subject: Re: RFC2873 manually setting precedence.
Message-ID: <20000702114318.A198@ivmg.net>
References: <4DD6239844F3D311A198009027FC4210AE85C5@syd-exch1.magna.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <4DD6239844F3D311A198009027FC4210AE85C5@syd-exch1.magna.com.au>; from Phillip.Grasso@magna.com.au on Sun, Jul 02, 2000 at 02:23:52PM +1000
X-Loop: ietf@ietf.org


  Phillip,

> Since most DSCP and QoS functions are normally handled within a single
> network domain, what impact would it have to manually set precedence at the
> edge.
> 
> for example,
> CE = customer edge, or host systems (TCP endpoints)
> PE = Provider edge,
> P   = Provider Core, 
> 
> CE - PE - P - PE - CE

  I'll modify as:

  CE1 -- PE1 -- P -- PE2 -- CE2

> 
> If the provider PE edge manually sets the precedence outbound to the CE what
> affect will this have on the TCP session.

  As I think you know, the primary catalyst for this modification
  was observed operational behaviour.  We saw that when mid-point
  devices [P] changed TOS/DSCP and the observed response packets
  [at CE1] within the TCP session varied, CE1 would reset the packet.

> the TCP RST condition should happen when their is a ["lower precedence" or
> any change in precedence] if both ends where set to the same precedence by
> the PE router 

  Although a viable solution, this is difficult to implement in
  practice.  The need this presents for PE1 and PE2 to synchronize by
  session and policy is great.  I believe this demand would severely
  impede DHCP/TOS and internet deployment.

  Another implementation workaround would maintain state as below,
  but this is only a partial resolution to the problem.

> for example precedence or dscp of "0". Does tcp security have
> a specific requirement of precedence, 

  In practice, no.  Per a strict interpretation of the RFC793, yes.
  We saw that mainly some [10%] of MacTCP (apple) TCP/IP stacks
  enforced this, as well as some old IBM stacks.

> what happens if the tcp stack
> initiates a connection with a precedence of 1 and during transmission it
> gets reassigned with precedence of "0" does this screw the TCP
> session/connection? 

  Yes, because what CE1 sends "1" is changed by {PE1,P,PE2, or CE2}
  and is not what he expected.

> is manually setting precedence or DSCP to the a single
> value outbound to the CE or TCP endpoints a possible work around?

  It might be, except that it either:

  	requires sychnornization by CE's or PE's

  	or

  	disallows tcp-based DSCP delivery.  One could set things to a
  	default value [say, 0] and remember what it got on a
  	flow-by-flow basis.  However, this would negate end-to-end
  	ability of DSCP/TCP; which is certainly a desirable behaviour
  	we do not wish to negate.

   -alan

> 
> Regards
> 	Phillip.
> 
> ********************************************
> Phillip Grasso-Nguyen (CCNA)
> Senior Network Engineer - Core Engineering Team
> Davnet Telecommunications
> Level 7, Magna Data House
> 209 Castlereagh Street, Sydney
> NSW, Australia, 2000.
> Tel: +61 2 9272 9600 Fax: +61 2 9272 9605
> mailto:phillipg@magna.com.au
> http://www.magna.com.au
> PGP Fingerprint:1083 7987 D33A C7E8 5DB2  AAD2 4F5D 6B99 CBB7 55A4
> PGP Key: http://www.magna.com.au/~phillipg/phillipg.asc
> Australian General Telecommunications Carrier License No 23
> ********************************************
> Disclaimer: http://www.magna.com.au/~phillipg/disclaimer.txt
> "Leave complexity at the 'edges' and keep the network 'core' simple" 



From owner-ietf-outbound  Mon Jul  3 07:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA29644
	for ietf-outbound.10@ietf.org; Mon, 3 Jul 2000 07:50:02 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29605
	for <ietf@ietf.org>; Mon, 3 Jul 2000 07:48:43 -0400 (EDT)
Message-Id: <200007031148.HAA29605@ietf.org>
From: The IETF Secretariat <ietf-secretariat@ietf.org>
To: ietf@ietf.org
Subject: IETF List maintenance
Reply-to: ietf-request@ietf.org
Date: Mon, 03 Jul 2000 07:48:43 -0400
Sender: scoya@cnri.reston.va.us
X-Loop: ietf@ietf.org


To remove yourself from the IETF discussion list, send a message to
ietf-request@ietf.org

Enter just the word unsubscribe in the body of the message.

NOTE: List requests do not take effect until the next day, and there
      are always messages in the outbound queue. As such, you may 
      continue receiving messages for a short while after successfully
      unsubscribing from the list.



The IETF discussion list serves two purposes. It furthers the
development and specification of Internet technology through discussion
of technical issues. It also hosts discussions of IETF direction,
policy, and procedures. As this is the most general IETF mailing list,
considerable latitude is allowed. Advertising, whether to solicit
business or promote employment opportunities, falls well outside the
range of acceptable topics, as do discussions of a personal nature.

This list is meant for initial discussion only. Discussions that fall
within the area of any working group or well established list should be
moved to such more specific forum as soon as this is pointed out,
unless the issue is one for which the working group needs wider input
or direction.

In addition to the topics noted above, appropriate postings include: 

o Last Call discussions of proposed protocol actions 
o Discussion of technical issues that are candidates for IETF work, but
  do not yet have an appropriate e-mail venue
o Discussion of IETF administrative policies 
o Questions and clarifications concerning IETF meetings. 

Inappropriate postings include: 
o Unsolicited bulk e-mail 
o Discussion of subjects unrelated to IETF policy, meetings,
  activities, or technical concerns
o Unprofessional commentary, regardless of the general subject. 

The IETF Chair, the IETF Executive Director, or a sergeant-at-arms
appointed by the Chair is empowered to restrict posting by a person or
of a thread as they deem appropriate to limit abuse. Complaints
regarding their decisions should be referred to the IAB <iab@iab.org>



From owner-ietf-outbound  Mon Jul  3 11:30:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA03321
	for ietf-outbound.10@ietf.org; Mon, 3 Jul 2000 11:30:02 -0400 (EDT)
Received: from msw.mimesweeper.com (msw.mimesweeper.com [194.168.90.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03193
	for <ietf@ietf.org>; Mon, 3 Jul 2000 11:24:08 -0400 (EDT)
Received: from BELL.mimesweeper.com (unverified) by msw.mimesweeper.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc2a85a129f4d2e4fd035@msw.mimesweeper.com>;
 Mon, 3 Jul 2000 16:24:24 +0100
Received: from GK-VAIO.Dial.pipex.com (gk-vaio.mimesweeper.com [194.168.90.137]) by BELL.mimesweeper.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id N9HF2RWK; Mon, 3 Jul 2000 16:23:00 +0100
Message-Id: <4.3.2.7.2.20000703150246.0266c890@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 03 Jul 2000 15:57:57 +0100
To: "Anthony Atkielski" <anthony@atkielski.com>
From: Graham Klyne <GK@dial.pipex.com>
Subject: Re: WAP - What A Problem...
Cc: <ietf@ietf.org>
In-Reply-To: <002201bfe2b6$5e68b970$0a00000a@abo.wanadoo.fr>
References: <1287.962382283@cs.ucl.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 07:12 PM 6/30/00 +0200, Anthony Atkielski wrote:
>Why use SMS instead of just voice?
>
>Has anyone considered the ergonomics of WAP?  Even if it works perfectly,
>how many people are willing to work on a screen smaller than a credit card?
>How many people are capable of touch-typing on a keyboard with only ten soft
>keys that must be pressed in various arcane combinations for almost ever
>letter?  It just doesn't make intuitive sense.

On the face of it, I would have tended to agree.

But I have been astonished by the degree of adoption of SMS (in UK) by 
school children who purchase their own pre-pay mobile phones (for about 
$50-100).  SMS may be awkward, but the per-use cost is  is very low, and 
totally predictable.  And the users in this case soon learn to handle the 
"inadequate" user interface.

But it doesn't stop there:  when I travel abroad, my daughter sends SMS 
messages to my mobile phone, and I respond in kind.  And wherever I am in 
the world, the cost does not very.  And even I am finding the user 
interface manageable for simple messages.

Because it's messaging, not isochronous, SMS can ride "low-grade" bandwidth 
that voice cannot use.  I sometimes think the advantages of messaging are 
lost among those who are used to continuous network connections.

#g

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Mon Jul  3 11:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA03549
	for ietf-outbound.10@ietf.org; Mon, 3 Jul 2000 11:40:03 -0400 (EDT)
Received: from msw.mimesweeper.com (msw.mimesweeper.com [194.168.90.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03197
	for <ietf@ietf.org>; Mon, 3 Jul 2000 11:24:09 -0400 (EDT)
Received: from BELL.mimesweeper.com (unverified) by msw.mimesweeper.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc2a85a129f4d2e4fcd3c@msw.mimesweeper.com> for <ietf@ietf.org>;
 Mon, 3 Jul 2000 16:24:23 +0100
Received: from GK-VAIO.Dial.pipex.com (gk-vaio.mimesweeper.com [194.168.90.137]) by BELL.mimesweeper.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id N9HF2RWG; Mon, 3 Jul 2000 16:23:00 +0100
Message-Id: <4.3.1.2.20000626165643.00a805d0@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 03 Jul 2000 12:44:16 +0100
To: IETF Mailing List <ietf@ietf.org>
From: Graham Klyne <GK@dial.pipex.com>
Subject: Re: Seeking Open Mobile Messaging Protocols -- Efficient E-Mail
In-Reply-To: <20000626053311.10599.qmail@tooran.byname.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

In response to a recent request for information about efficient messaging 
protocols, may I refer you to a proposal that has been offered as a 
candidate for IMPP, but which is built on a relay model capable of matching 
and enhancing SMTP transfer semantics:

   http://search.ietf.org/internet-drafts/draft-mrose-imxp-core-00.txt
   http://search.ietf.org/internet-drafts/draft-mrose-imxp-access-00.txt
   http://search.ietf.org/internet-drafts/draft-mrose-blocks-protocol-04.txt

#g
--

At 05:33 AM 6/26/00 +0000, Mohsen BANAN-Public wrote:
>Existing SMTP/IMAP/TCP technology is not well suited for
>mobile and wireless environments where bandwidth and
>capacity are always limited and precious.
>
>
>More efficient protocols are needed to address the new
>reality of mobile and wireless networks. I am seeking
>open protocols which are better suited to address the
>requirements of mobile and wireless networks.
>
>The key functional requirements for the protocols that
>I am seeking are:
>
>  -  Provide for the submission and delivery of short
>     (4 kilobytes or less) Internet e-mail messages
>     with the same level of functionality (or higher)
>     that the existing SMTP protocols provide.
>
>  -  Provide the same (or better) level of reliability
>     and security that the existing SMTP protocols provide.
>
>  -  Make reasonable trade-offs between specification complexity,
>     implementation complexity, extendibility, scalability and efficiency.
>
>  -  Provide the required efficiency characteristics. These include:
>     minimizing the number of transmissions, minimizing the number of
>     bytes transmitted, minimizing the latency of message
>     submission and delivery.
>
>
>The protocols I seek are intended to be used primarily
>in IP based wide area wireless environments (e.g., CDPD)
>The devices used have a wide variety of form factors and
>platforms.
>
>Timely delivery ("push") to unconscious carry devices
>similar to the two-way paging model is also an important
>goal.
>
>The origin of the open protocols that I am seeking can
>be any individual, company, or organization, provided:
>
>   - The protocols are intended to be patent-free and are
>     declared as such.
>
>   - They are published as stable specifications and are
>     readily and permanently available to anyone.
>     RFC publication is the prefered method.
>
>   - Participation in the maintenance and enhancement of the protocols
>     is public, open and free. The maintenance process must
>     also be such as to maintain the patent-free nature of the protocols.
>
>
>The absence of a set of open protocols satisfying these requirements
>has led to the adoption of patented protocols such as WAP, and the
>appearance of closed systems such as BlackBerry (tm).
>
>I consider the availability of open alternatives in this
>area to be of benefit to the consumer and the industry.
>
>
>If you are aware of any protocol specifications which
>address the above mentioned requirements please send me
>--
>     Mohsen BANAN  mailto:public@mohsen.banan.1.byname.net
>--
>a note. I will compile the results, then make publicly available.
>
>Please feel free to distribute this request wherever appropriate.
>
>
>Thank you.
>
>Mohsen BANAN
>
>-
>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.

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Mon Jul  3 11:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA03717
	for ietf-outbound.10@ietf.org; Mon, 3 Jul 2000 11:50:03 -0400 (EDT)
Received: from mail-server-6.star.net.uk (mail-server-6.star.net.uk [195.216.16.176])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03683
	for <ietf@ietf.org>; Mon, 3 Jul 2000 11:49:12 -0400 (EDT)
X-VirusChecked: Checked
Received: (qmail 13009 invoked from network); 3 Jul 2000 15:47:50 -0000
Received: from dynamic3-96.star.co.uk (HELO chevin?nt.chevin) (212.125.92.96)
  by mail-server-6.star.net.uk with SMTP; 3 Jul 2000 15:47:50 -0000
Received: by chevin_nt.chevin.com with Internet Mail Service (5.5.2448.0)
	id <3BR20079>; Mon, 3 Jul 2000 16:38:11 +0100
Message-ID: <D05C92AB7BD9D311B79D0060080C139ACAE3@chevin_nt.chevin.com>
From: Phil Snell <phils@chevin.com>
To: "'Graham Klyne'" <GK@dial.pipex.com>,
        Anthony Atkielski
	 <anthony@atkielski.com>
Cc: ietf@ietf.org
Subject: RE: WAP - What A Problem...
Date: Mon, 3 Jul 2000 16:38:04 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Loop: ietf@ietf.org


> But I have been astonished by the degree of adoption of SMS (in UK) by 
> school children who purchase their own pre-pay mobile phones (for about 
> $50-100).  SMS may be awkward, but the per-use cost is  is very low, and 
> totally predictable.  And the users in this case soon learn to handle the 
> "inadequate" user interface.
> 
I have to agree, my daughter can type at astonishing speed on her cell phone
- it is a good way for me to keep in touch with her
P.

________________________________________________________________________
This message has been checked for all known viruses, by Star Internet, 
delivered through the MessageLabs Virus Control Centre. 
For further information visit:
http://www.star.net.uk/stats.asp



From owner-ietf-outbound  Tue Jul  4 13:52:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA29468
	for ietf-outbound.10@ietf.org; Tue, 4 Jul 2000 13:50:02 -0400 (EDT)
Received: from hqvsbh1.ms.com (hqvsbh1.ms.com [205.228.12.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29421
	for <ietf@ietf.org>; Tue, 4 Jul 2000 13:43:04 -0400 (EDT)
Received: (from uucp@localhost)
        by hqvsbh1.ms.com (8.9.3/fw v1.30) id NAA25717;
        Tue, 4 Jul 2000 13:43:03 -0400 (EDT)
Received: from localhost(127.0.0.1) by hqvsbh1 via smap (4.1)
	id sma.9627325751.025642; Tue, 4 Jul 00 13:42:55 -0400
Received: (from uucp@localhost)
	by hqvsbh1.ms.com (8.9.3/8.9.3(vs)) id NAA25631;
	Tue, 4 Jul 2000 13:42:54 -0400 (EDT)
X-Authentication-Warning: hqvsbh1.ms.com: Processed from queue /var/spool/mqueue-vs
X-Authentication-Warning: hqvsbh1.ms.com: Processed by uucp with -C /etc/mail/sendmail.vs.cf
Received: from ebsmh2.ms.com(161.144.69.74) by hqvsbh1 via smap (4.1)
	id sma.9627325671.025500; Tue, 4 Jul 00 13:42:47 -0400
Received: from msdw.com (eqtk99.morgan.com [205.228.79.99])
        by ebsmh2.ms.com (8.8.5/imap+ldap v2.4) with ESMTP id CAA24769;
        Wed, 5 Jul 2000 02:42:43 +0900 (JST)
Message-ID: <396221E7.B4DF4EF9@msdw.com>
Date: Wed, 05 Jul 2000 02:41:59 +0900
From: Renfield Kuroda <Renfield.Kuroda@msdw.com>
Reply-To: Renfield.Kuroda@msdw.com
Organization: Morgan Stanley Dean Witter & Co.
X-Mailer: Mozilla 4.7 [ja]C-CCK-MCD   (WinNT; I)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: Graham Klyne <GK@DIAL.PIPEX.COM>, ietf@ietf.org
Subject: Re: WAP - What A Problem...
References: <1287.962382283@cs.ucl.ac.uk> <4.3.2.7.2.20000703150246.0266c890@pop.dial.pipex.com>
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Graham Klyne wrote:

> At 07:12 PM 6/30/00 +0200, Anthony Atkielski wrote:
> >Why use SMS instead of just voice?
> >
> >Has anyone considered the ergonomics of WAP?  Even if it works perfectly,
> >how many people are willing to work on a screen smaller than a credit card?

Well, 10 million Japanese, and growing by 20,000 every DAY.

>
> >How many people are capable of touch-typing on a keyboard with only ten soft
> >keys that must be pressed in various arcane combinations for almost ever
> >letter?  It just doesn't make intuitive sense.

In Japan email and SMS traffic is outstripping voice calls. The number of SMS
and/or emails (in Japan the difference between email and SMS is prtty much
transparent) is growing more rapidly than cell phone penetration and voice calls.

In fact, chat rooms, realtime chat, and message boards are also very popular now,
too.

Regards,

r e n




From owner-ietf-outbound  Tue Jul  4 15:00:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA29984
	for ietf-outbound.10@ietf.org; Tue, 4 Jul 2000 15:00:02 -0400 (EDT)
Received: from zrtps06s.us.nortel.com ([47.140.48.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29944
	for <ietf@ietf.org>; Tue, 4 Jul 2000 14:58:29 -0400 (EDT)
Received: from zrtpd004.us.nortel.com by zrtps06s.us.nortel.com;
          Tue, 4 Jul 2000 14:57:16 -0400
Received: by zrtpd004.us.nortel.com with Internet Mail Service (5.5.2650.21) 
          id <NQCAXKF8>; Tue, 4 Jul 2000 14:57:16 -0400
Message-ID: <456E6DB7180ED3118A670000F8BDCA29021BB079@zcard00p.ca.nortel.com>
From: "Glenn Parsons" <gparsons@nortelnetworks.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: FW: DELIVERY FAILURE: User socialevent (socialevent@marconi.com) not 
         listed in public Name & Address Book
Date: Tue, 4 Jul 2000 14:57:06 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01BFE5E9.ABC2692E"
X-Orig: <gparsons@americasm01.nt.com>
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFE5E9.ABC2692E
Content-Type: text/plain

Folks,

I just tried to send a message to Marconi (to the address indicated on the
IETF 48 social site) querying about tax being charged on the social event
when you reserve on the website.  I received the following NDN.

Has anyone else tried this address?

Thanks,
Glenn.

> ----------
> From: 	Postmaster@marconi.com
> Sent: 	Tuesday, July 4, 2000 2:35 pm
> To: 	Parsons, Glenn 
> Subject: 	DELIVERY FAILURE: User socialevent (socialevent@marconi.com)
> not  listed in public Name & Address Book
> 
> Your message
> 
>   Subject: IETF social fee
> 
> was not delivered to:
> 
>   socialevent@marconi.com
> 
> because:
> 
>   User socialevent (socialevent@marconi.com) not listed in public Name &
> Address Book
> 
> 
> 

------_=_NextPart_001_01BFE5E9.ABC2692E
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2651.65">
<TITLE>FW: DELIVERY FAILURE: User socialevent (socialevent@marconi.com) =
not  listed in public Name &amp; Address Book</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Folks,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">I just tried to send a =
message to Marconi (to the address indicated on the IETF 48 social =
site) querying about tax being charged on the social event when you =
reserve on the website.&nbsp; I received the following NDN.</FONT></P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Has anyone else tried this =
address?</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Thanks,</FONT>
<BR><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Glenn.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Geneva">----------</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Geneva">From:</FONT></B> &nbsp; <FONT =
SIZE=3D2 FACE=3D"Geneva">Postmaster@marconi.com</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Geneva">Sent:</FONT></B> &nbsp; <FONT =
SIZE=3D2 FACE=3D"Geneva">Tuesday, July 4, 2000 2:35 pm</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Geneva">To:</FONT></B> &nbsp;&nbsp;&nbsp; =
<FONT SIZE=3D2 FACE=3D"Geneva">Parsons, Glenn </FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Geneva">Subject:</FONT></B> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Geneva">DELIVERY FAILURE: User socialevent =
(socialevent@marconi.com) not&nbsp; listed in public Name &amp; Address =
Book</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Monaco">Your message</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Monaco">&nbsp; Subject: IETF social =
fee</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Monaco">was not delivered to:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Monaco">&nbsp; socialevent@marconi.com</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Monaco">because:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Monaco">&nbsp; User socialevent =
(socialevent@marconi.com) not listed in public Name &amp; Address =
Book</FONT>
</P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01BFE5E9.ABC2692E--



From owner-ietf-outbound  Tue Jul  4 18:50:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA01198
	for ietf-outbound.10@ietf.org; Tue, 4 Jul 2000 18:50:02 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01141
	for <ietf@ietf.org>; Tue, 4 Jul 2000 18:40:59 -0400 (EDT)
Received: from AStLambert101214 (ASt-Lambert-101-2-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.8.8) id AAA27926; Wed, 5 Jul 2000 00:40:58 +0200 (CEST)
Message-ID: <020b01bfe608$ec222210$0a00000a@abo.wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <1287.962382283@cs.ucl.ac.uk> <4.3.2.7.2.20000703150246.0266c890@pop.dial.pipex.com> <396221E7.B4DF4EF9@msdw.com>
Subject: Re: WAP - What A Problem...
Date: Wed, 5 Jul 2000 00:40:57 +0200
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
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> Well, 10 million Japanese, and growing by 20,000 every DAY.

Only 100 million more to go.

The Japanese, however, have a passion for highly miniaturized gadgets, so
I'm not sure that they are representative.

Personally, I don't even have a laptop, mainly because I find laptops so
incredibly clumsy to use, with their tiny keyboards and bizarre mouse
substitutes and what-not.

> In Japan email and SMS traffic is outstripping
> voice calls.

E-mail via what type of computer or terminal?





From owner-ietf-outbound  Tue Jul  4 21:30:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA01955
	for ietf-outbound.10@ietf.org; Tue, 4 Jul 2000 21:30:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01906
	for <ietf@ietf.org>; Tue, 4 Jul 2000 21:22:04 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id TAA25618
	for ietf@ietf.org  env-from <vjs>;
	Tue, 4 Jul 2000 19:22:04 -0600 (MDT)
Date: Tue, 4 Jul 2000 19:22:04 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007050122.TAA25618@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: WAP - What A Problem...
X-Loop: ietf@ietf.org

> > Well, 10 million Japanese, and growing by 20,000 every DAY.
>
> Only 100 million more to go.
>
> The Japanese, however, have a passion for highly miniaturized gadgets, so
> I'm not sure that they are representative.
>
> Personally, I don't even have a laptop, mainly because I find laptops so
> incredibly clumsy to use, with their tiny keyboards and bizarre mouse
> substitutes and what-not.
> ...

The recent reports have concerned email and similar small text messages.
Pure email is very different from the world wide superhypeway web.  I
value email far higher than the WWW, perhaps because I've been receiving
email as "vjs" since the 1960's.  However, even I doubt that the telephants
would have jumped on the WAP bandwagon if WAP were intended merely as
competition for the alphanumeric or "chatty" paging services common at
least in Silicon Valley since the early 1990's, and now commonly two-way.

If you are only using your cell phone screen for text messages, why
do you need WAP?  I doubt even the WAP enthusiasts would claim that
14 kbit/sec is very a low speed or that radio telephones have
terrible BER's for moving tiny, text-only messages.

The notion that WAP will be only ever be used for tiny, text only
messages sounds likely to me, but doesn't put WAP enthusiasts in
a good light and shouldn't please their stockholders.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Wed Jul  5 03:40:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA18253
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 03:40:02 -0400 (EDT)
Received: from mex.italtel.it ([138.132.117.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18224
	for <ietf@ietf.org>; Wed, 5 Jul 2000 03:35:25 -0400 (EDT)
Received: .(iltws72 [138.132.52.82]) by mex.italtel.it (8.9.0/8.9.0) with ESMTP id JAA19004
Received: .(localhost [127.0.0.1]) by iltws72.settimo.italtel.it (8.9.1a/8.9.1) with ESMTP
 id JAA18358
Received: from ic8u32.settimo.italtel.it (ic8u32.settimo.italtel.it [138.132.1.1])
	by mix.italtel.it (8.9.3/8.9.3) with SMTP id JAA27412;
	Wed, 5 Jul 2000 09:31:52 +0200 (MET DST)
Received: by ic8u32.settimo.italtel.it id AA04710; Wed, 5 Jul 2000 09:54:59 +0200
Received: from icn.siemens.it (localhost [127.0.0.1])
	by iltws09.settimo.italtel.it (8.10.1/8.10.1) with ESMTP id e657aFt01896;
	Wed, 5 Jul 2000 09:36:16 +0200 (MET DST)
Sender: buschman@iltws09.settimo.italtel.it
Message-Id: <3962E56C.D50419A9@icn.siemens.it>
Date: Wed, 05 Jul 2000 09:36:13 +0200
From: Jonathan Buschmann <Jonathan.Buschmann@icn.siemens.it>
Reply-To: Jonathan.Buschmann@icn.siemens.it
X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
Mime-Version: 1.0
To: Glenn Parsons <gparsons@nortelnetworks.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: FW: DELIVERY FAILURE: User socialevent (socialevent@marconi.com) not 
 listed in public Name & Address Book
References: <456E6DB7180ED3118A670000F8BDCA29021BB079@zcard00p.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Glenn Parsons wrote:

>
>
> Folks,
>
> I just tried to send a message to Marconi (to the address indicated on
> the IETF 48 social site) querying about tax being charged on the
> social event when you reserve on the website.  I received the
> following NDN.
>
> Has anyone else tried this address?
>
> Thanks,
> Glenn.
>
> ----------
> From:   Postmaster@marconi.com
> Sent:   Tuesday, July 4, 2000 2:35 pm
> To:     Parsons, Glenn
> Subject:        DELIVERY FAILURE: User socialevent
> (socialevent@marconi.com) not  listed in public Name & Address Book
>
> Your message
>
>   Subject: IETF social fee
>
> was not delivered to:
>
>   socialevent@marconi.com
>
> because:
>
>   User socialevent (socialevent@marconi.com) not listed in public Name
> & Address Book
>

Yep. Tried Monday and this AM - got the same message. Had problems with
my reservations too.

--
Jonathan Buschmann
Siemens Information and Communication Networks S.p.A.
CLTB, Cascina Castelletto, 20019 Settimo Milanese (Mi) Italy
Phone: (+39-2)43888754  Fax: (+39-2)43887989
Jonathan.Buschmann@icn.siemens.it
 "Sometimes when you fill a vacuum, it still sucks." - Dennis Ritchie





From owner-ietf-outbound  Wed Jul  5 06:10:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA19253
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 06:10:04 -0400 (EDT)
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 GAA19221
	for <ietf@ietf.org>; Wed, 5 Jul 2000 06:05:24 -0400 (EDT)
Received: (qmail 15497 invoked from network); 5 Jul 2000 10:05:25 -0000
Received: from userbe84.uk.uudial.com (HELO GK-VAIO.Dial.pipex.com) (62.188.142.6)
  by smtp.dial.pipex.com with SMTP; 5 Jul 2000 10:05:25 -0000
Message-Id: <4.3.2.7.2.20000705105811.00e00ed0@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 05 Jul 2000 10:59:04 +0100
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Graham Klyne <GK@Dial.pipex.com>
Subject: Re: WAP - What A Problem...
Cc: ietf@ietf.org
In-Reply-To: <200007050122.TAA25618@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 07:22 PM 7/4/00 -0600, Vernon Schryver wrote:

>If you are only using your cell phone screen for text messages, why
>do you need WAP?

You don't.

(My phone isn't a WAP phone, but it does do SMS.)

#g

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Wed Jul  5 07:40:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA20319
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 07:40:02 -0400 (EDT)
Received: from roam1 (roam1.u-net.net [195.102.240.81])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20224
	for <ietf@ietf.org>; Wed, 5 Jul 2000 07:36:53 -0400 (EDT)
Received: from ts33202.hknet.com ([202.67.170.202] helo=thunder)
	by roam1 with asmtp (Exim 3.036 #1)
	id 139nLA-0007Xb-00
	for ietf@ietf.org; Wed, 05 Jul 2000 11:27:40 +0000
Reply-To: <andy.murton@threegee.net>
From: "Andy Murton" <andy.murton@threegee.net>
Cc: <ietf@ietf.org>
Subject: RE: WAP - What A Problem...
Date: Wed, 5 Jul 2000 19:34:52 +0800
Message-ID: <LPBBKNBNGGCHNEHBFKIEEEFFCCAA.andy.murton@threegee.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.2911.0)
In-Reply-To: <4.3.2.7.2.20000705105811.00e00ed0@pop.dial.pipex.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

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

Provided your message fits into 160 characters.

- --murton

- -----Original Message-----
From: Graham Klyne [mailto:GK@Dial.pipex.com]
Sent: 05 July 2000 17:59
To: Vernon Schryver
Cc: ietf@ietf.org
Subject: Re: WAP - What A Problem...


At 07:22 PM 7/4/00 -0600, Vernon Schryver wrote:

>If you are only using your cell phone screen for text messages, why
>do you need WAP?

You don't.

(My phone isn't a WAP phone, but it does do SMS.)

#g

- ------------
Graham Klyne
(GK@ACM.ORG)



-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBOWKs19dTCRmPZunGEQLMSQCgrVUEojnTxFFatkC6iVRx1rLfliQAoNtF
c2Ct0TnhNg8gkjqg27d07h9U
=eINA
-----END PGP SIGNATURE-----



From owner-ietf-outbound  Wed Jul  5 08:00:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA20644
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 08:00:02 -0400 (EDT)
Received: from pntsmtp02.hq.espire.net ([206.222.96.209])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA20479
	for <ietf@ietf.org>; Wed, 5 Jul 2000 07:51:22 -0400 (EDT)
Received: FROM pntsmtp02.hq.espire.net BY pntsmtp02.hq.espire.net ; Wed Jul 05 07:51:43 2000 -0400
Received: by PNTSMTP02.hq.espire.net with Internet Mail Service (5.5.2650.21)
	id <3KJNK2SZ>; Wed, 5 Jul 2000 07:51:42 -0400
Message-ID: <11C39F7E0407D411AF1000D0B7475FDE4A96C3@PNTEXCH04.hq.espire.net>
From: "Taylor, Johnny" <Johnny.Taylor@espire.net>
To: Anthony Atkielski <anthony@atkielski.com>, ietf@ietf.org
Cc: "Kevin Clements (E-mail)" <kclement@morehouse.edu>,
        "Kevin Lampkin (E-mail)" <kevin.lampkin@wcom.com>,
        "Raymond Cutts (E-mail)" <rcutts@netrail.net>,
        "Robert Scott (E-mail)"
	 <Rob.Scott@wcom.com>
Subject: RE: WAP - What A Problem...
Date: Mon, 3 Jul 2000 13:06:53 -0400 
Return-Receipt-To: "Taylor, Johnny" <Johnny.Taylor@espire.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Well I guess when you look at multiple technologies like
VR (voice recognition), VN (voice navigation), IA (intelligent agents),
& WAP of course, Then you begin to see the relationships and importance 
of wireless applications. I concur with you on the point of land optics
however the average person requires remote and mobile access to their 
corporate networks, intra-nets, extra-nets, and value-added-networks. 
Therefore one could conclude that wireless access will have a main 
space within future technologies. In addition to this point I would 
like to also state WAP is the front runner in regards to linking 
wireless apps to the Global Internet and her sub-nets. Also, I would 
like to re-reference you to understanding Teledesic's network model. 
This is where you can clearly see the wireless model @ work. In closing,
I would ask that you stay aware of WAP for this is not a govt technology,
it was formulated from people like you, me, & the members of IETF! And
it will play a major role in all of our lives from a protocol stand point.

Video to Video, Voice to Text, Broadcast to IP, Data to Voice = WAP(Display)

Coming From The Brain,

JT

-----Original Message-----
From: Anthony Atkielski [mailto:anthony@atkielski.com]
Sent: Friday, June 30, 2000 1:12 PM
To: ietf@ietf.org
Subject: Re: WAP - What A Problem...


> thats why intelsat and a cosortium of telcos has
> a charity that built a box that is solar powered
> and provides n gsm phones access + 1 64kbps uplink/
> downlink to geostatinary atellites

So that's what, 64/5 = 13 kbps per user?  Even as current Internet designs
require ever more bandwidth and strain even multi-megabit connections?  And
has anyone considered what happens when you have 6 million active ground
transceivers trying to communicate with a single satellite?

> actualyl, a LOT of places that are really poor in
> the world dont even have electricty- but they can get
> batteries and if they use sms (e.g. for calling
> emergency service/flying doctors/vets etc), they
> can make them last quite a long time

Why use SMS instead of just voice?

Has anyone considered the ergonomics of WAP?  Even if it works perfectly,
how many people are willing to work on a screen smaller than a credit card?
How many people are capable of touch-typing on a keyboard with only ten soft
keys that must be pressed in various arcane combinations for almost ever
letter?  It just doesn't make intuitive sense.

Anyway, I have a really good instinct for picking technology winners, and
thus far I put WAP in the same category as MiniDiscs, bubble memory, color
fax machines, and quadraphonic sound.  I think the growth area is in
broadband land-based links; I don't understand why people have flown off on
tangents towards wireless when land links are just starting to come into
their own.  I suspect it is more politically motivated than technically
motivated, and that is one reason why I think it will fail.  A lot of time
and effort is being wasted on WAP.




From owner-ietf-outbound  Wed Jul  5 08:10:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA21630
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 08:10:02 -0400 (EDT)
Received: from pntsmtp02.hq.espire.net ([206.222.96.209])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA20535
	for <ietf@ietf.org>; Wed, 5 Jul 2000 07:54:05 -0400 (EDT)
Received: FROM pntsmtp02.hq.espire.net BY pntsmtp02.hq.espire.net ; Wed Jul 05 07:54:26 2000 -0400
Received: by PNTSMTP02.hq.espire.net with Internet Mail Service (5.5.2650.21)
	id <3KJNK24W>; Wed, 5 Jul 2000 07:54:25 -0400
Message-ID: <11C39F7E0407D411AF1000D0B7475FDE4A96D8@PNTEXCH04.hq.espire.net>
From: "Taylor, Johnny" <Johnny.Taylor@espire.net>
To: Gilbert Cattoire <gilbert@cattoire.net>,
        Anthony Atkielski
	 <anthony@atkielski.com>, ietf@ietf.org
Subject: RE: WAP - What A Problem...
Date: Mon, 3 Jul 2000 14:32:10 -0400 
Return-Receipt-To: "Taylor, Johnny" <Johnny.Taylor@espire.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

I like that close!

-----Original Message-----
From: Gilbert Cattoire [mailto:gilbert@cattoire.net]
Sent: Thursday, June 29, 2000 1:12 PM
To: Anthony Atkielski; ietf@ietf.org
Subject: Re: WAP - What A Problem...


At 18:29 +0200 29/06/00, Anthony Atkielski wrote:
>I don't understand why so much effort is expended on things like WAP when
>99% of the real world still doesn't have any access at all to the Internet,
>much less wireless access.  And even of those who do, most have such slow
>connections that even download a simple test page is an ordeal.

Refreshing...


>
>I know it's not very sexy to drop the blue-sky toys, but doesn't anyone
ever
>work on improving and democratizing existing infrastructure instead of
>widening the gap between what people really have and what looks cool in the
>lab?

Yes indeed. It would be interesting to know how many of us on this 
list agree with you.

Yet again, as I just mentioned in an earlier post, isn't it a matter 
regarding business models rather than technology?
What looks cool in the lab is quite often related to what is dear to 
investors'eyes.
WAP is just such a thing, regardless of technical niceties : a closed 
proprietary system built for a closed business model blessed with 
himalayan piles of cash.
Is it healthy ? With the Internet spirit in mind, does anyone need to 
dwell in the intricacies of gateways and so on to answer this 
question ? I would suggest this daring task : when in doubt, reboot 
your mindset.

best to all,




Gilbert Cattoire

==================================
+33 (0)6 08 35 15 82
gilbert@cattoire.net
==================================



From owner-ietf-outbound  Wed Jul  5 08:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA23315
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 08:20:03 -0400 (EDT)
Received: from pntsmtp02.hq.espire.net ([206.222.96.209])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA20542
	for <ietf@ietf.org>; Wed, 5 Jul 2000 07:54:07 -0400 (EDT)
Received: FROM pntsmtp02.hq.espire.net BY pntsmtp02.hq.espire.net ; Wed Jul 05 07:54:35 2000 -0400
Received: by PNTSMTP02.hq.espire.net with Internet Mail Service (5.5.2650.21)
	id <3KJNK2VG>; Wed, 5 Jul 2000 07:54:34 -0400
Message-ID: <11C39F7E0407D411AF1000D0B7475FDE4A96E2@PNTEXCH04.hq.espire.net>
From: "Taylor, Johnny" <Johnny.Taylor@espire.net>
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>,
        "'Lars-Erik Jonsson'" <lars-erik.jonsson@ERICSSON.COM>, ietf@ietf.org
Subject: RE: Is WAP mobile Internet??
Date: Mon, 3 Jul 2000 14:59:39 -0400 
Return-Receipt-To: "Taylor, Johnny" <Johnny.Taylor@espire.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Great Catch. It doesn't get any more Mobile on the Internet then that!


-----Original Message-----
From: Parkinson, Jonathan [mailto:Jonathan.Parkinson@compaq.com]
Sent: Friday, June 30, 2000 8:24 AM
To: 'Lars-Erik Jonsson'; ietf@ietf.org
Subject: RE: Is WAP mobile Internet??


Okay WAP at the moment is only in its baby stage, hence a few mobile phones
have it and a few other devices, and yes at the moment its not very good,
but that's because of the current technology. I know I keep going on about
it, but, I'm sure Bluetooth can and will change the way people use WAP and
as the applications become Bluetooth enabled, WAP is a perfect way of
transmitting data. 

Have a look at
http://news6.thdo.bbc.co.uk/hi/english/sci/tech/newsid%5F791000/791297.stm
Sony has said It is planning to put the Bluetooth short range wireless
technology in almost every gadget it produces making it easier to get at
data in any device, whether that is messages, music or video. 

IE
Walkmans, laptops, digital cameras and even electronic pets like the Aibo
robotic. 

WAP will be a perfect side technology for this. 

'This is just my opinion and not that of Compaq's (Yet :-))'

-----Original Message-----
From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ERICSSON.COM]
Sent: Friday, June 30, 2000 12:54 PM
To: ietf@ietf.org
Subject: Is WAP mobile Internet??


Hi Folks!!

I would like to hear your opinions about how WAP people often say that WAP
is
"mobile Internet". In my opinion, WAP is NOT mobile Internet at all. The
Internet is built on the e2e principle and based on the Internet Protocols,
which WAP is not. I can not tell people that they should not use WAP (even
if I
have my opinions about WAP). If they believe in WAP that is their problem,
but
when they try to use the words WAP and Internet in the same sentence I think
it
is time to clarify a few things. I accept that WAP is there, but be honest
about
what it is.

Cheers!
/Lars-Erik (expressing my PERSONAL opinions)



From owner-ietf-outbound  Wed Jul  5 08:30:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA24991
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 08:30:04 -0400 (EDT)
Received: from pntsmtp02.hq.espire.net ([206.222.96.209])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA20549
	for <ietf@ietf.org>; Wed, 5 Jul 2000 07:54:08 -0400 (EDT)
Received: FROM pntsmtp02.hq.espire.net BY pntsmtp02.hq.espire.net ; Wed Jul 05 07:54:36 2000 -0400
Received: by PNTSMTP02.hq.espire.net with Internet Mail Service (5.5.2650.21)
	id <3KJNK2V2>; Wed, 5 Jul 2000 07:54:34 -0400
Message-ID: <11C39F7E0407D411AF1000D0B7475FDE4A96E3@PNTEXCH04.hq.espire.net>
From: "Taylor, Johnny" <Johnny.Taylor@espire.net>
To: Renfield Kuroda <Renfield.Kuroda@msdw.com>, ietf@ietf.org
Subject: RE: Is WAP mobile Internet??
Date: Mon, 3 Jul 2000 15:03:50 -0400 
Return-Receipt-To: "Taylor, Johnny" <Johnny.Taylor@espire.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-2022-jp"
X-Loop: ietf@ietf.org

Good Point & I will tap into Japan Wireless infra-structure!

-----Original Message-----
From: Renfield Kuroda [mailto:Renfield.Kuroda@msdw.com]
Sent: Friday, June 30, 2000 9:07 PM
To: ietf@ietf.org
Subject: Re: Is WAP mobile Internet??


I don't think WAP Mobile Internet any more than TCP/IP is Internet.
The Mobile Internet is data/communication devices you carry around with you.

Here in Japan we have 8 million non-WAP mobile internet users, plus another
2
million WAP users, and the numbers are exploding.

But, and I know this may be the wrong mailing list for this comment, the
point is a
non-technical one. Users don't care if it's WAP/WML, or cHTML or MML or text
SMS, on
a cdmaONE network, PDC-P, or what.

Technically, I think many agree that WAP and its various technical standards
are
ill-conceived and poorly executed, but that doesn't mean the potential of
the Mobile
Internet isn't there. I personally think if WAP migrated to xHTML and
operators
looked at the successes here in Japan, than the next generation of WAP
phones (or
whatever you call them) really can and will be Mobile Internet.

Regards,

r e n

Lars-Erik Jonsson wrote:

> Hi Folks!!
>
> I would like to hear your opinions about how WAP people often say that WAP
is
> "mobile Internet". In my opinion, WAP is NOT mobile Internet at all. The
> Internet is built on the e2e principle and based on the Internet
Protocols,
> which WAP is not. I can not tell people that they should not use WAP (even
if I
> have my opinions about WAP). If they believe in WAP that is their problem,
but
> when they try to use the words WAP and Internet in the same sentence I
think it
> is time to clarify a few things. I accept that WAP is there, but be honest
about
> what it is.
>
> Cheers!
> /Lars-Erik (expressing my PERSONAL opinions)

--
ascii: r e n f i e l d
octal: \162 \145 \156 \146 \151 \145 \154 \144
hex:   \x72 \x65 \x6e \x66 \x69 \x65 \x6c  \x64
morgan stanley dean witter japan
e-business technologies | engineering and strategy



From owner-ietf-outbound  Wed Jul  5 08:40:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA26587
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 08:40:02 -0400 (EDT)
Received: from pntsmtp02.hq.espire.net ([206.222.96.209])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA20555
	for <ietf@ietf.org>; Wed, 5 Jul 2000 07:54:17 -0400 (EDT)
Received: FROM pntsmtp02.hq.espire.net BY pntsmtp02.hq.espire.net ; Wed Jul 05 07:54:28 2000 -0400
Received: by PNTSMTP02.hq.espire.net with Internet Mail Service (5.5.2650.21)
	id <3KJNK240>; Wed, 5 Jul 2000 07:54:28 -0400
Message-ID: <11C39F7E0407D411AF1000D0B7475FDE4A96DC@PNTEXCH04.hq.espire.net>
From: "Taylor, Johnny" <Johnny.Taylor@espire.net>
To: Lars-Erik Jonsson <lars-erik.jonsson@ericsson.com>, ietf@ietf.org
Subject: RE: Is WAP mobile Internet??
Date: Mon, 3 Jul 2000 14:45:14 -0400 
Return-Receipt-To: "Taylor, Johnny" <Johnny.Taylor@espire.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

The Internet allows all protocols to in-operate with her. This is the
uniqueness
of the web. Therefore WAP falls within this area!

-----Original Message-----
From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ericsson.com]
Sent: Friday, June 30, 2000 7:54 AM
To: ietf@ietf.org
Subject: Is WAP mobile Internet??


Hi Folks!!

I would like to hear your opinions about how WAP people often say that WAP
is
"mobile Internet". In my opinion, WAP is NOT mobile Internet at all. The
Internet is built on the e2e principle and based on the Internet Protocols,
which WAP is not. I can not tell people that they should not use WAP (even
if I
have my opinions about WAP). If they believe in WAP that is their problem,
but
when they try to use the words WAP and Internet in the same sentence I think
it
is time to clarify a few things. I accept that WAP is there, but be honest
about
what it is.

Cheers!
/Lars-Erik (expressing my PERSONAL opinions)



From owner-ietf-outbound  Wed Jul  5 09:10:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA00443
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 09:10:02 -0400 (EDT)
Received: from hqvsbh1.ms.com (hqvsbh1.ms.com [205.228.12.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25390
	for <ietf@ietf.org>; Wed, 5 Jul 2000 08:32:27 -0400 (EDT)
Received: (from uucp@localhost)
        by hqvsbh1.ms.com (8.9.3/fw v1.30) id IAA26639;
        Wed, 5 Jul 2000 08:32:09 -0400 (EDT)
Received: from localhost(127.0.0.1) by hqvsbh1 via smap (4.1)
	id sma.9628003111.026224; Wed, 5 Jul 00 08:31:51 -0400
Received: (from uucp@localhost)
	by hqvsbh1.ms.com (8.9.3/8.9.3(vs)) id IAA26167;
	Wed, 5 Jul 2000 08:31:50 -0400 (EDT)
X-Authentication-Warning: hqvsbh1.ms.com: Processed from queue /var/spool/mqueue-vs
X-Authentication-Warning: hqvsbh1.ms.com: Processed by uucp with -C /etc/mail/sendmail.vs.cf
Received: from ebsmh2.ms.com(161.144.69.74) by hqvsbh1 via smap (4.1)
	id sma.9628002971.025871; Wed, 5 Jul 00 08:31:37 -0400
Received: from msdw.com (hait35.morgan.com [138.20.191.29])
        by ebsmh2.ms.com (8.8.5/imap+ldap v2.4) with ESMTP id VAA15918;
        Wed, 5 Jul 2000 21:31:29 +0900 (JST)
Sender: renfield@ms.com
Message-ID: <39632AA0.9CB28F0B@msdw.com>
Date: Wed, 05 Jul 2000 13:31:28 +0100
From: Renfield Kuroda <Renfield.Kuroda@msdw.com>
Reply-To: Renfield.Kuroda@msdw.com
Organization: Morgan Stanley Dean Witter & Co.
X-Mailer: Mozilla 4.7C-CCK-MCD  [en] (X11; U; SunOS 5.5.1 sun4u)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: "Taylor, Johnny" <Johnny.Taylor@espire.net>
CC: Anthony Atkielski <anthony@atkielski.com>, ietf@ietf.org,
        "Kevin Clements (E-mail)" <kclement@morehouse.edu>,
        "Kevin Lampkin (E-mail)" <kevin.lampkin@wcom.com>,
        "Raymond Cutts (E-mail)" <rcutts@netrail.net>,
        "Robert Scott (E-mail)" <Rob.Scott@wcom.com>
Subject: Re: WAP - What A Problem...
References: <11C39F7E0407D411AF1000D0B7475FDE4A96C3@PNTEXCH04.hq.espire.net>
Content-Type: multipart/alternative;
 boundary="------------03B25B50316E3A4A5D6F3EEA"
X-Loop: ietf@ietf.org


--------------03B25B50316E3A4A5D6F3EEA
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

"Taylor, Johnny" wrote:

> In addition to this point I would
> like to also state WAP is the front runner in regards to linking
>
> wireless apps to the Global Internet and her sub-nets.
>
I'd have to disagree there. The 8 million non-WAP users in Japan are unarguably
enjoying the most prolific, robust, and deep wireless Internet available today.

Regards,

r e n

> --
> ascii: r e n f i e l d
> octal: \162 \145 \156 \146 \151 \145 \154 \144
> hex:   \x72 \x65 \x6e \x66 \x69 \x65 \x6c  \x64
> ** note new work email: renfield.kuroda@msdw.com **
>

--------------03B25B50316E3A4A5D6F3EEA
Content-Type: text/html; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
"Taylor, Johnny" wrote:
<blockquote TYPE=CITE>In addition to this point I would
<br>like to also state WAP is the front runner in regards to linking
<pre>wireless apps to the Global Internet and her sub-nets.</pre>
</blockquote>
I'd have to disagree there. The 8 million non-WAP users in Japan are unarguably
enjoying the most prolific, robust, and deep wireless Internet available
today.
<p>Regards,
<p>r e n
<blockquote TYPE=CITE>
<pre>--&nbsp;
ascii: r e n f i e l d
octal: \162 \145 \156 \146 \151 \145 \154 \144
hex:&nbsp;&nbsp; \x72 \x65 \x6e \x66 \x69 \x65 \x6c&nbsp; \x64
** note new work email: renfield.kuroda@msdw.com **</pre>
</blockquote>
</html>

--------------03B25B50316E3A4A5D6F3EEA--



From owner-ietf-outbound  Wed Jul  5 09:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA01132
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 09:20:03 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00989
	for <ietf@ietf.org>; Wed, 5 Jul 2000 09:17:15 -0400 (EDT)
Received: from lms001.lu.erisoft.se (lms001.lu.erisoft.se [150.132.144.19])
	by penguin.wise.edt.ericsson.se (8.10.1/8.10.1/WIREfire-1.9) with ESMTP id e65DHFs26123;
	Wed, 5 Jul 2000 15:17:15 +0200 (MET DST)
Received: by lms001.lu.erisoft.se id PAA00970; Wed, 5 Jul 2000 15:17:13 +0200 (MET DST)
Message-ID: <005701bfe683$7d6f1780$e064d693@e00008639f5da>
From: "Lars-Erik Jonsson" <lars-erik.jonsson@ericsson.com>
To: "Taylor, Johnny" <Johnny.Taylor@espire.net>, <ietf@ietf.org>
Subject: Re: Is WAP mobile Internet??
Date: Wed, 5 Jul 2000 15:18:18 +0200
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.3612.1700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

The Web is NOT the Internet. The Web is one Internet application. 

/L-E



>The Internet allows all protocols to in-operate with her. This is the
>uniqueness
>of the web. Therefore WAP falls within this area!
>
>-----Original Message-----
>From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ericsson.com]
>Sent: Friday, June 30, 2000 7:54 AM
>To: ietf@ietf.org
>Subject: Is WAP mobile Internet??
>
>
>Hi Folks!!
>
>I would like to hear your opinions about how WAP people often say that WAP
>is
>"mobile Internet". In my opinion, WAP is NOT mobile Internet at all. The
>Internet is built on the e2e principle and based on the Internet Protocols,
>which WAP is not. I can not tell people that they should not use WAP (even
>if I
>have my opinions about WAP). If they believe in WAP that is their problem,
>but
>when they try to use the words WAP and Internet in the same sentence I think
>it
>is time to clarify a few things. I accept that WAP is there, but be honest
>about
>what it is.
>
>Cheers!
>/Lars-Erik (expressing my PERSONAL opinions)
>



From owner-ietf-outbound  Wed Jul  5 09:30:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA01638
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 09:30:02 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01247
	for <ietf@ietf.org>; Wed, 5 Jul 2000 09:21:57 -0400 (EDT)
Received: from AStLambert101214 (ASt-Lambert-101-2-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.8.8) id PAA97087; Wed, 5 Jul 2000 15:21:52 +0200 (CEST)
Message-ID: <002a01bfe683$fc0c1de0$0a00000a@abo.wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <11C39F7E0407D411AF1000D0B7475FDE4A96C3@PNTEXCH04.hq.espire.net>
Subject: Re: WAP - What A Problem...
Date: Wed, 5 Jul 2000 15:21:51 +0200
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
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> I concur with you on the point of land optics
> however the average person requires remote and
> mobile access to their corporate networks,
> intra-nets, extra-nets, and value-added-networks.

The average person doesn't use any of these networks, and so does not
require access to them.  There are still too many people (_most_ people, in
fact) who do not have an e-mail address.

> Therefore one could conclude that wireless access will
> have a main space within future technologies.

Some sort of wireless access to the Internet will surely have a place in the
future.  Beyond that, I wouldn't make any specific predictions about what
form it might take.

> In addition to this point I would like to also
> state WAP is the front runner in regards to linking
> wireless apps to the Global Internet and her sub-nets.

I'm not sure what you mean by "Global Internet," since I'm not aware of any
other kind of Internet.

Also, in English, inanimate objects and concepts take the neuter gender, not
the female gender, so the Internet is "it," not "she."

> Also, I would like to re-reference you to
> understanding Teledesic's network model.

Satellites in low orbit providing two-way communication with a vast number
of ground stations, right?  What else is there to it?

> This is where you can clearly see the wireless model
> @ work.

Has this wireless network actually been implemented?  Last I heard of
anything coming close was Iridium, and we know what happened to that.

> In closing, I would ask that you stay aware of WAP
> for this is not a govt technology, it was formulated
> from people like you, me, & the members of IETF!

I'm as aware of it as I was of MiniDiscs and Betamax.  When and if it moves
to the mainstream (something I do not really expect at this point), I'll
consider it in greater detail.

One thing I'd like to know is:  Is WAP a response to user demands for
wireless Net access from credit-card-sized terminals, or is WAP something
that looked like it would be cool to implement that the inventors and their
marketroids are now trying to sell to others?

> And it will play a major role in all of our lives
> from a protocol stand point.

Just like Picturephone service and DIVX.

> Video to Video, Voice to Text, Broadcast to IP,
> Data to Voice = WAP(Display)

I don't see the two killer apps here--e-mail and the Web--unless they are
disguised in terminology somewhere in there.  I'm not even convinced of the
practicality of those, however, on terminals that are ergonomically
unsuitable to either.





From owner-ietf-outbound  Wed Jul  5 09:40:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA02009
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 09:40:02 -0400 (EDT)
Received: from mlgdn00101.planetasia.com ([164.164.80.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01290
	for <ietf@ietf.org>; Wed, 5 Jul 2000 09:22:24 -0400 (EDT)
Received: by MLGDN00101 with Internet Mail Service (5.5.2650.21)
	id <3BZQS9Y7>; Wed, 5 Jul 2000 18:55:01 +0530
Message-ID: <E70B4F843879D111B68B00805F0D2559016E93A8@MLGDN00101>
From: Ashutosh Agarwal <ashutosha@planetasia.com>
To: "'Taylor, Johnny'" <Johnny.Taylor@espire.net>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Is WAP mobile Internet??
Date: Wed, 5 Jul 2000 18:55:00 +0530 
Return-Receipt-To: Ashutosh Agarwal <ashutosha@planetasia.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop: ietf@ietf.org

Hi all,
I fully agree with Lars. Even I believe WAP does not fall under the Internet
Umbrella


Ashutosh Agarwal	
e-mail : ashutosha@planetasia.com
------------------------------------------------------------------------
Change your thoughts and you change your world.
							The Buddha 
------------------------------------------------------------------------

> -----Original Message-----
> From:	Taylor, Johnny [SMTP:Johnny.Taylor@espire.net]
> Sent:	Tuesday, July 04, 2000 12:15 AM
> To:	Lars-Erik Jonsson; ietf@ietf.org
> Subject:	RE: Is WAP mobile Internet??
> 
> The Internet allows all protocols to in-operate with her. This is the
> uniqueness
> of the web. Therefore WAP falls within this area!
> 
> -----Original Message-----
> From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ericsson.com]
> Sent: Friday, June 30, 2000 7:54 AM
> To: ietf@ietf.org
> Subject: Is WAP mobile Internet??
> 
> 
> Hi Folks!!
> 
> I would like to hear your opinions about how WAP people often say that WAP
> is
> "mobile Internet". In my opinion, WAP is NOT mobile Internet at all. The
> Internet is built on the e2e principle and based on the Internet
> Protocols,
> which WAP is not. I can not tell people that they should not use WAP (even
> if I
> have my opinions about WAP). If they believe in WAP that is their problem,
> but
> when they try to use the words WAP and Internet in the same sentence I
> think
> it
> is time to clarify a few things. I accept that WAP is there, but be honest
> about
> what it is.
> 
> Cheers!
> /Lars-Erik (expressing my PERSONAL opinions)



From owner-ietf-outbound  Wed Jul  5 09:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA02936
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 09:50:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01411
	for <ietf@ietf.org>; Wed, 5 Jul 2000 09:24:58 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA19516;
        Wed, 5 Jul 2000 09:24:56 -0400 (EDT)
Message-Id: <200007051324.JAA19516@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Renfield Kuroda <Renfield.Kuroda@msdw.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Is WAP mobile Internet?? 
In-reply-to: Your message of "Sat, 01 Jul 2000 10:06:54 +0900."
             <395D442D.C506FEEA@msdw.com> 
Date: Wed, 05 Jul 2000 09:24:56 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Here in Japan we have 8 million non-WAP mobile internet users,

uh, no.  if you don't have IP to the phone, it's not mobile Internet.
calling it Internet is just deceptive advertising.



From owner-ietf-outbound  Wed Jul  5 10:00:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA03763
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 10:00:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01476
	for <ietf@ietf.org>; Wed, 5 Jul 2000 09:26:13 -0400 (EDT)
Received: from AStLambert101214 (ASt-Lambert-101-2-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.8.8) id PAA97596; Wed, 5 Jul 2000 15:26:14 +0200 (CEST)
Message-ID: <003601bfe684$97e6cc60$0a00000a@abo.wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <11C39F7E0407D411AF1000D0B7475FDE4A96C3@PNTEXCH04.hq.espire.net> <39632AA0.9CB28F0B@msdw.com>
Subject: Re: WAP - What A Problem...
Date: Wed, 5 Jul 2000 15:26:13 +0200
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
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> I'd have to disagree there. The 8 million non-WAP users
> in Japan are unarguably enjoying the most prolific, robust,
> and deep wireless Internet available today.

We still have more than five billion users who aren't even online yet.  They
haven't enjoyed anything thus far.



From owner-ietf-outbound  Wed Jul  5 10:10:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA04367
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 10:10:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01519
	for <ietf@ietf.org>; Wed, 5 Jul 2000 09:27:25 -0400 (EDT)
Received: from AStLambert101214 (ASt-Lambert-101-2-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.8.8) id PAA97690; Wed, 5 Jul 2000 15:27:26 +0200 (CEST)
Message-ID: <003f01bfe684$c30305d0$0a00000a@abo.wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <11C39F7E0407D411AF1000D0B7475FDE4A96DC@PNTEXCH04.hq.espire.net>
Subject: Re: Is WAP mobile Internet??
Date: Wed, 5 Jul 2000 15:27:22 +0200
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
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> The Internet allows all protocols to in-operate with her.

With it, you mean.



From owner-ietf-outbound  Wed Jul  5 10:20:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA04810
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 10:20:02 -0400 (EDT)
Received: from mlgdn00101.planetasia.com ([164.164.80.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01542
	for <ietf@ietf.org>; Wed, 5 Jul 2000 09:27:40 -0400 (EDT)
Received: by MLGDN00101 with Internet Mail Service (5.5.2650.21)
	id <3BZQS9Z4>; Wed, 5 Jul 2000 19:00:07 +0530
Message-ID: <E70B4F843879D111B68B00805F0D2559016E93A9@MLGDN00101>
From: Ashutosh Agarwal <ashutosha@planetasia.com>
To: "'Lars-Erik Jonsson'" <lars-erik.jonsson@ericsson.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Is WAP mobile Internet??
Date: Wed, 5 Jul 2000 19:00:06 +0530 
Return-Receipt-To: Ashutosh Agarwal <ashutosha@planetasia.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop: ietf@ietf.org

Well the web is indeed the Internet we are talking about
The Internet is an internet, but an internet is not an Internet always


Ashutosh Agarwal	
e-mail : ashutosha@planetasia.com
------------------------------------------------------------------------
Change your thoughts and you change your world.
							The Buddha 
------------------------------------------------------------------------

> -----Original Message-----
> From:	Lars-Erik Jonsson [SMTP:lars-erik.jonsson@ericsson.com]
> Sent:	Wednesday, July 05, 2000 6:48 PM
> To:	Taylor, Johnny; ietf@ietf.org
> Subject:	Re: Is WAP mobile Internet??
> 
> The Web is NOT the Internet. The Web is one Internet application. 
> 
> /L-E
> 
> 
> 
> >The Internet allows all protocols to in-operate with her. This is the
> >uniqueness
> >of the web. Therefore WAP falls within this area!
> >
> >-----Original Message-----
> >From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ericsson.com]
> >Sent: Friday, June 30, 2000 7:54 AM
> >To: ietf@ietf.org
> >Subject: Is WAP mobile Internet??
> >
> >
> >Hi Folks!!
> >
> >I would like to hear your opinions about how WAP people often say that
> WAP
> >is
> >"mobile Internet". In my opinion, WAP is NOT mobile Internet at all. The
> >Internet is built on the e2e principle and based on the Internet
> Protocols,
> >which WAP is not. I can not tell people that they should not use WAP
> (even
> >if I
> >have my opinions about WAP). If they believe in WAP that is their
> problem,
> >but
> >when they try to use the words WAP and Internet in the same sentence I
> think
> >it
> >is time to clarify a few things. I accept that WAP is there, but be
> honest
> >about
> >what it is.
> >
> >Cheers!
> >/Lars-Erik (expressing my PERSONAL opinions)
> >



From owner-ietf-outbound  Wed Jul  5 10:30:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA05764
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 10:30:02 -0400 (EDT)
Received: from ztxmail04.ztx.compaq.com (ztxmail04.ztx.compaq.com [161.114.1.208])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04659
	for <ietf@ietf.org>; Wed, 5 Jul 2000 10:15:50 -0400 (EDT)
Received: by ztxmail04.ztx.compaq.com (Postfix, from userid 12345)
	id D80581CF; Wed,  5 Jul 2000 09:15:21 -0500 (CDT)
Received: from excreo-gh01.reo.dec.com (excreo-gh01.reo.cpqcorp.net [16.41.128.40])
	by ztxmail04.ztx.compaq.com (Postfix) with ESMTP
	id 270D62B3; Wed,  5 Jul 2000 09:15:20 -0500 (CDT)
Received: by excreo-gh01.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <N64N1RXR>; Wed, 5 Jul 2000 15:15:18 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9C39@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'Ashutosh Agarwal'" <ashutosha@planetasia.com>,
        "'Taylor, Johnny'" <Johnny.Taylor@espire.net>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Is WAP mobile Internet??
Date: Wed, 5 Jul 2000 15:15:13 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

I disagree, WAP, Wireless Application Protocol, Its a way of transmitting
data I.E. to and from the Web. How does this not fall under the Internet
Umbrella ?

Thanks
Jon

-----Original Message-----
From: Ashutosh Agarwal [mailto:ashutosha@planetasia.com]
Sent: Wednesday, July 05, 2000 2:25 PM
To: 'Taylor, Johnny'
Cc: 'ietf@ietf.org'
Subject: RE: Is WAP mobile Internet??


Hi all,
I fully agree with Lars. Even I believe WAP does not fall under the Internet
Umbrella


Ashutosh Agarwal	
e-mail : ashutosha@planetasia.com
------------------------------------------------------------------------
Change your thoughts and you change your world.
							The Buddha 
------------------------------------------------------------------------

> -----Original Message-----
> From:	Taylor, Johnny [SMTP:Johnny.Taylor@espire.net]
> Sent:	Tuesday, July 04, 2000 12:15 AM
> To:	Lars-Erik Jonsson; ietf@ietf.org
> Subject:	RE: Is WAP mobile Internet??
> 
> The Internet allows all protocols to in-operate with her. This is the
> uniqueness
> of the web. Therefore WAP falls within this area!
> 
> -----Original Message-----
> From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ericsson.com]
> Sent: Friday, June 30, 2000 7:54 AM
> To: ietf@ietf.org
> Subject: Is WAP mobile Internet??
> 
> 
> Hi Folks!!
> 
> I would like to hear your opinions about how WAP people often say that WAP
> is
> "mobile Internet". In my opinion, WAP is NOT mobile Internet at all. The
> Internet is built on the e2e principle and based on the Internet
> Protocols,
> which WAP is not. I can not tell people that they should not use WAP (even
> if I
> have my opinions about WAP). If they believe in WAP that is their problem,
> but
> when they try to use the words WAP and Internet in the same sentence I
> think
> it
> is time to clarify a few things. I accept that WAP is there, but be honest
> about
> what it is.
> 
> Cheers!
> /Lars-Erik (expressing my PERSONAL opinions)



From owner-ietf-outbound  Wed Jul  5 10:45:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07214
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 10:45:10 -0400 (EDT)
Received: from terra.telestet.gr (terra.telestet.gr [194.219.149.99])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA04918
	for <ietf@ietf.org>; Wed, 5 Jul 2000 10:21:43 -0400 (EDT)
Received: from [192.168.2.2]
	(HELO localhost)
	by terra.telestet.gr (AltaVista Mail V2.0J/2.0J BL25J listener)
	id 0000_0051_3963_4331_6d43;
	Wed, 05 Jul 2000 17:16:17 +0300
Received: by mail.telestet.gr with Internet Mail Service (5.5.2650.21)
	id <3KBFDKHY>; Wed, 5 Jul 2000 17:19:31 +0300
Message-ID: <6ADD5A0DF6B1D31193430090279A2A08E45044@mail.telestet.gr>
From: TSIGARIDAS PANAGIOTIS <P.TSIGARIDAS@telestet.gr>
To: Lars-Erik Jonsson <lars-erik.jonsson@ericsson.com>,
        "Taylor, Johnny"
	 <Johnny.Taylor@espire.net>, ietf@ietf.org
Subject: RE: Is WAP mobile Internet??
Date: Wed, 5 Jul 2000 17:19:22 +0300 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFE68C.08E4ECF6"
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFE68C.08E4ECF6
Content-Type: text/plain;
	charset="iso-8859-1"

I believe, I found part of the following text in WAP Forum's WEB-pages.
However, I think the answer -from business and technology point of view- is
simple; 

Is WAP mobile Internet ?  Yes and NO

WAP is using existing Internet standards.  The WAP architecture was designed
to enable standard Internet servers to provide services to wireless devices.
In addition, when communicating with wireless devices, WAP uses many
Internet standards such as XML, UDP and IP. The WAP wireless protocols are
based on Internet standards such as HTTP and TLS but have been optimised for
the unique constraints of the wireless environment.
Internet standards such as HTML, HTTP, TLS and TCP are inefficient over
mobile networks, requiring: 

	Large amounts of mainly text based data to be sent.

	Standard HTML web content generally cannot be displayed in an
effective way on the small size screens of mobile phones and 
	pagers, and navigation around and between screens is not easy.

	HTTP and TCP are not optimised for the gaps of coverage (change over
etc.), long latencies and limited bandwidth associated 
	with wireless networks. HTTP sends its headers and commands in  text
format instead of compressed binary. Wireless 
	services using these protocols are often slow, costly and difficult
to use. The TLS security standard requires many messages 
	to be exchanged between client and server which, with wireless
transmission latencies, results in a very slow response for the 
	user.

WAP has been optimised to solve all these problems (??? my oppinion),
utilising binary transmission and greater compression of data, and is
optimised for long latency and low/medium bandwidth. WAP session protocol
stack can cope with limited coverage (gaps of coverage) and can operate over
a wide variety of wireless transports using IP where possible and other
optimised protocols where IP is impossible (WDP).

The WML language used for WAP content makes optimum use of small screens and
allows easy navigation with without a full keyboard, and has built-in
scaleability from two-line text displays  to the full graphic screens of
smart phones and communicators.

Additionally, WAP goes far beyond the Internet technology not in order to
extent the Internet,  but to address functional entities like SIM/WIM,
GSM-Telephony etc., they are not part of  the Internet market technology.
They are  an important part of the cellular technology and they simply do
exist and have to be addressed.  

----------------------------------------------------------------------------
-------------------------------
Is WAP going in a different direction than Internet standards do ? NO.

Many of WAP Forum's protocols are Internet standards such as XML, IP and
UDP. The Forum has created a protocol suite that is optimised for the mobile
environment. WAP Forum is working closely with the W3C (World Wide Web
Consortium) and the IETF (Internet Engineering Task Force) to ensure that
the future versions of HTML, HTTP and TCP will accommodate the special needs
of mobile devices and can be supported in the WAP framework.



Panagiotis Tsigaridas
Telco Information Systems Manager
STET Hellas Telecommunuications S.A.

-----Original Message-----
From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ericsson.com]
Sent: Wednesday, July 05, 2000 4:18 PM
To: Taylor, Johnny; ietf@ietf.org
Subject: Re: Is WAP mobile Internet??


The Web is NOT the Internet. The Web is one Internet application.

/L-E



>The Internet allows all protocols to in-operate with her. This is the
>uniqueness
>of the web. Therefore WAP falls within this area!
>
>-----Original Message-----
>From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ericsson.com]
>Sent: Friday, June 30, 2000 7:54 AM
>To: ietf@ietf.org
>Subject: Is WAP mobile Internet??
>
>
>Hi Folks!!
>
>I would like to hear your opinions about how WAP people often say that WAP
>is
>"mobile Internet". In my opinion, WAP is NOT mobile Internet at all. The
>Internet is built on the e2e principle and based on the Internet Protocols,
>which WAP is not. I can not tell people that they should not use WAP (even
>if I
>have my opinions about WAP). If they believe in WAP that is their problem,
>but
>when they try to use the words WAP and Internet in the same sentence I
think
>it
>is time to clarify a few things. I accept that WAP is there, but be honest
>about
>what it is.
>
>Cheers!
>/Lars-Erik (expressing my PERSONAL opinions)
>

------_=_NextPart_001_01BFE68C.08E4ECF6
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: Is WAP mobile Internet??</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I believe, I found part of the following text in WAP =
Forum's WEB-pages. However, I think the answer -from business and =
technology point of view- is simple; </FONT></P>

<P><FONT SIZE=3D2>Is WAP mobile Internet ?&nbsp; Yes and NO</FONT>
</P>

<P><FONT SIZE=3D2>WAP is using existing Internet standards.&nbsp; The =
WAP architecture was designed to enable standard Internet servers to =
provide services to wireless devices.&nbsp; In addition, when =
communicating with wireless devices, WAP uses many Internet standards =
such as XML, UDP and IP. The WAP wireless protocols are based on =
Internet standards such as HTTP and TLS but have been optimised for the =
unique constraints of the wireless environment.</FONT></P>

<P><FONT SIZE=3D2>Internet standards such as HTML, HTTP, TLS and TCP =
are inefficient over mobile networks, requiring: </FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Large =
amounts of mainly text based data to be sent.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Standard =
HTML web content generally cannot be displayed in an effective way on =
the small size screens of mobile phones and </FONT></P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>pagers, =
and navigation around and between screens is not easy.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>HTTP and =
TCP are not optimised for the gaps of coverage (change over etc.), long =
latencies and limited bandwidth associated </FONT></P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>with =
wireless networks. HTTP sends its headers and commands in&nbsp; text =
format instead of compressed binary. Wireless </FONT></P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>services =
using these protocols are often slow, costly and difficult to use. The =
TLS security standard requires many messages </FONT></P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>to be =
exchanged between client and server which, with wireless transmission =
latencies, results in a very slow response for the </FONT></P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>user.</FONT>
</P>

<P><FONT SIZE=3D2>WAP has been optimised to solve all these problems =
(??? my oppinion), utilising binary transmission and greater =
compression of data, and is optimised for long latency and low/medium =
bandwidth. WAP session protocol stack can cope with limited coverage =
(gaps of coverage) and can operate over a wide variety of wireless =
transports using IP where possible and other optimised protocols where =
IP is impossible (WDP).</FONT></P>

<P><FONT SIZE=3D2>The WML language used for WAP content makes optimum =
use of small screens and allows easy navigation with without a full =
keyboard, and has built-in scaleability from two-line text =
displays&nbsp; to the full graphic screens of smart phones and =
communicators.</FONT></P>

<P><FONT SIZE=3D2>Additionally, WAP goes far beyond the Internet =
technology not in order to extent the Internet,&nbsp; but to address =
functional entities like SIM/WIM, GSM-Telephony etc., they are not part =
of&nbsp; the Internet market technology. They are&nbsp; an important =
part of the cellular technology and they simply do exist and have to be =
addressed.&nbsp; </FONT></P>

<P><FONT =
SIZE=3D2>---------------------------------------------------------------=
--------------------------------------------</FONT>
<BR><FONT SIZE=3D2>Is WAP going in a different direction than Internet =
standards do ? NO.</FONT>
</P>

<P><FONT SIZE=3D2>Many of WAP Forum's protocols are Internet standards =
such as XML, IP and UDP. The Forum has created a protocol suite that is =
optimised for the mobile environment. WAP Forum is working closely with =
the W3C (World Wide Web Consortium) and the IETF (Internet Engineering =
Task Force) to ensure that the future versions of HTML, HTTP and TCP =
will accommodate the special needs of mobile devices and can be =
supported in the WAP framework.</FONT></P>
<BR>
<BR>

<P><FONT SIZE=3D2>Panagiotis Tsigaridas</FONT>
<BR><FONT SIZE=3D2>Telco Information Systems Manager</FONT>
<BR><FONT SIZE=3D2>STET Hellas Telecommunuications S.A.</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Lars-Erik Jonsson [<A =
HREF=3D"mailto:lars-erik.jonsson@ericsson.com">mailto:lars-erik.jonsson@=
ericsson.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, July 05, 2000 4:18 PM</FONT>
<BR><FONT SIZE=3D2>To: Taylor, Johnny; ietf@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: Is WAP mobile Internet??</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>The Web is NOT the Internet. The Web is one Internet =
application.</FONT>
</P>

<P><FONT SIZE=3D2>/L-E</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt;The Internet allows all protocols to in-operate =
with her. This is the</FONT>
<BR><FONT SIZE=3D2>&gt;uniqueness</FONT>
<BR><FONT SIZE=3D2>&gt;of the web. Therefore WAP falls within this =
area!</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt;From: Lars-Erik Jonsson [<A =
HREF=3D"mailto:lars-erik.jonsson@ericsson.com">mailto:lars-erik.jonsson@=
ericsson.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt;Sent: Friday, June 30, 2000 7:54 AM</FONT>
<BR><FONT SIZE=3D2>&gt;To: ietf@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt;Subject: Is WAP mobile Internet??</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;Hi Folks!!</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;I would like to hear your opinions about how WAP =
people often say that WAP</FONT>
<BR><FONT SIZE=3D2>&gt;is</FONT>
<BR><FONT SIZE=3D2>&gt;&quot;mobile Internet&quot;. In my opinion, WAP =
is NOT mobile Internet at all. The</FONT>
<BR><FONT SIZE=3D2>&gt;Internet is built on the e2e principle and based =
on the Internet Protocols,</FONT>
<BR><FONT SIZE=3D2>&gt;which WAP is not. I can not tell people that =
they should not use WAP (even</FONT>
<BR><FONT SIZE=3D2>&gt;if I</FONT>
<BR><FONT SIZE=3D2>&gt;have my opinions about WAP). If they believe in =
WAP that is their problem,</FONT>
<BR><FONT SIZE=3D2>&gt;but</FONT>
<BR><FONT SIZE=3D2>&gt;when they try to use the words WAP and Internet =
in the same sentence I think</FONT>
<BR><FONT SIZE=3D2>&gt;it</FONT>
<BR><FONT SIZE=3D2>&gt;is time to clarify a few things. I accept that =
WAP is there, but be honest</FONT>
<BR><FONT SIZE=3D2>&gt;about</FONT>
<BR><FONT SIZE=3D2>&gt;what it is.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;Cheers!</FONT>
<BR><FONT SIZE=3D2>&gt;/Lars-Erik (expressing my PERSONAL =
opinions)</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFE68C.08E4ECF6--



From owner-ietf-outbound  Wed Jul  5 10:55:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07684
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 10:55:10 -0400 (EDT)
Received: from orion.usno.navy.mil ([192.5.41.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06610
	for <ietf@ietf.org>; Wed, 5 Jul 2000 10:37:44 -0400 (EDT)
Received: (from dnm@localhost) by orion.usno.navy.mil (8.8.6 (PHNE_14041)/8.7.1) id OAA10836 for ietf@ietf.org; Wed, 5 Jul 2000 14:36:35 GMT
Date: Wed, 5 Jul 2000 14:36:35 GMT
From: Demetrios N Matsakis <dnm@orion.usno.navy.mil>
Message-Id: <200007051436.OAA10836@orion.usno.navy.mil>
To: ietf@ietf.org
Subject: Leap Second Report
Mime-Version: 1.0
Content-Type: text/plain; charset=X-roman8
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Dear Respondee,

Thank you for having responded to, or somehow been connected with, our 
questionnaire concerning the effects of a redefinition of UTC.

If you are interested in pursuing this issue, we welcome you to join our
listserv "chat group", http://clockdev.usno.navy.mil/archives/leapsecs.html.

Demetrios Matsakis

***************************************************************************

   Report of the URSI Commission J Working Group on the Leap Second

   Date: July 2, 2000
 
Abstract and Conclusions
 
An e-mail survey to find possible adverse effects of a redefinition of
UTC has identified some possibly expensive or unsolvable problems
involving software rewriting or checking, which are listed below.
Although it was not possible to quantify the financial scale of
resolving the software problems, the largest expenses appear to be for
satellite systems, of which one estimate of several hundred thousand
dollars was supplied.  The quantity and quality of the responses
opposed to a change indicate that those who favor any change must be
prepared to make a very convincing argument to people and groups who
initially will disagree with them.

To further discuss this issue and inform the community of any developments, 
an archived electronic listserv has been set up.  Anyone wishing to join
can do so using http://clockdev.usno.navy.mil/archives/leapsecs.html.
 
Introduction
 
UTC (Coordinated Universal Time), which the public commonly confuses
with Greenwich Mean Time, is computed by occasionally adding leap
seconds to International Atomic Time (TAI).  Since 1972, these leap
seconds have been added on December 31 or June 30, at the rate of about
one every 18 months, and serve to keep atomic time in step with the
Earth's rotation. Although it is recommended that users use only TAI or
UTC, as their needs indicate, many major navigation system have used
times offset from TAI by fixed amounts.  The most important of these is
GPS, which is offset by 19 seconds from TAI.
 
A segment of the international timing community has proposed a revision
of the definition of UTC to avoid the discontinuities due to
intermittent leap seconds.  A discussion of the motivations for a
change and of possible solutions has been published by McCarthy and
Klepczynski in the Innovations Section of the November, 1999 issue of
GPS World.   The authors consider the most significant reason for a
change to be keeping spread-spectrum communication systems and
satellite navigation systems compatible with each other and with civil
times.  Another reason is the emerging need in the financial community
to keep all computer time-stamps synchronized.
 
In order to survey the effects of any action, an URSI Commission J
Working Group (WG) was formed, whose purpose was to prepare this report
and propose further actions.
 
Methodology
 
A questionnaire (Appendix I) was distributed as widely as seemed
appropriate (Appendix II). The goal of the questionnaire was to find
and categorize those operations that would be adversely affected should
a change in UTC's computation be made. The questionnaire focused on the
possibility of simply inserting no new leap seconds, although
alternative solutions were also solicited.  Over 200 responses were
received, and no effort was made to separate the responses of URSI
members from those of nonmembers. 
 
The principal object of the questionnaire was to find what systems
would be adversely affected should a change be made in leap second
procedures rather than to convince users of the need for a change or
to take a vote.  However, so many queries on these matters were
received that a "standard reply" (Appendix III) was developed and
distributed as appropriate.   In the spirit of full disclosure, the
number of responses in each category is given, but we caution that this
was by no means an unbiased sampling of all who would be affected by
the change.  All responses were counted only once, with preference to
the most practical grounds for objection.  About half the responses
that were received were opposed to any change, while one-fourth were 
in favor of a change, and one-fourth indifferent.
 
I.  Responses Opposed to Changes in the Status Quo
 
A. The expense of rewriting software.
 
Five responses suggested that contractors would have to be hired to
scrutinize and adapt large amounts of code for operational satellite
systems.  Efforts were made to contact these responders for specific
dollar amounts, and one off-the-cuff estimate of "several $100,000" was
received.  The impact on such systems would be lessened if any decision
to redefine UTC were announced several years in advance.
 
Twenty-six others indicated that software would be a serious problem - a
very few of these were from people who did not seem to understand the 
proposal. There were 9 responses involving telescope control; one of these,
from the Keck Observatory, provided a rough estimate of a few programmer-
months.  Others pointed out the problems computing eclipses and 
occultations, for telescope pointing by amateurs, or with code they had 
themselves written for professional-level projects such as speckle 
interferometry.  One observatory indicated its station clock can not 
accommodate a large UT1-UTC correction.
 
Fourteen more indicated that software issues would be a problem, but that
they are probably solvable.  Some of these actually indicated support
for the change.
 
B. Inherent inability to rewrite software to allow for |UT1-UTC|
exceeding .9 seconds.
 
Ten responses involved navigational software.  Taking the example of a
software product of the US Naval Observatory (USNO), pilots and sailors
are given the option to input UT1-UTC. However, it is expected that
many users would not understand this and enter 0, leading to noticeable
errors within a decade. These are similar to the telescope-control
problems covered above, except that one could not and should not expect
the general public to ever understand these issues.  Problems amateur
astronomers might have are also included here, and were brought up by
many responders in other contexts.
 
One of the problems anticipated is that UT1-UTC could be applied with
the wrong sign, just as the leap second is occasionally applied with
the wrong sign.  An example of "buffer overflow" problem would happen
in NIST's WWV, WWVH and WWWB transmissions, which do not allow enough
space for |UT1-UTC| to exceed .9 sec.  Any users of these broadcasts 
who might need this information and who are unaware of the problem, 
decoding in hardware, or relying on old software would be adversely 
affected. Under the best of future circumstances only the sub-second 
(tenths) digit would be available, requiring the user to keep track of 
the digits to the left of the decimal point.
 
Not tabulated is an informal comment seriously made to the Working 
Group's Chairman, by a respected and competent scientist from a 
non-western nation, that astrologers would be adversely affected.
 
C. Philosophical Objections
 
Eight thought this would confuse or antagonize the public, religious
authorities, or even scientists - in essence because solar time is
"true time". (In contrast, one responder in favor of a change thought
this would help educate the public to the fact that Earth rotation is
not "true" time).
 
Three pointed out that legal complications might occur in countries
where laws are specified in terms of solar time, or GMT (which has not
existed for thirty years).  Although one of these responders feared
governments would not follow the scientist's lead, we find it difficult
to believe that governments would, on their own, choose to add leap
seconds.  Others thought that any legal system flexible enough to
handle daylight savings time and the past abandonment of GMT in favor of
UTC would easily accommodate a seamless change in UTC's computation,
especially if no other time standard were available.  Some of the
history of legal issues concerning past changes in time definition can
be found in the book "Greenwich Time and Longitude" by Derek Howse.
 
Three thought we should not adopt a system which will fail in the long
run, even if that is a very distant time in the future.  (It could be
pointed out that all current time systems will eventually fail.  Well
before 2050 we could be routinely adding more than one leap second per
year, and when we reach the point where a day is 48 hours long we
would have to add a leap second every second.  Even the Gregorian
calendar will eventually need revision because in a few million years
the Earth will rotate less than 365 times per year, and leap days will
not be necessary.)
 
Two thought this would deprive the timing community of free publicity
when leap seconds are inserted.
 
Thirty-eight expressed opposition, but gave no specific reason. Eleven
of those also indicated that a problem would exist with their system,
but did not specify it.  Some of these pointed out that TAI was readily
available, or indicated that they had seen no justification for a
change.  (We had intentionally provided no justification in the initial
questionnaire, but two responders replied that they still believed
there was not enough reason to change even after having read "standard
response".)
 
Four were against it because they thought problems would happen if some
systems did not use the new system, and because they thought one would
have to separate analyses based upon whether data were recorded with
the current system or the old system.  (We believe these to be based
upon a misunderstanding of the "no new leap seconds" proposal, but
entirely possible if the more drastic measure of re-defining SI, the
International Second, were adopted.)
 
II.  Alternative Suggestions
 
Five suggested that it would be better to redefine the second to be
longer, add 1 second every 18 months forever, change on leap years or
century-ends, or change when the number exceeded a fixed amount. These
possibilities are also discussed in the GPS World Article.
 
A suggestion was received to add enough "negative leap seconds" to
bring UTC in line with GPS.  However, a different responder pointed out
that many of NASA's programs assume UT1-UTC always grows and that
problems would happen with any change that would sometimes lead to a
"negative leap second". (According to Dennis McCarthy of the USNO, this
is possible even with the current system, but unlikely).
 
It was also pointed out that rubidium atomic fountains or optical
standards could lead to a redefinition of the second using an element 
other than cesium.  If so, it could be redefined using a scale factor
of sufficient magnitude to avoid the short-term need for leap seconds 
(As noted in the GPS World article, such a change would alter the 
values of those physical quantities that depend upon time.)
 
One suggested that a redefined UTC should have a new name.
 
III. Responses in favor of changing the current leap second procedures
 
Forty-eight responses in favor were received, several from people who
experienced minor problems now in handling leap seconds, such as
confusion due to GPS time being currently 13 seconds offset from UTC
and computer errors at the time of the leap seconds. Along with
responses based upon reasons already covered in the GPS World Article,
there were also three from the highly undersampled group of computer
programmers, which pointed out the growing need to synchronize diverse
computers to one second accuracy and the difficulties of doing so in an
when dates of future leap seconds were unpredictable. Many of the 
responses indicated that periodic addition of leap seconds on a scheduled 
basis would also be acceptable.  One of the responders, who was opposed to 
a change, suggested that leap seconds were not a problem because computer 
users could program an automatic extraction of the needed information from 
some publicly available source; however it must be pointed out that no 
one can guarantee that a given file, whether it be for leap seconds or 
for daily values of UT1-UTC (see part IV, below), will remain forever 
available in a given format or given IP address.   
 
Four responses were from people who indicated that the convenience in
not having to update files every 18 months outweighed the expense and
problems rewriting software.  One of these suggested the use of
sufficient negative leap seconds to bring UTC in line with TAI, and
several noted that UT1-users easily incorporate the offsets due to 
time zones and daylight time.
 
IV. Other Responses
 
Forty-seven responders checked the "indifferent" option.  Most
indicated that there would be no problems with their system, or that
the problems were small enough that they were indifferent to a change.
 
Seven other responders indicated that the change would be okay if they
could somehow reliably obtain UT1-UTC.  (The USNO, as a sub-bureau of
the IERS, freely provides this information on its web site, http://www.
maia.usno.navy.mil, and via weekly emailings.  Other organizations also
provide this information.)  Some responses tabulated here were phrased
in the negative because the responders were apparently unaware that the
information was available.  One responder was concerned that the GPS
system itself would be degraded for this reason, however this is not
the case because GPS currently uses UT1-UTC values derived from USNO
products.

________________________________________________________________________
 
Appendix I. Questionnaire
 
It is being proposed to change the definition of Coordinated Universal
Time (UTC) regarding the insertion of leap seconds, possibly even
eliminating their use.  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, with Demetrios Matsakis being the chair.
 
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)
 
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.
 
I am attaching a list of institutions and persons contacted, except
for 931 institutions whose emails were obtained from the AAS. I would
like to apologize to anyone contacted twice, but also appreciate it if
you would forward this email to anyone we have missed.  Also, if you
are an URSI Commission J national chair, we would appreciate your
forwarding this email to your complete membership and in particular to
the directors of observatories.

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
________________________________________________________________________

Appendix II. Distribution List
 
Efforts were made to conduct an international survey, and responses
were received from Europe, Japan, China, Australia, Canada, Russia,
Saudi Arabia, Brazil, and other countries.  The majority of the
responses, however, were from the U.S.   Commercial interests, such as
satellite companies, were highly undersampled.  The questionnaire asked
people to forward it to others, and we know the following were
contacted:
 
1. 128 prominent scientists, who were mostly URSI Commission J members
and official representatives of institutions associated with URSI.
 
2. 27 URSI Commission J national chairs.
 
3. 931 Institutions extracted from a database kept by the American
Astronomical Society, including many from outside the United States.
Several hundred of those email addresses proved invalid.
 
4. All on the USNO Series 7 mailing list.
 
5. All on the "Gazette" mailing list of the International Earth
Rotation Service (IERS).  This would be expected to include most 
scientific groups that are directly involved with UT1.
 
6. One responder who worked in SETI indicated he had forwarded it to
SETI circles.
 
7. The Internet Engineering Task Force's mail exploder.
 
8. One responder, who was against any change, indicated he had forwarded
the questionnaire extensively around Jet Propulsion Labs (JPL).

________________________________________________________________________

Appendix III.  "Standard Reply" to queries concerning the questionnaire

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, particularly those using 
spread-spectrum techniques, 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  Wed Jul  5 11:00:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA07859
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 11:00:02 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07179
	for <ietf@ietf.org>; Wed, 5 Jul 2000 10:44:47 -0400 (EDT)
Received: from [10.0.0.3] (nix.swip.net [192.71.220.2]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id QAA20268; 
          Wed, 5 Jul 2000 16:43:32 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@127.0.0.1
Message-Id: <p0432042cb588f9f7ee47@[10.0.0.3]>
In-Reply-To: 
 <71C4C55F198BD211B24F0000F842F15807ED9C39@reoexc6.reo.cpqcorp.net>
References: 
 <71C4C55F198BD211B24F0000F842F15807ED9C39@reoexc6.reo.cpqcorp.net>
Date: Wed, 5 Jul 2000 07:45:14 -0700
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>,
        "'Ashutosh Agarwal'" <ashutosha@planetasia.com>,
        "'Taylor, Johnny'" <Johnny.Taylor@ESPIRE.NET>
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: RE: Is WAP mobile Internet??
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 15.15 +0100 00-07-05, Parkinson, Jonathan wrote:
>I disagree, WAP, Wireless Application Protocol, Its a way of transmitting
>data I.E. to and from the Web. How does this not fall under the Internet
>Umbrella ?

Things connected to the "Internet" is able to exchange IP packets 
from other things connected to the "Internet".

"web" is one application which can run where one have access to the 
Internet, and in some cases, you can even access the data "on the 
web" by using other services, like WAP.

    Patrik Faltstrom
    Area Director, Applications Area



From owner-ietf-outbound  Wed Jul  5 11:20:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA08469
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 11:20:03 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08286
	for <ietf@ietf.org>; Wed, 5 Jul 2000 11:10:22 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 139qoU-000JqQ-00; Wed, 05 Jul 2000 08:10:10 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Cc: ietf@ietf.org
Subject: RE: Is WAP mobile Internet??
References: <71C4C55F198BD211B24F0000F842F15807ED9C39@reoexc6.reo.cpqcorp.net>
	<p0432042cb588f9f7ee47@[10.0.0.3]>
Message-Id: <E139qoU-000JqQ-00@rip.psg.com>
Date: Wed, 05 Jul 2000 08:10:10 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

if i have a device which can only send and receive email, am i "on the
internet?"

if i have a device that lets me send and receive messages to/from internet
users, am i "on the internet"

note that sms with a gateway satisfies the last one.

my point is not to push sms or whatever.  but that by "on the internet" i
think we mean having unincumbered availability of the common application
protocols, email, http, ftp, ssh, ...  i may not choose to use/install them
all, but the commumications technology i use (note this did not say the end
device) should not prevent me from doing so.

e.g. that one-chip web server, with no human interface, is indeed "on the
internet."  a wap phone is not internet, it's waporware <tm>!

randy



From owner-ietf-outbound  Wed Jul  5 11:30:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA08626
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 11:30:03 -0400 (EDT)
Received: from velma.seeglasgow.com (velma.seeglasgow.com [212.250.141.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08427
	for <ietf@ietf.org>; Wed, 5 Jul 2000 11:18:49 -0400 (EDT)
Received: by velma.seeglasgow.com with Internet Mail Service (5.5.2650.21)
	id <NG93QYN5>; Wed, 5 Jul 2000 16:18:42 +0100
Message-ID: <91FBC84CBEF8D211AE2E0008C79F8A95302B85@velma.seeglasgow.com>
From: Stewart Nolan <stewart.nolan@seeglasgow.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Is WAP mobile Internet??
Date: Wed, 5 Jul 2000 16:18:41 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

I think mobile internet is misleading. (A subset of)mobile web perhaps, but
not mobile internet. What about services such as SMTP/Telnet/Usenet? These
are not protocols that a WAP Browser will deal with, it might emulate the
services provided via WAP, but it won't do it natively. The web sits atop
the internet, as do the protocols mentioned, as does WAP.

bcnu,
sn

> -----Original Message-----
> From: Parkinson, Jonathan [mailto:Jonathan.Parkinson@compaq.com]
> Sent: 05 July 2000 15:15
> To: 'Ashutosh Agarwal'; 'Taylor, Johnny'
> Cc: 'ietf@ietf.org'
> Subject: RE: Is WAP mobile Internet??
> 
> 
> I disagree, WAP, Wireless Application Protocol, Its a way of 
> transmitting
> data I.E. to and from the Web. How does this not fall under 
> the Internet
> Umbrella ?
> 
> Thanks
> Jon
> 
> -----Original Message-----
> From: Ashutosh Agarwal [mailto:ashutosha@planetasia.com]
> Sent: Wednesday, July 05, 2000 2:25 PM
> To: 'Taylor, Johnny'
> Cc: 'ietf@ietf.org'
> Subject: RE: Is WAP mobile Internet??
> 
> 
> Hi all,
> I fully agree with Lars. Even I believe WAP does not fall 
> under the Internet
> Umbrella
> 
> 
> Ashutosh Agarwal	
> e-mail : ashutosha@planetasia.com
> --------------------------------------------------------------
> ----------
> Change your thoughts and you change your world.
> 							The Buddha 
> --------------------------------------------------------------
> ----------
> 
> > -----Original Message-----
> > From:	Taylor, Johnny [SMTP:Johnny.Taylor@espire.net]
> > Sent:	Tuesday, July 04, 2000 12:15 AM
> > To:	Lars-Erik Jonsson; ietf@ietf.org
> > Subject:	RE: Is WAP mobile Internet??
> > 
> > The Internet allows all protocols to in-operate with her. 
> This is the
> > uniqueness
> > of the web. Therefore WAP falls within this area!
> > 
> > -----Original Message-----
> > From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ericsson.com]
> > Sent: Friday, June 30, 2000 7:54 AM
> > To: ietf@ietf.org
> > Subject: Is WAP mobile Internet??
> > 
> > 
> > Hi Folks!!
> > 
> > I would like to hear your opinions about how WAP people 
> often say that WAP
> > is
> > "mobile Internet". In my opinion, WAP is NOT mobile 
> Internet at all. The
> > Internet is built on the e2e principle and based on the Internet
> > Protocols,
> > which WAP is not. I can not tell people that they should 
> not use WAP (even
> > if I
> > have my opinions about WAP). If they believe in WAP that is 
> their problem,
> > but
> > when they try to use the words WAP and Internet in the same 
> sentence I
> > think
> > it
> > is time to clarify a few things. I accept that WAP is 
> there, but be honest
> > about
> > what it is.
> > 
> > Cheers!
> > /Lars-Erik (expressing my PERSONAL opinions)
> 



From owner-ietf-outbound  Wed Jul  5 11:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA09014
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 11:40:03 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA08444
	for <ietf@ietf.org>; Wed, 5 Jul 2000 11:19:52 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.07722-0@bells.cs.ucl.ac.uk>; Wed, 5 Jul 2000 16:19:26 +0100
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
cc: "'ietf@ietf.org'" <ietf@ietf.org>, J.Crowcroft@CS.UCL.AC.UK
Subject: Re: Is WAP mobile Internet??
In-reply-to: Your message of "Wed, 05 Jul 2000 15:15:13 BST." <71C4C55F198BD211B24F0000F842F15807ED9C39@reoexc6.reo.cpqcorp.net>
Date: Wed, 05 Jul 2000 16:19:23 +0100
Message-ID: <8567.962810363@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <71C4C55F198BD211B24F0000F842F15807ED9C39@reoexc6.reo.cpqcorp.net>, 
"Parkinson, Jonathan" typed:

 >>I disagree, WAP, Wireless Application Protocol, Its a way of transmitting
 >>data I.E. to and from the Web. How does this not fall under the Internet
 >>Umbrella ?

1 youcan't get at an arbirtrary web page
2/ you can't get at an arbitraty application written on TCP/IP or
UDP/IP

ergo its not internet, its not Internet, and its not provided by
Internet Service Providers, and this is Very Silly

WAP is quite a neat idea but its a prototype - as folks have said, SMS
is very cool - generalisations of it are cooler - native IP based ones
cooler stil coz then your application base can benefot from the
breadth and depth of stuff that people develop all around the world
for IP and the disciplines and understanding of markets that ISPs now
have......

mobile telephony service providers have a reasonable understanding of
one thing - telephony, based in years of fixed/wireline telephony -
however, this doesnt mean they haev much of a clue when it comes to
software based services that people are exponentiateding in the native
IP world......

 
 >>Thanks
 >>Jon
 >>
 >>-----Original Message-----
 >>From: Ashutosh Agarwal [mailto:ashutosha@planetasia.com]
 >>Sent: Wednesday, July 05, 2000 2:25 PM
 >>To: 'Taylor, Johnny'
 >>Cc: 'ietf@ietf.org'
 >>Subject: RE: Is WAP mobile Internet??
 >>
 >>
 >>Hi all,
 >>I fully agree with Lars. Even I believe WAP does not fall under the Internet
 >>Umbrella
 >>
 >>
 >>Ashutosh Agarwal	
 >>e-mail : ashutosha@planetasia.com
 >>------------------------------------------------------------------------
 >>Change your thoughts and you change your world.
 >>							The Buddha 
 >>------------------------------------------------------------------------
 >>
 >>> -----Original Message-----
 >>> From:	Taylor, Johnny [SMTP:Johnny.Taylor@espire.net]
 >>> Sent:	Tuesday, July 04, 2000 12:15 AM
 >>> To:	Lars-Erik Jonsson; ietf@ietf.org
 >>> Subject:	RE: Is WAP mobile Internet??
 >>> 
 >>> The Internet allows all protocols to in-operate with her. This is the
 >>> uniqueness
 >>> of the web. Therefore WAP falls within this area!
 >>> 
 >>> -----Original Message-----
 >>> From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ericsson.com]
 >>> Sent: Friday, June 30, 2000 7:54 AM
 >>> To: ietf@ietf.org
 >>> Subject: Is WAP mobile Internet??
 >>> 
 >>> 
 >>> Hi Folks!!
 >>> 
 >>> I would like to hear your opinions about how WAP people often say that WAP
 >>> is
 >>> "mobile Internet". In my opinion, WAP is NOT mobile Internet at all. The
 >>> Internet is built on the e2e principle and based on the Internet
 >>> Protocols,
 >>> which WAP is not. I can not tell people that they should not use WAP (even
 >>> if I
 >>> have my opinions about WAP). If they believe in WAP that is their problem,
 >>> but
 >>> when they try to use the words WAP and Internet in the same sentence I
 >>> think
 >>> it
 >>> is time to clarify a few things. I accept that WAP is there, but be honest
 >>> about
 >>> what it is.
 >>> 
 >>> Cheers!
 >>> /Lars-Erik (expressing my PERSONAL opinions)
 >>

 cheers

   jon



From owner-ietf-outbound  Wed Jul  5 11:50:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA09194
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 11:50:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@[131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09110
	for <ietf@ietf.org>; Wed, 5 Jul 2000 11:45:36 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 139rMT-0002a6-00; Wed, 05 Jul 2000 16:45:17 +0100
Date: Wed, 5 Jul 2000 16:45:13 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: TSIGARIDAS PANAGIOTIS <P.TSIGARIDAS@telestet.gr>
cc: Lars-Erik Jonsson <lars-erik.jonsson@ericsson.com>, ietf@ietf.org
Subject: RE: Is WAP mobile Internet??
In-Reply-To: <6ADD5A0DF6B1D31193430090279A2A08E45044@mail.telestet.gr>
Message-ID: <Pine.GSO.4.21.0007051637060.3480-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Wed, 5 Jul 2000, TSIGARIDAS PANAGIOTIS wrote:

> WAP is using existing Internet standards.  The WAP architecture was designed
> to enable standard Internet servers to provide services to wireless devices.
> In addition, when communicating with wireless devices, WAP uses many
> Internet standards such as XML, UDP and IP.

XML is not an Internet standard.


 The WAP wireless protocols are
> based on Internet standards such as HTTP and TLS

HTTP and TLS are proposed standards at this time. They are not
Internet standards.


> WAP Forum is working closely with the W3C (World Wide Web
> Consortium) and the IETF (Internet Engineering Task Force) 
> to ensure that the future versions of HTML, HTTP and TCP will
> accommodate the special needs of mobile devices and can be supported
> in the WAP framework.

What future versions of HTML?

L.

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



From owner-ietf-outbound  Wed Jul  5 12:00:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA09388
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 12:00:03 -0400 (EDT)
Received: from svanekaer.dk (qmailr@[129.142.164.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA09268
	for <ietf@ietf.org>; Wed, 5 Jul 2000 11:52:27 -0400 (EDT)
Received: (qmail 83383 invoked by uid 1011); 5 Jul 2000 15:52:27 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 5 Jul 2000 15:52:27 -0000
Date: Wed, 5 Jul 2000 17:52:27 +0200 (CEST)
From: Steven Cotton <steven@cotton.dk>
X-Sender: steven@localhost
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Is WAP mobile Internet??
In-Reply-To: <91FBC84CBEF8D211AE2E0008C79F8A95302B85@velma.seeglasgow.com>
Message-ID: <Pine.BSF.4.21.0007051746470.8308-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Wed, 5 Jul 2000, Stewart Nolan wrote:

> The web sits atop the internet, as do the protocols mentioned, as does
> WAP.

Yes - the Internet in my mind is just a collection of protocols, be they
what they may. Over what physical medium data travel is irrelevant, but
doesn't the term "on the Internet" mean the object can query and be
queryied, over this infrastructure?

-- 
steven




From owner-ietf-outbound  Wed Jul  5 12:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA09952
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 12:10:02 -0400 (EDT)
Received: from imo-d04.mx.aol.com (imo-d04.mx.aol.com [205.188.157.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09615
	for <ietf@ietf.org>; Wed, 5 Jul 2000 12:03:40 -0400 (EDT)
From: DQuade2502@aol.com
Received: from DQuade2502@aol.com
	by imo-d04.mx.aol.com (mail_out_v27.10.) id l.35.71e8ac9 (3893)
	 for <ietf@ietf.org>; Wed, 5 Jul 2000 12:03:05 -0400 (EDT)
Message-ID: <35.71e8ac9.2694b639@aol.com>
Date: Wed, 5 Jul 2000 12:03:05 EDT
Subject: (no subject)
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Windows sub 68
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

 



From owner-ietf-outbound  Wed Jul  5 12:20:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10324
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 12:20:04 -0400 (EDT)
Received: from ljcqs016.cnf.com ([205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10047
	for <ietf@ietf.org>; Wed, 5 Jul 2000 12:13:01 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id JAA06512
	for <ietf@ietf.org>; Wed, 5 Jul 2000 09:12:32 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <3C76CCJR>; Wed, 5 Jul 2000 16:10:24 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D2D0@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Is WAP mobile Internet??
Date: Wed, 5 Jul 2000 16:11:53 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

->-----Original Message-----
->From: Jon Crowcroft [mailto:J.Crowcroft@cs.ucl.ac.uk]
->Sent: Wednesday, July 05, 2000 11:19 AM
->To: Parkinson, Jonathan
->Cc: 'ietf@ietf.org'; J.Crowcroft@cs.ucl.ac.uk
->Subject: Re: Is WAP mobile Internet??
->
->
->
->In message 
-><71C4C55F198BD211B24F0000F842F15807ED9C39@reoexc6.reo.cpqcorp.net>, 
->"Parkinson, Jonathan" typed:
->
-> >>I disagree, WAP, Wireless Application Protocol, Its a way 
->of transmitting
-> >>data I.E. to and from the Web. How does this not fall 
->under the Internet
-> >>Umbrella ?
->
->1 youcan't get at an arbirtrary web page
->2/ you can't get at an arbitraty application written on TCP/IP or
->UDP/IP


Jon, I wonder how WAP will fit into  Multicast apps - even 
if its single line txt based msg's app ?

/pd



From owner-ietf-outbound  Wed Jul  5 12:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10687
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 12:30:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@[128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10359
	for <ietf@ietf.org>; Wed, 5 Jul 2000 12:20:36 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@localhost [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta4/8.11.0.Beta4) with ESMTP id e65GKXS33484
	for <ietf@ietf.org>; Wed, 5 Jul 2000 12:20:33 -0400
Message-Id: <200007051620.e65GKXS33484@black-ice.cc.vt.edu>
To: ietf@ietf.org
Subject: Re: WAP - What A Problem... 
In-reply-to: Your message of "Wed, 05 Jul 2000 15:26:13 +0200."
             <003601bfe684$97e6cc60$0a00000a@abo.wanadoo.fr> 
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: <11C39F7E0407D411AF1000D0B7475FDE4A96C3@PNTEXCH04.hq.espire.net> <39632AA0.9CB28F0B@msdw.com>
            <003601bfe684$97e6cc60$0a00000a@abo.wanadoo.fr>
Date: Wed, 05 Jul 2000 12:20:33 -0400
X-Loop: ietf@ietf.org

On Wed, 05 Jul 2000 15:26:13 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
> > I'd have to disagree there. The 8 million non-WAP users
> > in Japan are unarguably enjoying the most prolific, robust,
> > and deep wireless Internet available today.
> 
> We still have more than five billion users who aren't even online yet.  They
> haven't enjoyed anything thus far.
> 

Umm.. A large fraction of those 5 billion would settle for
clean drinking water and some protien in their diet...



From owner-ietf-outbound  Wed Jul  5 12:40:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA11088
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 12:40:04 -0400 (EDT)
Received: from kenny.netrail.net ([205.215.10.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10574
	for <ietf@ietf.org>; Wed, 5 Jul 2000 12:25:34 -0400 (EDT)
Received: from rcutts (kenny.netrail.net [205.215.10.5])
	by kenny.netrail.net (8.9.3/8.9.3) with SMTP id MAA06175;
	Wed, 5 Jul 2000 12:26:17 -0400 (EDT)
From: "Raymond Cutts Jr." <rcutts@netrail.net>
To: "Taylor, Johnny" <Johnny.Taylor@espire.net>,
        "Anthony Atkielski" <anthony@atkielski.com>, <ietf@ietf.org>
Cc: "Kevin Clements \(E-mail\)" <kclement@morehouse.edu>,
        "Kevin Lampkin \(E-mail\)" <kevin.lampkin@wcom.com>,
        "Robert Scott \(E-mail\)" <Rob.Scott@wcom.com>
Subject: RE: WAP - What A Problem...
Date: Wed, 5 Jul 2000 12:27:21 -0400
Message-ID: <KEEOJAIPJAIEPPKFOAJJAEILCAAA.rcutts@netrail.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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
In-Reply-To: <11C39F7E0407D411AF1000D0B7475FDE4A96C3@PNTEXCH04.hq.espire.net>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I think you both makes some good points.  However, the main issue is: "Will
there be a NEED for some type of Wireless Application?" ...and the
Undisputable answer is: "Absolutely".

Now, whether the ultimate STANDARD will be WAP or some other application is
somewhat irrelevant.  The bottom line is there WILL BE some wireless
application(s) that will become the preferred protocol(s) to transmit
information through RF.

Some of the arguments stated by the gentleman in the original e-mail are
some of the same type arguments stated 15 years ago, when cellular phones
initially came onto the consumer scene.  The argument(s) about the number of
user -vs- the capacity limitations, etc., etc., were all the same type
issues that the cellular industry overcame.  They will also be overcome in
the newer wireless information transmission industry; if by nothing else
than Economies of Scale.  As more and more people demand service, and more
and more money (lots of money) is thrown in this direction, the cost
justification for embarking on such ventures will become more and more
reasonable; and companies/individuals will invest their energy to make it
happen {and make a profit at the same time}.

As far as 'ergonomics', those issues will become non-issues, as well.  I
recently started work with a new company, and many of the employees use
"i-pagers".  If you are not familiar with i-pagers, they are paging units
(slightly larger than the miniature text pager) that are used predominately
for transmitting e-mail messages.  I have no problem reading through long
messages on the screen, which is smaller than a credit card.  Even when you
read through text on your computer screen, you never get the entire document
(or picture), thus you have to scroll up and/or down to read the entire
message.  This is the same thing with the smaller devices.  Also, these
i-pagers have a FULL "qwerty" style keyboard for typing messages; not ten
soft keys that need to be combined to type out one letter.  I actually find
this "mini-laptop" to be very useful, and I enjoy using it.  We also have a
wireless LAN, which everybody loves.  It's one of the most convenient
devices used widely in our office {and it works almost flawlessly}.

The bottom lines is that wireless devices provide convenience and
productivity, which land-line devices can not even begin to compete; thus,
wireless devices inherently capture a segment of the market unattainable by
land-line devices.  This provides for an extraordinary opportunity in the
Wireless Industry.  And as the land-line infrastructure continues to
increase, to accommodate higher bandwidth, the opportunities in the wireless
world will increase.

There is no question that the immediate opportunities are in increasing the
bandwidth for the land-line infrastructure.  The infrastructure must be
improved in order to provide next generation type applications for the
consumers.  Even if one could send Gigabit sized information through the
air, once it connect to a land based network, there will still be a
bottle-neck if something is not done.  However, for longer-term
opportunities you must look to the wireless industry.  Once the build-out of
the land-line network is complete (or as complete as necessary), there will
still be opportunities for value-added services.  This is where the wireless
services come into play.

Just take another look back at the cellular industry.  Who would have
thought that the number of wireless phone user would ever surpass the number
of land-line user? ...well were coming up on that reality very soon; and it
has already happened in several places.  Also, who would have thought that
the revenues from the wireless side of the Baby Bells would (or could) ever
exceed the mammoth revenues produced by their land-line business.  Well, the
revenues (and profits) from the wireless side of the Baby Bells have BLOWN
AWAY the revenues (and profits) of the traditional land-line business ....
and this took place many years ago.

Don't Sleep on the Wireless Industry.  The intensity of the current
situation is much more focused on the land-line infrastructure (as well as
it should be), but don't pack up your stuff and go home once that party is
over....because there is going to be an after-party.  It may not be "WAP",
it may not be one of the other "sexy" acronyms being thrown around ...., but
one thing you can be sure of: it will be something wireless.

Peace,
Raymond

-----Original Message-----
From: Taylor, Johnny [mailto:Johnny.Taylor@espire.net]
Sent: Monday, July 03, 2000 1:07 PM
To: Anthony Atkielski; ietf@ietf.org
Cc: Kevin Clements (E-mail); Kevin Lampkin (E-mail); Raymond Cutts
(E-mail); Robert Scott (E-mail)
Subject: RE: WAP - What A Problem...


Well I guess when you look at multiple technologies like
VR (voice recognition), VN (voice navigation), IA (intelligent agents),
& WAP of course, Then you begin to see the relationships and importance
of wireless applications. I concur with you on the point of land optics
however the average person requires remote and mobile access to their
corporate networks, intra-nets, extra-nets, and value-added-networks.
Therefore one could conclude that wireless access will have a main
space within future technologies. In addition to this point I would
like to also state WAP is the front runner in regards to linking
wireless apps to the Global Internet and her sub-nets. Also, I would
like to re-reference you to understanding Teledesic's network model.
This is where you can clearly see the wireless model @ work. In closing,
I would ask that you stay aware of WAP for this is not a govt technology,
it was formulated from people like you, me, & the members of IETF! And
it will play a major role in all of our lives from a protocol stand point.

Video to Video, Voice to Text, Broadcast to IP, Data to Voice = WAP(Display)

Coming From The Brain,

JT

-----Original Message-----
From: Anthony Atkielski [mailto:anthony@atkielski.com]
Sent: Friday, June 30, 2000 1:12 PM
To: ietf@ietf.org
Subject: Re: WAP - What A Problem...


> thats why intelsat and a cosortium of telcos has
> a charity that built a box that is solar powered
> and provides n gsm phones access + 1 64kbps uplink/
> downlink to geostatinary atellites

So that's what, 64/5 = 13 kbps per user?  Even as current Internet designs
require ever more bandwidth and strain even multi-megabit connections?  And
has anyone considered what happens when you have 6 million active ground
transceivers trying to communicate with a single satellite?

> actualyl, a LOT of places that are really poor in
> the world dont even have electricty- but they can get
> batteries and if they use sms (e.g. for calling
> emergency service/flying doctors/vets etc), they
> can make them last quite a long time

Why use SMS instead of just voice?

Has anyone considered the ergonomics of WAP?  Even if it works perfectly,
how many people are willing to work on a screen smaller than a credit card?
How many people are capable of touch-typing on a keyboard with only ten soft
keys that must be pressed in various arcane combinations for almost ever
letter?  It just doesn't make intuitive sense.

Anyway, I have a really good instinct for picking technology winners, and
thus far I put WAP in the same category as MiniDiscs, bubble memory, color
fax machines, and quadraphonic sound.  I think the growth area is in
broadband land-based links; I don't understand why people have flown off on
tangents towards wireless when land links are just starting to come into
their own.  I suspect it is more politically motivated than technically
motivated, and that is one reason why I think it will fail.  A lot of time
and effort is being wasted on WAP.





From owner-ietf-outbound  Wed Jul  5 12:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA11313
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 12:50:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@[131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10582
	for <ietf@ietf.org>; Wed, 5 Jul 2000 12:25:36 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 139rzN-0002sL-00; Wed, 05 Jul 2000 17:25:29 +0100
Date: Wed, 5 Jul 2000 17:25:26 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Randy Bush <randy@psg.com>
cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@SWIP.NET>, ietf@ietf.org
Subject: RE: Is WAP mobile Internet??
In-Reply-To: <E139qoU-000JqQ-00@rip.psg.com>
Message-ID: <Pine.GSO.4.21.0007051721560.3480-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Wed, 5 Jul 2000, Randy Bush wrote:

> my point is not to push sms or whatever.  but that by "on the internet" i
> think we mean having unincumbered availability of the common application
> protocols, email, http, ftp, ssh, ...  

that's not quite enough; in the UK we're seeing cable-modem ISPs
attempt to restrict services to those applications, or to a subset of 
those applications (lotsa luck setting up an http server or using
ssh.)

being on the Internet means that you can choose to deploy and use new
Internet applications that use the Internet in new ways...

> i may not choose to use/install them
> all, but the commumications technology i use (note this did not say the end
> device) should not prevent me from doing so.

...without having to ask some telco's permission or pay more to enable
the ability. (This is distinct from charging for extreme capacity
use.)

L.

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



From owner-ietf-outbound  Wed Jul  5 13:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA11574
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 13:00:02 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA11520
	for <ietf@ietf.org>; Wed, 5 Jul 2000 12:59:27 -0400 (EDT)
Received: from eucharisto.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.15096-0@bells.cs.ucl.ac.uk>; Wed, 5 Jul 2000 17:59:21 +0100
To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: Is WAP mobile Internet??
In-reply-to: Your message of "Wed, 05 Jul 2000 16:11:53 -0000." <C7091526C06AD211A7450004AC384A350C35D2D0@mwabs035.emeryworld.com>
Date: Wed, 05 Jul 2000 17:59:18 +0100
Message-ID: <2174.962816358@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


 >>Jon, I wonder how WAP will fit into  Multicast apps - even 
 >>if its single line txt based msg's app ?
 
football scores/(tennis etc)

share price (look at stockbroker trading terminal - they have very
small amount of realestate for the given instrument)

many many things would work v. well  - iff you had full ip capability...

i guess you'd need an rtp mixer capability in the net for packet ip multiast as
mixing at the receiver might stress the limited capacity...although as
next generation rolls out, this might change too then ip voice
conferencing using multicast (which kind of maps well onto real shared
capacity channels anyhow) would be quite cute...

a lot of sip stuff would be v. cute too (a lot of fancy call handling
scripting things would be dead useful to be able to download onto the
phone.....).......

 cheers

   jon



From owner-ietf-outbound  Wed Jul  5 13:10:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA11927
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 13:10:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11858
	for <ietf@ietf.org>; Wed, 5 Jul 2000 13:05:23 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id LAA10522
	for ietf@ietf.org  env-from <vjs>;
	Wed, 5 Jul 2000 11:05:23 -0600 (MDT)
Date: Wed, 5 Jul 2000 11:05:23 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007051705.LAA10522@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: Is WAP mobile Internet??
X-Loop: ietf@ietf.org

> From: Lloyd Wood <l.wood@eim.surrey.ac.uk>

> ...
> > my point is not to push sms or whatever.  but that by "on the internet" i
> > think we mean having unincumbered availability of the common application
> > protocols, email, http, ftp, ssh, ...  
>
> that's not quite enough; in the UK we're seeing cable-modem ISPs
> attempt to restrict services to those applications, or to a subset of 
> those applications (lotsa luck setting up an http server or using
> ssh.)
> ...

and also like AOL's redirecting proxies for out-bound SMTP?
and the port-25 filtering of many ISP's including UUNET?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Wed Jul  5 13:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA12396
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 13:30:02 -0400 (EDT)
Received: from ibd.ar.com (ibd.ar.com [63.194.205.75])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12243
	for <ietf@ietf.org>; Wed, 5 Jul 2000 13:22:19 -0400 (EDT)
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 KAA24869;
	Wed, 5 Jul 2000 10:22:11 -0700 (PDT)
Date: Wed, 5 Jul 2000 10:22:11 -0700 (PDT)
From: Rick H Wesson <wessorh@ar.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: RE: Is WAP mobile Internet??
In-Reply-To: <200007051705.LAA10522@calcite.rhyolite.com>
Message-ID: <Pine.LNX.4.10.10007051020150.20774-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


Vernon,

would pacbell filtering all multicast at all CPE equipemt fall into your 
bucket, where do you draw the line?

-rick

On Wed, 5 Jul 2000, Vernon Schryver wrote:

> > From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
> 
> > ...
> > > my point is not to push sms or whatever.  but that by "on the internet" i
> > > think we mean having unincumbered availability of the common application
> > > protocols, email, http, ftp, ssh, ...  
> >
> > that's not quite enough; in the UK we're seeing cable-modem ISPs
> > attempt to restrict services to those applications, or to a subset of 
> > those applications (lotsa luck setting up an http server or using
> > ssh.)
> > ...
> 
> and also like AOL's redirecting proxies for out-bound SMTP?
> and the port-25 filtering of many ISP's including UUNET?
> 
> 
> Vernon Schryver    vjs@rhyolite.com
> 



From owner-ietf-outbound  Wed Jul  5 14:11:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA13220
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 14:10:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13080
	for <ietf@ietf.org>; Wed, 5 Jul 2000 14:02:32 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id MAA12030
	for ietf@ietf.org  env-from <vjs>;
	Wed, 5 Jul 2000 12:02:33 -0600 (MDT)
Date: Wed, 5 Jul 2000 12:02:33 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007051802.MAA12030@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: Is WAP mobile Internet??
X-Loop: ietf@ietf.org

> > > > think we mean having unincumbered availability of the common application
> > > > protocols, email, http, ftp, ssh, ...  
> > >
> > > that's not quite enough; in the UK we're seeing cable-modem ISPs
> > > attempt to restrict services to those applications, or to a subset of 
> > > those applications (lotsa luck setting up an http server or using
> > > ssh.)
> > > ...
> > 
> > and also like AOL's redirecting proxies for out-bound SMTP?
> > and the port-25 filtering of many ISP's including UUNET?


> From: Rick H Wesson <wessorh@ar.com>

> would pacbell filtering all multicast at all CPE equipemt fall into your 
> bucket, where do you draw the line?

I think it depends on motives.  Port 25 filtering and SMTP redirecting
proxies exist for the same reasons slumlords put bulletproof glass in
their windows and chainlink fencing on their balconies instead of evicting
or otherwise dealing with criminals.  Port 25 filtering and SMTP
redirecting is easier but more expensive in the long run than enforcing
strong terms of service, such as $500/day clean-up fees.  HTTP redirecting
proxies sometimes have much worse, completely intolerable motives, from
unvarnish government censorship of political speech to inserting ads.

Historically multicast was filtered because routers didn't know about it
and those operating them no better informed and caring even less.  Today,
I can still imagine some technical motives for filtering multicast packets.
They would be defensible for a while.  I know nothing about what PacBell
is doing now, but they're filtering class-D addresses for any except real
technical reasons that they honestly plan to fix, then they are not selling
Internet access.  If they are advertising otherwise, then appropriate
legal steps should be taken.

Instead of silly blathering about getting wireless phones and SuperHypeWay
access to the billions of people who currently have neither those modern
necessities, reasonable food or shelter, or even per capita incomes of
$1000/year, those who care about the Internet should be worrying about
the efforts of the old media and communications outfits to transform the
Internet into something they know, whether POTS or TV.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Wed Jul  5 14:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA13795
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 14:40:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13463
	for <ietf@ietf.org>; Wed, 5 Jul 2000 14:20:20 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA24859;
        Wed, 5 Jul 2000 14:20:17 -0400 (EDT)
Message-Id: <200007051820.OAA24859@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Randy Bush <randy@psg.com>
cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@SWIP.NET>, ietf@ietf.org
Subject: Re: Is WAP mobile Internet?? 
In-reply-to: Your message of "Wed, 05 Jul 2000 08:10:10 PDT."
             <E139qoU-000JqQ-00@rip.psg.com> 
Date: Wed, 05 Jul 2000 14:20:17 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> but that by "on the internet" i
>think we mean having unincumbered availability of the common application
>protocols, email, http, ftp, ssh, ...  

I'd go farther than that.  Internet access includes only only the 
ability to use the common protocols, but also the uncommon ones -
indeed, any protocol that works over IP.

some folks tend to think that as long as the popular protocols 
(as measured by counts of packets with certain port numbers)
are handled this is good enough.   there are at least two fallacies
here - (1) it assumes that the Internet is static and that no
new protocols need be accomodated and (2) it assumes that there
is a relationship between the amount of bandwidth used by a protocol
and the importance of that protocol.

IMHO, one of the most important features of the Internet is its 
flexibility, and in particular, its ability to handle arbitrary 
protocols as long as they can run over IP.  

Keith



From owner-ietf-outbound  Wed Jul  5 19:01:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA18306
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 19:00:02 -0400 (EDT)
Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18245
	for <ietf@ietf.org>; Wed, 5 Jul 2000 18:51:31 -0400 (EDT)
Received: from computer.ix.netcom.com ([209.138.155.46])
	by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id SAA23880
	for <ietf@ietf.org>; Wed, 5 Jul 2000 18:51:25 -0400 (EDT)
Message-Id: <4.3.1.2.20000705175039.00bd19e0@127.0.0.1>
X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 05 Jul 2000 17:51:39 -0500
To: ietf@ietf.org
From: Richard Shockey <rshockey@ix.netcom.com>
Subject: Fwd: FC: Pittsburgh politicos don't like criticism at
  anonymous web site
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org


News from our host city.......


>>Date: Wed, 05 Jul 2000 00:14:02 -0700
>>Subject: Online criticism of politicians draws lawsuit
>>From: Jack Dean <JackDean@InternetCampaigns.com>
>>To: Declan McCullagh <declan@well.com>
>>
>>
>>Online criticism of politicians draws lawsuit
>>City: Pittsburgh, State: PA, Country: United States
>>    Government officials in Pittsburgh have launched a courtroom
>>    assault on a Web site that allows citizens to anonymously
>>    criticize the authorities. (6/30/00)
>>URL: http://www.tribunereview.com/news/pgs0630.html
>
>--------------------------------------------------------------------------
>POLITECH -- the moderated mailing list of politics and technology
>To subscribe, visit http://www.politechbot.com/info/subscribe.html
>This message is archived at http://www.politechbot.com/
>--------------------------------------------------------------------------



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Please Note New Contact Information:

Richard Shockey
Shockey Consulting LLC
5237 Sutherland
St. Louis, MO 63109
Voice 314.503.0640
eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
INTERNET Mail & IFAX : rshockey@ix.netcom.com
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<



From owner-ietf-outbound  Wed Jul  5 20:40:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA19559
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 20:40:02 -0400 (EDT)
Received: from mail-blue.research.att.com ([135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19496
	for <ietf@ietf.org>; Wed, 5 Jul 2000 20:36:46 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id C830E4CE04; Wed,  5 Jul 2000 20:36:47 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id UAA15169;
	Wed, 5 Jul 2000 20:36:46 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 5895635DC2; Wed,  5 Jul 2000 20:36:41 -0400 (EDT)
X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.3 #1[UCI]
From: "Steven M. Bellovin" <smb@research.att.com>
To: Richard Shockey <rshockey@ix.netcom.com>
Cc: ietf@ietf.org
Subject: Re: Fwd: FC: Pittsburgh politicos don't like criticism at anonymous web site 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 05 Jul 2000 20:36:41 -0400
Sender: smb@research.att.com
Message-Id: <20000706003641.5895635DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <4.3.1.2.20000705175039.00bd19e0@127.0.0.1>, Richard Shockey writes:
>
>News from our host city.......
>
>
>>>Date: Wed, 05 Jul 2000 00:14:02 -0700
>>>Subject: Online criticism of politicians draws lawsuit
>>>From: Jack Dean <JackDean@InternetCampaigns.com>
>>>To: Declan McCullagh <declan@well.com>
>>>
>>>
>>>Online criticism of politicians draws lawsuit
>>>City: Pittsburgh, State: PA, Country: United States
>>>    Government officials in Pittsburgh have launched a courtroom
>>>    assault on a Web site that allows citizens to anonymously
>>>    criticize the authorities. (6/30/00)
>>>URL: http://www.tribunereview.com/news/pgs0630.html

Sigh.  Judges should know better.  See, for example, 514 US 334 (on the 
Web via http://www.jurisline.com and lots of other cases.

		--Steve Bellovin




From owner-ietf-outbound  Wed Jul  5 21:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA20523
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 21:20:02 -0400 (EDT)
Received: from torque.pothole.com ([38.138.52.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20466
	for <ietf@ietf.org>; Wed, 5 Jul 2000 21:16:37 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id VAA14389
	for ietf@ietf.org; Wed, 5 Jul 2000 21:18:57 -0400 (EDT)
Message-Id: <200007060118.VAA14389@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: Fwd: FC: Pittsburgh politicos don't like criticism at anonymous web site
In-reply-to: Your message of "Wed, 05 Jul 2000 17:51:39 CDT."
             <4.3.1.2.20000705175039.00bd19e0@127.0.0.1> 
Date: Wed, 05 Jul 2000 21:18:57 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org

URL is typoed below.  It's really www.tribune-review.com
                                             ^
Donald

From:  Richard Shockey <rshockey@ix.netcom.com>
Message-Id:  <4.3.1.2.20000705175039.00bd19e0@127.0.0.1>
Date:  Wed, 05 Jul 2000 17:51:39 -0500
To:  ietf@ietf.org

>News from our host city.......
>
>>>Date: Wed, 05 Jul 2000 00:14:02 -0700
>>>Subject: Online criticism of politicians draws lawsuit
>>>From: Jack Dean <JackDean@InternetCampaigns.com>
>>>To: Declan McCullagh <declan@well.com>
>>>
>>>
>>>Online criticism of politicians draws lawsuit
>>>City: Pittsburgh, State: PA, Country: United States
>>>    Government officials in Pittsburgh have launched a courtroom
>>>    assault on a Web site that allows citizens to anonymously
>>>    criticize the authorities. (6/30/00)
>>>URL: http://www.tribunereview.com/news/pgs0630.html
>>
>>--------------------------------------------------------------------------
>>POLITECH -- the moderated mailing list of politics and technology
>>To subscribe, visit http://www.politechbot.com/info/subscribe.html
>>This message is archived at http://www.politechbot.com/
>>--------------------------------------------------------------------------
>
>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>Please Note New Contact Information:
>
>Richard Shockey
>Shockey Consulting LLC
>5237 Sutherland
>St. Louis, MO 63109
>Voice 314.503.0640
>eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
>INTERNET Mail & IFAX : rshockey@ix.netcom.com
><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>



From owner-ietf-outbound  Wed Jul  5 22:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA22087
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 22:00:02 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21988
	for <ietf@ietf.org>; Wed, 5 Jul 2000 21:54:45 -0400 (EDT)
Received: from [10.0.0.3] (nix.swip.net [192.71.220.2]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id DAA06444; 
          Thu, 6 Jul 2000 03:51:30 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@127.0.0.1
Message-Id: <p0432042eb5898e77cf8f@[10.0.0.3]>
In-Reply-To: 
 <Pine.GSO.4.21.0007051721560.3480-100000@petra.ee.surrey.ac.uk>
References: <Pine.GSO.4.21.0007051721560.3480-100000@petra.ee.surrey.ac.uk>
Date: Wed, 5 Jul 2000 18:22:37 -0700
To: Lloyd Wood <l.wood@eim.surrey.ac.uk>, Randy Bush <randy@psg.com>
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: RE: Is WAP mobile Internet??
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 17.25 +0100 00-07-05, Lloyd Wood wrote:
>  > i may not choose to use/install them
>  > all, but the commumications technology i use (note this did not say the end
>  > device) should not prevent me from doing so.
>
>...without having to ask some telco's permission or pay more to enable
>the ability. (This is distinct from charging for extreme capacity
>use.)

There is nothing wrong by providers selling you one thing (accessing 
data also available on the Internet) for one sum of money, and the 
ability to have Internet access for another (higher).

What I don't like is that providers sell non-Internet connections and 
then "charge more" for the abilities you list above (and others).

I.e. if they can produce something silly which the market buys, I 
don't see anything wrong with that -- but it should NOT be called 
Internet Access.

In Sweden we have rules for how much beef there have to be 
(percentage) for something to be called "meatballs". Other things are 
called "frying balls", "lean balls" etc. The same market-driven 
regulation should be true for "Internet Access".


    Patrik



From owner-ietf-outbound  Wed Jul  5 23:20:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA23694
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 23:20:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23652
	for <ietf@ietf.org>; Wed, 5 Jul 2000 23:13:00 -0400 (EDT)
Received: (from braden@localhost)
	by boreas.isi.edu (8.9.3/8.9.3) id UAA10989;
	Wed, 5 Jul 2000 20:13:01 -0700 (PDT)
Date: Wed, 5 Jul 2000 20:13:01 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Message-Id: <200007060313.UAA10989@boreas.isi.edu>
To: Jonathan.Parkinson@compaq.com
Subject: Re: Is WAP mobile Internet??
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org


  *> From owner-ietf-outbound@ietf.org Wed Jul  5 08:58:47 2000
  *> To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
  *> cc: "'ietf@ietf.org'" <ietf@ietf.org>, J.Crowcroft@cs.ucl.ac.uk
  *> Subject: Re: Is WAP mobile Internet??
  *> In-reply-to: Your message of "Wed, 05 Jul 2000 15:15:13 BST." <71C4C55F198BD211B24F0000F842F15807ED9C39@reoexc6.reo.cpqcorp.net>
  *> Date: Wed, 05 Jul 2000 16:19:23 +0100
  *> From: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>
  *> X-Loop: ietf@ietf.org
  *> Content-Length: 3148
  *> X-Lines: 95
  *> 
  *> 
  *> In message <71C4C55F198BD211B24F0000F842F15807ED9C39@reoexc6.reo.cpqcorp.net>, 
  *> "Parkinson, Jonathan" typed:
  *> 
  *>  >>I disagree, WAP, Wireless Application Protocol, Its a way of transmitting
  *>  >>data I.E. to and from the Web. How does this not fall under the Internet
  *>  >>Umbrella ?
  *> 

Jon Postel would have said: If it speaks IP (UDP/TCP are not
necessary), then it's Internet, else not.

However, during the 1980s the IAB tried to float the concept of an
extended Internet defined by email connectivity.

Bob Braden



From owner-ietf-outbound  Wed Jul  5 23:50:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA24343
	for ietf-outbound.10@ietf.org; Wed, 5 Jul 2000 23:50:03 -0400 (EDT)
Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24256
	for <ietf@ietf.org>; Wed, 5 Jul 2000 23:44:57 -0400 (EDT)
Received: from dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155])
	by piglet.dstc.edu.au (8.10.1/8.10.1) with ESMTP id e663iYb29075;
	Thu, 6 Jul 2000 13:44:34 +1000 (EST)
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: Bob Braden <braden@ISI.EDU>
cc: Jonathan.Parkinson@compaq.com, ietf@ietf.org
Subject: Re: Is WAP mobile Internet?? 
In-Reply-To: Message from Bob Braden <braden@ISI.EDU> 
   of "Wed, 05 Jul 2000 20:13:01 MST." <200007060313.UAA10989@boreas.isi.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 06 Jul 2000 13:44:39 +1000
Message-ID: <5315.962855079@dstc.edu.au>
From: George Michaelson <ggm@dstc.edu.au>
X-Loop: ietf@ietf.org


  Jon Postel would have said: If it speaks IP (UDP/TCP are not
  necessary), then it's Internet, else not.
  
I thought part of the argument was about capitalization of the I. if its
lowercase, then its using IP, if its uppercase then you can expect to use
global Internet addresses and achieve a substantive amount of end-to-end
connectivity. Of course, that was before NAT.

  However, during the 1980s the IAB tried to float the concept of an
  extended Internet defined by email connectivity.

Is this different to John Quartermains Matrix definition? Gosh, how
prescient to choose that word...
  
-George

--
George Michaelson         |  DSTC Pty Ltd
Email: ggm@dstc.edu.au    |  University of Qld 4072
Phone: +61 7 3365 4310    |  Australia
  Fax: +61 7 3365 4311    |  http://www.dstc.edu.au




From owner-ietf-outbound  Thu Jul  6 03:00:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA08773
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 03:00:02 -0400 (EDT)
Received: from mex.italtel.it ([138.132.117.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08706
	for <ietf@ietf.org>; Thu, 6 Jul 2000 02:52:53 -0400 (EDT)
Received: .(iltws72 [138.132.52.82]) by mex.italtel.it (8.9.0/8.9.0) with ESMTP id IAA24658
Received: .(localhost [127.0.0.1]) by iltws72.settimo.italtel.it (8.9.1a/8.9.1) with ESMTP
 id IAA23713
Received: from ic8u32.settimo.italtel.it (ic8u32.settimo.italtel.it [138.132.1.1])
	by mix.italtel.it (8.9.3/8.9.3) with SMTP id IAA18510;
	Thu, 6 Jul 2000 08:49:20 +0200 (MET DST)
Received: by ic8u32.settimo.italtel.it id AA14754; Thu, 6 Jul 2000 09:12:28 +0200
Received: from icn.siemens.it (localhost [127.0.0.1])
	by iltws09.settimo.italtel.it (8.10.1/8.10.1) with ESMTP id e666rht05506;
	Thu, 6 Jul 2000 08:53:43 +0200 (MET DST)
Sender: buschman@iltws09.settimo.italtel.it
Message-Id: <39642CF4.5D9BC998@icn.siemens.it>
Date: Thu, 06 Jul 2000 08:53:41 +0200
From: Jonathan Buschmann <Jonathan.Buschmann@icn.siemens.it>
Reply-To: Jonathan.Buschmann@icn.siemens.it
X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
Mime-Version: 1.0
To: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
Cc: ietf@ietf.org
Subject: Re: Fwd: FC: Pittsburgh politicos don't like criticism at anonymous web 
 site
References: <200007060118.VAA14389@torque.pothole.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

It worked for me.

"Donald E. Eastlake 3rd" wrote:

> URL is typoed below.  It's really www.tribune-review.com
>                                              ^
> Donald
>
> From:  Richard Shockey <rshockey@ix.netcom.com>
> Message-Id:  <4.3.1.2.20000705175039.00bd19e0@127.0.0.1>
> Date:  Wed, 05 Jul 2000 17:51:39 -0500
> To:  ietf@ietf.org
>
> >News from our host city.......
> >
> >>>Date: Wed, 05 Jul 2000 00:14:02 -0700
> >>>Subject: Online criticism of politicians draws lawsuit
> >>>From: Jack Dean <JackDean@InternetCampaigns.com>
> >>>To: Declan McCullagh <declan@well.com>
> >>>
> >>>
> >>>Online criticism of politicians draws lawsuit
> >>>City: Pittsburgh, State: PA, Country: United States
> >>>    Government officials in Pittsburgh have launched a courtroom
> >>>    assault on a Web site that allows citizens to anonymously
> >>>    criticize the authorities. (6/30/00)
> >>>URL: http://www.tribunereview.com/news/pgs0630.html
> >>
> >>--------------------------------------------------------------------------
> >>POLITECH -- the moderated mailing list of politics and technology
> >>To subscribe, visit http://www.politechbot.com/info/subscribe.html
> >>This message is archived at http://www.politechbot.com/
> >>--------------------------------------------------------------------------
> >
> >
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >Please Note New Contact Information:
> >
> >Richard Shockey
> >Shockey Consulting LLC
> >5237 Sutherland
> >St. Louis, MO 63109
> >Voice 314.503.0640
> >eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
> >INTERNET Mail & IFAX : rshockey@ix.netcom.com
> ><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> >
>
> -
> 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.

--
Jonathan Buschmann
Siemens Information and Communication Networks S.p.A.
CLTB, Cascina Castelletto, 20019 Settimo Milanese (Mi) Italy
Phone: (+39-2)43888754  Fax: (+39-2)43887989
Jonathan.Buschmann@icn.siemens.it
 "Sometimes when you fill a vacuum, it still sucks." - Dennis Ritchie





From owner-ietf-outbound  Thu Jul  6 05:10:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA09872
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 05:10:02 -0400 (EDT)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09833
	for <ietf@ietf.org>; Thu, 6 Jul 2000 05:04:50 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id CAA20642;
	Thu, 6 Jul 2000 02:04:34 -0700 (PDT)
Date: Thu, 6 Jul 2000 02:04:34 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200007060904.CAA20642@shell9.ba.best.com>
To: ietf@ietf.org
Subject: wireless services
X-Loop: ietf@ietf.org


Where, and by whom, is wireless service with the following features offered?

1.  An option for incoming telephone calls to go directly to voicemail, 
transmitting spoken messages asynchronously to a buffer inside the telephone 
transceiver, using a reliable transport of high quality audio.  Messages 
could thereby be played back in regions without good RF conditions, and 
replayed any number of times without incurring additional airtime charges.

2.  A means to send voice messages to email destinations with an Internet 
message containing a URL pointing to a web server with a choice of audio 
formats from which the message would be played back.  Again, it would be 
preferable if such messages were buffered on the telephone transceiver, 
sent reliably, asynchronously, and using high quality audio, because RF 
congestion could cease to be a significant problem if circuit-switched 
telephone connections were replaced with the flexibility of packet TDMA.
 
3.  A means to send similarly asynchronous messages to telephone 
destinations with an automated outbound call announcing the message sent 
and offering to play the message upon a touch-tone response, or announcing 
the telephone and access numbers with which the message can be retrieved 
(in case the announcement ends up in the recipient's voicemail.)

4.  A means to send instructions for retrieving such messages using 
numeric page or SMS messages for other wireless destinations. 

5.  A means for recipients of messages as described in 2-4 above to reply 
with spoken or numeric or short text messages.  The identity of the message 
being replied to should be clear from the characteristics of the reply.

6.  A serial port on the telephone transceiver providing a PPP link to a 
laptop, palmtop, desktop, or server with severed net connection, etc.

Any one of those features would provide far more value to me and most of 
the people I know than WAP.

Who was/will be first to market with them?

Asynchronous voice messaging is very useful when replies are easy -- 
which is not the case with most voicemail systems in use today.  
Effective asynchronous voice messaging will be a more important 
application than either web or email service on wireless platforms 
because the portable nature of wireless devices is simply antithetical 
to bulky keyboards and large displays.

Cheers,
James



From owner-ietf-outbound  Thu Jul  6 06:10:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA10371
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 06:10:03 -0400 (EDT)
Received: from ztxmail04.ztx.compaq.com (ztxmail04.ztx.compaq.com [161.114.1.208])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10318
	for <ietf@ietf.org>; Thu, 6 Jul 2000 06:01:19 -0400 (EDT)
Received: by ztxmail04.ztx.compaq.com (Postfix, from userid 12345)
	id 54F1767D; Thu,  6 Jul 2000 05:00:51 -0500 (CDT)
Received: from excreo-gh01.reo.dec.com (excreo-gh01.reo.cpqcorp.net [16.41.128.40])
	by ztxmail04.ztx.compaq.com (Postfix) with ESMTP
	id 8B59464C; Thu,  6 Jul 2000 05:00:50 -0500 (CDT)
Received: by excreo-gh01.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <N64N194S>; Thu, 6 Jul 2000 11:00:45 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9C41@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'Jon Crowcroft'" <J.Crowcroft@CS.UCL.AC.UK>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Is WAP mobile Internet??
Date: Thu, 6 Jul 2000 11:00:32 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Wellas I see it, and belive me I may be wrong 'Its been known' :-) This been
the IETF talks about well Internet ... 

 >>I disagree, WAP, Wireless Application Protocol, Its a way of transmitting
 >>data I.E. to and from the Web. How does this not fall under the Internet
 >>Umbrella ?

1 youcan't get at an arbirtrary web page
2/ you can't get at an arbitraty application written on TCP/IP or
UDP/IP

A)youcan't get at an arbirtrary web page (Yes but you can navigate via WAP
I.E BT Genie) and there are places/portals that transform a webpage to WAP
format. 


B/ you can't get at an arbitraty application written on TCP/IP or UDP/IP.
Does it need to be if the Web/Wap app can handle this format?



-----Original Message-----
From: Jon Crowcroft [mailto:J.Crowcroft@cs.ucl.ac.uk]
Sent: Wednesday, July 05, 2000 4:19 PM
To: Parkinson, Jonathan
Cc: 'ietf@ietf.org'; J.Crowcroft@cs.ucl.ac.uk
Subject: Re: Is WAP mobile Internet??



In message
<71C4C55F198BD211B24F0000F842F15807ED9C39@reoexc6.reo.cpqcorp.net>, 
"Parkinson, Jonathan" typed:

 >>I disagree, WAP, Wireless Application Protocol, Its a way of transmitting
 >>data I.E. to and from the Web. How does this not fall under the Internet
 >>Umbrella ?

1 youcan't get at an arbirtrary web page
2/ you can't get at an arbitraty application written on TCP/IP or
UDP/IP

ergo its not internet, its not Internet, and its not provided by
Internet Service Providers, and this is Very Silly

WAP is quite a neat idea but its a prototype - as folks have said, SMS
is very cool - generalisations of it are cooler - native IP based ones
cooler stil coz then your application base can benefot from the
breadth and depth of stuff that people develop all around the world
for IP and the disciplines and understanding of markets that ISPs now
have......

mobile telephony service providers have a reasonable understanding of
one thing - telephony, based in years of fixed/wireline telephony -
however, this doesnt mean they haev much of a clue when it comes to
software based services that people are exponentiateding in the native
IP world......

 
 >>Thanks
 >>Jon
 >>
 >>-----Original Message-----
 >>From: Ashutosh Agarwal [mailto:ashutosha@planetasia.com]
 >>Sent: Wednesday, July 05, 2000 2:25 PM
 >>To: 'Taylor, Johnny'
 >>Cc: 'ietf@ietf.org'
 >>Subject: RE: Is WAP mobile Internet??
 >>
 >>
 >>Hi all,
 >>I fully agree with Lars. Even I believe WAP does not fall under the
Internet
 >>Umbrella
 >>
 >>
 >>Ashutosh Agarwal	
 >>e-mail : ashutosha@planetasia.com
 >>------------------------------------------------------------------------
 >>Change your thoughts and you change your world.
 >>							The Buddha 
 >>------------------------------------------------------------------------
 >>
 >>> -----Original Message-----
 >>> From:	Taylor, Johnny [SMTP:Johnny.Taylor@espire.net]
 >>> Sent:	Tuesday, July 04, 2000 12:15 AM
 >>> To:	Lars-Erik Jonsson; ietf@ietf.org
 >>> Subject:	RE: Is WAP mobile Internet??
 >>> 
 >>> The Internet allows all protocols to in-operate with her. This is the
 >>> uniqueness
 >>> of the web. Therefore WAP falls within this area!
 >>> 
 >>> -----Original Message-----
 >>> From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ericsson.com]
 >>> Sent: Friday, June 30, 2000 7:54 AM
 >>> To: ietf@ietf.org
 >>> Subject: Is WAP mobile Internet??
 >>> 
 >>> 
 >>> Hi Folks!!
 >>> 
 >>> I would like to hear your opinions about how WAP people often say that
WAP
 >>> is
 >>> "mobile Internet". In my opinion, WAP is NOT mobile Internet at all.
The
 >>> Internet is built on the e2e principle and based on the Internet
 >>> Protocols,
 >>> which WAP is not. I can not tell people that they should not use WAP
(even
 >>> if I
 >>> have my opinions about WAP). If they believe in WAP that is their
problem,
 >>> but
 >>> when they try to use the words WAP and Internet in the same sentence I
 >>> think
 >>> it
 >>> is time to clarify a few things. I accept that WAP is there, but be
honest
 >>> about
 >>> what it is.
 >>> 
 >>> Cheers!
 >>> /Lars-Erik (expressing my PERSONAL opinions)
 >>

 cheers

   jon



From owner-ietf-outbound  Thu Jul  6 06:30:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA10674
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 06:30:03 -0400 (EDT)
Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10636
	for <ietf@ietf.org>; Thu, 6 Jul 2000 06:27:53 -0400 (EDT)
Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84])
	by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id DAA26146;
	Thu, 6 Jul 2000 03:18:57 -0700 (PDT)
Received: from mailhost.CorpIndia.BayNetworks.COM (ns1.corpindia.baynetworks.com [141.251.85.6])
	by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id GAA00099;
	Thu, 6 Jul 2000 06:26:38 -0400 (EDT)
Received: from corpindia.baynetworks.com ([141.251.87.53])
	by mailhost.CorpIndia.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id PAA19149;
	Thu, 6 Jul 2000 15:52:37 -0500 (GMT)
Message-ID: <39645FF7.7D094C71@corpindia.baynetworks.com>
Date: Thu, 06 Jul 2000 16:01:20 +0530
From: Aditya Mohan <amohan@baynetworks.com>
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "James P. Salsman" <bovik@best.com>
CC: ietf@ietf.org
Subject: Re: wireless services
References: <200007060904.CAA20642@shell9.ba.best.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi James

You are certainly correct to some extent . These type of features ARE useful . I
myself would like to use them. But why are you segregating these voice features
with web/email/WAP?? To be more specific using WAP, we can easily incorporate
these features in today's cellular phone. Rember , in WAP we have some thing
called the WTAI ( Wireless Telephony Application Interface ) that provides
services like auto call back, voice mail etc to mobile handset via concept of
WTA Server.

Internet has the power to be available to us any time anywhere , and we should
use this facility as effectively as possible either via wireline links  or
Wireless


cheers
Aditya



"James P. Salsman" wrote:

> Where, and by whom, is wireless service with the following features offered?
>
> 1.  An option for incoming telephone calls to go directly to voicemail,
> transmitting spoken messages asynchronously to a buffer inside the telephone
> transceiver, using a reliable transport of high quality audio.  Messages
> could thereby be played back in regions without good RF conditions, and
> replayed any number of times without incurring additional airtime charges.
>
> 2.  A means to send voice messages to email destinations with an Internet
> message containing a URL pointing to a web server with a choice of audio
> formats from which the message would be played back.  Again, it would be
> preferable if such messages were buffered on the telephone transceiver,
> sent reliably, asynchronously, and using high quality audio, because RF
> congestion could cease to be a significant problem if circuit-switched
> telephone connections were replaced with the flexibility of packet TDMA.
>
> 3.  A means to send similarly asynchronous messages to telephone
> destinations with an automated outbound call announcing the message sent
> and offering to play the message upon a touch-tone response, or announcing
> the telephone and access numbers with which the message can be retrieved
> (in case the announcement ends up in the recipient's voicemail.)
>
> 4.  A means to send instructions for retrieving such messages using
> numeric page or SMS messages for other wireless destinations.
>
> 5.  A means for recipients of messages as described in 2-4 above to reply
> with spoken or numeric or short text messages.  The identity of the message
> being replied to should be clear from the characteristics of the reply.
>
> 6.  A serial port on the telephone transceiver providing a PPP link to a
> laptop, palmtop, desktop, or server with severed net connection, etc.
>
> Any one of those features would provide far more value to me and most of
> the people I know than WAP.
>
> Who was/will be first to market with them?
>
> Asynchronous voice messaging is very useful when replies are easy --
> which is not the case with most voicemail systems in use today.
> Effective asynchronous voice messaging will be a more important
> application than either web or email service on wireless platforms
> because the portable nature of wireless devices is simply antithetical
> to bulky keyboards and large displays.
>
> Cheers,
> James



From owner-ietf-outbound  Thu Jul  6 07:30:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA12306
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 07:30:02 -0400 (EDT)
Received: from aloe.us.pw.com (pw21.pw9.com [208.141.52.244])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA12102
	for <ietf@ietf.org>; Thu, 6 Jul 2000 07:24:18 -0400 (EDT)
From: arindam.das@in.pwcglobal.com
Received: by aloe.us.pw.com; id HAA01640; Thu, 6 Jul 2000 07:17:15 -0400
Received: from palm.us.pw.com(10.9.16.43) by aloe.us.pw.com via smap (4.1)
	id xma001258; Thu, 6 Jul 00 07:16:54 -0400
Received: from intlnamsmtp10.us.pw.com by palm.us.pw.com (PMDF V5.1-12 #U3018)
 with SMTP id <0FX900D6TX3VHX@palm.us.pw.com>; Thu,
 6 Jul 2000 07:26:19 -0400 (EDT)
Received: by intlnamsmtp10.us.pw.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))
 id 85256914.003E87D8 ; Thu, 06 Jul 2000 07:23:00 -0400
Date: Thu, 06 Jul 2000 16:00:16 +0530
Subject: RE: Is WAP mobile Internet??
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
Cc: "'Jon Crowcroft'" <J.Crowcroft@CS.UCL.AC.UK>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Message-id: <85256914.003E8340.00@intlnamsmtp10.us.pw.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
X-Lotus-FromDomain: PRICE WATERHOUSE-INDIA@INTL
X-Loop: ietf@ietf.org



I have no access to WAP as it is, so far. Can see a glimpse through the
Internet! Anybody who can give any suggestions however will not get a
prize........




"Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com> on 06-07-2000 03:30:32 PM

To:   'Jon Crowcroft' <J.Crowcroft@cs.ucl.ac.uk>
cc:   "'ietf@ietf.org'" <ietf@ietf.org>
Subject:  RE: Is WAP mobile Internet??



Wellas I see it, and belive me I may be wrong 'Its been known' :-) This been
the IETF talks about well Internet ...

 >>I disagree, WAP, Wireless Application Protocol, Its a way of transmitting
 >>data I.E. to and from the Web. How does this not fall under the Internet
 >>Umbrella ?

1 youcan't get at an arbirtrary web page
2/ you can't get at an arbitraty application written on TCP/IP or
UDP/IP

A)youcan't get at an arbirtrary web page (Yes but you can navigate via WAP
I.E BT Genie) and there are places/portals that transform a webpage to WAP
format.


B/ you can't get at an arbitraty application written on TCP/IP or UDP/IP.
Does it need to be if the Web/Wap app can handle this format?



-----Original Message-----
From: Jon Crowcroft [mailto:J.Crowcroft@cs.ucl.ac.uk]
Sent: Wednesday, July 05, 2000 4:19 PM
To: Parkinson, Jonathan
Cc: 'ietf@ietf.org'; J.Crowcroft@cs.ucl.ac.uk
Subject: Re: Is WAP mobile Internet??



In message
<71C4C55F198BD211B24F0000F842F15807ED9C39@reoexc6.reo.cpqcorp.net>,
"Parkinson, Jonathan" typed:

 >>I disagree, WAP, Wireless Application Protocol, Its a way of transmitting
 >>data I.E. to and from the Web. How does this not fall under the Internet
 >>Umbrella ?

1 youcan't get at an arbirtrary web page
2/ you can't get at an arbitraty application written on TCP/IP or
UDP/IP

ergo its not internet, its not Internet, and its not provided by
Internet Service Providers, and this is Very Silly

WAP is quite a neat idea but its a prototype - as folks have said, SMS
is very cool - generalisations of it are cooler - native IP based ones
cooler stil coz then your application base can benefot from the
breadth and depth of stuff that people develop all around the world
for IP and the disciplines and understanding of markets that ISPs now
have......

mobile telephony service providers have a reasonable understanding of
one thing - telephony, based in years of fixed/wireline telephony -
however, this doesnt mean they haev much of a clue when it comes to
software based services that people are exponentiateding in the native
IP world......


 >>Thanks
 >>Jon
 >>
 >>-----Original Message-----
 >>From: Ashutosh Agarwal [mailto:ashutosha@planetasia.com]
 >>Sent: Wednesday, July 05, 2000 2:25 PM
 >>To: 'Taylor, Johnny'
 >>Cc: 'ietf@ietf.org'
 >>Subject: RE: Is WAP mobile Internet??
 >>
 >>
 >>Hi all,
 >>I fully agree with Lars. Even I believe WAP does not fall under the
Internet
 >>Umbrella
 >>
 >>
 >>Ashutosh Agarwal
 >>e-mail : ashutosha@planetasia.com
 >>------------------------------------------------------------------------
 >>Change your thoughts and you change your world.
 >>                                The Buddha
 >>------------------------------------------------------------------------
 >>
 >>> -----Original Message-----
 >>> From:     Taylor, Johnny [SMTP:Johnny.Taylor@espire.net]
 >>> Sent:     Tuesday, July 04, 2000 12:15 AM
 >>> To:  Lars-Erik Jonsson; ietf@ietf.org
 >>> Subject:  RE: Is WAP mobile Internet??
 >>>
 >>> The Internet allows all protocols to in-operate with her. This is the
 >>> uniqueness
 >>> of the web. Therefore WAP falls within this area!
 >>>
 >>> -----Original Message-----
 >>> From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ericsson.com]
 >>> Sent: Friday, June 30, 2000 7:54 AM
 >>> To: ietf@ietf.org
 >>> Subject: Is WAP mobile Internet??
 >>>
 >>>
 >>> Hi Folks!!
 >>>
 >>> I would like to hear your opinions about how WAP people often say that
WAP
 >>> is
 >>> "mobile Internet". In my opinion, WAP is NOT mobile Internet at all.
The
 >>> Internet is built on the e2e principle and based on the Internet
 >>> Protocols,
 >>> which WAP is not. I can not tell people that they should not use WAP
(even
 >>> if I
 >>> have my opinions about WAP). If they believe in WAP that is their
problem,
 >>> but
 >>> when they try to use the words WAP and Internet in the same sentence I
 >>> think
 >>> it
 >>> is time to clarify a few things. I accept that WAP is there, but be
honest
 >>> about
 >>> what it is.
 >>>
 >>> Cheers!
 >>> /Lars-Erik (expressing my PERSONAL opinions)
 >>

 cheers

   jon




----------------------------------------------------------------
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential and/or privileged material.  Any
review, retransmission, dissemination or other use of, or taking of any action
in reliance upon, this information by persons or entities other than the
intended recipient is prohibited.   If you received this in error, please
contact the sender and delete the material from any computer.




From owner-ietf-outbound  Thu Jul  6 08:40:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA14688
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 08:40:03 -0400 (EDT)
Received: from shrimp.baynetworks.com (ns4.BayNetworks.COM [192.32.253.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14448
	for <ietf@ietf.org>; Thu, 6 Jul 2000 08:32:45 -0400 (EDT)
Received: from mailhost.BayNetworks.COM (ns4.baynetworks.com [132.245.135.84])
	by shrimp.baynetworks.com (8.9.1/8.9.1) with ESMTP id IAA08773;
	Thu, 6 Jul 2000 08:23:27 -0400 (EDT)
Received: from mailhost.CorpIndia.BayNetworks.COM (ns1.corpindia.baynetworks.com [141.251.85.6])
	by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id IAA02095;
	Thu, 6 Jul 2000 08:29:28 -0400 (EDT)
Received: from corpindia.baynetworks.com ([141.251.87.53])
	by mailhost.CorpIndia.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id RAA21698;
	Thu, 6 Jul 2000 17:55:27 -0500 (GMT)
Message-ID: <39647CBE.4B8672A4@corpindia.baynetworks.com>
Date: Thu, 06 Jul 2000 18:04:06 +0530
From: Aditya Mohan <amohan@baynetworks.com>
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: arindam.das@in.pwcglobal.com, ietf@ietf.org
Subject: Re: Is WAP mobile Internet??
References: <85256914.003E8340.00@intlnamsmtp10.us.pw.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

hi arindam
try any of the WAP Emulators - from Nokia.com , phone.com etc  Using that you can
get the feel of the WAP world .

cheers
Aditya
arindam.das@in.pwcglobal.com wrote:

> I have no access to WAP as it is, so far. Can see a glimpse through the
> Internet! Anybody who can give any suggestions however will not get a
> prize........
>
> "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com> on 06-07-2000 03:30:32 PM
>
> To:   'Jon Crowcroft' <J.Crowcroft@cs.ucl.ac.uk>
> cc:   "'ietf@ietf.org'" <ietf@ietf.org>
> Subject:  RE: Is WAP mobile Internet??
>
> Wellas I see it, and belive me I may be wrong 'Its been known' :-) This been
> the IETF talks about well Internet ...
>
>  >>I disagree, WAP, Wireless Application Protocol, Its a way of transmitting
>  >>data I.E. to and from the Web. How does this not fall under the Internet
>  >>Umbrella ?
>
> 1 youcan't get at an arbirtrary web page
> 2/ you can't get at an arbitraty application written on TCP/IP or
> UDP/IP
>
> A)youcan't get at an arbirtrary web page (Yes but you can navigate via WAP
> I.E BT Genie) and there are places/portals that transform a webpage to WAP
> format.
>
> B/ you can't get at an arbitraty application written on TCP/IP or UDP/IP.
> Does it need to be if the Web/Wap app can handle this format?
>
> -----Original Message-----
> From: Jon Crowcroft [mailto:J.Crowcroft@cs.ucl.ac.uk]
> Sent: Wednesday, July 05, 2000 4:19 PM
> To: Parkinson, Jonathan
> Cc: 'ietf@ietf.org'; J.Crowcroft@cs.ucl.ac.uk
> Subject: Re: Is WAP mobile Internet??
>
> In message
> <71C4C55F198BD211B24F0000F842F15807ED9C39@reoexc6.reo.cpqcorp.net>,
> "Parkinson, Jonathan" typed:
>
>  >>I disagree, WAP, Wireless Application Protocol, Its a way of transmitting
>  >>data I.E. to and from the Web. How does this not fall under the Internet
>  >>Umbrella ?
>
> 1 youcan't get at an arbirtrary web page
> 2/ you can't get at an arbitraty application written on TCP/IP or
> UDP/IP
>
> ergo its not internet, its not Internet, and its not provided by
> Internet Service Providers, and this is Very Silly
>
> WAP is quite a neat idea but its a prototype - as folks have said, SMS
> is very cool - generalisations of it are cooler - native IP based ones
> cooler stil coz then your application base can benefot from the
> breadth and depth of stuff that people develop all around the world
> for IP and the disciplines and understanding of markets that ISPs now
> have......
>
> mobile telephony service providers have a reasonable understanding of
> one thing - telephony, based in years of fixed/wireline telephony -
> however, this doesnt mean they haev much of a clue when it comes to
> software based services that people are exponentiateding in the native
> IP world......
>
>  >>Thanks
>  >>Jon
>  >>
>  >>-----Original Message-----
>  >>From: Ashutosh Agarwal [mailto:ashutosha@planetasia.com]
>  >>Sent: Wednesday, July 05, 2000 2:25 PM
>  >>To: 'Taylor, Johnny'
>  >>Cc: 'ietf@ietf.org'
>  >>Subject: RE: Is WAP mobile Internet??
>  >>
>  >>
>  >>Hi all,
>  >>I fully agree with Lars. Even I believe WAP does not fall under the
> Internet
>  >>Umbrella
>  >>
>  >>
>  >>Ashutosh Agarwal
>  >>e-mail : ashutosha@planetasia.com
>  >>------------------------------------------------------------------------
>  >>Change your thoughts and you change your world.
>  >>                                The Buddha
>  >>------------------------------------------------------------------------
>  >>
>  >>> -----Original Message-----
>  >>> From:     Taylor, Johnny [SMTP:Johnny.Taylor@espire.net]
>  >>> Sent:     Tuesday, July 04, 2000 12:15 AM
>  >>> To:  Lars-Erik Jonsson; ietf@ietf.org
>  >>> Subject:  RE: Is WAP mobile Internet??
>  >>>
>  >>> The Internet allows all protocols to in-operate with her. This is the
>  >>> uniqueness
>  >>> of the web. Therefore WAP falls within this area!
>  >>>
>  >>> -----Original Message-----
>  >>> From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ericsson.com]
>  >>> Sent: Friday, June 30, 2000 7:54 AM
>  >>> To: ietf@ietf.org
>  >>> Subject: Is WAP mobile Internet??
>  >>>
>  >>>
>  >>> Hi Folks!!
>  >>>
>  >>> I would like to hear your opinions about how WAP people often say that
> WAP
>  >>> is
>  >>> "mobile Internet". In my opinion, WAP is NOT mobile Internet at all.
> The
>  >>> Internet is built on the e2e principle and based on the Internet
>  >>> Protocols,
>  >>> which WAP is not. I can not tell people that they should not use WAP
> (even
>  >>> if I
>  >>> have my opinions about WAP). If they believe in WAP that is their
> problem,
>  >>> but
>  >>> when they try to use the words WAP and Internet in the same sentence I
>  >>> think
>  >>> it
>  >>> is time to clarify a few things. I accept that WAP is there, but be
> honest
>  >>> about
>  >>> what it is.
>  >>>
>  >>> Cheers!
>  >>> /Lars-Erik (expressing my PERSONAL opinions)
>  >>
>
>  cheers
>
>    jon
>
> ----------------------------------------------------------------
> The information transmitted is intended only for the person or entity to which
> it is addressed and may contain confidential and/or privileged material.  Any
> review, retransmission, dissemination or other use of, or taking of any action
> in reliance upon, this information by persons or entities other than the
> intended recipient is prohibited.   If you received this in error, please
> contact the sender and delete the material from any computer.



From owner-ietf-outbound  Thu Jul  6 10:40:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA17406
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 10:40:01 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17298
	for <ietf@ietf.org>; Thu, 6 Jul 2000 10:36:25 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id KAA05905;
        Thu, 6 Jul 2000 10:36:20 -0400 (EDT)
Message-Id: <200007061436.KAA05905@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
cc: "'Jon Crowcroft'" <J.Crowcroft@CS.UCL.AC.UK>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: Is WAP mobile Internet?? 
In-reply-to: Your message of "Thu, 06 Jul 2000 11:00:32 BST."
             <71C4C55F198BD211B24F0000F842F15807ED9C41@reoexc6.reo.cpqcorp.net> 
Date: Thu, 06 Jul 2000 10:36:20 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Does it need to be if the Web/Wap app can handle this format?

web/wap apps handle a very small number of protocols compared to the
protocols that are handled by IP and used in practice.  

Keith



From owner-ietf-outbound  Thu Jul  6 12:50:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA20734
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 12:50:01 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20579
	for <ietf@ietf.org>; Thu, 6 Jul 2000 12:42:20 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id JAA18801;
	Thu, 6 Jul 2000 09:42:12 -0700 (PDT)
Message-ID: <3964B6D9.CA2C0D92@isi.edu>
Date: Thu, 06 Jul 2000 09:42:01 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.73 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org
Subject: Re: Is WAP mobile Internet??
References: <200007051802.MAA12030@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Vernon Schryver wrote:
> 
> > > > > think we mean having unincumbered availability of the common application
> > > > > protocols, email, http, ftp, ssh, ...
> > > >
> > > > that's not quite enough; in the UK we're seeing cable-modem ISPs
> > > > attempt to restrict services to those applications, or to a subset of
> > > > those applications (lotsa luck setting up an http server or using
> > > > ssh.)
> > > > ...
> > >
> > > and also like AOL's redirecting proxies for out-bound SMTP?
> > > and the port-25 filtering of many ISP's including UUNET?
> > From: Rick H Wesson <wessorh@ar.com>
> 
> > would pacbell filtering all multicast at all CPE equipemt fall into your
> > bucket, where do you draw the line?

At IP, as Bob Braden said.

SMTP is _over_ IP.

Multicast _redefines_ IP (or portions of the address space thereof); it
could be argued that a service provider sells 'Internet' without selling
multicast IP.

Joe



From owner-ietf-outbound  Thu Jul  6 13:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA21751
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 13:40:03 -0400 (EDT)
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21572
	for <ietf@ietf.org>; Thu, 6 Jul 2000 13:30:03 -0400 (EDT)
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 NAA04393
	for <ietf@ietf.org>; Thu, 6 Jul 2000 13:30:03 -0400 (EDT)
Received: from localhost (brunner@localhost)
	by world.std.com (8.9.3/8.9.3) with SMTP id NAA13172
	for <ietf@ietf.org>; Thu, 6 Jul 2000 13:30:02 -0400 (EDT)
Message-Id: <200007061730.NAA13172@world.std.com>
X-Authentication-Warning: world.std.com: brunner@localhost didn't use HELO protocol
To: ietf@ietf.org
Subject: Defining "Internet" (or "internet")
Date: Thu, 06 Jul 2000 13:30:02 -0400
From: Eric Brunner <brunner@world.std.com>
X-Loop: ietf@ietf.org


The Swedish legal definition (Patrik provided the pointer) may not be the
only one which attempts to define what "Internet" is, fixed or broken, er,
"mobile".

Anyone else with a normative legal reference, your favorite jurisdiction or
someone else's, please drop me a line. I'll summarize to the list.

Eric



From owner-ietf-outbound  Thu Jul  6 14:21:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA22509
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 14:20:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22376
	for <ietf@ietf.org>; Thu, 6 Jul 2000 14:12:30 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.11.0.Beta3/calcite) id e66ICTl26447
	for ietf@ietf.org  env-from <vjs>;
	Thu, 6 Jul 2000 12:12:29 -0600 (MDT)
Date: Thu, 6 Jul 2000 12:12:29 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007061812.e66ICTl26447@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Is WAP mobile Internet??
X-Loop: ietf@ietf.org

> From: Joe Touch <touch@ISI.EDU>

> ...
> > > would pacbell filtering all multicast at all CPE equipemt fall into your
> > > bucket, where do you draw the line?
>
> At IP, as Bob Braden said.
>
> SMTP is _over_ IP.
>
> Multicast _redefines_ IP (or portions of the address space thereof); it
> could be argued that a service provider sells 'Internet' without selling
> multicast IP.

That grossly overstates the difference between multicast IP services and
classic IP services.  For one thing, many multicast applications work
fine, albeit with rather reduced scope, when sent to the local IP broadcast
address instead of a multicast address.  For another, since CIDR
"_redefines_ IP (or portions of the address space thereof", are ISP's
that sell non-classful blocks not in the IP business?

It's also a of a stretch to call the 1985 change of class D from
"unused" or "reserved" to the multicast space a redefinition of the
IP address space.  (RFC 966 mentions the change.  RFC 960 still 
said "Note:  No addresses are allowed with the three highest-order bits
set to 1-1-1.  These addresses (sometimes called "class D") are reserved.")


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu Jul  6 14:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA23167
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 14:50:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22579
	for <ietf@ietf.org>; Thu, 6 Jul 2000 14:22:33 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id OAA07867;
	Thu, 6 Jul 2000 14:21:23 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: "'Bob Braden'" <braden@ISI.EDU>, <Jonathan.Parkinson@COMPAQ.COM>
Cc: <ietf@ietf.org>
Subject: RE: Is WAP mobile Internet??
Date: Thu, 6 Jul 2000 15:25:28 -0400
Message-ID: <00ad01bfe77f$f1f08d80$d001010a@tst.ennovatenetworks.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.2615.200
In-reply-to: <200007060313.UAA10989@boreas.isi.edu>
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


Bob Braden writes:

> -----Original Message-----
>
> Jon Postel would have said: If it speaks IP (UDP/TCP are not
> necessary), then it's Internet, else not.

I will add a bit to this discussion.

1. A WAP phone without an IP address is not an Internet device. And,
no one claims so.

2. A WAP device can have both IP and non-IP addresses. So a WAP device
could be an Internet device at one time and non-Internet device a bit
later (at least in theory).

3. An IP address is not very useful on most mobile (cellular) devices.
A lot of useful services and applications can be provided without IP
on the wireless devices. That includes sending and receiving mails
to/from the Internet, and limited web browsing via proxy gateways.

4. Wireless web access using IP is already here, but very few bother
to use it. Networks with the ability to handle IP traffic such as CDPD
have traditionally very low (as per my info, under 15% or so) capacity
utilization and just about every network is under utilized, and in big
loss situation, so much for IP access in wireless devices. At the same
time GSM SMS which needs no IP addressing has a tremendous demands. So
go figure out utility and economics of IP addresses in wireless
devices for now.


Cheers,

--brijesh
Ennovate Networks Inc.






From owner-ietf-outbound  Thu Jul  6 15:30:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA24013
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 15:30:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@[131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23954
	for <ietf@ietf.org>; Thu, 6 Jul 2000 15:28:59 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 13AHKD-00040X-00; Thu, 06 Jul 2000 20:28:41 +0100
Date: Thu, 6 Jul 2000 20:28:34 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Brijesh Kumar <bkumar@ennovatenetworks.com>
cc: "'Bob Braden'" <braden@ISI.EDU>, Jonathan.Parkinson@COMPAQ.COM,
        ietf@ietf.org
Subject: RE: Is WAP mobile Internet??
In-Reply-To: <00ad01bfe77f$f1f08d80$d001010a@tst.ennovatenetworks.com>
Message-ID: <Pine.GSO.4.21.0007062016550.6831-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Thu, 6 Jul 2000, Brijesh Kumar wrote:

> Bob Braden writes:
> > Jon Postel would have said: If it speaks IP (UDP/TCP are not
> > necessary), then it's Internet, else not.
> 
> I will add a bit to this discussion.
> 
> 1. A WAP phone without an IP address is not an Internet device. And,
> no one claims so.

apart from the people selling the things. e.g. http://www.bt.com/

'Getoutthere and check out what's happening on the youth scene
 Find out more about our Internet Mobile Phone special offer'.


> 4. Wireless web access using IP is already here, but very few bother
> to use it. Networks with the ability to handle IP traffic such as CDPD
> have traditionally very low (as per my info, under 15% or so) capacity
> utilization and just about every network is under utilized, and in big
> loss situation, so much for IP access in wireless devices. At the same
> time GSM SMS which needs no IP addressing has a tremendous demands.

pretty ironic considering that SMS is a last-minute control-channel
hack, really.

L.

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



From owner-ietf-outbound  Thu Jul  6 16:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24768
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 16:20:02 -0400 (EDT)
Received: from ce-nfs-1.cisco.com (ce-nfs-1.cisco.com [171.68.202.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24594
	for <ietf@ietf.org>; Thu, 6 Jul 2000 16:09:56 -0400 (EDT)
Received: from glock (dallas-nt-33.cisco.com [171.68.37.33])
	by ce-nfs-1.cisco.com (8.8.8+Sun/8.8.8) with SMTP id NAA29630;
	Thu, 6 Jul 2000 13:08:21 -0700 (PDT)
Message-ID: <013c01bfe785$f0331750$212544ab@glock>
From: "Stephen Sprunk" <ssprunk@cisco.com>
To: <bkumar@ENNOVATENETWORKS.COM>, "'Bob Braden'" <braden@ISI.EDU>,
        <Jonathan.Parkinson@COMPAQ.COM>
Cc: <ietf@ietf.org>
References: <00ad01bfe77f$f1f08d80$d001010a@tst.ennovatenetworks.com>
Subject: Re: Is WAP mobile Internet??
Date: Thu, 6 Jul 2000 14:57:03 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Thus spake "Brijesh Kumar" <bkumar@ENNOVATENETWORKS.COM>
> 1. A WAP phone without an IP address is not an Internet device. And,
> no one claims so.

The telcos who offer WAP service (at least in my town) market it as
"Wireless Internet Access".  They do not advertise it as "wireless
application-proxy-based access to certain web pages", which is what
they're really selling.

> 2. A WAP device can have both IP and non-IP addresses. So a WAP
> device could be an Internet device at one time and non-Internet device
> a bit later (at least in theory).

If it speaks IP, it's Internet.  None of the WAP phones I've used or
seen so far speak IP.

> 3. An IP address is not very useful on most mobile (cellular) devices.

With the current billing model of per-minute connection charges and slow
speeds, it's not useful.  The economics just aren't there for the
consumer.

If the business model were different, it could definitely be useful --
if my laptop had fast, always-on wireless IP access at a reasonable
price, I'd never go to the office.

> A lot of useful services and applications can be provided without IP
> on the wireless devices. That includes sending and receiving mails
> to/from the Internet, and limited web browsing via proxy gateways.

Agreed.  Those services are useful, and they can be done without IP --
it's just not Internet.

Let's not forget one of the most significant reasons the Internet was
created was to eliminate the need for network-based application
gateways.  In this context, WAP devices are anti-Internet.

> 4. Wireless web access using IP is already here, but very few bother
> to use it. Networks with the ability to handle IP traffic such as CDPD
> have traditionally very low (as per my info, under 15% or so) capacity
> utilization and just about every network is under utilized, and in big
> loss situation, so much for IP access in wireless devices. At the same
> time GSM SMS which needs no IP addressing has a tremendous
> demands. So go figure out utility and economics of IP addresses in
> wireless devices for now.

See above.

S

     |          |         Stephen Sprunk, K5SSS, CCIE #3723
    :|:        :|:        Network Design Consultant, HCOE
   :|||:      :|||:       14875 Landmark Blvd #400; Dallas, TX
.:|||||||:..:|||||||:.    Email: ssprunk@cisco.com



From owner-ietf-outbound  Thu Jul  6 16:30:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24951
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 16:30:03 -0400 (EDT)
Received: from tantalum (tantalum.btinternet.com [194.73.73.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24643
	for <ietf@ietf.org>; Thu, 6 Jul 2000 16:11:52 -0400 (EDT)
Received: from [62.7.45.58] (helo=salavat)
	by tantalum with esmtp (Exim 3.03 #82)
	id 13AI00-0007L1-00
	for ietf@ietf.org; Thu, 06 Jul 2000 21:11:52 +0100
Message-ID: <015801bfe76d$6988fca0$3a2d073e@salavat>
Reply-To: "Salavat R. Magazov \(BT\)" <srm4@ukc.ac.uk>
From: "Salavat R. Magazov \(BT\)" <S.R.Magazov@btinternet.com>
To: "IETF mailing list" <ietf@ietf.org>
Subject: Routing vs Route discovery protocol
Date: Thu, 6 Jul 2000 21:12:16 +0400
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_013F_01BFE78E.DCD54580"
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
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_013F_01BFE78E.DCD54580
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit

Hello

I cannot understand the difference between routing and route discovery
protocols. Is there any?

Regards
Salavat





------=_NextPart_000_013F_01BFE78E.DCD54580
Content-Type: text/x-vcard;
	name="Salavat R. Magazov.vcf"
Content-Disposition: attachment;
	filename="Salavat R. Magazov.vcf"
Content-Transfer-Encoding: 7bit

BEGIN:VCARD
VERSION:2.1
N:Magazov;Salavat;R.
FN:Salavat R. Magazov
NICKNAME:Sal
ORG:University of Kent at Canterbury
TEL;HOME;VOICE:+44-1227-472835
X-WAB-GENDER:2
BDAY:20000517
EMAIL;PREF;INTERNET:srm4@ukc.ac.uk
EMAIL;INTERNET:salavat@ukonline.co.uk
REV:20000706T080032Z
END:VCARD

------=_NextPart_000_013F_01BFE78E.DCD54580--



From owner-ietf-outbound  Thu Jul  6 16:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA25353
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 16:50:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25129
	for <ietf@ietf.org>; Thu, 6 Jul 2000 16:35:44 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id NAA18561;
	Thu, 6 Jul 2000 13:35:29 -0700 (PDT)
Message-ID: <3964ED85.F750AA5F@isi.edu>
Date: Thu, 06 Jul 2000 13:35:17 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.73 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org, touch@ISI.EDU
Subject: Re: Is WAP mobile Internet??
References: <200007061812.e66ICTl26447@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Vernon Schryver wrote:
> 
> > From: Joe Touch <touch@ISI.EDU>
> 
> > ...
> > > > would pacbell filtering all multicast at all CPE equipemt fall into your
> > > > bucket, where do you draw the line?
> >
> > At IP, as Bob Braden said.
> >
> > SMTP is _over_ IP.
> >
> > Multicast _redefines_ IP (or portions of the address space thereof); it
> > could be argued that a service provider sells 'Internet' without selling
> > multicast IP.
> 
> That grossly overstates the difference between multicast IP services and
> classic IP services.  For one thing, many multicast applications work
> fine, albeit with rather reduced scope, when sent to the local IP broadcast
> address instead of a multicast address.  For another, since CIDR
> "_redefines_ IP (or portions of the address space thereof", are ISP's
> that sell non-classful blocks not in the IP business?

'Internet' is about speaking IP and ICMP.

There are many variants of routing; none are required to be deployed
_throughout_ the Internet. Static routes are sufficient, and 'who speaks
what routing protocol' and 'what the routes mean' (CIDR included) is a
matter of consensus among parties exchanging a single routing protocol,
not an Internet-wide requirement.

> It's also a of a stretch to call the 1985 change of class D from
> "unused" or "reserved" to the multicast space a redefinition of the
> IP address space. 

Under classic IP, class D was defined as unused/reserved;
under multicast IP, class D is now defined as multicast. 
That is the purest form of the change of a definition.
While it affects only a portion of all IP packets, it did redefine
the meaning of that portion.

(it redefined the meaning of values of the space, not the partitioning
of the space).

Joe



From owner-ietf-outbound  Thu Jul  6 17:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA25828
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 17:20:02 -0400 (EDT)
Received: from emx.siamrelay.com ([202.183.201.126])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25695
	for <ietf@ietf.org>; Thu, 6 Jul 2000 17:12:46 -0400 (EDT)
Received: by emx.siamrelay.com (8.9.3/8.9.3) with ESMTP id EAA23736;
	Fri, 7 Jul 2000 04:12:13 +0700
Received: from localhost (fygrave@localhost)
	by beez.siamrelay.com (8.9.3/8.9.3) with ESMTP id EAA04764;
	Fri, 7 Jul 2000 04:10:11 +0700 (ICT)
	(envelope-from fygrave@relaygroup.com)
X-Authentication-Warning: beez.siamrelay.com: fygrave owned process doing -bs
Date: Fri, 7 Jul 2000 04:10:11 +0700 (ICT)
From: Fyodor <fygrave@relaygroup.com>
X-Sender: fygrave@beez.siamrelay.com
Reply-To: fyodor@relaygroup.com
To: "Salavat R. Magazov (BT)" <srm4@ukc.ac.uk>
cc: IETF mailing list <ietf@ietf.org>
Subject: Re: Routing vs Route discovery protocol
In-Reply-To: <015801bfe76d$6988fca0$3a2d073e@salavat>
Message-ID: <Pine.BSF.4.21.0007070404080.15759-100000@beez.siamrelay.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


~ :Hello
~ :
~ :I cannot understand the difference between routing and route discovery
~ :protocols. Is there any?


 Yes. RDP is designed to discover default gateway(s) by broadcasting rdp
request packs. It's just a protocol, which lacks security implications by
the way (see l0pht.com advisory).

 Routing however is just a complex concept of delivering datagrams from
one network entity to another. blah blah blah..


hope I won't be flamed by the list for answering a couple of du^H^Hnot so
sophisticated questions. :) I just feel bored at 4am in the morning :)



From owner-ietf-outbound  Thu Jul  6 18:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA26623
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 18:10:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26493
	for <ietf@ietf.org>; Thu, 6 Jul 2000 17:58:56 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.11.0.Beta3/calcite) id e66Lwww03871
	for ietf@ietf.org  env-from <vjs>;
	Thu, 6 Jul 2000 15:58:58 -0600 (MDT)
Date: Thu, 6 Jul 2000 15:58:58 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007062158.e66Lwww03871@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Is WAP mobile Internet??
X-Loop: ietf@ietf.org

> From: Joe Touch <touch@ISI.EDU>

> ...
> > > At IP, as Bob Braden said.
> > >
> > > SMTP is _over_ IP.
> > >
> > > Multicast _redefines_ IP (or portions of the address space thereof); it
> > > could be argued that a service provider sells 'Internet' without selling
> > > multicast IP.
> > 
> > That grossly overstates the difference between multicast IP services and
> > classic IP services.  For one thing, many multicast applications work
> ...

> 'Internet' is about speaking IP and ICMP.

And which multicast application isn't?

> There are many variants of routing; none are required to be deployed
> _throughout_ the Internet. Static routes are sufficient, and 'who speaks
> what routing protocol' and 'what the routes mean' (CIDR included) is a
> matter of consensus among parties exchanging a single routing protocol,
> not an Internet-wide requirement.

What is the relevance of that to the question of when a package labeled
"The Internet" is a fraud?
BGP4 is a lot newer than multicasting.  Would you say that an ISP with
broken routing that makes a significant part of the net unreachable is
still legitimately selling "The Internet"?


> > It's also a of a stretch to call the 1985 change of class D from
> > "unused" or "reserved" to the multicast space a redefinition of the
> > IP address space. 
>
> Under classic IP, class D was defined as unused/reserved;
> under multicast IP, class D is now defined as multicast. 
> That is the purest form of the change of a definition.
> While it affects only a portion of all IP packets, it did redefine
> the meaning of that portion.

In exactly what way did it redefine any IP header bits?  Yes, what routers
must do and the link-layer destination of some IP addresses was tweaked,
but little more than what RFC 1122 did to broadcast addresses.  The
multicast changes were no than many other changes since 1085, including
new ICMP types.  Would you say an ISP selling "Internet email and web
hosting" is honest if its hosts don't do slow start, because slow start
wasn't there at the beginning?  What about the many other new requirements,
such as egress filtering and not advertising routes to RFC 1918 networks?
Or the deprecation of RFC 822 promiscuous relaying?

> (it redefined the meaning of values of the space, not the partitioning
> of the space).

More than the meanings of other large chunks of the 32-bit IPv4 space
listed in RFC 960 as "reserved"?  I'll grant the word "reserved" was a
little general, but not enough to matter.


The question is not "what was NFSNet in 1985."  It is, "in 2000, at what
point is a vendor claiming to be selling "The Internet" guilty of false
and misleading advertising?"  Would you really allow a vendor to sell
exactly those services that were available in 1985?  Why not pick 1970?
If you must do it by date, 1990 or 1995 makes a lot more, but still not
much sense.  "The Internet" is not a static thing.

When (and if) IPv6 takes off, would you say an "Internet" package could
exclude the IPv6 universe, including hosts reachable with an embedded IPv4
address?  If you're consistent, your answer must be "yse."

If it were relevant, I'd ask about the cause for your unreasoning prejudice
against multicasting.  You might be able to support a claim that
multicasting in the Internet is a bad idea, can't work in many ve large
internets (small 'i'), is useless except for either trivial applications
or applications that can do as well or better with broadcasting (e.g.
NTP), or similar.  Claiming that multicasting is not part of The Internet
because it wasn't in TIP's and IMP's in 1970 is something else.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu Jul  6 21:40:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29780
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 21:40:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29718
	for <ietf@ietf.org>; Thu, 6 Jul 2000 21:36:00 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007070125.KAA11442@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id KAA11442; Fri, 7 Jul 2000 10:25:12 +0900
Subject: Re: Is WAP mobile Internet??
In-Reply-To: <3964B6D9.CA2C0D92@isi.edu> from Joe Touch at "Jul 6, 2000 09:42:01
 am"
To: Joe Touch <touch@ISI.EDU>
Date: Fri, 7 Jul 2000 10:25:10 +0859 ()
CC: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Joe;

> > > would pacbell filtering all multicast at all CPE equipemt fall into your
> > > bucket, where do you draw the line?
> 
> At IP, as Bob Braden said.
> 
> SMTP is _over_ IP.

Wrong. RFC821 says:

   SMTP is independent of the particular transmission subsystem and
   requires only a reliable ordered data stream channel.  Appendices A,
   B, C, and D describe the use of SMTP with various transport services.
   A Glossary provides the definitions of terms as used in this
   document.

> Multicast _redefines_ IP (or portions of the address space thereof); it
> could be argued that a service provider sells 'Internet' without selling
> multicast IP.

See STD1 for a list of "required" protocols.

							Masataka Ohta



From owner-ietf-outbound  Thu Jul  6 22:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA00279
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 22:10:03 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29958
	for <ietf@ietf.org>; Thu, 6 Jul 2000 21:49:44 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id SAA24227;
	Thu, 6 Jul 2000 18:49:35 -0700 (PDT)
Message-ID: <39653723.E521D116@isi.edu>
Date: Thu, 06 Jul 2000 18:49:23 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.73 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
CC: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: Is WAP mobile Internet??
References: <200007070125.KAA11442@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Masataka Ohta wrote:
> 
> Joe;
> 
> > > > would pacbell filtering all multicast at all CPE equipemt fall into your
> > > > bucket, where do you draw the line?
> >
> > At IP, as Bob Braden said.
> >
> > SMTP is _over_ IP.
> 
> Wrong. RFC821 says:
> 
>    SMTP is independent of the particular transmission subsystem and
>    requires only a reliable ordered data stream channel.  Appendices A,
>    B, C, and D describe the use of SMTP with various transport services.
>    A Glossary provides the definitions of terms as used in this
>    document.

Appendix A is SMTP over TCP (over IP). (I was implying that it was on
TOP of IP, not that it was exclusively on top of IP).

SMTP in the Internet is, by definition, over IP. STD1 defined only one
required reliable ordered data stream protocol - TCP.

> > Multicast _redefines_ IP (or portions of the address space thereof); it
> > could be argued that a service provider sells 'Internet' without selling
> > multicast IP.
> 
> See STD1 for a list of "required" protocols.

Multicasting is RFC1112, one of the 'required' protocols.

On page 1 of that RFC:   

	Level 0: no support for IP multicasting

   There is, at this time, no requirement that all IP implementations
   support IP multicasting.  Level 0 hosts will, in general, be
   unaffected by multicast activity.  The only exception arises on some
   types of local network, where the presence of level 1 or 2 hosts may
   cause misdelivery of multicast IP datagrams to level 0 hosts.  Such
   datagrams can easily be identified by the presence of a class D IP
   address in their destination address field; they should be quietly
   discarded by hosts that do not support IP multicasting. 

Interestingly, the RFC indicates 'should be quietly dropped' where not
supported. There is no requirement that they not be dropped, or that the
dropping be quiet.

Joe



From owner-ietf-outbound  Thu Jul  6 22:27:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA00488
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 22:26:51 -0400 (EDT)
Received: from cannon6.mp3.com (cannon6.mp3.com [63.241.18.18])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA00006
	for <ietf@ietf.org>; Thu, 6 Jul 2000 21:52:02 -0400 (EDT)
Received: (qmail 28913 invoked by uid 0); 7 Jul 2000 01:52:03 -0000
Date: 7 Jul 2000 01:52:03 -0000
Message-ID: <20000707015203.28912.qmail@cannon6.mp3.com>
Content-Transfer-Encoding: binary
Content-Type: multipart/alternative; boundary="_----------=_9629347232857498"
MIME-Version: 1.0
X-Mailer: MIME::Lite 1.135  (B2.11; Q2.03)
To: ietf@ietf.org
From: welcome@mp3.com
Subject: Thanks for visiting MP3.com
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

--_----------=_9629347232857498
Content-Disposition: inline
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hello ,

Welcome to MP3.com!

Thanks again for visiting MP3.com and providing us with your
email address. If you would like to unsubscribe from future
MP3.com announcements, or if you received this message in
error, please see the bottom of this message for instructions.

===( Sponsor )===============================================

Find your favorite type of music easily with Internet 
Keywords.  Type MP3.com Hip Hop into your browser, and 
Internet Keywords take you to that page directly. Try Internet 
Keywords today, in Microsoft IE and most search engines.
http://click.mp3.com/c/c_adaa/n_633239552/u_www.realnames.com

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

At MP3.com, our mission is simple--be a complete Music
Service Provider that brings artists together with their fans.
Whether you're looking for new music from your hometown or
the other side of the world, you'll find a wealth of
FREE music downloads and services on MP3.com.

The next time you visit MP3.com, we invite you to:

* Take advantage of your personal music center at My.MP3.com:

Create online music compilations in minutes.

Set up your FREE My.MP3.com account today. It's all one click
away at:
http://click.mp3.com/c/c_adab/n_633239552/u_my

* Classical Music Channel
Instant access to Bach, Beethoven, Mozart and more
http://click.mp3.com/c/c_adac/n_633239552/u_www/channels

* Send Free Music Greeting Cards
Pick any occasion and attach your favorite MP3 song
http://click.mp3.com/c/c_adad/n_633239552/u_musicgreetings/

* Catch Live Events
in your area with free Notify Me! email alerts
http://click.mp3.com/c/c_adae/n_633239552/u_reg/notifyme/

* Get Free Songs
Delivered via email with Music Messenger
http://click.mp3.com/c/c_adaf/n_633239552/u_reg/songrec_signup/emags.cgi

* Free MP3 Software
All you'll ever need to make and play MP3s
http://click.mp3.com/c/c_adag/n_633239552/u_software/software/

* MP3.com Top 40
See who's topping the charts
http://click.mp3.com/c/c_adah/n_633239552/u_genres/music/

* Free Extras
Such as headsets and more
http://click.mp3.com/c/c_adai/n_633239552/u_www/promos/extras/index.html

Since it's all about great music, we want to make sure the
tunes are coming in loud and clear. To listen to MP3s, you
first need to install an MP3 player. Click on the link below
to get set up with one of our recommended players:
http://click.mp3.com/c/c_adaj/n_633239552/u_software/software/

Once you've got your player installed, the easiest and fastest 
way to fill it with MP3s is to use the free NetSonic Internet 
Accelerator.
http://click.mp3.com/c/c_adak/n_633239552/u_www.netsonic.com/sku/e1-060200_Mp3/index.asp

So dive in, explore and expand your music collection on MP3.com!

Regards,

Michael Robertson
CEO
MP3.com--Your Premier Music Service Provider

P.S. Support your favorite artists and check out their CDs for
sale:
http://click.mp3.com/c/c_adal/n_633239552/u_www/store

-----------[ Unsubscribe Instructions ]----------------
If you'd rather not receive future emails from MP3.com,
please click the web address below, or forward this email
to unsubscribe@mp3.com
http://click.mp3.com/c/c_adam/n_633239552/u_chooser/cgi-bin/membership/subscribe.cgi?id=AEEAeL4l20vnxNnBPogjm2jhuLlBwQ--

Copyright  1996-2000 MP3.com, Inc. All rights reserved.
Legal Information, Privacy Policy.

http://click.mp3.com/c/c_adan/n_633239552/u_www/aboutus.html
http://click.mp3.com/c/c_adao/n_633239552/u_www/disclaimer.html
http://click.mp3.com/c/c_adap/n_633239552/u_www/privacy.html

--_----------=_9629347232857498
Content-Disposition: inline
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<HTML>
<HEAD>
<TITLE>welcome</TITLE>
</HEAD>

<BODY bgcolor=3D"#ffffff">

<CENTER>

<TABLE border=3D"0" cellSpacing=3D"0" width=3D"600">
<TR>
<TD>
<CENTER><a href=3D"http://click.mp3.com/c/c_adbr/n_633239552/u_www.realname=
s.com/?cp=3Drealnames"><img src=3D"http://click.mp3.com/c/v_ad/n_633239552/=
u_images/mp3s/images/mail/realnames66.gif" alt=3D"Find your favorite type o=
f music easily with Internet Keywords" BORDER=3D"0" height=3D"60" width=3D"=
468"></A>
</CENTER>
</TD>
</TR>
</TABLE>
</CENTER>&nbsp;=20

<CENTER>

<center><table BORDER=3D"0" CELLSPACING=3D"0" CELLPADDING=3D"2" WIDTH=3D"60=
0" BGCOLOR=3D"#000000" >
<tr>
<td>
<table BORDER=3D"0" CELLSPACING=3D"0" CELLPADDING=3D"4" WIDTH=3D"600" BGCOL=
OR=3D"#000000" >
<tr>
<td><font face=3D"arial, helvetica" color=3D"#ffffff">The MP3.com <b>Welcom=
e Email</b>
</td>
</tr>
</table>
<table BORDER=3D"0" CELLSPACING=3D"0" CELLPADDING=3D"0" WIDTH=3D"600">
<tr>
<td><a href=3D"http://click.mp3.com/c/c_adbs/n_633239552/u_www/"><IMG src=
=3D"http://images.mp3.com/mp3s/images/mail/welcome.gif" alt=3D"MP3.com Home=
" border=3D"0" height=3D"60" width=3D"600"></a>
</td>
</tr>
<tr>
<td>
<TABLE bgcolor=3D"#ffffff" border=3D"0" cellpadding=3D"0" cellSpacing=3D"0"=
 width=3D"100%">
<TR>
<TD>

<TABLE border=3D"0" cellSpacing=3D"0" cellpadding=3D"5" width=3D"100%">
<TR>
<TD bgColor=3D"#ffffff" colSpan=3D"2"><FONT face=3D"Arial,Helvetica"><FONT =
size=3D"-2">Thanks again for visiting MP3.com and providing us with your em=
ail address. If you would like to unsubscribe from future MP3.com announcem=
ents or if you received this message in error, please see the bottom of thi=
s message for instructions.</FONT></FONT></TD></TR>
<TR>
<TD bgColor=3D"#e2f0fc" width=3D"70%"><B><FONT face=3D"Arial,Helvetica"><FO=
NT size=3D"-1">Dear Music Fan,</FONT></FONT></B>
<P><FONT face=3D"Arial,Helvetica"><FONT size=3D"-1">At MP3.com, our mission=
 is simple--to be a complete <B>Music Service Provider</B> that brings arti=
sts together with their fans. Whether you're looking for new music from you=
r hometown or the other side of the world, you'll <B>find a wealth of free =
music downloads and services</B> on MP3.com.</FONT></FONT>
<P><FONT face=3D"Arial,Helvetica"><FONT size=3D"-1">Since it's all about gr=
eat music, we want to make sure the tunes are coming in loud and clear. To =
listen to MP3s, you first need to install an MP3 player. <a href=3D"http://=
click.mp3.com/c/c_adbt/n_633239552/u_software/software/?cp=3Dsoftware">Go h=
ere</A> to get set up with one of our recommended players.</FONT></FONT>
<P><FONT face=3D"Arial,Helvetica"><FONT size=3D"-1">Once you've got your pl=
ayer installed, the easiest and fastest way to fill it with MP3s is to use =
the free <a href=3D"http://click.mp3.com/c/c_adbu/n_633239552/u_www.netsoni=
c.com/sku/e1-060200_Mp3/index.asp?cp=3Dnetsonic">NetSonic Internet Accelera=
tor</a>.</font></font>
<P><B><FONT face=3D"Arial,Helvetica"><FONT size=3D"-1">So dive in, explore =
and expand your music collection on MP3.com!</FONT></FONT></B>=20
<BR><FONT face=3D"Arial,Helvetica"><FONT size=3D"-1">Regards,</FONT></FONT>
<P><IMG height=3D"29" src=3D"http://images.mp3.com/mp3s/images/mail/signatu=
re.gif" width=3D"74">=20
<BR><FONT face=3D"Arial,Helvetica"><FONT size=3D"-1">Michael Robertson</FON=
T></FONT>=20
<BR><FONT face=3D"Arial,Helvetica"><FONT size=3D"-1">CEO</FONT></FONT>=20
<BR><FONT face=3D"Arial,Helvetica"><FONT size=3D"-1">MP3.com--Your Premier =
Music Service Provider</FONT></FONT>=20
<BR><FONT face=3D"Arial,Helvetica"><FONT size=3D"-1">P.S. <a href=3D"http:/=
/click.mp3.com/c/c_adbv/n_633239552/u_www/store/?cp=3Dstore">Support your f=
avorite artists</A> and check out their CDs for sale.</FONT></FONT></P>
</TD>

<TD vAlign=3D"top" width=3D"30%">

<TABLE border=3D"0" cellSpacing=3D"0" cols=3D"1" width=3D"171">
<TR>
<TD bgColor=3D"#003366">
<CENTER><B><FONT face=3D"Arial,Helvetica"><FONT color=3D"#ffffff">MP3.com S=
ervices</FONT></FONT></B>
</CENTER>
</TD>
</TR>
<TR>
<TD>
<CENTER><a href=3D"http://click.mp3.com/c/c_adbw/n_633239552/u_my/?cp=3Dmym=
p3_img"><IMG alt=3D"Try My.MP3.com!" border=3D"0" height=3D"92" src=3D"http=
://images.mp3.com/mp3s/images/mail/my_mp3.gif" width=3D"170"></A>
</CENTER>
</TD>
</TR>
<TR>
<TD></TD>
</TR>
<TR>
<TD>
<table border=3D"0" width=3D"171" cellpadding=3D"0" cellspacing=3D"0">
<tr>
<td valign=3D"top"><LI><br></LI>
</td>
<td valign=3D"top" width=3D171><B><FONT face=3D"Arial,Helvetica"><FONT size=
=3D"-1"><a href=3D"http://click.mp3.com/c/c_adbx/n_633239552/u_www/channels=
/?cp=3Dcmc">Classical Music Channel</A> - </FONT></FONT></B><FONT face=3D"A=
rial,Helvetica"><FONT size=3D"-1">Instant access to Bach, Beethoven, Mozart=
 and more</FONT></FONT>
</td>
</tr>
<tr>
<td valign=3D"top"><LI><br></LI>
</td>
<td valign=3D"top" width=3D171><B><FONT face=3D"Arial,Helvetica"><FONT size=
=3D"-1"><a href=3D"http://click.mp3.com/c/c_adby/n_633239552/u_musicgreetin=
gs/?cp=3Dmusicgreetings">Send Free Music Greeting Cards</A> - </FONT></FONT=
></B><FONT face=3D"Arial,Helvetica"><FONT size=3D"-1">Pick any occasion and=
 attach your favorite MP3 song</FONT></FONT>
</td>
</tr>
<tr>
<td valign=3D"top"><LI><br></LI>
</td>
<td valign=3D"top" width=3D171><B><FONT face=3D"Arial,Helvetica"><FONT size=
=3D"-1"><a href=3D"http://click.mp3.com/c/c_adbz/n_633239552/u_reg/notifyme=
/?cp=3Dnotify_me">Catch Live Events</A> - </FONT></FONT></B><FONT face=3D"A=
rial,Helvetica"><FONT size=3D"-1">in your area with free Notify Me! email a=
lerts</FONT></FONT>
</td>
</tr>

<tr>
<td valign=3D"top"><LI><br></LI>
</td>
<td valign=3D"top" width=3D171><B><FONT face=3D"Arial,Helvetica"><FONT size=
=3D"-1"><a href=3D"http://click.mp3.com/c/c_adbA/n_633239552/u_reg/songrec_=
signup/emags.cgi?cp=3Dmessenger">Get Free Songs</A> - </FONT></FONT></B><FO=
NT face=3D"Arial,Helvetica"><FONT size=3D"-1">Delivered via email with MP3.=
com Messenger</FONT></FONT>
</td>
</tr>

<tr>
<td valign=3D"top"><LI><br></LI>
</td>
<td valign=3D"top" width=3D171><FONT face=3D"Arial,Helvetica"><FONT size=3D=
"-1"><B><a href=3D"http://click.mp3.com/c/c_adbB/n_633239552/u_software/sof=
tware/?cp=3Dsoftware_fs">Free MP3 Software</A></B> - All you'll ever need t=
o make and play MP3s</FONT></FONT>
</td>
</tr>
<tr>
<td valign=3D"top"><LI><br></LI>
</td>
<td valign=3D"top" width=3D171><B><FONT face=3D"Arial,Helvetica"><FONT size=
=3D"-1"><a href=3D"http://click.mp3.com/c/c_adbC/n_633239552/u_genres/music=
/?cp=3Dtop40">MP3.com Top 40</A></FONT></FONT></B><FONT face=3D"Arial,Helve=
tica"><FONT size=3D"-1"> - See who's topping the charts</FONT></FONT>
</td>
</tr>
<tr>
<td valign=3D"top"><LI><br></LI>
</td>
<td valign=3D"top" width=3D171><B><FONT face=3D"Arial,Helvetica"><FONT size=
=3D"-1"><a href=3D"http://click.mp3.com/c/c_adbD/n_633239552/u_www/promos/e=
xtras/index.html?cp=3Dfree_extras">Free Extras</A> - </FONT></FONT></B><FON=
T face=3D"Arial,Helvetica"><FONT size=3D"-1">Such as headsets and more</FON=
T></FONT>
</td>
</tr>
</table>=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20
</TD>
</TR>
</TABLE>
</TD>
</TR>
</TABLE>
</TD>
</TR>
</TABLE>
<center>
<FONT face=3D"Arial,Helvetica"><FONT color=3D"#ffffff"><FONT size=3D"-1">If=
 you'd rather not receive future emails from MP3.com, <a href=3D"http://cli=
ck.mp3.com/c/c_adbE/n_633239552/u_chooser/cgi-bin/membership/subscribe.cgi?=
id=3DAEEAeL4l20vnxNnBPogjm2jhuLlBwQ--"><FONT color=3D"#ffffff">click here</=
FONT></A>  to unsubscribe or forward this email to <a href=3D"mailto:unsubs=
cribe@mp3.com"><font color=3D"#FFFFFF">unsubscribe@mp3.com</font></a>.</FON=
T></FONT></FONT>
</center>
</TD>
</TR>
</TABLE>

</td>
</tr>
</table>

<CENTER>
<br>
<font face=3D"Arial,Helvetica" color=3D"#000000" size=3D"-2">Copyright &cop=
y; 1996-2000 <a href=3D"http://click.mp3.com/c/c_adbF/n_633239552/u_www/abo=
utus.html?cp=3Dmp3_about"><font color=3D"#000000">MP3.com, Inc</a></font>. =
All rights reserved. <a href=3D"http://click.mp3.com/c/c_adbG/n_633239552/u=
_www/disclaimer.html?cp=3Dmp3_legal"><font color=3D"#000000">Legal Informat=
ion</a></font>, <a href=3D"http://click.mp3.com/c/c_adbH/n_633239552/u_www/=
privacy.html?cp=3Dmp3_privacy"><font color=3D"#000000">Privacy Policy</a></=
font>.
</center>

</CENTER><BR>&nbsp;
</BODY>
</HTML>

--_----------=_9629347232857498--



From owner-ietf-outbound  Thu Jul  6 23:40:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA02490
	for ietf-outbound.10@ietf.org; Thu, 6 Jul 2000 23:40:03 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00474
	for <ietf@ietf.org>; Thu, 6 Jul 2000 22:25:34 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007070222.LAA11893@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id LAA11893; Fri, 7 Jul 2000 11:21:46 +0859
Subject: Re: Is WAP mobile Internet??
In-Reply-To: <39653723.E521D116@isi.edu> from Joe Touch at "Jul 6, 2000 06:49:23
 pm"
To: Joe Touch <touch@ISI.EDU>
Date: Fri, 7 Jul 2000 11:21:44 +0859 ()
CC: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Joe;

> SMTP in the Internet is, by definition, over IP. STD1 defined only one
> required reliable ordered data stream protocol - TCP.

What is your point?

Are you saying that, in the Internet, there is some application/transport
protocols not over IP but SMTP is exclusively over IP?

> > > Multicast _redefines_ IP (or portions of the address space thereof); it
> > > could be argued that a service provider sells 'Internet' without selling
> > > multicast IP.
> > 
> > See STD1 for a list of "required" protocols.
> 
> Multicasting is RFC1112, one of the 'required' protocols.

In RFC 2400, the last STD1 which included information on requirement
levels, it is a "recommended", not "required" protocol.

I wonder why the information is missing in the recent STD1.

							Masataka Ohta



From owner-ietf-outbound  Fri Jul  7 00:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA02860
	for ietf-outbound.10@ietf.org; Fri, 7 Jul 2000 00:20:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@[128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01554
	for <ietf@ietf.org>; Thu, 6 Jul 2000 22:37:34 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@localhost [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta4/8.11.0.Beta4) with ESMTP id e672bZS33072
	for <ietf@ietf.org>; Thu, 6 Jul 2000 22:37:35 -0400
Message-Id: <200007070237.e672bZS33072@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/16/2000 with nmh-1.0.4+dev
To: ietf@ietf.org
Subject: Re: Thanks for visiting MP3.com 
In-Reply-To: Your message of "Fri, 07 Jul 2000 01:52:03 -0000."
             <20000707015203.28912.qmail@cannon6.mp3.com> 
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: <20000707015203.28912.qmail@cannon6.mp3.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_551313432P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 06 Jul 2000 22:37:34 -0400
X-Loop: ietf@ietf.org

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

On Fri, 07 Jul 2000 01:52:03 -0000, welcome@mp3.com  said:
> Thanks again for visiting MP3.com and providing us with your
> email address. If you would like to unsubscribe from future
> MP3.com announcements, or if you received this message in
> error, please see the bottom of this message for instructions.

OK.. I'll bite.  Is mp3.com spamming non-visitors, or did somebody
visit and give the IETF as their e-mail address?

Sorry, it's been a long day, and I'd love to use a clue-by-four on
somebody, but it's not obvious who to use it on... ;)
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOWVCbnAt5Vm009ewEQKKSgCg5t03wuu0s3Oj5HEJhQTkYNagT6MAnjhm
7JC1yN2hHw6M27HC+fqx+Zg6
=r33d
-----END PGP SIGNATURE-----

--==_Exmh_551313432P--



From owner-ietf-outbound  Fri Jul  7 02:40:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA15941
	for ietf-outbound.10@ietf.org; Fri, 7 Jul 2000 02:40:02 -0400 (EDT)
Received: from terra.telestet.gr (terra.telestet.gr [194.219.149.99])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA15904
	for <ietf@ietf.org>; Fri, 7 Jul 2000 02:32:46 -0400 (EDT)
Received: from [192.168.2.2]
	(HELO localhost)
	by terra.telestet.gr (AltaVista Mail V2.0J/2.0J BL25J listener)
	id 0000_0054_3965_783f_1aec;
	Fri, 07 Jul 2000 09:27:11 +0300
Received: by mail.telestet.gr with Internet Mail Service (5.5.2650.21)
	id <3KBFDN51>; Fri, 7 Jul 2000 09:30:30 +0300
Message-ID: <6ADD5A0DF6B1D31193430090279A2A08E5E111@mail.telestet.gr>
From: TSIGARIDAS PANAGIOTIS <P.TSIGARIDAS@telestet.gr>
To: Eric Brunner <brunner@world.std.com>, ietf@ietf.org
Subject: RE: Defining "Internet" (or "internet")
Date: Fri, 7 Jul 2000 09:30:30 +0300 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFE7DC.D8EEE23E"
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFE7DC.D8EEE23E
Content-Type: text/plain;
	charset="iso-8859-1"

I found this definition in the  INTEROP Book of Carl Malamud.


The Internet (note the uppercase "I') is a network infrastructure that
supports reasearch, engineering, education, and commercial services. The
word internet (with a lowercase "i") refers to any interconnected set of
substrates (provided, of course, they are running the  internetwork protocol
IP)  



Panagiotis Tsigaridas 


-----Original Message-----
From: Eric Brunner [mailto:brunner@world.std.com]
Sent: Thursday, July 06, 2000 8:30 PM
To: ietf@ietf.org
Subject: Defining "Internet" (or "internet")



The Swedish legal definition (Patrik provided the pointer) may not be the
only one which attempts to define what "Internet" is, fixed or broken, er,
"mobile".

Anyone else with a normative legal reference, your favorite jurisdiction or
someone else's, please drop me a line. I'll summarize to the list.

Eric

------_=_NextPart_001_01BFE7DC.D8EEE23E
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: Defining &quot;Internet&quot; (or =
&quot;internet&quot;)</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I found this definition in the&nbsp; INTEROP Book of =
Carl Malamud.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>The Internet (note the uppercase &quot;I') is a =
network infrastructure that supports reasearch, engineering, education, =
and commercial services. The word internet (with a lowercase =
&quot;i&quot;) refers to any interconnected set of substrates =
(provided, of course, they are running the&nbsp; internetwork protocol =
IP)&nbsp; </FONT></P>
<BR>
<BR>

<P><FONT SIZE=3D2>Panagiotis Tsigaridas </FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Eric Brunner [<A =
HREF=3D"mailto:brunner@world.std.com">mailto:brunner@world.std.com</A>]<=
/FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, July 06, 2000 8:30 PM</FONT>
<BR><FONT SIZE=3D2>To: ietf@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: Defining &quot;Internet&quot; (or =
&quot;internet&quot;)</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>The Swedish legal definition (Patrik provided the =
pointer) may not be the</FONT>
<BR><FONT SIZE=3D2>only one which attempts to define what =
&quot;Internet&quot; is, fixed or broken, er,</FONT>
<BR><FONT SIZE=3D2>&quot;mobile&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>Anyone else with a normative legal reference, your =
favorite jurisdiction or</FONT>
<BR><FONT SIZE=3D2>someone else's, please drop me a line. I'll =
summarize to the list.</FONT>
</P>

<P><FONT SIZE=3D2>Eric</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFE7DC.D8EEE23E--



From owner-ietf-outbound  Fri Jul  7 03:20:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA16219
	for ietf-outbound.10@ietf.org; Fri, 7 Jul 2000 03:20:03 -0400 (EDT)
Received: from gwa2.fe.bosch.de (gwa2.fe.bosch.de [194.39.218.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16155
	for <ietf@ietf.org>; Fri, 7 Jul 2000 03:14:19 -0400 (EDT)
Received: (from uucp@localhost)
	by gwa2.fe.bosch.de (8.9.1/8.9.1) id HAA27822
	for <ietf@ietf.org>; Fri, 7 Jul 2000 07:13:50 GMT
Received: from fez8020.fe.bosch.de(virus-out2.fe.internet.bosch.de 10.4.4.20) by gwa2.fe.bosch.de via smap (V2.1)
	id xma027039; Fri, 7 Jul 00 07:13:22 GMT
Received: by fez7202.server.bosch.de with Internet Mail Service (5.5.2651.58)
	id <3N4KR01S>; Fri, 7 Jul 2000 09:13:15 +0200
Message-ID: <EF0BBE069A12D41197B700508B65098E0BCD52@bkmail04.bk.bosch.de>
From: "EXTERN Feigel Reinhold (Marconi; MC-AC/WES1)"
	 <Reinhold.Feigel@marconi.com>
To: ietf@ietf.org, "'welcome@mp3.com'" <welcome@mp3.com>
Subject: AW: Thanks for visiting MP3.com
Date: Fri, 7 Jul 2000 09:12:53 +0200 
Return-Receipt-To: "EXTERN Feigel Reinhold (Marconi; MC-AC/WES1)"
	 <Reinhold.Feigel@marconi.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id DAA16155
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

I didn't have you provided with my e-mail address.  That is in fact again
one of the outrageous trials to make mony using huge e-mail exploder for
free advertisment.

Disappear immediately from this location, click yourself back behind your
firewall and stay there at least over the weekend. I strongly recommend you
to use the time and  to mull over your simple mission and worthwhile
contribution to the benefit of the world as unwanted penetrator on other
peoples working area.   


> ----------
> Von: 	welcome@mp3.com[SMTP:welcome@mp3.com]
> Gesendet: 	Freitag, 7. Juli 2000 03:52
> An: 	ietf@ietf.org
> Betreff: 	Thanks for visiting MP3.com
> 
> Find your favorite type of music easily with Internet Keywords 
>   
> The MP3.com Welcome Email 	
> MP3.com Home 	
> Thanks again for visiting MP3.com and providing us with your email
> address. If you would like to unsubscribe from future MP3.com
> announcements or if you received this message in error, please see the
> bottom of this message for instructions.	
> Dear Music Fan, 
> 
> At MP3.com, our mission is simple--to be a complete Music Service Provider
> that brings artists together with their fans. Whether you're looking for
> new music from your hometown or the other side of the world, you'll find a
> wealth of free music downloads and services on MP3.com. 
> 
> Since it's all about great music, we want to make sure the tunes are
> coming in loud and clear. To listen to MP3s, you first need to install an
> MP3 player. Go here to get set up with one of our recommended players. 
> 
> Once you've got your player installed, the easiest and fastest way to fill
> it with MP3s is to use the free NetSonic Internet Accelerator. 
> 
> So dive in, explore and expand your music collection on MP3.com! 
> Regards, 
> 
>  
> Michael Robertson 
> CEO 
> MP3.com--Your Premier Music Service Provider 
> P.S. Support your favorite artists and check out their CDs for sale.
> 
> MP3.com Services 
> Try My.MP3.com! 
> 	
> *	
> *	
> Classical Music Channel - Instant access to Bach, Beethoven, Mozart and
> more 	
> *	
> *	
> Send Free Music Greeting Cards - Pick any occasion and attach your
> favorite MP3 song 	
> *	
> *	
> Catch Live Events - in your area with free Notify Me! email alerts 	
> *	
> *	
> Get Free Songs - Delivered via email with MP3.com Messenger 	
> *	
> *	
> Free MP3 Software - All you'll ever need to make and play MP3s 	
> *	
> *	
> MP3.com Top 40 - See who's topping the charts 	
> *	
> *	
> Free Extras - Such as headsets and more 	
> If you'd rather not receive future emails from MP3.com, click here to
> unsubscribe or forward this email to unsubscribe@mp3.com. 
> 
> Copyright © 1996-2000 MP3.com, Inc. All rights reserved. Legal
> Information, Privacy Policy. 
> 
>   
> 



From owner-ietf-outbound  Fri Jul  7 04:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA18623
	for ietf-outbound.10@ietf.org; Fri, 7 Jul 2000 04:20:02 -0400 (EDT)
Received: from mex.italtel.it ([138.132.117.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18423
	for <ietf@ietf.org>; Fri, 7 Jul 2000 04:10:56 -0400 (EDT)
Received: .(iltws72 [138.132.52.82]) by mex.italtel.it (8.9.0/8.9.0) with ESMTP id KAA12495
Received: .(localhost [127.0.0.1]) by iltws72.settimo.italtel.it (8.9.1a/8.9.1) with ESMTP
 id KAA10460
Received: from ic8u32.settimo.italtel.it (ic8u32.settimo.italtel.it [138.132.1.1])
	by mix.italtel.it (8.9.3/8.9.3) with SMTP id KAA25757;
	Fri, 7 Jul 2000 10:07:20 +0200 (MET DST)
Received: by ic8u32.settimo.italtel.it id AA25037; Fri, 7 Jul 2000 10:30:33 +0200
Received: from icn.siemens.it (localhost [127.0.0.1])
	by iltws09.settimo.italtel.it (8.10.1/8.10.1) with ESMTP id e678Bjt09265;
	Fri, 7 Jul 2000 10:11:45 +0200 (MET DST)
Sender: buschman@iltws09.settimo.italtel.it
Message-Id: <396590BE.E7314276@icn.siemens.it>
Date: Fri, 07 Jul 2000 10:11:43 +0200
From: Jonathan Buschmann <Jonathan.Buschmann@icn.siemens.it>
Reply-To: Jonathan.Buschmann@icn.siemens.it
X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
Mime-Version: 1.0
To: Valdis.Kletnieks@vt.edu
Cc: ietf@ietf.org
Subject: Re: Thanks for visiting MP3.com
References: <20000707015203.28912.qmail@cannon6.mp3.com> <200007070237.e672bZS33072@black-ice.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Valdis.Kletnieks@vt.edu wrote:

> On Fri, 07 Jul 2000 01:52:03 -0000, welcome@mp3.com  said:
> > Thanks again for visiting MP3.com and providing us with your
> > email address. If you would like to unsubscribe from future
> > MP3.com announcements, or if you received this message in
> > error, please see the bottom of this message for instructions.
>
> OK.. I'll bite.  Is mp3.com spamming non-visitors, or did somebody
> visit and give the IETF as their e-mail address?
>
> Sorry, it's been a long day, and I'd love to use a clue-by-four on
> somebody, but it's not obvious who to use it on... ;)
> --
>                                 Valdis Kletnieks
>                                 Operating Systems Analyst
>                                 Virginia Tech
>
>   ------------------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature

OK, I'll bite now. I know what a two-by-four is, but what's a clue-by-four?

--
Jonathan Buschmann
Siemens Information and Communication Networks S.p.A.
CLTB, Cascina Castelletto, 20019 Settimo Milanese (Mi) Italy
Phone: (+39-2)43888754  Fax: (+39-2)43887989
Jonathan.Buschmann@icn.siemens.it
 "Sometimes when you fill a vacuum, it still sucks." - Dennis Ritchie





From owner-ietf-outbound  Fri Jul  7 10:20:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA27246
	for ietf-outbound.10@ietf.org; Fri, 7 Jul 2000 10:20:03 -0400 (EDT)
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 KAA27048
	for <ietf@ietf.org>; Fri, 7 Jul 2000 10:13:59 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id JAA21093
	for <ietf@ietf.org>; Fri, 7 Jul 2000 09:11:26 -0500 (CDT)
Message-Id: <200007071411.JAA21093@rgfsparc.cr.usgs.gov>
Date: Fri, 7 Jul 2000 09:11:26 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: Thanks for visiting MP3.com
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: d4AWjCXtyRFkPdbAF1x2Kg==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>OK, I'll bite now. I know what a two-by-four is, but what's a clue-by-four?

A clue-by-four is a large, heavy, blunt object used to forcibly inject clues 
into those who have proven otherwise clue-resistant.

RGF

Robert G. Ferrell, CISSP
========================================
 Who goeth without humor goeth unarmed.
========================================



From owner-ietf-outbound  Fri Jul  7 13:00:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA03912
	for ietf-outbound.10@ietf.org; Fri, 7 Jul 2000 13:00:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03411
	for <ietf@ietf.org>; Fri, 7 Jul 2000 12:50:08 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA11613;
        Fri, 7 Jul 2000 12:50:05 -0400 (EDT)
Message-Id: <200007071650.MAA11613@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
cc: ietf@ietf.org
Subject: Re: Thanks for visiting MP3.com 
In-reply-to: Your message of "Fri, 07 Jul 2000 09:11:26 CDT."
             <200007071411.JAA21093@rgfsparc.cr.usgs.gov> 
Date: Fri, 07 Jul 2000 12:50:05 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> A clue-by-four is a large, heavy, blunt object used to forcibly inject clues 
> into those who have proven otherwise clue-resistant.

sometimes this is done by inducing unconsciousness, thereby raising the 
clue level in a subject who was formerly negatively clued.

Keith



From owner-ietf-outbound  Fri Jul  7 13:20:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA05348
	for ietf-outbound.10@ietf.org; Fri, 7 Jul 2000 13:20:04 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04388
	for <ietf@ietf.org>; Fri, 7 Jul 2000 13:04:49 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id KAA07293;
	Fri, 7 Jul 2000 10:04:21 -0700 (PDT)
Message-ID: <39660D84.3497E619@isi.edu>
Date: Fri, 07 Jul 2000 10:04:04 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.73 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: TSIGARIDAS PANAGIOTIS <P.TSIGARIDAS@telestet.gr>
CC: Eric Brunner <brunner@world.std.com>, ietf@ietf.org
Subject: Re: Defining "Internet" (or "internet")
References: <6ADD5A0DF6B1D31193430090279A2A08E5E111@mail.telestet.gr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



> TSIGARIDAS PANAGIOTIS wrote:
> 
> I found this definition in the  INTEROP Book of Carl Malamud.
> 
> The Internet (note the uppercase "I') is a network infrastructure that
> supports reasearch, engineering, education, and commercial services.
> The word internet (with a lowercase "i") refers to any interconnected
> set of substrates (provided, of course, they are running the
> internetwork protocol IP)

internet is just a truncation of internetwork, but it has come to mean
'runs IP' (and a few others, e.g., ICMP).

Internet = usually defined as a transitive closure, as in
	'speaks IP and is connected to another site already on the Internet'

	where the base-case is usually defined as the NSF-funded backbone
pre-1988

There are certainly internets that support the services above, but are
not connected to the "Cap-I Internet".

Joe



From owner-ietf-outbound  Fri Jul  7 15:40:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA11128
	for ietf-outbound.10@ietf.org; Fri, 7 Jul 2000 15:40:02 -0400 (EDT)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10584
	for <ietf@ietf.org>; Fri, 7 Jul 2000 15:25:20 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id MAA24308;
	Fri, 7 Jul 2000 12:24:00 -0700 (PDT)
Date: Fri, 7 Jul 2000 12:24:00 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200007071924.MAA24308@shell9.ba.best.com>
To: amohan@baynetworks.com
Subject: Re: wireless services
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

Aditya,

Thank you for your Internet message:

>... why are you segregating these voice features with web/email/WAP?

I do not understand that question.  My problem stems from the use of 
the verb "segregating" modified by "with" -- those two do not work 
well together.

>... using WAP, we can easily incorporate these features in today's 
> cellular phone....

Great.  Please explain how to use WAP for asynchronous audio messaging. 
I had not been told that the WAP forum had incorporated that yet.  I 
predicted it would take them at least three months longer.  In terms 
of open standards, Dave Raggett designed INPUT TYPE=AUDIO in HTML+ 
forms in 1993.  I wonder what the WML form bytecodes for that are, or 
if they have even been designed within the confines of the WML forum.

>... in WAP we have some thing called the WTAI ( Wireless Telephony 
> Application Interface ) that provides services like auto call back,
> voice mail etc to mobile handset via concept of WTA Server.

Where is WTAI documented?

If WTAI is proprietary, closed, and obscure, as it has been, it will 
have limited market share when compared to open, free, and 
well-documented standards.  Good asynch voice in a portable is just 
as good as quality email on the desktop, and the quality of voice 
browsers will get up there, too.  Likewise, IP will stay as popular 
for its API as it already is, and packet switches with popular 
routing protocols will become typical options for cellular switch 
installations.  Those APIs that allow programs to perform operations 
unpopular with the hardware owners will tend to be discouraged.

Similarly, until voicemail replies are as easy as email replies, the 
full benefits of asyncrhonous voice messaging are unlikely to be 
realized.  I feel it is very likely that the more open a standard is, 
the easier it is to reply to a message sent using that standard.

Many of us have a duty to work towards these optimum conditions.  
There are plenty of ways to make incremental improvements in the 
right direction.  The solutions that appear to have the strongest 
monitary potential in the short term are not as worthwhile as 
those that clearly do have greater strength in the long term.

Cheers,
James
-- 
http://www.bovik.org.



From owner-ietf-outbound  Fri Jul  7 18:11:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA14415
	for ietf-outbound.10@ietf.org; Fri, 7 Jul 2000 18:10:03 -0400 (EDT)
Received: from mail.sollea.com ([195.154.125.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13984
	for <ietf@ietf.org>; Fri, 7 Jul 2000 17:49:09 -0400 (EDT)
Received: from oemcomputer [193.251.41.69] by mail.sollea.com
  (SMTPD32-6.00) id AC74BCF701A6; Sat, 08 Jul 2000 00:40:52 +0200
Message-ID: <201701bfe85e$430c1b60$0a00000a@oemcomputer>
From: "Rosie Drugeault" <rosie@ptolemee.com>
To: "Jon Knight" <J.P.Knight@lboro.ac.uk>
Cc: <ietf@ietf.org>
Subject: Re: Speakers - WAP CONVENTION - The European Event
Date: Fri, 7 Jul 2000 23:56:23 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
Content-Transfer-Encoding: 8bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

why don't you come along to WAPconvention 2000 and give our delegates that
warm fuzzy feeling with the real story?

Speaker applications welcome.

Rosie Drugeault

-----Message d'origine-----
De : Jon Knight <J.P.Knight@lboro.ac.uk>
À : Rosie Drugeault <rosie@ptolemee.com>
Cc : ietf@ietf.org <ietf@ietf.org>
Date : vendredi 30 juin 2000 15:09
Objet : Re: Speakers - WAP CONVENTION - The European Event


>I might be missing something here but weren't mobile phones around for
>years before they became as ubiquituous as they are now?
>
>Tatty bye,
>
>Jim'll
>
>



From owner-ietf-outbound  Fri Jul  7 19:20:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA15285
	for ietf-outbound.10@ietf.org; Fri, 7 Jul 2000 19:20:01 -0400 (EDT)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15218
	for <ietf@ietf.org>; Fri, 7 Jul 2000 19:12:53 -0400 (EDT)
From: Jim_Stephenson-Dunn@3com.com
Received: from new-york.3com.com (new-york.3com.com [129.213.157.12])
	by seattle.3com.com (8.8.8/8.8.8) with ESMTP id QAA20513;
	Fri, 7 Jul 2000 16:12:22 -0700 (PDT)
Received: from hqoutbound.ops.3com.com (hqoutbound.OPS.3Com.COM [139.87.48.104])
	by new-york.3com.com (8.8.8/8.8.8) with SMTP id QAA08077;
	Fri, 7 Jul 2000 16:12:01 -0700 (PDT)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256915.007F4725 ; Fri, 7 Jul 2000 16:10:12 -0700
X-Lotus-FromDomain: 3COM
To: Joe Touch <touch@ISI.EDU>
cc: TSIGARIDAS PANAGIOTIS <P.TSIGARIDAS@telestet.gr>,
        Eric Brunner <brunner@world.std.com>, ietf@ietf.org
Message-ID: <88256915.007F4502.00@hqoutbound.ops.3com.com>
Date: Fri, 7 Jul 2000 16:09:53 -0700
Subject: Re: Defining "Internet" (or "internet")
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org



I always thought that Internet with capital "I" meant the Internet between
countries, whilst the internet with a lower case "i"  is referred to by the
press as an intranet within a corporate structure. Both run IP but within
different environments.

Just my 2 cents.........

Jim



**************************************************************************************
       Legal Disclaimer


The opinions expressed within this mail are specifically my own and in no way
refer to or relate to any
ongoing business and/or the technical direction of 3Com Corporation, or any
subsidiary companies or
business units within 3Com Corporation and its subsidiaries.


**************************************************************************************






Joe Touch <touch@ISI.EDU> on 07/07/2000 10:04:04 AM

Sent by:  Joe Touch <touch@ISI.EDU>


To:   TSIGARIDAS PANAGIOTIS <P.TSIGARIDAS@telestet.gr>
cc:   Eric Brunner <brunner@world.std.com>, ietf@ietf.org (Jim
      Stephenson-Dunn/C/HQ/3Com)
Subject:  Re: Defining "Internet" (or "internet")





> TSIGARIDAS PANAGIOTIS wrote:
>
> I found this definition in the  INTEROP Book of Carl Malamud.
>
> The Internet (note the uppercase "I') is a network infrastructure that
> supports reasearch, engineering, education, and commercial services.
> The word internet (with a lowercase "i") refers to any interconnected
> set of substrates (provided, of course, they are running the
> internetwork protocol IP)

internet is just a truncation of internetwork, but it has come to mean
'runs IP' (and a few others, e.g., ICMP).

Internet = usually defined as a transitive closure, as in
     'speaks IP and is connected to another site already on the Internet'

     where the base-case is usually defined as the NSF-funded backbone
pre-1988

There are certainly internets that support the services above, but are
not connected to the "Cap-I Internet".

Joe







From owner-ietf-outbound  Fri Jul  7 21:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA16514
	for ietf-outbound.10@ietf.org; Fri, 7 Jul 2000 21:30:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16474
	for <ietf@ietf.org>; Fri, 7 Jul 2000 21:24:27 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007080115.KAA02253@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id KAA02253; Sat, 8 Jul 2000 10:15:35 +0900
Subject: Re: Defining "Internet" (or "internet")
In-Reply-To: <88256915.007F4502.00@hqoutbound.ops.3com.com> from "Jim_Stephenson-Dunn@3com.com"
 at "Jul 7, 2000 04:09:53 pm"
To: Jim_Stephenson-Dunn@3com.com
Date: Sat, 8 Jul 2000 10:15:34 +0859 ()
CC: Joe Touch <touch@ISI.EDU>,
        TSIGARIDAS PANAGIOTIS <P.TSIGARIDAS@telestet.gr>,
        Eric Brunner <brunner@world.std.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Jim;

> I always thought that Internet with capital "I" meant the Internet between
> countries, whilst the internet with a lower case "i"  is referred to by the
> press as an intranet within a corporate structure. Both run IP but within
> different environments.

They are same.

							Masataka Ohta



From owner-ietf-outbound  Sat Jul  8 01:40:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA25065
	for ietf-outbound.10@ietf.org; Sat, 8 Jul 2000 01:40:02 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET ([166.60.6.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24222
	for <ietf@ietf.org>; Sat, 8 Jul 2000 01:34:05 -0400 (EDT)
Received: from cerf.mci.net ([166.60.14.53])
 by shoe.reston.mci.net (PMDF V5.2-32 #40475)
 with ESMTPA id <01JRI98QSZ4W9KM8GY@shoe.reston.mci.net> for ietf@ietf.org;
 Sat, 8 Jul 2000 01:34:00 EST
Date: Sat, 08 Jul 2000 01:08:36 -0400
From: "vinton g. cerf" <vcerf@MCI.NET>
Subject: Internet vs internet
X-Sender: vcerf@shoe.reston.mci.net
To: ietf@ietf.org
Message-id: <4.3.1.2.20000708010816.028f5e08@shoe.reston.mci.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7BIT

Date: Fri, 07 Jul 2000 21:16:47 -0700 
 >From: Jim_Stephenson-Dunn@3com.com 
 >Subject: Re: Defining "Internet" (or "internet") 
 >To: "vinton g. cerf" <vcerf@MCI.NET> 
 >X-Lotus-FromDomain: 3COM 
 >Original-recipient: rfc822;vcerf@MCI.NET 
 > 
 > 
 > 
 > 
 >Thanks for deciphering my blurb into something that makes sense. ( can you send 
 >this on to the IETF mailing list, so I don't recieve similar mails for the rest 
 >of the night correcting me ;-> ) 
 > 
 >Regards 
 > 
 >Jim 
 > 
 > 
 > 
 >"vinton g. cerf" <vcerf@MCI.NET> on 07/07/2000 08:26:07 PM 
 > 
 >Sent by: "vinton g. cerf" <vcerf@MCI.NET> 
 > 
 > 
 >To: Jim Stephenson-Dunn/C/HQ/3Com 
 >cc: 
 >Subject: Re: Defining "Internet" (or "internet") 
 > 
 > 
 > 
 >the capital I meant the public Internet - nothing to do with countries - 
 >just that this was the global, publicly accessible Internet. 
 > 
 >"internet" meant a private network that used IP technology. 
 > 
 >vint 
 > 
 >At 04:09 PM 7/7/2000 -0700, you wrote: 
 > >I always thought that Internet with capital "I" meant the Internet between 
 > >countries, whilst the internet with a lower case "i" is referred to by the 
 > >press as an intranet within a corporate structure. Both run IP but within 
 > >different environments. 
 > > 
 > >Just my 2 cents......... 
 > > 
 > >Jim 
 > > 
 > >

=================================================================
I moved to a new MCI WorldCom facility on Nov 11, 1999

MCI WorldCom
22001 Loudoun County Parkway
Building F2, Room 4115, ATTN: Vint Cerf
Ashburn, VA 20147
Telephone (703) 886-1690
FAX (703) 886-0047


"INTERNET IS FOR EVERYONE!" 
See you at INET2000, Yokohama, Japan July 18-21, 2000
http://www.isoc.org/inet2000




From owner-ietf-outbound  Sat Jul  8 01:50:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA26295
	for ietf-outbound.10@ietf.org; Sat, 8 Jul 2000 01:50:03 -0400 (EDT)
Received: from mail.shadow.net (mail.shadow.net [204.177.71.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25620
	for <ietf@ietf.org>; Sat, 8 Jul 2000 01:43:49 -0400 (EDT)
Received: from flywheel.com (ppp-114.shadow.net [207.17.58.134])
	by mail.shadow.net (8.9.3+Sun/8.9.3) with ESMTP id BAA16929;
	Sat, 8 Jul 2000 01:30:13 -0400 (EDT)
Message-ID: <3966BF8D.634551C6@flywheel.com>
Date: Sat, 08 Jul 2000 01:43:41 -0400
From: Craig Simon <cls@flywheel.com>
Reply-To: cls@flywheel.com
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Brunner <brunner@world.std.com>
CC: ietf@ietf.org
Subject: Re: Defining "Internet" (or "internet")
References: <200007061730.NAA13172@world.std.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


Eric Brunner wrote:
> Anyone else with a normative legal reference, your favorite 
...

I saw this in someone's sig line.

But what *IS* the internet?

It's the largest equivalence class in the reflexive transitive symmetric
closure of the relationship "can be reached by an IP packet from".
--Seth Breidbart 


cls



From owner-ietf-outbound  Sat Jul  8 02:10:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA03361
	for ietf-outbound.10@ietf.org; Sat, 8 Jul 2000 02:10:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02378
	for <ietf@ietf.org>; Sat, 8 Jul 2000 02:04:20 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007080557.OAA03847@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id OAA03847; Sat, 8 Jul 2000 14:56:55 +0859
Subject: Re: Internet vs internet
In-Reply-To: <4.3.1.2.20000708010816.028f5e08@shoe.reston.mci.net> from "vinton
 g. cerf" at "Jul 8, 2000 01:08:36 am"
To: "vinton g. cerf" <vcerf@MCI.NET>
Date: Sat, 8 Jul 2000 14:56:54 +0859 ()
CC: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Vint;

>  >the capital I meant the public Internet - nothing to do with countries - 
>  >just that this was the global, publicly accessible Internet. 
>  > 
>  >"internet" meant a private network that used IP technology. 

In many RFCs, "internet" is used as adnoun.

> "INTERNET IS FOR EVERYONE!" 

Huh? What is for everyone?

						Masataka Ohta



From owner-ietf-outbound  Sat Jul  8 19:43:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA10232
	for ietf-outbound.10@ietf.org; Sat, 8 Jul 2000 19:40:01 -0400 (EDT)
Received: from songbird.com (IDENT:kent@[206.14.4.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10144
	for <ietf@ietf.org>; Sat, 8 Jul 2000 19:30:52 -0400 (EDT)
Received: (from kent@localhost)
	by songbird.com (8.9.1a/8.9.1) id QAA29015
	for ietf@ietf.org; Sat, 8 Jul 2000 16:30:47 -0700
Message-ID: <20000708163047.O17221@songbird.com>
Date: Sat, 8 Jul 2000 16:30:47 -0700
From: Kent Crispin <kent@songbird.com>
To: ietf@ietf.org
Subject: Re: Internet vs internet
Mail-Followup-To: ietf@ietf.org
References: <4.3.1.2.20000708010816.028f5e08@shoe.reston.mci.net> <200007080557.OAA03847@necom830.hpcl.titech.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <200007080557.OAA03847@necom830.hpcl.titech.ac.jp>; from Masataka Ohta on Sat, Jul 08, 2000 at 02:56:54PM +0859
X-Loop: ietf@ietf.org

On Sat, Jul 08, 2000 at 02:56:54PM +0859, Masataka Ohta wrote:
> Vint;
> 
> >  >the capital I meant the public Internet - nothing to do with countries - 
> >  >just that this was the global, publicly accessible Internet. 
> >  > 
> >  >"internet" meant a private network that used IP technology. 
> 
> In many RFCs, "internet" is used as adnoun.

"adnoun"?  Is that like an adverb?

-- 
Kent Crispin                               "Do good, and you'll be
kent@songbird.com                           lonesome." -- Mark Twain



From owner-ietf-outbound  Sun Jul  9 20:32:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA11976
	for ietf-outbound.10@ietf.org; Sun, 9 Jul 2000 20:30:02 -0400 (EDT)
Received: from rgate.ricochet.net (rgate.ricochet.net [204.179.143.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11951
	for <ietf@ietf.org>; Sun, 9 Jul 2000 20:23:54 -0400 (EDT)
Received: from kaipara.live.com (mg131-017.ricochet.net [204.179.131.17])
	by rgate.ricochet.net (8.9.3/8.9.3) with ESMTP id TAA19435
	for <ietf@ietf.org>; Sun, 9 Jul 2000 19:20:53 -0500 (CDT)
Message-Id: <4.3.1.1.20000709170651.00b72650@shell7.ba.best.com>
X-Sender: rsf@shell7.ba.best.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 09 Jul 2000 17:18:32 -0700
To: ietf@ietf.org
From: Ross Finlayson <finlayson@live.com>
Subject: Any RFCs describing mailing list subscription practice?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Do we have any RFCs (or even I-Ds) that describe the preferred '3-way 
handshake' method for validating a request to subscribe to a mailing list - 
i.e., to first send back - to the requester's source email address - a 
"please confirm your subscription" response message (preferably containing 
a random token), and then add the address to the mailing list *only if* the 
user responds to this second message?

I am constantly fighting with clueless (or lazy, or opportunistic) mailing 
list operators who insist on adding bogus email addresses - containing my 
domain name - to their mailing lists, without first confirming their 
validity.  It would be nice if there were an IETF document that I could 
point them at.

	Ross.



From owner-ietf-outbound  Sun Jul  9 21:21:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA12560
	for ietf-outbound.10@ietf.org; Sun, 9 Jul 2000 21:20:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12515
	for <ietf@ietf.org>; Sun, 9 Jul 2000 21:14:34 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007100106.KAA12155@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id KAA12155; Mon, 10 Jul 2000 10:06:29 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <7731.957178550@cs.ucl.ac.uk> from Jon Crowcroft at "May 1, 2000
 11:55:50 am"
To: ietf@ietf.org
Date: Mon, 10 Jul 2000 10:06:29 +0859 ()
CC: "vinton g. cerf" <vcerf@MCI.NET>, Matt Holdrege <holdrege@lucent.com>,
        Thomas Narten <narten@raleigh.ibm.com>, ietf@ietf.org,
        J.Crowcroft@CS.UCL.AC.UK
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Dear all;

Based on the previous discussion,

Jon> In message <200005010842.RAA11363@necom830.hpcl.titech.ac.jp>, Masataka Ohta ty
Jon> ped:
Jon>  
Jon>  >>	Is it fair if providers using iMODE or WAP are advertised
Jon>  >>	to be ISPs?
Jon>  >>
Jon>  >>	Is it fair if providers using NAT are advertised to be ISPs?
Jon>  >>
Jon>  >>My answer to both questions is
Jon>  >>
Jon>  >>	No, while they may be Internet Service Access Providers and
Jon>  >>	NAT users may be IP Service Providers, they don't provide
Jon>  >>	Internet service and are no ISPs.
Jon> 
Jon> i agree:
Jon> in the UK, i would say that someone claiming internet access via WAP
Jon> would be in breach of the trades description act.
Jon> 
Jon>  >>Any oppositions?
Jon>  
Jon> not from here (for wap - i dont know enough about iMODE to comment)

and lack of oppsitions in the thread, I have drafted an attached ID.

However, IESG is blocking the publication of the ID (it is just an
Internet Draft, NOT an Informational RFC)!

IESG says they have not even saw the content, which means a lot of
time will be wasted further.

So, I post the draft to the Mailing List.

Any comments on the content of the draft? Comments for the blockage,
if any, should be given with a separate subject?

I hope IESG has not taken the obvious next step of the moderation
of the Mailing List.

							Masataka Ohta
---






INTERNET DRAFT                                                   M. Ohta
draft-ohta-isps-00.txt                     Tokyo Institute of Technology
                                                               July 2000

                         The Internet and ISPs

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   Copyright (C) The Internet Society (May/1/2000).  All Rights
   Reserved.

Abstract

   This memo gives definitions on the Internet and ISPs (Internet
   Service Providers).

1. The Internet

   The Internet is a public IP [1, 2] network globally connected end to
   end [3] at the Internetworking layer.

2. ISPs

   A network provider is an ISP, if and only if its network, including
   access parts of the network to its subscribers, is a part of the
   Internet.

   As such, ISPs must preserve the end to end and globally connected
   principles of the Internet at the Internetworking layer.



M. Ohta                Expires on January 1, 2001               [Page 1]

INTERNET DRAFT                    ISPs                         July 2000


   A network provider of a private IP or non-IP network, which is
   connected to the Internet through an application and/or transport
   gateway is not an ISP.

   Dispit the requirement of "global connectivity", a network provider
   may use transparent firewalls to the Internet with no translation to
   filter out a limited number of problematic well known ports of TCP
   and/or UDP and can still be an ISP.  However, if filtering out is a
   default and only a limited number of protocols are allowed to pass
   the firewalls (which means snooping of transport/application layer
   protocols), it can not be regarded as full connectivity to the
   Internet and the provider is not an ISP.

3. Security Considerations

   While some people may think that filtering by application/transport
   gateways offer some sort of security, they should recognize that
   macro virus in e-mails can pass and are passing through all such
   gateways.

4. References

   [1] J. Postel, "Internet Protocol", RFC791, September 1981.

   [2] S. Deering, R. Hinden, "Internet Protocol, Version 6 (IPv6)
   Specification", RFC2460, December 1998.

   [3] B. Carpenter, "Architectural Principles of the Internet",
   RFC1958, June 1996.

5. Author's Address

   Masataka Ohta
   Computer Center, Tokyo Institute of Technology
   2-12-1, O-okayama, Meguro-ku, Tokyo 152-8550, JAPAN

   Phone: +81-3-5734-3299
   Fax: +81-3-5734-3415
   EMail: mohta@necom830.hpcl.titech.ac.jp












M. Ohta                Expires on January 1, 2001               [Page 2]

INTERNET DRAFT                    ISPs                         July 2000


6. Full Copyright Statement

   "Copyright (C) The Internet Society (July/1/2000).  All Rights
   Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.























M. Ohta                Expires on January 1, 2001               [Page 3]




From owner-ietf-outbound  Sun Jul  9 21:31:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA12641
	for ietf-outbound.10@ietf.org; Sun, 9 Jul 2000 21:30:03 -0400 (EDT)
Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.147.1.144])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12522
	for <ietf@ietf.org>; Sun, 9 Jul 2000 21:15:21 -0400 (EDT)
Received: from [24.147.154.31] (chapins.ne.mediaone.net [24.147.154.31])
	by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id VAA11355;
	Sun, 9 Jul 2000 21:15:20 -0400 (EDT)
Mime-Version: 1.0
X-Sender: lyman@127.0.0.1
Message-Id: <v04220803b58ed1e9a3ea@[192.168.181.1]>
In-Reply-To: <3966BF8D.634551C6@flywheel.com>
References: <200007061730.NAA13172@world.std.com>
 <3966BF8D.634551C6@flywheel.com>
Date: Sun, 9 Jul 2000 21:15:19 -0400
To: cls@flywheel.com
From: Lyman Chapin <lyman@bbn.com>
Subject: Re: Defining "Internet" (or "internet")
Cc: ietf@ietf.org, lyman@bbn.com
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Craig,

 From RFC 1287:

"If I could PING you, and you could PING me, then we were both on the 
Internet, and a satisfying working definition of the Internet could 
be constructed as a roughly transitive closure of IP-speaking 
systems. This model of the Internet was simple, uniform, and - 
perhaps most important - testable. The IP-connectivity model clearly 
distinguished systems that were "on the Internet" from those that 
were not."

In the same RFC, we proposed a different answer to your "what *IS* 
the Internet?" question, based not on IP (network address) 
connectivity but on the shared domain name space managed by DNS - 
"the Internet" consists of entities nameable within the DNS, however 
they may be interconnected by underlying networks.

- Lyman

At 1:43 AM -0400 7/8/00, Craig Simon wrote:
>Eric Brunner wrote:
>  > Anyone else with a normative legal reference, your favorite
>...
>
>I saw this in someone's sig line.
>
>But what *IS* the internet?
>
>It's the largest equivalence class in the reflexive transitive symmetric
>closure of the relationship "can be reached by an IP packet from".
>--Seth Breidbart
>
>
>cls
>
>-
>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  Sun Jul  9 23:11:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA15305
	for ietf-outbound.10@ietf.org; Sun, 9 Jul 2000 23:10:01 -0400 (EDT)
Received: from torque.pothole.com ([38.138.52.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15253
	for <ietf@ietf.org>; Sun, 9 Jul 2000 23:02:03 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id XAA22624;
	Sun, 9 Jul 2000 23:04:19 -0400 (EDT)
Message-Id: <200007100304.XAA22624@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: Ross Finlayson <finlayson@live.com>
cc: ietf@ietf.org
Subject: Re: Any RFCs describing mailing list subscription practice? 
In-reply-to: Your message of "Sun, 09 Jul 2000 17:18:32 PDT."
             <4.3.1.1.20000709170651.00b72650@shell7.ba.best.com> 
Date: Sun, 09 Jul 2000 23:04:19 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org


As far as I know, there is no such IETF document.  The only even
vaguely related RFCs I know of are 2369 and 1211.  Standardizing list
processor commands has proven to be very controversial.  But a BCP
supporting use of a mail loop to confirm subscription would be a good
thing and should be doable...

Thanks,
Donald

From:  Ross Finlayson <finlayson@live.com>
Message-Id:  <4.3.1.1.20000709170651.00b72650@shell7.ba.best.com>
X-Sender:  rsf@shell7.ba.best.com
Date:  Sun, 09 Jul 2000 17:18:32 -0700
To:  ietf@ietf.org

>Do we have any RFCs (or even I-Ds) that describe the preferred '3-way 
>handshake' method for validating a request to subscribe to a mailing list - 
>i.e., to first send back - to the requester's source email address - a 
>"please confirm your subscription" response message (preferably containing 
>a random token), and then add the address to the mailing list *only if* the 
>user responds to this second message?
>
>I am constantly fighting with clueless (or lazy, or opportunistic) mailing 
>list operators who insist on adding bogus email addresses - containing my 
>domain name - to their mailing lists, without first confirming their 
>validity.  It would be nice if there were an IETF document that I could 
>point them at.
>
>	Ross.



From owner-ietf-outbound  Mon Jul 10 03:41:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA00136
	for ietf-outbound.10@ietf.org; Mon, 10 Jul 2000 03:40:02 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA00034
	for <ietf@ietf.org>; Mon, 10 Jul 2000 03:29:07 -0400 (EDT)
Received: from cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.02891-0@bells.cs.ucl.ac.uk>; Mon, 10 Jul 2000 08:27:39 +0100
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-reply-to: Your message of "Mon, 10 Jul 2000 10:06:29 +0859." <200007100106.KAA12155@necom830.hpcl.titech.ac.jp>
Date: Mon, 10 Jul 2000 08:27:37 +0100
Message-ID: <2889.963214057@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


 >>Any comments on the content of the draft? 

I would go further - first to define by exclusion, secondly to define
a new class of providers (according tro common uisage) so that
discussion can proceed 

An ISP _hosts_ its own and customer's hosts.  Hosts follow the 
hosts requirements RFC, at least.

An ISP uses routers to interconnect its, its customers, and other to ISPs
networks, Routers follow the router requirements RFC, at least.

Service Organisations that don't allow a host or router that follows the above
definition to excercise capabilities defined are what we now know as
Content Service Providers, and must provide application level gateways, 
Application Service Providers, and offer portals or ALGs. In each case there
may be good performance or security reasons for this mode of service, but
there will usually be lack of flexibility or ease of introdution to new
services, content and applications in general. 

personal comment
Other classes of organisation may simply be providing a subset of
internet services - I don't see a market or technical case for these
and in fact would encourage regulatory bodies to see if these types of
organisations are trying to achieve lock out or are engaged in 
other types of monopolistic or anti-competitive behaviour. :-)

cheers
j.



From owner-ietf-outbound  Mon Jul 10 04:50:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA00763
	for ietf-outbound.10@ietf.org; Mon, 10 Jul 2000 04:50:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00736
	for <ietf@ietf.org>; Mon, 10 Jul 2000 04:44:23 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007100836.RAA14137@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id RAA14137; Mon, 10 Jul 2000 17:36:07 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <2889.963214057@cs.ucl.ac.uk> from Jon Crowcroft at "Jul 10, 2000
 08:27:37 am"
To: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
Date: Mon, 10 Jul 2000 17:36:05 +0859 ()
CC: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Jon;

>  >>Any comments on the content of the draft? 
> 
> I would go further - first to define by exclusion, secondly to define
> a new class of providers (according tro common uisage) so that
> discussion can proceed 

My intention is to provide a semi permanent definition as an Informational
RFC.

It is important to make the definition protected by bogus opinions
of various bodies including IETF.

> An ISP _hosts_ its own and customer's hosts.  Hosts follow the 
> hosts requirements RFC, at least.
> 
> An ISP uses routers to interconnect its, its customers, and other to ISPs
> networks, Routers follow the router requirements RFC, at least.

They are requirements by IETF.

Worse, even in IETF, there is no Internet Standard of router requirements
yet and the newest revision to the Proposed Standard is BCP.

So, please don't attempt to rely on it.

> Service Organisations that don't allow a host or router that follows the above
> definition to excercise capabilities defined are what we now know as
> Content Service Providers, and must provide application level gateways, 
> Application Service Providers, and offer portals or ALGs. In each case there
> may be good performance or security reasons for this mode of service, but
> there will usually be lack of flexibility or ease of introdution to new
> services, content and applications in general. 

I think my draft covers the case to make such network providers
not ISPs.

> personal comment
> Other classes of organisation may simply be providing a subset of
> internet services - I don't see a market or technical case for these
> and in fact would encourage regulatory bodies to see if these types of
> organisations are trying to achieve lock out or are engaged in 
> other types of monopolistic or anti-competitive behaviour. :-)

I just want to make it illegal for these types of organisations call
their service "Internet" or "internet".

It's something like "Olympic".

							Masataka Ohta



From owner-ietf-outbound  Mon Jul 10 05:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA00944
	for ietf-outbound.10@ietf.org; Mon, 10 Jul 2000 05:10:03 -0400 (EDT)
Received: from mailer1.lut.ac.uk (mailer1.lut.ac.uk [158.125.1.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00918
	for <ietf@ietf.org>; Mon, 10 Jul 2000 05:07:34 -0400 (EDT)
Received: from jon (helo=localhost)
	by mailer1.lut.ac.uk with local-smtp (Exim 2.10 #1)
	id 13BZXK-0003XL-00; Mon, 10 Jul 2000 10:07:34 +0100
Date: Mon, 10 Jul 2000 10:07:33 +0100 (BST)
From: Jon Knight <J.P.Knight@lboro.ac.uk>
X-Sender: jon@mailer1
To: Rosie Drugeault <rosie@ptolemee.com>
cc: ietf@ietf.org
Subject: Re: Speakers - WAP CONVENTION - The European Event
In-Reply-To: <201701bfe85e$430c1b60$0a00000a@oemcomputer>
Message-ID: <Pine.SOL.3.96.1000710100700.13401B-100000@mailer1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Lboro-Filtered: mailer1.lut.ac.uk, Mon, 10 Jul 2000 10:07:34 +0100
X-Loop: ietf@ietf.org

On Fri, 7 Jul 2000, Rosie Drugeault wrote:
> why don't you come along to WAPconvention 2000 and give our delegates that
> warm fuzzy feeling with the real story?

'Cos I've got better things to do with my time than go to conventions. ;-)

Tatty bye,

Jim'll



From owner-ietf-outbound  Mon Jul 10 09:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA09017
	for ietf-outbound.10@ietf.org; Mon, 10 Jul 2000 09:50:02 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08499
	for <ietf@ietf.org>; Mon, 10 Jul 2000 09:35:55 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 13Bdit-000PFI-00; Mon, 10 Jul 2000 06:35:47 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <2889.963214057@cs.ucl.ac.uk>
	<200007100836.RAA14137@necom830.hpcl.titech.ac.jp>
Message-Id: <E13Bdit-000PFI-00@rip.psg.com>
Date: Mon, 10 Jul 2000 06:35:47 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>> I would go further - first to define by exclusion, secondly to define
>> a new class of providers (according tro common uisage) so that
>> discussion can proceed 
> 
> My intention is to provide a semi permanent definition as an Informational
> RFC.
> 
> It is important to make the definition protected by bogus opinions
> of various bodies including IETF.

of course you will exuse the providers if we continue to be perverse and
find new business models.

randy



From owner-ietf-outbound  Mon Jul 10 19:10:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA01455
	for ietf-outbound.10@ietf.org; Mon, 10 Jul 2000 19:10:02 -0400 (EDT)
Received: from wodc7-2.relay.mail.uu.net (wodc7-2.relay.mail.uu.net [199.171.54.115])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01431
	for <ietf@ietf.org>; Mon, 10 Jul 2000 19:09:47 -0400 (EDT)
Received: from chibdc01.thgus.com by wodc7mr0.ffx.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [208.205.25.50])
	id QQixhk28831
	for <ietf@ietf.org>; Mon, 10 Jul 2000 23:09:48 GMT
Received: by CHIBDC01 with Internet Mail Service (5.5.2650.21)
	id <347B7MDG>; Mon, 10 Jul 2000 18:16:25 -0500
Message-ID: <01B2EF133BD0D311B652009027DE74CD33223A@CHIBDC01>
From: Ann Pendleton <AnnP@thgus.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject:  MPLS Global Summit
Date: Mon, 10 Jul 2000 18:16:23 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

MPLS Global Summit taking place October 3-4, 2000 at the Fairmont Copley
Plaza in Boston, MA.   

As you may know this is ICM's third MPLS event.  The program has been
recognized as one of the leading industry events.  The most recent gathering
in San Diego attracted approximately 250 representatives from leading
carriers and organizations worldwide.

Over the past year, MPLS has received a great deal of attention as the next
great traffic engineering solution.  The core benefits of MPLS have been
widely promoted and now carriers must examine how MPLS can enhance their
networks and services in a manner that extends benefits to their customers.
Join us for this two tracked, information-packed event.

Further information and registration details are available online at
www.IT-TelecomSolutions.com <http://www.IT-TelecomSolutions.com> .  



From owner-ietf-outbound  Mon Jul 10 21:51:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA04156
	for ietf-outbound.10@ietf.org; Mon, 10 Jul 2000 21:50:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04085
	for <ietf@ietf.org>; Mon, 10 Jul 2000 21:43:50 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id VAA20661;
        Mon, 10 Jul 2000 21:43:13 -0400 (EDT)
Message-Id: <200007110143.VAA20661@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Randy Bush <randy@psg.com>
cc: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>,
        Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Mon, 10 Jul 2000 06:35:47 PDT."
             <E13Bdit-000PFI-00@rip.psg.com> 
Date: Mon, 10 Jul 2000 21:43:13 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> of course you will exuse the providers if we continue to be perverse and
> find new business models.

not bloody likely.  some things are inexcusable.  munging data in
transit is one of them.  the fact that you may have a business
model that says you can make money doing something that is inexcusable
is not a justification for doing that thing.

I'm sick and tired of folks justifing all manner of brain damage
merely because they think they can make money at it.  you'd think
that they believe that the only purpose in life is to make money.

Keith

p.s. sorry to single you out, there are far worse culprits.



From owner-ietf-outbound  Mon Jul 10 22:30:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA04665
	for ietf-outbound.10@ietf.org; Mon, 10 Jul 2000 22:30:03 -0400 (EDT)
Received: from ogma.cisco.com (ogma.cisco.com [144.254.74.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04500
	for <ietf@ietf.org>; Mon, 10 Jul 2000 22:13:23 -0400 (EDT)
Received: from nordic.cisco.com (nordic.cisco.com [144.254.116.14])
	by ogma.cisco.com (Postfix) with ESMTP
	id 2E3AABA4; Tue, 11 Jul 2000 04:12:54 +0200 (MET DST)
Received: from [10.0.0.3] ([171.70.221.22])
	by nordic.cisco.com (8.8.8+Sun/8.8.8) with ESMTP id EAA17635;
	Tue, 11 Jul 2000 04:12:51 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: pfaltstr@nordic.cisco.com
Message-Id: <p04320402b590408e2bcd@[10.0.0.3]>
In-Reply-To: <200007110143.VAA20661@astro.cs.utk.edu>
References: <200007110143.VAA20661@astro.cs.utk.edu>
Date: Mon, 10 Jul 2000 20:13:19 -0700
To: Keith Moore <moore@cs.utk.edu>, Randy Bush <randy@psg.com>
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>,
        Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 21.43 -0400 00-07-10, Keith Moore wrote:
>not bloody likely.  some things are inexcusable.  munging data in
>transit is one of them.  the fact that you may have a business
>model that says you can make money doing something that is inexcusable
>is not a justification for doing that thing.

I don't see any problems people making money on weird 
NAT-munging-weirdo-webonly-wap things which they sell to customers, 
BUT, it is NOT Internet access.

I would not buy it, because I want Internet access.

What I oppose strongly, is that people sell weird stuff and call it Internet.

   paf



From owner-ietf-outbound  Mon Jul 10 23:00:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA06171
	for ietf-outbound.10@ietf.org; Mon, 10 Jul 2000 23:00:02 -0400 (EDT)
Received: from roam.psg.com (mg-206253200-105.ricochet.net [206.253.200.105])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04627
	for <ietf@ietf.org>; Mon, 10 Jul 2000 22:28:38 -0400 (EDT)
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 13BpkK-0000T3-00; Mon, 10 Jul 2000 19:26:04 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Keith Moore <moore@cs.utk.edu>
Cc: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>,
        Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
References: <E13Bdit-000PFI-00@rip.psg.com>
	<200007110143.VAA20661@astro.cs.utk.edu>
Message-Id: <E13BpkK-0000T3-00@roam.psg.com>
Date: Mon, 10 Jul 2000 19:26:04 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>> of course you will exuse the providers if we continue to be perverse and
>> find new business models.
> 
> not bloody likely.  some things are inexcusable.  munging data in
> transit is one of them.  the fact that you may have a business
> model that says you can make money doing something that is inexcusable
> is not a justification for doing that thing.
> 
> I'm sick and tired of folks justifing all manner of brain damage
> merely because they think they can make money at it.  you'd think
> that they believe that the only purpose in life is to make money.
> 
> Keith
> 
> p.s. sorry to single you out, there are far worse culprits.

have you tried valerian root tea?



From owner-ietf-outbound  Tue Jul 11 03:11:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA21490
	for ietf-outbound.10@ietf.org; Tue, 11 Jul 2000 03:10:02 -0400 (EDT)
Received: from gadolinium (gadolinium.btinternet.com [194.73.73.111])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21459
	for <ietf@ietf.org>; Tue, 11 Jul 2000 03:08:52 -0400 (EDT)
Received: from [62.7.61.46] (helo=patonmj)
	by gadolinium with smtp (Exim 3.03 #83)
	id 13BuA0-0005GQ-00
	for ietf@ietf.org; Tue, 11 Jul 2000 08:08:52 +0100
From: "mark.paton" <mark.paton@btinternet.com>
To: <ietf@ietf.org>
Subject: RE: draft-ietf-nat-protocol-complications-02.txt 
Date: Tue, 11 Jul 2000 08:12:37 +0100
Message-ID: <NCBBINIKLKLJEEDCGLOAAECMCHAA.mark.paton@btinternet.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0011_01BFEB0F.C7243960"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-reply-to: <E13BpkK-0000T3-00@roam.psg.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901
Importance: Normal
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

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

I thought the real purpose of life was too make
money!!

Joking aside, I agree with Keith Moore, some
things are totally unacceptable and this falls
into that category.  Data integrity should be of
the utmost importance in any network.  The
InterNet is no exception.

Regards

Mark Paton CEO/DIR. Internet Network Eng
Mercury Network Systems Limited
+44 585 649051
+44 1256 761925
http://www.mnsl.org

"Mercury Network Systems - The Unstoppable Force"

This e-mail is intended only for the addressee
named above. As this e-mail may contain
confidential or privileged information if you are
not, or suspect that you are not, the named
addressee or the person responsible for delivering
the message to the named addressee, please
telephone us immediately. Please note that we
cannot guarantee that this message or any
attachment is virus free or has not been
intercepted and amended.


The views of the author may not necessarily
reflect those of the Company.


-----Original Message-----
From: Randy Bush [mailto:randy@psg.com]
Sent: 11 July 2000 03:26
To: Keith Moore
Cc: Masataka Ohta; Jon Crowcroft; ietf@ietf.org
Subject: Re:
draft-ietf-nat-protocol-complications-02.txt


>> of course you will exuse the providers
if we continue to be perverse and
>> find new business models.
>
> not bloody likely.  some things are
inexcusable.  munging data in
> transit is one of them.  the fact that
you may have a business
> model that says you can make money
doing something that is inexcusable
> is not a justification for doing that thing.
>
> I'm sick and tired of folks justifing
all manner of brain damage
> merely because they think they can make
money at it.  you'd think
> that they believe that the only purpose
in life is to make money.
>
> Keith
>
> p.s. sorry to single you out, there are
far worse culprits.

have you tried valerian root tea?


------=_NextPart_000_0011_01BFEB0F.C7243960
Content-Type: text/x-vcard;
	name="Mark. J.S Paton.vcf"
Content-Disposition: attachment;
	filename="Mark. J.S Paton.vcf"
Content-Transfer-Encoding: quoted-printable

BEGIN:VCARD
VERSION:2.1
N:Paton;Mark.;J.S;;
FN:Mark. J.S Paton
ORG:Mnsl;Consultancy
TITLE:Network Design / Support
TEL;WORK;VOICE:+44 0585 649051
TEL;CELL;VOICE:+44 (0585) 649051
ADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;Basingstoke;Willow =
Cottage=3D0D=3D0AReading Road;Mattingley;Hampshire;RG27 8JU;=3D
United Kingdom
LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:Basingstoke=3D0D=3D0AWillow =
Cottage=3D0D=3D0AReading Road=3D0D=3D0AMattingley, Hampshire=3D
 RG27 8JU=3D0D=3D0AUnited Kingdom
URL:
URL:http://www.mnsl.org
EMAIL;PREF;INTERNET:mark.paton@mnsl.org
REV:19990422T133901Z
END:VCARD

------=_NextPart_000_0011_01BFEB0F.C7243960--



From owner-ietf-outbound  Tue Jul 11 03:21:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA21634
	for ietf-outbound.10@ietf.org; Tue, 11 Jul 2000 03:20:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21609
	for <ietf@ietf.org>; Tue, 11 Jul 2000 03:18:18 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id DAA27111;
        Tue, 11 Jul 2000 03:17:49 -0400 (EDT)
Message-Id: <200007110717.DAA27111@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>
cc: Keith Moore <moore@cs.utk.edu>, Randy Bush <randy@psg.com>,
        Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>,
        Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Mon, 10 Jul 2000 20:13:19 PDT."
             <p04320402b590408e2bcd@[10.0.0.3]> 
Date: Tue, 11 Jul 2000 03:17:47 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> What I oppose strongly, is that people sell weird stuff and call it Internet.

I've never seen a marketing person that wouldn't lie and do exactly that.
If folks want to buy wierd stuff, and they know it's wierd stuff and
are aware of its limitations, I don't have much problem with that.
But I've yet to see a NAT product that was advertised honestly.



From owner-ietf-outbound  Tue Jul 11 10:32:50 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA01954
	for ietf-outbound.10@ietf.org; Tue, 11 Jul 2000 10:30:02 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01849
	for <ietf@ietf.org>; Tue, 11 Jul 2000 10:27:41 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 13C10e-000DNp-00; Tue, 11 Jul 2000 07:27:40 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "mark.paton" <mark.paton@btinternet.com>
Cc: <ietf@ietf.org>
Subject: RE: draft-ietf-nat-protocol-complications-02.txt 
References: <E13BpkK-0000T3-00@roam.psg.com>
	<NCBBINIKLKLJEEDCGLOAAECMCHAA.mark.paton@btinternet.com>
Message-Id: <E13C10e-000DNp-00@rip.psg.com>
Date: Tue, 11 Jul 2000 07:27:40 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> Joking aside, I agree with Keith Moore, some things are totally
> unacceptable and this falls into that category.

so we try to stay somewhere within the solar system, let's review what
"this" is.  it was a discussion with masataka and jon about defining classes
of providers.

    From: Randy Bush <randy@PSG.COM>
    To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
    Cc: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>, ietf@ietf.org
    Subject: Re: draft-ietf-nat-protocol-complications-02.txt
    Date: Mon, 10 Jul 2000 06:35:47 -0700

    >> I would go further - first to define by exclusion, secondly to define
    >> a new class of providers (according tro common uisage) so that
    >> discussion can proceed
    >
    > My intention is to provide a semi permanent definition as an
    > Informational RFC.
    >
    > It is important to make the definition protected by bogus opinions
    > of various bodies including IETF.

    of course you will exuse the providers if we continue to be perverse and
    find new business models.

masataka was saying that he could classify providers given a rather fixed
model.  i was saying that the world changes and that providers will find
new business models and bend masataka's rigid classification.

and then keith came out of left field without bothering to actually read
the thread and went off on his usual jihad against whatever perfidy drives
him to wild accusations and libel this week, usually nats, proxies, and
whatever.  booooring.

but yes, likely some things in this world are not acceptable to some
segment of the population.  so don't accept them.  but life goes on and
things change.

randy



From owner-ietf-outbound  Tue Jul 11 10:42:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02325
	for ietf-outbound.10@ietf.org; Tue, 11 Jul 2000 10:40:03 -0400 (EDT)
Received: from monitor.internaut.com (mg-206191146-48.ricochet.net [206.191.146.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02165
	for <ietf@ietf.org>; Tue, 11 Jul 2000 10:35:50 -0400 (EDT)
From: aboba@internaut.com
Received: from kidneybean ([204.57.137.38])
	by monitor.internaut.com (8.9.2/8.8.8) with SMTP id HAA81350;
	Tue, 11 Jul 2000 07:32:04 -0700 (PDT)
Reply-To: <aboba@internaut.com>
To: "=?us-ascii?Q?'Patrik_Faltstrom'?=" <paf@cisco.com>,
        "'Randy Bush'" <randy@psg.com>
Cc: <ietf@ietf.org>
Subject: RE: draft-ietf-nat-protocol-complications-02.txt
Date: Tue, 11 Jul 2000 04:21:38 -0700
Message-ID: <010301bfeb2a$2ed8d7e0$268939cc@ntdev.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <p04320402b590408e2bcd@[10.0.0.3]>
X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>I don't see any problems people making money 
>on weird NAT-munging-weirdo-webonly-wap things 
>which they sell to customers

"Making money" implies that for every seller
there is a willing buyer. For NAT to have
progressed from a twinkle-in-the-eye to the
near ubiquity that it will have in a few
years, there need to be a *lot* of willing
buyers. The marketplace rewards those who
satisfy a perceived need. 

If we would prefer that those customers
choose another solution (IPv6), then we
will need to make it every bit as easy 
to install and use as the alternative. 

However, even that may not be enough --
because history tells us that displacing
a deeply entrenched competitor (IPv4 + NAT) 
can generally only be accomplished by 
exploiting points of inflection. Perhaps 
Wireless and Infiniband will provide 
the required inflection points; we will see.

>BUT, it is NOT Internet access.

I'm not sure that in practice this is a
distinction that will ever be universally
understood in the marketplace. AOL isn't
Internet access either, but it serves
more than 25 million users. As with
NAT, AOL thrives because it fills a
perceived need better than the alternative.

>I would not buy it, because I want Internet access.

Perhaps it is more instructive to turn the tables
and complete the sentence:

"I would prefer {insert abomination here} to Internet
Access because {insert reason for preferring 
abomination}"

Then, try to complete an alternative sentence:

"I would prefer IPv6 to {insert abomination here} because
in addition to providing {insert reason for preferring
abomination} it can also enable my business to grow
faster in ways that IPv4 and {insert abomination here} 
cannot provide: {insert tangible business benefits of 
IPv6 here}"

The goal is to repeat the exercise until the above 
sentence convinces large numbers of customers 
(who may not know what Internet Access is) to part
with their money. 



From owner-ietf-outbound  Tue Jul 11 12:02:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA05849
	for ietf-outbound.10@ietf.org; Tue, 11 Jul 2000 12:00:02 -0400 (EDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05524
	for <ietf@ietf.org>; Tue, 11 Jul 2000 11:52:02 -0400 (EDT)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id IAA24115;
	Tue, 11 Jul 2000 08:52:04 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id PAA11284;
	Tue, 11 Jul 2000 15:52:04 GMT
Date: Tue, 11 Jul 2000 15:52:04 GMT
Message-Id: <200007111552.PAA11284@gra.isi.edu>
To: randy@psg.com
Subject: RE: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org


  *> 
  *> but yes, likely some things in this world are not acceptable to some
  *> segment of the population.  so don't accept them.  but life goes on and
  *> things change.
  *> 
  *> randy
  *> 
  *> 
Resist entropy.

Bob Braden



From owner-ietf-outbound  Tue Jul 11 15:32:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA17176
	for ietf-outbound.10@ietf.org; Tue, 11 Jul 2000 15:30:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16568
	for <ietf@ietf.org>; Tue, 11 Jul 2000 15:14:36 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA02596;
        Tue, 11 Jul 2000 15:14:34 -0400 (EDT)
Message-Id: <200007111914.PAA02596@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Randy Bush <randy@psg.com>
cc: "mark.paton" <mark.paton@btinternet.com>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Tue, 11 Jul 2000 07:27:40 PDT."
             <E13C10e-000DNp-00@rip.psg.com> 
Date: Tue, 11 Jul 2000 15:14:34 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> masataka was saying that he could classify providers given a rather fixed
> model.  i was saying that the world changes and that providers will find
> new business models and bend masataka's rigid classification.

yes, but the desire to have classification of providers is significantly 
motiviated by providers that keep coming up with "business models" that 
involve deliberately corrupting the data that they carry.

of course such providers would rather act as if they weren't doing anything
harmful...  which only further illustrates the need to have such 
classifications.

Keith  



From owner-ietf-outbound  Tue Jul 11 19:22:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA23111
	for ietf-outbound.10@ietf.org; Tue, 11 Jul 2000 19:20:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22920
	for <ietf@ietf.org>; Tue, 11 Jul 2000 19:14:23 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007112307.IAA22643@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id IAA22643; Wed, 12 Jul 2000 08:07:02 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <200007111552.PAA11284@gra.isi.edu> from Bob Braden at "Jul 11,
 2000 03:52:04 pm"
To: Bob Braden <braden@ISI.EDU>
Date: Wed, 12 Jul 2000 08:07:01 +0859 ()
CC: randy@psg.com, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Bob;

>   *> but yes, likely some things in this world are not acceptable to some
>   *> segment of the population.  so don't accept them.  but life goes on and
>   *> things change.
>   *> 
>   *> randy

Changes are already implied by RC1958, which I refer.

As things change, new RFCs can be issued.

> Resist entropy.

You can't.

Entropy and the number of RFCs monotonically increase.

						Masataka Ohta



From owner-ietf-outbound  Tue Jul 11 19:31:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA23317
	for ietf-outbound.10@ietf.org; Tue, 11 Jul 2000 19:30:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22931
	for <ietf@ietf.org>; Tue, 11 Jul 2000 19:14:33 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007112312.IAA22690@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id IAA22690; Wed, 12 Jul 2000 08:12:21 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <E13Bdit-000PFI-00@rip.psg.com> from Randy Bush at "Jul 10, 2000
 06:35:47 am"
To: Randy Bush <randy@psg.com>
Date: Wed, 12 Jul 2000 08:12:20 +0859 ()
CC: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Randy;

> > My intention is to provide a semi permanent definition as an Informational
> > RFC.
> > 
> > It is important to make the definition protected by bogus opinions
> > of various bodies including IETF.
> 
> of course you will exuse the providers if we continue to be perverse and
> find new business models.

Exuse? If you mean execution or decapitalization, yes, I will.

							Masataka Ohta



From owner-ietf-outbound  Tue Jul 11 20:32:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA24054
	for ietf-outbound.10@ietf.org; Tue, 11 Jul 2000 20:30:02 -0400 (EDT)
Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23977
	for <ietf@ietf.org>; Tue, 11 Jul 2000 20:21:12 -0400 (EDT)
Received: from Software.com ([207.175.94.192]) by mta1biz.bizmailsrvcs.net
          with ESMTP
          id <20000712002139.HIFC459995.mta1biz.bizmailsrvcs.net@Software.com>
          for <ietf@ietf.org>; Tue, 11 Jul 2000 19:21:40 -0500
Sender: droyer
Message-ID: <396BA950.1C87D29B@Software.com>
Date: Tue, 11 Jul 2000 16:10:08 -0700
From: Doug Royer <Doug.Royer@Software.com>
Reply-To: "ietf@ietf.org" <ietf@ietf.org>
Organization: Software.com
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Is WAP mobile Internet??
References: <200007051324.JAA19516@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Keith Moore wrote:
> 
> > Here in Japan we have 8 million non-WAP mobile internet users,
> 
> uh, no.  if you don't have IP to the phone, it's not mobile Internet.
> calling it Internet is just deceptive advertising.

I agree.

I have cell phone with an IP address. When it is powered on I can ping
it from any internet system.

I can browse the internet with the help of a internet <-> WAP gateway.

The two seem separate to me.

-Doug



From owner-ietf-outbound  Tue Jul 11 20:41:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA24234
	for ietf-outbound.10@ietf.org; Tue, 11 Jul 2000 20:40:02 -0400 (EDT)
Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24145
	for <ietf@ietf.org>; Tue, 11 Jul 2000 20:32:49 -0400 (EDT)
Received: from Software.com ([207.175.94.192]) by mta1biz.bizmailsrvcs.net
          with ESMTP
          id <20000712003318.HIMG459995.mta1biz.bizmailsrvcs.net@Software.com>
          for <ietf@ietf.org>; Tue, 11 Jul 2000 19:33:18 -0500
Sender: droyer
Message-ID: <396BAC0A.77994332@Software.com>
Date: Tue, 11 Jul 2000 16:21:46 -0700
From: Doug Royer <Doug.Royer@Software.com>
Reply-To: ietf@ietf.org
Organization: Software.com
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Is WAP mobile Internet??
References: <6ADD5A0DF6B1D31193430090279A2A08E45044@mail.telestet.gr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> TSIGARIDAS PANAGIOTIS wrote:
> 
> I believe, I found part of the following text in WAP Forum's WEB-pages.
> However, I think the answer -from business and technology point of view-
> is simple;
> 
> Is WAP mobile Internet ?  Yes and NO
> 
> WAP is using existing Internet standards.  The WAP architecture was
> designed to enable standard Internet servers to provide services to
> wireless devices.

In other words - a gateway?

If so, then it is a gateway to non-internet devices.
They are not just disconnected devices. Many people have laptops
that are connected then disconnected from an ISP. The mobile
phones use a different protocol suite to perform their operations.

I am not saying that is bad. Just that it seems to me to they are
saying that they are providing a gateway to the internet for non-internet
devices. Otherwise is all they would need is a bridge or router.

>  In addition, when communicating with wireless devices,
> WAP uses many Internet standards such as XML, UDP and IP. The WAP
> wireless protocols are based on Internet standards such as HTTP and TLS
> but have been optimised for the unique constraints of the wireless
> environment.

And much email is still sent in ASCII (IEEE I think), that does mean
that all internet email systems are IEEE devices.

> Internet standards such as HTML, HTTP, TLS and TCP are inefficient over
> mobile networks, requiring:
> ...

Orthogonal to the issue here - "is it the internet"?



From owner-ietf-outbound  Tue Jul 11 21:21:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA24697
	for ietf-outbound.10@ietf.org; Tue, 11 Jul 2000 21:20:02 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24647
	for <ietf@ietf.org>; Tue, 11 Jul 2000 21:12:20 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id SAA03427;
	Tue, 11 Jul 2000 18:12:21 -0700 (PDT)
Date: Tue, 11 Jul 2000 18:12:21 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200007120112.SAA03427@shell5.ba.best.com>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Mime-Version: 1.0
X-Loop: ietf@ietf.org

Jon:

> personal comment
> Other classes of organisation may simply be providing a subset of
> internet services - I don't see a market or technical case for these
> and in fact would encourage regulatory bodies to see if these types of
> organisations are trying to achieve lock out or are engaged in
> other types of monopolistic or anti-competitive behaviour. :-)

If I'm understanding you correctly, there is clearly a market for such
organizations, otherwise they would not exist.  Whether or not there
is technical justification for what they do is a matter of opinion.
For reasons that have been beaten to death here and elsewhere, they
provide some function that is not met with the existing IPv4 service.

I could make the argument that they provide Internet access, in the
sense that one can use these providers to gain access to a subset of
content and services that is "traditionally" called Internet service.
I would support them being classified as Internet Access Providers
(IAPs).  In some circles, that's what they're called.

Masataka:

> I just want to make it illegal for these types of organisations call
> their service "Internet" or "internet".

> It's something like "Olympic".

How would you go about doing that?  What judicial organization is likely
to make an issue of this, in light of all the other (arguably more serious)
issues on their plates?

--gregbo



From owner-ietf-outbound  Wed Jul 12 18:31:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA17189
	for ietf-outbound.10@ietf.org; Wed, 12 Jul 2000 18:30:04 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17107
	for <ietf@ietf.org>; Wed, 12 Jul 2000 18:24:17 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007122216.HAA27122@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id HAA27122; Thu, 13 Jul 2000 07:16:36 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <200007120112.SAA03427@shell5.ba.best.com> from Greg Skinner at
 "Jul 11, 2000 06:12:21 pm"
To: Greg Skinner <gds@best.com>
Date: Thu, 13 Jul 2000 07:16:35 +0859 ()
CC: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Greg;

> I could make the argument that they provide Internet access, in the
> sense that one can use these providers to gain access to a subset of
> content and services that is "traditionally" called Internet service.
> I would support them being classified as Internet Access Providers
> (IAPs).  In some circles, that's what they're called.

Your points are taken that you can call them WASP (Web Access Service
Providers).


							Masakaka Ohta



From owner-ietf-outbound  Wed Jul 12 18:50:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA17613
	for ietf-outbound.10@ietf.org; Wed, 12 Jul 2000 18:50:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17470
	for <ietf@ietf.org>; Wed, 12 Jul 2000 18:44:34 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007122233.HAA27697@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id HAA27697; Thu, 13 Jul 2000 07:33:17 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <010301bfeb2a$2ed8d7e0$268939cc@ntdev.microsoft.com> from "aboba@internaut.com"
 at "Jul 11, 2000 04:21:38 am"
To: aboba@internaut.com
Date: Thu, 13 Jul 2000 07:33:16 +0859 ()
CC: =?us-ascii?Q?=3D=3Fus=2Dascii=3FQ=3F=27Patrik=5FFaltstrom=27=3F?= =?us-ascii?Q?=3D?=
 <paf@cisco.com>,
        "'Randy Bush'" <randy@psg.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Aboba;

> >I don't see any problems people making money 
> >on weird NAT-munging-weirdo-webonly-wap things 
> >which they sell to customers
> 
> "Making money" implies that for every seller
> there is a willing buyer. For NAT to have
> progressed from a twinkle-in-the-eye to the
> near ubiquity that it will have in a few
> years, there need to be a *lot* of willing
> buyers. The marketplace rewards those who
> satisfy a perceived need. 
> 
> If we would prefer that those customers
> choose another solution (IPv6), then we
> will need to make it every bit as easy 
> to install and use as the alternative. 

See draft-ohta-address-allocation-00.txt on how to commercially motivate
ISPs (and private IP network providers with NAT, too) deploy IPv6 service.

It also makes NAT unnecessary.

> I'm not sure that in practice this is a
> distinction that will ever be universally
> understood in the marketplace. AOL isn't
> Internet access either, but it serves
> more than 25 million users. As with
> NAT, AOL thrives because it fills a
> perceived need better than the alternative.

If IETF makes it clear that AOL is not an ISP, it will commercially
motivate AOL to be an ISP.

						Masataka Ohta



From owner-ietf-outbound  Wed Jul 12 19:51:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA18389
	for ietf-outbound.10@ietf.org; Wed, 12 Jul 2000 19:50:02 -0400 (EDT)
Received: from smtp.mail.yahoo.com (smtp.mail.yahoo.com [128.11.68.32])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA18320
	for <ietf@ietf.org>; Wed, 12 Jul 2000 19:40:57 -0400 (EDT)
Received: from 53dial22.poly.edu (HELO computer) (128.238.4.102)
  by smtp.mail.yahoo.com with SMTP; 12 Jul 2000 22:58:30 -0000
X-Apparently-From: <jty202@yahoo.com>
Message-ID: <000801bfec54$f7b05640$6604ee80@computer>
From: "jty202Yahoo" <jty202@yahoo.com>
To: <ietf@ietf.org>
References: <38E2E8DA.A71CBABB@kasey.umkc.edu>
Subject: Re: HTML forms
Date: Wed, 12 Jul 2000 18:13:42 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0003_01BFEC2C.E9696D60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

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

Need info. on programming voice over ip.  Appeciate any detail =
assistance.  Thanks.

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#b5d2f2>
<DIV><FONT face=3DArial size=3D2>Need info. on programming voice over =
ip.&nbsp;=20
Appeciate any detail assistance.&nbsp; =
Thanks.</FONT></DIV></BODY></HTML>

------=_NextPart_000_0003_01BFEC2C.E9696D60--


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com



From owner-ietf-outbound  Wed Jul 12 21:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA19920
	for ietf-outbound.10@ietf.org; Wed, 12 Jul 2000 21:30:02 -0400 (EDT)
Received: from rgate2.ricochet.net (rgate2.ricochet.net [204.179.143.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19876
	for <ietf@ietf.org>; Wed, 12 Jul 2000 21:26:50 -0400 (EDT)
Received: from mobile (mg137-021.ricochet.net [204.179.137.21])
	by rgate2.ricochet.net (8.9.3/8.9.3) with ESMTP id UAA26789
	for <ietf@ietf.org>; Wed, 12 Jul 2000 20:26:25 -0500 (CDT)
Message-Id: <4.2.0.58.20000712182547.00949b20@limbo.net>
X-Sender: rodney@limbo.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Wed, 12 Jul 2000 18:26:31 -0700
To: ietf@ietf.org
From: Rodney Thayer <rodney@TILLERMAN.TO>
Subject: agenda for Pittsburgh?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Where's the agenda for Pittsburgh?  I didn't see it on the
IETF web site, or in the FTP directory, or announced on any
lists.




From owner-ietf-outbound  Wed Jul 12 22:50:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA23168
	for ietf-outbound.10@ietf.org; Wed, 12 Jul 2000 22:50:01 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22831
	for <ietf@ietf.org>; Wed, 12 Jul 2000 22:40:32 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id WAA27021;
        Wed, 12 Jul 2000 22:39:01 -0400 (EDT)
Message-Id: <200007130239.WAA27021@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
cc: aboba@internaut.com,
        =?us-ascii?Q?=3D=3Fus=2Dascii=3FQ=3F=27Patrik=5FFaltstrom=27=3F?= =?us-ascii?Q?=3D?= <paf@cisco.com>,
        "'Randy Bush'" <randy@psg.com>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Thu, 13 Jul 2000 07:33:16 +0859."
             <200007122233.HAA27697@necom830.hpcl.titech.ac.jp> 
Date: Wed, 12 Jul 2000 22:39:01 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> If IETF makes it clear that AOL is not an ISP, it will commercially
> motivate AOL to be an ISP.

probably not.  folks who subscribe to AOL aren't likely to be 
reading IETF documents.

face it, it's not the superior quality of AOL's service that keeps 
AOLers from moving - it's their susceptibility to marketing BS and
their addiction to chat rooms.  it's hard to help those people.

Keith



From owner-ietf-outbound  Wed Jul 12 23:00:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA23285
	for ietf-outbound.10@ietf.org; Wed, 12 Jul 2000 23:00:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23062
	for <ietf@ietf.org>; Wed, 12 Jul 2000 22:47:21 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id WAA27208;
        Wed, 12 Jul 2000 22:47:23 -0400 (EDT)
Message-Id: <200007130247.WAA27208@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
X-PGP-Key: 2F07A741 ; 78 15 8E 8B C0 06 5D D1  BC 08 05 7F 42 81 7E 90 
To: ietf@ietf.org
Subject: belated apology
cc: moore@cs.utk.edu
From: Keith Moore <moore@cs.utk.edu>
Date: Wed, 12 Jul 2000 22:47:23 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

I'd like to publically apologize to Randy Bush for the tone of my 
response to his message from earlier this week.

Randy was quite correct to point out that any terms that IETF might
develop to describe ISPs might not be consistent with any particular
provider's offerings.  And though I have heard far too many attempts
to use "business models" to justify technical brain-damage and worse,
it was indeed a leap on my part to assume that Randy was referring 
to that type of business model. 

Keith

p.s. I do however think that, given the tendency of various providers 
these days to violate the internet protocol specifications and
erode the ability of applications to run on the network,  the 
community might benefit from some kind of "standardized" (in the
loose sense) description of IP service (rather than ISPs) that could be 
specified by customers.  and IETF would appear to be the organization 
which is best suited to define such terms.



From owner-ietf-outbound  Wed Jul 12 23:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA23440
	for ietf-outbound.10@ietf.org; Wed, 12 Jul 2000 23:10:03 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23412
	for <ietf@ietf.org>; Wed, 12 Jul 2000 23:07:05 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.11.0.Beta3/calcite) id e6D376V14029
	for ietf@ietf.org  env-from <vjs>;
	Wed, 12 Jul 2000 21:07:06 -0600 (MDT)
Date: Wed, 12 Jul 2000 21:07:06 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007130307.e6D376V14029@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
X-Loop: ietf@ietf.org

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

> ...
> face it, it's not the superior quality of AOL's service that keeps 
> AOLers from moving - it's their susceptibility to marketing BS and
> their addiction to chat rooms.  it's hard to help those people.

Other than latency, message size, message rate, and the number of
participants, what is the difference between an AOL chat room and this
mailing list as exemplified by this thread?

I don't intend to imply anything bad about this thread or suggest any of
the participants do or stop doing anything.  I've never subscribed to AOL,
never used an AOL chat room, and the closest I've come to something like
IIRC is the BSD UNIX `talk` and `write` commands and SDS-940 predecessors
in the 1960's.  However, I don't think that confers any virtue, and I hope
it doesn't blind me to all of the similarities between pots and kettles.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu Jul 13 00:10:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA24461
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 00:10:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24295
	for <ietf@ietf.org>; Thu, 13 Jul 2000 00:00:44 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id AAA28857;
        Thu, 13 Jul 2000 00:00:40 -0400 (EDT)
Message-Id: <200007130400.AAA28857@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Wed, 12 Jul 2000 21:07:06 MDT."
             <200007130307.e6D376V14029@calcite.rhyolite.com> 
Date: Thu, 13 Jul 2000 00:00:40 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Other than latency, message size, message rate, and the number of
> participants, what is the difference between an AOL chat room and this
> mailing list as exemplified by this thread?

why, the participants, of course.

once people move into chat rooms and make acquaintances there, they
become reluctant to leave.  if changing service providers means they 
must leave, they're less likely to change service providers even
though they get lousy service.

I suspect the "reluctance to leave" is no less true for mailing lists.  
but IETF mailing lists don't require you to use any particular ISP.

still, my point was that the AOL community is more-or-less disjoint
from the community of folks who read IETF documents, and is likely
to remain so.  that's not necessarily a bad thing overall, but it
does imply that IETF will have little effect on the decision-making
habits of AOL subscribers.  if AOL subscribers cared about standards
compliance they would have left AOL long ago.

Keith



From owner-ietf-outbound  Thu Jul 13 03:01:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA09082
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 03:00:02 -0400 (EDT)
Received: from roam.psg.com (ppp246-as10.lsanca.ni.net [209.189.118.246])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09029
	for <ietf@ietf.org>; Thu, 13 Jul 2000 02:57:44 -0400 (EDT)
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 13CcwO-0000Xw-00; Wed, 12 Jul 2000 23:57:48 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: Re: belated apology
References: <200007130247.WAA27208@astro.cs.utk.edu>
Message-Id: <E13CcwO-0000Xw-00@roam.psg.com>
Date: Wed, 12 Jul 2000 23:57:48 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

jeezus!  no need.  i can take it as well as dish it.  but thanks, i hear
you.

randy



From owner-ietf-outbound  Thu Jul 13 03:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA09609
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 03:50:03 -0400 (EDT)
Received: from euronet.be (caolila.euronet.be [195.74.193.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09514
	for <ietf@ietf.org>; Thu, 13 Jul 2000 03:40:39 -0400 (EDT)
Received: from atlas.adtech.be (i0218.bfp-s.euronet.be [212.65.48.218])
	by euronet.be (8.9.3/8.9.3) with ESMTP id JAA05618
	for <ietf@ietf.org>; Thu, 13 Jul 2000 09:40:37 +0200 (MET DST)
Received: by ATLAS with Internet Mail Service (5.5.2650.21)
	id <NJRZ5Z1J>; Thu, 13 Jul 2000 09:40:38 +0200
Message-ID: <C1A484FD220AD211963900805F8B49FF2A5062@ATLAS>
From: Michael Stilmant <michael.stilmant@adtech.be>
To: ietf@ietf.org
Subject: RE: HTML forms
Date: Thu, 13 Jul 2000 09:40:28 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFEC9D.A2A0AA60"
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFEC9D.A2A0AA60
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,
    there are the http://www.openh323.org <http://www.openh323.org>  for
open sources on H323
    for SIP you can check http://www.vovida.com <http://www.vovida.com>  who
provide some source for help programming Voip
 
http://www.tsufl.edu/williams/Projects/InternetPhone/TSCIS445.htm
<http://www.tsufl.edu/williams/Projects/InternetPhone/TSCIS445.htm> 
http://www.cis.ohio-state.edu/~jain/refs/ref_voip.htm
<http://www.cis.ohio-state.edu/~jain/refs/ref_voip.htm> 
http://www.cs.columbia.edu/sip/ <http://www.cs.columbia.edu/sip/> 
http://www.fokus.gmd.de/research/cc/glone/projects/ipt/
<http://www.fokus.gmd.de/research/cc/glone/projects/ipt/> 
 

-----Original Message-----
From: jty202Yahoo [mailto:jty202@yahoo.com]
Sent: jeudi 13 juillet 2000 00:14
To: ietf@ietf.org
Subject: Re: HTML forms


Need info. on programming voice over ip.  Appeciate any detail assistance.
Thanks.


------_=_NextPart_001_01BFEC9D.A2A0AA60
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#b5d2f2>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D893592107-13072000>Hi,</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D893592107-13072000>&nbsp;&nbsp;&nbsp; there are the <A=20
href=3D"http://www.openh323.org">http://www.openh323.org</A>&nbsp;for =
open sources=20
on H323</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D893592107-13072000>&nbsp;&nbsp;&nbsp; for SIP you can check <A=20
href=3D"http://www.vovida.com">http://www.vovida.com</A>&nbsp;who =
provide some=20
source for help programming Voip</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D893592107-13072000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D893592107-13072000><A=20
href=3D"http://www.tsufl.edu/williams/Projects/InternetPhone/TSCIS445.ht=
m">http://www.tsufl.edu/williams/Projects/InternetPhone/TSCIS445.htm</A>=
</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D893592107-13072000><A=20
href=3D"http://www.cis.ohio-state.edu/~jain/refs/ref_voip.htm">http://ww=
w.cis.ohio-state.edu/~jain/refs/ref_voip.htm</A></SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D893592107-13072000><A=20
href=3D"http://www.cs.columbia.edu/sip/">http://www.cs.columbia.edu/sip/=
</A></SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D893592107-13072000><A=20
href=3D"http://www.fokus.gmd.de/research/cc/glone/projects/ipt/">http://=
www.fokus.gmd.de/research/cc/glone/projects/ipt/</A></SPAN></FONT></DIV>=

<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D893592107-13072000></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> jty202Yahoo=20
  [mailto:jty202@yahoo.com]<BR><B>Sent:</B> jeudi 13 juillet 2000=20
  00:14<BR><B>To:</B> ietf@ietf.org<BR><B>Subject:</B> Re: HTML=20
  forms<BR><BR></DIV></FONT>
  <DIV><FONT face=3DArial size=3D2>Need info. on programming voice over =
ip.&nbsp;=20
  Appeciate any detail assistance.&nbsp;=20
Thanks.</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01BFEC9D.A2A0AA60--



From owner-ietf-outbound  Thu Jul 13 10:20:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA20366
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 10:20:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19946
	for <ietf@ietf.org>; Thu, 13 Jul 2000 10:10:42 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id KAA12560;
	Thu, 13 Jul 2000 10:10:06 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: <moore@cs.utk.edu>, <ietf@ietf.org>
Subject: RE: IP service definition
Date: Thu, 13 Jul 2000 10:10:03 -0400
Message-ID: <006d01bfecd4$0ad64660$d001010a@tst.ennovatenetworks.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)
In-Reply-To: <200007130247.WAA27208@astro.cs.utk.edu>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


> -----Original Message-----
> From: moore@cs.utk.edu [mailto:moore@cs.utk.edu]
> Sent: Wednesday, July 12, 2000 10:47 PM
> I do however think that, given the tendency of various providers
> these days to violate the internet protocol specifications and
> erode the ability of applications to run on the network,  the
> community might benefit from some kind of "standardized" (in the
> loose sense) description of IP service (rather than ISPs)
> that could be
> specified by customers.  and IETF would appear to be the
organization
> which is best suited to define such terms.

Keith,

It is akin to standardizing on what kind of light can come in your
neighbourhood. The vast majority of consumers care for applications,
not the transport that provides those services. This is why AOL can
have 25 million subscribers even though most technical people seem to
think very lowly of AOL (you can use only aol mail tool and nothing
else). As a technical person, you may not like their solution, but
they appear to meet requirements of their target market. The same
thing is true with WAP solutions on PDAs.

Standards, no matter who creates them and with what intensions, can't
be forced on either carriers or consumers. You can achieve better
results by supporting networks and solutions that are in line with
what you call "standardized IP", and clearly laying out benefits of
doing so for the rest of the world. If  "non-compliant" networks start
losing customers, they will see merits in transforming their
solutions.

Cheers,

--brijesh
Ennovate Networks Inc.



From owner-ietf-outbound  Thu Jul 13 10:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA21929
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 10:50:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21020
	for <ietf@ietf.org>; Thu, 13 Jul 2000 10:33:27 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id KAA13428;
	Thu, 13 Jul 2000 10:30:58 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: "'Masataka Ohta'" <mohta@necom830.hpcl.titech.ac.jp>,
        <aboba@internaut.com>
Cc: "'=?us-ascii?Q?'Patrik_Faltstrom'?='" <paf@CISCO.COM>,
        "'Randy Bush'" <randy@psg.com>, <ietf@ietf.org>
Subject: RE: draft-ietf-nat-protocol-complications-02.txt
Date: Thu, 13 Jul 2000 10:30:55 -0400
Message-ID: <000c01bfecd6$f47aaca0$d001010a@tst.ennovatenetworks.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)
In-Reply-To: <200007122233.HAA27697@necom830.hpcl.titech.ac.jp>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



> -----Original Message-----
> From: Masataka Ohta [mailto:mohta@necom830.hpcl.titech.ac.jp]
> 
> 
> If IETF makes it clear that AOL is not an ISP, it will commercially
> motivate AOL to be an ISP.

Oh really - it is that simple! 
Guess who is better known in masses - IETF or AOL :-).

Cheers,

--brijesh
Ennovate Networks Inc. 



From owner-ietf-outbound  Thu Jul 13 11:10:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA23092
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 11:10:02 -0400 (EDT)
Received: from apollo.dmnews.com (gw.dmnews.com [204.141.161.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22744
	for <ietf@ietf.org>; Thu, 13 Jul 2000 11:04:23 -0400 (EDT)
Received: by APOLLO with Internet Mail Service (5.5.2650.10)
	id <M8X8KNG8>; Thu, 13 Jul 2000 11:12:21 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE3023DE@APOLLO>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Browser - XML question and a little praise
Date: Thu, 13 Jul 2000 11:12:21 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

First of all let me tell you how much I am not only enjoying being the part
(if mainy listening part) of this list but also what a great learning
experience it is. (More than one way of course...)

Question: I am looking into implementing XML. For that I will have to look
into the browser compatibility issues for IE, NS and Opera. Also the
different kind of parsers or parsing capabilities, which will probably
mainly be in Perl. Any link to related information would be very useful.

Thanks all for your help,

Lillian Komlossy


Lillian Komlossy || Site Manager || http://www.dmnews.com ||
http://www.imarketingnews.com || 212 925-7300 ext. 232 ||
mailto:lillian@dmnews.com



From owner-ietf-outbound  Thu Jul 13 11:50:46 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA25195
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 11:50:01 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24764
	for <ietf@ietf.org>; Thu, 13 Jul 2000 11:41:54 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.11.0.Beta3/calcite) id e6DFftK01042
	for ietf@ietf.org  env-from <vjs>;
	Thu, 13 Jul 2000 09:41:55 -0600 (MDT)
Date: Thu, 13 Jul 2000 09:41:55 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007131541.e6DFftK01042@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
X-Loop: ietf@ietf.org

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

> ...
> > Other than latency, message size, message rate, and the number of
> > participants, what is the difference between an AOL chat room and this
> > mailing list as exemplified by this thread?
>
> why, the participants, of course.
>
> once people move into chat rooms and make acquaintances there, they
> become reluctant to leave.  if changing service providers means they 
> must leave, they're less likely to change service providers even
> though they get lousy service.

It sounded as if you were making the standard swipe at people who use
AOL.  If you had been, my rejoinder would have been to quote the first
vacation message I got in response to my note.

However, I've suddenly realized that the fault for some of the vacation
messages rests with the people running this list.  Notice that they
are not including a "Precedence: bulk" or "Precedence: bulk" lines
which tell at least some `vacation` programs to do the obvious.  They
do include "X-Loop: ietf@ietf.org"

In other words, the IETF itself is not above some standads bending..


> ...
> still, my point was that the AOL community is more-or-less disjoint
> from the community of folks who read IETF documents, and is likely
> to remain so.  that's not necessarily a bad thing overall, but it
> does imply that IETF will have little effect on the decision-making
> habits of AOL subscribers.  

yes.

>                             if AOL subscribers cared about standards
> compliance they would have left AOL long ago.

You're wrong about that.  Remember when AOL didn't have anything to do
with the Internet?  That the standards for some of the services that AOL
sells are written and published by AOL instead of the IETF, ITU, ANSI, or
IEEE doesn't make them any less interesting to those buying those services.
In other words, if the IETF were to suddenly and not upwardly compatibly
change the spelling of "Rctp To" in "To Rcpt" in SMTP and if AOL were to
make a similar change in their services, which change would generate more
enraged phone calls?

Note that I think AOL ought to be sued for false advertising because
of the SMTP redirection proxies it interposes in the services that it
does claim have something to do with the Internet.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu Jul 13 12:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA25615
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 12:00:03 -0400 (EDT)
Received: from ckmso1.proxy.att.com (ckmso1.att.com [12.20.58.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25131
	for <ietf@ietf.org>; Thu, 13 Jul 2000 11:49:32 -0400 (EDT)
Received: from njb140r1.ems.att.com ([135.65.202.58])
	by ckmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id LAA24194
	for <ietf@ietf.org>; Thu, 13 Jul 2000 11:49:02 -0400 (EDT)
Received: from njb140bh2.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2)
	id LAA03275; Thu, 13 Jul 2000 11:47:52 -0400 (EDT)
Received: by njb140bh2.ems.att.com with Internet Mail Service (5.5.2650.21)
	id <3NACXLKX>; Thu, 13 Jul 2000 11:49:00 -0400
Message-ID: <1F035F2B8F59D31185840000C06803000412D9A2@njb140po08.ems.att.com>
From: "Gayen, Sanjukta, CMDR" <gayen@att.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: SNMP, CORBA and XML
Date: Thu, 13 Jul 2000 11:48:57 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org



I am trying to understand the application and advantages of multiple
protocols like SNMP, CORBA and XML. I will appreciate a lot if any one can
help me to understand which protocol to choose under what circumstances.  I
am coming across few systems which supports all three interfaces. Can only
one protocol do the job ?

Thanks very much in advance.
Sanjukta Gayen



From owner-ietf-outbound  Thu Jul 13 12:10:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA26177
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 12:10:01 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25149
	for <ietf@ietf.org>; Thu, 13 Jul 2000 11:49:38 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id LAA09613
	for <ietf@ietf.org>; Thu, 13 Jul 2000 11:49:58 -0400
Sender: francis@localhost.localdomain
Message-ID: <396DE524.87668937@ecal.com>
Date: Thu, 13 Jul 2000 11:49:56 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IP service definition
References: <006d01bfecd4$0ad64660$d001010a@tst.ennovatenetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Brijesh Kumar wrote:

> As a technical person, you may not like their solution, but
> they appear to meet requirements of their target market.

Emphasis on "appear".  The non-ISPs provide services that appear to be
Internet access, but aren't.  The big problem is when new protocols come
along that permit new functionality, but can't reach the non-ISPs'
users.  This hurts developers, of course, because it limits our user
base; but it also hurts the non-ISPs' users (obviously) *and* all other
users (by Metcalfe's Law).

--
/=================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.   |
|Chief Scientist |================================================|
|eCal Corp.      |"Where's your sense of adventure?" "Hiding under|
|francis@ecal.com|the bed."                                       |
\=================================================================/





From owner-ietf-outbound  Thu Jul 13 12:20:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA26691
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 12:20:05 -0400 (EDT)
Received: from mail.xybridge.com (IDENT:root@[209.111.160.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26025
	for <ietf@ietf.org>; Thu, 13 Jul 2000 12:08:07 -0400 (EDT)
Received: from yixin ([10.10.13.107])
	by mail.xybridge.com (8.9.3/8.9.3) with SMTP id KAA03407;
	Thu, 13 Jul 2000 10:22:33 -0500
From: "Yixin Zhu" <yixin@xybridge.com>
To: "Gayen, Sanjukta, CMDR" <gayen@att.com>, <ietf@ietf.org>
Subject: RE: SNMP, CORBA and XML
Date: Thu, 13 Jul 2000 11:08:54 -0500
Message-ID: <NDBBIFGHKLHKNCMEKGHAKEFCCCAA.yixin@xybridge.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 IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <1F035F2B8F59D31185840000C06803000412D9A2@njb140po08.ems.att.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

In addition, I am also interested in the differences bwteen SNMP and JMX.
Thanks.


Yixin Zhu

-----Original Message-----
From: Gayen, Sanjukta, CMDR [mailto:gayen@att.com]
Sent: Thursday, July 13, 2000 10:49 AM
To: 'ietf@ietf.org'
Subject: SNMP, CORBA and XML




I am trying to understand the application and advantages of multiple
protocols like SNMP, CORBA and XML. I will appreciate a lot if any one can
help me to understand which protocol to choose under what circumstances.  I
am coming across few systems which supports all three interfaces. Can only
one protocol do the job ?

Thanks very much in advance.
Sanjukta Gayen



From owner-ietf-outbound  Thu Jul 13 12:50:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA28334
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 12:50:03 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27929
	for <ietf@ietf.org>; Thu, 13 Jul 2000 12:42:29 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 13Cm47-0004xN-00; Thu, 13 Jul 2000 17:42:23 +0100
Date: Thu, 13 Jul 2000 17:42:19 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: John Stracke <francis@ecal.com>
cc: ietf@ietf.org
Subject: Re: IP service definition
In-Reply-To: <396DE524.87668937@ecal.com>
Message-ID: <Pine.GSO.4.21.0007131739370.29318-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Thu, 13 Jul 2000, John Stracke wrote:

> Brijesh Kumar wrote:
> 
> > As a technical person, you may not like their solution, but
> > they appear to meet requirements of their target market.
> 
> Emphasis on "appear".  The non-ISPs provide services that appear to be
> Internet access, but aren't.  The big problem is when new protocols come
> along that permit new functionality, but can't reach the non-ISPs'
> users.  This hurts developers, of course, because it limits our user
> base; but it also hurts the non-ISPs' users (obviously) *and* all other
> users (by Metcalfe's Law).

...but benefits the non-ISPs, who can charge for selectively
introducing any new service (even if it's e.g. by opening a port in
their firewall.)

The telco mindset has never really gone away. No wonder there's so
much emphasis on e.g. tunnelling everything on top of http...

L.

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



From owner-ietf-outbound  Thu Jul 13 13:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA28995
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 13:00:02 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28741
	for <ietf@ietf.org>; Thu, 13 Jul 2000 12:56:38 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id MAA10271
	for <ietf@ietf.org>; Thu, 13 Jul 2000 12:56:56 -0400
Sender: francis@localhost.localdomain
Message-ID: <396DF4D8.5D937651@ecal.com>
Date: Thu, 13 Jul 2000 12:56:56 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IP service definition
References: <Pine.GSO.4.21.0007131739370.29318-100000@petra.ee.surrey.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Lloyd Wood wrote:

> > users.  This hurts developers, of course, because it limits our user
> > base; but it also hurts the non-ISPs' users (obviously) *and* all other
> > users (by Metcalfe's Law).
>
> ...but benefits the non-ISPs, who can charge for selectively
> introducing any new service (even if it's e.g. by opening a port in
> their firewall.)

Only if they take the narrow view.  In the long run, by putting up the walled
garden, the non-ISP reduces the number of potential users for any new
service, which makes it less likely for that service to get enough momentum
to be accepted.  And, of course, any new, popular Internet service is
valuable to all ISPs, since it increases the value of their service.

--
/=================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.   |
|Chief Scientist |================================================|
|eCal Corp.      |It's not an optical illusion, it just looks like|
|francis@ecal.com|one.                                            |
\=================================================================/





From owner-ietf-outbound  Thu Jul 13 13:20:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA00388
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 13:20:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29913
	for <ietf@ietf.org>; Thu, 13 Jul 2000 13:12:26 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA05974;
        Thu, 13 Jul 2000 13:12:24 -0400 (EDT)
Message-Id: <200007131712.NAA05974@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: precedence field and mailing lists 
In-reply-to: Your message of "Thu, 13 Jul 2000 09:41:55 MDT."
             <200007131541.e6DFftK01042@calcite.rhyolite.com> 
Date: Thu, 13 Jul 2000 13:12:23 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> However, I've suddenly realized that the fault for some of the vacation
> messages rests with the people running this list.  Notice that they
> are not including a "Precedence: bulk" or "Precedence: bulk" lines
> which tell at least some `vacation` programs to do the obvious.  

nor should they.  Precedence is not a standard header field, and it's
used in so many different ways by different pieces of software
(to do everything from setting queueing priority to telling peered
mailing lists not to forward the message) that it's better to omit it.

> In other words, the IETF itself is not above some standads bending..

what standard are you referring to?

Keith



From owner-ietf-outbound  Thu Jul 13 13:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA01009
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 13:30:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00197
	for <ietf@ietf.org>; Thu, 13 Jul 2000 13:16:50 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA06084;
        Thu, 13 Jul 2000 13:16:48 -0400 (EDT)
Message-Id: <200007131716.NAA06084@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: AOL and standards
In-reply-to: Your message of "Thu, 13 Jul 2000 09:41:55 MDT."
             <200007131541.e6DFftK01042@calcite.rhyolite.com> 
Date: Thu, 13 Jul 2000 13:16:42 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> 
> >                             if AOL subscribers cared about standards
> > compliance they would have left AOL long ago.
> 
> You're wrong about that.  Remember when AOL didn't have anything to do
> with the Internet?  That the standards for some of the services that AOL
> sells are written and published by AOL instead of the IETF, ITU, ANSI, or
> IEEE doesn't make them any less interesting to those buying those services.

nothing that AOL does on its own is standard.  to use the term "standard"
in that way is to make the term meaningless.

the people who I'm receiving mail from are not complaining about AOL not 
following its own "standards"; they're complaining about AOL's failure
to interoperate with Internet Mail.  and rightfully so.

> Note that I think AOL ought to be sued for false advertising because
> of the SMTP redirection proxies it interposes in the services that it
> does claim have something to do with the Internet.

that's just one item in a long list.

Keith



From owner-ietf-outbound  Thu Jul 13 14:30:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA04307
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 14:30:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04218
	for <ietf@ietf.org>; Thu, 13 Jul 2000 14:27:24 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.11.0.Beta3/calcite) id e6DIRO904849
	for ietf@ietf.org  env-from <vjs>;
	Thu, 13 Jul 2000 12:27:24 -0600 (MDT)
Date: Thu, 13 Jul 2000 12:27:24 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007131827.e6DIRO904849@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: precedence field and mailing lists
Precedence: bulk
X-Loop: ietf@ietf.org

I've recombined these because they have an important connection, the
notion that the pronouncements of ITU, ANSI, IEEE, ATM Forum, the WAP
consortium, and the IETF are somehow necessarily better than those of any
other arbitrary group of people.


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

> > However, I've suddenly realized that the fault for some of the vacation
> > messages rests with the people running this list.  Notice that they
> > are not including a "Precedence: bulk" or "Precedence: bulk" lines
> > which tell at least some `vacation` programs to do the obvious.  
>
> nor should they.  Precedence is not a standard header field, and it's
> used in so many different ways by different pieces of software
> (to do everything from setting queueing priority to telling peered
> mailing lists not to forward the message) that it's better to omit it.

None of those sound like bad things for IETF lists, except when
intentionally overridden by people running their own software.

Despite IETF snobbery, Precedence: has decades of use.  It has defects as
a vacation program tamer, but those would be better fixed by coming up
with a replacement than by ignoring the problem.  IETF effort on that
would be better spent than on some (but not all) of the newest SMTP
elaborations.


> > In other words, the IETF itself is not above some standads bending..
>
> what standard are you referring to?

How about hoping that X-Loop will be preserved by those peered mailing
lists and other gateways and so prevent loops?

(I'm adding a Precedence: bulk to this to see what the IETF reflector
does with it.)


    ....

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

] nothing that AOL does on its own is standard.  to use the term "standard"
] in that way is to make the term meaningless.
> ...

In ancient days, there was a group of people, probably smaller than the
group now at AOL designing and implementing their protocols, who came up
with some protocols.  Those old protocols were explicitly ad hoc or at
least unofficial.  They were documented with informal and semi-formal
documents that really asked for comments, unlike any "real" standard,
including those from the IETF.  After more than a dozen years of guerilla
war, those de facto protocols clobbered the official, de jure protocols.
As usually happens, as they won the revolution, many of the revolutionaries
moved into the deposed overlords' offices and accepted fealty from the
toadies, go-ers, empire builders, and courtiers of the old regime, and
things went back to normal.

My point is that in rational eyes, a blessing from the ITU in Switzerland
or the IESG is neither necessary nor always sufficent to make a standard.
A standard is what http://www.m-w.com/ says, "something established by
authority, custom, or general consent as a model or example."

I'd rather that AOL took outside comments on their standards, but they're
still standards, no more or less than the latest embrace-and-extend brain
fart incompletely described in RFC format from the Pacific Northwest.
AOL's standards are not non-proprietary, open, or sanctioned by the IETF,
but they're as much standards as the greats on which the IETF bases its
existence.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu Jul 13 15:30:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA06566
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 15:30:03 -0400 (EDT)
Received: from apollo.dmnews.com (gw.dmnews.com [204.141.161.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06397
	for <ietf@ietf.org>; Thu, 13 Jul 2000 15:24:01 -0400 (EDT)
Received: by APOLLO with Internet Mail Service (5.5.2650.10)
	id <M8X8KN8D>; Thu, 13 Jul 2000 15:31:59 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE3023E6@APOLLO>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Email Privacy eating software
Date: Thu, 13 Jul 2000 15:31:58 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

The following articles describe an email reading software Big Bro is
apparently already using. I think this is more than appropriate to start a
discussion about.

While it can be a powerful tool in the right hands, my three concerns about
this are:
	1. Privacy of course - just the same way you don't want somebody
reading your snail mail - for all intents and purposes email is not
different.
	2. Who oversees the agents in terms of - who are they going to go
after - bad guys, or maybe political opponents?
	3. How long before the software will collect 'other' information as
well - and sell -ah pardon me: "make it available" to "valuable third party
companies" ?

Make up your own mind, here are the links:
http://www.zdnet.com/zdnn/stories/news/0,4586,2601502,00.html
and
http://www.zdnet.com/zdnn/stories/comment/0,5859,2601960,00.html

Lillian Komlossy || Site Manager || http://www.dmnews.com ||
http://www.imarketingnews.com || 212 925-7300 ext. 232 ||
mailto:lillian@dmnews.com



From owner-ietf-outbound  Thu Jul 13 16:40:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA18787
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 16:40:02 -0400 (EDT)
Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17142
	for <ietf@ietf.org>; Thu, 13 Jul 2000 16:36:03 -0400 (EDT)
Received: from Software.com ([207.175.94.235]) by mta1biz.bizmailsrvcs.net
          with ESMTP
          id <20000713203634.JLWW459995.mta1biz.bizmailsrvcs.net@Software.com>
          for <ietf@ietf.org>; Thu, 13 Jul 2000 15:36:34 -0500
Sender: droyer
Message-ID: <396E1786.B44B1CD3@Software.com>
Date: Thu, 13 Jul 2000 12:24:54 -0700
From: Doug Royer <Doug.Royer@Software.com>
Reply-To: ietf@ietf.org
Organization: Software.com
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: precedence field and mailing lists
References: <200007131827.e6DIRO904849@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


> Despite IETF snobbery,  has decades of use.  It has defects as
> a vacation program tamer, but those would be better fixed by coming up
> with a replacement than by ignoring the problem.  IETF effort on that
> would be better spent than on some (but not all) of the newest SMTP
> elaborations.

Could you please point me at the standards (or otherwise) documents
that describe the semantics of 'Precedence:'?  It sounds interesting
but I just can't seem to find out what you mean or expect it to do.
And do you happen to know the name of the standards body that
approved that standard? Perhaps I can find it that way.

> > > In other words, the IETF itself is not above some standads bending..
> >
> > what standard are you referring to?
> 
> How about hoping that X-Loop will be preserved by those peered mailing
> lists and other gateways and so prevent loops?

FYI: X-<anything> is by definition - not standard header.

> ...
> My point is that in rational eyes, a blessing from the ITU in Switzerland
> or the IESG is neither necessary nor always sufficent to make a standard.
> A standard is what http://www.m-w.com/ says, "something established by
> authority, custom, or general consent as a model or example."
> ..

Something can be 'standard' and never used by anyone. Something can be
used by everyone and never a 'standard'. 

However the word 'standard' does not mean 'used by a bigger number of
people'.

> I'd rather that AOL took outside comments on their standards, but they're
> still standards.

Please point me at those standards. Or did you mean undocumented
protocols? Or did you mean documented and not public protocols?

> no more or less than the latest embrace-and-extend brain
> fart incompletely described in RFC format from the Pacific Northwest.
> AOL's standards are not non-proprietary, open, or sanctioned by the IETF,
> but they're as much standards as the greats on which the IETF bases its
> existence.

I think the standard definition of standard includes, approved,
reviewed, and publicly available.

-Doug



From owner-ietf-outbound  Thu Jul 13 17:50:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA16585
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 17:50:03 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14578
	for <ietf@ietf.org>; Thu, 13 Jul 2000 17:44:00 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.11.0.Beta3/calcite) id e6DLi2l08298
	for ietf@ietf.org  env-from <vjs>;
	Thu, 13 Jul 2000 15:44:02 -0600 (MDT)
Date: Thu, 13 Jul 2000 15:44:02 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007132144.e6DLi2l08298@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: precedence field and mailing lists
X-Loop: ietf@ietf.org

> From: Doug Royer <Doug.Royer@SOFTWARE.COM>

> ...
> Could you please point me at the standards (or otherwise) documents
> that describe the semantics of 'Precedence:'?  It sounds interesting
> but I just can't seem to find out what you mean or expect it to do.

`man vacation` on any modern BSD-like UNIX box should say something like:
   No message will be sent unless login (or an alias supplied using the -a
   option) is part of either the ``To:'' or ``Cc:'' headers of the mail.  No
   messages from ``???-REQUEST'', ``Postmaster'', ``UUCP'', ``MAILER'', or
   ``MAILER-DAEMON'' will be replied to (where these strings are case insen-
   sitive) nor is a notification sent if a ``Precedence: bulk'' or
   ``Precedence: junk'' line is included in the mail headers.  

Near the end you'll likely find something like:
   The vacation command appeared in 4.3BSD.
which the knowledgable translate into "official, open source publication
in 1985 or 1986, depending on access to the Beta tape."
Then there are the at least as ancient words in sendmail documenation.


> ...
> > > > In other words, the IETF itself is not above some standads bending..
> > > what standard are you referring to?
> > How about hoping that X-Loop will be preserved by those peered mailing
> > lists and other gateways and so prevent loops?
> 
> FYI: X-<anything> is by definition - not standard header.

While your words agree with my point, you say them as if you disagree.


> ...
> > A standard is what http://www.m-w.com/ says, "something established by
> > authority, custom, or general consent as a model or example."

> ...
> Something can be 'standard' and never used by anyone. Something can be
> used by everyone and never a 'standard'. 

Perhaps according to the Church of De Jure Standards.
Among those who disagree are dictionaries, heathens, apostates,
and others whose livelihoods or self-esteem don't require the
validation of what other standards bodies officially and revealingly
call "The Standards Process."

> ...
> > I'd rather that AOL took outside comments on their standards, but they're
> > still standards.
>
> Please point me at those standards. Or did you mean undocumented
> protocols? Or did you mean documented and not public protocols?

I mean AOL's protocols, applications, and other computer stuff which meet
the definition of "standard" in http://www.m-w.com/ by being "established
by authority, custom, or general consent as a model or example." 
The consent and custom of 23,000,000 people and the authority of AOL meet
all three of those dictionary requirements.  They don't and should not
meet modern IETF requirements for standards track RFCs, but I suspect that
if (perhaps a big 'if') they met technical muster, they would have been
accepted 18 or 20 years ago by the ad hoc group that preceded the IETF.

Which gets me back to the Precedence: header.  That some people dislike
it, many more are ignorant of it, and it has more than one use does not
imply that the IESG should not be using it as the best and only available
fix to a real problem.  That the Precedence: header meets the dictionary
definition of "standard" is gravy, except for the awkwardness of the IETF
admitting that the IETF is not the font of all wisdom.  Long ago that
self-knowledge was a given, and at still is among "legacy programmers."


> ...
> I think the standard definition of standard includes, approved,
> reviewed, and publicly available.

That implies you think that TCP, IP, STMP, and the rest of the IETF's
claim to fame are not standards because they were not externally (since
I'm sure AOL reviews AOL stuff) reviewed more than AOL's, were in practice
no more publically available (who knew of them?), and several years after
being specified, were not merely unapproved but explicitly forbidden by
many national goverments in the many GOSIP's.

Believe it or not, SMTP was not created this year with the publication of
the new SMTP RFC, nor even 1989 with the minor elaborations in RFC 1123.
TCP is not significantly changed from it's ancient, unapproved, unreviewd
(by outsiders), not publicly available (because of obscurity) form.  Thus
the only large scale transport protocols available that meet your
particular definition of "standard" are TP0 through TP4.

Why do I suspect some of the most vigorous supporters of the sanctity of
standards committee authority don't know what I mean by GOSIP and TP4?
In other words and as I said before, many of the revolutionaries moved
into the deposed overlords' offices and accepted fealty from the toadies,
go-ers, empire builders, and courtiers of the old regime, and things went
back to normal.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu Jul 13 18:00:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA20009
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 18:00:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16683
	for <ietf@ietf.org>; Thu, 13 Jul 2000 17:50:17 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA11768;
        Thu, 13 Jul 2000 17:50:17 -0400 (EDT)
Message-Id: <200007132150.RAA11768@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: precedence field and mailing lists 
In-reply-to: Your message of "Thu, 13 Jul 2000 12:27:24 MDT."
             <200007131827.e6DIRO904849@calcite.rhyolite.com> 
Date: Thu, 13 Jul 2000 17:50:17 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> I've recombined these because they have an important connection, the
> notion that the pronouncements of ITU, ANSI, IEEE, ATM Forum, the WAP
> consortium, and the IETF are somehow necessarily better than those of any
> other arbitrary group of people.

none of these is an 'arbitrary' group of people.  the thing that makes one
group different from another, and potentially impacts the quality of
that group's work, is the kinds of people that each group attracts -
their talents, their values, their kinds of expertise, their culture,
and their ability to work together to acheive common goals.

> Despite IETF snobbery, Precedence: has decades of use.  

Precedence has decades of *varying* and "conflicting* use.  
That's not a result of IETF snobbery, that's a result of poor
design in the first place and, subsequently, several instances 
of J. Random email hacker deciding (incorrectly), in absence 
of any published definition of the Precedence field, that 
Precedence already did more-or-less what he/she wanted and 
there was no need to define a new field that did the right thing.

> It has defects as
> a vacation program tamer, but those would be better fixed by coming up
> with a replacement than by ignoring the problem.  

you don't need a 'replacement' header field to keep vacation from 
replying.  all you have to do is not send an auto-reply when the 
recipient's address doesn't appear in the To or Cc header field. 

> > > In other words, the IETF itself is not above some standads bending..
> >
> > what standard are you referring to?
> 
> How about hoping that X-Loop will be preserved by those peered mailing
> lists and other gateways and so prevent loops?

fine with me.  but I don't see what this has to do with the IETF list.

As for the drivel about AOL proprietary protocols being standards:
You can act like Humpty Dumpty if you want to, but don't pretend 
that anyone else is going to listen.

Keith



From owner-ietf-outbound  Thu Jul 13 18:40:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA01835
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 18:40:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00359
	for <ietf@ietf.org>; Thu, 13 Jul 2000 18:33:39 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 13CrXy-0007Nt-00; Thu, 13 Jul 2000 23:33:34 +0100
Date: Thu, 13 Jul 2000 23:33:31 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: precedence field and mailing lists
In-Reply-To: <200007132144.e6DLi2l08298@calcite.rhyolite.com>
Message-ID: <Pine.GSO.4.21.0007132322480.29318-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Thu, 13 Jul 2000, Vernon Schryver wrote:

> > From: Doug Royer <Doug.Royer@SOFTWARE.COM>
> > ...
> > Could you please point me at the standards (or otherwise) documents
> > that describe the semantics of 'Precedence:'?  It sounds interesting
> > but I just can't seem to find out what you mean or expect it to do.
> 
> `man vacation` on any modern BSD-like UNIX box should say something like:
>    No message will be sent unless login (or an alias supplied using the -a
>    option) is part of either the ``To:'' or ``Cc:'' headers of the mail.

Over the past few weeks I've been replying to a number
of vacation mails sent to me as a result of posting here with:

I sent mail to a mailing list. Not to you. Your autoreply software
should only reply to mail explicitly To: or Cc: you.
[Oh, and your autoreply is screwed. No body. - optional when needed.]
[Oh, and you're not maintaining a list of addresses already contacted
- optional when needed.]

L.

oh, and you Cc: to postmaster for maximum effect.

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





From owner-ietf-outbound  Thu Jul 13 20:01:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA25766
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 20:00:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24475
	for <ietf@ietf.org>; Thu, 13 Jul 2000 19:54:26 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007132346.IAA02761@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id IAA02761; Fri, 14 Jul 2000 08:46:23 +0900
Subject: Re: belated apology
In-Reply-To: <200007130247.WAA27208@astro.cs.utk.edu> from Keith Moore at "Jul
 12, 2000 10:47:23 pm"
To: Keith Moore <moore@cs.utk.edu>
Date: Fri, 14 Jul 2000 08:46:22 +0859 ()
CC: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Keith;

> p.s. I do however think that, given the tendency of various providers 
> these days to violate the internet protocol specifications and
> erode the ability of applications to run on the network,  the 
> community might benefit from some kind of "standardized" (in the
> loose sense) description of IP service (rather than ISPs) that could be 
> specified by customers.  and IETF would appear to be the organization 
> which is best suited to define such terms.

It exactly what IETF is (or, at least, was) doing, when loose sense
means "standard to be used on the Internet".

IETF is "Internet Engineering Task Force", not "IP Engineering
Task Force".

IETF can't say anything to braindead protocols of braindead providers
in their purely private IP network.

							Masataka Ohta



From owner-ietf-outbound  Thu Jul 13 20:11:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA28676
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 20:10:02 -0400 (EDT)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25797
	for <ietf@ietf.org>; Thu, 13 Jul 2000 20:00:10 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id QAA20933;
	Thu, 13 Jul 2000 16:59:58 -0700 (PDT)
Date: Thu, 13 Jul 2000 16:59:58 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200007132359.QAA20933@shell9.ba.best.com>
To: ietf@ietf.org
Subject: RE: HTML forms 
X-Loop: ietf@ietf.org

jty202@yahoo.com writes:
>
> Subject: Re: HTML forms
> 
> Need info. on programming voice over ip....

If you mean with HTML forms, try:

  http://www.bovik.org/devup

Imagine my shock when I learned microphone upload wasn't in MSIE 5.5.

Mozilla already has it, if you're willing to apply the patch referenced 
on the page above.  Soon the Mozilla helper application registry (which 
was completed less than two weeks ago) will handle input helper 
applications in addition to traditional output helper applications.

Amaya, the official web browser of the W3C, still doesn't even have 
file upload.  And the W3C policy directors have capitulated so far to 
the estado corporativo that they might as well start displaying the 
Microsoft and WAP Forum logos on www.w3.org.  Good thing that those 
Melissa/ILoveYou/etc. worms only truncate *.{doc,xls,ppt,c,h,asm} 
files, because if they hit HTML files the W3C web site would probably 
go blank every day.  (But don't worry, I'm sure that the Outlook patch 
that Microsoft's Office Products Division V.P. promised over two 
months ago will be ready real soon now.)

Anyone know whether Opera has microphone upload yet?

Cheers,
James



From owner-ietf-outbound  Thu Jul 13 20:21:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA01255
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 20:20:04 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27482
	for <ietf@ietf.org>; Thu, 13 Jul 2000 20:06:06 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007132355.IAA02811@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id IAA02811; Fri, 14 Jul 2000 08:54:55 +0859
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <200007130239.WAA27021@astro.cs.utk.edu> from Keith Moore at "Jul
 12, 2000 10:39:01 pm"
To: Keith Moore <moore@cs.utk.edu>
Date: Fri, 14 Jul 2000 08:54:54 +0859 ()
CC: aboba@internaut.com,
        =?us-ascii?Q?=3D=3Fus=2Dascii=3FQ=3F=27Patrik=5FFaltstrom=27=3F?= =?us-ascii?Q?=3D?=
 <paf@cisco.com>,
        "'Randy Bush'" <randy@psg.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Keith;

> > If IETF makes it clear that AOL is not an ISP, it will commercially
> > motivate AOL to be an ISP.
> 
> probably not.  folks who subscribe to AOL aren't likely to be 
> reading IETF documents.

AOL will be motivated but, considering other factors, may not
change the current practice.

That's fine.

> face it, it's not the superior quality of AOL's service that keeps 
> AOLers from moving - it's their susceptibility to marketing BS and
> their addiction to chat rooms.  it's hard to help those people.

I'm no user of AOL that I don't have to face it.

It is arrogance of you if you think you must help AOL users.

Just make the IETF definition of "ISP" clear and let ISP competitors
of AOL give reasons to say "AOL is not ISP".

							Masataka Ohta



From owner-ietf-outbound  Thu Jul 13 20:43:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA06738
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 20:40:03 -0400 (EDT)
Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01296
	for <ietf@ietf.org>; Thu, 13 Jul 2000 20:20:09 -0400 (EDT)
Received: from Software.com ([207.175.94.235]) by mta1biz.bizmailsrvcs.net
          with ESMTP
          id <20000714002040.JSIC459995.mta1biz.bizmailsrvcs.net@Software.com>;
          Thu, 13 Jul 2000 19:20:40 -0500
Sender: droyer
Message-ID: <396E4C05.A199EED8@Software.com>
Date: Thu, 13 Jul 2000 16:08:53 -0700
From: Doug Royer <Doug.Royer@Software.com>
Organization: Software.com
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Vernon Schryver <vjs@CALCITE.RHYOLITE.COM>
CC: ietf@ietf.org
Subject: Re: precedence field and mailing lists
References: <200007132144.e6DLi2l08298@calcite.rhyolite.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms39C7FD79DED86BCF4C72DF45"
X-Loop: ietf@ietf.org

This is a cryptographically signed message in MIME format.

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

> > ...
> > Something can be 'standard' and never used by anyone. Something can be
> > used by everyone and never a 'standard'.
> 
> Perhaps according to the Church of De Jure Standards.

Well according to those in the IETF (This mailing list you keep
sending to). Did you expect the ietf@ietf.org mailing list
to say everything is a standard just because someone wants it to be?

When in Rome do as the Romans.

When on an IETF mailing list, the language and definitions are
defined in RFC's. They are (at least) Experimental, Informational,
Standards Track, and Standard as defined by the IETF RFC's.

> I mean AOL's protocols, applications, and other computer stuff which meet
> the definition of "standard" in http://www.m-w.com/ by being "established
> by authority, custom, or general consent as a model or example."

I still seem to be missing your point. Is it that you wish to change the
IETF to be more like the AOL chat rooms? 

> The consent and custom of 23,000,000 people and the authority of AOL meet
> all three of those dictionary requirements.  They don't and should not
> meet modern IETF requirements for standards track RFCs, but I suspect that
> if (perhaps a big 'if') they met technical muster, they would have been
> accepted 18 or 20 years ago by the ad hoc group that preceded the IETF.

Again, why are you posting to this group list if you do not
respect its processes? If you are attempting to change something,
then maybe I missed your proposal.

-Doug
--------------ms39C7FD79DED86BCF4C72DF45
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIIKVQYJKoZIhvcNAQcCoIIKRjCCCkICAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CCIwggTsMIIEVaADAgECAhA2tOutfntkPZeWwhSMC60VMA0GCSqGSIb3DQEBBAUAMIHMMRcw
FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5
IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp
dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAwMDExNzAwMDAw
MFoXDTAwMTAxMzIzNTk1OVowggEZMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE
CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y
ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO
ZXRzY2FwZSBGdWxsIFNlcnZpY2UxGDAWBgNVBAMUD0RvdWdsYXMgTSBSb3llcjEmMCQGCSqG
SIb3DQEJARYXZG91Zy5yb3llckBzb2Z0d2FyZS5jb20wXDANBgkqhkiG9w0BAQEFAANLADBI
AkEA8b+/7AusCQc89McoXWlPBDcEaOyt/e2NdL+lPypsoauWxoLohWrk708y93xfziOVZ/Jh
3yF9Dq43K9rW9m8SewIDAQABo4IBwTCCAb0wCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe
BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t
L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg
Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ
YIZIAYb4QgEBBAQDAgeAMIGGBgpghkgBhvhFAQYDBHgWdmQ0NjUyYmQ2M2YyMDQ3MDI5Mjk4
NzYzYzlkMmYyNzUwNjljNzM1OWJlZDFiMDU5ZGE3NWJjNGJjOTcwMTc0N2RhNWQzZjIxNDFi
ZWFkYjJiZDJlODkyMWZhODZiZjFkMTExNDk5ZmEzYmE0N2ZkZjNlYTQ1MDYwMAYKYIZIAYb4
RQEGBwQiFiA2NWVlMGM5M2RkNDY2OGJjNGViOGM2OWNiMDliZWYxNzAzBgNVHR8ELDAqMCig
JqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0GCSqGSIb3DQEBBAUA
A4GBAIfiBv6wsXfERKczHkNCZ3zPRgSs/eOEutA2lnTtejz+sHTm3XWcEEx0zcEkYafFIOCK
GFgFsy6cR4czApnWlILPzDAyT+FcDsAqTtSGDL8jTVMo/7MW6CHReAc0oSzGtapMxWcLgaMh
/D0lM5vSddVM7EgNhGLWQPoAvxKe4PExMIIDLjCCApegAwIBAgIRANJ2Lo0UDD19sqglXa/u
DXUwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0
aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZl
cmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQL
Ez13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFC
LkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vi
c2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ
AoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJvnFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI
4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpdtrA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqO
f2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMBAAGjfDB6MBEGCWCGSAGG+EIBAQQEAwIBBjBH
BgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5j
b20vcmVwb3NpdG9yeS9SUEEwDwYDVR0TBAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZI
hvcNAQECBQADgYEAiLg3O93alDcAraqf4YEBcR6Sam0v9vGd08pkONwbmAwHhluFFWoPuUmF
pJXxF31ntH8tLN2aQp7DPrSOquULBt7yVir6M8e+GddTTMO9yOMXtaRJQmPswqYXD11YGkk8
kFxVo2UgAP0YIOVfgqaxqJLFWGrBjQM868PNBaKQrm4xggH7MIIB9wIBATCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQNrTrrX57ZD2XlsIUjAut
FTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF
MQ8XDTAwMDcxMzIzMDg1NlowIwYJKoZIhvcNAQkEMRYEFBV9jGHxnVXm3QxxpQ6q1LQbllVq
MFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIH
MA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3DQEBAQUABEB1yeD5PMjx
kbFWifknfZ+g/pUsTrk6QvcGgsMTlN6oHl0cy/QK40EnwiqCwYPcrlFkO+5ikVuTW3QiX/HY
xERL
--------------ms39C7FD79DED86BCF4C72DF45--



From owner-ietf-outbound  Thu Jul 13 20:54:00 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA09337
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 20:50:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04239
	for <ietf@ietf.org>; Thu, 13 Jul 2000 20:29:38 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 13CtMA-0000bj-00; Fri, 14 Jul 2000 01:29:30 +0100
Date: Fri, 14 Jul 2000 01:29:27 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: "James P. Salsman" <bovik@best.com>
cc: ietf@ietf.org
Subject: RE: HTML forms
In-Reply-To: <200007132359.QAA20933@shell9.ba.best.com>
Message-ID: <Pine.GSO.4.21.0007140129110.29318-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Thu, 13 Jul 2000, James P. Salsman wrote:

> Anyone know whether Opera has microphone upload yet?

More to the point, does anyone care?

L.

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



From owner-ietf-outbound  Thu Jul 13 21:03:03 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA11700
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 21:00:03 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11557
	for <ietf@ietf.org>; Thu, 13 Jul 2000 20:59:28 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.11.0.Beta3/calcite) id e6E0xTN12063
	for ietf@ietf.org  env-from <vjs>;
	Thu, 13 Jul 2000 18:59:29 -0600 (MDT)
Date: Thu, 13 Jul 2000 18:59:29 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007140059.e6E0xTN12063@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: precedence field and mailing lists
X-Loop: ietf@ietf.org

> From: Doug Royer <Doug.Royer@Software.com>

> ...
> I still seem to be missing your point. Is it that you wish to change the
> IETF to be more like the AOL chat rooms? 

Exactly the opposite, assuming that my guess that AOL chat rooms (which
I've never seen directly) and modern netnews share some characteristics.


> Again, why are you posting to this group list if you do not
> respect its processes? If you are attempting to change something,
> then maybe I missed your proposal.

I thought I was clear about proposing that the IESG or whomever add those
nasty, evil, not entirely effective, sometimes harmful, anti-standard,
profane, deprecated, left-coast Precedence: Bulk lines in the hope of
reducing the plague of vacation noise.

Agreed; as Lloyd Wood and Keith Moore have pointed out, if people would
use vacation programs that didn't respond to Bcc's, then Precedence: bulk
would be redundant.  And yes, vacation programs that reply to bcc's cannot
be relied upon to get Precedence: bulk right.

If I've a second proposal, it would be that people who delude themselves
into thinking that talk every few months in a hotel ballroom or a mailing
list matters more than what happens in the outer of the world check their
Microsoft style provincialism--err--inward directedness for holes.


> --------------ms39C7FD79DED86BCF4C72DF45
> Content-Type: application/x-pkcs7-signature; name="smime.p7s"
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment; filename="smime.p7s"
> Content-Description: S/MIME Cryptographic Signature
>
> MIIKVQYJKoZIhvcNAQcCoIIKRjCCCkICAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
> ...

A third proposal is that people not send nearly 4K byte signature blocks
such as that one to 1000's of people (and 2 copies to me), particularly
in circumstances where they serve no conceivable good, except perhaps to
support by example my second proposal.  (Since Mr.  Royer's preceding
message did not consist mostly of cryptographic cybercrud, I assume this
was purely an accident instead of an effort to second my 2nd proposal.)


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu Jul 13 21:51:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA28173
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 21:50:02 -0400 (EDT)
Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22508
	for <ietf@ietf.org>; Thu, 13 Jul 2000 21:33:29 -0400 (EDT)
Received: from Software.com ([207.175.94.235]) by mta1biz.bizmailsrvcs.net
          with ESMTP
          id <20000714013401.JTNX459995.mta1biz.bizmailsrvcs.net@Software.com>;
          Thu, 13 Jul 2000 20:34:01 -0500
Sender: droyer
Message-ID: <396E5D38.DFEB8B84@Software.com>
Date: Thu, 13 Jul 2000 17:22:16 -0700
From: Doug Royer <Doug.Royer@Software.com>
Organization: Software.com
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Vernon Schryver <vjs@CALCITE.RHYOLITE.COM>
CC: ietf@ietf.org
Subject: Re: precedence field and mailing lists
References: <200007140059.e6E0xTN12063@calcite.rhyolite.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms267A7009C5FC54E473A1779E"
X-Loop: ietf@ietf.org

This is a cryptographically signed message in MIME format.

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


> I thought I was clear about proposing that the IESG or whomever add those
> nasty, evil, not entirely effective, sometimes harmful, anti-standard,
> profane, deprecated, left-coast Precedence: Bulk lines in the hope of
> reducing the plague of vacation noise.

Then write an internet draft and drive it through the IETF processes.
If people like it, they adopt it. So far I don't think that 'Precedence'
is a standard. If you want it to be an IETF standard (and you are sending
to the IETF list), then submit an internet draft.

> Agreed; as Lloyd Wood and Keith Moore have pointed out, if people would
> use vacation programs that didn't respond to Bcc's, then Precedence: bulk
> would be redundant.  And yes, vacation programs that reply to bcc's cannot
> be relied upon to get Precedence: bulk right.

Exactly why we have this process. I as a user want ALL of the
senders of email (bcc'd to me and all) being notified of the fact that
I am on vacation. I don't see it as a bug. I might be in the minority or
you might be in the minority. Until there is a proposal - the correct
people will not debate the solution.

> If I've a second proposal, it would be that people who delude themselves
> into thinking that talk every few months in a hotel ballroom or a mailing
> list matters more than what happens in the outer of the world check their
> Microsoft style provincialism--err--inward directedness for holes.

If you don't like the IETF process: (1) try to change it using
the rules, or (2) quit.

> A third proposal is that people not send nearly 4K byte signature blocks
> such as that one to 1000's of people (and 2 copies to me), particularly
> in circumstances where they serve no conceivable good, except perhaps to
> support by example my second proposal.  (Since Mr.  Royer's preceding
> message did not consist mostly of cryptographic cybercrud, I assume this
> was purely an accident instead of an effort to second my 2nd proposal.)

Perhaps you can write a draft to include user preferences in email.
In that way an MUA will not sent data you don't like. Unless of course
others think of those preferences as cybercrud. :-)

-Doug
--------------ms267A7009C5FC54E473A1779E
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIIKVQYJKoZIhvcNAQcCoIIKRjCCCkICAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CCIwggTsMIIEVaADAgECAhA2tOutfntkPZeWwhSMC60VMA0GCSqGSIb3DQEBBAUAMIHMMRcw
FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5
IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp
dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAwMDExNzAwMDAw
MFoXDTAwMTAxMzIzNTk1OVowggEZMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE
CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y
ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO
ZXRzY2FwZSBGdWxsIFNlcnZpY2UxGDAWBgNVBAMUD0RvdWdsYXMgTSBSb3llcjEmMCQGCSqG
SIb3DQEJARYXZG91Zy5yb3llckBzb2Z0d2FyZS5jb20wXDANBgkqhkiG9w0BAQEFAANLADBI
AkEA8b+/7AusCQc89McoXWlPBDcEaOyt/e2NdL+lPypsoauWxoLohWrk708y93xfziOVZ/Jh
3yF9Dq43K9rW9m8SewIDAQABo4IBwTCCAb0wCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe
BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t
L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg
Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ
YIZIAYb4QgEBBAQDAgeAMIGGBgpghkgBhvhFAQYDBHgWdmQ0NjUyYmQ2M2YyMDQ3MDI5Mjk4
NzYzYzlkMmYyNzUwNjljNzM1OWJlZDFiMDU5ZGE3NWJjNGJjOTcwMTc0N2RhNWQzZjIxNDFi
ZWFkYjJiZDJlODkyMWZhODZiZjFkMTExNDk5ZmEzYmE0N2ZkZjNlYTQ1MDYwMAYKYIZIAYb4
RQEGBwQiFiA2NWVlMGM5M2RkNDY2OGJjNGViOGM2OWNiMDliZWYxNzAzBgNVHR8ELDAqMCig
JqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0GCSqGSIb3DQEBBAUA
A4GBAIfiBv6wsXfERKczHkNCZ3zPRgSs/eOEutA2lnTtejz+sHTm3XWcEEx0zcEkYafFIOCK
GFgFsy6cR4czApnWlILPzDAyT+FcDsAqTtSGDL8jTVMo/7MW6CHReAc0oSzGtapMxWcLgaMh
/D0lM5vSddVM7EgNhGLWQPoAvxKe4PExMIIDLjCCApegAwIBAgIRANJ2Lo0UDD19sqglXa/u
DXUwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0
aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZl
cmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQL
Ez13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFC
LkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vi
c2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ
AoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJvnFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI
4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpdtrA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqO
f2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMBAAGjfDB6MBEGCWCGSAGG+EIBAQQEAwIBBjBH
BgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5j
b20vcmVwb3NpdG9yeS9SUEEwDwYDVR0TBAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZI
hvcNAQECBQADgYEAiLg3O93alDcAraqf4YEBcR6Sam0v9vGd08pkONwbmAwHhluFFWoPuUmF
pJXxF31ntH8tLN2aQp7DPrSOquULBt7yVir6M8e+GddTTMO9yOMXtaRJQmPswqYXD11YGkk8
kFxVo2UgAP0YIOVfgqaxqJLFWGrBjQM868PNBaKQrm4xggH7MIIB9wIBATCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQNrTrrX57ZD2XlsIUjAut
FTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF
MQ8XDTAwMDcxNDAwMjIxNlowIwYJKoZIhvcNAQkEMRYEFBTe+mQv2P2WIp4uI/HDyz7jb3Vk
MFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIH
MA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3DQEBAQUABEBbeZAyzsfL
DqtSApgKOeDPXFsrWXMFyWd80X2892Lq+W6UFPhP1AOmSFGWHZ8ecm7jTjvM99BA5I9cxh0d
Vpii
--------------ms267A7009C5FC54E473A1779E--



From owner-ietf-outbound  Thu Jul 13 22:11:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA03889
	for ietf-outbound.10@ietf.org; Thu, 13 Jul 2000 22:10:03 -0400 (EDT)
Received: from mail.nbn.net (root@nbn.net [207.51.86.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02686
	for <ietf@ietf.org>; Thu, 13 Jul 2000 22:04:44 -0400 (EDT)
Received: from server-1 (dial5-59.nbn.net [208.139.67.245])
	by mail.nbn.net (8.9.3/8.9.3) with SMTP id WAA29128
	for <ietf@ietf.org>; Thu, 13 Jul 2000 22:04:41 -0400
Message-ID: <396E7852.10E6@nbn.net>
Date: Thu, 13 Jul 2000 22:17:54 -0400
From: Betsy Brennan <bbrennan@nbn.net>
Reply-To: bbrennan@nbn.net
X-Mailer: Mozilla 3.04 (Win95; U)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Cryptography
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Can anyone tell me where I can get Current information about
Cryptography and US law? Thanks before hand. BLB



From owner-ietf-outbound  Fri Jul 14 02:20:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA29602
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 02:20:04 -0400 (EDT)
Received: from roam.psg.com (roam.psg.com [147.28.0.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26093
	for <ietf@ietf.org>; Fri, 14 Jul 2000 02:10:04 -0400 (EDT)
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 13Cwa3-0001CW-00; Thu, 13 Jul 2000 20:56:03 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
Cc: ietf@ietf.org
Subject: RE: IP service definition
References: <200007130247.WAA27208@astro.cs.utk.edu>
	<006d01bfecd4$0ad64660$d001010a@tst.ennovatenetworks.com>
Message-Id: <E13Cwa3-0001CW-00@roam.psg.com>
Date: Thu, 13 Jul 2000 20:56:03 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> It is akin to standardizing on what kind of light can come in your
> neighbourhood.

properly done, and with no adjectives or judgement spin, it could be a
taxonomy of what kinds of light are known.  this might be useful, witness
a recent discussion re wap of what is being on the internet.

randy



From owner-ietf-outbound  Fri Jul 14 04:10:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA29820
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 04:10:01 -0400 (EDT)
Received: from peace.off.org (root@peace.off.org [198.58.4.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28819
	for <ietf@ietf.org>; Fri, 14 Jul 2000 04:05:23 -0400 (EDT)
Received: (from tex@localhost)
	by peace.off.org (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id AAA32203;
	Fri, 14 Jul 2000 00:04:35 -0700
Date: Fri, 14 Jul 2000 00:04:35 -0700
From: Austin Schutz <tex@gblx.net>
To: Lloyd Wood <l.wood@eim.surrey.ac.uk>
Cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: precedence field and mailing lists
Message-ID: <20000714000435.C31745@off.org>
References: <200007132144.e6DLi2l08298@calcite.rhyolite.com> <Pine.GSO.4.21.0007132322480.29318-100000@petra.ee.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <Pine.GSO.4.21.0007132322480.29318-100000@petra.ee.surrey.ac.uk>
X-Loop: ietf@ietf.org

On Thu, Jul 13, 2000 at 11:33:31PM +0100, Lloyd Wood wrote:
> On Thu, 13 Jul 2000, Vernon Schryver wrote:
> 
> > > From: Doug Royer <Doug.Royer@SOFTWARE.COM>
> > > ...
> > > Could you please point me at the standards (or otherwise) documents
> > > that describe the semantics of 'Precedence:'?  It sounds interesting
> > > but I just can't seem to find out what you mean or expect it to do.
> > 
> > `man vacation` on any modern BSD-like UNIX box should say something like:
> >    No message will be sent unless login (or an alias supplied using the -a
> >    option) is part of either the ``To:'' or ``Cc:'' headers of the mail.
> 
> Over the past few weeks I've been replying to a number
> of vacation mails sent to me as a result of posting here with:
> 
> I sent mail to a mailing list. Not to you. Your autoreply software
> should only reply to mail explicitly To: or Cc: you.

	This breaks for mail aliases. Perhaps, if you are root on
a unix machine, you might want someone sending mail to that address
to know you are away?

	Austin



From owner-ietf-outbound  Fri Jul 14 04:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA04171
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 04:30:03 -0400 (EDT)
Received: from pusren01.risti.telkom.co.id (pusren01.risti.telkom.co.id [202.134.0.53])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02693
	for <ietf@ietf.org>; Fri, 14 Jul 2000 04:23:11 -0400 (EDT)
Received: from TMN11 ([10.14.5.254])
	by pusren01.risti.telkom.co.id (8.9.1/8.9.1) with SMTP id PAA12257
	for <ietf@ietf.org>; Fri, 14 Jul 2000 15:30:17 +0700 (JVT)
Reply-To: <heruir@risti.telkom.co.id>
From: "Heru Irman" <heruir@risti.telkom.co.id>
To: <ietf@ietf.org>
Subject: RE: SNMP, CORBA and XML
Date: Fri, 14 Jul 2000 15:31:52 +0700
Message-ID: <005201bfed6d$f6c6b8e0$fe050e0a@telkom.co.id>
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.2314.1300
In-Reply-To: <NDBBIFGHKLHKNCMEKGHAKEFCCCAA.yixin@xybridge.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I think the other protocols to be added on are CMIP and TL1.
And for sure we still need more then one protocol to do and manage all
stuff.
Any doubt?

-----Original Message-----
From: Yixin Zhu [mailto:yixin@xybridge.com]
Sent: Thursday, July 13, 2000 11:09 PM
To: Gayen, Sanjukta, CMDR; ietf@ietf.org
Subject: RE: SNMP, CORBA and XML


In addition, I am also interested in the differences bwteen SNMP and JMX.
Thanks.


Yixin Zhu

-----Original Message-----
From: Gayen, Sanjukta, CMDR [mailto:gayen@att.com]
Sent: Thursday, July 13, 2000 10:49 AM
To: 'ietf@ietf.org'
Subject: SNMP, CORBA and XML




I am trying to understand the application and advantages of multiple
protocols like SNMP, CORBA and XML. I will appreciate a lot if any one can
help me to understand which protocol to choose under what circumstances.  I
am coming across few systems which supports all three interfaces. Can only
one protocol do the job ?

Thanks very much in advance.
Sanjukta Gayen



From owner-ietf-outbound  Fri Jul 14 05:20:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA14968
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 05:20:02 -0400 (EDT)
Received: from peace.off.org (root@peace.off.org [198.58.4.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13769
	for <ietf@ietf.org>; Fri, 14 Jul 2000 05:14:22 -0400 (EDT)
Received: (from tex@localhost)
	by peace.off.org (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id BAA32373;
	Fri, 14 Jul 2000 01:14:10 -0700
Date: Fri, 14 Jul 2000 01:14:10 -0700
From: Austin Schutz <tex@gblx.net>
To: Lloyd Wood <l.wood@eim.surrey.ac.uk>
Cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Arrgh! Re: precedence field and mailing lists
Message-ID: <20000714011410.F31745@off.org>
References: <200007132144.e6DLi2l08298@calcite.rhyolite.com> <Pine.GSO.4.21.0007132322480.29318-100000@petra.ee.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <Pine.GSO.4.21.0007132322480.29318-100000@petra.ee.surrey.ac.uk>
X-Loop: ietf@ietf.org

> Over the past few weeks I've been replying to a number
> of vacation mails sent to me as a result of posting here with:
> 
	Now _I'm_ getting them :P

	Here are the applicable headers. Note the absence of X-loop or
precedence headers! 

To: tex@gblx.net
Subject: Out of Office AutoReply: precedence field and mailing lists
Date: Fri, 14 Jul 2000 04:14:11 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain

	If Precendence: bulk stops this broken behavior, it might be
worth implementing, if only to stop the inevitable DOS that will occur
when someone clever and irritating figures out what happens when you
forge mail from one of these weenies to the list. I verified that they
don't respond to mail w/ Precedence: bulk, btw.
	Wanna have some real fun? See what happens when you forge mail
from all of them to each other _and_ cc: the list.
	Of course maybe the Content-Type header lets their software know
that it's a web page, not mail, so it's not necessary to respond to
anyway.

	Austin



From owner-ietf-outbound  Fri Jul 14 05:50:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA22127
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 05:50:03 -0400 (EDT)
Received: from aloe.us.pw.com ([12.26.159.123])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA17946
	for <ietf@ietf.org>; Fri, 14 Jul 2000 05:30:55 -0400 (EDT)
From: arindam.das@in.pwcglobal.com
Received: by aloe.us.pw.com; id FAA01426; Fri, 14 Jul 2000 05:23:43 -0400
Received: from palm.us.pw.com(10.26.104.82) by aloe.us.pw.com via smap (4.1)
	id xma000988; Fri, 14 Jul 00 05:23:17 -0400
Received: from intlnamsmtp10.us.pw.com by palm.us.pw.com (PMDF V5.1-12 #U3018)
 with SMTP id <0FXO00KVZL6QAN@palm.us.pw.com> for ietf@ietf.org; Fri,
 14 Jul 2000 05:32:52 -0400 (EDT)
Received: by intlnamsmtp10.us.pw.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))
 id 8525691C.003429CA ; Fri, 14 Jul 2000 05:29:45 -0400
Date: Fri, 14 Jul 2000 14:20:01 +0530
Subject: RE: SNMP, CORBA and XML
To: ietf@ietf.org
Message-id: <8525691C.00342967.00@intlnamsmtp10.us.pw.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
X-Lotus-FromDomain: PRICE WATERHOUSE-INDIA@INTL
X-Loop: ietf@ietf.org




Each protocol obviously has its own pros and cons and also areas of application.
SNMP is for mail transfer whereas CORBA allows you to work with Live Objects
across networks as if whole network is a single machine.
----------------------------------------------------------------
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential and/or privileged material.  Any
review, retransmission, dissemination or other use of, or taking of any action
in reliance upon, this information by persons or entities other than the
intended recipient is prohibited.   If you received this in error, please
contact the sender and delete the material from any computer.




From owner-ietf-outbound  Fri Jul 14 06:00:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA24677
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 06:00:02 -0400 (EDT)
Received: from ztxmail04.ztx.compaq.com (ztxmail04.ztx.compaq.com [161.114.1.208])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19235
	for <ietf@ietf.org>; Fri, 14 Jul 2000 05:36:44 -0400 (EDT)
Received: by ztxmail04.ztx.compaq.com (Postfix, from userid 12345)
	id 7AB76959; Fri, 14 Jul 2000 04:36:15 -0500 (CDT)
Received: from excreo-gh01.reo.dec.com (excreo-gh01.reo.cpqcorp.net [16.41.128.40])
	by ztxmail04.ztx.compaq.com (Postfix) with ESMTP
	id C2FF38CC; Fri, 14 Jul 2000 04:36:14 -0500 (CDT)
Received: by excreo-gh01.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <N64N25JM>; Fri, 14 Jul 2000 10:36:13 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9CD8@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'L.Wood@eim.surrey.ac.uk'" <L.Wood@eim.surrey.ac.uk>,
        "James P. Salsman" <bovik@BEST.COM>
Cc: ietf@ietf.org
Subject: RE: HTML forms
Date: Fri, 14 Jul 2000 10:35:47 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Thanks for the confirmation there Lloyd :)

J.
-------------------------------------------------------

On Thu, 13 Jul 2000, James P. Salsman wrote:

> Anyone know whether Opera has microphone upload yet?

More to the point, does anyone care?

L.

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



From owner-ietf-outbound  Fri Jul 14 06:10:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA27201
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 06:10:02 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20822
	for <ietf@ietf.org>; Fri, 14 Jul 2000 05:44:07 -0400 (EDT)
Received: from contactdish (atkielsk.adsl-net2-rg.nerim.net [62.4.19.136]) by atkielski.com (8.8.8) id LAA21030; Fri, 14 Jul 2000 11:44:08 +0200 (CEST)
Message-ID: <01dc01bfed78$0e7a55a0$0a00000a@contactdish>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <983B9A17F5EBD311905600D0B73EA0DE3023E6@APOLLO>
Subject: Re: Email Privacy eating software
Date: Fri, 14 Jul 2000 11:44:03 +0200
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
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I don't understand why the FBI feels that it needs to have a top-secret
black box attached to the ISP's network.  Why not just have the ISP provide
a copy of all e-mail to or from the specified mailbox?

----- Original Message -----
From: "Lillian Komlossy" <Lillian@dmnews.com>
To: <ietf@ietf.org>
Sent: Thursday, July 13, 2000 21:31
Subject: Email Privacy eating software


> The following articles describe an email reading software Big Bro is
> apparently already using. I think this is more than appropriate to start a
> discussion about.
>
> While it can be a powerful tool in the right hands, my three concerns
about
> this are:
> 1. Privacy of course - just the same way you don't want somebody
> reading your snail mail - for all intents and purposes email is not
> different.
> 2. Who oversees the agents in terms of - who are they going to go
> after - bad guys, or maybe political opponents?
> 3. How long before the software will collect 'other' information as
> well - and sell -ah pardon me: "make it available" to "valuable third
party
> companies" ?
>
> Make up your own mind, here are the links:
> http://www.zdnet.com/zdnn/stories/news/0,4586,2601502,00.html
> and
> http://www.zdnet.com/zdnn/stories/comment/0,5859,2601960,00.html
>
> Lillian Komlossy || Site Manager || http://www.dmnews.com ||
> http://www.imarketingnews.com || 212 925-7300 ext. 232 ||
> mailto:lillian@dmnews.com
>
>



From owner-ietf-outbound  Fri Jul 14 06:20:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA00399
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 06:20:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21089
	for <ietf@ietf.org>; Fri, 14 Jul 2000 05:45:16 -0400 (EDT)
Received: from contactdish (atkielsk.adsl-net2-rg.nerim.net [62.4.19.136]) by atkielski.com (8.8.8) id LAA21120; Fri, 14 Jul 2000 11:45:17 +0200 (CEST)
Message-ID: <01df01bfed78$379f7a00$0a00000a@contactdish>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <396E7852.10E6@nbn.net>
Subject: Re: Cryptography
Date: Fri, 14 Jul 2000 11:45:15 +0200
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
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

The regulations have changed fairly recently, so it is very likely that few
books are up to date.  Otherwise, _Applied Cryptography_ provides an
excellent overview.

----- Original Message -----
From: "Betsy Brennan" <bbrennan@nbn.net>
To: <ietf@ietf.org>
Sent: Friday, July 14, 2000 04:17
Subject: Cryptography


> Can anyone tell me where I can get Current information about
> Cryptography and US law? Thanks before hand. BLB
>
>



From owner-ietf-outbound  Fri Jul 14 06:40:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA05935
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 06:40:03 -0400 (EDT)
Received: from svanekaer.dk (slowboat.svanekaer.dk [129.142.164.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA03080
	for <ietf@ietf.org>; Fri, 14 Jul 2000 06:30:51 -0400 (EDT)
Received: (qmail 35862 invoked by uid 1011); 14 Jul 2000 10:30:48 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 14 Jul 2000 10:30:48 -0000
Date: Fri, 14 Jul 2000 12:30:48 +0200 (CEST)
From: Steven Cotton <steven@cotton.dk>
X-Sender: steven@localhost
To: ietf@ietf.org
Subject: Re: Email Privacy eating software
In-Reply-To: <01dc01bfed78$0e7a55a0$0a00000a@contactdish>
Message-ID: <Pine.BSF.4.21.0007141229490.35758-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Fri, 14 Jul 2000, Anthony Atkielski wrote:

> I don't understand why the FBI feels that it needs to have a top-secret
> black box attached to the ISP's network.  Why not just have the ISP provide
> a copy of all e-mail to or from the specified mailbox?

Because other people will know when they're snooping.

-- 
steven




From owner-ietf-outbound  Fri Jul 14 07:00:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA11889
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 07:00:03 -0400 (EDT)
Received: from smtp.mail.yahoo.com (smtp.mail.yahoo.com [128.11.68.32])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA10248
	for <ietf@ietf.org>; Fri, 14 Jul 2000 06:55:26 -0400 (EDT)
Received: from ppp-203-197-9-214.bom.vsnl.net.in (HELO muralidharan) (203.197.9.214)
  by smtp.mail.yahoo.com with SMTP; 14 Jul 2000 10:55:21 -0000
X-Apparently-From: <raghavan?muralidharan@yahoo.com>
Message-ID: <007901bfed82$3bc59880$1000a8c0@muralidharan>
Reply-To: "R. Muralidharan" <r.muralidharan@IEEE.ORG>
From: "R. Muralidharan" <raghavan_muralidharan@yahoo.com>
To: <arindam.das@in.pwcglobal.com>, <ietf@ietf.org>
References: <8525691C.00342967.00@intlnamsmtp10.us.pw.com>
Subject: Re: SNMP, CORBA and XML
Date: Fri, 14 Jul 2000 16:25:17 +0530
Organization: OSS Systems (India) Pvt Ltd/IEEE Bombay section
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.2615.200
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi Arindam,

  Pl note SNMP is not same as SMTP. SMTP which expands to "Simple Mail
Transfer Protocol" is for mail transfer while SNMP expands to "Simple
Network Management Protocol" and is for management of network elements.
  RFC 2571 on "An Architecture for describing SNMP Management frameworks",
April 1999 is a good reference.

muralidharan

----- Original Message -----
From: <arindam.das@in.pwcglobal.com>
To: <ietf@ietf.org>
Sent: Friday, July 14, 2000 2:20 PM
Subject: RE: SNMP, CORBA and XML


> Each protocol obviously has its own pros and cons and also areas of
application.
> SNMP is for mail transfer whereas CORBA allows you to work with Live
Objects
> across networks as if whole network is a single machine.
> ----------------------------------------------------------------



__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com



From owner-ietf-outbound  Fri Jul 14 07:10:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA15750
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 07:10:02 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA13477
	for <ietf@ietf.org>; Fri, 14 Jul 2000 07:03:54 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.25238-0@bells.cs.ucl.ac.uk>; Fri, 14 Jul 2000 12:03:12 +0100
To: Anthony Atkielski <anthony@atkielski.com>
cc: ietf <ietf@ietf.org>
Subject: Re: Email Privacy eating software
In-reply-to: Your message of "Fri, 14 Jul 2000 11:44:03 +0200." <01dc01bfed78$0e7a55a0$0a00000a@contactdish>
Date: Fri, 14 Jul 2000 12:03:11 +0100
Message-ID: <6821.963572591@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <01dc01bfed78$0e7a55a0$0a00000a@contactdish>, Anthony Atkielski type
d:

 >>I don't understand why the FBI feels that it needs to have a top-secret
 >>black box attached to the ISP's network.  Why not just have the ISP provide
 >>a copy of all e-mail to or from the specified mailbox?


wiretap is a weapon in the FBI's armoury

in the US, YOU have the right to bear arms

You should demand the constitutional right to wiretap the FBI and CIA and so 
on right now.

that will fix things.

j.



From owner-ietf-outbound  Fri Jul 14 07:40:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA24240
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 07:40:02 -0400 (EDT)
Received: from zmamail03.zma.compaq.com (zmamail03.zma.compaq.com [161.114.64.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22794
	for <ietf@ietf.org>; Fri, 14 Jul 2000 07:33:57 -0400 (EDT)
Received: by zmamail03.zma.compaq.com (Postfix, from userid 12345)
	id D93034CC1; Fri, 14 Jul 2000 07:33:26 -0400 (EDT)
Received: from excreo-gh02.reo.cpqcorp.net (excreo-gh02.reo.cpqcorp.net [16.37.150.254])
	by zmamail03.zma.compaq.com (Postfix) with ESMTP
	id 450D95F7A; Fri, 14 Jul 2000 07:33:26 -0400 (EDT)
Received: by excreo-gh02.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <N6ZR5JW1>; Fri, 14 Jul 2000 12:33:25 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9CD9@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'Jon Crowcroft'" <J.Crowcroft@CS.UCL.AC.UK>,
        Anthony Atkielski <anthony@atkielski.com>
Cc: ietf <ietf@ietf.org>
Subject: RE: Email Privacy eating software
Date: Fri, 14 Jul 2000 12:33:19 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA22794
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

In the UK we have the same type of problem, this time from my Favorite
Company MI5.

'The UK is leading the world when it comes to high-tech spying on its
citizens'
Please see
http://news6.thdo.bbc.co.uk/hi/english/sci/tech/newsid_762000/762514.stm

Lets face it, internet service providers will be forced to install black
boxes in their 
data centres that connect directly to an MI5 monitoring centre in London.
Now that would 
be nice to hack into.  

More to the point, Who is going to fund this? 'thinking' Oh yes thats why
Petrol in the 
UK has now passed the £1.03 per litre barrier.
'http://www.rip-off.co.uk/fuel.htm' 

:-)

-----Original Message-----
From: Jon Crowcroft [mailto:J.Crowcroft@cs.ucl.ac.uk]
Sent: Friday, July 14, 2000 12:03 PM
To: Anthony Atkielski
Cc: ietf
Subject: Re: Email Privacy eating software



In message <01dc01bfed78$0e7a55a0$0a00000a@contactdish>, Anthony Atkielski
type
d:

 >>I don't understand why the FBI feels that it needs to have a top-secret
 >>black box attached to the ISP's network.  Why not just have the ISP
provide
 >>a copy of all e-mail to or from the specified mailbox?


wiretap is a weapon in the FBI's armoury

in the US, YOU have the right to bear arms

You should demand the constitutional right to wiretap the FBI and CIA and so

on right now.

that will fix things.

j.



From owner-ietf-outbound  Fri Jul 14 07:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA27777
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 07:50:04 -0400 (EDT)
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27335
	for <ietf@ietf.org>; Fri, 14 Jul 2000 07:48:45 -0400 (EDT)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate3.mot.com (motgate3 2.1) with ESMTP id EAA17614 for <ietf@ietf.org>; Fri, 14 Jul 2000 04:47:19 -0700 (MST)]
Received: [from relay1.cig.mot.com (relay1.cig.mot.com [136.182.15.23]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id EAA17942 for <ietf@ietf.org>; Fri, 14 Jul 2000 04:48:32 -0700 (MST)]
Received: from philneumillerhm ([192.172.1.49]) by relay1.cig.mot.com (8.8.8+Sun/SCERG-RELAY-1.11b) with SMTP id GAA28721; Fri, 14 Jul 2000 06:48:20 -0500 (CDT)
Message-ID: <002601bfed89$bb787780$3101acc0@philneumillerhm>
From: "Phil Neumiller" <neumille@cig.mot.com>
To: "Jon Crowcroft" <J.Crowcroft@CS.UCL.AC.UK>
Cc: <ietf@ietf.org>
References: <6821.963572591@cs.ucl.ac.uk>
Subject: Re: Email Privacy eating software
Date: Fri, 14 Jul 2000 06:50:32 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I like this idea!  Yeah, if we can reclassify black boxes as munitions, as
the NSA has
done to encryption for years, then we can claim that we have the "right to
bear black
boxes".

This is great!


----- Original Message -----
From: "Jon Crowcroft" <J.Crowcroft@cs.ucl.ac.uk>
To: "Anthony Atkielski" <anthony@atkielski.com>
Cc: "ietf" <ietf@ietf.org>
Sent: Friday, July 14, 2000 6:03 AM
Subject: Re: Email Privacy eating software


>
> In message <01dc01bfed78$0e7a55a0$0a00000a@contactdish>, Anthony Atkielski
type
> d:
>
>  >>I don't understand why the FBI feels that it needs to have a top-secret
>  >>black box attached to the ISP's network.  Why not just have the ISP
provide
>  >>a copy of all e-mail to or from the specified mailbox?
>
>
> wiretap is a weapon in the FBI's armoury
>
> in the US, YOU have the right to bear arms
>
> You should demand the constitutional right to wiretap the FBI and CIA and
so
> on right now.
>
> that will fix things.
>
> j.
>
>



From owner-ietf-outbound  Fri Jul 14 08:10:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA04783
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 08:10:04 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA01492
	for <ietf@ietf.org>; Fri, 14 Jul 2000 08:00:33 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.28705-0@bells.cs.ucl.ac.uk>; Fri, 14 Jul 2000 13:00:26 +0100
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
cc: ietf <ietf@ietf.org>
Subject: Re: Email Privacy eating software
In-reply-to: Your message of "Fri, 14 Jul 2000 12:33:19 BST." <71C4C55F198BD211B24F0000F842F15807ED9CD9@reoexc6.reo.cpqcorp.net>
Date: Fri, 14 Jul 2000 13:00:25 +0100
Message-ID: <10846.963576025@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <71C4C55F198BD211B24F0000F842F15807ED9CD9@reoexc6.reo.cpqcorp.net>, 
"Parkinson, Jonathan" typed:

 >>In the UK we have the same type of problem, this time from my Favorite
 >>Company MI5.

I agree.
i also think that there are important lessons for lawmakers in other countries,
so it is a suitable subject for IETF discussion.

 >>'The UK is leading the world when it comes to high-tech spying on its
 >>citizens'
 >>Please see
 >>http://news6.thdo.bbc.co.uk/hi/english/sci/tech/newsid_762000/762514.stm=

yes, this is something that the UK should be ashamed of  - there is
very good documentary evidence that the government is ignoring
technical advice on the costs ot the ISP community in terms of
implementing this they wayu that the UK law was designed, or the risks
to citizens, and the loss of revenue when content and application
providers move their business to palecs which implement less stupid,
expensive and ineffective ways to intercept criminal or terrorist 
communication - the home offices response to criticism was a
masterpiece of political rubbish, and included specific items which
were lies.  examples include assertions about what other coutnries
were doing in terms of techniocal implementations of both intercept,
and who gets charged for the implementation cost.

 >>Lets face it, internet service providers will be forced to install =
 >>black
 >>boxes in their=20
 >>data centres that connect directly to an MI5 monitoring centre in =
 >>London.
 >>Now that would=20
 >>be nice to hack into. =20

when it happens, it will be a good day for demoracy.

one trick to do is to put a bunch of fake data on the net whch causes them
to either act on it, or have to randiomize whether they act or not
(see cryptonomicon) so that real miscreants wont be able to tell they
are listening (fairly standard stuff in fact) - turns out that there
are several ways to put in place random traffic generators (which even
more interestingly can also be part of billing systems) that run 
counter-intuitive, but make it very hard to do RIP but do allow one to
retain privacy.....

 >>More to the point, Who is going to fund this? 'thinking' Oh yes thats =
 >>why
 >>Petrol in the=20
 >>UK has now passed the =A31.03 per litre barrier.
 >>'http://www.rip-off.co.uk/fuel.htm'=20

 >>:-)

right - but in that case, we can take public transport or buy a bike -
in the case of ecommerce, it can go elsewhere and the UK loses.

note that a lot of the GRID users are talking about striping data over
multiple paths (yes, and at 1.2Gbps per path) so the data copy costs
of intercept are more than double the data transfer  - in fact they
would be just with normal dynamic routing

the reason the UK bill is confused is that it was written by
telephants - people who probably lost their jobs as the tradditonal
phone business goes marginal and now advise shady organisations such
as gchq - these folks understand that the Exchange in the PSTN is the
natuaral point for billing and is therefore also quite a reasnable
palce to do intercept 

what they dont get is that there is no natural point to do this in a
packet net, least of all a datagram, end to end network, except at the
end points.....


what annoys me is that the UK government has persistnytly caimed that
ALL opponents  of the bill oppose intercept, when in fact almost all
the ones I've spoken to object to a STUPID pointless waste of money,
not to intercept at feasiable (E.g. end systems - such as email
servers, web, web cachce/proxy, napster server etc) points....

 >>-----Original Message-----
 >>From: Jon Crowcroft [mailto:J.Crowcroft@cs.ucl.ac.uk]
 >>Sent: Friday, July 14, 2000 12:03 PM
 >>To: Anthony Atkielski
 >>Cc: ietf
 >>Subject: Re: Email Privacy eating software
 >>
 >>
 >>
 >>In message <01dc01bfed78$0e7a55a0$0a00000a@contactdish>, Anthony =
 >>Atkielski
 >>type
 >>d:
 >>
 >> >>I don't understand why the FBI feels that it needs to have a =
 >>top-secret
 >> >>black box attached to the ISP's network.  Why not just have the ISP
 >>provide
 >> >>a copy of all e-mail to or from the specified mailbox?
 >>
 >>
 >>wiretap is a weapon in the FBI's armoury
 >>
 >>in the US, YOU have the right to bear arms
 >>
 >>You should demand the constitutional right to wiretap the FBI and CIA =
 >>and so
 >>
 >>on right now.
 >>
 >>that will fix things.
 >>
 >>j.

 cheers

   jon



From owner-ietf-outbound  Fri Jul 14 08:40:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA12520
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 08:40:02 -0400 (EDT)
Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11315
	for <ietf@ietf.org>; Fri, 14 Jul 2000 08:35:20 -0400 (EDT)
Received: from dell-desktop.GigaLaw.com (user-1054hsm.dsl.mindspring.com [64.82.71.150])
	by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id IAA26957
	for <ietf@ietf.org>; Fri, 14 Jul 2000 08:35:19 -0400 (EDT)
Message-Id: <4.3.1.0.20000714083151.02fd3100@209.81.50.25>
X-Sender: isenberg@209.81.50.25
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 14 Jul 2000 08:33:30 -0400
To: ietf <ietf@ietf.org>
From: Doug Isenberg <disenberg@GigaLaw.com>
Subject: Re: Email Privacy eating software
In-Reply-To: <10846.963576025@cs.ucl.ac.uk>
References: <Your message of "Fri, 14 Jul 2000 12:33:19 BST." <71C4C55F198BD211B24F0000F842F15807ED9CD9@reoexc6.reo.cpqcorp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

         From today's Wall Street Journal 
(http://interactive.wsj.com/articles/SB963523417716552926.htm):

One of the nation's largest Internet-service providers, Earthlink Inc., has 
refused to install a new Federal Bureau of Investigation electronic 
surveillance device on its network, saying technical adjustments required 
to use the device caused disruptions for customers.

The FBI has used Carnivore, as the surveillance device is called, in a 
number of criminal investigations. But EarthLink is the first ISP to offer 
a public account of an actual experience with Carnivore. The FBI has 
claimed that Carnivore won't interfere with an ISP's operations....

=======================
Douglas M. Isenberg
Attorney @ Law
Editor & Publisher, GigaLaw.com
Legal columnist, Internet World magazine
=======================
GigaLaw.com: "Legal Information for
Internet and Technology Professionals"
http://www.GigaLaw.com
=======================



From owner-ietf-outbound  Fri Jul 14 09:30:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA24677
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 09:30:02 -0400 (EDT)
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23547
	for <ietf@ietf.org>; Fri, 14 Jul 2000 09:24:04 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-green.research.att.com (Postfix) with ESMTP
	id 05E511E037; Fri, 14 Jul 2000 09:24:05 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id JAA22228;
	Fri, 14 Jul 2000 09:24:04 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id B9DCB35DC2; Fri, 14 Jul 2000 09:23:29 -0400 (EDT)
X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.3 #1[UCI]
From: "Steven M. Bellovin" <smb@research.att.com>
To: Doug Isenberg <disenberg@gigalaw.com>
Cc: ietf <ietf@ietf.org>
Subject: Re: Email Privacy eating software 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 14 Jul 2000 09:23:29 -0400
Sender: smb@research.att.com
Message-Id: <20000714132329.B9DCB35DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <4.3.1.0.20000714083151.02fd3100@209.81.50.25>, Doug Isenberg writes
:
>         From today's Wall Street Journal 
>(http://interactive.wsj.com/articles/SB963523417716552926.htm):
>
>One of the nation's largest Internet-service providers, Earthlink Inc., has 
>refused to install a new Federal Bureau of Investigation electronic 
>surveillance device on its network, saying technical adjustments required 
>to use the device caused disruptions for customers.
>
>The FBI has used Carnivore, as the surveillance device is called, in a 
>number of criminal investigations. But EarthLink is the first ISP to offer 
>a public account of an actual experience with Carnivore. The FBI has 
>claimed that Carnivore won't interfere with an ISP's operations....

One can draw some interesting conclusions from that article, though 
firm technical details from the FBI would be welcome.

First -- the box was placed at the remote access servers, and is -- 
according to the article -- capable of monitoring email and other 
network traffic.  Earthlink claims that the box was incompatible with 
the software version of the server they were running, and says that 
they had to downgrade to an older, buggy version, which crashed, 
causing a denial of service.  The FBI, in turn, says that their box is 
purely passive, so it can't affect the net.

My suspicion is that the box wants to monitor traffic based on IP 
address, and not just email headers.  To do that, it needs to know 
when the suspect has dialed in, and what his/her IP address is.  That, 
in turn, would likely require monitoring of the RADIUS traffic, which 
(if it were different from release to release) might have forced the 
downgrade.

		--Steve Bellovin




From owner-ietf-outbound  Fri Jul 14 10:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA11685
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 10:30:03 -0400 (EDT)
Received: from svanekaer.dk (slowboat.svanekaer.dk [129.142.164.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA07252
	for <ietf@ietf.org>; Fri, 14 Jul 2000 10:13:35 -0400 (EDT)
Received: (qmail 36416 invoked by uid 1011); 14 Jul 2000 14:13:35 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 14 Jul 2000 14:13:35 -0000
Date: Fri, 14 Jul 2000 16:13:35 +0200 (CEST)
From: Steven Cotton <steven@cotton.dk>
X-Sender: steven@localhost
To: ietf <ietf@ietf.org>
Subject: Re: Email Privacy eating software 
In-Reply-To: <20000714132329.B9DCB35DC2@smb.research.att.com>
Message-ID: <Pine.BSF.4.21.0007141558550.35758-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Fri, 14 Jul 2000, Steven M. Bellovin wrote:

> That, in turn, would likely require monitoring of the RADIUS traffic,
> which (if it were different from release to release) might have forced
> the downgrade.

RADIUS logfiles provide lots of interesting information. They'll know your
dial-up habits, phone number, length of time connected etc. The FBI should
just start their own ISP.

-- 
steven




From owner-ietf-outbound  Fri Jul 14 10:41:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA14318
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 10:40:03 -0400 (EDT)
Received: from ogma.cisco.com (ogma.cisco.com [144.254.74.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14014
	for <ietf@ietf.org>; Fri, 14 Jul 2000 10:38:59 -0400 (EDT)
Received: from nordic.cisco.com (nordic.cisco.com [144.254.116.14])
	by ogma.cisco.com (Postfix) with ESMTP
	id C5345189; Fri, 14 Jul 2000 16:38:29 +0200 (MET DST)
Received: from [10.0.0.7] ([171.70.221.22])
	by nordic.cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA29472;
	Fri, 14 Jul 2000 16:38:25 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: pfaltstr@nordic.cisco.com
Message-Id: <p0432040cb594d459c18b@[10.0.0.7]>
In-Reply-To: <20000714000435.C31745@off.org>
References: <200007132144.e6DLi2l08298@calcite.rhyolite.com>
 <Pine.GSO.4.21.0007132322480.29318-100000@petra.ee.surrey.ac.uk>
 <20000714000435.C31745@off.org>
Date: Fri, 14 Jul 2000 07:35:34 -0700
To: Austin Schutz <tex@gblx.net>, Lloyd Wood <l.wood@eim.surrey.ac.uk>
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>
Subject: Re: precedence field and mailing lists
Cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 00.04 -0700 00-07-14, Austin Schutz wrote:
>  > I sent mail to a mailing list. Not to you. Your autoreply software
>  > should only reply to mail explicitly To: or Cc: you.
>
>	This breaks for mail aliases. Perhaps, if you are root on
>a unix machine, you might want someone sending mail to that address
>to know you are away?

Not at all. You tell your favorite vacation software what aliases it 
should reply to. If you have a unix system, see the manual page for 
vacation. This after of course having the mail to root go to your 
private mailbox.

Example:

# cat .forward
\paf,"| vacation -a root@example.net -u paf"
# uname -a
SunOS nix 5.5.1 Generic_103640-24 sun4m sparc SUNW,SPARCstation-20
# man vacation
Reformatting page.  Wait... done



vacation(1)               User Commands               vacation(1)



NAME
      vacation - reply to mail automatically

SYNOPSIS
      vacation [ -I ]
      vacation [ -j ] [ -a alias ] [ -tN ] username
:
:
:
      -a alias   Indicate that alias is one of the  valid  aliases
                for  the  user  running  vacation,  so  that  mail
                addressed to that alias generates a reply.
:
:
:


    paf



From owner-ietf-outbound  Fri Jul 14 11:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA24195
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 11:10:02 -0400 (EDT)
Received: from apollo.dmnews.com (gw.dmnews.com [204.141.161.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21689
	for <ietf@ietf.org>; Fri, 14 Jul 2000 11:01:57 -0400 (EDT)
Received: by APOLLO with Internet Mail Service (5.5.2650.10)
	id <M8X8KPC0>; Fri, 14 Jul 2000 11:09:56 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE3023F7@APOLLO>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re. Email Privacy eating software
Date: Fri, 14 Jul 2000 11:09:54 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

The 'saga' continues... Read Janet Reno's input in all this.
"Reno: Web 'Wiretap' Review Underway" by AP:
http://wire.ap.org/APnews/?SITE=NYTRO&FRONTID=HOME

Looks like the feds are developing a real "love affair" for the electronic
mail.
"White House Is Retrieving E-Mails" by AP:
http://wire.ap.org/APnews/?SITE=VTRUT&FRONTID=HOME

>Jon Crowfort wrote:

>"the reason the UK bill is confused is that it was written by
>telephants - people who probably lost their jobs as the tradditonal
>phone business goes marginal..."

I've been wondering what to call them but you came up with the perfect name!
Telephants!
Pease note they do not all exist only in the UK or US but all over the World
and there are a lot more 'telephants' out there today than technically apt
(call them 'Digiphants'?) people. I think it goes not only by knowledge but
acceptance or attitude toward the new changes IT brings to the World, one of
which is refining old boundaries.
Most of the poiticians, lawmakers and even law enforcers - especially in
higher levels - still believe the 'old ways' - or so they say. Problem is
you can not govern or rule something you don't understand - and they are way
high up in the ranks already to just go and ask questions. That is how some
of the dumbest laws and 'actions' were even born (remember the "Exxon law"?
How about the german judge at CompuServe in 1995?) 
My point in all this is - we need the gov't but it has to be the gov' we
need in these days and time. They should not scan emails of their citizens
unless they have a good reason and especially a court issued warrant to do
so. Imagine the police blocing off an entire block and search every house,
building, apartment because they 'think' that there might be a criminal
activity in one of them?
The new technologies, the Internet and the ease of communication now is
re-defining the boundaries the World used to live by. Old boundaries are
going to be gone, and new ones defined. This is the time law and law
enforcement is re-defining it's boudaries as well and we have to watch where
those boundaries are going to be - or else we can end up in a system where
we will only read about freedom in story books or worse yet just whisper
about it when no one can hear. A lot depends on us now - history is still in
the making.

Cheers and have a good weekend everybody,

Lillian

Lillian Komlossy || Site Manager || http://www.dmnews.com ||
http://www.imarketingnews.com || 212 925-7300 ext. 232 ||
mailto:lillian@dmnews.com



From owner-ietf-outbound  Fri Jul 14 11:20:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA27899
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 11:20:02 -0400 (EDT)
Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22375
	for <ietf@ietf.org>; Fri, 14 Jul 2000 11:04:40 -0400 (EDT)
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 KAA05413
	for <ietf@ietf.org>; Fri, 14 Jul 2000 10:04:36 -0500 (CDT)
	(envelope-from salo@us.networkcs.com)
Received: (from salo@localhost)
	by us.networkcs.com (8.9.2/8.9.2) id KAA54785
	for ietf@ietf.org; Fri, 14 Jul 2000 10:04:35 -0500 (CDT)
	(envelope-from salo)
Date: Fri, 14 Jul 2000 10:04:35 -0500 (CDT)
From: Tim Salo <salo@networkcs.com>
Message-Id: <200007141504.KAA54785@us.networkcs.com>
To: ietf@ietf.org
Subject: Re: Email Privacy eating software
In-Reply-To: <Pine.BSF.4.21.0007141558550.35758-100000@localhost>
X-Loop: ietf@ietf.org

> Date: Fri, 14 Jul 2000 16:13:35 +0200 (CEST)
> From: Steven Cotton <steven@COTTON.DK>
> Subject: Re: Email Privacy eating software 
> 
> On Fri, 14 Jul 2000, Steven M. Bellovin wrote:
> 
> > That, in turn, would likely require monitoring of the RADIUS traffic,
> > which (if it were different from release to release) might have forced
> > the downgrade.
> 
> RADIUS logfiles provide lots of interesting information. They'll know your
> dial-up habits, phone number, length of time connected etc. The FBI should
> just start their own ISP.

How do you know "they" (whoever "they" might be) haven't?

-tjs



From owner-ietf-outbound  Fri Jul 14 11:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA01569
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 11:30:04 -0400 (EDT)
Received: from apollo.dmnews.com (gw.dmnews.com [204.141.161.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22685
	for <ietf@ietf.org>; Fri, 14 Jul 2000 11:05:42 -0400 (EDT)
Received: by APOLLO with Internet Mail Service (5.5.2650.10)
	id <M8X8KPDS>; Fri, 14 Jul 2000 11:13:41 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE3023F8@APOLLO>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'Steven Cotton'" <steven@cotton.dk>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Email Privacy eating software 
Date: Fri, 14 Jul 2000 11:13:40 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain;
	charset="windows-1252"
X-Loop: ietf@ietf.org


-----Original Message-----
From: Steven Cotton [mailto:steven@cotton.dk]
Sent: Friday, July 14, 2000 10:14 AM
To: ietf
Subject: Re: Email Privacy eating software 


On Fri, 14 Jul 2000, Steven M. Bellovin wrote:

>> That, in turn, would likely require monitoring of the RADIUS traffic,
>> which (if it were different from release to release) might have forced
>> the downgrade.

>RADIUS logfiles provide lots of interesting information. They'll know your
>dial-up habits, phone number, length of time connected etc. The FBI should
>just start their own ISP.

What a scary thought! Maybe then they would not need to scan email - they
could just tell us what to write.

Cheers,

~L



From owner-ietf-outbound  Fri Jul 14 11:40:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA05269
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 11:40:05 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23361
	for <ietf@ietf.org>; Fri, 14 Jul 2000 11:07:43 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id LAA27008;
	Fri, 14 Jul 2000 11:06:37 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: "'Randy Bush'" <randy@psg.com>
Cc: <ietf@ietf.org>
Subject: RE: IP service definition
Date: Fri, 14 Jul 2000 11:06:36 -0400
Message-ID: <009401bfeda5$1b6bce60$d001010a@tst.ennovatenetworks.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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <E13Cwa3-0001CW-00@roam.psg.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


> -----Original Message-----
> From: Randy Bush [mailto:randy@psg.com]

> > It is akin to standardizing on what kind of light can come in your
> > neighbourhood.
>
> properly done, and with no adjectives or judgement spin, it could be
a
> taxonomy of what kinds of light are known.  this might be
> useful, witness
> a recent discussion re wap of what is being on the internet.

Hi Randy,

Yes - both AOL and WAP aren't IP solutions in true sense, but both are
unqualified commercial success for the organizations promoting them.
Yes, you can go ahead and blame AOL and WAP forum for them but who
would you blame for creating NAT. NAT is no less offender of the end
to end design paradigm, than WAP and AOL. Why criticize WAP forum if
it decided not to hide wireless devices behind NAT boxes.

After hearing Java and Windows on every device, I am hearing NAT and
BGP for every thing from some vendors. Who is controlling these
standards - is it IETF. Or it is OK to do any thing as long as your
implementation gets published as an I-D or RFC (in that case AOL and
WAP forums should perhaps publish their specs as RFCs). Hear..hear..

Cheers,

--brijesh
(personal views only)



From owner-ietf-outbound  Fri Jul 14 12:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA12427
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 12:00:02 -0400 (EDT)
Received: from svanekaer.dk (slowboat.svanekaer.dk [129.142.164.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA05771
	for <ietf@ietf.org>; Fri, 14 Jul 2000 11:41:03 -0400 (EDT)
Received: (qmail 36799 invoked by uid 1011); 14 Jul 2000 15:40:59 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 14 Jul 2000 15:40:59 -0000
Date: Fri, 14 Jul 2000 17:40:59 +0200 (CEST)
From: Steven Cotton <steven@cotton.dk>
X-Sender: steven@localhost
To: ietf@ietf.org
Subject: Re: Email Privacy eating software
In-Reply-To: <200007141504.KAA54785@us.networkcs.com>
Message-ID: <Pine.BSF.4.21.0007141740090.35758-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Fri, 14 Jul 2000, Tim Salo wrote:

> > RADIUS logfiles provide lots of interesting information. They'll know your
> > dial-up habits, phone number, length of time connected etc. The FBI should
> > just start their own ISP.
> 
> How do you know "they" (whoever "they" might be) haven't?

Ooh, the paranoia :)

-- 
steven




From owner-ietf-outbound  Fri Jul 14 12:50:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA28685
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 12:50:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26955
	for <ietf@ietf.org>; Fri, 14 Jul 2000 12:43:47 -0400 (EDT)
Received: from contactdish (atkielsk.adsl-net2-rg.nerim.net [62.4.19.136]) by atkielski.com (8.8.8) id SAA68663; Fri, 14 Jul 2000 18:43:47 +0200 (CEST)
Message-ID: <007e01bfedb2$ae6242a0$0a00000a@contactdish>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <200007141504.KAA54785@us.networkcs.com>
Subject: Re: Email Privacy eating software
Date: Fri, 14 Jul 2000 18:43:29 +0200
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
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> How do you know "they" (whoever "they" might be) haven't?

Because they don't know how.  And we know that they don't know how because
they are still setting up stupid things like Carnivore.



From owner-ietf-outbound  Fri Jul 14 13:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA10303
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 13:30:03 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08261
	for <ietf@ietf.org>; Fri, 14 Jul 2000 13:24:00 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@localhost [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta4/8.11.0.Beta4) with ESMTP id e6EHNfn26088;
	Fri, 14 Jul 2000 13:23:42 -0400
Message-Id: <200007141723.e6EHNfn26088@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: ietf@ietf.org
Subject: Re: Email Privacy eating software 
In-Reply-To: Your message of "Fri, 14 Jul 2000 18:43:29 +0200."
             <007e01bfedb2$ae6242a0$0a00000a@contactdish> 
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: <200007141504.KAA54785@us.networkcs.com>
            <007e01bfedb2$ae6242a0$0a00000a@contactdish>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1324791880P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 14 Jul 2000 13:23:38 -0400
X-Loop: ietf@ietf.org

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

On Fri, 14 Jul 2000 18:43:29 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
> > How do you know "they" (whoever "they" might be) haven't?
> 
> Because they don't know how.  And we know that they don't know how because
> they are still setting up stupid things like Carnivore.

It has long been a well-known fact that to excel in slapstick comedy requires
incredible agility, strength, and flexibility....

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOW9MmnAt5Vm009ewEQIPjACgwKrgl4aGrmostAPgCJMddI+BoFAAoIM4
M5CyfZWJ7f29sd50EkYeP/N6
=8++F
-----END PGP SIGNATURE-----

--==_Exmh_-1324791880P--



From owner-ietf-outbound  Fri Jul 14 14:00:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA21429
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 14:00:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21212
	for <ietf@ietf.org>; Fri, 14 Jul 2000 13:59:23 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA26559;
        Fri, 14 Jul 2000 13:59:17 -0400 (EDT)
Message-Id: <200007141759.NAA26559@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Austin Schutz <tex@gblx.net>
cc: Lloyd Wood <l.wood@eim.surrey.ac.uk>,
        Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: precedence field and mailing lists 
In-reply-to: Your message of "Fri, 14 Jul 2000 00:04:35 PDT."
             <20000714000435.C31745@off.org> 
Date: Fri, 14 Jul 2000 13:59:16 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > I sent mail to a mailing list. Not to you. Your autoreply software
> > should only reply to mail explicitly To: or Cc: you.
> 
>         This breaks for mail aliases.

not if you tell your vacation program which mail aliases are yours.



There was once another draft proposal by Jacob Palme for an auto-submitted
header field, which would allow you to label a message either

auto-submitted (a message automatically generated not in response to any input)
auto-forwarded (such as a message from a mailing list)
auto-replied (an automatic reply to a message)
not-auto-submitted

...but it got bogged down somewhere.  I'd very much like to see 
this go forward - it solves the vacation problem quite neatly,
(just don't reply to any message that is either auto-submitted,
auto-forwarded, or auto-replied) and unlike Precedence, seems 
technically sound.

the idea is borrowed from X.400, but we shouldn't hold that against it. :)

a variant of this header (spelled differently) is defined in RFC 2156.

Keith



From owner-ietf-outbound  Fri Jul 14 20:52:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA29286
	for ietf-outbound.10@ietf.org; Fri, 14 Jul 2000 20:50:03 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28102
	for <ietf@ietf.org>; Fri, 14 Jul 2000 20:44:37 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007150043.JAA01994@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id JAA01994; Sat, 15 Jul 2000 09:42:50 +0859
Subject: Re: IP service definition
In-Reply-To: <009401bfeda5$1b6bce60$d001010a@tst.ennovatenetworks.com> from Brijesh
 Kumar at "Jul 14, 2000 11:06:36 am"
To: bkumar@ennovatenetworks.com
Date: Sat, 15 Jul 2000 09:42:49 +0859 ()
CC: "'Randy Bush'" <randy@psg.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Brijesh;

> NAT is no less offender of the end
> to end design paradigm, than WAP and AOL.

Of course.

Who said otherwise?

							Masataka Ohta



From owner-ietf-outbound  Sun Jul 16 01:37:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA21194
	for ietf-outbound.10@ietf.org; Sun, 16 Jul 2000 01:30:05 -0400 (EDT)
Received: from net.batm.co.il ([212.29.220.190])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15557
	for <ietf@ietf.org>; Sun, 16 Jul 2000 01:20:50 -0400 (EDT)
Received: from moshnt (MOSH_NT [212.29.220.134]) by net.batm.co.il with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id 36DP61HX; Sun, 16 Jul 2000 08:18:35 +0200
From: "Moshe Aharon" <mosh@batm.co.il>
To: <ietf@ietf.org>
Subject: Layer 3 Security for ISP applications
Date: Sun, 16 Jul 2000 08:18:49 +0200
Message-ID: <NEBBJMPLOKLHBCBMHKJPKEAHCBAA.mosh@batm.co.il>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0151_01BFEEFE.78397AC0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0151_01BFEEFE.78397AC0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: 7bit

Sorry, the last email had no subject field ...


Greetings,

Please let me know if this question is not suitable for this forum, and if
so, can you point me where to try.

I'm conducting a research which refers to new ISP infrastructures.
ISP's today start offering new layer 2 access to the home (Ethernet, Cable).

What is recommended for implementing security over these undedicated
connections?

I guess Authentication and security must go up to layer 3 ... which means
all applications
must use at least Layer 3 aware routing switches.

Is there a way to establish PPP Authentication over these layer 2
infrastructure?
(Resembling the common ISP application with dial up access servers)

Thanks in advance,
Moshe



------=_NextPart_000_0151_01BFEEFE.78397AC0
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1255" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial>
<DIV><FONT face=3DArial>
<DIV><FONT color=3D#000080 face=3DArial><SPAN =
class=3D535131914-12072000><SPAN=20
class=3D953481706-16072000>Sorry, the last email had no subject field=20
...</SPAN></SPAN></FONT></DIV>
<DIV><FONT color=3D#000080 face=3DArial><SPAN =
class=3D535131914-12072000><SPAN=20
class=3D953481706-16072000></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><SPAN =
class=3D535131914-12072000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000080 face=3DArial><SPAN=20
class=3D535131914-12072000>Greetings,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial><SPAN =
class=3D535131914-12072000></SPAN></FONT><FONT=20
color=3D#000080>&nbsp;</FONT></DIV>
<DIV><FONT color=3D#000080 face=3D"ARIAL (HEBREW)"><SPAN=20
class=3D535131914-12072000>Please let me know if this question is not =
suitable for=20
this forum, and if so,&nbsp;can you point me where to =
try.</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#000080 face=3DArial><SPAN =
class=3D535131914-12072000>I'm=20
conducting a research which refers to&nbsp;new ISP=20
infrastructures.</SPAN></FONT></DIV>
<DIV><FONT color=3D#000080 face=3D"ARIAL (HEBREW)"><SPAN=20
class=3D535131914-12072000>ISP's today start offering new layer 2 access =
to the=20
home (Ethernet, Cable).</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#000080 face=3DArial><SPAN =
class=3D535131914-12072000>What is=20
recommended for implementing security over these undedicated=20
connections?</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#000080 face=3D"ARIAL (HEBREW)"><SPAN =
class=3D535131914-12072000>I=20
guess Authentication and security must go up to layer 3 ... which means =
all=20
applications</SPAN></FONT></DIV>
<DIV><FONT color=3D#000080 face=3D"ARIAL (HEBREW)"><SPAN=20
class=3D535131914-12072000>must use at least Layer 3 aware routing=20
switches.</SPAN></FONT></DIV>
<DIV><FONT face=3D"ARIAL (HEBREW)"><SPAN=20
class=3D535131914-12072000></SPAN></FONT><FONT =
color=3D#000080>&nbsp;</FONT></DIV>
<DIV><FONT color=3D#000080 face=3D"Arial (Hebrew)"><SPAN =
class=3D535131914-12072000>Is=20
there a way to establish PPP Authentication over these layer 2=20
infrastructure?</SPAN></FONT></DIV>
<DIV><FONT color=3D#000080 face=3D"Arial (Hebrew)"><SPAN=20
class=3D535131914-12072000>(Resembling the&nbsp;common ISP application =
with dial=20
up access servers)</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#000080 face=3DArial><SPAN =
class=3D535131914-12072000>Thanks in=20
advance,</SPAN></FONT></DIV>
<DIV><FONT color=3D#000080 face=3DArial><SPAN=20
class=3D535131914-12072000>Moshe</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV></FONT></DIV></FONT></DIV>
<DIV><FONT face=3D"Arial (Hebrew)" size=3D2></DIV></FONT>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0151_01BFEEFE.78397AC0--



From owner-ietf-outbound  Sun Jul 16 17:03:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA23084
	for ietf-outbound.10@ietf.org; Sun, 16 Jul 2000 17:00:02 -0400 (EDT)
Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16735
	for <ietf@ietf.org>; Sun, 16 Jul 2000 16:30:26 -0400 (EDT)
Received: from [62.7.3.50] (helo=salavat)
	by tungsten.btinternet.com with esmtp (Exim 3.03 #83)
	id 13Dv3S-0000KM-00
	for ietf@ietf.org; Sun, 16 Jul 2000 21:30:26 +0100
Message-ID: <000601bfef64$d1cffc60$3203073e@salavat>
From: "Salavat R. Magazov" <srm4@ukc.ac.uk>
To: "IETF mailing list" <ietf@ietf.org>
Subject: Security standarts
Date: Sat, 15 Jul 2000 09:54:31 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_001A_01BFEE42.AC13E360"
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
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_001A_01BFEE42.AC13E360
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit

I have seen somebody's e-mail asking for any standards in cryptographic
algorithms. I have the chapter from "Handbook of Applied Cryptography"
describing the issue. If you still need it let me know.

Salavat

------=_NextPart_000_001A_01BFEE42.AC13E360
Content-Type: text/x-vcard;
	name="Salavat R. Magazov.vcf"
Content-Disposition: attachment;
	filename="Salavat R. Magazov.vcf"
Content-Transfer-Encoding: 7bit

BEGIN:VCARD
VERSION:2.1
N:Magazov;Salavat;R.
FN:Salavat R. Magazov
NICKNAME:Sal
ORG:University of Kent at Canterbury
TEL;HOME;VOICE:+44-1227-472835
X-WAB-GENDER:2
BDAY:20000517
EMAIL;PREF;INTERNET:srm4@ukc.ac.uk
EMAIL;INTERNET:salavat@ukonline.co.uk
REV:20000715T085431Z
END:VCARD

------=_NextPart_000_001A_01BFEE42.AC13E360--



From owner-ietf-outbound  Mon Jul 17 10:21:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA28042
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 10:20:03 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25272
	for <ietf@ietf.org>; Mon, 17 Jul 2000 10:14:18 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id KAA17151
	for <ietf@ietf.org>; Mon, 17 Jul 2000 10:15:07 -0400
Sender: francis@localhost.localdomain
Message-ID: <397314EA.E2D506C1@ecal.com>
Date: Mon, 17 Jul 2000 10:15:07 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Email Privacy eating software
References: <6821.963572591@cs.ucl.ac.uk> <002601bfed89$bb787780$3101acc0@philneumillerhm>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Phil Neumiller wrote:

> I like this idea!  Yeah, if we can reclassify black boxes as munitions, as
> the NSA has
> done to encryption for years, then we can claim that we have the "right to
> bear black
> boxes".

...just like we have the right to own nuclear weapons.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |You buttered your bread, now lie in it.      |
|francis@ecal.com|                                             |
\==============================================================/





From owner-ietf-outbound  Mon Jul 17 11:01:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA15988
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 11:00:03 -0400 (EDT)
Received: from dragonfly.ncdragonfly.com (dragonfly.ncdragonfly.com [209.137.27.201])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11948
	for <ietf@ietf.org>; Mon, 17 Jul 2000 10:50:58 -0400 (EDT)
Received: from HDAHTS66001 (209.137.27.230 [209.137.27.230]) by dragonfly.ncdragonfly.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3)
	id LDTWSAJF; Mon, 17 Jul 2000 11:03:18 -0400
Reply-To: <dahigginbotham@ncdragonfly.com>
From: "David A. Higginbotham" <dahigginbotham@ncdragonfly.com>
To: <ietf@ietf.org>
Subject: RE: Email Privacy eating software
Date: Mon, 17 Jul 2000 10:53:50 -0400
Message-ID: <BB2831D3689AD211B14C00104B14623B1E7632@HAZEN04>
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.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

we have the right to own anything we can dream up and build, we do not
always have the right to use it for its intended purpose

-----Original Message-----
From: francis@localhost.localdomain
[mailto:francis@localhost.localdomain]On Behalf Of John Stracke
Sent: Monday, July 17, 2000 10:15 AM
To: ietf@ietf.org
Subject: Re: Email Privacy eating software


Phil Neumiller wrote:

> I like this idea!  Yeah, if we can reclassify black boxes as munitions, as
> the NSA has
> done to encryption for years, then we can claim that we have the "right to
> bear black
> boxes".

...just like we have the right to own nuclear weapons.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |You buttered your bread, now lie in it.      |
|francis@ecal.com|                                             |
\==============================================================/




From owner-ietf-outbound  Mon Jul 17 13:21:46 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA08181
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 13:20:03 -0400 (EDT)
Received: from doberman.cwusa.com (doberman-dmz.cwusa.com [146.135.88.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26079
	for <ietf@ietf.org>; Mon, 17 Jul 2000 12:45:24 -0400 (EDT)
Received: from us-cwi-exc-a10.cwusa.com (us-cwi-exc-a10.cwusa.com [146.135.85.143])
	by doberman.cwusa.com (8.9.1/8.9.1) with ESMTP id MAA17291;
	Mon, 17 Jul 2000 12:44:41 -0400 (EDT)
Received: by us-cwi-exc-a10.cwi.cablew.com with Internet Mail Service (5.5.2650.21)
	id <PD3PA18P>; Mon, 17 Jul 2000 12:44:36 -0400
Message-ID: <F685A00DB7B4D111B2400020AFFC2D580D702FAA@us-cwi-exc-a03.cwi.cablew.com>
From: "Book, Robert" <Robert.BookIII@cwusa.com>
To: "'dahigginbotham@ncdragonfly.com'" <dahigginbotham@ncdragonfly.com>,
        ietf@ietf.org
Subject: RE: Email Privacy eating software
Date: Mon, 17 Jul 2000 12:44:34 -0400
Return-Receipt-To: "Book, Robert" <Robert.BookIII@cwusa.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Hmmm, I think the federal government might have another opinion that topic,
re: Waco, etc., but this is far off the topic. It's an idyllic viewpoint,
though. But I'm afraid we're at the point in history where the phrase "a
life of freedom in the United States" is an oxymoron. And, if Carnivore
isn't as clear an example of that as one needs, then one is probably wearing
rose-colored glasses.

-----Original Message-----
From: David A. Higginbotham [mailto:dahigginbotham@ncdragonfly.com]
Sent: Monday, July 17, 2000 10:54 AM
To: ietf@ietf.org
Subject: RE: Email Privacy eating software


we have the right to own anything we can dream up and build, we do not
always have the right to use it for its intended purpose

-----Original Message-----
From: francis@localhost.localdomain
[mailto:francis@localhost.localdomain]On Behalf Of John Stracke
Sent: Monday, July 17, 2000 10:15 AM
To: ietf@ietf.org
Subject: Re: Email Privacy eating software


Phil Neumiller wrote:

> I like this idea!  Yeah, if we can reclassify black boxes as munitions, as
> the NSA has
> done to encryption for years, then we can claim that we have the "right to
> bear black
> boxes".

...just like we have the right to own nuclear weapons.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |You buttered your bread, now lie in it.      |
|francis@ecal.com|                                             |
\==============================================================/



From owner-ietf-outbound  Mon Jul 17 13:51:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA22418
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 13:50:04 -0400 (EDT)
Received: from dragonfly.ncdragonfly.com (dragonfly.ncdragonfly.com [209.137.27.201])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03740
	for <ietf@ietf.org>; Mon, 17 Jul 2000 13:08:34 -0400 (EDT)
Received: from HDAHTS66001 (216.5.191.38 [216.5.191.38]) by dragonfly.ncdragonfly.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3)
	id LDTWSAKA; Mon, 17 Jul 2000 13:20:55 -0400
Reply-To: <dahigginbotham@ncdragonfly.com>
From: "David A. Higginbotham" <dahigginbotham@ncdragonfly.com>
To: <ietf@ietf.org>
Subject: RE: Email Privacy eating software
Date: Mon, 17 Jul 2000 13:11:27 -0400
Message-ID: <BB2831D3689AD211B14C00104B14623B1E7635@HAZEN04>
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.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I can not disagree, however, where does the responsibility to ensure liberty
lay, and what is required to ensure said liberty? specifically, what may be
suggested that one do, assuming bearing arms is inappropriate, to ensure
email privacy in particular and 'internet' liberty in general?

-----Original Message-----
From: Book, Robert [mailto:Robert.BookIII@cwusa.com]
Sent: Monday, July 17, 2000 12:45 PM
To: 'dahigginbotham@ncdragonfly.com'; ietf@ietf.org
Subject: RE: Email Privacy eating software


Hmmm, I think the federal government might have another opinion that topic,
re: Waco, etc., but this is far off the topic. It's an idyllic viewpoint,
though. But I'm afraid we're at the point in history where the phrase "a
life of freedom in the United States" is an oxymoron. And, if Carnivore
isn't as clear an example of that as one needs, then one is probably wearing
rose-colored glasses.

-----Original Message-----
From: David A. Higginbotham [mailto:dahigginbotham@ncdragonfly.com]
Sent: Monday, July 17, 2000 10:54 AM
To: ietf@ietf.org
Subject: RE: Email Privacy eating software


we have the right to own anything we can dream up and build, we do not
always have the right to use it for its intended purpose

-----Original Message-----
From: francis@localhost.localdomain
[mailto:francis@localhost.localdomain]On Behalf Of John Stracke
Sent: Monday, July 17, 2000 10:15 AM
To: ietf@ietf.org
Subject: Re: Email Privacy eating software


Phil Neumiller wrote:

> I like this idea!  Yeah, if we can reclassify black boxes as munitions, as
> the NSA has
> done to encryption for years, then we can claim that we have the "right to
> bear black
> boxes".

...just like we have the right to own nuclear weapons.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |You buttered your bread, now lie in it.      |
|francis@ecal.com|                                             |
\==============================================================/



From owner-ietf-outbound  Mon Jul 17 14:01:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA26842
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 14:00:06 -0400 (EDT)
Received: from apollo.dmnews.com (gw.dmnews.com [204.141.161.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25901
	for <ietf@ietf.org>; Mon, 17 Jul 2000 13:58:09 -0400 (EDT)
Received: by APOLLO with Internet Mail Service (5.5.2650.10)
	id <M8X8KRHM>; Mon, 17 Jul 2000 14:06:12 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE302407@APOLLO>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Email Privacy eating software - If you think you've heard it 
	all check this
Date: Mon, 17 Jul 2000 14:06:11 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Just when we thought it could not get more - well.. "complicated", someone
sent me this article:
http://ecommerce.internet.com/opinions/article/0,1467,3551_415491,00.html
If there is any truth in this and it continues like this I wonder how many
people will stay connected to the 'Net".

Lil

Lillian Komlossy || Site Manager || http://www.dmnews.com ||
http://www.imarketingnews.com || 212 925-7300 ext. 232 ||
mailto:lillian@dmnews.com


-----Original Message-----
From: Book, Robert [mailto:Robert.BookIII@CWUSA.COM]
Sent: Monday, July 17, 2000 12:45 PM
To: 'dahigginbotham@ncdragonfly.com'; ietf@ietf.org
Subject: RE: Email Privacy eating software


Hmmm, I think the federal government might have another opinion that topic,
re: Waco, etc., but this is far off the topic. It's an idyllic viewpoint,
though. But I'm afraid we're at the point in history where the phrase "a
life of freedom in the United States" is an oxymoron. And, if Carnivore
isn't as clear an example of that as one needs, then one is probably wearing
rose-colored glasses.

-----Original Message-----
From: David A. Higginbotham [mailto:dahigginbotham@ncdragonfly.com]
Sent: Monday, July 17, 2000 10:54 AM
To: ietf@ietf.org
Subject: RE: Email Privacy eating software


we have the right to own anything we can dream up and build, we do not
always have the right to use it for its intended purpose

-----Original Message-----
From: francis@localhost.localdomain
[mailto:francis@localhost.localdomain]On Behalf Of John Stracke
Sent: Monday, July 17, 2000 10:15 AM
To: ietf@ietf.org
Subject: Re: Email Privacy eating software


Phil Neumiller wrote:

> I like this idea!  Yeah, if we can reclassify black boxes as munitions, as
> the NSA has
> done to encryption for years, then we can claim that we have the "right to
> bear black
> boxes".

...just like we have the right to own nuclear weapons.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |You buttered your bread, now lie in it.      |
|francis@ecal.com|                                             |
\==============================================================/



From owner-ietf-outbound  Mon Jul 17 14:42:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA13535
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 14:40:03 -0400 (EDT)
Received: from keith.fenris.net (keith.fenris.net [158.222.0.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12649
	for <ietf@ietf.org>; Mon, 17 Jul 2000 14:37:54 -0400 (EDT)
Received: from localhost (brian@localhost)
	by keith.fenris.net (8.10.1/8.10.1) with ESMTP id e6HIblw08848;
	Mon, 17 Jul 2000 11:37:47 -0700 (PDT)
Date: Mon, 17 Jul 2000 11:37:47 -0700 (PDT)
From: Brian Lloyd <brian@lloyd.com>
X-Sender: brian@keith.fenris.net
To: "David A. Higginbotham" <dahigginbotham@ncdragonfly.com>
cc: ietf@ietf.org
Subject: RE: Email Privacy eating software
In-Reply-To: <BB2831D3689AD211B14C00104B14623B1E7635@HAZEN04>
Message-ID: <Pine.GSO.4.21.0007171126380.8004-100000@keith.fenris.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Mon, 17 Jul 2000, David A. Higginbotham wrote:

> I can not disagree, however, where does the responsibility to ensure liberty
> lay, and what is required to ensure said liberty? specifically, what may be
> suggested that one do, assuming bearing arms is inappropriate, to ensure
> email privacy in particular and 'internet' liberty in general?

If you cannot fight back against oppression, you have already lost.  I
believe that the Jewish people in Europe learned that lesson in a rather
painful manner some time back.  Of course, *our* government would *never*
try to abridge our rights in the name of The Greater Good.  The corolary
would be that the government always has our (collective) best interests at
heart and therefore fighting back is never appropriate.  

Personally, I satisfy my desire for privacy by using strong encryption
wherever possible.  I sure hope I am not hurting any feelings at the FBI.

This is a subject of great interest but probably not relevant to the
purpose of this specific group.

Brian Lloyd
brian@lloyd.com
+1.530.676.6513



From owner-ietf-outbound  Mon Jul 17 15:01:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA21409
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 15:00:03 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21196
	for <ietf@ietf.org>; Mon, 17 Jul 2000 14:59:33 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.11.0.Gamma0/calcite) id e6HIxWK09566
	for ietf@ietf.org  env-from <vjs>;
	Mon, 17 Jul 2000 12:59:32 -0600 (MDT)
Date: Mon, 17 Jul 2000 12:59:32 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007171859.e6HIxWK09566@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: Email Privacy eating software - If you think you've heard it all check this
X-Loop: ietf@ietf.org

> From: Lillian Komlossy <Lillian@dmnews.com>

> Just when we thought it could not get more - well.. "complicated", someone
> sent me this article:
> http://ecommerce.internet.com/opinions/article/0,1467,3551_415491,00.html
> If there is any truth in this and it continues like this I wonder how many
> people will stay connected to the 'Net".

There's no news there, nor any relevance to this mailing list.


No one with common senses expects to be both publicly visible and
anonymous "on the 'Net" or anywhere.  The saying "on the Internet no
one can tell if you're a dog" has always applied only to people lacking
modest clues about how things work or the motivation to use them.
The major irony of that "no one can tell" saying is that it applies at
least as much to the more than skin deep natures of old media reporters
and chatty heads.

Why should "the 'Net" be different from other media?  If you say unkind
things about someone or something, it's always wise to have empty or very
deep pockets, or proof that what you say is the truth.  It's been half a
dozen years since someone in the U.K. won a defamation case about pointed
words in netnews.  If non-U.S. (e.g. U.K.) legal rules that value truth
less than hurt feelings or reputations don't apply in your jurisdiction,
what's your worry?  The biggest danger in your words remains the harm they
can do to your own reputation.

Etoys.com vs etoy.com and many other cases have demonstrated the
fundamental weakness of aggressive consumer goods vendors' efforts
to right offenses against what they think are their good names.
As other media (e.g. the "Wall Street Journal") have long reported,
smart users of the monitoring described in that article cause the
"anti-corporate activist" to disappear or switch sides, usually with a
bribe such as fixing whatever originally angered the "activist."


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon Jul 17 15:22:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA27259
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 15:20:04 -0400 (EDT)
Received: from dragonfly.ncdragonfly.com (dragonfly.ncdragonfly.com [209.137.27.201])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25038
	for <ietf@ietf.org>; Mon, 17 Jul 2000 15:12:48 -0400 (EDT)
Received: from HDAHTS66001 (209.137.27.221 [209.137.27.221]) by dragonfly.ncdragonfly.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3)
	id LDTWSAKY; Mon, 17 Jul 2000 15:25:11 -0400
Reply-To: <dahigginbotham@ncdragonfly.com>
From: "David A. Higginbotham" <dahigginbotham@ncdragonfly.com>
To: "'Brian Lloyd'" <brian@lloyd.com>,
        "'David A. Higginbotham'" <dahigginbotham@ncdragonfly.com>
Cc: <ietf@ietf.org>
Subject: RE: Email Privacy eating software
Date: Mon, 17 Jul 2000 15:15:42 -0400
Message-ID: <BB2831D3689AD211B14C00104B14623B1E7636@HAZEN04>
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.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
In-Reply-To: <BB2831D3689AD211B14C00104B14623B278CBF@HAZEN04>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

When is one oppressed such that fighting is appropriate? Where does one
begin this fight should such a point be reached?

-----Original Message-----
From: Brian Lloyd [mailto:brian@lloyd.com]
Sent: Monday, July 17, 2000 2:38 PM
To: David A. Higginbotham
Cc: ietf@ietf.org
Subject: RE: Email Privacy eating software


On Mon, 17 Jul 2000, David A. Higginbotham wrote:

> I can not disagree, however, where does the responsibility to ensure
liberty
> lay, and what is required to ensure said liberty? specifically, what may
be
> suggested that one do, assuming bearing arms is inappropriate, to ensure
> email privacy in particular and 'internet' liberty in general?

If you cannot fight back against oppression, you have already lost.  I
believe that the Jewish people in Europe learned that lesson in a rather
painful manner some time back.  Of course, *our* government would *never*
try to abridge our rights in the name of The Greater Good.  The corolary
would be that the government always has our (collective) best interests at
heart and therefore fighting back is never appropriate.

Personally, I satisfy my desire for privacy by using strong encryption
wherever possible.  I sure hope I am not hurting any feelings at the FBI.

This is a subject of great interest but probably not relevant to the
purpose of this specific group.

Brian Lloyd
brian@lloyd.com
+1.530.676.6513



From owner-ietf-outbound  Mon Jul 17 15:42:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA04567
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 15:40:03 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26316
	for <ietf@ietf.org>; Mon, 17 Jul 2000 15:17:23 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.11.0.Gamma0/calcite) id e6HJHO409888
	for ietf@ietf.org  env-from <vjs>;
	Mon, 17 Jul 2000 13:17:24 -0600 (MDT)
Date: Mon, 17 Jul 2000 13:17:24 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007171917.e6HJHO409888@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: a modest proposal
X-Loop: ietf@ietf.org

Why not treat vacation insults like persistent delivery problems?
In other words, automatically unsubscribe the perpetrators.
Everyone makes mistakes now and then, but anyone not competent enough
to pick half reasonable software has no business bothering the IETF.

Let 'em use http://www.ietf.org/mail-archive/ietf/Current/maillist.html
if they can't handle big kids' toys.

If you don't like that, how about blackholing (e.g. procmail, DCC, or
sendmail pattern match) anything with the taint of
"Internet Mail Service (5.5.2651.58)" or
"Internet Mail Service (5.5.2650.21)"?


Vernon Schryver    vjs@rhyolite.com


> ...
> Received: by blsmsgims02.bls.com with Internet Mail Service (5.5.2650.21)
> 	id <377YRNX8>; Mon, 17 Jul 2000 15:01:24 -0400
> Message-ID: <CE46DA2B024AD311B85400A0C9F497248CD89F@BLSMSGPRV01>
> From: "Irwin, Tim A" <TIM.A.IRWIN@BELLSOUTH.COM>
> To: Vernon Schryver <vjs@calcite.rhyolite.com>
> Subject: Out of Office AutoReply: Email Privacy eating software - If you t
> 	hink you've heard it all check this
> Date: Mon, 17 Jul 2000 15:01:18 -0400
> MIME-Version: 1.0
> X-Mailer: Internet Mail Service (5.5.2650.21)
> Content-Type: text/plain;
> 	charset="windows-1252"
>
> I will be out of the office in training the week of July 17 - 21 and on
> vacation the week of July 24 - 28.  I will return to the office on Monday,
> July 31st.  
>
> I will be checking messages and responding as I'm able while attending
> training, however I will be unavailable while on vacation.
>
> Have a nice day!



] ...
] Received: from fez8019.fe.bosch.de(virus-out.fe.internet.bosch.de 10.4.4.19) by gwa2.fe.bosch.de via smap (V2.1)
] 	id xma019720; Mon, 17 Jul 00 19:02:16 GMT
] Received: by fez7202.server.bosch.de with Internet Mail Service (5.5.2651.58)
] 	id <PDN0ALG3>; Mon, 17 Jul 2000 21:02:10 +0200
] Message-ID: <EF0BBE069A12D41197B700508B65098E0A1157@bkmail04.bk.bosch.de>
] From: "EXTERN Feigel Reinhold (Marconi; MC-AC/WES1)"
] 	 <Reinhold.Feigel@marconi.com>
] To: Vernon Schryver <vjs@calcite.rhyolite.com>
] Subject: Out of Office AutoReply: Email Privacy eating software - If you t
] 	hink you've heard it all check this
] Date: Mon, 17 Jul 2000 21:01:43 +0200
] MIME-Version: 1.0
] X-Mailer: Internet Mail Service (5.5.2651.58)
] Content-Type: text/plain
] Status: R
]
] I will be back on Monday , 24th July 2000. Contact via:
] reinhold.feigel@ties.itu.int or
] reinhold.feigel@marconi.com
]



From owner-ietf-outbound  Mon Jul 17 15:52:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA07240
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 15:50:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02949
	for <ietf@ietf.org>; Mon, 17 Jul 2000 15:34:06 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@localhost [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta4/8.11.0.Beta4) with ESMTP id e6HJXGY17070;
	Mon, 17 Jul 2000 15:33:16 -0400
Message-Id: <200007171933.e6HJXGY17070@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4+dev
To: Brian Lloyd <brian@lloyd.com>
Cc: ietf@ietf.org
Subject: Re: Email Privacy eating software 
In-Reply-To: Your message of "Mon, 17 Jul 2000 11:37:47 PDT."
             <Pine.GSO.4.21.0007171126380.8004-100000@keith.fenris.net> 
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.GSO.4.21.0007171126380.8004-100000@keith.fenris.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1181880606P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 17 Jul 2000 15:33:11 -0400
X-Loop: ietf@ietf.org

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

On Mon, 17 Jul 2000 11:37:47 PDT, Brian Lloyd said:
> Personally, I satisfy my desire for privacy by using strong encryption
> wherever possible.  I sure hope I am not hurting any feelings at the FBI.

From the Sendmail 8.11 Release notes:

        Support SMTP Service Extension for Secure SMTP (RFC 2487) (STARTTLS).
                Implementation influenced by the example programs of
                OpenSSL and the work of Lutz Jaenicke of TU Cottbus.
        Support the security layer in SMTP AUTH for mechanisms which
                support encryption.  Based on code contributed by Tim
                Martin of CMU.

I'm sure that the guys who run Echelon will be overjoyed when this
ships (Real Soon Now ;)

They'll be even more overjoyed if a lot of sites start using it...

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOXNfd3At5Vm009ewEQKIBQCggRF7jNDyYQ/cG2xKyslLmUMsV8cAniiG
5lm3CU9pa16pA/glvpxj6bU5
=fDJm
-----END PGP SIGNATURE-----

--==_Exmh_-1181880606P--



From owner-ietf-outbound  Mon Jul 17 16:02:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA10635
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 16:00:05 -0400 (EDT)
Received: from keith.fenris.net (keith.fenris.net [158.222.0.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04176
	for <ietf@ietf.org>; Mon, 17 Jul 2000 15:38:46 -0400 (EDT)
Received: from robert.lloyd.com (keith.fenris.net [158.222.0.2])
	by keith.fenris.net (8.10.1/8.10.1) with ESMTP id e6HJcij09899;
	Mon, 17 Jul 2000 12:38:44 -0700 (PDT)
Message-Id: <4.3.1.0.20000717123457.00b6db70@127.0.0.1>
X-Sender: brian@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Mon, 17 Jul 2000 12:37:42 -0700
To: <dahigginbotham@ncdragonfly.com>
From: Brian Lloyd <brian@lloyd.com>
Subject: RE: Email Privacy eating software
Cc: <ietf@ietf.org>
In-Reply-To: <BB2831D3689AD211B14C00104B14623B1E7636@HAZEN04>
References: <BB2831D3689AD211B14C00104B14623B278CBF@HAZEN04>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 12:15 PM 7/17/2000, David A. Higginbotham wrote:
>When is one oppressed such that fighting is appropriate? Where does one
>begin this fight should such a point be reached?

I will be happy to discuss my views on this with you but my feeling is that 
it is not an appropriate topic of discussion for the IETF list.


Brian Lloyd                          Lucent Technologies
brian@lloyd.com                      3461 Robin Lane, Suite 1
http://www.livingston.com            Cameron Park, CA  95682
+1.530.676.6513 - voice              +1.530.676.3442 - fax



From owner-ietf-outbound  Mon Jul 17 16:12:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14367
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 16:10:03 -0400 (EDT)
Received: from keith.fenris.net (keith.fenris.net [158.222.0.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07099
	for <ietf@ietf.org>; Mon, 17 Jul 2000 15:49:36 -0400 (EDT)
Received: from robert.lloyd.com (keith.fenris.net [158.222.0.2])
	by keith.fenris.net (8.10.1/8.10.1) with ESMTP id e6HJnZj10058;
	Mon, 17 Jul 2000 12:49:35 -0700 (PDT)
Message-Id: <4.3.1.0.20000717124108.00b70e88@127.0.0.1>
X-Sender: brian@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Mon, 17 Jul 2000 12:49:25 -0700
To: Valdis.Kletnieks@vt.edu
From: Brian Lloyd <brian@lloyd.com>
Subject: Re: Email Privacy eating software 
Cc: ietf@ietf.org
In-Reply-To: <200007171933.e6HJXGY17070@black-ice.cc.vt.edu>
References: <Your message of "Mon, 17 Jul 2000 11:37:47 PDT." <Pine.GSO.4.21.0007171126380.8004-100000@keith.fenris.net>
 <Pine.GSO.4.21.0007171126380.8004-100000@keith.fenris.net>
Mime-Version: 1.0
Content-Type: multipart/signed;
 boundary="=---======--======-----==----=--=--=-==--===--==";
 protocol="application/pgp-signature"; micalg=pgp-sha1
X-Loop: ietf@ietf.org

--=---======--======-----==----=--=--=-==--===--==
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 12:33 PM 7/17/2000, Valdis.Kletnieks@vt.edu wrote:
>On Mon, 17 Jul 2000 11:37:47 PDT, Brian Lloyd said:
> > Personally, I satisfy my desire for privacy by using strong encryption
> > wherever possible.  I sure hope I am not hurting any feelings at the FBI.
>
> From the Sendmail 8.11 Release notes:
>
>         Support SMTP Service Extension for Secure SMTP (RFC 2487) (STARTTLS).
>                 Implementation influenced by the example programs of
>                 OpenSSL and the work of Lutz Jaenicke of TU Cottbus.
>         Support the security layer in SMTP AUTH for mechanisms which
>                 support encryption.  Based on code contributed by Tim
>                 Martin of CMU.
>
>I'm sure that the guys who run Echelon will be overjoyed when this
>ships (Real Soon Now ;)
>
>They'll be even more overjoyed if a lot of sites start using it...

That will be nice.  But even PGP suffices for now.  I do my level best to 
get people with whom I regularly correspond to install and use PGP, 
including those outside the USoA.  If we use strong encryption for even 
trivial/uninteresting messages we deny those who believe that they should 
have access to our information even the hint of which messages might be 
more interesting than others.  And as encrypted traffic increases, the task 
of determining which messages are "interesting" becomes even more 
difficult, perhaps to the point where it becomes effectively 
impossible.  This seems reasonable and proper to me.


Brian Lloyd                          Lucent Technologies
brian@lloyd.com                      3461 Robin Lane, Suite 1
http://www.livingston.com            Cameron Park, CA  95682
+1.530.676.6513 - voice              +1.530.676.3442 - fax

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

-----BEGIN PGP MESSAGE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBOXNjRafoWUoGaJhEEQJQxACgyT+T4QjNCO6dwKUt7WCwOQjHK2kAnjPV
gnwe8pXTQ0swXyGx0KSk9uqn
=xIrh
-----END PGP MESSAGE-----

--=---======--======-----==----=--=--=-==--===--==--



From owner-ietf-outbound  Mon Jul 17 16:23:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA18674
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 16:20:04 -0400 (EDT)
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 PAA07534
	for <ietf@ietf.org>; Mon, 17 Jul 2000 15:51:00 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id OAA07616
	for <ietf@ietf.org>; Mon, 17 Jul 2000 14:48:11 -0500 (CDT)
Message-Id: <200007171948.OAA07616@rgfsparc.cr.usgs.gov>
Date: Mon, 17 Jul 2000 14:48:11 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: RE: If you think you've heard it  all check this
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: q1yaQG5ar5hADt+v04Jh8g==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>If there is any truth in this and it continues like this I wonder how many
>people will stay connected to the 'Net".

This is just sort of a corporate version of 'Echelon.'  There's nothing that I 
can see in this technology that any ordinary person couldn't do using Deja.com 
and other search engines.  A bit more organized, and conducted, apparently, on a 
grand scale, but nothing new.  

I think people need to realize that sending unencrypted email over the Internet 
is a little like tacking a message to a public bulletin board in a city park.  
You can fold it over and write "personal for Bill only" on it, but if someone 
decides they want to read it before Bill does, there's not much you can do about 
it (unless you stand there and guard it, but that's not really practical with 
SMTP traffic).   This may not be moral, ethical, or legal, but it's going to 
happen nonetheless.  And it won't just be "Big Brother," either.

Caveat Scriptor, if you know what I mean.

RGF  

Robert G. Ferrell, CISSP
========================================
 Who goeth without humor goeth unarmed.
========================================



From owner-ietf-outbound  Mon Jul 17 16:32:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA23361
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 16:30:03 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11929
	for <ietf@ietf.org>; Mon, 17 Jul 2000 16:03:24 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id QAA18472
	for <ietf@ietf.org>; Mon, 17 Jul 2000 16:04:11 -0400
Sender: francis@localhost.localdomain
Message-ID: <397366B9.ED6ED719@ecal.com>
Date: Mon, 17 Jul 2000 16:04:09 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: a modest proposal
References: <200007171917.e6HJHO409888@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Vernon Schryver wrote:

> Why not treat vacation insults like persistent delivery problems?
> In other words, automatically unsubscribe the perpetrators.

Mmm, it probably can't be done automatically, since the mailing list doesn't get the vacation messages (that I know
of--it doesn't happen with the mailing lists I run, anyway).

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |"What we have here is a failure to assimilate."|
|francis@ecal.com|--Cool Hand Locutius                           |
\================================================================/





From owner-ietf-outbound  Mon Jul 17 16:52:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA01728
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 16:50:04 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28013
	for <ietf@ietf.org>; Mon, 17 Jul 2000 16:40:02 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id NAA15994;
	Mon, 17 Jul 2000 13:40:02 -0700 (PDT)
Date: Mon, 17 Jul 2000 13:40:02 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200007172040.NAA15994@shell5.ba.best.com>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Mime-Version: 1.0
X-Loop: ietf@ietf.org

Masataka:
   
> If IETF makes it clear that AOL is not an ISP, it will commercially
> motivate AOL to be an ISP.

Keith:

> probably not.  folks who subscribe to AOL aren't likely to be
> reading IETF documents.

> face it, it's not the superior quality of AOL's service that keeps
> AOLers from moving - it's their susceptibility to marketing BS and
> their addiction to chat rooms.  it's hard to help those people.

Assuming they need help.  The impression I have gotten from people
who regularly use AOL is that they are generally satisfied with the
nature of the service (as opposed to the quality of the service).
As they discover more about the Internet, they may or may not switch
to "real" ISPs, depending on whether they have needs for what "real"
ISPs provide.

--gregbo



From owner-ietf-outbound  Mon Jul 17 17:02:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA05559
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 17:00:03 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00534
	for <ietf@ietf.org>; Mon, 17 Jul 2000 16:46:39 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 13EHmS-0004nA-00; Mon, 17 Jul 2000 21:46:24 +0100
Date: Mon, 17 Jul 2000 21:46:21 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: a modest proposal
In-Reply-To: <200007171917.e6HJHO409888@calcite.rhyolite.com>
Message-ID: <Pine.GSO.4.21.0007172143350.10394-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Mon, 17 Jul 2000, Vernon Schryver wrote:

> Why not treat vacation insults like persistent delivery problems?
> In other words, automatically unsubscribe the perpetrators.

How about because the vacation message came to you, the poster, and
not to list administration? You've got a third-party trust issue right
there.

L.

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



From owner-ietf-outbound  Mon Jul 17 17:12:45 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA09611
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 17:10:03 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06365
	for <ietf@ietf.org>; Mon, 17 Jul 2000 17:01:50 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.11.0.Gamma0/calcite) id e6HL1pB12081
	for ietf@ietf.org  env-from <vjs>;
	Mon, 17 Jul 2000 15:01:51 -0600 (MDT)
Date: Mon, 17 Jul 2000 15:01:51 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007172101.e6HL1pB12081@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: a modest proposal
X-Loop: ietf@ietf.org

> > Why not treat vacation insults like persistent delivery problems?
> > In other words, automatically unsubscribe the perpetrators.
>
> How about because the vacation message came to you, the poster, and
> not to list administration? You've got a third-party trust issue right
> there.

Once upon a time, "automatically" did not mean only "by computer and
untouched by human let, leave, hindrance or even oversight." I was
thinking of such as the so called "automatic suspension of driving
priviledges" that drunk driving convictions or refusals to take alcohol
tests cause in some places, say by sending copies of vacation messages to
the human administrators of IETF lists.

If you want something purely computer-controlled, how about using
vacation responses to the regular "IETF List maintenance" messages
from ietf-secretariat@ietf.org and the announcments of the filtered
form of this list?

My theory is if that vacation noise were known to be reason for
involuntary unsubscribing or just likely cause for public humiliation,
people would exercise a little care.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon Jul 17 17:32:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA20243
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 17:30:04 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11894
	for <ietf@ietf.org>; Mon, 17 Jul 2000 17:14:25 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA10240;
        Mon, 17 Jul 2000 17:14:04 -0400 (EDT)
Message-Id: <200007172114.RAA10240@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: a modest proposal 
In-reply-to: Your message of "Mon, 17 Jul 2000 13:17:24 MDT."
             <200007171917.e6HJHO409888@calcite.rhyolite.com> 
Date: Mon, 17 Jul 2000 17:14:04 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Why not treat vacation insults like persistent delivery problems?

go right ahead, you have my blessing to do this for your lists. :)

OTOH enforcing this policy right now on the IETF list would probably
do more harm than good.  we can hardly expect the vacation bouncers
to "do the right thing" when "the right thing" isn't written down 
anywhere, and there may not even be consensus on what "the right thing"
is.

Keith



From owner-ietf-outbound  Mon Jul 17 17:42:50 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA25980
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 17:40:04 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22196
	for <ietf@ietf.org>; Mon, 17 Jul 2000 17:33:50 -0400 (EDT)
Received: from contactdish (atkielsk.adsl-net2-rg.nerim.net [62.4.19.136]) by atkielski.com (8.8.8) id XAA64234; Mon, 17 Jul 2000 23:33:51 +0200 (CEST)
Message-ID: <007501bff036$b3a72880$0a00000a@contactdish>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <200007172040.NAA15994@shell5.ba.best.com>
Subject: AOL's view of the Net versus the rest
Date: Mon, 17 Jul 2000 23:33:50 +0200
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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Greg Skinner writes:

> The impression I have gotten from people who regularly
> use AOL is that they are generally satisfied with the
> nature of the service (as opposed to the quality of the
> service).

It's like radio:  Some people are content to tune in to their favorite FM
station and listen to the Top 40 or "easy listening" music; whereas others
prefer to get ham radio licenses and explore the medium to its fullest.
People who want "easy listening" on the Internet subscribe to AOL; people
who want "ham Internet" subscribe to smaller ISPs that specialize in
providing nothing but fast, "raw" connections to the mighty Net for people
who know what they want.

As long as there are still ways to get the "raw" connections that I prefer,
I don't really care if most people are satisfied with AOL and its
clones--that's their choice.



From owner-ietf-outbound  Mon Jul 17 17:52:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA01263
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 17:50:03 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26426
	for <ietf@ietf.org>; Mon, 17 Jul 2000 17:40:47 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id OAA12289;
	Mon, 17 Jul 2000 14:40:49 -0700 (PDT)
Date: Mon, 17 Jul 2000 14:40:49 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200007172140.OAA12289@shell5.ba.best.com>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Mime-Version: 1.0
X-Loop: ietf@ietf.org

Masataka Ohta wrote:

> If IETF makes it clear that AOL is not an ISP, it will commercially
> motivate AOL to be an ISP.

Why?  Certainly, they are aware that they are not an ISP by your
definition.  It hasn't changed their business practices.  Why would
an IETF RFC change their business practices?  The business practices
of AOL are determined, for the most part, by what Wall Street and
their customers think is important, not what the IETF thinks.  Most
of their customers are unlikely to read such an RFC anyway.

--gregbo



From owner-ietf-outbound  Mon Jul 17 18:02:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA07391
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 18:00:03 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04132
	for <ietf@ietf.org>; Mon, 17 Jul 2000 17:54:15 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@localhost [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta4/8.11.0.Beta4) with ESMTP id e6HLsCY26134;
	Mon, 17 Jul 2000 17:54:12 -0400
Message-Id: <200007172154.e6HLsCY26134@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: ietf@ietf.org
Subject: Re: AOL's view of the Net versus the rest 
In-Reply-To: Your message of "Mon, 17 Jul 2000 23:33:50 +0200."
             <007501bff036$b3a72880$0a00000a@contactdish> 
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: <200007172040.NAA15994@shell5.ba.best.com>
            <007501bff036$b3a72880$0a00000a@contactdish>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-713051206P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 17 Jul 2000 17:54:11 -0400
X-Loop: ietf@ietf.org

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

On Mon, 17 Jul 2000 23:33:50 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
> It's like radio:  Some people are content to tune in to their favorite FM
> station and listen to the Top 40 or "easy listening" music; whereas others
> prefer to get ham radio licenses and explore the medium to its fullest.

Interesting analogy..

> As long as there are still ways to get the "raw" connections that I prefer,
> I don't really care if most people are satisfied with AOL and its
> clones--that's their choice.

Well.. obviously you're not a ham operator - most of the ones I know are
quite zealous about complaining when another operator does anything out
of spec.. ;)

It's interesting that the major complaint from the non-AOL crowd isn't about
AOL's existence, it's about interoperability problems.  Quite similar to the
average ham operator....

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOXOAg3At5Vm009ewEQJthwCfV7QrVddfJsg/jYaEH82amLAf6rYAoM0j
ECH4vGfZTMziaYab1RDwFkyA
=iL16
-----END PGP SIGNATURE-----

--==_Exmh_-713051206P--



From owner-ietf-outbound  Mon Jul 17 18:21:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA16636
	for ietf-outbound.10@ietf.org; Mon, 17 Jul 2000 18:20:03 -0400 (EDT)
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13175
	for <ietf@ietf.org>; Mon, 17 Jul 2000 18:12:25 -0400 (EDT)
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id PAA15769 for <ietf@ietf.org>; Mon, 17 Jul 2000 15:12:24 -0700 (MST)]
Received: [from tx14exm01.ftw.mot.com ([178.1.100.241]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id PAA22237 for <ietf@ietf.org>; Mon, 17 Jul 2000 15:12:09 -0700 (MST)]
Received: by tx14exm01.ftw.mot.com with Internet Mail Service (5.5.2650.21)
	id <M4PVPJ8G>; Mon, 17 Jul 2000 17:12:22 -0500
Message-ID: <ED53441FBBDAD311B85000508B95104D33AB66@tx14exm03.ftw.mot.com>
From: Briancon Alain-FAB005 <Alain_Briancon-FAB005@email.mot.com>
To: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
        Anthony Atkielski <anthony@atkielski.com>
Cc: ietf@ietf.org
Subject: RE: AOL's view of the Net versus the rest 
Date: Mon, 17 Jul 2000 17:12:21 -0500
Return-Receipt-To: Briancon Alain-FAB005
	 <Alain_Briancon-FAB005@email.mot.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop: ietf@ietf.org

the internet is the ham radio for the '00s.

it's also the combination of gutenberg and luther for the '00s. Remember
where the simple nailing of theses did for us way back when...


-----Original Message-----
From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
Sent: Monday, July 17, 2000 5:54 PM
To: Anthony Atkielski
Cc: ietf@ietf.org
Subject: Re: AOL's view of the Net versus the rest 


On Mon, 17 Jul 2000 23:33:50 +0200, Anthony Atkielski
<anthony@atkielski.com>  said:
> It's like radio:  Some people are content to tune in to their favorite FM
> station and listen to the Top 40 or "easy listening" music; whereas others
> prefer to get ham radio licenses and explore the medium to its fullest.

Interesting analogy..

> As long as there are still ways to get the "raw" connections that I
prefer,
> I don't really care if most people are satisfied with AOL and its
> clones--that's their choice.

Well.. obviously you're not a ham operator - most of the ones I know are
quite zealous about complaining when another operator does anything out
of spec.. ;)

It's interesting that the major complaint from the non-AOL crowd isn't about
AOL's existence, it's about interoperability problems.  Quite similar to the
average ham operator....

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Tue Jul 18 03:44:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA12985
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 03:40:02 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA09315
	for <ietf@ietf.org>; Tue, 18 Jul 2000 03:31:25 -0400 (EDT)
Received: from hocus.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.03267-0@bells.cs.ucl.ac.uk>; Tue, 18 Jul 2000 08:30:54 +0100
To: Valdis.Kletnieks@vt.edu
cc: Brian Lloyd <brian@lloyd.com>, ietf@ietf.org, J.Crowcroft@CS.UCL.AC.UK
Subject: Re: Email Privacy eating software
In-reply-to: Your message of "Mon, 17 Jul 2000 15:33:11 EDT." <200007171933.e6HJXGY17070@black-ice.cc.vt.edu>
Date: Tue, 18 Jul 2000 08:30:52 +0100
Message-ID: <814.963905452@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


yo udont know about RIP then

if you visit the UK, and are asked to show any files on your computer,
you cannot claim you "cannot remember the key"

that wil lbe deemed evidence that you are witholding evidence and yo
ucan go to jail jus for that.,. i.e. our new crypto-fascist law takes
away the right to the presumption of innocence  ratehr than guilt....

its like escrow only worse.

the technology is irrelevant in the face of such blatant misuse of
human rights.

In message <200007171933.e6HJXGY17070@black-ice.cc.vt.edu>, Valdis.Kletnieks@vt
.edu typed:

 >>--==_Exmh_-1181880606P
 >>Content-Type: text/plain; charset=us-ascii
 >>
 >>On Mon, 17 Jul 2000 11:37:47 PDT, Brian Lloyd said:
 >>> Personally, I satisfy my desire for privacy by using strong encryption
 >>> wherever possible.  I sure hope I am not hurting any feelings at the FBI.
 >>
 >>From the Sendmail 8.11 Release notes:
 >>
 >>        Support SMTP Service Extension for Secure SMTP (RFC 2487) (STARTTLS).
 >>                Implementation influenced by the example programs of
 >>                OpenSSL and the work of Lutz Jaenicke of TU Cottbus.
 >>        Support the security layer in SMTP AUTH for mechanisms which
 >>                support encryption.  Based on code contributed by Tim
 >>                Martin of CMU.
 >>
 >>I'm sure that the guys who run Echelon will be overjoyed when this
 >>ships (Real Soon Now ;)
 >>
 >>They'll be even more overjoyed if a lot of sites start using it...
 >>
 >>-- 
 >>				Valdis Kletnieks
 >>				Operating Systems Analyst
 >>				Virginia Tech
 >>
 >>
 >>--==_Exmh_-1181880606P
 >>Content-Type: application/pgp-signature
 >>
 >>-----BEGIN PGP SIGNATURE-----
 >>Version: PGP 6.5.2
 >>Comment: Exmh version 2.2 06/16/2000
 >>
 >>iQA/AwUBOXNfd3At5Vm009ewEQKIBQCggRF7jNDyYQ/cG2xKyslLmUMsV8cAniiG
 >>5lm3CU9pa16pA/glvpxj6bU5
 >>=fDJm
 >>-----END PGP SIGNATURE-----
 >>
 >>--==_Exmh_-1181880606P--
 >>

 cheers

   jon



From owner-ietf-outbound  Tue Jul 18 04:42:57 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA05053
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 04:40:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03980
	for <ietf@ietf.org>; Tue, 18 Jul 2000 04:36:43 -0400 (EDT)
Received: from contactdish (atkielsk.adsl-net2-rg.nerim.net [62.4.19.136]) by atkielski.com (8.8.8) id KAA30385; Tue, 18 Jul 2000 10:36:43 +0200 (CEST)
Message-ID: <001f01bff093$4d6e3470$0a00000a@contactdish>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <814.963905452@cs.ucl.ac.uk>
Subject: Re: Email Privacy eating software
Date: Tue, 18 Jul 2000 10:36:42 +0200
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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Jon Crowcroft wrote:

> yo udont know about RIP then
>
> if you visit the UK, and are asked to show any files on your computer,
> you cannot claim you "cannot remember the key"
>
> that wil lbe deemed evidence that you are witholding evidence and yo
> ucan go to jail jus for that.,. i.e. our new crypto-fascist law takes
> away the right to the presumption of innocence  ratehr than guilt....
>
> its like escrow only worse.
>
> the technology is irrelevant in the face of such blatant misuse of
> human rights.

Well, the U.K. is supposed to be a democracy; why don't you just vote to get
your rights restored?



From owner-ietf-outbound  Tue Jul 18 05:12:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA15510
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 05:10:03 -0400 (EDT)
Received: from ztxmail04.ztx.compaq.com (ztxmail04.ztx.compaq.com [161.114.1.208])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13864
	for <ietf@ietf.org>; Tue, 18 Jul 2000 05:05:00 -0400 (EDT)
Received: by ztxmail04.ztx.compaq.com (Postfix, from userid 12345)
	id 7AF6C130; Tue, 18 Jul 2000 04:04:31 -0500 (CDT)
Received: from excreo-gh02.reo.cpqcorp.net (excreo-gh02.reo.cpqcorp.net [16.37.150.254])
	by ztxmail04.ztx.compaq.com (Postfix) with ESMTP
	id AA7D81CA; Tue, 18 Jul 2000 04:04:30 -0500 (CDT)
Received: by excreo-gh02.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <396GLK0Y>; Tue, 18 Jul 2000 10:04:29 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9CF5@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'Anthony Atkielski'" <anthony@atkielski.com>, ietf@ietf.org
Subject: RE: Email Privacy eating software
Date: Tue, 18 Jul 2000 10:04:20 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Well been British, we are to polite and would not like to make a fuss. :)

-----Original Message-----
From: Anthony Atkielski [mailto:anthony@atkielski.com]
Sent: Tuesday, July 18, 2000 9:37 AM
To: ietf@ietf.org
Subject: Re: Email Privacy eating software


Jon Crowcroft wrote:

> yo udont know about RIP then
>
> if you visit the UK, and are asked to show any files on your computer,
> you cannot claim you "cannot remember the key"
>
> that wil lbe deemed evidence that you are witholding evidence and yo
> ucan go to jail jus for that.,. i.e. our new crypto-fascist law takes
> away the right to the presumption of innocence  ratehr than guilt....
>
> its like escrow only worse.
>
> the technology is irrelevant in the face of such blatant misuse of
> human rights.

Well, the U.K. is supposed to be a democracy; why don't you just vote to get
your rights restored?



From owner-ietf-outbound  Tue Jul 18 05:42:59 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA25211
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 05:40:02 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23829
	for <ietf@ietf.org>; Tue, 18 Jul 2000 05:35:42 -0400 (EDT)
Received: from contactdish (atkielsk.adsl-net2-rg.nerim.net [62.4.19.136]) by atkielski.com (8.8.8) id LAA36030; Tue, 18 Jul 2000 11:35:43 +0200 (CEST)
Message-ID: <008601bff09b$8b32e9b0$0a00000a@contactdish>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <71C4C55F198BD211B24F0000F842F15807ED9CF5@reoexc6.reo.cpqcorp.net>
Subject: Re: Email Privacy eating software
Date: Tue, 18 Jul 2000 11:35:41 +0200
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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Jonathan Parkinson wrote:

> Well been British, we are to polite and would not like to make a fuss. :)

Yeah, the ones who liked to make a fuss went off and started their own
democracies centuries ago.

So the British really don't mind having their privacy compromised, then?  I
hope Americans show a bit more concern, before it's too late.





From owner-ietf-outbound  Tue Jul 18 07:02:45 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA22482
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 07:00:02 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA19348
	for <ietf@ietf.org>; Tue, 18 Jul 2000 06:50:36 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.15954-0@bells.cs.ucl.ac.uk>; Tue, 18 Jul 2000 11:50:31 +0100
To: Anthony Atkielski <anthony@atkielski.com>
cc: ietf <ietf@ietf.org>
Subject: Re: Email Privacy eating software
In-reply-to: Your message of "Tue, 18 Jul 2000 11:35:41 +0200." <008601bff09b$8b32e9b0$0a00000a@contactdish>
Date: Tue, 18 Jul 2000 11:50:31 +0100
Message-ID: <4189.963917431@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <008601bff09b$8b32e9b0$0a00000a@contactdish>, Anthony Atkielski type
d:
 >>> Well been British, we are to polite and would not like to make a fuss. :)
 
 >>Yeah, the ones who liked to make a fuss went off and started their own
 >>democracies centuries ago.

 >>So the British really don't mind having their privacy compromised, then?  I
 >>hope Americans show a bit more concern, before it's too late.

 
next summer's IETF meeting is tentatively scheduled for London, England
http://www.ietf.org/meetings/0mtg-sites.txt

if you turn up at customs with a laptop, you may be asked to show any
and all files on it to the nice chaps there. if someone has sent you
crypted email (say using your public key) you may be obliged to
connect the lapto pto the public net and  access your other key to
decrypt the mail for the nice chaps in customs to priove that it is
not to do with pornography or terrorism - whereeve yo uare from, you
will have no recourse to say "no" or "this is commercial in
confidence" or "my company will fire me if i let this go to anyone or
send it over the net to decrypt at my home site etc etc"

the wavelan in the meeting site may be subject to wiretap...etc etc

the ietf community may wish to send a message by reconsidering having
a meeting in the UK....until the law here is made more rational.

 cheers

   jon



From owner-ietf-outbound  Tue Jul 18 08:42:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA00450
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 08:40:04 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23147
	for <ietf@ietf.org>; Tue, 18 Jul 2000 08:21:03 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 13EWMv-0002gv-00
	for ietf@ietf.org; Tue, 18 Jul 2000 13:21:01 +0100
Date: Tue, 18 Jul 2000 13:20:58 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: ietf@ietf.org
Subject: Re: Email Privacy eating software
In-Reply-To: <814.963905452@cs.ucl.ac.uk>
Message-ID: <Pine.GSO.4.21.0007181317340.12921-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Tue, 18 Jul 2000, Jon Crowcroft wrote:

> yo udont know about RIP then
> 
> if you visit the UK, and are asked to show any files on your computer,
> you cannot claim you "cannot remember the key"
> 
> that wil lbe deemed evidence that you are witholding evidence and yo
> ucan go to jail jus for that.,. i.e. our new crypto-fascist law takes
> away the right to the presumption of innocence  ratehr than guilt....
> 
> its like escrow only worse.

See http://www.stand.org.uk/
    http://www.ntk.net/index.cgi?back=2000/now0714.txt&line=18#l

The RIP bill's currently being debated.

L.

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



From owner-ietf-outbound  Tue Jul 18 09:12:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA15080
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 09:10:03 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11874
	for <ietf@ietf.org>; Tue, 18 Jul 2000 09:03:01 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 13EX1T-00038g-00; Tue, 18 Jul 2000 14:02:55 +0100
Date: Tue, 18 Jul 2000 14:02:52 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Anthony Atkielski <anthony@atkielski.com>
cc: ietf@ietf.org
Subject: Re: Email Privacy eating software
In-Reply-To: <001f01bff093$4d6e3470$0a00000a@contactdish>
Message-ID: <Pine.GSO.4.21.0007181400470.12921-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Tue, 18 Jul 2000, Anthony Atkielski wrote:

> Well, the U.K. is supposed to be a democracy;

actually, it's a 'constitutional monarchy', with no elections in the
executive branch.

http://www.odci.gov/cia/publications/factbook/uk.html#gov

hth,

L.

> why don't you just vote to get your rights restored?

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



From owner-ietf-outbound  Tue Jul 18 09:42:51 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA28186
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 09:40:06 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19234
	for <ietf@ietf.org>; Tue, 18 Jul 2000 09:20:09 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@localhost [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta4/8.11.0.Beta4) with ESMTP id e6IDJuY10886;
	Tue, 18 Jul 2000 09:19:56 -0400
Message-Id: <200007181319.e6IDJuY10886@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4+dev
To: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
Cc: Brian Lloyd <brian@lloyd.com>, ietf@ietf.org
Subject: Re: Email Privacy eating software 
In-Reply-To: Your message of "Tue, 18 Jul 2000 08:30:52 BST."
             <814.963905452@cs.ucl.ac.uk> 
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: <814.963905452@cs.ucl.ac.uk>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1550644026P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 18 Jul 2000 09:19:55 -0400
X-Loop: ietf@ietf.org

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

On Tue, 18 Jul 2000 08:30:52 BST, Jon Crowcroft said:
> yo udont know about RIP then

I'm quite aware of RIP.

> if you visit the UK, and are asked to show any files on your computer,
> you cannot claim you "cannot remember the key"

This is about session keys - Sendmail will do SSL connections (basically).

You ever found the key for an HTTP SSL session? If you did, that would be
considered breaking SSL.  

I really hope that the Brits making this poor law understand the distiction
for session keys, or they can kiss e-commerce goodbye. ;)

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOXRZe3At5Vm009ewEQKpTACfWRXnxLrK1FiLk9fGZC1v5RTbJYQAnRNG
ocbOhYDs/DO98dxnp5vVGA9m
=P8wf
-----END PGP SIGNATURE-----

--==_Exmh_1550644026P--



From owner-ietf-outbound  Tue Jul 18 09:52:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA02783
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 09:50:03 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA02037
	for <ietf@ietf.org>; Tue, 18 Jul 2000 09:48:18 -0400 (EDT)
Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.27671-0@bells.cs.ucl.ac.uk>; Tue, 18 Jul 2000 14:48:05 +0100
To: L.Wood@eim.surrey.ac.uk
cc: ietf@ietf.org
Subject: Re: Email Privacy eating software
In-reply-to: Your message of "Tue, 18 Jul 2000 13:20:58 BST." <Pine.GSO.4.21.0007181317340.12921-100000@petra.ee.surrey.ac.uk>
Date: Tue, 18 Jul 2000 14:48:02 +0100
Message-ID: <2068.963928082@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <Pine.GSO.4.21.0007181317340.12921-100000@petra.ee.surrey.ac.uk>, Ll
oyd Wood typed:

 >>On Tue, 18 Jul 2000, Jon Crowcroft wrote:
 >>
 >>> yo udont know about RIP then
 >>> 
 >>> if you visit the UK, and are asked to show any files on your computer,
 >>> you cannot claim you "cannot remember the key"
 >>> 
 >>> that wil lbe deemed evidence that you are witholding evidence and yo
 >>> ucan go to jail jus for that.,. i.e. our new crypto-fascist law takes
 >>> away the right to the presumption of innocence  ratehr than guilt....
 >>> 
 >>> its like escrow only worse.
 >>
 >>See http://www.stand.org.uk/
 >>    http://www.ntk.net/index.cgi?back=2000/now0714.txt&line=18#l
 >>
 >>The RIP bill's currently being debated.

see also
http://www.fipr.org/rip/
for the gory details...

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

 cheers

   jon



From owner-ietf-outbound  Tue Jul 18 11:12:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA10819
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 11:10:03 -0400 (EDT)
Received: from web4601.mail.yahoo.com (web4601.mail.yahoo.com [216.115.105.156])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA07807
	for <ietf@ietf.org>; Tue, 18 Jul 2000 11:02:34 -0400 (EDT)
Message-ID: <20000718150202.4234.qmail@web4601.mail.yahoo.com>
Received: from [4.33.131.234] by web4601.mail.yahoo.com; Tue, 18 Jul 2000 08:02:02 PDT
Date: Tue, 18 Jul 2000 08:02:02 -0700 (PDT)
From: Eli Sanchez <geekfreak2000@yahoo.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: Greg Skinner <gds@best.com>, ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

Wrong I'm reading it :P  Leave AOL alone.  There are
many FREE connections to select one can have AOL and
many other "raw" connections.  Maybe we like AOL, and
that is why we pick it.  AOlers also know that AOL
isnt top class but we like easy listening once in a
while :P We're not all idiots and although there are
some exceptions we have brains to!

-Eli

--- Greg Skinner <gds@best.com> wrote:
> Masataka Ohta wrote:
> 
> > If IETF makes it clear that AOL is not an ISP, it
> will commercially
> > motivate AOL to be an ISP.
> 
> Why?  Certainly, they are aware that they are not an
> ISP by your
> definition.  It hasn't changed their business
> practices.  Why would
> an IETF RFC change their business practices?  The
> business practices
> of AOL are determined, for the most part, by what
> Wall Street and
> their customers think is important, not what the
> IETF thinks.  Most
> of their customers are unlikely to read such an RFC
> anyway.
> 
> --gregbo
> 


__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail – Free email you can access from anywhere!
http://mail.yahoo.com/



From owner-ietf-outbound  Tue Jul 18 12:21:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA11706
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 12:20:03 -0400 (EDT)
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 MAA07635
	for <ietf@ietf.org>; Tue, 18 Jul 2000 12:10:12 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id LAA19038
	for <ietf@ietf.org>; Tue, 18 Jul 2000 11:07:22 -0500 (CDT)
Message-Id: <200007181607.LAA19038@rgfsparc.cr.usgs.gov>
Date: Tue, 18 Jul 2000 11:07:22 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: ThWc4GEuoZiHj6N4WrTvag==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>Wrong I'm reading it :P  Leave AOL alone.  
>AOlers also know that AOL
>isnt top class but we like easy listening once in a while

Um, I guess this isn't one of those 'whiles.'

>Received: from [4.33.131.234] by web4601.mail.yahoo.com

;-)

RGF

Robert G. Ferrell, CISSP
========================================
 Who goeth without humor goeth unarmed.
========================================



From owner-ietf-outbound  Tue Jul 18 14:01:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA23750
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 14:00:04 -0400 (EDT)
Received: from ex1.clearaccess.net ([204.214.6.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22799
	for <ietf@ietf.org>; Tue, 18 Jul 2000 13:57:27 -0400 (EDT)
Received: by EX1 with Internet Mail Service (5.5.1960.3)
	id <3GXDV8QT>; Tue, 18 Jul 2000 13:52:08 -0400
Message-ID: <818BD117E43BD4118A7A0008C7CF9C3102BDC7@EX1>
From: Scot Mc Pherson <smcpherson@clearaccess.net>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: testing (NT)
Date: Tue, 18 Jul 2000 13:52:03 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
X-Loop: ietf@ietf.org

NT



From owner-ietf-outbound  Tue Jul 18 14:11:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA27232
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 14:10:03 -0400 (EDT)
Received: from thunderer.cnchost.com (thunderer.concentric.net [207.155.252.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24835
	for <ietf@ietf.org>; Tue, 18 Jul 2000 14:02:31 -0400 (EDT)
Received: from MATT.ascend.com (ts005d24.sjc-ca.concentric.net [206.173.234.228])
	by thunderer.cnchost.com
	id OAA17276; Tue, 18 Jul 2000 14:02:22 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.8]
Errors-To: <matt@ipverse.com>
Message-Id: <4.3.1.2.20000718105915.00bd2de0@pop3.ipverse.com>
X-Sender: matt@ipverse.com@pop3.ipverse.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 18 Jul 2000 11:03:28 -0700
To: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
From: Matt Holdrege <matt@ipverse.com>
Subject: Re: Email Privacy eating software
Cc: ietf@ietf.org
In-Reply-To: <4189.963917431@cs.ucl.ac.uk>
References: <Your message of "Tue, 18 Jul 2000 11:35:41 +0200." <008601bff09b$8b32e9b0$0a00000a@contactdish>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 11:50 AM 7/18/00 +0100, Jon Crowcroft wrote:
>next summer's IETF meeting is tentatively scheduled for London, England
>http://www.ietf.org/meetings/0mtg-sites.txt
>
>if you turn up at customs with a laptop, you may be asked to show any
>and all files on it to the nice chaps there. if someone has sent you
>crypted email (say using your public key) you may be obliged to
>connect the lapto pto the public net and  access your other key to
>decrypt the mail for the nice chaps in customs to priove that it is
>not to do with pornography or terrorism - whereeve yo uare from, you
>will have no recourse to say "no" or "this is commercial in
>confidence" or "my company will fire me if i let this go to anyone or
>send it over the net to decrypt at my home site etc etc"

As one who travels to London quite often and has red hair and is of Irish 
descent, this sounds a bit overmuch to me. I've never had anything other 
than a kind welcome by British customs officials. There are loads of crazy 
laws in the U.S. and other countries. We citizens are grateful that the 
enforcement branch of the government chooses to ignore them unless provoked.



From owner-ietf-outbound  Tue Jul 18 14:51:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA12869
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 14:50:03 -0400 (EDT)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10399
	for <ietf@ietf.org>; Tue, 18 Jul 2000 14:45:16 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id C1D784CE1E; Tue, 18 Jul 2000 14:45:15 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id OAA00804;
	Tue, 18 Jul 2000 14:45:15 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id BD10135DC2; Tue, 18 Jul 2000 14:45:14 -0400 (EDT)
X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.3 #1[UCI]
From: "Steven M. Bellovin" <smb@research.att.com>
To: Matt Holdrege <matt@ipverse.com>
Cc: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>, ietf@ietf.org
Subject: Re: Email Privacy eating software 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 18 Jul 2000 14:45:14 -0400
Sender: smb@research.att.com
Message-Id: <20000718184514.BD10135DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <4.3.1.2.20000718105915.00bd2de0@pop3.ipverse.com>, Matt Holdrege wr
ites:
>At 11:50 AM 7/18/00 +0100, Jon Crowcroft wrote:
>>next summer's IETF meeting is tentatively scheduled for London, England
>>http://www.ietf.org/meetings/0mtg-sites.txt
>>
>>if you turn up at customs with a laptop, you may be asked to show any
>>and all files on it to the nice chaps there. if someone has sent you
>>crypted email (say using your public key) you may be obliged to
>>connect the lapto pto the public net and  access your other key to
>>decrypt the mail for the nice chaps in customs to priove that it is
>>not to do with pornography or terrorism - whereeve yo uare from, you
>>will have no recourse to say "no" or "this is commercial in
>>confidence" or "my company will fire me if i let this go to anyone or
>>send it over the net to decrypt at my home site etc etc"
>
>As one who travels to London quite often and has red hair and is of Irish 
>descent, this sounds a bit overmuch to me. I've never had anything other 
>than a kind welcome by British customs officials. There are loads of crazy 
>laws in the U.S. and other countries. We citizens are grateful that the 
>enforcement branch of the government chooses to ignore them unless provoked.
>
>
I'm not sure what "sounds a bit overmuch" to you.  Have a look at
http://news.bbc.co.uk/hi/english/sci/tech/newsid%5F150000/150465.stm


		--Steve Bellovin




From owner-ietf-outbound  Tue Jul 18 15:31:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA04336
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 15:30:03 -0400 (EDT)
Received: from neodymium.btinternet.com (neodymium.btinternet.com [194.73.73.83])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29351
	for <ietf@ietf.org>; Tue, 18 Jul 2000 15:20:27 -0400 (EDT)
Received: from [62.7.102.236] (helo=salavat)
	by neodymium.btinternet.com with esmtp (Exim 3.03 #83)
	id 13Ecun-0006ya-00
	for ietf@ietf.org; Tue, 18 Jul 2000 20:20:25 +0100
Message-ID: <000301bff0ed$5f9cf320$ec66073e@salavat>
From: "Salavat R. Magazov" <srm4@ukc.ac.uk>
To: "IETF mailing list" <ietf@ietf.org>
Subject: Firewall standard
Date: Tue, 18 Jul 2000 17:27:54 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0008_01BFF0DD.81791CE0"
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
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0008_01BFF0DD.81791CE0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit

Hello

Are there any standards for application layer firewalls, particularly secure
tunnelers. Or may be some kind of recommendations to vendors and system
administrators.

Salavat

------=_NextPart_000_0008_01BFF0DD.81791CE0
Content-Type: text/x-vcard;
	name="Salavat R. Magazov.vcf"
Content-Disposition: attachment;
	filename="Salavat R. Magazov.vcf"
Content-Transfer-Encoding: 7bit

BEGIN:VCARD
VERSION:2.1
N:Magazov;Salavat;R.
FN:Salavat R. Magazov
NICKNAME:Sal
ORG:University of Kent at Canterbury
TEL;HOME;VOICE:+44-1227-472835
X-WAB-GENDER:2
BDAY:20000517
EMAIL;PREF;INTERNET:srm4@ukc.ac.uk
EMAIL;INTERNET:salavat@ukonline.co.uk
REV:20000718T162753Z
END:VCARD

------=_NextPart_000_0008_01BFF0DD.81791CE0--



From owner-ietf-outbound  Tue Jul 18 16:01:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA18306
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 16:00:04 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17561
	for <ietf@ietf.org>; Tue, 18 Jul 2000 15:58:25 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id MAA24045
	for <ietf@ietf.org>; Tue, 18 Jul 2000 12:57:53 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <3C76KLDP>; Tue, 18 Jul 2000 19:54:56 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D302@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: IETF mailing list <ietf@ietf.org>
Subject: RE: Firewall standard
Date: Tue, 18 Jul 2000 19:57:11 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="koi8-r"
X-Loop: ietf@ietf.org

RFC2401.. is a good starting point


->-----Original Message-----
->From: Salavat R. Magazov [mailto:srm4@ukc.ac.uk]
->Sent: Tuesday, July 18, 2000 12:28 PM
->To: IETF mailing list
->Subject: Firewall standard
->
->
->Hello
->
->Are there any standards for application layer firewalls, 
->particularly secure
->tunnelers. Or may be some kind of recommendations to vendors 
->and system
->administrators.
->
->Salavat
->



From owner-ietf-outbound  Tue Jul 18 16:11:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA23458
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 16:10:03 -0400 (EDT)
Received: from tantalum (tantalum.btinternet.com [194.73.73.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20577
	for <ietf@ietf.org>; Tue, 18 Jul 2000 16:04:04 -0400 (EDT)
Received: from [62.7.102.236] (helo=salavat)
	by tantalum with esmtp (Exim 3.03 #83)
	id 13Edb1-00024p-00
	for ietf@ietf.org; Tue, 18 Jul 2000 21:04:03 +0100
Message-ID: <00b301bff0f3$77e0bec0$ec66073e@salavat>
From: "Salavat R. Magazov" <srm4@ukc.ac.uk>
To: "IETF mailing list" <ietf@ietf.org>
Subject: Author! Author! Author!
Date: Tue, 18 Jul 2000 21:02:17 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0098_01BFF0FB.74A6A8C0"
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
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0098_01BFF0FB.74A6A8C0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit

Hello

I have read the book "Mobile IP: the Internet unplugged" and have several
ideas to exchange with the author Mr James Solomon. Could you please reply
to this e-mail

Regards
Salavat

------=_NextPart_000_0098_01BFF0FB.74A6A8C0
Content-Type: text/x-vcard;
	name="Salavat R. Magazov.vcf"
Content-Disposition: attachment;
	filename="Salavat R. Magazov.vcf"
Content-Transfer-Encoding: 7bit

BEGIN:VCARD
VERSION:2.1
N:Magazov;Salavat;R.
FN:Salavat R. Magazov
NICKNAME:Sal
ORG:University of Kent at Canterbury
TEL;HOME;VOICE:+44-1227-472835
X-WAB-GENDER:2
BDAY:20000517
EMAIL;PREF;INTERNET:srm4@ukc.ac.uk
EMAIL;INTERNET:salavat@ukonline.co.uk
REV:20000718T200217Z
END:VCARD

------=_NextPart_000_0098_01BFF0FB.74A6A8C0--



From owner-ietf-outbound  Tue Jul 18 16:21:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA28056
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 16:20:04 -0400 (EDT)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20824
	for <ietf@ietf.org>; Tue, 18 Jul 2000 16:04:33 -0400 (EDT)
From: Jim_Stephenson-Dunn@3com.com
Received: from new-york.3com.com (new-york.3com.com [129.213.157.12])
	by seattle.3com.com (8.8.8/8.8.8) with ESMTP id NAA14092;
	Tue, 18 Jul 2000 13:04:03 -0700 (PDT)
Received: from hqoutbound.ops.3com.com (hqoutbound.OPS.3Com.COM [139.87.48.104])
	by new-york.3com.com (8.8.8/8.8.8) with SMTP id NAA03649;
	Tue, 18 Jul 2000 13:03:37 -0700 (PDT)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256920.006E1E86 ; Tue, 18 Jul 2000 13:02:47 -0700
X-Lotus-FromDomain: 3COM
To: "Steven M. Bellovin" <smb@RESEARCH.ATT.COM>
cc: Matt Holdrege <matt@ipverse.com>, Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>,
        ietf@ietf.org
Message-ID: <88256920.006E1CC2.00@hqoutbound.ops.3com.com>
Date: Tue, 18 Jul 2000 13:01:10 -0700
Subject: Re: Email Privacy eating software
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org



I have had a similar experience to the one reported in the article, and was meet
with a similar dejected mood when they fired up my laptop to find not the usual,
nice, graphical widows desktop but Linux, The officer in question picked up a
phone and said to his colleague, It doesn't look like windows I think it is
something else. When I said it was UNIX, he visibly paled in front of me, and
waved me through.

So it would appear that if you are a terrorist, bomb maker, subversive or have a
hard disk full of pornography and plan to travel to London for the IETF meeting
or anything else for that matter, I would recommend trading in your Laptop's
running windows for an Apple or in my case a laptop running Linux, which cannot
be scanned.

It is sometimes kind of silly, but I am also English (working in the US) and
frankly, I have to admit that in the grand scheme of things I do sleep slightly
better at night knowing that these people (H.M. Customs & Excise and even U.S.
Customs) are there plugging away for us, I am sure that the way they look at it
,they also do not want to be doing it, but every so often they must catch a bad
person. (notice, I did not say guilty ;->) that they can charge with something
really heinous.

And let us not forget that these people are enforcing the law that the
politicians make.

What we need IMHO is more understanding by the legislators, without this we are
doomed to have our time wasted by ineffectual laws that serve no real purpose
other than to waste people's time and slow them down instead of protecting the
public interest.

The future may hold that if you are running the non-de facto O/S like MacOS or
Linux then you are technically guilty of encrypting data, because the guy that
wants to search your hard disk is only trained on the commands and how to
navigate the windows file system and no other.
Maybe the NSA will classify Linux and other non windows operating systems as
munitions of war ;-> (which would be interesting seeing as I recall they (NSA)
also run Linux, something about better security)


Jim



**************************************************************************************
       Legal Disclaimer


The opinions expressed within this mail are specifically my own and in no way
refer to or relate to any
ongoing business and/or the technical direction of 3Com Corporation, or any
subsidiary companies or
business units within 3Com Corporation and its subsidiaries.


**************************************************************************************








"Steven M. Bellovin" <smb@RESEARCH.ATT.COM> on 07/18/2000 11:45:14 AM

Sent by:  "Steven M. Bellovin" <smb@RESEARCH.ATT.COM>


To:   Matt Holdrege <matt@ipverse.com>
cc:   Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>, ietf@ietf.org (Jim
      Stephenson-Dunn/C/HQ/3Com)
Subject:  Re: Email Privacy eating software



In message <4.3.1.2.20000718105915.00bd2de0@pop3.ipverse.com>, Matt Holdrege wr
ites:
>At 11:50 AM 7/18/00 +0100, Jon Crowcroft wrote:
>>next summer's IETF meeting is tentatively scheduled for London, England
>>http://www.ietf.org/meetings/0mtg-sites.txt
>>
>>if you turn up at customs with a laptop, you may be asked to show any
>>and all files on it to the nice chaps there. if someone has sent you
>>crypted email (say using your public key) you may be obliged to
>>connect the lapto pto the public net and  access your other key to
>>decrypt the mail for the nice chaps in customs to priove that it is
>>not to do with pornography or terrorism - whereeve yo uare from, you
>>will have no recourse to say "no" or "this is commercial in
>>confidence" or "my company will fire me if i let this go to anyone or
>>send it over the net to decrypt at my home site etc etc"
>
>As one who travels to London quite often and has red hair and is of Irish
>descent, this sounds a bit overmuch to me. I've never had anything other
>than a kind welcome by British customs officials. There are loads of crazy
>laws in the U.S. and other countries. We citizens are grateful that the
>enforcement branch of the government chooses to ignore them unless provoked.
>
>
I'm not sure what "sounds a bit overmuch" to you.  Have a look at
http://news.bbc.co.uk/hi/english/sci/tech/newsid%5F150000/150465.stm


          --Steve Bellovin








From owner-ietf-outbound  Tue Jul 18 18:51:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA02106
	for ietf-outbound.10@ietf.org; Tue, 18 Jul 2000 18:50:02 -0400 (EDT)
Received: from infidel.boolean.net (root@router.boolean.net [198.144.206.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00200;
	Tue, 18 Jul 2000 18:45:01 -0400 (EDT)
Received: from gypsy.OpenLDAP.org (gypsy.boolean.net [198.144.202.243])
	by infidel.boolean.net (8.9.3/8.9.3) with ESMTP id WAA32692;
	Tue, 18 Jul 2000 22:44:57 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <4.3.2.7.0.20000718143734.00b164a0@infidel.boolean.net>
X-Sender: guru@infidel.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 18 Jul 2000 15:44:56 -0700
To: IETF-LDAPbis@OPENLDAP.ORG, agenda@ietf.org
From: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Subject: LDAP (v3) Revision BOF (LDAPbis)
Cc: IETF-LDAPext@netscape.com, IETF-LDUP@IMC.ORG, IETF@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

This is the final IETF#48 LDAPbis BOF agenda.
Those interested are encouraged to attend.

Regards, Kurt

--- cut here ---

NAME: LDAP (v3) Revision BOF
ACRONYM: LDAPbis

CHAIRS:
  Kurt Zeilenga <kurt@openldap.org>
  RL "Bob" Morgan <rlmorgan@washington.edu>

MAILING LIST:
  Archives: http://www.openldap.org/lists/ietf-ldapbis/
  Subscribe: mailto:ietf-ldapbis-request@OpenLDAP.org?body=subscribe
  Post: mailto:ietf-ldapbis@OpenLDAP.org
  Policy: You must be subscribed to post.

INTRODUCTION:
  LDAPv3 core specifications (RFC 2251-56) must be revised if
  they are to be progressed to Draft Standard per the IESG
  Note contained within these documents.  With the approval
  of RFC 2829 and 2830, the necessary secure authentication
  mechanisms to obtain Draft Standard status are now available.

  In addition, the community has obtain a wealth of operational
  experience using the current specifications.  The community
  has identified a number of areas where the specifications
  need to amended.  These amendments include a few significant
  substantive changes, a fair number of lessor substantive changes,
  and many clarifications.  A forum for discussing and addressing
  these issues is needed.

PURPOSE:
  The purpose of this BOF is to discuss proposed updates to the
  LDAPv3 core protocol specification (RFC 2251-56, 2829-30),
  to identify work items, and discuss formation of a working
  group specifically chartered to address identified work items.

  Extensions to LDAPv3 are not within the scope of this BOF
  as this is the realm of existing IETF working groups.

BACKGROUND:
  The LDAPv3 specifications were developed by the ASID and
  LDAPext working groups.  The ASID working group is defunct.
  The LDAPext WG is focused on significant protocol extensions
  such as Access Control, APIs, Referrals, and CLDAP.  A separate
  working group is currently proposed to focus energies to address
  LDAPv3 specification updates while not distracting LDAPext from
  their chartered work.  However, at the discretion of the IESG,
  work items identified by this BOF may be assigned to LDAPext
  or other appropriate WG (after appropriate charter review).

TIME/PLACE:
  WEDNESDAY, August 2, 2000, 1530-1730
 
AGENDA:
  Agenda Bashing
  Introduction, Chair(s), 10m
    Extent of suggested changes
    LDAPv3 vs LDAPv4
  IESG Note, AD, 5m
  LDAPv3 Applicability Statement, JeffH, 10m
  Relationship to X.500, MarkW, 10m
  Reorganisation of the Specification, MarkW, 5m
  Other Issues, TBD, 10m
  Next Steps, Chair(s), 10m

  I-D Review (as time permits), Author(s), 1hr (5m/I-D)
  Order to be determined by chair(s)

READING MATERIALS:
  RFC 2251-2256,2829,2830

  draft-armijo-ldap-control-error-00.txt 
  draft-hodges-ldapv3-as-00.txt
  draft-just-ldapv3-rescodes-02.txt
  draft-rharrison-ldap-extpartresp-01.txt
  draft-smith-ldapv3-dn-update-00.txt
  draft-smith-ldapv3-url-update-00.txt
  draft-zeilenga-ldapv3bis-opattrs.txt
  draft-zeilenga-ldapv3bis-rfc2251.txt
  draft-zeilenga-ldapv3bis-rfc2252.txt
  draft-zeilenga-ldapv3bis-rfc2253.txt
  draft-zeilenga-ldapv3bis-rfc2254.txt
  draft-zeilenga-ldapv3bis-rfc2255.txt
  draft-zeilenga-ldapv3bis-rfc2256.txt
  draft-zeilenga-ldapv3bis-rfc2829.txt
  draft-zeilenga-ldapv3bis-rfc2830.txt 



From owner-ietf-outbound  Wed Jul 19 03:12:04 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA07988
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 03:10:03 -0400 (EDT)
Received: from carbon.btinternet.com (carbon.btinternet.com [194.73.73.92])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01862
	for <ietf@ietf.org>; Wed, 19 Jul 2000 02:56:11 -0400 (EDT)
Received: from [213.1.145.106] (helo=patonmj)
	by carbon.btinternet.com with smtp (Exim 3.03 #83)
	id 13Enlx-0007Pq-00; Wed, 19 Jul 2000 07:56:01 +0100
From: "mark.paton" <mark.paton@btinternet.com>
To: "Eli Sanchez" <geekfreak2000@yahoo.com>, "Greg Skinner" <gds@BEST.COM>,
        <ietf@ietf.org>
Subject: RE: draft-ietf-nat-protocol-complications-02.txt
Date: Wed, 19 Jul 2000 07:59:51 +0100
Message-ID: <NCBBINIKLKLJEEDCGLOAEEGFCHAA.mark.paton@btinternet.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0028_01BFF157.51A156C0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901
In-reply-to: <20000718150202.4234.qmail@web4601.mail.yahoo.com>
Importance: Normal
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0028_01BFF157.51A156C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

I think we are moving off subject here, why not
drop the thread and concentrate on the job in
hand!!

Regards

Mark Paton CEO/DIR. Internet Network Eng
Mercury Network Systems Limited
+44 585 649051
+44 1256 761925
http://www.mnsl.org

"Mercury Network Systems - The Unstoppable Force"

This e-mail is intended only for the addressee
named above. As this e-mail may contain
confidential or privileged information if you are
not, or suspect that you are not, the named
addressee or the person responsible for delivering
the message to the named addressee, please
telephone us immediately. Please note that we
cannot guarantee that this message or any
attachment is virus free or has not been
intercepted and amended.


The views of the author may not necessarily
reflect those of the Company.


-----Original Message-----
From: Eli Sanchez [mailto:geekfreak2000@yahoo.com]
Sent: 18 July 2000 16:02
To: Greg Skinner; ietf@ietf.org
Subject: Re:
draft-ietf-nat-protocol-complications-02.txt


Wrong I'm reading it :P  Leave AOL alone.
 There are
many FREE connections to select one can
have AOL and
many other "raw" connections.  Maybe we
like AOL, and
that is why we pick it.  AOlers also know that AOL
isnt top class but we like easy listening
once in a
while :P We're not all idiots and
although there are
some exceptions we have brains to!

-Eli

--- Greg Skinner <gds@best.com> wrote:
> Masataka Ohta wrote:
>
> > If IETF makes it clear that AOL is
not an ISP, it
> will commercially
> > motivate AOL to be an ISP.
>
> Why?  Certainly, they are aware that
they are not an
> ISP by your
> definition.  It hasn't changed their business
> practices.  Why would
> an IETF RFC change their business
practices?  The
> business practices
> of AOL are determined, for the most
part, by what
> Wall Street and
> their customers think is important, not what the
> IETF thinks.  Most
> of their customers are unlikely to read
such an RFC
> anyway.
>
> --gregbo
>


__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail – Free email you can
access from anywhere!
http://mail.yahoo.com/


------=_NextPart_000_0028_01BFF157.51A156C0
Content-Type: text/x-vcard;
	name="Mark. J.S Paton.vcf"
Content-Disposition: attachment;
	filename="Mark. J.S Paton.vcf"
Content-Transfer-Encoding: quoted-printable

BEGIN:VCARD
VERSION:2.1
N:Paton;Mark.;J.S;;
FN:Mark. J.S Paton
ORG:Mnsl;Consultancy
TITLE:Network Design / Support
TEL;WORK;VOICE:+44 0585 649051
TEL;CELL;VOICE:+44 (0585) 649051
ADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;Basingstoke;Willow =
Cottage=3D0D=3D0AReading Road;Mattingley;Hampshire;RG27 8JU;=3D
United Kingdom
LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:Basingstoke=3D0D=3D0AWillow =
Cottage=3D0D=3D0AReading Road=3D0D=3D0AMattingley, Hampshire=3D
 RG27 8JU=3D0D=3D0AUnited Kingdom
URL:
URL:http://www.mnsl.org
EMAIL;PREF;INTERNET:mark.paton@mnsl.org
REV:19990422T133901Z
END:VCARD

------=_NextPart_000_0028_01BFF157.51A156C0--



From owner-ietf-outbound  Wed Jul 19 04:21:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA05046
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 04:20:02 -0400 (EDT)
Received: from wellington.cnchost.com (wellington.concentric.net [207.155.252.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03499
	for <ietf@ietf.org>; Wed, 19 Jul 2000 04:15:13 -0400 (EDT)
Received: from MATT.ascend.com (ts011d19.lap-ca.concentric.net [64.1.212.31])
	by wellington.cnchost.com
	id EAA15834; Wed, 19 Jul 2000 04:15:10 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.8]
Errors-To: <matt@ipverse.com>
Message-Id: <4.3.1.2.20000719011133.00ca2ea0@pop3.ipverse.com>
X-Sender: matt@ipverse.com@pop3.ipverse.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 19 Jul 2000 01:16:18 -0700
To: "Steven M. Bellovin" <smb@research.att.com>
From: Matt Holdrege <matt@ipverse.com>
Subject: Re: Email Privacy eating software 
Cc: ietf@ietf.org
In-Reply-To: <20000718184514.BD10135DC2@smb.research.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 02:45 PM 7/18/00 -0400, Steven M. Bellovin wrote:
>In message <4.3.1.2.20000718105915.00bd2de0@pop3.ipverse.com>, Matt 
>Holdrege wr
>ites:
> >At 11:50 AM 7/18/00 +0100, Jon Crowcroft wrote:
> >>next summer's IETF meeting is tentatively scheduled for London, England
> >>http://www.ietf.org/meetings/0mtg-sites.txt
> >>
> >>if you turn up at customs with a laptop, you may be asked to show any
> >>and all files on it to the nice chaps there. if someone has sent you
> >>crypted email (say using your public key) you may be obliged to
> >>connect the lapto pto the public net and  access your other key to
> >>decrypt the mail for the nice chaps in customs to priove that it is
> >>not to do with pornography or terrorism - whereeve yo uare from, you
> >>will have no recourse to say "no" or "this is commercial in
> >>confidence" or "my company will fire me if i let this go to anyone or
> >>send it over the net to decrypt at my home site etc etc"
> >
> >As one who travels to London quite often and has red hair and is of Irish
> >descent, this sounds a bit overmuch to me. I've never had anything other
> >than a kind welcome by British customs officials. There are loads of crazy
> >laws in the U.S. and other countries. We citizens are grateful that the
> >enforcement branch of the government chooses to ignore them unless provoked.
> >
> >
>I'm not sure what "sounds a bit overmuch" to you.  Have a look at
>http://news.bbc.co.uk/hi/english/sci/tech/newsid%5F150000/150465.stm

How is this different than looking in your bags for porn magazines or 
videotapes? How is looking at your stored email different than looking at 
your paper correspondence?

As I stated in my previous post "unless provoked". Customs in many 
countries can be provoked to look at those things. What makes a computer 
special? Why single out the U.K. government when many others do essentially 
the same thing.



From owner-ietf-outbound  Wed Jul 19 07:51:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA21636
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 07:50:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18901
	for <ietf@ietf.org>; Wed, 19 Jul 2000 07:43:22 -0400 (EDT)
Received: from contactdish (atkielsk.adsl-net2-rg.nerim.net [62.4.19.136]) by atkielski.com (8.8.8) id NAA10702; Wed, 19 Jul 2000 13:43:17 +0200 (CEST)
Message-ID: <009501bff176$8ad2a9c0$0a00000a@contactdish>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <Your message of "Tue, 18 Jul 2000 11:35:41 +0200." <008601bff09b$8b32e9b0$0a00000a@contactdish> <4.3.1.2.20000718105915.00bd2de0@pop3.ipverse.com>
Subject: Re: Email Privacy eating software
Date: Wed, 19 Jul 2000 13:42:59 +0200
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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Matt Holdrege writes:

> There are loads of crazy laws in the U.S. and other
> countries. We citizens are grateful that the enforcement
> branch of the government chooses to ignore them unless
> provoked.

Some of us citizens prefer not to give the enforcement branch of the
government the opportunity for selective enforcement in the first place, and
will vote against anyone running for office who advocates opening any such
doors.  Freedom is something that you tend not to miss until it's gone.



From owner-ietf-outbound  Wed Jul 19 08:01:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA25675
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 08:00:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24534
	for <ietf@ietf.org>; Wed, 19 Jul 2000 07:56:57 -0400 (EDT)
Received: from contactdish (atkielsk.adsl-net2-rg.nerim.net [62.4.19.136]) by atkielski.com (8.8.8) id NAA12037; Wed, 19 Jul 2000 13:56:56 +0200 (CEST)
Message-ID: <00ac01bff178$70ba4b90$0a00000a@contactdish>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <4.3.1.2.20000719011133.00ca2ea0@pop3.ipverse.com>
Subject: Re: Email Privacy eating software 
Date: Wed, 19 Jul 2000 13:56:52 +0200
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.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Matt Holdrege writes:

> How is this different than looking in your bags for
> porn magazines or videotapes?

It's not.  I take it that you don't mind having your bags searched?  How
about your wallet?  Where do you draw the line, or don't you draw one?

> How is looking at your stored email different
> than looking at your paper correspondence?

It's not--but nobody looks at your paper correspondence.  Through many
centuries of familiarity, it has come to be accepted that paper
correspondence is relatively private, even by those who fail to grasp the
equivalence of correspondence stored in computers.

> As I stated in my previous post "unless provoked".

As I implied in my previous post, selective enforcement is an open door to
erosion of critical freedoms.  "Provocation" should not be a factor in
enforcement.

> Customs in many countries can be provoked to look
> at those things.

If they can be provoked into looking at those things, then it stands to
reason that they can also be persuaded to ignore them.  Which technique do
you think the bad guys are more likely to use?

> What makes a computer special?

Nothing.  It's just like, say, the sum total of all the papers and personal
effects that you have in your home.  You don't mind if someone goes through
all of those, do you?  There _might_ be something illegal among them, after
all.

> Why single out the U.K. government when many others
> do essentially the same thing.

Multiple wrongs don't make a right.  And it sounds like the U.K. has gone
further than many other countries held to be at a similar level of
"civilization" (or "civilisation").



From owner-ietf-outbound  Wed Jul 19 09:51:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA08434
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 09:50:03 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07290
	for <ietf@ietf.org>; Wed, 19 Jul 2000 09:47:11 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id JAA15094
	for <ietf@ietf.org>; Wed, 19 Jul 2000 09:47:11 -0400 (EDT)
Received: from hotair.hobl.lucent.com (h199-118-135-2.lucent.com [199.118.135.2])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with SMTP id JAA15082
	for <ietf@ietf.org>; Wed, 19 Jul 2000 09:47:10 -0400 (EDT)
Received: from lucent.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id JAA07778; Wed, 19 Jul 2000 09:47:10 -0400
Message-ID: <3975B15A.A9EACF28@lucent.com>
Date: Wed, 19 Jul 2000 09:47:06 -0400
From: Hui-Lan Lu <huilanlu@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.6 [en]C-CCK-MCD EMS-1.4  (WinNT; U)
X-Accept-Language: zh-TW,zh-CN
MIME-Version: 1.0
To: ietf@ietf.org, sip@lists.bell-labs.com, pint@lists.bell-labs.com,
        spirits@lists.bell-labs.com, iptel@lists.bell-labs.com
Subject: The New Mailing list for SIP/IN Interworking
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


A mailing list for the upcoming BOF on SIP/IN interworking (SIN) has
been set up to begin the relevant discussion. To join the list
(ietf-sin@lists.bell-labs.com), please follow the instructions at
http://lists.bell-labs.com/mailman/listinfo/ietf-sin.

Hui-Lan Lu
Lucent Technologies



From owner-ietf-outbound  Wed Jul 19 10:21:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA19853
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 10:20:03 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18295
	for <ietf@ietf.org>; Wed, 19 Jul 2000 10:15:33 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id KAA23374
	for <ietf@ietf.org>; Wed, 19 Jul 2000 10:16:23 -0400
Sender: francis@localhost.localdomain
Message-ID: <3975B837.95C3767E@ecal.com>
Date: Wed, 19 Jul 2000 10:16:23 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Email Privacy eating software
References: <4.3.1.2.20000719011133.00ca2ea0@pop3.ipverse.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Matt Holdrege wrote:

> >I'm not sure what "sounds a bit overmuch" to you.  Have a look at
> >http://news.bbc.co.uk/hi/english/sci/tech/newsid%5F150000/150465.stm
>
> How is this different than looking in your bags for porn magazines or
> videotapes? How is looking at your stored email different than looking at
> your paper correspondence?

Read it again--they were apparently going to use their program to view a known
porn site, not porn on his hard drive.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |You buttered your bread, now lie in it.      |
|francis@ecal.com|                                             |
\==============================================================/





From owner-ietf-outbound  Wed Jul 19 10:41:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA27624
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 10:40:03 -0400 (EDT)
Received: from ztxmail04.ztx.compaq.com (ztxmail04.ztx.compaq.com [161.114.1.208])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26892
	for <ietf@ietf.org>; Wed, 19 Jul 2000 10:37:51 -0400 (EDT)
Received: by ztxmail04.ztx.compaq.com (Postfix, from userid 12345)
	id 81FDA7F3; Wed, 19 Jul 2000 09:37:22 -0500 (CDT)
Received: from excreo-gh01.reo.dec.com (excreo-gh01.reo.cpqcorp.net [16.41.128.40])
	by ztxmail04.ztx.compaq.com (Postfix) with ESMTP
	id C5DB37EE; Wed, 19 Jul 2000 09:37:21 -0500 (CDT)
Received: by excreo-gh01.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <N64NLK6T>; Wed, 19 Jul 2000 15:37:20 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9D18@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'John Stracke'" <francis@ECAL.COM>, ietf@ietf.org
Subject: RE: Email Privacy eating software
Date: Wed, 19 Jul 2000 15:37:19 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

"I use the computer to access the Internet, yes," I said, rather proud of
myself for my accuracy. 
"Is there any pornography on it?" she said, stoically. 

I belive she ment the Computer not the Internet. 

-----Original Message-----
From: John Stracke [mailto:francis@ECAL.COM]
Sent: Wednesday, July 19, 2000 3:16 PM
To: ietf@ietf.org
Subject: Re: Email Privacy eating software


Matt Holdrege wrote:

> >I'm not sure what "sounds a bit overmuch" to you.  Have a look at
> >http://news.bbc.co.uk/hi/english/sci/tech/newsid%5F150000/150465.stm
>
> How is this different than looking in your bags for porn magazines or
> videotapes? How is looking at your stored email different than looking at
> your paper correspondence?

Read it again--they were apparently going to use their program to view a
known
porn site, not porn on his hard drive.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |You buttered your bread, now lie in it.      |
|francis@ecal.com|                                             |
\==============================================================/




From owner-ietf-outbound  Wed Jul 19 10:51:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA01697
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 10:50:04 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00824
	for <ietf@ietf.org>; Wed, 19 Jul 2000 10:47:41 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 13Ev8O-0006Qv-00; Wed, 19 Jul 2000 15:47:40 +0100
Date: Wed, 19 Jul 2000 15:47:36 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Hui-Lan Lu <huilanlu@lucent.com>
cc: ietf@ietf.org, sip@lists.bell-labs.com
Subject: Re: The New Mailing list for SIP/IN Interworking
In-Reply-To: <3975B15A.A9EACF28@lucent.com>
Message-ID: <Pine.GSO.4.21.0007191547080.16030-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Wed, 19 Jul 2000, Hui-Lan Lu wrote:

> A mailing list for the upcoming BOF on SIP/IN interworking (SIN) has
> been set up to begin the relevant discussion. To join the list
> (ietf-sin@lists.bell-labs.com), please follow the instructions at
> http://lists.bell-labs.com/mailman/listinfo/ietf-sin.

"The current archive is only available to the list members."?

Not very spirit-of-IETF.

L.

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



From owner-ietf-outbound  Wed Jul 19 11:11:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA09453
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 11:10:04 -0400 (EDT)
Received: from hesketh.net (wasabi-eth0-1.hesketh.net [216.27.10.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07100
	for <ietf@ietf.org>; Wed, 19 Jul 2000 11:04:13 -0400 (EDT)
Received: from thinkpadssl (ith1-3c4.twcny.rr.com [24.24.11.196])
	by hesketh.net (8.9.3/8.9.3) with SMTP id LAA25591
	for <ietf@ietf.org>; Wed, 19 Jul 2000 11:04:12 -0400
Message-Id: <200007191504.LAA25591@hesketh.net>
X-Received-From: simonstl@simonstl.com
X-Delivered-To: <ietf@ietf.org>
X-Sender: simonstl@216.27.10.33
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 
Date: Wed, 19 Jul 2000 11:06:57 -0400
To: ietf@ietf.org
From: "Simon St.Laurent" <simonstl@simonstl.com>
Subject: Re: The New Mailing list for SIP/IN Interworking
In-Reply-To: <Pine.GSO.4.21.0007191547080.16030-100000@petra.ee.surrey.a
 c.uk>
References: <3975B15A.A9EACF28@lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 03:47 PM 7/19/00 +0100, Lloyd Wood wrote:
>On Wed, 19 Jul 2000, Hui-Lan Lu wrote:
>
>> A mailing list for the upcoming BOF on SIP/IN interworking (SIN) has
>> been set up to begin the relevant discussion. To join the list
>> (ietf-sin@lists.bell-labs.com), please follow the instructions at
>> http://lists.bell-labs.com/mailman/listinfo/ietf-sin.
>
>"The current archive is only available to the list members."?
>
>Not very spirit-of-IETF.

Perhaps that's in keeping with the name "ietf-sin"?

Simon St.Laurent
XML Elements of Style / XML: A Primer, 2nd Ed.
http://www.simonstl.com - XML essays and books



From owner-ietf-outbound  Wed Jul 19 12:13:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA05258
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 12:10:02 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01603
	for <ietf@ietf.org>; Wed, 19 Jul 2000 12:02:04 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id MAA27419
	for <ietf@ietf.org>; Wed, 19 Jul 2000 12:02:04 -0400 (EDT)
Received: from hotair.hobl.lucent.com (h199-118-135-2.lucent.com [199.118.135.2])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with SMTP id MAA27402;
	Wed, 19 Jul 2000 12:02:04 -0400 (EDT)
Received: from lucent.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id MAA20761; Wed, 19 Jul 2000 12:02:03 -0400
Message-ID: <3975D0FA.3C736E5A@lucent.com>
Date: Wed, 19 Jul 2000 12:02:02 -0400
From: Hui-Lan Lu <huilanlu@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.6 [en]C-CCK-MCD EMS-1.4  (WinNT; U)
X-Accept-Language: zh-TW,zh-CN
MIME-Version: 1.0
To: L.Wood@eim.surrey.ac.uk
CC: ietf@ietf.org, sip@lists.bell-labs.com
Subject: Re: The New Mailing list for SIP/IN Interworking
References: <Pine.GSO.4.21.0007191547080.16030-100000@petra.ee.surrey.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit




Lloyd Wood wrote:
> 
> On Wed, 19 Jul 2000, Hui-Lan Lu wrote:
> 
> > A mailing list for the upcoming BOF on SIP/IN interworking (SIN) has
> > been set up to begin the relevant discussion. To join the list
> > (ietf-sin@lists.bell-labs.com), please follow the instructions at
> > http://lists.bell-labs.com/mailman/listinfo/ietf-sin.
> 
> "The current archive is only available to the list members."?
> 
> Not very spirit-of-IETF.

The archive is now set to be public. Thanks for spotting the problem.

Hui-Lan Lu
Lucent Technologies



From owner-ietf-outbound  Wed Jul 19 18:21:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA06698
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 18:20:02 -0400 (EDT)
Received: from europe.std.com (europe-e.std.com [192.74.137.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03498
	for <ietf@ietf.org>; Wed, 19 Jul 2000 18:10:58 -0400 (EDT)
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 SAA25144;
	Wed, 19 Jul 2000 18:10:55 -0400 (EDT)
Received: from localhost (brunner@localhost)
	by world.std.com (8.9.3/8.9.3) with SMTP id SAA09826;
	Wed, 19 Jul 2000 18:10:55 -0400 (EDT)
Message-Id: <200007192210.SAA09826@world.std.com>
X-Authentication-Warning: world.std.com: brunner@localhost didn't use HELO protocol
To: ietf@ietf.org
cc: J.Crowcroft@CS.UCL.AC.UK
Subject: RE: Email Privacy eating software
Date: Wed, 19 Jul 2000 18:10:55 -0400
From: Eric Brunner <brunner@world.std.com>
X-Loop: ietf@ietf.org

[from BENTON-COMPOLICY@CDINET.COM, (www.benton.org/News/)
 Communications-related Headlines for 7/19/2000
]

BRITISH AUTHORITIES MAY GET WIDE POWER TO DECODE E-MAIL
Issue: Privacy/International
Britain may adopt a law making it the only Western democracy where the
government could require anyone using the Internet to turn over the keys to
decoding e-mails messages and other data. "The powers in the bill are
necessary and proportionate to the threat posed by 21st century criminals,
no more, no less," Charles Clarke, the Home Office official in charge of the
bill, said last week. The legislation would allow the British government to
tap into and monitor electronic communication for a host of reasons,
including to protect national security, to "safeguard the country's
well-being," and to prevent and detect serious crime. That last,
far-reaching category might include, for instance, "a large number of
persons in pursuit of a common purpose." The measure would not require
traditional warrants signed by judges. "This is Big Brother government
realizing that unless they get their act together, technology is going to
make them impotent by allowing individuals to bypass the regulations, and
the spies, of the state," said Ian Angell, professor of information systems
at the London School of Economics and a consultant on the recent report.
"I'm a supporter of the police, and I believe they should be given powers,
but there has to be due process, and this bill doesn't provide that," Mr.
Angell said. "They'll be allowed to go on fishing expeditions."
[SOURCE: New York Times (A3), AUTHOR: Sarah Lyall]



From owner-ietf-outbound  Wed Jul 19 19:01:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA20142
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 19:00:04 -0400 (EDT)
Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19789
	for <ietf@ietf.org>; Wed, 19 Jul 2000 18:59:05 -0400 (EDT)
Received: from software-munitions.com (fwiw.plaintalk.bellevue.wa.us [206.129.5.157])
	by btw.plaintalk.bellevue.wa.us (8.10.2/8.10.2) with ESMTP id e6JMwMC42403;
	Wed, 19 Jul 2000 15:58:22 -0700 (PDT)
Message-ID: <3976328E.5741D73F@software-munitions.com>
Date: Wed, 19 Jul 2000 15:58:22 -0700
From: Dennis Glatting <dennis.glatting@software-munitions.com>
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Brunner <brunner@WORLD.STD.COM>
CC: ietf@ietf.org, J.Crowcroft@CS.UCL.AC.UK
Subject: Re: Email Privacy eating software
References: <200007192210.SAA09826@world.std.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Eric Brunner wrote:
> 
> [from BENTON-COMPOLICY@CDINET.COM, (www.benton.org/News/)
>  Communications-related Headlines for 7/19/2000
> ]
> 
> BRITISH AUTHORITIES MAY GET WIDE POWER TO DECODE E-MAIL

Perhaps at the Pittsburgh plenary we should discuss whether we want to
move the London meeting elsewhere, least all of our lap tops be
"scanned" and cryto keys surrendered.



From owner-ietf-outbound  Wed Jul 19 21:32:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA10822
	for ietf-outbound.10@ietf.org; Wed, 19 Jul 2000 21:30:04 -0400 (EDT)
Received: from mailgate.sbell.com.cn (mailgate.sbell.com.cn [202.96.203.173])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09798
	for <ietf@ietf.org>; Wed, 19 Jul 2000 21:26:52 -0400 (EDT)
Received: from bellnet-mail3.sbell.com.cn (bellnet-mail3.sbell.com.cn [202.96.203.172])
	by mailgate.sbell.com.cn (8.9.2/8.9.2) with ESMTP id JAA01732
	for <ietf@ietf.org>; Thu, 20 Jul 2000 09:19:13 +0800 (CST)
Received: by bellnet-mail3.sbell.com.cn with Internet Mail Service (5.5.2448.0)
	id <N23NDXGT>; Thu, 20 Jul 2000 09:25:43 +0800
Message-ID: <77D4835D5290D111B8CC00805FE6AAD504A7F910@bellnet-mail1.sbell.com.cn>
From: SRD Ye JianLiang <SVCYJL@sbell.com.cn>
To: ietf@ietf.org
Subject: does there have any rfc documents about NAS(Net Access Server)?
Date: Thu, 20 Jul 2000 09:25:41 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Loop: ietf@ietf.org




From owner-ietf-outbound  Thu Jul 20 00:53:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA23521
	for ietf-outbound.10@ietf.org; Thu, 20 Jul 2000 00:50:02 -0400 (EDT)
Received: from muSys.com (techno.musys.com [199.190.178.75])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA19924
	for <ietf@ietf.org>; Wed, 19 Jul 2000 23:15:06 -0400 (EDT)
Received: (from miyata@localhost)
	by muSys.com (8.8.6/8.8.6) id XAA04494
	for ietf@ietf.org; Wed, 19 Jul 2000 23:15:05 -0400 (EDT)
Date: Wed, 19 Jul 2000 23:15:05 -0400 (EDT)
From: "Gaylord K. Miyata" <miyata@muSys.com>
Message-Id: <200007200315.XAA04494@muSys.com>
To: ietf@ietf.org
Subject: V5.2 MIBs?
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org


Are there any V5.2 MIB definitions/specifications in the public 
domain?  Searches aren't coming up with anything.

Thanks,

	- gaylord



From owner-ietf-outbound  Thu Jul 20 02:13:01 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA12709
	for ietf-outbound.10@ietf.org; Thu, 20 Jul 2000 02:10:03 -0400 (EDT)
Received: from snipe.prod.itd.earthlink.net (snipe.prod.itd.earthlink.net [207.217.120.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02460
	for <ietf@ietf.org>; Thu, 20 Jul 2000 02:00:11 -0400 (EDT)
Received: from earthlink.net (pool0526.cvx19-bradley.dialup.earthlink.net [209.179.246.16])
	by snipe.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id WAA29237;
	Wed, 19 Jul 2000 22:58:19 -0700 (PDT)
Message-ID: <39766AEF.B13828BA@earthlink.net>
Date: Wed, 19 Jul 2000 22:58:55 -0400
From: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
X-Mailer: Mozilla 4.08 [en] (Win95; I)
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
CC: aboba@internaut.com, "=?us-ascii?Q?'Patrik Faltstrom'? =" <paf@cisco.com>,
        "'Randy Bush'" <randy@psg.com>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <200007122233.HAA27697@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

g'day,

Masataka Ohta wrote:
.  .  .
> If IETF makes it clear that AOL is not an ISP, it will commercially
> motivate AOL to be an ISP.

Not to be unkind, since the IETF has done some good work, but the above
statement is incorrect. If you'd written "If AOL perceives that the
market would punish them if the IETF makes it clear that AOL is not an
ISP, it will commercially motivate AOL to be an ISP" you might be closer
to the mark. 

The bottom line is, the world isn't waiting for us to tell them the
right way to do what they want and the clever solutions we came up with
as solutions to the networking problems of 1970, or 1980, or 1990 don't
demand that they adopt our proposals for solving their problems of 2000.
We're in serious danger of surrendering to the same elitist posturing
for which we used to vilify the mainframe community. Pity, but we'll
have only ourselves to blame if and when the users pass us by...


				- peterd (feeling testy this evening)

-- 
--------------------------------------------------------------------------------
Peter Deutsch                               work email: 
pdeutsch@cisco.com
Engineerng Manager
Caching & Content Routing
Content Services Business Unit                 private:
pdeutsch@earthlink.net
Cisco Systems

  "I want to die quietly and peacefully in my sleep like my granfather,
             not screaming in terror like his passengers..."

                                             - Emo Phillips
--------------------------------------------------------------------------------



From owner-ietf-outbound  Thu Jul 20 02:42:56 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA25750
	for ietf-outbound.10@ietf.org; Thu, 20 Jul 2000 02:40:03 -0400 (EDT)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24377
	for <ietf@ietf.org>; Thu, 20 Jul 2000 02:36:52 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 35A2D4CE14; Thu, 20 Jul 2000 02:36:53 -0400 (EDT)
Received: from smb.research.att.com (secure.research.att.com [135.207.25.14])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id CAA06886;
	Thu, 20 Jul 2000 02:36:47 -0400 (EDT)
Received: from smb.research.att.com (localhost [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id D3E6835DD0; Wed, 19 Jul 2000 22:36:07 -0400 (EDT)
X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.3 #1[UCI]
From: "Steven M. Bellovin" <smb@research.att.com>
To: Matt Holdrege <matt@ipverse.com>
Cc: ietf@ietf.org
Subject: Re: Email Privacy eating software 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 19 Jul 2000 22:36:07 -0400
Sender: smb@research.att.com
Message-Id: <20000720023607.D3E6835DD0@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <4.3.1.2.20000719011133.00ca2ea0@pop3.ipverse.com>, Matt Holdrege wr
ites:

>> >
>>I'm not sure what "sounds a bit overmuch" to you.  Have a look at
>>http://news.bbc.co.uk/hi/english/sci/tech/newsid%5F150000/150465.stm
>
>How is this different than looking in your bags for porn magazines or 
>videotapes? How is looking at your stored email different than looking at 
>your paper correspondence?

Leaving out their technical limitations and assumptions (the whole 
world doesn't run Windows), the problem is that you don't know what 
they're really doing.  Indeed, the Customs officers may not -- can you 
tell from the wrapper what an arbitrary piece of software does?  A 
magazine is fairly obviously just that -- but there's a lot of very 
sensitive data on many people's laptops.  Perhaps the British 
government can be trusted -- but I can name a number of others, 
including nominal democracies, that I wouldn't trust.
>
>As I stated in my previous post "unless provoked". Customs in many 
>countries can be provoked to look at those things. What makes a computer 
>special? Why single out the U.K. government when many others do essentially 
>the same thing.

Apart from the question of what it takes to "provoke" a Customs officer 
-- skin color? -- the issue with the UK in particular is the lack of 
any checks on the powers of the House of Commons.  Usually, they show 
restraint and common sense -- but not always.  (As an aside, one of the 
Customs officials I encountered in Australia, after hearing why I was 
there, opined that the Internet was really a tool of the Devil, and 
that it was somehow related to the Mark of the Beast.  I decided not to 
argue, not even to point out that my religion knows nothing of Beasts 
nor marks thereof.)

		--Steve Bellovin




From owner-ietf-outbound  Thu Jul 20 05:24:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA04510
	for ietf-outbound.10@ietf.org; Thu, 20 Jul 2000 05:20:02 -0400 (EDT)
Received: from marvin.axion.bt.co.uk (marvin.axion.bt.co.uk [132.146.16.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00072
	for <ietf@ietf.org>; Thu, 20 Jul 2000 05:09:40 -0400 (EDT)
From: utthan.nakarmi@bt.com
Received: from cbtlipnt02.btlabs.bt.co.uk by marvin (local) with ESMTP;
          Thu, 20 Jul 2000 10:08:14 +0100
Received: by cbtlipnt02.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2651.88) id <3GKHGRKA>;
          Thu, 20 Jul 2000 10:08:13 +0100
Message-ID: <B76B75D34ACFD31180A600606DDFE79B02C90ADC@mbtlipnt04.btlabs.bt.co.uk>
To: ietf@ietf.org
Subject:  Traffic Engineering tools 
Date: Thu, 20 Jul 2000 10:08:10 +0100
X-Mailer: Internet Mail Service (5.5.2651.88)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
X-Loop: ietf@ietf.org


I am trying to assessing some traffic engineering tools features include
monitoring, measuring etc.They should be able to cope  with a large scale
mpls network. Would you have any suggestions?
Thanks in advance.
utthan



From owner-ietf-outbound  Thu Jul 20 08:21:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA00926
	for ietf-outbound.10@ietf.org; Thu, 20 Jul 2000 08:20:05 -0400 (EDT)
Received: from esebh02nok.ntc.nokia.com (esebh02nok.ntc.nokia.com [131.228.118.151])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26546;
	Thu, 20 Jul 2000 08:11:05 -0400 (EDT)
From: haitao.tang@nokia.com
Received: by esebh02nok with Internet Mail Service (5.5.2650.10)
	id <PJFP1R03>; Thu, 20 Jul 2000 15:10:37 +0300
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE104926518@eseis04nok>
To: ietf-announce-request@ietf.org
Cc: ietf@ietf.org, ietf-spatial@research.nokia.com
Subject: agenda of Spatial Location BOF (spatial -- APP)
Date: Thu, 20 Jul 2000 15:10:30 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Hi,

The attached is the description and agenda of Spatial Location BOF (spatial)
for IETF#48. Those interested are encouraged to attend. Thanks.

Regards,

Haitao Tang
James M. Polk

------------- cut here ----------------

Spatial Location BOF (spatial)

Chair(s):

Haitao Tang <haitao.tang@nokia.com>
James M. Polk <jmpolk@cisco.com>

Applications Area Director(s): 

Patrik Faltstrom <paf@cisco.com>
Ned Freed <ned.freed@innosoft.com>

Applications Area Advisor: 

Patrik Faltstrom <paf@cisco.com>

Mailing Lists:

General Discussion: ietf-spatial@research.nokia.com
To Subscribe: majordomo@research.nokia.com ('subscribe ietf-spatial' in
body)
Archive: http://www-nrc.nokia.com/mail-archive/ietf-spatial/
Other Archived Files: http://www-nrc.nokia.com/ietf-spatial/others.html

Description:

As more and more resources become available on the Internet, there are
immediate and pressing needs for some applications to acquire spatial
location information about certain resources. These applications include
navigation, emergency services, management of equipment in the field, and
other location based applications. 

However, there is no standard way for an application to get the information
over the Internet, although there are many methods to determine spatial
location of the resources. The purpose of Spatial Location WG is to develop
a protocol to solve the problem: How can an application acquire the spatial
location of an identifiable resource over/represented on the Internet, in a
reliable, secure, and scalable manner? 

The protocol delivers the spatial location of an identifiable resource from
a device that knows the location to an application that needs to know the
location of the element. The work items for the protocol, called as Spatial
Location Protocol (SLoP), are: 

1. Spatial Location Representations. There is the need to support different
location data representations/expressions. For interoperability reasons, we
need to have an absolute location system as the supported format by all SLoP
speakers. Its data format should be selected as such, e.g., longitude,
latitude, and altitude, with timestamp and accuracy. It is needed to list
all other absolute location systems and their data formats, which may be
supported by SLoP on an optional basis. Provisions should be made to support
new location systems and data formats. Support for descriptive locations,
when needed, should be added, while no syntax and standard will be defined
in the
current SLoP scope. 

2. Representation Negotiation Mechanism. There must be a representation
negotiation mechanism designed. The mechanism must be able to support the
selection of the wanted location system and data format between two SLoP
speakers. Usually, a server has some options while a client may have only
few of them. The descriptive location negotiation is not considered part of
the current SLoP scope. 

3. Security Mechanisms. There must be an authentication mechanism
selected/defined between SLoP speakers, to guarantee the
integrity/authenticity/accessibility (e.g., no spoofing and certain DOS
attacks) of the involved parties. There must be an encryption system
selected/defined to guarantee the privacy/confidentiality of the transferred
information between SLoP speakers. As an option, it would be preferred to
select/define a mechanism to guarantee availability (preventing
denial-of-service) for a SLoP speaker. Use of the authentication and/or the
encryption mechanisms should be setable by the
SLoP endpoint (user may enable or disable the use of the mechanisms). It is
done per session or per SLoP endpoint. The primary design for security in
SLoP must be end-to-end. When end-to-end security is not possible for
certain cases, then hop-by-hop security associations could be used between
the server and the client if allowed by the related policy for a target.
There are several mechanisms that can be used to build security
associations. The specific mechanisms for use are needed to be figured out.
All the mechanisms here should be affected by the related policies. 

4. Policy Mechanisms. There must be a policy specification language
selected/defined for specifying various policies that are relevant to SLoP.
A PIB must be defined for all SLoP speakers. There must be basic sets of
security policy, locatability policy, accuracy policy, and explicitness
policy defined for all SLoP users, where any new relevant policy rule can be
appended into a set if needed, given it is specified via the language.
Privacy policy is in fact built from the combination from the four policy
sets. The policy instance for a target should be available to the server
representing the target, where the policy instance tells how a server shall
serve the spatial location of the target. 

5. Server Discovery Mechanism. There should be a discovery mechanism
selected/ defined for client to find the appropriate server for a given
target when needed. 

6. Transmission and Reliability Mechanism. The design of a reliability
mechanism is affected by the transport protocol below SLoP. Various
transport protocols have different reliable levels. If TCP is selected,
there is no need to have this extra mechanism. However, TCP seems too heavy
for some SLoP speakers. UDP is thus likely to be selected. If so, a
reliability mechanism must be designed into SLoP. 

7. SLoP Message Coding Mechanism. There must be a coding mechanism selected/
designed for coding/decoding all SLoP messages. The coding mechanism must be
supported by all SLoP speakers. 

TIME/PLACE: MONDAY, July 31, 2000, 1930-2200

Pittsburgh Meeting Agenda (150 min):
 
  5 min     Agenda Bashing  

 15 min     Haitao Tang - Scope of This Effort 

 35 min     Brian Rosen - Spatial Location Protocol Requirements
            (draft-rosen-spatial-requirements-00.txt) 

 10 min     Rohan Mahy - A Simple Text Format for the Spatial Location
            Protocol (draft-mahy-spatial-simple-coord-00.txt) 
  
 10 min     Haitao Tang - Target Naming Scheme
            (draft-tang-spatial-target-00.txt) 
  
 10 min     John Loughney - Basic SLoP Architecture Proposal
            (draft-loughney-spatial-arch-00.txt) 
  
 20 min     James M. Polk - Charter Bashing 
  
 10 min     Haitao Tang - Review of Milestones and Group Status



From owner-ietf-outbound  Thu Jul 20 09:01:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA21523
	for ietf-outbound.10@ietf.org; Thu, 20 Jul 2000 09:00:04 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18464
	for <ietf@ietf.org>; Thu, 20 Jul 2000 08:54:14 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id IAA01484;
        Thu, 20 Jul 2000 08:52:49 -0400 (EDT)
Message-Id: <200007201252.IAA01484@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Peter Deutsch in Mountain View <pdeutsch@EARTHLINK.NET>
cc: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>, aboba@internaut.com,
        "=?us-ascii?Q?'Patrik Faltstrom'? =" <paf@cisco.com>,
        "'Randy Bush'" <randy@psg.com>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Wed, 19 Jul 2000 22:58:55 EDT."
             <39766AEF.B13828BA@earthlink.net> 
Date: Thu, 20 Jul 2000 08:52:49 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> The bottom line is, the world isn't waiting for us to tell them the
> right way to do what they want and the clever solutions we came up with
> as solutions to the networking problems of 1970, or 1980, or 1990 don't
> demand that they adopt our proposals for solving their problems of 2000.
> We're in serious danger of surrendering to the same elitist posturing
> for which we used to vilify the mainframe community. Pity, but we'll
> have only ourselves to blame if and when the users pass us by...

not that I disagree with you, but this is a fairly content-free statement.
yes, we are seriously deluded if we think that the industry will do 
whatever we say just because we are IETF.  but a similar statement 
could be made of any organization that had been around awhile -
including, for instance, (but by no means specifically) your employer,
a few other large gorillas, telephants, other standards bodies, etc.  
in a free market, *anyone* is in danger of becoming irrelevant.

the reason I say that your statement is content-free is that it offers
no specific criticism of IETF that can be used in a constructive fashion.

I find that the work of IETF varies in quality - much of it is quite
good, some of it mediocre, a small fraction is highly dubious.
Most IETF WGs I've worked with do not operate with an attitude like
"people will have to do what we say", but rather "how do we solve
this problem".  Most of them seem to understand that they have not
only to solve the problem, but also to make the solution technically
sound, attractive to those who would use it, and easy to deploy.

So while I'm not familiar with every area of IETF, I don't see that
IETF as a whole is suffering from the problem you describe.  If
there are specific areas or groups you think are suffering from this
problem, you would do better to direct your criticism to those
areas or groups, to defend your argument with specific examples,
and to provide constructive suggestions for improvement.

Keith



From owner-ietf-outbound  Thu Jul 20 10:31:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA10124
	for ietf-outbound.10@ietf.org; Thu, 20 Jul 2000 10:30:03 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05604
	for <ietf@ietf.org>; Thu, 20 Jul 2000 10:20:26 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id KAA27260
	for <ietf@ietf.org>; Thu, 20 Jul 2000 10:20:53 -0400
Sender: francis@localhost.localdomain
Message-ID: <39770AC5.3CDFA298@ecal.com>
Date: Thu, 20 Jul 2000 10:20:53 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Email Privacy eating software
References: <200007192210.SAA09826@world.std.com> <3976328E.5741D73F@software-munitions.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Dennis Glatting wrote:

> Perhaps at the Pittsburgh plenary we should discuss whether we want to
> move the London meeting elsewhere, least all of our lap tops be
> "scanned" and cryto keys surrendered.

Or maybe we should discuss it here, so as not to exclude people who can't
make it to Pittsburgh (particularly Europeans, who would be more likely
to go to London than to Pittsburgh).

Much as I like London, I would be in favor of moving the meeting if the
RIP bill passes.  Email is bad enough; but suppose some British police
authority notices encrypted SSH and IPSec traffic coming from the IETF
network, and demands the keys? They'd be able to use those keys to
connect to our (nominally) secure networks.

It might also be useful for the British organizations lobbying against
RIP if they could point to an IETF boycott as evidence that RIP was
harming British companies.  (Or it might not, of course; Parliament might
decide they didn't like being threatened.)

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Never do card tricks for your poker buddies. |
|francis@ecal.com|                                             |
\==============================================================/





From owner-ietf-outbound  Thu Jul 20 17:18:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA08342
	for ietf-outbound.10@ietf.org; Thu, 20 Jul 2000 17:17:06 -0400 (EDT)
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 RAA02709
	for <ietf@ietf.org>; Thu, 20 Jul 2000 17:06:01 -0400 (EDT)
Received: from [192.168.0.1] (ipa80.trenton2.nj.pub-ip.psi.net [38.26.139.80])
	by eagle.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id OAA15074
	for <ietf@ietf.org>; Thu, 20 Jul 2000 14:06:00 -0700 (PDT)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <p0432042db59d18413a99@[192.168.0.1]>
Date: Thu, 20 Jul 2000 17:02:32 -0400
To: ietf@ietf.org
From: Gordon Cook <cook@cookreport.com>
Subject: 100th Issue of The COOK Report on Internet  (September 2000)
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Caimis Launched as CAIDA Commercial Spin Off
Goal Is to Give Internet Industry its First Production Quality 
Network Management, Traffic Analysis and Location Sensitive 
Measurement Tools				pp. 1 - 8,

We interview Tracie Monk, Kim Claffy (kc), David Moore, and Daniel 
McRobb on the details of CAIDA's creation of Caimis.  Caimis 
www.caimis.com is a profit making spin off from CAIDA that will take 
many of CAIDA's research oriented, network traffic management tools 
and upgrade them to production quality commercial software for use by 
major ISPs.  Kc explains the CAIDA Internet Teaching Laboratory 
program, the san Diego Nap and plans for OC48 mon - as well as 
CAIDA's work on defining and understanding the Internet core.

The Caimis web site went live on July 12.  This interview is the 
first detailed description of Caimis to be published.  Caimis will 
focus on monitoring systems, network management systems and 
geographic location systems. In the monitoring area it will offer a 
variety of solutions that are for passive and active monitoring 
through active polling and passive analysis of router and link data. 
Its network management systems will be used for acquiring, storing, 
correlating, and analyzing data. The third area, geographic 
localization services, involves a set of solutions aimed at mapping 
different types of network data to geographic locations. It is the 
latter area that has direct relevance for e-commerce and financial 
transactions.

In June Caimis formed an affiliate company, Caimis Geo, Inc., to 
develop the geographic location services business. These will be 
tools aimed more towards content providers or e-commerce websites, 
where they want to know where their customers are actually located - 
perhaps because they have restrictions on distribution of software to 
people in different regions, restrictions that are geographically 
based or by country.  Or, you might have web sites that might want to 
change the language presented on their homepage depending on which 
country the user is coming from or return targeted content based on 
where the user lives, e.g., content appropriate to Southern 
California versus Boston.

Caimis finds that ISP service level agreements generally still do not 
measure up to the standards that business to business customers 
expect to see. Hewlett Packard, Cabletron and Seagate produce network 
management systems but do so without an adequate understanding of the 
Internet problem domain. While current solutions can tell network 
engineers what's going on with a particular router, when that ISP needs 
to move up to something like defining an end-to-end service for a 
particular customer, there is a big void. Providing such solutions 
are challenges that happen both within and between providers.

When you start talking about inter-providers, the situation gets 
worse. Information can't be exchanged. Providers don't want to 
provide any sort of service level guarantees for infrastructure that 
they don't control and to which they have no access. Among the things 
that need to be done are the creation of some sort of common 
interfaces that providers can use within their own network, but 
between different systems.  For example provisioning and network 
management itself, and element management. Today, basically most of 
the network management systems sit in the element level, meaning they 
tell you what's going on with particular devices in the network. They 
don't interface well with any of the other business processes within 
a provider.  These are the customer care processes, billing, 
provisioning, ordering, trouble-ticketing, which is a big problem in 
providing service to the business-to-business environment. Ironically 
in this respect the ILECs have better systems than the Internet 
industry.  Caimis intends to solve that shortcoming.

Caimis has two offices. The San Diego headquarters is focusing on the 
development of the geographic-locations services under Caimis Geo, 
Inc.  The San Diego headquarters will also be doing all of the 
productization, sales and distribution of all of Caimis monitors and 
network management systems. The Ann Arbor office will be the leading 
edge site for senior software and network engineers who are doing 
customized network management solutions. They will be the ones 
staying on the cutting edge technology-wise and requirement-wise for 
the large providers. San Diego will take some of these solutions and 
develop standardized products that can then be distributed and made 
available for the smaller ISPs, enterprises, and others.

Cogent  Communications  Guarantees 100 Mbs Internet for $1000 per 
Month Buys Dark Fiber and Builds National Network Optimized Entirely for 
Data - Business Model Emphasizes 100 BaseT LAN Interconnection in 
Buildings it Serves			pp. 9 - 14

We interview Dave Schaeffer, CEO of Cogent which n July 17th 
announced $90 million dollars in second round venture capital 
fnding..  Cogent is the first national ISP to be formed with the 
business model made possible by the new combination of SONET free 
fiber, gigabit Ethernet and dense wave division multiplexing.  This 
technology permits IP data networks to be built for  only one one -
hundredth of the cost of their voice equivalents less than 10 years 
ago.  It will use a two hundred million dollar 30 year IRU on a pair 
of fibers from the Williams  Communications Network and  fiber from 
Metromedia to connect  office buildings in twenty cities nationwide.  
It will offer tenants of these buildings 100 megabit per second 
internet connectivity for $1000 per month. Cogent has signed 
commitments to spend more than $600 million on its build out. Without  
SONET  equipment Cogent is protecting its network at layer 3.  It 
describes itself as a facilities-based nationwide switched LAN.

Gigabit Ethernet is used in their local loop.  SONET framing in long 
haul.  The SONET framing is a transport standard that is built into 
the Cisco routers.  Consequently there is no additional cost.  In the 
event of a fiber cut instead of 50 milli-second SONET based recovery, 
they  get one second recovery at the router level which, for data, is 
adequate. Any physical disruption in service would cause the core 
routers to start rerouting packets.  This process takes about one 
second.  Cogent promises to give its customers a full 100 megabits of 
band width pledging not to put more than 96 on a OC192 -  or 9.6 
gigabit - loop  of 1500 miles in length.

Schaeffer explains how Cogent selected its fiber providers.  He notes 
that: "There are some vendors whose equipment will only work with 
certain physical shelter spacing.  As we evaluated our potential dark 
fiber vendor, we looked for that network vendor whose shelter spacing 
would support the maximum number of equipment vendors. Note that the 
shelter spacings are not inter connect points.  They are there only 
to amplify the signal.  All that we need to be able to do is to rent 
standard size rack space in the shelters."  He points out that "fiber 
can be optimized for the number of wave lengths, for distance or for 
the power applied to it.  There are a number of different design 
criteria and each vendor takes a slightly different approach to which 
of those criteria they emphasize with their fiber."

Schaeffer developed a matrix for the evaluation and selection of both 
his long distance and metropolitan area software.  He discusses in 
detail how Cogent arrived at the decisions for selecting and 
integrating both sets of equipment.  Cogent's Network will open in 
New York, Philadelphia, Washington and Chicago in October.


GAO Report Shatters ICANN Founding Myths:  Neither Privatizaton Nor 
Power Sharing 	--	Policy Control Over Operation and Content of 
the "Authoritative" Root - ICANN's Single Biggest Prize - Remains 
with US Government			pp. 15 - 21

We describe how ICANN marches onward to the chant of its own version 
of reality.  The GAO report released in July 7 found ICANN's creation 
to have been legal but it could not find any support for the idea 
that the Department of Commerce had the right to manage the root.  It 
concluded that it was also very doubtful that the DoC had the legal 
right to give control of the root to ICANN saying that it did not 
look exhaustively at this point because the DoC told it that it had 
no intention of doing so anyway.  In Yokohama only a few days later 
Beckwith Burr proceeded to muddy the waters by stating that she was 
prepared to give ICANN operational but not policy control of the 
root.  An ominous development considering ICANN's statement that it 
was ready to demand that the root sever operators sign contracts with 
it.

After having caved in rather than face discovery on its first 
lawsuit, at Yokohama the ICANN Board proceeded quite skillfully to 
disarm its next, potentially more serious, opponent IO Design.  
Having given the impression that it might rule on who would get in 
the root, it collected a number of TLD applicants on its web site, 
lied that it had consensus for only a very small number of new top 
level domains, (between 1 and 3) set up a $50,000 application fee and 
then announced that it would receive applications August 1 and 
announce the winners on October 1.  In one swift move it deprived IO 
design of both due process and anti-trust grounds for suing it.  It 
will choose on October first .eu and a gTLD that will have no 
negative baggage for its trademark rulers.  Dot web will not be in 
the running.

The Board also showed its continuing fear of letting in any outside 
influence that might expose its operations to public view.  For the 
ninth time in less than two years ICANN changed its by-laws.  To 
ensure continued control by the original Dyson, Roberts, Touton 
cabal, it extended once again the terms of four of the original 
directors through the annual meeting in November 2002.  It decided to 
study the question of whether it should even have an at large 
membership.  In its efforts to make certain that no one outside the 
original cabal would ever have a voice it entered the following 
paragraph into its by laws: "The Corporation shall not have members 
as defined in the California Nonprofit Public Benefit Corporation Law 
("CNPBCL"), notwithstanding the use of the term "Member" in these 
bylaws, in a selection plan adopted by Board resolution, or in any 
other action of the Board. Instead, the Corporation shall allow 
individuals (described in these bylaws as "Members") to participate 
in the activities of the Corporation as described in this Article II 
and in a selection plan adopted by Board resolution, and only to the 
extent set forth in this Article II and in a selection plan adopted 
by particular router, when that ISP needs to move up to something like 
defining an end-to-end service for a particular customer, there is a 
big void. Providing such solutions are challenges that happen both 
within and between Board resolution."
 
Optical BGP Proposed as Means of Wide Area Interconnection of 
Bandwidth-Rich Edges Without Burdening Largest Backbones With 
Additional Traffic Created by Gigabit Ethernet and Dark Fiber Driven 
Local Bandwidth Explosion	 		pp. 22-24

"OBGP is a proposed extension to BGP for the manipulation of optical  
cross connects to permit them to be automatically setup and 
configured as BGP speaking devices to support multiple direct optical 
lightpaths between  many different autonomous domains. OBGP may also 
allow customers at the edge to control a subset of lightpaths within 
another network's wavelength cloud so that they can manage their own 
light path routing within that cloud."  . .  .  . [We suggest 
treating] 'each optical cross connect as an independent virtual BGP 
router with only one input port and one output port.  A virtual BGP 
router can then be set up for each optical cross connect and separate 
BGP sessions initiated with its peers."  .   .  .  .  "The physical 
characteristics of a lightpath give it an intrinsic capability of 
being a "poor man's" logical switched path with a predefined Quality 
of Service. " .  .  .  .  "The exchange of lightpaths may also allow 
for a simpler mechanism to allow for settlement in peering and 
transit between ISPs."  .  .  .   . "In future there may even be 
wavelength commodity markets where ISPs can trade wavelengths and 
adjacencies on the open market."

-- 
****************************************************************
The COOK Report on Internet      Index to 8 years of the COOK  Report
431 Greenway Ave, Ewing, NJ 08618 USA   at http://cookreport.com
(609) 882-2572 (phone & fax)            Have you done your part to keep
cook@cookreport.com                  the Internet free from ICANN's control?
Replace your machine's DNS numbers from http://dnsroot.org/ today
****************************************************************



From owner-ietf-outbound  Thu Jul 20 18:11:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA03144
	for ietf-outbound.10@ietf.org; Thu, 20 Jul 2000 18:10:03 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00061
	for <ietf@ietf.org>; Thu, 20 Jul 2000 18:03:02 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id PAA21312;
	Thu, 20 Jul 2000 15:01:34 -0700 (PDT)
Date: Thu, 20 Jul 2000 15:01:34 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200007202201.PAA21312@shell5.ba.best.com>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Mime-Version: 1.0
X-Loop: ietf@ietf.org

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

> the reason I say that your statement is content-free is that it offers
> no specific criticism of IETF that can be used in a constructive fashion.

With respect to this particular thread, the only criticism I'd make is
I don't see how the draft in question will alter the business practices of
AOL or any other large Internet access provider that does not provide
full Internet service.  I think the draft is useful for protocol
developers who may require interoperability across NAT boundaries, and
network managers who may need to explain why certain architectures may
cause certain protocols to break.  Beyond that, I don't see that it will
cause any significant change in the business practices of companies who
have decided (for whatever reasons) that it is not necessary to give any
(or all) of their customers full Internet service.

The IETF might perhaps take an advocacy position for traditional Internet
service.  An RFC on the order of "Full Internet Access is Good" might
sway a few people who are unaware of the wealth of services a full
provider offers.  On the other hand, a provider that actually offers
such services is much more likely (imho) to have success among a
potential customer base for them, and arguably has more resources to do so.
By this I mean the money for a PR campaign, advertising, etc.

> I find that the work of IETF varies in quality - much of it is quite
> good, some of it mediocre, a small fraction is highly dubious.
> Most IETF WGs I've worked with do not operate with an attitude like
> "people will have to do what we say", but rather "how do we solve
> this problem".  Most of them seem to understand that they have not
> only to solve the problem, but also to make the solution technically
> sound, attractive to those who would use it, and easy to deploy.

OK, in this case, what is the problem that needs to be solved, from the
standpoint of AOL?  Their customers, for the most part, are either unaware
that there is a problem, or the problem does not currently affect them.  If
enough of their customers feel it is a problem, no doubt AOL will change
their business practices (because if they fail to do so they will lose
business to access providers who will solve their problems).

So, what is the problem we are trying to solve here, and is the IETF the
organization that can provide the most effective solution?

--gregbo



From owner-ietf-outbound  Thu Jul 20 20:31:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA02304
	for ietf-outbound.10@ietf.org; Thu, 20 Jul 2000 20:30:02 -0400 (EDT)
Received: from mail.nbn.net (root@nbn.net [207.51.86.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29883
	for <ietf@ietf.org>; Thu, 20 Jul 2000 20:24:06 -0400 (EDT)
Received: from server-1 (dial5-33.nbn.net [208.139.67.219])
	by mail.nbn.net (8.9.3/8.9.3) with SMTP id UAA29246
	for <ietf@ietf.org>; Thu, 20 Jul 2000 20:23:57 -0400
Message-ID: <39779B5D.B6D@nbn.net>
Date: Thu, 20 Jul 2000 20:37:49 -0400
From: Betsy Brennan <bbrennan@nbn.net>
Reply-To: bbrennan@nbn.net
X-Mailer: Mozilla 3.04 (Win95; U)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 100th Issue of The COOK Report on Internet  (September 2000)
References: <p0432042db59d18413a99@[192.168.0.1]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> Gordon Cook wrote:

Just wondering - does anyone know why this was sent to us?
BLB



From owner-ietf-outbound  Thu Jul 20 22:01:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA05022
	for ietf-outbound.10@ietf.org; Thu, 20 Jul 2000 22:00:02 -0400 (EDT)
Received: from pita.cisco.com (pita.cisco.com [171.71.68.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20629
	for <ietf@ietf.org>; Thu, 20 Jul 2000 21:25:08 -0400 (EDT)
Received: from cowboy-mr.cisco.com (michaelr@dhcp-o-38-248.cisco.com [171.71.38.248])
	by pita.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id SAA28398;
	Thu, 20 Jul 2000 18:24:33 -0700 (PDT)
Received: (from michaelr@localhost)
	by cowboy-mr.cisco.com (8.9.3/8.9.0) id SAA00376;
	Thu, 20 Jul 2000 18:23:22 -0700 (PDT)
From: "Michael Reilly <Michael Reilly" <michaelr@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14711.42506.525883.616317@cowboy-mr.cisco.com>
Date: Thu, 20 Jul 2000 18:23:22 -0700 (PDT)
To: bbrennan@nbn.net
Cc: ietf@ietf.org
Subject: Re: 100th Issue of The COOK Report on Internet  (September 2000)
In-Reply-To: Betsy Brennan's message of 20 July 2000 20:37:49 -0400
References: <p0432042db59d18413a99@[192.168.0.1]>
	<39779B5D.B6D@nbn.net>
X-Mailer: VM 6.75 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>>Just wondering - does anyone know why this was sent to us?
>>BLB

SPAM



From owner-ietf-outbound  Fri Jul 21 09:31:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA12124
	for ietf-outbound.10@ietf.org; Fri, 21 Jul 2000 09:30:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11823
	for <ietf@ietf.org>; Fri, 21 Jul 2000 09:24:37 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@localhost [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta4/8.11.0.Beta4) with ESMTP id e6LDOaY30862;
	Fri, 21 Jul 2000 09:24:36 -0400
Message-Id: <200007211324.e6LDOaY30862@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4+dev
To: "Michael Reilly <Michael Reilly" <michaelr@cisco.com>
Cc: ietf@ietf.org
Subject: Re: 100th Issue of The COOK Report on Internet (September 2000) 
In-Reply-To: Your message of "Thu, 20 Jul 2000 18:23:22 PDT."
             <14711.42506.525883.616317@cowboy-mr.cisco.com> 
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: <p0432042db59d18413a99@[192.168.0.1]> <39779B5D.B6D@nbn.net>
            <14711.42506.525883.616317@cowboy-mr.cisco.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_778317306P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 21 Jul 2000 09:24:35 -0400
X-Loop: ietf@ietf.org

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

On Thu, 20 Jul 2000 18:23:22 PDT, "Michael Reilly <Michael Reilly" said:
> >>Just wondering - does anyone know why this was sent to us?
> >>BLB
> 
> SPAM

Umm.. to be correct, the proper term is probably "spewage".   True SPAM
is either the brand name for an alledgedly-edible canned meat product, or
mail sent with little or no regard for whether the recipient is interested.

For all of Gordon's faults, I think he was convinced that the IETF membership
was at least tangentially interested.. 4 news items, one each on network
management tools, network infrastructure, ICANN, and BGP.  Last I heard,
the IETF was at least slightly concerned with what ICANN was doing, although
the NANOG people are probably more interested in the Cogent Comm and BGP
articles.

Certainly more on topic than advertisement for HP printer supplies, anyhow ;)

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOXhPE3At5Vm009ewEQIedQCdHuj1Vc6NANSJ7qizWICafJVnRJ4AoK9m
tpMq+9Q7EWXkaSlDgsmvcff3
=taty
-----END PGP SIGNATURE-----

--==_Exmh_778317306P--



From owner-ietf-outbound  Fri Jul 21 10:01:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA13847
	for ietf-outbound.10@ietf.org; Fri, 21 Jul 2000 10:00:02 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13168
	for <ietf@ietf.org>; Fri, 21 Jul 2000 09:46:52 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id JAA01082
	for <ietf@ietf.org>; Fri, 21 Jul 2000 09:46:52 -0400
Sender: francis@localhost.localdomain
Message-ID: <3978544B.68F4A192@ecal.com>
Date: Fri, 21 Jul 2000 09:46:51 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <200007202201.PAA21312@shell5.ba.best.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Greg Skinner wrote:

> The IETF might perhaps take an advocacy position for traditional Internet
> service.  An RFC on the order of "Full Internet Access is Good" might
> sway a few people who are unaware of the wealth of services a full
> provider offers.  On the other hand, a provider that actually offers
> such services is much more likely (imho) to have success among a
> potential customer base for them, and arguably has more resources to do so.
> By this I mean the money for a PR campaign, advertising, etc.

On the other other hand, such a PR campaign might be able to gain some weight
by quoting the RFC.

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |All I ask is a chance to prove that money can't|
|francis@ecal.com|make me happy.                                 |
\================================================================/





From owner-ietf-outbound  Fri Jul 21 15:41:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA17869
	for ietf-outbound.10@ietf.org; Fri, 21 Jul 2000 15:40:05 -0400 (EDT)
Received: from alijku04.edvz.uni-linz.ac.at (alijku04.edvz.uni-linz.ac.at [140.78.182.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09728
	for <ietf@ietf.org>; Fri, 21 Jul 2000 15:30:44 -0400 (EDT)
Received: from Michael (z2225-034-098.Raab-Heim.Uni-Linz.AC.AT [193.171.34.98])
	by alijku04.edvz.uni-linz.ac.at (8.8.8/8.8.8) with SMTP id VAA72298
	for <ietf@ietf.org>; Fri, 21 Jul 2000 21:30:23 +0200
Message-Id: <3.0.32.20000721213058.009d3530@mikasa.tk.uni-linz.ac.at>
X-Sender: michael@mikasa.tk.uni-linz.ac.at
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Fri, 21 Jul 2000 21:30:58 +0200
To: ietf@ietf.org
From: Michael Welzl <michael@tk.uni-linz.ac.at>
Subject: Warriors of the net
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Hi all,

I just saw this today ... for those of you who don't know it yet, it truly
is a must-see.

Note that this is NOT spam! It's something funny - and so cool that you
IETF people just need to see it. I just watched it three times in a row   :)
Besides being funny, it's a great way to teach your kids how the 'net
works, too.

http://www.warriorsofthe.net/

Also note that I'm by now means involved with this project (wish I was  :) ),
I'm just impressed by it.

Cheers,
Michael Welzl



From owner-ietf-outbound  Fri Jul 21 16:51:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA22861
	for ietf-outbound.10@ietf.org; Fri, 21 Jul 2000 16:50:04 -0400 (EDT)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22571
	for <ietf@ietf.org>; Fri, 21 Jul 2000 16:49:28 -0400 (EDT)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id PAA28054;
	Fri, 21 Jul 2000 15:49:26 -0500 (CDT)
Message-Id: <200007212049.PAA28054@gungnir.fnal.gov>
To: Michael Welzl <michael@tk.uni-linz.ac.at>
Cc: ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: Warriors of the net 
In-reply-to: Your message of Fri, 21 Jul 2000 21:30:58 +0200.
             <3.0.32.20000721213058.009d3530@mikasa.tk.uni-linz.ac.at> 
Date: Fri, 21 Jul 2000 15:49:26 -0500
Sender: crawdad@gungnir.fnal.gov
X-Loop: ietf@ietf.org

> Note that this is NOT spam! It's something funny - and so cool that you
> IETF people just need to see it. I just watched it three times in a row   :)
> Besides being funny, it's a great way to teach your kids how the 'net
> works, too.
> 
> http://www.warriorsofthe.net/

It's full of mistakes.



From owner-ietf-outbound  Sun Jul 23 11:17:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA19718
	for ietf-outbound.10@ietf.org; Sun, 23 Jul 2000 11:10:02 -0400 (EDT)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17694
	for <ietf@ietf.org>; Sun, 23 Jul 2000 11:00:51 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id IAA26722;
	Sun, 23 Jul 2000 08:00:39 -0700 (PDT)
Date: Sun, 23 Jul 2000 08:00:39 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200007231500.IAA26722@shell9.ba.best.com>
To: l.wood@eim.surrey.ac.uk
Subject: RE: HTML forms 
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

>> Anyone know whether Opera has microphone upload yet?
> 
> More to the point, does anyone care?

Well, sure, Opera probably cares whether they have a feature that 
Tim Berners-Lee claims is an integral part of the HTML standard, 
but hasn't yet been implemented by any of their competitors:

  http://www.bovik.org/devup/tbl-devup.txt

Over 150 people have told me, using a web-based endorsement form, 
that they want the elegant symmetry that general device input and 
upload would provide.  Traditionally, helper applications for 
browsers have handled output presentation.  The same facilities can
be used for input from any number of sources and uploaded using 
standard form submission.  This will enable interoperability that 
closed cartels can not, with much greater customer approval.

Anyone whose life would be enriched by ease in implementing and 
performing media upload, be it audio, video, images, text editor 
files, or even raw serial input should care, even if they do not at 
present.  One of the strongest supporters is a Professor of 
Linguistics at the U.S. Military Academy at West Point, who probably 
means a lot of potential sales, given the number of cadets that he 
is responsible for teaching spoken languages to.

Those who wish to register their support are encouraged to vote:

  http://bugzilla.mozilla.org/showvotes.cgi?voteon=46135

on this Mozilla feature request:

  http://bugzilla.mozilla.org/show_bug.cgi?id=46135

Cheers,
James



From owner-ietf-outbound  Mon Jul 24 10:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08527
	for ietf-outbound.10@ietf.org; Mon, 24 Jul 2000 10:40:01 -0400 (EDT)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07739;
	Mon, 24 Jul 2000 10:35:02 -0400 (EDT)
Received: from cisco.com (toronto-isdn-109.cisco.com [171.70.77.109]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with ESMTP id HAA06363; Mon, 24 Jul 2000 07:34:31 -0700 (PDT)
Message-ID: <397C5418.D136B8B5@cisco.com>
Date: Mon, 24 Jul 2000 10:35:04 -0400
From: Albert Herrera <albherre@cisco.com>
Organization: Cisco Systems, Inc.
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-announce-request@ietf.org
CC: ietf@ietf.org, "ptrings@cisco.com" <ptrings@external.cisco.com>
Subject: Agenda for IPoPTR BOF
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Attached is the description and agenda for the IPoPTR BOF
at the 48th IETF. We encourage all those interested to attend.

Thanks,
Albert

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

IP over Packet Transport Rings BOF  (IPoPTR)

Chair(s):

Albert Herrera albherre@cisco.com
Raj Sharma raj@luminousnetworks.com

Internet Area Director(s):

Thomas Narten narten@raleigh.ibm.com
Erik Nordmark Erik.Nordmark@eng.sun.com

General Discussion:ptrings@cisco.com
To Subscribe: send an email to
ptrings-request@cisco.com with 'subscribe ptrings' in the
body and subject of the message.

Other Related documents/sites:

I-D: http://search.ietf.org/internet-drafts/draft-tsiang-srp-02.txt
IEEE RPRSG site: http://www.ieee802.org/rprsg

Description:

The purpose of this BoF is to discuss the proposed Charter
for the IPoPTR WG. The WGs focus will be to standardize
specifications that will allow upper layer (IP) awareness within
Packet Transport Rings for tighter routing and forwarding
control as well as more efficient interworking of other features.

Proposed work includes interactions between the rings
and L3 routing protocols:

- IGP awareness of adjacent upstream and downstream neighbors
- Enable faster L3 convergence when nodes drops out
  or are  removed from the ring
- Enhancements to IGP metric and cost features
- Determine appropriate flooding mechanisms
- Extensions to enable ring-aware MPLS-TE
- MIB definitions

Time/Location: August 4, 2000 09:00-11:30

Pittsburgh Agenda:

Agenda Bashing (5 min.)
Scope and Objectives (10 min.)
Packet Transport Rings Concepts and Requirements (40 min.)
Status of IEEE related activities (30 min.)
Proposed Charter (10 min.)
Charter Bashing (20 min.)
WG Status (10 min.)

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





From owner-ietf-outbound  Mon Jul 24 11:20:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA20468
	for ietf-outbound.10@ietf.org; Mon, 24 Jul 2000 11:20:02 -0400 (EDT)
Received: from uforce.com (gatekeeper.uforce.com [216.208.234.226])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17666
	for <ietf@ietf.org>; Mon, 24 Jul 2000 11:11:28 -0400 (EDT)
Received: from uforce.com (wm1.uforce.internal [192.168.1.31])
	by uforce.com (8.9.3/8.9.3) with ESMTP id LAA06394
	for <ietf@ietf.org>; Mon, 24 Jul 2000 11:10:48 -0400
Message-ID: <397C5C82.80885C03@uforce.com>
Date: Mon, 24 Jul 2000 11:10:58 -0400
From: Andre-John Mas <ajmas@uforce.com>
Organization: UForce Inc.
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Domain name organization recommendation
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

 I was wondering if anybody has written a documentation that examines
 the usability of national domain names and provides advice on what 
 approaches are actually useable. For example, I recently had a
discussion
 with some people on the .us domain on how unusable it is due to the
length
 of the domain names - myco.mytown.mystate.us. How about having .com.us,
 .edu.us, and accepting that anything without a country extension is
should
 now be reserved for international use, contrary to what the original
RFC
 said on the use of the .com, .edu, .gov domain names.

 Andre



From owner-ietf-outbound  Mon Jul 24 11:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA00776
	for ietf-outbound.10@ietf.org; Mon, 24 Jul 2000 11:50:04 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29482
	for <ietf@ietf.org>; Mon, 24 Jul 2000 11:44:43 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200007241542.AAA12619@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id AAA12619; Tue, 25 Jul 2000 00:42:30 +0900
Subject: Re: Domain name organization recommendation
In-Reply-To: <397C5C82.80885C03@uforce.com> from Andre-John Mas at "Jul 24, 2000
 11:10:58 am"
To: Andre-John Mas <ajmas@uforce.com>
Date: Tue, 25 Jul 2000 00:42:30 +0859 ()
CC: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Andre;

>  I was wondering if anybody has written a documentation that examines
>  the usability of national domain names and provides advice on what 
>  approaches are actually useable.

It highly depends on locale that generic document is harmful.

> For example, I recently had a
> discussion
>  with some people on the .us domain on how unusable it is due to the
> length
>  of the domain names - myco.mytown.mystate.us. How about having .com.us,

Try to use <zip-code>.us.

>  .edu.us, and accepting that anything without a country extension is
> should
>  now be reserved for international use, contrary to what the original
> RFC
>  said on the use of the .com, .edu, .gov domain names.

Huh?

.com etc. have been international, from the beginning.

Who, do you think, can say a US or JP corporate which want to
attract customers worldwide is NOT international?

If you think domain names under TLDs scarese, you should better try
to charge annurally $15000 for domain names directly under TLDs and
for ones indirectly under ccTLDs $15.

							Masataka Ohta



From owner-ietf-outbound  Mon Jul 24 12:00:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA03725
	for ietf-outbound.10@ietf.org; Mon, 24 Jul 2000 12:00:03 -0400 (EDT)
Received: from ztxmail04.ztx.compaq.com (ztxmail04.ztx.compaq.com [161.114.1.208])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01802
	for <ietf@ietf.org>; Mon, 24 Jul 2000 11:54:43 -0400 (EDT)
Received: by ztxmail04.ztx.compaq.com (Postfix, from userid 12345)
	id 7784352E; Mon, 24 Jul 2000 10:54:10 -0500 (CDT)
Received: from excreo-gh01.reo.dec.com (excreo-gh01.reo.cpqcorp.net [16.41.128.40])
	by ztxmail04.ztx.compaq.com (Postfix) with ESMTP
	id DA45F7D1; Mon, 24 Jul 2000 10:54:09 -0500 (CDT)
Received: by excreo-gh01.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <N64NNQJY>; Mon, 24 Jul 2000 16:54:08 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9D65@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'Andre-John Mas'" <ajmas@uforce.com>, ietf@ietf.org
Subject: RE: Domain name organization recommendation
Date: Mon, 24 Jul 2000 16:54:06 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Hi there
	Its already set up link that, Not that I can ever recall seeing a
.us. The example that you have used myco.mytown.mystate.us. is a trick on.
It is in reality www.mystate.us the rest are virtual Server adress's (Sub
domains)

But yes from what I have seen the US tend to use .COM as default.

Jon


-----Original Message-----
From: Andre-John Mas [mailto:ajmas@uforce.com]
Sent: Monday, July 24, 2000 4:11 PM
To: ietf@ietf.org
Subject: Domain name organization recommendation


Hi,

 I was wondering if anybody has written a documentation that examines
 the usability of national domain names and provides advice on what 
 approaches are actually useable. For example, I recently had a
discussion
 with some people on the .us domain on how unusable it is due to the
length
 of the domain names - myco.mytown.mystate.us. How about having .com.us,
 .edu.us, and accepting that anything without a country extension is
should
 now be reserved for international use, contrary to what the original
RFC
 said on the use of the .com, .edu, .gov domain names.

 Andre



From owner-ietf-outbound  Mon Jul 24 12:10:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA07082
	for ietf-outbound.10@ietf.org; Mon, 24 Jul 2000 12:10:02 -0400 (EDT)
Received: from uforce.com (gatekeeper.uforce.com [216.208.234.226])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02809
	for <ietf@ietf.org>; Mon, 24 Jul 2000 11:57:19 -0400 (EDT)
Received: from uforce.com (wm1.uforce.internal [192.168.1.31])
	by uforce.com (8.9.3/8.9.3) with ESMTP id LAA06673;
	Mon, 24 Jul 2000 11:56:17 -0400
Message-ID: <397C673E.6ECCE2C9@uforce.com>
Date: Mon, 24 Jul 2000 11:56:46 -0400
From: Andre-John Mas <ajmas@uforce.com>
Organization: UForce Inc.
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>, ietf@ietf.org
Subject: Re: Domain name organization recommendation
References: <200007241542.AAA12619@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Masataka Ohta wrote:
> 
> Andre;
> 
> >  I was wondering if anybody has written a documentation that examines
> >  the usability of national domain names and provides advice on what
> >  approaches are actually useable.
> 
> It highly depends on locale that generic document is harmful.
> 
> > For example, I recently had a
> > discussion
> >  with some people on the .us domain on how unusable it is due to the
> > length
> >  of the domain names - myco.mytown.mystate.us. How about having .com.us,
> 
> Try to use <zip-code>.us.
> 
> >  .edu.us, and accepting that anything without a country extension is
> > should
> >  now be reserved for international use, contrary to what the original
> > RFC
> >  said on the use of the .com, .edu, .gov domain names.
> 
> Huh?
> 
> .com etc. have been international, from the beginning.

If you read the following RFC: http://www.isi.edu/in-notes/rfc1591.txt
you will
see there are limitations to which the USA has privilege. Has this
document
been revised?

Andre



From owner-ietf-outbound  Mon Jul 24 12:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA13490
	for ietf-outbound.10@ietf.org; Mon, 24 Jul 2000 12:30:03 -0400 (EDT)
Received: from orchard.arlington.ma.us (orchard.hamachi.org [4.255.0.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11650
	for <ietf@ietf.org>; Mon, 24 Jul 2000 12:24:25 -0400 (EDT)
Received: by orchard.arlington.ma.us (Postfix, from userid 587)
	id 6AF682A22; Mon, 24 Jul 2000 12:24:24 -0400 (EDT)
Received: from orchard.arlington.ma.us (localhost [127.0.0.1])
	by orchard.arlington.ma.us (Postfix) with ESMTP
	id 52DD21F98; Mon, 24 Jul 2000 12:24:24 -0400 (EDT)
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
Cc: "'Andre-John Mas'" <ajmas@uforce.com>, ietf@ietf.org
Subject: Re: Domain name organization recommendation 
In-Reply-To: Message from "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com> 
   of "Mon, 24 Jul 2000 16:54:06 BST." <71C4C55F198BD211B24F0000F842F15807ED9D65@reoexc6.reo.cpqcorp.net> 
Reply-To: sommerfeld@orchard.arlington.ma.us
Date: Mon, 24 Jul 2000 12:24:19 -0400
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
Message-Id: <20000724162424.6AF682A22@orchard.arlington.ma.us>
X-Loop: ietf@ietf.org

> 	Its already set up link that, Not that I can ever recall seeing a
> .us. 

you have now.

					- Bill



From owner-ietf-outbound  Mon Jul 24 13:00:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA23720
	for ietf-outbound.10@ietf.org; Mon, 24 Jul 2000 13:00:02 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23507
	for <ietf@ietf.org>; Mon, 24 Jul 2000 12:59:11 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id NAA13325
	for <ietf@ietf.org>; Mon, 24 Jul 2000 13:00:08 -0400
Sender: francis@localhost.localdomain
Message-ID: <397C7618.6C70244@ecal.com>
Date: Mon, 24 Jul 2000 13:00:08 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Domain name organization recommendation
References: <71C4C55F198BD211B24F0000F842F15807ED9D65@reoexc6.reo.cpqcorp.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

"Parkinson, Jonathan" wrote:

>         Its already set up link that, Not that I can ever recall seeing a
> .us. The example that you have used myco.mytown.mystate.us. is a trick on.
> It is in reality www.mystate.us the rest are virtual Server adress's (Sub
> domains)

What are you trying to say here? All domains except "." are subdomains.

--
/===============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own. |
|Chief Scientist |==============================================|
|eCal Corp.      |"If it failed then, there's no reason to think|
|francis@ecal.com|we can't make it fail now." -- Colin Benson   |
\===============================================================/





From owner-ietf-outbound  Mon Jul 24 13:20:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA29731
	for ietf-outbound.10@ietf.org; Mon, 24 Jul 2000 13:20:03 -0400 (EDT)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24996
	for <ietf@ietf.org>; Mon, 24 Jul 2000 13:04:03 -0400 (EDT)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id MAA13160;
	Mon, 24 Jul 2000 12:03:35 -0500 (CDT)
Message-Id: <200007241703.MAA13160@gungnir.fnal.gov>
To: sommerfeld@orchard.arlington.ma.us
Cc: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>,
        "'Andre-John Mas'" <ajmas@uforce.com>, ietf@ietf.org
From: "Matt Crawford" <matt+ietf1@severian.chi.il.us>
Subject: Re: Domain name organization recommendation 
In-reply-to: Your message of Mon, 24 Jul 2000 12:24:19 EDT.
             <20000724162424.6AF682A22@orchard.arlington.ma.us> 
Date: Mon, 24 Jul 2000 12:03:34 -0500
Sender: crawdad@gungnir.fnal.gov
X-Loop: ietf@ietf.org

> > Its already set up link that, Not that I can ever recall seeing a .us. 
> 
> you have now.
> 					- Bill

And what was that nonsense they were spewing about www.state.us?

And if .us is "unusable", how did it get to be the third most common
country-code domain, with all those three-letter TLDs competing with
it?  Hm?

Case (and plaintiffs) dismissed.

			matt@severian.batavia.il.us



From owner-ietf-outbound  Mon Jul 24 14:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA26316
	for ietf-outbound.10@ietf.org; Mon, 24 Jul 2000 14:50:02 -0400 (EDT)
Received: from A4.JCK.COM (ns.jck.com [209.187.148.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15808
	for <ietf@ietf.org>; Mon, 24 Jul 2000 14:14:16 -0400 (EDT)
Received: from P2 ("port 1707"@[209.187.148.217])
 by a4.jck.com (PMDF V6.0-23 #40360) with ESMTP id <0FY700L0NS20Z1@a4.jck.com>
 for ietf@ietf.org; Mon, 24 Jul 2000 14:15:36 -0400 (EDT)
Date: Mon, 24 Jul 2000 14:14:13 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: Domain name organization recommendation
In-reply-to: <397C673E.6ECCE2C9@uforce.com>
To: Andre-John Mas <ajmas@uforce.com>
Cc: ietf@ietf.org
Message-id: <2375379196.964448053@P2>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.0 (Win32)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

--On Monday, 24 July, 2000 11:56 -0400 Andre-John Mas
<ajmas@uforce.com> wrote:

> If you read the following RFC:
> http://www.isi.edu/in-notes/rfc1591.txt you will
> see there are limitations to which the USA has privilege. Has
> this document
> been revised?

No, although ICANN has been working on sections of it.  See
their web site (http://www.icann.org/) for more information on
this and other DNS policy and administrative issues (in which
the IETF is _not_, as an organization, involved).   

Incidentally, the relevant defining (policy) document for the US
domain is RFC 1480.  More information can be obtained at
http://www.nic.us/, which also contains current-practice updates
to RFC 1480.  

The various domain surveys routinely show the US domain as among
the largest half-dozen country code domains --I think recently
about third-- and it tends to run a much closer ratio of
registered names to actual, distinct, hosts than those domains
which have become overwhelmed registrations of many product or
company names which point to a much smaller number of web
servers).

That information is obviously at some variance with the amount
of misinformation posted on this subject to the IETF list in the
last 24 hours.

But, more generally:

* If someone has issues or suggestions about general
domainnaming policy, take them to ICANN.   They are not
engineering issues, and the IETF isn't involved.

* If someone has issues with how the US Domain is managed,
administered, or delegated internally, I'd recommend discussing
them with the US Domain Administrator, after reviewing the
material on the web page cited above.   Again, the IETF isn't
involved and this mailing list isn't an especially useful
discussion forum.

     john



From owner-ietf-outbound  Mon Jul 24 17:00:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA05122
	for ietf-outbound.10@ietf.org; Mon, 24 Jul 2000 17:00:03 -0400 (EDT)
Received: from stewart.chicago.il.us (3ff83343.dsl.flashcom.net [63.248.51.67])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04562
	for <ietf@ietf.org>; Mon, 24 Jul 2000 16:57:55 -0400 (EDT)
Received: from stewart.chicago.il.us (IDENT:randall@stewart.chicago.il.us [10.1.1.1])
	by stewart.chicago.il.us (8.9.3/8.8.7) with ESMTP id PAA06837;
	Mon, 24 Jul 2000 15:44:11 -0500
Sender: randall@STEWART.CHICAGO.IL.US
Message-ID: <397CAA9B.A57B7F02@stewart.chicago.il.us>
Date: Mon, 24 Jul 2000 15:44:11 -0500
From: "Randall R. Stewart" <randall@STEWART.CHICAGO.IL.US>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: sommerfeld@orchard.arlington.ma.us
CC: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>,
        "'Andre-John Mas'" <ajmas@uforce.com>, ietf@ietf.org
Subject: Re: Domain name organization recommendation
References: <20000724162424.6AF682A22@orchard.arlington.ma.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Bill Sommerfeld wrote:
> 
> >       Its already set up link that, Not that I can ever recall seeing a
> > .us.
> 
> you have now.
> 
>                                         - Bill
And of course you can see one over
here as well :-)

Also 

www.stewart.chicago.il.us

and coming soon..

www.sctp.chicago.il.us

R
-- 
Randall R. Stewart
randall@stewart.chicago.il.us



From owner-ietf-outbound  Tue Jul 25 11:30:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA27527
	for ietf-outbound.10@ietf.org; Tue, 25 Jul 2000 11:30:02 -0400 (EDT)
Received: from popcorn.cisco.com (popcorn.cisco.com [171.69.18.32])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27212
	for <ietf@ietf.org>; Tue, 25 Jul 2000 11:29:10 -0400 (EDT)
Received: from [10.19.130.188] (deering-dsl3.cisco.com [10.19.130.188])
	by popcorn.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.8.8) with ESMTP id IAA05865
	for <ietf@ietf.org>; Tue, 25 Jul 2000 08:27:53 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@ups
Message-Id: <v04220801b5a35f94d6c8@[10.19.130.188]>
In-Reply-To: <200007251035.GAA23500@ietf.org>
References: <200007251035.GAA23500@ietf.org>
Date: Tue, 25 Jul 2000 08:30:05 -0700
To: ietf@ietf.org
From: Steve Deering <deering@cisco.com>
Subject: Re: I-D ACTION:draft-dommety-mobileip-anchor-handoff-01.txt
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 6:35 AM -0400 7/25/00, Internet-Drafts@ietf.org wrote:
>    Title        : Local and Indirect Registration for Anchoring Handoffs
>    Author(s)    : G. Dommety, T. Ye
>	
>...This document proposes enchantments to reduce the latencies involved...

Somebody's been reading too much Harry Potter.  Nice thought, though.

Steve



From owner-ietf-outbound  Wed Jul 26 11:20:59 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA27520
	for ietf-outbound.10@ietf.org; Wed, 26 Jul 2000 11:20:02 -0400 (EDT)
Received: from galactica.it (mail1.galactica.it [212.41.208.18] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27413
	for <ietf@ietf.org>; Wed, 26 Jul 2000 11:19:34 -0400 (EDT)
Received: (apparently) from 192.168.1.2 ([213.167.194.228]) by galactica.it  with Microsoft SMTPSVC(5.5.1877.447.44);
	 Wed, 26 Jul 2000 17:19:49 +0200
From: Oliviero Abbigliamento <oliviero@oliviero.it>
To: <ietf@ietf.org>
Subject: Saldi di Oliviero
Message-ID: <052574919151a70MAIL1@galactica.it>
Date: 26 Jul 2000 17:19:50 +0200
X-Loop: ietf@ietf.org


Gentile sig.
Vi informiamo che il 20 di Luglio sono iniziati i Saldi di Oliviero Abigliamento e sul nostro sito abbiamo inserito vari prodotti con prezzi scontati dal 20 al 50%.
Non lasciarti sfuggire le nostre occasioni, 
veniteci a trovare all'indirizzo: http://www.oliviero.it oppure http://www.oliviero.it/shop/saldi.htm (sezione saldi).

Alcune categorie del sito di Oliviero: Abbigliamento, Abiti da sposa, calzature, sport, attrezzature sportive, elettrostimolatori, integratori alimentari, snelling-salute,divise-professionali, tempo libero,  lineamare, camping...

Per informazioni info@oliviero.it
Cordiali saluti

 
P.S. Se in futuro non desidererà più ricevere segnalazioni delle nostre iniziative e promozioni sarà sufficiente inviare una e-mail all'indirizzo
delete@oliviero.it con oggetto CANCELLAMI (solo questa indicazione nell'oggetto, grazie.)



From owner-ietf-outbound  Wed Jul 26 14:52:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA15225
	for ietf-outbound.10@ietf.org; Wed, 26 Jul 2000 14:50:02 -0400 (EDT)
Received: from neodymium.btinternet.com (neodymium.btinternet.com [194.73.73.83])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14853
	for <ietf@ietf.org>; Wed, 26 Jul 2000 14:47:18 -0400 (EDT)
Received: from [62.6.93.50] (helo=salavat)
	by neodymium.btinternet.com with esmtp (Exim 3.03 #83)
	id 13HWD4-0004Xp-00
	for ietf@ietf.org; Wed, 26 Jul 2000 19:47:14 +0100
Message-ID: <005f01bff732$1377b160$325d063e@salavat>
From: "Salavat R. Magazov" <srm4@ukc.ac.uk>
To: "IETF mailing list" <ietf@ietf.org>
Subject: Calls for papers
Date: Wed, 26 Jul 2000 19:48:18 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_005C_01BFF73A.7262BAA0"
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
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_005C_01BFF73A.7262BAA0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Hello

Are there any calls for papers that I missed. I am trying to submit my work
somewhere to see how good it is.

Regards
Salavat

------=_NextPart_000_005C_01BFF73A.7262BAA0
Content-Type: text/x-vcard;
	name="Salavat R. Magazov.vcf"
Content-Disposition: attachment;
	filename="Salavat R. Magazov.vcf"
Content-Transfer-Encoding: 7bit

BEGIN:VCARD
VERSION:2.1
N:Magazov;Salavat;R.;Mr
FN:Salavat R. Magazov
NICKNAME:Sal
ORG:University of Kent at Canterbury
TEL;HOME;VOICE:+44-1227-472835
X-WAB-GENDER:2
BDAY:20000517
EMAIL;PREF;INTERNET:srm4@ukc.ac.uk
EMAIL;INTERNET:salavat@ukonline.co.uk
REV:20000726T184818Z
END:VCARD

------=_NextPart_000_005C_01BFF73A.7262BAA0--



From owner-ietf-outbound  Thu Jul 27 02:00:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA21369
	for ietf-outbound.10@ietf.org; Thu, 27 Jul 2000 02:00:04 -0400 (EDT)
Received: from [10.0.1.27] ([64.44.133.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18490
	for <ietf@ietf.org>; Thu, 27 Jul 2000 01:53:20 -0400 (EDT)
Received: from [10.0.1.27] by [10.0.1.27]
 with ESMTP (Eudora Internet Mail Server 1.3.1); Wed, 26 Jul 2000 22:53:35 -0700
Mime-Version: 1.0
X-Sender: rah@shell3.shore.net
Message-Id: <p04320402b5a57ec8696e@[10.0.1.27]>
Date: Wed, 26 Jul 2000 22:53:21 -0700
To: ietf@ietf.org
From: "R. A. Hettinga" <rah@shipwright.com>
Subject: Kill the RIAA: a protocol
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org


--- begin forwarded text


Date: Thu, 27 Jul 2000 01:30:32 -0400
To: coderpunks@toad.com, cypherpunks@algebra.com, dbs@philodox.com,
        mac-crypto@vmeng.com, cryptography@c2.net
From: Jeff Kandt <jeff@scrollbar.com>
Subject: Kill the RIAA: a protocol
Sender: owner-coderpunks@toad.com

I've downloaded maybe twenty songs with Napster in my life, but the
RIAA has gotten me pretty pissed tonight.

The major labels still haven't figured out a way for me to download
their "product" directly into my music collection.  All of the music
in my 6gb and growing collection (well, all but those 30 I downloaded
with Napster) were ripped from CDs.  These CDs came from somewhere
else in the world on trucks, wrapped in 8" of cardboard and
cellophane.  This is obviously a very expensive model of bit
transmission, which is why the music labels can justify making so
much profit.

Since I discovered MP3s a year or two ago, I've purchased more
plastic slabs of bits than at any other time in my life. Industry
sales numbers and polls confirm that the RIAA is lying when they
claim MP3 is hurting CD sales. I'm buying albums I haven't had since
cassette tape, since vinyl.  Music plays in my house almost
constantly.  It's wonderful, but it's costing me a lot of money.

The music labels are going down and they know it.  They're making a
last grab at milking undeserved money from copyrighted bits because
they know how little time they have left.  They know Napster is only
the beginning.  Gnutella is coming, Freenet is coming, something else
after that.  But the music labels are greedy bastards and their
supply of lawyers is deep.

Well, the internet treats greed like damage and routes around it.

I'd like to pay the musicians for music I download, but I can't.  Of
the 30 songs I downloaded, there are maybe five that I really like
and feel bad about not having paid the musicians for their work and
creativity.  If I could easily send small amounts of tip money to the
musicians I listen to most, to thank them and keep them playing, I
would.  If I'm willing to tip my musicians maybe others are, too.

I don't think most musicians are in it for the money.  But even if
they are, I think they'd make more money under a voluntary payment
system where they didn't have greedy labels taking a huge cut off the
top.

Maybe all we need is a system to make that easy.  Easy for the
consumers so they'll remember to tip, and also easy for the artists
so they don't need to choose which of the (seven?) big labels they're
going to sell out to in order to get their CD in Wall*Mart.  I'd like
to see even the smallest garage bands able to connect with their fans
wherever they are and turn their creativity into a steady stream of
both good will and revenue.

To get the ball rolling, I humbly submit a protocol for a voluntary
payment mechanism.

This protocol encourages free distribution of music (or whatever).
It embeds information about how payments can be negotiated in a
cryptographically secure way, and in a way that attempts to keep the
payment route back to the artist viable even years or decades after
the content was created.

Although the protocol attempts to assure that the embedded payment
information is legitimate, it fails if people strip the payment info
from the files before they distribute them.  This is why I think it's
very important to make payment voluntary so as to remove any
motivation for doing that.

I would appreciate if some folks who know crypto would comment on its
feasibility.  There may already exist such protocols; if so, I would
appreciate references.

Warning: I am not a cryptographer.  There are probably gaping holes.
But like I said, I'm just trying to get the ball rolling.

The protocol description:
http://wmf.editthispage.com/discuss/msgReader$1469

Follow up clarifications and enhancements so far:
http://wmf.editthispage.com/discuss/msgReader$1477
http://wmf.editthispage.com/discuss/msgReader$1491
http://wmf.editthispage.com/discuss/msgReader$1488
http://wmf.editthispage.com/discuss/msgReader$1481
http://wmf.editthispage.com/discuss/msgReader$1473

Thanks in advance.

-Jeff

-- 
--------------------------------------------------------------------------
|Jeff Kandt         |  "When cryptography is outlawed, bayl bhgynjf      |
|jeff@scrollbar.com |   jvyy unir cevinpl!"  -Brad Templeton of ClariNet |
|[PGP Pub key: http://pgp.ai.mit.edu/pks/lookup?op=get&search=0x6CE51904 |
|              or send a message with the subject "send pgp key"]        |
--------------------------------------------------------------------------

--- end forwarded text


-- 
-----------------
R. A. Hettinga <mailto: rah@ibuc.com>
The Internet Bearer Underwriting Corporation <http://www.ibuc.com/>
44 Farquhar Street, Boston, MA 02131 USA
"... however it may deserve respect for its usefulness and antiquity,
[predicting the end of the world] has not been found agreeable to
experience." -- Edward Gibbon, 'Decline and Fall of the Roman Empire'



From owner-ietf-outbound  Thu Jul 27 10:20:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA00838
	for ietf-outbound.10@ietf.org; Thu, 27 Jul 2000 10:20:04 -0400 (EDT)
Received: from varese.appliedtheory.com (IDENT:root@varese.appliedtheory.com [204.168.94.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29653
	for <ietf@ietf.org>; Thu, 27 Jul 2000 10:11:10 -0400 (EDT)
Received: from localhost (alexk@localhost)
	by varese.appliedtheory.com (8.9.3/8.9.3) with ESMTP id JAA14774;
	Thu, 27 Jul 2000 09:22:12 -0400
Date: Thu, 27 Jul 2000 09:22:12 -0400 (EDT)
From: Alex Kamantauskas <alexk@tugger.net>
To: "R. A. Hettinga" <rah@shipwright.com>
cc: ietf@ietf.org
Subject: Re: Kill the RIAA: a protocol
In-Reply-To: <p04320402b5a57ec8696e@[10.0.1.27]>
Message-ID: <Pine.LNX.4.21.0007270920130.14654-100000@varese.appliedtheory.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Wed, 26 Jul 2000, R. A. Hettinga wrote:

> From: Jeff Kandt <jeff@scrollbar.com>
> Subject: Kill the RIAA: a protocol
> 
> I don't think most musicians are in it for the money.  But even if
> they are, I think they'd make more money under a voluntary payment
> system where they didn't have greedy labels taking a huge cut off the
> top.

 The only problem with a voluntary payment system is that under such a
 system, the musician cannot call his A&R guy at 3:30 in the morning
 (while tearing his hotel room apart) and demand another bottle of Chivas
 Regal.

-- 
Alex Kamantauskas
alexk@tugger.net



From owner-ietf-outbound  Thu Jul 27 11:00:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA11603
	for ietf-outbound.10@ietf.org; Thu, 27 Jul 2000 11:00:03 -0400 (EDT)
Received: from uforce.com (gatekeeper.uforce.com [216.208.234.226])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10640
	for <ietf@ietf.org>; Thu, 27 Jul 2000 10:55:40 -0400 (EDT)
Received: from uforce.com (wm1.uforce.internal [192.168.1.31])
	by uforce.com (8.9.3/8.9.3) with ESMTP id KAA23159;
	Thu, 27 Jul 2000 10:52:32 -0400
Message-ID: <39804D05.4899023C@uforce.com>
Date: Thu, 27 Jul 2000 10:53:57 -0400
From: Andre-John Mas <ajmas@uforce.com>
Organization: UForce Inc.
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Alex Kamantauskas <alexk@tugger.net>
CC: "R. A. Hettinga" <rah@SHIPWRIGHT.COM>, ietf@ietf.org
Subject: Re: Kill the RIAA: a protocol
References: <Pine.LNX.4.21.0007270920130.14654-100000@varese.appliedtheory.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Alex Kamantauskas wrote:
> 
> On Wed, 26 Jul 2000, R. A. Hettinga wrote:
> 
> > From: Jeff Kandt <jeff@scrollbar.com>
> > Subject: Kill the RIAA: a protocol
> >
> > I don't think most musicians are in it for the money.  But even if
> > they are, I think they'd make more money under a voluntary payment
> > system where they didn't have greedy labels taking a huge cut off the
> > top.
> 
>  The only problem with a voluntary payment system is that under such a
>  system, the musician cannot call his A&R guy at 3:30 in the morning
>  (while tearing his hotel room apart) and demand another bottle of Chivas
>  Regal.

In other words the only people who really loose out are the hotels ;-)



From owner-ietf-outbound  Thu Jul 27 11:10:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA13278
	for ietf-outbound.10@ietf.org; Thu, 27 Jul 2000 11:10:04 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11246
	for <ietf@ietf.org>; Thu, 27 Jul 2000 10:58:36 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id KAA25991
	for <ietf@ietf.org>; Thu, 27 Jul 2000 10:59:12 -0400
Sender: francis@localhost.localdomain
Message-ID: <39804E40.879D49EE@ecal.com>
Date: Thu, 27 Jul 2000 10:59:12 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Kill the RIAA: a protocol
References: <Pine.LNX.4.21.0007270920130.14654-100000@varese.appliedtheory.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Alex Kamantauskas wrote:

>  The only problem with a voluntary payment system is that under such a
>  system, the musician cannot call his A&R guy at 3:30 in the morning
>  (while tearing his hotel room apart) and demand another bottle of Chivas
>  Regal.

The hotel managers would not consider that a problem.  ;-)

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |We must be devious, cunning, inventive... too|
|francis@ecal.com|bad we're us.                                |
\==============================================================/





From owner-ietf-outbound  Thu Jul 27 23:40:45 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA09499
	for ietf-outbound.10@ietf.org; Thu, 27 Jul 2000 23:40:03 -0400 (EDT)
Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07862
	for <ietf@ietf.org>; Thu, 27 Jul 2000 23:31:58 -0400 (EDT)
Received: from dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155])
	by piglet.dstc.edu.au (8.10.1/8.10.1) with ESMTP id e6S3Vjs16910
	for <ietf@ietf.org>; Fri, 28 Jul 2000 13:31:45 +1000 (EST)
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: ietf@ietf.org
Subject: novel use of URL space
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 28 Jul 2000 13:31:45 +1000
Message-ID: <844.964755105@dstc.edu.au>
From: George Michaelson <ggm@dstc.edu.au>
X-Loop: ietf@ietf.org


I found this via the tasty bits site:

	http://rfc2826.x42.com/ (try for any rfcXXXX)

The idea certainly isn't copyright, and it has a compelling simplicity
which makes me think the IETF could consider adopting it when it
promotes 'canonical' URLs for accessing the standards.

Its probably not such a good idea for the drafts mind you!

comments?

	-George
--
George Michaelson         |  DSTC Pty Ltd
Email: ggm@dstc.edu.au    |  University of Qld 4072
Phone: +61 7 3365 4310    |  Australia
  Fax: +61 7 3365 4311    |  http://www.dstc.edu.au




From owner-ietf-outbound  Fri Jul 28 00:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA13374
	for ietf-outbound.10@ietf.org; Fri, 28 Jul 2000 00:00:05 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13093
	for <ietf@ietf.org>; Thu, 27 Jul 2000 23:58:44 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 13I1Hy-000FLH-00; Thu, 27 Jul 2000 20:58:22 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: George Michaelson <ggm@dstc.edu.au>
Cc: ietf@ietf.org
Subject: Re: novel use of URL space
References: <844.964755105@dstc.edu.au>
Message-Id: <E13I1Hy-000FLH-00@rip.psg.com>
Date: Thu, 27 Jul 2000 20:58:22 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> http://rfc2826.x42.com/ (try for any rfcXXXX)

operationally, useably, ... how is this more useful than putting the rfc
after the slash, e.g.

  http://x42.com/rfc2826

what's it get me, other than less dns hits?

ramdu



From owner-ietf-outbound  Fri Jul 28 00:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA19740
	for ietf-outbound.10@ietf.org; Fri, 28 Jul 2000 00:30:03 -0400 (EDT)
Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17198
	for <ietf@ietf.org>; Fri, 28 Jul 2000 00:18:12 -0400 (EDT)
Received: from dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155])
	by piglet.dstc.edu.au (8.10.1/8.10.1) with ESMTP id e6S4Hus19911;
	Fri, 28 Jul 2000 14:17:56 +1000 (EST)
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: Randy Bush <randy@psg.com>
cc: ietf@ietf.org
Subject: Re: novel use of URL space 
In-Reply-To: Message from Randy Bush <randy@psg.com> 
   of "Thu, 27 Jul 2000 20:58:22 MST." <E13I1Hy-000FLH-00@rip.psg.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 28 Jul 2000 14:17:57 +1000
Message-ID: <1023.964757877@dstc.edu.au>
From: George Michaelson <ggm@dstc.edu.au>
X-Loop: ietf@ietf.org


  > http://rfc2826.x42.com/ (try for any rfcXXXX)
  
  operationally, useably, ... how is this more useful than putting the rfc
  after the slash, e.g.
  
    http://x42.com/rfc2826
  
  what's it get me, other than less dns hits?

you can do a rfc-centric  implementation of further functionality so that
its document/context or document/markup or document/cross-ref.

sure, you can do all that via a cgi, but this way, its document-centric
ie all the sub-features if you do them, hang from the name of the document.

Its not *that* neat an idea, but it had some attraction to me. Actually
the wider idea of embedding information in DNS like that also seems to be
either evil or sweet, depending on how you look at it.
  
costs heaps of overhead for sure!

-george
--
George Michaelson         |  DSTC Pty Ltd
Email: ggm@dstc.edu.au    |  University of Qld 4072
Phone: +61 7 3365 4310    |  Australia
  Fax: +61 7 3365 4311    |  http://www.dstc.edu.au




From owner-ietf-outbound  Fri Jul 28 01:10:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA00107
	for ietf-outbound.10@ietf.org; Fri, 28 Jul 2000 01:10:08 -0400 (EDT)
Received: from ns.nesser.com (host238.2alpha.com [206.129.134.238] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26338;
	Fri, 28 Jul 2000 01:01:43 -0400 (EDT)
Received: from pcpjnesser (host227.2alpha.com [206.129.134.227] (may be forged))
	by ns.nesser.com (8.10.2/8.10.2) with SMTP id e6S4tob00384;
	Thu, 27 Jul 2000 21:55:51 -0700 (PDT)
Reply-To: <phil@nesser.com>
From: "Philip J. Nesser II" <phil@nesser.com>
To: "Iepg@Iepg. Org" <iepg@iepg.org>
Cc: <nanog@nanog.org>, <ietf@ietf.org>, <ietf-announce@ietf.org>
Subject: IEPG Meeting
Date: Thu, 27 Jul 2000 21:56:29 -0700
Message-ID: <FAECIHPANKDMDHLNFMEEEEJPCMAA.phil@nesser.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 IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Greetings,

Sorry to bother all the other lists with IEPG stuff, but the server that
runs the IEPG list has gone down hard and in an effort to get this info out
I am sending to a number of other operations lists.  Feel free to forward
this to other appropriate lists.

The IEPG meeting will be held on Sunday, 30 July from 10:00-17:00 at the
DoubleTree Hotel in the Cambria room located on the second level of the
hotel.

This will occur in conjunction with the IETF meeting starting directly
afterwards in Pittsburgh.

Because of the list problems I have very few agenda items "officially" down
so feel free to show up and we can talk about anything that people want to
discuss.

--->  Phil



From owner-ietf-outbound  Fri Jul 28 02:00:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA29525
	for ietf-outbound.10@ietf.org; Fri, 28 Jul 2000 02:00:05 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25243
	for <ietf@ietf.org>; Fri, 28 Jul 2000 01:51:35 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id BAA03734;
        Fri, 28 Jul 2000 01:51:17 -0400 (EDT)
Message-Id: <200007280551.BAA03734@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Randy Bush <randy@psg.com>
cc: George Michaelson <ggm@dstc.edu.au>, ietf@ietf.org
Subject: Re: novel use of URL space 
In-reply-to: Your message of "Thu, 27 Jul 2000 20:58:22 PDT."
             <E13I1Hy-000FLH-00@rip.psg.com> 
Date: Fri, 28 Jul 2000 01:51:17 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> operationally, useably, ... how is this more useful than putting the rfc
> after the slash, e.g.

you can set up different sets of mirrors for each RFC.
(with different maintainers and/or different TTLs for each set)
you can delegate each RFC to a different DNS zone
(not so useful for RFCs but might be useful for other kinds of documents)

so for instance you can replicate a document to several mirrors
(each represented by an A record) and have the A records for 
that document get updated each time a new replica is created.  
(or each time a replica is destroyed). that way, you have a 
high probability that the mirror server you go to to fetch a
particular document will actually have the document you want.

yes, you can more-or-less do that with HTTP also, using redirects,
but the lookup overhead is higher with HTTP, and DNS has better
support for replication between servers.    so it's probably 
more robust to us DNS

Keith

p.s. otoh, there are subtle differences in the way that relative URLs work 
between the two cases.  if a document is referenced as

http://rfcXXXX.x42.com/ 

then a relative URL of the form "rfcYYYY" presumably won't 
work right (absent the server for XXXX generating a redirect) 

but if you reference it as

http://x42.com/rfcXXXX

then "rfcYYYY" presumably will work if the server mirrors all 
of the RFCs.

so putting the document ID within the DNS name sort of defeats
relative addressing.  whether this is a bug or a feature depends
on your point of view.



From owner-ietf-outbound  Fri Jul 28 10:30:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA00884
	for ietf-outbound.10@ietf.org; Fri, 28 Jul 2000 10:30:03 -0400 (EDT)
Received: from www.counter4all.dk (c1.counter4all.com [195.249.86.201])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28968
	for <ietf@ietf.org>; Fri, 28 Jul 2000 10:21:31 -0400 (EDT)
From: postbox@counter4all.com
Received: from mail pickup service by www.counter4all.dk with Microsoft SMTPSVC;
	 Fri, 28 Jul 2000 16:21:21 +0200
To: <ietf@ietf.org>
Subject: RE: Professional statistics for your homepage
Date: Fri, 28 Jul 2000 16:21:21 +0200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Message-ID: <PLUTODS7hx27kBnccYT00000259@www.counter4all.dk>
X-OriginalArrivalTime: 28 Jul 2000 14:21:21.0140 (UTC) FILETIME=[1A1F2340:01BFF89F]
X-Loop: ietf@ietf.org

Hi ietf@ietf.org

Check http://www.counter4all.com/omcounter.asp



From owner-ietf-outbound  Fri Jul 28 11:00:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA08665
	for ietf-outbound.10@ietf.org; Fri, 28 Jul 2000 11:00:03 -0400 (EDT)
Received: from ngate.noida.hclt.com (IDENT:root@[204.160.254.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06254
	for <ietf@ietf.org>; Fri, 28 Jul 2000 10:50:58 -0400 (EDT)
Received: from titanium.noida.hclt.com (IDENT:root@titanium [204.160.252.2])
	by ngate.noida.hclt.com (8.9.3/8.9.3) with ESMTP id UAA19102
	for <ietf@ietf.org>; Fri, 28 Jul 2000 20:21:39 +0530
Received: from mukta (mukta [204.160.252.39])
	by titanium.noida.hclt.com (8.8.7/8.8.7) with SMTP id UAA17805
	for <ietf@ietf.org>; Fri, 28 Jul 2000 20:21:10 +0530
Message-ID: <00e401bff8a4$2a737d40$27fca0cc@mukta.noida.hclt.com>
From: "Mukta A. Verma" <mukta@noida.hclt.com>
To: <ietf@ietf.org>
Subject: Add to the list
Date: Fri, 28 Jul 2000 20:27:35 +0530
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.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit





From owner-ietf-outbound  Fri Jul 28 12:00:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA27249
	for ietf-outbound.10@ietf.org; Fri, 28 Jul 2000 12:00:02 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26794
	for <ietf@ietf.org>; Fri, 28 Jul 2000 11:58:08 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id LAA02099
	for <ietf@ietf.org>; Fri, 28 Jul 2000 11:59:11 -0400
Sender: francis@localhost.localdomain
Message-ID: <3981ADCE.3279C4F5@ecal.com>
Date: Fri, 28 Jul 2000 11:59:10 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: novel use of URL space
References: <1023.964757877@dstc.edu.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

George Michaelson wrote:

> you can do a rfc-centric  implementation of further functionality so that
> its document/context or document/markup or document/cross-ref.
>
> sure, you can do all that via a cgi, but this way, its document-centric
> ie all the sub-features if you do them, hang from the name of the document.

You can do that with CGI, too.  If you request
http://example.com/foo.cgi/bar/baz, foo.cgi gets run with PATH_INFO set to
"/bar/baz".

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |We must be devious, cunning, inventive... too|
|francis@ecal.com|bad we're us.                                |
\==============================================================/





From owner-ietf-outbound  Fri Jul 28 13:10:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA13000
	for ietf-outbound.10@ietf.org; Fri, 28 Jul 2000 13:10:02 -0400 (EDT)
Received: from ogma.cisco.com (ogma.cisco.com [144.254.74.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10677;
	Fri, 28 Jul 2000 13:00:03 -0400 (EDT)
Received: from nordic.cisco.com (nordic.cisco.com [144.254.116.14])
	by ogma.cisco.com (Postfix) with ESMTP
	id 08F0A189; Fri, 28 Jul 2000 18:59:33 +0200 (MET DST)
Received: from [10.83.97.218] (sj-dial-1-103.cisco.com [171.68.179.104])
	by nordic.cisco.com (8.8.8+Sun/8.8.8) with ESMTP id SAA01481;
	Fri, 28 Jul 2000 18:59:29 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: pfaltstr@nordic.cisco.com
Message-Id: <p04320426b5a767586344@[10.83.97.218]>
Date: Fri, 28 Jul 2000 12:42:49 -0400
To: ietf@ietf.org
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>
Subject: Applications Area Open Meeting
Cc: IESG <iesg@ietf.org>, iab@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

The Applications Area will have an open meeting monday morning (see agenda).

The purpose of this meeting is, like previous years, to both talk 
about common issues, as giving the wg and bof chairs the ability to 
present what the status of their group is.

A draft agenda is as follows:

  1. Ned and Patrik gives a brief introduction
  2. IPR issues
  3. What is a consensus-driven process, and what
     responsibility to wg participants have?
  4. Status of current working groups
     [Each chair, or standin, should prepare one
     sentence to say...you don't have to go to
     the front of the room, use overhead slides etc
     if it is not something specific you want to
     talk about]
  5. Status of BOFs meeting this week
     [See 4 above regarding participation]
  6. Other issues


       Patrik



From owner-ietf-outbound  Fri Jul 28 22:56:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA07100
	for ietf-outbound.10@ietf.org; Fri, 28 Jul 2000 22:56:28 -0400 (EDT)
Received: from web221.mail.yahoo.com (web221.mail.yahoo.com [128.11.68.121])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA04635
	for <IETF@ietf.org>; Fri, 28 Jul 2000 22:43:22 -0400 (EDT)
Message-ID: <20000729024323.7859.rocketmail@web221.mail.yahoo.com>
Received: from [216.185.17.129] by web221.mail.yahoo.com; Fri, 28 Jul 2000 19:43:23 PDT
Date: Fri, 28 Jul 2000 19:43:23 -0700 (PDT)
From: kysi ferul <redwingblakburdz@yahoo.com>
Subject: Re: How many nexuses would it take?
To: nanog@merit.edu
Cc: IETF@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1350490027-964838603=:6227"
X-Loop: ietf@ietf.org

--0-1350490027-964838603=:6227
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

 Very much as with the question;
 "How many were going to St. Ives?"...
I say the sewcret of maximizing the stability of the
Internet would lie in the 're-wiring' of the CONTENT.
This is the FIRST, LAST, and ON-GOING, precondition to
being able to CONVERGE all platforms & applications.
 
   The correct 'ANSWER' was ONE, but the NECESSARY 
MATH gives one the old CALENDRICAL COUNT for
STONEHENGE, which was an event of 2744 Days!   

Note: forwarded message attached.


=====
redwingblakburdz@yahoo.com



__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/
--0-1350490027-964838603=:6227
Content-Type: message/rfc822

X-Apparently-To: redwingblakburdz@yahoo.com via web201.mail.yahoo.com
Received: from web1801.mail.yahoo.com (128.11.23.44)
  by mta125.mail.yahoo.com with SMTP; 28 Jul 2000 10:17:35 -0700 (PDT)
Received: (qmail 16640 invoked by uid 60001); 28 Jul 2000 17:17:03 -0000
Message-ID: <20000728171703.16639.qmail@web1801.mail.yahoo.com>
Received: from [216.185.17.221] by web1801.mail.yahoo.com; Fri, 28 Jul 2000 10:17:03 PDT
Date: Fri, 28 Jul 2000 10:17:03 -0700 (PDT)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: Fwd: Re:DeYoung Museum's Hearst Collection
To: redwingblakburdz@yahoo.com
Cc: norwegianization@yahoo.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1681692777-964804623=:15734"
Content-Length: 9371

--0-1681692777-964804623=:15734
Content-Type: multipart/alternative; boundary="0-1714636915-964804623=:15734"

--0-1714636915-964804623=:15734
Content-Type: text/plain; charset=us-ascii


 

  Note: forwarded message attached. 



Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

This Letter and All Contents Copyright 2000 Casey Farrell
All Rights Reserved

Copyright 2000 Webmaster@oh-yeah.net



---------------------------------
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
--0-1714636915-964804623=:15734
Content-Type: text/html; charset=us-ascii

<P> <BR>
<P>&nbsp; Note: forwarded message attached. </P><BR><BR><P>Casey Farrell; Designer<BR><BR>oh_yeah_dot_net@yahoo.com<BR><BR>This Letter and All Contents Copyright 2000 Casey Farrell<BR>All Rights Reserved</P>
<P>Copyright 2000 <A href="mailto:Webmaster@oh-yeah.net">Webmaster@oh-yeah.net</A></P><p><br><hr size=1><b>Do You Yahoo!?</b><br>
Kick off your party with <a href="http://invites.yahoo.com/">Yahoo! Invites</a>.
--0-1714636915-964804623=:15734--
--0-1681692777-964804623=:15734
Content-Type: message/rfc822

Received: from [216.185.17.215] by web1804.mail.yahoo.com; Thu, 27 Jul 2000 16:04:05 PDT
Date: Thu, 27 Jul 2000 16:04:05 -0700 (PDT)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: Re:DeYoung Museum's Hearst Collection
To: shearst@hearst.com
Cc: twortham@hearst.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-846930886-964739045=:13631"
Content-Length: 7854

--0-846930886-964739045=:13631
Content-Type: text/plain; charset=us-ascii


Casey Farrell, Designer                                                                    July 27, 2000

Attn: Stephen Hearst

           Dear Sir,

      I noticed an electronic glitch or two in my previous letter to you-here is the succinct correct version. My family owned the origianl edifce that is today called the DeYoung Museum, it was created from the "MUSEUM" a building which was the inspiration and template for the CALIFORNIA 

MID WINTER EXPOSITION of 1894.  The building was replete with endowments of all sorts from the "first families of California," from bric-a-brac and knick-knacks to some very fine paintings, one may

be even be that 'Rembrandt' they were trying to find a provanance for? The mainstay of the exhibition was provided by  the Woodward's Gardens collection. After 1894 the DeYoung family expressed a desire to make the Museum all anew-and by the time I was in school, the memorable front section was of course, the Great Gallery which was in the amin all from the Hearst family.

   Now we are in a new century, and as a good many San Franciscans are as forward looking as the

previous generation was in both preserving the beautiful past, and pioneering the exciting future-I wanted to make  sure that you knew that it might be time to find a Julian Morgan or  a Maybeck who can help you create and develop an  ARCHITECTURE which will sustain both the CALIFORNIA  MISSIONS and perhaps help assist you in some directional moves for HEARST PUBLICATIONS ?

   Here are a few of my designs which perhaps can be of some service in the Internet Age-the idea is to create each project as REAL enterprise (NO 'Virtual' ..anything!) with a DOMAIN NAME, ("DOT.COM") and a PRINT INDUSTRY aside, no matter WHAT the MAIN INDUSTRY....

let's say sports? How about http://www.slip.net/~o614275

 this is "dot.commed" as http://www.614275.com

 and then there is always textbooks, http://www.cam.org/home/Wcoprod/mmpro.htm

first page 7th entry "California Star"  ("Digital High Schools" AB64)

howabout CHINESE to ENGLISH and ROMAN to CHARACTERS tutorial for China WEB PORTAL?

http://www.slip.net/~navyblue

and that is to appear at http://www.baozi.org

    I would like very much to consult with you for both Hearst Publications & California Missions,

and at the moment have picture libraries with complimentary art renditions for either Haight Ashbury of the 1890's ot The Haight of 1960's, at my disposal, can at a moment gather some of the best creative writers and historians, and taking all into consideration make at the very least a 'prototype' of what one  might expect to see as a ARCHIVAL work on the INTERNET which is NATURAL and PLEASING! Any and All-the More the Merrier! 

     Please let me know how I may be of service to Hearst Newspapers and Hearst Foundation.

   Thank you,

       Casey Farrell

tel:(415 )664-2489

      This Letter and All Contents Copyright 20000 webmaster@mv3srok4unyrlsh2.com

 

     

 



Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

This Letter and All Contents Copyright 2000 Casey Farrell
All Rights Reserved

Copyright 2000 Webmaster@oh-yeah.net



---------------------------------
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
--0-846930886-964739045=:13631
Content-Type: text/html; charset=us-ascii

<P>Casey Farrell, Designer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; July 27, 2000</P>
<P>Attn: Stephen Hearst</P>
<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dear Sir,</P>
<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I noticed an electronic glitch or two in&nbsp;my previous letter to you-here is the succinct correct version. My family owned the origianl edifce that is today called the DeYoung Museum, it was created from the "MUSEUM" a building which was the inspiration and template for the CALIFORNIA </P>
<P>MID WINTER EXPOSITION of 1894.&nbsp; The building was replete with endowments of all sorts from the "first families of California," from bric-a-brac and knick-knacks to some very fine paintings, one may</P>
<P>be even be that 'Rembrandt' they were trying to find a provanance for? The mainstay of the exhibition was provided by&nbsp; the Woodward's Gardens collection. After 1894 the DeYoung family expressed a desire to make the Museum all anew-and by the time I was in school, the memorable front section was of course, the Great Gallery which was in the amin all from the Hearst family.</P>
<P>&nbsp;&nbsp; Now we are in a new century, and as a good many San Franciscans are as forward looking as the</P>
<P>previous generation was in both preserving the beautiful past, and pioneering the exciting future-I wanted to make&nbsp; sure that you knew that it might be time to find a Julian Morgan or&nbsp; a Maybeck who can&nbsp;help you create and develop an  ARCHITECTURE which will sustain both the CALIFORNIA&nbsp; MISSIONS&nbsp;and&nbsp;perhaps help&nbsp;assist you in some directional moves for&nbsp;HEARST PUBLICATIONS ?</P>
<P>&nbsp;&nbsp; Here are a few of my&nbsp;designs which perhaps can be of some service in the Internet Age-the idea is to create each project as REAL enterprise (NO 'Virtual'&nbsp;..anything!) with a DOMAIN NAME, ("DOT.COM") and a PRINT INDUSTRY aside, no matter WHAT the MAIN INDUSTRY....</P>
<P>let's say sports? How about <A href="http://www.slip.net/~o614275">http://www.slip.net/~o614275</A></P>
<P>&nbsp;this is "dot.commed" as <A href="http://www.614275.com">http://www.614275.com</A></P>
<P>&nbsp;and then there is always textbooks, <A href="http://www.cam.org/home/Wcoprod/mmpro.htm">http://www.cam.org/home/Wcoprod/mmpro.htm</A></P>
<P>first page 7th entry "California Star"&nbsp; ("Digital High Schools" AB64)</P>
<P>howabout CHINESE to ENGLISH and ROMAN to CHARACTERS tutorial for China WEB PORTAL?</P>
<P><A href="http://www.slip.net/~navyblue">http://www.slip.net/~navyblue</A></P>
<P>and that is to appear at <A href="http://www.baozi.org">http://www.baozi.org</A></P>
<P>&nbsp;&nbsp;&nbsp; I would like very much to consult with you for both Hearst Publications &amp; California Missions,</P>
<P>and at the moment have&nbsp;picture libraries with complimentary art renditions for either Haight Ashbury&nbsp;of the 1890's ot The Haight&nbsp;of 1960's,&nbsp;at my disposal,&nbsp;can at a moment gather some of the best creative writers and historians, and&nbsp;taking all into consideration make at the very least a 'prototype' of what&nbsp;one&nbsp; might expect to see as a ARCHIVAL work on the INTERNET which is NATURAL and PLEASING!&nbsp;Any and All-the More the Merrier! </P>
<P>&nbsp;&nbsp;&nbsp;&nbsp; Please let me know how I may be of service to Hearst Newspapers and Hearst Foundation.</P>
<P>&nbsp;&nbsp; Thank you,</P>
<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Casey Farrell</P>
<P>tel:(415 )664-2489</P>
<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This&nbsp;Letter and All Contents Copyright 20000 <A href="mailto:webmaster@mv3srok4unyrlsh2.com">webmaster@mv3srok4unyrlsh2.com</A></P>
<P>&nbsp;</P>
<P>&nbsp;&nbsp;&nbsp;&nbsp; </P>
<P>&nbsp;</P><BR><BR><P>Casey Farrell; Designer<BR><BR>oh_yeah_dot_net@yahoo.com<BR><BR>This Letter and All Contents Copyright 2000 Casey Farrell<BR>All Rights Reserved</P>
<P>Copyright 2000 <A href="mailto:Webmaster@oh-yeah.net">Webmaster@oh-yeah.net</A></P><p><br><hr size=1><b>Do You Yahoo!?</b><br>
Kick off your party with <a href="http://invites.yahoo.com/">Yahoo! Invites</a>.
--0-846930886-964739045=:13631--

--0-1681692777-964804623=:15734--
--0-1350490027-964838603=:6227--



From owner-ietf-outbound  Fri Jul 28 23:00:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA07541
	for ietf-outbound.10@ietf.org; Fri, 28 Jul 2000 23:00:02 -0400 (EDT)
Received: from web209.mail.yahoo.com (web209.mail.yahoo.com [128.11.68.109])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA04810
	for <IETF@ietf.org>; Fri, 28 Jul 2000 22:44:13 -0400 (EDT)
Received: (qmail 21941 invoked by uid 60001); 29 Jul 2000 02:44:14 -0000
Message-ID: <20000729024414.21940.qmail@web209.mail.yahoo.com>
Received: from [216.185.17.129] by web209.mail.yahoo.com; Fri, 28 Jul 2000 19:44:14 PDT
Date: Fri, 28 Jul 2000 19:44:14 -0700 (PDT)
From: kysi ferul <redwingblakburdz@yahoo.com>
Subject: Re: How many nexuses would it take?
To: kysi ferul <redwingblakburdz@yahoo.com>, nanog@merit.edu
Cc: IETF@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org


--- kysi ferul <redwingblakburdz@yahoo.com> wrote:
>  Very much as with the question;
>  "How many were going to St. Ives?"...
> I say the sewcret of maximizing the stability of the
> Internet would lie in the 're-wiring' of the
> CONTENT.
> This is the FIRST, LAST, and ON-GOING, precondition
> to
> being able to CONVERGE all platforms & applications.
>  
>    The correct 'ANSWER' was ONE, but the NECESSARY 
> MATH gives one the old CALENDRICAL COUNT for
> STONEHENGE, which was an event of 2744 Days!   
> 
> Note: forwarded message attached.
> 
> 
> =====
> redwingblakburdz@yahoo.com
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Kick off your party with Yahoo! Invites.
> http://invites.yahoo.com/

> ATTACHMENT part 2 message/rfc822 
> Date: Fri, 28 Jul 2000 10:17:03 -0700 (PDT)
> From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
> Subject: Fwd: Re:DeYoung Museum's Hearst Collection
> To: redwingblakburdz@yahoo.com
> CC: norwegianization@yahoo.com
> 
> 
>  
> 
>   Note: forwarded message attached. 
> 
> 
> 
> Casey Farrell; Designer
> 
> oh_yeah_dot_net@yahoo.com
> 
> This Letter and All Contents Copyright 2000 Casey
> Farrell
> All Rights Reserved
> 
> Copyright 2000 Webmaster@oh-yeah.net
> 
> 
> 
> ---------------------------------
> Do You Yahoo!?
> Kick off your party with Yahoo! Invites.

> ATTACHMENT part 2.2 message/rfc822 
> Date: Thu, 27 Jul 2000 16:04:05 -0700 (PDT)
> From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
> Subject: Re:DeYoung Museum's Hearst Collection
> To: shearst@hearst.com
> CC: twortham@hearst.com
> 
> 
> Casey Farrell, Designer                             
>                                       July 27, 2000
> 
> Attn: Stephen Hearst
> 
>            Dear Sir,
> 
>       I noticed an electronic glitch or two in my
> previous letter to you-here is the succinct correct
> version. My family owned the origianl edifce that is
> today called the DeYoung Museum, it was created from
> the "MUSEUM" a building which was the inspiration
> and template for the CALIFORNIA 
> 
> MID WINTER EXPOSITION of 1894.  The building was
> replete with endowments of all sorts from the "first
> families of California," from bric-a-brac and
> knick-knacks to some very fine paintings, one may
> 
> be even be that 'Rembrandt' they were trying to find
> a provanance for? The mainstay of the exhibition was
> provided by  the Woodward's Gardens collection.
> After 1894 the DeYoung family expressed a desire to
> make the Museum all anew-and by the time I was in
> school, the memorable front section was of course,
> the Great Gallery which was in the amin all from the
> Hearst family.
> 
>    Now we are in a new century, and as a good many
> San Franciscans are as forward looking as the
> 
> previous generation was in both preserving the
> beautiful past, and pioneering the exciting future-I
> wanted to make  sure that you knew that it might be
> time to find a Julian Morgan or  a Maybeck who can
> help you create and develop an  ARCHITECTURE which
> will sustain both the CALIFORNIA  MISSIONS and
> perhaps help assist you in some directional moves
> for HEARST PUBLICATIONS ?
> 
>    Here are a few of my designs which perhaps can be
> of some service in the Internet Age-the idea is to
> create each project as REAL enterprise (NO 'Virtual'
> ..anything!) with a DOMAIN NAME, ("DOT.COM") and a
> PRINT INDUSTRY aside, no matter WHAT the MAIN
> INDUSTRY....
> 
> let's say sports? How about
> http://www.slip.net/~o614275
> 
>  this is "dot.commed" as http://www.614275.com
> 
>  and then there is always textbooks,
> http://www.cam.org/home/Wcoprod/mmpro.htm
> 
> first page 7th entry "California Star"  ("Digital
> High Schools" AB64)
> 
> howabout CHINESE to ENGLISH and ROMAN to CHARACTERS
> tutorial for China WEB PORTAL?
> 
> http://www.slip.net/~navyblue
> 
> and that is to appear at http://www.baozi.org
> 
>     I would like very much to consult with you for
> both Hearst Publications & California Missions,
> 
> and at the moment have picture libraries with
> complimentary art renditions for either Haight
> Ashbury of the 1890's ot The Haight of 1960's, at my
> disposal, can at a moment gather some of the best
> creative writers and historians, and taking all into
> consideration make at the very least a 'prototype'
> of what one  might expect to see as a ARCHIVAL work
> on the INTERNET which is NATURAL and PLEASING! Any
> and All-the More the Merrier! 
> 
>      Please let me know how I may be of service to
> Hearst Newspapers and Hearst Foundation.
> 
>    Thank you,
> 
>        Casey Farrell
> 
> tel:(415 )664-2489
> 
>       This Letter and All Contents Copyright 20000
> webmaster@mv3srok4unyrlsh2.com
> 
>  
> 
>      
> 
>  
> 
> 
> 
> Casey Farrell; Designer
> 
> oh_yeah_dot_net@yahoo.com
> 
> This Letter and All Contents Copyright 2000 Casey
> Farrell
> All Rights Reserved
> 
> Copyright 2000 Webmaster@oh-yeah.net
> 
> 
> 
> ---------------------------------
> Do You Yahoo!?
> Kick off your party with Yahoo! Invites.


=====
redwingblakburdz@yahoo.com



__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/



From owner-ietf-outbound  Sat Jul 29 05:11:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA13440
	for ietf-outbound.10@ietf.org; Sat, 29 Jul 2000 05:10:02 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11098;
	Sat, 29 Jul 2000 05:02:38 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id FAA05623;
	Sat, 29 Jul 2000 05:02:39 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id FAA05614;
	Sat, 29 Jul 2000 05:02:38 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21)
	id <PW2CY6AH>; Sat, 29 Jul 2000 11:02:33 +0200
Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB08717A6B@nl0006exch002u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: ietf@ietf.org
Cc: IESG <iesg@ietf.org>, IAB <iab@ietf.org>
Subject: Operations and Management Area Open Meeting
Date: Sat, 29 Jul 2000 11:02:30 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop: ietf@ietf.org

The O&M Area (OPS) will have an open meeting on thursday afternoon
(see agenda).

The purpose of this meeting is, like previous O&M Area open meetings,
to present/discuss current hot topics in our Area and as a general
forum to discuss common issues.

The OPS co-ADs discussed this a bit, and we felt that folk should 
> hear from _at_least_ those WGs/RGs/BOFs included in the agenda:
> 
  o Pass out Blue sheets, volunteer/assign scribe

  o Agenda Bashing
  
>   o AAA - proposal evaluation process and results
> 
>   o BMWG - how come this WG is so darned productive?
> 
>   o IEPS BOF - what are the operational/management aspects to consider?
> 
>   o NIM BOF - is it time for a new network information model?
> 
>   o NMRG - status on SNMP research issues. ready to move some to IETF?
> 
>   o RMONMIB - where are we wrt application peformance monitoring?
> 
>   o SNMPCONF - what we've done, where we are going
> 
>   o MBONED - which protocol pieces are moving and where
> 
>   o GRIP - where/how to go on the ISP expectations document
> 
>   o NGTRANS - document status and new deployment stories
> 
  o wrapup

> Other working groups are *extremely* welcome and downright solicited to
> join the agenda and/or make suggestion(s) for other agenda items.  Again,
> let us know ASAP if you want to contribute and how much time you expect to
> need.
> 
> Thanks.
> 
> Bert and Randy
> 



From owner-ietf-outbound  Sat Jul 29 10:40:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA06828
	for ietf-outbound.10@ietf.org; Sat, 29 Jul 2000 10:40:03 -0400 (EDT)
Received: from infidel.boolean.net (root@router.boolean.net [198.144.206.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06720
	for <ietf@ietf.org>; Sat, 29 Jul 2000 10:39:39 -0400 (EDT)
Received: from gypsy.OpenLDAP.org (gypsy.boolean.net [198.144.202.243])
	by infidel.boolean.net (8.9.3/8.9.3) with ESMTP id OAA10929
	for <ietf@ietf.org>; Sat, 29 Jul 2000 14:39:40 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <4.3.2.7.0.20000729072417.00b05940@infidel.boolean.net>
X-Sender: guru@infidel.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 29 Jul 2000 07:39:39 -0700
To: ietf@ietf.org
From: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Subject: I-D no action period
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

I would like to propose the introduction of a "no action" period
for Internet Drafts.  Upon (re)publication of an I-D, no action
(except removal) would be allowed upon the I-D for a short
period of time (two weeks?).  No LAST CALLs, no submission
to AD, IESG, RFC-Editor, etc.  This would allow the community a
brief opportunity to point out any flaws in the revisions to
responsible parties desiring to take action upon the I-D.  I
know of a number of cases where immediate action was taken
upon I-Ds with significant flaws which were pointed out within
days of the publication.   A "no action" period would allow a
small window of last minute community review.

	Kurt



From owner-ietf-outbound  Sat Jul 29 12:20:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA04750
	for ietf-outbound.10@ietf.org; Sat, 29 Jul 2000 12:20:02 -0400 (EDT)
Received: from orchard.arlington.ma.us (orchard.hamachi.org [4.255.0.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02413
	for <ietf@ietf.org>; Sat, 29 Jul 2000 12:12:30 -0400 (EDT)
Received: by orchard.arlington.ma.us (Postfix, from userid 587)
	id CC0C92A40; Sat, 29 Jul 2000 12:12:32 -0400 (EDT)
Received: from orchard.arlington.ma.us (localhost [127.0.0.1])
	by orchard.arlington.ma.us (Postfix) with ESMTP
	id 8D51A1F98; Sat, 29 Jul 2000 12:12:32 -0400 (EDT)
To: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Cc: ietf@ietf.org
Subject: Re: I-D no action period 
In-Reply-To: Message from "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 
   of "Sat, 29 Jul 2000 07:39:39 PDT." <4.3.2.7.0.20000729072417.00b05940@infidel.boolean.net> 
Reply-To: sommerfeld@orchard.arlington.ma.us
Date: Sat, 29 Jul 2000 12:12:27 -0400
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
Message-Id: <20000729161232.CC0C92A40@orchard.arlington.ma.us>
X-Loop: ietf@ietf.org

> I would like to propose the introduction of a "no action" period for
> Internet Drafts.  Upon (re)publication of an I-D, no action (except
> removal) would be allowed upon the I-D for a short period of time
> (two weeks?).  No LAST CALLs, no submission to AD, IESG, RFC-Editor,
> etc.  
	[trimmed...]
> A "no action" period would allow a small window of last minute
> community review. 

Isn't that what a last call is?  A two-week window for last minute
community review?

					- Bill



From owner-ietf-outbound  Sat Jul 29 20:10:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA11141
	for ietf-outbound.10@ietf.org; Sat, 29 Jul 2000 20:10:02 -0400 (EDT)
Received: from torque.pothole.com ([38.138.52.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10524
	for <ietf@ietf.org>; Sat, 29 Jul 2000 20:04:37 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id UAA23079;
	Sat, 29 Jul 2000 20:06:52 -0400 (EDT)
Message-Id: <200007300006.UAA23079@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
cc: ietf@ietf.org, poised@lists.tislabs.com
reply-to: poised@lists.tislabs.com
Subject: Re: I-D no action period 
In-reply-to: Your message of "Sat, 29 Jul 2000 07:39:39 PDT."
             <4.3.2.7.0.20000729072417.00b05940@infidel.boolean.net> 
Date: Sat, 29 Jul 2000 20:06:52 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org


I'm certainly opposed to such a rule.  There is already too much
rigidity in the IETF rules.  It is frequently useful to post an
updated version, initiate a Last Call, etc., very shortly after an I-D
is published.

In some cases, an I-D is posted to include and summarize the final
changes decided on by Last Call or IESG review and is then immediately
approved.  There is very rarely a problem in this.  If there is, the
RFC-editor can fix some types of errors, the IESG can reverse itself,
and ultimately new RFCs can be issued to obsolere and replace thsoe
with problems.

No document produced by the IETF is perfect. But there is also a heavy
penalty in timliness to be paid for endless polishing.  The currently
system seems reasonable to me and, if anything, leans too far towards
providing review cycles and delays.

The POISED working group is established to discuss such procedure
questions and I have set the reply-to header of this message to point
to its mailing list.

Thanks,
Donald

From:  "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Message-Id:  <4.3.2.7.0.20000729072417.00b05940@infidel.boolean.net>
Date:  Sat, 29 Jul 2000 07:39:39 -0700
To:  ietf@ietf.org

>I would like to propose the introduction of a "no action" period
>for Internet Drafts.  Upon (re)publication of an I-D, no action
>(except removal) would be allowed upon the I-D for a short
>period of time (two weeks?).  No LAST CALLs, no submission
>to AD, IESG, RFC-Editor, etc.  This would allow the community a
>brief opportunity to point out any flaws in the revisions to
>responsible parties desiring to take action upon the I-D.  I
>know of a number of cases where immediate action was taken
>upon I-Ds with significant flaws which were pointed out within
>days of the publication.   A "no action" period would allow a
>small window of last minute community review.
>
>	Kurt
>



From owner-ietf-outbound  Sun Jul 30 01:10:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA29138
	for ietf-outbound.10@ietf.org; Sun, 30 Jul 2000 01:10:02 -0400 (EDT)
Received: from infidel.boolean.net (root@router.boolean.net [198.144.206.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27585
	for <ietf@ietf.org>; Sun, 30 Jul 2000 01:02:13 -0400 (EDT)
Received: from gypsy.OpenLDAP.org (root@infidel.boolean.net [198.144.202.225])
	by infidel.boolean.net (8.9.3/8.9.3) with ESMTP id FAA12425;
	Sun, 30 Jul 2000 05:01:45 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <4.3.2.7.0.20000729213916.00af0b80@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 29 Jul 2000 21:42:07 -0700
To: sommerfeld@orchard.arlington.ma.us
From: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Subject: Re: I-D no action period 
Cc: ietf@ietf.org
In-Reply-To: <20000729161232.CC0C92A40@orchard.arlington.ma.us>
References: <Message from "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
 <4.3.2.7.0.20000729072417.00b05940@infidel.boolean.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 12:12 PM 7/29/00 -0400, Bill Sommerfeld wrote:
>> I would like to propose the introduction of a "no action" period for
>> Internet Drafts.  Upon (re)publication of an I-D, no action (except
>> removal) would be allowed upon the I-D for a short period of time
>> (two weeks?).  No LAST CALLs, no submission to AD, IESG, RFC-Editor,
>> etc.  
>        [trimmed...]
>> A "no action" period would allow a small window of last minute
>> community review. 
>
>Isn't that what a last call is?  A two-week window for last minute
>community review?

The current process does not provide any mechanism for review
by the community of any changes made based upon LAST CALL comments.
That is, an individual makes comments which prompts changes.
The community, let alone this individual, often are not given any
opportunity to review the changes made.



From owner-ietf-outbound  Sun Jul 30 12:41:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA02660
	for ietf-outbound.10@ietf.org; Sun, 30 Jul 2000 12:40:02 -0400 (EDT)
Received: from mail2.panix.com (mail2.panix.com [166.84.0.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02256
	for <ietf@ietf.org>; Sun, 30 Jul 2000 12:38:11 -0400 (EDT)
From: ronda@panix.com
Received: from panix2.panix.com (panix2.panix.com [166.84.0.227])
	by mail2.panix.com (Postfix) with ESMTP
	id 10F429025; Sun, 30 Jul 2000 12:38:13 -0400 (EDT)
Received: (from ronda@localhost) by panix2.panix.com (8.8.8/8.7.1/PanixN1.0) id MAA03991; Sun, 30 Jul 2000 12:38:12 -0400 (EDT)
Date: Sun, 30 Jul 2000 12:38:12 -0400 (EDT)
Message-Id: <200007301638.MAA03991@panix2.panix.com>
To: comments@icann.org, cpart@interaccess.com, edyson@edventure.com,
        gregcrew@iaa.com.au, icann@icann.org, ietf@ietf.org
Subject: Complaint to Dept of Commerce on abuse of users by ICANN
Cc: abd@cdt.org, baf@fausett.com, bburr@ntia.doc.gov, bdooley@cix.org,
        carl@oppedahl.com, Charles.Pickering@mail.house.gov,
        cpsr-activsts@cpsr.org, cpsr-cyber-rights@cpsr.org,
        dnso.discuss@lists.association.org, dnspolicy@ntia.doc.gov,
        domain-policy@internic.net, eric.menge@sba.gov, falco@vex.net,
        froomkin@law.miami.edu, gconrades@icann.org, glenn@technologylaw.com,
        harryh-dns@quark.cpsr.org, info@name-space.com,
        InfoCker@worldnet.att.net, ivan@netnames.com, JacobsonSJ@aol.com,
        jeri@nytimes.com, KathrynKL@aol.com, kent@songbird.com,
        krose@ntia.doc.gov, list@ifwp.org, lleblanc@leblanc.com,
        love@cptech.org, Mark.Harrington@mail.house.gov, mgordon@pipeline.com,
        michael@memra.com, mleblanc@leblanc.com, process@dnso.org,
        rep.e.b.johnson@mail.house.gov, Rep.Morella@mail.house.gov,
        rlongstaff@leblanc.com, roberts@icann.org, russ@russ-smith.com,
        sdoty@jaxx.net, tchatham@leblanc.com, tkoors@famousbrand.com
X-Loop: ietf@ietf.org

I sent the following to Becky Burr a few minutes ago as a formal 
complaint about the ICANN abuse of users 
My proposal is online at the Dept of Commerce NTIA web site and 
also at http://www.columbia.edu/~rh120/other/dns_proposal.txt
I welcome comments and discussion on the issues raised by the letter
I have sent to Becky Burr and on the actual problem that has to 
be solved to protect and scale the vital functions of the Internet
in the public internet.

Ronda
ronda@panix.com
----------



>Date: Sun, 30 Jul 2000 11:57:34 -0400 (EDT)
>From: <ronda@panix.com>
>To: bburr@ntia.doc.gov, msondow@iciiu.org, tom.bliley@mail.house.gov,
	vcerf@mci.net
>Subject: Formal complaint of abuse of users by ICANN

Becky Burr
NTIA 
U.S. Dept of Commerce
Washington, D.C.

Dear Becky

Have you tried to register for ICANN's membership? First the membership
is an ill conceived notion to try to hide that ICANN has been formed
to deny the public interest with regard to the Internet's names,
numbers and protocols. It's an effort to make it seem that a non profit
corporation can be entrusted with the ownership and control of vital
functions of the infrastructure of the Internet. A nonprofit corporation
can't be entrusted with this. These are vital social and public 
resources and they can't be put into a private sector entity.

However, rather than the US government making it possible to 
examine the problem of how to protect the vital functions of the 
Internet and to scale them in the public interest, ICANN was empowered
by the U.S. Department of Commerce with unbridled powers and a limited 
provision was created for so called "membership" of users, i.e. some 
limited right supposedly to vote for certain so called at large directors. 

Well, people are now trying to sign up for that membership, for that
limited right to vote and it is clear that the ICANN folks are
not even making any access available to that. The version to sign
up at the ICANN web site requires frames. So people who don't have
a browser with frames are not able to even use that part of the 
web site. And an alternative web site set up in another country
gives a message of "We are sorry. The database is currently overloaded.
Please try again when the system is less busy." when I tried to sign
up.

Clearly the whole ICANN model is not appropriate for the needs
of the Internet and its users.

I did propose a different model, and a prototype to build this
model to you before ICANN was given the U.S. Dept of Commerce
contract.

Clearly it was crucial that you explore other models and try
to determine what was the best proposal for the problem the 
U.S. government was faced with, namely how to protect the vital
functions of the Internet from vested interests and to make
it possible for them to scale.

It seems that the U.S. government wasn't even interested
in trying to identify the problem that had to be solved,
let alone in trying to determine how to solve it.

I am formerly objecting to the whole process of the creation
and development of ICANN by the U.S. Department of Commerce,
and requesting that you find a way to have the proposal I 
provided the Department of Commerce implemented.

My proposal provided a means to create meaningful online participation 
by users and for computer scientists supported by their governments
to create an open process that would utilize the Internet and 
its interactive processes to create the cooperative form needed
to safeguard the vital functions of the Internet's infrastructure.
That is what is needed not an institutional entity to encourage
the "vested interests" to fight over power and control over vital
functions of the Internet.

I am sending this to you as a formal complaint of not being
allowed to register with ICANN and asking that you take the necessary
means to stop the abuse of users and the Internet that ICANN 
represents.

Sincerely

Ronda Hauben
244 West 72nd Street Apt 15D
New York, N.Y. 10023
U.S.A.
(212)787-9361
ronda@ais.org






From owner-ietf-outbound  Sun Jul 30 12:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA05398
	for ietf-outbound.10@ietf.org; Sun, 30 Jul 2000 12:50:02 -0400 (EDT)
Received: from fledge.watson.org (root@fledge.watson.org [204.156.12.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03650
	for <ietf@ietf.org>; Sun, 30 Jul 2000 12:43:57 -0400 (EDT)
Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3])
	by fledge.watson.org (8.9.3/8.9.3) with SMTP id MAA46944
	for <ietf@ietf.org>; Sun, 30 Jul 2000 12:43:55 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Date: Sun, 30 Jul 2000 12:43:54 -0400 (EDT)
From: Robert Watson <rwatson@FreeBSD.org>
X-Sender: robert@fledge.watson.org
To: ietf@ietf.org
Subject: pass 2: Pittsburgh August IETF Meeting: FreeBSD dinner, et al? (fwd)
Message-ID: <Pine.NEB.3.96L.1000730124303.46757B-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


Someone suggested I forward this to the IETF discuss mailing list, so I
am.  :-)

  Robert N M Watson 

robert@fledge.watson.org              http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A 79 37  ED 5F 55 E9 58 04 6A B1
TIS Labs at Network Associates, Safeport Network Services

---------- Forwarded message ----------
Date: Mon, 24 Jul 2000 13:00:56 -0400 (EDT)
From: Robert Watson <rwatson@FreeBSD.org>
To: freebsd-hackers@FreeBSD.org, freebsd-net@FreeBSD.org
Subject: pass 2: Pittsburgh August IETF Meeting: FreeBSD dinner, et al? (fwd)

This is a resend of the original as we haven't picked up many people yet.
Please reply to only appropriate addresses. :-)

  Robert N M Watson 

robert@fledge.watson.org              http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A 79 37  ED 5F 55 E9 58 04 6A B1
TIS Labs at Network Associates, Safeport Network Services

---------- Forwarded message ----------
Date: Fri, 14 Jul 2000 00:38:35 -0400 (EDT)
From: Robert Watson <rwatson@FreeBSD.org>
To: freebsd-hackers@FreeBSD.org, freebsd-chat@FreeBSD.org
Subject: Pittsburgh August IETF Meeting: FreeBSD dinner, et al?


So it's coming up on that IETF time of year again, this time in beautiful
(?) down-town Pittsburgh, in the first week of August.

First, I'd like to encourage FreeBSD people to turn out for the event, as
a strong showing in the standards community is great, and keeps the
research projects coming to the platform (bring us things like
industry-standard IP stacks).   IETF meetings are a lot of fun, even if
you don't have the technical background to participate fully.  The hotels
are filling fast, so book soon.

Second, I'd like to bring up the topic of a FreeBSD dinner.  We did one at
the November IETF in DC with relatively good success, last year, although
a reservation in advance is probably a good idea this time :-).  With that
in mind, I'd be glad to help organize things somewhat.  The best day for
me might actually be Monday evening, during the two-hour break, but I'm
open to suggestions here if there are any serious BSD conflicts (i.e., a
KAME meeting or something).  If you're interested in participating, please
feel free to send me an e-mail including:

 Your name
 Your preferred e-mail address
 Your preferred contact mechanism while at IETF (shout, for example, but
    preferably e-mail, or hotel information)
 Whether you would like to attend (obligatory: yes)
 Whether Monday would work for you or not, and if not, why

Hope to see you all there!

  Robert N M Watson 

robert@fledge.watson.org              http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A 79 37  ED 5F 55 E9 58 04 6A B1
TIS Labs at Network Associates, Safeport Network Services



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



From owner-ietf-outbound  Sun Jul 30 13:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA08813
	for ietf-outbound.10@ietf.org; Sun, 30 Jul 2000 13:00:03 -0400 (EDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03651
	for <ietf@ietf.org>; Sun, 30 Jul 2000 12:43:57 -0400 (EDT)
Received: (from itojun@localhost)
	by coconut.itojun.org (8.9.3+3.2W/3.7W) id BAA12184
	for ietf@ietf.org; Mon, 31 Jul 2000 01:43:49 +0900 (JST)
Date: Mon, 31 Jul 2000 01:43:49 +0900 (JST)
From: Jun-ichiro itojun Hagino <itojun@itojun.org>
Message-Id: <200007301643.BAA12184@coconut.itojun.org>
To: ietf@ietf.org
Subject: IETF venue IPv6 network information
X-Loop: ietf@ietf.org

IPv6 is ready and runinng at IETF venue.  see http://www.kame.net/ietf48/ for
detailed info.  you just need to use autoconfiguration, that's all.

itojun



From owner-ietf-outbound  Sun Jul 30 13:16:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA15176
	for ietf-outbound.10@ietf.org; Sun, 30 Jul 2000 13:16:08 -0400 (EDT)
Received: from web221.mail.yahoo.com (web221.mail.yahoo.com [128.11.68.121])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA09065
	for <IETF@ietf.org>; Sun, 30 Jul 2000 13:00:47 -0400 (EDT)
Message-ID: <20000730170048.25248.rocketmail@web221.mail.yahoo.com>
Received: from [216.185.17.222] by web221.mail.yahoo.com; Sun, 30 Jul 2000 10:00:48 PDT
Date: Sun, 30 Jul 2000 10:00:48 -0700 (PDT)
From: kysi ferul <redwingblakburdz@yahoo.com>
Subject:  "The Future of Internet in China:"  by Queen Elizabeth
To: nanog@merit.edu
Cc: IETF@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1804289383-964976448=:25199"
X-Loop: ietf@ietf.org

--0-1804289383-964976448=:25199
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline


Note: forwarded message attached.


=====
redwingblakburdz@yahoo.com



__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/
--0-1804289383-964976448=:25199
Content-Type: message/rfc822

X-Apparently-To: redwingblakburdz@yahoo.com via mdd202.mail.yahoo.com
Received: from web5201.mail.yahoo.com (216.115.106.95)
  by mta140.mail.yahoo.com with SMTP; 30 Jul 2000 09:57:32 -0700 (PDT)
Message-ID: <20000730165732.22875.qmail@web5201.mail.yahoo.com>
Received: from [216.185.17.222] by web5201.mail.yahoo.com; Sun, 30 Jul 2000 09:57:32 PDT
Date: Sun, 30 Jul 2000 09:57:32 -0700 (PDT)
From: Casey Farrell <yr4yn_dot_com@yahoo.com>
Subject:  "The Future of Internet in China:"  by Queen Elizabeth
To: redwingblakburdz@yahoo.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1102520059-964976252=:20503"
Content-Length: 8100

--0-1102520059-964976252=:20503
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline


Note: forwarded message attached.


__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/
--0-1102520059-964976252=:20503
Content-Type: message/rfc822

Received: from [216.185.17.222] by web5203.mail.yahoo.com; Sun, 30 Jul 2000 09:55:59 PDT
Date: Sun, 30 Jul 2000 09:55:59 -0700 (PDT)
From: Casey Farrell <yr4yn_dot_com@yahoo.com>
Subject: "The Future of Internet in China:"  by Queen Elizabeth
To: Hong Kong News <listsupport@internet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 7358


--- Hong Kong News <listsupport@internet.com> wrote:
> ==========================
> Hong Kong InternetNews Weekly
>  July 24-28, 2000
> ==========================
> 
> /-------------------------MAIN
> EVENT-------------------------\ 
> "What is the Future of Internet Advertising in
> Greater China?"

   The Future MUST be "BAOZI" ('Chromatic Pin-Yin')
says Queen Elizabeth. "If we are to communicate in
both
the Roman keyboard and in BIG 5, we must adapt to the 
methods which most ally themselves to real-time
applications on the 'Net. " her Majesty said, last
night asdding that, "Baozi works for both Mandarina
and
cantonese, and in Characters and Roman letters, a good
way in which to teach English, in Hong Kong schools."

http://www.slip.net/~navyblue

http://www.baozi.org


> Sponsor: BMC Media
> Speaker: renren.com's VP Marketing and Sales and
> Chairman of the Internet Advertising Bureau in Hong
> Kong
> 
> 1 August 2000, JW Marriott Hotel Hong Kong,
> 8:00-9:30am
> Cost: Free (includes continental breakfast) SPACE
> LIMITED
> 
> Check it out at:
> http://asia.internet.com/forums.html 
>
\---------------------------------------------------adv.------------/
> 
> In This Issue:
> 
> 1. The Blood Flows
> 2. tom.com Scraps 80 Staff
> 3. CTI Lays Off 200 in Broadband Division
> 4. MarketWatch.com, Asiacontent.com Create Joint
> Venture
> 5. Asia2B Declares Itself "Virtual WTO"
> 6. Yahoo! HK Offers Localized Tools
> 7. Hutchison, Casio, Siemens Ally for Multimedia
> 8. renren Partners with ChengDa for Jobs
> 9. chinadotcom, CCIDNet.com JV for ASP Marketplace
> 10. chinadotcom Joins with InfoIsLive.com
> 
> Internet Event
> 
> 11. What Is The Future of Internet Advertising in
> China?
> _____________________________________
> 
> This service is provided free of charge to the
> Internet community,
> courtesy of internet.com's Asia site: 
> You may SIGN UP for this newsletter and other Asia
> Internet newsletters at
> 
> http://asia.internet.com/e-newsletters.html
> _____________________________________
> 
> 1. The Blood Flows
> --------------------------------------- 
> At least 281 are having a lousy weekend in Hong
> Kong. That extra one is new tom.com CEO Wang Sing,
> who, 10 days after being officially named to the
> position, got to make his first public appearance in
> the post at a press conference to announce and
> clarify rumors that the Internet company was indeed
> cutting 80 staff from its Hong Kong operations.
> Feel bad for the newly jobless, but not for the
> company. On Monday, Hong Kong iMail ran a cover
> story in its iBusiness section about Li Ka-shing’s
> “push on mainland,” with exploring tom.com’s links
> to Chinese Internet companies, including Wang’s
> 163.net and Shanghai Maya Online, a broadband
> content provider in which tom.com recently invested.
> The firings were explained by Wang as a way of
> re-aligning the company’s mainland staff, so that
> personnel would be split 50/50 between Hong Kong and
> its northern neighbor. Do you think the tom.com
> severance package, which Wang described as higher
> than legally required, include tickets to next
> week’s Leslie Cheung concerts, which tom.com is
> sponsoring? Or maybe shares in the company, still
> riding high after its site-less IPO four months ago?
> The office carpet also turned red over at City
> Telecom (CTI), where the company’s broadband
> division sliced over from its workforce. 
> What does this all mean? At the very least, it means
> that the F****d Company Web site will be registering
> a lot more page views from Hong Kong IP addresses,
> now that the latest unemployed will be joining the
> 18 cut from SCMP.com and 100 from Next Media. Is the
> Post Office hiring?
> Asia Internet Stock Report Internet Analyst Brian
> Fan summed up the markets well: “It was a painful
> week for net stocks this week.” GEM actually managed
> to go up, despite 36.com immediately dumping 20
> percent of its value during its IPO Tuesday, and
> SEHK-listed i100 hit the treadmill and similarly
> lost over 22 percent. Hey, can I borrow that copy of
> Recruit? 
> By Steven Schwankert, Managing Editor,
> asia.internet.com
>
/-------------------------------------------------------------------\
> FREE FOOD & INTELLIGENT DISCUSSION
> internet.com's Breakfast Forums - Hong Kong Edition
> 
> "What is the future of Internet Advertising in
> Greater China?"
> By Richard Robinson, renren.com's VP Marketing and
> Sales and
> Chairman of the Internet Advertising Bureau in Hong
> Kong
>  
> 1 August 2000, JW Marriott Hong Kong, 8:00am -
> 9:30am
> Cost: Free (includes continental breakfast)
>  
> SPACE LIMITED 
> Contact mailto:hcheung@internet.com or check it out
> at
> http://asia.internet.com/forums.html
>
\--------------------------------------------------------------adv.-/
> 
> The Week in Review
> -------------------------
> 
> 2>> tom.com Scraps 80 Staff
> 
> [July 28--HONG KONG] One month after its official
> launch, tom.com [8001
> HK] announced on Friday plans to lay off 80 staff
> members in a realignment
> of resources.
> 
> Full Story>>
> http://asia.internet.com/2000/7/2801-tom.html
> 
> /-------------------------------------------------\
> Asia Internet VC Watch
> VC buzz, biggest deals and startup profiles.
> Sign up for this e-mail 
> newsletter and others at:
> http://asia.internet.com/e-newsletters.html
> \--------------------------------------------adv.-/
> 
> 3>> CTI Fires 200 in Broadband Division
> 
> [July 28--HONG KONG] Hong Kong-based
> telecommunication company City
> Telecommunication [1137 HK] (CTI) announced on
> Thursday the termination of
> 200 staff in its newly-launched subsidiary Hong Kong
> Broadband.
> 
> Full Story>>
> http://asia.internet.com/2000/7/2802-cti.html
> --------------
> 
> 4>>MarketWatch.com, Asiacontent.com Create Joint
> Venture
> 
> [July 28--HONG KONG] MarketWatch.com, Inc.
> (Nasdaq:MKTW) and
> Asiacontent.com, Ltd. (Nasdaq:IASIA) announced
> Thursday a memorandum of
> understanding to form a joint venture to create a
> network of
> MarketWatch.com-branded financial Web sites
> throughout Asia.
> 
> Full Story>>
>
http://asia.internet.com/2000/7/2806-marketwatch.html
> 
> -------------------------
> 
> 5>>Asia2B Declares Itself "Virtual WTO"
> 
> [July 27--HONG KONG] B2B site Asia2B.com Limited
> soft-launched Thursday in Hong Kong in a
> presentation long on superlatives and short on
> innovation.
> 
> Full Story>>
> http://asia.internet.com/2000/7/2702-asia2b.html 
> --------------
> 
> 6>>Yahoo! HK Offers Localized Tools
> 
> [July 27--HONG KONG] Yahoo! Hong Kong announced the
> formal launch of its localized version of integrated
> communication tools on Thursday.
> 
> Full Story>>
> http://asia.internet.com/2000/7/2709-yahoo.html 
> -------------------------
> 
> 7>>Hutchison, Casio, Siemens Ally for Multimedia
> 
> [July 26--HONG KONG] Hutchison Telecom, Casio and
> Siemens announced
> Wednesday a strategic alliance to offer mobile
> multimedia communications solutions, which allow
> access to Hutchison's Orange mobile network through
> Casio's Personal Digital Assistant (PDA).
> 
> Full Story>>
> http://asia.internet.com/2000/7/2601-hutchison.html 
> 
=== message truncated ===


__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/

--0-1102520059-964976252=:20503--
--0-1804289383-964976448=:25199--



From owner-ietf-outbound  Sun Jul 30 13:20:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA16522
	for ietf-outbound.10@ietf.org; Sun, 30 Jul 2000 13:20:02 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET ([166.60.6.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09100
	for <ietf@ietf.org>; Sun, 30 Jul 2000 13:00:53 -0400 (EDT)
Received: from cerf.mci.net ([166.60.14.59])
 by shoe.reston.mci.net (PMDF V5.2-32 #40475)
 with ESMTPA id <01JSDNMDLRM49N458O@shoe.reston.mci.net> for ietf@ietf.org;
 Sun, 30 Jul 2000 13:00:39 EST
Date: Sun, 30 Jul 2000 13:00:35 -0400
From: "vinton g. cerf" <vcerf@MCI.NET>
Subject: Re: Complaint to Dept of Commerce on abuse of users by ICANN
In-reply-to: <200007301638.MAA03991@panix2.panix.com>
X-Sender: vcerf@shoe.reston.mci.net
To: ronda@panix.com, comments@icann.org, cpart@interaccess.com,
        edyson@edventure.com, gregcrew@iaa.com.au, icann@icann.org,
        ietf@ietf.org
Cc: abd@cdt.org, baf@fausett.com, bburr@ntia.doc.gov, bdooley@cix.org,
        carl@oppedahl.com, Charles.Pickering@mail.house.gov,
        cpsr-activsts@cpsr.org, cpsr-cyber-rights@cpsr.org,
        dnso.discuss@lists.association.org, dnspolicy@ntia.doc.gov,
        domain-policy@INTERNIC.NET, eric.menge@sba.gov, falco@vex.net,
        froomkin@law.miami.edu, gconrades@icann.org, glenn@technologylaw.com,
        harryh-dns@quark.cpsr.org, info@name-space.com,
        InfoCker@worldnet.att.net, ivan@netnames.com, JacobsonSJ@aol.com,
        jeri@nytimes.com, KathrynKL@aol.com, kent@songbird.com,
        krose@ntia.doc.gov, list@ifwp.org, lleblanc@leblanc.com,
        love@cptech.org, Mark.Harrington@mail.house.gov, mgordon@pipeline.com,
        michael@memra.com, mleblanc@leblanc.com, process@dnso.org,
        rep.e.b.johnson@mail.house.gov, Rep.Morella@mail.house.gov,
        rlongstaff@leblanc.com, roberts@icann.org, russ@russ-smith.com,
        sdoty@jaxx.net, tchatham@leblanc.com, tkoors@famousbrand.com
Message-id: <4.3.1.2.20000730130025.08839008@shoe.reston.mci.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7BIT

and I replied:

Ronda,

have you taken time to look into the numbers of people trying to 
register? do you know what the planning estimates were before
registration campaigns were initiated by various organizations?
The planning numbers for registration were on the order of 10,000
people. As of a few days ago something like 145,000 people had
sent in raw registrations. Keep in mind also that there is a
PIN number that has to be sent by mail. There is a calendar
schedule that ICANN is trying to keep for the election itself,
so the PINs have to get to the voters in time for that. 

Every possible effort was made to increase the rate at which
registrations could be processed and we've gone from about 1000
a day to an artificially limited 5,000 per day (200 per hour)
simply because staff time to process is limited. Registrations
close July 31. 

We all understand that the demand for this franchise far exceeds
our ability to satisfy it in this election cycle. An in-depth study
of the whole process is scheduled to begin after this election,
Ronda - perhaps you were unaware of that? The board detailed specific
areas to be considered. Perhaps the most effective way for your
idea to be considered is to arrange for your proposal to be made
available to the ICANN board?

Vint Cerf


At 12:38 PM 7/30/2000 -0400, ronda@panix.com wrote:
>I sent the following to Becky Burr a few minutes ago as a formal 
>complaint about the ICANN abuse of users 
>My proposal is online at the Dept of Commerce NTIA web site and 
>also at http://www.columbia.edu/~rh120/other/dns_proposal.txt
>I welcome comments and discussion on the issues raised by the letter
>I have sent to Becky Burr and on the actual problem that has to 
>be solved to protect and scale the vital functions of the Internet
>in the public internet.
>
>Ronda
>ronda@panix.com
>----------
>
>
>
> >Date: Sun, 30 Jul 2000 11:57:34 -0400 (EDT)
> >From: <ronda@panix.com>
> >To: bburr@ntia.doc.gov, msondow@iciiu.org, tom.bliley@mail.house.gov,
>         vcerf@mci.net
> >Subject: Formal complaint of abuse of users by ICANN
>
>Becky Burr
>NTIA 
>U.S. Dept of Commerce
>Washington, D.C.
>
>Dear Becky
>
>Have you tried to register for ICANN's membership? First the membership
>is an ill conceived notion to try to hide that ICANN has been formed
>to deny the public interest with regard to the Internet's names,
>numbers and protocols. It's an effort to make it seem that a non profit
>corporation can be entrusted with the ownership and control of vital
>functions of the infrastructure of the Internet. A nonprofit corporation
>can't be entrusted with this. These are vital social and public 
>resources and they can't be put into a private sector entity.
>
>However, rather than the US government making it possible to 
>examine the problem of how to protect the vital functions of the 
>Internet and to scale them in the public interest, ICANN was empowered
>by the U.S. Department of Commerce with unbridled powers and a limited 
>provision was created for so called "membership" of users, i.e. some 
>limited right supposedly to vote for certain so called at large directors. 
>
>Well, people are now trying to sign up for that membership, for that
>limited right to vote and it is clear that the ICANN folks are
>not even making any access available to that. The version to sign
>up at the ICANN web site requires frames. So people who don't have
>a browser with frames are not able to even use that part of the 
>web site. And an alternative web site set up in another country
>gives a message of "We are sorry. The database is currently overloaded.
>Please try again when the system is less busy." when I tried to sign
>up.
>
>Clearly the whole ICANN model is not appropriate for the needs
>of the Internet and its users.
>
>I did propose a different model, and a prototype to build this
>model to you before ICANN was given the U.S. Dept of Commerce
>contract.
>
>Clearly it was crucial that you explore other models and try
>to determine what was the best proposal for the problem the 
>U.S. government was faced with, namely how to protect the vital
>functions of the Internet from vested interests and to make
>it possible for them to scale.
>
>It seems that the U.S. government wasn't even interested
>in trying to identify the problem that had to be solved,
>let alone in trying to determine how to solve it.
>
>I am formerly objecting to the whole process of the creation
>and development of ICANN by the U.S. Department of Commerce,
>and requesting that you find a way to have the proposal I 
>provided the Department of Commerce implemented.
>
>My proposal provided a means to create meaningful online participation 
>by users and for computer scientists supported by their governments
>to create an open process that would utilize the Internet and 
>its interactive processes to create the cooperative form needed
>to safeguard the vital functions of the Internet's infrastructure.
>That is what is needed not an institutional entity to encourage
>the "vested interests" to fight over power and control over vital
>functions of the Internet.
>
>I am sending this to you as a formal complaint of not being
>allowed to register with ICANN and asking that you take the necessary
>means to stop the abuse of users and the Internet that ICANN 
>represents.
>
>Sincerely
>
>Ronda Hauben
>244 West 72nd Street Apt 15D
>New York, N.Y. 10023
>U.S.A.
>(212)787-9361
>ronda@ais.org
>
>

=================================================================
I moved to a new MCI WorldCom facility on Nov 11, 1999

MCI WorldCom
22001 Loudoun County Parkway
Building F2, Room 4115, ATTN: Vint Cerf
Ashburn, VA 20147
Telephone (703) 886-1690
FAX (703) 886-0047


"INTERNET IS FOR EVERYONE!" 
INET 2001: Internet Global Summit 
5-8 June 2001 
Sweden International Fairs 
Stockholm, Sweden 
http://www.isoc.org/inet2001





From owner-ietf-outbound  Sun Jul 30 13:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA19493
	for ietf-outbound.10@ietf.org; Sun, 30 Jul 2000 13:30:03 -0400 (EDT)
Received: from web209.mail.yahoo.com (web209.mail.yahoo.com [128.11.68.109])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA09577
	for <IETF@ietf.org>; Sun, 30 Jul 2000 13:01:54 -0400 (EDT)
Received: (qmail 6078 invoked by uid 60001); 30 Jul 2000 17:01:54 -0000
Message-ID: <20000730170154.6077.qmail@web209.mail.yahoo.com>
Received: from [216.185.17.222] by web209.mail.yahoo.com; Sun, 30 Jul 2000 10:01:54 PDT
Date: Sun, 30 Jul 2000 10:01:54 -0700 (PDT)
From: kysi ferul <redwingblakburdz@yahoo.com>
Subject: Re: "The Future of Internet in China:"  by Queen Elizabeth
To: kysi ferul <redwingblakburdz@yahoo.com>, nanog@merit.edu
Cc: IETF@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org


--- kysi ferul <redwingblakburdz@yahoo.com> wrote:
> 
> Note: forwarded message attached.
> 
> 
> =====
> redwingblakburdz@yahoo.com
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Kick off your party with Yahoo! Invites.
> http://invites.yahoo.com/

> ATTACHMENT part 2 message/rfc822 
> Date: Sun, 30 Jul 2000 09:57:32 -0700 (PDT)
> From: Casey Farrell <yr4yn_dot_com@yahoo.com>
> Subject:  "The Future of Internet in China:"  by
> Queen Elizabeth
> To: redwingblakburdz@yahoo.com
> 
> 
> Note: forwarded message attached.
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Kick off your party with Yahoo! Invites.
> http://invites.yahoo.com/

> ATTACHMENT part 2.2 message/rfc822 
> Date: Sun, 30 Jul 2000 09:55:59 -0700 (PDT)
> From: Casey Farrell <yr4yn_dot_com@yahoo.com>
> Subject: "The Future of Internet in China:"  by
> Queen Elizabeth
> To: Hong Kong News <listsupport@internet.com>
> 
> 
> --- Hong Kong News <listsupport@internet.com> wrote:
> > ==========================
> > Hong Kong InternetNews Weekly
> >  July 24-28, 2000
> > ==========================
> > 
> > /-------------------------MAIN
> > EVENT-------------------------\ 
> > "What is the Future of Internet Advertising in
> > Greater China?"
> 
>    The Future MUST be "BAOZI" ('Chromatic Pin-Yin')
> says Queen Elizabeth. "If we are to communicate in
> both
> the Roman keyboard and in BIG 5, we must adapt to
> the 
> methods which most ally themselves to real-time
> applications on the 'Net. " her Majesty said, last
> night asdding that, "Baozi works for both Mandarina
> and
> cantonese, and in Characters and Roman letters, a
> good
> way in which to teach English, in Hong Kong
> schools."
> 
> http://www.slip.net/~navyblue
> 
> http://www.baozi.org
> 
> 
> > Sponsor: BMC Media
> > Speaker: renren.com's VP Marketing and Sales and
> > Chairman of the Internet Advertising Bureau in
> Hong
> > Kong
> > 
> > 1 August 2000, JW Marriott Hotel Hong Kong,
> > 8:00-9:30am
> > Cost: Free (includes continental breakfast) SPACE
> > LIMITED
> > 
> > Check it out at:
> > http://asia.internet.com/forums.html 
> >
>
\---------------------------------------------------adv.------------/
> > 
> > In This Issue:
> > 
> > 1. The Blood Flows
> > 2. tom.com Scraps 80 Staff
> > 3. CTI Lays Off 200 in Broadband Division
> > 4. MarketWatch.com, Asiacontent.com Create Joint
> > Venture
> > 5. Asia2B Declares Itself "Virtual WTO"
> > 6. Yahoo! HK Offers Localized Tools
> > 7. Hutchison, Casio, Siemens Ally for Multimedia
> > 8. renren Partners with ChengDa for Jobs
> > 9. chinadotcom, CCIDNet.com JV for ASP Marketplace
> > 10. chinadotcom Joins with InfoIsLive.com
> > 
> > Internet Event
> > 
> > 11. What Is The Future of Internet Advertising in
> > China?
> > _____________________________________
> > 
> > This service is provided free of charge to the
> > Internet community,
> > courtesy of internet.com's Asia site: 
> > You may SIGN UP for this newsletter and other Asia
> > Internet newsletters at
> > 
> > http://asia.internet.com/e-newsletters.html
> > _____________________________________
> > 
> > 1. The Blood Flows
> > --------------------------------------- 
> > At least 281 are having a lousy weekend in Hong
> > Kong. That extra one is new tom.com CEO Wang Sing,
> > who, 10 days after being officially named to the
> > position, got to make his first public appearance
> in
> > the post at a press conference to announce and
> > clarify rumors that the Internet company was
> indeed
> > cutting 80 staff from its Hong Kong operations.
> > Feel bad for the newly jobless, but not for the
> > company. On Monday, Hong Kong iMail ran a cover
> > story in its iBusiness section about Li Ka-shing’s
> > “push on mainland,” with exploring tom.com’s links
> > to Chinese Internet companies, including Wang’s
> > 163.net and Shanghai Maya Online, a broadband
> > content provider in which tom.com recently
> invested.
> > The firings were explained by Wang as a way of
> > re-aligning the company’s mainland staff, so that
> > personnel would be split 50/50 between Hong Kong
> and
> > its northern neighbor. Do you think the tom.com
> > severance package, which Wang described as higher
> > than legally required, include tickets to next
> > week’s Leslie Cheung concerts, which tom.com is
> > sponsoring? Or maybe shares in the company, still
> > riding high after its site-less IPO four months
> ago?
> > The office carpet also turned red over at City
> > Telecom (CTI), where the company’s broadband
> > division sliced over from its workforce. 
> > What does this all mean? At the very least, it
> means
> > that the F****d Company Web site will be
> registering
> > a lot more page views from Hong Kong IP addresses,
> > now that the latest unemployed will be joining the
> > 18 cut from SCMP.com and 100 from Next Media. Is
> the
> > Post Office hiring?
> > Asia Internet Stock Report Internet Analyst Brian
> > Fan summed up the markets well: “It was a painful
> > week for net stocks this week.” GEM actually
> managed
> > to go up, despite 36.com immediately dumping 20
> > percent of its value during its IPO Tuesday, and
> > SEHK-listed i100 hit the treadmill and similarly
> > lost over 22 percent. Hey, can I borrow that copy
> of
> > Recruit? 
> > By Steven Schwankert, Managing Editor,
> > asia.internet.com
> >
>
/-------------------------------------------------------------------\
> > FREE FOOD & INTELLIGENT DISCUSSION
> > internet.com's Breakfast Forums - Hong Kong
> Edition
> > 
> > "What is the future of Internet Advertising in
> > Greater China?"
> > By Richard Robinson, renren.com's VP Marketing and
> > Sales and
> > Chairman of the Internet Advertising Bureau in
> Hong
> > Kong
> >  
> > 1 August 2000, JW Marriott Hong Kong, 8:00am -
> > 9:30am
> > Cost: Free (includes continental breakfast)
> >  
> > SPACE LIMITED 
> > Contact mailto:hcheung@internet.com or check it
> out
> > at
> > http://asia.internet.com/forums.html
> >
>
\--------------------------------------------------------------adv.-/
> > 
> > The Week in Review
> > -------------------------
> > 
> > 2>> tom.com Scraps 80 Staff
> > 
> > [July 28--HONG KONG] One month after its official
> > launch, tom.com [8001
> > HK] announced on Friday plans to lay off 80 staff
> > members in a realignment
> > of resources.
> > 
> > Full Story>>
> > http://asia.internet.com/2000/7/2801-tom.html
> > 
> >
> /-------------------------------------------------\
> > Asia Internet VC Watch
> > VC buzz, biggest deals and startup profiles.
> > Sign up for this e-mail 
> > newsletter and others at:
> > http://asia.internet.com/e-newsletters.html
> >
> \--------------------------------------------adv.-/
> > 
> > 3>> CTI Fires 200 in Broadband Division
> > 
> > [July 28--HONG KONG] Hong Kong-based
> > telecommunication company City
> > Telecommunication [1137 HK] (CTI) announced on
> > Thursday the termination of
> > 200 staff in its newly-launched subsidiary Hong
> Kong
> > Broadband.
> > 
> > Full Story>>
> > http://asia.internet.com/2000/7/2802-cti.html
> > --------------
> > 
> > 4>>MarketWatch.com, Asiacontent.com Create Joint
> > Venture
> > 
> > [July 28--HONG KONG] MarketWatch.com, Inc.
> > (Nasdaq:MKTW) and
> > Asiacontent.com, Ltd. (Nasdaq:IASIA) announced
> > Thursday a memorandum of
> 
=== message truncated ===


=====
redwingblakburdz@yahoo.com



__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/



From owner-ietf-outbound  Sun Jul 30 14:00:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA28280
	for ietf-outbound.10@ietf.org; Sun, 30 Jul 2000 14:00:02 -0400 (EDT)
Received: from 5015.consumer.net ([209.237.131.115])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27049
	for <ietf@ietf.org>; Sun, 30 Jul 2000 13:54:37 -0400 (EDT)
Received: from CJ52269A ([24.10.226.181]) by 5015.consumer.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-52914U100L100S0V35)
          with SMTP id net; Sun, 30 Jul 2000 13:51:41 -0400
From: "Russ Smith" <russ@consumer.net>
To: "vinton g. cerf" <vcerf@mci.net>, <ronda@panix.com>, <comments@icann.org>,
        <cpart@interaccess.com>, <edyson@edventure.com>, <gregcrew@iaa.com.au>,
        <icann@icann.org>, <ietf@ietf.org>
Cc: <abd@cdt.org>, <baf@fausett.com>, <bburr@ntia.doc.gov>, <bdooley@cix.org>,
        <carl@oppedahl.com>, <Charles.Pickering@mail.house.gov>,
        <cpsr-activsts@cpsr.org>, <cpsr-cyber-rights@cpsr.org>,
        <dnso.discuss@lists.association.org>, <dnspolicy@ntia.doc.gov>,
        <domain-policy@INTERNIC.NET>, <eric.menge@sba.gov>, <falco@vex.net>,
        <froomkin@law.miami.edu>, <gconrades@icann.org>,
        <glenn@technologylaw.com>, <harryh-dns@quark.cpsr.org>,
        <info@name-space.com>, <InfoCker@worldnet.att.net>,
        <ivan@netnames.com>, <JacobsonSJ@aol.com>, <jeri@nytimes.com>,
        <KathrynKL@aol.com>, <kent@songbird.com>, <krose@ntia.doc.gov>,
        <list@ifwp.org>, <lleblanc@leblanc.com>, <love@cptech.org>,
        <Mark.Harrington@mail.house.gov>, <mgordon@pipeline.com>,
        <michael@memra.com>, <mleblanc@leblanc.com>, <process@dnso.org>,
        <rep.e.b.johnson@mail.house.gov>, <Rep.Morella@mail.house.gov>,
        <rlongstaff@leblanc.com>, <roberts@icann.org>, <russ@russ-smith.com>,
        <sdoty@jaxx.net>, <tchatham@leblanc.com>, <tkoors@famousbrand.com>
Subject: RE: Complaint to Dept of Commerce on abuse of users by ICANN
Date: Sun, 30 Jul 2000 13:54:19 -0400
Message-ID: <000901bffa4f$2f7f8570$b5e20a18@alex1.va.home.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 8.5, Build 4.71.2173.0
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
In-Reply-To: <4.3.1.2.20000730130025.08839008@shoe.reston.mci.net>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>have you taken time to look into the numbers of people trying to
>register? do you know what the planning estimates were before
>registration campaigns were initiated by various organizations?
>The planning numbers for registration were on the order of 10,000
>people. As of a few days ago something like 145,000 people had


This excuse follows the same "excuse pattern" that ICANN provides for almost
every problem.  What keeps happening is that these groups that do the
"planning" do so in secret and routinely ignore comments and often do not
know what they are doing.  Then when all kinds of problems occur due to the
faulty planning there are all these claims that some schedule must be met
and that anyone who wants to correct the problems is trying to slow down the
process and should be ignored.

The same thing happened with the UDRP.  When that was written many people
complained about no appeals process (short of filing a lawsuit).  There are
also extremely short deadlines for responding to a complaint or filing the
"appeal" lawsuit (10 days).  The excuse that was given was that these
appeals were only a delaying tactic by "cybersquatters".  Here we are 8
months into the UDRP process and all kinds of problems have been identified
with some of decisions rendered.  The lack of an appeals process has
resulted in at least 5 federal lawsuits and there have been numerous
complaints about the short deadlines.  Now that people are asking ICANN to
fix it we get brushed off.  McLaughlin recommended lawyers publish the UDRP
problems in legal journals so ICANN can review these some time in the
future.  Meanwhile, known problem that could be corrected are allowed to
continue.

There have been 2 reconsideration requests filed concerning the issue of
ICANN posting the appeals lawsuits in the list of decisions.  ICANN's
response to the request
included:http://www.icann.org/reconsideration/rc00-5.htm

"The ICANN tables do not include notations relating to subsequent
litigation, because the ICANN staff is simply too small and too
overstretched to monitor and verify the hundreds of legal disputes that will
surely ensue."

This response is misleading as the only thing that needs to be monitored and
published is whether a domain owner files a lawsuit within 10 days and has
the domain transfer stopped.  I filed a reconsideration request on this
matter (based on ICANN's misleading response) and that reconsideration
request has been ignored.

Russ Smith
http://consumer.net



From owner-ietf-outbound  Sun Jul 30 14:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA03916
	for ietf-outbound.10@ietf.org; Sun, 30 Jul 2000 14:20:04 -0400 (EDT)
Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02492
	for <ietf@ietf.org>; Sun, 30 Jul 2000 14:13:34 -0400 (EDT)
Received: from vaio.Fenello.com (user-38ld5ho.dialup.mindspring.com [209.86.150.56])
	by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id OAA04265;
	Sun, 30 Jul 2000 14:13:13 -0400 (EDT)
Message-Id: <4.3.1.2.20000730141416.00b958a0@mail.mindspring.com>
X-Sender: jfenello@mail.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 30 Jul 2000 14:15:29 -0400
To: "vinton g. cerf" <vcerf@mci.net>
From: Jay Fenello <Jay@Fenello.com>
Subject: Re: [IFWP] Re: Complaint to Dept of Commerce on abuse of users
  by ICANN
Cc: ronda@panix.com, comments@icann.org, cpart@interaccess.com,
        edyson@edventure.com, gregcrew@iaa.com.au, icann@icann.org,
        ietf@ietf.org, abd@cdt.org, baf@fausett.com, bburr@ntia.doc.gov,
        bdooley@cix.org, carl@oppedahl.com, Charles.Pickering@mail.house.gov,
        cpsr-activsts@cpsr.org, cpsr-cyber-rights@cpsr.org,
        dnso.discuss@lists.association.org, dnspolicy@ntia.doc.gov,
        domain-policy@INTERNIC.NET, eric.menge@sba.gov, falco@vex.net,
        froomkin@law.miami.edu, gconrades@icann.org, glenn@technologylaw.com,
        harryh-dns@quark.cpsr.org, info@name-space.com,
        InfoCker@worldnet.att.net, ivan@netnames.com, JacobsonSJ@aol.com,
        jeri@nytimes.com, KathrynKL@aol.com, kent@songbird.com,
        krose@ntia.doc.gov, list@ifwp.org, lleblanc@leblanc.com,
        love@cptech.org, Mark.Harrington@mail.house.gov, mgordon@pipeline.com,
        michael@memra.com, mleblanc@leblanc.com, process@dnso.org,
        rep.e.b.johnson@mail.house.gov, Rep.Morella@mail.house.gov,
        rlongstaff@leblanc.com, roberts@icann.org, russ@russ-smith.com,
        sdoty@jaxx.net, tchatham@leblanc.com, tkoors@famousbrand.com
In-Reply-To: <4.3.1.2.20000730130025.08839008@shoe.reston.mci.net>
References: <200007301638.MAA03991@panix2.panix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 01:00 PM 7/30/00, vinton g. cerf wrote:
>and I replied:
>
>Ronda,


Hi Vint,

It is thoroughly disheartening to see one of
the founding fathers of the Internet become
just another run-of-the-mill ICANN apologist.


>have you taken time to look into the numbers of people trying to
>register? do you know what the planning estimates were before
>registration campaigns were initiated by various organizations?


There's an old saying --
   "A lack of planning on your part, does
   not constitute an emergency on our part."

Frankly, even calling those bogus Membership
Committee processes "planning" is a joke.  If
anything, it was an exercise in "how do we
give the *appearances* of accountability and
representation, without really doing so."

If ICANN was so concerned about doing studies
about representation before proceeding, then why
didn't they worry about "representation" when the
initial board was announced?  Why didn't they
worry about studies when the DNSO structure
(another gamed entity) was announced?

What's truly ironic is the double standard that
applies to user representation.  Why do people
who were initially funded by the U.S. Government
(with U.S. taxpayer dollars) somehow feel that
they have some kind of God-given right to assume
control over ICANN, and make these decisions for
all Netizens of the World?


>The planning numbers for registration were on the order of 10,000
>people.


A case of bad planning, or gaming gone bad?

I'll remind you that ICANN was originally promoted
as some obscure technical coordination society, despite
repeated claims from the outside that it was much more
important than that (Post, Froomkin, Mueller, et al.)

Now that the Internet community realizes that they've
been lied to, they want to participate in the process.
I can't blame them.  In fact, if I thought for a minute
that my vote would make a difference, I would join in a
heartbeat (or at least *try* and join :-).

I now know better than that :-(

Jay.


>As of a few days ago something like 145,000 people had
>sent in raw registrations. Keep in mind also that there is a
>PIN number that has to be sent by mail. There is a calendar
>schedule that ICANN is trying to keep for the election itself,
>so the PINs have to get to the voters in time for that.
>
>Every possible effort was made to increase the rate at which
>registrations could be processed and we've gone from about 1000
>a day to an artificially limited 5,000 per day (200 per hour)
>simply because staff time to process is limited. Registrations
>close July 31.
>
>We all understand that the demand for this franchise far exceeds
>our ability to satisfy it in this election cycle. An in-depth study
>of the whole process is scheduled to begin after this election,
>Ronda - perhaps you were unaware of that? The board detailed specific
>areas to be considered. Perhaps the most effective way for your
>idea to be considered is to arrange for your proposal to be made
>available to the ICANN board?
>
>Vint Cerf
>
>At 11:57 AM 7/30/2000 -0400, ronda@panix.com wrote:
> >Becky Burr
> >NTIA
> >U.S. Dept of Commerce
> >Washington, D.C.
> >
> >Dear Becky
> >
> >Have you tried to register for ICANN's membership? First the membership
> >is an ill conceived notion to try to hide that ICANN has been formed
> >to deny the public interest with regard to the Internet's names,
> >numbers and protocols. It's an effort to make it seem that a non profit
> >corporation can be entrusted with the ownership and control of vital
> >functions of the infrastructure of the Internet. A nonprofit corporation
> >can't be entrusted with this. These are vital social and public
> >resources and they can't be put into a private sector entity.
> >
> >However, rather than the US government making it possible to
> >examine the problem of how to protect the vital functions of the
> >Internet and to scale them in the public interest, ICANN was empowered
> >by the U.S. Department of Commerce with unbridled powers and a limited
> >provision was created for so called "membership" of users, i.e. some
> >limited right supposedly to vote for certain so called at large directors.
> >
> >Well, people are now trying to sign up for that membership, for that
> >limited right to vote and it is clear that the ICANN folks are
> >not even making any access available to that. The version to sign
> >up at the ICANN web site requires frames. So people who don't have
> >a browser with frames are not able to even use that part of the
> >web site. And an alternative web site set up in another country
> >gives a message of "We are sorry. The database is currently overloaded.
> >Please try again when the system is less busy." when I tried to sign
> >up.
> >
> >Clearly the whole ICANN model is not appropriate for the needs
> >of the Internet and its users.
> >
> >I did propose a different model, and a prototype to build this
> >model to you before ICANN was given the U.S. Dept of Commerce
> >contract.
> >
> >Clearly it was crucial that you explore other models and try
> >to determine what was the best proposal for the problem the
> >U.S. government was faced with, namely how to protect the vital
> >functions of the Internet from vested interests and to make
> >it possible for them to scale.
> >
> >It seems that the U.S. government wasn't even interested
> >in trying to identify the problem that had to be solved,
> >let alone in trying to determine how to solve it.
> >
> >I am formerly objecting to the whole process of the creation
> >and development of ICANN by the U.S. Department of Commerce,
> >and requesting that you find a way to have the proposal I
> >provided the Department of Commerce implemented.
> >
> >My proposal provided a means to create meaningful online participation
> >by users and for computer scientists supported by their governments
> >to create an open process that would utilize the Internet and
> >its interactive processes to create the cooperative form needed
> >to safeguard the vital functions of the Internet's infrastructure.
> >That is what is needed not an institutional entity to encourage
> >the "vested interests" to fight over power and control over vital
> >functions of the Internet.
> >
> >I am sending this to you as a formal complaint of not being
> >allowed to register with ICANN and asking that you take the necessary
> >means to stop the abuse of users and the Internet that ICANN
> >represents.
> >
> >Sincerely
> >
> >Ronda Hauben
> >244 West 72nd Street Apt 15D
> >New York, N.Y. 10023
> >U.S.A.
> >(212)787-9361
> >ronda@ais.org
> >
>
>=================================================================
>I moved to a new MCI WorldCom facility on Nov 11, 1999
>
>MCI WorldCom
>22001 Loudoun County Parkway
>Building F2, Room 4115, ATTN: Vint Cerf
>Ashburn, VA 20147
>Telephone (703) 886-1690
>FAX (703) 886-0047
>
>
>"INTERNET IS FOR EVERYONE!"
>INET 2001: Internet Global Summit
>5-8 June 2001
>Sweden International Fairs
>Stockholm, Sweden
>http://www.isoc.org/inet2001


Respectfully,

Jay Fenello,
New Media Strategies
------------------------------------
http://www.fenello.com  770-392-9480
Aligning with Purpose(sm) ... for a Better World
-------------------------------------------------------
"We are witness to the emergence of an epic struggle
between corporate globalization and popular democracy."
http://cyberjournal.org/cj/korten/korten_feasta.shtml
    -- David Korten



From owner-ietf-outbound  Sun Jul 30 23:30:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA27113
	for ietf-outbound.10@ietf.org; Sun, 30 Jul 2000 23:30:03 -0400 (EDT)
Received: from roam.psg.com (wired-128-128.ietf.marconi.com [147.73.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26522
	for <ietf@ietf.org>; Sun, 30 Jul 2000 23:27:25 -0400 (EDT)
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 13IwMd-0000WQ-00; Sun, 30 Jul 2000 12:54:59 -0400
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: ronda@panix.com
Cc: comments@icann.org, cpart@interaccess.com, edyson@edventure.com,
        gregcrew@iaa.com.au, icann@icann.org, ietf@ietf.org, abd@cdt.org,
        baf@fausett.com, bburr@ntia.doc.gov, bdooley@cix.org,
        carl@oppedahl.com, Charles.Pickering@mail.house.gov,
        cpsr-activsts@cpsr.org, cpsr-cyber-rights@cpsr.org,
        dnso.discuss@lists.association.org, dnspolicy@ntia.doc.gov,
        domain-policy@internic.net, eric.menge@sba.gov, falco@vex.net,
        froomkin@law.miami.edu, gconrades@icann.org, glenn@technologylaw.com,
        harryh-dns@quark.cpsr.org, info@name-space.com,
        InfoCker@worldnet.att.net, ivan@netnames.com, JacobsonSJ@aol.com,
        jeri@nytimes.com, KathrynKL@aol.com, kent@songbird.com,
        krose@ntia.doc.gov, list@ifwp.org, lleblanc@leblanc.com,
        love@cptech.org, Mark.Harrington@mail.house.gov, mgordon@pipeline.com,
        michael@memra.com, mleblanc@leblanc.com, process@dnso.org,
        rep.e.b.johnson@mail.house.gov, Rep.Morella@mail.house.gov,
        rlongstaff@leblanc.com, roberts@icann.org, russ@russ-smith.com,
        sdoty@jaxx.net, tchatham@leblanc.com, tkoors@famousbrand.com
Subject: Re: Complaint to Dept of Commerce on abuse of users by ICANN
References: <200007301638.MAA03991@panix2.panix.com>
Message-Id: <E13IwMd-0000WQ-00@roam.psg.com>
Date: Sun, 30 Jul 2000 12:54:59 -0400
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> I sent the following to Becky Burr a few minutes ago as a formal 
> complaint about the ICANN abuse of users 

some of us want to do work and not play in the snake pit.  please remove me,
ietf, ... from your list of teh diseas-laden.  thanks.

randy



From owner-ietf-outbound  Sun Jul 30 23:40:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA01372
	for ietf-outbound.10@ietf.org; Sun, 30 Jul 2000 23:40:04 -0400 (EDT)
Received: from watervalley.net (mail.WaterValley.Net [216.220.140.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA26972
	for <ietf@ietf.org>; Sun, 30 Jul 2000 23:29:32 -0400 (EDT)
Received: from [198.110.21.84] (HELO greendragon.com) by watervalley.net (Stalker SMTP Server 1.8b8) with ESMTP id S.0008206044; Sun, 30 Jul 2000 22:29:29 -0500
Message-ID: <3984F245.1AB9E50B@greendragon.com>
Date: Sun, 30 Jul 2000 23:28:25 -0400
From: William Allen Simpson <wsimpson@greendragon.com>
Organization: DayDreamer
X-Mailer: Mozilla 4.73 (Macintosh; U; PPC)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
CC: ronda@panix.com, comments@icann.org, cpart@INTERACCESS.COM,
        gregcrew@iaa.com.au, baf@fausett.com, carl@oppedahl.com,
        cpsr-activsts@cpsr.org, cpsr-cyber-rights@cpsr.org,
        dnso.discuss@lists.association.org, domain-policy@INTERNIC.NET,
        falco@vex.net, froomkin@law.miami.edu, glenn@technologylaw.com,
        info@name-space.com, InfoCker@worldnet.att.net, ivan@netnames.com,
        JacobsonSJ@aol.com, jeri@nytimes.com, KathrynKL@aol.com, list@ifwp.org,
        lleblanc@leblanc.com, love@cptech.org, mgordon@pipeline.com,
        michael@memra.com, mleblanc@leblanc.com, process@dnso.org,
        rlongstaff@leblanc.com, russ@russ-smith.com, sdoty@jaxx.net,
        tchatham@leblanc.com, tkoors@famousbrand.com
Subject: Re: Complaint to Dept of Commerce on abuse of users by ICANN
References: <000901bffa4f$2f7f8570$b5e20a18@alex1.va.home.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I have no idea why so many different lists have been spammed.  (Spam is 
a technical term for massive cross-posting.  Spam is bad.)

The US congresscritters listed won't even see the message, as their 
mail server searches (or some poor aide searches by hand) for the 
correct legislative office matching the users' home address.  In 
Ronda's case, it appears to be New York, but s/he didn't bother to 
research the correct recipient legislator.  (I've removed or BCC'd the 
legislators, and other obvious duplications and errors.  Again, I've no 
idea about many of the remainder.)

In short, Ronda and Russ are spammers with no clue.


ronda@panix.com wrote:
> 
>...  The version to sign
> up at the ICANN web site requires frames. So people who don't have
> a browser with frames are not able to even use that part of the
> web site. And an alternative web site set up in another country
> gives a message of "We are sorry. The database is currently overloaded.
> Please try again when the system is less busy." when I tried to sign
> up.
> 
> Clearly the whole ICANN model is not appropriate for the needs
> of the Internet and its users.
> 
> I did propose a different model, and a prototype to build this
> model to you before ICANN was given the U.S. Dept of Commerce
> contract.
> 
Ronda has been active in ICANN for several years.  Yet s/he did not 
bother to sign up for membership until the last possible moment?

The users of the Internet have access to several free browsers that 
support frames on a dozen platforms.  Folks that are unable to use 
the Internet are not an appropriate electorate.  Lazy kindergartners 
are not the target audience for ICANN membership.


"vinton g. cerf" wrote:
> have you taken time to look into the numbers of people trying to
> register? do you know what the planning estimates were before
> registration campaigns were initiated by various organizations?
> The planning numbers for registration were on the order of 10,000
> people. As of a few days ago something like 145,000 people had
> sent in raw registrations. Keep in mind also that there is a
> PIN number that has to be sent by mail. There is a calendar
> schedule that ICANN is trying to keep for the election itself,
> so the PINs have to get to the voters in time for that.
> 
> Every possible effort was made to increase the rate at which
> registrations could be processed and we've gone from about 1000
> a day to an artificially limited 5,000 per day (200 per hour)
> simply because staff time to process is limited. Registrations
> close July 31.
> 
I signed up shortly after the announcement.  I was surprised at the 
length of time it took for my PIN to arrive in the mail.  But, I did 
receive an announcement in April to the prospective members 
explaining the delay.

Never-the-less, there is no fee for processing the membership.  
"Thanks to a grant from the Markle Foundation, the initial launch of 
ICANN's At Large Membership program has been funded without the need 
for membership dues."

Those that desire faster service might offer to pay for expediting.  
There's no such thing as a free lunch.  


Russ Smith wrote:
> This excuse follows the same "excuse pattern" that ICANN provides for almost
> every problem.  What keeps happening is that these groups that do the
> "planning" do so in secret and routinely ignore comments and often do not
> know what they are doing.  

The planning was done in the open, and those that bothered to join the 
official announcement list anytime in the past several years has been 
aware of the process.  


> The same thing happened with the UDRP.  When that was written many people
> complained about no appeals process (short of filing a lawsuit).  

This poster appears to be ignorant of traditions of administrative law in 
the US and elsewhere.  Judicial review _is_ an appeals process!  That's 
why a "lawsuit" is filed.

> There are
> also extremely short deadlines for responding to a complaint or filing the
> "appeal" lawsuit (10 days).  The excuse that was given was that these
> appeals were only a delaying tactic by "cybersquatters".  

On one hand, there is a complaint that response time is too slow.  On the 
other hand, that response time is too fast.  Make up your mind!

Although multiples of 10 days is a traditional time measure, in many 
jurisdictions times have been changed to reflect a 7 day week.  The 
Internet allows faster responses.  Why not reduce the time to 7 days?

Oh, I see, everybody else should be fast, but you should be allowed to 
be slower.  How thoughtful and consistent.

>... McLaughlin recommended lawyers publish the UDRP
> problems in legal journals so ICANN can review these some time in the
> future.  

That's what one might expect for a legal process with peer review.

>...
> "The ICANN tables do not include notations relating to subsequent
> litigation, because the ICANN staff is simply too small and too
> overstretched to monitor and verify the hundreds of legal disputes that will
> surely ensue."
> 
Should a fee be added for litigants to pay ICANN to register their case?
Again, there's no such thing as a free lunch.



From owner-ietf-outbound  Mon Jul 31 06:30:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA05587
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 06:30:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03500
	for <ietf@ietf.org>; Mon, 31 Jul 2000 06:20:09 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 13JCfz-0000fO-00; Mon, 31 Jul 2000 11:20:03 +0100
Date: Mon, 31 Jul 2000 11:20:00 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: William Allen Simpson <wsimpson@greendragon.com>
cc: ietf@ietf.org
Subject: Re: Complaint to Dept of Commerce on abuse of users by ICANN
In-Reply-To: <3984F245.1AB9E50B@greendragon.com>
Message-ID: <Pine.GSO.4.21.0007311114070.24684-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Sun, 30 Jul 2000, William Allen Simpson wrote:

> ronda@panix.com wrote:
> > 
> >...  The version to sign
> > up at the ICANN web site requires frames. So people who don't have
> > a browser with frames are not able to even use that part of the
> > web site. And an alternative web site set up in another country
> > gives a message of "We are sorry. The database is currently overloaded.
> > Please try again when the system is less busy." when I tried to sign
> > up.
> > 
> > Clearly the whole ICANN model is not appropriate for the needs
> > of the Internet and its users.
> > 
> > I did propose a different model, and a prototype to build this
> > model to you before ICANN was given the U.S. Dept of Commerce
> > contract.
> > 
> Ronda has been active in ICANN for several years.  Yet s/he did not 
> bother to sign up for membership until the last possible moment?
> 
> The users of the Internet have access to several free browsers that 
> support frames on a dozen platforms.  Folks that are unable to use 
> the Internet are not an appropriate electorate.  Lazy kindergartners 
> are not the target audience for ICANN membership.

I do hope this isn't the official ICANN view. I imagine that 
a disability discrimination lawsuit would soon follow.

L.

how many text-to-speech audio browsers support frames well?

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




From owner-ietf-outbound  Mon Jul 31 10:20:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA11941
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 10:20:02 -0400 (EDT)
Received: from fledge.watson.org (root@fledge.watson.org [204.156.12.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10802
	for <ietf@ietf.org>; Mon, 31 Jul 2000 10:09:34 -0400 (EDT)
Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3])
	by fledge.watson.org (8.9.3/8.9.3) with SMTP id KAA59988;
	Mon, 31 Jul 2000 10:07:43 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Date: Mon, 31 Jul 2000 10:07:42 -0400 (EDT)
From: Robert Watson <rwatson@FreeBSD.org>
X-Sender: robert@fledge.watson.org
To: Chris BeHanna <behanna@zbzoom.net>,
        Francis Dupont <Francis.Dupont@enst-bretagne.fr>, itojun@iijlab.net,
        Kenjiro Cho <kjc@csl.sony.co.jp>, lewis@tislabs.com,
        Lyndon Nerenberg <lyndon@orthanc.ab.ca>,
        Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>, ogud@tislabs.com,
        "Person, Roderick" <personrp@ccbh.com>,
        Ping Pan <pingpan@dnrc.bell-labs.com>, Randy Bush <randy@psg.com>,
        Stephen Casner <casner@packetdesign.com>
cc: ietf@ietf.org
Subject: IETF/FreeBSD dinner tonight
Message-ID: <Pine.NEB.3.96L.1000731094351.59719A-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


I've included even those who said they might not be able to make it, in
case they change their minds :-).

The current plan is to do dinner during the Monday night break, between
5:30pm and 7:30pm.  We'll meet in the terminal room (South Hall), by the
"Do not use this door as an exit" sign.  In case the sign is missing,
that's on the wall towards the center of the building (presumably North?),
third from the left when facing that wall.

We plan to be back by the evening session.

  Robert N M Watson 

robert@fledge.watson.org              http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A 79 37  ED 5F 55 E9 58 04 6A B1
TIS Labs at Network Associates, Safeport Network Services



From owner-ietf-outbound  Mon Jul 31 11:10:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA17813
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 11:10:02 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16935
	for <ietf@ietf.org>; Mon, 31 Jul 2000 11:02:10 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id IAA07268;
	Mon, 31 Jul 2000 08:02:11 -0700 (PDT)
Date: Mon, 31 Jul 2000 08:02:11 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200007311502.IAA07268@shell5.ba.best.com>
To: ietf@ietf.org
cc: list@ifwp.org
Subject: Re: Complaint to Dept of Commerce on abuse of users by ICANN
Mime-Version: 1.0
X-Loop: ietf@ietf.org

Lloyd Wood <l.wood@eim.surrey.ac.uk> wrote:

> William Allen Simpson wrote:

>> The users of the Internet have access to several free browsers that
>> support frames on a dozen platforms.  Folks that are unable to use
>> the Internet are not an appropriate electorate.  Lazy kindergartners
>> are not the target audience for ICANN membership.

> I do hope this isn't the official ICANN view. I imagine that
> a disability discrimination lawsuit would soon follow.

> how many text-to-speech audio browsers support frames well?

Support for the disabled does seem to be a concern in some quarters;
for example, see

http://dir.yahoo.com/Computers_and_Internet/Software/Internet/World_Wide_Web/Browsers/Lynx/

The secure registration page requires https, which isn't available in lynx
as far as I know.

I am wondering if it might make sense going forward to allow an email
submission.  Email is for the most part a queued delivery mechanism, so it
is not necessary for the user to resubmit an html form if the server is
busy.

--gregbo



From owner-ietf-outbound  Mon Jul 31 11:40:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA25354
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 11:40:02 -0400 (EDT)
Received: from wodc7-2.corprelay.mail.uu.net (wodc7-2.corprelay.mail.uu.net [192.48.96.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23553
	for <ietf@ietf.org>; Mon, 31 Jul 2000 11:34:17 -0400 (EDT)
Received: from webserve0.corp.us.uu.net by wodc7mr2.ffx.ops.us.uu.net with ESMTP 
	(peer crosschecked as: webserve0.corp.us.uu.net [153.39.203.155])
	id QQjafu09261;
	Mon, 31 Jul 2000 15:34:15 GMT
Received: from localhost by webserve0.corp.us.uu.net with ESMTP 
	(peer crosschecked as: rmueller@localhost)
	id QQjafu01705;
	Mon, 31 Jul 2000 11:34:15 -0400 (EDT)
Date: Mon, 31 Jul 2000 11:34:15 -0400 (EDT)
From: ross <rmueller@UU.NET>
X-Sender: rmueller@webserve0.corp.us.uu.net
To: Greg Skinner <gds@best.com>
cc: ietf@ietf.org, list@ifwp.org
Subject: Re: Complaint to Dept of Commerce on abuse of users by ICANN
In-Reply-To: <200007311502.IAA07268@shell5.ba.best.com>
Message-ID: <Pine.GSO.4.20.0007311133110.22754-100000@webserve0.corp.us.uu.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

lynxssl is available....

Lynx Version 2.7.1ac-0.50-SSL0.8.1-RSAREF2.0 (1997)
Copyrights held by the University of Kansas, CERN, and other contributors.
Distributed under the GNU General Public License.
See http://lynx.browser.org/ and the online help for more information.

..ross
0x75,0x75,0x6e,0x65,0x74

On Mon, 31 Jul 2000, Greg Skinner wrote:

> Lloyd Wood <l.wood@eim.surrey.ac.uk> wrote:
> 
> > William Allen Simpson wrote:
> 
> >> The users of the Internet have access to several free browsers that
> >> support frames on a dozen platforms.  Folks that are unable to use
> >> the Internet are not an appropriate electorate.  Lazy kindergartners
> >> are not the target audience for ICANN membership.
> 
> > I do hope this isn't the official ICANN view. I imagine that
> > a disability discrimination lawsuit would soon follow.
> 
> > how many text-to-speech audio browsers support frames well?
> 
> Support for the disabled does seem to be a concern in some quarters;
> for example, see
> 
> http://dir.yahoo.com/Computers_and_Internet/Software/Internet/World_Wide_Web/Browsers/Lynx/
> 
> The secure registration page requires https, which isn't available in lynx
> as far as I know.
> 
> I am wondering if it might make sense going forward to allow an email
> submission.  Email is for the most part a queued delivery mechanism, so it
> is not necessary for the user to resubmit an html form if the server is
> busy.
> 
> --gregbo
> 




From owner-ietf-outbound  Mon Jul 31 11:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA28055
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 11:50:02 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET ([166.60.6.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24578
	for <ietf@ietf.org>; Mon, 31 Jul 2000 11:38:00 -0400 (EDT)
Received: from cerf.mci.net ([166.60.14.225])
 by shoe.reston.mci.net (PMDF V5.2-32 #40475)
 with ESMTPA id <01JSEZ1MLQH49N45AD@shoe.reston.mci.net> for ietf@ietf.org;
 Mon, 31 Jul 2000 11:38:01 EST
Date: Mon, 31 Jul 2000 11:35:36 -0400
From: "vinton g. cerf" <vcerf@MCI.NET>
Subject: Re: Complaint to Dept of Commerce on abuse of users by ICANN
In-reply-to: <200007311502.IAA07268@shell5.ba.best.com>
X-Sender: vcerf@shoe.reston.mci.net
To: Greg Skinner <gds@best.com>, ietf@ietf.org
Cc: list@ifwp.org
Message-id: <4.3.1.2.20000731113431.023ac500@shoe.reston.mci.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7BIT

Greg,

I am a strong proponent of developing and implementing accessibility
guidelines. The ICANN election has simply overwhelmed the available
resources - but I think the follow-on study absolutely should take into
account accessibility concerns.

vint

At 08:02 AM 7/31/2000 -0700, Greg Skinner wrote:
>Lloyd Wood <l.wood@eim.surrey.ac.uk> wrote:
>
> > William Allen Simpson wrote:
>
> >> The users of the Internet have access to several free browsers that
> >> support frames on a dozen platforms.  Folks that are unable to use
> >> the Internet are not an appropriate electorate.  Lazy kindergartners
> >> are not the target audience for ICANN membership.
>
> > I do hope this isn't the official ICANN view. I imagine that
> > a disability discrimination lawsuit would soon follow.
>
> > how many text-to-speech audio browsers support frames well?
>
>Support for the disabled does seem to be a concern in some quarters;
>for example, see
>
>http://dir.yahoo.com/Computers_and_Internet/Software/Internet/World_Wide_Web/Browsers/Lynx/
>
>The secure registration page requires https, which isn't available in lynx
>as far as I know.
>
>I am wondering if it might make sense going forward to allow an email
>submission.  Email is for the most part a queued delivery mechanism, so it
>is not necessary for the user to resubmit an html form if the server is
>busy.
>
>--gregbo

=================================================================
I moved to a new MCI WorldCom facility on Nov 11, 1999

MCI WorldCom
22001 Loudoun County Parkway
Building F2, Room 4115, ATTN: Vint Cerf
Ashburn, VA 20147
Telephone (703) 886-1690
FAX (703) 886-0047


"INTERNET IS FOR EVERYONE!" 
INET 2001: Internet Global Summit 
5-8 June 2001 
Sweden International Fairs 
Stockholm, Sweden 
http://www.isoc.org/inet2001





From owner-ietf-outbound  Mon Jul 31 12:10:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA02320
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 12:10:03 -0400 (EDT)
Received: from mail.yourfit.com (root@28.wxfr1.xdsl.nauticom.net [209.195.150.61])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02107
	for <ietf@ietf.org>; Mon, 31 Jul 2000 12:08:47 -0400 (EDT)
Received: from armani.yourfit.com (armani.yourfit.com [192.168.1.120])
	by mail.yourfit.com (8.9.3/8.9.3) with ESMTP id MAA29683;
	Mon, 31 Jul 2000 12:06:29 -0400
Date: Mon, 31 Jul 2000 12:06:29 -0400 (Eastern Daylight Time)
From: Chris BeHanna <behanna@zbzoom.net>
Reply-To: Chris BeHanna <behanna@zbzoom.net>
To: Robert Watson <rwatson@FreeBSD.org>
cc: Francis Dupont <Francis.Dupont@enst-bretagne.fr>, itojun@iijlab.net,
        Kenjiro Cho <kjc@csl.sony.co.jp>, lewis@tislabs.com,
        Lyndon Nerenberg <lyndon@orthanc.ab.ca>,
        Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>, ogud@tislabs.com,
        "Person, Roderick" <personrp@ccbh.com>,
        Ping Pan <pingpan@dnrc.bell-labs.com>, Randy Bush <randy@psg.com>,
        Stephen Casner <casner@packetdesign.com>, ietf@ietf.org
Subject: Re: IETF/FreeBSD dinner tonight
In-Reply-To: <Pine.NEB.3.96L.1000731094351.59719A-100000@fledge.watson.org>
Message-ID: <Pine.WNT.4.21.0007311204380.289-100000@armani.yourfit.com>
Sender: behanna@mail.zbzoom.net
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Mon, 31 Jul 2000, Robert Watson wrote:

> 
> I've included even those who said they might not be able to make it, in
> case they change their minds :-).
> 
> The current plan is to do dinner during the Monday night break, between
> 5:30pm and 7:30pm.  We'll meet in the terminal room (South Hall), by the
> "Do not use this door as an exit" sign.  In case the sign is missing,
> that's on the wall towards the center of the building (presumably North?),
> third from the left when facing that wall.
> 
> We plan to be back by the evening session.

    I am not attending IETF, but would drive down to meet you.  As
such, I'll probably not be allowed in as far as the terminal room.
Will there be a secondary staging area (e.g., main lobby, internal
restaurant, etc.?).

    I can bring a piece of paper and scrawl "FreeBSD Dinner" so you
can find me. :-)

-- 
Chris BeHanna
Software Engineer (at yourfit.com)
behanna@zbzoom.net



From owner-ietf-outbound  Mon Jul 31 13:21:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA12522
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 13:20:02 -0400 (EDT)
Received: from songbird.com (IDENT:kent@songbird.com [206.14.4.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11415
	for <ietf@ietf.org>; Mon, 31 Jul 2000 13:10:33 -0400 (EDT)
Received: (from kent@localhost)
	by songbird.com (8.9.1a/8.9.1) id KAA18646;
	Mon, 31 Jul 2000 10:10:16 -0700
Message-ID: <20000731101016.D13808@songbird.com>
Date: Mon, 31 Jul 2000 10:10:16 -0700
From: Kent Crispin <kent@songbird.com>
To: ietf@ietf.org, list@ifwp.org
Subject: Re: [IFWP] Re: Complaint to Dept of Commerce on abuse of users by ICANN
Mail-Followup-To: ietf@ietf.org, list@ifwp.org
References: <200007311502.IAA07268@shell5.ba.best.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <200007311502.IAA07268@shell5.ba.best.com>; from Greg Skinner on Mon, Jul 31, 2000 at 08:02:11AM -0700
X-Loop: ietf@ietf.org

On Mon, Jul 31, 2000 at 08:02:11AM -0700, Greg Skinner wrote:
> Lloyd Wood <l.wood@eim.surrey.ac.uk> wrote:
> 
> > William Allen Simpson wrote:
> 
> >> The users of the Internet have access to several free browsers that
> >> support frames on a dozen platforms.  Folks that are unable to use
> >> the Internet are not an appropriate electorate.  Lazy kindergartners
> >> are not the target audience for ICANN membership.
> 
> > I do hope this isn't the official ICANN view. I imagine that
> > a disability discrimination lawsuit would soon follow.
> 
> > how many text-to-speech audio browsers support frames well?
> 
> Support for the disabled does seem to be a concern in some quarters;
> for example, see
> 
> http://dir.yahoo.com/Computers_and_Internet/Software/Internet/World_Wide_Web/Browsers/Lynx/
> 
> The secure registration page requires https, which isn't available in lynx
> as far as I know.

1) The web page does NOT use frames -- as far as I know, there are no frames 
in the entire ICANN site; 

2) the secure registration page is OPTIONAL; you can register through a
nonsecure path. 

-- 
Kent Crispin                               "Do good, and you'll be
kent@songbird.com                           lonesome." -- Mark Twain



From owner-ietf-outbound  Mon Jul 31 13:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA14154
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 13:30:02 -0400 (EDT)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11825
	for <ietf@ietf.org>; Mon, 31 Jul 2000 13:14:05 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id CB9184CE59; Mon, 31 Jul 2000 13:14:01 -0400 (EDT)
Received: from smb.research.att.com (secure.research.att.com [135.207.25.14])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id NAA04390;
	Mon, 31 Jul 2000 13:14:00 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 335F835DC2; Mon, 31 Jul 2000 13:13:53 -0400 (EDT)
X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.3 #1[UCI]
From: "Steven M. Bellovin" <smb@research.att.com>
To: "vinton g. cerf" <vcerf@mci.net>
Cc: Greg Skinner <gds@best.com>, ietf@ietf.org, list@ifwp.org
Subject: Re: Complaint to Dept of Commerce on abuse of users by ICANN 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 31 Jul 2000 13:13:48 -0400
Sender: smb@research.att.com
Message-Id: <20000731171353.335F835DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

It's also worth noting that virtually every other major Internet 
service has been swamped by unexpected load.  Predicting load, and 
engineering for it without prior experience in that particular kind (and
popularity) of service is just plain hard.

		--Steve Bellovin




From owner-ietf-outbound  Mon Jul 31 14:30:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA21377
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 14:30:02 -0400 (EDT)
Received: from trampoline.thunk.org (IDENT:root@wireless-134-7.ietf.marconi.com [147.73.134.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21324
	for <ietf@ietf.org>; Mon, 31 Jul 2000 14:29:48 -0400 (EDT)
Received: (from tytso@localhost)
	by trampoline.thunk.org (8.9.3/8.9.3) id OAA02094;
	Mon, 31 Jul 2000 14:29:57 -0400
Date: Mon, 31 Jul 2000 14:29:57 -0400
Message-Id: <200007311829.OAA02094@trampoline.thunk.org>
To: ietf@ietf.org
Subject: IETF PGP Key Signing Party
From: tytso@mit.edu
Phone: (781) 391-3464
X-Loop: ietf@ietf.org


Once again, we will be holding a PGP Key signing party at the IETF
meeting in Pittsburgh.  We have been scheduled to meet at 10:30pm on the
evening of Wednesday, August 2, 2000 in the South Room (11/12). The
procedure we will use is the following:

o People who wish to participate should email an ASCII extract of their
  PGP public key to <tytso@mit.edu> by noon on Wednesday, August 2,
  2000. Please include a subject line of "IETF PGP KEY", and please
  avoid MIME-encrypting your e-mail.  (I will be running the emacs RMAIL
  file through PGP, and PGP-keys that are base-64 encoded will get
  ignored unless I take manual action to fix things, which I will try
  to do but make no guarantees about doing.)

  The method of generating the ASCII extract under Unix is:

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

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

o By 6pm on Wednesday, you will be able to fetch complete key ring
  from the following URL with all of the keys that were submitted:

 	http://web.mit.edu/tytso/www/ietf.pgp

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

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

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

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

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

					 - Ted



From owner-ietf-outbound  Mon Jul 31 17:10:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA16435
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 17:10:02 -0400 (EDT)
Received: from netmail.netscape.com (netmail.netscape.com [207.200.73.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15601
	for <ietf@ietf.org>; Mon, 31 Jul 2000 17:03:02 -0400 (EDT)
Received: from ureg20.netscape.com (ureg20 [207.200.82.220])
	by netmail.netscape.com (8.9.1/8.9.1) with ESMTP id OAA26627
	for <ietf@ietf.org>; Mon, 31 Jul 2000 14:02:39 -0700 (PDT)
Received: (from http@localhost)
	by ureg20.netscape.com (8.9.1/8.9.1) id OAA10159
	for ietf@ietf.org; Mon, 31 Jul 2000 14:01:14 -0700 (PDT)
Date: Mon, 31 Jul 2000 14:01:14 -0700 (PDT)
Message-Id: <200007312101.OAA10159@ureg20.netscape.com>
From: netcenter-reg@netscape.com (Netcenter Registration)
Reply-to: netcenter-reg@netscape.com
To: ietf@ietf.org
MIME-Version: 1.0
Subject: NETCENTER uid=ccnriNreston key=Wlno/V/Teien CONFIRM!
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

<html><pre> 

Dear cnri org, 

Welcome to Netcenter! In order to gain full access to
Netcenter member services, please CONFIRM that this is
your correct email address by replying to this message
within 48 hours. If you do not confirm within 48 hours,
your account will not be fully activated.

NOTE: If you DID NOT request this account, please see
the instructions at the bottom of this message.

You can confirm by:

1. Clicking Reply and Send to return this email to
   Netcenter
               
      OR

2. If you CAN SEE THE IMAGE BELOW, just click on
   the image to confirm your account.

<A HREF=
http://ureg.netscape.com/iiop/UReg2/mailback/confirm_email_form?uid=ccnriNreston&key=Wlno%2FV%2FTei&U2_CS=iso-8859-1&U2_LA=en>
<IMG SRC="http://ureg.netscape.com/ureg/generic/en/confirm_banner.gif"></A>


Thank You! 

Netcenter Registration 


If you DID NOT register for this account, please forward
this message, with a brief note, to Netscape Registration
Support at the email address: regsupport@netscape.com 
We will remove your email address from the account to
prevent further account related notices.

</html>







From owner-ietf-outbound  Mon Jul 31 17:50:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA20962
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 17:50:02 -0400 (EDT)
Received: from ywing.netscape.com (ywing.netscape.com [207.200.72.93])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20472
	for <ietf@ietf.org>; Mon, 31 Jul 2000 17:45:41 -0400 (EDT)
Received: from ureg30.netscape.com (ureg30.netscape.com [207.200.82.230])
	by ywing.netscape.com (8.10.0/8.10.0) with ESMTP id e6VLjgM04781
	for <ietf@ietf.org>; Mon, 31 Jul 2000 14:45:42 -0700 (PDT)
Received: (from http@localhost)
	by ureg30.netscape.com (8.9.3+Sun/8.9.1) id OAA16918
	for ietf@ietf.org; Mon, 31 Jul 2000 14:44:50 -0700 (PDT)
Date: Mon, 31 Jul 2000 14:44:50 -0700 (PDT)
Message-Id: <200007312144.OAA16918@ureg30.netscape.com>
From: netcenter-reg@netscape.com (Netcenter Registration)
Reply-to: netcenter-reg@netscape.com
To: ietf@ietf.org
MIME-Version: 1.0
Subject: Welcome to Netcenter
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

<HTML>
<HEAD>

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">

<TITLE>Welcome to Netscape Netcenter</TITLE>

</HEAD>

<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#000099" VLINK="#660099" ALINK="#CC0033">

<CENTER>
<TABLE BORDER=0 CELLSPACING=0 CELLPADDING=5 BGCOLOR="#99CCCC" >
<TR>
<TD>

<TABLE BORDER=0 CELLSPACING=0 CELLPADDING=20 BGCOLOR="#FFFFFF" >
<TR>
<TD>

<TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=550> 
<TR> 
<TD ROWSPAN=2 WIDTH=135 HEIGHT=35 VALIGN="TOP"> 
<!-- Netscape lockup image and link go in this cell -->
<!-- E1:START:NSCP_LOCKUP --><A HREF="http://home.netscape.com/index.html"><IMG SRC="http://home.netscape.com/images/nnc_lockup.gif" ALT="Netscape Netcenter" WIDTH=123 HEIGHT=33 BORDER=0></A><!-- E1:END:NSCP_LOCKUP --></TD>

<TD WIDTH=415 BGCOLOR="#99CCCC" HEIGHT=17  ALIGN="RIGHT" VALIGN="middle"><FONT FACE="Sans-Serif,Arial,Helvetica"><FONT SIZE=-1><A HREF="http://home.netscape.com/escapes/search/netsearch_0.html">Netsearch</A>&nbsp;

|&nbsp; <A HREF="http://webmail.netscape.com">Webmail</A>&nbsp;&nbsp; |&nbsp;&nbsp; <A HREF="http://my.netscape.com/">My Netscape</A>&nbsp;&nbsp;
|&nbsp;&nbsp; <A HREF="http://form.netscape.com/members/index.html">Member Directory</A>&nbsp;</FONT></FONT></TD></TR>
<!-- Blank cells for spacing: do not remove -->
<TR> <TD HEIGHT=20></TD> </TR>
</TABLE>

<TABLE BORDER=0 CELLSPACING=0 CELLPADDING=15 WIDTH="550" BGCOLOR="#FFFFFF" >
<TR>
<TD>
<SPACER type="vertical" size="5">
<FONT FACE="Arial,Helvetica,Sans-Serif">Dear cnri org,

<P>
Welcome to <B><A HREF="http://home.netscape.com/index.html">Netscape Netcenter</A></B>, where all your interests come together, just the way you like them. With your FREE enrollment in Netscape Netcenter, you're joining millions of others who've already discovered the place to get all the tools you need online.   

<P><FONT COLOR="#408080"><B>IMPORTANT MEMBERSHIP INFORMATION</B></FONT>
<BR>Each time you visit us at Netscape Netcenter, you may need to enter your user name and password. Please keep a copy of this information in a safe place for future reference. You now can access Netscape Netcenter from anywhere you have an Internet connection.

<UL>Your User Name is: ccnriNreston</UL>
<P>
To edit your personal profile or registration information, <A HREF="http://home.netscape.com/netcenter/membercenter.html">click here</A>.

<P>
<FONT COLOR="#408080"><B>YOUR FREE EMAIL ACCOUNT</FONT></B>
<BR>As a bonus, we have automatically reserved for you your own private Netscape WebMail account:
<UL>ccnriNreston@netscape.net</UL>
Netscape WebMail accounts, provided free to all Netcenter members, are accessible from any computer with Internet access. <A HREF="http://webmail.netscape.com">Click here</A> to activate your WebMail account.

<P>
<B><FONT COLOR="#408080">YOUR FREE INSTANT MESSENGER ACCOUNT</FONT></B><BR>
Another bonus is that you now have a FREE Netscape AOL Instant Messenger account. Your Netcenter user name, listed above, is also your screen name that you will enter when signing on to Netscape AOL Instant Messenger. Now you can exchange instant and private messages, chat one-on-one or in a group, and know instantly when a friend, colleague, or family member is online.

<P>
As a new member of the fastest growing Internet online community in the world, we encourage you to connect online today by simply <A HREF="http://aim.aol.com/aim/imreg_download_template?pageset=netscape//&promo=73026">clicking here</A>.

<P><B><FONT COLOR="#408080">THE WAY YOU WANT IT</FONT></B><BR>With your Netscape Netcenter membership, you'll be able to:
<UL TYPE=DISC>
	<LI>Download the world's most popular browser, Netscape Communicator using <A HREF="http://home.netscape.com/download/su1.html">SmartUpdate</A> to keep your software current
	<LI>Access 'Teach Yourself Netscape Netcenter in 10 Minutes' free <A HREF="http://home.netscape.com/support/books/netcenter/index.html?cp=h">online book</A> 
	<LI>Manage your stock portfolio, check weather and read your daily horoscope with your personalized <A HREF="http://my.netscape.com/">My Netscape</A> service
	<LI>Chat with your friends in real time with <A HREF="http://www.newaol.com/aim/netscape/adb00.html">AOL Instant Messenger</A>
	<LI>Take advantage of a broad variety of business and consumer channels like news, entertainment and sports
</UL>

With free Instant Messaging, email, a personalized home page, automatic updates, personal finance services, and online shopping, Netcenter is one place on the Internet where all our interests come together.

<P>
Sincerely,<P>

Netscape Netcenter Team<BR>
<a href="http://home.netscape.com">http://home.netscape.com</a>
<BR>
<HR NOSHADE><FONT SIZE=-1>Netscape respects your online time and Internet privacy. This welcome letter is a one-time only mailing. To edit your personal information or privacy options, including whether you want to receive other Netscape mailings, please go to the <A HREF="http://home.netscape.com/netcenter/membercenter.html">Netscape Member Center</A>.</FONT>

<P><CENTER><FONT SIZE=-2>Copyright &copy; 1999. <A HREF="http://home.netscape.com">Netscape Communications Corporation</A>. All rights reserved.</FONT></CENTER>
</TD>
</TR>
</TABLE>
</TD>
</TR>
</TABLE>

</TD>
</TR>
</TABLE>
</CENTER>

</BODY>
</HTML>



From owner-ietf-outbound  Mon Jul 31 19:10:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA04773
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 19:10:01 -0400 (EDT)
Received: from perfekt.perfekt.net (perfekt.net [205.230.176.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04677
	for <ietf@ietf.org>; Mon, 31 Jul 2000 19:09:19 -0400 (EDT)
Received: from iciiu.org (slip-ppp-1-183.perfekt.net [205.230.176.183])
	by perfekt.perfekt.net (8.9.3+Sun/8.9.3) with ESMTP id TAA21166;
	Mon, 31 Jul 2000 19:10:27 -0400 (EDT)
Message-ID: <398605AB.2AF909B7@iciiu.org>
Date: Mon, 31 Jul 2000 19:03:07 -0400
From: Michael Sondow <msondow@iciiu.org>
X-Mailer: Mozilla 4.03 [fr] (Win95; I)
MIME-Version: 1.0
To: list@ifwp.org
CC: Greg Skinner <gds@best.com>, ietf@ietf.org
Subject: Re: [IFWP] Re: Complaint to Dept of Commerce on abuse of users by ICANN
References: <4.3.1.2.20000731113431.023ac500@shoe.reston.mci.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

vinton g. cerf wrote:

> I think the follow-on study absolutely should take into
> account accessibility concerns.

More Cerf newspeak (like "Internet for everyone"). Accessibility
concerns = 90% of those wishing to join the At-large membership
turned away because ICANN wouldn't spend a little money upgrading
the sign-up website.

Why wouldn't they? Simply because the At-large membership means
nothing anyway, now that they have been deprived of any power by the
new bylaws depriving them of a vote on anything but the minority (5
out of eighteen) At-large directors, who will anyway be nominated by
the ICANN Nominating Committee. (Nothing has been left to chance.)


============================================================
Michael Sondow           I.C.I.I.U.     http://www.iciiu.org
Tel. (718)846-7482                        Fax: (603)754-8927
============================================================



From owner-ietf-outbound  Mon Jul 31 19:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA07043
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 19:30:03 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05339
	for <ietf@ietf.org>; Mon, 31 Jul 2000 19:15:03 -0400 (EDT)
Received: (from hta@localhost)
	by dokka.maxware.no (8.9.3/8.9.3) id BAA32512
	for ietf@ietf.org; Tue, 1 Aug 2000 01:15:02 +0200
Date: Tue, 1 Aug 2000 01:15:02 +0200
From: Harald Tveit Alvestrand <hta@dokka.maxware.no>
Message-Id: <200007312315.BAA32512@dokka.maxware.no>
To: ietf@ietf.org
Subject: FAQ: The IETF+Censored list
X-Loop: ietf@ietf.org


                        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).
   
   To unsubscribe, [2]send the word "unsubscribe" in the BODY of a
   message to ietf+censored-request@alvestrand.no. Do not send to the
   list - your message will be filtered!
   (members of the main IETF list itself must follow instructions for
   that list, of course. You are only a member of ietf+censored if there
   is a comment on the bottom of your IETF list mail saying that the
   message has been sent through the ietf+censored list.)
   
   For fun, there is a special list for the rejected messages:
   ietf+censored-rejects@alvestrand.no - subscribe in the same fashion,
   by [3]mail to ietf+censored-rejects-request@alvestrand.no
   
   By public request, the current set of filters are listed at
   [4]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
   [5]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 [6]< Harald@Alvestrand.no>

References

   1. mailto:ietf+censored-request@alvestrand.no?body=subscribe
   2. mailto:ietf+censored-request@alvestrand.no?body=unsubscribe
   3. mailto:ietf+censored-rejects-request@alvestrand.no?body=subscribe
   4. http://www.alvestrand.no/cgi-bin/hta/ietf+censored-filters
   5. http://www.alvestrand.no/posting-counts.html
   6. mailto:harald@alvestrand.no



From owner-ietf-outbound  Mon Jul 31 21:30:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA24021
	for ietf-outbound.10@ietf.org; Mon, 31 Jul 2000 21:30:03 -0400 (EDT)
Received: from perfekt.perfekt.net (perfekt.net [205.230.176.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21838
	for <ietf@ietf.org>; Mon, 31 Jul 2000 21:11:16 -0400 (EDT)
Received: from iciiu.org (slip-ppp-1-209.perfekt.net [205.230.176.209])
	by perfekt.perfekt.net (8.9.3+Sun/8.9.3) with ESMTP id VAA25278;
	Mon, 31 Jul 2000 21:11:51 -0400 (EDT)
Message-ID: <39862221.18230398@iciiu.org>
Date: Mon, 31 Jul 2000 21:04:33 -0400
From: Michael Sondow <msondow@iciiu.org>
X-Mailer: Mozilla 4.03 [fr] (Win95; I)
MIME-Version: 1.0
To: "DNSO.association.org" <dnso.discuss@lists.association.org>
CC: comments@icann.org, cpart@interaccess.com, edyson@edventure.com,
        gregcrew@iaa.com.au, icann@icann.org, ietf@ietf.org, abd@cdt.org,
        baf@fausett.com, bburr@ntia.doc.gov, bdooley@cix.org,
        carl@oppedahl.com, Charles.Pickering@mail.house.gov,
        cpsr-activsts@cpsr.org, cpsr-cyber-rights@cpsr.org,
        dnspolicy@ntia.doc.gov, domain-policy@internic.net, eric.menge@sba.gov,
        falco@vex.net, froomkin@law.miami.edu, gconrades@icann.org,
        glenn@technologylaw.com, harryh-dns@quark.cpsr.org,
        info@name-space.com, InfoCker@worldnet.att.net, ivan@netnames.com,
        JacobsonSJ@aol.com, jeri@nytimes.com, KathrynKL@aol.com,
        kent@songbird.com, krose@ntia.doc.gov, list@ifwp.org,
        lleblanc@leblanc.com, love@cptech.org, Mark.Harrington@mail.house.gov,
        mgordon@pipeline.com, michael@memra.com, mleblanc@leblanc.com,
        process@dnso.org, rep.e.b.johnson@mail.house.gov,
        Rep.Morella@mail.house.gov, rlongstaff@leblanc.com, roberts@icann.org,
        russ@russ-smith.com, sdoty@jaxx.net, tchatham@leblanc.com,
        tkoors@famousbrand.com
Subject: Re: [dnso.discuss] Re: Complaint to Dept of Commerce on abuse of users by ICANN
References: <200007301638.MAA03991@panix2.panix.com> <LYR42195-26074-2000.07.30-23.34.27--msondow#iciiu.org@lists.association.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Randy Bush wrote:
> 
> some of us want to do work

Do you work, Mr. Bush? This is the first I've heard of it. I thought
you made your living by acting as a shill for Vint Cerf. 

> and not play in the snake pit.

Such respect for the users of the Internet! Finally someone from the
ICANN inner circle has spoken honestly.

> please remove me,
> ietf

Are you now the IETF, Mr. Bush? Or have you gone mad from
megalomania?

> from your list of the disease-laden.

Do the members of the dnso.discuss list have a disease? A
psychological disease, perhaps. Like icannophobia.

============================================================
Michael Sondow           I.C.I.I.U.     http://www.iciiu.org
Tel. (718)846-7482                        Fax: (603)754-8927
============================================================



