
From ietf-secretariat@ietf.org  Mon Jan  7 12:58:50 2013
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 7B36121F86D4; Mon,  7 Jan 2013 12:58:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RKJ52z2VSHtg; Mon,  7 Jan 2013 12:58:49 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EFB421F868D; Mon,  7 Jan 2013 12:58:49 -0800 (PST)
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 86 - Meeting Information
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130107205849.5823.95171.idtracker@ietfa.amsl.com>
Date: Mon, 07 Jan 2013 12:58:49 -0800
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: Mon, 07 Jan 2013 20:58:50 -0000

86th IETF Meeting
Orlando, FL, USA
March 10-15, 2013
Host: Comcast and NBCUniversal

Meeting venue:  Caribe Royale http://www.cariberoyale.com

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

1.  Registration
2.  Social Event
3.  Visas & Letters of Invitation
4.  Accommodations
5.  Companion Program
6.  IETF and IEEE back-to-back Meetings

1. Registration
    A. Early-Bird Registration - USD 650.00 Pay by Friday, 1 March 2013 UTC=
 24:00
    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,
                4 March 2013 at UTC 24:00.
                Cancellations are subject to a 10% (ten percent)
                cancellation fee if requested by that date and time.
    F. Online Registration and Payment ends Friday, 8 March 2013, 1700 loca=
l Orlando time.
    G. On-site Registration starting Sunday, 10 March 2013 at 1100 local Or=
lando time.

2. Social Event
    IETF86's social event sponsored by Comcast and NBCUniversal will be at =
Universal Studios Orlando's Wizarding World of Harry Potter on Tuesday even=
ing. =

    The Wizarding World of Harry Potter will be open exclusively for the IE=
TF86 social. Attendees will be transported from the Caribe Royal to Univers=
al Studios where they will enjoy the many attractions of Harry Potter inclu=
ding the thrilling Harry Potter and the Forbidden Journey ride.   =

    Guest will enjoy a buffet dinner, soft drinks, wine, beer and Harry Pot=
ter's own Butterbeer served in Hogsmeade Village through out the evening.  =

    Return transportation will be provided to the Caribe Royale throughout =
the evening.
    The cost for the event is $30 per person and due to the expected high d=
emand, registration is limited to two tickets an attendee.

3. Visas & Letters of Invitation:
    Information on Visiting the United States, please visit:
http://travel.state.gov/visa/

    After you complete the registration process, you can request an electro=
nic IETF letter of invitation as well. The registration system also allows =
for you to request a hard copy IETF letter of invitation. You may also requ=
est one at a later time by following the link provided in the confirmation =
email.

    Please note that the IETF Letter of Invitation may not be sufficient fo=
r obtaining a visa to enter the United States.

4.  Accommodations
    The IETF is holding a block of guest rooms at the Caribe Royale, the me=
eting venue.
    Room Rates include in room high-speed Internet access. Sales/room tax (=
applicable taxes are subject to change) are excluded in the above prices, c=
urrently 12.5%. Room rates DO NOT include daily breakfast.

    Reservations Cut off Date: 13 February 2013 =


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

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

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

   You can register your companion at any time via the IETF website or onsi=
te at the meeting.

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

6.  IETF and IEEE back-to-back Meetings
   The IEEE 802 Executive Committee and the IETF, IESG and IAOC are pleased=
 to confirm the March 2013 IEEE 802 Plenary Session and IETF86 will both ta=
ke place at the Caribe Royale Resort & Convention Center in Orlando, Florid=
a, USA during the month of March 2013. IETF86 will take place March 10-15, =
2013 and the IEEE 802 Plenary Session will occur March 17-22, 2013.
   Registration for the March 2013 IEEE 802 Plenary Session and IETF86 are =
now available and the Caribe Royale has extended great rates for session at=
tendees over the dates of both sessions. We encourage IEEE 802 and IETF par=
ticipants to consider registering for both events in order to take advantag=
e of this fine opportunity to learn more about each group.
    For Registration, Hotel Reservations and more information about the spe=
cific events please visit the event websites for the March 2013 IEEE 802 Pl=
enary Session, https://802world.org/apps/session/79/register1/register and =
the IETF86, http://www.ietf.org/meetings/86/.

Only 61 days until the Orlando IETF!

From yaronf.ietf@gmail.com  Wed Jan  9 11:23:07 2013
Return-Path: <yaronf.ietf@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 B270E21F860A for <wgchairs@ietfa.amsl.com>; Wed,  9 Jan 2013 11:23:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ChoyekFKZJOv for <wgchairs@ietfa.amsl.com>; Wed,  9 Jan 2013 11:23:06 -0800 (PST)
Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by ietfa.amsl.com (Postfix) with ESMTP id C6CAE21F870A for <wgchairs@ietf.org>; Wed,  9 Jan 2013 11:23:04 -0800 (PST)
Received: by mail-bk0-f54.google.com with SMTP id je9so1150243bkc.13 for <wgchairs@ietf.org>; Wed, 09 Jan 2013 11:23:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=o91UfNf0SYkQKFZZAnhFXx2RcisuSO0sySldOagTi84=; b=bOYHCdykwxHXF329tKpaJGhg91gzOXlTEbfUswNmzpzr2+VbUj+RP5aCOQ6VvshxKY zix/wi+P3K7RuA0/lOcd+1ha5on1PofSe8t7MFbzxEzVLJ388DpyaTvqacLSo54LnxVH L6h2mElR6gUklwyRnHDHuAL4/LG6VXYpannEJ6cFIw2VKxARrB3YtUrvy8LaGLajXOk+ cMTPmEj591qVDtjx/PkG+BDxFBw74e5Z8O1k1l1+i7cTNMB+6oUr5NaUnZk4qWgFxoz9 KIvCPFwUM+/tStKTcO29KnPRKYMA7whcfJnUV/Vysw7ydkSXPnlF1zTIFTtsIulwsSTT i0aA==
X-Received: by 10.204.143.147 with SMTP id v19mr33353884bku.32.1357759383688;  Wed, 09 Jan 2013 11:23:03 -0800 (PST)
Received: from [10.0.0.5] ([109.66.16.66]) by mx.google.com with ESMTPS id o9sm49878838bko.15.2013.01.09.11.22.57 (version=SSLv3 cipher=OTHER); Wed, 09 Jan 2013 11:23:00 -0800 (PST)
Message-ID: <50EDC390.3070907@gmail.com>
Date: Wed, 09 Jan 2013 21:22:56 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: WG Chairs <wgchairs@ietf.org>
Subject: "Running code" draft
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Wed, 09 Jan 2013 19:23:08 -0000

