doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 –...

24
July 2009 doc.: IEEE 802.11-09/0677r5 IEEE P802.11 Wireless LANs TGv Teleconference Minutes June-July 2009 Date: 2009-07-10 Author(s): Name Affiliation Address Phone email Dorothy Stanley Aruba Networks 1332 Crossman Ave Sunnyvale, CA 94089 +1-630-363- 1389 dstanley@aruba networks.com Submission page 1 Dorothy Stanley (Aruba Networks) Abstract This document contains the meeting notes from the TGv teleconference held June 16 th , June 19 th , June 23 rd , June 26 th , June 30 th , and July 10 th 2009.

Transcript of doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 –...

Page 1: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

IEEE P802.11Wireless LANs

TGv Teleconference Minutes June-July 2009

Date: 2009-07-10

Author(s):Name Affiliation Address Phone email

Dorothy Stanley Aruba Networks 1332 Crossman Ave

Sunnyvale, CA 94089 +1-630-363-1389 [email protected]

Submission page 1 Dorothy Stanley (Aruba Networks)

AbstractThis document contains the meeting notes from the TGv teleconference held June 16 th, June 19th, June 23rd, June 26th, June 30th, and July 10th 2009.

Page 2: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

June 16, 2009 Teleconference

Agenda, from e-mail notice:

1. Call to Order, Patent Notification2. Editor Update 3. Comment Resolution – LB150, see https://mentor.ieee.org/802.11/dcn/09/11-09-0676-00-000v-lb-150-comments.xls 4. Adjourn

Please review the documents at the following links prior to the call:

-  IEEE Patent Policy - http://standards.ieee.org/board/pat/pat-slideset.ppt-  Affiliation FAQ - http://standards.ieee.org/faqs/affiliationFAQ.html-  Anti-Trust FAQ - http://standards.ieee.org/resources/antitrust-guidelines.pdf -  Ethics - http://www.ieee.org/portal/cms_docs/about/CoE_poster.pdf

Notes – Tuesday, June 16th, 2009

Attendees: Alex Ashley (NDS), Gabor Bajko (Nokia), Mark Hamilton (Polycomm), Emily Qi (Intel), Dorothy Stanley (Aruba Networks), Allan Thomson (Cisco), Qi Wang (Broadcom), Joshua Zhau (Atheros)

1. Chair called meeting to order: 12:05 Eastern

Chair called attention to the patent policy slides. Are there any questions on the slides?None

Chair asked: Are there any patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) that the participant believes may be essential for the use of that standard? None brought forward

Are there any additions to the proposed agenda? No changes proposed.

2. TG Status & Editor Report

LB150 on Draft 6.0 passed, with an approval of 89.5%. We have 140 comments, 93 technical and 47 editorial. The goal is to go out for the next LB and request conditional approval for going to Sponsor Ballot from the July meeting. We have additional conference calls scheduled:

– Tuesday, June 16, 23, 30, Noon Eastern, 2 hours– Friday, June 19, 26, July 10 Noon Eastern, 2 hours

Dorothy will follow-up with “no” voters who didn’t submit comments on LB150 to determine if their votes have changed, or which comments are still unresolved.

Emily will incorporate proposed resolutions for the editorial comments into D6.01, and bring any comments that she defers for discussion on an upcoming conference call. She has also requested ANA number assignments from Terry Cole; these should be available within a week or so, and will be incorporated into Draft 6.01. Dorothy has requested Mandatory Editorial Coordination (MEC) from IEEE staff; mandatory MEC items must also be incorporated before going to SB. MEC input should be received July 1.

Submission page 2 Dorothy Stanley (Aruba Networks)

Page 3: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

CID 112 is mis-categorised, it should be in STA Statistics rather than Multicast Diagnostics; Emily will incorporate this change in the next revision of the spreadsheet.

3. Comment resolutions

Discussion on the FMS category comment.

- CID 111 – The rate field was added in 7.3.1.18 so that additional capabilities, not just FMS can use the field. This field has a different purpose than the rate field in the phy header; it is used for example to negotiate desired rates. Also “rate” has been broadened in TGn. Agree to keep the general field. Qi to review text to see if she recommends renaming the field.

Discussion on select Location category comments:

