idnits 2.17.1 draft-ietf-ipfix-data-link-layer-monitoring-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 9 instances of too long lines in the document, the longest one being 17 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 5, 2012) is 4220 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. 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 (-09) exists of draft-mahalingam-dutt-dcops-vxlan-02 -- Obsolete informational reference (is this intentional?): RFC 5101 (Obsoleted by RFC 7011) Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IP Flow Information Export S. Kashima 3 Internet-Draft NTT 4 Intended status: Standards Track A. Kobayashi 5 Expires: April 8, 2013 NTT East 6 P. Aitken 7 Cisco Systems, Inc. 8 October 5, 2012 10 Information Elements for Data Link Layer Traffic Measurement 11 draft-ietf-ipfix-data-link-layer-monitoring-01 13 Abstract 15 This document describes Information Elements related to data link 16 layer. They are used by the IP Flow Information Export (IPFIX) 17 protocol for encoding measured data link layer traffic information. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on April 8, 2013. 36 Copyright Notice 38 Copyright (c) 2012 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 This document may contain material from IETF Documents or IETF 52 Contributions published or made publicly available before November 53 10, 2008. The person(s) controlling the copyright in some of this 54 material may not have granted the IETF Trust the right to allow 55 modifications of such material outside the IETF Standards Process. 56 Without obtaining an adequate license from the person(s) controlling 57 the copyright in such materials, this document may not be modified 58 outside the IETF Standards Process, and derivative works of it may 59 not be created outside the IETF Standards Process, except to format 60 it for publication as an RFC or to translate it into languages other 61 than English. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 1.1. Conventions Used in This Document . . . . . . . . . . . . 4 67 2. Extended Ethernet Technology . . . . . . . . . . . . . . . . . 4 68 2.1. Wide-Area Ethernet Summary . . . . . . . . . . . . . . . . 4 69 2.2. Data Center Bridging Summary . . . . . . . . . . . . . . . 5 70 2.3. Multiple Path Ethernet Summary . . . . . . . . . . . . . . 5 71 2.4. VXLAN Summary . . . . . . . . . . . . . . . . . . . . . . 6 72 3. New Information Elements . . . . . . . . . . . . . . . . . . . 6 73 3.1. dataLinkFrameSize . . . . . . . . . . . . . . . . . . . . 7 74 3.2. dataLinkFrameSection . . . . . . . . . . . . . . . . . . . 8 75 3.3. dataLinkFrameType . . . . . . . . . . . . . . . . . . . . 8 76 3.4. sectionOffset . . . . . . . . . . . . . . . . . . . . . . 9 77 3.5. sectionObservedOctets . . . . . . . . . . . . . . . . . . 9 78 3.6. dot1qServiceInstanceTag . . . . . . . . . . . . . . . . . 10 79 3.7. dot1qServiceInstanceId . . . . . . . . . . . . . . . . . . 10 80 3.8. dot1qServiceInstancePriority . . . . . . . . . . . . . . . 11 81 3.9. dot1qCustomerDestinationMacAddress . . . . . . . . . . . . 11 82 3.10. dot1qCustomerSourceMacAddress . . . . . . . . . . . . . . 11 83 3.11. l2OctetDeltaCount . . . . . . . . . . . . . . . . . . . . 12 84 3.12. postMCastL2OctetDeltaCount . . . . . . . . . . . . . . . . 12 85 3.13. postL2OctetDeltaCount . . . . . . . . . . . . . . . . . . 13 86 3.14. minimumL2TotalLength . . . . . . . . . . . . . . . . . . . 13 87 3.15. maximumL2TotalLength . . . . . . . . . . . . . . . . . . . 14 88 3.16. l2octetTotalCount . . . . . . . . . . . . . . . . . . . . 14 89 3.17. droppedL2OctetDeltaCount . . . . . . . . . . . . . . . . . 14 90 3.18. droppedL2OctetTotalCount . . . . . . . . . . . . . . . . . 15 91 3.19. ignoredL2OctetTotalCount . . . . . . . . . . . . . . . . . 15 92 3.20. notSentL2OctetTotalCount . . . . . . . . . . . . . . . . . 16 93 3.21. postL2OctetTotalCount . . . . . . . . . . . . . . . . . . 16 94 3.22. postMCastL2OctetTotalCount . . . . . . . . . . . . . . . . 16 95 3.23. l2octetDeltaSumOfSquares . . . . . . . . . . . . . . . . . 17 96 3.24. l2octetTotalSumOfSquares . . . . . . . . . . . . . . . . . 17 97 4. Modification of Existing Information Elements Related to 98 Packet Section . . . . . . . . . . . . . . . . . . . . . . . . 18 99 4.1. ipHeaderPacketSection . . . . . . . . . . . . . . . . . . 18 100 4.2. ipPayloadPacketSection . . . . . . . . . . . . . . . . . . 18 101 4.3. mplsLabelStackSection . . . . . . . . . . . . . . . . . . 18 102 4.4. mplsPayloadPacketSection . . . . . . . . . . . . . . . . . 19 103 5. Modification of Existing Information Elements Related to 104 VLAN Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 105 5.1. dot1qVlanId . . . . . . . . . . . . . . . . . . . . . . . 19 106 5.2. dot1qPriority . . . . . . . . . . . . . . . . . . . . . . 20 107 5.3. dot1qCustomerVlanId . . . . . . . . . . . . . . . . . . . 20 108 5.4. dot1qCustomerPriority . . . . . . . . . . . . . . . . . . 21 109 6. The relationship between Ethernet header fields and 110 Information Elements . . . . . . . . . . . . . . . . . . . . . 22 111 7. Security Considerations . . . . . . . . . . . . . . . . . . . 23 112 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 113 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 114 9.1. Normative References . . . . . . . . . . . . . . . . . . . 23 115 9.2. Informative References . . . . . . . . . . . . . . . . . . 23 116 Appendix A. Frame Formats in Wide-Area Ethernet Network . . . . . 26 117 Appendix B. Frame Formats in Data Center Network . . . . . . . . 30 118 Appendix C. Template Formats Example . . . . . . . . . . . . . . 33 119 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 121 1. Introduction 123 Ethernet [IEEE802.1D] and VLAN (Virtual LAN) [IEEE802.1Q-2005] 124 technologies used to be used only in Local Area Networks. Recently, 125 they have been used in Wide Area Networks, e.g., L2-VPN services. 126 Accordingly, the IEEE802.1Q standard has been enhanced to IEEE802.1ad 127 [IEEE802.1ad-2005] and IEEE802.1ah [IEEE802.1ah-2008]. And, Ethernet 128 in data center also has been enhanced for server virtualization and 129 I/O consolidation. 131 While these innovations provide flexibility, scalability, and 132 mobility to an existing network architecture, it increases the 133 complexity of traffic measurement due to the existence of various 134 Ethernet header formats. To cope with this, a more sophisticated 135 method is required. 137 IPFIX/PSAMP helps to resolve these problems. However, the PSAMP 138 Information Model [RFC5477] and the IPFIX Information Model [RFC5101] 139 are not yet enough for Information Elements related to data link 140 layer, e.g., Ethernet header forms. This document describes the 141 Information Elements related to data link layers that enable a more 142 sophisticated traffic measurement method. 144 1.1. Conventions Used in This Document 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 RFC 2119 [RFC2119]. 150 2. Extended Ethernet Technology 152 2.1. Wide-Area Ethernet Summary 154 Provider Bridge [IEEE802.1ad-2005] and Provider Backbone Bridge 155 [IEEE802.1ah-2008], which are standards for the Wide-Area Ethernet, 156 are described below. 158 o In Provider Bridge [IEEE802.1ad-2005], there are two VLAN IDs: 159 Service VLAN Identifier (S-VID) and Customer VLAN Identifier 160 (C-VID). S-VID is assigned to an Ethernet frame by a service 161 provider, while C-VID is independently assigned to an Ethernet 162 frame by a customer. Frame switching in a service provider 163 network is based on only S-VID. 164 o In Provider Backbone Bridge [IEEE802.1ah-2008], new Ethernet 165 fields, such as Backbone VLAN Identifier (B-VID) and Backbone 166 Service Instance Identifier (I-SID), are introduced to overcome 167 the limitations on the VLAN identifier space on IEEE802.1ad 169 [IEEE802.1ad-2005] and to isolate the service provider and 170 customer identifier spaces. Frame switching is based on a 12-bit 171 B-VID, and customer identification is based on a 24-bit I-SID. A 172 flexible network design has become possible because network 173 management is separated from customer management. Other Ethernet 174 fields that indicate quality of service (QoS) class are B-PCP, 175 B-DEI, I-PCP, and I-DEI. 177 Provider Backbone Bridge enables a wide-area Ethernet service to be 178 improved from a flat network to a hierarchical network co-existing 179 Provider Bridge and Provider Backbone Bridge. 181 Frame formats used in Wide-Area Ethernet are shown in Appendix A. 183 2.2. Data Center Bridging Summary 185 In data center networks, Ethernet needs to be enhanced to provide the 186 flexibility, mobility for server virtualization, and I/O 187 consolidation. In IEEE802.1 Data Center Bridging Task Group, several 188 Ethernet header formats are proposed to enable a simplifying networks 189 and server managements. 191 The one of the enhanced methods is Bridge Port Extension 192 [IEEE802.1BR], which brings a traffic exchange point to upper 193 bridges. Bridge Port Extension introduces a Ethernet format named 194 Extension Tag (E-TAG) in addition to existing Service VLAN Tag 195 (S-TAG) and Customer VLAN Tag (C-TAG) to move the policy enhancement 196 to upper bridges in data center network. On the other hand, the 197 complexity for traffic measurement would be increased, because 198 multiple Ethernet header formats as shown in Appendix B co-exist in 199 the same network. 201 2.3. Multiple Path Ethernet Summary 203 Inside data center networks, Ethernet need to be enhanced to support 204 multiple path for effective utilization of bandwidth. Existing 205 Ethernet does not support multiple path because it is based on STP 206 (Spanning Tree Protocol) [IEEE802.1D]. 208 Two solutions for multiple path Ethernet are discussed for 209 standardization. One is Shortest Path Bridging [IEEE802.1aq] in IEEE 210 802, the other is TRILL (Transparent Interconnection of Lots of 211 Links) [RFC6325] in IETF. Both solutions realize multiple path with 212 IS-IS [ISO_IEC.10589_2002] and Layer 2 over Layer 2 encapsulation. 213 Shortest Path Bridging uses IEEE802.1ah [IEEE802.1ah-2008] header as 214 an encapsulation technology and TRILL uses an unique header as shown 215 in Section 3 of [RFC6325]. 217 In multiple path Ethernet network, a traffic measurement based on MAC 218 address and VLAN Tag is more important than single path Ethernet 219 network in which traffic measurement is based on only VLAN Tag. 221 2.4. VXLAN Summary 223 Inside and between data center networks, the existing Ethernet and 224 VLAN technologies have two problems. One is that 12 bit of VLAN ID 225 does not have enough length for identifying a lot of tenants. The 226 other is that it is difficult to place same VLAN in multiple data 227 centers. 229 The solution for the problems is VXLAN 230 [I-D.mahalingam-dutt-dcops-vxlan]. VXLAN has 24 bit length of 231 identifier named VXLAN Segment ID/VXLAN Network Identifier (VNI) and 232 uses Layer 2 over Layer 3 encapsulation with the frame format as show 233 in Section 5 of [I-D.mahalingam-dutt-dcops-vxlan]. 235 In VXLAN networks, a traffic measurement based on multiple kinds of 236 IP/MAC address and new VXLAN header is more important than existing 237 Ethernet network in which traffic measurement is based on only VLAN 238 Tag. 240 3. New Information Elements 242 The following Information Elements whose ElementId are from 312 to 243 TBD03 are necessary for enabling the IPFIX/PSAMP traffic measurement 244 for data link layer, which is not limited to Ethernet because the 245 method can be applied to other data link protocols as well. 247 The following Information Elements whose ElementId are from TBD04 to 248 TBD08 are necessary for enabling the IPFIX/PSAMP traffic measurement 249 for IEEE 802.1ah. 251 The following Information Elements whose ElementId are TBD09 from to 252 TBD22 are octet counter or packet length for layer 2, and are 253 necessary for enabling the IPFIX/PSAMP traffic measurement for data 254 link layer. 256 Note that 312 and 315 are proposed IDs, subject to approval by IANA. 258 +-----+------------------------------------+ 259 | ID | Name | 260 +-----+------------------------------------+ 261 | 312 | dataLinkFrameSize | 262 | 315 | dataLinkFrameSection | 263 |TBD01| dataLinkFrameType | 264 |TBD02| sectionOffset | 265 |TBD03| sectionObservedOctets | 266 |TBD04| dot1qServiceInstanceTag | 267 |TBD05| dot1qServiceInstanceId | 268 |TBD06| dot1qServiceInstancePriority | 269 |TBD07| dot1qCustomerDestinationMacAddress | 270 |TBD08| dot1qCustomerSourceMacAddress | 271 |TBD09| l2octetDeltaCount | 272 |TBD10| postMCastL2OctetDeltaCount | 273 |TBD11| postL2OctetDeltaCount | 274 |TBD12| minimumL2TotalLength | 275 |TBD13| maximumL2TotalLength | 276 |TBD14| l2octetTotalCount | 277 |TBD15| droppedL2OctetDeltaCount | 278 |TBD16| droppedL2OctetTotalCount | 279 |TBD17| ignoredL2OctetTotalCount | 280 |TBD18| notSentL2OctetTotalCount | 281 |TBD19| postL2OctetTotalCount | 282 |TBD20| postMCastL2OctetTotalCount | 283 |TBD21| l2octetDeltaSumOfSquares | 284 |TBD22| l2octetTotalSumOfSquares | 285 +-----+------------------------------------+ 287 Table 1: New Information Elements 289 3.1. dataLinkFrameSize 291 Description: 293 This Information Element specifies the length of the selected data 294 link frame. 296 The data link layer is defined in [ISO_IEC.7498-1_1994]. 298 Abstract Data Type: unsigned16 300 Data Type Semantics: quantity 302 ElementId: 312 304 Status: current 306 3.2. dataLinkFrameSection 308 Description: 310 This Information Element carries n octets from the data link frame 311 of a selected frame, starting sectionOffset octets into the frame. 313 The sectionObservedOctets expresses how much data was observed, 314 while the remainder is padding. 316 When the sectionObservedOctets field corresponding to this 317 Information Element exists, this Information Element MAY have a 318 fixed length and MAY be padded, or MAY have a variable length. 320 When the sectionObservedOctets field corresponding to this 321 Information Element does not exist, this Information Element 322 SHOULD have a variable length and MUST NOT be padded. In this 323 case, the size of the exported section may be constrained due to 324 limitations in the IPFIX protocol. 326 Further Information Elements, i.e., dataLinkFrameType and 327 dataLinkFrameSize are needed to specify the data link type and the 328 size of the data link frame of this Information Element. A set of 329 these Information Elements MAY be contained in a structured data 330 type, as expressed in [RFC6313]. Or a set of these Information 331 Elements MAY be contained in one Flow Record as shown in Appendix 332 C. 334 The data link layer is defined in [ISO_IEC.7498-1_1994]. 336 Abstract Data Type: octetArray 338 ElementId: 315 340 Status: current 342 3.3. dataLinkFrameType 344 Description: 346 This Information Element specifies the type of the selected data 347 link frame. 349 The following data link types are defined here. 351 - 0x01 ETHERNET 352 Further values may be assigned by IANA. 354 The data link layer is defined in [ISO_IEC.7498-1_1994]. 356 Abstract Data Type: unsigned16 358 Data Type Semantics: identifier 360 ElementId: TBD01 362 Status: current 364 3.4. sectionOffset 366 Description: 368 This Information Element specifies the offset of the packet 369 section (e.g., dataLinkFrameSection, ipHeaderPacketSection, 370 ipPayloadPacketSection, mplsLabelStackSection and 371 mplsPayloadPacketSection). If this Information Element is 372 omitted, it defaults to zero (ie, no offset). 373 If multiple sectionOffset IEs are specified within a single 374 Template, then they apply to the packet section IEs in order. ie, 375 the first sectionOffset applies to the first packet section, etc. 376 Note that the "closest" sectionOffset and packet section IEs 377 within a given Template are not necessarily related. If there are 378 less sectionOffset IEs than packet section IEs, then subsequent 379 packet section IEs have no offset. If there are more 380 sectionOffset IEs than the number of packet section IEs, then the 381 additional sectionOffset IEs are meaningless. 383 Abstract Data Type: unsigned16 385 Data Type Semantics: quantity 387 ElementId: TBD02 389 Status: current 391 3.5. sectionObservedOctets 393 Description: 395 This Information Element specifies the observed length of the 396 packet section (e.g., dataLinkFrameSection, ipHeaderPacketSection, 397 ipPayloadPacketSection, mplsLabelStackSection and 398 mplsPayloadPacketSection) when padding is used. 400 The packet section may be of a fixed size larger than the 401 sectionObservedOctets. In this case, octets in the packet section 402 beyond the sectionObservedOctets MUST follow the [RFC5101] rules 403 for padding (ie, be composed of zero (0) valued octets). 405 Abstract Data Type: unsigned16 407 Data Type Semantics: quantity 409 ElementId: TBD03 411 Status: current 413 3.6. dot1qServiceInstanceTag 415 Description: 417 This Information Element, which may have 16 octets length, 418 represents the Backbone Service Instance Tag (I-TAG) Tag Control 419 Information (TCI) field of an Ethernet frame as described in 420 [IEEE802.1ah-2008]. It encodes the Backbone Service Instance 421 Priority Code Point (I-PCP), Drop Eligible Indicator (I-DEI), Use 422 Customer Addresses (UCA), Backbone Service Instance Identifier 423 (I-SID), Encapsulated Customer Destination Address (C-DA), 424 Encapsulated Customer Source Address (C-SA) and reserved fields. 426 Abstract Data Type: octetArray 428 Data Type Semantics: identifier 430 ElementId: TBD04 432 Status: current 434 3.7. dot1qServiceInstanceId 436 Description: 438 The value of the 24-bit Backbone Service Instance Identifier 439 (I-SID) portion of the Backbone Service Instance Tag (I-TAG) Tag 440 Control Information (TCI) field of an Ethernet frame as described 441 in section 9.8 of [IEEE802.1ah-2008]. The structure and semantics 442 within the Tag Control Information field are defined in 443 IEEE802.1ah. 445 Abstract Data Type: unsigned32 446 Data Type Semantics: identifier 448 ElementId: TBD05 450 Status: current 452 3.8. dot1qServiceInstancePriority 454 Description: 456 The value of the 3-bit Backbone Service Instance Priority Code 457 Point (I-PCP) portion of the Backbone Service Instance Tag (I-TAG) 458 Tag Control Information (TCI) field of an Ethernet frame as 459 described in section 9.8 of [IEEE802.1ah-2008]. The structure and 460 semantics within the Tag Control Information field are defined in 461 IEEE802.1ah. 463 Abstract Data Type: unsigned8 465 Data Type Semantics: identifier 467 ElementId: TBD06 469 Status: current 471 3.9. dot1qCustomerDestinationMacAddress 473 Description: 475 The value of the Encapsulated Customer Destination Address (C-DA) 476 portion of the Backbone Service Instance Tag (I-TAG) Tag Control 477 Information (TCI) field of an Ethernet frame as described in 478 section 9.8 of [IEEE802.1ah-2008]. The structure and semantics 479 within the Tag Control Information field are defined in 480 IEEE802.1ah. 482 Abstract Data Type: macAddress 484 Data Type Semantics: identifier 486 ElementId: TBD07 488 Status: current 490 3.10. dot1qCustomerSourceMacAddress 492 Description: 494 The value of the Encapsulated Customer Source Address (C-SA) 495 portion of the Backbone Service Instance Tag (I-TAG) Tag Control 496 Information (TCI) field of an Ethernet frame as described in 497 section 9.8 of [IEEE802.1ah-2008]. The structure and semantics 498 within the Tag Control Information field are defined in 499 IEEE802.1ah. 501 Abstract Data Type: macAddress 503 Data Type Semantics: identifier 505 ElementId: TBD08 507 Status: current 509 3.11. l2OctetDeltaCount 511 Description: 513 The number of layer 2 octets since the previous report (if any) in 514 incoming packets for this Flow at the Observation Point. The 515 number of octets includes layer 2 header(s) and layer 2 payload. 516 # memo: layer 2 version of octetDeltaCount (field #1) 518 Abstract Data Type: unsigned64 520 Data Type Semantics: deltaCounter 522 ElementId: TBD09 524 Status: current 526 Units: octets 528 3.12. postMCastL2OctetDeltaCount 530 Description: 532 The number of layer 2 octets since the previous report (if any) in 533 outgoing multicast packets sent for packets of this Flow by a 534 multicast daemon within the Observation Domain. This property 535 cannot necessarily be observed at the Observation Point, but may 536 be retrieved by other means. The number of octets includes layer 537 2 header(s) and layer 2 payload. 538 # memo: layer 2 version of postMCastOctetDeltaCount (field #20) 540 Abstract Data Type: unsigned64 541 Data Type Semantics: deltaCounter 543 ElementId: TBD10 545 Status: current 547 Units: octets 549 3.13. postL2OctetDeltaCount 551 Description: 553 The definition of this Information Element is identical to the 554 definition of Information Element 'l2OctetDeltaCount', except that 555 it reports a potentially modified value caused by a middlebox 556 function after the packet passed the Observation Point. 557 # memo: layer 2 version of postOctetDeltaCount (field #23) 559 Abstract Data Type: unsigned64 561 Data Type Semantics: deltaCounter 563 ElementId: TBD11 565 Status: current 567 Units: octets 569 3.14. minimumL2TotalLength 571 Description: 573 Layer 2 length of the smallest packet observed for this Flow. The 574 packet length includes the layer 2 header(s) length and the layer 575 2 payload length. 576 # memo: layer 2 version of minimumIpTotalLength (field #25) 578 Abstract Data Type: unsigned64 580 ElementId: TBD12 582 Status: current 584 Units: octets 586 3.15. maximumL2TotalLength 588 Description: 590 Layer 2 length of the largest packet observed for this Flow. The 591 packet length includes the layer 2 header(s) length and the layer 592 2 payload length. 593 # memo: layer 2 version of maximumIpTotalLength (field #26) 595 Abstract Data Type: unsigned64 597 ElementId: TBD13 599 Status: current 601 Units: octets 603 3.16. l2octetTotalCount 605 Description: 607 The total number of layer 2 octets in incoming packets for this 608 Flow at the Observation Point since the Metering Process 609 (re-)initialization for this Observation Point. The number of 610 octets includes layer 2 header(s) and layer 2 payload. 611 # memo: layer 2 version of octetTotalCount (field #85) 613 Abstract Data Type: unsigned64 615 Data Type Semantics: totalCounter 617 ElementId: TBD14 619 Status: current 621 Units: octets 623 3.17. droppedL2OctetDeltaCount 625 Description: 627 The number of layer 2 octets since the previous report (if any) in 628 packets of this Flow dropped by packet treatment. The number of 629 octets includes layer 2 header(s) and layer 2payload. 630 # memo: layer 2 version of droppedOctetDeltaCount (field #132) 632 Abstract Data Type: unsigned64 633 Data Type Semantics: deltaCounter 635 ElementId: TBD15 637 Status: current 639 Units: octets 641 3.18. droppedL2OctetTotalCount 643 Description: 645 The number of layer 2 octets since the previous report (if any) in 646 packets of this Flow dropped by packet treatment. The number of 647 octets includes layer 2 header(s) and layer 2 payload. 648 # memo: layer 2 version of droppedOctetTotalCount (field #134) 650 Abstract Data Type: unsigned64 652 Data Type Semantics: totalCounter 654 ElementId: TBD16 656 Status: current 658 Units: octets 660 3.19. ignoredL2OctetTotalCount 662 Description: 664 The total number of octets in observed layer 2 packets (including 665 the layer 2 header) that the Metering Process did not process 666 since the (re-)initialization of the Metering Process. 667 # memo: layer 2 version of ignoredOctetTotalCount (field #165) 669 Abstract Data Type: unsigned64 671 Data Type Semantics: totalCounter 673 ElementId: TBD17 675 Status: current 677 Units: octets 679 3.20. notSentL2OctetTotalCount 681 Description: 683 The total number of octets in observed layer 2 packets (including 684 the layer 2 header) that the Metering Process did not process 685 since the (re-)initialization of the Metering Process. 686 # memo: layer 2 version of notSentOctetTotalCount (field #168) 688 Abstract Data Type: unsigned64 690 Data Type Semantics: totalCounter 692 ElementId: TBD18 694 Status: current 696 Units: octets 698 3.21. postL2OctetTotalCount 700 Description: 702 The definition of this Information Element is identical to the 703 definition of Information Element 'l2OctetTotalCount', except that 704 it reports a potentially modified value caused by a middlebox 705 function after the packet passed the Observation Point. 706 # memo: layer 2 version of postOctetTotalCount (field #171) 708 Abstract Data Type: unsigned64 710 Data Type Semantics: totalCounter 712 ElementId: TBD19 714 Status: current 716 Units: octets 718 3.22. postMCastL2OctetTotalCount 720 Description: 722 The total number of layer 2 octets in outgoing multicast packets 723 sent for packets of this Flow by a multicast daemon in the 724 Observation Domain since the Metering Process (re-)initialization. 725 This property cannot necessarily be observed at the Observation 726 Point, but may be retrieved by other means. The number of octets 727 includes layer 2 header(s) and layer 2 payload. 728 # memo: layer 2 version of postMCastOctetTotalCount (field #175) 730 Abstract Data Type: unsigned64 732 Data Type Semantics: totalCounter 734 ElementId: TBD20 736 Status: current 738 Units: octets 740 3.23. l2octetDeltaSumOfSquares 742 Description: 744 The sum of the squared numbers of layer 2 octets per incoming 745 packet since the previous report (if any) for this Flow at the 746 Observation Point. The number of octets includes layer 2 747 header(s) and layer 2 payload. 748 # memo: layer 2 version of octetDeltaSumOfSquares (field #198) 750 Abstract Data Type: unsigned64 752 Data Type Semantics: deltaCounter 754 ElementId: TBD21 756 Status: current 758 Units: octets 760 3.24. l2octetTotalSumOfSquares 762 Description: 764 The total sum of the squared numbers of layer 2 octets in incoming 765 packets for this Flow at the Observation Point since the Metering 766 Process (re-)initialization for this Observation Point. The 767 number of octets includes layer 2 header(s) and layer 2 payload. 768 # memo: layer 2 version of octetTotalSumOfSquares (field #199) 770 Abstract Data Type: unsigned64 772 Data Type Semantics: totalCounter 774 ElementId: TBD22 775 Status: current 777 Units: octets 779 4. Modification of Existing Information Elements Related to Packet 780 Section 782 --- This is open issue. --- 784 New Information Elements related to packet section (ie, sectionOffset 785 and sectionObservedOctets) can be applied to not only 786 dataLinkFrameSection but also all kinds of packet section. In this 787 case, existing Information Elements Description should be modified as 788 follows: 790 4.1. ipHeaderPacketSection 792 Description: 794 TBD 796 Abstract Data Type: octetArray 798 ElementId: 313 800 Status: current 802 4.2. ipPayloadPacketSection 804 Description: 806 TBD 808 Abstract Data Type: octetArray 810 ElementId: 314 812 Status: current 814 4.3. mplsLabelStackSection 816 Description: 818 TBD 820 Abstract Data Type: octetArray 821 ElementId: 316 823 Status: current 825 4.4. mplsPayloadPacketSection 827 Description: 829 TBD 831 Abstract Data Type: octetArray 833 ElementId: 317 835 Status: current 837 5. Modification of Existing Information Elements Related to VLAN Tag 839 Information Elements related to Backbone Service Instance Tag (I-TAG) 840 and Backbone VLAN Tag (B-TAG) are required in order to monitor 841 IEEE802.1ah traffic with IPFIX/PSAMP. New Information Elements 842 related to I-TAG are added in section 3 because I-TAG has different 843 structure and semantics from Service VLAN Tag (S-TAG) and Customer 844 VLAN Tag (C-TAG). On the other hand, Information Elements related to 845 B-TAG reuse existing Information Elements related to C-TAG and S-TAG 846 because B-TAG has same structure and semantics with C-TAG and S-TAG, 847 Though they reuse existing Information Elements, it required to 848 modify existing Descriptions and Reference as follows: 850 5.1. dot1qVlanId 852 Description: 854 The value of the 12-bit VLAN Identifier portion of the Tag Control 855 Information field of an Ethernet frame as described in section 856 3.5.5 of [IEEE802.3-2005]. The structure and semantics within the 857 Tag Control Information field are defined in IEEE P802.1Q. In case 858 of a QinQ frame it represents the outer tag's VLAN identifier, in 859 case of an IEEE 802.1ad frame it represents the Service VLAN 860 identifier in the S-TAG Tag Control Information (TCI) field as 861 described in [IEEE802.1ad-2005] and in case of an IEEE 802.1ah 862 frame it represents the Backbone VLAN identifier in the B-TAG Tag 863 Control Information (TCI) field as described in 864 [IEEE802.1ah-2008]. 866 Abstract Data Type: unsigned16 867 Data Type Semantics: identifier 869 ElementId: 243 871 Status: current 873 Reference: 875 (1) [IEEE802.3-2005] 876 (2) [IEEE802.1ad-2005] 877 (3) [IEEE802.1ah-2008] 879 5.2. dot1qPriority 881 Description: 883 The value of the 3-bit User Priority portion of the Tag Control 884 Information field of an Ethernet frame as described in section 885 3.5.5 of [IEEE802.3-2005]. The structure and semantics within the 886 Tag Control Information field are defined in IEEE P802.1Q. In case 887 of a QinQ frame it represents the outer tag's 3-bit Class of 888 Service (CoS) identifier, in case of an IEEE 802.1ad frame it 889 represents the 3-bit Priority Code Point (PCP) portion of the 890 S-TAG Tag Control Information (TCI) field as described in 891 [IEEE802.1ad-2005] and in case of an IEEE 802.1ah frame it 892 represents the 3-bit Priority Code Point (PCP) portion of the 893 B-TAG Tag Control Information (TCI) field as described in 894 [IEEE802.1ah-2008]. 896 Abstract Data Type: unsigned8 898 Data Type Semantics: identifier 900 ElementId: 244 902 Status: current 904 Reference: 906 (1) [IEEE802.3-2005] 907 (2) [IEEE802.1ad-2005] 908 (3) [IEEE802.1ah-2008] 910 5.3. dot1qCustomerVlanId 912 Description: 914 In case of a QinQ frame it represents the inner tag's (*) VLAN 915 identifier, in case of an IEEE 802.1ad frame it represents the 916 Customer VLAN identifier in the C-TAG Tag Control Information 917 (TCI) field as described in [IEEE802.1ad-2005] and in case of an 918 IEEE 802.1ah frame it represents the Customer VLAN identifier in 919 the C-TAG Tag Control Information (TCI) field in encapsulated IEEE 920 802.1ad or IEEE 802.1Q frame as described in [IEEE802.1ah-2008]. 921 (*) Note: the 802.1Q tag directly following the outer one. 923 Abstract Data Type: unsigned16 925 Data Type Semantics: identifier 927 ElementId: 245 929 Status: current 931 Reference: 933 (1) [IEEE802.1ad-2005] 934 (2) [IEEE802.1Q-2005] 935 (3) [IEEE802.1ah-2008] 937 5.4. dot1qCustomerPriority 939 Description: 941 In case of a QinQ frame it represents the inner tag's (*) Class of 942 Service (CoS) identifier, in case of an IEEE 802.1ad frame it 943 represents the 3-bit Priority Code Point (PCP) portion of the 944 C-TAG Tag Control Information (TCI) field as described in 945 [IEEE802.1ad-2005] and in case of an IEEE 802.1ah frame it 946 represents the 3-bit Priority Code Point (PCP) portion of the 947 C-TAG Tag Control Information (TCI) field in encapsulated IEEE 948 802.1ad or IEEE 802.1Q frame as described in [IEEE802.1ad-2005]. 949 (*) Note: the 802.1Q tag directly following the outer one. 951 Abstract Data Type: unsigned8 953 Data Type Semantics: identifier 955 ElementId: 246 957 Status: current 959 Reference: 961 (1) [IEEE802.1ad-2005] 962 (2) [IEEE802.1Q-2005] 963 (3) [IEEE802.1ah-2008] 965 6. The relationship between Ethernet header fields and Information 966 Elements 968 The following figures shows summary of various Ethernet header fields 969 and the Informational Elements which would be used to represent each 970 of the fields. 972 <----6----><----6----><----4----><------2------> 973 +----------+----------+----------+--------------+ 974 + + + + + 975 + C-DA + C-SA + C-TAG + Length/Type + 976 + a + b + c + d + 977 +----------+----------+----------+--------------+ 979 a.(Existing Information Element) destinationMacAddress 80 980 b.(Existing Information Element) sourceMacAddress 56 981 c.(Existing Information Elements) dot1qVlanId 243, dot1qPriority 244 982 d.(Existing Information Element) ethernetType 256 984 Figure 1: IEEE 802.1Q header fields 986 <----6----><----6----><----4----><----4----><------2------> 987 +----------+----------+----------+----------+--------------+ 988 + + + + + + 989 + C-DA + C-SA + S-TAG + C-TAG + Length/Type + 990 + a + b + c + d + e + 991 +----------+----------+----------+----------+--------------+ 993 a.(Existing Information Element) destinationMacAddress 80 994 b.(Existing Information Element) sourceMacAddress 56 995 c.(Existing Information Elements) dot1qVlanId 243, dot1qPriority 244 996 d.(Existing Information Elements) dot1qCustomerVlanId 245, dot1qCustomerPriority 246 997 e.(Existing Information Element) ethernetType 256 999 Figure 2: IEEE 802.1ad header fields 1001 <----6----><----6----><----4----><------18------><----4----><------2------> 1002 +----------+----------+----------+---------------+----------+--------------+ 1003 + + + + + + + 1004 + B-DA + B-SA + B-TAG + I-TAG + C-TAG + Length/Type + 1005 + a + b + c + d + e + f + 1006 +----------+----------+----------+---------------+----------+--------------+ 1008 a.(Existing Information Element) destinationMacAddress 80 1009 b.(Existing Information Element) sourceMacAddress 56 1010 c.(Existing Information Elements) dot1qVlanId 243, dot1qPriority 244 1011 d.(New Information Elements) defined in section 3.6, 3.7, 3.8, 3.9 and 3.10 of this draft 1012 e.(Existing Information Elements) dot1qCustomerVlanId 245, dot1qCustomerPriority 246 1013 f.(Existing Information Element) ethernetType 256 1015 Figure 3: IEEE 802.1ah header fields 1017 7. Security Considerations 1019 The recommendations in this document do not introduce any additional 1020 security issues to those already mentioned in [RFC5101] and 1021 [RFC5477]. 1023 8. IANA Considerations 1025 This document requests that the Information Element IDs are allocated 1026 as shown in section 3 1028 In addition, the dataLinkFrameType Information Element requires the 1029 creation of new IANA registries. 1031 And this document requests that the existing Information Element 1032 Description are modified as shown in section 4 and 5 1034 9. References 1036 9.1. Normative References 1038 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1039 Requirement Levels", BCP 14, RFC 2119, March 1997. 1041 9.2. Informative References 1043 [I-D.mahalingam-dutt-dcops-vxlan] 1044 Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, 1045 L., Sridhar, T., Bursell, M., and C. Wright, "VXLAN: A 1046 Framework for Overlaying Virtualized Layer 2 Networks over 1047 Layer 3 Networks", draft-mahalingam-dutt-dcops-vxlan-02 1048 (work in progress), August 2012. 1050 [IEEE802.1BR] 1051 IEEE Computer Society, "Draft Standards for Local and 1052 Metropolitan Area Networks: Virtual Bridged Local Area 1053 Networks Amendment: Bridge Port Extension", IEEE 1054 Std P802.1BR/D1.1, February 2011. 1056 [IEEE802.1D] 1057 IEEE Computer Society, "IEEE Standards for Local and 1058 Metropolitan Area Networks: Media Access Control (MAC) 1059 Bridges", IEEE Std 802.1D-2004, June 2004. 1061 [IEEE802.1Q-2005] 1062 IEEE Computer Society, "IEEE Standards for Local and 1063 Metropolitan Area Networks: Virtual Bridged Local Area 1064 Networks", IEEE Std 802.1Q-2005, May 2006. 1066 [IEEE802.1ad-2005] 1067 IEEE Computer Society, "IEEE Standards for Local and 1068 Metropolitan Area Networks: Virtual Bridged Local Area 1069 Networks Amendment 4: Provider Bridges", IEEE Std 802.1ad- 1070 2005, May 2006. 1072 [IEEE802.1ah-2008] 1073 IEEE Computer Society, "IEEE Standards for Local and 1074 Metropolitan Area Networks: Virtual Bridged Local Area 1075 Networks Amendment 7: Provider Backbone Bridges", IEEE 1076 Std 802.1ah-2008, August 2008. 1078 [IEEE802.1aq] 1079 IEEE Computer Society, "Draft Standards for Local and 1080 Metropolitan Area Networks: Virtual Bridged Local Area 1081 Networks Amendment: Shortest Path Bridging", IEEE 1082 Std P802.1aq/D3.6, February 2011. 1084 [IEEE802.3-2005] 1085 IEEE Computer Society, "IEEE Standard for Information 1086 Technology - Telecommunications and Information Exchange 1087 Between Systems - Local and Metropolitan Area Networks - 1088 Specific Requirements Part 3: Carrier Sense Multiple 1089 Access with Collision Detection (CSMA/CD) Access Method 1090 and Physical Layer Specifications", IEEE Std 802.3-2005, 1091 December 2005. 1093 [ISO_IEC.10589_2002] 1094 International Organization for Standardization, 1095 "Information technology -- Telecommunications and 1096 information exchange between systems -- Intermediate 1097 System to Intermediate System intra-domain routing 1098 information exchange protocol for use in conjunction with 1099 the protocol for providing the connectionless-mode network 1100 service (ISO 8473)", ISO Standard 10589:2002, 1101 November 2002. 1103 [ISO_IEC.7498-1_1994] 1104 International Organization for Standardization, 1105 "Information technology -- Open Systems Interconnection -- 1106 Basic Reference Model: The Basic Mode", ISO Standard 7498- 1107 1:1994, June 1996. 1109 [RFC5101] Claise, B., "Specification of the IP Flow Information 1110 Export (IPFIX) Protocol for the Exchange of IP Traffic 1111 Flow Information", RFC 5101, January 2008. 1113 [RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G. 1114 Carle, "Information Model for Packet Sampling Exports", 1115 RFC 5477, March 2009. 1117 [RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates, 1118 "Export of Structured Data in IP Flow Information Export 1119 (IPFIX)", RFC 6313, July 2011. 1121 [RFC6325] Perlman, R., Eastlake, D., Dutt, D., Gai, S., and A. 1122 Ghanwani, "Routing Bridges (RBridges): Base Protocol 1123 Specification", RFC 6325, July 2011. 1125 Appendix A. Frame Formats in Wide-Area Ethernet Network 1127 0 1 2 3 1128 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 1129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1130 | C-DA | 1131 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1132 | | | 1133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1134 | C-SA | 1135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1136 | Length/Type | | 1137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1138 | | 1139 ~ Customer Data ~ 1140 ~ ~ 1141 | | 1142 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1144 Figure A-1: IEEE802.1D Frame Format in Customer Bridged Network 1146 0 1 2 3 1147 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 1148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1149 | C-DA | 1150 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1151 | | | 1152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1153 | C-SA | 1154 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1155 | C-TAG TCI=0x8100 |C-PCP|C| C-VID | 1156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1157 | Length/Type | | 1158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1159 | | 1160 ~ Customer Data ~ 1161 ~ ~ 1162 | | 1163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1165 Figure A-2: IEEE802.1Q Frame Format in Customer Bridged Network 1167 0 1 2 3 1168 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 1169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1170 | C-DA | 1171 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1172 | | | 1173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1174 | C-SA | 1175 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1176 | S-TAG TCI=0x88a8 |S-PCP|D| S-VID | 1177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1178 | Length/Type | | 1179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1180 | | 1181 ~ Customer Data ~ 1182 ~ ~ 1183 | | 1184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1186 Figure A-3: IEEE802.1ad (no C-Tag) Frame Format in Provider Bridged 1187 Network 1189 0 1 2 3 1190 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 1191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1192 | C-DA | 1193 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1194 | | | 1195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1196 | C-SA | 1197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1198 | S-TAG TCI=0x88a8 |S-PCP|D| S-VID | 1199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1200 | C-TAG TCI=0x8100 |C-PCP|C| C-VID | 1201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1202 | Length/Type | | 1203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1204 | | 1205 ~ Customer Data ~ 1206 ~ ~ 1207 | | 1208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1210 Figure A-4: IEEE802.1ad (C-Tagged) Frame Format in Provider Bridged 1211 Network 1213 0 1 2 3 1214 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 1215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1216 | B-DA | 1217 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1218 | | | 1219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1220 | B-SA | 1221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1222 | B-TAG TCI=0x88a8 |B-PCP|D| B-VID | 1223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1224 | I-TAG TCI=0x88e7 |I-PCP|D|U| Res | I-SID | 1225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1226 | I-SID | | 1227 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1228 | C-DA | 1229 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1230 | C-SA | 1231 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1232 | | Length/Type | 1233 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1234 | | 1235 ~ Customer Data ~ 1236 ~ ~ 1237 | | 1238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1240 Figure A-5: IEEE802.1ah (no C-Tag) Frame Format in Provider Backbone 1241 Bridged Network 1243 0 1 2 3 1244 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 1245 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1246 | B-DA | 1247 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1248 | | | 1249 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1250 | B-SA | 1251 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1252 | B-TAG TCI=0x88a8 |B-PCP|D| B-VID | 1253 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1254 | I-TAG TCI=0x88e7 |I-PCP|D|U| Res | I-SID | 1255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1256 | I-SID | | 1257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1258 | C-DA | 1259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1260 | C-SA | 1261 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1262 | | C-TAG TCI=0x8100 | 1263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1264 |C-PCP|C| C-VID | Length/Type | 1265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1266 | | 1267 ~ Customer Data ~ 1268 ~ ~ 1269 | | 1270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1272 Figure A-6: IEEE802.1ah (C-Tagged) Frame Format in Provider Backbone 1273 Bridged Network 1275 Appendix B. Frame Formats in Data Center Network 1277 0 1 2 3 1278 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 1279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1280 | C-DA | 1281 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1282 | | | 1283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1284 | C-SA | 1285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1286 | S-TAG TCI=0x88a8 |S-PCP|D| S-VID | 1287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1288 | Length/Type | | 1289 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1290 | | 1291 ~ Customer Data ~ 1292 ~ ~ 1293 | | 1294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1296 Figure B-1: IEEE802.1BR (S-TAG) Frame Format in Data Center Network 1298 0 1 2 3 1299 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 1300 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1301 | C-DA | 1302 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1303 | | | 1304 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1305 | C-SA | 1306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1307 | S-TAG TCI=0x88a8 |S-PCP|D| S-VID | 1308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1309 | C-TAG TCI=0x8100 |C-PCP|C| C-VID | 1310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1311 | Length/Type | | 1312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1313 | | 1314 ~ Customer Data ~ 1315 ~ ~ 1316 | | 1317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1319 Figure B-2: IEEE802.1BR (S-TAG+C-TAG) Frame Format in Data Center 1320 Network 1322 0 1 2 3 1323 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 1324 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1325 | C-DA | 1326 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1327 | | | 1328 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1329 | C-SA | 1330 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1331 | E-TAG TCI=0x893F |E-PCP|D| Ingress_E-CID_base | 1332 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1333 |Res|GRP| E-CID_base | 1334 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1335 | Ingress_E-CID_ext | E-CID_ext | 1336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1337 | Length/Type | | 1338 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1339 | | 1340 ~ Customer Data ~ 1341 ~ ~ 1342 | | 1343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1345 Figure B-3: IEEE802.1BR (E-TAG) Frame Format in Data Center Network 1347 0 1 2 3 1348 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 1349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1350 | C-DA | 1351 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1352 | | | 1353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1354 | C-SA | 1355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1356 | E-TAG TCI=0x893F |E-PCP|D| Ingress_E-CID_base | 1357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1358 |Res|GRP| E-CID_base | 1359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1360 | Ingress_E-CID_ext | E-CID_ext | 1361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1362 | C-TAG TCI=0x8100 |C-PCP|C| C-VID | 1363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1364 | Length/Type | | 1365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1366 | | 1367 ~ Customer Data ~ 1368 ~ ~ 1369 | | 1370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1372 Figure B-4: IEEE802.1BR (E-TAG+C-TAG) Frame Format in Data Center 1373 Network 1375 Appendix C. Template Formats Example 1377 0 1 2 3 1378 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 1379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1380 | Set ID (0x0002) | Length | 1381 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1382 | Template ID (0x0103) | Field Count (0x0008) | 1383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1384 | ingressInterface (0x000A) | Field Length (0x0004) | 1385 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1386 | egressInterface (0x000E) | Field Length (0x0004) | 1387 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1388 |observationTimeSeconds (0x0142)| Field Length (0x0008) | 1389 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1390 | dataLinkFrameSize (0x0138) | Field Length (0x0002) | 1391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1392 | dataLinkFrameSection (0x013B) | Field Length (0xFF40) | 1393 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1394 | dataLinkFrameType (0x015B) | Field Length (0x0002) | 1395 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1396 | sectionOffset (0x015C) | Field Length (0x0002) | 1397 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1398 |sectionObservedOctets (0x015D) | Field Length (0x0002) | 1399 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1401 Figure C-1: Template Format Example 1403 Authors' Addresses 1405 Shingo Kashima 1406 NTT Information Sharing Platform Lab. 1407 Midori-Cho 3-9-11 1408 Musashino-shi, Tokyo 180-8585 1409 Japan 1411 Phone: +81 422 59 3894 1412 Email: kashima@nttv6.net 1413 Atsushi Kobayashi 1414 NTT EAST IT Innovation Department 1415 25F 3-20-2 Nishi-shinjuku 1416 Shinjuku-ku, Tokyo 163-1425 1417 Japan 1419 Phone: +81 3 5353 3636 1420 Email: akoba@nttv6.net 1422 Paul Aitken 1423 Cisco Systems, Inc. 1424 96 Commercial Quay 1425 Commercial Street, Edinburgh EH6 6LX 1426 United Kingdom 1428 Phone: +44 131 561 3616 1429 Email: paitken@cisco.com