1. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [Comment Resolutions related to the RIT mode]
Date Submitted: []
Source: [Hiroshi Harada1, Fumihide Kojima1, Ryuhei Funada1, Sum Chin Sean1, Takaaki Hatauchi2, Minoru Tanabe3, Tomonori Sato4, Kentaro Sakamoto5, Aiichiro Kashiwagi6, Takahiro Banno7, Hirohito Nishiyama8, Kiyoshi Fukui9]
Company [1NICT, 2Fuji Electric, 3Panasonic, 4Toshiba Toko Meter Systems, 5Tokyo Gas, 6Osaka Gas, 7Toho Gas, 8Mitsubishi Electric Corp., 9Oki Electric Industry.]
Address [13-4, Hikari-no-oka,Yokosuka-shi,Kanagawa ,Japan]
Voice:[ ]
FAX: [ ] ]
Re: [TG4e comment resolution]
Abstract: [Comment resolutions related to the RIT mode]
Notice: This document has been prepared to assist the IEEE P It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P
<author>, <company>

2. CID #1437: RIT Data request command frame
<month year>
doc.: IEEE <doc#>
CID #1437: RIT Data request command frame
Comment: “RIT data request command shall be processed in not only a RIT-mode device. There is a case that a LE device request data to no LE device which understand RIT request command.”
Resolution: Replace the following text;
“This command shall only be sent and received in the RIT mode (macRitPeriod : non zero value).”
as provided below;
“This command shall only be sent and received by a device supporting the RIT mode.”
Slide 2
Page 2
<author>, <company>

3. CID #1422: Command frame to be sent in the RIT mode
<month year>
doc.: IEEE <doc#>
CID #1422: Command frame to be sent in the RIT mode
Comment: “It is unable to send commands related to the association, the scan and the poll to the receiver using RIT.”
Resolution: To amend the following primitives to support RIT mode;
MLME-ASSOCIATION.request
MLME-DISASSOCIATE.request
MLME-SCAN.request
MLME-START.request
MLME-POLL.request
MLME-FAST-ASSOCIATE.request
In order to support RIT mode, add TxIndirect parameter to each "Semantics of the service primitive" section and parameters table, and also the description regarding this parameter to each "Effect on receipt" section.
-> Actual modification for each primitive provided in the following slides
<author>, <company>

4. 7.1.3.1 MLME-ASSOCIATION.request
In “Semantics of the service primitive”
Add TxIndirect parameter in the semantics
Add following row in the Table 47
In “Effect on receipt”
Add the following paragraph; “If the TxIndirect parameter is set to TRUE and the device is in the RIT mode (macRITPeriod is non-zero value), the association request command shall be sent in the RIT mode.”
Name
Type
Valid Range
Description
TxIndirect
Boolean
TRUE or FALSE
TRUE if the association command is to be sent in the RIT mode

5. 7.1.4.1 MLME-DISASSOCIATE.request
In “Semantics of the service primitive”
Add following (underlined) text in the Table 51
In “Effect on receipt”
Add the following paragraph; “If the TxIndirect parameter is set to TRUE and the device is in the RIT mode (macRITPeriod is non-zero value), the disassociation notification command shall be sent in the RIT mode.”
Name
Type
Valid Range
Description
TxIndirect
Boolean
TRUE or FALSE
TRUE if the disassociation notification command is to be sent indirectly, or in the RIT mode.

6. MLME-SCAN.request
In “Semantics of the service primitive”
Add TxIndirect parameter in the semantics
Add following row in the Table 67
In “Effect on receipt”
Add the following paragraph; “If the TxIndirect parameter is set to TRUE, the ScanType parameter is 0x01 (active) or 0x03 (orphan) and the device is in the RIT mode (macRITPeriod is non-zero value), the beacon request command or orphan notification command shall be sent in the RIT mode, respectively.”
Name
Type
Valid Range
Description
TxIndirect
Boolean
TRUE or FALSE
TRUE if the beacon request command or orphan notification command is to be sent in the RIT mode.

7. MLME-START.request
In “Semantics of the service primitive”
Add TxIndirect parameter in the semantics
Add following row in the Table 72
In “Effect on receipt”
Add the following paragraph; “If the TxIndirect parameter is set to TRUE and the device is in the RIT mode (macRITPeriod is non-zero value), the coordinator realignment command shall be sent in the RIT mode.”
Name
Type
Valid Range
Description
TxIndirect
Boolean
TRUE or FALSE
TRUE if the coordinator realignment command is to be sent in the RIT mode.

8. MLME-POLL.request
In “Semantics of the service primitive”
Add TxIndirect parameter in the semantics
Add following row in the Table 76
In “Effect on receipt”
Add the following paragraph; “If the TxIndirect parameter is set to TRUE and the device is in the RIT mode (macRITPeriod is non-zero value), the data request command shall be sent in the RIT mode.”
Name
Type
Valid Range
Description
TxIndirect
Boolean
TRUE or FALSE
TRUE if the data request command is to be sent in the RIT mode.

9. 7.1.22.1 MLME-FAST-ASSOCIATE.request
In “Semantics of the service primitive”
Add TxIndirect parameter in the semantics
Add following row in the Table ZZ (There is no parameter table in the latest draft)
In “Effect on receipt”
Add the following paragraph; “If the TxIndirect parameter is set to TRUE and the device is in the RIT mode (macRITPeriod is non-zero value), the fast association request command shall be sent in the RIT mode.”
Name
Type
Valid Range
Description
TxIndirect
Boolean
TRUE or FALSE
TRUE if the fast association command is to be sent in the RIT mode