Date: Wed, 15 Apr 1998 14:45:45 -0700 From: George_Morgan@BayNetworks.COM (George Morgan) To: freebsd-tokenring@FreeBSD.ORG Subject: LLC Spec. Outline (monospaced view) Message-ID: <19980415214341.AAA3255@gmorgan-pc.corpwest.baynetworks.com>
next in thread | raw e-mail | index | archive | help
Well, here is what 802.2 says to me (so far):
LLC
|---------|----------|
Class I Class II
| |----------|----------|
|-> Connectionless Connection-based
| |
|-Data Transfer Services
|-Request |-Connect
|-Indicate | |-Request
| |-Indicate
| |-Confirm
|-Data Transfer
| |-Request
| |-Indicate
| |-Confirm
|-Disconnect
| |-Request
| |-Indicate
| |-Confirm
|-Reset Connection
| |-Request
| |-Indicate
| |-Confirm
|-Flow Control
| |-Request
| |-Indicate
And this is only the beginning!!!! Ethernet only
requires a Class I LLC interface so you can guess why
they did not write a Class II LLC or even see the need
to partition the LLC into a separate .c file. I
recommend that we try to modify the kernel as follows:
FreeBSD Kernel
|
|-----------------------|
Current Ethernet LLC
|-------|-------|
802.3 802.4 802.5
ENET ??? TokRng
This says, that if we can patch in our own LLC layer and
leave the existing Ethernet intact and then figure out
how to merge the current Ethernet over to our new setup,
then we might be able to ignore some of the more
horrible code the exists currently...
Just an idea; what do you think?
George Morgan
Bay Networks
gmorgan@baynetworks.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-tokenring" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980415214341.AAA3255>