idnits 2.17.1 draft-chen-ippm-ipfpm-report-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 (July 3, 2014) is 3586 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) == Outdated reference: A later version (-06) exists of draft-chen-ippm-coloring-based-ipfpm-framework-01 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 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 H. Liu 5 Expires: January 4, 2015 Y. Yin 6 R. Papneja 7 Huawei Technologies 8 G. Mirsky , Ed. 9 Ericsson 10 S. Abhyankar 11 Vodafone 12 G. Deng 13 CNNIC 14 Y. Huang 15 China Unicom 16 July 3, 2014 18 IP Flow Performance Measurement Report 19 draft-chen-ippm-ipfpm-report-00 21 Abstract 23 A "marking" based IP Flow Performance Measurement (IPFPM) framework 24 is specified in draft-chen-ippm-coloring-based-ipfpm-framework. IP 25 Flow Information eXport (IPFIX) is used for exporting the performance 26 of IPFPM. Several new Information Elements of IPFIX are defined for 27 IPFPM in this document. 29 Requirements Language 31 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 32 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 33 document are to be interpreted as described in RFC 2119 [RFC2119]. 35 Status of This Memo 37 This Internet-Draft is submitted in full conformance with the 38 provisions of BCP 78 and BCP 79. 40 Internet-Drafts are working documents of the Internet Engineering 41 Task Force (IETF). Note that other groups may also distribute 42 working documents as Internet-Drafts. The list of current Internet- 43 Drafts is at http://datatracker.ietf.org/drafts/current/. 45 Internet-Drafts are draft documents valid for a maximum of six months 46 and may be updated, replaced, or obsoleted by other documents at any 47 time. It is inappropriate to use Internet-Drafts as reference 48 material or to cite them other than as "work in progress." 49 This Internet-Draft will expire on January 4, 2015. 51 Copyright Notice 53 Copyright (c) 2014 IETF Trust and the persons identified as the 54 document authors. All rights reserved. 56 This document is subject to BCP 78 and the IETF Trust's Legal 57 Provisions Relating to IETF Documents 58 (http://trustee.ietf.org/license-info) in effect on the date of 59 publication of this document. Please review these documents 60 carefully, as they describe your rights and restrictions with respect 61 to this document. Code Components extracted from this document must 62 include Simplified BSD License text as described in Section 4.e of 63 the Trust Legal Provisions and are provided without warranty as 64 described in the Simplified BSD License. 66 Table of Contents 68 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 69 2. Measurement Data Report . . . . . . . . . . . . . . . . . . . 3 70 3. IPFIX Information Element for IPFPM . . . . . . . . . . . . . 4 71 3.1. maIdentifier . . . . . . . . . . . . . . . . . . . . . . 4 72 3.2. periodNumber . . . . . . . . . . . . . . . . . . . . . . 5 73 3.3. maStatus . . . . . . . . . . . . . . . . . . . . . . . . 5 74 4. Templates for IPFPM . . . . . . . . . . . . . . . . . . . . . 6 75 4.1. MA Status Options Template . . . . . . . . . . . . . . . 6 76 4.2. Flow Options Template . . . . . . . . . . . . . . . . . . 6 77 4.3. Packet Loss Template . . . . . . . . . . . . . . . . . . 9 78 4.4. Packet Delay Template . . . . . . . . . . . . . . . . . . 10 79 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 80 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 81 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 82 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 83 8.1. Normative References . . . . . . . . . . . . . . . . . . 12 84 8.2. Informative References . . . . . . . . . . . . . . . . . 12 85 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 87 1. Introduction 89 A "marking" based IP Flow Performance Measurement (IPFPM) framework 90 is specified in [I-D.chen-ippm-coloring-based-ipfpm-framework]. This 91 document is the companion document of 92 [I-D.chen-ippm-coloring-based-ipfpm-framework]. The IPFPM framework 93 describes a mechanism where data packets are marked so that they form 94 blocks of data. No additional delimiting OAM is needed and the 95 performance metrics can be measured in-service without the insertion 96 of additional traffic. Furthermore, because marking based IP 97 performance measurement does not require extra OAM packets for 98 traffic delimitation, it can be used in situations where there is 99 packets re-ordering. IP Flow Information eXport (IPFIX) [RFC7011] is 100 used for exporting the performance of IPFPM. Several new Information 101 Elements of IPFIX are defined for IPFPM in this document. 103 2. Measurement Data Report 105 In the IPFPM reference model, the Measurement Agent (MA) executes the 106 measurement actions (e.g., marks the packets, counts the packets, 107 records the timestamps, etc.), and reports the data to the 108 Measurement Control Point (MCP). The MCP is a centralized 109 calculation element, responsible for collecting measurement data from 110 MA and calculating the performance metrics according to the received 111 measurement data from the MAs. During the performance measurement 112 period, each MA reports performance measurementmeasurement data to 113 the MCP, and the MCP will compute the performance measurement results 114 according to the received measurement data. For a specific IP flow, 115 for either packet delay or loss measurement, there will be at least 116 one upstream and one downstream MA. For accurate measurements, time 117 synchronization is required and the Period Number 118 [I-D.chen-ippm-coloring-based-ipfpm-framework] is used by MCP to 119 uniquely identify and correlate the packet counts/ timestamps between 120 the upstream and downstream MAs for a specific block of markers or 121 marked packet. 123 For packet loss measurement, the following information is required to 124 report to the MCP: 126 MA Identifier 128 Flow Identifier (identify the flow to be measured) 130 Period Number 132 Packet Number Count 134 Packet Octets Count 136 For packet delay measurement, the following information is required 137 to report to the MCP: 139 MA Identifier 141 Flow Identifier 143 Period Number 144 Timestamp 146 In addition, a MA may report some status (e.g., whether a MA is time 147 synchronized) to the MCP, hence to help the MCP to determine whether 148 measurement data from a MA is valid and can be used for computation. 149 The following information may be included: 151 MA Identifier 153 MA Status 155 3. IPFIX Information Element for IPFPM 157 The IPFIX protocol [RFC7011] defines how IP Flow information can be 158 exported from routers, measurement probes, or other devices. It 159 defines many Information Elements [RFC7012] that can be used to carry 160 and export the above information from MAs to MCP. Section 2 lists 161 the statistic Information and status information need to be reported 162 for IPFPM. Most of them can be identified with the existing 163 Information Elements. New Information Element is defined for MA 164 Identifer, Period Number and MA Status respectively in the following 165 sections. 167 Flow Identifier: flowId (148) 169 Packet Number Count: packetTotalCount (86) 171 Packet Octets Count: octetTotalCount (85) 173 Timestamp: flowStartMicroseconds (154) 175 3.1. maIdentifier 177 Description: The maIdentifier is used to identify a MA. An 178 maIdentifiler is unique within a specific administrative domain (e.g. 179 within one MCP). The MA identifier can be generated and maintained 180 by MCP. How to generate and maintain the maIdentifier is out the 181 scope of this document. 183 Abstract Data Type: unsigned32 185 ElementId: TBD1 187 Status: current 189 3.2. periodNumber 191 Description: The periodNumber (PN) is used to identify a packet count 192 or timestamp that belongs to a specific block of markers or marked 193 packet. The MCP uses it to determine whether any two or more packet 194 counts (from distributed MAs) are related to the same block of 195 markers or any two timestamps are related to the same marked packet. 196 The PN is generated each time a MA reads the packet counts and 197 timestamp, and is equal to the modulo of the local time (when the 198 counts and timestamps are read) and the interval of the marking time 199 period [I-D.chen-ippm-coloring-based-ipfpm-framework]. 201 Abstract Data Type: unsigned32 203 ElementId: TBD2 205 Status: current 207 3.3. maStatus 209 Description: The maStatus is used to carry status information of a MA 210 (For example, whether a MA has already time synchronized, whether is 211 a upstream or downstream MA for a specific measured flow). 213 Abstract Data Type: unsigned16 215 ElementId: TBD3 217 Status: current 219 The maStaus is defined as follows: 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 | Reserved |U|T| 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 225 Two bits are defined in this document. The T bit (Time synchronized 226 bit) it is used to indicate whether a MA is time synchronized. When 227 the T bit set, the MA is time synchronized; when the T bit is 228 cleared, the MA is not time synchronized. The MCP MUST calculate the 229 results when all related MAs of a flow are time synchronized, 230 otherwise, the results will not correct. The U bit ( Upstream MA 231 bit) is used to indicate whether a MA is the upstream or downstream 232 TLP for an IP flow. When the U bit set, the MA is the upstream MA of 233 the flow; otherwise, the MA is the downstream MA of the flow. 235 4. Templates for IPFPM 237 4.1. MA Status Options Template 239 The MA Status Options Template is used to report the status of a MA; 240 it SHOULD contain the following Information Elements: 242 meteringProcessId (scope) [IPFIX-IANA] 244 MA Identifier 246 The maIdentifier is as defined in Section 3.1 of this document. 248 MA Status 250 The maStatus is as defined in Section 3.3 of this document. 252 The Data Records specified by the MA Status Options Template SHOULD 253 be exported once the IPFIX session established or when status 254 changed. 256 An example of the MA Status Options Template Set is as follows: 258 0 1 2 3 259 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 260 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 261 | Set ID = 3 | Length = 24 | 262 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 263 | Template ID XXX | Field Count = 3 | 264 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 265 | Scope Field Count = 1 |0| meteringProcessId = 143 | 266 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 267 | Scope 1 Field Length = 4 |0| maIdentifier = TBD1 | 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 269 | Scope 1 Field Length = 4 |0| ma Status = TBD3 | 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 | Field Length = 1 | Padding | 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 274 4.2. Flow Options Template 276 The Flow Options Template is used to report all the configured flows 277 (to be measured) on a MA. It SHOULD include the following the 278 Information Elements: 280 meteringProcessId (scope) [IPFIX-IANA] 281 MA Identifier 283 The maIdentifier is as defined in Section 3.1 of this document. 285 maStatus [Section 3.3] 287 flowId [IPFIX-IANA] 289 protocolIdentifier [IPFIX-IANA] 291 Source IP address 293 The source IP address or prefix of an IP flow, for this address, 294 any of the following Information Elements can be used: 296 sourceIPv4Address [IPFIX-IANA] 298 sourceIPv6Address [IPFIX-IANA] 300 sourceIPv4Prefix [IPFIX-IANA] 302 sourceIPv6Prefix [IPFIX-IANA] 304 Source IP prefix length 306 The source IP prefix length of a prefix, any of the following 307 Information Elements can be used: 309 sourceIPv4PrefixLength [IPFIX-IANA] 311 sourceIPv6PrefixLength [IPFIX-IANA] 313 Source port 315 The source port of an IP flow, any of the following Information 316 Elements can be used: 318 udpSourcePort [IPFIX-IANA] 320 tcpSourcePort [IPFIX-IANA] 322 Destination IP address 324 The destination IP address or prefix of an IP flow, for this 325 address, any of the following Information Elements can be used: 327 destinationIPv4Address [IPFIX-IANA] 328 destinationIPv6Address [IPFIX-IANA] 330 destinationIPv4Prefix [IPFIX-IANA] 332 destinationIPv6Prefix [IPFIX-IANA] 334 Destination IP prefix length 336 The destination IP prefix length of a prefix, any of the following 337 Information Elements can be used: 339 destinationIPv4PrefixLength [IPFIX-IANA] 341 destinationIPv6PrefixLength [IPFIX-IANA] 343 Destination port 345 The destination port of an IP flow, any of the following 346 Information Elements can be used: 348 udpDestinationPort [IPFIX-IANA] 350 tcpDestinationPort [IPFIX-IANA] 352 The Data Records specified by the Flow Options Template SHOULD be 353 exported once the IPFIX session established or when the configured 354 flows changed (e.g., a new flow is added for measurement or a flow 355 deleted to stop the measurement). 357 An example of the Flow Options Template Set is as follows: 359 0 1 2 3 360 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 361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 362 | Set ID = 3 | Length = 52 | 363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 364 | Template ID XXX | Field Count = 10 | 365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 366 | Scope Field Count = 1 |0| meteringProcessId=143 | 367 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 368 | Scope 1 Field Length = 4 |0| maIdentifier = TBD1 | 369 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 370 | Field Length = 4 |0| maStatus = TBD3 | 371 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 372 | Field Length = 1 |0| flowID = 148 | 373 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 374 | Field Length = 4 |0| protocolIdentifier = 4 | 375 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 376 | Field Length = 1 |0| sourceIPv4Address = 8 | 377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 378 | Field Length = 4 |0| udpSourcePort = 4 | 379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 380 | Field Length = 2 |0| destinationIPv4Address = 4 | 381 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 382 | Field Length = 4 |0| udpDestinationPort = 4 | 383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 384 | Field Length = 4 |0| udpDestinationPort = 4 | 385 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 386 | Field Length = 2 | Padding | 387 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 389 4.3. Packet Loss Template 391 The Packet Loss Template is used by a MA to report the packet loss 392 measurement statistic of a flow to the MCP; it SHOULD contain the 393 following Information Elements: 395 MA Identifier 397 The maIdentifier is as defined in Section 3.1 of this document. 399 flowId[IPFIX-IANA] 401 periodNumber [Section 3.2] 403 packetTotalCount[IPFIX-IANA] 405 octetTotalCount[IPFIX-IANA] 406 An example of the Packet Loss Data Set is as follows: 408 0 1 2 3 409 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 410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 411 | Set ID = 2 | Length = 28 octets | 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 | Template ID XXX | Field Count = 5 | 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 415 |0| maIdentifier = TBD1 | Field Length = 4 | 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 417 |0| flowId = 148 | Field Length = 4 | 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 419 |0| periodNumber = TBD2 | Field Length = 4 | 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 |0| packetTotalCount = 86 | Field Length = 8 | 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 |0| octetTotalCount = 85 | Field Length = 8 | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 426 The maIdenfier is used to identify and MA. 428 The flowId is a identifier that is unique within a specific 429 administrative domain (e.g., within one MCP). The MA and MCP have to 430 agree a flow identifier related to a specific flow. For example, the 431 flow identifier can be generated and maintained by a centralized 432 element. How to generate and maintain the flowId is out the scope of 433 this document. 435 The periodNumber is as defined in Section 3.2 of this document. 437 The packetTotalCount is used to carry the total transmitted/received 438 packets of a flow since the measurement start. 440 The octetTotalCount is used to carry the total transmitted/received 441 octets of a flow since the measurement start. 443 4.4. Packet Delay Template 445 The Packet Delay Template is used by a MA to report the packet delay 446 measurement statistic of a flow to the MCP; it SHOULD contain the 447 following Information Elements: 449 MA Identifier 451 The maIdentifier is as defined in Section 3.1 of this document. 453 flowId [IPFIX-IANA] 455 periodNumber [Section 3.2] 457 timestamp 459 The time when marked a packet, flowStartMicroseconds is used to 460 carry the timestamp: 462 flowStartMicroseconds[IPFIX-IANA] 464 An example of the Packet Delay Data Set is as follows: 466 0 1 2 3 467 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 468 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 469 | Set ID = 2 | Length = 24 octets | 470 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 471 | Template ID 258 | Field Count = 4 | 472 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 473 |0| maIdentifier = TBD1 | Field Length = 4 | 474 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 475 |0| flowId = 148 | Field Length = 4 | 476 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 477 |0| periodNumber = TBD2 | Field Length = 4 | 478 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 479 |0| flowStartMicroseconds = 154 | Field Length = 8 | 480 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 482 The maIdenfier is used to identify and MA. 484 The flowId is used to carry the flow identifier of a flow; the 485 structure is defined in Section 4.3 of this document. 487 The periodNumber is as defined in Section 3.2 of this document. 489 The flowStartMicroseconds is used to carry the timestamp of a marked 490 packet of a specific flow. 492 5. IANA Considerations 494 The IANA is requested to allocate 3new Information Elements codes for 495 the Information Elements defined in Section 3 from the IPFIX 496 Information Elements registry. 498 6. Security Considerations 500 This document does not bring new security issue to IPFIX. 502 7. Acknowledgements 504 The authors would like to thank Adrian Farrel for his review, 505 suggestion and comments to this document. 507 8. References 509 8.1. Normative References 511 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 512 Requirement Levels", BCP 14, RFC 2119, March 1997. 514 [RFC7011] Claise, B., Trammell, B., and P. Aitken, "Specification of 515 the IP Flow Information Export (IPFIX) Protocol for the 516 Exchange of Flow Information", STD 77, RFC 7011, September 517 2013. 519 [RFC7012] Claise, B. and B. Trammell, "Information Model for IP Flow 520 Information Export (IPFIX)", RFC 7012, September 2013. 522 8.2. Informative References 524 [I-D.chen-ippm-coloring-based-ipfpm-framework] 525 Chen, M., Liu, H., Yin, Y., Papneja, R., Abhyankar, S., 526 Deng, G., and Y. Huang, "Coloring based IP Flow 527 Performance Measurement Framework", draft-chen-ippm- 528 coloring-based-ipfpm-framework-01 (work in progress), 529 October 2013. 531 [IPFIX-IANA] 532 "http://www.iana.org/assignments/ipfix/ipfix.xml", . 534 Authors' Addresses 536 Mach(Guoyi) Chen (editor) 537 Huawei Technologies 539 Email: mach.chen@huawei.com 541 Lianshu Zheng (editor) 542 Huawei Technologies 544 Email: vero.zheng@huawei.com 545 Hongming Liu 546 Huawei Technologies 548 Email: liuhongming@huawei.com 550 Yuanbin Yin 551 Huawei Technologies 553 Email: yinyuanbin@huawei.com 555 Rajiv Papneja 556 Huawei Technologies 558 Email: Rajiv.Papneja@huawei.com 560 Greg Mirsky (editor) 561 Ericsson 562 USA 564 Email: gregory.mirsky@ericsson.com 566 Shailesh Abhyankar 567 Vodafone 568 Vodafone House, Ganpat Rao kadam Marg Lower Parel 569 Mumbai 40003 570 India 572 Email: shailesh.abhyankar@vodafone.com 574 Guangqing Deng 575 CNNIC 576 4 South 4th Street, Zhongguancun, Haidian District 577 Beijing 578 China 580 Email: dengguangqing@cnnic.cn 582 Yongliang Huang 583 China Unicom 585 Email: huangyl@dipmt.com