\section{IANA Registration of \header{Resource-Priority} and
\header{Accept-Resource-Priority} Header Fields}
\label{sec:iana-registration}

The following is the registration for the \header{Resource-Priority}
header field:

\begin{description}
\item[RFC number:] RFCxxxx
\item[Header name:] \header{Resource-Priority}
\item[Compact form:] none
\end{description}

The following is the registration for the
\header{Accept-Resource-Priority} header field:

\begin{description}
\item[RFC number:] RFCxxxx
\item[Header name:] \header{Accept-Resource-Priority}
\item[Compact form:] none
\end{description}

\section{IANA Registration for Option Tag \header{Resource-Priority}}
\label{sec:iana-option}

\begin{description}
\item[RFC number:] RFCxxxx
\item[Name of option tag:] \header{Resource-Priority}
\item[Descriptive text:] Indicates or requests support for the resource
priority mechanism.
\end{description}

\section{IANA Registration for Response Code 417}
\label{sec:iana-417}

\begin{description}
\item[RFC number:] RFCxxxx
\item[Response code:] 417
\item[Default reason phrase:] Unknown Resource-Priority
\end{description}

\section{IANA Considerations}
\label{sec:iana}

Additional namespaces and priority values are registered with IANA. 
Within each namespace, the registration may indicate the relative
precedence levels, expressed as an ordered list.  New labels should not
be added to existing namespaces.  The registration {\SHOULD} describe
how SIP elements should treat requests from that namespace, e.g.,
whether preemption or only preferential queueing are allowed.  A
reference to a stable external document, e.g., by the International
Telecommunication Union, other SDOs or national regulatory bodies,
suffices.  An expert review, by an expert designated by the Transport
Area Director or designate, is required.

Namespaces do not describe how they relate to other existing namespaces,
as each namespace is independent of other registrations. 
