draft-ietf-ospf-lls-interface-id-05.txt   draft-ietf-ospf-lls-interface-id-06.txt 
Open Shortest Path First IGP P. Psenak, Ed. Open Shortest Path First IGP P. Psenak, Ed.
Internet-Draft K. Talaulikar Internet-Draft K. Talaulikar
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: January 19, 2019 W. Henderickx Expires: March 28, 2019 W. Henderickx
Nokia Nokia
P. Pillay-Esnault P. Pillay-Esnault
Huawei Huawei
July 18, 2018 September 24, 2018
OSPF LLS Extensions for Local Interface ID Advertisement OSPF LLS Extensions for Local Interface ID Advertisement
draft-ietf-ospf-lls-interface-id-05 draft-ietf-ospf-lls-interface-id-06
Abstract Abstract
Every OSPF interface is assigned an identifier, Interface ID, which Every OSPF interface is assigned an identifier, Interface ID, which
uniquely identifies the interface on the router. In some cases it is uniquely identifies the interface on the router. In some cases it is
useful to know the Interface ID assigned by the adjacent router on useful to know the assigned Interface ID on the remote side of the
its side of the adjacency (Remote Interface ID). adjacency (Remote Interface ID).
This draft describes the extensions to OSPF link-local signalling to This draft describes the extensions to OSPF link-local signalling to
advertise the Local Interface Identifier. advertise the Local Interface Identifier.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
BCP14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP14 [RFC2119] [RFC8174] when, and only when, they appear in all
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 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 January 19, 2019. This Internet-Draft will expire on March 28, 2019.
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
(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
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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Interface ID Exchange using TE Opaque LSA . . . . . . . . . . 3 1.1. Interface ID Exchange using TE Opaque LSA . . . . . . . . 3
3. Interface ID Exchange using OSPF LLS . . . . . . . . . . . . 3 2. Interface ID Exchange using OSPF LLS . . . . . . . . . . . . 3
3.1. Local Interface Identifier TLV . . . . . . . . . . . . . 3 2.1. Local Interface Identifier TLV . . . . . . . . . . . . . 4
4. Backward Compatibility with RFC 4203 . . . . . . . . . . . . 4 3. Backward Compatibility with RFC 4203 . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . 5
9.1. Normative References . . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
Every OSPF interface is assigned an Interface ID, which uniquely Every OSPF interface is assigned an Interface ID, which uniquely
identifies the interface on the router. For example, some identifies the interface on the router. [RFC2328] uses this
implementations MAY be able to use the MIB-II IfIndex [RFC2863] as Interface ID in the Router-LSA Link Data for unnumbered links and
the Interface ID. uses the value of the MIB-II IfIndex [RFC2863]. [RFC4203] refers to
these Interface IDs as the Link Local/Remote Identifiers and defines
a way to advertise and use and use them for Generalized Multi-
Protocol Label Switching (GMPLS) purposes. [RFC7684] defines a way
to advertise Local/Remote Interface IDs in the OSPFv2 Extended Link
LSA.
Local/Remote Interface Identifiers MAY be flooded by OSPF [RFC2328] There is a known OSPFv2 protocol problem in verifying the bi-
as defined in [RFC4203]. From the perspective of the advertising directional connectivity with parallel unnumbered links. If there
router, the Local Interface Identifier is a known value, however the are two parallel unnumbered links between a pair of routers and each
Remote Interface Identifier needs to be learnt before it can be link is only advertised from single direction, such two
advertised. [RFC4203] suggests to use TE Link Local LSA [RFC3630] to unidirectional parallel links could be considered as a valid single
communicate the Local Interface Identifier to neighbors on the link. bidirectional link during the OSPF route computation on some other
Though such mechanism works, it has some drawbacks. router. If each link is advertised with both its Local and Remote
Interface IDs, the advertisement of each link from both sides of
adjacency can be verified by cross-checking the Local and Remote
Interface IDs of both advertisements.
From the perspective of the advertising router, the Local Interface
Identifier is a known value, however the Remote Interface Identifier
needs to be learnt before it can be advertised. [RFC4203] suggests
to use TE Link Local LSA [RFC3630] to communicate the Local Interface
Identifier to neighbors on the link. Though such mechanism works, it
has some drawbacks.
This draft proposes an extension to OSPF link-local signalling This draft proposes an extension to OSPF link-local signalling
[RFC5613] to advertise the Local Interface Identifier. [RFC5613] to advertise the Local Interface Identifier.
2. Interface ID Exchange using TE Opaque LSA 1.1. Interface ID Exchange using TE Opaque LSA
Usage of the Link Local TE Opaque LSA to propagate the Local Usage of the Link Local TE Opaque LSA to propagate the Local
Interface Identifier to the neighbors on the link is described in Interface Identifier to the neighbors on the link is described in
[RFC4203]. This mechanism has following problems: [RFC4203]. This mechanism has the following problems:
LSAs can only be flooded over an existing adjacency that is in LSAs can only be flooded over an existing adjacency that is in
Exchange state or greater. The adjacency state machine progresses Exchange state or greater. The adjacency state machine progresses
independently on each side of the adjacency and, as such, may independently on each side of the adjacency and, as such, may
reach the Full state on one side before the TE Link Opaque LSA reach the Full state on one side before the TE Link Opaque LSA
arrives. The consequence is that link can be initially advertised arrives. The consequence is that link can be initially advertised
without the Remote Interface Identifier. Later, when the TE Link without the Remote Interface Identifier. Later, when the TE Link
Opaque LSA arrives, the link must be advertised again, this time Opaque LSA arrives, the link must be advertised again, this time
with the valid Remote Interface Identifier. Implementations may with the valid Remote Interface Identifier. Implementations may
choose to wait before advertising the link, but there is no choose to wait before advertising the link, but there is no
guarantee that the neighbor will ever advertise the TE Link Opaque guarantee that the neighbor will ever advertise the TE Link Opaque
LSA with the Interface Identifier. In summary, the existing LSA with the Interface Identifier. In summary, the existing
mechanism does not guarantee that the Remote Interface Identifier mechanism does not guarantee that the Remote Interface Identifier
is known at the time the link is advertised. is known at the time the link is advertised.
The TE Opaque LSA is defined for MPLS Traffic Engineering, but the The TE Opaque LSA is defined for MPLS Traffic Engineering, but the
knowledge of the Remote Interface Identifier is useful also for knowledge of the Remote Interface Identifier is useful also for
cases where MPLS TE is not used. One example is the lack of a cases where MPLS TE is not used. One example is the mentioned
valid 2-way connectivity check for parallel point-to-point links lack of a valid 2-way connectivity check for parallel point-to-
between OSPF routers. point links between OSPF routers.
3. Interface ID Exchange using OSPF LLS 2. Interface ID Exchange using OSPF LLS
To address the problems described earlier and to allow the Interface To address the problems described earlier and to allow the Interface
Identifier exchange to be part of the neighbor discovery process, we Identifier exchange to be part of the neighbor discovery process, we
propose to extend OSPF link-local signalling to advertise the Local propose to extend OSPF link-local signalling to advertise the Local
Interface Identifier in OSPF Hello packets. Interface Identifier in OSPF Hello and Database Description (DD)
packets.
3.1. Local Interface Identifier TLV 2.1. Local Interface Identifier TLV
The Local Interface Identifier TLV is a LLS TLV. It has following The Local Interface Identifier TLV is a LLS TLV. It has following
format: format:
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Interface Identifier | | Local Interface Identifier |
skipping to change at page 4, line 15 skipping to change at page 4, line 30
Type: 18 Type: 18
Length: 4 octets Length: 4 octets
Local Interface Identifier: The value of the local Interface Local Interface Identifier: The value of the local Interface
Identifier. Identifier.
Local Interface Identifier TLV signalling using LLS is applicable to Local Interface Identifier TLV signalling using LLS is applicable to
all OSPF interface types other than virtual links. all OSPF interface types other than virtual links.
4. Backward Compatibility with RFC 4203 3. Backward Compatibility with RFC 4203
Implementations which support Local Interface ID signalling using LLS If the Local Interface ID signaling via Link Local TE Opaque LSA is
MUST prefer the Local Interface ID value received through LLS over supported in addition to the new LLS mechanism, implementations which
the value received through Link Local TE Opaque LSA if both are support Local Interface ID signalling using LLS MUST prefer the Local
received from the same OSPF router. Interface ID value received through LLS over the value received
through the Link Local TE Opaque LSA if both are received from the
same OSPF router.
Implementations which support Local Interface ID signalling via Link Implementations which support Local Interface ID signalling via Link
Local TE Opaque LSA MAY continue to do so to ensure backward Local TE Opaque LSA MAY continue to do so to ensure backward
compatibility. If they also support Local Interface ID signalling compatibility. If they also support Local Interface ID signalling
using LLS as described herein, they SHOULD signal the same Local using LLS as described herein, they MUST signal the same Local
Interface ID via both mechanisms. Interface ID via both mechanisms.
During the rare conditions, when the Local Interface ID changes, a During the rare conditions, when the Local Interface ID changes, a
timing interval may exist, where the received values of the Local timing interval may exist, where the received values of the Local
Interface ID advertised through LLS and Link Local TE Opaque LSA may Interface ID advertised through LLS and Link Local TE Opaque LSA may
differ. Such situation is temporary and received values via both differ. Such situation is temporary and received values via both
mechanisms should become equal as soon as the next Hello and/or Link mechanisms should become equal as soon as the next Hello and/or Link
Local TE Opaque LSA is re-generated by the originator. Local TE Opaque LSA is re-generated by the originator.
5. IANA Considerations 4. IANA Considerations
This specification allocates a single code point from the "Open This specification allocates a single code point from the "Open
Shortest Path First (OSPF) Link Local Signalling (LLS) - Type/Length/ Shortest Path First (OSPF) Link Local Signalling (LLS) - Type/Length/
Value Identifiers (TLV)" registry. Value Identifiers (TLV)" registry.
Following values is allocated: Following value is allocated:
o 18 - Local Interface Identifier TLV o 18 - Local Interface Identifier TLV
6. Security Considerations 5. Security Considerations
The security considerations for "OSPF Link-Local Signaling" [RFC5613] The security considerations for "OSPF Link-Local Signaling" [RFC5613]
also apply to the Local Interface Identifier TLV described herein. also apply to the Local Interface Identifier TLV described herein.
The current usage of a neighbor's Local Interface Identifier is to The current usage of a neighbor's Local Interface Identifier is to
disambiguate parallel links between OSPF routers. Hence, disambiguate parallel links between OSPF routers. Hence,
modification of the advertised Local Interface Identifier TLV may modification of the advertised Local Interface Identifier TLV may
result in the wrong neighbor interface identifier being advertised in result in the wrong neighbor interface identifier being advertised in
the OSPFv2 Extended Link LSA [RFC8379] and could prevent the link the OSPFv2 Extended Link LSA [RFC7684] and could prevent the link
from being used. If authentication is being used in the OSPF routing from being used. If authentication is being used in the OSPF routing
domain [RFC5709], then the Cryptographic Authentication TLV [RFC5613] domain [RFC5709], then the Cryptographic Authentication TLV [RFC5613]
SHOULD also be used to protect that contents of the Link-Local SHOULD also be used to protect that contents of the Link-Local
Signaling (LLS) block. Signaling (LLS) block.
Implementations must assure that malformed LLS TLVs and Sub-TLVs Receiving a malformed LLS Interface Identifier TLV MUST NOT result in
permutations do not result in errors which cause hard OSPF failures. a hard router or OSPF process failure. The reception of malformed
LLS TLVs or Sub-TLVs SHOULD be logged but such logging MUST be rate-
7. Contributors limited to prevent Denial-of-Service (DoS) attacks.
8. Acknowledgements 6. Acknowledgements
Thanks to Tony Przygienda for his extensive review and useful Thanks to Tony Przygienda for his extensive review and useful
comments. comments.
9. References 7. References
9.1. Normative References 7.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 5, line 48 skipping to change at page 6, line 20
[RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in
Support of Generalized Multi-Protocol Label Switching Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005,
<https://www.rfc-editor.org/info/rfc4203>. <https://www.rfc-editor.org/info/rfc4203>.
[RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D. [RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D.
Yeung, "OSPF Link-Local Signaling", RFC 5613, Yeung, "OSPF Link-Local Signaling", RFC 5613,
DOI 10.17487/RFC5613, August 2009, DOI 10.17487/RFC5613, August 2009,
<https://www.rfc-editor.org/info/rfc5613>. <https://www.rfc-editor.org/info/rfc5613>.
[RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W.,
Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute
Advertisement", RFC 7684, DOI 10.17487/RFC7684, November
2015, <https://www.rfc-editor.org/info/rfc7684>.
[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>.
9.2. Informative References 7.2. Informative References
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,
<https://www.rfc-editor.org/info/rfc2863>. <https://www.rfc-editor.org/info/rfc2863>.
[RFC5709] Bhatia, M., Manral, V., Fanto, M., White, R., Barnes, M., [RFC5709] Bhatia, M., Manral, V., Fanto, M., White, R., Barnes, M.,
Li, T., and R. Atkinson, "OSPFv2 HMAC-SHA Cryptographic Li, T., and R. Atkinson, "OSPFv2 HMAC-SHA Cryptographic
Authentication", RFC 5709, DOI 10.17487/RFC5709, October Authentication", RFC 5709, DOI 10.17487/RFC5709, October
2009, <https://www.rfc-editor.org/info/rfc5709>. 2009, <https://www.rfc-editor.org/info/rfc5709>.
 End of changes. 27 change blocks. 
53 lines changed or deleted 75 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/