RE: CPRI mapper and control word processing
Folks,
Few more points here. As far as I remember there was concerns splitting the control words (VSD & Ctrl_AxC) into separate flows instead of sending them as a one blob. I probably failed to stress the fact that when one does per AxC switching you would need to send parts of the control words potentially to different destinations. Also some control information like Ctrl_AxC might be time sensitive in a sense that it needs to be sent earlier than waiting first collecting all control words. For these uses we (I think) need a bit more elaborate way to deal with VSD & Ctrl_AxC parts of the control words.
- Jouni
> -----Original Message-----
> From: stds-1904-3-tf@xxxxxxxx [mailto:stds-1904-3-tf@xxxxxxxx] On Behalf
> Of Jouni Korhonen
> Sent: Tuesday, December 01, 2015 12:13 PM
> To: stds-1904-3-tf@xxxxxxxx
> Subject: CPRI mapper and control word processing
>
> Folks,
>
> Just reminding that one of the bigger open topics in the spec is the handling
> of the CPRI mapper control words. More specifically the handling of VSD and
> Ctrl_AxC. The rest we already got into some kind shape.
>
> I had my views in Hillsboro but I would appreciate that those who had a
> different view/opinion would actually voice how they want VSD and Ctrl_AxC
> to be handled.
>
> - Jouni
>
> --
> Jouni Korhonen, CTO Office, Networking, Broadcom Corporation
> O: +1-408-922-8135, M: +1-408-391-7160