Xref: utzoo comp.protocols.iso:1705 comp.protocols.iso.dev-environ:787
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!bu.edu!encore!pinocchio.encore.com!mckellar
From: mckellar@pinocchio.encore.com (Steve McKellar)
Newsgroups: comp.protocols.iso,comp.protocols.iso.dev-environ
Subject: Re: ES-IS Resolved (Token Ring!)
Message-ID: <14934@encore.Encore.COM>
Date: 28 May 91 14:34:30 GMT
Sender: news@Encore.COM
Reply-To: mckellar@pinocchio.encore.com (Steve McKellar)
Followup-To: comp.protocols.iso
Organization: Encore Computer Corp, Marlboro, MA
Lines: 13
Nntp-Posting-Host: pinocchio.encore.com

In article <1991May24.031145.948@netcom.COM> cmilono@netcom.COM (Carlo Milono)
writes:

> Ah, I have found several references that back-up these standards - ahem, 
> however...I failed to mention (because I didn't think it was an issue)
> that I was attempting to route over Token Ring, which uses FUNCTIONAL
> Addresses rather than multicast.

um, could someone explain - or point to an explanation - of FUNCTIONAL
addresses? what they are, how they're used, etc. thanks.


steve mckellar