- CID 9 – Text in 7.3.2.22.13 refers to a public URI field. Proposed resolution is to re-word to remove reference; reference is not needed for our use. The upper level application will need to know how to encode specific location values for a service, but we are providing the transport of a URI only. Agree with this approach, Allan to prepare text.

- CIDs 113, 114 – When the bit fields were added, the use case was Emergency Services. Usage can actually be broader. No change to functionality/operation is suggested/made, only modification of the name of the field. Agree to delete “ES”.

- CID 44 and similar – Currently have XYZ accuracy fields in the Civic location subelement. Propose to remove the fields, since submissions in the IETF will incorporate both location and accuracy values – no need to split the info over two specifications. Agree to this approach, Allan to provide editorial instructions for the deletion.

Discussion on General category comments:

- CIDs 25, 101, 102 – Commenter asks for an explanation of why data frames rather than action frames are used for the event and diagnostic frames. Agree to add a sentence or so to the text on motivation –to enable delivery of the frames to be prioritized. Dorothy will draft proposed text. Also identified editorial improvements to the existing text.

Discussion on TCLAS category comments:

- CIDs 130, 132 – Agree to decline the comment. The restriction on TCP/UDP is from the base spec. Group agreed to not modify the baseline, commenter can submit to TGmb.

- CID 133 – Yes, Types 1 and 4 are similar, 4 removes the restriction that is present in type 1. Again, no desire to change the deployed/baseline types.

- CID 134 – Agree with comment.

Discussion on the TIM Broadcast category comment:

- CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need to account for the multiple BSSID case, re-word, no change in functionality.

Discussion on Event category comments:

- CID 23 – Agree that text needs to be changed – at least one element with zero or more subelements.

- CID 30 – Agree to explicitly define 0 as indicating as many elements as the STA can provide.- CID 116 – Agree to the suggestion, need to include the editing instructions.- CIDs 117, 119 – No text change needed, point the commenter to existing text.- CID 118 – Agree to rename the field to be more specific.

Submission page 3 Dorothy Stanley (Aruba Networks)

Page 4: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

- CIDs 135, 138 – discuss next time

4. Adjourned at 1410 Eastern. The next conference call is Friday, June 19th , Noon Eastern

1-719-457-6209Code: 712-821-86412 hours

Friday – June 19th – FMS, Location, Time Advertisement, remaining Event commentsTuesday – June 23rd – Directed Multicast, Sleep Mode, Channel Usage, Multicast Diagnostics, Virtual AP, DiagnosticsFriday - June 26th – TBD Tuesday June 30th – TBDFriday July 10th - TBD

Still need to determine timeslot for: Timing Measurement, STA Statistics, Editorials, unresolved CIDs from previous LBs

Submission page 4 Dorothy Stanley (Aruba Networks)

Page 5: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

June 19, 2009 Teleconference

Agenda, from e-mail notice:

1. Call to Order, Patent Notification2. Editor Update 3. Comment Resolution – LB150, see https://mentor.ieee.org/802.11/dcn/09/11-09-0676-00-000v-lb-150-comments.xls - FMS, Location, Time Advertisement, remaining Event comments, others as time permits.4. Adjourn

Please review the documents at the following links prior to the call:

-  IEEE Patent Policy - http://standards.ieee.org/board/pat/pat-slideset.ppt-  Affiliation FAQ - http://standards.ieee.org/faqs/affiliationFAQ.html-  Anti-Trust FAQ - http://standards.ieee.org/resources/antitrust-guidelines.pdf -  Ethics - http://www.ieee.org/portal/cms_docs/about/CoE_poster.pdf

Notes – Friday, June 19th, 2009

Attendees: Gabor Bajko (Nokia), Emily Qi (Intel), Dorothy Stanley (Aruba Networks), Allan Thomson (Cisco), Qi Wang (Broadcom)

1. Chair called meeting to order: 12:05 Eastern

Chair called attention to the patent policy slides. Are there any questions on the slides?None

Chair asked: Are there any patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) that the participant believes may be essential for the use of that standard? None brought forward

Are there any additions to the proposed agenda? No changes proposed.

2. TG Status & Editor Report

