RFC 8770: Host Router Support for OSPFv2
In plain English — editorial summary, not part of the RFC
The Open Shortest Path First Version 2 (OSPFv2) protocol does not have a mechanism for a node to repel transit traffic if it is on the shortest path. This document defines a bit called the Host-bit (H-bit). This bit enables a router to advertise that it is a non-transit router. This document also describes the changes needed to support the H-bit in the domain. In addition, this document updates RFC 6987 to advertise Type 2 External and Not-So-Stubby Area (NSSA) Link State Advertisements (LSAs) (RFC 3101) with a high cost in order to repel traffic effectively.
Document record
- Document ID
- RFC8770
- Published
- April 2020
- Authors
- K. Patel; P. Pillay-Esnault; M. Bhardwaj; S. Bayraktar
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
- Updates:
- RFC 6987
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8775PIM Designated Router Load BalancingCurrent
April 2020
- RFC 8776Common YANG Data Types for Traffic EngineeringCurrent
June 2020
- RFC 8779Path Computation Element Communication Protocol (PCEP) Extensions for GMPLSUpdated
July 2020
- RFC 8780The Path Computation Element Communication Protocol (PCEP) Extension for Wavelength Switched Optical Network (WSON) Routing and Wavelength Assignment (RWA)Updated
July 2020
- RFC 8757Dynamic Link Exchange Protocol (DLEP) Latency Range ExtensionCurrent
March 2020
- RFC 8786Updated Rules for Processing Stateful PCE Request Parameters FlagsCurrent
May 2020
- RFC 8751Hierarchical Stateful Path Computation Element (PCE)Current
March 2020
- RFC 8745Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCEUpdated
March 2020
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?