On Tue, 11 Mar 2014, [email protected] wrote:
A new version of I-D, draft-wilkinson-afs3-rxgk-afs-05.txt has been successfully submitted by Benjamin Kaduk and posted to the IETF repository. Name: draft-wilkinson-afs3-rxgk-afs Revision: 05 Title: Integrating rxgk with AFS Document date: 2014-03-11 Group: Individual Submission Pages: 23 URL: http://www.ietf.org/internet-drafts/draft-wilkinson-afs3-rxgk-afs-05.txt Status: https://datatracker.ietf.org/doc/draft-wilkinson-afs3-rxgk-afs/ Htmlized: http://tools.ietf.org/html/draft-wilkinson-afs3-rxgk-afs-05 Diff: http://www.ietf.org/rfcdiff?url2=draft-wilkinson-afs3-rxgk-afs-05 Abstract: This document describes how the new GSSAPI-based rxgk security class for RX is integrated with the AFS application protocol. It describes a number of extensions to the basic rxgk protocol, clarifies a number of implementation issues, and provides values for the application- specific elements of rxgk.
There's a lot of churn between -04 and -05. (Sorry!) I moved a bunch of content around to try and improve the organization and make things flow better, so lots of things got moved and consolidated and reworked to transition through each other, but I think that the document has more of a flow to it, now.
I also changed the token format: now there are separate PrAuthName<>s in the token for the user identity and the identity to be used for callbacks created from connections using this token (user_tok and cb_tok, respectively). This ends up making for a pretty clear division of what's used for what, actually.
I made a bit more explicit where we are specifying bits that the core rxgk document left as "application-specific", and I copied the editorial note about the RFC 4402 PRF+ function's counter.
Since a lot of the text has changed, it would be nice to get fresh eyes on this one.
-Ben _______________________________________________ AFS3-standardization mailing list [email protected] http://lists.openafs.org/mailman/listinfo/afs3-standardization
