RFC 2862: RTP Payload Format for Real-Time Pointers
In plain English — editorial summary, not part of the RFC
This document describes an RTP payload format for transporting the coordinates of a dynamic pointer that may be used during a presentation. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2862
- Published
- June 2000
- Authors
- M. Civanlar; G. Cash
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3550RTP: A Transport Protocol for Real-Time ApplicationsUpdated
July 2003
- RFC 1889RTP: A Transport Protocol for Real-Time ApplicationsObsoleted
January 1996
- RFC 6416RTP Payload Format for MPEG-4 Audio/Visual StreamsCurrent
October 2011
- RFC 2793RTP Payload for Text ConversationObsoleted
May 2000
- RFC 2736Guidelines for Writers of RTP Payload Format SpecificationsUpdated
December 1999
- RFC 3190RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled AudioCurrent
January 2002
- RFC 2343RTP Payload Format for Bundled MPEGCurrent
May 1998
- RFC 3389Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)Current
October 2002
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?