Dorothy has e-mailed the “no” voters who voted “no” on LB146 and didn’t submit comments on LB150 to determine if their votes have changed, or which comments are still unresolved.

3. Comment resolutions

Discussion on the FMS category comment, see https://mentor.ieee.org/802.11/dcn/09/11-09-0685-00-000v-lb150-comments-fms.xlsx .

- CID 111 – Reviewed the proposed decline reason. Agree to keep the general field. TGz can potentially use this field, along with the TGv location track notification capability. Agree with proposed resolution with Qi to review current text and potentially proposed additional changes.

Discussion on the Location category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0684-00-000v-lb150-comments-location.xlsx .

- CIDs 9, 51 - Agree with proposed resolution- CID 29 – Change to decline; RFC4776 does include the latest binary representation fields.

Submission page 5 Dorothy Stanley (Aruba Networks)

Page 6: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

- CIDs 43, 68 – Long discussion on the new format and the right place to have it specified. Agree that an additional format is required. Agree that best solution is to re-use an existing definition. Discussion on pros and cons of IETF versus 3GPP as venues for the definition. Concern about prior IETG geopriv discussion to not specify detailed binary representation. Would be used by other applications though, including LLDP-MED. Agree to start with IETF, develop liaison letter requesting development of binary representation there. If not successful, consider other venues, including 3GPP. Change to counter with this explanation.

- CID 44 – Agree with proposed resolution.- CIDs 53, 54 – agree with proposed resolution- CID 67 – Agree with the decline, modifications to the reason.- CID 69 – Agree to decline, add reference to resolution of CID 44, have all related fields together- CID 70 – Start with this one next time.

Discussion on the General category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0689-00-000v-lb-150-resolutions-general-et-al.xls .

- CIDs 25, 101, 102 – Agree with proposed resolution

Discussion on the TCLAS category comment, see https://mentor.ieee.org/802.11/dcn/09/11-09-0689-00-000v-lb-150-resolutions-general-et-al.xls . Dorothy to e-mail proposed resolutions to the commenter for follow-up.

- CID 130 – Agree with decline, changes to decline reason- CIDs 132, 133, 134 – Agree with proposed resolution

Discussion on the Tim Broadcast category comment, see https://mentor.ieee.org/802.11/dcn/09/11-09-0689-00-000v-lb-150-resolutions-general-et-al.xls .

- CID 89 – Agree with proposed resolution

Discussion on Event category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0689-00-000v-lb-150-resolutions-general-et-al.xls .

- CID 23, 30, 116, 117, 118, 119 – Agree with proposed resolutions- CID 135 – Agree to decline, current encoding is more efficient than that proposed by the

commenter.- CID 138 – Agree to counter, generalizing the transition reason.

Discussion on Diagnostics category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0689-00-000v-lb-150-resolutions-general-et-al.xls .

- CID 6, 107, 120, 121, 128, 139 – Agree with proposed resolutions

Discussion: Agenda for July – Anticipate being able to prepare resolutions to nearly all of the LB150 comments on the conference calls; may have additional comments from commenters on their resolutions, as we determine the list of unresolved coments. Agreed to release Monday AM ad-hoc and Tuesday evening timeslots.

Tuesday – June 23rd – Any Editorials, Directed Multicast, Sleep Mode, Channel Usage, Multicast Diagnostics, Virtual AP, Location (continued), Time Advertisement

Friday - June 26th – Timing Measurement, STA Statistics, others as availableTuesday June 30th – TBDFriday July 10th – TBD

Submission page 6 Dorothy Stanley (Aruba Networks)

Page 7: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

4. Adjourned at 1345 Eastern. The next conference call is Tuesday, June 23rd , Noon Eastern

1-719-457-6209Code: 712-821-86412 hours

Submission page 7 Dorothy Stanley (Aruba Networks)

Page 8: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

June 23, 2009 Teleconference

Agenda, from e-mail notice:

1. Call to Order, Patent Notification2. Editor Update 3. Comment Resolution – LB150, see https://mentor.ieee.org/802.11/dcn/09/11-09-0676-00-000v-lb-150-comments.xls - Editorials, Directed Multicast, Sleep Mode, Channel Usage, Multicast Diagnostics, Virtual AP, Location (continued), Time Advertisement

4. Adjourn

