draft-ietf-mpls-tp-loss-delay-profile-00.txt   draft-ietf-mpls-tp-loss-delay-profile-01.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: June 26, 2011 December 23, 2010 Expires: June 27, 2011 December 24, 2010
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-00 draft-ietf-mpls-tp-loss-delay-profile-01
Abstract Abstract
Procedures for the measurement of packet loss, delay, and throughput Procedures and protocol mechanisms to enable the efficient and
in MPLS networks are defined in RFC XXXX. This document describes a accurate measurement of packet loss, delay, and throughput in MPLS
profile, i.e. a simplified subset, of these procedures that suffices networks are defined in RFC XXXX.
to meet the specific requirements of MPLS-based transport networks.
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 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.
This Informational Internet-Draft is aimed at achieving IETF
Consensus before publication as an RFC and will be subject to an IETF
Last Call.
[RFC Editor, please remove this note before publication as an RFC and [RFC Editor, please remove this note before publication as an RFC and
insert the correct Streams Boilerplate to indicate that the published insert the correct Streams Boilerplate to indicate that the published
RFC has IETF consensus.] RFC has IETF consensus.]
[RFC Editor, please replace XXXX with the RFC number assigned to
draft-ietf-mpls-loss-delay.]
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 June 26, 2011. This Internet-Draft will expire on June 27, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
1. Introduction 1. Introduction
Procedures for the measurement of packet loss, delay, and throughput Procedures for the measurement of packet loss, delay, and throughput
in MPLS networks are defined in [I-D.frost-mpls-loss-delay]. This in MPLS networks are defined in [I-D.ietf-mpls-loss-delay]. This
document describes a profile, i.e. a simplified subset, of these document describes a profile, i.e. a simplified subset, of these
procedures that suffices to meet the specific requirements of MPLS- procedures that suffices to meet the specific requirements of MPLS-
based transport networks [RFC5921] as defined in [RFC5860]. This based transport networks [RFC5921] as defined in [RFC5860]. This
profile is presented for the convenience of implementors who are profile is presented for the convenience of implementors who are
concerned exclusively with the transport network context. concerned exclusively with the transport network context.
The use of the profile specified in this document is purely optional. The use of the profile specified in this document is purely optional.
Implementors wishing to provide enhanced functionality that is within Implementors wishing to provide enhanced functionality that is within
the scope of [I-D.frost-mpls-loss-delay] but outside the scope of the scope of [I-D.ietf-mpls-loss-delay] but outside the scope of this
this profile may do so, whether or not the implementation is profile may do so, whether or not the implementation is restricted to
restricted to the transport network context. the transport network context.
The assumption of this profile is that the devices involved in a The assumption of this profile is that the devices involved in a
measurement operation are configured for measurement by a means measurement operation are configured for measurement by a means
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
skipping to change at page 4, line 21 skipping to change at page 4, line 34
as follows: as follows:
o Query control code: In-band response requested o Query control code: In-band response requested
o QTF: IEEE 1588 version 1 o QTF: IEEE 1588 version 1
o RTF: IEEE 1588 version 1 o RTF: IEEE 1588 version 1
o RPTF: IEEE 1588 version 1 o RPTF: IEEE 1588 version 1
o T flag: traffic-class-scoped
The TC field is set according to the class of traffic to be measured. The TC field is set according to the class of traffic to be measured.
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 externally-determined A simple implementation may assume externally-determined
configuration and need only support the functionality required by configuration and need only support the functionality required by
these defaults. these defaults.
4. Security Considerations 4. Security Considerations
This document delineates a subset of the procedures specified in This document delineates a subset of the procedures specified in
[I-D.frost-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.frost-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 5. IANA Considerations
This document introduces no new IANA considerations. This document introduces no new IANA considerations.
6. References 6. References
6.1. Normative References 6.1. Normative References
[I-D.frost-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-frost-mpls-loss-delay-00 (work in progress), draft-ietf-mpls-loss-delay-00 (work in progress),
December 2010. December 2010.
[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 6.2. Informative References
 End of changes. 14 change blocks. 
17 lines changed or deleted 30 lines changed or added

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