RFC 2824: Call Processing Language Framework and Requirements
In plain English — editorial summary, not part of the RFC
This document describes an architectural framework we call a processing language, as a simple and standardized way for implementing and deploying Internet telephony. A large number of the services we wish to make possible for Internet telephony require fairly elaborate combinations of signalling operations, often in network devices, to complete. It also outlines requirements for such a language. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2824
- Published
- May 2000
- Authors
- J. Lennox; H. Schulzrinne
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2432Terminology for IP Multicast BenchmarkingCurrent
October 1998
- RFC 2805Media Gateway Control Protocol Architecture and RequirementsCurrent
April 2000
- RFC 2960Stream Control Transmission ProtocolObsoleted
October 2000
- RFC 3550RTP: A Transport Protocol for Real-Time ApplicationsUpdated
July 2003
- RFC 3551RTP Profile for Audio and Video Conferences with Minimal ControlUpdated
July 2003
- RFC 3666Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call FlowsCurrent
January 2004
- RFC 1890RTP Profile for Audio and Video Conferences with Minimal ControlObsoleted
January 1996
- RFC 1889RTP: A Transport Protocol for Real-Time ApplicationsObsoleted
January 1996
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?