RE: draft-ietf-sigtran-security-03.txt

["Peterson, Jon" <jon.peterson@neustar.biz>]

Hello Michelle,

I think we have this cleared up now.

The intention was that these message class parameters should be registered
in the following (in the first table here):

http://www.iana.org/assignments/sigtran-adapt

Unfortunately, nothing is registered there now. These registries were
defined in RFC3332, and RFC3332 even declared some values for these
parameters (see Section 3.1.2 for message class values), but the IANA
Considerations of RFC3332 did not direct IANA to pre-populate the registry
with these values.

Ultimately, I think the message class registry at the sigtran-adapt page
should be provisioned with the message class values in Section 3.1.2. Either
way, these message class values in sigtran-security are supposed to go into
that registry.

- J

> -----Original Message-----
> From: Michelle S. Cotton [mailto:cotton@icann.org]
> Sent: Wednesday, August 20, 2003 3:37 PM
> To: Jon Peterson
> Cc: iana@iana.org; iesg@ietf.org
> Subject: draft-ietf-sigtran-security-03.txt
> 
> 
> Jon,
> 
> Which registry will this message be reserved in?
> 
> Can you clarify?
> 
> Thanks,
> 
> Michelle
> IANA
> 
> 
> 10. IANA Considerations
> 
>    The message class 10 has to be reserved for STARTTLS 
> messages for all
>    SIGTRAN adaptation layers. For this message class, message 
> type 1 has
>    to be reserved for the STARTTLS message, message type 2 for the
>    STARTTLS_ACK message.
>