--On Monday, August 30, 2010 04:50:13 PM -0400 Derrick Brashear
<[email protected]> wrote:
On Mon, Aug 30, 2010 at 4:05 PM, Jeffrey Hutzelman <[email protected]> wrote:
--On Monday, August 30, 2010 03:54:09 PM +0100 Simon Wilkinson
<[email protected]> wrote:
On 28 Aug 2010, at 22:53, Derrick Brashear wrote:
I have again revised this draft based on feedback, and -04 is
available.
https://datatracker.ietf.org/doc/draft-brashear-afs3-pts-extended-name
s/
I'm happy with the proposed mechanism for handling Kerberos v5 names in
this version of the document.
As am I.
I believe doing this calls for deleting section 10.2 and the registry
entry for PRAUTHTYPE_KRB5. I also believe it is worth adding to
section 10.4.2 a sentence or two about how non-GSS-API implementations
can perform the conversion by prefixing a fixed octet string and a
32-bit length (see my previous message).
Ok. -05 will follow shortly, then.
Looks good. Note that your reference to RFC1510 is stale; it should be to
RFC4120. I'm not sure why I didn't catch this before. If you use this
link instead:
<http://tools.ietf.org/html/draft-brashear-afs3-pts-extended-names-05>
it is easier to see version history, diff to previous version, and run the
current version through the id-nits tool, which reports various formatting
and other mechanical problems, including the stale reference.
_______________________________________________
AFS3-standardization mailing list
[email protected]
http://michigan-openafs-lists.central.org/mailman/listinfo/afs3-standardization
