Re: [STDS-802-16] [MMR-AH-UM] Some comments for joint contributions of usage model
Hello Jen-Shun.
To me, your proposal is more or less related with the implementation aspects of
routing protocols. Why should we ever mention such details -- i.e.,
prohibition or
enforcement of the use of certain types of protocol implementations --
in this usage
model document?
Regards,
Kyeongsoo (Joseph) Kim
--
Principal Engineer
Advanced System Technology
STMicroelectronics
- Mobile: (408) 621-4913
- kyeongsoo.kim@st.com / kks@stanford.edu
- http://www.stanford.edu/~kks/
On 6/13/06, Jen-Shun Yang <jsyang@itri.org.tw> wrote:
> Dear Jerry,
>
> Thanks for your great efforts.
>
> Regarding the Chapter 5.3 "Types of Routes", I would like to have the
> comments as below:
>
> 1. To distinguish MMR's topology from Mesh topology, it is not clear if we
> said the MMR's topology is only tree-like topology; because the mesh
> network could be a tree-like topology too.
> 2. Actually, I think the "centralized relay path selection by MMR-BS" is
> the major difference to distinguish MMR's topology from Mesh topology, and
> we should not allow the distributed routing protocols implemented in each
> RS due to the connection oriented characteristics in MMR. It will worsen
> the complexity if we allow the implementation of distributed routing
> protocols.
> 3. Therefore, I would like to make a revision to the following sentence
> written in the second paragraph of chapter 5.3.
> Original sentence:
> It should be noted that even when multiple routes are enabled between the
> RSs, the overall topology is still tree-like because all data
> communications are between the MMR-BS and MSs and this usage does not
> violate the scope as defined in 802.16j PAR.
> Revised sentence:
> It should be noted that even when multiple routes are enabled between the
> RSs, the overall topology is still tree-like and applying centralized relay
> path selection by MMR-BS, because all data communications are between the
> MMR-BS and MSs and this usage should not violate the scope as defined in
> 802.16j PAR.
>
> Best Regards,
>
> Jen-Shun Yang (Tonny Yang)
> ITRI/ICL
> TEL: +886-3-5914616
> email: jsyang@itri.org.tw
>
> 本信件可能包含工研院機密資訊，非指定之收件者，請勿使用或揭露本信件內容，並請銷毀此信件。
> 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.
>