Re: [conex] Fwd: 86th IETF - Working Group/BOF/IRTF Scheduling

[Bob Briscoe <[e-mail]>]

Marcelo,

Five things I'd like to hear by then (two are my own):

1/ Now that concept-uses is out as RFC6789, I 
will focus on abstract-mech. I will resolve to 
pick up the discussions that I've been missing. 
I'd like to have that off to the IESG before 
March. But if we get bogged down, we will need to sort this out in Orlando.

2&3/ I can't speak for the other immediate 
milestones (destopt, tcp-modifications), but they 
should be able to follow fairly quickly after abstract-mech.

4/ I admit I've been fairly much buried in 
internal BT fluff for some months. I should have 
time for some more practical work from now on.

I have been promised a Linux implementation of 
ConEx shortly, and I'm currently getting the 
go-ahead to deploy it into BT's data centre 
testbed to evaluate the design in 
draft-briscoe-conex-data-centre. Should be able to report on that by March.

5/ I'd like to hear a presentation from Zhu Lei & 
co-authors, who have an interesting draft: 
draft-zhang-tsvwg-tunnel-congestion-exposure-00. 
It doesn't need ConEx, instead it uses feedback 
across a tunnel to get congestion information to 
the ingress. A network operator can unilaterally 
deploy this neat idea to capture 80% (?) of the benefits of ConEx.

And the network can turn on ECN unilaterally so 
the tunnel egress can detect congestion easily 
without burying into transport headers to look 
for gaps in sequence numbers. Then for e2e 
traffic that isn't ECN-capable, the tunnel egress 
will naturally turn ECN marks into drops just by complying with [RFC6040].

I suggested (offlist) they should require that 
the tunnel doesn't do congestion feedback for 
ConEx-enabled packets. Then, as ConEx is 
deployed, the tunnel just fills in congestion 
feedback for non-ConEx traffic. So more ConEx 
makes it more efficient (and it adds the benefit 
of credit marking, which makes a big difference 
for lots of short flows). There's some open 
questions, but it's interesting. 
Conex-data-centre uses a tunnel in a similar way.



Bob

