Web Elucidation of Internet Related Developments WG 47th IETF - Adelaide, SA, Australia.
IETF-90 AQM WG
description
Transcript of IETF-90 AQM WG
IETF-90, Toronto 1
IETF-90 AQM WGWesley Eddy <[email protected]>
Richard Scheffenegger <[email protected]>
July 22, 2014
http://www.ietf.org/mail-archive/web/aqm/current/maillist.html
IETF-90, Toronto 2
Note WellAny submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:
– The IETF plenary session– The IESG, or any member thereof on behalf of the IESG– Any IETF mailing list, including the IETF list itself, any working group or design team list, or any
other list functioning under IETF auspices– Any IETF working group or portion thereof– Any Birds of a Feather (BOF) session– The IAB or any member thereof on behalf of the IAB– The RFC Editor or the Internet-Drafts function
All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879). Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 5378 and RFC 3979 for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.July 22, 2014
IETF-90, Toronto 3
IETF-90 AQM WG Agenda
Day Time Topics Speaker
Tuesday 16:40 WG Status & Agenda BashingProcess for adopting algorithms
Chairs
17:00 draft-ietf-aqm-recommendation Gorry / Fred
17:15 draft-kuhn-aqm-eval-guidelines Nicolas Kuhn
18:00 draft-baker-aqm-sfq-implementation Fred Baker
Tentative 18:20 The Case for Comprehensive Queue Management
Dave That
Tentative 18:35 draft-welzl-ecn-benefits Michael Welzl
July 22, 2014
IETF-90, Toronto 4
WG / Milestone Items
•draft-ietf-aqm-recommendationsWGLC was completedComments discussed during interim in June
• draft-kuhn-aqm-eval-guidelinesReady to adopt?
July 22, 2014
IETF-90, Toronto 5
Algorithms
• One goal of the working group is to advance algorithm specifications
• The initial plan to do this in serial after evaluation guidelines may be too slow
• The next slide is a proposal for a process to advance algorithm specifications in parallel to the evaluation guidelines.
July 22, 2014
IETF-90, Toronto 6July 22, 2014
Internet-Draft on Algorithm X
Gate-1Decision
Authors Start AQM List Discussions
on Draft for Algorithm X
Authors can present on draft at WG meetings,
telecons, etc. and continue to discuss on-list
Gate-2 Decision
Editors work to improve the draft based on
feedback, testing, and experience with implementations
Working Group Draft on Algorithm X
Draft Submitted as Experimental RFC
Gate-3 Decision
Chairs Either Submit Document to ADs for
Publication, or Remove as WG Item
Draft Submitted as Informational RFC(e.g. inferior to other
algorithms, etc)
WG Draft Dead(e.g. loss of
interest)
Working Group Last Call
Working Group Adoption Call
For Gate-1: Algorithm should be reasonably described, reasonably unique from other algorithms, and have some promise towards meeting the goals and recommendations in the AQM BCP
For Gate-2: Algorithm should be actively evaluated or worked with by multiple groups (not just the editors), committed to implementing, testing, and/or eventually deploying it.
For Gate-3: Algorithm should have been carefully evaluated with regard to AQM evaluation guidelines for some target scenario(s), and updated with regard to relevant experience, lessons learned, etc. Any further research or improvements are necessary should be identified, or any caveats or risks to deploying it should be understood.
Eventually, there could be a “Gate-4” for advancing Experimental RFCs to the Standards Track.