Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Apr 1998 17:20:44 -0400
From:      "Cambria, Mike" <MCambria@lucent.com>
To:        "'tokenring@freebsd.org'" <tokenring@FreeBSD.ORG>
Subject:   RE: Current work...
Message-ID:  <813D2854D1B0D1118236006097177581036B28@smtp.Lucentmmit.com>

next in thread | raw e-mail | index | archive | help


Matthew N. Dodd wrote:

	Also remember that all our data rides around in 802.2 packets so
we have those headers to deal with as well.

Do we plan on supporting both SNAP headers and IEEE headers?  IP can use
both, some protocols can use only one or the other.

MikeC

Michael C. Cambria                        Lucent Technologies
Member of Technical Staff                        Bell Labs Innovations
   Voice: (978) 287 - 2807                300 Baker Avenue
     Fax: (978) 287 - 2810                Concord, Massachusetts 01742
Internet:  mcambria@lucent.com <mailto:mcambria@lucent.com> 


-----Original Message-----
From:	owner-freebsd-tokenring@freebsd.org
[SMTP:owner-freebsd-tokenring@freebsd.org]
Sent:	Tuesday, April 21, 1998 4:41 PM
To:	Larry S. Lile
Cc:	tokenring@freebsd.org
Subject:	Re: Current work...

On Tue, 21 Apr 1998, Larry S. Lile wrote:
> Yes, but there is some minimum and some maximum and by default we
should
> pick some arbitrary point and let each driver adjust it to fit its
> insertion speed.  Also source routing can (I think) can affect the
> header size of the packets. 

We need to set our min and max based on line speed and let the user
adjust
to some value between if they desire.  Min will probably be the same for
both.

Routing info only takes 30 octets, so we have to consider that as well.

Also remember that all our data rides around in 802.2 packets so we have
those headers to deal with as well.

Eventually, our frame type code will deal with MTUs instead of
ethernet/fddi/tokenring.  The device will still determine the hard MTU
but
we have to have a way of supporting multiple MTUs per i/f.  We don't
really need to worry about that for now.

If you like, you can do what the FDDI code did and just use all the
ether_* stuff.

/* 
   Matthew N. Dodd		| A memory retaining a love you had for
life	
   winter@jurai.net		| As cruel as it seems nothing ever
seems to
   http://www.jurai.net/~winter | go right - FLA M 3.1:53	
*/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-tokenring" in the body of the message

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?813D2854D1B0D1118236006097177581036B28>