< draft-ietf-lsr-ospf-prefix-originator-09.txt   draft-ietf-lsr-ospf-prefix-originator-10.txt >
LSR Working Group A. Wang LSR Working Group A. Wang
Internet-Draft China Telecom Internet-Draft China Telecom
Intended status: Standards Track A. Lindem Intended status: Standards Track A. Lindem
Expires: September 20, 2021 Cisco Systems Expires: October 4, 2021 Cisco Systems
J. Dong J. Dong
Huawei Technologies Huawei Technologies
P. Psenak P. Psenak
K. Talaulikar K. Talaulikar, Ed.
Cisco Systems Cisco Systems
March 19, 2021 April 2, 2021
OSPF Prefix Originator Extensions OSPF Prefix Originator Extensions
draft-ietf-lsr-ospf-prefix-originator-09 draft-ietf-lsr-ospf-prefix-originator-10
Abstract Abstract
This document defines OSPF extensions to include information This document defines OSPF extensions to include information
associated with the node originating a prefix along with the prefix associated with the node originating a prefix along with the prefix
advertisement. advertisement.
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
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 September 20, 2021. This Internet-Draft will expire on October 4, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 18 skipping to change at page 2, line 18
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 3 2. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 3
2.1. Prefix Source OSPF Router-ID Sub-TLV . . . . . . . . . . 3 2.1. Prefix Source OSPF Router-ID Sub-TLV . . . . . . . . . . 3
2.2. Prefix Source Router Address Sub-TLV . . . . . . . . . . 4 2.2. Prefix Source Router Address Sub-TLV . . . . . . . . . . 4
3. Elements of Procedure . . . . . . . . . . . . . . . . . . . . 5 3. Elements of Procedure . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. Operational Considerations . . . . . . . . . . . . . . . . . 6
6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 7 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Normative References . . . . . . . . . . . . . . . . . . 8 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.2. Informative References . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
Prefix attributes are advertised in OSPFv2 [RFC2328] using the Prefix attributes are advertised in OSPFv2 [RFC2328] using the
Extended Prefix Opaque Link State Advertisement (LSA) [RFC7684] and Extended Prefix Opaque Link State Advertisement (LSA) [RFC7684] and
in OSPFv3 [RFC5340] using the various Extended Prefix LSA types in OSPFv3 [RFC5340] using the various Extended Prefix LSA types
[RFC8362]. [RFC8362].
The identification of the originating router for a prefix in OSPF The identification of the originating router for a prefix in OSPF
skipping to change at page 5, line 17 skipping to change at page 5, line 17
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router Address (4 or 16 octets) | | Router Address (4 or 16 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Prefix Source Router Address Sub-TLV Format Figure 2: Prefix Source Router Address Sub-TLV Format
Where: Where:
o Type: TBD1 for OSPFv2 and TBD2 for OSPFv3 o Type: 5 (suggested) for OSPFv2 and 28 (suggested) for OSPFv3
o Length: 4 or 16 o Length: 4 or 16
o Router Address: A reachable IPv4 or IPv6 router address for the o Router Address: A reachable IPv4 or IPv6 router address for the
router that originated the IPv4 or IPv6 prefix advertisement router that originated the IPv4 or IPv6 prefix advertisement
respectively. Such an address would be semantically equivalent to respectively. Such an address would be semantically equivalent to
what may be advertised in the OSPFv2 Router Address TLV [RFC3630] what may be advertised in the OSPFv2 Router Address TLV [RFC3630]
or in the OSPFv3 Router IPv6 Address TLV [RFC5329]. or in the OSPFv3 Router IPv6 Address TLV [RFC5329].
The parent TLV of a prefix advertisement MAY include more than one The parent TLV of a prefix advertisement MAY include more than one
Prefix Source Router Address Sub-TLV, one corresponding to each of Prefix Source Router Address Sub-TLV, one corresponding to each of
the Equal-Cost Multi-Path (ECMP) nodes that originated the given the Equal-Cost Multi-Path (ECMP) nodes that originated the given
prefix. prefix.
A received Prefix Source Router Address Sub-TLV that has an invalid A received Prefix Source Router Address Sub-TLV that has an invalid
length (i.e. not consistent with the prefix's address family) or a length (i.e. not consistent with the prefix's address family) MUST be
Router Address containing an invalid IPv4 or IPv6 address (dependent considered invalid and ignored. Additionally, reception of such Sub-
on address family of the associated prefix) MUST be considered TLV SHOULD be logged as an error (subject to rate-limiting).
invalid and ignored. Additionally, reception of such Sub-TLV SHOULD
be logged as an error (subject to rate-limiting).
3. Elements of Procedure 3. Elements of Procedure
This section describes the procedure for advertisement of the Prefix This section describes the procedure for advertisement of the Prefix
Source OSPF Router-ID and Prefix Source Router Address Sub-TLVs along Source OSPF Router-ID and Prefix Source Router Address Sub-TLVs along
with the prefix advertisement. with the prefix advertisement.
The OSPF Router ID of the Prefix Source OSPF Router-ID is set to the The OSPF Router ID of the Prefix Source OSPF Router-ID is set to the
OSPF Router ID of the node originating the prefix in the OSPF domain. OSPF Router ID of the node originating the prefix in the OSPF domain.
If the originating node is advertising an OSPFv2 Router Address TLV If the originating node is advertising an OSPFv2 Router Address TLV
[RFC3630] or an OSPFv3 Router IPv6 Address TLV [RFC5329], then the [RFC3630] or an OSPFv3 Router IPv6 Address TLV [RFC5329], then the
same address MUST be used in the Router Address field of the Prefix same address MUST be used in the Router Address field of the Prefix
Source Router Address Sub-TLV. When the originating node is not Source Router Address Sub-TLV. When the originating node is not
advertising such an address, implementations can determine a unique advertising such an address, implementations can determine a unique
and reachable address (i.e., advertised with the N-flag set [RFC7684] and reachable address (i.e., advertised with the N-flag set [RFC7684]
or N-bit set [RFC8362]) belonging to the originating node to set in or N-bit set [RFC8362]) belonging to the originating node to set in
the Router Address field. the Router Address field.
Implementations MAY support the selection of specific prefixes for
which the originating node information needs to be included with
their prefix advertisements.
When an ABR generates inter-area prefix advertisements into its non- When an ABR generates inter-area prefix advertisements into its non-
backbone areas corresponding to an inter-area prefix advertisement backbone areas corresponding to an inter-area prefix advertisement
from the backbone area, the only way to determine the originating from the backbone area, the only way to determine the originating
node information is based on the Prefix Source OSPF Router-ID and node information is based on the Prefix Source OSPF Router-ID and
Prefix Source Router Address Sub-TLVs present in the inter-area Prefix Source Router Address Sub-TLVs present in the inter-area
prefix advertisement originated into the backbone area by an ABR from prefix advertisement originated into the backbone area by an ABR from
another non-backbone area. The ABR performs its prefix calculation another non-backbone area. The ABR performs its prefix calculation
to determine the set of nodes that contribute to the best prefix to determine the set of nodes that contribute to the best prefix
reachability. It MUST use the prefix originator information only reachability. It MUST use the prefix originator information only
from this set of nodes. The ABR MUST NOT include the Prefix Source from this set of nodes. The ABR MUST NOT include the Prefix Source
OSPF Router-ID or the Prefix Source Router Address Sub-TLVs when it OSPF Router-ID or the Prefix Source Router Address Sub-TLVs when it
is unable to determine the information of the best originating node. is unable to determine the information of the best originating node.
Implementations MAY provide control on ABRs to selectively disable
the propagation of the originating node information across area
boundaries.
Implementations may support the propagation of the originating node Implementations may support the propagation of the originating node
information along with a redistributed prefix into the OSPF domain information along with a redistributed prefix into the OSPF domain
from another routing domain. The details of such mechanisms are from another routing domain. The details of such mechanisms are
outside the scope of this document. Such implementations may also outside the scope of this document. Such implementations may also
provide control on whether the Router Address in the Prefix Source provide control on whether the Router Address in the Prefix Source
Router Address Sub-TLV is set as the ABSR node address or as the Router Address Sub-TLV is set as the ABSR node address or as the
address of the actual node outside the OSPF domain that owns the address of the actual node outside the OSPF domain that owns the
prefix. prefix.
When translating the NSSA prefix advertisements [RFC3101] to the AS When translating the NSSA prefix advertisements [RFC3101] to the AS
skipping to change at page 7, line 8 skipping to change at page 6, line 47
security considerations for [RFC7684] are applicable. Similarly, security considerations for [RFC7684] are applicable. Similarly,
since this document extends the OSPFv3 E-Intra-Area-Prefix-LSA, E- since this document extends the OSPFv3 E-Intra-Area-Prefix-LSA, E-
Inter-Area-Prefix-LSA, E-AS-External LSA and E-NSSA-LSA, the security Inter-Area-Prefix-LSA, E-AS-External LSA and E-NSSA-LSA, the security
considerations for [RFC8362] are applicable. The new sub-TLVs considerations for [RFC8362] are applicable. The new sub-TLVs
introduced in this document are optional and do not affect the OSPF introduced in this document are optional and do not affect the OSPF
route computation and therefore do not affect the security aspects of route computation and therefore do not affect the security aspects of
OSPF protocol operations. A rogue node that can inject prefix OSPF protocol operations. A rogue node that can inject prefix
advertisements may use the new extensions introduced in this document advertisements may use the new extensions introduced in this document
to indicate incorrect prefix source information. to indicate incorrect prefix source information.
5. IANA Considerations 5. Operational Considerations
Consideration should be given to the operation impact of the increase
in the size of the OSPF Link-State Database as a result of the
protocol extensions in this document. Based on deployment design and
requirements, a subset of prefixes may be identified for which the
originating node information needs to be included with their prefix
advertisements.
The propagation of the prefix source node information when doing
prefix advertisements across OSPF area or domain boundaries results
in the exposure of node information outside of an area or domain
within which it is normally hidden or abstracted by the base OSPF
protocol. Based on deployment design and requirements, a subset of
prefixes may be identified for which the propagation of the
originating node information across area boundaries is disabled at
the ABRs.
The identification of the node that is originating a specific prefix
in the network may aid in debugging of issues related to prefix
reachability within an OSPF network.
6. IANA Considerations
This document requests IANA for the allocation of the codepoints from This document requests IANA for the allocation of the codepoints from
the "OSPFv2 Extended Prefix TLV Sub-TLVs" registry under the "Open the "OSPFv2 Extended Prefix TLV Sub-TLVs" registry under the "Open
Shortest Path First v2 (OSPFv2) Parameters" registry. Shortest Path First v2 (OSPFv2) Parameters" registry.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Code | Description | IANA Allocation | | Code | Description | IANA Allocation |
|Point| | Status | | Point | | Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 4 | Prefix Source OSPF Router-ID Sub-TLV| early allocation done | | 4 | Prefix Source OSPF Router-ID | early allocation done |
| TBD1| Prefix Source Router Address Sub-TLV| pending | | 5 | Prefix Source Router Address | suggested |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Codepoints in OSPFv2 Extended Prefix TLV Sub-TLVs Figure 3: Codepoints in OSPFv2 Extended Prefix TLV Sub-TLVs
This document requests IANA for the allocation of the codepoints from This document requests IANA for the allocation of the codepoints from
the "OSPFv3 Extended Prefix TLV Sub-TLVs" registry under the "Open the "OSPFv3 Extended-LSA Sub-TLVs" registry under the "Open Shortest
Shortest Path First v3 (OSPFv3) Parameters" registry. Path First v3 (OSPFv3) Parameters" registry.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Code | Description | IANA Allocation | | Code | Description | IANA Allocation |
|Point| | Status | | Point | | Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 27 | Prefix Source OSPF Router-ID Sub-TLV| early allocation done | | 27 | Prefix Source OSPF Router-ID | early allocation done |
|TBD2 | Prefix Source Router Address Sub-TLV| pending | | 28 | Prefix Source Router Address | suggested |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Codepoints in OSPFv3 Extended-LSA Sub-TLVs Figure 4: Codepoints in OSPFv3 Extended-LSA Sub-TLVs
6. Acknowledgement 7. Acknowledgement
Many thanks to Les Ginsberg for his suggestions on this draft. Also Many thanks to Les Ginsberg for his suggestions on this draft. Also
thanks to Jeff Tantsura, Rob Shakir, Gunter Van De Velde, Goethals thanks to Jeff Tantsura, Rob Shakir, Gunter Van De Velde, Goethals
Dirk, Smita Selot, Shaofu Peng, John E Drake and Baalajee S for their Dirk, Smita Selot, Shaofu Peng, John E Drake and Baalajee S for their
review and valuable comments. The authors would also like to thank review and valuable comments. The authors would also like to thank
Alvaro Retana for his detailed review and suggestions for the Alvaro Retana for his detailed review and suggestions for the
improvement of this document. improvement of this document.
7. References 8. References
7.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
DOI 10.17487/RFC2328, April 1998, DOI 10.17487/RFC2328, April 1998,
<https://www.rfc-editor.org/info/rfc2328>. <https://www.rfc-editor.org/info/rfc2328>.
skipping to change at page 8, line 46 skipping to change at page 9, line 10
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8362] Lindem, A., Roy, A., Goethals, D., Reddy Vallem, V., and [RFC8362] Lindem, A., Roy, A., Goethals, D., Reddy Vallem, V., and
F. Baker, "OSPFv3 Link State Advertisement (LSA) F. Baker, "OSPFv3 Link State Advertisement (LSA)
Extensibility", RFC 8362, DOI 10.17487/RFC8362, April Extensibility", RFC 8362, DOI 10.17487/RFC8362, April
2018, <https://www.rfc-editor.org/info/rfc8362>. 2018, <https://www.rfc-editor.org/info/rfc8362>.
7.2. Informative References 8.2. Informative References
[I-D.ietf-idr-bgp-ls-segment-routing-ext] [I-D.ietf-idr-bgp-ls-segment-routing-ext]
Previdi, S., Talaulikar, K., Filsfils, C., Gredler, H., Previdi, S., Talaulikar, K., Filsfils, C., Gredler, H.,
and M. Chen, "BGP Link-State extensions for Segment and M. Chen, "BGP Link-State extensions for Segment
Routing", draft-ietf-idr-bgp-ls-segment-routing-ext-16 Routing", draft-ietf-idr-bgp-ls-segment-routing-ext-16
(work in progress), June 2019. (work in progress), June 2019.
[RFC3101] Murphy, P., "The OSPF Not-So-Stubby Area (NSSA) Option", [RFC3101] Murphy, P., "The OSPF Not-So-Stubby Area (NSSA) Option",
RFC 3101, DOI 10.17487/RFC3101, January 2003, RFC 3101, DOI 10.17487/RFC3101, January 2003,
<https://www.rfc-editor.org/info/rfc3101>. <https://www.rfc-editor.org/info/rfc3101>.
skipping to change at page 9, line 37 skipping to change at page 10, line 4
Email: wangaj3@chinatelecom.cn Email: wangaj3@chinatelecom.cn
Acee Lindem Acee Lindem
Cisco Systems Cisco Systems
301 Midenhall Way 301 Midenhall Way
Cary, NC 27513 Cary, NC 27513
USA USA
Email: acee@cisco.com Email: acee@cisco.com
Jie Dong Jie Dong
Huawei Technologies Huawei Technologies
Beijing Beijing
China China
Email: jie.dong@huawei.com Email: jie.dong@huawei.com
Peter Psenak Peter Psenak
Cisco Systems Cisco Systems
Pribinova Street 10 Pribinova Street 10
Bratislava, Eurovea Centre, Central 3 81109 Bratislava, Eurovea Centre, Central 3 81109
Slovakia Slovakia
Email: ppsenak@cisco.com Email: ppsenak@cisco.com
Ketan Talaulikar Ketan Talaulikar (editor)
Cisco Systems Cisco Systems
India India
Email: ketant@cisco.com Email: ketant@cisco.com
 End of changes. 21 change blocks. 
47 lines changed or deleted 60 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/