Submission doc.: IEEE 11-13/0938r1 August 2013 Norman Finn, Cisco SystemsSlide 1 Service mapping between the ISS and 802.11 Date: 2013-08-05 Authors:

Slides:



Advertisements
Similar presentations
Submission doc.: IEEE 11-13/ ak-r0 March 2013 Norman Finn, Cisco SystemsSlide 1 Changes to 802.1Q required by 802.1Qbz Date: Authors:
Advertisements

Submission doc.: IEEE 11-13/ ak July 2013 Finn and Hart, Cisco SystemsSlide 1 P802.1Qbz + P802.11ak Proposed Division of Work Date:
Cisco Confidential 1 bz-nfinn-soln-station-subset-0113-v02.pdf Solutions for P802.1Qbz / P802.11ak: Station subset issue Norman Finn January, 2013 Version.
Doc.: IEEE /2897r3 Submission May 2008 Qi Wang, Broadcom CorporationSlide 1 Efficient TIM element supporting multiple BSSIDs Date:
Joining LANs - Bridges. Connecting LANs 4 Repeater –Operates at the Physical layer no decision making, processing signal boosting only 4 Bridges –operates.
Doc.: IEEE 11-15/0454r0 March 2015 SubmissionSlide 1, Mark Hamilton, Spectralink Some more DS architecture concepts Date: Authors: Sli de 1.
Oct 12, 2004CS573: Network Protocols and Standards1 Virtual LANs Network Protocols and Standards Autumn
Jan 10, 2008CS573: Network Protocols and Standards1 Virtual LANs Network Protocols and Standards Winter
Submission doc.: IEEE 11-12/ ak December 2012 Norman Finn, Cisco SystemsSlide 1 Problem list for P802.1Qbz / P802.11ak point-to-point model Date:
Submission doc.: IEEE 11/ ak Jan 2013 Norman Finn, Cisco SystemsSlide Qbz–802.11ak Solutions: Station Subsetting Issue Date:
LOGO Local Area Network (LAN) Layer 2 Switching and Virtual LANs (VLANs) Local Area Network (LAN) Layer 2 Switching and Virtual LANs (VLANs) Chapter 6.
Doc.: IEEE /2233r0 Submission July 2007 Darwin Engwer, Nortel NetworksSlide 1 Wireless Bridge Common Practices Notice: This document has been.
Doc.: IEEE 11-14/0562r4 November 2014 SubmissionSlide 1Norman Finn, Cisco Systems, Mark Hamilton, Spectralink ak and 802.1AC Convergence Function.
Doc.: IEEE /0065r2 Submission January 2011 Ivan Pustogarov, IITP RASSlide 1 GCR for mesh Date: January 2011 Authors:
Submission doc.: IEEE 11-13/ ak May 2013 Norman Finn, Cisco SystemsSlide 1 P802.1Qbz + P802.11ak Proposed Division of Work Date: Authors:
Month Year doc.: IEEE yy/0221r2 Mar 2013
Doc.: IEEE /0981r1 TGs Reference Architecture Considerations September 6, 2004 Tricci So & W. Steven Conner.Slide 1 TGs ESS Mesh System Reference.
Submission doc.: IEEE 11-12/0589r2 July 2012 Donald Eastlake 3rd, Huawei R&D USASlide 1 General Links Date: Authors:
Doc.: IEEE /2901r06 Submission November 2007 Doug Kavner, RaytheonSlide 1 Use of BSSID in WAVE Date: Authors:
Submission doc.: IEEE 11-13/ ak May 2013 Norman Finn, Cisco SystemsSlide 1 P802.1Qbz + P802.11ak Proposed Division of Work Date: Authors:
Doc.: IEEE /1265r0 Submission November 2008 Liwen Chu, et al.Slide 1 STA Communication Inside a BSS and Outside the Context of a BSS Date:
Submission doc.: IEEE 11-14/0867r0 July 2014 Donald Eastlake, HuaweiSlide 1 A Subsetting and EPD Approach Date: Authors:
Submission doc.: IEEE 11/ ak Jan 2013 Norman Finn, Cisco SystemsSlide Qbz–802.11ak Solutions: Architecture Issue Date: Authors:
Submission doc.: IEEE 11/ ak Jan 2013 Norman Finn, Cisco SystemsSlide Qbz–802.11ak Solutions: Tagging Date: Authors:
Doc.: IEEE /0897r0 SubmissionJae Seung Lee, ETRISlide 1 Active Scanning considering Operating Status of APs Date: July 2012.
Submission doc.: IEEE 11-13/1453r0 November 2014 Norman Finn, Cisco SystemsSlide 1 Tag Stacking in existing links Date: Authors:
Submission doc.: IEEE 11-13/ ak May 2013 Finn and Hart, Cisco SystemsSlide 1 P802.1Qbz + P802.11ak Proposed Division of Work Date:
Doc.: IEEE /0981r0 TGs Reference Architecture Considerations August 30, 2004 Tricci So.Slide 1 TGs ESS Mesh System Reference Architecture Considerations.
Doc.: IEEE /1109r0 Submission Month Year Tom Siep, CSRSlide 1 Amendment Creation Process Date: YYYY-MM-DD Authors:
Doc.: IEEE /1378r0 Submission November 2008 Darwin Engwer, Nortel NetworksSlide 1 Improving Multicast Reliability Date: Authors:
Chapter 4 Version 1 Virtual LANs. Introduction By default, switches forward broadcasts, this means that all segments connected to a switch are in one.
Submission doc.: IEEE 11-13/0221r1 Mar 2013 BroadcomSlide QoS Queue Architecture and Possible 802.1bz Bridge Model Date: Authors:
Submission doc.: IEEE 11-13/ ak-r1 July 2013 Norman Finn, Cisco SystemsSlide 1 Comparison of Receiver Subset Techniques Date: Authors:
Submission doc.: IEEE 11-12/ ak January 2013 Norman Finn, Cisco SystemsSlide 1 Problem list for P802.1Qbz / P802.11ak point-to-point model Date:
Submission doc.: IEEE 11-13/0526r1 May 2013 Donald Eastlake, HuaweiSlide 1 Sub-Setting Date: Authors:
September 2002 doc.: IEEE /568r0 David Skellern, Cisco SystemsSlide 1Submission RRM Architectural Framework David Skellern Wireless Networking.
Submission doc.: IEEE 11/ ak Jan 2013 Norman Finn, Cisco SystemsSlide Qbz–802.11ak Solutions: Station Subsetting Issue Date:
Submission doc.: IEEE 11-13/ ak May 2013 Norman Finn, Cisco SystemsSlide 1 P802.1Qbz + P802.11ak Proposed Division of Work Date: Authors:
Submission doc.: IEEE 11-13/0148r1 January 2013 Donald Eastlake, Huawei TechnologiesSlide 1 TGak January Closing Report Date: Authors: NameAddressAffiliationsPhone .
Doc.: IEEE /102r0 Submission January 2003 Sid Schrum, Texas Instruments, Inc.Slide 1 QBSS Downlink Broadcast and Multicast Data Frame Handling.
Doc.: IEEE 11-14/0562r0 May 2014 SubmissionSlide 1Norman Finn, Cisco Systems, Mark Hamilton, Spectralink ak and 802.1AC Convergence Function Date:
Doc.: IEEE /2901r05 Submission November 2007 Doug Kavner, RaytheonSlide 1 Use of BSSID in WAVE Date: Authors:
Submission doc.: IEEE 11-12/1162r0 September 2012 Norman Finn, Cisco SystemsSlide Q Bridge Baggy Pants Explanation Date: Authors:
Doc.: IEEE 11-14/0562r7 November 2015 SubmissionSlide 1Norman Finn, Cisco Systems, Mark Hamilton, Spectralink ak and 802.1AC Convergence Function.
Doc.: IEEE /2901r08 Submission March 2008 Doug Kavner, RaytheonSlide 1 Use of BSSID in WAVE Date: Authors:
Doc: IEEE /0395r2 Submission March 2009 R. Roy, ConnexisSlide 1 WAVE ITS Station Technical Capabilities Summary Date: Authors:
Submission doc.: IEEE 11-13/0221r0 Feb 2013 BroadcomSlide QoS Queue Architecture and Possible 802.1bz Bridge Model Date: Authors:
Doc.: IEEE 11-16/ arc March 2016 SubmissionSlide ak/802.1AC/STAs/APs/DSes and Convergence Functions Date: Authors:
Doc.: IEEE 11-14/0562r6 March 2015 SubmissionSlide 1Norman Finn, Cisco Systems, Mark Hamilton, Spectralink ak and 802.1AC Convergence Function Date:
Portal and 802.1AC Convergence Function
Switching and VLANs.
Switching and VLANs.
Virtual Local Area Networks (VLANs) Part I
doc.: IEEE /xxxr0 Mike Moreton
802.11ak/802.1AC/STAs/APs/DSes and Convergence Functions
Ethernet : Framing and Addressing
Proposal for IEEE solution
Switching and VLANs.
Problem & Proposal for User Plane Support for QoS Mapping
802.11ak Architecture Date: Authors: July 2013
AP Architecture Thoughts
MAPID for User Plane Support
2/17/2019 Interpretations of the Distribution System Service Based on the Specification W. Steven Conner, Intel Corp. Tricci So, Nortel Networks.
Portal and 802.1AC Convergence Function
802.11ba Architecture Discussion
Use of BSSID in WAVE Date: Authors: November 2007
Use of BSSID in WAVE Date: Authors: November 2007
FILS Frame Content Date: Authors: February 2008
MAC Service Updates for NGV
Roaming mechanism for duty cycle mode
Presentation transcript:

