RFC 3087: Control of Service Context using SIP Request-URI
In plain English — editorial summary, not part of the RFC
This memo describes a useful way to conceptualize the use of the standard SIP (Session Initiation Protocol) Request-URI (Uniform Resource Identifier) that the authors and many members of the SIP community think is suitable as a convention. It does not define any new protocol with respect to RFC 2543. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3087
- Published
- April 2001
- Authors
- B. Campbell; R. Sparks
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 39
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2732Format for Literal IPv6 Addresses in URL'sObsoleted
December 1999
- RFC 3050Common Gateway Interface for SIPCurrent
January 2001
- RFC 2192IMAP URL SchemeObsoleted
September 1997
- RFC 2187Application of Internet Cache Protocol (ICP), version 2Current
September 1997
- RFC 2296HTTP Remote Variant Selection Algorithm -- RVSA/1.0Current
March 1998
- RFC 1959An LDAP URL FormatObsoleted
June 1996
- RFC 5092IMAP URL SchemeUpdated
November 2007
- RFC 3085URN Namespace for NewsML ResourcesCurrent
March 2001
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?