Prefix Flag Extension for OSPFv2 and OSPFv3
draft-chen-lsr-prefix-extended-flags-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ran Chen , Detao Zhao , Peter Psenak , Ketan Talaulikar | ||
| Last updated | 2023-11-05 | ||
| Replaced by | draft-ietf-lsr-ospf-prefix-extended-flags | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-lsr-ospf-prefix-extended-flags | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Within OSPF, each prefix is advertised along with an 8-bit field of capabilities, by using the Prefix Options (OSPFv3) and the flag flield in the OSPFv2 Extended Prefix TLV (OSPFv2). However, for OSPFv3, all the bits of the Prefix Options have already been assigned, and for OSPFv2, there are not many undefined bits left in the OSPFv2 Extended Prefix TLV. This document solves the problem of insufficient existing flags, and defines the variable length Prefix attributes Sub-TLVs for OSPFv2 and OSPFv3 respectively for the extended flag fields.
Authors
Ran Chen
Detao Zhao
Peter Psenak
Ketan Talaulikar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)