< draft-ietf-ospf-ospfv3-lsa-extend-18.txt   draft-ietf-ospf-ospfv3-lsa-extend-19.txt >
Network Working Group A. Lindem Network Working Group A. Lindem
Internet-Draft A. Roy Internet-Draft A. Roy
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: May 25, 2018 D. Goethals Expires: June 21, 2018 D. Goethals
Nokia Nokia
V. Reddy Vallem V. Reddy Vallem
F. Baker F. Baker
November 21, 2017 December 18, 2017
OSPFv3 LSA Extendibility OSPFv3 LSA Extendibility
draft-ietf-ospf-ospfv3-lsa-extend-18.txt draft-ietf-ospf-ospfv3-lsa-extend-19.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 44 skipping to change at page 1, line 44
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 25, 2018. This Internet-Draft will expire on June 21, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 3, line 8 skipping to change at page 3, line 8
4.6. OSPFv3 E-NSSA-LSA . . . . . . . . . . . . . . . . . . . . 23 4.6. OSPFv3 E-NSSA-LSA . . . . . . . . . . . . . . . . . . . . 23
4.7. OSPFv3 E-Link-LSA . . . . . . . . . . . . . . . . . . . . 24 4.7. OSPFv3 E-Link-LSA . . . . . . . . . . . . . . . . . . . . 24
4.8. OSPFv3 E-Intra-Area-Prefix-LSA . . . . . . . . . . . . . 26 4.8. OSPFv3 E-Intra-Area-Prefix-LSA . . . . . . . . . . . . . 26
5. Malformed OSPFv3 Extended LSA Handling . . . . . . . . . . . 27 5. Malformed OSPFv3 Extended LSA Handling . . . . . . . . . . . 27
6. LSA Extension Backward Compatibility . . . . . . . . . . . . 27 6. LSA Extension Backward Compatibility . . . . . . . . . . . . 27
6.1. Full Extended LSA Migration . . . . . . . . . . . . . . . 27 6.1. Full Extended LSA Migration . . . . . . . . . . . . . . . 27
6.2. Extended LSA Spare-Mode Backward Compatibility . . . . . 28 6.2. Extended LSA Spare-Mode Backward Compatibility . . . . . 28
6.3. LSA TLV Processing Backward Compatibility . . . . . . . . 28 6.3. LSA TLV Processing Backward Compatibility . . . . . . . . 28
7. Security Considerations . . . . . . . . . . . . . . . . . . . 29 7. Security Considerations . . . . . . . . . . . . . . . . . . . 29
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 30 8.1. OSPFv3 Extended-LSA TLV Registry . . . . . . . . . . . . 29
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 30 8.2. OSPFv3 Extended-LSA sub-TLV Registry . . . . . . . . . . 30
10.1. Normative References . . . . . . . . . . . . . . . . . . 30 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 31
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 31
10.1. Normative References . . . . . . . . . . . . . . . . . . 31
10.2. Informative References . . . . . . . . . . . . . . . . . 31 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. Appendix C - Deprecated LSA Extension Backward Appendix C. Appendix C - Deprecated LSA Extension Backward
Compatibility . . . . . . . . . . . . . . . . . . . 32 Compatibility . . . . . . . . . . . . . . . . . . . 32
C.1. Extended LSA Mixed-Mode Backward Compatibility . . . . . 34 C.1. Extended LSA Mixed-Mode Backward Compatibility . . . . . 34
C.1.1. Area Extended LSA Mixed-Mode Backward Compatibility . 34 C.1.1. Area Extended LSA Mixed-Mode Backward Compatibility . 35
C.2. Global Configuration Parameters . . . . . . . . . . . . . 35 C.2. Global Configuration Parameters . . . . . . . . . . . . . 36
C.3. Area Configuration Parameters . . . . . . . . . . . . . . 36 C.3. Area Configuration Parameters . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37
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 29, line 22 skipping to change at page 29, line 22
implementations must assure that malformed TLV and sub-TLV implementations must assure that malformed TLV and sub-TLV
permutations do not result in errors that cause hard OSPFv3 failures. permutations do not result in errors that cause hard OSPFv3 failures.
If there were ever a requirement to digitally sign OSPFv3 LSAs as If there were ever a requirement to digitally sign OSPFv3 LSAs as
described for OSPFv2 LSAs in RFC 2154 [OSPF-DIGITAL-SIGNATURE], the described for OSPFv2 LSAs in RFC 2154 [OSPF-DIGITAL-SIGNATURE], the
mechanisms described herein would greatly simplify the extension. mechanisms described herein would greatly simplify the extension.
8. IANA Considerations 8. 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. These will be added to the existing OSPFv3
LSA Function Codes registry.
The specification will define a new code point for the N-bit in the
OSPFv3 Prefix-Options registry. The value 0x20 is suggested.
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.
8.1. OSPFv3 Extended-LSA TLV Registry
The OSPFv3 Extended-LSA TLV registry will define top-level TLVs for The OSPFv3 Extended-LSA TLV registry will define top-level TLVs for
Extended-LSAs and should be placed in the existing OSPFv3 IANA Extended-LSAs and should be placed in the existing OSPFv3 IANA
registry. New values can be allocated via IETF Consensus or IESG registry.
Approval.
Nine values are allocated by this specification: Nine values are allocated by this specification:
o 0 - Reserved o 0 - Reserved
o 1 - Router-Link TLV o 1 - Router-Link TLV
o 2 - Attached-Routers TLV o 2 - Attached-Routers TLV
o 3 - Inter-Area Prefix TLV o 3 - Inter-Area Prefix TLV
skipping to change at page 29, line 47 skipping to change at page 30, line 4
o 1 - Router-Link TLV o 1 - Router-Link TLV
o 2 - Attached-Routers TLV o 2 - Attached-Routers TLV
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
Types in the range 9-32767 are allocated via IETF Consensus or IESG
Approval.
Types in the range 32768-33023 are for experimental use; these will
not be registered with IANA, and MUST NOT be mentioned by RFCs.
Types in the range 33024-65535 are not to be assigned at this time.
Before any assignments can be made in the 33024-65535 range, there
MUST be an IETF specification that specifies IANA Considerations that
covers the range being assigned.
8.2. OSPFv3 Extended-LSA sub-TLV Registry
The OSPFv3 Extended-LSA sub-TLV registry will define sub-TLVs at any The OSPFv3 Extended-LSA sub-TLV registry will define sub-TLVs at any
level of nesting for Extended-LSAs and should be placed in the level of nesting for Extended-LSAs and should be placed in the
existing OSPFv3 IANA registry. New values can be allocated via IETF existing OSPFv3 IANA registry.
Review.
Three values are allocated by this specification: Four values are allocated by this specification:
o 0 - Reserved o 0 - Reserved
o 1 - Forwarding Address o 1 - IPv6 Forwarding Address sub-TLV
o 2 - Route Tag o 2 - IPv4 Forwarding Address sub-TLV
The OSPFv3 Prefix Options registry will define a new code point for o 3 - Route Tag sub-TLV
the N-bit. The value 0x20 is suggested.
Types in the range 4-32767 are allocated via IETF Consensus or IESG
Approval.
Types in the range 32768-33023 are for experimental use; these will
not be registered with IANA, and MUST NOT be mentioned by RFCs.
Types in the range 33024-65535 are not to be assigned at this time.
Before any assignments can be made in the 33024-65535 range, there
MUST be an IETF specification that specifies IANA Considerations that
covers the range being assigned.
9. Contributors 9. Contributors
Contributors' Addresses Contributors' Addresses
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. 18 change blocks. 
23 lines changed or deleted 52 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/