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

Re: [802.19] TVWS Coexistence Plan



Hi Mariana, ALL

I understand what you are saying, but in my opinion, there will be specific pointers from the use case and scenarios that
will guide the group towards what is the most important coexistence deliverables to attack, per the R&O. I believe that
the reason the use case received 97.5% is because the use cases will show, per the R and O what needs to be done,

And some of those situations clearly have not even been brought up yet.
It may be that included are the other questions in the poll, but it seems like most people want to see
what it looks like, which will make sure we handle each deliverable in the most effective manner.
Contributions are always allowed I would think…Steve can answer that. .

There is one other thing that we could do now, though we haven’t much time,. and that would be something

That Steve would know how to handle. Does the .19 Tag and WS want to comment on the new NOI, answers are due shortly.
This is something that seems very worthwhile, and would if agreed upon in the group, go to .18 for their

Approval to forward to the FCC.

I am not sure any one is interested in this, but it is something that could be done in a couple of days, if we
all had the time to do it? What do you all think? I believe Steve can advise the date due, which may be
the 25th of April…..ok, lots of calls, discussion ,in a short time…


Not sure anyone else agrees or has any ideas about important comments that need addressing in the NO!..

Respectfully, Nancy


From: whitespace@xxxxxxxx [mailto:whitespace@xxxxxxxx] On Behalf Of Mariana Goldhamer
Sent: Monday, April 20, 2009 5:26 AM
To: Shellhammer, Steve; stds-802-19@xxxxxxxx; WHITESPACE@xxxxxxxxxxxxxxxxx
Subject: RE: TVWS Coexistence Plan

 

Steve, ALL,

 

The poll clearly shows that most of the people prefer to limit the TVWS Coexistence deliverables to Coexistence scenarios. The poll also shows enough interest in other topics for keeping them on the list.

 

I do not think that the Coexistence scenarios only will help EC to make significant progress in understanding the cross-802 activities related to TVWS. This document may only show the need for a cross-802 activity, but there will be no hints about what such an activity should include and which the obstacles to be addressed by EC are. With other words, there will be no much progress relative to March situation, when one of the tutorials also addressed coexistence scenarios extensively.

 

My suggestion is to keep the deliverables open for contributions, while taking some phased approach, as initially proposed by you. It is logical to address the scenarios first. But when this document will be in a mature state, if there will be contributions to anyone of the documents on your deliverable list, the contributions should be accepted and harmonized using the regular SG procedures. Based on this, it may be derived a plan for providing the other deliverables.

 

Regards,

 

Mariana


From: whitespace@xxxxxxxx [mailto:whitespace@xxxxxxxx] On Behalf Of Shellhammer, Steve
Sent: Sunday, April 19, 2009 10:16 PM
To: 802. 19 TAG (stds-802-19@xxxxxxxx); 802TVWS (WHITESPACE@xxxxxxxxxxxxxxxxx)
Subject: TVWS Coexistence Plan

 

All,

 

                I have updated the TVWS coexistence plan based on the straw poll results,

 

                https://mentor.ieee.org/802.19/dcn/09/19-09-0010-01-tvws-tv-white-space-coexistence-plan.ppt

 

                On Tuesday’s conference call we need to discuss this plan and make any necessary changes.  Then we will be good to go.

 

Regards,

Steve

 



************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(190).
************************************************************************************



************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(43).
************************************************************************************



************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(43).
************************************************************************************