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

Re: [STDS-802-16] Wireless Broadband Task Force of U.S. FCC Requests Comments



The referenced URL list was left out of the note. However, the only
one you need is <http://www.fcc.gov/wbatf>.

Roger


At 08:49 -0700 04/05/10, Ken Stanwood wrote:
>Where are the URLs?
>
>Ken
>
>-----Original Message-----
>From: owner-stds-802-16@LISTSERV.IEEE.ORG
>[mailto:owner-stds-802-16@LISTSERV.IEEE.ORG] On Behalf Of Barry Lewis
>Sent: Monday, May 10, 2004 1:58 AM
>To: STDS-802-16@LISTSERV.IEEE.ORG
>Subject: Re: [STDS-802-16] Wireless Broadband Task Force of U.S. FCC
>Requests Comments
>
>Roger,
>I'd be happy to co-ordinate any comments on this issue.
>
>Regards
>
>Barry Lewis
>Redline Communications
>Regulatory Manager
>Tel: +44 1276 479087
>Cell: +44 7947 496588
>
>mailto: blewis@redlinecommunications.com
>www.redlinecommunications.com
>
>
>-----Original Message-----
>From: owner-stds-802-16@LISTSERV.IEEE.ORG
>[mailto:owner-stds-802-16@LISTSERV.IEEE.ORG] On Behalf Of Roger B. Marks
>Sent: Monday, May 10, 2004 8:04 AM
>To: STDS-802-16@LISTSERV.IEEE.ORG
>Subject: [STDS-802-16] Wireless Broadband Task Force of U.S. FCC
>Requests Comments
>
>Folks,
>
>The U.S. FCC's Wireless Broadband Access Task Force
><<http://www.fcc.gov/wbatf>http://www.fcc.gov/wbatf> has requested
>comments, with a deadline of June 3.
>
>The 802.18 TAG, meeting this week near Anaheim, CA, USA, plans to
>prepare comments. Carl is inviting 802.16 to prepare input for them
>by Wednesday of this week.
>
>We have no formal process to do this, but we can submit something
>informally. It would be helpful to have it coordinated.
>
>Personally, I am extremely busy this week. Does anyone want to
>volunteer to coordinate comments?
>
>Roger
>
>
>>Roger,
>>
>  >If you check the last set of URLs at the bottom of this thread, it
>>has a list of items the Commission would like comment on.
>>
>>Since .16 is not meeting with the other wireless groups in SoCal
>>next week, if you can *try* to get some inputs to .18 by e-mail, say
>>by Wednesday of next week, on .16's views on the questions the
>>Commission is asking, it would be helpful. That would allow us to
>>take .16's views into account as we formulate comments ... (I would
>>hope that we could avoid WG partisanship/competition and stick to
>>facts as much as possible).
>>
>>I realize that I'm asking you to try to get input from your group by
>>e-mail before you meet, but with the comments due on June 03, it
>>would be helpful for us to have your inputs while we're meeting - if
>>possible. If this is not possible, I will schedule a conference call
>>meeting of 802.18 for Monday, May 24th at 12:00 noon EDT to
>>integrate/resolve .16's inputs against whatever .18 comes up with in
>>SoCal next week.
>>
>>Remember, I have to notice conference call meetings 5 days in
>>advance and whatever we produce has to pass a 5 day 802 EC review to
>  >file it as an 802.18 document - if that product is to be reviewed
>  >and blessed by CCIP (perhaps modified, perhaps as a joint filing?),
>  >we have to allow for that, too (that's why I'm asking you for input
>>next week if it's at all possible ...)
>>
>>
>>Regards,
>>Carl R. Stevenson
>>Chair, IEEE 802.18 Radio Regulatory Technical Advisory Group
>>IEEE Liaison to ITU-R
>>610-965-8799 (home office)
>>610-712-3217 (fax mailbox)
>>610-570-6168 (cellphone)
>>Short Message Service: 6105706168@voicestream.net
>>carl.stevenson@ieee.org
>
>
>IMPORTANT NOTICE: This message is intended only for the use of the
>individual or entity to which it is addressed. The message may contain
>information that is privileged, confidential and exempt from disclosure
>under applicable law. If the reader of this message is not the intended
>recipient, or the employee or agent responsible for delivering the message
>to the intended recipient, you are notified that any dissemination,
>distribution or copying of this communication is strictly prohibited. If you
>have received this communication in error, please notify Redline immediately
>by email at postmaster@redlinecommunications.com.
>
>Thank you.