Hi,

Adrian and I published a draft [1] before the holidays that suggests to 
include an Implementation Status section in I-Ds, where any extant (even 
partial) implementations of the specification are described. The goal is 
to increase working group members' confidence in the maturity level of 
the spec, to motivate people to implement drafts before publication, and 
several other lesser benefits.

We would like to encourage people on this list to include Implementation 
Status sections in working group drafts (this is no process change: 
anybody can include ANY additional sections in drafts). We would 
appreciate comments on this proposal from this list, and would be even 
happier to hear reports of your experience implementing this idea in 
your WG.

Thanks,
     Yaron

[1] http://tools.ietf.org/html/draft-sheffer-running-code-01

From agenda@ietf.org  Wed Jan  9 12:05:25 2013
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 DE77B21F88D1; Wed,  9 Jan 2013 12:05:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h98UlI1M+Fje; Wed,  9 Jan 2013 12:05:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66D8A11E8099; Wed,  9 Jan 2013 12:05:25 -0800 (PST)
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: IETF 86 - Working Group Chairs' Lunch Tutorial
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130109200525.17739.51318.idtracker@ietfa.amsl.com>
Date: Wed, 09 Jan 2013 12:05:25 -0800
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: Wed, 09 Jan 2013 20:05:26 -0000

Hi All,

As usual, we will be holding a WG Chairs training lunch at IETF 86 in Orlan=
do.  All current WG chairs, BOF chairs, IRTF chairs, and IESG members are w=
elcome to attend. The lunch meeting will take place on Wednesday, March 13,=
 2013 at 11:30am, location TBD, and a complementary lunch will be provided.

For this session, Pete Resnick and Stephen Farrell will talk about RFC 2119=
: MUST, SHOULD, MUST NOT. There will also be time for questions and answers.

If you would like to attend this session, please RSVP to agenda@ietf.org AS=
AP and the cutoff will be February 22, 2013. The location will be sent to t=
hose who RSVP.


Thanks,
Wanda
(on behalf of Mirjam Kuehne, Radia Perlman, & Edu Team)

From agenda@ietf.org  Wed Jan  9 12:10:21 2013
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 C8D7921F8858; Wed,  9 Jan 2013 12:10:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BBxQfbJAjBml; Wed,  9 Jan 2013 12:10:20 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5DAF21F884A; Wed,  9 Jan 2013 12:10:20 -0800 (PST)
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: 86th IETF - Working Group/BOF/IRTF Scheduling - REMINDER
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130109201020.26789.70949.idtracker@ietfa.amsl.com>
Date: Wed, 09 Jan 2013 12:10:20 -0800
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: Wed, 09 Jan 2013 20:10:22 -0000

-----------------------------------------------------------------
86th IETF =E2=80=93 Orlando, FL, USA
Meeting Dates: March 10-15, 2013
Host: Comcast and NBC Universal
-----------------------------------------------------------------
IETF meetings start Monday morning and run through Friday afternoon (13:30).

The milestones and deadlines for scheduling-related activities are as follo=
ws:

NOTE: cutoff dates are subject to change.

- 2013-01-14 (Monday): Cutoff date for requests to schedule Working Group m=
eetings at UTC 24:00. To request a Working Group session, use the IETF Meet=
ing Session Request Tool.
- 2013-01-28 (Monday): Cutoff date for BOF proposal requests to Area Direct=
ors at UTC 24:00. To request a BOF, please see instructions on Requesting a=
 BOF.
- 2013-01-31 (Thursday): Cutoff date for Area Directors to approve BOFs at =
UTC 24:00.
- 2013-02-07 (Thursday): Preliminary agenda published for comment.
- 2013-02-11 (Monday): Cutoff date for requests to reschedule Working Group=
 and BOF meetings UTC 24:00.
- 2013-02-15 (Friday): Final agenda to be published.
- 2013-02-27 (Wednesday): Draft Working Group agendas due by UTC 24:00, upl=
oad using IETF Meeting Materials Management Tool.
- 2013-03-04 (Monday): Revised Working Group agendas due by UTC 24:00, uplo=
ad using IETF Meeting Materials Management Tool.
- 2013-04-12 (Friday): Proceedings submission cutoff date by UTC 24:00, upl=
oad using IETF Meeting Materials Management Tool.
- 2013-05-01 (Wednesday): Proceedings submission corrections cutoff date by=
 UTC 24:00, 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, February 27, 2013 at UTC 24:00.  Revised Worki=
