Re: [sipcore] Draft new: draft-holmberg-sipcore-auth-id-00

[Christer Holmberg <[e-mail]>]

Hi,

>> I've submitted a new draft, draft-holmberg-sipcore-auth-id-00.
>
> It would help if the Abstract was rewritten so that one did not need to know the meanings of "eP-CSCF", "WAF", and "S-CSCF" to understand what the mechanism can do.

I had very limited time to write the draft, so that's the reason it ended up in this way. But, I DO agree with you, and that will be fixed in the next version :)

>> The draft defines a new Authorization header field parameter, which 
>> can carry a string value identifying an authorization server, based on 
>> a requirement from 3GPP (the mechanism is general, though).
>
> The text says that the "authorization-entity" parameter carries "a string value which represents the identity of an authorization server".  You might want to expand
> on that.  I'm guessing it means that any entity that wants to verify the authorization of the REGISTER request should present the request contents to the specified 
> authorization server.

I am not sure I understand what you mean by "present the request contents to the specified authorization server". The identity is obtained from the authorization server (or, the eP-CSCF knows it by configuration). The identity is then provided to the S-CSCF (SIP registrar), which can use the information for policy decisions.

Regards,

Christer