datatracker.ietf.org
Sign in
Version 5.6.2.p2, 2014-07-24
Report a bug

Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL)
RFC 6905

Internet Engineering Task Force (IETF)                   T. Senevirathne
Request for Comments: 6905                                         Cisco
Category: Informational                                          D. Bond
ISSN: 2070-1721                                                      IBM
                                                               S. Aldrin
                                                                   Y. Li
                                                                  Huawei
                                                                R. Watve
                                                                   Cisco
                                                              March 2013

   Requirements for Operations, Administration, and Maintenance (OAM)
        in Transparent Interconnection of Lots of Links (TRILL)

Abstract

   Operations, Administration, and Maintenance (OAM) is a general term
   used to identify functions and toolsets to troubleshoot and monitor
   networks.  This document presents OAM requirements applicable to the
   Transparent Interconnection of Lots of Links (TRILL).

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   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).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

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

Senevirathne, et al.          Informational                     [Page 1]
RFC 6905                 TRILL OAM Requirements               March 2013

Copyright Notice

   Copyright (c) 2013 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
      1.1. Scope ......................................................3
   2. Conventions Used in This Document ...............................3
   3. Terminology .....................................................3
   4. OAM Requirements ................................................4
      4.1. Data Plane .................................................4
      4.2. Connectivity Verification ..................................5
           4.2.1. Unicast .............................................5
           4.2.2. Distribution Trees ..................................5
      4.3. Continuity Check ...........................................5
      4.4. Path Tracing ...............................................6
      4.5. General Requirements .......................................6
      4.6. Performance Monitoring .....................................7
           4.6.1. Packet Loss .........................................7
           4.6.2. Packet Delay ........................................7
      4.7. ECMP Utilization ...........................................8
      4.8. Security and Operational Considerations ....................8
      4.9. Fault Indications ..........................................8
      4.10. Defect Indications ........................................9
      4.11. Live Traffic Monitoring ...................................9
   5. Security Considerations .........................................9
   6. References ......................................................9
      6.1. Normative References .......................................9
      6.2. Informative References ....................................10
   7. Acknowledgments ................................................11
   8. Contributors ...................................................11

Senevirathne, et al.          Informational                     [Page 2]
RFC 6905                 TRILL OAM Requirements               March 2013

1.  Introduction

   The Operations, Administration, and Maintenance (OAM) generally

[include full document text]