issues in 11 and 12 in the sterman draft

[Jari Arkko <jari.arkko@piuha.net>]

I am happy with the resolutions of everything in
these issues, except for two parts:

(1) My understanding is that there's still
one version of at least of the AAA draft and maybe
of both drafts coming due to the attribute merge.
This was part of issue 11, so I'd like to check
the results when the final text is available.

(2) I think we didn't end the discussion on:

    Jari wrote:

    > The choice between the server and client generated
    > nonces: is there some guidance on how the client knows
    > which one to do? if it believes it may have a user that
    > does Digest AKA then it should do use the server generated
    > scheme? But how would it know this in a roaming case?

    Wolfgang wrote:

    > If you are expecting AKA users, you have to use server
    > generated nonces.

    Jari wrote:

    > I guess my question was how do you know you are expecting
    > AKA users. Is there a fallback in case we were NOT expecting
    > them but one showed up because our roaming partner started
    > supporting AKA yesterday?

    (Or am I missing an e-mail?) I also looked through the draft
    but did not spot text that deals with this. Can we provide
    a server-generated error that says "please try again without
    generating your own nonce"? Or is it too late if some message
    has already been sent to the user at this point?

--Jari

--
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/>