REVIEW ITEM DISPOSITION (RID):
                    RED BOOK RID INITIATION FORM

AGENCY RID NUMBER: JAXA-RPA830-03
SUBMITTING ORGANIZATION (Agency, Center): JAXA
------------------------------------------------------------------
REVIEWER'S NAME:   Shigeyuki Furushima
CODE:              Mitsubishi Electric Corporation
E-MAIL ADDRESS:    jaxa.ccsds@jaxa.jp
TELEPHONE:         +81-29-868-2587
------------------------------------------------------------------
DOCUMENT NUMBER:   CCSDS 732.0-P-2.1        Pink Sheets, Issue 2.1
DOCUMENT NAME:     AOS Space Data Link Protocol
DATE ISSUED:       December 2008
PAGE NUMBER:  4-10              PARAGRAPH NUMBER:  4.1.4.1.5
RID SHORT TITLE:   The cange from "Idle Frame" to "OID Frame" (3)
------------------------------------------------------------------
DESCRIPTION OF REQUESTED CHANGE:  (Use From: "..." To "..." format)

"Idle Pattern" has been already defined in the section 4.1.4.2.4.2 and 
 4.1.4.3.4.2(There is no change in these parts in the pink sheet.).
 Moreover, the definition of the pink sheet is conflicting with actual standard.

   cf.
   4.1.4.1.5 Notes 3
   The idle pattern used in the OID Transfer Frame is project specific, but a random
   pattern is preferred. Problems with the reception of frames have been encountered
   because of insufficient randomization.

   4.1.4.2.4.2
   The M_PDU Packet Zone shall contain either Packets or Idle Data (a fixedlength
   project-specified �eidle�f pattern).

   4.1.4.3.4.2
   The Bitstream Data Zone shall contain either a fixed-length block of the user
   Bitstream Data (possibly terminated with idle data at a location delimited by the Bitstream
   Data Pointer), or Idle Data (a fixed-length project-specified �eidle�f pattern).

 






------------------------------------------------------------------
CATEGORY OF REQUESTED CHANGE:
     Technical Fact ___    Recommended _X_    Editorial ___
NOTES:
TECHNICAL FACT:  Major technical change of sufficient magnitude as to
 render the Recommendation inaccurate and unacceptable if not
 corrected.  (Supporting analysis/rationale is essential.)
RECOMMENDED:  Change of a nature that would, if incorporated, produce
 a marked improvement in document quality and acceptance.
EDITORIAL:  Typographical or other factual error needing correction.
 (This type of change will be made without feedback to submitter.)
------------------------------------------------------------------
SUPPORTING ANALYSIS:





------------------------------------------------------------------
DISPOSITION: Not Accepted.

The term �OID� was chosen to refer to the data field of an AOS or TM transfer frame, when that data field contains only Idle Data.

The other two data structures referred to in this RID i.e., M_PDU data zone and B_PDU data zone were explicitly excluded from using the term OID so as not to confuse the user. In these cases, the term Idle Data is used. 

Also see the following note 3 in section 4.1.4.2.4.4

An M_PDU that contains only Idle Data in its Packet Zone must not be confused with
the OID Transfer Frame defined in 4.1.4.1.5.

Also Note 4:

Idle Data in the M_PDU Packet Zone should not be confused with the Idle Packet
specified in reference [4].

We choose these words (OID versus Idle Data) in an attempt to differentiate between these usages.