|
All,
I like Roger's suggestion
*The record is contained in a subset of the documents stored at https://mentor.ieee.org/802.11/documents?is_group=0reg. The relevant documents are dated between 21 August 2013 and 11 March 2015; most, but not necessarily all, include the word "DSRC" and/or "Tiger" in the title. "
the best of all the alternatives we've seen so far.
Regards,
--Paul
------ Original Message ------
Sent: 5/14/2015 3:55:13 PM
Subject: Re: [802SEC] 802 letter to FCC regarding 802.11 Radio Regulatory DSRC Tiger Team
We've already come to the conclusion that we lack the capability to provide a summary report. Now I'm hearing the argument that we lack the capability to even provide a list of documents considered. I'm not satisfied with that notion and can't commit to voting approve on the resulting statement. However, I really think we can do better than the current proposed text:
*The record is contained at https://mentor.ieee.org/802.11/documents?is_group=0reg.
In the very worst case, if we are unable to create any selection of documents, then we should improve this, to something like:
*The record is contained in a subset of the documents stored at https://mentor.ieee.org/802.11/documents?is_group=0reg. The relevant documents are dated between 21 August 2013 and 11 March 2015; most, but not necessarily all, include the word "DSRC" and/or "Tiger" in the title.
I like John's suggestion. It could be implemented this way:
*The record is contained in a subset of the documents stored at https://mentor.ieee.org/802.11/documents?is_group=0reg. The relevant documents are dated between 21 August 2013 and 11 March 2015; most, but not necessarily all, include the word "DSRC" and/or "Tiger" in the title. For convenience, we include the attached list of documents whose relevance has been brought to our attention.
None of these are satisfying to me, except in relative terms.
Roger
James Lansford wrote:
Hi John,
I can't say for sure that only those 2 or 3 people at the FCC will see the letter, but I can tell you that one of those people has contacted me and stated that his job is to summarize the activities of the group for internal review. It is unlikely that anyone other than those three people will try to read through over 120 documents. Again, this represents a large percentage of the REG-SC activities over the past two years, so trying to list all these documents isn't really narrowing the search very much compared to a simple, clean pointer to REG-SC. As I mentioned previously, trying to parse the list may omit REG-SC documents where DSRC was discussed. I still believe a simple link is most appropriate.
Best regards,
Jim
On Wednesday, May 13, 2015, < John_DAmbrosia@dell.com> wrote:
Jim,
Noting your statement in Item #1 – will you please clarify if these will be the only individuals from the FCC that may be reviewing this letter?
While I appreciate the noted effort – the simple reality is I believe that this contribution could be viewed by more than just these 2 or 3 people who have participated actively. We should make a best effort to list all documents with a pointer to the proposed list, in case any other contributions may have been missed. (Appropriate language to be finalized).
Regards,
John
From: James Lansford [mailto:_javascript_:_e(%7B%7D,'cvml','jim.lansford@ieee.org');]
Sent: Wednesday, May 13, 2015 10:33 AM
To: DAmbrosia, John
Cc: _javascript_:_e(%7B%7D,'cvml','STDS-802-SEC@listserv.ieee.org');
Subject: Re: [802SEC] 802 letter to FCC regarding 802.11 Radio Regulatory DSRC Tiger Team
As the chair of the Tiger Team, I'd like to clarify a couple of things:
1) During the last several months of its activities, we had active participation from the FCC in the Tiger Team calls. Not just one person, but usually 2 or 3 people. They are well aware of how to use Mentor and get the documents they are interested in. We do not need to send a detailed list of documents.
2) Parsing out a "complete list" of documents isn't as easy as it sounds. We had discussions in some of the REG-SC meetings about DSRC Coex TT activities which make the line between TT activities and REC-SC activities fuzzy at best. Many, if not most, of the REG-SC documents over the last two years have been related to the DSRC Coex TT anyway. This is not looking for a needle in a haystack.
In summary, as Rich, John K. and Adrian have pointed out, a link to the REG-SC list is the most appropriate way to point to the Tiger Team's activities. Trying to get more granular is not necessary given the active participation by the FCC and would unnecessarily clutter up the letter, in my opinion.
On Wed, May 13, 2015 at 8:00 AM, John DAmbrosia <_javascript_:_e(%7B%7D,'cvml','John_DAmbrosia@dell.com');> wrote:
While I realize it is probably more work, I believe the best path forward is to provide the complete list, and not count on any regulatory body to parse through Mentor to find the appropriate documents.
I agree. There is no link that will get only the tiger team docs.
You’d probably have to search on “DSRC” or “Tiger”, and the mentor URL
doesn’t support that.
So the choice is to list them all, or to include all REG SC docs, and hope the
FCC have the intelligence to ignore the irrelevant ones.
Best Regards,
Adrian P STEPHENS
Tel: +44 (1793) 404825 (office)
Tel: +1 (971) 330 6025 (mobile) ç please note new number
----------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
From: ***** IEEE 802 Executive Committee List ***** [_javascript_:_e(%7B%7D,'cvml','STDS-802-SEC@ieee.org');] On Behalf Of John Kenney
Sent: Tuesday, May 12, 2015 9:51 PM
To: _javascript_:_e(%7B%7D,'cvml','STDS-802-SEC@LISTSERV.IEEE.ORG');
Subject: Re: [802SEC] 802 letter to FCC regarding 802.11 Radio Regulatory DSRC Tiger Team
Paul, thanks for this suggestion to provide information about the Tiger Team to the FCC.
As for the link to provide, I appreciate the motivation for Roger's narrower list, but I notice it leaves out several key documents from the Tiger Team record:
- Most importantly it omits both of the two original sharing proposal documents contributed to the Tiger Team (11-13-0994/r0 and 11-13-1276/r1).
- It also omits a detailed critique of one proposal (11-14-1101/r1).
- It also omits some other salient contributions (US DOT test beds, channel models)
So, absent a better suggestion, I prefer to use Paul's original link.
On Tue, May 12, 2015 at 9:21 PM, Jon Rosdahl <_javascript_:_e(%7B%7D,'cvml','jrosdahl@ieee.org');> wrote:
Roger your suggested URL is a nice suggestion.
I would support updating the URL
Regards,
Jon
-----------------------------------------------------------------------------
Jon Rosdahl Senior Standards Architect
hm:801-756-1496 CSR Technologies Inc.
cell:801-376-6435 10871 North 5750 West
office: 801-492-4023 Highland, UT 84003
A Job is only necessary to eat!
A Family is necessary to be happy!!
On Tue, May 12, 2015 at 10:02 PM, Roger Marks <_javascript_:_e(%7B%7D,'cvml','r.b.marks@ieee.org');> wrote:
Adrian,
In keeping with my suggestion of a list, a simple solution is to refer to this link:
https://mentor.ieee.org/802.11/documents?is_dcn=dsrc&is_group=0reg
That gives all the Regulatory SC documents with "DSRC" in the title. It has 129 hits, out of the 500 or so Regulatory SC documents.
If that's not the right list, then I'd propose inserting a hard list into the document.
Regards,
Roger
Stephens, Adrian P wrote:
Hello all,
I believe Paul’s intent is not to highlight any particular document, but the corpus (nice word, that) of all documents that comprise the entire discussion of the tiger team, including contributions, minutes, reports etc...
The majority of documents in the REG SC area (linked) since 2013 relate to this activity. I estimate the number to be around 120.
Best Regards,
Adrian P STEPHENS
Tel: +44 (1793) 404825 (office)
Tel: +1 (971) 330 6025 (mobile) ç please note new number
----------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
Paul,
I like the approach. However, the link points to a repository of every 802.11 Regulatory SC document of the past (and of the future too, for that matter). I think it would be better to make a list of all the relevant documents and add that to the statement.
Roger
Paul Nikolich wrote:
I am at the 802 wireless interim session in Vancouver Canada this week and met with a few of the key interested parties to resolve the pending 802-to-FCC communication regarding the completion of the 802.11 RR DSRC TT work. We put together a short, straightforward statement regarding the activity. It was agreed to by everyone involved as an effective way to communicate the accomplishments of the Tiger Team. It is located at https://mentor.ieee.org/802-ec/dcn/15/ec-15-0035-00-00EC-letter-to-fcc-regarding-802-11-rr-dsrc-tt.pdf.
My plan to close the pending 802/FCC/DSRC-TT action item from the March plenary closing EC meeting is to ask AdrianS and JonR to move/second a motion for EC email ballot that authorizes me to forward the document to the FCC as part of their 13-49 proceeding.
Please review the document and let me know if you have suggestions to improve the content--but remember, I want to keep this communication as brief and straightforward as possible.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
--
Director and Principal Researcher
Toyota InfoTechnology Center, USA
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv. |