# | Feature | Details | Motion | Reference File |
March 2007 | ||||
1 | Accommodation of FEC overhead | 10GEPON shall accommodate FEC’s parity bandwidth by reducing the MAC’s effective data rate (sub-rating). | See Motion 3 | |
2 | Upstream FEC framing and synchronization | Accept the scheme outlined in slides 3-7 in 3av_0703_mandin_2.pdf as the baseline scheme for upstream FEC framing and synchronization. | See Motion 4 | 3av_0703_mandin_2.pdf |
3 | Downstream FEC codeword structure | Accept as a baseline scheme the FEC codeword structure depicted in the illustration on slide 5 in 3av_0703_mandin_2.pdf for the downstream (so that the FEC codeword structures on the upstream and downstream are identical). | See Motion 5 | 3av_0703_mandin_2.pdf |
4 | P802.3av document structure | The 802.3av Task Force approves the creation of two clauses as presented in 3av_0703_remein_1.pdf slides 7, 8, & 9. Outline of the clauses may be modified as necessary. | See Motion 6 | 3av_0703_remein_1.pdf |
5 | 10G/1G coexistence using upstream TDMA at 1310 | For the 10GEPON upstream, the TDMA at 1310nm coexistence method is conditionally selected as baseline, unless technically and economically feasible link budgets cannot be found for all cases. | See Motion 7 | 3av_0703_effenberger_4.pdf |
May 2007 | ||||
6 | 10 Gbps upstream signal | 10 Gbps upstream signal to have a pass band of 20 nm. | See Motion 3 | 3av_0705_tanaka_1.pdf (slide 14) |
7 | Handling of XAUI errors | 802.3av shall not support a physical XAUI interface between PHY and MAC in the ONU. | See Motion 5 | |
8 | FEC Codeword Structure | The FEC algorithm shall accept as its input Nx65bit payloads (the second bit of the sync header plus 64 bits of data) pre-pended with padding consisting of zeros to bring the input codeword to the required size; notwithstanding, both bits of the sync header shall be transmitted, while the padding shall not be transmitted, as illustrated in 3av_0705_effenberger_4.pdf. | See Motion 6 | 3av_0705_effenberger_4.pdf |
9 | FEC Framing | To accept as a baseline for FEC framing the presentations 3av_0701_effenberger_1.pdf, 3av_0703_kramer_1.pdf, and 3av_0705_lynskey_1.pdf. | See Motion 7 | 3av_0701_effenberger_1.pdf 3av_0703_kramer_1.pdf 3av_0705_lynskey_1.pdf |
July 2007 | ||||
10 | 10G Broadcast MAC | There shall be a Broadcast MAC instance for 10G distinct from the 1G Broadcast MAC instance | See Motion 3 | |
11 | Upstream power budget target | For the B++ case, adopt a baseline proposal for the upstream specifications corresponding to an APD with high output power DML. | See Motion 8 | |
12 | Start-of-Packet Alignment | Idle Deletion State machine should align /S/ character of the first frame in the burst to the byte-0 position as shown in FSM1 on slide 7 in 3av_0707_kramer_1.pdf. | See Motion 9 | 3av_0707_kramer_1.pdf |
13 | Idle Insertion | Adopt as a baseline proposal the idle insertion mechanism set forth in 3av_0707_lynskey_2.pdf. | See Motion 10 | 3av_0707_lynskey_2.pdf |
14 | 10G upstream wavelength | 10Gbps upstream signal shall be centered at 1270 nm for all power budget classes. | See Motion 12 | |
15 | Broadcast MAC LLIDs | Each broadcast MAC instance shall be associated with a unique LLID. The 10G broadcast channel shall be associated with LLID 0x7FFE. The 1G broadcast channel shall be associated with LLID 0x7FFF. The ONU transmits REGISTER_REQ with an LLID according to its upstream rate. A 10G/1G ONU receives broadcasts on LLID 0x7FFE and REGISTER_REQ to 0x7FFF. | See Motion 22 | 3av_0707_mandin_3.pdf |
September 2007 | ||||
16 | PR10 ONU Receiver | PR-10 ONU receiver shall use sensitivity typical of a PIN-PD. | See Motion 5 | |
17 | PR30 Wavelength Range | The wavelength range for the OLT transmitter and ONU receiver shall span from 1574 to 1580 nm for power class PR30. | See Motion 9 | |
18 | PR20 and PR30 ONU Receivers | ONU for PR20 shall have sensitivity typical of PINs and ONU for PR30 shall have sensitivity typical of APDs. | See Motion 12 | |
19 | OLT Transmitters | PMDs with two Tx power levels shall be specified for the OLT. | See Motion 13 | |
20 | OLT Transmitters (2) | One OLT PMD shall be specified with the parameters typical of High Power EML and one OLT PMD shall be specified with the parameters typical of EML with booster amplifier. | See Motion 14 | |
21 | Discovery GATE and REGISTER_REQ Messages | Adopt modifications to Discovery GATE and REGISTER_REQ as defined in 3av_0709_lynskey_3.pdf. | See Motion 15 | 3av_0709_lynskey_3.pdf |
22 | PR10 and PR20 ONU Transmitters | PR10 and PR20 ONU transmitter shall have parameters typical of a DML. | See Motion 17 | |
23 | PR10 and PR20 OLT Receivers | PR10 and PR20 OLT receiver shall have parameters typical of an APD. | See Motion 18 | |
24 | PR30 OLT Transmitter | PR30 OLT transmitter shall be specified with parameters typical of High Power EML. | See Motion 21 | |
25 | PR20 OLT Transmitter | PR20 OLT transmitter shall be specified with parameters typical of EML with a booster amplifier. | See Motion 22 | |
26 | PR10 OLT Transmitter | PR10 OLT transmitter shall be specified with parameters typical of High Power EML. | See Motion 23 | |
November 2007 | ||||
27 | Power Budget Parameters for PR10, PR20, and PR30 | Adopt the power budgets defined on pages 3-5 of 3av_0711_effenberger_1.pdf as the baseline for PR10, PR20, and PR30 PMDs. | See Motion 3 | 3av_0711_effenberger_1.pdf |
28 | PR10 and PR20 Downstream Wavelengths | Define the OLT transmit wavelength range for PR10 and PR20 PMDs to be 1580nm to 1600nm. | See Motion 4 | |
29 | FEC Algorithm | Accept RS(255, 223) as the baseline proposal for the FEC algorithm. | See Motion 7 | |
30 | Adjustable Laser On/Off Times | Accept as a baseline proposal for MPCP handshake-based adjustable Laser On and Laser Off times for 10G EPON using modified REGISTER_REQ and REGISTER messages shown in pages 6 and 7 of 3av_0711_suzuki_1.pdf. | See Motion 10 | 3av_0711_suzuki_1.pdf |
April 2008 | ||||
31 | Reported Queue Length values | REPORT messages shall report queue length in units of time_quanta without rounding up to integer number of FEC codewords. | See Motion 4 | |
Return to IEEE P802.3av 10GEPON Task Force Home Page
Last Update: 21 April 2008
Questions or comments: send e-mail to glen.kramer@ieee.org