Re: RFC-4460

Yes, RFC 2960 did not specify if there is one number space for  
parameters
or one number space for each chunk.

This has been clarified that there is only one number space.

You can write an ID for an extension of the protocol, define there
new parameters and register them at IANA. This is how protocol  
extensions
work.

Best regards
Michael

On Oct 3, 2006, at 10:44 AM, Bhanu Prakash wrote:

>
> The section 2.4.2. of RFC-4460 says that:
>
>
>    ---------
>    New text: (Section 3.2.1)
>    ---------
>
>    The actual SCTP parameters are defined in the specific SCTP chunk
>    sections.  The rules for IETF-defined parameter extensions are
>    defined in Section 13.2.  Note that a parameter type MUST be unique
>    across all chunks.  For example, the parameter type '5' is used to
>    represent an IPv4 address (see Section 3.3.2).  The value '5'  
> then is
>    reserved across all chunks to represent an IPv4 address and MUST  
> NOT
>    be reused with a different meaning in any other chunk.
>
>
> Does it means that the RFC 2960 had allowed to have same parameter  
> type across different chunks..?
> Can an implementor define and use his own parameter type other than  
> what specified in RFC..?
> Please clarify.
>
> Thanks.
> Bhanuprakash.
>
>
>
> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/sigtran