Re: Expert review for AAA Diamater assignments

[Jari Arkko <jari.arkko@piuha.net>]

Hi Bert,

If the 3GPP requests are for vendor specific application
identifiers, then we do not need to do anything as its
FCFS (see Section 11.3 of RFC 3588). If the requests are
for standards track application identifiers, then an expert
review with specification required is needed.

Note that the already allocated 16777216-16777218 for
Cx, Sh, and Rf appear to be in the vendor specific
range (0x01000000 = 16777216). A wild guess is that
3GPP wants the rest in the same way.

This would lessen your need to do expert reviews at
least for this request. IANA's suggested modification
of the aaa registry file looks good to me, although
I would like to see a URL and the requesting person's
name in the references section.

Anyway, expert help for 3GPP's use of Diameter is very
useful. I spend surprisingly lot of time in talking to
either our implementation folks or the 3GPP participants
about their use of Diameter. One of the recent topics
has been the application identifier usage of some of
their newer Diameter-based interfaces.

--Jari

Wijnen, Bert (Bert) wrote:

> I believe we have not yet assigned an expert review of
> IANA requests for Diameter parameter assignments.
> So I will have to start up that process too.
>
> For now, can the AAA doctors pls review the below request
> for assignments. I have copied the word content as ASCII text 
> below as well.
>
> Thanks, Bert
> -----------
> AAA Parameters - per [RFC3588]
>
> (last updated 10 October 2004)
>
> AVP Header
>  - AVP Codes
>  - AVP Specific Values
>  - AVP Flags
>  - Application IDs
>  - Command Codes
>  - Command Flags
>
> AVP Codes
> =========
>
> AVP Codes are allocated by designated expert with a 
> specification.  If a block of codes is needed (more than 3),
> IETF Consensus is needed.
>
> .
> .
> .
>
>
> Application IDs
> ===============
>
>  ID values     Name                                Reference
> -----------    ------------------------            ---------
>           0    Diameter common message             [RFC3588]
>           1    NASREQ                              [RFC3588] 
>           2    Mobile IPv4                         [RFC3588]
>           3    Diameter base accounting            [RFC3588]
>  4-16777215    Unallocated (Standards Track)  		
>    16777216    3GPP Cx                             [3GPP TS 29.228 and 29.229]
>    16777217    3GPP Sh                             [3GPP TS 29.328 and 29.329]
>    16777218    3GPP Rf/Ro                          [3GPP TS 32.225]
>    16777xaa    3GPP Wx                             [3GPP TS 29.234]
>    16777xbb    3GPP Zn                             [3GPP TS 29.109]
>    16777xcc    3GPP Zh                             [3GPP TS 29.109]
>    16777xdd    3GPP Gq                             [3GPP TS 29.209]
>    16777xee    3GPP Gmb                            [3GPP TS 29.061]
>
> 1677721916777xff-4294967294 Unallocated (Vendor Specific, FCFS)	
> 4294967295    Relay                               [RFC3588]
>
> .
> .
> .
>
> References
> ----------
> [RAD-IANA]	http://www.iana.org/assignments/radius-types
>     
> [RFC2104]   H. Krawczyk, M. Bellare, and R. Cannetti.  "HMAC: Keyed 
>             Hashing for Message Authentication", RFC 2104, February 1997. 
>
> [RFC3588]  P. Calhoun, J. Loughney, E. Guttman, G. Zorn, and J. Arkko,
>            "Diameter Base Protocol", RFC 3588, September 2003.
>
> [RFC3589]  J. Loughney, "Diameter Command Codes for 3GPP Release 5",
>            RFC 3589, September 2003.
>
> [3GPP TS 29.061]
>
> [3GPP TS 29.109]
>
> [3GPP TS 29.209]
>
> [3GPP TS 29.234]
>
> [3GPP TS 29.228 and 29.229] 
>
> [3GPP TS 29.328 and 29.329]
>
> [3GPP TS 32.225] Patrik Teppo, <patrik.teppo@ericsson.com>, March 2003.
>
> [RFC-ietf-aaa-diameter-nasreq-17.txt]
>             P. Calhoun, G. Zorn, D. Spence, and D. Mitton, "Diameter Network 
>             Access Server Application", RFC XXXX, Month Year.
>
> [RFC-ietf-aaa-diameter-mobileip-20.txt]
>             P. Calhoun, T. Jahansson, C. Perkins, T. Hiller, Ed., and P. McCann,
>             "Diameter Mobile IPv4 Application", RFC XXXX, Month Year.
>
> (registry created 2003-04-08)
>
> []
>
>
> -----Original Message-----
> From: IANA [mailto:iana@iana.org]
> Sent: Thursday, November 18, 2004 10:46
> To: Bert Wijnen
> Subject: FW: New application IDs in AAA Parameters (Kymalainen)
> Importance: High
>
>
> Bert,
>
> Below is the request needing expert review.
> If for some reason I'm wrong on this, please let me know.
> Thanks for your help on this.
>
> Michelle
>
> *********************************************************************
>
> Dear IANA,
> I didn't have a contact person name so I had to sent this in common email
> address.
> We have a need for 5 new 3GPP specific application identifiers (next free
> number after 16777217).
> More information in attached file.
> Best Regards, Kimmo Kymäläinen
> Kimmo Kymäläinen
> Mobile Competence Centre
> 3GPP CN4/EP SCP
> European Telecommunications Standards Institute
> 949 rue Albert Einstein
> F-06921 Sophia Antipolis Cedex
> FRANCE
> Phone +33 (0)4 92 94 42 38
> Fax +33 (0)4 92 38 52 38
> mailto:Kimmo.Kymalainen@etsi.org
> http://www.etsi.org/
> http://www.3gpp.org/
> ETSI, Beyond the future
> <<3GPP specific application identifiers.doc>>