Sept 2004 doc IEEE 802 15 04 0640

Sept 2004 doc. : IEEE 802. 15 -04 -0640 -01 -0000 Project: IEEE P 802. 15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [802 Architecture Meeting and Work Items] Date Submitted: [15 -Nov-04] Source: [Tom Siep] Company [TMS Associates, LLC] Address [Suite 100, ms 365, 1802 Pleasant Valley Dr, Garland, TX, USA, 75040] Voice: [+1 972 496 0766], FAX: [+1 469 366 1480], E-Mail: [tom. siep@ieee. org] Re: [Update to correct heading and description page. ] Abstract: [Report on 802 Architecture meeting and call for Ad Hoc meeting to address work items. ] Purpose: [Call for Ad Hoc. ] Notice: This document has been prepared to assist the IEEE P 802. 15. 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. Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P 802. 15. Submission 1 Tom Siep, TMS Assoicates, LLC

Sept 2004 doc. : IEEE 802. 15 -04 -0640 -01 -0000 802 Architecture Meeting and Work Items Tom Siep TMS Associates, LLC 802. 15 Liaison to 802 Architecture Committee Submission 2 Tom Siep, TMS Assoicates, LLC

Sept 2004 doc. : IEEE 802. 15 -04 -0640 -01 -0000 Intent for 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. Submission 3 Tom Siep, TMS Assoicates, LLC

Sept 2004 doc. : IEEE 802. 15 -04 -0640 -01 -0000 Known issues – 802. 15 • Are PANs different from WLANs? – We hope the answer is “No” (wrt the MAC service) • Security – What functionality is needed – Who does what aspect • Bridging compatibility – handling of multicasts, no clause 6 section for. 1 D • LLC – acts as a block to passing additional (e. g. , Qo. S) parameters • Mesh (not the same as the. 11 issue though) • Qo. S • Architectural consistency across three MACs • (Signal) Power/channel management Submission 4 Tom Siep, TMS Assoicates, LLC

Sept 2004 doc. : IEEE 802. 15 -04 -0640 -01 -0000 Proposals for resolution • Due diligence issues – need to fix 802 procedures – TJ to propose to SEC that the rules forwarding to SB & Rev. Com be strengthened – WGs should review projects against PAR/5 C requirements during the development cycle • Each WG: – – Submission Prioritize issues Characterize the problem Propose approach to resolve, or identify as intractable Identify other groups (802 or external) that may be affected 5 Tom Siep, TMS Assoicates, LLC

Sept 2004 doc. : IEEE 802. 15 -04 -0640 -01 -0000 Ad Hoc Meeting on Architecture • James Gilb, Tom Siep facilitating • Tuesday, 7 pm • Director’s room, Hyatt Submission 6 Tom Siep, TMS Assoicates, LLC