Prefix Flag Extension for OSPFv2 and OSPFv3
draft-ietf-lsr-ospf-prefix-extended-flags-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Ran Chen , Detao Zhao , Peter Psenak , Ketan Talaulikar , Liyan Gong | ||
| Last updated | 2024-07-28 (Latest revision 2024-01-25) | ||
| Replaces | draft-chen-lsr-prefix-extended-flags | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 Attribute Flags Sub-TLVs for OSPFv2 and OSPFv3 respectively for the extended flag fields.
Authors
Ran Chen
Detao Zhao
Peter Psenak
Ketan Talaulikar
Liyan Gong
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)