6375
INFORMATIONAL
A Packet Loss and Delay Measurement Profile for MPLS-Based Transport Networks
Authors: D. Frost, S. Bryant
Date: September 2011
Area: rtg
Working Group: mpls
Stream: IETF
Abstract
Procedures and protocol mechanisms to enable efficient and accurate measurement of packet loss, delay, and throughput in MPLS networks are defined in RFC 6374.
The MPLS Transport Profile (MPLS-TP) is the set of MPLS protocol functions applicable to the construction and operation of packet- switched transport networks.
This document describes a profile of the general MPLS loss, delay, and throughput measurement techniques that suffices to meet the specific requirements of MPLS-TP.
This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunication Union Telecommunication Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge (PWE3) architectures to support the capabilities and functionalities of a packet transport network as defined by the ITU-T. This document is not an Internet Standards Track specification; it is published for informational purposes.
RFC 6375
INFORMATIONAL
Internet Engineering Task Force (IETF) D. Frost, Ed.
Request for Comments: 6375 S. Bryant, Ed.
Category: Informational Cisco Systems
ISSN: 2070-1721 September 2011
<span class="h1">A Packet Loss and Delay Measurement Profile</span>
<span class="h1">for MPLS-Based Transport Networks</span>
Abstract
Procedures and protocol mechanisms to enable efficient and accurate
measurement of packet loss, delay, and throughput in MPLS networks
are defined in <a href="./rfc6374">RFC 6374</a>.
The MPLS Transport Profile (MPLS-TP) is the set of MPLS protocol
functions applicable to the construction and operation of packet-
switched transport networks.
This document describes a profile of the general MPLS loss, delay,
and throughput measurement techniques that suffices to meet the
specific requirements of MPLS-TP.
This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge
(PWE3) architectures to support the capabilities and functionalities
of a packet transport network as defined by the ITU-T.
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 <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc6375">http://www.rfc-editor.org/info/rfc6375</a>.
<span class="grey">Frost & Bryant Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc6375">RFC 6375</a> MPLS-TP Loss and Delay Measurement September 2011</span>
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Procedures for the measurement of packet loss, delay, and throughput
in MPLS networks are defined in [<a href="./rfc6374" title=""Packet Loss and Delay Measurement for MPLS Networks"">RFC6374</a>]. This document describes a
profile, i.e., a simplified subset, of these procedures that suffices
to meet the specific requirements of MPLS-based transport networks
[<a href="./rfc5921" title=""A Framework for MPLS in Transport Networks"">RFC5921</a>] as defined in [<a href="./rfc5860" title=""Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks"">RFC5860</a>]. This profile is presented for the
convenience of implementors who are concerned exclusively with the
transport network context.
The use of the profile specified in this document is purely optional.
Implementors wishing to provide enhanced functionality that is within
the scope of [<a href="./rfc6374" title=""Packet Loss and Delay Measurement for MPLS Networks"">RFC6374</a>] but outside the scope of this profile may do
so, whether or not the implementation is restricted to the transport
network context.
The assumption of this profile is that the devices involved in a
measurement operation are configured for measurement by a means
external to the measurement protocols themselves, for example, via a
Network Management System (NMS) or separate configuration protocol.
The manageability considerations in [<a href="./rfc6374" title=""Packet Loss and Delay Measurement for MPLS Networks"">RFC6374</a>] apply, and further
information on MPLS-TP network management can be found in [<a href="./rfc5950" title=""Network Management Framework for MPLS-based Transport Networks"">RFC5950</a>].
This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge
(PWE3) architectures to support the capabilities and functionalities
of a packet transport network as defined by the ITU-T.
<span class="grey">Frost & Bryant Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc6375">RFC 6375</a> MPLS-TP Loss and Delay Measurement September 2011</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. MPLS-TP Measurement Considerations</span>
The measurement considerations discussed in <a href="./rfc6374#section-2.9">Section 2.9 of [RFC6374]</a>
apply also in the context of MPLS-TP, except for the following, which
pertain to topologies excluded from MPLS-TP:
o Equal Cost Multipath considerations (<a href="./rfc6374#section-2.9.4">Section 2.9.4 of [RFC6374]</a>)
o Considerations for direct Loss Measurement (LM) in the presence of
Label Switched Paths constructed via the Label Distribution
Protocol (LDP) or utilizing Penultimate Hop Popping (<a href="./rfc6374#section-2.9.8">Section 2.9.8
of [RFC6374]</a>)
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Packet Loss Measurement (LM) Profile</span>
When an LM session is externally configured, the values of several
protocol parameters can be fixed in advance at the endpoints involved
in the session, so that negotiation of these parameters is not
required. These parameters, and their default values as specified by
this profile, are as follows:
Parameter Default Value
----------------------------------------- --------------------------
Query control code In-band Response Requested
Byte/packet Count (B) Flag Packet count
Traffic-class-specific (T) Flag Traffic-class-scoped
Origin Timestamp Format (OTF) Truncated IEEE 1588v2
A simple implementation may assume that external configuration will
ensure that both ends of the communication are using the default
values for these parameters. However, implementations are strongly
advised to validate the values of these parameters in received
messages so that configuration inconsistencies can be detected and
reported.
LM message rates (and test message rates, when inferred LM is used)
should be configurable by the network operator on a per-channel
basis. The following intervals should be supported:
Message Type Supported Intervals
-------------- ------------------------------------------------------
LM Message 100 milliseconds, 1 second, 10 seconds, 1 minute, 10
minutes
Test Message 10 milliseconds, 100 milliseconds, 1 second, 10
seconds, 1 minute
<span class="grey">Frost & Bryant Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc6375">RFC 6375</a> MPLS-TP Loss and Delay Measurement September 2011</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Packet Delay Measurement (DM) Profile</span>
When a DM session is externally configured, the values of several
protocol parameters can be fixed in advance at the endpoints involved
in the session, so that negotiation of these parameters is not
required. These parameters, and their default values as specified by
this profile, are as follows:
Parameter Default Value
------------------------------------------ --------------------------
Query control code In-band Response Requested
Querier Timestamp Format (QTF) Truncated IEEE 1588v2
Responder Timestamp Format (RTF) Truncated IEEE 1588v2
Responder's Preferred Timestamp Format Truncated IEEE 1588v2
(RPTF)
A simple implementation may assume that external configuration will
ensure that both ends of the communication are using the default
values for these parameters. However, implementations are strongly
advised to validate the values of these parameters in received
messages so that configuration inconsistencies can be detected and
reported.
DM message rates should be configurable by the network operator on a
per-channel basis. The following message intervals should be
supported: 1 second, 10 seconds, 1 minute, 10 minutes.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
This document delineates a subset of the procedures specified in
[<a href="./rfc6374" title=""Packet Loss and Delay Measurement for MPLS Networks"">RFC6374</a>], and as such introduces no new security considerations in
itself. The security considerations discussed in [<a href="./rfc6374" title=""Packet Loss and Delay Measurement for MPLS Networks"">RFC6374</a>] also
apply to the profile presented in this document. General
considerations for MPLS-TP network security can be found in
[<a href="#ref-SECURITY-FRAMEWORK">SECURITY-FRAMEWORK</a>].
<span class="grey">Frost & Bryant Informational [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc6375">RFC 6375</a> MPLS-TP Loss and Delay Measurement September 2011</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-RFC5860">RFC5860</a>] Vigoureux, M., Ward, D., and M. Betts, "Requirements for
Operations, Administration, and Maintenance (OAM) in MPLS
Transport Networks", <a href="./rfc5860">RFC 5860</a>, May 2010.
[<a id="ref-RFC6374">RFC6374</a>] Frost, D. and S. Bryant, "Packet Loss and Delay
Measurement for MPLS Networks", <a href="./rfc6374">RFC 6374</a>, September 2011.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-RFC5921">RFC5921</a>] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L.
Berger, "A Framework for MPLS in Transport Networks",
<a href="./rfc5921">RFC 5921</a>, July 2010.
[<a id="ref-RFC5950">RFC5950</a>] Mansfield, S., Gray, E., and K. Lam, "Network Management
Framework for MPLS-based Transport Networks", <a href="./rfc5950">RFC 5950</a>,
September 2010.
[<a id="ref-SECURITY-FRAMEWORK">SECURITY-FRAMEWORK</a>]
Fang, L., Niven-Jenkins, B., and S. Mansfield, "MPLS-TP
Security Framework", Work in Progress, May 2011.
Authors' Addresses
Dan Frost (editor)
Cisco Systems
EMail: [email protected]
Stewart Bryant (editor)
Cisco Systems
EMail: [email protected]
Frost & Bryant Informational [Page 5]
Annotations
Select text to annotate