RFC 5168: XML Schema for Media Control
In plain English — editorial summary, not part of the RFC
This document defines an Extensible Markup Language (XML) Schema for video fast update in a tightly controlled environment, developed by Microsoft, Polycom, Radvision and used by multiple vendors. This document describes a method that has been deployed in Session Initiation Protocol (SIP) based systems over the last three years and is being used across real-time interactive applications from different vendors in an interoperable manner. New implementations are discouraged from using the method described except for backward compatibility purposes. New implementations are required to use the new Full Intra Request command in the RTP Control Protocol (RTCP) channel. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5168
- Published
- March 2008
- Authors
- O. Levin; R. Even; P. Hagendorf
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5277NETCONF Event NotificationsCurrent
July 2008
- RFC 5025Presence Authorization RulesCurrent
December 2007
- RFC 5361A Document Format for Requesting ConsentCurrent
October 2008
- RFC 5388Information Model and XML Data Model for Traceroute MeasurementsCurrent
December 2008
- RFC 4914Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the XML Encoding Rules (XER)Current
July 2007
- RFC 4913Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the Generic String Encoding Rules (GSER)Current
July 2007
- RFC 4912Abstract Syntax Notation X (ASN.X)Current
July 2007
- RFC 4911Encoding Instructions for the Robust XML Encoding Rules (RXER)Current
July 2007
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?