idnits 2.17.1 draft-frost-mpls-tp-loss-delay-profile-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 15, 2010) is 4882 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC5586' is defined on line 190, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MPLS D. Frost, Ed. 3 Internet-Draft S. Bryant, Ed. 4 Intended status: Informational Cisco Systems 5 Expires: June 18, 2011 December 15, 2010 7 A Packet Loss and Delay Measurement Profile for MPLS-based Transport 8 Networks 9 draft-frost-mpls-tp-loss-delay-profile-00 11 Abstract 13 Procedures for the measurement of packet loss, delay, and throughput 14 in MPLS networks are defined in RFC XXXX. This document describes a 15 profile, i.e. a simplified subset, of these procedures that suffices 16 to meet the specific requirements of MPLS-based transport networks. 18 This document is a product of a joint Internet Engineering Task Force 19 (IETF) / International Telecommunication Union Telecommunication 20 Standardization Sector (ITU-T) effort to include an MPLS Transport 21 Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge 22 (PWE3) architectures to support the capabilities and functionalities 23 of a packet transport network as defined by the ITU-T. 25 [RFC Editor, please remove this note before publication as an RFC and 26 insert the correct Streams Boilerplate to indicate that the published 27 RFC has IETF consensus.] 29 Status of this Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at http://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on June 18, 2011. 46 Copyright Notice 48 Copyright (c) 2010 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 1. Introduction 63 Procedures for the measurement of packet loss, delay, and throughput 64 in MPLS networks are defined in [I-D.frost-mpls-loss-delay]. This 65 document describes a profile, i.e. a simplified subset, of these 66 procedures that suffices to meet the specific requirements of MPLS- 67 based transport networks [RFC5921] as defined in [RFC5860]. This 68 profile is presented for the convenience of implementors who are 69 concerned exclusively with the transport network context. 71 The use of the profile specified in this document is purely optional. 72 Implementors wishing to provide enhanced functionality that is within 73 the scope of [I-D.frost-mpls-loss-delay] but outside the scope of 74 this profile may do so, whether or not the implementation is 75 restricted to the transport network context. 77 The assumption of this profile is that the devices involved in a 78 measurement operation are configured for measurement by a means 79 external to the measurement protocols themselves, for example via a 80 Network Management System (NMS) or separate configuration protocol. 82 This document is a product of a joint Internet Engineering Task Force 83 (IETF) / International Telecommunication Union Telecommunication 84 Standardization Sector (ITU-T) effort to include an MPLS Transport 85 Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge 86 (PWE3) architectures to support the capabilities and functionalities 87 of a packet transport network as defined by the ITU-T. 89 2. Packet Loss Measurement (LM) Profile 91 When an LM session is externally configured, the values of several 92 protocol parameters can be fixed in advance at the endpoints involved 93 in the session, so that inspection or negotiation of these parameters 94 is not required: 96 o The Query control code 98 o The byte/packet count (B) flag 100 o The extended data format (X) flag 102 o The Traffic-Class-specific (T) flag 104 o The Traffic Class (TC) 106 o The Origin Timestamp Format (OTF) 108 The default values for these parameters are specified by this profile 109 as follows: 111 o Query control code: In-band response requested 113 o B flag: packet count 115 o X flag: 32-bit 117 o T flag: traffic-class-scoped 119 o OTF: IEEE 1588 version 1 121 The TC field is set according to the class of traffic to be measured. 123 This profile is restricted to direct-mode LM and therefore uses the 124 MPLS Direct Packet Loss Measurement (DLM) Channel Type in the 125 Associated Channel Header (ACH). 127 A simple implementation may assume externally-determined 128 configuration and need only support the functionality required by 129 these defaults. 131 3. Packet Delay Measurement (DM) Profile 133 When a DM session is externally configured, the values of several 134 protocol parameters can be fixed in advance at the endpoints involved 135 in the session, so that inspection or negotiation of these parameters 136 is not required: 138 o The Query control code 140 o The Querier Timestamp Format (QTF) field 141 o The Responder Timestamp Format (RTF) field 143 o The Responder's Preferred Timestamp Format (RPTF) field 145 o The Traffic Class (TC) 147 The default values for these parameters are specified by this profile 148 as follows: 150 o Query control code: In-band response requested 152 o QTF: IEEE 1588 version 1 154 o RTF: IEEE 1588 version 1 156 o RPTF: IEEE 1588 version 1 158 o T flag: traffic-class-scoped 160 The TC field is set according to the class of traffic to be measured. 162 This profile uses the MPLS Delay Measurement (DM) Channel Type in the 163 Associated Channel Header (ACH). 165 A simple implementation may assume externally-determined 166 configuration and need only support the functionality required by 167 these defaults. 169 4. Security Considerations 171 This document delineates a subset of the procedures specified in 172 [I-D.frost-mpls-loss-delay], and as such introduces no new security 173 considerations in itself. The security considerations discussed in 174 [I-D.frost-mpls-loss-delay] apply also to the profile presented in 175 this document. 177 5. IANA Considerations 179 This document introduces no new IANA considerations. 181 6. References 182 6.1. Normative References 184 [I-D.frost-mpls-loss-delay] 185 Frost, D. and S. Bryant, "Packet Loss and Delay 186 Measurement for MPLS Networks", 187 draft-frost-mpls-loss-delay-00 (work in progress), 188 December 2010. 190 [RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic 191 Associated Channel", RFC 5586, June 2009. 193 [RFC5860] Vigoureux, M., Ward, D., and M. Betts, "Requirements for 194 Operations, Administration, and Maintenance (OAM) in MPLS 195 Transport Networks", RFC 5860, May 2010. 197 6.2. Informative References 199 [RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. 200 Berger, "A Framework for MPLS in Transport Networks", 201 RFC 5921, July 2010. 203 Authors' Addresses 205 Dan Frost (editor) 206 Cisco Systems 208 Email: danfrost@cisco.com 210 Stewart Bryant (editor) 211 Cisco Systems 213 Email: stbryant@cisco.com