Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!uw-beaver!cornell!ken
From: ken@gvax.cs.cornell.edu (Ken Birman)
Newsgroups: comp.sys.isis
Subject: Re: A technical question
Keywords: Bypass protocols
Message-ID: <35565@cornell.UUCP>
Date: 29 Dec 89 17:35:38 GMT
References: <35521@cornell.UUCP> <35564@cornell.UUCP>
Sender: nobody@cornell.UUCP
Reply-To: ken@gvax.cs.cornell.edu (Ken Birman)
Distribution: comp
Organization: Cornell Univ. CS Dept, Ithaca NY
Lines: 19

In article <35564@cornell.UUCP> mak@cs.cornell.edu (Mesaac Makpangou) writes:
>Why not define this as a different protocol with a different name, say a
>Per Group ABCAST....  It seems to me that, ISIS already provides a set of
>protocols enforcing different ordering properties.  This will just
>one more protocol, appropriate for a certain class of applications.

Well, for one thing, ISIS already has too many protocols for any reasonable
purpose.  I would prefer to pretend we have cbcast and abcast, and
gbcast for "special configuration problems".  What I am suggesting is that
Per Group ABCAST should be the one you get when you say "bcast" or "abcast",
e.g. that it be default.

I can certainly leave around a way to force ISIS to use the old flavor of
abcast -- but since this won't provide ordering relative to the per-group
abcast, you will still need to think in per-group terms...

Basically, I would like the defaults to be as fast as possible.

Ken