Re: [802.3_NGECDC] [YANG for 802.3] Clause 30 modelling assumptions Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [802.3_NGECDC] [YANG for 802.3] Clause 30 modelling assumptions To : STDS-802-3-NGECDC@xxxxxxxxxxxxxxxxx Subject : Re: [802.3_NGECDC] [YANG for 802.3] Clause 30 modelling assumptions From : Edwin Mallette < edwin.mallette@xxxxxxxxx > Date : Mon, 8 Feb 2016 09:53:00 -0500 Delivered-to : mhonarc@xxxxxxxxxxxxxxxx In-reply-to : <000c01d16041$1c125800$54370800$@gmail.com> List-help : < https://listserv.ieee.org/cgi-bin/wa?

Re: [802.3_NGECDC] [YANG for 802.3] Clause 30 modelling assumptions Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [802.3_NGECDC] [YANG for 802.3] Clause 30 modelling assumptions To : STDS-802-3-NGECDC@xxxxxxxxxxxxxxxxx Subject : Re: [802.3_NGECDC] [YANG for 802.3] Clause 30 modelling assumptions From : Marek Hajduczenia < marek.hajduczenia@xxxxxxxxx > Date : Fri, 5 Feb 2016 13:14:51 -0500 Delivered-to : mhonarc@xxxxxxxxxxxxxxxx In-reply-to : < D2DA42C5.91A71%edwin.mallette@gmail.com > List-help : < https://listserv.ieee.org/cgi-bin/wa?

Re: [802.3_NGECDC] [YANG for 802.3] Clause 30 modelling assumptions Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [802.3_NGECDC] [YANG for 802.3] Clause 30 modelling assumptions To : STDS-802-3-NGECDC@xxxxxxxxxxxxxxxxx Subject : Re: [802.3_NGECDC] [YANG for 802.3] Clause 30 modelling assumptions From : Marek Hajduczenia < marek.hajduczenia@xxxxxxxxx > Date : Mon, 8 Feb 2016 15:49:44 -0500 Delivered-to : mhonarc@xxxxxxxxxxxxxxxx In-reply-to : < D2DE1565.91BBC%edwin.mallette@gmail.com > List-help : < https://listserv.ieee.org/cgi-bin/wa?

Re: Hari Debate, Response to Richard Taborek's Note to Dan Dove,dated 12 Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: Hari Debate, Response to Richard Taborek's Note to Dan Dove,dated 12/16/99 08:50:38 PM To : HSSG < stds-802-3-hssg@xxxxxxxx > Subject : Re: Hari Debate, Response to Richard Taborek's Note to Dan Dove,dated 12/16/99 08:50:38 PM From : Rich Taborek < rtaborek@xxxxxxxxxxxxx > Date : Thu, 30 Dec 1999 01:47:32 -0800 References : < 85256854.0072C1BD.00@xxxxxxxxxxxxxxxxxxxx > Reply-To : rtaborek@xxxxxxxxxx , rtaborek@xxxxxxxxxxxxx Sender : owner-stds-802-3-hssg@xxxxxxxx Al and fellow Stripers, First of all, you DO realize that my response is going to be long-winded.

pqdif.doc ON CREATING A NEW FORMAT FOR POWER QUALITY AND QUANTITY DATA INTERCHANGE Erich W.

P P P 3 Buckman, Lisa Hewlett-Packard P P P 3 Busse, Robert Transition Networks P P P P 4 Cam, Richard PMC-Sierra, Inc.

Lucent Technologies P P P 3 Bohbot, Michel NORDX/CDT P P P P 4 Booth, Brad Level One Communications P P P P 4 Bottorff, Paul Nortel Networks P P P 3 Brooks, Rick Nortel Networks P 1 Brown, Benjamin Nortel Networks P P P P 4 Buckman, Lisa Hewlett-Packard P P P 3 Buckmeir, Brian Bel Fuse P P 2 Burton, Scott MITEL Corporation P P P P 4 Busse, Robert Transition Networks P P P P 4 Bynum, Roy MCI Worldcom P P P P 4 Cady, Ed FCI P P 2 Campbell, Bob Lucent Technologies P P P P 4 Carlson, Steve ESTA P P P 3 Carroll, Paul PMC-Sierra P 1 Caspi, Rami Siemens Data Comm.

