IETF-87 AQM BoF Wesley Eddy Richard Scheffenegger Tue., 30. July 2013 17:00, Potsdam 1 Room 30 July 20131IETF-87, Berlin,

Slides:



Advertisements
Similar presentations
IETF Calsify.
Advertisements

STRAW IETF#91, Honolulu, USA. Victor Pascual Christer Holmberg.
IETF-92 AQM WG Wesley Eddy Richard Scheffenegger 24 March, 2015IETF-92, Dallas1
Deterministic Networking (DetNet) BoF IETF 91 Monday Afternoon Session II, Coral 1.
L2VPN WG “NVO3” Meeting IETF 82 Taipei, Taiwan. Agenda Administrivia Framing Today’s Discussions (5 minutes) Cloud Networking: Framework and VPN Applicability.
IETF-87 AQM BoF Wesley Eddy Richard Scheffenegger Tue., 30. July :00, Potsdam 1 Room 30 July 20131IETF-87, Berlin,
Note Well Any 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.
PPSP Working Group IETF-89 London, UK 16:10-18:40, Tuesday, Webex: participation.html.
CCAMP Working Group Online Agenda and Slides at: Tools start page:
DRINKS Interim („77.5“) Reston, VA Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF.
IETF 90: NetExt WG Meeting. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet- Draft.
IETF-89 AQM WG Wesley Eddy Richard Scheffenegger
Note Well Any 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.
L3VPN WG IETF 78 09/11/ :00-15:00 Chairs: Marshall Eubanks Danny McPherson Ben Niven-Jenkins.
Dime WG Status Update IETF#81, THURSDAY, July 28, Afternoon Session I.
SIPCLF Working Group Spencer Dawkins Theo Zourzouvillys IETF 76 – November 2009 Hiroshima, Japan.
EAP Method Update (EMU) IETF-79 Chairs Joe Salowey Alan DeKok.
1 NOTE WELL Any 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.
GROW IETF 78 Maastricht, Netherlands. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.
Authority To Citizen Alerts IETF 81 Quebec. Note: Note Well the Note Well Any submission to the IETF intended by the Contributor for publication as all.
IETF 86 PIM wg meeting. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC.
IETF 79 - Beijing, China1 Martini Working Group IETF 79 Beijing Chairs: Bernard Spencer
Extensible Messaging and Presence Protocol (XMPP) WG Interim Meeting, Monday, January 7,
Tictoc working group Thursday, 28 July – 1720 EDT (1920 – 2120 UTC) Karen O’Donoghue and Yaakov Stein, co-chairs.
Technical Plenary Agenda IETF 81 Quebec City, Quebec July 25, 2011 Presentations: Jabber room:
SIPREC WG, IETF# , GMT+2 John Elwell (WG co-chair) Brian Rosen (WG co-chair)
CCAMP Working Group Online Agenda and Slides at: Data tracker:
Web Authorization Protocol (oauth) IETF 90, Toronto Chairs: Hannes Tschofenig, Derek Atkins Responsible AD: Kathleen Moriarty Mailing List:
Web Authorization Protocol (oauth) Hannes Tschofenig.
Transport Service (TAPS) Aaron Falk
BFD IETF 83. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any.
OAuth WG Blaine Cook, Hannes Tschofenig. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.
Authentication and Authorization for Constrained Environment (ACE) WG Chairs: Kepeng Li, Hannes
IETF 89, LONDON, UK LISP Working Group. 2 Agenda and slides:  lisp.html Audio Stream 
IETF – NVO3 WG Virtual Interim Meeting Chairs: Secretary: Sam Aldrin Benson Schliesser Matthew Bocci.
DNSEXT at IETF-83 Paris 2012/3/27 at 17:10 – 18:10 Ólafur Guðmundsson Andrew Sullivan.
DMM WG IETF 84 DMM WG Agenda & Status Tuesday, July 31 st, 2012 Jouni Korhonen, Julien Laganier.
1 Transport Area Open Meeting Lars Eggert & Magnus Westerlund IETF-69 Chicago, IL, USA
LMAP WG IETF 92, Dallas, TX Dan Romascanu Jason Weil.
Transport Layer Security (TLS) IETF-84 Chairs: Eric Rescorla Joe Salowey.
Interface to the Routing System (IRS) BOF IETF 85, Atlanta November 2012.
IPR WG IETF 62 Minneapolis. IPR WG: Administrivia Blue sheets Scribes Use the microphones Note Well.
IETF #81 - NETCONF WG session 1 NETCONF WG IETF 81, Quebec City, Canada MONDAY, July 25, Bert Wijnen Mehmet Ersue.
Transport Layer Security (TLS) IETF-78 Chairs Joe Salowey Eric Rescorla
HIP WG Gonzalo Camarillo David Ward IETF 80, Prague, Czech Republic THURSDAY, March 31, 2011, Barcelona/Berlin.
OPSREA Open Meeting Area Directors: Dan Romascanu and Ron Bonica Monday, March 28, 2011 Morning Session, 10:30 – 11:30, Room Barcelona/Berlin Discussion.
Agenda Behcet Sarikaya Dirk von Hugo November 2012 FMC BOF IETF
IETF #82 - NETCONF WG session 1 NETCONF WG IETF 82, Taipei, Taiwan TUESDAY, November 15, Afternoon Session III Bert Wijnen Mehmet Ersue.
Agenda Stig Venaas Behcet Sarikaya November 2011 Multimob WG IETF
Alternatives to Content Classification for Operator Resource Deployment (ACCORD) BOF Chairs: Gonzalo Camarillo & Pete Resnick.
TSVAREA IETF84 - Vancouver. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.
Audio/Video Transport Extensions (avtext) Working Group Keith Drage Magnus Westerlund Jabber room:
OPSAWG chairs: Scott Bradner Christopher Liljenstolpe.
Agenda Wednesday, July 29, :00 – 15:00 Congresshall B Please join the Jabber room: LEDBAT WG IETF 75.
STIR Secure Telephone Identity Revisited
LMAP WG IETF 97 – Seoul, SK November 17, 2016 Dan Romascanu Jason Weil
Note Well Any 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.
MODERN Working Group IETF 97 November 14, 2016.
Kathleen Moriarty, Trusted Execution Environment Provisioning (TEEP) BoF IETF-100 November 2017 Chairs: Nancy Cam-Winget,
Note Well Any 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.
Thursday, 20th of July 2017.
16th November 2016 Gorry Fairhurst (via webrtc) David Black WG chairs
Agenda IETF 82 Taipei November 14, 2011
JSON Object Signing and Encryption (JOSE) Working Group
Flexible Ethernet (Side meeting)
20th July 2017 Gorry Fairhurst Wes Eddy David Black WG chairs
TEAS CCAMP MPLS PCE Working Groups
SIPBRANDY Chair Slides
Scott Bradner & Martin Thomson
Presentation transcript:

