[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AW: AW: [Issue] Review of draft-ietf-radext-digest-auth-01.txt, Diameter dependency
Diameter SIP app already has a normative dependency on the RADIUS Digest
draft (remember the imported Digest-* attributes).
So I don't see a problem in adding or moving that text to the Diameter
I am more worried about Wolfgang's concerns about "Diameter SIP document
is likely to be blocked based on the lack of compatibility with RADIUS
Digest". Can someone expand these concerns, because we should addressed
them. I thought that we have limited compatibility just restricted by
the smaller scope of the RADIUS draft.
Beck01, Wolfgang wrote:
I think Miguel should be included into the discussion.
[Migration Path to Diameter]
We had some discussion about this. If we move it to
Diameter, Miguel Garcia suffers from the dependency. Someone has to bear it. Both
documents have finished WGLC in parallel.
I agree that one of the drafts does need this section.
However, the RADIUS Digest authentication is on a tight time
schedule and I am concerned about delays that could result
from keeping this section in it, particularly since the
Diameter SIP document is likely to be blocked based on the
lack of compatibility with RADIUS Digest. So my advice is to
move it to the Diameter SIP document.
Next Generation IP Services and Systems
+49 6151 937 2863
Am Kavalleriesand 3
Miguel A. Garcia tel:+358-50-4804586
Nokia Research Center Helsinki, Finland
to unsubscribe send a message to email@example.com with
the word 'unsubscribe' in a single line as the message text body.