1 / 10

Liaison presentation to SC6 in relation to the identifier conflict issue

Liaison presentation to SC6 in relation to the identifier conflict issue. Date: 2011-06-13. Authors:. Agenda. Summary of work to date to resolve identifier conflicts Review IEEE 802.11 Recent Actions

fadhila
Download Presentation

Liaison presentation to SC6 in relation to the identifier conflict issue

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. Liaison presentation to SC6in relation to the identifier conflict issue • Date: 2011-06-13 Authors:

  2. Agenda • Summary of work to date to resolve identifier conflicts • Review IEEE 802.11 Recent Actions • IEEE 802.11 Assigned Number Authority (ANA) has reserved identifier values to enable path forward • Review of the identifier conflicts • Summary of mitigation mechanisms & impacts • Request for confirmation of reserved values • References

  3. 802.11 WG & SC6 have worked together to define short/long terms solutions to identifier conflict issue 802.11 WG noted identifier conflicts Two SC6 NBs responded with partial solution IEEE provided identifiers for long term solution • The 802.11 WG liaised N14494 in Dec 2010 • N14494 described the conflict between WAPI & 802.11 identifiers • 802.11k IE identifier • 802.11e status codes • Both the Swiss &Chinese NBs responded similarly in early 2011 • N14511 (Swiss NB) • N14544 (China NB) • Responses suggest “parameter checking” to distinguish the conflicting IE identifiers • Neither NB suggested a solution for the status code conflicts • The 802.11 WG responded in March 2011 • N14643 • Agreed “parameter checking” can be used to resolve the IE identifier conflict • The 802.11 WG allocated non conflicting identifiers for long term solution of both IE identifier and status code conflicts

  4. Summary of Identifier Conflicts between IEEE 802.11 and WD20011 - 1 • Conflict with IE identifier in IEEE 802.11k (Radio Resource Measurement) • Information Element value “68” is assigned to “BSS AC Access Delay” in 802.11k • Used in WD 20011 for “WAPI Parameter Set” • Conflict with two status codes in IEEE 802.11e (MAC QoS Enhancements) • Status Codes “49” and “50” used in Direct Link Set-up (DLS) • Used in WD20011 for “Unsupported WAPI Parameter Set information element version” and “Invalid WAPI Parameter Set information element capabilities”

  5. Summary of Identifier Conflicts between IEEE 802.11 and WD20011 - 2 • Conflict with three reason codes in IEEE 802.11e, 11n, 11u • “30” - 11u “Requested service not authorized in this location” • “31” – 11n “TS deleted because QoS AP lacks sufficient bandwidth for this QoSSTA due to a change in BSS service characteristics or operational mode (e.g., an HT BSS change from 40 MHz channel to 20 MHz channel)” • “32” – 11e “Disassociated for unspecified, QoS-related reason” • Used in WD20011 for • “30” - “Unsupported WAPI Parameter Set information element version”, • “31” - “Invalid WAPI Parameter Set information element capabilities” and • “32” - “WAI Certificate Authentication failed”

  6. Impact of Identifier Conflicts • The conflicts are not a problem for 802.11 or 8802-11 systems because they are unlikely to ever support WAPI • The conflicts might be a problem for WAPI systems if they make use of advanced features in 802.11-2012 • 8802-11:2005 (same as 802.11-2003) is likely to be replaced by 802.11-2012 very soon • 802.11:2012 incorporates 802.11k and 802.11e. • Short term and long term mitigation mechanisms can be used to address conflicts

  7. Mechanisms exist to mitigate the identifier conflicts • Short term mitigation mechanisms • Implementation “Parameter checking” of IE value (length field) • Implementation context interpretation of Status code, Reason code • Long term mitigation mechanisms • ANA assignment of new IE value (180) • ANA assignment of new status code values (90,91) • Maximum flexibility will be attained by WAPI transitioning to use its own non conflicting IE identifier & status codes • There are various methods that could be specified in ISO/IEC WD 20011 to implement such a transition. • Reference: N14643, N14544, N14511

  8. N14744 proposes to use IE 180 as a “coexistence” indicator • SC6 are free to use the IE in whatever way they choose • IEEE 802.11 WG has no opinion on the use of IE=180 • Mechanism in N14744 should be evaluated on its merits

  9. 802.11 WG requests SC6 to confirm allocation of non conflicting values for long term solution • The 802.11 ANA has reserved IE = 180 for use in ISO/IEC WD 20011 as part of any transition process • The 802.11 ANA has similarly reserved two status codes (90 and 91) for use by WAPI • The ANA assignments are updated frequently, and are available on-line, • Most recent version is here: https://mentor.ieee.org/802.11/dcn/11/11-11-0270-04-0000-ana-database.xls • The 802.11 WG requests that SC6 confirm whether or not SC6 requires the IE identifier and the status codes to remain reserved • Reference: N14643

  10. References • 6N14494, 2010-12-01 • Liaison statement from IEEE 802.11 to JTC1/SC6 in relation to identifiers in proposed WAPI standard • 6N14511, 2010-12-20 • NB if Switzerland comments on 6N14494 • 6N14544, 2011-01-03 • NB of China’s response to 6N14494 • 6N14643, 2011-04-04 • Liaison statement from IEEE 802.11 Working Group to JTC1/SC6 in relation to identifiers in proposed WAPI standard • 6N14744, 2011- 05-18 • NB of Switzerland’s proposal in response to 6N14643 regarding identifiers in WD 20011

More Related