IETF-87 AQM BoF Wesley Eddy Richard Scheffenegger Tue., 30. July :00, Potsdam 1 Room 30 July 20131IETF-87, Berlin, Germany

Welcome to the AQM BoF 30 July 2013IETF-87, Berlin, Germany2 Active Queue Management Discussion Archive

Note Well Any 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. 30 July 2013IETF-87, Berlin, Germany3

IETF-87 AQM BoF Agenda 30 July 20134IETF-87, Berlin, Germany TopicsSpeakerTime Introduction & BackgroundChairs17:00 RecommendationsFred Baker (Cisco)17:05 PIE (Proportional Integral Controller Enhanced) Rong Pan (Cisco)17:15 [FQ-]CoDelAndrew McGregor (Google)17:30 Algorithm discussionGroup17:45 BoF QuestionsChairs18:00 Adjourn BoFChairs<18:30

Introduction and Background The Active Queue Ma­na­ge­ment and Packet Scheduling work­ing group (AQM) works on algorithms for reactively managing queues in or­der to minimize standing queues, help control the sending rates without un­due losses, minimize delays for in­ter­active apps, and protect flows from misbehaving flows. 30 July 2013IETF-87, Berlin, Germany5

PRESENTATIONS 30 July 20136IETF-87, Berlin, Germany

Algorithm discussion Similarities Use delay rather than occupancy Minimal tunable parameters Permit high link utilization Intend to permit efficient implementations Both are promising – Better than drop tail, RED Incremental deployment Differences PIE – Drop before enque – Compute drop rate from departure rate and queue length – Decoupled from FQ/CBQ implementation FQ-CoDel – Drop at Dequeue – Drop based on inferring a „bad“ standing queue – Recent CoDel work includes emphasis on integrating FQ/SFQ aspects with the AQM 30 July 2013IETF-87, Berlin, Germany7

BoF Questions are the goals of this WG clear, well-scoped, solvable, and useful? should Fred's document be an initial WG item? should packet scheduling be a part of the charter? how many people might be planning to work directly on algorithms? – writing the specs, implementing, testing / evaluating should the group require evaluation criteria and requirements to be finished before adopting algorithm specifications? should testing methodology be something the WG should focus on early? should the group initially aim for a single AQM spec, or take on multiple algorithms in parallel? – differentiate between Core and Edge? should an AQM working group be formed? should the working group NOT be formed? 30 July 2013IETF-87, Berlin, Germany8

WG Naming AQM – good enough naming for WG? – Potential to invoke historic connotations Scheduling and Queue Management (SQM) – suggested by Dave Taht, updated by Gorry Fairhurst Active Queue Management and Packet Scheduling (AQMPS) or Queue Utilization for Enhanced User Experience (QUEUE) – suggested by Grenville Armitage Queue Management (QMAN) – suggested by Bob Briscoe Queue Management And Packet Scheduling (QMAPS) – suggested by David Ros 30 July 2013IETF-87, Berlin, Germany9

30 July IETF-87, Berlin, Germany