OSPF LLS Extensions for Local Interface ID Advertisement
draft-ietf-ospf-lls-interface-id-05

Document Type Active Internet-Draft (lsr WG)
Last updated 2018-07-18
Replaces draft-ppsenak-ospf-lls-interface-id
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Yingzhen Qu
Shepherd write-up Show (last changed 2018-07-08)
IESG IESG state Publication Requested
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to Yingzhen Qu <yingzhen.ietf@gmail.com>
Open Shortest Path First IGP                              P. Psenak, Ed.
Internet-Draft                                             K. Talaulikar
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: January 19, 2019                                  W. Henderickx
                                                                   Nokia
                                                       P. Pillay-Esnault
                                                                  Huawei
                                                           July 18, 2018

        OSPF LLS Extensions for Local Interface ID Advertisement
                  draft-ietf-ospf-lls-interface-id-05

Abstract

   Every OSPF interface is assigned an identifier, Interface ID, which
   uniquely identifies the interface on the router.  In some cases it is
   useful to know the Interface ID assigned by the adjacent router on
   its side of the adjacency (Remote Interface ID).

   This draft describes the extensions to OSPF link-local signalling to
   advertise the Local Interface Identifier.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 19, 2019.

Psenak, et al.          Expires January 19, 2019                [Page 1]
Internet-DraOSPF Link Local Signalling (LLS) Extensions for I  July 2018

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Interface ID Exchange using TE Opaque LSA . . . . . . . . . .   3
   3.  Interface ID Exchange using OSPF LLS  . . . . . . . . . . . .   3
     3.1.  Local Interface Identifier TLV  . . . . . . . . . . . . .   3
   4.  Backward Compatibility with RFC 4203  . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Every OSPF interface is assigned an Interface ID, which uniquely
   identifies the interface on the router.  For example, some
   implementations MAY be able to use the MIB-II IfIndex [RFC2863] as
   the Interface ID.

   Local/Remote Interface Identifiers MAY be flooded by OSPF [RFC2328]
   as defined in [RFC4203].  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
   [RFC5613] to advertise the Local Interface Identifier.

Psenak, et al.          Expires January 19, 2019                [Page 2]
Internet-DraOSPF Link Local Signalling (LLS) Extensions for I  July 2018

2.  Interface ID Exchange using TE Opaque LSA
Show full document text