Miguel,
> As you probably know, the Diameter SIP application supports this
> operational mode where nonces are generated in the Diameter server. it
> could be possible to have another mode of operation where nonces are
> generated in the Diameter client (SIP server). Actually, this is the
> approach that has been taken by the RADIUS HTTP/SIP Digest draft: there
> are two modes of operation, one where nonces are generated in the RADIUS
> server; the other where nonces are generated in the RADIUS client.
>
> Since Diameter SIP app does not provide one of this modes, it won't be
> possible to provide a smooth transition or compatibility between RADIUS
> and Diameter. We have been asked to enhance the Diameter SIP application
> by adding the mode of operation where nonces are generated in the
> Diameter client (SIP server).
>
> I have been doing an investigation and there is no technical concern why
> this wouldn't work. The current Diameter SIP app draft does not
> implement this mode because we never had requirements. But now we have
> them, and we should do it.
>
> So I would be creating a new revision of the draft in the next weeks. If
> someone has any comment, please do it now.
What is the real requirement for this? It seems that the RADIUS HTTP/SIP
digest draft has an additional mode of operation that is not included
the Diameter SIP app. What is the usage / deployment scenario where this
is needed? If there isn't a pressing need for this, I think we should not
support this mode in the current Diameter SIP application, but leave it
to an extension if there is need or desire.
At some point, we've got to finish this work, and not endlessly tweak this
stuff forever. Unless there is concensus on adding this feature, I don't think
we address it.
John
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.