Charles,
Thanks for informing the group of this. I am assuming any interested parties may contact you for possible collaboration.
Regards,
John
From: Charles Moore [mailto:charles.moore@xxxxxxxxxxxxx]
Sent: Monday, November 14, 2011 5:27 PM
To: John D'Ambrosia
Cc: STDS-802-3-100GCU@xxxxxxxxxxxxxxxxx
Subject: Re: [802.3_100GCU] Teleconference Announcement
john,
I plan to make a presentation to the task force in January proposing:
1. Test points and Rx and Tx test methods for cables
similar to clause 85 except for parameter values, eg
frequency, tap counts, gains etc.
2. Cable spec in terms of dibit gain and power sum of ICN
and re-reflection noise.
3. Test point defined for Tx chip test a short distance
(a few dB) from the chip itself to allow for a trace,
a connector and a coax to test equipment.
4. Tx chip spec (normative for backplane, informative for
cables) similar to clause 85 Tx spec except for
parameter values.
5. Test point defined for Rx chip test a short distance
(a few dB) from the chip itself to allow for a trace,
a connector and AC coupling.
6. Rx chip interference tolerance and return loss specs
(normative for backplane, informative for cable)
similar to Annex 69A but with different values to allow
for different frequencies, expected performance, and
loss between test point and chip pins.
7. Backplane spec based on method of moore_01_0311 and
improvements on that method.
So far this is intended to be general enough to cover both NRZ and PAM4, except that it may be necessary to add a level difference uniformity spec (2 bit DAC linearity) spec to the Tx spec for PAM4 Tx's.
charles
|--------------------------------------------------------------------|
| Charles Moore
| Avago Technologies
| APD
| charles.moore@xxxxxxxxxxxxx
| (970) 288-4561
|--------------------------------------------------------------------|
John D'Ambrosia wrote:
Dear Task Force Participants,
As indicated at the end of our meeting this week, at the next meeting we will be spending more time focusing on making decisions. This will limit the amount of time for presentations. Please note we will only be meeting for 2 days at the next interim (Thurs- Fri) – see http://events.r20.constantcontact.com/register/event?oeidk=a07e4y9n3wia6bed54a&llr=bqlaqkgab.
In the interest of getting organized for this meeting, I will be hosting a conference call on Tuesday, November 29, 9am to 10:30am (Pacific) to discuss organization of project proposals. Anticipated proposal topics include (but are not limited to)
Architecture
FEC / Encoding
MDI
The Channel
Signaling – NRZ / PAM-4 / Full duplex 8 lane
Test Specifications
As I said in the meeting – work on the standard doesn’t end with the meeting adjournment. It is obvious that we will all need to do a lot of offline consensus building. Given the limited amount of meeting time in January, priority will be given to multi-author presentations where offline consensus building is evident.
Regards,
John D’Ambrosia
from exch7-eqx-fe.force10networks.com (10.14.1.36) by exch7-sjc-fe.force10networks.com (10.11.0.87) with Microsoft SMTP Server (TLS) id 8.1.436.0; Fri, 11 Nov 2011 12:17:58 -0800 |
from mx.force10networks.com (10.14.131.3) by exch7-eqx-fe.force10networks.com (10.14.1.36) with Microsoft SMTP Server id 8.1.436.0; Fri, 11 Nov 2011 12:17:58 -0800 |
from engine.ieee.org (engine.ieee.org [140.98.193.23]) by pps-eqx-01.force10networks.com (8.14.3/8.14.3) with ESMTP id pABKLmjv012706 for <jdambrosia@xxxxxxxxxxxxxxxxxxx>; Fri, 11 Nov 2011 12:21:49 -0800 |
from gemini3.ieee.org (gemini3.ieee.org [140.98.193.188]) by engine.ieee.org (8.13.1/8.13.1/) with ESMTP id pABKHvtH007984 for <jdambrosia@xxxxxxxx>; Fri, 11 Nov 2011 15:17:57 -0500 |
from hormel8.ieee.org (hormel8.ieee.org [140.98.193.231]) by gemini3.ieee.org (Postfix) with ESMTP id BB65DBB813B for <jdambrosia@xxxxxxxx>; Fri, 11 Nov 2011 15:17:55 -0500 (EST) |
from mx.force10networks.com (64-186-164-204.static-ip.telepacific.net [64.186.164.204]) by hormel8.ieee.org (8.13.8/8.13.8/Debian-3+etch1) with ESMTP id pABKHsgq002310 for <jdambrosia@xxxxxxxx>; Fri, 11 Nov 2011 15:17:55 -0500 |
from EXCH-CLUSTER-09.force10networks.com ([10.11.10.114]) by exch7-sjc-fe.force10networks.com ([10.11.0.87]) with mapi; Fri, 11 Nov 2011 12:17:53 -0800 |
802.3bj Teleconference Announcement |
Acygrv1kyfdhNVP4Qx6/PCwmt3mIXQ== |
<905F3A9996E2A947BEF25553874A9EF601AE450666@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
en-US |
en-US |
X-MS-Exchange-Organization-AuthAs: Anonymous |
X-MS-Exchange-Organization-AuthSource: exch7-eqx-fe.force10networks.com |
en-US |
x-proofpoint-spam-details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=7 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1012030000 definitions=main-1111110202 |
0.00 () [Hold at 8.00] HTML_MESSAGE,SPF(none:0) |
IEEE Spam Scanner (https://uce.ieee.org/) on 140.98.193.231 |
0.0001 (Score 0, tokens from: @@RPTN) |
ip=64.186.164.204; country=US; region=CA; city=San Jose; postalcode=95134; latitude=37.4250; longitude=-121.9460; metrocode=807; areacode=408; http://maps.google.com/maps?q=37.4250,-121.9460&z=6 |
jodam (inherits from 80_DEFAULT,default) |
Bayes signature not available |
multipart/alternative; boundary="_000_905F3A9996E2A947BEF25553874A9EF601AE450666EXCHCLUSTER09_" |
1.0 |
When: Tuesday, November 29, 2011 12:00 PM-1:30 PM (GMT-05:00) Eastern Time (US & Canada).
Where: Ready-Access: 8663654406; 7-digit access code: 5662602
Note: The GMT offset above does not reflect daylight saving time adjustments.
READY-ACCESS® DIAL IN INFORMATION
You have been invited to join an audio conference.
Dial Ready-Access phone number: 8663654406 (Canada & US)
+13032489655 (Canada & US)
View additional Ready-Access phone numbers:
Enter 7-digit access code: 5662602
You will be placed on music hold until the Chairperson starts the conference.
READY-ACCESS® WEB MEETING PARTICIPANT LOGIN INFORMATION
You have been invited to join a Web Conference.
Click here to automatically login:
Enter your participant registration information.
You will view a "Lobby screen" until the Chairperson starts the Web Conference.
To test your browser and network connections for compatibility prior to the conference, go to:
If you have trouble automatically logging in using the link above, please do the following:
Enter Ready-Access phone number: 8663654406
Enter 7-digit access code: 5662602
If you have problems joining the conference or need technical assistance, please contact Customer Care:
If you have any questions pertaining to this meeting, please contact me directly. I look forward to having you join the conference.