RE: : Diameter SIP Application Command code allocation

German,

>a few weeks ago I wrote to this list requesting that the draft 
>used the 3GPP AVP codes.  Given that this is not going to 
>happen, I understand that new command codes, and a new 
>Application Id will be allocated for all the commands in the 
>draft.  That is, the values for the Cx Interface in 3GPP are 
>NOT going to be used for this RFC.
>
>Could anybody please confirm that?


As the author of:

"Diameter Command Codes for Third Generation Partnership Project (3GPP)
Release 5"

This document says:

   The IANA has allocated Diameter Command Codes 300 through 313, for
   use in 3GPP Release 5.  The protocols defined by these command codes
   have not been carefully reviewed by the IETF community and are not
   considered to be general mechanisms appropriate for broad usage.
   More work is needed to develop general mechanisms and may become a
   work item of an IETF Working Group.  These command codes are intended
   to be used for 3GPP Release 5 only [29.228], [29.229].  Future 3GPP
   releases are expected to make use of alternate mechanisms.

   Command codes for 3GPP Release 6 are expected to be allocated from
   the standard command space, with IETF documentation.  The current
   intent as agreed with 3GPP is to develop a standards track
   application addressing the needs of AAA for SIP/SDP and encompassing
   the requirements of the cellular community.

So, these command codes are for 3GPP Release 5 & not for any later
releases.  This was
something which was agreed between the IESG & 3GPP.  I do not think that
the IETF
can re-claim these for the SIP-Diameter application.

This is something that the AAA WG can decide do to, it would have to be
done via
the IESG and 3GPP Liason.

best regards,
John