< draft-ietf-ospf-ospfv3-lsa-extend-22.txt   draft-ietf-ospf-ospfv3-lsa-extend-23.txt >
Network Working Group A. Lindem Network Working Group A. Lindem
Internet-Draft A. Roy Internet-Draft A. Roy
Updates: 5340, 5838 (if approved) Cisco Systems Updates: 5340, 5838 (if approved) Cisco Systems
Intended status: Standards Track D. Goethals Intended status: Standards Track D. Goethals
Expires: July 28, 2018 Nokia Expires: July 29, 2018 Nokia
V. Reddy Vallem V. Reddy Vallem
F. Baker F. Baker
January 24, 2018 January 25, 2018
OSPFv3 LSA Extendibility OSPFv3 LSA Extendibility
draft-ietf-ospf-ospfv3-lsa-extend-22.txt draft-ietf-ospf-ospfv3-lsa-extend-23.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
skipping to change at page 1, line 48 skipping to change at page 1, line 48
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 July 28, 2018. This Internet-Draft will expire on July 29, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 31 skipping to change at page 2, line 31
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements notation . . . . . . . . . . . . . . . . . . 4 1.1. Requirements notation . . . . . . . . . . . . . . . . . . 4
1.2. OSPFv3 LSA Terminology . . . . . . . . . . . . . . . . . 4 1.2. OSPFv3 LSA Terminology . . . . . . . . . . . . . . . . . 4
2. OSPFv3 Extended LSA Types . . . . . . . . . . . . . . . . . . 4 2. OSPFv3 Extended LSA Types . . . . . . . . . . . . . . . . . . 4
3. OSPFv3 Extended LSA TLVs . . . . . . . . . . . . . . . . . . 5 3. OSPFv3 Extended LSA TLVs . . . . . . . . . . . . . . . . . . 5
3.1. Prefix Options Extensions . . . . . . . . . . . . . . . . 6 3.1. Prefix Options Extensions . . . . . . . . . . . . . . . . 6
3.1.1. N-bit Prefix Option . . . . . . . . . . . . . . . . . 6 3.1.1. N-bit Prefix Option . . . . . . . . . . . . . . . . . 6
3.2. Router-Link TLV . . . . . . . . . . . . . . . . . . . . . 7 3.2. Router-Link TLV . . . . . . . . . . . . . . . . . . . . . 7
3.3. Attached-Routers TLV . . . . . . . . . . . . . . . . . . 8 3.3. Attached-Routers TLV . . . . . . . . . . . . . . . . . . 8
3.4. Inter-Area-Prefix TLV . . . . . . . . . . . . . . . . . . 9 3.4. Inter-Area-Prefix TLV . . . . . . . . . . . . . . . . . . 10
3.5. Inter-Area-Router TLV . . . . . . . . . . . . . . . . . . 10 3.5. Inter-Area-Router TLV . . . . . . . . . . . . . . . . . . 11
3.6. External-Prefix TLV . . . . . . . . . . . . . . . . . . . 11 3.6. External-Prefix TLV . . . . . . . . . . . . . . . . . . . 12
3.7. Intra-Area-Prefix TLV . . . . . . . . . . . . . . . . . . 12 3.7. Intra-Area-Prefix TLV . . . . . . . . . . . . . . . . . . 13
3.8. IPv6 Link-Local Address TLV . . . . . . . . . . . . . . . 13 3.8. IPv6 Link-Local Address TLV . . . . . . . . . . . . . . . 14
3.9. IPv4 Link-Local Address TLV . . . . . . . . . . . . . . . 14 3.9. IPv4 Link-Local Address TLV . . . . . . . . . . . . . . . 15
3.10. IPv6-Forwarding-Address Sub-TLV . . . . . . . . . . . . . 15 3.10. IPv6-Forwarding-Address Sub-TLV . . . . . . . . . . . . . 16
3.11. IPv4-Forwarding-Address Sub-TLV . . . . . . . . . . . . . 15 3.11. IPv4-Forwarding-Address Sub-TLV . . . . . . . . . . . . . 16
3.12. Route-Tag Sub-TLV . . . . . . . . . . . . . . . . . . . . 16 3.12. Route-Tag Sub-TLV . . . . . . . . . . . . . . . . . . . . 17
4. OSPFv3 Extended LSAs . . . . . . . . . . . . . . . . . . . . 16 4. OSPFv3 Extended LSAs . . . . . . . . . . . . . . . . . . . . 17
4.1. OSPFv3 E-Router-LSA . . . . . . . . . . . . . . . . . . . 16 4.1. OSPFv3 E-Router-LSA . . . . . . . . . . . . . . . . . . . 17
4.2. OSPFv3 E-Network-LSA . . . . . . . . . . . . . . . . . . 18 4.2. OSPFv3 E-Network-LSA . . . . . . . . . . . . . . . . . . 19
4.3. OSPFv3 E-Inter-Area-Prefix-LSA . . . . . . . . . . . . . 19 4.3. OSPFv3 E-Inter-Area-Prefix-LSA . . . . . . . . . . . . . 20
4.4. OSPFv3 E-Inter-Area-Router-LSA . . . . . . . . . . . . . 20 4.4. OSPFv3 E-Inter-Area-Router-LSA . . . . . . . . . . . . . 21
4.5. OSPFv3 E-AS-External-LSA . . . . . . . . . . . . . . . . 21 4.5. OSPFv3 E-AS-External-LSA . . . . . . . . . . . . . . . . 22
4.6. OSPFv3 E-NSSA-LSA . . . . . . . . . . . . . . . . . . . . 22 4.6. OSPFv3 E-NSSA-LSA . . . . . . . . . . . . . . . . . . . . 23
4.7. OSPFv3 E-Link-LSA . . . . . . . . . . . . . . . . . . . . 23 4.7. OSPFv3 E-Link-LSA . . . . . . . . . . . . . . . . . . . . 24
4.8. OSPFv3 E-Intra-Area-Prefix-LSA . . . . . . . . . . . . . 25 4.8. OSPFv3 E-Intra-Area-Prefix-LSA . . . . . . . . . . . . . 26
5. Malformed OSPFv3 Extended LSA Handling . . . . . . . . . . . 26 5. Malformed OSPFv3 Extended LSA Handling . . . . . . . . . . . 27
6. LSA Extension Backward Compatibility . . . . . . . . . . . . 26 6. LSA Extension Backward Compatibility . . . . . . . . . . . . 27
6.1. Full Extended LSA Migration . . . . . . . . . . . . . . . 26 6.1. Full Extended LSA Migration . . . . . . . . . . . . . . . 27
6.2. Extended LSA Sparse-Mode Backward Compatibility . . . . . 27 6.2. Extended LSA Sparse-Mode Backward Compatibility . . . . . 28
6.3. LSA TLV Processing Backward Compatibility . . . . . . . . 27 6.3. LSA TLV Processing Backward Compatibility . . . . . . . . 28
7. Security Considerations . . . . . . . . . . . . . . . . . . . 28 7. Security Considerations . . . . . . . . . . . . . . . . . . . 29
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
8.1. OSPFv3 Extended-LSA TLV Registry . . . . . . . . . . . . 28 8.1. OSPFv3 Extended-LSA TLV Registry . . . . . . . . . . . . 29
8.2. OSPFv3 Extended-LSA sub-TLV Registry . . . . . . . . . . 29 8.2. OSPFv3 Extended-LSA sub-TLV Registry . . . . . . . . . . 30
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 30 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 31
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 30 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 31
10.1. Normative References . . . . . . . . . . . . . . . . . . 30 10.1. Normative References . . . . . . . . . . . . . . . . . . 31
10.2. Informative References . . . . . . . . . . . . . . . . . 30 10.2. Informative References . . . . . . . . . . . . . . . . . 31
Appendix A. Appendix A - Global Configuration Parameters . . . . 31 Appendix A. Appendix A - Global Configuration Parameters . . . . 32
Appendix B. Appendix B - Area Configuration Parameters . . . . . 31 Appendix B. Appendix B - Area Configuration Parameters . . . . . 32
Appendix C. Acknowledgments . . . . . . . . . . . . . . . . . . 31 Appendix C. Acknowledgments . . . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 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 7, line 18 skipping to change at page 7, line 18
router MAY choose NOT to set the N-bit even when the above conditions 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 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 N-bit MUST be ignored. Additionally, the N-bit is propagated in the
PrefixOptions when an OSPFv3 Area Border Router (ABR) originates an 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 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 in the PrefixOptions. Similarly, the N-bit is propagated in the
PrefixOptions when an OSPFv3 NSSA ABR originates an E-AS-External-LSA PrefixOptions when an OSPFv3 NSSA ABR originates an E-AS-External-LSA
corresponding to an NSSA route as described in section 3 of RFC 3101 corresponding to an NSSA route as described in section 3 of RFC 3101
([NSSA]). The N-bit is added to the Inter-Area-Prefix-TLV ([NSSA]). The N-bit is added to the Inter-Area-Prefix-TLV
(Section 3.4), External-Prefix-TLV (Section 3.6), and Intra-Area- (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 Prefix-TLV (Section 3.7). The N-bit is used as hint to identify the
as identifying the prefixes corresponding to Node Segment Identifiers preferred address to reach the advertising OSPFv3 router. This would
(SIDs) in Segment Routing [SEGMENT-ROUTING]. be in contrast to an Anycast Address [IPV6-ADDRESS-ARCH] which could
also be a local address with the LA-bit set. It is useful for
applications such as identifying the prefixes corresponding to Node
Segment Identifiers (SIDs) in Segment Routing [SEGMENT-ROUTING].
There may be future applications requiring selection of a prefix
associated with an OSPFv3 router.
3.2. Router-Link TLV 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
skipping to change at page 30, line 44 skipping to change at page 31, line 44
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", RFC 8174, May 2017. 2119 Key Words", RFC 8174, May 2017.
[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.
10.2. Informative References 10.2. Informative References
[IPV6-ADDRESS-ARCH]
Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
[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-04.txt
(work in progress), January 2008. (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.
[OSPF-PREFIX-LINK] [OSPF-PREFIX-LINK]
 End of changes. 7 change blocks. 
42 lines changed or deleted 51 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/