Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP Multiplexing (RFC8035)

IP.com Disclosure Number: IPCOM000248434D
Original Publication Date: 2016-Nov-01
Included in the Prior Art Database: 2016-Nov-29
Document File: 14 page(s) / 12K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

C. Holmberg: AUTHOR

Abstract

RFC 5761 [RFC5761] specifies how to multiplex RTP data packets and RTP Control Protocol (RTCP) packets on a single UDP port, and how to negotiate usage of such multiplexing using the SDP offer/answer mechanism [RFC3264] with an "a=rtcp-mux" attribute. However, the text is unclear on whether an answerer is allowed to include the attribute in an answer even if the associated offer did not contain an attribute.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 23% of the total text.

Internet Engineering Task Force (IETF)                       C. Holmberg Request for Comments: 8035                                      Ericsson Updates: 5761                                              November 2016 Category: Standards Track ISSN: 2070-1721

      Session Description Protocol (SDP) Offer/Answer Clarifications                        for RTP/RTCP Multiplexing

Abstract

   This document updates RFC 5761 by clarifying the SDP offer/answer    negotiation of RTP and RTP Control Protocol (RTCP) multiplexing.  It    makes it clear that an answerer can only include an "a=rtcp-mux"    attribute in a Session Description Protocol (SDP) answer if the    associated SDP offer contained the attribute.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8035.

 Holmberg                     Standards Track                    [Page 1]
 RFC 8035               RTP/RTCP Mux Clarifications         November 2016

 Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF    Contributions published or made publicly available before November    10, 2008.  The person(s) controlling the copyright in some of this    material may not have granted the IETF Trust the right to allow    modifications of such material outside the IETF Standards Process.    Without obtaining an adequate license from the person(s) controlling    the copyright in such materials, this document may not be modified    outside the IETF Standards Process, and derivative works of it may    not be...