Rbridges: Bidirectional Forwarding Detection (BFD) support for TRILL
draft-ietf-trill-rbridge-bfd-02

The information below is for an old version of the document
Document Type Active Internet-Draft (trill WG)
Last updated 2012-01-24 (latest revision 2011-10-31)
Replaces draft-manral-trill-bfd-encaps
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          V. Manral
Internet-Draft                                       Hewlett Packard Co.
Intended status: Standards-Track                             D. Eastlake
Expires: July 27, 2012                                    Huawei R&D USA
                                                                 D. Ward
                                                             A. Banerjee
                                                           Cisco Systems
                                                        January 24, 2012

  Rbridges: Bidirectional Forwarding Detection (BFD) support for TRILL
                    draft-ietf-trill-rbridge-bfd-02

Abstract

   This document specifies use of the BFD (Bidirectional Forwarding
   Detection) protocol in RBridge campuses based on the Rbridge Channel
   extension to the the TRILL (TRansparent Interconnection of Lots of
   Links) protocol.

   BFD is a widely deployed OAM (Operations, Administration, and
   Maintenance) mechanism in IP and MPLS networks, using UDP and ACH
   encapsulation respectively.  This document specifies the BFD
   encapsulation over TRILL.

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 [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 July 27, 2012.

Manral, et al.            Expires July 27, 2012                 [Page 1]

Internet-Draft           BFD TRILL Encapsulation            January 2012

Copyright Notice

   Copyright (c) 2012 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  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  BFD over TRILL  . . . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Sessions and Initialization . . . . . . . . . . . . . . . . . . 4
   5.  Relationship to MPLS OAM  . . . . . . . . . . . . . . . . . . . 5
   6.  TRILL BFD Control Protocol  . . . . . . . . . . . . . . . . . . 5
   7.  One-Hop TRILL BFD Control . . . . . . . . . . . . . . . . . . . 6
   8.  BFD Control Frame Processing  . . . . . . . . . . . . . . . . . 6
   9.  TRILL BFD Echo Protocol . . . . . . . . . . . . . . . . . . . . 7
     9.1.  BFD Echo Frame Processing . . . . . . . . . . . . . . . . . 7
   10. Management and Operations Considerations  . . . . . . . . . . . 8
   11. Security Considerations . . . . . . . . . . . . . . . . . . . . 8
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
   13. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 8
   14. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 9
     14.1. Normative References  . . . . . . . . . . . . . . . . . . . 9
     14.2. Informative References  . . . . . . . . . . . . . . . . . . 9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

Manral, et al.            Expires July 27, 2012                 [Page 2]

Internet-Draft           BFD TRILL Encapsulation            January 2012

1.  Introduction

   Faster convergence is a critical feature of TRILL networks.  The
   TRILL IS-IS Hellos used between RBridges provide a basic neighbor and
   continuity check for TRILL links.  However, failure detection by non-
   receipt of such Hellos is based on the holding time parameter that is
   commonly set to a value of tens of seconds and, in any case, has a
   minimum expressible value of one second.
Show full document text