ng Group agendas are due no later than Monday, March 4, 2013 at UTC 24:00. =
 The proposed agenda for a BOF session should be submitted along with your =
request for a session.  Please be sure to copy your Area Director on that m=
essage.

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

https://datatracker.ietf.org/meeting/86/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 86 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, February 11, 2013, the cut-off date for requests to r=
eschedule 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
85th IETF Meeting Attendance Number

6man - 153
6renum - 30
abfab	47
alto  - 59
apparea (AG) - 122
atoca - 20
avtcore (2nd session) - 60
avtext - 40
bmwg - 34
ccamp (2nd session) - 52
cdni - 54
cdni (2nd session) - 51
certrans - 99
clue - 55
clue (2nd session) - 53
core - 64
core (2nd session) - 50
dhc - 62
dime - 23
dispatch - 53
dtnrg (RG) - 39
ecrit - 36
eman - 44
emu - 25
forces - 44
geopriv - 41
httpauth - 103
httpbis - 85
iccrg (RG) - 81
idr - 62
intarea (AG) - 105
ippm - 56
iri - 26
irs - 291
IRTF Open Meeting - 82
isis - 34
karp - 46
l3vpn - 63
mdnsext - 164
mif - 68
mile - 39
mpls (2nd session) - 79
mptcp - 63
multimob - 21
netext - 46
netmod	 - 41
nvo3 (BoF) - 198
oauth - 65
opsawg - 66
opsec - 45
pce - 74
pcp - 27
pim - 24
pkix - 30
ppsp - 28
radext - 18
rmcat (BoF) - 64
rtcweb (2nd session) - 145
rtgarea (AG) - 72
rtgwg - 113
sacm - 63
sdnrg (RG) - 264
sidr - 65
siprec - 29
softwire - 89
softwire (2nd session) - 79
sunset4 - 142
tcpm - 32
tictoc - 23
tls - 80
trill - 38
tsvarea (AG) - 92
tsvwg - 38
tsvwg (2nd session) - 48
v6ops - 146
videocodec - 142
wpkops - 100

From ned.freed@mrochek.com  Wed Jan  9 13:52:49 2013
Return-Path: <ned.freed@mrochek.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 96DB521F8862 for <wgchairs@ietfa.amsl.com>; Wed,  9 Jan 2013 13:52:49 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bd+dScn3v73R for <wgchairs@ietfa.amsl.com>; Wed,  9 Jan 2013 13:52:49 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id C56DE21F86F8 for <wgchairs@ietf.org>; Wed,  9 Jan 2013 13:52:46 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOSE38D16O00471U@mauve.mrochek.com> for wgchairs@ietf.org; Wed, 9 Jan 2013 13:47:44 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOJ8U2Q2U800008S@mauve.mrochek.com>; Wed, 9 Jan 2013 13:47:41 -0800 (PST)
Message-id: <01OOSE36ELI200008S@mauve.mrochek.com>
Date: Wed, 09 Jan 2013 13:45:12 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
Subject: Re: "Running code" draft
In-reply-to: "Your message dated Wed, 09 Jan 2013 21:22:56 +0200" <50EDC390.3070907@gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <50EDC390.3070907@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Cc: WG Chairs <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: Wed, 09 Jan 2013 21:52:49 -0000

This seems like a reasonable proposal to me. The one (very minor)
point is that I would simply call for the section to be marked as
"remove before publication" rather than calling for the authors to do it
manually at some point. The RFC Editors handles such removals routinely
for things like "changes since" sections.

				Ned

> Adrian and I published a draft [1] before the holidays that suggests to
> include an Implementation Status section in I-Ds, where any extant (even
> partial) implementations of the specification are described. The goal is
> to increase working group members' confidence in the maturity level of
> the spec, to motivate people to implement drafts before publication, and
> several other lesser benefits.

> We would like to encourage people on this list to include Implementation
> Status sections in working group drafts (this is no process change:
> anybody can include ANY additional sections in drafts). We would
> appreciate comments on this proposal from this list, and would be even
> happier to hear reports of your experience implementing this idea in
> your WG.

> Thanks,
>      Yaron

> [1] http://tools.ietf.org/html/draft-sheffer-running-code-01

From adrian@olddog.co.uk  Thu Jan 10 04:08:24 2013
Return-Path: <adrian@olddog.co.uk>
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 BF2CE21F87E7 for <wgchairs@ietfa.amsl.com>; Thu, 10 Jan 2013 04:08:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A5kObZtsm4-n for <wgchairs@ietfa.amsl.com>; Thu, 10 Jan 2013 04:08:24 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id AEC8D21F87CB for <wgchairs@ietf.org>; Thu, 10 Jan 2013 04:08:23 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0AC8Kb5018489;  Thu, 10 Jan 2013 12:08:20 GMT
Received: from 950129200 (089144192226.atnat0001.highway.a1.net [89.144.192.226]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0AC8IrE018483 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 10 Jan 2013 12:08:19 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Ned Freed'" <ned.freed@mrochek.com>, "'Yaron Sheffer'" <yaronf.ietf@gmail.com>
References: <50EDC390.3070907@gmail.com> <01OOSE36ELI200008S@mauve.mrochek.com>
In-Reply-To: <01OOSE36ELI200008S@mauve.mrochek.com>
Subject: RE: "Running code" draft
Date: Thu, 10 Jan 2013 12:08:19 -0000
Message-ID: <028301cdef2b$2f0aedd0$8d20c970$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJLQLQ95p8YqZeE24TUr90mPFQ/YgIEsEYllzeu+BA=
Content-Language: en-gb
Cc: 'WG Chairs' <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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 Jan 2013 12:08:24 -0000

Good catch, Ned.

We can add that to the next revision.

Hoping to see some running code examples of implementation of this I-D soon :-)

