From mailman-bounces@ietf.org  Thu Jul  1 05:33:04 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08388
	for <ietf-archive@ietf.org>; Thu, 1 Jul 2004 05:33:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BfxwG-0002el-Aq
	for ietf-archive@ietf.org; Thu, 01 Jul 2004 05:33:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BfxvI-0002G5-00
	for ietf-archive@ietf.org; Thu, 01 Jul 2004 05:32:05 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BfxuS-0001Tn-00
	for ietf-archive@ietf.org; Thu, 01 Jul 2004 05:31:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BfxSJ-0002AC-IM
	for ietf-archive@ietf.org; Thu, 01 Jul 2004 05:02:07 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: ietf-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.2130.1088672445.3306.mailman@lists.ietf.org>
Date: Thu, 01 Jul 2004 05:00:45 -0400
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

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

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

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


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for ietf-archive@ietf.org:

List                                     Password // URL
----                                     --------  
ifmib@ietf.org                           FmlC      
https://www1.ietf.org/mailman/options/ifmib/ietf-archive%40ietf.org

ietf@ietf.org                            puaceh    
https://www1.ietf.org/mailman/options/ietf/ietf-archive%40ietf.org


From mailman-bounces@mailman.isi.edu  Thu Jul  1 08:51:10 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20985
	for <ietf-archive@ietf.org>; Thu, 1 Jul 2004 08:51:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bg120-0002l4-FB
	for ietf-archive@ietf.org; Thu, 01 Jul 2004 08:51:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bg10z-0002MB-00
	for ietf-archive@ietf.org; Thu, 01 Jul 2004 08:50:10 -0400
Received: from gamma.isi.edu ([128.9.144.145])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bg101-0001wp-00
	for ietf-archive@ietf.org; Thu, 01 Jul 2004 08:49:09 -0400
Received: from gamma.isi.edu (localhost [127.0.0.1])
	by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i61CU1i25764
	for <ietf-archive@ietf.org>; Thu, 1 Jul 2004 05:30:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: isi.edu mailing list memberships reminder
From: mailman-owner@ISI.EDU
To: ietf-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.1989.1088683454.11132.mailman@mailman.isi.edu>
Date: Thu, 01 Jul 2004 05:04:14 -0700
Precedence: bulk
X-BeenThere: mailman@mailman.isi.edu
X-Mailman-Version: 2.1.4
List-Id: Mailman site list <mailman.mailman.isi.edu>
X-List-Administrivia: yes
Sender: mailman-bounces@mailman.isi.edu
Errors-To: mailman-bounces@mailman.isi.edu
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: mailman-bounces@mailman.isi.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your isi.edu mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@isi.edu) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@isi.edu.  Thanks!

Passwords for ietf-archive@ietf.org:

List                                     Password // URL
----                                     --------  
tcpsat@isi.edu                           okecem    
http://mailman.isi.edu/mailman/options/tcpsat/ietf-archive%40ietf.org


From ietf-bounces@ietf.org  Thu Jul  1 11:36:00 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11390
	for <ietf-archive@ietf.org>; Thu, 1 Jul 2004 11:36:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bg3bV-000339-CI
	for ietf-archive@ietf.org; Thu, 01 Jul 2004 11:36:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bg3aZ-0002bg-00
	for ietf-archive@ietf.org; Thu, 01 Jul 2004 11:35:04 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bg3Zd-0001rR-00; Thu, 01 Jul 2004 11:34:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bg2aE-0004gj-U2; Thu, 01 Jul 2004 10:30:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BfzX4-0007wF-EY
	for ietf@megatron.ietf.org; Thu, 01 Jul 2004 07:15:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15030
	for <ietf@ietf.org>; Thu, 1 Jul 2004 07:15:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BfzX1-0003w7-Vs
	for ietf@ietf.org; Thu, 01 Jul 2004 07:15:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BfzW2-0003YR-00
	for ietf@ietf.org; Thu, 01 Jul 2004 07:14:07 -0400
Received: from infres.enst.fr ([137.194.160.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BfzV0-00032H-00
	for ietf@ietf.org; Thu, 01 Jul 2004 07:13:02 -0400
Received: from enst.fr (nadour.enst.fr [137.194.162.91])
	by infres.enst.fr (Postfix) with ESMTP
	id 91E392FD9; Thu,  1 Jul 2004 13:13:01 +0200 (MEST)
Message-ID: <40E3F174.8040301@enst.fr>
Date: Thu, 01 Jul 2004 13:11:48 +0200
From: Tarek Nadour <tarek.nadour@enst.fr>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
References: <20040623192937.GA26196@danisch.de>
	<200406242005.i5OK51Fg032690@turing-police.cc.vt.edu>
In-Reply-To: <200406242005.i5OK51Fg032690@turing-police.cc.vt.edu>
X-Mailman-Approved-At: Thu, 01 Jul 2004 10:30:37 -0400
Cc: ietf@ietf.org, Hadmut Danisch <hadmut@danisch.de>
Subject: Re: Defining Internet services/service levels?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1838563838=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_MESSAGE,HTML_TITLE_EMPTY 
	autolearn=no version=2.60

This is a multi-part message in MIME format.
--===============1838563838==
Content-Type: multipart/alternative;
	boundary="------------040806070206090905040904"

This is a multi-part message in MIME format.
--------------040806070206090905040904
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

We worked, in our research group, on the definition and specification of 
the "services" since 1990. We specified the equipments level services 
(switching, CPU time, ...), the network level services (classification, 
resources reservation, ..), applicative level services (service 
elements, IN like services, NGOSS, ..) and recently the user level 
services (user demand grides, ..). We validated our reflexions and 
models through divers platforms with several indutrial companies. The 
results of our works is published in many conferences and journals. We 
would be pleased to contribute to the definition of the Internet 
services within the IETF.
Regards,
Tarek Nadour.

Valdis.Kletnieks@vt.edu wrote:

>On Wed, 23 Jun 2004 21:29:37 +0200, Hadmut Danisch <hadmut@danisch.de>  said:
>  
>
>>OK, there was some discussion about different
>>levels of Internet services and categories. 
>>
>>So should the IETF publish a definition?
>>    
>>
>
>There's discussion in progress off-list.  The problem is that although it's
>probably feasible to get a consensus on the definitions within the IETF, it's
>unclear how to phrase it so that the people who actually need the definitions
>can use them.
>
>"This planet has - or rather had - a problem, which was this: most of the
>people living on it were unhappy for pretty much of the time. Many solutions
>were suggested for this problem, but most of these were largely concerned with
>the movements of small green pieces of paper, which is odd because on the whole
>it wasn't the small green pieces of paper that were unhappy" -- Douglas Adams
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf
>  
>

--------------040806070206090905040904
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi,<br>
<br>
We worked, in our research group, on the definition and specification
of the "services" since 1990. We specified the equipments level
services (switching, CPU time, ...), the network level services
(classification, resources reservation, ..), applicative level services
(service elements, IN like services, NGOSS, ..) and recently the user
level services (user demand grides, ..). We validated our reflexions
and models through divers platforms with several indutrial companies.
The results of our works is published in many conferences and journals.
We would be pleased to contribute to the definition of the Internet
services within the IETF. <br>
Regards,<br>
Tarek Nadour.<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Valdis.Kletnieks@vt.edu">Valdis.Kletnieks@vt.edu</a> wrote:<br>
<blockquote type="cite"
 cite="mid200406242005.i5OK51Fg032690@turing-police.cc.vt.edu">
  <pre wrap="">On Wed, 23 Jun 2004 21:29:37 +0200, Hadmut Danisch <a class="moz-txt-link-rfc2396E" href="mailto:hadmut@danisch.de">&lt;hadmut@danisch.de&gt;</a>  said:
  </pre>
  <blockquote type="cite">
    <pre wrap="">OK, there was some discussion about different
levels of Internet services and categories. 

So should the IETF publish a definition?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
There's discussion in progress off-list.  The problem is that although it's
probably feasible to get a consensus on the definitions within the IETF, it's
unclear how to phrase it so that the people who actually need the definitions
can use them.

"This planet has - or rather had - a problem, which was this: most of the
people living on it were unhappy for pretty much of the time. Many solutions
were suggested for this problem, but most of these were largely concerned with
the movements of small green pieces of paper, which is odd because on the whole
it wasn't the small green pieces of paper that were unhappy" -- Douglas Adams

  </pre>
  <pre wrap="">
<hr width="90%" size="4">
_______________________________________________
Ietf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ietf@ietf.org">Ietf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/ietf">https://www1.ietf.org/mailman/listinfo/ietf</a>
  </pre>
</blockquote>
</body>
</html>

--------------040806070206090905040904--




--===============1838563838==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1838563838==--





From ietf-bounces@ietf.org  Fri Jul  2 10:10:46 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07391
	for <ietf-archive@ietf.org>; Fri, 2 Jul 2004 10:10:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BgOkZ-0006kQ-HX
	for ietf-archive@ietf.org; Fri, 02 Jul 2004 10:10:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BgOjg-0006Ns-00
	for ietf-archive@ietf.org; Fri, 02 Jul 2004 10:09:53 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BgOie-0005zB-00; Fri, 02 Jul 2004 10:08:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BgOPc-0007a3-6o; Fri, 02 Jul 2004 09:49:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BgOLt-0006EP-6V
	for ietf@megatron.ietf.org; Fri, 02 Jul 2004 09:45:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05942
	for <ietf@ietf.org>; Fri, 2 Jul 2004 09:45:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BgOLs-0006ls-HC
	for ietf@ietf.org; Fri, 02 Jul 2004 09:45:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BgOKu-0006TL-00
	for ietf@ietf.org; Fri, 02 Jul 2004 09:44:16 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12)
	id 1BgOK3-0005s3-00
	for ietf@ietf.org; Fri, 02 Jul 2004 09:43:23 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 02 Jul 2004 06:42:22 -0700
Received: from edison.cisco.com (edison.cisco.com [171.71.180.109])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i62DgoSc026859;
	Fri, 2 Jul 2004 06:42:50 -0700 (PDT)
Received: from [10.61.124.137] (ams-clip-equant-dhcp-136.cisco.com
	[10.61.124.137]) by edison.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id GAA07369;
	Fri, 2 Jul 2004 06:42:43 -0700 (PDT)
Message-ID: <40E56650.2050809@cisco.com>
Date: Fri, 02 Jul 2004 15:42:40 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.8a1) Gecko/20040520
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Sabharwal, Atul" <atul.sabharwal@intel.com>
References: <66539F0E7F15B44C9C0FC50D0FF024F7C6B1EF@orsmsx407>
In-Reply-To: <66539F0E7F15B44C9C0FC50D0FF024F7C6B1EF@orsmsx407>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, "Lynch, Rusty" <rusty.lynch@intel.com>
Subject: Re: RFC 3164 i.e. BSD Syslog Protocol
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

In theory there's no reason multicast SYSLOG shouldn't work.  The packet 
format doesn't need to change and you just need to bind to a multicast 
socket.  I haven't any idea how implementations will currently behave.

But you're addressing two separate problems- distribution and 
reliability.  Reliability is addressed with SYSLOG/BEEP, which I believe 
is a Proposed Standard (RFC 3195).

Eliot


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul  2 11:00:03 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10831
	for <ietf-archive@ietf.org>; Fri, 2 Jul 2004 11:00:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BgPWG-0007hX-Uv
	for ietf-archive@ietf.org; Fri, 02 Jul 2004 11:00:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BgPV6-0007Ho-00
	for ietf-archive@ietf.org; Fri, 02 Jul 2004 10:58:52 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BgPTu-0006YL-00; Fri, 02 Jul 2004 10:57:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BgPGZ-0001mg-G7; Fri, 02 Jul 2004 10:43:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BgP8O-0006Dm-TW
	for ietf@megatron.ietf.org; Fri, 02 Jul 2004 10:35:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09244
	for <ietf@ietf.org>; Fri, 2 Jul 2004 10:35:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BgP8O-0007CN-2b
	for ietf@ietf.org; Fri, 02 Jul 2004 10:35:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BgP7e-0006tB-00
	for ietf@ietf.org; Fri, 02 Jul 2004 10:34:38 -0400
Received: from [199.239.208.244] (helo=199.239.208.244)
	by ietf-mx with esmtp (Exim 4.12) id 1BgP6r-0006U7-00
	for ietf@ietf.org; Fri, 02 Jul 2004 10:33:49 -0400
Received: from [24.239.105.13] (helo=x)
	by 199.239.208.244 with asmtp (Exim 3.36 #1)
	id 1BgP6M-00038q-00; Fri, 02 Jul 2004 10:33:18 -0400
From: "Sal Mangiapane" <salm@servanttechnology.com>
To: <Valdis.Kletnieks@vt.edu>
Date: Fri, 2 Jul 2004 10:33:09 -0400
Message-ID: <OJELKLINFKPMOMIFLIDFEEIAFLAA.salm@servanttechnology.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <200406242154.i5OLsWSa004819@turing-police.cc.vt.edu>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: Intellectual property clarification - please 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: salm@servanttechnology.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=RCVD_NUMERIC_HELO autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

> > Is it the intention to always include the IPR statement and the RFC
> > Editor will only "ensure" it when an IPR disclosure has been made?
> 
> I read it as "If we are aware of an IPR claim or disclosure, the RFC Editor
> will include the appropriate text.".  I don't see any requirement that the RFC Editor
> add text protecting against an undisclosed "submarine" patent claim or similar
> unfriendly activities....
> 
> (Whether such language *should* be added to protect against that is a subject
> for another flame-fest, another day.. ;)


I don't expect the RFC Editor to add any text.  It appeared that an IPR statement was
only required by the authors when they also made an IPR disclosure.  Likewise, when an
IPR disclosure was made, the RFC Editor would make sure that the IPR statement was
within the document.

I am comfortable with the understanding that the IPR statement is always included and
the RFC Editor will only be required to verify when an IPR disclosure has been made too.

Then of course I ask myself.  If it is supposed to always be included why not "ensure"
it is in there for every document?

IMHO (I have no authority :) it appears that an IPR statement should be included in all
documents.

Regards,

Sal

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul  2 13:18:53 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21219
	for <ietf-archive@ietf.org>; Fri, 2 Jul 2004 13:18:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BgRgb-0001eC-Ud
	for ietf-archive@ietf.org; Fri, 02 Jul 2004 13:18:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BgRfm-0001I0-00
	for ietf-archive@ietf.org; Fri, 02 Jul 2004 13:18:03 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BgRei-0000s7-00; Fri, 02 Jul 2004 13:16:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BgRMi-0003dM-Q2; Fri, 02 Jul 2004 12:58:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BgRC7-0008Pl-Qc
	for ietf@megatron.ietf.org; Fri, 02 Jul 2004 12:47:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19304
	for <ietf@ietf.org>; Fri, 2 Jul 2004 12:47:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BgRC6-0006qQ-LN
	for ietf@ietf.org; Fri, 02 Jul 2004 12:47:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BgRB6-0006WN-00
	for ietf@ietf.org; Fri, 02 Jul 2004 12:46:21 -0400
Received: from hermes.py.intel.com ([146.152.216.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BgRA8-0005uy-00
	for ietf@ietf.org; Fri, 02 Jul 2004 12:45:20 -0400
Received: from petasus.py.intel.com (petasus.py.intel.com [146.152.221.4])
	by hermes.py.intel.com (8.12.9-20030918-01/8.12.9/d: large-outer.mc,v
	1.9 2004/01/09 00:55:23 root Exp $) with ESMTP id i62Gi9S3003055; 
	Fri, 2 Jul 2004 16:44:09 GMT
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com
	[192.168.65.206])
	by petasus.py.intel.com (8.12.9-20030918-01/8.12.9/d: large-inner.mc,v
	1.10 2004/03/01 19:22:27 root Exp $) with SMTP id i62GjFwO032437; 
	Fri, 2 Jul 2004 16:45:22 GMT
Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56])
	by orsmsxvs040.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id
	M2004070209440620703 ; Fri, 02 Jul 2004 09:44:06 -0700
Received: from orsmsx407.amr.corp.intel.com ([192.168.65.50]) by
	orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0);
	Fri, 2 Jul 2004 09:43:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 2 Jul 2004 09:43:53 -0700
Message-ID: <66539F0E7F15B44C9C0FC50D0FF024F7D0398D@orsmsx407>
Thread-Topic: RFC 3164 i.e. BSD Syslog Protocol
thread-index: AcRgOnp9JJQGlLITSUqiYGniuaCuLQAGSZ6A
From: "Sabharwal, Atul" <atul.sabharwal@intel.com>
To: "Eliot Lear" <lear@cisco.com>
X-OriginalArrivalTime: 02 Jul 2004 16:43:54.0870 (UTC)
	FILETIME=[C3520160:01C46053]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org, "Lynch, Rusty" <rusty.lynch@intel.com>
Subject: RE: RFC 3164 i.e. BSD Syslog Protocol
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable



>
>In theory there's no reason multicast SYSLOG shouldn't work. =20
>The packet=20
>format doesn't need to change and you just need to bind to a multicast=20
>socket.  I haven't any idea how implementations will currently behave.
>
>But you're addressing two separate problems- distribution and=20
>reliability.  Reliability is addressed with SYSLOG/BEEP, which=20
>I believe=20
>is a Proposed Standard (RFC 3195).
>

Part of the reliability standard is TCP based. Hence, multicast is not
Supported. On the UDP side, it can be done.

Thanks,

Atul

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul  5 10:17:26 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29360
	for <ietf-archive@ietf.org>; Mon, 5 Jul 2004 10:17:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BhUHg-0004B3-0u
	for ietf-archive@ietf.org; Mon, 05 Jul 2004 10:17:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhUGo-0003uQ-00
	for ietf-archive@ietf.org; Mon, 05 Jul 2004 10:16:35 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BhUGK-0003b5-00; Mon, 05 Jul 2004 10:16:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BhTTO-0005GW-Br; Mon, 05 Jul 2004 09:25:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhTLd-0004XE-G5
	for ietf@megatron.ietf.org; Mon, 05 Jul 2004 09:17:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25314
	for <ietf@ietf.org>; Mon, 5 Jul 2004 09:17:22 -0400 (EDT)
From: hadmut@danisch.de
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhTLX-0002Mi-QM
	for ietf@ietf.org; Mon, 05 Jul 2004 09:17:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhTKS-00022g-00
	for ietf@ietf.org; Mon, 05 Jul 2004 09:16:17 -0400
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx with esmtp (Exim 4.12) id 1BhTJU-0001kK-00
	for ietf@ietf.org; Mon, 05 Jul 2004 09:15:17 -0400
Received: (from hadmut@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) id i65DFFCX031305
	for ietf@ietf.org; Mon, 5 Jul 2004 15:15:15 +0200
Date: Mon, 5 Jul 2004 15:15:15 +0200
To: ietf@ietf.org
Message-ID: <20040705131515.GA31127@danisch.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
Subject: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

Hi,

a german computer magazine reported that China
is developing their own IP address scheme as
IPv9 ( http://www.heise.de/newsticker/meldung/48859 )
in order to improve "security" (probably spelled: censorship).
They cite

http://news.xinhuanet.com/english/2004-07/05/content_1572719.htm

It is to be used inside China, and they will have routers
as gateways to ipv4 and ipv6 and the borders of China
(obviously not letting everything pass through).

Does anyone know details about this protocol?

What's the IETF's opinion (if IETF does have anything like an 
IETF's opinion) about such an effort?

regards
Hadmut



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul  5 12:11:34 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04933
	for <ietf-archive@ietf.org>; Mon, 5 Jul 2004 12:11:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BhW48-0007JE-1A
	for ietf-archive@ietf.org; Mon, 05 Jul 2004 12:11:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhW37-00070u-00
	for ietf-archive@ietf.org; Mon, 05 Jul 2004 12:10:33 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BhW2S-0006f7-00; Mon, 05 Jul 2004 12:09:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BhVJp-0005Yb-8n; Mon, 05 Jul 2004 11:23:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhV6k-0004T8-6u
	for ietf@megatron.ietf.org; Mon, 05 Jul 2004 11:10:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02468
	for <ietf@ietf.org>; Mon, 5 Jul 2004 11:10:06 -0400 (EDT)
From: Gordon.Lennox@cec.eu.int
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhV6e-0004MN-A7
	for ietf@ietf.org; Mon, 05 Jul 2004 11:10:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhV44-0003xj-00
	for ietf@ietf.org; Mon, 05 Jul 2004 11:07:29 -0400
Received: from ex3beimcoims01.cec.eu.int ([158.169.131.56])
	by ietf-mx with esmtp (Exim 4.12) id 1BhV2g-0003Jk-00
	for ietf@ietf.org; Mon, 05 Jul 2004 11:06:02 -0400
Received: by ex3beimcoims01 with Internet Mail Service (5.5.2657.72)
	id <NSDH28NF>; Mon, 5 Jul 2004 17:05:30 +0200
Message-ID: <8723A4EA11C8D7119DC80003470D204904A291CB@ex2beimcombx08>
To: ietf@ietf.org
Date: Mon, 5 Jul 2004 17:05:25 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

See also:

http://www.chinatechnews.com/index.php?action=show&type=news&id=1405

Google gives about 4000 hits for IPv9.

Including of course RFC 1606....

:-)

Gordon

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
hadmut@danisch.de
Sent: Monday, July 05, 2004 3:15 PM
To: ietf@ietf.org
Subject: Chinese IPv9


Hi,

a german computer magazine reported that China
is developing their own IP address scheme as
IPv9 ( http://www.heise.de/newsticker/meldung/48859 )
in order to improve "security" (probably spelled: censorship).
They cite

http://news.xinhuanet.com/english/2004-07/05/content_1572719.htm

It is to be used inside China, and they will have routers
as gateways to ipv4 and ipv6 and the borders of China
(obviously not letting everything pass through).

Does anyone know details about this protocol?

What's the IETF's opinion (if IETF does have anything like an 
IETF's opinion) about such an effort?

regards
Hadmut



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul  5 19:27:47 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23080
	for <ietf-archive@ietf.org>; Mon, 5 Jul 2004 19:27:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BhcsE-0007Sc-ND
	for ietf-archive@ietf.org; Mon, 05 Jul 2004 19:27:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhcrI-00079l-00
	for ietf-archive@ietf.org; Mon, 05 Jul 2004 19:26:48 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BhcqP-0006Zb-00; Mon, 05 Jul 2004 19:25:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bhc1s-0006nv-W5; Mon, 05 Jul 2004 18:33:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhbuH-00065Z-7a
	for ietf@megatron.ietf.org; Mon, 05 Jul 2004 18:25:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21128
	for <ietf@ietf.org>; Mon, 5 Jul 2004 18:25:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhbuA-0004DD-Qg
	for ietf@ietf.org; Mon, 05 Jul 2004 18:25:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhbtF-0003vT-00
	for ietf@ietf.org; Mon, 05 Jul 2004 18:24:45 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12) id 1BhbsQ-0003Lk-00
	for ietf@ietf.org; Mon, 05 Jul 2004 18:23:54 -0400
Received: from consulintel02 by consulintel.es (MDaemon.PRO.v7.1.1.R)
	with ESMTP id md50000114137.msg
	for <ietf@ietf.org>; Tue, 06 Jul 2004 00:25:45 +0200
Message-ID: <023f01c462de$a32ddc50$640a0a0a@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <8723A4EA11C8D7119DC80003470D204904A291CB@ex2beimcombx08>
Date: Tue, 6 Jul 2004 00:23:01 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Tue, 06 Jul 2004 00:25:45 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Tue, 06 Jul 2004 00:25:47 +0200
Content-Transfer-Encoding: quoted-printable
Subject: Re: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

Complete compilation of news at http://www.ist-ipv6.org/modules.php?op=3Dmodload&name=3DNews&file=3Darticle&sid=3D622

But I guess is an hoax ?

----- Original Message -----=20
From: <Gordon.Lennox@cec.eu.int>
To: <ietf@ietf.org>
Sent: Monday, July 05, 2004 5:05 PM
Subject: RE: Chinese IPv9


> See also:
>=20
> http://www.chinatechnews.com/index.php?action=3Dshow&type=3Dnews&id=3D1405
>=20
> Google gives about 4000 hits for IPv9.
>=20
> Including of course RFC 1606....
>=20
> :-)
>=20
> Gordon
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> hadmut@danisch.de
> Sent: Monday, July 05, 2004 3:15 PM
> To: ietf@ietf.org
> Subject: Chinese IPv9
>=20
>=20
> Hi,
>=20
> a german computer magazine reported that China
> is developing their own IP address scheme as
> IPv9 ( http://www.heise.de/newsticker/meldung/48859 )
> in order to improve "security" (probably spelled: censorship).
> They cite
>=20
> http://news.xinhuanet.com/english/2004-07/05/content_1572719.htm
>=20
> It is to be used inside China, and they will have routers
> as gateways to ipv4 and ipv6 and the borders of China
> (obviously not letting everything pass through).
>=20
> Does anyone know details about this protocol?
>=20
> What's the IETF's opinion (if IETF does have anything like an=20
> IETF's opinion) about such an effort?
>=20
> regards
> Hadmut
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20


**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul  5 21:33:55 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28038
	for <ietf-archive@ietf.org>; Mon, 5 Jul 2004 21:33:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BheqJ-00076D-O0
	for ietf-archive@ietf.org; Mon, 05 Jul 2004 21:33:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhepe-0006nf-00
	for ietf-archive@ietf.org; Mon, 05 Jul 2004 21:33:15 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bheos-0006PX-00; Mon, 05 Jul 2004 21:32:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bhe6C-000747-KZ; Mon, 05 Jul 2004 20:46:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bhdy4-0006Ip-DC
	for ietf@megatron.ietf.org; Mon, 05 Jul 2004 20:37:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25950
	for <ietf@ietf.org>; Mon, 5 Jul 2004 20:37:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bhdxx-0005Ww-Uj
	for ietf@ietf.org; Mon, 05 Jul 2004 20:37:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhdwz-0005Eg-00
	for ietf@ietf.org; Mon, 05 Jul 2004 20:36:46 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12)
	id 1Bhdvu-0004eo-00
	for ietf@ietf.org; Mon, 05 Jul 2004 20:35:38 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 05 Jul 2004 17:41:04 +0000
X-BrightmailFiltered: true
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i660Z64N010869;
	Mon, 5 Jul 2004 17:35:06 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	(authenticated bits=0)
	by imail.cisco.com (8.12.5/8.12.10) with ESMTP id i660utjO023436;
	Mon, 5 Jul 2004 17:56:55 -0700
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16617.62390.183948.455497@thomasm-u1.cisco.com>
Date: Mon, 5 Jul 2004 17:35:02 -0700 (PDT)
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
In-Reply-To: <023f01c462de$a32ddc50$640a0a0a@consulintel.es>
References: <8723A4EA11C8D7119DC80003470D204904A291CB@ex2beimcombx08>
	<023f01c462de$a32ddc50$640a0a0a@consulintel.es>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &, heK/V66p?[2!i|tVn,
	9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
	@RFNnJEg~WZ/(8<`5a), -7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,
	g">$%B!0w{W)qIhmwhye104zd bUcI'1!
X-IMAIL-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home";
	t:"1089075416.117626"; x:"1089507416"; a:"rsa-sha1"; b:"0:2658";
	e:"Iw==";
	n:"zCnd+ByA23/7WMiIwaIZ7Ez3DplzVMdRKP138IXLOvBVeaRZ4yWEPclZ/2Mda"
	"s5Bs9RPWH0BGd3fx6j+txdOXarv4Y8kpMqTexCOMFlDmatpXDXfFj3VI9o4G7"
	"674gFTasaoPcvEfZCwcBgZD7T6sLZa3RTBUGzZqOshAMRpVek=";
	s:"acO4WaJsE8l1WRdbQbi6Fe03oQ9vo2kWTbdKYq2YGel2FnuNFtgliALpJD61w"
	"pGfVujTi1D5eI+/z9OJwz7JrrX7F821sVYjNqLipybVKIu37NTThpyKQPAx7t"
	"g89y3FSWjKdoHJIxymJGdZ77cR/l5aFEiCoaLaO2M46cO+D98=";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Mon, 5 Jul 2004 17:35:02 -0700 (PDT)";
	c:"Subject: Re: Chinese IPv9"
X-IMAIL-VERIFY: s:"y"; v:"y"; r:"19"; h:"imail.cisco.com"
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

JORDI PALET MARTINEZ writes:
 > Complete compilation of news at http://www.ist-ipv6.org/modules.php?op=modload&name=News&file=article&sid=622
 > 
 > But I guess is an hoax ?

   Or the revenge of J*m Fl*mm*ng?

      Mike, 4 is to 6 as 6 is to 9?

 > 
 > ----- Original Message ----- 
 > From: <Gordon.Lennox@cec.eu.int>
 > To: <ietf@ietf.org>
 > Sent: Monday, July 05, 2004 5:05 PM
 > Subject: RE: Chinese IPv9
 > 
 > 
 > > See also:
 > > 
 > > http://www.chinatechnews.com/index.php?action=show&type=news&id=1405
 > > 
 > > Google gives about 4000 hits for IPv9.
 > > 
 > > Including of course RFC 1606....
 > > 
 > > :-)
 > > 
 > > Gordon
 > > 
 > > -----Original Message-----
 > > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
 > > hadmut@danisch.de
 > > Sent: Monday, July 05, 2004 3:15 PM
 > > To: ietf@ietf.org
 > > Subject: Chinese IPv9
 > > 
 > > 
 > > Hi,
 > > 
 > > a german computer magazine reported that China
 > > is developing their own IP address scheme as
 > > IPv9 ( http://www.heise.de/newsticker/meldung/48859 )
 > > in order to improve "security" (probably spelled: censorship).
 > > They cite
 > > 
 > > http://news.xinhuanet.com/english/2004-07/05/content_1572719.htm
 > > 
 > > It is to be used inside China, and they will have routers
 > > as gateways to ipv4 and ipv6 and the borders of China
 > > (obviously not letting everything pass through).
 > > 
 > > Does anyone know details about this protocol?
 > > 
 > > What's the IETF's opinion (if IETF does have anything like an 
 > > IETF's opinion) about such an effort?
 > > 
 > > regards
 > > Hadmut
 > > 
 > > 
 > > 
 > > _______________________________________________
 > > Ietf mailing list
 > > Ietf@ietf.org
 > > https://www1.ietf.org/mailman/listinfo/ietf
 > > 
 > > _______________________________________________
 > > Ietf mailing list
 > > Ietf@ietf.org
 > > https://www1.ietf.org/mailman/listinfo/ietf
 > > 
 > 
 > 
 > **********************************
 > Madrid 2003 Global IPv6 Summit
 > Presentations and videos on line at:
 > http://www.ipv6-es.com
 > 
 > This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
 > 
 > 
 > 
 > 
 > _______________________________________________
 > Ietf mailing list
 > Ietf@ietf.org
 > https://www1.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul  5 21:48:58 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28442
	for <ietf-archive@ietf.org>; Mon, 5 Jul 2004 21:48:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bhf4s-0003uz-El
	for ietf-archive@ietf.org; Mon, 05 Jul 2004 21:48:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhf3z-0003Xp-00
	for ietf-archive@ietf.org; Mon, 05 Jul 2004 21:48:03 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bhf2w-0002sG-00; Mon, 05 Jul 2004 21:46:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bhefv-0000rf-CW; Mon, 05 Jul 2004 21:23:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BheVy-0000IG-VB
	for ietf@megatron.ietf.org; Mon, 05 Jul 2004 21:12:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27046
	for <ietf@ietf.org>; Mon, 5 Jul 2004 21:12:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BheVs-0000TH-8G
	for ietf@ietf.org; Mon, 05 Jul 2004 21:12:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BheUw-0000BM-00
	for ietf@ietf.org; Mon, 05 Jul 2004 21:11:51 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BheU0-0007P5-00
	for ietf@ietf.org; Mon, 05 Jul 2004 21:10:52 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i6619x926092;
	Mon, 5 Jul 2004 18:09:59 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200407060109.i6619x926092@boreas.isi.edu>
To: jordi.palet@consulintel.es
Date: Mon, 5 Jul 2004 18:09:59 -0700 (PDT)
In-Reply-To: <023f01c462de$a32ddc50$640a0a0a@consulintel.es> from "JORDI PALET
	MARTINEZ" at Jul 06, 2004 12:23:01 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: bmanning
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

% Complete compilation of news at http://www.ist-ipv6.org/modules.php?op=modload&name=News&file=article&sid=622
% 
% But I guess is an hoax ?
% 

	the site seems to be missing some of the chinese language
	reports... :)
	and based on (imho) more informed sources, this is not a
	hoax but a real effort.      

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

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul  5 23:21:00 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02083
	for <ietf-archive@ietf.org>; Mon, 5 Jul 2004 23:21:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BhgVx-0000ww-J0
	for ietf-archive@ietf.org; Mon, 05 Jul 2004 23:21:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhgV4-0000em-00
	for ietf-archive@ietf.org; Mon, 05 Jul 2004 23:20:07 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BhgUV-0000Ke-00; Mon, 05 Jul 2004 23:19:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bhg9u-0000EM-8z; Mon, 05 Jul 2004 22:58:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhfxA-0007px-Kb
	for ietf@megatron.ietf.org; Mon, 05 Jul 2004 22:45:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00670
	for <ietf@ietf.org>; Mon, 5 Jul 2004 22:44:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bhfwy-0005Yr-Pz
	for ietf@ietf.org; Mon, 05 Jul 2004 22:44:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhfvy-0005G6-00
	for ietf@ietf.org; Mon, 05 Jul 2004 22:43:51 -0400
Received: from evrtwa1-ar11-4.14.89.246.evrtwa1.dsl-verizon.net ([4.14.89.246]
	helo=tndh.net) by ietf-mx with esmtp (Exim 4.12) id 1Bhfut-0004gV-00
	for ietf@ietf.org; Mon, 05 Jul 2004 22:42:43 -0400
Received: from eaglet (127.0.0.1:3066)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S5ED88> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Mon, 5 Jul 2004 19:39:31 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Bill Manning'" <bmanning@ISI.EDU>, <jordi.palet@consulintel.es>
Date: Mon, 5 Jul 2004 19:42:33 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcRi+qFB9QZhd2oxSeKIS7+q9v23BQAB3ABA
In-Reply-To: <200407060109.i6619x926092@boreas.isi.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-Id: <E1Bhfut-0004gV-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Sitting here in Seoul, Janet Sun (BII) said this is self-promotion of a
single researcher looking to improve his funding. There is technical
content, but no business content and the service providers are ignoring it
as a waste of time. Think of it as E-164 on steroids.

Tony


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Bill Manning
> Sent: Monday, July 05, 2004 6:10 PM
> To: jordi.palet@consulintel.es
> Cc: ietf@ietf.org
> Subject: Re: Chinese IPv9
> 
> % Complete compilation of news at http://www.ist-
> ipv6.org/modules.php?op=modload&name=News&file=article&sid=622
> %
> % But I guess is an hoax ?
> %
> 
> 	the site seems to be missing some of the chinese language
> 	reports... :)
> 	and based on (imho) more informed sources, this is not a
> 	hoax but a real effort.
> 
> --bill
> Opinions expressed may not even be mine by the time you read them, and
> certainly don't reflect those of any other entity (legal or otherwise).
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul  6 04:08:08 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27703
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 04:08:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bhkzn-0003uK-Qw
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 04:08:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhkys-0003bw-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 04:07:11 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BhkyG-00030v-00; Tue, 06 Jul 2004 04:06:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BhkFm-0006X9-W2; Tue, 06 Jul 2004 03:20:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bhk0y-0005DZ-9z
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 03:05:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25591
	for <ietf@ietf.org>; Tue, 6 Jul 2004 03:05:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bhk0m-0000To-6x
	for ietf@ietf.org; Tue, 06 Jul 2004 03:05:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhjzr-0000CE-00
	for ietf@ietf.org; Tue, 06 Jul 2004 03:04:07 -0400
Received: from dialpool-210-214-81-67.maa.sify.net ([210.214.81.67]
	helo=comnet.org) by ietf-mx with smtp (Exim 4.12) id 1BhjzP-0007hi-00
	for ietf@ietf.org; Tue, 06 Jul 2004 03:03:40 -0400
Date: Tue, 06 Jul 2004 12:38:01 +0530
To: ietf@ietf.org
From: support@ietf.org
Message-ID: <aknijsewosnfnpckadn@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------xrtijsvbvsnhrteompnc"
Subject: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE,
	NO_REAL_NAME autolearn=no version=2.60

----------xrtijsvbvsnhrteompnc
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
Dear user  of <b>Ietf.org</b>,<br>
<br>
Your e-mail account has  been temporary disabled because of unauthorized access.<br><br>

For more information see the  attached file.<br>
<br>
Kind  regards,<br>
&nbsp; &nbsp; The Ietf.org team &nbsp; &nbsp;  &nbsp;  &nbsp;  &nbsp; &nbsp; &nbsp; &nbsp;  <a href="http://www.ietf.org">http://www.ietf.org</a></body></html>

----------xrtijsvbvsnhrteompnc
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: Text.pif, Content-Type: application/octet-stream]
The attachment file in the message has been removed by eManager.

----------xrtijsvbvsnhrteompnc
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

----------xrtijsvbvsnhrteompnc--




From ietf-bounces@ietf.org  Tue Jul  6 13:43:40 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06062
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 13:43:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bhtym-0000QX-J1
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 13:43:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhtxt-00003W-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 13:42:46 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bhtx8-0007OE-00; Tue, 06 Jul 2004 13:41:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BhshD-0003dA-46; Tue, 06 Jul 2004 12:21:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bhgu4-0004Nv-Pm
	for ietf@megatron.ietf.org; Mon, 05 Jul 2004 23:45:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03110
	for <ietf@ietf.org>; Mon, 5 Jul 2004 23:45:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bhgu2-0000rT-Ud
	for ietf@ietf.org; Mon, 05 Jul 2004 23:45:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhgt3-0000ZD-00
	for ietf@ietf.org; Mon, 05 Jul 2004 23:44:53 -0400
Received: from mercury.lcs.mit.edu ([18.26.0.122])
	by ietf-mx with esmtp (Exim 4.12) id 1Bhgs2-0007mQ-00
	for ietf@ietf.org; Mon, 05 Jul 2004 23:43:50 -0400
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id 5B87C872F4; Mon,  5 Jul 2004 23:43:20 -0400 (EDT)
To: ietf@ietf.org
Message-Id: <20040706034320.5B87C872F4@mercury.lcs.mit.edu>
Date: Mon,  5 Jul 2004 23:43:20 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Mailman-Approved-At: Tue, 06 Jul 2004 12:21:25 -0400
Cc: jnc@mercury.lcs.mit.edu
Subject: RE: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

    > From: "Tony Hain" <alh-ietf@tndh.net>

    > There is technical content, but no business content and the service
    > providers are ignoring it as a waste of time.

Sounds like an apt description for some other IPvN efforts... :-)

	Noel

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul  6 13:43:41 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06083
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 13:43:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bhtyo-0000Qj-08
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 13:43:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhtxw-00003r-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 13:42:49 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bhtx9-0007Oz-00; Tue, 06 Jul 2004 13:41:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bht1Y-0007eB-Kr; Tue, 06 Jul 2004 12:42:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhrBc-0000kF-BU
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 10:44:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20750
	for <ietf@ietf.org>; Tue, 6 Jul 2004 10:44:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhrBW-0003X2-Fr
	for ietf@ietf.org; Tue, 06 Jul 2004 10:44:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhrAf-0003Cf-00
	for ietf@ietf.org; Tue, 06 Jul 2004 10:43:45 -0400
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx with esmtp (Exim 4.12) id 1BhrA4-0002pc-00
	for ietf@ietf.org; Tue, 06 Jul 2004 10:43:08 -0400
Received: from skuld (pcp03328070pcs.ypwest01.mi.comcast.net[68.43.176.45])
	by comcast.net (rwcrmhc13) with SMTP id <20040706144237015003ku7ne>
	(Authid: pagerl); Tue, 6 Jul 2004 14:42:38 +0000
From: "Rebecca L. Page" <page@mail.msen.com>
To: <support@ietf.org>, <ietf@ietf.org>
Date: Tue, 6 Jul 2004 10:42:26 -0400
Organization: Teris Consulting Group
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAq9ntXiJf/E6+nYYpAr0x/sKAAAAQAAAAsYJD8ggpy0+GG3AywTEP8QEAAAAA@mail.msen.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
In-Reply-To: <aknijsewosnfnpckadn@ietf.org>
Importance: Normal
Subject: RE: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: page@mail.msen.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1140890799=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_60_70,
	HTML_FONTCOLOR_UNKNOWN,HTML_MESSAGE autolearn=no version=2.60

This is a multi-part message in MIME format.

--===============1140890799==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0050_01C46345.F168D890"

This is a multi-part message in MIME format.

------=_NextPart_000_0050_01C46345.F168D890
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I have not recently used my account, so reinstate it now!!!  I suggest
you do a more through investigation prior to turning off legitimate
access for a member, without prior warning.  Fix this now!!!
 
Rebecca L. Page, Ph.D.
 
Teris Consulting Group
 
-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
support@ietf.org
Sent: Tuesday, July 06, 2004 3:08 AM
To: ietf@ietf.org
Subject: Email account utilization warning.
 
Dear user of Ietf.org,

Your e-mail account has been temporary disabled because of unauthorized
access.

For more information see the attached file.

Kind regards,
    The Ietf.org team                 http://www.ietf.org

------=_NextPart_000_0050_01C46345.F168D890
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C46345.ED539E70">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:Compatibility>
   <w:ApplyBreakingRules/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:1627421319 -2147483648 8 0 66047 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I have not recently used my =
account, so
reinstate it now!!!<span style=3D'mso-spacerun:yes'>&nbsp; </span>I =
suggest you
do a more through investigation prior to turning off legitimate access =
for a
member, without prior warning.<span style=3D'mso-spacerun:yes'>&nbsp; =
</span>Fix
this now!!!<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Rebecca L. Page, =
Ph.D.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Teris Consulting =
Group<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> =
ietf-bounces@ietf.org
[mailto:ietf-bounces@ietf.org] <b><span style=3D'font-weight:bold'>On =
Behalf Of </span></b>support@ietf.org<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, July 06, =
2004 3:08
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> ietf@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Email account =
utilization
warning.</span></font></p>

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

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>Dear user of <b><span =
style=3D'font-weight:bold'>Ietf.org</span></b>,<br>
<br>
Your e-mail account has been temporary disabled because of unauthorized =
access.<br>
<br>
For more information see the attached file.<br>
<br>
Kind regards,<br>
&nbsp; &nbsp; The Ietf.org team &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; <a =
href=3D"http://www.ietf.org">http://www.ietf.org</a><o:p></o:p></span></f=
ont></p>

</div>

</body>

</html>

------=_NextPart_000_0050_01C46345.F168D890--




--===============1140890799==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1140890799==--





From ietf-bounces@ietf.org  Tue Jul  6 13:43:43 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06110
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 13:43:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bhtyq-0000Qz-4v
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 13:43:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhtxz-00004H-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 13:42:51 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BhtxD-0007S5-00; Tue, 06 Jul 2004 13:42:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BhshE-0003dJ-E2; Tue, 06 Jul 2004 12:21:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhoW1-00070K-Vi
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 07:53:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08040
	for <ietf@ietf.org>; Tue, 6 Jul 2004 07:53:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhoVw-0007W2-Dw
	for ietf@ietf.org; Tue, 06 Jul 2004 07:53:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhoUs-00077I-00
	for ietf@ietf.org; Tue, 06 Jul 2004 07:52:27 -0400
Received: from [203.117.75.21] (helo=red-aura.com)
	by ietf-mx with smtp (Exim 4.12) id 1BhoTw-0006QN-00
	for ietf@ietf.org; Tue, 06 Jul 2004 07:51:28 -0400
Received: (qmail 49180 invoked from network); 6 Jul 2004 06:53:38 -0000
Received: from icsf.ida.gov.sg (HELO ?10.75.120.56?) (210.24.193.10)
	by red-aura.com with SMTP; 6 Jul 2004 06:53:38 -0000
Message-ID: <40EA4C16.3010506@seng.cc>
Date: Tue, 06 Jul 2004 14:52:06 +0800
From: James Seng <james@seng.cc>
User-Agent: Mozilla Thunderbird 0.7.1 (Macintosh/20040626)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tony Hain <alh-ietf@tndh.net>
References: <E1Bhfut-0004gV-00@ietf-mx>
In-Reply-To: <E1Bhfut-0004gV-00@ietf-mx>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id HAA08040
X-Mailman-Approved-At: Tue, 06 Jul 2004 12:21:25 -0400
Cc: ietf@ietf.org, jordi.palet@consulintel.es,
        "'Bill Manning'" <bmanning@ISI.EDU>
Subject: Re: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

See http://james.seng.cc/node/view/235

I receive some email from friends asking me if I know of the recent IPv9=20
news from China. I thought I should just blog about it and point them to=20
this entry.

I heard of them first time back in 2001. The technology is developed by=20
=E5=8D=81=E8=BF=9B=E5=88=B6=E7=BD=91[1] called "=E6=95=B0=E5=AD=97=E5=9F=9F=
=E5=90=8D" which translate roughly to 'Numerical=20
Domain Name". They call it ADDA (All Digital Domain Address) and then=20
later IPv9. (Okay, I laughed back then too so don't hold back yourself ;-=
)

The technology as I understand can be summarise as follows: The 10=20
digits they refer to are phone numbers (China uses 10 digit local phone=20
number). The idea is that you can navigate the web by using phone=20
numbers in the browser. The technology is basically a modified DNS and=20
the business model is to get you to registered your phone numbers with th=
em.

So it isn't really IP as you would think. But despite these, they seem=20
pretty well connected in China and have support from Ministry of=20
Information Industry (MII) among others. However, I have not seen any=20
actual deployment anywhere. Lots of press release but thats about it.

ps: There is a article in Sina.com[2] explaining the technology pretty=20
well but it is written in Chinese.

[1] http://www.em777.net/
[2] http://tech.sina.com.cn/i/w/2004-06-28/2331380918.shtml

-James Seng

Tony Hain wrote:

> Sitting here in Seoul, Janet Sun (BII) said this is self-promotion of a
> single researcher looking to improve his funding. There is technical
> content, but no business content and the service providers are ignoring=
 it
> as a waste of time. Think of it as E-164 on steroids.
>=20
> Tony
>=20
>=20
>=20
>>-----Original Message-----
>>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>>Bill Manning
>>Sent: Monday, July 05, 2004 6:10 PM
>>To: jordi.palet@consulintel.es
>>Cc: ietf@ietf.org
>>Subject: Re: Chinese IPv9
>>
>>% Complete compilation of news at http://www.ist-
>>ipv6.org/modules.php?op=3Dmodload&name=3DNews&file=3Darticle&sid=3D622
>>%
>>% But I guess is an hoax ?
>>%
>>
>>	the site seems to be missing some of the chinese language
>>	reports... :)
>>	and based on (imho) more informed sources, this is not a
>>	hoax but a real effort.
>>
>>--bill
>>Opinions expressed may not even be mine by the time you read them, and
>>certainly don't reflect those of any other entity (legal or otherwise).
>>
>>_______________________________________________
>>Ietf mailing list
>>Ietf@ietf.org
>>https://www1.ietf.org/mailman/listinfo/ietf
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul  6 14:10:30 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08234
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 14:10:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BhuOk-0002VT-Vl
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 14:10:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhuMu-0001tz-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 14:08:37 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BhuLr-0001CA-00; Tue, 06 Jul 2004 14:07:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BhtWh-0006Pk-5e; Tue, 06 Jul 2004 13:14:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhsIX-00073T-0J
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 11:55:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25795
	for <ietf@ietf.org>; Tue, 6 Jul 2004 11:55:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhsIR-0004z7-58
	for ietf@ietf.org; Tue, 06 Jul 2004 11:55:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhsEq-0003sC-00
	for ietf@ietf.org; Tue, 06 Jul 2004 11:52:09 -0400
Received: from mail-red.research.att.com ([192.20.225.110]
	helo=mail-white.research.att.com) by ietf-mx with esmtp (Exim 4.12)
	id 1BhsBw-0002gC-00
	for ietf@ietf.org; Tue, 06 Jul 2004 11:49:08 -0400
Received: from mail-blue.research.att.com (H-135-207-30-102.research.att.com
	[135.207.30.102])
	by mail-white.research.att.com (Postfix) with ESMTP id 9EA7566405C;
	Tue,  6 Jul 2004 11:48:38 -0400 (EDT)
Received: from bigmail.research.att.com (bigmail.research.att.com
	[135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP id CB834197482;
	Tue,  6 Jul 2004 11:48:12 -0400 (EDT)
Received: from berkshire.research.att.com (raptor.research.att.com
	[135.207.23.32])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id
	i66Fmc425208; Tue, 6 Jul 2004 11:48:38 -0400 (EDT)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 145501AE90; Tue,  6 Jul 2004 11:48:38 -0400 (EDT)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: "Tony Hain" <alh-ietf@tndh.net>
In-Reply-To: Your message of "Mon, 05 Jul 2004 19:42:33 PDT."
	<E1Bhfut-0004gV-00@ietf-mx> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 06 Jul 2004 11:48:38 -0400
Message-Id: <20040706154838.145501AE90@berkshire.research.att.com>
Cc: ietf@ietf.org, jordi.palet@consulintel.es,
        "'Bill Manning'" <bmanning@ISI.EDU>
Subject: Re: Chinese IPv9 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

In message <E1Bhfut-0004gV-00@ietf-mx>, "Tony Hain" writes:
>Sitting here in Seoul, Janet Sun (BII) said this is self-promotion of a
>single researcher looking to improve his funding. There is technical
>content, but no business content and the service providers are ignoring it
>as a waste of time. Think of it as E-164 on steroids.
>


Right.  See http://www.theregister.co.uk/2004/07/06/ipv9_hype_dismissed/
and several postings at http://www.interesting-people.org/archives/interesting-people/


		--Steve Bellovin, http://www.research.att.com/~smb



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul  6 15:42:17 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16815
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 15:42:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bhvpa-0003jQ-40
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 15:42:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhvnN-00038W-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 15:40:01 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BhvmU-0002nm-00; Tue, 06 Jul 2004 15:39:06 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BhvlE-0003Gb-El; Tue, 06 Jul 2004 15:37:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BhvF1-000516-BX; Tue, 06 Jul 2004 15:04:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhugS-0001Jy-GF
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 14:28:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10020
	for <ietf@ietf.org>; Tue, 6 Jul 2004 14:28:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhugM-0001eQ-8W
	for ietf@ietf.org; Tue, 06 Jul 2004 14:28:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhufM-0001JG-00
	for ietf@ietf.org; Tue, 06 Jul 2004 14:27:41 -0400
Received: from adsl-66-137-237-100.dsl.rcsntx.swbell.net ([66.137.237.100]
	helo=gw.frascone.com) by ietf-mx with esmtp (Exim 4.12)
	id 1BhueR-0000yT-00
	for ietf@ietf.org; Tue, 06 Jul 2004 14:26:43 -0400
Received: by gw.frascone.com (Postfix, from userid 500)
	id D31E458058B; Tue,  6 Jul 2004 13:26:42 -0500 (CDT)
Date: Tue, 6 Jul 2004 13:26:42 -0500
From: David Frascone <dave@frascone.com>
To: "Rebecca L. Page" <page@mail.msen.com>
Message-ID: <20040706182642.GA2101@wolverine.frascone.com>
References: <aknijsewosnfnpckadn@ietf.org>
	<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAq9ntXiJf/E6+nYYpAr0x/sKAAAAQAAAAsYJD8ggpy0+GG3AywTEP8QEAAAAA@mail.msen.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAq9ntXiJf/E6+nYYpAr0x/sKAAAAQAAAAsYJD8ggpy0+GG3AywTEP8QEAAAAA@mail.msen.com>
User-Agent: Mutt/1.4.1i
Cc: support@ietf.org, ietf@ietf.org
Subject: Re: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Perhaps with a  "more through[sic] investigation" of the headers, you
would have identified that mailing as forged.

-Dave

On Tuesday, 06 Jul 2004, Rebecca L. Page wrote:
> I have not recently used my account, so reinstate it now!!!  I suggest
> you do a more through investigation prior to turning off legitimate
> access for a member, without prior warning.  Fix this now!!!
>  
> Rebecca L. Page, Ph.D.
>  
> Teris Consulting Group
>  
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> support@ietf.org
> Sent: Tuesday, July 06, 2004 3:08 AM
> To: ietf@ietf.org
> Subject: Email account utilization warning.
>  
> Dear user of Ietf.org,
> 
> Your e-mail account has been temporary disabled because of unauthorized
> access.
> 
> For more information see the attached file.
> 
> Kind regards,
>     The Ietf.org team                 http://www.ietf.org

> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf


-- 
David Frascone

      To define recursion, we must first define recursion.

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul  6 15:43:00 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16951
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 15:43:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BhvqH-00045W-1w
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 15:43:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhvo5-0003H2-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 15:40:47 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bhvmd-0002nm-00; Tue, 06 Jul 2004 15:39:15 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BhvgT-00032m-6K; Tue, 06 Jul 2004 15:32:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bhv42-0006Ro-90; Tue, 06 Jul 2004 14:53:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhuUD-0006qq-9y
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 14:16:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09022
	for <ietf@ietf.org>; Tue, 6 Jul 2004 14:16:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhuU7-0004ri-8Q
	for ietf@ietf.org; Tue, 06 Jul 2004 14:16:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhuSk-0004Hx-00
	for ietf@ietf.org; Tue, 06 Jul 2004 14:14:39 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BhuRC-0003XN-00
	for ietf@ietf.org; Tue, 06 Jul 2004 14:13:03 -0400
Received: from scan.jck.com ([209.187.148.215])
	by bs.jck.com with esmtp (Exim 4.10) id 1BhuRD-0003VH-00
	for ietf@ietf.org; Tue, 06 Jul 2004 13:13:03 -0500
Date: Tue, 06 Jul 2004 14:13:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Message-ID: <FADC9C272BAA921AAD71AD91@scan.jck.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="==========7F2BD8628DF84D9770AB=========="
Subject: Re: What exactly is an internet (service) provider?
 (FWD: I-D ACTION:draft-klensin-ip-service-terms-03.txt)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,MIME_SUSPECT_NAME 
	autolearn=no version=2.60

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

For those who have been interested in this discussion, a new
version of the draft has been posted.  It incorporates, to the
extent to which I could figure out how to do so, comments on the
list and some very specific suggestions from a few people (see
acknowledgements).

As the document indicates, and as has been said on this list, it
is pretty easy to slice and dice this along a whole series of
dimensions and by differentiating among issues that, while
potentially important, are comprehensible only to experts.  So,
if you are going to read it and comment, I suggest (and request)
that you try to adopt the perspective of an end-user, regulator,
or legislator who is easily confused by, and impatient of,
details.  

If we have managed to design (or back into) a network design
with sufficiently many combinations of options that the
knowledge level of the readers of this list are required to
understand a service offering, that is probably a problem.  But
it is not a problem that any document like this can solve.

     john

--==========7F2BD8628DF84D9770AB==========
Content-Type: message/rfc822;
	name="I-D ACTION:draft-klensin-ip-service-terms-03.txt"

Return-path: <i-d-announce-bounces@ietf.org>
Envelope-to: klensin+ietf@jck.com
Delivery-date: Tue, 06 Jul 2004 10:46:06 -0500
Received: from [132.151.6.71] (helo=megatron.ietf.org)
	by bs.jck.com with esmtp (Exim 4.10) id 1Bhs8z-000NtF-00
	for klensin+ietf@jck.com; Tue, 06 Jul 2004 10:46:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bhr8e-0008Vu-6T; Tue, 06 Jul 2004 10:41:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhqeS-0001xI-Is
	for i-d-announce@megatron.ietf.org; Tue, 06 Jul 2004 10:10:28 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17308
	for <i-d-announce@ietf.org>; Tue, 6 Jul 2004 10:10:26 -0400 (EDT)
Message-Id: <200407061410.KAA17308@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 06 Jul 2004 10:10:26 -0400
Subject: I-D ACTION:draft-klensin-ip-service-terms-03.txt
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Terminology for Describing Internet Connectivivy
	Author(s)	: J. Klensin
	Filename	: draft-klensin-ip-service-terms-03.txt
	Pages		: 11
	Date		: 2004-7-2
	
As the Internet has evolved, many types of arrangements have been
   advertised and sold as 'Internet connectivity'.  Because these may
   differ significantly in the capabilities they offer, the range of
   options, and the lack of any standard terminology, has cause
   considerable consumer confusion.  This document provides a list of
   terms and definitions that may be helpful to providers, consumers,
   and, potentially, regulators in clarifying the type and character of
   services being offered.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-klensin-ip-service-terms-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-klensin-ip-service-terms-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-klensin-ip-service-terms-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2004-7-2121504.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-klensin-ip-service-terms-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-klensin-ip-service-terms-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2004-7-2121504.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--NextPart--




--==========7F2BD8628DF84D9770AB==========
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--==========7F2BD8628DF84D9770AB==========--




From ietf-bounces@ietf.org  Tue Jul  6 16:27:42 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19877
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 16:27:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BhwXX-0003mM-Lf
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 16:27:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhwVS-0002xU-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 16:25:35 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BhwTZ-0002OK-01; Tue, 06 Jul 2004 16:23:37 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BhwLm-0003zz-5F; Tue, 06 Jul 2004 16:15:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BhvdI-0008Qk-8t; Tue, 06 Jul 2004 15:29:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhvAY-0008He-K1
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 14:59:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12752
	for <ietf@ietf.org>; Tue, 6 Jul 2004 14:59:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhvAS-0005LO-Im
	for ietf@ietf.org; Tue, 06 Jul 2004 14:59:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhv9c-00050R-00
	for ietf@ietf.org; Tue, 06 Jul 2004 14:58:57 -0400
Received: from jormungand.iconz.co.nz ([210.48.22.36] helo=hel.iconz.co.nz)
	by ietf-mx with esmtp (Exim 4.12) id 1Bhv8i-0004c0-00
	for ietf@ietf.org; Tue, 06 Jul 2004 14:58:00 -0400
Received: from localhost (hel [127.0.0.1])
	by hel.iconz.co.nz (Postfix) with ESMTP id ED8F980183;
	Wed,  7 Jul 2004 06:57:17 +1200 (NZST)
Received: from hel.iconz.co.nz ([127.0.0.1])
	by localhost (hel.iconz.co.nz [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 15200-10; Wed, 7 Jul 2004 06:57:16 +1200 (NZST)
Received: from xthree.x.iconz.co.nz (xthree.x.iconz.co.nz [210.48.1.47])
	by hel.iconz.co.nz (Postfix) with ESMTP id AB4EA8012C;
	Wed,  7 Jul 2004 06:57:16 +1200 (NZST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 Jul 2004 06:57:56 +1200
Message-ID: <7EC070F3FFCB09418CD6BDD7B21C6B93043479@xthree.x.iconz.co.nz>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Thread-Topic: Email account utilization warning.
Thread-Index: AcRjMBE/ZS8yfTL/SDu1iLcjusbnKwAWsmUg
From: "Sean Weekes" <sean.weekes@iconz.net>
To: <support@ietf.org>, <ietf@ietf.org>
X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at hel.iconz.co.nz
Subject: RE: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1121439426=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_40_50,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60

This is a multi-part message in MIME format.

--===============1121439426==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4638B.17AF56EC"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4638B.17AF56EC
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Please can you reinstate my account or at least explain in more detail
the reason for your actions here.
=20
I'm not happy that you arbitrarily undertake this course of action
without prior notification or discussion.
=20
I also am at a loss as to why you have done this.
=20
Please can you elaborate.
=20


Regards.
Sean Weekes

General Manager, ICONZ

www.iconz.co.nz <http://www.iconz.co.nz>=20

 =20

=20

________________________________

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
support@ietf.org
Sent: Tuesday, 6 July 2004 7:08 p.m.
To: ietf@ietf.org
Subject: Email account utilization warning.


Dear user of Ietf.org,

Your e-mail account has been temporary disabled because of unauthorized
access.

For more information see the attached file.

Kind regards,
    The Ietf.org team                 http://www.ietf.org=20

------_=_NextPart_001_01C4638B.17AF56EC
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Please can you reinstate my account or at least =
explain in=20
more detail the reason for your actions here.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I'm not happy that you arbitrarily undertake =
this course of=20
action without prior notification or discussion.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I also am at a loss as to why you have done=20
this.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Please can you elaborate.</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV><BR>
<P><FONT size=3D2>Regards.<BR>Sean<SPAN class=3D182505518-06072004>=20
Weekes</SPAN></FONT></P>
<P><SPAN class=3D182505518-06072004></SPAN><SPAN=20
class=3D182505518-06072004></SPAN><FONT size=3D2>G<SPAN=20
class=3D182505518-06072004>eneral Manager, ICONZ</SPAN></FONT></P>
<P><SPAN class=3D182505518-06072004></SPAN><SPAN=20
class=3D182505518-06072004></SPAN><FONT size=3D2><A=20
href=3D"http://www.iconz.co.nz">w<SPAN=20
class=3D182505518-06072004>ww.iconz.co.nz</A></SPAN><BR><BR>&nbsp;</FONT>=
 </P>
<DIV>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> ietf-bounces@ietf.org=20
[mailto:ietf-bounces@ietf.org] <B>On Behalf Of=20
</B>support@ietf.org<BR><B>Sent:</B> Tuesday, 6 July 2004 7:08=20
p.m.<BR><B>To:</B> ietf@ietf.org<BR><B>Subject:</B> Email account =
utilization=20
warning.<BR></FONT><BR></DIV>
<DIV></DIV>Dear user of <B>Ietf.org</B>,<BR><BR>Your e-mail account has =
been=20
temporary disabled because of unauthorized access.<BR><BR>For more =
information=20
see the attached file.<BR><BR>Kind regards,<BR>&nbsp; &nbsp; The =
Ietf.org team=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <A=20
href=3D"http://www.ietf.org">http://www.ietf.org</A> </BODY></HTML>

------_=_NextPart_001_01C4638B.17AF56EC--



--===============1121439426==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1121439426==--




From ietf-bounces@ietf.org  Tue Jul  6 21:46:57 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10891
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 21:46:57 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bi1WT-00068K-NP
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 21:46:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi1VQ-0005mi-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 21:45:53 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bi1UU-00058X-00; Tue, 06 Jul 2004 21:44:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi04R-00079r-AU; Tue, 06 Jul 2004 20:13:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bhws4-0000ZD-3x
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 16:48:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21333
	for <ietf@ietf.org>; Tue, 6 Jul 2004 16:48:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bhwrx-0003OI-L5
	for ietf@ietf.org; Tue, 06 Jul 2004 16:48:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bhwqw-00031C-00
	for ietf@ietf.org; Tue, 06 Jul 2004 16:47:47 -0400
Received: from host-6.cybrnet.net ([209.5.206.27])
	by ietf-mx with esmtp (Exim 4.12) id 1Bhwq4-0002eq-00
	for ietf@ietf.org; Tue, 06 Jul 2004 16:46:52 -0400
X-ClientAddr: 216.254.186.110
Received: from tnguyen (gw-amnet2000.dsl.primus.ca [216.254.186.110])
	(authenticated bits=0)
	by host-6.cybrnet.net (8.12.10/8.12.10) with ESMTP id i66KoESv025710;
	Tue, 6 Jul 2004 16:50:16 -0400
From: "Trang Nguyen" <tnguyen@perfisans.com>
To: "Sean Weekes" <sean.weekes@iconz.net>, <support@ietf.org>, <ietf@ietf.org>
Date: Tue, 6 Jul 2004 16:56:33 -0400
Message-ID: <BFEPLILMEGEJJBOLGNKHOEDBCAAA.tnguyen@perfisans.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <7EC070F3FFCB09418CD6BDD7B21C6B93043479@xthree.x.iconz.co.nz>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-mycybernet.net-MailScanner-Information: Please contact the ISP for more
	information
X-mycybernet.net-MailScanner: Not scanned: please contact your Internet E-Mail
	Service Provider for details
Subject: RE: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0080917987=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_40_50,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60

This is a multi-part message in MIME format.

--===============0080917987==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001E_01C4637A.3154AF90"

This is a multi-part message in MIME format.

------=_NextPart_000_001E_01C4637A.3154AF90
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Same with me.  Please don't cut us off without reasonable explanation.

Regards,

Trang Nguyen
  -----Original Message-----
  From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]On Behalf Of
Sean Weekes
  Sent: July 6, 2004 2:58 PM
  To: support@ietf.org; ietf@ietf.org
  Subject: RE: Email account utilization warning.


  Please can you reinstate my account or at least explain in more detail the
reason for your actions here.

  I'm not happy that you arbitrarily undertake this course of action without
prior notification or discussion.

  I also am at a loss as to why you have done this.

  Please can you elaborate.



  Regards.
  Sean Weekes

  General Manager, ICONZ

  www.iconz.co.nz







----------------------------------------------------------------------------
--
  From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
support@ietf.org
  Sent: Tuesday, 6 July 2004 7:08 p.m.
  To: ietf@ietf.org
  Subject: Email account utilization warning.


  Dear user of Ietf.org,

  Your e-mail account has been temporary disabled because of unauthorized
access.

  For more information see the attached file.

  Kind regards,
      The Ietf.org team                 http://www.ietf.org

------=_NextPart_000_001E_01C4637A.3154AF90
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D196255420-06072004><FONT face=3DArial color=3D#0000ff =
size=3D2>Same=20
with me.&nbsp; Please don't cut us off without reasonable=20
explanation.</FONT></SPAN></DIV>
<DIV><SPAN class=3D196255420-06072004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D196255420-06072004><FONT face=3DArial color=3D#0000ff =

size=3D2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D196255420-06072004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D196255420-06072004><FONT face=3DArial color=3D#0000ff =
size=3D2>Trang=20
Nguyen</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
ietf-bounces@ietf.org=20
  [mailto:ietf-bounces@ietf.org]<B>On Behalf Of </B>Sean =
Weekes<BR><B>Sent:</B>=20
  July 6, 2004 2:58 PM<BR><B>To:</B> support@ietf.org;=20
  ietf@ietf.org<BR><B>Subject:</B> RE: Email account utilization=20
  warning.<BR><BR></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Please can you reinstate my account or at =
least explain=20
  in more detail the reason for your actions here.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>I'm not happy that you arbitrarily undertake =
this course=20
  of action without prior notification or =
discussion.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>I also am at a loss as to why you have done=20
  this.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Please can you elaborate.</FONT></SPAN></DIV>
  <DIV>&nbsp;</DIV><BR>
  <P><FONT size=3D2>Regards.<BR>Sean<SPAN class=3D182505518-06072004>=20
  Weekes</SPAN></FONT></P>
  <P><SPAN class=3D182505518-06072004></SPAN><SPAN=20
  class=3D182505518-06072004></SPAN><FONT size=3D2>G<SPAN=20
  class=3D182505518-06072004>eneral Manager, ICONZ</SPAN></FONT></P>
  <P><SPAN class=3D182505518-06072004></SPAN><SPAN=20
  class=3D182505518-06072004></SPAN><FONT size=3D2><A=20
  href=3D"http://www.iconz.co.nz">w<SPAN=20
  =
class=3D182505518-06072004>ww.iconz.co.nz</A></SPAN><BR><BR>&nbsp;</FONT>=
 </P>
  <DIV>&nbsp;</DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ietf-bounces@ietf.org=20
  [mailto:ietf-bounces@ietf.org] <B>On Behalf Of=20
  </B>support@ietf.org<BR><B>Sent:</B> Tuesday, 6 July 2004 7:08=20
  p.m.<BR><B>To:</B> ietf@ietf.org<BR><B>Subject:</B> Email account =
utilization=20
  warning.<BR></FONT><BR></DIV>
  <DIV></DIV>Dear user of <B>Ietf.org</B>,<BR><BR>Your e-mail account =
has been=20
  temporary disabled because of unauthorized access.<BR><BR>For more =
information=20
  see the attached file.<BR><BR>Kind regards,<BR>&nbsp; &nbsp; The =
Ietf.org team=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <A=20
  href=3D"http://www.ietf.org">http://www.ietf.org</A> =
</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_001E_01C4637A.3154AF90--




--===============0080917987==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============0080917987==--





From ietf-bounces@ietf.org  Tue Jul  6 22:03:20 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11813
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 22:03:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bi1mL-0003ur-Cp
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 22:03:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi1lQ-0003Wy-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 22:02:24 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bi1kD-0002mW-00; Tue, 06 Jul 2004 22:01:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi0Ib-0001lJ-JF; Tue, 06 Jul 2004 20:28:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhxED-00038m-84
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 17:11:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23376
	for <ietf@ietf.org>; Tue, 6 Jul 2004 17:11:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhxE6-0004FC-KO
	for ietf@ietf.org; Tue, 06 Jul 2004 17:11:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhxD7-0003sO-00
	for ietf@ietf.org; Tue, 06 Jul 2004 17:10:41 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1BhxCA-0003PF-00
	for ietf@ietf.org; Tue, 06 Jul 2004 17:09:43 -0400
Received: (qmail 42929 invoked from network); 6 Jul 2004 21:12:44 -0000
Received: from yahoobb219001188015.bbtec.net (HELO necom830.hpcl.titech.ac.jp)
	(219.1.188.15)
	by necom830.hpcl.titech.ac.jp with SMTP; 6 Jul 2004 21:12:44 -0000
Message-ID: <40EB1654.7080804@necom830.hpcl.titech.ac.jp>
Date: Wed, 07 Jul 2004 06:15:00 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
References: <FADC9C272BAA921AAD71AD91@scan.jck.com>
In-Reply-To: <FADC9C272BAA921AAD71AD91@scan.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider? (FWD: I-D
	ACTION:draft-klensin-ip-service-terms-03.txt)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

John C Klensin;

You made, at least, two mistakes, minor and major ones.

A minor mistake is that you think you can let people outside
of IETF use your terminology, if you give loose enough
terminlogy.

As you introduce "Web connectivity", such people (including
mobile operators in Japan) claim that they are ISPs, because
they are offering web connectivity over X.25 without IP. That
is, "The definitions proposed here are clearly of little value
if service providers and vendors are not willing to adopt them."
is applicable to your draft.

A major mistake is that you are forcing people within IETF
use your terminology even though you are fully aware that
"some members of the IETF community that some of these
connectively models are simply "broken" or "not really an
Internet service"".

						Masataka Ohta


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul  6 22:06:07 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12033
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 22:06:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bi1p1-00050O-SO
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 22:06:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi1o3-0004cu-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 22:05:08 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bi1mw-0003vq-00; Tue, 06 Jul 2004 22:03:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi0KW-0002Ig-LL; Tue, 06 Jul 2004 20:30:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhxQP-00053R-PG
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 17:24:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24301
	for <ietf@ietf.org>; Tue, 6 Jul 2004 17:24:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhxQJ-0000yR-El
	for ietf@ietf.org; Tue, 06 Jul 2004 17:24:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhxPG-0000Yf-00
	for ietf@ietf.org; Tue, 06 Jul 2004 17:23:15 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BhxOF-0000A0-00
	for ietf@ietf.org; Tue, 06 Jul 2004 17:22:11 -0400
Received: from scan.jck.com ([209.187.148.215])
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BhxOF-0008oX-00; Tue, 06 Jul 2004 16:22:11 -0500
Date: Tue, 06 Jul 2004 17:22:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-ID: <D8DE8C30E0F6781B32A4422C@scan.jck.com>
In-Reply-To: <40EB1654.7080804@necom830.hpcl.titech.ac.jp>
References: <FADC9C272BAA921AAD71AD91@scan.jck.com>
	<40EB1654.7080804@necom830.hpcl.titech.ac.jp>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
 (FWD: I-D ACTION:draft-klensin-ip-service-terms-03.txt)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Ohta-san,

We have been through this before.  There is no issue of
"forcing" - this is being proposed because some people think
they would find it useful.   Everyone else will presumably
ignore it.  If it turns out that there are, in practice, none of
the former, then the document will presumably go the way of many
other ideas that didn't get any traction.

Vendors who are going to do these things will -- based on the
fact that they are being done already -- do them, with or
without this document.  And that includes providers who are
doing very little that we would recognize as "internet service"
characterizing themselves as "ISPs".   If this document can
accomplish anything, it is, as several people have pointed out,
provide a definitional basis for claiming that a vendor is lying
about what is being provided.  Put differently, the theory
behind it is to give operators/providers an opportunity to
disclose what they are doing in a more or less clear way.  If
they choose to exaggerate what they are offering, or to lie
about their services, that is a problem that this document
cannot solve and is not intended to try.

regards,
      john


--On Wednesday, 07 July, 2004 06:15 +0900 Masataka Ohta
<mohta@necom830.hpcl.titech.ac.jp> wrote:

> John C Klensin;
> 
> You made, at least, two mistakes, minor and major ones.
> 
> A minor mistake is that you think you can let people outside
> of IETF use your terminology, if you give loose enough
> terminlogy.
> 
> As you introduce "Web connectivity", such people (including
> mobile operators in Japan) claim that they are ISPs, because
> they are offering web connectivity over X.25 without IP. That
> is, "The definitions proposed here are clearly of little value
> if service providers and vendors are not willing to adopt
> them." is applicable to your draft.
> 
> A major mistake is that you are forcing people within IETF
> use your terminology even though you are fully aware that
> "some members of the IETF community that some of these
> connectively models are simply "broken" or "not really an
> Internet service"".
> 
> 						Masataka Ohta
> 





_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul  6 22:51:01 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15252
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 22:51:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bi2WU-0005KS-NA
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 22:51:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi2VT-0004tb-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 22:50:00 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bi2TU-0003xY-00; Tue, 06 Jul 2004 22:47:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi0YK-0006W1-6z; Tue, 06 Jul 2004 20:44:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhzKF-0000dw-EV
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 19:26:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03403
	for <ietf@ietf.org>; Tue, 6 Jul 2004 19:26:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhzK8-0005FR-RT
	for ietf@ietf.org; Tue, 06 Jul 2004 19:26:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhzJ8-0004ts-00
	for ietf@ietf.org; Tue, 06 Jul 2004 19:25:03 -0400
Received: from sentosa.post1.com ([202.27.17.100])
	by ietf-mx with smtp (Exim 4.12) id 1BhzIT-0004VS-00
	for ietf@ietf.org; Tue, 06 Jul 2004 19:24:21 -0400
Received: (qmail 64825 invoked from network); 6 Jul 2004 23:47:53 -0000
Received: from bb220-255-110-221.singnet.com.sg (HELO ?192.168.0.173?)
	(220.255.110.221)
	by sentosa.post1.com with SMTP; 6 Jul 2004 23:47:53 -0000
Message-ID: <40EB3483.7030902@pobox.org.sg>
Date: Wed, 07 Jul 2004 07:23:47 +0800
From: James Seng <jseng@pobox.org.sg>
User-Agent: Mozilla Thunderbird 0.7 (Macintosh/20040616)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
References: <E1Bhfut-0004gV-00@ietf-mx>
In-Reply-To: <E1Bhfut-0004gV-00@ietf-mx>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id TAA03403
Subject: Re: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

See http://james.seng.cc/node/view/235

I receive some email from friends asking me if I know of the recent IPv9=20
news from China. I thought I should just blog about it and point them to=20
this entry.

I heard of them first time back in 2001. The technology is developed by=20
=E5=8D=81=E8=BF=9B=E5=88=B6=E7=BD=91[1] called "=E6=95=B0=E5=AD=97=E5=9F=9F=
=E5=90=8D" which translate roughly to 'Numerical=20
Domain Name". They call it ADDA (All Digital Domain Address) and then=20
later IPv9. (Okay, I laughed back then too so don't hold back yourself ;-=
)

The technology as I understand can be summarise as follows: The 10=20
digits they refer to are phone numbers (China uses 10 digit local phone=20
number). The idea is that you can navigate the web by using phone=20
numbers in the browser. The technology is basically a modified DNS and=20
the business model is to get you to registered your phone numbers with th=
em.

So it isn't really IP as you would think. But despite these, they seem=20
pretty well connected in China and have support from Ministry of=20
Information Industry (MII) among others. However, I have not seen any=20
actual deployment anywhere. Lots of press release but thats about it.

ps: There is a article in Sina.com[2] explaining the technology pretty=20
well but it is written in Chinese.

[1] http://www.em777.net/
[2] http://tech.sina.com.cn/i/w/2004-06-28/2331380918.shtml

-James Seng

Tony Hain wrote:

> Sitting here in Seoul, Janet Sun (BII) said this is self-promotion of a
> single researcher looking to improve his funding. There is technical
> content, but no business content and the service providers are ignoring=
 it
> as a waste of time. Think of it as E-164 on steroids.
>=20
> Tony
>=20
>=20
>=20
>>-----Original Message-----
>>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>>Bill Manning
>>Sent: Monday, July 05, 2004 6:10 PM
>>To: jordi.palet@consulintel.es
>>Cc: ietf@ietf.org
>>Subject: Re: Chinese IPv9
>>
>>% Complete compilation of news at http://www.ist-
>>ipv6.org/modules.php?op=3Dmodload&name=3DNews&file=3Darticle&sid=3D622
>>%
>>% But I guess is an hoax ?
>>%
>>
>>	the site seems to be missing some of the chinese language
>>	reports... :)
>>	and based on (imho) more informed sources, this is not a
>>	hoax but a real effort.
>>
>>--bill
>>Opinions expressed may not even be mine by the time you read them, and
>>certainly don't reflect those of any other entity (legal or otherwise).
>>
>>_______________________________________________
>>Ietf mailing list
>>Ietf@ietf.org
>>https://www1.ietf.org/mailman/listinfo/ietf
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul  6 23:40:56 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18215
	for <ietf-archive@ietf.org>; Tue, 6 Jul 2004 23:40:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bi3In-0006BU-Hu
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 23:40:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi3Hp-0005pi-00
	for ietf-archive@ietf.org; Tue, 06 Jul 2004 23:39:57 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bi3Gm-00057b-00; Tue, 06 Jul 2004 23:38:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi26C-0005ER-SR; Tue, 06 Jul 2004 22:23:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bi12X-0003J7-I7
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 21:16:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09896
	for <ietf@ietf.org>; Tue, 6 Jul 2004 21:15:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bi12Q-0003wM-PD
	for ietf@ietf.org; Tue, 06 Jul 2004 21:15:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi11S-0003cV-00
	for ietf@ietf.org; Tue, 06 Jul 2004 21:14:55 -0400
Received: from smtp001.mail.ukl.yahoo.com ([217.12.11.32])
	by ietf-mx with smtp (Exim 4.12) id 1Bi10g-0002yO-00
	for ietf@ietf.org; Tue, 06 Jul 2004 21:14:06 -0400
Received: from unknown (HELO josephmushi) (mushyjc@202.114.82.43 with login)
	by smtp001.mail.ukl.yahoo.com with SMTP; 7 Jul 2004 01:13:35 -0000
From: "Joseph C. Mushi" <mushyjc@yahoo.co.uk>
To: <ietf@ietf.org>
Date: Wed, 7 Jul 2004 09:13:28 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2739.300
In-Reply-To: <20040706034320.5B87C872F4@mercury.lcs.mit.edu>
Thread-Index: AcRjgpbK2AZKfJKFQmKknxIXV/qQEgAOiCHQ
Message-Id: <E1Bi10g-0002yO-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Subject: RE: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

> From: "Tony Hain" <alh-ietf@tndh.net>

> There is technical content, but no business content and the service
> providers are ignoring it as a waste of time.

I think we still have many areas within IPv6 that need more researches and
concentration. Why doesn't this group join hand to insure full exploitation
of IPv6? In my opinion, I don't think whether China or the rest of World
Internet community needs more address space than that provided by IPv6 at
this time, as per their school of thought. As far as I know even China has
not yet full exploit IPv6.

Mushi.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 00:08:14 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19835
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 00:08:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bi3jD-0007ae-9j
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 00:08:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi3iK-0007BI-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 00:07:21 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bi3ge-0006Zi-00; Wed, 07 Jul 2004 00:05:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi2VW-0001L0-JY; Tue, 06 Jul 2004 22:50:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bi1n7-0002GV-Hw
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 22:04:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11891
	for <ietf@ietf.org>; Tue, 6 Jul 2004 22:04:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bi1n0-0004FO-K5
	for ietf@ietf.org; Tue, 06 Jul 2004 22:04:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi1mD-0003ty-00
	for ietf@ietf.org; Tue, 06 Jul 2004 22:03:15 -0400
Received: from mail.teal.net ([209.142.3.58] helo=teal.net)
	by ietf-mx with esmtp (Exim 4.12) id 1Bi1lI-0003Vh-00
	for ietf@ietf.org; Tue, 06 Jul 2004 22:02:16 -0400
Received: from [24.2.56.29] by teal.net [209.142.3.58] with SmartMax MailMax
	for ietf@ietf.org; Tue, 06 Jul 2004 18:58:34 -0700
X-SmartMax-AuthUser: jstrutt@pcpotato.com
From: "Jasen Strutt" <jstrutt@pcpotato.com>
To: "'Trang Nguyen'" <tnguyen@perfisans.com>,
        "'Sean Weekes'" <sean.weekes@iconz.net>, <support@ietf.org>,
        <ietf@ietf.org>
Date: Tue, 6 Jul 2004 19:02:05 -0700
Message-ID: <005001c463c6$68bba960$6401a8c0@SATELLITE>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
In-Reply-To: <BFEPLILMEGEJJBOLGNKHOEDBCAAA.tnguyen@perfisans.com>
Subject: RE: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jstrutt@pcpotato.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1915475174=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_60_70,
	HTML_FONTCOLOR_UNKNOWN,HTML_MESSAGE autolearn=no version=2.60

This is a multi-part message in MIME format.

--===============1915475174==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0051_01C4638B.BC5CD160"

This is a multi-part message in MIME format.

------=_NextPart_000_0051_01C4638B.BC5CD160
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Did anyone take mention of the virus infected file that was attached to the
email?  Did anyone take mention that the header information is junk? I hope
spam and phishing are not foreign terms to you. 

 

Please perform 20 seconds of due diligence prior to jumping to conclusions
and blasting the IETF list.  

 

Regards-

Jasen  

 

 

 

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Trang Nguyen
Sent: Tuesday, July 06, 2004 1:57 PM
To: Sean Weekes; support@ietf.org; ietf@ietf.org
Subject: RE: Email account utilization warning.

 

Same with me.  Please don't cut us off without reasonable explanation.

 

Regards,

 

Trang Nguyen

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]On Behalf Of Sean
Weekes
Sent: July 6, 2004 2:58 PM
To: support@ietf.org; ietf@ietf.org
Subject: RE: Email account utilization warning.

Please can you reinstate my account or at least explain in more detail the
reason for your actions here.

 

I'm not happy that you arbitrarily undertake this course of action without
prior notification or discussion.

 

I also am at a loss as to why you have done this.

 

Please can you elaborate.

 

 

Regards.
Sean Weekes

General Manager, ICONZ

www.iconz.co.nz

  

 

 


  _____  


From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
support@ietf.org
Sent: Tuesday, 6 July 2004 7:08 p.m.
To: ietf@ietf.org
Subject: Email account utilization warning.

Dear user of Ietf.org,

Your e-mail account has been temporary disabled because of unauthorized
access.

For more information see the attached file.

Kind regards,
    The Ietf.org team                 http://www.ietf.org 


------=_NextPart_000_0051_01C4638B.BC5CD160
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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


<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

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

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Did anyone take mention of the =
virus infected
file that was attached to the email? &nbsp;Did anyone take mention that =
the
header information is junk? I hope spam and phishing are not foreign =
terms to
you. </span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Please perform 20 seconds of due =
diligence
prior to jumping to conclusions and blasting the IETF list. =
&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Regards-</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Jasen&nbsp; </span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> =

ietf-bounces@ietf.org
[mailto:ietf-bounces@ietf.org] <b><span style=3D'font-weight:bold'>On =
Behalf Of </span></b>Trang
Nguyen<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, July 06, =
2004 1:57
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Sean Weekes; =
support@ietf.org;
ietf@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Email =
account
utilization warning.</span></font></p>

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

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Same with =
me.&nbsp;
Please don't cut us off without reasonable =
explanation.</span></font></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Regards,</span></=
font></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Trang =
Nguyen</span></font></p>

</div>

<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>

<p class=3DMsoNormal =
style=3D'margin-right:0in;margin-bottom:12.0pt;margin-left:
.5in'><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> =
ietf-bounces@ietf.org
[mailto:ietf-bounces@ietf.org]<b><span style=3D'font-weight:bold'>On =
Behalf Of </span></b>Sean
Weekes<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> July 6, 2004 2:58 =
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> support@ietf.org;
ietf@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Email =
account
utilization warning.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Please can you =
reinstate
my account or at least explain in more detail the reason for your =
actions here.</span></font></p>

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

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>I'm not happy =
that you
arbitrarily undertake this course of action without prior notification =
or
discussion.</span></font></p>

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

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>I also am at a =
loss as to
why you have done this.</span></font></p>

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

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Please can you =
elaborate.</span></font></p>

<div>

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

</div>

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

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>Regards.<br>
Sean Weekes</span></font></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>General Manager, ICONZ</span></font></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'><a =
href=3D"http://www.iconz.co.nz">www.iconz.co.nz</a><br>
<br>
&nbsp;</span></font> </p>

<div>

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

</div>

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

<div class=3DMsoNormal align=3Dcenter =
style=3D'margin-left:.5in;text-align:center'><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal =
style=3D'margin-right:0in;margin-bottom:12.0pt;margin-left:
.5in'><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:
Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'> ietf-bounces@ietf.org
[mailto:ietf-bounces@ietf.org] <b><span style=3D'font-weight:bold'>On =
Behalf Of </span></b>support@ietf.org<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, 6 July =
2004 7:08
p.m.<br>
<b><span style=3D'font-weight:bold'>To:</span></b> ietf@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Email account =
utilization
warning.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>Dear user of <b><span =
style=3D'font-weight:bold'>Ietf.org</span></b>,<br>
<br>
Your e-mail account has been temporary disabled because of unauthorized =
access.<br>
<br>
For more information see the attached file.<br>
<br>
Kind regards,<br>
&nbsp; &nbsp; The Ietf.org team &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; <a href=3D"http://www.ietf.org">http://www.ietf.org</a> =
</span></font></p>

</blockquote>

</div>

</body>

</html>

------=_NextPart_000_0051_01C4638B.BC5CD160--




--===============1915475174==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1915475174==--





From ietf-bounces@ietf.org  Wed Jul  7 00:18:10 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20490
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 00:18:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bi3sp-0003O0-5X
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 00:18:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi3rp-00031c-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 00:17:09 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bi3qx-0002Mj-00; Wed, 07 Jul 2004 00:16:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi2iT-0003pI-QJ; Tue, 06 Jul 2004 23:03:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bi26v-0005HO-5h
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 22:24:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13532
	for <ietf@ietf.org>; Tue, 6 Jul 2004 22:24:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bi26j-0003jW-8n
	for ietf@ietf.org; Tue, 06 Jul 2004 22:24:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi25e-0003KE-00
	for ietf@ietf.org; Tue, 06 Jul 2004 22:23:18 -0400
Received: from ms-smtp-01-smtplb.rdc-nyc.rr.com ([24.29.109.5]
	helo=ms-smtp-01.rdc-nyc.rr.com) by ietf-mx with esmtp (Exim 4.12)
	id 1Bi24S-0002w4-00
	for ietf@ietf.org; Tue, 06 Jul 2004 22:22:04 -0400
Received: from jb (24-168-69-77.si.rr.com [24.168.69.77])
	by ms-smtp-01.rdc-nyc.rr.com (8.12.10/8.12.7) with SMTP id
	i672M1S6026520
	for <ietf@ietf.org>; Tue, 6 Jul 2004 22:22:01 -0400 (EDT)
From: "John Buda" <jbuda@si.rr.com>
To: <ietf@ietf.org>
Date: Tue, 6 Jul 2004 22:22:11 -0400
Message-ID: <LIEIIBKFLHADFDBCGDIHCELCCMAA.jbuda@si.rr.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-reply-to: <BFEPLILMEGEJJBOLGNKHOEDBCAAA.tnguyen@perfisans.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-Virus-Scanned: Symantec AntiVirus Scan Engine
Subject: RE: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1084522905=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_40_50,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60

This is a multi-part message in MIME format.

--===============1084522905==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_014C_01C463A7.AEDB1C60"

This is a multi-part message in MIME format.

------=_NextPart_000_014C_01C463A7.AEDB1C60
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Remain calm members,
Its a bogus email.....

Its not from the IETF..

Someone is just having fun with the IETF email list...

John Buda
------=_NextPart_000_014C_01C463A7.AEDB1C60
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D265271902-07072004><FONT face=3DArial color=3D#0000ff =
size=3D2>Remain=20
calm members,</FONT></SPAN></DIV>
<DIV><SPAN class=3D265271902-07072004><FONT face=3DArial color=3D#0000ff =
size=3D2>Its a=20
bogus email.....</FONT></SPAN></DIV>
<DIV><SPAN class=3D265271902-07072004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D265271902-07072004><FONT face=3DArial color=3D#0000ff =
size=3D2>Its=20
not from the IETF..</FONT></SPAN></DIV>
<DIV><SPAN class=3D265271902-07072004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D265271902-07072004><FONT face=3DArial color=3D#0000ff =

size=3D2>Someone is just having fun with the IETF email=20
list...</FONT></SPAN></DIV>
<DIV><SPAN class=3D265271902-07072004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D265271902-07072004><FONT face=3DArial color=3D#0000ff =
size=3D2>John=20
Buda</FONT></SPAN></DIV></BODY></HTML>

------=_NextPart_000_014C_01C463A7.AEDB1C60--



--===============1084522905==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1084522905==--




From ietf-bounces@ietf.org  Wed Jul  7 01:09:12 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23742
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 01:09:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bi4gC-0006Au-61
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 01:09:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi4fB-0005nF-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 01:08:09 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bi4eG-000562-00; Wed, 07 Jul 2004 01:07:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi44y-0002bN-Kj; Wed, 07 Jul 2004 00:30:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bi3Rk-0002oV-6H
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 23:50:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18849
	for <ietf@ietf.org>; Tue, 6 Jul 2004 23:50:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bi3Rd-0001j0-65
	for ietf@ietf.org; Tue, 06 Jul 2004 23:50:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi3Qk-0001P0-00
	for ietf@ietf.org; Tue, 06 Jul 2004 23:49:11 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65]
	helo=arneill-py.sacramento.ca.us) by ietf-mx with esmtp (Exim 4.12)
	id 1Bi3Pr-0000iA-00
	for ietf@ietf.org; Tue, 06 Jul 2004 23:48:15 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Tue, 6 Jul 2004 20:47:45 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB27F@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: Email account utilization warning.
thread-index: AcRj1Ms7PyIYI1KISrenlLDjMuFqcwAADdOA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <jstrutt@pcpotato.com>, "Trang Nguyen" <tnguyen@perfisans.com>,
        "Sean Weekes" <sean.weekes@iconz.net>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: RE: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

Darn Jasen, you just stopped the entertainment. It's a lot of fun =
watching how many could be caught by phishing.

Michel.

________________________________________
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Jasen Strutt
Sent: Tuesday, July 06, 2004 7:02 PM
To: 'Trang Nguyen'; 'Sean Weekes'; support@ietf.org; ietf@ietf.org
Subject: RE: Email account utilization warning.

Did anyone take mention of the virus infected file that was attached to =
the email? =A0Did anyone take mention that the header information is =
junk? I hope spam and phishing are not foreign terms to you.=20
=A0
Please perform 20 seconds of due diligence prior to jumping to =
conclusions and blasting the IETF list. =A0
=A0
Regards-
Jasen=A0=20
=A0
=A0
=A0
-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Trang Nguyen
Sent: Tuesday, July 06, 2004 1:57 PM
To: Sean Weekes; support@ietf.org; ietf@ietf.org
Subject: RE: Email account utilization warning.
=A0
Same with me.=A0 Please don't cut us off without reasonable explanation.
=A0
Regards,
=A0
Trang Nguyen
-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]On Behalf Of =
Sean Weekes
Sent: July 6, 2004 2:58 PM
To: support@ietf.org; ietf@ietf.org
Subject: RE: Email account utilization warning.
Please can you reinstate my account or at least explain in more detail =
the reason for your actions here.
=A0
I'm not happy that you arbitrarily undertake this course of action =
without prior notification or discussion.
=A0
I also am at a loss as to why you have done this.
=A0
Please can you elaborate.
=A0
=A0
Regards.
Sean Weekes
General Manager, ICONZ
www.iconz.co.nz

=A0=20
=A0
=A0
________________________________________
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
support@ietf.org
Sent: Tuesday, 6 July 2004 7:08 p.m.
To: ietf@ietf.org
Subject: Email account utilization warning.
Dear user of Ietf.org,

Your e-mail account has been temporary disabled because of unauthorized =
access.

For more information see the attached file.

Kind regards,
=A0 =A0 The Ietf.org team =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
http://www.ietf.org=20

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 01:10:11 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23835
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 01:10:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bi4h8-0006ZC-9u
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 01:10:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi4gB-0006Am-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 01:09:11 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bi4fB-0005Sv-00; Wed, 07 Jul 2004 01:08:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi3ur-00080m-8F; Wed, 07 Jul 2004 00:20:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bi3BO-0008MC-1W
	for ietf@megatron.ietf.org; Tue, 06 Jul 2004 23:33:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17965
	for <ietf@ietf.org>; Tue, 6 Jul 2004 23:33:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bi3BH-0003az-2K
	for ietf@ietf.org; Tue, 06 Jul 2004 23:33:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi3AH-0003G1-00
	for ietf@ietf.org; Tue, 06 Jul 2004 23:32:09 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1Bi39a-0002fp-00
	for ietf@ietf.org; Tue, 06 Jul 2004 23:31:26 -0400
Received: (qmail 44522 invoked from network); 7 Jul 2004 03:34:33 -0000
Received: from vaio.hpcl.titech.ac.jp (HELO necom830.hpcl.titech.ac.jp)
	(131.112.32.134)
	by necom830.hpcl.titech.ac.jp with SMTP; 7 Jul 2004 03:34:33 -0000
Message-ID: <40EB6FD1.90504@necom830.hpcl.titech.ac.jp>
Date: Wed, 07 Jul 2004 12:36:49 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Tony Hain <alh-ietf@tndh.net>
References: <E1Bhfut-0004gV-00@ietf-mx>
In-Reply-To: <E1Bhfut-0004gV-00@ietf-mx>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, jordi.palet@consulintel.es,
        "'Bill Manning'" <bmanning@ISI.EDU>
Subject: Re: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Tony Hain wrote:

> There is technical
> content, but no business content and the service providers are ignoring it
> as a waste of time.

So, it's almost identical to IPv6.

							Masataka Ohta



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 03:23:15 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27246
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 03:23:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bi6lv-0004ev-Dk
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 03:23:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi6j8-0003k8-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 03:20:22 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bi6hw-0003MV-00; Wed, 07 Jul 2004 03:19:08 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Bi6hg-0007dC-71; Wed, 07 Jul 2004 03:18:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi5rl-00008k-1m; Wed, 07 Jul 2004 02:25:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bi5Ua-00061w-4O
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 02:01:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27446
	for <ietf@ietf.org>; Wed, 7 Jul 2004 02:01:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bi5US-00013w-V8
	for ietf@ietf.org; Wed, 07 Jul 2004 02:01:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi5TZ-0000iv-00
	for ietf@ietf.org; Wed, 07 Jul 2004 02:00:14 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1Bi5Sm-00003g-00
	for ietf@ietf.org; Wed, 07 Jul 2004 01:59:24 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0G00B4PWM5LL@mailout2.samsung.com> for ietf@ietf.org; Wed,
	07 Jul 2004 14:58:53 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0G00JWNWKIYV@mailout2.samsung.com> for ietf@ietf.org;
	Wed, 07 Jul 2004 14:57:54 +0900 (KST)
Received: from LocalHost ([168.219.202.103])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0G00J34WKHBB@mmp2.samsung.com> for
	ietf@ietf.org; Wed, 07 Jul 2004 14:57:53 +0900 (KST)
Date: Wed, 07 Jul 2004 14:58:46 +0900
From: Soohong Daniel Park <soohong.park@samsung.com>
In-reply-to: <40EB6FD1.90504@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>,
        Tony Hain <alh-ietf@tndh.net>
Message-id: <EDELKJDGPGNIPOAOHMNPCEOPFNAA.soohong.park@samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Cc: ietf@ietf.org, jordi.palet@consulintel.es,
        "'Bill Manning'" <bmanning@ISI.EDU>
Subject: RE: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT


> So, it's almost identical to IPv6.

It's very interesting indication. Can you show
me several clues why you think so.

- Daniel (Soohong Daniel Park)
- Mobile Platform Lab. Samsung Electronics.

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]On 
> Behalf Of Masataka Ohta
> Sent: Wednesday, July 07, 2004 12:37 PM
> To: Tony Hain
> Cc: ietf@ietf.org; jordi.palet@consulintel.es; 'Bill Manning'
> Subject: Re: Chinese IPv9
> 
> 
> Tony Hain wrote:
> 
> > There is technical
> > content, but no business content and the service providers are 
> ignoring it
> > as a waste of time.
> 

> 
> 							Masataka Ohta
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 03:25:40 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27916
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 03:25:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bi6oG-0005RQ-D2
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 03:25:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi6ls-0004dv-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 03:23:13 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bi6j6-0003jq-00; Wed, 07 Jul 2004 03:20:20 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Bi6j7-0007m7-FV; Wed, 07 Jul 2004 03:20:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi5rm-00009m-Fs; Wed, 07 Jul 2004 02:25:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bi5Uf-00065F-Ar
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 02:01:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27539
	for <ietf@ietf.org>; Wed, 7 Jul 2004 02:01:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bi5UY-00014h-3t
	for ietf@ietf.org; Wed, 07 Jul 2004 02:01:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi5Tc-0000jW-00
	for ietf@ietf.org; Wed, 07 Jul 2004 02:00:17 -0400
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx with esmtp (Exim 4.12) id 1Bi5TE-0000OQ-00
	for ietf@ietf.org; Wed, 07 Jul 2004 01:59:52 -0400
Received: from mobilebill (c-24-20-39-234.client.comcast.net[24.20.39.234])
	by comcast.net (rwcrmhc12) with SMTP
	id <2004070705592201400jctdse>; Wed, 7 Jul 2004 05:59:22 +0000
From: "bill" <bill@strahm.net>
To: <ietf@ietf.org>
Date: Tue, 6 Jul 2004 22:59:09 -0700
Message-ID: <01ce01c463e7$887e24a0$6601a8c0@mobilebill>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <BFEPLILMEGEJJBOLGNKHOEDBCAAA.tnguyen@perfisans.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
Subject: RE: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2092080834=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_40_50,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60

This is a multi-part message in MIME format.

--===============2092080834==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_01CF_01C463AC.DC1F4CA0"

This is a multi-part message in MIME format.

------=_NextPart_000_01CF_01C463AC.DC1F4CA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

You would think this crowd is used to Joe Jobs and Phishing.  Of course
I knew the internet was coming to an end when Steve B. put up the Code
Red statistics in London...
 
You would think at least this crowd would learn
 
Bill

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Trang Nguyen
Sent: Tuesday, July 06, 2004 1:57 PM
To: Sean Weekes; support@ietf.org; ietf@ietf.org
Subject: RE: Email account utilization warning.


Same with me.  Please don't cut us off without reasonable explanation.
 
Regards,
 
Trang Nguyen

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]On Behalf Of
Sean Weekes
Sent: July 6, 2004 2:58 PM
To: support@ietf.org; ietf@ietf.org
Subject: RE: Email account utilization warning.


Please can you reinstate my account or at least explain in more detail
the reason for your actions here.
 
I'm not happy that you arbitrarily undertake this course of action
without prior notification or discussion.
 
I also am at a loss as to why you have done this.
 
Please can you elaborate.
 


Regards.
Sean Weekes

General Manager, ICONZ

w <http://www.iconz.co.nz> ww.iconz.co.nz

  

 

  _____  

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
support@ietf.org
Sent: Tuesday, 6 July 2004 7:08 p.m.
To: ietf@ietf.org
Subject: Email account utilization warning.


Dear user of Ietf.org,

Your e-mail account has been temporary disabled because of unauthorized
access.

For more information see the attached file.

Kind regards,
    The Ietf.org team                 http://www.ietf.org 


------=_NextPart_000_01CF_01C463AC.DC1F4CA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D009265505-07072004><FONT face=3DArial color=3D#0000ff =
size=3D2>You=20
would think this crowd is used to Joe Jobs and Phishing.&nbsp; Of course =
I knew=20
the internet was coming to an end when Steve B. put up the Code Red =
statistics=20
in London...</FONT></SPAN></DIV>
<DIV><SPAN class=3D009265505-07072004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D009265505-07072004><FONT face=3DArial color=3D#0000ff =
size=3D2>You=20
would think at least this crowd would learn</FONT></SPAN></DIV>
<DIV><SPAN class=3D009265505-07072004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D009265505-07072004><FONT face=3DArial color=3D#0000ff =

size=3D2>Bill</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <B>On Behalf Of =
</B>Trang=20
  Nguyen<BR><B>Sent:</B> Tuesday, July 06, 2004 1:57 PM<BR><B>To:</B> =
Sean=20
  Weekes; support@ietf.org; ietf@ietf.org<BR><B>Subject:</B> RE: Email =
account=20
  utilization warning.<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D196255420-06072004><FONT face=3DArial =
color=3D#0000ff size=3D2>Same=20
  with me.&nbsp; Please don't cut us off without reasonable=20
  explanation.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D196255420-06072004><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D196255420-06072004><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Regards,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D196255420-06072004><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D196255420-06072004><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Trang Nguyen</FONT></SPAN></DIV>
  <BLOCKQUOTE>
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> =
ietf-bounces@ietf.org=20
    [mailto:ietf-bounces@ietf.org]<B>On Behalf Of </B>Sean=20
    Weekes<BR><B>Sent:</B> July 6, 2004 2:58 PM<BR><B>To:</B> =
support@ietf.org;=20
    ietf@ietf.org<BR><B>Subject:</B> RE: Email account utilization=20
    warning.<BR><BR></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>Please can you reinstate my account or at =
least explain=20
    in more detail the reason for your actions here.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>I'm not happy that you arbitrarily =
undertake this=20
    course of action without prior notification or=20
    discussion.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>I also am at a loss as to why you have done =

    this.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D182505518-06072004><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>Please can you =
elaborate.</FONT></SPAN></DIV>
    <DIV>&nbsp;</DIV><BR>
    <P><FONT size=3D2>Regards.<BR>Sean<SPAN class=3D182505518-06072004>=20
    Weekes</SPAN></FONT></P>
    <P><SPAN class=3D182505518-06072004></SPAN><SPAN=20
    class=3D182505518-06072004></SPAN><FONT size=3D2>G<SPAN=20
    class=3D182505518-06072004>eneral Manager, ICONZ</SPAN></FONT></P>
    <P><SPAN class=3D182505518-06072004></SPAN><SPAN=20
    class=3D182505518-06072004></SPAN><FONT size=3D2><A=20
    href=3D"http://www.iconz.co.nz">w<SPAN=20
    =
class=3D182505518-06072004>ww.iconz.co.nz</A></SPAN><BR><BR>&nbsp;</FONT>=
 </P>
    <DIV>&nbsp;</DIV><BR>
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> ietf-bounces@ietf.org=20
    [mailto:ietf-bounces@ietf.org] <B>On Behalf Of=20
    </B>support@ietf.org<BR><B>Sent:</B> Tuesday, 6 July 2004 7:08=20
    p.m.<BR><B>To:</B> ietf@ietf.org<BR><B>Subject:</B> Email account=20
    utilization warning.<BR></FONT><BR></DIV>
    <DIV></DIV>Dear user of <B>Ietf.org</B>,<BR><BR>Your e-mail account =
has been=20
    temporary disabled because of unauthorized access.<BR><BR>For more=20
    information see the attached file.<BR><BR>Kind regards,<BR>&nbsp; =
&nbsp; The=20
    Ietf.org team &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; <A=20
    href=3D"http://www.ietf.org">http://www.ietf.org</A>=20
</BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_01CF_01C463AC.DC1F4CA0--




--===============2092080834==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============2092080834==--





From ietf-bounces@ietf.org  Wed Jul  7 03:45:32 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28858
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 03:45:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bi77U-0003m8-SD
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 03:45:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi74p-0002ox-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 03:42:48 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bi71L-0001t4-03; Wed, 07 Jul 2004 03:39:11 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Bi6pC-0007sa-06; Wed, 07 Jul 2004 03:26:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi6Cc-00054d-Nn; Wed, 07 Jul 2004 02:46:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bi5or-0007bs-Ts
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 02:22:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16297
	for <ietf@ietf.org>; Wed, 7 Jul 2004 02:22:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bi5ok-0000L9-Rw
	for ietf@ietf.org; Wed, 07 Jul 2004 02:22:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi5nj-0007nN-00
	for ietf@ietf.org; Wed, 07 Jul 2004 02:21:04 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1Bi5mj-00079I-00
	for ietf@ietf.org; Wed, 07 Jul 2004 02:20:01 -0400
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i676JKNp018029
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 7 Jul 2004 02:19:25 -0400
Date: Wed, 7 Jul 2004 02:19:20 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Michel Py <michel@arneill-py.sacramento.ca.us>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB27F@server2003.arneill-py.sacramento.ca.us>
Message-ID: <Pine.LNX.4.44.0407070200310.17487-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by cirrus.av8.net id
	i676JKNp018029
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org, jstrutt@pcpotato.com
Subject: RE: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

Given the recent unreasonable behavior by IETF staff where they really ar=
e
blocking blocking of email from members, it is not very unreasonable to b=
e
fooled by such a thing.  People have come to expect this from the IETF.

Dean Anderson=20
Av8 Internet, Inc=20

P.S. I am still blocked from emailing DNS WG chair, and prevented from
registering complaint about improper DNS WG RFC process activity by ISC
and DNS WG chair Austein, because the IETF chairman Alvestrand demands
that such complaints be made offlist, yet chairman Alvestrand refuses to
require the WG Chairs to accept email from participants.  Under chairman
Alvestrand's leadership, the IETF can choose to ignore complaints based o=
n
the participant, rather than the merit of the complaint.  And Although
this runs contrary to every stated principle of the IETF, contrary to man=
y
suggestions of many other participants, contrary to civil courtesy, and
contrary to lawful behavior, chairman Alvestrand is not moved from his
course.  He leaves us no choice but to engage lawyers against the IETF. =20
This is very sad.

On Tue, 6 Jul 2004, Michel Py wrote:

> Darn Jasen, you just stopped the entertainment. It's a lot of fun watch=
ing how many could be caught by phishing.
>=20
> Michel.
>=20
> ________________________________________
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of=
 Jasen Strutt
> Sent: Tuesday, July 06, 2004 7:02 PM
> To: 'Trang Nguyen'; 'Sean Weekes'; support@ietf.org; ietf@ietf.org
> Subject: RE: Email account utilization warning.
>=20
> Did anyone take mention of the virus infected file that was attached to=
 the email? =A0Did anyone take mention that the header information is jun=
k? I hope spam and phishing are not foreign terms to you.=20
> =A0
> Please perform 20 seconds of due diligence prior to jumping to conclusi=
ons and blasting the IETF list. =A0
> =A0
> Regards-
> Jasen=A0=20
> =A0
> =A0
> =A0
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of=
 Trang Nguyen
> Sent: Tuesday, July 06, 2004 1:57 PM
> To: Sean Weekes; support@ietf.org; ietf@ietf.org
> Subject: RE: Email account utilization warning.
> =A0
> Same with me.=A0 Please don't cut us off without reasonable explanation.
> =A0
> Regards,
> =A0
> Trang Nguyen
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]On Behalf Of =
Sean Weekes
> Sent: July 6, 2004 2:58 PM
> To: support@ietf.org; ietf@ietf.org
> Subject: RE: Email account utilization warning.
> Please can you reinstate my account or at least explain in more detail =
the reason for your actions here.
> =A0
> I'm not happy that you arbitrarily undertake this course of action with=
out prior notification or discussion.
> =A0
> I also am at a loss as to why you have done this.
> =A0
> Please can you elaborate.
> =A0
> =A0
> Regards.
> Sean Weekes
> General Manager, ICONZ
> www.iconz.co.nz
>=20
> =A0=20
> =A0
> =A0
> ________________________________________
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of=
 support@ietf.org
> Sent: Tuesday, 6 July 2004 7:08 p.m.
> To: ietf@ietf.org
> Subject: Email account utilization warning.
> Dear user of Ietf.org,
>=20
> Your e-mail account has been temporary disabled because of unauthorized=
 access.
>=20
> For more information see the attached file.
>=20
> Kind regards,
> =A0 =A0 The Ietf.org team =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://www.ie=
tf.org=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 09:59:26 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20178
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 09:59:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiCxM-0003NP-6H
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 09:59:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiCwK-00031N-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 09:58:24 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiCvK-0002Me-00; Wed, 07 Jul 2004 09:57:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiC1J-0006zQ-Ew; Wed, 07 Jul 2004 08:59:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiBf7-0000vC-GJ
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 08:36:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15225
	for <ietf@ietf.org>; Wed, 7 Jul 2004 08:36:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiBf1-0005Sq-TH
	for ietf@ietf.org; Wed, 07 Jul 2004 08:36:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiBeH-000582-00
	for ietf@ietf.org; Wed, 07 Jul 2004 08:35:42 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12) id 1BiBdR-0004mo-00
	for ietf@ietf.org; Wed, 07 Jul 2004 08:34:49 -0400
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id
	i67CYmnE012453
	for <ietf@ietf.org>; Wed, 7 Jul 2004 13:34:48 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id NAA00918
	for <ietf@ietf.org>; Wed, 7 Jul 2004 13:34:43 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i67CYhR15544
	for ietf@ietf.org; Wed, 7 Jul 2004 13:34:43 +0100
Date: Wed, 7 Jul 2004 13:34:43 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Message-ID: <20040707123443.GI8470@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more
	information
X-ECS-MailScanner: Found to be clean
Subject: xml2rfc and new RFC3667 requirements
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

I guess many people will use these tools already, but I thought I'd
just post that the excellent xml2rfc tool now supports the RFC3667
requirements as per ftp://ftp.ietf.org/ietf/1id-guidelines.txt

See http://xml.resource.org/, v1.24.

You just need to select the full3667 ipr option, e.g.

<rfc ipr="full3667" category="...

in your XML, where you probably had "full2026" beforehand.

In other words, you must upgrade your xml2rfc before the I-D cutoff rush
next week :)

Tim

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 13:30:02 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02596
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 13:30:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiGFB-0003Fy-57
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 13:30:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiGDj-0002ZD-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 13:28:35 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiGCD-000258-01; Wed, 07 Jul 2004 13:27:02 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BiFxv-0006TM-5F; Wed, 07 Jul 2004 13:12:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiEpx-0008Fe-Pj; Wed, 07 Jul 2004 11:59:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiECy-000665-IB
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 11:19:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25500
	for <ietf@ietf.org>; Wed, 7 Jul 2004 11:19:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiECs-0007Kh-P9
	for ietf@ietf.org; Wed, 07 Jul 2004 11:19:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiEC3-00071D-00
	for ietf@ietf.org; Wed, 07 Jul 2004 11:18:44 -0400
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12) id 1BiEB9-0006YK-00
	for ietf@ietf.org; Wed, 07 Jul 2004 11:17:47 -0400
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id AC72B83AB; Wed,  7 Jul 2004 17:17:43 +0200 (CEST)
Received: from purgatory.unfix.org ([127.0.0.1])
	by localhost (purgatory [127.0.0.1]) (amavisd-new, port 10024)
	with SMTP id 08825-39; Wed, 7 Jul 2004 17:17:24 +0200 (CEST)
Received: from [9.4.70.109] (pat.zurich.ibm.com [195.176.20.45])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 129F28583; Wed,  7 Jul 2004 17:16:01 +0200 (CEST)
From: Jeroen Massar <jeroen@unfix.org>
To: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20040707123443.GI8470@login.ecs.soton.ac.uk>
References: <20040707123443.GI8470@login.ecs.soton.ac.uk>
Organization: Unfix
Message-Id: <1089213359.21961.125.camel@segesta.zurich.ibm.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) 
Date: Wed, 07 Jul 2004 17:15:59 +0200
X-Virus-Scanned: purgatory.unfix.org - http://unfix.org
Cc: ietf@ietf.org
Subject: Re: xml2rfc and new RFC3667 requirements
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1436832879=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


--===============1436832879==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-Al1hGNfEue1rJfKB+s2E"


--=-Al1hGNfEue1rJfKB+s2E
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2004-07-07 at 14:34, Tim Chown wrote:
> I guess many people will use these tools already, but I thought I'd
> just post that the excellent xml2rfc tool now supports the RFC3667
> requirements as per ftp://ftp.ietf.org/ietf/1id-guidelines.txt
>=20
> See http://xml.resource.org/, v1.24.
>=20
> You just need to select the full3667 ipr option, e.g.
>=20
> <rfc ipr=3D"full3667" category=3D"...
>=20
> in your XML, where you probably had "full2026" beforehand.
>=20
> In other words, you must upgrade your xml2rfc before the I-D cutoff rush
> next week :)

They are already complaining about that since monday with a 'read that
url about the new guidelines', while they might just mention that you
could turn the ipr option on to the new RFC. You can actually just set
the ipr option to 999999 and xml2rfc will be compliant for ever as it
just checks if it is lower than a certain version when including some
text.

Quite odd actually, one can't send internet-drafts@ pgp-signed email
because their pegasus mua's can't read it but they do dare to complain
about some legal crap in a technical document. Submitting .xml's is not
an option either apparently, which I would think would be much easier
for them to be checked "ah they have ipr=3D wrong". xml2rfc could/should
warn about this btw, but then again how many times does this change.

Greets,
 Jeroen

PS: For debian users, it is not in there (yet)....


--=-Al1hGNfEue1rJfKB+s2E
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iD8DBQBA7BOvKaooUjM+fCMRAlLXAJwPhOYXm/ardE+C4tA3s8J0k5+9KwCfU+RR
j37HrlGhSmzUVfZP4tSevyw=
=yHvM
-----END PGP SIGNATURE-----

--=-Al1hGNfEue1rJfKB+s2E--



--===============1436832879==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1436832879==--




From ietf-bounces@ietf.org  Wed Jul  7 13:37:37 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03198
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 13:37:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiGMU-00061f-2p
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 13:37:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiGLT-0005ft-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 13:36:36 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiGKT-00053A-00; Wed, 07 Jul 2004 13:35:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiFUU-00055B-72; Wed, 07 Jul 2004 12:41:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiEbD-0004GN-JJ
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 11:44:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26811
	for <ietf@ietf.org>; Wed, 7 Jul 2004 11:44:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiEb7-000011-RS
	for ietf@ietf.org; Wed, 07 Jul 2004 11:44:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiEaH-0007Ur-00
	for ietf@ietf.org; Wed, 07 Jul 2004 11:43:46 -0400
Received: from twinlark.arctic.org ([168.75.98.6])
	by ietf-mx with esmtp (Exim 4.12) id 1BiEZV-000790-00
	for ietf@ietf.org; Wed, 07 Jul 2004 11:42:57 -0400
Received: (qmail 31561 invoked from network); 7 Jul 2004 15:42:45 -0000
Received: from unknown (HELO ?55.55.1.11?) (AUTH mark) (64.60.241.211)
	by 168.75.98.6 with SMTP; 7 Jul 2004 15:42:45 -0000
Message-ID: <40EC1AE8.7040908@spandrel.com>
Date: Wed, 07 Jul 2004 08:46:48 -0700
From: Mark Durham <mdurham@spandrel.com>
User-Agent: Mozilla Thunderbird 0.7.1 (Macintosh/20040626)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
References: <Pine.LNX.4.44.0407070200310.17487-100000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0407070200310.17487-100000@cirrus.av8.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, ietf@ietf.org,
        jstrutt@pcpotato.com
Subject: Re: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Could we try to keep our narcissistic eye on the ball here?

I realize that the only thing on this list that matters to you is you, 
and normally I do what I imagine most of the list is doing: I suffer 
your rants in silence. But recognizing this stuff is actually important, 
and if there are people on the IETF list who don't, that's a situation 
that cries out for attention. Please, for once, let's assume that you 
are *not* the topic, and stay on whatever the topic actually is. You can 
trot out your personal demons (or daemons, for that matter) under some 
other subject line ... and, by all evidence, you certainly will. In the 
meantime, let's not treat every message on this list as your personal 
song cue.

Is this really too much to ask?


Dean Anderson wrote:

>Given the recent unreasonable behavior by IETF staff where they really are
>blocking blocking of email from members, it is not very unreasonable to be
>fooled by such a thing.  People have come to expect this from the IETF.
>
>Dean Anderson 
>Av8 Internet, Inc 
>
>P.S. I am still blocked from emailing DNS WG chair, and prevented from
>registering complaint about improper DNS WG RFC process activity by ISC
>and DNS WG chair Austein, because the IETF chairman Alvestrand demands
>that such complaints be made offlist, yet chairman Alvestrand refuses to
>require the WG Chairs to accept email from participants.  Under chairman
>Alvestrand's leadership, the IETF can choose to ignore complaints based on
>the participant, rather than the merit of the complaint.  And Although
>this runs contrary to every stated principle of the IETF, contrary to many
>suggestions of many other participants, contrary to civil courtesy, and
>contrary to lawful behavior, chairman Alvestrand is not moved from his
>course.  He leaves us no choice but to engage lawyers against the IETF.  
>This is very sad.
>
>On Tue, 6 Jul 2004, Michel Py wrote:
>
>  
>
>>Darn Jasen, you just stopped the entertainment. It's a lot of fun watching how many could be caught by phishing.
>>
>>Michel.
>>
>>________________________________________
>>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Jasen Strutt
>>Sent: Tuesday, July 06, 2004 7:02 PM
>>To: 'Trang Nguyen'; 'Sean Weekes'; support@ietf.org; ietf@ietf.org
>>Subject: RE: Email account utilization warning.
>>
>>Did anyone take mention of the virus infected file that was attached to the email?  Did anyone take mention that the header information is junk? I hope spam and phishing are not foreign terms to you. 
>> 
>>Please perform 20 seconds of due diligence prior to jumping to conclusions and blasting the IETF list.  
>> 
>>Regards-
>>Jasen  
>> 
>> 
>> 
>>-----Original Message-----
>>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Trang Nguyen
>>Sent: Tuesday, July 06, 2004 1:57 PM
>>To: Sean Weekes; support@ietf.org; ietf@ietf.org
>>Subject: RE: Email account utilization warning.
>> 
>>Same with me.  Please don't cut us off without reasonable explanation.
>> 
>>Regards,
>> 
>>Trang Nguyen
>>-----Original Message-----
>>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]On Behalf Of Sean Weekes
>>Sent: July 6, 2004 2:58 PM
>>To: support@ietf.org; ietf@ietf.org
>>Subject: RE: Email account utilization warning.
>>Please can you reinstate my account or at least explain in more detail the reason for your actions here.
>> 
>>I'm not happy that you arbitrarily undertake this course of action without prior notification or discussion.
>> 
>>I also am at a loss as to why you have done this.
>> 
>>Please can you elaborate.
>> 
>> 
>>Regards.
>>Sean Weekes
>>General Manager, ICONZ
>>www.iconz.co.nz
>>
>>  
>> 
>> 
>>________________________________________
>>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of support@ietf.org
>>Sent: Tuesday, 6 July 2004 7:08 p.m.
>>To: ietf@ietf.org
>>Subject: Email account utilization warning.
>>Dear user of Ietf.org,
>>
>>Your e-mail account has been temporary disabled because of unauthorized access.
>>
>>For more information see the attached file.
>>
>>Kind regards,
>>    The Ietf.org team                 http://www.ietf.org 
>>
>>_______________________________________________
>>Ietf mailing list
>>Ietf@ietf.org
>>https://www1.ietf.org/mailman/listinfo/ietf
>>
>>    
>>
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf
>
>  
>


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 15:11:51 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09571
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 15:11:51 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiHpg-0006ii-6x
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 15:11:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiHow-0006OX-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 15:11:07 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiHo7-000603-00; Wed, 07 Jul 2004 15:10:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiGri-0001tJ-7X; Wed, 07 Jul 2004 14:09:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiGLd-0001WY-Qh
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 13:36:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03132
	for <ietf@ietf.org>; Wed, 7 Jul 2004 13:36:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiGLX-0005gY-PP
	for ietf@ietf.org; Wed, 07 Jul 2004 13:36:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiGKZ-0005Ll-00
	for ietf@ietf.org; Wed, 07 Jul 2004 13:35:40 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1BiGJf-0004j6-00
	for ietf@ietf.org; Wed, 07 Jul 2004 13:34:43 -0400
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i67HYBCo030673
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 7 Jul 2004 13:34:11 -0400
Date: Wed, 7 Jul 2004 13:34:11 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Mark Durham <mdurham@spandrel.com>
In-Reply-To: <40EC1AE8.7040908@spandrel.com>
Message-ID: <Pine.LNX.4.44.0407071255240.29649-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, ietf@ietf.org,
        jstrutt@pcpotato.com
Subject: Re: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Mark, 

To fool people, the "phish" has to be plausible.  In this case, people
have come to expect capricious behavior from the IETF and so the
"phishing" claim of turning off email capriciously isn't out of the realm
of the expected behavior.  People saw the IETF do it before, and expect it
might might happen again.

"Dean Anderson" is not the topic: The IETF principles are the topic;  The
IETF rules are the topic; The misbehavior by people including the IETF
leadership is the topic.  Those who don't want to address the problems try
to portray this as about Dean Anderson, or about Dan Bernstein, or about
whoever else is being abused at the moment.  It's not about Dean Anderson;
It's not about Dan Bernstein; Its not those other innocent people defamed
and disparaged by a select few abusers.  Its about abusive behavior by a
select group, and the willfull, repeated, and perfidious failure of the
leadership to address the abuse, and the participation by the leadership
in the abuse.

It should not be too much to ask that the IETF Leadership follow the IETF
rules and the IETF principles.  Is that too much to ask?  When the
leadership acts capriciously, frivolously, perfidiously and acts contrary
to the rules and principles of the IETF, this behavior is observed by
others.  These things don't happen in a vacuum.  The complaints of Dean
Anderson, or Dan Bernstein, or of anyone else do not bring dishonor to the
IETF. Only the behavior by the leadership brings disrespect and dishonor
to the IETF.  And we see the effects of that: People come to expect
capricious behavior from the IETF and so the "phishing" premise isn't out
of the realm of the expected behavior.  People saw the IETF do it before,
and expect it might might happen again.  Solve the problem: Obey the IETF
principles and rules. Then such "phishes" will be out of character, and 
people would be more suspicious of such a "phish".


As I said offlist to Mark Smith:

  From: Dean Anderson <dean@av8.com>
  To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
  Subject: Re: Email account utilization warning.

  Because I have respect for the IETF, and its principles. It is the IETF
  leadership that is disgraceful.

  But it has been the desire of the leadership to run the IETF like a
  private club, and many people would be (and have been) driven off by 
  their behavior. Someone, sometime has to stand up to them.

                --Dean

  On Wed, 7 Jul 2004, Mark Smith wrote:

  > If you have such low respect for the IETF, why don't you just remove
  > yourself from all associated IETF mailing lists, and stop
  > "contributing" too them?


On Wed, 7 Jul 2004, Mark Durham wrote:

> Could we try to keep our narcissistic eye on the ball here?
> 
> I realize that the only thing on this list that matters to you is you, 
> and normally I do what I imagine most of the list is doing: I suffer 
> your rants in silence. But recognizing this stuff is actually important, 
> and if there are people on the IETF list who don't, that's a situation 
> that cries out for attention. Please, for once, let's assume that you 
> are *not* the topic, and stay on whatever the topic actually is. You can 
> trot out your personal demons (or daemons, for that matter) under some 
> other subject line ... and, by all evidence, you certainly will. In the 
> meantime, let's not treat every message on this list as your personal 
> song cue.
> 
> Is this really too much to ask?
> 


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 15:19:51 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10796
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 15:19:51 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiHxQ-0001b0-Ld
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 15:19:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiHwT-0001G2-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 15:18:53 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiHvV-0000au-00; Wed, 07 Jul 2004 15:17:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiHPd-0002wc-Sw; Wed, 07 Jul 2004 14:44:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiGgu-0007mu-Co
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 13:58:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04509
	for <ietf@ietf.org>; Wed, 7 Jul 2004 13:58:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiGgo-0005Ju-9m
	for ietf@ietf.org; Wed, 07 Jul 2004 13:58:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiGft-000510-00
	for ietf@ietf.org; Wed, 07 Jul 2004 13:57:42 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65]
	helo=arneill-py.sacramento.ca.us) by ietf-mx with esmtp (Exim 4.12)
	id 1BiGfI-0004fa-00
	for ietf@ietf.org; Wed, 07 Jul 2004 13:57:05 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Wed, 7 Jul 2004 10:56:34 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB281@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: Email account utilization warning.
thread-index: AcRj8Pg0ZCHw4Lm6SA2nwWi1iVjFvQASPWwA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "bill" <bill@strahm.net>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: RE: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

> Bill wrote:
> You would think this crowd is used to Joe Jobs and Phishing.

Nah. Even if the scheme is crude and/or rudimentary and almost nobody
(except secretariat/staff) actually has an IETF e-mail account, it still
works.

This is interesting, as it goes against the current phishing trends that
tend to produce ultra-realistic baits; maybe it's not necessary to spend
all the time copying the target's logos and mimicking their fonts and
style after all. Good ol' tricks still work.

> You would think at least this crowd would learn.

Indeed this is not encouraging in terms of grandma being able to detect
phishing :-( Maybe I'll put a disguised Paypal donate button on my web
site and start a new career as a joe-jobber; looks like it could work.

Michel.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 16:41:46 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16212
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 16:41:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiJEh-0005cS-GS
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 16:41:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiJDg-0005HR-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 16:40:45 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiJCf-0004fR-00; Wed, 07 Jul 2004 16:39:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiIPc-0008KM-CG; Wed, 07 Jul 2004 15:49:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiHyF-0005q5-Ek
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 15:20:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10890
	for <ietf@ietf.org>; Wed, 7 Jul 2004 15:20:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiHy9-0001uw-Aw
	for ietf@ietf.org; Wed, 07 Jul 2004 15:20:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiHxA-0001Z3-00
	for ietf@ietf.org; Wed, 07 Jul 2004 15:19:37 -0400
Received: from mail.teal.net ([209.142.3.58] helo=teal.net)
	by ietf-mx with esmtp (Exim 4.12) id 1BiHwC-00015w-00
	for ietf@ietf.org; Wed, 07 Jul 2004 15:18:36 -0400
Received: from [24.2.56.29] by teal.net [209.142.3.58] with SmartMax MailMax
	for dean@av8.com; Wed, 07 Jul 2004 12:14:50 -0700
X-SmartMax-AuthUser: jstrutt@pcpotato.com
From: "Jasen Strutt" <jstrutt@pcpotato.com>
To: "'Dean Anderson'" <dean@av8.com>, "'Mark Durham'" <mdurham@spandrel.com>
Date: Wed, 7 Jul 2004 12:18:27 -0700
Message-ID: <00fa01c46457$2f2df590$6401a8c0@SATELLITE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
In-Reply-To: <Pine.LNX.4.44.0407071255240.29649-100000@cirrus.av8.net>
Content-Transfer-Encoding: quoted-printable
Cc: "'Michel Py'" <michel@arneill-py.sacramento.ca.us>, ietf@ietf.org
Subject: RE: Email account utilization warning. (Final) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jstrutt@pcpotato.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

"Dean Anderson"
Would you give it a rest already? Take your issue(s) up with the =
appropriate
person(s) in a separate, mutually exclusive thread, and stop blasting =
the
IETF list. =20

I'm sure you'll be unable to contain yourself and blast yet, another =
message
out, about how everyone else is wrong, and you have the ideas which lead =
us
to the wonderland of end all. Therein lies the problem.  =20

Your continued replies are a surefire way to test my "poignant 'stuff' =
from
"Dean Anderson" to ignore" ...."rule".

Cheers-=20
Jasen =20


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Dean
Anderson
Sent: Wednesday, July 07, 2004 10:34 AM
To: Mark Durham
Cc: Michel Py; ietf@ietf.org; jstrutt@pcpotato.com
Subject: Re: Email account utilization warning.

Mark,=20

To fool people, the "phish" has to be plausible.  In this case, people
have come to expect capricious behavior from the IETF and so the
"phishing" claim of turning off email capriciously isn't out of the =
realm
of the expected behavior.  People saw the IETF do it before, and expect =
it
might might happen again.

"Dean Anderson" is not the topic: The IETF principles are the topic;  =
The
IETF rules are the topic; The misbehavior by people including the IETF
leadership is the topic.  Those who don't want to address the problems =
try
to portray this as about Dean Anderson, or about Dan Bernstein, or about
whoever else is being abused at the moment.  It's not about Dean =
Anderson;
It's not about Dan Bernstein; Its not those other innocent people =
defamed
and disparaged by a select few abusers.  Its about abusive behavior by a
select group, and the willfull, repeated, and perfidious failure of the
leadership to address the abuse, and the participation by the leadership
in the abuse.

It should not be too much to ask that the IETF Leadership follow the =
IETF
rules and the IETF principles.  Is that too much to ask?  When the
leadership acts capriciously, frivolously, perfidiously and acts =
contrary
to the rules and principles of the IETF, this behavior is observed by
others.  These things don't happen in a vacuum.  The complaints of Dean
Anderson, or Dan Bernstein, or of anyone else do not bring dishonor to =
the
IETF. Only the behavior by the leadership brings disrespect and dishonor
to the IETF.  And we see the effects of that: People come to expect
capricious behavior from the IETF and so the "phishing" premise isn't =
out
of the realm of the expected behavior.  People saw the IETF do it =
before,
and expect it might might happen again.  Solve the problem: Obey the =
IETF
principles and rules. Then such "phishes" will be out of character, and=20
people would be more suspicious of such a "phish".


As I said offlist to Mark Smith:

  From: Dean Anderson <dean@av8.com>
  To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
  Subject: Re: Email account utilization warning.

  Because I have respect for the IETF, and its principles. It is the =
IETF
  leadership that is disgraceful.

  But it has been the desire of the leadership to run the IETF like a
  private club, and many people would be (and have been) driven off by=20
  their behavior. Someone, sometime has to stand up to them.

                --Dean

  On Wed, 7 Jul 2004, Mark Smith wrote:

  > If you have such low respect for the IETF, why don't you just remove
  > yourself from all associated IETF mailing lists, and stop
  > "contributing" too them?


On Wed, 7 Jul 2004, Mark Durham wrote:

> Could we try to keep our narcissistic eye on the ball here?
>=20
> I realize that the only thing on this list that matters to you is you, =

> and normally I do what I imagine most of the list is doing: I suffer=20
> your rants in silence. But recognizing this stuff is actually =
important,=20
> and if there are people on the IETF list who don't, that's a situation =

> that cries out for attention. Please, for once, let's assume that you=20
> are *not* the topic, and stay on whatever the topic actually is. You =
can=20
> trot out your personal demons (or daemons, for that matter) under some =

> other subject line ... and, by all evidence, you certainly will. In =
the=20
> meantime, let's not treat every message on this list as your personal=20
> song cue.
>=20
> Is this really too much to ask?
>=20


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 18:43:02 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25144
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 18:43:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiL84-00075E-Rj
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 18:43:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiL7B-0006k5-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 18:42:10 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiL6R-0006N7-00; Wed, 07 Jul 2004 18:41:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiJKj-0005Xu-AK; Wed, 07 Jul 2004 16:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiIb4-0002of-6R
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 16:00:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14402
	for <ietf@ietf.org>; Wed, 7 Jul 2004 16:00:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiIay-0000W9-03
	for ietf@ietf.org; Wed, 07 Jul 2004 16:00:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiIa5-0000Cn-00
	for ietf@ietf.org; Wed, 07 Jul 2004 15:59:49 -0400
Received: from adsl-66-137-237-100.dsl.rcsntx.swbell.net ([66.137.237.100]
	helo=gw.frascone.com) by ietf-mx with esmtp (Exim 4.12)
	id 1BiIZ6-0007fV-00
	for ietf@ietf.org; Wed, 07 Jul 2004 15:58:48 -0400
Received: by gw.frascone.com (Postfix, from userid 500)
	id A419C58058B; Wed,  7 Jul 2004 14:58:47 -0500 (CDT)
Date: Wed, 7 Jul 2004 14:58:47 -0500
From: David Frascone <dave@frascone.com>
To: Dean Anderson <dean@av8.com>
Message-ID: <20040707195847.GO2101@wolverine.frascone.com>
References: <40EC1AE8.7040908@spandrel.com>
	<Pine.LNX.4.44.0407071255240.29649-100000@cirrus.av8.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0407071255240.29649-100000@cirrus.av8.net>
User-Agent: Mutt/1.4.1i
Cc: ietf@ietf.org
Subject: Re: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

I wonder how hard it would be to set my mail server to drop your mail
too?  Since, obviously, "Email account utilization warning" has nothing
to do with your rants. . . 

-Dave

On Wednesday, 07 Jul 2004, Dean Anderson wrote:
> Mark, 
> 
> To fool people, the "phish" has to be plausible.  In this case, people
> have come to expect capricious behavior from the IETF and so the
> "phishing" claim of turning off email capriciously isn't out of the realm
> of the expected behavior.  People saw the IETF do it before, and expect it
> might might happen again.
> 
> "Dean Anderson" is not the topic: The IETF principles are the topic;  The
> IETF rules are the topic; The misbehavior by people including the IETF
> leadership is the topic.  Those who don't want to address the problems try
> to portray this as about Dean Anderson, or about Dan Bernstein, or about
> whoever else is being abused at the moment.  It's not about Dean Anderson;
> It's not about Dan Bernstein; Its not those other innocent people defamed
> and disparaged by a select few abusers.  Its about abusive behavior by a
> select group, and the willfull, repeated, and perfidious failure of the
> leadership to address the abuse, and the participation by the leadership
> in the abuse.
> 
> It should not be too much to ask that the IETF Leadership follow the IETF
> rules and the IETF principles.  Is that too much to ask?  When the
> leadership acts capriciously, frivolously, perfidiously and acts contrary
> to the rules and principles of the IETF, this behavior is observed by
> others.  These things don't happen in a vacuum.  The complaints of Dean
> Anderson, or Dan Bernstein, or of anyone else do not bring dishonor to the
> IETF. Only the behavior by the leadership brings disrespect and dishonor
> to the IETF.  And we see the effects of that: People come to expect
> capricious behavior from the IETF and so the "phishing" premise isn't out
> of the realm of the expected behavior.  People saw the IETF do it before,
> and expect it might might happen again.  Solve the problem: Obey the IETF
> principles and rules. Then such "phishes" will be out of character, and 
> people would be more suspicious of such a "phish".
> 
> 
> As I said offlist to Mark Smith:
> 
>   From: Dean Anderson <dean@av8.com>
>   To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
>   Subject: Re: Email account utilization warning.
> 
>   Because I have respect for the IETF, and its principles. It is the IETF
>   leadership that is disgraceful.
> 
>   But it has been the desire of the leadership to run the IETF like a
>   private club, and many people would be (and have been) driven off by 
>   their behavior. Someone, sometime has to stand up to them.
> 
>                 --Dean
> 
>   On Wed, 7 Jul 2004, Mark Smith wrote:
> 
>   > If you have such low respect for the IETF, why don't you just remove
>   > yourself from all associated IETF mailing lists, and stop
>   > "contributing" too them?
> 
> 
> On Wed, 7 Jul 2004, Mark Durham wrote:
> 
> > Could we try to keep our narcissistic eye on the ball here?
> > 
> > I realize that the only thing on this list that matters to you is you, 
> > and normally I do what I imagine most of the list is doing: I suffer 
> > your rants in silence. But recognizing this stuff is actually important, 
> > and if there are people on the IETF list who don't, that's a situation 
> > that cries out for attention. Please, for once, let's assume that you 
> > are *not* the topic, and stay on whatever the topic actually is. You can 
> > trot out your personal demons (or daemons, for that matter) under some 
> > other subject line ... and, by all evidence, you certainly will. In the 
> > meantime, let's not treat every message on this list as your personal 
> > song cue.
> > 
> > Is this really too much to ask?
> > 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 

-- 
David Frascone

                   Hindsight is always 20/20.

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 19:29:46 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27678
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 19:29:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiLrI-0006tW-Cs
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 19:29:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiLqJ-0006Z0-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 19:28:48 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiLpE-0005v9-00; Wed, 07 Jul 2004 19:27:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiKQL-00025N-9x; Wed, 07 Jul 2004 17:57:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiJEu-0004M0-KY
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 16:42:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16250
	for <ietf@ietf.org>; Wed, 7 Jul 2004 16:41:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiJEo-0005dQ-Ba
	for ietf@ietf.org; Wed, 07 Jul 2004 16:41:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiJDw-0005JM-00
	for ietf@ietf.org; Wed, 07 Jul 2004 16:41:01 -0400
Received: from twinlark.arctic.org ([168.75.98.6])
	by ietf-mx with esmtp (Exim 4.12) id 1BiJDN-0004zL-00
	for ietf@ietf.org; Wed, 07 Jul 2004 16:40:25 -0400
Received: (qmail 4444 invoked from network); 7 Jul 2004 20:40:14 -0000
Received: from unknown (HELO ?55.55.1.11?) (AUTH mark) (64.60.241.211)
	by 168.75.98.6 with SMTP; 7 Jul 2004 20:40:14 -0000
Message-ID: <40EC60A9.1020102@spandrel.com>
Date: Wed, 07 Jul 2004 13:44:25 -0700
From: Mark Durham <mdurham@spandrel.com>
User-Agent: Mozilla Thunderbird 0.7.1 (Macintosh/20040626)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
References: <Pine.LNX.4.44.0407071255240.29649-100000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0407071255240.29649-100000@cirrus.av8.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, ietf@ietf.org,
        jstrutt@pcpotato.com
Subject: Re: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

As Freud remarked, "Denial is avowal." Q.E.D.


Dean Anderson wrote:

>Mark, 
>
>To fool people, the "phish" has to be plausible.  In this case, people
>have come to expect capricious behavior from the IETF and so the
>"phishing" claim of turning off email capriciously isn't out of the realm
>of the expected behavior.  People saw the IETF do it before, and expect it
>might might happen again.
>
>"Dean Anderson" is not the topic: The IETF principles are the topic;  The
>IETF rules are the topic; The misbehavior by people including the IETF
>leadership is the topic.  Those who don't want to address the problems try
>to portray this as about Dean Anderson, or about Dan Bernstein, or about
>whoever else is being abused at the moment.  It's not about Dean Anderson;
>It's not about Dan Bernstein; Its not those other innocent people defamed
>and disparaged by a select few abusers.  Its about abusive behavior by a
>select group, and the willfull, repeated, and perfidious failure of the
>leadership to address the abuse, and the participation by the leadership
>in the abuse.
>
>It should not be too much to ask that the IETF Leadership follow the IETF
>rules and the IETF principles.  Is that too much to ask?  When the
>leadership acts capriciously, frivolously, perfidiously and acts contrary
>to the rules and principles of the IETF, this behavior is observed by
>others.  These things don't happen in a vacuum.  The complaints of Dean
>Anderson, or Dan Bernstein, or of anyone else do not bring dishonor to the
>IETF. Only the behavior by the leadership brings disrespect and dishonor
>to the IETF.  And we see the effects of that: People come to expect
>capricious behavior from the IETF and so the "phishing" premise isn't out
>of the realm of the expected behavior.  People saw the IETF do it before,
>and expect it might might happen again.  Solve the problem: Obey the IETF
>principles and rules. Then such "phishes" will be out of character, and 
>people would be more suspicious of such a "phish".
>
>
>As I said offlist to Mark Smith:
>
>  From: Dean Anderson <dean@av8.com>
>  To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
>  Subject: Re: Email account utilization warning.
>
>  Because I have respect for the IETF, and its principles. It is the IETF
>  leadership that is disgraceful.
>
>  But it has been the desire of the leadership to run the IETF like a
>  private club, and many people would be (and have been) driven off by 
>  their behavior. Someone, sometime has to stand up to them.
>
>                --Dean
>
>  On Wed, 7 Jul 2004, Mark Smith wrote:
>
>  > If you have such low respect for the IETF, why don't you just remove
>  > yourself from all associated IETF mailing lists, and stop
>  > "contributing" too them?
>
>
>On Wed, 7 Jul 2004, Mark Durham wrote:
>
>  
>
>>Could we try to keep our narcissistic eye on the ball here?
>>
>>I realize that the only thing on this list that matters to you is you, 
>>and normally I do what I imagine most of the list is doing: I suffer 
>>your rants in silence. But recognizing this stuff is actually important, 
>>and if there are people on the IETF list who don't, that's a situation 
>>that cries out for attention. Please, for once, let's assume that you 
>>are *not* the topic, and stay on whatever the topic actually is. You can 
>>trot out your personal demons (or daemons, for that matter) under some 
>>other subject line ... and, by all evidence, you certainly will. In the 
>>meantime, let's not treat every message on this list as your personal 
>>song cue.
>>
>>Is this really too much to ask?
>>
>>    
>>
>
>
>  
>


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 19:29:58 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27727
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 19:29:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiLrU-0006v3-LT
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 19:30:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiLqc-0006bb-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 19:29:07 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiLpu-0006FB-00; Wed, 07 Jul 2004 19:28:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiKQK-000250-86; Wed, 07 Jul 2004 17:57:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiJEu-0004Lx-2D
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 16:42:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16247
	for <ietf@ietf.org>; Wed, 7 Jul 2004 16:41:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiJEn-0005dK-N3
	for ietf@ietf.org; Wed, 07 Jul 2004 16:41:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiJDv-0005JE-00
	for ietf@ietf.org; Wed, 07 Jul 2004 16:41:00 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12) id 1BiJD7-0004zJ-00
	for ietf@ietf.org; Wed, 07 Jul 2004 16:40:09 -0400
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i67KdnJ13842; Wed, 7 Jul 2004 23:39:49 +0300 (EET DST)
X-Scanned: Wed, 7 Jul 2004 23:39:44 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i67Kdihk004207;
	Wed, 7 Jul 2004 23:39:44 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 006GzsCJ; Wed, 07 Jul 2004 23:39:41 EEST
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com
	[10.241.35.121])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i67Kddn23311; Wed, 7 Jul 2004 23:39:40 +0300 (EET DST)
Received: from dadhcp-172019068136.americas.nokia.com ([172.19.68.140]) by
	daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 7 Jul 2004 15:39:31 -0500
Received: from dadhcp-172019068136.americas.nokia.com (localhost.localdomain
	[127.0.0.1])
	by dadhcp-172019068136.americas.nokia.com (8.12.8/8.12.8) with ESMTP id
	i67KdVje012879; Wed, 7 Jul 2004 13:39:31 -0700
Received: (from kessens@localhost)
	by dadhcp-172019068136.americas.nokia.com (8.12.8/8.12.8/Submit) id
	i67KdU5s012877; Wed, 7 Jul 2004 13:39:30 -0700
Date: Wed, 7 Jul 2004 13:39:30 -0700
From: David Kessens <david.kessens@nokia.com>
To: Dean Anderson <dean@av8.com>
Message-ID: <20040707203930.GB12623@nokia.com>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB27F@server2003.arneill-py.sacramento.ca.us>
	<Pine.LNX.4.44.0407070200310.17487-100000@cirrus.av8.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0407070200310.17487-100000@cirrus.av8.net>
User-Agent: Mutt/1.4.1i
X-OriginalArrivalTime: 07 Jul 2004 20:39:32.0063 (UTC)
	FILETIME=[81CF36F0:01C46462]
Cc: ietf@ietf.org
Subject: Re: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


Dean,

On Wed, Jul 07, 2004 at 02:19:20AM -0400, Dean Anderson wrote:
> 
> P.S. I am still blocked from emailing DNS WG chair, and prevented from
> registering complaint about improper DNS WG RFC process activity by ISC
> and DNS WG chair Austein, because the IETF chairman Alvestrand demands
> that such complaints be made offlist, yet chairman Alvestrand refuses to
> require the WG Chairs to accept email from participants.

Can you please keep the facts straight:

- there is no such thing as the DNS WG
  do you mean the dnsop working group by any chance ?

- the dnsop working group has two chairpeople, not just Rob Austein

- you are not blocked by Rob Austein or prevented from registering a
  complaint.
  it has been pointed out to you that you have the ability to
  communicate with Rob Austein using the mail address that is posted
  on the ietf dnsop charter web page:
  http://www.ietf.org/html.charters/dnsop-charter.html  

Thanks,

David Kessens
---

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 21:05:56 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01853
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 21:05:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiNMK-0005yr-TF
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 21:05:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiNLI-0005eb-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 21:04:53 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiNKE-00053j-00; Wed, 07 Jul 2004 21:03:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiLB2-00034J-7b; Wed, 07 Jul 2004 18:46:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiJuf-0004yh-Vj
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 17:25:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18115
	for <ietf@ietf.org>; Wed, 7 Jul 2004 17:24:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiJuU-00041L-Mr
	for ietf@ietf.org; Wed, 07 Jul 2004 17:24:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiJtX-0003eh-00
	for ietf@ietf.org; Wed, 07 Jul 2004 17:24:00 -0400
Received: from user-0c6s170.cable.mindspring.com ([24.110.4.224]
	helo=sleekfreak.ath.cx) by ietf-mx with esmtp (Exim 4.12)
	id 1BiJsR-0003Jq-00
	for ietf@ietf.org; Wed, 07 Jul 2004 17:22:51 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1BiFEX-000427-00; Wed, 07 Jul 2004 12:25:21 -0400
Date: Wed, 7 Jul 2004 12:25:15 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Jasen Strutt <jstrutt@pcpotato.com>
In-Reply-To: <00fa01c46457$2f2df590$6401a8c0@SATELLITE>
Message-ID: <Pine.LNX.4.44.0407071223020.15496-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "'Mark Durham'" <mdurham@spandrel.com>,
        "'Michel Py'" <michel@arneill-py.sacramento.ca.us>,
        "'Dean Anderson'" <dean@av8.com>, ietf@ietf.org
Subject: RE: Email account utilization warning. (Final) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=2.0 required=5.0 tests=AWL,WEIRD_PORT autolearn=no 
	version=2.60

I would agree.  Perhaps an inquiry as to the motives behind this continual
attack that the IETF has endured would help mitigate the situation.


On Wed, 7 Jul 2004, Jasen Strutt wrote:

> "Dean Anderson"
> Would you give it a rest already? Take your issue(s) up with the appropriate
> person(s) in a separate, mutually exclusive thread, and stop blasting the
> IETF list.
>
> I'm sure you'll be unable to contain yourself and blast yet, another message
> out, about how everyone else is wrong, and you have the ideas which lead us
> to the wonderland of end all. Therein lies the problem.
>
> Your continued replies are a surefire way to test my "poignant 'stuff' from
> "Dean Anderson" to ignore" ...."rule".
>
> Cheers-
> Jasen
>
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Dean
> Anderson
> Sent: Wednesday, July 07, 2004 10:34 AM
> To: Mark Durham
> Cc: Michel Py; ietf@ietf.org; jstrutt@pcpotato.com
> Subject: Re: Email account utilization warning.
>
> Mark,
>
> To fool people, the "phish" has to be plausible.  In this case, people
> have come to expect capricious behavior from the IETF and so the
> "phishing" claim of turning off email capriciously isn't out of the realm
> of the expected behavior.  People saw the IETF do it before, and expect it
> might might happen again.
>
> "Dean Anderson" is not the topic: The IETF principles are the topic;  The
> IETF rules are the topic; The misbehavior by people including the IETF
> leadership is the topic.  Those who don't want to address the problems try
> to portray this as about Dean Anderson, or about Dan Bernstein, or about
> whoever else is being abused at the moment.  It's not about Dean Anderson;
> It's not about Dan Bernstein; Its not those other innocent people defamed
> and disparaged by a select few abusers.  Its about abusive behavior by a
> select group, and the willfull, repeated, and perfidious failure of the
> leadership to address the abuse, and the participation by the leadership
> in the abuse.
>
> It should not be too much to ask that the IETF Leadership follow the IETF
> rules and the IETF principles.  Is that too much to ask?  When the
> leadership acts capriciously, frivolously, perfidiously and acts contrary
> to the rules and principles of the IETF, this behavior is observed by
> others.  These things don't happen in a vacuum.  The complaints of Dean
> Anderson, or Dan Bernstein, or of anyone else do not bring dishonor to the
> IETF. Only the behavior by the leadership brings disrespect and dishonor
> to the IETF.  And we see the effects of that: People come to expect
> capricious behavior from the IETF and so the "phishing" premise isn't out
> of the realm of the expected behavior.  People saw the IETF do it before,
> and expect it might might happen again.  Solve the problem: Obey the IETF
> principles and rules. Then such "phishes" will be out of character, and
> people would be more suspicious of such a "phish".
>
>
> As I said offlist to Mark Smith:
>
>   From: Dean Anderson <dean@av8.com>
>   To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
>   Subject: Re: Email account utilization warning.
>
>   Because I have respect for the IETF, and its principles. It is the IETF
>   leadership that is disgraceful.
>
>   But it has been the desire of the leadership to run the IETF like a
>   private club, and many people would be (and have been) driven off by
>   their behavior. Someone, sometime has to stand up to them.
>
>                 --Dean
>
>   On Wed, 7 Jul 2004, Mark Smith wrote:
>
>   > If you have such low respect for the IETF, why don't you just remove
>   > yourself from all associated IETF mailing lists, and stop
>   > "contributing" too them?
>
>
> On Wed, 7 Jul 2004, Mark Durham wrote:
>
> > Could we try to keep our narcissistic eye on the ball here?
> >
> > I realize that the only thing on this list that matters to you is you,
> > and normally I do what I imagine most of the list is doing: I suffer
> > your rants in silence. But recognizing this stuff is actually important,
> > and if there are people on the IETF list who don't, that's a situation
> > that cries out for attention. Please, for once, let's assume that you
> > are *not* the topic, and stay on whatever the topic actually is. You can
> > trot out your personal demons (or daemons, for that matter) under some
> > other subject line ... and, by all evidence, you certainly will. In the
> > meantime, let's not treat every message on this list as your personal
> > song cue.
> >
> > Is this really too much to ask?
> >
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 21:27:06 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02831
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 21:27:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiNgp-0004zJ-15
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 21:27:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiNff-0004ap-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 21:25:55 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiNec-0003xY-00; Wed, 07 Jul 2004 21:24:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiLEE-0003zX-0v; Wed, 07 Jul 2004 18:49:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiK4z-0006k5-FB
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 17:35:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18732
	for <ietf@ietf.org>; Wed, 7 Jul 2004 17:35:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiK4t-0007dW-6v
	for ietf@ietf.org; Wed, 07 Jul 2004 17:35:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiK3t-0007KB-00
	for ietf@ietf.org; Wed, 07 Jul 2004 17:34:42 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BiK2s-0006jk-00
	for ietf@ietf.org; Wed, 07 Jul 2004 17:33:38 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i67LX87x034629
	for ietf@ietf.org env-from <vjs>;
	Wed, 7 Jul 2004 15:33:08 -0600 (MDT)
Date: Wed, 7 Jul 2004 15:33:08 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200407072133.i67LX87x034629@calcite.rhyolite.com>
To: ietf@ietf.org
References: <00fa01c46457$2f2df590$6401a8c0@SATELLITE>
Subject: RE: Email account utilization warning. (Final)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

> From: "Jasen Strutt" 

> Would you give it a rest already? Take your issue(s) up with the appropriate
> person(s) in a separate, mutually exclusive thread, and stop blasting the
> IETF list.  

I would rather not offend you, but please consider that good advice.
Please do not respond to those whose only interest is provoking a
response, any response from anyone and so being reassured they exist
and that people care about them, even if those concerns are negative.
Many of us know of their messages only when people respond to them,
and would rather not have that particular clipping service.

The differences among trolling, trollbaiting, countering trolls, and
everything else related to trolling are almost entirely in the minds
of the players.  To the rest of the world it is all useless, costly noise.


As for the Internet experts who still don't recognize phishing or
Microsoft worm noise when it hits their mailboxes, the Secretariat
should interpret complaints sent to the thousands of readers of this
list as requests to be unsubscribed with prejudice from all IETF mailing
lists, particularly when their complaints are double-encrypted in
base64 and HTML.  Such people are better served reading IETF mailing
lists through archives such as http://www1.ietf.org/mail-archive/web/ietf/

I promise to try to apply that policy to the minor, non-IETF lists
that I run.

I don't intend any criticism of those who choose on their own to use
archives instead of subscribing.  That's how I follow some mailing
lists that for various reasons I choose to not give my address.


Vernon Schryver    vjs@rhyolite.com

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 21:32:52 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03243
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 21:32:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiNmP-00073R-O0
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 21:32:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiNlS-0006jT-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 21:31:55 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiNkX-00067m-00; Wed, 07 Jul 2004 21:30:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiLEG-000407-D8; Wed, 07 Jul 2004 18:49:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiK55-0006l3-ME
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 17:35:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18752
	for <ietf@ietf.org>; Wed, 7 Jul 2004 17:35:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiK4z-0007eE-FU
	for ietf@ietf.org; Wed, 07 Jul 2004 17:35:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiK48-0007LW-00
	for ietf@ietf.org; Wed, 07 Jul 2004 17:34:57 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12) id 1BiK3l-00072o-00
	for ietf@ietf.org; Wed, 07 Jul 2004 17:34:33 -0400
Received: from f01v-28-21.d0.club-internet.fr ([212.195.253.21]
	helo=jfc2.jefsey.com) by montage.altserver.com with esmtp (Exim 4.34)
	id 1BiK3d-0001NS-8M; Wed, 07 Jul 2004 14:34:28 -0700
Message-Id: <6.1.1.1.2.20040707213641.046d2b30@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Wed, 07 Jul 2004 21:47:16 +0200
To: John C Klensin <john-ietf@jck.com>,
        Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <D8DE8C30E0F6781B32A4422C@scan.jck.com>
References: <FADC9C272BAA921AAD71AD91@scan.jck.com>
	<40EB1654.7080804@necom830.hpcl.titech.ac.jp>
	<D8DE8C30E0F6781B32A4422C@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider? (FWD: I-D
 ACTION:draft-klensin-ip-service-terms-03.txt)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

At 23:22 06/07/04, John C Klensin wrote:
>Vendors who are going to do these things will -- based on the
>fact that they are being done already -- do them, with or
>without this document.  And that includes providers who are
>doing very little that we would recognize as "internet service"
>characterizing themselves as "ISPs".   If this document can
>accomplish anything, it is, as several people have pointed out,
>provide a definitional basis for claiming that a vendor is lying
>about what is being provided.  Put differently, the theory
>behind it is to give operators/providers an opportunity to
>disclose what they are doing in a more or less clear way.  If
>they choose to exaggerate what they are offering, or to lie
>about their services, that is a problem that this document
>cannot solve and is not intended to try.

John,
This is quite ambitious to say "lying". Let say that it permits to say that 
a word is not used in John Klensin's way - may be not in an IETF ways. This 
permits to understand why, what is different, what are the con and pros. To 
have a reference is always a good point.

We are starting AFRAC as an experimental national Common Reference Center. 
The target is to understand how such center may support interapplications, 
contain metastructural risks, support dedicated governance and 
intergovernance relations, etc.  Masataka Otha's remark is quite 
interesting, since it shows that he doubts that non-IETF community members, 
while members of the Internet Gobal community may not use some words in the 
same way, or should not ne encouraged to use them. Obviously not sharing 
the same referential creates confusion. (IMHO we are at the core of the 
networking notion - thank you for the initaitive I called for for years).

I am going to use your draft as an "IETF reference lexicon". We will see if 
someone wants to translate it as several concept may differ in French or in 
other latin languages (I do not know about other langages).

Is that label agreeable to you?
Are you interested in continuing building on it when new words are 
questionned?
jfc


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 21:33:03 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03305
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 21:33:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiNma-000757-H4
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 21:33:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiNle-0006lD-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 21:32:07 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiNl7-0006QU-00; Wed, 07 Jul 2004 21:31:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiLEF-0003zv-DQ; Wed, 07 Jul 2004 18:49:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiK55-0006ku-1b
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 17:35:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18749
	for <ietf@ietf.org>; Wed, 7 Jul 2004 17:35:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiK4y-0007e9-QQ
	for ietf@ietf.org; Wed, 07 Jul 2004 17:35:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiK47-0007LO-00
	for ietf@ietf.org; Wed, 07 Jul 2004 17:34:56 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12) id 1BiK3k-00072m-00
	for ietf@ietf.org; Wed, 07 Jul 2004 17:34:32 -0400
Received: from f01v-28-21.d0.club-internet.fr ([212.195.253.21]
	helo=jfc2.jefsey.com) by montage.altserver.com with esmtp (Exim 4.34)
	id 1BiK3i-0001NS-Ou; Wed, 07 Jul 2004 14:34:32 -0700
Message-Id: <6.1.1.1.2.20040707215502.046d0eb0@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Wed, 07 Jul 2004 22:07:51 +0200
To: "Steven M. Bellovin" <smb@research.att.com>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <20040706154838.145501AE90@berkshire.research.att.com>
References: <Your message of "Mon,
	05 Jul 2004 19:42:33 PDT." <E1Bhfut-0004gV-00@ietf-mx>
	<20040706154838.145501AE90@berkshire.research.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
Cc: ietf@ietf.org
Subject: Re: Chinese IPv9 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

At 17:48 06/07/04, Steven M. Bellovin wrote:
>In message <E1Bhfut-0004gV-00@ietf-mx>, "Tony Hain" writes:
> >Sitting here in Seoul, Janet Sun (BII) said this is self-promotion of a
> >single researcher looking to improve his funding. There is technical
> >content, but no business content and the service providers are ignoring it
> >as a waste of time. Think of it as E-164 on steroids.
> >
>
>Right.

Dear Steven,
This looks as a well planned, polite and intelligent warning. About 
possible other ways to use/plan the DNS, IPv6, VoIP etc. We probably have 
to get used to Chinese ways. I read this as "are you sure IPv6.001 
numbering plan, IDNA, VoIP and ENUM are Internet Gospel?".

The surprisingly agressive mail of Vint Cerf seems to show he read it that 
way - at least in part. But is not IANA now "an ICANN function"?
I am sure reading comments from IETF and other mailing lists taught a lot 
to the IPv9's team (BTW, hello to them!)
jfc






_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul  7 23:30:14 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08771
	for <ietf-archive@ietf.org>; Wed, 7 Jul 2004 23:30:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiPbz-000689-Bp
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 23:30:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiPb8-0005o7-00
	for ietf-archive@ietf.org; Wed, 07 Jul 2004 23:29:23 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiPaV-0005U5-00; Wed, 07 Jul 2004 23:28:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiNd7-0003Pm-DM; Wed, 07 Jul 2004 21:23:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiLZ5-0000Uu-4m
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 19:10:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26773
	for <ietf@ietf.org>; Wed, 7 Jul 2004 19:10:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiLYy-0000mp-Gc
	for ietf@ietf.org; Wed, 07 Jul 2004 19:10:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiLY3-0000UJ-00
	for ietf@ietf.org; Wed, 07 Jul 2004 19:09:56 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12) id 1BiLWb-0007iG-00
	for ietf@ietf.org; Wed, 07 Jul 2004 19:08:25 -0400
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id
	i67N8PnE027035
	for <ietf@ietf.org>; Thu, 8 Jul 2004 00:08:25 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id AAA17909
	for <ietf@ietf.org>; Thu, 8 Jul 2004 00:08:23 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i67N8NW29490
	for ietf@ietf.org; Thu, 8 Jul 2004 00:08:23 +0100
Date: Thu, 8 Jul 2004 00:08:23 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Message-ID: <20040707230823.GA29023@login.ecs.soton.ac.uk>
References: <40EC1AE8.7040908@spandrel.com>
	<Pine.LNX.4.44.0407071255240.29649-100000@cirrus.av8.net>
	<20040707195847.GO2101@wolverine.frascone.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040707195847.GO2101@wolverine.frascone.com>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more
	information
X-ECS-MailScanner: Found to be clean
Subject: Re: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Oh, you can filter out any sender easily enough.   The snag is you see all
the replies people send to their mailings :(

Tim

On Wed, Jul 07, 2004 at 02:58:47PM -0500, David Frascone wrote:
> I wonder how hard it would be to set my mail server to drop your mail
> too?  Since, obviously, "Email account utilization warning" has nothing
> to do with your rants. . . 
> 
> -Dave
> 
> On Wednesday, 07 Jul 2004, Dean Anderson wrote:
> > Mark, 
> > 
> > To fool people, the "phish" has to be plausible.  In this case, people
> > have come to expect capricious behavior from the IETF and so the
> > "phishing" claim of turning off email capriciously isn't out of the realm
> > of the expected behavior.  People saw the IETF do it before, and expect it
> > might might happen again.
> > 
> > "Dean Anderson" is not the topic: The IETF principles are the topic;  The
> > IETF rules are the topic; The misbehavior by people including the IETF
> > leadership is the topic.  Those who don't want to address the problems try
> > to portray this as about Dean Anderson, or about Dan Bernstein, or about
> > whoever else is being abused at the moment.  It's not about Dean Anderson;
> > It's not about Dan Bernstein; Its not those other innocent people defamed
> > and disparaged by a select few abusers.  Its about abusive behavior by a
> > select group, and the willfull, repeated, and perfidious failure of the
> > leadership to address the abuse, and the participation by the leadership
> > in the abuse.
> > 
> > It should not be too much to ask that the IETF Leadership follow the IETF
> > rules and the IETF principles.  Is that too much to ask?  When the
> > leadership acts capriciously, frivolously, perfidiously and acts contrary
> > to the rules and principles of the IETF, this behavior is observed by
> > others.  These things don't happen in a vacuum.  The complaints of Dean
> > Anderson, or Dan Bernstein, or of anyone else do not bring dishonor to the
> > IETF. Only the behavior by the leadership brings disrespect and dishonor
> > to the IETF.  And we see the effects of that: People come to expect
> > capricious behavior from the IETF and so the "phishing" premise isn't out
> > of the realm of the expected behavior.  People saw the IETF do it before,
> > and expect it might might happen again.  Solve the problem: Obey the IETF
> > principles and rules. Then such "phishes" will be out of character, and 
> > people would be more suspicious of such a "phish".
> > 
> > 
> > As I said offlist to Mark Smith:
> > 
> >   From: Dean Anderson <dean@av8.com>
> >   To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
> >   Subject: Re: Email account utilization warning.
> > 
> >   Because I have respect for the IETF, and its principles. It is the IETF
> >   leadership that is disgraceful.
> > 
> >   But it has been the desire of the leadership to run the IETF like a
> >   private club, and many people would be (and have been) driven off by 
> >   their behavior. Someone, sometime has to stand up to them.
> > 
> >                 --Dean
> > 
> >   On Wed, 7 Jul 2004, Mark Smith wrote:
> > 
> >   > If you have such low respect for the IETF, why don't you just remove
> >   > yourself from all associated IETF mailing lists, and stop
> >   > "contributing" too them?
> > 
> > 
> > On Wed, 7 Jul 2004, Mark Durham wrote:
> > 
> > > Could we try to keep our narcissistic eye on the ball here?
> > > 
> > > I realize that the only thing on this list that matters to you is you, 
> > > and normally I do what I imagine most of the list is doing: I suffer 
> > > your rants in silence. But recognizing this stuff is actually important, 
> > > and if there are people on the IETF list who don't, that's a situation 
> > > that cries out for attention. Please, for once, let's assume that you 
> > > are *not* the topic, and stay on whatever the topic actually is. You can 
> > > trot out your personal demons (or daemons, for that matter) under some 
> > > other subject line ... and, by all evidence, you certainly will. In the 
> > > meantime, let's not treat every message on this list as your personal 
> > > song cue.
> > > 
> > > Is this really too much to ask?
> > > 
> > 
> > 
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ietf
> > 
> 
> -- 
> David Frascone
> 
>                    Hindsight is always 20/20.
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul  8 00:39:11 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11870
	for <ietf-archive@ietf.org>; Thu, 8 Jul 2004 00:39:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiQgj-0005eJ-3U
	for ietf-archive@ietf.org; Thu, 08 Jul 2004 00:39:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiQfi-0005Jq-00
	for ietf-archive@ietf.org; Thu, 08 Jul 2004 00:38:11 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiQfC-0004yY-00; Thu, 08 Jul 2004 00:37:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiOUL-0008Lm-8T; Wed, 07 Jul 2004 22:18:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiMtK-0002qM-0u
	for ietf@megatron.ietf.org; Wed, 07 Jul 2004 20:35:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00559
	for <ietf@ietf.org>; Wed, 7 Jul 2004 20:35:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiMtD-0004N1-Jt
	for ietf@ietf.org; Wed, 07 Jul 2004 20:35:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiMsG-000431-00
	for ietf@ietf.org; Wed, 07 Jul 2004 20:34:52 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BiMrN-0003jn-00
	for ietf@ietf.org; Wed, 07 Jul 2004 20:33:57 -0400
Received: from scan.jck.com ([209.187.148.215])
	by bs.jck.com with esmtp (Exim 4.34)
	id 1BiMrJ-0008vZ-WD; Wed, 07 Jul 2004 19:33:54 -0500
Date: Wed, 07 Jul 2004 20:33:53 -0400
From: John C Klensin <john-ietf@jck.com>
To: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Message-ID: <C22CC5896BA4DE25ECA3916E@scan.jck.com>
In-Reply-To: <6.1.1.1.2.20040707213641.046d2b30@mail.jefsey.com>
References: <FADC9C272BAA921AAD71AD91@scan.jck.com>
	<40EB1654.7080804@necom830.hpcl.titech.ac.jp>
	<D8DE8C30E0F6781B32A4422C@scan.jck.com>
	<6.1.1.1.2.20040707213641.046d2b30@mail.jefsey.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
 (FWD: I-D  ACTION:draft-klensin-ip-service-terms-03.txt)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On Wednesday, 07 July, 2004 21:47 +0200 "JFC (Jefsey) Morfin"
<jefsey@jefsey.com> wrote:

> At 23:22 06/07/04, John C Klensin wrote:
>> Vendors who are going to do these things will -- based on the
>> fact that they are being done already -- do them, with or
>> without this document.  And that includes providers who are
>> doing very little that we would recognize as "internet
>> service" characterizing themselves as "ISPs".   If this
>> document can accomplish anything, it is, as several people
>> have pointed out, provide a definitional basis for claiming
>> that a vendor is lying about what is being provided.  Put
>> differently, the theory behind it is to give
>> operators/providers an opportunity to disclose what they are
>> doing in a more or less clear way.  If they choose to
>> exaggerate what they are offering, or to lie about their
>> services, that is a problem that this document cannot solve
>> and is not intended to try.
> 
> John,
> This is quite ambitious to say "lying". Let say that it
> permits to say that a word is not used in John Klensin's way -
> may be not in an IETF ways.

No, I actually had a different case in mind, and the
clarification may be useful.   I used "lying" above to described
an intentional act, e.g., "we know the definitions say we a
doing 'A', but we will advertise 'B' in the hope of tricking
people".  Those who are not aware of the definitions, or decide
to ignore them entirely, are in other categories.  As I have
said before, only a government --typically a regulator or
legislature-- can make _any_ terminology mandatory, so there is
no question here of "forcing" (to repeat Ohta-san's term) anyone
to do (or not do) anything.  Definitions can also be written
into contracts by saying things like "X will be supplied, where
'X' is as defined in..."; such definitions may be more or less
useful depending on circumstances that are of more interest to
lawyers than to an engineering group.

> This permits to understand why,
> what is different, what are the con and pros. To have a
> reference is always a good point.

If I correctly understand your comment, we are in agreement.

> We are starting AFRAC as an experimental national Common
> Reference Center. The target is to understand how such center
> may support interapplications, contain metastructural risks,
> support dedicated governance and intergovernance relations,
> etc.  Masataka Otha's remark is quite interesting, since it
> shows that he doubts that non-IETF community members, while
> members of the Internet Gobal community may not use some words
> in the same way, or should not ne encouraged to use them.
> Obviously not sharing the same referential creates confusion.
> (IMHO we are at the core of the networking notion - thank you
> for the initaitive I called for for years).
> 
> I am going to use your draft as an "IETF reference lexicon".

Please do not.  While you are welcome to use it, it is, at the
moment, only _my_ reference lexicon.  Not even the people who
contributed significantly to the document are responsible for
it.  And, indeed, I'm not completely happy with all of the
definitions and categorizations: they are just the best I could
do with a limited amount of time and effort.   Characterizing it
as an "IETF reference" anything requires some evidence of IETF
community consensus.  That may or may not exist, but, under IETF
principles, only the IESG can reach a conclusion on that subject.

> We will see if someone wants to translate it as several
> concept may differ in French or in other latin languages (I do
> not know about other langages).

This might be very useful.
 
> Is that label agreeable to you?

See above.

> Are you interested in continuing building on it when new words
> are questionned?

To an extremely limited extent, yes.  The limits are imposed by
my conviction that something like this is not going to be useful
unless it is quite stable.  So addition or modification of basic
terms should be completed quickly or not at all.  One could even
make a case for trimming everything but the basic categories out
of this document and then producing a second, more informational
one, that identified the two collections of additional terms.
Personally, I don't think that is worth the effort and the added
confusion it would cause -- anyone actually using these
definitions can divide them up as they find useful.

regards,
    john



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul  8 06:09:31 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10663
	for <ietf-archive@ietf.org>; Thu, 8 Jul 2004 06:09:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BiVqM-0000bc-Vl
	for ietf-archive@ietf.org; Thu, 08 Jul 2004 06:09:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiVpI-0000IS-00
	for ietf-archive@ietf.org; Thu, 08 Jul 2004 06:08:25 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BiVoJ-0007Ta-00; Thu, 08 Jul 2004 06:07:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiUxa-0007Uj-EU; Thu, 08 Jul 2004 05:12:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiUW7-0007L7-62
	for ietf@megatron.ietf.org; Thu, 08 Jul 2004 04:44:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07188
	for <ietf@ietf.org>; Thu, 8 Jul 2004 04:44:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiUVz-0003EI-Vb
	for ietf@ietf.org; Thu, 08 Jul 2004 04:44:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiUUx-0002uX-00
	for ietf@ietf.org; Thu, 08 Jul 2004 04:43:19 -0400
Received: from mail23.nhs.uk ([62.6.139.221]) by ietf-mx with esmtp (Exim 4.12)
	id 1BiUU2-0002GT-00
	for ietf@ietf.org; Thu, 08 Jul 2004 04:42:23 -0400
Received: from [10.191.254.3] (helo=relayint2.nhs.uk)
	by mail23.nhs.uk with esmtp (MTC MTA) id 1BiUTZ-0007YS-TP
	for ietf@ietf.org; Thu, 08 Jul 2004 09:41:53 +0100
Received: from relay.nhs.uk (194.62.42.142) by relayint2.nhs.uk (Syntegra-I2
	7.0.008)
	id 409511E60120085B for ietf@ietf.org; Thu, 8 Jul 2004 09:41:53 +0100
Received: from mailgwexe.nhsia.nhs.uk (194.101.216.133) by relay.nhs.uk
	(Syntegra-2 7.0.008) (authenticated as
	smtpout_nhsia_nhs_uk@es2002.nhs.uk)
	id 40ECF5C70000BC36 for ietf@ietf.org; Thu, 8 Jul 2004 09:41:53 +0100
Received: from exchgwexe.nhsia.nhs.uk ([192.168.17.117]) by
	mailgwexe.nhsia.nhs.uk with Microsoft SMTPSVC(6.0.3790.0);
	Thu, 8 Jul 2004 09:45:34 +0100
Received: from exchaq2.nhsia.nhs.uk ([192.168.33.90]) by
	exchgwexe.nhsia.nhs.uk with Microsoft SMTPSVC(5.0.2195.6713);
	Thu, 8 Jul 2004 09:41:50 +0100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.132
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 8 Jul 2004 09:37:21 +0100
Message-ID: <595299DD7F30014BBCE48B93DCB606525F5B54@EXCHAQ2.nhsia.nhs.uk>
Thread-Topic: Email account utilization warning.
thread-index: AcRj8Pg0ZCHw4Lm6SA2nwWi1iVjFvQASPWwAACMlOjA=
From: "Harley David" <david.harley@nhsia.nhs.uk>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 08 Jul 2004 08:41:50.0962 (UTC)
	FILETIME=[69CE6520:01C464C7]
Content-Transfer-Encoding: quoted-printable
Subject: RE: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

> This is interesting, as it goes against the current phishing trends
that
> tend to produce ultra-realistic baits; maybe it's not necessary to
spend
> all the time copying the target's logos and mimicking their fonts and
> style after all. Good ol' tricks still work.

Indeed. But this isn't a phishing scam at all. It's a mass mailer
virus - one of the Bagle variants, by the look.
=20
--=20
David Harley
Threat Assessment Centre Manager
Malware and Email Abuse Management Specialist
NHS Information Authority


This e-mail is confidential and privileged. If you are not the intended =
recipient please accept our apologies; please do not disclose, copy or =
distribute information in this e-mail or take any action in reliance on =
its contents: to do so is strictly prohibited and may be unlawful. =
Please inform us that this message has gone astray before deleting it. =
Thank you for your co-operation.



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul  8 12:06:04 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05420
	for <ietf-archive@ietf.org>; Thu, 8 Jul 2004 12:06:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BibPS-0001Fn-C9
	for ietf-archive@ietf.org; Thu, 08 Jul 2004 12:06:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BibO0-0000jC-00
	for ietf-archive@ietf.org; Thu, 08 Jul 2004 12:04:37 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BibLz-0007k6-00; Thu, 08 Jul 2004 12:02:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiahR-0006I4-6x; Thu, 08 Jul 2004 11:20:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bia7d-00057T-IC
	for ietf@megatron.ietf.org; Thu, 08 Jul 2004 10:43:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27548
	for <ietf@ietf.org>; Thu, 8 Jul 2004 10:43:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bia7X-0002ZN-Mv
	for ietf@ietf.org; Thu, 08 Jul 2004 10:43:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bia6h-0002Eb-00
	for ietf@ietf.org; Thu, 08 Jul 2004 10:42:40 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65]
	helo=arneill-py.sacramento.ca.us) by ietf-mx with esmtp (Exim 4.12)
	id 1Bia5l-0001UQ-00
	for ietf@ietf.org; Thu, 08 Jul 2004 10:41:41 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 8 Jul 2004 07:41:00 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB284@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: Email account utilization warning.
thread-index: AcRj8Pg0ZCHw4Lm6SA2nwWi1iVjFvQASPWwAACMlOjAADIID4A==
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Harley David" <david.harley@nhsia.nhs.uk>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: RE: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

>> Michel Py wrote:
>> This is interesting, as it goes against the current
>> phishing trends that tend to produce ultra-realistic
>> baits; maybe it's not necessary to spend all the time
>> copying the target's logos and mimicking their fonts
>> and style after all. Good ol' tricks still work.

> Harley David
> Indeed. But this isn't a phishing scam at all. It's a
> mass mailer virus - one of the Bagle variants, by the
> look.

I was looking at the social implications only; has someone actually
analyzed the payload?

I would not be surprised to see shortly a real phishing propagated by a
slow-spreading mass mailer virus (this might be a proof-of-concept).

Michel.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul  8 14:04:06 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14313
	for <ietf-archive@ietf.org>; Thu, 8 Jul 2004 14:04:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BidFe-0000Nc-MI
	for ietf-archive@ietf.org; Thu, 08 Jul 2004 14:04:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BidEl-0007lT-00
	for ietf-archive@ietf.org; Thu, 08 Jul 2004 14:03:12 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BidDG-0006zW-00; Thu, 08 Jul 2004 14:01:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiawU-0002pi-7p; Thu, 08 Jul 2004 11:36:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiacR-0004fy-To
	for ietf@megatron.ietf.org; Thu, 08 Jul 2004 11:15:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29783
	for <ietf@ietf.org>; Thu, 8 Jul 2004 11:15:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiacM-0005XF-4O
	for ietf@ietf.org; Thu, 08 Jul 2004 11:15:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiaZm-0004wD-00
	for ietf@ietf.org; Thu, 08 Jul 2004 11:12:43 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65]
	helo=arneill-py.sacramento.ca.us) by ietf-mx with esmtp (Exim 4.12)
	id 1BiaYZ-0004F8-00
	for ietf@ietf.org; Thu, 08 Jul 2004 11:11:27 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 8 Jul 2004 08:10:57 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB285@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: Email account utilization warning.
thread-index: AcRkmUZkFixQo1iSSBqrzsOrO1R8fwAZEQeg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Tim Chown" <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: RE: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

> Tim Chown
> Oh, you can filter out any sender easily enough. The snag
> is you see all the replies people send to their mailings :(

Indeed.

Michel.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul  8 19:04:54 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12173
	for <ietf-archive@ietf.org>; Thu, 8 Jul 2004 19:04:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bihwm-0002op-He
	for ietf-archive@ietf.org; Thu, 08 Jul 2004 19:04:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bihvi-0002Q3-00
	for ietf-archive@ietf.org; Thu, 08 Jul 2004 19:03:51 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bihuk-0001hl-00; Thu, 08 Jul 2004 19:02:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiftA-0002iP-UC; Thu, 08 Jul 2004 16:53:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BidAi-0006ea-JO
	for ietf@megatron.ietf.org; Thu, 08 Jul 2004 13:59:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13811
	for <ietf@ietf.org>; Thu, 8 Jul 2004 13:58:54 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BidAc-0006A7-Es
	for ietf@ietf.org; Thu, 08 Jul 2004 13:58:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bid9o-0005l7-00
	for ietf@ietf.org; Thu, 08 Jul 2004 13:58:04 -0400
Received: from turing-police.cirt.vt.edu ([128.173.54.129] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1Bid8c-00055h-00
	for ietf@ietf.org; Thu, 08 Jul 2004 13:56:50 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0/8.13.0) with ESMTP id i68Huo36030273
	for <ietf@ietf.org>; Thu, 8 Jul 2004 13:56:50 -0400
Message-Id: <200407081756.i68Huo36030273@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4+dev
To: ietf@ietf.org
In-Reply-To: Your message of "Thu, 08 Jul 2004 08:10:57 PDT."
	<DD7FE473A8C3C245ADA2A2FE1709D90B0DB285@server2003.arneill-py.sacramento.ca.us>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB285@server2003.arneill-py.sacramento.ca.us>
Mime-Version: 1.0
Date: Thu, 08 Jul 2004 13:56:50 -0400
Subject: Re: Email account utilization warning. 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1766313434=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

--===============1766313434==
Content-Type: multipart/signed; boundary="==_Exmh_1520836946P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Thu, 08 Jul 2004 08:10:57 PDT, Michel Py <michel@arneill-py.sacramento.ca.us>  said:
> > Tim Chown
> > Oh, you can filter out any sender easily enough. The snag
> > is you see all the replies people send to their mailings :(
> 
> Indeed.

Procmail filtering on 'From:|To:|cc:' is easy enough.  There's probably
a way to get Procmail to snarf up the Message-Id: header for the sender's
posting, and then look for that msgid in any References: or In-Reply-To:
headers ('formail -D 16384 that_persons_postings' will get a cache
going, but matching any header other than another Message-Id: is interesting.. ;)

The Gnus mail/news reader has adaptive thread scoring - so you can drop "User X
and any followups/replies" into non-visibility...

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

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

iD8DBQFA7YricC3lWbTT17ARAle6AJsHZTvwVIU0s23n+v74Et8ugbHppwCdEc6g
Ev9BisFNuNx6y7KJ/0CUvTI=
=dVnm
-----END PGP SIGNATURE-----

--==_Exmh_1520836946P--


--===============1766313434==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1766313434==--



From ietf-bounces@ietf.org  Thu Jul  8 19:05:07 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12228
	for <ietf-archive@ietf.org>; Thu, 8 Jul 2004 19:05:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bihwz-0002q8-6L
	for ietf-archive@ietf.org; Thu, 08 Jul 2004 19:05:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bihvx-0002SA-00
	for ietf-archive@ietf.org; Thu, 08 Jul 2004 19:04:06 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bihuw-0001i1-00; Thu, 08 Jul 2004 19:03:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BiftK-00031D-L2; Thu, 08 Jul 2004 16:53:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BidBM-0006kU-Dd
	for ietf@megatron.ietf.org; Thu, 08 Jul 2004 13:59:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13844
	for <ietf@ietf.org>; Thu, 8 Jul 2004 13:59:38 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BidBL-0006Y8-8d
	for ietf@ietf.org; Thu, 08 Jul 2004 13:59:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BidAM-00067f-00
	for ietf@ietf.org; Thu, 08 Jul 2004 13:58:38 -0400
Received: from turing-police.cirt.vt.edu ([128.173.54.129] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1Bid9E-0005Ms-00
	for ietf@ietf.org; Thu, 08 Jul 2004 13:57:28 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0/8.13.0) with ESMTP id i68HvShf004541
	for <ietf@ietf.org>; Thu, 8 Jul 2004 13:57:28 -0400
Message-Id: <200407081757.i68HvShf004541@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4+dev
To: ietf@ietf.org
In-Reply-To: Your message of "Tue, 06 Jul 2004 12:38:01 +0530."
	<aknijsewosnfnpckadn@ietf.org> 
References: <aknijsewosnfnpckadn@ietf.org>
Mime-Version: 1.0
Date: Thu, 08 Jul 2004 13:57:28 -0400
Subject: Re: Email account utilization warning. 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1627199459=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

--===============1627199459==
Content-Type: multipart/signed; boundary="==_Exmh_1521839792P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Tue, 06 Jul 2004 12:38:01 +0530, support@ietf.org  said:

> Your e-mail account has  been temporary disabled because of unauthorized access.

Our virus scanners are still nailing some 30K Bagles a week.  Are there
really people net.clued enough to be subscribed to the IETF list, but
with so few e-mail contacts that they've never encountered a copy before?

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

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

iD8DBQFA7YsIcC3lWbTT17ARArlXAKDzksX61xUU4gqi5+tGIoaeL6F6IgCg9Gpb
hyhPGlQ483xMeiR3pFIwOMs=
=WvwY
-----END PGP SIGNATURE-----

--==_Exmh_1521839792P--


--===============1627199459==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1627199459==--



From ietf-bounces@ietf.org  Fri Jul  9 03:42:12 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08924
	for <ietf-archive@ietf.org>; Fri, 9 Jul 2004 03:42:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Biq1M-0007hS-2k
	for ietf-archive@ietf.org; Fri, 09 Jul 2004 03:42:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Biq0Q-0007OD-00
	for ietf-archive@ietf.org; Fri, 09 Jul 2004 03:41:15 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bipzo-000739-00; Fri, 09 Jul 2004 03:40:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BipGr-0007CM-Us; Fri, 09 Jul 2004 02:54:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Biovk-0002fN-M9
	for ietf@megatron.ietf.org; Fri, 09 Jul 2004 02:32:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05767
	for <ietf@ietf.org>; Fri, 9 Jul 2004 02:32:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Biovd-0001EU-Iw
	for ietf@ietf.org; Fri, 09 Jul 2004 02:32:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Biouh-0000uu-00
	for ietf@ietf.org; Fri, 09 Jul 2004 02:31:15 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12) id 1Biou2-0000c7-00
	for ietf@ietf.org; Fri, 09 Jul 2004 02:30:34 -0400
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id
	i696UYnE004575
	for <ietf@ietf.org>; Fri, 9 Jul 2004 07:30:34 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id HAA23465
	for <ietf@ietf.org>; Fri, 9 Jul 2004 07:30:30 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i696UU904410
	for ietf@ietf.org; Fri, 9 Jul 2004 07:30:30 +0100
Date: Fri, 9 Jul 2004 07:30:30 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Message-ID: <20040709063029.GA4320@login.ecs.soton.ac.uk>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB285@server2003.arneill-py.sacramento.ca.us>
	<200407081756.i68Huo36030273@turing-police.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200407081756.i68Huo36030273@turing-police.cc.vt.edu>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more
	information
X-ECS-MailScanner: Found to be clean
Subject: Re: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Thu, Jul 08, 2004 at 01:56:50PM -0400, Valdis.Kletnieks@vt.edu wrote:
> 
> Procmail filtering on 'From:|To:|cc:' is easy enough.  There's probably
> a way to get Procmail to snarf up the Message-Id: header for the sender's
> posting, and then look for that msgid in any References: or In-Reply-To:
> headers ('formail -D 16384 that_persons_postings' will get a cache
> going, but matching any header other than another Message-Id: is interesting.. ;)

I use procmail, but have a headache working out how to use the Message-ID
to filter out a thread started by someone in my kill list.   Using all
receipt headers is dangerous because if one of the loons joins a good
discussion the procmail may essentially DoS it for me.   I just want to lose
any posting and any thread started by anyone in my kill list.   At the
momnet I just have the former.

tim

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul  9 22:01:29 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23273
	for <ietf-archive@ietf.org>; Fri, 9 Jul 2004 22:01:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bj7BB-00031H-Sy
	for ietf-archive@ietf.org; Fri, 09 Jul 2004 22:01:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bj78j-00027f-00
	for ietf-archive@ietf.org; Fri, 09 Jul 2004 21:58:58 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bj77L-0001fR-03; Fri, 09 Jul 2004 21:57:31 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Bj6yo-0000pV-Qw; Fri, 09 Jul 2004 21:48:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bj1kR-0005An-G0; Fri, 09 Jul 2004 16:13:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bj1CE-0002qu-TO
	for ietf@megatron.ietf.org; Fri, 09 Jul 2004 15:38:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24902
	for <ietf@ietf.org>; Fri, 9 Jul 2004 15:38:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bj1C8-00054M-Kw
	for ietf@ietf.org; Fri, 09 Jul 2004 15:38:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bj1At-0004So-00
	for ietf@ietf.org; Fri, 09 Jul 2004 15:36:48 -0400
Received: from terrapinnmail.terrapinn.com ([217.29.193.44])
	by ietf-mx with esmtp (Exim 4.12) id 1Bj195-0003eI-00
	for ietf@ietf.org; Fri, 09 Jul 2004 15:34:55 -0400
To: ietf@ietf.org
From: simon.dux@totaltele.com
Message-Id: <B0051064786@terrapinnmail.terrapinn.com>
Date: Fri, 9 Jul 2004 20:36:51 +0100
Subject: Autoreply: Ietf Digest, Vol 3, Issue 13
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60

I'm out of the office on Monday and Tuesday (13th-14th) so please send enquires to ttmag@totaltele.com. Contributors contact David Molony or Ian Kemp



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Sat Jul 10 12:34:32 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21522
	for <ietf-archive@ietf.org>; Sat, 10 Jul 2004 12:34:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BjKo5-00000K-RK
	for ietf-archive@ietf.org; Sat, 10 Jul 2004 12:34:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjKn9-0007VQ-00
	for ietf-archive@ietf.org; Sat, 10 Jul 2004 12:33:36 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BjKmN-0006uv-00; Sat, 10 Jul 2004 12:32:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BjKhH-0002EI-QP; Sat, 10 Jul 2004 12:27:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjKcQ-0001eU-FO
	for ietf@megatron.ietf.org; Sat, 10 Jul 2004 12:22:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21075
	for <ietf@ietf.org>; Sat, 10 Jul 2004 12:22:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjKcP-00042f-Ki
	for ietf@ietf.org; Sat, 10 Jul 2004 12:22:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjKbR-0003iy-00
	for ietf@ietf.org; Sat, 10 Jul 2004 12:21:29 -0400
Received: from terrapinnmail.terrapinn.com ([217.29.193.44])
	by ietf-mx with esmtp (Exim 4.12) id 1BjKaL-00038V-00
	for ietf@ietf.org; Sat, 10 Jul 2004 12:20:22 -0400
To: ietf@ietf.org
From: simon.dux@totaltele.com
Message-Id: <B0051069198@terrapinnmail.terrapinn.com>
Date: Sat, 10 Jul 2004 17:22:14 +0100
Subject: Autoreply: Ietf Digest, Vol 3, Issue 14
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

I'm out of the office on Monday and Tuesday (13th-14th) so please send enquires to ttmag@totaltele.com. Contributors contact David Molony or Ian Kemp



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Sun Jul 11 12:29:28 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29299
	for <ietf-archive@ietf.org>; Sun, 11 Jul 2004 12:29:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BjhCj-0003ZX-In
	for ietf-archive@ietf.org; Sun, 11 Jul 2004 12:29:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjhBq-0003PJ-00
	for ietf-archive@ietf.org; Sun, 11 Jul 2004 12:28:34 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BjhBA-00034I-00; Sun, 11 Jul 2004 12:27:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bjh7F-0001jI-L0; Sun, 11 Jul 2004 12:23:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bjh3G-0001E8-AX
	for ietf@megatron.ietf.org; Sun, 11 Jul 2004 12:19:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28676
	for <ietf@ietf.org>; Sun, 11 Jul 2004 12:19:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bjh3F-0001Xz-IY
	for ietf@ietf.org; Sun, 11 Jul 2004 12:19:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bjh2J-0001Lw-00
	for ietf@ietf.org; Sun, 11 Jul 2004 12:18:43 -0400
Received: from terrapinnmail.terrapinn.com ([217.29.193.44])
	by ietf-mx with esmtp (Exim 4.12) id 1Bjh1U-0000yr-00
	for ietf@ietf.org; Sun, 11 Jul 2004 12:17:52 -0400
To: ietf@ietf.org
From: simon.dux@totaltele.com
Message-Id: <B0051074107@terrapinnmail.terrapinn.com>
Date: Sun, 11 Jul 2004 17:19:47 +0100
Subject: Autoreply: Ietf Digest, Vol 3, Issue 15
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

I'm out of the office on Monday and Tuesday (13th-14th) so please send enquires to ttmag@totaltele.com. Contributors contact David Molony or Ian Kemp



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 12 09:56:34 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07799
	for <ietf-archive@ietf.org>; Mon, 12 Jul 2004 09:56:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bk1IK-0001yV-4k
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 09:56:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk1HN-0001jj-00
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 09:55:38 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bk1Ga-0001W7-00; Mon, 12 Jul 2004 09:54:48 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Bk1Ga-0004Yf-UZ; Mon, 12 Jul 2004 09:54:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bk157-0002IY-Di; Mon, 12 Jul 2004 09:42:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjTm4-0002OL-KH
	for ietf@megatron.ietf.org; Sat, 10 Jul 2004 22:09:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12103
	for <ietf@ietf.org>; Sat, 10 Jul 2004 22:09:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjTm2-00030i-RN
	for ietf@ietf.org; Sat, 10 Jul 2004 22:09:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjTk8-0002NF-00
	for ietf@ietf.org; Sat, 10 Jul 2004 22:07:04 -0400
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BjTjI-00023E-00; Sat, 10 Jul 2004 22:06:12 -0400
Received: from razor.cs.columbia.edu
	(IDENT:8DJaNs932WCy2xpmDv22zS9P6zlTRwaO@razor.cs.columbia.edu
	[128.59.16.8])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i6B269fq007978
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); 
	Sat, 10 Jul 2004 22:06:09 -0400 (EDT)
Received: from cs.columbia.edu
	(IDENT:a4SI2RDyHUyarkFLSllwqTxuPBua232s@localhost [127.0.0.1])
	by razor.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i6B267jd019857;
	Sat, 10 Jul 2004 22:06:08 -0400
Message-ID: <40F0A08F.5080003@cs.columbia.edu>
Date: Sat, 10 Jul 2004 22:06:07 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6a) Gecko/20031030
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org, "'geopriv@ietf.org'" <geopriv@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.6.0.99824, Antispam-Core: 4.6.1.104326,
	Antispam-Data: 2004.7.9.106820
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0,
	__HAS_MSGID 0, __SANE_MSGID 0, __USER_AGENT 0, X_ACCEPT_LANG 0,
	__MIME_VERSION 0, __TO_MALFORMED_2 0, __EVITE_CTYPE 0,
	__CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __MIME_TEXT_ONLY 0,
	USER_AGENT 0.000'
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 12 Jul 2004 09:42:53 -0400
Subject: Comments on draft-ietf-pidf-lo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Based on suggestions by Brian Rosen, I'd like to propose three 
additional civic location elements for this document:

- BLDG (building), e.g., "Empire State Building"
- UNIT (unit), e.g, "APT 42" or "SUITE 123"
- ROOM (room number), e.g., "1234"

Henning

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 12 10:01:30 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08274
	for <ietf-archive@ietf.org>; Mon, 12 Jul 2004 10:01:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bk1N6-0003Es-Bt
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 10:01:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk1MC-00030p-00
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 10:00:37 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bk1LZ-0002mh-00; Mon, 12 Jul 2004 09:59:57 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Bk1LX-0004mc-Mh; Mon, 12 Jul 2004 09:59:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bk158-0002If-M8; Mon, 12 Jul 2004 09:42:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjUKr-0006U1-9U
	for ietf@megatron.ietf.org; Sat, 10 Jul 2004 22:45:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13266
	for <ietf@ietf.org>; Sat, 10 Jul 2004 22:44:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjUKp-0006rQ-Is
	for ietf@ietf.org; Sat, 10 Jul 2004 22:44:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjUJq-0006VP-00
	for ietf@ietf.org; Sat, 10 Jul 2004 22:43:58 -0400
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BjUII-0005rl-00; Sat, 10 Jul 2004 22:42:22 -0400
Received: from razor.cs.columbia.edu
	(IDENT:0eJYSvP/93/cdLpOwcS8fJIYmdKC3cfW@razor.cs.columbia.edu
	[128.59.16.8])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i6B2gGfq014026
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); 
	Sat, 10 Jul 2004 22:42:16 -0400 (EDT)
Received: from cs.columbia.edu
	(IDENT:/X6X3Gh1We8ooC52YagWP/B0G23i4+V6@localhost [127.0.0.1])
	by razor.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i6B2gEjd019979;
	Sat, 10 Jul 2004 22:42:15 -0400
Message-ID: <40F0A904.9050501@cs.columbia.edu>
Date: Sat, 10 Jul 2004 22:42:12 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6a) Gecko/20031030
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "James M. Polk" <jmpolk@cisco.com>
References: <4.3.2.7.2.20040702162911.03647008@localhost>
	<4.3.2.7.2.20040702162911.03647008@localhost>
	<4.3.2.7.2.20040710212647.025b7190@localhost>
In-Reply-To: <4.3.2.7.2.20040710212647.025b7190@localhost>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.6.0.99824, Antispam-Core: 4.6.1.104326,
	Antispam-Data: 2004.7.9.106820
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0,
	__HAS_MSGID 0, __SANE_MSGID 0, __USER_AGENT 0, X_ACCEPT_LANG 0,
	__MIME_VERSION 0, __TO_MALFORMED_2 0, __REFERENCES 0,
	__IN_REP_TO 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0,
	__CTE 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0,
	__MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0,
	USER_AGENT 0.000'
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 12 Jul 2004 09:42:53 -0400
Cc: geopriv@ietf.org, ietf@ietf.org
Subject: Re: Civil-02 ID and PIDF-LO inconsistencies
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

James M. Polk wrote:

> I agree it is related.  Perhaps the pidf-lo document should only 
> reference the civil doc for the chart? In other words, have the civil ID 
> be the creator of the chart, and not have it in both documents (fearing 
> inconsistency), but have the pidf-lo document reference *to* the chart 
> in the civil doc.
> 
> I know this is not necessarily optimal, but this is the last week to 
> catch this before IETF LC in the pidf-lo doc is completed, so there is 
> time to address it now.

Given that both need to define different tags (XML element names in one 
case, numeric tags in the other), I think such reference would be 
difficult, even leaving timing issues aside. I think we can handle the 
synchronization of the documents - the list of elements is small.

Henning

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 12 10:08:26 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09061
	for <ietf-archive@ietf.org>; Mon, 12 Jul 2004 10:08:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bk1Tn-0004vJ-Rg
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 10:08:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk1Sm-0004el-00
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 10:07:25 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bk1Rl-0004Lv-00; Mon, 12 Jul 2004 10:06:21 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Bk1Rm-00059x-2V; Mon, 12 Jul 2004 10:06:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bk15A-0002Im-7C; Mon, 12 Jul 2004 09:43:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjVqV-0003YT-Ly
	for ietf@megatron.ietf.org; Sun, 11 Jul 2004 00:21:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18726
	for <ietf@ietf.org>; Sun, 11 Jul 2004 00:21:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjVqT-0004wa-Ol
	for ietf@ietf.org; Sun, 11 Jul 2004 00:21:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjVpG-0004Z9-00
	for ietf@ietf.org; Sun, 11 Jul 2004 00:20:30 -0400
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BjVmk-0003rZ-00; Sun, 11 Jul 2004 00:17:54 -0400
Received: from razor.cs.columbia.edu
	(IDENT:eB2tQI+dwlCLxo3HClE2mE4pwPH0xcgx@razor.cs.columbia.edu
	[128.59.16.8])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i6B4Hkfq028372
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); 
	Sun, 11 Jul 2004 00:17:46 -0400 (EDT)
Received: from cs.columbia.edu
	(IDENT:Zzid/ZAXDcSXuLUuFxH+j/3B8Ln8TXxf@localhost [127.0.0.1])
	by razor.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i6B4Hdjd020193;
	Sun, 11 Jul 2004 00:17:41 -0400
Message-ID: <40F0BF62.5020607@cs.columbia.edu>
Date: Sun, 11 Jul 2004 00:17:38 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6a) Gecko/20031030
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "James M. Polk" <jmpolk@cisco.com>
References: <4.3.2.7.2.20040710213746.025ba3c0@localhost>
In-Reply-To: <4.3.2.7.2.20040710213746.025ba3c0@localhost>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.6.0.99824, Antispam-Core: 4.6.1.104326,
	Antispam-Data: 2004.7.10.106855
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0,
	__HAS_MSGID 0, __SANE_MSGID 0, __USER_AGENT 0, X_ACCEPT_LANG 0,
	__MIME_VERSION 0, __TO_MALFORMED_2 0, __REFERENCES 0,
	__IN_REP_TO 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0,
	__CTE 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0,
	__MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0,
	USER_AGENT 0.000'
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 12 Jul 2004 09:42:53 -0400
Cc: "'geopriv@ietf.org'" <geopriv@ietf.org>, ietf@ietf.org
Subject: Re: [Geopriv] Comments on draft-ietf-pidf-lo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

James M. Polk wrote:
> I think "LMK" covers this (which is already defined), and is different 
> than the occupant the building (which would be "NAM" I believe).

In many cases, yes. In other cases, LMK would be a larger complex ("The 
Mews"), comprising more than one building.

> 
>> - UNIT (unit), e.g, "APT 42" or "SUITE 123"
>> - ROOM (room number), e.g., "1234"
> 
> 
> I know you gave only one example per, but room numbers have other 
> characters in them frequently, like "63-1N" (which is my office 
> designation, so I didn't make it up)
> 
> Otherwise, these last two seem reasonable

Both are strings.

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 12 10:11:35 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09521
	for <ietf-archive@ietf.org>; Mon, 12 Jul 2004 10:11:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bk1Wr-0005hE-Ao
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 10:11:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk1Vs-0005RZ-00
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 10:10:37 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bk1Ux-0004za-00; Mon, 12 Jul 2004 10:09:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bk161-0002Oq-Pf; Mon, 12 Jul 2004 09:43:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjUFE-0005yl-AT
	for ietf@megatron.ietf.org; Sat, 10 Jul 2004 22:39:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13086
	for <ietf@ietf.org>; Sat, 10 Jul 2004 22:39:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjUFC-0005Cs-KU
	for ietf@ietf.org; Sat, 10 Jul 2004 22:39:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjUEC-0004re-00
	for ietf@ietf.org; Sat, 10 Jul 2004 22:38:08 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12)
	id 1BjUDK-0004Ae-00; Sat, 10 Jul 2004 22:37:14 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 10 Jul 2004 19:37:48 +0000
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i6B2agt1001544;
	Sat, 10 Jul 2004 19:36:42 -0700 (PDT)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-rtp-1.cisco.com
	[161.44.11.166]) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id TAA21568;
	Sat, 10 Jul 2004 19:36:40 -0700 (PDT)
Message-Id: <4.3.2.7.2.20040710212647.025b7190@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 10 Jul 2004 21:36:50 -0500
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <40F0A237.60205@cs.columbia.edu>
References: <4.3.2.7.2.20040702162911.03647008@localhost>
	<4.3.2.7.2.20040702162911.03647008@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Mon, 12 Jul 2004 09:43:50 -0400
Cc: geopriv@ietf.org, ietf@ietf.org
Subject: Civil-02 ID and PIDF-LO inconsistencies
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

At 10:13 PM 7/10/2004 -0400, Henning Schulzrinne wrote:
>James M. Polk wrote:
>
>>In reviewing the pidf-lo-02 and the civil-02 IDs, I have discovered minor 
>>inconsistencies.
>
>Please note that the labels in the column 'NENA' refer to the NENA 02-010 
>data element labels. Neither FLR or PC are used there, as far as I can 
>tell. FLR is not defined there at all and PC is called ZIP.

hmmmm - inconsistencies should be avoided if known (therefore - see below)

>I've added a separate column to the civil-02 table, labeled PIDF, to make 
>the correspondence explicit.

this is good for the civil ID, but doesn't address what the pidf-lo ID is 
stating (which you shouldn't be solving)

>>I believe the two charts should be consistent to each other, with the 
>>civil-02 ID being the one that's less complete, it should have the 
>>appropriate text added.
>
>They definitely should be. A separate, but related issue, is whether the 
>language information contained in the civil-02 draft should also appear in 
>PIDF-LO.

I agree it is related.  Perhaps the pidf-lo document should only reference 
the civil doc for the chart? In other words, have the civil ID be the 
creator of the chart, and not have it in both documents (fearing 
inconsistency), but have the pidf-lo document reference *to* the chart in 
the civil doc.

I know this is not necessarily optimal, but this is the last week to catch 
this before IETF LC in the pidf-lo doc is completed, so there is time to 
address it now.


>>cheers,
>>James
>>                                *******************
>>                 Truth is not to be argued... it is to be presented
>


cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 12 10:29:58 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11306
	for <ietf-archive@ietf.org>; Mon, 12 Jul 2004 10:29:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bk1oe-0002I5-GV
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 10:30:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk1no-00021G-00
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 10:29:09 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bk1mq-0001jm-01; Mon, 12 Jul 2004 10:28:08 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Bk1Xo-0005XK-3O; Mon, 12 Jul 2004 10:12:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bk164-0002P9-Ge; Mon, 12 Jul 2004 09:43:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjVLq-0005uZ-0F
	for ietf@megatron.ietf.org; Sat, 10 Jul 2004 23:50:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15138
	for <ietf@ietf.org>; Sat, 10 Jul 2004 23:50:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjVLo-00048p-6v
	for ietf@ietf.org; Sat, 10 Jul 2004 23:50:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjVKu-0003op-00
	for ietf@ietf.org; Sat, 10 Jul 2004 23:49:09 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12)
	id 1BjVKF-0003Kw-00; Sat, 10 Jul 2004 23:48:27 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 10 Jul 2004 20:49:02 +0000
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i6B3ltt1015418;
	Sat, 10 Jul 2004 20:47:55 -0700 (PDT)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-rtp-1.cisco.com
	[161.44.11.166]) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id UAA22084;
	Sat, 10 Jul 2004 20:47:54 -0700 (PDT)
Message-Id: <4.3.2.7.2.20040710223507.0248a008@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 10 Jul 2004 22:48:29 -0500
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <40F0A904.9050501@cs.columbia.edu>
References: <4.3.2.7.2.20040710212647.025b7190@localhost>
	<4.3.2.7.2.20040702162911.03647008@localhost>
	<4.3.2.7.2.20040702162911.03647008@localhost>
	<4.3.2.7.2.20040710212647.025b7190@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Mon, 12 Jul 2004 09:43:50 -0400
Cc: geopriv@ietf.org, ietf@ietf.org
Subject: Re: Civil-02 ID and PIDF-LO inconsistencies
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

At 10:42 PM 7/10/2004 -0400, Henning Schulzrinne wrote:
>James M. Polk wrote:
>
>>I know this is not necessarily optimal, but this is the last week to 
>>catch this before IETF LC in the pidf-lo doc is completed, so there is 
>>time to address it now.
>
>Given that both need to define different tags (XML element names in one 
>case, numeric tags in the other), I think such reference would be difficult,

but they both have a way too similar chart that doesn't match - 
implementors down the road might not see the subtle differences and we end 
up with another Mars Probe crashing into the planet because one set of 
engineers used km and the other used miles and both groups were happy until 
there were flames and smoke

Not being consistent MUST lead to ignoring of fields in the IETF... this is 
not good unless (see below)

>even leaving timing issues aside. I think we can handle the 
>synchronization of the documents

this means the civil doc needs to change to exactly what the pidf-lo doc 
has (as the synchronization is up to the most mobile doc - and that's the 
civil doc near WGLC, but far from IETF LC)

>- the list of elements is small.

agreed they are in the details side of addressing, but if someone sending a 
message was coded to the civil doc and includes BLDG, and the recipient's 
device was coded to the pidf-lo doc without such a reference, the BLDG 
value must be ignored by the recipient.

Maybe this is the lone identifier on the Columbia Univ campus ("The Law 
School"). Leaving everything else consistent, a responder is going to go to 
a campus address and have the floor and room number, but not which building 
the caller was in. That might mean less lawyers that year...

This I think presents a problem.


>Henning


cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 12 10:30:00 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11327
	for <ietf-archive@ietf.org>; Mon, 12 Jul 2004 10:30:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bk1of-0002IF-Qk
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 10:30:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk1nq-00021V-00
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 10:29:11 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bk1mq-0001jm-02; Mon, 12 Jul 2004 10:28:08 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Bk1Xn-0005XM-39; Mon, 12 Jul 2004 10:12:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bk163-0002Ox-5D; Mon, 12 Jul 2004 09:43:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjUNq-0007CD-H4
	for ietf@megatron.ietf.org; Sat, 10 Jul 2004 22:48:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13376
	for <ietf@ietf.org>; Sat, 10 Jul 2004 22:48:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjUNo-00006F-OX
	for ietf@ietf.org; Sat, 10 Jul 2004 22:48:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjUMy-0007YQ-00
	for ietf@ietf.org; Sat, 10 Jul 2004 22:47:12 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12)
	id 1BjUM6-0006u9-00; Sat, 10 Jul 2004 22:46:18 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 10 Jul 2004 19:46:52 +0000
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i6B2jkSc002172;
	Sat, 10 Jul 2004 19:45:46 -0700 (PDT)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-rtp-1.cisco.com
	[161.44.11.166]) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id TAA24819;
	Sat, 10 Jul 2004 19:45:45 -0700 (PDT)
Message-Id: <4.3.2.7.2.20040710213746.025ba3c0@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 10 Jul 2004 21:46:21 -0500
To: Henning Schulzrinne <hgs@cs.columbia.edu>, ietf@ietf.org,
        "'geopriv@ietf.org'" <geopriv@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <40F0A08F.5080003@cs.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Mon, 12 Jul 2004 09:43:50 -0400
Subject: Re: [Geopriv] Comments on draft-ietf-pidf-lo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

At 10:06 PM 7/10/2004 -0400, Henning Schulzrinne wrote:
>Based on suggestions by Brian Rosen, I'd like to propose three additional 
>civic location elements for this document:
>
>- BLDG (building), e.g., "Empire State Building"

I think "LMK" covers this (which is already defined), and is different than 
the occupant the building (which would be "NAM" I believe).

>- UNIT (unit), e.g, "APT 42" or "SUITE 123"
>- ROOM (room number), e.g., "1234"

I know you gave only one example per, but room numbers have other 
characters in them frequently, like "63-1N" (which is my office 
designation, so I didn't make it up)

Otherwise, these last two seem reasonable


>Henning
>
>_______________________________________________
>Geopriv mailing list
>Geopriv@ietf.org
>https://www1.ietf.org/mailman/listinfo/geopriv


cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 12 13:02:47 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24136
	for <ietf-archive@ietf.org>; Mon, 12 Jul 2004 13:02:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bk4CX-0007R7-8H
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 13:02:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk4BV-0007Bu-00
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 13:01:46 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bk4B5-0006x7-00; Mon, 12 Jul 2004 13:01:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bk3ze-0003Ua-IF; Mon, 12 Jul 2004 12:49:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bk3gO-0000LN-Ps
	for ietf@megatron.ietf.org; Mon, 12 Jul 2004 12:29:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21586
	for <ietf@ietf.org>; Mon, 12 Jul 2004 12:29:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bk3gN-000776-NM
	for ietf@ietf.org; Mon, 12 Jul 2004 12:29:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk3fR-0006t2-00
	for ietf@ietf.org; Mon, 12 Jul 2004 12:28:37 -0400
Received: from terrapinnmail.terrapinn.com ([217.29.193.44])
	by ietf-mx with esmtp (Exim 4.12) id 1Bk3ep-0006Si-00
	for ietf@ietf.org; Mon, 12 Jul 2004 12:27:59 -0400
To: ietf@ietf.org
From: simon.dux@totaltele.com
Message-Id: <B0051085040@terrapinnmail.terrapinn.com>
Date: Mon, 12 Jul 2004 17:29:55 +0100
Subject: Autoreply: Ietf Digest, Vol 3, Issue 16
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

I'm out of the office on Monday and Tuesday (13th-14th) so please send enquires to ttmag@totaltele.com. Contributors contact David Molony or Ian Kemp



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 12 13:33:38 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26247
	for <ietf-archive@ietf.org>; Mon, 12 Jul 2004 13:33:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bk4gM-0007Jv-Fd
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 13:33:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk4fP-000767-00
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 13:32:40 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bk4eo-0006r0-00; Mon, 12 Jul 2004 13:32:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bk4RJ-0008Ar-B3; Mon, 12 Jul 2004 13:18:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bk47Y-00050l-6N
	for ietf@megatron.ietf.org; Mon, 12 Jul 2004 12:57:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23820
	for <ietf@ietf.org>; Mon, 12 Jul 2004 12:57:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bk47W-0006Ef-Lj
	for ietf@ietf.org; Mon, 12 Jul 2004 12:57:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk46b-0005yr-00
	for ietf@ietf.org; Mon, 12 Jul 2004 12:56:42 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1Bk45i-0005Ve-00
	for ietf@ietf.org; Mon, 12 Jul 2004 12:55:46 -0400
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i6CGt7E0007577
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 12 Jul 2004 12:55:10 -0400
Date: Mon, 12 Jul 2004 12:55:07 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: David Kessens <david.kessens@nokia.com>
In-Reply-To: <20040707203930.GB12623@nokia.com>
Message-ID: <Pine.LNX.4.44.0407121249520.7397-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
Subject: Re: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Wed, 7 Jul 2004, David Kessens wrote:

> 
> Dean,
> 
> On Wed, Jul 07, 2004 at 02:19:20AM -0400, Dean Anderson wrote:
> > 
> > P.S. I am still blocked from emailing DNS WG chair, and prevented from
> > registering complaint about improper DNS WG RFC process activity by ISC
> > and DNS WG chair Austein, because the IETF chairman Alvestrand demands
> > that such complaints be made offlist, yet chairman Alvestrand refuses to
> > require the WG Chairs to accept email from participants.
> 
> Can you please keep the facts straight:
> 
> - there is no such thing as the DNS WG
>   do you mean the dnsop working group by any chance ?

Yes. That is correct.

> - the dnsop working group has two chairpeople, not just Rob Austein

At present.

> - you are not blocked by Rob Austein or prevented from registering a
>   complaint.

I have posted the blocked messages in the past. Are you asserting that
something has changed?  I am not aware of any change.  Indeed, Chairmain
Alvestrand has clearly stated that he has not requested any change.

>   it has been pointed out to you that you have the ability to
>   communicate with Rob Austein using the mail address that is posted
>   on the ietf dnsop charter web page:

As Chairman Alvestrand has clearly stated, IETF email lists are not to be
used for making complaints.  One is not supposed to make complaints to the
DNSOP list.  The only exception to this rule is the main IETF list which
has administrative discussion as its purpose.

>   http://www.ietf.org/html.charters/dnsop-charter.html  

Yes, I've read this carefully.



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 12 21:59:01 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12986
	for <ietf-archive@ietf.org>; Mon, 12 Jul 2004 21:59:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BkCZS-00046p-7N
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 21:59:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkCTm-0002mZ-00
	for ietf-archive@ietf.org; Mon, 12 Jul 2004 21:53:11 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BkCQ2-0001kl-00; Mon, 12 Jul 2004 21:49:18 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BkCBH-0004rL-T9; Mon, 12 Jul 2004 21:34:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkAvN-0004RC-GP; Mon, 12 Jul 2004 20:13:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bk8rP-0007qd-7g
	for ietf@megatron.ietf.org; Mon, 12 Jul 2004 18:01:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20391
	for <ietf@ietf.org>; Mon, 12 Jul 2004 18:01:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bk8rN-0006zY-Ak
	for ietf@ietf.org; Mon, 12 Jul 2004 18:01:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk8qK-0006eO-00
	for ietf@ietf.org; Mon, 12 Jul 2004 18:00:13 -0400
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12) id 1Bk8pH-0006Jw-00
	for ietf@ietf.org; Mon, 12 Jul 2004 17:59:07 -0400
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i6CLx4822375; Tue, 13 Jul 2004 00:59:04 +0300 (EET DST)
X-Scanned: Tue, 13 Jul 2004 00:59:02 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i6CLx2Kv004748;
	Tue, 13 Jul 2004 00:59:02 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks004.ntc.nokia.com 00Mddsa2; Tue, 13 Jul 2004 00:59:01 EEST
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com
	[10.241.35.121])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i6CLx0u15349; Tue, 13 Jul 2004 00:59:00 +0300 (EET DST)
Received: from dadhcp-172019068136.americas.nokia.com ([172.19.68.140]) by
	daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Mon, 12 Jul 2004 16:58:34 -0500
Received: from dadhcp-172019068136.americas.nokia.com (localhost.localdomain
	[127.0.0.1])
	by dadhcp-172019068136.americas.nokia.com (8.12.8/8.12.8) with ESMTP id
	i6CLwYje004113; Mon, 12 Jul 2004 14:58:34 -0700
Received: (from kessens@localhost)
	by dadhcp-172019068136.americas.nokia.com (8.12.8/8.12.8/Submit) id
	i6CLwX2p004111; Mon, 12 Jul 2004 14:58:33 -0700
Date: Mon, 12 Jul 2004 14:58:33 -0700
From: David Kessens <david.kessens@nokia.com>
To: Dean Anderson <dean@av8.com>
Message-ID: <20040712215833.GC2851@nokia.com>
References: <20040707203930.GB12623@nokia.com>
	<Pine.LNX.4.44.0407121249520.7397-100000@cirrus.av8.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0407121249520.7397-100000@cirrus.av8.net>
User-Agent: Mutt/1.4.1i
X-OriginalArrivalTime: 12 Jul 2004 21:58:34.0791 (UTC)
	FILETIME=[60C2D370:01C4685B]
Cc: ietf@ietf.org
Subject: Re: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


Dean,

On Mon, Jul 12, 2004 at 12:55:07PM -0400, Dean Anderson wrote:
> 
> >   http://www.ietf.org/html.charters/dnsop-charter.html  
> 
> Yes, I've read this carefully.

Did you really ? If you did, you would have found a mail address of
Rob Austein that you can use to send him mail.

David Kessens
---

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul 13 09:01:41 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07550
	for <ietf-archive@ietf.org>; Tue, 13 Jul 2004 09:01:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BkMuk-0004RK-Dm
	for ietf-archive@ietf.org; Tue, 13 Jul 2004 09:01:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkMtf-00046H-00
	for ietf-archive@ietf.org; Tue, 13 Jul 2004 09:00:36 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BkMsp-0003WJ-00; Tue, 13 Jul 2004 08:59:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkMkU-0001SF-0F; Tue, 13 Jul 2004 08:51:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkMdz-0008AE-3s
	for ietf@megatron.ietf.org; Tue, 13 Jul 2004 08:44:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06828
	for <ietf@ietf.org>; Tue, 13 Jul 2004 08:44:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkMdy-00076r-H1
	for ietf@ietf.org; Tue, 13 Jul 2004 08:44:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkMcz-0006ns-00
	for ietf@ietf.org; Tue, 13 Jul 2004 08:43:22 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12) id 1BkMbz-0006Dl-00
	for ietf@ietf.org; Tue, 13 Jul 2004 08:42:19 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 0FC1B61BF5; Tue, 13 Jul 2004 14:41:48 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 27023-07; Tue, 13 Jul 2004 14:41:46 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id A25EB61B9C; Tue, 13 Jul 2004 14:41:44 +0200 (CEST)
Date: Tue, 13 Jul 2004 14:02:05 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>, David Kessens <david.kessens@nokia.com>
Message-ID: <AD3CBB2AE184EBE720065CB2@B50854F0A9192E8EC6CDA126>
In-Reply-To: <Pine.LNX.4.44.0407121249520.7397-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0407121249520.7397-100000@cirrus.av8.net>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Quote from me that isn't (Re: Email account utilization warning.)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On 12. juli 2004 12:55 -0400 Dean Anderson <dean@av8.com> wrote:

>>   it has been pointed out to you that you have the ability to
>>   communicate with Rob Austein using the mail address that is posted
>>   on the ietf dnsop charter web page:
>
> As Chairman Alvestrand has clearly stated, IETF email lists are not to be
> used for making complaints.  One is not supposed to make complaints to the
> DNSOP list.  The only exception to this rule is the main IETF list which
> has administrative discussion as its purpose.

I do not recognize that as anything I have said.
Please point to the quote.

               Harald





_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul 13 12:49:50 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23835
	for <ietf-archive@ietf.org>; Tue, 13 Jul 2004 12:49:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BkQTY-0000dZ-J7
	for ietf-archive@ietf.org; Tue, 13 Jul 2004 12:49:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkQSa-0000H5-00
	for ietf-archive@ietf.org; Tue, 13 Jul 2004 12:48:52 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BkQRX-0007OL-00; Tue, 13 Jul 2004 12:47:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkQDu-0003p4-Ez; Tue, 13 Jul 2004 12:33:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkQ5H-0001PY-R9
	for ietf@megatron.ietf.org; Tue, 13 Jul 2004 12:24:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21761
	for <ietf@ietf.org>; Tue, 13 Jul 2004 12:24:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkQ5H-0007V4-1W
	for ietf@ietf.org; Tue, 13 Jul 2004 12:24:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkQ4E-0007BK-00
	for ietf@ietf.org; Tue, 13 Jul 2004 12:23:42 -0400
Received: from terrapinnmail.terrapinn.com ([217.29.193.44])
	by ietf-mx with esmtp (Exim 4.12) id 1BkQ3V-0006ZW-00
	for ietf@ietf.org; Tue, 13 Jul 2004 12:22:57 -0400
To: ietf@ietf.org
From: simon.dux@totaltele.com
Message-Id: <B0051099503@terrapinnmail.terrapinn.com>
Date: Tue, 13 Jul 2004 17:24:50 +0100
Subject: Autoreply: Ietf Digest, Vol 3, Issue 17
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

I'm out of the office on Monday and Tuesday (13th-14th) so please send enquires to ttmag@totaltele.com. Contributors contact David Molony or Ian Kemp



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul 13 15:58:48 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09701
	for <ietf-archive@ietf.org>; Tue, 13 Jul 2004 15:58:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BkTQP-000452-Fr
	for ietf-archive@ietf.org; Tue, 13 Jul 2004 15:58:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkTPL-0003f4-00
	for ietf-archive@ietf.org; Tue, 13 Jul 2004 15:57:44 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BkTOG-0002v0-00; Tue, 13 Jul 2004 15:56:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkSzm-000834-L2; Tue, 13 Jul 2004 15:31:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkSrh-0005OX-RQ
	for ietf@megatron.ietf.org; Tue, 13 Jul 2004 15:22:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06471
	for <ietf@ietf.org>; Tue, 13 Jul 2004 15:22:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkSrg-0006d8-6q
	for ietf@ietf.org; Tue, 13 Jul 2004 15:22:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkSql-0006JV-00
	for ietf@ietf.org; Tue, 13 Jul 2004 15:22:00 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1BkSq8-0005y3-00
	for ietf@ietf.org; Tue, 13 Jul 2004 15:21:21 -0400
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i6DJKnvm004192
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 13 Jul 2004 15:20:49 -0400
Date: Tue, 13 Jul 2004 15:20:49 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: David Kessens <david.kessens@nokia.com>
In-Reply-To: <20040712215833.GC2851@nokia.com>
Message-ID: <Pine.LNX.4.44.0407131449180.3536-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
Subject: Re: Email account utilization warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

This page lists his old address. Mr. Austein's current address (as can be
seen from the DNSOP archives) is sra@isc.org. The current sra@isc.org
email address does not receive email from Av8 Internet or any of its
customers due to Rob's (and hence the IETF's) participation in an unlawful
boycott**.

Please do not forget that this is not the first time that the DNSOP and/or
Namedroppers chairs have attempted to ignore private complaints. They have
even altered on-list email from participants and inappropriately published
the private unsubscription addresses so that forged unsubscriptions can be
issued to Majordomo.  See for example complaints by Dan Bernstein.  
Majordomo has a security flaw that allows unsubscriptions to be forged if
you know the subscription address.  Their latest scheme is just a
continuation of their previous misbehavior.

		--Dean

** Please note that this boycott has nothing whatsoever to do with spam or
spam-blocking.  Note also that the emails we refer to as "bounces" are not
actually bounces in the commonly used sense of a mail delivery error. The
messages do not represent a genuine mail system error: They make the false
claim that "sra@isc.org" doesn't exist. In fact, this address does exist.  
The response messages are in fact intentionally configured auto-responder
messages which are meant to harrass and annoy.  As Joe Abley noted, they
are not even meant to block email.  It is only Chairman Alvestrand (and of
course Paul Vixie), who misleadingly claim that these messages are genuine
mail delivery errors.  I note that both Chairman Alvestrand and former
chair Randy Bush each initially responded that these messages weren't
really bounces, and that reporting them as genuine failures was "designed
to attract a stupid response".  It is only after they are asked to enforce
the various IETF and ISOC policies with respect to computer harrassment by
auto-responder that they have decided to (disingenously) view them as
genuine mail system failures.




On Mon, 12 Jul 2004, David Kessens wrote:

> 
> Dean,
> 
> On Mon, Jul 12, 2004 at 12:55:07PM -0400, Dean Anderson wrote:
> > 
> > >   http://www.ietf.org/html.charters/dnsop-charter.html  
> > 
> > Yes, I've read this carefully.
> 
> Did you really ? If you did, you would have found a mail address of
> Rob Austein that you can use to send him mail.
> 
> David Kessens
> ---
> 


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 14 00:09:43 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10372
	for <ietf-archive@ietf.org>; Wed, 14 Jul 2004 00:09:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bkb5U-0002YE-Eh
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 00:09:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkaQu-0003dY-00
	for ietf-archive@ietf.org; Tue, 13 Jul 2004 23:27:49 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BkZwy-0006Wu-00; Tue, 13 Jul 2004 22:56:52 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BkZu4-00081E-Ow; Tue, 13 Jul 2004 22:53:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkVQA-0001ib-FM; Tue, 13 Jul 2004 18:06:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkTnG-0000AR-7v
	for ietf@megatron.ietf.org; Tue, 13 Jul 2004 16:22:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12652
	for <ietf@ietf.org>; Tue, 13 Jul 2004 16:22:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkTnF-0003jL-1H
	for ietf@ietf.org; Tue, 13 Jul 2004 16:22:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkTju-0002ft-00
	for ietf@ietf.org; Tue, 13 Jul 2004 16:18:59 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1BkTfz-0001PM-00
	for ietf@ietf.org; Tue, 13 Jul 2004 16:14:55 -0400
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i6DKENaO005096
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 13 Jul 2004 16:14:24 -0400
Date: Tue, 13 Jul 2004 16:14:23 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
In-Reply-To: <AD3CBB2AE184EBE720065CB2@B50854F0A9192E8EC6CDA126>
Message-ID: <Pine.LNX.4.44.0407131546440.3536-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
Subject: Re: Quote from me that isn't (Re: Email account utilization
	warning.)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


Funny that: if you don't recognize the statements, why don't you clearly
state that is appropriate to make complaints on-list and refute those who
ask for such complaints to be made offlist?  Complaints _should_ be made
offlist.  

Myself, Dan Bernstein, and I think others have been chastised for making
on-list complaints.  Of course, we have only made them public after they 
were privately ignored.

Of course, making every complaint on-list would be unreasonable--not to
mention inappropriate for a variety of legal reasons. It would subject the
IETF to claims of defamation, for example.  So is your objection here
anything but frivolous? 

		--Dean


On 26 Nov 2002, D. J. Bernstein wrote:

> [ post by non-subscriber.  with the massive amount of spam, it is easy 
to
>   miss and therefore delete mis-posts.  your subscription address is
>   54830374684695-namedroppers@sublist.cr.yp.to, please post from it or 
>   fix subscription your subscription address! ]
> 
> I've sent twelve messages to the namedroppers mailing list this month.
> Five of them have been silently discarded by the namedroppers censor,
> Randy Bush. (See http://cr.yp.to/djbdns/namedroppers.html for previous
> incidents.)
> 
> Bush says that the only relevant feature of my messages is that they're 
> sent from an address that isn't subscribed to namedroppers. Okay, boys
> and girls, let's look at some statistics:
> 
>    * 5/12 of my messages have been silently discarded;
> 
>    * according to Bush, this has nothing to do with me or the content,
>      so we estimate that about 5/12 of all non-subscriber messages have
>      been silently discarded;
>
>    * in the past three months, there have been about 100 legitimate
>      messages from other people who Bush labelled as non-subscribers;  
> 
>    * so we estimate that, in the last three months, Bush has silently
>      discarded about 71 legitimate messages from other people. That's a
>      rate of hundreds per year.
>
> Bush doesn't say ``Your message didn't go through.'' Bush doesn't say
> ``Reply to this bounce to confirm your original message.'' He simply
> throws the message away.
>
> This is supposed to be the mailing list for an open IETF working group.
> It's outrageous that valid messages are being silently discarded---even
> if the number is not as large as hundreds per year.
>
> ---D. J. Bernstein, Associate Professor, Department of Mathematics,
> Statistics, and Computer Science, University of Illinois at Chicago
>
> P.S. Out of my twelve messages, the five that were silently discarded
> are exactly the five that I would pick if I were a censor trying to bias
> the DNSEXT decisions in favor of the BIND company. Coincidence, right?
>
> P.P.S. Bush's mailing-list software doesn't cryptographically confirm
> unsubscription requests. I kept my subscription address private until
> Bush revealed it a few days ago. I'm working on obtaining a subscription
> through an address that Bush doesn't know is connected to me.
>
>
>



On Tue, 13 Jul 2004, Harald Tveit Alvestrand wrote:

> 
> 
> --On 12. juli 2004 12:55 -0400 Dean Anderson <dean@av8.com> wrote:
> 
> >>   it has been pointed out to you that you have the ability to
> >>   communicate with Rob Austein using the mail address that is posted
> >>   on the ietf dnsop charter web page:
> >
> > As Chairman Alvestrand has clearly stated, IETF email lists are not to be
> > used for making complaints.  One is not supposed to make complaints to the
> > DNSOP list.  The only exception to this rule is the main IETF list which
> > has administrative discussion as its purpose.
> 
> I do not recognize that as anything I have said.
> Please point to the quote.
> 
>                Harald
> 
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 14 01:20:20 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23693
	for <ietf-archive@ietf.org>; Wed, 14 Jul 2004 01:20:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BkcBn-0007mu-0u
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 01:20:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkc6Q-0006Lq-00
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 01:14:47 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BkbtK-0003jh-00; Wed, 14 Jul 2004 01:01:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkbiO-0005zC-00; Wed, 14 Jul 2004 00:49:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkbY7-0000hs-VK
	for ietf@megatron.ietf.org; Wed, 14 Jul 2004 00:39:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15960
	for <ietf@ietf.org>; Wed, 14 Jul 2004 00:39:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkbY5-0007jP-Pm
	for ietf@ietf.org; Wed, 14 Jul 2004 00:39:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkb1g-0001gn-00
	for ietf@ietf.org; Wed, 14 Jul 2004 00:05:49 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65]
	helo=arneill-py.sacramento.ca.us) by ietf-mx with esmtp (Exim 4.12)
	id 1BkaNE-0002fc-00
	for ietf@ietf.org; Tue, 13 Jul 2004 23:24:00 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Tue, 13 Jul 2004 20:23:25 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB2A8@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: Quote from me that isn't (Re: Email account utilizationwarning.)
thread-index: AcRpTYsm028mwDfPQWqIxeyzU0ofqwAArJgg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: RE: Quote from me that isn't (Re: Email account utilizationwarning.)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

Harald and David,

I'm getting tired of this. Can we take a hum and put this guy in the
troll box please? Frankly, I would even settle for Jim Fleming instead;
if we ought to have trolls, can we have good and/or entertaining ones at
least?

Do something; David, I remember what you did on RIPE MLs, FWIW it was
perfectly acceptable/appropriate. You have an overwhelming support in
the community if you take action.

Michel.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 14 12:39:29 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27377
	for <ietf-archive@ietf.org>; Wed, 14 Jul 2004 12:39:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bkmn5-00073f-OO
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 12:39:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkmmB-0006i9-00
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 12:38:36 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bkml3-000647-00; Wed, 14 Jul 2004 12:37:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkmYo-0005uS-Uf; Wed, 14 Jul 2004 12:24:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkmKu-0002dy-N1
	for ietf@megatron.ietf.org; Wed, 14 Jul 2004 12:10:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25815
	for <ietf@ietf.org>; Wed, 14 Jul 2004 12:10:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkmKt-0005QU-Tl
	for ietf@ietf.org; Wed, 14 Jul 2004 12:10:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkmJy-00055I-00
	for ietf@ietf.org; Wed, 14 Jul 2004 12:09:27 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BkmJ1-0004k2-00
	for ietf@ietf.org; Wed, 14 Jul 2004 12:08:28 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.34) id 1BkmJ2-000My9-0U
	for ietf@ietf.org; Wed, 14 Jul 2004 12:08:28 -0400
Date: Wed, 14 Jul 2004 12:08:27 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Message-ID: <AB0C4F754871C5B322AF95A0@scan.jck.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Subject: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Hi.

A question as to whether I'm the only one who is bothered by a
trend and, if not, if it is time for the community to give the
IESG and the RFC Editor some advice.

I note that my concern is _only_ about standards-track
documents: they are widely referenced and cited by title as well
as number, they are IETF work products, and the IESG presumably
has, or should have final authority about what they are called.
It seems plausible, indeed likely, that other conventions and
issues might reasonably apply to non-standards-track documents.


The RFC Editor has a policy about "abbreviations" in titles and
body text.  The title part of that policy, from 2223bis, is

" 2.9 Titles

		Abbreviations (e.g., acronyms) in a title should
		generally be expanded; the exception is abbreviations
		that are so common (like TCP, IP, SNMP, FTP, etc.) that
		every member of the IETF can be expected to recognize
		them immediately.  It is often helpful to follow the
		expansion with the parenthesized abbreviation, as in
   [...]"

While perhaps not as explicitly stated, this has been the policy
for as long as I can remember.  And, for whatever my opinion, it
is a policy I strongly support for "real" abbreviations.  In
years past, it has been applied with considerable discretion.
It appears to me that we are now going too far in the direction
of expansion.  In our industry, there are many occasions in
which a name is formed from an abbreviation, but the original
expansion rapidly loses meaning (or had a very contrived meaning
to start with).  In those cases, the string is a name, not an
"abbreviation", regardless of its origins.  The expansion of it
as an abbreviation doesn't provide significant information and
may, indeed, add to confusion.  

We have been exploiting that mechanism for years in the names of
IETF WGs: they are almost all abbreviations for something, but
some of those abbreviations are from strings that are so
contrived that many active participants in the relevant WGs
would have trouble either expanding the string or recognizing
the name of the WG if spelled out without the abbreviation.
Quick, what is "lemonade" and, based on the expansion, what does
the WG do?

I suggest that, for standards-track documents, if there are
terms that are almost always used as words, with little or no
information value in treating them as abbreviations (even if
they were derived that way), we should just treat them as words.
An explanation in the body text (not the title or abstract) as
to where the term came from might well be appropriate, but
forcing a long title is, I believe, not in IETF's best interests
in these cases.

To take an example --not because it is an especially good one,
but because it showed up in my mailbox today-- the RFC Editor
recently announced publication of RFC 3839, "MIME Type
Registrations for
3rd Generation Partnership Project (3GPP) Multimedia files".
Now, as far as I have been able to tell, everyone who has
anything to do with 3GPP or its standards knows it as "3GPP".
The RFC that defines the original cooperation agreement from
which this work presumably derives, RFC 3113, uses "3GPP" as a
name.   If one writes out "Third Generation Partnership Project"
(I believe that "3rd..." is not even correct), the active users
of those standards are likely to have to stop to think about
what one is talking about.  So we are not adding information
value by this expansion: we are being fussy (never a good
property for an engineering body) and we are making the title
much longer, which, in turn requires a short form which is a
potential source of confusion.  If we treat "3GPP" as a name,
which is how it is used, we would have had "MIME Type
Registrations for 3GPP Multimedia Files".

Our problem in this example is further illustrated by the
observation that, if it is an abbreviation, we can't figure out
what the abbreviation is.    It is "Third Generation Partnership
Project" in RFC 3314 and 3589, "3rd-Generation Partnership
Project" in RFC 3445, treated as a name in RFC 3574, and
apparently "3rd Generation Partnership Project" in the most
recent case.  Perhaps the inability of experts to agree on what
the "abbreviation" stands for is further evidence that it has
become a word.

Again, am I the only one who is bothered by this?  And, if not,
can we ask the IESG to think a bit about this matter going
forward?

thanks,
      john


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 14 13:21:40 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00120
	for <ietf-archive@ietf.org>; Wed, 14 Jul 2004 13:21:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BknRu-0005Jk-80
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 13:21:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BknQv-0004yF-00
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 13:20:42 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BknQG-0004cK-00; Wed, 14 Jul 2004 13:20:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BknFK-0005IN-Fq; Wed, 14 Jul 2004 13:08:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkn9J-0004PM-2p
	for ietf@megatron.ietf.org; Wed, 14 Jul 2004 13:02:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29267
	for <ietf@ietf.org>; Wed, 14 Jul 2004 13:02:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bkn9I-00070p-2b
	for ietf@ietf.org; Wed, 14 Jul 2004 13:02:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkn8O-0006i6-00
	for ietf@ietf.org; Wed, 14 Jul 2004 13:01:33 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12) id 1Bkn7c-000634-00
	for ietf@ietf.org; Wed, 14 Jul 2004 13:00:44 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
	by carwash.centive.com (SMSSMTP 4.0.0.59) with SMTP id
	M2004071413054500043
	for <ietf@ietf.org>; Wed, 14 Jul 2004 13:05:45 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by
	minglewood.incentivesystems.com with Microsoft SMTPSVC(6.0.3790.0); 
	Wed, 14 Jul 2004 12:56:15 -0400
Message-ID: <40F565AE.30508@centive.com>
Date: Wed, 14 Jul 2004 12:56:14 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
References: <AB0C4F754871C5B322AF95A0@scan.jck.com>
In-Reply-To: <AB0C4F754871C5B322AF95A0@scan.jck.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Jul 2004 16:56:15.0091 (UTC)
	FILETIME=[797BC430:01C469C3]
Content-Transfer-Encoding: 7bit
Subject: Re: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

John C Klensin wrote:

>The expansion of it
>as an abbreviation doesn't provide significant information and
>may, indeed, add to confusion.
>  
>
It also makes it harder to search rfc-index.txt, since names can span 
line boundaries and abbrevations can't.

>Now, as far as I have been able to tell, everyone who has
>anything to do with 3GPP or its standards knows it as "3GPP".
>  
>
It's also reported in the trade press as 3GPP; I don't have anything to 
do with it, but I recognize 3GPP and didn't recognize "3rd Generation 
Partnership Project".

-- 
/=============================================================\
|John Stracke      |jstracke@centive.com                      |
|Principal Engineer|http://www.centive.com                    |
|Centive           |My opinions are my own.                   |
|=============================================================|
|Q: What goes "Pieces of 7! Pieces of 7!"? A: A parroty error.|
\=============================================================/



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 14 13:57:46 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01863
	for <ietf-archive@ietf.org>; Wed, 14 Jul 2004 13:57:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bko0o-0001Mz-PY
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 13:57:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bknzg-00012B-00
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 13:56:37 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BknzI-0000iB-00; Wed, 14 Jul 2004 13:56:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BknsV-0003gP-E0; Wed, 14 Jul 2004 13:49:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BknfB-0001Rk-9z
	for ietf@megatron.ietf.org; Wed, 14 Jul 2004 13:35:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00914
	for <ietf@ietf.org>; Wed, 14 Jul 2004 13:35:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BknfA-00026r-94
	for ietf@ietf.org; Wed, 14 Jul 2004 13:35:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkneF-0001or-00
	for ietf@ietf.org; Wed, 14 Jul 2004 13:34:28 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12) id 1Bkndr-0001WZ-00
	for ietf@ietf.org; Wed, 14 Jul 2004 13:34:03 -0400
Received: from [10.20.30.249] (dsl2-63-249-109-252.cruzio.com [63.249.109.252])
	(authenticated bits=0)
	by above.proper.com (8.12.11/8.12.9) with ESMTP id i6EHXw7L037209;
	Wed, 14 Jul 2004 10:33:59 -0700 (PDT)
	(envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
X-Sender: phoffvpnc@mail.vpnc.org
Message-Id: <p0611041bbd1b1e102bfa@[10.20.30.249]>
In-Reply-To: <AB0C4F754871C5B322AF95A0@scan.jck.com>
References: <AB0C4F754871C5B322AF95A0@scan.jck.com>
Date: Wed, 14 Jul 2004 10:34:27 -0700
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Subject: Re: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

At 12:08 PM -0400 7/14/04, John C Klensin wrote:
>Again, am I the only one who is bothered by this?

No, not all. The RFC Editor is about to release revisions to the 
S/MIME specs where "MIME" is spelled out, for example.

>   And, if not,
>can we ask the IESG to think a bit about this matter going
>forward?

I'd certainly agree to this. It makes sense that if the RFC Editor is 
going to change something as major as the title of a document, that 
the IESG should at least see that with more than 48 hours to think 
about it.

--Paul Hoffman, Director
--VPN Consortium

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 14 14:57:41 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06412
	for <ietf-archive@ietf.org>; Wed, 14 Jul 2004 14:57:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bkowo-0005Xr-Ei
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 14:57:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkovf-00059J-00
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 14:56:31 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bkoue-0004W8-00; Wed, 14 Jul 2004 14:55:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkokE-0003oS-45; Wed, 14 Jul 2004 14:44:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkoab-0002Gs-Gz
	for ietf@megatron.ietf.org; Wed, 14 Jul 2004 14:34:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05097
	for <ietf@ietf.org>; Wed, 14 Jul 2004 14:34:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bkoaa-0005ub-9p
	for ietf@ietf.org; Wed, 14 Jul 2004 14:34:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkoZh-0005Zr-00
	for ietf@ietf.org; Wed, 14 Jul 2004 14:33:49 -0400
Received: from parsley.amaranth.net ([216.44.4.23])
	by ietf-mx with esmtp (Exim 4.12) id 1BkoYp-0005FI-00
	for ietf@ietf.org; Wed, 14 Jul 2004 14:32:55 -0400
Received: from Willow.senie.com (h004005591600.ne.client2.attbi.com
	[24.91.82.117]) (authenticated bits=0)
	by parsley.amaranth.net (8.12.8/8.12.8) with ESMTP id i6EIWhVW029938
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Wed, 14 Jul 2004 14:32:47 -0400
Message-Id: <6.1.2.0.2.20040714142230.063c0ce8@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Wed, 14 Jul 2004 14:30:36 -0400
To: ietf@ietf.org
From: Daniel Senie <dts@senie.com>
In-Reply-To: <40F565AE.30508@centive.com>
References: <AB0C4F754871C5B322AF95A0@scan.jck.com>
	<40F565AE.30508@centive.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

At 12:56 PM 7/14/2004, John Stracke wrote:
>John C Klensin wrote:
>
>>The expansion of it
>>as an abbreviation doesn't provide significant information and
>>may, indeed, add to confusion.
>>
>It also makes it harder to search rfc-index.txt, since names can span line 
>boundaries and abbrevations can't.
>
>>Now, as far as I have been able to tell, everyone who has
>>anything to do with 3GPP or its standards knows it as "3GPP".
>>
>It's also reported in the trade press as 3GPP; I don't have anything to do 
>with it, but I recognize 3GPP and didn't recognize "3rd Generation 
>Partnership Project".

Now a different viewpoint. When looking at drafts as they go by on 
id-announce, nothing gets me more annoyed than reading the title and 
summary, and having no idea what the document is about. The audience for 
documents spreads beyond those working in the very specific area. New 
acronyms pop up often, and frequently the same acronym means different 
things to different folks in this industry. Spelling out is essential.

In the example given, the best solution likely is to say "Third Generation 
Partnership Project (3GPP)." In that way, those searching for the acronym 
will find what they want, and those trying to figure out what a document is 
about will learn the definition of the acronym.

My test when writing the abstract for a dradft is to make things 
sufficiently clear that anyone in the IETF, and most people in the 
networking business, will be able to get some idea of what the document is, 
regardless of the reader's particular focus area.

At the very least, someone reading the title and abstract of a draft (or 
RFC) should be able to come away with enough of a sense of the document to 
know whether it's a document they want to read and is applicable to them, 
or it's not.

Dan 


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 14 15:23:43 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09311
	for <ietf-archive@ietf.org>; Wed, 14 Jul 2004 15:23:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BkpLz-0006Co-Vp
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 15:23:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkpKy-0005rf-00
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 15:22:40 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BkpK2-0005Ef-00; Wed, 14 Jul 2004 15:21:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkpFz-000263-Vk; Wed, 14 Jul 2004 15:17:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkpCA-0000cf-Fk
	for ietf@megatron.ietf.org; Wed, 14 Jul 2004 15:13:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08127
	for <ietf@ietf.org>; Wed, 14 Jul 2004 15:13:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkpC8-0002wA-DN
	for ietf@ietf.org; Wed, 14 Jul 2004 15:13:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkpBH-0002Yb-00
	for ietf@ietf.org; Wed, 14 Jul 2004 15:12:40 -0400
Received: from flamingo.mail.pas.earthlink.net ([207.217.120.232])
	by ietf-mx with esmtp (Exim 4.12) id 1BkpAT-0002Ew-00
	for ietf@ietf.org; Wed, 14 Jul 2004 15:11:49 -0400
Received: from h-66-167-207-210.snvacaid.dynamic.covad.net ([66.167.207.210]
	helo=oemcomputer)
	by flamingo.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1BkpAS-0007Vq-00
	for ietf@ietf.org; Wed, 14 Jul 2004 12:11:48 -0700
Message-ID: <000901c469d6$ab4bb5c0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <AB0C4F754871C5B322AF95A0@scan.jck.com><40F565AE.30508@centive.com>
	<6.1.2.0.2.20040714142230.063c0ce8@mail.amaranth.net>
Date: Wed, 14 Jul 2004 12:13:38 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Subject: Re: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi -

> From: "Daniel Senie" <dts@senie.com>
> To: <ietf@ietf.org>
> Sent: Wednesday, July 14, 2004 11:30 AM
> Subject: Re: Names of standards-track RFCs
...
> Now a different viewpoint. When looking at drafts as they go by on
> id-announce, nothing gets me more annoyed than reading the title and
> summary, and having no idea what the document is about. The audience for
> documents spreads beyond those working in the very specific area. New
> acronyms pop up often, and frequently the same acronym means different
> things to different folks in this industry. Spelling out is essential.
...

Agreed.  Spelling things out becomes even more important as
documents age.  Consider, for example, "IMP" in some of the
older RFCs.  I suspect many IETF participants have never seen
or used one, yet this was probably considered "well known" when
those RFCs were written.

Randy



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 14 21:43:37 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29149
	for <ietf-archive@ietf.org>; Wed, 14 Jul 2004 21:43:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BkvHd-0001Tu-MI
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 21:43:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkvGh-00017h-00
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 21:42:40 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BkvFm-0000RW-00; Wed, 14 Jul 2004 21:41:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bkv7t-0007Yh-GI; Wed, 14 Jul 2004 21:33:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkv36-0005je-PZ
	for ietf@megatron.ietf.org; Wed, 14 Jul 2004 21:28:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27032
	for <ietf@ietf.org>; Wed, 14 Jul 2004 21:28:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bkv34-0005kf-KV
	for ietf@ietf.org; Wed, 14 Jul 2004 21:28:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkusP-0003ep-00
	for ietf@ietf.org; Wed, 14 Jul 2004 21:17:35 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BkuUU-0006Xk-00
	for ietf@ietf.org; Wed, 14 Jul 2004 20:52:50 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1BkuUU-0000XO-KZ; Wed, 14 Jul 2004 20:52:50 -0400
Date: Wed, 14 Jul 2004 20:52:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Message-ID: <0921B37ADBF88A1C0C79BA98@scan.jck.com>
In-Reply-To: <000901c469d6$ab4bb5c0$7f1afea9@oemcomputer>
References: <AB0C4F754871C5B322AF95A0@scan.jck.com>
	<40F565AE.30508@centive.com>
	<6.1.2.0.2.20040714142230.063c0ce8@mail.amaranth.net>
	<000901c469d6$ab4bb5c0$7f1afea9@oemcomputer>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On Wednesday, 14 July, 2004 12:13 -0700 Randy Presuhn
<randy_presuhn@mindspring.com> wrote:

> Hi -
> 
>> From: "Daniel Senie" <dts@senie.com>
>> To: <ietf@ietf.org>
>> Sent: Wednesday, July 14, 2004 11:30 AM
>> Subject: Re: Names of standards-track RFCs
> ...
>> Now a different viewpoint. When looking at drafts as they go
>> by on id-announce, nothing gets me more annoyed than reading
>> the title and summary, and having no idea what the document
>> is about. The audience for documents spreads beyond those
>> working in the very specific area. New acronyms pop up often,
>> and frequently the same acronym means different things to
>> different folks in this industry. Spelling out is essential.
> ...
> 
> Agreed.  Spelling things out becomes even more important as
> documents age.  Consider, for example, "IMP" in some of the
> older RFCs.  I suspect many IETF participants have never seen
> or used one, yet this was probably considered "well known" when
> those RFCs were written.

Randy, that is actually a pretty good example of the problem.
If I tell you that something is an "Interface Message
Processor", and you have no history (direct or indirect) that
goes back to the ARPANET, what are you likely to think it is?
Something to do with email or instant messaging, perhaps?
Certainly neither you, nor any search engine you are likely to
be able to apply, are likely to assume that it is a box of the
same general class of things as "router".

I think the solution to the problem that you and Dan raise
--which I acknowledge is legitimate-- is to insist that
abstracts really reflect purpose and context.  That is in the
current rules too -- if you, or Dan, can't figure out what
something is about from the abstract, than the process has
slipped up somewhere.  Personally, I think that should be a
legitimate Last Call issue -- I don't know if the IESG would be
very happy about Last Call response notes that say "I couldn't
figure out what this was about from reading the abstract, so
didn't review the document, but the abstract ought to be fixed
and then the Last Call restarted", but it would, IMO, focus the
issue correctly.  Certainly, a "good abstracts" rule is harder
to enforce automatically or objectively than "spell out
abbreviations", but trying to put the burden of explaining the
relevancy or lack thereof to someone else's work on a document's
title, with our without abbreviations, is just not feasible, at
least IMO.

best,
    john


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 14 22:00:35 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29891
	for <ietf-archive@ietf.org>; Wed, 14 Jul 2004 22:00:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BkvY4-0006eS-69
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 22:00:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkvVp-0005sy-00
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 21:58:17 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BkvUU-0005Tp-00; Wed, 14 Jul 2004 21:56:54 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BkvKI-0001l5-Or; Wed, 14 Jul 2004 21:46:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkvHw-0003GI-9t; Wed, 14 Jul 2004 21:43:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkv94-0007zC-QH
	for ietf@megatron.ietf.org; Wed, 14 Jul 2004 21:34:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27724
	for <ietf@ietf.org>; Wed, 14 Jul 2004 21:34:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bkv93-0006Vn-5B
	for ietf@ietf.org; Wed, 14 Jul 2004 21:34:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkuze-0004vU-00
	for ietf@ietf.org; Wed, 14 Jul 2004 21:25:02 -0400
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx with esmtp (Exim 4.12) id 1Bkui1-0001O1-00
	for ietf@ietf.org; Wed, 14 Jul 2004 21:06:50 -0400
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.175); 
	Wed, 14 Jul 2004 18:06:10 -0700
Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by
	mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); 
	Wed, 14 Jul 2004 18:06:22 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com
	([157.54.0.39]) by RED-IMC-04.redmond.corp.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.0); Wed, 14 Jul 2004 18:06:20 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com
	([157.54.12.81]) by
	win-imc-01.wingroup.windeploy.ntdev.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1069); Wed, 14 Jul 2004 18:03:45 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 14 Jul 2004 18:06:16 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA0A079232@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Names of standards-track RFCs
thread-index: AcRp1+7+ym81lPQyQXaUv594gxQYTwAL72ow
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 15 Jul 2004 01:03:45.0356 (UTC)
	FILETIME=[940000C0:01C46A07]
Content-Transfer-Encoding: quoted-printable
Subject: RE: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

> Agreed.  Spelling things out becomes even more important as
> documents age.  Consider, for example, "IMP" in some of the
> older RFCs.  I suspect many IETF participants have never seen
> or used one, yet this was probably considered "well known" when
> those RFCs were written.

Or consider the RFC that describes Classical IP and ARP over Automatic
Teller Machines...

-- Christian Huitema

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 14 23:39:36 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05356
	for <ietf-archive@ietf.org>; Wed, 14 Jul 2004 23:39:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bkx5t-0007Tc-2Q
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 23:39:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkx4t-00075e-00
	for ietf-archive@ietf.org; Wed, 14 Jul 2004 23:38:36 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bkx3q-0006P2-00; Wed, 14 Jul 2004 23:37:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkwsJ-0004XE-0r; Wed, 14 Jul 2004 23:25:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkwpj-0003eY-1o
	for ietf@megatron.ietf.org; Wed, 14 Jul 2004 23:22:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04751
	for <ietf@ietf.org>; Wed, 14 Jul 2004 23:22:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bkwph-0001yC-31
	for ietf@ietf.org; Wed, 14 Jul 2004 23:22:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkwoT-0001dU-00
	for ietf@ietf.org; Wed, 14 Jul 2004 23:21:38 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1Bkwlw-000122-00
	for ietf@ietf.org; Wed, 14 Jul 2004 23:19:00 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1Bkwlw-0001R1-HR; Wed, 14 Jul 2004 23:19:00 -0400
Date: Wed, 14 Jul 2004 23:19:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: Christian Huitema <huitema@windows.microsoft.com>
Message-ID: <91D83C5BBFA925A50B50743C@scan.jck.com>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA0A079232@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References: <DAC3FCB50E31C54987CD10797DA511BA0A079232@WIN-MSG-10.
	wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On Wednesday, 14 July, 2004 18:06 -0700 Christian Huitema
<huitema@windows.microsoft.com> wrote:

>...
> Or consider the RFC that describes Classical IP and ARP over
> Automatic Teller Machines...

What did you say an ARP was?  Some sort of fuzzy alien, perhaps?
A digestive sound made after excessive SIPPING ?  Or, given
those teller machines, perhaps an Advanced Reimbursement
Procedure?
<grin>

I am not suggesting that we never expand an abbreviation and
never explain an acronym.   I suggest only that 

	* we need to rethink the application of the rules a bit
	for situations in which the constructed or shortened
	term has become a word in its own right and, more
	important, in which an expansion would tend to confuse
	rather than illuminate, and 
	
	* that we get a little more serious about the
	requirement that abstracts be sufficient for someone who
	doesn't know what the document is about to figure that
	out because titles will never be able to adequately do
	that job.

For the second, pretend that you are reading the title that
Christian cites above: "Classical IP and ARP over ATM".  Now
pretend that you don't know much about that corner of the IETF's
work, or even that you are an applications type who doesn't know
much about _anything_ at that layer.  Now expand the
abbreviations and try to convince yourself that you would know
something you didn't know with the present title.  Reaction to
present title: "Huh? Strange abbreviations".   Reaction to title
with abbreviations expanded: "Huh? What on earth do those words
mean?"

I don't see a lot of difference.

     john


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 15 02:30:51 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27549
	for <ietf-archive@ietf.org>; Thu, 15 Jul 2004 02:30:51 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bkzla-0000ky-Tv
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 02:30:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkzkc-0000IJ-00
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 02:29:50 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bkzk6-0007mN-00; Thu, 15 Jul 2004 02:29:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bkzdc-0004ny-MY; Thu, 15 Jul 2004 02:22:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkzc2-0003zs-Js
	for ietf@megatron.ietf.org; Thu, 15 Jul 2004 02:20:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26546
	for <ietf@ietf.org>; Thu, 15 Jul 2004 02:20:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bkzc0-0005Ak-6F
	for ietf@ietf.org; Thu, 15 Jul 2004 02:20:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkzb5-0004qJ-00
	for ietf@ietf.org; Thu, 15 Jul 2004 02:20:00 -0400
Received: from fw.osdl.org ([65.172.181.6] helo=mail.osdl.org)
	by ietf-mx with esmtp (Exim 4.12) id 1BkzaI-0004Oy-00
	for ietf@ietf.org; Thu, 15 Jul 2004 02:19:11 -0400
Received: from midway.verizon.net (build.pdx.osdl.net [172.20.1.2])
	by mail.osdl.org (8.11.6/8.11.6) with SMTP id i6F6IVk23691;
	Wed, 14 Jul 2004 23:18:31 -0700
Date: Wed, 14 Jul 2004 23:11:07 -0700
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: John C Klensin <john-ietf@jck.com>
Message-Id: <20040714231107.7030b61b.rddunlap@osdl.org>
In-Reply-To: <91D83C5BBFA925A50B50743C@scan.jck.com>
References: <DAC3FCB50E31C54987CD10797DA511BA0A079232@WIN-MSG-10.
	wingroup.windeploy.ntdev.microsoft.com>
	<91D83C5BBFA925A50B50743C@scan.jck.com>
Organization: OSDL
X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: huitema@windows.microsoft.com, ietf@ietf.org
Subject: Re: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

On Wed, 14 Jul 2004 23:19:00 -0400 John C Klensin wrote:

| 
| 
| --On Wednesday, 14 July, 2004 18:06 -0700 Christian Huitema
| <huitema@windows.microsoft.com> wrote:
| 
| >...
| > Or consider the RFC that describes Classical IP and ARP over
| > Automatic Teller Machines...
| 
| What did you say an ARP was?  Some sort of fuzzy alien, perhaps?
| A digestive sound made after excessive SIPPING ?  Or, given
| those teller machines, perhaps an Advanced Reimbursement
| Procedure?
| <grin>
| 
| I am not suggesting that we never expand an abbreviation and
| never explain an acronym.   I suggest only that 
| 
| 	* we need to rethink the application of the rules a bit
| 	for situations in which the constructed or shortened
| 	term has become a word in its own right and, more
| 	important, in which an expansion would tend to confuse
| 	rather than illuminate, and 
| 	
| 	* that we get a little more serious about the
| 	requirement that abstracts be sufficient for someone who
| 	doesn't know what the document is about to figure that
| 	out because titles will never be able to adequately do
| 	that job.
| 
| For the second, pretend that you are reading the title that
| Christian cites above: "Classical IP and ARP over ATM".  Now
| pretend that you don't know much about that corner of the IETF's
| work, or even that you are an applications type who doesn't know
| much about _anything_ at that layer.  Now expand the
| abbreviations and try to convince yourself that you would know
| something you didn't know with the present title.  Reaction to
| present title: "Huh? Strange abbreviations".   Reaction to title
| with abbreviations expanded: "Huh? What on earth do those words
| mean?"
| 
| I don't see a lot of difference.

:)

Good docs just include a glossary of terms/abbreviations/acronyms.

I'd prefer to see acronyms in the titles.

--
~Randy

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 15 02:58:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29122
	for <ietf-archive@ietf.org>; Thu, 15 Jul 2004 02:58:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bl0Ce-0002N8-G2
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 02:58:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl0Be-00020C-00
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 02:57:46 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bl0AY-0001NV-00; Thu, 15 Jul 2004 02:56:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl05I-0007KQ-P4; Thu, 15 Jul 2004 02:51:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl00B-0005Yq-4Q
	for ietf@megatron.ietf.org; Thu, 15 Jul 2004 02:45:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28295
	for <ietf@ietf.org>; Thu, 15 Jul 2004 02:45:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl008-0005bm-Uh
	for ietf@ietf.org; Thu, 15 Jul 2004 02:45:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkzzF-0005Ho-00
	for ietf@ietf.org; Thu, 15 Jul 2004 02:44:57 -0400
Received: from hdflem01.fl.hostdepot.net ([66.242.128.131])
	by ietf-mx with esmtp (Exim 4.12) id 1BkzyI-0004ea-00
	for ietf@ietf.org; Thu, 15 Jul 2004 02:43:58 -0400
Received: from vaio (unverified [67.166.143.234]) by hdflem01.fl.hostdepot.net
	(Vircom SMTPRS 3.1.293.1) with ESMTP id
	<B1040521954@hdflem01.fl.hostdepot.net> for <ietf@ietf.org>; 
	Thu, 15 Jul 2004 02:43:06 -0400
From: "Dr Harsh Verma" <hverma@glocol.net>
To: <ietf@ietf.org>
Date: Wed, 14 Jul 2004 23:43:01 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook, Build 11.0.5207
Thread-Index: AcRp18GWUwfdIIKWQ+qq3Qao/rm8VQALIovg
In-Reply-To: <000901c469d6$ab4bb5c0$7f1afea9@oemcomputer>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-Id: <E1BkzyI-0004ea-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Subject: RE: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Hi,

Ok, many of us have set up rules to move the WG emails to the appropriate
folders, so I am wondering how these email subject lines do not show the WG
name...

Request All to include a WG name in the subject line []s like [manet]. 
(which includes this email too!!)

I would think IETF moderator should add that, but which WG??

Thanks,
Harsh





_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 15 03:18:48 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29920
	for <ietf-archive@ietf.org>; Thu, 15 Jul 2004 03:18:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bl0W0-000120-Eh
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 03:18:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl0V0-0000h8-00
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 03:17:47 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bl0U3-00005p-00; Thu, 15 Jul 2004 03:16:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl0RS-0005qC-SM; Thu, 15 Jul 2004 03:14:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl0PL-00056H-HU
	for ietf@megatron.ietf.org; Thu, 15 Jul 2004 03:11:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29627
	for <ietf@ietf.org>; Thu, 15 Jul 2004 03:11:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl0PJ-0006V5-37
	for ietf@ietf.org; Thu, 15 Jul 2004 03:11:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl0OT-0006CH-00
	for ietf@ietf.org; Thu, 15 Jul 2004 03:11:01 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12) id 1Bl0Nm-0005qg-00
	for ietf@ietf.org; Thu, 15 Jul 2004 03:10:18 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id RAA535507;
	Thu, 15 Jul 2004 17:09:46 +1000 (EST)
Message-ID: <40F62DBA.4C76E1D8@swin.edu.au>
Date: Thu, 15 Jul 2004 17:09:46 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures,
	Swinburne University of Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
CC: ietf@ietf.org
References: <E1BkzyI-0004ea-00@ietf-mx>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: Re: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Dr Harsh Verma wrote:
> 
> Hi,
> 
> Ok, many of us have set up rules to move the WG emails to the appropriate
> folders, so I am wondering how these email subject lines do not show the WG
> name...
> 
> Request All to include a WG name in the subject line []s like [manet].
> (which includes this email too!!)
> 
> I would think IETF moderator should add that, but which WG??

My mysteriously functional email filter rules appear to work
just fine without extra crud in subject lines.... (but how
amusingly ironic a request for a thread on the topic of reducing
crud in RFC titles...)

gja

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 15 04:13:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02273
	for <ietf-archive@ietf.org>; Thu, 15 Jul 2004 04:13:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bl1NF-0003L4-Ew
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 04:13:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl1MG-0002zi-00
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 04:12:48 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bl1LB-0002Lo-00; Thu, 15 Jul 2004 04:11:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl18k-00016C-2m; Thu, 15 Jul 2004 03:58:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl168-0007qP-4J
	for ietf@megatron.ietf.org; Thu, 15 Jul 2004 03:56:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01459
	for <ietf@ietf.org>; Thu, 15 Jul 2004 03:55:51 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl15q-000580-RJ
	for ietf@ietf.org; Thu, 15 Jul 2004 03:55:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl14t-0004oj-00
	for ietf@ietf.org; Thu, 15 Jul 2004 03:54:51 -0400
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bl145-0004Cm-00; Thu, 15 Jul 2004 03:54:01 -0400
Received: from [10.1.1.112] (marseille.netlab.nec.de [195.37.70.15])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id 696CC1BAC4D;
	Thu, 15 Jul 2004 09:53:24 +0200 (CEST)
Message-ID: <40F637F3.1000809@netlab.nec.de>
Date: Thu, 15 Jul 2004 09:53:23 +0200
From: Lars Eggert <lars.eggert@netlab.nec.de>
Organization: NEC Network Laboratories
User-Agent: Mozilla Thunderbird 0.7.1 (Macintosh/20040626)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org, ietf-secretariat@ietf.org
Subject: ical version of the IETF-60 agenda
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1693531088=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--===============1693531088==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms030301080201030200080303"

This is a cryptographically signed message in MIME format.

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

Hi,

FYI, I've again made ical versions of the agenda available at

	webcal://icalx.com/public/larse/IETF-60.ics
	webcal://icalx.com/public/larse/IETF-60-TZ.ics

The first one (IETF-60.ics) has all events without a timezone, the 
second one (IETF-60-TZ.ics) has them all tagged with the US/Pacific 
timezone.

Apple users can click on the links and subscribe. This may work for 
Mozilla users as well. Replace "webcal://" with "http://" to download 
instead of subscribing.

Lars

PS: A perl script periodically updates the ical version based on the 
ASCII agenda at 
http://ietf.org/meetings/agenda_60ietf-secretariat@ietf.org.txt. No 
guarantees for accuracy!
-- 
Lars Eggert                                     NEC Network Laboratories

--------------ms030301080201030200080303
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJpzCC
Ay4wggKXoAMCAQICAwyFWjANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UE
ChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv
bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwHhcNMDQwNjE3MDcyMjAzWhcNMDUwNjE3MDcyMjAz
WjCBhDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn
Z2VydDEoMCYGCSqGSIb3DQEJARYZbGFycy5lZ2dlcnRAbmV0bGFiLm5lYy5kZTEiMCAGCSqG
SIb3DQEJARYTbGFycy5lZ2dlcnRAZ214Lm5ldDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAOowMZjwQREXIdWxQacJDyqczykKpfIVmid2m8xBuUO53uWgnK3F8R20u/7PVugU
zjNNqaivnU6qHtr/jdAn1UnyXzA/4Re+AqsKNiw8hZkVonkJ+G4O0TFzMNeWUdrjX1FaSAsL
uAPA6661cN4YDzrOYC3O3zgGtVvJAra0+iw9eD2qWsnH0AVLFtq7H5ZFhz5zeOeCrrayqEhf
S6tnTSjBzaH8SOdeemPTxdLRbMptLSy7lEFo8f1xisltw2eRT0txoUCqq0mjFEp8LgJ+s6p1
4M4cG3CDkKd5kNjdTWaokAo4qmpfF9IyA7uheaAHAz8UOH5GsH+Vkjbz5yFO1SsCAwEAAaNL
MEkwOQYDVR0RBDIwMIEZbGFycy5lZ2dlcnRAbmV0bGFiLm5lYy5kZYETbGFycy5lZ2dlcnRA
Z214Lm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBAE9rOnUtJERYLNbDztLI
sH4AolAWkvNKoj7Ikst1M1X3myXqxYAHa9bsoPJy15qEV2B4ftOmJLrZL9kb8RZnzGBii8a/
XQ5wqaHZAJYcxQ6lp6UDTabhQN7J1trAOKgs+PFlF3lm6NOkXygiQH5PPO5kIHRjNvXpNGYe
C7S3K8YsMIIDLjCCApegAwIBAgIDDIVaMA0GCSqGSIb3DQEBBAUAMGIxCzAJBgNVBAYTAlpB
MSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3
dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNDA2MTcwNzIyMDNaFw0wNTA2
MTcwNzIyMDNaMIGEMQ8wDQYDVQQEEwZFZ2dlcnQxDTALBgNVBCoTBExhcnMxFDASBgNVBAMT
C0xhcnMgRWdnZXJ0MSgwJgYJKoZIhvcNAQkBFhlsYXJzLmVnZ2VydEBuZXRsYWIubmVjLmRl
MSIwIAYJKoZIhvcNAQkBFhNsYXJzLmVnZ2VydEBnbXgubmV0MIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA6jAxmPBBERch1bFBpwkPKpzPKQql8hWaJ3abzEG5Q7ne5aCcrcXx
HbS7/s9W6BTOM02pqK+dTqoe2v+N0CfVSfJfMD/hF74Cqwo2LDyFmRWieQn4bg7RMXMw15ZR
2uNfUVpICwu4A8DrrrVw3hgPOs5gLc7fOAa1W8kCtrT6LD14PapaycfQBUsW2rsflkWHPnN4
54KutrKoSF9Lq2dNKMHNofxI5156Y9PF0tFsym0tLLuUQWjx/XGKyW3DZ5FPS3GhQKqrSaMU
SnwuAn6zqnXgzhwbcIOQp3mQ2N1NZqiQCjiqal8X0jIDu6F5oAcDPxQ4fkawf5WSNvPnIU7V
KwIDAQABo0swSTA5BgNVHREEMjAwgRlsYXJzLmVnZ2VydEBuZXRsYWIubmVjLmRlgRNsYXJz
LmVnZ2VydEBnbXgubmV0MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEEBQADgYEAT2s6dS0k
RFgs1sPO0siwfgCiUBaS80qiPsiSy3UzVfebJerFgAdr1uyg8nLXmoRXYHh+06Ykutkv2Rvx
FmfMYGKLxr9dDnCpodkAlhzFDqWnpQNNpuFA3snW2sA4qCz48WUXeWbo06RfKCJAfk887mQg
dGM29ek0Zh4LtLcrxiwwggM/MIICqKADAgECAgENMA0GCSqGSIb3DQEBBQUAMIHRMQswCQYD
VQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAY
BgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZp
Y2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzAp
BgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMwNzE3MDAw
MDAwWhcNMTMwNzE2MjM1OTU5WjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENv
bnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls
IElzc3VpbmcgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5o
wHUEcJ3f6f+jHuy9zfVb8hp2vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuv
PAsH5/EfkTYkKhPPK9Xzgnc9A74r/rsYPge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAe
ZBlyYLf7AgMBAAGjgZQwgZEwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0
hjJodHRwOi8vY3JsLnRoYXd0ZS5jb20vVGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDAL
BgNVHQ8EBAMCAQYwKQYDVR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4
MA0GCSqGSIb3DQEBBQUAA4GBAEiM0VCD6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6ot
nzYvwPQcUCCTcDz9reFhYsPZOhl+hLGZGwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V
2vf3h9bGCE6u9uo05RAaWzVNd+NWIXiC3CEZNd4ksdMdRv9dX2VPMYIDOzCCAzcCAQEwaTBi
MQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEs
MCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAwyFWjAJBgUr
DgMCGgUAoIIBpzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0w
NDA3MTUwNzUzMjNaMCMGCSqGSIb3DQEJBDEWBBSmRat4FUxV4ETlN9JpwHAqGN+S5zBSBgkq
hkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIB
QDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDB4BgkrBgEEAYI3EAQxazBpMGIxCzAJBgNVBAYT
AlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNU
aGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIDDIVaMHoGCyqGSIb3DQEJEAIL
MWugaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAwyF
WjANBgkqhkiG9w0BAQEFAASCAQAsCUpbRfTbh8RLmT6reQhViSQnuvndLxTMSMWmceW+Kj3E
xikLyf7J4Ny8Qu3oOVq+7/bFJxcEVyNdReub8Wotc7RFrnCNr6bf5dNY5Pf6VzrVNlNFcQPx
pU64BQhMF/XIrqmeqEh6iYcVq03coYeQq2ZppA4+DqgSD4luOY1tyvq5h1tkSygwEM5xtxBX
ukx+X6krLn9ko6/uKgIYgAsAybQgy8hPsDDe4JX4JtE+g26O9NETaMEni2GrpIdTDt+eqm2h
ZLXNxWZiZ1xHK1G+KGAwL/LGO/IsfTKAWjzBinc9/9SEwKBOVlaQLimtiKQ+pHAA66iT032Y
RlbaB1dxAAAAAAAA
--------------ms030301080201030200080303--


--===============1693531088==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1693531088==--



From ietf-bounces@ietf.org  Thu Jul 15 07:46:34 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12977
	for <ietf-archive@ietf.org>; Thu, 15 Jul 2004 07:46:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bl4h9-0002aX-3h
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 07:46:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl4g6-0002BX-00
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 07:45:30 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bl4fB-0001iR-00; Thu, 15 Jul 2004 07:44:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl4Qp-0000QS-CL; Thu, 15 Jul 2004 07:29:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkpnZ-0002Xz-Jy
	for ietf@megatron.ietf.org; Wed, 14 Jul 2004 15:52:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12085
	for <ietf@ietf.org>; Wed, 14 Jul 2004 15:52:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkpnY-0000a2-En
	for ietf@ietf.org; Wed, 14 Jul 2004 15:52:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkpma-0000Bw-00
	for ietf@ietf.org; Wed, 14 Jul 2004 15:51:13 -0400
Received: from [65.85.17.142] (helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12) id 1Bkpld-0007WO-00
	for ietf@ietf.org; Wed, 14 Jul 2004 15:50:13 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id i6EJd5I09703
	for <ietf@ietf.org>; Wed, 14 Jul 2004 12:39:05 -0700
Date: Wed, 14 Jul 2004 12:39:04 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
In-Reply-To: <6.1.2.0.2.20040714142230.063c0ce8@mail.amaranth.net>
Message-ID: <Pine.LNX.4.33.0407141204300.9241-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Thu, 15 Jul 2004 07:29:41 -0400
Subject: Re: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60



On Wed, 14 Jul 2004, Daniel Senie wrote:

>
> At the very least, someone reading the title and abstract of a draft (or
> RFC) should be able to come away with enough of a sense of the document to
> know whether it's a document they want to read and is applicable to them,
> or it's not.

Best served in my opinion by expanding acronyms in the body of the
abstract and not the title.  Well more specifically, in the announcement
email subject line since that improves processing of my inbox.

Dave Morris


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 15 09:47:07 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19787
	for <ietf-archive@ietf.org>; Thu, 15 Jul 2004 09:47:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bl6Zo-0002g9-CN
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 09:47:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl6Yn-0002Jt-00
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 09:46:06 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bl6Xn-0001iI-00; Thu, 15 Jul 2004 09:45:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl6MM-000342-9w; Thu, 15 Jul 2004 09:33:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl6HM-000221-Fg
	for ietf@megatron.ietf.org; Thu, 15 Jul 2004 09:28:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18721
	for <ietf@ietf.org>; Thu, 15 Jul 2004 09:28:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl6HL-0004DQ-R8
	for ietf@ietf.org; Thu, 15 Jul 2004 09:28:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl6GU-0003ub-00
	for ietf@ietf.org; Thu, 15 Jul 2004 09:27:10 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12)
	id 1Bl6Fi-0003Ia-00
	for ietf@ietf.org; Thu, 15 Jul 2004 09:26:22 -0400
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-3.cisco.com with ESMTP; 15 Jul 2004 06:27:17 +0000
X-BrightmailFiltered: true
Received: from cisco.com (sjc-vpn2-440.cisco.com [10.21.113.184])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with SMTP id i6FDPInK022903
	for <ietf@ietf.org>; Thu, 15 Jul 2004 06:25:18 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation);
	Thu, 15 Jul 2004 09:25:17 -0400
Date: Thu, 15 Jul 2004 09:25:17 -0400
From: Scott W Brim <sbrim@cisco.com>
To: ietf@ietf.org
Message-ID: <20040715132517.GC2484@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <sbrim@cisco.com>, ietf@ietf.org
References: <E1BkzyI-0004ea-00@ietf-mx> <40F62DBA.4C76E1D8@swin.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40F62DBA.4C76E1D8@swin.edu.au>
User-Agent: Mutt/1.4.1i
Subject: Re: Names of standards-track RFCs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Thu, Jul 15, 2004 05:09:46PM +1000, grenville armitage allegedly wrote:
> > Request All to include a WG name in the subject line []s like [manet].
> > (which includes this email too!!)
> 
> My mysteriously functional email filter rules appear to work
> just fine without extra crud in subject lines.... (but how
> amusingly ironic a request for a thread on the topic of reducing
> crud in RFC titles...)

Agreed, twice.

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 15 10:57:05 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25394
	for <ietf-archive@ietf.org>; Thu, 15 Jul 2004 10:57:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bl7fX-0001bp-El
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 10:57:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl7eY-0001HT-00
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 10:56:07 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bl7da-0000g1-00; Thu, 15 Jul 2004 10:55:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl7Vp-0004EU-GD; Thu, 15 Jul 2004 10:47:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl7MS-0001M7-Bt
	for ietf@megatron.ietf.org; Thu, 15 Jul 2004 10:37:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24271
	for <ietf@ietf.org>; Thu, 15 Jul 2004 10:37:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl7MR-0002oU-8v
	for ietf@ietf.org; Thu, 15 Jul 2004 10:37:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl7LZ-0002Uc-00
	for ietf@ietf.org; Thu, 15 Jul 2004 10:36:29 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1Bl7Ks-0002AR-00
	for ietf@ietf.org; Thu, 15 Jul 2004 10:35:47 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1Bl7Km-0005Iv-BV; Thu, 15 Jul 2004 10:35:40 -0400
Date: Thu, 15 Jul 2004 10:35:40 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dr Harsh Verma <hverma@glocol.net>
Message-ID: <B8C8915F026C8AD0E7D26411@scan.jck.com>
In-Reply-To: <E1BkzyI-0004ea-00@ietf-mx>
References: <E1BkzyI-0004ea-00@ietf-mx>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Mailing list identification, e.g., [IETF], in subject
 lines (was: RE: Names of standards-track RFCs )
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Hi.

Since I'm the apparent offender...

Those little inserts are a function of list management software
(which software is chosen and how it is configured), and not the
actions of individual authors (despite the indication I manually
included in this posting).  If a change in how the IETF list
works is needed, you probably need to take it up with the
Secretariat or the IESG.

best,
    john


--On Wednesday, 14 July, 2004 23:43 -0700 Dr Harsh Verma
<hverma@glocol.net> wrote:

> Hi,
> 
> Ok, many of us have set up rules to move the WG emails to the
> appropriate folders, so I am wondering how these email subject
> lines do not show the WG name...
> 
> Request All to include a WG name in the subject line []s like
> [manet].  (which includes this email too!!)
> 
> I would think IETF moderator should add that, but which WG??
> 
> Thanks,
> Harsh
> 
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf





_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 15 11:35:11 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27742
	for <ietf-archive@ietf.org>; Thu, 15 Jul 2004 11:35:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bl8GP-0006M3-N8
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 11:35:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl8FM-0005yD-00
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 11:34:09 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bl8EJ-0005L1-00; Thu, 15 Jul 2004 11:33:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl8AK-0007Gf-7q; Thu, 15 Jul 2004 11:28:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl87o-0006Vo-5y
	for ietf@megatron.ietf.org; Thu, 15 Jul 2004 11:26:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27290
	for <ietf@ietf.org>; Thu, 15 Jul 2004 11:26:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl87n-0003NZ-92
	for ietf@ietf.org; Thu, 15 Jul 2004 11:26:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl86u-00033Y-00
	for ietf@ietf.org; Thu, 15 Jul 2004 11:25:25 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12) id 1Bl86C-0002XQ-00
	for ietf@ietf.org; Thu, 15 Jul 2004 11:24:40 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 2BA1361AD5; Thu, 15 Jul 2004 17:24:10 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 04232-09; Thu, 15 Jul 2004 17:24:09 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id 67A8761A93; Thu, 15 Jul 2004 17:24:08 +0200 (CEST)
Date: Thu, 15 Jul 2004 17:24:07 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dr Harsh Verma <hverma@glocol.net>
Message-ID: <55EEF84EB99208BEDCE001B2@[10.0.0.2]>
In-Reply-To: <B8C8915F026C8AD0E7D26411@scan.jck.com>
References: <E1BkzyI-0004ea-00@ietf-mx> <B8C8915F026C8AD0E7D26411@scan.jck.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Mailing list identification, e.g., [IETF], in subject lines
 (was: RE: Names of standards-track RFCs )
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Short answer:

No.

Long answer:

This item has been discussed to death once every 3 months on this very 
list. We have never found a consensus to add these tags.

                  Harald

--On 15. juli 2004 10:35 -0400 John C Klensin <john-ietf@jck.com> wrote:

> Hi.
>
> Since I'm the apparent offender...
>
> Those little inserts are a function of list management software
> (which software is chosen and how it is configured), and not the
> actions of individual authors (despite the indication I manually
> included in this posting).  If a change in how the IETF list
> works is needed, you probably need to take it up with the
> Secretariat or the IESG.
>





_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 15 13:00:24 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03936
	for <ietf-archive@ietf.org>; Thu, 15 Jul 2004 13:00:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bl9as-0003sA-II
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 13:00:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl9Zm-0003X6-00
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 12:59:19 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bl9Z1-0002uz-00; Thu, 15 Jul 2004 12:58:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl9Rg-0003VM-Ex; Thu, 15 Jul 2004 12:50:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl9GW-0007hX-Vy
	for ietf@megatron.ietf.org; Thu, 15 Jul 2004 12:39:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02024
	for <ietf@ietf.org>; Thu, 15 Jul 2004 12:39:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl9GW-0004Fq-0P
	for ietf@ietf.org; Thu, 15 Jul 2004 12:39:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl9FN-0003qt-00
	for ietf@ietf.org; Thu, 15 Jul 2004 12:38:14 -0400
Received: from adsl-66-137-237-100.dsl.rcsntx.swbell.net ([66.137.237.100]
	helo=gw.frascone.com) by ietf-mx with esmtp (Exim 4.12)
	id 1Bl9EG-0003HD-00
	for ietf@ietf.org; Thu, 15 Jul 2004 12:37:04 -0400
Received: by gw.frascone.com (Postfix, from userid 500)
	id 8AE8A58058B; Thu, 15 Jul 2004 11:37:03 -0500 (CDT)
Date: Thu, 15 Jul 2004 11:37:03 -0500
From: David Frascone <dave@frascone.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Message-ID: <20040715163703.GC32043@wolverine.frascone.com>
References: <E1BkzyI-0004ea-00@ietf-mx> <B8C8915F026C8AD0E7D26411@scan.jck.com>
	<55EEF84EB99208BEDCE001B2@[10.0.0.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <55EEF84EB99208BEDCE001B2@[10.0.0.2]>
User-Agent: Mutt/1.4.1i
Cc: ietf@ietf.org
Subject: Re: Mailing list identification, e.g., [IETF],
	in subject lines (was: RE: Names of standards-track RFCs )
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Not to feed the troll, but, if I remember correctly, the overwhelming
response is always:  we don't need it.  Procmail can filter fine without
it.

So, since there's no one vehemently opposed to it (that I can remember),
why not just turn it on, to avoid the quarterly request?  Not everyone
uses procmail / nice mailers to filter their mail.  Some people are even
forced to use Windows mailers! *shudder*

-Dave

On Thursday, 15 Jul 2004, Harald Tveit Alvestrand wrote:
> Short answer:
> 
> No.
> 
> Long answer:
> 
> This item has been discussed to death once every 3 months on this very 
> list. We have never found a consensus to add these tags.
> 
>                  Harald
> 
> --On 15. juli 2004 10:35 -0400 John C Klensin <john-ietf@jck.com> wrote:
> 
> >Hi.
> >
> >Since I'm the apparent offender...
> >
> >Those little inserts are a function of list management software
> >(which software is chosen and how it is configured), and not the
> >actions of individual authors (despite the indication I manually
> >included in this posting).  If a change in how the IETF list
> >works is needed, you probably need to take it up with the
> >Secretariat or the IESG.
> >
> 
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 

-- 
David Frascone

    Fife. n. Small shrill instrument that rhymes with wife.

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 15 20:26:28 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21662
	for <ietf-archive@ietf.org>; Thu, 15 Jul 2004 20:26:28 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BlGYW-00064n-Jc
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 20:26:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlGXZ-0005ju-00
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 20:25:29 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BlGWk-00057Y-00; Thu, 15 Jul 2004 20:24:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlGR2-0004ak-5n; Thu, 15 Jul 2004 20:18:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlGNx-0003s0-Bw
	for ietf@megatron.ietf.org; Thu, 15 Jul 2004 20:15:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21234
	for <ietf@ietf.org>; Thu, 15 Jul 2004 20:15:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlGNv-0002SB-9U
	for ietf@ietf.org; Thu, 15 Jul 2004 20:15:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlGN5-00029E-00
	for ietf@ietf.org; Thu, 15 Jul 2004 20:14:40 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12) id 1BlGMV-0001mm-00
	for ietf@ietf.org; Thu, 15 Jul 2004 20:14:03 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id KAA637198;
	Fri, 16 Jul 2004 10:13:24 +1000 (EST)
Message-ID: <40F71DA4.602153D9@swin.edu.au>
Date: Fri, 16 Jul 2004 10:13:24 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures,
	Swinburne University of Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
References: <E1BkzyI-0004ea-00@ietf-mx> <B8C8915F026C8AD0E7D26411@scan.jck.com>
	<55EEF84EB99208BEDCE001B2@[10.0.0.2]>
	<20040715163703.GC32043@wolverine.frascone.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: Re: Mailing list identification, e.g., [IETF],
 in subject lines (was: RE: Names of standards-track RFCs )
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit


David Frascone wrote:
	[..]
> So, since there's no one vehemently opposed to it (that I can remember),
> why not just turn it on,

Finally we're a true Standards Organization.

cheers,
gja

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 15 20:44:45 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22629
	for <ietf-archive@ietf.org>; Thu, 15 Jul 2004 20:44:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BlGqD-00048Y-RH
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 20:44:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlGp1-0003mf-00
	for ietf-archive@ietf.org; Thu, 15 Jul 2004 20:43:31 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BlGoG-00039Q-00; Thu, 15 Jul 2004 20:42:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlGgm-00004x-Pn; Thu, 15 Jul 2004 20:35:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlGeK-0007xh-9D
	for ietf@megatron.ietf.org; Thu, 15 Jul 2004 20:32:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22038
	for <ietf@ietf.org>; Thu, 15 Jul 2004 20:32:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlGeI-0000IX-FP
	for ietf@ietf.org; Thu, 15 Jul 2004 20:32:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlGdJ-0007lz-00
	for ietf@ietf.org; Thu, 15 Jul 2004 20:31:25 -0400
Received: from bay18-dav3.bay18.hotmail.com ([65.54.187.183] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BlGcE-00079D-00
	for ietf@ietf.org; Thu, 15 Jul 2004 20:30:18 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Thu, 15 Jul 2004 17:29:49 -0700
Received: from 66.193.147.68 by bay18-dav3.bay18.hotmail.com with DAV;
	Fri, 16 Jul 2004 00:29:49 +0000
X-Originating-IP: [66.193.147.68]
X-Originating-Email: [anubee24@hotmail.com]
X-Sender: anubee24@hotmail.com
From: "002" <anubee24@hotmail.com>
To: <ietf@ietf.org>
Date: Thu, 15 Jul 2004 02:29:49 -0700
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <BAY18-DAV3R8Cp2YpMM00028951@hotmail.com>
X-OriginalArrivalTime: 16 Jul 2004 00:29:49.0289 (UTC)
	FILETIME=[00D29590:01C46ACC]
Subject: post
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0143901271=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=2.0 required=5.0 tests=AWL,DATE_IN_PAST_12_24,
	FROM_ENDS_IN_NUMS,HTML_20_30,HTML_MESSAGE autolearn=no version=2.60

This is a multi-part message in MIME format.

--===============0143901271==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_003F_01C46A13.9A0072A0"

This is a multi-part message in MIME format.

------=_NextPart_000_003F_01C46A13.9A0072A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


------=_NextPart_000_003F_01C46A13.9A0072A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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

------=_NextPart_000_003F_01C46A13.9A0072A0--


--===============0143901271==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============0143901271==--



From ietf-bounces@ietf.org  Fri Jul 16 16:30:36 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00799
	for <ietf-archive@ietf.org>; Fri, 16 Jul 2004 16:30:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BlZLn-0001iF-6L
	for ietf-archive@ietf.org; Fri, 16 Jul 2004 16:30:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlZKv-0001Li-00
	for ietf-archive@ietf.org; Fri, 16 Jul 2004 16:29:42 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BlZK3-0000w7-00; Fri, 16 Jul 2004 16:28:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlZAJ-0003Qp-Vk; Fri, 16 Jul 2004 16:18:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlNI8-0001o4-0K
	for ietf@megatron.ietf.org; Fri, 16 Jul 2004 03:38:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11941
	for <ietf@ietf.org>; Fri, 16 Jul 2004 03:37:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlNI5-0002Iu-K6
	for ietf@ietf.org; Fri, 16 Jul 2004 03:37:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlNHL-0001xw-00
	for ietf@ietf.org; Fri, 16 Jul 2004 03:37:12 -0400
Received: from mailsrv.psl.com.sg ([202.14.153.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BlNGe-0001YK-00
	for ietf@ietf.org; Fri, 16 Jul 2004 03:36:28 -0400
Received: from jadefox ([10.81.113.120])
	by mailsrv.psl.com.sg (8.12.11/8.12.11) with ESMTP id i6G7XfGq005667
	for <ietf@ietf.org>; Fri, 16 Jul 2004 15:33:41 +0800 (SGT)
From: "Saravanan Govindan" <sgovindan@psl.com.sg>
To: <ietf@ietf.org>
Date: Fri, 16 Jul 2004 15:36:39 +0800
Organization: Panasonic Singapore Laboratories
Message-ID: <002601c46b07$a1e24440$7871510a@jadefox>
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, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 16 Jul 2004 16:18:42 -0400
Subject: Los Angeles to San Diego
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sgovindan@psl.com.sg
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Dear All,

Would anyone know how to hire a shuttle or van from the LA International
Airport to San Diego? I know there are a number of car rentals, but I am
trying to find some other type of road transport. 

Regards
Saravanan

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.720 / Virus Database: 476 - Release Date: 14/07/2004
 


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul 16 23:07:40 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00375
	for <ietf-archive@ietf.org>; Fri, 16 Jul 2004 23:07:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BlfY1-0001yV-TA
	for ietf-archive@ietf.org; Fri, 16 Jul 2004 23:07:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlfX4-0001et-00
	for ietf-archive@ietf.org; Fri, 16 Jul 2004 23:06:38 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BlfWP-0001I7-00; Fri, 16 Jul 2004 23:05:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlfQP-0005vt-RO; Fri, 16 Jul 2004 22:59:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlfML-0005XR-Mf
	for ietf@megatron.ietf.org; Fri, 16 Jul 2004 22:55:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29867
	for <ietf@ietf.org>; Fri, 16 Jul 2004 22:55:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlfMH-00067f-J0
	for ietf@ietf.org; Fri, 16 Jul 2004 22:55:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlfLJ-0005og-00
	for ietf@ietf.org; Fri, 16 Jul 2004 22:54:29 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12) id 1BlfKM-0005Ng-00
	for ietf@ietf.org; Fri, 16 Jul 2004 22:53:30 -0400
Received: from f04m-5-162.d3.club-internet.fr ([212.195.80.162]
	helo=jfc2.jefsey.com) by montage.altserver.com with esmtp (Exim 4.34)
	id 1BlfKI-0007DB-BO
	for ietf@ietf.org; Fri, 16 Jul 2004 19:53:27 -0700
Message-Id: <6.1.1.1.2.20040717005831.050db120@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Sat, 17 Jul 2004 01:05:11 +0200
To: ietf@ietf.org
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <55EEF84EB99208BEDCE001B2@[10.0.0.2]>
References: <E1BkzyI-0004ea-00@ietf-mx> <B8C8915F026C8AD0E7D26411@scan.jck.com>
	<55EEF84EB99208BEDCE001B2@[10.0.0.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
Subject: [IETF] Mailing list identification, e.g., [IETF], in subject
 lines (was: RE: Names of standards-track RFCs )
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,DATE_IN_PAST_03_06 
	autolearn=no version=2.60

At 17:24 15/07/04, Harald Tveit Alvestrand wrote:
>This item has been discussed to death once every 3 months on this very 
>list. We have never found a consensus to add these tags.

It would be illusory to have everyone (consensus) accepting to be 
nice/polite to a few/many others and to conform to a de facto standard they 
did not write.

Tiring, but so human.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 19 08:35:15 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10682
	for <ietf-archive@ietf.org>; Mon, 19 Jul 2004 08:35:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BmXMT-0004Sw-34
	for ietf-archive@ietf.org; Mon, 19 Jul 2004 08:35:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BmXLR-0004DS-00
	for ietf-archive@ietf.org; Mon, 19 Jul 2004 08:34:13 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BmXKx-0003xo-00; Mon, 19 Jul 2004 08:33:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BmXB7-0007MI-FZ; Mon, 19 Jul 2004 08:23:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlakP-0007W7-FI
	for ietf@megatron.ietf.org; Fri, 16 Jul 2004 18:00:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12302
	for <ietf@ietf.org>; Fri, 16 Jul 2004 18:00:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlakL-0003cJ-Jk
	for ietf@ietf.org; Fri, 16 Jul 2004 18:00:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Blaib-00033m-00
	for ietf@ietf.org; Fri, 16 Jul 2004 17:58:14 -0400
Received: from sa.vix.com ([204.152.187.1]) by ietf-mx with esmtp (Exim 4.12)
	id 1Bladx-0001lb-00
	for ietf@ietf.org; Fri, 16 Jul 2004 17:53:25 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 39DF213DE5; Fri, 16 Jul 2004 21:52:57 +0000 (GMT)
To: ietf@ietf.org
References: <20040706034320.5B87C872F4@mercury.lcs.mit.edu>
	<E1Bi10g-0002yO-00@ietf-mx>
From: Paul Vixie <vixie@vix.com>
Date: 16 Jul 2004 21:52:57 +0000
In-Reply-To: <E1Bi10g-0002yO-00@ietf-mx>
Message-ID: <g3pt6vk4au.fsf@sa.vix.com>
Lines: 21
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Mon, 19 Jul 2004 08:23:31 -0400
Subject: Re: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

> ... Why doesn't this group join hand to insure full exploitation of IPv6?

based on http://www.chinatechnews.com/index.php?action=show&type=news&id=1405,
i'd say that the answer to that question is implied by the following quote:

        China and the United States are currently the only two countries
        that possess root domain name analysis servers, IP address servers,
        independent domain names, IP addresses and MAC address sources.

IPv6 is apparently being seen as just one more way in which the United States
is trying to dominate the world's commerce and communications systems.  The
IPv9 team in China is able to justify continued government funding simply by
saying that "this will make China a peer of the United States".

One way of reading these tea leaves is to say that ICANN hasn't been seen as
truly open, truly inclusive, or truly independent.  "Lapdog of the US-DoC"
was one critic's description.  Speaking as an early adopter of Vint's and
Jon's philosophy of openness/inclusiveness/interoperability, it's really
painful to see balkanization and to consider it inevitable.
-- 
Paul Vixie

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 19 08:39:10 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11006
	for <ietf-archive@ietf.org>; Mon, 19 Jul 2004 08:39:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BmXQF-0005Vt-Gz
	for ietf-archive@ietf.org; Mon, 19 Jul 2004 08:39:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BmXOA-00051l-00
	for ietf-archive@ietf.org; Mon, 19 Jul 2004 08:37:03 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BmXNC-0004Up-00; Mon, 19 Jul 2004 08:36:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BmXB8-0007MT-DG; Mon, 19 Jul 2004 08:23:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bm8yV-0002d6-9M
	for ietf@megatron.ietf.org; Sun, 18 Jul 2004 06:32:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01641
	for <ietf@ietf.org>; Sun, 18 Jul 2004 06:32:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bm8yP-0006wd-6p
	for ietf@ietf.org; Sun, 18 Jul 2004 06:32:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bm8xP-0006j2-00
	for ietf@ietf.org; Sun, 18 Jul 2004 06:31:48 -0400
Received: from colo.khms.westfalen.de ([213.239.196.208] ident=Debian-exim)
	by ietf-mx with esmtp (Exim 4.12) id 1Bm8wN-0006KP-00
	for ietf@ietf.org; Sun, 18 Jul 2004 06:30:43 -0400
Received: from khms.vpn
	([10.172.192.2]:39620 helo=khms.westfalen.de ident=Debian-exim)
	by colo.khms.westfalen.de with asmtp (TLS-1.0:RSA_ARCFOUR_SHA:16)
	(Exim 4.32) id 1Bm8wF-00015O-Tv
	for ietf@ietf.org; Sun, 18 Jul 2004 12:30:36 +0200
Received: from root (helo=khms.westfalen.de)
	by khms.westfalen.de with local-bsmtp (Exim 4.32) id 1Bm8w8-0000iB-LC
	for ietf@ietf.org; Sun, 18 Jul 2004 12:30:28 +0200
Received: by khms.westfalen.de (CrossPoint v3.12d.kh14 R/C435);
	18 Jul 2004 12:27:17 +0200
Date: 18 Jul 2004 12:11:00 +0200
From: kaih@khms.westfalen.de (Kai Henningsen)
To: ietf@ietf.org
Message-ID: <9D6kdCYXw-B@khms.westfalen.de>
In-Reply-To: <55EEF84EB99208BEDCE001B2@[10.0.0.2]>
X-Mailer: CrossPoint v3.12d.kh14 R/C435
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Organization: Organisation? Me?! Are you kidding?
References: <E1BkzyI-0004ea-00@ietf-mx> <B8C8915F026C8AD0E7D26411@scan.jck.com>
	<B8C8915F026C8AD0E7D26411@scan.jck.com>
	<55EEF84EB99208BEDCE001B2@[10.0.0.2]>
X-No-Junk-Mail: I do not want to get *any* junk mail.
Comment: Unsolicited commercial mail will incur an US$100 handling fee per
	received mail.
X-Fix-Your-Modem: +++ATS2=255&WO1
X-Mailman-Approved-At: Mon, 19 Jul 2004 08:23:31 -0400
Subject: Re: Mailing list identification, e.g., [IETF], in subject lines
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

harald@alvestrand.no (Harald Tveit Alvestrand)  wrote on 15.07.04 in <55EEF84EB99208BEDCE001B2@[10.0.0.2]>:

> Short answer:
>
> No.
>
> Long answer:
>
> This item has been discussed to death once every 3 months on this very
> list. We have never found a consensus to add these tags.

 List-Id: IETF-Discussion <ietf.ietf.org>
 List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
 	<mailto:ietf-request@ietf.org?subject=unsubscribe>
 List-Post: <mailto:ietf@ietf.org>
 List-Help: <mailto:ietf-request@ietf.org?subject=help>
 List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
 	<mailto:ietf-request@ietf.org?subject=subscribe>

If that's not enough for sorting, nothing is.

MfG Kai

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 19 13:28:50 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08611
	for <ietf-archive@ietf.org>; Mon, 19 Jul 2004 13:28:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BmbwZ-0007Qi-41
	for ietf-archive@ietf.org; Mon, 19 Jul 2004 13:28:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BmbvR-00077m-00
	for ietf-archive@ietf.org; Mon, 19 Jul 2004 13:27:42 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bmbue-0006kp-00; Mon, 19 Jul 2004 13:26:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bmbme-00050M-1T; Mon, 19 Jul 2004 13:18:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BmbXl-0002Rt-Dt
	for ietf@megatron.ietf.org; Mon, 19 Jul 2004 13:03:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06458
	for <ietf@ietf.org>; Mon, 19 Jul 2004 13:03:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BmbXk-0007cR-Fm
	for ietf@ietf.org; Mon, 19 Jul 2004 13:03:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BmbWn-0007LL-00
	for ietf@ietf.org; Mon, 19 Jul 2004 13:02:14 -0400
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx with esmtp (Exim 4.12) id 1BmbVr-0006nh-00
	for ietf@ietf.org; Mon, 19 Jul 2004 13:01:15 -0400
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.191); 
	Mon, 19 Jul 2004 10:00:45 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by
	mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); 
	Mon, 19 Jul 2004 10:00:47 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com
	([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.0); Mon, 19 Jul 2004 10:00:43 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com
	([157.54.12.81]) by
	win-imc-01.wingroup.windeploy.ntdev.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1069); Mon, 19 Jul 2004 09:59:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Jul 2004 10:00:41 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA0A15D604@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Central registries (was RE: Chinese IPv9)
thread-index: AcRtjLp4jNbCkHzAToayOGRcv6KKzgAIikXA
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Paul Vixie" <vixie@vix.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 19 Jul 2004 16:59:41.0737 (UTC)
	FILETIME=[C8B83190:01C46DB1]
Content-Transfer-Encoding: quoted-printable
Subject: Central registries (was RE: Chinese IPv9)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

Paul, this IPv9 hoopla strikes me as another research project harping
the nationalistic chord in order to get funding. This is not exactly
news. It was a common undertone in many European research proposals in
the 1980's and 1990's, and it is also a classic line in NSF or DARPA
proposals. The officials in the Chinese government may fall for that
line a few times, but I believe that they are smart and will eventually
allocate their grants based on technical merit rather than non-technical
arguments.

There is however an interesting technical point behind all these
discussions of number allocations. The general Internet architecture is
largely decentralized, but we have accepted to rely on a few centralized
functions. The obvious ones are DNS names and IP addresses, but there
are many others, such as port numbers and generally the various
registries held by IANA.

Centralized registries are expedient, and are not a big concern when the
network is small, or when the central authority is virtuous. However,
the network is big and the central authority becomes a locus of power.
The history text books teach us that loci of power attract politicians
and politician-friendly profiteers, and the Internet does not appear to
be an exception.

It seems that we, the IETF community, have been complacent to
centralization and have dug ourselves in a centralization hole. We may
hope to get out of it by ensuring that ICANN remains in charge and
remains virtuous, but that goes very much against all historic
precedents.

When in a hole, one should obviously first stop digging: that would mean
a moratorium on the creation of IANA registries. One should also think
hard about technical alternatives to central registries. In some case,
that may mean a slightly larger field in a protocol format, so a large
random number can be used instead of a short registered number. In other
cases, like name resolution, that may require a technical break-through.
But we should definitely think about it!

-- Christian Huitema

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 19 20:12:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13917;
	Mon, 19 Jul 2004 20:12:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BmiFe-0006bk-Ej; Mon, 19 Jul 2004 20:12:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bmi5K-00022c-91; Mon, 19 Jul 2004 20:02:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BmhiF-0005LF-QD
	for ietf@megatron.ietf.org; Mon, 19 Jul 2004 19:38:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06936
	for <ietf@ietf.org>; Mon, 19 Jul 2004 19:38:25 -0400 (EDT)
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BmhiF-0004h8-OF
	for ietf@ietf.org; Mon, 19 Jul 2004 19:38:29 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id JAA674459;
	Tue, 20 Jul 2004 09:37:43 +1000 (EST)
Message-ID: <40FC5B46.FA9C1917@swin.edu.au>
Date: Tue, 20 Jul 2004 09:37:42 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures,
	Swinburne University of Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
References: <20040706034320.5B87C872F4@mercury.lcs.mit.edu>
	<E1Bi10g-0002yO-00@ietf-mx> <g3pt6vk4au.fsf@sa.vix.com>
	<6.1.1.1.2.20040719200850.0527a710@mail.jefsey.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: 7bit
Subject: Re: Chinese IPv9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit


"JFC (Jefsey) Morfin" wrote:
	[..]
> - We need a multilingual multinational root matrix.

....instead I think we're going to be getting a root canal.

gja

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul 20 09:47:59 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19683;
	Tue, 20 Jul 2004 09:47:59 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BmuyZ-0000HU-4Y; Tue, 20 Jul 2004 09:48:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BmuuA-0000jZ-Fq; Tue, 20 Jul 2004 09:43:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BmupO-0007jS-EM
	for ietf@megatron.ietf.org; Tue, 20 Jul 2004 09:38:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19102
	for <ietf@ietf.org>; Tue, 20 Jul 2004 09:38:40 -0400 (EDT)
Received: from 206-169-2-196.gen.twtelecom.net ([206.169.2.196]
	helo=mail.optistreams.net) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BmupX-000080-Dl
	for ietf@ietf.org; Tue, 20 Jul 2004 09:38:51 -0400
Received: from [9.33.155.80] [129.42.208.182] by mail.optistreams.net with
	ESMTP (SMTPD32-8.04) id AA75196E029C; Tue, 20 Jul 2004 06:13:25 -0700
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA0A15D604@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References: <DAC3FCB50E31C54987CD10797DA511BA0A15D604@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0CD1A5A3-DA52-11D8-9B96-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
From: Nathaniel Borenstein <nsb@guppylake.com>
Date: Tue, 20 Jul 2004 09:38:14 -0400
To: "Christian Huitema" <huitema@windows.microsoft.com>
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: 7bit
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: Central registries (was RE: Chinese IPv9)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: 7bit

Christian -- Your mesage seems to presume rather optimistically that 
there can be a workable technical alternative to central registries.  
If not -- and I'm skeptical -- your "stop digging" advice might 
translate into "stop improving the net."

At the very least, it's an open question whether it is possible to 
build an Internet without central registries.  Until we prove otherwise 
-- and I  would certainly support research and experiments to devise an 
alternative -- central registries will remain essential, and no amount 
of wishful thinking will eliminate the need for a *political* solution 
to the management question.

The IETF is in the business of technical solutions, but that doesn't 
mean that there *is* a technical solution to every problem.  Where 
there isn't (or might not be) it is our duty to make the public and 
politicians aware of the political issues and the technical tradeoffs.  
(The fact that such political discussions tend to be messy and 
unsatisfying doesn't make the duty any less real.)  We should be 
careful not to dodge this responsibility by pretending that we're sure 
we can come up with an alternative when there isn't one on the horizon.

In short, I think it would be a mistake to declare a "moratorium on the 
creation of IANA registries" without at least a plausible theory about 
what kind of alternatives might be possible.  -- Nathaniel

On Jul 19, 2004, at 1:00 PM, Christian Huitema wrote:

> Paul, this IPv9 hoopla strikes me as another research project harping
> the nationalistic chord in order to get funding. This is not exactly
> news. It was a common undertone in many European research proposals in
> the 1980's and 1990's, and it is also a classic line in NSF or DARPA
> proposals. The officials in the Chinese government may fall for that
> line a few times, but I believe that they are smart and will eventually
> allocate their grants based on technical merit rather than 
> non-technical
> arguments.
>
> There is however an interesting technical point behind all these
> discussions of number allocations. The general Internet architecture is
> largely decentralized, but we have accepted to rely on a few 
> centralized
> functions. The obvious ones are DNS names and IP addresses, but there
> are many others, such as port numbers and generally the various
> registries held by IANA.
>
> Centralized registries are expedient, and are not a big concern when 
> the
> network is small, or when the central authority is virtuous. However,
> the network is big and the central authority becomes a locus of power.
> The history text books teach us that loci of power attract politicians
> and politician-friendly profiteers, and the Internet does not appear to
> be an exception.
>
> It seems that we, the IETF community, have been complacent to
> centralization and have dug ourselves in a centralization hole. We may
> hope to get out of it by ensuring that ICANN remains in charge and
> remains virtuous, but that goes very much against all historic
> precedents.
>
> When in a hole, one should obviously first stop digging: that would 
> mean
> a moratorium on the creation of IANA registries. One should also think
> hard about technical alternatives to central registries. In some case,
> that may mean a slightly larger field in a protocol format, so a large
> random number can be used instead of a short registered number. In 
> other
> cases, like name resolution, that may require a technical 
> break-through.
> But we should definitely think about it!
>
> -- Christian Huitema
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>
>


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul 20 14:50:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15082;
	Tue, 20 Jul 2004 14:50:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BmzhT-000559-ME; Tue, 20 Jul 2004 14:50:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BmzVl-00083U-5B; Tue, 20 Jul 2004 14:38:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BmzNN-0005O1-Qk
	for ietf@megatron.ietf.org; Tue, 20 Jul 2004 14:30:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13488
	for <ietf@ietf.org>; Tue, 20 Jul 2004 14:30:04 -0400 (EDT)
Received: from cyphermail.sandelman.ottawa.on.ca ([205.150.200.161]
	helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BmzNX-0004mp-UU
	for ietf@ietf.org; Tue, 20 Jul 2004 14:30:17 -0400
Received: from lox.sandelman.ottawa.on.ca
	(IDENT:root@lox.sandelman.ottawa.on.ca [205.150.200.178])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i6KITtX23148
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	FAIL); Tue, 20 Jul 2004 14:29:56 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (desk.marajade.sandelman.ca
	[205.150.200.247])
	by lox.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i6KIZXk20943
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	FAIL); Tue, 20 Jul 2004 14:35:39 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i6KISdtA003789
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 20 Jul 2004 14:28:39 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i6KISbbg003786; Tue, 20 Jul 2004 14:28:38 -0400
To: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: Message from Nathaniel Borenstein <nsb@guppylake.com> of "Tue,
	20 Jul 2004 09:38:14 EDT."
	<0CD1A5A3-DA52-11D8-9B96-000A9571873E@guppylake.com> 
References: <DAC3FCB50E31C54987CD10797DA511BA0A15D604@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<0CD1A5A3-DA52-11D8-9B96-000A9571873E@guppylake.com> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 20 Jul 2004 14:28:37 -0400
Message-ID: <3784.1090348117@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: Christian Huitema <huitema@windows.microsoft.com>,
        IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: Central registries (was RE: Chinese IPv9) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1

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


>>>>> "Nathaniel" == Nathaniel Borenstein <nsb@guppylake.com> writes:
    Nathaniel> Christian -- Your mesage seems to presume rather
    Nathaniel> optimistically that there can be a workable technical
    Nathaniel> alternative to central registries.  If not -- and I'm
    Nathaniel> skeptical -- your "stop digging" advice might translate
    Nathaniel> into "stop improving the net."

  I think that there are many places where we can do without a central 
registries. Alas, the places that are the easiest are also the places
where it matters the least.
  
  This doesn't mean stop improving. It means do so with some thought.
  And the places where it matters the most - allocation of prefixes for
IPv4 and IPv6, are already done deals.

  This is why I was and I still am interested in geographically based
allocation of addresses. Something that does not require any registry,
such as Tony Hain's proposals, or various mutations of it. 
  Even if they do not result in efficiencies in the routing table, I
think they would go a long way to making people happy. It won't make
China happy --- the last thing they want is every rice farmer to have
his own /48 that he can number each of the rice grains he produces with.
  China wants their own central registry, IMHO. Geo-allocation would
make any arguments about central registries more clear -- it would tell
us which people are concerned about being on the wrong end of the
scarcity stick, vs which ones want their own sticks.

    Nathaniel> research and experiments to devise an alternative --
    Nathaniel> central registries will remain essential, and no amount
    Nathaniel> of wishful thinking will eliminate the need for a
    Nathaniel> *political* solution to the management question.

  This is true.

    Nathaniel> The IETF is in the business of technical solutions, but
    Nathaniel> that doesn't mean that there *is* a technical solution to
    Nathaniel> every problem.  Where there isn't (or might not be) it is
    Nathaniel> our duty to make the public and politicians aware of the

  It is a question of constraints. Right now, central repositories have
not bothered the people who have been involved -- equipment makers and
ISPs. It might bother other people, but they haven't been invited to the
requirements discussion.

    Nathaniel> In short, I think it would be a mistake to declare a
    Nathaniel> "moratorium on the creation of IANA registries" without
    Nathaniel> at least a plausible theory about what kind of
    Nathaniel> alternatives might be possible.  -- Nathaniel

  I think that Christian actually did propose some things:

    >> should also think hard about technical alternatives to central
    >> registries. In some case, that may mean a slightly larger field
    >> in a protocol format, so a large random number can be used
    >> instead of a short registered number. In other cases, like name
    >> resolution, that may require a technical break-through.  But we
    >> should definitely think about it!

  I think that reducing the number of IANA registries should be a goal
simply because it takes IANA a lot of work to manage them.  

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [

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

iQCVAwUBQP1kU4qHRg3pndX9AQGeyAP9E9GPVOQ9m9BrdazY+dhai43nUETjGHBq
90+kZMr9YnsYC56YBlv9CON681JpHqU6NtszjsEhA0bZgBcNtG/uhl9wqOuQUll7
K7bCwJhda2ccuCzYH8St2OvLmwpv1FBGDeeN4cF2ryMdIISJICetsTi62vaVk1Uk
4JljjoLoeOg=
=nd0Y
-----END PGP SIGNATURE-----

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul 20 15:19:00 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18439;
	Tue, 20 Jul 2004 15:19:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bn08v-0005Vj-D7; Tue, 20 Jul 2004 15:19:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bn03W-00009H-Lg; Tue, 20 Jul 2004 15:13:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bn002-0006ET-JT
	for ietf@megatron.ietf.org; Tue, 20 Jul 2004 15:10:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17010
	for <ietf@ietf.org>; Tue, 20 Jul 2004 15:10:00 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bn00B-0005Kr-Ib
	for ietf@ietf.org; Tue, 20 Jul 2004 15:10:14 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0/8.13.0) with ESMTP id i6KJ9su7019619;
	Tue, 20 Jul 2004 15:09:54 -0400
Message-Id: <200407201909.i6KJ9su7019619@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4+dev
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
In-Reply-To: Your message of "Tue, 20 Jul 2004 14:28:37 EDT."
	<3784.1090348117@marajade.sandelman.ottawa.on.ca> 
References: <DAC3FCB50E31C54987CD10797DA511BA0A15D604@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<0CD1A5A3-DA52-11D8-9B96-000A9571873E@guppylake.com>
	<3784.1090348117@marajade.sandelman.ottawa.on.ca>
Mime-Version: 1.0
Date: Tue, 20 Jul 2004 15:09:54 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: Central registries (was RE: Chinese IPv9) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1393397009=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002

--===============1393397009==
Content-Type: multipart/signed; boundary="==_Exmh_618298136P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Tue, 20 Jul 2004 14:28:37 EDT, Michael Richardson said:
>   Even if they do not result in efficiencies in the routing table, I
> think they would go a long way to making people happy.

If you want to make people happy by promising technically infeasible solutions,
I suggest a career in politics rather than technology.

Geographically allocated addresses are a *dead* *dead* *dead* end, unless you
have some new work-around for the *very real* routing table explosion issues
they cause.  If wishes were horses, then beggars would ride - but we're the IETF,
so we'll settle for a *workable* design for a new bicycle. ;)


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

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

iD8DBQFA/W4CcC3lWbTT17ARAu6gAJ9L7mmQaFJQnBjUNpCpWuE1XJgnfACeO676
WwSVWmCRkFVaUUutuWcpNzk=
=WLKS
-----END PGP SIGNATURE-----

--==_Exmh_618298136P--


--===============1393397009==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1393397009==--



From ietf-bounces@ietf.org  Wed Jul 21 00:38:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16680;
	Wed, 21 Jul 2004 00:38:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bn8sF-0004Ka-2D; Wed, 21 Jul 2004 00:38:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bn8fQ-00057W-A4; Wed, 21 Jul 2004 00:25:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bn8cI-0002HD-Pj
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 00:22:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15751
	for <ietf@ietf.org>; Wed, 21 Jul 2004 00:22:03 -0400 (EDT)
Received: from vapor.isi.edu ([128.9.64.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bn8cW-0004BS-VY
	for ietf@ietf.org; Wed, 21 Jul 2004 00:22:24 -0400
Received: from [192.168.1.3] (dsl081-036-151.lax1.dsl.speakeasy.net
	[64.81.36.151])
	by vapor.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i6L4L4B24732;
	Tue, 20 Jul 2004 21:21:04 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
Content-Transfer-Encoding: 7bit
From: Aaron Falk <falk@ISI.EDU>
Date: Tue, 20 Jul 2004 21:20:54 -0700
To: ietf@ietf.org
X-Mailer: Apple Mail (2.618)
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: falk@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
Cc: Henrik Levkowetz <henrik@levkowetz.com>, Mark Allman <mallman@icir.org>
Subject: survey on Friday IETF sessions
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

One of the issues we seem to be running into is an increased number of
conflicts in meeting slots at IETF meetings.  For instance, two years
ago the meeting slots predominantly were used for 6-7 meetings, whereas
the agenda for the upcoming meeting has no slot except for Friday
without 7-8 meetings.  There has been some discussion about IETF
meetings on Fridays, possibly extending the agenda to later Friday
afternoon.  In the interest of creating a more informed discussion,
we've put together a short questionnaire to gather some data on
attending meetings from IETF participants.

See http://ietf.levkowetz.com/survey/attendance/

--aaron  (for Aaron Falk, Henrik Levkowetz, and Mark Allman)

PS. Please don't complain about the questions.  If you have better,
feel free to build your own -- more data is good!  :)


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 21 14:37:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11031;
	Wed, 21 Jul 2004 14:37:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnLyo-0006uU-Ov; Wed, 21 Jul 2004 14:38:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnLsi-000872-GZ; Wed, 21 Jul 2004 14:31:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnLpo-0007Fz-EO
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 14:28:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10454
	for <ietf@ietf.org>; Wed, 21 Jul 2004 14:28:54 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnLq7-0006mt-Si
	for ietf@ietf.org; Wed, 21 Jul 2004 14:29:21 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i6LISId16499
	for <ietf@ietf.org>; Wed, 21 Jul 2004 21:28:18 +0300
Date: Wed, 21 Jul 2004 21:28:17 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Message-ID: <Pine.LNX.4.44.0407212125001.16177-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: IETF60: time needed for check-in at San Diego?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581

Hi,

Now that there's a lot of stuff on Friday sessions, and most have 
flights leaving some time during the afternoon, a critical question is 
probably how much time do you need at the San Diego airport for 
check-in, etc. -- either for a domestic flight (ultimate destination 
possibly being outside of the US) or for a direct international 
flight.

Any experiences?  Is 1.5 or 2 hours (for example) enough at SD?

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


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 21 15:15:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14541;
	Wed, 21 Jul 2004 15:15:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnMZ3-0007P6-1Z; Wed, 21 Jul 2004 15:15:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnMVB-0002jn-15; Wed, 21 Jul 2004 15:11:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnMMD-0003ag-07
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 15:02:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12945
	for <ietf@ietf.org>; Wed, 21 Jul 2004 15:02:23 -0400 (EDT)
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnMMb-0007E0-M0
	for ietf@ietf.org; Wed, 21 Jul 2004 15:02:50 -0400
Received: from consulintel02 by consulintel.es (MDaemon.PRO.v7.1.2.R)
	with ESMTP id md50000150704.msg
	for <ietf@ietf.org>; Wed, 21 Jul 2004 21:04:43 +0200
Message-ID: <1a4701c46f55$1fbbc840$8700000a@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <Pine.LNX.4.44.0407212125001.16177-100000@netcore.fi>
Date: Wed, 21 Jul 2004 21:01:25 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Wed, 21 Jul 2004 21:04:43 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Wed, 21 Jul 2004 21:04:48 +0200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: quoted-printable
Subject: Re: IETF60: time needed for check-in at San Diego?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: quoted-printable

Is not only check-in time ...

My last very unfortunate experience was traveling back to Madrid from Las Vegas, in January.

The check-in was about 2 hours queue, and then it took to me almost 4 hours (standing up, an infinite zig-zag of people filling all the airport) to pass the security check.

Consequently me, and most of the people in the airport miss their flights, and the travel companies rejected to allocate a new flight. They said claim for the cost to the US government.

I was booked for the following day flight (only option available to catch my next meeting in time, flying directly to Brussels instead of via Madrid), extra hotel expenses pay by myself also. Again same answer, claim to the US government.

By the way, the most curious thing is that despite the international air security regulations regarding the baggage can't travel alone, the planes take-off with the baggage ... and of course, you only get it 2-3 days after arriving to destination. No compensation either. Claim to the US government. They can break all the rules, even the security rules, just because improper security handling.

One moth ago, flying back from Santa Monica it was only 3 hours total time, but you never know ...

What is clear is that the US government should consider this type of events and provide facilities. Otherwise, the IETF, IEEE and other organizations, should consider very seriously skipping event in US.

Clearly it seems that this is irrelevant (in general) to US people, they don't mind what they government do, good or bad, but negative for the rest of the world. So the rest of the world should also consider offering the same pain and wait time to the US nationals ? I'm not asking for it, but the question is an exercise for US nationals to understand our situation, and consider taking some actions.

Hopefully we don't have this +4 hours situation anymore.

Regards,
Jordi

----- Original Message -----=20
From: "Pekka Savola" <pekkas@netcore.fi>
To: <ietf@ietf.org>
Sent: Wednesday, July 21, 2004 8:28 PM
Subject: IETF60: time needed for check-in at San Diego?


> Hi,
>=20
> Now that there's a lot of stuff on Friday sessions, and most have=20
> flights leaving some time during the afternoon, a critical question is=20
> probably how much time do you need at the San Diego airport for=20
> check-in, etc. -- either for a domestic flight (ultimate destination=20
> possibly being outside of the US) or for a direct international=20
> flight.
>=20
> Any experiences?  Is 1.5 or 2 hours (for example) enough at SD?
>=20
> --=20
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20


**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 21 15:33:57 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16525;
	Wed, 21 Jul 2004 15:33:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnMrA-0007g4-FE; Wed, 21 Jul 2004 15:34:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnMhN-00018k-3w; Wed, 21 Jul 2004 15:24:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnMXg-0004CT-EI
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 15:14:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14415
	for <ietf@ietf.org>; Wed, 21 Jul 2004 15:14:14 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnMY4-0007OD-Df
	for ietf@ietf.org; Wed, 21 Jul 2004 15:14:41 -0400
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i6LJF6i9063695;
	Wed, 21 Jul 2004 21:15:07 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 21 Jul 2004 21:13:51 +0200
To: Aaron Falk <falk@ISI.EDU>
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: Mark Allman <mallman@icir.org>, Henrik Levkowetz <henrik@levkowetz.com>,
        ietf@ietf.org
Subject: Re: survey on Friday IETF sessions
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

On 21-jul-04, at 6:20, Aaron Falk wrote:

> In the interest of creating a more informed discussion,
> we've put together a short questionnaire to gather some data on
> attending meetings from IETF participants.

Ok, that's great of course, but I have two different suggestions:

1. Get a better feel for which wgs can overlap without problems and 
which can't. (Hint: two wgs with "6" in their name probably shouldn't 
overlap...)

2. Move away from the session/break/session model. So rather than let 
the rooms be empty for 1.5 hours during the lunch and dinner breaks, 
schedule sessions more or less continuously. People who want to eat are 
no worse off, as they still get to attend one session and eat during 
another, while those who can't stand overlap now have a better chance 
of being able to attend everything they want to.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 21 17:32:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06013;
	Wed, 21 Jul 2004 17:32:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnOhq-0004sE-H8; Wed, 21 Jul 2004 17:32:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnMyg-00072V-KH; Wed, 21 Jul 2004 15:42:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnMsz-0004jX-5r
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 15:36:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16714
	for <ietf@ietf.org>; Wed, 21 Jul 2004 15:36:14 -0400 (EDT)
Received: from cyphermail.sandelman.ottawa.on.ca ([205.150.200.161]
	helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnMtM-0007iC-Qn
	for ietf@ietf.org; Wed, 21 Jul 2004 15:36:42 -0400
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca
	[205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i6LJa0X02708
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK); Wed, 21 Jul 2004 15:36:01 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i6LJZxtA006393
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 21 Jul 2004 15:35:59 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i6LJZvRs006389; Wed, 21 Jul 2004 15:35:59 -0400
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
In-Reply-To: Message from "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es> 
	of "Wed, 21 Jul 2004 21:01:25 +0200."
	<1a4701c46f55$1fbbc840$8700000a@consulintel.es> 
References: <Pine.LNX.4.44.0407212125001.16177-100000@netcore.fi>
	<1a4701c46f55$1fbbc840$8700000a@consulintel.es> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 21 Jul 2004 15:35:57 -0400
Message-ID: <6387.1090438557@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: ietf@ietf.org
Subject: Re: IETF60: time needed for check-in at San Diego? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126


>>>>> "JORDI" == JORDI PALET MARTINEZ <jordi.palet@consulintel.es> writes:
    JORDI> What is clear is that the US government should consider this
    JORDI> type of events and provide facilities. Otherwise, the IETF,
    JORDI> IEEE and other organizations, should consider very seriously
    JORDI> skipping event in US.

  What he said.

--
]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 21 18:37:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18680;
	Wed, 21 Jul 2004 18:37:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnPjE-0007us-A7; Wed, 21 Jul 2004 18:38:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnOKK-000719-NI; Wed, 21 Jul 2004 17:08:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnJWS-0005F9-2c
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 12:00:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29409
	for <ietf@ietf.org>; Wed, 21 Jul 2004 12:00:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnJWp-0004xI-Lq
	for ietf@ietf.org; Wed, 21 Jul 2004 12:01:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnJJz-0001Ar-A8
	for ietf@ietf.org; Wed, 21 Jul 2004 11:47:55 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
From: iesg-bounces@ietf.org
To: ietf@ietf.org
Message-ID: <mailman.316.1090424874.21047.iesg@ietf.org>
Date: Wed, 21 Jul 2004 11:47:54 -0400
Precedence: bulk
X-BeenThere: iesg@ietf.org
X-Mailman-Version: 2.1.5
X-List-Administrivia: yes
X-Spam-Score: 0.3 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 21 Jul 2004 17:08:35 -0400
Subject: Your message to iesg awaits moderator approval
X-BeenThere: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

Your mail to 'iesg' with the subject

    Re:

Is being held until the list moderator can review it for approval.

The reason it is being held:

    Post by non-member to a members-only list

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.  If you would like to cancel
this posting, please visit the following URL:

    https://www1.ietf.org/mailman/confirm/iesg/e48917ac8b10e0dea133e447e1c5bcbdd41ba8d0


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 21 19:51:58 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04556;
	Wed, 21 Jul 2004 19:51:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnQst-00040x-5e; Wed, 21 Jul 2004 19:52:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnOwc-0003nT-9h; Wed, 21 Jul 2004 17:48:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnN80-00028M-Jv
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 15:51:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18216
	for <ietf@ietf.org>; Wed, 21 Jul 2004 15:51:46 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnN8P-0007xq-5c
	for ietf@ietf.org; Wed, 21 Jul 2004 15:52:14 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 0A828621D0; Wed, 21 Jul 2004 21:51:16 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 28819-09; Wed, 21 Jul 2004 21:51:14 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id C8AE461AD5; Wed, 21 Jul 2004 21:51:13 +0200 (CEST)
Date: Wed, 21 Jul 2004 21:51:12 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Iljitsch van Beijnum <iljitsch@muada.com>, Aaron Falk <falk@ISI.EDU>
Message-ID: <D56BFBF597F94C89784423A4@[10.0.0.2]>
In-Reply-To: <19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Henrik Levkowetz <henrik@levkowetz.com>,
        Mark Allman <mallman@icir.org>
Subject: Re: survey on Friday IETF sessions
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit



--On 21. juli 2004 21:13 +0200 Iljitsch van Beijnum <iljitsch@muada.com> 
wrote:

> On 21-jul-04, at 6:20, Aaron Falk wrote:
>
>> In the interest of creating a more informed discussion,
>> we've put together a short questionnaire to gather some data on
>> attending meetings from IETF participants.
>
> Ok, that's great of course, but I have two different suggestions:
>
> 1. Get a better feel for which wgs can overlap without problems and which
> can't. (Hint: two wgs with "6" in their name probably shouldn't
> overlap...)
>
> 2. Move away from the session/break/session model. So rather than let the
> rooms be empty for 1.5 hours during the lunch and dinner breaks, schedule
> sessions more or less continuously. People who want to eat are no worse
> off, as they still get to attend one session and eat during another,
> while those who can't stand overlap now have a better chance of being
> able to attend everything they want to.

that's OK with me - I have meetings in all the breaks, so I have to take my 
breaks when there are scheduled meetings :-)

seriously - I think this is a seriously bad idea, because it lessens the 
ability of people to schedule informal time together.

New survey question: How many lunches and dinners did you have at the last 
IETF that were NOT meetings....?



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 21 20:28:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09434;
	Wed, 21 Jul 2004 20:28:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnRRv-0005NK-L1; Wed, 21 Jul 2004 20:28:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnPiO-00035Y-BU; Wed, 21 Jul 2004 18:37:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnOHg-00063J-PL
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 17:05:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01556
	for <ietf@ietf.org>; Wed, 21 Jul 2004 17:05:50 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnOI6-0003Y6-Us
	for ietf@ietf.org; Wed, 21 Jul 2004 17:06:19 -0400
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i6LL71i9065497;
	Wed, 21 Jul 2004 23:07:01 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <D56BFBF597F94C89784423A4@[10.0.0.2]>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <BC717493-DB59-11D8-A54A-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 21 Jul 2004 23:05:46 +0200
To: Harald Tveit Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
Cc: Aaron Falk <falk@ISI.EDU>, Mark Allman <mallman@icir.org>,
        Henrik Levkowetz <henrik@levkowetz.com>, ietf@ietf.org
Subject: Re: survey on Friday IETF sessions
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit

On 21-jul-04, at 21:51, Harald Tveit Alvestrand wrote:

>> 2. Move away from the session/break/session model. So rather than let 
>> the
>> rooms be empty for 1.5 hours during the lunch and dinner breaks, 
>> schedule
>> sessions more or less continuously. People who want to eat are no 
>> worse
>> off, as they still get to attend one session and eat during another,
>> while those who can't stand overlap now have a better chance of being
>> able to attend everything they want to.

> seriously - I think this is a seriously bad idea, because it lessens 
> the ability of people to schedule informal time together.

The first thing we should recognize is that between the two of us, we 
probably represent the two ends of the spectrum in IETF meeting 
attendee type: you being the chair and all, and me being a fairly 
casual IETF goer who participates mainly in one wg.

That being said, the informal scheduling thing isn't my experience. 
I've had a few of those during the breaks, but more often than not 
there isn't enough time or previous commitments so it's easier to find 
some mutually dead space in the schedule. This is usually doable for a 
three - four person group.

As the number of concurrent sessions becomes smaller, the opportunities 
for people with the same interests to find some "dead" time in the 
schedule increase. Only people who want to participate in pretty much 
everything won't benefit, but they have many problems now anyway.

But first and foremost we need to do SMARTER scheduling: even though 
I'm only really interested in the IPv6 stuff, idr, rpsec and grow, I've 
had overlapping sessions in all three meetings I attended. I would make 
a survey for that if I had the software...

Speaking of surveys: the results of Aaron's suggests that having 
session on sunday is probably a better idea than having them on 
friday...


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 21 20:35:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11243;
	Wed, 21 Jul 2004 20:35:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnRZ6-0005tX-AM; Wed, 21 Jul 2004 20:36:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnQqg-0003eF-3l; Wed, 21 Jul 2004 19:50:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnOwa-0003nG-4N
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 17:48:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09097
	for <ietf@ietf.org>; Wed, 21 Jul 2004 17:48:05 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnOx0-0005ph-NS
	for ietf@ietf.org; Wed, 21 Jul 2004 17:48:35 -0400
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i6LLnGi9066297;
	Wed, 21 Jul 2004 23:49:18 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <6387.1090438557@marajade.sandelman.ottawa.on.ca>
References: <Pine.LNX.4.44.0407212125001.16177-100000@netcore.fi>
	<1a4701c46f55$1fbbc840$8700000a@consulintel.es>
	<6387.1090438557@marajade.sandelman.ottawa.on.ca>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A3613606-DB5F-11D8-A54A-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 21 Jul 2004 23:48:01 +0200
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: IETF60: time needed for check-in at San Diego? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit

On 21-jul-04, at 21:35, Michael Richardson wrote:

>     JORDI> What is clear is that the US government should consider this
>     JORDI> type of events and provide facilities. Otherwise, the IETF,
>     JORDI> IEEE and other organizations, should consider very seriously
>     JORDI> skipping event in US.

>   What he said.

What is Canada like in this regard? Seems to me this would be a perfect 
compromise for the North American meetings: reasonable distance for the 
US attendees, reasonable treatment of foreign nationals for everyone 
else (AFAIK).

Personally, I can live without being fingerprinted like a common 
criminal, which will start for EU citizens entering the US this fall. 
(Which obviously means even longer lines at Immigration...)


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 21 23:04:48 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27103;
	Wed, 21 Jul 2004 23:04:48 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnTtZ-0001QH-0R; Wed, 21 Jul 2004 23:05:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnTnx-0004Su-Eg; Wed, 21 Jul 2004 22:59:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnTlj-0003Ir-6Y
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 22:57:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26611
	for <ietf@ietf.org>; Wed, 21 Jul 2004 22:57:12 -0400 (EDT)
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnTm2-0001KZ-Bp
	for ietf@ietf.org; Wed, 21 Jul 2004 22:57:44 -0400
Received: from portal (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id 7526217921; Wed, 21 Jul 2004 22:56:58 -0400 (EDT)
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: Pekka Savola <pekkas@netcore.fi>
In-Reply-To: Message from Pekka Savola <pekkas@netcore.fi> of "Wed,
	21 Jul 2004 21:28:17 +0300."
	<Pine.LNX.4.44.0407212125001.16177-100000@netcore.fi> 
Date: Wed, 21 Jul 2004 22:56:58 -0400
Message-Id: <20040722025658.7526217921@portal.hamachi.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ietf@ietf.org
Subject: Re: IETF60: time needed for check-in at San Diego? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sommerfeld@orchard.arlington.ma.us
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

I was last in San Diego in late January of this year.  For my
(domestic US) return flight, I arrived at the terminal about an hour
and a half before my (domestic) flight home on a 9:50am Friday morning
flight.

I think there were about a dozen people ahead of me in line for
security in terminal 2 and I got through it a minute or two.

A snapshot of http://www.san.org/airport/flights/flight_info.asp this
friday might be useful -- it may give you a sense for how many other
flights will be departing from the same wing of the terminal at around
the same time as your flight (see the terminal maps -- there are two
main terminals; each terminal has two wings, and IIRC there's a
security checkpoint and corresponding queue per wing).

					- Bill










_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Wed Jul 21 23:46:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29687;
	Wed, 21 Jul 2004 23:46:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnUY6-0001x1-AZ; Wed, 21 Jul 2004 23:47:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnUVe-0004LM-1d; Wed, 21 Jul 2004 23:44:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnUUW-0003XX-Cd
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 23:43:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29469
	for <ietf@ietf.org>; Wed, 21 Jul 2004 23:43:29 -0400 (EDT)
Received: from user-0c6s170.cable.mindspring.com ([24.110.4.224]
	helo=sleekfreak.ath.cx) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnUUv-0001uP-MC
	for ietf@ietf.org; Wed, 21 Jul 2004 23:44:02 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1BnPn3-0003T6-00; Wed, 21 Jul 2004 18:42:22 -0400
Date: Wed, 21 Jul 2004 18:41:53 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <A3613606-DB5F-11D8-A54A-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0407211839310.13331-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Michael Richardson <mcr@sandelman.ottawa.on.ca>, ietf@ietf.org,
        JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: IETF60: time needed for check-in at San Diego? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d

On Wed, 21 Jul 2004, Iljitsch van Beijnum wrote:

> On 21-jul-04, at 21:35, Michael Richardson wrote:
>
> >     JORDI> What is clear is that the US government should consider this
> >     JORDI> type of events and provide facilities. Otherwise, the IETF,
> >     JORDI> IEEE and other organizations, should consider very seriously
> >     JORDI> skipping event in US.
>
> >   What he said.
>
> What is Canada like in this regard? Seems to me this would be a perfect
> compromise for the North American meetings: reasonable distance for the
> US attendees, reasonable treatment of foreign nationals for everyone
> else (AFAIK).
>
> Personally, I can live without being fingerprinted like a common
> criminal, which will start for EU citizens entering the US this fall.
> (Which obviously means even longer lines at Immigration...)
>

How about a city in the US which agrees to not engage in such
behavior, and has an international airport, and several private airports?

>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 00:06:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00726;
	Thu, 22 Jul 2004 00:06:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnUrS-0002Nd-7H; Thu, 22 Jul 2004 00:07:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnUnz-0003cb-5O; Thu, 22 Jul 2004 00:03:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnUmj-0003GI-SX
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 00:02:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00543
	for <ietf@ietf.org>; Thu, 22 Jul 2004 00:02:18 -0400 (EDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnUnC-0002LT-Lh
	for ietf@ietf.org; Thu, 22 Jul 2004 00:02:52 -0400
Received: from esunmail ([129.147.156.34])
	by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id i6M40353012060
	for <ietf@ietf.org>; Wed, 21 Jul 2004 22:00:03 -0600 (MDT)
Received: from xpa-fe2 (esunmail [129.147.156.34]) by edgemail1.Central.Sun.COM
	(iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
	with ESMTP id <0I1800JVNJ7QWQ@edgemail1.Central.Sun.COM> for
	ietf@ietf.org; Wed, 21 Jul 2004 22:02:15 -0600 (MDT)
Received: from [192.168.1.24] ([216.113.203.45])
	by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8
	2003))
	with ESMTPSA id <0I18003S8J7NL2@mail.sun.net> for ietf@ietf.org; Wed,
	21 Jul 2004 22:02:11 -0600 (MDT)
Date: Wed, 21 Jul 2004 21:02:20 -0700
From: Tim Bray <tbray@textuality.com>
In-reply-to: <A3613606-DB5F-11D8-A54A-000A95CD987A@muada.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Message-id: <EE0BCFCC-DB93-11D8-AC8C-000A95A51C9E@textuality.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.618)
References: <Pine.LNX.4.44.0407212125001.16177-100000@netcore.fi>
	<1a4701c46f55$1fbbc840$8700000a@consulintel.es>
	<6387.1090438557@marajade.sandelman.ottawa.on.ca>
	<A3613606-DB5F-11D8-A54A-000A95CD987A@muada.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: Michael Richardson <mcr@sandelman.ottawa.on.ca>, ietf@ietf.org,
        JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: IETF60: time needed for check-in at San Diego?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1738000029=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2


--===============1738000029==
Content-type: multipart/signed; micalg=sha1; boundary=Apple-Mail-11-492591142; 
	protocol="application/pkcs7-signature"


--Apple-Mail-11-492591142
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

On Jul 21, 2004, at 2:48 PM, Iljitsch van Beijnum wrote:

> What is Canada like in this regard? Seems to me this would be a 
> perfect compromise for the North American meetings: reasonable 
> distance for the US attendees, reasonable treatment of foreign 
> nationals for everyone else (AFAIK).

I noted to Harald off-line that I think Canada would be an attractive 
choice for IETF meetings.  The tourism/conference biz is important to 
us, we're quite a bit cheaper than the U.S., and the border officials 
quite a bit softer-edged.  (To be fair to the U.S., we're also on fewer 
terrorist hit-lists).  I would think for something with the IETF's 
prestige, we might even be able to arrange a friendly nod from the 
Canadian feds, particularly if they could get a little marketing 
mileage out of the deal.

-Tim (writing from Vancouver, Canada)

--Apple-Mail-11-492591142
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGHDCCAtUw
ggI+oAMCAQICAwuKuTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDQwMTIyMjMzOTA2WhcNMDUwMTIxMjMzOTA2WjBGMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMSMwIQYJKoZIhvcNAQkBFhR0YnJheUB0ZXh0dWFsaXR5
LmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMYiIlrf7yTblabXBlwkonodVyp+
W7Oo8w71ErSW7mKramEBAkfkUnPmbRqcS2wqFaK34GbQMk/1vcOxo2AmfmFVec13SWKi0YzXC8xf
9SbjfQU1tXiC9LJB1HeOO46UVRqTNeayruz2pQBztvYF76G5sGmwKjoR/DhimwUM579MaJln38SK
UQ6Ya768DwyaDNY7yDWYh1gUxizx71QkzyRCPQdmq6g1ebrVYyoBE33BXQRNGZm2zrlI5JBQ4oax
E0Cz3BjR8iZFzK/AhFGDllZYuojf7iZuaNhWr3aWAvHNyLHVMaxXNFb/CUri5c7StFVEgXUVvlgP
eSHIPg9gqaECAwEAAaMxMC8wHwYDVR0RBBgwFoEUdGJyYXlAdGV4dHVhbGl0eS5jb20wDAYDVR0T
AQH/BAIwADANBgkqhkiG9w0BAQQFAAOBgQBQAlJ/qQJmtQN966ahSWiovhjWj5Qwk6BnPP+Fjfbo
9guSIWWBw2DEXh8nPT4WJchZSVz4SwDtZ0SZ2PWWToRo/Dmpv+ehzNNhR/y2CdU/zNo+kSShBhc6
HNtp6A0+Yh6Vw0Y+qHa0EKppOJM2D5WTExycYjHU8Xs+dLktAmKqlzCCAz8wggKooAMCAQICAQ0w
DQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQ
BgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0Nl
cnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAe
Fw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU
aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl
ZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688
Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJg
t/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6
Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIB
BjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEF
BQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFi
w9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU13
41YheILcIRk13iSx0x1G/11fZU8xggLnMIIC4wIBATBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK
ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQQIDC4q5MAkGBSsOAwIaBQCgggFTMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA0MDcyMjA0MDIyMVowIwYJKoZIhvcNAQkEMRYEFDyD
9XpZO4sL46mk/u7iio78JKIqMHgGCSsGAQQBgjcQBDFrMGkwYjELMAkGA1UEBhMCWkExJTAjBgNV
BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h
bCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLirkwegYLKoZIhvcNAQkQAgsxa6BpMGIxCzAJBgNVBAYT
AlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3
dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIDC4q5MA0GCSqGSIb3DQEBAQUABIIBAH4q
Fx/FxxgFSIRQ2YeTmYD3QglwxkwVVE6w/jaAyTnjjoklwzic47HasYu5TUYsJbgGG7XmppdJ1O7Q
3nIZAJxgu1wIXPAgXx/kW/kyiCfN+uzSB3R5zw1vNvoVUhJ0q3XEzId7ZMeQD4wcuFI8lrL2mTL6
rp89Ssgw8wTxHwMw4JYJpVKRKtGBeIp/zw8w4vtlfj4l88oH9rcr6erEW1BA1p1zt1tuTG/8pNNo
s0+g9WVV7mOND9V03rOeOj9SKpsd8G0Vc9NLCMwkV7bHRQYLYvAT+B3Ga2ek60Bus1c67mlx+M/O
AbXr9jt+6GcJ8fKnheBxtBbvmXEoAz7yIKQAAAAAAAA=

--Apple-Mail-11-492591142--



--===============1738000029==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1738000029==--




From ietf-bounces@ietf.org  Thu Jul 22 07:22:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10506;
	Thu, 22 Jul 2004 07:22:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnbfC-0007dB-MX; Thu, 22 Jul 2004 07:23:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnbbv-0002Sh-Lq; Thu, 22 Jul 2004 07:19:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnRGU-0005f9-L2
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 20:16:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08367
	for <ietf@ietf.org>; Wed, 21 Jul 2004 20:16:48 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnRGv-000577-It
	for ietf@ietf.org; Wed, 21 Jul 2004 20:17:18 -0400
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-5.cisco.com with ESMTP; 21 Jul 2004 17:16:51 -0700
X-BrightmailFiltered: true
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i6M0GGmI010372;
	Wed, 21 Jul 2004 17:16:16 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-219.cisco.com
	[10.32.244.219]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with SMTP id AVN67607; Wed, 21 Jul 2004 17:15:04 -0700 (PDT)
Message-Id: <6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Wed, 21 Jul 2004 17:07:25 -0700
To: Harald Tveit Alvestrand <harald@alvestrand.no>
From: Fred Baker <fred@cisco.com>
In-Reply-To: <D56BFBF597F94C89784423A4@[10.0.0.2]>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
X-Mailman-Approved-At: Thu, 22 Jul 2004 07:19:38 -0400
Cc: ietf@ietf.org
Subject: Re: survey on Friday IETF sessions
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2

At 09:51 PM 07/21/04 +0200, Harald Tveit Alvestrand wrote:
>New survey question: How many lunches and dinners did you have at the last 
>IETF that were NOT meetings....?

For me, it is rare to have meals that are not meetings of some sort. And I 
often have face-to-face editing sessions on IETF business or 
offline-but-topical discussions with customers and partners during slots 
that I don't have scheduled meetings in. 


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 07:26:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10784;
	Thu, 22 Jul 2004 07:26:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnbjM-0007hD-P4; Thu, 22 Jul 2004 07:27:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnbbw-0002So-Jq; Thu, 22 Jul 2004 07:19:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnRPQ-0005db-22
	for ietf@megatron.ietf.org; Wed, 21 Jul 2004 20:26:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09026
	for <ietf@ietf.org>; Wed, 21 Jul 2004 20:26:02 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnRPr-0005Fl-PW
	for ietf@ietf.org; Wed, 21 Jul 2004 20:26:32 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 21 Jul 2004 17:28:45 +0000
X-BrightmailFiltered: true
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i6M0PUNv012184;
	Wed, 21 Jul 2004 17:25:30 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-219.cisco.com
	[10.32.244.219]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with SMTP id AVN68249; Wed, 21 Jul 2004 17:24:18 -0700 (PDT)
Message-Id: <6.1.1.1.2.20040721170857.05203700@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Wed, 21 Jul 2004 17:23:38 -0700
To: Pekka Savola <pekkas@netcore.fi>
From: Fred Baker <fred@cisco.com>
In-Reply-To: <Pine.LNX.4.44.0407212125001.16177-100000@netcore.fi>
References: <Pine.LNX.4.44.0407212125001.16177-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id UAA09026
X-Mailman-Approved-At: Thu, 22 Jul 2004 07:19:38 -0400
Cc: ietf@ietf.org
Subject: Re: IETF60: time needed for check-in at San Diego?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: quoted-printable

At 09:28 PM 07/21/04 +0300, Pekka Savola wrote:
>Any experiences?  Is 1.5 or 2 hours (for example) enough at SD?

Any time *I* have been through either CLD or SAN, 90 minutes has been qui=
te=20
sufficient, and 60 minutes is usually enough for domestic travellers. If =
I=20
were checking in at LAX for an international departure, however, there is=
=20
no way I would arrive a minute less than two hours in advance.

Note that if you are a frequent flier on United or American and are not=20
checking baggage, you can check in on-line up to 24 hours prior to actual=
ly=20
boarding. You have to be a mileage club member and have access to a print=
er=20
(found in the terminal room, or you can FAX it to yourself via the hotel =
if=20
you have FAX software on your laptop) to print the boarding pass. With=20
that, the only line is the TSA line.

The following are from United.

http://www.united.com/page/article/0,6722,50446,00.html
>We know that leaving on time is important to you.
>
>To facilitate an on-time departure, we recommend that you allow ample ti=
me=20
>for check-in, especially if you are checking baggage.
>
>For travel within the United States, we recommend that you arrive at the=
=20
>airport:
>  - 60 minutes before your flight if you are not checking any bags
>  - 90 minutes before your flight if you are checking baggage
>For international departures, we recommend that you arrive at the airpor=
t:
>     2 hours before your flight
>
>In a growing number of U.S. airports, the Transportation Security=20
>Administration (TSA) requires that all customers check-in to receive a=20
>boarding pass before entering the security check-point. The TSA website=20
>has a list of airports which require customers to obtain their boarding =
pass.
>
>Please note that reservations are subject to cancellation if you are not=
=20
>checked in and available for boarding at the gate:
>  - At least 20 minutes prior to departure between U.S. cities (except=20
> Hawaii =96 30 minutes), to/from Canada, Mexico and the Caribbean.
>  - At least 30 minutes prior to departure for all other international c=
ities.
>
>At 20 minutes before your flight, we'll begin awarding upgrades and star=
t=20
>accommodating customers who are waiting for seat assignments.
>
>At 10 minutes before your flight you should be onboard and ready for an=20
>on-time departure.
>
>For additional information about your airport, including security line=20
>waits, peak times and days of travel and other important information, se=
e=20
>Airport check-in information.
>
>When traveling around holidays or other peak travel times, we recommend=20
>you allow additional time.
>
>There are certain circumstances that will contribute to delays (i.e.=20
>weather, air traffic, mechanical problems); however, United is committed=
=20
>to doing everything possible to ensure on-time departures on all flights.


https://www.ua2go.com/ci/Login.jsp?return_to=3Deasy_checkin
>EasyCheck-in Online
>
>Save time and avoid check-in lines with EasyCheck-in Online. Check in an=
d=20
>print your boarding pass from home or the office, then proceed directly =
to=20
>security at the airport.
>
>EasyCheck-in Online is available 1 to 24 hours prior to your departure o=
n=20
>United and United Express flights within the U.S., San Juan, Puerto Rico=
,=20
>St. Thomas and the Virgin Islands.
>
>EasyCheck-in Online is as easy 1-2-3:
>   Select the itinerary you would like to check in
>   Select the passengers you would like to check-in
>   Review your flight information and Print
>
>Print your own boarding pass
>
>By printing your boarding pass through united.com, you can proceed=20
>directly to security. If you have bags to check, you can use curb side=20
>check-in and still avoid lines at the airport.
>
>In order to use EasyCheck-in Online, you must:
>Be a Mileage Plus Member
>Check in within 24 hours prior to your scheduled departure
>Use a computer that is connected to a working printer


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 08:20:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14275;
	Thu, 22 Jul 2004 08:20:43 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BncZa-0000Fy-1H; Thu, 22 Jul 2004 08:21:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BncS2-0004Lh-CM; Thu, 22 Jul 2004 08:13:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BncLm-0001lY-RM
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 08:07:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13387
	for <ietf@ietf.org>; Thu, 22 Jul 2004 08:07:01 -0400 (EDT)
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BncMJ-0008VR-V1
	for ietf@ietf.org; Thu, 22 Jul 2004 08:07:37 -0400
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id
	i6MC6xnE021007
	for <ietf@ietf.org>; Thu, 22 Jul 2004 13:06:59 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id NAA26465
	for <ietf@ietf.org>; Thu, 22 Jul 2004 13:06:58 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i6MC6wP32629
	for ietf@ietf.org; Thu, 22 Jul 2004 13:06:58 +0100
Date: Thu, 22 Jul 2004 13:06:58 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Message-ID: <20040722120658.GR26441@login.ecs.soton.ac.uk>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
	<6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more
	information
X-ECS-MailScanner: Found to be clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: Re: survey on Friday IETF sessions
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

On Wed, Jul 21, 2004 at 05:07:25PM -0700, Fred Baker wrote:
> At 09:51 PM 07/21/04 +0200, Harald Tveit Alvestrand wrote:
> >New survey question: How many lunches and dinners did you have at the last 
> >IETF that were NOT meetings....?
> 
> For me, it is rare to have meals that are not meetings of some sort. And I 
> often have face-to-face editing sessions on IETF business or 
> offline-but-topical discussions with customers and partners during slots 
> that I don't have scheduled meetings in. 

I think it is useful to have lunch gaps to have fringe meetings, and many
people may wish to retain the ability to arrange gatherings outside the
main program.

I've also been to Internet 2 meetings where they have WG or special
interest meetings through lunch, and you take lunch into the meeting.
That seems to work fine.   These are meetings on the agenda, rather than
the ad-hoc IETF groupings that might (do) happen.

I can remember an IETF over a year ago where Iljitsch and Michel organised
a whole week of unofficial multi6 meetings through the event.   So if
you pick your slots, and the people are determined, anything is possible :)
(and that IETF really helped get multi6 back on track)

Tim

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 09:12:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17705;
	Thu, 22 Jul 2004 09:12:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BndNO-00013Q-1F; Thu, 22 Jul 2004 09:12:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BndEy-0004MT-JK; Thu, 22 Jul 2004 09:04:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bnd7I-00027e-11
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 08:56:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16258
	for <ietf@ietf.org>; Thu, 22 Jul 2004 08:56:06 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23] helo=ftmailgfi.HQ.Flarion.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bnd7q-0000gZ-Ht
	for ietf@ietf.org; Thu, 22 Jul 2004 08:56:42 -0400
Received: from ftmail2000.HQ.Flarion.com ([10.10.1.120]) by
	ftmailgfi.HQ.Flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Thu, 22 Jul 2004 08:55:27 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 22 Jul 2004 08:55:27 -0400
Message-ID: <F4410B91C6CC314F9582B1A8E91DC928BEECCB@ftmail2000>
Thread-Topic: IETF60: time needed for check-in at San Diego?
Thread-Index: AcRv3xtnVy2JeUorRrqGNdZ8DrLtygACXL/Q
From: "Soliman Hesham" <H.Soliman@flarion.com>
To: "Fred Baker" <fred@cisco.com>, "Pekka Savola" <pekkas@netcore.fi>
X-OriginalArrivalTime: 22 Jul 2004 12:55:27.0131 (UTC)
	FILETIME=[292206B0:01C46FEB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: RE: IETF60: time needed for check-in at San Diego?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Content-Transfer-Encoding: quoted-printable

The problem is not in the airline check in queue, that usually=20
takes me 10 mins. It's the nice one after that to get through=20
the security machines.

For those tansiting in LAX (international), my advice is: don't!
Try to get a direct flight or through San Francisco. A typical time in
my last two trips to get out of the international terminal (LAX) and get =

into the boarding area in domestic is around 3.5 hours give or take...
Of course the official transit time (seen by your travel agent)
is about 2 hrs.



 > -----Original Message-----
 > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]On=20
 > Behalf Of
 > Fred Baker
 > Sent: Wednesday, July 21, 2004 8:24 PM
 > To: Pekka Savola
 > Cc: ietf@ietf.org
 > Subject: Re: IETF60: time needed for check-in at San Diego?
 >=20
 >=20
 > At 09:28 PM 07/21/04 +0300, Pekka Savola wrote:
 > >Any experiences?  Is 1.5 or 2 hours (for example) enough at SD?
 >=20
 > Any time *I* have been through either CLD or SAN, 90 minutes=20
 > has been quite=20
 > sufficient, and 60 minutes is usually enough for domestic=20
 > travellers. If I=20
 > were checking in at LAX for an international departure,=20
 > however, there is=20
 > no way I would arrive a minute less than two hours in advance.
 >=20
 > Note that if you are a frequent flier on United or American=20
 > and are not=20
 > checking baggage, you can check in on-line up to 24 hours=20
 > prior to actually=20
 > boarding. You have to be a mileage club member and have=20
 > access to a printer=20
 > (found in the terminal room, or you can FAX it to yourself=20
 > via the hotel if=20
 > you have FAX software on your laptop) to print the boarding=20
 > pass. With=20
 > that, the only line is the TSA line.
 >=20
 > The following are from United.
 >=20
 > http://www.united.com/page/article/0,6722,50446,00.html
 > >We know that leaving on time is important to you.
 > >
 > >To facilitate an on-time departure, we recommend that you=20
 > allow ample time=20
 > >for check-in, especially if you are checking baggage.
 > >
 > >For travel within the United States, we recommend that you=20
 > arrive at the=20
 > >airport:
 > >  - 60 minutes before your flight if you are not checking any bags
 > >  - 90 minutes before your flight if you are checking baggage
 > >For international departures, we recommend that you arrive=20
 > at the airport:
 > >     2 hours before your flight
 > >
 > >In a growing number of U.S. airports, the Transportation Security=20
 > >Administration (TSA) requires that all customers check-in=20
 > to receive a=20
 > >boarding pass before entering the security check-point. The=20
 > TSA website=20
 > >has a list of airports which require customers to obtain=20
 > their boarding pass.
 > >
 > >Please note that reservations are subject to cancellation=20
 > if you are not=20
 > >checked in and available for boarding at the gate:
 > >  - At least 20 minutes prior to departure between U.S.=20
 > cities (except=20
 > > Hawaii - 30 minutes), to/from Canada, Mexico and the Caribbean.
 > >  - At least 30 minutes prior to departure for all other=20
 > international cities.
 > >
 > >At 20 minutes before your flight, we'll begin awarding=20
 > upgrades and start=20
 > >accommodating customers who are waiting for seat assignments.
 > >
 > >At 10 minutes before your flight you should be onboard and=20
 > ready for an=20
 > >on-time departure.
 > >
 > >For additional information about your airport, including=20
 > security line=20
 > >waits, peak times and days of travel and other important=20
 > information, see=20
 > >Airport check-in information.
 > >
 > >When traveling around holidays or other peak travel times,=20
 > we recommend=20
 > >you allow additional time.
 > >
 > >There are certain circumstances that will contribute to=20
 > delays (i.e.=20
 > >weather, air traffic, mechanical problems); however, United=20
 > is committed=20
 > >to doing everything possible to ensure on-time departures=20
 > on all flights.
 >=20
 >=20
 > https://www.ua2go.com/ci/Login.jsp?return_to=3Deasy_checkin
 > >EasyCheck-in Online
 > >
 > >Save time and avoid check-in lines with EasyCheck-in=20
 > Online. Check in and=20
 > >print your boarding pass from home or the office, then=20
 > proceed directly to=20
 > >security at the airport.
 > >
 > >EasyCheck-in Online is available 1 to 24 hours prior to=20
 > your departure on=20
 > >United and United Express flights within the U.S., San=20
 > Juan, Puerto Rico,=20
 > >St. Thomas and the Virgin Islands.
 > >
 > >EasyCheck-in Online is as easy 1-2-3:
 > >   Select the itinerary you would like to check in
 > >   Select the passengers you would like to check-in
 > >   Review your flight information and Print
 > >
 > >Print your own boarding pass
 > >
 > >By printing your boarding pass through united.com, you can proceed=20
 > >directly to security. If you have bags to check, you can=20
 > use curb side=20
 > >check-in and still avoid lines at the airport.
 > >
 > >In order to use EasyCheck-in Online, you must:
 > >Be a Mileage Plus Member
 > >Check in within 24 hours prior to your scheduled departure
 > >Use a computer that is connected to a working printer
 >=20
 >=20
 > _______________________________________________
 > Ietf mailing list
 > Ietf@ietf.org
 > https://www1.ietf.org/mailman/listinfo/ietf
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 09:29:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19047;
	Thu, 22 Jul 2004 09:29:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BndeH-0001M3-RD; Thu, 22 Jul 2004 09:30:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BndWm-0003fx-Ch; Thu, 22 Jul 2004 09:22:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BndUN-0002aj-VT
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 09:20:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18244
	for <ietf@ietf.org>; Thu, 22 Jul 2004 09:19:57 -0400 (EDT)
Received: from cyphermail.sandelman.ottawa.on.ca ([205.150.200.161]
	helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BndUr-0001Bv-Jn
	for ietf@ietf.org; Thu, 22 Jul 2004 09:20:33 -0400
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca
	[205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i6MDJcX09197
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK); Thu, 22 Jul 2004 09:19:39 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i6MDJctA031210
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 22 Jul 2004 09:19:38 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i6MDJWhY031203; Thu, 22 Jul 2004 09:19:33 -0400
To: Tim Bray <tbray@textuality.com>
In-Reply-To: Message from Tim Bray <tbray@textuality.com> of "Wed,
	21 Jul 2004 21:02:20 PDT."
	<EE0BCFCC-DB93-11D8-AC8C-000A95A51C9E@textuality.com> 
References: <Pine.LNX.4.44.0407212125001.16177-100000@netcore.fi>
	<1a4701c46f55$1fbbc840$8700000a@consulintel.es>
	<6387.1090438557@marajade.sandelman.ottawa.on.ca>
	<A3613606-DB5F-11D8-A54A-000A95CD987A@muada.com>
	<EE0BCFCC-DB93-11D8-AC8C-000A95A51C9E@textuality.com> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 22 Jul 2004 09:19:32 -0400
Message-ID: <31202.1090502372@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org,
        JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: IETF60: time needed for check-in at San Diego? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

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


>>>>> "Tim" == Tim Bray <tbray@textuality.com> writes:
    Tim> even be able to arrange a friendly nod from the Canadian feds,

  The who?
  Fed:  "IETF? Internet stuff, yeah... isn't that a division of microsoft?
         no? right. Internet, not Internet Explorer. The thing that
	 Nortel invented." 

  Don't expect any help from the Canadian federal government. Too
clueless, sorry.  On the other hand, do not expect any hinderance
either.

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBQP++44qHRg3pndX9AQE4vgP+M4W6qCedvHpYw8hlJMQ9EHlJlRkQg92a
H3Bq3OE3A00l8Dk7mXKkWNJcQ93+SP8ByvFNeO2eBtPiALP1lmwvUdT522b03yT8
4lxnvUkkZb3jB65NUMEHmM5kxiDrV/zWVpPjr72Kqc+xtw40Cnm+p+3qdwlSJwu5
0LStIYKPL8M=
=oSV8
-----END PGP SIGNATURE-----

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 09:54:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20768;
	Thu, 22 Jul 2004 09:54:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bne23-0001kK-E0; Thu, 22 Jul 2004 09:54:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bndpw-0001we-M3; Thu, 22 Jul 2004 09:42:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bndeo-0006C1-AB
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 09:30:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19170
	for <ietf@ietf.org>; Thu, 22 Jul 2004 09:30:44 -0400 (EDT)
Received: from cyphermail.sandelman.ottawa.on.ca ([205.150.200.161]
	helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BndfN-0001Mm-A2
	for ietf@ietf.org; Thu, 22 Jul 2004 09:31:21 -0400
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca
	[205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i6MDUVX09268
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK); Thu, 22 Jul 2004 09:30:32 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i6MDUVtA031499
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 22 Jul 2004 09:30:31 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i6MDUVNN031496; Thu, 22 Jul 2004 09:30:31 -0400
To: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: Message from Tim Chown <tjc@ecs.soton.ac.uk> of "Thu,
	22 Jul 2004 13:06:58 BST."
	<20040722120658.GR26441@login.ecs.soton.ac.uk> 
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
	<6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
	<20040722120658.GR26441@login.ecs.soton.ac.uk> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 22 Jul 2004 09:30:31 -0400
Message-ID: <31495.1090503031@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: ietf@ietf.org
Subject: Re: survey on Friday IETF sessions 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a

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


>>>>> "Tim" == Tim Chown <tjc@ecs.soton.ac.uk> writes:
    >> For me, it is rare to have meals that are not meetings of some
    >> sort. And I often have face-to-face editing sessions on IETF
    >> business or offline-but-topical discussions with customers and
    >> partners during slots that I don't have scheduled meetings in.

    Tim> I think it is useful to have lunch gaps to have fringe
    Tim> meetings, and many people may wish to retain the ability to
    Tim> arrange gatherings outside the main program.

  If asked, I would give up an hour of the dinner break and retain the
lunch break. The why is simple: the 2 hours we have to dinner is both
too long for a quick bite, and too short for a relaxed meal.

    Tim> I've also been to Internet 2 meetings where they have WG or
    Tim> special interest meetings through lunch, and you take lunch
    Tim> into the meeting.  That seems to work fine.  These are meetings

  Hmm. That could work, but aren't IETF meetings a bit bigger than
Internet2? I'm thinking about the logistics of 1200 people trying to get
a bag lunch all at the same time.

    Tim> I can remember an IETF over a year ago where Iljitsch and
    Tim> Michel organised a whole week of unofficial multi6 meetings
    Tim> through the event.  So if you pick your slots, and the people

  And... some of us couldn't make any of those either.
  having been on nomcom one year, I can tell you --- there are people
who make use of every single gap in the day.
  I think it comes back to:
    a) some groups probably shouldn't meet as often
    b) some groups perhaps shouldn't exist at all
    c) some groups need 6-10 hours of continuous face-time in which they
       can actually get things done. We have pushed such things to
       interim meetings, sometimes with success, sometimes without.
       The problem is that these groups get 4 hours at IETF, easily
       fill that, and still feel that they didn't get everything done.

  We can tweak the schedule a bit and get some time back for some
people. At least, perhaps even things out. Someone needs to run an
online scheduling experiment, and see what we can actually do with some
sophisticated scheduling software. (Most of it is very hard to use
right, based upon my experience with our local transit company.) 

  I'm not in the loop on the problem-statement stuff, having missed two
IETFs, and been busy. But that's where some of the answers need to come
from.

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [



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

iQCVAwUBQP/BdoqHRg3pndX9AQFS0AP+Nkc1sris9ZlKxV24KyMHG0f19+5S2SkP
H52qMQ27OnK0KWuEecUDGLER2Ix05XaF7PvAZAhNqX5qqaNI2GuxdXE3Qgd5H7nL
tXvA6vMDNbgo6Qx5jkNEdJpRFZUxfjQ1TYBrYuj8tZdJOjmE8LXqMVzRHWV4E/kA
aD9LeIeMqQY=
=kARp
-----END PGP SIGNATURE-----

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 10:58:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27159;
	Thu, 22 Jul 2004 10:58:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bnf2R-00035d-89; Thu, 22 Jul 2004 10:59:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnes5-0000Rs-UU; Thu, 22 Jul 2004 10:48:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BneoO-0007JP-9R
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 10:44:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26240
	for <ietf@ietf.org>; Thu, 22 Jul 2004 10:44:42 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bneov-0002uG-6R
	for ietf@ietf.org; Thu, 22 Jul 2004 10:45:20 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.1.Alpha0/8.13.1.Alpha0) with ESMTP id
	i6MEidNR021129; Thu, 22 Jul 2004 10:44:39 -0400
Message-Id: <200407221444.i6MEidNR021129@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4+dev
To: shogunx <shogunx@sleekfreak.ath.cx>
In-Reply-To: Your message of "Wed, 21 Jul 2004 18:41:53 EDT."
	<Pine.LNX.4.44.0407211839310.13331-100000@sleekfreak.ath.cx> 
References: <Pine.LNX.4.44.0407211839310.13331-100000@sleekfreak.ath.cx>
Mime-Version: 1.0
Date: Thu, 22 Jul 2004 10:44:39 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ietf@ietf.org
Subject: Re: IETF60: time needed for check-in at San Diego? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1021384408=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081

--===============1021384408==
Content-Type: multipart/signed; boundary="==_Exmh_-893411256P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Wed, 21 Jul 2004 18:41:53 EDT, shogunx said:

> How about a city in the US which agrees to not engage in such
> behavior, and has an international airport, and several private airports?

The cities aren't given a choice in the matter - some bright bulb in the
federal bureaucracy decided that fingerprinting airline travelers made sense,
totally overlooking the fact that the terrorists aren't so stupid they can't
catch a flight to Montreal, Ottowa, or Vancouver and rent a car..... 

Or just *walk* across the border, for that matter...

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

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

iD8DBQFA/9LXcC3lWbTT17ARAmkkAKC9ZIU2CoO8W/pBfZqa7hi+lVdlzgCg8och
RB3fRuLAVOZJBVEMgChu7So=
=ZI43
-----END PGP SIGNATURE-----

--==_Exmh_-893411256P--


--===============1021384408==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1021384408==--



From ietf-bounces@ietf.org  Thu Jul 22 11:35:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29714;
	Thu, 22 Jul 2004 11:35:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnfcJ-0003hn-Lp; Thu, 22 Jul 2004 11:36:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnfUg-0005Ob-JV; Thu, 22 Jul 2004 11:28:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnfPh-0003s4-7q
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 11:23:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28886
	for <ietf@ietf.org>; Thu, 22 Jul 2004 11:23:14 -0400 (EDT)
Received: from user-0c6s170.cable.mindspring.com ([24.110.4.224]
	helo=sleekfreak.ath.cx) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnfQE-0003V2-EH
	for ietf@ietf.org; Thu, 22 Jul 2004 11:23:53 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1Bnaj3-0003t2-00; Thu, 22 Jul 2004 06:22:57 -0400
Date: Thu, 22 Jul 2004 06:22:54 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Valdis.Kletnieks@vt.edu
In-Reply-To: <200407221444.i6MEidNR021129@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0407220619290.14765-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ietf@ietf.org
Subject: Re: IETF60: time needed for check-in at San Diego? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d

On Thu, 22 Jul 2004 Valdis.Kletnieks@vt.edu wrote:

> On Wed, 21 Jul 2004 18:41:53 EDT, shogunx said:
>
> > How about a city in the US which agrees to not engage in such
> > behavior, and has an international airport, and several private airports?
>
> The cities aren't given a choice in the matter - some bright bulb in the
> federal bureaucracy decided that fingerprinting airline travelers made sense,
> totally overlooking the fact that the terrorists aren't so stupid they can't
> catch a flight to Montreal, Ottowa, or Vancouver and rent a car.....

And if we bring suit against this obvious invasion of privacy, citing
detriment to our local tourism based economy, due to a lower rate of
international visitors, combined with a media campaign exposing the corruption
that brought all of this about in the first place?  Oh, wait, the former
is already taking place.
>
> Or just *walk* across the border, for that matter...
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 11:55:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01129;
	Thu, 22 Jul 2004 11:55:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bnfva-00041E-0D; Thu, 22 Jul 2004 11:56:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnfpv-0005p1-8f; Thu, 22 Jul 2004 11:50:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bnffs-0001pi-4P
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 11:40:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00099
	for <ietf@ietf.org>; Thu, 22 Jul 2004 11:39:57 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnfgR-0003ob-BZ
	for ietf@ietf.org; Thu, 22 Jul 2004 11:40:36 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.1.Alpha0/8.13.1.Alpha0) with ESMTP id
	i6MFdvUL029328; Thu, 22 Jul 2004 11:39:57 -0400
Message-Id: <200407221539.i6MFdvUL029328@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4+dev
To: shogunx <shogunx@sleekfreak.ath.cx>
In-Reply-To: Your message of "Thu, 22 Jul 2004 06:22:54 EDT."
	<Pine.LNX.4.44.0407220619290.14765-100000@sleekfreak.ath.cx> 
References: <Pine.LNX.4.44.0407220619290.14765-100000@sleekfreak.ath.cx>
Mime-Version: 1.0
Date: Thu, 22 Jul 2004 11:39:57 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ietf@ietf.org
Subject: Re: IETF60: time needed for check-in at San Diego? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1337538524=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352

--===============1337538524==
Content-Type: multipart/signed; boundary="==_Exmh_-610840872P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Thu, 22 Jul 2004 06:22:54 EDT, shogunx said:

> And if we bring suit against this obvious invasion of privacy,

It's been tried.

http://freetotravel.org/

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

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

iD8DBQFA/9/NcC3lWbTT17ARAt+hAKDlOBESNtp+hjoMS+vGMPQw+TSSLgCgiBWr
anKoQEDRLu+Q8qhJRab4HOc=
=vjrw
-----END PGP SIGNATURE-----

--==_Exmh_-610840872P--


--===============1337538524==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--===============1337538524==--



From ietf-bounces@ietf.org  Thu Jul 22 12:23:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02794;
	Thu, 22 Jul 2004 12:23:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BngME-0004QC-0K; Thu, 22 Jul 2004 12:23:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bng2P-0002mY-L4; Thu, 22 Jul 2004 12:03:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnfuL-00075j-3d
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 11:54:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01096
	for <ietf@ietf.org>; Thu, 22 Jul 2004 11:54:54 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bnfuu-00040X-D2
	for ietf@ietf.org; Thu, 22 Jul 2004 11:55:33 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 22 Jul 2004 08:56:50 -0700
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i6MFskIV009536;
	Thu, 22 Jul 2004 08:54:46 -0700 (PDT)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id IAA27357;
	Thu, 22 Jul 2004 08:54:46 -0700 (PDT)
Date: Thu, 22 Jul 2004 08:54:46 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Soliman Hesham <H.Soliman@flarion.com>
In-Reply-To: <F4410B91C6CC314F9582B1A8E91DC928BEECCB@ftmail2000>
Message-ID: <Pine.HPX.4.58.0407220846500.16320@wells.cisco.com>
References: <F4410B91C6CC314F9582B1A8E91DC928BEECCB@ftmail2000>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: ietf@ietf.org, Fred Baker <fred@cisco.com>,
        Pekka Savola <pekkas@netcore.fi>
Subject: RE: IETF60: time needed for check-in at San Diego?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007

Yes, the transit security is indeed infuriating. Happens in London too and
can take a long time if you happen to arrive during a high "load average".
Basically, they all seem to be saying "we don't trust the security in the
country you just came from." Or perhaps: "We want to make sure you don't
use any of those weapons you bought on board from the duty free catalog on
your way here."

Arrgh!



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




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 12:23:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02812;
	Thu, 22 Jul 2004 12:23:08 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BngMG-0004QJ-0x; Thu, 22 Jul 2004 12:23:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bng2i-0002tB-HL; Thu, 22 Jul 2004 12:03:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnfwU-00086W-O2
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 11:57:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01297
	for <ietf@ietf.org>; Thu, 22 Jul 2004 11:57:08 -0400 (EDT)
Received: from user-0c6s170.cable.mindspring.com ([24.110.4.224]
	helo=sleekfreak.ath.cx) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bnfx4-00042v-2I
	for ietf@ietf.org; Thu, 22 Jul 2004 11:57:47 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1BnbFt-0003v2-00; Thu, 22 Jul 2004 06:56:53 -0400
Date: Thu, 22 Jul 2004 06:56:53 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Valdis.Kletnieks@vt.edu
In-Reply-To: <200407221539.i6MFdvUL029328@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0407220656050.14980-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ietf@ietf.org
Subject: Re: IETF60: time needed for check-in at San Diego? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

On Thu, 22 Jul 2004 Valdis.Kletnieks@vt.edu wrote:

> On Thu, 22 Jul 2004 06:22:54 EDT, shogunx said:
>
> > And if we bring suit against this obvious invasion of privacy,
>
> It's been tried.
>
> http://freetotravel.org/

What if we throw in a large protest and some civil disobedience
simultaneously?

>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 13:36:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08495;
	Thu, 22 Jul 2004 13:36:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnhV0-0005gi-Ba; Thu, 22 Jul 2004 13:36:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnhKh-0007LN-Pv; Thu, 22 Jul 2004 13:26:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnh8W-0002f2-F2; Thu, 22 Jul 2004 13:13:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06936;
	Thu, 22 Jul 2004 13:13:21 -0400 (EDT)
Received: from m018e36d0.tmodns.net ([208.54.142.1]
	helo=mailrelay.t-mobile.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bnh8q-0005NC-En; Thu, 22 Jul 2004 13:14:01 -0400
Received: from [192.168.2.2] (unknown [10.224.7.242])
	by mailrelay.t-mobile.com (Postfix) with ESMTP
	id 5D939189C4; Thu, 22 Jul 2004 09:57:17 -0700 (PDT)
Mime-Version: 1.0
X-Sender: margaret@mail.thingmagic.com
Message-Id: <p06020422bd25878ad86d@[192.168.2.2]>
Date: Thu, 22 Jul 2004 11:05:55 -0400
To: wgchairs@ietf.org, bofchairs@ietf.org, ietf@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Subject: General Training in San Diego
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64


Hi All,

We have our usual complement of training sessions scheduled for 
Sunday afternoon at the San Diego IETF meeting (see below for 
details).  These sessions include training for IETF Newcomer's, 
Introductory Training for New or Aspiring WG Chairs, Training for 
IETF Document Editors and a technical Security Tutorial.

All of these sessions are open to any IETF participant.  So, if you 
will be in San Diego on Sunday afternoon, I hope you will attend!

Thanks,
Margaret

---

Sunday, August 1, 2004
===================

1300-1400  Newcomer's Training -- Grande Ballroom A (Margaret Wasserman)

            An introduction to the IETF for new or recent IETF
            attendees.  Covers the IETF document processes, the
            structure of the IETF, and tips for new attendees to
            be successful in the IETF environment.

1300-1500  Editor's Training -- Marina 5  (Avri Doria)

            Training for current or aspiring IETF document
            editors.  Covers the roles and responsibilities
            of a document editor, and includes advice on
            producing a high-quality IETF specification.

1500-1700  Intro WG Chairs Training -- Location TBD  (Spencer Dawkins)

            Introductory training for new or aspiring WG
            chairs.  Covers the role and responsibilities of
            a WG chair, and includes advice on how to run a
            WG that is fair, open and productive.  This class
            is open to all IETF attendees.

1500-1700  Security Tutorial -- Grande Ballroom A  (Radia Perlman)

            All IETF attendees need to be aware of the security
            implications of our design choices.  This session
            offers a basic primer in protocol security, as well
            as advice on how to write the Security Considerations
            sections required for all IETF documents.

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 14:10:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10896;
	Thu, 22 Jul 2004 14:10:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bni2V-0006Aa-H3; Thu, 22 Jul 2004 14:11:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnhoA-0004zE-It; Thu, 22 Jul 2004 13:56:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bnhm9-00040E-JJ
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 13:54:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09790
	for <ietf@ietf.org>; Thu, 22 Jul 2004 13:54:36 -0400 (EDT)
Received: from wiproecmx2.wipro.com ([164.164.31.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bnhmg-0005wT-Aw
	for ietf@ietf.org; Thu, 22 Jul 2004 13:55:15 -0400
Received: from ec-vwall-wd (ec-vwall-wd.wipro.com [10.200.52.125])
	by wiproecmx2.wipro.com (8.12.9-20031013/8.12.9) with SMTP id
	i6MHrqRD009593
	for <ietf@ietf.org>; Thu, 22 Jul 2004 23:23:52 +0530 (IST)
Received: from blr-ec-bh1.wipro.com ([10.200.50.91]) by ec-vwall-wd with
	InterScan Messaging Security Suite; Thu, 22 Jul 2004 23:23:51 +0530
Received: from blr-ec-msg02.wipro.com ([10.200.51.99]) by blr-ec-bh1.wipro.com
	with Microsoft SMTPSVC(5.0.2195.6713); 
	Thu, 22 Jul 2004 23:23:51 +0530
Received: from wipro.com ([192.168.22.182]) by blr-ec-msg02.wipro.com with
	Microsoft SMTPSVC(5.0.2195.6713); Thu, 22 Jul 2004 23:23:51 +0530
Message-ID: <40FFFECD.FF21BDAC@wipro.com>
Date: Thu, 22 Jul 2004 23:22:13 +0530
From: Mahendran <mahendran.devaraj@wipro.com>
Organization: Wipro Technologies
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Content-Type: multipart/mixed; boundary="------------220B66CDD48E745A068936D9"
X-OriginalArrivalTime: 22 Jul 2004 17:53:51.0553 (UTC)
	FILETIME=[D9000310:01C47014]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: Activities of IETF in Asia Pacific
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d

This is a multi-part message in MIME format.
--------------220B66CDD48E745A068936D9
Content-Type: text/plain; charset=UTF-7
Content-Transfer-Encoding: base64

aGFpIGFsbCwNCkNhbiBhbnlvbmUgbGV0IG1lIGFib3V0IHRoZSBhY3Rpdml0aWVzIG9mIElF
VEYgaW4gdGhlIEFzaWEgUGFjaWZpYw0KR2l2ZSBtZSBpbiBkZXRhaWwgaWYgcG9zc2libGUu
DQoNClRoYW5rcw0KTWFoZQ0K
--------------220B66CDD48E745A068936D9
Content-Type: text/x-vcard; charset=UTF-7;
 name="mahendran.devaraj.vcf"
Content-Description: Card for Mahendran
Content-Disposition: attachment;
 filename="mahendran.devaraj.vcf"
Content-Transfer-Encoding: base64

YmVnaW46dmNhcmQgCm46O01haGVuZHJhbgp0ZWw7Y2VsbDowODAtMzczNDQ4NTFbUmVsaWFu
Y2VdCnRlbDt3b3JrOjI4NTIwNDA4LzUxMjIxMTExL0V4dG44NTMxNgp4LW1vemlsbGEtaHRt
bDpUUlVFCm9yZzpXaXBybyBUZWNobm9sb2dpZXM7VGVsZWNvbW11bmljYXRpb24gYW5kIElu
dGVybmV0d29ya2luZwp2ZXJzaW9uOjIuMQplbWFpbDtpbnRlcm5ldDptYWhlbmRyYW4uZGV2
YXJhakB3aXByby5jb20KdGl0bGU6UHJvamVjdCBFbmdpbmVlcgphZHI7cXVvdGVkLXByaW50
YWJsZTo7O0VDMywgVG93ZXIgOCxDIFdpbmcsIDV0aCBGbG9vciwgPTBEPTBBV2lwcm8gVGVj
aG5vbG9naWVzLD0wRD0wQTcyLCBLZW9uaWNzLCBFbGVjdHJvbmljIENpdHksPTBEPTBBO0Jh
bmdhbG9yZS01NjAyMjk7OzsKbm90ZTtxdW90ZWQtcHJpbnRhYmxlOj0wRD0wQQp4LW1vemls
bGEtY3B0OjsxNDY4OApmbjpNYWhlbmRyYW4KZW5kOnZjYXJkCg==
--------------220B66CDD48E745A068936D9
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--------------220B66CDD48E745A068936D9--




From ietf-bounces@ietf.org  Thu Jul 22 14:44:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14201;
	Thu, 22 Jul 2004 14:44:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BniZP-0006t9-DN; Thu, 22 Jul 2004 14:45:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BniP6-0000YM-DW; Thu, 22 Jul 2004 14:34:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BniFh-0005sF-Go
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 14:25:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12254
	for <ietf@ietf.org>; Thu, 22 Jul 2004 14:25:08 -0400 (EDT)
Received: from vapor.isi.edu ([128.9.64.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BniGE-0006Qg-63
	for ietf@ietf.org; Thu, 22 Jul 2004 14:25:47 -0400
Received: from [128.9.176.129] (ras29.isi.edu [128.9.176.129])
	by vapor.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i6MIO1B20959;
	Thu, 22 Jul 2004 11:24:02 -0700 (PDT)
In-Reply-To: <31495.1090503031@marajade.sandelman.ottawa.on.ca>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
	<6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
	<20040722120658.GR26441@login.ecs.soton.ac.uk>
	<31495.1090503031@marajade.sandelman.ottawa.on.ca>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
Content-Transfer-Encoding: 7bit
From: Aaron Falk <falk@ISI.EDU>
Date: Thu, 22 Jul 2004 10:55:51 -0700
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Mailer: Apple Mail (2.618)
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: falk@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: survey on Friday IETF sessions
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit


On Jul 22, 2004, at 6:30 AM, Michael Richardson wrote:

>   I think it comes back to:
>     a) some groups probably shouldn't meet as often
>     b) some groups perhaps shouldn't exist at all
>     c) some groups need 6-10 hours of continuous face-time in which 
> they
>        can actually get things done. We have pushed such things to
>        interim meetings, sometimes with success, sometimes without.
>        The problem is that these groups get 4 hours at IETF, easily
>        fill that, and still feel that they didn't get everything done.


Perhaps we should raise the bar on what it takes to get a slot at the 
IETF meeting.  For example, try to come up with some objective criteria 
for what deserves a 1hr slot, 2hrs, multiple, etc.  This  might even 
nudge groups into making some additional progress  ("you can't have 
your meeting if you don't hit a/some milestones").

BTW, regarding the survey: there's only been 80 responses so far.  My 
take is that people don't care about the issue enough to voice their 
opinion.

--aaron


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 14:52:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14979;
	Thu, 22 Jul 2004 14:52:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bnih7-00071V-Ac; Thu, 22 Jul 2004 14:53:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BniQc-0001Lk-BL; Thu, 22 Jul 2004 14:36:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BniNA-0008L5-8D
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 14:32:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13110
	for <ietf@ietf.org>; Thu, 22 Jul 2004 14:32:50 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BniNk-0006bH-NV
	for ietf@ietf.org; Thu, 22 Jul 2004 14:33:30 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 22 Jul 2004 11:34:44 -0700
X-BrightmailFiltered: true
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i6MIWFIX007911;
	Thu, 22 Jul 2004 11:32:17 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-219.cisco.com
	[10.32.244.219]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with SMTP id AVO29341; Thu, 22 Jul 2004 11:31:03 -0700 (PDT)
Message-Id: <6.1.1.1.2.20040722112151.064a9380@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Thu, 22 Jul 2004 11:22:58 -0700
To: "Soliman Hesham" <H.Soliman@flarion.com>
From: Fred Baker <fred@cisco.com>
In-Reply-To: <F4410B91C6CC314F9582B1A8E91DC928BEECCB@ftmail2000>
References: <F4410B91C6CC314F9582B1A8E91DC928BEECCB@ftmail2000>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: Pekka Savola <pekkas@netcore.fi>, ietf@ietf.org
Subject: RE: IETF60: time needed for check-in at San Diego?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199

At 08:55 AM 07/22/04 -0400, Soliman Hesham wrote:
>Try to get a direct flight or through San Francisco.

I hear that. But (west coast perspective...) I avoid SFO like the plague. 
When fog sets in, they shut down one runway, and flights throughout the US 
get delayed. And what is San Francisco famous for? 


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 18:44:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22692;
	Thu, 22 Jul 2004 18:44:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnmJK-0008LS-4s; Thu, 22 Jul 2004 18:45:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnjpJ-0001js-L2; Thu, 22 Jul 2004 16:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnjbI-00034h-SE
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 15:51:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21572
	for <ietf@ietf.org>; Thu, 22 Jul 2004 15:51:30 -0400 (EDT)
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bnjbu-00088o-BD
	for ietf@ietf.org; Thu, 22 Jul 2004 15:52:11 -0400
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id
	i6MJpTnE003147
	for <ietf@ietf.org>; Thu, 22 Jul 2004 20:51:29 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id UAA12409
	for <ietf@ietf.org>; Thu, 22 Jul 2004 20:51:26 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i6MJpQQ16320
	for ietf@ietf.org; Thu, 22 Jul 2004 20:51:26 +0100
Date: Thu, 22 Jul 2004 20:51:25 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Message-ID: <20040722195125.GA16216@login.ecs.soton.ac.uk>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
	<6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
	<20040722120658.GR26441@login.ecs.soton.ac.uk>
	<31495.1090503031@marajade.sandelman.ottawa.on.ca>
	<5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more
	information
X-ECS-MailScanner: Found to be clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Subject: Re: survey on Friday IETF sessions
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c

On Thu, Jul 22, 2004 at 10:55:51AM -0700, Aaron Falk wrote:
> 
> BTW, regarding the survey: there's only been 80 responses so far.  My 
> take is that people don't care about the issue enough to voice their 
> opinion.

Or maybe that 5% of a typical attendance is a good sample of the more
active people?

Tim

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 18:54:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24377;
	Thu, 22 Jul 2004 18:54:13 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnmSm-0000L0-Oz; Thu, 22 Jul 2004 18:54:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnkGT-0007F4-8c; Thu, 22 Jul 2004 16:34:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bnjgo-00056M-1a
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 15:57:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22340
	for <ietf@ietf.org>; Thu, 22 Jul 2004 15:57:09 -0400 (EDT)
Received: from cyphermail.sandelman.ottawa.on.ca ([205.150.200.161]
	helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnjhM-0008Lj-Jd
	for ietf@ietf.org; Thu, 22 Jul 2004 15:57:50 -0400
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca
	[205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i6MJv6X11418
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK) for <ietf@ietf.org>; Thu, 22 Jul 2004 15:57:06 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i6MJv6tA007921
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Thu, 22 Jul 2004 15:57:06 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i6MJv6xq007918 for <ietf@ietf.org>; Thu, 22 Jul 2004 15:57:06 -0400
To: ietf@ietf.org
In-Reply-To: Message from Fred Baker <fred@cisco.com> of "Thu,
	22 Jul 2004 11:22:58 PDT."
	<6.1.1.1.2.20040722112151.064a9380@mira-sjc5-b.cisco.com> 
References: <F4410B91C6CC314F9582B1A8E91DC928BEECCB@ftmail2000>
	<6.1.1.1.2.20040722112151.064a9380@mira-sjc5-b.cisco.com> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 22 Jul 2004 15:57:05 -0400
Message-ID: <7917.1090526225@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Subject: Re: IETF60: time needed for check-in at San Diego? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

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


>>>>> "Fred" == Fred Baker <fred@cisco.com> writes:
    >> Try to get a direct flight or through San Francisco.

    Fred> I hear that. But (west coast perspective...) I avoid SFO like
    Fred> the plague. When fog sets in, they shut down one runway, and
    Fred> flights throughout the US get delayed. And what is San
    Fred> Francisco famous for?

  Ah, but that's why the lineup at SFO is so much shorter!
  And, if the flights are delayed, it's okay if the lineup is longer.

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [

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

iQCVAwUBQQAcCYqHRg3pndX9AQGkJQQA1amzzyFBpGS2Fgh10ygEL8dx6g416enl
4dooEDkv7GCWowLGMD4ar8tBlpVoDt6Hdi5jYMYrz3gCn/ixlj6hKQWphjpqiI0C
zO+XwGa8eIMm/Y+B96U+/PtXe1ABGNTl0Aq8PcRj5pI5ZcQdcQmTp63FCdcFC5+t
X5vnvIY9YZU=
=R+4N
-----END PGP SIGNATURE-----

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 19:02:29 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25822;
	Thu, 22 Jul 2004 19:02:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bnmaj-0000ld-BP; Thu, 22 Jul 2004 19:03:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnlCo-0002cH-Ug; Thu, 22 Jul 2004 17:34:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bnjkg-0007t9-UC
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 16:01:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23049
	for <ietf@ietf.org>; Thu, 22 Jul 2004 16:01:12 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnjlI-0000CL-0Y
	for ietf@ietf.org; Thu, 22 Jul 2004 16:01:53 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i6MK0XJ28064;
	Thu, 22 Jul 2004 13:00:33 -0700
X-mProtect: <200407222000> Nokia Silicon Valley Messaging Protection
Received: from walnut2.iprg.nokia.com (205.226.9.199,
	claiming to be "spruce.nokia.com")
	by darkstar.iprg.nokia.com smtpdbaPyxc; Thu, 22 Jul 2004 13:00:31 PDT
Message-Id: <4.3.2.7.2.20040722125026.00b79c20@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 22 Jul 2004 12:53:55 -0700
To: Fred Baker <fred@cisco.com>
From: Bob Hinden <bob.hinden@nokia.com>
In-Reply-To: <6.1.1.1.2.20040722112151.064a9380@mira-sjc5-b.cisco.com>
References: <F4410B91C6CC314F9582B1A8E91DC928BEECCB@ftmail2000>
	<F4410B91C6CC314F9582B1A8E91DC928BEECCB@ftmail2000>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: ietf@ietf.org
Subject: RE: IETF60: time needed for check-in at San Diego?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581

Fred,

At 11:22 AM 7/22/2004, Fred Baker wrote:
>At 08:55 AM 07/22/04 -0400, Soliman Hesham wrote:
>>Try to get a direct flight or through San Francisco.
>
>I hear that. But (west coast perspective...) I avoid SFO like the plague. 
>When fog sets in, they shut down one runway, and flights throughout the US 
>get delayed. And what is San Francisco famous for?

For what it's worth, my experience at SFO for the past few years is that 
it's been fine.  I prefer it over SJC (San Jose), especially for 
international flights.

Bob


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 19:36:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29923;
	Thu, 22 Jul 2004 19:36:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bnn81-0001sQ-9Z; Thu, 22 Jul 2004 19:37:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnmuM-0002yZ-LK; Thu, 22 Jul 2004 19:23:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnmcW-0002eO-B7
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 19:05:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26023
	for <ietf@ietf.org>; Thu, 22 Jul 2004 19:04:57 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bnmd5-0000nW-FS
	for ietf@ietf.org; Thu, 22 Jul 2004 19:05:40 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 22 Jul 2004 16:06:51 -0700
X-BrightmailFiltered: true
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i6MN4KIV022231;
	Thu, 22 Jul 2004 16:04:20 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	(authenticated bits=0)
	by imail.cisco.com (8.12.5/8.12.10) with ESMTP id i6MNV5kY016044;
	Thu, 22 Jul 2004 16:31:06 -0700
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16640.18419.123043.556829@thomasm-u1.cisco.com>
Date: Thu, 22 Jul 2004 16:04:19 -0700 (PDT)
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
In-Reply-To: <7917.1090526225@marajade.sandelman.ottawa.on.ca>
References: <F4410B91C6CC314F9582B1A8E91DC928BEECCB@ftmail2000>
	<6.1.1.1.2.20040722112151.064a9380@mira-sjc5-b.cisco.com>
	<7917.1090526225@marajade.sandelman.ottawa.on.ca>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &, heK/V66p?[2!i|tVn,
	9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
	@RFNnJEg~WZ/(8<`5a), -7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,
	g">$%B!0w{W)qIhmwhye104zd bUcI'1!
X-IMAIL-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1090539066.254184"; x:"432000"; a:"rsa-sha1"; b:"0:768";
	e:"Iw==";
	n:"zCnd+ByA23/7WMiIwaIZ7Ez3DplzVMdRKP138IXLOvBVeaRZ4yWEPclZ/2Mda"
	"s5Bs9RPWH0BGd3fx6j+txdOXarv4Y8kpMqTexCOMFlDmatpXDXfFj3VI9o4G7"
	"674gFTasaoPcvEfZCwcBgZD7T6sLZa3RTBUGzZqOshAMRpVek=";
	s:"L28c2AIlsdmPJKaorCGuIIPXqRUwyTf0aXCHcNEWz/JUYMti7Mq5ihWSOfw92"
	"ydy02wvKOB4/6FA0s0Hxfk/L581EjdjuW7Ctq4javh8lz1l+HT2Cf+OmiZYGI"
	"DKl+Nq77kE0mPmSYD92ei2fv7Ghd0BJ0oZEt1/m2WWj+GwfTs=";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Thu, 22 Jul 2004 16:04:19 -0700 (PDT)";
	c:"Subject: Re: IETF60: time needed for check-in at San Diego? "
X-IMAIL-VERIFY: s:"y"; v:"y"; r:"19"; h:"imail.cisco.com"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: IETF60: time needed for check-in at San Diego? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit

Michael Richardson writes:
 > -----BEGIN PGP SIGNED MESSAGE-----
 > 
 > 
 > >>>>> "Fred" == Fred Baker <fred@cisco.com> writes:
 >     >> Try to get a direct flight or through San Francisco.
 > 
 >     Fred> I hear that. But (west coast perspective...) I avoid SFO like
 >     Fred> the plague. When fog sets in, they shut down one runway, and
 >     Fred> flights throughout the US get delayed. And what is San
 >     Fred> Francisco famous for?
 > 
 >   Ah, but that's why the lineup at SFO is so much shorter!
 >   And, if the flights are delayed, it's okay if the lineup is longer.

It's clear and sunny here today. Can't imagine
what this scurrilous "fog" hearsay that Fred's on
about.

		Mike, but west of twin peaks
		      doesn't count


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 19:40:40 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00546;
	Thu, 22 Jul 2004 19:40:40 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnnBk-00021A-9d; Thu, 22 Jul 2004 19:41:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnn4r-0000LJ-Jr; Thu, 22 Jul 2004 19:34:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnmjA-0002CZ-TQ
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 19:11:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27309
	for <ietf@ietf.org>; Thu, 22 Jul 2004 19:11:49 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bnmjo-0001CC-2e
	for ietf@ietf.org; Thu, 22 Jul 2004 19:12:33 -0400
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i6MNCjnw088268;
	Fri, 23 Jul 2004 01:12:46 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <6.1.1.1.2.20040722112151.064a9380@mira-sjc5-b.cisco.com>
References: <F4410B91C6CC314F9582B1A8E91DC928BEECCB@ftmail2000>
	<6.1.1.1.2.20040722112151.064a9380@mira-sjc5-b.cisco.com>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <77FA8D76-DC34-11D8-A54A-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Fri, 23 Jul 2004 01:11:31 +0200
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: IETF60: time needed for check-in at San Diego?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit

On 22-jul-04, at 20:22, Fred Baker wrote:

>> Try to get a direct flight or through San Francisco.

> I hear that. But (west coast perspective...) I avoid SFO like the 
> plague. When fog sets in, they shut down one runway, and flights 
> throughout the US get delayed. And what is San Francisco famous for?

I haven't had any real trouble on the way back, I'm more concerned with 
the flight in. At IETF 55 I had to change planes in Washington. Between 
being a bit late in the first place and the lines at immigration and 
the security check I was at the other gate 2 minutes before scheduled 
departure. Fortunately, this flight was late also, so no real trouble. 
Since then I always try to change planes outside of the US. Iceland on 
the way to Minneapolis was especially good: I was at the connecting 
gate 15 minutes after touchdown.

I don't understand why those online booking services still assume 2 
hours between connecting flights...


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 21:26:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07060;
	Thu, 22 Jul 2004 21:26:54 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnoqW-0003NS-Lc; Thu, 22 Jul 2004 21:27:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnobd-0000j7-0O; Thu, 22 Jul 2004 21:12:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnoX9-0007ME-TS
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 21:07:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05982
	for <ietf@ietf.org>; Thu, 22 Jul 2004 21:07:34 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnoXp-00038Y-5F
	for ietf@ietf.org; Thu, 22 Jul 2004 21:08:17 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 22 Jul 2004 18:09:33 -0700
X-BrightmailFiltered: true
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i6N172IV027033;
	Thu, 22 Jul 2004 18:07:02 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-219.cisco.com
	[10.32.244.219]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with SMTP id AVO78293; Thu, 22 Jul 2004 18:05:51 -0700 (PDT)
Message-Id: <6.1.1.1.2.20040722174726.056f5208@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Thu, 22 Jul 2004 18:07:18 -0700
To: Aaron Falk <falk@ISI.EDU>
From: Fred Baker <fred@cisco.com>
In-Reply-To: <5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
	<6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
	<20040722120658.GR26441@login.ecs.soton.ac.uk>
	<31495.1090503031@marajade.sandelman.ottawa.on.ca>
	<5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: ietf@ietf.org
Subject: Re: survey on Friday IETF sessions
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88

At 10:55 AM 07/22/04 -0700, Aaron Falk wrote:
>Perhaps we should raise the bar on what it takes to get a slot at the IETF 
>meeting.  For example, try to come up with some objective criteria for 
>what deserves a 1hr slot, 2hrs, multiple, etc.  This  might even nudge 
>groups into making some additional progress  ("you can't have your meeting 
>if you don't hit a/some milestones").

At the risk of making a statement that arguably belongs on (and which I 
have made on) the problem-statement list...

IMHO, the charter of a working group is a contract-of-sorts to accomplish 
something. If a working group has no future milestones, I can't imagine why 
it is meeting - at minimum, it should be (IMHO) in the process of 
rechartering (which is a milestone in its own right). I would like to see 
working groups held to their chartered work plans, and rechartered if the 
work-plan changes.

I'll name one example, but (since I'm not trying to pick on anybody, 
whether AD, WG Chair, or WG, but point out something that is far too 
frequently true of WGs), I will only tell you how I found them. I went to 
see whether there was an obvious example of a working group that was 
outside its charter. I went to www.ietf.org, clicked on "working groups", 
clicked on the area at the top of the list, and clicked on the first 
working group under that area. This working group has two milestones that 
are past and a number that are future, and no notation of whether they have 
met their milestones or not. I then clicked on the second working group in 
that area, and found the following:

>Done  Submit ### specification as Internet-Draft.
>Done  Submit first Internet-Draft of ### Interoperability Protocol.
>Done  Submit second draft of ### specification as Internet-Draft.
>Done  Submit revised Internet-Draft of ### Interoperability Protocol.
>Done  Submit ### specification to IESG for consideration as a Proposed 
>Standard.
>Done  Submit ### Interoperability Protocol to IESG for consideration as a 
>Proposed Draft.

What *is* a "Proposed Draft" anyway?

>Done  Submit Internet-Draft (informational) on Guide to Implementors using 
>### Protocols
>Feb 01  Hold second ### Testing on ###, ### and ###
>Mar 01  Submit Internet-Draft on ### Protocol to IESG for consideration as 
>a Proposed Standard.
>Jul 01  Request last call on Guide to ###
>Jul 01  Submit Internet-Draft on Guide to ### for consideration as a 
>Proposed Standard
>Jul 01  Submit revisions for Internet-Draft for ###, ### and ###
>Jul 01  Submit revisions for Internet-Draft for ### Protocol
>Jan 02  Evaluate readiness for interoperability testing of ### Protocol

Consider the dates: what is the argument for this WG meeting? Someone needs 
to sit down and very specifically ask "what in the world is happening? Is 
this WG moribund and in need of some merciful person to put it out of its 
misery? If not, what is the real plan for its future?"

On the whole, the IESG is doing a much better job than it used to in this 
area. But I will agree that working groups need to do a much better job of 
managing to their objectives, and producing results. Whether that means 
interim meetings or putting an end to projects that are not actually moving 
forward, working groups (and therefore chairs and authors) need to take 
their tasks rather more seriously than they do, and ADs need to grade them 
on their track record in doing so.

If there is further comment on this topic, I would suggest it continue on 
the problem-statement list. 


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 23:08:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24153;
	Thu, 22 Jul 2004 23:08:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnqRD-0004cC-PC; Thu, 22 Jul 2004 23:09:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnq8A-0007N5-Ca; Thu, 22 Jul 2004 22:49:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bnq4k-0005nP-Q8
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 22:46:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22706
	for <ietf@ietf.org>; Thu, 22 Jul 2004 22:46:20 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bnq5Q-0004Iz-4O
	for ietf@ietf.org; Thu, 22 Jul 2004 22:47:05 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1Bnq4Z-0000Iw-Qv; Thu, 22 Jul 2004 22:46:12 -0400
Date: Thu, 22 Jul 2004 22:46:07 -0400
From: John C Klensin <john-ietf@jck.com>
To: Aaron Falk <falk@ISI.EDU>, Michael Richardson <mcr@sandelman.ottawa.on.ca>
Message-ID: <99812074371554AA5D7A2B21@localhost>
In-Reply-To: <5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
	<6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
	<20040722120658.GR26441@login.ecs.soton.ac.uk>
	<31495.1090503031@marajade.sandelman.ottawa.on.ca>
	<5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: survey on Friday IETF sessions
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit



--On Thursday, July 22, 2004 10:55 AM -0700 Aaron Falk 
<falk@ISI.EDU> wrote:

> BTW, regarding the survey: there's only been 80 responses so
> far.  My take is that people don't care about the issue enough
> to voice their opinion.

I can't guess at the percentages, but at least a few people (who 
do care) took a look at the survey, concluded that answering it 
accurately would take some digging through old notes, assessed 
the odds that the questions, as asked, would yield good and 
useful information, and then decided they had other things to do 
with their lives than to respond to the "survey".

     john


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 22 23:57:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26940;
	Thu, 22 Jul 2004 23:57:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnrCL-00056o-JZ; Thu, 22 Jul 2004 23:58:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnr5Q-0002gB-Px; Thu, 22 Jul 2004 23:51:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bnr0u-0000CT-F9
	for ietf@megatron.ietf.org; Thu, 22 Jul 2004 23:46:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26391
	for <ietf@ietf.org>; Thu, 22 Jul 2004 23:46:25 -0400 (EDT)
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bnr1a-00050B-Cz
	for ietf@ietf.org; Thu, 22 Jul 2004 23:47:11 -0400
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i6N3jnnn027276
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Thu, 22 Jul 2004 23:45:50 -0400
Date: Thu, 22 Jul 2004 23:45:49 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: ietf@ietf.org
Message-ID: <Pine.LNX.4.44.0407222343430.26723-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: Report on Nanog
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 2.7 (++)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4

Have I been ejected from the IETF list?

Or is this just one of many false reports posted to Nanog?

		--Dean

---------- Forwarded message ----------
Date: Thu, 22 Jul 2004 19:51:42 -0700
From: Michel Py <michel@arneill-py.sacramento.ca.us>
To: Mark Kent <mark@noc.mainstreet.net>
Cc: nanog@merit.edu
Subject: RE: T1 short-haul vs. long-haul


Please don't feed the troll; he's about to be ejected from IETF mailing
lists by my request, and can't stand it.

Thanks
Michel.

-----Original Message-----
From: Mark Kent [mailto:mark@noc.mainstreet.net] 
Sent: Thursday, July 22, 2004 3:53 PM
To: dean@av8.com
Cc: Michel Py; nanog@merit.edu
Subject: Re: T1 short-haul vs. long-haul

Dean Anderson <dean@av8.com> typed:
>> Hmm. Michel, We disagree on everything it seems.

Just for the record: I believe that, with the exception of your
first point (re: diff between ATT telecom and ATT data services),
the rest of your black-and-white "Wrong" declarations should instead
be more vague "YMMV" declarations.

-mark


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul 23 00:58:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00745;
	Fri, 23 Jul 2004 00:58:42 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bns9Z-00060W-Eo; Fri, 23 Jul 2004 00:59:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnryQ-0005CD-83; Fri, 23 Jul 2004 00:47:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnrtF-0002Ek-FE
	for ietf@megatron.ietf.org; Fri, 23 Jul 2004 00:42:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29802
	for <ietf@ietf.org>; Fri, 23 Jul 2004 00:42:34 -0400 (EDT)
Received: from vmail.vsnl.com ([203.199.113.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bnrtw-0005pr-Cf
	for ietf@ietf.org; Fri, 23 Jul 2004 00:43:21 -0400
Received: from tsslaptop ([127.0.0.1])
	by vmail.vsnl.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May
	14
	2003)) with ESMTP id <0I1A00A21FPUSF@vmail.vsnl.com> for ietf@ietf.org;
	Fri, 23 Jul 2004 10:11:59 +0530 (IST)
Received: from ([tataelxsi.co.in (203.197.168.145)])
	by vmail.vsnl.com	(InterScan E-Mail VirusWall Unix); Fri,
	23 Jul 2004 10:11:58 +0530 (IST)
Date: Fri, 23 Jul 2004 10:11:58 +0530
From: Saravanan T S <saravanants@tataelxsi.co.in>
In-reply-to: <40FFFECD.FF21BDAC@wipro.com>
To: "'Mahendran'" <mahendran.devaraj@wipro.com>, ietf@ietf.org
Message-id: <021801c4706f$668109f0$793c010a@telxsi.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.2616
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7BIT
Subject: RE: Activities of IETF in Asia Pacific
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7BIT

Even I would be interested to know the same.
Thanks.

./tss

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Mahendran
Sent: Thursday, July 22, 2004 11:22 PM
To: ietf@ietf.org
Subject: Activities of IETF in Asia Pacific

hai all,
Can anyone let me about the activities of IETF in the Asia Pacific
Give me in detail if possible.

Thanks
Mahe


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul 23 04:09:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28256;
	Fri, 23 Jul 2004 04:09:48 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bnv8V-0000R6-MQ; Fri, 23 Jul 2004 04:10:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnuvP-00081u-MX; Fri, 23 Jul 2004 03:57:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnumY-0004H9-CT; Fri, 23 Jul 2004 03:47:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26798;
	Fri, 23 Jul 2004 03:47:52 -0400 (EDT)
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnunG-0008OX-9U; Fri, 23 Jul 2004 03:48:39 -0400
Received: from consulintel02 by consulintel.es (MDaemon.PRO.v7.1.2.R)
	with ESMTP id md50000154584.msg; Fri, 23 Jul 2004 09:50:17 +0200
Message-ID: <30ca01c47089$384ff090$8700000a@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ngtrans@sunroof.eng.sun.com>, <v6ops@ops.ietf.org>, <ipv6@ietf.org>,
        <multi6@ops.ietf.org>, <mip6@ietf.org>, <ietf@ietf.org>
Date: Fri, 23 Jul 2004 09:46:50 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
X-Priority: 1
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Fri, 23 Jul 2004 09:50:17 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDAV-Processed: consulintel.es, Fri, 23 Jul 2004 09:50:20 +0200
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: quoted-printable
Subject: IEEE SAINT2005 workshop CPF: IPv6 Deployment Status and Challenges
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: quoted-printable

Hi all,

The call for papers for this international workshop is now open until October 7. Authors are kindly requested to submit papers as early as possible to facilitate a review process.

IEEE SAINT2005 workshop CPF: IPv6 Deployment Status and Challenges
http://www.ist-ipv6.org/modules.php?op=3Dmodload&name=3DNews&file=3Darticle&sid=3D659

Please forward this email to all your contacts.

Regards,
Jordi




**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul 23 04:55:57 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02236;
	Fri, 23 Jul 2004 04:55:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnvrA-0001LU-Cm; Fri, 23 Jul 2004 04:56:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnvmG-0004nv-Io; Fri, 23 Jul 2004 04:51:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnvjJ-0003ML-Uu
	for ietf@megatron.ietf.org; Fri, 23 Jul 2004 04:48:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01700
	for <ietf@ietf.org>; Fri, 23 Jul 2004 04:48:36 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bnvk0-0001DA-Gi
	for ietf@ietf.org; Fri, 23 Jul 2004 04:49:23 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 23 Jul 2004 01:50:35 -0700
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i6N8m1IV007910;
	Fri, 23 Jul 2004 01:48:01 -0700 (PDT)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id BAA23990;
	Fri, 23 Jul 2004 01:48:01 -0700 (PDT)
Date: Fri, 23 Jul 2004 01:48:01 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Saravanan T S <saravanants@tataelxsi.co.in>
In-Reply-To: <021801c4706f$668109f0$793c010a@telxsi.com>
Message-ID: <Pine.HPX.4.58.0407230141340.13474@wells.cisco.com>
References: <021801c4706f$668109f0$793c010a@telxsi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: ietf@ietf.org
Subject: RE: Activities of IETF in Asia Pacific
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793

The IETF is the standards setting organization for the Internet. As such,
it does not have "activities" in any specific regions of the world, unless
you mean IETF Meetings. We did meet in Seoul, Korea last time and have
previously met in Adelaide, Australia and Yokohama, Japan.

Participants in the IETF process come from all regions of the world and
participation is by e-mail or thought the regular meetings.

Please visit www.ietf.org for more information.

Ole


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



On Fri, 23 Jul 2004, Saravanan T S wrote:

> Even I would be interested to know the same.
> Thanks.
>
> ./tss
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Mahendran
> Sent: Thursday, July 22, 2004 11:22 PM
> To: ietf@ietf.org
> Subject: Activities of IETF in Asia Pacific
>
> hai all,
> Can anyone let me about the activities of IETF in the Asia Pacific
> Give me in detail if possible.
>
> Thanks
> Mahe
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul 23 05:03:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02752;
	Fri, 23 Jul 2004 05:03:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnvyF-0001Tr-C8; Fri, 23 Jul 2004 05:04:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnvrZ-0006xf-QD; Fri, 23 Jul 2004 04:57:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bnvnq-0005Ro-Qy
	for ietf@megatron.ietf.org; Fri, 23 Jul 2004 04:53:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01992
	for <ietf@ietf.org>; Fri, 23 Jul 2004 04:53:17 -0400 (EDT)
Received: from wiproecmx1.wipro.com ([164.164.31.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnvoN-0001IC-H8
	for ietf@ietf.org; Fri, 23 Jul 2004 04:54:04 -0400
Received: from ec-vwall-wd (ec-vwall-wd.wipro.com [10.200.52.125])
	by wiproecmx1.wipro.com (8.12.9-20031013/8.12.9) with SMTP id
	i6N8qUEd000202
	for <ietf@ietf.org>; Fri, 23 Jul 2004 14:22:30 +0530 (IST)
Received: from blr-ec-bh2.wipro.com ([10.200.50.92]) by ec-vwall-wd with
	InterScan Messaging Security Suite; Fri, 23 Jul 2004 14:22:29 +0530
Received: from blr-ec-msg02.wipro.com ([10.200.51.99]) by blr-ec-bh2.wipro.com
	with Microsoft SMTPSVC(5.0.2195.6713); 
	Fri, 23 Jul 2004 14:22:28 +0530
Received: from wipro.com ([192.168.22.182]) by blr-ec-msg02.wipro.com with
	Microsoft SMTPSVC(5.0.2195.6713); Fri, 23 Jul 2004 14:22:27 +0530
Message-ID: <4100D16A.5AD8F045@wipro.com>
Date: Fri, 23 Jul 2004 14:20:50 +0530
From: Mahendran <mahendran.devaraj@wipro.com>
Organization: Wipro Technologies
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>, ietf@ietf.org
References: <021801c4706f$668109f0$793c010a@telxsi.com>
	<Pine.HPX.4.58.0407230141340.13474@wells.cisco.com>
Content-Type: multipart/mixed; boundary="------------F294779DA894474B857318E4"
X-OriginalArrivalTime: 23 Jul 2004 08:52:27.0814 (UTC)
	FILETIME=[61988C60:01C47092]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: Re: Activities of IETF in Asia Pacific
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1

This is a multi-part message in MIME format.
--------------F294779DA894474B857318E4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

WWEgSSBtZWFudCB0aGUgbWVldGluZ3MNClRoYW5rcyBmb3IgeW91ciBpbmZvcm1hdGlvbg0K
UmVnYXJkcywNCk1haGVuZHJhbg0K
--------------F294779DA894474B857318E4
Content-Type: text/x-vcard; charset=UTF-8;
 name="mahendran.devaraj.vcf"
Content-Description: Card for Mahendran
Content-Disposition: attachment;
 filename="mahendran.devaraj.vcf"
Content-Transfer-Encoding: base64

YmVnaW46dmNhcmQgCm46O01haGVuZHJhbgp0ZWw7Y2VsbDowODAtMzczNDQ4NTFbUmVsaWFu
Y2VdCnRlbDt3b3JrOjI4NTIwNDA4LzUxMjIxMTExL0V4dG44NTMxNgp4LW1vemlsbGEtaHRt
bDpUUlVFCm9yZzpXaXBybyBUZWNobm9sb2dpZXM7VGVsZWNvbW11bmljYXRpb24gYW5kIElu
dGVybmV0d29ya2luZwp2ZXJzaW9uOjIuMQplbWFpbDtpbnRlcm5ldDptYWhlbmRyYW4uZGV2
YXJhakB3aXByby5jb20KdGl0bGU6UHJvamVjdCBFbmdpbmVlcgphZHI7cXVvdGVkLXByaW50
YWJsZTo7O0VDMywgVG93ZXIgOCxDIFdpbmcsIDV0aCBGbG9vciwgPTBEPTBBV2lwcm8gVGVj
aG5vbG9naWVzLD0wRD0wQTcyLCBLZW9uaWNzLCBFbGVjdHJvbmljIENpdHksPTBEPTBBO0Jh
bmdhbG9yZS01NjAyMjk7OzsKbm90ZTtxdW90ZWQtcHJpbnRhYmxlOj0wRD0wQQp4LW1vemls
bGEtY3B0OjsxNDY4OApmbjpNYWhlbmRyYW4KZW5kOnZjYXJkCg==
--------------F294779DA894474B857318E4
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

--------------F294779DA894474B857318E4--




From ietf-bounces@ietf.org  Fri Jul 23 08:34:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17645;
	Fri, 23 Jul 2004 08:34:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BnzGw-0005TI-KI; Fri, 23 Jul 2004 08:35:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnz40-0003wn-Jx; Fri, 23 Jul 2004 08:22:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bnz2Q-00033d-8N
	for ietf@megatron.ietf.org; Fri, 23 Jul 2004 08:20:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16707
	for <ietf@ietf.org>; Fri, 23 Jul 2004 08:20:33 -0400 (EDT)
Received: from mailgate1.fcc.gov ([192.104.54.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bnz3A-0005Dl-MN
	for ietf@ietf.org; Fri, 23 Jul 2004 08:21:22 -0400
Received: from fw1 ([192.104.54.27])
	by mailgate1.fcc.gov (dcMail/040510q) with SMTP id i6NCK20n004547
	for <ietf@ietf.org>; Fri, 23 Jul 2004 08:20:02 -0400 (EDT)
Received: from smarthost1.fcc.gov ([165.135.234.3]) by fw1.fcc.gov;
	Fri, 23 Jul 2004 08:19:44 -0400 (EDT)
Received: from P2PXCS01.fccnet.win.fcc.gov (p2pxcs01.fccnet.win.fcc.gov
	[165.135.240.60]) by smarthost1.fcc.gov with ESMTP for
	ietf@ietf.org; Fri, 23 Jul 2004 08:19:45 -0400
Received: from P2PXMB01.fccnet.win.fcc.gov ([165.135.240.50]) by
	P2PXCS01.fccnet.win.fcc.gov with Microsoft SMTPSVC(5.0.2195.6713); 
	Fri, 23 Jul 2004 08:19:45 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 23 Jul 2004 08:19:44 -0400
Message-Id: <BF17D4F30776D441B05165F92C68ACD103458B4E@p2pxmb01.fccnet.win.fcc.gov>
Thread-Topic: USG IPv6 Public Mtg notice
Thread-Index: AcRwr1dEsky+RnWrT5WovChKCkACQg==
From: "Richard Hovey" <Richard.Hovey@fcc.gov>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 23 Jul 2004 12:19:45.0469 (UTC)
	FILETIME=[570416D0:01C470AF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: quoted-printable
Subject: USG IPv6 Public Mtg notice
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: quoted-printable

I haven't noticed this on the list, so I thought=20
I'd post this excerpt from the July 15 Federal Register.
More info and discussion paper at=20
http://www.ntia.doc.gov/ntiahome/ntiageneral/ipv6/index.html

SUMMARY: The National Institute of Standards and
Technology (NIST) and the National Telecommunications
and Information Administration (NTIA), U.S. Department
of Commerce, will host a half-day public meeting on
Internet Protocol version 6 (IPv6), entitled IPv6
Public Meeting.=20

The meeting will provide an opportunity for interested=20
parties to discuss IPv6 deployment issues, including=20
the appropriate government role, if any, in IPv6=20
deployment.

DATES: The IPv6 Public Meeting will be held from 9:00
a.m. to 1:30 p.m. on Wednesday, July 28, 2004.

ADDRESSES: The public meeting will be held at the U.S.
Department of Commerce, 1401 Constitution Avenue,
N.W., Room 4830, Washington, D.C. (Entrance to the
Department of Commerce is on 14th Street between
Constitution and Pennsylvania Avenues, N.W.)

FOR FURTHER INFORMATION CONTACT: Alfred Lee, Office of
Policy Analysis and Development, NTIA, at (202)
482-1880, or via electronic mail: alee at ntia.doc.gov.

NTIA is posting the IPv6 Task Force discussion draft,=20
"Technical and Economic Assessment of Internet Protocol=20
Version 6 (IPv6)."



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul 23 18:31:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02097;
	Fri, 23 Jul 2004 18:31:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bo8ad-0007fJ-Pi; Fri, 23 Jul 2004 18:32:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bo8UZ-0007ig-CZ; Fri, 23 Jul 2004 18:26:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bo8Ot-0006in-CZ
	for ietf@megatron.ietf.org; Fri, 23 Jul 2004 18:20:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01764
	for <ietf@ietf.org>; Fri, 23 Jul 2004 18:20:20 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bo8Ph-0007b5-8f
	for ietf@ietf.org; Fri, 23 Jul 2004 18:21:16 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 3F85461B92; Sat, 24 Jul 2004 00:19:48 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 07475-05; Sat, 24 Jul 2004 00:19:47 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id 501E461B7E; Sat, 24 Jul 2004 00:19:46 +0200 (CEST)
Date: Fri, 23 Jul 2004 22:34:32 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>, ietf@ietf.org
Message-ID: <8FE382BBF7062ECC4DF9EF58@B50854F0A9192E8EC6CDA126>
In-Reply-To: <Pine.LNX.4.44.0407222343430.26723-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0407222343430.26723-100000@cirrus.av8.net>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Subject: Re: Report on Nanog
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit

Michel Py suggested it on June 14. I have not acted on the request.

--On 22. juli 2004 23:45 -0400 Dean Anderson <dean@av8.com> wrote:

> Have I been ejected from the IETF list?
>
> Or is this just one of many false reports posted to Nanog?
>





_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Sun Jul 25 14:43:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20957;
	Sun, 25 Jul 2004 14:43:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BonzL-0001LP-5N; Sun, 25 Jul 2004 14:44:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BonuS-0003Fs-PE; Sun, 25 Jul 2004 14:39:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bonts-000388-1V
	for ietf@megatron.ietf.org; Sun, 25 Jul 2004 14:39:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20790
	for <ietf@ietf.org>; Sun, 25 Jul 2004 14:39:06 -0400 (EDT)
Received: from darkwing.uoregon.edu ([128.223.142.13] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bonv6-0001Il-SY
	for ietf@ietf.org; Sun, 25 Jul 2004 14:40:25 -0400
Received: from twin.uoregon.edu (twin.uoregon.edu [128.223.214.27])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6PId5qI029323
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); 
	Sun, 25 Jul 2004 11:39:06 -0700 (PDT)
Date: Sun, 25 Jul 2004 11:39:05 -0700 (PDT)
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
X-X-Sender: joelja@twin.uoregon.edu
To: ietf@ietf.org
Message-ID: <Pine.LNX.4.60.0407251132120.32094@twin.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: Current plan for IETF-60
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793


Broadcasting for IETF-60 has some substantial changes from previous
meetings.

Coverage has been expanded from 2 to 4 rooms (meeting wise the are 6-7
rooms in use at all times during the day), as soon as we have a final
schedule we'll know which ones they are...

The two new rooms as well as the traditional multicast rooms will be
served with a new unicast mp3 audio stream. The audio will be reflected
off a Quicktime darwin streaming-server located at the University of
Orego.

More information is available from our IETF 60 broadcast page located 
here:

http://videolab.uoregon.edu/events/ietf/ietf60.html

so, to recap sources from IETF 60 should be:

Channel-1
 	h.261/pcm - multicast
 	mpeg-1 - multicast
 	mp3 - unicast
Chanel-2
         h.261/pcm - multicast
         mpeg-1 - multicast
 	mp3 - unicast
Channel-3
 	mp3 - unicast
Channel-4
 	mp3 - unicast

In terms of archiving, mpeg-1 and mp3 audio recording should become
available shortly after the completion of a given day on an ftp server
local to the IETF, as well as from the UO as has been typical for the
last couple of meetings.

Regards
joelja

--
--------------------------------------------------------------------------
Joel Jaeggli  	       Unix Consulting 	       joelja@darkwing.uoregon.edu
GPG Key Fingerprint:     5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Mon Jul 26 11:37:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16160;
	Mon, 26 Jul 2004 11:37:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bp7ZE-0007CP-Bt; Mon, 26 Jul 2004 11:39:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bp7K3-0006hU-LZ; Mon, 26 Jul 2004 11:23:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bp7Bm-0004Mu-KS
	for ietf@megatron.ietf.org; Mon, 26 Jul 2004 11:14:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11888
	for <ietf@ietf.org>; Mon, 26 Jul 2004 11:14:51 -0400 (EDT)
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bp7DB-0005Sr-CA
	for ietf@ietf.org; Mon, 26 Jul 2004 11:16:22 -0400
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i6QFEHaM027119
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 26 Jul 2004 11:14:18 -0400
Date: Mon, 26 Jul 2004 11:14:17 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
In-Reply-To: <8FE382BBF7062ECC4DF9EF58@B50854F0A9192E8EC6CDA126>
Message-ID: <Pine.LNX.4.44.0407261112440.27021-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ietf@ietf.org
Subject: Re: Report on Nanog
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 2.7 (++)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

Can you elaborate?  

Do you mean that it was a silly request, that was immediately rejected or 
do you mean you are thinking it over?  "Thinking it over for 6 weeks" 
seems sort of defamatory.

		--Dean


On Fri, 23 Jul 2004, Harald Tveit Alvestrand wrote:

> Michel Py suggested it on June 14. I have not acted on the request.
> 
> --On 22. juli 2004 23:45 -0400 Dean Anderson <dean@av8.com> wrote:
> 
> > Have I been ejected from the IETF list?
> >
> > Or is this just one of many false reports posted to Nanog?
> >
> 
> 
> 
> 
> 


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul 27 02:48:58 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23337;
	Tue, 27 Jul 2004 02:48:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BpLnH-00018g-V1; Tue, 27 Jul 2004 02:50:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BpLiT-0002MI-Nv; Tue, 27 Jul 2004 02:45:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BpLft-0001rr-Ka
	for ietf@megatron.ietf.org; Tue, 27 Jul 2004 02:42:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23171
	for <ietf@ietf.org>; Tue, 27 Jul 2004 02:42:56 -0400 (EDT)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpLhR-00014J-Jh
	for ietf@ietf.org; Tue, 27 Jul 2004 02:44:34 -0400
Received: from parmhs4.rd.francetelecom.fr ([10.193.117.63]) by
	parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(6.0.3790.0); 
	Tue, 27 Jul 2004 08:42:48 +0200
Received: from [10.193.106.18] ([10.193.106.18]) by
	parmhs4.rd.francetelecom.fr with Microsoft SMTPSVC(5.0.2195.6747); 
	Tue, 27 Jul 2004 08:42:47 +0200
Message-ID: <4105F996.5070501@rd.francetelecom.fr>
Date: Tue, 27 Jul 2004 08:43:34 +0200
From: Florent <florent.bersani@rd.francetelecom.fr>
User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Jul 2004 06:42:47.0459 (UTC)
	FILETIME=[EDCB9730:01C473A4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Subject: Naming convention for a WG I-D that returns to individual
	submission?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit

Hi all,

I am looking for procedural guidance on the naming convention to be 
followed for an Internet-Draft that has been adopted as a WG item and 
that has therefore been granted a name like 
draft-mybelovedwg-blabla-XX.txt but that is now returning to the 
individual submission status - be it that the WG finally abandoned this 
WG item after more technical investigations, that the WG rechartered 
making this former WG item now out of scope, etc.

Thus, this Internet-Draft should probably revert to a filename similar 
to draft-myfavoriteauthor-blibli-YY.txt, shouldn't it?

I couldn't unfortunately find any relevant text on this (though I tried 
RFC 2026 and http://www.ietf.org/ietf/1id-guidelines.txt) :-(

Any feedback most welcome,
Many thanks in advance,

Florent

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Tue Jul 27 12:38:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27381;
	Tue, 27 Jul 2004 12:38:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BpV0A-0003fv-UR; Tue, 27 Jul 2004 12:40:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BpUhq-00010M-0w; Tue, 27 Jul 2004 12:21:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BpUXn-0006Qr-Os
	for ietf@megatron.ietf.org; Tue, 27 Jul 2004 12:11:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25151
	for <ietf@ietf.org>; Tue, 27 Jul 2004 12:11:09 -0400 (EDT)
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpUZR-000306-0z
	for ietf@ietf.org; Tue, 27 Jul 2004 12:12:53 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i6RGAWN31647;
	Tue, 27 Jul 2004 09:10:32 -0700
Date: Tue, 27 Jul 2004 09:08:35 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <699096171.20040727090835@brandenburg.com>
To: Florent <florent.bersani@rd.francetelecom.fr>
In-Reply-To: <4105F996.5070501@rd.francetelecom.fr>
References: <4105F996.5070501@rd.francetelecom.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Naming convention for a WG I-D that returns to individual
	submission?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

Florent,

F> Thus, this Internet-Draft should probably revert to a filename similar 
F> to draft-myfavoriteauthor-blibli-YY.txt, shouldn't it?

I don't recall seeing any guidance for choosing the full details of a
private I-D's name.

blibli-YY is chosen at the author's discretion. Having blibli be the
name of the working group has obvious benefits.

So, your thought on the choices sounds reasonable to me.

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


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 29 02:48:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19777;
	Thu, 29 Jul 2004 02:48:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bq4kf-0007AM-72; Thu, 29 Jul 2004 02:50:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bq4d7-0007ow-3n; Thu, 29 Jul 2004 02:43:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bq4PI-0005Aa-Lf
	for ietf@megatron.ietf.org; Thu, 29 Jul 2004 02:28:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18303
	for <ietf@ietf.org>; Thu, 29 Jul 2004 02:28:47 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bq4RF-0006m7-Ug
	for ietf@ietf.org; Thu, 29 Jul 2004 02:30:51 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 398C761B91; Thu, 29 Jul 2004 08:28:16 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 12095-04; Thu, 29 Jul 2004 08:28:15 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id 0D9A561A93; Thu, 29 Jul 2004 08:28:15 +0200 (CEST)
Date: Thu, 29 Jul 2004 08:28:14 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Florent <florent.bersani@rd.francetelecom.fr>, ietf@ietf.org
Message-ID: <D6B102EB643A6E67C4FC39C2@[10.0.0.9]>
In-Reply-To: <4105F996.5070501@rd.francetelecom.fr>
References: <4105F996.5070501@rd.francetelecom.fr>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
Subject: Re: Naming convention for a WG I-D that returns to
 individual	submission?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit

Florent,
as in many other things, the IETF doesn't have a history of complete 
consistency.....

in the case of an existing WG abandoning an I-D, I'm sure that the next 
version of the I-D should be named draft-myfavouriteauthor-something (where 
"something" can easily contain the WG name if so desired).

Sometimes, when a WG is closed with outstanding I-Ds, and some of these are 
finished as individual submissions, we have allowed them to be updated 
keeping the old draft name. But that's the exception.

Makes sense?

                   Harald

--On 27. juli 2004 08:43 +0200 Florent 
<florent.bersani@rd.francetelecom.fr> wrote:

> Hi all,
>
> I am looking for procedural guidance on the naming convention to be
> followed for an Internet-Draft that has been adopted as a WG item and
> that has therefore been granted a name like
> draft-mybelovedwg-blabla-XX.txt but that is now returning to the
> individual submission status - be it that the WG finally abandoned this
> WG item after more technical investigations, that the WG rechartered
> making this former WG item now out of scope, etc.
>
> Thus, this Internet-Draft should probably revert to a filename similar to
> draft-myfavoriteauthor-blibli-YY.txt, shouldn't it?
>
> I couldn't unfortunately find any relevant text on this (though I tried
> RFC 2026 and http://www.ietf.org/ietf/1id-guidelines.txt) :-(
>
> Any feedback most welcome,
> Many thanks in advance,
>
> Florent
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>





_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Thu Jul 29 12:20:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22252;
	Thu, 29 Jul 2004 12:20:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BqDgR-0007SA-ED; Thu, 29 Jul 2004 12:23:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BqBnH-0004nY-2E; Thu, 29 Jul 2004 10:22:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BqBAH-0007lL-HS
	for ietf@megatron.ietf.org; Thu, 29 Jul 2004 09:41:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22572
	for <ietf@ietf.org>; Thu, 29 Jul 2004 03:27:59 -0400 (EDT)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bq5MZ-0007mF-Tu
	for ietf@ietf.org; Thu, 29 Jul 2004 03:30:04 -0400
Received: from parmhs4.rd.francetelecom.fr ([10.193.117.63]) by
	parsmtp2.rd.francetelecom.com with Microsoft SMTPSVC(6.0.3790.0); 
	Thu, 29 Jul 2004 09:27:51 +0200
Received: from [10.193.167.26] ([10.193.167.26]) by
	parmhs4.rd.francetelecom.fr with Microsoft SMTPSVC(5.0.2195.6747); 
	Thu, 29 Jul 2004 09:27:50 +0200
Message-ID: <4108A729.5070609@rd.francetelecom.fr>
Date: Thu, 29 Jul 2004 09:28:41 +0200
From: Florent Bersani <florent.bersani@rd.francetelecom.fr>
User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
References: <4105F996.5070501@rd.francetelecom.fr>
	<D6B102EB643A6E67C4FC39C2@[10.0.0.9]>
In-Reply-To: <D6B102EB643A6E67C4FC39C2@[10.0.0.9]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Jul 2004 07:27:50.0731 (UTC)
	FILETIME=[8DE5A9B0:01C4753D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Naming convention for a WG I-D that returns to
	individual	submission?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: 7bit

Harald,

Harald Tveit Alvestrand wrote:

> Florent,
> as in many other things, the IETF doesn't have a history of complete 
> consistency.....
>
> in the case of an existing WG abandoning an I-D, I'm sure that the 
> next version of the I-D should be named 
> draft-myfavouriteauthor-something (where "something" can easily 
> contain the WG name if so desired).
>
> Sometimes, when a WG is closed with outstanding I-Ds, and some of 
> these are finished as individual submissions, we have allowed them to 
> be updated keeping the old draft name. But that's the exception.
>
> Makes sense?

It makes a lot of sense: many thanks for the piece of advice :-)

Florent

P.S:

1) My original concern was that if a WG I-D has been abandoned, having 
it keep its draft-mybelovedWG-something name could be confusing.
     Indeed, people aware of the IETF naming convention for I-Ds but not 
of the history of this draft might misinterpret the status of this 
particular draft!
     And this was my case for a specific draft ;-) ...
    However, I also agree that making the abandoned WG I-D revert to an 
individual submission filename could also confuse by "hiding" the 
version numbers of the work that has possibly been done while it was a 
WG item.

2) My two cents: perhaps we could incorporate this in the Guidelines to 
Authors of Internet-Drafts (http://www.ietf.org/ietf/1id-guidelines.txt) 
in the submitting section, at the end of the second paragraph:
"If the document is abandoned as a working group document, it should be 
processed as an individual submission, where the filename will be 
draft-<yourname>-....txt".... but since I am not sure how often this 
occurs, such a precision may be more harmful than useful

>
>
>                   Harald
>
> --On 27. juli 2004 08:43 +0200 Florent 
> <florent.bersani@rd.francetelecom.fr> wrote:
>
>> Hi all,
>>
>> I am looking for procedural guidance on the naming convention to be
>> followed for an Internet-Draft that has been adopted as a WG item and
>> that has therefore been granted a name like
>> draft-mybelovedwg-blabla-XX.txt but that is now returning to the
>> individual submission status - be it that the WG finally abandoned this
>> WG item after more technical investigations, that the WG rechartered
>> making this former WG item now out of scope, etc.
>>
>> Thus, this Internet-Draft should probably revert to a filename 
>> similar to
>> draft-myfavoriteauthor-blibli-YY.txt, shouldn't it?
>>
>> I couldn't unfortunately find any relevant text on this (though I tried
>> RFC 2026 and http://www.ietf.org/ietf/1id-guidelines.txt) :-(
>>
>> Any feedback most welcome,
>> Many thanks in advance,
>>
>> Florent
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf
>>
>
>
>
>
>


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul 30 10:03:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06750;
	Fri, 30 Jul 2004 10:03:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BqY1a-0007sU-45; Fri, 30 Jul 2004 10:06:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BqXkj-0008Ag-Ac; Fri, 30 Jul 2004 09:48:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BqXjw-0007ac-Gh
	for ietf@megatron.ietf.org; Fri, 30 Jul 2004 09:48:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28614
	for <ietf@ietf.org>; Fri, 30 Jul 2004 06:47:38 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BqUxa-0005Mj-7M
	for ietf@ietf.org; Fri, 30 Jul 2004 06:49:59 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i6UAkLC20550;
	Fri, 30 Jul 2004 03:46:21 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200407301046.i6UAkLC20550@boreas.isi.edu>
To: harald@alvestrand.no (Harald Tveit Alvestrand)
Date: Fri, 30 Jul 2004 03:46:21 -0700 (PDT)
In-Reply-To: <D6B102EB643A6E67C4FC39C2@[10.0.0.9]> from "Harald Tveit
	Alvestrand" at Jul 29, 2004 08:28:14 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: bmanning
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Naming convention for a WG I-D that returns to
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit


clearly different rules apply, depending on whom makes the submission.

for example, several individual submissions were made before this
IETF and we (the authors) were told that we -MUST- use the name of
one of th eauthors in the draft name... however, we see that other
individual submissions are allowed to fabricate ID lables that do not
reflect any of the authors or any WG.  e.g.


draft-ymbk-downref-03.txt
draft-kolkman-dnsext-dnssec-in-band-rollover-00

of course, ymmv. I remain greatful for the opportunity to publish
ideas in this forum. 

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

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul 30 12:53:57 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18926;
	Fri, 30 Jul 2004 12:53:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bqag8-0002dE-IK; Fri, 30 Jul 2004 12:56:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BqaXK-0003tq-7T; Fri, 30 Jul 2004 12:47:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BqaQH-00014x-VQ
	for ietf@megatron.ietf.org; Fri, 30 Jul 2004 12:39:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18027
	for <ietf@ietf.org>; Fri, 30 Jul 2004 12:39:54 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BqaSV-0002PD-8A
	for ietf@ietf.org; Fri, 30 Jul 2004 12:42:18 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i6UGdCM06515;
	Fri, 30 Jul 2004 09:39:12 -0700
X-mProtect: <200407301639> Nokia Silicon Valley Messaging Protection
Received: from walnut2.iprg.nokia.com (205.226.9.199,
	claiming to be "spruce.nokia.com")
	by darkstar.iprg.nokia.com smtpdKlFzSa; Fri, 30 Jul 2004 09:39:10 PDT
Message-Id: <4.3.2.7.2.20040730092746.01a4f3e0@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 30 Jul 2004 09:34:45 -0700
To: Bill Manning <bmanning@ISI.EDU>
From: Bob Hinden <bob.hinden@nokia.com>
In-Reply-To: <200407301046.i6UAkLC20550@boreas.isi.edu>
References: <D6B102EB643A6E67C4FC39C2@[10.0.0.9]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: Naming convention for a WG I-D that returns to
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22

Bill,

At 03:46 AM 7/30/2004, Bill Manning wrote:

>clearly different rules apply, depending on whom makes the submission.
>
>for example, several individual submissions were made before this
>IETF and we (the authors) were told that we -MUST- use the name of
>one of th eauthors in the draft name... however, we see that other
>individual submissions are allowed to fabricate ID lables that do not
>reflect any of the authors or any WG.  e.g.
>
>draft-ymbk-downref-03.txt
>draft-kolkman-dnsext-dnssec-in-band-rollover-00

There are also some drafts by someone called "manyfolks":

   draft-manyfolks-sipping-ToIP-01.txt
   draft-manyfolks-nsis-nslp-QSpec-00.txt
   draft-ietf-sip-manyfolks-resource-07.txt

Bob


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul 30 13:55:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21577;
	Fri, 30 Jul 2004 13:55:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bqbe2-0003SO-6G; Fri, 30 Jul 2004 13:58:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BqbZg-0002yU-6g; Fri, 30 Jul 2004 13:53:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BqbSv-0008UO-RU
	for ietf@megatron.ietf.org; Fri, 30 Jul 2004 13:46:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21272
	for <ietf@ietf.org>; Fri, 30 Jul 2004 13:46:44 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BqbVA-0003Ks-5s
	for ietf@ietf.org; Fri, 30 Jul 2004 13:49:07 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i6UHjgZ28225;
	Fri, 30 Jul 2004 10:45:42 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200407301745.i6UHjgZ28225@boreas.isi.edu>
To: falk@ISI.EDU (Aaron Falk)
Date: Fri, 30 Jul 2004 10:45:42 -0700 (PDT)
In-Reply-To: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu> from "Aaron Falk"
	at Jul 20, 2004 09:20:54 PM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: bmanning
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Cc: Mark Allman <mallman@icir.org>, ietf@ietf.org,
        Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: survey on Friday IETF sessions
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit


perhaps the reason there has not been more participation in your survey is
associated w/ the following:

"A problem occurred in a Python script. Here is the sequence of function calls leading up to the error, in the order they occurred."

this error could be due to the fact that I did not attend Seoul but did attned MPLS and will attend
SD.  in any case, here is a data point:

I will be in SD the friday,saturday,sunday -PRIOR- to the offical IETF meeting to attend other,
ancillery mtgs that can not be held (for whatever reasons) during the IETF week.  Depending on the
scheduling of the WG's of interest, I'd be just as happy arriving in SD on the Wed during IETF and
staying through the trailing  wkend, holding the ancillery mtgs of interest then.

that said, most corporate travel folks don't mind sending folks a few days early (there are plausable
reasons for this) - it is -MUCH- harder to justify staying around -AFTER- the conference has ended.

YMMV.

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

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Fri Jul 30 23:14:17 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18765;
	Fri, 30 Jul 2004 23:14:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BqkMX-0001pS-Ld; Fri, 30 Jul 2004 23:16:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BqkGa-0005bC-Vw; Fri, 30 Jul 2004 23:10:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bqk9f-0003ow-GA
	for ietf@megatron.ietf.org; Fri, 30 Jul 2004 23:03:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18451
	for <ietf@ietf.org>; Fri, 30 Jul 2004 23:03:24 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BqkC0-0001ha-Vx
	for ietf@ietf.org; Fri, 30 Jul 2004 23:05:54 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 2980961B8E; Sat, 31 Jul 2004 05:02:55 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 13003-06; Sat, 31 Jul 2004 05:02:54 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id 991EE61B8F; Sat, 31 Jul 2004 05:02:49 +0200 (CEST)
Date: Sat, 31 Jul 2004 04:59:45 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Bob Hinden <bob.hinden@nokia.com>, Bill Manning <bmanning@ISI.EDU>
Message-ID: <525291F319CF8E84A3FE89BE@B50854F0A9192E8EC6CDA126>
In-Reply-To: <4.3.2.7.2.20040730092746.01a4f3e0@mailhost.iprg.nokia.com>
References: <D6B102EB643A6E67C4FC39C2@[10.0.0.9]>
	<4.3.2.7.2.20040730092746.01a4f3e0@mailhost.iprg.nokia.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Naming convention for a WG I-D that returns to
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit

hm.... do you think Olaf Kolkman has misspelled his name, or what?

and draft-ietf-sip-manyfolks is *formally* correct.

draft-ymbk has tradition, but it's likely to be crushed under the wheel of 
procedural correctness once the present batch is gone.

I don't know whether stopping "manyfolks" is right or not.

                 harald

--On 30. juli 2004 09:34 -0700 Bob Hinden <bob.hinden@nokia.com> wrote:

> Bill,
>
> At 03:46 AM 7/30/2004, Bill Manning wrote:
>
>> clearly different rules apply, depending on whom makes the submission.
>>
>> for example, several individual submissions were made before this
>> IETF and we (the authors) were told that we -MUST- use the name of
>> one of th eauthors in the draft name... however, we see that other
>> individual submissions are allowed to fabricate ID lables that do not
>> reflect any of the authors or any WG.  e.g.
>>
>> draft-ymbk-downref-03.txt
>> draft-kolkman-dnsext-dnssec-in-band-rollover-00
>
> There are also some drafts by someone called "manyfolks":
>
>    draft-manyfolks-sipping-ToIP-01.txt
>    draft-manyfolks-nsis-nslp-QSpec-00.txt
>    draft-ietf-sip-manyfolks-resource-07.txt
>
> Bob
>
>
>





_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Sat Jul 31 05:23:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16692;
	Sat, 31 Jul 2004 05:23:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bqq8F-0005v6-6O; Sat, 31 Jul 2004 05:26:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bqq3N-0002TK-58; Sat, 31 Jul 2004 05:21:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bqq2k-0002Jk-2J
	for ietf@megatron.ietf.org; Sat, 31 Jul 2004 05:20:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16632
	for <ietf@ietf.org>; Sat, 31 Jul 2004 05:20:39 -0400 (EDT)
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bqq59-0005tF-RD
	for ietf@ietf.org; Sat, 31 Jul 2004 05:23:12 -0400
Received: from [80.125.78.232] (helo=jfc.jefsey.com)
	by montage.altserver.com with esmtp (Exim 4.34) id 1Bqq2c-00085f-SH
	for ietf@ietf.org; Sat, 31 Jul 2004 02:20:35 -0700
Message-Id: <6.1.2.0.2.20040731110208.029b7730@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Sat, 31 Jul 2004 11:19:23 +0200
To: ietf@ietf.org
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <525291F319CF8E84A3FE89BE@B50854F0A9192E8EC6CDA126>
References: <D6B102EB643A6E67C4FC39C2@[10.0.0.9]>
	<4.3.2.7.2.20040730092746.01a4f3e0@mailhost.iprg.nokia.com>
	<525291F319CF8E84A3FE89BE@B50854F0A9192E8EC6CDA126>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Subject: Re: Naming convention for a WG I-D that returns to
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8

What about an information draft reporting on the results of the work of an 
existing organization or project? Can it use the name of the organization 
and only quote as authors the actual writers? where/holw should the 
organization be introduced? Is there any difference if the draft is not for 
information?
thank you. jfc

PS. Can someone tell me which RFC says that a draft must include a security 
part?. thank you;

At 04:59 31/07/2004, Harald Tveit Alvestrand wrote:
>hm.... do you think Olaf Kolkman has misspelled his name, or what?
>
>and draft-ietf-sip-manyfolks is *formally* correct.
>
>draft-ymbk has tradition, but it's likely to be crushed under the wheel of 
>procedural correctness once the present batch is gone.
>
>I don't know whether stopping "manyfolks" is right or not.
>
>                 harald
>
>--On 30. juli 2004 09:34 -0700 Bob Hinden <bob.hinden@nokia.com> wrote:
>
>>Bill,
>>
>>At 03:46 AM 7/30/2004, Bill Manning wrote:
>>
>>>clearly different rules apply, depending on whom makes the submission.
>>>
>>>for example, several individual submissions were made before this
>>>IETF and we (the authors) were told that we -MUST- use the name of
>>>one of th eauthors in the draft name... however, we see that other
>>>individual submissions are allowed to fabricate ID lables that do not
>>>reflect any of the authors or any WG.  e.g.
>>>
>>>draft-ymbk-downref-03.txt
>>>draft-kolkman-dnsext-dnssec-in-band-rollover-00
>>
>>There are also some drafts by someone called "manyfolks":
>>
>>    draft-manyfolks-sipping-ToIP-01.txt
>>    draft-manyfolks-nsis-nslp-QSpec-00.txt
>>    draft-ietf-sip-manyfolks-resource-07.txt
>>
>>Bob
>>
>>
>
>
>
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf
>


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Sat Jul 31 07:07:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21347;
	Sat, 31 Jul 2004 07:07:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bqrkf-000758-Fb; Sat, 31 Jul 2004 07:10:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BqrgW-00051b-J9; Sat, 31 Jul 2004 07:05:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BqrfM-0004qy-Gp
	for ietf@megatron.ietf.org; Sat, 31 Jul 2004 07:04:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21277
	for <ietf@ietf.org>; Sat, 31 Jul 2004 07:04:37 -0400 (EDT)
Received: from [199.239.208.244] (helo=199.239.208.244)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bqrhm-000733-2q
	for ietf@ietf.org; Sat, 31 Jul 2004 07:07:11 -0400
Received: from [24.239.105.13] (helo=[10.0.131.11])
	by 199.239.208.244 with asmtp (Exim 3.36 #1)
	id 1Bqrei-0002V1-00; Sat, 31 Jul 2004 07:04:00 -0400
Message-ID: <410B7C94.1030207@servanttechnology.com>
Date: Sat, 31 Jul 2004 07:03:48 -0400
From: Sal Mangiapane <salm@servanttechnology.com>
Organization: Servant Technology, Inc.
User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
References: <D6B102EB643A6E67C4FC39C2@[10.0.0.9]>	<4.3.2.7.2.20040730092746.01a4f3e0@mailhost.iprg.nokia.com>	<525291F319CF8E84A3FE89BE@B50854F0A9192E8EC6CDA126>
	<6.1.2.0.2.20040731110208.029b7730@mail.jefsey.com>
In-Reply-To: <6.1.2.0.2.20040731110208.029b7730@mail.jefsey.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Naming convention for a WG I-D that returns to
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: salm@servanttechnology.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit

> PS. Can someone tell me which RFC says that a draft must include a 
> security part?. thank you;

RFC2223 section 9

Sal

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Sat Jul 31 08:47:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24927;
	Sat, 31 Jul 2004 08:47:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BqtJW-0008Gp-0s; Sat, 31 Jul 2004 08:50:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BqtDt-0004we-HE; Sat, 31 Jul 2004 08:44:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BqtC1-0004S1-Js
	for ietf@megatron.ietf.org; Sat, 31 Jul 2004 08:42:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24695
	for <ietf@ietf.org>; Sat, 31 Jul 2004 08:42:28 -0400 (EDT)
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BqtES-0008C3-BL
	for ietf@ietf.org; Sat, 31 Jul 2004 08:45:01 -0400
Received: from [80.125.78.232] (helo=jfc.jefsey.com)
	by montage.altserver.com with esmtp (Exim 4.34)
	id 1BqtBt-0005Su-Rj; Sat, 31 Jul 2004 05:42:22 -0700
Message-Id: <6.1.2.0.2.20040731142932.0280a050@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Sat, 31 Jul 2004 14:36:32 +0200
To: salm@servanttechnology.com
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <410B7C94.1030207@servanttechnology.com>
References: <D6B102EB643A6E67C4FC39C2@[10.0.0.9]>
	<4.3.2.7.2.20040730092746.01a4f3e0@mailhost.iprg.nokia.com>
	<525291F319CF8E84A3FE89BE@B50854F0A9192E8EC6CDA126>
	<6.1.2.0.2.20040731110208.029b7730@mail.jefsey.com>
	<410B7C94.1030207@servanttechnology.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: ietf@ietf.org
Subject: Re: Naming convention for a WG I-D that returns to
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

At 13:03 31/07/2004, Sal Mangiapane wrote:
>>PS. Can someone tell me which RFC says that a draft must include a 
>>security part?. thank you;
>
>RFC2223 section 9
>Sal

Thank you. I was also looking for an RFC - if any -which documents why. To 
know what would be the proper process to introduce a comparable  addition 
to the drafts format.
jfc  


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Sat Jul 31 09:14:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26477;
	Sat, 31 Jul 2004 09:14:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bqtjp-0000FJ-5E; Sat, 31 Jul 2004 09:17:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bqtex-0002Vt-Mw; Sat, 31 Jul 2004 09:12:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bqtdh-00029z-RZ
	for ietf@megatron.ietf.org; Sat, 31 Jul 2004 09:11:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26311
	for <ietf@ietf.org>; Sat, 31 Jul 2004 09:11:03 -0400 (EDT)
Received: from [199.239.208.244] (helo=199.239.208.244)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bqtg6-0000C7-Pw
	for ietf@ietf.org; Sat, 31 Jul 2004 09:13:38 -0400
Received: from [24.239.105.13] (helo=[10.0.131.11])
	by 199.239.208.244 with asmtp (Exim 3.36 #1)
	id 1Bqtd7-0003nq-00; Sat, 31 Jul 2004 09:10:29 -0400
Message-ID: <410B9A40.3040800@servanttechnology.com>
Date: Sat, 31 Jul 2004 09:10:24 -0400
From: Sal Mangiapane <salm@servanttechnology.com>
Organization: Servant Technology, Inc.
User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
References: <D6B102EB643A6E67C4FC39C2@[10.0.0.9]>
	<4.3.2.7.2.20040730092746.01a4f3e0@mailhost.iprg.nokia.com>
	<525291F319CF8E84A3FE89BE@B50854F0A9192E8EC6CDA126>
	<6.1.2.0.2.20040731110208.029b7730@mail.jefsey.com>
	<410B7C94.1030207@servanttechnology.com>
	<6.1.2.0.2.20040731142932.0280a050@mail.jefsey.com>
In-Reply-To: <6.1.2.0.2.20040731142932.0280a050@mail.jefsey.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Naming convention for a WG I-D that returns to
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: salm@servanttechnology.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit

> Thank you. I was also looking for an RFC - if any -which documents why. 

There is RFC3552 which is the Security Considerations Best Practices but 
it doesn't answer the WHY question.

Sal

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


From ietf-bounces@ietf.org  Sat Jul 31 12:34:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04761;
	Sat, 31 Jul 2004 12:34:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BqwrE-0002KW-6f; Sat, 31 Jul 2004 12:37:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bqwio-0001ah-O7; Sat, 31 Jul 2004 12:28:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bqwdc-0000r0-Ly
	for ietf@megatron.ietf.org; Sat, 31 Jul 2004 12:23:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04424
	for <ietf@ietf.org>; Sat, 31 Jul 2004 12:23:09 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bqwg5-0002Do-CT
	for ietf@ietf.org; Sat, 31 Jul 2004 12:25:46 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 6B5CD61BB4; Sat, 31 Jul 2004 18:22:39 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 26309-09; Sat, 31 Jul 2004 18:22:38 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id A173661B7E; Sat, 31 Jul 2004 18:22:35 +0200 (CEST)
Date: Sat, 31 Jul 2004 07:59:42 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>, ietf@ietf.org
Message-ID: <0176FA1F2F3F11797AC35832@B50854F0A9192E8EC6CDA126>
In-Reply-To: <6.1.2.0.2.20040731110208.029b7730@mail.jefsey.com>
References: <D6B102EB643A6E67C4FC39C2@[10.0.0.9]>
	<4.3.2.7.2.20040730092746.01a4f3e0@mailhost.iprg.nokia.com>
	<525291F319CF8E84A3FE89BE@B50854F0A9192E8EC6CDA126>
	<6.1.2.0.2.20040731110208.029b7730@mail.jefsey.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Subject: Re: Naming convention for a WG I-D that returns to
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit



--On 31. juli 2004 11:19 +0200 "JFC (Jefsey) Morfin" <jefsey@jefsey.com> 
wrote:

> What about an information draft reporting on the results of the work of
> an existing organization or project? Can it use the name of the
> organization and only quote as authors the actual writers?

that would require giving the secretariat a list of "acceptable" 
organizations - and some idea of when someone should be allowed to speak 
for them or not. We started down that route in the past, and decided not to 
go there any more.



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


