idnits 2.17.1 draft-ietf-ipfix-data-link-layer-monitoring-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 6 instances of too long lines in the document, the longest one being 7 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 date (September 29, 2013) is 3861 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.11' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.1BR' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.1Q' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.1Qbg' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.3' ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) ** Downref: Normative reference to an Informational RFC: RFC 2804 Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 6 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 02, 2014 NTT East 6 P. Aitken 7 Cisco Systems, Inc. 8 September 29, 2013 10 Information Elements for Data Link Layer Traffic Measurement 11 draft-ietf-ipfix-data-link-layer-monitoring-04 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 02, 2014. 36 Copyright Notice 38 Copyright (c) 2013 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 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.1. Conventions Used in This Document . . . . . . . . . . . . 4 55 2. Extended Ethernet Technology . . . . . . . . . . . . . . . . 4 56 2.1. Wide-Area Ethernet Technology Summary . . . . . . . . . . 4 57 2.2. Virtual Ethernet Technology Summary . . . . . . . . . . . 4 58 3. Information Elements Related to Link Frame Section . . . . . 6 59 3.1. Existing Information Elements . . . . . . . . . . . . . . 7 60 3.1.1. dataLinkFrameSize . . . . . . . . . . . . . . . . . . 7 61 3.1.2. dataLinkFrameSection . . . . . . . . . . . . . . . . 7 62 3.2. New Information Elements . . . . . . . . . . . . . . . . 8 63 3.2.1. dataLinkFrameType . . . . . . . . . . . . . . . . . . 8 64 3.2.2. sectionOffset . . . . . . . . . . . . . . . . . . . . 8 65 3.2.3. sectionExportedOctets . . . . . . . . . . . . . . . . 9 66 3.2.4. dot1qServiceInstanceTag . . . . . . . . . . . . . . . 9 67 3.2.5. dot1qServiceInstanceId . . . . . . . . . . . . . . . 10 68 3.2.6. dot1qServiceInstancePriority . . . . . . . . . . . . 10 69 3.2.7. dot1qCustomerDestinationMacAddress . . . . . . . . . 11 70 3.2.8. dot1qCustomerSourceMacAddress . . . . . . . . . . . . 11 71 3.2.9. l2OctetDeltaCount . . . . . . . . . . . . . . . . . . 11 72 3.2.10. postMCastL2OctetDeltaCount . . . . . . . . . . . . . 12 73 3.2.11. postL2OctetDeltaCount . . . . . . . . . . . . . . . . 12 74 3.2.12. minimumL2TotalLength . . . . . . . . . . . . . . . . 13 75 3.2.13. maximumL2TotalLength . . . . . . . . . . . . . . . . 13 76 3.2.14. l2OctetTotalCount . . . . . . . . . . . . . . . . . . 13 77 3.2.15. droppedL2OctetDeltaCount . . . . . . . . . . . . . . 14 78 3.2.16. droppedL2OctetTotalCount . . . . . . . . . . . . . . 14 79 3.2.17. ignoredL2OctetTotalCount . . . . . . . . . . . . . . 15 80 3.2.18. notSentL2OctetTotalCount . . . . . . . . . . . . . . 15 81 3.2.19. postL2OctetTotalCount . . . . . . . . . . . . . . . . 16 82 3.2.20. postMCastL2OctetTotalCount . . . . . . . . . . . . . 16 83 3.2.21. l2OctetDeltaSumOfSquares . . . . . . . . . . . . . . 17 84 3.2.22. l2OctetTotalSumOfSquares . . . . . . . . . . . . . . 17 85 4. Modification of Existing Information Elements Related to 86 Packet Section . . . . . . . . . . . . . . . . . . . . . . . 17 87 4.1. ipHeaderPacketSection . . . . . . . . . . . . . . . . . . 18 88 4.2. ipPayloadPacketSection . . . . . . . . . . . . . . . . . 18 89 4.3. mplsLabelStackSection . . . . . . . . . . . . . . . . . . 19 90 4.4. mplsPayloadPacketSection . . . . . . . . . . . . . . . . 20 91 5. Modification of Existing Information Elements Related to VLAN 92 Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 93 5.1. dot1qVlanId . . . . . . . . . . . . . . . . . . . . . . . 22 94 5.2. dot1qPriority . . . . . . . . . . . . . . . . . . . . . . 22 95 5.3. dot1qCustomerVlanId . . . . . . . . . . . . . . . . . . . 23 96 5.4. dot1qCustomerPriority . . . . . . . . . . . . . . . . . . 23 97 6. The relationship between Ethernet header fields and 98 Information Elements . . . . . . . . . . . . . . . . . . . . 24 99 7. Security Considerations . . . . . . . . . . . . . . . . . . . 25 100 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 101 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25 102 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 103 10.1. Normative References . . . . . . . . . . . . . . . . . . 25 104 10.2. Informative References . . . . . . . . . . . . . . . . . 27 105 Appendix A. Tagged Frame Formats . . . . . . . . . . . . . . . . 27 106 Appendix B. Template Formats Example . . . . . . . . . . . . . . 32 107 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 109 1. Introduction 111 Ethernet [IEEE802.1D] and VLAN (Virtual LAN) technologies had been 112 used only in Local Area Networks. Recently, they have been used in 113 Wide Area Networks, e.g., L2-VPN services. Accordingly, the carrier 114 networks using the VLAN technologies have been enhanced to Provider 115 Bridged Network and Provider Backbone Bridged Networks [IEEE802.1Q]. 116 And, Ethernet in data center also has been enhanced for server 117 virtualization and I/O consolidation. 119 While these innovations provide flexibility, scalability, and 120 mobility to an existing network architecture, it increases the 121 complexity of traffic measurement due to the existence of various 122 Ethernet header formats. To cope with this, a more sophisticated 123 method is required. 125 IPFIX and PSAMP helps to resolve these problems. However, the PSAMP 126 Information Model [RFC5477] and the IPFIX Information Model [RFC7011] 127 are not yet enough for Information Elements related to data link 128 layer, e.g., Ethernet header forms. This document describes the 129 Information Elements related to data link layers that enable a more 130 sophisticated traffic measurement method. 132 1.1. Conventions Used in This Document 134 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 135 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 136 document are to be interpreted as described in RFC 2119 [RFC2119]. 138 2. Extended Ethernet Technology 140 2.1. Wide-Area Ethernet Technology Summary 142 Provider Bridge and Provider Backbone Bridge [IEEE802.1Q], which are 143 standards for the Wide-Area Ethernet, are described below. 145 o In Provider Bridge [IEEE802.1Q], there are two VLAN IDs: Service 146 VLAN Identifier (S-VID) and Customer VLAN Identifier (C-VID). 147 S-VID is assigned to an Ethernet frame by a service provider, 148 while C-VID is independently assigned to an Ethernet frame by a 149 customer. Frame switching in a service provider network is based 150 on only S-VID. 152 o In Provider Backbone Bridge [IEEE802.1Q], new Ethernet fields, 153 such as Backbone VLAN Identifier (B-VID) and Backbone Service 154 Instance Identifier (I-SID), are introduced to overcome the 155 limitations on the VLAN identifier space and to isolate the 156 service provider and customer identifier spaces. Frame switching 157 is based on a 12-bit B-VID, and customer identification is based 158 on a 24-bit I-SID. A flexible network design has become possible 159 because network management is separated from customer management. 160 Other Ethernet fields that indicate quality of service (QoS) class 161 are Backbone VLAN priority code point (B-PCP), Backbone VLAN drop 162 eligible indicator (B-DEI), Backbone Service Instance priority 163 code point (I-PCP), and Backbone Service Instance Drop Eligibility 164 Indicator (I-DEI). 166 The Provider Backbone Bridge technologies have enhanced a wide-area 167 Ethernet service from a flat network to a hierarchical network 168 consisting of Provider Bridge Network and Provider Backbone Bridge 169 Network. 171 Frame formats used in Wide-Area Ethernet are shown in Appendix A. 173 2.2. Virtual Ethernet Technology Summary 175 There have been several challenges in the existing virtual switches 176 environment in a data center. One is the lack of network management 177 visiblity. The limited feature on the virtual switch makes difficult 178 to monitor traffic among virtual machines (VMs). Second is the lack 179 of management scalability and flexibility. Increasing the number of 180 VMs for multi-tenant causes the increase of the number of virtual 181 switches and of the number of the traffic control policies. This 182 reaches the limitation of network management scalability and 183 flexibility. 185 In this situation, IEEE 802.1 Working Group is standardizing virtual 186 bridging technologies as Edge Virtual Bridge (EVB) including two 187 kinds of Edge Relay (ER): Virtual Edge Bridge (VEB) and Virtual Edge 188 Port Aggregator (VEPA) [IEEE802.1Qbg]. The VEB is a bridge that 189 provides a bridging among multiple VMs and the external bridging 190 environment. The VEPA is a bridge-like device on a host that 191 forwards all internal traffic to the adjacent EVB bridge and then 192 distributes any traffic received from the adjacent EVB bridge to VMs. 193 The VEPA makes all the VM-to-VM traffic visible to EVB bridge so that 194 the traffic can be monitored and so the EVB bridge can apply 195 filtering to the traffic. 197 To improve flexibility, a virtual link between a host system and EVB 198 bridge is standardized as S-channel. S-channel allows a bridge to 199 treat the traffic in the virtual link as if it comes in on a separate 200 port. For example, in the host, an S-channel may be attached to a 201 VEB or a VEPA or directly an internal port in order to apply each 202 port-based filtering rules to the traffic. S-channel over the link 203 between a host and its adjacent bridge uses S-TAG [IEEE802.1Q]. When 204 S-channel is in use, frames on the link carry an S-TAG to identify 205 the S-channel. 207 On the other hand, Bridge Port Extension emulates single Extended 208 Bridge from multiple physical switches and virtual switches, and 209 simplifies network management. Also, it solves the lack of network 210 management visiblity by forwarding all traffic into a central 211 Controlling Bridge using E-channel. E-channel over the link between 212 a Bridge Port extender and a Controlling Bridge uses E-TAG defined in 213 [IEEE802.1BR]. 215 The traffic monitoring over S-channel and E-channel is required in 216 order to get the visiblity of VM-to-VM traffic, and the visiblity of 217 each channel traffic on a virtual link. 219 Frame formats with E-TAG used in E-channel and S-TAG used in 220 S-channel are shown in Appendix A. Though these frames carry special 221 tags while on the link, those tags identify a virtual port (or for 222 multicast in the downstream direction, a set of virtual ports) to 223 which they are destined. These tag values only have local meaning 224 and the flow would be reported as sent and arriving on the 225 corresponding virtual ports. Therefore, IPFIX does not need to 226 monitor data based on these tags. 228 3. Information Elements Related to Link Frame Section 230 The following Information Elements whose ElementId are from 312 to 231 TBD03 are necessary for enabling the IPFIX and PSAMP traffic 232 measurement for data link layer, which is not limited to Ethernet 233 because the method can be applied to other data link protocols as 234 well. 236 The following Information Elements whose ElementId are from TBD05 to 237 TBD09 are necessary for enabling the IPFIX and PSAMP traffic 238 measurement for [IEEE802.1Q]. 240 The following Information Elements whose ElementId are from TBD12 to 241 TBD25 are octet counter or packet length for layer 2, and are 242 necessary for enabling the IPFIX and PSAMP traffic measurement for 243 data link layer. 245 +-----+------------------------------------+ 246 | ID | Name | 247 +-----+------------------------------------+ 248 | 312 | dataLinkFrameSize | 249 | 315 | dataLinkFrameSection | 250 |TBD01| dataLinkFrameType | 251 |TBD02| sectionOffset | 252 |TBD03| sectionExportedOctets | 253 |TBD05| dot1qServiceInstanceTag | 254 |TBD06| dot1qServiceInstanceId | 255 |TBD07| dot1qServiceInstancePriority | 256 |TBD08| dot1qCustomerDestinationMacAddress | 257 |TBD09| dot1qCustomerSourceMacAddress | 258 |TBD12| l2OctetDeltaCount | 259 |TBD13| postMCastL2OctetDeltaCount | 260 |TBD14| postL2OctetDeltaCount | 261 |TBD15| minimumL2TotalLength | 262 |TBD16| maximumL2TotalLength | 263 |TBD17| l2OctetTotalCount | 264 |TBD18| droppedL2OctetDeltaCount | 265 |TBD19| droppedL2OctetTotalCount | 266 |TBD20| ignoredL2OctetTotalCount | 267 |TBD21| notSentL2OctetTotalCount | 268 |TBD22| postL2OctetTotalCount | 269 |TBD23| postMCastL2OctetTotalCount | 270 |TBD24| l2OctetDeltaSumOfSquares | 271 |TBD25| l2OctetTotalSumOfSquares | 272 +-----+------------------------------------+ 274 Table 1: Information Elements related to link frame section 276 3.1. Existing Information Elements 278 3.1.1. dataLinkFrameSize 280 Description: 282 This Information Element specifies the length of the selected data 283 link frame. 285 The data link layer is defined in [ISO_IEC.7498-1_1994]. 287 Abstract Data Type: unsigned16 289 Data Type Semantics: quantity 291 ElementId: 312 293 Status: current 295 3.1.2. dataLinkFrameSection 297 Description: 299 This Information Element carries n octets from the data link frame 300 of a selected frame, starting sectionOffset octets into the frame. 302 When the sectionOffset field corresponding to this Information 303 Element does not exist, starting point should be the head of the 304 data link frame. 306 The sectionExportedOctets expresses how much data was observed, 307 while the remainder is padding. 309 When the sectionExportedOctets field corresponding to this 310 Information Element exists, this Information Element MAY have a 311 fixed length and MAY be padded, or MAY have a variable length. 313 When the sectionExportedOctets field corresponding to this 314 Information Element does not exist, this Information Element 315 SHOULD have a variable length and MUST NOT be padded. In this 316 case, the size of the exported section may be constrained due to 317 limitations in the IPFIX protocol. 319 Further Information Elements, i.e., dataLinkFrameType and 320 dataLinkFrameSize are needed to specify the data link type and the 321 size of the data link frame of this Information Element. A set of 322 these Information Elements MAY be contained in a structured data 323 type, as expressed in [RFC6313]. Or a set of these Information 324 Elements MAY be contained in one Flow Record as shown in 325 Appendix B. 327 The data link layer is defined in [ISO_IEC.7498-1_1994]. 329 Abstract Data Type: octetArray 331 ElementId: 315 333 Status: current 335 3.2. New Information Elements 337 3.2.1. dataLinkFrameType 339 Description: 341 This Information Element specifies the type of the selected data 342 link frame. 344 The following data link types are defined here. 346 - 0x01 IEEE802.3 ETHERNET [IEEE802.3] 348 - 0x02 IEEE802.11 MAC Frame format [IEEE802.11] 350 Further values may be assigned by IANA. 352 The data link layer is defined in [ISO_IEC.7498-1_1994]. 354 Abstract Data Type: unsigned16 356 Data Type Semantics: identifier 358 ElementId: TBD01 360 Status: current 362 3.2.2. sectionOffset 364 Description: 366 This Information Element specifies the offset of the packet 367 section (e.g., dataLinkFrameSection, ipHeaderPacketSection, 368 ipPayloadPacketSection, mplsLabelStackSection and 369 mplsPayloadPacketSection). If this Information Element is 370 omitted, it defaults to zero (ie, no offset). 372 If multiple sectionOffset IEs are specified within a single 373 Template, then they apply to the packet section IEs in order. ie, 374 the first sectionOffset applies to the first packet section, etc. 375 Note that the "closest" sectionOffset and packet section IEs 376 within a given Template are not necessarily related. If there are 377 less sectionOffset IEs than packet section IEs, then subsequent 378 packet section IEs have no offset. If there are more 379 sectionOffset IEs than the number of packet section IEs, then the 380 additional sectionOffset IEs are meaningless. 382 Abstract Data Type: unsigned16 384 Data Type Semantics: quantity 386 ElementId: TBD02 388 Status: current 390 3.2.3. sectionExportedOctets 392 Description: 394 This Information Element specifies the observed length of the 395 packet section (e.g., dataLinkFrameSection, ipHeaderPacketSection, 396 ipPayloadPacketSection, mplsLabelStackSection and 397 mplsPayloadPacketSection) when padding is used. 399 The packet section may be of a fixed size larger than the 400 sectionExportedOctets. In this case, octets in the packet section 401 beyond the sectionExportedOctets MUST follow the [RFC7011] rules 402 for padding (ie, be composed of zero (0) valued octets). 404 Abstract Data Type: unsigned16 406 Data Type Semantics: quantity 408 ElementId: TBD03 410 Status: current 412 3.2.4. dot1qServiceInstanceTag 414 Description: 416 This Information Element, which is 16 octets long, represents the 417 Backbone Service Instance Tag (I-TAG) Tag Control Information 418 (TCI) field of an Ethernet frame as described in [IEEE802.1Q]. It 419 encodes the Backbone Service Instance Priority Code Point (I-PCP), 420 Drop Eligible Indicator (I-DEI), Use Customer Addresses (UCA), 421 Backbone Service Instance Identifier (I-SID), Encapsulated 422 Customer Destination Address (C-DA), Encapsulated Customer Source 423 Address (C-SA) and reserved fields. The structure and semantics 424 within the Tag Control Information field are defined in 425 [IEEE802.1Q]. 427 Abstract Data Type: octetArray 429 Data Type Semantics: identifier 431 ElementId: TBD05 433 Status: current 435 3.2.5. dot1qServiceInstanceId 437 Description: 439 The value of the 24-bit Backbone Service Instance Identifier 440 (I-SID) portion of the Backbone Service Instance Tag (I-TAG) Tag 441 Control Information (TCI) field of an Ethernet frame as described 442 in [IEEE802.1Q]. 444 Abstract Data Type: unsigned32 446 Data Type Semantics: identifier 448 ElementId: TBD06 450 Status: current 452 3.2.6. 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 [IEEE802.1Q]. 461 Abstract Data Type: unsigned8 463 Data Type Semantics: identifier 465 ElementId: TBD07 467 Status: current 469 3.2.7. dot1qCustomerDestinationMacAddress 471 Description: 473 The value of the Encapsulated Customer Destination Address (C-DA) 474 portion of the Backbone Service Instance Tag (I-TAG) Tag Control 475 Information (TCI) field of an Ethernet frame as described in 476 [IEEE802.1Q]. 478 Abstract Data Type: macAddress 480 Data Type Semantics: identifier 482 ElementId: TBD08 484 Status: current 486 3.2.8. dot1qCustomerSourceMacAddress 488 Description: 490 The value of the Encapsulated Customer Source Address (C-SA) 491 portion of the Backbone Service Instance Tag (I-TAG) Tag Control 492 Information (TCI) field of an Ethernet frame as described in 493 [IEEE802.1Q]. 495 Abstract Data Type: macAddress 497 Data Type Semantics: identifier 499 ElementId: TBD09 501 Status: current 503 3.2.9. l2OctetDeltaCount 505 Description: 507 The number of layer 2 octets since the previous report (if any) in 508 incoming packets for this Flow at the Observation Point. The 509 number of octets includes layer 2 header(s) and layer 2 payload. 511 The Information Element is layer 2 version of octetDeltaCount 512 (ElementId #1) in [RFC5477]. 514 Abstract Data Type: unsigned64 516 Data Type Semantics: deltaCounter 517 ElementId: TBD12 519 Status: current 521 Units: octets 523 3.2.10. postMCastL2OctetDeltaCount 525 Description: 527 The number of layer 2 octets since the previous report (if any) in 528 outgoing multicast packets sent for packets of this Flow by a 529 multicast daemon within the Observation Domain. This property 530 cannot necessarily be observed at the Observation Point, but may 531 be retrieved by other means. The number of octets includes layer 532 2 header(s) and layer 2 payload. 534 The Information Element is layer 2 version of 535 postMCastOctetDeltaCount (ElementId #20) in [RFC5477]. 537 Abstract Data Type: unsigned64 539 Data Type Semantics: deltaCounter 541 ElementId: TBD13 543 Status: current 545 Units: octets 547 3.2.11. postL2OctetDeltaCount 549 Description: 551 The definition of this Information Element is identical to the 552 definition of Information Element 'l2OctetDeltaCount', except that 553 it reports a potentially modified value caused by a middlebox 554 function after the packet passed the Observation Point. 556 The Information Element is layer 2 version of postOctetDeltaCount 557 (ElementId #23) in [RFC5477]. 559 Abstract Data Type: unsigned64 561 Data Type Semantics: deltaCounter 563 ElementId: TBD14 564 Status: current 566 Units: octets 568 3.2.12. minimumL2TotalLength 570 Description: 572 Layer 2 length of the smallest packet observed for this Flow. The 573 packet length includes the layer 2 header(s) length and the layer 574 2 payload length. 576 The Information Element is layer 2 version of minimumIpTotalLength 577 (ElementId #25) in [RFC5477]. 579 Abstract Data Type: unsigned64 581 ElementId: TBD15 583 Status: current 585 Units: octets 587 3.2.13. maximumL2TotalLength 589 Description: 591 Layer 2 length of the largest packet observed for this Flow. The 592 packet length includes the layer 2 header(s) length and the layer 593 2 payload length. 595 The Information Element is layer 2 version of maximumIpTotalLength 596 (ElementId #26) in [RFC5477]. 598 Abstract Data Type: unsigned64 600 ElementId: TBD16 602 Status: current 604 Units: octets 606 3.2.14. l2OctetTotalCount 608 Description: 610 The total number of layer 2 octets in incoming packets for this 611 Flow at the Observation Point since the Metering Process 612 (re-)initialization for this Observation Point. The number of 613 octets includes layer 2 header(s) and layer 2 payload. 615 The Information Element is layer 2 version of octetTotalCount 616 (ElementId #85) in [RFC5477]. 618 Abstract Data Type: unsigned64 620 Data Type Semantics: totalCounter 622 ElementId: TBD17 624 Status: current 626 Units: octets 628 3.2.15. droppedL2OctetDeltaCount 630 Description: 632 The number of layer 2 octets since the previous report (if any) in 633 packets of this Flow dropped by packet treatment. The number of 634 octets includes layer 2 header(s) and layer 2payload. 636 The Information Element is layer 2 version of 637 droppedOctetDeltaCount (ElementId #132) in [RFC5477]. 639 Abstract Data Type: unsigned64 641 Data Type Semantics: deltaCounter 643 ElementId: TBD18 645 Status: current 647 Units: octets 649 3.2.16. droppedL2OctetTotalCount 651 Description: 653 The number of layer 2 octets since the previous report (if any) in 654 packets of this Flow dropped by packet treatment. The number of 655 octets includes layer 2 header(s) and layer 2 payload. 657 The Information Element is layer 2 version of 658 droppedOctetTotalCount (ElementId #134) in [RFC5477]. 660 Abstract Data Type: unsigned64 662 Data Type Semantics: totalCounter 664 ElementId: TBD19 666 Status: current 668 Units: octets 670 3.2.17. ignoredL2OctetTotalCount 672 Description: 674 The total number of octets in observed layer 2 packets (including 675 the layer 2 header) that the Metering Process did not process 676 since the (re-)initialization of the Metering Process. 678 The Information Element is layer 2 version of 679 ignoredOctetTotalCount (ElementId #165) in [RFC5477]. 681 Abstract Data Type: unsigned64 683 Data Type Semantics: totalCounter 685 ElementId: TBD20 687 Status: current 689 Units: octets 691 3.2.18. notSentL2OctetTotalCount 693 Description: 695 The total number of octets in observed layer 2 packets (including 696 the layer 2 header) that the Metering Process did not process 697 since the (re-)initialization of the Metering Process. 699 The Information Element is layer 2 version of 700 notSentOctetTotalCount (ElementId #168) in [RFC5477]. 702 Abstract Data Type: unsigned64 704 Data Type Semantics: totalCounter 706 ElementId: TBD21 707 Status: current 709 Units: octets 711 3.2.19. postL2OctetTotalCount 713 Description: 715 The definition of this Information Element is identical to the 716 definition of Information Element 'l2OctetTotalCount', except that 717 it reports a potentially modified value caused by a middlebox 718 function after the packet passed the Observation Point. 720 The Information Element is layer 2 version of postOctetTotalCount 721 (ElementId #171) in [RFC5477]. 723 Abstract Data Type: unsigned64 725 Data Type Semantics: totalCounter 727 ElementId: TBD22 729 Status: current 731 Units: octets 733 3.2.20. postMCastL2OctetTotalCount 735 Description: 737 The total number of layer 2 octets in outgoing multicast packets 738 sent for packets of this Flow by a multicast daemon in the 739 Observation Domain since the Metering Process (re-)initialization. 740 This property cannot necessarily be observed at the Observation 741 Point, but may be retrieved by other means. The number of octets 742 includes layer 2 header(s) and layer 2 payload. 744 The Information Element is layer 2 version of 745 postMCastOctetTotalCount (ElementId #175) in [RFC5477]. 747 Abstract Data Type: unsigned64 749 Data Type Semantics: totalCounter 751 ElementId: TBD23 753 Status: current 754 Units: octets 756 3.2.21. l2OctetDeltaSumOfSquares 758 Description: 760 The sum of the squared numbers of layer 2 octets per incoming 761 packet since the previous report (if any) for this Flow at the 762 Observation Point. The number of octets includes layer 2 763 header(s) and layer 2 payload. 765 The Information Element is layer 2 version of 766 octetDeltaSumOfSquares (ElementId #198) in [RFC5477]. 768 Abstract Data Type: unsigned64 770 Data Type Semantics: deltaCounter 772 ElementId: TBD24 774 Status: current 776 Units: octets 778 3.2.22. l2OctetTotalSumOfSquares 780 Description: 782 The total sum of the squared numbers of layer 2 octets in incoming 783 packets for this Flow at the Observation Point since the Metering 784 Process (re-)initialization for this Observation Point. The 785 number of octets includes layer 2 header(s) and layer 2 payload. 787 The Information Element is layer 2 version of 788 octetTotalSumOfSquares (ElementId #199) in [RFC5477]. 790 Abstract Data Type: unsigned64 792 Data Type Semantics: totalCounter 794 ElementId: TBD25 796 Status: current 798 Units: octets 800 4. Modification of Existing Information Elements Related to Packet 801 Section 803 New Information Elements related to packet section (ie, sectionOffset 804 and sectionExportedOctets) can be applied to not only 805 dataLinkFrameSection but also all kinds of packet section (ie, 806 ipHeaderPacketSection, ipPayloadPacketSection, mplsLabelStackSection, 807 and mplsPayloadPacketSection defined in [RFC5477]). In this case, 808 existing Information Elements Description should be modified as 809 follows: 811 4.1. ipHeaderPacketSection 813 Description: 815 This Information Element carries a series of n octets from the IP 816 header of a sampled packet, starting sectionOffset octets into the 817 IP header. 819 When the sectionOffset field corresponding to this Information 820 Element does not exist, starting point should be the head of the 821 IP header. 823 The Information Element is defined in [RFC5477]. The description 824 is updated from [RFC5477]. 826 With sufficient length, this element also reports octets from the 827 IP payload, subject to [RFC2804]. See the Security Considerations 828 section in [RFC5477]. 830 The sectionExportedOctets expresses how much data was exported, 831 while the remainder is padding. 833 When the sectionExportedOctets field corresponding to this 834 Information Element exists, this Information Element MAY have a 835 fixed length and MAY be padded, or MAY have a variable length. 837 When the sectionExportedOctets field corresponding to this 838 Information Element does not exist, this Information Element 839 SHOULD have a variable length and MUST NOT be padded. In this 840 case, the size of the exported section may be constrained due to 841 limitations in the IPFIX protocol. 843 Abstract Data Type: octetArray 845 ElementId: 313 847 Status: current 849 4.2. ipPayloadPacketSection 850 Description: 852 This Information Element carries a series of n octets from the IP 853 payload of a sampled packet, starting sectionOffset octets into 854 the IP payload. 856 When the sectionOffset field corresponding to this Information 857 Element does not exist, starting point should be the head of the 858 IP payload. 860 The Information Element is defined in [RFC5477]. The description 861 is updated from [RFC5477]. 863 The IPv4 payload is that part of the packet that follows the IPv4 864 header and any options, which [RFC0791] refers to as "data" or 865 "data octets". For example, see the examples in [RFC0791], 866 Appendix A. 868 The IPv6 payload is the rest of the packet following the 40-octet 869 IPv6 header. Note that any extension headers present are 870 considered part of the payload. See [RFC2460] for the IPv6 871 specification. 873 The sectionExportedOctets expresses how much data was observed, 874 while the remainder is padding. 876 When the sectionExportedOctets field corresponding to this 877 Information Element exists, this Information Element MAY have a 878 fixed length and MAY be padded, or MAY have a variable length. 880 When the sectionExportedOctets field corresponding to this 881 Information Element does not exist, this Information Element 882 SHOULD have a variable length and MUST NOT be padded. In this 883 case, the size of the exported section may be constrained due to 884 limitations in the IPFIX protocol. 886 Abstract Data Type: octetArray 888 ElementId: 314 890 Status: current 892 4.3. mplsLabelStackSection 894 Description: 896 This Information Element carries a series of n octets from the 897 MPLS label stack of a sampled packet, starting sectionOffset 898 octets into the MPLS label stack. 900 When the sectionOffset field corresponding to this Information 901 Element does not exist, starting point should be the head of the 902 MPLS label stack. 904 The Information Element is defined in [RFC5477]. The description 905 is updated from [RFC5477]. 907 With sufficient length, this element also reports octets from the 908 MPLS payload, subject to [RFC2804]. See the Security 909 Considerations section in [RFC5477]. 911 See [RFC3031] for the specification of MPLS packets. 913 See [RFC3032] for the specification of the MPLS label stack. 915 The sectionExportedOctets expresses how much data was observed, 916 while the remainder is padding. 918 When the sectionExportedOctets field corresponding to this 919 Information Element exists, this Information Element MAY have a 920 fixed length and MAY be padded, or MAY have a variable length. 922 When the sectionExportedOctets field corresponding to this 923 Information Element does not exist, this Information Element 924 SHOULD have a variable length and MUST NOT be padded. In this 925 case, the size of the exported section may be constrained due to 926 limitations in the IPFIX protocol. 928 Abstract Data Type: octetArray 930 ElementId: 316 932 Status: current 934 4.4. mplsPayloadPacketSection 936 Description: 938 This Information Element carries a series of n octets from the 939 MPLS payload of a sampled packet, starting sectionOffset octets 940 into the MPLS payload, being data that follows immediately after 941 the MPLS label stack. 943 When the sectionOffset field corresponding to this Information 944 Element does not exist, starting point should be the head of the 945 MPLS payload. 947 The Information Element is defined in [RFC5477]. The description 948 is updated from [RFC5477]. 950 See [RFC3031] for the specification of MPLS packets. 952 See [RFC3032] for the specification of the MPLS label stack. 954 The sectionExportedOctets expresses how much data was observed, 955 while the remainder is padding. 957 When the sectionExportedOctets field corresponding to this 958 Information Element exists, this Information Element MAY have a 959 fixed length and MAY be padded, or MAY have a variable length. 961 When the sectionExportedOctets field corresponding to this 962 Information Element does not exist, this Information Element 963 SHOULD have a variable length and MUST NOT be padded. In this 964 case, the size of the exported section may be constrained due to 965 limitations in the IPFIX protocol. 967 Abstract Data Type: octetArray 969 ElementId: 317 971 Status: current 973 5. Modification of Existing Information Elements Related to VLAN Tag 975 The traffic measurement using IPFIX and PSAMP for a Provider Backbone 976 Bridged Network requires the Information Elements related to Backbone 977 Service Instance Tag (I-TAG) and Backbone VLAN Tag (B-TAG). The set 978 of Information Elements related to I-TAG is added in section 3, 979 becasue I-TAG structure and semantics are different from that of 980 Service VLAN Tag (S-TAG) and Customer VLAN Tag (C-TAG). The set of 981 Information Elements related to B-TAG reuses the existing Information 982 Elements, because B-TAG structure and semantics are identical to that 983 of C-TAG and S-TAG. This section modifies existing Descriptions and 984 Reference related to C-TAG and S-TAG as follows: 986 5.1. dot1qVlanId 988 Description: 990 The value of the 12-bit VLAN Identifier portion of the Tag Control 991 Information field of an Ethernet frame. The structure and 992 semantics within the Tag Control Information field are defined in 993 [IEEE802.1Q]. In Provider Bridged Networks, it represents the 994 Service VLAN identifier in the S-TAG Tag Control Information (TCI) 995 field or the Customer VLAN identifier in the C-TAG Tag Control 996 Information (TCI) field as described in [IEEE802.1Q]. In Provider 997 Backbone Bridged Networks, it represents the Backbone VLAN 998 identifier in the B-TAG Tag Control Information (TCI) field as 999 described in [IEEE802.1Q]. In a virtual link between a host 1000 system and EVB bridge, it represents the Service VLAN identifier 1001 indicating S-channel as described in [IEEE802.1Qbg]. 1003 In the case of multi-tagged frame, it represents the outer tag's 1004 VLAN identifier except for I-TAG. 1006 Abstract Data Type: unsigned16 1008 Data Type Semantics: identifier 1010 ElementId: 243 1012 Status: current 1014 Reference: 1016 (1) [IEEE802.1Q] 1018 (2) [IEEE802.1Qbg] 1020 5.2. dot1qPriority 1022 Description: 1024 The value of the 3-bit User Priority portion of the Tag Control 1025 Information field of an Ethernet frame. The structure and 1026 semantics within the Tag Control Information field are defined in 1027 [IEEE802.1Q]. In the case of multi-tagged frame, it represents 1028 the 3-bit Priority Code Point (PCP) portion of the outer tag's Tag 1029 Control Information (TCI) field as described in [IEEE802.1Q] 1030 except for I-TAG. 1032 Abstract Data Type: unsigned8 1033 Data Type Semantics: identifier 1035 ElementId: 244 1037 Status: current 1039 Reference: 1041 (1) [IEEE802.1Q] 1043 5.3. dot1qCustomerVlanId 1045 Description: 1047 The value represents the Customer VLAN identifier in the C-TAG Tag 1048 Control Information (TCI) field as described in [IEEE802.1Q]. 1050 Abstract Data Type: unsigned16 1052 Data Type Semantics: identifier 1054 ElementId: 245 1056 Status: current 1058 Reference: 1060 (1) [IEEE802.1Q] 1062 5.4. dot1qCustomerPriority 1064 Description: 1066 The value represents the 3-bit Priority Code Point (PCP) portion 1067 of the C-TAG Tag Control Information (TCI) field as described in 1068 [IEEE802.1Q]. 1070 Abstract Data Type: unsigned8 1072 Data Type Semantics: identifier 1074 ElementId: 246 1076 Status: current 1078 Reference: 1080 (1) [IEEE802.1Q] 1082 6. The relationship between Ethernet header fields and Information 1083 Elements 1085 The following figures shows summary of various Ethernet header fields 1086 and the Informational Elements which would be used to represent each 1087 of the fields. 1089 <----6----><----6----><----4----><------2------> 1090 +----------+----------+----------+--------------+ 1091 + + + + + 1092 + C-DA + C-SA + C-TAG + Length/Type + 1093 + a + b + c + d + 1094 +----------+----------+----------+--------------+ 1096 a.(Information Element) destinationMacAddress 80 1097 b.(Information Element) sourceMacAddress 56 1098 c.(Information Elements) dot1qVlanId 243, dot1qPriority 244 1099 d.(Information Element) ethernetType 256 1101 Figure 1: Customer tagged frame header fields 1103 <----6----><----6----><----4----><----4----><------2------> 1104 +----------+----------+----------+----------+--------------+ 1105 + + + + + + 1106 + C-DA + C-SA + S-TAG + C-TAG + Length/Type + 1107 + a + b + c + d + e + 1108 +----------+----------+----------+----------+--------------+ 1110 a.(Information Element) destinationMacAddress 80 1111 b.(Information Element) sourceMacAddress 56 1112 c.(Information Elements) dot1qVlanId 243, dot1qPriority 244 1113 d.(Information Elements) dot1qCustomerVlanId 245, 1114 dot1qCustomerPriority 246 1115 e.(Information Element) ethernetType 256 1117 Figure 2: Service tagged frame header fields 1119 <----6----><----6----><----4----><------16------><----4----><------2------> 1120 +----------+----------+----------+---------------+----------+--------------+ 1121 + + + + + + + 1122 + B-DA + B-SA + B-TAG + I-TAG + C-TAG + Length/Type + 1123 + a + b + c + d + e + f + 1124 +----------+----------+----------+---------------+----------+--------------+ 1125 a.(Information Element) destinationMacAddress 80 1126 b.(Information Element) sourceMacAddress 56 1127 c.(Information Elements) dot1qVlanId 243, dot1qPriority 244 1128 d.(Information Elements) dot1qServiceInstanceTag TBD05, or 1129 a set of dot1qServiceInstanceId TBD06, 1130 dot1qServiceInstancePriority TBD07, 1131 dot1qCustomerDestinationMacAddress TBD08, 1132 dot1qCustomerSourceMacAddress TBD09 1133 e.(Information Elements) dot1qCustomerVlanId 245, 1134 dot1qCustomerPriority 246 1135 f.(Information Element) ethernetType 256 1137 Figure 3: Backbone VLAN tagged frame header fields 1139 7. Security Considerations 1141 The recommendations in this document do not introduce any additional 1142 security issues to those already mentioned in [RFC7011] and 1143 [RFC5477]. 1145 8. IANA Considerations 1147 This document requests that the Information Element IDs are allocated 1148 as shown in section 3 1150 And this document requests that the existing Information Element 1151 Description are modified as shown in section 4 and 5 1153 9. Acknowledgments 1155 Thanks to Brian Trammell and IPFIX members who contributed to 1156 mailing-list discussions throughout the development of this document, 1157 and especially to Pat Thaler for her help with the IEEE 802 aspects 1158 of this work. 1160 10. References 1162 10.1. Normative References 1164 [IEEE802.11] 1165 IEEE Computer Society, "IEEE Standard for Information 1166 technology. Telecommunications and information exchange 1167 between systems Local and metropolitan area networks. 1168 Specific requirements Part 11: Wireless LAN Medium Access 1169 Control (MAC) and Physical Layer (PHY) Specifications ", 1170 IEEE Std 802.11-2012, March 2012. 1172 [IEEE802.1BR] 1173 IEEE Computer Society, "IEEE Standard for Local and 1174 metropolitan area networks: Virtual Bridged Local Area 1175 Networks: Bridge Port Extension ", IEEE Std 802.1BR-2012, 1176 July 2012. 1178 [IEEE802.1Q] 1179 IEEE Computer Society, "IEEE Standard for Local and 1180 metropolitan area networks: Media Access Control (MAC) 1181 Bridges and Virtual Bridged Local Area Networks ", IEEE 1182 Std 802.1Q-2011, August 2011. 1184 [IEEE802.1Qbg] 1185 IEEE Computer Society, "IEEE Standard for Local and 1186 metropolitan area networks: Media Access Control (MAC) 1187 Bridges and Virtual Bridged Local Area Networks: Amendment 1188 21: Edge Virtual Bridging ", IEEE Std 802.1Qbg-2012, July 1189 2012. 1191 [IEEE802.3] 1192 IEEE Computer Society, "IEEE Standard for Ethernet ", IEEE 1193 Std 802.3-2012, December 2012. 1195 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1196 1981. 1198 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1199 Requirement Levels", BCP 14, RFC 2119, March 1997. 1201 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 1202 (IPv6) Specification", RFC 2460, December 1998. 1204 [RFC2804] IAB IESG, "IETF Policy on Wiretapping", RFC 2804, May 1205 2000. 1207 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 1208 Label Switching Architecture", RFC 3031, January 2001. 1210 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 1211 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack 1212 Encoding", RFC 3032, January 2001. 1214 [RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G. 1215 Carle, "Information Model for Packet Sampling Exports", 1216 RFC 5477, March 2009. 1218 [RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates, 1219 "Export of Structured Data in IP Flow Information Export 1220 (IPFIX)", RFC 6313, July 2011. 1222 [RFC7011] Claise, B., Trammell, B., and P. Aitken, "Specification of 1223 the IP Flow Information Export (IPFIX) Protocol for the 1224 Exchange of Flow Information", STD 77, RFC 7011, September 1225 2013. 1227 10.2. Informative References 1229 [IEEE802.1D] 1230 IEEE Computer Society, "IEEE Standard for Local and 1231 metropolitan area networks: Media Access Control (MAC) 1232 Bridges", IEEE Std 802.1D-2004, June 2004. 1234 [ISO_IEC.7498-1_1994] 1235 International Organization for Standardization, 1236 "Information technology -- Open Systems Interconnection -- 1237 Basic Reference Model: The Basic Mode", ISO Standard 1238 7498-1:1994, June 1996. 1240 Appendix A. Tagged Frame Formats 1242 0 1 2 3 1243 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 1244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1245 | C-DA | 1246 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1247 | | | 1248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1249 | C-SA | 1250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1251 | Length/Type | | 1252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1253 | | 1254 ~ Customer Data ~ 1255 ~ ~ 1256 | | 1257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1259 Figure A-1: Untagged frame format 1261 0 1 2 3 1262 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 1263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1264 | C-DA | 1265 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1266 | | | 1267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1268 | C-SA | 1269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1270 | C-TAG TPID=0x8100 |C-PCP|C| C-VID | 1271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1272 | Length/Type | | 1273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1274 | | 1275 ~ Customer Data ~ 1276 ~ ~ 1277 | | 1278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1280 Figure A-2: C-TAG tagging frame format 1282 0 1 2 3 1283 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 1284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1285 | C-DA | 1286 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1287 | | | 1288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1289 | C-SA | 1290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1291 | S-TAG TPID=0x88a8 |S-PCP|D| S-VID | 1292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1293 | Length/Type | | 1294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1295 | | 1296 ~ Customer Data ~ 1297 ~ ~ 1298 | | 1299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1301 Figure A-3: S-TAG tagging frame format in Provider Bridged Networks 1303 0 1 2 3 1304 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 1305 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1306 | C-DA | 1307 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1308 | | | 1309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1310 | C-SA | 1311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1312 | S-TAG TPID=0x88a8 |S-PCP|D| S-VID | 1313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1314 | C-TAG TPID=0x8100 |C-PCP|C| C-VID | 1315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1316 | Length/Type | | 1317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1318 | | 1319 ~ Customer Data ~ 1320 ~ ~ 1321 | | 1322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1324 Figure A-4: S-TAG and C-TAG tagging frame format in Provider Bridged 1325 Networks 1327 0 1 2 3 1328 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 1329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1330 | B-DA | 1331 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1332 | | | 1333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1334 | B-SA | 1335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1336 | B-TAG TPID=0x88a8 |B-PCP|D| B-VID | 1337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1338 | I-TAG TPID=0x88e7 |I-PCP|D|U| Res | I-SID | 1339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1340 | I-SID | | 1341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1342 | C-DA | 1343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1344 | C-SA | 1345 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1346 | | Length/Type | 1347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1348 | | 1349 ~ Customer Data ~ 1350 ~ ~ 1351 | | 1352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1354 Figure A-5: B-TAG and I-TAG tagging frame format in Provider Backbone 1355 Bridged Networks 1357 0 1 2 3 1358 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 1359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1360 | B-DA | 1361 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1362 | | | 1363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1364 | B-SA | 1365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1366 | B-TAG TPID=0x88a8 |B-PCP|D| B-VID | 1367 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1368 | I-TAG TPID=0x88e7 |I-PCP|D|U| Res | I-SID | 1369 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1370 | I-SID | | 1371 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1372 | C-DA | 1373 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1374 | C-SA | 1375 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1376 | | C-TAG TCI=0x8100 | 1377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1378 |C-PCP|C| C-VID | Length/Type | 1379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1380 | | 1381 ~ Customer Data ~ 1382 ~ ~ 1383 | | 1384 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1386 Figure A-6: B-TAG, I-TAG and C-TAG tagging frame format in Provider 1387 Backbone Bridged Networks 1389 0 1 2 3 1390 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 1391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1392 | C-DA | 1393 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1394 | | | 1395 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1396 | C-SA | 1397 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1398 | S-TAG TPID=0x88a8 |S-PCP|D| S-VID | 1399 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1400 | Length/Type | | 1401 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1402 | | 1403 ~ Customer Data ~ 1404 ~ ~ 1405 | | 1406 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1408 This frame format is identical to the format in Figure A-3. 1410 Figure A-7: S-TAG tagging frame format for S-channel over the link 1411 between an end station and its adjacent bridge 1413 0 1 2 3 1414 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 1415 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1416 | C-DA | 1417 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1418 | | | 1419 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1420 | C-SA | 1421 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1422 | S-TAG TPID=0x88a8 |S-PCP|D| S-VID | 1423 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1424 | C-TAG TPID=0x8100 |C-PCP|C| C-VID | 1425 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1426 | Length/Type | | 1427 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1428 | | 1429 ~ Customer Data ~ 1430 ~ ~ 1431 | | 1432 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1434 This frame format is identical to the format in Figure A-4. 1436 Figure A-8: S-TAG and C-TAG tagging frame format over the link 1437 between an end station and its adjacent bridge 1439 0 1 2 3 1440 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 1441 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1442 | C-DA | 1443 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1444 | | | 1445 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1446 | C-SA | 1447 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1448 | E-TAG TPID=0x893F |E-PCP|D| Ingress_E-CID_base | 1449 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1450 |Res|GRP| E-CID_base |Ingre_E-CID_ext| E-CID_ext | 1451 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1452 | Length/Type | | 1453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1454 | | 1455 ~ Customer Data ~ 1456 ~ ~ 1457 | | 1458 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1460 Figure A-9: E-TAG tagging frame format over the link between a 1461 Controlling Bridge and a Bridge Port Extender 1463 0 1 2 3 1464 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 1465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1466 | C-DA | 1467 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1468 | | | 1469 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1470 | C-SA | 1471 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1472 | E-TAG TPID=0x893F |E-PCP|D| Ingress_E-CID_base | 1473 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1474 |Res|GRP| E-CID_base |Ingre_E-CID_ext| E-CID_ext | 1475 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1476 | C-TAG TPID=0x8100 |C-PCP|C| C-VID | 1477 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1478 | Length/Type | | 1479 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1480 | | 1481 ~ Customer Data ~ 1482 ~ ~ 1483 | | 1484 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1486 Figure A-10: E-TAG and C-TAG tagging frame format over the link 1487 between a Controlling Bridge and a Bridge Port Extender 1489 Appendix B. Template Formats Example 1491 0 1 2 3 1492 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 1493 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1494 | Set ID (0x0002) | Length | 1495 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1496 | Template ID (0x0103) | Field Count (0x0008) | 1497 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1498 | ingressInterface (0x000A) | Field Length (0x0004) | 1499 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1500 | egressInterface (0x000E) | Field Length (0x0004) | 1501 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1502 |observationTimeSeconds (0x0142)| Field Length (0x0008) | 1503 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1504 | dataLinkFrameSize (0x0138) | Field Length (0x0002) | 1505 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1506 | dataLinkFrameSection (0x013B) | Field Length (0xFF40) | 1507 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1508 | dataLinkFrameType (0x015B) | Field Length (0x0002) | 1509 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1510 | sectionOffset (0x015C) | Field Length (0x0002) | 1511 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1512 |sectionObservedOctets (0x015D) | Field Length (0x0002) | 1513 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1515 Figure B-1: Template Format Example 1517 Authors' Addresses 1519 Shingo Kashima 1520 Nippon Telegraph and Telephone Corporation 1521 Midori-Cho 3-9-11 1522 Musashino-shi, Tokyo 180-8585 1523 Japan 1525 Phone: +81 422 59 3894 1526 Email: kashima@nttv6.net 1528 Atsushi Kobayashi 1529 Nippon Telegraph and Telephone East Corporation 1530 3-19-2 Nishi-shinjuku 1531 Shinjuku-ku, Tokyo 163-8019 1532 Japan 1534 Phone: +81 3 5359 4351 1535 Email: akoba@nttv6.net 1537 Paul Aitken 1538 Cisco Systems, Inc. 1539 96 Commercial Quay 1540 Commercial Street, Edinburgh EH6 6LX 1541 United Kingdom 1543 Phone: +44 131 561 3616 1544 Email: paitken@cisco.com