1 Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP draft-briscoe-tsvwg-ecn-encap-guidelines-01 Bob Briscoe IETF-85 Nov 2012.

Slides:



Advertisements
Similar presentations
Tunnel congestion Feedback (draft-wei-tunnel-congestion-feedback-01) Xinpeng Wei Lei Zhu Lingli Deng Huawei Huawei China Mobile IETF 89 London, UK.
Advertisements

Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP draft-briscoe-tsvwg-ecn-encap-guidelines-00 Bob Briscoe IETF-80 Mar 2011.
Problem Statement and Architecture for Information Exchange Between Interconnected Traffic Engineered Networks draft-farrel-interconnected-te-info-exchange-03.txt.
TELE202 Lecture 8 Congestion control 1 Lecturer Dr Z. Huang Overview ¥Last Lecture »X.25 »Source: chapter 10 ¥This Lecture »Congestion control »Source:
Top-Down Network Design Chapter Thirteen Optimizing Your Network Design Copyright 2010 Cisco Press & Priscilla Oppenheimer.
A Test To Allow TCP Senders to Identify Receiver Non-Compliance Toby Moncaster †, Bob Briscoe*, Arnaud Jacquet* † University of Cambridge * BT draft-moncaster-tcpm-rcv-cheat-03.
An open ECN service in the IP layer 19 Mar 2001 Bob Briscoe, BT & UCL Jon Crowcroft, UCL M3I - Market Managed Multi-service Internet IST Project No
© British Telecommunications plc 1 Network Performance Isolation in Data Centres using ConEx Congestion Policing draft-briscoe-conex-policing-01 draft-briscoe-conex-data-centre-02.
Explicit Congestion Notification (ECN) RFC 3168 Justin Yackoski DEGAS Networking Group CISC856 – TCP/IP Thanks to Namratha Hundigopal.
1 Internet Networking Spring 2003 Tutorial 11 Explicit Congestion Notification (RFC 3168) Limited Transmit (RFC 3042)
1 Internet Networking Spring 2003 Tutorial 11 Explicit Congestion Notification (RFC 3168)
A Real-Time Video Multicast Architecture for Assured Forwarding Services Ashraf Matrawy, Ioannis Lambadaris IEEE TRANSACTIONS ON MULTIMEDIA, AUGUST 2005.
1 Spring Semester 2007, Dept. of Computer Science, Technion Internet Networking recitation #8 Explicit Congestion Notification (RFC 3168) Limited Transmit.
Internet, Part 2 1) Session Initiating Protocol (SIP) 2) Quality of Service (QoS) support 3) Mobility aspects (terminal vs. personal mobility) 4) Mobile.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Security Level: Slide title :40-47pt Slide subtitle :26-30pt Color::white Corporate Font : FrutigerNext.
Initial ConEx Deployment Examples draft-briscoe-conex-initial-deploy-00.txt draft-briscoe-conex-initial-deploy-00.txt apologies from Bob Briscoe, BT presented.
ConEx Concepts and Abstract Mechanism draft-ietf-conex-abstract-mech-07.txt draft-ietf-conex-abstract-mech-07.txt Matt Mathis, Google Bob Briscoe, BT IETF-87.
1 Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP draft-briscoe-tsvwg-ecn-encap-guidelines-02 Bob Briscoe, BT John Kaippallimalil,
Byte and Packet Congestion Notification draft-ietf-tsvwg-byte-pkt-congest-02.txt draft-ietf-tsvwg-byte-pkt-congest-02.txt Bob Briscoe, BT IETF-78 tsvwg.
1 Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP draft-ietf-tsvwg-ecn-encap-guidelines-01 Bob Briscoe, BT John Kaippallimalil,
Tunnelling of Explicit Congestion Notification draft-briscoe-tsvwg-ecn-tunnel-08.txt draft-briscoe-tsvwg-ecn-tunnel-08.txt Bob Briscoe, BT IETF-77 tsvwg.
© 2006 Cisco Systems, Inc. All rights reserved. Optimizing Converged Cisco Networks (ONT) Module 4: Implement the DiffServ QoS Model.
Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets A. Kuzmanovic, A. Mondal, S. Floyd, and K.K. Ramakrishnan draft-ietf-tcpm-ecnsyn-03.txt.
ConEx Concepts and Abstract Mechanism draft-mathis-conex-abstract-mech-00.txt draft-mathis-conex-abstract-mech-00.txt Matt Mathis, Google Bob Briscoe,
PPTP Point-to-Point Tunneling Protocol (PPTP) –Problem: PPP was created for dialing into a local RAS server –But the site’s RAS may be far away –Long-distance.
Byte and Packet Congestion Notification draft-briscoe-tsvwg-byte-pkt-mark-01.txt draft-briscoe-tsvwg-byte-pkt-mark-01.txt Bob Briscoe, BT & UCL IETF-70.
Byte and Packet Congestion Notification draft-briscoe-tsvwg-byte-pkt-mark-00.txt draft-briscoe-tsvwg-byte-pkt-mark-00.txt Bob Briscoe, BT & UCL IETF-69.
1 Congestion Control Computer Networks. 2 Where are we?
Congestion exposure BoF candidate protocol: re-ECN Bob Briscoe Chief Researcher, BT Nov 2009 This work is partly funded by Trilogy, a research project.
Tunnelling of Explicit Congestion Notification draft-briscoe-tsvwg-ecn-tunnel-03.txt draft-briscoe-tsvwg-ecn-tunnel-03.txt Bob Briscoe, BT IETF-75 saag.
Byte and Packet Congestion Notification draft-ietf-tsvwg-byte-pkt-congest-00.txt draft-ietf-tsvwg-byte-pkt-congest-00.txt Bob Briscoe, BT & UCL IETF-73.
Congestion Notification Mechanisms in 802 networks Manoj Wadekar IEEE Interim Meeting January 12, 2005.
Doc.: IEEE /0158r2 Submission TGaq Pre-Association Discovery Protocol for ANDSF Discovery Service Date: May 2014 Joe Kwak, InterDigitalSlide.
Tunnelling of Explicit Congestion Notification draft-briscoe-tsvwg-ecn-tunnel-02.txt draft-briscoe-tsvwg-ecn-tunnel-02.txt Bob Briscoe, BT IETF-74 tsvwg.
Guaranteed QoS Synthesiser (GQS) Bob Briscoe, Peter Hovell BT Research Jan 2005.
Mr. Mark Welton.  Quality of Service is deployed to prevent data from saturating a link to the point that other data cannot gain access to it  QoS allows.
Network Performance Isolation in Data Centres using Congestion Policing draft-briscoe-conex-data-centre-01.txt draft-briscoe-conex-data-centre-01.txt Bob.
ConEx Concepts and Abstract Mechanism draft-ietf-conex-abstract-mech-01.txt draft-ietf-conex-abstract-mech-01.txt Matt Mathis, Google Bob Briscoe, BT IETF-80.
1 Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP draft-briscoe-tsvwg-ecn-encap-guidelines-03 Bob Briscoe, BT John Kaippallimalil,
Support for ECN and PCN in MPLS networks draft-davie-ecn-mpls-00.txt Bruce Davie Cisco Systems Bob Briscoe June Tay BT Research.
Byte and Packet Congestion Notification draft-briscoe-tsvwg-byte-pkt-mark-02.txt draft-briscoe-tsvwg-byte-pkt-mark-02.txt Bob Briscoe, BT & UCL IETF-71.
The Benefits to Applications of using Explicit Congestion Notification (ECN) draft-welzl-ecn-benefits-00 89th IETF Meeting London, UK 4 March 2014 Michael.
Initial ConEx Deployment Examples draft-briscoe-conex-initial-deploy-00.txt draft-briscoe-conex-initial-deploy-00.txt apologies from Bob Briscoe, BT presented.
1 Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP draft-briscoe-tsvwg-ecn-encap-guidelines-04 Bob Briscoe, BT John Kaippallimalil,
Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP (draft-ietf-tsvwg-ecn-encap-guidelines-04) Bob Briscoe (Simula Research.
Congestion Notification Process for Real-Time Traffic draft-babiarz-tsvwg-rtecn-04.txt Jozef Babiarz Kwok Ho Chan
Philip Eardley, Bob Briscoe, Dave Songhurst - BT Francois Le Faucheur, Anna Charny, Vassilis Liatsos – Cisco Kwok-Ho Chan, Joe Babiarz, Stephen Dudley.
Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets A. Kuzmanovic, A. Mondal, S. Floyd, and K.K. Ramakrishnan draft-ietf-tcpm-ecnsyn-02.txt.
1 Congestion and Congestion Control in Packet- Switched Networks.
Layered Encapsulation of Congestion Notification draft-briscoe-tsvwg-ecn-tunnel-01.txt draft-briscoe-tsvwg-ecn-tunnel-01.txt Bob Briscoe, BT IETF-72 tsvwg.
recap draft-ietf-tsvwg-ecn-encap-guidelines-07
draft-briscoe-tsvwg-l4s-arch-00 B. Briscoe, K. De Schepper, M. Bagnulo
Support for ECN and PCN in MPLS networks
Bob Briscoe, BT IETF-73 pcn Nov 2008
Internet Networking recitation #9
Bob Briscoe Simula Research Laboratory
Top-Down Network Design Chapter Thirteen Optimizing Your Network Design Copyright 2010 Cisco Press & Priscilla Oppenheimer.
Encoding 3 PCN-States in the IP header using a single DSCP draft-ietf-pcn-3-in-1-encoding-06.txt Bob Briscoe, BT Toby Moncaster, independent Michael Menth,
Point-to-Multipoint Pseudo-Wire Encapsulation draft-raggarwa-pwe3-p2mp-pw-encaps-00.txt R. Aggarwal (Juniper)
Bob Briscoe, BT Murari Sridharan, Microsoft IETF-84 ConEx Jul 2012
15th November 2016 Gorry Fairhurst (via webrtc) David Black WG chairs
Bob Briscoe, BT IETF-72 tsvwg Jul 2008
Bob Briscoe Simula Research Laboratory
draft-bagnulo-tcpm-generalized-ecn-00 M. Bagnulo & B. Briscoe IETF97
Additional TRILL Work/Documents
Michael Welzl University of Oslo
Internet Networking recitation #10
ECN Experimentation draft-black-ecn-experimentation
Encoding 3 PCN-States in the IP header using a single DSCP draft-ietf-pcn-3-in-1-encoding-06.txt Bob Briscoe, BT Toby Moncaster, independent Michael Menth,
DetNet Architecture Updates
Presentation transcript:

1 Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP draft-briscoe-tsvwg-ecn-encap-guidelines-01 Bob Briscoe IETF-85 Nov 2012

2 explicit congestion notification (ECN) growing interest again in recognition of the importance of low delay particularly in L2 networks (backhaul, data centres) drop: both congestion signal and impairment compromise: deliberately delay the signals (bufferbloat) ECN: a signal without impairment can signal as early as needed

3 problem AQM* & ECN are for queues at any layer not just IP ECN has to be explicitly propagated up the layers in contrast drop is easy it naturally propagates up the layers * AQM = active queue management (e.g. RED)

4 aim of this draft guidelines for writing specs to propagate ECN up to IP from: L2 protocols (e.g. IEEE802, TRILL) tunnelling protocols (L2TP, GRE, PPTP, GTP,…) for authors who may not be ECN experts draft status resurrected individual draft, -00 posted 18months ago fell down my priority list, but has become important again intended status: best current practice L2TP = layer 2 tunnelling protocol [RFC2661] PPTP = Point-to-point Tunnelling Protocol [RFC2637] GRE = generic routing encapsulation [RFC1701, RFC2784] QCN = quantised congestion notification [IEEE 802.1Qau] GTP = GPRS tunnelling protocol [3GPP TS ]

5 a variety of arrangements avoid precluding L2 innovation must not be over-prescriptive guidelines for each mode see draft (or spare slides) wide expertise needed for authoring & review app L4 IP L app L4 IP L app L4 IP L2 3 4 forward-and-up mode up-and-forward mode backward mode null mode

6 next steps process aim to request adoption as wg item at next IETF will require liaison with other standards bodies –setting requirements for interfacing IP with their protocols document I’m conscripting expert help –L2 & tunnelling experts text & structure largely complete –new co-authors & reviewers may disagree reviews pls

Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP draft-briscoe-tsvwg-ecn-encap-guidelines-01 Q&A & spare slides

8 status of congestion notification in protocols that encapsulate IP IETF done: MPLS-in-MPLS, IP-in-MPLS [RFC5129], IP-in-IP [RFC6040] to do: trill-rbridge-options (in progress), & pass ECN thru tunnel protocols, eg. L2TP, GRE Other standards bodies: done: QCN [802.1Qau], Frame Relay, ATM [I.371] (all subnet-local) todo: IEEE 802.1, (802.3, ), …? & pass ECN thru tunnel protocols, eg. 3GPP GTP L2TP = layer 2 tunnelling protocol [RFC2661] GRE = generic routing encapsulation [RFC1701, RFC2784] QCN = quantised congestion notification GTP = GPRS tunnelling protocol - user plane [3GPP TS ]

9 forward and upward mode requirements identifying whether transport will understand ECN identifying whether egress will understand ECN propagating ECN on encapsulation propagating ECN on decapsulation reframing issues app L4 IP L

10 forward and upward mode guidelines identifying whether transport will understand ECN ‘ECN-capable transport’ codepoint or other approaches identifying whether egress will understand ECN new problem propagating ECN on encapsulation copying ECN down for monitoring purposes propagating ECN on decapsulation combining inner & outer reframing issues marked bytes in  marked bytes out timeliness – don’t hold back any remainder app L4 IP L

11 the main problem: incremental deployment IP-ECN designed for incremental deployment if transport only understands drop lower layer must not send it congestion indications need not mimic IP mechanism (grey) but needs to achieve same outcome (white) also, must check egress understands ECN too congested queue supports ECN? transport supports ECN?IP headerNY NNot-ECTdrop YECTdropCE ECT = ECN-capable transport CE = Congestion Experienced

12 up and forward mode guidelines identifying whether transport will understand ECN use IP mechanism identifying whether egress will understand ECN propagating ECN on encapsulation propagating ECN on decapsulation reframing issues a layering violation but safe if guidelines apply app L4 IP L

13 backward mode often designed for where the subnet is the whole network doesn’t interwork efficiently with IP’s forwards-only mode app L4 IP L2 IEEE 802.1Qau (QCN) ATM ITU-T-I.371 Frame Relay app L4 IP L congestion f/b slows down L2 incoming load unchanged backs up into L3 not a good fit