TRILL Support of Point to Multipoint BFD
draft-ietf-trill-p2mp-bfd-02

The information below is for an old version of the document
Document Type Active Internet-Draft (trill WG)
Last updated 2016-05-23
Replaces draft-zhang-trill-p2mp-bfd
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd Donald Eastlake
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
TRILL                                                           M. Zhang
Internet-Draft                                       Huawei Technologies
Intended status: Standards Track                           S. Pallagatti
Expires: November 25, 2016                              Juniper Networks
                                                             V. Govindan
                                                           Cisco Systems
                                                            May 24, 2016

                TRILL Support of Point to Multipoint BFD
                      draft-ietf-trill-p2mp-bfd-02

Abstract

   Point to multipoint (P2MP) BFD is designed to verify multipoint
   connectivity.  This document specifies the support of P2MP BFD in
   TRILL.  Similar to TRILL point-to-point BFD, BFD Control packets in
   TRILL P2MP BFD are transmitted using RBridge Channel message.

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 December 11, 2015.

Copyright Notice

   Copyright (c) 2016 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
 

Zhang, et al.          Expires November 25, 2016                [Page 1]
Internet-Draft             P2MP BFD for TRILL               May 24, 2016

   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 . . . . . . . . . . . . . . . . . . .  2
     2.1.  Acronyms . . . . . . . . . . . . . . . . . . . . . . . . .  2
     2.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Bootstrapping  . . . . . . . . . . . . . . . . . . . . . . . .  3
   4.  A New RBridge Channel Message for P2MP BFD . . . . . . . . . .  3
   5.  Discriminators and Packet Demultiplexing . . . . . . . . . . .  4
   6.  Tracking Active Tails  . . . . . . . . . . . . . . . . . . . .  4
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . .  4
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  5
   10.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  5
     10.1.  Normative References  . . . . . . . . . . . . . . . . . .  5
     10.2.  Informative References  . . . . . . . . . . . . . . . . .  6
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  7

1.  Introduction

   TRILL supports multicast forwarding.  Applications based on TRILL
   multicast may need quick detection of multicast failures using P2MP
   BFD.  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 [I-D.ietf-trill-resilient-trees], the head needs
   to track the active status of tails
   [I-D.ietf-bfd-multipoint-active-tail].  If the tail loses
   connectivity of the new RBridge Channel message from the head, the
   tail should notify the head of the lack of multipoint connectivity
   with unicast BFD Control packets.  These unicast BFD Control packets
   are transmitted using the existing RBridge Channel message assigned
   to BFD Control [RFC7175].

2.  Acronyms and Terminology

2.1.  Acronyms

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

Zhang, et al.          Expires November 25, 2016                [Page 2]
Internet-Draft             P2MP BFD for TRILL               May 24, 2016

   BFD: Bidirectional Forwarding Detection

   P2MP: Point to Multi-Point
Show full document text