Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

RE: Radio over Ethernet draft PAR for the IEEE 1904 pre-review & discussion



Jouni, 

Perhaps I am trying to indeed engineer a solution within PAR. 

If everybody else is fine with this level of detail, so will I 

Marek

-----Original Message-----
From: Jouni Korhonen [mailto:jouni.korhonen@xxxxxxxxxxxx] 
Sent: Tuesday, October 7, 2014 3:59 PM
To: Marek Hajduczenia; 'AshwoodsmithPeter'; 'Hesham ElBakoury'; Glen Kramer;
'STDS-1904-WG@xxxxxxxxxxxxxxxxx'
Subject: RE: Radio over Ethernet draft PAR for the IEEE 1904 pre-review &
discussion

Marek,

Right. My assumption is that these details would go into PAR step 5.2. How
much more detail would be needed? Currently the scope says:

1) Standard specifies the encapsulation of digitized radio In-phase
Quadrature (IQ) payload and related control data into an Ethernet packet
including the necessary encapsulation within the encapsulating Ethernet
frame.

2) Both structure-aware and structure-agnostic encapsulation of existing
digitized radio transport formats are within the scope. The
structure-agnostic encapsulation is not restricted to CPRI.

3) The standard will specify a structure-aware mapper for Common Public
Radio Interface (CPRI) frames and payloads to/from Ethernet encapsulated
packets.

I am more than happy to clarify all above three steps. However, I would be
reluctant to go into detail that would allow a single solution outcome at
this point, since we do not know the details yet that everybody can agree
on.
 
- Jouni

