
From wwwrun@core3.amsl.com  Tue Jan  4 08:21:56 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 414BC3A6CCE; Tue,  4 Jan 2011 08:21:56 -0800 (PST)
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 80th IETF - Working Group/BOF Scheduling 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110104162156.414BC3A6CCE@core3.amsl.com>
Date: Tue,  4 Jan 2011 08:21:56 -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: Tue, 04 Jan 2011 16:21: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.

•  2010-12-27 (Monday): Working Group and BOF scheduling begins. To
request a Working Group session, use the IETF Meeting Session Request
Tool. 
•  2011- 01-31 (Monday): Cutoff date for BOF proposal requests to Area
Directors at 17:00 PT (01:00 Tuesday, February 1 UTC). To request a BOF,
please see instructions on Requesting a BOF. 
•  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 wwwrun@core3.amsl.com  Tue Jan  4 17:40:41 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 D8D323A6807; Tue,  4 Jan 2011 17:40:41 -0800 (PST)
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: IETF 80 - Registration is Now Open 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110105014041.D8D323A6807@core3.amsl.com>
Date: Tue,  4 Jan 2011 17:40:41 -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, 05 Jan 2011 01:40:42 -0000

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

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

1.  Registration
2.  Meeting and Training Schedule
3.  Visas & Letters of Invitation
4.  Accommodations, Breakfast and Cancellation Policy
5.  NEW: Companion Program

1. Registration
	A. Early-Bird Registration - USD 650.00 Pay by Friday, 18 March
	2011 17:00 PT (01:00 Saturday, 19 March UTC) 
	B. After Early-Bird cutoff - USD 800.00
	C. Full-time Student Registrations - USD 150.00 (with proper ID)
	D. One Day Pass Registration - USD 350.00
	E. Registration Cancellation 	
		Cut-off for registration cancellation is Monday, 
		21 March 2011 at 17:00 PT (01:00 Tuesday, 22 March UTC). 
		Cancellations are subject to a 10% (ten percent)
		cancellation fee if requested by that date and time.
	F.  Online Registration and Payment ends Friday, 25 March 2011,
	17:00 local time, Europe/Prague (09:00 PT, 16:00 UTC).
	G. On-site Registration starting Sunday, 27 March 2011 at 11:00 AM
	local Prague time.

2. Meeting and Training Schedule: 
	A. Meeting starts Monday morning and runs through Friday at 
	15:15 local time. 
	B. Most training sessions will take place on Sunday afternoon 
	27 March 2011. 

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, Breakfast and Cancellation Policy
	The IETF is holding blocks of guest rooms at 3 hotels in Prague:
	the Hilton Prague (the Meeting Venue), the InterContinental Prague
	and the Sheraton Prague Charles Square Hotel, both of which are in
	Prague Old Town and a 25 minute walk from the Hilton. There are
	smaller hotels located closer to the Hilton Prague.

	Room rates are inclusive of daily breakfast and in room
	high-speed Internet access. 
	Note that breakfast will not be served at the Meeting venue as it 
	is included in the above hotel guest room rates.

	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.  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.

Only 79 days until the Prague IETF!

From jari.arkko@piuha.net  Wed Jan  5 13:27:30 2011
Return-Path: <jari.arkko@piuha.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 B386B3A6B8E; Wed,  5 Jan 2011 13:27:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, 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 0oJ8oYNGEEpa; Wed,  5 Jan 2011 13:27:29 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 79D9B3A6B87; Wed,  5 Jan 2011 13:27:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E98CF2CC45; Wed,  5 Jan 2011 23:29:35 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q3r1HQWHVx3y; Wed,  5 Jan 2011 23:29:35 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 1950F2CC2F; Wed,  5 Jan 2011 23:29:34 +0200 (EET)
Message-ID: <4D24E2BE.6010207@piuha.net>
Date: Wed, 05 Jan 2011 22:29:34 +0100
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>, Working Group Chairs <wgchairs@ietf.org>
Subject: time to act on IETF-80 BOFs
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, 05 Jan 2011 21:27:30 -0000

Just as a reminder, if any of you are thinking of proposing new IETF
work: the deadline for BOF proposals for the next meeting is January
31st. But if you have something in mind, please talk to your ADs as soon
as possible. More information at
http://www.ietf.org/meeting/cutoff-dates-2011.html#IETF80

Jari


