< draft-ietf-ospf-ospfv3-lsa-extend-05.txt   draft-ietf-ospf-ospfv3-lsa-extend-06.txt >
Network Working Group A. Lindem Network Working Group A. Lindem
Internet-Draft S. Mirtorabi Internet-Draft S. Mirtorabi
Intended status: Standards Track A. Roy Intended status: Standards Track A. Roy
Expires: May 28, 2015 F. Baker Expires: August 20, 2015 F. Baker
Cisco Systems Cisco Systems
November 24, 2014 February 16, 2015
OSPFv3 LSA Extendibility OSPFv3 LSA Extendibility
draft-ietf-ospf-ospfv3-lsa-extend-05.txt draft-ietf-ospf-ospfv3-lsa-extend-06.txt
Abstract Abstract
OSPFv3 requires functional extension beyond what can readily be done OSPFv3 requires functional extension beyond what can readily be done
with the fixed-format Link State Advertisement (LSA) as described in with the fixed-format Link State Advertisement (LSA) as described in
RFC 5340. Without LSA extension, attributes associated with OSPFv3 RFC 5340. Without LSA extension, attributes associated with OSPFv3
links and advertised IPv6 prefixes must be advertised in separate links and advertised IPv6 prefixes must be advertised in separate
LSAs and correlated to the fixed-format LSAs. This document extends LSAs and correlated to the fixed-format LSAs. This document extends
the LSA format by encoding the existing OSPFv3 LSA information in the LSA format by encoding the existing OSPFv3 LSA information in
Type-Length-Value (TLV) tuples and allowing advertisement of Type-Length-Value (TLV) tuples and allowing advertisement of
additional information with additional TLVs. Backward compatibility additional information with additional TLVs. Backward compatibility
mechanisms are also described. 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 May 28, 2015. This Internet-Draft will expire on August 20, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3 1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3
1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3 1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3
2. OSPFv3 Extended LSA Types . . . . . . . . . . . . . . . . . . 5 2. OSPFv3 Extended LSA Types . . . . . . . . . . . . . . . . . . 4
3. OSPFv3 Extended LSA TLVs . . . . . . . . . . . . . . . . . . . 6 3. OSPFv3 Extended LSA TLVs . . . . . . . . . . . . . . . . . . 5
3.1. Router-Link TLV . . . . . . . . . . . . . . . . . . . . . 7 3.1. Prefix Options Extensions . . . . . . . . . . . . . . . . 6
3.2. Attached-Routers TLV . . . . . . . . . . . . . . . . . . . 8 3.1.1. N-bit Prefix Option . . . . . . . . . . . . . . . . . 6
3.3. Inter-Area-Prefix TLV . . . . . . . . . . . . . . . . . . 9 3.2. Router-Link TLV . . . . . . . . . . . . . . . . . . . . . 7
3.4. Inter-Area-Router TLV . . . . . . . . . . . . . . . . . . 10 3.3. Attached-Routers TLV . . . . . . . . . . . . . . . . . . 7
3.5. External-Prefix TLV . . . . . . . . . . . . . . . . . . . 11 3.4. Inter-Area-Prefix TLV . . . . . . . . . . . . . . . . . . 9
3.6. Intra-Area-Prefix TLV . . . . . . . . . . . . . . . . . . 12 3.5. Inter-Area-Router TLV . . . . . . . . . . . . . . . . . . 10
3.7. IPv6 Link-Local Address TLV . . . . . . . . . . . . . . . 13 3.6. External-Prefix TLV . . . . . . . . . . . . . . . . . . . 11
3.8. IPv4 Link-Local Address TLV . . . . . . . . . . . . . . . 14 3.7. Intra-Area-Prefix TLV . . . . . . . . . . . . . . . . . . 12
3.9. IPv6-Forwarding-Address Sub-TLV . . . . . . . . . . . . . 15 3.8. IPv6 Link-Local Address TLV . . . . . . . . . . . . . . . 13
3.10. IPv4-Forwarding-Address Sub-TLV . . . . . . . . . . . . . 15 3.9. IPv4 Link-Local Address TLV . . . . . . . . . . . . . . . 14
3.11. Route-Tag Sub-TLV . . . . . . . . . . . . . . . . . . . . 16 3.10. IPv6-Forwarding-Address Sub-TLV . . . . . . . . . . . . . 15
4. OSPFv3 Extended LSAs . . . . . . . . . . . . . . . . . . . . . 17 3.11. IPv4-Forwarding-Address Sub-TLV . . . . . . . . . . . . . 15
4.1. OSPFv3 E-Router-LSA . . . . . . . . . . . . . . . . . . . 17 3.12. Route-Tag Sub-TLV . . . . . . . . . . . . . . . . . . . . 16
4.2. OSPFv3 E-Network-LSA . . . . . . . . . . . . . . . . . . . 18 4. OSPFv3 Extended LSAs . . . . . . . . . . . . . . . . . . . . 16
4.3. OSPFv3 E-Inter-Area-Prefix-LSA . . . . . . . . . . . . . . 19 4.1. OSPFv3 E-Router-LSA . . . . . . . . . . . . . . . . . . . 16
4.4. OSPFv3 E-Inter-Area-Router-LSA . . . . . . . . . . . . . . 20 4.2. OSPFv3 E-Network-LSA . . . . . . . . . . . . . . . . . . 18
4.5. OSPFv3 E-AS-External-LSA . . . . . . . . . . . . . . . . . 21 4.3. OSPFv3 E-Inter-Area-Prefix-LSA . . . . . . . . . . . . . 19
4.6. OSPFv3 E-NSSA-LSA . . . . . . . . . . . . . . . . . . . . 22 4.4. OSPFv3 E-Inter-Area-Router-LSA . . . . . . . . . . . . . 20
4.7. OSPFv3 E-Link-LSA . . . . . . . . . . . . . . . . . . . . 23 4.5. OSPFv3 E-AS-External-LSA . . . . . . . . . . . . . . . . 21
4.8. OSPFv3 E-Intra-Area-Prefix-LSA . . . . . . . . . . . . . . 25 4.6. OSPFv3 E-NSSA-LSA . . . . . . . . . . . . . . . . . . . . 22
5. Malformed OSPFv3 Extended LSA Handling . . . . . . . . . . . . 26 4.7. OSPFv3 E-Link-LSA . . . . . . . . . . . . . . . . . . . . 23
6. LSA Extension Backward Compatibility . . . . . . . . . . . . . 27 4.8. OSPFv3 E-Intra-Area-Prefix-LSA . . . . . . . . . . . . . 25
6.1. Extended LSA Mixed-Mode Backward Compatibility . . . . . . 28 5. Malformed OSPFv3 Extended LSA Handling . . . . . . . . . . . 25
6.1.1. Area Extended LSA Mixed-Mode Backward Compatibility . 29 6. LSA Extension Backward Compatibility . . . . . . . . . . . . 26
6.2. LSA TLV Processing Backward Compatibility . . . . . . . . 30 6.1. Extended LSA Mixed-Mode Backward Compatibility . . . . . 27
7. Security Considerations . . . . . . . . . . . . . . . . . . . 31 6.1.1. Area Extended LSA Mixed-Mode Backward Compatibility . 28
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 6.2. LSA TLV Processing Backward Compatibility . . . . . . . . 29
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33 7. Security Considerations . . . . . . . . . . . . . . . . . . . 29
9.1. Normative References . . . . . . . . . . . . . . . . . . . 33 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
9.2. Informative References . . . . . . . . . . . . . . . . . . 33 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 30
Appendix A. Global Configuration Parameters . . . . . . . . . . . 34 9.1. Normative References . . . . . . . . . . . . . . . . . . 30
Appendix B. Area Configuration Parameters . . . . . . . . . . . . 35 9.2. Informative References . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36 Appendix A. Global Configuration Parameters . . . . . . . . . . 31
Appendix B. Area Configuration Parameters . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
1. Introduction 1. Introduction
OSPFv3 requires functional extension beyond what can readily be done OSPFv3 requires functional extension beyond what can readily be done
with the fixed-format Link State Advertisement (LSA) as described in with the fixed-format Link State Advertisement (LSA) as described in
RFC 5340 [OSPFV3]. Without LSA extension, attributes associated with RFC 5340 [OSPFV3]. Without LSA extension, attributes associated with
OSPFv3 links and advertised IPv6 prefixes must be advertised in OSPFv3 links and advertised IPv6 prefixes must be advertised in
separate LSAs and correlated to the fixed-format LSAs. This document separate LSAs and correlated to the fixed-format LSAs. This document
extends the LSA format by encoding the existing OSPFv3 LSA extends the LSA format by encoding the existing OSPFv3 LSA
information in Type-Length-Value (TLV) tuples and allowing information in Type-Length-Value (TLV) tuples and allowing
skipping to change at page 6, line 9 skipping to change at page 5, line 9
39 0xA027 E-Type-7-LSA 39 0xA027 E-Type-7-LSA
40 0x8028 E-Link-LSA 40 0x8028 E-Link-LSA
41 0xA029 E-Intra-Area-Prefix-LSA 41 0xA029 E-Intra-Area-Prefix-LSA
OSPFv3 Extended LSA Types OSPFv3 Extended LSA Types
3. OSPFv3 Extended LSA TLVs 3. OSPFv3 Extended LSA TLVs
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
Length/Value (TLV) tuples. Nested TLVs are also referred to as sub- Type/Length/Value (TLV) tuples. Nested TLVs are also referred to as
TLVs. The format of each TLV is: sub-TLVs. The format of each TLV is:
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value... | | Value... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Format TLV Format
skipping to change at page 7, line 4 skipping to change at page 5, line 49
o 3 - Inter-Area Prefix TLV o 3 - Inter-Area Prefix TLV
o 4 - Inter-Area Router TLV o 4 - Inter-Area Router TLV
o 5 - External Prefix TLV o 5 - External Prefix TLV
o 6 - Intra-Area Prefix TLV o 6 - Intra-Area Prefix TLV
o 7 - IPv6 Link-Local Address TLV o 7 - IPv6 Link-Local Address TLV
o 8 - IPv4 Link-Local Address TLV
o 8 - IPv4 Link-Local Address TLV
Additionally, this document defines the following sub-TLV types: Additionally, this document defines the following sub-TLV types:
o 0 - Reserved o 0 - Reserved
o 1 - IPv6 Forwarding Address sub-TLV o 1 - IPv6 Forwarding Address sub-TLV
o 2 - IPv4 Forwarding Address sub-TLV o 2 - IPv4 Forwarding Address sub-TLV
o 3 - Route Tag sub-TLV o 3 - Route Tag sub-TLV
In general, TLVs and sub-TLVs MAY occur in any order and the In general, TLVs and sub-TLVs MAY occur in any order and the
specification should define whether the TLV or sub-TLV is required specification should define whether the TLV or sub-TLV is required
and the behavior when there are multiple occurances of the TLV or and the behavior when there are multiple occurances of the TLV or
sub-TLVs. sub-TLVs.
3.1. Router-Link TLV 3.1. Prefix Options Extensions
The prefix options are extended from Appendix A.4.1.1 [OSPFV3]. The
applicability of the LA-bit is expanded and it SHOULD be set in
Inter-Area-Prefix-TLVs and MAY be set in External-Prefix-TLVs when
the advertised host IPv6 address, i.e., PrefixLength = 128, is an
interface address. In RFC 5340, the LA-bit is only set in Intra-
Area-Prefix-LSAs (Section 4.4.3.9 in [OSPFV3]). This will allow a
stable address to be advertised without having to configure a
separate loopback address in every OSPFv3 area.
3.1.1. N-bit Prefix Option
Additionally, the N-bit prefix option is defined. The figure below
shows the position of the N-bit in the prefix options (pending IANA
allocation). This corresponds to the value 0x20.
0 1 2 3 4 5 6 7
+--+--+--+--+--+--+--+--+
| | | N|DN| P| x|LA|NU|
+--+--+--+--+--+--+--+--+
The Prefix Options field
The N-bit is set in PrefixOptions for a host address
(PrefixLength=128) that identifies the advertising router. While it
is similar to the LA-bit, there are two differences. The advertising
router MAY choose NOT to set the N-bit even when the above conditions
are met. If the N-bit is set and the PrefixLength is NOT 128, the
N-bit MUST be ignored. Additionally, the N-bit is propagated in the
PrefixOptions when an OSPFv3 Area Border Router (ABR) originates an
Inter-Area-Prefix-LSA for an Intra-Area route which has the N-bit set
in the PrefixOptions. Similarly, the N-bit is propagated in the
PrefixOptions when an OSPFv3 NSSA ABR originates an Extended-AS-
External-LSA corresponding to an NSSA route as described in section 3
of RFC 3101 ([NSSA]). The N-bit is to the Inter-Area-Prefix-TLV
(Section 3.4), External-Prefix-TLV (Section 3.6), and Intra-Area-
Prefix-TLV (Section 3.7) The N-bit is useful for applications such as
identifying the prefixes corresponding to Node Segment Identifiers
(SIDs) in Segment Routing [SEGMENT-ROUTING].
3.2. Router-Link TLV
The Router-Link TLV defines a single router link and the field The Router-Link TLV defines a single router link and the field
definitions correspond directly to links in the OSPFv3 Router-LSA, definitions correspond directly to links in the OSPFv3 Router-LSA,
section A.4.3, [OSPFV3]. The Router-Link TLV is only applicable to section A.4.3, [OSPFV3]. The Router-Link TLV is only applicable to
the E-Router-LSA (Section 4.1). Inclusion in other Extended LSAs the E-Router-LSA (Section 4.1). Inclusion in other Extended LSAs
MUST be ignored. MUST be ignored.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 8, line 5 skipping to change at page 7, line 42
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor Router ID | | Neighbor Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. sub-TLVs . . sub-TLVs .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Router-Link TLV Router-Link TLV
3.2. Attached-Routers TLV 3.3. Attached-Routers TLV
The Attached-Routers TLV defines all the routers attached to an The Attached-Routers TLV defines all the routers attached to an
OSPFv3 multi-access network. The field definitions correspond OSPFv3 multi-access network. The field definitions correspond
directly to content of the OSPFv3 Network-LSA, section A.4.4, directly to content of the OSPFv3 Network-LSA, section A.4.4,
[OSPFV3]. The Attached-Routers TLV is only applicable to the [OSPFV3]. The Attached-Routers TLV is only applicable to the E-
E-Network-LSA (Section 4.2). Inclusion in other Extended LSAs MUST Network-LSA (Section 4.2). Inclusion in other Extended LSAs MUST be
be ignored. ignored.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 (Attached-Routers) | TLV Length | | 2 (Attached-Routers) | TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Adjacent Neighbor Router ID | | Adjacent Neighbor Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. Additional Adjacent Neighbors . . Additional Adjacent Neighbors .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Attached-Routers TLV Attached-Routers TLV
There are two reasons for not having a separate TLV or sub-TLV for There are two reasons for not having a separate TLV or sub-TLV for
each adjacent neighbor. The first is to discourage using the each adjacent neighbor. The first is to discourage using the E-
E-Network-LSA for more than its current role of solely advertising Network-LSA for more than its current role of solely advertising the
the routers attached to a multi-access network. The router's metric routers attached to a multi-access network. The router's metric as
as well as the attributes of individual attached routers should be well as the attributes of individual attached routers should be
advertised in their respective E-Router-LSAs. The second reason is advertised in their respective E-Router-LSAs. The second reason is
that there is only a single E-Network-LSA per multi-access link with that there is only a single E-Network-LSA per multi-access link with
the Link State ID set to the Designated Router's Interface ID and, the Link State ID set to the Designated Router's Interface ID and,
consequently, compact encoding has been chosen to decrease the consequently, compact encoding has been chosen to decrease the
likelihood that the size of the E-Network-LSA will require IPv6 likelihood that the size of the E-Network-LSA will require IPv6
fragmentation when advertised in an OSPFv3 Link State Update packet. fragmentation when advertised in an OSPFv3 Link State Update packet.
3.3. Inter-Area-Prefix TLV 3.4. Inter-Area-Prefix TLV
The Inter-Area-Prefix TLV defines a single OSPFV3 inter-area prefix. The Inter-Area-Prefix TLV defines a single OSPFV3 inter-area prefix.
The field definitions correspond directly to the content of an OSPFv3 The field definitions correspond directly to the content of an OSPFv3
IPv6 Prefix as defined in Section A.4.1, [OSPFV3] and an OSPFv3 IPv6 Prefix as defined in Section A.4.1, [OSPFV3] and an OSPFv3
Inter-Area-Prefix-LSA, as defined in section A.4.5, [OSPFV3]. The Inter-Area-Prefix-LSA, as defined in section A.4.5, [OSPFV3].
Inter-Area-Prefix TLV is only applicable to the E-Inter-Area-Prefix- Additionally, the PrefixOptions are extended as described in
LSA (Section 4.3). Inclusion in other Extended LSAs MUST be ignored. Section 3.1. The Inter-Area-Prefix TLV is only applicable to the E-
Inter-Area-Prefix-LSA (Section 4.3). Inclusion in other Extended
LSAs MUST be ignored.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 3 (Inter-Area Prefix) | TLV Length | | 3 (Inter-Area Prefix) | TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | Metric | | 0 | Metric |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PrefixLength | PrefixOptions | 0 | | PrefixLength | PrefixOptions | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Prefix | | Address Prefix |
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. sub-TLVs . . sub-TLVs .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Inter-Area Prefix TLV Inter-Area Prefix TLV
3.4. Inter-Area-Router TLV 3.5. Inter-Area-Router TLV
The Inter-Area-Router TLV defines a single OSPFv3 Autonomous System The Inter-Area-Router TLV defines a single OSPFv3 Autonomous System
Boundary Router (ASBR) reachable in another area. The field Boundary Router (ASBR) reachable in another area. The field
definitions correspond directly to the content of an OSPFv3 Inter- definitions correspond directly to the content of an OSPFv3 Inter-
Area-Router-LSA, as defined in section A.4.6, [OSPFV3]. The Inter- Area-Router-LSA, as defined in section A.4.6, [OSPFV3]. The Inter-
Area-Router TLV is only applicable to the E-Inter-Area-Router-LSA Area-Router TLV is only applicable to the E-Inter-Area-Router-LSA
(Section 4.4). Inclusion in other Extended LSAs MUST be ignored. (Section 4.4). Inclusion in other Extended LSAs MUST be ignored.
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
skipping to change at page 11, line 5 skipping to change at page 11, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Router ID | | Destination Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. sub-TLVs . . sub-TLVs .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Inter-Area Router TLV Inter-Area Router TLV
3.5. External-Prefix TLV 3.6. External-Prefix TLV
The External-Prefix TLV defines a single OSPFv3 external prefix. The The External-Prefix TLV defines a single OSPFv3 external prefix. The
field definitions correspond directly to the content of an OSPFv3 field definitions correspond directly to the content of an OSPFv3
IPv6 Prefix as defined in Section A.4.1, [OSPFV3] and an OSPFv3 AS- IPv6 Prefix as defined in Section A.4.1, [OSPFV3] and an OSPFv3 AS-
External-LSA, as defined in section A.4.7, [OSPFV3]. The External- External-LSA, as defined in section A.4.7, [OSPFV3]. The External-
Prefix TLV is only applicable to the E-AS-External-LSA (Section 4.5) Prefix TLV is only applicable to the E-AS-External-LSA (Section 4.5)
and the E-NSSA-LSA (Section 4.6). Inclusion in other Extended LSAs and the E-NSSA-LSA (Section 4.6). Additionally, the PrefixOptions
MUST be ignored. are extended as described in Section 3.1. Inclusion in other
Extended LSAs MUST be ignored.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 (External Prefix) | TLV Length | | 5 (External Prefix) | TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |E| | | Metric | | |E| | | Metric |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PrefixLength | PrefixOptions | 0 | | PrefixLength | PrefixOptions | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Prefix | | Address Prefix |
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. sub-TLVs . . sub-TLVs .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
External Prefix TLV External Prefix TLV
skipping to change at page 11, line 44 skipping to change at page 11, line 45
In the External-Prefix TLV, the optional IPv6/IPv4 Forwarding Address In the External-Prefix TLV, the optional IPv6/IPv4 Forwarding Address
and External Route Tag are now sub-TLVs. Given the Referenced LS and External Route Tag are now sub-TLVs. Given the Referenced LS
type and Referenced Link State ID from the AS-External-LSA have never type and Referenced Link State ID from the AS-External-LSA have never
been used or even specified, they have been omitted from the External been used or even specified, they have been omitted from the External
Prefix TLV. If there were ever a requirement for a referenced LSA, Prefix TLV. If there were ever a requirement for a referenced LSA,
it could be satisfied with a sub-TLV. it could be satisfied with a sub-TLV.
The following sub-TLVs are defined for optional inclusion in the The following sub-TLVs are defined for optional inclusion in the
External Prefix TLV: External Prefix TLV:
o 1 - IPv6 Forwarding Address sub-TLV (Section 3.9) o 1 - IPv6 Forwarding Address sub-TLV (Section 3.10)
o 2 - IPv4 Forwarding Address sub-TLV (Section 3.10) o 2 - IPv4 Forwarding Address sub-TLV (Section 3.11)
o 3 - Route Tag sub-TLV (Section 3.11) o 3 - Route Tag sub-TLV (Section 3.12)
3.6. Intra-Area-Prefix TLV 3.7. Intra-Area-Prefix TLV
The Intra-Area-Prefix TLV defines a single OSPFv3 intra-area prefix. The Intra-Area-Prefix TLV defines a single OSPFv3 intra-area prefix.
The field definitions correspond directly to the content of an OSPFv3 The field definitions correspond directly to the content of an OSPFv3
IPv6 Prefix as defined in Section A.4.1, [OSPFV3] and an OSPFv3 Link- IPv6 Prefix as defined in Section A.4.1, [OSPFV3] and an OSPFv3 Link-
LSA, as defined in section A.4.9, [OSPFV3]. The Intra-Area-Prefix LSA, as defined in section A.4.9, [OSPFV3]. The Intra-Area-Prefix
TLV is only applicable to the E-Link-LSA (Section 4.7) and the TLV is only applicable to the E-Link-LSA (Section 4.7) and the
E-Intra-Area-Prefix-LSA (Section 4.8). Inclusion in other Extended Additionally, the PrefixOptions are extended as described in
LSAs MUST be ignored. Section 3.1. E-Intra-Area-Prefix-LSA (Section 4.8). Inclusion in
other Extended LSAs MUST be ignored.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 6 (Intra-Area Prefix) | TLV Length | | 6 (Intra-Area Prefix) | TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | Metric | | 0 | Metric |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PrefixLength | PrefixOptions | 0 | | PrefixLength | PrefixOptions | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Prefix | | Address Prefix |
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. sub-TLVs . . sub-TLVs .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Intra-Area Prefix TLV Intra-Area Prefix TLV
3.7. IPv6 Link-Local Address TLV 3.8. IPv6 Link-Local Address TLV
The IPv6 Link-Local Address TLV is to be used with IPv6 address The IPv6 Link-Local Address TLV is to be used with IPv6 address
families as defined in [OSPFV3-AF]. The IPv6 Link-Local Address TLV families as defined in [OSPFV3-AF]. The IPv6 Link-Local Address TLV
is only applicable to the E-Link-LSA (Section 4.7). Inclusion in is only applicable to the E-Link-LSA (Section 4.7). Inclusion in
other Extended LSAs MUST be ignored. other Extended LSAs MUST be ignored.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 7 (IPv6 Local-Local Address) | TLV Length | | 7 (IPv6 Local-Local Address) | TLV Length |
skipping to change at page 14, line 5 skipping to change at page 14, line 5
+- -+ +- -+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. sub-TLVs . . sub-TLVs .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6 Link-Local Address TLV IPv6 Link-Local Address TLV
3.8. IPv4 Link-Local Address TLV 3.9. IPv4 Link-Local Address TLV
The IPv4 Link-Local Address TLV is to be used with IPv4 address The IPv4 Link-Local Address TLV is to be used with IPv4 address
families as defined in [OSPFV3-AF]. The IPv4 Link-Local Address TLV families as defined in [OSPFV3-AF]. The IPv4 Link-Local Address TLV
is only applicable to the E-Link-LSA (Section 4.7). Inclusion in is only applicable to the E-Link-LSA (Section 4.7). Inclusion in
other Extended LSAs MUST be ignored. other Extended LSAs MUST be ignored.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 8 (IPv4 Local-Local Address) | TLV Length | | 8 (IPv4 Local-Local Address) | TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Link-Local Interface Address | | IPv4 Link-Local Interface Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. sub-TLVs . . sub-TLVs .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv4 Link-Local Address TLV IPv4 Link-Local Address TLV
3.9. IPv6-Forwarding-Address Sub-TLV 3.10. IPv6-Forwarding-Address Sub-TLV
The IPv6 Forwarding Address TLV has identical semantics to the The IPv6 Forwarding Address TLV has identical semantics to the
optional forwarding address in section A.4.7 of [OSPFV3]. The IPv6 optional forwarding address in section A.4.7 of [OSPFV3]. The IPv6
Forwarding Address TLV is applicable to the External-Prefix TLV Forwarding Address TLV is applicable to the External-Prefix TLV
(Section 3.5). Specification as a sub-TLV of other TLVs is not (Section 3.6). Specification as a sub-TLV of other TLVs is not
defined herein. The sub-TLV is optional and the first specified defined herein. The sub-TLV is optional and the first specified
instance is used as the Forwarding Address as defined in [OSPFV3]. instance is used as the Forwarding Address as defined in [OSPFV3].
Instances subsequent to the first MUST be ignored. Instances subsequent to the first MUST be ignored.
The IPv6 Forwarding Address TLV is to be used with IPv6 address The IPv6 Forwarding Address TLV is to be used with IPv6 address
families as defined in [OSPFV3-AF] It MUST be ignored for other families as defined in [OSPFV3-AF] It MUST be ignored for other
address families. address families.
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
skipping to change at page 15, line 35 skipping to change at page 15, line 35
+- -+ +- -+
| | | |
+- Forwarding Address -+ +- Forwarding Address -+
| | | |
+- -+ +- -+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Forwarding Address Tag TLV Forwarding Address Tag TLV
3.10. IPv4-Forwarding-Address Sub-TLV 3.11. IPv4-Forwarding-Address Sub-TLV
The IPv4 Forwarding Address TLV has identical semantics to the The IPv4 Forwarding Address TLV has identical semantics to the
optional forwarding address in section A.4.7 of [OSPFV3]. The IPv4 optional forwarding address in section A.4.7 of [OSPFV3]. The IPv4
Forwarding Address TLV is The IPv4 Forwarding Address TLV is Forwarding Address TLV is The IPv4 Forwarding Address TLV is
applicable to the External-Prefix TLV (Section 3.5). Specification applicable to the External-Prefix TLV (Section 3.6). Specification
as a sub-TLV of other TLVs is not defined herein. The sub-TLV is as a sub-TLV of other TLVs is not defined herein. The sub-TLV is
optional and the first specified instance is used as the Forwarding optional and the first specified instance is used as the Forwarding
Address as defined in [OSPFV3]. Instances subsequent to the first Address as defined in [OSPFV3]. Instances subsequent to the first
MUST be ignored. MUST be ignored.
The IPv4 Forwarding Address TLV is to be used with IPv3 address The IPv4 Forwarding Address TLV is to be used with IPv3 address
families as defined in [OSPFV3-AF] It MUST be ignored for other families as defined in [OSPFV3-AF] It MUST be ignored for other
address families. address families.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 - Forwarding Address | sub-TLV Length | | 2 - Forwarding Address | sub-TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Forwarding Address | | Forwarding Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Forwarding Address Tag TLV Forwarding Address Tag TLV
3.11. Route-Tag Sub-TLV 3.12. Route-Tag Sub-TLV
The optional Route Tag sub-TLV has identical semantics to the The optional Route Tag sub-TLV has identical semantics to the
optional External Route Tag in section A.4.7 of [OSPFV3]. The Route optional External Route Tag in section A.4.7 of [OSPFV3]. The Route
Tag sub-TLV is applicable to the External-Prefix TLV (Section 3.5). Tag sub-TLV is applicable to the External-Prefix TLV (Section 3.6).
Specification as a sub-TLV of other TLVs is not defined herein. The Specification as a sub-TLV of other TLVs is not defined herein. The
sub-TLV is optional and the first specified instance is used as the sub-TLV is optional and the first specified instance is used as the
Route Tag as defined in [OSPFV3]. Instances subsequent to the first Route Tag as defined in [OSPFV3]. Instances subsequent to the first
MUST be ignored. MUST be ignored.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 3 - Route Tag | sub-TLV Length | | 3 - Route Tag | sub-TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 17, line 41 skipping to change at page 17, line 28
| 0 |Nt|x|V|E|B| Options | | 0 |Nt|x|V|E|B| Options |
+-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. TLVs . . TLVs .
. . . .
+-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+--+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Extended Router-LSA Extended Router-LSA
All LSA Header fields are the same as defined for the Router-LSA. All LSA Header fields are the same as defined for the Router-LSA.
Initially, only the top-level Router-Link TLV Section 3.1 is Initially, only the top-level Router-Link TLV Section 3.2 is
applicable and an E-Router-LSA may include multiple Router-Link TLVs. applicable and an E-Router-LSA may include multiple Router-Link TLVs.
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. end of the LSA including TLVs.
4.2. OSPFv3 E-Network-LSA 4.2. OSPFv3 E-Network-LSA
The E-Network-LSA has an LS Type of 0xA022 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 defined in section A.4.4 of information content as the Network-LSA defined in section A.4.4 of
[OSPFV3]. However, unlike the existing Network-LSA, it is fully [OSPFV3]. However, unlike the existing Network-LSA, it is fully
extendable and represented as TLVs. extendable and represented as TLVs.
skipping to change at page 18, line 37 skipping to change at page 18, line 37
. . . .
. TLVs . . TLVs .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
E-Network-LSA E-Network-LSA
All LSA Header fields are the same as defined for the Network-LSA. All LSA Header fields are the same as defined for the Network-LSA.
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. Initially, only the top-level the end of the LSA including TLVs. Initially, only the top-level
Attached-Routers TLV Section 3.2 is applicable. If the Attached- Attached-Routers TLV Section 3.3 is applicable. If the Attached-
Router TLV is not included in the E-Network-LSA, it is treated as Router TLV is not included in the E-Network-LSA, it is treated as
malformed as described in Section 5. Instances of the Attached- malformed as described in Section 5. Instances of the Attached-
Router TLV subsequent to the first MUST be ignored. Router TLV subsequent to the first MUST be ignored.
4.3. OSPFv3 E-Inter-Area-Prefix-LSA 4.3. OSPFv3 E-Inter-Area-Prefix-LSA
The E-Inter-Area-Prefix-LSA has an LS Type of 0xA023 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 defined in base information content as the Inter-Area-Prefix-LSA defined in
section A.4.5 of [OSPFV3]. However, unlike the existing Inter-Area- section A.4.5 of [OSPFV3]. However, unlike the existing Inter-Area-
Prefix-LSA, it is fully extendable and represented as TLVs. Prefix-LSA, it is fully extendable and represented as TLVs.
skipping to change at page 19, line 40 skipping to change at page 19, line 40
E-Inter-Area-Prefix-LSA E-Inter-Area-Prefix-LSA
All LSA Header fields are the same as defined for the Inter-Area- All LSA Header fields are the same as defined for the Inter-Area-
Prefix-LSA. In order to retain compatibility and semantics with the Prefix-LSA. In order to retain compatibility and semantics with the
current OSPFv3 specification, each Inter-Area-Prefix LSA MUST contain current OSPFv3 specification, each Inter-Area-Prefix LSA MUST contain
a single Inter-Area Prefix TLV. This will facilitate migration and a single Inter-Area Prefix TLV. This will facilitate migration and
avoid changes to functions such as incremental SPF computation. avoid changes to 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. Initially, only the top- determine the end of the LSA including TLV. Initially, only the top-
level Inter-Area-Prefix TLV (Section 3.3) is applicable. If the level Inter-Area-Prefix TLV (Section 3.4) is applicable. If the
Inter-Area-Prefix TLV is not included in the E-Inter-Area-Prefix-LSA, Inter-Area-Prefix TLV is not included in the E-Inter-Area-Prefix-LSA,
it is treated as malformed as described in Section 5. Instances of it is treated as malformed as described in Section 5. Instances of
the Inter-Area-Prefix TLV subsequent to the first MUST be ignored. the Inter-Area-Prefix TLV subsequent to the first MUST be ignored.
4.4. OSPFv3 E-Inter-Area-Router-LSA 4.4. OSPFv3 E-Inter-Area-Router-LSA
The E-Inter-Area-Router-LSA has an LS Type of 0xA024 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-LSAE defined in base information content as the Inter-Area-Router-LSAE defined in
section A.4.6 of [OSPFV3]. However, unlike the Inter-Area-Router- section A.4.6 of [OSPFV3]. However, unlike the Inter-Area-Router-
LSA, it is fully extendable and represented as TLVs. LSA, it is fully extendable and represented as TLVs.
skipping to change at page 20, line 40 skipping to change at page 20, line 40
E-Inter-Area-Router-LSA E-Inter-Area-Router-LSA
All LSA Header fields are the same as defined for the Inter-Area- All LSA Header fields are the same as defined for the Inter-Area-
Router-LSA. In order to retain compatibility and semantics with the Router-LSA. In order to retain compatibility and semantics with the
current OSPFv3 specification, each Inter-Area-Router LSA MUST contain current OSPFv3 specification, each Inter-Area-Router LSA MUST contain
a single Inter-Area Router TLV. This will facilitate migration and a single Inter-Area Router TLV. This will facilitate migration and
avoid changes to functions such as incremental SPF computation. avoid changes to 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 TLV. Initially, only the top- determine the end of the LSA including TLV. Initially, only the top-
level Inter-Area-Router TLV (Section 3.4) is applicable. If the level Inter-Area-Router TLV (Section 3.5) is applicable. If the
Inter-Area-Router TLV is not included in the E-Inter-Area-Router-LSA, Inter-Area-Router TLV is not included in the E-Inter-Area-Router-LSA,
it is treated as malformed as described in Section 5. Instances of it is treated as malformed as described in Section 5. Instances of
the Inter-Area-Router TLV subsequent to the first MUST be ignored. the Inter-Area-Router TLV subsequent to the first MUST be ignored.
4.5. OSPFv3 E-AS-External-LSA 4.5. OSPFv3 E-AS-External-LSA
The E-AS-External-LSA has an LS Type of 0xC025 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 defined in section A.4.7 information content as the AS-External-LSA defined in section A.4.7
of [OSPFV3]. However, unlike the existing AS-External-LSA, it is of [OSPFV3]. However, unlike the existing AS-External-LSA, it is
fully extendable and represented as TLVs. fully extendable and represented as TLVs.
skipping to change at page 21, line 40 skipping to change at page 21, line 40
E-AS-External-LSA E-AS-External-LSA
All LSA Header fields are the same as defined for the AS-External- All LSA Header fields are the same as defined for the AS-External-
LSA. In order to retain compatibility and semantics with the current LSA. In order to retain compatibility and semantics with the current
OSPFv3 specification, each LSA MUST contain a single External Prefix OSPFv3 specification, each LSA MUST contain a single External Prefix
TLV. This will facilitate migration and avoid changes to OSPFv3 TLV. This will facilitate migration and avoid changes to OSPFv3
processes such as incremental SPF computation. processes such as incremental SPF computation.
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. Initially, only the determine the end of the LSA including sub-TLVs. Initially, only the
top-level External-Prefix TLV (Section 3.5) is applicable. If the top-level External-Prefix TLV (Section 3.6) is applicable. If the
External-Prefix TLV is not included in the E-External-AS-LSA, it is External-Prefix TLV is not included in the E-External-AS-LSA, it is
treated as malformed as described in Section 5. Instances of the treated as malformed as described in Section 5. Instances of the
External-Prefix TLV subsequent to the first MUST be ignored. External-Prefix TLV subsequent to the first MUST be ignored.
4.6. OSPFv3 E-NSSA-LSA 4.6. 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 4.5. This is the same relationship as exists External-LSA Section 4.5. This is the same relationship as exists
between the NSSA-LSA defined in section A.4.8 of [OSPFV3], and the between the NSSA-LSA defined in section A.4.8 of [OSPFV3], and the
AS-External-LSA. The NSSA-LSA will have type 0xA027 which implies AS-External-LSA. The NSSA-LSA will have type 0xA027 which implies
skipping to change at page 23, line 36 skipping to change at page 23, line 36
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. TLVs . . TLVs .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
E-Link-LSA E-Link-LSA
All LSA Header fields are the same as defined for the Link-LSA. All LSA Header fields are the same as defined for the Link-LSA.
Only the Intra-Area-Prefix TLV (Section 3.6), IPv6 Link-Local Address Only the Intra-Area-Prefix TLV (Section 3.7), IPv6 Link-Local Address
TLV (Section 3.7), and IPv4 Link-Local Address TLV (Section 3.8) are TLV (Section 3.8), and IPv4 Link-Local Address TLV (Section 3.9) are
applicable to the E-Link-LSA. Like the Link-LSA, the E-Link-LSA applicable to the E-Link-LSA. Like the Link-LSA, the E-Link-LSA
affords advertisement of multiple intra-area prefixes. Hence, affords advertisement of multiple intra-area prefixes. Hence,
multiple Intra-Area Prefix TLVs (Section 3.6) may be specified and multiple Intra-Area Prefix TLVs (Section 3.7) may be specified and
the LSA length defines the end of the LSA including all TLVs. the LSA length defines the end of the LSA including all TLVs.
A single instance of the IPv6 Link-Local Address TLV (Section 3.7) A single instance of the IPv6 Link-Local Address TLV (Section 3.8)
SHOULD be included in the E-Link-LSA. Instances following the first SHOULD be included in the E-Link-LSA. Instances following the first
MUST be ignored. For IPv4 address families as defined in MUST be ignored. For IPv4 address families as defined in
[OSPFV3-AF], this TLV MUST be ignored. [OSPFV3-AF], this TLV MUST be ignored.
Similarly, only a single instance of the IPv4 Link-Local Address TLV Similarly, only a single instance of the IPv4 Link-Local Address TLV
(Section 3.8) SHOULD be included in the E-Link-LSA. Instances (Section 3.9) SHOULD be included in the E-Link-LSA. Instances
following the first MUST be ignored. For OSPFv3 IPv6 address following the first MUST be ignored. For OSPFv3 IPv6 address
families as defined in [OSPFV3-AF], this TLV MUST be ignored. families as defined in [OSPFV3-AF], this TLV MUST be ignored.
If the IPv4/IPv6 Link-Local Address TLV corresponding to the OSPFv3 If the IPv4/IPv6 Link-Local Address TLV corresponding to the OSPFv3
Address Family is not included in the E-Link-LSA, it is treated as Address Family is not included in the E-Link-LSA, it is treated as
malformed as described in Section 5. malformed as described in Section 5.
Future specifications may support advertisement of routing and Future specifications may support advertisement of routing and
topology information for multiple address families. However, this is topology information for multiple address families. However, this is
beyond the scope of this document. beyond the scope of this document.
skipping to change at page 33, line 5 skipping to change at page 30, line 40
Consensus or IESG Approval. Consensus or IESG Approval.
Three values are allocated by this specification: Three values are allocated by this specification:
o 0 - Reserved o 0 - Reserved
o 1 - Forwarding Address o 1 - Forwarding Address
o 2 - Route Tag o 2 - Route Tag
The OSPFv3 Prefix Options registry will define a new code point for
the N-bit. The value 0x20 is suggested.
9. References 9. References
9.1. Normative References 9.1. Normative References
[GRACEFUL-RESTART] [GRACEFUL-RESTART]
Lindem, A. and P. Pillay-Esnault, "OSPFv3 Graceful Lindem, A. and P. Pillay-Esnault, "OSPFv3 Graceful
Restart", RFC 5178, June 2008. Restart", RFC 5187, June 2008.
[NSSA] Murphy, P., "The OSPF Not-So-Stubby Area (NSSA) Option",
RFC 3101, January 2003.
[OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
for IPv6", RFC 5340, July 2008. for IPv6", RFC 5340, July 2008.
[OSPFV3-AF] [OSPFV3-AF]
Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R.
Aggarwal, "Support of Address Families in OSPFv3", Aggarwal, "Support of Address Families in OSPFv3", RFC
RFC 5838, April 2010. 5838, April 2010.
[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.
9.2. Informative References 9.2. Informative References
[MT-OSPFV3] [MT-OSPFV3]
Mirtorabi, S. and A. Roy, "Multi-topology routing in Mirtorabi, S. and A. Roy, "Multi-topology routing in
OSPFv3 (MT-OSPFV3)", draft-ietf-ospf-mt-ospfv3-04.txt OSPFv3 (MT-OSPFV3)", draft-ietf-ospf-mt-ospfv3-03.txt
(work in progress). (work in progress), January 2008.
[OSPF-DIGITAL-SIGNATURE] [OSPF-DIGITAL-SIGNATURE]
Murphy, S., Badger, M., and B. Wellington, "OSPF with Murphy, S., Badger, M., and B. Wellington, "OSPF with
Digital Signatures", RFC 2154, June 1997. Digital Signatures", RFC 2154, June 1997.
[SEGMENT-ROUTING]
Psenak, P., Previdi, S., Filsfils, C., Gredler, H.,
Shakir, R., Henderickx, W., and J. Tantsura, "OSPF
Extensions for Segment Routing", draft-ietf-ospf-segment-
routing-extensions-04.txt (work in progress), February
2015.
Appendix A. Global Configuration Parameters Appendix A. Global Configuration Parameters
An additional global configurable parameter will be added to the An additional global configurable parameter 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 values for the enumeration are: Extended LSAs. The valid values for the enumeration are:
 End of changes. 47 change blocks. 
95 lines changed or deleted 155 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/