Advertising L2 Bundle Member Link Attributes in OSPF
draft-ketant-lsr-ospf-l2bundles-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

Link State Routing                                         K. Talaulikar
Internet-Draft                                                 P. Psenak
Intended status: Standards Track                           Cisco Systems
Expires: January 5, 2020                                    July 4, 2019

          Advertising L2 Bundle Member Link Attributes in OSPF
                   draft-ketant-lsr-ospf-l2bundles-00

Abstract

   There are deployments where the Layer 3 interface on which OSPF
   operates is a Layer 2 interface bundle.  Existing OSPF advertisements
   only support advertising link attributes of the Layer 3 interface.
   If entities external to OSPF wish to control traffic flows on the
   individual physical links which comprise the Layer 2 interface bundle
   link attribute information about the bundle members is required.

   This document introduces the ability for OSPF to advertise the link
   attributes of layer 2 (L2) Bundle members.

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 BCP
   14 [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 5, 2020.

Talaulikar & Psenak      Expires January 5, 2020                [Page 1]
Internet-Draft               OSPF L2 Bundles                   July 2019

Copyright Notice

   Copyright (c) 2019 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.  L2 Bundle Member Attributes . . . . . . . . . . . . . . . . .   3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     6.2.  Informational References  . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   There are deployments where the Layer 3 interface on which an OSPF
   adjacency is established is a Layer 2 interface bundle, for instance
   a Link Aggregation Group (LAG) [IEEE802.1AX] . This reduces the
   number of adjacencies which need to be maintained by the routing
   protocol in cases where there are parallel links between the
   neighbors.  Entities external to OSPF such as Path Computation
   Elements (PCE) [RFC4655] may wish to control traffic flows on
   individual members of the underlying Layer 2 bundle.  In order to do
   so link attribute information about individual bundle members is
   required.  The protocol extensions defined in this document provide
   the means to advertise this information.

   This document introduces new sub-TLVs to advertise link attribute
   information for each of the L2 Bundle members which comprise the
   Layer 3 interface on which OSPF operates.  Similar capabilities were
   introduced in IS-IS via [I-D.ietf-isis-l2bundles].

   [I-D.ietf-ospf-segment-routing-extensions] and
   [I-D.ietf-ospf-ospfv3-segment-routing-extensions] introduced the

Talaulikar & Psenak      Expires January 5, 2020                [Page 2]
Internet-Draft               OSPF L2 Bundles                   July 2019

   adjacency segment identifier (Adj-SID) link attribute for OSPFv2 and
   OSPFv3 respectively which can be used as an instruction to forwarding
   to send traffic over a specific link [RFC8402].  This document