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

The information below is for an old version of the document
Document Type Active Internet-Draft (ospf WG)
Last updated 2017-07-07 (latest revision 2017-05-24)
Replaces draft-ppsenak-ospf-lls-interface-id
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Open Shortest Path First IGP                              P. Psenak, Ed.
Internet-Draft                                             K. Talaulikar
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: November 25, 2017                                 W. Henderickx
                                                                   Nokia
                                                       P. Pillay-Esnault
                                                                  Huawei
                                                            May 24, 2017

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

Abstract

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

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 http://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 November 25, 2017.

Copyright Notice

   Copyright (c) 2017 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

Psenak, et al.          Expires November 25, 2017               [Page 1]
Internet-Draft    OSPF LLS Extensions for Interface ID          May 2017

   (http://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 . . . . . . . . . .   2
   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  . . . . . . . . . . . . . . . . . . . . . . . .   4
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Every 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 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 signaling (LLS)
   [RFC5613] to advertise the Local Interface Identifier.

2.  Interface ID Exchange using TE Opaque LSA

   Usage of the Link Local TE Opaque LSA to propagate the Local
   Interface Identifier to the neighbors on the link is described in
   [RFC4203].  This mechanism has following problems:

      LSAs can only be flooded over an existing adjacency that is in
      Exchange state or greater.  The adjacency state machine progresses

Psenak, et al.          Expires November 25, 2017               [Page 2]
Internet-Draft    OSPF LLS Extensions for Interface ID          May 2017

      independently on each side of the adjacency and, as such, may
      reach the Full state on one side before the TE Link Opaque LSA
      arrives.  The consequence is that link can be initially advertised
Show full document text