Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

RE: [EFM] EFM Requirements [really Oregon Trail Etherloop?]


So by making it a standard with the relevant reassurances to the IEEE by Elastic regarding access etc. then we could be close to an answer?

R's

Andy

-----Original Message-----
From: Fletcher E Kittredge [mailto:fkittred@xxxxxxx]
Sent: Thursday, August 16, 2001 10:13 PM
To: Frank Miller
Cc: 'Vladimir Oksman'; 'Hugh Barrass'; Lough, Andy; Sherman Ackley;
Stds-802-3-Efm (E-mail)
Subject: Re: [EFM] EFM Requirements [really Oregon Trail Etherloop?] 



Thanks Frank!  

What I take away from your reply is what I have heard elsewhere:  The
Etherloop stuff works well, but is proprietary.  My sense is what
happens is that lots of people look at Etherloop, see that it is a closed,
proprietary protocol and walk away.

regards,
fletcher