IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespaces
Extracted elements (10)
DISA requires a large pool of Resource-Priority namespaces to support fine-grained assignment to groups of varying sizes — from entire branches of service (Army, Navy, etc.) down to temporary unit assignments such as task forces or platoons. This justifies deviating from RFC 4412's guidance to have as few namespaces as possible.
According to RFC 4412 Section 8, one or more sets of namespaces can be treated as equivalent when configured as an aggregated grouping. These aggregates may consist of any IANA-registered namespaces, not just adjacent or consecutive ones.
The dash character ('-') within a namespace name is treated as an ordinary ASCII character and is not considered a delimiter in any official capacity. Future namespace definitions could change this convention.
An IANA-registered namespace MUST NOT change the relative priority order of its assigned priority-values.
An IANA-registered namespace SHOULD NOT change the number of its assigned priority-values.
Each of the 40 new namespaces has 10 priority levels ranging from .0 (lowest) to .9 (highest). Priority-values have a relative order for preferential treatment unless consecutive groups are configured as equivalent (first-received, first-treated).
This document creates 40 new SIP Resource-Priority namespaces in four families: dsn-000000 through dsn-000009, drsn-000000 through drsn-000009, rts-000000 through rts-000009, and crts-000000 through crts-000009. Each namespace is wholly independent and uses preemption as its intended algorithm.
This document registers 40 new namespaces in the IANA 'Resource-Priority Namespaces' registry under sip-parameters. Each entry specifies 10 levels, preemption as the intended algorithm, and no new warning or response codes.
This document registers priority-values '0' through '9' (least to greatest) for each of the 40 new namespaces in the IANA 'Resource-Priority Priority-values' registry under sip-parameters.
This document introduces no new security considerations beyond those already documented in RFC 4412 (Communications Resource Priority for SIP).