| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Dear Roger and all, For what it is worth here are some definitions for term “Broadband”
as used in some ETSI standards or documents. Most are based on modified ITU-T
Recommendation I.113-101: (Source of information http://webapp.etsi.org/Teddi/
)
Kindest
Regards Nader ********************************************************** IMPORTANT:
The information contained in this e-mail and attachment (if any) is intended
for the person to whom it is addressed and may contain confidential and/or
privileged information. The contents of this message may contain personal views
which are not the views of NEC Europe Ltd or its subsidiaries, unless
specifically stated. You should not copy, retain, forward or disclose its
contents to anyone else, or take any action based upon it, if it is not
addressed to you personally. If you have received this e-mail in error
please contact the sender immediately. Any legally binding agreement resulting
from its content must be made separately in a printed medium. ********************************************************** From: Roger B. Marks
[mailto:r.b.marks@ieee.org] As detailed below, IEEE 802.18
plans to (quickly) develop a response to the FCC regarding the definition of
“broadband”. I am unable to attend the conference call on 26 August. Our
802.18 Liaison, Reza Arefi, has agreed to do so. If you have comments or suggestions regarding the topic,
please reply to the 802.16 reflector. Roger Begin forwarded message:
From: Mike
Lynch <freqmgr@SBCGLOBAL.NET> Date: 21
August 2009 3:32:07 PM MDT Subject: [802-18] 802.18 Conference Call - 26 August - 2:00
p.m. CDT - FCC Request for Help to Define "Broadband" Reply-To: Mike Lynch <freqmgr@SBCGLOBAL.NET> Dear EC and RR-TAG, Paul kindly brought to my attention that yesterday the FCC
released an item that asks for help in defining “broadband”. This
relates to the FCC’s development of a National Broadband Plan (NBP). The following link will take you to the item: As you will see the comment due date is 31 August and reply
comments are due 8 September. Not only is this a very short notice proceeding
but it falls between IEEE 802 meetings. Paul has asked that we try to implement
“Option 1” contained in my earlier email to the EC and
develop a response to be filed on 31 August. There is a reference to a previous FCC NOI regarding a
nationwide broadband network, GN Docket 09-51. At the May interim 802.18 made
comments on that NOI. The earlier FCC NOI is available on 802.18’s Mentor
web site: The 802.18 comments are available at: To do this we can take advantage of 802.18’s ability to meet
and approve documents on conference calls. What I propose is that all those WGs
in 802 (not only the wireless groups) meet by conference call at the date and
time given below. I further propose that each interested WG, as much as
possible in the limited time available prior to the call, develop views for
discussion on what is meant by “broadband”. In order to make the
call work more smoothly I ask that each interested WG chair (or designated
representative), with no more than 2 “advisors”, participate in the
call. All wireless chairs already have voting privileges in 802.18 and for this
call that privilege will be extended to all other WG chairs. Date – 26
August 2009 Time – 2:00
pm/14:00 CDT Bridge number – TBA NLT
Tuesday, 25 August Pass code – TBA NLT
Tuesday, 25 August Presuming success on the call the document will be submitted on
27 August for EC 5 day review and approval. Again let me say that I realize that this is a very short notice
for a meeting to deal with a topic such as this one. It is important that we
try and put the IEEE 802 view before the FCC on time. Beside the normal
boilerplate at the beginning of the comments we will also comment to the FCC
about the very short timeframe - 11 days from the public notice of the request
to the comment date. If possible please circulate any proposed text prior to the call. Glad to discuss. Regards, Mike Click here
to report this email as spam. |