Adrian

> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of Ned
> Freed
> Sent: 09 January 2013 21:45
> To: Yaron Sheffer
> Cc: WG Chairs
> Subject: Re: "Running code" draft
> 
> This seems like a reasonable proposal to me. The one (very minor)
> point is that I would simply call for the section to be marked as
> "remove before publication" rather than calling for the authors to do it
> manually at some point. The RFC Editors handles such removals routinely
> for things like "changes since" sections.
> 
> 				Ned
> 
> > Adrian and I published a draft [1] before the holidays that suggests to
> > include an Implementation Status section in I-Ds, where any extant (even
> > partial) implementations of the specification are described. The goal is
> > to increase working group members' confidence in the maturity level of
> > the spec, to motivate people to implement drafts before publication, and
> > several other lesser benefits.
> 
> > We would like to encourage people on this list to include Implementation
> > Status sections in working group drafts (this is no process change:
> > anybody can include ANY additional sections in drafts). We would
> > appreciate comments on this proposal from this list, and would be even
> > happier to hear reports of your experience implementing this idea in
> > your WG.
> 
> > Thanks,
> >      Yaron
> 
> > [1] http://tools.ietf.org/html/draft-sheffer-running-code-01


From ietf-secretariat@ietf.org  Wed Jan 16 06:51:26 2013
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 3B43121F8923; Wed, 16 Jan 2013 06:51:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBnwPdRsUpdX; Wed, 16 Jan 2013 06:51:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6924421F86FD; Wed, 16 Jan 2013 06:51:25 -0800 (PST)
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 86 - Meeting Information
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130116145125.29768.56592.idtracker@ietfa.amsl.com>
Date: Wed, 16 Jan 2013 06:51:25 -0800
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: Wed, 16 Jan 2013 14:51:26 -0000

86th IETF Meeting
Orlando, FL, USA
March 10-15, 2013
Host: Comcast and NBCUniversal

Meeting venue:  Caribe Royale http://www.cariberoyale.com

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

1.  Registration
2.  Social Event
3.  Visas & Letters of Invitation
4.  Accommodations
5.  Companion Program
6.  IETF and IEEE back-to-back Meetings

1. Registration
   A. Early-Bird Registration - USD 650.00 Pay by Friday, 1 March 2013 UTC =
24:00
   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,
               4 March 2013 at UTC 24:00.
               Cancellations are subject to a 10% (ten percent)
               cancellation fee if requested by that date and time.
   F. Online Registration and Payment ends Friday, 8 March 2013, 1700 local=
 Orlando time.
   G. On-site Registration starting Sunday, 10 March 2013 at 1100 local Orl=
ando time.

2. Social Event
   IETF86's social event sponsored by Comcast and NBCUniversal will be at U=
niversal Studios Orlando's Wizarding World of Harry Potter on Tuesday eveni=
ng. =

   The Wizarding World of Harry Potter will be open exclusively for the IET=
F86 social. Attendees will be transported from the Caribe Royal to Universa=
l Studios where they will enjoy the many attractions of Harry Potter includ=
ing the thrilling Harry Potter and the Forbidden Journey ride.   =

   Guest will enjoy a buffet dinner, soft drinks, wine, beer and Harry Pott=
er's own Butterbeer served in Hogsmeade Village through out the evening.  =

   Return transportation will be provided to the Caribe Royale throughout t=
he evening.
   The cost for the event is $30 per person and due to the expected high de=
mand, registration is limited to two tickets an attendee.

3. Visas & Letters of Invitation:
   Information on Visiting the United States, please visit:
http://travel.state.gov/visa/

   After you complete the registration process, you can request an electron=
ic IETF letter of invitation as well. The registration system also allows f=
or you to request a hard copy IETF letter of invitation. You may also reque=
st one at a later time by following the link provided in the confirmation e=
mail.

   Please note that the IETF Letter of Invitation may not be sufficient for=
 obtaining a visa to enter the United States.

4.  Accommodations
   The IETF is holding a block of guest rooms at the Caribe Royale, the mee=
ting venue.
   Room Rates include in room high-speed Internet access. Sales/room tax (a=
pplicable taxes are subject to change) are excluded in the above prices, cu=
rrently 12.5%. Room rates DO NOT include daily breakfast.

   Reservations Cut off Date: 13 February 2013 =


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

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

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

  You can register your companion at any time via the IETF website or onsit=
e at the meeting.

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

6.  IETF and IEEE back-to-back Meetings
  The IEEE 802 Executive Committee and the IETF, IESG and IAOC are pleased =
to confirm the March 2013 IEEE 802 Plenary Session and IETF86 will both tak=
e place at the Caribe Royale Resort & Convention Center in Orlando, Florida=
, USA during the month of March 2013. IETF86 will take place March 10-15, 2=
013 and the IEEE 802 Plenary Session will occur March 17-22, 2013.
  Registration for the March 2013 IEEE 802 Plenary Session and IETF86 are n=
ow available and the Caribe Royale has extended great rates for session att=
endees over the dates of both sessions. We encourage IEEE 802 and IETF part=
icipants to consider registering for both events in order to take advantage=
 of this fine opportunity to learn more about each group.
   For Registration, Hotel Reservations and more information about the spec=