Submission doc.: IEEE 11-13/0938r1 August 2013 Norman Finn, Cisco SystemsSlide 1 Service mapping between the ISS and Date: Authors:

Submission doc.: IEEE 11-13/0938r1 August 2013 Norman Finn, Cisco SystemsSlide 2 Abstract The ISS services required by IEEE 802.1Q Bridges can be mapped to the services offered by either the infrastructure or non-AP station interfaces of P802.11ak. This can be accomplished by defining a new interface between P802.11ak and 802.1AC consisting of a single instance of the ISS with an associated port vector.

Submission doc.: IEEE 11-13/0938r1 The Virtual Bridge Architecture IEEE Std 802.1Q-2011

Submission doc.: IEEE 11-13/0938r1 The Virtual Bridge Architecture IEEE Std 802.1Q-2011 Let’s zoom in on this

Submission doc.: IEEE 11-13/0938r1 Three methods for connecting a Bridge to media P802.1Qbz Draft 1.2 (still in early Task Group balloting stage) DONENEW 123

Submission doc.: IEEE 11-13/0938r1 INFRASTRUCTURE SIDE August 2013 Norman Finn, Cisco SystemsSlide 6

Submission doc.: IEEE 11-13/0938r1 Convergence Functions for 2: infrastructure access For most media (e.g , FDDI, MOST, or the Portal interface) it is a relatively simple chore to map the ISS parameters to the particular medium’s parameters. For P802.1Qbz / P802.11ak, convergence is more complex. The security layer is necessarily down in , not above the ISS, because secures fragments of frames. There is one physical interface that can send a multicast, theoretically sent on multiple ports, with a single transmission. This multiplexing involves the cooperation of the AP and the non-AP station; the non- AP station must decode the port selection encoded in the frame by the AP. Media Access Method Dependent Convergence Functions (802.11) 802.1AE SecY (ISS) controlled uncontrolled 802.1AE SecY (ISS) controlled uncontrolled (ISS) (Not strictly 802.1AE SecY, but equivalent in terms of usage and effect.)

