1May 2004 IEEE 802.15-04-0289r0 1 IEEE 802.15 Wireless Personal Area Networks 2 Project IEEE 802.15 Working Group for WPANs Title IEEE 802.15.3b Teleconference minutes from May to July

Date [June 9, 2004] Submitted

Sources Jim Allen Voice (585) 214-2465 Appairent Technologies, Inc. Fax: 150 Lucius Gordon Dr. E-mail: [email protected] Rochester, NY 14586 Re: []

Abstract [IEEE 802.15.3b TG ad hoc meeting minutes]

Purpose [Minutes of the 802.15.3b Task Group at hoc teleconference calls from May’s interim meeting to July’s Plenary meeting.]

Notice This document has been prepared to assist the IEEE P802.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 P802.15.

3 4 Table of Contents (Hot Linked) 5 6 June 7, 2004...... 2

7

2Submission Page 1 of 7 Jim Allen, Appairent Technologies 3May 2004 IEEE 802.15-04-0289r0

8June 7, 2004 9 10Attendees: 11 Jay Bain 12 James Gilb 13 Allen Heberling 14 Bill Shvodian 15 Jim Allen 16 Knut Odman 17 18 19Called to order at 11:06 EDT by Gilb. 20 21 22Agenda: 23 24 - Administrative issues: 25 - Schedule for Portland 26 - Tuesday all day (four sessions) 27 - Wednesday afternoon (two sessions) 28 - Thursday morning and evening (one session in the morning, evening if required) 29 - Do we need more time? 30 - All comments due by July 9th, 12 p.m. PDT. 31 - Comment submission form issues? 32 - Items to discuss on future calls 33 - Technical stuff 34 - Multiple CAPs/MCTAs in superframe 35 - Suggestions for Multicast? Can we get a small group to work on a proposal? 36 - Other off-line work? 37 - Adjourn 38 39Minutes: 40 41Discussed the July Portland details. 42 · Need to request additional meeting times: Monday AM 1 and 2, PM 2 and evening, 43 Tuesday evening, and Thursday PM 1 and 2 so we can get as much done before Berlin as 44 possible. 45 · Arrange a co-session with TG5 for Thursday at 10:30 a.m. 46 · Barr needs to announce the Monday morning ad hoc meeting by June 11 as well as to 47 post a tentative agenda. 48 · Barr needs to request room for at least 25-30 people (note, TG3b is already down for 50 49 people)

4Submission Page 2 of 7 Jim Allen, Appairent Technologies 5May 2004 IEEE 802.15-04-0289r0 50 · Barr needs to send out a notice to the reflector that all comments are due in Comment 51 Resolution format (using the tool or ASCII input form) by noon PDT, July 9th 2004 and 52 needs to point to where the tool is located on the web. 53 54 55 56Technical discussion: 57 58 We briefly discussed and scheduled the following items. 59 60 In next meeting (2 weeks from now) we need to start discussions on Multiple CAPs/MCTAs 61 in superframe. A general discussion followed. 62 63 Access methods were discussed. If broadcast-to-broadcast is done, it needs to be the same 64 access method used by the PNC so it’s consistent throughout the piconetwork. 65 66 Need to discuss (in two weeks) reserving FF value for stream index. We want to make sure 67 this was resolved. 68 69 At the same meeting, discuss allowing devices to opt-in or opt-out of listening to broadcast 70 slots and decide how that relates to multicast groups 71 72Regarding Multicast, how do we get to a coherent proposal? Separate call? Email? Lack of well- 73defined multicast is one issue people use to comment against 15.3. Heberling will start June 7, 742004 75 76Attendees: 77 Jay Bain 78 James Gilb 79 Allen Heberling 80 Bill Shvodian 81 Jim Allen 82 Knut Odman 83 84 85Called to order at 11:06 EDT by Gilb. 86 87 88Agenda: 89 90 - Administrative issues: 91 - Schedule for Portland 92 - Tuesday all day (four sessions) 93 - Wednesday afternoon (two sessions) 94 - Thursday morning and evening (one session in the morning, evening if required) 95 - Do we need more time?

6Submission Page 3 of 7 Jim Allen, Appairent Technologies 7May 2004 IEEE 802.15-04-0289r0 96 - All comments due by July 9th, 12 p.m. PDT. 97 - Comment submission form issues? 98 - Items to discuss on future calls 99 - Technical stuff 100 - Multiple CAPs/MCTAs in superframe 101 - Suggestions for Multicast? Can we get a small group to work on a proposal? 102 - Other off-line work? 103 - Adjourn 104 105Minutes: 106 107Discussed the July Portland details. 108 · Need to request additional meeting times: Monday AM 1 and 2, PM 2 and evening, 109 Tuesday evening, and Thursday PM 1 and 2 so we can get as much done before Berlin as 110 possible. 111 · Arrange a co-session with TG5 for Thursday at 10:30 a.m. 112 · Barr needs to announce the Monday morning ad hoc meeting by June 11 as well as to 113 post a tentative agenda. 114 · Barr needs to request room for at least 25-30 people (note, TG3b is already down for 50 115 people) 116 · Barr needs to send out a notice to the reflector that all comments are due in Comment 117 Resolution format (using the tool or ASCII input form) by noon PDT, July 9th 2004 and 118 needs to point to where the tool is located on the web. 119 120 121 122Technical discussion: 123 124 We briefly discussed and scheduled the following items. 125 126 In next meeting (2 weeks from now) we need to start discussions on Multiple CAPs/MCTAs 127 in superframe. A general discussion followed. 128 129 Access methods were discussed. If broadcast-to-broadcast is done, it needs to be the same 130 access method used by the PNC so it’s consistent throughout the piconetwork. 131 132 Need to discuss (in two weeks) reserving FF value for stream index. We want to make sure 133 this was resolved. 134 135 At the same meeting, discuss allowing devices to opt-in or opt-out of listening to broadcast 136 slots and decide how that relates to multicast groups 137 138 Regarding Multicast, how do we get to a coherent proposal? Separate call? Email? Lack of 139 well-defined multicast is one issue people use to comment against 15.3. Heberling will start 140 by doing some research and perhaps drafting a proposal. 141