., LVDS SERDES reverse channel • Proxy Access • A type of I2C device access • Original requestor is aware of 1722 • Requestor will generate packets directly – Initiator Agent implemented in software • Remote bus would have a 1722 Target Agent • Target Agent could be software driving an I2C bus master interface • Transactions are atomic – target bus is left in idle state at end of transaction • Better performance than Transparent Access • Can coexist with Transparent Access Transparent Access • M1 and M2 are I2C masters • IA1 and IA2 are 1722 Initiator Agents • TA is a 1722 Target Agent • A, B, C, and D are end stations (masters or targets) M1 IA1A TA DC M2 IA2B Transparent Access • 1722 Requests originate from Initiator Agent • Breaks down I2C transaction into segments: • Start Write - generate START, ADDR, WRITE, return ACK • Continue Write - generate DATA, return ACK • End Write - generate STOP • Start Read - generate START/RESTART, ADDR, READ, return ACK, DATA • Continue Read - generate ACK, return DATA • End Read - generate NACK, STOP • Request includes: • Segment Type • Bus ID – for multi-initiator arbitration • Maximum completion time – milliseconds • ADDR, DATA • Each request will generate a response • Provides a way to rate limit the requests Transparent Access (cont) • Response includes: • Response type • Success/failure of associated request • State of Target Agent • Response data from Read Request • Extended status upon Status Request or request failure • Failure code: • None • Bus busy timeout – transaction was unable to start in allocated time • Stall timeout – transaction did not complete in allocated time • Initiator conflict– Target Agent busy servicing another initiator’s request • Sequence error – Continue or End with incorrect or missing Start • Address error – Continue or End address not matching Start address • Bus busy time – reports how long the bus had been busy • Competing initiator – bus ID of the initiator agent currently being serviced • Segment count – request segments processed for this I2C transaction, mod 4 • Agent busy – Target Agent was busy processing Transparent Access Requests • Bus ID – Bus ID of the client that the Target Agent is currently servicing Transparent Use Cases • LVDS extender emulation • Only two buses being bridged • Target bus can have local bus masters, but not allowed to access 1722 channel • Target Agent required to maintain retry buffer if local master supported • Multi-Bus • Masters on multiple I2C busses accessing a single target bus • Target Agent locked while busy servicing a request sequence • Target Agent may reject requests while busy with another initiator • Target Agent could provide additional queue to eliminate need to reject new requests while busy • Rejected Initiator Agent will need to retry request • This should be rare – only during initialization or error handling/recovery?

JP03a: 15 repetitions of “03” and then 16 repetitions of “30” (periodical at 2*(15+16)=62 UI  219 MHz)  In both cases, 0 denotes the −1 PAM4 symbol, and 3 denotes the +1 PAM4 symbol  Use JP03 to measure RJ and deterministic clock jitter (DCJ)  Method described below (based on well-known Dual-Dirac)  DDJ doesn’t exist, so need not be excluded  Use JP03a to measure EOJ  Enables measuring both duty cycle and rise/fall time distortion  Total length is 2*31UI – 31 is prime, so all internal busses are “challenged” equally (with reasonable implementations)  Specifications shall be met with any valid equalization setting 6 IEEE P802.3bj 100 Gb/s Backplane and Copper Cable September 2013, Geneva, Switzerland RJ and DCJ measurement procedure #1  Use JP03 to measure RJ and DCJ.  All 4 lanes active and transmit same sequence  Capture a waveform of N UI (N≥107) e.g. using a real- time scope.  Calculate the zero-crossing times TZC(i), i=1..N (interpolate if necessary).  Align so that TZC(1)=0  Calculate the average pulse width:  Calculate the phase jitter series:  Apply a 1st-order discrete high-pass filter HCDR(z) to the phase jitter series τ(n).  Denote the result τHPF(n) 7 1 )1()( 2 − −− =∆ ∑ = N iTiT T N i ZCZC AVG NnTnnTn AVGZC ..2,)2()1()( =∆−−−=τ IEEE P802.3bj 100 Gb/s Backplane and Copper Cable September 2013, Geneva, Switzerland RJ and DCJ measurement procedure #2  Sort the values of τHPF(n) in increasing order  Denote the result τsorted(n)  Determine the values J5 and J6 (in units of time) as follows (with either B=5 or B=6)  JB- is the maximum time that satisfies τsorted(0.5×10-B×N) ≤ JB- (typically negative)  JB+ is the minimum time that satisfies τsorted(N – 0.5×10-B×N) ≥ JB+ (typically positive)  JB = JB+ – JB-  Similar to clause 86.8.3.3 definitions 8 IEEE P802.3bj 100 Gb/s Backplane and Copper Cable September 2013, Geneva, Switzerland RJ and DCJ measurement procedure #3  Calculate RJRMS and DCJ according to: Where Q-1 is the inverse Q-function. 9             × × =      − −− −− 5 6 1 51 61 1)105.0(2 1)105.0(2 J J Q Q DCJ RJ RMS IEEE P802.3bj 100 Gb/s Backplane and Copper Cable September 2013, Geneva, Switzerland EOJ measurement procedure  Use JP03a to measure EOJ  All 4 lanes active and transmit same sequence  Capture 20 full cycles of JP03a  Interpolate if necessary and calculate the average zero-crossing time for each of the 60 transitions in JP03a, relative to start of pattern  Average is calculated across the 20 full pattern cycles  Denote the average values by TZC(i), i=1..60, where i=1 is the first transition following the two consecutive “3” symbols  Calculate the widths of 40 pulses from 41 transitions excluding the “repeated symbols” vicinity:  EOJ is half of the magnitude of the difference between the mean width of the even pulses and the mean width of the odd pulses: 10    ≤≤+−+ ≤≤+−+ =∆ 4021)18()19( 201),9()10( )( iiTiT iiTiT iT ZCZC ZCZC 40 )12()2( 20 1 20 1 ∑∑ == −∆−∆ = ii iTiT EOJ IEEE P802.3bj 100 Gb/s Backplane and Copper Cable September 2013, Geneva, Switzerland 2 2.5 3 3.5 4 4.5 5 5.5 6 6.5 7 x 10 -9 -0.4 0 0.4 JP03a, duty cycle=48.5% [V ] T (seconds) Example: EOJ measurement using JP03a 11  This is the voltage signal resulting from simulation of JP03a driven through a risetime filter + sample package and test fixture (provided by Liav Ben- Artsi).  The clock driving the signal has a slight duty cycle mismatch, in addition to DJ and RJ.  From this signal, calculation of EOJ is straightforward.

