MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators
RFC 7271

<draft-ietf-trill-address-flush-01.txt>

Abstract

  The TRILL (TRansparent Interconnection of Lots of Links) protocol, by
  default, learns end station addresses from observing the data plane.
  In particular, it learns local MAC addresses and edge switch port of
  attachment from the receipt of local data frames and learns remote
  MAC addresses and edge switch of attachment from the decapsulation of
  remotely sourced TRILL Data packets.

  This document specifies a message by which an originating TRILL
  switch can explicitly request other TRILL switches to flush certain
  MAC reachability learned through the decapsulation of TRILL Data
  packets. This is a supplement to the TRILL automatic address
  forgetting and can assist in achieving more rapid convergence in case
  of topology or configuration change.

Status of This Memo

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

  Distribution of this document is unlimited. Comments should be sent
  to the TRILL working group mailing list: trill@ietf.org.

  Internet-Drafts are working documents of the Internet Engineering
  Task Force (IETF), its areas, and its working groups.  Note that
  other groups may also distribute working documents as Internet-
  Drafts.

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

W. Hao, et al                                                  [Page 1]
INTERNET-DRAFT                                    Address Flush Message

  The list of current Internet-Drafts can be accessed at
  http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft
  Shadow Directories can be accessed at
  http://www.ietf.org/shadow.html.

W. Hao, et al                                                  [Page 2]
INTERNET-DRAFT                                    Address Flush Message

Table of Contents

      1. Introduction............................................4
      1.1 Terminology and Acronyms...............................4

      2. Address Flush Message Details...........................6
      2.1 VLAN Block Only Case...................................7
      2.2 Extensible Case........................................8
      2.2.1 Blocks of VLANs.....................................11
      2.2.2 Bit Map of VLANs....................................11
      2.2.3 Blocks of FGLs......................................12
      2.2.4 list of FGLs........................................12
      2.2.5 Big Map of FGLs.....................................13
      2.2.6 All Data Labels.....................................13
      2.2.7 MAC Address List....................................14
      2.2.8 MAC Address Blocks..................................14

      3. IANA Considerations....................................16
      3.1 Address Flush RBridge Channel Protocol Number.........16
      3.2 TRILL Address Flush TLV Types.........................16

      4. Security Considerations................................17

      Normative References......................................18
      Informative References....................................18

      Acknowledgements..........................................18

      Authors' Addresses........................................19

W. Hao, et al                                                  [Page 3]
INTERNET-DRAFT                                    Address Flush Message

1. Introduction

  Edge TRILL (Transparent Interconnection of Lots of Links) switches
  [RFC6325] [RFC7780], also called edge RBridges, by default learn end
  station MAC address reachability from observing the data plane. On
  receipt of a native frame from an end station, they would learn the
  local MAC address attachment of the source end station. And on
  egressing (decapsulating) a remotely originated TRILL Data packet,
  they learn the remote MAC address and remote attachment TRILL switch.
  Such learning is all scoped by data label (VLAN or Fine Grained Label
  [RFC7172]).

  TRILL has mechanisms for timing out such learning and appropriately
  clearing it based on some network connectivity and configuration
  changes; however, there are circumstances under which it would be
  helpful for a TRILL switch to be able to explicitly flush (purge)
  certain learned end station reachability information in remote
  RBridges to achieve more rapid convergence. For example, in the case
  of topology change or reconfiguration in a bridged network attached
  to multiple edge RBridges. Section 6.2 of [RFC4762] is another
  example of use of such a mechanism.

  A TRILL switch R1 can easily flush any locally learned addresses it
  wants. This document specifies an RBridge Channel protocol [RFC7178]
  message to request flushing address information learned from
  decapsulating at remote RBridges.

1.1 Terminology and Acronyms

  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 [RFC2119].

  This document uses the terms and acronyms defined in [RFC6325] and
  [RFC7978] as well as the following:

      Data Label - VLAN or FGL.

      Edge TRILL switch - A TRILL switch attached to one or more links
        that provide end station service.

      FGL - Fine Grained Label [RFC7172].

      Management VLAN - A VLAN in which all TRILL switches in a campus
        indicate interest so that multi-destination TRILL Data packets,
        including RBridge Channel messages [RFC7978], sent with that
        VLAN as the Inner.VLAN will be delivered to all TRILL switches
        in the campus. Usually no end station service is offered in the

W. Hao, et al                                                  [Page 4]
Received changes through RFC Editor sync (changed abstract to 'This document describes alternate mechanisms to perform some of the functions of MPLS Transport Profile (MPLS-TP) linear protection defined in RFC 6378, and also defines additional mechanisms. The purpose of these alternate and additional mechanisms is to provide operator control and experience that more closely models the behavior of linear protection seen in other transport networks.

This document also introduces capabilities and modes for linear protection. A capability is an individual behavior, and a mode is a particular combination of capabilities. Two modes are defined in this document: Protection State Coordination (PSC) mode and Automatic Protection Switching (APS) mode.

This document describes the behavior of the PSC protocol including priority logic and state machine when all the capabilities associated with the APS mode are enabled.

This document updates RFC 6378 in that the capability advertisement method defined here is an addition to that document.')