Subject: Re: "dribbling bit"
To: Michael Richardson <firstname.lastname@example.org>
From: None <email@example.com>
Date: 01/22/2003 16:41:47
I've never encountered a case where problems were caused by a line being too
cold, but I have to admit that it doesn't happen all that often that a line
On 22-Jan-2003 Michael Richardson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>>>>>> "seth" == seth <firstname.lastname@example.org> writes:
> seth> That's not what I meant. In no sense can the ethernet encoding be
> viewed as
> seth> bits on the wire. There is no simple explanation, but basically
> seth> interpretation of the signal on the wire depends on the history of
> the signal.
> Yes, FastEthernet encodes as sequences of MII symbols in a star pattern,
> like modems, of which 16 of them encode 4 bits of data at a
> time. GigEthernet, depending upon the media does other various things.
> However, on FE, you can send a non-integral number of bytes, by sending an
> odd number of nibbles.
> In this case, it is 10Mb/s UTP, so there really are 8 bit times worth of
> data, with appropriate manchester encoding. As this goes into a ADSL box,
> and that box is *certainly* regenerating the signal on the wire (since it has
> to shop it up in various ways to spread the bit errors over the FEC, and then
> there is ATM encoding on top of that), it seems like some kind of cabling
> For what it's worth, I think it went away! I did change the cable, but that
> didn't immediately help. It is next to a cold basement wall, and it has been
> - -40, so...
> ] ON HUMILITY: to err is human. To moo, bovine. | firewalls
> ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net
> ] email@example.com http://www.sandelman.ottawa.on.ca/ |device
> ] panic("Just another Debian GNU/Linux using, kernel hacking, security guy");
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> Comment: Finger me for keys
> -----END PGP SIGNATURE-----
M. I. S. Corp.
This message was sent by XFMail