RE: First early cut draft of the ieee1904_3_D01 specification

["Devi, Sriram" <sriram.devi@xxxxxxxxx>]

Hi Jouni/Richard,
   I am attaching my update, the changes are tracked in the attached document, I have summarized them below for easy reference:

Page 11: lines 36,37,41
Page 12 : line 5
Page 18 : Table 2 , last entry
Page 22: line 31
Page 23: Figure 7

I reviewed the data payload structure. From the scheme described, it appears that each packet will contain data from all AxCs similar to 
CPRI basic frame but replicated by RoE.numSegments. There does not seem to be an equivalent for oversampling ratio (within a container) 
as in CPRI. Not sure if flow id is required for a segment since it includes multiple containers with their own individual flow ids.
	
Thanks,
Sriram


-----Original Message-----
From: stds-1904-3-tf@xxxxxxxx [mailto:stds-1904-3-tf@xxxxxxxx] On Behalf Of Jouni Korhonen
Sent: Monday, September 14, 2015 10:43 PM
To: stds-1904-3-tf@xxxxxxxx
Subject: First early cut draft of the ieee1904_3_D01 specification

Folks,

Sorry for being this late.. See the attached early draft of the 1904.3 specification. We tried to capture all baselines (could have missed few) and latest discussion outcomes. I also added some food for thought on how to describe the RoE payload field in a way that it can also be used by a mapper parser as well.

Let's go this draft through in the call tomorrow and then continue putting material into the spec. There's much to do ;)

- Jouni

Attachment: ieee1904_3_D01_sriram.docx
Description: ieee1904_3_D01_sriram.docx