draft-ietf-mpls-tp-loss-delay-profile-01.txt   draft-ietf-mpls-tp-loss-delay-profile-02.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 27, 2011 December 24, 2010 Expires: August 8, 2011 February 4, 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-01 draft-ietf-mpls-tp-loss-delay-profile-02
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 June 27, 2011. This Internet-Draft will expire on August 8, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 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
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
skipping to change at page 3, line 17 skipping to change at page 3, line 17
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. 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 inspection or negotiation of these parameters
is not required: is not required. These parameters, and their default values as
specified by this profile, are as follows:
o The Query control code
o The byte/packet count (B) flag
o The extended data format (X) flag
o The Traffic-Class-specific (T) flag
o The Traffic Class (TC)
o The Origin Timestamp Format (OTF)
The default values for these parameters are specified by this profile
as follows:
o Query control code: In-band response requested
o B flag: packet count
o X flag: 32-bit
o T flag: traffic-class-scoped
o OTF: IEEE 1588 version 1
The TC field is set according to the class of traffic to be measured. 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) IEEE 1588 version 1
This profile is restricted to direct-mode LM and therefore uses the This profile is restricted to direct-mode LM and therefore uses the
MPLS Direct Packet Loss Measurement (DLM) Channel Type in the MPLS Direct Packet Loss Measurement (DLM) Channel Type in the
Associated Channel Header (ACH). Associated Channel Header (ACH).
A simple implementation may assume externally-determined A simple implementation may assume that external configuration will
configuration and need only support the functionality required by ensure that both ends of the communication are using the default
these defaults. values for these parameters.
3. Packet Delay Measurement (DM) Profile 3. 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 inspection or negotiation of these parameters
is not required: is not required. These parameters, and their default values as
specified by this profile, are as follows:
o The Query control code
o The Querier Timestamp Format (QTF) field
o The Responder Timestamp Format (RTF) field
o The Responder's Preferred Timestamp Format (RPTF) field
o The Traffic Class (TC)
The default values for these parameters are specified by this profile
as follows:
o Query control code: In-band response requested
o QTF: IEEE 1588 version 1
o RTF: IEEE 1588 version 1
o RPTF: IEEE 1588 version 1
The TC field is set according to the class of traffic to be measured.
Parameter Default Value
------------------------------------------ --------------------------
Query control code In-band response requested
Querier Timestamp Format (QTF) IEEE 1588 version 1
Responder Timestamp Format (RTF) IEEE 1588 version 1
Responder's Preferred Timestamp Format IEEE 1588 version 1
(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 externally-determined A simple implementation may assume that external configuration will
configuration and need only support the functionality required by ensure that both ends of the communication are using the default
these defaults. values for these parameters.
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.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 5. IANA Considerations
 End of changes. 10 change blocks. 
61 lines changed or deleted 27 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/