Project IEEE 802 15 Working Group for Wireless

Project: IEEE 802. 15 Working Group for Wireless Personal Area Networks (WPANs) March 2001 doc. : IEEE 802. 15 -01/291 r 0 Submission Title: [WG Liaison Report, No. 14] Date Submitted: [9 Jul 01] Source: [Ian Gifford] Company [Consultant] Address [23 Kelshill Road, MA USA 01863] Voice: [+1 978 251 3451], FAX: [+1 978 251 1437], E-Mail: [giffordi@ieee. org] Re: [-01/215 r 0, etc. ] Abstract: [This Liaison Report is a running Liaison report that is offered to the WG for their consideration. It is only as good as what is provided to the Author…there are many WG Liaisons that are not captured as they are not provided to the Author or Liaison Officer. ] Purpose: [Our Sponsor requested that an official Liaison Officer be added to the WG. This report is for the Sponsor and/or the WG. ] Notice: This document has been prepared to assist the IEEE 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 802. 15. Submission 1 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 IEEE 802. 15 Working Group for Wireless Personal Area Networks™ Liaison Report #14 July 2001 Portland, OR USA Submission 2 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 Contents • • • Liaison Objectives Liaison Summary Liaison Reports Liaison Negotiations Liaison Observations Submission 3 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 Liaison Objectives • Promote the IEEE as a Value Add • Promote the IEEE 802 as a leader in Wireless Standards-Making • Promote P 802. 15 as an expert in WPANs • Request/Receive Draft Standard Submissions from External and Internal (IEEE) from our Liaison activities Submission 4 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 Liaison Summary • Active Liaison List – – – – • – IEEE 802. 1 (/Lindinsky) – IEEE 802. 2 (/Carlson) – ATM Forum WATM (/Delaverson) – Digital Imaging Group (Allen/? ) – DSRC (? /Kurihara) – ETSI BRAN (? /Khun-Jush) – Home. RF Working Group (/Manny) – IETF BOF on Bluetooth over IP (Siep/Atwal, Akers) – Ir. DA (/Mc. Kay) – UWBWG (/Withington) – WAP Forum (/Parrish) – WECA (? ) – WLANA (? /Di. Cillo) Note 1: 802. 15/Liaison TG 1 – BSIG (Gifford/Truntzer) TG 2 – BSIG (Shellhammer/Sizer) TG 3 – BSIG (Barr/Siep) TG 4 – BSIG (Heile/Siep) TG 4 – Zig. Bee Working Group IEEE 802. 11 (? /Kerry) IEEE 802. 16 (? /Roger. M ) IEEE • Standards Activities, Standards Publishing Programs (Gifford/Tatiner) • IEEE Standards Dept. , Balloting Center (Gifford/Kahofer) • Submission Nonactive Liaison List 5 Other Liaisons? Note 2: ? Unknown Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 IEEE 802. 15 Working Group for Wireless Personal Area Networks External Liaison Report Submission 6 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 Bluetooth™ TG 1 Report • Telecon & Meetings – Miscellaneous • E-Mail’s to Bluetooth SIG – 30 May 01 “IEEE 802. 15. 1 - BSIG Word Usage and IEEE Style Manual” request – 27 Jun 01 “WPAN/ LB 11 begins today and closes Friday July 6 at 11 pm edt” alert – Miscellaneous • E-Mail’s from Bluetooth SIG – 18 Jun 01 “BARB review of must 2 shalls” reply – Miscellaneous • Next Steps – Update BSIG PM during/post Session #13/Portland – Bluetooth SIGnal Editor/Publisher and Issue No. 7, 8, 9, etc. , follow up Submission 7 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 Zig. Bee Working Group • The Zig. Bee Working Group a. k. a. PURLnet star network proposal which has PURL LLC, PURL NWK, etc. • Zig. Bee URL – http: //12. 5. 139. 199/ or www. zigbee. org Submission 8 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 IEEE 802. 15 Working Group for Wireless Personal Area Networks Internal Liaison Report Submission 9 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 IEEE Report • Telecon & Meetings – Miscellaneous • E-Mail’s to IEEE – Miscellaneous • E-Mail’s from IEEE – Miscellaneous • Next Steps – Follow up on 802. 15. 1/D 0. 9. 2 + Comments or D 1. 0. 1 for Sponsor Ballot, contact Balloting Center. – Follow up on 802. 15. 1 Handbook request and plan Manuscript due 2 H 01 – Follow up on 802. 15. 1 Draft Std onto IEEE 802 Plus CD-ROM Submission 10 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 Liaison Negotiations • Bluetooth™ SIG – Next BSIG-IEEE 802. 15. 1 Telecon and f 2 f Meeting Dates? • IEEE – 802. 11/802. 15 Interim Meetings? • We need to identify hosts and venue 12 months out, or more. – We need to benchmark our Admin tools i. e. , Balloting Tools, Comment DB, etc. to other IEEE WGs and other SDOs. As well as future proof our Membership DB. Submission 11 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 Liaison Observation #1 – 802. 15 WG Projects…promo? • Wireless 802 WGs – 802. 11 is a single MAC Sublayer/WG. – 802. 16 is a single MAC Sublayer/WG. – …but 802. 15 has 3 MAC Sublayers/WGs. = Draft in process or complete = Draft not defined e. g. , CFP, etc. Submission 12 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 Liaison Observation #1 – 802. 15 WG Projects…promo? Logical Link Control Sublayer { 802. 15. 4 LLC 802. 15. 4 PAR? Medium Access Control Sublayer Physical Layer { { “The data rate will be high enough, 20 Mbps or more (see 13 a), to satisfy a set of consumer multimedia industry needs for WPAN communications. ” 802. 15. 3 PAR Submission “…allow message data in the CAP in order to insure that the TG 3 MAC and TG 4 MAC are compatible. ” Mark. S What’s up w/ the 11 Mbit/s? Source: 802. 15. 3/D 0. 5, pg 127 13 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 Liaison Observation #1 – 802. 15 WG Projects…promo? • Promotion of the various Projects as well as the various PHY Layers, MAC Sublayers, and in the case of TG 4 the 802. 15. 4 LLC is very complex. • The WG needs to have a unified story and each Project needs to have its own story. These promotional stories should be complementary. • Reviewing lessons learned from related WGs is highly suggested e. g. , 802. 3, 802. 11, etc. and SDOs e. g. ETSI BRAN, etc. Submission 14 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 Liaison Observation #2 – 802. 15. 4 LLC? • 802. 15. 4 CFP review… • In reviewing – 01/272 r 3, it appears this contribution is promoting the PURL LLC as 802. 15. 4 LLC BUT you need to sign Zig. Bee agreement to access the Zig. Bee Spec. which includes PURL LLC a. k. a. 802. 15. 4 LLC. • Also I believe this 802. 15. 4 LLC is out of scope for the 802. 15. 4 PAR? PHY/MAC only. Submission 15 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 Liaison Observation #2 – 802. 15. 4 LLC? • “…-01/272 r 3 slide 27 & 28, suggests the upper layers are being invented by an 802 group. There is the possibility that 802. 2 could adopt these alternate topological LLC methodologies, but 802. 2 must define it, not 802. 15. 4. 802. 51. 4 can SUGGEST it, but it is not for them to decide. • It is totally incorrect and unacceptable for an 802 WG to violate the fundamental premises of LMSC. Any and all 802 stack components must use the common 802. 2 LLC. Submission 16 Ian Gifford, Consultant

