Browse Prior Art Database

Network Transport Circuit Breakers (RFC8084)

IP.com Disclosure Number: IPCOM000249614D
Original Publication Date: 2017-Mar-01
Included in the Prior Art Database: 2017-Mar-08
Document File: 48 page(s) / 62K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Fairhurst: AUTHOR

Abstract

The term "Circuit Breaker" originates in electricity supply, and has nothing to do with network circuits or virtual circuits. In electricity supply, a Circuit Breaker (CB) is intended as a protection mechanism of last resort. Under normal circumstances, a CB ought not to be triggered; it is designed to protect the supply network and attached equipment when there is overload. People do not expect an electrical CB (or fuse) in their home to be triggered, except when there is a wiring fault or a problem with an electrical appliance.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Internet Engineering Task Force (IETF)                      G. Fairhurst Request for Comments: 8084                        University of Aberdeen BCP: 208                                                      March 2017 Category: Best Current Practice ISSN: 2070-1721

                    Network Transport Circuit Breakers

Abstract

   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.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    BCPs is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8084.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Fairhurst                 Best Current Practice                 [Page 1]
 RFC 8084                                                      March 2017

 Table of Contents

   1. Introduction ....................................................2

      1.1. Types of CBs ...............................................5

   2. Terminology .....................................................6

   3. Design of a CB (What makes a good CB?) ..........................6

      3.1. Functional Components ......................................6

      3.2. Other Network Topologies ...................................9

           3.2.1. Use with a Multicast Control/Routing Protocol ......10

        ...