[AFS3-std] Re: rxgk (protocol) error codes

[Andrew Deason]

On Fri, 4 Jan 2013 11:42:12 -0500 (EST)
Benjamin Kaduk <kaduk@MIT.EDU> wrote:

> I think jaltman also wanted some guidance on how these codes should be
> used to go into the rxgk document.  I am not opposed to this, and once
> we get agreement on what things mean (and which ones to include), I
> can put them in the document somewhere.  It might end up being a new
> section.

Specifically I think, under what circumstances an endpoint generates
these (generally the direction you're already going for in these
descriptions), and what an endpoint is supposed to do when it receives
those errors. From what I recall from what Simon said in jabber, for all
or almost all of these, when you get any of these errors you're just
supposed to fail the whole operation.

To me, that is as important as any other aspect of the description for
one of the codes; the behavior around generating/receiving the code is
what defines it.


I'd also just like to note that I think spending too much time early on
on the specific error code values is a waste of time. You/we'd have a
better idea on error codes with an implementation underway, and it won't
be finalized until then, anyway. Especially if the way a client handles
all of them is the same... The ones listed make sense to me so far,
though.

-- 
Andrew Deason
adeason@sinenomine.net