draft-ietf-ospf-lls-interface-id-07.txt   draft-ietf-ospf-lls-interface-id-08.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 13, 2019 W. Henderickx Expires: April 14, 2019 W. Henderickx
Nokia Nokia
P. Pillay-Esnault P. Pillay-Esnault
Huawei Huawei
October 10, 2018 October 11, 2018
OSPF LLS Extensions for Local Interface ID Advertisement OSPF LLS Extensions for Local Interface ID Advertisement
draft-ietf-ospf-lls-interface-id-07 draft-ietf-ospf-lls-interface-id-08
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 to This draft describes the extensions to OSPF link-local signalling
advertise the Local Interface Identifier. (LLS) to 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
capitals, as shown here. capitals, as shown here.
Status of This Memo Status of This Memo
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 13, 2019. This Internet-Draft will expire on April 14, 2019.
Internet-DrafOSPF Link Local Signalling (LLS) Extensions fo October 2018 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
skipping to change at page 2, line 31 skipping to change at page 2, line 31
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Interface ID Exchange using TE Opaque LSA . . . . . . . . 3 1.1. Interface ID Exchange using TE Opaque LSA . . . . . . . . 3
2. Interface ID Exchange using OSPF LLS . . . . . . . . . . . . 3 2. Interface ID Exchange using OSPF LLS . . . . . . . . . . . . 3
2.1. Local Interface Identifier TLV . . . . . . . . . . . . . 4 2.1. Local Interface Identifier TLV . . . . . . . . . . . . . 4
3. Backward Compatibility with RFC 4203 . . . . . . . . . . . . 4 3. Backward Compatibility with RFC 4203 . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . 5
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
skipping to change at page 3, line 19 skipping to change at page 3, line 19
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
has some drawbacks. has some drawbacks.
This draft proposes an extension to OSPF link-local signalling This draft proposes an extension to OSPF link-local signalling (LLS)
[RFC5613] to advertise the Local Interface Identifier. [RFC5613] to advertise the Local Interface Identifier.
1.1. 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 the 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
skipping to change at page 5, line 36 skipping to change at page 5, line 36
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.
6. Acknowledgements 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,
skipping to change at page 7, line 19 skipping to change at page 7, line 19
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
Copernicuslaan 50 Copernicuslaan 50
Antwerp 2018 Antwerp 2018
BE Belgium
Email: wim.henderickx@nokia.com Email: wim.henderickx@nokia.com
Padma Pillay-Esnault Padma Pillay-Esnault
Huawei Huawei
2330 Central Expressway 2330 Central Expressway
Santa Clara, CA 95050 Santa Clara, CA 95050
USA USA
Email: padma@huawei.com Email: padma@huawei.com
 End of changes. 9 change blocks. 
10 lines changed or deleted 10 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/