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

Re: [10GBT] phy parameter list



Brad,

Maybe the 10GBT Technical Alliance starting up on 1/1/04 wasn't such a bad
idea?

    - Jeff

----- Original Message -----
From: "Booth, Bradley" <bradley.booth@INTEL.COM>
To: <STDS-802-3-10GBT@listserv.ieee.org>
Sent: Thursday, April 01, 2004 9:58 PM
Subject: Re: [10GBT] phy parameter list


> Sanjay,
>
> Thanks for putting the list together.  I will try to get the list up on
> the website by early next week (I'm on the road this week).
>
> Just a note to the Task Force, I am a bit concerned about the lack of
> discussion around this material and lack of technical discussions in
> general.  For the Task Force to make progress, the reflectors should be
> used as much as possible to discuss ideas and concepts.  Please do not
> wait until our meetings to bring up issues or concerns, as we should be
> using our meeting time to present information that is establishing or
> has established consensus (hopefully via the reflector) to build out the
> baseline and eventually a completed draft specification for Working
> Group ballot.
>
> Thanks,
> Brad
>
> Bradley Booth
> Chair, IEEE P802.3an Task Force
> bbooth@ieee.org
> 512-732-3924 (W)
> 512-422-6708 (C)
>
>
> -----Original Message-----
> From: stds-802-3-10gbt@IEEE.ORG [mailto:stds-802-3-10gbt@IEEE.ORG] On
> Behalf Of Geoff Thompson
> Sent: Saturday, March 27, 2004 4:15 PM
> To: STDS-802-3-10GBT@LISTSERV.IEEE.ORG
> Subject: Re: [10GBT] phy parameter list
>
>
> Sanjay-
>
> I think it would be helpful to have the values from 1000BASE-T preserved
> on
> the spreadsheet as a basis for comparison.
>
> Thanks
>
> Geoff
>
>
> At 05:05 PM 3/26/2004 -0800, Sanjay Kasturia wrote:
> >I hope all of you have recovered from the visit to Disney World, from
> >the ethernet guitar music and from the wild nights at Pleasure Island.
> >
> >While we made good progress in arriving at an agreement on the channel
> >models and on the link specification front, I am obliged to point out
> >that we will need to reach agreement on a number other critical
> >parameters to have a reasonably complete draft 1.0
> >
> >I looked through the draft that George Eisler generated by modifying
> the
> >1000BASE-T spec and the large number of TBDs and listed some of the
> >important ones in an excel spreadsheet. The spreadsheet is attached and
> >I am sure Brad can help us put it on the website so it becomes a living
> >document. If there are other critical parameters that should be listed
> >in it, please send me email.
> >
> >I think participants should start thinking of presentations for the
> next
> >802.3an meeting to make a case for specific values for the parameters
> >listed in the spreadsheet.
> >
> >I am collecting information on how the selection was made for
> 1000BASE-T
> >and will come up with suggestions on how we can start the process of
> >comparing different phy proposals in case there isn't unanimity on all
> >the parameter values right from the start!
> >
> >Sanjay Kasturia
> >Editor, IEEE 802.3an
> >
> >sanjay@teranetics.com
> >cell (650) 704-7686
> >office (408) 653-2235
> >
> >
> >Item #  Description                             Current proposals
> >approved
> >         PCS
> >1       Symbol rate
> >2       Modulation
> >3       Frame structure
> >4       Transmit encoding for FEC
> >5       Transmitter bit to symbol mapping
> >6       Transmit processing
> >7       Transmit latency through PCS
> >         PMA
> >8       Transmit voltage specification
> >9       Transmit pulse shaping
> >10      Transmit master and slave jitter specifications
> >11      Transmit linearity specifications
> >12      Maximum allowable transmit distortion
> >13      Transmit noise floor
> >14      Transmit latency through PMA
> >         Startup protocol
> >15      state diagram for training
> >16      Coefficient exchange if required
> >17      Coefficient initialization if required
> >18      Mode selection method if phy operates in multiple modes
> >         Receiver performance requirement
> >19      BER or FER over specified channel models             10^-12 for
> >BER, FER??
> >20      Receiver latency requirement
> >