idnits 2.17.1 draft-ietf-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 04, 2013) is 3825 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: 2 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, Ed. 5 Expires: May 08, 2014 NTT East 6 P. Aitken 7 Cisco Systems, Inc. 8 November 04, 2013 10 Information Elements for Data Link Layer Traffic Measurement 11 draft-ietf-ipfix-data-link-layer-monitoring-07 13 Abstract 15 This document describes Information Elements related to the 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 May 08, 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 Data Link Layer . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . 9 65 3.2.3. sectionExportedOctets . . . . . . . . . . . . . . . . 9 66 3.2.4. dot1qServiceInstanceTag . . . . . . . . . . . . . . . 10 67 3.2.5. dot1qServiceInstanceId . . . . . . . . . . . . . . . 10 68 3.2.6. dot1qServiceInstancePriority . . . . . . . . . . . . 10 69 3.2.7. dot1qCustomerSourceMacAddress . . . . . . . . . . . . 11 70 3.2.8. dot1qCustomerDestinationMacAddress . . . . . . . . . 11 71 3.2.9. l2OctetDeltaCount . . . . . . . . . . . . . . . . . . 11 72 3.2.10. postL2OctetDeltaCount . . . . . . . . . . . . . . . . 12 73 3.2.11. postMCastL2OctetDeltaCount . . . . . . . . . . . . . 12 74 3.2.12. l2OctetTotalCount . . . . . . . . . . . . . . . . . . 13 75 3.2.13. postL2OctetTotalCount . . . . . . . . . . . . . . . . 13 76 3.2.14. postMCastL2OctetTotalCount . . . . . . . . . . . . . 14 77 3.2.15. minimumL2TotalLength . . . . . . . . . . . . . . . . 14 78 3.2.16. maximumL2TotalLength . . . . . . . . . . . . . . . . 15 79 3.2.17. droppedL2OctetDeltaCount . . . . . . . . . . . . . . 15 80 3.2.18. droppedL2OctetTotalCount . . . . . . . . . . . . . . 16 81 3.2.19. ignoredL2OctetTotalCount . . . . . . . . . . . . . . 16 82 3.2.20. notSentL2OctetTotalCount . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . 18 87 4.1. ipHeaderPacketSection . . . . . . . . . . . . . . . . . . 18 88 4.2. ipPayloadPacketSection . . . . . . . . . . . . . . . . . 19 89 4.3. mplsLabelStackSection . . . . . . . . . . . . . . . . . . 20 90 4.4. mplsPayloadPacketSection . . . . . . . . . . . . . . . . 21 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 . . . . . . . . . . . . . . 33 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, carrier 114 networks using VLAN technologies have been enhanced to Provider 115 Bridged Network and Provider Backbone Bridged Networks [IEEE802.1Q]. 116 And, Ethernet in data centers has also 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 don't yet contain enough 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 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 visibility: limited features on virtual switches makes it difficult 178 to monitor traffic among virtual machines (VMs). Also, the lack of 179 management scalability and flexibility: increasing the number of VMs 180 for multi-tenant causes an increase of the number of virtual switches 181 and of the number of the traffic control policies, which reaches the 182 limitations of network management scalability and flexibility. 184 In this situation, the IEEE 802.1 Working Group is standardizing 185 virtual bridging technologies as Edge Virtual Bridge (EVB) including 186 two kinds of Edge Relay (ER): Virtual Edge Bridge (VEB) and Virtual 187 Edge Port Aggregator (VEPA) [IEEE802.1Qbg]. The VEB is a bridge that 188 provides a bridging among multiple VMs and the external bridging 189 environment. The VEPA is a bridge-like device on a host that 190 forwards all internal traffic to the adjacent EVB bridge and then 191 distributes any traffic received from the adjacent EVB bridge to VMs. 192 The VEPA makes all the VM-to-VM traffic visible to EVB bridge so that 193 the traffic can be monitored and so the EVB bridge can apply 194 filtering to the traffic. 196 To improve flexibility, a virtual link between a host system and EVB 197 bridge is standardized as S-channel. S-channel allows a bridge to 198 treat the traffic in the virtual link as if it comes in on a separate 199 port. For example, in the host, an S-channel may be attached to a 200 VEB or a VEPA or directly an internal port in order to apply each 201 port-based filtering rules to the traffic. S-channel over the link 202 between a host and its adjacent bridge uses S-TAG [IEEE802.1Q]. When 203 S-channel is in use, frames on the link carry an S-TAG to identify 204 the S-channel. 206 On the other hand, Bridge Port Extension emulates single Extended 207 Bridge from multiple physical switches and virtual switches, and 208 simplifies network management. Also, it solves the lack of network 209 management visibility by forwarding all traffic into a central 210 Controlling Bridge using E-channel. E-channel over the link between 211 a Bridge Port extender and a Controlling Bridge uses E-TAG defined in 212 [IEEE802.1BR]. 214 Traffic monitoring over S-channel and E-channel is required in order 215 to get visibility of VM-to-VM traffic, and visibility of each 216 channel's traffic on a virtual link. 218 Frame formats with E-TAG used in E-channel and S-TAG used in 219 S-channel are shown in Appendix A. Though these frames carry special 220 tags while on the link, those tags identify a virtual port (or for 221 multicast in the downstream direction, a set of virtual ports) to 222 which they are destined. These tag values only have local meaning 223 and the flow would be reported as sent and arriving on the 224 corresponding virtual ports. Therefore, IPFIX does not need to 225 monitor data based on these tags. 227 3. Information Elements Related to Data Link Layer 229 The following Information Elements whose ElementId are from 312 to 230 TBD03 are necessary for enabling the IPFIX and PSAMP traffic 231 measurement for data link layer, which is not limited to Ethernet 232 because the method can be applied to other data link protocols as 233 well. 235 The following Information Elements whose ElementId are from TBD04 to 236 TBD08 are necessary for enabling the IPFIX and PSAMP traffic 237 measurement for [IEEE802.1Q]. 239 The following Information Elements whose ElementId are from TBD09 to 240 TBD22 are octet counter or packet length for layer 2, and are 241 necessary for enabling the IPFIX and PSAMP traffic measurement for 242 data link layer. 244 +-----+------------------------------------+ 245 | ID | Name | 246 +-----+------------------------------------+ 247 | 312 | dataLinkFrameSize | 248 | 315 | dataLinkFrameSection | 249 |TBD01| dataLinkFrameType | 250 |TBD02| sectionOffset | 251 |TBD03| sectionExportedOctets | 252 |TBD04| dot1qServiceInstanceTag | 253 |TBD05| dot1qServiceInstanceId | 254 |TBD06| dot1qServiceInstancePriority | 255 |TBD07| dot1qCustomerSourceMacAddress | 256 |TBD08| dot1qCustomerDestinationMacAddress | 257 |TBD09| l2OctetDeltaCount | 258 |TBD10| postL2OctetDeltaCount | 259 |TBD11| postMCastL2OctetDeltaCount | 260 |TBD12| l2OctetTotalCount | 261 |TBD13| postL2OctetTotalCount | 262 |TBD14| postMCastL2OctetTotalCount | 263 |TBD15| minimumL2TotalLength | 264 |TBD16| maximumL2TotalLength | 265 |TBD17| droppedL2OctetDeltaCount | 266 |TBD18| droppedL2OctetTotalCount | 267 |TBD19| ignoredL2OctetTotalCount | 268 |TBD20| notSentL2OctetTotalCount | 269 |TBD21| l2OctetDeltaSumOfSquares | 270 |TBD22| l2OctetTotalSumOfSquares | 271 +-----+------------------------------------+ 273 Table 1: Information Elements related to data link layer 275 3.1. Existing Information Elements 277 Some existing Information Elements are required for data link layer 278 export. Their details are reproduced here from IANA's IPFIX registry 279 [IANA-IPFIX], except for additions as marked *. 281 3.1.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.1.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 *However, when the sectionOffset field corresponding to this 306 Information Element does not exist, the octets MUST be from the 307 start of the data link frame.* 309 The sectionExportedOctets expresses how much data was observed, 310 while the remainder is padding. 312 When the sectionExportedOctets field corresponding to this 313 Information Element exists, this Information Element MAY have a 314 fixed length and MAY be padded, or MAY have a variable length. 316 When the sectionExportedOctets field corresponding to this 317 Information Element does not exist, this Information Element 318 SHOULD have a variable length and MUST NOT be padded. In this 319 case, the size of the exported section may be constrained due to 320 limitations in the IPFIX protocol. 322 Further Information Elements, i.e., dataLinkFrameType and 323 dataLinkFrameSize are needed to specify the data link type and the 324 size of the data link frame of this Information Element. A set of 325 these Information Elements MAY be contained in a structured data 326 type, as expressed in [RFC6313]. Or a set of these Information 327 Elements MAY be contained in one Flow Record as shown in 328 Appendix B of [RFCEDITOR:thisRFC]. 330 The data link layer is defined in [ISO_IEC.7498-1_1994]. 332 Abstract Data Type: octetArray 334 ElementId: 315 336 Status: current 338 3.2. New Information Elements 340 The following new Information Elements are added for data link layer 341 monitoring. 343 3.2.1. dataLinkFrameType 345 Description: 347 This Information Element specifies the type of the selected data 348 link frame. 350 The following data link types are defined here. 352 - 0x01 IEEE802.3 ETHERNET [IEEE802.3] 354 - 0x02 IEEE802.11 MAC Frame format [IEEE802.11] 356 Further values may be assigned by IANA. Note that the assigned 357 values are bits so that multiple observations can be OR'd 358 together. 360 The data link layer is defined in [ISO_IEC.7498-1_1994]. 362 Abstract Data Type: unsigned16 364 Data Type Semantics: flags 366 ElementId: TBD01 368 Status: current 370 3.2.2. sectionOffset 372 Description: 374 This Information Element specifies the offset of the packet 375 section (e.g., dataLinkFrameSection, ipHeaderPacketSection, 376 ipPayloadPacketSection, mplsLabelStackSection and 377 mplsPayloadPacketSection). If this Information Element is 378 omitted, it defaults to zero (ie, no offset). 380 If multiple sectionOffset IEs are specified within a single 381 Template, then they apply to the packet section IEs in order. ie, 382 the first sectionOffset applies to the first packet section, etc. 383 Note that the "closest" sectionOffset and packet section IEs 384 within a given Template are not necessarily related. If there are 385 less sectionOffset IEs than packet section IEs, then subsequent 386 packet section IEs have no offset. If there are more 387 sectionOffset IEs than the number of packet section IEs, then the 388 additional sectionOffset IEs are meaningless. 390 Abstract Data Type: unsigned16 392 Data Type Semantics: quantity 394 ElementId: TBD02 396 Status: current 398 3.2.3. sectionExportedOctets 400 Description: 402 This Information Element specifies the observed length of the 403 packet section (e.g., dataLinkFrameSection, ipHeaderPacketSection, 404 ipPayloadPacketSection, mplsLabelStackSection and 405 mplsPayloadPacketSection) when padding is used. 407 The packet section may be of a fixed size larger than the 408 sectionExportedOctets. In this case, octets in the packet section 409 beyond the sectionExportedOctets MUST follow the [RFC7011] rules 410 for padding (ie, be composed of zero (0) valued octets). 412 Abstract Data Type: unsigned16 414 Data Type Semantics: quantity 416 ElementId: TBD03 417 Status: current 419 3.2.4. dot1qServiceInstanceTag 421 Description: 423 This Information Element, which is 16 octets long, represents the 424 Backbone Service Instance Tag (I-TAG) Tag Control Information 425 (TCI) field of an Ethernet frame as described in [IEEE802.1Q]. It 426 encodes the Backbone Service Instance Priority Code Point (I-PCP), 427 Drop Eligible Indicator (I-DEI), Use Customer Addresses (UCA), 428 Backbone Service Instance Identifier (I-SID), Encapsulated 429 Customer Destination Address (C-DA), Encapsulated Customer Source 430 Address (C-SA) and reserved fields. The structure and semantics 431 within the Tag Control Information field are defined in 432 [IEEE802.1Q]. 434 Abstract Data Type: octetArray 436 Data Type Semantics: identifier 438 ElementId: TBD04 440 Status: current 442 3.2.5. dot1qServiceInstanceId 444 Description: 446 The value of the 24-bit Backbone Service Instance Identifier 447 (I-SID) portion of the Backbone Service Instance Tag (I-TAG) Tag 448 Control Information (TCI) field of an Ethernet frame as described 449 in [IEEE802.1Q]. 451 Abstract Data Type: unsigned32 453 Data Type Semantics: identifier 455 ElementId: TBD05 457 Status: current 459 3.2.6. dot1qServiceInstancePriority 461 Description: 463 The value of the 3-bit Backbone Service Instance Priority Code 464 Point (I-PCP) portion of the Backbone Service Instance Tag (I-TAG) 465 Tag Control Information (TCI) field of an Ethernet frame as 466 described in [IEEE802.1Q]. 468 Abstract Data Type: unsigned8 470 Data Type Semantics: identifier 472 ElementId: TBD06 474 Status: current 476 3.2.7. dot1qCustomerSourceMacAddress 478 Description: 480 The value of the Encapsulated Customer Source Address (C-SA) 481 portion of the Backbone Service Instance Tag (I-TAG) Tag Control 482 Information (TCI) field of an Ethernet frame as described in 483 [IEEE802.1Q]. 485 Abstract Data Type: macAddress 487 Data Type Semantics: identifier 489 ElementId: TBD07 491 Status: current 493 3.2.8. dot1qCustomerDestinationMacAddress 495 Description: 497 The value of the Encapsulated Customer Destination Address (C-DA) 498 portion of the Backbone Service Instance Tag (I-TAG) Tag Control 499 Information (TCI) field of an Ethernet frame as described in 500 [IEEE802.1Q]. 502 Abstract Data Type: macAddress 504 Data Type Semantics: identifier 506 ElementId: TBD08 508 Status: current 510 3.2.9. l2OctetDeltaCount 512 Description: 514 The number of layer 2 octets since the previous report (if any) in 515 incoming packets for this Flow at the Observation Point. The 516 number of octets includes layer 2 header(s) and layer 2 payload. 518 This Information Element is the layer 2 version of octetDeltaCount 519 (ElementId #1) in [RFC5477]. 521 Abstract Data Type: unsigned64 523 Data Type Semantics: deltaCounter 525 ElementId: TBD09 527 Status: current 529 Units: octets 531 3.2.10. postL2OctetDeltaCount 533 Description: 535 The definition of this Information Element is identical to the 536 definition of Information Element 'l2OctetDeltaCount', except that 537 it reports a potentially modified value caused by a middlebox 538 function after the packet passed the Observation Point. 540 This Information Element is the layer 2 version of 541 postOctetDeltaCount (ElementId #23) in [RFC5477]. 543 Abstract Data Type: unsigned64 545 Data Type Semantics: deltaCounter 547 ElementId: TBD10 549 Status: current 551 Units: octets 553 3.2.11. postMCastL2OctetDeltaCount 555 Description: 557 The number of layer 2 octets since the previous report (if any) in 558 outgoing multicast packets sent for packets of this Flow by a 559 multicast daemon within the Observation Domain. This property 560 cannot necessarily be observed at the Observation Point, but may 561 be retrieved by other means. The number of octets includes layer 562 2 header(s) and layer 2 payload. 564 This Information Element is the layer 2 version of 565 postMCastOctetDeltaCount (ElementId #20) in [RFC5477]. 567 Abstract Data Type: unsigned64 569 Data Type Semantics: deltaCounter 571 ElementId: TBD11 573 Status: current 575 Units: octets 577 3.2.12. l2OctetTotalCount 579 Description: 581 The total number of layer 2 octets in incoming packets for this 582 Flow at the Observation Point since the Metering Process 583 (re-)initialization for this Observation Point. The number of 584 octets includes layer 2 header(s) and layer 2 payload. 586 This Information Element is the layer 2 version of octetTotalCount 587 (ElementId #85) in [RFC5477]. 589 Abstract Data Type: unsigned64 591 Data Type Semantics: totalCounter 593 ElementId: TBD12 595 Status: current 597 Units: octets 599 3.2.13. postL2OctetTotalCount 601 Description: 603 The definition of this Information Element is identical to the 604 definition of Information Element 'l2OctetTotalCount', except that 605 it reports a potentially modified value caused by a middlebox 606 function after the packet passed the Observation Point. 608 This Information Element is the layer 2 version of 609 postOctetTotalCount (ElementId #171) in [RFC5477]. 611 Abstract Data Type: unsigned64 613 Data Type Semantics: totalCounter 615 ElementId: TBD13 617 Status: current 619 Units: octets 621 3.2.14. postMCastL2OctetTotalCount 623 Description: 625 The total number of layer 2 octets in outgoing multicast packets 626 sent for packets of this Flow by a multicast daemon in the 627 Observation Domain since the Metering Process (re-)initialization. 628 This property cannot necessarily be observed at the Observation 629 Point, but may be retrieved by other means. The number of octets 630 includes layer 2 header(s) and layer 2 payload. 632 This Information Element is the layer 2 version of 633 postMCastOctetTotalCount (ElementId #175) in [RFC5477]. 635 Abstract Data Type: unsigned64 637 Data Type Semantics: totalCounter 639 ElementId: TBD14 641 Status: current 643 Units: octets 645 3.2.15. minimumL2TotalLength 647 Description: 649 Layer 2 length of the smallest packet observed for this Flow. The 650 packet length includes the layer 2 header(s) length and the layer 651 2 payload length. 653 This Information Element is the layer 2 version of 654 minimumIpTotalLength (ElementId #25) in [RFC5477]. 656 Abstract Data Type: unsigned64 658 ElementId: TBD15 660 Status: current 662 Units: octets 664 3.2.16. maximumL2TotalLength 666 Description: 668 Layer 2 length of the largest packet observed for this Flow. The 669 packet length includes the layer 2 header(s) length and the layer 670 2 payload length. 672 This Information Element is the layer 2 version of 673 maximumIpTotalLength (ElementId #26) in [RFC5477]. 675 Abstract Data Type: unsigned64 677 ElementId: TBD16 679 Status: current 681 Units: octets 683 3.2.17. droppedL2OctetDeltaCount 685 Description: 687 The number of layer 2 octets since the previous report (if any) in 688 packets of this Flow dropped by packet treatment. The number of 689 octets includes layer 2 header(s) and layer 2payload. 691 This Information Element is the layer 2 version of 692 droppedOctetDeltaCount (ElementId #132) in [RFC5477]. 694 Abstract Data Type: unsigned64 696 Data Type Semantics: deltaCounter 698 ElementId: TBD17 700 Status: current 701 Units: octets 703 3.2.18. droppedL2OctetTotalCount 705 Description: 707 The total number of octets in observed layer 2 packets (including 708 the layer 2 header) that were dropped by packet treatment since 709 the (re-)initialization of the Metering Process. 711 This Information Element is the layer 2 version of 712 droppedOctetTotalCount (ElementId #134) in [RFC5477]. 714 Abstract Data Type: unsigned64 716 Data Type Semantics: totalCounter 718 ElementId: TBD18 720 Status: current 722 Units: octets 724 3.2.19. ignoredL2OctetTotalCount 726 Description: 728 The total number of octets in observed layer 2 packets (including 729 the layer 2 header) that the Metering Process did not process 730 since the (re-)initialization of the Metering Process. 732 This Information Element is the layer 2 version of 733 ignoredOctetTotalCount (ElementId #165) in [RFC5477]. 735 Abstract Data Type: unsigned64 737 Data Type Semantics: totalCounter 739 ElementId: TBD19 741 Status: current 743 Units: octets 745 3.2.20. notSentL2OctetTotalCount 747 Description: 749 The total number of octets in observed layer 2 packets (including 750 the layer 2 header) that the Metering Process did not process 751 since the (re-)initialization of the Metering Process. 753 This Information Element is the layer 2 version of 754 notSentOctetTotalCount (ElementId #168) in [RFC5477]. 756 Abstract Data Type: unsigned64 758 Data Type Semantics: totalCounter 760 ElementId: TBD20 762 Status: current 764 Units: octets 766 3.2.21. l2OctetDeltaSumOfSquares 768 Description: 770 The sum of the squared numbers of layer 2 octets per incoming 771 packet since the previous report (if any) for this Flow at the 772 Observation Point. The number of octets includes layer 2 773 header(s) and layer 2 payload. 775 This Information Element is the layer 2 version of 776 octetDeltaSumOfSquares (ElementId #198) in [RFC5477]. 778 Abstract Data Type: unsigned64 780 Data Type Semantics: deltaCounter 782 ElementId: TBD21 784 Status: current 786 Units: octets 788 3.2.22. l2OctetTotalSumOfSquares 790 Description: 792 The total sum of the squared numbers of layer 2 octets in incoming 793 packets for this Flow at the Observation Point since the Metering 794 Process (re-)initialization for this Observation Point. The 795 number of octets includes layer 2 header(s) and layer 2 payload. 797 This Information Element is the layer 2 version of 798 octetTotalSumOfSquares (ElementId #199) in [RFC5477]. 800 Abstract Data Type: unsigned64 802 Data Type Semantics: totalCounter 804 ElementId: TBD22 806 Status: current 808 Units: octets 810 4. Modification of Existing Information Elements Related to Packet 811 Section 813 The new Information Elements related to packet section (ie, 814 sectionOffset and sectionExportedOctets) can be applied to not only 815 dataLinkFrameSection but also all kinds of packet section (ie, 816 ipHeaderPacketSection, ipPayloadPacketSection, mplsLabelStackSection, 817 and mplsPayloadPacketSection defined in [RFC5477]). Therefore 818 existing Information Elements Descriptions should be modified as 819 follows: 821 4.1. ipHeaderPacketSection 823 This Information Element is defined in [RFC5477]. The description is 824 updated from [RFC5477]. 826 Description: 828 This Information Element carries a series of n octets from the IP 829 header of a sampled packet, starting sectionOffset octets into the 830 IP header. 832 However, when the sectionOffset field corresponding to this 833 Information Element does not exist, the octets MUST be from the 834 start of the IP header. 836 With sufficient length, this element also reports octets from the 837 IP payload, subject to [RFC2804]. See the Security Considerations 838 section in [RFC5477]. 840 The sectionExportedOctets expresses how much data was exported, 841 while the remainder is padding. 843 When the sectionExportedOctets field corresponding to this 844 Information Element exists, this Information Element MAY have a 845 fixed length and MAY be padded, or MAY have a variable length. 847 When the sectionExportedOctets field corresponding to this 848 Information Element does not exist, this Information Element 849 SHOULD have a variable length and MUST NOT be padded. In this 850 case, the size of the exported section may be constrained due to 851 limitations in the IPFIX protocol. 853 Abstract Data Type: octetArray 855 ElementId: 313 857 Status: current 859 4.2. ipPayloadPacketSection 861 This Information Element is defined in [RFC5477]. The description is 862 updated from [RFC5477]. 864 Description: 866 This Information Element carries a series of n octets from the IP 867 payload of a sampled packet, starting sectionOffset octets into 868 the IP payload. 870 However, when the sectionOffset field corresponding to this 871 Information Element does not exist, the octets MUST be from the 872 start of the IP payload. 874 The IPv4 payload is that part of the packet that follows the IPv4 875 header and any options, which [RFC0791] refers to as "data" or 876 "data octets". For example, see the examples in [RFC0791], 877 Appendix A. 879 The IPv6 payload is the rest of the packet following the 40-octet 880 IPv6 header. Note that any extension headers present are 881 considered part of the payload. See [RFC2460] for the IPv6 882 specification. 884 The sectionExportedOctets expresses how much data was observed, 885 while the remainder is padding. 887 When the sectionExportedOctets field corresponding to this 888 Information Element exists, this Information Element MAY have a 889 fixed length and MAY be padded, or MAY have a variable length. 891 When the sectionExportedOctets field corresponding to this 892 Information Element does not exist, this Information Element 893 SHOULD have a variable length and MUST NOT be padded. In this 894 case, the size of the exported section may be constrained due to 895 limitations in the IPFIX protocol. 897 Abstract Data Type: octetArray 899 ElementId: 314 901 Status: current 903 4.3. mplsLabelStackSection 905 This Information Element is defined in [RFC5477]. The description is 906 updated from [RFC5477]. 908 Description: 910 This Information Element carries a series of n octets from the 911 MPLS label stack of a sampled packet, starting sectionOffset 912 octets into the MPLS label stack. 914 However, when the sectionOffset field corresponding to this 915 Information Element does not exist, the octets MUST be from the 916 head of the MPLS label stack. 918 With sufficient length, this element also reports octets from the 919 MPLS payload, subject to [RFC2804]. See the Security 920 Considerations section in [RFC5477]. 922 See [RFC3031] for the specification of MPLS packets. 924 See [RFC3032] for the specification of the MPLS label stack. 926 The sectionExportedOctets expresses how much data was observed, 927 while the remainder is padding. 929 When the sectionExportedOctets field corresponding to this 930 Information Element exists, this Information Element MAY have a 931 fixed length and MAY be padded, or MAY have a variable length. 933 When the sectionExportedOctets field corresponding to this 934 Information Element does not exist, this Information Element 935 SHOULD have a variable length and MUST NOT be padded. In this 936 case, the size of the exported section may be constrained due to 937 limitations in the IPFIX protocol. 939 Abstract Data Type: octetArray 941 ElementId: 316 943 Status: current 945 4.4. mplsPayloadPacketSection 947 This Information Element is defined in [RFC5477]. The description is 948 updated from [RFC5477]. 950 Description: 952 The mplsPayloadPacketSection carries a series of n octets from the 953 MPLS payload of a sampled packet, starting sectionOffset octets 954 into the MPLS payload, being data that follows immediately after 955 the MPLS label stack. 957 However, when the sectionOffset field corresponding to this 958 Information Element does not exist, the octets MUST be from the 959 start of the MPLS payload. 961 See [RFC3031] for the specification of MPLS packets. 963 See [RFC3032] for the specification of the MPLS label stack. 965 The sectionExportedOctets expresses how much data was observed, 966 while the remainder is padding. 968 When the sectionExportedOctets field corresponding to this 969 Information Element exists, this Information Element MAY have a 970 fixed length and MAY be padded, or MAY have a variable length. 972 When the sectionExportedOctets field corresponding to this 973 Information Element does not exist, this Information Element 974 SHOULD have a variable length and MUST NOT be padded. In this 975 case, the size of the exported section may be constrained due to 976 limitations in the IPFIX protocol. 978 Abstract Data Type: octetArray 980 ElementId: 317 982 Status: current 984 5. Modification of Existing Information Elements Related to VLAN Tag 985 The traffic measurement using IPFIX and PSAMP for a Provider Backbone 986 Bridged Network requires the Information Elements related to Backbone 987 Service Instance Tag (I-TAG) and Backbone VLAN Tag (B-TAG). The set 988 of Information Elements related to I-TAG is added in section 3, 989 because I-TAG structure and semantics are different from that of 990 Service VLAN Tag (S-TAG) and Customer VLAN Tag (C-TAG). The set of 991 Information Elements related to B-TAG reuses the existing Information 992 Elements, because B-TAG structure and semantics are identical to that 993 of C-TAG and S-TAG. This section modifies existing Descriptions and 994 Reference related to C-TAG and S-TAG as follows: 996 5.1. dot1qVlanId 998 Description: 1000 The value of the 12-bit VLAN Identifier portion of the Tag Control 1001 Information field of an Ethernet frame. The structure and 1002 semantics within the Tag Control Information field are defined in 1003 [IEEE802.1Q]. In Provider Bridged Networks, it represents the 1004 Service VLAN identifier in the S-TAG Tag Control Information (TCI) 1005 field or the Customer VLAN identifier in the C-TAG Tag Control 1006 Information (TCI) field as described in [IEEE802.1Q]. In Provider 1007 Backbone Bridged Networks, it represents the Backbone VLAN 1008 identifier in the B-TAG Tag Control Information (TCI) field as 1009 described in [IEEE802.1Q]. In a virtual link between a host 1010 system and EVB bridge, it represents the Service VLAN identifier 1011 indicating S-channel as described in [IEEE802.1Qbg]. 1013 In the case of multi-tagged frame, it represents the outer tag's 1014 VLAN identifier except for I-TAG. 1016 Abstract Data Type: unsigned16 1018 Data Type Semantics: identifier 1020 ElementId: 243 1022 Status: current 1024 Reference: 1026 (1) [IEEE802.1Q] 1028 (2) [IEEE802.1Qbg] 1030 5.2. dot1qPriority 1032 Description: 1034 The value of the 3-bit User Priority portion of the Tag Control 1035 Information field of an Ethernet frame. The structure and 1036 semantics within the Tag Control Information field are defined in 1037 [IEEE802.1Q]. In the case of multi-tagged frame, it represents 1038 the 3-bit Priority Code Point (PCP) portion of the outer tag's Tag 1039 Control Information (TCI) field as described in [IEEE802.1Q] 1040 except for I-TAG. 1042 Abstract Data Type: unsigned8 1044 Data Type Semantics: identifier 1046 ElementId: 244 1048 Status: current 1050 Reference: 1052 (1) [IEEE802.1Q] 1054 5.3. dot1qCustomerVlanId 1056 Description: 1058 The value represents the Customer VLAN identifier in the C-TAG Tag 1059 Control Information (TCI) field as described in [IEEE802.1Q]. 1061 Abstract Data Type: unsigned16 1063 Data Type Semantics: identifier 1065 ElementId: 245 1067 Status: current 1069 Reference: 1071 (1) [IEEE802.1Q] 1073 5.4. dot1qCustomerPriority 1075 Description: 1077 The value represents the 3-bit Priority Code Point (PCP) portion 1078 of the C-TAG Tag Control Information (TCI) field as described in 1079 [IEEE802.1Q]. 1081 Abstract Data Type: unsigned8 1082 Data Type Semantics: identifier 1084 ElementId: 246 1086 Status: current 1088 Reference: 1090 (1) [IEEE802.1Q] 1092 6. The relationship between Ethernet header fields and Information 1093 Elements 1095 The following figures shows summary of various Ethernet header fields 1096 and the Informational Elements which would be used to represent each 1097 of the fields. 1099 <-- 6 --> <-- 6 --> <-- 4 --> <---- 2 ----> 1100 +---------+---------+---------+-------------+ 1101 | | | | | 1102 | C-DA | C-SA | C-TAG | Length/Type | 1103 | a | b | c | d | 1104 +---------+---------+---------+-------------+ 1106 a.(Information Element) destinationMacAddress (80) 1107 b.(Information Element) sourceMacAddress (56) 1108 c.(Information Elements) dot1qVlanId (243), dot1qPriority (244) 1109 d.(Information Element) ethernetType (256) 1111 Figure 1: Customer tagged frame header fields 1113 <-- 6 --> <-- 6 --> <-- 4 --> <-- 4 --> <---- 2 ----> 1114 +---------+---------+---------+---------+-------------+ 1115 | | | | | | 1116 | C-DA | C-SA | S-TAG | C-TAG | Length/Type | 1117 | a | b | c | d | e | 1118 +---------+---------+---------+---------+-------------+ 1120 a.(Information Element) destinationMacAddress (80) 1121 b.(Information Element) sourceMacAddress (56) 1122 c.(Information Elements) dot1qVlanId (243), dot1qPriority (244) 1123 d.(Information Elements) dot1qCustomerVlanId (245), 1124 dot1qCustomerPriority (246) 1125 e.(Information Element) ethernetType (256) 1127 Figure 2: Service tagged frame header fields 1129 <-- 6 --> <-- 6 --> <-- 4 --> <--- 16 ---> <-- 4 --> <---- 2 ----> 1130 +---------+---------+---------+------------+---------+-------------+ 1131 | | | | | | | 1132 | B-DA | B-SA | B-TAG | I-TAG | C-TAG | Length/Type | 1133 | a | b | c | d | e | f | 1134 +---------+---------+---------+------------+---------+-------------+ 1136 a.(Information Element) destinationMacAddress (80) 1137 b.(Information Element) sourceMacAddress (56) 1138 c.(Information Elements) dot1qVlanId (243, dot1qPriority (244) 1139 d.(Information Elements) dot1qServiceInstanceTag (TBD04), or 1140 a set of dot1qServiceInstanceId (TBD05), 1141 dot1qServiceInstancePriority (TBD06), 1142 dot1qCustomerSourceMacAddress (TBD07) 1143 dot1qCustomerDestinationMacAddress (TBD08), 1144 e.(Information Elements) dot1qCustomerVlanId (245), 1145 dot1qCustomerPriority (246) 1146 f.(Information Element) ethernetType (256) 1148 Figure 3: Backbone VLAN tagged frame header fields 1150 7. Security Considerations 1152 The recommendations in this document do not introduce any additional 1153 security issues beyond those already mentioned in [RFC7011] and 1154 [RFC5477]. 1156 8. IANA Considerations 1158 This document requests that existing IPFIX Information Elements 1159 [IANA-IPFIX] are modified as indicated in sections 3.1, 4, and 5 1160 above. 1162 This document requests that new IPFIX Information Elements 1163 [IANA-IPFIX] are allocated as shown in section 3.2 above. 1165 9. Acknowledgments 1167 Thanks to Brian Trammell and IPFIX members who contributed to 1168 mailing-list discussions throughout the development of this document, 1169 and especially to Pat Thaler for her help with the IEEE 802 aspects 1170 of this work. 1172 10. References 1174 10.1. Normative References 1176 [IEEE802.11] 1177 IEEE Computer Society, "IEEE Standard for Information 1178 technology. Telecommunications and information exchange 1179 between systems Local and metropolitan area networks. 1180 Specific requirements Part 11: Wireless LAN Medium Access 1181 Control (MAC) and Physical Layer (PHY) Specifications ", 1182 IEEE Std 802.11-2012, March 2012. 1184 [IEEE802.1BR] 1185 IEEE Computer Society, "IEEE Standard for Local and 1186 metropolitan area networks: Virtual Bridged Local Area 1187 Networks: Bridge Port Extension ", IEEE Std 802.1BR-2012, 1188 July 2012. 1190 [IEEE802.1Q] 1191 IEEE Computer Society, "IEEE Standard for Local and 1192 metropolitan area networks: Media Access Control (MAC) 1193 Bridges and Virtual Bridged Local Area Networks ", IEEE 1194 Std 802.1Q-2011, August 2011. 1196 [IEEE802.1Qbg] 1197 IEEE Computer Society, "IEEE Standard for Local and 1198 metropolitan area networks: Media Access Control (MAC) 1199 Bridges and Virtual Bridged Local Area Networks: Amendment 1200 21: Edge Virtual Bridging ", IEEE Std 802.1Qbg-2012, July 1201 2012. 1203 [IEEE802.3] 1204 IEEE Computer Society, "IEEE Standard for Ethernet ", IEEE 1205 Std 802.3-2012, December 2012. 1207 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1208 1981. 1210 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1211 Requirement Levels", BCP 14, RFC 2119, March 1997. 1213 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 1214 (IPv6) Specification", RFC 2460, December 1998. 1216 [RFC2804] IAB IESG, "IETF Policy on Wiretapping", RFC 2804, May 1217 2000. 1219 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 1220 Label Switching Architecture", RFC 3031, January 2001. 1222 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 1223 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack 1224 Encoding", RFC 3032, January 2001. 1226 [RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G. 1227 Carle, "Information Model for Packet Sampling Exports", 1228 RFC 5477, March 2009. 1230 [RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates, 1231 "Export of Structured Data in IP Flow Information Export 1232 (IPFIX)", RFC 6313, July 2011. 1234 [RFC7011] Claise, B., Trammell, B., and P. Aitken, "Specification of 1235 the IP Flow Information Export (IPFIX) Protocol for the 1236 Exchange of Flow Information", STD 77, RFC 7011, September 1237 2013. 1239 10.2. Informative References 1241 [IANA-IPFIX] 1242 Internet Assigned Numbers Authority, "IANA IPFIX 1243 Information Element Registry", 1244 http://www.iana.org/assignments/ipfix/ipfix.xhtml. 1246 [IEEE802.1D] 1247 IEEE Computer Society, "IEEE Standard for Local and 1248 metropolitan area networks: Media Access Control (MAC) 1249 Bridges", IEEE Std 802.1D-2004, June 2004. 1251 [ISO_IEC.7498-1_1994] 1252 International Organization for Standardization, 1253 "Information technology -- Open Systems Interconnection -- 1254 Basic Reference Model: The Basic Mode", ISO Standard 1255 7498-1:1994, June 1996. 1257 Appendix A. Tagged Frame Formats 1259 0 1 2 3 1260 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 1261 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1262 | C-DA | 1263 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1264 | | | 1265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1266 | C-SA | 1267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1268 | Length/Type | | 1269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1270 | | 1271 ~ Customer Data ~ 1272 ~ ~ 1273 | | 1274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1276 Figure A-1: Untagged frame format 1278 0 1 2 3 1279 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 1280 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1281 | C-DA | 1282 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1283 | | | 1284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1285 | C-SA | 1286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1287 | C-TAG TPID=0x8100 |C-PCP|C| C-VID | 1288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1289 | Length/Type | | 1290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1291 | | 1292 ~ Customer Data ~ 1293 ~ ~ 1294 | | 1295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1297 Figure A-2: C-TAG tagging frame format 1299 0 1 2 3 1300 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 1301 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1302 | C-DA | 1303 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1304 | | | 1305 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1306 | C-SA | 1307 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1308 | S-TAG TPID=0x88a8 |S-PCP|D| S-VID | 1309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1310 | Length/Type | | 1311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1312 | | 1313 ~ Customer Data ~ 1314 ~ ~ 1315 | | 1316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1318 Figure A-3: S-TAG tagging frame format in Provider Bridged Networks 1320 0 1 2 3 1321 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 1322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1323 | C-DA | 1324 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1325 | | | 1326 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1327 | C-SA | 1328 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1329 | S-TAG TPID=0x88a8 |S-PCP|D| S-VID | 1330 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1331 | C-TAG TPID=0x8100 |C-PCP|C| C-VID | 1332 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1333 | Length/Type | | 1334 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1335 | | 1336 ~ Customer Data ~ 1337 ~ ~ 1338 | | 1339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1341 Figure A-4: S-TAG and C-TAG tagging frame format in Provider Bridged 1342 Networks 1344 0 1 2 3 1345 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 1346 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1347 | B-DA | 1348 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1349 | | | 1350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1351 | B-SA | 1352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1353 | B-TAG TPID=0x88a8 |B-PCP|D| B-VID | 1354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1355 | I-TAG TPID=0x88e7 |I-PCP|D|U| Res | I-SID | 1356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1357 | I-SID | | 1358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1359 | C-DA | 1360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1361 | C-SA | 1362 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1363 | | Length/Type | 1364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1365 | | 1366 ~ Customer Data ~ 1367 ~ ~ 1368 | | 1369 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1371 Figure A-5: B-TAG and I-TAG tagging frame format in Provider Backbone 1372 Bridged Networks 1374 0 1 2 3 1375 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 1376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1377 | B-DA | 1378 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1379 | | | 1380 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1381 | B-SA | 1382 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1383 | B-TAG TPID=0x88a8 |B-PCP|D| B-VID | 1384 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1385 | I-TAG TPID=0x88e7 |I-PCP|D|U| Res | I-SID | 1386 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1387 | I-SID | | 1388 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1389 | C-DA | 1390 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1391 | C-SA | 1392 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1393 | | C-TAG TCI=0x8100 | 1394 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1395 |C-PCP|C| C-VID | Length/Type | 1396 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1397 | | 1398 ~ Customer Data ~ 1399 ~ ~ 1400 | | 1401 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1403 Figure A-6: B-TAG, I-TAG and C-TAG tagging frame format in Provider 1404 Backbone Bridged Networks 1406 0 1 2 3 1407 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 1408 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1409 | C-DA | 1410 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1411 | | | 1412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1413 | C-SA | 1414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1415 | S-TAG TPID=0x88a8 |S-PCP|D| S-VID | 1416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1417 | Length/Type | | 1418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1419 | | 1420 ~ Customer Data ~ 1421 ~ ~ 1422 | | 1423 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1425 Figure A-7: S-TAG tagging frame format for S-channel over the link 1426 between an end station and its adjacent bridge 1428 Note that this frame format is identical to the format in Figure A-3. 1430 0 1 2 3 1431 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 1432 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1433 | C-DA | 1434 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1435 | | | 1436 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1437 | C-SA | 1438 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1439 | S-TAG TPID=0x88a8 |S-PCP|D| S-VID | 1440 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1441 | C-TAG TPID=0x8100 |C-PCP|C| C-VID | 1442 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1443 | Length/Type | | 1444 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1445 | | 1446 ~ Customer Data ~ 1447 ~ ~ 1448 | | 1449 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1451 Figure A-8: S-TAG and C-TAG tagging frame format over the link 1452 between an end station and its adjacent bridge 1454 This frame format is identical to the format in Figure A-4. 1456 0 1 2 3 1457 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 1458 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1459 | C-DA | 1460 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1461 | | | 1462 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1463 | C-SA | 1464 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1465 | E-TAG TPID=0x893F |E-PCP|D| Ingress_E-CID_base | 1466 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1467 |Res|GRP| E-CID_base |Ingre_E-CID_ext| E-CID_ext | 1468 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1469 | Length/Type | | 1470 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1471 | | 1472 ~ Customer Data ~ 1473 ~ ~ 1474 | | 1475 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1477 Figure A-9: E-TAG tagging frame format over the link between a 1478 Controlling Bridge and a Bridge Port Extender 1480 0 1 2 3 1481 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 1482 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1483 | C-DA | 1484 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1485 | | | 1486 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1487 | C-SA | 1488 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1489 | E-TAG TPID=0x893F |E-PCP|D| Ingress_E-CID_base | 1490 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1491 |Res|GRP| E-CID_base |Ingre_E-CID_ext| E-CID_ext | 1492 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1493 | C-TAG TPID=0x8100 |C-PCP|C| C-VID | 1494 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1495 | Length/Type | | 1496 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1497 | | 1498 ~ Customer Data ~ 1499 ~ ~ 1500 | | 1501 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1503 Figure A-10: E-TAG and C-TAG tagging frame format over the link 1504 between a Controlling Bridge and a Bridge Port Extender 1506 Appendix B. Template Formats Example 1508 0 1 2 3 1509 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 1510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1511 | Set ID (0x0002) | Length | 1512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1513 | Template ID (0x0103) | Field Count (0x0008) | 1514 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1515 | ingressInterface (0x000A) | Field Length (0x0004) | 1516 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1517 | egressInterface (0x000E) | Field Length (0x0004) | 1518 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1519 |observationTimeSeconds (0x0142)| Field Length (0x0008) | 1520 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1521 | dataLinkFrameSize (0x0138) | Field Length (0x0002) | 1522 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1523 | dataLinkFrameSection (0x013B) | Field Length (0xFF40) | 1524 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1525 | dataLinkFrameType (0x015B) | Field Length (0x0002) | 1526 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1527 | sectionOffset (0x015C) | Field Length (0x0002) | 1528 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1529 |sectionObservedOctets (0x015D) | Field Length (0x0002) | 1530 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1532 Figure B-1: Template Format Example 1534 Authors' Addresses 1536 Shingo Kashima 1537 Nippon Telegraph and Telephone Corporation 1538 Midori-Cho 3-9-11 1539 Musashino-shi, Tokyo 180-8585 1540 Japan 1542 Phone: +81 422 59 3894 1543 Email: kashima@nttv6.net 1544 Atsushi Kobayashi 1545 Nippon Telegraph and Telephone East Corporation 1546 3-19-2 Nishi-shinjuku 1547 Shinjuku-ku, Tokyo 163-8019 1548 Japan 1550 Phone: +81 3 5359 4351 1551 Email: akoba@nttv6.net 1553 Paul Aitken 1554 Cisco Systems, Inc. 1555 96 Commercial Quay 1556 Commercial Street, Edinburgh EH6 6LX 1557 United Kingdom 1559 Phone: +44 131 561 3616 1560 Email: paitken@cisco.com