| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Folks, Given the discussion during our last call, and Xiaofei’s statement below that we do not require any additional failure information, I am OK with the idea of
a single success/failure bit and no status octet. I’ll start revising the document to reflect that, but will hold off uploading the new version until others have had a chance to weigh in. John From: ** STDS-802-11-TGbc -- Enhanced Broadcast Service ** <STDS-802-11-TGBC@xxxxxxxxxxxxxxxxx>
On Behalf Of Stephen McCann Xiaofei, I think this is a good approach. As also mentioned in the discussion, if a failure is indicated, then perhaps another mechanism or other frame can indicate a specific status code (either an existing one or a new one). Kind regards Stephen On Thu, 13 Jan 2022 at 23:28, Xiaofei Wang <Xiaofei.Wang@xxxxxxxxxxxxxxxx> wrote:
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 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 |