RE: : Diameter SIP Application AVP and command codes

Hi,

I agree the best solution would be to use the same AVP-
and command-codes where possible.

I think the application-id must be different, though.


BR,
Mikko


> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]]On Behalf Of
> ext German Blanco (ML/EEM)
> Sent: 03 June, 2005 15:57
> To: '[email protected]'
> Subject: [AAA-WG]: Diameter SIP Application AVP and command codes
> 
> 
> Hi all,
> 
> in the set of AVPs and commands used in the draft there are 
> some that have been already reserved in 3GPP for the same 
> purpose, with the same type and in some cases with the same 
> name as in the draft.
> Are there any plans of reusing the AVP and command codes of 
> the Cx Application?
> 
> This is the list of similar AVPs:
> + 3GPP Vendor AVP           + in the draft
> Server-Name                 SIP-Server-URI
> Server-Capabilities         SIP-Server-Capabilities
> Mandatory-Capability	    SIP-Mandatory-Capability
> Optional-Capability	    SIP-Optional-Capability
> SIP-Number-Auth-Items	    SIP-Number-Auth-Items
> SIP-Authentication-Context  SIP-Authentication-Context
> SIP-Item-Number	          SIP-Item-Number
> SIP-Auth-Data-Item	    SIP-Auth-Data-Item
> Server-Assignment-Type	    SIP-Server-Assignment-Type
> Deregistration-Reason	    SIP-Deregistration-Reason
> Reason-Code	                SIP-Reason-Code
> Reason-Info	                SIP-Reason-Info
> User-Authorization-Type	    SIP-User-Authorization-Type
> User-Data-Already-Available SIP-User-Data-Already-Available
> 
> The command values could all be reused as far as I can see.
> 
> Cheers,
> 
> German Blanco.