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

This document calls for IANA to:

\begin{itemize}
\item register two new XML namespace URNs per
\citenorm{draft-mealling-iana-xmlns-registry};

\item establish registry for activity categories
(Section~\ref{sec:activity}), place types (Section~\ref{sec:placetype}),
and relationships (Section~\ref{sec:relationship}).

\end{itemize}

Note that this document does not need a new content type.  It inherits
the content type from \citenorm{draft-ietf-impp-cpim-pidf}, namely
\verb|application/cpim-pidf+xml|.

\subsection{URN Sub-Namespace Registration for
'urn:ietf:params:xml:ns:pidf:rpid-status'}

\begin{description}
\item[URI:] urn:ietf:params:xml:ns:rpid-status

\item[Description:] This is the XML namespace for XML elements defined
by RFCXXXX to describe rich presence information extensions for the
status element in the PIDF presence document format in the
\begin{flushleft}
\verb|application/cpim-pidf+xml| 
\end{flushleft}
content type.

\item[Registrant Contact:] 
IETF, SIMPLE working group, \xmlelement{simple@ietf.org},\\
Henning Schulzrinne, \xmlelement{hgs@cs.columbia.edu}

\item[XML:] 
\begin{verbatim}
 BEGIN
   <?xml version="1.0"?>
   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
   "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
   <html xmlns="http://www.w3.org/1999/xhtml
   <head>
        <meta http-equiv="content-type"
        content="text/html;charset=iso-8859-1"/>
        <title>RPID -- Rich Presence Information Data Format 
  for Presence</title>
   </head>
   <body>
       <h1>Namespace for rich presence extension (status)</h1>
       <h2>application/pidf+xml</h2>
       <p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
    </body>
    </html>
   END
\end{verbatim}

\end{description}

\subsection{URN Sub-Namespace Registration for
'urn:ietf:params:xml:ns:pidf:rpid-tuple'}

\begin{description}
\item[URI:] urn:ietf:params:xml:ns:rpid-tuple

\item[Description:] This is the XML namespace for XML elements defined
by RFCXXXX to describe rich presence information extensions for the
tuple element in the PIDF presence document format in the
\begin{flushleft}
\verb|application/cpim-pidf+xml| 
\end{flushleft}
content type.

\item[Registrant Contact:] 
IETF, SIMPLE working group, \xmlelement{simple@ietf.org},\\
Henning Schulzrinne, \xmlelement{hgs@cs.columbia.edu}

\item[XML:] 
\begin{verbatim}
 BEGIN
   <?xml version="1.0"?>
   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
   "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
   <html xmlns="http://www.w3.org/1999/xhtml
   <head>
        <meta http-equiv="content-type"
        content="text/html;charset=iso-8859-1"/>
        <title>RPID -- Rich Presence Information Data Format 
  for Presence</title>
   </head>
   <body>
       <h1>Namespace for rich presence extension (tuple)</h1>
       <h2>application/pidf+xml</h2>
       <p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
    </body>
    </html>
   END
\end{verbatim}

\end{description}

\subsection{Place Type, Tuple Type, Activities, Relationships}

This document creates new IANA registries for activities, tuple types,
place types and relationships.  All are XML tokens.  Registered tokens
must be documented at the time of registration, as most descriptions are
expected to be brief.

The SIMPLE working group, or, if no longer available, the SIP working
group should be consulted prior to registration.
