RFC 3487: Requirements for Resource Priority Mechanisms for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
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 memo provides information for the Internet community.
Document record
- Document ID
- RFC3487
- Published
- March 2003
- Authors
- H. Schulzrinne
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3486Compressing the Session Initiation Protocol (SIP)Updated
February 2003
- RFC 3485The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)Updated
March 2003
- RFC 3482Number Portability in the Global Switched Telephone Network (GSTN): An OverviewCurrent
February 2003
- RFC 3497RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) 292M VideoCurrent
March 2003
- RFC 3515The Session Initiation Protocol (SIP) Refer MethodUpdated
April 2003
- RFC 3523Internet Emergency Preparedness (IEPREP) Telephony Topology TerminologyCurrent
April 2003
- RFC 3525Gateway Control Protocol Version 1Obsoleted
June 2003
- RFC 3545Enhanced Compressed RTP (CRTP) for Links with High Delay, Packet Loss and ReorderingCurrent
July 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?