Multicore SIP parsing with imperative and declarative implementations. RFC 6157 - IPv6 Transition in the Session Initiation Protocol (SIP) [Docs] [txt|pdf] [draft-ietf-sippin...]
[Diff1] [Diff2] [Errata] PROPOSED STANDARD Errata Exist Internet Engineering Task Force (IETF) G. Camarillo Request for Comments: 6157 Ericsson Updates: 3264 K. El Malki Category: Standards Track Athonet ISSN: 2070-1721 V. Gurbani Bell Labs, Alcatel-Lucent April 2011 Abstract This document describes how the IPv4 Session Initiation Protocol (SIP) user agents can communicate with IPv6 SIP user agents (and vice versa) at the signaling layer as well as exchange media once the session has been successfully set up. RFC 6157 IPv6 Transition in SIP April 2011 This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. 1.
SIP [3] is a protocol to establish and manage multimedia sessions. RFC 6157 IPv6 Transition in SIP April 2011 This document addresses the system-level issues in order to make SIP work successfully between IPv4 and IPv6. RFC 6184 - RTP Payload Format for H.264 Video. RFC 4583 - Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams. [Docs] [txt|pdf] [draft-ietf-mmusic...]
[Diff1] [Diff2] [Errata] PROPOSED STANDARD Errata Exist Network Working Group G. Camarillo Request for Comments: 4583 Ericsson Category: Standards Track November 2006 Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. RFC 4583 SDP Format for BFCP Streams November 2006 1. As discussed in the BFCP (Binary Floor Control Protocol) specification [8], a given BFCP client needs a set of data in order to establish a BFCP connection to a floor control server. 2. 3.
This section describes how to generate an 'm' line for a BFCP stream. 4. When two endpoints establish a BFCP stream, they need to determine which of them acts as a floor control server. RFC 4566 - SDP: Session Description Protocol. [Docs] [txt|pdf] [draft-ietf-mmusic...]
[Diff1] [Diff2] [Errata] PROPOSED STANDARD Errata Exist Network Working Group M. Handley Request for Comments: 4566 UCL Obsoletes: 2327, 3266 V. Jacobson Category: Standards Track Packet Design C. Perkins University of Glasgow July 2006 Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. RFC 3840 - Indicating User Agent Capabilities in the Session Initiation Protocol (SIP) [Docs] [txt|pdf] [draft-ietf-sip-ca...]
[Diff1] [Diff2] PROPOSED STANDARD Network Working Group J. Rosenberg Request for Comments: 3840 dynamicsoft Category: Standards Track H. Schulzrinne Columbia University P. Kyzivat Cisco Systems August 2004 Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. RFC 3840 SIP Capabilities August 2004 Table of Contents 1. RFC 3840 SIP Capabilities August 2004 1. Session Initiation Protocol (SIP) [1] user agents vary widely in their capabilities and in the types of devices they represent. RFC 3840 SIP Capabilities August 2004 the Contact header field. 2. In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 [2] and indicate requirement levels for compliant implementations.
RFC 3264 - An Offer/Answer Model with Session Description Protocol (SDP) Session Description Protocol. The Session Description Protocol (SDP) is a format for describing streaming media initialization parameters.
The IETF published the original specification as an IETF Proposed Standard in April 1998,[1] and subsequently published a revised specification as an IETF Proposed Standard as RFC 4566 in July 2006.[2] SDP is intended for describing multimedia communication sessions for the purposes of session announcement, session invitation, and parameter negotiation. SDP does not deliver media itself but is used for negotiation between end points of media type, format, and all associated properties. The set of properties and parameters are often called a session profile. SDP is designed to be extensible to support new media types and formats. Session description[edit] A session is described by a series of fields, one per line. <character>=<value> Where <character> is a single case-significant character and value is structured text whose format depends upon attribute type.
RFC 4585 - Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF) [Docs] [txt|pdf] [draft-ietf-avt-rt...]
[Diff1] [Diff2] [Errata] Updated by: 5506 PROPOSED STANDARD Errata Exist Network Working Group J. Ott Request for Comments: 4585 Helsinki University of Technology Category: Standards Track S. Wenger Nokia N. Sato Oki C. RFC 4585 RTP/AVPF July 2006 Table of Contents 1. RFC 4585 RTP/AVPF July 2006. Issue 114 - libjingle - Video keyframe requests - Google Talk Voice and P2P Interoperability Library. RFC 5104 - Codec Control Messages in the RTP Audio-Visual Profil (RFC5104)