1 / 5

Payload Format / Tag Stacking Change

Payload Format / Tag Stacking Change. Authors:. Date: 2013-09-17. Abstract. This presentation discusses payload encoding and the conversion thereof in relation to P802.11ak. Background.

wood
Download Presentation

Payload Format / Tag Stacking Change

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Payload Format / Tag Stacking Change Authors: • Date:2013-09-17 Norman Finn, Cisco Systems

  2. Abstract • This presentation discusses payload encoding and the conversion thereof in relation to P802.11ak. Norman Finn, Cisco Systems

  3. Background • 802.11 and the rest of the world use different frame payload encodings. 802.11 uses LLC (LSAP-LSAP-Control format) encoding while the rest of the world uses Length/Type format encoding. • This is not a problem for simple payloads as usually occur at the edge of the network. But, in the general case of a payload with multiple tags (VLAN, congestion, security, proprietary, etc.), including future tags yet to be defined, it is not possible to convert from one to the other which might be required on entry to or exit from an 802.11ak link. • To fix this requires a frame format change, at least under some circumstances. Norman Finn, Cisco Systems

  4. The Question: • The diagram below is from 802.11-2012 Table P-3. • Does anyone use this format? Or any other cases of stacked SNAP/LLC encoding? If so, please tell TGak. • Some proposed solutions to the problem on the previous slide prohibit the use of this encoding. • Two SNAPs • No Length/Type . 6 2 L 6 2 M EtherType SNAP Tag value SNAP EtherType data AA-AA-03-00-00-00 81-00 87-65 AA-AA-03-00-00-00 08-06 IP ARP packet Slide 4 Norman Finn, Cisco Systems Norman Finn, Cisco Systems

  5. References • For further discussion of this topic, come to the TGak session tomorrow, Thursday, AM1. • More detailed discussion of some aspects of these issues is in document 11-13/0952r2. • The current text of P802.1Qbz Draft 1.3 contains a new tag stacking scheme. P802.1Qbz has passed Task Group Ballot with no “Disapprove” votes. Norman Finn, Cisco Systems

More Related