RFC 8084: Network Transport Circuit Breakers
In plain English — editorial summary, not part of the RFC
This document explains what is meant by the term "network transport Circuit Breaker". It describes the need for Circuit Breakers (CBs) for network tunnels and applications when using non-congestion- controlled traffic and explains where CBs are, and are not, needed. It also defines requirements for building a CB and the expected outcomes of using a CB within the Internet.
Document record
- Document ID
- RFC8084
- Published
- March 2017
- Authors
- G. Fairhurst
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- wit
- Pages
- 24
- Also known as
- BCP208
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7510Encapsulating MPLS in UDPCurrent
April 2015
- RFC 6679Explicit Congestion Notification (ECN) for RTP over UDPUpdated
August 2012
- RFC 6633Deprecation of ICMP Source Quench MessagesCurrent
May 2012
- RFC 7978Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Header ExtensionCurrent
September 2016
- RFC 6935IPv6 and UDP Checksums for Tunneled PacketsCurrent
April 2013
- RFC 5512The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation AttributeObsoleted
April 2009
- RFC 2637Point-to-Point Tunneling Protocol (PPTP)Current
July 1999
- RFC 8085UDP Usage GuidelinesUpdated
March 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?