MPLS Working Group Y.Koike, Ed.
Internet Draft T.Hamano
M.Namiki
NTT
Intended status: Informational
Expires: August 24, 2013 February 25, 2013
Framework for Point-to-Multipoint MPLS-TP OAM
draft-hmk-mpls-tp-p2mp-oam-framework-02.txt
Status of this Memo
This Internet-Draft is submitted to IETF 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 August 24, 2013.
Copyright Notice
Copyright (c) 2011 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
Koike, et al. Expires August 24, 2013 [Page 1]
Internet-Draft MPLS-TP p2mp OAM framework February 2013
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.
Abstract
The MPLS transport profile (MPLS-TP) is being standardized to enable
carrier-grade packet transport.
This document discusses and specifies the P2MP framework primarily
related to OAM and related management in MPLS-TP networks. This
document mainly refers to RFC5654 and RFC6371. The main focus is on
the details that are not covered or not clarified in relevant RFCs
such as RFC5654, RFC5860, RFC5921, RFC5951, RFC6371, and draft-mpls-
tp-p2mp-framework.
Note: This I-D was made and updated including the discussions in ITU-
T SG15, which were described in Liaison Statements such as
(https://datatracker.ietf.org/liaison/1235/)
This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunications Union Telecommunications
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network.
Table of Contents
1. Introduction ................................................ 3
2. Conventions used in this document............................ 4
2.1. Terminology ............................................ 4
2.2. Definitions ............................................ 4
3. P2MP OAM .................................................... 5
3.1. OAM functions for proactive monitoring .................. 8
3.1.1. Continuity Check and Connectivity Verification..... 11
3.1.2. Remote Defect Indication .......................... 11
3.1.3. Alarm Reporting ................................... 12
Koike, et al. Expires May 8, 2013 [Page 2]
Internet-Draft MPLS-TP p2mp OAM framework February 2013
3.1.4. Lock Reporting .................................... 12
3.1.5. Packet Loss Measurement ........................... 12
3.1.6. Packet Delay Measurement .......................... 12
3.1.7. Client Failure Indication ......................... 12
3.2. OAM functions for on-demand monitoring ................. 12
3.2.1. Connectivity verification ......................... 12
3.2.2. Packet loss measurement ........................... 13
3.2.3. Diagnostic tests .................................. 13
3.2.4. Route Tracing ..................................... 13
3.2.5. Packet delay measurement .......................... 13
3.3. OAM functions for administration control ............... 13
datatracker.ietf.org