| draft-ietf-rtcweb-rtp-usage-19.txt | draft-ietf-rtcweb-rtp-usage-20.txt | |||
|---|---|---|---|---|
| RTCWEB Working Group C. S. Perkins | RTCWEB Working Group C. S. Perkins | |||
| Internet-Draft University of Glasgow | Internet-Draft University of Glasgow | |||
| Intended status: Standards Track M. Westerlund | Intended status: Standards Track M. Westerlund | |||
| Expires: April 30, 2015 Ericsson | Expires: May 14, 2015 Ericsson | |||
| J. Ott | J. Ott | |||
| Aalto University | Aalto University | |||
| October 27, 2014 | November 10, 2014 | |||
| Web Real-Time Communication (WebRTC): Media Transport and Use of RTP | Web Real-Time Communication (WebRTC): Media Transport and Use of RTP | |||
| draft-ietf-rtcweb-rtp-usage-19 | draft-ietf-rtcweb-rtp-usage-20 | |||
| Abstract | Abstract | |||
| The Web Real-Time Communication (WebRTC) framework provides support | The Web Real-Time Communication (WebRTC) framework provides support | |||
| for direct interactive rich communication using audio, video, text, | for direct interactive rich communication using audio, video, text, | |||
| collaboration, games, etc. between two peers' web-browsers. This | collaboration, games, etc. between two peers' web-browsers. This | |||
| memo describes the media transport aspects of the WebRTC framework. | memo describes the media transport aspects of the WebRTC framework. | |||
| It specifies how the Real-time Transport Protocol (RTP) is used in | It specifies how the Real-time Transport Protocol (RTP) is used in | |||
| the WebRTC context, and gives requirements for which RTP features, | the WebRTC context, and gives requirements for which RTP features, | |||
| profiles, and extensions need to be supported. | profiles, and extensions need to be supported. | |||
| skipping to change at page 1, line 39 | skipping to change at page 1, line 39 | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on April 30, 2015. | This Internet-Draft will expire on May 14, 2015. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2014 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 19, line 13 | skipping to change at page 19, line 13 | |||
| RTP bandwidth, and can potentially caused increased packet loss if | RTP bandwidth, and can potentially caused increased packet loss if | |||
| the original packet loss was caused by network congestion. Note, | the original packet loss was caused by network congestion. Note, | |||
| however, that retransmission of an important lost packet to repair | however, that retransmission of an important lost packet to repair | |||
| decoder state can have lower cost than sending a full intra frame. | decoder state can have lower cost than sending a full intra frame. | |||
| It is not appropriate to blindly retransmit RTP packets in response | It is not appropriate to blindly retransmit RTP packets in response | |||
| to a NACK. The importance of lost packets and the likelihood of them | to a NACK. The importance of lost packets and the likelihood of them | |||
| arriving in time to be useful needs to be considered before RTP | arriving in time to be useful needs to be considered before RTP | |||
| retransmission is used. | retransmission is used. | |||
| Receivers are REQUIRED to implement support for RTP retransmission | Receivers are REQUIRED to implement support for RTP retransmission | |||
| packets [RFC4588] (both session multiplexing and SSRC multiplexing | packets [RFC4588] sent using SSRC multiplexing, and MAY also support | |||
| need to be supported; see Section 4.4). Senders MAY send RTP | RTP retransmission packets sent using session multiplexing. Senders | |||
| retransmission packets in response to NACKs if the RTP retransmission | MAY send RTP retransmission packets in response to NACKs if support | |||
| payload format has been negotiated for the session, and if the sender | for the RTP retransmission payload format has been negotiated, and if | |||
| believes it is useful to send a retransmission of the packet(s) | the sender believes it is useful to send a retransmission of the | |||
| referenced in the NACK. An RTP sender does not need to retransmit | packet(s) referenced in the NACK. Senders do not need to retransmit | |||
| every NACKed packet. | every NACKed packet. | |||
| 6.2. Forward Error Correction (FEC) | 6.2. Forward Error Correction (FEC) | |||
| The use of Forward Error Correction (FEC) can provide an effective | The use of Forward Error Correction (FEC) can provide an effective | |||
| protection against some degree of packet loss, at the cost of steady | protection against some degree of packet loss, at the cost of steady | |||
| bandwidth overhead. There are several FEC schemes that are defined | bandwidth overhead. There are several FEC schemes that are defined | |||
| for use with RTP. Some of these schemes are specific to a particular | for use with RTP. Some of these schemes are specific to a particular | |||
| RTP payload format, others operate across RTP packets and can be used | RTP payload format, others operate across RTP packets and can be used | |||
| with any payload format. It needs to be noted that using redundant | with any payload format. It needs to be noted that using redundant | |||
| skipping to change at page 39, line 6 | skipping to change at page 39, line 6 | |||
| [I-D.ietf-avtcore-multi-media-rtp-session] | [I-D.ietf-avtcore-multi-media-rtp-session] | |||
| Westerlund, M., Perkins, C., and J. Lennox, "Sending | Westerlund, M., Perkins, C., and J. Lennox, "Sending | |||
| Multiple Types of Media in a Single RTP Session", draft- | Multiple Types of Media in a Single RTP Session", draft- | |||
| ietf-avtcore-multi-media-rtp-session-06 (work in | ietf-avtcore-multi-media-rtp-session-06 (work in | |||
| progress), October 2014. | progress), October 2014. | |||
| [I-D.ietf-avtcore-rtp-circuit-breakers] | [I-D.ietf-avtcore-rtp-circuit-breakers] | |||
| Perkins, C. and V. Singh, "Multimedia Congestion Control: | Perkins, C. and V. Singh, "Multimedia Congestion Control: | |||
| Circuit Breakers for Unicast RTP Sessions", draft-ietf- | Circuit Breakers for Unicast RTP Sessions", draft-ietf- | |||
| avtcore-rtp-circuit-breakers-06 (work in progress), July | avtcore-rtp-circuit-breakers-07 (work in progress), | |||
| 2014. | October 2014. | |||
| [I-D.ietf-avtcore-rtp-multi-stream-optimisation] | [I-D.ietf-avtcore-rtp-multi-stream-optimisation] | |||
| Lennox, J., Westerlund, M., Wu, Q., and C. Perkins, | Lennox, J., Westerlund, M., Wu, Q., and C. Perkins, | |||
| "Sending Multiple Media Streams in a Single RTP Session: | "Sending Multiple Media Streams in a Single RTP Session: | |||
| Grouping RTCP Reception Statistics and Other Feedback ", | Grouping RTCP Reception Statistics and Other Feedback ", | |||
| draft-ietf-avtcore-rtp-multi-stream-optimisation-00 (work | draft-ietf-avtcore-rtp-multi-stream-optimisation-00 (work | |||
| in progress), July 2013. | in progress), July 2013. | |||
| [I-D.ietf-avtcore-rtp-multi-stream] | [I-D.ietf-avtcore-rtp-multi-stream] | |||
| Lennox, J., Westerlund, M., Wu, W., and C. Perkins, | Lennox, J., Westerlund, M., Wu, W., and C. Perkins, | |||
| "Sending Multiple Media Streams in a Single RTP Session", | "Sending Multiple Media Streams in a Single RTP Session", | |||
| draft-ietf-avtcore-rtp-multi-stream-05 (work in progress), | draft-ietf-avtcore-rtp-multi-stream-06 (work in progress), | |||
| July 2014. | October 2014. | |||
| [I-D.ietf-rtcweb-security-arch] | [I-D.ietf-rtcweb-security-arch] | |||
| Rescorla, E., "WebRTC Security Architecture", draft-ietf- | Rescorla, E., "WebRTC Security Architecture", draft-ietf- | |||
| rtcweb-security-arch-10 (work in progress), July 2014. | rtcweb-security-arch-10 (work in progress), July 2014. | |||
| [I-D.ietf-rtcweb-security] | [I-D.ietf-rtcweb-security] | |||
| Rescorla, E., "Security Considerations for WebRTC", draft- | Rescorla, E., "Security Considerations for WebRTC", draft- | |||
| ietf-rtcweb-security-07 (work in progress), July 2014. | ietf-rtcweb-security-07 (work in progress), July 2014. | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| skipping to change at page 42, line 15 | skipping to change at page 42, line 15 | |||
| "Negotiating Media Multiplexing Using the Session | "Negotiating Media Multiplexing Using the Session | |||
| Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle- | Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle- | |||
| negotiation-12 (work in progress), October 2014. | negotiation-12 (work in progress), October 2014. | |||
| [I-D.ietf-payload-rtp-howto] | [I-D.ietf-payload-rtp-howto] | |||
| Westerlund, M., "How to Write an RTP Payload Format", | Westerlund, M., "How to Write an RTP Payload Format", | |||
| draft-ietf-payload-rtp-howto-13 (work in progress), | draft-ietf-payload-rtp-howto-13 (work in progress), | |||
| January 2014. | January 2014. | |||
| [I-D.ietf-rmcat-cc-requirements] | [I-D.ietf-rmcat-cc-requirements] | |||
| Jesup, R., "Congestion Control Requirements For RMCAT", | Jesup, R. and Z. Sarker, "Congestion Control Requirements | |||
| draft-ietf-rmcat-cc-requirements-06 (work in progress), | for Interactive Real-Time Media", draft-ietf-rmcat-cc- | |||
| October 2014. | requirements-07 (work in progress), October 2014. | |||
| [I-D.ietf-rtcweb-audio] | [I-D.ietf-rtcweb-audio] | |||
| Valin, J. and C. Bran, "WebRTC Audio Codec and Processing | Valin, J. and C. Bran, "WebRTC Audio Codec and Processing | |||
| Requirements", draft-ietf-rtcweb-audio-07 (work in | Requirements", draft-ietf-rtcweb-audio-07 (work in | |||
| progress), October 2014. | progress), October 2014. | |||
| [I-D.ietf-rtcweb-overview] | [I-D.ietf-rtcweb-overview] | |||
| Alvestrand, H., "Overview: Real Time Protocols for | Alvestrand, H., "Overview: Real Time Protocols for | |||
| Browser-based Applications", draft-ietf-rtcweb-overview-12 | Browser-based Applications", draft-ietf-rtcweb-overview-12 | |||
| (work in progress), October 2014. | (work in progress), October 2014. | |||
| End of changes. 8 change blocks. | ||||
| 17 lines changed or deleted | 17 lines changed or added | |||
This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||