Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 6128

RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions,February 2011

File formats:
icon for text fileicon for PDFicon for HTML
Status:
PROPOSED STANDARD
Updates:
RFC 5760
Author:
A. Begen
Stream:
IETF
Source:
avt (rai)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6128

Discuss this RFC: Send questions or comments to the mailing listavt@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6128


Abstract

The Session Description Protocol (SDP) has an attribute that allowsRTP applications to specify an address and a port associated with theRTP Control Protocol (RTCP) traffic. In RTP-based source-specificmulticast (SSM) sessions, the same attribute is used to designate theaddress and the RTCP port of the Feedback Target in the SDPdescription. However, the RTCP port associated with the SSM sessionitself cannot be specified by the same attribute to avoid ambiguity,and thus, is required to be derived from the "m=" line of the mediadescription. Deriving the RTCP port from the "m=" line imposes anunnecessary restriction. This document removes this restriction byintroducing a new SDP attribute. [STANDARDS-TRACK]


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp