draft-ietf-ieprep-sip-reqs

Last Version:	draft-ietf-ieprep-sip-reqs-03.txt		Tracker Entry
Date:	29-Mar-2004
Disposition:	non-current
Previous Versions:	draft-ietf-ieprep-sip-reqs-03.txt (diff)    - 12-Mar-2003
	draft-ietf-ieprep-sip-reqs-02.txt (diff)    - 07-Dec-2002
	draft-ietf-ieprep-sip-reqs-01.txt (diff)    - 03-Dec-2002
	draft-ietf-ieprep-sip-reqs-00.txt (diff)    - 22-Oct-2002

A new Request for Comments is now available in online RFC libraries.


        RFC 3487

        Title:      Requirements for Resource Priority Mechanisms for
                    the Session Initiation Protocol (SIP)
        Author(s):  H. Schulzrinne
        Status:     Informational
        Date:       February 2003
        Mailbox:    schulzrinne@cs.columbia.edu
        Pages:      17
        Characters: 39615
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-ieprep-sip-reqs-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3487.txt


This document summarizes requirements for prioritizing access to
circuit-switched network, end system and proxy resources for
emergency preparedness communications using the Session Initiation
Protocol (SIP).

This document is a product of the Internet Emergency Preparedness
Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.