Please review the documents at the following links prior to the call:

-  IEEE Patent Policy - http://standards.ieee.org/board/pat/pat-slideset.ppt-  Affiliation FAQ - http://standards.ieee.org/faqs/affiliationFAQ.html-  Anti-Trust FAQ - http://standards.ieee.org/resources/antitrust-guidelines.pdf -  Ethics - http://www.ieee.org/portal/cms_docs/about/CoE_poster.pdf

Notes – Tuesday, June 23rd, 2009

Attendees: Alex Ashley (NDS), Joe Kwak (Interdigital), Emily Qi (Intel), Dorothy Stanley (Aruba Networks), Allan Thomson (Cisco), Qi Wang (Broadcom),Joshua Zhao (Atheros)

1. Chair called meeting to order: 12:05 Eastern

Chair called attention to the patent policy slides. Are there any questions on the slides?None

Chair asked: Are there any patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) that the participant believes may be essential for the use of that standard? None brought forward

Are there any additions to the proposed agenda? No changes proposed.

2. TG Status & Editor Report

Emily is working on producing a draft 6.01 that includes the editorial comment resolutions, including ANA assignments.

3. Comment resolutions

Discussion on selected editorial comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0676-00-000v-lb-150-comments.xls .

- CID 2 – The figure will need to be re-drawn; Emily will do this, but will take some time.- CID 19 – Agree that rewording is needed, transfer to the location category.- CID 42 – Agree that the ANA values need to be supplied now; Emily has requested ANA

assignments from Terry Cole.- CID 88 – Agree to decline, 11n HT action frames are an example of action frames that are not

protected, and are in a separate category & section. - CID 127 – Transfer to Virtual AP- CID 136 – Agree to accept the comment, move the reference.

Submission page 8 Dorothy Stanley (Aruba Networks)

Page 9: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

Discussion on the Channel Usage category comment, see https://mentor.ieee.org/802.11/dcn/09/11-09-0676-00-000v-lb-150-comments.xls .

- CID 47 – Agree to accept the comment

Discussion on the Sleep Mode category comment, see https://mentor.ieee.org/802.11/dcn/09/11-09-0676-00-000v-lb-150-comments.xls .

- CID 140 – Agree to a decline resolution. The Listen Interval and Sleep Mode are orthodonal features. Also Emily to contact the commenter and explain our rationale.

Discussion on Directed Multicast category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0676-00-000v-lb-150-comments.xls .

- CID 57 – Agree to accept the comment.- CID 103 – Need more discussion on a means to indicate the “last DMS frame”. Issue with

sequence number is that it is a value known in the lower MAC. Still open.- CID 104 – Inclined to decline. Get more information from the commenter tomake sure we

understand the comment accurately.- CIDs 108, 109, 110 – Agree to decline the comments; the non-AP STA must be able to support

the capability – e.g. transmit and receive frames, even though most of the operational aspects are implemented in the AP. The non-AP STA indicates its support of the feature by setting the bit field value to 1.

- CID 141 – Arrange a time to discuss with the commenter.

Discussion on the Multicast Diagnostics category comment, see https://mentor.ieee.org/802.11/dcn/09/11-09-0694-00-000v-lb150-comments-multicast-diagnostics.xls .

- CIDs 38, 39 – Agree with proposed resolution

Discussion on Virtual AP category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0676-00-000v-lb-150-comments.xls .

- CID 11 – Need to add text specifying how to set any potentially unused bits, agree that a simple approach is preferred. Qi to propose text.

- CID 87 – Qi to discuss with the commenter.- CID 122 – Agree to accept the comment.- CID 123 – Slight re-wording, change “SSID” to “BSS”.- CID 127 – Qi to see if the website indicated by the commenter has the proposed Annex L

updates.

Discussion on Location category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0684-00-000v-lb150-comments-location.xlsx .

- CIDs 70, 71, 72, 73, 81, 82, 83 – Agree with proposed resolution, all resolved with removal of text by CID 44.

- CIDs 74, 84, Agree to decline since the length field exists, add a reference to the TGk text where the length field is specified.

- CID 76 – Slight modifications to the proposed text to refer to “location reference” rather than value.

- CID 124 – Agree to slight modifications to the proposed text addition.