See next slide 4.3 Report voltage/power in bundle [ ] 12V (cars), 24V (trucks, busses) and 48V (future supply voltage) currents are up to 150A@12V (e.g. steering, air condition, …). 5.

Agere Systems P P P P Brown, Kevin Broadcom Corporation P P P P Brownlee, Phillip Coilcraft P Brunner, Robert Ericsson Research P P P P IEEE 802.3 - Attendance Sheet Page 2 Atlanta, Georgia, USA - March 2005 Name Company Mon Tue Wed Thu Bublil, Memorach Intel P P P Buckmeier, Brian Bel Fuse P Busse, Robert Transition Networks P P P P Cain, Jeff Cisco Systems, Inc.

Brown, Benjamin Brown, Kevin Brunn, Brian Busse, Robert Cain, Jeff Carlson, Steve Cates, Ron Chang, Luke Chen, Xiaopeng Cheong, Kok-Wui Chopra, Rahul *Chou, Joseph Claseman, George Cobb, Terry Cohen, Larry 14 March 2005 IEEE 802.3 Opening Plenary 10 802.3 Members (voters) p.2 Cornejo, Edward Cravens, George Cunningham, David Dabiri, Dariush Daines, Kevin Dallesasse, John D'Ambrosia, John Darshan, Yair Dawe, Piers Di Minico, Chris Diab, Wael Dineen, Thomas Dove, Dan Dupuis, Joseph E.

P P P Brownlee, Phillip Coilcraft P P P Brunner, Robert Ericsson Research P P P Buckmeier, Brian Bel Fuse P P Busse, Robert Transition Networks P P P P Cain, Jeff Cisco Systems, Inc.

Amphenol P Bouda, Martin Fujitsu 2P PFujitsu Braun, Ralf-Peter T Systems Enterprise Services 4P P P PDeutsche Telekom AG, T-Systems ES Brownlee, Phillip Coilcraft 2P PCoilcraft Brunner, Robert Ericsson Research 3P P PEricsson Research Buckmeier, Brian Bel Fuse 2P PBel Fuse Busse, Robert Transition Networks 3P P PTransition Networks Cady, Ed Meritec 2P PMeritec Cain, Jeff Cisco Systems, Inc. 4P P P PCisco Systems, Inc.

Babanezhad, Joseph N Barnette, Jim Barrass, Hugh Barrick, Scott Baumer, Howard Beaudoin, Denis Beck, Michaël Beia, Christian Bennett, Mike *Bhoja, Sudeep Booth, Brad Braun, Ralf-Peter Brearley, Dave *Brown, Kevin Brown, Matt Brownlee, Phillip *Brunn, Brian Brunner, Robert Busse, Robert Cain, Jeff Carlson, Steve Chalupsky, David Chang, Frank Chang, Luke *Chin, David *Chopra, Rahul Claseman, George Cobb, Terry *Cohen, Larry Collum, James *Crepin, J.

Bemmel, Vincent Bennett, Mike Bhatt, Vipul Booth, Brad Bradshaw, Peter Braga, Al Brand, Richard Brown, Benjamin Brown, Kevin Burton, Scott Busse, Robert Cain, Jeff Cam, Richard Carlo, James T.

