Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!csn!boulder!daemon
From: Allen Robel <robel2@mythos.ucs.indiana.edu>
Newsgroups: comp.dcom.sys.cisco
Subject: Re: cisco - proteon interop on FDDI
Message-ID: <35331@boulder.Colorado.EDU>
Date: 23 May 91 15:45:19 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 31

Hi Jay,

   One possible source of trouble is bridging.  The
cisco manual doesn't specifically mention whether
they are an encapsulation or translation bridge
over FDDI.  The manual *does* say this (pp 17-3,
November 1990):

   The transit bridging of Ethernet datagrams across
   an FDDI is also supported.  The term transit refers
   to the fact that the source or destination of the
   datagram cannot be on the FDDI ring itself.

This implies to me that the cisco is an encapsulating
bridge.  If this is so, its pretty much guaranteed that
it will be incompatible *for bridging* with your Proteons.
You may also want to check to see what type of bridging
the Proteon supports.  


If you're not bridging any traffic, you probably won't have 

any problems (unless there are inherent incompatibilities
between the two vendor's FDDI implementations which I
doubt in this day and age...).  Maybe someone else can
speak to this.

regards,

allen