Congestion Exposure BoF (ConEx)

(was re-ECN)

Draft Charter

BoF minutes & slides

BoF Chairs

Leslie Daigle & Philip Eardley


Congestion Exposure (ConEx) is a proposed new IETF activity to enable congestion to be exposed along the forwarding path of the Internet. By revealing expected congestion in the IP header of packets, congestion exposure provides a generic network capability which allows greater freedom over how capacity is shared. Such information could be used for many purposes, including congestion policing, accountability and inter-domain SLAs. It may also open new approaches to QoS and traffic engineering.

The Internet is, in essence, about pooling resources. The ability to share capacity has been paramount to its success and has traditionally been managed through the voluntary use of TCP congestion control. However, TCP doesn't account for how much an application (and a user) occupies capacity over time. This has led ISPs to deploy ad-hoc mechanisms such as volume accounting, rate policing and deep packet inspection. These try to protect the experience of the majority of users by limiting persistent traffic such as peer-to-peer file-sharing or video streaming. These ad-hoc practices can stifle innovation at the transport and application layer, and have led to calls for government regulations (see for example, the problem statement I-D (ref below) and RFC5594).

We believe these problems stem from the lack of a network-layer system for accountability -- among all parties -- for sending traffic which causes congestion. We propose a metric where IP packets carry information about the expected rest-of-path congestion, so that any network node may estimate how much congestion it is likely to cause by sending or forwarding traffic. A network operator can then count the volume of congestion about to be caused by an aggregate of traffic as easily as it can count the volume of bytes entering its network today.

Once ISPs can see rest-of-path congestion, they will no longer need to unnecessarily limit volume or bit-rate or p2p just in case it leads to congestion. They can limit only those users who actually cause large volumes of congestion, and they can discourage other networks from allowing their users to cause congestion. This will allow ISPs to encourage transports like LEDBAT that send large amounts of volume while causing little congestion. And end-hosts may be freed from peak rate restrictions when their traffic causes little congestion.

The purpose of the BoF is to explore the support for and viability of pursuing an IETF activity to define a basic protocol to expose the expected rest-of-path congestion in the IP header. Any such protocol should work with minimal changes to the existing network, in particular it should work with unmodified routers. There is already one existing proposal that builds on ECN to provide rest-of-path congestion information in IP headers and other proposals may come forward.

If supported, an eventual WG would focus on the development of its chosen congestion exposure protocol as its main work item. The chosen protocol will need to be deployable with minimal changes to the existing Internet, preferably working with unmodified routers. Additional work items could include detailing the motivations for congestion exposure, a threat analysis of the subsequent protocol, reporting on experimental trials and describing deployment considerations. Importantly, the proposed WG would encourage experimentation but not deliberate on how congestion exposure should be used: our concern would be how flexibly the resulting protocol can support differing needs at run-time, rather than dictating a particular usage at design time.

Related Internet-Drafts include:

ConEx Problem statement:
re-ECN protocol spec:
re-ECN motivation:

Other useful reference material:

Overview: problem & solution (7pp):

Mailing list for discussion: re-ecn@…

IETF 76 BoF Proposal

Meeting Notes

Other Related Resources

Last modified 8 years ago Last modified on Mar 5, 2010, 5:34:38 AM