From owner-stds-802-3-hssg@ieee.org Wed Mar  1 16:01 GMT 2000
Received: from gatekeeper.pdd.3com.com (gatekeeper [161.71.169.3])
	by isolan.pdd.3com.com (8.9.1b+Sun/8.9.3) with ESMTP id QAA13905;
	Wed, 1 Mar 2000 16:01:54 GMT
Received: from ruebert.ieee.org ([199.172.136.3])
          by gatekeeper.pdd.3com.com (Netscape Messaging Server 3.6)
           with ESMTP id AAA1FB9; Wed, 1 Mar 2000 16:00:13 +0000
Received:  by ruebert.ieee.org (8.9.3/8.9.3)	id KAA12529; Wed, 1 Mar 2000 10:15:53 -0500 (EST)
Message-ID: <38BD340D.E908D3A@lucent.com>
Date: Wed, 01 Mar 2000 10:15:25 -0500
From: Sean Leighton <sleighton@lucent.com>
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: stds-802-3-hssg@ieee.org
Subject: Re: PAM-5, what are your BERs ?
References: <NDBBLFICGKDCKJBHKIAEAEDOCBAA.edward.chang@networthtech.com> <38BC82A0.BB5C0148@nSerial.com>
Content-Transfer-Encoding: 7bit
Sender: owner-stds-802-3-hssg@ieee.org
Precedence: bulk
X-Resent-To: Multiple Recipients <stds-802-3-hssg@majordomo.ieee.org>
X-Listname: stds-802-3-hssg
X-Info: [Un]Subscribe requests to  majordomo@majordomo.ieee.org
X-Moderator-Address: stds-802-3-hssg-approval@majordomo.ieee.org
X-Lines: 15
Status: RO
Content-Type: text/plain; charset="us-ascii"
Content-Length: 520


Hello,

With regards to the BER problem, are we open to the possible use of forward error
correction to correct for bit errors in the transmission stream. Currently in
T1X1.5, there is a submission for inband FEC based on a BCH-3 code that turns a
1x10**-7 BER into a corrected BER of 1x10**-17. Prehaps a BCH-1 code could be used?
Using FEC would introduce the need for some additional bits within the frame format
and it would probably introduce some latency, but it would introduce some coding
gain.

Cheers,
Sean