Bernard, Jari,
> Ok, this is mostly as I wanted it to be in the Radius document.
> However, I wonder if the current Diameter document should
> use individual AVPs instead of Grouped AVP:
>
> SIP-Authenticate ::= < AVP Header: xx12 >
> { Digest-Realm }
> { Digest-Nonce }
> [ Digest-Domain ]
> [ Digest-Opaque ]
> [ Digest-Stale ]
> [ Digest-Algorithm ]
> [ Digest-QoP ]
> [ Digest-HA1]
> * [ Digest-Auth-Param ]
> * [ AVP ]
>
>
> Because translating this grouped AVP appears to require
> additional work from a gateway, no? Bernard/Miguel, can
> you file on issue to the Diameter document on this.
This is a much more general issue than just for the SIP document.
Diameter has improved over RADIUS in a number of areas, one
being support for Grouped AVPs. What you are suggesting is
that we should dumb-down Diameter SIP so that it can live
with RADIUS. However, I don't think we have a requirement for
this. I actually think that in any real deployments of this,
there will need to be specialized support from the gateway
anyway. I don't think putting a generic Diameter-RADIUS
gateway (even if there were such a thing) would work. Also,
I think the deployment scenarios for this interworking have
not really been thought through - is there any need at present
for this? I see this as a non-issue.
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.