Extensions to OSPF for Advertising Prefix Administrative Tags
draft-acee-lsr-ospf-admin-tags-07

Document Type Replaced Internet-Draft (lsr WG)
Authors Acee Lindem  , Peter Psenak 
Last updated 2021-01-20 (latest revision 2020-09-23)
Replaced by draft-ietf-lsr-ospf-admin-tags
Stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state Adopted by a WG
Document shepherd Christian Hopps
IESG IESG state Replaced by draft-ietf-lsr-ospf-admin-tags
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to chopps@chopps.org

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-acee-lsr-ospf-admin-tags-07.txt

Abstract

It is useful for routers in an OSPFv2 or OSPFv3 routing domain to be able to associate tags with prefixes. Previously, OSPFv2 and OSPFv3 were relegated to a single tag for AS External and Not-So-Stubby-Area (NSSA) prefixes. With the flexible encodings provided by OSPFv2 Prefix/Link Attribute Advertisement and OSPFv3 Extended LSAs, multiple administrative tags may advertised for all types of prefixes. These administrative tags can be used for many applications including route redistribution policy, selective prefix prioritization, selective IP Fast-ReRoute (IPFRR) prefix protection, and many others. The ISIS protocol supports a similar mechanism that is described in RFC 5130.

Authors

Acee Lindem (acee@cisco.com)
Peter Psenak (ppsenak@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)