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

Re: [STDS-802-11-TGAZ] Asking for reassigning of TGaz LB240 CIDs addressing TB Ranging features that also applies to Passive Location Ranging

Erik,

The way we've been handling the reassignment requests is to identify the primary for each CID you are requesting, and negotiate with them whether you can take primary ownership. If they agree, send me the CID list for transfer from that person, and I'll update the spreadsheet. You can use 11-19/413r3 to guide you on the current assignee. When you have all your answers I'll make the update on 11-19/413r4, and then I'll coordinate with Chao-Chun to update the main database.

Does this work for you?

--Roy
__________________________
Roy Want
Google Android
Location & Context Team
MTV-43-299E,  Cell: 650 691 3600




On Wed, Mar 27, 2019 at 11:13 AM Erik Lindskog <e.lindskog@xxxxxxxxxxx> wrote:

Roy and all,

 

May I suggest we reassign/assign the TGaz LB240 CIDs:

 

1520, 1523, 1524, 1528, 1529, 1530, 1531, 1532, 1535, 1536, 1537, 1538, 1539, 1540, 1542, 1543, 1544, 1545, 1547, 1548, 1551, 1552, 1553, 1554, 1555, 1556, 1560, 1561, 1562, 1564, 1565, 1568, 1574, 1579

 

to me.

 

These are all CIDs that comment on the need to specify that some TB Ranging feature or behavior also applies to Passive Location Ranging.

 

My thinking is to rather than in each of these cases specify that these TB Ranging specifications also applies to Passive Location Ranging, instead improve upon our general statement that what applies to TB Ranging also applies to Passive Location Ranging, and where applicable rather specify what TB Ranging features does not apply to Passive Location Ranging, e.g. secure ranging and the ISTA to RSTA LMR reporting. This should save us a whole lot of text.

 

Best Regards,

Erik

 

 

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