idnits 2.17.1 draft-ietf-opsawg-ipfix-bgp-community-03.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 : ---------------------------------------------------------------------------- == There are 6 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 17, 2017) is 2381 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 (-36) exists of draft-ietf-idr-bgp-extended-messages-22 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 opsawg Z. Li 3 Internet-Draft R. Gu 4 Updates: 7012 (if approved) China Mobile 5 Intended status: Standards Track J. Dong 6 Expires: April 20, 2018 Huawei Technologies 7 October 17, 2017 9 Export BGP community information in IP Flow Information Export (IPFIX) 10 draft-ietf-opsawg-ipfix-bgp-community-03 12 Abstract 14 This draft updates RFC7012 IPFIX information model by introducing 15 several information elements to enable IPFIX to export the BGP 16 community information, including BGP standard community defined in 17 RFC1997, BGP extended community defined in RFC4360, and BGP large 18 community defined in RFC8092. Network traffic flow information can 19 then be accumulated and analysed at the granularity specified by the 20 BGP communities, which is suitable for and needed by some traffic 21 optimization applications located in IPFIX collector, SDN controller 22 or PCE (Path Computation Element). 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at https://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on April 20, 2018. 41 Copyright Notice 43 Copyright (c) 2017 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (https://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 3. IEs for BGP Standard Community . . . . . . . . . . . . . . . 4 61 3.1. bgpCommunity . . . . . . . . . . . . . . . . . . . . . . 4 62 3.2. bgpSourceCommunityList . . . . . . . . . . . . . . . . . 4 63 3.3. bgpDestinationCommunityList . . . . . . . . . . . . . . . 5 64 4. IEs for BGP Extended Community . . . . . . . . . . . . . . . 5 65 4.1. bgpExtendedCommunity . . . . . . . . . . . . . . . . . . 6 66 4.2. bgpSourceExtendedCommunityList . . . . . . . . . . . . . 6 67 4.3. bgpDestinationExtendedCommunityList . . . . . . . . . . . 7 68 5. IEs for BGP Large Community . . . . . . . . . . . . . . . . . 7 69 5.1. bgpLargeCommunity . . . . . . . . . . . . . . . . . . . . 8 70 5.2. bgpSourceLargeCommunityList . . . . . . . . . . . . . . . 8 71 5.3. bgpDestinationLargeCommunityList . . . . . . . . . . . . 9 72 6. Operational Considerations . . . . . . . . . . . . . . . . . 9 73 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 74 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 75 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 76 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 77 10.1. Normative References . . . . . . . . . . . . . . . . . . 12 78 10.2. Informative References . . . . . . . . . . . . . . . . . 13 79 Appendix A. Application Example . . . . . . . . . . . . . . . . 14 80 A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 14 81 A.2. Data Set . . . . . . . . . . . . . . . . . . . . . . . . 15 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 84 1. Introduction 86 IP Flow Information Export (IPFIX) [RFC7011] provides network 87 administrators with traffic flow information using the information 88 elements (IEs) defined in [IANA-IPFIX] registries. Based on the 89 traffic flow information, network administrators know the amount and 90 direction of the traffic in their network, then they can optimize 91 their network when needed. For example, they can shift some flows 92 from the congested links to the low utilized links through a SDN 93 controller or PCE [RFC4655]. 95 [IANA-IPFIX] has already defined the following IEs for traffic flow 96 information exporting in different granularities: sourceIPv4Address, 97 sourceIPv4Prefix, destinationIPv4Address, destinationIPv4Prefix, 98 bgpSourceAsNumber, bgpDestinationAsNumber, bgpNextHopIPv4Address, 99 etc. In some circumstances, however, especially when traffic 100 engineering and optimization are executed in the Tier 1 or Tier 2 101 operators' backbone networks, traffic flow information based on these 102 IEs may not be suitable. Flow information based on IP address or IP 103 prefix may provide much too fine granularity for a large network. On 104 the contrary, flow information based on AS number may be too coarse. 105 BGP community [RFC1997], which describes a group of routes sharing 106 some common properties, is preferably used for traffic engineering at 107 the proper granularity [Community-TE] [RFC4384]. There is no IE 108 defined for BGP community information in [IANA-IPFIX] yet. 110 Flow information based on BGP community may be collected by a 111 mediator defined in [RFC6183]. Mediator is responsible for the 112 correlation between flow information and BGP community. However no 113 IEs are defined in [RFC6183] for exporting BGP community information 114 in IPFIX. Furthermore, to correlate the BGP community with the flow 115 information, mediator needs to learn BGP routes and perform lookup in 116 the BGP routing table to get the matching entry for specific flow. 117 Neither BGP route learning nor routing table lookup is trivial for a 118 mediator. Mediator is mainly introduced to release the performance 119 requirement for the exporter [RFC5982]. In fact, to obtain the 120 information for BGP related IEs that have already been defined, such 121 as bgpSourceAsNumber, bgpDestinationAsNumber, and 122 bgpNextHopIPv4Address, etc, exporter has to hold the up-to-date BGP 123 routing table and perform lookup in the BGP routing table. The 124 exporter can obtain the BGP community information in the same 125 procedure, thus exporting BGP community information adds no more 126 requirement for exporter. It is RECOMMENDED that the BGP community 127 information be exported by the exporter directly using IPFIX. 129 This draft introduces new IEs to extend the IPFIX information model 130 defined in [RFC7012] to export the BGP community information, 131 including BGP standard community defined in [RFC1997], BGP extended 132 community defined in [RFC4360], and BGP large community defined in 133 [RFC8092]. Flow information, including packetDeltaCount, 134 octetDeltaCount [RFC7012] etc, can then be accumulated and analysed 135 by the collector or other applications, such as SDN controller or PCE 136 [RFC4655], at the granularity specified by BGP community , which is 137 useful for traffic engineering or traffic optimization applications, 138 especially in the backbone network. 140 The IEs introduced in this document are applicable for both IPv4 and 141 IPv6 traffic. Both exporter and mediator can use these IEs to export 142 BGP community information in IPFIX. 144 2. Terminology 146 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 147 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 148 document are to be interpreted as described in [RFC2119]. 150 3. IEs for BGP Standard Community 152 [RFC1997] defines the BGP Communities attribute, called BGP Standard 153 Community in this document, which describes a group of routes sharing 154 some common properties. BGP Standard Communities are treated as 32 155 bit values as stated in[RFC1997]. 157 In order to export BGP standard community information along with 158 other flow information defined by IPFIX, three new IEs are 159 introduced. One is bgpCommunity, which is used to identify that the 160 value in this IE is a BGP standard community. The other two are 161 bgpSourceCommunityList and bgpDestinationCommunityList, which are 162 both basicList [RFC6313] of bgpCommunity, and are used to export BGP 163 standard community information corresponding to a specific flow's 164 source IP and destination IP respectively. 166 The detailed information of the three new IEs are shown in the 167 following sections. 169 3.1. bgpCommunity 171 ---------------------------------------------------------------------- 172 | ElementID | to be assigned by IANA | 173 |--------------------------------------------------------------------| 174 | Name | bgpCommunity | 175 |--------------------------------------------------------------------| 176 | Data Type | unsigned32 | 177 |--------------------------------------------------------------------| 178 | Data Type Semantics | identifier | 179 |--------------------------------------------------------------------| 180 | Description | BGP community as defined in [RFC1997] | 181 |--------------------------------------------------------------------| 182 | Units | none | 183 |--------------------------------------------------------------------| 185 Figure 1: bgpCommunity 187 3.2. bgpSourceCommunityList 188 ---------------------------------------------------------------------- 189 | ElementID | to be assigned by IANA | 190 |--------------------------------------------------------------------| 191 | Name | bgpSourceCommunityList | 192 |--------------------------------------------------------------------| 193 | Data Type | basicList, as specified in [RFC6313] | 194 |--------------------------------------------------------------------| 195 | Data Type Semantics | list | 196 |--------------------------------------------------------------------| 197 | Description | zero or more BGP communities corresponding | 198 | | with source IP address of a specific flow | 199 |--------------------------------------------------------------------| 200 | Units | none | 201 |--------------------------------------------------------------------| 203 Figure 2: bgpSourceCommunityList 205 3.3. bgpDestinationCommunityList 207 --------------------------------------------------------------------- 208 | ElementID | to be assigned by IANA | 209 |--------------------------------------------------------------------| 210 | Name | bgpDestinationCommunityList | 211 |--------------------------------------------------------------------| 212 | Data Type | basicList, as specified in [RFC6313] | 213 |--------------------------------------------------------------------| 214 | Data Type Semantics | list | 215 |--------------------------------------------------------------------| 216 | Description | zero or more BGP communities corresponding | 217 | |with destination IP address of a specific flow| 218 |--------------------------------------------------------------------| 219 | Units | none | 220 |--------------------------------------------------------------------| 222 Figure 3: bgpDestinationCommunityList 224 4. IEs for BGP Extended Community 226 [RFC4360] defines the BGP Extended Communities attribute, which 227 provides a mechanism for labeling the information carried in BGP. 228 Each Extended Community is encoded as an 8-octet quantity with the 229 format defined in [RFC4360]. 231 In order to export BGP Extended Community information together with 232 other flow information by IPFIX, three new IEs are introduced. The 233 first one is bgpExtendedCommunity, which is used to identify that the 234 value in this IE is a BGP Extended Community. The other two are 235 bgpSourceExtendedCommunityList and 236 bgpDestinationExtendedCommunityList, which are both basicList 237 [RFC6313] of bgpExtendedCommunity, and are used to export the BGP 238 Extended Community information corresponding to a specific flow's 239 source IP and destination IP respectively. 241 The detailed information of the three new IEs are shown in the 242 following sections. 244 4.1. bgpExtendedCommunity 246 ---------------------------------------------------------------------- 247 | ElementID | to be assigned by IANA | 248 |--------------------------------------------------------------------| 249 | Name | bgpExtendedCommunity | 250 |--------------------------------------------------------------------| 251 | Data Type | octetArray | 252 |--------------------------------------------------------------------| 253 | Data Type Semantics | default | 254 |--------------------------------------------------------------------| 255 | |BGP Extended Community as defined in [RFC4360]| 256 | Description |The size of this Information Element is 8 | 257 | |octets. | 258 |--------------------------------------------------------------------| 259 | Units | none | 260 |--------------------------------------------------------------------| 262 Figure 4: bgpExtendedCommunity 264 4.2. bgpSourceExtendedCommunityList 265 ---------------------------------------------------------------------- 266 | ElementID | to be assigned by IANA | 267 |--------------------------------------------------------------------| 268 | Name | bgpSourceExtendedCommunityList | 269 |--------------------------------------------------------------------| 270 | Data Type | basicList, as specified in [RFC6313] | 271 |--------------------------------------------------------------------| 272 | Data Type Semantics | list | 273 |--------------------------------------------------------------------| 274 | | zero or more BGP Extended Communities | 275 | Description | corresponding with source IP address | 276 | | of a specific flow | 277 |--------------------------------------------------------------------| 278 | Units | none | 279 |--------------------------------------------------------------------| 281 Figure 5: bgpSourceExtendedCommunityList 283 4.3. bgpDestinationExtendedCommunityList 285 ---------------------------------------------------------------------- 286 | ElementID | to be assigned by IANA | 287 |--------------------------------------------------------------------| 288 | Name | bgpDestinationExtendedCommunityList | 289 |--------------------------------------------------------------------| 290 | Data Type | basicList, as specified in [RFC6313] | 291 |--------------------------------------------------------------------| 292 | Data Type Semantics | list | 293 |--------------------------------------------------------------------| 294 | | zero or more BGP Extended communities | 295 | Description | corresponding with destination IP address | 296 | | of a specific flow | 297 |--------------------------------------------------------------------| 298 | Units | none | 299 |--------------------------------------------------------------------| 301 Figure 6: bgpDestinationExtendedCommunityList 303 5. IEs for BGP Large Community 305 [RFC8092] defines the BGP Large Communities attribute, which is 306 suitable for use with all Autonomous System Numbers (ASNs) including 307 four-octet ASNs. Each BGP Large Community is encoded as a 12-octet 308 quantity with the format defined in [RFC8092]. 310 In order to export BGP Large Community information together with 311 other flow information by IPFIX, three new IEs are introduced. The 312 first one is bgpLargeCommunity, which is used to identify that the 313 value in this IE is a BGP Large Community. The other two are 314 bgpSourceLargeCommunityList and bgpDestinationLargeCommunityList, 315 which are both basicList [RFC6313] of bgpLargeCommunity, and are used 316 to export the BGP Large Community information corresponding to a 317 specific flow's source IP and destination IP respectively. 319 The detailed information of the three new IEs are shown in the 320 following sections. 322 5.1. bgpLargeCommunity 324 ---------------------------------------------------------------------- 325 | ElementID | to be assigned by IANA | 326 |--------------------------------------------------------------------| 327 | Name | bgpLargeCommunity | 328 |--------------------------------------------------------------------| 329 | Data Type | octetArray | 330 |--------------------------------------------------------------------| 331 | Data Type Semantics | default | 332 |--------------------------------------------------------------------| 333 | | BGP Large Community as defined in [RFC8092] | 334 | Description | The size of this Information Element is 12 | 335 | | octets. | 336 |--------------------------------------------------------------------| 337 | Units | none | 338 |--------------------------------------------------------------------- 340 Figure 7: bgpLargeCommunity 342 5.2. bgpSourceLargeCommunityList 343 ---------------------------------------------------------------------- 344 | ElementID | to be assigned by IANA | 345 |--------------------------------------------------------------------| 346 | Name | bgpSourceLargeCommunityList | 347 |--------------------------------------------------------------------| 348 | Data Type | basicList, as specified in [RFC6313] | 349 |--------------------------------------------------------------------| 350 | Data Type Semantics | list | 351 |--------------------------------------------------------------------| 352 | | zero or more BGP Large Communities | 353 | Description | corresponding with source IP address | 354 | | of a specific flow | 355 |--------------------------------------------------------------------| 356 | Units | none | 357 |--------------------------------------------------------------------| 359 Figure 8: bgpSourceLargeCommunityList 361 5.3. bgpDestinationLargeCommunityList 363 ---------------------------------------------------------------------- 364 | ElementID | to be assigned by IANA | 365 |--------------------------------------------------------------------| 366 | Name | bgpDestinationLargeCommunityList | 367 |--------------------------------------------------------------------| 368 | Data Type | basicList, as specified in [RFC6313] | 369 |--------------------------------------------------------------------| 370 | Data Type Semantics | list | 371 |--------------------------------------------------------------------| 372 | Description | zero or more BGP Large communities | 373 | | corresponding with destination IP address | 374 | | of a specific flow | 375 |--------------------------------------------------------------------| 376 | Units | none | 377 |--------------------------------------------------------------------| 379 Figure 9: bgpDestinationLargeCommunityList 381 6. Operational Considerations 383 The maximum length of an IPFIX message is 65535 bytes as per 384 [RFC7011] , and the maximum length of a normal BGP message is 4096 385 bytes as per [RFC4271]. Since BGP communities, including standard, 386 extended, and large communities , are BGP path attributes carried in 387 BGP Update messages, the total length of these attributes can not 388 exceed the length of a BGP message, i.e. 4096 bytes. So one IPFIX 389 message with maximum length of 65535 bytes has enough space to fit 390 all the communities related to a specific flow, both the source IP 391 and the destination IP related. 393 [I-D.ietf-idr-bgp-extended-messages] extends the maximum size of a 394 BGP Update message to 65535 bytes. Then theoretically the BGP 395 community information related to a specific flow may exceed the 396 length one IPFIX message. However, according to the information 397 about the networks in the field, the number of BGP communities in one 398 BGP route is usually no more than 10. Nevertheless, BGP speakers 399 that support the extended message SHOULD be careful to export the BGP 400 communities in the IPFIX message properly, such as only convey as 401 many communities as possible in the IPFIX message. The collector 402 which receives an IPFIX message with maximum length and BGP 403 communities contained in its data set SHOULD be aware that the BGP 404 communities may be truncated due to limited message space. In this 405 case, it is RECOMMENDED to configure export policy of BGP communities 406 on the exporter to limit the BGP communities to be exported, so as to 407 only export some specific communities,or not to export some specific 408 communities. 410 If needed, we may consider to extend the message length of IPFIX 411 [RFC7011] from 16 bits to 32 bits to solve this problem completely. 412 The detailed mechanism is out of the scope of this document. 414 7. Security Considerations 416 This document only defines three new IEs for IPFIX. This document 417 itself does not directly introduce security issues. The same 418 security considerations as for the IPFIX Protocol Specification 419 [RFC7011] and Information Model [RFC7012] apply. 421 As the BGP community information is deducible by other means, there 422 are no increased privacy concerns, neither. 424 8. IANA Considerations 426 This draft specifies the following IPFIX IEs to export BGP community 427 information along with other flow information. 429 The Element IDs for these IEs are solicited to be assigned by IANA. 430 The following table is for IANA's reference to put in each field in 431 the registry. 433 ---------------------------------------------------------------------- 434 |ElementID| Name | Data Type|Data Type Semantics| 435 |--------------------------------------------------------------------| 436 | TBA1 | bgpCommunity |unsigned32| identifier | 437 |--------------------------------------------------------------------| 438 | TBA2 | bgpSourceCommunityList | basicList| list | 439 |--------------------------------------------------------------------| 440 | TBA3 |bgpDestinationCommunityList| basicList| list | 441 |--------------------------------------------------------------------| 442 | TBA4 | bgpExtendedCommunity |octetArray| default | 443 |--------------------------------------------------------------------| 444 | TBA5 | bgpSourceExtended | | | 445 | | CommunityList | basicList| list | 446 |--------------------------------------------------------------------| 447 | TBA6 | bgpDestinationExtended | | | 448 | | CommunityList | basicList| list | 449 |--------------------------------------------------------------------| 450 | TBA7 | bgpLargeCommunity |octetArray| default | 451 |--------------------------------------------------------------------| 452 | TBA8 |bgpSourceLargeCommunityList| basicList| list | 453 |--------------------------------------------------------------------| 454 | TBA9 | bgpDestinationLarge | | | 455 | | CommunityList | basicList| list | 456 |--------------------------------------------------------------------| 458 ---------------------------------------------------------------------- 459 |ElementID| Description | Units | 460 |--------------------------------------------------------------------| 461 | TBA1 | BGP community as defined in [RFC1997] | | 462 |--------------------------------------------------------------------| 463 | TBA2 | zero or more BGP communities corresponding | | 464 | | with source IP address of a specific flow | | 465 |--------------------------------------------------------------------| 466 | TBA3 | zero or more BGP communities corresponding | | 467 | |with destination IP address of a specific flow| | 468 |--------------------------------------------------------------------| 469 | TBA4 |BGP Extended Community as defined in [RFC4360]| | 470 | |The size of this IE is 8 octets | | 471 |--------------------------------------------------------------------| 472 | | zero or more BGP Extended Communities | | 473 | TBA5 | corresponding with source IP address of | | 474 | | a specific flow | | 475 |--------------------------------------------------------------------| 476 | | zero or more BGP Extended communities | | 477 | TBA6 | corresponding with destination IP address | | 478 | | of a specific flow | | 479 |--------------------------------------------------------------------| 480 | TBA7 | BGP Large Community as defined in [RFC8092] | | 481 | | The size of this IE is 12 octets. | | 482 |--------------------------------------------------------------------| 483 | | zero or more BGP Large Communities | | 484 | TBA8 | corresponding with source IP address | | 485 | | of a specific flow | | 486 |--------------------------------------------------------------------| 487 | | zero or more BGP Large communities | | 488 | TBA9 | corresponding with destination IP address | | 489 | | of a specific flow | | 490 |--------------------------------------------------------------------| 492 ---------------------------------------------------------------------- 493 |ElementID| Range | References | Requester | Revision | date | 494 |--------------------------------------------------------------------| 495 | TBA1 | | RFC1997 |this draft | 0 | | 496 |--------------------------------------------------------------------| 497 | TBA2 | |RFC6313,RFC1997|this draft | 0 | | 498 |--------------------------------------------------------------------| 499 | TBA3 | |RFC6313,RFC1997|this draft | 0 | | 500 |--------------------------------------------------------------------| 501 | TBA4 | | RFC4360 |this draft | 0 | | 502 |--------------------------------------------------------------------| 503 | TBA5 | |RFC6313,RFC4360|this draft | 0 | | 504 |--------------------------------------------------------------------| 505 | TBA6 | |RFC6313,RFC4360|this draft | 0 | | 506 |--------------------------------------------------------------------| 507 | TBA7 | | RFC8092 |this draft | 0 | | 508 |--------------------------------------------------------------------| 509 | TBA8 | |RFC6313,RFC8092|this draft | 0 | | 510 |--------------------------------------------------------------------| 511 | TBA9 | |RFC6313,RFC8092|this draft | 0 | | 512 |--------------------------------------------------------------------| 514 Figure 10: IANA Considerations 516 9. Acknowledgements 518 The authors would like to thank Benoit Claise and Paul Aitken for 519 their comments and suggestions to promote this document. 520 Appreciations are given to Tianran Zhou, Warren Kumari, Jeffrey Haas, 521 Ignas Bagdonas, Stewart Bryant, Paolo Lucente, Job Snijders, Jared 522 Mauch, Rudiger Volk, etc, for their discussion, comments and 523 suggestions in the face to face meetings and in the mail list. 525 10. References 527 10.1. Normative References 529 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 530 Requirement Levels", BCP 14, RFC 2119, 531 DOI 10.17487/RFC2119, March 1997, 532 . 534 [RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates, 535 "Export of Structured Data in IP Flow Information Export 536 (IPFIX)", RFC 6313, DOI 10.17487/RFC6313, July 2011, 537 . 539 [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, 540 "Specification of the IP Flow Information Export (IPFIX) 541 Protocol for the Exchange of Flow Information", STD 77, 542 RFC 7011, DOI 10.17487/RFC7011, September 2013, 543 . 545 [RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model 546 for IP Flow Information Export (IPFIX)", RFC 7012, 547 DOI 10.17487/RFC7012, September 2013, 548 . 550 10.2. Informative References 552 [Community-TE] 553 Shao, W., Devienne, F., Iannone, L., and JL. Rougier, "On 554 the use of BGP communities for fine-grained inbound 555 traffic engineering", Computer Science 27392(1):476-487, 556 November 2015. 558 [I-D.ietf-idr-bgp-extended-messages] 559 Bush, R., Patel, K., and D. Ward, "Extended Message 560 support for BGP", draft-ietf-idr-bgp-extended-messages-22 561 (work in progress), August 2017. 563 [IANA-IPFIX] 564 "IP Flow Information Export (IPFIX) Entities", 565 . 567 [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities 568 Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, 569 . 571 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 572 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 573 DOI 10.17487/RFC4271, January 2006, 574 . 576 [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended 577 Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, 578 February 2006, . 580 [RFC4384] Meyer, D., "BGP Communities for Data Collection", BCP 114, 581 RFC 4384, DOI 10.17487/RFC4384, February 2006, 582 . 584 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation 585 Element (PCE)-Based Architecture", RFC 4655, 586 DOI 10.17487/RFC4655, August 2006, 587 . 589 [RFC5982] Kobayashi, A., Ed. and B. Claise, Ed., "IP Flow 590 Information Export (IPFIX) Mediation: Problem Statement", 591 RFC 5982, DOI 10.17487/RFC5982, August 2010, 592 . 594 [RFC6183] Kobayashi, A., Claise, B., Muenz, G., and K. Ishibashi, 595 "IP Flow Information Export (IPFIX) Mediation: Framework", 596 RFC 6183, DOI 10.17487/RFC6183, April 2011, 597 . 599 [RFC8092] Heitz, J., Ed., Snijders, J., Ed., Patel, K., Bagdonas, 600 I., and N. Hilliard, "BGP Large Communities Attribute", 601 RFC 8092, DOI 10.17487/RFC8092, February 2017, 602 . 604 Appendix A. Application Example 606 In this section, we give an example to show the encoding format for 607 the three new introduced IEs. 609 Flow information including BGP communities is shown in the below 610 table. Suppose we want all the fields to be reported by IPFIX. 612 ----------------------------------------------------------------------- 613 |Source ip|Destination ip |Source BGP community| Destination BGP | 614 | | | | community | 615 ----------------------------------------------------------------------- 616 | 1.1.1.1 | 2.2.2.2 |1:1001,1:1002,8:1001| 2:1002,8:1001 | 617 ----------------------------------------------------------------------- 618 | 3.3.3.3 | 4.4.4.4 |3:1001,3:1002,8:1001| 4:1001,8:1001 | 619 ----------------------------------------------------------------------- 621 Figure 11: Flow information including BGP communities 623 A.1. Template Record 624 0 1 2 3 625 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 626 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 627 | SET ID = 2 | Length = 24 | 628 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 629 | Template ID = 256 | Field Count = 4 | 630 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 631 |0| SourceIPv4Address = 8 | Field length = 4 | 632 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 633 |0| DestinationIPv4Address = 12 | Field length = 4 | 634 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 635 |0| bgpSourceCommunityList = 459| Field length = 0xFFFF | 636 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 637 |0| bgpDestinationCommunityList | Field length = 0xFFFF | 638 | | = 460 | | 639 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 641 Figure 12: Template Record Encoding Format 643 In this example, the Template ID is 256, which will be used in the 644 data record. The field length for bgpSourceCommunityList and 645 bgpDestinationCommunityList is 0xFFFF, which means the length of this 646 IE is variable, the actual length of this IE is indicated by the list 647 length field in the basic list format as per [RFC6313]. 649 A.2. Data Set 651 The data set is represented as follows: 653 0 1 2 3 654 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 655 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 656 | SET ID = 256 | Length = 92 | 657 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 658 | SourceIPv4Address = 1.1.1.1 | 659 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 660 | DestinationIPv4Address = 2.2.2.2 | 661 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 662 | 255 | List length = 17 |semantic=allof | 663 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 664 | bgpCommunity = 458 | Field Len = 4 | 665 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 666 | BGP Source Community Value 1 = 1:1001 | 667 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 668 | BGP Source Community Value 2 = 1:1002 | 669 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 670 | BGP Source Community Value 3 = 8:1001 | 671 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 672 | 255 | List length = 13 |semantic =allof| 673 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 674 | bgpCommunity = 458 | Field Len = 4 | 675 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 676 | BGP Destination Community Value 1 = 2:1002 | 677 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 678 | BGP Destination Community Value 2 = 8:1001 | 679 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 680 | SourceIPv4Address = 3.3.3.3 | 681 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 682 | DestinationIPv4Address = 4.4.4.4 | 683 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 684 | 255 | List length = 17 |semantic =allof| 685 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 686 | bgpCommunity = 458 | Field Len = 4 | 687 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 688 | BGP Source Community Value 1 = 3:1001 | 689 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 690 | BGP Source Community Value 2 = 3:1002 | 691 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 692 | BGP Source Community Value 3 = 8:1001 | 693 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 694 | 255 | List length = 13 |semantic =allof| 695 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 696 | bgpCommunity = 458 | Field Len = 4 | 697 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 698 | BGP Destination Community Value 1 = 4:1001 | 699 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 700 | BGP Destination Community Value 2 = 8:1001 | 701 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 703 Figure 13: Data Set Encoding Format 705 Authors' Addresses 707 Zhenqiang Li 708 China Mobile 709 32 Xuanwumen West Ave, Xicheng District 710 Beijing 100053 711 China 713 Email: li_zhenqiang@hotmail.com 714 Rong Gu 715 China Mobile 716 32 Xuanwumen West Ave, Xicheng District 717 Beijing 100053 718 China 720 Email: gurong_cmcc@outlook.com 722 Jie Dong 723 Huawei Technologies 724 Huawei Campus, No. 156 Beiqing Rd. 725 Beijing 100095 726 China 728 Email: jie.dong@huawei.com