rfc9792.original   rfc9792.txt 
LSR R. Chen Internet Engineering Task Force (IETF) R. Chen
Internet-Draft D. Zhao Request for Comments: 9792 D. Zhao
Intended status: Standards Track ZTE Corporation Category: Standards Track ZTE Corporation
Expires: 10 October 2025 P. Psenak ISSN: 2070-1721 P. Psenak
K. Talaulikar K. Talaulikar
Cisco Systems Cisco Systems
L. Gong L. Gong
China mobile China mobile
8 April 2025 June 2025
Prefix Flag Extension for OSPFv2 and OSPFv3 Prefix Flag Extension for OSPFv2 and OSPFv3
draft-ietf-lsr-ospf-prefix-extended-flags-07
Abstract Abstract
Each OSPF prefix can be advertised with an 8-bit field to indicate Each OSPF prefix can be advertised with an 8-bit field to indicate
specific properties of that prefix. However, all the OSPFv3 Prefix specific properties of that prefix. However, all the OSPFv3 Prefix
Options bits have already been assigned and only a few bits remain Options bits have already been assigned, and only a few bits remain
unassigned in the flags field of the OSPFv2 Extended Prefix TLV. unassigned in the Flags field of the OSPFv2 Extended Prefix TLV.
This document solves this problem by defining variable-length Prefix This document solves this problem by defining a variable-length
Attribute Flags sub-TLV for OSPF. This sub-TLV is applicable to Prefix Extended Flags sub-TLV for OSPF. This sub-TLV is applicable
OSPFv2 and OSPFv3. to OSPFv2 and OSPFv3.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on 10 October 2025. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9792.
Copyright Notice Copyright Notice
Copyright (c) 2025 IETF Trust and the persons identified as the Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (https://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Revised BSD License text as to this document. Code Components extracted from this document must
described in Section 4.e of the Trust Legal Provisions and are include Revised BSD License text as described in Section 4.e of the
provided without warranty as described in the Revised BSD License. Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language
2. Variable-Length Prefix Attribute Flags Sub-TLV . . . . . . . 3 2. Variable-Length Prefix Extended Flags Sub-TLV
3. Backward Compatibility . . . . . . . . . . . . . . . . . . . 4 3. Backward Compatibility
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 4.1. OSPFv2
5.1. OSPFv2 . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.1.1. OSPFv2 Prefix Extended Flags Sub-TLV
5.1.1. OSPFv2 Prefix Attribute Flags Sub-TLV Registry . . . 5 4.1.2. OSPFv2 Prefix Extended Flags Registry
5.1.2. OSPFv2 Prefix Extended Flags Field Registry . . . . . 5 4.2. OSPFv3
5.2. OSPFv3 . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2.1. OSPFv3 Prefix Extended Flags Sub-TLV
5.2.1. OSPFv3 Prefix Attribute Flags Sub-TLV Registry . . . 6 4.2.2. OSPFv3 Prefix Extended Flags Registry
5.2.2. OSPFv3 Prefix Extended Flags Field Registry . . . . . 6 5. Security Considerations
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 6. References
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.1. Normative References
7.1. Normative References . . . . . . . . . . . . . . . . . . 6 6.2. Informative References
7.2. Informative References . . . . . . . . . . . . . . . . . 7 Acknowledgements
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses
1. Introduction 1. Introduction
Each OSPF prefix can be advertised with an 8-bit field to indicate Each OSPF prefix can be advertised with an 8-bit field to indicate
specific properties of that prefix. This is done using the OSPFv3 specific properties of that prefix. This is done using the OSPFv3
Prefix Options (Appendix A.4.1.1 of [RFC5340]) and the flags field in Prefix Options (Appendix A.4.1.1 of [RFC5340]) and the Flags field in
the OSPFv2 Extended Prefix TLV (Section 2.1 of [RFC7684]). The rest the OSPFv2 Extended Prefix TLV (Section 2.1 of [RFC7684]). The rest
of this document refers to these 8-bit fields in both OSPFv2 and of this document refers to these 8-bit fields in both OSPFv2 and
OSPFv3 as the "existing fixed-size prefix attribute flags". OSPFv3 as the "existing fixed-size prefix flags".
However, all the OSPFv3 Prefix Options bits have already been However, all the OSPFv3 Prefix Options bits have already been
assigned (see "OSPFv3 Prefix Options (8 bits)" IANA registry assigned (see the "OSPFv3 Prefix Options (8 bits)" IANA registry
[IANA-OSPFv3-PO]). Also, only 5 bits remain unassigned (at the time [IANA-OSPFv3-PO]). Also, at the time of publication of this
of publication of this document) in the Flags field of the OSPFv2 document, only 5 bits remain unassigned in the Flags field of the
Extended Prefix TLV (see "OSPFv2 Extended Prefix TLV Flags" IANA OSPFv2 Extended Prefix TLV (see the "OSPFv2 Extended Prefix TLV
registry [IANA-OSPFv2-EPF]). Flags" IANA registry [IANA-OSPFv2-EPF]).
This document solves the problem of insufficient flag bits for the This document solves the problem of insufficient flag bits for the
signaling of prefix properties in OSPF by defining variable-length signaling of prefix properties in OSPF by defining a variable-length
Prefix Attribute Flags sub-TLVs for OSPFv2 and OSPFv3. Prefix Extended Flags sub-TLV for OSPFv2 and OSPFv3.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in
14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. Variable-Length Prefix Attribute Flags Sub-TLV 2. Variable-Length Prefix Extended Flags Sub-TLV
This document defines variable-Length Prefix Attribute Flags sub-TLV This document defines a variable-length Prefix Extended Flags sub-TLV
for OSPFv2 and OSPFv3. Such sub-TLV specifies the variable-flag for OSPFv2 and OSPFv3. The sub-TLV specifies the variable-length
fields to advertise additional attributes associated with OSPF Prefix Extended Flags field to advertise additional attributes
prefixes. The advertisement and processing of the existing fixed- associated with OSPF prefixes. The advertisement and processing of
size prefix attribute flags remain unchanged. the existing fixed-size prefix flags remain unchanged.
The format of OSPFv2/OSPFv3 Prefix Attribute Flags sub-TLVs is shown The format of the OSPFv2/OSPFv3 Prefix Extended Flags sub-TLV is
in Figure 1. shown in Figure 1.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// Prefix Attribute Flags (Variable) // // Prefix Extended Flags (Variable) //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Format of OSPFv2/OSPFv3 Prefix Attribute Flags Sub-TLV Figure 1: Format of OSPFv2/OSPFv3 Prefix Extended Flags Sub-TLV
where: where:
Type (2 octets): 11 for OSPFv2 and 37 for OSPFv3. Type (2 octets): 11 for OSPFv2 and 37 for OSPFv3
Length (2 octets): Variable, dependent on the included Prefix Length (2 octets): Variable, dependent on the included Prefix
Attribute Flags. This indicates the length of the prefix attributes Extended Flags field. This indicates the length of the Prefix
flags in octets. The length MUST be a multiple of 4 octets. If the Extended Flags field in octets. The length MUST be a multiple of
length is not a multiple of 4 octets, the Link State Advertisement 4 octets. If the length is not a multiple of 4 octets, the Link
(LSA) is malformed and MUST be ignored. State Advertisement (LSA) is malformed and MUST be ignored.
Prefix Attribute Flags (Variable): The extended flag field. This Prefix Extended Flags (Variable): The extended flag field. This
field contains a variable number of flags, grouped in 4-octet blocks. field contains a variable number of flags, grouped in 4-octet
The bits are numbered starting from bit 0 as the most significant bit blocks. The bits are numbered starting from bit 0 as the most
of the first 32-bit block. If a Prefix Attribute Flags field's significant bit of the first 32-bit block. If the length of the
length exceeds 4 octets, numbering for the additional bits picks up Prefix Extended Flags field exceeds 4 octets, numbering for the
where the previous 4-octet block left off. For example, the most additional bits picks up where the previous 4-octet block left
significant bit in the fifth octet of an 8-octet Prefix Attribute off. For example, the most significant bit in the fifth octet of
Flags is referred to as bit 32. Currently, no bits are defined in an 8-octet Prefix Extended Flags field is referred to as bit 32.
this document. Currently, no bits are defined in this document.
Unassigned bits MUST be set to zero on transmission and MUST be Unassigned bits MUST be set to zero on transmission and MUST be
ignored on receipt. ignored on receipt.
An implementation MUST limit the length of the sub-TLV so as to 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 signal the bits that are set to 1. Defined prefix flags that are not
transmitted due to being beyond the transmitted length MUST be transmitted due to being beyond the transmitted length MUST be
treated as being set to 0. treated as being set to 0.
OSPFv2 Prefix Attribute Flags sub-TLV is advertised as a sub-TLV of The OSPFv2 Prefix Extended Flags sub-TLV is advertised as a sub-TLV
the OSPFv2 Extended Prefix TLV defined in [RFC7684]. Additional of the OSPFv2 Extended Prefix TLV defined in [RFC7684]. Additional
OSPFv2 prefix flags SHOULD be allocated from the unused bits in the OSPFv2 prefix flags SHOULD be allocated from the unused bits in the
Flags field of the OSPFv2 Extended Prefix TLV prior to allocating Flags field of the OSPFv2 Extended Prefix TLV prior to allocating
flags in the OSPFv2 Prefix Attribute Flags sub-TLV. flags in the OSPFv2 Prefix Extended Flags sub-TLV.
OSPFv3 Prefix Attribute Flags sub-TLV is advertised as a sub-TLV of The OSPFv3 Prefix Extended Flags sub-TLV is advertised as a sub-TLV
the following OSPFv3 TLVs: of the following OSPFv3 TLVs:
* Inter-Area-Prefix TLV (Section 3.4 of [RFC8362]). * Inter-Area-Prefix TLV (Section 3.4 of [RFC8362])
* External-Prefix TLV (Section 3.6 of [RFC8362]). * External-Prefix TLV (Section 3.6 of [RFC8362])
* Intra-Area-Prefix TLV (Section 3.7 of [RFC8362]). * Intra-Area-Prefix TLV (Section 3.7 of [RFC8362])
* SRv6 Locator TLV [RFC9513]. * SRv6 Locator TLV [RFC9513]
When multiple instances of the OSPFv2/OSPFv3 Prefix Attribute Flags When multiple instances of the OSPFv2/OSPFv3 Prefix Extended Flags
sub-TLVs are received within the same TLV, an implementation MUST use sub-TLVs are received within the same TLV, an implementation MUST use
only the first occurrence of the sub-TLV and MUST ignore all only the first occurrence of the sub-TLV and MUST ignore all
subsequent instances of the sub-TLV. Errors SHOULD be logged subject subsequent instances of the sub-TLV. Errors SHOULD be logged subject
to rate limiting. to rate limiting.
3. Backward Compatibility 3. Backward Compatibility
The Prefix Attribute Flags sub-TLV does not introduce any backward The OSPFv2/OSPFv3 Prefix Extended Flags sub-TLV does not introduce
compatibility issues. An implementation that does not recognize the any backward compatibility issues. An implementation that does not
OSPFv2/OSPFv3 Prefix Attribute Flags sub-TLV would ignore the sub-TLV recognize the OSPFv2/OSPFv3 Prefix Extended Flags sub-TLV would
as per normal TLV processing operations (refer Section 6.3 of ignore the sub-TLV as per normal TLV processing operations (refer to
[RFC3630] and Section 2.3.2 of [RFC8362]). Section 2.3.2 of [RFC3630] and Section 6.3 of [RFC8362]).
4. Acknowledgements
The authors thank Shraddha Hegde, Changwang Lin, Tom Petch and many 4. IANA Considerations
others for their suggestions and comments.
The authors would like to thank Acee Lindem for aligning the 4.1. OSPFv2
terminology with existing OSPF documents and for editorial
improvements.
5. IANA Considerations 4.1.1. OSPFv2 Prefix Extended Flags Sub-TLV
This document requests allocation for the following registries. IANA has allocated the following codepoint in the "OSPFv2 Extended
Prefix TLV Sub-TLVs" registry:
5.1. OSPFv2 +=======+==============================+===========+
| Value | Description | Reference |
+=======+==============================+===========+
| 11 | OSPFv2 Prefix Extended Flags | RFC 9792 |
+-------+------------------------------+-----------+
5.1.1. OSPFv2 Prefix Attribute Flags Sub-TLV Registry Table 1
This document requests IANA to make permanent the early allocation of 4.1.2. OSPFv2 Prefix Extended Flags Registry
the following codepoint for the "OSPFv2 Prefix Attribute Flags" in
the "OSPFv2 Extended Prefix TLV Sub-TLVs" registry to be made
permanent:
Value Description Reference IANA has created the "OSPFv2 Prefix Extended Flags" registry within
--------- ----------------------------------- --------------- the "Open Shortest Path First v2 (OSPFv2) Parameters" registry group.
11 OSPFv2 Prefix Attribute Flags RFC to be The registry defines the bits in the Prefix Extended Flags field in
the OSPFv2 Prefix Extended Flags sub-TLV as specified in Section 2.
The bits are to be allocated via IETF Review [RFC8126]. Each bit
definition will include:
5.1.2. OSPFv2 Prefix Extended Flags Field Registry * Bit number (counting from bit 0 as the most significant bit of the
first block)
This document requests the creation of "OSPFv2 Prefix Extended Flag * Description
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 [RFC8126]. Each bit definition will include:
* Bit number (counting from bit 0 as the most significant * Reference
bit of the first block)
* Description
* Reference
No bits are currently defined. Bits 0-31 are to be initially marked 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 as "Unassigned". The flags defined in this document may use either a
single bit or multiple bits to represent a state, as determined by single bit or multiple bits to represent a state, as determined by
the specific requirements of the document defining them. IANA is the specific requirements of the document defining them. IANA will
requested to add subsequent blocks of 32 bits upon exhaustion of the add subsequent blocks of 32 bits upon exhaustion of the preceding
preceding 32-bit block. 32-bit block.
5.2. OSPFv3 4.2. OSPFv3
5.2.1. OSPFv3 Prefix Attribute Flags Sub-TLV Registry 4.2.1. OSPFv3 Prefix Extended Flags Sub-TLV
This document requests IANA to make permanent the early allocation of IANA has allocated the following codepoint in the "OSPFv3 Extended-
the following codepoint for the "OSPFv3 Prefix Attribute Flags" in LSA Sub-TLVs" registry:
the "OSPFv3 Extended-LSA sub-TLVs" registry:
Value Description Reference +=======+==============================+======+===========+
-------- ---------------------------------- -------------- | Value | Description | L2BM | Reference |
37 OSPFv3 Prefix Attribute Flags RFC to be +=======+==============================+======+===========+
| 37 | OSPFv3 Prefix Extended Flags | X | RFC 9792 |
+-------+------------------------------+------+-----------+
5.2.2. OSPFv3 Prefix Extended Flags Field Registry Table 2
This document requests the creation of "OSPFv3 Prefix Extended Flag 4.2.2. OSPFv3 Prefix Extended Flags Registry
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 [RFC8126].
Each bit definition will include:
* Bit number (counting from bit 0 as the most significant IANA has created the "OSPFv3 Prefix Extended Flags" registry within
bit of the first block ) the "Open Shortest Path First v3 (OSPFv3) Parameters" registry group.
* Description The registry defines the bits in the Prefix Extended Flags field in
* Reference the OSPFv2 Prefix Extended Flags sub-TLV as specified in Section 2.
The bits are to be allocated via IETF Review [RFC8126]. Each bit
definition will include:
* Bit number (counting from bit 0 as the most significant bit of the
first block)
* Description
* Reference
No bits are currently defined. Bits 0-31 are to be initially marked 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 as "Unassigned". The flags defined in this document may use either a
single bit or multiple bits to represent a state, as determined by single bit or multiple bits to represent a state, as determined by
the specific requirements of the document defining them. IANA is the specific requirements of the document defining them. IANA will
requested to add subsequent blocks of 32 bits upon exhaustion of the add subsequent blocks of 32 bits upon exhaustion of the preceding
preceding 32-bit block. 32-bit block.
6. Security Considerations 5. Security Considerations
Procedures and protocol extensions defined in this document do not Procedures and protocol extensions defined in this document do not
affect the OSPFv2 or OSPFv3 security models. See the "Security affect the OSPFv2 or OSPFv3 security models. See Section 5 of
Considerations" Section of [RFC7684] for a discussion of OSPFv2 TLV- [RFC7684] for a discussion of OSPFv2 TLV-encoding considerations and
encoding considerations, and the "Security Considerations" Section of Section 7 of [RFC8362] for a discussion of OSPFv3 security.
[RFC8362] for a discussion of OSPFv3 security.
7. References 6. References
7.1. Normative References 6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, (TE) Extensions to OSPF Version 2", RFC 3630,
DOI 10.17487/RFC3630, September 2003, DOI 10.17487/RFC3630, September 2003,
<https://www.rfc-editor.org/info/rfc3630>. <https://www.rfc-editor.org/info/rfc3630>.
skipping to change at page 7, line 43 skipping to change at line 311
[RFC8362] Lindem, A., Roy, A., Goethals, D., Reddy Vallem, V., and [RFC8362] Lindem, A., Roy, A., Goethals, D., Reddy Vallem, V., and
F. Baker, "OSPFv3 Link State Advertisement (LSA) F. Baker, "OSPFv3 Link State Advertisement (LSA)
Extensibility", RFC 8362, DOI 10.17487/RFC8362, April Extensibility", RFC 8362, DOI 10.17487/RFC8362, April
2018, <https://www.rfc-editor.org/info/rfc8362>. 2018, <https://www.rfc-editor.org/info/rfc8362>.
[RFC9513] Li, Z., Hu, Z., Talaulikar, K., Ed., and P. Psenak, [RFC9513] Li, Z., Hu, Z., Talaulikar, K., Ed., and P. Psenak,
"OSPFv3 Extensions for Segment Routing over IPv6 (SRv6)", "OSPFv3 Extensions for Segment Routing over IPv6 (SRv6)",
RFC 9513, DOI 10.17487/RFC9513, December 2023, RFC 9513, DOI 10.17487/RFC9513, December 2023,
<https://www.rfc-editor.org/info/rfc9513>. <https://www.rfc-editor.org/info/rfc9513>.
7.2. Informative References 6.2. Informative References
[IANA-OSPFv2-EPF] [IANA-OSPFv2-EPF]
"OSPFv2 Extended Prefix TLV Flags", IANA, "OSPFv2 Extended Prefix TLV Flags",
<https://www.iana.org/assignments/ospfv2-parameters/ <https://www.iana.org/assignments/ospfv2-parameters>.
ospfv2-parameters.xhtml#extended-prefix-tlv-flags>.
[IANA-OSPFv3-PO] [IANA-OSPFv3-PO]
"OSPFv3 Prefix Options (8 bits)", IANA, "OSPFv3 Prefix Options (8 bits)",
<https://www.iana.org/assignments/ospfv3-parameters/ <https://www.iana.org/assignments/ospfv3-parameters>.
ospfv3-parameters.xhtml#ospfv3-parameters-4>.
Acknowledgements
The authors would like to thank Shraddha Hegde, Changwang Lin, Tom
Petch, and many others for their suggestions and comments.
The authors would also like to thank Acee Lindem for aligning the
terminology with existing OSPF documents and for editorial
improvements.
Authors' Addresses Authors' Addresses
Ran Chen Ran Chen
ZTE Corporation ZTE Corporation
Nanjing Nanjing
China China
Email: chen.ran@zte.com.cn Email: chen.ran@zte.com.cn
Detao Zhao Detao Zhao
ZTE Corporation ZTE Corporation
Nanjing Nanjing
China China
Email: zhao.detao@zte.com.cn Email: zhao.detao@zte.com.cn
Peter Psenak Peter Psenak
Cisco Systems Cisco Systems
Apollo Business Center Apollo Business Center
Mlynske nivy 43 Mlynske nivy 43
Bratislava 821 09 821 09 Bratislava
Slovakia Slovakia
Email: ppsenak@cisco.com Email: ppsenak@cisco.com
Ketan Talaulikar Ketan Talaulikar
Cisco Systems Cisco Systems
India India
Email: ketant.ietf@gmail.com Email: ketant.ietf@gmail.com
Liyan Gong Liyan Gong
China mobile China mobile
 End of changes. 60 change blocks. 
167 lines changed or deleted 168 lines changed or added

This html diff was produced by rfcdiff 1.48.