8Submission Page 4 of 7 Jim Allen, Appairent Technologies 9May 2004 IEEE 802.15-04-0289r0 142 143New business - 144 We need to start promoting 15.3 and need to discuss this process. Need to 145 discuss a group article next week. We’ll have an ad hoc meeting next week 146 that will be scheduled via email. Bill Shvodian will send out the call contact 147 information for the 802.15.3 publicity sub-committee conference call. 148 149The next 3b meeting is in two weeks. James Gilb will send out the call information for the TG3b 150technical call. 151 152Adjourned 12:05 a.m. EDT . 153 154June 7, 2004 155 156Attendees: 157 Jay Bain 158 James Gilb 159 Allen Heberling 160 Bill Shvodian 161 Jim Allen 162 Knut Odman 163 164 165Called to order at 11:06 EDT by Gilb. 166 167 168Agenda: 169 170 - Administrative issues: 171 - Schedule for Portland 172 - Tuesday all day (four sessions) 173 - Wednesday afternoon (two sessions) 174 - Thursday morning and evening (one session in the morning, evening if required) 175 - Do we need more time? 176 - All comments due by July 9th, 12 p.m. PDT. 177 - Comment submission form issues? 178 - Items to discuss on future calls 179 - Technical stuff 180 - Multiple CAPs/MCTAs in superframe 181 - Suggestions for Multicast? Can we get a small group to work on a proposal? 182 - Other off-line work? 183 - Adjourn 184 185Minutes: 186

10Submission Page 5 of 7 Jim Allen, Appairent Technologies 11May 2004 IEEE 802.15-04-0289r0 187Discussed the July Portland details. 188 · Need to request additional meeting times: Monday AM 1 and 2, PM 2 and evening, 189 Tuesday evening, and Thursday PM 1 and 2 so we can get as much done before Berlin as 190 possible. 191 · Arrange a co-session with TG5 for Thursday at 10:30 a.m. 192 · Barr needs to announce the Monday morning ad hoc meeting by June 11 as well as to 193 post a tentative agenda. 194 · Barr needs to request room for at least 25-30 people (note, TG3b is already down for 50 195 people) 196 · Barr needs to send out a notice to the reflector that all comments are due in Comment 197 Resolution format (using the tool or ASCII input form) by noon PDT, July 9th 2004 and 198 needs to point to where the tool is located on the web. 199 200 201 202Technical discussion: 203 204 We briefly discussed and scheduled the following items. 205 206 In next meeting (2 weeks from now) we need to start discussions on Multiple CAPs/MCTAs 207 in superframe. A general discussion followed. 208 209 Access methods were discussed. If broadcast-to-broadcast is done, it needs to be the same 210 access method used by the PNC so it’s consistent throughout the piconetwork. 211 212 Need to discuss (in two weeks) reserving FF value for stream index. We want to make sure 213 this was resolved. 214 215 At the same meeting, discuss allowing devices to opt-in or opt-out of listening to broadcast 216 slots and decide how that relates to multicast groups 217 218 Regarding Multicast, how do we get to a coherent proposal? Separate call? Email? Lack of 219 well-defined multicast is one issue people use to comment against 15.3. Heberling will start 220 by doing some research and perhaps drafting a proposal. 221 222 223New business - 224 We need to start promoting 15.3 and need to discuss this process. Need to 225 discuss a group article next week. We’ll have an ad hoc meeting next week 226 that will be scheduled via email. Bill Shvodian will send out the call contact 227 information for the 802.15.3 publicity sub-committee conference call. 228 229The next 3b meeting is in two weeks. James Gilb will send out the call information for the TG3b 230technical call. 231

12Submission Page 6 of 7 Jim Allen, Appairent Technologies 13May 2004 IEEE 802.15-04-0289r0 232Adjourned 12:05 a.m. EDT . 233 234 by doing some research and perhaps drafting a proposal. 235 236 237New business - 238 We need to start promoting 15.3 and need to discuss this process. Need to discuss a 239 group article next week. We’ll have an ad hoc meeting next week that will be scheduled 240 via email. Bill Shvodian will send out the call contact information for the 802.15.3 241 publicity sub-committee conference call. 242 243The next 3b meeting is in two weeks. James Gilb will send out the call information for the TG3b 244technical call. 245 246Adjourned 12:05 a.m. EDT . 247 248

14Submission Page 7 of 7 Jim Allen, Appairent Technologies