ific events please visit the event websites for the March 2013 IEEE 802 Ple=
nary Session, https://802world.org/apps/session/79/register1/register and t=
he IETF86, http://www.ietf.org/meetings/86/.

Only 52 days until the Orlando IETF!

From dcrocker@bbiw.net  Wed Jan 16 13:21:53 2013
Return-Path: <dcrocker@bbiw.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 2903F21F8758 for <wgchairs@ietfa.amsl.com>; Wed, 16 Jan 2013 13:21:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OW6LdqiZi72l for <wgchairs@ietfa.amsl.com>; Wed, 16 Jan 2013 13:21:52 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0D21D21F87F9 for <wgchairs@ietf.org>; Wed, 16 Jan 2013 13:21:50 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r0GLLmsw002416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 16 Jan 2013 13:21:49 -0800
Message-ID: <50F719EB.90903@bbiw.net>
Date: Wed, 16 Jan 2013 13:21:47 -0800
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: "Running code" draft
References: <50EDC390.3070907@gmail.com> <01OOSE36ELI200008S@mauve.mrochek.com>
In-Reply-To: <01OOSE36ELI200008S@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 16 Jan 2013 13:21:49 -0800 (PST)
Cc: WG Chairs <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: Wed, 16 Jan 2013 21:21:53 -0000

On 1/9/2013 1:45 PM, Ned Freed wrote:
> This seems like a reasonable proposal to me.

+1

 >  The one (very minor)
> point is that I would simply call for the section to be marked as
> "remove before publication" rather than calling for the authors to do it
> manually at some point.

+1


Tidbits:

1.   While I understand the Procrustean need to label this a "process 
experiment" it doesn't really involve process as much as a standardized 
form and a standardized section in Drafts.  I think the document would 
be a tad clearer to have the primary descriptive text characterize this 
as standardizing a reporting section.


2.   The title also would be better if it did not promise such a 
grandiose effect as improving consensus.  Keep things modest and direct, 
such as:

      Improving Awareness of Running Code


3.   Rather than specifying that a wiki "replaces" the I-D section, I 
suggest having the reference to the wiki be the content of the section.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From adrian@olddog.co.uk  Thu Jan 17 10:29:03 2013
Return-Path: <adrian@olddog.co.uk>
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 9022D21F8684 for <wgchairs@ietfa.amsl.com>; Thu, 17 Jan 2013 10:29:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zGOl6HHWbwOy for <wgchairs@ietfa.amsl.com>; Thu, 17 Jan 2013 10:29:03 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id BE2FA21F8803 for <wgchairs@ietf.org>; Thu, 17 Jan 2013 10:29:02 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0HISs8Q018973;  Thu, 17 Jan 2013 18:28:54 GMT
Received: from 950129200 (089144192239.atnat0001.highway.a1.net [89.144.192.239]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0HISiLB018878 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 17 Jan 2013 18:28:51 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Dave Crocker'" <dcrocker@bbiw.net>, "'Ned Freed'" <ned.freed@mrochek.com>
References: <50EDC390.3070907@gmail.com> <01OOSE36ELI200008S@mauve.mrochek.com> <50F719EB.90903@bbiw.net>
In-Reply-To: <50F719EB.90903@bbiw.net>
Subject: RE: "Running code" draft
Date: Thu, 17 Jan 2013 18:28:44 -0000
Message-ID: <019101cdf4e0$81562310$84026930$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJLQLQ95p8YqZeE24TUr90mPFQ/YgIEsEYlAbmwYeaXNUn/oA==
Content-Language: en-gb
Cc: 'WG Chairs' <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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 Jan 2013 18:29:03 -0000

Hi Dave,

Thanks for reading.

> > This seems like a reasonable proposal to me.
> 
> +1

Excellent! Hoping to see some chairs encouraging their editors/authors to give
it a try.

>  >  The one (very minor)
> > point is that I would simply call for the section to be marked as
> > "remove before publication" rather than calling for the authors to do it
> > manually at some point.
> 
> +1

Yup. Yaron and I will fold that in.

> Tidbits:
> 
> 1.   While I understand the Procrustean need to label this a "process
> experiment" it doesn't really involve process as much as a standardized
> form and a standardized section in Drafts.  I think the document would
> be a tad clearer to have the primary descriptive text characterize this
> as standardizing a reporting section.

Ah, legacy text from last year when we thought it might have to be run as a 3933
process experiment.

We will polish this rough edge.

Thanks for suggesting I may have Procrustean leanings. Could I have this as a
framed certificate?

> 2.   The title also would be better if it did not promise such a
> grandiose effect as improving consensus.  Keep things modest and direct,
> such as:
> 
>       Improving Awareness of Running Code

Point taken.

> 3.   Rather than specifying that a wiki "replaces" the I-D section, I
> suggest having the reference to the wiki be the content of the section.

Indeed. The substantive content of the section will move to the wiki, but yes,
the section will still remain and will point to the wiki.

Cheers,
Adrian


From dcrocker@bbiw.net  Thu Jan 17 10:38:36 2013
Return-Path: <dcrocker@bbiw.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 ADC5621F8840 for <wgchairs@ietfa.amsl.com>; Thu, 17 Jan 2013 10:38:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v+hARJVg+ESk for <wgchairs@ietfa.amsl.com>; Thu, 17 Jan 2013 10:38:32 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 887A321F8569 for <wgchairs@ietf.org>; Thu, 17 Jan 2013 10:38:32 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r0HIcVYw032410 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 17 Jan 2013 10:38:32 -0800
Message-ID: <50F84525.6050909@bbiw.net>
Date: Thu, 17 Jan 2013 10:38:29 -0800
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: "Running code" draft
References: <50EDC390.3070907@gmail.com> <01OOSE36ELI200008S@mauve.mrochek.com> <50F719EB.90903@bbiw.net> <019101cdf4e0$81562310$84026930$@olddog.co.uk>
In-Reply-To: <019101cdf4e0$81562310$84026930$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 17 Jan 2013 10:38:32 -0800 (PST)
Cc: 'WG Chairs' <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, 17 Jan 2013 18:38:36 -0000

On 1/17/2013 10:28 AM, Adrian Farrel wrote:
>> 1.   While I understand the Procrustean need to label this a "process
>> experiment" it doesn't really involve process as much as a standardized
>> form and a standardized section in Drafts.
...
> Thanks for suggesting I may have Procrustean leanings. Could I have this as a
> framed certificate?

As enticing as an actual ad hominem reference always is, even in the 
midst of my making such a nit-picking document criticism, I didn't mean 
'you' as much as 'us'.  The issue I see is IETF-level and not 
author-level...

So there!


>> 3.   Rather than specifying that a wiki "replaces" the I-D section, I
>> suggest having the reference to the wiki be the content of the section.
>
> Indeed. The substantive content of the section will move to the wiki, but yes,
> the section will still remain and will point to the wiki.

Makes sense, but I read the current language as implying otherwise.  Not 
a big deal.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From loa@pi.nu  Thu Jan 17 10:50:28 2013
Return-Path: <loa@pi.nu>
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 BB0C221F8865 for <wgchairs@ietfa.amsl.com>; Thu, 17 Jan 2013 10:50:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.744
X-Spam-Level: 
X-Spam-Status: No, score=-97.744 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, MIME_QP_LONG_LINE=1.396,  RCVD_ILLEGAL_IP=1.908, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aHe9lMoCqJyT for <wgchairs@ietfa.amsl.com>; Thu, 17 Jan 2013 10:50:27 -0800 (PST)
Received: from mail.pi.nu (unknown [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id 2789E21F8860 for <wgchairs@ietf.org>; Thu, 17 Jan 2013 10:50:27 -0800 (PST)
Received: from [2.69.44.34] (2.69.44.34.mobile.tre.se [2.69.44.34]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id 7F489823B5; Thu, 17 Jan 2013 19:50:23 +0100 (CET)
References: <50EDC390.3070907@gmail.com> <01OOSE36ELI200008S@mauve.mrochek.com> <50F719EB.90903@bbiw.net> <019101cdf4e0$81562310$84026930$@olddog.co.uk>
In-Reply-To: <019101cdf4e0$81562310$84026930$@olddog.co.uk>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <CF59A115-C87D-4D65-AB7D-B45B41F237CD@pi.nu>
X-Mailer: iPhone Mail (10A551)
From: "Loa@pi.nu" <loa@pi.nu>
Subject: Re: "Running code" draft
Date: Thu, 17 Jan 2013 19:50:22 +0100
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Cc: WG Chairs <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, 17 Jan 2013 18:50:28 -0000

Folks,

On this draft there is also a case informational case that is not covered. W=
hen we've had two competing solutions and one have been chosen to be publish=
ed as standards track, IETF has traditionally been willing to publish the ot=
her as Informational given that there is running code  available.=20

Might be worth mentioning.=20

/Loa

Skickat fr=C3=A5n min iPhone

17 jan 2013 kl. 19:28 skrev "Adrian Farrel" <adrian@olddog.co.uk>:

> Hi Dave,
>=20
> Thanks for reading.
>=20
>>> This seems like a reasonable proposal to me.
>>=20
>> +1
>=20
> Excellent! Hoping to see some chairs encouraging their editors/authors to g=
ive
> it a try.
>=20
>>> The one (very minor)
>>> point is that I would simply call for the section to be marked as
>>> "remove before publication" rather than calling for the authors to do it=

>>> manually at some point.
>>=20
>> +1
>=20
> Yup. Yaron and I will fold that in.
>=20
>> Tidbits:
>>=20
>> 1.   While I understand the Procrustean need to label this a "process
>> experiment" it doesn't really involve process as much as a standardized
>> form and a standardized section in Drafts.  I think the document would
>> be a tad clearer to have the primary descriptive text characterize this
>> as standardizing a reporting section.
>=20
> Ah, legacy text from last year when we thought it might have to be run as a=
 3933
> process experiment.
>=20
> We will polish this rough edge.
>=20
> Thanks for suggesting I may have Procrustean leanings. Could I have this a=
s a
> framed certificate?
>=20
>> 2.   The title also would be better if it did not promise such a
>> grandiose effect as improving consensus.  Keep things modest and direct,
>> such as:
>>=20
>>      Improving Awareness of Running Code
>=20
> Point taken.
>=20
>> 3.   Rather than specifying that a wiki "replaces" the I-D section, I
>> suggest having the reference to the wiki be the content of the section.
>=20
> Indeed. The substantive content of the section will move to the wiki, but y=
es,
> the section will still remain and will point to the wiki.
>=20
> Cheers,
> Adrian
>=20

From yaronf.ietf@gmail.com  Thu Jan 17 11:58:17 2013
Return-Path: <yaronf.ietf@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 F11AD21F88BC for <wgchairs@ietfa.amsl.com>; Thu, 17 Jan 2013 11:58:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c-zHZC8J2LVd for <wgchairs@ietfa.amsl.com>; Thu, 17 Jan 2013 11:58:17 -0800 (PST)
Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) by ietfa.amsl.com (Postfix) with ESMTP id E79ED21F88F7 for <wgchairs@ietf.org>; Thu, 17 Jan 2013 11:58:16 -0800 (PST)
Received: by mail-bk0-f53.google.com with SMTP id j5so1623853bkw.12 for <wgchairs@ietf.org>; Thu, 17 Jan 2013 11:58:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=m5y2C+QqfXTAFsl7vSZr3ac8qOV4l03/e8X3W+V1IrE=; b=VObJ/lJL4Ct7Athg9lwCN6o0+lpgvDCjf3aI5Atoe61R1J0xsvObUKCblQEkNv4dwV cBJUI2PydeR0jcZ1yNSvGdK+IzwSEpRb5jT7TNAjAuGCEp6VZCv2TtAOzm1OD2zJ0UfM bgycfdUswXTK/bC3Q4HZVr5bAfAhvD+dbMcg3NuhCOrgQZmBGtkLWg2s35Hn/eyUEA+q 0BEykVv7o+GxpnXb5Mj8ALMXRWpZ+fWn+4QGuKw6vuV9ZvjSoWztJqFHU7j9hZ0cY7nq THW/XWQjjxDpCGU5C20to//rt3bUXpcofcuVzjP+Wowe77yrKYjF2ugKq+ILgkeeepO5 WAyQ==
X-Received: by 10.204.153.15 with SMTP id i15mr1919925bkw.64.1358452695799; Thu, 17 Jan 2013 11:58:15 -0800 (PST)
Received: from [10.0.0.5] (bzq-79-176-124-5.red.bezeqint.net. [79.176.124.5]) by mx.google.com with ESMTPS id v8sm2377307bku.6.2013.01.17.11.58.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Jan 2013 11:58:14 -0800 (PST)
Message-ID: <50F857D3.3020006@gmail.com>
Date: Thu, 17 Jan 2013 21:58:11 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Loa@pi.nu" <loa@pi.nu>
Subject: Re: "Running code" draft
References: <50EDC390.3070907@gmail.com> <01OOSE36ELI200008S@mauve.mrochek.com> <50F719EB.90903@bbiw.net> <019101cdf4e0$81562310$84026930$@olddog.co.uk> <CF59A115-C87D-4D65-AB7D-B45B41F237CD@pi.nu>
In-Reply-To: <CF59A115-C87D-4D65-AB7D-B45B41F237CD@pi.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, WG Chairs <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, 17 Jan 2013 19:58:18 -0000

I agree. The Implementation Status section provides information that may 
help WG chairs and Area Directors in deciding on alternative publication 
venues, when the Standards Track option is not available.

Thanks,
	Yaron

On 01/17/2013 08:50 PM, Loa@pi.nu wrote:
> Folks,
>
> On this draft there is also a case informational case that is not covered. When we've had two competing solutions and one have been chosen to be published as standards track, IETF has traditionally been willing to publish the other as Informational given that there is running code  available.
>
> Might be worth mentioning.
>
> /Loa
>
> Skickat från min iPhone
>
> 17 jan 2013 kl. 19:28 skrev "Adrian Farrel" <adrian@olddog.co.uk>:
>
>> Hi Dave,
>>
>> Thanks for reading.
>>
>>>> This seems like a reasonable proposal to me.
>>>
>>> +1
>>
>> Excellent! Hoping to see some chairs encouraging their editors/authors to give
>> it a try.
>>
>>>> The one (very minor)
>>>> point is that I would simply call for the section to be marked as
>>>> "remove before publication" rather than calling for the authors to do it
>>>> manually at some point.
>>>
>>> +1
>>
>> Yup. Yaron and I will fold that in.
>>
>>> Tidbits:
>>>
>>> 1.   While I understand the Procrustean need to label this a "process
>>> experiment" it doesn't really involve process as much as a standardized
>>> form and a standardized section in Drafts.  I think the document would
>>> be a tad clearer to have the primary descriptive text characterize this
>>> as standardizing a reporting section.
>>
>> Ah, legacy text from last year when we thought it might have to be run as a 3933
>> process experiment.
>>
>> We will polish this rough edge.
>>
>> Thanks for suggesting I may have Procrustean leanings. Could I have this as a
>> framed certificate?
>>
>>> 2.   The title also would be better if it did not promise such a
>>> grandiose effect as improving consensus.  Keep things modest and direct,
>>> such as:
>>>
>>>       Improving Awareness of Running Code
>>
>> Point taken.
>>
>>> 3.   Rather than specifying that a wiki "replaces" the I-D section, I
>>> suggest having the reference to the wiki be the content of the section.
>>
>> Indeed. The substantive content of the section will move to the wiki, but yes,
>> the section will still remain and will point to the wiki.
>>
>> Cheers,
>> Adrian
>>

From iad@ietf.org  Fri Jan 18 11:46:09 2013
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 2A42C21F8759; Fri, 18 Jan 2013 11:46:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kSM7FR4yxaMV; Fri, 18 Jan 2013 11:46:08 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC7DE21F8536; Fri, 18 Jan 2013 11:46:08 -0800 (PST)
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: IETF Meeting Hotels for 2013
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130118194608.726.21941.idtracker@ietfa.amsl.com>
Date: Fri, 18 Jan 2013 11:46:08 -0800
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, 18 Jan 2013 19:46:09 -0000

The IAOC has approved giving advance notice of the IETF Meeting hotel venue=
s for 2013 as an experiment. =

Customarily such information has not been provided prior to registration op=
ening for that meeting, however =

the IAOC is persuaded that it may be advantageous to attendees and wants to=
 determine whether there are any =

unintended consequences.

IETF 88	March 10 - 15
Location: Orlando, FL
Venue:	Caribe Royale
		Registration now open:  <https://www.ietf.org/meeting/86/index.html>

IETF 87 	July 28 - August 2
Location: Berlin, Germany
Venue:  	InterContinental Berlin  =

		(Note: Reservations to open approximately 12 weeks before the meeting.)

IETF 88	November 3-8
Location: 	Vancouver, BC, Canada
Venue:  	Hyatt Regency Vancouver  =

		(Note: Reservations to open approximately 12 weeks before the meeting.)

Providing Venue information for 2013 is an experiment to determine impacts =
to participants, Secretariat, =

contracts, venue, and budget.  A decision will be made whether to continue =
to provide Venue information =

for 2014 after IETF 88.

Ray
IETF Administrative Director

From ietf-secretariat@ietf.org  Thu Jan 31 13:25:20 2013
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 0F8E821F87D3; Thu, 31 Jan 2013 13:25:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AnA8OVxGlVN9; Thu, 31 Jan 2013 13:25:19 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1521421F8722; Thu, 31 Jan 2013 13:25:19 -0800 (PST)
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 86 - Meeting Information
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130131212519.26348.91618.idtracker@ietfa.amsl.com>
Date: Thu, 31 Jan 2013 13:25:19 -0800
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 Jan 2013 21:25:20 -0000

86th IETF Meeting
Orlando, FL, USA
March 10-15, 2013
Host: Comcast and NBCUniversal

Meeting venue:  Caribe Royale http://www.cariberoyale.com

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

1.  Registration
2.  Social Event
3.  Visas & Letters of Invitation
4.  Accommodations
5.  Companion Program
6.  IETF and IEEE back-to-back Meetings

1. Registration
  A. Early-Bird Registration - USD 650.00 Pay by Friday, 1 March 2013 UTC 2=
4:00
  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,
              4 March 2013 at UTC 24:00.
              Cancellations are subject to a 10% (ten percent)
              cancellation fee if requested by that date and time.
  F. Online Registration and Payment ends Friday, 8 March 2013, 1700 local =
Orlando time.
  G. On-site Registration starting Sunday, 10 March 2013 at 1100 local Orla=
ndo time.

2. Social Event
  IETF86's social event sponsored by Comcast and NBCUniversal will be at Un=
iversal Studios Orlando's Wizarding World of Harry Potter on Tuesday evenin=
g. =

  The Wizarding World of Harry Potter will be open exclusively for the IETF=
86 social. Attendees will be transported from the Caribe Royal to Universal=
 Studios where they will enjoy the many attractions of Harry Potter includi=
ng the thrilling Harry Potter and the Forbidden Journey ride.   =

  Guest will enjoy a buffet dinner, soft drinks, wine, beer and Harry Potte=
r's own Butterbeer served in Hogsmeade Village through out the evening.  =

  Return transportation will be provided to the Caribe Royale throughout th=
e evening.
  The cost for the event is $30 per person and due to the expected high dem=
and, registration is limited to two tickets an attendee.

3. Visas & Letters of Invitation:
  Information on Visiting the United States, please visit:
http://travel.state.gov/visa/

  After you complete the registration process, you can request an electroni=
c IETF letter of invitation as well. The registration system also allows fo=
r you to request a hard copy IETF letter of invitation. You may also reques=
t one at a later time by following the link provided in the confirmation em=
ail.

  Please note that the IETF Letter of Invitation may not be sufficient for =
obtaining a visa to enter the United States.

4.  Accommodations
  The IETF is holding a block of guest rooms at the Caribe Royale, the meet=
ing venue.
  Room Rates include in room high-speed Internet access. Sales/room tax (ap=
plicable taxes are subject to change) are excluded in the above prices, cur=
rently 12.5%. Room rates DO NOT include daily breakfast.

  Reservations Cut off Date: 13 February 2013 =


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

5.  Companion Program
 If you are traveling with a friend or family member over 18 years of age y=
ou 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 Sunday, 10 =
March
 - Ability to attend the official Welcome Reception from 1700-1900 on Sunda=
y, 10 March
 - A distinctive meeting badge that grants access to the venue (not to be u=
sed to attend working sessions)
 - Participation in a separate companion email list if you choose to help c=
ommunicate 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 86 companions mailing list only see:
 https://www.ietf.org/mailman/listinfo/86companions

6.  IETF and IEEE back-to-back Meetings
 The IEEE 802 Executive Committee and the IETF, IESG and IAOC are pleased t=
o confirm the March 2013 IEEE 802 Plenary Session and IETF86 will both take=
 place at the Caribe Royale Resort & Convention Center in Orlando, Florida,=
 USA during the month of March 2013. IETF86 will take place March 10-15, 20=
13 and the IEEE 802 Plenary Session will occur March 17-22, 2013.
 Registration for the March 2013 IEEE 802 Plenary Session and IETF86 are no=
w available and the Caribe Royale has extended great rates for session atte=
ndees over the dates of both sessions. We encourage IEEE 802 and IETF parti=
cipants to consider registering for both events in order to take advantage =
of this fine opportunity to learn more about each group.
  For Registration, Hotel Reservations and more information about the speci=
fic events please visit the event websites for the March 2013 IEEE 802 Plen=
ary Session, https://802world.org/apps/session/79/register1/register and th=
e IETF86, http://www.ietf.org/meetings/86/.

Only 37 days until the Orlando IETF!
