Advertising L2 Bundle Member Link Attributes in IS-IS
draft-ginsberg-isis-l2bundles-00

The information below is for an old version of the document
Document Type Active Internet-Draft (candidate for isis WG)
Last updated 2016-01-03 (latest revision 2015-07-06)
Replaced by draft-ietf-isis-l2bundles
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Networking Working Group                                     L. Ginsberg
Internet-Draft                                               A. Bashandy
Intended status: Standards Track                             C. Filsfils
Expires: January 7, 2016                                      S. Previdi
                                                           Cisco Systems
                                                              M. Nanduri
                                                               Microsoft
                                                                E. Aries
                                                                Facebook
                                                           July 06, 2015

         Advertising L2 Bundle Member Link Attributes in IS-IS
                  draft-ginsberg-isis-l2bundles-00.txt

Abstract

   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."

   This Internet-Draft will expire on January 7, 2016.

Copyright Notice

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

Ginsberg, et al.         Expires January 7, 2016                [Page 1]
Internet-Draft               isis-l2bundles                    July 2015

   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

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.  However, if there is still a desire to control traffic
   flows on individual physical links, information about each of the L2
Show full document text