Re: [802.3_NGEPON] Upstream Wavelength Plan

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

I agree that separate DBA domains for 10G and 25G upstream is desirable. In pure 50G greenfield we already have a mechanism—just use US0-A and US0-B (harstead_3ca_1_0917). Marek’s proposal is to extend this capability to the 10G PON brownfield co-existence scenario.

The disadvantages that I see:

A small DS/US gap for these 25/10 US0-A ONUs—only 25 nm. I don’t know the penalty, as funada_3ca_1_0117 does not address penalties for gaps this small. It could be sizable. Is there a risk that 25 nm gap is not implementable in the traditional 45 degree BOSA?
Lose the advantage John has cited with his favored plan, that of not requiring a new wavelength for 10G DMLs (1310 nm DMLs exist).

From: Marek Hajduczenia [mailto:mxhajduczenia@xxxxxxxxx]
Sent: Thursday, January 04, 2018 4:13 PM
To: STDS-802-3-NGEPON@xxxxxxxxxxxxxxxxx
Subject: Re: [802.3_NGEPON] Upstream Wavelength Plan

That might James' opinion. I do not share it. We have enough spectrum to optionally allow WDM coexistence between 25G and 10G systems.

At the end of the day, I personally do not care about new 10G upstream, but only about making both 25G channels equally challenging and limit their dispersion penalty. I do know though that the optional ability to do 10G and 1G upstream separation in today's system is a saving grace in many deployments where these systems are overlapped on the same fiber strand. I do not see any advance of doing the overlap if we can have some separation between these systems

On Thu, Jan 4, 2018 at 2:08 PM, John Johnson <john.johnson@xxxxxxxxxxxx> wrote:

Marek,

zhang_dezhi_3ca_2a_1117 proposed the principal that different rates in the same PON generation should share spectrum by TDM. I think that this principal should apply to 25G and 10G (using 25G protocol) upstream.

Ed, please add me to your list.

Regards,

John

On Thu, Jan 4, 2018 at 3:08 PM, Marek Hajduczenia <mxhajduczenia@xxxxxxxxx> wrote:

Ed et al.,

Here are two versions of what I was suggesting, depending on how we want to stack red 25/10G options

Please include me in the discussion chain.

Thanks

M

From: Harstead, Ed (Nokia - US) [mailto:ed.harstead@xxxxxxxxx]
Sent: Thursday, January 4, 2018 12:48 PM
To: STDS-802-3-NGEPON@xxxxxxxxxxxxxxxxx
Subject: [802.3_NGEPON] Upstream Wavelength Plan

All,

Per the discussion on today’s call: For anyone interested in joining the small group working to achieve consensus on the upstream wavelength plan, please send me an email.

Ed

From: Curtis Knittle [mailto:C.Knittle@xxxxxxxxxxxxx]
Sent: Wednesday, January 03, 2018 4:09 PM
To: STDS-802-3-NGEPON@xxxxxxxxxxxxxxxxx
Subject: [802.3_NGEPON] 1/4/18 IEEE 802.3ca (100G-EPON) consensus building meeting agenda

Dear Colleagues,

We have two contributions for consensus-building meeting on January 4, 2018:

Upstream Wavelength Plan - Ed Harstead
Upstream Burst Structure – Marek Hajduczenia

Meeting time is 11:30 – 1:00 Mountain Standard Time. Zoom details are below.

Curtis

Join from PC, Mac, Linux, iOS or Android: https://cablelabs.zoom.us/j/804971785

Or iPhone one-tap :

    US: +16699006833,,804971785# or +16465588656,,804971785#

Or Telephone：

   Dial(for higher quality, dial a number based on your current location)：

        US: +1 669 900 6833 or +1 646 558 8656

    Meeting ID: 804 971 785

    International numbers available: https://cablelabs.zoom.us/zoomconference?m=P8kmLi3Ns-dj0dUo8wlHA03Ja5cqdVFx

Or an H.323/SIP room system:

    H.323:

        162.255.37.11 (US West)

        162.255.36.11 (US East)

        221.122.88.195 (China)

        115.114.131.7 (India)

        213.19.144.110 (EMEA)

        202.177.207.158 (Australia)

        209.9.211.110 (Hong Kong)

        64.211.144.160 (Brazil)

        69.174.57.160 (Canada)

    Meeting ID: 804 971 785

    SIP: 804971785@xxxxxxxxxxx

Curtis Knittle

VP Wired Technologies – R&D

CableLabs

desk: +1-303-661-3851

mobile: +1-303-589-6869

c.knittle@xxxxxxxxxxxxx

Stay up to date with CableLabs: Read the blog and follow us on Twitter