< draft-acee-ospfv3-lsa-extend-01.txt   draft-acee-ospfv3-lsa-extend-02.txt >
Network Working Group A. Lindem Network Working Group A. Lindem
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track S. Mirtorabi Intended status: Standards Track S. Mirtorabi
Expires: January 16, 2014 A. Roy Expires: March 14, 2014 A. Roy
F. Baker F. Baker
Cisco Systems Cisco Systems
July 15, 2013 September 10, 2013
OSPFv3 LSA Extendibility OSPFv3 LSA Extendibility
draft-acee-ospfv3-lsa-extend-01.txt draft-acee-ospfv3-lsa-extend-02.txt
Abstract Abstract
OSPFv3 requires functional extension beyond what can be done with the OSPFv3 requires functional extension beyond what can readily be done
fixed Link State Advertisement (LSA) format as described in RFC 5340. with the fixed-format Link State Advertisement (LSA) as described in
This document extends the LSA format by allowing the optional RFC 5340. Without LSA extension, attributes associated with OSPFv3
inclusion of Type-Length-Value (TLV) tuples in the LSAs. It also links and advertised IPv6 prefixes must be advertised in separate
covers all aspects of backward compatibility. LSAs and correlated to the fixed-format LSA. This document extends
the LSA format by allowing the optional inclusion of Type-Length-
Value (TLV) tuples in the LSAs. Backward compatibility mechanisms
are also described.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 16, 2014. This Internet-Draft will expire on March 14, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 22 skipping to change at page 3, line 7
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3 1.1. Requirements notation . . . . . . . . . . . . . . . . . . 4
1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3 1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 4
2. OSPFv3 Extended LSA Types . . . . . . . . . . . . . . . . . . 4 2. OSPFv3 Extended LSA Types . . . . . . . . . . . . . . . . . . 6
3. OSPFv3 Extended LSA TLV . . . . . . . . . . . . . . . . . . . 5 3. OSPFv3 Extended LSA TLV . . . . . . . . . . . . . . . . . . . 7
4. OSPFv3 E-Router-LSA . . . . . . . . . . . . . . . . . . . . . 6 4. OSPFv3 E-Router-LSA . . . . . . . . . . . . . . . . . . . . . 8
5. OSPFv3 E-Network-LSA . . . . . . . . . . . . . . . . . . . . . 8 5. OSPFv3 E-Network-LSA . . . . . . . . . . . . . . . . . . . . . 10
6. OSPFv3 E-Inter-Area-Prefix-LSA . . . . . . . . . . . . . . . . 10 6. OSPFv3 E-Inter-Area-Prefix-LSA . . . . . . . . . . . . . . . . 12
7. OSPFv3 E-Inter-Area-Router-LSA . . . . . . . . . . . . . . . . 12 7. OSPFv3 E-Inter-Area-Router-LSA . . . . . . . . . . . . . . . . 14
8. OSPFv3 E-AS-External-LSA . . . . . . . . . . . . . . . . . . . 14 8. OSPFv3 E-AS-External-LSA . . . . . . . . . . . . . . . . . . . 16
9. OSPFv3 E-NSSA-LSA . . . . . . . . . . . . . . . . . . . . . . 16 9. OSPFv3 E-NSSA-LSA . . . . . . . . . . . . . . . . . . . . . . 18
10. OSPFv3 E-Link-LSA . . . . . . . . . . . . . . . . . . . . . . 17 10. OSPFv3 E-Link-LSA . . . . . . . . . . . . . . . . . . . . . . 19
11. OSPFv3 E-Intra-Area-Prefix-LSA . . . . . . . . . . . . . . . . 20 11. OSPFv3 E-Intra-Area-Prefix-LSA . . . . . . . . . . . . . . . . 22
12. LSA Extension Backward Compatibility . . . . . . . . . . . . . 21 12. LSA Extension Backward Compatibility . . . . . . . . . . . . . 23
12.1. Extended LSA Mixed-Mode Backward Compatibility . . . . . . 22 12.1. Extended LSA Mixed-Mode Backward Compatibility . . . . . . 24
12.2. LSA TLV Processing Backward Compatibility . . . . . . . . 22 12.2. LSA TLV Processing Backward Compatibility . . . . . . . . 24
13. Security Considerations . . . . . . . . . . . . . . . . . . . 23 13. Security Considerations . . . . . . . . . . . . . . . . . . . 25
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27
15.1. Normative References . . . . . . . . . . . . . . . . . . . 25 15.1. Normative References . . . . . . . . . . . . . . . . . . . 27
15.2. Informative References . . . . . . . . . . . . . . . . . . 25 15.2. Informative References . . . . . . . . . . . . . . . . . . 27
Appendix A. Configurable Constants . . . . . . . . . . . . . . . 26 Appendix A. Configurable Constants . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29
1. Introduction 1. Introduction
OSPFv3 requires functional extension beyond what can be done with the OSPFv3 requires functional extension beyond what can readily be done
fixed Link State Advertisement (LSA) format as described in RFC 5340 with the fixed-format Link State Advertisement (LSA) as described in
[OSPFV3]. This document extends the LSA format by allowing the RFC 5340 [OSPFV3]. Without LSA extension, attributes associated with
optional inclusion of Type-Length-Value (TLV) tuples in the LSAs. OSPFv3 links and advertised IPv6 prefixes must be advertised in
Backward compatibility mechanisms are also described. separate LSAs and correlated to the fixed-format LSA. This document
extends the LSA format by allowing the optional inclusion of Type-
Length-Value (TLV) tuples in the LSAs. Backward compatibility
mechanisms are also described.
A similar extension was previously proposed in support of multi- A similar extension was previously proposed in support of multi-
topology routing. Additional requirements for OSPFv3 LSA extension topology routing. Additional requirements for OSPFv3 LSA extension
include source/destination routing, route tagging, and others. include source/destination routing, route tagging, and others.
A final requirement is to limit the changes to OSPFv3 to those A final requirement is to limit the changes to OSPFv3 to those
necessary for TLV-based LSAs. For the most part, the semantics of necessary for TLV-based LSAs. For the most part, the semantics of
existing OSPFv3 LSA are retained for their TLV-based successor LSAs existing OSPFv3 LSA are retained for their TLV-based successor LSAs
described herein. Additionally, encoding details, e.g., the described herein. Additionally, encoding details, e.g., the
representation of IPv6 prefixes as described in section A.4.1 in RFC representation of IPv6 prefixes as described in section A.4.1 in RFC
skipping to change at page 3, line 44 skipping to change at page 4, line 47
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC-KEYWORDS]. document are to be interpreted as described in [RFC-KEYWORDS].
1.2. Acknowledgments 1.2. Acknowledgments
OSPFv3 TLV-based LSAs were first proposed in "Multi-topology routing OSPFv3 TLV-based LSAs were first proposed in "Multi-topology routing
in OSPFv3 (MT-OSPFv3)" [MT-OSPFV3]. in OSPFv3 (MT-OSPFv3)" [MT-OSPFV3].
Thanks go to Michael Barnes, Peter Psenak, Mike Dubrovskiy, and Anton Thanks for Peter Psenak for significant contributions to the backward
Smirnov for review of the initial draft version and discussions of compatibility mechanisms.
backward compatibility.
Thanks go to Michael Barnes, Mike Dubrovsky, and Anton Smirnov for
review of the draft versions and discussions of backward
compatibility.
The RFC text was produced using Marshall Rose's xml2rfc tool. The RFC text was produced using Marshall Rose's xml2rfc tool.
2. OSPFv3 Extended LSA Types 2. OSPFv3 Extended LSA Types
In order to provide backward compatibility, new LSA codes must be In order to provide backward compatibility, new LSA codes must be
allocated. There are eight fixed format TLVs defined in RFC 5340 allocated. There are eight fixed-format LSAs defined in RFC 5340
[OSPFV3]. For ease of implementation and debugging, the LSA function [OSPFV3]. For ease of implementation and debugging, the LSA function
codes are the same as the fixed-format LSAs only with 32, i.e., 0x20, codes are the same as the fixed-format LSAs only with 32, i.e., 0x20,
added. The alternative was to allocate a bit in the LSA Type added. The alternative was to allocate a bit in the LSA Type
indicating the new LSA format. However, this would have used one indicating the new LSA format. However, this would have used one
half the LSA function code space for the migration of the eight half the LSA function code space for the migration of the eight
original fixed format LSAs. original fixed-format LSAs. For backward compatibility, the U-bit
will be set in LS Type so that the LSAs will be flooded by OSPFv3
routers that do not understand them.
LSA function code LS Type Description LSA function code LS Type Description
---------------------------------------------------- ----------------------------------------------------
33 0x2021 E-Router-LSA 33 0xA021 E-Router-LSA
34 0x2022 E-Network-LSA 34 0xA022 E-Network-LSA
35 0x2023 E-Inter-Area-Prefix-LSA 35 0xA023 E-Inter-Area-Prefix-LSA
36 0x2024 E-Inter-Area-Router-LSA 36 0xA024 E-Inter-Area-Router-LSA
37 0x4025 E-AS-External-LSA 37 0xC025 E-AS-External-LSA
38 N/A Unused (Not to be allocated) 38 N/A Unused (Not to be allocated)
39 0x2027 E-Type-7-LSA 39 0xA027 E-Type-7-LSA
40 0x0028 E-Link-LSA 40 0x8028 E-Link-LSA
41 0x2029 E-Intra-Area-Prefix-LSA 41 0xA029 E-Intra-Area-Prefix-LSA
OSPFv3 Extended LSA Types OSPFv3 Extended LSA Types
3. OSPFv3 Extended LSA TLV 3. OSPFv3 Extended LSA TLV
The format of the TLVs within the body of the extended LSAs is the The format of the TLVs within the body of the extended LSAs is the
same as the format used by the Traffic Engineering Extensions to OSPF same as the format used by the Traffic Engineering Extensions to OSPF
[TE]. The variable TLV section consists of one or more nested Type/ [TE]. The variable TLV section consists of one or more nested Type/
Length/Value (TLV) tuples. The format of each TLV is: Length/Value (TLV) tuples. The format of each TLV is:
skipping to change at page 6, line 7 skipping to change at page 8, line 7
(thus a TLV with no value portion would have a length of 0). The TLV (thus a TLV with no value portion would have a length of 0). The TLV
is padded to 4-octet alignment; padding is not included in the length is padded to 4-octet alignment; padding is not included in the length
field (so a 3-octet value would have a length of 3, but the total field (so a 3-octet value would have a length of 3, but the total
size of the TLV would be 8 octets). Nested TLVs are also 32-bit size of the TLV would be 8 octets). Nested TLVs are also 32-bit
aligned. For example, a 1-byte value would have the length field set aligned. For example, a 1-byte value would have the length field set
to 1, and 3 octets of padding would be added to the end of the value to 1, and 3 octets of padding would be added to the end of the value
portion of the TLV. Unrecognized types are ignored. portion of the TLV. Unrecognized types are ignored.
4. OSPFv3 E-Router-LSA 4. OSPFv3 E-Router-LSA
The E-Router-LSA has an LS Type of 0x2021 and has the same base The E-Router-LSA has an LS Type of 0xA021 and has the same base
information content as the Router-LSA, section 4.4.3.2 in [OSPFV3]. information content as the Router-LSA, section 4.4.3.2 in [OSPFV3].
However, unlike the existing Router-LSA, it is fully extendable and However, unlike the existing Router-LSA, it is fully extendable and
represented as TLVs. represented as TLVs.
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
+-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Age |0|0|1| 0x21 | | LS Age |1|0|1| 0x21 |
+-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID | | Link State ID |
+-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Sequence Number | | LS Sequence Number |
+-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Checksum | Length | | LS Checksum | Length |
+-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 |Nt|x|V|E|B| Options | | 0 |Nt|x|V|E|B| Options |
skipping to change at page 8, line 7 skipping to change at page 10, line 7
Router-Link TLV Router-Link TLV
Like the existing Router-LSA, the LSA length is used to determine the Like the existing Router-LSA, the LSA length is used to determine the
end of the LSA including TLVs. The Router-Link TLV is only end of the LSA including TLVs. The Router-Link TLV is only
applicable to the E-Router-LSA. Inclusion in other Extended LSAs applicable to the E-Router-LSA. Inclusion in other Extended LSAs
MUST be ignored. MUST be ignored.
5. OSPFv3 E-Network-LSA 5. OSPFv3 E-Network-LSA
The E-Network-LSA has an LS Type of 0x2022 and has the same base The E-Network-LSA has an LS Type of 0xA022 and has the same base
information content as the Network-LSA, section 4.4.3.3 in [OSPFV3]. information content as the Network-LSA, section 4.4.3.3 in [OSPFV3].
However, unlike the existing Network-LSA, it is fully extendable and However, unlike the existing Network-LSA, it is fully extendable and
represented as TLVs. represented as TLVs.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Age |0|0|1| 0x22 | | LS Age |1|0|1| 0x22 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID | | Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Sequence Number | | LS Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Checksum | Length | | LS Checksum | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | Options | | 0 | Options |
skipping to change at page 10, line 7 skipping to change at page 12, line 7
likelihood of the size of the E-Network-LSA requiring IPv6 likelihood of the size of the E-Network-LSA requiring IPv6
fragmentation when advertised in an OSPFv3 Link State Update packet. fragmentation when advertised in an OSPFv3 Link State Update packet.
Like the existing Network-LSA, the LSA length is used to determine Like the existing Network-LSA, the LSA length is used to determine
the end of the LSA including TLVs. The Attached-Routers TLV is only the end of the LSA including TLVs. The Attached-Routers TLV is only
applicable to the E-Network-LSA. Inclusion in other Extended LSAs applicable to the E-Network-LSA. Inclusion in other Extended LSAs
MUST be ignored. MUST be ignored.
6. OSPFv3 E-Inter-Area-Prefix-LSA 6. OSPFv3 E-Inter-Area-Prefix-LSA
The E-Inter-Area-Prefix-LSA has an LS Type of 0x2023 and has the same The E-Inter-Area-Prefix-LSA has an LS Type of 0xA023 and has the same
base information content as the Inter-Area-Prefix-LSA, section base information content as the Inter-Area-Prefix-LSA, section
4.4.3.4 in [OSPFV3]. However, unlike the existing Inter-Area-Prefix- 4.4.3.4 in [OSPFV3]. However, unlike the existing Inter-Area-Prefix-
LSA, it is fully extendable and represented as TLVs. LSA, it is fully extendable and represented as TLVs.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Age |0|0|1| 0x23 | | LS Age |1|0|1| 0x23 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID | | Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Sequence Number | | LS Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Checksum | Length | | LS Checksum | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
skipping to change at page 12, line 7 skipping to change at page 14, line 7
Prefix TLV. This will facilitate migration and avoid changes to Prefix TLV. This will facilitate migration and avoid changes to
functions such as incremental SPF computation. functions such as incremental SPF computation.
Like the existing Inter-Area-Prefix-LSA, the LSA length is used to Like the existing Inter-Area-Prefix-LSA, the LSA length is used to
determine the end of the LSA including TLV. The Inter-Area-Prefix determine the end of the LSA including TLV. The Inter-Area-Prefix
TLV is only applicable to the E-Inter-Area-Prefix-LSA. Inclusion in TLV is only applicable to the E-Inter-Area-Prefix-LSA. Inclusion in
other Extended LSAs MUST be ignored. other Extended LSAs MUST be ignored.
7. OSPFv3 E-Inter-Area-Router-LSA 7. OSPFv3 E-Inter-Area-Router-LSA
The E-Inter-Area-Router-LSA has an LS Type of 0x2024 and has the same The E-Inter-Area-Router-LSA has an LS Type of 0xA024 and has the same
base information content as the Inter-Area-Router-LSA, section base information content as the Inter-Area-Router-LSA, section
4.4.3.5 in [OSPFV3]. However, unlike the Inter-Area-Router-LSA, it 4.4.3.5 in [OSPFV3]. However, unlike the Inter-Area-Router-LSA, it
is fully extendable and represented as TLVs. is fully extendable and represented as TLVs.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Age |0|0|1| 0x24 | | LS Age |1|0|1| 0x24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID | | Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Sequence Number | | LS Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Checksum | Length | | LS Checksum | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
skipping to change at page 14, line 7 skipping to change at page 16, line 7
Router TLV. This will facilitate migration and avoid changes to Router TLV. This will facilitate migration and avoid changes to
functions such as incremental SPF computation. functions such as incremental SPF computation.
Like the existing Inter-Area-Router-LSA, the LSA length is used to Like the existing Inter-Area-Router-LSA, the LSA length is used to
determine the end of the LSA including sub-TLVs. The Inter-Area- determine the end of the LSA including sub-TLVs. The Inter-Area-
Router TLV is only applicable to the E-Inter-Area-Router-LSA. Router TLV is only applicable to the E-Inter-Area-Router-LSA.
Inclusion in other Extended LSAs MUST be ignored. Inclusion in other Extended LSAs MUST be ignored.
8. OSPFv3 E-AS-External-LSA 8. OSPFv3 E-AS-External-LSA
The E-AS-External-LSA has an LS Type of 0x4025 and has the same base The E-AS-External-LSA has an LS Type of 0xC025 and has the same base
information content as the AS-External-LSA, section 4.4.3.6 in information content as the AS-External-LSA, section 4.4.3.6 in
[OSPFV3]. However, unlike the existing AS-External-LSA, it is fully [OSPFV3]. However, unlike the existing AS-External-LSA, it is fully
extendable and represented as TLVs. extendable and represented as TLVs.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Age |0|1|0| 0x25 | | LS Age |1|1|0| 0x25 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID | | Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Sequence Number | | LS Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Checksum | Length | | LS Checksum | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
skipping to change at page 16, line 10 skipping to change at page 18, line 10
Like the existing AS-External-LSA, the LSA length is used to Like the existing AS-External-LSA, the LSA length is used to
determine the end of the LSA including sub-TLVs. The External-Prefix determine the end of the LSA including sub-TLVs. The External-Prefix
TLV is only applicable to the E-AS-External-LSA and the E-NSSA-LSA. TLV is only applicable to the E-AS-External-LSA and the E-NSSA-LSA.
Inclusion in other Extended LSAs MUST be ignored. Inclusion in other Extended LSAs MUST be ignored.
9. OSPFv3 E-NSSA-LSA 9. OSPFv3 E-NSSA-LSA
The E-NSSA-LSA will have the same format and TLVs as the Extended AS- The E-NSSA-LSA will have the same format and TLVs as the Extended AS-
External-LSA Section 8. This is the same relationship as exists External-LSA Section 8. This is the same relationship as exists
between the NSSA-LSA, section 4.4.3.7 in [OSPFV3], and the AS- between the NSSA-LSA, section 4.4.3.7 in [OSPFV3], and the AS-
External-LSA. The NSSA-LSA will have type 0x2027 which implies area External-LSA. The NSSA-LSA will have type 0xA027 which implies area
flooding scope. Future requirements may dictate that supported TLVs flooding scope. Future requirements may dictate that supported TLVs
differ between the E-AS-External-LSA and the E-NSSA-TLV. However, differ between the E-AS-External-LSA and the E-NSSA-LSA. However,
future requirements are beyond the scope of this document. future requirements are beyond the scope of this document.
10. OSPFv3 E-Link-LSA 10. OSPFv3 E-Link-LSA
The E-Link-LSA has an LS Type of 0x0028 and will have the same base The E-Link-LSA has an LS Type of 0x8028 and will have the same base
information content as the Link-LSA, section 4.4.3.8 in [OSPFV3]. information content as the Link-LSA, section 4.4.3.8 in [OSPFV3].
However, unlike the existing Link-LFA, it is extendable and However, unlike the existing Link-LFA, it is extendable and
represented as TLVs. represented as TLVs.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Age |0|0|0| 0x28 | | LS Age |1|0|0| 0x28 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID | | Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Sequence Number | | LS Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Checksum | Length | | LS Checksum | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rtr Priority | Options | | Rtr Priority | Options |
skipping to change at page 20, line 7 skipping to change at page 22, line 7
LSAs MUST be ignored. Only a single instance of the IPv4 Link-Local LSAs MUST be ignored. Only a single instance of the IPv4 Link-Local
Address family SHOULD be included in the E-Link-LSA. Instances Address family SHOULD be included in the E-Link-LSA. Instances
preceding the first MUST be ignored. For IPv6 address families as preceding the first MUST be ignored. For IPv6 address families as
defined in [OSPFV3-AF]. Future specifications may support defined in [OSPFV3-AF]. Future specifications may support
advertisement of routing and topology information for multiple advertisement of routing and topology information for multiple
address families. However, this is beyond the scope of this address families. However, this is beyond the scope of this
document. document.
11. OSPFv3 E-Intra-Area-Prefix-LSA 11. OSPFv3 E-Intra-Area-Prefix-LSA
The E-Intra-Area-Prefix-LSA has an LS Type of 0x2029 and has the same The E-Intra-Area-Prefix-LSA has an LS Type of 0xA029 and has the same
base information content as the Intra-Area-Prefix-LSA, section base information content as the Intra-Area-Prefix-LSA, section
4.4.3.9 in [OSPFV3]. However, unlike the Intra-Area-Prefix-LSA, it 4.4.3.9 in [OSPFV3]. However, unlike the Intra-Area-Prefix-LSA, it
is fully extendable and represented as TLVs. is fully extendable and represented as TLVs.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Age |0|0|1| 0x29 | | LS Age |1|0|1| 0x29 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link State ID | | Link State ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router | | Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Sequence Number | | LS Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Checksum | Length | | LS Checksum | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | Referenced LS Type | | 0 | Referenced LS Type |
skipping to change at page 21, line 10 skipping to change at page 23, line 10
Like the Intra-Area-Prefix-LSA, the E-Intra-Area-Link-LSA affords Like the Intra-Area-Prefix-LSA, the E-Intra-Area-Link-LSA affords
advertisement of multiple intra-area prefixes. Hence, multiple advertisement of multiple intra-area prefixes. Hence, multiple
Intra-Area Prefix TLVs may be specified and the LSA length defines Intra-Area Prefix TLVs may be specified and the LSA length defines
the end of the LSA including all TLVs. the end of the LSA including all TLVs.
12. LSA Extension Backward Compatibility 12. LSA Extension Backward Compatibility
In the context of this document, backward compatibility is solely In the context of this document, backward compatibility is solely
related to the capability of an OSPFv3 router to receive, process, related to the capability of an OSPFv3 router to receive, process,
and originate the TLV-based LSAs defined herein. Backward and originate the TLV-based LSAs defined herein. Backward
compatility for future OSPFv3 extensions utilizing the TLV-based LSAs compatibility for future OSPFv3 extensions utilizing the TLV-based
is out of scope and must be covered in the documents describing those LSAs is out of scope and must be covered in the documents describing
extensions. Both full and, if applicable, partial deployment should those extensions. Both full and, if applicable, partial deployment
be covered for future OSPFv3 LSA extensions. should be covered for future OSPFv3 LSA extensions.
For simplicity and to avoid the scaling impact of maintaining both For simplicity and to avoid the scaling impact of maintaining both
TLV and non-TLV based versions of the same LSA within a routing TLV and non-TLV based versions of the same LSA within a routing
domain, the basic backward compatibility mode will not allow mixing domain, the basic backward compatibility mode will not allow mixing
of LSA formats. Different formats could still be supported with of LSA formats. Different formats could still be supported with
multiple OSPFv3 instances and separate OSPFv3 routing domains. multiple OSPFv3 instances and separate OSPFv3 routing domains.
Additionally, a more complex mode is provided in Section 12.1, where Additionally, a more complex mode is provided in Section 12.1, where
both formats of LSA coexist. An OSPFv3 instance will be configured both formats of LSA coexist. An OSPFv3 instance will be configured
to use either the Non-TLV-based LSAs, TLV-based LSAs, or support both to use either the Non-TLV-based LSAs, TLV-based LSAs, or support both
(Appendix A). In order to facilitate backward compatibility, the (Appendix A). In order to facilitate backward compatibility, the
OSPFv3 options field (as described in Appendix A.2 of RFC 5340 OSPFv3 options field (as described in Appendix A.2 of RFC 5340
[OSPFV3]), will contain an additional options bits. The EL-bit will [OSPFV3]), will contain an additional options bits. The EL-bit will
be used to indicate that the advertising OSPFv3 Router can receive, be used to indicate that the advertising OSPFv3 Router can receive,
process, and originate TLV-based LSAs. An OSPFv3 router configured process, and originate TLV-based LSAs. An OSPFv3 router configured
to support TLV-based LSAs WILL set its option field EL-bit in OSPFv3 to support TLV-based LSAs WILL set its option field EL-bit in OSPFv3
Hello and Database Description packets. If "Normal" is specified for Hello and Database Description packets. If "Normal" is specified for
ExtendedLSASupport, the OSPFv3 router MUST NOT form adjacencieswith ExtendedLSASupport, the OSPFv3 router MUST NOT form adjacencies with
OSPFv3 Routers sending OSPFv3 Hello and Database Description packets OSPFv3 Routers sending OSPFv3 Hello and Database Description packets
with the options field EL-bit clear. In this manner, OSPFv3 routing with the options field EL-bit clear. In this manner, OSPFv3 routing
domains utilizing the new encoding will be completely isolated from domains utilizing the new encoding will be completely isolated from
those using the RFC 5340 encodings. those using the RFC 5340 encodings.
1 2 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 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
+-+-+-+-+-+-+-+-+-+-+-+-+--+--+-+--+-+-+--+-+-+-+--+--+ +-+-+-+-+-+-+-+-+-+-+-+-+--+--+-+--+-+-+--+-+-+-+--+--+
| | | | | | | | | | | | |EL|AT|L|AF|*|*|DC|R|N|x| E|V6| | | | | | | | | | | | | |EL|AT|L|AF|*|*|DC|R|N|x| E|V6|
+-+-+-+-+-+-+-+-+-+-+-+-+--+--+-+--+-+-+--+-+-+-+--+--+ +-+-+-+-+-+-+-+-+-+-+-+-+--+--+-+--+-+-+--+-+-+-+--+--+
skipping to change at page 22, line 10 skipping to change at page 24, line 10
supports the Extended LSA format with the bit set condition supports the Extended LSA format with the bit set condition
indicating support. indicating support.
Options Field EL-bit Options Field EL-bit
12.1. Extended LSA Mixed-Mode Backward Compatibility 12.1. Extended LSA Mixed-Mode Backward Compatibility
An implementation MAY support configuration allowing a mixture of An implementation MAY support configuration allowing a mixture of
OSPFv3 routers supporting and not supporting TLV-based LSAs in the OSPFv3 routers supporting and not supporting TLV-based LSAs in the
same OSPFv3 routing domain. In these deployments, the OSPFv3 routers same OSPFv3 routing domain. In these deployments, the OSPFv3 routers
configured with a value of MixedMode for ExtendedLSASupport, configured with a value of MixedMode or MixedModeDegraded for
(Appendix A), MUST originate both the TLV-based and non-TLV-based ExtendedLSASupport, (Appendix A), MUST originate both the TLV-based
versions of the OSPFv3 LSAs described herein. For the purposes of and non-TLV-based versions of the OSPFv3 LSAs described herein. For
Shortest Path First (SPF) computation, the TLV-based LSAs MUST be the purposes of Shortest Path First (SPF) computation, if the
used by OSPFv3 routers supporting this specification. OSPFv3 routers configured value is MixedMode, the TLV-based LSAs MUST be used by
configured for mixed mode operation also MUST form adjacencies with OSPFv3 routers supporting this specification. If MixedModeDegraded
OSPFv3 Routers sending OSPFv3 Hello and Database Description packets is configured, the non-TLV-based versions of the OSPFv3 LSAs are used
with the options field EL-bit clear. In this manner, OSPFv3 routing for SPF computation. OSPFv3 routers configured for mixed mode
domains utilizing the new encodings can be gradually migrated with a operation also MUST form adjacencies with OSPFv3 Routers sending
worst case cost of approximately doubling the number of LSAs in the OSPFv3 Hello and Database Description packets with the options field
routing domain. EL-bit clear. In this manner, OSPFv3 routing domains utilizing the
new encodings can be gradually migrated with a worst-case cost of
approximately doubling the number of LSAs in the routing domain.
12.2. LSA TLV Processing Backward Compatibility 12.2. LSA TLV Processing Backward Compatibility
This section defines the general rules for processing LSA TLVs. To This section defines the general rules for processing LSA TLVs. To
ensure compatibility of future TLV-based LSA extensions, all ensure compatibility of future TLV-based LSA extensions, all
implementations MUST adhere to these rules: implementations MUST adhere to these rules:
1. Unrecognized TLVs and sub-TLVs are ignored when parsing or 1. Unrecognized TLVs and sub-TLVs are ignored when parsing or
processing Extended-LSAs. processing Extended-LSAs.
skipping to change at page 23, line 7 skipping to change at page 25, line 7
3. If partial deployment is not supported, mechanisms to ensure the 3. If partial deployment is not supported, mechanisms to ensure the
corresponding feature are not deployed MUST be specified in the corresponding feature are not deployed MUST be specified in the
document defining the new TLV or sub-TLV. document defining the new TLV or sub-TLV.
4. If partial deployment is supported, backward compatibility and 4. If partial deployment is supported, backward compatibility and
partial deployment MUST be specified in the document defining the partial deployment MUST be specified in the document defining the
new TLV or sub-TLV. new TLV or sub-TLV.
13. Security Considerations 13. Security Considerations
Extendible OSPFv3 LSAs do not introduce any new security concerns In general, extendible OSPFv3 LSAs are subject to the same security
beyond those described in RFC 5340 [OSPFV3]. concerns as those described in RFC 5340 [OSPFV3]. Additionally,
implementations must assure that malformed TLV and Sub-TLV
permutations do not result in errors which cause hard OSPFv3
failures.
If there were ever a requirement to digitally sign OSPFv3 LSAs as
described for OSPFv2 LSAs in RFC 2154 [OSPF-DIGITAL-SIGNATURE], the
mechanisms described herein would greatly simplify the extension.
14. IANA Considerations 14. IANA Considerations
This specification defines nine OSPFv3 Extended LSA types as This specification defines nine OSPFv3 Extended LSA types as
described in Section 2. described in Section 2.
This specification also creates two registries OSPFv3 Extended-LSAs This specification also creates two registries OSPFv3 Extended-LSAs
TLVs and sub-TLVs. The TLV and Sub-TLV code-points in these TLVs and sub-TLVs. The TLV and Sub-TLV code-points in these
registries are common to all Extended-LSAs and their respective registries are common to all Extended-LSAs and their respective
definitions must define where they are applicable. definitions must define where they are applicable.
skipping to change at page 25, line 27 skipping to change at page 27, line 27
[RFC-KEYWORDS] [RFC-KEYWORDS]
Bradner, S., "Key words for use in RFCs to Indicate Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering [TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering
Extensions to OSPF", RFC 3630, September 2003. Extensions to OSPF", RFC 3630, September 2003.
15.2. Informative References 15.2. Informative References
[MT-OSPFV3] [MT-OSPFV3]
Mirtorabi, S. and A. Roy, "Multi-toplogy routing in OSPFv3 Mirtorabi, S. and A. Roy, "Multi-topology routing in
(MT-OSPFV3)", draft-ietf-ospf-mt-ospfv3-04.txt (work in OSPFv3 (MT-OSPFV3)", draft-ietf-ospf-mt-ospfv3-04.txt
progress). (work in progress).
[OSPF-DIGITAL-SIGNATURE]
Murphy, S., Badger, M., and B. Wellington, "OSPF with
Digital Signatures", RFC 2154, June 1997.
Appendix A. Configurable Constants Appendix A. Configurable Constants
An additional global configurable constant will be added to the An additional global configurable constant will be added to the
OSPFv3 protocol. OSPFv3 protocol.
ExtendedLSASupport ExtendedLSASupport
This is an enumeration type indicating the extent to which the This is an enumeration type indicating the extent to which the
OSPFv3 instance supports the TLV format described herein for OSPFv3 instance supports the TLV format described herein for
Extended LSAs. The valid value for the enumeration are: Extended LSAs. The valid value for the enumeration are:
* None - Non-extended LSAs will not be originated or used in the * None - Non-extended LSAs will not be originated or used in the
SPF calculation. SPF calculation.
* Normal - Extended LSAs will not be originated and adjacencies * Normal - Extended LSAs will be originated and adjacencies will
will not be formed with OSPFv3 routers not supporting this not be formed with OSPFv3 routers not supporting this
specification. specification.
* MixedMode - Both extended and non-extended LSAs will be * MixedMode - Both extended and non-extended LSAs will be
originated. OSPFv3 adjacencies will be formed with OSPFv3 originated. OSPFv3 adjacencies will be formed with OSPFv3
routers not supporting this specification. routers not supporting this specification. The extended LSAs
are used for the SPF computation.
* MixedModeDegraded - Both extended and non-extended LSAs will be
originated. OSPFv3 adjacencies will be formed with OSPFv3
routers not supporting this specification. The non-extended
LSAs are used for the SPF computation.
Authors' Addresses Authors' Addresses
Acee Lindem Acee Lindem
Ericsson Ericsson
102 Carric Bend Court 301 Midenhall Way
Cary, NC 27519 Cary, NC 27513
USA USA
Email: acee.lindem@ericsson.com Email: acee.lindem@ericsson.com
Sina Mirtorabi Sina Mirtorabi
Cisco Systems Cisco Systems
170 Tasman Drive 170 Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
 End of changes. 36 change blocks. 
92 lines changed or deleted 122 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/