Submission doc.: IEEE 11-13/0938r Q AC Convergence ak infrastructure 802.1AC Media Access Method Dependent Convergence Functions Many ISS  Infrastructure SAP + vector of ports ak Infrastructure access Vector of ports  N frames with third MAC address and subset encoding (802.11) SecY 1 (ISS) SecY 2 (ISS) SecY m (ISS) … CUCC C C: UC: controlled uncontrolled (Infrastructure SAP with port vector)

Submission doc.: IEEE 11-13/0938r AC Media Access Method Dependent Convergence Functions Many ISS  Infrastructure SAP + vector of ports ak Infrastructure access Vector of ports  N frames with third MAC address and subset encoding (802.11) (ISS) … CUCC C Eliminate the SecY. Attach both controlled and uncontrolled ports to the convergence function. (This trick goes in 802.1Qbz.) (Infrastructure SAP with port vector) 1 2m 802.1Q AC Convergence ak infrastructure

Submission doc.: IEEE 11-13/0938r1 Infrastructure 802.1AC Convergence (ISS) … CUCC C All of the ports associated with a given AP (or BSS, in the sense of a logical function) go through a single instance of the convergence function. For.requests: The convergence function turns some number of.requests presented “simultaneously” on some number of its upper SAPs into a single.request and a vector indicating on which SAPs it was presented. For.indications: The convergence function presents the frame on the SAP(s) indicated by the vector. (It so happens that this is always just one port.) (Infrastructure SAP with port vector) 1 2m

