| < draft-ietf-ospf-ospfv3-lsa-extend-04.txt | draft-ietf-ospf-ospfv3-lsa-extend-05.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: March 22, 2015 F. Baker | Expires: May 28, 2015 F. Baker | |||
| Cisco Systems | Cisco Systems | |||
| September 18, 2014 | November 24, 2014 | |||
| OSPFv3 LSA Extendibility | OSPFv3 LSA Extendibility | |||
| draft-ietf-ospf-ospfv3-lsa-extend-04.txt | draft-ietf-ospf-ospfv3-lsa-extend-05.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 40 ¶ | skipping to change at page 1, line 40 ¶ | |||
| 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 March 22, 2015. | This Internet-Draft will expire on May 28, 2015. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2014 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 4, line 16 ¶ | skipping to change at page 4, line 16 ¶ | |||
| Przygienda for review of the draft versions and discussions of | Przygienda for review of the draft versions and discussions of | |||
| backward compatibility. | backward compatibility. | |||
| Thanks to Alan Davey for review and comments including the suggestion | Thanks to Alan Davey for review and comments including the suggestion | |||
| to separate the extended LSA TLV definitions from the extended LSAs | to separate the extended LSA TLV definitions from the extended LSAs | |||
| definitions. | definitions. | |||
| Thanks to David Lamparter for review and suggestions on backward | Thanks to David Lamparter for review and suggestions on backward | |||
| compatibility. | compatibility. | |||
| Thanks to Karsten Thomann for review and editorial comments. | ||||
| 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 LSAs 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 to this mapping was to allocate a bit in the | added. The alternative to this mapping was to allocate a bit in the | |||
| LS Type indicating the new LSA format. However, this would have used | LS Type indicating the new LSA format. However, this would have used | |||
| skipping to change at page 15, line 16 ¶ | skipping to change at page 15, line 16 ¶ | |||
| 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.5). 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 will 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 | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| | 1 - Forwarding Address | sub-TLV Length | | | 1 - Forwarding Address | sub-TLV Length | | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| | | | | | | |||
| +- -+ | +- -+ | |||
| | | | | | | |||
| skipping to change at page 15, line 47 ¶ | skipping to change at page 15, line 47 ¶ | |||
| 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.5). 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 will 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 | | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| skipping to change at page 23, line 9 ¶ | skipping to change at page 23, line 9 ¶ | |||
| 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 | |||
| area flooding scope. Future requirements may dictate that supported | area flooding scope. Future requirements may dictate that supported | |||
| TLVs differ between the E-AS-External-LSA and the E-NSSA-LSA. | TLVs differ between the E-AS-External-LSA and the E-NSSA-LSA. | |||
| However, future requirements are beyond the scope of this document. | However, future requirements are beyond the scope of this document. | |||
| 4.7. OSPFv3 E-Link-LSA | 4.7. OSPFv3 E-Link-LSA | |||
| The E-Link-LSA has an LS Type of 0x8028 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 defined in section A.4.9 of | information content as the Link-LSA defined in section A.4.9 of | |||
| [OSPFV3]. However, unlike the existing Link-LFA, it is extendable | [OSPFV3]. However, unlike the existing Link-LSA, it is extendable | |||
| and represented as TLVs. | 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 |1|0|0| 0x28 | | | LS Age |1|0|0| 0x28 | | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| | Link State ID | | | Link State ID | | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| | Advertising Router | | | Advertising Router | | |||
| End of changes. 8 change blocks. | ||||
| 7 lines changed or deleted | 9 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/ | ||||