| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Can you show the exact text in question?  -Glen  From: Kevin Noll [mailto:kevin.noll@xxxxxxxxxxxx]  The text refers to â??xPDUâ?? in a way that implies that it is a singular parameter. This does not agree with the semantics of the primitives  VLCSI:OMCI.request ( omci_vendor_id, omci_serial_number, omci_frame_sdu )  MA_DATA.request ( destination_address, source_address, mac_service_data_unit, frame_check_sequence )   -- Kevin A. Noll  From: Glen Kramer <glen.kramer@xxxxxxxxxxxx>  Kevin,  I am not sure I understand the problem. Specifically, this statement:  This is inaccurate for VLCSI:OMCI.request and VLCSI:MA_DATA.request, since the primitives have parameters that do not correspond directly to an xPDU.  What exactly does not correspond? -Glen  From: Kevin Noll [mailto:kevin.noll@xxxxxxxxxxxx]  Glen,  It seems that the VLC sublayer block diagram (fig 6-1) is inconsistent with the Tx/Rx path specifications and state diagrams as it relates to the use of primitives.  The block diagram shows primitives going to adapters. Presumably the adapters are supposed to convert the received primitive parameters to the TxInputPdu (egress direction). There is nothing in the draft that explicitly says this, though.  In 6.3 (for egress), the text indicates that the Tx path of the VLC sublayer receives an xPDU from the primitives. This is inaccurate for VLCSI:OMCI.request and VLCSI:MA_DATA.request, since the primitives have parameters that do not correspond directly to an xPDU.  It seems to me that we need to delete the adapter blocks from fig 6-1 and add additional details to the text and state diagrams to describe how the primitive parameters are encapsulated and then handed to the CTE.  Alternatively, we can add text that defines the function of the adapters, which is to receive the primitive and format the parameters for use by the CTE.  I can draft these changes, but would like your opinion on which approach to take.  -- Kevin A. Noll  To unsubscribe from the STDS-1904-2-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-2-TF&A=1 |