call 9/29/2015 notes; was RE: call 7/29/2015 notes
Ok.. this slipped out prematurely.. thick fingers you know..
Fix:
Start: 9/29/2015 6AM PDT
End: 9/29/2015 7:15AM PDT
- Jouni
> -----Original Message-----
> From: stds-1904-3-tf@xxxxxxxx [mailto:stds-1904-3-tf@xxxxxxxx] On Behalf
> Of Jouni Korhonen
> Sent: Tuesday, September 29, 2015 9:24 AM
> To: stds-1904-3-tf@xxxxxxxx
> Subject: call 7/29/2015 notes
>
> Folks,
>
> Start: 9/15/2015 6AM PDT
> End: 9/15/2015 7:05AM PDT
>
> Present:
> Jouni Korhonen
> Bomin Li
> Raz Gabe
> Richard Maiden
> Peter Turnbull
> Sriram Devi
> Kevin Bross
> Xhafer Krasnigi
> Gareth Edwards
>
> Actual Agenda:
>
> * NGFI update (the English version of the white paper is out)
> * 1904.3 Spec D0.1 contributions
>
> Discussion:
>
> Jouni gave a quick update on NGFI. The English version of the white
> paper is now officially
> available. See the main in 1904.3 reflector:
> http://www.ieee1904.org/3/email/msg00251.html
>
> NGFI PAR will be presented again in IEEE ComSoc/SDB on 30-Sep and
> they will e-vote for being
> a sponsor for the project. 16-Oct is the deadline for PAR submission
> into IEEE process and then
> next NesCom call is on 4-Dec for the approval of the PAR.
>
> Three contributions were sent to 1904.3 reflector before the call.
>
> Sriram goes through the edits he made to D0.1 draft. No issues with
> those. Revised version
> to be incorporated to master draft.
>
> Xhafer goes through the edits he made to D0.1 draft. No issues with
> those after some little
> online editing. Revised version to be incorporated to master draft.
>
> Kevin points out (and Jouni agrees) that modulo 1 does the same as
> modulo 0 i.e. matching
> all container. Jouni points out that the difference really is that
> modulo 0 sets the whole
> modulo logic off while modulo 1 needs to have the index also set
> properly for the matching
> take place.
>
> Jouni goes through the edits and additions he made to D0.1 draft.
> Some online editing
> done. Jouni regrets the subclause 4.9 content for RoE Control Packet
> structure for CPRI
> mapper did not make it in time. No issue and the content will be
> added into the master
> draft for the time being.
>
> Jouni points out that his assumption is that in case of mapping
> technologies that do not
> nicely fit into UMTS Chip rate are resampled to be some nice
> fraction/multiple of UMTS
> Chip rate. That makes life much easier. That is widely practiced in the
> field already and
> we do not need to try to please all possible weird solutions there
> have been done for
> CPRI carrying non LTE/UMTS traffic.
>
> Next call in two weeks. Jouni to send more content (with fancy
> pictures) to subclause 4.9.
> Also example how to handle mapping of CPRI streams with multiple
> technologies like
> LTE + GSM.
>
> Other business:
>
> Next call 10/13/2015.
>
>
>
> --
> Jouni Korhonen, CTO Office, Networking, Broadcom Corporation
> O: +1-408-922-8135, M: +1-408-391-7160
>
>
>
> --
> Jouni Korhonen, CTO Office, Networking, Broadcom Corporation
> O: +1-408-922-8135, M: +1-408-391-7160