
From agenda@ietf.org  Thu May 10 13:48:05 2012
Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D59A921F857A; Thu, 10 May 2012 13:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.2
X-Spam-Level: 
X-Spam-Status: No, score=-101.2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MWrsf1kJ1une; Thu, 10 May 2012 13:48:05 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CCDC21F8541; Thu, 10 May 2012 13:48:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 84th IETF - Working Group/BOF/IRTF Scheduling
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120510204805.5051.55270.idtracker@ietfa.amsl.com>
Date: Thu, 10 May 2012 13:48:05 -0700
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 10 May 2012 20:48:06 -0000

-----------------------------------------------------------------
84th IETF =E2=80=93 Vancouver, BC, Canada
Meeting Dates: July 29-August 3, 2012
Host: Google
-----------------------------------------------------------------
IETF meetings start Monday morning and run through Friday afternoon (13:30).

We are accepting scheduling requests for all Working Groups and BOFs starti=
ng today.  The milestones and deadlines for scheduling-related activities a=
re as follows:

NOTE: cutoff dates are subject to change.

- 2012-05-07 (Week of): Working Group and BOF scheduling begins. To request=
 a Working Group session, use the IETF Meeting Session Request Tool.
- 2012-06-04 (Monday): Cutoff date for requests to schedule Working Group m=
eetings at 17:00 PT (UTC -7). To request a Working Group session, use the I=
ETF Meeting Session Request Tool.
-2012-06-18 (Monday): Cutoff date for BOF proposal requests to Area Directo=
rs at 17:00 PT (UTC -7). To request a BOF, please see instructions on Reque=
sting a BOF.
- 2012-06-21 (Thursday): Cutoff date for Area Directors to approve BOFs at =
17:00 PT (UTC -7).
- 2012-06-28 (Thursday): Preliminary agenda published for comment.
- 2012-07-02 (Monday): Cutoff date for requests to reschedule Working Group=
 and BOF meetings 17:00 PT (UTC -7). =

- 2012-07-06 (Friday): Final agenda to be published.
- 2012-07-18 (Wednesday): Draft Working Group agendas due by 17:00 PT (UTC =
-7), upload using IETF Meeting Materials Management Tool.
- 2012-07-23 (Monday): Revised Working Group agendas due by 17:00 PT (UTC -=
7), upload using IETF Meeting Materials Management Tool. =

- 2012-08-31 (Friday): Proceedings submission cutoff date by 17:00 PT (UTC =
-7), upload using IETF Meeting Materials Management Tool.
- 2012-09-19 (Wednesday): Proceedings submission corrections cutoff date by=
 17:00 PT (UTC -7), 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 "I=
ETF Meeting Session Request Tool," a Web-based tool for submitting all of t=
he information that the Secretariat requires to schedule your sessions.

The URL for the tool is:

https://pub.ietf.org/sreq/

Please send requests to schedule your BOF sessions to agenda@ietf.org.  Ple=
ase 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 Meetin=
g 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 agenda=
s for your Working Group sessions as early as possible.  Draft Working Grou=
p agendas are due Wednesday, July 18, 2012 by 17:00.  Revised Working Group=
 agendas are due no later than Monday, July 23, 2012 at 17:00 PT.  The prop=
osed agenda for a BOF session should be submitted along with your request f=
or 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 M=
eeting 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://pub.ietf.org/proceedings/

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 84 Meeting Materials" Web page is:

https://datatracker.ietf.org/meeting/84/materials.html

If you are a Working Group chair, then you already have accounts on the "IE=
TF Meeting Session Request Tool" and the "IETF Meeting Materials Management=
 Tool."  The same User ID and password will work for both tools.  If you ar=
e 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 h=
as 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.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
For your convenience, comprehensive information on requesting meeting sessi=
ons at IETF 84 is presented below:

1. Requests to schedule Working Group sessions should be submitted using th=
e "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://pub.ietf.org/sreq/

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 ple=
ase send a message to ietf-action@ietf.org.  If you are unable to use the t=
ool, then you may send your request via e-mail to agenda@ietf.org, with a c=
opy to the appropriate Area Director(s).

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

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

2. BOFs will NOT be scheduled unless the Area Director(s) approved the BOF.=
 The proponents behind a BOF need to contact a relevant Area Director, pref=
erably well in advance of the BOF approval deadline date. The AD needs to h=
ave the full name of the BOF, its acronym, suggested names of chairs, an ag=
enda, full description of the BOF and the information covered in item 4. Pl=
ease read RFC 5434 for instructions on how to drive a successful BOF effort=
. The approval depends on, for instance, Internet-Drafts and list discussio=
n on the suggested topic. BOF agenda requests, if approved, will be submitt=
ed to the IETF Secretariat by the ADs.

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 availa=
bility, after Monday, July 2, 2012 at 17:00 PT, the cut-off date for reques=
ts 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 r=
efer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and Procedures" (=
http://www.ietf.org/rfc/rfc2418.txt).
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
For your convenience please find here a list of the IETF Area Directors wit=
h their e-mail addresses:

IETF Chair =

Russ Housley <housley@vigilsec.com> =


Applications Area (app)
Barry Leiba <barryleiba@computer.org>
Pete Resnick <presnick@qualcomm.com>

Internet Area (int) =

Ralph Droms <rdroms.ietf@gmail.com>
Brian Haberman <brian@innovationslab.net> =


Operations & Management Area (ops) =

Ronald Bonica <rbonica@juniper.net>
Benoit Claise <bclaise@cisco.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@olddog.co.uk>  =


Security Area (sec) =

Stephen Farrell <stephen.farrell@cs.tcd.ie>
Sean Turner <turners@ieca.com>  =


Transport Area (tsv) =

Wesley Eddy <wes@mti-systems.com>
Martin Stiemerling <martin.stiemerling@neclab.eu>  =

 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
83rd IETF Meeting Attendance Number
		=

6man - 141	=

6renum =E2=80=93 62
abfab =E2=80=93 29
alto - 70
ancp =E2=80=93 11
antitrust (BoF)	 - 60
appsawg - 125	=

armd =E2=80=93 42
atoca - 20
avtcore - 79
avtext =E2=80=93 52
bfcpbis	 - 28
bfd - 51
bmwg =E2=80=93 23
ccamp =E2=80=93 79
ccamp (2nd session) - 91
cdni =E2=80=93 118
cdni (2nd session) =E2=80=93 81
cfrg (RG) =E2=80=93 40
clue - 52
clue (2nd session) - 46
conex - 41
core - 133
core (2nd session) - 104
cuss - 21
decade =E2=80=93 31
dhc - 56
dime =E2=80=93 16
dispatch =E2=80=93 83
dmm - 55
dnsext - 99
dnsop - 87
drinks =E2=80=93 22
dtnrg (RG) - 35
ecrit - 39
eman - 70
emu - 27
forces =E2=80=93 60
geopriv - 22
grow - 63
homenet =E2=80=93 212
httpbis  - 187
hybi =E2=80=93 49
i2aex (BoF) - 120
iccrg (RG) - 92
idr - 93	=

insipid - 42
intarea (AG) - 97
ipfix =E2=80=93 28
ippm =E2=80=93 34
ipsecme =E2=80=93 30
iri - 14
isis - 61
jose - 77
karp - 31
kitten =E2=80=93 40
krb-wg =E2=80=93 55
l2vpn =E2=80=93 126
lisp - 93
lwig =E2=80=93 77
manet - 53
marf =E2=80=93 9
mboned - 24	=

mif - 69	=

mile =E2=80=93 27
mmusic - 81	=

mobopts (RG) - 44	=

mpls - 183
mpls (2nd session) - 112	=

mptcp - 64
multimob - 40
ncrg (RG) - 57	=

nea - 28
netconf - 31
netext - 54	=

netmod - 30	=

nfsv4 - 19
nvo3 (BoF) - 276	=

oauth - 75
opsarea (AG) - 64
opsawg - 64
opsec - 64
ospf - 66	=

p2psip - 39
paws - 32	=

pce - 64
pcn - 26
pcp - 78	=

pcp (2nd session) - 63
pim - 45
pkix - 52
ppsp - 30
pr=C3=A9cis - 26
pwe3 - 106
radext - 23	=

rfcform (BoF) - 98
repute - 40
rmt - 20
rpsreqs (BoF) - 33	=

rtcweb - 133
rtcweb (second session) - 163	=

rtgarea (AG) - 129	=

rtgwg - 72
saag (AG) -124
samrg (RG) - 17
scim (BoF) - 132	=

sidr - 77
sidr (2nd session) - 63	=

sipcore - 57	=

siprec - 27	=

soc - 30
softwire - 59
softwire (2nd session) - 76
spfbis - 18
tcpm - 38
tictoc - 24
tls - 59	=

trill - 75	=

trill (second session) - 65	=

tsvwg - 56
urnbis - 26
v6ops - 164	=

v6ops (second session) - 131
vipr - 22
websec - 97	=

weirds (BoF) - 80
xmpp - 34
xrblock - 32

From ietf-secretariat@ietf.org  Thu May 10 14:04:11 2012
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBED321F858A; Thu, 10 May 2012 14:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.299
X-Spam-Level: 
X-Spam-Status: No, score=-105.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mmV0gkt6iWac; Thu, 10 May 2012 14:04:11 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00D7021F855B; Thu, 10 May 2012 14:04:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF 84 - Registration Now Open
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120510210410.8819.90522.idtracker@ietfa.amsl.com>
Date: Thu, 10 May 2012 14:04:11 -0700
Cc: wgchairs@ietf.org, irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 10 May 2012 21:04:11 -0000

84th IETF Meeting
Vancouver, BC, Canada
July 29-August 3, 2012
Host: Google

Meeting venue:  Hyatt Regency Vancouver http://Vancouver.hyatt.com

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

1.  Registration
2.  Visas & Letters of Invitation
3.  Accommodations
4.  Companion Program

