idnits 2.17.1 draft-li-opsawg-ipfix-bgp-community-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 : ---------------------------------------------------------------------------- ** There are 7 instances of too long lines in the document, the longest one being 2 characters in excess of 72. ** The abstract seems to contain references ([RFC7012]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == 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 28, 2016) is 2731 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: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 opsawg Z. Li, Ed. 3 Internet-Draft R. Gu, Ed. 4 Intended status: Standards Track China Mobile 5 Expires: May 1, 2017 J. Dong 6 Huawei Technologies 7 October 28, 2016 9 Export BGP community information in IP Flow Information Export (IPFIX) 10 draft-li-opsawg-ipfix-bgp-community-01 12 Abstract 14 This draft specifies an extension to the IPFIX information model 15 defined in [RFC7012] to export the BGP community information. Three 16 information elements, bgpCommunity, bgpSourceCommunityList and 17 bgpDestinationCommunityList, are introduced in this document to carry 18 the community information for the source IP and destination IP 19 respectively. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on May 1, 2017. 38 Copyright Notice 40 Copyright (c) 2016 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. BGP Community Information Elements . . . . . . . . . . . . . 3 58 3.1. bgpCommunity . . . . . . . . . . . . . . . . . . . . . . 4 59 3.2. bgpSourceCommunityList . . . . . . . . . . . . . . . . . 4 60 3.3. bgpDestinationCommunityList . . . . . . . . . . . . . . . 4 61 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 62 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 63 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 64 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 65 7.1. Normative References . . . . . . . . . . . . . . . . . . 5 66 7.2. Informative References . . . . . . . . . . . . . . . . . 6 67 Appendix A. Application Example . . . . . . . . . . . . . . . . 7 68 A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 7 69 A.2. Data Set . . . . . . . . . . . . . . . . . . . . . . . . 8 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 72 1. Introduction 74 IP Flow Information Export (IPFIX) [RFC7011] provides network 75 administrators with traffic flow information using the information 76 elements (IEs) defined in [IANA-IPFIX] registries. Based on the 77 traffic flow information, network administrators know the amount and 78 direction of the traffic in their network, then they can optimize 79 their network when needed. For example, they can steer some flows 80 from the congested links to the low utilised links. 82 [IANA-IPFIX] has already defined the following IEs for traffic flow 83 information exporting in different grain: sourceIPv4Address, 84 sourceIPv4Prefix, destinationIPv4Address, destinationIPv4Prefix, 85 bgpSourceAsNumber, bgpDestinationAsNumber, bgpNextHopIPv4Address, 86 etc. In some circumstances, however, especially when traffic 87 engineering and optimazation are used in the Tier 1 or Tier 2 88 operators' backbone networks, traffic flow information based on these 89 IEs is not suitable. Flow information based on IP address or IP 90 prefix is much more mediculous. On the contrary, flow information 91 based on AS number is too coarse. BGP community [RFC1997], which 92 describes a group of routes sharing some common properties, is 93 preferablely used for fine granularity traffic engineering 94 [Community-TE] [RFC4384]. Unfortunately, [IANA-IPFIX] has no IE 95 defined for BGP community information, yet. 97 Flow information based on BGP community can be collected by a 98 mediator defined in [RFC6183]. Mediator is responsible for the 99 correlation between flow information and BGP community. However no 100 IEs are defined in [RFC6183] for exporting BGP community information 101 in IPFIX. Furthermore, to correlate the BGP community with the flow 102 information, mediator needs to learn BGP routes and lookup in the BGP 103 routing table to get the matching entry for the specific flow. 104 Neither BGP route learning nor routing table lookup is trivial for a 105 mediator. Mediator is mainly introduced to release the performance 106 requirement for the exporter [RFC5982]. In fact, to obtain the BGP 107 related IEs that have already been defined, such as 108 bgpSourceAsNumber, bgpDestinationAsNumber, bgpNextHopIPv4Address, 109 etc, exporter has to hold the up-to-date BGP routing table and look 110 up in the BGP routing table. The exporter can get the community 111 information in the same procedure. So, getting BGP community 112 information adds no more requirement for exporter. Some vendors have 113 implemented this feture in their exporters using private IEs. So, 114 exporter is RECOMMENDED to export the BGP community information in 115 IPFIX directly, other than the mediator. 117 This draft specifies an extension to the IPFIX information model 118 defined in [RFC7012] to export the BGP community information. Two 119 IEs, bgpSourceCommunityList and bgpDestinationCommunityList, are 120 introduced to complete this task. BgpSourceCommunityList is for the 121 source IP address, and bgpDestinationCommunityList is for the 122 destination IP address. bgpSourceCommunityList and 123 bgpDestinationCommunityList IEs are applicable for both IPv4 and IPv6 124 traffic. Both exporter and mediator can use these two IEs to export 125 BGP community informaiton in IPFIX. 127 2. Terminology 129 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 130 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 131 document are to be interpreted as described in [RFC2119]. 133 3. BGP Community Information Elements 135 In order to export BGP community information along with other flow 136 information defined by IPFIX, we need to introduce three new IEs. 137 One is bgpCommunity. It is used to identify that the value in this 138 IE is BGP community [RFC1997]. The other two are 139 bgpSourceCommunityList and bgpDestinationCommunityList. They both 140 are basicList [RFC6313] of bgpCommunity. bgpSourceCommunityList and 141 bgpDestinationCommunityList are used to export BGP community 142 information corresponding to a specific flow's source IP and 143 destination IP respectively. Flow information based on BGP community 144 can then be accumulated and analysed by the collector or other 145 applications. 147 The details of these three new introduced IEs are illustrated below, 148 including name, ID, type, semantics, description and units. 150 3.1. bgpCommunity 152 ---------------------------------------------------------------------- 153 | ElementID | to be assigned by IANA, 458 is suggested | 154 ---------------------------------------------------------------------- 155 | Name | bgpCommunity | 156 |--------------------------------------------------------------------- 157 | Data Type | unsigned32 | 158 |--------------------------------------------------------------------- 159 | Data Type Semantics | identifier | 160 ---------------------------------------------------------------------- 161 | Description | BGP community as defined in [RFC1997] | 162 ---------------------------------------------------------------------- 163 | Units | none | 164 |--------------------------------------------------------------------- 166 Figure 1: bgpCommunity 168 3.2. bgpSourceCommunityList 170 ---------------------------------------------------------------------- 171 | ElementID | to be assigned by IANA, 459 is suggested | 172 ---------------------------------------------------------------------- 173 | Name | bgpSourceCommunityList | 174 |--------------------------------------------------------------------- 175 | Data Type | basicList, as specifed in [RFC6313] | 176 |--------------------------------------------------------------------- 177 | Data Type Semantics | list | 178 ---------------------------------------------------------------------- 179 | Description | zero or more BGP communities corresponding | 180 | | with source IP address of a specific flow | 181 ---------------------------------------------------------------------- 182 | Units | none | 183 |--------------------------------------------------------------------- 185 Figure 2: bgpSourceCommunityList 187 3.3. bgpDestinationCommunityList 188 ---------------------------------------------------------------------- 189 | ElementID | to be assigned by IANA, 460 is suggested | 190 ---------------------------------------------------------------------- 191 | Name | bgpDestinationCommunityList | 192 |--------------------------------------------------------------------- 193 | Data Type | basicList, as specifed in [RFC6313] | 194 |--------------------------------------------------------------------- 195 | Data Type Semantics | list | 196 ---------------------------------------------------------------------- 197 | Description | zero or more BGP communities corresponding | 198 | |with destination IP address of a specific flow| 199 ---------------------------------------------------------------------- 200 | Units | none | 201 |--------------------------------------------------------------------- 203 Figure 3: bgpDestinationCommunityList 205 4. Security Considerations 207 This document only defines three new IEs for IPFIX. So, this 208 document itself does not directly introduce security issues. The 209 same security considerations as for the IPFIX Protocol Specification 210 [RFC7011] and Information Model [RFC7012] apply. 212 5. IANA Considerations 214 This draft specifies three new IPFIX IEs, bgpCommunity, 215 bgpSourceCommunityList and bgpDestinationCommunityList, to export BGP 216 community information along with other flow information. 218 The Element IDs for these three IEs are solicited to be assigned by 219 IANA. Number 458, 459 and 460 are suggested for bgpCommunity, 220 bgpSourceCommunityList and bgpDestinationCommunityList, respectively. 222 6. Acknowledgements 224 The authors would like to thank Benoit Claise and Paul Aitken for 225 discussion and suggestions to promote this document. 227 7. References 229 7.1. Normative References 231 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 232 Requirement Levels", BCP 14, RFC 2119, 233 DOI 10.17487/RFC2119, March 1997, 234 . 236 [RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates, 237 "Export of Structured Data in IP Flow Information Export 238 (IPFIX)", RFC 6313, DOI 10.17487/RFC6313, July 2011, 239 . 241 [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, 242 "Specification of the IP Flow Information Export (IPFIX) 243 Protocol for the Exchange of Flow Information", STD 77, 244 RFC 7011, DOI 10.17487/RFC7011, September 2013, 245 . 247 [RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model 248 for IP Flow Information Export (IPFIX)", RFC 7012, 249 DOI 10.17487/RFC7012, September 2013, 250 . 252 7.2. Informative References 254 [Community-TE] 255 Shao, W., Devienne, F., Iannone, L., and JL. Rougier, "On 256 the use of BGP communities for fine-grained inbound 257 traffic engineering", Computer Science 27392(1):476-487, 258 November 2015. 260 [IANA-IPFIX] 261 "IP Flow Information Export (IPFIX) Entities", 262 . 264 [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities 265 Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, 266 . 268 [RFC4384] Meyer, D., "BGP Communities for Data Collection", BCP 114, 269 RFC 4384, DOI 10.17487/RFC4384, February 2006, 270 . 272 [RFC5982] Kobayashi, A., Ed. and B. Claise, Ed., "IP Flow 273 Information Export (IPFIX) Mediation: Problem Statement", 274 RFC 5982, DOI 10.17487/RFC5982, August 2010, 275 . 277 [RFC6183] Kobayashi, A., Claise, B., Muenz, G., and K. Ishibashi, 278 "IP Flow Information Export (IPFIX) Mediation: Framework", 279 RFC 6183, DOI 10.17487/RFC6183, April 2011, 280 . 282 Appendix A. Application Example 284 In this section, we give an example to show the encoding format for 285 the three new introduced IEs. 287 Flow information including BGP communities is shown in the below 288 table. Suppose we want all the fields to be reported by IPFIX. 290 -------------------------------------------------------------------------- 291 |Source ip|Destination ip |Source BGP community|Destination BGP community| 292 -------------------------------------------------------------------------- 293 | 1.1.1.1 | 2.2.2.2 |1:1001,1:1002,8:1001| 2:1002,8:1001 | 294 -------------------------------------------------------------------------- 295 | 3.3.3.3 | 4.4.4.4 |3:1001,3:1002,8:1001| 4:1001,8:1001 | 296 -------------------------------------------------------------------------- 298 Figure 4: Flow information including BGP communities 300 A.1. Template Record 302 0 1 2 3 303 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 304 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 305 | SET ID = 2 | Length = 24 | 306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 307 | Template ID = 256 | Field Count = 4 | 308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 309 |0| SourceIPv4Address = 8 | Field length = 4 | 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 311 |0| DestinationIPv4Address = 12 | Field length = 4 | 312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 313 |0| bgpSourceCommunityList = 459| Field length = 0xFFFF | 314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 |0| bgpDestinationCommunityList | Field length = 0xFFFF | 316 | | = 460 | | 317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 319 Figure 5: Template Record Encoding Format 321 In this example, the Template ID is 256, which will be used in the 322 data record. The field length for bgpSourceCommunityList and 323 bgpDestinationCommunityList is 0xFFFF, which means the length of this 324 IE is variable, the actual length of this IE is indicated by the list 325 length field in the basic list format as per [RFC6313]. 327 A.2. Data Set 329 The data set is represented as follows: 331 0 1 2 3 332 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 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 334 | SET ID = 256 | Length = 92 | 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 336 | SourceIPv4Address = 1.1.1.1 | 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 | DestinationIPv4Address = 2.2.2.2 | 339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 340 | 255 | List length = 17 |semantic=allof | 341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 | bgpCommunity = 458 | Field Len = 4 | 343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 344 | BGP Source Community Value 1 = 1:1001 | 345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 346 | BGP Source Community Value 2 = 1:1002 | 347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 348 | BGP Source Community Value 3 = 8:1001 | 349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 350 | 255 | List length = 13 |semantic =allof| 351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 352 | bgpCommunity = 458 | Field Len = 4 | 353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 354 | BGP Destination Community Value 1 = 2:1002 | 355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 | BGP Destination Community Value 2 = 8:1001 | 357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 358 | SourceIPv4Address = 3.3.3.3 | 359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 360 | DestinationIPv4Address = 4.4.4.4 | 361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 362 | 255 | List length = 17 |semantic =allof| 363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 364 | bgpCommunity = 458 | Field Len = 4 | 365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 366 | BGP Source Community Value 1 = 3:1001 | 367 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 368 | BGP Source Community Value 2 = 3:1002 | 369 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 370 | BGP Source Community Value 3 = 8:1001 | 371 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 372 | 255 | List length = 13 |semantic =allof| 373 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 374 | bgpCommunity = 458 | Field Len = 4 | 375 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 376 | BGP Destination Community Value 1 = 4:1001 | 377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 378 | BGP Destination Community Value 2 = 8:1001 | 379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 381 Figure 6: Data Set Encoding Format 383 Authors' Addresses 385 Zhenqiang Li (editor) 386 China Mobile 387 32 Xuanwumen West Ave, Xicheng District 388 Beijing 100053 389 China 391 Email: lizhenqiang@chinamobile.com 393 Rong Gu (editor) 394 China Mobile 395 32 Xuanwumen West Ave, Xicheng District 396 Beijing 100053 397 China 399 Email: gurong_cmcc@outlook.com 401 Jie Dong 402 Huawei Technologies 403 Huawei Campus, No. 156 Beiqing Rd. 404 Beijing 100095 405 China 407 Email: jie.dong@huawei.com