1. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 1 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-05-0273-00-0000- Wireless_Architecture_Ad_Hoc_meeting_notes.ppt Title: Wireless Architecture Ad Hoc meeting notes Date Submitted: March, 19, 2005 Presented at IEEE 802.21 session #8 in Cairns Authors or Source(s): Tom Siep, tom.siep@csr.com Cambridge Silicon Radio 2425 N. Central Expressway, Suite 1000, Richardson, TX 75080 USA

2. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 2 IEEE 802.21 presentation release statements This document has been prepared to assist the IEEE 802.21 Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.21. The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/guide.html> Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3 http://standards.ieee.org/board/pat/guide.html

3. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 3 Abstract The following slides document the Wireless Architecture Ad Hoc meeting held the evening of 16May05 at the Cairns Interim meeting

4. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 4 Agenda for Ad Hoc Tuesday Evening PURPOSE: Brief ad hoc attendees and prepare for Plenary meeting of 802.1 Architecture Consolidate 802.wireless community’s architecture issues –Quality of Service –Security –Management –Other? Determine if we, as the wireless 802 community, want to: –Present a common set of issues –Request formation of a TAG to address architecture issues

5. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 5 Attendees (1 of 2) Last NameFirst NameEmail AddressWG OdmanKnutkodman@pulselink.net15 LushengJilji@research.att.com11 MillerBobrrm@att.com11 WorstellHarryhworstell@att.com11 FalkLarslars.p.falk@-------.com11 ButtarAlistairalistair.buttar@jp.panasonic.com21 TakashiAramakiaramaki.takashi@jp.panasonic.com11 KeigoAsoaso.keigo@jp.panasonic.com21 McInnisMikemichael.d.mcinnis@boeing.com15 NjedjonEriceric.njedjon@francetelecom.com16 CallawayEded.callaway@motorola.com15 ShusakuShimadashusaku@ieee.org15 HaixiangHehaixiang@nortel.com11 GodfreyTimtim.godfrey@conerant.com11 ShinkichiIkedaikeda.shinkichi@jp.panasonic.com21 LachHong-Yonhong-yon.lach@motorola.com21 HiertzGuido R.hiertz@ieee.org11 LotharSkibovlsr@comnets.--------.de11 O'HaraBobbob.ohara@cisco.com11 LiuXiaoyuxiaoyu.liu@samsung.com21

6. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 6 Attendees (2 of 2) Last NameFirst NameEmail AddressWG WilliamsMichaelmichael.g.williams@nokia.com21 BarberPhillippbarber@broadbandmobiletech.com16 RajkumarAjayajayrajkumar@lucent.com21 KimRonny (Yong-Ho)ronnykim@lge.com21 HendersonG. Scottshenderson@rim.com11 EngwerDarwindengwer@nortel.com11 ZunigaJuan Carlosj.c.zuniga@ieee.org11 ChouiwardGeraldgerald.chouiward@crc.ca22 DecuirJoejoe@mcci.com15 AstrinArtartastrin@aol.com11 BahrMichaelbahr@siemens.com11 ZweisJohnnyjustjohnny@apple.com11 YongwonKwakyongwon@ige.com21 JinLeejins978@ige.com21 JeomSoon Iksijeon@etri.re.kr22 SongMyungsunmssong@etri.re.kr22 KimChang-Joocjkim@etri.re.kr22 TanTeik-Kheongtktan@ieee.org22 KiernanBrianbrian.kiernan@-----digital.com16 HunterDavidhunter@timefactor.com21

7. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 7 Intent for 802.1 Arch Committee Improve alignment between WG projects and existing 802 architecture by: –Identifying current problems, omissions, conflicts, ramifications, and their potential resolution –Identifying potential refinements or changes to the architecture –Providing a regular forum in which such discussion can take place, in a lower pressure environment than is possible during the core Plenary cycle.

8. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 8 Proposals for resolution Due diligence issues – need to fix 802 procedures –TJ to propose to SEC that the rules for forwarding to SB & RevCom be strengthened –WGs should review projects against PAR/5C requirements during the development cycle Each WG: –Prioritize issues –Characterize the problem –Propose approach to resolve, or identify as intractable –Identify other groups (802 or external) that may be affected

9. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 9 Pending 802.1 PARs Security –This standard specifies unique per-device identifiers (DevID) and the management and cryptographic binding of a device to its identifiers, the relationship between an initially installed identity and subsequent locally significant identities, and interfaces and methods for use of DevIDs with existing and new provisioning and authentication protocols. –See 11-05-xxxx-00-0000-Summary_of_PAR-5C_of_P802-1AL.ppt Management of RF –This standard specifies protocols, procedures, and managed objects to support Radio Frequency (RF) management across IEEE 802 wireless Media Access Control (MAC) layers. –See 11-05-xxxx-00-0000-Summary_of_PAR-5C_of_P802-1AM.ppt

10. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 10 Discussions at Architecture Meeting ~60 people present (40 signed attendance sheet) Discussion turned initially to the 802.1AM PAR –There was concern that 802.1 may not have the expertise to do the RF management task –Question: Is management of an RF system fundamentally different than a wired system? Yes. –Straw poll: “Do you favor approval of the 802.1AM PAR?” yes 13; no 20; reserve judgment 13 Discussion then turned to what wireless groups need in common –Straw poll: “Is a common language needed for wireless for communicating operational characteristics and status of dissimilar wireless systems?” yes 23; no 1; reserve judgement15

11. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 11 Output from Wireless Architecture Discussions Establish a joint wireless systems study group to address common 802 wireless issues consisting of representatives of the various wireless groups –Focus on cooperation between wireless groups –Might lead to formation of a TAG or WG or TGs within a WG or a standing committee –Support coexistence or handoff efforts, not duplicating –Investigate a common language for communicating operational characteristics and status of dissimilar wireless systems Action: representatives from all wireless groups to present the above request for approval

12. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 12 Discussions at Architecture Meeting ~60 people present (40 signed attendance sheet) Discussion turned initially to the 802.1AM PAR –There was concern that 802.1 may not have the expertise to do the RF management task –Question: Is management of an RF system fundamentally different than a wired system? Yes. –Straw poll: “Do you favor approval of the 802.1AM PAR?” yes 13; no 20; reserve judgment 13 Discussion then turned to what wireless groups need in common –Straw poll: “Is a common language needed for wireless for communicating operational characteristics and status of dissimilar wireless systems?” yes 23; no 1; reserve judgement15

13. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 13 Output from Wireless Architecture Discussions Establish a joint wireless systems study group to address common 802 wireless issues consisting of representatives of the various wireless groups –Focus on cooperation between wireless groups –Might lead to formation of a TAG, WG, or TGs within a WG; or perhaps a standing committee –Support coexistence or handoff efforts, not duplicating –Investigate a common language for communicating operational characteristics and status of dissimilar wireless systems Action: representatives from all wireless groups to present the above request for approval

14. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 14 BACKUP SLIDES: 802.15 Inputs to Arch Ad Hoc Presented at Monterey

15. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 15 Prioritized issues – 802.15 Management –LLC – acts as a block to passing additional (e.g., QoS) parameters –QoS –(Signal) Power/channel management Bridging compatibility –handling of multicasts, no clause 6 section for.1D

16. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 16 LLC – acts as a block to passing additional (e.g., QoS) parameters All 3 MAC need LLC support to requests to create/modify/terminate streams based on QoS parameters Data needs to be able to be associated with a stream at the MAC SAP QoS changes need to be communicated to the higher layers Need to be able to inquire QoS characteristics of remote nodes

17. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 17 QoS Block asynchronous data –Need block size to plan and allocate resources

18. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 18 (Signal) Power/channel management Need a way to pass (up and down) information that is important to wireless, for example –Transmit power –Regulatory domain –Signal quality –Coexistence information –Other Must be extensible

19. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 19 Bridging compatibility – handling of multicasts, no clause 6 section for.1D Compatibility with.1D –15.1a – Bridging is handled in BNEP, which maps to Ethernet. –15.3 – Annex A (normative) specifies compatibility –15.4 – Annex A (normative) specifies compatibility Multicasts –15.1a – does not do multicast –15.3 – Had multicast, being revised in current work –15.4 – Had broadcast, being revised to include multicast in current work

20. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 20 Other Groups Affected LLC – acts as a block  802.1 and 802.2 QoS  802.1 and 802.2 (Signal) Power/channel management  802.1 and 802.2 Bridging compatibility – internal problem being worked

21. doc.: IEEE 802.21-05/0273-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon Radio Slide 21 Work to be done by 802.15 Form plans to solve issues Determine feasibility of plans Study proposal to use IETF model for QoS – will it work for.15 TGs? Characterize management function needs Can’t do bridging 64 to 48 bit addresses – are we OK with this?