draft-ietf-ospf-lls-interface-id-08.txt   draft-ietf-ospf-lls-interface-id-09.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: April 14, 2019 W. Henderickx Expires: May 8, 2019 W. Henderickx
Nokia Nokia
P. Pillay-Esnault P. Pillay-Esnault
Huawei Huawei
October 11, 2018 November 4, 2018
OSPF LLS Extensions for Local Interface ID Advertisement OSPF LLS Extensions for Local Interface ID Advertisement
draft-ietf-ospf-lls-interface-id-08 draft-ietf-ospf-lls-interface-id-09
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 assigned Interface ID on the remote side of the useful to know the assigned Interface ID on the remote side of the
adjacency (Remote Interface ID). adjacency (Remote Interface ID).
This draft describes the extensions to OSPF link-local signalling This draft describes the extensions to OSPF link-local signalling
(LLS) to advertise the Local Interface Identifier. (LLS) to advertise the Local Interface Identifier.
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 April 14, 2019. This Internet-Draft will expire on May 8, 2019.
Internet-DrafOSPF Link Local Signalling (LLS) Extensions fo October 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
(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 44 skipping to change at page 2, line 42
7.2. Informative References . . . . . . . . . . . . . . . . . 6 7.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. [RFC2328] uses this identifies the interface on the router. [RFC2328] uses this
Interface ID in the Router-LSA Link Data for unnumbered links and Interface ID in the Router-LSA Link Data for unnumbered links and
uses the value of the MIB-II IfIndex [RFC2863]. [RFC4203] refers to uses the value of the MIB-II IfIndex [RFC2863]. [RFC4203] refers to
these Interface IDs as the Link Local/Remote Identifiers and defines these Interface IDs as the Link Local/Remote Identifiers and defines
a way to advertise and use and use them for Generalized Multi- a way to advertise and use them for Generalized Multi-Protocol Label
Protocol Label Switching (GMPLS) purposes. [RFC7684] defines a way Switching (GMPLS) purposes. [RFC7684] defines a way to advertise
to advertise Local/Remote Interface IDs in the OSPFv2 Extended Link Local/Remote Interface IDs in the OSPFv2 Extended Link LSA.
LSA.
There is a known OSPFv2 protocol problem in verifying the bi- There is a known OSPFv2 protocol problem in verifying the bi-
directional connectivity with parallel unnumbered links. If there directional connectivity with parallel unnumbered links. If there
are two parallel unnumbered links between a pair of routers and each are two parallel unnumbered links between a pair of routers and each
link is only advertised from single direction, such two link is only advertised from single direction, such two
unidirectional parallel links could be considered as a valid single unidirectional parallel links could be considered as a valid single
bidirectional link during the OSPF route computation on some other bidirectional link during the OSPF route computation on some other
Internet-DrafOSPF Link Local Signalling (LLS) Extensions fo October 2018
router. If each link is advertised with both its Local and Remote router. If each link is advertised with both its Local and Remote
Interface IDs, the advertisement of each link from both sides of Interface IDs, the advertisement of each link from both sides of
adjacency can be verified by cross-checking the Local and Remote adjacency can be verified by cross-checking the Local and Remote
Interface IDs of both advertisements. Interface IDs of both advertisements.
From the perspective of the advertising router, the Local Interface From the perspective of the advertising router, the Local Interface
Identifier is a known value, however the Remote Interface Identifier Identifier is a known value, however the Remote Interface Identifier
needs to be learnt before it can be advertised. [RFC4203] suggests needs to be learnt before it can be advertised. [RFC4203] suggests
to use TE Link Local LSA [RFC3630] to communicate the Local Interface to use TE Link Local LSA [RFC3630] to communicate the Local Interface
Identifier to neighbors on the link. Though such mechanism works, it Identifier to neighbors on the link. Though such mechanism works, it
skipping to change at page 4, line 5 skipping to change at page 4, line 5
point links between OSPF routers. point links between OSPF routers.
2. 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 and Database Description (DD) Interface Identifier in OSPF Hello and Database Description (DD)
packets. packets.
Internet-DrafOSPF Link Local Signalling (LLS) Extensions fo October 2018
2.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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 5 skipping to change at page 5, line 5
using LLS as described herein, they MUST 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.
Internet-DrafOSPF Link Local Signalling (LLS) Extensions fo October 2018
4. 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 value is allocated: Following value is allocated:
o TBD - Local Interface Identifier TLV o TBD - Local Interface Identifier TLV
skipping to change at page 5, line 36 skipping to change at page 5, line 34
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.
Receiving a malformed LLS Interface Identifier TLV MUST NOT result in Receiving a malformed LLS Interface Identifier TLV MUST NOT result in
a hard router or OSPF process failure. The reception of malformed 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- LLS TLVs or Sub-TLVs SHOULD be logged but such logging MUST be rate-
limited to prevent Denial-of-Service (DoS) attacks. limited to prevent Denial-of-Service (DoS) attacks.
The interface ID is assigned by the advertising OSPF router as a
locally unique identifier and need not be unique in any broader
context; it is not expected to contain any information about the
device owner or traffic transiting the device, so there are no
privacy oncerns associated with its advertisement.
6. Acknowledgments 6. Acknowledgments
Thanks to Tony Przygienda for his extensive review and useful Thanks to Tony Przygienda for his extensive review and useful
comments. comments.
7. References 7. References
7.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>.
Internet-DrafOSPF Link Local Signalling (LLS) Extensions fo October 2018
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, (TE) Extensions to OSPF Version 2", RFC 3630,
DOI 10.17487/RFC3630, September 2003, DOI 10.17487/RFC3630, September 2003,
<https://www.rfc-editor.org/info/rfc3630>. <https://www.rfc-editor.org/info/rfc3630>.
[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>.
skipping to change at page 6, line 43 skipping to change at page 7, line 4
[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>.
Authors' Addresses Authors' Addresses
Peter Psenak (editor) Peter Psenak (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
Apollo Business Center Apollo Business Center
Mlynske nivy 43 Mlynske nivy 43
Bratislava 821 09 Bratislava 821 09
Slovakia Slovakia
Email: ppsenak@cisco.com Email: ppsenak@cisco.com
Internet-DrafOSPF Link Local Signalling (LLS) Extensions fo October 2018
Ketan Jivan Talaulikar Ketan Jivan Talaulikar
Cisco Systems, Inc. Cisco Systems, Inc.
S.No. 154/6, Phase I, Hinjawadi S.No. 154/6, Phase I, Hinjawadi
PUNE, MAHARASHTRA 411 057 PUNE, MAHARASHTRA 411 057
India India
Email: ketant@cisco.com Email: ketant@cisco.com
Wim Henderickx Wim Henderickx
Nokia Nokia
 End of changes. 12 change blocks. 
22 lines changed or deleted 13 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/