Submission page 9 Dorothy Stanley (Aruba Networks)

Page 10: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

Review of topics for next conference calls:

Friday - June 26th – Time Advertisement, others as availableTuesday June 30th – Timing Measurement, STA Statistics, others as available; this moved from Friday the 26th due to Ganesh’s time conflict.Friday July 10th – TBD

4. Adjourned at 1350 Eastern. The next conference call is Friday, June 26th, Noon Eastern

1-719-457-6209Code: 712-821-86412 hours

Submission page 10 Dorothy Stanley (Aruba Networks)

Page 11: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

June 26, 2009 Teleconference

Agenda, from e-mail notice:

1. Call to Order, Patent Notification2. Editor Update 3. Comment Resolution – LB150, see https://mentor.ieee.org/802.11/dcn/09/11-09-0676-00-000v-lb-150-comments.xls - Time Advertisement, others as available4. Adjourn

Please review the documents at the following links prior to the call:

-  IEEE Patent Policy - http://standards.ieee.org/board/pat/pat-slideset.ppt-  Affiliation FAQ - http://standards.ieee.org/faqs/affiliationFAQ.html-  Anti-Trust FAQ - http://standards.ieee.org/resources/antitrust-guidelines.pdf -  Ethics - http://www.ieee.org/portal/cms_docs/about/CoE_poster.pdf

Notes – Friday, June 26th, 2009

Attendees: Gabor Bajko (Nokia), Dorothy Stanley (Aruba Networks), Allan Thomson (Cisco), Qi Wang (Broadcom), one unknown attendee

1. Chair called meeting to order: 1217 Eastern

Chair called attention to the patent policy slides. Are there any questions on the slides?None

Chair asked: Are there any patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) that the participant believes may be essential for the use of that standard? None brought forward

Are there any additions to the proposed agenda? No changes proposed.

2. TG Status & Editor Report

Emily is working on producing a draft 6.01 that includes the editorial comment resolutions, including ANA assignments.

3. Comment resolutions

Discussion on Location category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0684-01-000v-lb150-comments-location.xlsx .

- CIDs 74 – Commenter agrees that the length field as indicated is correct. Additional change requested to explicitly name the data fields, Change to “The Civic Location field is a variable octet field and contains a list of civic address elements in TLV format as defined in IETF RFC 4776-2006.”Agree to change to “counter”.

Discussion on Time Advertisement category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0686-00-000v-lb150-comments-timeadv.xlsx .

- CIDs 3,5,8 – The comments are against TGp text. Change to counter; agree with the comments, but the text is TGp text; TGv will adopt changes as adopted in updated TGv drafts.

Submission page 11 Dorothy Stanley (Aruba Networks)

Page 12: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

- CID 26 – Similarly, this comment is against TGp text. Change to counter; agree with the comments, but the text is TGp text; TGv will adopt changes as adopted in updated TGv drafts. Also TGv chair will forward to TGp.

- CIDs 28, 34, 78 – Still open. Long discussion on possible alternatives for meeting the requirements to advertise the Time Zone info efficiently before association. Concern with requiring a translation between the current encoding for time zone and a potentially more efficient encoding. End device applications and POSIX expect to have the time zone info in IEEE STD 1004 string format. Alternatives include

o Keep the Time Zone element in the Beacon – no changeo Keep Time Zone element in the Beacon with more effient encodingo Move to (Re)-association request – concern, lose advertisement attribute, needed in TGuo Advertize in TGu GAS frame

- CID 35 Discussion on need to update the Time value to account for clock drift. Clock drift not expected to be significant for TGv needs. Need to make sure that provided time is accurate though. Concern with implementations “setting and forgetting” though. Allan to propose text

- CID 36 – Agree to accept the comment- CIDs 46, 79, 86 – Still open. True that now a calculation in required on the part of the station.

Prior (non-common u/p/v implementation) did not require a calculation. Station will be implementing u and v. Have to do the calculation for TGv anyway.

- CID 115 – Agree to decline resolution.

Review of topics for next conference calls:

Tuesday June 30th – Timing Measurement, STA Statistics, discussion on directed multicast CID 141 with the commenter at 1000, Location CID 19

