RFC 7777: Advertising Node Administrative Tags in OSPF
In plain English — editorial summary, not part of the RFC
This document describes an extension to the OSPF protocol to add an optional operational capability that allows tagging and grouping of the nodes in an OSPF domain. This allows simplification, ease of management and control over route and path selection based on configured policies. This document describes an extension to the OSPF protocol to advertise node administrative tags. The node tags can be used to express and apply locally defined network policies, which are a very useful operational capability. Node tags may be used by either OSPF itself or other applications consuming information propagated via OSPF. This document describes the protocol extensions to disseminate node administrative tags to the OSPFv2 and OSPFv3 protocol. It provides example use cases of administrative node tags.
Document record
- Document ID
- RFC7777
- Published
- March 2016
- Authors
- S. Hegde; R. Shakir; A. Smirnov; Z. Li; B. Decraene
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7770Extensions to OSPF for Advertising Optional Router CapabilitiesCurrent
February 2016
- RFC 7684OSPFv2 Prefix/Link Attribute AdvertisementCurrent
November 2015
- RFC 5820Extensions to OSPF to Support Mobile Ad Hoc NetworkingUpdated
March 2010
- RFC 5709OSPFv2 HMAC-SHA Cryptographic AuthenticationUpdated
October 2009
- RFC 5643Management Information Base for OSPFv3Current
August 2009
- RFC 5642Dynamic Hostname Exchange Mechanism for OSPFCurrent
August 2009
- RFC 5613OSPF Link-Local SignalingCurrent
August 2009
- RFC 5523OSPFv3-Based Layer 1 VPN Auto-DiscoveryCurrent
April 2009
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?