Questions about RfC3310 and RADIUS HTTP-Digest

["Beck01, Wolfgang" <BeckW@t-systems.com>]

Jari,

while preparing the -02 version of the sterman draft, I discovered that
it would take an additional message exchange to handle AKA. In the
previous versions of the draft, nonces where only generated by the RADIUS
client. Assuming that authentication vectors are user-specific, this would
not work with AKA. So I included an optional message exchange. However,
after re-reading my changes, the word "optional" turned up quite frequently.
A bad thing in a standard.

- Do we need RADIUS server generated nonces in other scenarios than AKA?
- Would it be better to put RADIUS AKA Digest into a separate
  (informational) document?

Wolfgang


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>