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

Re: [STDS-802-11-TGBB] 11-21-0276-03-00bb-proposed-text-for-4-4 (1).docx



Thanks for asking Volker. It’s clear now.

Kind regards,

Nikola

 

From: ** STDS-802-11-TGbb -- Light Communication Task Group** <STDS-802-11-TGBB@xxxxxxxxxxxxxxxxx> On Behalf Of Jungnickel, Volker
Sent: 09 March 2021 08:43
To: STDS-802-11-TGBB@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBB] WG: 11-21-0276-03-00bb-proposed-text-for-4-4 (1).docx

 

FYI

 

Von: Peter Ecclesine (pecclesi) [mailto:pecclesi@xxxxxxxxx]
Gesendet: Dienstag, 9. März 2021 05:48
An: Robert Stacey <rjstacey@xxxxxxxxx>; Jungnickel, Volker <volker.jungnickel@xxxxxxxxxxxxxxxxx>
Cc: nikola.serafimovski@xxxxxxxxxxxx; Chong Han (chong.han@xxxxxxxxxxxx) <chong.han@xxxxxxxxxxxx>
Betreff: RE: 11-21-0276-03-00bb-proposed-text-for-4-4 (1).docx

 

Following on from Robert, in amendments:

 

The editing instructions are shown in bold italic. Four editing instructions are used: change, delete, insert, and replace.

 Change is used to make corrections in existing text or tables. The editing instruction specifies the location of the change and describes what is being changed by using strikethrough (to remove old material) and underscore (to add new material).  Delete removes existing material. Insert adds new material without disturbing the existing material. Insertions may require renumbering. If so, renumbering instructions are given in the editing instruction. Replace is used to make changes in figures or equations by removing the existing figure or equation and replacing it with a new one. Editing instructions, change markings, and this NOTE will not be carried over into future editions because the changes will be incorporated into the base standard.

 

/Users/jgraybea/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_1806251772

Peter Ecclesine

Technology Analyst

+1.408.722.8489

 

pecclesi@xxxxxxxxx

Cisco Systems
170 W. Tasman Dr.
San Jose, California 95134
USA

Cisco.com

 

 

From: Robert Stacey <rjstacey@xxxxxxxxx>
Sent: Monday, March 8, 2021 12:39 PM
To: Jungnickel, Volker <volker.jungnickel@xxxxxxxxxxxxxxxxx>
Cc: Peter Ecclesine (pecclesi) <pecclesi@xxxxxxxxx>; nikola.serafimovski@xxxxxxxxxxxx; Chong Han (chong.han@xxxxxxxxxxxx) <chong.han@xxxxxxxxxxxx>
Subject: Re: 11-21-0276-03-00bb-proposed-text-for-4-4 (1).docx

 

Hello Volker,

 

For 1), yes this is the correct way to indicate the change: an editing instruction starting with the verb "change" (Change the 2nd paragraph as follows:) And then underline showing the inserted text. However, you just want to underline the inserted text and not the whole line, i.e., "j) DFS (not LC facility)"

 

For 2), I don't think calling out (no LC facility) or (not for LC) is necessary here. Using DFS as an example: DFS is only applicable to some channels in some regulatory domains. It is certainly not universal, so your change would just highlight this (not LC, but what about "not 2.4 GHz band").

I would avoid adding too much detail to this introductory clause. 

 

-Robert

 

 

On Mon, Mar 8, 2021 at 11:43 AM Jungnickel, Volker <volker.jungnickel@xxxxxxxxxxxxxxxxx> wrote:

Dear Peter, Robert,

 

I was asked to relay some questions to you.

 

In the enclosed document, the underlined text indicates changes requested by TGbb to the 802.11 Editor.

 

1)     Is this the right way to indicate any changes here

2)     What do you suggest

a.      j) DFS (no LC facility) or

b.      j) DFS (not for LC)

 

Thanks and best regards - Volker

 

 


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


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