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

Re: [STDS-802-11-TGBH] CC resolutions from 11-22/1329r15, collision with approved resolutions

I added them in the comments.

 

Yes, in some cases the already resolved CIDs were included, in other instances, they were moved and re-worded to make them
more clear.

 

Kurt Lumbatis

Distinguished Software Engineer

DOCSIS CPE R&D SW Architecture (Wi-Fi)

 

ARRIS AND RUCKUS HAVE JOINED COMMSCOPE

 

3871 Lakefield Dr, Suwanee, GA 30024 USA

Office: +01-678-473-2921

 

From: mark.hamilton2152@xxxxxxxxx <mark.hamilton2152@xxxxxxxxx>
Sent: Saturday, February 25, 2023 5:58 PM
To: Lumbatis, Kurt <kurt.lumbatis@xxxxxxxxxxxxx>
Cc: STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: CC resolutions from 11-22/1329r15, collision with approved resolutions

 

 

Kurt,

 

As I pull in the comment resolutions listed in your 11-22/1329r15 (and 11-23/0083r5), per our straw poll last week to proceed to motion on these, I see that some of the CIDs you quoted in 11-22/1329r15 already have resolutions that we have motioned.

 

Can you (and others, in preparation for discussion) review your proposed resolutions and compare to the already motioned resolutions, and determine how to resolve the duplication/conflict/addition that your document brings?  I’d like to give the task group a chance to review your thoughts, and for me to prepare the motion for those CIDs as some variation of:

  • Replace the current resolution, or
  • Keep the current resolution, AND apply the changes in 11-22/1329r15 (if that will be clear to the Editor), or
  • Some more explicit process, to make sure things are clear to the Editor

 

Specifically, this applies to CIDs: 3, 51, 52, and 55.

 

Thanks.  Mark

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