--On Friday, December 17, 2010 01:18:56 PM -0500 Jeffrey Altman
<[email protected]> wrote:
I believe that Andrew's feedback is completely appropriate for a last
call. The lack of a definition of "implicit mapping" vs "explicit
mapping" is not something that most readers would notice because I'm
sure that all of us just assume that we know what is meant. It is only
when someone attempts to implement the specification that most
ambiguities are uncovered. I would rather have someone discover a
weakness during Last Call than not have it discovered until after a
document is published.
My interpretation of explicit mappings are those mappings that can be
added, viewed and modified using the protocol specified in this
document. Implicit mappings are those that are implemented in an
implementation specific manner such that they are invisible to the user
of this specification. One example of such implicit mappings are the
krb5 to krb4 principal mappings built-in to OpenAFS rxkad.
I propose that we agree upon a definition to be added to the existing
document and conclude the Last Call since there appear to be no other
outstanding issues.
+1
_______________________________________________
AFS3-standardization mailing list
[email protected]
http://lists.openafs.org/mailman/listinfo/afs3-standardization
