From owner-ietf-outbound  Wed Nov  1 19:32:03 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA14662
	for ietf-outbound.10@ietf.org; Wed, 1 Nov 2000 19:30:03 -0500 (EST)
Received: from linux368.dn.net (systemserver.com [207.153.200.204] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA09064
	for <IETF@ietf.org>; Wed, 1 Nov 2000 19:04:51 -0500 (EST)
Received: (from nobody@localhost)
	by linux368.dn.net (8.9.3/8.9.1) id UAA31660
	for IETF@ietf.org; Wed, 1 Nov 2000 20:20:09 -0500
Date: Wed, 1 Nov 2000 20:20:09 -0500
Message-Id: <200011020120.UAA31660@linux368.dn.net>
To: IETF@ietf.org
From: reports@betterwhois.com (BetterWhois.com)
Subject: BetterWhois Search: pogo.com
X-Loop: ietf@ietf.org

[whois.crsnic.net]Whois Server Version 1.3Domain names in the .com, .net, and .org domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.   Domain Name: POGO.COM
   Registrar: NETWORK SOLUTIONS, INC.
   Whois Server: whois.networksolutions.com
   Referral URL: www.networksolutions.com
   Name Server: DNS03.POGO.COM
   Name Server: DNS02.POGO.COM
   Updated Date: 16-aug-2000
The Registry database contains ONLY .COM, .NET, .ORG, .EDU domains and
Registrars.

[whois.networksolutions.com]
The Data in Network Solutions' WHOIS database is provided by Network
Solutions for information purposes, and to assist persons in obtaining
information about or related to a domain name registration record.
Network Solutions does not guarantee its accuracy.  By submitting a
WHOIS query, you agree that you will use this Data only for lawful
purposes and that, under no circumstances will you use this Data to:
(1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail
(spam); or  (2) enable high volume, automated, electronic processes
that apply to Network Solutions (or its systems).  Network Solutions
reserves the right to modify these terms at any time.  By submitting
this query, you agree to abide by this policy.

Registrant:
pogo.com Inc (POGO9-DOM)
   300 California Street, Suite 800
   San Francisco, CA 94104
   US

   Domain Name: POGO.COM

   Administrative Contact, Technical Contact, Zone Contact:
      King, David M  (DMK2)  dking@POGO.COM
      pogo.com Inc.
      300 California Street, Suite 800
      San Francisco, CA 94104
      415-778-3548
   Billing Contact:
      Chao, Rachel  (CR449-ORG)  rchao@TENETWORK.COM
      Total Entertainment Network
      500 Howard Street, Suite 300
      San Francisco , CA 94105
      US
      415-778-3500
      Fax- 415-778-3520

   Record last updated on 16-Aug-2000.
   Record expires on 16-Aug-2001.
   Record created on 16-Aug-2000.
   Database last updated on 31-Oct-2000 06:27:59 EST.

   Domain servers in listed order:

   DNS02.POGO.COM		208.50.167.248
   DNS03.POGO.COM		208.50.167.249


------------------------------------------------------------------
You received this message because you searched for a domain
on BetterWhois.com (http://www.betterwhois.com) and asked to
have the results e-mailed to you.
------------------------------------------------------------------



From owner-ietf-outbound  Thu Nov  2 09:30:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA02332
	for ietf-outbound.10@ietf.org; Thu, 2 Nov 2000 09:30:03 -0500 (EST)
Received: from heron.verisign.com ([216.168.233.95])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29581
	for <ietf@ietf.org>; Thu, 2 Nov 2000 09:22:08 -0500 (EST)
Received: from REGDOM-EX01.prod.netsol.com (rdex01-node1.prod.netsol.com [10.131.4.28])
	by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id JAA13573
	for <ietf@ietf.org>; Thu, 2 Nov 2000 09:11:20 -0500 (EST)
Received: by regdom-ex01.prod.netsol.com with Internet Mail Service (5.5.2650.21)
	id <VMQ0BQZF>; Thu, 2 Nov 2000 09:19:28 -0500
Message-ID: <DF737E620579D411A8E400D0B77E671D310E77@regdom-ex01.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Domain Registration Services BOF Announcement
Date: Thu, 2 Nov 2000 09:19:25 -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

There will be a BOF session during the San Diego IETF meeting to ascertain
interest and (potentially) establish goals for a working group devoted to
developing standards track Internet domain name registration service
protocols.  The BOF has been tentatively scheduled for Thursday 14 December
during the 0900-1130 morning session.

BOF Description:
Discussion of existing requirements for a generic registry-registrar
protocol and check of interest in using these requirements as the basis for
a standards track protocol.  Review of current whois protocol proposals and
check of interest in including whois protocols within the charter of a
working group.

Suggested Agenda:
5m Introductions and agenda presentation
20m Review of existing requirements per draft-hollenbeck-grrp-reqs-05.txt
15m Discussion of interest in a standards track domain registration protocol
15m Discussion of interest in whois protocols
15m (If needed) Review of existing whois protocol efforts
20m Open discussion -- do we go on?
30m (If needed) WG goal brainstorming

Scott Hollenbeck
VeriSign Global Registry Services



From owner-ietf-outbound  Sat Nov  4 23:32:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA14792
	for ietf-outbound.10@ietf.org; Sat, 4 Nov 2000 23:30:03 -0500 (EST)
Received: from tomts7-srv.bellnexxia.net (tomts7.bellnexxia.net [209.226.175.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA14221
	for <ietf@ietf.org>; Sat, 4 Nov 2000 23:27:41 -0500 (EST)
Received: from ietf.org ([216.209.82.195]) by tomts7-srv.bellnexxia.net
          (InterMail vM.4.01.03.00 201-229-121) with SMTP
          id <20001105042713.FZKF20301.tomts7-srv.bellnexxia.net@ietf.org>
          for <ietf@ietf.org>; Sat, 4 Nov 2000 23:27:13 -0500
MIME-Version: 1.0
From: Mary
REPLY-TO: group3us@yahoo.com
To: ietf@ietf.org
Subject: Ebay4Sex Gets Laid!!!!!
Content-Type: multipart/mixed;
              boundary=Uniqque-Boundary
Message-Id: <20001105042713.FZKF20301.tomts7-srv.bellnexxia.net@ietf.org>
Date: Sat, 4 Nov 2000 23:27:13 -0500
X-Loop: ietf@ietf.org

 [ Random garbage here ]


--Uniqque-Boundary
Content-type: text/html; charset=US-ASCII

<html>

<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Brought to you by</title>
</head>

<body bgcolor="#000000" text="#FFFFFF">

<p>&nbsp;</p>
<p>&nbsp;</p>
<table border="0" cellpadding="0">
  <tr>
    <td valign="middle" align="center">Brought to you by;<br>
      EVERYTHINGAMATEUR.COM</td>
    <td valign="middle" align="center"><a href="http://www.everythingamateur.com"><img border="0" src="http://216.66.44.110/nakedchix_img05_rgt.jpg" width="310" height="73"></a></td>
  </tr>
  <tr>
    <td valign="middle" align="center"><a href="http://www.rakil.com"><img border="0" src="http://216.66.44.110/ban468-rakil.jpg" width="468" height="60"></a></td>
    <td valign="middle" align="center"><a href="http://www.ebay4sex.com"><img border="0" src="http://216.66.44.110/ebay_banner.jpg" width="468" height="60"></a></td>
  </tr>
</table>
<p>&nbsp;</p>
<p align="center">for advertising information<br>
<a href="mailto:webmaster@everythingamateur.com">webmaster@everythingamateur.com</a></p>

</body>

</html>


























--Uniqque-Boundary--



From owner-ietf-outbound  Sat Nov  4 23:41:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA18178
	for ietf-outbound.10@ietf.org; Sat, 4 Nov 2000 23:40:04 -0500 (EST)
Received: from tomts5-srv.bellnexxia.net (tomts5.bellnexxia.net [209.226.175.25])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA14552
	for <ietf@ietf.org>; Sat, 4 Nov 2000 23:29:03 -0500 (EST)
Received: from ietf.org ([216.209.82.195]) by tomts5-srv.bellnexxia.net
          (InterMail vM.4.01.03.00 201-229-121) with SMTP
          id <20001105042835.YEYG18376.tomts5-srv.bellnexxia.net@ietf.org>
          for <ietf@ietf.org>; Sat, 4 Nov 2000 23:28:35 -0500
MIME-Version: 1.0
From: Mary
REPLY-TO: group3us@yahoo.com
To: ietf@ietf.org
Subject: Ebay4Sex Gets Laid!!!!!
Content-Type: multipart/mixed;
              boundary=Uniqque-Boundary
Message-Id: <20001105042835.YEYG18376.tomts5-srv.bellnexxia.net@ietf.org>
Date: Sat, 4 Nov 2000 23:28:36 -0500
X-Loop: ietf@ietf.org

 [ Random garbage here ]


--Uniqque-Boundary
Content-type: text/html; charset=US-ASCII

<html>

<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Brought to you by</title>
</head>

<body bgcolor="#000000" text="#FFFFFF">

<p>&nbsp;</p>
<p>&nbsp;</p>
<table border="0" cellpadding="0">
  <tr>
    <td valign="middle" align="center">Brought to you by;<br>
      EVERYTHINGAMATEUR.COM</td>
    <td valign="middle" align="center"><a href="http://www.everythingamateur.com"><img border="0" src="http://216.66.44.110/nakedchix_img05_rgt.jpg" width="310" height="73"></a></td>
  </tr>
  <tr>
    <td valign="middle" align="center"><a href="http://www.rakil.com"><img border="0" src="http://216.66.44.110/ban468-rakil.jpg" width="468" height="60"></a></td>
    <td valign="middle" align="center"><a href="http://www.ebay4sex.com"><img border="0" src="http://216.66.44.110/ebay_banner.jpg" width="468" height="60"></a></td>
  </tr>
</table>
<p>&nbsp;</p>
<p align="center">for advertising information<br>
<a href="mailto:webmaster@everythingamateur.com">webmaster@everythingamateur.com</a></p>

</body>

</html>


























--Uniqque-Boundary--



From owner-ietf-outbound  Mon Nov  6 15:21:46 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA14084
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 15:20:02 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA12812
	for <ietf@ietf.org>; Mon, 6 Nov 2000 15:14:48 -0500 (EST)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id PAA27003
	for <ietf@ietf.org>; Mon, 6 Nov 2000 15:14:44 -0500 (EST)
Sender: hgs@cs.columbia.edu
Message-ID: <3A071135.38F7B7D8@cs.columbia.edu>
Date: Mon, 06 Nov 2000 15:14:45 -0500
From: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
Organization: Dept. of Computer Science, Columbia University
X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Bake-off as trademark
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've been approached regarding the use of the (claimed-to-be)
trademarked term bake-off. It would be helpful if somebody can provide
credible evidence that this term has been used within the technical
community for many years. (In case you didn't know,
http://www.bakeoff.com/ shows the non-technical use....)

Thank you.
-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From owner-ietf-outbound  Mon Nov  6 16:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA25691
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 16:00:03 -0500 (EST)
Received: from mail-green.research.att.com ([135.207.30.103])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA25484
	for <ietf@ietf.org>; Mon, 6 Nov 2000 15:59:08 -0500 (EST)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-green.research.att.com (Postfix) with ESMTP
	id B23EA1E005; Mon,  6 Nov 2000 15:59:09 -0500 (EST)
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 PAA19786;
	Mon, 6 Nov 2000 15:59:07 -0500 (EST)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id A206135DC2; Mon,  6 Nov 2000 15:59:05 -0500 (EST)
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: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
Cc: ietf@ietf.org
Subject: Re: Bake-off as trademark 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 06 Nov 2000 15:59:05 -0500
Sender: smb@research.att.com
Message-Id: <20001106205905.A206135DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <3A071135.38F7B7D8@cs.columbia.edu>, "Henning G. Schulzrinne" writes
:
>I've been approached regarding the use of the (claimed-to-be)
>trademarked term bake-off. It would be helpful if somebody can provide
>credible evidence that this term has been used within the technical
>community for many years. (In case you didn't know,
>http://www.bakeoff.com/ shows the non-technical use....)

It's used in RFC 1371, from October 1992.  Of course, that RFC also 
says:

   The IAB/IETF are committed to a timely introduction of OSI into the
   Internet.

Anyway -- I seem to recall seeing the term in "TCP/IP Protocol 
Transition Handbook", from circa 193, but my copy isn't conveniently 
accessible at the moment.

		--Steve Bellovin




From owner-ietf-outbound  Mon Nov  6 16:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA28300
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 16:10:03 -0500 (EST)
Received: from localhost.localdomain ([207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA26591
	for <ietf@ietf.org>; Mon, 6 Nov 2000 16:02:51 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eA6L5lo02884
	for <ietf@ietf.org>; Mon, 6 Nov 2000 16:05:47 -0500
Sender: francis@localhost.localdomain
Message-ID: <3A071D25.1B5C7DE2@ecal.com>
Date: Mon, 06 Nov 2000 16:05:41 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586)
X-Accept-Language: en, de, es
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Bake-off as trademark
References: <3A071135.38F7B7D8@cs.columbia.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

"Henning G. Schulzrinne" wrote:

> I've been approached regarding the use of the (claimed-to-be)
> trademarked term bake-off. It would be helpful if somebody can provide
> credible evidence that this term has been used within the technical
> community for many years.

Well, there's RFC-1025, published in 1987; is 13 years enough? Also, it
refers to bakeoffs held as early as 1979, though it could be that they
were called something else at the time.

In any case, don't trademarks apply only within a single domain? There
isn't much overlap between the markets for baked goods and network
protocols.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Please do not adjust your mind--reality is   |
|francis@ecal.com|malfunctioning.                              |
\==============================================================/





From owner-ietf-outbound  Mon Nov  6 16:20:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA01674
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 16:20:04 -0500 (EST)
Received: from marcos.networkcs.com ([137.66.16.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA26737
	for <ietf@ietf.org>; Mon, 6 Nov 2000 16:03:20 -0500 (EST)
Received: from us.networkcs.com (us.networkcs.com [137.66.11.15])
	by marcos.networkcs.com (8.9.3/8.9.3) with ESMTP id PAA91130
	for <ietf@ietf.org>; Mon, 6 Nov 2000 15:03:21 -0600 (CST)
	(envelope-from salo@us.networkcs.com)
Received: (from salo@localhost)
	by us.networkcs.com (8.9.2/8.9.2) id PAA45318
	for ietf@ietf.org; Mon, 6 Nov 2000 15:03:21 -0600 (CST)
	(envelope-from salo)
Date: Mon, 6 Nov 2000 15:03:21 -0600 (CST)
From: Tim Salo <salo@networkcs.com>
Message-Id: <200011062103.PAA45318@us.networkcs.com>
To: ietf@ietf.org
Subject: Re: Bake-off as trademark
In-Reply-To: <3A071135.38F7B7D8@cs.columbia.edu>
X-Loop: ietf@ietf.org

> Date: Mon, 06 Nov 2000 15:14:45 -0500
> From: "Henning G. Schulzrinne" <hgs@CS.COLUMBIA.EDU>
> Subject: Bake-off as trademark
> 
> I've been approached regarding the use of the (claimed-to-be)
> trademarked term bake-off. It would be helpful if somebody can provide
> credible evidence that this term has been used within the technical
> community for many years. (In case you didn't know,
> http://www.bakeoff.com/ shows the non-technical use....)

RFC 1025, "TCP and IP Bake Off", J. Postel, September 1987.

-tjs



From owner-ietf-outbound  Mon Nov  6 16:30:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA05594
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 16:30:03 -0500 (EST)
Received: from aegir.EU.net (aegir.EU.net [193.242.90.19])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA27057
	for <ietf@ietf.org>; Mon, 6 Nov 2000 16:04:33 -0500 (EST)
Received: from aegir.EU.net (localhost.eu.net [127.0.0.1])
	by aegir.EU.net (8.9.3/8.9.3) with ESMTP id WAA12315;
	Mon, 6 Nov 2000 22:04:18 +0100 (MET)
Message-Id: <200011062104.WAA12315@aegir.EU.net>
To: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
cc: ietf@ietf.org
Subject: Re: Bake-off as trademark 
In-reply-to: Your message of "Mon, 06 Nov 2000 15:14:45 EST."
             <3A071135.38F7B7D8@cs.columbia.edu> 
From: James Aldridge <jhma@KPNQwest.net>
Date: Mon, 06 Nov 2000 22:04:18 +0100
Sender: jhma@EU.net
X-Loop: ietf@ietf.org

"Henning G. Schulzrinne" wrote:
> I've been approached regarding the use of the (claimed-to-be)
> trademarked term bake-off. It would be helpful if somebody can provide
> credible evidence that this term has been used within the technical
> community for many years. (In case you didn't know,
> http://www.bakeoff.com/ shows the non-technical use....)

See, for example, rfc-1025 (September 1987).

James



From owner-ietf-outbound  Mon Nov  6 16:50:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA12467
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 16:50:04 -0500 (EST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA02900
	for <ietf@ietf.org>; Mon, 6 Nov 2000 16:22:54 -0500 (EST)
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 NAA00782;
	Mon, 6 Nov 2000 13:22:51 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id VAA26405;
	Mon, 6 Nov 2000 21:22:50 GMT
Date: Mon, 6 Nov 2000 21:22:50 GMT
Message-Id: <200011062122.VAA26405@gra.isi.edu>
To: ietf@ietf.org, hgs@CS.COLUMBIA.EDU
Subject: Re: Bake-off as trademark
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org


  *> From owner-ietf-outbound@ietf.org Mon Nov  6 12:51:57 2000
  *> Sender: hgs@CS.COLUMBIA.EDU
  *> Date: Mon, 06 Nov 2000 15:14:45 -0500
  *> From: "Henning G. Schulzrinne" <hgs@CS.COLUMBIA.EDU>
  *> Organization: Dept. of Computer Science, Columbia University
  *> X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.7 sun4u)
  *> X-Accept-Language: en
  *> MIME-Version: 1.0
  *> To: ietf@ietf.org
  *> Subject: Bake-off as trademark
  *> Content-Transfer-Encoding: 7bit
  *> Content-Transfer-Encoding: 7bit
  *> X-Loop: ietf@ietf.org
  *> Content-Transfer-Encoding: 7bit
  *> X-Lines: 10
  *> 
  *> I've been approached regarding the use of the (claimed-to-be)
  *> trademarked term bake-off. It would be helpful if somebody can provide
  *> credible evidence that this term has been used within the technical
  *> community for many years. (In case you didn't know,
  *> http://www.bakeoff.com/ shows the non-technical use....)
  *> 
  *> Thank you.
  *> -- 
  *> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs
  *> 
  *> 

Henning,

Please see RFC 1025 from Sept 1987, or IEN 160 (online at
the RFC Editor web site) for a November 1980 bake off.
Is this 20 years ago early enough?

Bob Braden



From owner-ietf-outbound  Mon Nov  6 17:00:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15757
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 17:00:03 -0500 (EST)
Received: from roam.psg.com (210146008044.cidr.odn.ne.jp [210.146.8.44])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA04355
	for <ietf@ietf.org>; Mon, 6 Nov 2000 16:26:23 -0500 (EST)
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 13stmU-0001xt-00; Tue, 07 Nov 2000 06:26:18 +0900
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: John Stracke <francis@ecal.com>
Cc: ietf@ietf.org
Subject: Re: Bake-off as trademark
References: <3A071135.38F7B7D8@cs.columbia.edu>
	<3A071D25.1B5C7DE2@ecal.com>
Message-Id: <E13stmU-0001xt-00@roam.psg.com>
Date: Tue, 07 Nov 2000 06:26:18 +0900
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> There isn't much overlap between the markets for baked goods and network
> protocols.

the main intersection is in the doughnut area of high fat, too much sugar,
and too little nutritional value.

randy



From owner-ietf-outbound  Mon Nov  6 17:10:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA18630
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 17:10:02 -0500 (EST)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA05058
	for <ietf@ietf.org>; Mon, 6 Nov 2000 16:28:32 -0500 (EST)
Received: from contactdish (st-lambert-101-2-atkielsk.adsl.nerim.net [62.4.19.136]) by atkielski.com (8.8.8) id WAA91812; Mon, 6 Nov 2000 22:28:29 +0100 (CET)
Message-ID: <004e01c04838$8261cd70$0a00000a@contactdish>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <3A071135.38F7B7D8@cs.columbia.edu>
Subject: Re: Bake-off as trademark
Date: Mon, 6 Nov 2000 22:28:27 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.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

> I've been approached regarding the use of the
> (claimed-to-be) trademarked term bake-off. It
> would be helpful if somebody can provide credible
> evidence that this term has been used within
> the technical community for many years.

Not necessary.  Trademark protection only extends to uses of a trademarked
term or mark that might elicit confusion with the protected use.  Thus,
Bake-Off might be protected with respect to use by companies in the same
business as Pillsbury, or in situations where use of the term might falsely
create the impression of a connection with or an endorsement by Pilsbury,
but in other contexts the protection does not apply.  Protection for coined
terms such as Bake-Off is much stronger than for ordinary terms (such as
Windows), however.

Actually, I don't recall hearing this term used in technical circles.  What
is it supposed to mean?

Did you know that Paramount Pictures has asserted trademark status for all
of the names of the characters in the original Star Trek series?  Only in
America!



From owner-ietf-outbound  Mon Nov  6 17:20:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA22542
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 17:20:03 -0500 (EST)
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA09792
	for <ietf@ietf.org>; Mon, 6 Nov 2000 16:41:51 -0500 (EST)
From: Mike_Borella@3com.com
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id eA6LeiO12247;
	Mon, 6 Nov 2000 13:40:44 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.OPS.3Com.COM [139.87.48.104])
	by opal.3com.com (Switch-2.0.1/Switch-2.0.1) with SMTP id eA6LfLX03353;
	Mon, 6 Nov 2000 13:41:21 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 8825698F.007753E7 ; Mon, 6 Nov 2000 13:43:22 -0800
X-Lotus-FromDomain: 3COM
To: "Steven M. Bellovin" <smb@RESEARCH.ATT.COM>
cc: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>, ietf@ietf.org
Message-ID: <8825698F.00774F74.00@hqoutbound.ops.3com.com>
Date: Mon, 6 Nov 2000 15:41:33 -0600
Subject: Re: Bake-off as trademark
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org



>In message <3A071135.38F7B7D8@cs.columbia.edu>, "Henning G. Schulzrinne"
writes:
>>I've been approached regarding the use of the (claimed-to-be)
>>trademarked term bake-off. It would be helpful if somebody can provide
>>credible evidence that this term has been used within the technical
>>community for many years. (In case you didn't know,
>>http://www.bakeoff.com/ shows the non-technical use....)
>
>It's used in RFC 1371, from October 1992.  Of course, that RFC also
>says:
>
>   The IAB/IETF are committed to a timely introduction of OSI into the
>   Internet.

There is an earlier reference.

From the text of RFC1025:

   In the early days of the development of TCP and IP, when there were
   very few implementations and the specifications were still evolving,
   the only way to determine if an implementation was "correct" was to
   test it against other implementations and argue that the results
   showed your own implementation to have done the right thing.  These
   tests and discussions could, in those early days, as likely change
   the specification as change the implementation.

   There were a few times when this testing was focused, bringing
   together all known implementations and running through a set of tests
   in hopes of demonstrating the N squared connectivity and correct
   implementation of the various tricky cases.  These events were called
   "Bake Offs".

   An early version of the list of tests included here appears in IEN-69
   of October 1978.  A demonstration of four TCP implementations was
   held at the Defense Communication Engineering Center in Reston,
   Virginia on 4 December 1978, and reported in IEN-70 of December 1978.
   A bake off of six implementations was held 27-28 January 1979 at
   USC-Information Sciences Institute in Marina del Rey, California and
   reported in IEN-77 of February 1979.  And a distributed bake off was
   held in April 1980 over the network and reported in IEN-145 of May
   1980.

   The following section reproduces (with very slight editing) the
   procedure, tests, and scoring of the April 1980 Bake Off.

Of course one would hope that they were called "bake offs"
back then, as well.


>Anyway -- I seem to recall seeing the term in "TCP/IP Protocol
>Transition Handbook", from circa 193, but my copy isn't conveniently
                                  ^^^
>accessible at the moment.
>
>         --Steve Bellovin

You must have misplaced the stone tablets.

-Mike





From owner-ietf-outbound  Mon Nov  6 17:30:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA26661
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 17:30:04 -0500 (EST)
Received: from femail4.sdc1.sfba.home.com (femail4.sdc1.sfba.home.com [24.0.95.84])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA10015
	for <ietf@ietf.org>; Mon, 6 Nov 2000 16:42:29 -0500 (EST)
Received: from home.com ([24.3.205.203]) by femail4.sdc1.sfba.home.com
          (InterMail vM.4.01.03.00 201-229-121) with ESMTP
          id <20001106214101.JKXX26316.femail4.sdc1.sfba.home.com@home.com>;
          Mon, 6 Nov 2000 13:41:01 -0800
Message-ID: <3A0725B5.1DCC1A05@home.com>
Date: Mon, 06 Nov 2000 16:42:13 -0500
From: Herman Silbiger <hsilbiger@home.com>
Reply-To: hsilbiger@IEEE.ORG
X-Mailer: Mozilla 4.75 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
CC: ietf@ietf.org
Subject: Re: Bake-off as trademark
References: <3A071135.38F7B7D8@cs.columbia.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

By whom, Pillsbury?

"Henning G. Schulzrinne" wrote:

> I've been approached regarding the use of the (claimed-to-be)
> trademarked term bake-off. It would be helpful if somebody can provide
> credible evidence that this term has been used within the technical
> community for many years. (In case you didn't know,
> http://www.bakeoff.com/ shows the non-technical use....)
>
> Thank you.
> --
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From owner-ietf-outbound  Mon Nov  6 17:40:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA29893
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 17:40:02 -0500 (EST)
Received: from diablo.cisco.com (diablo.cisco.com [171.68.224.210])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11282
	for <ietf@ietf.org>; Mon, 6 Nov 2000 16:46:29 -0500 (EST)
Received: from localhost (ole@localhost) by diablo.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id NAA27071; Mon, 6 Nov 2000 13:45:29 -0800 (PST)
Date: Mon, 6 Nov 2000 13:45:28 -0800 (PST)
From: "Ole J. Jacobsen" <ole@cisco.com>
To: Tim Salo <salo@networkcs.com>
cc: ietf@ietf.org
Subject: Re: Bake-off as trademark
In-Reply-To: <200011062103.PAA45318@us.networkcs.com>
Message-ID: <Pine.HPX.4.02.10011061341530.21134-100000@diablo.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

Prior use as a generic term isn't always enough though.

In 1994 a competitor to Interop trademarked the generic word "shownet" as
a purely hostile move, forcing Interop to stop using it because it had not
previously been trademarked and the theory was that it would take to much
time and money to fight.

Thus, it is now called "InteropNet" and yes, it's heavily trademarked.

Ole


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






From owner-ietf-outbound  Mon Nov  6 17:50:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA03178
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 17:50:03 -0500 (EST)
Received: from renoir.op.net (root@[207.29.195.4])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11785
	for <ietf@ietf.org>; Mon, 6 Nov 2000 16:47:59 -0500 (EST)
Received: from pisarro.op.net (jaw@pisarro.op.net [207.29.195.22]) by renoir.op.net (o1/$Revision: 1.18 $) with ESMTP id QAA12403 for <ietf@ietf.org>; Mon, 6 Nov 2000 16:47:58 -0500 (EST)
Received: (from jaw@localhost) by pisarro.op.net (o2/$Revision: 1.1 $) id QAA11855 for ietf@ietf.org; Mon, 6 Nov 2000 16:47:57 -0500 (EST)
Date: Mon, 6 Nov 2000 16:47:57 -0500 (EST)
From: Jeff Weisberg <jaw@Op.Net>
Message-Id: <200011062147.QAA11855@pisarro.op.net>
To: ietf@ietf.org
Subject: Re: Bake-off as trademark
X-Loop: ietf@ietf.org


| > I've been approached regarding the use of the (claimed-to-be)
| > trademarked term bake-off. It would be helpful if somebody can provide
| > credible evidence that this term has been used within the technical
| > community for many years. (In case you didn't know,
| > http://www.bakeoff.com/ shows the non-technical use....)
| 
| RFC 1025, "TCP and IP Bake Off", J. Postel, September 1987.

IEN 160, "Internet Meeting Notes", J. Postel, Nov. 1980
	Section V. - "BAKE OFF SUMMARY"


	--jeff



From owner-ietf-outbound  Mon Nov  6 18:00:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA07407
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 18:00:03 -0500 (EST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA18224
	for <ietf@ietf.org>; Mon, 6 Nov 2000 17:08:11 -0500 (EST)
Received: from zed.isi.edu (root@zed.isi.edu [128.9.160.57])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id OAA07462;
	Mon, 6 Nov 2000 14:08:01 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.9.3/8.8.6) id OAA10379;
	Mon, 6 Nov 2000 14:08:01 -0800
Message-Id: <200011062208.OAA10379@zed.isi.edu>
Subject: Re: Bake-off as trademark
To: smb@research.att.com (Steven M. Bellovin)
Date: Mon, 6 Nov 2000 14:08:01 -0800 (PST)
Cc: hgs@CS.COLUMBIA.EDU (Henning G. Schulzrinne), ietf@ietf.org
In-Reply-To: <20001106205905.A206135DC2@smb.research.att.com> from "Steven M. Bellovin" at Nov 06, 2000 03:59:05 PM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

% 
% In message <3A071135.38F7B7D8@cs.columbia.edu>, "Henning G. Schulzrinne" writes
% :
% >I've been approached regarding the use of the (claimed-to-be)
% >trademarked term bake-off. It would be helpful if somebody can provide
% >credible evidence that this term has been used within the technical
% >community for many years. (In case you didn't know,
% >http://www.bakeoff.com/ shows the non-technical use....)
% 
% It's used in RFC 1371, from October 1992.  Of course, that RFC also 
% says:
% 
%    The IAB/IETF are committed to a timely introduction of OSI into the
%    Internet.
% 
% Anyway -- I seem to recall seeing the term in "TCP/IP Protocol 
% Transition Handbook", from circa 193, but my copy isn't conveniently 
% accessible at the moment.
% 
% 		--Steve Bellovin

Interop was Dan Lynches venue for TCP/IP bakeoffs in the 1980's.
(thats why we have only three IETFs... :)

--bill



From owner-ietf-outbound  Mon Nov  6 18:10:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA11035
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 18:10:03 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA20445
	for <ietf@ietf.org>; Mon, 6 Nov 2000 17:14:28 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA01399;
	Mon, 6 Nov 2000 17:13:57 -0500 (EST)
Received: from whq-msgrtr-01.fore.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA19578;
	Mon, 6 Nov 2000 17:13:58 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <V6TAD9JL>; Mon, 6 Nov 2000 17:13:17 -0500
Message-ID: <4FBEA8857476D311A03300204840E1CF01A6E9D2@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Steven M. Bellovin'" <smb@research.att.com>,
        "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
Cc: ietf@ietf.org
Subject: RE: Bake-off as trademark 
Date: Mon, 6 Nov 2000 17:13:50 -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

That gave me a lead on a better one:

Network Working Group                                          J. Postel
Request for Comments: 1025                                           ISI
                                                          September 1987


                          TCP AND IP BAKE OFF

How about that!

Brian

> -----Original Message-----
> From: Steven M. Bellovin [mailto:smb@research.att.com]
> Sent: Monday, November 06, 2000 3:59 PM
> To: Henning G. Schulzrinne
> Cc: ietf@ietf.org
> Subject: Re: Bake-off as trademark 
> 
> 
> In message <3A071135.38F7B7D8@cs.columbia.edu>, "Henning G. 
> Schulzrinne" writes
> :
> >I've been approached regarding the use of the (claimed-to-be)
> >trademarked term bake-off. It would be helpful if somebody 
> can provide
> >credible evidence that this term has been used within the technical
> >community for many years. (In case you didn't know,
> >http://www.bakeoff.com/ shows the non-technical use....)
> 
> It's used in RFC 1371, from October 1992.  Of course, that RFC also 
> says:
> 
>    The IAB/IETF are committed to a timely introduction of OSI into the
>    Internet.
> 
> Anyway -- I seem to recall seeing the term in "TCP/IP Protocol 
> Transition Handbook", from circa 193, but my copy isn't conveniently 
> accessible at the moment.
> 
> 		--Steve Bellovin
> 
> 
> -
> 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  Mon Nov  6 18:30:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA19050
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 18:30:03 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA24244
	for <ietf@ietf.org>; Mon, 6 Nov 2000 17:24:13 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA02101;
	Mon, 6 Nov 2000 17:23:43 -0500 (EST)
Received: from whq-msgrtr-01.fore.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA21375;
	Mon, 6 Nov 2000 17:23:43 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <V6TAD940>; Mon, 6 Nov 2000 17:23:02 -0500
Message-ID: <4FBEA8857476D311A03300204840E1CF01A6E9D3@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Henning G. Schulzrinne'" <hgs@cs.columbia.edu>, ietf@ietf.org
Subject: RE: Bake-off as trademark
Date: Mon, 6 Nov 2000 17:23:42 -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

I also looked at the references in RFC1025, and found that IEN-70 and
IEN-77 are not on line.  However, IEN-165 is:
http://www.normos.org/ietf/ien/ien-160.txt.1
J. Postel IEN 160 ISI 7 November 1980 Internet Meeting Notes -- 7-8-9
October 1980 
and states:
BAKE OFF SUMMARY Dave Mills reported on the sessions for testing the
fragmentation ...

Brian

> -----Original Message-----
> From: Henning G. Schulzrinne [mailto:hgs@cs.columbia.edu]
> Sent: Monday, November 06, 2000 3:15 PM
> To: ietf@ietf.org
> Subject: Bake-off as trademark
> 
> 
> I've been approached regarding the use of the (claimed-to-be)
> trademarked term bake-off. It would be helpful if somebody can provide
> credible evidence that this term has been used within the technical
> community for many years. (In case you didn't know,
> http://www.bakeoff.com/ shows the non-technical use....)
> 
> Thank you.
> -- 
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs
> 
> -
> 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  Mon Nov  6 18:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA22371
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 18:40:03 -0500 (EST)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA29698
	for <ietf@ietf.org>; Mon, 6 Nov 2000 17:39:26 -0500 (EST)
Received: from airborne.cisco.com (airborne.cisco.com [171.71.154.32])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA19314;
	Mon, 6 Nov 2000 14:38:29 -0800 (PST)
Received: from sbrim-nt.cisco.com (dhcp-128-107-141-187.cisco.com [128.107.141.187])
	by airborne.cisco.com (Mirapoint)
	with ESMTP id AAI16306;
	Mon, 6 Nov 2000 14:38:25 -0800 (PST)
Message-Id: <4.3.2.7.2.20001106173723.00ae05b0@airborne.cisco.com>
X-Sender: sbrim@airborne.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 06 Nov 2000 17:38:20 -0500
To: Bob Braden <braden@ISI.EDU>
From: Scott Brim <sbrim@cisco.com>
Subject: Re: Bake-off as trademark
Cc: ietf@ietf.org, hgs@CS.COLUMBIA.EDU
In-Reply-To: <200011062122.VAA26405@gra.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 09:22 PM 11/06/2000 +0000, Bob Braden wrote:
>Henning,
>
>Please see RFC 1025 from Sept 1987, or IEN 160 (online at
>the RFC Editor web site) for a November 1980 bake off.
>Is this 20 years ago early enough?

Since the first Pillsbury Bake-Off was 50 years ago, no.  But what's the 
issue?  Is Pillsbury telling us cease and desist?  



From owner-ietf-outbound  Mon Nov  6 18:50:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA26883
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 18:50:04 -0500 (EST)
Received: from lespaul.process.com ([192.42.95.27])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA02574
	for <ietf@ietf.org>; Mon, 6 Nov 2000 17:48:08 -0500 (EST)
Received: by lespaul.process.com with Internet Mail Service (5.5.2650.21)
	id <VRHLALK1>; Mon, 6 Nov 2000 17:47:39 -0500
Message-ID: <63D30D6E10CFD11190A90000F805FE8603607271@lespaul.process.com>
From: Bernie Volz <Volz@ipworks.com>
To: ietf@ietf.org
Subject: RE: Bake-off as trademark
Date: Mon, 6 Nov 2000 17:47:37 -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

John is correct.

You can do the searches yourself at http://www.uspto.gov.

All of the "bake-off" trademarks found by the system are those relating to
cooking and baked goods, not for software or hardware testing, etc. Some of
these trademarks go back to 1965. But again they are not in the computer
field and so it is not an issue.

- Bernie Volz

-----Original Message-----
From: John Stracke [mailto:francis@ecal.com]
Sent: Monday, November 06, 2000 4:06 PM
To: ietf@ietf.org
Subject: Re: Bake-off as trademark


"Henning G. Schulzrinne" wrote:

> I've been approached regarding the use of the (claimed-to-be)
> trademarked term bake-off. It would be helpful if somebody can provide
> credible evidence that this term has been used within the technical
> community for many years.

Well, there's RFC-1025, published in 1987; is 13 years enough? Also, it
refers to bakeoffs held as early as 1979, though it could be that they
were called something else at the time.

In any case, don't trademarks apply only within a single domain? There
isn't much overlap between the markets for baked goods and network
protocols.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Please do not adjust your mind--reality is   |
|francis@ecal.com|malfunctioning.                              |
\==============================================================/




From owner-ietf-outbound  Mon Nov  6 19:00:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA00507
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 19:00:02 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA06466
	for <ietf@ietf.org>; Mon, 6 Nov 2000 17:57:45 -0500 (EST)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id RAA09708;
	Mon, 6 Nov 2000 17:57:40 -0500 (EST)
Sender: hgs@cs.columbia.edu
Message-ID: <3A073764.51898752@cs.columbia.edu>
Date: Mon, 06 Nov 2000 17:57:40 -0500
From: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
Organization: Dept. of Computer Science, Columbia University
X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Scott Brim <sbrim@cisco.com>
CC: Bob Braden <braden@ISI.EDU>, ietf@ietf.org
Subject: Re: Bake-off as trademark
References: <4.3.2.7.2.20001106173723.00ae05b0@airborne.cisco.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

Scott Brim wrote:
> 
> At 09:22 PM 11/06/2000 +0000, Bob Braden wrote:
> >Henning,
> >
> >Please see RFC 1025 from Sept 1987, or IEN 160 (online at
> >the RFC Editor web site) for a November 1980 bake off.
> >Is this 20 years ago early enough?
> 
> Since the first Pillsbury Bake-Off was 50 years ago, no.  But what's the
> issue?  Is Pillsbury telling us cease and desist?

Pillsbury sent Columbia University a cease-and-desist letter, indeed,
presumably because of http://www.cs.columbia.edu/sip/bakeoff


-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From owner-ietf-outbound  Mon Nov  6 19:10:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA04057
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 19:10:04 -0500 (EST)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA17606
	for <ietf@ietf.org>; Mon, 6 Nov 2000 18:25:44 -0500 (EST)
Received: from contactdish (st-lambert-101-2-atkielsk.adsl.nerim.net [62.4.19.136]) by atkielski.com (8.8.8) id AAA04117; Tue, 7 Nov 2000 00:25:46 +0100 (CET)
Message-ID: <012301c04848$e3fba960$0a00000a@contactdish>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <Pine.HPX.4.02.10011061341530.21134-100000@diablo.cisco.com>
Subject: Re: Bake-off as trademark
Date: Tue, 7 Nov 2000 00:25:44 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.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

> In 1994 a competitor to Interop trademarked the generic
> word "shownet" as a purely hostile move, forcing Interop
> to stop using it because it had not previously been
> trademarked and the theory was that it would take to much
> time and money to fight.

Whose theory was that?  At least in the United States, that makes little
sense.  In the U.S., you must show that you have been consistently using a
trademark and identifying it with your product or service in order to claim
proprietary status for it, and if you have not been actively using and
protecting it, or if someone was actively using it before you did, your
trademark is unlikely to stand.  Maybe Interop should have fought it.

Trademarks are not like patents or copyrights.  You must actively use and
protect a trademark, or it can lose its special status.  And you can only
register it _after_ you have established it as a trademark, not before (in
the U.S.--in Europe, you can register before you use it, which is kind of
bizarre and much more restrictive).

> Thus, it is now called "InteropNet" and yes, it's heavily
> trademarked.

It's either a trademark or it's not.  There are no degrees of trademark
(other than registration).



From owner-ietf-outbound  Mon Nov  6 19:20:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA07705
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 19:20:03 -0500 (EST)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA18095
	for <ietf@ietf.org>; Mon, 6 Nov 2000 18:27:04 -0500 (EST)
Received: from contactdish (st-lambert-101-2-atkielsk.adsl.nerim.net [62.4.19.136]) by atkielski.com (8.8.8) id AAA04208; Tue, 7 Nov 2000 00:27:05 +0100 (CET)
Message-ID: <012c01c04849$13593600$0a00000a@contactdish>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <200011062147.QAA11855@pisarro.op.net>
Subject: Re: Bake-off as trademark
Date: Tue, 7 Nov 2000 00:27:04 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.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

> IEN 160, "Internet Meeting Notes", J. Postel, Nov. 1980
> Section V. - "BAKE OFF SUMMARY"

The problem with this prior use is that it was almost certainly based on the
trademarked use for baking competitions.  However, at the same time, since
this term is not being used in a contest that lends itself to confusion with
actual baking competitions, there may be no conflict, and thus no trademark
protection to worry about.



From owner-ietf-outbound  Mon Nov  6 19:40:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA15088
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 19:40:03 -0500 (EST)
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 SMTP id TAA13801
	for <ietf@ietf.org>; Mon, 6 Nov 2000 19:36:00 -0500 (EST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200011070026.JAA09362@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id JAA09362; Tue, 7 Nov 2000 09:26:44 +0900
Subject: Re: Bake-off as trademark
In-Reply-To: <3A071135.38F7B7D8@cs.columbia.edu> from "Henning G. Schulzrinne"
 at "Nov 6, 2000 03:14:45 pm"
To: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
Date: Tue, 7 Nov 2000 09:26:44 +0859 ()
CC: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Henning;

Silly thread. I thought, through discussion on domain names, people
are get accostomed not to think US trademark is not THE trademark.

> I've been approached regarding the use of the (claimed-to-be)
> trademarked term bake-off.

Trademarked in which country?

						Masataka Ohta



From owner-ietf-outbound  Mon Nov  6 20:20:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA27655
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 20:20:03 -0500 (EST)
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA25213
	for <ietf@ietf.org>; Mon, 6 Nov 2000 20:11:03 -0500 (EST)
From: Jim_Stephenson-Dunn@3com.com
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id eA719rD04756;
	Mon, 6 Nov 2000 17:09:53 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.OPS.3Com.COM [139.87.48.104])
	by opal.3com.com (Switch-2.0.1/Switch-2.0.1) with SMTP id eA71AUs07978;
	Mon, 6 Nov 2000 17:10:30 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256990.00069FF3 ; Mon, 6 Nov 2000 17:12:21 -0800
X-Lotus-FromDomain: 3COM
To: "Anthony Atkielski" <anthony@ATKIELSKI.COM>
cc: ietf@ietf.org
Message-ID: <88256990.00069EE6.00@hqoutbound.ops.3com.com>
Date: Mon, 6 Nov 2000 17:12:03 -0800
Subject: Re: Bake-off as trademark
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org



> I've been approached regarding the use of the
> (claimed-to-be) trademarked term bake-off. It
> would be helpful if somebody can provide credible
> evidence that this term has been used within
> the technical community for many years.

Did you know that Paramount Pictures has asserted trademark status for all
of the names of the characters in the original Star Trek series?  Only in
America!


Hmmm..... That is interesting in that I have a friend called James T. Kirk (the
T. is for Thomas instead of Tiberius). Does this mean that in the event of
paramount discovering the existence of this individual, they will sue him to
change his name ?

On the subject at hand though, I do not believe that a Trademark appies in this
case due to the fact that "bake-Off" is not a term that can be specifically and
individually applied to one company or product.

Just my two cents :-)

Jim




From owner-ietf-outbound  Mon Nov  6 21:20:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA18831
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 21:20:04 -0500 (EST)
Received: from smtp4-cm.mail.eni.net (smtp4a-cm.mail.eni.net [216.133.226.137])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA16730
	for <ietf@ietf.org>; Mon, 6 Nov 2000 21:12:40 -0500 (EST)
Received: from mdf (smirnoff.eni.net [155.229.121.74])
	by smtp4-cm.mail.eni.net (8.9.3/8.9.3) with SMTP id SAA17664;
	Mon, 6 Nov 2000 18:12:36 -0800
Reply-To: <mdf@epoch.net>
From: "Michael Francois" <mdf@epoch.net>
To: <hgs@cs.columbia.edu>, <ietf@ietf.org>
Subject: RE: Bake-off as trademark
Date: Mon, 6 Nov 2000 18:13:31 -0800
Message-ID: <NCBBKPAHJDJGOKEKJHAKAEAMFAAA.mdf@epoch.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <3A071135.38F7B7D8@cs.columbia.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

the term 'Bake-Off' is trademarked by the Pillsbury Company, with the first
use I can see in 1950 ... it refers to:

Word Mark BAKE-OFF
Goods and Services IC 035. US 101. G & S: COOKING CONTESTS FOR THE PURPOSE
OF PROMOTING THE CREATION OF NEW RECIPES. FIRST USE: 19500000. FIRST USE IN
COMMERCE: 19500000
Mark Drawing Code (1) TYPED DRAWING
Serial Number 72354774
Filing Date March 23, 1970
Registration Number 0938249
Registration Date July 18, 1972
Owner (REGISTRANT) PILLSBURY COMPANY, THE CORPORATION DELAWARE PILLSBURY
CENTER 200 SOUTH SIXTH ST. MINNEAPOLIS MINNESOTA 55402
Attorney of Record RICHARD Q. RUSSETH
Prior Registrations 0871348
Type of Mark SERVICE MARK
Register PRINCIPAL
Affidavit Text SECT 15. SECT 8 (6-YR).
Renewal 1ST RENEWAL 19920325
Live/Dead Indicator LIVE

http://tess.uspto.gov/bin/gate.exe?f=toc&state=mn8lij.1.1&p_search=searchss&
p_L=50&Search+History=&p_plural=yes&p_s_PARA4=&p_tagrepl%7E%3A=PARA4%24LD&p_
s_PARA3=bake+off&p_tagrepl%7E%3A=PARA3%24COMB&p_op_PARA3=AND&a_default=searc
h&a_search=Submit+Query

i noticed this site crossed out 'bake off' and replaced it with 'cacheoff'
... wonder if pilssbury spoke to them ...

http://cacheoff.ircache.net/

searching at google came back with pages and pages of technical and other
'bake offs' ...

http://www.google.com/search?q=bake+off

getting international for a moment, i think in england the term 'bake off'
refers to the process of finishing a partially baked product at another
location ...

http://www.wrightspies.co.uk/bake-off.htm

anyway, i should obviously be spending my time on something else ... :)

michael


:-----Original Message-----
:From: hgs@cs.columbia.edu [mailto:hgs@cs.columbia.edu]
:Sent: Monday, November 06, 2000 12:15 PM
:To: ietf@ietf.org
:Subject: Bake-off as trademark
:
:
:I've been approached regarding the use of the (claimed-to-be)
:trademarked term bake-off. It would be helpful if somebody can provide
:credible evidence that this term has been used within the technical
:community for many years. (In case you didn't know,
:http://www.bakeoff.com/ shows the non-technical use....)
:
:Thank you.
:--
:Henning Schulzrinne   http://www.cs.columbia.edu/~hgs
:
:



From owner-ietf-outbound  Mon Nov  6 21:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA22871
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 21:30:03 -0500 (EST)
Received: from nemo.corp.equinix.com (somehost-2.equinix.net [207.20.85.154])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA20678
	for <ietf@ietf.org>; Mon, 6 Nov 2000 21:24:38 -0500 (EST)
From: hardie@equinix.com
Received: (from hardie@localhost)
	by nemo.corp.equinix.com (8.9.3/8.9.3) id SAA15811;
	Mon, 6 Nov 2000 18:24:35 -0800 (PST)
Message-Id: <200011070224.SAA15811@nemo.corp.equinix.com>
Subject: Re: Bake-off as trademark
To: smb@research.att.com (Steven M. Bellovin)
Date: Mon, 6 Nov 2000 18:24:35 -0800 (PST)
Cc: hgs@cs.columbia.edu (Henning G. Schulzrinne), ietf@ietf.org
In-Reply-To: <20001106205905.A206135DC2@smb.research.att.com> from "Steven M. Bellovin" at Nov 06, 2000 03:59:05 PM
Reply-to: hardie@equinix.com
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>    The IAB/IETF are committed to a timely introduction of OSI into the
>    Internet.

I seem to recall Jake Feinler (who fought had against the mandate of
OSI by the government in GOSIP) said that the appropriate timing of
the introduction of OSI protocols would be measured by ice crystal
formation in Hell.  "Never" is time too, after all.

See RFC1169 for more about GOSIP.  We're your government, and we're
here to help you.

			Ted Hardie
			(No longer part of anyone's government)



From owner-ietf-outbound  Mon Nov  6 22:40:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA20190
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 22:40:03 -0500 (EST)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA18350
	for <ietf@ietf.org>; Mon, 6 Nov 2000 22:34:42 -0500 (EST)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id WAA06752;
        Mon, 6 Nov 2000 22:34:18 -0500 (EST)
Message-Id: <200011070334.WAA06752@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
cc: Scott Brim <sbrim@cisco.com>, Bob Braden <braden@ISI.EDU>, ietf@ietf.org
Subject: Re: Bake-off as trademark 
In-reply-to: Your message of "Mon, 06 Nov 2000 17:57:40 EST."
             <3A073764.51898752@cs.columbia.edu> 
Date: Mon, 06 Nov 2000 22:34:18 -0500
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Pillsbury sent Columbia University a cease-and-desist letter, indeed,
> presumably because of http://www.cs.columbia.edu/sip/bakeoff

maybe we should organize a boycott of Pillsbury then.  it would be 
worth it just for the symbol - a dough-boy with a red circle-slash 
through him.

let's stamp out intellectual property lawyers in our lifetime.

Keith



From owner-ietf-outbound  Mon Nov  6 22:50:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA24466
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 22:50:04 -0500 (EST)
Received: from zrtps06s.us.nortel.com ([47.140.48.50])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA23745
	for <ietf@ietf.org>; Mon, 6 Nov 2000 22:48:20 -0500 (EST)
Received: from zmers013 (actually zmers013.ca.nortel.com) 
          by zrtps06s.us.nortel.com; Mon, 6 Nov 2000 16:03:34 -0500
Received: from rftzy230.ca.nortel.com by zmers013;
          Mon, 6 Nov 2000 16:01:24 -0500
Received: from NORTELNETWORKS.COM (wftzh00e.ca.nortel.com [47.130.116.9]) 
          by rftzy230.ca.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.39) 
          id W1DZZN7G; Mon, 6 Nov 2000 16:00:33 -0500
Sender: "Marcus Leech" <mleech@nortelnetworks.com>
Message-ID: <3A071BF1.25049B2A@NORTELNETWORKS.COM>
Date: Mon, 06 Nov 2000 16:00:33 -0500
From: "Marcus Leech" <mleech@nortelnetworks.com>
X-Mailer: Mozilla 4.73C-CCK-MCD [en] (X11; U; HP-UX B.10.20 9000/785)
X-Accept-Language: en
MIME-Version: 1.0
To: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
CC: ietf@ietf.org
Subject: Re: Bake-off as trademark
References: <3A071135.38F7B7D8@cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Orig: <mleech@americasm97.nt.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

"Henning G. Schulzrinne" wrote:
> 
> I've been approached regarding the use of the (claimed-to-be)
> trademarked term bake-off. It would be helpful if somebody can provide
> credible evidence that this term has been used within the technical
> community for many years. (In case you didn't know,
> http://www.bakeoff.com/ shows the non-technical use....)
> 
> Thank you.
It wouldn't matter if we'd been using the term since only last Wednesday.
  Most trademark systems that I'm aware of share a doctrine of separation
  of intended audience.  So the word "bake-off" in the technical
  "market" of the Internet community is entirely seperate from the
  "market" of Pillsbury pastry products.

-- 
----------------------------------------------------------------------
Marcus Leech                             Mail:   Dept 8M70, MS 012, FITZ
Advisor                                  Phone: (ESN) 393-9145  +1 613 763 9145
Security Architecture and Planning       Fax:   (ESN) 393-9435  +1 613 763 9435
Nortel Networks                          mleech@nortelnetworks.com
-----------------Expressed opinions are my own, not my employer's------



From owner-ietf-outbound  Mon Nov  6 23:10:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA03332
	for ietf-outbound.10@ietf.org; Mon, 6 Nov 2000 23:10:04 -0500 (EST)
Received: from smtp-out1.bellatlantic.net ([199.45.39.156])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA01424
	for <ietf@ietf.org>; Mon, 6 Nov 2000 23:05:25 -0500 (EST)
Received: from cs.columbia.edu (adsl-151-198-20-48.nnj.adsl.bellatlantic.net [151.198.20.48])
	by smtp-out1.bellatlantic.net (8.9.1/8.9.1) with ESMTP id XAA29533
	for <ietf@ietf.org>; Mon, 6 Nov 2000 23:05:20 -0500 (EST)
Message-ID: <3A077F75.D9F8D55A@cs.columbia.edu>
Date: Mon, 06 Nov 2000 23:05:09 -0500
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD BA45DSL  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: More on bake-offs and trademarks
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

"Just because you're paranoid doesn't mean they are not after you... "
Apparently, Pillsbury is on a bigger crusade, as the editorial change at
http://cacheoff.ircache.net/ is indeed due to lawyer pressure, based on
reports from the owners of the site.



From owner-ietf-outbound  Tue Nov  7 03:20:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA24745
	for ietf-outbound.10@ietf.org; Tue, 7 Nov 2000 03:20:03 -0500 (EST)
Received: from bells.cs.ucl.ac.uk ([128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA22422
	for <ietf@ietf.org>; Tue, 7 Nov 2000 03:14:47 -0500 (EST)
Received: from hocus.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.03264-0@bells.cs.ucl.ac.uk>; Tue, 7 Nov 2000 08:14:40 +0000
To: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
cc: ietf@ietf.org
Subject: Re: More on bake-offs and trademarks
In-reply-to: Your message of "Mon, 06 Nov 2000 23:05:09 EST." <3A077F75.D9F8D55A@cs.columbia.edu>
Date: Tue, 07 Nov 2000 08:14:39 +0000
Message-ID: <7751.973584879@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <3A077F75.D9F8D55A@cs.columbia.edu>, Henning Schulzrinne typed:

 >>"Just because you're paranoid doesn't mean they are not after you... "
 >>Apparently, Pillsbury is on a bigger crusade, as the editorial change at
 >>http://cacheoff.ircache.net/ is indeed due to lawyer pressure, based on
 >>reports from the owners of the site.
 >>

an earliesh ref is below.....

if (as i assume) they are referrng to 19th century pie competitions
between people at county fairs, i think they have a problem coz that
means its a word in common use and not a trademark

 cheers

   jon
---------------------------------

11-Feb-88 18:46:52-PST,1331;000000000000M
Received: from UDEL.EDU by SRI-NIC.ARPA with TCP; Thu 11 Feb 88
18:40:35-PSTM
Received: from huey.udel.edu by Louie.UDEL.EDU id aa04152; 11 Feb 88
21:35 ESTM
Date:     Thu, 11 Feb 88 21:33:49 ESTM
From:     Mills@UDEL.EDUM
To:       Hal Peterson <hrp%windsor.CRAY.COM@uc.msc.umn.edu>M
cc:       Mills@UDEL.EDU, kleonard@burdvax.prc.unisys.com, M
          bobj@mcl.unisys.com, dcmartin@protolaba.arpa,
tcp-ip@sri-nic.arpaM
Subject:  Re:  Life in the Swamps / TestingM
Message-ID:  <8802112133.aa06023@Huey.UDEL.EDU>M
M
Hal,M
M
Once upon a time Vint Cerf was keeper of the alligators and even Bob
BradenM
collected a few. I've got a backyard full of the critters myself.
However,M
the point of my remark was that we don't need to invent bizarre test
suites,M
just how well it works in the current environment. What may be more
usefulM
for you would be to find out what the current environment really is
(lossM
rates, mangle angles, quench characteristiccs, etc., then build a
flakewayM
(broken network simulator) with similar characteristics and do war
with it.M
That's in fact how we did the initial IP testing (with credit to Bob
Braden)M
in the bakeoffs of antiquity.M
M
I'll rephrase my homily: We have met the enemy and he is us. Now you
mayM
understand my preocupation with swamps. Pass the stogies, Albert.M
M
DaveM



From owner-ietf-outbound  Tue Nov  7 10:00:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA12385
	for ietf-outbound.10@ietf.org; Tue, 7 Nov 2000 10:00:02 -0500 (EST)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10554
	for <ietf@ietf.org>; Tue, 7 Nov 2000 09:56:23 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eA7Ewve06520
	for <ietf@ietf.org>; Tue, 7 Nov 2000 09:58:58 -0500
Sender: francis@localhost.localdomain
Message-ID: <3A080B23.73F0B9F8@ecal.com>
Date: Tue, 07 Nov 2000 09:01:07 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586)
X-Accept-Language: en, de, es
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Bake-off as trademark
References: <4.3.2.7.2.20001106173723.00ae05b0@airborne.cisco.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

Scott Brim wrote:

> At 09:22 PM 11/06/2000 +0000, Bob Braden wrote:
> >Henning,
> >
> >Please see RFC 1025 from Sept 1987, or IEN 160 (online at
> >the RFC Editor web site) for a November 1980 bake off.
> >Is this 20 years ago early enough?
>
> Since the first Pillsbury Bake-Off was 50 years ago, no.

Well, but if they've failed to defend their trademark for 20 years, maybe
they've lost it.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Any sufficiently rigged demo is              |
|francis@ecal.com|indistinguishable from advanced technology.  |
\==============================================================/






From owner-ietf-outbound  Tue Nov  7 13:00:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA02131
	for ietf-outbound.10@ietf.org; Tue, 7 Nov 2000 13:00:02 -0500 (EST)
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA00575
	for <ietf@ietf.org>; Tue, 7 Nov 2000 12:56:31 -0500 (EST)
Received: from [165.227.249.17] (ip17.proper.com [165.227.249.17])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA17867
	for <ietf@ietf.org>; Tue, 7 Nov 2000 09:49:36 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05010465b62df15ea4d8@[165.227.249.17]>
In-Reply-To: <3A080B23.73F0B9F8@ecal.com>
References: <4.3.2.7.2.20001106173723.00ae05b0@airborne.cisco.com>
 <3A080B23.73F0B9F8@ecal.com>
Date: Tue, 7 Nov 2000 09:56:25 -0800
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@IMC.ORG>
Subject: Re: Bake-off as trademark
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

OK, we have now reached >20 messages from armchair lawyers on 
trademark law. Given the earlier threads this year from armchair 
lawyers on patents, that leaves us just two months for us to have a 
ponderous thread on trade secrets, and we will have covered the main 
parts of intellectual property law.

For 2001, I propose that we have at least one long thread with our 
expert opinions on international law, given that the IETF is a global 
community.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf-outbound  Tue Nov  7 13:20:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA08904
	for ietf-outbound.10@ietf.org; Tue, 7 Nov 2000 13:20:05 -0500 (EST)
Received: from breakaway.Stanford.EDU (breakaway.Stanford.EDU [171.64.20.202])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA07051
	for <ietf@ietf.org>; Tue, 7 Nov 2000 13:14:34 -0500 (EST)
Received: from localhost (hodges@localhost)
	by breakaway.Stanford.EDU (8.9.3/8.9.3) with ESMTP id KAA11764;
	Tue, 7 Nov 2000 10:14:34 -0800 (PST)
Message-Id: <200011071814.KAA11764@breakaway.Stanford.EDU>
X-Mailer: exmh version 2.0.2 2/24/98
Subject: Is there a URL for the Pillsbury "bake-off" cease-and-desist letter?
From: Jeff.Hodges@kingsmountain.com
To: ietf@ietf.org
cc: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Date: Tue, 07 Nov 2000 10:14:33 -0800
Sender: hodges@breakaway.Stanford.EDU
X-Loop: ietf@ietf.org

thanks,

JeffH




From owner-ietf-outbound  Wed Nov  8 01:20:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA00899
	for ietf-outbound.10@ietf.org; Wed, 8 Nov 2000 01:20:06 -0500 (EST)
Received: from indigo.acceleratednetworks.soft.net ([164.164.79.6])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA29214
	for <ietf@ietf.org>; Wed, 8 Nov 2000 01:17:32 -0500 (EST)
Received: by INDIGO with Internet Mail Service (5.5.2650.21)
	id <WA65J3S8>; Wed, 8 Nov 2000 11:47:16 +0530
Message-ID: <D9AEFD5D4D90D41181AB00508BCDF0E701085E@INDIGO>
From: Raghavendra Rao <raghavendra@acceleratednetworks.soft.net>
To: ietf@ietf.org
Subject: RFC 2327 extensions - draft document
Date: Wed, 8 Nov 2000 11:47:13 +0530 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop: ietf@ietf.org

Hi,

	Need to know how the IETF draft document on 
		"extensions to RFC 2327 for use in ATM base network" may be
accessed.

	The URL:://Draft-ietf-megaco-sdp-atm-00.txt is no longer accessible.

Thanks in adv,
Ragahvendra

Do not go where the path may lead, go instead where there is no path and
leave a trail. -Ralph Waldo Emerson





From owner-ietf-outbound  Wed Nov  8 02:50:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA29197
	for ietf-outbound.10@ietf.org; Wed, 8 Nov 2000 02:50:03 -0500 (EST)
Received: from breakaway.Stanford.EDU (breakaway.Stanford.EDU [171.64.20.202])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA27009
	for <ietf@ietf.org>; Wed, 8 Nov 2000 02:45:51 -0500 (EST)
Received: from localhost (hodges@localhost)
	by breakaway.Stanford.EDU (8.9.3/8.9.3) with ESMTP id XAA17482
	for <ietf@ietf.org>; Tue, 7 Nov 2000 23:45:51 -0800 (PST)
Message-Id: <200011080745.XAA17482@breakaway.Stanford.EDU>
X-Mailer: exmh version 2.0.2 2/24/98
Subject: why specify on-the-wire protocols?
To: ietf@ietf.org
From: Jeff.Hodges@kingsmountain.com
Reply-to: ietf@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 07 Nov 2000 23:45:51 -0800
Sender: hodges@breakaway.Stanford.EDU
X-Loop: ietf@ietf.org

"So why," I am asked from time-to-time, "should we bother thoroughly 
specifying on-the-wire protocols? Why isn't just having the app (or whatever) 
open a socket to the other machine and schlep bytes over to it good enough? 
Why isn't it good enough to hide the protocol behind an API and only think 
about this protocol stuff in terms of APIs?"

Examples of this are various apps or chunks of middleware which are built in a 
given environment and on a given (set of) platform(s). Often, it seems, the 
"protocols" aren't designed per se, rather APIs are designed and some common 
technique (perhaps one that's a feature of the environment this is being done 
within, e.g. SUN ONC RPC) is used "under the hood" of the API to actually get 
bits across the wire in a coherent fashion, but the on-the-wire protocol per 
se is (often) never designed and/or documented as such (in these situations).

Most everyone on this list "gets" why we (the IETF community) design and 
document protocols from an on-the-wire perspective --  but I can't seem to 
find it concisely written down anywhere.

What I'm looking for is existing documents that concisely explain this 
reasoning (so I can use 'em when trying to answer the above class of 
questions).

E.g. I've been trying to RTFM and have looked at..

  Architectural Principles of the Internet
  http://www.ietf.org/rfc/rfc1958.txt

  The Design Philosophy of the DARPA Internet Protocols.
  D.D.Clark, Proc SIGCOMM 88, ACM CCR Vol 18, Number 4, August 1988.
  http://netweb.usc.edu/cs551f00/papers/Clark.pdf

  End-To-End Arguments in System Design. J.H. Saltzer,
  D.P.Reed, D.D.Clark, ACM TOCS, Vol 2, Number 4, November 1984.
  http://www.reed.com/Papers/EndtoEnd.html

  Stacks: Interoperability in Today's Comuter Networks.
  Carl Malamud, 1992.

  Computer Networks. Andrew Tanenbaum, 1981 (yes, my bookshelf is dusty).

  Internetworking with TCP/IP: Principles, Protocols, and Architecture.
  Douglas Comer, 1988.


..plus poked about in http://www.ietf.org/ and with http//google.com/, and yet 
I haven't been able to find a paper, book, or whatever that clearly and
concisely says something like..

  "when designing computer-to-computer network communications, it behooves 
   the designers to do so from an on-the-wire protocol perspective, because
   blah, blah, blah..."


[true story: while I was researching/writing this, someone dropped by to ask 
some questions w.r.t. an "industry leading" vendor's authentication server. We 
were discussing communication between the server and code running on another 
node, and I said something like "..and so one uses some protocol to talk with 
the server, right?", and he says "Right, they've defined an API that you 
call." and gives me an otherwise blank look.  ~sigh~ ]


Now, Comer does come pretty close with this bit in section 1.3 of the 
above-referenced book..

  Much of our discussion of services will focus on standards called 
  "protocols". Protocols, like TCP/IP, give the formulas for passing messages, 
  specify the details of message formats, and describe how to handle error 
  conditions. Most important, they allow us to discuss communication standards 
  independent of any particular vendor's network hardware. In a sense, 
  protocols are to communication what programming languages are to 
computation.
  A programming language allows one to specify or understand computation 
  without knowing the details of any particular CPU instruction set. 
Similarly,
  a communication protocol allows one to specify or understand data 
  communication without depending on a detailed knowledge of a particular 
  vendor's network hardware. 


..and I do like his analogy of protocols as compared to (higher than assembly) 
programming languages. But I guess I'm looking for something more fleshed out 
and focused on this point.

Anyone have any ideas and/or relevant pointers?

thanks,

JeffH

ps: I note that RFC 1983 has a nice concise definition for "protocol". 





From owner-ietf-outbound  Wed Nov  8 21:00:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA09399
	for ietf-outbound.10@ietf.org; Wed, 8 Nov 2000 21:00:03 -0500 (EST)
Received: from trebuchet.rc.vix.com ([204.152.187.68])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA08122
	for <ietf@ietf.org>; Wed, 8 Nov 2000 20:54:18 -0500 (EST)
Received: (from gson@localhost)
	by trebuchet.rc.vix.com (8.11.0/8.8.8) id eA91rjf17163;
	Wed, 8 Nov 2000 17:53:45 -0800 (PST)
Date: Wed, 8 Nov 2000 17:53:45 -0800 (PST)
Message-Id: <200011090153.eA91rjf17163@trebuchet.rc.vix.com>
From: Andreas Gustafsson <gson@nominum.com>
To: ietf@ietf.org
Subject: Social event registration security
X-Loop: ietf@ietf.org

Looks like the IETF49 Social Event and LAN Card Registration Page at
<http://www2.eventreg.com/ietf_reg/ietf_reg.html> will send your
credit card number over the net unencrypted.  Could someone fix this,
please?
-- 
Andreas Gustafsson, gson@nominum.com



From owner-ietf-outbound  Thu Nov  9 08:00:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA14101
	for ietf-outbound.10@ietf.org; Thu, 9 Nov 2000 08:00:03 -0500 (EST)
Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA09110
	for <ietf@ietf.org>; Thu, 9 Nov 2000 07:45:07 -0500 (EST)
Received: from aswathi.india.hp.com (aswathi.india.hp.com [15.10.43.124])
	by palrel3.hp.com (Postfix) with ESMTP id BFF09976
	for <ietf@ietf.org>; Thu,  9 Nov 2000 04:45:05 -0800 (PST)
Received: from india.hp.com (aswathi.india.hp.com [15.10.43.124]) by aswathi.india.hp.com with ESMTP (8.7.1/8.7.3 SMKit7.02) id SAA22476 for <ietf@ietf.org>; Thu, 9 Nov 2000 18:06:57 +0530 (IST)
Sender: ramanan@india.hp.com
Message-ID: <3A0A9A68.A8C7B360@india.hp.com>
Date: Thu, 09 Nov 2000 18:06:57 +0530
From: Ramanan <ramanan@india.hp.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; HP-UX B.10.20 9000/712)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: IPv6 address formats (rfc1884)
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 want  some clarification on ip(v6) address representation.

  How do we treat the following addresses? Are they valid or
  otherwise?

  1:2:3:4:5:6::7:8
  ::1:2:3:4:5:6:7:8

  0:0:0:0:0:0:1.2.3.4
  0::0:0:0:0:0:1.2.3.4

  0:0:0:0:0:ffff:1.2.3.4
  0::0:0:0:0:ffff:1.2.3.4

  The rfc does not state if these are allowed.

  This clarification is important as some user scripts might
  generate such ip addresses.

  An analogy I found is that most unix versions treat
        /home/./ftp
  same as
        /home/ftp

  please getback to me suggestions?


Ramanan





From owner-ietf-outbound  Thu Nov  9 10:10:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02708
	for ietf-outbound.10@ietf.org; Thu, 9 Nov 2000 10:10:04 -0500 (EST)
Received: from smtprch1.nortel.com ([192.135.215.14])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA29890
	for <ietf@ietf.org>; Thu, 9 Nov 2000 10:04:19 -0500 (EST)
Received: from zrchb213.us.nortel.com (actually zrchb213) 
          by smtprch1.nortel.com; Thu, 9 Nov 2000 08:52:32 -0600
Received: by zrchb213.us.nortel.com with Internet Mail Service (5.5.2652.35) 
          id <WM1DZ5B0>; Thu, 9 Nov 2000 08:52:25 -0600
Message-ID: <61265F35C3FCD31199EF08002BC4B41302234874@ztcfd000.ca.nortel.com>
From: "Ron Evanoff" <revanoff@nortelnetworks.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Bluetooth MIB
Date: Thu, 9 Nov 2000 08:52:06 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.35)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C04A5C.A0EE91D0"
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_01C04A5C.A0EE91D0
Content-Type: text/plain;
	charset="iso-8859-1"

Hello,

IANA suggested that I send you this question. Are you aware of anyone that
has created or is creating a Bluetooth MIB? 

Best regards, 
Ron Evanoff


------_=_NextPart_001_01C04A5C.A0EE91D0
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.2652.35">
<TITLE>Bluetooth MIB</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">IANA suggested that I send you this =
question.</FONT><FONT SIZE=3D2 FACE=3D"Arial"> Are you aware of anyone =
that has created or is creating a Bluetooth MIB? </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Best regards, </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Ron Evanoff</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C04A5C.A0EE91D0--



From owner-ietf-outbound  Thu Nov  9 17:30:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA00887
	for ietf-outbound.10@ietf.org; Thu, 9 Nov 2000 17:30:02 -0500 (EST)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA28265
	for <ietf@ietf.org>; Thu, 9 Nov 2000 17:19:13 -0500 (EST)
Received: from mira-sjcd-1.cisco.com (mira-sjcd-1.cisco.com [171.69.43.44])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA19732;
	Thu, 9 Nov 2000 14:18:48 -0800 (PST)
Received: from ckaekel-lap (ckaekel-lap.cisco.com [171.68.134.178])
	by mira-sjcd-1.cisco.com (Mirapoint)
	with SMTP id AAA16947;
	Thu, 9 Nov 2000 14:18:44 -0800 (PST)
Message-Id: <4.1.20001109141835.00a1af00@mira-sjcd-1.cisco.com>
X-Sender: ckaekel@mira-sjcd-1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 09 Nov 2000 14:19:05 -0800
To: Ramanan <ramanan@india.hp.com>
From: Chuck Kaekel <ckaekel@cisco.com>
Subject: Re: IPv6 address formats (rfc1884)
Cc: ietf@ietf.org
In-Reply-To: <3A0A9A68.A8C7B360@india.hp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

See RFC 2373

At 06:06 PM 11/9/00 +0530, Ramanan wrote:
>  I want  some clarification on ip(v6) address representation.
>
>  How do we treat the following addresses? Are they valid or
>  otherwise?
>
>  1:2:3:4:5:6::7:8
>  ::1:2:3:4:5:6:7:8
>
>  0:0:0:0:0:0:1.2.3.4
>  0::0:0:0:0:0:1.2.3.4
>
>  0:0:0:0:0:ffff:1.2.3.4
>  0::0:0:0:0:ffff:1.2.3.4
>
>  The rfc does not state if these are allowed.
>
>  This clarification is important as some user scripts might
>  generate such ip addresses.
>
>  An analogy I found is that most unix versions treat
>        /home/./ftp
>  same as
>        /home/ftp
>
>  please getback to me suggestions?
>
>
>Ramanan
>
>


Chuck Kaekel
ckaekel@cisco.com



From owner-ietf-outbound  Fri Nov 10 22:20:58 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA09480
	for ietf-outbound.10@ietf.org; Fri, 10 Nov 2000 22:20:01 -0500 (EST)
Received: from shell9.ba.best.com (root@[206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA08844
	for <ietf@ietf.org>; Fri, 10 Nov 2000 22:17:10 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id TAA01900;
	Fri, 10 Nov 2000 19:16:54 -0800 (PST)
Date: Fri, 10 Nov 2000 19:16:54 -0800 (PST)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200011110316.TAA01900@shell9.ba.best.com>
To: vpim@lists.neystadt.org
Subject: Active Voice's products: VPIM or something similar?
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

Does anyone know if Active Voice supports Internet standards?
This quote is interesting:

"... future versions of Unity will support Audio Messaging
Interchange Specification (AMIS) as well as Voice Profile for 
Internet Mail (VPIM)...."

  --  http://www.activevoice.com/custom/press/pk/pdfs/nareport.pdf

What is AMIS, other than an unfortunate choice of acronym initials? 

Active Voice looks like another TAPI vendor.  Is there a reference 
implementation of VPIM on TAPI?

If not, and someone wants to make one, here are the docs:

  http://msdn.microsoft.com/library/psdk/tapi22/quickref_1pnp.htm
  http://msdn.microsoft.com/library/psdk/tapi3/tapiovr1_7juf.htm
  http://msdn.microsoft.com/library/psdk/tapi22/intro_2khj.htm
  http://msdn.microsoft.com/library/psdk/tapi22/quickref_1okl.htm
  http://msdn.microsoft.com/library/psdk/tapi22/func1_8rub.htm
  http://msdn.microsoft.com/library/psdk/tapi22/quickref_2eud.htm
  http://msdn.microsoft.com/library/psdk/tapi3/tapiovr1_4zxw.htm
  http://msdn.microsoft.com/library/psdk/tapi3/tspmsp_68mv.htm

This example code claims to make "complete" use of TAPI, but in 
fact it avoids use of the MS-WAVE interface, e.g., waveInOpen() 
and associated asyncronous usually-C buffer-based audio I/O calls, 
which would be necessary for a TAPI VPIM implementation:

  http://www.shrinkwrapvb.com/vbtapi.htm

Another technical introduction might be the Microsoft TAPI browser, 
e.g., TB20.EXE, which can put much of TAPI v.2 through its paces.

As usual, I'd be happy with something that could send an Audio/L16
;rate=11025 file as a base64 MIME attachment to a standard Internet 
message, but VPIM is more well thought out and usually less of a 
spool-buster.

Cheers,
James



From owner-ietf-outbound  Sat Nov 11 12:31:04 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA05105
	for ietf-outbound.10@ietf.org; Sat, 11 Nov 2000 12:30:04 -0500 (EST)
Received: from trampoline.thunk.org (IDENT:root@[216.175.175.172])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA03567
	for <ietf@ietf.org>; Sat, 11 Nov 2000 12:22:48 -0500 (EST)
From: tytso@mit.edu
Received: (from tytso@localhost)
	by trampoline.thunk.org (8.11.0/8.11.0) id eABIMdW05598;
	Sat, 11 Nov 2000 13:22:39 -0500
Date: Sat, 11 Nov 2000 13:22:39 -0500
Message-Id: <200011111822.eABIMdW05598@trampoline.thunk.org>
X-Authentication-Warning: trampoline.thunk.org: tytso set sender to tytso@mit.edu using -f
To: gson@nominum.com
CC: ietf@ietf.org
In-reply-to: <200011090153.eA91rjf17163@trebuchet.rc.vix.com> (message from
	Andreas Gustafsson on Wed, 8 Nov 2000 17:53:45 -0800 (PST))
Subject: Re: Social event registration security
Phone: (781) 391-3464
References:  <200011090153.eA91rjf17163@trebuchet.rc.vix.com>
X-Loop: ietf@ietf.org

   Date: Wed, 8 Nov 2000 17:53:45 -0800 (PST)
   From: Andreas Gustafsson <gson@nominum.com>

   Looks like the IETF49 Social Event and LAN Card Registration Page at
   <http://www2.eventreg.com/ietf_reg/ietf_reg.html> will send your
   credit card number over the net unencrypted.  Could someone fix this,
   please?

Upon further investigation, there doesn't appear to be a non-web
alternative for registration.  

Also, if you go to the top-level page at www2.eventreg.com, you'll find
the default Microsoft IIS page, complete with "sample pages and
application ideas" and "sample site" links.  If you go to the sample
database link, you can "click here" to create a database for the sample
applications.

Hmm..... This isn't calculated to give me a warm and fuzzy feeling about
the time spent by whoever set up this Windows NT server.  I wonder if it
has the latest security patches applied?  I wonder if it would be a good
idea to trust my credit card number to it?  (NOT.)

I guess I'll have to register on-site and forgo the T-shirt.  (Darn.
Like I needed Yet Another T-Shirt.  :-)

						- Ted

P.S.  Maybe someone from Cisco and Qualcomm can have a little chat with
whatever contractor set up the server?  I didn't do much prodding, but
I'd guess the chances are pretty high that there's some security
vulnerabilities left on that machine.



From owner-ietf-outbound  Tue Nov 14 15:11:01 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA14943
	for ietf-outbound.10@ietf.org; Tue, 14 Nov 2000 15:10:02 -0500 (EST)
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 SMTP id PAA13434
	for <ietf@ietf.org>; Tue, 14 Nov 2000 15:03:24 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id MAA00809;
	Tue, 14 Nov 2000 12:03:04 -0800 (PST)
Date: Tue, 14 Nov 2000 12:03:04 -0800 (PST)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200011142003.MAA00809@shell9.ba.best.com>
To: vpim@lists.neystadt.org
Subject: GSM 6.10 is public domain; audio/wav needs registered
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

Contrary to what people at VPIM meetings, lists, and on web pages 
have suggested, nobody owns any IPR on the GSM 06.10 vocodec format, 
or on any routines for encoding or decoding it.  It was developed 
from published code by people who took care to publish it before it 
could be monopolized.

Philips owns the rights to a related but different form of LPC, 
from U.S. patent 5,943,646, which was applied for more than four 
years after the publication of GSM 06.10 by ETSI.  That patent is 
most likely what is confusing people about the status.

Also,  http://www.ema.org/vpimdir/specs/draft-ema-vpim-wav-00.txt
-- the pending-in-limbo audio/wav IANA registration -- has an error:  
it reads "audio/vnd.wav"; that should be "audio/vnd.wave", which,  
by the way, hasn't been registered with IANA either.  I agree with 
Keith Moore that they should be registered as identical, and I hope
that they be registered in the same document to make that clearer.
The definitive reference for these formats seems to be kept in 
Microsoft's Support Knowledge Base Article ID Q120253:
  http://support.microsoft.com/support/kb/articles/Q120/2/53.asp

Cheers,
James



From owner-ietf-outbound  Wed Nov 15 13:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA17759
	for ietf-outbound.10@ietf.org; Wed, 15 Nov 2000 13:30:03 -0500 (EST)
Received: from mirapoint.mediagate.com (IDENT:mirapoint@mail.mediagate.com [207.88.19.194])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17486
	for <ietf@ietf.org>; Wed, 15 Nov 2000 13:29:28 -0500 (EST)
Received: from mediagate.com (cm2081384532.cableco-op.com [208.138.45.32])
	by mirapoint.mediagate.com (Mirapoint)
	with ESMTP id AAA64658 (AUTH jutta.degener);
	Wed, 15 Nov 2000 10:29:18 -0800 (PST)
Message-ID: <3A12D5D2.8BE13D30@mediagate.com>
Date: Wed, 15 Nov 2000 10:28:34 -0800
From: Jutta Degener <jutta@mediagate.com>
Organization: mediagate
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "James P. Salsman" <bovik@best.com>
CC: vpim@lists.neystadt.org, ietf@ietf.org
Subject: Re: [VPIM] GSM 6.10 is public domain; audio/wav needs registered
References: <200011142003.MAA00809@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

"James P. Salsman" wrote:
> Philips owns the rights to a related but different form of LPC, 
> from U.S. patent 5,943,646, which was applied for more than four 
> years after the publication of GSM 06.10 by ETSI.  That patent is 
> most likely what is confusing people about the status.

The patent I've seen investigated in connection with GSM 06.10
and Philips is the older 4,932,061 (1990), not 5,943,646.
4,932,061 does precede publication of GSM by two years.

Jutta Degener
<jutta@mediagate.com>



From owner-ietf-outbound  Wed Nov 15 19:02:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA25986
	for ietf-outbound.10@ietf.org; Wed, 15 Nov 2000 19:00:03 -0500 (EST)
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 SMTP id SAA23826
	for <ietf@ietf.org>; Wed, 15 Nov 2000 18:53:15 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id PAA09662;
	Wed, 15 Nov 2000 15:52:47 -0800 (PST)
Date: Wed, 15 Nov 2000 15:52:47 -0800 (PST)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200011152352.PAA09662@shell9.ba.best.com>
To: jutta@mediagate.com
Subject: Re: [VPIM] GSM 6.10 is public domain; audio/wav needs registered
Cc: ietf@ietf.org, vpim@lists.neystadt.org
In-Reply-To: <3A12D5D2.8BE13D30@mediagate.com>
X-Loop: ietf@ietf.org

Jutta,

Thanks for the information:

> The patent I've seen investigated in connection with GSM 06.10
> and Philips is the older 4,932,061 (1990)....

Interesting.  The priority date of that one is 22 March 1985.
The practice of quantizing residual exitation in LPC vocoders was 
not novel in 1985.  For an example of how people were performing 
VQ classification on the exitation residual much earlier, see:

"Epoch extraction from linear prediction residual for 
identification of closed glottis interval", by T. Ananthapadmanabha 
and B. Yegnanarayana,  in IEEE Transactions on Acoustics, Speech, 
and Signal Processing, vol. 27, no.4, pp. 309-19 (1979). 

Certainly the methods of doing such quantization described in the 
claims of patent 4,932,061 are novel, because they all explicitly 
refer to "perceptually weighting" the exitation residual.  However, 
GSM 6.10 uses only four quantization vectors and a linear scaling 
factor, without any weighting based on non-linear perceptual 
modeling, so that particular set of claims do not apply to GSM 6.10.

It also might be helpful to look at the references in the these 
GSM 6.10 descriptions published prior to ETSI's:

"Evolution of Six Medium Bit rate Coders For The Pan-European
Digital Mobile Radio System", by E. Natvig, in Journal On Selected
Areas In Communications, vol. 6, no. 2, pp 324-34 (1988).

"Speech Codec for the European Mobile Radio System", by K. Hellwig, 
P. Vary, D. Massaloux, and J.P. Petit, in Proceedings of the 
ICASSP-88, pp. 227 (April, 1988).

Cheers,
James



From owner-ietf-outbound  Wed Nov 15 19:10:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA29881
	for ietf-outbound.10@ietf.org; Wed, 15 Nov 2000 19:10:02 -0500 (EST)
Received: from rly-ip01.mx.aol.com (rly-ip01.mx.aol.com [205.188.156.49])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27778
	for <ietf@ietf.org>; Wed, 15 Nov 2000 19:04:24 -0500 (EST)
Received: from tot-we.proxy.aol.com (tot-we.proxy.aol.com [205.188.195.1])
	  by rly-ip01.mx.aol.com (8.8.8/8.8.8/AOL-5.0.0)
	  with ESMTP id TAA15835;
	  Wed, 15 Nov 2000 19:03:38 -0500 (EST)
Received: from eburger (AC83F318.ipt.aol.com [172.131.243.24])
	by tot-we.proxy.aol.com (8.10.0/8.10.0) with SMTP id eAG03aJ30598;
	Wed, 15 Nov 2000 19:03:36 -0500 (EST)
From: "Eric Burger" <eburger@snowshore.com>
To: <vpim@lists.neystadt.org>
Cc: <ietf@ietf.org>
Subject: RE: [VPIM] GSM 6.10 is public domain; audio/wav needs registered
Date: Thu, 16 Nov 2000 01:03:02 +0100
Message-ID: <NEBBLACLCLHMJBCAJGOEIEGNCBAA.eburger@snowshore.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.2911.0)
In-Reply-To: <200011152352.PAA09662@shell9.ba.best.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Apparently-From: Eburger3@aol.com
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

The question is not if there is any prior art.  The question is if any of
the primary claims in the Philips patent cover any aspect of GSM.  If not,
it doesn't matter.  If so...

U.S. law is peculiar when it comes to patents.  You are deemed to be
infringing UNLESS you can prove otherwise TO A COURT.  In addition, the
patent is deemed to be valid UNLESS you can prove otherwise TO A COURT.  The
prior art will help your case, but it won't avoid the lawsuit, if the patent
holder thinks they have a case.

The question is whether Philips thinks they have property rights to GSM.
Can't anyone with a big legal staff give them a call?  (C'mon Microsoft,
Lucent, Nortel... we know you know and we know they know you know, so it
won't be such a big deal to have your lawyers call Philips' lawyers...)

--
- Eric
[7 patents pending; 3 more in the works]


> -----Original Message-----
> From: owner-vpim@lists.neystadt.org
> [mailto:owner-vpim@lists.neystadt.org]On Behalf Of James P. Salsman
> Sent: Thursday, November 16, 2000 12:53 AM
> To: jutta@mediagate.com
> Cc: ietf@ietf.org; vpim@lists.neystadt.org
> Subject: Re: [VPIM] GSM 6.10 is public domain; audio/wav needs
> registered
>
>
> Jutta,
>
> Thanks for the information:
>
> > The patent I've seen investigated in connection with GSM 06.10
> > and Philips is the older 4,932,061 (1990)....
>
> Interesting.  The priority date of that one is 22 March 1985.
> The practice of quantizing residual exitation in LPC vocoders was
> not novel in 1985.  For an example of how people were performing
> VQ classification on the exitation residual much earlier, see:
>
> "Epoch extraction from linear prediction residual for
> identification of closed glottis interval", by T. Ananthapadmanabha
> and B. Yegnanarayana,  in IEEE Transactions on Acoustics, Speech,
> and Signal Processing, vol. 27, no.4, pp. 309-19 (1979).
>
> Certainly the methods of doing such quantization described in the
> claims of patent 4,932,061 are novel, because they all explicitly
> refer to "perceptually weighting" the exitation residual.  However,
> GSM 6.10 uses only four quantization vectors and a linear scaling
> factor, without any weighting based on non-linear perceptual
> modeling, so that particular set of claims do not apply to GSM 6.10.
>
> It also might be helpful to look at the references in the these
> GSM 6.10 descriptions published prior to ETSI's:
>
> "Evolution of Six Medium Bit rate Coders For The Pan-European
> Digital Mobile Radio System", by E. Natvig, in Journal On Selected
> Areas In Communications, vol. 6, no. 2, pp 324-34 (1988).
>
> "Speech Codec for the European Mobile Radio System", by K. Hellwig,
> P. Vary, D. Massaloux, and J.P. Petit, in Proceedings of the
> ICASSP-88, pp. 227 (April, 1988).
>
> Cheers,
> James
>
>



From owner-ietf-outbound  Thu Nov 16 13:30:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA19236
	for ietf-outbound.10@ietf.org; Thu, 16 Nov 2000 13:30:03 -0500 (EST)
Received: from smtprch2.nortel.com (smtprch2.nortelnetworks.com [192.135.215.15])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17328
	for <ietf@ietf.org>; Thu, 16 Nov 2000 13:25:29 -0500 (EST)
Received: from zrchb213.us.nortel.com (actually zrchb213) 
          by smtprch2.nortel.com; Thu, 16 Nov 2000 12:16:58 -0600
Received: by zrchb213.us.nortel.com with Internet Mail Service (5.5.2652.35) 
          id <W57YT185>; Thu, 16 Nov 2000 12:21:10 -0600
Message-ID: <488891341182D4118A870000F80822E782B700@zcard00p.ca.nortel.com>
From: "Glenn Parsons" <gparsons@nortelnetworks.com>
To: vpim@lists.neystadt.org
Cc: ietf@ietf.org
Subject: RE: [VPIM] GSM 6.10 is public domain; audio/wav needs registered
Date: Thu, 16 Nov 2000 12:21:02 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.35)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C04FF9.F9E50240"
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_01C04FF9.F9E50240
Content-Type: text/plain

FYI,

In the VPIM WG, for IVM we are interested in the MS-GSM codec.  It is
different enough from GSM 6.10 for Microsoft to hold a patent.

It is some sort of patent release statement (as well as an accurate
definition) from Microsoft on MG-GSM and WAVE (audio/wav) that we have been
waiting for.

Note that we have been waiting for a while and at the last meeting the
consensus was that G.711 (as in audio/basic) would be the alternative should
we decide that we have waited long enough.

Cheers,
Glenn.

> ----------
> From: 	James P. Salsman
> Sent: 	Tuesday, November 14, 2000 3:03 pm
> To: 	vpim@lists.neystadt.org
> Cc: 	ietf@ietf.org
> Subject: 	[VPIM] GSM 6.10 is public domain; audio/wav needs registered
> 
> Contrary to what people at VPIM meetings, lists, and on web pages 
> have suggested, nobody owns any IPR on the GSM 06.10 vocodec format, 
> or on any routines for encoding or decoding it.  It was developed 
> from published code by people who took care to publish it before it 
> could be monopolized.
> 
> Philips owns the rights to a related but different form of LPC, 
> from U.S. patent 5,943,646, which was applied for more than four 
> years after the publication of GSM 06.10 by ETSI.  That patent is 
> most likely what is confusing people about the status.
> 
> Also,  http://www.ema.org/vpimdir/specs/draft-ema-vpim-wav-00.txt
> -- the pending-in-limbo audio/wav IANA registration -- has an error:  
> it reads "audio/vnd.wav"; that should be "audio/vnd.wave", which,  
> by the way, hasn't been registered with IANA either.  I agree with 
> Keith Moore that they should be registered as identical, and I hope
> that they be registered in the same document to make that clearer.
> The definitive reference for these formats seems to be kept in 
> Microsoft's Support Knowledge Base Article ID Q120253:
>   http://support.microsoft.com/support/kb/articles/Q120/2/53.asp
> 
> Cheers,
> James
> 
> 
> 

------_=_NextPart_001_01C04FF9.F9E50240
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.2652.35">
<TITLE>RE: [VPIM] GSM 6.10 is public domain; audio/wav needs =
registered</TITLE>
</HEAD>
<BODY>

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

<P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">In the VPIM WG, for IVM we =
are interested in the MS-GSM codec.&nbsp; It is different enough from =
GSM 6.10 for Microsoft to hold a patent.</FONT></P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">It is some sort of patent =
release statement (as well as an accurate definition) from Microsoft on =
MG-GSM and WAVE (audio/wav) that we have been waiting for.</FONT></P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Note that we have been =
waiting for a while and at the last meeting the consensus was that =
G.711 (as in audio/basic) would be the alternative should we decide =
that we have waited long enough.</FONT></P>

<P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Cheers,</FONT>
<BR><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Glenn.</FONT>
</P>
<UL>
<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">James P. Salsman</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Geneva">Sent:</FONT></B> &nbsp; <FONT =
SIZE=3D2 FACE=3D"Geneva">Tuesday, November 14, 2000 3:03 pm</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Geneva">To:</FONT></B> &nbsp;&nbsp;&nbsp; =
<FONT SIZE=3D2 FACE=3D"Geneva">vpim@lists.neystadt.org</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Geneva">Cc:</FONT></B> &nbsp;&nbsp;&nbsp; =
<FONT SIZE=3D2 FACE=3D"Geneva">ietf@ietf.org</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Geneva">Subject:</FONT></B> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Geneva">[VPIM] GSM 6.10 is public domain; audio/wav needs =
registered</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Monaco">Contrary to what people at VPIM =
meetings, lists, and on web pages </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">have suggested, nobody owns any IPR =
on the GSM 06.10 vocodec format, </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">or on any routines for encoding or =
decoding it.&nbsp; It was developed </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">from published code by people who =
took care to publish it before it </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">could be monopolized.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Monaco">Philips owns the rights to a related =
but different form of LPC, </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">from U.S. patent 5,943,646, which =
was applied for more than four </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">years after the publication of GSM =
06.10 by ETSI.&nbsp; That patent is </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">most likely what is confusing people =
about the status.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Monaco">Also,&nbsp;</FONT><U> <FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Monaco"><A =
HREF=3D"http://www.ema.org/vpimdir/specs/draft-ema-vpim-wav-00.txt" =
TARGET=3D"_blank">http://www.ema.org/vpimdir/specs/draft-ema-vpim-wav-00=
.txt</A></FONT></U>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">-- the pending-in-limbo audio/wav =
IANA registration -- has an error:&nbsp; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">it reads &quot;audio/vnd.wav&quot;; =
that should be &quot;audio/vnd.wave&quot;, which,&nbsp; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">by the way, hasn't been registered =
with IANA either.&nbsp; I agree with </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">Keith Moore that they should be =
registered as identical, and I hope</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">that they be registered in the same =
document to make that clearer.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">The definitive reference for these =
formats seems to be kept in </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">Microsoft's Support Knowledge Base =
Article ID Q120253:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">&nbsp;</FONT><U> <FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Monaco"><A =
HREF=3D"http://support.microsoft.com/support/kb/articles/Q120/2/53.asp" =
TARGET=3D"_blank">http://support.microsoft.com/support/kb/articles/Q120/=
2/53.asp</A></FONT></U>
</P>

<P><FONT SIZE=3D2 FACE=3D"Monaco">Cheers,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Monaco">James</FONT>
</P>
<BR>
<BR>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C04FF9.F9E50240--



From owner-ietf-outbound  Thu Nov 16 17:30:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA20181
	for ietf-outbound.10@ietf.org; Thu, 16 Nov 2000 17:30:02 -0500 (EST)
Received: from mail.connectedsystems.com (host16.connectedsystems.com [205.227.183.113])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA16940
	for <ietf@ietf.org>; Thu, 16 Nov 2000 17:20:54 -0500 (EST)
Received: from software-caleb (red.hq.connsys.com [192.168.0.32]) by mail.connectedsystems.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id WMN2D6J3; Thu, 16 Nov 2000 14:18:04 -0800
From: "Caleb Clausen" <clausen@connsys.com>
To: "Glenn Parsons" <gparsons@nortelnetworks.com>
Date: Thu, 16 Nov 2000 14:22:30 -0800
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: RE: [VPIM] GSM 6.10 is public domain; audio/wav needs registered
CC: vpim@lists.neystadt.org, ietf@ietf.org
Message-ID: <3A13EDA6.14245.463EBB@localhost>
Priority: normal
In-reply-to: <488891341182D4118A870000F80822E782B700@zcard00p.ca.nortel.com>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Content-Transfer-Encoding: 7BIT
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7BIT

From:           	"Glenn Parsons" <gparsons@nortelnetworks.com>
> In the VPIM WG, for IVM we are interested in the MS-GSM codec.  It is
> different enough from GSM 6.10 for Microsoft to hold a patent.

do you know the patent number?  i could have sworn i had seen 
some such patent too, but now i can't find it.



"The battle 
 for mental territory 
            is glory. 
            End of story."
                           --KRS-ONE



From owner-ietf-outbound  Fri Nov 17 09:50:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA29644
	for ietf-outbound.10@ietf.org; Fri, 17 Nov 2000 09:50:03 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA27462
	for <ietf@ietf.org>; Fri, 17 Nov 2000 09:44:03 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id eAHEi0t20109
	for <ietf@ietf.org>; Fri, 17 Nov 2000 15:44:00 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Fri Nov 17 15:43:49 2000 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2651.58)
	id <XCK5VH65>; Fri, 17 Nov 2000 15:43:47 +0100
Message-ID: <0DAEDF148988D411BB980008C7E65D2E4B8B42@esealnt416>
From: "Amleset Kelati (EBC)" <Amleset.Kelati@EBC.ERICSSON.SE>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Radius client implementation
Date: Fri, 17 Nov 2000 15:43:45 +0100
Return-Receipt-To: "Amleset Kelati (EBC)" <Amleset.Kelati@ebc.ericsson.se>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Hi,

I am looking for existing standard on Radius client implementation.
Please indicate me where to get this information in order to use it for my project.
Thank you for your help.

Amleset



From owner-ietf-outbound  Fri Nov 17 13:20:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA00397
	for ietf-outbound.10@ietf.org; Fri, 17 Nov 2000 13:20:03 -0500 (EST)
Received: from uucp1.nwnexus.com (uucp1.nwnexus.com [206.63.63.110])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA29498
	for <ietf@ietf.org>; Fri, 17 Nov 2000 13:18:03 -0500 (EST)
Received: from internaut.com (uucp@localhost)
	by uucp1.nwnexus.com (8.8.8/8.8.8) with UUCP id KAA07624
	for ietf.org!ietf; Fri, 17 Nov 2000 10:18:04 -0800 (PST)
Received: from [64.38.134.109] by internaut.com (NX5.67e/NeXT-3.0)
	id AA00790; Fri, 17 Nov 00 10:37:03 -0800
From: "Bernard Aboba" <aboba@internaut.com>
To: <ietf@ietf.org>
Subject: ACTION REQUESTED: Call for nominations
Date: Fri, 17 Nov 2000 09:56:03 -0800
Message-Id: <OJEJKOMOEAKLMOILFCPJIEAPDKAA.aboba@internaut.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.50.4133.2400
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

The 2000 Nominations Committee is now
soliciting nominations for the open
slots on the IESG and IAB. 

Members of the community are encouraged to 
nominate candidates for any of the positions 
which are up for re-filling: 

IESG Terms ending in March, 2001: 

Fred Baker		IETF Chair
Scott Bradner	Transport
Randy Bush		Operations & Management
Patrik Faltstrom	Applications
Thomas Narten	Internet
Dave Oran		Routing
Jeff Schiller	Security

IAB Terms ending in March, 2001: 

Harald Alvestrand 
Ran Atkinson
Rob Austein
Steve Deering
Tony Hain 
Geoff Huston

Members of the community are encouraged to contact the
nomcom to nominate someone for any of these positions, 
to provide input relating to potential candidates,
or to provide comments regarding the past performance
of incumbents, which will be considered
during the deliberations of the nominating committee. 

Comments sent to the nominations committee will be
kept in confidence. As noted in RFC 2727 "all 
deliberations and supporting information that 
relates to specific nominees, candidates, 
and confirmed candidates are confidential." 

Self-nominations are accepted. The deadline for
nominations is midnight Monday, December 16, 2000. 
Early input is desirable so that candidates may be 
interviewed during IETF 49. 

The members of the NomCom can be contacted individually  at
the addresses below or collectively at nomcom@ietf.org.  
Additionally, the members of the NomCom will be identified 
at the IETF by a marker (as yet undetermined) on their name 
tags.  People are encouraged to take advantage of the 
opportunity to talk to the members of the NomCom about 
nominations and other issues related to the IAB and IESG 
membership. 

The 2000 Nominations Committee

Phil Roberts <qa3445@email.mot.com>
Stuart Cheshire <cheshire@apple.com>
Perry E. Metzger <perry@piermont.com>
Bill Woodcock <woody@zocalo.net>
Hadriel Kaplan <hadriel@nortelnetworks.com>
Alain Durand <alain.durand@eng.sun.com>
Vijay Srinivasan <vijay.srinivasan@cosinecom.com>
Hal Sandick <hsandick@nortelnetworks.com>
David Robinson <david.robinson@ebay.sun.com>
David Allan <dallan@nortelnetworks.com>

Non-voting members:
Bernard Aboba <aboba@internaut.com> (Chair)
Avri Doria <avri@nortelnetworks.com> (Past Chair)
Leslie Daigle <leslie@thinkingcat.com> (IAB liason)
Allison Mankin <mankin@isi.edu> (IESG liason)

The role of non-voting members (from RFC 2727)

The nominations committee comprises at least a non-voting 
Chair, 10 voting volunteers, and 3 non-voting liaisons.
The sitting IAB and IESG members each appoint a non-voting
liaison to the nominating committee from their current
membership who are not sitting in an open position.
The Chair of the prior year's nominating committee also 
serves as a non-voting liaison.







From owner-ietf-outbound  Mon Nov 20 02:53:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA02633
	for ietf-outbound.10@ietf.org; Mon, 20 Nov 2000 02:50:01 -0500 (EST)
Received: from telesoft.indts.com (PPP-174-99.bng.vsnl.net.in [203.197.174.99])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA02587
	for <ietf@ietf.org>; Mon, 20 Nov 2000 02:43:33 -0500 (EST)
Received: from babhishek ([201.64.64.198])
	by telesoft.indts.com (8.8.7/8.8.7) with SMTP id KAA24864
	for <ietf@ietf.org>; Mon, 20 Nov 2000 10:55:49 +0530
From: "abhishek" <abhishek@indts.com>
To: <ietf@ietf.org>
Subject: RFC 2705
Date: Mon, 20 Nov 2000 10:42:03 +0530
Message-ID: <NEBBIBMEGMNDIACHJAPAEEEPCCAA.abhishek@indts.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.2314.1300
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Hi there,
I was going through the RFC 2705 of the MGCP. I have a doubt. Suppose my
gateway is playing some signal at a specific endpoint and during that course
of action, I get another (notification request) signal to be applied at the
same endpoint (without getting a request to stop the previous signal). In
this case what should the gateway do?

(1) Should it stop the previous signal and play the new one?

(2) Should it ignore the new signal?

(3) Should it keep the new signal in a buffer and once the first signal is
over, it should apply the new signal? If so, are we maintaining the Master
Slave behaviour between Call agent and gateway? (For instance, the first
signal may be of a very long duration).


thanks and regards,

abhishek mishra

sr. software engineer
Ind-Telesoft Pvt Ltd.
Bangalore
(India) -560095



From owner-ietf-outbound  Mon Nov 20 07:00:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA06320
	for ietf-outbound.10@ietf.org; Mon, 20 Nov 2000 07:00:02 -0500 (EST)
Received: from web1103.mail.yahoo.com (web1103.mail.yahoo.com [128.11.23.123])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA06284
	for <ietf@ietf.org>; Mon, 20 Nov 2000 06:59:51 -0500 (EST)
Received: (qmail 23063 invoked by uid 60001); 20 Nov 2000 11:59:49 -0000
Message-ID: <20001120115949.23062.qmail@web1103.mail.yahoo.com>
Received: from [213.29.206.6] by web1103.mail.yahoo.com; Mon, 20 Nov 2000 03:59:49 PST
Date: Mon, 20 Nov 2000 03:59:49 -0800 (PST)
From: mohammad behdadfar <m_behdadfar@yahoo.com>
Subject: would you help me?
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

Hai,

I would like to get info on IP Packet classification
and filtering, can anybody help?

 Thanks

__________________________________________________
Do You Yahoo!?
Yahoo! Calendar - Get organized for the holidays!
http://calendar.yahoo.com/



From owner-ietf-outbound  Tue Nov 21 08:30:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA26192
	for ietf-outbound.10@ietf.org; Tue, 21 Nov 2000 08:30:02 -0500 (EST)
Received: from htt-consult.com ([63.82.18.210])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA25791
	for <ietf@ietf.org>; Tue, 21 Nov 2000 08:26:49 -0500 (EST)
Received: from rgm.htt-consult.com ([63.82.18.195]) by htt-consult.com ; Tue, 21 Nov 2000 08:29:20 -0500
Message-Id: <5.0.0.25.2.20001121082345.033910d0@homebase.htt-consult.com>
X-Sender: rgm-ietf@homebase.htt-consult.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Tue, 21 Nov 2000 08:28:59 -0500
To: ietf@ietf.org
From: Robert Moskowitz <rgm-ietf@htt-consult.com>
Subject: IETF 49 -- Porblems with LAN registration pages
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Warning for users of Netscape 6.0,

I can't seem to get the Wireless popup hot links to HDR or 822.11 to be 
clickable.

It works with Netscape 4.75 and IE 5.5

If you are using Netscape 6.0, and find this problem just select the social 
event.  It will get you to the registration form which allows either social 
and/or lan card registration.

Oh, and SSL security with 128bit keys is used for the registration form 
now.  The server cert is issued by RSA Data Security, Inc.

  



From owner-ietf-outbound  Tue Nov 21 15:00:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA14977
	for ietf-outbound.10@ietf.org; Tue, 21 Nov 2000 15:00:03 -0500 (EST)
Received: from uucp1.nwnexus.com (uucp1.nwnexus.com [206.63.63.110])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA13842
	for <ietf@ietf.org>; Tue, 21 Nov 2000 14:52:19 -0500 (EST)
Received: from internaut.com (uucp@localhost)
	by uucp1.nwnexus.com (8.8.8/8.8.8) with UUCP id LAA27665
	for ietf.org!ietf; Tue, 21 Nov 2000 11:52:19 -0800 (PST)
Received: from [64.38.134.109] by internaut.com (NX5.67e/NeXT-3.0)
	id AA01537; Tue, 21 Nov 00 12:21:25 -0800
From: "Bernard Aboba" <aboba@internaut.com>
To: <ietf@ietf.org>
Subject: 3rd notice: ACTION REQUESTED: Call for nominations
Date: Tue, 21 Nov 2000 11:41:48 -0800
Message-Id: <OJEJKOMOEAKLMOILFCPJEEGKDKAA.aboba@internaut.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)
Importance: Normal
X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

The 2000 Nominations Committee is now
soliciting nominations for the open
slots on the IESG and IAB. 

Members of the community are encouraged to 
nominate candidates for any of the positions 
which are up for re-filling: 

IESG Terms ending in March, 2001: 

Fred Baker		IETF Chair
Scott Bradner	Transport
Randy Bush		Operations & Management
Patrik Faltstrom	Applications
Thomas Narten	Internet
Dave Oran		Routing
Jeff Schiller	Security

IAB Terms ending in March, 2001: 

Harald Alvestrand 
Ran Atkinson
Rob Austein
Steve Deering
Tony Hain 
Geoff Huston

Members of the community are encouraged to contact the
nomcom to nominate someone for any of these positions, 
to provide input relating to potential candidates,
or to provide comments regarding the past performance
of incumbents, which will be considered
during the deliberations of the nominating committee. 

Comments sent to the nominations committee will be
kept in confidence. As noted in RFC 2727 "all 
deliberations and supporting information that 
relates to specific nominees, candidates, 
and confirmed candidates are confidential." 

Self-nominations are accepted. The deadline for
nominations is midnight Monday, December 16, 2000. 
Early input is desirable so that candidates may be 
interviewed during IETF 49. 

The members of the NomCom can be contacted individually  at
the addresses below or collectively at nomcom@ietf.org.  
Additionally, the members of the NomCom will be identified 
at the IETF by a marker (as yet undetermined) on their name 
tags.  People are encouraged to take advantage of the 
opportunity to talk to the members of the NomCom about 
nominations and other issues related to the IAB and IESG 
membership. 

The 2000 Nominations Committee

Phil Roberts <qa3445@email.mot.com>
Stuart Cheshire <cheshire@apple.com>
Perry E. Metzger <perry@piermont.com>
Bill Woodcock <woody@zocalo.net>
Hadriel Kaplan <hadriel@nortelnetworks.com>
Alain Durand <alain.durand@eng.sun.com>
Vijay Srinivasan <vijay.srinivasan@cosinecom.com>
Hal Sandick <hsandick@nortelnetworks.com>
David Robinson <david.robinson@ebay.sun.com>
David Allan <dallan@nortelnetworks.com>

Non-voting members:
Bernard Aboba <aboba@internaut.com> (Chair)
Avri Doria <avri@nortelnetworks.com> (Past Chair)
Leslie Daigle <leslie@thinkingcat.com> (IAB liason)
Allison Mankin <mankin@isi.edu> (IESG liason)

The role of non-voting members (from RFC 2727)

The nominations committee comprises at least a non-voting 
Chair, 10 voting volunteers, and 3 non-voting liaisons.
The sitting IAB and IESG members each appoint a non-voting
liaison to the nominating committee from their current
membership who are not sitting in an open position.
The Chair of the prior year's nominating committee also 
serves as a non-voting liaison.



From owner-ietf-outbound  Tue Nov 21 19:20:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA00815
	for ietf-outbound.10@ietf.org; Tue, 21 Nov 2000 19:20:03 -0500 (EST)
Received: from linux368.dn.net (systemserver.com [207.153.200.204] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA00162
	for <IETF@ietf.org>; Tue, 21 Nov 2000 19:15:10 -0500 (EST)
Received: (from nobody@localhost)
	by linux368.dn.net (8.9.3/8.9.1) id UAA17493
	for IETF@ietf.org; Tue, 21 Nov 2000 20:31:11 -0500
Date: Tue, 21 Nov 2000 20:31:11 -0500
Message-Id: <200011220131.UAA17493@linux368.dn.net>
To: IETF@ietf.org
From: reports@betterwhois.com (BetterWhois.com)
Subject: BetterWhois Search: iandi.com
X-Loop: ietf@ietf.org

[whois.crsnic.net]Whois Server Version 1.3Domain names in the .com, .net, and .org domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.   Domain Name: IANDI.COM
   Registrar: NETWORK SOLUTIONS, INC.
   Whois Server: whois.networksolutions.com
   Referral URL: www.networksolutions.com
   Name Server: NS1.GLOBAL-COMMONS.COM
   Name Server: NS3.GLOBAL-COMMONS.COM
   Name Server: NS2.GLOBAL-COMMONS.COM
   Updated Date: 25-nov-1999
The Registry database contains ONLY .COM, .NET, .ORG, .EDU domains and
Registrars.

[whois.networksolutions.com]
The Data in Network Solutions' WHOIS database is provided by Network
Solutions for information purposes, and to assist persons in obtaining
information about or related to a domain name registration record.
Network Solutions does not guarantee its accuracy.  By submitting a
WHOIS query, you agree that you will use this Data only for lawful
purposes and that, under no circumstances will you use this Data to:
(1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail
(spam); or  (2) enable high volume, automated, electronic processes
that apply to Network Solutions (or its systems).  Network Solutions
reserves the right to modify these terms at any time.  By submitting
this query, you agree to abide by this policy.

Registrant:
i & i Co.,Ltd. (IANDI-DOM)
   Adax Akasaka Bldg.
   2-13 Akasaka 4 chome
   Minato-ku, Tokyo
   Japan

   Domain Name: IANDI.COM

   Administrative Contact, Billing Contact:
      Tsubo, Toshihiro  (TT198)  hostmaster@GLOBAL-COMMONS.COM
      Global Commons, Inc.
      Sunrise Shinjuku 7F
      Okubo 2-4-15, Shinjuku-ku
      Tokyo 169
      JP
      +81-3-3204-8104
   Technical Contact:
      Domain Administrator  (DA9278-ORG)  dnsadmin@GLOBAL-COMMONS.COM
      Global Commons, Inc.
      Sunrise Shinjuku 7F
      Okubo 2-4-15, Shinjuku-ku
      Tokyo, 169
      JP
      972-881-9595 Fax- - 972-578-6045

   Record last updated on 08-Jan-1999.
   Record expires on 26-Nov-2000.
   Record created on 25-Nov-1995.
   Database last updated on 21-Nov-2000 14:48:50 EST.

   Domain servers in listed order:

   NS1.GLOBAL-COMMONS.COM	209.217.1.3
   NS2.GLOBAL-COMMONS.COM	207.240.44.3
   NS3.GLOBAL-COMMONS.COM	209.217.16.3


------------------------------------------------------------------
You received this message because you searched for a domain
on BetterWhois.com (http://www.betterwhois.com) and asked to
have the results e-mailed to you.
------------------------------------------------------------------



From owner-ietf-outbound  Thu Nov 23 17:33:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA00292
	for ietf-outbound.10@ietf.org; Thu, 23 Nov 2000 17:30:03 -0500 (EST)
Received: from uucp1.nwnexus.com (uucp1.nwnexus.com [206.63.63.110])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA24162
	for <ietf@ietf.org>; Thu, 23 Nov 2000 17:17:03 -0500 (EST)
Received: from internaut.com (uucp@localhost)
	by uucp1.nwnexus.com (8.8.8/8.8.8) with UUCP id OAA26280
	for ietf.org!ietf; Thu, 23 Nov 2000 14:17:04 -0800 (PST)
Received: from [64.38.134.109] by internaut.com (NX5.67e/NeXT-3.0)
	id AA01926; Thu, 23 Nov 00 14:49:33 -0800
From: "Bernard Aboba" <aboba@internaut.com>
To: <ietf@ietf.org>
Subject: ACTION REQUESTED: Call for nominations for IAB/IESG (4th request)
Date: Thu, 23 Nov 2000 14:10:05 -0800
Message-Id: <OJEJKOMOEAKLMOILFCPJOELPDKAA.aboba@internaut.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)
Importance: Normal
X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

The 2000 Nominations Committee is now
soliciting nominations for the open
slots on the IESG and IAB. 

Please take the time, even if it is
only a few moments, to send us your
thoughts. 

Members of the community are encouraged to 
nominate candidates for any of the positions 
which are up for re-filling: 

IESG Terms ending in March, 2001: 

Fred Baker		IETF Chair
Scott Bradner	Transport
Randy Bush		Operations & Management
Patrik Faltstrom	Applications
Thomas Narten	Internet
Dave Oran		Routing
Jeff Schiller	Security

IAB Terms ending in March, 2001: 

Harald Alvestrand 
Ran Atkinson
Rob Austein
Steve Deering
Tony Hain 
Geoff Huston

Members of the community are encouraged to contact the
nomcom to nominate someone for any of these positions, 
to provide input relating to potential candidates,
or to provide comments regarding the past performance
of incumbents, which will be considered
during the deliberations of the nominating committee. 

Comments sent to the nominations committee will be
kept in confidence. As noted in RFC 2727 "all 
deliberations and supporting information that 
relates to specific nominees, candidates, 
and confirmed candidates are confidential." 

Self-nominations are accepted. The deadline for
nominations is midnight Monday, December 18, 2000. 
Early input is desirable so that candidates may be 
interviewed during IETF 49. 

The members of the NomCom can be contacted individually  at
the addresses below or collectively at nomcom@ietf.org.  
Additionally, the members of the NomCom will be identified 
at the IETF by a marker (as yet undetermined) on their name 
tags.  People are encouraged to take advantage of the 
opportunity to talk to the members of the NomCom about 
nominations and other issues related to the IAB and IESG 
membership. 

The 2000 Nominations Committee

Phil Roberts <qa3445@email.mot.com>
Stuart Cheshire <cheshire@apple.com>
Perry E. Metzger <perry@piermont.com>
Bill Woodcock <woody@zocalo.net>
Hadriel Kaplan <hadriel@nortelnetworks.com>
Alain Durand <alain.durand@eng.sun.com>
Vijay Srinivasan <vijay.srinivasan@cosinecom.com>
Hal Sandick <hsandick@nortelnetworks.com>
David Robinson <david.robinson@ebay.sun.com>
David Allan <dallan@nortelnetworks.com>

Non-voting members:
Bernard Aboba <aboba@internaut.com> (Chair)
Avri Doria <avri@nortelnetworks.com> (Past Chair)
Leslie Daigle <leslie@thinkingcat.com> (IAB liason)
Allison Mankin <mankin@isi.edu> (IESG liason)

The role of non-voting members (from RFC 2727)

The nominations committee comprises at least a non-voting 
Chair, 10 voting volunteers, and 3 non-voting liaisons.
The sitting IAB and IESG members each appoint a non-voting
liaison to the nominating committee from their current
membership who are not sitting in an open position.
The Chair of the prior year's nominating committee also 
serves as a non-voting liaison.



From owner-ietf-outbound  Fri Nov 24 10:32:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08055
	for ietf-outbound.10@ietf.org; Fri, 24 Nov 2000 10:30:03 -0500 (EST)
Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA06796
	for <ietf@ietf.org>; Fri, 24 Nov 2000 10:24:29 -0500 (EST)
Received: from esebh11nok.ntc.nokia.com (esebh11nok.ntc.nokia.com [131.228.10.108])
	by mgw-x3.nokia.com (8.10.2/8.10.2/Nokia) with ESMTP id eAOFNHB16188
	for <ietf@ietf.org>; Fri, 24 Nov 2000 17:23:17 +0200 (EET)
Received: from news1.nokia.com ([131.228.6.98]) by esebh11nok.ntc.nokia.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.78)
	id X3402J7Q; Fri, 24 Nov 2000 17:23:17 +0200
Received: (from news@localhost)
	by news1.nokia.com (8.8.8+Sun/8.8.8) id RAA20134;
	Fri, 24 Nov 2000 17:22:40 +0200 (EET)
To: ietf@ietf.org
Path: not-for-mail
From: "John Loughney" <john.loughney@nokia.com>
Newsgroups: nokia.lists.ietf.general
Subject: Auto reply from IETF-Draft administrator
Lines: 11
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID: <3JvT5.15221$AM5.289256@news1.nokia.com>
Date: Fri, 24 Nov 2000 15:22:39 GMT
NNTP-Posting-Host: 172.21.41.213
X-Complaints-To: newsmaster@nokia.com
X-Trace: news1.nokia.com 975079359 172.21.41.213 (Fri, 24 Nov 2000 17:22:39 EET)
NNTP-Posting-Date: Fri, 24 Nov 2000 17:22:39 EET
Organization: Nokia
X-Loop: ietf@ietf.org

Hi all,

I'm not sure if this is the right place for this (probably it is), but I
just wanted to say that the autoreply from the IETF-drafts mailing list when
submitting a draft is a very nice thing.  I suggest that this is kept as a
feature.

best regards,
John



From owner-ietf-outbound  Sat Nov 25 20:21:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA18253
	for ietf-outbound.10@ietf.org; Sat, 25 Nov 2000 20:20:02 -0500 (EST)
Received: from linux368.dn.net (systemserver.com [207.153.200.204] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA17822
	for <IETF@ietf.org>; Sat, 25 Nov 2000 20:16:33 -0500 (EST)
Received: (from nobody@localhost)
	by linux368.dn.net (8.9.3/8.9.1) id VAA28123
	for IETF@ietf.org; Sat, 25 Nov 2000 21:32:29 -0500
Date: Sat, 25 Nov 2000 21:32:29 -0500
Message-Id: <200011260232.VAA28123@linux368.dn.net>
To: IETF@ietf.org
From: reports@betterwhois.com (BetterWhois.com)
Subject: BetterWhois Search: unitrendix.com
X-Loop: ietf@ietf.org

[whois.crsnic.net]Whois Server Version 1.3Domain names in the .com, .net, and .org domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.   Domain Name: UNITRENDIX.COM
   Registrar: NETWORK SOLUTIONS, INC.
   Whois Server: whois.networksolutions.com
   Referral URL: www.networksolutions.com
   Name Server: NS2.UNITRENDIX.COM
   Name Server: NS1.UNITRENDIX.COM
   Updated Date: 12-nov-2000
The Registry database contains ONLY .COM, .NET, .ORG, .EDU domains and
Registrars.

[whois.networksolutions.com]
The Data in Network Solutions' WHOIS database is provided by Network
Solutions for information purposes, and to assist persons in obtaining
information about or related to a domain name registration record.
Network Solutions does not guarantee its accuracy.  By submitting a
WHOIS query, you agree that you will use this Data only for lawful
purposes and that, under no circumstances will you use this Data to:
(1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail
(spam); or  (2) enable high volume, automated, electronic processes
that apply to Network Solutions (or its systems).  Network Solutions
reserves the right to modify these terms at any time.  By submitting
this query, you agree to abide by this policy.

Registrant:
Unitrendix Corporation (UNITRENDIX-DOM)
   23900 Hawthorne Blvd.
   Torrance, CA 90505  US

   Domain Name: UNITRENDIX.COM

   Administrative Contact:
      Unitrendix Administration  (UA25-ORG)  administration@UNITRENDIX.COM
      Unitrendix Corporation
      23900 Hawthorne Boulevard
      Torrance,, CA 90505
      US
      310-791-2320 Fax- 310-378-6049
   Technical Contact:
      Unitrendix Technical  (UT17-ORG)  networks@UNITRENDIX.COM
      Unitrendix Corporation
      23900 Hawthorne Boulevard
      Torrance,, CA 90505
      US
      310-791-2320 Fax- 310-378-6049
   Billing Contact:
      Unitrendix Billing  (UB12-ORG)  billing@UNITRENDIX.COM
      Unitrendix Corporation
      23900 Hawthorne Boulevard
      Torrance,, CA 90505
      US
      310-791-2320 Fax- 310-378-6049

   Record last updated on 23-Nov-2000.
   Record expires on 14-Nov-2001.
   Record created on 13-Nov-1995.
   Database last updated on 25-Nov-2000 16:53:17 EST.

   Domain servers in listed order:

   NS1.UNITRENDIX.COM		198.187.208.2
   NS2.UNITRENDIX.COM		207.124.196.50


------------------------------------------------------------------
You received this message because you searched for a domain
on BetterWhois.com (http://www.betterwhois.com) and asked to
have the results e-mailed to you.
------------------------------------------------------------------



From owner-ietf-outbound  Sun Nov 26 14:51:58 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA29185
	for ietf-outbound.10@ietf.org; Sun, 26 Nov 2000 14:50:03 -0500 (EST)
Received: from mx01-a.netapp.com ([198.95.226.53])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA27425
	for <ietf@ietf.org>; Sun, 26 Nov 2000 14:44:25 -0500 (EST)
Received: from frejya.corp.netapp.com (frejya.corp.netapp.com [10.10.20.91])
	by mx01-a.netapp.com (8.11.0/8.11.0/NTAP-1.0) with ESMTP id eAQJiVJ14563
	for <ietf@ietf.org>; Sun, 26 Nov 2000 11:44:39 -0800 (PST)
Received: from ussvlexc06.corp.netapp.com (localhost [127.0.0.1])
	by frejya.corp.netapp.com (8.11.0/8.11.0/NTAP-1.1) with ESMTP id eAQJhm825821
	for <ietf@ietf.org>; Sun, 26 Nov 2000 11:43:49 -0800 (PST)
Received: by ussvlexc06.corp.netapp.com with Internet Mail Service (5.5.2650.21)
	id <XJKT1VT3>; Sun, 26 Nov 2000 11:49:19 -0800
Message-ID: <B4353D108FA4D4118C3A00D0B782A4581039D5@ussvlexc07.corp.netapp.com>
From: "Skardal, Harald" <Harald.Skardal@netapp.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Network Data Management Protocol announcement
Date: Sun, 26 Nov 2000 11:48:48 -0800
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

This is an announcement of a new standards effort for NDMP,
Network Data Management Protocol, version 4. We are hoping to 
start up an NDMP effort under the IETF. We would appreciate 
if anyone interested in the areas of data management, 
including archival, backup, restore, replication, 
mirroring, would review and consider participating in this effort.
The following summarize the status of NDMP:

- A new draft, draft-ndmpv4-001.txt is in the process of 
becoming available in the IETF drafts directory.

- The NDMP effort was started in 1996. Currently NDMP versions 2 
and 3 are supported by more than 10 vendors of disk and tape 
based storage systems, as well as vendors of data management 
applications. More than 5 additional companies are implementing 
NDMP based products for the first time. 

- The version 4 draft has been produced by a group of 
approx. 10 people representing 6 companies. 
Several others have contributed in the review of the 
draft in weekly teleconferences and on the mailing list. 

- The effort has been organized through the mailing list 
ndmp-tech@ndmp.org, and the web site www.ndmp.org. 
The web site has email archives going back to the 
work on version 2, as well as a number of "backgrounder"
documents for version 4 as well as future NDMP work.
  
- As an introduction to the protocol, first read the 
abstract of the draft:

 Abstract 
    The Network Data Management Protocol (NDMP) is an open 
    protocol for enterprise wide network based data management. 
    NDMP defines a TCP/IP based mechanism for 
    controlling the transfer of data between 
    primary and secondary storage subsystems on behalf of 
    data archival or backup and recovery operations.  NDMP provides 
    architectural separation of the network attached Data 
    Management Application (DMA), Data Servers and Tape Servers 
    participating in archival or recovery operations. 
    NDMP also provides low level control
    of tape devices and tape library robotics on behalf of 
    DMAs. Multi-vendor interoperability and extensibility 
    are key goals of NDMP. 

To further clarify:
 
  1: NDMP is focused on allowing a data management 
  application to set up and *manage* a data 
  management session, such as backup, between a 
  source and a target.
  The source can be a server with direct attached storage 
  or a file server appliance. The target can be a 
  server with a tape drive, or a tape library appliance.

  2: NDMP is agnostic to the data format sent from the 
  source to the target.

  3: NDMP is agnostic to the transport mechanism used to 
  transport the data between source and target.

- There is storage related work under way in the IP Storage working 
groups. The two existing drafts: "Fibre Channel over TCP/IP", and
"iSCSI" focuses on the transport of the data over the Internet. NDMP
focuses on the control of the participating parties in the session.
It is therefore our understanding that NDMP is orthogonal 
to ongoing storage related work in the IETF.

- There is work going on in the IETF in the area of "reliable sever 
pooling" (RSERPOOL). Although the goal is for NDMP sessions to be 
"highly reliable applications", there does not seem to be any direct
connection between RSERPOOL and NDMP.


We ask that all interested parties contact the NDMP group
by sending email to ndmp-tech@ndmp.org. One can be added to this
mailing list from the "NDMP Initiative" page on www.ndmp.org.  

We will have a discussion on the ndmp-tech@ndmp.org mailing list to 
decide which are the appropriate next steps to take.

On behalf of the NDMP effort,

	Harald Skardal


      Harald Skardal,
      Network Appliance Inc.,
      Email: Harald.Skardal@netapp.com,
      Tel: 603.882.3881,
      Cel: 603.566.3027.



From owner-ietf-outbound  Mon Nov 27 13:50:59 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA25480
	for ietf-outbound.10@ietf.org; Mon, 27 Nov 2000 13:50:02 -0500 (EST)
Received: from swan.prod.itd.earthlink.net (swan.prod.itd.earthlink.net [207.217.120.123])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA24034
	for <ietf@ietf.org>; Mon, 27 Nov 2000 13:46:40 -0500 (EST)
Received: from vaio (hsa138.pool010.at101.earthlink.net [216.249.81.138])
	by swan.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id KAA15931
	for <ietf@ietf.org>; Mon, 27 Nov 2000 10:46:35 -0800 (PST)
From: "Shirley Tseng" <shirleytseng@earthlink.net>
To: <ietf@ietf.org>
Subject: Useable video from meetings - was suggestion
Date: Mon, 27 Nov 2000 10:50:12 -0800
Message-ID: <NDBBLGAIACLIKKIHOHEHCELCCGAA.shirleytseng@earthlink.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
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.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

It sure would be nice for the IETF to offer webcasting of the meetings.  The
objective of 'ease of access to information' would be greatly serve if the
protocol and software package debate can be put aside...  If commercial
conferences like Comdex can be provided by CNET (See
http://www.key3media.com/comdex/fall2000/), the ISOC can webcast INET
conference (See notice below), and ICANN meetings are webcast and archives
available overnight (see below), why is the bar to IETF participation still
having to deploy MBONE or have access to it?

..just a simple question...  If it is a money issue, perhaps student
volunteers from the local university or companies can donate their services.

The IETF agenda is global.  The IETF operating principle is open access.
Any tool that can lower the barriar to participation would make sense...

Just having useable archive webcast would be an improvement.  Technology for
real-time humming and vote counting can come later!!!  (I am sure better
technology on vote counting will be very popular in the next year...)

Shirley Tseng
Infinite Global Infrastructures
stseng@ieee.org

-- INET meeting archive

Fri, 28 Jul 2000 18:21:05 +0900
From: KAWAI Keiichi <kero@sfc.wide.ad.jp>
To: "ISTF Discussion" <istf-participants@lyris.isoc.org>
CC: inet2k-live@sfc.wide.ad.jp
Subject: Announce: Archive of 1st ISTF face-to-face Informal Meeting is now
available.

Dear ISTFers:

I am pleased to announce that Video / Audio / Text Archive of ISTF
Meeting in Yokohama is now available at

	http://inet.sfc.wide.ad.jp/

On behalf of 8 volunteer webcast team members, I would like to thank
for all the encouragement and compliments given to the webcast team.

We have tried to make this webcast as accessible as possible --
video/audio works with old players, bandwidth can be as low as 12kbps,
and scribe system was also available for people with language/hearing
barriers.
I apologize for people who could not watch the live webcast even with
those efforts. I will work more for next time.

And I would like to thank Ms. Abigail Cooke who volunteered for the
scribe.
My small scribing system could not work without you.

I would like to thank all of you again for letting us work with you,
and, please enjoy!

Sincerely,

Keiichi "kero" KAWAI
Webcast Team,  Jun Murai Lab.
Keio University
kero@sfc.wide.ad.jp

ICANN archives
Today's ICANN Board Meeting is now complete, and archives of this session,
yesterday's Public Forum, and Tuesday's DNSO meetings have been posted in
the online meeting archive at
<http://cyber.law.harvard.edu/icann/la2000/archive>.  Archives include
RealVideo archives, agendas, scribe's notes, documents and presentations
used, real-time questions received, and online discussion logs.



From owner-ietf-outbound  Mon Nov 27 14:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA09609
	for ietf-outbound.10@ietf.org; Mon, 27 Nov 2000 14:30:03 -0500 (EST)
Received: from twin.uoregon.edu (IDENT:root@twin.uoregon.edu [128.223.214.27])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA08952
	for <ietf@ietf.org>; Mon, 27 Nov 2000 14:28:50 -0500 (EST)
Received: from localhost (joelja@localhost)
	by twin.uoregon.edu (8.11.0/8.11.0) with ESMTP id eARJSuh24900;
	Mon, 27 Nov 2000 11:28:56 -0800
X-Authentication-Warning: twin.uoregon.edu: joelja owned process doing -bs
Date: Mon, 27 Nov 2000 11:28:56 -0800 (PST)
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
X-Sender: joelja@twin.uoregon.edu
To: Shirley Tseng <shirleytseng@earthlink.net>
cc: ietf@ietf.org
Subject: Re: Useable video from meetings - was suggestion
In-Reply-To: <NDBBLGAIACLIKKIHOHEHCELCCGAA.shirleytseng@earthlink.net>
Message-ID: <Pine.LNX.4.21.0011271112410.22985-100000@twin.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

Two of the rooms will be multicast, in two formats h.261 and mpeg-1. Those
sessions will be recorded and can then be down-mixed to various formats
for archiving...

They should be available slighlty thereafter in a format similar to what
we're currently doing for the nanog meetings...

http://videolab.uoregon.edu/nanog/

Doing even a small number of sessions all day for four days is a major
logistical effort that currently involves around 20 volunteers including
at current count something like 7-9 students...

joelja

On Mon, 27 Nov 2000, Shirley Tseng wrote:

> Hi,
> 
> It sure would be nice for the IETF to offer webcasting of the meetings.  The
> objective of 'ease of access to information' would be greatly serve if the
> protocol and software package debate can be put aside...  If commercial
> conferences like Comdex can be provided by CNET (See
> http://www.key3media.com/comdex/fall2000/), the ISOC can webcast INET
> conference (See notice below), and ICANN meetings are webcast and archives
> available overnight (see below), why is the bar to IETF participation still
> having to deploy MBONE or have access to it?
> 
> ..just a simple question...  If it is a money issue, perhaps student
> volunteers from the local university or companies can donate their services.
> 
> The IETF agenda is global.  The IETF operating principle is open access.
> Any tool that can lower the barriar to participation would make sense...
> 
> Just having useable archive webcast would be an improvement.  Technology for
> real-time humming and vote counting can come later!!!  (I am sure better
> technology on vote counting will be very popular in the next year...)
> 
> Shirley Tseng
> Infinite Global Infrastructures
> stseng@ieee.org
> 
> -- INET meeting archive
> 
> Fri, 28 Jul 2000 18:21:05 +0900
> From: KAWAI Keiichi <kero@sfc.wide.ad.jp>
> To: "ISTF Discussion" <istf-participants@lyris.isoc.org>
> CC: inet2k-live@sfc.wide.ad.jp
> Subject: Announce: Archive of 1st ISTF face-to-face Informal Meeting is now
> available.
> 
> Dear ISTFers:
> 
> I am pleased to announce that Video / Audio / Text Archive of ISTF
> Meeting in Yokohama is now available at
> 
> 	http://inet.sfc.wide.ad.jp/
> 
> On behalf of 8 volunteer webcast team members, I would like to thank
> for all the encouragement and compliments given to the webcast team.
> 
> We have tried to make this webcast as accessible as possible --
> video/audio works with old players, bandwidth can be as low as 12kbps,
> and scribe system was also available for people with language/hearing
> barriers.
> I apologize for people who could not watch the live webcast even with
> those efforts. I will work more for next time.
> 
> And I would like to thank Ms. Abigail Cooke who volunteered for the
> scribe.
> My small scribing system could not work without you.
> 
> I would like to thank all of you again for letting us work with you,
> and, please enjoy!
> 
> Sincerely,
> 
> Keiichi "kero" KAWAI
> Webcast Team,  Jun Murai Lab.
> Keio University
> kero@sfc.wide.ad.jp
> 
> ICANN archives
> Today's ICANN Board Meeting is now complete, and archives of this session,
> yesterday's Public Forum, and Tuesday's DNSO meetings have been posted in
> the online meeting archive at
> <http://cyber.law.harvard.edu/icann/la2000/archive>.  Archives include
> RealVideo archives, agendas, scribe's notes, documents and presentations
> used, real-time questions received, and online discussion logs.
> 

-- 
-------------------------------------------------------------------------- 
Joel Jaeggli				       joelja@darkwing.uoregon.edu    
Academic User Services			     consult@gladstone.uoregon.edu
     PGP Key Fingerprint: 1DE9 8FCA 51FB 4195 B42A 9C32 A30D 121E
--------------------------------------------------------------------------
It is clear that the arm of criticism cannot replace the criticism of
arms.  Karl Marx -- Introduction to the critique of Hegel's Philosophy of
the right, 1843.





From owner-ietf-outbound  Mon Nov 27 14:50:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA16359
	for ietf-outbound.10@ietf.org; Mon, 27 Nov 2000 14:50:03 -0500 (EST)
Received: from garlic.amaranth.net (garlic.amaranth.net [216.235.243.195])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15337
	for <ietf@ietf.org>; Mon, 27 Nov 2000 14:47:26 -0500 (EST)
Received: from yarrow (amaranth.ne.mediaone.net [24.147.137.133])
	(authenticated (0 bits))
	by garlic.amaranth.net (8.11.1/8.11.1) with ESMTP id eARJlMH03782
	(using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO);
	Mon, 27 Nov 2000 14:47:22 -0500
Message-ID: <00e301c058aa$dbe0c7c0$0901a8c0@local.senie.com>
From: "Daniel Senie" <dts@senie.com>
To: "Shirley Tseng" <shirleytseng@earthlink.net>, <ietf@ietf.org>
References: <NDBBLGAIACLIKKIHOHEHCELCCGAA.shirleytseng@earthlink.net>
Subject: Re: Useable video from meetings - was suggestion
Date: Mon, 27 Nov 2000 14:47:21 -0500
Organization: Amaranth Networks Inc.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="x-user-defined"
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


----- Original Message -----
From: Shirley Tseng <shirleytseng@earthlink.net>
To: <ietf@ietf.org>
Sent: Monday, November 27, 2000 1:50 PM
Subject: Useable video from meetings - was suggestion


> Hi,
>
> It sure would be nice for the IETF to offer webcasting of the meetings.
The
> objective of 'ease of access to information' would be greatly serve if the
> protocol and software package debate can be put aside...  If commercial
> conferences like Comdex can be provided by CNET (See
> http://www.key3media.com/comdex/fall2000/), the ISOC can webcast INET
> conference (See notice below), and ICANN meetings are webcast and archives
> available overnight (see below), why is the bar to IETF participation
still
> having to deploy MBONE or have access to it?
>
> ..just a simple question...  If it is a money issue, perhaps student
> volunteers from the local university or companies can donate their
services.


I have raised this issue many times, including on the floor of the open
plenary.

College students ALREADY are there providing video feeds onto the MBONE. The
problem is the MBONE doesn't reach the target audience. In the past this was
less problematic, as the universities and corporations able to connect to
the MBONE covered the core IETF activist audience pretty well. I doubt
that's true today.

Rather than volunteer efforts, I've proposed collecting and using real
dollars. Instead of an in-person attendance fee (which pays for the meeting
rooms, and the refreshments) I proposed we collect a telepresence fee to
help defray the costs of broadcasting the event with tools accessible from
ANY location on the Internet.

>
> The IETF agenda is global.  The IETF operating principle is open access.
> Any tool that can lower the barriar to participation would make sense...

I agree, as do many others, but nothing's happened in this regard beyond the
MBONE broadcast and archiving after-the-fact.

>
> Just having useable archive webcast would be an improvement.  Technology
for
> real-time humming and vote counting can come later!!!  (I am sure better
> technology on vote counting will be very popular in the next year...)
>
> Shirley Tseng
> Infinite Global Infrastructures
> stseng@ieee.org
>
> -- INET meeting archive
>
> Fri, 28 Jul 2000 18:21:05 +0900
> From: KAWAI Keiichi <kero@sfc.wide.ad.jp>
> To: "ISTF Discussion" <istf-participants@lyris.isoc.org>
> CC: inet2k-live@sfc.wide.ad.jp
> Subject: Announce: Archive of 1st ISTF face-to-face Informal Meeting is
now
> available.
>
> Dear ISTFers:
>
> I am pleased to announce that Video / Audio / Text Archive of ISTF
> Meeting in Yokohama is now available at
>
> http://inet.sfc.wide.ad.jp/
>
> On behalf of 8 volunteer webcast team members, I would like to thank
> for all the encouragement and compliments given to the webcast team.
>
> We have tried to make this webcast as accessible as possible --
> video/audio works with old players, bandwidth can be as low as 12kbps,
> and scribe system was also available for people with language/hearing
> barriers.
> I apologize for people who could not watch the live webcast even with
> those efforts. I will work more for next time.
>
> And I would like to thank Ms. Abigail Cooke who volunteered for the
> scribe.
> My small scribing system could not work without you.
>
> I would like to thank all of you again for letting us work with you,
> and, please enjoy!
>
> Sincerely,
>
> Keiichi "kero" KAWAI
> Webcast Team,  Jun Murai Lab.
> Keio University
> kero@sfc.wide.ad.jp
>
> ICANN archives
> Today's ICANN Board Meeting is now complete, and archives of this session,
> yesterday's Public Forum, and Tuesday's DNSO meetings have been posted in
> the online meeting archive at
> <http://cyber.law.harvard.edu/icann/la2000/archive>.  Archives include
> RealVideo archives, agendas, scribe's notes, documents and presentations
> used, real-time questions received, and online discussion logs.
>



From owner-ietf-outbound  Mon Nov 27 16:41:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA13914
	for ietf-outbound.10@ietf.org; Mon, 27 Nov 2000 16:40:02 -0500 (EST)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA13565
	for <ietf@ietf.org>; Mon, 27 Nov 2000 16:39:00 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.11.0/8.11.0) with ESMTP id eARLg4C01449
	for <ietf@ietf.org>; Mon, 27 Nov 2000 16:42:04 -0500
Sender: francis@localhost.localdomain
Message-ID: <3A22D52B.1EEDBC95@ecal.com>
Date: Mon, 27 Nov 2000 16:42:04 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i586)
X-Accept-Language: en, de, es
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Useable video from meetings - was suggestion
References: <NDBBLGAIACLIKKIHOHEHCELCCGAA.shirleytseng@earthlink.net> <00e301c058aa$dbe0c7c0$0901a8c0@local.senie.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

Daniel Senie wrote:

> College students ALREADY are there providing video feeds onto the MBONE. The
> problem is the MBONE doesn't reach the target audience. In the past this was
> less problematic, as the universities and corporations able to connect to
> the MBONE covered the core IETF activist audience pretty well. I doubt
> that's true today.

Hmm.  A hosting company could subscribe to the MBONE feed and bridge it over to
their RealVideo (or whatever) server.  That would avoid complicating the
on-site logistics.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Speak softly and carry an Illudium Q-32      |
|francis@ecal.com|Explosive Space Disintegrator.               |
\==============================================================/





From owner-ietf-outbound  Mon Nov 27 18:20:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA15830
	for ietf-outbound.10@ietf.org; Mon, 27 Nov 2000 18:20:02 -0500 (EST)
Received: from letters.cs.ucsb.edu (letters.cs.ucsb.edu [128.111.41.13])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA29486
	for <ietf@ietf.org>; Mon, 27 Nov 2000 17:23:18 -0500 (EST)
Received: from jackson.cs.ucsb.edu (jackson [128.111.52.10])
	by letters.cs.ucsb.edu (8.9.3+Sun/8.9.3) with ESMTP id OAA20913
	for <ietf@ietf.org>; Mon, 27 Nov 2000 14:23:18 -0800 (PST)
Received: by jackson.cs.ucsb.edu (8.9.3+Sun/SMI-SVR4)
	id OAA25960 for ietf@ietf.org; Mon, 27 Nov 2000 14:23:17 -0800 (PST)
Date: Mon, 27 Nov 2000 14:23:17 -0800 (PST)
From: almeroth@cs.ucsb.edu (Kevin C. Almeroth)
Message-Id: <200011272223.OAA25960@jackson.cs.ucsb.edu>
To: ietf@ietf.org
Subject: Re: Useable video from meetings - was suggestion
X-Loop: ietf@ietf.org

>>Doing even a small number of sessions all day for four days is a major
>>logistical effort that currently involves around 20 volunteers including
>>at current count something like 7-9 students...

Just to re-iterate what Joel said...  we are doing things differently
this IETF than we have in the past.  Joel posted what kind of cotent
and in what encoding formats will be available.

If anyone has suggestions now, during, or after the meeting on how to
improve things, please let ME know...  I don't always follow this list
on a message-by-message basis.

-Kevin



From owner-ietf-outbound  Tue Nov 28 03:50:46 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA15921
	for ietf-outbound.10@ietf.org; Tue, 28 Nov 2000 03:50:03 -0500 (EST)
Received: from sm.luth.se (ny.sm.luth.se [130.240.3.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA09586
	for <ietf@ietf.org>; Tue, 28 Nov 2000 03:34:50 -0500 (EST)
Received: from cdt.luth.se (blipp.cdt.luth.se [130.240.60.72])
	by sm.luth.se (8.10.0/8.10.0) with ESMTP id eAS8Z7T07128;
	Tue, 28 Nov 2000 09:35:07 +0100 (MET)
Message-ID: <3A236E26.190E469F@cdt.luth.se>
Date: Tue, 28 Nov 2000 09:34:46 +0100
From: Peter Parnes <peppar@CDT.LUTH.SE>
Organization: Centre for Distance-spanning =?iso-8859-1?Q?Technology=2FLule=E5?= 
	University of Technology, Marratech AB
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Daniel Senie <dts@senie.com>
CC: Shirley Tseng <shirleytseng@earthlink.net>, ietf@ietf.org
Subject: Re: Useable video from meetings - was suggestion
References: <NDBBLGAIACLIKKIHOHEHCELCCGAA.shirleytseng@earthlink.net> <00e301c058aa$dbe0c7c0$0901a8c0@local.senie.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

> The problem is the MBONE doesn't reach the target audience.

If just multicast access is the problem, then why not use a number of
multicast/unicast reflectors as was done on the last SIGCOMM conference.
One application for this might be the marratech Session Proxy which can
be found on e.g. 
www.emeetingportal.com or 
msp.cdt.luth.se:7000 

All you you need on the receiver side is a way to launch mbone tools via
a SDP-file delivered via HTTP (like e.g. the free Marratech Player or
the commercial Marratech Pro) or be able to launch the tools manually. 

/P



From owner-ietf-outbound  Wed Nov 29 01:20:50 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA26377
	for ietf-outbound.10@ietf.org; Wed, 29 Nov 2000 01:20:03 -0500 (EST)
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 SMTP id BAA22370
	for <ietf@ietf.org>; Wed, 29 Nov 2000 01:12:39 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id WAA13819;
	Tue, 28 Nov 2000 22:11:52 -0800 (PST)
Date: Tue, 28 Nov 2000 22:11:52 -0800 (PST)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200011290611.WAA13819@shell9.ba.best.com>
To: ietf@ietf.org
Subject: audio makes more sense than video
X-Loop: ietf@ietf.org

Given that audio recording and production is less expensive than 
video production, and audio takes less bandwidth, how about audio 
recordings as an alternative?

Whether we use GSM 06.10 or MP3 format, it makes economic sense.

Lincoln D. Stein suggests MP3:

  http://www.itknowledge.com/tpj/feature/tpj0503-0002.html

  http://www.mp3dev.org/mp3

  http://www.sfs.nphil.uni-tuebingen.de/~hipp/mpg123.html

Since this would be for noncommercial use for the IETF, no patent 
licensing would be required.  Commercial concerns would be free 
to pay non-profit organizations to convert the format for them.

Cheers,
James



From owner-ietf-outbound  Wed Nov 29 12:03:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10686
	for ietf-outbound.10@ietf.org; Wed, 29 Nov 2000 12:00:03 -0500 (EST)
Received: from twin.uoregon.edu (IDENT:root@twin.uoregon.edu [128.223.214.27])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA05156
	for <ietf@ietf.org>; Wed, 29 Nov 2000 11:45:30 -0500 (EST)
Received: from localhost (joelja@localhost)
	by twin.uoregon.edu (8.11.0/8.11.0) with ESMTP id eATGjxx10687;
	Wed, 29 Nov 2000 08:45:59 -0800
X-Authentication-Warning: twin.uoregon.edu: joelja owned process doing -bs
Date: Wed, 29 Nov 2000 08:45:58 -0800 (PST)
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
X-Sender:  <joelja@twin.uoregon.edu>
To: "James P. Salsman" <bovik@best.com>
cc: <ietf@ietf.org>
Subject: Re: audio makes more sense than video
In-Reply-To: <200011290611.WAA13819@shell9.ba.best.com>
Message-ID: <Pine.LNX.4.30.0011290837190.10357-100000@twin.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

There will of course be an mpeg-1 layer 2 96Kb/s bitstream as part of the
mpeg-1 multicast source. royalties have already been payed by the
hardware encoder vendor.

playback using a client that liscenses the the fraunhoffer IP such as mtv
(on unix's), windows media-player, or quicktime 5 is left to the
discretion of the viewer.

On Tue, 28 Nov 2000, James P. Salsman wrote:

> Given that audio recording and production is less expensive than
> video production, and audio takes less bandwidth, how about audio
> recordings as an alternative?
>
> Whether we use GSM 06.10 or MP3 format, it makes economic sense.
>
> Lincoln D. Stein suggests MP3:
>
>   http://www.itknowledge.com/tpj/feature/tpj0503-0002.html
>
>   http://www.mp3dev.org/mp3
>
>   http://www.sfs.nphil.uni-tuebingen.de/~hipp/mpg123.html
>
> Since this would be for noncommercial use for the IETF, no patent
> licensing would be required.  Commercial concerns would be free
> to pay non-profit organizations to convert the format for them.
>
> Cheers,
> James
>

-- 
--------------------------------------------------------------------------
Joel Jaeggli				       joelja@darkwing.uoregon.edu
Academic User Services			     consult@gladstone.uoregon.edu
     PGP Key Fingerprint: 1DE9 8FCA 51FB 4195 B42A 9C32 A30D 121E
--------------------------------------------------------------------------
It is clear that the arm of criticism cannot replace the criticism of
arms.  Karl Marx -- Introduction to the critique of Hegel's Philosophy of
the right, 1843.




From owner-ietf-outbound  Wed Nov 29 14:40:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA06017
	for ietf-outbound.10@ietf.org; Wed, 29 Nov 2000 14:40:04 -0500 (EST)
Received: from breakaway.Stanford.EDU (breakaway.Stanford.EDU [171.64.20.202])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA03974
	for <ietf@ietf.org>; Wed, 29 Nov 2000 14:34:56 -0500 (EST)
Received: from localhost (hodges@localhost)
	by breakaway.Stanford.EDU (8.9.3/8.9.3) with ESMTP id LAA01221
	for <ietf@ietf.org>; Wed, 29 Nov 2000 11:34:56 -0800 (PST)
Message-Id: <200011291934.LAA01221@breakaway.Stanford.EDU>
X-Mailer: exmh version 2.0.2 2/24/98
Subject: Of possible interest:  A conversation with Vinton Cerf
To: ietf@ietf.org
Reply-to: ietf@ietf.org
From: Jeff.Hodges@kingsmountain.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sendwidth: 150
sendbreakwidth: 150
Date: Wed, 29 Nov 2000 11:34:56 -0800
Sender: hodges@breakaway.Stanford.EDU
X-Loop: ietf@ietf.org

Q AND A: Web Pioneer Looks Ahead --
 A conversation with Vinton Cerf, new chief of the
 group that will help determine the future of Internet

http://www.sfgate.com/cgi-bin/article.cgi?file=/chronicle/archive/2000/11/27/BU
124729.DTL



JeffH





From owner-ietf-outbound  Thu Nov 30 14:50:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA17994
	for ietf-outbound.10@ietf.org; Thu, 30 Nov 2000 14:50:02 -0500 (EST)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15184
	for <ietf@ietf.org>; Thu, 30 Nov 2000 14:41:58 -0500 (EST)
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.130])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id LAA10819
	for <ietf@ietf.org>; Thu, 30 Nov 2000 11:41:34 -0800 (PST)
Received: from mailman.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-1.cisco.com (8.10.1/8.10.1) with ESMTP id eAUJfe327280
	for <ietf@ietf.org>; Thu, 30 Nov 2000 11:41:40 -0800 (PST)
Received: from [10.0.1.28] (ssh-sj1.cisco.com [171.68.225.134])
	by mailman.cisco.com (8.9.3/8.9.1) with ESMTP id LAA22995
	for <ietf@ietf.org>; Thu, 30 Nov 2000 11:41:23 -0800 (PST)
Mime-Version: 1.0
X-Sender: pfaltstr@127.0.0.1
Message-Id: <p0510054eb64c5d109ad9@[10.0.1.28]>
Date: Thu, 30 Nov 2000 20:40:55 +0100
To: ietf@ietf.org
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@cisco.com>
Subject: Information from the Unicode Consortium
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
X-MIME-Autoconverted: from 8bit to quoted-printable by sj-msg-core-1.cisco.com id LAA10819
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA15184
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit


1. The Unicode Technical Committee has modified the definition of UTF-8 to
forbid conformant implementations from interpreting non-shortest forms for
BMP characters, and clarified some of the conformance clauses. For more
information, see
http://www.unicode.org/unicode/uni2errata/UTF-8_Corrigendum.html

2. The Unicode Glossary (http://www.unicode.org/glossary) has been updated.
As a part of this work, stable bookmarks (anchors) have been added to all
defined terms. This allows other web pages to directly link to the Unicode
definitions.

For uniformity, the bookmarks are all lowercase (except for acronyms), with
any spaces replaced by underscores. For example, to insert a link for
"supplementary code point" in a web page, use
http://www.unicode.org/glossary#supplementary_code_point


    Patrik Fältström
    Co Area Director, Applications Area IETF
    Liason Unicode Consortium, IETF

-- 



From owner-ietf-outbound  Thu Nov 30 19:20:46 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA18357
	for ietf-outbound.10@ietf.org; Thu, 30 Nov 2000 19:20:03 -0500 (EST)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA16649
	for <ietf@ietf.org>; Thu, 30 Nov 2000 19:15:05 -0500 (EST)
Received: (from hta@localhost)
	by dokka.maxware.no (8.9.3/8.9.3) id BAA27592
	for ietf@ietf.org; Fri, 1 Dec 2000 01:15:03 +0100
Date: Fri, 1 Dec 2000 01:15:03 +0100
From: Harald Tveit Alvestrand <hta@dokka.maxware.no>
Message-Id: <200012010015.BAA27592@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