*Brown, Benjamin Brown, Kevin Brunn, Brian Brunner, Robert Busse, Robert Cain, Jeff Carlson, Steve Chang, Luke Cheong, Kok-Wui Cho, Jae hun Chopra, Rahul Claseman, George Cobb, Terry Cohen, Larry Cornejo, Edward *Cravens, George Cunningham, David Dabiri, Dariush 14 November 2005 IEEE 802.3 Opening Plenary 11 802.3 Members (voters) p.2 Daines, Kevin Dallesasse, John D'Ambrosia, John Darshan, Yair Dawe, Piers Di Minico, Chris Diab, Wael Dineen, Thomas Dinh, Thuyen Dove, Dan Dring, John Dudek, Mike Dupuis, Joseph E.

Bhoja, Sudeep *Bhugra, Harmeet *Bonnamy, Jean-Michel Booth, Brad Braun, Ralf-Peter Brearley, Dave Brown, Kevin Brown, Matt Brownlee, Phillip Brunn, Brian Brunner, Robert Busse, Robert Cain, Jeff Carlson, Steve Chalupsky, David Chang, Frank Chang, Luke Chin, David Chopra, Rahul Claseman, George Cobb, Terry Cohen, Larry Collum, James Crepin, J.

Broadcom Corporation P P P Brownlee, Phillip Coilcraft P P Buckmeier, Brian Bel Fuse P P Busse, Robert Transition Networks P P P Cady, Ed Meritec P P P Cain, Jeff Cisco Systems, Inc.

Enablence Technologies, Inc. 1 1 1 1 4 Busse, Robert Transition Networks, Inc.

Cisco Systems, Inc. 1 1 411 Bates, Stephen PMC-Sierra, Inc. 1 1 310 Beaudoin, Denis Texas Instruments Incorporated Texas Instruments Incorporated 1 1 411 Belopolsky, Yakov Self Employed Bel Stewart Connector 1 1 301 Bennett, Michael Lawrence Berkeley National Lab (LBNL) Lawrence Berkeley National Lab (LBNL) 1 1 411 Bernstein, Gary Leviton Manufacturing Co. 1 1 200 Bhatt, Vipul Lightwire, Inc. 1 1 411 Bhoja, Sudeep Broadcom Corporation 1 1 200 bliss, will Broadcom Corporation Broadcom Corporation 1 1 411 Bolig, Matthew NetLogic Microsystems 1 1 301 Booth, Brad Dell Dell 0 0 101 Boyce, Christina IEEE IEEE 0 0 101 Breuer, Dirk Deutsche Telekom AG Deutsche Telekom AG 1 1 411 Brown, Alan Aurora Networks Aurora Networks 1 1 411 Brown, Matthew Applied Micro (AMCC) Applied Micro (AMCC) 1 1 411 Bugg, Mark Molex Incorporated 1 1 411 Name Employer Affiliation Tue Wed IEEE 802.3 - Attendance and Affiliation Sheet Atlanta - November 2011 Page 2 CreditThuMon Busse, Robert Transition Networks, Inc.

Brown, Kevin Brown, Matt Brownlee, Phillip Brunn, Brian Brunner, Robert Busse, Robert Cain, Jeff Carlson, Steve Chalupsky, David Chang, Luke Chin, David *Cho, Jae hun Chopra, Rahul Claseman, George Cobb, Terry Cohen, Larry Crepin, J.

Brown, Kevin Broadcom Corporation 2P PBroadcom Corporation Budd, Lloyd Nexans 3P P PNexans Buehler, Kevin Maxim Integrated Products 3P P PProducts Busse, Robert Transition Networks 4P P P PTransition Networks Cady, Ed Meritec 1PMeritec Caggioni, Francesco AMCC 4P P P PAMCC IEEE 802.3 Attendance Sheet Page 2 Denver, CO - July 2008 Name Employer WTMAffiliation CrdtT Caldwell, Maurice Broadcom 2P PBroadcom Carlson, Steve High Speed Design, Inc. 4P P P PHigh Speed Design, Inc.

Deutsche Telekom AG 1 1 1 1 4 Breuer, Dirk Deutsche Telekom AG Deutsche Telekom 1 1 1 1 4 Brown, Matthew Quake Technologies AMCC 1 1 1 1 4 Busse, Robert Transition Networks, Inc.

Cisco Systems, Inc. 1 1 411 Beaudoin, Denis Texas Instruments Incorporated Texas Instruments Incorporated 1 1 411 Bennett, Michael Lawrence Berkeley National Lab Lawrence Berkeley National Lab 1 1 411 Bhatt, Vipul Lightwire, Inc. 1 1 411 Bhoja, Sudeep Broadcom Corporation 1 1 310 bliss, will Broadcom Corporation Broadcom Corporation 1 1 301 Breuer, Dirk Deutsche Telekom AG Deutsche Telekom AG 1 1 411 Brown, Matthew Applied Micro (AMCC) Applied Micro (AMCC) 1 1 411 Bugg, Mark Molex Incorporated 0 1 311 Busse, Robert Transition Networks, Inc.