Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[STDS-802-11-TGBC] discussion CID 1490 1492



Hi Stephen,

 

Want to touch base with you on CID 1490 and 1492. After the discussion during the last teleconference, I have revised the resolution somewhat to add some clarifications. Please let me know whether these have addressed your concerns.

 

 

 

1490

Within Figure 9-bc8 when the "Requested Time To Termination" is set to 0, the "eBCS Request Info frame" then only contains the "eBCS Request Info Control" and the "Content ID" sub-fields. But this does nothing, so why have the "eBCS Request Info frame" there in the first place?

Re-write the "eBCS Request Info" subfield (Figure 9-bc7) without the "eBCS Request Info Control subfield" as it's redundant. If the eBCS Request Info has useful data in it (e.g. a Requested Time to Termination), then include the subfield within the eBCS Request element. If there is no Requested Time to Termination then do not include it in the eBCS Request element.

Then most of the optional bits and fields drop out resulting in a much simpler eBCS Request Info subfield.

Revised:
The cited text has been deleted and its content has been moved to Clause 9.4.1.xxx.

Content ID will always be present; all other optional fields may be optional and their presence is indicated in the Control subfield. Since the length may be variable, EBCS Request Info Control subfield would be needed to parse the EBCS Request Information List. Otherwise the receiving STA may have issues understanding the length of each of the EBCS Request Info subfield.

The value of Request Time To Termination = 0 has been clarified.

Note to editor:
Please incorporate changes in 11-21/667r1 under CID 1490.

 

 

1492

Within Figure 9-bc10, if all the optional sub-fields are not present, then the eBCS Response Info subfield does not need to be included within the "eBCS Response Information Set". This is because the eBCS Response Info subfield doesn't do anythimg.

Add a sentence to the cited clause stating that when an "eBCS Response Info" subfield has no optional information, then it does not need to be included in the "eBCS Response Information Set".

Revised:
The cited text has been deleted.

The EBCS Response Info subfield will always contain Content ID and EBCS Request Status to confirm the status of the request EBCS traffic stream, all other optional fields may be optional and their presence is indicated in the Control subfield. The Control subfield would be needed for receiving STAs to parse the EBCS Response Info subfield since the length is variable.

 

 

Best regards,

 

Xiaofei Clement Wang

Principal Engineer | InterDigital

T: (631) 622.4028

E:  Xiaofei.wang@xxxxxxxxxxxxxxxx

 


To unsubscribe from the STDS-802-11-TGBC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBC&A=1