From lars.eggert@nokia.com  Mon Jan 10 04:56:15 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 9B8E828C142 for <wgchairs@core3.amsl.com>; Mon, 10 Jan 2011 04:56:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.806
X-Spam-Level: 
X-Spam-Status: No, score=-104.806 tagged_above=-999 required=5 tests=[AWL=-2.207, 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 42QbbwlmZalJ for <wgchairs@core3.amsl.com>; Mon, 10 Jan 2011 04:56:13 -0800 (PST)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by core3.amsl.com (Postfix) with ESMTP id 823D628C159 for <wgchairs@ietf.org>; Mon, 10 Jan 2011 04:56:13 -0800 (PST)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da02.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p0ACwPa6007960 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Mon, 10 Jan 2011 14:58:26 +0200
From: Eggert Lars (Nokia-NRC/Espoo) <lars.eggert@nokia.com>
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96.5 at fit.nokia.com
Content-Type: multipart/signed; boundary=Apple-Mail-14-677000489; protocol="application/pkcs7-signature"; micalg=sha1
Subject: latest missing replaced-by information
Date: Mon, 10 Jan 2011 14:58:16 +0200
Message-Id: <D2906EA5-2DAB-44C3-A3C7-86598C0CBF29@nokia.com>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Mon, 10 Jan 2011 14:58:21 +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: Mon, 10 Jan 2011 12:56:15 -0000

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

Hi,

here's yet another installment in the series of reports on potentially =
missing "replaced-by" relationships in the IETF datatracker.

WG chairs are encouraged to check whether these are accurate for their =
WGs, and if so, send a ticket to the secretariat instructing them to =
"record in the database that draft X replaced draft Y".

As always, double-check before reporting to the secretariat. Also, see =
list of possible inconsistencies at the end of the report.

(Note that the IPR disclosure search tool uses these replaced-by =
relationships, so keeping them up-to-date is actually useful and not =
just WG hygiene.)

Lars

-----------------------------------------------------------------
APP Area
-----------------------------------------------------------------
EAI Working Group, APP Area
   draft-yao-eai-rfc5336bis POTENTIALLY REPLACED BY =
draft-ietf-eai-rfc5336bis

SIEVE Working Group, APP Area
   draft-george-sieve-autoreply POTENTIALLY REPLACED BY =
draft-ietf-sieve-autoreply
   draft-george-sieve-notify-presence POTENTIALLY REPLACED BY =
draft-ietf-sieve-notify-presence

-----------------------------------------------------------------
INT Area
-----------------------------------------------------------------
6MAN Working Group, INT Area
   draft-arifumi-6man-rfc3484-revise POTENTIALLY REPLACED BY =
draft-ietf-6man-rfc3484-revise
   draft-carpenter-6man-flow-update POTENTIALLY REPLACED BY =
draft-ietf-6man-flow-update
   draft-fujisaki-6man-addr-select-opt POTENTIALLY REPLACED BY =
draft-ietf-6man-addr-select-opt
   draft-joshi-6man-neighbor-inform POTENTIALLY REPLACED BY =
draft-ietf-6man-neighbor-inform

ANCP Working Group, INT Area
   draft-lefaucheur-ancp-mc-extensions POTENTIALLY REPLACED BY =
draft-ietf-ancp-mc-extensions

AUTOCONF Working Group, INT Area
   draft-baccelli-autoconf-adhoc-addr-model POTENTIALLY REPLACED BY =
draft-ietf-autoconf-adhoc-addr-model

CSI Working Group, INT Area
   draft-jiang-csi-dhcpv6-cga-ps POTENTIALLY REPLACED BY =
draft-ietf-csi-dhcpv6-cga-ps
   draft-rgaglian-csi-send-name-type-registry POTENTIALLY REPLACED BY =
draft-ietf-csi-send-name-type-registry

DHC Working Group, INT Area
   draft-miles-dhc-dhcpv6-ldra POTENTIALLY REPLACED BY =
draft-ietf-dhc-dhcpv6-ldra

DNSEXT Working Group, INT Area
   draft-dolmatov-dnsext-dnssec-gost POTENTIALLY REPLACED BY =
draft-ietf-dnsext-dnssec-gost
   draft-wang-dnsext-newzone-notify POTENTIALLY REPLACED BY =
draft-ietf-dnsext-newzone-notify

HIP Working Group, INT Area
   draft-camarillo-hip-via POTENTIALLY REPLACED BY draft-ietf-hip-via
   draft-henderson-hip-rfc5206-bis POTENTIALLY REPLACED BY =
draft-ietf-hip-rfc5206-bis
   draft-jokela-hip-rfc5202-bis POTENTIALLY REPLACED BY =
draft-ietf-hip-rfc5202-bis
   draft-keranen-hip-native-nat-traversal POTENTIALLY REPLACED BY =
draft-ietf-hip-native-nat-traversal
   draft-keranen-hip-over-hip POTENTIALLY REPLACED BY =
draft-ietf-hip-over-hip
   draft-keranen-hip-reload-instance POTENTIALLY REPLACED BY =
draft-ietf-hip-reload-instance
   draft-moskowitz-hip-rfc4423-bis POTENTIALLY REPLACED BY =
draft-ietf-hip-rfc4423-bis
   draft-moskowitz-hip-rfc5201-bis POTENTIALLY REPLACED BY =
draft-ietf-hip-rfc5201-bis
   draft-nikander-hip-hiccups POTENTIALLY REPLACED BY =
draft-ietf-hip-hiccups

LISP Working Group, INT Area
   draft-schudel-lisp-mib POTENTIALLY REPLACED BY draft-ietf-lisp-mib

NETEXT Working Group, INT Area
   draft-korhonen-netext-redirect POTENTIALLY REPLACED BY =
draft-ietf-netext-redirect
   draft-krishnan-netext-pmip-lr POTENTIALLY REPLACED BY =
draft-ietf-netext-pmip-lr
   draft-melia-netext-logical-interface-support POTENTIALLY REPLACED BY =
draft-ietf-netext-logical-interface-support

SAVI Working Group, INT Area
   draft-vogt-savi-framework POTENTIALLY REPLACED BY =
draft-ietf-savi-framework

SOFTWIRE Working Group, INT Area
   draft-guo-softwire-6rd-radius-attrib POTENTIALLY REPLACED BY =
draft-ietf-softwire-6rd-radius-attrib
   draft-maglione-softwire-dslite-radius-ext POTENTIALLY REPLACED BY =
draft-ietf-softwire-dslite-radius-ext

-----------------------------------------------------------------
OPS Area
-----------------------------------------------------------------
BMWG Working Group, OPS Area
   draft-asati-bmwg-reset POTENTIALLY REPLACED BY draft-ietf-bmwg-reset
   draft-janovak-bmwg-ipflow-meth POTENTIALLY REPLACED BY =
draft-ietf-bmwg-ipflow-meth
   draft-novak-bmwg-ipflow-meth POTENTIALLY REPLACED BY =
draft-ietf-bmwg-ipflow-meth

DIME Working Group, OPS Area
   draft-zorn-dime-rfc4005bis POTENTIALLY REPLACED BY =
draft-ietf-dime-rfc4005bis

EMAN Working Group, OPS Area
   draft-parello-eman-energy-aware-mib POTENTIALLY REPLACED BY =
draft-ietf-eman-energy-aware-mib

GROW Working Group, OPS Area
   draft-dimitri-grow-rss POTENTIALLY REPLACED BY draft-ietf-grow-rss
   draft-manderson-grow-geomrt POTENTIALLY REPLACED BY =
draft-ietf-grow-geomrt

IPFIX Working Group, OPS Area
   draft-boschi-ipfix-anon POTENTIALLY REPLACED BY draft-ietf-ipfix-anon
   draft-boschi-ipfix-exporting-type POTENTIALLY REPLACED BY =
draft-ietf-ipfix-exporting-type
   draft-claise-ipfix-export-per-sctp-stream POTENTIALLY REPLACED BY =
draft-ietf-ipfix-export-per-sctp-stream
   draft-gupta-ipfix-reliability-template-ext POTENTIALLY REPLACED BY =
draft-ietf-ipfix-reliability-template-ext
   draft-trammell-ipfix-file POTENTIALLY REPLACED BY =
draft-ietf-ipfix-file

MBONED Working Group, OPS Area
   draft-asaeda-mboned-mtrace-v2 POTENTIALLY REPLACED BY =
draft-ietf-mboned-mtrace-v2
   draft-asaeda-mboned-session-announcement-req POTENTIALLY REPLACED BY =
draft-ietf-mboned-session-announcement-req
   draft-venaas-mboned-ssmping POTENTIALLY REPLACED BY =
draft-ietf-mboned-ssmping

NETCONF Working Group, OPS Area
   draft-bierman-netconf-access-control POTENTIALLY REPLACED BY =
draft-ietf-netconf-access-control
   draft-bierman-netconf-with-defaults POTENTIALLY REPLACED BY =
draft-ietf-netconf-with-defaults
   draft-chisholm-netconf-monitoring POTENTIALLY REPLACED BY =
draft-ietf-netconf-monitoring

NETMOD Working Group, OPS Area
   draft-bierman-netmod-yang-usage POTENTIALLY REPLACED BY =
draft-ietf-netmod-yang-usage
   draft-schoenw-netmod-yang-types POTENTIALLY REPLACED BY =
draft-ietf-netmod-yang-types
   draft-shafer-netmod-arch POTENTIALLY REPLACED BY =
draft-ietf-netmod-arch

OPSAWG Working Group, OPS Area
   draft-mizrahi-opsawg-oam-overview POTENTIALLY REPLACED BY =
draft-ietf-opsawg-oam-overview

OPSEC Working Group, OPS Area
   draft-gont-opsec-icmp-filtering POTENTIALLY REPLACED BY =
draft-ietf-opsec-icmp-filtering
   draft-gont-opsec-ip-security POTENTIALLY REPLACED BY =
draft-ietf-opsec-ip-security

RADEXT Working Group, OPS Area
   draft-dekok-radext-dtls POTENTIALLY REPLACED BY =
draft-ietf-radext-dtls
   draft-dekok-radext-tcp-transport POTENTIALLY REPLACED BY =
draft-ietf-radext-tcp-transport
   draft-lourdelet-radext-ipv6-access POTENTIALLY REPLACED BY =
draft-ietf-radext-ipv6-access
   draft-nelson-radext-crypto-agility-requirements POTENTIALLY REPLACED =
BY draft-ietf-radext-crypto-agility-requirements
   draft-tiwari-radext-tunnel-type POTENTIALLY REPLACED BY =
draft-ietf-radext-tunnel-type

V6OPS Working Group, OPS Area
   draft-rgaglian-v6ops-v6inixp POTENTIALLY REPLACED BY =
draft-ietf-v6ops-v6inixp
   draft-vandevelde-v6ops-ra-guard POTENTIALLY REPLACED BY =
draft-ietf-v6ops-ra-guard

-----------------------------------------------------------------
RAI Area
-----------------------------------------------------------------
ATOCA Working Group, RAI Area
   draft-rosen-atoca-cap POTENTIALLY REPLACED BY draft-ietf-atoca-cap
   draft-schulzrinne-atoca-requirements POTENTIALLY REPLACED BY =
draft-ietf-atoca-requirements

BLISS Working Group, RAI Area
   draft-elwell-bliss-ach-analysis POTENTIALLY REPLACED BY =
draft-ietf-bliss-ach-analysis
   draft-poetzl-bliss-call-completion POTENTIALLY REPLACED BY =
draft-ietf-bliss-call-completion
   draft-procter-bliss-call-park-extension POTENTIALLY REPLACED BY =
draft-ietf-bliss-call-park-extension
   draft-rosenberg-bliss-problem-statement POTENTIALLY REPLACED BY =
draft-ietf-bliss-problem-statement

CUSS Working Group, RAI Area
   draft-johnston-cuss-sip-uui-reqs POTENTIALLY REPLACED BY =
draft-ietf-cuss-sip-uui-reqs

DRINKS Working Group, RAI Area
   draft-channabasappa-drinks-usecases-requirements POTENTIALLY REPLACED =
BY draft-ietf-drinks-usecases-requirements

ECRIT Working Group, RAI Area
   draft-barnes-ecrit-rough-loc POTENTIALLY REPLACED BY =
draft-ietf-ecrit-rough-loc
   draft-rosen-ecrit-additional-data POTENTIALLY REPLACED BY =
draft-ietf-ecrit-additional-data
   draft-rosen-ecrit-data-only-ea POTENTIALLY REPLACED BY =
draft-ietf-ecrit-data-only-ea
   draft-schulzrinne-ecrit-location-hiding-req POTENTIALLY REPLACED BY =
draft-ietf-ecrit-location-hiding-req
   draft-schulzrinne-ecrit-lost-sync POTENTIALLY REPLACED BY =
draft-ietf-ecrit-lost-sync
   draft-schulzrinne-ecrit-psap-callback POTENTIALLY REPLACED BY =
draft-ietf-ecrit-psap-callback
   draft-schulzrinne-ecrit-unauthenticated-access POTENTIALLY REPLACED =
BY draft-ietf-ecrit-unauthenticated-access
   draft-taylor-ecrit-security-threats POTENTIALLY REPLACED BY =
draft-ietf-ecrit-security-threats
   draft-tschofenig-ecrit-trustworthy-location POTENTIALLY REPLACED BY =
draft-ietf-ecrit-trustworthy-location
   draft-winterbottom-ecrit-specifying-holes POTENTIALLY REPLACED BY =
draft-ietf-ecrit-specifying-holes

GEOPRIV Working Group, RAI Area
   draft-mayrhofer-geopriv-geo-uri POTENTIALLY REPLACED BY =
draft-ietf-geopriv-geo-uri

P2PSIP Working Group, RAI Area
   draft-bryan-p2psip-reload POTENTIALLY REPLACED BY =
draft-ietf-p2psip-reload

SPEERMINT Working Group, RAI Area
   draft-meyer-speermint-reqs-and-terminology POTENTIALLY REPLACED BY =
draft-ietf-speermint-reqs-and-terminology
   draft-niccolini-speermint-voipthreats POTENTIALLY REPLACED BY =
draft-ietf-speermint-voipthreats

XCON Working Group, RAI Area
   draft-barnes-xcon-ccmp POTENTIALLY REPLACED BY draft-ietf-xcon-ccmp
   draft-barnes-xcon-examples POTENTIALLY REPLACED BY =
draft-ietf-xcon-examples

XMPP Working Group, RAI Area
   draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna

-----------------------------------------------------------------
RTG Area
-----------------------------------------------------------------
CCAMP Working Group, RTG Area
   draft-berger-ccamp-assoc-info POTENTIALLY REPLACED BY =
draft-ietf-ccamp-assoc-info
   draft-berger-ccamp-attribute-bnf POTENTIALLY REPLACED BY =
draft-ietf-ccamp-attribute-bnf
   draft-bernstein-ccamp-wson-signaling POTENTIALLY REPLACED BY =
draft-ietf-ccamp-wson-signaling
   draft-kern-ccamp-rsvp-te-sdh-otn-oam-ext POTENTIALLY REPLACED BY =
draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext
   draft-lee-ccamp-wson-signal-compatibility-ospf POTENTIALLY REPLACED =
BY draft-ietf-ccamp-wson-signal-compatibility-ospf
   draft-li-ccamp-lmp-behavior-negotiation POTENTIALLY REPLACED BY =
draft-ietf-ccamp-lmp-behavior-negotiation
   draft-sun-ccamp-dpm POTENTIALLY REPLACED BY draft-ietf-ccamp-dpm
   draft-takacs-ccamp-asymm-bw-bidir-lsps-bis POTENTIALLY REPLACED BY =
draft-ietf-ccamp-asymm-bw-bidir-lsps-bis
   draft-zhang-ccamp-gmpls-g709-framework POTENTIALLY REPLACED BY =
draft-ietf-ccamp-gmpls-g709-framework

FORCES Working Group, RTG Area
   draft-hadi-forces-sctptml POTENTIALLY REPLACED BY =
draft-ietf-forces-sctptml
   draft-haleplidis-forces-implementation-experience POTENTIALLY =
REPLACED BY draft-ietf-forces-implementation-experience

IDR Working Group, RTG Area
   draft-uttaro-idr-add-paths-guidelines POTENTIALLY REPLACED BY =
draft-ietf-idr-add-paths-guidelines

ISIS Working Group, RTG Area
   draft-chopps-isis-bfd-tlv POTENTIALLY REPLACED BY =
draft-ietf-isis-bfd-tlv
   draft-ginsberg-isis-genapp POTENTIALLY REPLACED BY =
draft-ietf-isis-genapp
   draft-previdi-isis-mi POTENTIALLY REPLACED BY draft-ietf-isis-mi

L2VPN Working Group, RTG Area
   draft-henderickx-l2vpn-vpls-multihoming POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-multihoming
   draft-kompella-l2vpn-vpls-multihoming POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-multihoming
   draft-pdutta-l2vpn-vpls-ldp-mac-opt POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-ldp-mac-opt
   draft-pkwok-l2vpn-vpls-macflush-ld POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-macflush-ld
   draft-sajassi-l2vpn-vpls-pbb-interop POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-pbb-interop

MANET Working Group, RTG Area
   draft-sratliff-manet-dlep POTENTIALLY REPLACED BY =
draft-ietf-manet-dlep

MPLS Working Group, RTG Area
   draft-frost-mpls-loss-delay POTENTIALLY REPLACED BY =
draft-ietf-mpls-loss-delay
   draft-frost-mpls-tp-loss-delay-profile POTENTIALLY REPLACED BY =
draft-ietf-mpls-tp-loss-delay-profile

OSPF Working Group, RTG Area
   draft-acee-ospf-multi-instance POTENTIALLY REPLACED BY =
draft-ietf-ospf-multi-instance
   draft-acee-ospf-transport-instance POTENTIALLY REPLACED BY =
draft-ietf-ospf-transport-instance
   draft-hartman-ospf-analysis POTENTIALLY REPLACED BY =
draft-ietf-ospf-analysis
   draft-nguyen-ospf-lls POTENTIALLY REPLACED BY draft-ietf-ospf-lls
   draft-ogier-ospf-dbex-opt POTENTIALLY REPLACED BY =
draft-ietf-ospf-dbex-opt
   draft-venkata-ospf-dynamic-hostname POTENTIALLY REPLACED BY =
draft-ietf-ospf-dynamic-hostname

PCE Working Group, RTG Area
   draft-bradford-pce-path-key POTENTIALLY REPLACED BY =
draft-ietf-pce-path-key
   draft-farrel-pce-vendor-constraints POTENTIALLY REPLACED BY =
draft-ietf-pce-vendor-constraints
   draft-king-pce-inter-area-as-applicability POTENTIALLY REPLACED BY =
draft-ietf-pce-inter-area-as-applicability
   draft-kkoushik-pce-pcep-mib POTENTIALLY REPLACED BY =
draft-ietf-pce-pcep-mib
   draft-lee-pce-wson-routing-wavelength POTENTIALLY REPLACED BY =
draft-ietf-pce-wson-routing-wavelength
   draft-leroux-pce-of POTENTIALLY REPLACED BY draft-ietf-pce-of
   draft-margaria-pce-gmpls-pcep-extensions POTENTIALLY REPLACED BY =
draft-ietf-pce-gmpls-pcep-extensions
   draft-oki-pce-inter-layer-ext POTENTIALLY REPLACED BY =
draft-ietf-pce-inter-layer-ext
   draft-otani-pce-gmpls-aps-req POTENTIALLY REPLACED BY =
draft-ietf-pce-gmpls-aps-req
   draft-sivabalan-pce-dste POTENTIALLY REPLACED BY draft-ietf-pce-dste
   draft-vasseur-pce-monitoring POTENTIALLY REPLACED BY =
draft-ietf-pce-monitoring
   draft-yasukawa-pce-p2mp-app POTENTIALLY REPLACED BY =
draft-ietf-pce-p2mp-app
   draft-yasukawa-pce-p2mp-req POTENTIALLY REPLACED BY =
draft-ietf-pce-p2mp-req
   draft-yasukawa-pce-vpn-req POTENTIALLY REPLACED BY =
draft-ietf-pce-vpn-req

PWE3 Working Group, RTG Area
   draft-lm-pwe3-mpls-tp-gal-in-pw POTENTIALLY REPLACED BY =
draft-ietf-pwe3-mpls-tp-gal-in-pw

ROLL Working Group, RTG Area
   draft-dt-roll-p2p-rpl POTENTIALLY REPLACED BY draft-ietf-roll-p2p-rpl
   draft-gnawali-roll-minrank-hysteresis-of POTENTIALLY REPLACED BY =
draft-ietf-roll-minrank-hysteresis-of
   draft-levis-roll-trickle POTENTIALLY REPLACED BY =
draft-ietf-roll-trickle
   draft-tsao-roll-security-framework POTENTIALLY REPLACED BY =
draft-ietf-roll-security-framework

SIDR Working Group, RTG Area
   draft-huston-sidr-bogons POTENTIALLY REPLACED BY =
draft-ietf-sidr-bogons
   draft-huston-sidr-keyroll POTENTIALLY REPLACED BY =
draft-ietf-sidr-keyroll
   draft-huston-sidr-repos-struct POTENTIALLY REPLACED BY =
draft-ietf-sidr-repos-struct
   draft-huston-sidr-roa-validation POTENTIALLY REPLACED BY =
draft-ietf-sidr-roa-validation
   draft-huston-sidr-rpki-algs POTENTIALLY REPLACED BY =
draft-ietf-sidr-rpki-algs
   draft-kisteleki-sidr-rpsl-sig POTENTIALLY REPLACED BY =
draft-ietf-sidr-rpsl-sig
   draft-manderson-sidr-usecases POTENTIALLY REPLACED BY =
draft-ietf-sidr-usecases
   draft-pmohapat-sidr-origin-validation-signaling POTENTIALLY REPLACED =
BY draft-ietf-sidr-origin-validation-signaling
   draft-pmohapat-sidr-pfx-validate POTENTIALLY REPLACED BY =
draft-ietf-sidr-pfx-validate
   draft-weiler-sidr-publication POTENTIALLY REPLACED BY =
draft-ietf-sidr-publication

-----------------------------------------------------------------
SEC Area
-----------------------------------------------------------------
DKIM Working Group, SEC Area
   draft-lindsey-dkim-mailinglists POTENTIALLY REPLACED BY =
draft-ietf-dkim-mailinglists

HOKEY Working Group, SEC Area
   draft-wu-hokey-rfc5296bis POTENTIALLY REPLACED BY =
draft-ietf-hokey-rfc5296bis

PKIX Working Group, SEC Area
   draft-cooper-pkix-rfc2560bis POTENTIALLY REPLACED BY =
draft-ietf-pkix-rfc2560bis
   draft-cooper-pkix-rfc5280-clarifications POTENTIALLY REPLACED BY =
draft-ietf-pkix-rfc5280-clarifications
   draft-santesson-pkix-certimage POTENTIALLY REPLACED BY =
draft-ietf-pkix-certimage

TLS Working Group, SEC Area
   draft-rescorla-tls-suiteb POTENTIALLY REPLACED BY =
draft-ietf-tls-suiteb
   draft-seggelmann-tls-dtls-heartbeat POTENTIALLY REPLACED BY =
draft-ietf-tls-dtls-heartbeat

-----------------------------------------------------------------
TSV Area
-----------------------------------------------------------------
BEHAVE Working Group, TSV Area
   draft-liu-behave-ftp64 POTENTIALLY REPLACED BY =
draft-ietf-behave-ftp64

CONEX Working Group, TSV Area
   draft-moncaster-conex-concepts-uses POTENTIALLY REPLACED BY =
draft-ietf-conex-concepts-uses

DCCP Working Group, TSV Area
   draft-renker-dccp-tfrc-rtt-option POTENTIALLY REPLACED BY =
draft-ietf-dccp-tfrc-rtt-option

IPPM Working Group, TSV Area
   draft-geib-ippm-metrictest POTENTIALLY REPLACED BY =
draft-ietf-ippm-metrictest

MPTCP Working Group, TSV Area
   draft-scharf-mptcp-api POTENTIALLY REPLACED BY draft-ietf-mptcp-api

NFSV4 Working Group, TSV Area
   draft-alexrn-nfsv4-ipv6 POTENTIALLY REPLACED BY draft-ietf-nfsv4-ipv6
   draft-eisler-nfsv4-minorversion-2-requirements POTENTIALLY REPLACED =
BY draft-ietf-nfsv4-minorversion-2-requirements
   draft-faibish-nfsv4-pnfs-access-permissions-check POTENTIALLY =
REPLACED BY draft-ietf-nfsv4-pnfs-access-permissions-check

PCN Working Group, TSV Area
   draft-karagiannis-pcn-signaling-requirements POTENTIALLY REPLACED BY =
draft-ietf-pcn-signaling-requirements

TCPM Working Group, TSV Area
   draft-hkchu-tcpm-initcwnd POTENTIALLY REPLACED BY =
draft-ietf-tcpm-initcwnd

-----------------------------------------------------------------
Potential Inconsistencies
-----------------------------------------------------------------
draft-ietf-6lowpan-nd may replace one or more of 2 individual IDs - =
check this
draft-ietf-avt-rtp-gsm-hr may replace one or more of 3 individual IDs - =
check this
draft-ietf-avt-rtp-svc may replace one or more of 2 individual IDs - =
check this
draft-ietf-bmwg-ipflow-meth may replace one or more of 2 individual IDs =
- check this
draft-ietf-decade-survey may replace one or more of 2 individual IDs - =
check this
draft-ietf-dhc-dhcpv4-bulk-leasequery may replace one or more of 2 =
individual IDs - check this
draft-ietf-forces-tmlsp may replace one or more of 2 individual IDs - =
check this
draft-ietf-ipfix-biflow may replace one or more of 2 individual IDs - =
check this
draft-ietf-l2tpext-tdm may replace one or more of 2 individual IDs - =
check this
draft-ietf-l2vpn-vpls-multihoming may replace one or more of 2 =
individual IDs - check this
draft-ietf-mpls-tp-fault may replace one or more of 2 individual IDs - =
check this
draft-ietf-netconf-monitoring may replace one or more of 2 individual =
IDs - check this
draft-ietf-netlmm-lma-discovery may replace one or more of 2 individual =
IDs - check this
draft-ietf-netlmm-mip-interactions may replace one or more of 2 =
individual IDs - check this
draft-ietf-sip-saml may replace one or more of 2 individual IDs - check =
this
draft-ietf-sipping-service-identification may replace one or more of 2 =
individual IDs - check this
draft-ietf-trill-rbridge-arch may replace one or more of 2 individual =
IDs - check this



--Apple-Mail-14-677000489
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDExMDEyNTgxN1owIwYJKoZIhvcNAQkE
MRYEFJRNJl3YtT+zarLKEU/HcBjThhwKMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
ACK38Fthk6E2mMa70yQSh+qyK5YklayMU5GQFn4kEwYTY4asIT1VLj9q0SPmWS44I1B/5YwYlBBw
PUs01pvInaxkS4/lJzzr1C87H9QH4xx2dI4T0Zvyy35u8tpN1vv8Sb2QODK+2InxaOvV/QYi+ls4
bgGzgYuteL7DS+dQ4BV43Lz1WXnu9qvXQxXgyDLuCuYCKgBr+t/cooXt2hJ4QyiSdvySmE/+9me3
RtvbkPig/5CzzD4mcY0gnDwWeluFwSXeQ9VHZON1TscxRdbr5jYUAkp0qmOFmBmNPMUakDnLr03W
Hd1PV3tXabCdNZnaTgurI2uexTpmld02vJd0kdIAAAAAAAA=

--Apple-Mail-14-677000489--

From lars.eggert@nokia.com  Tue Jan 11 02:08:32 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 711B73A6A13 for <wgchairs@core3.amsl.com>; Tue, 11 Jan 2011 02:08:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.402
X-Spam-Level: 
X-Spam-Status: No, score=-108.402 tagged_above=-999 required=5 tests=[AWL=1.597, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 4Rs84FE8SDmT for <wgchairs@core3.amsl.com>; Tue, 11 Jan 2011 02:08:30 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id 877AB3A63EB for <wgchairs@ietf.org>; Tue, 11 Jan 2011 02:08:30 -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 p0BAAi6c011338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Tue, 11 Jan 2011 12:10:45 +0200
From: Lars Eggert <lars.eggert@nokia.com>
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96.5 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary=Apple-Mail-1-753344173; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: latest missing replaced-by information
Date: Tue, 11 Jan 2011 12:10:40 +0200
In-Reply-To: <D2906EA5-2DAB-44C3-A3C7-86598C0CBF29@nokia.com>
To: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>
References: <D2906EA5-2DAB-44C3-A3C7-86598C0CBF29@nokia.com>
Message-Id: <3300FFB3-CFCE-44AA-8C69-E9588758D351@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); Tue, 11 Jan 2011 12:10:40 +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: Tue, 11 Jan 2011 10:08:32 -0000

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

Hi,

forgot to mention: even if the WG *tools* page shows that an ID replaces =
another one, the *datatracker* may not have this information. (The tools =
page uses its own heuristic to identify likely replaced-by =
relationships, similar to my script that generates the output below.)

You need to check http://datatracker.ietf.org/doc/<draftname>/ to see if =
it says "State: Replaced by <other-draftname>"

Lars

On 2011-1-10, at 14:58, Eggert Lars (Nokia-NRC/Espoo) wrote:

> Hi,
>=20
> here's yet another installment in the series of reports on potentially =
missing "replaced-by" relationships in the IETF datatracker.
>=20
> WG chairs are encouraged to check whether these are accurate for their =
WGs, and if so, send a ticket to the secretariat instructing them to =
"record in the database that draft X replaced draft Y".
>=20
> As always, double-check before reporting to the secretariat. Also, see =
list of possible inconsistencies at the end of the report.
>=20
> (Note that the IPR disclosure search tool uses these replaced-by =
relationships, so keeping them up-to-date is actually useful and not =
just WG hygiene.)
>=20
> Lars
>=20
> -----------------------------------------------------------------
> APP Area
> -----------------------------------------------------------------
> EAI Working Group, APP Area
>   draft-yao-eai-rfc5336bis POTENTIALLY REPLACED BY =
draft-ietf-eai-rfc5336bis
>=20
> SIEVE Working Group, APP Area
>   draft-george-sieve-autoreply POTENTIALLY REPLACED BY =
draft-ietf-sieve-autoreply
>   draft-george-sieve-notify-presence POTENTIALLY REPLACED BY =
draft-ietf-sieve-notify-presence
>=20
> -----------------------------------------------------------------
> INT Area
> -----------------------------------------------------------------
> 6MAN Working Group, INT Area
>   draft-arifumi-6man-rfc3484-revise POTENTIALLY REPLACED BY =
draft-ietf-6man-rfc3484-revise
>   draft-carpenter-6man-flow-update POTENTIALLY REPLACED BY =
draft-ietf-6man-flow-update
>   draft-fujisaki-6man-addr-select-opt POTENTIALLY REPLACED BY =
draft-ietf-6man-addr-select-opt
>   draft-joshi-6man-neighbor-inform POTENTIALLY REPLACED BY =
draft-ietf-6man-neighbor-inform
>=20
> ANCP Working Group, INT Area
>   draft-lefaucheur-ancp-mc-extensions POTENTIALLY REPLACED BY =
draft-ietf-ancp-mc-extensions
>=20
> AUTOCONF Working Group, INT Area
>   draft-baccelli-autoconf-adhoc-addr-model POTENTIALLY REPLACED BY =
draft-ietf-autoconf-adhoc-addr-model
>=20
> CSI Working Group, INT Area
>   draft-jiang-csi-dhcpv6-cga-ps POTENTIALLY REPLACED BY =
draft-ietf-csi-dhcpv6-cga-ps
>   draft-rgaglian-csi-send-name-type-registry POTENTIALLY REPLACED BY =
draft-ietf-csi-send-name-type-registry
>=20
> DHC Working Group, INT Area
>   draft-miles-dhc-dhcpv6-ldra POTENTIALLY REPLACED BY =
draft-ietf-dhc-dhcpv6-ldra
>=20
> DNSEXT Working Group, INT Area
>   draft-dolmatov-dnsext-dnssec-gost POTENTIALLY REPLACED BY =
draft-ietf-dnsext-dnssec-gost
>   draft-wang-dnsext-newzone-notify POTENTIALLY REPLACED BY =
draft-ietf-dnsext-newzone-notify
>=20
> HIP Working Group, INT Area
>   draft-camarillo-hip-via POTENTIALLY REPLACED BY draft-ietf-hip-via
>   draft-henderson-hip-rfc5206-bis POTENTIALLY REPLACED BY =
draft-ietf-hip-rfc5206-bis
>   draft-jokela-hip-rfc5202-bis POTENTIALLY REPLACED BY =
draft-ietf-hip-rfc5202-bis
>   draft-keranen-hip-native-nat-traversal POTENTIALLY REPLACED BY =
draft-ietf-hip-native-nat-traversal
>   draft-keranen-hip-over-hip POTENTIALLY REPLACED BY =
draft-ietf-hip-over-hip
>   draft-keranen-hip-reload-instance POTENTIALLY REPLACED BY =
draft-ietf-hip-reload-instance
>   draft-moskowitz-hip-rfc4423-bis POTENTIALLY REPLACED BY =
draft-ietf-hip-rfc4423-bis
>   draft-moskowitz-hip-rfc5201-bis POTENTIALLY REPLACED BY =
draft-ietf-hip-rfc5201-bis
>   draft-nikander-hip-hiccups POTENTIALLY REPLACED BY =
draft-ietf-hip-hiccups
>=20
> LISP Working Group, INT Area
>   draft-schudel-lisp-mib POTENTIALLY REPLACED BY draft-ietf-lisp-mib
>=20
> NETEXT Working Group, INT Area
>   draft-korhonen-netext-redirect POTENTIALLY REPLACED BY =
draft-ietf-netext-redirect
>   draft-krishnan-netext-pmip-lr POTENTIALLY REPLACED BY =
draft-ietf-netext-pmip-lr
>   draft-melia-netext-logical-interface-support POTENTIALLY REPLACED BY =
draft-ietf-netext-logical-interface-support
>=20
> SAVI Working Group, INT Area
>   draft-vogt-savi-framework POTENTIALLY REPLACED BY =
draft-ietf-savi-framework
>=20
> SOFTWIRE Working Group, INT Area
>   draft-guo-softwire-6rd-radius-attrib POTENTIALLY REPLACED BY =
draft-ietf-softwire-6rd-radius-attrib
>   draft-maglione-softwire-dslite-radius-ext POTENTIALLY REPLACED BY =
draft-ietf-softwire-dslite-radius-ext
>=20
> -----------------------------------------------------------------
> OPS Area
> -----------------------------------------------------------------
> BMWG Working Group, OPS Area
>   draft-asati-bmwg-reset POTENTIALLY REPLACED BY draft-ietf-bmwg-reset
>   draft-janovak-bmwg-ipflow-meth POTENTIALLY REPLACED BY =
draft-ietf-bmwg-ipflow-meth
>   draft-novak-bmwg-ipflow-meth POTENTIALLY REPLACED BY =
draft-ietf-bmwg-ipflow-meth
>=20
> DIME Working Group, OPS Area
>   draft-zorn-dime-rfc4005bis POTENTIALLY REPLACED BY =
draft-ietf-dime-rfc4005bis
>=20
> EMAN Working Group, OPS Area
>   draft-parello-eman-energy-aware-mib POTENTIALLY REPLACED BY =
draft-ietf-eman-energy-aware-mib
>=20
> GROW Working Group, OPS Area
>   draft-dimitri-grow-rss POTENTIALLY REPLACED BY draft-ietf-grow-rss
>   draft-manderson-grow-geomrt POTENTIALLY REPLACED BY =
draft-ietf-grow-geomrt
>=20
> IPFIX Working Group, OPS Area
>   draft-boschi-ipfix-anon POTENTIALLY REPLACED BY =
draft-ietf-ipfix-anon
>   draft-boschi-ipfix-exporting-type POTENTIALLY REPLACED BY =
draft-ietf-ipfix-exporting-type
>   draft-claise-ipfix-export-per-sctp-stream POTENTIALLY REPLACED BY =
draft-ietf-ipfix-export-per-sctp-stream
>   draft-gupta-ipfix-reliability-template-ext POTENTIALLY REPLACED BY =
draft-ietf-ipfix-reliability-template-ext
>   draft-trammell-ipfix-file POTENTIALLY REPLACED BY =
draft-ietf-ipfix-file
>=20
> MBONED Working Group, OPS Area
>   draft-asaeda-mboned-mtrace-v2 POTENTIALLY REPLACED BY =
draft-ietf-mboned-mtrace-v2
>   draft-asaeda-mboned-session-announcement-req POTENTIALLY REPLACED BY =
draft-ietf-mboned-session-announcement-req
>   draft-venaas-mboned-ssmping POTENTIALLY REPLACED BY =
draft-ietf-mboned-ssmping
>=20
> NETCONF Working Group, OPS Area
>   draft-bierman-netconf-access-control POTENTIALLY REPLACED BY =
draft-ietf-netconf-access-control
>   draft-bierman-netconf-with-defaults POTENTIALLY REPLACED BY =
draft-ietf-netconf-with-defaults
>   draft-chisholm-netconf-monitoring POTENTIALLY REPLACED BY =
draft-ietf-netconf-monitoring
>=20
> NETMOD Working Group, OPS Area
>   draft-bierman-netmod-yang-usage POTENTIALLY REPLACED BY =
draft-ietf-netmod-yang-usage
>   draft-schoenw-netmod-yang-types POTENTIALLY REPLACED BY =
draft-ietf-netmod-yang-types
>   draft-shafer-netmod-arch POTENTIALLY REPLACED BY =
draft-ietf-netmod-arch
>=20
> OPSAWG Working Group, OPS Area
>   draft-mizrahi-opsawg-oam-overview POTENTIALLY REPLACED BY =
draft-ietf-opsawg-oam-overview
>=20
> OPSEC Working Group, OPS Area
>   draft-gont-opsec-icmp-filtering POTENTIALLY REPLACED BY =
draft-ietf-opsec-icmp-filtering
>   draft-gont-opsec-ip-security POTENTIALLY REPLACED BY =
draft-ietf-opsec-ip-security
>=20
> RADEXT Working Group, OPS Area
>   draft-dekok-radext-dtls POTENTIALLY REPLACED BY =
draft-ietf-radext-dtls
>   draft-dekok-radext-tcp-transport POTENTIALLY REPLACED BY =
draft-ietf-radext-tcp-transport
>   draft-lourdelet-radext-ipv6-access POTENTIALLY REPLACED BY =
draft-ietf-radext-ipv6-access
>   draft-nelson-radext-crypto-agility-requirements POTENTIALLY REPLACED =
BY draft-ietf-radext-crypto-agility-requirements
>   draft-tiwari-radext-tunnel-type POTENTIALLY REPLACED BY =
draft-ietf-radext-tunnel-type
>=20
> V6OPS Working Group, OPS Area
>   draft-rgaglian-v6ops-v6inixp POTENTIALLY REPLACED BY =
draft-ietf-v6ops-v6inixp
>   draft-vandevelde-v6ops-ra-guard POTENTIALLY REPLACED BY =
draft-ietf-v6ops-ra-guard
>=20
> -----------------------------------------------------------------
> RAI Area
> -----------------------------------------------------------------
> ATOCA Working Group, RAI Area
>   draft-rosen-atoca-cap POTENTIALLY REPLACED BY draft-ietf-atoca-cap
>   draft-schulzrinne-atoca-requirements POTENTIALLY REPLACED BY =
draft-ietf-atoca-requirements
>=20
> BLISS Working Group, RAI Area
>   draft-elwell-bliss-ach-analysis POTENTIALLY REPLACED BY =
draft-ietf-bliss-ach-analysis
>   draft-poetzl-bliss-call-completion POTENTIALLY REPLACED BY =
draft-ietf-bliss-call-completion
>   draft-procter-bliss-call-park-extension POTENTIALLY REPLACED BY =
draft-ietf-bliss-call-park-extension
>   draft-rosenberg-bliss-problem-statement POTENTIALLY REPLACED BY =
draft-ietf-bliss-problem-statement
>=20
> CUSS Working Group, RAI Area
>   draft-johnston-cuss-sip-uui-reqs POTENTIALLY REPLACED BY =
draft-ietf-cuss-sip-uui-reqs
>=20
> DRINKS Working Group, RAI Area
>   draft-channabasappa-drinks-usecases-requirements POTENTIALLY =
REPLACED BY draft-ietf-drinks-usecases-requirements
>=20
> ECRIT Working Group, RAI Area
>   draft-barnes-ecrit-rough-loc POTENTIALLY REPLACED BY =
draft-ietf-ecrit-rough-loc
>   draft-rosen-ecrit-additional-data POTENTIALLY REPLACED BY =
draft-ietf-ecrit-additional-data
>   draft-rosen-ecrit-data-only-ea POTENTIALLY REPLACED BY =
draft-ietf-ecrit-data-only-ea
>   draft-schulzrinne-ecrit-location-hiding-req POTENTIALLY REPLACED BY =
draft-ietf-ecrit-location-hiding-req
>   draft-schulzrinne-ecrit-lost-sync POTENTIALLY REPLACED BY =
draft-ietf-ecrit-lost-sync
>   draft-schulzrinne-ecrit-psap-callback POTENTIALLY REPLACED BY =
draft-ietf-ecrit-psap-callback
>   draft-schulzrinne-ecrit-unauthenticated-access POTENTIALLY REPLACED =
BY draft-ietf-ecrit-unauthenticated-access
>   draft-taylor-ecrit-security-threats POTENTIALLY REPLACED BY =
draft-ietf-ecrit-security-threats
>   draft-tschofenig-ecrit-trustworthy-location POTENTIALLY REPLACED BY =
draft-ietf-ecrit-trustworthy-location
>   draft-winterbottom-ecrit-specifying-holes POTENTIALLY REPLACED BY =
draft-ietf-ecrit-specifying-holes
>=20
> GEOPRIV Working Group, RAI Area
>   draft-mayrhofer-geopriv-geo-uri POTENTIALLY REPLACED BY =
draft-ietf-geopriv-geo-uri
>=20
> P2PSIP Working Group, RAI Area
>   draft-bryan-p2psip-reload POTENTIALLY REPLACED BY =
draft-ietf-p2psip-reload
>=20
> SPEERMINT Working Group, RAI Area
>   draft-meyer-speermint-reqs-and-terminology POTENTIALLY REPLACED BY =
draft-ietf-speermint-reqs-and-terminology
>   draft-niccolini-speermint-voipthreats POTENTIALLY REPLACED BY =
draft-ietf-speermint-voipthreats
>=20
> XCON Working Group, RAI Area
>   draft-barnes-xcon-ccmp POTENTIALLY REPLACED BY draft-ietf-xcon-ccmp
>   draft-barnes-xcon-examples POTENTIALLY REPLACED BY =
draft-ietf-xcon-examples
>=20
> XMPP Working Group, RAI Area
>   draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna
>=20
> -----------------------------------------------------------------
> RTG Area
> -----------------------------------------------------------------
> CCAMP Working Group, RTG Area
>   draft-berger-ccamp-assoc-info POTENTIALLY REPLACED BY =
draft-ietf-ccamp-assoc-info
>   draft-berger-ccamp-attribute-bnf POTENTIALLY REPLACED BY =
draft-ietf-ccamp-attribute-bnf
>   draft-bernstein-ccamp-wson-signaling POTENTIALLY REPLACED BY =
draft-ietf-ccamp-wson-signaling
>   draft-kern-ccamp-rsvp-te-sdh-otn-oam-ext POTENTIALLY REPLACED BY =
draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext
>   draft-lee-ccamp-wson-signal-compatibility-ospf POTENTIALLY REPLACED =
BY draft-ietf-ccamp-wson-signal-compatibility-ospf
>   draft-li-ccamp-lmp-behavior-negotiation POTENTIALLY REPLACED BY =
draft-ietf-ccamp-lmp-behavior-negotiation
>   draft-sun-ccamp-dpm POTENTIALLY REPLACED BY draft-ietf-ccamp-dpm
>   draft-takacs-ccamp-asymm-bw-bidir-lsps-bis POTENTIALLY REPLACED BY =
draft-ietf-ccamp-asymm-bw-bidir-lsps-bis
>   draft-zhang-ccamp-gmpls-g709-framework POTENTIALLY REPLACED BY =
draft-ietf-ccamp-gmpls-g709-framework
>=20
> FORCES Working Group, RTG Area
>   draft-hadi-forces-sctptml POTENTIALLY REPLACED BY =
draft-ietf-forces-sctptml
>   draft-haleplidis-forces-implementation-experience POTENTIALLY =
REPLACED BY draft-ietf-forces-implementation-experience
>=20
> IDR Working Group, RTG Area
>   draft-uttaro-idr-add-paths-guidelines POTENTIALLY REPLACED BY =
draft-ietf-idr-add-paths-guidelines
>=20
> ISIS Working Group, RTG Area
>   draft-chopps-isis-bfd-tlv POTENTIALLY REPLACED BY =
draft-ietf-isis-bfd-tlv
>   draft-ginsberg-isis-genapp POTENTIALLY REPLACED BY =
draft-ietf-isis-genapp
>   draft-previdi-isis-mi POTENTIALLY REPLACED BY draft-ietf-isis-mi
>=20
> L2VPN Working Group, RTG Area
>   draft-henderickx-l2vpn-vpls-multihoming POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-multihoming
>   draft-kompella-l2vpn-vpls-multihoming POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-multihoming
>   draft-pdutta-l2vpn-vpls-ldp-mac-opt POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-ldp-mac-opt
>   draft-pkwok-l2vpn-vpls-macflush-ld POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-macflush-ld
>   draft-sajassi-l2vpn-vpls-pbb-interop POTENTIALLY REPLACED BY =
draft-ietf-l2vpn-vpls-pbb-interop
>=20
> MANET Working Group, RTG Area
>   draft-sratliff-manet-dlep POTENTIALLY REPLACED BY =
draft-ietf-manet-dlep
>=20
> MPLS Working Group, RTG Area
>   draft-frost-mpls-loss-delay POTENTIALLY REPLACED BY =
draft-ietf-mpls-loss-delay
>   draft-frost-mpls-tp-loss-delay-profile POTENTIALLY REPLACED BY =
draft-ietf-mpls-tp-loss-delay-profile
>=20
> OSPF Working Group, RTG Area
>   draft-acee-ospf-multi-instance POTENTIALLY REPLACED BY =
draft-ietf-ospf-multi-instance
>   draft-acee-ospf-transport-instance POTENTIALLY REPLACED BY =
draft-ietf-ospf-transport-instance
>   draft-hartman-ospf-analysis POTENTIALLY REPLACED BY =
draft-ietf-ospf-analysis
>   draft-nguyen-ospf-lls POTENTIALLY REPLACED BY draft-ietf-ospf-lls
>   draft-ogier-ospf-dbex-opt POTENTIALLY REPLACED BY =
draft-ietf-ospf-dbex-opt
>   draft-venkata-ospf-dynamic-hostname POTENTIALLY REPLACED BY =
draft-ietf-ospf-dynamic-hostname
>=20
> PCE Working Group, RTG Area
>   draft-bradford-pce-path-key POTENTIALLY REPLACED BY =
draft-ietf-pce-path-key
>   draft-farrel-pce-vendor-constraints POTENTIALLY REPLACED BY =
draft-ietf-pce-vendor-constraints
>   draft-king-pce-inter-area-as-applicability POTENTIALLY REPLACED BY =
draft-ietf-pce-inter-area-as-applicability
>   draft-kkoushik-pce-pcep-mib POTENTIALLY REPLACED BY =
draft-ietf-pce-pcep-mib
>   draft-lee-pce-wson-routing-wavelength POTENTIALLY REPLACED BY =
draft-ietf-pce-wson-routing-wavelength
>   draft-leroux-pce-of POTENTIALLY REPLACED BY draft-ietf-pce-of
>   draft-margaria-pce-gmpls-pcep-extensions POTENTIALLY REPLACED BY =
draft-ietf-pce-gmpls-pcep-extensions
>   draft-oki-pce-inter-layer-ext POTENTIALLY REPLACED BY =
draft-ietf-pce-inter-layer-ext
>   draft-otani-pce-gmpls-aps-req POTENTIALLY REPLACED BY =
draft-ietf-pce-gmpls-aps-req
>   draft-sivabalan-pce-dste POTENTIALLY REPLACED BY draft-ietf-pce-dste
>   draft-vasseur-pce-monitoring POTENTIALLY REPLACED BY =
draft-ietf-pce-monitoring
>   draft-yasukawa-pce-p2mp-app POTENTIALLY REPLACED BY =
draft-ietf-pce-p2mp-app
>   draft-yasukawa-pce-p2mp-req POTENTIALLY REPLACED BY =
draft-ietf-pce-p2mp-req
>   draft-yasukawa-pce-vpn-req POTENTIALLY REPLACED BY =
draft-ietf-pce-vpn-req
>=20
> PWE3 Working Group, RTG Area
>   draft-lm-pwe3-mpls-tp-gal-in-pw POTENTIALLY REPLACED BY =
draft-ietf-pwe3-mpls-tp-gal-in-pw
>=20
> ROLL Working Group, RTG Area
>   draft-dt-roll-p2p-rpl POTENTIALLY REPLACED BY =
draft-ietf-roll-p2p-rpl
>   draft-gnawali-roll-minrank-hysteresis-of POTENTIALLY REPLACED BY =
draft-ietf-roll-minrank-hysteresis-of
>   draft-levis-roll-trickle POTENTIALLY REPLACED BY =
draft-ietf-roll-trickle
>   draft-tsao-roll-security-framework POTENTIALLY REPLACED BY =
draft-ietf-roll-security-framework
>=20
> SIDR Working Group, RTG Area
>   draft-huston-sidr-bogons POTENTIALLY REPLACED BY =
draft-ietf-sidr-bogons
>   draft-huston-sidr-keyroll POTENTIALLY REPLACED BY =
draft-ietf-sidr-keyroll
>   draft-huston-sidr-repos-struct POTENTIALLY REPLACED BY =
draft-ietf-sidr-repos-struct
>   draft-huston-sidr-roa-validation POTENTIALLY REPLACED BY =
draft-ietf-sidr-roa-validation
>   draft-huston-sidr-rpki-algs POTENTIALLY REPLACED BY =
draft-ietf-sidr-rpki-algs
>   draft-kisteleki-sidr-rpsl-sig POTENTIALLY REPLACED BY =
draft-ietf-sidr-rpsl-sig
>   draft-manderson-sidr-usecases POTENTIALLY REPLACED BY =
draft-ietf-sidr-usecases
>   draft-pmohapat-sidr-origin-validation-signaling POTENTIALLY REPLACED =
BY draft-ietf-sidr-origin-validation-signaling
>   draft-pmohapat-sidr-pfx-validate POTENTIALLY REPLACED BY =
draft-ietf-sidr-pfx-validate
>   draft-weiler-sidr-publication POTENTIALLY REPLACED BY =
draft-ietf-sidr-publication
>=20
> -----------------------------------------------------------------
> SEC Area
> -----------------------------------------------------------------
> DKIM Working Group, SEC Area
>   draft-lindsey-dkim-mailinglists POTENTIALLY REPLACED BY =
draft-ietf-dkim-mailinglists
>=20
> HOKEY Working Group, SEC Area
>   draft-wu-hokey-rfc5296bis POTENTIALLY REPLACED BY =
draft-ietf-hokey-rfc5296bis
>=20
> PKIX Working Group, SEC Area
>   draft-cooper-pkix-rfc2560bis POTENTIALLY REPLACED BY =
draft-ietf-pkix-rfc2560bis
>   draft-cooper-pkix-rfc5280-clarifications POTENTIALLY REPLACED BY =
draft-ietf-pkix-rfc5280-clarifications
>   draft-santesson-pkix-certimage POTENTIALLY REPLACED BY =
draft-ietf-pkix-certimage
>=20
> TLS Working Group, SEC Area
>   draft-rescorla-tls-suiteb POTENTIALLY REPLACED BY =
draft-ietf-tls-suiteb
>   draft-seggelmann-tls-dtls-heartbeat POTENTIALLY REPLACED BY =
draft-ietf-tls-dtls-heartbeat
>=20
> -----------------------------------------------------------------
> TSV Area
> -----------------------------------------------------------------
> BEHAVE Working Group, TSV Area
>   draft-liu-behave-ftp64 POTENTIALLY REPLACED BY =
draft-ietf-behave-ftp64
>=20
> CONEX Working Group, TSV Area
>   draft-moncaster-conex-concepts-uses POTENTIALLY REPLACED BY =
draft-ietf-conex-concepts-uses
>=20
> DCCP Working Group, TSV Area
>   draft-renker-dccp-tfrc-rtt-option POTENTIALLY REPLACED BY =
draft-ietf-dccp-tfrc-rtt-option
>=20
> IPPM Working Group, TSV Area
>   draft-geib-ippm-metrictest POTENTIALLY REPLACED BY =
draft-ietf-ippm-metrictest
>=20
> MPTCP Working Group, TSV Area
>   draft-scharf-mptcp-api POTENTIALLY REPLACED BY draft-ietf-mptcp-api
>=20
> NFSV4 Working Group, TSV Area
>   draft-alexrn-nfsv4-ipv6 POTENTIALLY REPLACED BY =
draft-ietf-nfsv4-ipv6
>   draft-eisler-nfsv4-minorversion-2-requirements POTENTIALLY REPLACED =
BY draft-ietf-nfsv4-minorversion-2-requirements
>   draft-faibish-nfsv4-pnfs-access-permissions-check POTENTIALLY =
REPLACED BY draft-ietf-nfsv4-pnfs-access-permissions-check
>=20
> PCN Working Group, TSV Area
>   draft-karagiannis-pcn-signaling-requirements POTENTIALLY REPLACED BY =
draft-ietf-pcn-signaling-requirements
>=20
> TCPM Working Group, TSV Area
>   draft-hkchu-tcpm-initcwnd POTENTIALLY REPLACED BY =
draft-ietf-tcpm-initcwnd
>=20
> -----------------------------------------------------------------
> Potential Inconsistencies
> -----------------------------------------------------------------
> draft-ietf-6lowpan-nd may replace one or more of 2 individual IDs - =
check this
> draft-ietf-avt-rtp-gsm-hr may replace one or more of 3 individual IDs =
- check this
> draft-ietf-avt-rtp-svc may replace one or more of 2 individual IDs - =
check this
> draft-ietf-bmwg-ipflow-meth may replace one or more of 2 individual =
IDs - check this
> draft-ietf-decade-survey may replace one or more of 2 individual IDs - =
check this
> draft-ietf-dhc-dhcpv4-bulk-leasequery may replace one or more of 2 =
individual IDs - check this
> draft-ietf-forces-tmlsp may replace one or more of 2 individual IDs - =
check this
> draft-ietf-ipfix-biflow may replace one or more of 2 individual IDs - =
check this
> draft-ietf-l2tpext-tdm may replace one or more of 2 individual IDs - =
check this
> draft-ietf-l2vpn-vpls-multihoming may replace one or more of 2 =
individual IDs - check this
> draft-ietf-mpls-tp-fault may replace one or more of 2 individual IDs - =
check this
> draft-ietf-netconf-monitoring may replace one or more of 2 individual =
IDs - check this
> draft-ietf-netlmm-lma-discovery may replace one or more of 2 =
individual IDs - check this
> draft-ietf-netlmm-mip-interactions may replace one or more of 2 =
individual IDs - check this
> draft-ietf-sip-saml may replace one or more of 2 individual IDs - =
check this
> draft-ietf-sipping-service-identification may replace one or more of 2 =
individual IDs - check this
> draft-ietf-trill-rbridge-arch may replace one or more of 2 individual =
IDs - check this
>=20
>=20


--Apple-Mail-1-753344173
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDExMTEwMTA0MFowIwYJKoZIhvcNAQkE
MRYEFPi+gLj07YIfYAAchAiDCnQyHspNMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AKqJqrLPRIWjBdPKZpljM4vfvqVGw/RSiTpJV+sqnJSxK3te1PKTtrXzzoB2BUTfUfUSHf2bEdst
uausQQyQK0UFs5zLUQ7rCnBIKLPjKRDStaB4d2udjqDABiwMplOXqvDq/d4EYsRSFeQX3IiDlxa2
xijePIQhDTeeRs9T3+bPme3fZulLGVQ2lGiNFHtcFsfsEgTt+eHkEYcs0/t+LqsXZQJLF+hwBRb5
oXvbVDf3pArv94/WhDGO1E2vby4XfRYKYT5HMyRiTEc2jfSyIhijluQtwc+fMZG6zSYPK8+vZ28J
Ww1Ul4RMAZ2TkGhI7ZFew/ApmbHq0qdut2BGYdoAAAAAAAA=

--Apple-Mail-1-753344173--

From keith.drage@alcatel-lucent.com  Tue Jan 11 07:46:24 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 5AE3B3A6A47 for <wgchairs@core3.amsl.com>; Tue, 11 Jan 2011 07:46:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.351
X-Spam-Level: 
X-Spam-Status: No, score=-103.351 tagged_above=-999 required=5 tests=[AWL=-1.702, 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 HKhreoJEE0DP for <wgchairs@core3.amsl.com>; Tue, 11 Jan 2011 07:46:22 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id 3195B3A67FA for <wgchairs@ietf.org>; Tue, 11 Jan 2011 07:46:22 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p0BFmY7T003023 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 11 Jan 2011 16:48:38 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Tue, 11 Jan 2011 16:48:35 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Eggert Lars <lars.eggert@nokia.com>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Date: Tue, 11 Jan 2011 16:48:34 +0100
Subject: RE: latest missing replaced-by information
Thread-Topic: latest missing replaced-by information
Thread-Index: AcuwxkYFeyYpxjhDQY2OychaKLY6lwA3OARQ
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21E5E9C7E@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <D2906EA5-2DAB-44C3-A3C7-86598C0CBF29@nokia.com>
In-Reply-To: <D2906EA5-2DAB-44C3-A3C7-86598C0CBF29@nokia.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.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: Tue, 11 Jan 2011 15:46:24 -0000

I don't understand these two lines:

draft-ietf-avt-rtp-gsm-hr may replace one or more of 3 individual IDs - che=
ck this
draft-ietf-avt-rtp-svc may replace one or more of 2 individual IDs - check =
this

Yes they do replace exactly this number of individual drafts, and exactly t=
hat number are already listed in the datatracker under the replaced by info=
rmation.

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org
> [mailto:wgchairs-bounces@ietf.org] On Behalf Of Eggert Lars
> Sent: Monday, January 10, 2011 12:58 PM
> To: wgchairs@ietf.org
> Subject: latest missing replaced-by information
>
> Hi,
>
> here's yet another installment in the series of reports on
> potentially missing "replaced-by" relationships in the IETF
> datatracker.
>
> WG chairs are encouraged to check whether these are accurate
> for their WGs, and if so, send a ticket to the secretariat
> instructing them to "record in the database that draft X
> replaced draft Y".
>
> As always, double-check before reporting to the secretariat.
> Also, see list of possible inconsistencies at the end of the report.
>
> (Note that the IPR disclosure search tool uses these
> replaced-by relationships, so keeping them up-to-date is
> actually useful and not just WG hygiene.)
>
> Lars
>
> -----------------------------------------------------------------
> APP Area
> -----------------------------------------------------------------
> EAI Working Group, APP Area
>    draft-yao-eai-rfc5336bis POTENTIALLY REPLACED BY
> draft-ietf-eai-rfc5336bis
>
> SIEVE Working Group, APP Area
>    draft-george-sieve-autoreply POTENTIALLY REPLACED BY
> draft-ietf-sieve-autoreply
>    draft-george-sieve-notify-presence POTENTIALLY REPLACED BY
> draft-ietf-sieve-notify-presence
>
> -----------------------------------------------------------------
> INT Area
> -----------------------------------------------------------------
> 6MAN Working Group, INT Area
>    draft-arifumi-6man-rfc3484-revise POTENTIALLY REPLACED BY
> draft-ietf-6man-rfc3484-revise
>    draft-carpenter-6man-flow-update POTENTIALLY REPLACED BY
> draft-ietf-6man-flow-update
>    draft-fujisaki-6man-addr-select-opt POTENTIALLY REPLACED
> BY draft-ietf-6man-addr-select-opt
>    draft-joshi-6man-neighbor-inform POTENTIALLY REPLACED BY
> draft-ietf-6man-neighbor-inform
>
> ANCP Working Group, INT Area
>    draft-lefaucheur-ancp-mc-extensions POTENTIALLY REPLACED
> BY draft-ietf-ancp-mc-extensions
>
> AUTOCONF Working Group, INT Area
>    draft-baccelli-autoconf-adhoc-addr-model POTENTIALLY
> REPLACED BY draft-ietf-autoconf-adhoc-addr-model
>
> CSI Working Group, INT Area
>    draft-jiang-csi-dhcpv6-cga-ps POTENTIALLY REPLACED BY
> draft-ietf-csi-dhcpv6-cga-ps
>    draft-rgaglian-csi-send-name-type-registry POTENTIALLY
> REPLACED BY draft-ietf-csi-send-name-type-registry
>
> DHC Working Group, INT Area
>    draft-miles-dhc-dhcpv6-ldra POTENTIALLY REPLACED BY
> draft-ietf-dhc-dhcpv6-ldra
>
> DNSEXT Working Group, INT Area
>    draft-dolmatov-dnsext-dnssec-gost POTENTIALLY REPLACED BY
> draft-ietf-dnsext-dnssec-gost
>    draft-wang-dnsext-newzone-notify POTENTIALLY REPLACED BY
> draft-ietf-dnsext-newzone-notify
>
> HIP Working Group, INT Area
>    draft-camarillo-hip-via POTENTIALLY REPLACED BY draft-ietf-hip-via
>    draft-henderson-hip-rfc5206-bis POTENTIALLY REPLACED BY
> draft-ietf-hip-rfc5206-bis
>    draft-jokela-hip-rfc5202-bis POTENTIALLY REPLACED BY
> draft-ietf-hip-rfc5202-bis
>    draft-keranen-hip-native-nat-traversal POTENTIALLY
> REPLACED BY draft-ietf-hip-native-nat-traversal
>    draft-keranen-hip-over-hip POTENTIALLY REPLACED BY
> draft-ietf-hip-over-hip
>    draft-keranen-hip-reload-instance POTENTIALLY REPLACED BY
> draft-ietf-hip-reload-instance
>    draft-moskowitz-hip-rfc4423-bis POTENTIALLY REPLACED BY
> draft-ietf-hip-rfc4423-bis
>    draft-moskowitz-hip-rfc5201-bis POTENTIALLY REPLACED BY
> draft-ietf-hip-rfc5201-bis
>    draft-nikander-hip-hiccups POTENTIALLY REPLACED BY
> draft-ietf-hip-hiccups
>
> LISP Working Group, INT Area
>    draft-schudel-lisp-mib POTENTIALLY REPLACED BY draft-ietf-lisp-mib
>
> NETEXT Working Group, INT Area
>    draft-korhonen-netext-redirect POTENTIALLY REPLACED BY
> draft-ietf-netext-redirect
>    draft-krishnan-netext-pmip-lr POTENTIALLY REPLACED BY
> draft-ietf-netext-pmip-lr
>    draft-melia-netext-logical-interface-support POTENTIALLY
> REPLACED BY draft-ietf-netext-logical-interface-support
>
> SAVI Working Group, INT Area
>    draft-vogt-savi-framework POTENTIALLY REPLACED BY
> draft-ietf-savi-framework
>
> SOFTWIRE Working Group, INT Area
>    draft-guo-softwire-6rd-radius-attrib POTENTIALLY REPLACED
> BY draft-ietf-softwire-6rd-radius-attrib
>    draft-maglione-softwire-dslite-radius-ext POTENTIALLY
> REPLACED BY draft-ietf-softwire-dslite-radius-ext
>
> -----------------------------------------------------------------
> OPS Area
> -----------------------------------------------------------------
> BMWG Working Group, OPS Area
>    draft-asati-bmwg-reset POTENTIALLY REPLACED BY
> draft-ietf-bmwg-reset
>    draft-janovak-bmwg-ipflow-meth POTENTIALLY REPLACED BY
> draft-ietf-bmwg-ipflow-meth
>    draft-novak-bmwg-ipflow-meth POTENTIALLY REPLACED BY
> draft-ietf-bmwg-ipflow-meth
>
> DIME Working Group, OPS Area
>    draft-zorn-dime-rfc4005bis POTENTIALLY REPLACED BY
> draft-ietf-dime-rfc4005bis
>
> EMAN Working Group, OPS Area
>    draft-parello-eman-energy-aware-mib POTENTIALLY REPLACED
> BY draft-ietf-eman-energy-aware-mib
>
> GROW Working Group, OPS Area
>    draft-dimitri-grow-rss POTENTIALLY REPLACED BY draft-ietf-grow-rss
>    draft-manderson-grow-geomrt POTENTIALLY REPLACED BY
> draft-ietf-grow-geomrt
>
> IPFIX Working Group, OPS Area
>    draft-boschi-ipfix-anon POTENTIALLY REPLACED BY
> draft-ietf-ipfix-anon
>    draft-boschi-ipfix-exporting-type POTENTIALLY REPLACED BY
> draft-ietf-ipfix-exporting-type
>    draft-claise-ipfix-export-per-sctp-stream POTENTIALLY
> REPLACED BY draft-ietf-ipfix-export-per-sctp-stream
>    draft-gupta-ipfix-reliability-template-ext POTENTIALLY
> REPLACED BY draft-ietf-ipfix-reliability-template-ext
>    draft-trammell-ipfix-file POTENTIALLY REPLACED BY
> draft-ietf-ipfix-file
>
> MBONED Working Group, OPS Area
>    draft-asaeda-mboned-mtrace-v2 POTENTIALLY REPLACED BY
> draft-ietf-mboned-mtrace-v2
>    draft-asaeda-mboned-session-announcement-req POTENTIALLY
> REPLACED BY draft-ietf-mboned-session-announcement-req
>    draft-venaas-mboned-ssmping POTENTIALLY REPLACED BY
> draft-ietf-mboned-ssmping
>
> NETCONF Working Group, OPS Area
>    draft-bierman-netconf-access-control POTENTIALLY REPLACED
> BY draft-ietf-netconf-access-control
>    draft-bierman-netconf-with-defaults POTENTIALLY REPLACED
> BY draft-ietf-netconf-with-defaults
>    draft-chisholm-netconf-monitoring POTENTIALLY REPLACED BY
> draft-ietf-netconf-monitoring
>
> NETMOD Working Group, OPS Area
>    draft-bierman-netmod-yang-usage POTENTIALLY REPLACED BY
> draft-ietf-netmod-yang-usage
>    draft-schoenw-netmod-yang-types POTENTIALLY REPLACED BY
> draft-ietf-netmod-yang-types
>    draft-shafer-netmod-arch POTENTIALLY REPLACED BY
> draft-ietf-netmod-arch
>
> OPSAWG Working Group, OPS Area
>    draft-mizrahi-opsawg-oam-overview POTENTIALLY REPLACED BY
> draft-ietf-opsawg-oam-overview
>
> OPSEC Working Group, OPS Area
>    draft-gont-opsec-icmp-filtering POTENTIALLY REPLACED BY
> draft-ietf-opsec-icmp-filtering
>    draft-gont-opsec-ip-security POTENTIALLY REPLACED BY
> draft-ietf-opsec-ip-security
>
> RADEXT Working Group, OPS Area
>    draft-dekok-radext-dtls POTENTIALLY REPLACED BY
> draft-ietf-radext-dtls
>    draft-dekok-radext-tcp-transport POTENTIALLY REPLACED BY
> draft-ietf-radext-tcp-transport
>    draft-lourdelet-radext-ipv6-access POTENTIALLY REPLACED BY
> draft-ietf-radext-ipv6-access
>    draft-nelson-radext-crypto-agility-requirements
> POTENTIALLY REPLACED BY draft-ietf-radext-crypto-agility-requirements
>    draft-tiwari-radext-tunnel-type POTENTIALLY REPLACED BY
> draft-ietf-radext-tunnel-type
>
> V6OPS Working Group, OPS Area
>    draft-rgaglian-v6ops-v6inixp POTENTIALLY REPLACED BY
> draft-ietf-v6ops-v6inixp
>    draft-vandevelde-v6ops-ra-guard POTENTIALLY REPLACED BY
> draft-ietf-v6ops-ra-guard
>
> -----------------------------------------------------------------
> RAI Area
> -----------------------------------------------------------------
> ATOCA Working Group, RAI Area
>    draft-rosen-atoca-cap POTENTIALLY REPLACED BY draft-ietf-atoca-cap
>    draft-schulzrinne-atoca-requirements POTENTIALLY REPLACED
> BY draft-ietf-atoca-requirements
>
> BLISS Working Group, RAI Area
>    draft-elwell-bliss-ach-analysis POTENTIALLY REPLACED BY
> draft-ietf-bliss-ach-analysis
>    draft-poetzl-bliss-call-completion POTENTIALLY REPLACED BY
> draft-ietf-bliss-call-completion
>    draft-procter-bliss-call-park-extension POTENTIALLY
> REPLACED BY draft-ietf-bliss-call-park-extension
>    draft-rosenberg-bliss-problem-statement POTENTIALLY
> REPLACED BY draft-ietf-bliss-problem-statement
>
> CUSS Working Group, RAI Area
>    draft-johnston-cuss-sip-uui-reqs POTENTIALLY REPLACED BY
> draft-ietf-cuss-sip-uui-reqs
>
> DRINKS Working Group, RAI Area
>    draft-channabasappa-drinks-usecases-requirements
> POTENTIALLY REPLACED BY draft-ietf-drinks-usecases-requirements
>
> ECRIT Working Group, RAI Area
>    draft-barnes-ecrit-rough-loc POTENTIALLY REPLACED BY
> draft-ietf-ecrit-rough-loc
>    draft-rosen-ecrit-additional-data POTENTIALLY REPLACED BY
> draft-ietf-ecrit-additional-data
>    draft-rosen-ecrit-data-only-ea POTENTIALLY REPLACED BY
> draft-ietf-ecrit-data-only-ea
>    draft-schulzrinne-ecrit-location-hiding-req POTENTIALLY
> REPLACED BY draft-ietf-ecrit-location-hiding-req
>    draft-schulzrinne-ecrit-lost-sync POTENTIALLY REPLACED BY
> draft-ietf-ecrit-lost-sync
>    draft-schulzrinne-ecrit-psap-callback POTENTIALLY REPLACED
> BY draft-ietf-ecrit-psap-callback
>    draft-schulzrinne-ecrit-unauthenticated-access POTENTIALLY
> REPLACED BY draft-ietf-ecrit-unauthenticated-access
>    draft-taylor-ecrit-security-threats POTENTIALLY REPLACED
> BY draft-ietf-ecrit-security-threats
>    draft-tschofenig-ecrit-trustworthy-location POTENTIALLY
> REPLACED BY draft-ietf-ecrit-trustworthy-location
>    draft-winterbottom-ecrit-specifying-holes POTENTIALLY
> REPLACED BY draft-ietf-ecrit-specifying-holes
>
> GEOPRIV Working Group, RAI Area
>    draft-mayrhofer-geopriv-geo-uri POTENTIALLY REPLACED BY
> draft-ietf-geopriv-geo-uri
>
> P2PSIP Working Group, RAI Area
>    draft-bryan-p2psip-reload POTENTIALLY REPLACED BY
> draft-ietf-p2psip-reload
>
> SPEERMINT Working Group, RAI Area
>    draft-meyer-speermint-reqs-and-terminology POTENTIALLY
> REPLACED BY draft-ietf-speermint-reqs-and-terminology
>    draft-niccolini-speermint-voipthreats POTENTIALLY REPLACED
> BY draft-ietf-speermint-voipthreats
>
> XCON Working Group, RAI Area
>    draft-barnes-xcon-ccmp POTENTIALLY REPLACED BY draft-ietf-xcon-ccmp
>    draft-barnes-xcon-examples POTENTIALLY REPLACED BY
> draft-ietf-xcon-examples
>
> XMPP Working Group, RAI Area
>    draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna
>
> -----------------------------------------------------------------
> RTG Area
> -----------------------------------------------------------------
> CCAMP Working Group, RTG Area
>    draft-berger-ccamp-assoc-info POTENTIALLY REPLACED BY
> draft-ietf-ccamp-assoc-info
>    draft-berger-ccamp-attribute-bnf POTENTIALLY REPLACED BY
> draft-ietf-ccamp-attribute-bnf
>    draft-bernstein-ccamp-wson-signaling POTENTIALLY REPLACED
> BY draft-ietf-ccamp-wson-signaling
>    draft-kern-ccamp-rsvp-te-sdh-otn-oam-ext POTENTIALLY
> REPLACED BY draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext
>    draft-lee-ccamp-wson-signal-compatibility-ospf POTENTIALLY
> REPLACED BY draft-ietf-ccamp-wson-signal-compatibility-ospf
>    draft-li-ccamp-lmp-behavior-negotiation POTENTIALLY
> REPLACED BY draft-ietf-ccamp-lmp-behavior-negotiation
>    draft-sun-ccamp-dpm POTENTIALLY REPLACED BY draft-ietf-ccamp-dpm
>    draft-takacs-ccamp-asymm-bw-bidir-lsps-bis POTENTIALLY
> REPLACED BY draft-ietf-ccamp-asymm-bw-bidir-lsps-bis
>    draft-zhang-ccamp-gmpls-g709-framework POTENTIALLY
> REPLACED BY draft-ietf-ccamp-gmpls-g709-framework
>
> FORCES Working Group, RTG Area
>    draft-hadi-forces-sctptml POTENTIALLY REPLACED BY
> draft-ietf-forces-sctptml
>    draft-haleplidis-forces-implementation-experience
> POTENTIALLY REPLACED BY draft-ietf-forces-implementation-experience
>
> IDR Working Group, RTG Area
>    draft-uttaro-idr-add-paths-guidelines POTENTIALLY REPLACED
> BY draft-ietf-idr-add-paths-guidelines
>
> ISIS Working Group, RTG Area
>    draft-chopps-isis-bfd-tlv POTENTIALLY REPLACED BY
> draft-ietf-isis-bfd-tlv
>    draft-ginsberg-isis-genapp POTENTIALLY REPLACED BY
> draft-ietf-isis-genapp
>    draft-previdi-isis-mi POTENTIALLY REPLACED BY draft-ietf-isis-mi
>
> L2VPN Working Group, RTG Area
>    draft-henderickx-l2vpn-vpls-multihoming POTENTIALLY
> REPLACED BY draft-ietf-l2vpn-vpls-multihoming
>    draft-kompella-l2vpn-vpls-multihoming POTENTIALLY REPLACED
> BY draft-ietf-l2vpn-vpls-multihoming
>    draft-pdutta-l2vpn-vpls-ldp-mac-opt POTENTIALLY REPLACED
> BY draft-ietf-l2vpn-vpls-ldp-mac-opt
>    draft-pkwok-l2vpn-vpls-macflush-ld POTENTIALLY REPLACED BY
> draft-ietf-l2vpn-vpls-macflush-ld
>    draft-sajassi-l2vpn-vpls-pbb-interop POTENTIALLY REPLACED
> BY draft-ietf-l2vpn-vpls-pbb-interop
>
> MANET Working Group, RTG Area
>    draft-sratliff-manet-dlep POTENTIALLY REPLACED BY
> draft-ietf-manet-dlep
>
> MPLS Working Group, RTG Area
>    draft-frost-mpls-loss-delay POTENTIALLY REPLACED BY
> draft-ietf-mpls-loss-delay
>    draft-frost-mpls-tp-loss-delay-profile POTENTIALLY
> REPLACED BY draft-ietf-mpls-tp-loss-delay-profile
>
> OSPF Working Group, RTG Area
>    draft-acee-ospf-multi-instance POTENTIALLY REPLACED BY
> draft-ietf-ospf-multi-instance
>    draft-acee-ospf-transport-instance POTENTIALLY REPLACED BY
> draft-ietf-ospf-transport-instance
>    draft-hartman-ospf-analysis POTENTIALLY REPLACED BY
> draft-ietf-ospf-analysis
>    draft-nguyen-ospf-lls POTENTIALLY REPLACED BY draft-ietf-ospf-lls
>    draft-ogier-ospf-dbex-opt POTENTIALLY REPLACED BY
> draft-ietf-ospf-dbex-opt
>    draft-venkata-ospf-dynamic-hostname POTENTIALLY REPLACED
> BY draft-ietf-ospf-dynamic-hostname
>
> PCE Working Group, RTG Area
>    draft-bradford-pce-path-key POTENTIALLY REPLACED BY
> draft-ietf-pce-path-key
>    draft-farrel-pce-vendor-constraints POTENTIALLY REPLACED
> BY draft-ietf-pce-vendor-constraints
>    draft-king-pce-inter-area-as-applicability POTENTIALLY
> REPLACED BY draft-ietf-pce-inter-area-as-applicability
>    draft-kkoushik-pce-pcep-mib POTENTIALLY REPLACED BY
> draft-ietf-pce-pcep-mib
>    draft-lee-pce-wson-routing-wavelength POTENTIALLY REPLACED
> BY draft-ietf-pce-wson-routing-wavelength
>    draft-leroux-pce-of POTENTIALLY REPLACED BY draft-ietf-pce-of
>    draft-margaria-pce-gmpls-pcep-extensions POTENTIALLY
> REPLACED BY draft-ietf-pce-gmpls-pcep-extensions
>    draft-oki-pce-inter-layer-ext POTENTIALLY REPLACED BY
> draft-ietf-pce-inter-layer-ext
>    draft-otani-pce-gmpls-aps-req POTENTIALLY REPLACED BY
> draft-ietf-pce-gmpls-aps-req
>    draft-sivabalan-pce-dste POTENTIALLY REPLACED BY
> draft-ietf-pce-dste
>    draft-vasseur-pce-monitoring POTENTIALLY REPLACED BY
> draft-ietf-pce-monitoring
>    draft-yasukawa-pce-p2mp-app POTENTIALLY REPLACED BY
> draft-ietf-pce-p2mp-app
>    draft-yasukawa-pce-p2mp-req POTENTIALLY REPLACED BY
> draft-ietf-pce-p2mp-req
>    draft-yasukawa-pce-vpn-req POTENTIALLY REPLACED BY
> draft-ietf-pce-vpn-req
>
> PWE3 Working Group, RTG Area
>    draft-lm-pwe3-mpls-tp-gal-in-pw POTENTIALLY REPLACED BY
> draft-ietf-pwe3-mpls-tp-gal-in-pw
>
> ROLL Working Group, RTG Area
>    draft-dt-roll-p2p-rpl POTENTIALLY REPLACED BY
> draft-ietf-roll-p2p-rpl
>    draft-gnawali-roll-minrank-hysteresis-of POTENTIALLY
> REPLACED BY draft-ietf-roll-minrank-hysteresis-of
>    draft-levis-roll-trickle POTENTIALLY REPLACED BY
> draft-ietf-roll-trickle
>    draft-tsao-roll-security-framework POTENTIALLY REPLACED BY
> draft-ietf-roll-security-framework
>
> SIDR Working Group, RTG Area
>    draft-huston-sidr-bogons POTENTIALLY REPLACED BY
> draft-ietf-sidr-bogons
>    draft-huston-sidr-keyroll POTENTIALLY REPLACED BY
> draft-ietf-sidr-keyroll
>    draft-huston-sidr-repos-struct POTENTIALLY REPLACED BY
> draft-ietf-sidr-repos-struct
>    draft-huston-sidr-roa-validation POTENTIALLY REPLACED BY
> draft-ietf-sidr-roa-validation
>    draft-huston-sidr-rpki-algs POTENTIALLY REPLACED BY
> draft-ietf-sidr-rpki-algs
>    draft-kisteleki-sidr-rpsl-sig POTENTIALLY REPLACED BY
> draft-ietf-sidr-rpsl-sig
>    draft-manderson-sidr-usecases POTENTIALLY REPLACED BY
> draft-ietf-sidr-usecases
>    draft-pmohapat-sidr-origin-validation-signaling
> POTENTIALLY REPLACED BY draft-ietf-sidr-origin-validation-signaling
>    draft-pmohapat-sidr-pfx-validate POTENTIALLY REPLACED BY
> draft-ietf-sidr-pfx-validate
>    draft-weiler-sidr-publication POTENTIALLY REPLACED BY
> draft-ietf-sidr-publication
>
> -----------------------------------------------------------------
> SEC Area
> -----------------------------------------------------------------
> DKIM Working Group, SEC Area
>    draft-lindsey-dkim-mailinglists POTENTIALLY REPLACED BY
> draft-ietf-dkim-mailinglists
>
> HOKEY Working Group, SEC Area
>    draft-wu-hokey-rfc5296bis POTENTIALLY REPLACED BY
> draft-ietf-hokey-rfc5296bis
>
> PKIX Working Group, SEC Area
>    draft-cooper-pkix-rfc2560bis POTENTIALLY REPLACED BY
> draft-ietf-pkix-rfc2560bis
>    draft-cooper-pkix-rfc5280-clarifications POTENTIALLY
> REPLACED BY draft-ietf-pkix-rfc5280-clarifications
>    draft-santesson-pkix-certimage POTENTIALLY REPLACED BY
> draft-ietf-pkix-certimage
>
> TLS Working Group, SEC Area
>    draft-rescorla-tls-suiteb POTENTIALLY REPLACED BY
> draft-ietf-tls-suiteb
>    draft-seggelmann-tls-dtls-heartbeat POTENTIALLY REPLACED
> BY draft-ietf-tls-dtls-heartbeat
>
> -----------------------------------------------------------------
> TSV Area
> -----------------------------------------------------------------
> BEHAVE Working Group, TSV Area
>    draft-liu-behave-ftp64 POTENTIALLY REPLACED BY
> draft-ietf-behave-ftp64
>
> CONEX Working Group, TSV Area
>    draft-moncaster-conex-concepts-uses POTENTIALLY REPLACED
> BY draft-ietf-conex-concepts-uses
>
> DCCP Working Group, TSV Area
>    draft-renker-dccp-tfrc-rtt-option POTENTIALLY REPLACED BY
> draft-ietf-dccp-tfrc-rtt-option
>
> IPPM Working Group, TSV Area
>    draft-geib-ippm-metrictest POTENTIALLY REPLACED BY
> draft-ietf-ippm-metrictest
>
> MPTCP Working Group, TSV Area
>    draft-scharf-mptcp-api POTENTIALLY REPLACED BY draft-ietf-mptcp-api
>
> NFSV4 Working Group, TSV Area
>    draft-alexrn-nfsv4-ipv6 POTENTIALLY REPLACED BY
> draft-ietf-nfsv4-ipv6
>    draft-eisler-nfsv4-minorversion-2-requirements POTENTIALLY
> REPLACED BY draft-ietf-nfsv4-minorversion-2-requirements
>    draft-faibish-nfsv4-pnfs-access-permissions-check
> POTENTIALLY REPLACED BY draft-ietf-nfsv4-pnfs-access-permissions-check
>
> PCN Working Group, TSV Area
>    draft-karagiannis-pcn-signaling-requirements POTENTIALLY
> REPLACED BY draft-ietf-pcn-signaling-requirements
>
> TCPM Working Group, TSV Area
>    draft-hkchu-tcpm-initcwnd POTENTIALLY REPLACED BY
> draft-ietf-tcpm-initcwnd
>
> -----------------------------------------------------------------
> Potential Inconsistencies
> -----------------------------------------------------------------
> draft-ietf-6lowpan-nd may replace one or more of 2 individual
> IDs - check this draft-ietf-avt-rtp-gsm-hr may replace one or
> more of 3 individual IDs - check this draft-ietf-avt-rtp-svc
> may replace one or more of 2 individual IDs - check this
> draft-ietf-bmwg-ipflow-meth may replace one or more of 2
> individual IDs - check this draft-ietf-decade-survey may
> replace one or more of 2 individual IDs - check this
> draft-ietf-dhc-dhcpv4-bulk-leasequery may replace one or more
> of 2 individual IDs - check this draft-ietf-forces-tmlsp may
> replace one or more of 2 individual IDs - check this
> draft-ietf-ipfix-biflow may replace one or more of 2
> individual IDs - check this draft-ietf-l2tpext-tdm may
> replace one or more of 2 individual IDs - check this
> draft-ietf-l2vpn-vpls-multihoming may replace one or more of
> 2 individual IDs - check this draft-ietf-mpls-tp-fault may
> replace one or more of 2 individual IDs - check this
> draft-ietf-netconf-monitoring may replace one or more of 2
> individual IDs - check this draft-ietf-netlmm-lma-discovery
> may replace one or more of 2 individual IDs - check this
> draft-ietf-netlmm-mip-interactions may replace one or more of
> 2 individual IDs - check this draft-ietf-sip-saml may replace
> one or more of 2 individual IDs - check this
> draft-ietf-sipping-service-identification may replace one or
> more of 2 individual IDs - check this
> draft-ietf-trill-rbridge-arch may replace one or more of 2
> individual IDs - check this
>
>
>

From lars.eggert@nokia.com  Tue Jan 11 09:03:53 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 9DF013A68E2 for <wgchairs@core3.amsl.com>; Tue, 11 Jan 2011 09:03:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.383
X-Spam-Level: 
X-Spam-Status: No, score=-108.383 tagged_above=-999 required=5 tests=[AWL=1.616, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 u4nBVIPiopA3 for <wgchairs@core3.amsl.com>; Tue, 11 Jan 2011 09:03:51 -0800 (PST)
Received: from mgw-da01.nokia.com (mgw-da01.ext.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id 910E93A677E for <wgchairs@ietf.org>; Tue, 11 Jan 2011 09:03:51 -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 p0BH66b9001888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jan 2011 19:06:07 +0200
Subject: Re: latest missing replaced-by information
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96.5 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary=Apple-Mail-29-778261783; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE21E5E9C7E@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Tue, 11 Jan 2011 19:05:57 +0200
Message-Id: <252ABB2A-0329-47B3-BA70-2B0FF0A9B411@nokia.com>
References: <D2906EA5-2DAB-44C3-A3C7-86598C0CBF29@nokia.com> <EDC0A1AE77C57744B664A310A0B23AE21E5E9C7E@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.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); Tue, 11 Jan 2011 19:05:58 +0200 (EET)
X-Nokia-AV: Clean
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: Tue, 11 Jan 2011 17:03:53 -0000

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

On 2011-1-11, at 17:48, DRAGE, Keith (Keith) wrote:
> I don't understand these two lines:
>=20
> draft-ietf-avt-rtp-gsm-hr may replace one or more of 3 individual IDs =
- check this
> draft-ietf-avt-rtp-svc may replace one or more of 2 individual IDs - =
check this
>=20
> Yes they do replace exactly this number of individual drafts, and =
exactly that number are already listed in the datatracker under the =
replaced by information.

The tool simply warns when it finds more than one individual ID that has =
a file name that is similar to an IETF ID. It's too dumb to analyze this =
case further.

Lars


>=20
> Keith
>=20
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org
>> [mailto:wgchairs-bounces@ietf.org] On Behalf Of Eggert Lars
>> Sent: Monday, January 10, 2011 12:58 PM
>> To: wgchairs@ietf.org
>> Subject: latest missing replaced-by information
>>=20
>> Hi,
>>=20
>> here's yet another installment in the series of reports on
>> potentially missing "replaced-by" relationships in the IETF
>> datatracker.
>>=20
>> WG chairs are encouraged to check whether these are accurate
>> for their WGs, and if so, send a ticket to the secretariat
>> instructing them to "record in the database that draft X
>> replaced draft Y".
>>=20
>> As always, double-check before reporting to the secretariat.
>> Also, see list of possible inconsistencies at the end of the report.
>>=20
>> (Note that the IPR disclosure search tool uses these
>> replaced-by relationships, so keeping them up-to-date is
>> actually useful and not just WG hygiene.)
>>=20
>> Lars
>>=20
>> -----------------------------------------------------------------
>> APP Area
>> -----------------------------------------------------------------
>> EAI Working Group, APP Area
>>   draft-yao-eai-rfc5336bis POTENTIALLY REPLACED BY
>> draft-ietf-eai-rfc5336bis
>>=20
>> SIEVE Working Group, APP Area
>>   draft-george-sieve-autoreply POTENTIALLY REPLACED BY
>> draft-ietf-sieve-autoreply
>>   draft-george-sieve-notify-presence POTENTIALLY REPLACED BY
>> draft-ietf-sieve-notify-presence
>>=20
>> -----------------------------------------------------------------
>> INT Area
>> -----------------------------------------------------------------
>> 6MAN Working Group, INT Area
>>   draft-arifumi-6man-rfc3484-revise POTENTIALLY REPLACED BY
>> draft-ietf-6man-rfc3484-revise
>>   draft-carpenter-6man-flow-update POTENTIALLY REPLACED BY
>> draft-ietf-6man-flow-update
>>   draft-fujisaki-6man-addr-select-opt POTENTIALLY REPLACED
>> BY draft-ietf-6man-addr-select-opt
>>   draft-joshi-6man-neighbor-inform POTENTIALLY REPLACED BY
>> draft-ietf-6man-neighbor-inform
>>=20
>> ANCP Working Group, INT Area
>>   draft-lefaucheur-ancp-mc-extensions POTENTIALLY REPLACED
>> BY draft-ietf-ancp-mc-extensions
>>=20
>> AUTOCONF Working Group, INT Area
>>   draft-baccelli-autoconf-adhoc-addr-model POTENTIALLY
>> REPLACED BY draft-ietf-autoconf-adhoc-addr-model
>>=20
>> CSI Working Group, INT Area
>>   draft-jiang-csi-dhcpv6-cga-ps POTENTIALLY REPLACED BY
>> draft-ietf-csi-dhcpv6-cga-ps
>>   draft-rgaglian-csi-send-name-type-registry POTENTIALLY
>> REPLACED BY draft-ietf-csi-send-name-type-registry
>>=20
>> DHC Working Group, INT Area
>>   draft-miles-dhc-dhcpv6-ldra POTENTIALLY REPLACED BY
>> draft-ietf-dhc-dhcpv6-ldra
>>=20
>> DNSEXT Working Group, INT Area
>>   draft-dolmatov-dnsext-dnssec-gost POTENTIALLY REPLACED BY
>> draft-ietf-dnsext-dnssec-gost
>>   draft-wang-dnsext-newzone-notify POTENTIALLY REPLACED BY
>> draft-ietf-dnsext-newzone-notify
>>=20
>> HIP Working Group, INT Area
>>   draft-camarillo-hip-via POTENTIALLY REPLACED BY draft-ietf-hip-via
>>   draft-henderson-hip-rfc5206-bis POTENTIALLY REPLACED BY
>> draft-ietf-hip-rfc5206-bis
>>   draft-jokela-hip-rfc5202-bis POTENTIALLY REPLACED BY
>> draft-ietf-hip-rfc5202-bis
>>   draft-keranen-hip-native-nat-traversal POTENTIALLY
>> REPLACED BY draft-ietf-hip-native-nat-traversal
>>   draft-keranen-hip-over-hip POTENTIALLY REPLACED BY
>> draft-ietf-hip-over-hip
>>   draft-keranen-hip-reload-instance POTENTIALLY REPLACED BY
>> draft-ietf-hip-reload-instance
>>   draft-moskowitz-hip-rfc4423-bis POTENTIALLY REPLACED BY
>> draft-ietf-hip-rfc4423-bis
>>   draft-moskowitz-hip-rfc5201-bis POTENTIALLY REPLACED BY
>> draft-ietf-hip-rfc5201-bis
>>   draft-nikander-hip-hiccups POTENTIALLY REPLACED BY
>> draft-ietf-hip-hiccups
>>=20
>> LISP Working Group, INT Area
>>   draft-schudel-lisp-mib POTENTIALLY REPLACED BY draft-ietf-lisp-mib
>>=20
>> NETEXT Working Group, INT Area
>>   draft-korhonen-netext-redirect POTENTIALLY REPLACED BY
>> draft-ietf-netext-redirect
>>   draft-krishnan-netext-pmip-lr POTENTIALLY REPLACED BY
>> draft-ietf-netext-pmip-lr
>>   draft-melia-netext-logical-interface-support POTENTIALLY
>> REPLACED BY draft-ietf-netext-logical-interface-support
>>=20
>> SAVI Working Group, INT Area
>>   draft-vogt-savi-framework POTENTIALLY REPLACED BY
>> draft-ietf-savi-framework
>>=20
>> SOFTWIRE Working Group, INT Area
>>   draft-guo-softwire-6rd-radius-attrib POTENTIALLY REPLACED
>> BY draft-ietf-softwire-6rd-radius-attrib
>>   draft-maglione-softwire-dslite-radius-ext POTENTIALLY
>> REPLACED BY draft-ietf-softwire-dslite-radius-ext
>>=20
>> -----------------------------------------------------------------
>> OPS Area
>> -----------------------------------------------------------------
>> BMWG Working Group, OPS Area
>>   draft-asati-bmwg-reset POTENTIALLY REPLACED BY
>> draft-ietf-bmwg-reset
>>   draft-janovak-bmwg-ipflow-meth POTENTIALLY REPLACED BY
>> draft-ietf-bmwg-ipflow-meth
>>   draft-novak-bmwg-ipflow-meth POTENTIALLY REPLACED BY
>> draft-ietf-bmwg-ipflow-meth
>>=20
>> DIME Working Group, OPS Area
>>   draft-zorn-dime-rfc4005bis POTENTIALLY REPLACED BY
>> draft-ietf-dime-rfc4005bis
>>=20
>> EMAN Working Group, OPS Area
>>   draft-parello-eman-energy-aware-mib POTENTIALLY REPLACED
>> BY draft-ietf-eman-energy-aware-mib
>>=20
>> GROW Working Group, OPS Area
>>   draft-dimitri-grow-rss POTENTIALLY REPLACED BY draft-ietf-grow-rss
>>   draft-manderson-grow-geomrt POTENTIALLY REPLACED BY
>> draft-ietf-grow-geomrt
>>=20
>> IPFIX Working Group, OPS Area
>>   draft-boschi-ipfix-anon POTENTIALLY REPLACED BY
>> draft-ietf-ipfix-anon
>>   draft-boschi-ipfix-exporting-type POTENTIALLY REPLACED BY
>> draft-ietf-ipfix-exporting-type
>>   draft-claise-ipfix-export-per-sctp-stream POTENTIALLY
>> REPLACED BY draft-ietf-ipfix-export-per-sctp-stream
>>   draft-gupta-ipfix-reliability-template-ext POTENTIALLY
>> REPLACED BY draft-ietf-ipfix-reliability-template-ext
>>   draft-trammell-ipfix-file POTENTIALLY REPLACED BY
>> draft-ietf-ipfix-file
>>=20
>> MBONED Working Group, OPS Area
>>   draft-asaeda-mboned-mtrace-v2 POTENTIALLY REPLACED BY
>> draft-ietf-mboned-mtrace-v2
>>   draft-asaeda-mboned-session-announcement-req POTENTIALLY
>> REPLACED BY draft-ietf-mboned-session-announcement-req
>>   draft-venaas-mboned-ssmping POTENTIALLY REPLACED BY
>> draft-ietf-mboned-ssmping
>>=20
>> NETCONF Working Group, OPS Area
>>   draft-bierman-netconf-access-control POTENTIALLY REPLACED
>> BY draft-ietf-netconf-access-control
>>   draft-bierman-netconf-with-defaults POTENTIALLY REPLACED
>> BY draft-ietf-netconf-with-defaults
>>   draft-chisholm-netconf-monitoring POTENTIALLY REPLACED BY
>> draft-ietf-netconf-monitoring
>>=20
>> NETMOD Working Group, OPS Area
>>   draft-bierman-netmod-yang-usage POTENTIALLY REPLACED BY
>> draft-ietf-netmod-yang-usage
>>   draft-schoenw-netmod-yang-types POTENTIALLY REPLACED BY
>> draft-ietf-netmod-yang-types
>>   draft-shafer-netmod-arch POTENTIALLY REPLACED BY
>> draft-ietf-netmod-arch
>>=20
>> OPSAWG Working Group, OPS Area
>>   draft-mizrahi-opsawg-oam-overview POTENTIALLY REPLACED BY
>> draft-ietf-opsawg-oam-overview
>>=20
>> OPSEC Working Group, OPS Area
>>   draft-gont-opsec-icmp-filtering POTENTIALLY REPLACED BY
>> draft-ietf-opsec-icmp-filtering
>>   draft-gont-opsec-ip-security POTENTIALLY REPLACED BY
>> draft-ietf-opsec-ip-security
>>=20
>> RADEXT Working Group, OPS Area
>>   draft-dekok-radext-dtls POTENTIALLY REPLACED BY
>> draft-ietf-radext-dtls
>>   draft-dekok-radext-tcp-transport POTENTIALLY REPLACED BY
>> draft-ietf-radext-tcp-transport
>>   draft-lourdelet-radext-ipv6-access POTENTIALLY REPLACED BY
>> draft-ietf-radext-ipv6-access
>>   draft-nelson-radext-crypto-agility-requirements
>> POTENTIALLY REPLACED BY draft-ietf-radext-crypto-agility-requirements
>>   draft-tiwari-radext-tunnel-type POTENTIALLY REPLACED BY
>> draft-ietf-radext-tunnel-type
>>=20
>> V6OPS Working Group, OPS Area
>>   draft-rgaglian-v6ops-v6inixp POTENTIALLY REPLACED BY
>> draft-ietf-v6ops-v6inixp
>>   draft-vandevelde-v6ops-ra-guard POTENTIALLY REPLACED BY
>> draft-ietf-v6ops-ra-guard
>>=20
>> -----------------------------------------------------------------
>> RAI Area
>> -----------------------------------------------------------------
>> ATOCA Working Group, RAI Area
>>   draft-rosen-atoca-cap POTENTIALLY REPLACED BY draft-ietf-atoca-cap
>>   draft-schulzrinne-atoca-requirements POTENTIALLY REPLACED
>> BY draft-ietf-atoca-requirements
>>=20
>> BLISS Working Group, RAI Area
>>   draft-elwell-bliss-ach-analysis POTENTIALLY REPLACED BY
>> draft-ietf-bliss-ach-analysis
>>   draft-poetzl-bliss-call-completion POTENTIALLY REPLACED BY
>> draft-ietf-bliss-call-completion
>>   draft-procter-bliss-call-park-extension POTENTIALLY
>> REPLACED BY draft-ietf-bliss-call-park-extension
>>   draft-rosenberg-bliss-problem-statement POTENTIALLY
>> REPLACED BY draft-ietf-bliss-problem-statement
>>=20
>> CUSS Working Group, RAI Area
>>   draft-johnston-cuss-sip-uui-reqs POTENTIALLY REPLACED BY
>> draft-ietf-cuss-sip-uui-reqs
>>=20
>> DRINKS Working Group, RAI Area
>>   draft-channabasappa-drinks-usecases-requirements
>> POTENTIALLY REPLACED BY draft-ietf-drinks-usecases-requirements
>>=20
>> ECRIT Working Group, RAI Area
>>   draft-barnes-ecrit-rough-loc POTENTIALLY REPLACED BY
>> draft-ietf-ecrit-rough-loc
>>   draft-rosen-ecrit-additional-data POTENTIALLY REPLACED BY
>> draft-ietf-ecrit-additional-data
>>   draft-rosen-ecrit-data-only-ea POTENTIALLY REPLACED BY
>> draft-ietf-ecrit-data-only-ea
>>   draft-schulzrinne-ecrit-location-hiding-req POTENTIALLY
>> REPLACED BY draft-ietf-ecrit-location-hiding-req
>>   draft-schulzrinne-ecrit-lost-sync POTENTIALLY REPLACED BY
>> draft-ietf-ecrit-lost-sync
>>   draft-schulzrinne-ecrit-psap-callback POTENTIALLY REPLACED
>> BY draft-ietf-ecrit-psap-callback
>>   draft-schulzrinne-ecrit-unauthenticated-access POTENTIALLY
>> REPLACED BY draft-ietf-ecrit-unauthenticated-access
>>   draft-taylor-ecrit-security-threats POTENTIALLY REPLACED
>> BY draft-ietf-ecrit-security-threats
>>   draft-tschofenig-ecrit-trustworthy-location POTENTIALLY
>> REPLACED BY draft-ietf-ecrit-trustworthy-location
>>   draft-winterbottom-ecrit-specifying-holes POTENTIALLY
>> REPLACED BY draft-ietf-ecrit-specifying-holes
>>=20
>> GEOPRIV Working Group, RAI Area
>>   draft-mayrhofer-geopriv-geo-uri POTENTIALLY REPLACED BY
>> draft-ietf-geopriv-geo-uri
>>=20
>> P2PSIP Working Group, RAI Area
>>   draft-bryan-p2psip-reload POTENTIALLY REPLACED BY
>> draft-ietf-p2psip-reload
>>=20
>> SPEERMINT Working Group, RAI Area
>>   draft-meyer-speermint-reqs-and-terminology POTENTIALLY
>> REPLACED BY draft-ietf-speermint-reqs-and-terminology
>>   draft-niccolini-speermint-voipthreats POTENTIALLY REPLACED
>> BY draft-ietf-speermint-voipthreats
>>=20
>> XCON Working Group, RAI Area
>>   draft-barnes-xcon-ccmp POTENTIALLY REPLACED BY draft-ietf-xcon-ccmp
>>   draft-barnes-xcon-examples POTENTIALLY REPLACED BY
>> draft-ietf-xcon-examples
>>=20
>> XMPP Working Group, RAI Area
>>   draft-barnes-xmpp-dna POTENTIALLY REPLACED BY draft-ietf-xmpp-dna
>>=20
>> -----------------------------------------------------------------
>> RTG Area
>> -----------------------------------------------------------------
>> CCAMP Working Group, RTG Area
>>   draft-berger-ccamp-assoc-info POTENTIALLY REPLACED BY
>> draft-ietf-ccamp-assoc-info
>>   draft-berger-ccamp-attribute-bnf POTENTIALLY REPLACED BY
>> draft-ietf-ccamp-attribute-bnf
>>   draft-bernstein-ccamp-wson-signaling POTENTIALLY REPLACED
>> BY draft-ietf-ccamp-wson-signaling
>>   draft-kern-ccamp-rsvp-te-sdh-otn-oam-ext POTENTIALLY
>> REPLACED BY draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext
>>   draft-lee-ccamp-wson-signal-compatibility-ospf POTENTIALLY
>> REPLACED BY draft-ietf-ccamp-wson-signal-compatibility-ospf
>>   draft-li-ccamp-lmp-behavior-negotiation POTENTIALLY
>> REPLACED BY draft-ietf-ccamp-lmp-behavior-negotiation
>>   draft-sun-ccamp-dpm POTENTIALLY REPLACED BY draft-ietf-ccamp-dpm
>>   draft-takacs-ccamp-asymm-bw-bidir-lsps-bis POTENTIALLY
>> REPLACED BY draft-ietf-ccamp-asymm-bw-bidir-lsps-bis
>>   draft-zhang-ccamp-gmpls-g709-framework POTENTIALLY
>> REPLACED BY draft-ietf-ccamp-gmpls-g709-framework
>>=20
>> FORCES Working Group, RTG Area
>>   draft-hadi-forces-sctptml POTENTIALLY REPLACED BY
>> draft-ietf-forces-sctptml
>>   draft-haleplidis-forces-implementation-experience
>> POTENTIALLY REPLACED BY draft-ietf-forces-implementation-experience
>>=20
>> IDR Working Group, RTG Area
>>   draft-uttaro-idr-add-paths-guidelines POTENTIALLY REPLACED
>> BY draft-ietf-idr-add-paths-guidelines
>>=20
>> ISIS Working Group, RTG Area
>>   draft-chopps-isis-bfd-tlv POTENTIALLY REPLACED BY
>> draft-ietf-isis-bfd-tlv
>>   draft-ginsberg-isis-genapp POTENTIALLY REPLACED BY
>> draft-ietf-isis-genapp
>>   draft-previdi-isis-mi POTENTIALLY REPLACED BY draft-ietf-isis-mi
>>=20
>> L2VPN Working Group, RTG Area
>>   draft-henderickx-l2vpn-vpls-multihoming POTENTIALLY
>> REPLACED BY draft-ietf-l2vpn-vpls-multihoming
>>   draft-kompella-l2vpn-vpls-multihoming POTENTIALLY REPLACED
>> BY draft-ietf-l2vpn-vpls-multihoming
>>   draft-pdutta-l2vpn-vpls-ldp-mac-opt POTENTIALLY REPLACED
>> BY draft-ietf-l2vpn-vpls-ldp-mac-opt
>>   draft-pkwok-l2vpn-vpls-macflush-ld POTENTIALLY REPLACED BY
>> draft-ietf-l2vpn-vpls-macflush-ld
>>   draft-sajassi-l2vpn-vpls-pbb-interop POTENTIALLY REPLACED
>> BY draft-ietf-l2vpn-vpls-pbb-interop
>>=20
>> MANET Working Group, RTG Area
>>   draft-sratliff-manet-dlep POTENTIALLY REPLACED BY
>> draft-ietf-manet-dlep
>>=20
>> MPLS Working Group, RTG Area
>>   draft-frost-mpls-loss-delay POTENTIALLY REPLACED BY
>> draft-ietf-mpls-loss-delay
>>   draft-frost-mpls-tp-loss-delay-profile POTENTIALLY
>> REPLACED BY draft-ietf-mpls-tp-loss-delay-profile
>>=20
>> OSPF Working Group, RTG Area
>>   draft-acee-ospf-multi-instance POTENTIALLY REPLACED BY
>> draft-ietf-ospf-multi-instance
>>   draft-acee-ospf-transport-instance POTENTIALLY REPLACED BY
>> draft-ietf-ospf-transport-instance
>>   draft-hartman-ospf-analysis POTENTIALLY REPLACED BY
>> draft-ietf-ospf-analysis
>>   draft-nguyen-ospf-lls POTENTIALLY REPLACED BY draft-ietf-ospf-lls
>>   draft-ogier-ospf-dbex-opt POTENTIALLY REPLACED BY
>> draft-ietf-ospf-dbex-opt
>>   draft-venkata-ospf-dynamic-hostname POTENTIALLY REPLACED
>> BY draft-ietf-ospf-dynamic-hostname
>>=20
>> PCE Working Group, RTG Area
>>   draft-bradford-pce-path-key POTENTIALLY REPLACED BY
>> draft-ietf-pce-path-key
>>   draft-farrel-pce-vendor-constraints POTENTIALLY REPLACED
>> BY draft-ietf-pce-vendor-constraints
>>   draft-king-pce-inter-area-as-applicability POTENTIALLY
>> REPLACED BY draft-ietf-pce-inter-area-as-applicability
>>   draft-kkoushik-pce-pcep-mib POTENTIALLY REPLACED BY
>> draft-ietf-pce-pcep-mib
>>   draft-lee-pce-wson-routing-wavelength POTENTIALLY REPLACED
>> BY draft-ietf-pce-wson-routing-wavelength
>>   draft-leroux-pce-of POTENTIALLY REPLACED BY draft-ietf-pce-of
>>   draft-margaria-pce-gmpls-pcep-extensions POTENTIALLY
>> REPLACED BY draft-ietf-pce-gmpls-pcep-extensions
>>   draft-oki-pce-inter-layer-ext POTENTIALLY REPLACED BY
>> draft-ietf-pce-inter-layer-ext
>>   draft-otani-pce-gmpls-aps-req POTENTIALLY REPLACED BY
>> draft-ietf-pce-gmpls-aps-req
>>   draft-sivabalan-pce-dste POTENTIALLY REPLACED BY
>> draft-ietf-pce-dste
>>   draft-vasseur-pce-monitoring POTENTIALLY REPLACED BY
>> draft-ietf-pce-monitoring
>>   draft-yasukawa-pce-p2mp-app POTENTIALLY REPLACED BY
>> draft-ietf-pce-p2mp-app
>>   draft-yasukawa-pce-p2mp-req POTENTIALLY REPLACED BY
>> draft-ietf-pce-p2mp-req
>>   draft-yasukawa-pce-vpn-req POTENTIALLY REPLACED BY
>> draft-ietf-pce-vpn-req
>>=20
>> PWE3 Working Group, RTG Area
>>   draft-lm-pwe3-mpls-tp-gal-in-pw POTENTIALLY REPLACED BY
>> draft-ietf-pwe3-mpls-tp-gal-in-pw
>>=20
>> ROLL Working Group, RTG Area
>>   draft-dt-roll-p2p-rpl POTENTIALLY REPLACED BY
>> draft-ietf-roll-p2p-rpl
>>   draft-gnawali-roll-minrank-hysteresis-of POTENTIALLY
>> REPLACED BY draft-ietf-roll-minrank-hysteresis-of
>>   draft-levis-roll-trickle POTENTIALLY REPLACED BY
>> draft-ietf-roll-trickle
>>   draft-tsao-roll-security-framework POTENTIALLY REPLACED BY
>> draft-ietf-roll-security-framework
>>=20
>> SIDR Working Group, RTG Area
>>   draft-huston-sidr-bogons POTENTIALLY REPLACED BY
>> draft-ietf-sidr-bogons
>>   draft-huston-sidr-keyroll POTENTIALLY REPLACED BY
>> draft-ietf-sidr-keyroll
>>   draft-huston-sidr-repos-struct POTENTIALLY REPLACED BY
>> draft-ietf-sidr-repos-struct
>>   draft-huston-sidr-roa-validation POTENTIALLY REPLACED BY
>> draft-ietf-sidr-roa-validation
>>   draft-huston-sidr-rpki-algs POTENTIALLY REPLACED BY
>> draft-ietf-sidr-rpki-algs
>>   draft-kisteleki-sidr-rpsl-sig POTENTIALLY REPLACED BY
>> draft-ietf-sidr-rpsl-sig
>>   draft-manderson-sidr-usecases POTENTIALLY REPLACED BY
>> draft-ietf-sidr-usecases
>>   draft-pmohapat-sidr-origin-validation-signaling
>> POTENTIALLY REPLACED BY draft-ietf-sidr-origin-validation-signaling
>>   draft-pmohapat-sidr-pfx-validate POTENTIALLY REPLACED BY
>> draft-ietf-sidr-pfx-validate
>>   draft-weiler-sidr-publication POTENTIALLY REPLACED BY
>> draft-ietf-sidr-publication
>>=20
>> -----------------------------------------------------------------
>> SEC Area
>> -----------------------------------------------------------------
>> DKIM Working Group, SEC Area
>>   draft-lindsey-dkim-mailinglists POTENTIALLY REPLACED BY
>> draft-ietf-dkim-mailinglists
>>=20
>> HOKEY Working Group, SEC Area
>>   draft-wu-hokey-rfc5296bis POTENTIALLY REPLACED BY
>> draft-ietf-hokey-rfc5296bis
>>=20
>> PKIX Working Group, SEC Area
>>   draft-cooper-pkix-rfc2560bis POTENTIALLY REPLACED BY
>> draft-ietf-pkix-rfc2560bis
>>   draft-cooper-pkix-rfc5280-clarifications POTENTIALLY
>> REPLACED BY draft-ietf-pkix-rfc5280-clarifications
>>   draft-santesson-pkix-certimage POTENTIALLY REPLACED BY
>> draft-ietf-pkix-certimage
>>=20
>> TLS Working Group, SEC Area
>>   draft-rescorla-tls-suiteb POTENTIALLY REPLACED BY
>> draft-ietf-tls-suiteb
>>   draft-seggelmann-tls-dtls-heartbeat POTENTIALLY REPLACED
>> BY draft-ietf-tls-dtls-heartbeat
>>=20
>> -----------------------------------------------------------------
>> TSV Area
>> -----------------------------------------------------------------
>> BEHAVE Working Group, TSV Area
>>   draft-liu-behave-ftp64 POTENTIALLY REPLACED BY
>> draft-ietf-behave-ftp64
>>=20
>> CONEX Working Group, TSV Area
>>   draft-moncaster-conex-concepts-uses POTENTIALLY REPLACED
>> BY draft-ietf-conex-concepts-uses
>>=20
>> DCCP Working Group, TSV Area
>>   draft-renker-dccp-tfrc-rtt-option POTENTIALLY REPLACED BY
>> draft-ietf-dccp-tfrc-rtt-option
>>=20
>> IPPM Working Group, TSV Area
>>   draft-geib-ippm-metrictest POTENTIALLY REPLACED BY
>> draft-ietf-ippm-metrictest
>>=20
>> MPTCP Working Group, TSV Area
>>   draft-scharf-mptcp-api POTENTIALLY REPLACED BY draft-ietf-mptcp-api
>>=20
>> NFSV4 Working Group, TSV Area
>>   draft-alexrn-nfsv4-ipv6 POTENTIALLY REPLACED BY
>> draft-ietf-nfsv4-ipv6
>>   draft-eisler-nfsv4-minorversion-2-requirements POTENTIALLY
>> REPLACED BY draft-ietf-nfsv4-minorversion-2-requirements
>>   draft-faibish-nfsv4-pnfs-access-permissions-check
>> POTENTIALLY REPLACED BY =
draft-ietf-nfsv4-pnfs-access-permissions-check
>>=20
>> PCN Working Group, TSV Area
>>   draft-karagiannis-pcn-signaling-requirements POTENTIALLY
>> REPLACED BY draft-ietf-pcn-signaling-requirements
>>=20
>> TCPM Working Group, TSV Area
>>   draft-hkchu-tcpm-initcwnd POTENTIALLY REPLACED BY
>> draft-ietf-tcpm-initcwnd
>>=20
>> -----------------------------------------------------------------
>> Potential Inconsistencies
>> -----------------------------------------------------------------
>> draft-ietf-6lowpan-nd may replace one or more of 2 individual
>> IDs - check this draft-ietf-avt-rtp-gsm-hr may replace one or
>> more of 3 individual IDs - check this draft-ietf-avt-rtp-svc
>> may replace one or more of 2 individual IDs - check this
>> draft-ietf-bmwg-ipflow-meth may replace one or more of 2
>> individual IDs - check this draft-ietf-decade-survey may
>> replace one or more of 2 individual IDs - check this
>> draft-ietf-dhc-dhcpv4-bulk-leasequery may replace one or more
>> of 2 individual IDs - check this draft-ietf-forces-tmlsp may
>> replace one or more of 2 individual IDs - check this
>> draft-ietf-ipfix-biflow may replace one or more of 2
>> individual IDs - check this draft-ietf-l2tpext-tdm may
>> replace one or more of 2 individual IDs - check this
>> draft-ietf-l2vpn-vpls-multihoming may replace one or more of
>> 2 individual IDs - check this draft-ietf-mpls-tp-fault may
>> replace one or more of 2 individual IDs - check this
>> draft-ietf-netconf-monitoring may replace one or more of 2
>> individual IDs - check this draft-ietf-netlmm-lma-discovery
>> may replace one or more of 2 individual IDs - check this
>> draft-ietf-netlmm-mip-interactions may replace one or more of
>> 2 individual IDs - check this draft-ietf-sip-saml may replace
>> one or more of 2 individual IDs - check this
>> draft-ietf-sipping-service-identification may replace one or
>> more of 2 individual IDs - check this
>> draft-ietf-trill-rbridge-arch may replace one or more of 2
>> individual IDs - check this
>>=20
>>=20
>>=20


--Apple-Mail-29-778261783
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDExMTE3MDU1OFowIwYJKoZIhvcNAQkE
MRYEFJkpN1/gHgH6XTlsvbDKEImDB7XiMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AK1O8lm3Gkl4JfTmCpHqLmmWGCmYuJ4xmc3uVL6C/zTPdqIgbPevw1D7toJFLvy26W2vNm6GVsmt
i5N1UgyOdED25eMUAYAOjy6Y31ugcqEPzQFmskU3FxPINcTmClytqgtygKcQ3ZZutC3LnjhUWi76
H27nYxorKsvj3VtCGedlxcQslUNSe3qu0Nh6/+pJc1mrL4DeVL8sL92i06WwzbRERzc/IskDp2Nk
nVlqDglcfyB+kd4RLakwEh/Yn6mcKEk2No8EeVFjmGEfdjK3tCgkVZQI9jEz99OA0TTD5TJVcFuH
Um1pweXPsqui2nf51yKMNUy0YeT54XglZpMJzC0AAAAAAAA=

--Apple-Mail-29-778261783--

From d3e3e3@gmail.com  Sun Jan 16 12:58:33 2011
Return-Path: <d3e3e3@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 CB5433A6E5E for <wgchairs@core3.amsl.com>; Sun, 16 Jan 2011 12:58:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.403
X-Spam-Level: 
X-Spam-Status: No, score=-103.403 tagged_above=-999 required=5 tests=[AWL=0.196, 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 B-cRt1V-NpEn for <wgchairs@core3.amsl.com>; Sun, 16 Jan 2011 12:58:33 -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 BDB2F3A6E5B for <wgchairs@ietf.org>; Sun, 16 Jan 2011 12:58:32 -0800 (PST)
Received: by wyf23 with SMTP id 23so4741112wyf.31 for <wgchairs@ietf.org>; Sun, 16 Jan 2011 13:01:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=PcnPrNWC390nrJrehIiWOudX89B1ymh6cqXaobBINqE=; b=Fa26yHyjVAJnt54DeK8oufPHQOKd0Dm6ZTAhVHiRGIQ1p79w1iy1+ZQoaIIBi5LXim uvXt1aN/seSzdcUIRXWmUGnRAq+hANm7BL02TmwZVIwYh57R+YhXcWFIZomuda+KXEgN zanDnjnTceYSRw4nsOMJLJ4qHwSZPIT00RVAI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; b=fQHKRncvmqUAMjoaRgpMjOCWg0RdUwwiaJ4VLm1gd6VHatE5jzEcUBd1unOLpIOMIV C5Unrc5AwCiZ4o4Sd78N2Kf4t4nM4Z1YpyUhtEdRx7Ex4KQ9kkiI7G/a+BDxOuV+b6Re 3e+yZdXQc1y89o1to41+UUbthd1B2ItEij1Cc=
Received: by 10.227.138.129 with SMTP id a1mr3221943wbu.37.1295211616202; Sun, 16 Jan 2011 13:00:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Sun, 16 Jan 2011 12:59:55 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 16 Jan 2011 15:59:55 -0500
Message-ID: <AANLkTinyBfeYFae+gjfJftaaS73xjRQpucQUo-PNCEMU@mail.gmail.com>
Subject: Draft submissions can't find first author
To: Working Group Chairs <wgchairs@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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, 16 Jan 2011 20:58:34 -0000

So, for my last draft submission and one I'm trying to do right now, I
find that the secretariat software can't find the first author's name
at the top right of the first page. It can find subsequent authors.
But something changed a few weeks ago so that draft formats that
worked find are now encountering this problem.

Has anyone else noticed this? If so, have you found a fix for it?

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street
=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

From tme@americafree.tv  Sun Jan 16 13:24:19 2011
Return-Path: <tme@americafree.tv>
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 A334B3A6E5B for <wgchairs@core3.amsl.com>; Sun, 16 Jan 2011 13:24:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.254
X-Spam-Level: 
X-Spam-Status: No, score=-102.254 tagged_above=-999 required=5 tests=[AWL=0.345, 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 tNYsi3M-OE4C for <wgchairs@core3.amsl.com>; Sun, 16 Jan 2011 13:24:18 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id D95273A6E3A for <wgchairs@ietf.org>; Sun, 16 Jan 2011 13:24:18 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 174519AB8BDF; Sun, 16 Jan 2011 16:26:48 -0500 (EST)
Subject: Re: Draft submissions can't find first author
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <AANLkTinyBfeYFae+gjfJftaaS73xjRQpucQUo-PNCEMU@mail.gmail.com>
Date: Sun, 16 Jan 2011 16:26:47 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <3EEA9B6E-FB38-43CF-A71B-BB48F86CB1EE@americafree.tv>
References: <AANLkTinyBfeYFae+gjfJftaaS73xjRQpucQUo-PNCEMU@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1081)
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, 16 Jan 2011 21:24:19 -0000

Taking this for a bug, I alerted the appropriate channels.

Regards
Marshall

On Jan 16, 2011, at 3:59 PM, Donald Eastlake wrote:

> So, for my last draft submission and one I'm trying to do right now, I
> find that the secretariat software can't find the first author's name
> at the top right of the first page. It can find subsequent authors.
> But something changed a few weeks ago so that draft formats that
> worked find are now encountering this problem.
> 
> Has anyone else noticed this? If so, have you found a fix for it?
> 
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street
>  Milford, MA 01757 USA
>  d3e3e3@gmail.com
> 


From bclaise@cisco.com  Sun Jan 16 15:06:43 2011
Return-Path: <bclaise@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 3E4DF3A6C43 for <wgchairs@core3.amsl.com>; Sun, 16 Jan 2011 15:06:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.487
X-Spam-Level: 
X-Spam-Status: No, score=-2.487 tagged_above=-999 required=5 tests=[AWL=0.112,  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 GqY3uHi72pOe for <wgchairs@core3.amsl.com>; Sun, 16 Jan 2011 15:06:42 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 0CAA83A6B74 for <wgchairs@ietf.org>; Sun, 16 Jan 2011 15:06:41 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p0GN9CZp003125; Mon, 17 Jan 2011 00:09:13 +0100 (CET)
Received: from [10.61.81.134] (ams3-vpn-dhcp4487.cisco.com [10.61.81.134]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p0GN9A2i015038; Mon, 17 Jan 2011 00:09:10 +0100 (CET)
Message-ID: <4D337A96.7030300@cisco.com>
Date: Mon, 17 Jan 2011 00:09:10 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: Draft submissions can't find first author
References: <AANLkTinyBfeYFae+gjfJftaaS73xjRQpucQUo-PNCEMU@mail.gmail.com>
In-Reply-To: <AANLkTinyBfeYFae+gjfJftaaS73xjRQpucQUo-PNCEMU@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 16 Jan 2011 23:06:43 -0000

Donald,

I faced the same issue when the company name for the author at the top 
is not exactly the same as in the authors section.
Example: "Cisco Systems" at the top versus "Cisco Systems, Inc." in the 
authors section.

Regards, Benoit.
> So, for my last draft submission and one I'm trying to do right now, I
> find that the secretariat software can't find the first author's name
> at the top right of the first page. It can find subsequent authors.
> But something changed a few weeks ago so that draft formats that
> worked find are now encountering this problem.
>
> Has anyone else noticed this? If so, have you found a fix for it?
>
> Thanks,
> Donald
> =============================
>   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>   155 Beaver Street
>   Milford, MA 01757 USA
>   d3e3e3@gmail.com


From d3e3e3@gmail.com  Sun Jan 16 20:47:52 2011
Return-Path: <d3e3e3@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 9492A3A6DBF for <wgchairs@core3.amsl.com>; Sun, 16 Jan 2011 20:47:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.407
X-Spam-Level: 
X-Spam-Status: No, score=-103.407 tagged_above=-999 required=5 tests=[AWL=0.192, 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 K7lriKwbZqEx for <wgchairs@core3.amsl.com>; Sun, 16 Jan 2011 20:47:51 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by core3.amsl.com (Postfix) with ESMTP id 80F7E3A6DA2 for <wgchairs@ietf.org>; Sun, 16 Jan 2011 20:47:51 -0800 (PST)
Received: by wwi17 with SMTP id 17so1709600wwi.1 for <wgchairs@ietf.org>; Sun, 16 Jan 2011 20:50:24 -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:content-type:content-transfer-encoding; bh=UwyY9ozMbO4XnHuwEf7WOAV3RDBAqqPheSJBzfvP/U0=; b=UxkR4xqx3dbkFb7P7fhMlNpaCA9EYpZbiqmSRL+gLB+neyimebOe8kRaS+rWLd6J0B SNOTWViWVBfxeG5ztlzFgIWGD009oAdKoFZlX97gI5+I0x61eidMrLysf3kfRF+eBZ+a FPUx+jM05R2E90fX0mnXyZRd9bATYtNMKaLiI=
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 :content-type:content-transfer-encoding; b=iSXR3/5QHisumREGOa/JAewfIG/MY0u+PtStx9aBActSd/M3fZAlbjQ5Ii6Op2JocT wO4oEU/BQdMo4USdQ6Yk8Qq/N3hPiCMIucShHrYtSBcgqUPAuxcR5BTxYVmbEZ7lkTvR 6zpc+RrAy/w/lQXhz6DN6QnBuoO1Jj3LyNkbc=
Received: by 10.227.143.79 with SMTP id t15mr3461101wbu.95.1295239824077; Sun, 16 Jan 2011 20:50:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Sun, 16 Jan 2011 20:50:04 -0800 (PST)
In-Reply-To: <4D337A96.7030300@cisco.com>
References: <AANLkTinyBfeYFae+gjfJftaaS73xjRQpucQUo-PNCEMU@mail.gmail.com> <4D337A96.7030300@cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 16 Jan 2011 23:50:04 -0500
Message-ID: <AANLkTin+B6XMOf-mr-_pm03MGVf6gUCbpbwuWjyCZ7Bd@mail.gmail.com>
Subject: Re: Draft submissions can't find first author
To: Working Group Chairs <wgchairs@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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, 17 Jan 2011 04:47:52 -0000

Based on the message below and a bunch of experiments, it appears that
the draft submission tool no longer allows names with greater than 2
parts (I sometimes list my name as "Donald Eastlake 3rd" which used to
work fine) and that it requires a more exact match than it used to
between the name and affiliation at the top right of the title page
and as the appear in the Authors' Addresses section...

Donald

On Sun, Jan 16, 2011 at 6:09 PM, Benoit Claise <bclaise@cisco.com> wrote:
> Donald,
>
> I faced the same issue when the company name for the author at the top is
> not exactly the same as in the authors section.
> Example: "Cisco Systems" at the top versus "Cisco Systems, Inc." in the
> authors section.
>
> Regards, Benoit.
>>
>> So, for my last draft submission and one I'm trying to do right now, I
>> find that the secretariat software can't find the first author's name
>> at the top right of the first page. It can find subsequent authors.
>> But something changed a few weeks ago so that draft formats that
>> worked find are now encountering this problem.
>>
>> Has anyone else noticed this? If so, have you found a fix for it?
>>
>> Thanks,
>> Donald
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>> =A0Donald E. Eastlake 3rd =A0 +1-508-333-2270 (cell)
>> =A0155 Beaver Street
>> =A0Milford, MA 01757 USA
>> =A0d3e3e3@gmail.com
>
>

From rjsparks@nostrum.com  Wed Jan 19 11:18:46 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 5C9E43A71A6 for <wgchairs@core3.amsl.com>; Wed, 19 Jan 2011 11:18:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, 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 e4ny5fjcdtmu for <wgchairs@core3.amsl.com>; Wed, 19 Jan 2011 11:18:45 -0800 (PST)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by core3.amsl.com (Postfix) with ESMTP id 506D03A71A5 for <wgchairs@ietf.org>; Wed, 19 Jan 2011 11:18:45 -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 p0JJLDol028421 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <wgchairs@ietf.org>; Wed, 19 Jan 2011 13:21:13 -0600 (CST) (envelope-from rjsparks@nostrum.com)
From: Robert Sparks <rjsparks@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: RFC Style guide
Date: Wed, 19 Jan 2011 13:21:12 -0600
Message-Id: <52827D5B-9F4A-43F5-870E-A3DCC7714F08@nostrum.com>
To: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
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, 19 Jan 2011 19:18:46 -0000

I had occasion to read through the RFC Style guide at
<http://www.rfc-editor.org/rfc-style-guide/rfc-style>
(linked from <http://www.rfc-editor.org/styleguide.html>)

and found a few tidbits that I had forgotten/misremembered.

If you haven't looked through it recently, consider doing so - it's good =
input for shepherd reviews.

RjS=

From stpeter@stpeter.im  Wed Jan 19 11:39:38 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 F1C903A71A8 for <wgchairs@core3.amsl.com>; Wed, 19 Jan 2011 11:39:38 -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 a9p03uPoQAfC for <wgchairs@core3.amsl.com>; Wed, 19 Jan 2011 11:39:38 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id F334F3A71A4 for <wgchairs@ietf.org>; Wed, 19 Jan 2011 11:39:37 -0800 (PST)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 18D5A400EE; Wed, 19 Jan 2011 12:57:56 -0700 (MST)
Message-ID: <4D373E98.5080204@stpeter.im>
Date: Wed, 19 Jan 2011 12:42:16 -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: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: RFC Style guide
References: <52827D5B-9F4A-43F5-870E-A3DCC7714F08@nostrum.com>
In-Reply-To: <52827D5B-9F4A-43F5-870E-A3DCC7714F08@nostrum.com>
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="------------ms000102030802000205050401"
Cc: "wgchairs@ietf.org 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, 19 Jan 2011 19:39:39 -0000

This is a cryptographically signed message in MIME format.

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

On 1/19/11 12:21 PM, Robert Sparks wrote:
> I had occasion to read through the RFC Style guide at
> <http://www.rfc-editor.org/rfc-style-guide/rfc-style>
> (linked from <http://www.rfc-editor.org/styleguide.html>)
>=20
> and found a few tidbits that I had forgotten/misremembered.
>=20
> If you haven't looked through it recently, consider doing so - it's goo=
d input for shepherd reviews.

I wonder why that document is not itself published as an RFC...

Peter

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




--------------ms000102030802000205050401
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
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEx
OTE5NDIxNlowIwYJKoZIhvcNAQkEMRYEFAtFA4zIY3lufvzQhJ9qoOw92gQ2MF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQA8r2E3zzLWTMVZgy2v5b1nJrP7UPXNSknIucbXsZODhVCeFbC2mRlDo3gH
1zQ1urtH9h3WH65ZIROX0QOYKGnJEiXJDKp5jetyxuuOk3XCBBNuVDGjn5v1qcGO0YX48CVY
WSmIaOAzW8gY9q8pj1rz1WSTQvDX01D7XbKJPedfD2oyWxMxrTxI2LBlUh/0oQYRImki51Mp
AMITvRzLSwxCjGB7LYBNATbvgTLmSKo/zJrhubosAFXiNIBrfQelDtkPDuDl36IRckByu/jw
qMfOPgTyZFKz0S0xq2x3WsQ281l0DC5NoOuyrtRH12+SMsCpAOZmdMMIAvx3ODnzepW3AAAA
AAAA
--------------ms000102030802000205050401--

From wwwrun@core3.amsl.com  Wed Jan 19 12:49: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 7995E3A717C; Wed, 19 Jan 2011 12:49:59 -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: <20110119204959.7995E3A717C@core3.amsl.com>
Date: Wed, 19 Jan 2011 12:49:59 -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, 19 Jan 2011 20:49:59 -0000

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

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

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

2. Meeting and Training Schedule: 
	A. Meeting starts 09:00 Monday 28 March through 15:15 Friday
	1 April. 
	B. Most training sessions on Sunday afternoon 27 March - see:
	http://www.ietf.org/meeting/80/tutorials.html

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
	The IETF is holding blocks of guest rooms at 3 hotels in Prague:
	the Hilton Prague (the Meeting Venue), the InterContinental Prague
	and the Sheraton Prague Charles Square Hotel, both of which are in
	Prague Old Town and a 25 minute walk from the Hilton. There are
	smaller hotels located closer to the Hilton Prague.

	In addition to public transportation and airport taxis at the 
	airport, these hotels can arrange to have you picked up at the
	airport. Fees and information on how to arrange for this
	service is available on the hotel page:
	http://www.ietf.org/meeting/80/hotel.html
	under "Airport Transfer Option"

	Room rates are inclusive of daily breakfast and in room
	high-speed Internet access. 
	Note that breakfast will not be served at the Meeting venue as it 
	is included in the above hotel guest room rates.

	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.  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.

6.  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.

	Some headings have already created, but no real content exists
	yet. The two links to "soccer/football" and "bar BoFs" that
	exist under Events are there as examples of things you can
	create, but there is nothing there if you follow the links.

	The wiki can be viewed by anyone but can only be edited by
	registered meeting attendees. If you want to add information 
	(a great restaurant you know of, an informal event (soccer game),
	etc.) you will have to log into the wiki. If you have already
	registered for the meeting, you have an account waiting for you.
	Your login name is the email address that you used to register
	for the meeting; your password is your full 10 digit confirmation
	number.

	Note: this wiki is not intended to replace the host website, nor
	any other official meeting related site. Instead, the intent is
	that some of the information currently shared on the XXattendees
	mailing list be captured online in one location, where it will be
	easy for members of the community to locate and add to it. Our
	hope is that your wiki makes a contribution to your meeting
	experience.

Only 64 days until the Prague IETF!


From dthaler@microsoft.com  Wed Jan 19 13:12:03 2011
Return-Path: <dthaler@microsoft.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 BD77D28C106 for <wgchairs@core3.amsl.com>; Wed, 19 Jan 2011 13:12:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.571
X-Spam-Level: 
X-Spam-Status: No, score=-110.571 tagged_above=-999 required=5 tests=[AWL=0.028, 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 KiUneTzelVh6 for <wgchairs@core3.amsl.com>; Wed, 19 Jan 2011 13:11:54 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 4397D28C0F4 for <wgchairs@ietf.org>; Wed, 19 Jan 2011 13:11:52 -0800 (PST)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 19 Jan 2011 13:14:32 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) with Microsoft SMTP Server (TLS) id 14.1.255.3; Wed, 19 Jan 2011 13:14:32 -0800
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.189]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Wed, 19 Jan 2011 13:14:31 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, Robert Sparks <rjsparks@nostrum.com>
Subject: RE: RFC Style guide
Thread-Topic: RFC Style guide
Thread-Index: AQHLuA4hGo35RISNXku3gDM/td+PSZPZN/MA//+SdRA=
Date: Wed, 19 Jan 2011 21:14:30 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF65344BB6DA@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
References: <52827D5B-9F4A-43F5-870E-A3DCC7714F08@nostrum.com> <4D373E98.5080204@stpeter.im>
In-Reply-To: <4D373E98.5080204@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "wgchairs@ietf.org 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, 19 Jan 2011 21:12:04 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiB3Z2NoYWlycy1ib3VuY2VzQGll
dGYub3JnIFttYWlsdG86d2djaGFpcnMtYm91bmNlc0BpZXRmLm9yZ10gT24NCj4gQmVoYWxmIE9m
IFBldGVyIFNhaW50LUFuZHJlDQo+IFNlbnQ6IFdlZG5lc2RheSwgSmFudWFyeSAxOSwgMjAxMSAx
MTo0MiBBTQ0KPiBUbzogUm9iZXJ0IFNwYXJrcw0KPiBDYzogd2djaGFpcnNAaWV0Zi5vcmcgQ2hh
aXJzDQo+IFN1YmplY3Q6IFJlOiBSRkMgU3R5bGUgZ3VpZGUNCj4gDQo+IE9uIDEvMTkvMTEgMTI6
MjEgUE0sIFJvYmVydCBTcGFya3Mgd3JvdGU6DQo+ID4gSSBoYWQgb2NjYXNpb24gdG8gcmVhZCB0
aHJvdWdoIHRoZSBSRkMgU3R5bGUgZ3VpZGUgYXQNCj4gPiA8aHR0cDovL3d3dy5yZmMtZWRpdG9y
Lm9yZy9yZmMtc3R5bGUtZ3VpZGUvcmZjLXN0eWxlPg0KPiA+IChsaW5rZWQgZnJvbSA8aHR0cDov
L3d3dy5yZmMtZWRpdG9yLm9yZy9zdHlsZWd1aWRlLmh0bWw+KQ0KPiA+DQo+ID4gYW5kIGZvdW5k
IGEgZmV3IHRpZGJpdHMgdGhhdCBJIGhhZCBmb3Jnb3R0ZW4vbWlzcmVtZW1iZXJlZC4NCj4gPg0K
PiA+IElmIHlvdSBoYXZlbid0IGxvb2tlZCB0aHJvdWdoIGl0IHJlY2VudGx5LCBjb25zaWRlciBk
b2luZyBzbyAtIGl0J3MgZ29vZCBpbnB1dCBmb3INCj4gc2hlcGhlcmQgcmV2aWV3cy4NCj4gDQo+
IEkgd29uZGVyIHdoeSB0aGF0IGRvY3VtZW50IGlzIG5vdCBpdHNlbGYgcHVibGlzaGVkIGFzIGFu
IFJGQy4uLg0KDQpXZWxsIGZvciBvbmUsIGJlY2F1c2UgdGhlIHJlYWwgInN0eWxlIGd1aWRlIiBp
cyBjdXJyZW50bHkgc2NhdHRlcmVkIGFjcm9zcyANCm11bHRpcGxlIGRvY3MsIGxpbmtlZCBmcm9t
IGh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvc3R5bGVndWlkZS5odG1sLA0KYW5kIHNvIG5lZWRz
IHNvbWUgd29yayB0byBnZXQgdGhpbmdzIGRvd24gdG8gb25seSBvbmUgb3IgdHdvIGRvY3VtZW50
cy4NCg0KQnV0IG1haW5seSwgSSB0aGluaywgYmVjYXVzZSBpdCB3b3VsZCBiZSB0aGUgam9iIG9m
IHRoZSBSU0UgdG8gZG8gdGhpbmdzIGxpa2UNCnRoaXMsIGFuZCB0aGF0IGhhc24ndCBiZWVuIHRo
ZSBwcmlvcml0eSBmb3IgdGhlIFRSU0UuDQoNCk9uZSBvZiB0aGUgVFJTRSdzIHJlcG9ydHMgbWVu
dGlvbmVkIHRoaXMgYXMgYW4gZXhhbXBsZSBvZiBzb21lIGxvbmdlci10ZXJtDQp3b3JrIHRoYXQg
dGhlIFJTRSBuZWVkcyB0byBkby4NCg0KLURhdmUNCg0KPiANCj4gUGV0ZXINCj4gDQo+IC0tDQo+
IFBldGVyIFNhaW50LUFuZHJlDQo+IGh0dHBzOi8vc3RwZXRlci5pbS8NCg0K

From wwwrun@core3.amsl.com  Wed Jan 19 13:31:26 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 E3D2228C0F4; Wed, 19 Jan 2011 13:31:25 -0800 (PST)
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: IETF 83 Venue 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110119213125.E3D2228C0F4@core3.amsl.com>
Date: Wed, 19 Jan 2011 13:31:25 -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: Wed, 19 Jan 2011 21:31:26 -0000

The IAOC is pleased to announce Paris as the site for IETF 83 from 25 - 30
March 2012.  The IETF last met in the city in 2005 at IETF 63.

Paris was the number one choice for a European venue in a venue
preference survey conducted after IETF 78.

Those who may be interested in hosting or sponsoring this or any future
meeting are invited to contact Drew Dvorshak at dvorshak@isoc.org.  See
meeting opportunities below.

Registration has opened for IETF 80 in Prague. 
http://www.ietf.org/meeting/80/index.html
Hope to see you there in 64 days!  Sponsorship opportunities are still
available for Prague, such as the Welcome Reception and beverage breaks. 
Contact Drew if interested.

Ray Pelletier
IETF Administrative Director

2011
IETF 80  Prague  27 March - 1 April  Host: CZ.NIC
IETF 81  Quebec City 24 - 29 July  Host:  RIM
IETF 82  Taipei  13 - 18 November  Host: TWNIC

2012
IETF 83  Paris 25 - 30 March 	Host:  <your name here>
IETF 84  Asia - Pacific  29 July - 3 Aug  Host:   <your name here>
IETF 85  Atlanta  4 - 9 November   Host:  <your name here>

2013
IETF 86  Orlando  10 - 15 March  Host:  <your name here> (Back-to-back
with IEEE)
IETF 87  Europe  28 July - 2 Aug  Host:  <your name here>
IETF 88  Asia  3 - 8 November  Host:  <your name here>

From Joe.Hildebrand@webex.com  Thu Jan 20 00:59:39 2011
Return-Path: <Joe.Hildebrand@webex.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 8673628C0DF for <wgchairs@core3.amsl.com>; Thu, 20 Jan 2011 00:59:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.341
X-Spam-Level: 
X-Spam-Status: No, score=-104.341 tagged_above=-999 required=5 tests=[AWL=0.191, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067, 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 J9DLXpuAe8Qo for <wgchairs@core3.amsl.com>; Thu, 20 Jan 2011 00:59:38 -0800 (PST)
Received: from gw2.webex.com (gw2.webex.com [64.68.122.209]) by core3.amsl.com (Postfix) with SMTP id C913228B23E for <wgchairs@ietf.org>; Thu, 20 Jan 2011 00:59:38 -0800 (PST)
Received: from SRV-EXSC03.webex.local ([192.168.252.197]) by gw2.webex.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 20 Jan 2011 01:02:20 -0800
Received: from 66.114.169.8 ([66.114.169.8]) by SRV-EXSC03.webex.local ([192.168.252.200]) via Exchange Front-End Server mailus.webex.com ([66.114.175.11]) with Microsoft Exchange Server HTTP-DAV ; Thu, 20 Jan 2011 09:02:20 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Thu, 20 Jan 2011 02:02:19 -0700
Subject: Re: RFC Style guide
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: Dave Thaler <dthaler@microsoft.com>, Peter Saint-Andre <stpeter@stpeter.im>, Robert Sparks <rjsparks@nostrum.com>
Message-ID: <C95D482B.47D01%joe.hildebrand@webex.com>
Thread-Topic: RFC Style guide
Thread-Index: AQHLuA4hGo35RISNXku3gDM/td+PSZPZN/MA//+SdRCAAMb3HA==
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF65344BB6DA@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
IM-ID: xmpp:jhildebr@cisco.com
Presence-ID: xmpp:jhildebr@cisco.com
Jabber-ID: jhildebr@cisco.com
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 20 Jan 2011 09:02:20.0761 (UTC) FILETIME=[BEDC1490:01CBB880]
Cc: "wgchairs@ietf.org 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: Thu, 20 Jan 2011 08:59:39 -0000

On 1/19/11 2:14 PM, "Dave Thaler" <dthaler@microsoft.com> wrote:

> But mainly, I think, because it would be the job of the RSE to do things like
> this, and that hasn't been the priority for the TRSE.
> 
> One of the TRSE's reports mentioned this as an example of some longer-term
> work that the RSE needs to do.

Sorry that I haven't followed this closely enough, but Glen has now been
formally the RSE since 2010-04-20?

Is it appropriate and respectful for us to start asking questions of the RSE
and RSAG yet about things we'd like to see for the future?  There were a few
questions I asked in Beijing that were met with "please wait for a few
months".

-- 
Joe Hildebrand


From jmpolk@cisco.com  Thu Jan 20 17:49:10 2011
Return-Path: <jmpolk@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 EEDF63A6897; Thu, 20 Jan 2011 17:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.525
X-Spam-Level: 
X-Spam-Status: No, score=-110.525 tagged_above=-999 required=5 tests=[AWL=0.074, 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 KdfQXoQ25SzZ; Thu, 20 Jan 2011 17:49:09 -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 385BB3A67AA; Thu, 20 Jan 2011 17:49:09 -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: AvsEABZ1OE2rR7H+/2dsb2JhbACkYXOkI5sKhVAEhG8
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 21 Jan 2011 01:51:53 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8716.cisco.com [10.99.80.23]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0L1pqVe014924; Fri, 21 Jan 2011 01:51:53 GMT
Message-Id: <201101210151.p0L1pqVe014924@sj-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 20 Jan 2011 19:51:51 -0600
To: IETF Administrative Director <iad@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: IETF 83 Venue 
In-Reply-To: <20110119213125.E3D2228C0F4@core3.amsl.com>
References: <20110119213125.E3D2228C0F4@core3.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 21 Jan 2011 01:49:10 -0000

At 03:31 PM 1/19/2011, IETF Administrative Director wrote:
>The IAOC is pleased to announce Paris as the site for IETF 83 from 25 - 30
>March 2012.  The IETF last met in the city in 2005 at IETF 63.
>
>Paris was the number one choice for a European venue in a venue
>preference survey conducted after IETF 78.

I don't know about this... after all, the last time we had an IETF 
there is when EKR blew a gasket at the lack of (real) cookies during 
the breaks. This cannot be overlooked as an isolated incident, or 
hand-waved away.  I wouldn't want to be around him if this were to occur again.

;-)

James

>2012
>IETF 83  Paris 25 - 30 March    Host:  <your name here>


From gonzalo.camarillo@ericsson.com  Fri Jan 21 02:54:55 2011
Return-Path: <gonzalo.camarillo@ericsson.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 2D6023A6910 for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 02:54:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.609
X-Spam-Level: 
X-Spam-Status: No, score=-106.609 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 zX-2iTjaeng3 for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 02:54:54 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id DC2753A691E for <wgchairs@ietf.org>; Fri, 21 Jan 2011 02:54:53 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-ab-4d3966a2ca91
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 4F.26.13987.2A6693D4; Fri, 21 Jan 2011 11:57:38 +0100 (CET)
Received: from [131.160.126.172] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.2.234.1; Fri, 21 Jan 2011 11:57:37 +0100
Message-ID: <4D3966A2.1040102@ericsson.com>
Date: Fri, 21 Jan 2011 12:57:38 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Experiment: tools for remote participation in IETF80
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
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, 21 Jan 2011 10:54:55 -0000

Chairs,

after the last IETF meeting there were some discussions about how to
allow people to participate in the meetings remotely. We already have
the jabber rooms and the (outgoing) mp3 feeds but some chairs felt that
was not enough. The mp3 feeds seemed to be too slow and presentations by
remote participants (which require at least incoming audio) were a
challenge.

A few IETFers have developed a web conferencing and collaboration system
based on IETF protocols such as SIP, XMPP, BFCP, and RTP. They are
willing to make it available for WG chairs who want to try it during the
upcoming IETF in Prague. You can have a look at the system at:

http://www.meetecho.com/

Simon Pietro (who chairs the SPLICES WG) can provide you with more
information about the capabilities of the system and its requirements.
If you are interested in this, please let him know.

Thanks,

Gonzalo

From spromano@unina.it  Fri Jan 21 04:25:46 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 0C7C03A694F for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 04:25:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.322
X-Spam-Level: 
X-Spam-Status: No, score=-99.322 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 sQSWmdIcixxf for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 04:25:44 -0800 (PST)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by core3.amsl.com (Postfix) with ESMTP id F1A803A693C for <wgchairs@ietf.org>; Fri, 21 Jan 2011 04:25:43 -0800 (PST)
Received: from [1.98.191.99] ([94.167.56.230]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id p0LCSFiZ011560 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Jan 2011 13:28:22 +0100
References: <4D3966A2.1040102@ericsson.com>
In-Reply-To: <4D3966A2.1040102@ericsson.com>
Mime-Version: 1.0 (iPhone Mail 8A306)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary=Apple-Mail-2--521904184
Message-Id: <EF85E490-B5FF-4E53-AA33-04FF8BFBD11C@unina.it>
X-Mailer: iPhone Mail (8A306)
From: Simon Pietro Romano <spromano@unina.it>
Subject: Re: Experiment: tools for remote participation in IETF80
Date: Fri, 21 Jan 2011 13:27:37 +0100
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Cc: soci@meetecho.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, 21 Jan 2011 12:25:46 -0000

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

Dear WG chairs,

as Gonzalo anticipated, Meetecho is a web conferencing and collaboration sys=
tem based on protocols devised by the IETF, and as such as standard as possi=
ble.

The system provides several functionality, including:

* moderated audio and video;
* chat;
* presentation sharing
* whiteboarding
* file sharing
* desktop sharing
* polling.

Most (if not all) of these features are implemented by means of standard pro=
tocols. The audio/video functionality, for instance, is made available via S=
IP/RTP (and RTSP as well, if you just want to listen); moderation is achieve=
d by means of BFCP; chat is XMPP-based; presentation and file sharing are ju=
st plain HTTP; and so on.

Besides, being the system based on standard protocols, access to the system i=
s as heterogeneous as it can get: you can either install our dedicated clien=
t (Java based, available for all platforms) which includes all of the above-=
mentioned features, or, if you feel uncomfortable with installing software o=
n your machine, just open your favourite browser and use the web interface w=
e devised. The web interface has no embedded streaming (RTCWEB is still to c=
ome ;) ) but you can just grab any SIP softphone or RTSP player and access t=
he media stream anyway.

Finally, waiting for SIPREC to come up with a standard solution, we also dev=
ised a SMIL-based homemade recording subsystem: this means that all sessions=
 can be recorded and subsequently replayed using a web player, which we hope=
 will be an appreciated improvement over mp3 recordings, jabber logs and min=
utes.

This makes it, in my opinion, a perfect candidate for the remote participati=
on needs of the IETF. As a matter of fact, we already made use of Meetecho t=
o make a remote presentation in Japan, when Lorenzo (a founding member of th=
e Meetecho team) had to present in the MEDIACTRL WG but couldn't make it the=
re in person, and it was quite a success.

Regards to everybody,

Simon

Il giorno 21/gen/2011, alle ore 11:57, Gonzalo Camarillo <Gonzalo.Camarillo@=
ericsson.com> ha scritto:

> Chairs,
>=20
> after the last IETF meeting there were some discussions about how to
> allow people to participate in the meetings remotely. We already have
> the jabber rooms and the (outgoing) mp3 feeds but some chairs felt that
> was not enough. The mp3 feeds seemed to be too slow and presentations by
> remote participants (which require at least incoming audio) were a
> challenge.
>=20
> A few IETFers have developed a web conferencing and collaboration system
> based on IETF protocols such as SIP, XMPP, BFCP, and RTP. They are
> willing to make it available for WG chairs who want to try it during the
> upcoming IETF in Prague. You can have a look at the system at:
>=20
> http://www.meetecho.com/
>=20
> Simon Pietro (who chairs the SPLICES WG) can provide you with more
> information about the capabilities of the system and its requirements.
> If you are interested in this, please let him know.
>=20
> Thanks,
>=20
> Gonzalo
>=20

--Apple-Mail-2--521904184
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><body bgcolor=3D"#FFFFFF"><div><span class=3D"Apple-style-span" style=3D=
"-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-compositio=
n-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color=
: rgba(77, 128, 180, 0.230469); font-size: medium; "><span>Dear WG chairs,</=
span><br><span></span><br><span>as Gonzalo anticipated, Meetecho is a web co=
nferencing and collaboration system based on protocols devised by the IETF, a=
nd as such as standard as possible.</span><br><span></span><br><span>The sys=
tem provides several functionality, including:</span><br><span></span><br><s=
pan>* moderated audio and video;</span><br><span>* chat;</span><br><span>* p=
resentation sharing</span><br><span>* whiteboarding</span><br><span>* file s=
haring</span><br><span>* desktop sharing</span><br><span>* polling.</span><b=
r><span></span><br><span>Most (if not all) of these features are implemented=
 by means of standard protocols. The audio/video functionality, for instance=
, is made available via SIP/RTP (and RTSP as well, if you just want to liste=
n); moderation is achieved by means of BFCP; chat is XMPP-based; presentatio=
n and file sharing are just plain HTTP; and so on.</span><br><span></span><b=
r><span>Besides, being the system based on standard protocols, access to the=
 system is as heterogeneous as it can get: you can either install our dedica=
ted client (Java based, available for all platforms) which includes all of t=
he above-mentioned features, or, if you feel uncomfortable with installing s=
oftware on your machine, just open your favourite browser and use the web in=
terface we devised. The web interface has no embedded streaming (RTCWEB is s=
till to come ;) ) but you can just grab any SIP softphone or RTSP player and=
 access the media stream anyway.</span><br><span></span><br><span>Finally, w=
aiting for SIPREC to come up with a standard solution, we also devised a SMI=
L-based homemade recording subsystem: this means that all sessions can be re=
corded and subsequently replayed using a web player, which we hope will be a=
n appreciated improvement over mp3 recordings, jabber logs and minutes.</spa=
n><br><span></span><br><span>This makes it, in my opinion, a perfect candida=
te for the remote participation needs of the IETF. As a matter of fact, we a=
lready made use of Meetecho to make a remote presentation in Japan, when Lor=
enzo (a founding member of the Meetecho team) had to present in the MEDIACTR=
L WG but couldn't make it there in person, and it was quite a success.</span=
></span></div><div><span class=3D"Apple-style-span" style=3D"-webkit-tap-hig=
hlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rg=
ba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 1=
80, 0.230469); font-size: medium;"><br></span></div><div><span></span><span c=
lass=3D"Apple-style-span" style=3D"-webkit-tap-highlight-color: rgba(26, 26,=
 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469=
); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); font-size:=
 medium;">Regards to everybody,</span></div><div><span class=3D"Apple-style-=
span" style=3D"-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -web=
kit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-compositi=
on-frame-color: rgba(77, 128, 180, 0.230469); font-size: medium;"><br></span=
></div><div><span class=3D"Apple-style-span" style=3D"-webkit-tap-highlight-=
color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175,=
 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.=
230469); font-size: medium;">Simon<br></span><br>Il giorno 21/gen/2011, alle=
 ore 11:57, Gonzalo Camarillo &lt;<a href=3D"mailto:Gonzalo.Camarillo@ericss=
on.com">Gonzalo.Camarillo@ericsson.com</a>&gt; ha scritto:<br><br></div><div=
></div><blockquote type=3D"cite"><div><span>Chairs,</span><br><span></span><=
br><span>after the last IETF meeting there were some discussions about how t=
o</span><br><span>allow people to participate in the meetings remotely. We a=
lready have</span><br><span>the jabber rooms and the (outgoing) mp3 feeds bu=
t some chairs felt that</span><br><span>was not enough. The mp3 feeds seemed=
 to be too slow and presentations by</span><br><span>remote participants (wh=
ich require at least incoming audio) were a</span><br><span>challenge.</span=
><br><span></span><br><span>A few IETFers have developed a web conferencing a=
nd collaboration system</span><br><span>based on IETF protocols such as SIP,=
 XMPP, BFCP, and RTP. They are</span><br><span>willing to make it available f=
or WG chairs who want to try it during the</span><br><span>upcoming IETF in P=
rague. You can have a look at the system at:</span><br><span></span><br><spa=
n><a href=3D"http://www.meetecho.com/">http://www.meetecho.com/</a></span><b=
r><span></span><br><span>Simon Pietro (who chairs the SPLICES WG) can provid=
e you with more</span><br><span>information about the capabilities of the sy=
stem and its requirements.</span><br><span>If you are interested in this, pl=
ease let him know.</span><br><span></span><br><span>Thanks,</span><br><span>=
</span><br><span>Gonzalo</span><br><span></span><br></div></blockquote></bod=
y></html>=

--Apple-Mail-2--521904184--

From mehmet.ersue@nsn.com  Fri Jan 21 04:43:47 2011
Return-Path: <mehmet.ersue@nsn.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 D1CA23A6958 for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 04:43:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.784
X-Spam-Level: 
X-Spam-Status: No, score=-102.784 tagged_above=-999 required=5 tests=[AWL=-0.185, 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 jM80smduWNse for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 04:43:46 -0800 (PST)
Received: from mumrelp001.nsn-inter.net (mumrelp001.nsn-inter.net [93.183.13.135]) by core3.amsl.com (Postfix) with ESMTP id 7E43B3A6952 for <wgchairs@ietf.org>; Fri, 21 Jan 2011 04:43:46 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by mumrelp001.nsn-inter.net (8.13.8/8.13.8) with ESMTP id p0LCkUjJ028457 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 21 Jan 2011 13:46:30 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0LCkUDN021839; Fri, 21 Jan 2011 13:46:30 +0100
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 21 Jan 2011 13:46:30 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Experiment: tools for remote participation in IETF80
Date: Fri, 21 Jan 2011 13:46:29 +0100
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6401812BB3@DEMUEXC006.nsn-intra.net>
In-Reply-To: <4D3966A2.1040102@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Experiment: tools for remote participation in IETF80
Thread-Index: Acu5WgyGU6+e4eSnThWhqszKQw3g3gADdnEA
References: <4D3966A2.1040102@ericsson.com>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>, <wgchairs@ietf.org>
X-OriginalArrivalTime: 21 Jan 2011 12:46:30.0301 (UTC) FILETIME=[39D2C4D0:01CBB969]
X-Scanned-By: MIMEDefang 2.71 on 93.183.13.135
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, 21 Jan 2011 12:43:48 -0000

Hi Gonzalo,

did you check the experiment already with the IETF=20
secretary and network responsibles (e.g. Joel Jaegli)?
What are the implications of this kind of streaming=20
on the IETF network?

Using tools based on IETF standards is valuable,=20
however what is the technical add-on or benefit=20
compared to Cisco Webex IETF secretary uses right=20
now? IOW, why should they change?

Cheers,=20
Mehmet=20


> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of ext Gonzalo Camarillo
> Sent: Friday, January 21, 2011 11:58 AM
> To: wgchairs@ietf.org
> Subject: Experiment: tools for remote participation in IETF80
>=20
> Chairs,
>=20
> after the last IETF meeting there were some discussions about how to
> allow people to participate in the meetings remotely. We already have
> the jabber rooms and the (outgoing) mp3 feeds but some chairs felt
that
> was not enough. The mp3 feeds seemed to be too slow and presentations
> by
> remote participants (which require at least incoming audio) were a
> challenge.
>=20
> A few IETFers have developed a web conferencing and collaboration
> system
> based on IETF protocols such as SIP, XMPP, BFCP, and RTP. They are
> willing to make it available for WG chairs who want to try it during
> the
> upcoming IETF in Prague. You can have a look at the system at:
>=20
> http://www.meetecho.com/
>=20
> Simon Pietro (who chairs the SPLICES WG) can provide you with more
> information about the capabilities of the system and its requirements.
> If you are interested in this, please let him know.
>=20
> Thanks,
>=20
> Gonzalo

From gonzalo.camarillo@ericsson.com  Fri Jan 21 05:14:23 2011
Return-Path: <gonzalo.camarillo@ericsson.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 C579B3A68F6 for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 05:14:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.609
X-Spam-Level: 
X-Spam-Status: No, score=-106.609 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 ZiD0742Zy3RH for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 05:14:22 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 6B2F53A6918 for <wgchairs@ietf.org>; Fri, 21 Jan 2011 05:14:22 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-a5-4d3987532e44
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 63.AB.13987.357893D4; Fri, 21 Jan 2011 14:17:07 +0100 (CET)
Received: from [131.160.126.172] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.2.234.1; Fri, 21 Jan 2011 14:17:06 +0100
Message-ID: <4D398752.50608@ericsson.com>
Date: Fri, 21 Jan 2011 15:17:06 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
Subject: Re: Experiment: tools for remote participation in IETF80
References: <4D3966A2.1040102@ericsson.com> <80A0822C5E9A4440A5117C2F4CD36A6401812BB3@DEMUEXC006.nsn-intra.net>
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6401812BB3@DEMUEXC006.nsn-intra.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
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: Fri, 21 Jan 2011 13:14:23 -0000

Hi,

no, this is just an unofficial experiment; it is not supported by the
secretary in any way. This type of experiment can be useful to gather
requirements and understand the needs we have for remote participation.

As I said in my original email, in the last IETF meeting, some WG chairs
thought the current tools did not meet all their requirements. Some of
them used tools such as Skype in their sessions. This is just another
alternative for chairs to choose from. Regarding the impact on the
network, the impact of a WG using this would be comparable to a WG using
any other tool such as Skype.

Cheers,

Gonzalo


On 21/01/2011 2:46 PM, Ersue, Mehmet (NSN - DE/Munich) wrote:
> Hi Gonzalo,
> 
> did you check the experiment already with the IETF 
> secretary and network responsibles (e.g. Joel Jaegli)?
> What are the implications of this kind of streaming 
> on the IETF network?
> 
> Using tools based on IETF standards is valuable, 
> however what is the technical add-on or benefit 
> compared to Cisco Webex IETF secretary uses right 
> now? IOW, why should they change?
> 
> Cheers, 
> Mehmet 
> 
> 
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
>> Behalf Of ext Gonzalo Camarillo
>> Sent: Friday, January 21, 2011 11:58 AM
>> To: wgchairs@ietf.org
>> Subject: Experiment: tools for remote participation in IETF80
>>
>> Chairs,
>>
>> after the last IETF meeting there were some discussions about how to
>> allow people to participate in the meetings remotely. We already have
>> the jabber rooms and the (outgoing) mp3 feeds but some chairs felt
> that
>> was not enough. The mp3 feeds seemed to be too slow and presentations
>> by
>> remote participants (which require at least incoming audio) were a
>> challenge.
>>
>> A few IETFers have developed a web conferencing and collaboration
>> system
>> based on IETF protocols such as SIP, XMPP, BFCP, and RTP. They are
>> willing to make it available for WG chairs who want to try it during
>> the
>> upcoming IETF in Prague. You can have a look at the system at:
>>
>> http://www.meetecho.com/
>>
>> Simon Pietro (who chairs the SPLICES WG) can provide you with more
>> information about the capabilities of the system and its requirements.
>> If you are interested in this, please let him know.
>>
>> Thanks,
>>
>> Gonzalo


From joelja@bogus.com  Fri Jan 21 05:40:23 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 D84003A6916 for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 05:40:23 -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 fvncc1vYSAtk for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 05:40:22 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 5CF4B3A6914 for <wgchairs@ietf.org>; Fri, 21 Jan 2011 05:40:22 -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 p0LDh1Fa074638 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 21 Jan 2011 13:43:02 GMT (envelope-from joelja@bogus.com)
Message-ID: <4D398D65.2020703@bogus.com>
Date: Fri, 21 Jan 2011 05:43:01 -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: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
Subject: Re: Experiment: tools for remote participation in IETF80
References: <4D3966A2.1040102@ericsson.com> <80A0822C5E9A4440A5117C2F4CD36A6401812BB3@DEMUEXC006.nsn-intra.net>
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6401812BB3@DEMUEXC006.nsn-intra.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org, Russ Housley <housley@vigilsec.com>, ext Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Ray Pelletier <rpelletier@isoc.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, 21 Jan 2011 13:40:23 -0000

On 1/21/11 4:46 AM, Ersue, Mehmet (NSN - DE/Munich) wrote:
> Hi Gonzalo,
> 
> did you check the experiment already with the IETF 
> secretary and network responsibles (e.g. Joel Jaegli)?
> What are the implications of this kind of streaming 
> on the IETF network?

I'm neither an obstacle to overcome or nor the arbiter of experiments.

I would suggest that you dicuss anything that you want to do at scale
with the IAD Ray Pelletier, and the IETF Chair.

> Using tools based on IETF standards is valuable, 
> however what is the technical add-on or benefit 
> compared to Cisco Webex IETF secretary uses right 
> now? IOW, why should they change?
> 
> Cheers, 
> Mehmet 
> 
> 
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
>> Behalf Of ext Gonzalo Camarillo
>> Sent: Friday, January 21, 2011 11:58 AM
>> To: wgchairs@ietf.org
>> Subject: Experiment: tools for remote participation in IETF80
>>
>> Chairs,
>>
>> after the last IETF meeting there were some discussions about how to
>> allow people to participate in the meetings remotely. We already have
>> the jabber rooms and the (outgoing) mp3 feeds but some chairs felt
> that
>> was not enough. The mp3 feeds seemed to be too slow and presentations
>> by
>> remote participants (which require at least incoming audio) were a
>> challenge.
>>
>> A few IETFers have developed a web conferencing and collaboration
>> system
>> based on IETF protocols such as SIP, XMPP, BFCP, and RTP. They are
>> willing to make it available for WG chairs who want to try it during
>> the
>> upcoming IETF in Prague. You can have a look at the system at:
>>
>> http://www.meetecho.com/
>>
>> Simon Pietro (who chairs the SPLICES WG) can provide you with more
>> information about the capabilities of the system and its requirements.
>> If you are interested in this, please let him know.
>>
>> Thanks,
>>
>> Gonzalo
> 


From marc.blanchet@viagenie.ca  Fri Jan 21 05:50:36 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 0ACB23A6990 for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 05:50:36 -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 3kROJdiN5Q3m for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 05:50:35 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 5E6E63A6984 for <wgchairs@ietf.org>; Fri, 21 Jan 2011 05:50:34 -0800 (PST)
Received: from mbl.lan (unknown [IPv6:2607:f2c0:f00e:6100:5ab0:35ff:fe6a:294a]) by jazz.viagenie.ca (Postfix) with ESMTPSA id A8A4720DC2 for <wgchairs@ietf.org>; Fri, 21 Jan 2011 08:53:16 -0500 (EST)
Message-ID: <4D398FCC.6090507@viagenie.ca>
Date: Fri, 21 Jan 2011 08:53:16 -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: wgchairs@ietf.org
Subject: Re: Experiment: tools for remote participation in IETF80
References: <4D3966A2.1040102@ericsson.com>
In-Reply-To: <4D3966A2.1040102@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
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, 21 Jan 2011 13:50:36 -0000

maybe I'm missing something, but that web site has a download menu with 
no downloadable software and almost no documentation. So it is pretty 
difficult to get any sense of the applicability of such software, not 
talking about trying it out in advance of the meeting to see how it fits.

Am I missing something too obvious?

Marc.

Le 11-01-21 05:57, Gonzalo Camarillo a écrit :
> Chairs,
>
> after the last IETF meeting there were some discussions about how to
> allow people to participate in the meetings remotely. We already have
> the jabber rooms and the (outgoing) mp3 feeds but some chairs felt that
> was not enough. The mp3 feeds seemed to be too slow and presentations by
> remote participants (which require at least incoming audio) were a
> challenge.
>
> A few IETFers have developed a web conferencing and collaboration system
> based on IETF protocols such as SIP, XMPP, BFCP, and RTP. They are
> willing to make it available for WG chairs who want to try it during the
> upcoming IETF in Prague. You can have a look at the system at:
>
> http://www.meetecho.com/
>
> Simon Pietro (who chairs the SPLICES WG) can provide you with more
> information about the capabilities of the system and its requirements.
> If you are interested in this, please let him know.
>
> Thanks,
>
> Gonzalo


-- 
=========
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 adam@nostrum.com  Fri Jan 21 07:30:51 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 07C813A6A09 for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 07:30:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.492
X-Spam-Level: 
X-Spam-Status: No, score=-102.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 MBCXAsWZ4vOg for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 07:30:50 -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 8567B3A6A1A for <wgchairs@ietf.org>; Fri, 21 Jan 2011 07:30:49 -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 p0LFXXMk084183 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 21 Jan 2011 09:33:34 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4D39A74D.2020501@nostrum.com>
Date: Fri, 21 Jan 2011 09:33:33 -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: Marc Blanchet <marc.blanchet@viagenie.ca>
Subject: Re: Experiment: tools for remote participation in IETF80
References: <4D3966A2.1040102@ericsson.com> <4D398FCC.6090507@viagenie.ca>
In-Reply-To: <4D398FCC.6090507@viagenie.ca>
Content-Type: multipart/alternative; boundary="------------030403040005050302030506"
Received-SPF: pass (nostrum.com: 75.53.54.121 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: Fri, 21 Jan 2011 15:30:51 -0000

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

On 1/21/11 7:53 AM, Marc Blanchet wrote:
> maybe I'm missing something, but that web site has a download menu 
> with no downloadable software and almost no documentation.

I suspect that the thing you're missing is this statement on the 
download page: "You have to login to download our client," followed by 
links to register a new 
account.<http://www.meetecho.com/index.php?option=com_comprofiler&task=registers&Itemid=66&lang=en>

/a

--------------030403040005050302030506
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    On 1/21/11 7:53 AM, Marc Blanchet wrote:
    <blockquote cite="mid:4D398FCC.6090507@viagenie.ca" type="cite">maybe
      I'm missing something, but that web site has a download menu with
      no downloadable software and almost no documentation.</blockquote>
    <br>
    I suspect that the thing you're missing is this statement on the
    download page: "You have to login to download our client," followed
    by links to register a new account.<a class="mod_login"
href="http://www.meetecho.com/index.php?option=com_comprofiler&amp;task=registers&amp;Itemid=66&amp;lang=en"></a><br>
    <br>
    /a<br>
  </body>
</html>

--------------030403040005050302030506--

From mary.ietf.barnes@gmail.com  Fri Jan 21 08:01:28 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 8E3343A6A36; Fri, 21 Jan 2011 08:01:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.306
X-Spam-Level: 
X-Spam-Status: No, score=-103.306 tagged_above=-999 required=5 tests=[AWL=0.292, 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 PUrdQK8Jj+me; Fri, 21 Jan 2011 08:01:27 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 5770C3A6A35; Fri, 21 Jan 2011 08:01:27 -0800 (PST)
Received: by yxt33 with SMTP id 33so645960yxt.31 for <multiple recipients>; Fri, 21 Jan 2011 08:04: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=hMB4sA/b0JgF4gFUDUvvWtwa490ir0S4N4CLyI9LGYg=; b=xO+QQxMIRCLB6Ld6V986gTn2fvxiB847txEgWCVC8vCqcbG/edt5Blli/0d7Jz2FXX Z+ukAonsYAlXC7Sxcb9Pm6nqHkIoaf4qn2rzywAe0H7RhdG+IyQWTMW6DGMCCAVwBLZM wluGfgwtET5O3Shu957r7GSNQ1z7Hlfxfisao=
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=bpYETyI2mfzuc/dUvJ1hLi5droS7TYdbsN2BMzPjXN91Ng8RE+5SyMSGioo3dMHawj QzlJGQR0eHpQ5lTY5xbReCKQl3kw24JJebtJHUeEyo7F01MkbUk2beaOru7bo2kW5dH6 2yIp91SKsqSLOkyq7FxIHCMx6kIWeXG740Fl4=
MIME-Version: 1.0
Received: by 10.42.173.71 with SMTP id q7mr1001487icz.65.1295625852971; Fri, 21 Jan 2011 08:04:12 -0800 (PST)
Received: by 10.42.202.12 with HTTP; Fri, 21 Jan 2011 08:04:12 -0800 (PST)
In-Reply-To: <201101210151.p0L1pqVe014924@sj-core-2.cisco.com>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com>
Date: Fri, 21 Jan 2011 10:04:12 -0600
Message-ID: <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com>
Subject: Re: IETF 83 Venue
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "James M. Polk" <jmpolk@cisco.com>
Content-Type: multipart/alternative; boundary=90e6ba6e8d2aba6c6f049a5d66bd
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, 21 Jan 2011 16:01:28 -0000

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

If it's the same conference center that we were at for IETF-63, there should
be few complaints about food given that there is a very nice (real) food
market in the shopping area in the Palais de Congres - i.e., if there aren't
enough cookies for you at the meeting, then you can go buy a whole package
at the food market.

Mary.

On Thu, Jan 20, 2011 at 7:51 PM, James M. Polk <jmpolk@cisco.com> wrote:

> At 03:31 PM 1/19/2011, IETF Administrative Director wrote:
>
>> The IAOC is pleased to announce Paris as the site for IETF 83 from 25 - 30
>> March 2012.  The IETF last met in the city in 2005 at IETF 63.
>>
>> Paris was the number one choice for a European venue in a venue
>> preference survey conducted after IETF 78.
>>
>
> I don't know about this... after all, the last time we had an IETF there is
> when EKR blew a gasket at the lack of (real) cookies during the breaks. This
> cannot be overlooked as an isolated incident, or hand-waved away.  I
> wouldn't want to be around him if this were to occur again.
>
> ;-)
>
> James
>
>
>  2012
>> IETF 83  Paris 25 - 30 March    Host:  <your name here>
>>
>
>

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

If it&#39;s the same conference center that we were at for IETF-63, there s=
hould be few complaints about food given that there is a very nice (real) f=
ood market in the shopping area in the Palais de Congres - i.e., if there a=
ren&#39;t enough cookies for you at the meeting, then you can go buy a whol=
e package at the food market.<div>
<br></div><div>Mary.<br><div><br></div><div>On Thu, Jan 20, 2011 at 7:51 PM=
, James M. Polk <span dir=3D"ltr">&lt;<a href=3D"mailto:jmpolk@cisco.com">j=
mpolk@cisco.com</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;">
<div class=3D"im">At 03:31 PM 1/19/2011, IETF Administrative Director wrote=
:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IAOC is pleased to announce Paris as the site for IETF 83 from 25 - 30<=
br>
March 2012. =A0The IETF last met in the city in 2005 at IETF 63.<br>
<br>
Paris was the number one choice for a European venue in a venue<br>
preference survey conducted after IETF 78.<br>
</blockquote>
<br></div>
I don&#39;t know about this... after all, the last time we had an IETF ther=
e is when EKR blew a gasket at the lack of (real) cookies during the breaks=
. This cannot be overlooked as an isolated incident, or hand-waved away. =
=A0I wouldn&#39;t want to be around him if this were to occur again.<br>

<br>
;-)<br><font color=3D"#888888">
<br>
James</font><div><div></div><div class=3D"h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
2012<br>
IETF 83 =A0Paris 25 - 30 March =A0 =A0Host: =A0&lt;your name here&gt;<br>
</blockquote>
<br>
</div></div></blockquote></div><br></div></div>

--90e6ba6e8d2aba6c6f049a5d66bd--

From spromano@unina.it  Fri Jan 21 08:32:12 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 18B213A6A13 for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 08:32:12 -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 IIg1SUgzehi6 for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 08:32:11 -0800 (PST)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by core3.amsl.com (Postfix) with ESMTP id A12693A69F7 for <wgchairs@ietf.org>; Fri, 21 Jan 2011 08:32:10 -0800 (PST)
Received: from [151.81.162.56] ([151.81.162.56]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id p0LGYrbp017981 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 21 Jan 2011 17:34:54 +0100
Message-ID: <4D39B5A2.5090709@unina.it>
Date: Fri, 21 Jan 2011 17:34:42 +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: Marc Blanchet <marc.blanchet@viagenie.ca>
Subject: Re: Experiment: tools for remote participation in IETF80
References: <4D3966A2.1040102@ericsson.com> <4D398FCC.6090507@viagenie.ca>
In-Reply-To: <4D398FCC.6090507@viagenie.ca>
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, 21 Jan 2011 16:32:12 -0000

Hi Marc,

you actually need to register in order to access the download section. I 
apologize if it is not enough in evidence on the web site. You will find 
there all versions (Windows, Linux and MAC) of our desktop client, which 
is integrated in the well known XMPP client called Spark (btw, people 
who are used to join the usual IETF conference rooms will be able to 
log-in both on 'jabber.ietf.org' and on our conference server from the 
same app). If someone is interested in giving a try to the mobile 
versions of the client app (Android and  Blackberry, since we cannot 
release our I-Phone and Symbian apps as yet), just drop an e-mail to 
info@meetecho.com. We ask people to send an e-mail to such address in 
order to be enabled and test the platform.
This said, I once again stress the point that if you are not willing to 
install any dedicated client, you can still access most of the provided 
functionality through your browser, plus any standard (VoIP or PSTN) 
phone (for the audio/video streams).
We do appreciate feedback from all of you guys; being capable to deal 
with potential issues/requests in advance will be fundamental for us. 
Our main objective at the upcoming IETF will be to seize the unique 
opportunity of gathering as much input as possible from the community in 
order to improve our platform. So, please don't hesitate even if you 
have to be harsh ;-)!

Cheers,

Simon

Il 21/01/2011 14:53, Marc Blanchet ha scritto:
> maybe I'm missing something, but that web site has a download menu 
> with no downloadable software and almost no documentation. So it is 
> pretty difficult to get any sense of the applicability of such 
> software, not talking about trying it out in advance of the meeting to 
> see how it fits.
>
> Am I missing something too obvious?
>
> Marc.
>
> Le 11-01-21 05:57, Gonzalo Camarillo a écrit :
>> Chairs,
>>
>> after the last IETF meeting there were some discussions about how to
>> allow people to participate in the meetings remotely. We already have
>> the jabber rooms and the (outgoing) mp3 feeds but some chairs felt that
>> was not enough. The mp3 feeds seemed to be too slow and presentations by
>> remote participants (which require at least incoming audio) were a
>> challenge.
>>
>> A few IETFers have developed a web conferencing and collaboration system
>> based on IETF protocols such as SIP, XMPP, BFCP, and RTP. They are
>> willing to make it available for WG chairs who want to try it during the
>> upcoming IETF in Prague. You can have a look at the system at:
>>
>> http://www.meetecho.com/
>>
>> Simon Pietro (who chairs the SPLICES WG) can provide you with more
>> information about the capabilities of the system and its requirements.
>> If you are interested in this, please let him know.
>>
>> Thanks,
>>
>> Gonzalo
>
>

-- 
                             _\\|//_
                             ( 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 tme@americafree.tv  Fri Jan 21 09:26:23 2011
Return-Path: <tme@americafree.tv>
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 815F43A6A68; Fri, 21 Jan 2011 09:26:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.273
X-Spam-Level: 
X-Spam-Status: No, score=-102.273 tagged_above=-999 required=5 tests=[AWL=0.326, 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 g-7t-PGX+uou; Fri, 21 Jan 2011 09:26:22 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 894883A6A67; Fri, 21 Jan 2011 09:26:22 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 9707B9B4F203; Fri, 21 Jan 2011 12:29:08 -0500 (EST)
Subject: Re: IETF 83 Venue
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com>
Date: Fri, 21 Jan 2011 12:29:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5BE5F222-1495-4137-9E43-7D214954EC93@americafree.tv>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: iaoc@ietf.org, ietf@ietf.org, iab@iab.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, 21 Jan 2011 17:26:23 -0000

On Jan 21, 2011, at 11:04 AM, Mary Barnes wrote:

> If it's the same conference center that we were at for IETF-63, there =
should be few complaints about food given that there is a very nice =
(real) food market in the shopping area in the Palais de Congres - i.e., =
if there aren't enough cookies for you at the meeting, then you can go =
buy a whole package at the food market.
>=20

It is - and  the main hotel is actually the one connected to that venue.=20=


Regards
Marshall


> Mary.
>=20
> On Thu, Jan 20, 2011 at 7:51 PM, James M. Polk <jmpolk@cisco.com> =
wrote:
> At 03:31 PM 1/19/2011, IETF Administrative Director wrote:
> The IAOC is pleased to announce Paris as the site for IETF 83 from 25 =
- 30
> March 2012.  The IETF last met in the city in 2005 at IETF 63.
>=20
> Paris was the number one choice for a European venue in a venue
> preference survey conducted after IETF 78.
>=20
> I don't know about this... after all, the last time we had an IETF =
there is when EKR blew a gasket at the lack of (real) cookies during the =
breaks. This cannot be overlooked as an isolated incident, or hand-waved =
away.  I wouldn't want to be around him if this were to occur again.
>=20
> ;-)
>=20
> James
>=20
>=20
> 2012
> IETF 83  Paris 25 - 30 March    Host:  <your name here>
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From ole@cisco.com  Fri Jan 21 08:08:13 2011
Return-Path: <ole@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 A7B803A6A3F; Fri, 21 Jan 2011 08:08:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.577
X-Spam-Level: 
X-Spam-Status: No, score=-110.577 tagged_above=-999 required=5 tests=[AWL=0.022, 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 Ft7BpS7CCM0L; Fri, 21 Jan 2011 08:08:12 -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 BA3D83A6A3B; Fri, 21 Jan 2011 08:08:12 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-3.cisco.com with ESMTP; 21 Jan 2011 16:10:57 +0000
Received: from [10.24.17.59] ([10.24.17.59]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0LGAs9q006553; Fri, 21 Jan 2011 16:10:55 GMT
Date: Fri, 21 Jan 2011 08:10:54 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: IETF 83 Venue
In-Reply-To: <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com>
Message-ID: <alpine.OSX.2.01.1101210808570.70222@macpro.local>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Fri, 21 Jan 2011 09:40:06 -0800
Cc: iaoc@ietf.org, ietf@ietf.org, iab@iab.org, wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
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, 21 Jan 2011 16:08:13 -0000

Does anyone see the irony of us even discussing concerns about, of all 
things, FOOD when it comes to Paris?

I can't wait to back to London :-)

Ole


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




From barryleiba.mailing.lists@gmail.com  Fri Jan 21 13:36:06 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 611A33A6A51 for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 13:36:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.808
X-Spam-Level: 
X-Spam-Status: No, score=-102.808 tagged_above=-999 required=5 tests=[AWL=0.169, 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 p5kI1xFqhC0Q for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 13:36:05 -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 354CC3A67F8 for <wgchairs@ietf.org>; Fri, 21 Jan 2011 13:36:05 -0800 (PST)
Received: by iyi42 with SMTP id 42so2317024iyi.31 for <wgchairs@ietf.org>; Fri, 21 Jan 2011 13:38:52 -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 :content-transfer-encoding; bh=2uu/ecQ7PElaQk1HOAMOA2gxY4ELhojmqWVhp18ENWk=; b=ky+iQzmFnJLPKTb+qLwewUax7wK8GQ0glFE9uXtO5o6xS8DLDLSy54+tiSDbT9TUPc fiE1geaYIjtY2dLfEU5NPKAQcu+SvkDJO8hFNl+a/a5UdmG/MLztI8/E3JYacEzhi4Ae 7lUZ32aPFNf5JbrH6KtDqfZhau7op1WTa81fI=
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 :content-transfer-encoding; b=EgX4KIW7+LmgJ6Au8bNQ6PUA8n5KQs2oHfCffZzeUtgasAkNUJw4r9n/oN2pjpbgFn GJ6dc4HRbSTeWG4EPVJNejruYbWB/nNxsmXTWwAW5LImpq569M4kqCg+h0ji7rIApXlS g1azLbKO+MtmWSJijM/x7ZTHlEAQdtgLYa/9s=
MIME-Version: 1.0
Received: by 10.42.218.200 with SMTP id hr8mr1456972icb.219.1295645932024; Fri, 21 Jan 2011 13:38:52 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.227.193 with HTTP; Fri, 21 Jan 2011 13:38:51 -0800 (PST)
In-Reply-To: <C95D482B.47D01%joe.hildebrand@webex.com>
References: <9B57C850BB53634CACEC56EF4853FF65344BB6DA@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <C95D482B.47D01%joe.hildebrand@webex.com>
Date: Fri, 21 Jan 2011 16:38:51 -0500
X-Google-Sender-Auth: oECcoFfESfvNlbLWE8IXVW6BND0
Message-ID: <AANLkTi=zw3+Vr+aPLewiuiDNQMwajkRDVijbvD7AkenV@mail.gmail.com>
Subject: Re: RFC Style guide
From: Barry Leiba <barryleiba@computer.org>
To: Joe Hildebrand <joe.hildebrand@webex.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "wgchairs@ietf.org 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, 21 Jan 2011 21:36:06 -0000

>> One of the TRSE's reports mentioned this as an example of some longer-te=
rm
>> work that the RSE needs to do.
>
> Sorry that I haven't followed this closely enough, but Glen has now been
> formally the RSE since 2010-04-20?
>
> Is it appropriate and respectful for us to start asking questions of the =
RSE
> and RSAG yet about things we'd like to see for the future? =A0There were =
a few
> questions I asked in Beijing that were met with "please wait for a few
> months".

Glen has never been, and never will be, formally the RSE.  Glen's the
Transitional RSE, and he expects to turn things over to the "formal"
RSE before his year is up.

Barry

From Glenn@RiverOnce.com  Fri Jan 21 14:01:20 2011
Return-Path: <Glenn@RiverOnce.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 B0E1E3A6AA9 for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 14:01:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, 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 sWOECMRm6e7a for <wgchairs@core3.amsl.com>; Fri, 21 Jan 2011 14:01:19 -0800 (PST)
Received: from sbh11.songbird.com (sbh11.songbird.com [72.52.113.11]) by core3.amsl.com (Postfix) with ESMTP id D2C353A6AAC for <wgchairs@ietf.org>; Fri, 21 Jan 2011 14:01:19 -0800 (PST)
Received: from [10.0.1.3] (c-68-51-252-202.hsd1.fl.comcast.net [68.51.252.202]) (authenticated bits=0) by sbh11.songbird.com (8.13.8/8.13.8) with ESMTP id p0LM3xGk031758 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Jan 2011 14:04:00 -0800
Subject: Re: RFC Style guide
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Glenn Kowack <Glenn@RiverOnce.com>
In-Reply-To: <AANLkTi=zw3+Vr+aPLewiuiDNQMwajkRDVijbvD7AkenV@mail.gmail.com>
Date: Fri, 21 Jan 2011 17:03:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D10C8A96-81B7-4BA6-B672-442A892D135F@RiverOnce.com>
References: <9B57C850BB53634CACEC56EF4853FF65344BB6DA@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <C95D482B.47D01%joe.hildebrand@webex.com> <AANLkTi=zw3+Vr+aPLewiuiDNQMwajkRDVijbvD7AkenV@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh11.songbird.com [72.52.113.11]); Fri, 21 Jan 2011 14:04:01 -0800 (PST)
Cc: "wgchairs@ietf.org 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, 21 Jan 2011 22:01:20 -0000

On Jan 21, 2011, at 4:38 PM, Barry Leiba wrote:

>>> One of the TRSE's reports mentioned this as an example of some =
longer-term
>>> work that the RSE needs to do.
>>=20
>> Sorry that I haven't followed this closely enough, but Glen has now =
been
>> formally the RSE since 2010-04-20?
>>=20
>> Is it appropriate and respectful for us to start asking questions of =
the RSE
>> and RSAG yet about things we'd like to see for the future?  There =
were a few
>> questions I asked in Beijing that were met with "please wait for a =
few
>> months".
>=20
> Glen has never been, and never will be, formally the RSE.  Glen's the
> Transitional RSE, and he expects to turn things over to the "formal"
> RSE before his year is up.
>=20
> Barry

Barry is generally right (see below).  However, there's no harm in =
discussing
issues as long as everyone appreciates that it would not be proper for =
us (or
me) to start making a lot of things happen just before the new  RSE =
shows
up. That could pull the rug out from under them.  We want to give the =
new
RSE full support for a clean start and a chance to start getting things =
right
w/r/t the "big picture" that they develop with the community.

So, if there are things you'd like to discuss, please feel free to bring =
them to
this list and I'll make sure they are carried over during the =
transition.

(*) Actually, I have formally been the RSE since 19 April, but with the
understanding that this is a transitional period, consistent with the =
points
I raised above.
http://www.rfc-editor.org/pipermail/rfc-interest/2010-April/001743.html

thanks,
Glenn


=20


From gonzalo.camarillo@ericsson.com  Sun Jan 23 01:02:17 2011
Return-Path: <gonzalo.camarillo@ericsson.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 503DD3A681B for <wgchairs@core3.amsl.com>; Sun, 23 Jan 2011 01:02:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.615
X-Spam-Level: 
X-Spam-Status: No, score=-106.615 tagged_above=-999 required=5 tests=[AWL=-0.016, 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 7GCxOzTt5JJm for <wgchairs@core3.amsl.com>; Sun, 23 Jan 2011 01:02:16 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 085F53A67D7 for <wgchairs@ietf.org>; Sun, 23 Jan 2011 01:02:15 -0800 (PST)
X-AuditID: c1b4fb39-b7cfbae000005c8e-d3-4d3bef424aa4
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 3D.28.23694.24FEB3D4; Sun, 23 Jan 2011 10:05:06 +0100 (CET)
Received: from [131.160.126.172] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.2.234.1; Sun, 23 Jan 2011 10:05:06 +0100
Message-ID: <4D3BEF42.10906@ericsson.com>
Date: Sun, 23 Jan 2011 11:05:06 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Simon Pietro Romano <spromano@unina.it>
Subject: Re: Experiment: tools for remote participation in IETF80
References: <4D3966A2.1040102@ericsson.com> <4D398FCC.6090507@viagenie.ca> <4D39B5A2.5090709@unina.it>
In-Reply-To: <4D39B5A2.5090709@unina.it>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, "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: Sun, 23 Jan 2011 09:02:17 -0000

Hi Simon Pietro,

I have received a few (off-list) emails from WG chairs who would like to
evaluate the system in order to decide whether to use it in their
sessions. Most pointed out that having this type of information
available on a web page would make their testing much easier.

Thanks,

Gonzalo

On 21/01/2011 6:34 PM, Simon Pietro Romano wrote:
> Hi Marc,
> 
> you actually need to register in order to access the download section. I 
> apologize if it is not enough in evidence on the web site. You will find 
> there all versions (Windows, Linux and MAC) of our desktop client, which 
> is integrated in the well known XMPP client called Spark (btw, people 
> who are used to join the usual IETF conference rooms will be able to 
> log-in both on 'jabber.ietf.org' and on our conference server from the 
> same app). If someone is interested in giving a try to the mobile 
> versions of the client app (Android and  Blackberry, since we cannot 
> release our I-Phone and Symbian apps as yet), just drop an e-mail to 
> info@meetecho.com. We ask people to send an e-mail to such address in 
> order to be enabled and test the platform.
> This said, I once again stress the point that if you are not willing to 
> install any dedicated client, you can still access most of the provided 
> functionality through your browser, plus any standard (VoIP or PSTN) 
> phone (for the audio/video streams).
> We do appreciate feedback from all of you guys; being capable to deal 
> with potential issues/requests in advance will be fundamental for us. 
> Our main objective at the upcoming IETF will be to seize the unique 
> opportunity of gathering as much input as possible from the community in 
> order to improve our platform. So, please don't hesitate even if you 
> have to be harsh ;-)!
> 
> Cheers,
> 
> Simon
> 
> Il 21/01/2011 14:53, Marc Blanchet ha scritto:
>> maybe I'm missing something, but that web site has a download menu 
>> with no downloadable software and almost no documentation. So it is 
>> pretty difficult to get any sense of the applicability of such 
>> software, not talking about trying it out in advance of the meeting to 
>> see how it fits.
>>
>> Am I missing something too obvious?
>>
>> Marc.
>>
>> Le 11-01-21 05:57, Gonzalo Camarillo a écrit :
>>> Chairs,
>>>
>>> after the last IETF meeting there were some discussions about how to
>>> allow people to participate in the meetings remotely. We already have
>>> the jabber rooms and the (outgoing) mp3 feeds but some chairs felt that
>>> was not enough. The mp3 feeds seemed to be too slow and presentations by
>>> remote participants (which require at least incoming audio) were a
>>> challenge.
>>>
>>> A few IETFers have developed a web conferencing and collaboration system
>>> based on IETF protocols such as SIP, XMPP, BFCP, and RTP. They are
>>> willing to make it available for WG chairs who want to try it during the
>>> upcoming IETF in Prague. You can have a look at the system at:
>>>
>>> http://www.meetecho.com/
>>>
>>> Simon Pietro (who chairs the SPLICES WG) can provide you with more
>>> information about the capabilities of the system and its requirements.
>>> If you are interested in this, please let him know.
>>>
>>> Thanks,
>>>
>>> Gonzalo
>>
>>
> 


From spromano@unina.it  Sun Jan 23 02:20:32 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 B56103A683B for <wgchairs@core3.amsl.com>; Sun, 23 Jan 2011 02:20:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.322
X-Spam-Level: 
X-Spam-Status: No, score=-99.322 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  MIME_QP_LONG_LINE=1.396, 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 JhI8rDaU8UxP for <wgchairs@core3.amsl.com>; Sun, 23 Jan 2011 02:20:31 -0800 (PST)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by core3.amsl.com (Postfix) with ESMTP id 66B833A67FD for <wgchairs@ietf.org>; Sun, 23 Jan 2011 02:20:30 -0800 (PST)
Received: from [1.98.191.99] ([94.167.146.87]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id p0NAND3P001967 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 23 Jan 2011 11:23:16 +0100
References: <4D3966A2.1040102@ericsson.com> <4D398FCC.6090507@viagenie.ca> <4D39B5A2.5090709@unina.it> <4D3BEF42.10906@ericsson.com>
In-Reply-To: <4D3BEF42.10906@ericsson.com>
Mime-Version: 1.0 (iPhone Mail 8A306)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <46174C3C-EDE6-426C-A11C-C2E61B02FF74@unina.it>
X-Mailer: iPhone Mail (8A306)
From: Simon Pietro Romano <spromano@unina.it>
Subject: Re: Experiment: tools for remote participation in IETF80
Date: Sun, 23 Jan 2011 11:22:40 +0100
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, "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: Sun, 23 Jan 2011 10:20:32 -0000

Hi Gonzalo,

I'll put on the web site a section specifically devoted to IETFfers, with a t=
utorial on how to download, install and test the system. We are also availab=
le for on-line demo sessions with interested people. I'll send a mail on the=
 list as soon as this new section is ready. OK?

Simon

Il giorno 23/gen/2011, alle ore 10:05, Gonzalo Camarillo <Gonzalo.Camarillo@=
ericsson.com> ha scritto:

> Hi Simon Pietro,
>=20
> I have received a few (off-list) emails from WG chairs who would like to
> evaluate the system in order to decide whether to use it in their
> sessions. Most pointed out that having this type of information
> available on a web page would make their testing much easier.
>=20
> Thanks,
>=20
> Gonzalo
>=20
> On 21/01/2011 6:34 PM, Simon Pietro Romano wrote:
>> Hi Marc,
>>=20
>> you actually need to register in order to access the download section. I=20=

>> apologize if it is not enough in evidence on the web site. You will find=20=

>> there all versions (Windows, Linux and MAC) of our desktop client, which=20=

>> is integrated in the well known XMPP client called Spark (btw, people=20
>> who are used to join the usual IETF conference rooms will be able to=20
>> log-in both on 'jabber.ietf.org' and on our conference server from the=20=

>> same app). If someone is interested in giving a try to the mobile=20
>> versions of the client app (Android and  Blackberry, since we cannot=20
>> release our I-Phone and Symbian apps as yet), just drop an e-mail to=20
>> info@meetecho.com. We ask people to send an e-mail to such address in=20
>> order to be enabled and test the platform.
>> This said, I once again stress the point that if you are not willing to=20=

>> install any dedicated client, you can still access most of the provided=20=

>> functionality through your browser, plus any standard (VoIP or PSTN)=20
>> phone (for the audio/video streams).
>> We do appreciate feedback from all of you guys; being capable to deal=20
>> with potential issues/requests in advance will be fundamental for us.=20
>> Our main objective at the upcoming IETF will be to seize the unique=20
>> opportunity of gathering as much input as possible from the community in=20=

>> order to improve our platform. So, please don't hesitate even if you=20
>> have to be harsh ;-)!
>>=20
>> Cheers,
>>=20
>> Simon
>>=20
>> Il 21/01/2011 14:53, Marc Blanchet ha scritto:
>>> maybe I'm missing something, but that web site has a download menu=20
>>> with no downloadable software and almost no documentation. So it is=20
>>> pretty difficult to get any sense of the applicability of such=20
>>> software, not talking about trying it out in advance of the meeting to=20=

>>> see how it fits.
>>>=20
>>> Am I missing something too obvious?
>>>=20
>>> Marc.
>>>=20
>>> Le 11-01-21 05:57, Gonzalo Camarillo a =C3=A9crit :
>>>> Chairs,
>>>>=20
>>>> after the last IETF meeting there were some discussions about how to
>>>> allow people to participate in the meetings remotely. We already have
>>>> the jabber rooms and the (outgoing) mp3 feeds but some chairs felt that=

>>>> was not enough. The mp3 feeds seemed to be too slow and presentations b=
y
>>>> remote participants (which require at least incoming audio) were a
>>>> challenge.
>>>>=20
>>>> A few IETFers have developed a web conferencing and collaboration syste=
m
>>>> based on IETF protocols such as SIP, XMPP, BFCP, and RTP. They are
>>>> willing to make it available for WG chairs who want to try it during th=
e
>>>> upcoming IETF in Prague. You can have a look at the system at:
>>>>=20
>>>> http://www.meetecho.com/
>>>>=20
>>>> Simon Pietro (who chairs the SPLICES WG) can provide you with more
>>>> information about the capabilities of the system and its requirements.
>>>> If you are interested in this, please let him know.
>>>>=20
>>>> Thanks,
>>>>=20
>>>> Gonzalo
>>>=20
>>>=20
>>=20
>=20
>=20

From hallam@gmail.com  Fri Jan 21 10:19:39 2011
Return-Path: <hallam@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 C2D8528C133; Fri, 21 Jan 2011 10:19:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.468
X-Spam-Level: 
X-Spam-Status: No, score=-3.468 tagged_above=-999 required=5 tests=[AWL=0.130,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 qix6lhtawYIE; Fri, 21 Jan 2011 10:19:39 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 74F2D28C123; Fri, 21 Jan 2011 10:19:38 -0800 (PST)
Received: by ywk9 with SMTP id 9so699178ywk.31 for <multiple recipients>; Fri, 21 Jan 2011 10:22:24 -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=GdtxymgJqgS3dDy51w6KOCEpFlD10S9Qhp6DO+L6OnM=; b=k6omNLCgQ9ewfQ06wJgbnlkgC4T+rCWelzICUzoTzDNGrwgY+tnxiWEdTZmENSvFMl zOkcbSOB/eZCh/If5OSye2Um/t99b7t5SWZJpwF5AIL5cvKbTQWdujPk5rssycPXIJxk qQdNbN6V4pUavTxvitZjIDRaVovh+KGZvjtHU=
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=vmEAcAM1NPW10RmygB59wisZECuXXe1TUq7oE0pqHJRrSw18EwIb7S8sC5WB8DznId YTV/8IHWXjyh9UXQVs7iRuvAvugCeKToP4RaRRGDeiJ9HiFJLTRXlBlZnZJrA7D6TQtW W5PTlQJtJ14tPZAWUc5FyI8zQJjMn+DtHdoiM=
MIME-Version: 1.0
Received: by 10.100.44.17 with SMTP id r17mr684652anr.222.1295634144678; Fri, 21 Jan 2011 10:22:24 -0800 (PST)
Received: by 10.101.71.15 with HTTP; Fri, 21 Jan 2011 10:22:24 -0800 (PST)
In-Reply-To: <alpine.OSX.2.01.1101210808570.70222@macpro.local>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com> <alpine.OSX.2.01.1101210808570.70222@macpro.local>
Date: Fri, 21 Jan 2011 13:22:24 -0500
Message-ID: <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com>
Subject: Re: IETF 83 Venue
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ole Jacobsen <ole@cisco.com>
Content-Type: multipart/alternative; boundary=0016e644bc76f3e142049a5f544e
X-Mailman-Approved-At: Mon, 24 Jan 2011 08:27:30 -0800
Cc: iaoc@ietf.org, ietf@ietf.org, iab@iab.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, 21 Jan 2011 18:19:39 -0000

--0016e644bc76f3e142049a5f544e
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <ole@cisco.com> wrote:

>
> Does anyone see the irony of us even discussing concerns about, of all
> things, FOOD when it comes to Paris?
>

What else is there to discuss in Paris?


-- 
Website: http://hallambaker.com/

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

On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:ole@cisco.com">ole@cisco.com</a>&gt;</span> wrote:<br><div clas=
s=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Does anyone see the irony of us even discussing concerns about, of all<br>
things, FOOD when it comes to Paris?<br></blockquote><div><br></div><div>Wh=
at else is there to discuss in Paris?</div><div><br></div><div><br></div></=
div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.=
com/</a><br>
<br>

--0016e644bc76f3e142049a5f544e--

From mnot@mnot.net  Tue Jan 25 17:55:54 2011
Return-Path: <mnot@mnot.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 6515D3A6906 for <wgchairs@core3.amsl.com>; Tue, 25 Jan 2011 17:55:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.598
X-Spam-Level: 
X-Spam-Status: No, score=-104.598 tagged_above=-999 required=5 tests=[AWL=-1.999, 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 8Kag+DOwcUbM for <wgchairs@core3.amsl.com>; Tue, 25 Jan 2011 17:55:53 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id A8E363A6905 for <wgchairs@ietf.org>; Tue, 25 Jan 2011 17:55:53 -0800 (PST)
Received: from chancetrain-lm.mnot.net (unknown [118.209.1.128]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 2F599509B3 for <wgchairs@ietf.org>; Tue, 25 Jan 2011 20:58:51 -0500 (EST)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Conference spam
Date: Wed, 26 Jan 2011 12:58:47 +1100
Message-Id: <7B2C0F44-0689-45CB-8283-4687925CB13C@mnot.net>
To: WG Chairs <wgchairs@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
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, 26 Jan 2011 01:55:54 -0000

How do other chairs do with the ubiquitous calls for papers to various =
conferences, often pertaining to topics that have *nothing* to do with =
the WG?

Regards,


--
Mark Nottingham   http://www.mnot.net/




From joelja@bogus.com  Tue Jan 25 18:04:27 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 B43023A68E7 for <wgchairs@core3.amsl.com>; Tue, 25 Jan 2011 18:04:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.025
X-Spam-Level: 
X-Spam-Status: No, score=-102.025 tagged_above=-999 required=5 tests=[AWL=0.574, 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 9jwpQxpzy8Gw for <wgchairs@core3.amsl.com>; Tue, 25 Jan 2011 18:04:26 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 60DCA3A6898 for <wgchairs@ietf.org>; Tue, 25 Jan 2011 18:04:26 -0800 (PST)
Received: from localhost (m470536d0.tmodns.net [208.54.5.71]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p0Q27JFr027344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 26 Jan 2011 02:07:23 GMT (envelope-from joelja@bogus.com)
Date: Tue, 25 Jan 2011 18:07:09 -0800
Subject: Re: Conference spam
Message-ID: <hitnvkgoxyrnvp0pohf15eyq.1296007629722@email.android.com>
From: Joel Jaeggli <joelja@bogus.com>
To: Mark Nottingham <mnot@mnot.net>, WG Chairs <wgchairs@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
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, 26 Jan 2011 02:04:27 -0000

V2UgbW9kZXJhdGUgdGhlIG5vbi1zdWJzY3JpYmVycy4KCk1hcmsgTm90dGluZ2hhbSA8bW5vdEBt
bm90Lm5ldD4gd3JvdGU6Cgo+SG93IGRvIG90aGVyIGNoYWlycyBkbyB3aXRoIHRoZSB1YmlxdWl0
b3VzIGNhbGxzIGZvciBwYXBlcnMgdG8gdmFyaW91cyBjb25mZXJlbmNlcywgb2Z0ZW4gcGVydGFp
bmluZyB0byB0b3BpY3MgdGhhdCBoYXZlICpub3RoaW5nKiB0byBkbyB3aXRoIHRoZSBXRz8KPgo+
UmVnYXJkcywKPgo+Cj4tLQo+TWFyayBOb3R0aW5naGFtICAgaHR0cDovL3d3dy5tbm90Lm5ldC8K
Pgo+Cj4KPgo=


From barryleiba.mailing.lists@gmail.com  Tue Jan 25 18:49:11 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 136E73A687E for <wgchairs@core3.amsl.com>; Tue, 25 Jan 2011 18:49:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.819
X-Spam-Level: 
X-Spam-Status: No, score=-102.819 tagged_above=-999 required=5 tests=[AWL=0.158, 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 yowXzv4oF11A for <wgchairs@core3.amsl.com>; Tue, 25 Jan 2011 18:49:09 -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 504FE3A6847 for <wgchairs@ietf.org>; Tue, 25 Jan 2011 18:49:09 -0800 (PST)
Received: by iyi42 with SMTP id 42so6381800iyi.31 for <wgchairs@ietf.org>; Tue, 25 Jan 2011 18:52:08 -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=PzA5NX3Z/qyienxmuFPnlHoCOBJ6B1kop6oo2hLtg5o=; b=H9sphl3ZvaijOewr/r6GJMVKQbI8IqC4yY02nQbdne1SxDfSMaP5rwXsnTNFiAtMYo mhvHb91mIlgecoFrpz5rDpOBrkp+SAOp6kUMYA1vnjHr3gTMInrDQs95WYauf3cPzb2H AFMvzN4aBQYH2VPjGy3PJh9jKeLdVQaMemGps=
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=mwk0bUku0uOdVDITcrankj2SP0goJEijfwVZDsQTKvrzUG0D2I6Bnc54l94nbTnhkE fzMIcYOQcUK3u+11nk9iciY4DVMPY+83TUvYkYfUPU2pZyO6oE6w07Q+nxoQfEJVpunl K3yzSvIZiFYzgncdUszFIDPVYl7eMlMk4ielA=
MIME-Version: 1.0
Received: by 10.42.222.66 with SMTP id if2mr7622564icb.487.1296010328303; Tue, 25 Jan 2011 18:52:08 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.227.193 with HTTP; Tue, 25 Jan 2011 18:52:08 -0800 (PST)
In-Reply-To: <hitnvkgoxyrnvp0pohf15eyq.1296007629722@email.android.com>
References: <hitnvkgoxyrnvp0pohf15eyq.1296007629722@email.android.com>
Date: Tue, 25 Jan 2011 21:52:08 -0500
X-Google-Sender-Auth: x8uoIcKNC0IPETG4ig0TQfN7Wj0
Message-ID: <AANLkTi=hfhCPxU3mwFX+yiLGHET-MB=j=3eqfNg3vEKz@mail.gmail.com>
Subject: Re: Conference spam
From: Barry Leiba <barryleiba@computer.org>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1
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, 26 Jan 2011 02:49:11 -0000

>> How do other chairs do with the ubiquitous calls for papers to various conferences,
>> often pertaining to topics that have *nothing* to do with the WG?
>
> We moderate the non-subscribers.

It might not help, Mark, that your mailing list is at w3c.org, rather
than at ietf.org.  I'm guessing you might even get more of those sorts
of things over there.

The moderation can be a pain at times, but it's effective.

Barry

From mnot@mnot.net  Tue Jan 25 18:56:00 2011
Return-Path: <mnot@mnot.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 2F3203A68FD for <wgchairs@core3.amsl.com>; Tue, 25 Jan 2011 18:56:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.582
X-Spam-Level: 
X-Spam-Status: No, score=-104.582 tagged_above=-999 required=5 tests=[AWL=-1.983, 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 jirenpqpVQ8s for <wgchairs@core3.amsl.com>; Tue, 25 Jan 2011 18:55:59 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 22F323A6867 for <wgchairs@ietf.org>; Tue, 25 Jan 2011 18:55:58 -0800 (PST)
Received: from chancetrain-lm.mnot.net (unknown [118.209.1.128]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 428DE509B3; Tue, 25 Jan 2011 21:58:56 -0500 (EST)
Subject: Re: Conference spam
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <AANLkTi=hfhCPxU3mwFX+yiLGHET-MB=j=3eqfNg3vEKz@mail.gmail.com>
Date: Wed, 26 Jan 2011 13:58:51 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2880D723-99F9-4B82-BD17-8DE3A3726211@mnot.net>
References: <hitnvkgoxyrnvp0pohf15eyq.1296007629722@email.android.com> <AANLkTi=hfhCPxU3mwFX+yiLGHET-MB=j=3eqfNg3vEKz@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1082)
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, 26 Jan 2011 02:56:00 -0000

Yep. *sigh*.

Thanks,


On 26/01/2011, at 1:52 PM, Barry Leiba wrote:

>>> How do other chairs do with the ubiquitous calls for papers to =
various conferences,
>>> often pertaining to topics that have *nothing* to do with the WG?
>>=20
>> We moderate the non-subscribers.
>=20
> It might not help, Mark, that your mailing list is at w3c.org, rather
> than at ietf.org.  I'm guessing you might even get more of those sorts
> of things over there.
>=20
> The moderation can be a pain at times, but it's effective.
>=20
> Barry

--
Mark Nottingham   http://www.mnot.net/




From Joe.Hildebrand@webex.com  Tue Jan 25 23:09:33 2011
Return-Path: <Joe.Hildebrand@webex.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 D94053A6948 for <wgchairs@core3.amsl.com>; Tue, 25 Jan 2011 23:09:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.353
X-Spam-Level: 
X-Spam-Status: No, score=-104.353 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067, 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 wvYiPDpjeDm9 for <wgchairs@core3.amsl.com>; Tue, 25 Jan 2011 23:09:33 -0800 (PST)
Received: from gw1.webex.com (gw1.webex.com [64.68.122.208]) by core3.amsl.com (Postfix) with SMTP id 03E3A3A6843 for <wgchairs@ietf.org>; Tue, 25 Jan 2011 23:09:32 -0800 (PST)
Received: from SRV-EXSC03.webex.local ([192.168.252.197]) by gw1.webex.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 25 Jan 2011 23:12:32 -0800
Received: from 66.114.169.8 ([66.114.169.8]) by SRV-EXSC03.webex.local ([192.168.252.200]) via Exchange Front-End Server mailus.webex.com ([66.114.175.12]) with Microsoft Exchange Server HTTP-DAV ; Wed, 26 Jan 2011 07:12:32 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Wed, 26 Jan 2011 00:12:30 -0700
Subject: Canonical RFC formatting
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: Glenn Kowack <Glenn@RiverOnce.com>
Message-ID: <C965176E.4854C%joe.hildebrand@webex.com>
Thread-Topic: Canonical RFC formatting
Thread-Index: Acu9KGTwdIe1dtHHgUSyQUly/ZKvfA==
In-Reply-To: <D10C8A96-81B7-4BA6-B672-442A892D135F@RiverOnce.com>
IM-ID: xmpp:jhildebr@cisco.com
Presence-ID: xmpp:jhildebr@cisco.com
Jabber-ID: jhildebr@cisco.com
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 26 Jan 2011 07:12:32.0502 (UTC) FILETIME=[666E0960:01CBBD28]
Cc: "wgchairs@ietf.org 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, 26 Jan 2011 07:09:34 -0000

On 1/21/11 3:03 PM, "Glenn Kowack" <Glenn@RiverOnce.com> wrote:

> (*) Actually, I have formally been the RSE since 19 April, but with the
> understanding that this is a transitional period, consistent with the
> points I raised above.
> http://www.rfc-editor.org/pipermail/rfc-interest/2010-April/001743.html

Yup, that was the message to which I was referring, and which I (slightly)
misunderstood, apparently.

> So, if there are things you'd like to discuss, please feel free
> to bring them to this list and I'll make sure they are carried
> over during the transition.

Well, you asked, and few will be surprised that I want to open *the* can of
worms:

The plain-text RFC format of our forefathers is woefully outdated to the
point where it is hindering our ability to build an Internet.  We at the
**very** least MUST allow authors to use their correct names in their own
specifications, and we MUST be able to write specifications that deal with
internationalization issues that actually use non-ASCII glyphs.

I would further suggest that the 80-column fixed page-size ^L format that
worked for some printers back when we started hinders readability,
particularly since most modern printers don't work that way in their normal
modes.

I personally don't care much about the ASCII-art issue, but that could be a
further refinement to shoot for down the road.

Now that adequate tooling such as HTML exists, we no longer have to accept
these limitations.

Objections:
- "That's the way we've always done it"
Yes, because when we started, that was the only way we could agree to do it.
We can do better now, and we have a responsibility to do so.

- "It's too hard to change"
XML2RFC already creates passable HTML.  We could start with that for *new*
specs.

- "I like to use Word to edit my text"
We can always build new tools if we need to; if the HTML format was
canonical, we could just work tooling directly for that, rather than making
folks edit the XML format.

- "English is the language of the IETF"
We could specify that all normative text was understandable to an English
speaker.

- "We don't want an unreadable mishmosh of fonts, colors, and blink tags"
Again, we could define what it's going to look like, and give the RFC editor
the power to enforce visual continuity.

- "We'll be able to read plain ASCII text 100 years from now"
Does anyone think you won't be able to read well-formed UTF-8 encoded HTML
in 100 years?  Even if you couldn't read the formatting, you could always
write 1 line of Perl2100 to strip out the tags.  But chances are, there will
still be enterprises running IE6 then.

-- 
Joe Hildebrand


From keith.drage@alcatel-lucent.com  Wed Jan 26 04:55:10 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 F04273A69B3 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 04:55:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.619
X-Spam-Level: 
X-Spam-Status: No, score=-105.619 tagged_above=-999 required=5 tests=[AWL=0.630, BAYES_00=-2.599, HELO_EQ_FR=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 8TtaIGtEbnmy for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 04:55:07 -0800 (PST)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id CD40A3A69BE for <wgchairs@ietf.org>; Wed, 26 Jan 2011 04:55:06 -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 p0QCw3OH020866 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 26 Jan 2011 13:58:03 +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; Wed, 26 Jan 2011 13:58:03 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Mark Nottingham <mnot@mnot.net>, Barry Leiba <barryleiba@computer.org>
Date: Wed, 26 Jan 2011 13:58:02 +0100
Subject: RE: Conference spam
Thread-Topic: Conference spam
Thread-Index: Acu9BSIksqpuLCb/Qiyn463/usKpsgARUPaw
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21E70B286@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <hitnvkgoxyrnvp0pohf15eyq.1296007629722@email.android.com> <AANLkTi=hfhCPxU3mwFX+yiLGHET-MB=j=3eqfNg3vEKz@mail.gmail.com> <2880D723-99F9-4B82-BD17-8DE3A3726211@mnot.net>
In-Reply-To: <2880D723-99F9-4B82-BD17-8DE3A3726211@mnot.net>
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: 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, 26 Jan 2011 12:55:10 -0000

Noone has mentioned criteria for acceptance. I expect posters to show the r=
elationship to advancing at least one of the milestones of the working grou=
p.

As regards persistent posters, sometimes they do respond to requests to wg =
email lists from their bulk mailing lists.

Regards

Keith

-----Original Message-----
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behal=
f Of Mark Nottingham
Sent: 26 January 2011 02:59
To: Barry Leiba
Cc: WG Chairs
Subject: Re: Conference spam

Yep. *sigh*.

Thanks,


On 26/01/2011, at 1:52 PM, Barry Leiba wrote:

>>> How do other chairs do with the ubiquitous calls for papers to various =
conferences,
>>> often pertaining to topics that have *nothing* to do with the WG?
>>=20
>> We moderate the non-subscribers.
>=20
> It might not help, Mark, that your mailing list is at w3c.org, rather
> than at ietf.org.  I'm guessing you might even get more of those sorts
> of things over there.
>=20
> The moderation can be a pain at times, but it's effective.
>=20
> Barry

--
Mark Nottingham   http://www.mnot.net/




From pkyzivat@cisco.com  Wed Jan 26 06:42:06 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 378AE3A6405 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 06:42:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.492
X-Spam-Level: 
X-Spam-Status: No, score=-110.492 tagged_above=-999 required=5 tests=[AWL=0.107, 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 Rzz5HligECZd for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 06:42:05 -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 2CB283A657C for <wgchairs@ietf.org>; Wed, 26 Jan 2011 06:42:05 -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: AvsEAP7BP01AZnwN/2dsb2JhbACkd3OhAptIhU8EhReHEoNG
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 26 Jan 2011 14:45:05 +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 p0QEj5Nu029762 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 14:45:05 GMT
Message-ID: <4D403371.9010108@cisco.com>
Date: Wed, 26 Jan 2011 09:45:05 -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: Canonical RFC formatting
References: <C965176E.4854C%joe.hildebrand@webex.com>
In-Reply-To: <C965176E.4854C%joe.hildebrand@webex.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, 26 Jan 2011 14:42:06 -0000

Joe,

I also chafe at the limitations of ascii for drafts/RFCs. Yet I think we 
must be careful about giving up the devil we know for the devil we don't 
know.

I have had some small experience with 3gpp specs.
They use MSWord, and I found it to be a nightmare to manage. The issues 
aren't all related to use of Word - its also due to cooperative editing 
of huge documents.

But the bottom line is that changing the document format impacts all the 
tools and procedures for managing the documents. So we should carefully 
consider those impacts before changing how we do things.

	Thanks,
	Paul

On 1/26/2011 2:12 AM, Joe Hildebrand wrote:
> On 1/21/11 3:03 PM, "Glenn Kowack"<Glenn@RiverOnce.com>  wrote:
>
>> (*) Actually, I have formally been the RSE since 19 April, but with the
>> understanding that this is a transitional period, consistent with the
>> points I raised above.
>> http://www.rfc-editor.org/pipermail/rfc-interest/2010-April/001743.html
>
> Yup, that was the message to which I was referring, and which I (slightly)
> misunderstood, apparently.
>
>> So, if there are things you'd like to discuss, please feel free
>> to bring them to this list and I'll make sure they are carried
>> over during the transition.
>
> Well, you asked, and few will be surprised that I want to open *the* can of
> worms:
>
> The plain-text RFC format of our forefathers is woefully outdated to the
> point where it is hindering our ability to build an Internet.  We at the
> **very** least MUST allow authors to use their correct names in their own
> specifications, and we MUST be able to write specifications that deal with
> internationalization issues that actually use non-ASCII glyphs.
>
> I would further suggest that the 80-column fixed page-size ^L format that
> worked for some printers back when we started hinders readability,
> particularly since most modern printers don't work that way in their normal
> modes.
>
> I personally don't care much about the ASCII-art issue, but that could be a
> further refinement to shoot for down the road.
>
> Now that adequate tooling such as HTML exists, we no longer have to accept
> these limitations.
>
> Objections:
> - "That's the way we've always done it"
> Yes, because when we started, that was the only way we could agree to do it.
> We can do better now, and we have a responsibility to do so.
>
> - "It's too hard to change"
> XML2RFC already creates passable HTML.  We could start with that for *new*
> specs.
>
> - "I like to use Word to edit my text"
> We can always build new tools if we need to; if the HTML format was
> canonical, we could just work tooling directly for that, rather than making
> folks edit the XML format.
>
> - "English is the language of the IETF"
> We could specify that all normative text was understandable to an English
> speaker.
>
> - "We don't want an unreadable mishmosh of fonts, colors, and blink tags"
> Again, we could define what it's going to look like, and give the RFC editor
> the power to enforce visual continuity.
>
> - "We'll be able to read plain ASCII text 100 years from now"
> Does anyone think you won't be able to read well-formed UTF-8 encoded HTML
> in 100 years?  Even if you couldn't read the formatting, you could always
> write 1 line of Perl2100 to strip out the tags.  But chances are, there will
> still be enterprises running IE6 then.
>

From julien.meuric@orange-ftgroup.com  Wed Jan 26 07:01:11 2011
Return-Path: <julien.meuric@orange-ftgroup.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 3C6983A67D6 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 07:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 CN2WSKkPtqQJ for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 07:01:10 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 822A73A67C0 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 07:01:10 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 81BD3FC4002 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 16:04:14 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id 79C73FC4001 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 16:04:14 +0100 (CET)
Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 26 Jan 2011 16:04:09 +0100
Received: from [10.193.71.237] ([10.193.71.237]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 26 Jan 2011 16:04:09 +0100
Message-ID: <4D4037E9.4080207@orange-ftgroup.com>
Date: Wed, 26 Jan 2011 16:04:09 +0100
From: Julien Meuric <julien.meuric@orange-ftgroup.com>
Organization: France Telecom
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; 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: Canonical RFC formatting
References: <C965176E.4854C%joe.hildebrand@webex.com> <4D403371.9010108@cisco.com>
In-Reply-To: <4D403371.9010108@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jan 2011 15:04:09.0773 (UTC) FILETIME=[48EAEDD0:01CBBD6A]
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, 26 Jan 2011 15:01:11 -0000

"Changing our internal document format is not that easy (good thing to 
consider it though), but the global network MUST upgrade its billions 
hosts to v6..." I love the irony, but I might be the only one. ;-)

Julien (shield on)


Le 26/01/2011 15:45, Paul Kyzivat wrote:
>
>  [...] But the bottom line is that changing the document format
>  impacts all the tools and procedures for managing the documents. So
>  we should carefully consider those impacts before changing how we do
>  things. [...]
>
>  On 1/26/2011 2:12 AM, Joe Hildebrand wrote:
> > [...]
> >
> > Objections: - "That's the way we've always done it" [...]
> >
> > - "It's too hard to change" [...]
> >


From spromano@unina.it  Wed Jan 26 07:15:47 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 1CA633A6816 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 07:15:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.603
X-Spam-Level: 
X-Spam-Status: No, score=-100.603 tagged_above=-999 required=5 tests=[AWL=0.116, 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 EUlohNPzBZVY for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 07:15:46 -0800 (PST)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by core3.amsl.com (Postfix) with ESMTP id 73A853A67FB for <wgchairs@ietf.org>; Wed, 26 Jan 2011 07:15:45 -0800 (PST)
Received: from [10.0.1.12] ([143.225.229.205]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id p0QFIf3x031872 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 26 Jan 2011 16:18:42 +0100
Message-ID: <4D403B4C.2000204@unina.it>
Date: Wed, 26 Jan 2011 16:18:36 +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: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: Experiment: tools for remote participation in IETF80
References: <4D3966A2.1040102@ericsson.com> <4D398FCC.6090507@viagenie.ca> <4D39B5A2.5090709@unina.it> <4D3BEF42.10906@ericsson.com>
In-Reply-To: <4D3BEF42.10906@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, "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: Wed, 26 Jan 2011 15:15:47 -0000

Dear Gonzalo and all,

sorry for delaying my response to your request. We worked these days in 
order to make available to all IETFfers a (hopefully) complete 
information kit related to Meetecho and the way it can be used. We just 
published such information, which is available at the following URL: 
http://conf.meetecho.com/. If you go to our site www.meetecho.com, you 
can still reach the mentioned information from the news section, where 
we announced our 'unofficial' experiment. We tried to make the 
information kit as complete as possible and we'll keep on updating it as 
long as we receive your suggestions for improvements and modifications.

If some of you are interested in giving Meetecho a try, please drop an 
e-mail to the following address: info@meetecho.com. We'll set up 
dedicated conference demos upon request. Let me thank in advance all of 
you for your feedbacks and comments.

Cheers,

Simon

Il 23/01/2011 10:05, Gonzalo Camarillo ha scritto:
> Hi Simon Pietro,
>
> I have received a few (off-list) emails from WG chairs who would like to
> evaluate the system in order to decide whether to use it in their
> sessions. Most pointed out that having this type of information
> available on a web page would make their testing much easier.
>
> Thanks,
>
> Gonzalo
>
> On 21/01/2011 6:34 PM, Simon Pietro Romano wrote:
>> Hi Marc,
>>
>> you actually need to register in order to access the download section. I
>> apologize if it is not enough in evidence on the web site. You will find
>> there all versions (Windows, Linux and MAC) of our desktop client, which
>> is integrated in the well known XMPP client called Spark (btw, people
>> who are used to join the usual IETF conference rooms will be able to
>> log-in both on 'jabber.ietf.org' and on our conference server from the
>> same app). If someone is interested in giving a try to the mobile
>> versions of the client app (Android and  Blackberry, since we cannot
>> release our I-Phone and Symbian apps as yet), just drop an e-mail to
>> info@meetecho.com. We ask people to send an e-mail to such address in
>> order to be enabled and test the platform.
>> This said, I once again stress the point that if you are not willing to
>> install any dedicated client, you can still access most of the provided
>> functionality through your browser, plus any standard (VoIP or PSTN)
>> phone (for the audio/video streams).
>> We do appreciate feedback from all of you guys; being capable to deal
>> with potential issues/requests in advance will be fundamental for us.
>> Our main objective at the upcoming IETF will be to seize the unique
>> opportunity of gathering as much input as possible from the community in
>> order to improve our platform. So, please don't hesitate even if you
>> have to be harsh ;-)!
>>
>> Cheers,
>>
>> Simon
>>
>> Il 21/01/2011 14:53, Marc Blanchet ha scritto:
>>> maybe I'm missing something, but that web site has a download menu
>>> with no downloadable software and almost no documentation. So it is
>>> pretty difficult to get any sense of the applicability of such
>>> software, not talking about trying it out in advance of the meeting to
>>> see how it fits.
>>>
>>> Am I missing something too obvious?
>>>
>>> Marc.
>>>
>>> Le 11-01-21 05:57, Gonzalo Camarillo a écrit :
>>>> Chairs,
>>>>
>>>> after the last IETF meeting there were some discussions about how to
>>>> allow people to participate in the meetings remotely. We already have
>>>> the jabber rooms and the (outgoing) mp3 feeds but some chairs felt that
>>>> was not enough. The mp3 feeds seemed to be too slow and presentations by
>>>> remote participants (which require at least incoming audio) were a
>>>> challenge.
>>>>
>>>> A few IETFers have developed a web conferencing and collaboration system
>>>> based on IETF protocols such as SIP, XMPP, BFCP, and RTP. They are
>>>> willing to make it available for WG chairs who want to try it during the
>>>> upcoming IETF in Prague. You can have a look at the system at:
>>>>
>>>> http://www.meetecho.com/
>>>>
>>>> Simon Pietro (who chairs the SPLICES WG) can provide you with more
>>>> information about the capabilities of the system and its requirements.
>>>> If you are interested in this, please let him know.
>>>>
>>>> Thanks,
>>>>
>>>> Gonzalo
>>>
>

-- 
                             _\\|//_
                             ( 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 paul.hoffman@vpnc.org  Wed Jan 26 07:22:23 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 E39383A67D7 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 07:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.187
X-Spam-Level: 
X-Spam-Status: No, score=-100.187 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, 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 3pgUVVHcwm1T for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 07:22:23 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id B66B73A67D9 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 07:22:22 -0800 (PST)
Received: from MacBook-08.local ([64.168.229.50]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p0QFPMZN095888 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Wed, 26 Jan 2011 08:25:23 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D403CE2.9010704@vpnc.org>
Date: Wed, 26 Jan 2011 07:25:22 -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: <C965176E.4854C%joe.hildebrand@webex.com>
In-Reply-To: <C965176E.4854C%joe.hildebrand@webex.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, 26 Jan 2011 15:22:24 -0000

Why is this thread appropriate for wg-chairs? What makes us special in 
the consideration of the RFC format?

From barryleiba.mailing.lists@gmail.com  Wed Jan 26 08:25:46 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 8F55B3A6803 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 08:25:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.854
X-Spam-Level: 
X-Spam-Status: No, score=-102.854 tagged_above=-999 required=5 tests=[AWL=0.123, 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 Xp7qWfDwkPrl for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 08:25:45 -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 8CAE13A688C for <wgchairs@ietf.org>; Wed, 26 Jan 2011 08:25:45 -0800 (PST)
Received: by iyi42 with SMTP id 42so583782iyi.31 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 08:28:46 -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=Phx2VHbbB79c8gFtfG3Lnqq28rQvIsd9BmOku8ANas8=; b=WDw5Ai4l7YHN+6FugZDh9uTbX59hk3DPKM0jNNxzeRBK8+yInNuv5mMRURXHfyiTuZ esSQYxhdt55Fs5MWQQMd457C2tCwyXO4DTGPcJ55moeScLEFvDAC3htKt8MPI6Ndbk2m Sb2FjioMNjz1spbOm4IqUg8ROKzFOSImP8hMI=
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=ORedYuJsUzqLD/5w28VytISNPhPr+TxuINY72DalaY6xv/aFoy+Jm4MaGWi/CHXKfw 6YtoAOHYrIetX8m4QzeCDZ4wjd9zndc3tMi2jWcmzJ/3Gg2b85tIdBTBvGGhXanqhtjG opMbaGGo52Q3XGn0LhsyuhZUNXJkycc69dg7c=
MIME-Version: 1.0
Received: by 10.42.227.199 with SMTP id jb7mr705490icb.286.1296059326404; Wed, 26 Jan 2011 08:28:46 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.227.193 with HTTP; Wed, 26 Jan 2011 08:28:46 -0800 (PST)
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE21E70B286@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <hitnvkgoxyrnvp0pohf15eyq.1296007629722@email.android.com> <AANLkTi=hfhCPxU3mwFX+yiLGHET-MB=j=3eqfNg3vEKz@mail.gmail.com> <2880D723-99F9-4B82-BD17-8DE3A3726211@mnot.net> <EDC0A1AE77C57744B664A310A0B23AE21E70B286@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Wed, 26 Jan 2011 11:28:46 -0500
X-Google-Sender-Auth: PM--PGKCU-dQmrjxpNssAkJZ9_M
Message-ID: <AANLkTim-cwEKum4be99Hy0bKw6Oj+Lj3DpOy41B3Ry_Y@mail.gmail.com>
Subject: Re: Conference spam
From: Barry Leiba <barryleiba@computer.org>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
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, 26 Jan 2011 16:25:46 -0000

> Noone has mentioned criteria for acceptance. I expect posters to show the relationship
> to advancing at least one of the milestones of the working group.

I'm a little more flexible: a clear connection to the work of the
group, even if it doesn't address a specific milestone, is sufficient
for me.  But I do require that they ask a chair before they post.
Just blasting off a post without asking is a sure way to get me to
reject it in the moderation queue, however closely related to the WG
it is.

> As regards persistent posters, sometimes they do respond to requests to wg email
> lists from their bulk mailing lists.

Missing word, apparently:  "requests to REMOVE wg email lists".  Yes,
it's worth asking them.

Barry

From barryleiba.mailing.lists@gmail.com  Wed Jan 26 08:29:48 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 CBFAD3A67A4 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 08:29:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.856
X-Spam-Level: 
X-Spam-Status: No, score=-102.856 tagged_above=-999 required=5 tests=[AWL=0.121, 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 rEWi1WBBSAsm for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 08:29:48 -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 027ED3A63D3 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 08:29:47 -0800 (PST)
Received: by iwn40 with SMTP id 40so1134539iwn.31 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 08:32:48 -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=2obkbLHVRoLcjBDi6VrPjjU8YC/tWTgvrPYrAvPm4q0=; b=gBtesr3dFKvC4Ag8W3OQlgGzZ7VAD0X/8LeL5HTfHj+QwUjhhsDxcLJ4fAkaTmbRNL xVtOYFrfi+N8+pExSWEQxyHkkNaRBBOLOY4L5PFNZoeazoPoNczQCn+tlkNXI/gxGbSB QwDT2m4b/p46ri+h2KBEOSERHYHU7/UfJVEk0=
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=NUOC4KCwBPy4HO2n9lpL7qKlchFWd0qR58V35nwwjRxthXMMQyIGZf514Zr7z0xDnm 1MABlqlQhXsDniH4ZW6dw4Y7W37AVIWvTwvTBi2OCRC0NJW4Vt0/zwcSOeOBQLdbr432 DEacPyR1R6C3bwGzYOiHQ6KrVZ3lkS2wJThs8=
MIME-Version: 1.0
Received: by 10.42.170.200 with SMTP id g8mr753756icz.85.1296059568933; Wed, 26 Jan 2011 08:32:48 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.227.193 with HTTP; Wed, 26 Jan 2011 08:32:48 -0800 (PST)
In-Reply-To: <4D403CE2.9010704@vpnc.org>
References: <C965176E.4854C%joe.hildebrand@webex.com> <4D403CE2.9010704@vpnc.org>
Date: Wed, 26 Jan 2011 11:32:48 -0500
X-Google-Sender-Auth: hQYlrrjN1XouSTD6H1GD427ss9w
Message-ID: <AANLkTi=h2k0XJRZXtV6=D9rW5aFA9f89k9bCC9UwMYxy@mail.gmail.com>
Subject: Re: Canonical RFC formatting
From: Barry Leiba <barryleiba@computer.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
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, 26 Jan 2011 16:29:48 -0000

> Why is this thread appropriate for wg-chairs? What makes us special in the
> consideration of the RFC format?

Maybe Joe wanted to float it here first before opening it up to the
One True Rathole.

And I agree with everything Joe says.

Barry

From alexey.melnikov@isode.com  Wed Jan 26 08:31:51 2011
Return-Path: <alexey.melnikov@isode.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 10F1E3A67EC for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 08:31:51 -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 8fU2ZVSO3wEs for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 08:31:50 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 388D33A67A4 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 08:31:50 -0800 (PST)
Received: from [192.168.1.124] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TUBNKQADL5yg@rufus.isode.com>; Wed, 26 Jan 2011 16:34:50 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4D404D16.6030407@isode.com>
Date: Wed, 26 Jan 2011 16:34:30 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Barry Leiba <barryleiba@computer.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Canonical RFC formatting
References: <C965176E.4854C%joe.hildebrand@webex.com> <4D403CE2.9010704@vpnc.org> <AANLkTi=h2k0XJRZXtV6=D9rW5aFA9f89k9bCC9UwMYxy@mail.gmail.com>
In-Reply-To: <AANLkTi=h2k0XJRZXtV6=D9rW5aFA9f89k9bCC9UwMYxy@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; 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, 26 Jan 2011 16:31:51 -0000

Barry Leiba wrote:

>>Why is this thread appropriate for wg-chairs? What makes us special in the
>>consideration of the RFC format?
>>    
>>
I am agreeing that this is probably not the right list for this discussion.

>Maybe Joe wanted to float it here first before opening it up to the
>One True Rathole.
>
>And I agree with everything Joe says.
>  
>
+1.


From rbarnes@bbn.com  Wed Jan 26 08:35:27 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 1643B3A67F3 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 08:35:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.094, 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 csa5yQf0gwAp for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 08:35:26 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 483133A67EF for <wgchairs@ietf.org>; Wed, 26 Jan 2011 08:35:26 -0800 (PST)
Received: from [128.89.255.99] (port=65367 helo=[192.168.1.16]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Pi8O1-000PMm-Ec; Wed, 26 Jan 2011 11:38:25 -0500
Subject: Re: Canonical RFC formatting
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: <4D404D16.6030407@isode.com>
Date: Wed, 26 Jan 2011 11:38:18 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF270520-6A0F-4196-8538-1E905EEC11C8@bbn.com>
References: <C965176E.4854C%joe.hildebrand@webex.com> <4D403CE2.9010704@vpnc.org> <AANLkTi=h2k0XJRZXtV6=D9rW5aFA9f89k9bCC9UwMYxy@mail.gmail.com> <4D404D16.6030407@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1082)
Cc: wgchairs@ietf.org, Barry Leiba <barryleiba@computer.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, 26 Jan 2011 16:35:27 -0000

+1 on both points!


On Jan 26, 2011, at 11:34 AM, Alexey Melnikov wrote:

> Barry Leiba wrote:
>=20
>>> Why is this thread appropriate for wg-chairs? What makes us special =
in the
>>> consideration of the RFC format?
>>>  =20
> I am agreeing that this is probably not the right list for this =
discussion.
>=20
>> Maybe Joe wanted to float it here first before opening it up to the
>> One True Rathole.
>>=20
>> And I agree with everything Joe says.
>>=20
> +1.
>=20


From dworley@avaya.com  Wed Jan 26 08:43:27 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 3FEE43A68D7 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 08:43:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 tkTssdwUHJ1e for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 08:43:26 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 49E2C3A68E3 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 08:43:26 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJfeP02HCzI1/2dsb2JhbACkd3OjOgKZLIVPBIUXinM
X-IronPort-AV: E=Sophos;i="4.60,380,1291611600"; d="scan'208";a="56171806"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 26 Jan 2011 11:46:26 -0500
X-IronPort-AV: E=Sophos;i="4.60,380,1291611600"; d="scan'208";a="588594956"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 26 Jan 2011 11:45:46 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Wed, 26 Jan 2011 11:45:46 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Joe Hildebrand <joe.hildebrand@webex.com>, Glenn Kowack <Glenn@RiverOnce.com>
Date: Wed, 26 Jan 2011 11:45:22 -0500
Subject: RE: Canonical RFC formatting
Thread-Topic: Canonical RFC formatting
Thread-Index: Acu9KGTwdIe1dtHHgUSyQUly/ZKvfAAUAc7z
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A1767EC@DC-US1MBEX4.global.avaya.com>
References: <D10C8A96-81B7-4BA6-B672-442A892D135F@RiverOnce.com>, <C965176E.4854C%joe.hildebrand@webex.com>
In-Reply-To: <C965176E.4854C%joe.hildebrand@webex.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 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, 26 Jan 2011 16:43:27 -0000

> From: Joe Hildebrand [joe.hildebrand@webex.com]
>=20
> Objections:
> - "That's the way we've always done it"
> Yes, because when we started, that was the only way we could agree to do =
it.
> We can do better now, and we have a responsibility to do so.

The expansion of the character set from ASCII to Unicode/UTF-8 would
be a good idea, at the very least to remove the bias against people
whose names cannot be properly expressed by the ASCII character set.

> - "English is the language of the IETF"
> We could specify that all normative text was understandable to an English
> speaker.

Strictly speaking, an English *reader* -- there are many more people
who read English effectively than can speak or hear it.  Fortunately,
reading is the critical skill for our purposes.

> - "We don't want an unreadable mishmosh of fonts, colors, and blink tags"
> Again, we could define what it's going to look like, and give the RFC edi=
tor
> the power to enforce visual continuity.

> - "It's too hard to change"
> XML2RFC already creates passable HTML.  We could start with that for *new=
*
> specs.

> - "I like to use Word to edit my text"
> We can always build new tools if we need to; if the HTML format was
> canonical, we could just work tooling directly for that, rather than maki=
ng
> folks edit the XML format.

The obvious choice is (X)HTML.  If written cleanly, HTML (1) provides
advanced formatting, (2) allows easy extraction of the text content,
and (3) is still low-bandwidth (thus not disadvantaging those with
poor network connectivity).

The problem with HTML is that much of it is generated by tools that
produce hideously complex HTML, often HTML that does not properly
express the intent of the native format of the text.  (E.g., I've seen
a lot of HTML-encoded e-mail where paragraphs were line-broken in the
HTML, despite that the text was clearly intended to flow, and HTML can
express that naturally.)

To put it simply, "People should be able to use HTML to express RFCs,
but they should not be allowed to use the HTML that Word generates."

This leads to he idea of allowing XML2RFC as an allowed source format,
and also distributing the HTML that XML2RFC generates.

Dale

From dworley@avaya.com  Wed Jan 26 08:51:08 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 7C5AF3A680F for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 08:51:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.059, 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 nq2+4lKDfDj9 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 08:51:07 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 9B3113A67D6 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 08:51:07 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAO/gP03GmAcF/2dsb2JhbACkeHOjOwKZL4VPBIUXinM
X-IronPort-AV: E=Sophos;i="4.60,380,1291611600"; d="scan'208";a="261619100"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 26 Jan 2011 11:54:08 -0500
X-IronPort-AV: E=Sophos;i="4.60,380,1291611600"; d="scan'208";a="574990924"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 26 Jan 2011 11:54:07 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Wed, 26 Jan 2011 11:54:07 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Mark Nottingham <mnot@mnot.net>, WG Chairs <wgchairs@ietf.org>
Date: Wed, 26 Jan 2011 11:52:16 -0500
Subject: RE: Conference spam
Thread-Topic: Conference spam
Thread-Index: Acu8/JfpvcePc9hZTWqQpjjJcTFJAwAfMtG/
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A1767ED@DC-US1MBEX4.global.avaya.com>
References: <7B2C0F44-0689-45CB-8283-4687925CB13C@mnot.net>
In-Reply-To: <7B2C0F44-0689-45CB-8283-4687925CB13C@mnot.net>
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, 26 Jan 2011 16:51:08 -0000

________________________________________
From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] On Behalf Of Ma=
rk Nottingham [mnot@mnot.net]

How do other chairs do with the ubiquitous calls for papers to various conf=
erences, often pertaining to topics that have *nothing* to do with the WG?
________________________________________

I've never seen this sort of trouble myself.  But the WG lists I've been on=
 are moderated to limit posting to subscribers, and as far as I know, confe=
rence announcements have always been under the name of a subscriber.  Since=
 a subscriber cares about his social capital in the WG, that probably is en=
ough to keep things under control.

Dale

From touch@isi.edu  Wed Jan 26 09:00:22 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 4015A3A67DF for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:00:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.495
X-Spam-Level: 
X-Spam-Status: No, score=-102.495 tagged_above=-999 required=5 tests=[AWL=0.104, 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 DikkCRCuiZmy for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:00:16 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com (Postfix) with ESMTP id C45EE3A6800 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 09:00:14 -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 nitro.isi.edu (8.13.8/8.13.8) with ESMTP id p0QH2Q8H029867 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 26 Jan 2011 09:02:36 -0800 (PST)
Message-ID: <4D4053A1.9010508@isi.edu>
Date: Wed, 26 Jan 2011 09:02: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: Joe Hildebrand <joe.hildebrand@webex.com>
Subject: Re: Canonical RFC formatting
References: <C965176E.4854C%joe.hildebrand@webex.com>
In-Reply-To: <C965176E.4854C%joe.hildebrand@webex.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: p0QH2Q8H029867
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, Glenn Kowack <Glenn@RiverOnce.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, 26 Jan 2011 17:00:22 -0000

On 1/25/2011 11:12 PM, Joe Hildebrand wrote:
>...
> Objections:
...
>
> - "I like to use Word to edit my text"
> We can always build new tools if we need to; if the HTML format was
> canonical, we could just work tooling directly for that, rather than making
> folks edit the XML format.

I appreciate that this entire discussion is a bit off-topic for this 
list, but just to clarify the state of Word-based editing, in case 
anyone else wants to use it:

See RFC 5385.

The .dot file and scripts to support that are accessible from the IETF 
author tools page; that tool has been available since 2004:

http://www.ietf.org/mail-archive/web/i-d-announce/current/msg03176.html

Joe

From ajs@shinkuro.com  Wed Jan 26 09:02:29 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 19BE93A6889 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:02:29 -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 jBZUmRoC13h8 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:02:27 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id D8FE33A6800 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 09:02:27 -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 D87081ECB426; Wed, 26 Jan 2011 17:05:27 +0000 (UTC)
Date: Wed, 26 Jan 2011 12:05:26 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: Canonical RFC formatting
Message-ID: <20110126170525.GM5011@shinkuro.com>
References: <C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767EC@DC-US1MBEX4.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A1767EC@DC-US1MBEX4.global.avaya.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: Glenn Kowack <Glenn@RiverOnce.com>, "wgchairs@ietf.org 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, 26 Jan 2011 17:02:29 -0000

On Wed, Jan 26, 2011 at 11:45:22AM -0500, Worley, Dale R (Dale) wrote:
> The obvious choice is (X)HTML. 

[. . .]

I think some here have heard my rants about the conflation of form and
content implicit in most of the RFC formatting discussions, the deep
mistake of understanding "ASCII" and "fixed page layout with
ASCII-encoded text" as meaning the same thing, and the bizarre
arrogance of computer geeks shrugging off the expert advice of
librarians on the topic of what is and is not a reliably durable
electronic archival format.  So I'll not repeat any of that.

But before we start deciding what "the obvious choice" is, could we
please at least do a little analysis of what the problem is?  I would
like to suggest that we leave that analysis to the next RSE incumbent
-- someone who will no doubt be eager to turn into a terrier and
explore this little hole in the ground.  It is not plain that "the
obvious choice" is anything given different and possibly competing
needs of the RFC Series, and over on the rfc-i list we are busily
hammering out the requirements for the job of someone who would
presumably be in a position to advise about those needs.  

If people really want this debate to be opened, then, I encourage them
to go read Glenn's proposals for the RSE, and comment on the rfc-i
list.  Indeed, that list has had an unfortunate preponderance of
certain well-known voices, and it might be nice to have some different
perspectives.

Thanks,

A

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

From pkyzivat@cisco.com  Wed Jan 26 09:08:48 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 98F623A6814 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.488
X-Spam-Level: 
X-Spam-Status: No, score=-110.488 tagged_above=-999 required=5 tests=[AWL=0.111, 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 iId9p58yGews for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:08:47 -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 C48EA3A6812 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 09:08:47 -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: AosFAH7kP01AZnwM/2dsb2JhbACWWI4gc6Eim1mFTwSFF4cSg0Y
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 26 Jan 2011 17:11:48 +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 p0QHBmOi021867 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 17:11:48 GMT
Message-ID: <4D4055D4.2070804@cisco.com>
Date: Wed, 26 Jan 2011 12:11:48 -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: Canonical RFC formatting
References: <D10C8A96-81B7-4BA6-B672-442A892D135F@RiverOnce.com>, <C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767EC@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A1767EC@DC-US1MBEX4.global.avaya.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, 26 Jan 2011 17:08:48 -0000

On 1/26/2011 11:45 AM, Worley, Dale R (Dale) wrote:

> This leads to he idea of allowing XML2RFC as an allowed source format,
> and also distributing the HTML that XML2RFC generates.

We could get a lot of mileage out of that. Just allow xml2rfc source to 
be submitted for drafts as an alternative to text, rather than waiting 
till the RFC stage.

And have the draft announcement messages and queries offer links to any 
of the formats XML2RFC can produce when the xml is available.

	Thanks,
	Paul

From ajs@shinkuro.com  Wed Jan 26 09:30:05 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 BFE8C3A6917 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:30:04 -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 unU6FkEn4hYT for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:30:03 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 06BDB3A684C for <wgchairs@ietf.org>; Wed, 26 Jan 2011 09:30:03 -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 BBAAF1ECB426 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 17:33:03 +0000 (UTC)
Date: Wed, 26 Jan 2011 12:33:02 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: wgchairs@ietf.org
Subject: Re: Canonical RFC formatting
Message-ID: <20110126173301.GN5011@shinkuro.com>
References: <C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767EC@DC-US1MBEX4.global.avaya.com> <4D4055D4.2070804@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D4055D4.2070804@cisco.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, 26 Jan 2011 17:30:05 -0000

On Wed, Jan 26, 2011 at 12:11:48PM -0500, Paul Kyzivat wrote:
> We could get a lot of mileage out of that. Just allow xml2rfc source to  
> be submitted for drafts as an alternative to text, rather than waiting  
> till the RFC stage.

Part of the reason I argued in this thread that we need to do a needs
analysis first before making this sort of change is that I think the
above is a terrible idea.

The only thing xml2rfc has going for it is that it automates certain
tasks that are otherwise harder to automate.  Those tasks are all a
direct result of the preposterous situation that we have line printer
output as our official format for the RFC.  Several of the checks that
are done by the nit checkers at distribution are in fact nits about
_page layout_, a problem that no author should in fact have to be
thinking about while making drafts.

But if we want to throw that line printer format over, then we need to
decide what we really want, and we need not to embrace a tool that is
a marginal author-input improvement over the line printer format, but
that still entrenches that format, as our official submission format.

A

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

From dworley@avaya.com  Wed Jan 26 09:34:01 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 F086A3A6845 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.059, 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 HLetu7Px+VXf for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:34:00 -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 D2C343A6803 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 09:33:59 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAIrqP02HCzI1/2dsb2JhbACkeHOjVQKZNIVPBIUXinM
X-IronPort-AV: E=Sophos;i="4.60,381,1291611600"; d="scan'208";a="229430718"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 26 Jan 2011 12:36:59 -0500
X-IronPort-AV: E=Sophos;i="4.60,381,1291611600"; d="scan'208";a="588619329"
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; 26 Jan 2011 12:36:59 -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; Wed, 26 Jan 2011 12:36:58 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Andrew Sullivan <ajs@shinkuro.com>
Date: Wed, 26 Jan 2011 12:36:57 -0500
Subject: RE: Canonical RFC formatting
Thread-Topic: Canonical RFC formatting
Thread-Index: Acu9ez9JgZCD/k5QRim8EPCPl1hY/gAAvoc1
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A1767EF@DC-US1MBEX4.global.avaya.com>
References: <C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767EC@DC-US1MBEX4.global.avaya.com>, <20110126170525.GM5011@shinkuro.com>
In-Reply-To: <20110126170525.GM5011@shinkuro.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: Glenn Kowack <Glenn@RiverOnce.com>, "wgchairs@ietf.org 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, 26 Jan 2011 17:34:01 -0000

> From: Andrew Sullivan [ajs@shinkuro.com]
>=20
> If people really want this debate to be opened, then, I encourage them
> to go read Glenn's proposals for the RSE, and comment on the rfc-i
> list.  Indeed, that list has had an unfortunate preponderance of
> certain well-known voices, and it might be nice to have some different
> perspectives.

All of what you say is well-taken, but it would make it easier for us
to participate in the manner you suggest if you gave more information
on how to do so.  After some searching, I think that when you say
"rfc-i list" you mean the "rfc-interest mailing list", with the info
page at https://www.rfc-editor.org/mailman/listinfo/rfc-interest.  I
haven't yet tracked down "Glenn's proposals for the RSE"; all I can
find are discussions about the political structure of the RFC Editor
function.  (And does "Glenn" mean "Glenn Kowack"?)  Perhaps you could
give the title of the thread, or even a link to it?

Thanks,

Dale

From touch@isi.edu  Wed Jan 26 09:36:03 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 0B2133A6917 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:36:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, 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 2b6SMnAIyR4t for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:36:02 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com (Postfix) with ESMTP id 3A3B73A686A for <wgchairs@ietf.org>; Wed, 26 Jan 2011 09:36:02 -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 nitro.isi.edu (8.13.8/8.13.8) with ESMTP id p0QHcdEo006369 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 26 Jan 2011 09:38:49 -0800 (PST)
Message-ID: <4D405C1E.80604@isi.edu>
Date: Wed, 26 Jan 2011 09:38:38 -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: Paul Kyzivat <pkyzivat@cisco.com>
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>
In-Reply-To: <4D4055D4.2070804@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: p0QHcdEo006369
X-ISI-4-69-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, 26 Jan 2011 17:36:03 -0000

Hi, Paul,

Again, as an FYI:

On 1/26/2011 9:11 AM, Paul Kyzivat wrote:
>
>
> On 1/26/2011 11:45 AM, Worley, Dale R (Dale) wrote:
>
>> This leads to he idea of allowing XML2RFC as an allowed source format,
>> and also distributing the HTML that XML2RFC generates.
>
> We could get a lot of mileage out of that. Just allow xml2rfc source to
> be submitted for drafts as an alternative to text, rather than waiting
> till the RFC stage.

The tools submission page already allows .xml to be submitted, and 
provides the link to the HTML it generates.

It does require .txt, which basically only forces the author to verify 
that the .xml compiles to .txt, rather than shifting that burden on the 
tool itself. 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.

> And have the draft announcement messages and queries offer links to any
> of the formats XML2RFC can produce when the xml is available.

IMO, it might even be useful to have the draft announcement pages point 
to the tools version, rather than a long list of URLs for different formats.

Joe

From davidbryan@gmail.com  Wed Jan 26 09:39:29 2011
Return-Path: <davidbryan@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 127813A67EF for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:39:29 -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 STq0UXdir072 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:39:28 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 9E6B03A686A for <wgchairs@ietf.org>; Wed, 26 Jan 2011 09:39:26 -0800 (PST)
Received: by fxm9 with SMTP id 9so1296223fxm.31 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 09:42:27 -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 :content-transfer-encoding; bh=KQUejqJ8b7diQLLcgxq0o+/M6efuekLiSsiSmjAzjWc=; b=D6kb+742SX1FXQm0ZW1fhtV/AVJJ2Istyt+I/NjeH/1MX9kJSDHIdw6J3t/miP1rDZ kX/e+OF1ZGNS1Yh/5tMi1NGLnsL1YIdSIij/LcT4va42dOn3PCFZYF+1uKjAuTe7yBnU beO7lRQ5YV+P6T76T2q7Iom6eECZaoKfUH3K8=
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 :content-transfer-encoding; b=QahdeGlErnUvC/B7q1oydaCjpKIALOXGVb85sNYhvEgGy5P44PTeLNZlqHi2/i4udv mycrKA2rvOA2dYteLdB9TXLeB0tJxMJaiHq6scfbmibsQRvozWrOcluYD6e2GlGY3xbk D3cgx2kdH6+eMQA/ucfriup6dqSrLOqIrrGZs=
MIME-Version: 1.0
Received: by 10.223.96.206 with SMTP id i14mr7554899fan.67.1296063478107; Wed, 26 Jan 2011 09:37:58 -0800 (PST)
Sender: davidbryan@gmail.com
Received: by 10.223.126.147 with HTTP; Wed, 26 Jan 2011 09:37:58 -0800 (PST)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A1767ED@DC-US1MBEX4.global.avaya.com>
References: <7B2C0F44-0689-45CB-8283-4687925CB13C@mnot.net> <CD5674C3CD99574EBA7432465FC13C1B220A1767ED@DC-US1MBEX4.global.avaya.com>
Date: Wed, 26 Jan 2011 12:37:58 -0500
X-Google-Sender-Auth: J3QMTJ6U8CioiQnjB60Ui95CuUI
Message-ID: <AANLkTik2haXh6DRgf84rPmFBGGr6+HbWMud3AonDBztM@mail.gmail.com>
Subject: Re: Conference spam
From: "David A. Bryan" <dbryan@ethernot.org>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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, 26 Jan 2011 17:39:29 -0000

I mostly have seen the same thing (the occasional post of a CFP-ish
thing by member seems to be very apropos if it happens), but I've also
seen folks subscribe simply to post CFPs...

David

On Wed, Jan 26, 2011 at 11:52 AM, Worley, Dale R (Dale)
<dworley@avaya.com> wrote:
> ________________________________________
> From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] On Behalf Of =
Mark Nottingham [mnot@mnot.net]
>
> How do other chairs do with the ubiquitous calls for papers to various co=
nferences, often pertaining to topics that have *nothing* to do with the WG=
?
> ________________________________________
>
> I've never seen this sort of trouble myself. =A0But the WG lists I've bee=
n on are moderated to limit posting to subscribers, and as far as I know, c=
onference announcements have always been under the name of a subscriber. =
=A0Since a subscriber cares about his social capital in the WG, that probab=
ly is enough to keep things under control.
>
> Dale
>

From ajs@shinkuro.com  Wed Jan 26 09:46:37 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 8BB743A6834 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:46:37 -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 yPDFyfAsSOgv for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 09:46:36 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 112903A681C for <wgchairs@ietf.org>; Wed, 26 Jan 2011 09:46:36 -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 4B8661ECB426; Wed, 26 Jan 2011 17:49:36 +0000 (UTC)
Date: Wed, 26 Jan 2011 12:49:34 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: Canonical RFC formatting
Message-ID: <20110126174934.GO5011@shinkuro.com>
References: <C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767EF@DC-US1MBEX4.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A1767EF@DC-US1MBEX4.global.avaya.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: Glenn Kowack <Glenn@RiverOnce.com>, "wgchairs@ietf.org 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, 26 Jan 2011 17:46:37 -0000

On Wed, Jan 26, 2011 at 12:36:57PM -0500, Worley, Dale R (Dale) wrote:
> All of what you say is well-taken, but it would make it easier for us
> to participate in the manner you suggest if you gave more information
> on how to do so.

Sorry it wasn't clear (though I'm vaguely alarmed that anyone on the
wg-chairs list doesn't already know about all this); you're quite
right for taking me to task.  

Everything you need to know to get started is available at 

http://www.rfc-editor.org/rse/RSE.html

A

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

From cabo@tzi.org  Wed Jan 26 10:17:49 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 424BC3A6850 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 10:17:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.332
X-Spam-Level: 
X-Spam-Status: No, score=-106.332 tagged_above=-999 required=5 tests=[AWL=-0.083, 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 JGjk9IoQ1QbX for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 10:17:48 -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 04BA43A6849 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 10:17:47 -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 p0QIKcaw018197; Wed, 26 Jan 2011 19:20:38 +0100 (CET)
Received: from [192.168.10.52] (christoph.dagstuhl.de [192.76.146.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 8F1EA1D4; Wed, 26 Jan 2011 19:20:38 +0100 (CET)
Subject: Re: Canonical RFC formatting
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4D405C1E.80604@isi.edu>
Date: Wed, 26 Jan 2011 19:21:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <58A43A73-5FD3-4A75-A223-29B24913C34E@tzi.org>
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>
To: Joe Touch <touch@isi.edu>
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, 26 Jan 2011 18:17:49 -0000

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.

Gruesse, Carsten


From touch@isi.edu  Wed Jan 26 10:27:28 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 A58B028C0D7 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 10:27:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.513
X-Spam-Level: 
X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, 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 DnSVU94AUclX for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 10:27:27 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id BB13528C0D0 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 10:27:27 -0800 (PST)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0QITtv4001104 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 26 Jan 2011 10:29:55 -0800 (PST)
Message-ID: <4D406822.5020402@isi.edu>
Date: Wed, 26 Jan 2011 10:29:54 -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: Carsten Bormann <cabo@tzi.org>
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>
In-Reply-To: <58A43A73-5FD3-4A75-A223-29B24913C34E@tzi.org>
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, 26 Jan 2011 18:27:28 -0000

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.

Joe

From dworley@avaya.com  Wed Jan 26 10:43:08 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 6E1E73A6842 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 10:43:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, 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 EW1sLlqvm1Lv for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 10:43:07 -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 31E643A686E for <wgchairs@ietf.org>; Wed, 26 Jan 2011 10:43:07 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPP6P02HCzI1/2dsb2JhbACkeHOjeAKZN4VPBIUXinM
X-IronPort-AV: E=Sophos;i="4.60,381,1291611600"; d="scan'208";a="229443820"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 26 Jan 2011 13:46:07 -0500
X-IronPort-AV: E=Sophos;i="4.60,381,1291611600"; d="scan'208";a="588645873"
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; 26 Jan 2011 13:46:06 -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; Wed, 26 Jan 2011 13:46:06 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Andrew Sullivan <ajs@shinkuro.com>
Date: Wed, 26 Jan 2011 13:46:05 -0500
Subject: RE: Canonical RFC formatting
Thread-Topic: Canonical RFC formatting
Thread-Index: Acu9gW4hd7xXLoSSS6iPICHN9YfrSwABuwKt
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A1767F2@DC-US1MBEX4.global.avaya.com>
References: <C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767EF@DC-US1MBEX4.global.avaya.com>, <20110126174934.GO5011@shinkuro.com>
In-Reply-To: <20110126174934.GO5011@shinkuro.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 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, 26 Jan 2011 18:43:08 -0000

________________________________________
From: Andrew Sullivan [ajs@shinkuro.com]

Sorry it wasn't clear (though I'm vaguely alarmed that anyone on the
wg-chairs list doesn't already know about all this); you're quite
right for taking me to task.

Everything you need to know to get started is available at

http://www.rfc-editor.org/rse/RSE.html
________________________________________

You can safely assume that if you address a community that is not specifica=
lly involved with a subject, that most of its members will know little abou=
t the internal discussion mechanics of the subject.  Especially in this sit=
uation, where you specifically want to get previously uninvolved people inv=
olved, you can pretty much assume that the people you are targeting don't k=
now about it.

Looking at RSE.html, or rather draft-kowack-rfc-editor-model-v2-motivations=
-00, which is linked from it, all I see is that the RFC Editor is expected =
to lead a discussion on RFC formats.  The vast remainder appears to be what=
 I call "the politics of the RFC Editor function", which I have absolutely =
no interest in dealing with.

So is there really a discussion of RFC formats on rfc-interest or not?  If =
so, how do I find it?

Dale

From ajs@shinkuro.com  Wed Jan 26 10:47:09 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 3C0DB3A6826 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 10:47:09 -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 WNUi8EZRdPn6 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 10:47:08 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 777B93A6849 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 10:47:08 -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 328E01ECB425; Wed, 26 Jan 2011 18:50:09 +0000 (UTC)
Date: Wed, 26 Jan 2011 13:50:07 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: Canonical RFC formatting
Message-ID: <20110126185006.GQ5011@shinkuro.com>
References: <C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767F2@DC-US1MBEX4.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A1767F2@DC-US1MBEX4.global.avaya.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: "wgchairs@ietf.org 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, 26 Jan 2011 18:47:09 -0000

On Wed, Jan 26, 2011 at 01:46:05PM -0500, Worley, Dale R (Dale) wrote:
> So is there really a discussion of RFC formats on rfc-interest or not?  If so, how do I find it?

No, there isn't, and I don't think I suggested there was.

What there is instead is a discussion of the scope of the RSE job, and
perhaps (probably, I'd guess from the drift of the discussion) an
oversight committee.  This is a sort of meta-requirements discussion.
But one of the important issues is what sort of experience one might
want in an RFC Series Editor if one were going to have that
discussion.

A

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

From touch@isi.edu  Wed Jan 26 11:34:21 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 554243A6842 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 11:34:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, 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 vjx0fZTXD0Zy for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 11:34:20 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 796873A6822 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 11:34:20 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0QJab1J015216 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 26 Jan 2011 11:36:37 -0800 (PST)
Message-ID: <4D4077C5.8010203@isi.edu>
Date: Wed, 26 Jan 2011 11:36:37 -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: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: Canonical RFC formatting
References: <C965176E.4854C%joe.hildebrand@webex.com>	<CD5674C3CD99574EBA7432465FC13C1B220A1767EF@DC-US1MBEX4.global.avaya.com>, <20110126174934.GO5011@shinkuro.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767F2@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A1767F2@DC-US1MBEX4.global.avaya.com>
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 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, 26 Jan 2011 19:34:21 -0000

On 1/26/2011 10:46 AM, Worley, Dale R (Dale) wrote:
...
> So is there really a discussion of RFC formats on rfc-interest or not?  If so, how do I find it?

There have been many; the discussion (sadly) appears to be cyclical. The 
following are pointers to such discussions - they're not the head of 
each thread, but should allow you to find it

As you can see, we had some gaps (2002-2004, 2007, 2009). I was hoping 
we could make it to 2012 at least until this whack-a-mole popped up again...

Joe

------

mail list	date		string

IETF(main list)	Feb 22, 2001	Why we shouldn' use ASCII text
IETF		Dec 12, 2001	the ascii discussion all over again...
IETF		Apr  8, 2005	I-D/RFC source formats
tools-team	Apr 14, 2005	Accepting other formats for "source"
IETF		Jun 14, 2006	(draft-ash-alt-formats)
IETF		Jan 12, 2006	Alternative formats for IDs
rfc-i		Sep 25, 2008	Action:draft-rfc-image-files-01.txt
rfc-i		Sep 25, 2008	ACTION:draft-hoffman-utf8-rfcs-02.txt
rfc-i		Jan 30, 2010	"canonical" URI for RFCs, BCPs
IETF		Mar 13, 2010	Towards consensus on document format

IETF list:
http://www.ietf.org/mail-archive/web/ietf/current/maillist.html

tools-team:
http://tools.ietf.org/discuss-archive

rfc-i:
http://www.rfc-editor.org/pipermail/rfc-interest/




From john-ietf@jck.com  Wed Jan 26 12:15:09 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 0F6F928C0D7 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 12:15:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.058
X-Spam-Level: 
X-Spam-Status: No, score=-103.058 tagged_above=-999 required=5 tests=[AWL=-0.459, 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 jsHosHga8YA1 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 12:15:08 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 0949328B56A for <wgchairs@ietf.org>; Wed, 26 Jan 2011 12:15:05 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PiBoY-000N0V-Bb; Wed, 26 Jan 2011 15:18:02 -0500
Date: Wed, 26 Jan 2011 15:18:01 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Andrew Sullivan <ajs@shinkuro.com>
Subject: RE: Canonical RFC formatting
Message-ID: <711BEF2E14B6D3713A6846B6@PST.JCK.COM>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A1767F2@DC-US1MBEX4.global.avaya.com>
References: <C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767EF@DC-US1MBEX4.global.avaya.com> ,	<20110126174934.GO5011@shinkuro.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767F2@DC-US1MBEX4.global.avaya.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 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, 26 Jan 2011 20:15:09 -0000

--On Wednesday, January 26, 2011 13:46 -0500 "Worley, Dale R
(Dale)" <dworley@avaya.com> wrote:

> So is there really a discussion of RFC formats on rfc-interest
> or not?  If so, how do I find it?

Dale, while I agree with Andrew's later note, the specific
answer to your question is that such discussions have occurred
over and over again, at intervals of a few years, on the
rfc-interest list since it was created, on the IETF list, and
elsewhere.  

The wgchairs list is almost the worst possible place to try to
initiate the discussion because almost none of the relevant
people are on it.

The bottom line about those prior discussions, at least to date,
is that the decisions that have been made have been strongly
conditioned on two things: the importance of having the RFC
Series (or at least its nominal official format) be archival and
archivally accessible and the importance of being able to easily
extract material from RFCs (especially what we now consider
standards-track ones) for use in other or updated documents.
Those two key principles, especially the first, have created
huge conservatism about changes.  That conservatism becomes
especially pronounced when formats are proposed that require
that a particular version of a document be bound to a particular
processor (or version of a processor) in order to get the same
output.  

That concern derives not just from theory but from a problem
that occurred fairly early in the life of the series -- many
early RFCs actually were created in in machine-readable form,
but using processors that one hears about today only in computer
history contexts (e.g., I assume that few contemporary
participants in the IETF have even heard of NLS, much less used
it or seen it in action).   We've discovered that the most
efficient way to salvage those documents is to scan paper
copies, run OCR programs over them, and then manually correct
the results.   Not good for an archival series.

So, over the years, proposals for having the authoritative
versions be in runoff and nroff, WordStar,  WordPerfect, HTML,
various generations of MSWord, Postscript, and PDF and a series
of other page-image arrangements have been rejected on the
grounds that either precise control of the RFC as the reader saw
it required binding to a particular version of a processor,
required a more or less complex profile (and tools to enforce
it) to maintain compatibility and archival permanence, or failed
on the extract-and-paste requirement.

If you (or others) want to start the debate again, you will need
to have it with the new RSE and whatever review groups are
associated with that role.  And that is where the rfc-interest
list comes in, both for defining the role and, in the future,
having the discussion.   Just as personal opinion, I'd recommend
that you (and others) think carefully about the historical
archival and extract-and-paste requirements before suggesting
alternate primary/official forms.

    john



From richard@shockey.us  Wed Jan 26 13:26:07 2011
Return-Path: <richard@shockey.us>
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 52DFA3A69D9 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 13:26:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.014
X-Spam-Level: 
X-Spam-Status: No, score=-102.014 tagged_above=-999 required=5 tests=[AWL=0.251, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 e9upc0DsWX4z for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 13:26:05 -0800 (PST)
Received: from cpoproxy3-pub.bluehost.com (cpoproxy3-pub.bluehost.com [67.222.54.6]) by core3.amsl.com (Postfix) with SMTP id 8AF413A69DF for <wgchairs@ietf.org>; Wed, 26 Jan 2011 13:26:05 -0800 (PST)
Received: (qmail 9487 invoked by uid 0); 26 Jan 2011 21:29:06 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by cpoproxy3.bluehost.com with SMTP; 26 Jan 2011 21:29:06 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:thread-index:Content-language:X-Identified-User; b=QZbe/vdYS6R6AguX3YUGWJz5T9Cs4UG4paYpgO+UXoDnYz/SFuck2uysoNIjVX7OJ0IJNi0xDmNwZ1gZClY1APGz9XQ4xH4457/jBsiuy0bHghKO8+ER0dErxyUSCy5C;
Received: from pool-173-79-200-247.washdc.fios.verizon.net ([173.79.200.247] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1PiCvK-0001mV-A9; Wed, 26 Jan 2011 14:29:06 -0700
From: "Richard Shockey" <richard@shockey.us>
To: "'Barry Leiba'" <barryleiba@computer.org>, "'Paul Hoffman'" <paul.hoffman@vpnc.org>
References: <C965176E.4854C%joe.hildebrand@webex.com>	<4D403CE2.9010704@vpnc.org> <AANLkTi=h2k0XJRZXtV6=D9rW5aFA9f89k9bCC9UwMYxy@mail.gmail.com>
In-Reply-To: <AANLkTi=h2k0XJRZXtV6=D9rW5aFA9f89k9bCC9UwMYxy@mail.gmail.com>
Subject: RE: Canonical RFC formatting
Date: Wed, 26 Jan 2011 16:29:03 -0500
Message-ID: <015a01cbbda0$0e976150$2bc623f0$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: Acu9dqydYg18wMUaTYaXBRGlKbDq8QAKSvbg
Content-language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.79.200.247 authed with richard@shockey.us}
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, 26 Jan 2011 21:26:07 -0000

I thought the rule was we don't talk about the RFC format until spring? Isnt
that in the Zen document or something?

I want epub but what do I know. 

-----Original Message-----
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behalf
Of Barry Leiba
Sent: Wednesday, January 26, 2011 11:33 AM
To: Paul Hoffman
Cc: wgchairs@ietf.org
Subject: Re: Canonical RFC formatting

> Why is this thread appropriate for wg-chairs? What makes us special in the
> consideration of the RFC format?

Maybe Joe wanted to float it here first before opening it up to the
One True Rathole.

And I agree with everything Joe says.

Barry


From dworley@avaya.com  Wed Jan 26 14:15:28 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 1A70E3A68AA for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 14:15:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, 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 ovpX1c9dZjHA for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 14:15:27 -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 12E683A68A0 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 14:15:26 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACssQE2HCzI1/2dsb2JhbACkenOjRQKZMYVPBIUXinM
X-IronPort-AV: E=Sophos;i="4.60,382,1291611600"; d="scan'208";a="229478981"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 26 Jan 2011 17:18:27 -0500
X-IronPort-AV: E=Sophos;i="4.60,382,1291611600"; d="scan'208";a="588719438"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 26 Jan 2011 17:18:26 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Wed, 26 Jan 2011 17:18:26 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: John C Klensin <john-ietf@jck.com>, Andrew Sullivan <ajs@shinkuro.com>
Date: Wed, 26 Jan 2011 17:18:25 -0500
Subject: RE: Canonical RFC formatting
Thread-Topic: Canonical RFC formatting
Thread-Index: Acu9lik/jYplCFQSRAmWaBkyH8FkKgAD2RaG
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A1767F7@DC-US1MBEX4.global.avaya.com>
References: <C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767EF@DC-US1MBEX4.global.avaya.com> , <20110126174934.GO5011@shinkuro.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767F2@DC-US1MBEX4.global.avaya.com>, <711BEF2E14B6D3713A6846B6@PST.JCK.COM>
In-Reply-To: <711BEF2E14B6D3713A6846B6@PST.JCK.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 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, 26 Jan 2011 22:15:28 -0000

> From: John C Klensin [john-ietf@jck.com]

> If you (or others) want to start the debate again, you will need
> to have it with the new RSE and whatever review groups are
> associated with that role.

Yes, that is the important point that wasn't stated clearly.  In the
context, it would have been more useful to say something like:

    This discussion recurs periodically, but for it to be useful, it
    needs to involve a librarian that is familiar with archival needs.
    That will have to wait until we select the new RFC Editor.

> I assume that few contemporary participants in the IETF have even
> heard of NLS, much less used it or seen it in action.

But I'm glad to see that we're still using Nroff, which appears to be
a descendant of the CTSS "runoff", which I first learned of in an
illustration in the September 1966 "Scientific American"!

Dale

From johnl@iecc.com  Wed Jan 26 21:36:55 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 D50CF3A6A86 for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 21:36:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.691
X-Spam-Level: 
X-Spam-Status: No, score=-110.691 tagged_above=-999 required=5 tests=[AWL=0.508, 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 yB22pyZH3pXP for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 21:36:54 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 9FAA03A691D for <wgchairs@ietf.org>; Wed, 26 Jan 2011 21:36:54 -0800 (PST)
Received: (qmail 12982 invoked from network); 27 Jan 2011 05:39:53 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 27 Jan 2011 05:39:53 -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=aa54.4d410529.k1101; i=johnl@user.iecc.com; bh=oJ27R3mQj+1JafLYPdCnw/PdUnWRaImnsXHdW6Cvzjs=; b=PQsxInOJHqk2RlZ0VI0rujwcOz2TnTxwSaJByP3UpSzhrXDKuWycpxMwjXtHl8nl2nu/u/Vq8rp7Qzw7v5lVKfxTYZL0FyJPCPJQ62lXk7MUyCVeLbpyy48PqPEB05iEmFLn5JUy8Z88Q6ZhEbhUUZhf08g/vtEySzNTrx5aJzg=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 27 Jan 2011 05:39:53 -0000
Message-ID: <20110127053953.43603.qmail@joyce.lan>
From: John Levine <johnl@iecc.com>
To: wgchairs@ietf.org
Subject: Re: Canonical RFC formatting
In-Reply-To: <20110126185006.GQ5011@shinkuro.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, 27 Jan 2011 05:36:55 -0000

>What there is instead is a discussion of the scope of the RSE job, and
>perhaps (probably, I'd guess from the drift of the discussion) an
>oversight committee.  This is a sort of meta-requirements discussion.
>But one of the important issues is what sort of experience one might
>want in an RFC Series Editor if one were going to have that
>discussion.

Entirely agree.  Selecting an archival document format that will
address the shortcomings of lineprinter ASCII while remaining usable
for decades is a hard problem, and I have to say that the recent
discussion, like previous IETF discussions on this topic, mostly
remind me that we may know a lot about network software, but we don't
know much about documents and archives.  (As an example, all of the
PDF RFCs to date need to be rebuilt to be of archival quality, because
they're all missing definitions of some of the fonts they use.)

This project is clearly something the RFC Editor needs to lead.

R's,
John


From john-ietf@jck.com  Wed Jan 26 23:02:25 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 EF8623A6AFE for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 23:02:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.042
X-Spam-Level: 
X-Spam-Status: No, score=-103.042 tagged_above=-999 required=5 tests=[AWL=-0.443, 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 tUs1hTyF7BDW for <wgchairs@core3.amsl.com>; Wed, 26 Jan 2011 23:02:23 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 45C6E3A6AF1 for <wgchairs@ietf.org>; Wed, 26 Jan 2011 23:02:23 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PiLuz-000DJg-LO; Thu, 27 Jan 2011 02:05:21 -0500
Date: Thu, 27 Jan 2011 02:05:20 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Andrew Sullivan <ajs@shinkuro.com>
Subject: RE: Canonical RFC formatting
Message-ID: <A8BD9409D8EE1F2191BFC77E@PST.JCK.COM>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A1767F7@DC-US1MBEX4.global.avaya.com>
References: <C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767EF@DC-US1MBEX4.global.avaya.com> ,	<20110126174934.GO5011@shinkuro.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767F2@DC-US1MBEX4.global.avaya.com> ,<711BEF2E14B6D3713A6846B6@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B220A1767F7@DC-US1MBEX4.global.avaya.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 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: Thu, 27 Jan 2011 07:02:25 -0000

--On Wednesday, January 26, 2011 17:18 -0500 "Worley, Dale R
(Dale)" <dworley@avaya.com> wrote:

>> From: John C Klensin [john-ietf@jck.com]
> 
>> If you (or others) want to start the debate again, you will
>> need to have it with the new RSE and whatever review groups
>> are associated with that role.
> 
> Yes, that is the important point that wasn't stated clearly.
> In the context, it would have been more useful to say
> something like:
> 
>     This discussion recurs periodically, but for it to be
> useful, it     needs to involve a librarian that is familiar
> with archival needs.     That will have to wait until we
> select the new RFC Editor.

That statement is true too.   We are describing different
perspectives on the proverbial elephant here... others who have
been even more involved than I have might describe things yet
differently although I hope my approximation is good enough.
And, while I think some having some approximation to "librarian
that is familiar with archival needs" in the system is
important, others might remind you that, while there are people
in the current Production Center who identify themselves
(justifiably) as professional technical editors, most or all of
what the RFC Editor staff has known that would fit into your
"librarian" category was learned on the job, over many years,
and by people who didn't primarily identify themselves with
those skills.

>> I assume that few contemporary participants in the IETF have
>> even heard of NLS, much less used it or seen it in action.
> 
> But I'm glad to see that we're still using Nroff, which
> appears to be a descendant of the CTSS "runoff", which I first
> learned of in an illustration in the September 1966
> "Scientific American"!

:-) 

Having used typset and runoff, on CTSS, before that and then
Multics runoff, which was completely forward-compatible, you
have just succeeded in making me feel really old :-(.   And,
yes, nroff and troff are descendants of runoff, sharing the
general syntax and basically providing a forward-compatible set
of commands.   With a few exceptions, and some issues about
conversion to ASCII, I think most of what was written in/for
runoff on CTSS in the mid-60s would process in a reasonable way
with nroff today... but the results might look a little
different.

    john



From john-ietf@jck.com  Thu Jan 27 01:16:29 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 64A2228C10D for <wgchairs@core3.amsl.com>; Thu, 27 Jan 2011 01:16:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.001
X-Spam-Level: 
X-Spam-Status: No, score=-103.001 tagged_above=-999 required=5 tests=[AWL=-0.402, 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 ExheRaBrrxm3 for <wgchairs@core3.amsl.com>; Thu, 27 Jan 2011 01:16:28 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 78B3228C127 for <wgchairs@ietf.org>; Thu, 27 Jan 2011 01:16:28 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PiO0b-000Gzj-QL; Thu, 27 Jan 2011 04:19:17 -0500
Date: Thu, 27 Jan 2011 04:19:17 -0500
From: John C Klensin <john-ietf@jck.com>
To: Richard Shockey <richard@shockey.us>, 'Barry Leiba' <barryleiba@computer.org>, 'Paul Hoffman' <paul.hoffman@vpnc.org>
Subject: RE: Canonical RFC formatting
Message-ID: <D968DB0CFF5E8C1D25F38DF5@PST.JCK.COM>
In-Reply-To: <015a01cbbda0$0e976150$2bc623f0$@us>
References: <C965176E.4854C%joe.hildebrand@webex.com> <4D403CE2.9010704@vpnc.org> <AANLkTi=h2k0XJRZXtV6=D9rW5aFA9f89k9bCC9UwMYxy@mail.gmail.com> <015a01cbbda0$0e976150$2bc623f0$@us>
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, 27 Jan 2011 09:16:29 -0000

--On Wednesday, January 26, 2011 16:29 -0500 Richard Shockey
<richard@shockey.us> wrote:

> I thought the rule was we don't talk about the RFC format
> until spring? Isnt that in the Zen document or something?
> 
> I want epub but what do I know. 

Richard (and others),

(1) If this discussion is to be useful, it has to occur on a
list to which the RFC Editor staff have access.  This one isn't
one of those, even if the issues that contributed to "spring"
didn't exist.

(2) FWIW, I think personally that the discussion would make lots
more progress if folks distinguished between authoritative
archival forms(s) and forms they would like to have the RFC
Editor make available as a matter of routine.  One could then
have a fairly focused discussion about how close to the
authoritative format the other formats needed to be, whether any
warnings were needed about the differences, resources required,
etc.  

Resources permitting, I think having epub (and maybe a few other
alternate reading-convenience forms) would be great.  I don't
know whether the community would want to invest resources that
way or what (extra) resources it would take, but that is a
matter for a separate discussion on another list.  I am pretty
confident that, as a primary archival form, epub would not pass
even a simple laugh test, but I don't think you suggested that.

     john


From warren@kumari.net  Thu Jan 27 19:11:04 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 C13593A6B7A for <wgchairs@core3.amsl.com>; Thu, 27 Jan 2011 19:11:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.436
X-Spam-Level: 
X-Spam-Status: No, score=-101.436 tagged_above=-999 required=5 tests=[AWL=-0.999, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.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 6V7tbMzKJlZH for <wgchairs@core3.amsl.com>; Thu, 27 Jan 2011 19:11:03 -0800 (PST)
Received: from vimes.kumari.net (unknown [198.186.192.250]) by core3.amsl.com (Postfix) with ESMTP id 405783A6B73 for <wgchairs@ietf.org>; Thu, 27 Jan 2011 19:11:03 -0800 (PST)
Received: from [172.19.119.184] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 9583D1B40CCB; Thu, 27 Jan 2011 13:56:49 -0500 (EST)
Message-Id: <07B77063-C8ED-4597-8A33-FFE4B78CBDD7@kumari.net>
From: Warren Kumari <warren@kumari.net>
To: Andrew Sullivan <ajs@shinkuro.com>
In-Reply-To: <20110126173301.GN5011@shinkuro.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: Canonical RFC formatting
Date: Thu, 27 Jan 2011 13:56:47 -0500
References: <C965176E.4854C%joe.hildebrand@webex.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767EC@DC-US1MBEX4.global.avaya.com> <4D4055D4.2070804@cisco.com> <20110126173301.GN5011@shinkuro.com>
X-Mailer: Apple Mail (2.936)
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, 28 Jan 2011 03:11:04 -0000

On Jan 26, 2011, at 12:33 PM, Andrew Sullivan wrote:

> On Wed, Jan 26, 2011 at 12:11:48PM -0500, Paul Kyzivat wrote:
>> We could get a lot of mileage out of that. Just allow xml2rfc  
>> source to
>> be submitted for drafts as an alternative to text, rather than  
>> waiting
>> till the RFC stage.
>
> Part of the reason I argued in this thread that we need to do a needs
> analysis first before making this sort of change is that I think the
> above is a terrible idea.
>
> The only thing xml2rfc has going for it is that it automates certain
> tasks that are otherwise harder to automate.  Those tasks are all a
> direct result of the preposterous situation that we have line printer
> output as our official format for the RFC.  Several of the checks that
> are done by the nit checkers at distribution are in fact nits about
> _page layout_, a problem that no author should in fact have to be
> thinking about while making drafts.
>
> But if we want to throw that line printer format over,

And, while we are figuring this out, I have a little python script  
that makes dealing with the line printer format easier...

Personally I like reading drafts and RFCs on dead trees (yes, I know,  
I know, but it works for me...).
Printing the current format on a laser printer leads to all sorts of  
ugliness (page length, weird page breaks, simplex / duplex, etc), so I  
have written a small script to make more pleasant. It grabs a draft or  
RFC (or reads it from disk), converts it to a PDF (using the  
ReportLabs stuff) and then ships it off to lpr to actually print it --  
it takes various flags to control operation...

This was written for my own use, and so the code is neither  
documented, nor polished, but if folk find it useful I can try make it  
better...

http://www.kumari.net/code/print_rfc_or_draft.py

W



> then we need to
> decide what we really want, and we need not to embrace a tool that is
> a marginal author-input improvement over the line printer format, but
> that still entrenches that format, as our official submission format.
>
> A
>
> -- 
> Andrew Sullivan
> ajs@shinkuro.com
> Shinkuro, Inc.


From Joe.Hildebrand@webex.com  Thu Jan 27 22:22:04 2011
Return-Path: <Joe.Hildebrand@webex.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 844F43A6A8C for <wgchairs@core3.amsl.com>; Thu, 27 Jan 2011 22:22:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.364
X-Spam-Level: 
X-Spam-Status: No, score=-104.364 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067, 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 mLOm5OtEy7ZJ for <wgchairs@core3.amsl.com>; Thu, 27 Jan 2011 22:22:03 -0800 (PST)
Received: from gw1.webex.com (gw1.webex.com [64.68.122.208]) by core3.amsl.com (Postfix) with SMTP id B74073A6A88 for <wgchairs@ietf.org>; Thu, 27 Jan 2011 22:22:03 -0800 (PST)
Received: from SRV-EXSC03.webex.local ([192.168.252.197]) by gw1.webex.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 27 Jan 2011 22:25:07 -0800
Received: from 66.114.169.7 ([66.114.169.7]) by SRV-EXSC03.webex.local ([192.168.252.200]) via Exchange Front-End Server mailus.webex.com ([66.114.175.11]) with Microsoft Exchange Server HTTP-DAV ; Fri, 28 Jan 2011 06:25:07 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Fri, 28 Jan 2011 01:25:07 -0500
Subject: Re: Canonical RFC formatting
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: Barry Leiba <barryleiba@computer.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <C967CB73.48851%joe.hildebrand@webex.com>
Thread-Topic: Canonical RFC formatting
Thread-Index: Acu+tBs0gtkWBi2/pkGXWLF/lcQdng==
In-Reply-To: <AANLkTi=h2k0XJRZXtV6=D9rW5aFA9f89k9bCC9UwMYxy@mail.gmail.com>
IM-ID: xmpp:jhildebr@cisco.com
Presence-ID: xmpp:jhildebr@cisco.com
Jabber-ID: jhildebr@cisco.com
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 28 Jan 2011 06:25:08.0132 (UTC) FILETIME=[1BE11E40:01CBBEB4]
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, 28 Jan 2011 06:22:04 -0000

On 1/26/11 9:32 AM, "Barry Leiba" <barryleiba@computer.org> wrote:

> Maybe Joe wanted to float it here first before opening it up to the
> One True Rathole.

Exactly.  I wanted to scare out any other likely objections to add to the
list before igniting the flames. :)

-- 
Joe Hildebrand


From Joe.Hildebrand@webex.com  Thu Jan 27 22:24:00 2011
Return-Path: <Joe.Hildebrand@webex.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 0C04A3A6A88 for <wgchairs@core3.amsl.com>; Thu, 27 Jan 2011 22:24:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.373
X-Spam-Level: 
X-Spam-Status: No, score=-104.373 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067, 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 ovRT5zVS29fn for <wgchairs@core3.amsl.com>; Thu, 27 Jan 2011 22:23:58 -0800 (PST)
Received: from gw2.webex.com (gw2.webex.com [64.68.122.209]) by core3.amsl.com (Postfix) with SMTP id 0FCDB3A6BB8 for <wgchairs@ietf.org>; Thu, 27 Jan 2011 22:23:58 -0800 (PST)
Received: from SRV-EXSC03.webex.local ([192.168.252.197]) by gw2.webex.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 27 Jan 2011 22:27:03 -0800
Received: from 66.114.169.8 ([66.114.169.8]) by SRV-EXSC03.webex.local ([192.168.252.200]) via Exchange Front-End Server mailus.webex.com ([66.114.175.11]) with Microsoft Exchange Server HTTP-DAV ; Fri, 28 Jan 2011 06:27:02 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Fri, 28 Jan 2011 01:27:02 -0500
Subject: Re: Canonical RFC formatting
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Glenn Kowack <Glenn@RiverOnce.com>
Message-ID: <C967CBE6.48853%joe.hildebrand@webex.com>
Thread-Topic: Canonical RFC formatting
Thread-Index: Acu9KGTwdIe1dtHHgUSyQUly/ZKvfAAUAc7zAE785XE=
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A1767EC@DC-US1MBEX4.global.avaya.com>
IM-ID: xmpp:jhildebr@cisco.com
Presence-ID: xmpp:jhildebr@cisco.com
Jabber-ID: jhildebr@cisco.com
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 28 Jan 2011 06:27:03.0471 (UTC) FILETIME=[60A073F0:01CBBEB4]
Cc: "wgchairs@ietf.org 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, 28 Jan 2011 06:24:00 -0000

On 1/26/11 9:45 AM, "Worley, Dale R (Dale)" <dworley@avaya.com> wrote:

> Strictly speaking, an English *reader* -- there are many more people
> who read English effectively than can speak or hear it.  Fortunately,
> reading is the critical skill for our purposes.

Typo.  Apparently you're a better reader than I am a speaker. :)

> To put it simply, "People should be able to use HTML to express RFCs,
> but they should not be allowed to use the HTML that Word generates."

+1

> This leads to he idea of allowing XML2RFC as an allowed source format,
> and also distributing the HTML that XML2RFC generates.

We might even semanticize the output of XML2RFC more; I haven't looked at it
recently to see how well it does.

-- 
Joe Hildebrand


From Joe.Hildebrand@webex.com  Thu Jan 27 22:36:22 2011
Return-Path: <Joe.Hildebrand@webex.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 E9CFA3A6BBD for <wgchairs@core3.amsl.com>; Thu, 27 Jan 2011 22:36:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.381
X-Spam-Level: 
X-Spam-Status: No, score=-104.381 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067, 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 ycWicTJ9aWQk for <wgchairs@core3.amsl.com>; Thu, 27 Jan 2011 22:36:20 -0800 (PST)
Received: from gw2.webex.com (gw2.webex.com [64.68.122.209]) by core3.amsl.com (Postfix) with SMTP id C73563A6BB8 for <wgchairs@ietf.org>; Thu, 27 Jan 2011 22:36:20 -0800 (PST)
Received: from SRV-EXSC03.webex.local ([192.168.252.197]) by gw2.webex.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 27 Jan 2011 22:39:26 -0800
Received: from 66.114.169.7 ([66.114.169.7]) by SRV-EXSC03.webex.local ([192.168.252.200]) via Exchange Front-End Server mailus.webex.com ([66.114.175.11]) with Microsoft Exchange Server HTTP-DAV ; Fri, 28 Jan 2011 06:39:25 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Fri, 28 Jan 2011 01:39:24 -0500
Subject: Re: Canonical RFC formatting
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: Andrew Sullivan <ajs@shinkuro.com>, "Worley, Dale R (Dale)" <dworley@avaya.com>
Message-ID: <C967CECC.48858%joe.hildebrand@webex.com>
Thread-Topic: Canonical RFC formatting
Thread-Index: Acu+thoETbxh2uyVP0+1rEdcAqxF4Q==
In-Reply-To: <20110126170525.GM5011@shinkuro.com>
IM-ID: xmpp:jhildebr@cisco.com
Presence-ID: xmpp:jhildebr@cisco.com
Jabber-ID: jhildebr@cisco.com
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 28 Jan 2011 06:39:26.0149 (UTC) FILETIME=[1B4C1F50:01CBBEB6]
Cc: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>, Glenn Kowack <Glenn@RiverOnce.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, 28 Jan 2011 06:36:22 -0000

On 1/26/11 10:05 AM, "Andrew Sullivan" <ajs@shinkuro.com> wrote:

> I think some here have heard my rants about the conflation of form and
> content implicit in most of the RFC formatting discussions, the deep
> mistake of understanding "ASCII" and "fixed page layout with
> ASCII-encoded text" as meaning the same thing,

I understand the difference, but I raised them as two separate points since
it's possible that if we tackle one, we'll be within spitting difference of
a solution to the other.

> and the bizarre
> arrogance of computer geeks shrugging off the expert advice of
> librarians on the topic of what is and is not a reliably durable
> electronic archival format.  So I'll not repeat any of that.

I acknowledge both my ignorance and arrogance.  Any chance you could point
me at some links off-list so I can work on the first?

> But before we start deciding what "the obvious choice" is, could we
> please at least do a little analysis of what the problem is?

+1

> I would
> like to suggest that we leave that analysis to the next RSE incumbent
> -- someone who will no doubt be eager to turn into a terrier and
> explore this little hole in the ground.

What if how someone digs into this problem is one of the primary criteria
that someone would use to choose the next RSE incumbent?

-- 
Joe Hildebrand


From Joe.Hildebrand@webex.com  Thu Jan 27 22:40:00 2011
Return-Path: <Joe.Hildebrand@webex.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 5E39028C0D7 for <wgchairs@core3.amsl.com>; Thu, 27 Jan 2011 22:40:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.389
X-Spam-Level: 
X-Spam-Status: No, score=-104.389 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067, 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 JGwELpaURp9a for <wgchairs@core3.amsl.com>; Thu, 27 Jan 2011 22:39:55 -0800 (PST)
Received: from gw2.webex.com (gw2.webex.com [64.68.122.209]) by core3.amsl.com (Postfix) with SMTP id 305F53A6A8C for <wgchairs@ietf.org>; Thu, 27 Jan 2011 22:39:55 -0800 (PST)
Received: from SRV-EXSC03.webex.local ([192.168.252.197]) by gw2.webex.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 27 Jan 2011 22:43:00 -0800
Received: from 66.114.169.7 ([66.114.169.7]) by SRV-EXSC03.webex.local ([192.168.252.200]) via Exchange Front-End Server mailus.webex.com ([66.114.175.11]) with Microsoft Exchange Server HTTP-DAV ; Fri, 28 Jan 2011 06:43:00 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Fri, 28 Jan 2011 01:42:59 -0500
Subject: Re: Canonical RFC formatting
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: Richard Shockey <richard@shockey.us>, 'Barry Leiba' <barryleiba@computer.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <C967CFA3.4885B%joe.hildebrand@webex.com>
Thread-Topic: Canonical RFC formatting
Thread-Index: Acu9dqydYg18wMUaTYaXBRGlKbDq8QAKSvbgAEWwbdM=
In-Reply-To: <015a01cbbda0$0e976150$2bc623f0$@us>
IM-ID: xmpp:jhildebr@cisco.com
Presence-ID: xmpp:jhildebr@cisco.com
Jabber-ID: jhildebr@cisco.com
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 28 Jan 2011 06:43:00.0661 (UTC) FILETIME=[9B280E50:01CBBEB6]
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, 28 Jan 2011 06:40:00 -0000

On 1/26/11 2:29 PM, "Richard Shockey" <richard@shockey.us> wrote:

> I thought the rule was we don't talk about the RFC format until spring? Isnt
> that in the Zen document or something?

That was why my original question was so elliptical.  I was hoping not to
light the flamewar until it was time.

"Spring" is ill-defined, but if it was meant to be "after Prague", then I'll
just continue to be disappointed in us for another several months.

-- 
Joe Hildebrand


From xmlscott@gmail.com  Fri Jan 28 04:28:37 2011
Return-Path: <xmlscott@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 9D1333A67A6 for <wgchairs@core3.amsl.com>; Fri, 28 Jan 2011 04:28:37 -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 ChBB9OwGSHXd for <wgchairs@core3.amsl.com>; Fri, 28 Jan 2011 04:28:36 -0800 (PST)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 9C7123A672F for <wgchairs@ietf.org>; Fri, 28 Jan 2011 04:28:36 -0800 (PST)
Received: by qyj19 with SMTP id 19so3403673qyj.10 for <wgchairs@ietf.org>; Fri, 28 Jan 2011 04:31:42 -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 :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=uigoLVS+HQ2bJdcpmnobBnoiTVKbqNmqWfu7/lYviH0=; b=W8BuPuvsRuj+BHx4CimVBcHWURpVnSwDC53SNdNbPZAVe18Vn1m31DJY87JKPK5i9+ huf/yB106s2S7eeudaEp8b8VOeMpFk9jlgQn/QbKEg9MU5Oc/AF8X/i8R2Nr+QvMMp12 sWy1oJVC2o05vDwSAif7bbCwVrZiLJXx7+/4A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=cNAl2iDFJJcc0RztGiDWbXyIKYLEP3Xoj9OJyiobqyhaslyf+nnYu7zY1rj42Gzo1l 0wjEhfnSMUxbhQomcZ7wxm2Ywk7yPSfjVlpFG5F8HCpyMUUV5pItLAnSFbC1LZ/avkLN L1w84G3uXft4GQ0MN4EzLm49p5gRzUv6UPkz8=
Received: by 10.224.89.81 with SMTP id d17mr2833200qam.332.1296217902557; Fri, 28 Jan 2011 04:31:42 -0800 (PST)
Received: from ybr.home.skrb.org (c-98-229-134-198.hsd1.ma.comcast.net [98.229.134.198]) by mx.google.com with ESMTPS id nb15sm12590231qcb.38.2011.01.28.04.31.40 (version=SSLv3 cipher=RC4-MD5); Fri, 28 Jan 2011 04:31:40 -0800 (PST)
Message-ID: <4D42B72B.4030903@gmail.com>
Date: Fri, 28 Jan 2011 07:31:39 -0500
From: Scott Lawrence <xmlscott@gmail.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: wgchairs@ietf.org
Subject: Re: Canonical RFC formatting
References: <C965176E.4854C%joe.hildebrand@webex.com> <4D403CE2.9010704@vpnc.org>
In-Reply-To: <4D403CE2.9010704@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: Fri, 28 Jan 2011 12:28:37 -0000

On 2011-01-26 10:25, Paul Hoffman wrote:
> Why is this thread appropriate for wg-chairs? What makes us special in 
> the consideration of the RFC format?

Please, people... take this discussion elsewhere.  IETFers of all people 
should be clued in to the appropriate choice of lists for a discussion.


From Jeff.Hodges@KingsMountain.com  Fri Jan 28 10:32:07 2011
Return-Path: <Jeff.Hodges@KingsMountain.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 D64483A67D1 for <wgchairs@core3.amsl.com>; Fri, 28 Jan 2011 10:32:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.144
X-Spam-Level: 
X-Spam-Status: No, score=-102.144 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 wrH3fdZNZhu6 for <wgchairs@core3.amsl.com>; Fri, 28 Jan 2011 10:32:07 -0800 (PST)
Received: from cpoproxy2-pub.bluehost.com (cpoproxy2-pub.bluehost.com [67.222.39.38]) by core3.amsl.com (Postfix) with SMTP id E61733A67CF for <wgchairs@ietf.org>; Fri, 28 Jan 2011 10:32:06 -0800 (PST)
Received: (qmail 4222 invoked by uid 0); 28 Jan 2011 18:35:13 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy2.bluehost.com with SMTP; 28 Jan 2011 18:35:13 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=ry4Q41yx4lJOXKEg1t9q+gvUxJQ1XJJ2y/qq1jXawuiU7UTyVSCBXKwPW6jeXg/cdghA5fUszLq7w/ToZdrGsYqAXiLomfmfMDhutfVrdytZa01J85ZnYnQ/kCb1LLBU;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.136.134]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1PitA9-0005Np-5g for wgchairs@ietf.org; Fri, 28 Jan 2011 11:35:13 -0700
Message-ID: <4D430C62.2040009@KingsMountain.com>
Date: Fri, 28 Jan 2011 10:35:14 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: IETF Working Group Chairs <wgchairs@ietf.org>
Subject: Re: Canonical RFC formatting
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 216.113.168.128 authed with jeff.hodges+kingsmountain.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, 28 Jan 2011 18:32:08 -0000

 > On 2011-01-26 10:25, Paul Hoffman wrote:
 >> Why is this thread appropriate for wg-chairs? What makes us special in
 >> the consideration of the RFC format?
 >
 > Please, people... take this discussion elsewhere.  IETFers of all people
 > should be clued in to the appropriate choice of lists for a discussion.

so where to?  <rfc-interest@rfc-editor.org> prior to going to "the one true 
rathole" (which i assume is ietf@ietf.org) ?

=JeffH



From touch@isi.edu  Fri Jan 28 10:46: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 73B083A67D1 for <wgchairs@core3.amsl.com>; Fri, 28 Jan 2011 10:46:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.513
X-Spam-Level: 
X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, 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 q7jvQe1EKdXT for <wgchairs@core3.amsl.com>; Fri, 28 Jan 2011 10:46:25 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 99EFD3A672E for <wgchairs@ietf.org>; Fri, 28 Jan 2011 10:46:25 -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 p0SIn4on024207 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 28 Jan 2011 10:49:04 -0800 (PST)
Message-ID: <4D430FA0.8040205@isi.edu>
Date: Fri, 28 Jan 2011 10:49:04 -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: =JeffH <Jeff.Hodges@KingsMountain.com>
Subject: Re: Canonical RFC formatting
References: <4D430C62.2040009@KingsMountain.com>
In-Reply-To: <4D430C62.2040009@KingsMountain.com>
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: IETF 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, 28 Jan 2011 18:46:26 -0000

On 1/28/2011 10:35 AM, =JeffH wrote:
>  > On 2011-01-26 10:25, Paul Hoffman wrote:
>  >> Why is this thread appropriate for wg-chairs? What makes us special in
>  >> the consideration of the RFC format?
>  >
>  > Please, people... take this discussion elsewhere. IETFers of all people
>  > should be clued in to the appropriate choice of lists for a discussion.
>
> so where to? <rfc-interest@rfc-editor.org> prior to going to "the one
> true rathole" (which i assume is ietf@ietf.org) ?

Yes, rfc-interest.

That's where most of the most recent discussions on this have been, as 
per my earlier mail.

Joe

From enrico.marocco@telecomitalia.it  Mon Jan 31 03:27:48 2011
Return-Path: <enrico.marocco@telecomitalia.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 E240E3A6911 for <wgchairs@core3.amsl.com>; Mon, 31 Jan 2011 03:27:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.596
X-Spam-Level: 
X-Spam-Status: No, score=-100.596 tagged_above=-999 required=5 tests=[AWL=0.123, 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 6ZxVnRDjr1uD for <wgchairs@core3.amsl.com>; Mon, 31 Jan 2011 03:27:48 -0800 (PST)
Received: from GRFEDG702BA020.telecomitalia.it (grfedg702ba020.telecomitalia.it [156.54.233.201]) by core3.amsl.com (Postfix) with ESMTP id 9D7143A6903 for <wgchairs@ietf.org>; Mon, 31 Jan 2011 03:27:12 -0800 (PST)
Received: from GRFHUB701BA020.griffon.local (10.188.101.111) by GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 31 Jan 2011 12:29:59 +0100
Received: from nbnt2006156109.telecomitalia.local (10.229.8.29) by smtp.telecomitalia.it (10.188.101.114) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 31 Jan 2011 12:29:57 +0100
Message-ID: <4D469D35.9020802@telecomitalia.it>
Date: Mon, 31 Jan 2011 12:29:57 +0100
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
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: Experiment: tools for remote participation in IETF80
References: <4D3966A2.1040102@ericsson.com>
In-Reply-To: <4D3966A2.1040102@ericsson.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms000608000502050108020500"
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, 31 Jan 2011 11:27:49 -0000

--------------ms000608000502050108020500
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

=46rom what I understand from the website, the tool's multiparty video
mixing and recording capabilities would be quite well suited for a
plugfest / demo show the ALTO WG will hold presumably during a lunch
break. Are such features going to be available in the experiment?

Enrico

On 1/21/11 11:57 AM, Gonzalo Camarillo wrote:
> Chairs,
>=20
> after the last IETF meeting there were some discussions about how to
> allow people to participate in the meetings remotely. We already have
> the jabber rooms and the (outgoing) mp3 feeds but some chairs felt that=

> was not enough. The mp3 feeds seemed to be too slow and presentations b=
y
> remote participants (which require at least incoming audio) were a
> challenge.
>=20
> A few IETFers have developed a web conferencing and collaboration syste=
m
> based on IETF protocols such as SIP, XMPP, BFCP, and RTP. They are
> willing to make it available for WG chairs who want to try it during th=
e
> upcoming IETF in Prague. You can have a look at the system at:
>=20
> http://www.meetecho.com/
>=20
> Simon Pietro (who chairs the SPLICES WG) can provide you with more
> information about the capabilities of the system and its requirements.
> If you are interested in this, please let him know.
>=20
> Thanks,
>=20
> Gonzalo



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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITpDCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGsjCCBZqgAwIBAgIDAZXQMA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTAwOTAyMjE0NjQ5
WhcNMTEwOTA0MDczNDM2WjCBnTEgMB4GA1UEDRMXMjUxNDUwLTVBOWo3QUhXTXgzNkVHa2Qx
HjAcBgNVBAoTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEpMCcGA1UEAxMgU3RhcnRDb20gRnJl
ZSBDZXJ0aWZpY2F0ZSBNZW1iZXIxLjAsBgkqhkiG9w0BCQEWH2Vucmljby5tYXJvY2NvQHRl
bGVjb21pdGFsaWEuaXQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCVq5Ial9/2
azyFbgXY2+yMbEwHjhOWlXcwa7sdnRZ6BUXjusppAmshM1SPz+IZYfLdqancntuhkG/YKR4T
Mg0SzWz3bDtCQjga0FSBQ5v2Up8kT/Q0F4/hkYrsTaKfL+WA2cjQtn8+K0fD3t/1tcuTuIHw
fesN6w1VDn4HhFj3WGSXok9Zxk7609/Z4ZBqr3trmQ5Dl6pwb8pO1kE/ggH7qCx537ybIByS
dxzcPNzbryGJiCfy4iXaws0xsl4xEQXDJFixLjgJm+AOTXb37AAgwKq+v9t3qIH6AHAbPBO6
I/qpoQ/zYMs1s9CoKkNDa9DsJlgyZdPH/vyFvCi/dDJ7AgMBAAGjggMIMIIDBDAJBgNVHRME
AjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0O
BBYEFCTMmq/In1ufC0+wdpHdBvezAYWcMB8GA1UdIwQYMBaAFFNy7ZKc4NrLAVx8fpY1TvLU
uFGCMCoGA1UdEQQjMCGBH2Vucmljby5tYXJvY2NvQHRlbGVjb21pdGFsaWEuaXQwggFCBgNV
HSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAuBggrBgEFBQcCARYiaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFy
dHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYBBQUHAgIwgaowFBYNU3RhcnRDb20g
THRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNlZSBzZWN0aW9uICpMZWdhbCBMaW1p
dGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5IFBvbGlj
eSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjBjBgNV
HR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9jcnR1MS1jcmwuY3JsMCug
KaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1MS1jcmwuY3JsMIGOBggrBgEFBQcB
AQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5zdGFydHNzbC5jb20vc3ViL2NsYXNz
MS9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2NlcnRz
L3N1Yi5jbGFzczEuY2xpZW50LmNhLmNydDAjBgNVHRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0
c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADWaaCjv4EfYGz4rrds8wLUpSPTi1tnO3hIm
/Hg0SHqDRWRv3AG/OjUKYj+UKKAzhhEoYYrYCxhQfO3uEAC4Mez+DWDsBymKHsRkpf/0efoh
mDe60HN81V6jB7hSB+FHaJ5QCBhJ/yasltL7HMl92dpRHYlnKXoXAiIoZUY54eYh09Gyk8su
xgaiAwWtn4NnTqnQTjYOOly+WOZ/M6AlmkTErzjliIyAJOIceWzByJs6iIvLXzqpdoZ1+BzE
TvoyaVidF13Xc8opUGSqYTyaVKwumrA5eUOZrLzdunkT8JuWgAx81syHYjSeD4ae+EoMFRJ8
gVm6vGPNETTSbFjGM38wggayMIIFmqADAgECAgMBldAwDQYJKoZIhvcNAQEFBQAwgYwxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGln
aXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFBy
aW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDA5MDIyMTQ2NDlaFw0xMTA5MDQw
NzM0MzZaMIGdMSAwHgYDVQQNExcyNTE0NTAtNUE5ajdBSFdNeDM2RUdrZDEeMBwGA1UEChMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMSkwJwYDVQQDEyBTdGFydENvbSBGcmVlIENlcnRpZmlj
YXRlIE1lbWJlcjEuMCwGCSqGSIb3DQEJARYfZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxp
YS5pdDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJWrkhqX3/ZrPIVuBdjb7Ixs
TAeOE5aVdzBrux2dFnoFReO6ymkCayEzVI/P4hlh8t2pqdye26GQb9gpHhMyDRLNbPdsO0JC
OBrQVIFDm/ZSnyRP9DQXj+GRiuxNop8v5YDZyNC2fz4rR8Pe3/W1y5O4gfB96w3rDVUOfgeE
WPdYZJeiT1nGTvrT39nhkGqve2uZDkOXqnBvyk7WQT+CAfuoLHnfvJsgHJJ3HNw83NuvIYmI
J/LiJdrCzTGyXjERBcMkWLEuOAmb4A5NdvfsACDAqr6/23eogfoAcBs8E7oj+qmhD/NgyzWz
0KgqQ0Nr0OwmWDJl08f+/IW8KL90MnsCAwEAAaOCAwgwggMEMAkGA1UdEwQCMAAwCwYDVR0P
BAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNVHQ4EFgQUJMyar8if
W58LT7B2kd0G97MBhZwwHwYDVR0jBBgwFoAUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwKgYDVR0R
BCMwIYEfZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxpYS5pdDCCAUIGA1UdIASCATkwggE1
MIIBMQYLKwYBBAGBtTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9wb2xpY3kucGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9p
bnRlcm1lZGlhdGUucGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEa
gZFMaW1pdGVkIExpYWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBv
ZiB0aGUgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJs
ZSBhdCBodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6Ap
oCeGJWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwK6ApoCeGJWh0dHA6
Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYI
KwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9j
YTBCBggrBgEFBQcwAoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNz
MS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzAN
BgkqhkiG9w0BAQUFAAOCAQEANZpoKO/gR9gbPiut2zzAtSlI9OLW2c7eEib8eDRIeoNFZG/c
Ab86NQpiP5QooDOGEShhitgLGFB87e4QALgx7P4NYOwHKYoexGSl//R5+iGYN7rQc3zVXqMH
uFIH4UdonlAIGEn/JqyW0vscyX3Z2lEdiWcpehcCIihlRjnh5iHT0bKTyy7GBqIDBa2fg2dO
qdBONg46XL5Y5n8zoCWaRMSvOOWIjIAk4hx5bMHImzqIi8tfOql2hnX4HMRO+jJpWJ0XXddz
yilQZKphPJpUrC6asDl5Q5msvN26eRPwm5aADHzWzIdiNJ4Php74SgwVEnyBWbq8Y80RNNJs
WMYzfzGCA9AwggPMAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20g
THRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EC
AwGV0DAJBgUrDgMCGgUAoIICEDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0xMTAxMzExMTI5NTdaMCMGCSqGSIb3DQEJBDEWBBS4Dz4m08nKEMAEcwQTUnz5
WjI1zzBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG
9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgaUGCSsG
AQQBgjcQBDGBlzCBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMBldAw
gacGCyqGSIb3DQEJEAILMYGXoIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQg
Q0ECAwGV0DANBgkqhkiG9w0BAQEFAASCAQA/VglpoMzvmQgFN2Wo1amEv9AJOtmn+h4SYAdu
+pSxsXyHwktmAI5m1BpsWLebuO/AYK0AuU8tdPY65/MLiNOEaQkeA8oBB9sXcu47qhhBJAwa
SY63gwIhXbDU56dZCHJLGNB+Sx4dT4h1vHJ+S3zY/rI65F6IUbSk5qYrGUXtK42RRUzySckB
Ct8aOOvEB/0esAAmZv/uaT+FXLjCCLIxLnxgOIxLpsvLOsKtd+Isisdb2e0iRFMQIfjMVEZb
TTyONgETqH4BjhMg0zqVeK8qhiOyG72B4fpJN7EYSpe9voAeYyXc9WWujRuXtfE0INZaXIKz
u1hHdZDYcWYfRCHSAAAAAAAA
--------------ms000608000502050108020500--

From spromano@unina.it  Mon Jan 31 05:59:35 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 7D7FE3A6B32 for <wgchairs@core3.amsl.com>; Mon, 31 Jan 2011 05:59:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.695
X-Spam-Level: 
X-Spam-Status: No, score=-99.695 tagged_above=-999 required=5 tests=[AWL=-0.835, BAYES_20=-0.74, 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 yhuqrFKdLyKh for <wgchairs@core3.amsl.com>; Mon, 31 Jan 2011 05:59:34 -0800 (PST)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by core3.amsl.com (Postfix) with ESMTP id F14103A6973 for <wgchairs@ietf.org>; Mon, 31 Jan 2011 05:59:33 -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 p0VE2ivF014648 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 31 Jan 2011 15:02:45 +0100
Message-ID: <4D46C0F7.6090001@unina.it>
Date: Mon, 31 Jan 2011 15:02:31 +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: Enrico Marocco <enrico.marocco@telecomitalia.it>
Subject: Re: Experiment: tools for remote participation in IETF80
References: <4D3966A2.1040102@ericsson.com> <4D469D35.9020802@telecomitalia.it>
In-Reply-To: <4D469D35.9020802@telecomitalia.it>
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: Mon, 31 Jan 2011 13:59:35 -0000

Hi Enrico,

all of the features of our platform will be available in the experiment. 
We'll be glad to help you guys set up remote participation in the ALTO 
demo show, if needed.

Cheers,

Simon

Il 31/01/2011 12:29, Enrico Marocco ha scritto:
>  From what I understand from the website, the tool's multiparty video
> mixing and recording capabilities would be quite well suited for a
> plugfest / demo show the ALTO WG will hold presumably during a lunch
> break. Are such features going to be available in the experiment?
>
> Enrico
>
> On 1/21/11 11:57 AM, Gonzalo Camarillo wrote:
>> Chairs,
>>
>> after the last IETF meeting there were some discussions about how to
>> allow people to participate in the meetings remotely. We already have
>> the jabber rooms and the (outgoing) mp3 feeds but some chairs felt that
>> was not enough. The mp3 feeds seemed to be too slow and presentations by
>> remote participants (which require at least incoming audio) were a
>> challenge.
>>
>> A few IETFers have developed a web conferencing and collaboration system
>> based on IETF protocols such as SIP, XMPP, BFCP, and RTP. They are
>> willing to make it available for WG chairs who want to try it during the
>> upcoming IETF in Prague. You can have a look at the system at:
>>
>> http://www.meetecho.com/
>>
>> Simon Pietro (who chairs the SPLICES WG) can provide you with more
>> information about the capabilities of the system and its requirements.
>> If you are interested in this, please let him know.
>>
>> Thanks,
>>
>> Gonzalo
>

-- 
                             _\\|//_
                             ( 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~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/


