idnits 2.17.1 draft-chen-ippm-ipfpm-report-01.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 (April 19, 2016) is 2927 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Chen, Ed. 3 Internet-Draft L. Zheng, Ed. 4 Intended status: Standards Track Huawei Technologies 5 Expires: October 21, 2016 G. Mirsky, Ed. 6 Ericsson 7 April 19, 2016 9 IP Flow Performance Measurement Report 10 draft-chen-ippm-ipfpm-report-01 12 Abstract 14 A "marking" based IP Flow Performance Measurement (IPFPM) framework 15 is specified in draft-chen-ippm-coloring-based-ipfpm-framework. IP 16 Flow Information eXport (IPFIX) is used for exporting the performance 17 of IPFPM. Several new Information Elements of IPFIX are defined for 18 IPFPM in this document. 20 Requirements Language 22 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 23 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 24 document are to be interpreted as described in RFC 2119 [RFC2119]. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on October 21, 2016. 43 Copyright Notice 45 Copyright (c) 2016 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 2. Measurement Data Report . . . . . . . . . . . . . . . . . . . 3 62 3. IPFIX Information Element for IPFPM . . . . . . . . . . . . . 4 63 3.1. maIdentifier . . . . . . . . . . . . . . . . . . . . . . 4 64 3.2. periodNumber . . . . . . . . . . . . . . . . . . . . . . 4 65 3.3. maStatus . . . . . . . . . . . . . . . . . . . . . . . . 5 66 4. Templates for IPFPM . . . . . . . . . . . . . . . . . . . . . 5 67 4.1. MA Status Options Template . . . . . . . . . . . . . . . 5 68 4.2. Flow Options Template . . . . . . . . . . . . . . . . . . 6 69 4.3. Packet Loss Template . . . . . . . . . . . . . . . . . . 9 70 4.4. Packet Delay Template . . . . . . . . . . . . . . . . . . 10 71 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 72 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 73 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 74 8. Contributing Authors . . . . . . . . . . . . . . . . . . . . 11 75 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 76 9.1. Normative References . . . . . . . . . . . . . . . . . . 12 77 9.2. Informative References . . . . . . . . . . . . . . . . . 13 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 80 1. Introduction 82 A "marking" based IP Flow Performance Measurement (IPFPM) framework 83 is specified in [I-D.chen-ippm-coloring-based-ipfpm-framework]. This 84 document is the companion document of 85 [I-D.chen-ippm-coloring-based-ipfpm-framework]. The IPFPM framework 86 describes a mechanism where data packets are marked so that they form 87 blocks of data. No additional delimiting OAM is needed and the 88 performance metrics can be measured in-service without the insertion 89 of additional traffic. Furthermore, because marking based IP 90 performance measurement does not require extra OAM packets for 91 traffic delimitation, it can be used in situations where there is 92 packets re-ordering. IP Flow Information eXport (IPFIX) [RFC7011] is 93 used for exporting the performance of IPFPM. Several new Information 94 Elements of IPFIX are defined for IPFPM in this document. 96 2. Measurement Data Report 98 In the IPFPM reference model, the Measurement Agent (MA) executes the 99 measurement actions (e.g., marks the packets, counts the packets, 100 records the timestamps, etc.), and reports the data to the 101 Measurement Control Point (MCP). The MCP is a centralized 102 calculation element, responsible for collecting measurement data from 103 MA and calculating the performance metrics according to the received 104 measurement data from the MAs. During the performance measurement 105 period, each MA reports performance measurementmeasurement data to 106 the MCP, and the MCP will compute the performance measurement results 107 according to the received measurement data. For a specific IP flow, 108 for either packet delay or loss measurement, there will be at least 109 one upstream and one downstream MA. For accurate measurements, time 110 synchronization is required and the Period Number 111 [I-D.chen-ippm-coloring-based-ipfpm-framework] is used by MCP to 112 uniquely identify and correlate the packet counts/ timestamps between 113 the upstream and downstream MAs for a specific block of markers or 114 marked packet. 116 For packet loss measurement, the following information is required to 117 report to the MCP: 119 MA Identifier 121 Flow Identifier (identify the flow to be measured) 123 Period Number 125 Packet Number Count 127 Packet Octets Count 129 For packet delay measurement, the following information is required 130 to report to the MCP: 132 MA Identifier 134 Flow Identifier 136 Period Number 138 Timestamp 140 In addition, a MA may report some status (e.g., whether a MA is time 141 synchronized) to the MCP, hence to help the MCP to determine whether 142 measurement data from a MA is valid and can be used for computation. 143 The following information may be included: 145 MA Identifier 147 MA Status 149 3. IPFIX Information Element for IPFPM 151 The IPFIX protocol [RFC7011] defines how IP Flow information can be 152 exported from routers, measurement probes, or other devices. It 153 defines many Information Elements [RFC7012] that can be used to carry 154 and export the above information from MAs to MCP. Section 2 lists 155 the statistic Information and status information need to be reported 156 for IPFPM. Most of them can be identified with the existing 157 Information Elements. New Information Element is defined for MA 158 Identifer, Period Number and MA Status respectively in the following 159 sections. 161 Flow Identifier: flowId (148) 163 Packet Number Count: packetTotalCount (86) 165 Packet Octets Count: octetTotalCount (85) 167 Timestamp: flowStartMicroseconds (154) 169 3.1. maIdentifier 171 Description: The maIdentifier is used to identify a MA. An 172 maIdentifiler is unique within a specific administrative domain (e.g. 173 within one MCP). The MA identifier can be generated and maintained 174 by MCP. How to generate and maintain the maIdentifier is out the 175 scope of this document. 177 Abstract Data Type: unsigned32 179 ElementId: TBD1 181 Status: current 183 3.2. periodNumber 185 Description: The periodNumber (PN) is used to identify a packet count 186 or timestamp that belongs to a specific block of markers or marked 187 packet. The MCP uses it to determine whether any two or more packet 188 counts (from distributed MAs) are related to the same block of 189 markers or any two timestamps are related to the same marked packet. 190 The PN is generated each time a MA reads the packet counts and 191 timestamp, and is equal to the modulo of the local time (when the 192 counts and timestamps are read) and the interval of the marking time 193 period [I-D.chen-ippm-coloring-based-ipfpm-framework]. 195 Abstract Data Type: unsigned32 197 ElementId: TBD2 199 Status: current 201 3.3. maStatus 203 Description: The maStatus is used to carry status information of a MA 204 (For example, whether a MA has already time synchronized, whether is 205 a upstream or downstream MA for a specific measured flow). 207 Abstract Data Type: unsigned16 209 ElementId: TBD3 211 Status: current 213 The maStaus is defined as follows: 215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 216 | Reserved |U|T| 217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 219 Two bits are defined in this document. The T bit (Time synchronized 220 bit) it is used to indicate whether a MA is time synchronized. When 221 the T bit set, the MA is time synchronized; when the T bit is 222 cleared, the MA is not time synchronized. The MCP MUST calculate the 223 results when all related MAs of a flow are time synchronized, 224 otherwise, the results will not correct. The U bit ( Upstream MA 225 bit) is used to indicate whether a MA is the upstream or downstream 226 TLP for an IP flow. When the U bit set, the MA is the upstream MA of 227 the flow; otherwise, the MA is the downstream MA of the flow. 229 4. Templates for IPFPM 231 4.1. MA Status Options Template 233 The MA Status Options Template is used to report the status of a MA; 234 it SHOULD contain the following Information Elements: 236 meteringProcessId (scope) [IPFIX-IANA] 238 MA Identifier 239 The maIdentifier is as defined in Section 3.1 of this document. 241 MA Status 243 The maStatus is as defined in Section 3.3 of this document. 245 The Data Records specified by the MA Status Options Template SHOULD 246 be exported once the IPFIX session established or when status 247 changed. 249 An example of the MA Status Options Template Set is as follows: 251 0 1 2 3 252 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 253 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 254 | Set ID = 3 | Length = 24 | 255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 256 | Template ID XXX | Field Count = 3 | 257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 258 | Scope Field Count = 1 |0| meteringProcessId = 143 | 259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 260 | Scope 1 Field Length = 4 |0| maIdentifier = TBD1 | 261 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 262 | Scope 1 Field Length = 4 |0| ma Status = TBD3 | 263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 264 | Field Length = 1 | Padding | 265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 267 4.2. Flow Options Template 269 The Flow Options Template is used to report all the configured flows 270 (to be measured) on a MA. It SHOULD include the following the 271 Information Elements: 273 meteringProcessId (scope) [IPFIX-IANA] 275 MA Identifier 277 The maIdentifier is as defined in Section 3.1 of this document. 279 maStatus [Section 3.3] 281 flowId [IPFIX-IANA] 283 protocolIdentifier [IPFIX-IANA] 285 Source IP address 286 The source IP address or prefix of an IP flow, for this address, 287 any of the following Information Elements can be used: 289 sourceIPv4Address [IPFIX-IANA] 291 sourceIPv6Address [IPFIX-IANA] 293 sourceIPv4Prefix [IPFIX-IANA] 295 sourceIPv6Prefix [IPFIX-IANA] 297 Source IP prefix length 299 The source IP prefix length of a prefix, any of the following 300 Information Elements can be used: 302 sourceIPv4PrefixLength [IPFIX-IANA] 304 sourceIPv6PrefixLength [IPFIX-IANA] 306 Source port 308 The source port of an IP flow, any of the following Information 309 Elements can be used: 311 udpSourcePort [IPFIX-IANA] 313 tcpSourcePort [IPFIX-IANA] 315 Destination IP address 317 The destination IP address or prefix of an IP flow, for this 318 address, any of the following Information Elements can be used: 320 destinationIPv4Address [IPFIX-IANA] 322 destinationIPv6Address [IPFIX-IANA] 324 destinationIPv4Prefix [IPFIX-IANA] 326 destinationIPv6Prefix [IPFIX-IANA] 328 Destination IP prefix length 330 The destination IP prefix length of a prefix, any of the following 331 Information Elements can be used: 333 destinationIPv4PrefixLength [IPFIX-IANA] 334 destinationIPv6PrefixLength [IPFIX-IANA] 336 Destination port 338 The destination port of an IP flow, any of the following 339 Information Elements can be used: 341 udpDestinationPort [IPFIX-IANA] 343 tcpDestinationPort [IPFIX-IANA] 345 The Data Records specified by the Flow Options Template SHOULD be 346 exported once the IPFIX session established or when the configured 347 flows changed (e.g., a new flow is added for measurement or a flow 348 deleted to stop the measurement). 350 An example of the Flow Options Template Set is as follows: 352 0 1 2 3 353 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 | Set ID = 3 | Length = 52 | 356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 | Template ID XXX | Field Count = 10 | 358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 359 | Scope Field Count = 1 |0| meteringProcessId=143 | 360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 | Scope 1 Field Length = 4 |0| maIdentifier = TBD1 | 362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 363 | Field Length = 4 |0| maStatus = TBD3 | 364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 365 | Field Length = 1 |0| flowID = 148 | 366 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 367 | Field Length = 4 |0| protocolIdentifier = 4 | 368 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 369 | Field Length = 1 |0| sourceIPv4Address = 8 | 370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 371 | Field Length = 4 |0| udpSourcePort = 4 | 372 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 373 | Field Length = 2 |0| destinationIPv4Address = 4 | 374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 375 | Field Length = 4 |0| udpDestinationPort = 4 | 376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 377 | Field Length = 4 |0| udpDestinationPort = 4 | 378 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 379 | Field Length = 2 | Padding | 380 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 382 4.3. Packet Loss Template 384 The Packet Loss Template is used by a MA to report the packet loss 385 measurement statistic of a flow to the MCP; it SHOULD contain the 386 following Information Elements: 388 MA Identifier 390 The maIdentifier is as defined in Section 3.1 of this document. 392 flowId[IPFIX-IANA] 394 periodNumber [Section 3.2] 396 packetTotalCount[IPFIX-IANA] 398 octetTotalCount[IPFIX-IANA] 400 An example of the Packet Loss Data Set is as follows: 402 0 1 2 3 403 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 404 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 405 | Set ID = 2 | Length = 28 octets | 406 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 407 | Template ID XXX | Field Count = 5 | 408 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 409 |0| maIdentifier = TBD1 | Field Length = 4 | 410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 411 |0| flowId = 148 | Field Length = 4 | 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 |0| periodNumber = TBD2 | Field Length = 4 | 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 415 |0| packetTotalCount = 86 | Field Length = 8 | 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 417 |0| octetTotalCount = 85 | Field Length = 8 | 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 420 The maIdenfier is used to identify and MA. 422 The flowId is a identifier that is unique within a specific 423 administrative domain (e.g., within one MCP). The MA and MCP have to 424 agree a flow identifier related to a specific flow. For example, the 425 flow identifier can be generated and maintained by a centralized 426 element. How to generate and maintain the flowId is out the scope of 427 this document. 429 The periodNumber is as defined in Section 3.2 of this document. 431 The packetTotalCount is used to carry the total transmitted/received 432 packets of a flow since the measurement start. 434 The octetTotalCount is used to carry the total transmitted/received 435 octets of a flow since the measurement start. 437 4.4. Packet Delay Template 439 The Packet Delay Template is used by a MA to report the packet delay 440 measurement statistic of a flow to the MCP; it SHOULD contain the 441 following Information Elements: 443 MA Identifier 445 The maIdentifier is as defined in Section 3.1 of this document. 447 flowId [IPFIX-IANA] 449 periodNumber [Section 3.2] 451 timestamp 453 The time when marked a packet, flowStartMicroseconds is used to 454 carry the timestamp: 456 flowStartMicroseconds[IPFIX-IANA] 458 An example of the Packet Delay Data Set is as follows: 460 0 1 2 3 461 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 462 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 463 | Set ID = 2 | Length = 24 octets | 464 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 465 | Template ID 258 | Field Count = 4 | 466 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 467 |0| maIdentifier = TBD1 | Field Length = 4 | 468 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 469 |0| flowId = 148 | Field Length = 4 | 470 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 471 |0| periodNumber = TBD2 | Field Length = 4 | 472 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 473 |0| flowStartMicroseconds = 154 | Field Length = 8 | 474 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 476 The maIdenfier is used to identify and MA. 478 The flowId is used to carry the flow identifier of a flow; the 479 structure is defined in Section 4.3 of this document. 481 The periodNumber is as defined in Section 3.2 of this document. 483 The flowStartMicroseconds is used to carry the timestamp of a marked 484 packet of a specific flow. 486 5. IANA Considerations 488 The IANA is requested to allocate 3new Information Elements codes for 489 the Information Elements defined in Section 3 from the IPFIX 490 Information Elements registry. 492 6. Security Considerations 494 This document does not bring new security issue to IPFIX. 496 7. Acknowledgements 498 The authors would like to thank Adrian Farrel for his review, 499 suggestion and comments to this document. 501 8. Contributing Authors 502 Hongming Liu 503 Huawei Technologies 505 Email: liuhongming@huawei.com 507 Yuanbin Yin 508 Huawei Technologies 510 Email: yinyuanbin@huawei.com 512 Rajiv Papneja 513 Huawei Technologies 515 Email: Rajiv.Papneja@huawei.com 517 Shailesh Abhyankar 518 Vodafone 519 Vodafone House, Ganpat Rao kadam Marg Lower Parel 520 Mumbai 40003 521 India 523 Email: shailesh.abhyankar@vodafone.com 525 Guangqing Deng 526 CNNIC 527 4 South 4th Street, Zhongguancun, Haidian District 528 Beijing 529 China 531 Email: dengguangqing@cnnic.cn 533 Yongliang Huang 534 China Unicom 536 Email: huangyl@dipmt.com 538 9. References 540 9.1. Normative References 542 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 543 Requirement Levels", BCP 14, RFC 2119, 544 DOI 10.17487/RFC2119, March 1997, 545 . 547 [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, 548 "Specification of the IP Flow Information Export (IPFIX) 549 Protocol for the Exchange of Flow Information", STD 77, 550 RFC 7011, DOI 10.17487/RFC7011, September 2013, 551 . 553 [RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model 554 for IP Flow Information Export (IPFIX)", RFC 7012, 555 DOI 10.17487/RFC7012, September 2013, 556 . 558 9.2. Informative References 560 [I-D.chen-ippm-coloring-based-ipfpm-framework] 561 Chen, M., Zheng, L., Mirsky, G., Fioccola, G., and T. 562 Mizrahi, "IP Flow Performance Measurement Framework", 563 draft-chen-ippm-coloring-based-ipfpm-framework-06 (work in 564 progress), March 2016. 566 [IPFIX-IANA] 567 "http://www.iana.org/assignments/ipfix/ipfix.xml". 569 Authors' Addresses 571 Mach(Guoyi) Chen (editor) 572 Huawei Technologies 574 Email: mach.chen@huawei.com 576 Lianshu Zheng (editor) 577 Huawei Technologies 579 Email: vero.zheng@huawei.com 581 Greg Mirsky (editor) 582 Ericsson 583 USA 585 Email: gregory.mirsky@ericsson.com