
From wwwrun@core3.amsl.com  Tue Feb  1 19:01:49 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 549B13A712D; Tue,  1 Feb 2011 19:01:49 -0800 (PST)
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: IETF 80 - Meeting Information 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110202030149.549B13A712D@core3.amsl.com>
Date: Tue,  1 Feb 2011 19:01:49 -0800 (PST)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 03:01:49 -0000

80th IETF Meeting
Prague, Czech Republic
March 27 - April 1, 2011
Host: CZ.NIC

1.  Registration
2.  NEW: Companion Program
3.  Visas & Letters of Invitation
4.  Accommodations and Transportation
5.  Meeting Wiki

1. Registration
	Register online at:
	http://www.ietf.org/meetings/80/

2.  Companion Program
	If you are traveling with a friend or family member over 18 years
	of age you can register them for the IETF Companion Program for
	only USD 15.00 

	Benefits include:
	- A special welcome reception for companions from 16:30-1700 on
	Sunday, 27 March
	- Ability to attend the official Welcome Reception from 1700-1900
	on Sunday, 27 March
	- A distinctive meeting badge that grants access to the venue
	(not to be used to attend working sessions)
	- Participation in a separate companion email list if you choose
	to help communicate and make plans with other IETF Companions.

	You can register your companion at any time via the IETF website
	or onsite at the meeting.

3. Visas & Letters of Invitation: 
	The Czech Republic has adopted the EU migration and visa policy
	principles and is about to complete the harmonization of its
	policies with the law of the European Communities.

	A list of countries, whose citizens need no visa to the Czech
	Republic, is available here:
	http://www.mzv.cz/jnp/en/information_for_aliens/list_of_states_whose_citizens_are_exempt/index.html

	For more detailed information please contact the diplomatic
	mission of the relevant country - their list sorted in the
	alphabetical order is available at:
	http://www.mzv.cz/jnp/en/information_for_aliens/local_competency_of_dm_in_processing/index.html
4.  Accommodations and Transportation
	Reservations Cut off Date: 9 March 2011 (Hilton), 11 March 2011
	(Sheraton and InterContinental).

	For additional information on rates and policies, please visit:
	http://www.ietf.org/meeting/80/hotel.html

5.  Meeting Wiki
	The IETF 80 meeting wiki (Your Wiki) has been created for the
	attendees of IETF 80 meeting to exchange information. The wiki
	uses DokuWiki software and a users guide can be found at: 
	http://www.dokuwiki.org/dokuwiki

	Your IETF 80 (Prague) wiki can be found here: 
	https://www.ietf.org/registration/MeetingWiki/wiki/ietf80
	and is also accessible from the Prague meeting page on the IETF
	website.

Only 51 days until the Prague IETF!


From jhutz@cmu.edu  Tue Feb  1 21:18:19 2011
Return-Path: <jhutz@cmu.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B6603A6BBB for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 21:18:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.518
X-Spam-Level: 
X-Spam-Status: No, score=-106.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9+uTabyvQN6y for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 21:18:18 -0800 (PST)
Received: from smtp03.srv.cs.cmu.edu (SMTP03.SRV.CS.CMU.EDU [128.2.217.198]) by core3.amsl.com (Postfix) with ESMTP id 190E93A6B08 for <wgchairs@ietf.org>; Tue,  1 Feb 2011 21:18:17 -0800 (PST)
Received: from MINBAR.FAC.CS.CMU.EDU (MINBAR.FAC.CS.CMU.EDU [128.2.216.42]) (authenticated bits=0) by smtp03.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id p125LYqn015869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2011 00:21:34 -0500 (EST)
Date: Wed, 02 Feb 2011 00:21:34 -0500
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Joe Touch <touch@isi.edu>, Carsten Bormann <cabo@tzi.org>
Subject: Re: Canonical RFC formatting
Message-ID: <CCE7200FB4688552E312C3CA@minbar.fac.cs.cmu.edu>
In-Reply-To: <31354_1296066632_p0QIUVD2001797_4D406822.5020402@isi.edu>
References: <D10C8A96-81B7-4BA6-B672-442A892D135F@RiverOnce.com> ,	<C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767EC@DC-US1MBEX4.global.avaya.com> <4D4055D4.2070804@cisco.com> <4D405C1E.80604@isi.edu>	<58A43A73-5FD3-4A75-A223-29B24913C34E@tzi.org> <31354_1296066632_p0QIUVD2001797_4D406822.5020402@isi.edu>
X-Mailer: Mulberry/4.0.8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: mimedefang-cmuscs on 128.2.217.198
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 05:18:19 -0000

--On Wednesday, January 26, 2011 10:29:54 AM -0800 Joe Touch 
<touch@isi.edu> wrote:

>
>
> On 1/26/2011 10:21 AM, Carsten Bormann wrote:
>> On Jan 26, 2011, at 18:38, Joe Touch wrote:
>>
>>> The tool could probably be modified to accept .xml and turn it into
>>> .txt, but that seems like a tool issue, not a "canonical formatting"
>>> issue.
>>
>> I don't think so, because then you wouldn't have submitted the legal
>> boilerplate.
>
> FWIW, that can be fixed on the confirmation page, where the text output
> including the legal boilerplate could appear and require positive
> confirmation.

That seems OK for a document like draft-arkko-dual-stack-extra-lite-03.txt, 
which one recent review described as "a very brief (8-page) document", or 
for a document like RFC347.

I worry, though, that the submission process might time out while the 
author verified correct compilation on a document like RFC5661.

More seriously, I also worry that the author is more likely to just click 
through such a confirmation, rather than actually verifying the correctness 
of the generated document.  Legal questions aside, this is a problem when 
the generated document is the one that will be considered "authoritative" 
if there is any discrepancy between versions.  Better IMHO to insist that 
the author submit the authoritative form, along with whatever alternates 
are desired.


FWIW, I completely agree with Joe Hildebrand on the question of moving to 
UTF-8 (which seems like a no-brainer), and on elimination of fixed page 
breaks.  Not so much on allowing 10000-character lines or generated HTML 
with 10x as much tags as content.

-- Jeff

From touch@isi.edu  Tue Feb  1 22:32:26 2011
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23AB23A7015 for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 22:32:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.496
X-Spam-Level: 
X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vbk6qz-+uimX for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 22:32:24 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 3C2663A6E77 for <wgchairs@ietf.org>; Tue,  1 Feb 2011 22:32:23 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-81-169.lsanca.dsl-w.verizon.net [71.105.81.169]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p126ZFAa017469 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 1 Feb 2011 22:35:25 -0800 (PST)
Message-ID: <4D48FB22.7010106@isi.edu>
Date: Tue, 01 Feb 2011 22:35:14 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: Canonical RFC formatting
References: <D10C8A96-81B7-4BA6-B672-442A892D135F@RiverOnce.com> , <C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767EC@DC-US1MBEX4.global.avaya.com> <4D4055D4.2070804@cisco.com> <4D405C1E.80604@isi.edu>	<58A43A73-5FD3-4A75-A223-29B24913C34E@tzi.org> <31354_1296066632_p0QIUVD2001797_4D406822.5020402@isi.edu> <CCE7200FB4688552E312C3CA@minbar.fac.cs.cmu.edu>
In-Reply-To: <CCE7200FB4688552E312C3CA@minbar.fac.cs.cmu.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 06:32:27 -0000

Hi, Jeff,

On 2/1/2011 9:21 PM, Jeffrey Hutzelman wrote:
> --On Wednesday, January 26, 2011 10:29:54 AM -0800 Joe Touch
> <touch@isi.edu> wrote:
>
>>
>>
>> On 1/26/2011 10:21 AM, Carsten Bormann wrote:
>>> On Jan 26, 2011, at 18:38, Joe Touch wrote:
>>>
>>>> The tool could probably be modified to accept .xml and turn it into
>>>> .txt, but that seems like a tool issue, not a "canonical formatting"
>>>> issue.
>>>
>>> I don't think so, because then you wouldn't have submitted the legal
>>> boilerplate.
>>
>> FWIW, that can be fixed on the confirmation page, where the text output
>> including the legal boilerplate could appear and require positive
>> confirmation.
>
> That seems OK for a document like
> draft-arkko-dual-stack-extra-lite-03.txt, which one recent review
> described as "a very brief (8-page) document", or for a document like
> RFC347.
>
> I worry, though, that the submission process might time out while the
> author verified correct compilation on a document like RFC5661.

We have a two phase process right now. That can be part of it, i.e., you 
submit, it compiles off-line, then emails you only when it's ready to 
confirm.

> More seriously, I also worry that the author is more likely to just
> click through such a confirmation, rather than actually verifying the
> correctness of the generated document.

They do that now. People cut/paste without reading things. They generate 
the TXT without reading it either.

 > Legal questions aside, this is a
> problem when the generated document is the one that will be considered
> "authoritative" if there is any discrepancy between versions. Better
> IMHO to insist that the author submit the authoritative form, along with
> whatever alternates are desired.

I'm not sure what "authoritative" means for drafts. They're drafts, 
after all ;-) IMO, integrating the on-line version with the submission 
process just makes it easier for the author - they still can and do use 
automated tools - some online -- and they can and do submit txt that 
they haven't checked.

IMO, providing a one-stop submission process just makes it less obscure 
as a process. I see no reason we require the knowledge of magical 
incantations to submit a doc.

(I'd be all for .doc->.txt too, if I could figure out how to automate 
it, i.e., .doc->.prn->.txt, where the last step is the tool I wrote and 
*is* already online)

> FWIW, I completely agree with Joe Hildebrand on the question of moving
> to UTF-8 (which seems like a no-brainer), and on elimination of fixed
> page breaks. Not so much on allowing 10000-character lines or generated
> HTML with 10x as much tags as content.

I was involved in some of the UTF8 discussions of the past. My challenge is:

	- try to read the txt on a variety of currently common devices
	if most render UTF8 fine, then let's change things

The last time I checked, UTF8 didn't work in Windows; I just checked 
again with Win7: the default text reader - Wordpad - changes fonts 
mid-stream when it hits such chars, and Emacs doesn't work either.

I also just checked on an iPhone4 and an iPad, and it doesn't work there 
either.

I'm all for whatever new format works in most of the most common places, 
but knocking out Windows' default reader, an iPhone, and an iPad, and my 
conclusion remains that it's not ready for prime time.

We can continue that on rfc-interest. This isn't a new issue; I just 
wanted to give the current state of things.

Joe


From yaronf.ietf@gmail.com  Tue Feb  1 22:53:34 2011
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F46F3A6E11 for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 22:53:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YYKe62J7C04k for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 22:53:32 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 460923A7004 for <wgchairs@ietf.org>; Tue,  1 Feb 2011 22:53:31 -0800 (PST)
Received: by wyf23 with SMTP id 23so7808835wyf.31 for <wgchairs@ietf.org>; Tue, 01 Feb 2011 22:56:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:date:subject:message-id:from:to:cc:content-type :content-transfer-encoding; bh=UPqJzIYOtGTS46jPZmRqFn1w7RMqXh51XBKXbCVRlAw=; b=Dl+sMV3+tkLo86KoqY0YhA2ryldjM2iSeCnTHD7cpJcJKYbu87TY1dzln+7T671AJc AGg6/+/Lol7SuIdY9zlQFA6+I+i7CB5mQHiPHRGRzGLIxQs/90L0dqtMurtDEVHRSqvu rds4fnF7Y4TMaHZg/FV7BZgSu2bLSr0uin4/g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:subject:message-id:from:to:cc:content-type :content-transfer-encoding; b=ZG/8iYF0YsX8MH48h2XgP0xtUhFptc2pPmZOp40PQT7J4Ewlg2Spg4GTa8j/NZvOLS PQI6St3cTsJKOHlBtAR19sBarXuc9ylqp6sRwfaen/RNzNaPAPD3D3AoKZvyHUGvLccJ +q7OOl26LgfLsNvlabW8JylJVsbsFuN6eWMts=
Received: by 10.216.164.14 with SMTP id b14mr9471505wel.33.1296629809392; Tue, 01 Feb 2011 22:56:49 -0800 (PST)
Received: from localhost ([80.250.146.47]) by mx.google.com with ESMTPS id o33sm11921569wej.13.2011.02.01.22.56.46 (version=SSLv3 cipher=RC4-MD5); Tue, 01 Feb 2011 22:56:48 -0800 (PST)
Date: Wed, 02 Feb 2011 08:56:38 +0200
Subject: Re: Canonical RFC formatting
Message-ID: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: Joe Touch <touch@isi.edu>, Jeffrey Hutzelman <jhutz@cmu.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 06:53:34 -0000

SGkgSm9lLCBjYW4geW91IGNsYXJpZnkgd2hhdCBkbyB5b3UgbWVhbiBieSAiZG9lcyBub3Qgc3Vw
cG9ydCBVVEYtOD8gSSBhbSBjb21wb3NpbmcgdGhpcyBtYWlsIG9uIGFuIEFuZHJvaWQgcGhvbmUg
dGhhdCBzdXBwb3J0cyBIZWJyZXcganVzdCBmaW5lLCBJLmUuIFVURi04IHdpdGggTFRSIHJlbmRl
cmluZyAuIEFuZCBzbyBkbyBhbGwgY3VycmVudCBwbGF0Zm9ybXMgSSBhbSBmYW1pbGlhciB3aXRo
LgoKVGhhbmtzLAogICAgICBZYXJvbgoKCkpvZSBUb3VjaCA8dG91Y2hAaXNpLmVkdT4gd3JvdGU6
Cgo+SGksIEplZmYsCj4KPk9uIDIvMS8yMDExIDk6MjEgUE0sIEplZmZyZXkgSHV0emVsbWFuIHdy
b3RlOgo+PiAtLU9uIFdlZG5lc2RheSwgSmFudWFyeSAyNiwgMjAxMSAxMDoyOTo1NCBBTSAtMDgw
MCBKb2UgVG91Y2gKPj4gPHRvdWNoQGlzaS5lZHU+IHdyb3RlOgo+Pgo+Pj4KPj4+Cj4+PiBPbiAx
LzI2LzIwMTEgMTA6MjEgQU0sIENhcnN0ZW4gQm9ybWFubiB3cm90ZToKPj4+PiBPbiBKYW4gMjYs
IDIwMTEsIGF0IDE4OjM4LCBKb2UgVG91Y2ggd3JvdGU6Cj4+Pj4KPj4+Pj4gVGhlIHRvb2wgY291
bGQgcHJvYmFibHkgYmUgbW9kaWZpZWQgdG8gYWNjZXB0IC54bWwgYW5kIHR1cm4gaXQgaW50bwo+
Pj4+PiAudHh0LCBidXQgdGhhdCBzZWVtcyBsaWtlIGEgdG9vbCBpc3N1ZSwgbm90IGEgImNhbm9u
aWNhbCBmb3JtYXR0aW5nIgo+Pj4+PiBpc3N1ZS4KPj4+Pgo+Pj4+IEkgZG9uJ3QgdGhpbmsgc28s
IGJlY2F1c2UgdGhlbiB5b3Ugd291bGRuJ3QgaGF2ZSBzdWJtaXR0ZWQgdGhlIGxlZ2FsCj4+Pj4g
Ym9pbGVycGxhdGUuCj4+Pgo+Pj4gRldJVywgdGhhdCBjYW4gYmUgZml4ZWQgb24gdGhlIGNvbmZp
cm1hdGlvbiBwYWdlLCB3aGVyZSB0aGUgdGV4dCBvdXRwdXQKPj4+IGluY2x1ZGluZyB0aGUgbGVn
YWwgYm9pbGVycGxhdGUgY291bGQgYXBwZWFyIGFuZCByZXF1aXJlIHBvc2l0aXZlCj4+PiBjb25m
aXJtYXRpb24uCj4+Cj4+IFRoYXQgc2VlbXMgT0sgZm9yIGEgZG9jdW1lbnQgbGlrZQo+PiBkcmFm
dC1hcmtrby1kdWFsLXN0YWNrLWV4dHJhLWxpdGUtMDMudHh0LCB3aGljaCBvbmUgcmVjZW50IHJl
dmlldwo+PiBkZXNjcmliZWQgYXMgImEgdmVyeSBicmllZiAoOC1wYWdlKSBkb2N1bWVudCIsIG9y
IGZvciBhIGRvY3VtZW50IGxpa2UKPj4gUkZDMzQ3Lgo+Pgo+PiBJIHdvcnJ5LCB0aG91Z2gsIHRo
YXQgdGhlIHN1Ym1pc3Npb24gcHJvY2VzcyBtaWdodCB0aW1lIG91dCB3aGlsZSB0aGUKPj4gYXV0
aG9yIHZlcmlmaWVkIGNvcnJlY3QgY29tcGlsYXRpb24gb24gYSBkb2N1bWVudCBsaWtlIFJGQzU2
NjEuCj4KPldlIGhhdmUgYSB0d28gcGhhc2UgcHJvY2VzcyByaWdodCBub3cuIFRoYXQgY2FuIGJl
IHBhcnQgb2YgaXQsIGkuZS4sIHlvdSAKPnN1Ym1pdCwgaXQgY29tcGlsZXMgb2ZmLWxpbmUsIHRo
ZW4gZW1haWxzIHlvdSBvbmx5IHdoZW4gaXQncyByZWFkeSB0byAKPmNvbmZpcm0uCj4KPj4gTW9y
ZSBzZXJpb3VzbHksIEkgYWxzbyB3b3JyeSB0aGF0IHRoZSBhdXRob3IgaXMgbW9yZSBsaWtlbHkg
dG8ganVzdAo+PiBjbGljayB0aHJvdWdoIHN1Y2ggYSBjb25maXJtYXRpb24sIHJhdGhlciB0aGFu
IGFjdHVhbGx5IHZlcmlmeWluZyB0aGUKPj4gY29ycmVjdG5lc3Mgb2YgdGhlIGdlbmVyYXRlZCBk
b2N1bWVudC4KPgo+VGhleSBkbyB0aGF0IG5vdy4gUGVvcGxlIGN1dC9wYXN0ZSB3aXRob3V0IHJl
YWRpbmcgdGhpbmdzLiBUaGV5IGdlbmVyYXRlIAo+dGhlIFRYVCB3aXRob3V0IHJlYWRpbmcgaXQg
ZWl0aGVyLgo+Cj4gPiBMZWdhbCBxdWVzdGlvbnMgYXNpZGUsIHRoaXMgaXMgYQo+PiBwcm9ibGVt
IHdoZW4gdGhlIGdlbmVyYXRlZCBkb2N1bWVudCBpcyB0aGUgb25lIHRoYXQgd2lsbCBiZSBjb25z
aWRlcmVkCj4+ICJhdXRob3JpdGF0aXZlIiBpZiB0aGVyZSBpcyBhbnkgZGlzY3JlcGFuY3kgYmV0
d2VlbiB2ZXJzaW9ucy4gQmV0dGVyCj4+IElNSE8gdG8gaW5zaXN0IHRoYXQgdGhlIGF1dGhvciBz
dWJtaXQgdGhlIGF1dGhvcml0YXRpdmUgZm9ybSwgYWxvbmcgd2l0aAo+PiB3aGF0ZXZlciBhbHRl
cm5hdGVzIGFyZSBkZXNpcmVkLgo+Cj5JJ20gbm90IHN1cmUgd2hhdCAiYXV0aG9yaXRhdGl2ZSIg
bWVhbnMgZm9yIGRyYWZ0cy4gVGhleSdyZSBkcmFmdHMsIAo+YWZ0ZXIgYWxsIDstKSBJTU8sIGlu
dGVncmF0aW5nIHRoZSBvbi1saW5lIHZlcnNpb24gd2l0aCB0aGUgc3VibWlzc2lvbiAKPnByb2Nl
c3MganVzdCBtYWtlcyBpdCBlYXNpZXIgZm9yIHRoZSBhdXRob3IgLSB0aGV5IHN0aWxsIGNhbiBh
bmQgZG8gdXNlIAo+YXV0b21hdGVkIHRvb2xzIC0gc29tZSBvbmxpbmUgLS0gYW5kIHRoZXkgY2Fu
IGFuZCBkbyBzdWJtaXQgdHh0IHRoYXQgCj50aGV5IGhhdmVuJ3QgY2hlY2tlZC4KPgo+SU1PLCBw
cm92aWRpbmcgYSBvbmUtc3RvcCBzdWJtaXNzaW9uIHByb2Nlc3MganVzdCBtYWtlcyBpdCBsZXNz
IG9ic2N1cmUgCj5hcyBhIHByb2Nlc3MuIEkgc2VlIG5vIHJlYXNvbiB3ZSByZXF1aXJlIHRoZSBr
bm93bGVkZ2Ugb2YgbWFnaWNhbCAKPmluY2FudGF0aW9ucyB0byBzdWJtaXQgYSBkb2MuCj4KPihJ
J2QgYmUgYWxsIGZvciAuZG9jLT4udHh0IHRvbywgaWYgSSBjb3VsZCBmaWd1cmUgb3V0IGhvdyB0
byBhdXRvbWF0ZSAKPml0LCBpLmUuLCAuZG9jLT4ucHJuLT4udHh0LCB3aGVyZSB0aGUgbGFzdCBz
dGVwIGlzIHRoZSB0b29sIEkgd3JvdGUgYW5kIAo+KmlzKiBhbHJlYWR5IG9ubGluZSkKPgo+PiBG
V0lXLCBJIGNvbXBsZXRlbHkgYWdyZWUgd2l0aCBKb2UgSGlsZGVicmFuZCBvbiB0aGUgcXVlc3Rp
b24gb2YgbW92aW5nCj4+IHRvIFVURi04ICh3aGljaCBzZWVtcyBsaWtlIGEgbm8tYnJhaW5lciks
IGFuZCBvbiBlbGltaW5hdGlvbiBvZiBmaXhlZAo+PiBwYWdlIGJyZWFrcy4gTm90IHNvIG11Y2gg
b24gYWxsb3dpbmcgMTAwMDAtY2hhcmFjdGVyIGxpbmVzIG9yIGdlbmVyYXRlZAo+PiBIVE1MIHdp
dGggMTB4IGFzIG11Y2ggdGFncyBhcyBjb250ZW50Lgo+Cj5JIHdhcyBpbnZvbHZlZCBpbiBzb21l
IG9mIHRoZSBVVEY4IGRpc2N1c3Npb25zIG9mIHRoZSBwYXN0LiBNeSBjaGFsbGVuZ2UgaXM6Cj4K
PgktIHRyeSB0byByZWFkIHRoZSB0eHQgb24gYSB2YXJpZXR5IG9mIGN1cnJlbnRseSBjb21tb24g
ZGV2aWNlcwo+CWlmIG1vc3QgcmVuZGVyIFVURjggZmluZSwgdGhlbiBsZXQncyBjaGFuZ2UgdGhp
bmdzCj4KPlRoZSBsYXN0IHRpbWUgSSBjaGVja2VkLCBVVEY4IGRpZG4ndCB3b3JrIGluIFdpbmRv
d3M7IEkganVzdCBjaGVja2VkIAo+YWdhaW4gd2l0aCBXaW43OiB0aGUgZGVmYXVsdCB0ZXh0IHJl
YWRlciAtIFdvcmRwYWQgLSBjaGFuZ2VzIGZvbnRzIAo+bWlkLXN0cmVhbSB3aGVuIGl0IGhpdHMg
c3VjaCBjaGFycywgYW5kIEVtYWNzIGRvZXNuJ3Qgd29yayBlaXRoZXIuCj4KPkkgYWxzbyBqdXN0
IGNoZWNrZWQgb24gYW4gaVBob25lNCBhbmQgYW4gaVBhZCwgYW5kIGl0IGRvZXNuJ3Qgd29yayB0
aGVyZSAKPmVpdGhlci4KPgo+SSdtIGFsbCBmb3Igd2hhdGV2ZXIgbmV3IGZvcm1hdCB3b3JrcyBp
biBtb3N0IG9mIHRoZSBtb3N0IGNvbW1vbiBwbGFjZXMsIAo+YnV0IGtub2NraW5nIG91dCBXaW5k
b3dzJyBkZWZhdWx0IHJlYWRlciwgYW4gaVBob25lLCBhbmQgYW4gaVBhZCwgYW5kIG15IAo+Y29u
Y2x1c2lvbiByZW1haW5zIHRoYXQgaXQncyBub3QgcmVhZHkgZm9yIHByaW1lIHRpbWUuCj4KPldl
IGNhbiBjb250aW51ZSB0aGF0IG9uIHJmYy1pbnRlcmVzdC4gVGhpcyBpc24ndCBhIG5ldyBpc3N1
ZTsgSSBqdXN0IAo+d2FudGVkIHRvIGdpdmUgdGhlIGN1cnJlbnQgc3RhdGUgb2YgdGhpbmdzLgo+
Cj5Kb2UKPgo=


From touch@isi.edu  Tue Feb  1 23:18:25 2011
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59E8D3A6CAC for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 23:18:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IJ--1QUqsn-Q for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 23:18:23 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 51ABA3A7015 for <wgchairs@ietf.org>; Tue,  1 Feb 2011 23:18:23 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-81-169.lsanca.dsl-w.verizon.net [71.105.81.169]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p127LK6A023381 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 1 Feb 2011 23:21:30 -0800 (PST)
Message-ID: <4D4905EF.1060807@isi.edu>
Date: Tue, 01 Feb 2011 23:21:19 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Canonical RFC formatting
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>
In-Reply-To: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 07:18:25 -0000

On 2/1/2011 10:56 PM, Yaron Sheffer wrote:
> Hi Joe, can you clarify what do you mean by "does not support UTF-8?
> I am composing this mail on an Android phone that supports Hebrew
> just fine, I.e. UTF-8 with LTR rendering . And so do all current
> platforms I am familiar with.

I opened a UTF-8 file as an email attachment, and it displayed the UTF-8 
chars as garbage.

My metric is: open a .txt file, encoded in UTF-8, and see what happens.

Joe

> Joe Touch<touch@isi.edu>  wrote:
>
>> Hi, Jeff,
>>
>> On 2/1/2011 9:21 PM, Jeffrey Hutzelman wrote:
>>> --On Wednesday, January 26, 2011 10:29:54 AM -0800 Joe Touch
>>> <touch@isi.edu>  wrote:
>>>
>>>>
>>>>
>>>> On 1/26/2011 10:21 AM, Carsten Bormann wrote:
>>>>> On Jan 26, 2011, at 18:38, Joe Touch wrote:
>>>>>
>>>>>> The tool could probably be modified to accept .xml and turn it into
>>>>>> .txt, but that seems like a tool issue, not a "canonical formatting"
>>>>>> issue.
>>>>>
>>>>> I don't think so, because then you wouldn't have submitted the legal
>>>>> boilerplate.
>>>>
>>>> FWIW, that can be fixed on the confirmation page, where the text output
>>>> including the legal boilerplate could appear and require positive
>>>> confirmation.
>>>
>>> That seems OK for a document like
>>> draft-arkko-dual-stack-extra-lite-03.txt, which one recent review
>>> described as "a very brief (8-page) document", or for a document like
>>> RFC347.
>>>
>>> I worry, though, that the submission process might time out while the
>>> author verified correct compilation on a document like RFC5661.
>>
>> We have a two phase process right now. That can be part of it, i.e., you
>> submit, it compiles off-line, then emails you only when it's ready to
>> confirm.
>>
>>> More seriously, I also worry that the author is more likely to just
>>> click through such a confirmation, rather than actually verifying the
>>> correctness of the generated document.
>>
>> They do that now. People cut/paste without reading things. They generate
>> the TXT without reading it either.
>>
>>> Legal questions aside, this is a
>>> problem when the generated document is the one that will be considered
>>> "authoritative" if there is any discrepancy between versions. Better
>>> IMHO to insist that the author submit the authoritative form, along with
>>> whatever alternates are desired.
>>
>> I'm not sure what "authoritative" means for drafts. They're drafts,
>> after all ;-) IMO, integrating the on-line version with the submission
>> process just makes it easier for the author - they still can and do use
>> automated tools - some online -- and they can and do submit txt that
>> they haven't checked.
>>
>> IMO, providing a one-stop submission process just makes it less obscure
>> as a process. I see no reason we require the knowledge of magical
>> incantations to submit a doc.
>>
>> (I'd be all for .doc->.txt too, if I could figure out how to automate
>> it, i.e., .doc->.prn->.txt, where the last step is the tool I wrote and
>> *is* already online)
>>
>>> FWIW, I completely agree with Joe Hildebrand on the question of moving
>>> to UTF-8 (which seems like a no-brainer), and on elimination of fixed
>>> page breaks. Not so much on allowing 10000-character lines or generated
>>> HTML with 10x as much tags as content.
>>
>> I was involved in some of the UTF8 discussions of the past. My challenge is:
>>
>> 	- try to read the txt on a variety of currently common devices
>> 	if most render UTF8 fine, then let's change things
>>
>> The last time I checked, UTF8 didn't work in Windows; I just checked
>> again with Win7: the default text reader - Wordpad - changes fonts
>> mid-stream when it hits such chars, and Emacs doesn't work either.
>>
>> I also just checked on an iPhone4 and an iPad, and it doesn't work there
>> either.
>>
>> I'm all for whatever new format works in most of the most common places,
>> but knocking out Windows' default reader, an iPhone, and an iPad, and my
>> conclusion remains that it's not ready for prime time.
>>
>> We can continue that on rfc-interest. This isn't a new issue; I just
>> wanted to give the current state of things.
>>
>> Joe
>>

From lachlan.andrew@gmail.com  Tue Feb  1 23:26:59 2011
Return-Path: <lachlan.andrew@gmail.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BEC443A6C6C for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 23:26:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sLuDaHxevUtc for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 23:26:58 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 2813E3A6C00 for <wgchairs@ietf.org>; Tue,  1 Feb 2011 23:26:58 -0800 (PST)
Received: by iwc10 with SMTP id 10so838288iwc.31 for <wgchairs@ietf.org>; Tue, 01 Feb 2011 23:30:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=U1CKurguqxmoFw86lehvHKseqd3AQdOjeGzcXgj+1Xc=; b=qiZAmmiKxSkX/O+nxnUAZTKiSig7hh/hL2BJW0MwgoMxh7JRz4Ot25ufkmnr6Q7lKO i9FOA0Nr3ocFNaGsRHD6/CFZ4N1rJLt9JaRmog5RbPxEORJSY34VZRtv0eXMlRNJUklZ FbwQLPVGU1OqJCJEZT3oAvcKEavadc+ikAlj0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=TAsiVUB+3TtiHou1CvIfY9A8+ePpAXGjo5vVqTsfSU4nJ3dlxbf1Bo6pJSLezM2T4I iffMJV/uQXlnNuiUCi0ns1kQdQD0Y8tpHYU/L4bZ9ERWvogj2g+chRVLPvS8f6kwqOVx HTDrtWSpx2qJAuC8gi9w+5zMTcuAEBLtoxO0c=
Received: by 10.231.199.10 with SMTP id eq10mr9444294ibb.112.1296631816921; Tue, 01 Feb 2011 23:30:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.32.201 with HTTP; Tue, 1 Feb 2011 23:29:56 -0800 (PST)
In-Reply-To: <4D4905EF.1060807@isi.edu>
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com> <4D4905EF.1060807@isi.edu>
From: Lachlan Andrew <lachlan.andrew@gmail.com>
Date: Wed, 2 Feb 2011 18:29:56 +1100
Message-ID: <AANLkTi=9Dw_6d45K_YkbxV2ZrCWeF3UndJNvBJpW3A4-@mail.gmail.com>
Subject: Re: Canonical RFC formatting
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 07:26:59 -0000

Greetings Joe,

Could you circulate an example problematic attachment, to see how many
people have the problem?  May it depend on whether a particular
Windows installation is set up for UTF-8?

For example, if you choose not to install fonts with accents, then
those characters can't be displayed.  The same applies to reading
ASCII if you choose to install an OS without any ASCII fonts.

Just a thought...

Lachlan

On 2 February 2011 18:21, Joe Touch <touch@isi.edu> wrote:
>
>
> On 2/1/2011 10:56 PM, Yaron Sheffer wrote:
>>
>> Hi Joe, can you clarify what do you mean by "does not support UTF-8?
>> I am composing this mail on an Android phone that supports Hebrew
>> just fine, I.e. UTF-8 with LTR rendering . And so do all current
>> platforms I am familiar with.
>
> I opened a UTF-8 file as an email attachment, and it displayed the UTF-8
> chars as garbage.
>
> My metric is: open a .txt file, encoded in UTF-8, and see what happens.
>
> Joe
>
>> Joe Touch<touch@isi.edu> =A0wrote:
>>
>>> Hi, Jeff,
>>>
>>> On 2/1/2011 9:21 PM, Jeffrey Hutzelman wrote:
>>>>
>>>> --On Wednesday, January 26, 2011 10:29:54 AM -0800 Joe Touch
>>>> <touch@isi.edu> =A0wrote:
>>>>
>>>>>
>>>>>
>>>>> On 1/26/2011 10:21 AM, Carsten Bormann wrote:
>>>>>>
>>>>>> On Jan 26, 2011, at 18:38, Joe Touch wrote:
>>>>>>
>>>>>>> The tool could probably be modified to accept .xml and turn it into
>>>>>>> .txt, but that seems like a tool issue, not a "canonical formatting=
"
>>>>>>> issue.
>>>>>>
>>>>>> I don't think so, because then you wouldn't have submitted the legal
>>>>>> boilerplate.
>>>>>
>>>>> FWIW, that can be fixed on the confirmation page, where the text outp=
ut
>>>>> including the legal boilerplate could appear and require positive
>>>>> confirmation.
>>>>
>>>> That seems OK for a document like
>>>> draft-arkko-dual-stack-extra-lite-03.txt, which one recent review
>>>> described as "a very brief (8-page) document", or for a document like
>>>> RFC347.
>>>>
>>>> I worry, though, that the submission process might time out while the
>>>> author verified correct compilation on a document like RFC5661.
>>>
>>> We have a two phase process right now. That can be part of it, i.e., yo=
u
>>> submit, it compiles off-line, then emails you only when it's ready to
>>> confirm.
>>>
>>>> More seriously, I also worry that the author is more likely to just
>>>> click through such a confirmation, rather than actually verifying the
>>>> correctness of the generated document.
>>>
>>> They do that now. People cut/paste without reading things. They generat=
e
>>> the TXT without reading it either.
>>>
>>>> Legal questions aside, this is a
>>>> problem when the generated document is the one that will be considered
>>>> "authoritative" if there is any discrepancy between versions. Better
>>>> IMHO to insist that the author submit the authoritative form, along wi=
th
>>>> whatever alternates are desired.
>>>
>>> I'm not sure what "authoritative" means for drafts. They're drafts,
>>> after all ;-) IMO, integrating the on-line version with the submission
>>> process just makes it easier for the author - they still can and do use
>>> automated tools - some online -- and they can and do submit txt that
>>> they haven't checked.
>>>
>>> IMO, providing a one-stop submission process just makes it less obscure
>>> as a process. I see no reason we require the knowledge of magical
>>> incantations to submit a doc.
>>>
>>> (I'd be all for .doc->.txt too, if I could figure out how to automate
>>> it, i.e., .doc->.prn->.txt, where the last step is the tool I wrote and
>>> *is* already online)
>>>
>>>> FWIW, I completely agree with Joe Hildebrand on the question of moving
>>>> to UTF-8 (which seems like a no-brainer), and on elimination of fixed
>>>> page breaks. Not so much on allowing 10000-character lines or generate=
d
>>>> HTML with 10x as much tags as content.
>>>
>>> I was involved in some of the UTF8 discussions of the past. My challeng=
e
>>> is:
>>>
>>> =A0 =A0 =A0 =A0- try to read the txt on a variety of currently common d=
evices
>>> =A0 =A0 =A0 =A0if most render UTF8 fine, then let's change things
>>>
>>> The last time I checked, UTF8 didn't work in Windows; I just checked
>>> again with Win7: the default text reader - Wordpad - changes fonts
>>> mid-stream when it hits such chars, and Emacs doesn't work either.
>>>
>>> I also just checked on an iPhone4 and an iPad, and it doesn't work ther=
e
>>> either.
>>>
>>> I'm all for whatever new format works in most of the most common places=
,
>>> but knocking out Windows' default reader, an iPhone, and an iPad, and m=
y
>>> conclusion remains that it's not ready for prime time.
>>>
>>> We can continue that on rfc-interest. This isn't a new issue; I just
>>> wanted to give the current state of things.
>>>
>>> Joe
>>>
>



--=20
Lachlan Andrew=A0 Centre for Advanced Internet Architectures (CAIA)
Swinburne University of Technology, Melbourne, Australia
<http://caia.swin.edu.au/cv/landrew>
Ph +61 3 9214 4837

From joelja@bogus.com  Tue Feb  1 23:32:46 2011
Return-Path: <joelja@bogus.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FB6A3A6CAC for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 23:32:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.199
X-Spam-Level: 
X-Spam-Status: No, score=-102.199 tagged_above=-999 required=5 tests=[AWL=0.400, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aCarOMB+EI5f for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 23:32:45 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 79EF43A6C6C for <wgchairs@ietf.org>; Tue,  1 Feb 2011 23:32:44 -0800 (PST)
Received: from joelja-mac.lan (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p127ZxRL086754 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 07:36:00 GMT (envelope-from joelja@bogus.com)
Message-ID: <4D49095F.20702@bogus.com>
Date: Tue, 01 Feb 2011 23:35:59 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Canonical RFC formatting
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com> <4D4905EF.1060807@isi.edu>
In-Reply-To: <4D4905EF.1060807@isi.edu>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 07:32:46 -0000

On 2/1/11 11:21 PM, Joe Touch wrote:
> 
> 
> On 2/1/2011 10:56 PM, Yaron Sheffer wrote:
>> Hi Joe, can you clarify what do you mean by "does not support UTF-8?
>> I am composing this mail on an Android phone that supports Hebrew
>> just fine, I.e. UTF-8 with LTR rendering . And so do all current
>> platforms I am familiar with.
> 
> I opened a UTF-8 file as an email attachment, and it displayed the UTF-8
> chars as garbage.
> 
> My metric is: open a .txt file, encoded in UTF-8, and see what happens.

I opened several utf-8 text samples I have on the ipad and they rendered
reasonably well (except for amharic), including although of questionable
utility the braile sample. this was via the browsers rendering engine.

> Joe
> 
>> Joe Touch<touch@isi.edu>  wrote:
>>
>>> Hi, Jeff,
>>>
>>> On 2/1/2011 9:21 PM, Jeffrey Hutzelman wrote:
>>>> --On Wednesday, January 26, 2011 10:29:54 AM -0800 Joe Touch
>>>> <touch@isi.edu>  wrote:
>>>>
>>>>>
>>>>>
>>>>> On 1/26/2011 10:21 AM, Carsten Bormann wrote:
>>>>>> On Jan 26, 2011, at 18:38, Joe Touch wrote:
>>>>>>
>>>>>>> The tool could probably be modified to accept .xml and turn it into
>>>>>>> .txt, but that seems like a tool issue, not a "canonical formatting"
>>>>>>> issue.
>>>>>>
>>>>>> I don't think so, because then you wouldn't have submitted the legal
>>>>>> boilerplate.
>>>>>
>>>>> FWIW, that can be fixed on the confirmation page, where the text
>>>>> output
>>>>> including the legal boilerplate could appear and require positive
>>>>> confirmation.
>>>>
>>>> That seems OK for a document like
>>>> draft-arkko-dual-stack-extra-lite-03.txt, which one recent review
>>>> described as "a very brief (8-page) document", or for a document like
>>>> RFC347.
>>>>
>>>> I worry, though, that the submission process might time out while the
>>>> author verified correct compilation on a document like RFC5661.
>>>
>>> We have a two phase process right now. That can be part of it, i.e., you
>>> submit, it compiles off-line, then emails you only when it's ready to
>>> confirm.
>>>
>>>> More seriously, I also worry that the author is more likely to just
>>>> click through such a confirmation, rather than actually verifying the
>>>> correctness of the generated document.
>>>
>>> They do that now. People cut/paste without reading things. They generate
>>> the TXT without reading it either.
>>>
>>>> Legal questions aside, this is a
>>>> problem when the generated document is the one that will be considered
>>>> "authoritative" if there is any discrepancy between versions. Better
>>>> IMHO to insist that the author submit the authoritative form, along
>>>> with
>>>> whatever alternates are desired.
>>>
>>> I'm not sure what "authoritative" means for drafts. They're drafts,
>>> after all ;-) IMO, integrating the on-line version with the submission
>>> process just makes it easier for the author - they still can and do use
>>> automated tools - some online -- and they can and do submit txt that
>>> they haven't checked.
>>>
>>> IMO, providing a one-stop submission process just makes it less obscure
>>> as a process. I see no reason we require the knowledge of magical
>>> incantations to submit a doc.
>>>
>>> (I'd be all for .doc->.txt too, if I could figure out how to automate
>>> it, i.e., .doc->.prn->.txt, where the last step is the tool I wrote and
>>> *is* already online)
>>>
>>>> FWIW, I completely agree with Joe Hildebrand on the question of moving
>>>> to UTF-8 (which seems like a no-brainer), and on elimination of fixed
>>>> page breaks. Not so much on allowing 10000-character lines or generated
>>>> HTML with 10x as much tags as content.
>>>
>>> I was involved in some of the UTF8 discussions of the past. My
>>> challenge is:
>>>
>>>     - try to read the txt on a variety of currently common devices
>>>     if most render UTF8 fine, then let's change things
>>>
>>> The last time I checked, UTF8 didn't work in Windows; I just checked
>>> again with Win7: the default text reader - Wordpad - changes fonts
>>> mid-stream when it hits such chars, and Emacs doesn't work either.
>>>
>>> I also just checked on an iPhone4 and an iPad, and it doesn't work there
>>> either.
>>>
>>> I'm all for whatever new format works in most of the most common places,
>>> but knocking out Windows' default reader, an iPhone, and an iPad, and my
>>> conclusion remains that it's not ready for prime time.
>>>
>>> We can continue that on rfc-interest. This isn't a new issue; I just
>>> wanted to give the current state of things.
>>>
>>> Joe
>>>
> 


From touch@isi.edu  Tue Feb  1 23:32:53 2011
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 47F433A70F8 for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 23:32:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level: 
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[AWL=-0.502, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Afpg+HyTDCb5 for <wgchairs@core3.amsl.com>; Tue,  1 Feb 2011 23:32:51 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 14D6B3A6E88 for <wgchairs@ietf.org>; Tue,  1 Feb 2011 23:32:51 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-81-169.lsanca.dsl-w.verizon.net [71.105.81.169]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p127ZRnK025340 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 1 Feb 2011 23:35:37 -0800 (PST)
Message-ID: <4D49093E.3030809@isi.edu>
Date: Tue, 01 Feb 2011 23:35:26 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Lachlan Andrew <lachlan.andrew@gmail.com>
Subject: Re: Canonical RFC formatting
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com> <4D4905EF.1060807@isi.edu> <AANLkTi=9Dw_6d45K_YkbxV2ZrCWeF3UndJNvBJpW3A4-@mail.gmail.com>
In-Reply-To: <AANLkTi=9Dw_6d45K_YkbxV2ZrCWeF3UndJNvBJpW3A4-@mail.gmail.com>
Content-Type: multipart/mixed; boundary="------------000205020106020509070904"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 07:32:53 -0000

This is a multi-part message in MIME format.
--------------000205020106020509070904
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sure - it was the test that Paul Hoffman wrote a while back. Attached.

My claim is that, ****out of the box, the following systems should be 
able to read the attached file with no additional configuration or software:

- Windows
- Linux
- MacOS
- FreeBSD
- IOS (iPhone/iPad)
- Android
- Blackberry

I'm sure there are a few others that people would like to throw in, 
notably things like:
- Kindle
- Sony e-reader

Maybe some others too. Not sure. But that's the basic test as a start.

I can read .txt on all these (excepting the e-book readers, which 
require a txt to something converter) *right now*.

Again, we can take this over to rfc-i...

Joe



On 2/1/2011 11:29 PM, Lachlan Andrew wrote:
> Greetings Joe,
>
> Could you circulate an example problematic attachment, to see how many
> people have the problem?  May it depend on whether a particular
> Windows installation is set up for UTF-8?
>
> For example, if you choose not to install fonts with accents, then
> those characters can't be displayed.  The same applies to reading
> ASCII if you choose to install an OS without any ASCII fonts.
>
> Just a thought...
>
> Lachlan
>
> On 2 February 2011 18:21, Joe Touch<touch@isi.edu>  wrote:
>>
>>
>> On 2/1/2011 10:56 PM, Yaron Sheffer wrote:
>>>
>>> Hi Joe, can you clarify what do you mean by "does not support UTF-8?
>>> I am composing this mail on an Android phone that supports Hebrew
>>> just fine, I.e. UTF-8 with LTR rendering . And so do all current
>>> platforms I am familiar with.
>>
>> I opened a UTF-8 file as an email attachment, and it displayed the UTF-8
>> chars as garbage.
>>
>> My metric is: open a .txt file, encoded in UTF-8, and see what happens.
>>
>> Joe
>>
>>> Joe Touch<touch@isi.edu>    wrote:
>>>
>>>> Hi, Jeff,
>>>>
>>>> On 2/1/2011 9:21 PM, Jeffrey Hutzelman wrote:
>>>>>
>>>>> --On Wednesday, January 26, 2011 10:29:54 AM -0800 Joe Touch
>>>>> <touch@isi.edu>    wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On 1/26/2011 10:21 AM, Carsten Bormann wrote:
>>>>>>>
>>>>>>> On Jan 26, 2011, at 18:38, Joe Touch wrote:
>>>>>>>
>>>>>>>> The tool could probably be modified to accept .xml and turn it into
>>>>>>>> .txt, but that seems like a tool issue, not a "canonical formatting"
>>>>>>>> issue.
>>>>>>>
>>>>>>> I don't think so, because then you wouldn't have submitted the legal
>>>>>>> boilerplate.
>>>>>>
>>>>>> FWIW, that can be fixed on the confirmation page, where the text output
>>>>>> including the legal boilerplate could appear and require positive
>>>>>> confirmation.
>>>>>
>>>>> That seems OK for a document like
>>>>> draft-arkko-dual-stack-extra-lite-03.txt, which one recent review
>>>>> described as "a very brief (8-page) document", or for a document like
>>>>> RFC347.
>>>>>
>>>>> I worry, though, that the submission process might time out while the
>>>>> author verified correct compilation on a document like RFC5661.
>>>>
>>>> We have a two phase process right now. That can be part of it, i.e., you
>>>> submit, it compiles off-line, then emails you only when it's ready to
>>>> confirm.
>>>>
>>>>> More seriously, I also worry that the author is more likely to just
>>>>> click through such a confirmation, rather than actually verifying the
>>>>> correctness of the generated document.
>>>>
>>>> They do that now. People cut/paste without reading things. They generate
>>>> the TXT without reading it either.
>>>>
>>>>> Legal questions aside, this is a
>>>>> problem when the generated document is the one that will be considered
>>>>> "authoritative" if there is any discrepancy between versions. Better
>>>>> IMHO to insist that the author submit the authoritative form, along with
>>>>> whatever alternates are desired.
>>>>
>>>> I'm not sure what "authoritative" means for drafts. They're drafts,
>>>> after all ;-) IMO, integrating the on-line version with the submission
>>>> process just makes it easier for the author - they still can and do use
>>>> automated tools - some online -- and they can and do submit txt that
>>>> they haven't checked.
>>>>
>>>> IMO, providing a one-stop submission process just makes it less obscure
>>>> as a process. I see no reason we require the knowledge of magical
>>>> incantations to submit a doc.
>>>>
>>>> (I'd be all for .doc->.txt too, if I could figure out how to automate
>>>> it, i.e., .doc->.prn->.txt, where the last step is the tool I wrote and
>>>> *is* already online)
>>>>
>>>>> FWIW, I completely agree with Joe Hildebrand on the question of moving
>>>>> to UTF-8 (which seems like a no-brainer), and on elimination of fixed
>>>>> page breaks. Not so much on allowing 10000-character lines or generated
>>>>> HTML with 10x as much tags as content.
>>>>
>>>> I was involved in some of the UTF8 discussions of the past. My challenge
>>>> is:
>>>>
>>>>         - try to read the txt on a variety of currently common devices
>>>>         if most render UTF8 fine, then let's change things
>>>>
>>>> The last time I checked, UTF8 didn't work in Windows; I just checked
>>>> again with Win7: the default text reader - Wordpad - changes fonts
>>>> mid-stream when it hits such chars, and Emacs doesn't work either.
>>>>
>>>> I also just checked on an iPhone4 and an iPad, and it doesn't work there
>>>> either.
>>>>
>>>> I'm all for whatever new format works in most of the most common places,
>>>> but knocking out Windows' default reader, an iPhone, and an iPad, and my
>>>> conclusion remains that it's not ready for prime time.
>>>>
>>>> We can continue that on rfc-interest. This isn't a new issue; I just
>>>> wanted to give the current state of things.
>>>>
>>>> Joe
>>>>
>>
>
>
>

--------------000205020106020509070904
Content-Type: text/plain;
 name="draft-hoffman-utf8-rfcs-04-as-utf8.txt"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment;
 filename="draft-hoffman-utf8-rfcs-04-as-utf8.txt"

﻿


Network Working Group                                         P. Hoffman
Internet-Draft                                            VPN Consortium
Updates: 2223 (if approved)                                      T. Bray
Intended status: Informational                          Sun Microsystems
Expires: May 7, 2009                                    November 3, 2008


                   Using non-ASCII Characters in RFCs
                       draft-hoffman-utf8-rfcs-04

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

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

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

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

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

   This Internet-Draft will expire on May 7, 2009.

Copyright Notice

   Copyright (C) The IETF Trust (2008).

Abstract

   This document specifies a change to the IETF process in which
   Internet Drafts and RFCs are allowed to contain non-ASCII characters.
   The proposed change is to change the encoding of Internet Drafts and
   RFCs to UTF-8.






Hoffman & Bray             Expires May 7, 2009                  [Page 1]

Internet-Draft              Non-ASCII in RFCs              November 2008


1.  Introduction

   The purpose of this document is to specify a way for the IETF to use
   non-ASCII characters in Internet Drafts and RFCs.

   Various guideline documents in the IETF, notably [RFC2223], specify
   that RFCs must use only the US-ASCII character set.  This restriction
   has historically caused problems, notably:

   o  Names and addresses of authors of IETF documents are misspelled

   o  Names and document titles in references are misspelled

   o  Protocol examples that include non-ASCII characters cannot be
      included straightforwardly

   The first two issues cause real problems for people searching for
   RFCs for particular authors or references that contain non-ASCII
   characters.  For many languages that use Latin characters outside the
   ASCII range, there are no absolute mappings between those non-ASCII
   characters and ASCII equivalents.  A common example is that "u-with-
   umlaut" (U+00FC) may be mapped to "u" or to "ue"; many other mapping
   difficulties exist.

   The third issue reduces the effectiveness of IETF specifications;
   Implementors of protocols which carry textual payloads often
   experience difficulty in achieving interoperability related to the
   use of character sets from around the world.  Specifications which
   can provide concrete examples of such protocol scenarios will be of
   significant benefit to these implementors.

   Now that UTF-8 [RFC3629] is nearly universally available in text-
   editing and display systems, the IETF can eliminate these problems by
   allowing RFCs to use UTF-8.  As a reminder, UTF-8 is fully and
   thorougly upwards compatible to US-ASCII.

   This document uses example characters as specified in [RFC5137].  Had
   the recommendations from this document already been implemented, this
   alternate representation would, of course, not be necessary.

   It is important to note that this document does not use RFC 2119
   language (MUST, SHOULD, and so on).  Instead, it lists practices that
   the IETF should consider.  If the ideas in this document are adopted,
   the final list of rules for using UTF-8 in Internet Drafts and RFCs
   would be published by the IAOC.  The authors are open to changing
   this and using 2119-style language if the community prefers it.





Hoffman & Bray             Expires May 7, 2009                  [Page 2]

Internet-Draft              Non-ASCII in RFCs              November 2008


2.  Use of UTF-8 in Internet Drafts and RFCs

   Upon publication of this document as an RFC, all existing RFCs and
   Internet Drafts will be considered to be encoded in UTF-8.  The RFC
   Editor needs to change their processes to publish documents that are
   valid UTF-8.

   Similarly, upon acceptance of this document by the IETF, the IAOC
   should direct the IETF Secretariat to have all Internet Drafts
   encoded in UTF-8.  The Secretariat needs to change their processes to
   publish documents that are valid UTF-8.

2.1.  Limits On the Locations In Which Non-ASCII Text May Be Used

   It is suggested that the IETF Secretariat and RFC Editor limit non-
   ASCII characters to the following:

   o  Names and addresses of authors, used at the top of RFCs and in
      Author Contact sections

   o  Names and document titles used in References sections

   o  Quotations where the original contains non-ASCII characters

   o  Protocol examples that include non-ASCII characters, for example
      in Internationalized Domain Names (IDNs), Internationalized
      Resource Identifiers (IRIs), and Internationalized Email Addresses
      (IEA).

   Using non-ASCII characters in areas other than those listed above is
   prohibited.  In specific, using "curly quotes", m-dashes, and other
   punctuation that appear in normal publishing is not allowed under
   these guidelines.  This limitation is to help those people who are
   reading Internet Drafts and RFCs on systems that do not render UTF-8
   legibly.

2.2.  Allowable Character Repertoire

   UTF-8 is an encoding of the Unicode Character Set and can be used to
   encode any of its numeric codepoints, from U+0000 to U+10FFFF
   inclusive.  Specifications using UTF-8 must not use the following
   codepoint ranges:

   o  The "ASCII control characters" in the ranges U+0000 to U+0008,
      U+000B, and U+000D to U+001F. Also, the "C1 control characters" in
      the ranges U+0080 to U+009F. These lack either visual
      representations, interoperable semantics, or both.




Hoffman & Bray             Expires May 7, 2009                  [Page 3]

Internet-Draft              Non-ASCII in RFCs              November 2008


   o  The Surrogate-block range U+D800 to U+DFFF.  These codepoints do
      not identify characters, but exist to support the UTF-16 encoding.

   o  The ZERO WIDTH NO-BREAK SPACE U+FEFF and its mirror image U+FFFE.

   o  The Private-Use-Area ranges, U+E000 to U+F8FF, U+F0000 to U+FFFFD,
      and U+100000 to U+10FFFD.

   Specifications encoded in UTF-8 should not contain the encodings of
   Unicode codepoints which are "Compatibility Characters", that is,
   those whose properties include a compatibility decomposition.  Note
   that such characters occur rarely and detecting them requires run-
   time access to the Unicode character database, which may not be
   practical in some situations.

   [[ Need to add additional types of characters that should not be
   allowed: unassigned characters, other control characters, ones that
   are really formatting characters, and maybe others.  This needs some
   wording, given that the lists of these change over time. ]]

2.3.  Normalization

   Due to the way that Unicode uses combining characters, there are
   sometimes multiple codepoint sequences that denote what, to a human,
   is the same character.  For example, the character "lowercase-a-with-
   acute" can be spelled in two ways: as a single character (U+00E1) or
   as two characters (U+0061 followed by U+0301).  This can present
   problems in searching and rendering.

   The process of standardizing on one of these possibilities is
   referred to as "normalization" and several "normalization forms" are
   defined by the Unicode Consortium.  All UTF-8 text appearing in RFCs
   (but not necessarily Internet Drafts) ought to be normalized using
   Normalization Form C [[ reference needed, should be the version of
   Unicode when this is finalized ]].

2.4.  Author and Employer Names

   Authors can choose how to spell their names and the names of their
   employers in the various parts of Internet Drafts they are writing.
   The spelling at the top of the first page of the document needs to
   match the spelling in the "Authors' Addresses" section near the end
   of the document, but the latter can have alternate spellings to help
   those searching documents by name.  Postal information listed in the
   "Authors' Addresses" section can also use non-ASCII.

   For example, assume that an author whose name is 晓东 Fältström has a
   preferred all-ASCII spelling of Xiaodong Faltstrom.  Two expected



Hoffman & Bray             Expires May 7, 2009                  [Page 4]

Internet-Draft              Non-ASCII in RFCs              November 2008


   allowed methods for spelling his name would be:
   

   Network Working Group                                 X. Faltstrom
   Internet-Draft                                           ExampleCo
   . . .
   Author's Address

       Xiaodong Faltstrom (晓东 Fältström)
       ExampleCo

       Email: xiaodong.faltstrom@example.com


   Network Working Group                                 X. Fältström
   Internet-Draft                                           ExampleCo
   . . .
   Author's Address

       晓东 Fältström (Xiaodong Faltstrom)
       ExampleCo

       Email: xiaodong.faltstrom@example.com


3.  Document Content

   In order to assist text display software, any Internet Draft or RFC
   that contains non-ASCII characters should start with the byte order
   mark (BOM) U+FEFF.  The UTF-8 byte order mark should not be included
   in any Internet Draft or RFC that does not contain non-ASCII
   characters.  Detecting if an Internet Draft or RFC contains non-ASCII
   characters and being sure that such a document has a byte order mark
   can be done by the IETF's Internet Draft submission tool and the RFC
   Editor's publishing process.

   RFCs are currently published with form-feed characters between pages.
   These marks work on some printers but not others.  This proposed
   change does not affect any policy whether or not to use form-feed
   characters.


4.  Security Considerations

   A display program that expects only US-ASCII input may fail when it
   encounters octets outside the US-ASCII range of values.  Such a
   failure may become a security issue.  For example, the program may
   display incorrect results for the input.  More seriously, the program



Hoffman & Bray             Expires May 7, 2009                  [Page 5]

Internet-Draft              Non-ASCII in RFCs              November 2008


   may have an internal error that causes it to fail in a security-
   compromising fashion.  Note that such a program is vulnerable to many
   attacks other than just showing IETF documents.

   Someone could insert a UTF-8 host name in an RFC that has visually
   confusing characters.  Another person could copy that host name out
   of the RFC and have it resolve to an unintended DNS name.  This
   scenario seems quite far-fetched, given that tracking the RFC back to
   the author is trivial.


5.  IAOC considerations

   If this document is adopted by the IETF, it will be up to the IAOC to
   have the IETF Secretariat and the RFC Editor implement it.  The IAOC
   needs to consider all of the suggested rules in this document, both
   the positive ones (such as allowing additional characters in some
   parts of Internet Drafts and RFCs) and the negative ones (such as
   disallowing particular characters from being used).  The IAOC might
   want to publish proposed instructions to he IETF Secretariat and the
   RFC Editor and ask for community input on the specific instructions.


6.  Informative References

   [RFC2223]  Postel, J. and J. Reynolds, "Instructions to RFC Authors",
              RFC 2223, October 1997.

   [RFC3629]  Yergeau, F., "UTF-8, a transformation format of ISO
              10646", STD 63, RFC 3629, November 2003.

   [RFC5137]  Klensin, J., "ASCII Escaping of Unicode Characters",
              BCP 137, RFC 5137, February 2008.


Appendix A.  Arguments Against Changing to UTF-8

   Over more than a decade, the question of changing the encoding of
   RFCs to UTF-8 has come up repeatedly.  Although many people wanted
   the change, various people had different reasons why they felt it was
   a bad idea.  This appendix is a summary of those arguments and an
   explanation of why they are no longer as critical as they were long
   ago.

A.1.  Difficulty in Displaying

   Some text display systems only know how to display US-ASCII.
   Displaying an RFC that uses non-ASCII characters encoded in UTF-8



Hoffman & Bray             Expires May 7, 2009                  [Page 6]

Internet-Draft              Non-ASCII in RFCs              November 2008


   will cause those characters to be unreadable.

   There are, of course, still such display systems, and there always
   will be.  However, the number is dwindling as more software is
   improved to display non-ASCII characters and, in particular, to read
   UTF-8 as an encoding.  Of the systems that can only render US-ASCII,
   only a small subset drop non-ASCII characters: the others show an
   incorrect character in its place.  Thus, the person using such a
   system can often see that there is a problem, and can possibly choose
   to get better display software.

A.2.  Difficulty in Printing

   Some printers can only print a limited set of characters due to the
   fact that they are character-oriented, not graphical.  Such printers
   inherently cannot print characters they do not understand.  Almost
   all such printers print the visible ASCII characters just fine, but
   many cannot print the formfeeds currently used correctly.

   There are, of course, still such printers, and there always will be.
   However, the number is dwindling as older printers are replaced with
   ones that can print graphics so that now-common text features like
   boldface and italics can be printed.

A.3.  Insufficient Fonts

   Almost no display system that can display text that is encoded with
   UTF-8 can display every character in the Unicode repertoire.  Thus,
   some non-ASCII characters that are included in RFCs will not display
   properly.

   Virtually every system that can display Unicode knows how to
   substitute a replacement character for ones that cannot be displayed.
   In fact, many such systems have glyphs for rendering unknown
   characters and different glyphs for rendering known characters for
   which the system has no font.

A.4.  Inability to Search for Non-ASCII Characers

   If authors start using non-ASCII characters in their names and/or
   addresses, people who know the characters but are unfamiliar with the
   user interface on their computers may not be able to enter those
   characters in the search criteria.  For example, some people do not
   know how to enter "u-with-umlaut" in their operating system, even
   though the operating system allows such input.

   This is a valid concern, but one that is orthogonal to whether or not
   RFCs should use these characters.  The alternative (never go to



Hoffman & Bray             Expires May 7, 2009                  [Page 7]

Internet-Draft              Non-ASCII in RFCs              November 2008


   UTF-8) simply shifts the problem to forcing the user to guess which
   ASCII-only spelling to use when searching.


Appendix B.  Changes from -03 to -04

   Fixed many editorial nits pointed out by Martin Duerst.

   Changed the example in section 1 to u-with-umlaut.

   In section 1, added "As a reminder, UTF-8 is fully and thorougly
   upwards compatible to US-ASCII".

   In 2.1, changed "Quotations from non-English languages" to
   "Quotations where the original contains non-ASCII characters"

   Added the prohibition on "curly quotes", m-dashes, and so on at the
   end of section 2.1.

   Took formfeed (U+000C) out of the list in section 2.2.

   Added the C1 control characters to the list in section 2.2.

   Added note at the end of 2.2 on needing more about additional types
   of characters.

   Added a new section 3 about document content that covers byte order
   marks and form feeds.

   In A.2, changed "Almost all such printers print the ASCII characters
   just fine." to "Almost all such printers print the visible ASCII
   characters just fine, but many cannot print the formfeeds currently
   used correctly."


Authors' Addresses

   Paul Hoffman
   VPN Consortium

   Email: paul.hoffman@vpnc.org


   Tim Bray
   Sun Microsystems

   Email: tbray@textuality.com




Hoffman & Bray             Expires May 7, 2009                  [Page 8]

Internet-Draft              Non-ASCII in RFCs              November 2008


Full Copyright Statement

   Copyright (C) The IETF Trust (2008).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).





Hoffman & Bray             Expires May 7, 2009                  [Page 9]


--------------000205020106020509070904--

From joelja@bogus.com  Wed Feb  2 00:19:28 2011
Return-Path: <joelja@bogus.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A65A33A7075 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 00:19:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.216
X-Spam-Level: 
X-Spam-Status: No, score=-102.216 tagged_above=-999 required=5 tests=[AWL=0.383, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sfdhupdJUZVV for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 00:19:27 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id A70D13A6E3D for <wgchairs@ietf.org>; Wed,  2 Feb 2011 00:19:26 -0800 (PST)
Received: from joelja-mac.lan (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p128MgSb089307 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 08:22:43 GMT (envelope-from joelja@bogus.com)
Message-ID: <4D491452.1040605@bogus.com>
Date: Wed, 02 Feb 2011 00:22:42 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Canonical RFC formatting
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>	<4D4905EF.1060807@isi.edu>	<AANLkTi=9Dw_6d45K_YkbxV2ZrCWeF3UndJNvBJpW3A4-@mail.gmail.com> <4D49093E.3030809@isi.edu>
In-Reply-To: <4D49093E.3030809@isi.edu>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 08:19:28 -0000

On 2/1/11 11:35 PM, Joe Touch wrote:
> Sure - it was the test that Paul Hoffman wrote a while back. Attached.
> 
> My claim is that, ****out of the box, the following systems should be
> able to read the attached file with no additional configuration or
> software:
> 
> - Windows
> - Linux
> - MacOS

	right, so this opened in textedit by default

which rendered:

	晓东 Fältström

just fine:

> - FreeBSD
> - IOS (iPhone/iPad)

this rendered in preview by default, which did not render that properly
however the browser and the email client both did when the text was
rendered in them.


> - Android
> - Blackberry
> 
> I'm sure there are a few others that people would like to throw in,
> notably things like:
> - Kindle
> - Sony e-reader
> 
> Maybe some others too. Not sure. But that's the basic test as a start.
> 
> I can read .txt on all these (excepting the e-book readers, which
> require a txt to something converter) *right now*.
> 
> Again, we can take this over to rfc-i...
> 
> Joe
> 
> 
> 
> On 2/1/2011 11:29 PM, Lachlan Andrew wrote:
>> Greetings Joe,
>>
>> Could you circulate an example problematic attachment, to see how many
>> people have the problem?  May it depend on whether a particular
>> Windows installation is set up for UTF-8?
>>
>> For example, if you choose not to install fonts with accents, then
>> those characters can't be displayed.  The same applies to reading
>> ASCII if you choose to install an OS without any ASCII fonts.
>>
>> Just a thought...
>>
>> Lachlan
>>
>> On 2 February 2011 18:21, Joe Touch<touch@isi.edu>  wrote:
>>>
>>>
>>> On 2/1/2011 10:56 PM, Yaron Sheffer wrote:
>>>>
>>>> Hi Joe, can you clarify what do you mean by "does not support UTF-8?
>>>> I am composing this mail on an Android phone that supports Hebrew
>>>> just fine, I.e. UTF-8 with LTR rendering . And so do all current
>>>> platforms I am familiar with.
>>>
>>> I opened a UTF-8 file as an email attachment, and it displayed the UTF-8
>>> chars as garbage.
>>>
>>> My metric is: open a .txt file, encoded in UTF-8, and see what happens.
>>>
>>> Joe
>>>
>>>> Joe Touch<touch@isi.edu>    wrote:
>>>>
>>>>> Hi, Jeff,
>>>>>
>>>>> On 2/1/2011 9:21 PM, Jeffrey Hutzelman wrote:
>>>>>>
>>>>>> --On Wednesday, January 26, 2011 10:29:54 AM -0800 Joe Touch
>>>>>> <touch@isi.edu>    wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 1/26/2011 10:21 AM, Carsten Bormann wrote:
>>>>>>>>
>>>>>>>> On Jan 26, 2011, at 18:38, Joe Touch wrote:
>>>>>>>>
>>>>>>>>> The tool could probably be modified to accept .xml and turn it
>>>>>>>>> into
>>>>>>>>> .txt, but that seems like a tool issue, not a "canonical
>>>>>>>>> formatting"
>>>>>>>>> issue.
>>>>>>>>
>>>>>>>> I don't think so, because then you wouldn't have submitted the
>>>>>>>> legal
>>>>>>>> boilerplate.
>>>>>>>
>>>>>>> FWIW, that can be fixed on the confirmation page, where the text
>>>>>>> output
>>>>>>> including the legal boilerplate could appear and require positive
>>>>>>> confirmation.
>>>>>>
>>>>>> That seems OK for a document like
>>>>>> draft-arkko-dual-stack-extra-lite-03.txt, which one recent review
>>>>>> described as "a very brief (8-page) document", or for a document like
>>>>>> RFC347.
>>>>>>
>>>>>> I worry, though, that the submission process might time out while the
>>>>>> author verified correct compilation on a document like RFC5661.
>>>>>
>>>>> We have a two phase process right now. That can be part of it,
>>>>> i.e., you
>>>>> submit, it compiles off-line, then emails you only when it's ready to
>>>>> confirm.
>>>>>
>>>>>> More seriously, I also worry that the author is more likely to just
>>>>>> click through such a confirmation, rather than actually verifying the
>>>>>> correctness of the generated document.
>>>>>
>>>>> They do that now. People cut/paste without reading things. They
>>>>> generate
>>>>> the TXT without reading it either.
>>>>>
>>>>>> Legal questions aside, this is a
>>>>>> problem when the generated document is the one that will be
>>>>>> considered
>>>>>> "authoritative" if there is any discrepancy between versions. Better
>>>>>> IMHO to insist that the author submit the authoritative form,
>>>>>> along with
>>>>>> whatever alternates are desired.
>>>>>
>>>>> I'm not sure what "authoritative" means for drafts. They're drafts,
>>>>> after all ;-) IMO, integrating the on-line version with the submission
>>>>> process just makes it easier for the author - they still can and do
>>>>> use
>>>>> automated tools - some online -- and they can and do submit txt that
>>>>> they haven't checked.
>>>>>
>>>>> IMO, providing a one-stop submission process just makes it less
>>>>> obscure
>>>>> as a process. I see no reason we require the knowledge of magical
>>>>> incantations to submit a doc.
>>>>>
>>>>> (I'd be all for .doc->.txt too, if I could figure out how to automate
>>>>> it, i.e., .doc->.prn->.txt, where the last step is the tool I wrote
>>>>> and
>>>>> *is* already online)
>>>>>
>>>>>> FWIW, I completely agree with Joe Hildebrand on the question of
>>>>>> moving
>>>>>> to UTF-8 (which seems like a no-brainer), and on elimination of fixed
>>>>>> page breaks. Not so much on allowing 10000-character lines or
>>>>>> generated
>>>>>> HTML with 10x as much tags as content.
>>>>>
>>>>> I was involved in some of the UTF8 discussions of the past. My
>>>>> challenge
>>>>> is:
>>>>>
>>>>>         - try to read the txt on a variety of currently common devices
>>>>>         if most render UTF8 fine, then let's change things
>>>>>
>>>>> The last time I checked, UTF8 didn't work in Windows; I just checked
>>>>> again with Win7: the default text reader - Wordpad - changes fonts
>>>>> mid-stream when it hits such chars, and Emacs doesn't work either.
>>>>>
>>>>> I also just checked on an iPhone4 and an iPad, and it doesn't work
>>>>> there
>>>>> either.
>>>>>
>>>>> I'm all for whatever new format works in most of the most common
>>>>> places,
>>>>> but knocking out Windows' default reader, an iPhone, and an iPad,
>>>>> and my
>>>>> conclusion remains that it's not ready for prime time.
>>>>>
>>>>> We can continue that on rfc-interest. This isn't a new issue; I just
>>>>> wanted to give the current state of things.
>>>>>
>>>>> Joe
>>>>>
>>>
>>
>>
>>


From yaronf.ietf@gmail.com  Wed Feb  2 02:22:44 2011
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F9873A6BA1 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 02:22:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0k1xtYOpk4s for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 02:22:42 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 738DC3A6B98 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 02:22:42 -0800 (PST)
Received: by wwa36 with SMTP id 36so8539828wwa.13 for <wgchairs@ietf.org>; Wed, 02 Feb 2011 02:26:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=uehu3tmj1dRgF4MblsLYp8LaC+4HbQSBL6SEg5Jiz28=; b=x4mbKdBqder3aX7go+WJMs67KmKnpQFf3aePisB1Nxm528v12uvZkvmi9nyj964HOs cxECZm3IoUmshVZGLhaxwYjyWa5LVDORNc8x76V5bs1hYbKOH/bprLFQkBqMmlp8nYX0 RQCpa+N4O91w2Ta711qS3p+QjCxBtjCsvXizU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=XpwKXZiNPoGHaZDHHiKnVV0eIeak0iQ8JGgz3IK6XDESjAUWycV8CphxpbyZZ3nhGu 59UqOegXJ0e3dXjBIBV5YhjEB74q68m6/HbV7JLeG82gAkMEQk38LPt8MiVqv08kcEre MAY29C7BqGtFJF4mN4FVbCTf9bfrZZ/VpX2/s=
Received: by 10.227.133.15 with SMTP id d15mr8885848wbt.76.1296642361077; Wed, 02 Feb 2011 02:26:01 -0800 (PST)
Received: from [10.0.0.4] (46-116-122-59.bb.netvision.net.il [46.116.122.59]) by mx.google.com with ESMTPS id f27sm5977271wbf.1.2011.02.02.02.25.59 (version=SSLv3 cipher=RC4-MD5); Wed, 02 Feb 2011 02:26:00 -0800 (PST)
Message-ID: <4D493136.7080606@gmail.com>
Date: Wed, 02 Feb 2011 12:25:58 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: Canonical RFC formatting
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>	<4D4905EF.1060807@isi.edu>	<AANLkTi=9Dw_6d45K_YkbxV2ZrCWeF3UndJNvBJpW3A4-@mail.gmail.com>	<4D49093E.3030809@isi.edu> <4D491452.1040605@bogus.com>
In-Reply-To: <4D491452.1040605@bogus.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 10:22:44 -0000

Add Linux: gedit and Thunderbird on Ubuntu.

But not the Android mail reader, or the default Android preview apps (I 
suspect a more general mail-related problem there).

But I have a problem with the attitude. Some systems are broken. That's 
no reason to have people's name mangled on the documents that they write.

I don't have the statistics at hand, but I suppose *many more* people 
are using UTF-8 today, compared to plain ASCII.

Thanks,
	Yaron

On 02/02/2011 10:22 AM, Joel Jaeggli wrote:
> On 2/1/11 11:35 PM, Joe Touch wrote:
>> Sure - it was the test that Paul Hoffman wrote a while back. Attached.
>>
>> My claim is that, ****out of the box, the following systems should be
>> able to read the attached file with no additional configuration or
>> software:
>>
>> - Windows
>> - Linux
>> - MacOS
>
> 	right, so this opened in textedit by default
>
> which rendered:
>
> 	晓东 Fältström
>
> just fine:
>
>> - FreeBSD
>> - IOS (iPhone/iPad)
>
> this rendered in preview by default, which did not render that properly
> however the browser and the email client both did when the text was
> rendered in them.
>
>
>> - Android
>> - Blackberry
>>
>> I'm sure there are a few others that people would like to throw in,
>> notably things like:
>> - Kindle
>> - Sony e-reader
>>
>> Maybe some others too. Not sure. But that's the basic test as a start.
>>
>> I can read .txt on all these (excepting the e-book readers, which
>> require a txt to something converter) *right now*.
>>
>> Again, we can take this over to rfc-i...
>>
>> Joe
>>
>>
>>
>> On 2/1/2011 11:29 PM, Lachlan Andrew wrote:
>>> Greetings Joe,
>>>
>>> Could you circulate an example problematic attachment, to see how many
>>> people have the problem?  May it depend on whether a particular
>>> Windows installation is set up for UTF-8?
>>>
>>> For example, if you choose not to install fonts with accents, then
>>> those characters can't be displayed.  The same applies to reading
>>> ASCII if you choose to install an OS without any ASCII fonts.
>>>
>>> Just a thought...
>>>
>>> Lachlan
>>>
>>> On 2 February 2011 18:21, Joe Touch<touch@isi.edu>   wrote:
>>>>
>>>>
>>>> On 2/1/2011 10:56 PM, Yaron Sheffer wrote:
>>>>>
>>>>> Hi Joe, can you clarify what do you mean by "does not support UTF-8?
>>>>> I am composing this mail on an Android phone that supports Hebrew
>>>>> just fine, I.e. UTF-8 with LTR rendering . And so do all current
>>>>> platforms I am familiar with.
>>>>
>>>> I opened a UTF-8 file as an email attachment, and it displayed the UTF-8
>>>> chars as garbage.
>>>>
>>>> My metric is: open a .txt file, encoded in UTF-8, and see what happens.
>>>>
>>>> Joe
>>>>
>>>>> Joe Touch<touch@isi.edu>     wrote:
>>>>>
>>>>>> Hi, Jeff,
>>>>>>
>>>>>> On 2/1/2011 9:21 PM, Jeffrey Hutzelman wrote:
>>>>>>>
>>>>>>> --On Wednesday, January 26, 2011 10:29:54 AM -0800 Joe Touch
>>>>>>> <touch@isi.edu>     wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 1/26/2011 10:21 AM, Carsten Bormann wrote:
>>>>>>>>>
>>>>>>>>> On Jan 26, 2011, at 18:38, Joe Touch wrote:
>>>>>>>>>
>>>>>>>>>> The tool could probably be modified to accept .xml and turn it
>>>>>>>>>> into
>>>>>>>>>> .txt, but that seems like a tool issue, not a "canonical
>>>>>>>>>> formatting"
>>>>>>>>>> issue.
>>>>>>>>>
>>>>>>>>> I don't think so, because then you wouldn't have submitted the
>>>>>>>>> legal
>>>>>>>>> boilerplate.
>>>>>>>>
>>>>>>>> FWIW, that can be fixed on the confirmation page, where the text
>>>>>>>> output
>>>>>>>> including the legal boilerplate could appear and require positive
>>>>>>>> confirmation.
>>>>>>>
>>>>>>> That seems OK for a document like
>>>>>>> draft-arkko-dual-stack-extra-lite-03.txt, which one recent review
>>>>>>> described as "a very brief (8-page) document", or for a document like
>>>>>>> RFC347.
>>>>>>>
>>>>>>> I worry, though, that the submission process might time out while the
>>>>>>> author verified correct compilation on a document like RFC5661.
>>>>>>
>>>>>> We have a two phase process right now. That can be part of it,
>>>>>> i.e., you
>>>>>> submit, it compiles off-line, then emails you only when it's ready to
>>>>>> confirm.
>>>>>>
>>>>>>> More seriously, I also worry that the author is more likely to just
>>>>>>> click through such a confirmation, rather than actually verifying the
>>>>>>> correctness of the generated document.
>>>>>>
>>>>>> They do that now. People cut/paste without reading things. They
>>>>>> generate
>>>>>> the TXT without reading it either.
>>>>>>
>>>>>>> Legal questions aside, this is a
>>>>>>> problem when the generated document is the one that will be
>>>>>>> considered
>>>>>>> "authoritative" if there is any discrepancy between versions. Better
>>>>>>> IMHO to insist that the author submit the authoritative form,
>>>>>>> along with
>>>>>>> whatever alternates are desired.
>>>>>>
>>>>>> I'm not sure what "authoritative" means for drafts. They're drafts,
>>>>>> after all ;-) IMO, integrating the on-line version with the submission
>>>>>> process just makes it easier for the author - they still can and do
>>>>>> use
>>>>>> automated tools - some online -- and they can and do submit txt that
>>>>>> they haven't checked.
>>>>>>
>>>>>> IMO, providing a one-stop submission process just makes it less
>>>>>> obscure
>>>>>> as a process. I see no reason we require the knowledge of magical
>>>>>> incantations to submit a doc.
>>>>>>
>>>>>> (I'd be all for .doc->.txt too, if I could figure out how to automate
>>>>>> it, i.e., .doc->.prn->.txt, where the last step is the tool I wrote
>>>>>> and
>>>>>> *is* already online)
>>>>>>
>>>>>>> FWIW, I completely agree with Joe Hildebrand on the question of
>>>>>>> moving
>>>>>>> to UTF-8 (which seems like a no-brainer), and on elimination of fixed
>>>>>>> page breaks. Not so much on allowing 10000-character lines or
>>>>>>> generated
>>>>>>> HTML with 10x as much tags as content.
>>>>>>
>>>>>> I was involved in some of the UTF8 discussions of the past. My
>>>>>> challenge
>>>>>> is:
>>>>>>
>>>>>>          - try to read the txt on a variety of currently common devices
>>>>>>          if most render UTF8 fine, then let's change things
>>>>>>
>>>>>> The last time I checked, UTF8 didn't work in Windows; I just checked
>>>>>> again with Win7: the default text reader - Wordpad - changes fonts
>>>>>> mid-stream when it hits such chars, and Emacs doesn't work either.
>>>>>>
>>>>>> I also just checked on an iPhone4 and an iPad, and it doesn't work
>>>>>> there
>>>>>> either.
>>>>>>
>>>>>> I'm all for whatever new format works in most of the most common
>>>>>> places,
>>>>>> but knocking out Windows' default reader, an iPhone, and an iPad,
>>>>>> and my
>>>>>> conclusion remains that it's not ready for prime time.
>>>>>>
>>>>>> We can continue that on rfc-interest. This isn't a new issue; I just
>>>>>> wanted to give the current state of things.
>>>>>>
>>>>>> Joe
>>>>>>
>>>>
>>>
>>>
>>>
>

From duerst@it.aoyama.ac.jp  Wed Feb  2 02:57:54 2011
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C93DA3A6C98 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 02:57:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.219
X-Spam-Level: 
X-Spam-Status: No, score=-100.219 tagged_above=-999 required=5 tests=[AWL=-0.429, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iOWCIV5t9TQ4 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 02:57:53 -0800 (PST)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by core3.amsl.com (Postfix) with ESMTP id 361483A6C48 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 02:57:53 -0800 (PST)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id p12B15vK007162 for <wgchairs@ietf.org>; Wed, 2 Feb 2011 20:01:05 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 6a42_490e_bb2fbf5c_2ebb_11e0_a513_001d096c5782; Wed, 02 Feb 2011 20:01:05 +0900
Received: from [IPv6:::1] ([133.2.210.1]:33581) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S14C5E6A> for <wgchairs@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 2 Feb 2011 20:01:05 +0900
Message-ID: <4D49394F.7070108@it.aoyama.ac.jp>
Date: Wed, 02 Feb 2011 20:00:31 +0900
From: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Canonical RFC formatting
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>	<4D4905EF.1060807@isi.edu>	<AANLkTi=9Dw_6d45K_YkbxV2ZrCWeF3UndJNvBJpW3A4-@mail.gmail.com> <4D49093E.3030809@isi.edu>
In-Reply-To: <4D49093E.3030809@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 10:57:54 -0000

A few comments:

- The attached file was in UTF-8, but the Content-Type didn't say so.
   (I'm not sure if it had, that would have fixed the problem, but at
    least I think we should follow our own standards.)
- Browsers and email readers (for the main part of an email) should work
   without problems these days because they actually handle Content-Type
   charset information, which the file systems in general are very bad
   at doing.
- A file like this one is a tough job for software that tries to
   deal with both legacy encoding (e.g. ISO-8859-1 in Western Europe)
   and UTF-8. There's very little actual UTF-8 in there, and it's
   towards the end. (That could be fixed with a BOM, but then that
   might create other problems.)

On 2011/02/02 16:35, Joe Touch wrote:
> Sure - it was the test that Paul Hoffman wrote a while back. Attached.
>
> My claim is that, ****out of the box, the following systems should be
> able to read the attached file with no additional configuration or
> software:
>
> - Windows
> - Linux
> - MacOS
> - FreeBSD
> - IOS (iPhone/iPad)
> - Android
> - Blackberry

"with no additional configuration or software" can definitely be done. 
What may be needed is a choice of software (not just a double-click) and 
maybe even a choice of encoding (from a menu).

What is impossible to do is "with whatever software I always used to 
read Drafts/RFCs", because some such software may be older than UTF-8.

The question of what characters should be allowed to reduce the "missing 
font problem" is something that can be addressed even on a case-by-case 
base by the RFC specialists.

Regards,   Martin.

P.S.: To Yaron: I think you mean RTL when you talk about Hebrew,
not LTR.


> I'm sure there are a few others that people would like to throw in,
> notably things like:
> - Kindle
> - Sony e-reader
>
> Maybe some others too. Not sure. But that's the basic test as a start.
>
> I can read .txt on all these (excepting the e-book readers, which
> require a txt to something converter) *right now*.
>
> Again, we can take this over to rfc-i...
>
> Joe
>
>
>
> On 2/1/2011 11:29 PM, Lachlan Andrew wrote:
>> Greetings Joe,
>>
>> Could you circulate an example problematic attachment, to see how many
>> people have the problem? May it depend on whether a particular
>> Windows installation is set up for UTF-8?
>>
>> For example, if you choose not to install fonts with accents, then
>> those characters can't be displayed. The same applies to reading
>> ASCII if you choose to install an OS without any ASCII fonts.
>>
>> Just a thought...
>>
>> Lachlan
>>
>> On 2 February 2011 18:21, Joe Touch<touch@isi.edu> wrote:
>>>
>>>
>>> On 2/1/2011 10:56 PM, Yaron Sheffer wrote:
>>>>
>>>> Hi Joe, can you clarify what do you mean by "does not support UTF-8?
>>>> I am composing this mail on an Android phone that supports Hebrew
>>>> just fine, I.e. UTF-8 with LTR rendering . And so do all current
>>>> platforms I am familiar with.
>>>
>>> I opened a UTF-8 file as an email attachment, and it displayed the UTF-8
>>> chars as garbage.
>>>
>>> My metric is: open a .txt file, encoded in UTF-8, and see what happens.
>>>
>>> Joe
>>>
>>>> Joe Touch<touch@isi.edu> wrote:
>>>>
>>>>> Hi, Jeff,
>>>>>
>>>>> On 2/1/2011 9:21 PM, Jeffrey Hutzelman wrote:
>>>>>>
>>>>>> --On Wednesday, January 26, 2011 10:29:54 AM -0800 Joe Touch
>>>>>> <touch@isi.edu> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 1/26/2011 10:21 AM, Carsten Bormann wrote:
>>>>>>>>
>>>>>>>> On Jan 26, 2011, at 18:38, Joe Touch wrote:
>>>>>>>>
>>>>>>>>> The tool could probably be modified to accept .xml and turn it
>>>>>>>>> into
>>>>>>>>> .txt, but that seems like a tool issue, not a "canonical
>>>>>>>>> formatting"
>>>>>>>>> issue.
>>>>>>>>
>>>>>>>> I don't think so, because then you wouldn't have submitted the
>>>>>>>> legal
>>>>>>>> boilerplate.
>>>>>>>
>>>>>>> FWIW, that can be fixed on the confirmation page, where the text
>>>>>>> output
>>>>>>> including the legal boilerplate could appear and require positive
>>>>>>> confirmation.
>>>>>>
>>>>>> That seems OK for a document like
>>>>>> draft-arkko-dual-stack-extra-lite-03.txt, which one recent review
>>>>>> described as "a very brief (8-page) document", or for a document like
>>>>>> RFC347.
>>>>>>
>>>>>> I worry, though, that the submission process might time out while the
>>>>>> author verified correct compilation on a document like RFC5661.
>>>>>
>>>>> We have a two phase process right now. That can be part of it,
>>>>> i.e., you
>>>>> submit, it compiles off-line, then emails you only when it's ready to
>>>>> confirm.
>>>>>
>>>>>> More seriously, I also worry that the author is more likely to just
>>>>>> click through such a confirmation, rather than actually verifying the
>>>>>> correctness of the generated document.
>>>>>
>>>>> They do that now. People cut/paste without reading things. They
>>>>> generate
>>>>> the TXT without reading it either.
>>>>>
>>>>>> Legal questions aside, this is a
>>>>>> problem when the generated document is the one that will be
>>>>>> considered
>>>>>> "authoritative" if there is any discrepancy between versions. Better
>>>>>> IMHO to insist that the author submit the authoritative form,
>>>>>> along with
>>>>>> whatever alternates are desired.
>>>>>
>>>>> I'm not sure what "authoritative" means for drafts. They're drafts,
>>>>> after all ;-) IMO, integrating the on-line version with the submission
>>>>> process just makes it easier for the author - they still can and do
>>>>> use
>>>>> automated tools - some online -- and they can and do submit txt that
>>>>> they haven't checked.
>>>>>
>>>>> IMO, providing a one-stop submission process just makes it less
>>>>> obscure
>>>>> as a process. I see no reason we require the knowledge of magical
>>>>> incantations to submit a doc.
>>>>>
>>>>> (I'd be all for .doc->.txt too, if I could figure out how to automate
>>>>> it, i.e., .doc->.prn->.txt, where the last step is the tool I wrote
>>>>> and
>>>>> *is* already online)
>>>>>
>>>>>> FWIW, I completely agree with Joe Hildebrand on the question of
>>>>>> moving
>>>>>> to UTF-8 (which seems like a no-brainer), and on elimination of fixed
>>>>>> page breaks. Not so much on allowing 10000-character lines or
>>>>>> generated
>>>>>> HTML with 10x as much tags as content.
>>>>>
>>>>> I was involved in some of the UTF8 discussions of the past. My
>>>>> challenge
>>>>> is:
>>>>>
>>>>> - try to read the txt on a variety of currently common devices
>>>>> if most render UTF8 fine, then let's change things
>>>>>
>>>>> The last time I checked, UTF8 didn't work in Windows; I just checked
>>>>> again with Win7: the default text reader - Wordpad - changes fonts
>>>>> mid-stream when it hits such chars, and Emacs doesn't work either.
>>>>>
>>>>> I also just checked on an iPhone4 and an iPad, and it doesn't work
>>>>> there
>>>>> either.
>>>>>
>>>>> I'm all for whatever new format works in most of the most common
>>>>> places,
>>>>> but knocking out Windows' default reader, an iPhone, and an iPad,
>>>>> and my
>>>>> conclusion remains that it's not ready for prime time.
>>>>>
>>>>> We can continue that on rfc-interest. This isn't a new issue; I just
>>>>> wanted to give the current state of things.
>>>>>
>>>>> Joe
>>>>>
>>>
>>
>>
>>

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

From duerst@it.aoyama.ac.jp  Wed Feb  2 03:15:50 2011
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E95063A6BB3 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 03:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.211
X-Spam-Level: 
X-Spam-Status: No, score=-100.211 tagged_above=-999 required=5 tests=[AWL=-0.421, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4VYDuXYKZcv3 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 03:15:49 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by core3.amsl.com (Postfix) with ESMTP id 3B3673A7142 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 03:15:45 -0800 (PST)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id p12BJ40r014638 for <wgchairs@ietf.org>; Wed, 2 Feb 2011 20:19:04 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 6b90_4833_3e1ab082_2ebe_11e0_a30d_001d096c566a; Wed, 02 Feb 2011 20:19:04 +0900
Received: from [IPv6:::1] ([133.2.210.1]:52633) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S14C5EB6> for <wgchairs@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 2 Feb 2011 20:19:04 +0900
Message-ID: <4D493D85.1080708@it.aoyama.ac.jp>
Date: Wed, 02 Feb 2011 20:18:29 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Canonical RFC formatting
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>	<4D4905EF.1060807@isi.edu>	<AANLkTi=9Dw_6d45K_YkbxV2ZrCWeF3UndJNvBJpW3A4-@mail.gmail.com>	<4D49093E.3030809@isi.edu>	<4D491452.1040605@bogus.com> <4D493136.7080606@gmail.com>
In-Reply-To: <4D493136.7080606@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 11:15:51 -0000

On 2011/02/02 19:25, Yaron Sheffer wrote:

> I don't have the statistics at hand, but I suppose *many more* people
> are using UTF-8 today, compared to plain ASCII.

For the Web, that seems to be very much so indeed:

http://trends.builtwith.com/encoding/UTF-8
http://w3techs.com/technologies/details/en-utf8/all/all
http://googleblog.blogspot.com/2008/05/moving-to-unicode-51.html

I think the statistics for documents used locally would trail behind 
(UTF-8 vs. legacy encodings in general, not UTF-8 vs. US-ASCII), but the 
direction would be the same.

I wonder what percentage US-ASCII had when it was decided that that 
would be used for RFCs. In the old days, EBCDIC was still going strong, 
so my assumption would be that it wouldn't have been that much more than 
UTF-8 now :-).


Regards,   Martin.


-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

From marc.blanchet@viagenie.ca  Wed Feb  2 06:09:18 2011
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F3193A6C04 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 06:09:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sq84jrqxMBjl for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 06:09:16 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 3EF593A6BFB for <wgchairs@ietf.org>; Wed,  2 Feb 2011 06:09:16 -0800 (PST)
Received: from mbl.local (unknown [IPv6:2620:0:230:c003:5ab0:35ff:fef4:6fa]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 59F7A21D21 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 09:12:34 -0500 (EST)
Message-ID: <4D496651.3030006@viagenie.ca>
Date: Wed, 02 Feb 2011 09:12:33 -0500
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Working Group Chairs <wgchairs@ietf.org>
Subject: RFC2119 keywords
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 14:09:18 -0000

Hello,
  almost all drafts copy the following text:
"The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
             "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
             and "OPTIONAL" in this document are to be interpreted as ...
"
and also add a reference to RFC2119.


Instead of copying all the time, and given that everybody knows this 
stuff, why don't we instead put this text or reference it in the 
document boilerplate generated by xml2rfc or else?

Marc.
-- 
=========
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN Implementation: http://postellation.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca


From yaronf.ietf@gmail.com  Wed Feb  2 06:30:27 2011
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69B233A6D09 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 06:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.449
X-Spam-Level: 
X-Spam-Status: No, score=-103.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cRxtyy5c7Vaq for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 06:30:26 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id AB0E83A6CE0 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 06:30:25 -0800 (PST)
Received: by wyf23 with SMTP id 23so23420wyf.31 for <wgchairs@ietf.org>; Wed, 02 Feb 2011 06:33:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Mgc5CXpso8RWw7VpoVtPVQzyNG0MCmbSiw6pC9yAUH4=; b=Owrfu/t0B80NQSem1msDAax3nl9Bv58v7Tvu9L/TgOtza/yAsf7s+jZwO7PKXGx7nR MZyOSYFZ/a2dltFiSTN6aZ06cKuamdap/VbQXGGJ/kQ49r2tjsUybbi0hmnNGzOU9QAy pJp2nG5TY4XzVJI1JckZkuTzQK3X5IPkg08kA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=YTFq1gdoL/7JSD415cZ/YzasW8syV06Pcjva0Q9zERneh+TXOPx40gBk5DlF1x2Z+T NYILosLoBPg0i+UG8w67lgMPdsQBSpK21aiOztQsh2WCIvq5aTaLRI3w4Zi0bCen0pVU vwUyWHDsVanfyA8arx6W8VYo9DTR8X5H3RUl8=
Received: by 10.227.142.85 with SMTP id p21mr9258558wbu.12.1296657224551; Wed, 02 Feb 2011 06:33:44 -0800 (PST)
Received: from [10.0.0.4] (46-116-122-59.bb.netvision.net.il [46.116.122.59]) by mx.google.com with ESMTPS id y29sm11848257wbd.4.2011.02.02.06.33.41 (version=SSLv3 cipher=RC4-MD5); Wed, 02 Feb 2011 06:33:42 -0800 (PST)
Message-ID: <4D496B44.2030404@gmail.com>
Date: Wed, 02 Feb 2011 16:33:40 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: Canonical RFC formatting
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>	<4D4905EF.1060807@isi.edu>	<AANLkTi=9Dw_6d45K_YkbxV2ZrCWeF3UndJNvBJpW3A4-@mail.gmail.com>	<4D49093E.3030809@isi.edu> <4D49394F.7070108@it.aoyama.ac.jp>
In-Reply-To: <4D49394F.7070108@it.aoyama.ac.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 14:30:27 -0000

RTL, seY :-)

On 02/02/2011 01:00 PM, "Martin J. Dürst" wrote:
> A few comments:
>
> - The attached file was in UTF-8, but the Content-Type didn't say so.
> (I'm not sure if it had, that would have fixed the problem, but at
> least I think we should follow our own standards.)
> - Browsers and email readers (for the main part of an email) should work
> without problems these days because they actually handle Content-Type
> charset information, which the file systems in general are very bad
> at doing.
> - A file like this one is a tough job for software that tries to
> deal with both legacy encoding (e.g. ISO-8859-1 in Western Europe)
> and UTF-8. There's very little actual UTF-8 in there, and it's
> towards the end. (That could be fixed with a BOM, but then that
> might create other problems.)
>
> On 2011/02/02 16:35, Joe Touch wrote:
>> Sure - it was the test that Paul Hoffman wrote a while back. Attached.
>>
>> My claim is that, ****out of the box, the following systems should be
>> able to read the attached file with no additional configuration or
>> software:
>>
>> - Windows
>> - Linux
>> - MacOS
>> - FreeBSD
>> - IOS (iPhone/iPad)
>> - Android
>> - Blackberry
>
> "with no additional configuration or software" can definitely be done.
> What may be needed is a choice of software (not just a double-click) and
> maybe even a choice of encoding (from a menu).
>
> What is impossible to do is "with whatever software I always used to
> read Drafts/RFCs", because some such software may be older than UTF-8.
>
> The question of what characters should be allowed to reduce the "missing
> font problem" is something that can be addressed even on a case-by-case
> base by the RFC specialists.
>
> Regards, Martin.
>
> P.S.: To Yaron: I think you mean RTL when you talk about Hebrew,
> not LTR.
>
>
>> I'm sure there are a few others that people would like to throw in,
>> notably things like:
>> - Kindle
>> - Sony e-reader
>>
>> Maybe some others too. Not sure. But that's the basic test as a start.
>>
>> I can read .txt on all these (excepting the e-book readers, which
>> require a txt to something converter) *right now*.
>>
>> Again, we can take this over to rfc-i...
>>
>> Joe
>>
>>
>>
>> On 2/1/2011 11:29 PM, Lachlan Andrew wrote:
>>> Greetings Joe,
>>>
>>> Could you circulate an example problematic attachment, to see how many
>>> people have the problem? May it depend on whether a particular
>>> Windows installation is set up for UTF-8?
>>>
>>> For example, if you choose not to install fonts with accents, then
>>> those characters can't be displayed. The same applies to reading
>>> ASCII if you choose to install an OS without any ASCII fonts.
>>>
>>> Just a thought...
>>>
>>> Lachlan
>>>
>>> On 2 February 2011 18:21, Joe Touch<touch@isi.edu> wrote:
>>>>
>>>>
>>>> On 2/1/2011 10:56 PM, Yaron Sheffer wrote:
>>>>>
>>>>> Hi Joe, can you clarify what do you mean by "does not support UTF-8?
>>>>> I am composing this mail on an Android phone that supports Hebrew
>>>>> just fine, I.e. UTF-8 with LTR rendering . And so do all current
>>>>> platforms I am familiar with.
>>>>
>>>> I opened a UTF-8 file as an email attachment, and it displayed the
>>>> UTF-8
>>>> chars as garbage.
>>>>
>>>> My metric is: open a .txt file, encoded in UTF-8, and see what happens.
>>>>
>>>> Joe
>>>>
>>>>> Joe Touch<touch@isi.edu> wrote:
>>>>>
>>>>>> Hi, Jeff,
>>>>>>
>>>>>> On 2/1/2011 9:21 PM, Jeffrey Hutzelman wrote:
>>>>>>>
>>>>>>> --On Wednesday, January 26, 2011 10:29:54 AM -0800 Joe Touch
>>>>>>> <touch@isi.edu> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 1/26/2011 10:21 AM, Carsten Bormann wrote:
>>>>>>>>>
>>>>>>>>> On Jan 26, 2011, at 18:38, Joe Touch wrote:
>>>>>>>>>
>>>>>>>>>> The tool could probably be modified to accept .xml and turn it
>>>>>>>>>> into
>>>>>>>>>> .txt, but that seems like a tool issue, not a "canonical
>>>>>>>>>> formatting"
>>>>>>>>>> issue.
>>>>>>>>>
>>>>>>>>> I don't think so, because then you wouldn't have submitted the
>>>>>>>>> legal
>>>>>>>>> boilerplate.
>>>>>>>>
>>>>>>>> FWIW, that can be fixed on the confirmation page, where the text
>>>>>>>> output
>>>>>>>> including the legal boilerplate could appear and require positive
>>>>>>>> confirmation.
>>>>>>>
>>>>>>> That seems OK for a document like
>>>>>>> draft-arkko-dual-stack-extra-lite-03.txt, which one recent review
>>>>>>> described as "a very brief (8-page) document", or for a document
>>>>>>> like
>>>>>>> RFC347.
>>>>>>>
>>>>>>> I worry, though, that the submission process might time out while
>>>>>>> the
>>>>>>> author verified correct compilation on a document like RFC5661.
>>>>>>
>>>>>> We have a two phase process right now. That can be part of it,
>>>>>> i.e., you
>>>>>> submit, it compiles off-line, then emails you only when it's ready to
>>>>>> confirm.
>>>>>>
>>>>>>> More seriously, I also worry that the author is more likely to just
>>>>>>> click through such a confirmation, rather than actually verifying
>>>>>>> the
>>>>>>> correctness of the generated document.
>>>>>>
>>>>>> They do that now. People cut/paste without reading things. They
>>>>>> generate
>>>>>> the TXT without reading it either.
>>>>>>
>>>>>>> Legal questions aside, this is a
>>>>>>> problem when the generated document is the one that will be
>>>>>>> considered
>>>>>>> "authoritative" if there is any discrepancy between versions. Better
>>>>>>> IMHO to insist that the author submit the authoritative form,
>>>>>>> along with
>>>>>>> whatever alternates are desired.
>>>>>>
>>>>>> I'm not sure what "authoritative" means for drafts. They're drafts,
>>>>>> after all ;-) IMO, integrating the on-line version with the
>>>>>> submission
>>>>>> process just makes it easier for the author - they still can and do
>>>>>> use
>>>>>> automated tools - some online -- and they can and do submit txt that
>>>>>> they haven't checked.
>>>>>>
>>>>>> IMO, providing a one-stop submission process just makes it less
>>>>>> obscure
>>>>>> as a process. I see no reason we require the knowledge of magical
>>>>>> incantations to submit a doc.
>>>>>>
>>>>>> (I'd be all for .doc->.txt too, if I could figure out how to automate
>>>>>> it, i.e., .doc->.prn->.txt, where the last step is the tool I wrote
>>>>>> and
>>>>>> *is* already online)
>>>>>>
>>>>>>> FWIW, I completely agree with Joe Hildebrand on the question of
>>>>>>> moving
>>>>>>> to UTF-8 (which seems like a no-brainer), and on elimination of
>>>>>>> fixed
>>>>>>> page breaks. Not so much on allowing 10000-character lines or
>>>>>>> generated
>>>>>>> HTML with 10x as much tags as content.
>>>>>>
>>>>>> I was involved in some of the UTF8 discussions of the past. My
>>>>>> challenge
>>>>>> is:
>>>>>>
>>>>>> - try to read the txt on a variety of currently common devices
>>>>>> if most render UTF8 fine, then let's change things
>>>>>>
>>>>>> The last time I checked, UTF8 didn't work in Windows; I just checked
>>>>>> again with Win7: the default text reader - Wordpad - changes fonts
>>>>>> mid-stream when it hits such chars, and Emacs doesn't work either.
>>>>>>
>>>>>> I also just checked on an iPhone4 and an iPad, and it doesn't work
>>>>>> there
>>>>>> either.
>>>>>>
>>>>>> I'm all for whatever new format works in most of the most common
>>>>>> places,
>>>>>> but knocking out Windows' default reader, an iPhone, and an iPad,
>>>>>> and my
>>>>>> conclusion remains that it's not ready for prime time.
>>>>>>
>>>>>> We can continue that on rfc-interest. This isn't a new issue; I just
>>>>>> wanted to give the current state of things.
>>>>>>
>>>>>> Joe
>>>>>>
>>>>
>>>
>>>
>>>
>

From ajs@shinkuro.com  Wed Feb  2 07:28:01 2011
Return-Path: <ajs@shinkuro.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 522B13A6CFB for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 07:28:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ahCi7x-6jhJA for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 07:28:00 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 4F8A83A6CD9 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 07:28:00 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id B75521ECB423 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 15:31:19 +0000 (UTC)
Date: Wed, 2 Feb 2011 10:31:17 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: wgchairs@ietf.org
Subject: Re: RFC2119 keywords
Message-ID: <20110202153117.GA7903@shinkuro.com>
References: <4D496651.3030006@viagenie.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D496651.3030006@viagenie.ca>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 15:28:01 -0000

On Wed, Feb 02, 2011 at 09:12:33AM -0500, Marc Blanchet wrote:
> Instead of copying all the time, and given that everybody knows this  
> stuff, why don't we instead put this text or reference it in the  
> document boilerplate generated by xml2rfc or else?

For xml2rfc, I think a directive would be needed.  It shouldn't be in
every draft -- there are drafts that don't have it or, more often,
include it and don't actually use any of the keywords.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From rbarnes@bbn.com  Wed Feb  2 07:32:18 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 865203A6D24 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 07:32:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.698
X-Spam-Level: 
X-Spam-Status: No, score=-102.698 tagged_above=-999 required=5 tests=[AWL=-0.099, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HeNfReVRYIaM for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 07:32:16 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id C2CD43A6CD9 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 07:32:16 -0800 (PST)
Received: from [192.1.255.181] (port=61969 helo=col-raltmann-l1.nira.bbn.com) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Pkek4-0007Ov-BP; Wed, 02 Feb 2011 10:35:36 -0500
Subject: Re: RFC2119 keywords
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <20110202153117.GA7903@shinkuro.com>
Date: Wed, 2 Feb 2011 10:35:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4E55351-4841-42F8-9F13-67951A5E241F@bbn.com>
References: <4D496651.3030006@viagenie.ca> <20110202153117.GA7903@shinkuro.com>
To: Andrew Sullivan <ajs@shinkuro.com>
X-Mailer: Apple Mail (2.1082)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 15:32:18 -0000

You could also define an entity in the DTD, assuming that the reference =
would be in the <references>.

<!ENTITY rfc2119 'The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", =
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and =
"OPTIONAL" in this document are to be interpreted as in RFC 2119 <xref =
target=3D"RFC2119"></xref>.'>

<section title=3D"Terminology">
&rfc2119;
</section>



On Feb 2, 2011, at 10:31 AM, Andrew Sullivan wrote:

> On Wed, Feb 02, 2011 at 09:12:33AM -0500, Marc Blanchet wrote:
>> Instead of copying all the time, and given that everybody knows this =20=

>> stuff, why don't we instead put this text or reference it in the =20
>> document boilerplate generated by xml2rfc or else?
>=20
> For xml2rfc, I think a directive would be needed.  It shouldn't be in
> every draft -- there are drafts that don't have it or, more often,
> include it and don't actually use any of the keywords.
>=20
> A
>=20
> --=20
> Andrew Sullivan
> ajs@shinkuro.com
> Shinkuro, Inc.


From pkyzivat@cisco.com  Wed Feb  2 08:47:43 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77FDE3A6CDC for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 08:47:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.521
X-Spam-Level: 
X-Spam-Status: No, score=-110.521 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VSTo9cTqF+ys for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 08:47:42 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id AB4933A6C05 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 08:47:42 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcGAIoaSU1AZnwN/2dsb2JhbACWd44jc6Bxmx+FUwSEeIZpgyo
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 02 Feb 2011 16:51:02 +0000
Received: from [10.86.254.109] ([10.86.254.109]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p12Gou5Y005747 for <wgchairs@ietf.org>; Wed, 2 Feb 2011 16:50:57 GMT
Message-ID: <4D498B72.6060400@cisco.com>
Date: Wed, 02 Feb 2011 11:50:58 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: RFC2119 keywords
References: <4D496651.3030006@viagenie.ca> <20110202153117.GA7903@shinkuro.com>
In-Reply-To: <20110202153117.GA7903@shinkuro.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 16:47:43 -0000

On 2/2/2011 10:31 AM, Andrew Sullivan wrote:
> On Wed, Feb 02, 2011 at 09:12:33AM -0500, Marc Blanchet wrote:
>> Instead of copying all the time, and given that everybody knows this
>> stuff, why don't we instead put this text or reference it in the
>> document boilerplate generated by xml2rfc or else?
>
> For xml2rfc, I think a directive would be needed.  It shouldn't be in
> every draft -- there are drafts that don't have it or, more often,
> include it and don't actually use any of the keywords.

Maybe a directive that says, in effect, "include that boilerplate and 
reference *if* any of those words appear in the document".

	Thanks,
	Paul

From ietfdbh@comcast.net  Wed Feb  2 09:16:33 2011
Return-Path: <ietfdbh@comcast.net>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DEB433A6CEC for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:16:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.609
X-Spam-Level: 
X-Spam-Status: No, score=-102.609 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2I5czY3DMFc1 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:16:33 -0800 (PST)
Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by core3.amsl.com (Postfix) with ESMTP id 305D93A6C3B for <wgchairs@ietf.org>; Wed,  2 Feb 2011 09:16:33 -0800 (PST)
Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta12.emeryville.ca.mail.comcast.net with comcast id 35Bg1g00F1vN32cAC5KtBP; Wed, 02 Feb 2011 17:19:53 +0000
Received: from davidPC ([67.189.235.106]) by omta22.emeryville.ca.mail.comcast.net with comcast id 35Kq1g01H2JQnJT8i5Krop; Wed, 02 Feb 2011 17:19:52 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>, <wgchairs@ietf.org>
References: <4D496651.3030006@viagenie.ca> <20110202153117.GA7903@shinkuro.com> <4D498B72.6060400@cisco.com>
In-Reply-To: <4D498B72.6060400@cisco.com>
Subject: RE: RFC2119 keywords
Date: Wed, 2 Feb 2011 12:19:25 -0500
Message-ID: <6E9C2DE0217B4935B527E3A12A225D66@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcvC+WItirkJ0oL/SI2VMGCSO9gq5AAA9X7A
X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16543
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 17:16:34 -0000

I think this is better handled by the human editor, using a directive.
It only needs to be added once per document.

dbh 

> -----Original Message-----
> From: wgchairs-bounces@ietf.org 
> [mailto:wgchairs-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: Wednesday, February 02, 2011 11:51 AM
> To: wgchairs@ietf.org
> Subject: Re: RFC2119 keywords
> 
> 
> 
> On 2/2/2011 10:31 AM, Andrew Sullivan wrote:
> > On Wed, Feb 02, 2011 at 09:12:33AM -0500, Marc Blanchet wrote:
> >> Instead of copying all the time, and given that everybody 
> knows this
> >> stuff, why don't we instead put this text or reference it in the
> >> document boilerplate generated by xml2rfc or else?
> >
> > For xml2rfc, I think a directive would be needed.  It 
> shouldn't be in
> > every draft -- there are drafts that don't have it or, more often,
> > include it and don't actually use any of the keywords.
> 
> Maybe a directive that says, in effect, "include that boilerplate
and 
> reference *if* any of those words appear in the document".
> 
> 	Thanks,
> 	Paul
> 


From sob@harvard.edu  Wed Feb  2 09:19:10 2011
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C6E43A6C05 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:19:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.256
X-Spam-Level: 
X-Spam-Status: No, score=-102.256 tagged_above=-999 required=5 tests=[AWL=0.343, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ECDbe3rfLF+B for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:19:10 -0800 (PST)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id E8AA53A6BC0 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 09:19:09 -0800 (PST)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id B63E282AD01; Wed,  2 Feb 2011 12:22:28 -0500 (EST)
To: pkyzivat@cisco.com, wgchairs@ietf.org
Subject: Re: RFC2119 keywords
In-Reply-To: <4D498B72.6060400@cisco.com>
Message-Id: <20110202172228.B63E282AD01@newdev.eecs.harvard.edu>
Date: Wed,  2 Feb 2011 12:22:28 -0500 (EST)
From: sob@harvard.edu (Scott O. Bradner)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 17:19:10 -0000

> Maybe a directive that says, in effect, "include that boilerplate and 
> reference *if* any of those words appear in the document".

case sensitive (not included for "must" but included if "MUST")

Scott

From touch@isi.edu  Wed Feb  2 09:27:36 2011
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F62F3A6D7E for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:27:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.455
X-Spam-Level: 
X-Spam-Status: No, score=-102.455 tagged_above=-999 required=5 tests=[AWL=-0.156, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ni7Ym9Nb+O0L for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:27:35 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 8FFB93A6D2C for <wgchairs@ietf.org>; Wed,  2 Feb 2011 09:27:35 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p12HUPmY029144 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 09:30:25 -0800 (PST)
Message-ID: <4D4994B1.5050103@isi.edu>
Date: Wed, 02 Feb 2011 09:30:25 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: Canonical RFC formatting
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>	<4D4905EF.1060807@isi.edu>	<AANLkTi=9Dw_6d45K_YkbxV2ZrCWeF3UndJNvBJpW3A4-@mail.gmail.com> <4D49093E.3030809@isi.edu> <4D49394F.7070108@it.aoyama.ac.jp>
In-Reply-To: <4D49394F.7070108@it.aoyama.ac.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 17:27:36 -0000

Hi, Martin,

On 2/2/2011 3:00 AM, "Martin J. Dürst" wrote:
> A few comments:
>
> - The attached file was in UTF-8, but the Content-Type didn't say so.
> (I'm not sure if it had, that would have fixed the problem, but at
> least I think we should follow our own standards.)

I dragged and dropped it into Thunderbird, FWIW.

> - Browsers and email readers (for the main part of an email) should work
> without problems these days because they actually handle Content-Type
> charset information, which the file systems in general are very bad
> at doing.

Maybe they should, but the evidence is that they do not. The 
drag-and-drop into Tbird didn't set the content type as needed, and as a 
result the iPhone/iPad didn't render it correctly.

> - A file like this one is a tough job for software that tries to
> deal with both legacy encoding (e.g. ISO-8859-1 in Western Europe)
> and UTF-8. There's very little actual UTF-8 in there, and it's
> towards the end. (That could be fixed with a BOM, but then that
> might create other problems.)

That might be very typical, e.g., if only an example or two and the 
authors' names actually were outside the existing RFC ASCII subset.

Joe

From touch@isi.edu  Wed Feb  2 09:32:16 2011
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A7CF3A6D8E for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:32:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.603
X-Spam-Level: 
X-Spam-Status: No, score=-102.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5I7DpR9V8Ua for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:32:15 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 8BE413A6D2C for <wgchairs@ietf.org>; Wed,  2 Feb 2011 09:32:15 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p12HYlip029984 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 09:34:47 -0800 (PST)
Message-ID: <4D4995B7.2000307@isi.edu>
Date: Wed, 02 Feb 2011 09:34:47 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Canonical RFC formatting
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>	<4D4905EF.1060807@isi.edu>	<AANLkTi=9Dw_6d45K_YkbxV2ZrCWeF3UndJNvBJpW3A4-@mail.gmail.com>	<4D49093E.3030809@isi.edu> <4D491452.1040605@bogus.com> <4D493136.7080606@gmail.com>
In-Reply-To: <4D493136.7080606@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 17:32:16 -0000

On 2/2/2011 2:25 AM, Yaron Sheffer wrote:
> Add Linux: gedit and Thunderbird on Ubuntu.
>
> But not the Android mail reader, or the default Android preview apps (I
> suspect a more general mail-related problem there).
>
> But I have a problem with the attitude. Some systems are broken. That's
> no reason to have people's name mangled on the documents that they write.

Yes, actually, it is.

The two alternatives are:

	- honor the specific requirements of a subset of people
	- make text readable to everyone

That's the same trade-off that led us to IP, which "works everywhere", 
but, AFAICT, is best nearly nowhere.

IMO, sticking to the RFC ASCII subset is no different. We *are* eating 
our own dogfood, or at least living by our own standards.

Yes, this is a good reason to fix these apps/systems. But it's also 
evidence that shifting to UTF-8 will make the RFCs less accessible than 
they are now.

> I don't have the statistics at hand, but I suppose *many more* people
> are using UTF-8 today, compared to plain ASCII.

By that logic we should write RFCs in Chinese ;-)

Joe

From paul.hoffman@vpnc.org  Wed Feb  2 09:33:39 2011
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D3CA3A6D98 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.552
X-Spam-Level: 
X-Spam-Status: No, score=-100.552 tagged_above=-999 required=5 tests=[AWL=-0.920, BAYES_40=-0.185, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dKX4nQa2EZyi for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:33:38 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id B3AFA3A6D95 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 09:33:38 -0800 (PST)
Received: from MacBook-08.local (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p12HavC8003068 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Wed, 2 Feb 2011 10:36:58 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D49963B.5020508@vpnc.org>
Date: Wed, 02 Feb 2011 09:36:59 -0800
From: Paul Hoffman <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Canonical RFC formatting
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>	<4D4905EF.1060807@isi.edu>	<AANLkTi=9Dw_6d45K_YkbxV2ZrCWeF3UndJNvBJpW3A4-@mail.gmail.com>	<4D49093E.3030809@isi.edu>	<4D491452.1040605@bogus.com> <4D493136.7080606@gmail.com> <4D4995B7.2000307@isi.edu>
In-Reply-To: <4D4995B7.2000307@isi.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 17:33:39 -0000

Again: why is this thread on the wg-chairs mailing list?

From touch@isi.edu  Wed Feb  2 09:42:09 2011
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D809D3A6C01 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:42:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.603
X-Spam-Level: 
X-Spam-Status: No, score=-102.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id odjW20BzNfEe for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:42:09 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 0C9533A6D67 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 09:42:09 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p12HjG6J001945 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 09:45:16 -0800 (PST)
Message-ID: <4D49982C.4010504@isi.edu>
Date: Wed, 02 Feb 2011 09:45:16 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Scott O. Bradner" <sob@harvard.edu>
Subject: Re: RFC2119 keywords
References: <20110202172228.B63E282AD01@newdev.eecs.harvard.edu>
In-Reply-To: <20110202172228.B63E282AD01@newdev.eecs.harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 17:42:10 -0000

On 2/2/2011 9:22 AM, Scott O. Bradner wrote:
 >> Maybe a directive that says, in effect, "include that boilerplate and
 >> reference *if* any of those words appear in the document".
 >
 > case sensitive (not included for "must" but included if "MUST")
 >
 > Scott

Hi, Scott (et al.),

FWIW, the text I've been using for a while in the .doc template is as 
follows, to avoid the lowercase being misinterpreted as 2119-related:

----
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
document are to be interpreted as described in RFC-2119 [RFC2119].
In this document, these words will appear with that interpretation 
only when in ALL CAPS. Lower case uses of these words are not to be 
interpreted as carrying RFC-2119 significance.
----

I also include the following convention to help people actually find 
such keyword statements, which I try very hard to list as single 
bullets, rather than in running text:

----
In this document, the characters ">>" preceding an indented line(s) 
indicates a compliance requirement statement using the key words 
listed above. This convention aids reviewers in quickly identifying   or 
finding the explicit compliance requirements of this RFC.
----

Joe

From sob@harvard.edu  Wed Feb  2 09:43:21 2011
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 129983A6C01 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:43:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.271
X-Spam-Level: 
X-Spam-Status: No, score=-102.271 tagged_above=-999 required=5 tests=[AWL=0.328, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C23RHUl-Y+5H for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:43:20 -0800 (PST)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id 6116F3A6D7C for <wgchairs@ietf.org>; Wed,  2 Feb 2011 09:43:20 -0800 (PST)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 82E8082AE0F; Wed,  2 Feb 2011 12:46:40 -0500 (EST)
To: sob@harvard.edu, touch@isi.edu
Subject: Re: RFC2119 keywords
In-Reply-To: <4D49982C.4010504@isi.edu>
Message-Id: <20110202174640.82E8082AE0F@newdev.eecs.harvard.edu>
Date: Wed,  2 Feb 2011 12:46:40 -0500 (EST)
From: sob@harvard.edu (Scott O. Bradner)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 17:43:21 -0000

> In this document, these words will appear with that interpretation 
> only when in ALL CAPS. Lower case uses of these words are not to be 
> interpreted as carrying RFC-2119 significance.

agree - done that myself

From loa@pi.nu  Wed Feb  2 09:47:40 2011
Return-Path: <loa@pi.nu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 865E13A6C01 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:47:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.112
X-Spam-Level: 
X-Spam-Status: No, score=-102.112 tagged_above=-999 required=5 tests=[AWL=-0.132, BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Of4AVeFEJ1F for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:47:39 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id BCE433A6BAB for <wgchairs@ietf.org>; Wed,  2 Feb 2011 09:47:39 -0800 (PST)
Received: from [10.154.12.191] (unknown [192.165.126.74]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 12C622A8001 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 18:50:59 +0100 (CET)
Message-ID: <4D499984.8060306@pi.nu>
Date: Wed, 02 Feb 2011 18:51:00 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: RFC2119 keywords
References: <20110202174640.82E8082AE0F@newdev.eecs.harvard.edu>
In-Reply-To: <20110202174640.82E8082AE0F@newdev.eecs.harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 17:47:40 -0000

"MUST NOT" and "must not" is OK, but "MUST not" is not

/Loa

On 2011-02-02 18:46, Scott O. Bradner wrote:
>> In this document, these words will appear with that interpretation
>> only when in ALL CAPS. Lower case uses of these words are not to be
>> interpreted as carrying RFC-2119 significance.
>
> agree - done that myself

From touch@isi.edu  Wed Feb  2 09:54:44 2011
Return-Path: <touch@isi.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A3653A6D79 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:54:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.603
X-Spam-Level: 
X-Spam-Status: No, score=-102.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rE77wQyJOgVg for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:54:43 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 9BDD33A67B7 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 09:54:43 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p12HvL2r004040 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 09:57:21 -0800 (PST)
Message-ID: <4D499B01.4090805@isi.edu>
Date: Wed, 02 Feb 2011 09:57:21 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>
Subject: Re: RFC2119 keywords
References: <20110202174640.82E8082AE0F@newdev.eecs.harvard.edu> <4D499984.8060306@pi.nu>
In-Reply-To: <4D499984.8060306@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 17:54:44 -0000

FWIW, I prefer that use of 2119 language is deliberate, so "must not" 
doesn't carry any particular importance to me - which is why I use the 
sentence below to be very clear on that point.

I can add "Lower case and mixed case uses of these words..." to handle 
the case you raise, if needed.

Joe

On 2/2/2011 9:51 AM, Loa Andersson wrote:
> "MUST NOT" and "must not" is OK, but "MUST not" is not
>
> /Loa
>
> On 2011-02-02 18:46, Scott O. Bradner wrote:
>>> In this document, these words will appear with that interpretation
>>> only when in ALL CAPS. Lower case uses of these words are not to be
>>> interpreted as carrying RFC-2119 significance.
>>
>> agree - done that myself

From ogud@ogud.com  Wed Feb  2 09:58:58 2011
Return-Path: <ogud@ogud.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C34A3A6DAF for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:58:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EPK89sC2Etcp for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 09:58:57 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 1E3203A6DAA for <wgchairs@ietf.org>; Wed,  2 Feb 2011 09:58:57 -0800 (PST)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p12I2GiL055156 for <wgchairs@ietf.org>; Wed, 2 Feb 2011 13:02:16 -0500 (EST) (envelope-from ogud@ogud.com)
Message-ID: <4D499C21.7020801@ogud.com>
Date: Wed, 02 Feb 2011 13:02:09 -0500
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: RFC2119 keywords
References: <4D496651.3030006@viagenie.ca>
In-Reply-To: <4D496651.3030006@viagenie.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 17:58:58 -0000

On 02/02/2011 9:12 AM, Marc Blanchet wrote:
> Hello,
> almost all drafts copy the following text:
> "The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
> "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
> and "OPTIONAL" in this document are to be interpreted as ...
> "
> and also add a reference to RFC2119.
>
>
> Instead of copying all the time, and given that everybody knows this
> stuff, why don't we instead put this text or reference it in the
> document boilerplate generated by xml2rfc or else?
>
> Marc.

Related question, is there a reason to list the words that do not
appear in the document?
To me the list in each document should only reflect the words used.
I would like xml2rfc generate this just like table of contents.
To accomplish this we may need to use something like &MUST each time we 
want to use a 2119 word.
A further advantage of this is when/if we move from TXT as the output
we can have the 2119 MUST show up differently than plain MUST.

	Olafur

From sob@harvard.edu  Wed Feb  2 10:00:35 2011
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 744733A6DAA for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 10:00:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.285
X-Spam-Level: 
X-Spam-Status: No, score=-102.285 tagged_above=-999 required=5 tests=[AWL=0.314, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g1EXXfR253sG for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 10:00:34 -0800 (PST)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id D4E503A6DB1 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 10:00:34 -0800 (PST)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id E8AE182AEE1; Wed,  2 Feb 2011 13:03:54 -0500 (EST)
To: ogud@ogud.com, wgchairs@ietf.org
Subject: Re: RFC2119 keywords
In-Reply-To: <4D499C21.7020801@ogud.com>
Message-Id: <20110202180354.E8AE182AEE1@newdev.eecs.harvard.edu>
Date: Wed,  2 Feb 2011 13:03:54 -0500 (EST)
From: sob@harvard.edu (Scott O. Bradner)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 18:00:35 -0000

> Related question, is there a reason to list the words that do not
> appear in the document?

(as the author of 2119) - no
but the suggested wording in 2119 is inclusive

Scott

From dwing@cisco.com  Wed Feb  2 10:03:07 2011
Return-Path: <dwing@cisco.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC3353A6D86 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 10:03:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.518
X-Spam-Level: 
X-Spam-Status: No, score=-110.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9+0oLLzCRB7U for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 10:03:07 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 20A323A6C01 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 10:03:07 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEBABIsSU2rRN+J/2dsb2JhbACWOoFljH1ziCyYI5sohVMEhHiTNA
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 02 Feb 2011 18:06:27 +0000
Received: from dwingWS ([10.32.240.197]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id p12I6QGO009666; Wed, 2 Feb 2011 18:06:27 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Marc Blanchet'" <marc.blanchet@viagenie.ca>, "'Working Group Chairs'" <wgchairs@ietf.org>
References: <4D496651.3030006@viagenie.ca>
In-Reply-To: <4D496651.3030006@viagenie.ca>
Subject: RE: RFC2119 keywords
Date: Wed, 2 Feb 2011 10:06:26 -0800
Message-ID: <085001cbc303$e916b9d0$bb442d70$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvC40MkbW7RE2XLRri23w/FSyssDgAIE55g
Content-Language: en-us
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 18:03:08 -0000

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Marc Blanchet
> Sent: Wednesday, February 02, 2011 6:13 AM
> To: Working Group Chairs
> Subject: RFC2119 keywords
> 
> Hello,
>   almost all drafts copy the following text:
> "The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
>              "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
>              and "OPTIONAL" in this document are to be interpreted as
> ...
> "
> and also add a reference to RFC2119.
> 
> 
> Instead of copying all the time, and given that everybody knows this
> stuff, why don't we instead put this text or reference it in the
> document boilerplate generated by xml2rfc or else?

That text is missing the "NOT RECOMMENDED" keyword.  See
http://www.rfc-editor.org/errata_search.php?eid=499

-d



From sob@harvard.edu  Wed Feb  2 10:04:12 2011
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 122AF3A6DB2 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 10:04:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.297
X-Spam-Level: 
X-Spam-Status: No, score=-102.297 tagged_above=-999 required=5 tests=[AWL=0.302, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lQA+atabrDlH for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 10:04:11 -0800 (PST)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id 73F903A6C01 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 10:04:11 -0800 (PST)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id A0F6582AF61; Wed,  2 Feb 2011 13:07:31 -0500 (EST)
To: dwing@cisco.com, marc.blanchet@viagenie.ca, wgchairs@ietf.org
Subject: RE: RFC2119 keywords
In-Reply-To: <085001cbc303$e916b9d0$bb442d70$@com>
Message-Id: <20110202180731.A0F6582AF61@newdev.eecs.harvard.edu>
Date: Wed,  2 Feb 2011 13:07:31 -0500 (EST)
From: sob@harvard.edu (Scott O. Bradner)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 18:04:12 -0000

> That text is missing the "NOT RECOMMENDED" keyword. 

correct - you can not imagine how many times I've been told that :-)

Scott

From dwing@cisco.com  Wed Feb  2 10:21:00 2011
Return-Path: <dwing@cisco.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B19A93A6DAF for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 10:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.537
X-Spam-Level: 
X-Spam-Status: No, score=-110.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TYNKe593w253 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 10:20:58 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id DA7D63A6DC7 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 10:20:58 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEBANMvSU2rR7Hu/2dsb2JhbACWOoFljH1zoFKbJ4VTBIR4kks
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 02 Feb 2011 18:24:19 +0000
Received: from dwingWS ([10.32.240.197]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p12IOI1j027212; Wed, 2 Feb 2011 18:24:18 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Scott O. Bradner'" <sob@harvard.edu>, <marc.blanchet@viagenie.ca>, <wgchairs@ietf.org>
References: <085001cbc303$e916b9d0$bb442d70$@com> <20110202180731.A0F6582AF61@newdev.eecs.harvard.edu>
In-Reply-To: <20110202180731.A0F6582AF61@newdev.eecs.harvard.edu>
Subject: RE: RFC2119 keywords
Date: Wed, 2 Feb 2011 10:24:18 -0800
Message-ID: <087301cbc306$67e608e0$37b21aa0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvDBBbMQs94Q/IaSNmnMq+fyCUW8wAAkxjg
Content-Language: en-us
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 18:21:00 -0000

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Scott O. Bradner
> Sent: Wednesday, February 02, 2011 10:08 AM
> To: dwing@cisco.com; marc.blanchet@viagenie.ca; wgchairs@ietf.org
> Subject: RE: RFC2119 keywords
> 
> > That text is missing the "NOT RECOMMENDED" keyword.
> 
> correct - you can not imagine how many times I've been told that :-)

:-)

-d



From john-ietf@jck.com  Wed Feb  2 10:32:26 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C6253A6D9F for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 10:32:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.966
X-Spam-Level: 
X-Spam-Status: No, score=-102.966 tagged_above=-999 required=5 tests=[AWL=-0.367, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XiBjq1-LE5Mi for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 10:32:25 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id AC1863A6C11 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 10:32:25 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PkhYP-0004Wq-7t; Wed, 02 Feb 2011 13:35:45 -0500
Date: Wed, 02 Feb 2011 13:35:44 -0500
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@shinkuro.com>, wgchairs@ietf.org
Subject: Re: RFC2119 keywords
Message-ID: <E301E6072A8EE1E53F827436@PST.JCK.COM>
In-Reply-To: <20110202153117.GA7903@shinkuro.com>
References: <4D496651.3030006@viagenie.ca> <20110202153117.GA7903@shinkuro.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 18:32:26 -0000

--On Wednesday, February 02, 2011 10:31 -0500 Andrew Sullivan
<ajs@shinkuro.com> wrote:

> On Wed, Feb 02, 2011 at 09:12:33AM -0500, Marc Blanchet wrote:
>> Instead of copying all the time, and given that everybody
>> knows this   stuff, why don't we instead put this text or
>> reference it in the   document boilerplate generated by
>> xml2rfc or else?
> 
> For xml2rfc, I think a directive would be needed.  It
> shouldn't be in every draft -- there are drafts that don't
> have it or, more often, include it and don't actually use any
> of the keywords.

The added advantage of doing something directive-like is that,
despite widely-adopted habits, pushback from nits checkers,
etc., the use of those definitions for those terms is still not
mandatory.

   john




From adam@nostrum.com  Wed Feb  2 11:24:34 2011
Return-Path: <adam@nostrum.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4A1E3A6D79 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 11:24:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.924
X-Spam-Level: 
X-Spam-Status: No, score=-101.924 tagged_above=-999 required=5 tests=[AWL=0.676, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id emlu078fRxsC for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 11:24:34 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id A31BA3A6C41 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 11:24:33 -0800 (PST)
Received: from hydra-3.local (99-152-144-32.lightspeed.dllstx.sbcglobal.net [99.152.144.32]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p12JRonF012464 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 2 Feb 2011 13:27:51 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4D49B036.9060203@nostrum.com>
Date: Wed, 02 Feb 2011 13:27:50 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Scott O. Bradner" <sob@harvard.edu>
Subject: Re: RFC2119 keywords
References: <20110202180354.E8AE182AEE1@newdev.eecs.harvard.edu>
In-Reply-To: <20110202180354.E8AE182AEE1@newdev.eecs.harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 99.152.144.32 is authenticated by a trusted mechanism)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 19:24:34 -0000

On 2/2/11 12:03, Feb 2, Scott O. Bradner wrote:
>> Related question, is there a reason to list the words that do not
>> appear in the document?
> (as the author of 2119) - no

The i-d submission tool recently started complaining if you don't use 
the exact, EXACT 2119 language. I had a tailored version of that text 
that only mentioned the actual terms used in the document, and i-d 
submission refused to let it go through.

So Scott's "no" is more philosophical than real. As a practical matter, 
it seems the tools are forcing the answer to be "yes."

/a

From sob@harvard.edu  Wed Feb  2 11:25:51 2011
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B5C13A6CDC for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 11:25:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.309
X-Spam-Level: 
X-Spam-Status: No, score=-102.309 tagged_above=-999 required=5 tests=[AWL=0.290, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sjyay-iUFCb8 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 11:25:50 -0800 (PST)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id 7B80A3A6C41 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 11:25:49 -0800 (PST)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 2763B82B3B1; Wed,  2 Feb 2011 14:29:09 -0500 (EST)
To: adam@nostrum.com, sob@harvard.edu
Subject: Re: RFC2119 keywords
In-Reply-To: <4D49B036.9060203@nostrum.com>
Message-Id: <20110202192909.2763B82B3B1@newdev.eecs.harvard.edu>
Date: Wed,  2 Feb 2011 14:29:09 -0500 (EST)
From: sob@harvard.edu (Scott O. Bradner)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 19:25:51 -0000

> So Scott's "no" is more philosophical than real.

correct

it is my opinion of how things should work

Scott

From john-ietf@jck.com  Wed Feb  2 12:12:57 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 244C83A6D1D for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 12:12:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.956
X-Spam-Level: 
X-Spam-Status: No, score=-102.956 tagged_above=-999 required=5 tests=[AWL=-0.357, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GowYhU9RIp4d for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 12:12:56 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 4EC333A6BA9 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 12:12:56 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Pkj7e-00078P-R2; Wed, 02 Feb 2011 15:16:14 -0500
Date: Wed, 02 Feb 2011 15:16:14 -0500
From: John C Klensin <john-ietf@jck.com>
To: Adam Roach <adam@nostrum.com>, "Scott O. Bradner" <sob@harvard.edu>
Subject: Re: RFC2119 keywords
Message-ID: <0985CB437E162DA583B788FF@PST.JCK.COM>
In-Reply-To: <4D49B036.9060203@nostrum.com>
References: <20110202180354.E8AE182AEE1@newdev.eecs.harvard.edu> <4D49B036.9060203@nostrum.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 20:12:57 -0000

--On Wednesday, February 02, 2011 13:27 -0600 Adam Roach
<adam@nostrum.com> wrote:

> On 2/2/11 12:03, Feb 2, Scott O. Bradner wrote:
>>> Related question, is there a reason to list the words that
>>> do not appear in the document?
>> (as the author of 2119) - no
> 
> The i-d submission tool recently started complaining if you
> don't use the exact, EXACT 2119 language. I had a tailored
> version of that text that only mentioned the actual terms used
> in the document, and i-d submission refused to let it go
> through.
> 
> So Scott's "no" is more philosophical than real. As a
> practical matter, it seems the tools are forcing the answer to
> be "yes."

If anyone cares enough, there should probably be forceful
pushback on any provisions of those tools that enforce rules
that derive neither from from formal community consensus nor
from IESG statements to which the community had an opportunity
to object.  Especially for I-Ds, flexibility for authors to make
sensible decisions is really an important asset.

That said, I have personally have other windmills with which to
do battle and am perfectly welcome to do manual submissions if
the tools get in my way.

    john






From carlsonj@workingcode.com  Wed Feb  2 14:33:52 2011
Return-Path: <carlsonj@workingcode.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7DABA3A6C72 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 14:33:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PRNzlE5rxx56 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 14:33:51 -0800 (PST)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id 51B483A6C6E for <wgchairs@ietf.org>; Wed,  2 Feb 2011 14:33:51 -0800 (PST)
Received: from [75.150.68.97] (carlson [75.150.68.97]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id p12Mb7pp016478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2011 17:37:09 -0500 (EST)
Message-ID: <4D49DC93.7070503@workingcode.com>
Date: Wed, 02 Feb 2011 17:37:07 -0500
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1.7) Gecko/20100214 Lightning/1.0b1 Thunderbird/3.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: RFC2119 keywords
References: <20110202180354.E8AE182AEE1@newdev.eecs.harvard.edu>	<4D49B036.9060203@nostrum.com> <0985CB437E162DA583B788FF@PST.JCK.COM>
In-Reply-To: <0985CB437E162DA583B788FF@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-SIHOPE-DCC-3-Metrics: carlson; whitelist
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 22:33:52 -0000

On 02/02/11 15:16, John C Klensin wrote:
> --On Wednesday, February 02, 2011 13:27 -0600 Adam Roach
> <adam@nostrum.com> wrote:
>> So Scott's "no" is more philosophical than real. As a
>> practical matter, it seems the tools are forcing the answer to
>> be "yes."
> 
> If anyone cares enough, there should probably be forceful
> pushback on any provisions of those tools that enforce rules
> that derive neither from from formal community consensus nor
> from IESG statements to which the community had an opportunity
> to object.  Especially for I-Ds, flexibility for authors to make
> sensible decisions is really an important asset.

For what it's worth (and it may not be much, as we're really talking
about minutiae here), I happen to like the insistence on the exact 2119
wording.  Having exactly the same wording in each document means that I
don't have to refer back to some author's quirky definition of the
keywords when reading a document.  If I encounter "RECOMMENDED," it
means the same thing everywhere, and I don't have to go check whether
this particular author happened to elide it from the list or (worse)
gave it different meaning.

The only way to go one better would be to remove this and other silly
boilerplate from all RFCs, and simply have a single "#include" for all
of it.  But that's obviously "impossible" in a world of laws and
regulations.  :-/

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

From ajs@shinkuro.com  Wed Feb  2 14:47:53 2011
Return-Path: <ajs@shinkuro.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A44563A6C80 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 14:47:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g45YkDHi7nfe for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 14:47:52 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id CBB763A6864 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 14:47:52 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 9861C1ECB421 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 22:51:12 +0000 (UTC)
Date: Wed, 2 Feb 2011 17:51:10 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: wgchairs@ietf.org
Subject: Re: RFC2119 keywords
Message-ID: <20110202225110.GB11578@shinkuro.com>
References: <20110202180354.E8AE182AEE1@newdev.eecs.harvard.edu> <4D49B036.9060203@nostrum.com> <0985CB437E162DA583B788FF@PST.JCK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0985CB437E162DA583B788FF@PST.JCK.COM>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 22:47:53 -0000

On Wed, Feb 02, 2011 at 03:16:14PM -0500, John C Klensin wrote:

> If anyone cares enough, there should probably be forceful
> pushback on any provisions of those tools that enforce rules
> that derive neither from from formal community consensus nor
> from IESG statements to which the community had an opportunity
> to object.  Especially for I-Ds, flexibility for authors to make
> sensible decisions is really an important asset.

Since this is now actually kind of back on topic for wgchairs, that
was the reason I replied in the first place, and it's tightly linked
to my usual complaint that the idnits process is about form, not
content.

I think as WG chairs, we ought to be concerned that process rules and
bureaucratic efficiency are gradually encroaching on the ability to
get work done easily and swiftly.  I find it not a little ironic that
old-fashioned tools like *roff -- or just an Emacs formatting
template, for all that -- are increasingly putting out formally
correct but idnits-rejected drafts because the tools are being tested
not against a spec, but against an implementation.  Given our usual
rules for protocols, that says something very bad about where our
values really lie.  I personally find xml2rfc easier to use than the
alternatives (although still much harder than, say, a well-designed
LaTeX style); but I see no reason why I need repeatedly to explain to
people who have been producing RFCs for 25 years why their template
suddenly doesn't work even though they have all the right boilerplate.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From johnl@iecc.com  Wed Feb  2 18:20:30 2011
Return-Path: <johnl@iecc.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 848383A67B6 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 18:20:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.705
X-Spam-Level: 
X-Spam-Status: No, score=-110.705 tagged_above=-999 required=5 tests=[AWL=0.494, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tARe8WfSWjAI for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 18:20:29 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 36A143A67B3 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 18:20:29 -0800 (PST)
Received: (qmail 70069 invoked from network); 3 Feb 2011 02:23:48 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 3 Feb 2011 02:23:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=1776.4d4a11b4.k1102; i=johnl@user.iecc.com; bh=Xqx4ChhheDlfLQHdu9YyALJ6HlefIQHPucGOcLbuxbA=; b=L4yrmJJfjCLwICsmr6kVpcLGTNsAu6YUfoeRx/BbTh8VcuzGrzl0mBAJQ0oTwL4SP2YdWfKH+1eZoGuKHg/BBmDQIaESvo4557xIUpRShMIK5QQu0Z2GdLWxK5mpKx/0dBKGelXXG+AOspxfy56ZCnqv+5Drq+eQvVIzVSZ3P3Y=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 3 Feb 2011 02:23:48 -0000
Message-ID: <20110203022348.6005.qmail@joyce.lan>
From: John Levine <johnl@iecc.com>
To: wgchairs@ietf.org
Subject: Re: Canonical RFC formatting
In-Reply-To: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 02:20:30 -0000

Here's what I saw when I tried to read it:

In article <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com> you write:
>SGkgSm9lLCBjYW4geW91IGNsYXJpZnkgd2hhdCBkbyB5b3UgbWVhbiBieSAiZG9lcyBub3Qgc3Vw
>cG9ydCBVVEYtOD8gSSBhbSBjb21wb3NpbmcgdGhpcyBtYWlsIG9uIGFuIEFuZHJvaWQgcGhvbmUg

 etc.

"It works fine for me" is rarely a useful metric.

R's,
John

From jhutz@cmu.edu  Wed Feb  2 21:50:08 2011
Return-Path: <jhutz@cmu.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 345693A6874 for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 21:50:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.513
X-Spam-Level: 
X-Spam-Status: No, score=-106.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JBL4uU3qvqJd for <wgchairs@core3.amsl.com>; Wed,  2 Feb 2011 21:50:07 -0800 (PST)
Received: from smtp01.srv.cs.cmu.edu (SMTP01.SRV.CS.CMU.EDU [128.2.217.196]) by core3.amsl.com (Postfix) with ESMTP id 1435A3A6872 for <wgchairs@ietf.org>; Wed,  2 Feb 2011 21:50:06 -0800 (PST)
Received: from [128.2.184.182] (JHUTZ-DYN5.PC.CS.CMU.EDU [128.2.184.182]) (authenticated bits=0) by smtp01.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id p135rPK6020491 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Feb 2011 00:53:26 -0500 (EST)
Subject: Re: RFC2119 keywords
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Andrew Sullivan <ajs@shinkuro.com>
In-Reply-To: <29802_1296687077_p12MpGxB006861_20110202225110.GB11578@shinkuro.com>
References: <20110202180354.E8AE182AEE1@newdev.eecs.harvard.edu> <4D49B036.9060203@nostrum.com> <0985CB437E162DA583B788FF@PST.JCK.COM> <29802_1296687077_p12MpGxB006861_20110202225110.GB11578@shinkuro.com>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 03 Feb 2011 00:53:25 -0500
Message-ID: <1296712405.3280.9.camel@destiny>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 7bit
X-Scanned-By: mimedefang-cmuscs on 128.2.217.196
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 05:50:08 -0000

On Wed, 2011-02-02 at 17:51 -0500, Andrew Sullivan wrote:

> I find it not a little ironic that
> old-fashioned tools like *roff -- or just an Emacs formatting
> template, for all that -- are increasingly putting out formally
> correct but idnits-rejected drafts because the tools are being tested
> not against a spec, but against an implementation. 

Unfortunately, it's impossible to test against a spec.  Unless the spec
is written in some formal language, in which case you've simply reduced
the problem to verifying the "spec" does as intended.

What is possible is to test against a test suite.  I don't have any
special knowledge here, but I suspect that tools like idnits _do_ get
tested against a test suite, but that the test cases primarily
concentrate on discovering false accepts rather than false rejects.  It
might be useful to produce some test cases which are prone to being
falsely rejected for some reason.  Perhaps this could even be done
semi-automatically, by collecting documents which were rejected but
later discovered to be valid.

Perhaps it would also be useful for the submission process to be less
strict.  Certainly it is necessary to check the legal boilerplate, but
many of our current requirements, such as correct use of RFC2119, are
things that should be enforced late in the development lifecycle, not
during I-D submission while someone is trying to get a -00 in before the
deadline.

-- Jeff


From john-ietf@jck.com  Thu Feb  3 06:05:53 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 425563A67D9 for <wgchairs@core3.amsl.com>; Thu,  3 Feb 2011 06:05:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.946
X-Spam-Level: 
X-Spam-Status: No, score=-102.946 tagged_above=-999 required=5 tests=[AWL=-0.347, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bo3fTaWUCQHG for <wgchairs@core3.amsl.com>; Thu,  3 Feb 2011 06:05:52 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 03FE13A6940 for <wgchairs@ietf.org>; Thu,  3 Feb 2011 06:05:52 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Pkzs1-0005aa-RM; Thu, 03 Feb 2011 09:09:14 -0500
Date: Thu, 03 Feb 2011 09:09:13 -0500
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@shinkuro.com>, wgchairs@ietf.org
Subject: Re: RFC2119 keywords
Message-ID: <E171F8D44EC302BB3CFB84B0@PST.JCK.COM>
In-Reply-To: <20110202225110.GB11578@shinkuro.com>
References: <20110202180354.E8AE182AEE1@newdev.eecs.harvard.edu> <4D49B036.9060203@nostrum.com> <0985CB437E162DA583B788FF@PST.JCK.COM> <20110202225110.GB11578@shinkuro.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 14:05:53 -0000

FWIW, +1

--On Wednesday, February 02, 2011 17:51 -0500 Andrew Sullivan
<ajs@shinkuro.com> wrote:

> Since this is now actually kind of back on topic for wgchairs,
> that was the reason I replied in the first place, and it's
> tightly linked to my usual complaint that the idnits process
> is about form, not content.
> 
> I think as WG chairs, we ought to be concerned that process
> rules and bureaucratic efficiency are gradually encroaching on
> the ability to get work done easily and swiftly.  I find it
> not a little ironic that old-fashioned tools like *roff -- or
> just an Emacs formatting template, for all that -- are
> increasingly putting out formally correct but idnits-rejected
> drafts because the tools are being tested not against a spec,
> but against an implementation.  Given our usual rules for
> protocols, that says something very bad about where our values
> really lie.  I personally find xml2rfc easier to use than the
> alternatives (although still much harder than, say, a
> well-designed LaTeX style); but I see no reason why I need
> repeatedly to explain to people who have been producing RFCs
> for 25 years why their template suddenly doesn't work even
> though they have all the right boilerplate.





From john-ietf@jck.com  Thu Feb  3 06:25:03 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E901A3A6974 for <wgchairs@core3.amsl.com>; Thu,  3 Feb 2011 06:25:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.937
X-Spam-Level: 
X-Spam-Status: No, score=-102.937 tagged_above=-999 required=5 tests=[AWL=-0.338, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3rVZMhNqQNNC for <wgchairs@core3.amsl.com>; Thu,  3 Feb 2011 06:24:59 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id D4A073A690B for <wgchairs@ietf.org>; Thu,  3 Feb 2011 06:24:58 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Pl0AR-0005zZ-UX; Thu, 03 Feb 2011 09:28:16 -0500
Date: Thu, 03 Feb 2011 09:28:14 -0500
From: John C Klensin <john-ietf@jck.com>
To: James Carlson <carlsonj@workingcode.com>
Subject: Re: RFC2119 keywords
Message-ID: <E2677790F172AD11EB4871D6@PST.JCK.COM>
In-Reply-To: <4D49DC93.7070503@workingcode.com>
References: <20110202180354.E8AE182AEE1@newdev.eecs.harvard.edu> <4D49B036.9060203@nostrum.com> <0985CB437E162DA583B788FF@PST.JCK.COM> <4D49DC93.7070503@workingcode.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 14:25:03 -0000

--On Wednesday, February 02, 2011 17:37 -0500 James Carlson
<carlsonj@workingcode.com> wrote:

> For what it's worth (and it may not be much, as we're really
> talking about minutiae here), I happen to like the insistence
> on the exact 2119 wording.  Having exactly the same wording in
> each document means that I don't have to refer back to some
> author's quirky definition of the keywords when reading a
> document.  If I encounter "RECOMMENDED," it means the same
> thing everywhere, and I don't have to go check whether this
> particular author happened to elide it from the list or (worse)
> gave it different meaning.

Again fwiw, it has gotten to be the case that any attempt to use
non-2119 definitions gets a lot of pushback from the IESG (and,
when anyone notices, the broader community).  I don't see that
as a problem as long as the pushback comes from the sort of
motivation you suggest -- that it is normally better if everyone
uses the same terms to mean the same thing and that doing
otherwise should require a significant reason and significant
justification.

However, there are situations in which the 2119 definitions are
actually a poor match for what is intended.    In my personal
experience, those definitions usually well matched to protocol
specifications ("Technical Specifications" in 2026-speak) but
sometimes less well matched to Applicability Statements or even
BCPs.  Giving up on the flexibility to convince the community
that different definitions are appropriate and doing so in the
interest of mindless consistency, or as Andrew put it, process
rules and bureaucratic efficiency, seems to me to be a really
poor idea.

    john



From sob@harvard.edu  Thu Feb  3 06:30:51 2011
Return-Path: <sob@harvard.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E21D83A697B for <wgchairs@core3.amsl.com>; Thu,  3 Feb 2011 06:30:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.32
X-Spam-Level: 
X-Spam-Status: No, score=-102.32 tagged_above=-999 required=5 tests=[AWL=0.279, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jbE1SL5+FZ67 for <wgchairs@core3.amsl.com>; Thu,  3 Feb 2011 06:30:51 -0800 (PST)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id CDFC33A6989 for <wgchairs@ietf.org>; Thu,  3 Feb 2011 06:30:50 -0800 (PST)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 7943382D709; Thu,  3 Feb 2011 09:34:12 -0500 (EST)
To: carlsonj@workingcode.com, john-ietf@jck.com
Subject: Re: RFC2119 keywords
In-Reply-To: <E2677790F172AD11EB4871D6@PST.JCK.COM>
Message-Id: <20110203143412.7943382D709@newdev.eecs.harvard.edu>
Date: Thu,  3 Feb 2011 09:34:12 -0500 (EST)
From: sob@harvard.edu (Scott O. Bradner)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 14:30:52 -0000

I agree with John that 2119 is not a good match for non-technical
documents - that said, one can (and I have) added text to say how to
do a match - see e.g., RFC 2418

  RFC 2119 defines the use of these key words to help make the intent 
  of standards track documents as clear as possible.  The same key words 
  are used in this document to help smooth WG operation and reduce the chance
  for confusion about the processes.

not an ideal match but a way to explain

Scott

From duerst@it.aoyama.ac.jp  Fri Feb  4 02:39:36 2011
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B4F93A6B84 for <wgchairs@core3.amsl.com>; Fri,  4 Feb 2011 02:39:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.342
X-Spam-Level: 
X-Spam-Status: No, score=-99.342 tagged_above=-999 required=5 tests=[AWL=-1.262, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, SARE_FWDLOOK=1.666, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KQhpP3bLU66R for <wgchairs@core3.amsl.com>; Fri,  4 Feb 2011 02:39:34 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by core3.amsl.com (Postfix) with ESMTP id 51D2F3A6B83 for <wgchairs@ietf.org>; Fri,  4 Feb 2011 02:39:33 -0800 (PST)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id p14AgrN8005658 for <wgchairs@ietf.org>; Fri, 4 Feb 2011 19:42:53 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 59f8_aef3_84f80fb6_304b_11e0_9284_001d096c566a; Fri, 04 Feb 2011 19:42:53 +0900
Received: from [IPv6:::1] ([133.2.210.1]:36535) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S14C78F5> for <wgchairs@ietf.org> from <duerst@it.aoyama.ac.jp>; Fri, 4 Feb 2011 19:42:51 +0900
Message-ID: <4D4BACB4.6000602@it.aoyama.ac.jp>
Date: Fri, 04 Feb 2011 16:37:24 +0900
From: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Canonical RFC formatting
References: <i5iwg1lpw2xo2ev2ylq9s1wk.1296629545532@email.android.com>	<4D4905EF.1060807@isi.edu>	<AANLkTi=9Dw_6d45K_YkbxV2ZrCWeF3UndJNvBJpW3A4-@mail.gmail.com> <4D49093E.3030809@isi.edu> <4D49394F.7070108@it.aoyama.ac.jp> <4D4994B1.5050103@isi.edu>
In-Reply-To: <4D4994B1.5050103@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 10:39:36 -0000

Hello Joe,

On 2011/02/03 2:30, Joe Touch wrote:
> Hi, Martin,
>
> On 2/2/2011 3:00 AM, "Martin J. Dürst" wrote:
>> A few comments:
>>
>> - The attached file was in UTF-8, but the Content-Type didn't say so.
>> (I'm not sure if it had, that would have fixed the problem, but at
>> least I think we should follow our own standards.)
>
> I dragged and dropped it into Thunderbird, FWIW.

Yes. You dragged it from the file system, which doesn't know the 
encoding. Thunderbird implementers had a few options for this case:
1) Ask the user (doesn't want to be bothered)
2) Assume it's the system encoding (may be wrong)
3) Leave the encoding information out (not wrong, but not right either)

The implementers choose 3).

>> - Browsers and email readers (for the main part of an email) should work
>> without problems these days because they actually handle Content-Type
>> charset information, which the file systems in general are very bad
>> at doing.
>
> Maybe they should, but the evidence is that they do not.

They do as far as the text is under their control (e.g. you type it in).

Btw, it gets quite a bit easier if HTML is used, because HTML can carry 
the encoding information internally. So it might be better to try an 
experiment with UTF-8 + HTML (clean, of course).

> The
> drag-and-drop into Tbird didn't set the content type as needed, and as a
> result the iPhone/iPad didn't render it correctly.
>
>> - A file like this one is a tough job for software that tries to
>> deal with both legacy encoding (e.g. ISO-8859-1 in Western Europe)
>> and UTF-8. There's very little actual UTF-8 in there, and it's
>> towards the end. (That could be fixed with a BOM, but then that
>> might create other problems.)
>
> That might be very typical, e.g., if only an example or two and the
> authors' names actually were outside the existing RFC ASCII subset.

Yes indeed. One way to fix this would be to replace some regular spaces 
with UTF-8 non-breaking spaces or something along these lines.


On 2011/02/03 2:34, Joe Touch wrote:

 >> But I have a problem with the attitude. Some systems are broken. That's
 >> no reason to have people's name mangled on the documents that they 
write.

It's not only people's names. It's also examples, where in some cases it 
gets quite a bit more complicated to understand an example if it is 
reduced to ASCII that if it uses some actual non-ASCII characters.

 > The two alternatives are:
 >
 > - honor the specific requirements of a subset of people
 > - make text readable to everyone

This is not an either/or tradeoff. First, in most cases, the ASCII part 
of the text is still readeable in such software even if the encoding is 
not detected correctly. Second, on the level of human readability, 
examples such as the Art of Computer Programming books by Knuth show 
that you can use the authors' original name (even if that's Arabic or 
Chinese) without affecting readability.

 > That's the same trade-off that led us to IP, which "works everywhere",
 > but, AFAICT, is best nearly nowhere.

If we had stopped at IP, the Internet would be a very boring place. 
Fortunately, we have built a lot of very useful applications on top of it.

 > IMO, sticking to the RFC ASCII subset is no different. We *are* eating
 > our own dogfood, or at least living by our own standards.

Distributing RFCs in electronic form was a big, forward-looking step 
when it was started decades ago. *Paper* was the lowest common 
denominator at that time. Compared with that, the current discussions 
about UTF-8 or HTML (clean and simple) or whatever are really, really 
small fish.

 > Yes, this is a good reason to fix these apps/systems. But it's also
 > evidence that shifting to UTF-8 will make the RFCs less accessible than
 > they are now.

It's difficult to beat US-ASCII (except on IBM mainframes), so even in 
10 years, I guess you will be able to find a hair in the UTF-8 soup. But 
I don't think requiring *absolutely perfect UTF-8 support everywhere* 
makes sense at all.


Regards,   Martin.

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

From tlyu@mit.edu  Fri Feb  4 13:03:30 2011
Return-Path: <tlyu@mit.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3303F3A69A9 for <wgchairs@core3.amsl.com>; Fri,  4 Feb 2011 13:03:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.28
X-Spam-Level: 
X-Spam-Status: No, score=-101.28 tagged_above=-999 required=5 tests=[AWL=1.319, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yurAfxLFl6jW for <wgchairs@core3.amsl.com>; Fri,  4 Feb 2011 13:03:29 -0800 (PST)
Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU [18.9.25.15]) by core3.amsl.com (Postfix) with ESMTP id 31C573A67C1 for <wgchairs@ietf.org>; Fri,  4 Feb 2011 13:03:29 -0800 (PST)
X-AuditID: 1209190f-b7c1dae000000a2b-a8-4d4c6a6e87c6
Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) by dmz-mailsec-scanner-4.mit.edu (Symantec Brightmail Gateway) with SMTP id D7.48.02603.E6A6C4D4; Fri,  4 Feb 2011 16:06:54 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id p14L6sM4024650;  Fri, 4 Feb 2011 16:06:54 -0500
Received: from cathode-dark-space.mit.edu (CATHODE-DARK-SPACE.MIT.EDU [18.18.1.96]) (authenticated bits=56) (User authenticated as tlyu@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p14L6qOO016889 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 4 Feb 2011 16:06:53 -0500 (EST)
Received: (from tlyu@localhost) by cathode-dark-space.mit.edu (8.12.9.20060308) id p14L6q2u019914; Fri, 4 Feb 2011 16:06:52 -0500 (EST)
To: Adam Roach <adam@nostrum.com>
Subject: Re: RFC2119 keywords
References: <20110202180354.E8AE182AEE1@newdev.eecs.harvard.edu> <4D49B036.9060203@nostrum.com>
From: Tom Yu <tlyu@MIT.EDU>
Date: Fri, 04 Feb 2011 16:06:52 -0500
In-Reply-To: <4D49B036.9060203@nostrum.com> (Adam Roach's message of "Wed, 02 Feb 2011 13:27:50 -0600")
Message-ID: <ldv8vxvpl03.fsf@cathode-dark-space.mit.edu>
Lines: 20
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Brightmail-Tracker: AAAAAA==
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 21:03:30 -0000

Adam Roach <adam@nostrum.com> writes:

> On 2/2/11 12:03, Feb 2, Scott O. Bradner wrote:
>>> Related question, is there a reason to list the words that do not
>>> appear in the document?
>> (as the author of 2119) - no
>
> The i-d submission tool recently started complaining if you don't use
> the exact, EXACT 2119 language. I had a tailored version of that text
> that only mentioned the actual terms used in the document, and i-d
> submission refused to let it go through.
>
> So Scott's "no" is more philosophical than real. As a practical
> matter, it seems the tools are forcing the answer to be "yes."
>
> /a

Tools forcing the exact list from RFC 2119 would be a problem in
documents including ASN.1 syntax, because the all-caps "OPTIONAL" has
a specific non-2119 meaning in ASN.1.

From wwwrun@core3.amsl.com  Mon Feb  7 08:01:52 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 56D763A6E12; Mon,  7 Feb 2011 08:01:52 -0800 (PST)
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 80th IETF - Working Group/BOF Scheduling REMINDER 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110207160152.56D763A6E12@core3.amsl.com>
Date: Mon,  7 Feb 2011 08:01:52 -0800 (PST)
Cc: irsg@isi.edu
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2011 16:01:52 -0000

-----------------------------------------------------------------
80th IETF Prague, Czech Republic
Meeting Dates: March 27-April 1, 2011
Host: CZ.NIC
-----------------------------------------------------------------
IETF meetings start Monday morning and run through Friday mid-afternoon
(15:15).

We are accepting scheduling requests for all Working Groups and BOFs
starting today.  The milestones and deadlines for scheduling-related
activities are as follows:

NOTE: cutoff dates are subject to change.

*2011-02-14 (Monday): Cutoff date for requests to schedule Working Group
meetings at 17:00 PT (01:00 Tuesday, February 15 UTC). To request a
Working Group session, use the IETF Meeting Session Request Tool. 
*2011-02-14 (Monday): Cutoff date for Area Directors to approve BOFs at
17:00 PT (01:00 Tuesday, February 15 UTC). 
*2011-02-24 (Thursday): Preliminary agenda published for comment. 
*2011-02-28 (Monday): Cutoff date for requests to reschedule Working
Group and BOF meetings 17:00 PT (01:00 Tuesday, March 1 UTC). 
*2011-02-28 (Monday): Working Group Chair approval for initial document
(Version -00) submissions appreciated by 17:00 PT (01:00 Tuesday, March 1
UTC). 
*2011-03-04 (Friday): Final agenda to be published. 
*2011-03-16 (Wednesday): Draft Working Group agendas due by 17:00 PT
(01:00 Thursday, March 17 UTC), upload using IETF Meeting Materials
Management Tool. 
*2011-03-21 (Monday): Revised Working Group agendas due by 17:00 PT
(01:00 Tuesday, March 22 UTC), upload using IETF Meeting Materials
Management Tool.

Submitting Requests for Working Group and BOF Sessions

Please submit requests to schedule your Working Group sessions using the
"IETF Meeting Session Request Tool," a Web-based tool for submitting all
of the information that the Secretariat requires to schedule your
sessions.

The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

Please send requests to schedule your BOF sessions to agenda@ietf.org. 
Please include the acronym of your BOF in the subject line of the message,
and include all of the information specified in item (4) of "Requesting
Meeting Sessions at IETF Meetings" in the body.  (This document is
included below.)

Submitting Session Agendas

For the convenience of meeting attendees, we ask that you submit the
agendas for your Working Group sessions as early as possible.  Draft
Working Group agendas are due Wednesday, March 16, 2011 by 17:00 PT (01:00
Thursday, March 17 UTC).  Revised Working Group agendas are due no later
than Monday, March 21, 2011 at 17:00 PT (01:00 Tuesday, March 22 UTC). 
The proposed agenda for a BOF session should be submitted along with your
request for a session.  Please be sure to copy your Area Director on that
message.

Please submit the agendas for your Working Group sessions using the "IETF
Meeting Materials Management Tool," a Web-based tool for making your
meeting agenda, minutes, and presentation slides available to the
community before, during, and after an IETF meeting.  If you are a BOF
chair, then you may use the tool to submit a revised agenda as well as
other materials for your BOF once the BOF has been approved.

The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi

Additional information about this tool is available at:

http://www.ietf.org/instructions/meeting_materials_tool.html

Agendas submitted via the tool will be available to the public on the
"IETF Meeting Materials" Web page as soon as they are submitted.

The URL for the "IETF 80 Meeting Materials" Web page is:

https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=80

If you are a Working Group chair, then you already have accounts on the
"IETF Meeting Session Request Tool" and the "IETF Meeting Materials
Management Tool."  The same User ID and password will work for both tools.

 If you are a BOF chair who is not also a Working Group chair, then you
will be given an account on the "IETF Meeting Materials Management Tool"
when your BOF has been approved.  If you require assistance in using
either tool, or wish to report a bug, then please send a message to:
ietf-action@ietf.org.
===============================================================
For your convenience, comprehensive information on requesting meeting
sessions at IETF 80 is presented below:

1. Requests to schedule Working Group sessions should be submitted using
the "IETF Meeting Session Request Tool," a Web-based tool for submitting
all of the information required by the Secretariat to schedule your
sessions.  The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

If you require an account on this tool, or assistance in using it, then
please send a message to ietf-action@ietf.org.  If you are unable to use
the tool, then you may send your request via e-mail to agenda@ietf.org,
with a copy to the appropriate Area Director(s).

Requests to schedule BOF sessions must be sent to agenda@ietf.org with a
copy to the appropriate Area Director(s).

When submitting a Working Group or BOF session request by e-mail, please
include the Working Group or BOF acronym in the Subject line.

2. BOFs will NOT be scheduled unless the Area Director(s) approved
request is accompanied by a BOF'S FULL NAME AND ACRONYM, AREA, CHAIR(S)
NAME(S) (given together with e-mail address(es)), AN AGENDA AND FULL
DESCRIPTION, and the information requested in (4) below. (Please read the
BOF Procedure at: http://www.ietf.org/ietf/1bof-procedures.txt before
requesting a session for a BOF.)

3. A Working Group may request either one or two sessions.  If your
Working Group requires more than two sessions, then your request must be
approved by an Area Director.  Additional sessions will be assigned, based
on availability, after Monday, February 28, 2011 at 17:00 PT (01:00
Tuesday, March 1 UTC), the cut-off date for requests to reschedule a
session.

4. You MUST provide the following information before a Working Group or
BOF session will be scheduled:

   a. Working Group or BOF full name with acronym in brackets: 

   b. AREA under which Working Group or BOF appears:

   c. CONFLICTS you wish to avoid, please be as specific as possible:

   d. Expected Attendance:

   e. Special requests:

   f. Number of sessions:

   g. Length of session: 
      - 1 hour 
      - 1 1/2 hours
      - 2 hours 
      - 2 1/2 hours

For more information on scheduling Working Group and BOF sessions, please
refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and Procedures"
(http://www.ietf.org/rfc/rfc2418.txt).
===============================================================
For your convenience please find here a list of the IETF Area Directors
with their e-mail addresses:

IETF Chair 
Russ Housley <housley@vigilsec.com>

Applications Area (app)
Alexey Melnikov <alexey.melnikov@isode.com>
Peter Saint-Andre <stpeter@stpeter.im> 

Internet Area (int) 
Jari Arkko <jari.arkko@piuha.net>
Ralph Droms <rdroms.ietf@gmail.com> 

Operations & Management Area (ops) 
Ronald Bonica <rbonica@juniper.net>
Dan Romascanu <dromasca@avaya.com>

Real-time Applications and Infrastructure Area (rai)
Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Robert Sparks <rjsparks@nostrum.com> 

Routing Area (rtg) 
Stewart Bryant <stbryant@cisco.com>
Adrian Farrel <adrian.farrel@huawei.com> 

Security Area (sec) 
Tim Polk <tim.polk@nist.gov>
Sean Turner <turners@ieca.com> 

Transport Area (tsv) 
Lars Eggert <lars.eggert@nokia.com>
David Harrington <ietfdbh@comcast.net> 
===========================================================
79th IETF Meeting Attendance Number

Working Group	

6lowpan - 108
6man - 178
abfab - 50
alto - 110
ancp - 26
apparea (AG) - 74
armd BOF - 70
atoca - 37
autoconf - 29
avt - 82
avt (2nd session) - 55
behave - 103
bmwg - 15
ccamp - 100
ccamp (2nd session) - 79
codec - 59
conex - 43
core - 81
core (2nd session) - 67
cuss - 14
decade - 59
dhc - 28
dime - 14
dispatch - 61
dnsext - 99
dnsop - 96
drinks - 37
dtnrg (RG) - 22
eai - 31
ecrit - 37
eman - 56
emu - 21
fecframe - 8
forces - 23
geopriv - 39
grow - 44
hiprg (RG) - 44
hokey - 22
iddtspec - 13
idr - 80
intarea (AG) - 111
ipfix - 37
ippm - 23
ipsecme - 28
iri - 18
isis - 52
isms - 14
karp - 50
kidns - 122
kitten - 31
krb-wg - 12
l2vpn - 119
l3vpn - 92
lisp - 69
lwip - 156
manet - 35
martini - 36
mboned - 18
mext - 69
mext (second session) - 64
mif - 114
mip4 - 10
mmusic - 50
mpls - 150
mpls (2nd session) - 158
mptcp - 101
mptcp (2nd session) - 64
msec - 33
multimob - 61
nbs BPF - 101
nea - 30
netconf - 42
netext - 52
netmod - 28
nfsv4 - 25
nfsv4 (second session) - NO SHEETS
opsarea (AG) - 40
opsawg - 51
ospf - 53
p2psip - 58
pcp - 59
pim - 47
pkix - 30
ppsp - 38
precis - 31
pwe3 - 140
radext - 20
roll - 72
rtgarea (AG) - 135
rtgwg - 56
saag (AG) - 90
samrg (RG) - 20
savi - 67
scap BOF - 44
sidr - 68
sipclf - 19
sipcore - 57
siprec - 44
softwire - 110
tcpm - 25
tictoc - 17
trill - 72
tsvarea (AG) - 33
tsvwg - 65
v6ops - 203
v6ops (second session) - 159
vcarddav - 13
vnrg (RG) - 48
websec - 101


From spromano@unina.it  Wed Feb  9 09:27:02 2011
Return-Path: <spromano@unina.it>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5819E3A67D1 for <wgchairs@core3.amsl.com>; Wed,  9 Feb 2011 09:27:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.719
X-Spam-Level: 
X-Spam-Status: No, score=-100.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2uynpE3+yHyh for <wgchairs@core3.amsl.com>; Wed,  9 Feb 2011 09:27:01 -0800 (PST)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by core3.amsl.com (Postfix) with ESMTP id 237013A67B5 for <wgchairs@ietf.org>; Wed,  9 Feb 2011 09:27:00 -0800 (PST)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id p19HR5PH009997 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 9 Feb 2011 18:27:06 +0100
Message-ID: <4D52CE63.70208@unina.it>
Date: Wed, 09 Feb 2011 18:26:59 +0100
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; it; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: Experiment: tools for remote participation in IETF80 -- update
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Feb 2011 17:27:02 -0000

Dear all,

first of all, let me thank all of the WG chairs who've given Meetecho a 
try: some of you have provided us with invaluable feedback (special 
thanks to Stevan Leiden and Andrew Malis from Verizon!) which did really 
help us target the weaknesses of our system and tackle them 
accordingly.  We've worked hard lately to improve Meetecho in all its 
aspects.

This is the list of all the major changes we've made to the system:

  * first of all, installing the Desktop Clients is now much easier. 
Specifically, a new installer has been created for the MAC OS desktop 
client, together with an updater application should new patches become 
available. If you already installed the client a few days ago, make sure 
you update it to take advantage of the latest features;

  * the bug a few of you had with the OS hosts file has been fixed, so 
no need to tweak such file is needed anymore;

* a few folks had some issues with the SIP call associated with the 
conference. This was due to a re-INVITE we made use of to negotiate the 
BFCP (floor control) channel (see RFC4583), which some network 
components (see providers, especially in the US) seemed to discard for 
some reason, thus invalidating the session. We fixed this issue by 
removing the mentioned re-INVITE and negotiating the BFCP channel 
through XMPP. This decreases our adherence to the standards (sic!), but 
seems to be the only way to have the client work out of the box in all 
environments;

  * we worked a lot on the Web Interface, by improving the existing 
functionality and adding new features. This interface now also includes 
a simple integrated VoIP client, which means now you really don't need 
to install anything to access Meetecho if you don't want to. Ironically, 
our approach is very similar to the one Jonathan Rosenberg just proposed 
in his latest RTCWEB draft: we use a custom JavaScript API to request 
the call, which is then originated server side via SIP. The media then 
flow via RTP between the system and the browser by means of a Java 
applet we implemented ad hoc. Obviously, the other alternatives to 
access the conference media (RTSP/SIP/PSTN) are still available.
BTW, we just introduced, with the same approach, support for video 
(reception only, at the moment).

That's all, for now. I really encourage you to give Meetecho a try now. 
We'll appreciate your feedback, comments and suggestions, as usual. 
Don't even hesitate to contact us should you be willing to make a guided 
tour of the platform capabilities.

Cheers,

Simon

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From wwwrun@core3.amsl.com  Fri Feb 11 10:08:05 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 8D67C3A6860; Fri, 11 Feb 2011 10:08:05 -0800 (PST)
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: RFP for XML2RFC Tool Development 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110211180805.8D67C3A6860@core3.amsl.com>
Date: Fri, 11 Feb 2011 10:08:05 -0800 (PST)
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, tools-development@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2011 18:08:05 -0000

The IETF Administrative Oversight Committee (IAOC), on behalf of the IETF,
announces this Request for Proposals to develop the XML2RFC Tool.  The
successful bidder will enter into a contract with the Internet Society.

The xml2rfc tool is used by authors to compose Internet-Drafts, and by
the RFC Production Center to produce RFCs. This development effort is
intended to produce an xml2rfc tool that uses the same input format with a
few enhancements, is easy to install on a personal machine, and is easier
to maintain and enhance in the future.

Bidders may elect to submit one or two bids to reflect the development
approach they follow, that is, whether to develop a single program that
handles the xml2rfc input format and does all of the processing, and/or
develop software that handles the xml2rfc input format and then calls upon
other existing programs as needed to complete the overall task (such as
nroff or gruff).

The python language is preferred for software development. Proposals that
use other languages will be accepted, but the proposal must explain why a
language other than python is desirable for the tasks proposed.

The xml2rfc tool created under this effort shall generate output
comparable to the current version xml2rfc.tcl with the current version of
the DTD, fixes to the various issues that have been filed in and resolved
in the bug tracker, and the enhancements specified below. To the greatest
extent practical, the xml2rfc tools needs to accommodate changes by the
community to the DTD; several potential improvements are under discussion.


During development, the winning bidder may come up with ideas to further
improve the usability or maintainability of the xml2rfc tools.

The Statement of Work includes three sections. The first section
discusses xml2rfc processing. The second section describes required
enhancements to the current xml2rfc tool. The third section describes the
preferred nroff output, which is a bit different than the nroff output
produced by the current xml2rfc tool.

The RFP can be found at: http://iaoc.ietf.org/rfpsrfis.html 

Proposals must be received via email at rpelletier@isoc.org no later than
February 28, 2011 5:00 P.M. EST.  All questions/inquiries must be
submitted in writing and must be received no later than midnight, EST,
February 18, 2011.  Responses to questions and inquiries shall be posted
online at:  http://iaoc.ietf.org/rfpsrfis.html by midnight, EST, February
22, 1011. 

The point of contact regarding this RFP is the IETF Administrative
Director, Ray Pelletier, iad@ietf.org.

From wwwrun@core3.amsl.com  Mon Feb 14 09:10:27 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id BBDD33A6D48; Mon, 14 Feb 2011 09:10:27 -0800 (PST)
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 80th IETF - Working Group/BOF Scheduling REMINDER - Closes today  at 5PM PT 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110214171027.BBDD33A6D48@core3.amsl.com>
Date: Mon, 14 Feb 2011 09:10:27 -0800 (PST)
Cc: irsg@isi.edu
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Feb 2011 17:10:28 -0000

-----------------------------------------------------------------
80th IETF Prague, Czech Republic
Meeting Dates: March 27-April 1, 2011
Host: CZ.NIC
-----------------------------------------------------------------
IETF meetings start Monday morning and run through Friday mid-afternoon
(15:15).

We are accepting scheduling requests for all Working Groups and BOFs
starting today.  The milestones and deadlines for scheduling-related
activities are as follows:

NOTE: cutoff dates are subject to change.

*2011-02-14 (Monday): Cutoff date for requests to schedule Working Group
meetings at 17:00 PT (01:00 Tuesday, February 15 UTC). To request a
Working Group session, use the IETF Meeting Session Request Tool. 
*2011-02-14 (Monday): Cutoff date for Area Directors to approve BOFs at
17:00 PT (01:00 Tuesday, February 15 UTC). 
*2011-02-24 (Thursday): Preliminary agenda published for comment. 
*2011-02-28 (Monday): Cutoff date for requests to reschedule Working
Group and BOF meetings 17:00 PT (01:00 Tuesday, March 1 UTC). 
*2011-02-28 (Monday): Working Group Chair approval for initial document
(Version -00) submissions appreciated by 17:00 PT (01:00 Tuesday, March 1
UTC). 
*2011-03-04 (Friday): Final agenda to be published. 
*2011-03-16 (Wednesday): Draft Working Group agendas due by 17:00 PT
(01:00 Thursday, March 17 UTC), upload using IETF Meeting Materials
Management Tool. 
*2011-03-21 (Monday): Revised Working Group agendas due by 17:00 PT
(01:00 Tuesday, March 22 UTC), upload using IETF Meeting Materials
Management Tool.

Submitting Requests for Working Group and BOF Sessions

Please submit requests to schedule your Working Group sessions using the
"IETF Meeting Session Request Tool," a Web-based tool for submitting all
of the information that the Secretariat requires to schedule your
sessions.

The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

Please send requests to schedule your BOF sessions to agenda@ietf.org. 
Please include the acronym of your BOF in the subject line of the message,
and include all of the information specified in item (4) of "Requesting
Meeting Sessions at IETF Meetings" in the body.  (This document is
included below.)

Submitting Session Agendas

For the convenience of meeting attendees, we ask that you submit the
agendas for your Working Group sessions as early as possible.  Draft
Working Group agendas are due Wednesday, March 16, 2011 by 17:00 PT (01:00
Thursday, March 17 UTC).  Revised Working Group agendas are due no later
than Monday, March 21, 2011 at 17:00 PT (01:00 Tuesday, March 22 UTC). 
The proposed agenda for a BOF session should be submitted along with your
request for a session.  Please be sure to copy your Area Director on that
message.

Please submit the agendas for your Working Group sessions using the "IETF
Meeting Materials Management Tool," a Web-based tool for making your
meeting agenda, minutes, and presentation slides available to the
community before, during, and after an IETF meeting.  If you are a BOF
chair, then you may use the tool to submit a revised agenda as well as
other materials for your BOF once the BOF has been approved.

The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi

Additional information about this tool is available at:

http://www.ietf.org/instructions/meeting_materials_tool.html

Agendas submitted via the tool will be available to the public on the
"IETF Meeting Materials" Web page as soon as they are submitted.

The URL for the "IETF 80 Meeting Materials" Web page is:

https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=80

If you are a Working Group chair, then you already have accounts on the
"IETF Meeting Session Request Tool" and the "IETF Meeting Materials
Management Tool."  The same User ID and password will work for both tools.


If you are a BOF chair who is not also a Working Group chair, then you
will be given an account on the "IETF Meeting Materials Management Tool"
when your BOF has been approved.  If you require assistance in using
either tool, or wish to report a bug, then please send a message to:
ietf-action@ietf.org.
===============================================================
For your convenience, comprehensive information on requesting meeting
sessions at IETF 80 is presented below:

1. Requests to schedule Working Group sessions should be submitted using
the "IETF Meeting Session Request Tool," a Web-based tool for submitting
all of the information required by the Secretariat to schedule your
sessions.  The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

If you require an account on this tool, or assistance in using it, then
please send a message to ietf-action@ietf.org.  If you are unable to use
the tool, then you may send your request via e-mail to agenda@ietf.org,
with a copy to the appropriate Area Director(s).

Requests to schedule BOF sessions must be sent to agenda@ietf.org with a
copy to the appropriate Area Director(s).

When submitting a Working Group or BOF session request by e-mail, please
include the Working Group or BOF acronym in the Subject line.

2. BOFs will NOT be scheduled unless the Area Director(s) approved
request is accompanied by a BOF'S FULL NAME AND ACRONYM, AREA, CHAIR(S)
NAME(S) (given together with e-mail address(es)), AN AGENDA AND FULL
DESCRIPTION, and the information requested in (4) below. (Please read the
BOF Procedure at: http://www.ietf.org/ietf/1bof-procedures.txt before
requesting a session for a BOF.)

3. A Working Group may request either one or two sessions.  If your
Working Group requires more than two sessions, then your request must be
approved by an Area Director.  Additional sessions will be assigned, based
on availability, after Monday, February 28, 2011 at 17:00 PT (01:00
Tuesday, March 1 UTC), the cut-off date for requests to reschedule a
session.

4. You MUST provide the following information before a Working Group or
BOF session will be scheduled:

  a. Working Group or BOF full name with acronym in brackets: 

  b. AREA under which Working Group or BOF appears:

  c. CONFLICTS you wish to avoid, please be as specific as possible:

  d. Expected Attendance:

  e. Special requests:

  f. Number of sessions:

  g. Length of session: 
     - 1 hour 
     - 1 1/2 hours
     - 2 hours 
     - 2 1/2 hours

For more information on scheduling Working Group and BOF sessions, please
refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and Procedures"
(http://www.ietf.org/rfc/rfc2418.txt).
===============================================================
For your convenience please find here a list of the IETF Area Directors
with their e-mail addresses:

IETF Chair 
Russ Housley <housley@vigilsec.com>

Applications Area (app)
Alexey Melnikov <alexey.melnikov@isode.com>
Peter Saint-Andre <stpeter@stpeter.im> 

Internet Area (int) 
Jari Arkko <jari.arkko@piuha.net>
Ralph Droms <rdroms.ietf@gmail.com> 

Operations & Management Area (ops) 
Ronald Bonica <rbonica@juniper.net>
Dan Romascanu <dromasca@avaya.com>

Real-time Applications and Infrastructure Area (rai)
Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Robert Sparks <rjsparks@nostrum.com> 

Routing Area (rtg) 
Stewart Bryant <stbryant@cisco.com>
Adrian Farrel <adrian.farrel@huawei.com> 

Security Area (sec) 
Tim Polk <tim.polk@nist.gov>
Sean Turner <turners@ieca.com> 

Transport Area (tsv) 
Lars Eggert <lars.eggert@nokia.com>
David Harrington <ietfdbh@comcast.net> 
===========================================================
79th IETF Meeting Attendance Number

Working Group	

6lowpan - 108
6man - 178
abfab - 50
alto - 110
ancp - 26
apparea (AG) - 74
armd BOF - 70
atoca - 37
autoconf - 29
avt - 82
avt (2nd session) - 55
behave - 103
bmwg - 15
ccamp - 100
ccamp (2nd session) - 79
codec - 59
conex - 43
core - 81
core (2nd session) - 67
cuss - 14
decade - 59
dhc - 28
dime - 14
dispatch - 61
dnsext - 99
dnsop - 96
drinks - 37
dtnrg (RG) - 22
eai - 31
ecrit - 37
eman - 56
emu - 21
fecframe - 8
forces - 23
geopriv - 39
grow - 44
hiprg (RG) - 44
hokey - 22
iddtspec - 13
idr - 80
intarea (AG) - 111
ipfix - 37
ippm - 23
ipsecme - 28
iri - 18
isis - 52
isms - 14
karp - 50
kidns - 122
kitten - 31
krb-wg - 12
l2vpn - 119
l3vpn - 92
lisp - 69
lwip - 156
manet - 35
martini - 36
mboned - 18
mext - 69
mext (second session) - 64
mif - 114
mip4 - 10
mmusic - 50
mpls - 150
mpls (2nd session) - 158
mptcp - 101
mptcp (2nd session) - 64
msec - 33
multimob - 61
nbs BPF - 101
nea - 30
netconf - 42
netext - 52
netmod - 28
nfsv4 - 25
nfsv4 (second session) - NO SHEETS
opsarea (AG) - 40
opsawg - 51
ospf - 53
p2psip - 58
pcp - 59
pim - 47
pkix - 30
ppsp - 38
precis - 31
pwe3 - 140
radext - 20
roll - 72
rtgarea (AG) - 135
rtgwg - 56
saag (AG) - 90
samrg (RG) - 20
savi - 67
scap BOF - 44
sidr - 68
sipclf - 19
sipcore - 57
siprec - 44
softwire - 110
tcpm - 25
tictoc - 17
trill - 72
tsvarea (AG) - 33
tsvwg - 65
v6ops - 203
v6ops (second session) - 159
vcarddav - 13
vnrg (RG) - 48
websec - 101

From paul.hoffman@vpnc.org  Tue Feb 15 07:55:40 2011
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 93ED73A6BCD for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 07:55:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.966
X-Spam-Level: 
X-Spam-Status: No, score=-99.966 tagged_above=-999 required=5 tests=[AWL=-0.520, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xjZX2Zk7y82K for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 07:55:39 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id A7E8F3A6B77 for <wgchairs@ietf.org>; Tue, 15 Feb 2011 07:55:39 -0800 (PST)
Received: from MacBook-08.local (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p1FFu4Kq000922 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Tue, 15 Feb 2011 08:56:05 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D5AA214.7070202@vpnc.org>
Date: Tue, 15 Feb 2011 07:56:04 -0800
From: Paul Hoffman <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: wgchairs <wgchairs@ietf.org>
Subject: New tool feature useful for WGs
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 15:55:40 -0000

Greetings again. The IETF Tools Team just made an update to the tools 
site that should be useful to WGs.

Before, when a new draft came out and you wanted to tell the WG to look 
at the diffs, you had to send the URL 
"http://tools.ietf.org/rfcdiff?url2=" with the draft name including the 
new draft number ("draft-ietf-somewg-someprot-10.txt"). When the next 
draft was issued, that email became stale; worse, someone reading it 
wouldn't know that they were looking at a diff that was not pointing to 
the latest draft.

Now, when you use 
"http://tools.ietf.org/rfcdiff?url2=draft-ietf-somewg-someprot" with no 
version number, the tool automatically diffs the current version with 
the previous one. You no longer have to (or want to!) include the 
version number when you are asking the WG to look at the diffs.

Hat tip to the Tools Team, yet again!

--Paul Hoffman, Director
--VPN Consortium


From bertietf@bwijnen.net  Tue Feb 15 08:37:40 2011
Return-Path: <bertietf@bwijnen.net>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FE3C3A6B7C for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 08:37:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.41
X-Spam-Level: 
X-Spam-Status: No, score=-102.41 tagged_above=-999 required=5 tests=[AWL=0.189, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DTO1c9dJpPDn for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 08:37:39 -0800 (PST)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id E372D3A6A8B for <wgchairs@ietf.org>; Tue, 15 Feb 2011 08:37:38 -0800 (PST)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1PpNtx-0005dv-1J; Tue, 15 Feb 2011 17:38:02 +0100
Received: from dog.ripe.net ([193.0.1.217] helo=BWMACBOOK.local) by dodo.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1PpNtw-0001Gy-Rv; Tue, 15 Feb 2011 17:37:20 +0100
Message-ID: <4D5AABC0.2030906@bwijnen.net>
Date: Tue, 15 Feb 2011 17:37:20 +0100
From: "Bert (IETF) Wijnen" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: New tool feature useful for WGs
References: <4D5AA214.7070202@vpnc.org>
In-Reply-To: <4D5AA214.7070202@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4fa2f4221659c8f59286697a062dad096
Cc: wgchairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 16:37:40 -0000

That sounds great.

I also recall (but I may be wrong), that at some point in the past, if we did
This for a specific document, (following is an example):
    http://tools.ietf.org/wg/netconf/draft-ietf-netconf-4741bis/
that we would get all the revisions and for each rev a ptr to the diffs.
The example above seems to show only rev 0, 1 and 2, while we are
now up to rev 10.

Did this change on purpose or by accident?

Bert


On 2/15/11 4:56 PM, Paul Hoffman wrote:
> Greetings again. The IETF Tools Team just made an update to the tools site that should be useful to WGs.
>
> Before, when a new draft came out and you wanted to tell the WG to look at the diffs, you had to send the URL 
> "http://tools.ietf.org/rfcdiff?url2=" with the draft name including the new draft number ("draft-ietf-somewg-someprot-10.txt"). 
> When the next draft was issued, that email became stale; worse, someone reading it wouldn't know that they were looking at a diff 
> that was not pointing to the latest draft.
>
> Now, when you use "http://tools.ietf.org/rfcdiff?url2=draft-ietf-somewg-someprot" with no version number, the tool automatically 
> diffs the current version with the previous one. You no longer have to (or want to!) include the version number when you are 
> asking the WG to look at the diffs.
>
> Hat tip to the Tools Team, yet again!
>
> --Paul Hoffman, Director
> --VPN Consortium
>
>


From henrik@levkowetz.com  Tue Feb 15 08:55:41 2011
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69E0A3A6D10 for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 08:55:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z9OIB13sNbTY for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 08:55:40 -0800 (PST)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id 028043A6C30 for <wgchairs@ietf.org>; Tue, 15 Feb 2011 08:55:40 -0800 (PST)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:51895 helo=dyn-fg117.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1PpOBt-0003sA-Jt; Tue, 15 Feb 2011 17:55:54 +0100
Message-ID: <4D5AB019.3060605@levkowetz.com>
Date: Tue, 15 Feb 2011 17:55:53 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Bert (IETF) Wijnen" <bertietf@bwijnen.net>
References: <4D5AA214.7070202@vpnc.org> <4D5AABC0.2030906@bwijnen.net>
In-Reply-To: <4D5AABC0.2030906@bwijnen.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: bertietf@bwijnen.net, paul.hoffman@vpnc.org, wgchairs@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: New tool feature useful for WGs
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: wgchairs <wgchairs@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 16:55:41 -0000

Hi Bert,

On 2011-02-15 17:37 Bert (IETF) Wijnen said:
> That sounds great.
> 
> I also recall (but I may be wrong), that at some point in the past, if we did
> This for a specific document, (following is an example):
>     http://tools.ietf.org/wg/netconf/draft-ietf-netconf-4741bis/
> that we would get all the revisions and for each rev a ptr to the diffs.
> The example above seems to show only rev 0, 1 and 2, while we are
> now up to rev 10.
> 
> Did this change on purpose or by accident?

Two of the tools servers (which recently was taken into rotation) are
lagging.  I'm fixing this now.

Best,

	Henrik

> Bert
> 
> 
> On 2/15/11 4:56 PM, Paul Hoffman wrote:
>> Greetings again. The IETF Tools Team just made an update to the tools site that should be useful to WGs.
>>
>> Before, when a new draft came out and you wanted to tell the WG to look at the diffs, you had to send the URL 
>> "http://tools.ietf.org/rfcdiff?url2=" with the draft name including the new draft number ("draft-ietf-somewg-someprot-10.txt"). 
>> When the next draft was issued, that email became stale; worse, someone reading it wouldn't know that they were looking at a diff 
>> that was not pointing to the latest draft.
>>
>> Now, when you use "http://tools.ietf.org/rfcdiff?url2=draft-ietf-somewg-someprot" with no version number, the tool automatically 
>> diffs the current version with the previous one. You no longer have to (or want to!) include the version number when you are 
>> asking the WG to look at the diffs.
>>
>> Hat tip to the Tools Team, yet again!
>>
>> --Paul Hoffman, Director
>> --VPN Consortium
>>
>>
> 
> 

From pkyzivat@cisco.com  Tue Feb 15 10:05:16 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 877193A6D2A for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 10:05:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QeQpKAhJgORp for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 10:05:15 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id F0A853A69A6 for <wgchairs@ietf.org>; Tue, 15 Feb 2011 10:05:14 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqUGAN9OWk1AZnwM/2dsb2JhbACXP44bc6Bcm2mFXgSFBYZ9gzU
X-IronPort-AV: E=Sophos;i="4.60,475,1291593600"; d="scan'208";a="215939625"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 15 Feb 2011 18:05:40 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p1FI5eG3014506 for <wgchairs@ietf.org>; Tue, 15 Feb 2011 18:05:40 GMT
Message-ID: <4D5AC074.7070206@cisco.com>
Date: Tue, 15 Feb 2011 13:05:40 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: New tool feature useful for WGs
References: <4D5AA214.7070202@vpnc.org> <4D5AABC0.2030906@bwijnen.net> <4D5AB019.3060605@levkowetz.com>
In-Reply-To: <4D5AB019.3060605@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 18:05:16 -0000

It would be nice when you did an ID or RFC search, or just used the url 
to a particular draft, if the page that came up, in addition to the 
other links it has, had a link to the diff from prior version.

	Thanks,
	Paul

On 2/15/2011 11:55 AM, Henrik Levkowetz wrote:
> Hi Bert,
>
> On 2011-02-15 17:37 Bert (IETF) Wijnen said:
>> That sounds great.
>>
>> I also recall (but I may be wrong), that at some point in the past, if we did
>> This for a specific document, (following is an example):
>>      http://tools.ietf.org/wg/netconf/draft-ietf-netconf-4741bis/
>> that we would get all the revisions and for each rev a ptr to the diffs.
>> The example above seems to show only rev 0, 1 and 2, while we are
>> now up to rev 10.
>>
>> Did this change on purpose or by accident?
>
> Two of the tools servers (which recently was taken into rotation) are
> lagging.  I'm fixing this now.
>
> Best,
>
> 	Henrik
>
>> Bert
>>
>>
>> On 2/15/11 4:56 PM, Paul Hoffman wrote:
>>> Greetings again. The IETF Tools Team just made an update to the tools site that should be useful to WGs.
>>>
>>> Before, when a new draft came out and you wanted to tell the WG to look at the diffs, you had to send the URL
>>> "http://tools.ietf.org/rfcdiff?url2=" with the draft name including the new draft number ("draft-ietf-somewg-someprot-10.txt").
>>> When the next draft was issued, that email became stale; worse, someone reading it wouldn't know that they were looking at a diff
>>> that was not pointing to the latest draft.
>>>
>>> Now, when you use "http://tools.ietf.org/rfcdiff?url2=draft-ietf-somewg-someprot" with no version number, the tool automatically
>>> diffs the current version with the previous one. You no longer have to (or want to!) include the version number when you are
>>> asking the WG to look at the diffs.
>>>
>>> Hat tip to the Tools Team, yet again!
>>>
>>> --Paul Hoffman, Director
>>> --VPN Consortium
>>>
>>>
>>
>>
>

From tony@att.com  Tue Feb 15 10:56:10 2011
Return-Path: <tony@att.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2AEEA3A6D6C for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 10:56:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IBySs0wwVzTC for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 10:56:09 -0800 (PST)
Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id 284C43A6D6A for <wgchairs@ietf.org>; Tue, 15 Feb 2011 10:56:08 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-12.tower-161.messagelabs.com!1297796194!48977881!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 12429 invoked from network); 15 Feb 2011 18:56:34 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-12.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Feb 2011 18:56:34 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p1FIuvNT020595 for <wgchairs@ietf.org>; Tue, 15 Feb 2011 13:56:57 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p1FIup93020459 for <wgchairs@ietf.org>; Tue, 15 Feb 2011 13:56:51 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p1FIuRTS019584 for <wgchairs@ietf.org>; Tue, 15 Feb 2011 13:56:27 -0500
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p1FIuKUZ019451 for <wgchairs@ietf.org>; Tue, 15 Feb 2011 13:56:20 -0500
Received: from [135.70.149.217] (vpn-135-70-149-217.vpn.mwst.att.com[135.70.149.217]) by maillennium.att.com (mailgw1) with ESMTP id <20110215185619gw100e4l50e> (Authid: tony); Tue, 15 Feb 2011 18:56:20 +0000
X-Originating-IP: [135.70.149.217]
Message-ID: <4D5ACC53.9010205@att.com>
Date: Tue, 15 Feb 2011 13:56:19 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: New tool feature useful for WGs
References: <4D5AA214.7070202@vpnc.org> <4D5AABC0.2030906@bwijnen.net>	<4D5AB019.3060605@levkowetz.com> <4D5AC074.7070206@cisco.com>
In-Reply-To: <4D5AC074.7070206@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 18:56:10 -0000

The URL tools.ietf.org/html/draft-whatever (or, 
tools.ietf.org/html/rfc####) has such links.

     Tony Hansen
     tony@att.com

On 2/15/2011 1:05 PM, Paul Kyzivat wrote:
> It would be nice when you did an ID or RFC search, or just used the 
> url to a particular draft, if the page that came up, in addition to 
> the other links it has, had a link to the diff from prior version.
>
>     Thanks,
>     Paul
>
> On 2/15/2011 11:55 AM, Henrik Levkowetz wrote:
>> Hi Bert,
>>
>> On 2011-02-15 17:37 Bert (IETF) Wijnen said:
>>> That sounds great.
>>>
>>> I also recall (but I may be wrong), that at some point in the past, 
>>> if we did
>>> This for a specific document, (following is an example):
>>>      http://tools.ietf.org/wg/netconf/draft-ietf-netconf-4741bis/
>>> that we would get all the revisions and for each rev a ptr to the 
>>> diffs.
>>> The example above seems to show only rev 0, 1 and 2, while we are
>>> now up to rev 10.
>>>
>>> Did this change on purpose or by accident?
>>
>> Two of the tools servers (which recently was taken into rotation) are
>> lagging.  I'm fixing this now.
>>
>> Best,
>>
>>     Henrik
>>
>>> Bert
>>>
>>>
>>> On 2/15/11 4:56 PM, Paul Hoffman wrote:
>>>> Greetings again. The IETF Tools Team just made an update to the 
>>>> tools site that should be useful to WGs.
>>>>
>>>> Before, when a new draft came out and you wanted to tell the WG to 
>>>> look at the diffs, you had to send the URL
>>>> "http://tools.ietf.org/rfcdiff?url2=" with the draft name including 
>>>> the new draft number ("draft-ietf-somewg-someprot-10.txt").
>>>> When the next draft was issued, that email became stale; worse, 
>>>> someone reading it wouldn't know that they were looking at a diff
>>>> that was not pointing to the latest draft.
>>>>
>>>> Now, when you use 
>>>> "http://tools.ietf.org/rfcdiff?url2=draft-ietf-somewg-someprot" 
>>>> with no version number, the tool automatically
>>>> diffs the current version with the previous one. You no longer have 
>>>> to (or want to!) include the version number when you are
>>>> asking the WG to look at the diffs.
>>>>
>>>> Hat tip to the Tools Team, yet again!
>>>>
>>>> --Paul Hoffman, Director
>>>> --VPN Consortium
>>>>
>>>>
>>>
>>>
>>

From pkyzivat@cisco.com  Tue Feb 15 11:24:20 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC18C3A6AB3 for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 11:24:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3W3WafPBB5iU for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 11:24:19 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 8B6673A6A6C for <wgchairs@ietf.org>; Tue, 15 Feb 2011 11:24:19 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJ9hWk1AZnwM/2dsb2JhbAClWXOgeZtfhV4EhQWGfYM1
X-IronPort-AV: E=Sophos;i="4.60,476,1291593600"; d="scan'208";a="215971941"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 15 Feb 2011 19:24:45 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p1FJOjxT021435; Tue, 15 Feb 2011 19:24:45 GMT
Message-ID: <4D5AD2FD.1030103@cisco.com>
Date: Tue, 15 Feb 2011 14:24:45 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Tony Hansen <tony@att.com>
Subject: Re: New tool feature useful for WGs
References: <4D5AA214.7070202@vpnc.org> <4D5AABC0.2030906@bwijnen.net>	<4D5AB019.3060605@levkowetz.com> <4D5AC074.7070206@cisco.com> <4D5ACC53.9010205@att.com>
In-Reply-To: <4D5ACC53.9010205@att.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 19:24:20 -0000

On 2/15/2011 1:56 PM, Tony Hansen wrote:
> The URL tools.ietf.org/html/draft-whatever (or,
> tools.ietf.org/html/rfc####) has such links.

Yeah, that's exactly what I was wishing for.
(E.g. I see it with
http://tools.ietf.org/html/draft-ietf-sipping-sip-offeranswer-13)

But https://datatracker.ietf.org/doc/ links me to
https://datatracker.ietf.org/doc/draft-ietf-sipping-sip-offeranswer/
which doesn't have those links.

Too many twisty little passages, all different.

	Thanks,
	Paul

> Tony Hansen
> tony@att.com
>
> On 2/15/2011 1:05 PM, Paul Kyzivat wrote:
>> It would be nice when you did an ID or RFC search, or just used the
>> url to a particular draft, if the page that came up, in addition to
>> the other links it has, had a link to the diff from prior version.
>>
>> Thanks,
>> Paul
>>
>> On 2/15/2011 11:55 AM, Henrik Levkowetz wrote:
>>> Hi Bert,
>>>
>>> On 2011-02-15 17:37 Bert (IETF) Wijnen said:
>>>> That sounds great.
>>>>
>>>> I also recall (but I may be wrong), that at some point in the past,
>>>> if we did
>>>> This for a specific document, (following is an example):
>>>> http://tools.ietf.org/wg/netconf/draft-ietf-netconf-4741bis/
>>>> that we would get all the revisions and for each rev a ptr to the
>>>> diffs.
>>>> The example above seems to show only rev 0, 1 and 2, while we are
>>>> now up to rev 10.
>>>>
>>>> Did this change on purpose or by accident?
>>>
>>> Two of the tools servers (which recently was taken into rotation) are
>>> lagging. I'm fixing this now.
>>>
>>> Best,
>>>
>>> Henrik
>>>
>>>> Bert
>>>>
>>>>
>>>> On 2/15/11 4:56 PM, Paul Hoffman wrote:
>>>>> Greetings again. The IETF Tools Team just made an update to the
>>>>> tools site that should be useful to WGs.
>>>>>
>>>>> Before, when a new draft came out and you wanted to tell the WG to
>>>>> look at the diffs, you had to send the URL
>>>>> "http://tools.ietf.org/rfcdiff?url2=" with the draft name including
>>>>> the new draft number ("draft-ietf-somewg-someprot-10.txt").
>>>>> When the next draft was issued, that email became stale; worse,
>>>>> someone reading it wouldn't know that they were looking at a diff
>>>>> that was not pointing to the latest draft.
>>>>>
>>>>> Now, when you use
>>>>> "http://tools.ietf.org/rfcdiff?url2=draft-ietf-somewg-someprot"
>>>>> with no version number, the tool automatically
>>>>> diffs the current version with the previous one. You no longer have
>>>>> to (or want to!) include the version number when you are
>>>>> asking the WG to look at the diffs.
>>>>>
>>>>> Hat tip to the Tools Team, yet again!
>>>>>
>>>>> --Paul Hoffman, Director
>>>>> --VPN Consortium
>>>>>
>>>>>
>>>>
>>>>
>>>
>

From paul.hoffman@vpnc.org  Tue Feb 15 12:04:55 2011
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DACB43A6D71 for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 12:04:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.959
X-Spam-Level: 
X-Spam-Status: No, score=-99.959 tagged_above=-999 required=5 tests=[AWL=-0.513, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0U2bsMiDWeN for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 12:04:55 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 1F79F3A6D10 for <wgchairs@ietf.org>; Tue, 15 Feb 2011 12:04:55 -0800 (PST)
Received: from MacBook-08.local (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p1FK5Kdu012198 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Tue, 15 Feb 2011 13:05:21 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D5ADC80.8010700@vpnc.org>
Date: Tue, 15 Feb 2011 12:05:20 -0800
From: Paul Hoffman <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: New tool feature useful for WGs
References: <4D5AA214.7070202@vpnc.org>	<4D5AABC0.2030906@bwijnen.net>	<4D5AB019.3060605@levkowetz.com>	<4D5AC074.7070206@cisco.com> <4D5ACC53.9010205@att.com> <4D5AD2FD.1030103@cisco.com>
In-Reply-To: <4D5AD2FD.1030103@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 20:04:56 -0000

On 2/15/11 11:24 AM, Paul Kyzivat wrote:
> Yeah, that's exactly what I was wishing for.
> (E.g. I see it with
> http://tools.ietf.org/html/draft-ietf-sipping-sip-offeranswer-13)
>
> But https://datatracker.ietf.org/doc/ links me to
> https://datatracker.ietf.org/doc/draft-ietf-sipping-sip-offeranswer/
> which doesn't have those links.

Tools != Datatracker

From dworley@avaya.com  Tue Feb 15 12:36:24 2011
Return-Path: <dworley@avaya.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1513C3A6D9A for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 12:36:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xZn9arjZkm0p for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 12:36:23 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id E84B83A6C43 for <wgchairs@ietf.org>; Tue, 15 Feb 2011 12:36:22 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEABByWk2HCzI1/2dsb2JhbAClWnOjIQKZK4VeBIUFikw
X-IronPort-AV: E=Sophos;i="4.60,476,1291611600"; d="scan'208";a="232567735"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 15 Feb 2011 15:36:48 -0500
X-IronPort-AV: E=Sophos;i="4.60,476,1291611600"; d="scan'208";a="600760658"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 15 Feb 2011 15:36:47 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Tue, 15 Feb 2011 15:36:47 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Date: Tue, 15 Feb 2011 15:35:20 -0500
Subject: RE: New tool feature useful for WGs
Thread-Topic: New tool feature useful for WGs
Thread-Index: AcvNS7yCMCwuPQ1TRB+krqGEWFggvQABCAw1
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A176880@DC-US1MBEX4.global.avaya.com>
References: <4D5AA214.7070202@vpnc.org>	<4D5AABC0.2030906@bwijnen.net> <4D5AB019.3060605@levkowetz.com>	<4D5AC074.7070206@cisco.com> <4D5ACC53.9010205@att.com> <4D5AD2FD.1030103@cisco.com>,<4D5ADC80.8010700@vpnc.org>
In-Reply-To: <4D5ADC80.8010700@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 20:36:24 -0000

________________________________________
From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] On Behalf Of Pa=
ul Hoffman [paul.hoffman@vpnc.org]

Tools !=3D Datatracker
________________________________________

True, but let us remember that only people who are deeply involved with the=
 IETF infrastructure have any idea which features are "tools" and which are=
 "datatracker".  Indeed, the IETF "user experience" would benefit greatly i=
f this distinction was erased.

Dale

From jhutz@cmu.edu  Tue Feb 15 13:23:28 2011
Return-Path: <jhutz@cmu.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 02B5E3A6C64 for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 13:23:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 76qJ8ervC8CY for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 13:23:25 -0800 (PST)
Received: from smtp03.srv.cs.cmu.edu (SMTP03.SRV.CS.CMU.EDU [128.2.217.198]) by core3.amsl.com (Postfix) with ESMTP id A12363A6C4E for <wgchairs@ietf.org>; Tue, 15 Feb 2011 13:23:24 -0800 (PST)
Received: from MINBAR.FAC.CS.CMU.EDU (MINBAR.FAC.CS.CMU.EDU [128.2.216.42]) (authenticated bits=0) by smtp03.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id p1FLNmsS020716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Feb 2011 16:23:48 -0500 (EST)
Date: Tue, 15 Feb 2011 16:23:48 -0500
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Paul Hoffman <paul.hoffman@vpnc.org>, wgchairs@ietf.org
Subject: RE: New tool feature useful for WGs
Message-ID: <D69CB225EF5DD6BE3CDC1464@minbar.fac.cs.cmu.edu>
In-Reply-To: <26018_1297802217_p1FKaucK029276_CD5674C3CD99574EBA7432465FC13C1B220A176880@DC-US1MBEX4.global.avaya.com>
References: <4D5AA214.7070202@vpnc.org>	<4D5AABC0.2030906@bwijnen.net> <4D5AB019.3060605@levkowetz.com>	<4D5AC074.7070206@cisco.com> <4D5ACC53.9010205@att.com>	<4D5AD2FD.1030103@cisco.com> ,<4D5ADC80.8010700@vpnc.org> <26018_1297802217_p1FKaucK029276_CD5674C3CD99574EBA7432465FC13C1B220A176880@DC-US1MBEX4.global.avaya.com>
X-Mailer: Mulberry/4.0.8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: mimedefang-cmuscs on 128.2.217.198
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 21:23:28 -0000

--On Tuesday, February 15, 2011 03:35:20 PM -0500 "Worley, Dale R (Dale)" 
<dworley@avaya.com> wrote:

> ________________________________________
> From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] On Behalf Of
> Paul Hoffman [paul.hoffman@vpnc.org]
>
> Tools != Datatracker
> ________________________________________
>
> True, but let us remember that only people who are deeply involved with
> the IETF infrastructure have any idea which features are "tools" and
> which are "datatracker".  Indeed, the IETF "user experience" would
> benefit greatly if this distinction was erased.

Unfortunately, it's a difficult distinction to erase, because it's the 
distinction between "official" infrastructure which the IETF controls and 
pays for (including development, maintenance, and also the server 
infrastructure it runs on) and a bunch of stuff put together by some 
volunteers which lots of people have found to be pretty useful.

It's pretty easy to tell the volunteer-maintained stuff from the "official" 
stuff, both from the URL's and because each has a fairly distinctive look.

-- Jeffrey T. Hutzelman (N3NHS) <jhutz+@cmu.edu>
   Carnegie Mellon University - Pittsburgh, PA


From pkyzivat@cisco.com  Tue Feb 15 16:33:55 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 406E03A6DA5 for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 16:33:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BSoJLhqsKIdF for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 16:33:53 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 8B6803A6D57 for <wgchairs@ietf.org>; Tue, 15 Feb 2011 16:33:53 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjUGAL6qWk2rRN+K/2dsb2JhbACXRI4cc6FMm2CFXgSFBocAgzY
X-IronPort-AV: E=Sophos;i="4.60,477,1291593600"; d="scan'208";a="264133568"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-3.cisco.com with ESMTP; 16 Feb 2011 00:34:20 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p1G0YKh0021563 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 00:34:20 GMT
Message-ID: <4D5B1B8B.2040800@cisco.com>
Date: Tue, 15 Feb 2011 19:34:19 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: New tool feature useful for WGs
References: <4D5AA214.7070202@vpnc.org>	<4D5AABC0.2030906@bwijnen.net>	<4D5AB019.3060605@levkowetz.com>	<4D5AC074.7070206@cisco.com>	<4D5ACC53.9010205@att.com> <4D5AD2FD.1030103@cisco.com> <4D5ADC80.8010700@vpnc.org>
In-Reply-To: <4D5ADC80.8010700@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 00:33:55 -0000

On 2/15/2011 3:05 PM, Paul Hoffman wrote:
> On 2/15/11 11:24 AM, Paul Kyzivat wrote:
>> Yeah, that's exactly what I was wishing for.
>> (E.g. I see it with
>> http://tools.ietf.org/html/draft-ietf-sipping-sip-offeranswer-13)
>>
>> But https://datatracker.ietf.org/doc/ links me to
>> https://datatracker.ietf.org/doc/draft-ietf-sipping-sip-offeranswer/
>> which doesn't have those links.
>
> Tools != Datatracker
>

Yes, I recognize that.
So, what is the relationship between those things? Are these just 
parallel universes? Why are they different? Datatracker finds the things 
I want to look at. Can tools do the same thing?

I'm not pointing a finger at anybody - I know this is mostly volunteer 
labor. I'm just confused.

It would be really nice if it was possible to "click through" from any 
of the various starting points to all of the related interesting stuff. E.g.

- start with announcement of new draft. Click to see it. Click again to 
see diffs, earlier versions, alternative representations. After clicking 
to earlier version, click again to get a diff of *it* to its predecessor.

- start with a query for an RFC or draft, using datadracker. Then do all 
the same stuff.

- start from a link to a wg doc off the wg home page. Do all the same stuff.

	Thanks,
	Paul

	Thanks,
	Paul

From barryleiba.mailing.lists@gmail.com  Tue Feb 15 19:11:03 2011
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC5523A6C7E for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 19:11:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9WH-dj7Pp-0f for <wgchairs@core3.amsl.com>; Tue, 15 Feb 2011 19:11:03 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id D0D9F3A6B8E for <wgchairs@ietf.org>; Tue, 15 Feb 2011 19:11:02 -0800 (PST)
Received: by iwc10 with SMTP id 10so909107iwc.31 for <wgchairs@ietf.org>; Tue, 15 Feb 2011 19:11:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=2OcibipjMC+2RMRo3BJVPeLK1J+A0iHyLQ9KF0u1EHU=; b=v2flcWg4W8uikNH3oxqIgJo9U5PfCQdnTA+ETAlVXdN3voFhpi/1N76Q2r6f4FTmqs vJN5BtdkZ42jzTtG/VDhfXM6xGPndCitqxzCYJXLv0V76WbMxKTkZjpSiOaZT3km7mXG gJ955hGih9Dydv+BB12ebrwSvaHPP9JQuR++Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=kIg95mJhClfA1x3YrRpUze1JKTHYce55xlvCya0LbVp7Sy2SiDFFlq6noIAKBdbBfh 04wF/eIWAK1E88Uic9+9sk4AAvGTdDj2xH8tk2PnvQLaJ0vM69akGLzlrv6qnun1dP9p 3xzRFx2Ef7iaZ3Xkadct+17tM2tZ9SIvJ55D0=
MIME-Version: 1.0
Received: by 10.42.170.195 with SMTP id g3mr57011icz.52.1297825889341; Tue, 15 Feb 2011 19:11:29 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.229.67 with HTTP; Tue, 15 Feb 2011 19:11:29 -0800 (PST)
In-Reply-To: <4D5B1B8B.2040800@cisco.com>
References: <4D5AA214.7070202@vpnc.org> <4D5AABC0.2030906@bwijnen.net> <4D5AB019.3060605@levkowetz.com> <4D5AC074.7070206@cisco.com> <4D5ACC53.9010205@att.com> <4D5AD2FD.1030103@cisco.com> <4D5ADC80.8010700@vpnc.org> <4D5B1B8B.2040800@cisco.com>
Date: Tue, 15 Feb 2011 22:11:29 -0500
X-Google-Sender-Auth: 2Orw3CALbFY8dNqgDUkXiIkEoSk
Message-ID: <AANLkTinYDZcGW+QFUqupR8YvgT=7Ap=uzwJgC06zxFra@mail.gmail.com>
Subject: Re: New tool feature useful for WGs
From: Barry Leiba <barryleiba@computer.org>
To: Paul Kyzivat <pkyzivat@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 03:11:03 -0000

> It would be really nice if it was possible to "click through" from any of
> the various starting points to all of the related interesting stuff. E.g.
>
> - start with announcement of new draft. Click to see it. Click again to see
> diffs, earlier versions, alternative representations. After clicking to
> earlier version, click again to get a diff of *it* to its predecessor.
>
> - start with a query for an RFC or draft, using datadracker. Then do all the
> same stuff.
>
> - start from a link to a wg doc off the wg home page. Do all the same stuff.

You can click through from tools to tracker and back, for documents.
Here's the datatracker link to the document Bert mentioned above:

   https://datatracker.ietf.org/doc/draft-ietf-netconf-4741bis/

Note this in the top box:

   Other versions:	plain text, xml, pdf, html

If you click "html" there, you'll get the tools version:

   http://tools.ietf.org/html/draft-ietf-netconf-4741bis-09

At the top of the tools version is this:

   [Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

And if you click "Tracker", you get back to the tracker info.

That's not the same as "erasing the difference", but at least you
*can* easily go back and forth.

Barry

From henrik@levkowetz.com  Wed Feb 16 03:33:43 2011
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B1B033A6E15 for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 03:33:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.503
X-Spam-Level: 
X-Spam-Status: No, score=-102.503 tagged_above=-999 required=5 tests=[AWL=0.097, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Kn-4wIB3gbY for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 03:33:42 -0800 (PST)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id 56C203A6E11 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 03:33:42 -0800 (PST)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:53660 helo=dyn-fg117.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1Ppfdm-0008C7-6s; Wed, 16 Feb 2011 12:33:54 +0100
Message-ID: <4D5BB61D.7080308@levkowetz.com>
Date: Wed, 16 Feb 2011 12:33:49 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <4D5AA214.7070202@vpnc.org>	<4D5AABC0.2030906@bwijnen.net>	<4D5AB019.3060605@levkowetz.com>	<4D5AC074.7070206@cisco.com> <4D5ACC53.9010205@att.com> <4D5AD2FD.1030103@cisco.com>
In-Reply-To: <4D5AD2FD.1030103@cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: pkyzivat@cisco.com, tony@att.com, wgchairs@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: New tool feature useful for WGs
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 11:33:43 -0000

Hi,

On 2011-02-15 20:24 Paul Kyzivat said:
> 
> 
> On 2/15/2011 1:56 PM, Tony Hansen wrote:
>> The URL tools.ietf.org/html/draft-whatever (or,
>> tools.ietf.org/html/rfc####) has such links.
> 
> Yeah, that's exactly what I was wishing for.
> (E.g. I see it with
> http://tools.ietf.org/html/draft-ietf-sipping-sip-offeranswer-13)
> 
> But https://datatracker.ietf.org/doc/ links me to
> https://datatracker.ietf.org/doc/draft-ietf-sipping-sip-offeranswer/
> which doesn't have those links.
> 
> Too many twisty little passages, all different.

Agreed.  And it is worthwhile to provide a lot of the features which
today live mostly on the tools servers also (or instead!) on the
datatracker.  Unfortunately, the database behind the datatracker is
also, because it 'just grew', full of twisty little passages, all
different:

http://merlot.tools.ietf.org/src/db/new/redesign/old-models.png

Instead of banging our heads against the walls of all those twisty
little passages forever, a new database schema has been designed, and
work is well under way of converting data and code to that new schema:

http://merlot.tools.ietf.org/src/db/new/redesign/models.png

Once this is in place, we can spend time making the datatracker nicer,
instead of endlessly hurting our heads trying to accomplish things in
the legacy code and data maze.

We'll get there :-)


Best,

	Henrik

From pkyzivat@cisco.com  Wed Feb 16 06:07:16 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D85863A6E14 for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 06:07:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X-2L2F8BdDhi for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 06:07:16 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 00F113A6CCD for <wgchairs@ietf.org>; Wed, 16 Feb 2011 06:07:15 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAEppW01AZnwN/2dsb2JhbAClYHOgRptOhV4EhQiHAoM4
X-IronPort-AV: E=Sophos;i="4.60,479,1291593600"; d="scan'208";a="216029359"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 16 Feb 2011 14:07:44 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p1GE7hJT005121; Wed, 16 Feb 2011 14:07:44 GMT
Message-ID: <4D5BDA2F.7080007@cisco.com>
Date: Wed, 16 Feb 2011 09:07:43 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: New tool feature useful for WGs
References: <4D5AA214.7070202@vpnc.org>	<4D5AABC0.2030906@bwijnen.net>	<4D5AB019.3060605@levkowetz.com>	<4D5AC074.7070206@cisco.com>	<4D5ACC53.9010205@att.com>	<4D5AD2FD.1030103@cisco.com>	<4D5ADC80.8010700@vpnc.org>	<4D5B1B8B.2040800@cisco.com> <AANLkTinYDZcGW+QFUqupR8YvgT=7Ap=uzwJgC06zxFra@mail.gmail.com>
In-Reply-To: <AANLkTinYDZcGW+QFUqupR8YvgT=7Ap=uzwJgC06zxFra@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 14:07:17 -0000

Barry - *thank you*!!!

That really makes my day. I doubt I would ever have figured that out 
without being told, and it provides pretty much everything I was asking 
for. While it could be simpler, its "simple enough".

	Thanks again,
	Paul

On 2/15/2011 10:11 PM, Barry Leiba wrote:
>> It would be really nice if it was possible to "click through" from any of
>> the various starting points to all of the related interesting stuff. E.g.
>>
>> - start with announcement of new draft. Click to see it. Click again to see
>> diffs, earlier versions, alternative representations. After clicking to
>> earlier version, click again to get a diff of *it* to its predecessor.
>>
>> - start with a query for an RFC or draft, using datadracker. Then do all the
>> same stuff.
>>
>> - start from a link to a wg doc off the wg home page. Do all the same stuff.
>
> You can click through from tools to tracker and back, for documents.
> Here's the datatracker link to the document Bert mentioned above:
>
>     https://datatracker.ietf.org/doc/draft-ietf-netconf-4741bis/
>
> Note this in the top box:
>
>     Other versions:	plain text, xml, pdf, html
>
> If you click "html" there, you'll get the tools version:
>
>     http://tools.ietf.org/html/draft-ietf-netconf-4741bis-09
>
> At the top of the tools version is this:
>
>     [Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]
>
> And if you click "Tracker", you get back to the tracker info.
>
> That's not the same as "erasing the difference", but at least you
> *can* easily go back and forth.
>
> Barry
>

From pkyzivat@cisco.com  Wed Feb 16 06:08:52 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 513833A6CCD for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 06:08:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P80RRBiDrhh9 for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 06:08:51 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 6B5C13A6CA7 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 06:08:51 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAEppW01AZnwM/2dsb2JhbAClYHOgRptOhV4EhQiHAoM4
X-IronPort-AV: E=Sophos;i="4.60,479,1291593600"; d="scan'208";a="216029870"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 16 Feb 2011 14:09:19 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p1GE9Jbk018532; Wed, 16 Feb 2011 14:09:19 GMT
Message-ID: <4D5BDA8F.2060109@cisco.com>
Date: Wed, 16 Feb 2011 09:09:19 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: New tool feature useful for WGs
References: <4D5AA214.7070202@vpnc.org>	<4D5AABC0.2030906@bwijnen.net>	<4D5AB019.3060605@levkowetz.com>	<4D5AC074.7070206@cisco.com> <4D5ACC53.9010205@att.com> <4D5AD2FD.1030103@cisco.com> <4D5BB61D.7080308@levkowetz.com>
In-Reply-To: <4D5BB61D.7080308@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 14:08:52 -0000

On 2/16/2011 6:33 AM, Henrik Levkowetz wrote:
> Hi,
>
> On 2011-02-15 20:24 Paul Kyzivat said:
>>
>>
>> On 2/15/2011 1:56 PM, Tony Hansen wrote:
>>> The URL tools.ietf.org/html/draft-whatever (or,
>>> tools.ietf.org/html/rfc####) has such links.
>>
>> Yeah, that's exactly what I was wishing for.
>> (E.g. I see it with
>> http://tools.ietf.org/html/draft-ietf-sipping-sip-offeranswer-13)
>>
>> But https://datatracker.ietf.org/doc/ links me to
>> https://datatracker.ietf.org/doc/draft-ietf-sipping-sip-offeranswer/
>> which doesn't have those links.
>>
>> Too many twisty little passages, all different.
>
> Agreed.  And it is worthwhile to provide a lot of the features which
> today live mostly on the tools servers also (or instead!) on the
> datatracker.  Unfortunately, the database behind the datatracker is
> also, because it 'just grew', full of twisty little passages, all
> different:
>
> http://merlot.tools.ietf.org/src/db/new/redesign/old-models.png
>
> Instead of banging our heads against the walls of all those twisty
> little passages forever, a new database schema has been designed, and
> work is well under way of converting data and code to that new schema:
>
> http://merlot.tools.ietf.org/src/db/new/redesign/models.png
>
> Once this is in place, we can spend time making the datatracker nicer,
> instead of endlessly hurting our heads trying to accomplish things in
> the legacy code and data maze.
>
> We'll get there :-)

Sounds good. Looking forward to it.

Meanwhile I'm pretty happy with the linkages Barry pointed out.

	Thanks,
	Paul

From dworley@avaya.com  Wed Feb 16 06:41:04 2011
Return-Path: <dworley@avaya.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03F0A3A6E48 for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 06:41:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id haknTbhqL3cx for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 06:41:03 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id EE3E53A6E65 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 06:41:02 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFNwW03GmAcF/2dsb2JhbAClYHOjDgKZJoVeBIUIilSILQ
X-IronPort-AV: E=Sophos;i="4.60,479,1291611600"; d="scan'208";a="232690346"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 16 Feb 2011 09:41:30 -0500
X-IronPort-AV: E=Sophos;i="4.60,479,1291611600"; d="scan'208";a="583088152"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 16 Feb 2011 09:41:29 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Wed, 16 Feb 2011 09:41:28 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Jeffrey Hutzelman <jhutz@cmu.edu>, Paul Hoffman <paul.hoffman@vpnc.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Date: Wed, 16 Feb 2011 09:41:28 -0500
Subject: RE: New tool feature useful for WGs
Thread-Topic: New tool feature useful for WGs
Thread-Index: AcvNVqc4fLo7gbA1SJOXx/+oc04sLgAj/SBC
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A176885@DC-US1MBEX4.global.avaya.com>
References: <4D5AA214.7070202@vpnc.org>	<4D5AABC0.2030906@bwijnen.net> <4D5AB019.3060605@levkowetz.com>	<4D5AC074.7070206@cisco.com> <4D5ACC53.9010205@att.com>	<4D5AD2FD.1030103@cisco.com> ,<4D5ADC80.8010700@vpnc.org> <26018_1297802217_p1FKaucK029276_CD5674C3CD99574EBA7432465FC13C1B220A176880@DC-US1MBEX4.global.avaya.com>, <D69CB225EF5DD6BE3CDC1464@minbar.fac.cs.cmu.edu>
In-Reply-To: <D69CB225EF5DD6BE3CDC1464@minbar.fac.cs.cmu.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 14:41:04 -0000

________________________________________
From: Jeffrey Hutzelman [jhutz@cmu.edu]

Unfortunately, it's a difficult distinction to erase, because it's the
distinction between "official" infrastructure which the IETF controls and
pays for (including development, maintenance, and also the server
infrastructure it runs on) and a bunch of stuff put together by some
volunteers which lots of people have found to be pretty useful.

It's pretty easy to tell the volunteer-maintained stuff from the "official"
stuff, both from the URL's and because each has a fairly distinctive look.
_________________________________________

Someone should get on top of straightening it out.

It's only "easy to tell" if one pays attention to "look", but not being a v=
isually-oriented kind of guy, I don't, it's all dancing hamsters to me.  Al=
l I see is that the URLs start with "http://www.ietf.org/".  That's the IET=
F domain name, innit?  Which means the IETF is responsible for it, eh?  (An=
d I notice that you haven't actually *said* what the difference in URLs is.=
)

If you have "unofficial stuff somehow related to the IETF", it would be a l=
ot better if you got a different domain name for it, to make it clear that =
the IETF isn't responsible for it.

But really, if you've got a bunch of stuff maintained by volunteers that's =
supposed to be useful for the IETF community generally, that's no excuse fo=
r it to be non-uniform with the rest of the IETF site.

Dale

From mary.ietf.barnes@gmail.com  Wed Feb 16 06:52:47 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 39D173A6C9F for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 06:52:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDWCggVO3nxw for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 06:52:45 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id BDD473A6C41 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 06:52:44 -0800 (PST)
Received: by iwc10 with SMTP id 10so1493011iwc.31 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 06:53:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ZztzAKhDviYJeICaZIxnanyyfB8iS+IPlPqv2YrkM2M=; b=i3LZ+qhqV3ouAK+HISz1EIPMBkXNgIOADzsQ4gDeLcNmtI7L+4yE0kebvoAJDEwRWU rvWrx2gOJnRzFahcC1M461CIFerXpIxp/CksmKzzJJqlJvy6V/J0QAOXMexSuJmBUg/z IU2KEZ8W339ve6tU/M4GaLdT+m5GkyFXOnQmc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=mqD+3YGoLYZG37zHggT/KdzxBteRzGXD9ZMOgRLmnXdMBjllPxkmxuLmN0fh9UAFed i90yjUrXIi4cZ6I4g8E1GuHn6iSHp9MgAAgUNx/JqlbpMFjCV7Ys5TXSyOagRPJSmq0j mD9SL637ReqBxP5Yrn2Q5FewIPSNDdQBocrx8=
MIME-Version: 1.0
Received: by 10.42.167.65 with SMTP id r1mr939138icy.65.1297867992939; Wed, 16 Feb 2011 06:53:12 -0800 (PST)
Received: by 10.42.202.12 with HTTP; Wed, 16 Feb 2011 06:53:12 -0800 (PST)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A176885@DC-US1MBEX4.global.avaya.com>
References: <4D5AA214.7070202@vpnc.org> <4D5AABC0.2030906@bwijnen.net> <4D5AB019.3060605@levkowetz.com> <4D5AC074.7070206@cisco.com> <4D5ACC53.9010205@att.com> <4D5AD2FD.1030103@cisco.com> <4D5ADC80.8010700@vpnc.org> <26018_1297802217_p1FKaucK029276_CD5674C3CD99574EBA7432465FC13C1B220A176880@DC-US1MBEX4.global.avaya.com> <D69CB225EF5DD6BE3CDC1464@minbar.fac.cs.cmu.edu> <CD5674C3CD99574EBA7432465FC13C1B220A176885@DC-US1MBEX4.global.avaya.com>
Date: Wed, 16 Feb 2011 08:53:12 -0600
Message-ID: <AANLkTi=o1D-uiUsNrpAsZUJsUqarum5Aonpcb_nhemQU@mail.gmail.com>
Subject: Re: New tool feature useful for WGs
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: multipart/alternative; boundary=90e6ba6e8e46af3c7b049c6770af
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 14:52:47 -0000

--90e6ba6e8e46af3c7b049c6770af
Content-Type: text/plain; charset=ISO-8859-1

Dale,

The URLs for the tools pages are differentiated as http://tools.ietf.org/.

While I totally agree with you that it is confusing - the two separate login
ids is often a source of confusion, I'm of the mindset that it's far more
important the tools actually exist.  Certainly, the main ietf webpages have
improved significantly over the past decade, however, the tools pages have
been invaluable over the past decade and are far more feature rich.  While,
it would be ideal to have a single website, I personally see value in the
two separate websites in that updates to the tools happen more rapidly on
the tools page and I believe it gives chairs more control over their WG
space, if you will. For example, the wikis can be extremely useful, although
I notice that they are underutilized.

Regards,
Mary.

On Wed, Feb 16, 2011 at 8:41 AM, Worley, Dale R (Dale) <dworley@avaya.com>wrote:

> ________________________________________
> From: Jeffrey Hutzelman [jhutz@cmu.edu]
>
> Unfortunately, it's a difficult distinction to erase, because it's the
> distinction between "official" infrastructure which the IETF controls and
> pays for (including development, maintenance, and also the server
> infrastructure it runs on) and a bunch of stuff put together by some
> volunteers which lots of people have found to be pretty useful.
>
> It's pretty easy to tell the volunteer-maintained stuff from the "official"
> stuff, both from the URL's and because each has a fairly distinctive look.
> _________________________________________
>
> Someone should get on top of straightening it out.
>
> It's only "easy to tell" if one pays attention to "look", but not being a
> visually-oriented kind of guy, I don't, it's all dancing hamsters to me.
>  All I see is that the URLs start with "http://www.ietf.org/".  That's the
> IETF domain name, innit?  Which means the IETF is responsible for it, eh?
>  (And I notice that you haven't actually *said* what the difference in URLs
> is.)
>
> If you have "unofficial stuff somehow related to the IETF", it would be a
> lot better if you got a different domain name for it, to make it clear that
> the IETF isn't responsible for it.
>
> But really, if you've got a bunch of stuff maintained by volunteers that's
> supposed to be useful for the IETF community generally, that's no excuse for
> it to be non-uniform with the rest of the IETF site.
>
> Dale
>

--90e6ba6e8e46af3c7b049c6770af
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dale,<div><br></div><div>The URLs for the tools pages are differentiated as=
 <a href=3D"http://tools.ietf.org/">http://tools.ietf.org/</a>.</div><div><=
br></div><div>While I totally agree with you that it is confusing - the two=
 separate login ids is often a source of confusion, I&#39;m of the mindset =
that it&#39;s far more important the tools actually exist. =A0Certainly, th=
e main ietf webpages have improved significantly over the past decade, howe=
ver, the tools pages have been invaluable over the past decade and are far =
more feature rich. =A0While, it would be ideal to have a single website, I =
personally see value in the two separate websites in that updates to the to=
ols happen more rapidly on the tools page and I believe it gives chairs mor=
e control over their WG space, if you will. For example, the wikis can be e=
xtremely useful, although I notice that they are underutilized.=A0</div>
<div><br></div><div>Regards,</div><div>Mary.=A0<br><br><div class=3D"gmail_=
quote">On Wed, Feb 16, 2011 at 8:41 AM, Worley, Dale R (Dale) <span dir=3D"=
ltr">&lt;<a href=3D"mailto:dworley@avaya.com">dworley@avaya.com</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">________________________________________<br=
>
From: Jeffrey Hutzelman [<a href=3D"mailto:jhutz@cmu.edu">jhutz@cmu.edu</a>=
]<br>
<br>
Unfortunately, it&#39;s a difficult distinction to erase, because it&#39;s =
the<br>
distinction between &quot;official&quot; infrastructure which the IETF cont=
rols and<br>
pays for (including development, maintenance, and also the server<br>
infrastructure it runs on) and a bunch of stuff put together by some<br>
volunteers which lots of people have found to be pretty useful.<br>
<br>
It&#39;s pretty easy to tell the volunteer-maintained stuff from the &quot;=
official&quot;<br>
stuff, both from the URL&#39;s and because each has a fairly distinctive lo=
ok.<br>
_________________________________________<br>
<br>
Someone should get on top of straightening it out.<br>
<br>
It&#39;s only &quot;easy to tell&quot; if one pays attention to &quot;look&=
quot;, but not being a visually-oriented kind of guy, I don&#39;t, it&#39;s=
 all dancing hamsters to me. =A0All I see is that the URLs start with &quot=
;<a href=3D"http://www.ietf.org/" target=3D"_blank">http://www.ietf.org/</a=
>&quot;. =A0That&#39;s the IETF domain name, innit? =A0Which means the IETF=
 is responsible for it, eh? =A0(And I notice that you haven&#39;t actually =
*said* what the difference in URLs is.)<br>

<br>
If you have &quot;unofficial stuff somehow related to the IETF&quot;, it wo=
uld be a lot better if you got a different domain name for it, to make it c=
lear that the IETF isn&#39;t responsible for it.<br>
<br>
But really, if you&#39;ve got a bunch of stuff maintained by volunteers tha=
t&#39;s supposed to be useful for the IETF community generally, that&#39;s =
no excuse for it to be non-uniform with the rest of the IETF site.<br>

<font color=3D"#888888"><br>
Dale<br>
</font></blockquote></div><br></div>

--90e6ba6e8e46af3c7b049c6770af--

From dworley@avaya.com  Wed Feb 16 07:01:00 2011
Return-Path: <dworley@avaya.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 295393A6E2C for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 07:01:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6tPMYp2Jngs for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 07:00:59 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 3525D3A6D3A for <wgchairs@ietf.org>; Wed, 16 Feb 2011 07:00:59 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMd0W03GmAcF/2dsb2JhbAClYHOjDQKZKYVeBIUIilSCcw
X-IronPort-AV: E=Sophos;i="4.60,480,1291611600"; d="scan'208";a="232694341"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 16 Feb 2011 10:01:26 -0500
X-IronPort-AV: E=Sophos;i="4.60,480,1291611600"; d="scan'208";a="583094441"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 16 Feb 2011 10:01:26 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Wed, 16 Feb 2011 10:01:25 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Wed, 16 Feb 2011 09:59:19 -0500
Subject: RE: New tool feature useful for WGs
Thread-Topic: New tool feature useful for WGs
Thread-Index: AcvN6T1wnHQ9HoBNR+G70SlZbt9JWwAANikg
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A176887@DC-US1MBEX4.global.avaya.com>
References: <4D5AA214.7070202@vpnc.org>	<4D5AABC0.2030906@bwijnen.net> <4D5AB019.3060605@levkowetz.com>	<4D5AC074.7070206@cisco.com> <4D5ACC53.9010205@att.com>	<4D5AD2FD.1030103@cisco.com> <4D5ADC80.8010700@vpnc.org> <26018_1297802217_p1FKaucK029276_CD5674C3CD99574EBA7432465FC13C1B220A176880@DC-US1MBEX4.global.avaya.com> <D69CB225EF5DD6BE3CDC1464@minbar.fac.cs.cmu.edu> <CD5674C3CD99574EBA7432465FC13C1B220A176885@DC-US1MBEX4.global.avaya.com>, <AANLkTi=o1D-uiUsNrpAsZUJsUqarum5Aonpcb_nhemQU@mail.gmail.com>
In-Reply-To: <AANLkTi=o1D-uiUsNrpAsZUJsUqarum5Aonpcb_nhemQU@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 15:01:00 -0000

________________________________________
From: Mary Barnes [mary.ietf.barnes@gmail.com]

The URLs for the tools pages are differentiated as http://tools.ietf.org/.
________________________________________

Interesting!  Are all pages that do *not* have hostname "tools.ietf.org" pa=
rt of the "datagracker" system?

Dale

From acmorton@att.com  Wed Feb 16 07:24:03 2011
Return-Path: <acmorton@att.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A00E3A6C41 for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 07:24:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.796
X-Spam-Level: 
X-Spam-Status: No, score=-105.796 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cI9HqjU3jmO7 for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 07:24:02 -0800 (PST)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by core3.amsl.com (Postfix) with ESMTP id AD8363A6A25 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 07:24:02 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-7.tower-120.messagelabs.com!1297869870!4661836!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 9181 invoked from network); 16 Feb 2011 15:24:30 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-7.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Feb 2011 15:24:30 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p1GFOrHG008840 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 10:24:53 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p1GFOkhL008698 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 10:24:46 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p1GFONTl018460 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 10:24:23 -0500
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p1GFOHFm018194 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 10:24:18 -0500
Message-Id: <201102161524.p1GFOHFm018194@alpd052.aldc.att.com>
Received: from acmt.att.com (dn135-16-251-71.dhcpn.ugn.att.com[135.16.251.71](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20110216152417gw100e4l7ae>; Wed, 16 Feb 2011 15:24:17 +0000
X-Originating-IP: [135.16.251.71]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 16 Feb 2011 10:24:52 -0500
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Jeffrey Hutzelman <jhutz@cmu.edu>, Paul Hoffman <paul.hoffman@vpnc.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
From: Al Morton <acmorton@att.com>
Subject: RE: New tool feature useful for WGs
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A176885@DC-US1MBEX4.glo bal.avaya.com>
References: <4D5AA214.7070202@vpnc.org> <4D5AABC0.2030906@bwijnen.net> <4D5AB019.3060605@levkowetz.com> <4D5AC074.7070206@cisco.com> <4D5ACC53.9010205@att.com> <4D5AD2FD.1030103@cisco.com> <4D5ADC80.8010700@vpnc.org> <26018_1297802217_p1FKaucK029276_CD5674C3CD99574EBA7432465FC13C1B220A176880@DC-US1MBEX4.global.avaya.com> <D69CB225EF5DD6BE3CDC1464@minbar.fac.cs.cmu.edu> <CD5674C3CD99574EBA7432465FC13C1B220A176885@DC-US1MBEX4.global.avaya.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 15:24:03 -0000

At 09:41 AM 2/16/2011, Worley, Dale R (Dale) wrote:
>If you have "unofficial stuff somehow related to the IETF", it would 
>be a lot better if you got a different domain name for it, to make 
>it clear that the IETF isn't responsible for it.

http://tools.ietf.org/

no requirement to use anything there...

Al




From mary.ietf.barnes@gmail.com  Wed Feb 16 07:24:56 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C3F73A6D3A for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 07:24:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MN2-x+XisdoC for <wgchairs@core3.amsl.com>; Wed, 16 Feb 2011 07:24:55 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 299873A6CA1 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 07:24:55 -0800 (PST)
Received: by iym1 with SMTP id 1so1405076iym.31 for <wgchairs@ietf.org>; Wed, 16 Feb 2011 07:25:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=59MdRt2h18MlFtDXnLlRn36Z7zIhqMi3RjARvKgIFDs=; b=EKmK1hlNf06ZfzwOX+A0erY1AR52dsiU9RDTMniCjqc6X5iB/v7h18lw1HywuEgQxN Cfq26jjbtBfg9VSXX7PRCQKU0zLqes23EhmmqMVnh5fMA4H7NS6WSFtDmyH8xMoNUtbL IoLiOa1IxLGudLSN/nXs7u0LT3KHwbcd1GpJM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=gTKEVec+vKm8z0y40ZoLHszUcnCqTunwgE4wqV+loU0z7FT1KXdjcqsYyJ2EHmEDPz DmBPryk/11A4JhmQpxU+Ns594NW1xwMI/m5jFkYsR+v0hBuWXfZ1KwP1fc/d3Lap2Sd+ BO+LZdaE9q0QP2+NkXLJX1ud2RrATtyDeJVjM=
MIME-Version: 1.0
Received: by 10.42.219.136 with SMTP id hu8mr964910icb.357.1297869893907; Wed, 16 Feb 2011 07:24:53 -0800 (PST)
Received: by 10.42.202.12 with HTTP; Wed, 16 Feb 2011 07:24:53 -0800 (PST)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A176887@DC-US1MBEX4.global.avaya.com>
References: <4D5AA214.7070202@vpnc.org> <4D5AABC0.2030906@bwijnen.net> <4D5AB019.3060605@levkowetz.com> <4D5AC074.7070206@cisco.com> <4D5ACC53.9010205@att.com> <4D5AD2FD.1030103@cisco.com> <4D5ADC80.8010700@vpnc.org> <26018_1297802217_p1FKaucK029276_CD5674C3CD99574EBA7432465FC13C1B220A176880@DC-US1MBEX4.global.avaya.com> <D69CB225EF5DD6BE3CDC1464@minbar.fac.cs.cmu.edu> <CD5674C3CD99574EBA7432465FC13C1B220A176885@DC-US1MBEX4.global.avaya.com> <AANLkTi=o1D-uiUsNrpAsZUJsUqarum5Aonpcb_nhemQU@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B220A176887@DC-US1MBEX4.global.avaya.com>
Date: Wed, 16 Feb 2011 09:24:53 -0600
Message-ID: <AANLkTi=U-6p0Snfi62d1SfPErvaJaZn2=Zs4x1W5+wDN@mail.gmail.com>
Subject: Re: New tool feature useful for WGs
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: multipart/alternative; boundary=20cf3054ab5ffdb4eb049c67e1ea
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 15:24:56 -0000

--20cf3054ab5ffdb4eb049c67e1ea
Content-Type: text/plain; charset=ISO-8859-1

No.  From the IETF home page, there is information that is under
www.ietf.org. However, all the detailed information (charters, drafts, etc.)
for the WGS are under datatracker: https://datatracker.ietf.org/

For example, this page summarizes what WGs and has links to all the useful
information, including WG chair specific pages:
http://www.ietf.org/wg/
Clickin on the *Active Working Group charters are available
here<http://www.ietf.org/dyn/wg/charter.html>
*  takes you to the datatracker pages.

So, IMHO, there is a fairly seamless interface to the tools pages and I find
that the addition of the link to the tools page for each of the WGs (from
the datatracker) makes things fairly seamless to me.  I usually go the
datatracker page for WGs and then navigate directly to the tools page.
Note also that there is a direct link to the tools pages from the main IETF
webpage (under Resources/Tools team pages).

Mary.

On Wed, Feb 16, 2011 at 8:59 AM, Worley, Dale R (Dale) <dworley@avaya.com>wrote:

> ________________________________________
> From: Mary Barnes [mary.ietf.barnes@gmail.com]
>
> The URLs for the tools pages are differentiated as http://tools.ietf.org/.
> ________________________________________
>
> Interesting!  Are all pages that do *not* have hostname "tools.ietf.org"
> part of the "datagracker" system?
>
> Dale
>

--20cf3054ab5ffdb4eb049c67e1ea
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

No. =A0From the IETF home page, there is information that is under <a href=
=3D"http://www.ietf.org">www.ietf.org</a>. However, all the detailed inform=
ation (charters, drafts, etc.) for the WGS are under datatracker: <a href=
=3D"https://datatracker.ietf.org/">https://datatracker.ietf.org/</a><div>
<br></div><div>For example, this page summarizes what WGs and has links to =
all the useful information, including WG chair specific pages:</div><div><a=
 href=3D"http://www.ietf.org/wg/">http://www.ietf.org/wg/</a></div><div>Cli=
ckin on the=A0<span class=3D"Apple-style-span" style=3D"font-family: Verdan=
a, Arial, Helvetica, sans-serif; font-size: 13px; "><strong>Active Working =
Group=A0<a href=3D"http://www.ietf.org/dyn/wg/charter.html">charters are av=
ailable here</a></strong></span>=A0=A0takes you to the datatracker pages.</=
div>
<div><div><br></div><div>So, IMHO, there is a fairly seamless interface to =
the tools pages and I find that the addition of the link to the tools page =
for each of the WGs (from the datatracker) makes things fairly seamless to =
me. =A0I usually go the datatracker page for WGs and then navigate directly=
 to the tools page. =A0 Note also that there is a direct link to the tools =
pages from the main IETF webpage (under Resources/Tools team pages).</div>
<div><br></div><div>Mary.=A0</div><div><br><div class=3D"gmail_quote">On We=
d, Feb 16, 2011 at 8:59 AM, Worley, Dale R (Dale) <span dir=3D"ltr">&lt;<a =
href=3D"mailto:dworley@avaya.com">dworley@avaya.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex;">
________________________________________<br>
From: Mary Barnes [<a href=3D"mailto:mary.ietf.barnes@gmail.com">mary.ietf.=
barnes@gmail.com</a>]<br>
<div class=3D"im"><br>
The URLs for the tools pages are differentiated as <a href=3D"http://tools.=
ietf.org/" target=3D"_blank">http://tools.ietf.org/</a>.<br>
</div>________________________________________<br>
<br>
Interesting! =A0Are all pages that do *not* have hostname &quot;<a href=3D"=
http://tools.ietf.org" target=3D"_blank">tools.ietf.org</a>&quot; part of t=
he &quot;datagracker&quot; system?<br>
<font color=3D"#888888"><br>
Dale<br>
</font></blockquote></div><br></div></div>

--20cf3054ab5ffdb4eb049c67e1ea--

From wwwrun@core3.amsl.com  Thu Feb 17 13:48:59 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id E588D3A6DC3; Thu, 17 Feb 2011 13:48:58 -0800 (PST)
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: IETF 80 - Social Event 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110217214858.E588D3A6DC3@core3.amsl.com>
Date: Thu, 17 Feb 2011 13:48:58 -0800 (PST)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 21:48:59 -0000

80th IETF Meeting
Prague, Czech Republic
March 27 - April 1, 2011
Host: CZ.NIC

1.  Social Event
2.  Host Web Page
3.  Registration

1.  Social Event
	General information: http://www.ietf80.cz/page/851/ietf-80/
	Date: Tuesday, 29 March 2011
	Time: 19:00

	The IETF 80 social event, hosted by CZ.NIC, will take place in
	the Municipal House. You will be able to survey very beautiful
	Art Nouveau building in the heart of Prague. As a contrast of 
	a historical building you will be treated to a very modern 
	performance of La Putyka. You will also have a possibility to
	taste variations of Czech cusine.

2.  Host Web Page
	CZ.NIC has set up a web page with information for travelers to
	Prague, please visit:
	http://www.ietf80.cz/

3. Registration
	Register online at:
	http://www.ietf.org/meetings/80/

Only 38 days until the Prague IETF!


From wwwrun@core3.amsl.com  Fri Feb 18 02:26:46 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 8A5B33A6DEB; Fri, 18 Feb 2011 02:26:46 -0800 (PST)
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: RFP for Legal Services Provider 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110218102646.8A5B33A6DEB@core3.amsl.com>
Date: Fri, 18 Feb 2011 02:26:46 -0800 (PST)
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 10:26:46 -0000

The Internet Society, on behalf of the IETF Administrative Oversight
Committee (IAOC), announces this Request for Proposals for a legal service
provider.  The successful bidder will enter into a contract with the
Internet Society.

The legal services provider (Provider) will provide advice to the IETF
Engineering Steering Group, IAOC, Internet Architecture Board, Internet
Research Task Force, RFC Series Editor, Independent Submissions Editor,
and the IETF Trust as requested, and will report to the IETF
Administrative Director.

The IAOC desires a long-term relationship commencing on 1 May 2011 of up
to four (4) years with a successful Provider.  Accordingly, it is looking
to structure a four (4) year term with contract review points at the
one-year and three-year marks to evaluate the success of the service
provider. The contract may be extended twice of one year’s duration each
for a possible contract term of six (6).  

The Internet Engineering Task Force (IETF) is a community of volunteers
interested in contributing to the long-term vitality of the Internet.  The
Internet Society is the organizational home of the IETF and is itself a
non-profit organization.  Pro bono bids are welcomed, however, where that
is not possible a fixed price would be desirable. It is understood that
for certain services additional costs may apply.  

Traditionally, the legal services that IETF has required have included
the following:

a)	Advice regarding the conduct of standard-setting activities,
particularly antitrust and intellectual property implications of IETF
policies and activities

b)	Development, drafting and interpretation of IETF policies relating to
intellectual property, namely copyright and patent policies

c)	Advice regarding the acquisition and licensing of intellectual
property held by the IETF Trust

d)	Maintenance and oversight of IETF’s global trademark portfolio

e)	Advice with drafting and negotiation of contracts with vendors and
service providers

f)	Response to third party subpoenas served on IETF by litigants in
cases, typically patent infringement suits, in which IETF standards or
activities are implicated

g)	Governance and procedural issues relating to the IETF Trust and IETF
in general

h)	Analysis and advice relating to relationships with other standards
development organizations, governmental entities, and the like

i)	Training sessions for the IETF Trust, as well as the IETF and WG
leadership on the above topics 

The RFP can be found at: http://iaoc.ietf.org/rfpsrfis.html 

Proposals must be received via email at rpelletier@isoc.org no later than
March 21, 2011 5:00 P.M. EST.  All questions/inquiries must be submitted
in writing and must be received no later than midnight, EST, March 1,
2011.  Responses to questions and inquiries shall be posted online at: 
http://iaoc.ietf.org/rfpsrfis.html by midnight, EST, March 7, 2011. 

The point of contact regarding this RFP is the IETF Administrative
Director, Ray Pelletier.

Ray Pelletier
IETF Administrative Director

From wwwrun@core3.amsl.com  Tue Feb 22 11:24:58 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id EC1893A6884; Tue, 22 Feb 2011 11:24:57 -0800 (PST)
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: IETF 80 - Hotel Reservation Cutoff 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110222192457.EC1893A6884@core3.amsl.com>
Date: Tue, 22 Feb 2011 11:24:57 -0800 (PST)
Cc: wgchairs@ietf.org, 80attendees@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 19:24:58 -0000

80th IETF Meeting
Prague, Czech Republic
March 27 - April 1, 2011
Host: CZ.NIC

The cut-off date for receiving the group rate at the Hilton is March 9,
please make your reservation soon!

Hotel Accommodations
	Reservations Cut off Date: 9 March 2011 (Hilton), 11 March 2011
	(Sheraton and InterContinental).

	For additional information on rates and policies, please visit:
	http://www.ietf.org/meeting/80/hotel.html

Register for the IETF Meeting online at:
	http://www.ietf.org/meetings/80/

Only 33 days until the Prague IETF!


From wwwrun@core3.amsl.com  Tue Feb 22 20:51:05 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 918EE3A69E3; Tue, 22 Feb 2011 20:51:04 -0800 (PST)
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: XML2RFC RFP on Hold 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110223045104.918EE3A69E3@core3.amsl.com>
Date: Tue, 22 Feb 2011 20:51:04 -0800 (PST)
Cc: wgchairs@ietf.org, rfc-interest@rfc-editor.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 04:51:05 -0000

Based on community discussion, the IAOC has decided to put the XML2RFC RFP
on hold, notify potential bidders of this, and have a community comment
period on the tools-discuss@ietf.org list.  Subscription information can
be found at:

 https://www.ietf.org/mailman/listinfo/tools-discuss

The RFP is located at:  

 http://iaoc.ietf.org/rfpsrfis.html 

The comment period will end on March 9.  

Please note that the main goal is to have a supportable xml2rfc tool this
year that works for the current users and provides the functionality of
the current tool with some incremental improvements.  There will be an
opportunity in the future for changes that can not be accommodated in this
phase.  

Ray Pelletier
IETF Administrative Director

From henrik@levkowetz.com  Wed Feb 23 08:11:05 2011
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D1143A6922 for <wgchairs@core3.amsl.com>; Wed, 23 Feb 2011 08:11:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JTwc1iCAs2h4 for <wgchairs@core3.amsl.com>; Wed, 23 Feb 2011 08:11:02 -0800 (PST)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id 130053A6933 for <wgchairs@ietf.org>; Wed, 23 Feb 2011 08:11:02 -0800 (PST)
Received: from localhost ([127.0.0.1]:45308 helo=dyn-fg117.sth.netnod.se) by merlot.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1PsHJP-00020g-Oh; Wed, 23 Feb 2011 17:11:35 +0100
Message-ID: <4D6531B7.4030202@levkowetz.com>
Date: Wed, 23 Feb 2011 17:11:35 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: WG Chairs <wgchairs@ietf.org>
Subject: Email input to WG issue trackers.
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: wgchairs@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 16:11:05 -0000

Hi,


Till now, the WG issue trackers maintained at tools.ietf.org have provided
the option to send email to the WG mailing list when an issue is added or
updated, but it has not been possible to automatically capture responses
as ticket updates.  With some coding yesterday I've adapted an existing
email2trac add-on so that this becomes possible.  By default this is not
enabled yet; I'd like to have a few WGs test this before I turn it on by
default.

Any takers?


Best,

	Henrik


From warren@kumari.net  Wed Feb 23 08:24:20 2011
Return-Path: <warren@kumari.net>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4C713A690A for <wgchairs@core3.amsl.com>; Wed, 23 Feb 2011 08:24:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.016
X-Spam-Level: 
X-Spam-Status: No, score=-102.016 tagged_above=-999 required=5 tests=[AWL=0.583, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bvoMYtrpeBXU for <wgchairs@core3.amsl.com>; Wed, 23 Feb 2011 08:24:19 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by core3.amsl.com (Postfix) with ESMTP id BCC953A68AC for <wgchairs@ietf.org>; Wed, 23 Feb 2011 08:24:19 -0800 (PST)
Received: from [172.19.118.186] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 8836F1B4096C; Wed, 23 Feb 2011 11:25:06 -0500 (EST)
Message-Id: <A4BADE0C-154D-4466-85E7-5C5B679BC469@kumari.net>
From: Warren Kumari <warren@kumari.net>
To: Henrik Levkowetz <henrik@levkowetz.com>
In-Reply-To: <4D6531B7.4030202@levkowetz.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Email input to WG issue trackers.
Date: Wed, 23 Feb 2011 11:25:04 -0500
References: <4D6531B7.4030202@levkowetz.com>
X-Mailer: Apple Mail (2.936)
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 16:24:20 -0000

On Feb 23, 2011, at 11:11 AM, Henrik Levkowetz wrote:

> Hi,
>
>
> Till now, the WG issue trackers maintained at tools.ietf.org have  
> provided
> the option to send email to the WG mailing list when an issue is  
> added or
> updated, but it has not been possible to automatically capture  
> responses
> as ticket updates.  With some coding yesterday I've adapted an  
> existing
> email2trac add-on so that this becomes possible.  By default this is  
> not
> enabled yet; I'd like to have a few WGs test this before I turn it  
> on by
> default.
>
> Any takers?

DANE will give it a whirl --- we use the issue tracker to try and stay  
focused (with varying levels of success ;-) ) and will be happy to be  
guinea pigs...

W

>
>
> Best,
>
> 	Henrik
>


From henrik@levkowetz.com  Wed Feb 23 09:20:04 2011
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB6D93A68C5 for <wgchairs@core3.amsl.com>; Wed, 23 Feb 2011 09:20:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aVOph6agIULW for <wgchairs@core3.amsl.com>; Wed, 23 Feb 2011 09:20:03 -0800 (PST)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id A62093A67A1 for <wgchairs@ietf.org>; Wed, 23 Feb 2011 09:20:03 -0800 (PST)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:63098 helo=dyn-fg117.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1PsIMA-0003hc-NV; Wed, 23 Feb 2011 18:18:33 +0100
Message-ID: <4D654165.9090900@levkowetz.com>
Date: Wed, 23 Feb 2011 18:18:29 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
References: <4D6531B7.4030202@levkowetz.com> <A4BADE0C-154D-4466-85E7-5C5B679BC469@kumari.net>
In-Reply-To: <A4BADE0C-154D-4466-85E7-5C5B679BC469@kumari.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: warren@kumari.net, wgchairs@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: Email input to WG issue trackers.
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 17:20:04 -0000

Hi Warren,

On 2011-02-23 17:25 Warren Kumari said:
> On Feb 23, 2011, at 11:11 AM, Henrik Levkowetz wrote:

...
>> Any takers?
> 
> DANE will give it a whirl --- we use the issue tracker to try and stay  
> focused (with varying levels of success ;-) ) and will be happy to be  
> guinea pigs...

Great.  I've enabled this for dane.  Please note that it will work for
replies that go to trac+dane@trac.tools.ietf.org, which is the From:
address used by the dane issue tracker from now on.  Earlier the tracker
used the more generic address trac@tools.ietf.org; replies to that
address won't cause automatic updates to the relevant issue.


Best,

	Henrik

From dwing@cisco.com  Wed Feb 23 09:56:17 2011
Return-Path: <dwing@cisco.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E45E3A6915 for <wgchairs@core3.amsl.com>; Wed, 23 Feb 2011 09:56:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.308
X-Spam-Level: 
X-Spam-Status: No, score=-110.308 tagged_above=-999 required=5 tests=[AWL=0.291, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qHWhrwKWyLnI for <wgchairs@core3.amsl.com>; Wed, 23 Feb 2011 09:56:16 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 4E76F3A6810 for <wgchairs@ietf.org>; Wed, 23 Feb 2011 09:56:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=580; q=dns/txt; s=iport; t=1298483824; x=1299693424; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=DCSnVrlYkKDEuqoDKqRvXUSVYcpXZ53aMSBpFFZ7HAk=; b=L4APDjD+lWtSgYuz92++Y9jfB43eMG3mhso6u7fEmfrxygsVsnBcouTF qoqP+4QxIkAXf4y+X0ZVhLIeXFS3rPTlJBxuSTtISkXkrvTSUwWRQhrvf BapZEvcgoFo+fHWie7whqZrerurennYE7gO1yyzmfG1zZ5thHd6Q/iqHi Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAIfYZE2rRN+K/2dsb2JhbACZMoxnc6AEm3yFXgSFDQ
X-IronPort-AV: E=Sophos;i="4.62,213,1297036800"; d="scan'208";a="269288759"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-3.cisco.com with ESMTP; 23 Feb 2011 17:57:04 +0000
Received: from dwingWS ([10.32.240.195]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p1NHv3nB007750; Wed, 23 Feb 2011 17:57:03 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Henrik Levkowetz'" <henrik@levkowetz.com>, "'WG Chairs'" <wgchairs@ietf.org>
References: <4D6531B7.4030202@levkowetz.com>
In-Reply-To: <4D6531B7.4030202@levkowetz.com>
Subject: RE: Email input to WG issue trackers.
Date: Wed, 23 Feb 2011 09:57:03 -0800
Message-ID: <1ab901cbd383$13f6d0b0$3be47210$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvTdGaHr0dcd93vQSuiCwS2wctUZQADqPFQ
Content-Language: en-us
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 17:56:17 -0000

> Till now, the WG issue trackers maintained at tools.ietf.org have
> provided
> the option to send email to the WG mailing list when an issue is added
> or
> updated, but it has not been possible to automatically capture
> responses
> as ticket updates.  With some coding yesterday I've adapted an existing
> email2trac add-on so that this becomes possible.  By default this is
> not
> enabled yet; I'd like to have a few WGs test this before I turn it on
> by
> default.
> 
> Any takers?

Neat.  Thanks for doing that.  It will help use the trackers more.

-d



From tena@huawei.com  Wed Feb 23 11:24:44 2011
Return-Path: <tena@huawei.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E10583A6A22 for <wgchairs@core3.amsl.com>; Wed, 23 Feb 2011 11:24:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.457
X-Spam-Level: 
X-Spam-Status: No, score=-106.457 tagged_above=-999 required=5 tests=[AWL=0.142, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qskTlMavlhmt for <wgchairs@core3.amsl.com>; Wed, 23 Feb 2011 11:24:44 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id F2F113A6940 for <wgchairs@ietf.org>; Wed, 23 Feb 2011 11:24:43 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LH300MJV4MIIV@usaga02-in.huawei.com> for wgchairs@ietf.org; Wed, 23 Feb 2011 11:25:31 -0800 (PST)
Received: from TingZousc1 ([10.193.34.106]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LH300K8R4MI33@usaga02-in.huawei.com> for wgchairs@ietf.org; Wed, 23 Feb 2011 11:25:30 -0800 (PST)
Date: Wed, 23 Feb 2011 11:25:32 -0800
From: Tina Tsou <tena@huawei.com>
Subject: RE: Email input to WG issue trackers.
In-reply-to: <1ab901cbd383$13f6d0b0$3be47210$@com>
To: 'Dan Wing' <dwing@cisco.com>, 'Henrik Levkowetz' <henrik@levkowetz.com>, 'WG Chairs' <wgchairs@ietf.org>
Message-id: <00d901cbd38f$70c76190$525624b0$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcvTdGaHr0dcd93vQSuiCwS2wctUZQADqPFQAAMQSTA=
References: <4D6531B7.4030202@levkowetz.com> <1ab901cbd383$13f6d0b0$3be47210$@com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 19:24:45 -0000

Thank you too; sorry it was me who triggered this issue yesterday.


We keep our promises with one another - no matter what!

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html


-----Original Message-----
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behalf
Of Dan Wing
Sent: Wednesday, February 23, 2011 9:57 AM
To: 'Henrik Levkowetz'; 'WG Chairs'
Subject: RE: Email input to WG issue trackers.

> Till now, the WG issue trackers maintained at tools.ietf.org have
> provided
> the option to send email to the WG mailing list when an issue is added
> or
> updated, but it has not been possible to automatically capture
> responses
> as ticket updates.  With some coding yesterday I've adapted an existing
> email2trac add-on so that this becomes possible.  By default this is
> not
> enabled yet; I'd like to have a few WGs test this before I turn it on
> by
> default.
> 
> Any takers?

Neat.  Thanks for doing that.  It will help use the trackers more.

-d




From wwwrun@core3.amsl.com  Thu Feb 24 20:29:52 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 4367F3A6904; Thu, 24 Feb 2011 20:29:51 -0800 (PST)
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 80th IETF DRAFT Agenda 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110225042952.4367F3A6904@core3.amsl.com>
Date: Thu, 24 Feb 2011 20:29:52 -0800 (PST)
Cc: irsg@isi.edu, irtf-chair@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 04:29:52 -0000

The DRAFT agenda is ready for viewing.  Please note the cutoff date for
requests to reschedule Working Group and BOF meetings is February 28, 2011
17:00 PT.  The final agenda will be published on March 4, 2011.

https://datatracker.ietf.org/meeting/80/agenda.html
https://datatracker.ietf.org/meeting/80/agenda.txt

http://www.ietf.org/meeting/80/index.html


Thanks,
Wanda

Only 31 days until the Prague IETF!
Online registration for the IETF meeting is at:
http://www.ietf.org/meetings/80/

From lars.eggert@nokia.com  Thu Feb 24 23:14:02 2011
Return-Path: <lars.eggert@nokia.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C20033A6938 for <wgchairs@core3.amsl.com>; Thu, 24 Feb 2011 23:14:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.121
X-Spam-Level: 
X-Spam-Status: No, score=-103.121 tagged_above=-999 required=5 tests=[AWL=0.478, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NWXGSVIiwTaF for <wgchairs@core3.amsl.com>; Thu, 24 Feb 2011 23:14:00 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id B87073A692F for <wgchairs@ietf.org>; Thu, 24 Feb 2011 23:14:00 -0800 (PST)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da01.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p1P7Enpw030778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Fri, 25 Feb 2011 09:14:51 +0200
From: Lars Eggert <lars.eggert@nokia.com>
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary=Apple-Mail-11-335817980; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: 80th IETF DRAFT Agenda 
Date: Fri, 25 Feb 2011 09:14:41 +0200
In-Reply-To: <20110225042952.4367F3A6904@core3.amsl.com>
To: Working Group Chairs <wgchairs@ietf.org>
References: <20110225042952.4367F3A6904@core3.amsl.com>
Message-Id: <E3598C87-7001-40A2-B88F-DED9A776C2D4@nokia.com>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Fri, 25 Feb 2011 09:14:46 +0200 (EET)
X-Nokia-AV: Clean
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 07:14:02 -0000

--Apple-Mail-11-335817980
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2011-2-25, at 6:29, IETF Agenda wrote:
> https://datatracker.ietf.org/meeting/80/agenda.html

is it possible to get an iCal subscription with the selections made on =
the URL above? (I like this interface better than the tools interface, =
but the tools one gives me the iCal calendar...)

Thanks,
Lars


--Apple-Mail-11-335817980
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMRjCCBVAw
ggQ4oAMCAQICEGxdPUZzCwUJ8KBiJwH+bYgwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMDEwMTUwMDAwMDBaFw0x
MTEwMTUyMzU5NTlaMIIBEzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9r
aWEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwolKEyOz/NQZJJlw0x9XBS9W
wCmabdY1fXpbWSdcaJiEWhQpRzSIC/pgIwCgaUW9g3JsWioXCawyjUVeg8xR42sR690f4z+OPAUm
3jokZxsuRaGX6fuPkPQomYAGz7htUHws/8FZIU+4dciETQf4vF5ptitJ+QZCVRCTLqisj6mG/kG4
65Op3G5/YZF9F/a390LdhuRP6vdY2Y+dqm8LDa0zmENPpoE98u1pIZGqCcnskN/nNBtEPd+a4lNh
ZSGnPuL4XCUSJYR9NB7FAYBvi5N7LSWHR3fspwa5EgpXynJcsLzaLA0iGfjFOBYFxul/07edmyw4
FIXuCIkaMDUfEwIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcX
ATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIF
oDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDov
L2luZGMxZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3Js
MA0GCSqGSIb3DQEBBQUAA4IBAQAlSTzUKqa3ZouKWFQfIJ+4l/KsztPnY4Onwzt8lqAmeiFPqOmf
kLTXbXDKtC6caFadNtyHpnsmQFFKXwhe5Z9/AaVSwryu6F9992DzYLp3j8PE0DSU0wmpUXUtp+rz
TFqJRkzB8RCBoq/TPBmkMPr68qB0TkU3dbYiVIvscOt1MRkdHiwG4wKQLyCf8XRRWqmMY6lbun7g
kiEWiris5StGKRvE5+e1SrcdnoZxIKQFF7Etr+4ftClrsDQWX9nRCEjYcmz4y/deq+HU8ylBaKZE
0ZJmcnYlAaD50OYWi0ckGDnKYyeMUEtCZJSV0otm2LqyIUAu9WPv/GNHt2ntjnUaMIIG7jCCBdag
AwIBAgIQcRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTow
OAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5
MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g
QXV0aG9yaXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBO
ZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t
L3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJp
U2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6Zvg
SU6Lb9UB0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHs
EnMhjfXcMM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO
4YM/d/mZ//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSy
riMGZSalJ1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCC
ArUwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20w
EgYDVR0TAQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUH
AgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWdu
LmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgw
VhYJaW1hZ2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDov
L2xvZ28udmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQ
cml2YXRlTGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYD
VR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4x
HzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlT
aWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENs
YXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaE
VIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlM
JBq6WaSHO3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKv
YLMVirOVnDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDR
yxTWcVibvtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy
+kgOZY5JyNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/
wYIxggSLMIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMu
MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2Ny
aWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJ
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDIyNTA3MTQ0MVowIwYJKoZIhvcNAQkE
MRYEFBpNVYtyi86F6Llxtd6C1Plt8fwpMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
ALiAFvb/6lt/ZFiuAA1tf4FL1zNsC+puSvGD90FZBuvu61xfMzJEw210wbf4Y8Iei0OOT09jsAmY
gWZPTvNZJZ0OdrkrvVg4n/QWKsiIdMqAOtvnf0Br0u7k1G6y6ptLyLlRK1PGwDXj6O+C0y3vjNGT
31JGk7gziLui276k0GcxLtWnXmhhzezEOG8q+80XBOGt32E56QDtEVfd6pzTV8g/B/2ze+ngrIlz
BCtHyddBRiAWHTFKj0esuwN2Mv5vZpKm4vxDugpLgr45sQHcthPJKiy+F0Ny3cbIU7D1J/pldyhH
VL2RPAdDMmgChDuB6kNLe93Oe/9FkmJAXgLAS0oAAAAAAAA=

--Apple-Mail-11-335817980--

From ben@niven-jenkins.co.uk  Fri Feb 25 00:44:20 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AF883A693B for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 00:44:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.882
X-Spam-Level: 
X-Spam-Status: No, score=-103.882 tagged_above=-999 required=5 tests=[AWL=-0.883, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Obe1iI5XyDU for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 00:44:19 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by core3.amsl.com (Postfix) with ESMTP id 815963A692F for <wgchairs@ietf.org>; Fri, 25 Feb 2011 00:44:19 -0800 (PST)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-144-devlan.cachelogic.com) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1PstIU-0005O6-3H for wgchairs@ietf.org; Fri, 25 Feb 2011 08:45:10 +0000
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: How to add a draft to the "Related Documents" section of the datatracker?
Date: Fri, 25 Feb 2011 08:45:09 +0000
Message-Id: <D15B5D00-8A86-4B9F-BD36-17DAB9A99703@niven-jenkins.co.uk>
To: wgchairs@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 08:44:20 -0000

Fellow WG chairs,

In L3VPN the chairs have had a request by an author to add two drafts to =
the "Related Documents" section of the WG's datatracker page.

One draft wasn't picked up automatically because the author hasn't =
followed the normal naming convention and didn't include l3vpn in the =
document filename (but the document is now on revision -04 so renaming =
would be non-ideal).

The other is owned by a different WG but does have applicability to =
L3VPN.

Does anyone know how (or if) I can add them to the list of related =
documents?

Thanks in advance
Ben


From peter.musgrave@magorcorp.com  Fri Feb 25 02:42:07 2011
Return-Path: <peter.musgrave@magorcorp.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 46CA43A694D for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 02:42:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.225
X-Spam-Level: 
X-Spam-Status: No, score=-103.225 tagged_above=-999 required=5 tests=[AWL=-0.226, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fWLD-vi8kn7k for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 02:42:06 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 61D353A685B for <wgchairs@ietf.org>; Fri, 25 Feb 2011 02:42:06 -0800 (PST)
Received: by iwl42 with SMTP id 42so1102637iwl.31 for <wgchairs@ietf.org>; Fri, 25 Feb 2011 02:42:58 -0800 (PST)
Received: by 10.42.241.73 with SMTP id ld9mr586690icb.265.1298630578060; Fri, 25 Feb 2011 02:42:58 -0800 (PST)
Received: from [192.168.1.100] ([204.237.32.134]) by mx.google.com with ESMTPS id z4sm607923ibg.7.2011.02.25.02.42.56 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 25 Feb 2011 02:42:57 -0800 (PST)
Subject: Re: How to add a draft to the "Related Documents" section of the datatracker?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Peter Musgrave <peter.musgrave@magorcorp.com>
In-Reply-To: <D15B5D00-8A86-4B9F-BD36-17DAB9A99703@niven-jenkins.co.uk>
Date: Fri, 25 Feb 2011 05:42:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5F971F9-0158-4CA5-BBA2-64E404C845C0@magorcorp.com>
References: <D15B5D00-8A86-4B9F-BD36-17DAB9A99703@niven-jenkins.co.uk>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
X-Mailer: Apple Mail (2.1082)
Cc: wgchairs@ietf.org, Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 10:42:07 -0000

Hi Ben,=20

I did some work in that code on the last code sprint. As far as I =
remember the search is keying off the WG name.=20

I can put in a ticket on this for the next sprint in March. =20

I have also CCed Henrick. Perhaps he has better insight...

Regards,=20

Peter Musgrave

On 2011-02-25, at 3:45 AM, Ben Niven-Jenkins wrote:

> Fellow WG chairs,
>=20
> In L3VPN the chairs have had a request by an author to add two drafts =
to the "Related Documents" section of the WG's datatracker page.
>=20
> One draft wasn't picked up automatically because the author hasn't =
followed the normal naming convention and didn't include l3vpn in the =
document filename (but the document is now on revision -04 so renaming =
would be non-ideal).
>=20
> The other is owned by a different WG but does have applicability to =
L3VPN.
>=20
> Does anyone know how (or if) I can add them to the list of related =
documents?
>=20
> Thanks in advance
> Ben
>=20


From brian@innovationslab.net  Fri Feb 25 04:51:01 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F5ED3A69AB for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 04:51:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.149
X-Spam-Level: 
X-Spam-Status: No, score=-102.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T9wgcpg89IXh for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 04:51:00 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id 34E5C3A69A8 for <wgchairs@ietf.org>; Fri, 25 Feb 2011 04:50:57 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 5348F8822E for <wgchairs@ietf.org>; Fri, 25 Feb 2011 04:51:48 -0800 (PST)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 8FD8E130002 for <wgchairs@ietf.org>; Fri, 25 Feb 2011 04:51:44 -0800 (PST)
Message-ID: <4D67A5DB.4010000@innovationslab.net>
Date: Fri, 25 Feb 2011 07:51:39 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: How to add a draft to the "Related Documents" section of the datatracker?
References: <D15B5D00-8A86-4B9F-BD36-17DAB9A99703@niven-jenkins.co.uk> <C5F971F9-0158-4CA5-BBA2-64E404C845C0@magorcorp.com>
In-Reply-To: <C5F971F9-0158-4CA5-BBA2-64E404C845C0@magorcorp.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 12:51:01 -0000

On 2/25/11 5:42 AM, Peter Musgrave wrote:
> Hi Ben,
> 
> I did some work in that code on the last code sprint. As far as I
> remember the search is keying off the WG name.
> 
> I can put in a ticket on this for the next sprint in March.
> 
> I have also CCed Henrick. Perhaps he has better insight...

Just thinking off of the top of my head, and with the caveat that it is
early in the morning... Would it make sense to have a mechanism in the
draft submission tool that allows an author to indicate WGs that their
draft may be related too?

Brian

> 
> Regards,
> 
> Peter Musgrave
> 
> On 2011-02-25, at 3:45 AM, Ben Niven-Jenkins wrote:
> 
>> Fellow WG chairs,
>> 
>> In L3VPN the chairs have had a request by an author to add two
>> drafts to the "Related Documents" section of the WG's datatracker
>> page.
>> 
>> One draft wasn't picked up automatically because the author hasn't
>> followed the normal naming convention and didn't include l3vpn in
>> the document filename (but the document is now on revision -04 so
>> renaming would be non-ideal).
>> 
>> The other is owned by a different WG but does have applicability to
>> L3VPN.
>> 
>> Does anyone know how (or if) I can add them to the list of related
>> documents?
>> 
>> Thanks in advance Ben
>> 


From ietfdbh@comcast.net  Fri Feb 25 08:20:31 2011
Return-Path: <ietfdbh@comcast.net>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5DA4D3A69EC for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 08:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y8m1Edkng3hq for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 08:20:30 -0800 (PST)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by core3.amsl.com (Postfix) with ESMTP id 50CDB3A69E9 for <wgchairs@ietf.org>; Fri, 25 Feb 2011 08:20:30 -0800 (PST)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by QMTA11.westchester.pa.mail.comcast.net with comcast id CFZS1g0021ZXKqc5BGMP4q; Fri, 25 Feb 2011 16:21:23 +0000
Received: from davidPC ([67.189.235.106]) by omta21.westchester.pa.mail.comcast.net with comcast id CGMA1g00A2JQnJT3hGMHYJ; Fri, 25 Feb 2011 16:21:21 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Brian Haberman'" <brian@innovationslab.net>, <wgchairs@ietf.org>
References: <D15B5D00-8A86-4B9F-BD36-17DAB9A99703@niven-jenkins.co.uk><C5F971F9-0158-4CA5-BBA2-64E404C845C0@magorcorp.com> <4D67A5DB.4010000@innovationslab.net>
In-Reply-To: <4D67A5DB.4010000@innovationslab.net>
Subject: RE: How to add a draft to the "Related Documents" section of thedatatracker?
Date: Fri, 25 Feb 2011 11:21:06 -0500
Message-ID: <1A5B6C1C10E64CE89794BB05847A7027@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16543
Thread-Index: AcvU6skCfzjqIi3VRG+mJ10aUS21dwAG3U+Q
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 16:20:31 -0000

Hi,

That capability already exists by including the WG name in the
filename.

I do not think it would be good to add an option where the author gets
to declare their draft is applicable to a whole bunch of WGs. This
might encourage WG shopping, trying to find a WG that would take an
interest in the draft. Currently, the author needs to decide in
advance which WG is an appropriate venue for their proposal (which
means they need to do some homework first). I would be concerned about
(inadvertent or deliberate) abuse of this option by authors.

It might make sense to me to allow WG chairs to add a draft as
relevant, but how important is this? A WG can always look at
individual drafts, and when the WG decides it really is relevant, they
can adopt it as a WG draft.  IIRC, datatracker extensions for WG
Chairs will have the ability to mark a draft as "being considered" by
a WG. 

dbh


> -----Original Message-----
> From: wgchairs-bounces@ietf.org 
> [mailto:wgchairs-bounces@ietf.org] On Behalf Of Brian Haberman
> Sent: Friday, February 25, 2011 7:52 AM
> To: wgchairs@ietf.org
> Subject: Re: How to add a draft to the "Related Documents" 
> section of thedatatracker?
> 
> On 2/25/11 5:42 AM, Peter Musgrave wrote:
> > Hi Ben,
> > 
> > I did some work in that code on the last code sprint. As far as I
> > remember the search is keying off the WG name.
> > 
> > I can put in a ticket on this for the next sprint in March.
> > 
> > I have also CCed Henrick. Perhaps he has better insight...
> 
> Just thinking off of the top of my head, and with the caveat 
> that it is
> early in the morning... Would it make sense to have a mechanism in
the
> draft submission tool that allows an author to indicate WGs that
their
> draft may be related too?
> 
> Brian
> 
> > 
> > Regards,
> > 
> > Peter Musgrave
> > 
> > On 2011-02-25, at 3:45 AM, Ben Niven-Jenkins wrote:
> > 
> >> Fellow WG chairs,
> >> 
> >> In L3VPN the chairs have had a request by an author to add two
> >> drafts to the "Related Documents" section of the WG's datatracker
> >> page.
> >> 
> >> One draft wasn't picked up automatically because the author
hasn't
> >> followed the normal naming convention and didn't include l3vpn in
> >> the document filename (but the document is now on revision -04 so
> >> renaming would be non-ideal).
> >> 
> >> The other is owned by a different WG but does have applicability
to
> >> L3VPN.
> >> 
> >> Does anyone know how (or if) I can add them to the list of
related
> >> documents?
> >> 
> >> Thanks in advance Ben
> >> 
> 
> 


From cabo@tzi.org  Fri Feb 25 08:30:15 2011
Return-Path: <cabo@tzi.org>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D56A3A6A19 for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 08:30:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.416
X-Spam-Level: 
X-Spam-Status: No, score=-106.416 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Od2Hx9L-zFS for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 08:30:14 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by core3.amsl.com (Postfix) with ESMTP id 1F6503A6A01 for <wgchairs@ietf.org>; Fri, 25 Feb 2011 08:30:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id p1PGUtBk016465; Fri, 25 Feb 2011 17:30:55 +0100 (CET)
Received: from [10.0.1.2] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id CB6E35F4; Fri, 25 Feb 2011 17:30:55 +0100 (CET)
Subject: Re: How to add a draft to the "Related Documents" section of thedatatracker?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <1A5B6C1C10E64CE89794BB05847A7027@davidPC>
Date: Fri, 25 Feb 2011 17:31:52 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <46291170-3DF1-4DFB-B7F6-F4F8F009A970@tzi.org>
References: <D15B5D00-8A86-4B9F-BD36-17DAB9A99703@niven-jenkins.co.uk><C5F971F9-0158-4CA5-BBA2-64E404C845C0@magorcorp.com> <4D67A5DB.4010000@innovationslab.net> <1A5B6C1C10E64CE89794BB05847A7027@davidPC>
To: "David Harrington" <ietfdbh@comcast.net>
X-Mailer: Apple Mail (2.1082)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 16:30:15 -0000

On Feb 25, 2011, at 17:21, David Harrington wrote:

> I do not think it would be good to add an option where the author gets
> to declare their draft is applicable to a whole bunch of WGs. This
> might encourage WG shopping,

+1.

Allowing the WG chair to add a draft to the WG would be a good new function.

Gruesse, Carsten


From ben@niven-jenkins.co.uk  Fri Feb 25 08:32:38 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2ECFB3A69EC for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 08:32:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.437
X-Spam-Level: 
X-Spam-Status: No, score=-104.437 tagged_above=-999 required=5 tests=[AWL=-0.837, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tiqwo5ojoz40 for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 08:32:37 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.64]) by core3.amsl.com (Postfix) with ESMTP id 4E7E63A69BA for <wgchairs@ietf.org>; Fri, 25 Feb 2011 08:32:37 -0800 (PST)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-144-devlan.cachelogic.com) by mail6.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1Pt0bh-0003IR-Pk; Fri, 25 Feb 2011 16:33:30 +0000
Subject: Re: How to add a draft to the "Related Documents" section of thedatatracker?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <1A5B6C1C10E64CE89794BB05847A7027@davidPC>
Date: Fri, 25 Feb 2011 16:33:27 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <B106A89D-5B35-427A-B048-BC7AA2B3E234@niven-jenkins.co.uk>
References: <D15B5D00-8A86-4B9F-BD36-17DAB9A99703@niven-jenkins.co.uk><C5F971F9-0158-4CA5-BBA2-64E404C845C0@magorcorp.com> <4D67A5DB.4010000@innovationslab.net> <1A5B6C1C10E64CE89794BB05847A7027@davidPC>
To: "David Harrington" <ietfdbh@comcast.net>
X-Mailer: Apple Mail (2.1082)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 16:32:38 -0000

David,

On 25 Feb 2011, at 16:21, David Harrington wrote:
> It might make sense to me to allow WG chairs to add a draft as
> relevant, but how important is this?

As I kicked off the thread...

I don't think it's that important. As it was requested by an author and =
that author is an experienced IETFer I just assumed the capability =
already existed and I didn't know how to access it.

Ben


From eburger@standardstrack.com  Fri Feb 25 12:59:59 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1529C3A6A49 for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 12:59:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mt-DCBukPkOw for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 12:59:58 -0800 (PST)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [66.117.4.68]) by core3.amsl.com (Postfix) with ESMTP id 1AFAC3A67AB for <wgchairs@ietf.org>; Fri, 25 Feb 2011 12:59:58 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer; b=me5YpqwtYy5vfncxmcLIi5vpq+Gj+Cj74hW9NsLm23Cc6CoZCnWKOexN4OqXL8Z2/gKRwW1nxz7neCWAA9fmef+z6dUZIYG+8PFaPONx9htB26aJkg+l4DzMu71Sd5ou;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.134]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1Pt4mM-0003jf-Dz for wgchairs@ietf.org; Fri, 25 Feb 2011 13:00:46 -0800
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary=Apple-Mail-126-385384561; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: 80th IETF DRAFT Agenda 
Date: Fri, 25 Feb 2011 16:00:47 -0500
In-Reply-To: <E3598C87-7001-40A2-B88F-DED9A776C2D4@nokia.com>
To: Working Group Chairs <wgchairs@ietf.org>
References: <20110225042952.4367F3A6904@core3.amsl.com> <E3598C87-7001-40A2-B88F-DED9A776C2D4@nokia.com>
Message-Id: <47A6A27E-6DCA-4661-80C0-BBAB79B5A589@standardstrack.com>
X-Mailer: Apple Mail (2.1082)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 20:59:59 -0000

--Apple-Mail-126-385384561
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

+1
On Feb 25, 2011, at 2:14 AM, Lars Eggert wrote:

> Hi,
>=20
> On 2011-2-25, at 6:29, IETF Agenda wrote:
>> https://datatracker.ietf.org/meeting/80/agenda.html
>=20
> is it possible to get an iCal subscription with the selections made on =
the URL above? (I like this interface better than the tools interface, =
but the tools one gives me the iCal calendar...)
>=20
> Thanks,
> Lars
>=20


--Apple-Mail-126-385384561
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILHzCCBN0w
ggPFoAMCAQICEHGS++YZX6xNEoV0cTSiGKcwDQYJKoZIhvcNAQEFBQAwezELMAkGA1UEBhMCR0Ix
GzAZBgNVBAgMEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBwwHU2FsZm9yZDEaMBgGA1UECgwR
Q29tb2RvIENBIExpbWl0ZWQxITAfBgNVBAMMGEFBQSBDZXJ0aWZpY2F0ZSBTZXJ2aWNlczAeFw0w
NDAxMDEwMDAwMDBaFw0yODEyMzEyMzU5NTlaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQx
FzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsx
ITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJz
dC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVNNRm5pELlzkniii8efNIx
B8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQylbsMTzC9mKALi+VuG6JG+ni8
om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHG
TPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7Nl
yP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu9mIwFIws6wIDAQABo4IBJzCCASMwHwYDVR0j
BBgwFoAUoBEKIz6W8Qfs4q8p74Klf9AwpLQwHQYDVR0OBBYEFImCZ33EnSZwAEu0UEh83j2uBG59
MA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr
BgEFBQcDBDARBgNVHSAECjAIMAYGBFUdIAAwewYDVR0fBHQwcjA4oDagNIYyaHR0cDovL2NybC5j
b21vZG9jYS5jb20vQUFBQ2VydGlmaWNhdGVTZXJ2aWNlcy5jcmwwNqA0oDKGMGh0dHA6Ly9jcmwu
Y29tb2RvLm5ldC9BQUFDZXJ0aWZpY2F0ZVNlcnZpY2VzLmNybDARBglghkgBhvhCAQEEBAMCAQYw
DQYJKoZIhvcNAQEFBQADggEBAJ2Vyzy4fqUJxB6/C8LHdo45PJTGEKpPDMngq4RdiVTgZTvzbRx8
NywlVF+WIfw3hJGdFdwUT4HPVB1rbEVgxy35l1FM+WbKPKCCjKbI8OLp1Er57D9Wyd12jMOCAU9s
APMeGmF0BEcDqcZAV5G8ZSLFJ2dPV9tkWtmNH7qGL/QGrpxp7en0zykX2OBKnxogL5dMUbtGB8SK
N04g4wkxaMeexIud6H4RvDJoEJYRmETYKlFgTYjrdDrfQwYyyDlWjDoRUtNBpEMD9O3vMyfbOeAU
TibJ2PU54om4k123KSZB6rObroP8d3XK6Mq1/uJlSmM+RMTQw16Hc6mYHK9/FX8wggY6MIIFIqAD
AgECAhEAxcM7lN0zgrA71mfq+sG6xjANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0xMDA5MDgwMDAw
MDBaFw0xMTA5MDgyMzU5NTlaMIHhMTUwMwYDVQQLEyxDb21vZG8gVHJ1c3QgTmV0d29yayAtIFBF
UlNPTkEgTk9UIFZBTElEQVRFRDFGMEQGA1UECxM9VGVybXMgYW5kIENvbmRpdGlvbnMgb2YgdXNl
OiBodHRwOi8vd3d3LmNvbW9kby5uZXQvcmVwb3NpdG9yeTEfMB0GA1UECxMWKGMpMjAwMyBDb21v
ZG8gTGltaXRlZDEUMBIGA1UEAxMLRXJpYyBCdXJnZXIxKTAnBgkqhkiG9w0BCQEWGmVidXJnZXJA
c3RhbmRhcmRzdHJhY2suY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqeauFkEq
5Pj7AIAaDRbUWIpoblTKyrjcSfXRaHvjk0jWBTsBPe6oOZjudMK0Vo9A1Sl52BixDgf1/qb2Z+PT
7M0mqSOOsSucEBid48IMvGi79xmKKAVf5jiyFNNAaTZWn76dwNLMkKd/+Ki0fn8kEbb2zG+gGKyZ
MNHiNX+GQfPpHyzo2MTwnb16lXMfGJrGv4uLZS/pY9PENdFQnwV0ASZoqX+ArtLY2xeuC+rYG9xQ
Cz7qiLbJhCJzWsEGETyHLDjE5bN4HB9DsJKtGFLQuOdTanwGigNz9cVH9pLFNQxiotavAouXgqS4
wGvcq4mGP9w9zTychoUqIKsEg9OD1wIDAQABo4ICHDCCAhgwHwYDVR0jBBgwFoAUiYJnfcSdJnAA
S7RQSHzePa4Ebn0wHQYDVR0OBBYEFAlgEOVj6Hl0La8sPRP388HEMiWvMA4GA1UdDwEB/wQEAwIF
oDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgB
hvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0
cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMwgaUGA1UdHwSBnTCBmjBMoEqgSIZGaHR0cDovL2Ny
bC5jb21vZG9jYS5jb20vVVROLVVTRVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWls
LmNybDBKoEigRoZEaHR0cDovL2NybC5jb21vZG8ubmV0L1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0
aGVudGljYXRpb25hbmRFbWFpbC5jcmwwbAYIKwYBBQUHAQEEYDBeMDYGCCsGAQUFBzAChipodHRw
Oi8vY3J0LmNvbW9kb2NhLmNvbS9VVE5BQUFDbGllbnRDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6
Ly9vY3NwLmNvbW9kb2NhLmNvbTAlBgNVHREEHjAcgRplYnVyZ2VyQHN0YW5kYXJkc3RyYWNrLmNv
bTANBgkqhkiG9w0BAQUFAAOCAQEACRTppSEc5DMYn8YXcbfX36iTaNBGw1gUvTNam0U8pXH0E7H3
2d4cTq6DEMu5ifEvxMGBqhUyv0sKxQ7+UvtDwrk7Kiy2L6TUC4zNEklZbtDqY7+Wd7EQZkN4k/zx
kMLlz2VIIRL/Cg48NrBKP5bo1la78NTJx8m4+VForLseEBabxMQoWB/GOVC7WpO/+RCgd93gz6H/
RzW1hnK0Uvu5H3Kz7HEC3R1Qk/sE9nXVzTfoJOMJRnyMS5Ut61mgoWSm/kUtczAlRRYh6IBOhzAl
awoXz+yk9hMCheYRAWx0EamBBpSzvqXj0N2vXYc62v3e3ddcLZncjiB0pYIfCE3s4DGCA/8wggP7
AgEBMIHEMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBD
aXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cu
dXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIEVtYWlsAhEAxcM7lN0zgrA71mfq+sG6xjAJBgUrDgMCGgUAoIICDzAYBgkqhkiG9w0B
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTAyMjUyMTAwNDhaMCMGCSqGSIb3DQEJ
BDEWBBQlNEo94R4MMzqRL46fDLZDZFbdhzCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAG0JR3gPOprsqq93mHHD6MUM7dQmEwQZDQYyZmXTHajlEELi
+I+9HDUBr0yI3fVNe4xJ+lJW8mn18hTFLzX58yzTd9dOWqj8p9bONiYt7N+bVnEXBGX1OSLd4Kia
xx7+p6JS/VBuRwm5AKm7w7+HzR+IsvFksXygj0/vN9fa5/rshwq5hX/hV2eiVsR8trGupS46pvRh
jmkvVezyhEWWvbEZUgUR/T51uTTm6FmxQSlqzyudSB7ULu9ByHYfQ55EBsawT8rPRCBQQ+lG93z3
8qkaN3tu8j7D0UwADiGd89pdatIaOWmTs/9YbzzmOcyas6iXVsXlR320kcNpNkaasLYAAAAAAAA=

--Apple-Mail-126-385384561--

From eburger@standardstrack.com  Fri Feb 25 13:01:33 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44D103A6A40; Fri, 25 Feb 2011 13:01:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7U45CzSQmZ0T; Fri, 25 Feb 2011 13:01:32 -0800 (PST)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [66.117.4.68]) by core3.amsl.com (Postfix) with ESMTP id 3B8753A67AB; Fri, 25 Feb 2011 13:01:32 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Message-Id:References:To:X-Mailer; b=pSvn3JJg0gY5WOmtFVWyLJne2ewgNFS1pPXapKHyDqNlhxN0k1inAoe2ur6lGrJuaYa0cMdY1MblC9Fy0Zo9CEpA/3rDsREEE0sQKICzK2ymbUcn/fXM8ROk4tFHsPWB;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.134]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1Pt4ns-0004DH-2G; Fri, 25 Feb 2011 13:02:20 -0800
Subject: Re: 80th IETF DRAFT Agenda 
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary=Apple-Mail-127-385478388; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <20110225042952.4367F3A6904@core3.amsl.com>
Date: Fri, 25 Feb 2011 16:02:21 -0500
Message-Id: <FF9EABB4-1060-45CD-8667-EF2591068043@standardstrack.com>
References: <20110225042952.4367F3A6904@core3.amsl.com>
To: IETF Agenda <agenda@ietf.org>, rai-ads@tools.ietf.org
X-Mailer: Apple Mail (2.1082)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
Cc: Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 21:01:33 -0000

--Apple-Mail-127-385478388
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Any chance to swap rtcweb (Tues. AM) with sipcore (Weds. AM)?

On Feb 24, 2011, at 11:29 PM, IETF Agenda wrote:

> The DRAFT agenda is ready for viewing.  Please note the cutoff date for
> requests to reschedule Working Group and BOF meetings is February 28, 2011
> 17:00 PT.  The final agenda will be published on March 4, 2011.
> 
> https://datatracker.ietf.org/meeting/80/agenda.html
> https://datatracker.ietf.org/meeting/80/agenda.txt
> 
> http://www.ietf.org/meeting/80/index.html
> 
> 
> Thanks,
> Wanda
> 
> Only 31 days until the Prague IETF!
> Online registration for the IETF meeting is at:
> http://www.ietf.org/meetings/80/


--Apple-Mail-127-385478388
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILHzCCBN0w
ggPFoAMCAQICEHGS++YZX6xNEoV0cTSiGKcwDQYJKoZIhvcNAQEFBQAwezELMAkGA1UEBhMCR0Ix
GzAZBgNVBAgMEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBwwHU2FsZm9yZDEaMBgGA1UECgwR
Q29tb2RvIENBIExpbWl0ZWQxITAfBgNVBAMMGEFBQSBDZXJ0aWZpY2F0ZSBTZXJ2aWNlczAeFw0w
NDAxMDEwMDAwMDBaFw0yODEyMzEyMzU5NTlaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQx
FzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsx
ITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJz
dC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVNNRm5pELlzkniii8efNIx
B8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQylbsMTzC9mKALi+VuG6JG+ni8
om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHG
TPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7Nl
yP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu9mIwFIws6wIDAQABo4IBJzCCASMwHwYDVR0j
BBgwFoAUoBEKIz6W8Qfs4q8p74Klf9AwpLQwHQYDVR0OBBYEFImCZ33EnSZwAEu0UEh83j2uBG59
MA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr
BgEFBQcDBDARBgNVHSAECjAIMAYGBFUdIAAwewYDVR0fBHQwcjA4oDagNIYyaHR0cDovL2NybC5j
b21vZG9jYS5jb20vQUFBQ2VydGlmaWNhdGVTZXJ2aWNlcy5jcmwwNqA0oDKGMGh0dHA6Ly9jcmwu
Y29tb2RvLm5ldC9BQUFDZXJ0aWZpY2F0ZVNlcnZpY2VzLmNybDARBglghkgBhvhCAQEEBAMCAQYw
DQYJKoZIhvcNAQEFBQADggEBAJ2Vyzy4fqUJxB6/C8LHdo45PJTGEKpPDMngq4RdiVTgZTvzbRx8
NywlVF+WIfw3hJGdFdwUT4HPVB1rbEVgxy35l1FM+WbKPKCCjKbI8OLp1Er57D9Wyd12jMOCAU9s
APMeGmF0BEcDqcZAV5G8ZSLFJ2dPV9tkWtmNH7qGL/QGrpxp7en0zykX2OBKnxogL5dMUbtGB8SK
N04g4wkxaMeexIud6H4RvDJoEJYRmETYKlFgTYjrdDrfQwYyyDlWjDoRUtNBpEMD9O3vMyfbOeAU
TibJ2PU54om4k123KSZB6rObroP8d3XK6Mq1/uJlSmM+RMTQw16Hc6mYHK9/FX8wggY6MIIFIqAD
AgECAhEAxcM7lN0zgrA71mfq+sG6xjANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0xMDA5MDgwMDAw
MDBaFw0xMTA5MDgyMzU5NTlaMIHhMTUwMwYDVQQLEyxDb21vZG8gVHJ1c3QgTmV0d29yayAtIFBF
UlNPTkEgTk9UIFZBTElEQVRFRDFGMEQGA1UECxM9VGVybXMgYW5kIENvbmRpdGlvbnMgb2YgdXNl
OiBodHRwOi8vd3d3LmNvbW9kby5uZXQvcmVwb3NpdG9yeTEfMB0GA1UECxMWKGMpMjAwMyBDb21v
ZG8gTGltaXRlZDEUMBIGA1UEAxMLRXJpYyBCdXJnZXIxKTAnBgkqhkiG9w0BCQEWGmVidXJnZXJA
c3RhbmRhcmRzdHJhY2suY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqeauFkEq
5Pj7AIAaDRbUWIpoblTKyrjcSfXRaHvjk0jWBTsBPe6oOZjudMK0Vo9A1Sl52BixDgf1/qb2Z+PT
7M0mqSOOsSucEBid48IMvGi79xmKKAVf5jiyFNNAaTZWn76dwNLMkKd/+Ki0fn8kEbb2zG+gGKyZ
MNHiNX+GQfPpHyzo2MTwnb16lXMfGJrGv4uLZS/pY9PENdFQnwV0ASZoqX+ArtLY2xeuC+rYG9xQ
Cz7qiLbJhCJzWsEGETyHLDjE5bN4HB9DsJKtGFLQuOdTanwGigNz9cVH9pLFNQxiotavAouXgqS4
wGvcq4mGP9w9zTychoUqIKsEg9OD1wIDAQABo4ICHDCCAhgwHwYDVR0jBBgwFoAUiYJnfcSdJnAA
S7RQSHzePa4Ebn0wHQYDVR0OBBYEFAlgEOVj6Hl0La8sPRP388HEMiWvMA4GA1UdDwEB/wQEAwIF
oDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgB
hvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0
cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMwgaUGA1UdHwSBnTCBmjBMoEqgSIZGaHR0cDovL2Ny
bC5jb21vZG9jYS5jb20vVVROLVVTRVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWls
LmNybDBKoEigRoZEaHR0cDovL2NybC5jb21vZG8ubmV0L1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0
aGVudGljYXRpb25hbmRFbWFpbC5jcmwwbAYIKwYBBQUHAQEEYDBeMDYGCCsGAQUFBzAChipodHRw
Oi8vY3J0LmNvbW9kb2NhLmNvbS9VVE5BQUFDbGllbnRDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6
Ly9vY3NwLmNvbW9kb2NhLmNvbTAlBgNVHREEHjAcgRplYnVyZ2VyQHN0YW5kYXJkc3RyYWNrLmNv
bTANBgkqhkiG9w0BAQUFAAOCAQEACRTppSEc5DMYn8YXcbfX36iTaNBGw1gUvTNam0U8pXH0E7H3
2d4cTq6DEMu5ifEvxMGBqhUyv0sKxQ7+UvtDwrk7Kiy2L6TUC4zNEklZbtDqY7+Wd7EQZkN4k/zx
kMLlz2VIIRL/Cg48NrBKP5bo1la78NTJx8m4+VForLseEBabxMQoWB/GOVC7WpO/+RCgd93gz6H/
RzW1hnK0Uvu5H3Kz7HEC3R1Qk/sE9nXVzTfoJOMJRnyMS5Ut61mgoWSm/kUtczAlRRYh6IBOhzAl
awoXz+yk9hMCheYRAWx0EamBBpSzvqXj0N2vXYc62v3e3ddcLZncjiB0pYIfCE3s4DGCA/8wggP7
AgEBMIHEMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBD
aXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cu
dXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIEVtYWlsAhEAxcM7lN0zgrA71mfq+sG6xjAJBgUrDgMCGgUAoIICDzAYBgkqhkiG9w0B
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTAyMjUyMTAyMjJaMCMGCSqGSIb3DQEJ
BDEWBBSb/4/T3Gbi3nFd53timIWOqXd4yTCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBABcSWRZSewMt+saysMEln0P+uKpKZpe5NXnv5xGT2PLosy6X
LVz1xGx/JZ9mb4CiVGrk54HnkhmSbsz3OkpbI2QiPm1php7RjeY3E2zOeEDZhenhMlhNLDOeEbJE
D6TUspv2maIA1yDPR0r+X43M6n5GH/exAy9ixCeaNbMYLRSxmfPwvf8BzU3mWedH4rkgr0YSfR/+
9PCnlT7C18/onkw0Y1bbXborkhPczVh7+bafP8kZ2/Mfm16eM9W+YxZKd20HWm54O9JyOBz4CcCM
FEJROfpfcnwmCgD0kmkJzAV2wuD41EnclHBhy89gr/3YPGkoEKMFXTgXZPIQF5eN510AAAAAAAA=

--Apple-Mail-127-385478388--

From adam@nostrum.com  Fri Feb 25 14:25:30 2011
Return-Path: <adam@nostrum.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 258FE3A6A63 for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 14:25:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k3z90QvFJ7fW for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 14:25:29 -0800 (PST)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by core3.amsl.com (Postfix) with ESMTP id 39A963A6A5C for <wgchairs@ietf.org>; Fri, 25 Feb 2011 14:25:29 -0800 (PST)
Received: from dn3-228.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p1PMP63S075918 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 25 Feb 2011 16:25:06 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4D682C42.6090306@nostrum.com>
Date: Fri, 25 Feb 2011 16:25:06 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
Subject: Re: 80th IETF DRAFT Agenda
References: <20110225042952.4367F3A6904@core3.amsl.com>	<E3598C87-7001-40A2-B88F-DED9A776C2D4@nokia.com> <47A6A27E-6DCA-4661-80C0-BBAB79B5A589@standardstrack.com>
In-Reply-To: <47A6A27E-6DCA-4661-80C0-BBAB79B5A589@standardstrack.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 22:25:30 -0000

Thanks; I'm glad people are finding the agenda page improvements to be 
of use.

I've been working on the agenda page for the past couple of codesprints. 
I actually started doing some of the work to produce an .ics file in 
Beijing, but ran out of time. If things go well, I should be able to 
finish this task up during the Prague codesprint.

/a

On 2/25/11 3:00 PM, Eric Burger wrote:
> +1
> On Feb 25, 2011, at 2:14 AM, Lars Eggert wrote:
>
>> Hi,
>>
>> On 2011-2-25, at 6:29, IETF Agenda wrote:
>>> https://datatracker.ietf.org/meeting/80/agenda.html
>> is it possible to get an iCal subscription with the selections made on the URL above? (I like this interface better than the tools interface, but the tools one gives me the iCal calendar...)
>>
>> Thanks,
>> Lars
>>


From pkyzivat@cisco.com  Fri Feb 25 15:11:34 2011
Return-Path: <pkyzivat@cisco.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB55D3A6863 for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 15:11:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.578
X-Spam-Level: 
X-Spam-Status: No, score=-110.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yWxD4kdlGRnX for <wgchairs@core3.amsl.com>; Fri, 25 Feb 2011 15:11:32 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 7410B3A6A72 for <wgchairs@ietf.org>; Fri, 25 Feb 2011 15:11:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=840; q=dns/txt; s=iport; t=1298675546; x=1299885146; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=+baythy4QFwnUCCjO3aFr/HYcFkhur2i+VjcjxyshCo=; b=KLKW+KtY86lotcQCFQRk5GJodfYypwKqMNJSES/hc+LhSoYdvqYLaacx xm44/3/c59YhKx9EMfibOgAcIp+YmggSVjv23idk9RHH086AcMsAKDqy8 d3X/lyDm3IZd7UtWC7+6OxQ/tZxu6QsJwuVPxYd9BNcIGQhOz3re4OO6a Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AswGAIbGZ01AZnwM/2dsb2JhbACYLI4TdKEnm1CFYASFEIcNgz4
X-IronPort-AV: E=Sophos;i="4.62,228,1297036800"; d="scan'208";a="220529305"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 25 Feb 2011 23:12:25 +0000
Received: from [161.44.174.114] (dhcp-161-44-174-114.cisco.com [161.44.174.114]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p1PNCPca005008 for <wgchairs@ietf.org>; Fri, 25 Feb 2011 23:12:25 GMT
Message-ID: <4D683759.5050103@cisco.com>
Date: Fri, 25 Feb 2011 18:12:25 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: 80th IETF DRAFT Agenda
References: <20110225042952.4367F3A6904@core3.amsl.com> <FF9EABB4-1060-45CD-8667-EF2591068043@standardstrack.com>
In-Reply-To: <FF9EABB4-1060-45CD-8667-EF2591068043@standardstrack.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 23:11:34 -0000

On 2/25/2011 4:02 PM, Eric Burger wrote:
> Any chance to swap rtcweb (Tues. AM) with sipcore (Weds. AM)?

I don't know what all the constraints are, but I *personally* have no 
problem with that swap.

	Thanks,
	Paul

> On Feb 24, 2011, at 11:29 PM, IETF Agenda wrote:
>
>> The DRAFT agenda is ready for viewing.  Please note the cutoff date for
>> requests to reschedule Working Group and BOF meetings is February 28, 2011
>> 17:00 PT.  The final agenda will be published on March 4, 2011.
>>
>> https://datatracker.ietf.org/meeting/80/agenda.html
>> https://datatracker.ietf.org/meeting/80/agenda.txt
>>
>> http://www.ietf.org/meeting/80/index.html
>>
>>
>> Thanks,
>> Wanda
>>
>> Only 31 days until the Prague IETF!
>> Online registration for the IETF meeting is at:
>> http://www.ietf.org/meetings/80/
>

From keith.drage@alcatel-lucent.com  Sat Feb 26 07:56:50 2011
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 374553A687C for <wgchairs@core3.amsl.com>; Sat, 26 Feb 2011 07:56:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.319
X-Spam-Level: 
X-Spam-Status: No, score=-103.319 tagged_above=-999 required=5 tests=[AWL=-1.670, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q+m86RQxWvYu for <wgchairs@core3.amsl.com>; Sat, 26 Feb 2011 07:56:49 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id C32243A682C for <wgchairs@ietf.org>; Sat, 26 Feb 2011 07:56:47 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p1QFvVxa004607 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 26 Feb 2011 16:57:40 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Sat, 26 Feb 2011 16:57:37 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: David Harrington <ietfdbh@comcast.net>, "'Brian Haberman'" <brian@innovationslab.net>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Date: Sat, 26 Feb 2011 16:57:36 +0100
Subject: RE: How to add a draft to the "Related Documents" section of thedatatracker?
Thread-Topic: How to add a draft to the "Related Documents" section of thedatatracker?
Thread-Index: AcvU6skCfzjqIi3VRG+mJ10aUS21dwAG3U+QABQDADA=
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21E936C2E@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <D15B5D00-8A86-4B9F-BD36-17DAB9A99703@niven-jenkins.co.uk><C5F971F9-0158-4CA5-BBA2-64E404C845C0@magorcorp.com> <4D67A5DB.4010000@innovationslab.net> <1A5B6C1C10E64CE89794BB05847A7027@davidPC>
In-Reply-To: <1A5B6C1C10E64CE89794BB05847A7027@davidPC>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.84
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Feb 2011 15:56:50 -0000

In my view, the related documents section should be the list of documents w=
here respective author considers this is the WG to adopt the draft. As such=
 any such draft should only ever appear in one WGs related documents list.

And as such, there is an easy existing way for the author to control that h=
appening!

Regards

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org=20
> [mailto:wgchairs-bounces@ietf.org] On Behalf Of David Harrington
> Sent: 25 February 2011 16:21
> To: 'Brian Haberman'; wgchairs@ietf.org
> Subject: RE: How to add a draft to the "Related Documents"=20
> section of thedatatracker?
>=20
> Hi,
>=20
> That capability already exists by including the WG name in=20
> the filename.
>=20
> I do not think it would be good to add an option where the=20
> author gets to declare their draft is applicable to a whole=20
> bunch of WGs. This might encourage WG shopping, trying to=20
> find a WG that would take an interest in the draft.=20
> Currently, the author needs to decide in advance which WG is=20
> an appropriate venue for their proposal (which means they=20
> need to do some homework first). I would be concerned about=20
> (inadvertent or deliberate) abuse of this option by authors.
>=20
> It might make sense to me to allow WG chairs to add a draft=20
> as relevant, but how important is this? A WG can always look=20
> at individual drafts, and when the WG decides it really is=20
> relevant, they can adopt it as a WG draft.  IIRC, datatracker=20
> extensions for WG Chairs will have the ability to mark a=20
> draft as "being considered" by a WG.=20
>=20
> dbh
>=20
>=20
> > -----Original Message-----
> > From: wgchairs-bounces@ietf.org
> > [mailto:wgchairs-bounces@ietf.org] On Behalf Of Brian Haberman
> > Sent: Friday, February 25, 2011 7:52 AM
> > To: wgchairs@ietf.org
> > Subject: Re: How to add a draft to the "Related Documents"=20
> > section of thedatatracker?
> >=20
> > On 2/25/11 5:42 AM, Peter Musgrave wrote:
> > > Hi Ben,
> > >=20
> > > I did some work in that code on the last code sprint. As far as I=20
> > > remember the search is keying off the WG name.
> > >=20
> > > I can put in a ticket on this for the next sprint in March.
> > >=20
> > > I have also CCed Henrick. Perhaps he has better insight...
> >=20
> > Just thinking off of the top of my head, and with the=20
> caveat that it=20
> > is early in the morning... Would it make sense to have a=20
> mechanism in
> the
> > draft submission tool that allows an author to indicate WGs that
> their
> > draft may be related too?
> >=20
> > Brian
> >=20
> > >=20
> > > Regards,
> > >=20
> > > Peter Musgrave
> > >=20
> > > On 2011-02-25, at 3:45 AM, Ben Niven-Jenkins wrote:
> > >=20
> > >> Fellow WG chairs,
> > >>=20
> > >> In L3VPN the chairs have had a request by an author to add two=20
> > >> drafts to the "Related Documents" section of the WG's=20
> datatracker=20
> > >> page.
> > >>=20
> > >> One draft wasn't picked up automatically because the author
> hasn't
> > >> followed the normal naming convention and didn't include=20
> l3vpn in=20
> > >> the document filename (but the document is now on=20
> revision -04 so=20
> > >> renaming would be non-ideal).
> > >>=20
> > >> The other is owned by a different WG but does have applicability
> to
> > >> L3VPN.
> > >>=20
> > >> Does anyone know how (or if) I can add them to the list of
> related
> > >> documents?
> > >>=20
> > >> Thanks in advance Ben
> > >>=20
> >=20
> >=20
>=20
> =

From adam@nostrum.com  Sat Feb 26 15:38:09 2011
Return-Path: <adam@nostrum.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D25343A696D for <wgchairs@core3.amsl.com>; Sat, 26 Feb 2011 15:38:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.239
X-Spam-Level: 
X-Spam-Status: No, score=-102.239 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKShe63RnsSc for <wgchairs@core3.amsl.com>; Sat, 26 Feb 2011 15:38:09 -0800 (PST)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by core3.amsl.com (Postfix) with ESMTP id DA4E33A6960 for <wgchairs@ietf.org>; Sat, 26 Feb 2011 15:38:08 -0800 (PST)
Received: from hydra-3.local (99-152-144-32.lightspeed.dllstx.sbcglobal.net [99.152.144.32]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p1QNZjCV015582 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 26 Feb 2011 17:35:46 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4D698E50.5040802@nostrum.com>
Date: Sat, 26 Feb 2011 17:35:44 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Subject: Re: How to add a draft to the "Related Documents" section of	thedatatracker?
References: <D15B5D00-8A86-4B9F-BD36-17DAB9A99703@niven-jenkins.co.uk><C5F971F9-0158-4CA5-BBA2-64E404C845C0@magorcorp.com>	<4D67A5DB.4010000@innovationslab.net>	<1A5B6C1C10E64CE89794BB05847A7027@davidPC> <EDC0A1AE77C57744B664A310A0B23AE21E936C2E@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE21E936C2E@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 99.152.144.32 is authenticated by a trusted mechanism)
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Feb 2011 23:38:10 -0000

I'll admit that it was more the exception than the rule, but we did have 
a couple of documents go through -- RFCs 3486 and 5049 -- that were 
quite legitimately related equally to the SIP and ROHC working groups. 
If we were doing that kind of work presently, I would think it very much 
should appear in both lists.

It would be nice if the tools didn't get in the way of doing so.

/a

On 2/26/11 09:57, Feb 26, DRAGE, Keith (Keith) wrote:
> In my view, the related documents section should be the list of documents where respective author considers this is the WG to adopt the draft. As such any such draft should only ever appear in one WGs related documents list.
>
> And as such, there is an easy existing way for the author to control that happening!
>
> Regards
>
> Keith
>
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org
>> [mailto:wgchairs-bounces@ietf.org] On Behalf Of David Harrington
>> Sent: 25 February 2011 16:21
>> To: 'Brian Haberman'; wgchairs@ietf.org
>> Subject: RE: How to add a draft to the "Related Documents"
>> section of thedatatracker?
>>
>> Hi,
>>
>> That capability already exists by including the WG name in
>> the filename.
>>
>> I do not think it would be good to add an option where the
>> author gets to declare their draft is applicable to a whole
>> bunch of WGs. This might encourage WG shopping, trying to
>> find a WG that would take an interest in the draft.
>> Currently, the author needs to decide in advance which WG is
>> an appropriate venue for their proposal (which means they
>> need to do some homework first). I would be concerned about
>> (inadvertent or deliberate) abuse of this option by authors.
>>
>> It might make sense to me to allow WG chairs to add a draft
>> as relevant, but how important is this? A WG can always look
>> at individual drafts, and when the WG decides it really is
>> relevant, they can adopt it as a WG draft.  IIRC, datatracker
>> extensions for WG Chairs will have the ability to mark a
>> draft as "being considered" by a WG.
>>
>> dbh
>>
>>
>>> -----Original Message-----
>>> From: wgchairs-bounces@ietf.org
>>> [mailto:wgchairs-bounces@ietf.org] On Behalf Of Brian Haberman
>>> Sent: Friday, February 25, 2011 7:52 AM
>>> To: wgchairs@ietf.org
>>> Subject: Re: How to add a draft to the "Related Documents"
>>> section of thedatatracker?
>>>
>>> On 2/25/11 5:42 AM, Peter Musgrave wrote:
>>>> Hi Ben,
>>>>
>>>> I did some work in that code on the last code sprint. As far as I
>>>> remember the search is keying off the WG name.
>>>>
>>>> I can put in a ticket on this for the next sprint in March.
>>>>
>>>> I have also CCed Henrick. Perhaps he has better insight...
>>> Just thinking off of the top of my head, and with the
>> caveat that it
>>> is early in the morning... Would it make sense to have a
>> mechanism in
>> the
>>> draft submission tool that allows an author to indicate WGs that
>> their
>>> draft may be related too?
>>>
>>> Brian
>>>
>>>> Regards,
>>>>
>>>> Peter Musgrave
>>>>
>>>> On 2011-02-25, at 3:45 AM, Ben Niven-Jenkins wrote:
>>>>
>>>>> Fellow WG chairs,
>>>>>
>>>>> In L3VPN the chairs have had a request by an author to add two
>>>>> drafts to the "Related Documents" section of the WG's
>> datatracker
>>>>> page.
>>>>>
>>>>> One draft wasn't picked up automatically because the author
>> hasn't
>>>>> followed the normal naming convention and didn't include
>> l3vpn in
>>>>> the document filename (but the document is now on
>> revision -04 so
>>>>> renaming would be non-ideal).
>>>>>
>>>>> The other is owned by a different WG but does have applicability
>> to
>>>>> L3VPN.
>>>>>
>>>>> Does anyone know how (or if) I can add them to the list of
>> related
>>>>> documents?
>>>>>
>>>>> Thanks in advance Ben
>>>>>
>>>


From rbarnes@bbn.com  Sun Feb 27 09:16:19 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EAC03A6A19 for <wgchairs@core3.amsl.com>; Sun, 27 Feb 2011 09:16:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.538
X-Spam-Level: 
X-Spam-Status: No, score=-102.538 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LfoKW4s-pzKC for <wgchairs@core3.amsl.com>; Sun, 27 Feb 2011 09:16:18 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 5726F3A6A13 for <wgchairs@ietf.org>; Sun, 27 Feb 2011 09:16:18 -0800 (PST)
Received: from [128.89.253.231] (port=53526 helo=[192.168.0.198]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1PtkF2-0002D5-5B; Sun, 27 Feb 2011 12:17:08 -0500
Subject: Re: 80th IETF DRAFT Agenda 
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <FF9EABB4-1060-45CD-8667-EF2591068043@standardstrack.com>
Date: Sun, 27 Feb 2011 12:17:06 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1110AAB-B815-41CD-B4D1-BDBBFBC011D4@bbn.com>
References: <20110225042952.4367F3A6904@core3.amsl.com> <FF9EABB4-1060-45CD-8667-EF2591068043@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1082)
Cc: Working Group Chairs <wgchairs@ietf.org>, rai-ads@tools.ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Feb 2011 17:16:19 -0000

I would also be glad to swap GEOPRIV from Monday AM to Tuesday AM, to =
avoid conflict with APPAREA.  However, I would think that RTCWEB =
probably doesn't want to be against APPAREA either, so propose a =
three-part exchange:

GEOPRIV: Mon -> Tue
RTCWEB:  Tue -> Wed
SIPCORE: Wed -> Mon

--Richard


On Feb 25, 2011, at 4:02 PM, Eric Burger wrote:

> Any chance to swap rtcweb (Tues. AM) with sipcore (Weds. AM)?
>=20
> On Feb 24, 2011, at 11:29 PM, IETF Agenda wrote:
>=20
>> The DRAFT agenda is ready for viewing.  Please note the cutoff date =
for
>> requests to reschedule Working Group and BOF meetings is February 28, =
2011
>> 17:00 PT.  The final agenda will be published on March 4, 2011.
>>=20
>> https://datatracker.ietf.org/meeting/80/agenda.html
>> https://datatracker.ietf.org/meeting/80/agenda.txt
>>=20
>> http://www.ietf.org/meeting/80/index.html
>>=20
>>=20
>> Thanks,
>> Wanda
>>=20
>> Only 31 days until the Prague IETF!
>> Online registration for the IETF meeting is at:
>> http://www.ietf.org/meetings/80/
>=20


From barryleiba.mailing.lists@gmail.com  Sun Feb 27 10:36:12 2011
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F8813A6A00 for <wgchairs@core3.amsl.com>; Sun, 27 Feb 2011 10:36:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.897
X-Spam-Level: 
X-Spam-Status: No, score=-102.897 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7JhwtoFXZwou for <wgchairs@core3.amsl.com>; Sun, 27 Feb 2011 10:36:11 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 384DC3A67A5 for <wgchairs@ietf.org>; Sun, 27 Feb 2011 10:36:11 -0800 (PST)
Received: by iyj8 with SMTP id 8so2590458iyj.31 for <wgchairs@ietf.org>; Sun, 27 Feb 2011 10:37:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=8avie09NCvIOaXjFQEJApYEJWOSrUxRsG+MJgZ6XsZ8=; b=KOhW6amNyZnn3u723nvSYYkc5NvyzqRBXjEeK38eNMn4X3zidrueCgjs2ks/AuzUfF brzWgclSqJ0C6plm9YpqOTq14ORM129uBydgi/ZIkCgxpjVDljXcXqUutMOGMtjnCYHn 7e93g1LnfjqZSqrI04IuqqQ4DPXatp8A+xoyI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=NeZnlmCkuLq4aT0zftzcP+Ah5gzfyViYW650DG7ZYp7IghP5y3A3R/sA0IpI6cAmvd SLDo/zs2B5y6Pgu7nyebBjbl9DLsjGFy5HTfLkxU9YBJyG/l79LFpyNbTgturFnAIghg uqwifrjmGGfH4hN0ZG1vCXVgS3D/iket8iBTg=
MIME-Version: 1.0
Received: by 10.42.158.196 with SMTP id i4mr3856477icx.116.1298831828710; Sun, 27 Feb 2011 10:37:08 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.229.67 with HTTP; Sun, 27 Feb 2011 10:37:08 -0800 (PST)
In-Reply-To: <4D698E50.5040802@nostrum.com>
References: <D15B5D00-8A86-4B9F-BD36-17DAB9A99703@niven-jenkins.co.uk> <C5F971F9-0158-4CA5-BBA2-64E404C845C0@magorcorp.com> <4D67A5DB.4010000@innovationslab.net> <1A5B6C1C10E64CE89794BB05847A7027@davidPC> <EDC0A1AE77C57744B664A310A0B23AE21E936C2E@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4D698E50.5040802@nostrum.com>
Date: Sun, 27 Feb 2011 13:37:08 -0500
X-Google-Sender-Auth: hDfEcXNAoskvDXUD-tvvUp_F6j4
Message-ID: <AANLkTi=o11_Xq+GFDLF+X11jbz_iyiR+1nosN7Z8=fP4@mail.gmail.com>
Subject: Re: How to add a draft to the "Related Documents" section of thedatatracker?
From: Barry Leiba <barryleiba@computer.org>
To: Working Group Chairs <wgchairs@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Feb 2011 18:36:12 -0000

> couple of documents go through -- RFCs 3486 and 5049 -- that were quite
> legitimately related equally to the SIP and ROHC working groups. If we were
> doing that kind of work presently, I would think it very much should appear
> in both lists.
>
> It would be nice if the tools didn't get in the way of doing so.

Agreed.  I would very much like a way for the chairs (not the authors)
to mark a document as "related".  I'd similarly like a way for the
chairs to *unmark* a document, even if the author has put the WG name
in the filename.

Barry

From cabo@tzi.org  Sun Feb 27 11:23:34 2011
Return-Path: <cabo@tzi.org>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE8553A6A22 for <wgchairs@core3.amsl.com>; Sun, 27 Feb 2011 11:23:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hC13RKAiy+7s for <wgchairs@core3.amsl.com>; Sun, 27 Feb 2011 11:23:34 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by core3.amsl.com (Postfix) with ESMTP id B1A9C3A6A00 for <wgchairs@ietf.org>; Sun, 27 Feb 2011 11:23:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id p1RJOKH4008186; Sun, 27 Feb 2011 20:24:21 +0100 (CET)
Received: from [192.168.217.101] (p5489A685.dip.t-dialin.net [84.137.166.133]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 72DAD866; Sun, 27 Feb 2011 20:24:20 +0100 (CET)
Subject: Re: How to add a draft to the "Related Documents" section of thedatatracker?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <AANLkTi=o11_Xq+GFDLF+X11jbz_iyiR+1nosN7Z8=fP4@mail.gmail.com>
Date: Sun, 27 Feb 2011 20:25:25 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <11067574-1B9A-4992-B568-B3EA517DB62B@tzi.org>
References: <D15B5D00-8A86-4B9F-BD36-17DAB9A99703@niven-jenkins.co.uk> <C5F971F9-0158-4CA5-BBA2-64E404C845C0@magorcorp.com> <4D67A5DB.4010000@innovationslab.net> <1A5B6C1C10E64CE89794BB05847A7027@davidPC> <EDC0A1AE77C57744B664A310A0B23AE21E936C2E@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4D698E50.5040802@nostrum.com> <AANLkTi=o11_Xq+GFDLF+X11jbz_iyiR+1nosN7Z8=fP4@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1082)
Cc: Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Feb 2011 19:23:34 -0000

On Feb 27, 2011, at 19:37, Barry Leiba wrote:

> Agreed.  I would very much like a way for the chairs (not the authors)
> to mark a document as "related".  I'd similarly like a way for the
> chairs to *unmark* a document, even if the author has put the WG name
> in the filename.

+1

Now if we had a way to mark a non-WG document as replaced-by a WG =
document (this is often not a 1:1 relationship) without going through =
the secretariat...

Gruesse, Carsten


From keith.drage@alcatel-lucent.com  Sun Feb 27 16:37:46 2011
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DADE3A6A57 for <wgchairs@core3.amsl.com>; Sun, 27 Feb 2011 16:37:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.167
X-Spam-Level: 
X-Spam-Status: No, score=-105.167 tagged_above=-999 required=5 tests=[AWL=0.482, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KFzc8e2Hb+W7 for <wgchairs@core3.amsl.com>; Sun, 27 Feb 2011 16:37:45 -0800 (PST)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 5536B3A6A3B for <wgchairs@ietf.org>; Sun, 27 Feb 2011 16:37:43 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p1S0cd45011852 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 28 Feb 2011 01:38:40 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Mon, 28 Feb 2011 01:38:39 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Adam Roach <adam@nostrum.com>
Date: Mon, 28 Feb 2011 01:38:38 +0100
Subject: RE: How to add a draft to the "Related Documents" section of thedatatracker?
Thread-Topic: How to add a draft to the "Related Documents" section of thedatatracker?
Thread-Index: AcvWDeqRXkSYueyeQMKuQPBWxbFvuAAmaymQ
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21E936E47@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <D15B5D00-8A86-4B9F-BD36-17DAB9A99703@niven-jenkins.co.uk><C5F971F9-0158-4CA5-BBA2-64E404C845C0@magorcorp.com> <4D67A5DB.4010000@innovationslab.net> <1A5B6C1C10E64CE89794BB05847A7027@davidPC> <EDC0A1AE77C57744B664A310A0B23AE21E936C2E@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <4D698E50.5040802@nostrum.com>
In-Reply-To: <4D698E50.5040802@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.13
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 00:37:46 -0000

I believe by the time we reached that stage, it was already a WG item in on=
e group with some relation in the other.=20

There is possibly more call for a separate section that is WG items of anot=
her group that are of direct interest to this group.

Regards

Keith=20

> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]=20
> Sent: 26 February 2011 23:36
> To: DRAGE, Keith (Keith)
> Cc: David Harrington; 'Brian Haberman'; wgchairs@ietf.org
> Subject: Re: How to add a draft to the "Related Documents"=20
> section of thedatatracker?
>=20
> I'll admit that it was more the exception than the rule, but=20
> we did have a couple of documents go through -- RFCs 3486 and=20
> 5049 -- that were quite legitimately related equally to the=20
> SIP and ROHC working groups.=20
> If we were doing that kind of work presently, I would think=20
> it very much should appear in both lists.
>=20
> It would be nice if the tools didn't get in the way of doing so.
>=20
> /a
>=20
> On 2/26/11 09:57, Feb 26, DRAGE, Keith (Keith) wrote:
> > In my view, the related documents section should be the=20
> list of documents where respective author considers this is=20
> the WG to adopt the draft. As such any such draft should only=20
> ever appear in one WGs related documents list.
> >
> > And as such, there is an easy existing way for the author=20
> to control that happening!
> >
> > Regards
> >
> > Keith
> >
> >> -----Original Message-----
> >> From: wgchairs-bounces@ietf.org
> >> [mailto:wgchairs-bounces@ietf.org] On Behalf Of David Harrington
> >> Sent: 25 February 2011 16:21
> >> To: 'Brian Haberman'; wgchairs@ietf.org
> >> Subject: RE: How to add a draft to the "Related Documents"
> >> section of thedatatracker?
> >>
> >> Hi,
> >>
> >> That capability already exists by including the WG name in the=20
> >> filename.
> >>
> >> I do not think it would be good to add an option where the author=20
> >> gets to declare their draft is applicable to a whole bunch of WGs.=20
> >> This might encourage WG shopping, trying to find a WG that=20
> would take=20
> >> an interest in the draft.
> >> Currently, the author needs to decide in advance which WG is an=20
> >> appropriate venue for their proposal (which means they need to do=20
> >> some homework first). I would be concerned about (inadvertent or=20
> >> deliberate) abuse of this option by authors.
> >>
> >> It might make sense to me to allow WG chairs to add a draft as=20
> >> relevant, but how important is this? A WG can always look at=20
> >> individual drafts, and when the WG decides it really is relevant,=20
> >> they can adopt it as a WG draft.  IIRC, datatracker=20
> extensions for WG=20
> >> Chairs will have the ability to mark a draft as "being=20
> considered" by=20
> >> a WG.
> >>
> >> dbh
> >>
> >>
> >>> -----Original Message-----
> >>> From: wgchairs-bounces@ietf.org
> >>> [mailto:wgchairs-bounces@ietf.org] On Behalf Of Brian Haberman
> >>> Sent: Friday, February 25, 2011 7:52 AM
> >>> To: wgchairs@ietf.org
> >>> Subject: Re: How to add a draft to the "Related Documents"
> >>> section of thedatatracker?
> >>>
> >>> On 2/25/11 5:42 AM, Peter Musgrave wrote:
> >>>> Hi Ben,
> >>>>
> >>>> I did some work in that code on the last code sprint. As=20
> far as I=20
> >>>> remember the search is keying off the WG name.
> >>>>
> >>>> I can put in a ticket on this for the next sprint in March.
> >>>>
> >>>> I have also CCed Henrick. Perhaps he has better insight...
> >>> Just thinking off of the top of my head, and with the
> >> caveat that it
> >>> is early in the morning... Would it make sense to have a
> >> mechanism in
> >> the
> >>> draft submission tool that allows an author to indicate WGs that
> >> their
> >>> draft may be related too?
> >>>
> >>> Brian
> >>>
> >>>> Regards,
> >>>>
> >>>> Peter Musgrave
> >>>>
> >>>> On 2011-02-25, at 3:45 AM, Ben Niven-Jenkins wrote:
> >>>>
> >>>>> Fellow WG chairs,
> >>>>>
> >>>>> In L3VPN the chairs have had a request by an author to add two=20
> >>>>> drafts to the "Related Documents" section of the WG's
> >> datatracker
> >>>>> page.
> >>>>>
> >>>>> One draft wasn't picked up automatically because the author
> >> hasn't
> >>>>> followed the normal naming convention and didn't include
> >> l3vpn in
> >>>>> the document filename (but the document is now on
> >> revision -04 so
> >>>>> renaming would be non-ideal).
> >>>>>
> >>>>> The other is owned by a different WG but does have applicability
> >> to
> >>>>> L3VPN.
> >>>>>
> >>>>> Does anyone know how (or if) I can add them to the list of
> >> related
> >>>>> documents?
> >>>>>
> >>>>> Thanks in advance Ben
> >>>>>
> >>>
>=20
> =

From rjsparks@nostrum.com  Mon Feb 28 08:41:19 2011
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE48A3A6BE1 for <wgchairs@core3.amsl.com>; Mon, 28 Feb 2011 08:41:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.536
X-Spam-Level: 
X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0sj+sNNEkdFs for <wgchairs@core3.amsl.com>; Mon, 28 Feb 2011 08:41:18 -0800 (PST)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by core3.amsl.com (Postfix) with ESMTP id C4C5B3A687C for <wgchairs@ietf.org>; Mon, 28 Feb 2011 08:41:18 -0800 (PST)
Received: from dn3-177.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p1SGf0Da037389 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 28 Feb 2011 10:41:01 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Subject: Re: 80th IETF DRAFT Agenda 
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <A1110AAB-B815-41CD-B4D1-BDBBFBC011D4@bbn.com>
Date: Mon, 28 Feb 2011 10:40:59 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B63602B-5E91-42A9-8B3B-63C386711913@nostrum.com>
References: <20110225042952.4367F3A6904@core3.amsl.com> <FF9EABB4-1060-45CD-8667-EF2591068043@standardstrack.com> <A1110AAB-B815-41CD-B4D1-BDBBFBC011D4@bbn.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>
X-Mailer: Apple Mail (2.1082)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: Working Group Chairs <wgchairs@ietf.org>, rai-ads@tools.ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 16:41:19 -0000

Both Monday and Wednesday have area meetings (APPs on Monday, TSV on =
Wed).
We are trying to keep BoFs and area meetings from conflicting.

RjS

On Feb 27, 2011, at 11:17 AM, Richard L. Barnes wrote:

> I would also be glad to swap GEOPRIV from Monday AM to Tuesday AM, to =
avoid conflict with APPAREA.  However, I would think that RTCWEB =
probably doesn't want to be against APPAREA either, so propose a =
three-part exchange:
>=20
> GEOPRIV: Mon -> Tue
> RTCWEB:  Tue -> Wed
> SIPCORE: Wed -> Mon
>=20
> --Richard
>=20
>=20
> On Feb 25, 2011, at 4:02 PM, Eric Burger wrote:
>=20
>> Any chance to swap rtcweb (Tues. AM) with sipcore (Weds. AM)?
>>=20
>> On Feb 24, 2011, at 11:29 PM, IETF Agenda wrote:
>>=20
>>> The DRAFT agenda is ready for viewing.  Please note the cutoff date =
for
>>> requests to reschedule Working Group and BOF meetings is February =
28, 2011
>>> 17:00 PT.  The final agenda will be published on March 4, 2011.
>>>=20
>>> https://datatracker.ietf.org/meeting/80/agenda.html
>>> https://datatracker.ietf.org/meeting/80/agenda.txt
>>>=20
>>> http://www.ietf.org/meeting/80/index.html
>>>=20
>>>=20
>>> Thanks,
>>> Wanda
>>>=20
>>> Only 31 days until the Prague IETF!
>>> Online registration for the IETF meeting is at:
>>> http://www.ietf.org/meetings/80/
>>=20
>=20


From wwwrun@core3.amsl.com  Mon Feb 28 08:49:55 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id DA2C73A6C1D; Mon, 28 Feb 2011 08:49:55 -0800 (PST)
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 80th IETF - Working Group/BOF Re-Scheduling REMINDER - Closes  today at 5PM PT 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110228164955.DA2C73A6C1D@core3.amsl.com>
Date: Mon, 28 Feb 2011 08:49:55 -0800 (PST)
Cc: irsg@isi.edu
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 16:49:56 -0000

-----------------------------------------------------------------
80th IETF Prague, Czech Republic
Meeting Dates: March 27-April 1, 2011
Host: CZ.NIC
-----------------------------------------------------------------
IETF meetings start Monday morning and run through Friday mid-afternoon
(15:15).

We are accepting scheduling requests for all Working Groups and BOFs
starting today.  The milestones and deadlines for scheduling-related
activities are as follows:

NOTE: cutoff dates are subject to change.

*2011-02-28 (Monday): Cutoff date for requests to reschedule Working
Group and BOF meetings 17:00 PT (01:00 Tuesday, March 1 UTC). 
*2011-02-28 (Monday): Working Group Chair approval for initial document
(Version -00) submissions appreciated by 17:00 PT (01:00 Tuesday, March 1
UTC). 
*2011-03-04 (Friday): Final agenda to be published. 
*2011-03-16 (Wednesday): Draft Working Group agendas due by 17:00 PT
(01:00 Thursday, March 17 UTC), upload using IETF Meeting Materials
Management Tool. 
*2011-03-21 (Monday): Revised Working Group agendas due by 17:00 PT
(01:00 Tuesday, March 22 UTC), upload using IETF Meeting Materials
Management Tool.

Submitting Requests for Working Group and BOF Sessions

Please submit requests to schedule your Working Group sessions using the
"IETF Meeting Session Request Tool," a Web-based tool for submitting all
of the information that the Secretariat requires to schedule your
sessions.

The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

Please send requests to schedule your BOF sessions to agenda@ietf.org. 
Please include the acronym of your BOF in the subject line of the message,
and include all of the information specified in item (4) of "Requesting
Meeting Sessions at IETF Meetings" in the body.  (This document is
included below.)

Submitting Session Agendas

For the convenience of meeting attendees, we ask that you submit the
agendas for your Working Group sessions as early as possible.  Draft
Working Group agendas are due Wednesday, March 16, 2011 by 17:00 PT (01:00
Thursday, March 17 UTC).  Revised Working Group agendas are due no later
than Monday, March 21, 2011 at 17:00 PT (01:00 Tuesday, March 22 UTC). 
The proposed agenda for a BOF session should be submitted along with your
request for a session.  Please be sure to copy your Area Director on that
message.

Please submit the agendas for your Working Group sessions using the "IETF
Meeting Materials Management Tool," a Web-based tool for making your
meeting agenda, minutes, and presentation slides available to the
community before, during, and after an IETF meeting.  If you are a BOF
chair, then you may use the tool to submit a revised agenda as well as
other materials for your BOF once the BOF has been approved.

The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi

Additional information about this tool is available at:

http://www.ietf.org/instructions/meeting_materials_tool.html

Agendas submitted via the tool will be available to the public on the
"IETF Meeting Materials" Web page as soon as they are submitted.

The URL for the "IETF 80 Meeting Materials" Web page is:

https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=80

If you are a Working Group chair, then you already have accounts on the
"IETF Meeting Session Request Tool" and the "IETF Meeting Materials
Management Tool."  The same User ID and password will work for both tools.



If you are a BOF chair who is not also a Working Group chair, then you
will be given an account on the "IETF Meeting Materials Management Tool"
when your BOF has been approved.  If you require assistance in using
either tool, or wish to report a bug, then please send a message to:
ietf-action@ietf.org.
===============================================================
For your convenience, comprehensive information on requesting meeting
sessions at IETF 80 is presented below:

1. Requests to schedule Working Group sessions should be submitted using
the "IETF Meeting Session Request Tool," a Web-based tool for submitting
all of the information required by the Secretariat to schedule your
sessions.  The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

If you require an account on this tool, or assistance in using it, then
please send a message to ietf-action@ietf.org.  If you are unable to use
the tool, then you may send your request via e-mail to agenda@ietf.org,
with a copy to the appropriate Area Director(s).

Requests to schedule BOF sessions must be sent to agenda@ietf.org with a
copy to the appropriate Area Director(s).

When submitting a Working Group or BOF session request by e-mail, please
include the Working Group or BOF acronym in the Subject line.

2. BOFs will NOT be scheduled unless the Area Director(s) approved
request is accompanied by a BOF'S FULL NAME AND ACRONYM, AREA, CHAIR(S)
NAME(S) (given together with e-mail address(es)), AN AGENDA AND FULL
DESCRIPTION, and the information requested in (4) below. (Please read the
BOF Procedure at: http://www.ietf.org/ietf/1bof-procedures.txt before
requesting a session for a BOF.)

3. A Working Group may request either one or two sessions.  If your
Working Group requires more than two sessions, then your request must be
approved by an Area Director.  Additional sessions will be assigned, based
on availability, after Monday, February 28, 2011 at 17:00 PT (01:00
Tuesday, March 1 UTC), the cut-off date for requests to reschedule a
session.

4. You MUST provide the following information before a Working Group or
BOF session will be scheduled:

 a. Working Group or BOF full name with acronym in brackets: 

 b. AREA under which Working Group or BOF appears:

 c. CONFLICTS you wish to avoid, please be as specific as possible:

 d. Expected Attendance:

 e. Special requests:

 f. Number of sessions:

 g. Length of session: 
    - 1 hour 
    - 1 1/2 hours
    - 2 hours 
    - 2 1/2 hours

For more information on scheduling Working Group and BOF sessions, please
refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and Procedures"
(http://www.ietf.org/rfc/rfc2418.txt).
===============================================================
For your convenience please find here a list of the IETF Area Directors
with their e-mail addresses:

IETF Chair 
Russ Housley <housley@vigilsec.com>

Applications Area (app)
Alexey Melnikov <alexey.melnikov@isode.com>
Peter Saint-Andre <stpeter@stpeter.im> 

Internet Area (int) 
Jari Arkko <jari.arkko@piuha.net>
Ralph Droms <rdroms.ietf@gmail.com> 

Operations & Management Area (ops) 
Ronald Bonica <rbonica@juniper.net>
Dan Romascanu <dromasca@avaya.com>

Real-time Applications and Infrastructure Area (rai)
Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Robert Sparks <rjsparks@nostrum.com> 

Routing Area (rtg) 
Stewart Bryant <stbryant@cisco.com>
Adrian Farrel <adrian.farrel@huawei.com> 

Security Area (sec) 
Tim Polk <tim.polk@nist.gov>
Sean Turner <turners@ieca.com> 

Transport Area (tsv) 
Lars Eggert <lars.eggert@nokia.com>
David Harrington <ietfdbh@comcast.net> 
===========================================================
79th IETF Meeting Attendance Number

Working Group	

6lowpan - 108
6man - 178
abfab - 50
alto - 110
ancp - 26
apparea (AG) - 74
armd BOF - 70
atoca - 37
autoconf - 29
avt - 82
avt (2nd session) - 55
behave - 103
bmwg - 15
ccamp - 100
ccamp (2nd session) - 79
codec - 59
conex - 43
core - 81
core (2nd session) - 67
cuss - 14
decade - 59
dhc - 28
dime - 14
dispatch - 61
dnsext - 99
dnsop - 96
drinks - 37
dtnrg (RG) - 22
eai - 31
ecrit - 37
eman - 56
emu - 21
fecframe - 8
forces - 23
geopriv - 39
grow - 44
hiprg (RG) - 44
hokey - 22
iddtspec - 13
idr - 80
intarea (AG) - 111
ipfix - 37
ippm - 23
ipsecme - 28
iri - 18
isis - 52
isms - 14
karp - 50
kidns - 122
kitten - 31
krb-wg - 12
l2vpn - 119
l3vpn - 92
lisp - 69
lwip - 156
manet - 35
martini - 36
mboned - 18
mext - 69
mext (second session) - 64
mif - 114
mip4 - 10
mmusic - 50
mpls - 150
mpls (2nd session) - 158
mptcp - 101
mptcp (2nd session) - 64
msec - 33
multimob - 61
nbs BPF - 101
nea - 30
netconf - 42
netext - 52
netmod - 28
nfsv4 - 25
nfsv4 (second session) - NO SHEETS
opsarea (AG) - 40
opsawg - 51
ospf - 53
p2psip - 58
pcp - 59
pim - 47
pkix - 30
ppsp - 38
precis - 31
pwe3 - 140
radext - 20
roll - 72
rtgarea (AG) - 135
rtgwg - 56
saag (AG) - 90
samrg (RG) - 20
savi - 67
scap BOF - 44
sidr - 68
sipclf - 19
sipcore - 57
siprec - 44
softwire - 110
tcpm - 25
tictoc - 17
trill - 72
tsvarea (AG) - 33
tsvwg - 65
v6ops - 203
v6ops (second session) - 159
vcarddav - 13
vnrg (RG) - 48
websec - 101


From wwwrun@core3.amsl.com  Mon Feb 28 11:06:44 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: wgchairs@ietf.org
Delivered-To: wgchairs@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id C4F473A6C51; Mon, 28 Feb 2011 11:06:44 -0800 (PST)
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 80th IETF - Working Group Chairs Training 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110228190644.C4F473A6C51@core3.amsl.com>
Date: Mon, 28 Feb 2011 11:06:44 -0800 (PST)
Cc: irsg@isi.edu
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 19:06:44 -0000

During the Wednesday lunch slot (11:30am - 1:00pm) at IETF 80th in Prague,
we will be holding a WG chairs training session on Datatracker
Enhancements.  Please come to share your ideas on this important topic. 
This session is open to all current WG chairs, BOF chairs, IESG members,
IAB members, and WG Secretaries.  We will include a complementary lunch.

Datatracker Enhancements (Donald Eastlake and Glen Zorn):

Some enhancements of the Datatracker that will support WG chairs have
been implemented. It is expected that they will be operational before the
IETF meeting in Prague. Some WG Chairs have been testing the software, and
will share their experience.

If you would like to attend this session, please RSVP to agenda@ietf.org
by Thursday, March 24, 2011. The location will be sent to those who RSVP.


Thanks,
Wanda

From tlyu@mit.edu  Mon Feb 28 12:46:09 2011
Return-Path: <tlyu@mit.edu>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5DB8B3A6C9A; Mon, 28 Feb 2011 12:46:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.299
X-Spam-Level: 
X-Spam-Status: No, score=-101.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2DwtrvXm3Sfh; Mon, 28 Feb 2011 12:46:08 -0800 (PST)
Received: from dmz-mailsec-scanner-3.mit.edu (DMZ-MAILSEC-SCANNER-3.MIT.EDU [18.9.25.14]) by core3.amsl.com (Postfix) with ESMTP id 5F6BE3A6A14; Mon, 28 Feb 2011 12:46:08 -0800 (PST)
X-AuditID: 1209190e-b7b3bae000000a71-ed-4d6c09cd95dc
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-3.mit.edu (Symantec Brightmail Gateway) with SMTP id 99.D9.02673.DC90C6D4; Mon, 28 Feb 2011 15:47:09 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id p1SKl8Le003813;  Mon, 28 Feb 2011 15:47:08 -0500
Received: from cathode-dark-space.mit.edu (CATHODE-DARK-SPACE.MIT.EDU [18.18.1.96]) (authenticated bits=56) (User authenticated as tlyu@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p1SKl41T005363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Feb 2011 15:47:05 -0500 (EST)
Received: (from tlyu@localhost) by cathode-dark-space.mit.edu (8.12.9.20060308) id p1SKl4ET006376; Mon, 28 Feb 2011 15:47:04 -0500 (EST)
To: IETF Agenda <agenda@ietf.org>
Subject: Re: 80th IETF DRAFT Agenda
References: <20110225042952.4367F3A6904@core3.amsl.com>
From: Tom Yu <tlyu@MIT.EDU>
Date: Mon, 28 Feb 2011 15:47:04 -0500
In-Reply-To: <20110225042952.4367F3A6904@core3.amsl.com> (IETF Agenda's message of "Thu, 24 Feb 2011 20:29:52 -0800 (PST)")
Message-ID: <ldvy64z6g53.fsf@cathode-dark-space.mit.edu>
Lines: 6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Brightmail-Tracker: AAAAAReAgK8=
Cc: Working Group Chairs <wgchairs@ietf.org>, abfab-chairs@tools.ietf.org, kitten-chairs@tools.ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 20:46:09 -0000

abfab (2nd session) Fri 13:00-14:00 conflicts with kitten (1st session)

I don't have a suggested schedule swap yet, but these two groups
have a lot of participant overlap.  Any ideas?

Thanks.

From leifj@sunet.se  Mon Feb 28 14:04:48 2011
Return-Path: <leifj@sunet.se>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C76D3A6BEC for <wgchairs@core3.amsl.com>; Mon, 28 Feb 2011 14:04:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FlJqeJmef1HA for <wgchairs@core3.amsl.com>; Mon, 28 Feb 2011 14:04:47 -0800 (PST)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by core3.amsl.com (Postfix) with ESMTP id A14563A6CB2 for <wgchairs@ietf.org>; Mon, 28 Feb 2011 14:04:46 -0800 (PST)
Received: from [10.0.0.11] (ua-83-227-179-169.cust.bredbandsbolaget.se [83.227.179.169]) (authenticated bits=0) by backup-server.nordu.net (8.14.3/8.14.3) with ESMTP id p1SM5hEv028642 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Mon, 28 Feb 2011 23:05:47 +0100 (CET)
Message-ID: <4D6C1C37.1050508@sunet.se>
Date: Mon, 28 Feb 2011 23:05:43 +0100
From: Leif Johansson <leifj@sunet.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: 80th IETF DRAFT Agenda
References: <20110225042952.4367F3A6904@core3.amsl.com> <ldvy64z6g53.fsf@cathode-dark-space.mit.edu>
In-Reply-To: <ldvy64z6g53.fsf@cathode-dark-space.mit.edu>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 22:04:48 -0000

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

On 02/28/2011 09:47 PM, Tom Yu wrote:
> abfab (2nd session) Fri 13:00-14:00 conflicts with kitten (1st session)
> 
> I don't have a suggested schedule swap yet, but these two groups
> have a lot of participant overlap.  Any ideas?
> 
> Thanks.

I've notified the secretariat about that. How about moving oauth
to the iccrg-slot on tuesday and then moving the abfab session
to the oauth friday slot?

	Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1sHDcACgkQ8Jx8FtbMZndvPgCgreGQy4IHYAUXh8YRR/B9omzF
3jwAnjsPd81Xc62AvCZfrsyLgw8KX9xq
=9/rs
-----END PGP SIGNATURE-----

From stpeter@stpeter.im  Mon Feb 28 14:30:32 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D36E23A6CB9 for <wgchairs@core3.amsl.com>; Mon, 28 Feb 2011 14:30:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.629
X-Spam-Level: 
X-Spam-Status: No, score=-102.629 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5YyyCDaqCSzN for <wgchairs@core3.amsl.com>; Mon, 28 Feb 2011 14:30:31 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id C7EBE3A6CBD for <wgchairs@ietf.org>; Mon, 28 Feb 2011 14:30:31 -0800 (PST)
Received: from dhcp-64-101-72-185.cisco.com (dhcp-64-101-72-185.cisco.com [64.101.72.185]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 37FF7400F6; Mon, 28 Feb 2011 15:50:46 -0700 (MST)
Message-ID: <4D6C2242.9080005@stpeter.im>
Date: Mon, 28 Feb 2011 15:31:30 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Leif Johansson <leifj@sunet.se>
Subject: Re: 80th IETF DRAFT Agenda
References: <20110225042952.4367F3A6904@core3.amsl.com>	<ldvy64z6g53.fsf@cathode-dark-space.mit.edu> <4D6C1C37.1050508@sunet.se>
In-Reply-To: <4D6C1C37.1050508@sunet.se>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030107010502060709020203"
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 22:30:32 -0000

This is a cryptographically signed message in MIME format.

--------------ms030107010502060709020203
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 2/28/11 3:05 PM, Leif Johansson wrote:
> On 02/28/2011 09:47 PM, Tom Yu wrote:
>> abfab (2nd session) Fri 13:00-14:00 conflicts with kitten (1st session=
)
>=20
>> I don't have a suggested schedule swap yet, but these two groups
>> have a lot of participant overlap.  Any ideas?
>>=20
>> Thanks.
>=20
> I've notified the secretariat about that.=20

Thanks, that is a bad conflict.

> How about moving oauth
> to the iccrg-slot on tuesday and then moving the abfab session
> to the oauth friday slot?

Perhaps Hannes might have a concern, but other than that I don't see any
big problems with the swap you propose.

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDIy
ODIyMzEzMFowIwYJKoZIhvcNAQkEMRYEFA6/ko1SMlDvM04aGnh0PRU6VwYOMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQC0S850ULj+L5E4kTSTZ/xlpUbDPT/T1T3QB0GuOmLVRtT/xJSpzszr+T4P
xVI+jIr0LDuMUEjSYFrx/3s/T3Z/EOJ+zgvyeOvjJ23XzzXq1aTpt6QcmVDRVbdxKf86zQGx
vBg9GmhZPAtsiuHntkP2iCwJ9rZMIwyGf9KGVdHA8hEnM087qyQqczZG3Qxq0hthcHlA9bvt
UBMjeWBcmNVlESuHkX7cGvKo06V0gQ8Av7Zjx2rao1WqeRq4EHwolLhgocJtAE8s/iw67rzP
eLdSToGVkfJVs8L/kUS/bgYUCOsUvDK/HQn5XI3q6h4Haufij5ylLo6fGSNwW4GLQgW8AAAA
AAAA
--------------ms030107010502060709020203--

From leifj@sunet.se  Mon Feb 28 16:00:19 2011
Return-Path: <leifj@sunet.se>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79BCA3A6CF0 for <wgchairs@core3.amsl.com>; Mon, 28 Feb 2011 16:00:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9J3qqUfHfEkP for <wgchairs@core3.amsl.com>; Mon, 28 Feb 2011 16:00:18 -0800 (PST)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by core3.amsl.com (Postfix) with ESMTP id 76C973A6CEA for <wgchairs@ietf.org>; Mon, 28 Feb 2011 16:00:18 -0800 (PST)
Received: from [10.0.0.11] (ua-83-227-179-169.cust.bredbandsbolaget.se [83.227.179.169]) (authenticated bits=0) by backup-server.nordu.net (8.14.3/8.14.3) with ESMTP id p2101GXi014179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Mar 2011 01:01:18 +0100 (CET)
Message-ID: <4D6C374B.2020502@sunet.se>
Date: Tue, 01 Mar 2011 01:01:15 +0100
From: Leif Johansson <leifj@sunet.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: 80th IETF DRAFT Agenda
References: <20110225042952.4367F3A6904@core3.amsl.com>	<ldvy64z6g53.fsf@cathode-dark-space.mit.edu> <4D6C1C37.1050508@sunet.se> <4D6C2242.9080005@stpeter.im>
In-Reply-To: <4D6C2242.9080005@stpeter.im>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 00:00:19 -0000

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

On 02/28/2011 11:31 PM, Peter Saint-Andre wrote:
> On 2/28/11 3:05 PM, Leif Johansson wrote:
>> On 02/28/2011 09:47 PM, Tom Yu wrote:
>>> abfab (2nd session) Fri 13:00-14:00 conflicts with kitten (1st session)
>>
>>> I don't have a suggested schedule swap yet, but these two groups
>>> have a lot of participant overlap.  Any ideas?
>>>
>>> Thanks.
>>
>> I've notified the secretariat about that. 
> 
> Thanks, that is a bad conflict.
> 
>> How about moving oauth
>> to the iccrg-slot on tuesday and then moving the abfab session
>> to the oauth friday slot?
> 
> Perhaps Hannes might have a concern, but other than that I don't see any
> big problems with the swap you propose.
> 
> Peter
> 

Would anyone have a problem with iccrg for abfab (this is my last
attempt...) ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1sN0YACgkQ8Jx8FtbMZncZgQCguLJvboQUCoJx8FFUKsQIHje/
MsQAoMD/dv0re9bfY1+lOSUKB/RjKvuE
=eY8c
-----END PGP SIGNATURE-----

From wesley.m.eddy@nasa.gov  Mon Feb 28 19:09:28 2011
Return-Path: <wesley.m.eddy@nasa.gov>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23D353A6D6D for <wgchairs@core3.amsl.com>; Mon, 28 Feb 2011 19:09:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NXL5xVLcIc6r for <wgchairs@core3.amsl.com>; Mon, 28 Feb 2011 19:09:27 -0800 (PST)
Received: from ndjsnpf03.ndc.nasa.gov (ndjsnpf03.ndc.nasa.gov [198.117.1.123]) by core3.amsl.com (Postfix) with ESMTP id 23E9F3A6D16 for <wgchairs@ietf.org>; Mon, 28 Feb 2011 19:09:27 -0800 (PST)
Received: from ndjsppt04.ndc.nasa.gov (ndjsppt04.ndc.nasa.gov [198.117.1.103]) by ndjsnpf03.ndc.nasa.gov (Postfix) with ESMTP id 389772D8025; Mon, 28 Feb 2011 21:10:28 -0600 (CST)
Received: from ndjshub05.ndc.nasa.gov (ndjshub05.ndc.nasa.gov [198.117.4.164]) by ndjsppt04.ndc.nasa.gov (8.14.4/8.14.4) with ESMTP id p213ASFq002398; Mon, 28 Feb 2011 21:10:28 -0600
Received: from NDJSSCC01.ndc.nasa.gov ([198.117.4.166]) by ndjshub05.ndc.nasa.gov ([198.117.4.164]) with mapi; Mon, 28 Feb 2011 21:10:28 -0600
From: "Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]" <wesley.m.eddy@nasa.gov>
To: Leif Johansson <leifj@sunet.se>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Date: Mon, 28 Feb 2011 21:09:22 -0600
Subject: RE: 80th IETF DRAFT Agenda
Thread-Topic: 80th IETF DRAFT Agenda
Thread-Index: AcvXo88Q3wA8Hq/jSDKwGE+y7rQojwAGkEFF
Message-ID: <C304DB494AC0C04C87C6A6E2FF5603DB482B706AB0@NDJSSCC01.ndc.nasa.gov>
References: <20110225042952.4367F3A6904@core3.amsl.com> <ldvy64z6g53.fsf@cathode-dark-space.mit.edu>	<4D6C1C37.1050508@sunet.se> <4D6C2242.9080005@stpeter.im>,<4D6C374B.2020502@sunet.se>
In-Reply-To: <4D6C374B.2020502@sunet.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2011-03-01_02:2011-02-28, 2011-03-01, 1970-01-01 signatures=0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 03:09:28 -0000

ICCRG would not be acceptable in the ABFAB slot because TSVWG is currently =
in the ABFAB slot and would be a primary conflict for the majority of the I=
CCRG participants.

________________________________________
From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] On Behalf Of Le=
if Johansson [leifj@sunet.se]
Sent: Monday, February 28, 2011 7:01 PM
To: wgchairs@ietf.org
Subject: Re: 80th IETF DRAFT Agenda

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

On 02/28/2011 11:31 PM, Peter Saint-Andre wrote:
> On 2/28/11 3:05 PM, Leif Johansson wrote:
>> On 02/28/2011 09:47 PM, Tom Yu wrote:
>>> abfab (2nd session) Fri 13:00-14:00 conflicts with kitten (1st session)
>>
>>> I don't have a suggested schedule swap yet, but these two groups
>>> have a lot of participant overlap.  Any ideas?
>>>
>>> Thanks.
>>
>> I've notified the secretariat about that.
>
> Thanks, that is a bad conflict.
>
>> How about moving oauth
>> to the iccrg-slot on tuesday and then moving the abfab session
>> to the oauth friday slot?
>
> Perhaps Hannes might have a concern, but other than that I don't see any
> big problems with the swap you propose.
>
> Peter
>

Would anyone have a problem with iccrg for abfab (this is my last
attempt...) ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1sN0YACgkQ8Jx8FtbMZncZgQCguLJvboQUCoJx8FFUKsQIHje/
MsQAoMD/dv0re9bfY1+lOSUKB/RjKvuE
=3DeY8c
-----END PGP SIGNATURE-----=
