--- 1/draft-ietf-opsawg-oam-overview-04.txt 2011-05-16 11:15:43.000000000 +0200 +++ 2/draft-ietf-opsawg-oam-overview-05.txt 2011-05-16 11:15:43.000000000 +0200 @@ -1,23 +1,23 @@ Operations and Management Area Working Group T. Mizrahi Internet Draft Marvell Intended status: Informational N. Sprecher -Expires: September 2011 Nokia Siemens Networks +Expires: November 2011 Nokia Siemens Networks E. Bellagamba Ericsson Y. Weingarten Nokia Siemens Networks - March 29, 2011 + May 16, 2011 An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms - draft-ietf-opsawg-oam-overview-04.txt + draft-ietf-opsawg-oam-overview-05.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. @@ -26,21 +26,21 @@ 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 September 29, 2011. + This Internet-Draft will expire on November 16, 2011. 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 publication of this document. Please review these documents @@ -402,21 +402,21 @@ A wide variety of terms is used in various OAM standards. Each of the OAM standards listed in the reference section includes a section that defines the relevant terms. A thesaurus of terminology for MPLS-TP terms is presented in [MPLS-TP Term], and provides a good summary of some of the OAM related terminology. This section presents a comparison of the terms used in various OAM standards, without fully quoting the definition of each term. For a formal definition of each term, refer to the references at the end of this document. The comparison focuses on three basic terms, and is - summarized in section 3 ..2.6. + summarized in section 3.2.6. 3.2.2. OAM Maintenance Entities and Communication Links A Maintenance Entity (ME) is a point-to-point relationship between two Maintenance Points (MP). The connectivity between these Maintenance Points is managed and monitored by the OAM protocol. A pair of MPs engaged in an ME are connected by a communication Link. The term "Link" in this context is a generic term that may refer to one of several types of connection, e.g. a single physical @@ -699,22 +699,22 @@ PW, it is the responsibility of the operator to set consistent options at both ends. 4.5. IP Performance Metrics (IPPM) 4.5.1. Overview The IPPM working group [IPPM FW] in the IETF defines common criteria and metrics for measuring performance of IP traffic. Some of the key RFCs published by this working group have defined metrics for - measuring connectivity [rfc2678], delay [RFC2679, RFC 2681], and - packet loss [RFC2681]. + measuring connectivity [IPPM Con], delay ([IPPM 1DM], [IPPM 2DM]), + and packet loss [IPPM 1LM]. The IPPM working group has defined not only metrics for performance measurement, but also protocols that define how the measurement is carried out. The One-way Active Measurement Protocol [OWAMP] and the Two-Way Active Measurement Protocol [TWAMP] define a method and protocol for measuring delay and packet loss in IP networks. OWAMP [OWAMP] enables measurement of one-way characteristics of IP networks, such as one-way packet loss and one-way delay. For its proper operation OWAMP requires accurate time of day setting at its @@ -813,21 +813,21 @@ frames are sent proactively at a rate of 1 per second. Each frame contains the Trail-Termination Source Identifier (TTSI), indicating the identity of the transmitting LSR. The CV function can detect any of the following defect conditions. o Loss of Connectivity Verification (LOCV): A loss of connectivity is detected when no CV OAM packets are received in a period of 3 consecutive transmission periods. It should be noted that the LOCV defect is in fact loss of - continuity when using the terminology defined in 3 ..2.4. + continuity when using the terminology defined in 3.2.4. o TTSI Mismatch: A TTSI mismatch is detected when a CV frame with an unexpected TTSI is received. o TTSI Mismerge: A TTSI mismerge is detected when the CV frames received in a given LSP contain some frame with an expected TTSI, and some frames with an unexpected TTSI. o Excess: An excess is detected when at least 5 CV frames are received during a period of 3 consecutive transmission periods. @@ -1376,23 +1376,20 @@ There are no new IANA considerations implied by this document. 7. Acknowledgments This document was prepared using 2-Word-v2.0.template.dot. 8. References 8.1. Normative References - [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, March 1997. - [LSP Ping] Kompella, K., Swallow, G., "Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures", RFC 4379, February 2006. [MPLS OAM] Nadeau, T., Morrow, M., Swallow, G., Allan, D., and Matsushima, S., "Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks", RFC 4377, February 2006. [MPLS OAM FW] Allan, D., Nadeau, T., "A Framework for Multi-Protocol @@ -1412,20 +1409,24 @@ [MPLS-TP OAM] Vigoureux, M., Ward, D., Betts, M., "Requirements for OAM in MPLS Transport Networks", RFC 5860, May 2010. [G-ACh] Bocci, M., Vigoureux, M., Bryant, S., "MPLS Generic Associated Channel", RFC 5586, June 2009. [VCCV] Nadeau, T., Pignataro, C., "Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires", RFC 5085, December 2007. + [PW ACH] Bryant, S., Swallow, G., Martini, L., McPherson, D., + "Pseudowire Emulation Edge-to-Edge (PWE3) Control Word + for Use over an MPLS PSN", RFC 4385, February 2006. + [ICMPv4] Postel, J., "Internet Control Message Protocol", STD 5, RFC 792, September 1981. [ICMPv6] Conta, A., Deering, S., and M. Gupta, "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification", RFC 4443, March 2006. [IPPM FW] Paxson, V., Almes, G., Mahdavi, J., and Mathis, M., "Framework for IP Performance Metrics", RFC 2330, May 1998. @@ -1491,24 +1492,24 @@ [OAM Soup] Andersson, L., Van Helvoort, H., Bonica, R., Romascanu, D., Mansfield, S., " Guidelines for the use of the OAM acronym in the IETF ", work-in-progress, draft-ietf- opsawg-mpls-tp-oam-def, September, 2010. [OAM Analysis] Sprecher, N., Bellagamba, E., Weingarten, Y., "OAM functions in MPLS based transport network", work-in- progress, draft-ietf-mpls-tp-oam-analysis, January, 2011. - [MPLS-TP OAM FW] Busi, I., Niven-Jenkins, B., Allan, D., " - Operations, Administration and Maintenance Framework - for MPLS-based Transport Networks ", work-in-progress, - draft-ietf-mpls-tp-oam-framework, February, 2011. + [MPLS-TP OAM FW] Busi, I., Niven-Jenkins, B., Allan, D., "Operations, + Administration and Maintenance Framework for MPLS- + based Transport Networks ", work-in-progress, draft- + ietf-mpls-tp-oam-framework, February, 2011. [MPLS-TP Term]Van Helvoort, H., Andersson, L., Sprecher, N., "A Thesaurus for the Terminology used in Multiprotocol Label Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's Transport Network Recommendations", work-in-progress, draft-ietf-mpls- tp-rosetta-stone, November, 2010. [MPLS-TP Ping BFD] Bahadur, N., Aggarwal, R., Ward, D., Nadeau, T., Sprecher, N., Weingarten, Y., "LSP-Ping and BFD