Prefix Flag Extension for OSPFv2 and OSPFv3

Introduction Each OSPF prefix can be advertised with an 8-bit field to indicate specific properties of that prefix. This is done using the OSPFv3 Prefix Options (Appendix A.4.1.1 of ) and the flags field in the OSPFv2 Extended Prefix TLV (Section 2.1 of ). The rest of this document refers to these 8-bit fields in both OSPFv2 and OSPFv3 as the "existing fixed-size prefix attribute flags". However, all the OSPFv3 Prefix Options bits have already been assigned (see "OSPFv3 Prefix Options (8 bits)" IANA registry ). Also, only 5 bits remain unassigned (at the time of publication of this document) in the Flags field of the OSPFv2 Extended Prefix TLV (see "OSPFv2 Extended Prefix TLV Flags" IANA registry ). This document solves the problem of insufficient flag bits for the signaling of prefix properties in OSPF by defining variable-length Prefix Attribute Flags sub-TLVs for OSPFv2 and OSPFv3.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Variable-Length Prefix Attribute Flags Sub-TLV This document defines variable-Length Prefix Attribute Flags sub-TLV for OSPFv2 and OSPFv3. Such sub-TLV specifies the variable-flag fields to advertise additional attributes associated with OSPF prefixes. The advertisement and processing of the existing fixed-size prefix attribute flags remain unchanged. The format of OSPFv2/OSPFv3 Prefix Attribute Flags sub-TLVs is shown in Figure 1.

where: Type (2 octets): 11 for OSPFv2 and 37 for OSPFv3. Length (2 octets): Variable, dependent on the included Prefix Attribute Flags. This indicates the length of the prefix attributes flags in octets. The length MUST be a multiple of 4 octets. If the length is not a multiple of 4 octets, the Link State Advertisement (LSA) is malformed and MUST be ignored. Prefix Attribute Flags (Variable): The extended flag field. This field contains a variable number of flags, grouped in 4-octet blocks. The bits are numbered starting from bit 0 as the most significant bit of the first 32-bit block. If a Prefix Attribute Flags field's length exceeds 4 octets, numbering for the additional bits picks up where the previous 4-octet block left off. For example, the most significant bit in the fifth octet of an 8-octet Prefix Attribute Flags is referred to as bit 32. Currently, no bits are defined in this document. Unassigned bits MUST be set to zero on transmission and MUST be ignored on receipt. An implementation MUST limit the length of the sub-TLV so as to signal the bits that are set to 1. Defined prefix flags that are not transmitted due to being beyond the transmitted length MUST be treated as being set to 0. OSPFv2 Prefix Attribute Flags sub-TLV is advertised as a sub-TLV of the OSPFv2 Extended Prefix TLV defined in . Additional OSPFv2 prefix flags SHOULD be allocated from the unused bits in the Flags field of the OSPFv2 Extended Prefix TLV prior to allocating flags in the OSPFv2 Prefix Attribute Flags sub-TLV. OSPFv3 Prefix Attribute Flags sub-TLV is advertised as a sub-TLV of the following OSPFv3 TLVs:

Inter-Area-Prefix TLV (Section 3.4 of ).
External-Prefix TLV (Section 3.6 of ).
Intra-Area-Prefix TLV (Section 3.7 of ).
SRv6 Locator TLV .

When multiple instances of the OSPFv2/OSPFv3 Prefix Attribute Flags sub-TLVs are received within the same TLV, an implementation MUST use only the first occurrence of the sub-TLV and MUST ignore all subsequent instances of the sub-TLV. Errors SHOULD be logged subject to rate limiting.

Backward Compatibility The Prefix Attribute Flags sub-TLV does not introduce any backward compatibility issues. An implementation that does not recognize the OSPFv2/OSPFv3 Prefix Attribute Flags sub-TLV would ignore the sub-TLV as per normal TLV processing operations (refer Section 6.3 of and Section 2.3.2 of ).

Acknowledgements The authors thank Shraddha Hegde, Changwang Lin, Tom Petch and many others for their suggestions and comments. The authors would like to thank Acee Lindem for aligning the terminology with existing OSPF documents and for editorial improvements.

IANA Considerations This document requests allocation for the following registries.

OSPFv2

OSPFv2 Prefix Attribute Flags Sub-TLV Registry This document requests IANA to make permanent the early allocation of the following codepoint for the "OSPFv2 Prefix Attribute Flags" in the "OSPFv2 Extended Prefix TLV Sub-TLVs" registry to be made permanent:

OSPFv2 Prefix Extended Flags Field Registry This document requests the creation of "OSPFv2 Prefix Extended Flag Field" Registry under "Open Shortest Path First v2 (OSPFv2) Parameters" registry group. The registry defines the bits in the Prefix Attribute Flags field in the OSPFv2 Prefix Attribute Flags sub-TLV as specified in Section 2. The bits are to be allocated via IETF Review . Each bit definition will include: No bits are currently defined. Bits 0-31 are to be initially marked as "Unassigned". The flags defined in this document may use either a single bit or multiple bits to represent a state, as determined by the specific requirements of the document defining them. IANA is requested to add subsequent blocks of 32 bits upon exhaustion of the preceding 32-bit block.

OSPFv3

OSPFv3 Prefix Attribute Flags Sub-TLV Registry This document requests IANA to make permanent the early allocation of the following codepoint for the "OSPFv3 Prefix Attribute Flags" in the "OSPFv3 Extended-LSA sub-TLVs" registry:

OSPFv3 Prefix Extended Flags Field Registry This document requests the creation of "OSPFv3 Prefix Extended Flag Field" registry under "Open Shortest Path First v3 (OSPFv3)" registry group. The registry defines the bits in the Prefix Attribute Flags field in the OSPFv2 Prefix Attribute Flags sub-TLV as specified in Section 2. The bits are to be allocated via IETF Review . Each bit definition will include: No bits are currently defined. Bits 0-31 are to be initially marked as "Unassigned". The flags defined in this document may use either a single bit or multiple bits to represent a state, as determined by the specific requirements of the document defining them. IANA is requested to add subsequent blocks of 32 bits upon exhaustion of the preceding 32-bit block.

Security Considerations Procedures and protocol extensions defined in this document do not affect the OSPFv2 or OSPFv3 security models. See the "Security Considerations" Section of for a discussion of OSPFv2 TLV-encoding considerations, and the "Security Considerations" Section of for a discussion of OSPFv3 security.