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

Re: [802.3_NGEPON] Revised report available



Ed, Hesham, 

You are 100% on the money here - I was focused on how services are built,
and provided to end customers, and not necessarily on alignment with MEF.
MEF is more focused on abstract service definitions, which then need to be
translated into a specific network architecture, including EPON (OLT and
ONU). The E-ACCESS could be implemented in a number of ways, and what is
typically done today - it is implemented with E-LINE connectivity. 

Regards

Marek 

-----Original Message-----
From: Edwin Mallette [mailto:edwin.mallette@xxxxxxxxx] 
Sent: July 13, 2014 12:45 PM
To: STDS-802-3-NGEPON@xxxxxxxxxxxxxxxxx
Subject: Re: [802.3_NGEPON] Revised report available

Hi Hesham,

Good question.

Yes, in fact I believe Marek describes an E-Access service use case in his
document though he does not use the MEF language for such a thing.  The
Dedicated Internet use case described is essentially an E-Access circuit
which connects to a router; though many operators were provisioning such a
thing before the MEF language ever existed.  The E-Lines, E-LANs, and
E-Trees described can all be sub-divided where one or more segments of the
service are provided via an E-Access circuit to some kind of NNI to a
separate autonomous system where a separate operational party might manage
and provide the overarching service.  That service could be a MEF service
type or could be some other service type (i.e. L3VPN, etc.)

However my 2c is while there¹s value in describing use cases, there¹s
certainly a line between generalized use cases leveraging MEF verbiage and a
MEF CE2.0 service primer.  I would think we¹d want to stray to far into the
latter.

Regards,

Ed

On 7/13/14, 12:51 PM, "Hesham ElBakoury" <Hesham.ElBakoury@xxxxxxxxxx>
wrote:

>Hi Marek,
>
>Good paper. There is also  E-Access Services that are described in MEF 
>33. Is E-Access important for MSO ?
>
>Thanks
>
>Hesham
>
>-----Original Message-----
>From: Marek Hajduczenia [mailto:marek.hajduczenia@xxxxxxxxx]
>Sent: Sunday, July 13, 2014 8:16 AM
>To: STDS-802-3-NGEPON@xxxxxxxxxxxxxxxxx
>Subject: Re: [802.3_NGEPON] Revised report available
>
>Dear colleagues,
>
>Attached please find a contribution focusing on most common service 
>types provided over EPON. I focused on MSO access networks, though I 
>believe we can also easily add other service types addressing non-MSO 
>application space, if desired. To simplify development of such 
>contributions, I am sharing the editable format (DOCX with embedded 
>Visio files) of the contribution itself.
>
>If the group has no objections, I would like to go over the text and 
>individual applications at the meeting, and answer any questions.
>
>Regards
>
>Marek Hajduczenia, PhD
>Network Architect, Principal Engineer
>Bright House Networks
>Office +1-813-295-5644
>Cell +1-813-465-0669
>
>-----Original Message-----
>From: Howard Frazier [mailto:hfrazier@xxxxxxxxxxxx]
>Sent: July 11, 2014 5:03 PM
>To: STDS-802-3-NGEPON@xxxxxxxxxxxxxxxxx
>Subject: [802.3_NGEPON] Revised report available
>
>Dear members of the IEEE 802.3 NG-EPON Industry Connections ad hoc 
>committee,
>
>Our editors have updated the draft of our report to reflect comments 
>that were submitted. This version will be reviewed at our upcoming 
>meeting on Sunday.
>You can find the draft at the following URL:
>
>http://www.ieee802.org/3/ad_hoc/ngepon/private/report/NG-EPON%20IC%20Re
>por
>t%
>20R06d%20remein_ngepon_01_0714_kn_mh.pdf
>
>Note that the draft is in our private area.
>
>the username is: NGEPON
>the password is: Faster_Glass4U
>
>I look forward to meeting with you in San Diego.
>
>Howard Frazier
>Broadcom Corporation
>Chair, IEEE 802.3 NG-EPON IConnx ad hoc committee