Source: -01/272 r 3 [01272 r 3 P 802 -15_TG 4 -Unified-MAC-Proposal. ppt] March 2001 doc. : IEEE 802. 15 -01/291 r 0 Liaison Observation #2 – 802. 15. 4 LLC? Application Convergence Layer (ACL) NWK A NWK B NWK C IEEE 802. 2 LLC, Type I IEEE 802. 15. 4 LLC Maintained by IEEE 802. 15. 4 MAC IEEE 802. 15. 4 868/915 MHz PHY Submission Maintained by Zig. Bee Working Group IEEE 802. 15. 4 915/2400 MHz PHY 17 Ian Gifford, Consultant

March 2001 doc. : IEEE 802. 15 -01/291 r 0 Previous Liaison Reports On Web, Server & Flash Card(s) • • • • Report #1 -99/005 r 0 [99005 r 0 P 802 -15_Liaison-Report. ppt] Report #2 -99/029 r 0 [99029 r 0 P 802 -15_Liaison-Report-2. ppt] Report #3 -99/063 r 1 [99063 r 1 P 802 -15_Liaison-Report-3. ppt] Report #4 -99/124 r 0 [99124 r 0 P 802 -15_Liaison-Report-4. ppt] Report #5 -99/174 r 0 [99174 r 0 P 802 -15_WG-Liaison-Report-5. ppt] Report #6 -00/037 r 1 [00037 r 1 P 802 -15_WG-Liaison-Report-6. ppt] Report #7 -00/118 r 0 [00118 r 1 P 802 -15_WG-Liaison-Report-7. ppt] Report #8 -00/182 r 0 [00182 r 0 P 802 -15_WG-Liaison-Report-8. ppt] Report #9 -00/266 r 0 [00266 r 0 P 802 -15_WG-Liaison-Report-9. ppt] Report #10 -00/340 r 2 [00340 r 2 P 802 -15_WG-Liaison-Report-10. ppt] Report #11 – 01/020 r 1 [01020 r 1 P 802 -15_WG-Liaison-Report-11. ppt] Report #12 – 01/112 r 0 [01112 r 1 P 802 -15_WG-Liaison-Report-12. ppt] Report #13 – 01/215 r 0 [01215 r 0 P 802 -15_WG-Liaison-Report-13. ppt] Submission 18 Ian Gifford, Consultant