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

[STDS-802-16] [Relay TG][MPDU Construction Adhoc] 3rd teleconf minutes

Dear all:

Please find the attached minutes for the 3rd teleconf of Relay TG MPDU construction adhoc.

Best regards,

Jeff

_________________________________________
 
Jeffrey Z. TAO, Ph.D.
Member of Technical Staff
Mitsubishi Electric Research Laboratories (MERL)
201 Broadway, 8th floor
Cambridge, MA 02139
 
P 617.621.7557
F 617.621.7550
E tao@merl.com
_________________________________________
Title: Minutes of the third Relay TG MPDU construction adhoc conference call

 

Minutes of the third Relay TG MPDU construction adhoc conference call

Monday April 16 2007

(13:00 GMT, 8:00 CDT, 9:00 EDT, 21:00 P.R.C/R.O.C, 22:00 Japan)

 

 

Chair: Jeffrey (Zhifeng) Tao

 

Participants:

Kanchei (Ken) Loa

Hang Zhang

Hongyun Qu

Chie-Ming Chou

Mary Chion

Haihong Zheng

Huaqiang Lee

Youn-Tai Lee

 

 

 

 

The meeting was started at 13:00 GMT on April 16 2007 and chaired by Jeffrey Z. Tao.  The meeting continued the discussion and successfully formed a preliminary recommendation for each contribution.

 

1.     Roll call

Roll call was conducted at the beginning of the adhoc and participants listed above were identified.

 

2.     Contribution discussion and recommendation preparation

  1. 07/198r7
    1. H. Zheng agreed with M. Chion that the value of CID is not sufficient to distinguish a relay MAC header from a GMH.  A more detailed discussion was conducted on the adhoc group email list before this teleconf.
    2. J. Tao raised the question of whether ‘RSV’ bit or ‘mesh subheader’ bit should be used to indicate the relay MAC header.
    3. K. Loa explained the necessity of extending ‘LEN’ field, and further supported to use ‘mesh subheader’ bit to indicate the relay MAC header.
    4. M. Chion agreed that using ‘mesh subheader’ bit could make the relay MAC header design cleaner.
    5. M. Chion further suggested submitting a comment to 16d/Cor 2 to clarify the usage of ‘mesh subheader’ bit in MMR network.
    6. The participants of the teleconf agreed to recommend the TG to accept an updated version of 07/198r7 into the baseline.

                                               i.     The contribution update referred to hereby should reflect the consensus that ‘mesh subheader’ bit will be used to indicate the relay MAC header.

                                             ii.     Also, comment will be submitted to 16d/Cor 2, clarifying the usage of ‘mesh subheader’ bit in the MMR environment.

 

  1. 07/195r3
    1. H. Zhang first provided a brief overview of this contribution.
    2. H. Zhang further confirmed that the proposed routing method and associated subheader format would be an optional feature.
    3. H. Zheng wanted to confirm whether the routing based upon the destination RS CID was a kind of tunneling method, and could be used as an alternative to tunneling.
    4. H. Zhang explained that the proposed routing method can be applied on anything outside a tunnel.
    5. H. Zhang argued that the content of the proposed QoS subheader has not been clearly defined in this contribution so far.  Moreover, if the proposed QoS subheader only has 8 bits, it would not have sufficient space to convey QoS requirement (e.g., max rate, delay, etc.).  Given limited QoS information, it will be difficult for the scheduler to make any meaningful decision.  On the other hand, if the proposed QoS subheader provides adequate space for all necessary QoS information, significant overhead would result. 
    6. As a reply, H. Zhang explained that this proposal was meant for the connectionless QoS routing and control.  It can eliminate the need of populating and storing QoS requirement information on each and every intermediate RS.
    7. Given the fact this contribution also has implication on routing, J. Tao solicited opinion from the adhoc group as to how to handle this contribution in a proper way.
    8. K. Loa mentioned that the proposed subheader mechanism may have security implication,.
    9. H. Zhang argued that security is more of a problem pertaining to general 802.16 design methodology, rather than related to this contribution in particular.
    10. M. Chion mentioned that signaling MAC message is not protected, and suggested to follow the same design principle for MMR MPDU format.
    11. Both M. Chion and H. Zheng confirmed that the CID in 6.3.3.8.2 of the current baseline document (r3) refers to MS CID.
    12. The participants of this teleconf suggested the authors to split the contribution into several separate ones, each of which focuses on just one topic (e.g., routing, subheader design, etc.).

 

 

  1. 07/217r1
    1. The authors will resubmit an update of this contribution the TG.



  1. 07/256
    1. J. Tao confirmed with the authors (i.e., K. Loa) that no confusion will be caused to MS.
    2. H. Qu mentioned that no fragmentation can be applied on basic CID.
    3. K Loa clarified that no fragmentation was proposed in this contribution.
    4. M. Chion proposed to use a 16j specific broadcast CID instead of a multicast CID in the header in order to reduce the overhead associated with multicast group establishment and maintenance.
    5. K. Loa replied that only multicast scheme is considered at this moment.
    6. The participants of this teleconf agreed to recommend the TG to accept this contribution into baseline, if K. Loa can address the comments by M. Chion.

 

  1. 07/257
    1. The participants of this teleconf agreed to recommend the TG to accept this contribution into baseline.

 

  1. 07/267r2
    1. M. Chion provided a brief summary of this contribution, and explained that section 3.3.26 (page 93) of current baseline draft (r3) has implicitly specified the notion of source routing, and thus covered the essence of this contribution.  Nonetheless, 07/267r2 further proposes some clarification.
    2. H. Zhang asked whether subheader is used for source routing.
    3. H. Zheng confirmed with M. Chion that the notion of “hop-by-hop” tunneling in the previous version of this contribution has been completely dropped.
    4. M. Chion further clarified that CID encapsulation in the current baseline draft (r3) is only described in the systematic CID assignment section.  07/267r2 extended CID encapsulation scheme to an arbitrary CID assignment scheme and also provided further clarification to the scheme.
    5. The participants of this teleconf agreed to tentatively recommend TG to accept this contribution into baseline.  Nonetheless, given the fact little time has been given to the participants to review this new update, the recommendation of acceptance could be revised per request/comment from the adhoc members.

 

  1. 07/285
    1. The participants of this teleconf agreed to recommend TG to accept this contribution into baseline. 

 

3.     Action items

Roll call was conducted at the beginning of the adhoc and participants listed above were identified.

    1. Authors of 07/198 shall address the comments raised during this teleconf and upload an update of the contribution.
    2. H. Zheng would provide submit a clarification to section 6.3.3.8.2 in current baseline (r3), if necessary.
    3. M. Chion will email the comments regarding 07/256 to the adhoc group mailing list for K. Loa to address.