At 18:25 10/12/2012, marcelo bagnulo braun wrote:
>Hi,
>
>I wonder if we have to meet in orlando.
>Opinions?
>
>Regards, marcelo
>
>
>
>-------- Mensaje original --------
>Asunto:         86th IETF - Working Group/BOF/IRTF Scheduling
>Fecha:  Mon, 10 Dec 2012 10:11:21 -0800
>De:     IETF Agenda <[e-mail]>
>Para:   Working Group Chairs <[e-mail]>
>CC:     [e-mail]
>
>
>
>-----------------------------------------------------------------
>86th IETF ­ 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).
>
>We are accepting scheduling requests for all 
>Working Groups, BOFs, and IRTFs starting 
>today.  The milestones and deadlines for 
>scheduling-related activities are as follows:
>
>NOTE: cutoff dates are subject to change.
>
>- 2012-12-10 (Monday): Working Group and BOF 
>scheduling begins. To request a Working Group 
>session, use the IETF Meeting Session Request Tool.
>- 2013-01-14 (Monday): Cutoff date for requests 
>to schedule Working Group meetings at UTC 24:00. 
>To request a Working Group session, use the IETF Meeting Session Request Tool.
>- 2013-01-28 (Monday): Cutoff date for BOF 
>proposal requests to Area Directors 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, upload using IETF Meeting Materials Management Tool.
>- 2013-03-04 (Monday): Revised Working Group 
>agendas due by UTC 24:00, upload using IETF Meeting Materials Management Tool.
>- 2013-04-12 (Friday): Proceedings submission 
>cutoff date by UTC 24:00, upload 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 "IETF Meeting Session 
>Request Tool," a Web-based tool for submitting 
>all of the information that the Secretariat requires to schedule your sessions.
>
>The URL for the tool is:
>
>https://pub.ietf.org/sreq/
>
>Please send requests to schedule your BOF 
>sessions to [e-mail].  Please include the 
>acronym of your BOF in the subject line of the 
>message, and include all of the information 
>specified in item (4) of "Requesting Meeting 
>Sessions at IETF Meetings" in the body.  (This document is included below.)
>
>Submitting Session Agendas
>
>For the convenience of meeting attendees, we ask 
>that you submit the agendas for your Working 
>Group sessions as early as possible.  Draft 
>Working Group agendas are due Wednesday, 
>February 27, 2013 at UTC 24:00.  Revised Working 
>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 message.
>
>Please submit the agendas for your Working Group 
>sessions using the "IETF Meeting Materials 
>Management Tool," a Web-based tool for making 
>your meeting agenda, minutes, and presentation 
>slides available to the community before, 
>during, and after an IETF meeting.  If you are a 
>BOF chair, then you may use the tool to submit a 
>revised agenda as well as other materials for 
>your BOF once the BOF has been approved.
>
>The URL for the tool is:
>
>https://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 "IETF Meeting 
>Session Request Tool" and the "IETF Meeting 
>Materials Management Tool."  The same User ID 
>and password will work for both tools.  If you 
>are a BOF chair who is not also a Working Group 
>chair, then you will be given an account on the 
>"IETF Meeting Materials Management Tool" when 
>your BOF has been approved.  If you require 
>assistance in using either tool, or wish to 
>report a bug, then please send a message to:
>[e-mail].
>===============================================================
>For your convenience, comprehensive information 
>on requesting meeting sessions at IETF 86 is presented below:
>
>1. Requests to schedule Working Group sessions 
>should be submitted using the "IETF Meeting 
>Session Request Tool," a Web-based tool for 
>submitting all of the information required by 
>the Secretariat to schedule your sessions.  The URL for the tool is:
>
>https://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 please send a 
>message to [e-mail].  If you are 
>unable to use the tool, then you may send your 
>request via e-mail to [e-mail], with a 
>copy to the appropriate Area Director(s).
>
>Requests to schedule BOF sessions must be sent 
>to [e-mail] with a copy to the appropriate Area Director(s).
>
>When submitting a Working Group or BOF session 
>request by e-mail, please include the Working 
>Group or BOF acronym in the Subject line.
>
>2. BOFs will NOT be scheduled unless the Area 
>Director(s) approved the BOF. The proponents 
>behind a BOF need to contact a relevant Area 
>Director, preferably well in advance of the BOF 
>approval deadline date. The AD needs to have the 
>full name of the BOF, its acronym, suggested 
>names of chairs, an agenda, full description of 
>the BOF and the information covered in item 4. 
>Please read RFC 5434 for instructions on how to 
>drive a successful BOF effort. The approval 
>depends on, for instance, Internet-Drafts and 
>list discussion on the suggested topic. BOF 
>agenda requests, if approved, will be submitted 
>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 
>availability, after Monday, February 11, 2013, 
>the cut-off date for requests to reschedule a session.
>
>4. You MUST provide the following information 
>before a Working Group or BOF session will be scheduled:
>
>     a. Working Group or BOF full name with acronym in brackets:
>
>     b. AREA under which Working Group or BOF appears:
>
>     c. CONFLICTS you wish to avoid, please be as specific as possible:
>
>     d. Expected Attendance:
>
>     e. Special requests:
>
>     f. Number of sessions:
>
>     g. Length of session:
>        - 1 hour
>        - 1 1/2 hours
>        - 2 hours
>        - 2 1/2 hours
>
>For more information on scheduling Working Group 
>and BOF sessions, please refer to RFC 2418 (BCP 
>25), "IETF Working Group Guidelines and 
>Procedures" (http://www.ietf.org/rfc/rfc2418.txt).
>===============================================================
>For your convenience please find here a list of 
>the IETF Area Directors with their e-mail addresses:
>
>IETF Chair
>Russ Housley <[e-mail]>
>
>Applications Area (app)
>Barry Leiba <[e-mail]>
>Pete Resnick <[e-mail]>
>
>Internet Area (int)
>Ralph Droms <[e-mail]>
>Brian Haberman <[e-mail]>
>
>Operations & Management Area (ops)
>Ronald Bonica <[e-mail]>
>Benoit Claise <[e-mail]>
>
>Real-time Applications and Infrastructure Area (rai)
>Gonzalo Camarillo <[e-mail]>
>Robert Sparks <[e-mail]>
>
>Routing Area (rtg)
>Stewart Bryant <[e-mail]>
>Adrian Farrel <[e-mail]>
>
>Security Area (sec)
>Stephen Farrell <[e-mail]>
>Sean Turner <[e-mail]>
>
>Transport Area (tsv)
>Wesley Eddy <[e-mail]>
>Martin Stiemerling <[e-mail]>
>  ===========================================================
>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
>
>
>
>
>_______________________________________________
>conex mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/conex

________________________________________________________________
Bob Briscoe,                                BT Innovate & Design