draft-ietf-mpls-tp-loss-delay-profile-02.txt   draft-ietf-mpls-tp-loss-delay-profile-03.txt 
MPLS D. Frost, Ed. MPLS D. Frost, Ed.
Internet-Draft S. Bryant, Ed. Internet-Draft S. Bryant, Ed.
Intended status: Informational Cisco Systems Intended status: Informational Cisco Systems
Expires: August 8, 2011 February 4, 2011 Expires: October 22, 2011 April 20, 2011
A Packet Loss and Delay Measurement Profile for MPLS-based Transport A Packet Loss and Delay Measurement Profile for MPLS-based Transport
Networks Networks
draft-ietf-mpls-tp-loss-delay-profile-02 draft-ietf-mpls-tp-loss-delay-profile-03
Abstract Abstract
Procedures and protocol mechanisms to enable the efficient and Procedures and protocol mechanisms to enable the efficient and
accurate measurement of packet loss, delay, and throughput in MPLS accurate measurement of packet loss, delay, and throughput in MPLS
networks are defined in RFC XXXX. networks are defined in RFC XXXX.
The MPLS Transport Profile (MPLS-TP) is the set of MPLS protocol The MPLS Transport Profile (MPLS-TP) is the set of MPLS protocol
functions applicable to the construction and operation of packet- functions applicable to the construction and operation of packet-
switched transport networks. switched transport networks.
skipping to change at page 2, line 13 skipping to change at page 2, line 13
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 8, 2011. This Internet-Draft will expire on October 22, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 12 skipping to change at page 3, line 12
external to the measurement protocols themselves, for example via a external to the measurement protocols themselves, for example via a
Network Management System (NMS) or separate configuration protocol. Network Management System (NMS) or separate configuration protocol.
This document is a product of a joint Internet Engineering Task Force This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication (IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge
(PWE3) architectures to support the capabilities and functionalities (PWE3) architectures to support the capabilities and functionalities
of a packet transport network as defined by the ITU-T. of a packet transport network as defined by the ITU-T.
2. Packet Loss Measurement (LM) Profile 2. MPLS-TP Measurement Considerations
Several of the considerations discussed in [I-D.ietf-mpls-loss-delay]
can be disregarded in the more restrictive context of MPLS-TP:
o Equal Cost Multipath considerations (Section 2.7.3 of
[I-D.ietf-mpls-loss-delay])
o Considerations for direct LM in the presence of Label Switched
Paths constructed via the Label Distribution Protocol (LDP) or
utilizing Penultimate Hop Popping (Section 2.7.6 of
[I-D.ietf-mpls-loss-delay])
3. Packet Loss Measurement (LM) Profile
When an LM session is externally configured, the values of several When an LM session is externally configured, the values of several
protocol parameters can be fixed in advance at the endpoints involved protocol parameters can be fixed in advance at the endpoints involved
in the session, so that inspection or negotiation of these parameters in the session, so that negotiation of these parameters is not
is not required. These parameters, and their default values as required. These parameters, and their default values as specified by
specified by this profile, are as follows: this profile, are as follows:
Parameter Default Value Parameter Default Value
----------------------------------------- -------------------------- ----------------------------------------- --------------------------
Query control code In-band response requested Query control code In-band response requested
Byte/packet Count (B) Flag Packet count Byte/packet Count (B) Flag Packet count
Traffic-Class-specific (T) Flag Traffic-class-scoped Traffic-Class-specific (T) Flag Traffic-class-scoped
Origin Timestamp Format (OTF) IEEE 1588 version 1 Origin Timestamp Format (OTF) IEEE 1588 version 1
This profile is restricted to direct-mode LM and therefore uses the
MPLS Direct Packet Loss Measurement (DLM) Channel Type in the
Associated Channel Header (ACH).
A simple implementation may assume that external configuration will A simple implementation may assume that external configuration will
ensure that both ends of the communication are using the default ensure that both ends of the communication are using the default
values for these parameters. values for these parameters. Implementations are, however, strongly
advised to validate the values of these parameters in received
messages so that configuration inconsistencies can be detected and
reported.
3. Packet Delay Measurement (DM) Profile 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
4. Packet Delay Measurement (DM) Profile
When a DM session is externally configured, the values of several When a DM session is externally configured, the values of several
protocol parameters can be fixed in advance at the endpoints involved protocol parameters can be fixed in advance at the endpoints involved
in the session, so that inspection or negotiation of these parameters in the session, so that negotiation of these parameters is not
is not required. These parameters, and their default values as required. These parameters, and their default values as specified by
specified by this profile, are as follows: this profile, are as follows:
Parameter Default Value Parameter Default Value
------------------------------------------ -------------------------- ------------------------------------------ --------------------------
Query control code In-band response requested Query control code In-band response requested
Querier Timestamp Format (QTF) IEEE 1588 version 1 Querier Timestamp Format (QTF) IEEE 1588 version 1
Responder Timestamp Format (RTF) IEEE 1588 version 1 Responder Timestamp Format (RTF) IEEE 1588 version 1
Responder's Preferred Timestamp Format IEEE 1588 version 1 Responder's Preferred Timestamp Format IEEE 1588 version 1
(RPTF) (RPTF)
This profile uses the MPLS Delay Measurement (DM) Channel Type in the This profile uses the MPLS Delay Measurement (DM) Channel Type in the
Associated Channel Header (ACH). Associated Channel Header (ACH).
A simple implementation may assume that external configuration will A simple implementation may assume that external configuration will
ensure that both ends of the communication are using the default ensure that both ends of the communication are using the default
values for these parameters. values for these parameters. Implementations are, however, strongly
advised to validate the values of these parameters in received
messages so that configuration inconsistencies can be detected and
reported.
4. Security Considerations 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.
5. Security Considerations
This document delineates a subset of the procedures specified in This document delineates a subset of the procedures specified in
[I-D.ietf-mpls-loss-delay], and as such introduces no new security [I-D.ietf-mpls-loss-delay], and as such introduces no new security
considerations in itself. The security considerations discussed in considerations in itself. The security considerations discussed in
[I-D.ietf-mpls-loss-delay] apply also to the profile presented in [I-D.ietf-mpls-loss-delay] apply also to the profile presented in
this document. this document.
5. IANA Considerations 6. IANA Considerations
This document introduces no new IANA considerations. This document introduces no new IANA considerations.
6. References 7. References
6.1. Normative References 7.1. Normative References
[I-D.ietf-mpls-loss-delay] [I-D.ietf-mpls-loss-delay]
Frost, D. and S. Bryant, "Packet Loss and Delay Frost, D. and S. Bryant, "Packet Loss and Delay
Measurement for MPLS Networks", Measurement for MPLS Networks",
draft-ietf-mpls-loss-delay-00 (work in progress), draft-ietf-mpls-loss-delay-01 (work in progress),
December 2010. February 2011.
[RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic [RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic
Associated Channel", RFC 5586, June 2009. Associated Channel", RFC 5586, June 2009.
[RFC5860] Vigoureux, M., Ward, D., and M. Betts, "Requirements for [RFC5860] Vigoureux, M., Ward, D., and M. Betts, "Requirements for
Operations, Administration, and Maintenance (OAM) in MPLS Operations, Administration, and Maintenance (OAM) in MPLS
Transport Networks", RFC 5860, May 2010. Transport Networks", RFC 5860, May 2010.
6.2. Informative References 7.2. Informative References
[RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. [RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L.
Berger, "A Framework for MPLS in Transport Networks", Berger, "A Framework for MPLS in Transport Networks",
RFC 5921, July 2010. RFC 5921, July 2010.
Authors' Addresses Authors' Addresses
Dan Frost (editor) Dan Frost (editor)
Cisco Systems Cisco Systems
 End of changes. 17 change blocks. 
24 lines changed or deleted 55 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/