> -----Original Message-----
> From: Marek Hajduczenia [mailto:marek.hajduczenia@xxxxxxxxx]
> Sent: Tuesday, October 07, 2014 8:34 PM
> To: Jouni Korhonen; 'AshwoodsmithPeter'; 'Hesham ElBakoury'; Glen 
> Kramer; 'STDS-1904-WG@xxxxxxxxxxxxxxxxx'
> Subject: RE: Radio over Ethernet draft PAR for the IEEE 1904 
> pre-review & discussion
> 
> Jouni,
> 
> I believe you should clearly state what the intent is and what the 
> scope of the project will be. I think you have pretty much an idea of 
> what needs to be done and you can be very specific in the PAR.
> 
> MArek
> 
> -----Original Message-----
> From: Jouni Korhonen [mailto:jouni.korhonen@xxxxxxxxxxxx]
> Sent: Tuesday, October 7, 2014 12:51 PM
> To: Marek Hajduczenia; 'AshwoodsmithPeter'; 'Hesham ElBakoury'; Glen 
> Kramer; 'STDS-1904-WG@xxxxxxxxxxxxxxxxx'
> Subject: RE: Radio over Ethernet draft PAR for the IEEE 1904 
> pre-review & discussion
> 
> Marek,
> 
> For the below comment, which specific part(s) of the text you consider 
> having convoluted/vague statements? We'll have to fix those to avoid 
> confusion and misunderstanding.
> 
> - Jouni
> 
> > -----Original Message-----
> > From: stds-1904-wg@xxxxxxxx [mailto:stds-1904-wg@xxxxxxxx] On Behalf 
> > Of Marek Hajduczenia
> > Sent: Monday, October 06, 2014 10:38 PM
> > To: 'AshwoodsmithPeter'; 'Hesham ElBakoury'; Glen Kramer; 
> > 'STDS-1904- WG@xxxxxxxxxxxxxxxxx'
> > Subject: RE: Radio over Ethernet draft PAR for the IEEE 1904 
> > pre-review & discussion
> >
> > I believe the draft PAR proposal should make it then clear what the 
> > intent is, and avoid convoluted statements. Remember that people 
> > reading and voting on it in larger IEEE might not have sufficient 
> > background to understand all finer details of what you're trying to do.
> >
> > Being vague does not help getting projects approved.
> >
> > Marek
> >
> > -----Original Message-----
> > From: stds-1904-wg@xxxxxxxx [mailto:stds-1904-wg@xxxxxxxx] On Behalf 
> > Of AshwoodsmithPeter
> > Sent: Monday, October 6, 2014 3:33 PM
> > To: AshwoodsmithPeter; Hesham ElBakoury; Glen Kramer; STDS-1904- 
> > WG@xxxxxxxxxxxxxxxxx
> > Subject: RE: Radio over Ethernet draft PAR for the IEEE 1904 
> > pre-review & discussion
> >
> > Oh, I should add that this proposal is not looking at making changes 
> > to Ethernet to support CPRI, simply how the encapsulation would work.
> > The presentation to the IEEE 802.1 was to bring up the extremely 
> > challenging transport requirements which are independent of the
> encapsulation.
> >
> > Peter
> >
> > -----Original Message-----
> > From: stds-1904-wg@xxxxxxxx [mailto:stds-1904-wg@xxxxxxxx] On Behalf 
> > Of AshwoodsmithPeter
> > Sent: Monday, October 06, 2014 3:29 PM
> > To: Hesham ElBakoury; Glen Kramer; STDS-1904-WG@xxxxxxxxxxxxxxxxx
> > Subject: RE: Radio over Ethernet draft PAR for the IEEE 1904 
> > pre-review & discussion
> >
> > Thanks Hesham,
> >
> > We are happy to answer questions on the proposal. If people are 
> > interested I made a presentation to the IEEE a few months ago to 
> > discuss the possibility/requirements. The presentation is available
here:
> >
> > http://www.ieee802.org/1/files/public/docs2014/new-ashwood-tsn-cpri-
> > fronthau
> > l-0714-v03.pdf
> >
> > There is a link in there to the CPRI specification which has much 
> > more low level detail and if you Google things like "C-RAN" and
"Fronthaul"
> > there is a lot more information out there.
> >
> > Peter
> >
> > -----Original Message-----
> > From: stds-1904-wg@xxxxxxxx [mailto:stds-1904-wg@xxxxxxxx] On Behalf 
> > Of Hesham ElBakoury
> > Sent: Monday, October 06, 2014 3:21 PM
> > To: Glen Kramer; STDS-1904-WG@xxxxxxxxxxxxxxxxx
> > Subject: RE: Radio over Ethernet draft PAR for the IEEE 1904 
> > pre-review & discussion
> >
> > I have attached a clarification on this project from my Colleague 
> > Peter Ashwoodsmith.
> >
> > Thanks
> >
> > Hesham
> >
> > -----Original Message-----
> > From: Hesham ElBakoury
> > Sent: Monday, October 06, 2014 11:42 AM
> > To: 'Glen Kramer'; STDS-1904-WG@xxxxxxxxxxxxxxxxx
> > Subject: RE: Radio over Ethernet draft PAR for the IEEE 1904 
> > pre-review & discussion
> >
> > Glen,
> >
> > Is there a presentation that describes what this project aims to 
> > achieve (e.g. do they want to encapsulate OFDM symbol data in 
> > Ethernet frames ?) and why they think 1904 is the right standard 
> > group to work on
> this project ?
> >
> > Thanks
> >
> > Hesham
> >
> > -----Original Message-----
> > From: stds-1904-wg@xxxxxxxx [mailto:stds-1904-wg@xxxxxxxx] On Behalf 
> > Of Glen Kramer
> > Sent: Monday, October 06, 2014 11:16 AM
> > To: STDS-1904-WG@xxxxxxxxxxxxxxxxx
> > Subject: FW: Radio over Ethernet draft PAR for the IEEE 1904 
> > pre-review & discussion
> >
> > Dear Colleagues,
> >
> > I have received the following request for Radio-over-Ethernet (RoE) 
> > project to be formed under 1904 WG. The draft PAR is attached.
> > We will vote on this PAR at the next meeting. Meanwhile, I encourage 
> > everyone to review and discuss the draft PAR on the reflector. Feel 
> > free to contact PAR authors with any questions, or if you want your 
> > name to be added as a supporter.
> >
> > If approved, this PAR will become 1904.3 project.
> >
> > Thank you,
> > Glen
> >
> > -----Original Message-----
> > From: Jouni Korhonen
> > Sent: Monday, October 06, 2014 12:00 AM
> > To: Glen Kramer
> > Cc: Zongying He; Jay (James) Teborek; duanran@xxxxxxxxxxxxxxx; 
> > cuichunfeng@xxxxxxxxxxxxxxx; liu.qiong@xxxxxxxxxx; 
> > Patrice.Plante@xxxxxxxxxx; zhang.boshan@xxxxxxxxxx; 
> > satoru.matsushima@xxxxxxxxxxxxxxxx; tero.mustala@xxxxxxx; 
> > huangjinri@xxxxxxxxxxxxxxx; Peter.AshwoodSmith@xxxxxxxxxx
> > Subject: Radio over Ethernet draft PAR for the IEEE 1904 pre-review 
> > & discussion
> >
> > Dear chair of the IEEE 1904 ANWG,
> >
> > Please see the attached draft version of the PAR for Radio over 
> > Ethernet
> > (RoE) standardization effort that we (the individuals in the CC 
> > list) seek to pursue under the IEEE 1904 ANWG. We welcome a review 
> > and comments from
> > 1904 members on the current draft version of the PAR. We intend to 
> > present this PAR in the forthcoming 1904 meeting in Wuhan to drive 
> > our cause, which means we also ask for a presentation slot in the 
> > forthcoming
> 1904 meeting agenda.
> >
> > Should there be any additional backup material prior the meeting, 
> > please let us know. If there are any other matters we should be 
> > aware of
> just let us know.
> >
> > Best regards,
> > 	Jouni (on behalf of the PAR preparation team)
> >
> >
> > --
> > Jouni Korhonen
> > CTO Office, Networking
> > Broadcom