idnits 2.17.1 draft-ietf-ipfix-data-link-layer-monitoring-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 7 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 22, 2013) is 4079 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- 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' ** Obsolete normative reference: RFC 5101 (Obsoleted by RFC 7011) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 5 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: August 21, 2013 NTT East 6 P. Aitken 7 Cisco Systems, Inc. 8 February 22, 2013 10 Information Elements for Data Link Layer Traffic Measurement 11 draft-ietf-ipfix-data-link-layer-monitoring-02 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 August 21, 2013. 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 This document may contain material from IETF Documents or IETF 52 Contributions published or made publicly available before November 53 10, 2008. The person(s) controlling the copyright in some of this 54 material may not have granted the IETF Trust the right to allow 55 modifications of such material outside the IETF Standards Process. 56 Without obtaining an adequate license from the person(s) controlling 57 the copyright in such materials, this document may not be modified 58 outside the IETF Standards Process, and derivative works of it may 59 not be created outside the IETF Standards Process, except to format 60 it for publication as an RFC or to translate it into languages other 61 than English. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 1.1. Conventions Used in This Document . . . . . . . . . . . . 4 67 2. Extended Ethernet Technology . . . . . . . . . . . . . . . . . 4 68 2.1. Wide-Area Ethernet Technology Summary . . . . . . . . . . 4 69 2.2. Virtual Ethernet Technology Summary . . . . . . . . . . . 5 70 3. New Information Elements . . . . . . . . . . . . . . . . . . . 6 71 3.1. dataLinkFrameSize . . . . . . . . . . . . . . . . . . . . 7 72 3.2. dataLinkFrameSection . . . . . . . . . . . . . . . . . . . 8 73 3.3. dataLinkFrameType . . . . . . . . . . . . . . . . . . . . 8 74 3.4. sectionOffset . . . . . . . . . . . . . . . . . . . . . . 9 75 3.5. sectionObservedOctets . . . . . . . . . . . . . . . . . . 9 76 3.6. dot1qTagProtocolIdentification . . . . . . . . . . . . . . 10 77 3.7. dot1qServiceInstanceTag . . . . . . . . . . . . . . . . . 10 78 3.8. dot1qServiceInstanceId . . . . . . . . . . . . . . . . . . 11 79 3.9. dot1qServiceInstancePriority . . . . . . . . . . . . . . . 11 80 3.10. dot1qCustomerDestinationMacAddress . . . . . . . . . . . . 11 81 3.11. dot1qCustomerSourceMacAddress . . . . . . . . . . . . . . 12 82 3.12. dot1brEchannelTag . . . . . . . . . . . . . . . . . . . . 12 83 3.13. dot1brEChannelPriority . . . . . . . . . . . . . . . . . . 13 84 3.14. l2OctetDeltaCount . . . . . . . . . . . . . . . . . . . . 13 85 3.15. postMCastL2OctetDeltaCount . . . . . . . . . . . . . . . . 13 86 3.16. postL2OctetDeltaCount . . . . . . . . . . . . . . . . . . 14 87 3.17. minimumL2TotalLength . . . . . . . . . . . . . . . . . . . 14 88 3.18. maximumL2TotalLength . . . . . . . . . . . . . . . . . . . 15 89 3.19. l2octetTotalCount . . . . . . . . . . . . . . . . . . . . 15 90 3.20. droppedL2OctetDeltaCount . . . . . . . . . . . . . . . . . 15 91 3.21. droppedL2OctetTotalCount . . . . . . . . . . . . . . . . . 16 92 3.22. ignoredL2OctetTotalCount . . . . . . . . . . . . . . . . . 16 93 3.23. notSentL2OctetTotalCount . . . . . . . . . . . . . . . . . 17 94 3.24. postL2OctetTotalCount . . . . . . . . . . . . . . . . . . 17 95 3.25. postMCastL2OctetTotalCount . . . . . . . . . . . . . . . . 17 96 3.26. l2octetDeltaSumOfSquares . . . . . . . . . . . . . . . . . 18 97 3.27. l2octetTotalSumOfSquares . . . . . . . . . . . . . . . . . 18 98 4. Modification of Existing Information Elements Related to 99 Packet Section . . . . . . . . . . . . . . . . . . . . . . . . 19 100 4.1. ipHeaderPacketSection . . . . . . . . . . . . . . . . . . 19 101 4.2. ipPayloadPacketSection . . . . . . . . . . . . . . . . . . 19 102 4.3. mplsLabelStackSection . . . . . . . . . . . . . . . . . . 19 103 4.4. mplsPayloadPacketSection . . . . . . . . . . . . . . . . . 20 104 5. Modification of Existing Information Elements Related to 105 VLAN Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 106 5.1. dot1qVlanId . . . . . . . . . . . . . . . . . . . . . . . 20 107 5.2. dot1qPriority . . . . . . . . . . . . . . . . . . . . . . 21 108 5.3. dot1qCustomerVlanId . . . . . . . . . . . . . . . . . . . 21 109 5.4. dot1qCustomerPriority . . . . . . . . . . . . . . . . . . 22 110 6. The relationship between Ethernet header fields and 111 Information Elements . . . . . . . . . . . . . . . . . . . . . 22 112 7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 113 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 114 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 115 9.1. Normative References . . . . . . . . . . . . . . . . . . . 25 116 9.2. Informative References . . . . . . . . . . . . . . . . . . 26 117 Appendix A. Tagged Frame Formats . . . . . . . . . . . . . . . . 26 118 Appendix B. Template Formats Example . . . . . . . . . . . . . . 34 119 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34 121 1. Introduction 123 Ethernet [IEEE802.1D] and VLAN (Virtual LAN) technologies had been 124 used only in Local Area Networks. Recently, they have been used in 125 Wide Area Networks, e.g., L2-VPN services. Accordingly, the carrier 126 networks using the VLAN technologies have been enhanced to Provider 127 Bridged Network and Provider Backbone Bridged Networks [IEEE802.1Q]. 128 And, Ethernet in data center also has been enhanced for server 129 virtualization and I/O consolidation. 131 While these innovations provide flexibility, scalability, and 132 mobility to an existing network architecture, it increases the 133 complexity of traffic measurement due to the existence of various 134 Ethernet header formats. To cope with this, a more sophisticated 135 method is required. 137 IPFIX/PSAMP helps to resolve these problems. However, the PSAMP 138 Information Model [RFC5477] and the IPFIX Information Model [RFC5101] 139 are not yet enough for Information Elements related to data link 140 layer, e.g., Ethernet header forms. This document describes the 141 Information Elements related to data link layers that enable a more 142 sophisticated traffic measurement method. 144 1.1. Conventions Used in This Document 146 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 147 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 148 document are to be interpreted as described in RFC 2119 [RFC2119]. 150 2. Extended Ethernet Technology 152 2.1. Wide-Area Ethernet Technology Summary 154 Provider Bridge and Provider Backbone Bridge [IEEE802.1Q], which are 155 standards for the Wide-Area Ethernet, are described below. 157 o In Provider Bridge [IEEE802.1Q], there are two VLAN IDs: Service 158 VLAN Identifier (S-VID) and Customer VLAN Identifier (C-VID). 159 S-VID is assigned to an Ethernet frame by a service provider, 160 while C-VID is independently assigned to an Ethernet frame by a 161 customer. Frame switching in a service provider network is based 162 on only S-VID. 163 o In Provider Backbone Bridge [IEEE802.1Q], new Ethernet fields, 164 such as Backbone VLAN Identifier (B-VID) and Backbone Service 165 Instance Identifier (I-SID), are introduced to overcome the 166 limitations on the VLAN identifier space and to isolate the 167 service provider and customer identifier spaces. Frame switching 168 is based on a 12-bit B-VID, and customer identification is based 169 on a 24-bit I-SID. A flexible network design has become possible 170 because network management is separated from customer management. 171 Other Ethernet fields that indicate quality of service (QoS) class 172 are Backbone VLAN priority code point (B-PCP), Backbone VLAN drop 173 eligible indicator (B-DEI), Backbone Service Instance priority 174 code point (I-PCP), and Backbone Service Instance Drop Eligibility 175 Indicator (I-DEI). 177 The Provider Backbone Bridge technologies have enhanced a wide-area 178 Ethernet service from a flat network to a hierarchical network 179 consisting of Provider Bridge Network and Provider Backbone Bridge 180 Network. 182 Frame formats used in Wide-Area Ethernet are shown in Appendix A. 184 2.2. Virtual Ethernet Technology Summary 186 There have been three challenges in the existing virtual switches 187 environment in a data center. One is the overload on software-based 188 virtual switch. The large volume traffic among virtual machines 189 (VMs) consumes computing resource, then causes to reduce the host's 190 computing resources for the applications on the each VM. Second is 191 the lack of network management visibility. The limited feature on the 192 virtual switch makes difficult to monitor traffic among VMs. Third 193 is the lack of management scalability. Increasing the number of VMs 194 in a data center causes the increase of number of virtual switches. 195 It reaches the limitation of network management. 197 To cope with these challenges, IEEE 802.1 Working Group standardizes 198 two technologies; Virtual Ethernet Port Aggregator (VEPA) 199 [IEEE802.1Qbg] and Bridge Port Extension [IEEE802.1BR]. Edge Virtual 200 Bridging with VEPA removes the burden of host's computing resources 201 by forwarding the traffic among VMs to adjacent physical switch using 202 S-Channel. S-Channel over the link between an end station and its 203 adjacent bridge uses S-TAG [IEEE802.1Q]. On the other hand, Bridge 204 Port Extension emulates single Extended Bridge from multiple physical 205 switches and virtual switches, and simplifies network management. 206 Also, it solves the lack of network management visibility by 207 forwarding all traffic into a central Controlling Bridge using 208 E-Channel. E-Channel over the link between a Bridge Port extender 209 and a Controlling Bridge uses E-TAG defined in [IEEE802.1BR]. 211 The traffic monitoring over S-Channel and E-Channel is required in 212 order to get the visibility of VM-to-VM traffic. The Information 213 Elements related to S-Channel and E-Channel are necessary. 215 Frame format used in S-Channel is complied with S-TAG format. Frame 216 format with E-TAG used in E-channel are shown in Appendix A. 218 3. New Information Elements 220 The following Information Elements whose ElementId are from 312 to 221 TBD03 are necessary for enabling the IPFIX and PSAMP traffic 222 measurement for data link layer, which is not limited to Ethernet 223 because the method can be applied to other data link protocols as 224 well. 226 The following Information Elements whose ElementId are from TBD04 to 227 TBD09 are necessary for enabling the IPFIX and PSAMP traffic 228 measurement for [IEEE802.1Q]. 230 The following Information Elements whose ElementId are from TBD10 to 231 TBD11 are necessary for enabling the IPFIX and PSAMP traffic 232 measurement for [IEEE802.1BR]. 234 The following Information Elements whose ElementId are TBD12 from to 235 TBD25 are octet counter or packet length for layer 2, and are 236 necessary for enabling the IPFIX and PSAMP traffic measurement for 237 data link layer. 239 Note that 312 and 315 are proposed IDs, subject to approval by IANA. 241 +-----+------------------------------------+ 242 | ID | Name | 243 +-----+------------------------------------+ 244 | 312 | dataLinkFrameSize | 245 | 315 | dataLinkFrameSection | 246 |TBD01| dataLinkFrameType | 247 |TBD02| sectionOffset | 248 |TBD03| sectionObservedOctets | 249 |TBD04| dot1qTagProtocolIdentification | 250 |TBD05| dot1qServiceInstanceTag | 251 |TBD06| dot1qServiceInstanceId | 252 |TBD07| dot1qServiceInstancePriority | 253 |TBD08| dot1qCustomerDestinationMacAddress | 254 |TBD09| dot1qCustomerSourceMacAddress | 255 |TBD10| dot1brEChannelTag | 256 |TBD11| dot1brEChannelPriority | 257 |TBD12| l2octetDeltaCount | 258 |TBD13| postMCastL2OctetDeltaCount | 259 |TBD14| postL2OctetDeltaCount | 260 |TBD15| minimumL2TotalLength | 261 |TBD16| maximumL2TotalLength | 262 |TBD17| l2octetTotalCount | 263 |TBD18| droppedL2OctetDeltaCount | 264 |TBD19| droppedL2OctetTotalCount | 265 |TBD20| ignoredL2OctetTotalCount | 266 |TBD21| notSentL2OctetTotalCount | 267 |TBD22| postL2OctetTotalCount | 268 |TBD23| postMCastL2OctetTotalCount | 269 |TBD24| l2octetDeltaSumOfSquares | 270 |TBD25| l2octetTotalSumOfSquares | 271 +-----+------------------------------------+ 273 Table 1: New Information Elements 275 3.1. dataLinkFrameSize 277 Description: 279 This Information Element specifies the length of the selected data 280 link frame. 282 The data link layer is defined in [ISO_IEC.7498-1_1994]. 284 Abstract Data Type: unsigned16 286 Data Type Semantics: quantity 288 ElementId: 312 289 Status: current 291 3.2. dataLinkFrameSection 293 Description: 295 This Information Element carries n octets from the data link frame 296 of a selected frame, starting sectionOffset octets into the frame. 298 The sectionObservedOctets expresses how much data was observed, 299 while the remainder is padding. 301 When the sectionObservedOctets field corresponding to this 302 Information Element exists, this Information Element MAY have a 303 fixed length and MAY be padded, or MAY have a variable length. 305 When the sectionObservedOctets field corresponding to this 306 Information Element does not exist, this Information Element 307 SHOULD have a variable length and MUST NOT be padded. In this 308 case, the size of the exported section may be constrained due to 309 limitations in the IPFIX protocol. 311 Further Information Elements, i.e., dataLinkFrameType and 312 dataLinkFrameSize are needed to specify the data link type and the 313 size of the data link frame of this Information Element. A set of 314 these Information Elements MAY be contained in a structured data 315 type, as expressed in [RFC6313]. Or a set of these Information 316 Elements MAY be contained in one Flow Record as shown in Appendix 317 C. 319 The data link layer is defined in [ISO_IEC.7498-1_1994]. 321 Abstract Data Type: octetArray 323 ElementId: 315 325 Status: current 327 3.3. dataLinkFrameType 329 Description: 331 This Information Element specifies the type of the selected data 332 link frame. 334 The following data link types are defined here. 336 - 0x01 ETHERNET 338 Further values may be assigned by IANA. 340 The data link layer is defined in [ISO_IEC.7498-1_1994]. 342 Abstract Data Type: unsigned16 344 Data Type Semantics: identifier 346 ElementId: TBD01 348 Status: current 350 3.4. sectionOffset 352 Description: 354 This Information Element specifies the offset of the packet 355 section (e.g., dataLinkFrameSection, ipHeaderPacketSection, 356 ipPayloadPacketSection, mplsLabelStackSection and 357 mplsPayloadPacketSection). If this Information Element is 358 omitted, it defaults to zero (ie, no offset). 359 If multiple sectionOffset IEs are specified within a single 360 Template, then they apply to the packet section IEs in order. ie, 361 the first sectionOffset applies to the first packet section, etc. 362 Note that the "closest" sectionOffset and packet section IEs 363 within a given Template are not necessarily related. If there are 364 less sectionOffset IEs than packet section IEs, then subsequent 365 packet section IEs have no offset. If there are more 366 sectionOffset IEs than the number of packet section IEs, then the 367 additional sectionOffset IEs are meaningless. 369 Abstract Data Type: unsigned16 371 Data Type Semantics: quantity 373 ElementId: TBD02 375 Status: current 377 3.5. sectionObservedOctets 379 Description: 381 This Information Element specifies the observed length of the 382 packet section (e.g., dataLinkFrameSection, ipHeaderPacketSection, 383 ipPayloadPacketSection, mplsLabelStackSection and 384 mplsPayloadPacketSection) when padding is used. 386 The packet section may be of a fixed size larger than the 387 sectionObservedOctets. In this case, octets in the packet section 388 beyond the sectionObservedOctets MUST follow the [RFC5101] rules 389 for padding (ie, be composed of zero (0) valued octets). 391 Abstract Data Type: unsigned16 393 Data Type Semantics: quantity 395 ElementId: TBD03 397 Status: current 399 3.6. dot1qTagProtocolIdentification 401 Description: 403 The value represents the Tag Protocol Identification (TPID) in 404 [IEEE802.1Q] including an EtherType to identify the frame as a 405 tagged frame. In the case of multi-tagged frame, it represents 406 the TPID portion of the outer tag. 408 Abstract Data Type: unsigned16 410 Data Type Semantics: identifier 412 ElementId: TBD04 414 Status: current 416 3.7. dot1qServiceInstanceTag 418 Description: 420 This Information Element, which may have 16 octets length, 421 represents the Backbone Service Instance Tag (I-TAG) Tag Control 422 Information (TCI) field of an Ethernet frame as described in 423 [IEEE802.1Q]. It encodes the Backbone Service Instance Priority 424 Code Point (I-PCP), Drop Eligible Indicator (I-DEI), Use Customer 425 Addresses (UCA), Backbone Service Instance Identifier (I-SID), 426 Encapsulated Customer Destination Address (C-DA), Encapsulated 427 Customer Source Address (C-SA) and reserved fields. The structure 428 and semantics within the Tag Control Information field are defined 429 in [IEEE802.1Q]. 431 Abstract Data Type: octetArray 433 Data Type Semantics: identifier 435 ElementId: TBD05 437 Status: current 439 3.8. dot1qServiceInstanceId 441 Description: 443 The value of the 24-bit Backbone Service Instance Identifier 444 (I-SID) portion of the Backbone Service Instance Tag (I-TAG) Tag 445 Control Information (TCI) field of an Ethernet frame as described 446 in [IEEE802.1Q]. 448 Abstract Data Type: unsigned32 450 Data Type Semantics: identifier 452 ElementId: TBD06 454 Status: current 456 3.9. dot1qServiceInstancePriority 458 Description: 460 The value of the 3-bit Backbone Service Instance Priority Code 461 Point (I-PCP) portion of the Backbone Service Instance Tag (I-TAG) 462 Tag Control Information (TCI) field of an Ethernet frame as 463 described in [IEEE802.1Q]. 465 Abstract Data Type: unsigned8 467 Data Type Semantics: identifier 469 ElementId: TBD07 471 Status: current 473 3.10. dot1qCustomerDestinationMacAddress 475 Description: 477 The value of the Encapsulated Customer Destination Address (C-DA) 478 portion of the Backbone Service Instance Tag (I-TAG) Tag Control 479 Information (TCI) field of an Ethernet frame as described in 480 [IEEE802.1Q]. 482 Abstract Data Type: macAddress 484 Data Type Semantics: identifier 486 ElementId: TBD08 488 Status: current 490 3.11. dot1qCustomerSourceMacAddress 492 Description: 494 The value of the Encapsulated Customer Source Address (C-SA) 495 portion of the Backbone Service Instance Tag (I-TAG) Tag Control 496 Information (TCI) field of an Ethernet frame as described in 497 [IEEE802.1Q]. 499 Abstract Data Type: macAddress 501 Data Type Semantics: identifier 503 ElementId: TBD09 505 Status: current 507 3.12. dot1brEchannelTag 509 Description: 511 This Information Element, which has 6 octets length, represents 512 the E-channel Tag (E-TAG) Tag Control Information (TCI) field of 513 an Ethernet frame as described in [IEEE802.1BR]. It encodes the 514 Priority Code Point (E-PCP), Drop Eligible Indicator (E-DEI), 515 ingress E-channel identifier (Ingress E-CID), and E-channel 516 identifier (E-CID). The structure and semantics within the Tag 517 Control Information field are defined in [IEEE802.1BR]. 519 Abstract Data Type: octetArray 521 Data Type Semantics: identifier 523 ElementId: TBD10 524 Status: current 526 3.13. dot1brEChannelPriority 528 Description: 530 The value of the 3-bit E-channel Priority Code Point (E-PCP) 531 portion of the E-channel Tag (E-TAG) Tag Control Information (TCI) 532 field of an Ethernet frame as described in [IEEE802.1BR]. 534 Abstract Data Type: unsigned8 536 Data Type Semantics: identifier 538 ElementId: TBD11 540 Status: current 542 3.14. l2OctetDeltaCount 544 Description: 546 The number of layer 2 octets since the previous report (if any) in 547 incoming packets for this Flow at the Observation Point. The 548 number of octets includes layer 2 header(s) and layer 2 payload. 549 # memo: layer 2 version of octetDeltaCount (field #1) 551 Abstract Data Type: unsigned64 553 Data Type Semantics: deltaCounter 555 ElementId: TBD12 557 Status: current 559 Units: octets 561 3.15. postMCastL2OctetDeltaCount 563 Description: 565 The number of layer 2 octets since the previous report (if any) in 566 outgoing multicast packets sent for packets of this Flow by a 567 multicast daemon within the Observation Domain. This property 568 cannot necessarily be observed at the Observation Point, but may 569 be retrieved by other means. The number of octets includes layer 570 2 header(s) and layer 2 payload. 572 # memo: layer 2 version of postMCastOctetDeltaCount (field #20) 574 Abstract Data Type: unsigned64 576 Data Type Semantics: deltaCounter 578 ElementId: TBD13 580 Status: current 582 Units: octets 584 3.16. postL2OctetDeltaCount 586 Description: 588 The definition of this Information Element is identical to the 589 definition of Information Element 'l2OctetDeltaCount', except that 590 it reports a potentially modified value caused by a middlebox 591 function after the packet passed the Observation Point. 592 # memo: layer 2 version of postOctetDeltaCount (field #23) 594 Abstract Data Type: unsigned64 596 Data Type Semantics: deltaCounter 598 ElementId: TBD14 600 Status: current 602 Units: octets 604 3.17. minimumL2TotalLength 606 Description: 608 Layer 2 length of the smallest packet observed for this Flow. The 609 packet length includes the layer 2 header(s) length and the layer 610 2 payload length. 611 # memo: layer 2 version of minimumIpTotalLength (field #25) 613 Abstract Data Type: unsigned64 615 ElementId: TBD15 617 Status: current 619 Units: octets 621 3.18. maximumL2TotalLength 623 Description: 625 Layer 2 length of the largest packet observed for this Flow. The 626 packet length includes the layer 2 header(s) length and the layer 627 2 payload length. 628 # memo: layer 2 version of maximumIpTotalLength (field #26) 630 Abstract Data Type: unsigned64 632 ElementId: TBD16 634 Status: current 636 Units: octets 638 3.19. l2octetTotalCount 640 Description: 642 The total number of layer 2 octets in incoming packets for this 643 Flow at the Observation Point since the Metering Process 644 (re-)initialization for this Observation Point. The number of 645 octets includes layer 2 header(s) and layer 2 payload. 646 # memo: layer 2 version of octetTotalCount (field #85) 648 Abstract Data Type: unsigned64 650 Data Type Semantics: totalCounter 652 ElementId: TBD17 654 Status: current 656 Units: octets 658 3.20. droppedL2OctetDeltaCount 660 Description: 662 The number of layer 2 octets since the previous report (if any) in 663 packets of this Flow dropped by packet treatment. The number of 664 octets includes layer 2 header(s) and layer 2payload. 665 # memo: layer 2 version of droppedOctetDeltaCount (field #132) 667 Abstract Data Type: unsigned64 668 Data Type Semantics: deltaCounter 670 ElementId: TBD18 672 Status: current 674 Units: octets 676 3.21. droppedL2OctetTotalCount 678 Description: 680 The number of layer 2 octets since the previous report (if any) in 681 packets of this Flow dropped by packet treatment. The number of 682 octets includes layer 2 header(s) and layer 2 payload. 683 # memo: layer 2 version of droppedOctetTotalCount (field #134) 685 Abstract Data Type: unsigned64 687 Data Type Semantics: totalCounter 689 ElementId: TBD19 691 Status: current 693 Units: octets 695 3.22. ignoredL2OctetTotalCount 697 Description: 699 The total number of octets in observed layer 2 packets (including 700 the layer 2 header) that the Metering Process did not process 701 since the (re-)initialization of the Metering Process. 702 # memo: layer 2 version of ignoredOctetTotalCount (field #165) 704 Abstract Data Type: unsigned64 706 Data Type Semantics: totalCounter 708 ElementId: TBD20 710 Status: current 712 Units: octets 714 3.23. notSentL2OctetTotalCount 716 Description: 718 The total number of octets in observed layer 2 packets (including 719 the layer 2 header) that the Metering Process did not process 720 since the (re-)initialization of the Metering Process. 721 # memo: layer 2 version of notSentOctetTotalCount (field #168) 723 Abstract Data Type: unsigned64 725 Data Type Semantics: totalCounter 727 ElementId: TBD21 729 Status: current 731 Units: octets 733 3.24. postL2OctetTotalCount 735 Description: 737 The definition of this Information Element is identical to the 738 definition of Information Element 'l2OctetTotalCount', except that 739 it reports a potentially modified value caused by a middlebox 740 function after the packet passed the Observation Point. 741 # memo: layer 2 version of postOctetTotalCount (field #171) 743 Abstract Data Type: unsigned64 745 Data Type Semantics: totalCounter 747 ElementId: TBD22 749 Status: current 751 Units: octets 753 3.25. postMCastL2OctetTotalCount 755 Description: 757 The total number of layer 2 octets in outgoing multicast packets 758 sent for packets of this Flow by a multicast daemon in the 759 Observation Domain since the Metering Process (re-)initialization. 760 This property cannot necessarily be observed at the Observation 761 Point, but may be retrieved by other means. The number of octets 762 includes layer 2 header(s) and layer 2 payload. 763 # memo: layer 2 version of postMCastOctetTotalCount (field #175) 765 Abstract Data Type: unsigned64 767 Data Type Semantics: totalCounter 769 ElementId: TBD23 771 Status: current 773 Units: octets 775 3.26. l2octetDeltaSumOfSquares 777 Description: 779 The sum of the squared numbers of layer 2 octets per incoming 780 packet since the previous report (if any) for this Flow at the 781 Observation Point. The number of octets includes layer 2 782 header(s) and layer 2 payload. 783 # memo: layer 2 version of octetDeltaSumOfSquares (field #198) 785 Abstract Data Type: unsigned64 787 Data Type Semantics: deltaCounter 789 ElementId: TBD24 791 Status: current 793 Units: octets 795 3.27. l2octetTotalSumOfSquares 797 Description: 799 The total sum of the squared numbers of layer 2 octets in incoming 800 packets for this Flow at the Observation Point since the Metering 801 Process (re-)initialization for this Observation Point. The 802 number of octets includes layer 2 header(s) and layer 2 payload. 803 # memo: layer 2 version of octetTotalSumOfSquares (field #199) 805 Abstract Data Type: unsigned64 807 Data Type Semantics: totalCounter 809 ElementId: TBD25 810 Status: current 812 Units: octets 814 4. Modification of Existing Information Elements Related to Packet 815 Section 817 --- This is open issue. --- 819 New Information Elements related to packet section (ie, sectionOffset 820 and sectionObservedOctets) can be applied to not only 821 dataLinkFrameSection but also all kinds of packet section. In this 822 case, existing Information Elements Description should be modified as 823 follows: 825 4.1. ipHeaderPacketSection 827 Description: 829 TBD 831 Abstract Data Type: octetArray 833 ElementId: 313 835 Status: current 837 4.2. ipPayloadPacketSection 839 Description: 841 TBD 843 Abstract Data Type: octetArray 845 ElementId: 314 847 Status: current 849 4.3. mplsLabelStackSection 851 Description: 853 TBD 855 Abstract Data Type: octetArray 856 ElementId: 316 858 Status: current 860 4.4. mplsPayloadPacketSection 862 Description: 864 TBD 866 Abstract Data Type: octetArray 868 ElementId: 317 870 Status: current 872 5. Modification of Existing Information Elements Related to VLAN Tag 874 The traffic measurement using IPFIX and PSAMP for a Provider Backbone 875 Bridged Network requires the Information Elements related to Backbone 876 Service Instance Tag (I-TAG) and Backbone VLAN Tag (B-TAG). The set 877 of Information Elements related to I-TAG is added in section 3, 878 because I-TAG structure and semantics are different from that of 879 Service VLAN Tag (S-TAG) and Customer VLAN Tag (C-TAG). The set of 880 Information Elements related to B-TAG reuses the existing Information 881 Elements, because B-TAG structure and semantics are identical to that 882 of C-TAG and S-TAG. This section modifies existing Descriptions and 883 Reference related to C-TAG and S-TAG as follows: 885 5.1. dot1qVlanId 887 Description: 889 The value of the 12-bit VLAN Identifier portion of the Tag Control 890 Information field of an Ethernet frame. The structure and 891 semantics within the Tag Control Information field are defined in 892 [IEEE802.1Q]. In Provider Bridged Networks, it represents the 893 Service VLAN identifier in the S-TAG Tag Control Information (TCI) 894 field or the Customer VLAN identifier in the C-TAG Tag Control 895 Information (TCI) field as described in [IEEE802.1Q]. In Provider 896 Backbone Bridged Networks, it represents the Backbone VLAN 897 identifier in the B-TAG Tag Control Information (TCI) field as 898 described in [IEEE802.1Q]. In server-network edge using VEPA- 899 based switches, it represents the Service VLAN identifier 900 indicating S-channel as described in [IEEE802.1Qbg]. 902 In the case of multi-tagged frame, it represents the outer tag's 903 VLAN identifier except for I-TAG. 905 Abstract Data Type: unsigned16 907 Data Type Semantics: identifier 909 ElementId: 243 911 Status: current 913 Reference: 915 (1) [IEEE802.1Q] 916 (2) [IEEE802.1Qbg] 918 5.2. dot1qPriority 920 Description: 922 The value of the 3-bit User Priority portion of the Tag Control 923 Information field of an Ethernet frame. The structure and 924 semantics within the Tag Control Information field are defined in 925 [IEEE802.1Q]. In the case of multi-tagged frame, it represents 926 the 3-bit Priority Code Point (PCP) portion of the outer tag's Tag 927 Control Information (TCI) field as described in [IEEE802.1Q] 928 except for I-TAG. 930 Abstract Data Type: unsigned8 932 Data Type Semantics: identifier 934 ElementId: 244 936 Status: current 938 Reference: 940 (1) [IEEE802.1Q] 942 5.3. dot1qCustomerVlanId 944 Description: 946 The value represents the Customer VLAN identifier in the C-TAG Tag 947 Control Information (TCI) field as described in [IEEE802.1Q]. 949 Abstract Data Type: unsigned16 950 Data Type Semantics: identifier 952 ElementId: 245 954 Status: current 956 Reference: 958 (1) [IEEE802.1Q] 960 5.4. dot1qCustomerPriority 962 Description: 964 The value represents the 3-bit Priority Code Point (PCP) portion 965 of the C-TAG Tag Control Information (TCI) field as described in 966 [IEEE802.1Q]. 968 Abstract Data Type: unsigned8 970 Data Type Semantics: identifier 972 ElementId: 246 974 Status: current 976 Reference: 978 (1) [IEEE802.1Q] 980 6. The relationship between Ethernet header fields and Information 981 Elements 983 The following figures shows summary of various Ethernet header fields 984 and the Informational Elements which would be used to represent each 985 of the fields. 987 <----6----><----6----><----4----><------2------> 988 +----------+----------+----------+--------------+ 989 + + + + + 990 + C-DA + C-SA + C-TAG + Length/Type + 991 + a + b + c + d + 992 +----------+----------+----------+--------------+ 994 a.(Information Element) destinationMacAddress 80 995 b.(Information Element) sourceMacAddress 56 996 c.(Information Elements) dot1qTagProtocolIdentification TBD04, 997 dot1qVlanId 243, dot1qPriority 244 998 d.(Information Element) ethernetType 256 1000 Figure 1: Customer tagged frame header fields 1002 <----6----><----6----><----4----><----4----><------2------> 1003 +----------+----------+----------+----------+--------------+ 1004 + + + + + + 1005 + C-DA + C-SA + S-TAG + C-TAG + Length/Type + 1006 + a + b + c + d + e + 1007 +----------+----------+----------+----------+--------------+ 1009 a.(Information Element) destinationMacAddress 80 1010 b.(Information Element) sourceMacAddress 56 1011 c.(Information Elements) dot1qTagProtocolIdentification TBD04, 1012 dot1qVlanId 243, dot1qPriority 244 1013 d.(Information Elements) dot1qCustomerVlanId 245, 1014 dot1qCustomerPriority 246 1015 e.(Information Element) ethernetType 256 1017 Figure 2: Service tagged frame header fields 1019 <----6----><----6----><----4----><------16------><----4----><------2------> 1020 +----------+----------+----------+---------------+----------+--------------+ 1021 + + + + + + + 1022 + B-DA + B-SA + B-TAG + I-TAG + C-TAG + Length/Type + 1023 + a + b + c + d + e + f + 1024 +----------+----------+----------+---------------+----------+--------------+ 1026 a.(Information Element) destinationMacAddress 80 1027 b.(Information Element) sourceMacAddress 56 1028 c.(Information Elements) dot1qTagProtocolIdentification TBD04, 1029 dot1qVlanId 243, dot1qPriority 244 1030 d.(Information Elements) dot1qServiceInstanceTag TBD05, or 1031 a set of dot1qServiceInstanceId TBD06, 1032 dot1qServiceInstancePriority TBD07, 1033 dot1qCustomerDestinationMacAddress TBD08, 1034 dot1qCustomerSourceMacAddress TBD09 1036 e.(Information Elements) dot1qCustomerVlanId 245, 1037 dot1qCustomerPriority 246 1038 f.(Information Element) ethernetType 256 1040 Figure 3: Backbone VLAN tagged frame header fields 1042 <----6----><----6----><----6----><------2------> 1043 +----------+----------+----------+--------------+ 1044 + + + + + 1045 + C-DA + C-SA + E-TAG + Length/Type + 1046 + a + b + c + d + 1047 +----------+----------+----------+--------------+ 1049 a.(Information Element) destinationMacAddress 80 1050 b.(Information Element) sourceMacAddress 56 1051 c.(Information Elements) dot1brEChannelTag TBD10, 1052 dot1brPriority TBD11 1053 d.(Information Element) ethernetType 256 1055 Figure 4: E-channel tagging frame header fields 1057 7. Security Considerations 1059 The recommendations in this document do not introduce any additional 1060 security issues to those already mentioned in [RFC5101] and 1061 [RFC5477]. 1063 8. IANA Considerations 1065 This document requests that the Information Element IDs are allocated 1066 as shown in section 3 1068 In addition, the dataLinkFrameType Information Element requires the 1069 creation of new IANA registries. 1071 And this document requests that the existing Information Element 1072 Description are modified as shown in section 4 and 5 1074 9. References 1076 9.1. Normative References 1078 [IEEE802.1BR] 1079 IEEE Computer Society, "IEEE Standard for Local and 1080 metropolitan area networks: Virtual Bridged Local Area 1081 Networks: Bridge Port Extension", IEEE Std 802.1BR-2012, 1082 July 2012. 1084 [IEEE802.1Q] 1085 IEEE Computer Society, "IEEE Standard for Local and 1086 metropolitan area networks: Media Access Control (MAC) 1087 Bridges and Virtual Bridged Local Area Networks", IEEE 1088 Std 802.1Q-2011, August 2011. 1090 [IEEE802.1Qbg] 1091 IEEE Computer Society, "IEEE Standard for Local and 1092 metropolitan area networks: Media Access Control (MAC) 1093 Bridges and Virtual Bridged Local Area Networks: Amendment 1094 21: Edge Virtual Bridging", IEEE Std 802.1Qbg-2012, 1095 July 2012. 1097 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1098 Requirement Levels", BCP 14, RFC 2119, March 1997. 1100 [RFC5101] Claise, B., "Specification of the IP Flow Information 1101 Export (IPFIX) Protocol for the Exchange of IP Traffic 1102 Flow Information", RFC 5101, January 2008. 1104 [RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G. 1105 Carle, "Information Model for Packet Sampling Exports", 1106 RFC 5477, March 2009. 1108 [RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates, 1109 "Export of Structured Data in IP Flow Information Export 1110 (IPFIX)", RFC 6313, July 2011. 1112 9.2. Informative References 1114 [IEEE802.1D] 1115 IEEE Computer Society, "IEEE Standard for Local and 1116 metropolitan area networks: Media Access Control (MAC) 1117 Bridges", IEEE Std 802.1D-2004, June 2004. 1119 [ISO_IEC.7498-1_1994] 1120 International Organization for Standardization, 1121 "Information technology -- Open Systems Interconnection -- 1122 Basic Reference Model: The Basic Mode", ISO Standard 7498- 1123 1:1994, June 1996. 1125 Appendix A. Tagged Frame Formats 1127 0 1 2 3 1128 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1130 | C-DA | 1131 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1132 | | | 1133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1134 | C-SA | 1135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1136 | Length/Type | | 1137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1138 | | 1139 ~ Customer Data ~ 1140 ~ ~ 1141 | | 1142 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1144 Figure A-1: Untagged frame format 1146 0 1 2 3 1147 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1149 | C-DA | 1150 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1151 | | | 1152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1153 | C-SA | 1154 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1155 | C-TAG TPID=0x8100 |C-PCP|C| C-VID | 1156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1157 | Length/Type | | 1158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1159 | | 1160 ~ Customer Data ~ 1161 ~ ~ 1162 | | 1163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1165 Figure A-2: C-TAG tagging frame format 1167 0 1 2 3 1168 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1170 | C-DA | 1171 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1172 | | | 1173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1174 | C-SA | 1175 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1176 | S-TAG TPID=0x88a8 |S-PCP|D| S-VID | 1177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1178 | Length/Type | | 1179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1180 | | 1181 ~ Customer Data ~ 1182 ~ ~ 1183 | | 1184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1186 Figure A-3: S-TAG tagging frame format in Provider Bridged Networks 1188 0 1 2 3 1189 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 1190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1191 | C-DA | 1192 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1193 | | | 1194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1195 | C-SA | 1196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1197 | S-TAG TPID=0x88a8 |S-PCP|D| S-VID | 1198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1199 | C-TAG TPID=0x8100 |C-PCP|C| C-VID | 1200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1201 | Length/Type | | 1202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1203 | | 1204 ~ Customer Data ~ 1205 ~ ~ 1206 | | 1207 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1209 Figure A-4: S-TAG and C-TAG tagging frame format in Provider Bridged 1210 Networks 1212 0 1 2 3 1213 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 1214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1215 | B-DA | 1216 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1217 | | | 1218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1219 | B-SA | 1220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1221 | B-TAG TPID=0x88a8 |B-PCP|D| B-VID | 1222 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1223 | I-TAG TPID=0x88e7 |I-PCP|D|U| Res | I-SID | 1224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1225 | I-SID | | 1226 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1227 | C-DA | 1228 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1229 | C-SA | 1230 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1231 | | Length/Type | 1232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1233 | | 1234 ~ Customer Data ~ 1235 ~ ~ 1236 | | 1237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1239 Figure A-5: B-TAG and I-TAG tagging frame format in Provider Backbone 1240 Bridged Networks 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 | B-DA | 1246 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1247 | | | 1248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1249 | B-SA | 1250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1251 | B-TAG TPID=0x88a8 |B-PCP|D| B-VID | 1252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1253 | I-TAG TPID=0x88e7 |I-PCP|D|U| Res | I-SID | 1254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1255 | I-SID | | 1256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1257 | C-DA | 1258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1259 | C-SA | 1260 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1261 | | C-TAG TCI=0x8100 | 1262 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1263 |C-PCP|C| C-VID | Length/Type | 1264 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1265 | | 1266 ~ Customer Data ~ 1267 ~ ~ 1268 | | 1269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1271 Figure A-6: B-TAG, I-TAG and C-TAG tagging frame format in Provider 1272 Backbone Bridged Networks 1274 This frame format is identical to the format in Figure A-3. 1276 0 1 2 3 1277 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 1278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1279 | C-DA | 1280 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1281 | | | 1282 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1283 | C-SA | 1284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1285 | S-TAG TPID=0x88a8 |S-PCP|D| S-VID | 1286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1287 | Length/Type | | 1288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1289 | | 1290 ~ Customer Data ~ 1291 ~ ~ 1292 | | 1293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1295 Figure A-6: S-TAG tagging frame format for S-Channel over the link 1296 between an end station and its adjacent bridge 1298 This frame format is identical to the format in Figure A-4. 1300 0 1 2 3 1301 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 1302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1303 | C-DA | 1304 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1305 | | | 1306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1307 | C-SA | 1308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1309 | S-TAG TPID=0x88a8 |S-PCP|D| S-VID | 1310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1311 | C-TAG TPID=0x8100 |C-PCP|C| C-VID | 1312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1313 | Length/Type | | 1314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1315 | | 1316 ~ Customer Data ~ 1317 ~ ~ 1318 | | 1319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1320 Figure A-7: S-TAG and C-TAG tagging frame format over the link 1321 between an end station and its adjacent bridge 1323 0 1 2 3 1324 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 1325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1326 | C-DA | 1327 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1328 | | | 1329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1330 | C-SA | 1331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1332 | E-TAG TPID=0x893F |E-PCP|D| Ingress_E-CID_base | 1333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1334 |Res|GRP| E-CID_base |Ingre_E-CID_ext| E-CID_ext | 1335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1336 | Length/Type | | 1337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1338 | | 1339 ~ Customer Data ~ 1340 ~ ~ 1341 | | 1342 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1344 Figure A-8: E-TAG tagging frame format over the link between a 1345 Controlling Bridge and a Bridge Port Extender 1347 0 1 2 3 1348 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1350 | C-DA | 1351 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1352 | | | 1353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1354 | C-SA | 1355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1356 | E-TAG TPID=0x893F |E-PCP|D| Ingress_E-CID_base | 1357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1358 |Res|GRP| E-CID_base |Ingre_E-CID_ext| E-CID_ext | 1359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1360 | C-TAG TPID=0x8100 |C-PCP|C| C-VID | 1361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1362 | Length/Type | | 1363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 1364 | | 1365 ~ Customer Data ~ 1366 ~ ~ 1367 | | 1368 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1370 Figure A-9: E-TAG and C-TAG tagging frame format over the link 1371 between a Controlling Bridge and a Bridge Port Extender 1373 Appendix B. Template Formats Example 1375 0 1 2 3 1376 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 1377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1378 | Set ID (0x0002) | Length | 1379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1380 | Template ID (0x0103) | Field Count (0x0008) | 1381 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1382 | ingressInterface (0x000A) | Field Length (0x0004) | 1383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1384 | egressInterface (0x000E) | Field Length (0x0004) | 1385 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1386 |observationTimeSeconds (0x0142)| Field Length (0x0008) | 1387 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1388 | dataLinkFrameSize (0x0138) | Field Length (0x0002) | 1389 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1390 | dataLinkFrameSection (0x013B) | Field Length (0xFF40) | 1391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1392 | dataLinkFrameType (0x015B) | Field Length (0x0002) | 1393 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1394 | sectionOffset (0x015C) | Field Length (0x0002) | 1395 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1396 |sectionObservedOctets (0x015D) | Field Length (0x0002) | 1397 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1399 Figure B-1: Template Format Example 1401 Authors' Addresses 1403 Shingo Kashima 1404 NTT Information Sharing Platform Lab. 1405 Midori-Cho 3-9-11 1406 Musashino-shi, Tokyo 180-8585 1407 Japan 1409 Phone: +81 422 59 3894 1410 Email: kashima@nttv6.net 1411 Atsushi Kobayashi 1412 NTT EAST IT Innovation Department 1413 25F 3-20-2 Nishi-shinjuku 1414 Shinjuku-ku, Tokyo 163-1425 1415 Japan 1417 Phone: +81 3 5353 3636 1418 Email: akoba@nttv6.net 1420 Paul Aitken 1421 Cisco Systems, Inc. 1422 96 Commercial Quay 1423 Commercial Street, Edinburgh EH6 6LX 1424 United Kingdom 1426 Phone: +44 131 561 3616 1427 Email: paitken@cisco.com