\documentclass[11pt]{article}
\usepackage{times}
\usepackage{ifthen}
\usepackage{i-d}
%\usepackage{rfc}
\usepackage{html}
\usepackage{txtpsfig}
\usepackage{tight}
\usepackage[dvips]{changebar}

\title{SIP URLs for Common Services, Roles and Functions}
\author{Schulzrinne}
\shorttitle{SIP URLs}
\filename{draft-schulzrinne-sip-urls-00}
\wg{}
\expires{December 2001}
\address{Columbia U.}
\pubdate{\today}
\input{../defs}

\begin{document}
\maketitle
\begin{abstract}
This document defines a number of names for common services, roles and
functions found in SIP-based voice-over-IP networks. It extends RFC
2142.
\end{abstract}

\section{Terminology}
\label{sec:terminology}

In this document, the key words ``{\MUST}'', ``{\MUSTNOT}'',
``{\REQUIRED}'', ``{\SHALL}'', ``{\SHALLNOT}'', ``{\SHOULD}'',
``{\SHOULDNOT}'', ``{\RECOMMENDED}'', ``{\MAY}'', and ``{\OPTIONAL}''
are to be interpreted as described in RFC 2119 \cite{rfc2119} and
indicate requirement levels for compliant implementations.

\section{Common Functional Names}
\label{sec:functional}

The names below {\SHOULD} be reachable by SMTP (email), instant
messaging \cite{rfc2778} as well as SIP \cite{rfc2543}, in both
lower-case, upper-case and combinations thereof.  (For example,
variations such as Sos, SoS, SOS should all be valid.) This extends the
names enumerated in RFC 2142 \cite{rfc2142}.

\begin{flushleft}
\begin{tabular}{ll}
sos       & emergency services for members of this organization \cite{draft-schulzrinne-sip-911}\\
911       & alias for ``sos''\\
112       & alias for ``sos''\\
operator  & voice operator for organization\\
sipmaster & contact for technical issues with SIP services\\
voicemail & voicemail address (see also RFC 3087 \cite{rfc3087})\\
\end{tabular}
\end{flushleft}

TBD: Conferences?

\section{Functional Designations}

\begin{flushleft}
\begin{tabular}{ll}
sales & sales department\\
info  & general, typically automated, information\\
help  & general help, e.g., with locating other resources within an organization\\
support & \\
marketing & \\
\end{tabular}
\end{flushleft}

See Section 3, RFC 2142.

Any functional name designated by an email aliases {\SHOULD} also be
available via SIP.  Local language versions of these names {\SHOULD}
also be defined.

\section{Naming Users}

It is {\RECOMMENDED} that organizations allow ``first.last'' and
``first.m.last'' (where ``m'' is the middle initial) as aliases for
their users, with variations that differ only in the case of the
letters, such as ``First.Last'' or ``FIRST.M.LAST'' considered
equivalent to the canonical all-lower-case form.

\bibliographystyle{ieeetr}
\bibliography{string,i-d,rfc}

\section{Acknowledgements}

TBD.

\section{Authors' Addresses}
\begin{flushleft}
Henning Schulzrinne\\
Dept. of Computer Science\\
Columbia University\\
1214 Amsterdam Avenue\\
New York, NY 10027\\
USA\\
electronic mail: {\sf schulzrinne@cs.columbia.edu}
\end{flushleft}

\input{copyright}
\end{document}
