RFC 5478: IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespaces
In plain English — editorial summary, not part of the RFC
This document creates additional Session Initiation Protocol (SIP) Resource-Priority namespaces to meet the requirements of the US Defense Information Systems Agency, and places these namespaces in the IANA registry. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5478
- Published
- March 2009
- Authors
- J. Polk
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5479Requirements and Analysis of Media Security Management ProtocolsCurrent
April 2009
- RFC 5483ENUM Implementation Issues and ExperiencesCurrent
March 2009
- RFC 5484Associating Time-Codes with RTP StreamsCurrent
March 2009
- RFC 5486Session Peering for Multimedia Interconnect (SPEERMINT) TerminologyCurrent
March 2009
- RFC 5491GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and RecommendationsUpdated
March 2009
- RFC 5459G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) SupportCurrent
January 2009
- RFC 5450Transmission Time Offsets in RTP StreamsCurrent
March 2009
- RFC 5506Support for Reduced-Size Real-Time Transport Control Protocol (RTCP): Opportunities and ConsequencesCurrent
April 2009
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?