idnits 2.17.1 draft-ietf-mpls-tp-loss-delay-profile-04.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 (July 19, 2011) is 4627 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC5586' is defined on line 208, but no explicit reference was found in the text == Outdated reference: A later version (-04) exists of draft-ietf-mpls-loss-delay-03 == Outdated reference: A later version (-09) exists of draft-ietf-mpls-tp-security-framework-01 Summary: 0 errors (**), 0 flaws (~~), 4 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: January 20, 2012 July 19, 2011 7 A Packet Loss and Delay Measurement Profile for MPLS-based Transport 8 Networks 9 draft-ietf-mpls-tp-loss-delay-profile-04 11 Abstract 13 Procedures and protocol mechanisms to enable efficient and accurate 14 measurement of packet loss, delay, and throughput in MPLS networks 15 are defined in RFC XXXX. 17 The MPLS Transport Profile (MPLS-TP) is the set of MPLS protocol 18 functions applicable to the construction and operation of packet- 19 switched transport networks. 21 This document describes a profile of the general MPLS loss, delay, 22 and throughput measurement techniques that suffices to meet the 23 specific requirements of MPLS-TP. 25 This document is a product of a joint Internet Engineering Task Force 26 (IETF) / International Telecommunication Union Telecommunication 27 Standardization Sector (ITU-T) effort to include an MPLS Transport 28 Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge 29 (PWE3) architectures to support the capabilities and functionalities 30 of a packet transport network as defined by the ITU-T. 32 This Informational Internet-Draft is aimed at achieving IETF 33 Consensus before publication as an RFC and will be subject to an IETF 34 Last Call. 36 [RFC Editor, please remove this note before publication as an RFC and 37 insert the correct Streams Boilerplate to indicate that the published 38 RFC has IETF consensus.] 40 [RFC Editor, please replace XXXX with the RFC number assigned to 41 draft-ietf-mpls-loss-delay.] 43 Status of this Memo 45 This Internet-Draft is submitted in full conformance with the 46 provisions of BCP 78 and BCP 79. 48 Internet-Drafts are working documents of the Internet Engineering 49 Task Force (IETF). Note that other groups may also distribute 50 working documents as Internet-Drafts. The list of current Internet- 51 Drafts is at http://datatracker.ietf.org/drafts/current/. 53 Internet-Drafts are draft documents valid for a maximum of six months 54 and may be updated, replaced, or obsoleted by other documents at any 55 time. It is inappropriate to use Internet-Drafts as reference 56 material or to cite them other than as "work in progress." 58 This Internet-Draft will expire on January 20, 2012. 60 Copyright Notice 62 Copyright (c) 2011 IETF Trust and the persons identified as the 63 document authors. All rights reserved. 65 This document is subject to BCP 78 and the IETF Trust's Legal 66 Provisions Relating to IETF Documents 67 (http://trustee.ietf.org/license-info) in effect on the date of 68 publication of this document. Please review these documents 69 carefully, as they describe your rights and restrictions with respect 70 to this document. Code Components extracted from this document must 71 include Simplified BSD License text as described in Section 4.e of 72 the Trust Legal Provisions and are provided without warranty as 73 described in the Simplified BSD License. 75 1. Introduction 77 Procedures for the measurement of packet loss, delay, and throughput 78 in MPLS networks are defined in [I-D.ietf-mpls-loss-delay]. This 79 document describes a profile, i.e. a simplified subset, of these 80 procedures that suffices to meet the specific requirements of MPLS- 81 based transport networks [RFC5921] as defined in [RFC5860]. This 82 profile is presented for the convenience of implementors who are 83 concerned exclusively with the transport network context. 85 The use of the profile specified in this document is purely optional. 86 Implementors wishing to provide enhanced functionality that is within 87 the scope of [I-D.ietf-mpls-loss-delay] but outside the scope of this 88 profile may do so, whether or not the implementation is restricted to 89 the transport network context. 91 The assumption of this profile is that the devices involved in a 92 measurement operation are configured for measurement by a means 93 external to the measurement protocols themselves, for example via a 94 Network Management System (NMS) or separate configuration protocol. 95 The manageability considerations in [I-D.ietf-mpls-loss-delay] apply, 96 and further information on MPLS-TP network management can be found in 97 [RFC5950]. 99 This document is a product of a joint Internet Engineering Task Force 100 (IETF) / International Telecommunication Union Telecommunication 101 Standardization Sector (ITU-T) effort to include an MPLS Transport 102 Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge 103 (PWE3) architectures to support the capabilities and functionalities 104 of a packet transport network as defined by the ITU-T. 106 2. MPLS-TP Measurement Considerations 108 The measurement considerations discussed in Section 2.9 of 109 [I-D.ietf-mpls-loss-delay] apply also in the context of MPLS-TP, 110 except for the following, which pertain to topologies excluded from 111 MPLS-TP: 113 o Equal Cost Multipath considerations (Section 2.9.4 of 114 [I-D.ietf-mpls-loss-delay]) 116 o Considerations for direct Loss Measurement (LM) in the presence of 117 Label Switched Paths constructed via the Label Distribution 118 Protocol (LDP) or utilizing Penultimate Hop Popping (Section 2.9.8 119 of [I-D.ietf-mpls-loss-delay]) 121 3. Packet Loss Measurement (LM) Profile 123 When an LM session is externally configured, the values of several 124 protocol parameters can be fixed in advance at the endpoints involved 125 in the session, so that negotiation of these parameters is not 126 required. These parameters, and their default values as specified by 127 this profile, are as follows: 129 Parameter Default Value 130 ----------------------------------------- -------------------------- 131 Query control code In-band response requested 132 Byte/packet Count (B) Flag Packet count 133 Traffic-Class-specific (T) Flag Traffic-class-scoped 134 Origin Timestamp Format (OTF) Truncated IEEE 1588v2 136 A simple implementation may assume that external configuration will 137 ensure that both ends of the communication are using the default 138 values for these parameters. Implementations are, however, strongly 139 advised to validate the values of these parameters in received 140 messages so that configuration inconsistencies can be detected and 141 reported. 143 LM message rates (and test message rates, when inferred LM is used) 144 should be configurable by the network operator on a per-channel 145 basis. The following intervals should be supported: 147 Message Type Supported Intervals 148 -------------- ------------------------------------------------------ 149 LM Message 100 milliseconds, 1 second, 10 seconds, 1 minute, 10 150 minutes 151 Test Message 10 milliseconds, 100 milliseconds, 1 second, 10 152 seconds, 1 minute 154 4. Packet Delay Measurement (DM) Profile 156 When a DM session is externally configured, the values of several 157 protocol parameters can be fixed in advance at the endpoints involved 158 in the session, so that negotiation of these parameters is not 159 required. These parameters, and their default values as specified by 160 this profile, are as follows: 162 Parameter Default Value 163 ------------------------------------------ -------------------------- 164 Query control code In-band response requested 165 Querier Timestamp Format (QTF) Truncated IEEE 1588v2 166 Responder Timestamp Format (RTF) Truncated IEEE 1588v2 167 Responder's Preferred Timestamp Format Truncated IEEE 1588v2 168 (RPTF) 170 This profile uses the MPLS Delay Measurement (DM) Channel Type in the 171 Associated Channel Header (ACH). 173 A simple implementation may assume that external configuration will 174 ensure that both ends of the communication are using the default 175 values for these parameters. Implementations are, however, strongly 176 advised to validate the values of these parameters in received 177 messages so that configuration inconsistencies can be detected and 178 reported. 180 DM message rates should be configurable by the network operator on a 181 per-channel basis. The following message intervals should be 182 supported: 1 second, 10 seconds, 1 minute, 10 minutes. 184 5. Security Considerations 186 This document delineates a subset of the procedures specified in 187 [I-D.ietf-mpls-loss-delay], and as such introduces no new security 188 considerations in itself. The security considerations discussed in 190 [I-D.ietf-mpls-loss-delay] apply also to the profile presented in 191 this document. General considerations for MPLS-TP network security 192 can be found in [I-D.ietf-mpls-tp-security-framework]. 194 6. IANA Considerations 196 This document introduces no new IANA considerations. 198 7. References 200 7.1. Normative References 202 [I-D.ietf-mpls-loss-delay] 203 Frost, D. and S. Bryant, "Packet Loss and Delay 204 Measurement for MPLS Networks", 205 draft-ietf-mpls-loss-delay-03 (work in progress), 206 June 2011. 208 [RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic 209 Associated Channel", RFC 5586, June 2009. 211 [RFC5860] Vigoureux, M., Ward, D., and M. Betts, "Requirements for 212 Operations, Administration, and Maintenance (OAM) in MPLS 213 Transport Networks", RFC 5860, May 2010. 215 7.2. Informative References 217 [I-D.ietf-mpls-tp-security-framework] 218 Fang, L., Niven-Jenkins, B., and S. Mansfield, "MPLS-TP 219 Security Framework", 220 draft-ietf-mpls-tp-security-framework-01 (work in 221 progress), May 2011. 223 [RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. 224 Berger, "A Framework for MPLS in Transport Networks", 225 RFC 5921, July 2010. 227 [RFC5950] Mansfield, S., Gray, E., and K. Lam, "Network Management 228 Framework for MPLS-based Transport Networks", RFC 5950, 229 September 2010. 231 Authors' Addresses 233 Dan Frost (editor) 234 Cisco Systems 236 Email: danfrost@cisco.com 238 Stewart Bryant (editor) 239 Cisco Systems 241 Email: stbryant@cisco.com