Submission doc.: IEEE 11-13/0938r1 Infrastructure 802.1AC Convergence (Infrastructure SAP with port vector) (ISS) … CUCC C The creation and deletion of upper SAPs are handled by the AP and its security layer. The signaling of these events is a matter not visible outside the system, so may or may not be standardized, at the choice of TGak. Of course, the 802.1AC convergence function also performs any minor mapping required between the ISS and service definitions. 1 2m

Submission doc.: IEEE 11-13/0938r1 P802.11ak infrastructure access (Infrastructure SAP with port vector) (Feel free to suggest better names for this function.) For.requests: The frame has only Destination and Source addresses. Every frame has a Source and Transmitter address both the AP’s MAC address. Using the port vector, the infrastructure access function selects a Destination/Receiver address (either a unicast to a non-AP station or a broadcast to all) and encodes the station list appropriately in the A-MSDU. For.indications: The Transmitter address and whether the frame was encrypted determine the single-bit vector passed up with the frame. (802.11)

Submission doc.: IEEE 11-13/0938r1 What about VLAN tag variances? As will be made clear in P802.1Qbz (and in P802.11ak, if TGak so desires), the purpose of the architecture is to specify outcomes, not internal processes. So, whether variances in VLAN tagging, VID mapping, or priority mapping cause a frame to be replicated above 802.1AC convergence function, or below the infrastructure access function, is irrelevant to IEEE Std 802.1Q or to IEEE Std 802.1AC. If TGak chooses to add such mapping functions to the A-MSDU encoding, it will be documented in IEEE Std ak.

Submission doc.: IEEE 11-13/0938r1 NON-AP STATION SIDE August 2013 Norman Finn, Cisco SystemsSlide 14

Submission doc.: IEEE 11-13/0938r Q AC Convergence ak Non-AP station (only two ports, controlled and uncontrolled) 802.1AC Media Access Method Dependent Convergence Functions Many ISS  Infrastructure SAP + vector of ports ak Non-AP station Vector of ports  1 frame with third MAC address and subset encoding (802.11) (ISS) CUC (Non-AP station SAP with port vector)

Submission doc.: IEEE 11-13/0938r1 Non-AP station 802.1AC Convergence (Non-AP station SAP with port vector) The creation and deletion of upper SAPs are handled by the station and its security layer. The signaling of these events is a matter not visible outside the system, so may or may not be standardized, at the choice of TGak. Of course, the 802.1AC convergence function also performs any minor mapping required between the ISS and service definitions. (ISS) CUC

Submission doc.: IEEE 11-13/0938r1 P802.11ak Non-AP station access For.requests: The frame has only Destination and Source addresses. The port vector simply indicates whether the frame is or is not encrypted. The outer Destination and Receiver addresses are the AP, the Source/Transmitter address the non-AP station. The A-MSDU does not carry any subset encoding. For.indications: Whether or not the frame was encrypted determines the single-bit vector passed up with the frame. (802.11) (Non-AP station SAP with port vector)

Submission doc.: IEEE 11-13/0938r1 A FINAL OPTION August 2013 Norman Finn, Cisco SystemsSlide 18

Submission doc.: IEEE 11-13/0938r1 A final option If preferred by TGak, it would be just as easy to make separate controlled and uncontrolled ports at the interface: Controlled 802.1AC convergence function Controlled ak infrastructure access (802.11) (ISS) … CCC (Infrastruct. SAP w/ port vector) Uncontrolled 802.1AC convergence function Uncontrolled ak infrastructure access (802.11) (ISS) … UC (Infrastruct. SAP w/ port vector) 12m12m CUC

Submission doc.: IEEE 11-13/0938r1 A final option Note that, because the non-AP station has only one SAP for the AP, this effectively reduces the 802.1AC non-AP station convergence function to be exactly the same as the current Portal convergence function. Of course, the anti-reflection part of the subset solution is still required.