TRILL working Group Rohit Watve
Internet Draft Tissa Senevirathne
Intended status: Standards Track Chandan Mishra
CISCO
Gayatri Ramachandran
ARISTA Networks
February 4, 2013
Expires: July 2013
Pro-active connectivity monitoring for TRILL
draft-rohit-trill-proactive-oam-02.txt
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), 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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on July 4, 2013.
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
<Lastname> Expires July 4 2013 [Page 1]
Internet-Draft draft-rohit-trill-proactive-oam February 2013
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.
Abstract
Pro-active fault monitoring for TRILL monitors all the paths between
any two given RBridges in the network. Number of paths to be
monitored can be of exponential order based on the distance between
two RBridges. In this document novel fault monitoring mechanism
based on a distributed approach is presented.
Table of Contents
1. Introduction...................................................2
2. Conventions used in this document..............................3
3. Motivation.....................................................3
4. Solution overview..............................................6
4.1. Details for monitoring paths upto 2nd hop Rbridge.........8
5. Frame formats..................................................9
5.1.1. Pro-active fault monitoring request..................9
5.1.2. Pro-active Payload discovery request................10
5.1.3. Pro-active Payload discovery response...............12
5.1.4. Pro-active fault notification.......................13
6. Formal Syntax.................................................16
7. Security Considerations.......................................16
8. IANA Considerations...........................................16
9. Conclusions...................................................16
10. References...................................................16
10.1. Normative References....................................17
10.2. Informative References..................................17
11. Acknowledgments..............................................17
Appendix A. Sample report........................................19
A.1. Summary Report per monitor...............................19
A.2. Detail Report............................................19
A.2.1. <H2>................................................20
A.2.1.1. <H3>...........................................20
A.2.1.1.1. <H4>......................................20
A.2.1.1.1.1. <H5>.................................20
A.3. C type usage is messages.................................20
1. Introduction
Pro-active fault monitoring is necessary for all OAM solutions. It
gives network service providers confidence about the health of their
<Lastname> Expires July 4, 2013 [Page 2]
datatracker.ietf.org