1. Registration
           A. Early-Bird Registration - USD 650.00 Pay by Friday, 20 July 2=
012 1700 PT (UTC -7)
           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,
                       23 July 2012 at 1700 PT (UTC -7).
                       Cancellations are subject to a 10% (ten percent)
                       cancellation fee if requested by that date and time.
           F. Online Registration and Payment ends Friday, 27 July 2012, 17=
00 local Vancouver time.
           G. On-site Registration starting Sunday, 29 July 2012 at 1100 lo=
cal Vancouver time.

2. Visas & Letters of Invitation:
           Information on Visiting Canada, please visit:
http://www.cic.gc.ca/english/visit/index.asp

           After you complete the registration process, you can request an =
electronic IETF Letter of Invitation. You may also request one at a later t=
ime by following the link provided in the confirmation email.

           Please note that the IETF Letter of Invitation may not be suffic=
ient for obtaining a visa to enter Canada.  At this time local host letters=
 of invitation are not available.  Please send an email to registrar@ietf.o=
rg if you require a host letter of invitation, and within the next week one=
 will be provided.

3.  Accommodations
           The IETF is holding blocks of guest rooms at 2 hotels in Vancouv=
er:
           Hyatt Regency Vancouver (Meeting Venue and Headquarter Hotel) an=
d the Sheraton Wall Centre (approximately 3 blocks from Hyatt, about 5-10 m=
inute walk)

           Room Rates include in room high-speed Internet access. Taxes of =
15% HST, 2% Occupancy and 1.5% Destination Management fee (applicable taxes=
 are subject to change) are excluded from the above prices. Room rates DO N=
OT include daily breakfast.

           Reservations Cut off Date:
           15 July 2012 at the Hyatt Regency Vancouver
           06 July 2012 at the Sheraton Wall Centre

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

4.  Companion Program
           If you are traveling with a friend or family member over 18 year=
s of age you can register them for the IETF Companion Program for only USD =
25.00

           Benefits include:
           - A special welcome reception for companions from 1630-1730 on S=
unday, 29 July
           - Ability to attend the official Welcome Reception from 1700-190=