Friday July 10th – Remaining Comments - Directed Multicast – CIDs 103, 104- Virtual AP CIDs 11, 87, 127- Time Advertisement – CIDs (28,34,78), 35, (46,79,86) - Liaison letter

4. Adjourned at 1340 Eastern. The next conference call is Tuesday, June 30th, Noon Eastern

1-719-457-6209Code: 712-821-86412 hours

Submission page 12 Dorothy Stanley (Aruba Networks)

Page 13: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

June 30, 2009 Teleconference

Agenda, from e-mail notice:

1. Call to Order, Patent Notification2. Editor Update 3. Comment Resolution – LB150, see https://mentor.ieee.org/802.11/dcn/09/11-09-0676-00-000v-lb-150-comments.xls - Timing Measurement, STA Statistics, discussion on directed multicast CID 141

4. Adjourn

Please review the documents at the following links prior to the call:

-  IEEE Patent Policy - http://standards.ieee.org/board/pat/pat-slideset.ppt-  Affiliation FAQ - http://standards.ieee.org/faqs/affiliationFAQ.html-  Anti-Trust FAQ - http://standards.ieee.org/resources/antitrust-guidelines.pdf -  Ethics - http://www.ieee.org/portal/cms_docs/about/CoE_poster.pdf

Notes – Tuesday, June 30th, 2009

Attendees: Gabor Bajko (Nokia), Dorothy Stanley (Aruba Networks), Dave Stephenson (Cisco), Allan Thomson (Cisco), Ganesh Venkatesan (Intel), Qi Wang (Broadcom)

1. Chair called meeting to order: 1205 Eastern

Chair called attention to the patent policy slides. Are there any questions on the slides?None

Chair asked: Are there any patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) that the participant believes may be essential for the use of that standard? None brought forward

Are there any additions to the proposed agenda? No changes proposed.

2. TG Status & Editor Report

Emily is working on producing a draft 6.01 that includes the editorial comment resolutions, including ANA assignments.

3. Comment resolutions

Discussion on Timing Measurement category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0710-00-000v-lb-150-timing-measurement-comments.xls and https://mentor.ieee.org/802.11/dcn/09/11-09-0711-00-000v-lb150-timing-measurement-normative-text.doc .

- CIDs 45, 75, 85 – Still open, commenter to prepare text with proposed changes. The solution will require additional time info to be carried in a new frame, rather than the ACK frame. Discussion on pros and cons – adds a capability for future use. Let STA determine what accuracy is good enough; range increasing beyond 100 meters for WLAN systems. Not needed for all e.g. clock synch applications. Increase in complexity.

- CID 90 – Change to counter, include a corrected intro sentence- CID 91 – Change to counter, additional changes needed in Clause 10

Submission page 13 Dorothy Stanley (Aruba Networks)

Page 14: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

- CID 92 – Agree with proposed resolution.- CID 94 – Agree with proposed resolution- CID 96 – Agree with proposed resolution- CID 97 – Agree with proposed resolution, some wording changes- CID 99 – Agree with proposed resolution- CID 100 – Agree with proposed resolution

Discussion on Directed Multicast CID 141 (1000 with commenter)- CID 141 – Commenter states:

o “I'm not satisfied with the response to this comment from LB-146 (CID 294). The original comment was:"The text states that the classifier type must be 0 (ethernet parameters). This is a problem since up to 32 IP multicast addresses may be mapped to the same ethernet group address; thus this format does not uniquely define a multicast stream. Moreover, I can see no reason for this limitation. Why restrict the TCLAS parameters at all?"

TGv declined the comment with the following response:"The intention of the DMS request is to specify which multicast traffic is requested for AP to transmit as unicast traffic. This multicast traffic is identified by DMSID, and the Destination Address of the multicast traffic is equal to the multicast address as specified in TCLAS element. The original proposal is to use a MAC Address field to describe the destination address of desired multicast traffic group. Since TGv uses TCLAS element in multiple places, we decided to use TCLAS to describe the destination address of desired multicast traffic group. This is why we have this restriction to make sure the Destination Address of the desired multicast traffic group is specified in the TCLAS element. Specifying the multicast address of the desired multicast traffic can allow the non-AP STA to filter out duplicated multicast traffic without deep packet inspection. "

