802.3bj FEC Overview and Status. 400GbE Architecture Baseline Proposal (Update) DRAFT. IEEE P802.3bs 400 Gb/s Ethernet Task Force.

Size: px

Start display at page:

Download "802.3bj FEC Overview and Status. 400GbE Architecture Baseline Proposal (Update) DRAFT. IEEE P802.3bs 400 Gb/s Ethernet Task Force."

Molly Wood
8 years ago
Views:

1 802.3bj FC Overview and Status 400Gb rchitecture Baseline Proposal (Update) RFT P802.3bs 400 Gb/s thernet Task Force January 2015 Pete nslow - Ciena John mbrosia ell ark Gustlin Xilinx dam Healey vago avid Law HP Gary Nicholl - Cisco ave Ofelt Juniper Steve Trowbridge - LU Page 1

3bs 400 Gb/s thernet Task Force January 2015 Pete nslow - Ciena John

2 What Needs to be Supported in the rchitecture? The coding needs of the electrical interface may vary independently from the interface The requirements for each interface can be different, both the FC, modulation and number of lanes can change over time for each interface We need a single high level architecture which can support the evolving requirements of the interfaces over time This does not mean it requires a complicated implementation edia ndependent interface needs to be specified to enable standardization of different PHYs today and future, unknown, PHYs tomorrow. We need an electrical interface between different devices, CU (C2C & C2) supports two levels of implementers The system implementer The component implementer Page 2

can change over time for each interface We need a single high level architecture which can support the evolving requirements of the interfaces over time This does not mean it requires a

3 Sublayer Functions (at a high level) Sublayer 10Gb 100Gb 400Gb (proposed) Framing, addressing, error detection Framing, addressing, error detection Framing, addressing, error detection xtender XGXS ( + function) N/ ( + FC function) Coding (X: 8B/10B, R: 64B/66B), lane distribution, Coding (64B/66B), lane distribution, FC FC, transcoding FC, transcoding, align and deskew Serialization, clock and data recovery uxing, clock and data recovery, HO Coding, lane distribution,, FC N/ uxing, clock and data recovery, HO?? Physical interface driver Physical interface driver Physical interface driver Note that there are variations with a single speed, not all are captured in this table Page 3

FC, transcoding, align and deskew Serialization, clock and data recovery uxing, clock and data recovery, HO Coding, lane distribution,, FC N/ uxing, clock and data

4 The 400Gb Basic Layer iagram But C edium To enable flexibility for future efforts, an extender sublayer for the C is desirable, but there is no physical instantiation of the C. From a standardization perspective, it can leverage a CU, which is a optional physical instantiation of the service interface Page 4

5 Block iagrams CG CG 64B/66B ncode Transcode X^58 Scramble nsertion FC ncoder * Symbol istribution (16 LNS) 64B/66B ecode Transcode X^58 escramble Removal FC ecoder Lane Reorder Lock and eskew nterface Tx Specific FC code is TB From gustlin_3bs_02_0115 nterface Rx Page 5

X^58 escramble Removal FC ecoder Lane Reorder Lock and eskew

6 The following are the functions performed by the sublayer Provide appropriate multiplexing Provide appropriate modulation (P4 for instance if required) Provide per input-lane clock and data recovery Provide clock generation Provide signal drivers Optionally provide local loopback to/from the service interface Optionally provide remote loopback to/from the service interface Optionally provide test-pattern generation and detection Tolerate Skew Variation From gustlin_3bs_02_0115 Page 6

drivers Optionally provide local loopback to/from the service interface Optionally provide remote loopback to/from the

7 Comments on C lectrical nterface C C is the only media independent interface ifferent implementations or future PHYs may require changing FC, which would require a return to C (from a standardization perspective) The, as shown, is an extension of the C. This allows support for new / functionality below the extended C, if needed. The provides the coding / FC of the electrical interface, not the coding / FC of the PHY. Page 7

perspective) The, as shown, is an extension of the C.

8 C xtender Functional Concept C Optional C xtender / C CX-n liminating term CX since electrical interface is CU. ( funct.)* (16:n) CU-n PHY { C (n:16) ( funct.)* C edium nitial Proposal Updated Proposal * Note - Same as (including FC) to be defined. Page 8

9 400Gb xample mplementations SC iscrete C odule Option #1 Option #2 Option #3 Option #4 z may be different for various interfaces cited for CU Page 9

10 Leveraging the Proposed rchitecture Option #1 Option #1 1 Option #1 Option #4 Option #3 Option #3 Page 10

11 Thanks! Page 11

802.3bj FEC Overview and Status. 400GbE PCS Options DRAFT. IEEE P802.3bs 400 Gb/s Ethernet Task Force. November 2014 San Antonio

802.3bj FEC Overview and Status 400GbE PCS Options DRAFT IEEE P802.3bs 400 Gb/s Ethernet Task Force November 2014 San Antonio Mark Gustlin Xilinx Gary Nicholl Cisco Dave Ofelt Juniper Steve Trowbridge