0 on Sunday, 29 July
           - A distinctive meeting badge that grants access to the venue (n=
ot 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.

           To join the 84 companions mailing list see:
           https://www.ietf.org/mailman/listinfo/84companions

Only 79 days until the Vancouver IETF!

From martin.vigoureux@alcatel-lucent.com  Fri May 11 01:49:12 2012
Return-Path: <martin.vigoureux@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CEFE21F863B; Fri, 11 May 2012 01:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.049
X-Spam-Level: 
X-Spam-Status: No, score=-110.049 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VY1WQBCOmlR6; Fri, 11 May 2012 01:49:11 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 4637421F8628; Fri, 11 May 2012 01:49:10 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q4B8lkGU005552 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 11 May 2012 10:49:09 +0200
Received: from [172.27.205.189] (135.120.57.7) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 11 May 2012 10:48:49 +0200
Message-ID: <4FACD271.2010804@alcatel-lucent.com>
Date: Fri, 11 May 2012 10:48:49 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20
MIME-Version: 1.0
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: handling "replaced-by" via the datatracker [Re: latest missing replaced-by information]
References: <201204181418.QAA27098@TR-Sys.de>
In-Reply-To: <201204181418.QAA27098@TR-Sys.de>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Cc: "tools-discuss@ietf.org" <tools-discuss@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2012 08:49:12 -0000

Hello,

following up on that discussion, unless I am mistaken I do not see any 
way to manage the replaced-by status of drafts in the datatracker.
This applies both to drafts with a revision number greater or equal than 
01 and to newly adopted drafts.
If I am wrong I'd be glad if one of you could indicate me the way to
manage the replaced-by information via the tracker.
Otherwise, I think it would definitely be good if chairs could manage
this status via the tracker, and there seem to be some support for that.

Thanks
martin


Le 18/04/2012 16:18, ah@TR-Sys.de a écrit :
> RFC 6175 (WG Datatracker requirements) in Section 6.2 talks about...
>
> |  This will facilitate the Datatracker's ability to correctly
> |  capture "Replaces" information for WG drafts and "Replaced by"
> |  information for the individual submission I-Ds that are replaced
> |  by WG drafts.
>
> This is written in the context of pre-approval of WG drafts
> before submission (which so far seems not to be implemented
> in the Datatracker WG Chair user interface), but in the
> discussion on the draft for RFC 6175, IIRC it was clear that
> during approval of a WG -00 draft, a Chair needs to be able to
> supply the "Replaces" metadata -- or correct the preliminary
> guesses made by the system.  Somehow, this seems to have been
> lost during operation on the many change requests on the draft,
> but IMHO this requirement is implied in RFC 6175.
> It also has been discussed in the draft stage of RFC 6175 that
> the I-D upload tool should allow an I-D submitter to supply
> "replaces" metadata, without leading to manual processing
> of the submission by the Secretariat (as is the case for all
> metadata changes intended by the submitter); in the case of a
> WG draft adoption( WG -00 draft), the WG Chair UI then should
> allow to edit these metadata (if needed) before accepting the
> submission.
>
> I haven't a useful example at hands currently to exercise the
> procedure, but from a more detailed reading of RFC 6175, it looks
> like the desired functionality is seen in RFC 6175 part of WG Chair
> operation on the *individual* I-Ds being adopted, not on the
> 'draft-ietf-' ones.
>
> So could please someone with a pending draft adoption check whether
> they can enter the "replaced by" information for the individual I-D?
>
>
> Kind regards,
>    Alfred HÎnes.
>

From martin.vigoureux@alcatel-lucent.com  Fri May 11 04:02:17 2012
Return-Path: <martin.vigoureux@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1594A21F8449; Fri, 11 May 2012 04:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.099
X-Spam-Level: 
X-Spam-Status: No, score=-108.099 tagged_above=-999 required=5 tests=[AWL=-1.850, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a8PuAxbFhY+w; Fri, 11 May 2012 04:02:16 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [62.23.212.42]) by ietfa.amsl.com (Postfix) with ESMTP id 2111921F859E; Fri, 11 May 2012 04:02:15 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q4BB2734030526 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 11 May 2012 13:02:09 +0200
Received: from [172.27.205.189] (135.120.57.7) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 11 May 2012 13:02:09 +0200
Message-ID: <4FACF1B1.7040501@alcatel-lucent.com>
Date: Fri, 11 May 2012 13:02:09 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20
MIME-Version: 1.0
To: "afarrel@juniper.net" <afarrel@juniper.net>
Subject: Re: handling "replaced-by" via the datatracker [Re: latest missing replaced-by information]
References: <201204181418.QAA27098@TR-Sys.de> <4FACD271.2010804@alcatel-lucent.com> <02c801cd2f57$ec221810$c4664830$@juniper.net>
In-Reply-To: <02c801cd2f57$ec221810$c4664830$@juniper.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "tools-discuss@ietf.org" <tools-discuss@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2012 11:02:17 -0000

great! Thanks.

-m

Le 11/05/2012 11:24, Adrian Farrel a écrit :
> Hi,
>
> This popped up at the IESG retreat and Robert agreed to put it on the Tools Team
> To Do list.
>
> Is this a good time to remind you all of the code sprint that takes place on the
> day before each IETF meeting? Come along and help make the features you want to
> use a reality.
>
> Cheers,
> Adrian
>
>> -----Original Message-----
>> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
>> Martin Vigoureux
>> Sent: 11 May 2012 09:49
>> To: wgchairs@ietf.org
>> Cc: tools-discuss@ietf.org
>> Subject: handling "replaced-by" via the datatracker [Re: latest missing
> replaced-
>> by information]
>>
>> Hello,
>>
>> following up on that discussion, unless I am mistaken I do not see any
>> way to manage the replaced-by status of drafts in the datatracker.
>> This applies both to drafts with a revision number greater or equal than
>> 01 and to newly adopted drafts.
>> If I am wrong I'd be glad if one of you could indicate me the way to
>> manage the replaced-by information via the tracker.
>> Otherwise, I think it would definitely be good if chairs could manage
>> this status via the tracker, and there seem to be some support for that.
>>
>> Thanks
>> martin
>>
>>
>> Le 18/04/2012 16:18, ah@TR-Sys.de a écrit :
>>> RFC 6175 (WG Datatracker requirements) in Section 6.2 talks about...
>>>
>>> |  This will facilitate the Datatracker's ability to correctly
>>> |  capture "Replaces" information for WG drafts and "Replaced by"
>>> |  information for the individual submission I-Ds that are replaced
>>> |  by WG drafts.
>>>
>>> This is written in the context of pre-approval of WG drafts
>>> before submission (which so far seems not to be implemented
>>> in the Datatracker WG Chair user interface), but in the
>>> discussion on the draft for RFC 6175, IIRC it was clear that
>>> during approval of a WG -00 draft, a Chair needs to be able to
>>> supply the "Replaces" metadata -- or correct the preliminary
>>> guesses made by the system.  Somehow, this seems to have been
>>> lost during operation on the many change requests on the draft,
>>> but IMHO this requirement is implied in RFC 6175.
>>> It also has been discussed in the draft stage of RFC 6175 that
>>> the I-D upload tool should allow an I-D submitter to supply
>>> "replaces" metadata, without leading to manual processing
>>> of the submission by the Secretariat (as is the case for all
>>> metadata changes intended by the submitter); in the case of a
>>> WG draft adoption( WG -00 draft), the WG Chair UI then should
>>> allow to edit these metadata (if needed) before accepting the
>>> submission.
>>>
>>> I haven't a useful example at hands currently to exercise the
>>> procedure, but from a more detailed reading of RFC 6175, it looks
>>> like the desired functionality is seen in RFC 6175 part of WG Chair
>>> operation on the *individual* I-Ds being adopted, not on the
>>> 'draft-ietf-' ones.
>>>
>>> So could please someone with a pending draft adoption check whether
>>> they can enter the "replaced by" information for the individual I-D?
>>>
>>>
>>> Kind regards,
>>>     Alfred HÎnes.
>>>
>
>

From afarrel@juniper.net  Fri May 11 02:25:03 2012
Return-Path: <afarrel@juniper.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B35FF21F8621; Fri, 11 May 2012 02:25:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b04rvaG1EUxi; Fri, 11 May 2012 02:25:02 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD0921F861A; Fri, 11 May 2012 02:25:02 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q4B9OulI011243;  Fri, 11 May 2012 10:24:56 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q4B9Oten011183 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 11 May 2012 10:24:55 +0100
From: "Adrian Farrel" <afarrel@juniper.net>
To: "'Martin Vigoureux'" <martin.vigoureux@alcatel-lucent.com>, <wgchairs@ietf.org>
References: <201204181418.QAA27098@TR-Sys.de> <4FACD271.2010804@alcatel-lucent.com>
In-Reply-To: <4FACD271.2010804@alcatel-lucent.com>
Subject: RE: handling "replaced-by" via the datatracker [Re: latest missing	replaced-by information]
Date: Fri, 11 May 2012 10:24:52 +0100
Message-ID: <02c801cd2f57$ec221810$c4664830$@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQICmdavDkoq5AuQsACTuKCiqOeuoQFpNNgmlk4yIdA=
Content-Language: en-gb
X-Mailman-Approved-At: Fri, 11 May 2012 07:31:43 -0700
Cc: tools-discuss@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: afarrel@juniper.net
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2012 09:25:03 -0000

Hi,

This popped up at the IESG retreat and Robert agreed to put it on the =
Tools Team
To Do list.

Is this a good time to remind you all of the code sprint that takes =
place on the
day before each IETF meeting? Come along and help make the features you =
want to
use a reality.

Cheers,
Adrian

> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf =
Of
> Martin Vigoureux
> Sent: 11 May 2012 09:49
> To: wgchairs@ietf.org
> Cc: tools-discuss@ietf.org
> Subject: handling "replaced-by" via the datatracker [Re: latest =
missing
replaced-
> by information]
>=20
> Hello,
>=20
> following up on that discussion, unless I am mistaken I do not see any
> way to manage the replaced-by status of drafts in the datatracker.
> This applies both to drafts with a revision number greater or equal =
than
> 01 and to newly adopted drafts.
> If I am wrong I'd be glad if one of you could indicate me the way to
> manage the replaced-by information via the tracker.
> Otherwise, I think it would definitely be good if chairs could manage
> this status via the tracker, and there seem to be some support for =
that.
>=20
> Thanks
> martin
>=20
>=20
> Le 18/04/2012 16:18, ah@TR-Sys.de a =E9crit :
> > RFC 6175 (WG Datatracker requirements) in Section 6.2 talks about...
> >
> > |  This will facilitate the Datatracker's ability to correctly
> > |  capture "Replaces" information for WG drafts and "Replaced by"
> > |  information for the individual submission I-Ds that are replaced
> > |  by WG drafts.
> >
> > This is written in the context of pre-approval of WG drafts
> > before submission (which so far seems not to be implemented
> > in the Datatracker WG Chair user interface), but in the
> > discussion on the draft for RFC 6175, IIRC it was clear that
> > during approval of a WG -00 draft, a Chair needs to be able to
> > supply the "Replaces" metadata -- or correct the preliminary
> > guesses made by the system.  Somehow, this seems to have been
> > lost during operation on the many change requests on the draft,
> > but IMHO this requirement is implied in RFC 6175.
> > It also has been discussed in the draft stage of RFC 6175 that
> > the I-D upload tool should allow an I-D submitter to supply
> > "replaces" metadata, without leading to manual processing
> > of the submission by the Secretariat (as is the case for all
> > metadata changes intended by the submitter); in the case of a
> > WG draft adoption( WG -00 draft), the WG Chair UI then should
> > allow to edit these metadata (if needed) before accepting the
> > submission.
> >
> > I haven't a useful example at hands currently to exercise the
> > procedure, but from a more detailed reading of RFC 6175, it looks
> > like the desired functionality is seen in RFC 6175 part of WG Chair
> > operation on the *individual* I-Ds being adopted, not on the
> > 'draft-ietf-' ones.
> >
> > So could please someone with a pending draft adoption check whether
> > they can enter the "replaced by" information for the individual I-D?
> >
> >
> > Kind regards,
> >    Alfred H=CEnes.
> >


From wlo@amsl.com  Thu May 17 11:44:42 2012
Return-Path: <wlo@amsl.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1611321F86E2 for <wgchairs@ietfa.amsl.com>; Thu, 17 May 2012 11:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.854
X-Spam-Level: 
X-Spam-Status: No, score=-1.854 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 702jMN1lSuWM for <wgchairs@ietfa.amsl.com>; Thu, 17 May 2012 11:44:41 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 48CF821F86D4 for <wgchairs@ietf.org>; Thu, 17 May 2012 11:44:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 5590912C894; Thu, 17 May 2012 11:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5wv2aouAME0w; Thu, 17 May 2012 11:44:49 -0700 (PDT)
Received: from [12.22.58.170] (unknown [12.22.58.170]) by c8a.amsl.com (Postfix) with ESMTPSA id 347AD12C881; Thu, 17 May 2012 11:44:49 -0700 (PDT)
From: Wanda Lo <wlo@amsl.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-12-343311693
Subject: Request For IETF 83 WG and BOF Sessions Minutes and Presentations
Date: Thu, 17 May 2012 11:44:40 -0700
Message-Id: <CE3D35A9-11D5-400F-A29B-00E19D930E0B@amsl.com>
To: WG Chairs <wgchairs@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 18:44:42 -0000

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

Dear WG Chairs and BOF Chairs,
=20
The cutoff for submissions has past and I am still missing meeting =
minutes from various sessions.  Please upload meeting minutes, as well =
as any presentations from your sessions, at your earliest convenience =
using the Meeting Materials Manager found here: =
https://pub.ietf.org/proceedings/.  Alternatively, you are welcome to =
send them to proceedings@ietf.org or wlo@amsl.com for manual posting.

Groups I still need minutes from are:

Application Area
-core

Internet Area
-pcp
-trill

Operations and Management
-opsarea/opsawg


http://www.ietf.org/proceedings/83/index.html


If you have any questions, please let me know.=20
=20
Thanks,
Wanda





=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
Wanda Lo / Project Manager
Internet Engineering Task Force (IETF)
48377 Fremont Blvd., Ste. 117=20
Fremont, California 94538 / USA=20
T: +1.510.492.4082
F: +1.510.492.4001=20
www.ietf.org
=20
--
Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com





--Apple-Mail-12-343311693
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-family: Courier; "><span style=3D"font-family: =
Arial, sans-serif; "><font class=3D"Apple-style-span">Dear WG Chairs and =
BOF Chairs,<o:p></o:p></font></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-family: Courier; "><span style=3D"font-family: Arial, sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; "><span =
class=3D"Apple-style-span" style=3D"font-family: Arial, sans-serif; =
">The cutoff for submissions has past and&nbsp;</span><font =
class=3D"Apple-style-span"><span class=3D"Apple-style-span" =
style=3D"font-family: Arial, sans-serif; ">I am still missing meeting =
minutes from various sessions. &nbsp;</span></font><font =
class=3D"Apple-style-span"><span class=3D"Apple-style-span" =
style=3D"font-family: Arial, sans-serif; ">Please upload meeting =
minutes, as well as any presentations from your sessions, at your =
earliest convenience using the Meeting Materials Manager found =
here:&nbsp;</span></font><a =
href=3D"https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi" =
title=3D"blocked::https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.c=
gi" style=3D"font-family: Arial, sans-serif; color: blue; =
text-decoration: underline; ">https://pub.ietf.org/proceedings/</a><font =
class=3D"Apple-style-span" style=3D"font-family: Arial, sans-serif; =
">.&nbsp; Alternatively, you are welcome to send them to&nbsp;</font><a =
href=3D"mailto:proceedings@ietf.org" style=3D"font-family: Arial, =
sans-serif; color: blue; text-decoration: underline; =
">proceedings@ietf.org</a><font class=3D"Apple-style-span" =
style=3D"font-family: Arial, sans-serif; ">&nbsp;or&nbsp;</font><a =
href=3D"mailto:wlo@amsl.com" style=3D"font-family: Arial, sans-serif; =
color: blue; text-decoration: underline; ">wlo@amsl.com</a><font =
class=3D"Apple-style-span" style=3D"font-family: Arial, sans-serif; =
">&nbsp;for manual posting.<o:p></o:p></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-family: Courier; "><span style=3D"font-family: =
Arial, sans-serif; "><o:p><br></o:p></span></div><div style=3D"margin-top:=
 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
"><span class=3D"Apple-style-span" style=3D"font-family: Helvetica; =
">Groups I still need minutes from are:</span><div style=3D"font-family: =
Helvetica; "><br></div><div><b>Application Area</b></div><div =
style=3D"font-family: Helvetica; ">-core</div><div style=3D"font-family: =
Helvetica; "><br></div><div><b>Internet Area</b></div><div =
style=3D"font-family: Helvetica; ">-pcp</div><div style=3D"font-family: =
Helvetica; ">-trill</div><div style=3D"font-family: Helvetica; =
"><br></div><div><b>Operations and Management</b></div><div =
style=3D"font-family: Helvetica; ">-opsarea/opsawg</div><div =
style=3D"font-family: Helvetica; "><br></div><div style=3D"font-family: =
Helvetica; "><br></div><div style=3D"font-family: Helvetica; "><a =
href=3D"http://www.ietf.org/proceedings/83/index.html">http://www.ietf.org=
/proceedings/83/index.html</a></div><div><br></div><div><br></div>If you =
have any questions, please let me know.<font class=3D"Apple-style-span" =
face=3D"Arial, sans-serif">&nbsp;</font></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-family: Courier; "><span style=3D"font-family: Arial, sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-family: Courier; "><span style=3D"font-family: Arial, sans-serif; =
">Thanks,<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-family: Courier; "><span style=3D"font-family: Arial, sans-serif; =
">Wanda</span></div><div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Arial"><span style=3D"font-size: 10pt; font-family: Arial; "><br =
class=3D"Apple-interchange-newline"><br></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
font-family: Arial; "><br></span></font></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Arial"><span style=3D"font-size: 10pt; font-family: Arial; =
"><br></span></font></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Arial"><span =
style=3D"font-size: 10pt; font-family: Arial; =
"><br></span></font></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Arial"><span =
style=3D"font-size: 10pt; font-family: Arial; =
">=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</span></font><o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Arial"><span style=3D"font-size: 10pt; font-family: Arial; =
">Wanda Lo / Project Manager</span></font><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
font-family: Arial; ">Internet Engineering Task Force =
(IETF)</span></font><o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><st1:address =
w:st=3D"on"><st1:street w:st=3D"on"><font size=3D"2" face=3D"Arial"><span =
style=3D"font-size: 10pt; font-family: Arial; ">48377 Fremont Blvd., =
Ste. 117</span></font></st1:street><font size=3D"2" face=3D"Arial"><span =
style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;<br><st1:city =
w:st=3D"on">Fremont</st1:city>,&nbsp;<st1:state =
w:st=3D"on">California</st1:state>&nbsp;<st1:postalcode =
w:st=3D"on">94538</st1:postalcode></span></font></st1:address><font =
size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; font-family: =
Arial; ">&nbsp;/&nbsp;<st1:country-region w:st=3D"on"><st1:place =
w:st=3D"on">USA</st1:place></st1:country-region>&nbsp;<br>T: =
+1.510.492.4082<br>F: +1.510.492.4001&nbsp;<br><u><font =
color=3D"blue"><span =
title=3D"blocked::blocked::http://www.ipsphereforum.org/ =
blocked::http://www.ipsphereforum.org/"><span style=3D"color: blue; "><a =
href=3D"http://www.ietf.org/" style=3D"color: blue; text-decoration: =
underline; =
">www.ietf.org</a></span></span></font></u></span></font><o:p></o:p></div>=
<div style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: =
0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New =
Roman'; "><font size=3D"3" face=3D"Times New Roman"><span =
style=3D"font-size: 12pt; ">&nbsp;<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; =
"><i><font size=3D"1" face=3D"Verdana"><span style=3D"font-size: 7.5pt; =
font-family: Verdana; font-style: italic; "><span =
title=3D"blocked::blocked::http://www.ipsphereforum.org/ =
blocked::http://www.ipsphereforum.org/">--</span></span></font></i><i><fon=
t size=3D"1" face=3D"Arial"><span style=3D"font-size: 7.5pt; =
font-family: Arial; font-style: italic; =
"><o:p></o:p></span></font></i></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"1" =
face=3D"Arial"><span style=3D"font-size: 7.5pt; font-family: Arial; =
">Managed by Association Management Solutions =
(AMS)<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"1" =
face=3D"Arial"><span style=3D"font-size: 7.5pt; font-family: Arial; =
">Forum Management, Meeting and Event =
Planning<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"1" =
face=3D"Verdana"><span style=3D"font-size: 7.5pt; font-family: Verdana; =
"><a href=3D"http://www.amsl.com/" style=3D"color: blue; =
text-decoration: underline; "><font color=3D"purple" face=3D"Arial"><span =
style=3D"font-family: Arial; color: purple; =
">www.amsl.com</span></font></a></span></font></div></div></div><div><br><=
/div></div></span><br class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline"></div></span></div>
</div>
<br></body></html>=

--Apple-Mail-12-343311693--

From stpeter@stpeter.im  Mon May 21 19:44:00 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D3E221F855B; Mon, 21 May 2012 19:44:00 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id njcT2rTQQCYF; Mon, 21 May 2012 19:43:59 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 4543621F854F; Mon, 21 May 2012 19:43:56 -0700 (PDT)
Received: from [192.168.0.9] (unknown [216.17.175.135]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 371714005A; Mon, 21 May 2012 20:59:56 -0600 (MDT)
Message-ID: <4FBAFD6A.8030707@stpeter.im>
Date: Mon, 21 May 2012 20:43:54 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "George, Wes" <wesley.george@twcable.com>
Subject: Re: [vmeet] Remote participation
References: <4F737550.9070805@gmail.com> <DCC302FAA9FE5F4BBA4DCAD465693779173D5F98BD@PRVPEXVS03.corp.twcable.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD465693779173D5F98BD@PRVPEXVS03.corp.twcable.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Christopher LILJENSTOLPE <cdl@asgaard.org>, "vMeet@ietf.org" <vMeet@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2012 02:44:00 -0000

This is a very helpful page. I made a few tweaks, but not much was needed.

On 3/29/12 2:50 AM, George, Wes wrote:
> Melinda - This is great. I got volunteered to do this when I mentioned it at the plenary, so you just saved me a bunch of work. :-) Copying Peter and Chris, since they both volunteered to help.
> 
> I made a few changes in the wiki page, summarized below:
> 
> Paste the link to the presentation currently being discussed into the jabber room, and update which slide is being viewed so that participants can follow along with the slide deck (this assumes that Webex or Meetecho isn't being used).
> 
> It's often very difficult to understand people when they announce their names, and this helps to clarify (may also help the minutes-taker fill in details later). If you couldn't understand it to type it, chances are no one listening (who didn't already know the person) could either.
> 
> It may be worth noting that the audio stream typically runs at a 5-15 second delay, and give those proxying remote participant comments to the mic a priority interrupt/jump-the-line pass so that the comments are relayed while they are still relevant.
> 
> Thanks,
> 
> Wes George
> 
> 
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behalf
>> Of Melinda Shore
>> Sent: Wednesday, March 28, 2012 4:32 PM
>> To: wgchairs@ietf.org; vMeet@ietf.org
>> Subject: Re: [vmeet] Remote participation
>>
>> I've put up a first crack at a how-to-do-remote-good page, here:
>> http://wiki.tools.ietf.org/group/wgchairs/wiki/RemoteParticipation.
>> Please fix any errors, add any suggestions, etc. and otherwise have
>> at it.
>>
>> Melinda
> 
> This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.


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



From iad@ietf.org  Fri May 25 15:00:17 2012
Return-Path: <iad@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF84421F859B; Fri, 25 May 2012 15:00:16 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0sBZUJBT2ec2; Fri, 25 May 2012 15:00:16 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD4521F8512; Fri, 25 May 2012 15:00:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: RFP for IETF Meeting Agenda Scheduling Tool
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120525220016.11236.83513.idtracker@ietfa.amsl.com>
Date: Fri, 25 May 2012 15:00:16 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2012 22:00:17 -0000

The IETF Administrative Oversight Committee (IAOC), on behalf of the IETF, =
announces this Request for Proposals for an IETF Meeting Agenda Scheduling =
Tool.  The successful bidder will enter into a contract with the Internet S=
ociety.

The agenda tool will manage all meeting scheduling and space allocation ass=
ociated with interim meetings, Large Interim Meetings and regular IETF meet=
ings. This includes working group sessions, leadership meetings, EDU sessio=
ns, BoFs, office hours, registration, breaks, and more.

The Secretariat will construct the agenda template in the tool by entering =
venue, date and time information. The community will input the agenda conte=
nt by submitting session requests. The tool shall include an interface for =
an automatic schedule creation capability, which may optionally be included=
 in the initial delivery or procured in the future. The schedule creation c=
apability will generate a proposed agenda by finding the most appropriate m=
atch of venue (room capacity and availability) and the session request prof=
iles, which includes conflicts to be avoided. The tool will also be flexibl=
e enough to allow for ongoing updates and schedule regeneration as the meet=
ing content evolves.

Bidders may propose customization of an existing product(s), and/or develop=
ment of the solution.

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


Proposals must be received via email at agenda-tool@ietf-bids.org no later =
than July 9, 2012 5:00 P.M.  All questions/inquiries must be submitted in w=
riting and must be received no later than midnight, June 18, 2012.  Respons=
es to questions and inquiries shall be posted online at:  http://iaoc.ietf.=
org/rfpsrfis.html by June 22, 2012. =


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

Ray Pelletier



From agenda@ietf.org  Thu May 31 08:17:27 2012
Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79FE721F8754; Thu, 31 May 2012 08:17:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.2
X-Spam-Level: 
X-Spam-Status: No, score=-101.2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5lkf0-SRIwPc; Thu, 31 May 2012 08:17:26 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7740121F8743; Thu, 31 May 2012 08:17:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 84th IETF - Working Group/BOF/IRTF Scheduling REMINDER
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120531151726.8983.55735.idtracker@ietfa.amsl.com>
Date: Thu, 31 May 2012 08:17:26 -0700
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 31 May 2012 15:17:27 -0000

-----------------------------------------------------------------
84th IETF =E2=80=93 Vancouver, BC, Canada
Meeting Dates: July 29-August 3, 2012
Host: Google
-----------------------------------------------------------------
IETF meetings start Monday morning and run through Friday afternoon (13:30).

We are accepting scheduling requests for all Working Groups and BOFs starti=
ng today.  The milestones and deadlines for scheduling-related activities a=
re as follows:

NOTE: cutoff dates are subject to change.

- 2012-06-04 (Monday): Cutoff date for requests to schedule Working Group m=
eetings at 17:00 PT (UTC -7). To request a Working Group session, use the I=
ETF Meeting Session Request Tool.
-2012-06-18 (Monday): Cutoff date for BOF proposal requests to Area Directo=
rs at 17:00 PT (UTC -7). To request a BOF, please see instructions on Reque=
sting a BOF.
- 2012-06-21 (Thursday): Cutoff date for Area Directors to approve BOFs at =
17:00 PT (UTC -7).
- 2012-06-28 (Thursday): Preliminary agenda published for comment.
- 2012-07-02 (Monday): Cutoff date for requests to reschedule Working Group=
 and BOF meetings 17:00 PT (UTC -7). =

- 2012-07-06 (Friday): Final agenda to be published.
- 2012-07-18 (Wednesday): Draft Working Group agendas due by 17:00 PT (UTC =
-7), upload using IETF Meeting Materials Management Tool.
- 2012-07-23 (Monday): Revised Working Group agendas due by 17:00 PT (UTC -=
7), upload using IETF Meeting Materials Management Tool. =

- 2012-08-31 (Friday): Proceedings submission cutoff date by 17:00 PT (UTC =
-7), upload using IETF Meeting Materials Management Tool.
- 2012-09-19 (Wednesday): Proceedings submission corrections cutoff date by=
 17:00 PT (UTC -7), 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 "I=
ETF Meeting Session Request Tool," a Web-based tool for submitting all of t=
he information that the Secretariat requires to schedule your sessions.

The URL for the tool is:

https://pub.ietf.org/sreq/

Please send requests to schedule your BOF sessions to agenda@ietf.org.  Ple=
ase 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 Meetin=
g 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 agenda=
s for your Working Group sessions as early as possible.  Draft Working Grou=
p agendas are due Wednesday, July 18, 2012 by 17:00.  Revised Working Group=
 agendas are due no later than Monday, July 23, 2012 at 17:00 PT.  The prop=
osed agenda for a BOF session should be submitted along with your request f=
or 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 M=
eeting 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://pub.ietf.org/proceedings/

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 84 Meeting Materials" Web page is:

https://datatracker.ietf.org/meeting/84/materials.html

If you are a Working Group chair, then you already have accounts on the "IE=
TF 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 ha=
s been approved.  If you require assistance in using either tool, or wish t=
o report a bug, then please send a message to:
ietf-action@ietf.org.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
For your convenience, comprehensive information on requesting meeting sessi=
ons at IETF 84 is presented below:

1. Requests to schedule Working Group sessions should be submitted using th=
e "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://pub.ietf.org/sreq/

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 ple=
ase send a message to ietf-action@ietf.org.  If you are unable to use the t=
ool, then you may send your request via e-mail to agenda@ietf.org, with a c=
opy to the appropriate Area Director(s).

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

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

2. BOFs will NOT be scheduled unless the Area Director(s) approved the BOF.=
 The proponents behind a BOF need to contact a relevant Area Director, pref=
erably well in advance of the BOF approval deadline date. The AD needs to h=
ave the full name of the BOF, its acronym, suggested names of chairs, an ag=
enda, full description of the BOF and the information covered in item 4. Pl=
ease read RFC 5434 for instructions on how to drive a successful BOF effort=
. The approval depends on, for instance, Internet-Drafts and list discussio=
n on the suggested topic. BOF agenda requests, if approved, will be submitt=
ed to the IETF Secretariat by the ADs.

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 availa=
bility, after Monday, July 2, 2012 at 17:00 PT, the cut-off date for reques=
ts 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 r=
efer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and Procedures" (=
http://www.ietf.org/rfc/rfc2418.txt).
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
For your convenience please find here a list of the IETF Area Directors wit=
h their e-mail addresses:

IETF Chair =

Russ Housley <housley@vigilsec.com> =


Applications Area (app)
Barry Leiba <barryleiba@computer.org>
Pete Resnick <presnick@qualcomm.com>

Internet Area (int) =

Ralph Droms <rdroms.ietf@gmail.com>
Brian Haberman <brian@innovationslab.net> =


Operations & Management Area (ops) =

Ronald Bonica <rbonica@juniper.net>
Benoit Claise <bclaise@cisco.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@olddog.co.uk>  =


Security Area (sec) =

Stephen Farrell <stephen.farrell@cs.tcd.ie>
Sean Turner <turners@ieca.com>  =


Transport Area (tsv) =

Wesley Eddy <wes@mti-systems.com>
Martin Stiemerling <martin.stiemerling@neclab.eu>  =

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
83rd IETF Meeting Attendance Number
		=

6man - 141	=

6renum =E2=80=93 62
abfab =E2=80=93 29
alto - 70
ancp =E2=80=93 11
antitrust (BoF)	 - 60
appsawg - 125	=

armd =E2=80=93 42
atoca - 20
avtcore - 79
avtext =E2=80=93 52
bfcpbis	 - 28
bfd - 51
bmwg =E2=80=93 23
ccamp =E2=80=93 79
ccamp (2nd session) - 91
cdni =E2=80=93 118
cdni (2nd session) =E2=80=93 81
cfrg (RG) =E2=80=93 40
clue - 52
clue (2nd session) - 46
conex - 41
core - 133
core (2nd session) - 104
cuss - 21
decade =E2=80=93 31
dhc - 56
dime =E2=80=93 16
dispatch =E2=80=93 83
dmm - 55
dnsext - 99
dnsop - 87
drinks =E2=80=93 22
dtnrg (RG) - 35
ecrit - 39
eman - 70
emu - 27
forces =E2=80=93 60
geopriv - 22
grow - 63
homenet =E2=80=93 212
httpbis  - 187
hybi =E2=80=93 49
i2aex (BoF) - 120
iccrg (RG) - 92
idr - 93	=

insipid - 42
intarea (AG) - 97
ipfix =E2=80=93 28
ippm =E2=80=93 34
ipsecme =E2=80=93 30
iri - 14
isis - 61
jose - 77
karp - 31
kitten =E2=80=93 40
krb-wg =E2=80=93 55
l2vpn =E2=80=93 126
lisp - 93
lwig =E2=80=93 77
manet - 53
marf =E2=80=93 9
mboned - 24	=

mif - 69	=

mile =E2=80=93 27
mmusic - 81	=

mobopts (RG) - 44	=

mpls - 183
mpls (2nd session) - 112	=

mptcp - 64
multimob - 40
ncrg (RG) - 57	=

nea - 28
netconf - 31
netext - 54	=

netmod - 30	=

nfsv4 - 19
nvo3 (BoF) - 276	=

oauth - 75
opsarea (AG) - 64
opsawg - 64
opsec - 64
ospf - 66	=

p2psip - 39
paws - 32	=

pce - 64
pcn - 26
pcp - 78	=

pcp (2nd session) - 63
pim - 45
pkix - 52
ppsp - 30
pr=C3=A9cis - 26
pwe3 - 106
radext - 23	=

rfcform (BoF) - 98
repute - 40
rmt - 20
rpsreqs (BoF) - 33	=

rtcweb - 133
rtcweb (second session) - 163	=

rtgarea (AG) - 129	=

rtgwg - 72
saag (AG) -124
samrg (RG) - 17
scim (BoF) - 132	=

sidr - 77
sidr (2nd session) - 63	=

sipcore - 57	=

siprec - 27	=

soc - 30
softwire - 59
softwire (2nd session) - 76
spfbis - 18
tcpm - 38
tictoc - 24
tls - 59	=

trill - 75	=

trill (second session) - 65	=

tsvwg - 56
urnbis - 26
v6ops - 164	=

v6ops (second session) - 131
vipr - 22
websec - 97	=

weirds (BoF) - 80
xmpp - 34
xrblock - 32

From ietf-secretariat@ietf.org  Thu May 31 08:32:21 2012
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0BC11E80C8; Thu, 31 May 2012 08:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.166
X-Spam-Level: 
X-Spam-Status: No, score=-101.166 tagged_above=-999 required=5 tests=[AWL=-1.167, BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bYJsbS4il+aJ; Thu, 31 May 2012 08:32:20 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C40D11E80C7; Thu, 31 May 2012 08:32:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF 84 - Social Event
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120531153220.12145.59868.idtracker@ietfa.amsl.com>
Date: Thu, 31 May 2012 08:32:20 -0700
Cc: wgchairs@ietf.org, irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 31 May 2012 15:32:21 -0000

Only 58 days until the Vancouver IETF! =

Online registration for the IETF meeting is at: =

http://www.ietf.org/meetings/84/
Follow the IETF on twitter @ietf

IETF 84 - Social Event
Where: Telus World of Science =

Date: Tuesday, July 31, 2012
Time: 19:00 - 23:00 hours
Cost: $25 USD per person.
Availability: Open to all!!
Host: Google

Telus World of Science - Science World has recently completed a $35-million=
 renovation at its False Creek facility, adding 30,000 square feet of space=
, a green roof, and many energy=E2=80=90efficient initiatives with lots of =
hands-on exhibits.

Science World is home to five permanent galleries: the Eureka! Gallery, the=
 Sara Stern Search Gallery, the Kidspace Gallery, the Our World Gallery, an=
d Illusions. It also boasts a feature gallery for special exhibitions.

Both the 11,000 square-foot Eureka! Gallery and the facility=E2=80=99s new =
green roof provide incredible views of False Creek and the city skyline. Ex=
periment with water, light, sound, air and motion among the colourful and l=
ively exhibits in Eureka! Hands-on fun encourages visitors to ask "what wou=
ld happen if...?" Home to the popular water table with launchable balls, Eu=
reka! is a place where you can also launch a parachute, spin on a rotating =
platform, and capture your shadow. Eureka! is also home to the Engineering =
Lab by the James Dyson Foundation.

Experience Da Vinci - the genius, the most comprehensive exhibition ever co=
mpiled on the works of Leonardo da Vinci. This 10,000-square-foot exhibitio=
n features a vast array of full-scale machine inventions crafted from da Vi=
nci's personal notebooks; amazing anatomical sketches; reproductions of his=
 most famous Renaissance art examined in extraordinary detail, including th=
e Mona Lisa and the Virgin of the Rocks; and three-dimensional interactive =
presentations of the Last Supper and the Vitruvian Man. =


In addition guests will enjoy a showing at the famous OMNIMAX=C2=AE Theatre=
. It boasts a five-story high dome screen with an IMAX projection and surro=
und sound.

Getting there: World of Science is easily accessible via rail system SkyTra=
in from Burrad St (at Hyatt) - take SkyTrain EXPO Line to King George, exit=
 at Main Street/Science World SkyTrain Station. Approximately a 4 minute ri=
de. =


Food and Beverage:  Lots of local cuisine available to suit various dietary=
 choices. Buffet dinner and beverage service.

NOTE: You must be registered for IETF 84 to purchase a Social Ticket.  =

If you have already registered for the IETF, please use this link to
purchase a social ticket:
https://www.ietf.org/registration/ietf84/eventticket.py =


Only 58 days until the Vancouver IETF! =

Online registration for the IETF meeting is at: =

http://www.ietf.org/meetings/84/
Follow the IETF on twitter @ietf

From Sandra.Murphy@sparta.com  Thu May 31 10:36:53 2012
Return-Path: <Sandra.Murphy@sparta.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BDF311E8081 for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 10:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.267
X-Spam-Level: 
X-Spam-Status: No, score=-102.267 tagged_above=-999 required=5 tests=[AWL=-0.268, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9sT7tfsVwg9 for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 10:36:53 -0700 (PDT)
Received: from M4.sparta.com (M4.sparta.com [157.185.61.2]) by ietfa.amsl.com (Postfix) with ESMTP id F361F11E80E9 for <wgchairs@ietf.org>; Thu, 31 May 2012 10:36:52 -0700 (PDT)
Received: from Beta5.sparta.com (beta5.sparta.com [157.185.63.21]) by M4.sparta.com (8.14.4/8.14.4) with ESMTP id q4VHaqDS002107 for <wgchairs@ietf.org>; Thu, 31 May 2012 12:36:52 -0500
Received: from Hermes.columbia.ads.sparta.com ([157.185.80.107]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id q4VHaqk7021813 for <wgchairs@ietf.org>; Thu, 31 May 2012 12:36:52 -0500
Received: from HERMES.columbia.ads.sparta.com ([2002:9db9:506b::9db9:506b]) by Hermes.columbia.ads.sparta.com ([::1]) with mapi id 14.01.0355.002; Thu, 31 May 2012 13:36:52 -0400
From: "Murphy, Sandra" <Sandra.Murphy@sparta.com>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: pre-RIPE multiple IETF wg interim meetings
Thread-Topic: pre-RIPE multiple IETF wg interim meetings
Thread-Index: Ac0/Sy+jilRfyvVZRcmfjYuNpIO9NQ==
Date: Thu, 31 May 2012 17:36:51 +0000
Message-ID: <24B20D14B2CD29478C8D5D6E9CBB29F625F12F3C@Hermes.columbia.ads.sparta.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.185.63.137]
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.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 31 May 2012 17:36:53 -0000

SIDR is considering an interim meeting scheduled for pre/post RIPE in Septe=
mber, on the grounds that multiple wgs were considering interim meetings ar=
ound the RIPE meeting.=0A=
=0A=
The RIPE community is important to the SIDR work, so that made sense.=0A=
=0A=
I see email traffic in the last few weeks on v6ops to consider a RIPE tethe=
red interim.=0A=
=0A=
Are there other wgs are considering interim meetings around RIPE?=0A=
=0A=
Does anyone have a view as to whether the IETF would be willing to support =
such a gathering of interims?  (I.e., do the wgs who want to do this need t=
o find their own logistics?  Individually or together?)=0A=
=0A=
--Sandy, sidr co-chair=

From stpeter@stpeter.im  Thu May 31 10:39:59 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11B7211E80E0 for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 10:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.282
X-Spam-Level: 
X-Spam-Status: No, score=-102.282 tagged_above=-999 required=5 tests=[AWL=-0.283, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CaW537YKs8wT for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 10:39:58 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 94F5C11E80A4 for <wgchairs@ietf.org>; Thu, 31 May 2012 10:39:58 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id ABFB94005A; Thu, 31 May 2012 11:56:29 -0600 (MDT)
Message-ID: <4FC7ACED.2050305@stpeter.im>
Date: Thu, 31 May 2012 11:39:57 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Murphy, Sandra" <Sandra.Murphy@sparta.com>
Subject: Re: pre-RIPE multiple IETF wg interim meetings
References: <24B20D14B2CD29478C8D5D6E9CBB29F625F12F3C@Hermes.columbia.ads.sparta.com>
In-Reply-To: <24B20D14B2CD29478C8D5D6E9CBB29F625F12F3C@Hermes.columbia.ads.sparta.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 31 May 2012 17:39:59 -0000

On 5/31/12 11:36 AM, Murphy, Sandra wrote:
> SIDR is considering an interim meeting scheduled for pre/post RIPE in
> September, on the grounds that multiple wgs were considering interim
> meetings around the RIPE meeting.
> 
> The RIPE community is important to the SIDR work, so that made
> sense.
> 
> I see email traffic in the last few weeks on v6ops to consider a RIPE
> tethered interim.
> 
> Are there other wgs are considering interim meetings around RIPE?
> 
> Does anyone have a view as to whether the IETF would be willing to
> support such a gathering of interims?  (I.e., do the wgs who want to
> do this need to find their own logistics?  Individually or
> together?)

Talk with your Area Director. When I was on the IESG earlier this year,
we had active discussions about clustered interim meetings close in time
and space to events like RIPE. Sounds like a good idea to me.

Peter

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



From warren@kumari.net  Thu May 31 11:00:31 2012
Return-Path: <warren@kumari.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54C8C21F86D5 for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 11:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.086
X-Spam-Level: 
X-Spam-Status: No, score=-106.086 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jjEOcgtHAfwX for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 11:00:30 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id CFC1821F86D4 for <wgchairs@ietf.org>; Thu, 31 May 2012 11:00:30 -0700 (PDT)
Received: from [192.168.0.12] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 234531B402F2; Thu, 31 May 2012 14:00:30 -0400 (EDT)
Subject: Re: pre-RIPE multiple IETF wg interim meetings
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <24B20D14B2CD29478C8D5D6E9CBB29F625F12F3C@Hermes.columbia.ads.sparta.com>
Date: Thu, 31 May 2012 14:00:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E881943-0BA0-4CF0-A97A-FF7278F0CFEF@kumari.net>
References: <24B20D14B2CD29478C8D5D6E9CBB29F625F12F3C@Hermes.columbia.ads.sparta.com>
To: "Murphy, Sandra" <Sandra.Murphy@sparta.com>
X-Mailer: Apple Mail (2.1278)
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 31 May 2012 18:00:31 -0000

On May 31, 2012, at 1:36 PM, Murphy, Sandra wrote:

> SIDR is considering an interim meeting scheduled for pre/post RIPE in =
September, on the grounds that multiple wgs were considering interim =
meetings around the RIPE meeting.
>=20
> The RIPE community is important to the SIDR work, so that made sense.
>=20
> I see email traffic in the last few weeks on v6ops to consider a RIPE =
tethered interim.
>=20
> Are there other wgs are considering interim meetings around RIPE?

I believe that OpSec is considering an interim the collocated with RIPE=85=


W


>=20
> Does anyone have a view as to whether the IETF would be willing to =
support such a gathering of interims?  (I.e., do the wgs who want to do =
this need to find their own logistics?  Individually or together?)
>=20
> --Sandy, sidr co-chair


From rpelletier@isoc.org  Thu May 31 12:43:56 2012
Return-Path: <rpelletier@isoc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5886521F8755 for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 12:43:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.164
X-Spam-Level: 
X-Spam-Status: No, score=-103.164 tagged_above=-999 required=5 tests=[AWL=-0.165, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TwFubAkjGT3M for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 12:43:55 -0700 (PDT)
Received: from smtp125.iad.emailsrvr.com (smtp125.iad.emailsrvr.com [207.97.245.125]) by ietfa.amsl.com (Postfix) with ESMTP id DAA1721F8754 for <wgchairs@ietf.org>; Thu, 31 May 2012 12:43:55 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp32.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id EF15D14892E; Thu, 31 May 2012 15:43:54 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp32.relay.iad1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 1B060148859;  Thu, 31 May 2012 15:43:53 -0400 (EDT)
Subject: Re: pre-RIPE multiple IETF wg interim meetings
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <24B20D14B2CD29478C8D5D6E9CBB29F625F12F3C@Hermes.columbia.ads.sparta.com>
Date: Thu, 31 May 2012 15:43:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1FB768C9-5B80-42AF-836E-42C080E16119@isoc.org>
References: <24B20D14B2CD29478C8D5D6E9CBB29F625F12F3C@Hermes.columbia.ads.sparta.com>
To: "Murphy, Sandra" <Sandra.Murphy@sparta.com>
X-Mailer: Apple Mail (2.1084)
Cc: Chairs Working Group <wgchairs@ietf.org>, Housley Russ <housley@vigilsec.com>, Nugent Laura <lnugent@amsl.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 31 May 2012 19:43:56 -0000

On May 31, 2012, at 1:36 PM, Murphy, Sandra wrote:

> SIDR is considering an interim meeting scheduled for pre/post RIPE in =
September, on the grounds that multiple wgs were considering interim =
meetings around the RIPE meeting.
>=20
> The RIPE community is important to the SIDR work, so that made sense.
>=20
> I see email traffic in the last few weeks on v6ops to consider a RIPE =
tethered interim.
>=20
> Are there other wgs are considering interim meetings around RIPE?
>=20
> Does anyone have a view as to whether the IETF would be willing to =
support such a gathering of interims?  (I.e., do the wgs who want to do =
this need to find their own logistics?  Individually or together?)

Yes, the IETF is going to support a Large Interim Meeting in Amsterdam.  =
The tentative dates are 29 and 30 September.
We are hoping to use the same facility.  You will soon get guidance =
regarding the process of making known your interest in participating at =
the LIM.

Ray


>=20
> --Sandy, sidr co-chair


From fred@cisco.com  Thu May 31 14:24:22 2012
Return-Path: <fred@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6022721F85D4 for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 14:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.185
X-Spam-Level: 
X-Spam-Status: No, score=-110.185 tagged_above=-999 required=5 tests=[AWL=-0.186, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jzww0Urviadv for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 14:24:21 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id C129221F8493 for <wgchairs@ietf.org>; Thu, 31 May 2012 14:24:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2351; q=dns/txt; s=iport; t=1338499461; x=1339709061; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=GSsNws1dST4rVA2tNVuUtUmy4tb7EUwpY/7oPpnjwmM=; b=lAG16tVGWFonABbE1T4rGOYKQ/NDKKmGeJK/DZuViXqtCt5QXKIt4evx nD8d5PkAwHjb0gu2kO7YRzovaP4DqCZroiHDUZjbJ+duWreB88kd2GSz8 CxJcrr/8G4r7dI7UZ0z7j7aKQSH+hxuRQ4bNlg8gYqE9kr2NtTSJz1OKw w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAMPgx0+rRDoJ/2dsb2JhbABEtBWBB4IYAQEBBBIBJz8QCw4KLlcGJw6HaJkLn1OLEYRmYAOIQIxYhU+IPoFmgwCBNgcC
X-IronPort-AV: E=Sophos;i="4.75,693,1330905600"; d="scan'208";a="44067212"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 31 May 2012 21:24:21 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q4VLOKaC004130; Thu, 31 May 2012 21:24:20 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Thu, 31 May 2012 14:24:21 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Thu, 31 May 2012 14:24:21 -0700
Subject: Re: pre-RIPE multiple IETF wg interim meetings
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <1FB768C9-5B80-42AF-836E-42C080E16119@isoc.org>
Date: Thu, 31 May 2012 14:23:51 -0700
Message-Id: <3AD36537-E184-4DEB-826F-EF4B281B421A@cisco.com>
References: <24B20D14B2CD29478C8D5D6E9CBB29F625F12F3C@Hermes.columbia.ads.sparta.com> <1FB768C9-5B80-42AF-836E-42C080E16119@isoc.org>
To: Ray Pelletier <rpelletier@isoc.org>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Chairs Working Group <wgchairs@ietf.org>, Housley Russ <housley@vigilsec.com>, Nugent Laura <lnugent@amsl.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 31 May 2012 21:24:22 -0000

On May 31, 2012, at 12:43 PM, Ray Pelletier wrote:
> On May 31, 2012, at 1:36 PM, Murphy, Sandra wrote:
>> SIDR is considering an interim meeting scheduled for pre/post RIPE in =
September, on the grounds that multiple wgs were considering interim =
meetings around the RIPE meeting.
>>=20
>> The RIPE community is important to the SIDR work, so that made sense.
>>=20
>> I see email traffic in the last few weeks on v6ops to consider a RIPE =
tethered interim.
>>=20
>> Are there other wgs are considering interim meetings around RIPE?
>>=20
>> Does anyone have a view as to whether the IETF would be willing to =
support such a gathering of interims?  (I.e., do the wgs who want to do =
this need to find their own logistics?  Individually or together?)
>=20
> Yes, the IETF is going to support a Large Interim Meeting in =
Amsterdam.  The tentative dates are 29 and 30 September.
> We are hoping to use the same facility.  You will soon get guidance =
regarding the process of making known your interest in participating at =
the LIM.
>=20
> Ray

Well, yes. Russ has been interested in clustering interims; I *think* he =
is considering moving in the direction of replacing/augmenting the =
current schedule with smaller meetings of busy working groups. v6ops has =
been under a ddos of high rate low value drafts, has tried several =
approaches to dealing with it without the appearance of bias or =
favoritism, and has been repeatedly asked whether it would be a =
candidate for such additional meetings.

The comment we have gotten from the working group is that work will =
expand to fill the available capacity; they would prefer to restrict =
proposed work rather than increase meeting count. That said, if a =
meeting occurs on 29 September, we have tentative agreement from some of =
our members to attend, and I am currently planning other events around =
RIPE-65 on the assumption we will go there.

The sunset4 WG, assuming it comes into being, is ostensibly targeted at =
offloading work that comes to v6ops. However, as currently chartered, it =
requires a recharter from the IESG to do anything beyond occupy schedule =
space - or so its chairs tell me. Hence, I can't actually send proposed =
work to it. It's another meeting to spend time in, but it's not clear =
that it adds value.



From mary.ietf.barnes@gmail.com  Thu May 31 14:52:02 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E1E221F8655 for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 14:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.279
X-Spam-Level: 
X-Spam-Status: No, score=-103.279 tagged_above=-999 required=5 tests=[AWL=-0.281, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZUIs34mfydja for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 14:52:01 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id B9D9821F864F for <wgchairs@ietf.org>; Thu, 31 May 2012 14:52:00 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1023953vbb.31 for <wgchairs@ietf.org>; Thu, 31 May 2012 14:52:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sHd9rxV1PMF2kssKqixu9gURO4yFjNKuc6Fg+2AaDpM=; b=lNonSqu58qpSf/zzMIS36V8gc6WQsd1+ofkQ/oOXYMmcD0pSdwd/quLhYiO3qOuG/b vCChLX0LT+FdXdfaeBcLao+IA6GCOilGQ6C2NynjkT+ROJKrYRKGVFLgyNCbfp8oX0Qw 8cvp8IyhzPVa0+t7UwEaO91nZo858iyQRsOPXYlwH/t0bUBx3vuJPDvNv9bJzRYY90Tb dk8R2+9r67xdn8v9s6mxeBvPgQizda+xbeLVUlRtqara47LF06vsyKuzbapff1Fk02PB eQ99eLpctnnMChtBoFErHDxC5Dq/o1yq3co2o1mke0U9yg6+Rqq572Uy3XklYxxXqAec hJVQ==
MIME-Version: 1.0
Received: by 10.220.242.6 with SMTP id lg6mr111997vcb.18.1338501119867; Thu, 31 May 2012 14:51:59 -0700 (PDT)
Received: by 10.52.22.143 with HTTP; Thu, 31 May 2012 14:51:59 -0700 (PDT)
In-Reply-To: <3AD36537-E184-4DEB-826F-EF4B281B421A@cisco.com>
References: <24B20D14B2CD29478C8D5D6E9CBB29F625F12F3C@Hermes.columbia.ads.sparta.com> <1FB768C9-5B80-42AF-836E-42C080E16119@isoc.org> <3AD36537-E184-4DEB-826F-EF4B281B421A@cisco.com>
Date: Thu, 31 May 2012 16:51:59 -0500
Message-ID: <CAHBDyN42PDXZKnTqTKdFwSQWK85=nMsK7f9x=dnjGw=8wjGxCA@mail.gmail.com>
Subject: Re: pre-RIPE multiple IETF wg interim meetings
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Ray Pelletier <rpelletier@isoc.org>
Content-Type: multipart/alternative; boundary=14dae9ccd488c7fc2104c15c1353
Cc: Chairs Working Group <wgchairs@ietf.org>, Housley Russ <housley@vigilsec.com>, Nugent Laura <lnugent@amsl.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 31 May 2012 21:52:02 -0000

--14dae9ccd488c7fc2104c15c1353
Content-Type: text/plain; charset=ISO-8859-1

I personally have a concern with IETF sponsoring these large interim
meetings. The past model has been that these are sponsored by the
individuals' companies/sponsors as these are typically the folks that have
a vested interest in getting the work done in a timely manner.  I don't
recall any community discussion of this proposal.  I would think IETF funds
would be better allocated to the main IETF meetings when there is not a
sponsor and the entire community benefits.

In the RAI area, we have arranged an interim meeting that starts in a weeks
time that is intended to optimize the participation for folks involved in
two WGs and to encourage cross pollination as there will be a fair amount
of overlap in the solution space.  There will also be a related W3C meeting
in this block of meetings.  It was a challenge to organize this to optimize
participation for all the groups, as we ended up with a weekend between the
two meetings.  However, we do have a sponsor and while the location isn't
optimal (it's not in the city center) and getting hotel rooms was a
challenge as the meeting happened to be scheduled starting the day after a
major holiday Sweden, everyone seemed to manage their arrangements without
needing support from the secretariat,etc.  I think the burden was
rightfully placed on the individuals as well as their
corporations/sponsors.

Personally, I wonder if adding that burden to the secretariat would be a
good thing.  As a WG chair, it is somewhat of a challenge to manage prep
for the upcoming IETF meetings (with deadlines looming for the WGs) while
prepping for an interim meeting.  Recently, the secretariat has setup the
materials manager for the proceedings. which is a nice convenience, but I
don't see it a necessity to get them involved in planning interim meetings.


Although, reading this, it seems the suggestion is to evolve to this
smaller cluster of meetings model - i.e., the "augment/replace" suggestion.
  I don't think that's a good thing.  In some rare cases where there isn't
a RAI meeting that is of interest to me, I find it informative to attend
other WG sessions - e.g., APP area or OPS area meetings.  Also, RAI for
example, has overlap with a lot of areas.  So, we would lose some of the
expertise that can be helpful in getting our work progressed.  For example,
sitting down with a SEC AD to work through their list of discusses.
 Unless, of course the leadership must attend all these meeting clusters.
However, that would add to their burden and there is always discussion as
to how to reduce the overall burden.

I personally think we would be heading down a very slippery slope if IETF
starts sponsoring the interim meetings and evolves to a clustering model
for meetings.

Mary.

On Thu, May 31, 2012 at 4:23 PM, Fred Baker <fred@cisco.com> wrote:

>
> On May 31, 2012, at 12:43 PM, Ray Pelletier wrote:
> > On May 31, 2012, at 1:36 PM, Murphy, Sandra wrote:
> >> SIDR is considering an interim meeting scheduled for pre/post RIPE in
> September, on the grounds that multiple wgs were considering interim
> meetings around the RIPE meeting.
> >>
> >> The RIPE community is important to the SIDR work, so that made sense.
> >>
> >> I see email traffic in the last few weeks on v6ops to consider a RIPE
> tethered interim.
> >>
> >> Are there other wgs are considering interim meetings around RIPE?
> >>
> >> Does anyone have a view as to whether the IETF would be willing to
> support such a gathering of interims?  (I.e., do the wgs who want to do
> this need to find their own logistics?  Individually or together?)
> >
> > Yes, the IETF is going to support a Large Interim Meeting in Amsterdam.
>  The tentative dates are 29 and 30 September.
> > We are hoping to use the same facility.  You will soon get guidance
> regarding the process of making known your interest in participating at the
> LIM.
> >
> > Ray
>
> Well, yes. Russ has been interested in clustering interims; I *think* he
> is considering moving in the direction of replacing/augmenting the current
> schedule with smaller meetings of busy working groups. v6ops has been under
> a ddos of high rate low value drafts, has tried several approaches to
> dealing with it without the appearance of bias or favoritism, and has been
> repeatedly asked whether it would be a candidate for such additional
> meetings.
>
> The comment we have gotten from the working group is that work will expand
> to fill the available capacity; they would prefer to restrict proposed work
> rather than increase meeting count. That said, if a meeting occurs on 29
> September, we have tentative agreement from some of our members to attend,
> and I am currently planning other events around RIPE-65 on the assumption
> we will go there.
>
> The sunset4 WG, assuming it comes into being, is ostensibly targeted at
> offloading work that comes to v6ops. However, as currently chartered, it
> requires a recharter from the IESG to do anything beyond occupy schedule
> space - or so its chairs tell me. Hence, I can't actually send proposed
> work to it. It's another meeting to spend time in, but it's not clear that
> it adds value.
>
>
>

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

I personally have a concern with IETF sponsoring these large interim meetin=
gs. The past model has been that these are sponsored by the individuals&#39=
; companies/sponsors as these are typically the folks that have a vested in=
terest in getting the work done in a timely manner. =A0I don&#39;t recall a=
ny community discussion of this proposal. =A0I would think IETF funds would=
 be better allocated to the main IETF meetings when there is not a sponsor =
and the entire community benefits. =A0=A0<div>
<br></div><div>In the RAI area, we have arranged an interim meeting that st=
arts in a weeks time that is intended to optimize the participation for fol=
ks involved in two WGs and to encourage cross pollination as there will be =
a fair amount of overlap in the solution space. =A0There will also be a rel=
ated W3C meeting in this block of meetings. =A0It was a challenge to organi=
ze this to optimize participation for all the groups, as we ended up with a=
 weekend between the two meetings. =A0However, we do have a sponsor and whi=
le the location isn&#39;t optimal (it&#39;s not in the city center) and get=
ting hotel rooms was a challenge as the meeting happened to be scheduled st=
arting the day after a major holiday Sweden, everyone seemed to manage thei=
r arrangements without needing support from the secretariat,etc. =A0I think=
 the burden was rightfully placed on the individuals as well as their corpo=
rations/sponsors. =A0</div>
<div><br></div><div>Personally, I wonder if adding that burden to the secre=
tariat would be a good thing. =A0As a WG chair, it is somewhat of a challen=
ge to manage prep for the upcoming IETF meetings (with deadlines looming fo=
r the WGs) while prepping for an interim meeting. =A0Recently, the secretar=
iat has setup the materials manager for the proceedings. which is a nice co=
nvenience, but I don&#39;t see it a necessity to get them involved in plann=
ing interim meetings. =A0</div>
<div><br></div><div>Although, reading this, it seems the suggestion is to e=
volve to this smaller cluster of meetings model - i.e., the &quot;augment/r=
eplace&quot; suggestion. =A0 I don&#39;t think that&#39;s a good thing. =A0=
In some rare cases where there isn&#39;t a RAI meeting that is of interest =
to me, I find it informative to attend other WG sessions - e.g., APP area o=
r OPS area meetings. =A0Also, RAI for example, has overlap with a lot of ar=
eas. =A0So, we would lose some of the expertise that can be helpful in gett=
ing our work progressed. =A0For example, sitting down with a SEC AD to work=
 through their list of discusses. =A0Unless, of course the leadership must =
attend all these meeting clusters. However, that would add to their burden =
and there is always discussion as to how to reduce the overall burden. =A0<=
/div>
<div><br></div><div>I personally think we would be heading down a very slip=
pery slope if IETF starts sponsoring the interim meetings and evolves to a =
clustering model for meetings. =A0</div><div><br></div><div>Mary. =A0 =A0</=
div>
<div><div><br><div class=3D"gmail_quote">On Thu, May 31, 2012 at 4:23 PM, F=
red Baker <span dir=3D"ltr">&lt;<a href=3D"mailto:fred@cisco.com" target=3D=
"_blank">fred@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">
<br>
On May 31, 2012, at 12:43 PM, Ray Pelletier wrote:<br>
&gt; On May 31, 2012, at 1:36 PM, Murphy, Sandra wrote:<br>
&gt;&gt; SIDR is considering an interim meeting scheduled for pre/post RIPE=
 in September, on the grounds that multiple wgs were considering interim me=
etings around the RIPE meeting.<br>
&gt;&gt;<br>
&gt;&gt; The RIPE community is important to the SIDR work, so that made sen=
se.<br>
&gt;&gt;<br>
&gt;&gt; I see email traffic in the last few weeks on v6ops to consider a R=
IPE tethered interim.<br>
&gt;&gt;<br>
&gt;&gt; Are there other wgs are considering interim meetings around RIPE?<=
br>
&gt;&gt;<br>
&gt;&gt; Does anyone have a view as to whether the IETF would be willing to=
 support such a gathering of interims? =A0(I.e., do the wgs who want to do =
this need to find their own logistics? =A0Individually or together?)<br>
&gt;<br>
&gt; Yes, the IETF is going to support a Large Interim Meeting in Amsterdam=
. =A0The tentative dates are 29 and 30 September.<br>
&gt; We are hoping to use the same facility. =A0You will soon get guidance =
regarding the process of making known your interest in participating at the=
 LIM.<br>
&gt;<br>
&gt; Ray<br>
<br>
Well, yes. Russ has been interested in clustering interims; I *think* he is=
 considering moving in the direction of replacing/augmenting the current sc=
hedule with smaller meetings of busy working groups. v6ops has been under a=
 ddos of high rate low value drafts, has tried several approaches to dealin=
g with it without the appearance of bias or favoritism, and has been repeat=
edly asked whether it would be a candidate for such additional meetings.<br=
>

<br>
The comment we have gotten from the working group is that work will expand =
to fill the available capacity; they would prefer to restrict proposed work=
 rather than increase meeting count. That said, if a meeting occurs on 29 S=
eptember, we have tentative agreement from some of our members to attend, a=
nd I am currently planning other events around RIPE-65 on the assumption we=
 will go there.<br>

<br>
The sunset4 WG, assuming it comes into being, is ostensibly targeted at off=
loading work that comes to v6ops. However, as currently chartered, it requi=
res a recharter from the IESG to do anything beyond occupy schedule space -=
 or so its chairs tell me. Hence, I can&#39;t actually send proposed work t=
o it. It&#39;s another meeting to spend time in, but it&#39;s not clear tha=
t it adds value.<br>

<br>
<br>
</blockquote></div><br></div></div>

--14dae9ccd488c7fc2104c15c1353--

From john-ietf@jck.com  Thu May 31 18:01:04 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 705AC11E80C9 for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 18:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dBlysEwkONc5 for <wgchairs@ietfa.amsl.com>; Thu, 31 May 2012 18:01:04 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DB4DD11E80C6 for <wgchairs@ietf.org>; Thu, 31 May 2012 18:01:03 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SaG8m-000IpC-Sz; Thu, 31 May 2012 20:54:56 -0400
Date: Thu, 31 May 2012 21:00:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ray Pelletier <rpelletier@isoc.org>, "Murphy, Sandra" <Sandra.Murphy@sparta.com>
Subject: Re: pre-RIPE multiple IETF wg interim meetings
Message-ID: <27BA2CFB0B03B2EBA90AE4ED@PST.JCK.COM>
In-Reply-To: <1FB768C9-5B80-42AF-836E-42C080E16119@isoc.org>
References: <24B20D14B2CD29478C8D5D6E9CBB29F625F12F3C@Hermes.columbia.ads.sparta.com> <1FB768C9-5B80-42AF-836E-42C080E16119@isoc.org>
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: Chairs Working Group <wgchairs@ietf.org>, Housley Russ <housley@vigilsec.com>, Nugent Laura <lnugent@amsl.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 01 Jun 2012 01:01:04 -0000

--On Thursday, May 31, 2012 15:43 -0400 Ray Pelletier
<rpelletier@isoc.org> wrote:

>> Does anyone have a view as to whether the IETF would be
>> willing to support such a gathering of interims?  (I.e., do
>> the wgs who want to do this need to find their own logistics?
>> Individually or together?)
> 
> Yes, the IETF is going to support a Large Interim Meeting in
> Amsterdam.  The tentative dates are 29 and 30 September. We
> are hoping to use the same facility.  You will soon get
> guidance regarding the process of making known your interest
> in participating at the LIM.

And, without taking a position as to whether it is a good idea
or not, here we go down the slippery slope toward either four
full IETF meetings a year or perhaps toward one or two full IETF
meetings and a few Interim Meeting clusters.

   john