This is not responsive to my comment. For further explanation of mapping IP multicast addresses to MAC addresses, see:http://www.tcpipguide.com/free/t_TCPIPAddressResolutionForIPMulticastAddresses.htm.

Having the restriction to only be able to classify by MAC address means that a single DMS request may map anywhere between 1 and 32 multicast streams to unicast and create much more traffic than intended by the requesting STA. DMS should not be designed to operate in this manner.

Discussion: Agree that we don’t want the receiving STA to look into the IP layer. How the AP determines which frames to convert to unicast is out of scope. Agree to counter, allow non-AP STA to use existing TCLAS Classifier types 0,1 and 4.. Type 3 is used for TFS, structure not natural to use, can accomplish what is needed with the others. Type 2 doesn’t include IP address field. Commenter satisfied with this resolution.

Discussion on STA Statistics category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0712-00-000v-lb150-sta-statistics-comments.xls

- CIDs 22, 48, 49, 50, 95 - Agree with proposed resolution- CID 112 – Still open; unreasonable to ask for info that other stations have. Unclear that this

addition makes sense. Need to redefine the requirement to clarify, or delete.

Review of topics for next conference calls:

Friday July 10th – Remaining Comments - Directed Multicast – CIDs 103, 104- Virtual AP CIDs 11, 87, 127- Time Advertisement – CIDs (28, 34,78), 35, (46, 79, 86) - Discussion on Location category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-

0684-01-000v-lb150-comments-location.xlsx , CID 19 – Review proposed text change- Liaison letter, supporting resolution to CIDs 43, 68

4. Adjourned at 1340 Eastern. The next conference call is Friday, July 10th, Noon Eastern

Submission page 14 Dorothy Stanley (Aruba Networks)

Page 15: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

1-719-457-6209Code: 712-821-86412 hours

Submission page 15 Dorothy Stanley (Aruba Networks)

Page 16: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

July 10, 2009 Teleconference

Agenda, from e-mail notice:

1. Call to Order, Patent Notification2. Editor Update 3. Comment Resolution – LB150, see https://mentor.ieee.org/802.11/dcn/09/11-09-0676-00-000v-lb-150-comments.xls

- Directed Multicast – CIDs 103, 104- Virtual AP CIDs 11, 87, 127- Sleep Mode CID 140- Time Advertisement – CIDs (28, 34,78), 35, (46, 79, 86) - STA Statistics, CID 112- Timing Measurement – CIDs (45, 75, 85)- Discussion on Location category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-

0684-01-000v-lb150-comments-location.xlsx , CID 19 – Review proposed text change- Liaison letter, supporting resolution to CIDs 43, 68

4. Plans for July session5. Adjourn

Please review the documents at the following links prior to the call:

-  IEEE Patent Policy - http://standards.ieee.org/board/pat/pat-slideset.ppt-  Affiliation FAQ - http://standards.ieee.org/faqs/affiliationFAQ.html-  Anti-Trust FAQ - http://standards.ieee.org/resources/antitrust-guidelines.pdf -  Ethics - http://www.ieee.org/portal/cms_docs/about/CoE_poster.pdf

Notes – Friday, July 10th, 2009

Attendees: Gabor Bajko (Nokia), Emily Qi (Intel), Dorothy Stanley (Aruba Networks), Allan Thomson (Cisco), Ganesh Venkatesan (Intel), Joshua Zhao (Atheros)

1. Chair called meeting to order: 1205 Eastern

Chair called attention to the patent policy slides. Are there any questions on the slides?None

Chair asked: Are there any patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) that the participant believes may be essential for the use of that standard? None brought forward

Are there any additions to the proposed agenda? No changes proposed.

2. TG Status & Editor Report

Draft 6.01 is now posted in the members’ area of the 802.11 website. Draft 6.01 includes resolutions to the editorial comments, including ANA assignments and updated section, figure and table numbers. We should have the results of IEEE staff MEC review next week, to incorporate into the next revision of the draft.

3. Comment resolutions

Discussion on Directed Multicast – CIDs 103, 104

Submission page 16 Dorothy Stanley (Aruba Networks)

Page 17: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

