[Ieprep] RFC 3487 on Requirements for Resource Priority Mechanisms for the Session Initiation Protocol (SIP)
rfc-editor@rfc-editor.org Wed, 05 March 2003 14:49 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01983 for <ieprep-archive@odin.ietf.org>; Wed, 5 Mar 2003 09:49:11 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h25F0Aa31624 for ieprep-archive@odin.ietf.org; Wed, 5 Mar 2003 10:00:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25F0A531621 for <ieprep-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 10:00:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01967 for <ieprep-web-archive@ietf.org>; Wed, 5 Mar 2003 09:48:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25Ewb531457; Wed, 5 Mar 2003 09:58:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Npi524879 for <ieprep@optimus.ietf.org>; Tue, 4 Mar 2003 18:51:44 -0500
Received: from gamma.isi.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15542; Tue, 4 Mar 2003 18:40:30 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id h24NgXZ09182; Tue, 4 Mar 2003 15:42:33 -0800 (PST)
Message-Id: <200303042342.h24NgXZ09182@gamma.isi.edu>
To: IETF-Announce:;
Cc: rfc-editor@rfc-editor.org, ieprep@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 04 Mar 2003 15:42:33 -0800
Subject: [Ieprep] RFC 3487 on Requirements for Resource Priority Mechanisms for the Session Initiation Protocol (SIP)
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.