Support of Point-to-Multipoint Bidirectional Forwarding Detection (BFD) in Transparent Interconnection of Lots of Links (TRILL)
RFC 8564

Document Type RFC - Proposed Standard (April 2019; No errata)
Last updated 2019-04-25
Replaces draft-zhang-trill-p2mp-bfd
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Susan Hares
Shepherd write-up Show (last changed 2017-11-16)
IESG IESG state RFC 8564 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alia Atlas
Send notices to "Susan Hares" <shares@ndzh.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                          M. Zhang
Request for Comments: 8564                           Huawei Technologies
Updates: 7175, 7177                                        S. Pallagatti
Category: Standards Track                                         Vmware
ISSN: 2070-1721                                              V. Govindan
                                                           Cisco Systems
                                                              April 2019

Support of Point-to-Multipoint Bidirectional Forwarding Detection (BFD)
        in Transparent Interconnection of Lots of Links (TRILL)

Abstract

   Point-to-multipoint (P2MP) Bidirectional Forwarding Detection (BFD)
   is designed to verify multipoint connectivity.  This document
   specifies the support of P2MP BFD in Transparent Interconnection of
   Lots of Links (TRILL).  Similar to TRILL point-to-point BFD, BFD
   Control packets in TRILL P2MP BFD are transmitted using RBridge
   Channel messages.  This document updates RFCs 7175 and 7177.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8564.

Zhang, et al.                Standards Track                    [Page 1]
RFC 8564                   P2MP BFD for TRILL                 April 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.  Acronyms and Terminology  . . . . . . . . . . . . . . . . . .   3
     2.1.  Acronyms  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Bootstrapping . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  A New RBridge Channel Message for P2MP BFD  . . . . . . . . .   4
   5.  Discriminators and Packet Demultiplexing  . . . . . . . . . .   4
   6.  Tracking Active Tails . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   TRILL supports multicast forwarding.  Applications based on TRILL
   multicast may need quick detection of multicast failures using P2MP
   BFD [RFC8562].  This document specifies TRILL support of P2MP BFD.

   To use P2MP BFD, the head end needs to periodically transmit BFD
   Control packets to all tails using TRILL multicast.  A new RBridge
   Channel message is allocated for this purpose.

   In order to execute the global protection of distribution used for
   multicast forwarding [TRILL-TREES], the head needs to track the
   active status of tails [RFC8563].  If the tail loses connectivity as
   detected by not receiving the new RBridge Channel message from the
   head, the tail should notify the head of the lack of multipoint

Zhang, et al.                Standards Track                    [Page 2]
RFC 8564                   P2MP BFD for TRILL                 April 2019

   connectivity with unicast BFD Control packets.  These unicast BFD
   Control packets are transmitted using the existing RBridge Channel
   message assigned to BFD Control [RFC7175].

   This document updates [RFC7177] as specified in Section 3 and updates
   [RFC7175] as specified in Sections 4 and 5.

2.  Acronyms and Terminology

2.1.  Acronyms

   Data Label:  VLAN or Fine-Grained Label [RFC7172].

   BFD:   Bidirectional Forwarding Detection
Show full document text