Advertising L2 Bundle Member Link Attributes in IS-IS
draft-ietf-isis-l2bundles-03

Document Type Active Internet-Draft (isis WG)
Last updated 2017-02-22 (latest revision 2017-02-20)
Replaces draft-ginsberg-isis-l2bundles
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd Hannes Gredler
Shepherd write-up Show (last changed 2017-03-06)
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to "Hannes Gredler" <hannes@gredler.at>
Networking Working Group                                     L. Ginsberg
Internet-Draft                                               A. Bashandy
Intended status: Standards Track                             C. Filsfils
Expires: August 25, 2017                                      S. Previdi
                                                           Cisco Systems
                                                              M. Nanduri
                                                               Microsoft
                                                                E. Aries
                                                     Private Contributer
                                                       February 21, 2017

         Advertising L2 Bundle Member Link Attributes in IS-IS
                    draft-ietf-isis-l2bundles-03.txt

Abstract

   There are deployments where the Layer 3 interface on which IS-IS
   operates is a Layer 2 interface bundle.  Existing IS-IS
   advertisements only support advertising link attributes of the Layer
   3 interface.  If entities external to IS-IS 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 IS-IS 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", "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."

Ginsberg, et al.         Expires August 25, 2017                [Page 1]
Internet-Draft               isis-l2bundles                February 2017

   This Internet-Draft will expire on August 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
   (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.  L2 Bundle Member Attributes TLV . . . . . . . . . . . . . . .   3
     2.1.  Parallel L3 Adjacencies . . . . . . . . . . . . . . . . .   5
     2.2.  Shared Attribute sub-TLVs . . . . . . . . . . . . . . . .   5
   3.  Advertising L2 Bundle Member Adj-SIDs . . . . . . . . . . . .   5
     3.1.  L2 Bundle Member Adjacency Segment Identifier sub-TLV . .   6
     3.2.  L2 Bundle Member LAN Adjacency Segment Identifier sub-TLV   7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     7.2.  Informational References  . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   There are deployments where the Layer 3 interface on which an IS-IS
   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 IS-IS such as Path Computation
   Elements (PCE) [RFC4655] may wish to control traffic flows on
Show full document text