Re: [STDS-802-16] [MMR-AH-UM] Announcing the 6/29/06 Meeting of Multihop Relay Usage Model Ad Hoc Group
Dear Ching-Tarng,
Thank you for your comments. I will make the editorial changes. We can discuss the comment on section 8 (summary) in our call tomorrow. I think that your suggestion makes sense, but want to make sure folks are comfortable with that section in general.
Best Regards,
Jerry Sydir
-----Original Message-----
From: chsieh@ITRI.ORG.TW [mailto:chsieh@ITRI.ORG.TW]
Sent: Tuesday, June 27, 2006 8:39 AM
To: Sydir, Jerry
Cc: STDS-802-16@listserv.ieee.org
Subject: Re: [STDS-802-16] [MMR-AH-UM] Announcing the 6/29/06 Meeting of Multihop Relay Usage Model Ad Hoc Group
Dear Ad Hoc Participants,
I read the most recent version of the Usage Model document
and have the following comments. Mostly are editorial.
1. Section 3, line 3, change“requirements on for”to“requirements for”
2. Section 4.1, line 1, change“to improve to improve”to“to improve”
3. Section 4.1, line 13, change“Topologies can range from 2 hops”to
“Topologies can include communication paths that range from 2 hops".
(also applies to line 4 on page 4)
4. In Figure 1, change “inside room”to“inside building”
5. Section 4.3, line 9, change“Disaster Recover”to“Disaster Recovery”
(also applies in Figure 3)
6. Page 6, 3rd paragraph, line 10, change “low flying”to“low-flying”
7. Page 10, Section 7.1, line 4 (not including editor’s note), change
“will be access to”to“will have access to”
8. Page 11, Section 8, line 2, change“are provided considering to reflect"
to“are provided to reflect”
9. Page 11, Section 8, change all NRS, MRS, FRS to RS.
(We agreed to replace NRS, MRS, FRS with RS in Figure 5 in our conference
call.)
Best Regards,
Ching-Tarng Hsieh
Information & Communications Research Labs/ITRI
Tel: 886-3-591-7379, Fax: 886-3-582-0204
E-mail: chsieh@itri.org.tw
================================================
NOTICE:
This e-mail may contain privileged confidential information.
If you are not the intended recipient or have received
this email in error, please notify us and delete this email
immediately. We appreciate your cooperation. You should
be aware that any unauthorized use, distribution or copying
of said confidential information is strictly prohibited.
---------------- Original Message ----------------
> "Sydir, Jerry" <jerry.sydir@INTEL.COM> 2006-06-27 02:24:52 AM wrote:
收件人: STDS-802-16@listserv.ieee.org
主旨: [STDS-802-16] [MMR-AH-UM] Announcing the 6/29/06 Meeting of Multihop
Relay Usage Model Ad Hoc Group
Dear Ad Hoc participants,
I’m resending this message because the list server seems to think that it
is a duplicate. My apologies if some of you have already received it. The
contents of the message have not changed.
The next meeting of the Multihop Relay Usage Model Ad Hoc Group will occur
on Thursday June 29, 06:00 – 08:00 PDT (13:00 – 15:00 UTC).
The bridge for the meeting is 916-356-2663, Bridge: 3, Passcode: 0910666
I have updated the draft to include modifications to the outline that we
agreed to in the June 22 meeting. It can be found in the following
location:
http://dot16.org/CSUpload//upload/temp_db/C80216j%2d06_UMAHtemp_r5.doc.
Please review the changes to make sure they are consistent with what we
decided. This is the last meeting before the document is uploaded the relay
TG directory, so we will try to limit our discussion to refining the
existing material.
The main topics planned for the meeting are:
-Discuss the proposal to mention that relays can be used within an MMR
network between the MMR-BS and RS. (This was discussed in the previous
meeting, but concerns were raised at the end of the meeting).
-Discuss the summary section (section 7)
-Go over any issues identified in the current version of the document
-Review the Ad Hoc Group report (to be sent out Tuesday)
Please send comments and issues that we need to discuss to the mail list
prior to Wednesday June 14 8 AM PDT. I will send out a detailed agenda for
the meeting on Wednesday.
Regards,
Jerry Sydir
本信件可能包含工研院機密資訊，非指定之收件者，請勿使用或揭露本信件內容，並請銷毀此信件。
This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient.