idnits 2.17.1 draft-kashima-ipfix-data-link-layer-monitoring-07.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 (March 12, 2012) is 4427 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) == Unused Reference: 'RFC2863' is defined on line 1093, but no explicit reference was found in the text == Unused Reference: 'RFC3954' is defined on line 1096, but no explicit reference was found in the text == Unused Reference: 'RFC5475' is defined on line 1103, but no explicit reference was found in the text == Outdated reference: A later version (-09) exists of draft-mahalingam-dutt-dcops-vxlan-01 -- Obsolete informational reference (is this intentional?): RFC 5101 (Obsoleted by RFC 7011) Summary: 1 error (**), 0 flaws (~~), 6 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 K. Nakata 4 Intended status: Standards Track NTT 5 Expires: September 13, 2012 A. Kobayashi 6 NTT East 7 March 12, 2012 9 Information Elements for Data Link Layer Traffic Measurement 10 draft-kashima-ipfix-data-link-layer-monitoring-07 12 Abstract 14 This document describes Information Elements related to data link 15 layer. They are used by the IP Flow Information Export (IPFIX) 16 protocol for encoding measured data link layer traffic information. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on September 13, 2012. 35 Copyright Notice 37 Copyright (c) 2012 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 This document may contain material from IETF Documents or IETF 51 Contributions published or made publicly available before November 52 10, 2008. The person(s) controlling the copyright in some of this 53 material may not have granted the IETF Trust the right to allow 54 modifications of such material outside the IETF Standards Process. 55 Without obtaining an adequate license from the person(s) controlling 56 the copyright in such materials, this document may not be modified 57 outside the IETF Standards Process, and derivative works of it may 58 not be created outside the IETF Standards Process, except to format 59 it for publication as an RFC or to translate it into languages other 60 than English. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 1.1. Conventions Used in This Document . . . . . . . . . . . . 4 66 2. Extended Ethernet Technology . . . . . . . . . . . . . . . . . 4 67 2.1. Wide-Area Ethernet Summary . . . . . . . . . . . . . . . . 4 68 2.2. Data Center Bridging Summary . . . . . . . . . . . . . . . 5 69 2.3. Multiple Path Ethernet Summary . . . . . . . . . . . . . . 5 70 2.4. VXLAN Summary . . . . . . . . . . . . . . . . . . . . . . 6 71 3. New Information Elements . . . . . . . . . . . . . . . . . . . 6 72 3.1. dataLinkFrameSize . . . . . . . . . . . . . . . . . . . . 7 73 3.2. dataLinkFrameSection . . . . . . . . . . . . . . . . . . . 8 74 3.3. dataLinkFrameType . . . . . . . . . . . . . . . . . . . . 8 75 3.4. sectionOffset . . . . . . . . . . . . . . . . . . . . . . 9 76 3.5. sectionObservedOctets . . . . . . . . . . . . . . . . . . 9 77 3.6. dot1qServiceInstanceTag . . . . . . . . . . . . . . . . . 10 78 3.7. dot1qServiceInstanceId . . . . . . . . . . . . . . . . . . 10 79 3.8. dot1qServiceInstancePriority . . . . . . . . . . . . . . . 10 80 3.9. dot1qCustomerDestinationMacAddress . . . . . . . . . . . . 11 81 3.10. dot1qCustomerSourceMacAddress . . . . . . . . . . . . . . 11 82 3.11. l2OctetDeltaCount . . . . . . . . . . . . . . . . . . . . 12 83 3.12. postMCastL2OctetDeltaCount . . . . . . . . . . . . . . . . 12 84 3.13. postL2OctetDeltaCount . . . . . . . . . . . . . . . . . . 13 85 3.14. minimumL2TotalLength . . . . . . . . . . . . . . . . . . . 13 86 3.15. maximumL2TotalLength . . . . . . . . . . . . . . . . . . . 13 87 3.16. l2octetTotalCount . . . . . . . . . . . . . . . . . . . . 14 88 3.17. droppedL2OctetDeltaCount . . . . . . . . . . . . . . . . . 14 89 3.18. droppedL2OctetTotalCount . . . . . . . . . . . . . . . . . 15 90 3.19. ignoredL2OctetTotalCount . . . . . . . . . . . . . . . . . 15 91 3.20. notSentL2OctetTotalCount . . . . . . . . . . . . . . . . . 15 92 3.21. postL2OctetTotalCount . . . . . . . . . . . . . . . . . . 16 93 3.22. postMCastL2OctetTotalCount . . . . . . . . . . . . . . . . 16 94 3.23. l2octetDeltaSumOfSquares . . . . . . . . . . . . . . . . . 17 95 3.24. l2octetTotalSumOfSquares . . . . . . . . . . . . . . . . . 17 96 4. Modification of Existing Information Elements Related to 97 Packet Section . . . . . . . . . . . . . . . . . . . . . . . . 17 98 4.1. ipHeaderPacketSection . . . . . . . . . . . . . . . . . . 18 99 4.2. ipPayloadPacketSection . . . . . . . . . . . . . . . . . . 18 100 4.3. mplsLabelStackSection . . . . . . . . . . . . . . . . . . 18 101 4.4. mplsPayloadPacketSection . . . . . . . . . . . . . . . . . 18 102 5. Modification of Existing Information Elements Related to 103 VLAN Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 104 5.1. dot1qVlanId . . . . . . . . . . . . . . . . . . . . . . . 19 105 5.2. dot1qPriority . . . . . . . . . . . . . . . . . . . . . . 20 106 5.3. dot1qCustomerVlanId . . . . . . . . . . . . . . . . . . . 20 107 5.4. dot1qCustomerPriority . . . . . . . . . . . . . . . . . . 21 108 6. The relationship between Ethernet header filelds and 109 Information Elements . . . . . . . . . . . . . . . . . . . . . 21 110 7. Security Considerations . . . . . . . . . . . . . . . . . . . 23 111 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 112 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 113 9.1. Normative References . . . . . . . . . . . . . . . . . . . 23 114 9.2. Informative References . . . . . . . . . . . . . . . . . . 23 115 Appendix A. Frame Formats in Wide-Area Ethernet Network . . . . . 26 116 Appendix B. Frame Formats in Data Center Network . . . . . . . . 30 117 Appendix C. Template Formats Example . . . . . . . . . . . . . . 33 118 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 120 1. Introduction 122 Ethernet [IEEE802.1D] and VLAN (Virtual LAN) [IEEE802.1Q-2005] 123 technologies used to be used only in Local Area Networks. Recently, 124 they have been used in Wide Area Networks, e.g., L2-VPN services. 125 Accordingly, the IEEE802.1Q standard has been enhanced to IEEE802.1ad 126 [IEEE802.1ad-2005] and IEEE802.1ah [IEEE802.1ah-2008]. And, Ethernet 127 in data center also has been enhanced for server virtualization and 128 I/O consolidation. 130 While these innovations provide flexibility, scalability, and 131 mobility to an existing network architecture, it increases the 132 complexity of traffic measurement due to the existence of various 133 Ethernet header formats. To cope with this, a more sophisticated 134 method is required. 136 IPFIX/PSAMP helps to resolve these problems. However, the PSAMP 137 Information Model [RFC5477] and the IPFIX Information Model [RFC5101] 138 are not yet enough for Information Elements related to data link 139 layer, e.g., Ethernet header forms. This document describes the 140 Information Elements related to data link layers that enable a more 141 sophisticated traffic measurement method. 143 1.1. Conventions Used in This Document 145 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 146 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 147 document are to be interpreted as described in RFC 2119 [RFC2119]. 149 2. Extended Ethernet Technology 151 2.1. Wide-Area Ethernet Summary 153 Provider Bridge [IEEE802.1ad-2005] and Provider Backbone Bridge 154 [IEEE802.1ah-2008], which are standards for the Wide-Area Ethernet, 155 are described below. 157 o In Provider Bridge [IEEE802.1ad-2005], there are two VLAN IDs: 158 Service VLAN Identifier (S-VID) and Customer VLAN Identifier 159 (C-VID). S-VID is assigned to an Ethernet frame by a service 160 provider, while C-VID is independently assigned to an Ethernet 161 frame by a customer. Frame switching in a service provider 162 network is based on only S-VID. 163 o In Provider Backbone Bridge [IEEE802.1ah-2008], new Ethernet 164 fields, such as Backbone VLAN Identifier (B-VID) and Backbone 165 Service Instance Identifier (I-SID), are introduced to overcome 166 the limitations on the VLAN identifier space on IEEE802.1ad 168 [IEEE802.1ad-2005] and to isolate the service provider and 169 customer identifier spaces. Frame switching is based on a 12-bit 170 B-VID, and customer identification is based on a 24-bit I-SID. A 171 flexible network design has become possible because network 172 management is separated from customer management. Other Ethernet 173 fields that indicate quality of service (QoS) class are B-PCP, 174 B-DEI, I-PCP, and I-DEI. 176 Provider Backbone Bridge enables a wide-area Ethernet service to be 177 improved from a flat network to a hierarchical network co-existing 178 Provider Bridge and Provider Backbone Bridge. 180 Frame formats used in Wide-Area Ethernet are shown in Appendix A. 182 2.2. Data Center Bridging Summary 184 In data center networks, Ethernet needs to be enhanced to provide the 185 flexibility, mobility for server virtualization, and I/O 186 consolidation. In IEEE802.1 Data Center Bridging Task Group, several 187 Ethernet header formats are proposed to enable a simplifying networks 188 and server managements. 190 The one of the enhanced methods is Bridge Port Extension 191 [IEEE802.1BR], which brings a traffic exchange point to upper 192 bridges. Bridge Port Extension introduces a Ethernet format named 193 Extension Tag (E-TAG) in addition to existing Service VLAN Tag 194 (S-TAG) and Customer VLAN Tag (C-TAG) to move the policy enhancement 195 to upper bridges in data center network. On the other hand, the 196 complexity for traffic measurement would be increased, because 197 multiple Ethernet header formats as shown in Appendix B co-exist in 198 the same network. 200 2.3. Multiple Path Ethernet Summary 202 Inside data center networks, Ethernet need to be enhaced to support 203 multiple path for effective utilization of bandwidth. Existing 204 Ethernet does not support multiple path because it is based on STP 205 (Spanning Tree Protocol) [IEEE802.1D]. 207 Two solutions for multiple path Ethernet are discussed for 208 standardization. One is Shortest Path Bridging [IEEE802.1aq] in IEEE 209 802, the other is TRILL (Transparent Interconnection of Lots of 210 Links) [RFC6325] in IETF. Both solutions realize multiple path with 211 IS-IS [ISO_IEC.10589_2002] and Layer 2 over Layer 2 encapsulation. 212 Shortest Path Bridging uses IEEE802.1ah [IEEE802.1ah-2008] header as 213 an encapsulation technology and TRILL uses an unique header as shown 214 in Section 3 of [RFC6325]. 216 In multiple path Ehternet network, a traffic measurement based on MAC 217 address and VLAN Tag is more important than single path Ethernet 218 network in which traffic measurement is based on only VLAN Tag. 220 2.4. VXLAN Summary 222 Inside and between data center networks, the existing Ethernet and 223 VLAN technologies have two problems. One is that 12 bit of VLAN ID 224 does not have enough length for identifying a lot of tenants. The 225 other is that it is difficult to place same VLAN in multiple data 226 centers. 228 The solution for the problems is VXLAN 229 [I-D.mahalingam-dutt-dcops-vxlan]. VXLAN has 24 bit length of 230 identifier named VXLAN Segment ID/VXLAN Network Identifier (VNI) and 231 uses Layer 2 over Layer 3 encapsulation with the frame format as show 232 in Section 5 of [I-D.mahalingam-dutt-dcops-vxlan]. 234 3. New Information Elements 236 The following Information Elements whose ElementId are 31 from to 349 237 are necessary for enabling the IPFIX/PSAMP traffic measurement for 238 data link layer, which is not limited to Ethernet because the method 239 can be applied to other data link protocols as well. 241 The following Information Elements whose ElementId are 350 from to 242 354 are necessary for enabling the IPFIX/PSAMP traffic measurement 243 for IEEE 802.1ah. 245 The following Information Elements whose ElementId are TBD01 from to 246 TBD14 are octet counter or packet length for layer 2, and are 247 necessary for enabling the IPFIX/PSAMP traffic measurement for data 248 link layer. 250 Note that these are proposed IDs, subject to approval by IANA. 252 +-----+------------------------------------+ 253 | ID | Name | 254 +-----+------------------------------------+ 255 | 312 | dataLinkFrameSize | 256 | 315 | dataLinkFrameSection | 257 | 347 | dataLinkFrameType | 258 | 348 | sectionOffset | 259 | 349 | sectionObservedOctets | 260 | 350 | dot1qServiceInstanceTag | 261 | 351 | dot1qServiceInstanceId | 262 | 352 | dot1qServiceInstancePriority | 263 | 353 | dot1qCustomerDestinationMacAddress | 264 | 354 | dot1qCustomerSourceMacAddress | 265 |TBD01| l2octetDeltaCount | 266 |TBD02| postMCastL2OctetDeltaCount | 267 |TBD03| postL2OctetDeltaCount | 268 |TBD04| minimumL2TotalLength | 269 |TBD05| maximumL2TotalLength | 270 |TBD06| l2octetTotalCount | 271 |TBD07| droppedL2OctetDeltaCount | 272 |TBD08| droppedL2OctetTotalCount | 273 |TBD09| ignoredL2OctetTotalCount | 274 |TBD10| notSentL2OctetTotalCount | 275 |TBD11| postL2OctetTotalCount | 276 |TBD12| postMCastL2OctetTotalCount | 277 |TBD13| l2octetDeltaSumOfSquares | 278 |TBD14| l2octetTotalSumOfSquares | 279 +-----+------------------------------------+ 281 3.1. dataLinkFrameSize 283 Description: 285 This Information Element specifies the length of the selected data 286 link frame. 288 The data link layer is defined in [ISO_IEC.7498-1_1994]. 290 Abstract Data Type: unsigned16 292 Data Type Semantics: quantity 294 ElementId: 312 296 Status: current 298 3.2. dataLinkFrameSection 300 Description: 302 This Information Element carries n octets from the data link frame 303 of a selected frame, starting sectionOffset octets into the frame. 305 The sectionObservedOctets expresses how much data was observed, 306 while the remainder is padding. 308 When the sectionObservedOctets field corresponding to this 309 Information Element exists, this Information Element MAY have a 310 fixed length and MAY be padded, or MAY have a variable length. 312 When the sectionObservedOctets field corresponding to this 313 Information Element does not exist, this Information Element 314 SHOULD have a variable length and MUST NOT be padded. In this 315 case, the size of the exported section may be constrained due to 316 limitations in the IPFIX protocol. 318 Further Information Elements, i.e., dataLinkFrameType and 319 dataLinkFrameSize are needed to specify the data link type and the 320 size of the data link frame of this Information Element. A set of 321 these Information Elements MAY be contained in a structured data 322 type, as expressed in [RFC6313]. Or a set of these Information 323 Elements MAY be contained in one Flow Record as shown in Appendix 324 C. 326 The data link layer is defined in [ISO_IEC.7498-1_1994]. 328 Abstract Data Type: octetArray 330 ElementId: 315 332 Status: current 334 3.3. dataLinkFrameType 336 Description: 338 This Information Element specifies the type of the selected data 339 link frame. 341 The following data link types are defined here. 343 - 0x01 ETHERNET 344 Further values may be assigned by IANA. 346 The data link layer is defined in [ISO_IEC.7498-1_1994]. 348 Abstract Data Type: unsigned16 350 Data Type Semantics: identifier 352 ElementId: 347 354 Status: current 356 3.4. sectionOffset 358 Description: 360 This Information Element specifies the offset of the packet 361 section (e.g., dataLinkFrameSection, ipHeaderPacketSection, 362 ipPayloadPacketSection, mplsLabelStackSection and 363 mplsPayloadPacketSection). If this Information Element is 364 omitted, it defaults to zero. 366 Abstract Data Type: unsigned16 368 Data Type Semantics: quantity 370 ElementId: 348 372 Status: current 374 3.5. sectionObservedOctets 376 Description: 378 This Information Element specifies the observed length of the 379 packet section (e.g., dataLinkFrameSection, ipHeaderPacketSection, 380 ipPayloadPacketSection, mplsLabelStackSection and 381 mplsPayloadPacketSection) when padding is used. 383 The packet section may be of a fixed size larger than the 384 sectionObservedOctets. In this case, octets in the packet section 385 beyond the sectionObservedOctets MUST follow the [RFC5101] rules 386 for padding (ie, be composed of zero (0) valued octets). 388 Abstract Data Type: unsigned16 390 Data Type Semantics: quantity 391 ElementId: 349 393 Status: current 395 3.6. dot1qServiceInstanceTag 397 Description: 399 This Information Element, which may have 16 octets length, 400 represents the Backbone Service Instance Tag (I-TAG) Tag Control 401 Information (TCI) field of an Ethernet frame as described in 402 [IEEE802.1ah-2008]. It encodes the Backbone Service Instance 403 Priority Code Point (I-PCP), Drop Eligible Indicator (I-DEI), Use 404 Customer Addresses (UCA), Backbone Service Instance Identifier 405 (I-SID), Encapsulated Customer Destination Address (C-DA), 406 Encapsulated Customer Source Address (C-SA) and reserved fileds. 408 Abstract Data Type: octetArray 410 Data Type Semantics: identifier 412 ElementId: 350 414 Status: current 416 3.7. dot1qServiceInstanceId 418 Description: 420 The value of the 24-bit Backbone Service Instance Identifier 421 (I-SID) portion of the Backbone Service Instance Tag (I-TAG) Tag 422 Control Information (TCI) field of an Ethernet frame as described 423 in section 9.8 of [IEEE802.1ah-2008]. The structure and semantics 424 within the Tag Control Information field are defined in 425 IEEE802.1ah. 427 Abstract Data Type: unsigned32 429 Data Type Semantics: identifier 431 ElementId: 351 433 Status: current 435 3.8. dot1qServiceInstancePriority 437 Description: 439 The value of the 3-bit Backbone Service Instance Priority Code 440 Point (I-PCP) portion of the Backbone Service Instance Tag (I-TAG) 441 Tag Control Information (TCI) field of an Ethernet frame as 442 described in section 9.8 of [IEEE802.1ah-2008]. The structure and 443 semantics within the Tag Control Information field are defined in 444 IEEE802.1ah. 446 Abstract Data Type: unsigned8 448 Data Type Semantics: identifier 450 ElementId: 352 452 Status: current 454 3.9. dot1qCustomerDestinationMacAddress 456 Description: 458 The value of the Encapsulated Customer Destination Address (C-DA) 459 portion of the Backbone Service Instance Tag (I-TAG) Tag Control 460 Information (TCI) field of an Ethernet frame as described in 461 section 9.8 of [IEEE802.1ah-2008]. The structure and semantics 462 within the Tag Control Information field are defined in 463 IEEE802.1ah. 465 Abstract Data Type: macAddress 467 Data Type Semantics: identifier 469 ElementId: 353 471 Status: current 473 3.10. dot1qCustomerSourceMacAddress 475 Description: 477 The value of the Encapsulated Customer Source Address (C-SA) 478 portion of the Backbone Service Instance Tag (I-TAG) Tag Control 479 Information (TCI) field of an Ethernet frame as described in 480 section 9.8 of [IEEE802.1ah-2008]. The structure and semantics 481 within the Tag Control Information field are defined in 482 IEEE802.1ah. 484 Abstract Data Type: macAddress 486 Data Type Semantics: identifier 487 ElementId: 354 489 Status: current 491 3.11. l2OctetDeltaCount 493 Description: 495 The number of layer 2 octets since the previous report (if any) in 496 incoming packets for this Flow at the Observation Point. The 497 number of octets includes layer 2 header(s) and layer 2 payload. 498 # memo: layer 2 version of octetDeltaCount (field #1) 500 Abstract Data Type: unsigned64 502 Data Type Semantics: deltaCounter 504 ElementId: TBD01 506 Status: current 508 Units: octets 510 3.12. postMCastL2OctetDeltaCount 512 Description: 514 The number of layer 2 octets since the previous report (if any) in 515 outgoing multicast packets sent for packets of this Flow by a 516 multicast daemon within the Observation Domain. This property 517 cannot necessarily be observed at the Observation Point, but may 518 be retrieved by other means. The number of octets includes layer 519 2 header(s) and layer 2 payload. 520 # memo: layer 2 version of postMCastOctetDeltaCount (field #20) 522 Abstract Data Type: unsigned64 524 Data Type Semantics: deltaCounter 526 ElementId: TBD02 528 Status: current 530 Units: octets 532 3.13. postL2OctetDeltaCount 534 Description: 536 The definition of this Information Element is identical to the 537 definition of Information Element 'l2OctetDeltaCount', except that 538 it reports a potentially modified value caused by a middlebox 539 function after the packet passed the Observation Point. 540 # memo: layer 2 version of postOctetDeltaCount (field #23) 542 Abstract Data Type: unsigned64 544 Data Type Semantics: deltaCounter 546 ElementId: TBD03 548 Status: current 550 Units: octets 552 3.14. minimumL2TotalLength 554 Description: 556 Layer 2 length of the smallest packet observed for this Flow. The 557 packet length includes the layer 2 header(s) length and the layer 558 2 payload length. 559 # memo: layer 2 version of minimumIpTotalLength (field #25) 561 Abstract Data Type: unsigned64 563 ElementId: TBD04 565 Status: current 567 Units: octets 569 3.15. maximumL2TotalLength 571 Description: 573 Layer 2 length of the largest 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 maximumIpTotalLength (field #26) 578 Abstract Data Type: unsigned64 579 ElementId: TBD05 581 Status: current 583 Units: octets 585 3.16. l2octetTotalCount 587 Description: 589 The total number of layer 2 octets in incoming packets for this 590 Flow at the Observation Point since the Metering Process 591 (re-)initialization for this Observation Point. The number of 592 octets includes layer 2 header(s) and layer 2 payload. 593 # memo: layer 2 version of octetTotalCount (field #85) 595 Abstract Data Type: unsigned64 597 Data Type Semantics: totalCounter 599 ElementId: TBD06 601 Status: current 603 Units: octets 605 3.17. droppedL2OctetDeltaCount 607 Description: 609 The number of layer 2 octets since the previous report (if any) in 610 packets of this Flow dropped by packet treatment. The number of 611 octets includes layer 2 header(s) and layer 2payload. 612 # memo: layer 2 version of droppedOctetDeltaCount (field #132) 614 Abstract Data Type: unsigned64 616 Data Type Semantics: deltaCounter 618 ElementId: TBD07 620 Status: current 622 Units: octets 624 3.18. droppedL2OctetTotalCount 626 Description: 628 The number of layer 2 octets since the previous report (if any) in 629 packets of this Flow dropped by packet treatment. The number of 630 octets includes layer 2 header(s) and layer 2 payload. 631 # memo: layer 2 version of droppedOctetTotalCount (field #134) 633 Abstract Data Type: unsigned64 635 Data Type Semantics: totalCounter 637 ElementId: TBD08 639 Status: current 641 Units: octets 643 3.19. ignoredL2OctetTotalCount 645 Description: 647 The total number of octets in observed layer 2 packets (including 648 the layer 2 header) that the Metering Process did not process 649 since the (re-)initialization of the Metering Process. 650 # memo: layer 2 version of ignoredOctetTotalCount (field #165) 652 Abstract Data Type: unsigned64 654 Data Type Semantics: totalCounter 656 ElementId: TBD09 658 Status: current 660 Units: octets 662 3.20. notSentL2OctetTotalCount 664 Description: 666 The total number of octets in observed layer 2 packets (including 667 the layer 2 header) that the Metering Process did not process 668 since the (re-)initialization of the Metering Process. 669 # memo: layer 2 version of notSentOctetTotalCount (field #168) 671 Abstract Data Type: unsigned64 672 Data Type Semantics: totalCounter 674 ElementId: TBD10 676 Status: current 678 Units: octets 680 3.21. postL2OctetTotalCount 682 Description: 684 The definition of this Information Element is identical to the 685 definition of Information Element 'l2OctetTotalCount', except that 686 it reports a potentially modified value caused by a middlebox 687 function after the packet passed the Observation Point. 688 # memo: layer 2 version of postOctetTotalCount (field #171) 690 Abstract Data Type: unsigned64 692 Data Type Semantics: totalCounter 694 ElementId: TBD11 696 Status: current 698 Units: octets 700 3.22. postMCastL2OctetTotalCount 702 Description: 704 The total number of layer 2 octets in outgoing multicast packets 705 sent for packets of this Flow by a multicast daemon in the 706 Observation Domain since the Metering Process (re-)initialization. 707 This property cannot necessarily be observed at the Observation 708 Point, but may be retrieved by other means. The number of octets 709 includes layer 2 header(s) and layer 2 payload. 710 # memo: layer 2 version of postMCastOctetTotalCount (field #175) 712 Abstract Data Type: unsigned64 714 Data Type Semantics: totalCounter 716 ElementId: TBD12 718 Status: current 719 Units: octets 721 3.23. l2octetDeltaSumOfSquares 723 Description: 725 The sum of the squared numbers of layer 2 octets per incoming 726 packet since the previous report (if any) for this Flow at the 727 Observation Point. The number of octets includes layer 2 728 header(s) and layer 2 payload. 729 # memo: layer 2 version of octetDeltaSumOfSquares (field #198) 731 Abstract Data Type: unsigned64 733 Data Type Semantics: deltaCounter 735 ElementId: TBD13 737 Status: current 739 Units: octets 741 3.24. l2octetTotalSumOfSquares 743 Description: 745 The total sum of the squared numbers of layer 2 octets in incoming 746 packets for this Flow at the Observation Point since the Metering 747 Process (re-)initialization for this Observation Point. The 748 number of octets includes layer 2 header(s) and layer 2 payload. 749 # memo: layer 2 version of octetTotalSumOfSquares (field #199) 751 Abstract Data Type: unsigned64 753 Data Type Semantics: totalCounter 755 ElementId: TBD14 757 Status: current 759 Units: octets 761 4. Modification of Existing Information Elements Related to Packet 762 Section 764 --- This is open issue. --- 765 New Information Elements related to packet section (ie, sectionOffset 766 and sectionObservedOctets) can be applied to not only 767 dataLinkFrameSection but also all kinds of packet section. In this 768 case, existing Information Elements Description should be modified as 769 follows: 771 4.1. ipHeaderPacketSection 773 Description: 775 TBD 777 Abstract Data Type: octetArray 779 ElementId: 313 781 Status: current 783 4.2. ipPayloadPacketSection 785 Description: 787 TBD 789 Abstract Data Type: octetArray 791 ElementId: 314 793 Status: current 795 4.3. mplsLabelStackSection 797 Description: 799 TBD 801 Abstract Data Type: octetArray 803 ElementId: 316 805 Status: current 807 4.4. mplsPayloadPacketSection 809 Description: 811 TBD 813 Abstract Data Type: octetArray 815 ElementId: 317 817 Status: current 819 5. Modification of Existing Information Elements Related to VLAN Tag 821 Information Elements related to Backbone Service Instance Tag (I-TAG) 822 and Backbone VLAN Tag (B-TAG) are required in order to monitor 823 IEEE802.1ah traffic with IPFIX/PSAMP. New Information Elements 824 related to I-TAG are added in section 3 because I-TAG has different 825 structure and semantics from Service VLAN Tag (S-TAG) and Customer 826 VLAN Tag (C-TAG). On the other hand, Information Elements related to 827 B-TAG reuse existing Information Elements related to C-TAG and S-TAG 828 because B-TAG has same structure and semantics with C-TAG and S-TAG, 829 Though they reuse existing Information Elements, it required to 830 modify existing Descriptions and Reference as follows: 832 5.1. dot1qVlanId 834 Description: 836 The value of the 12-bit VLAN Identifier portion of the Tag Control 837 Information field of an Ethernet frame as described in section 838 3.5.5 of [IEEE802.3-2005]. The structure and semantics within the 839 Tag Control Information field are defined in IEEE P802.1Q. In case 840 of a QinQ frame it represents the outer tag's VLAN identifier, in 841 case of an IEEE 802.1ad frame it represents the Service VLAN 842 identifier in the S-TAG Tag Control Information (TCI) field as 843 described in [IEEE802.1ad-2005] and in case of an IEEE 802.1ah 844 frame it represents the Backbone VLAN identifier in the B-TAG Tag 845 Control Information (TCI) field as described in 846 [IEEE802.1ah-2008]. 848 Abstract Data Type: unsigned16 850 Data Type Semantics: identifier 852 ElementId: 243 854 Status: current 856 Reference: 858 (1) [IEEE802.3-2005] 859 (2) [IEEE802.1ad-2005] 860 (3) [IEEE802.1ah-2008] 862 5.2. dot1qPriority 864 Description: 866 The value of the 3-bit User Priority portion of the Tag Control 867 Information field of an Ethernet frame as described in section 868 3.5.5 of [IEEE802.3-2005]. The structure and semantics within the 869 Tag Control Information field are defined in IEEE P802.1Q. In case 870 of a QinQ frame it represents the outer tag's 3-bit Class of 871 Service (CoS) identifier, in case of an IEEE 802.1ad frame it 872 represents the 3-bit Priority Code Point (PCP) portion of the 873 S-TAG Tag Control Information (TCI) field as described in 874 [IEEE802.1ad-2005] and in case of an IEEE 802.1ah frame it 875 represents the 3-bit Priority Code Point (PCP) portion of the 876 B-TAG Tag Control Information (TCI) field as described in 877 [IEEE802.1ah-2008]. 879 Abstract Data Type: unsigned8 881 Data Type Semantics: identifier 883 ElementId: 244 885 Status: current 887 Reference: 889 (1) [IEEE802.3-2005] 890 (2) [IEEE802.1ad-2005] 891 (3) [IEEE802.1ah-2008] 893 5.3. dot1qCustomerVlanId 895 Description: 897 In case of a QinQ frame it represents the inner tag's (*) VLAN 898 identifier, in case of an IEEE 802.1ad frame it represents the 899 Customer VLAN identifier in the C-TAG Tag Control Information 900 (TCI) field as described in [IEEE802.1ad-2005] and in case of an 901 IEEE 802.1ah frame it represents the Customer VLAN identifier in 902 the C-TAG Tag Control Information (TCI) field in encapsulated IEEE 903 802.1ad or IEEE 802.1Q frame as described in [IEEE802.1ah-2008]. 905 (*) Note: the 802.1Q tag directly following the outer one. 907 Abstract Data Type: unsigned16 909 Data Type Semantics: identifier 911 ElementId: 245 913 Status: current 915 Reference: 917 (1) [IEEE802.1ad-2005] 918 (2) [IEEE802.1Q-2005] 919 (3) [IEEE802.1ah-2008] 921 5.4. dot1qCustomerPriority 923 Description: 925 In case of a QinQ frame it represents the inner tag's (*) Class of 926 Service (CoS) identifier, in case of an IEEE 802.1ad frame it 927 represents the 3-bit Priority Code Point (PCP) portion of the 928 C-TAG Tag Control Information (TCI) field as described in 929 [IEEE802.1ad-2005] and in case of an IEEE 802.1ah frame it 930 represents the 3-bit Priority Code Point (PCP) portion of the 931 C-TAG Tag Control Information (TCI) field in encapsulated IEEE 932 802.1ad or IEEE 802.1Q frame as described in [IEEE802.1ad-2005]. 933 (*) Note: the 802.1Q tag directly following the outer one. 935 Abstract Data Type: unsigned8 937 Data Type Semantics: identifier 939 ElementId: 246 941 Status: current 943 Reference: 945 (1) [IEEE802.1ad-2005] 946 (2) [IEEE802.1Q-2005] 947 (3) [IEEE802.1ah-2008] 949 6. The relationship between Ethernet header filelds and Information 950 Elements 952 The following figures shows summary of various Ethernet header fields 953 and the Informational Elements which would be used to represent each 954 of the fields. 956 <----6----><----6----><----4----><------2------> 957 +----------+----------+----------+--------------+ 958 + + + + + 959 + C-DA + C-SA + C-TAG + Length/Type + 960 + a + b + c + d + 961 +----------+----------+----------+--------------+ 963 a.(Existing Information Element) destinationMacAddress 80 964 b.(Existing Information Element) sourceMacAddress 56 965 c.(Existing Information Elements) dot1qVlanId 243, dot1qPriority 244 966 d.(Existing Information Element) ethernetType 256 968 Figure 1: IEEE 802.1Q header fields 970 <----6----><----6----><----4----><----4----><------2------> 971 +----------+----------+----------+----------+--------------+ 972 + + + + + + 973 + C-DA + C-SA + S-TAG + C-TAG + Length/Type + 974 + a + b + c + d + e + 975 +----------+----------+----------+----------+--------------+ 977 a.(Existing Information Element) destinationMacAddress 80 978 b.(Existing Information Element) sourceMacAddress 56 979 c.(Existing Information Elements) dot1qVlanId 243, dot1qPriority 244 980 d.(Existing Information Elements) dot1qCustomerVlanId 245, dot1qCustomerPriority 246 981 e.(Existing Information Element) ethernetType 256 983 Figure 2: IEEE 802.1ad header fields 985 <----6----><----6----><----4----><------18------><----4----><------2------> 986 +----------+----------+----------+---------------+----------+--------------+ 987 + + + + + + + 988 + B-DA + B-SA + B-TAG + I-TAG + C-TAG + Length/Type + 989 + a + b + c + d + e + f + 990 +----------+----------+----------+---------------+----------+--------------+ 992 a.(Existing Information Element) destinationMacAddress 80 993 b.(Existing Information Element) sourceMacAddress 56 994 c.(Existing Information Elements) dot1qVlanId 243, dot1qPriority 244 995 d.(New Information Elements) defined in section 3.6, 3.7, 3.8, 3.9 and 3.10 of this draft 996 e.(Existing Information Elements) dot1qCustomerVlanId 245, dot1qCustomerPriority 246 997 f.(Existing Information Element) ethernetType 256 999 Figure 3: IEEE 802.1ah header fields 1001 7. Security Considerations 1003 The recommendations in this document do not introduce any additional 1004 security issues to those already mentioned in [RFC5101] and 1005 [RFC5477]. 1007 8. IANA Considerations 1009 This document requests that the Information Element IDs are allocated 1010 as shown in section 3 1012 In addition, the dataLinkFrameType Information Element requires the 1013 creation of new IANA registries. 1015 And this document requests that the existing Information Element 1016 Description are modified as shown in section 4 and 5 1018 9. References 1020 9.1. Normative References 1022 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1023 Requirement Levels", BCP 14, RFC 2119, March 1997. 1025 9.2. Informative References 1027 [I-D.mahalingam-dutt-dcops-vxlan] 1028 Sridhar, T., Bursell, M., Kreeger, L., Dutt, D., Wright, 1029 C., Mahalingam, M., Duda, K., and P. Agarwal, "VXLAN: A 1030 Framework for Overlaying Virtualized Layer 2 Networks over 1031 Layer 3 Networks", draft-mahalingam-dutt-dcops-vxlan-01 1032 (work in progress), February 2012. 1034 [IEEE802.1BR] 1035 IEEE Computer Society, "Draft Standards for Local and 1036 Metropolitan Area Networks: Virtual Bridged Local Area 1037 Networks Amendment: Bridge Port Extension", IEEE 1038 Std P802.1BR/D1.1, February 2011. 1040 [IEEE802.1D] 1041 IEEE Computer Society, "IEEE Standards for Local and 1042 Metropolitan Area Networks: Media Access Control (MAC) 1043 Bridges", IEEE Std 802.1D-2004, June 2004. 1045 [IEEE802.1Q-2005] 1046 IEEE Computer Society, "IEEE Standards for Local and 1047 Metropolitan Area Networks: Virtual Bridged Local Area 1048 Networks", IEEE Std 802.1Q-2005, May 2006. 1050 [IEEE802.1ad-2005] 1051 IEEE Computer Society, "IEEE Standards for Local and 1052 Metropolitan Area Networks: Virtual Bridged Local Area 1053 Networks Amendment 4: Provider Bridges", IEEE Std 802.1ad- 1054 2005, May 2006. 1056 [IEEE802.1ah-2008] 1057 IEEE Computer Society, "IEEE Standards for Local and 1058 Metropolitan Area Networks: Virtual Bridged Local Area 1059 Networks Amendment 7: Provider Backbone Bridges", IEEE 1060 Std 802.1ah-2008, August 2008. 1062 [IEEE802.1aq] 1063 IEEE Computer Society, "Draft Standards for Local and 1064 Metropolitan Area Networks: Virtual Bridged Local Area 1065 Networks Amendment: Shortest Path Bridging", IEEE 1066 Std P802.1aq/D3.6, February 2011. 1068 [IEEE802.3-2005] 1069 IEEE Computer Society, "IEEE Standard for Information 1070 Technology - Telecommunications and Information Exchange 1071 Between Systems - Local and Metropolitan Area Networks - 1072 Specific Requirements Part 3: Carrier Sense Multiple 1073 Access with Collision Detection (CSMA/CD) Access Method 1074 and Physical Layer Specifications", IEEE Std 802.3-2005, 1075 December 2005. 1077 [ISO_IEC.10589_2002] 1078 International Organization for Standardization, 1079 "Information technology -- Telecommunications and 1080 information exchange between systems -- Intermediate 1081 System to Intermediate System intra-domain routing 1082 information exchange protocol for use in conjunction with 1083 the protocol for providing the connectionless-mode network 1084 service (ISO 8473)", ISO Standard 10589:2002, 1085 November 2002. 1087 [ISO_IEC.7498-1_1994] 1088 International Organization for Standardization, 1089 "Information technology -- Open Systems Interconnection -- 1090 Basic Reference Model: The Basic Mode", ISO Standard 7498- 1091 1:1994, June 1996. 1093 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1094 MIB", RFC 2863, June 2000. 1096 [RFC3954] Claise, B., "Cisco Systems NetFlow Services Export Version 1097 9", RFC 3954, October 2004. 1099 [RFC5101] Claise, B., "Specification of the IP Flow Information 1100 Export (IPFIX) Protocol for the Exchange of IP Traffic 1101 Flow Information", RFC 5101, January 2008. 1103 [RFC5475] Zseby, T., Molina, M., Duffield, N., Niccolini, S., and F. 1104 Raspall, "Sampling and Filtering Techniques for IP Packet 1105 Selection", RFC 5475, March 2009. 1107 [RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G. 1108 Carle, "Information Model for Packet Sampling Exports", 1109 RFC 5477, March 2009. 1111 [RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates, 1112 "Export of Structured Data in IP Flow Information Export 1113 (IPFIX)", RFC 6313, July 2011. 1115 [RFC6325] Perlman, R., Eastlake, D., Dutt, D., Gai, S., and A. 1116 Ghanwani, "Routing Bridges (RBridges): Base Protocol 1117 Specification", RFC 6325, July 2011. 1119 Appendix A. Frame Formats in Wide-Area Ethernet Network 1121 0 1 2 3 1122 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 1123 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1124 | C-DA | 1125 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1126 | | | 1127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1128 | C-SA | 1129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1130 | Length/Type | | 1131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1132 | | 1133 ~ Customer Data ~ 1134 ~ ~ 1135 | | 1136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1138 Figure A-1: IEEE802.1D Frame Format in Customer Bridged Network 1140 0 1 2 3 1141 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 1142 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1143 | C-DA | 1144 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1145 | | | 1146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1147 | C-SA | 1148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1149 | C-TAG TCI=0x8100 |C-PCP|C| C-VID | 1150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1151 | Length/Type | | 1152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1153 | | 1154 ~ Customer Data ~ 1155 ~ ~ 1156 | | 1157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1159 Figure A-2: IEEE802.1Q Frame Format in Customer Bridged Network 1161 0 1 2 3 1162 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 1163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1164 | C-DA | 1165 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1166 | | | 1167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1168 | C-SA | 1169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1170 | S-TAG TCI=0x88a8 |S-PCP|D| S-VID | 1171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1172 | Length/Type | | 1173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1174 | | 1175 ~ Customer Data ~ 1176 ~ ~ 1177 | | 1178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1180 Figure A-3: IEEE802.1ad (no C-Tag) Frame Format in Provider Bridged 1181 Network 1183 0 1 2 3 1184 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 1185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1186 | C-DA | 1187 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1188 | | | 1189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1190 | C-SA | 1191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1192 | S-TAG TCI=0x88a8 |S-PCP|D| S-VID | 1193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1194 | C-TAG TCI=0x8100 |C-PCP|C| C-VID | 1195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1196 | Length/Type | | 1197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1198 | | 1199 ~ Customer Data ~ 1200 ~ ~ 1201 | | 1202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1204 Figure A-4: IEEE802.1ad (C-Tagged) Frame Format in Provider Bridged 1205 Network 1207 0 1 2 3 1208 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 1209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1210 | B-DA | 1211 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1212 | | | 1213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1214 | B-SA | 1215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1216 | B-TAG TCI=0x88a8 |B-PCP|D| B-VID | 1217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1218 | I-TAG TCI=0x88e7 |I-PCP|D|U| Res | I-SID | 1219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1220 | I-SID | | 1221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1222 | C-DA | 1223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1224 | C-SA | 1225 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1226 | | Length/Type | 1227 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1228 | | 1229 ~ Customer Data ~ 1230 ~ ~ 1231 | | 1232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1234 Figure A-5: IEEE802.1ah (no C-Tag) Frame Format in Provider Backbone 1235 Bridged Network 1237 0 1 2 3 1238 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 1239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1240 | B-DA | 1241 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1242 | | | 1243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1244 | B-SA | 1245 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1246 | B-TAG TCI=0x88a8 |B-PCP|D| B-VID | 1247 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1248 | I-TAG TCI=0x88e7 |I-PCP|D|U| Res | I-SID | 1249 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1250 | I-SID | | 1251 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1252 | C-DA | 1253 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1254 | C-SA | 1255 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1256 | | C-TAG TCI=0x8100 | 1257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1258 |C-PCP|C| C-VID | Length/Type | 1259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1260 | | 1261 ~ Customer Data ~ 1262 ~ ~ 1263 | | 1264 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1266 Figure A-6: IEEE802.1ah (C-Tagged) Frame Format in Provider Backbone 1267 Bridged Network 1269 Appendix B. Frame Formats in Data Center Network 1271 0 1 2 3 1272 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 1273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1274 | C-DA | 1275 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1276 | | | 1277 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1278 | C-SA | 1279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1280 | S-TAG TCI=0x88a8 |S-PCP|D| S-VID | 1281 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1282 | Length/Type | | 1283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1284 | | 1285 ~ Customer Data ~ 1286 ~ ~ 1287 | | 1288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1290 Figure B-1: IEEE802.1BR (S-TAG) Frame Format in Data Center Network 1292 0 1 2 3 1293 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 1294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1295 | C-DA | 1296 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1297 | | | 1298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1299 | C-SA | 1300 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1301 | S-TAG TCI=0x88a8 |S-PCP|D| S-VID | 1302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1303 | C-TAG TCI=0x8100 |C-PCP|C| C-VID | 1304 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1305 | Length/Type | | 1306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1307 | | 1308 ~ Customer Data ~ 1309 ~ ~ 1310 | | 1311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1313 Figure B-2: IEEE802.1BR (S-TAG+C-TAG) Frame Format in Data Center 1314 Network 1316 0 1 2 3 1317 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 1318 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1319 | C-DA | 1320 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1321 | | | 1322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1323 | C-SA | 1324 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1325 | E-TAG TCI=0x893F |E-PCP|D| Ingress_E-CID_base | 1326 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1327 |Res|GRP| E-CID_base | 1328 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1329 | Ingress_E-CID_ext | E-CID_ext | 1330 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1331 | Length/Type | | 1332 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1333 | | 1334 ~ Customer Data ~ 1335 ~ ~ 1336 | | 1337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1339 Figure B-3: IEEE802.1BR (E-TAG) Frame Format in Data Center Network 1341 0 1 2 3 1342 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 1343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1344 | C-DA | 1345 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1346 | | | 1347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1348 | C-SA | 1349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1350 | E-TAG TCI=0x893F |E-PCP|D| Ingress_E-CID_base | 1351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1352 |Res|GRP| E-CID_base | 1353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1354 | Ingress_E-CID_ext | E-CID_ext | 1355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1356 | C-TAG TCI=0x8100 |C-PCP|C| C-VID | 1357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1358 | Length/Type | | 1359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1360 | | 1361 ~ Customer Data ~ 1362 ~ ~ 1363 | | 1364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1366 Figure B-4: IEEE802.1BR (E-TAG+C-TAG) Frame Format in Data Center 1367 Network 1369 Appendix C. Template Formats Example 1371 0 1 2 3 1372 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 1373 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1374 | Set ID (0x0002) | Length | 1375 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1376 | Template ID (0x0103) | Field Count (0x0008) | 1377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1378 | ingressInterface (0x000A) | Field Length (0x0004) | 1379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1380 | egressInterface (0x000E) | Field Length (0x0004) | 1381 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1382 |observationTimeSeconds (0x0142)| Field Length (0x0008) | 1383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1384 | dataLinkFrameSize (0x0138) | Field Length (0x0002) | 1385 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1386 | dataLinkFrameSection (0x013B) | Field Length (0xFF40) | 1387 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1388 | dataLinkFrameType (0x015B) | Field Length (0x0002) | 1389 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1390 | sectionOffset (0x015C) | Field Length (0x0002) | 1391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1392 |sectionObservedOctets (0x015D) | Field Length (0x0002) | 1393 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1395 Figure C-1: Template Format Example 1397 Authors' Addresses 1399 Shingo Kashima 1400 NTT Information Sharing Platform Lab. 1401 Midori-Cho 3-9-11 1402 Musashino-shi, Tokyo 180-8585 1403 Japan 1405 Phone: +81 422 59 3894 1406 Email: kashima@nttv6.net 1407 Kensuke Nakata 1408 NTT Information Sharing Platform Lab. 1409 Midori-Cho 3-9-11 1410 Musashino-shi, Tokyo 180-8585 1411 Japan 1413 Phone: +81 422 59 6958 1414 Email: nakata@nttv6.net 1416 Atsushi Kobayashi 1417 NTT EAST IT Innovation Department 1418 25F 3-20-2 Nishi-shinjuku 1419 Shinjuku-ku, Tokyo 163-1425 1420 Japan 1422 Phone: +81-3-5353-3636 1423 Email: akoba@nttv6.net