- CID 103 – Still open, Emily has contacted the commenter for further clarification. Commenter’s suggestion is to add the sequence number as an optional field, so the STA can detect a duplicate frame, after a directed multicast stream is terminated. Discussion:

o Are the frames protected? Yes, a DMS Response frame is used. Would require knowledge of the last transmitted unicast sequence number in the upper MAC. Sequence number is of the last unicast transmitted data frame.

o Adds a lot of complexity for a likely corner case. Not sure this is needed. AP is likely to terminat a DMS stream after a period of inactivity in the stream.

o Alternate means of detection of duplicates at the station?- CID 104 – Believe that the language in the base spec is sufficient. Emily has asked the

commenter to identify additional text changes he believes are required. Still open.

Discussion on remaining Sleep Mode comment, CID 140 - CID 140 – Discussion on interaction between Listen Interval and Sleep Interval. Which takes

precedence? Could have a scenario in which the STA indicates a listen interval upon association, then requests to enter sleep mode for additional power saving, and to eliminate the need to get GTK updates. When Sleep mode is active, the Sleep Interval applies. Dorothy and Emily to draft additional text.

Discussion on Time Advertisement, see https://mentor.ieee.org/802.11/dcn/09/11-09-0686-02-000v-lb150-comments-timeadv.xls , https://mentor.ieee.org/802.11/dcn/09/11-09-0729-00-000v-lb150-cid35.doc, and https://mentor.ieee.org/802.11/dcn/09/11-09-0759-00-000v-lb50-timeadvertisementcomment.doc . – CIDs (28, 34, 78), 35, (46, 79, 86)

- CID 28 – Agree with proposed resolution. Remove Time Zone element from Beacon, leave in Probe Response.

- CID 34 – Agree with proposed decline comment.- CID 78 – Agree with proposed counter, same as resolution to CID 28.- CID 35 – Agree with proposed resolution, slight text edits to 11-09-0729-00 text.- CID 46, 79, 86 – Update proposed decline reason with a description that the STA can calculate

the current time based on available information – UTC offset, time zone and TSF. Commenter notes that he prefers not requiring the STA to do the calculation but can live with this for now.

- CID 115 – Discussion on the difference between the TGu and TGp encodings, and a missing baseline UTC0 reference in the TGp usage. The missing baseline is a TGp issue, as development is underway there on the usage for classifier 1. Joe to raise the issue in TGp.

- New proposed improvement to the encoding of the error in 11-09-759-00; discuss next week.

Discussion on Location category comment, see https://mentor.ieee.org/802.11/dcn/09/11-09-0684-02-000v-lb150-comments-location.xls ,

- CID 19 – Agree with proposed resolution.

Discussion on STA Statistics category comments, see https://mentor.ieee.org/802.11/dcn/09/11-09-0712-01-000v-lb150-sta-statistics-comments.xls

- CID 112 – Agree with proposed resolution. Implementation keeps statistics counts on number of frames sent/received to each peer; if this is an issue, take to TGmb.

Discussion on Timing Measurement- CIDs 45, 75, 85 – Still open, commenter is preparing text with proposed changes. Discuss next

week.

4. Planning for July session

Currently have 6 sessions; Dorothy will post an initial agenda today. Initial discussion on assignment of topics to timeslots:

Submission page 17 Dorothy Stanley (Aruba Networks)

Page 18: doc.: IEEE 802.11-09/0677r5 · Web viewDiscussion on the TIM Broadcast category comment: CID 89 – Agree with the commenter, AID 0 is not typically referred to as a field, and need

July 2009 doc.: IEEE 802.11-09/0677r5

Monday PM2 – - Liaison Letter, supporting resolution to CIDs 43, 68- Timing measurement CIDs 45, 75, 85

Tuesday PM2 - Virtual AP CIDs 11, 87, 127- Sleep Mode- Directed Multicast- 11-09-0759-00 – Time error encoding

Wednesday AM1- Joint meeting with TGu if needed- 11-09-0755-00 – MIB addition- Review Draft EC report

Wednesday PM1Thursday AM2Thursday PM2

Prepare a consolidated spreadsheet for next week.

4. Adjourned at 1400 Eastern. The next meeting is at the July Plenary.

Submission page 18 Dorothy Stanley (Aruba Networks)