draft-ietf-avtext-rtp-stream-pause-03.txt   draft-ietf-avtext-rtp-stream-pause-04.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
Network Working Group B. Burman Network Working Group B. Burman
Internet-Draft A. Akram Internet-Draft A. Akram
Updates: 5104 (if approved) Ericsson Updates: 5104 (if approved) Ericsson
Intended status: Standards Track R. Even Intended status: Standards Track R. Even
Expires: April 17, 2015 Huawei Technologies Expires: April 17, 2015 Huawei Technologies
M. Westerlund M. Westerlund
Ericsson Ericsson
October 14, 2014 October 14, 2014
RTP Stream Pause and Resume RTP Stream Pause and Resume
draft-ietf-avtext-rtp-stream-pause-03 draft-ietf-avtext-rtp-stream-pause-04
Abstract Abstract
With the increased popularity of real-time multimedia applications, With the increased popularity of real-time multimedia applications,
it is desirable to provide good control of resource usage, and users it is desirable to provide good control of resource usage, and users
also demand more control over communication sessions. This document also demand more control over communication sessions. This document
describes how a receiver in a multimedia conversation can pause and describes how a receiver in a multimedia conversation can pause and
resume incoming data from a sender by sending real-time feedback resume incoming data from a sender by sending real-time feedback
messages when using Real-time Transport Protocol (RTP) for real time messages when using Real-time Transport Protocol (RTP) for real time
data transport. This document extends the Codec Control Messages data transport. This document extends the Codec Control Messages
skipping to change at page 2, line 20 skipping to change at page 2, line 20
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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. 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 created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6
2.3. Requirements Language . . . . . . . . . . . . . . . . . . 7 2.3. Requirements Language . . . . . . . . . . . . . . . . . . 7
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Point to Point . . . . . . . . . . . . . . . . . . . . . 7 3.1. Point to Point . . . . . . . . . . . . . . . . . . . . . 7
3.2. RTP Mixer to Media Sender . . . . . . . . . . . . . . . . 8 3.2. RTP Mixer to Media Sender . . . . . . . . . . . . . . . . 8
3.3. RTP Mixer to Media Sender in Point-to-Multipoint . . . . 9 3.3. RTP Mixer to Media Sender in Point-to-Multipoint . . . . 9
3.4. Media Receiver to RTP Mixer . . . . . . . . . . . . . . . 10 3.4. Media Receiver to RTP Mixer . . . . . . . . . . . . . . . 10
3.5. Media Receiver to Media Sender Across RTP Mixer . . . . . 10 3.5. Media Receiver to Media Sender Across RTP Mixer . . . . . 10
4. Design Considerations . . . . . . . . . . . . . . . . . . . . 10 4. Design Considerations . . . . . . . . . . . . . . . . . . . . 11
4.1. Real-time Nature . . . . . . . . . . . . . . . . . . . . 11 4.1. Real-time Nature . . . . . . . . . . . . . . . . . . . . 11
4.2. Message Direction . . . . . . . . . . . . . . . . . . . . 11 4.2. Message Direction . . . . . . . . . . . . . . . . . . . . 11
4.3. Apply to Individual Sources . . . . . . . . . . . . . . . 11 4.3. Apply to Individual Sources . . . . . . . . . . . . . . . 12
4.4. Consensus . . . . . . . . . . . . . . . . . . . . . . . . 11 4.4. Consensus . . . . . . . . . . . . . . . . . . . . . . . . 12
4.5. Message Acknowledgments . . . . . . . . . . . . . . . . . 12 4.5. Message Acknowledgments . . . . . . . . . . . . . . . . . 12
4.6. Request Retransmission . . . . . . . . . . . . . . . . . 12 4.6. Request Retransmission . . . . . . . . . . . . . . . . . 13
4.7. Sequence Numbering . . . . . . . . . . . . . . . . . . . 12 4.7. Sequence Numbering . . . . . . . . . . . . . . . . . . . 13
4.8. Relation to Other Solutions . . . . . . . . . . . . . . . 13 4.8. Relation to Other Solutions . . . . . . . . . . . . . . . 13
5. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 13 5. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 14
5.1. Expressing Capability . . . . . . . . . . . . . . . . . . 14 5.1. Expressing Capability . . . . . . . . . . . . . . . . . . 15
5.2. Requesting to Pause . . . . . . . . . . . . . . . . . . . 14 5.2. Requesting to Pause . . . . . . . . . . . . . . . . . . . 15
5.3. Media Sender Pausing . . . . . . . . . . . . . . . . . . 16 5.3. Media Sender Pausing . . . . . . . . . . . . . . . . . . 16
5.4. Requesting to Resume . . . . . . . . . . . . . . . . . . 17 5.4. Requesting to Resume . . . . . . . . . . . . . . . . . . 17
5.5. TMMBR/TMMBN Considerations . . . . . . . . . . . . . . . 18 5.5. TMMBR/TMMBN Considerations . . . . . . . . . . . . . . . 19
6. Participant States . . . . . . . . . . . . . . . . . . . . . 19 6. Participant States . . . . . . . . . . . . . . . . . . . . . 19
6.1. Playing State . . . . . . . . . . . . . . . . . . . . . . 19 6.1. Playing State . . . . . . . . . . . . . . . . . . . . . . 20
6.2. Pausing State . . . . . . . . . . . . . . . . . . . . . . 20 6.2. Pausing State . . . . . . . . . . . . . . . . . . . . . . 20
6.3. Paused State . . . . . . . . . . . . . . . . . . . . . . 20 6.3. Paused State . . . . . . . . . . . . . . . . . . . . . . 21
6.3.1. RTCP BYE Message . . . . . . . . . . . . . . . . . . 21 6.3.1. RTCP BYE Message . . . . . . . . . . . . . . . . . . 21
6.3.2. SSRC Time-out . . . . . . . . . . . . . . . . . . . . 21 6.3.2. SSRC Time-out . . . . . . . . . . . . . . . . . . . . 22
6.4. Local Paused State . . . . . . . . . . . . . . . . . . . 21 6.4. Local Paused State . . . . . . . . . . . . . . . . . . . 22
7. Message Format . . . . . . . . . . . . . . . . . . . . . . . 22 7. Message Format . . . . . . . . . . . . . . . . . . . . . . . 22
8. Message Details . . . . . . . . . . . . . . . . . . . . . . . 24 8. Message Details . . . . . . . . . . . . . . . . . . . . . . . 25
8.1. PAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . 24 8.1. PAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . 25
8.2. PAUSED . . . . . . . . . . . . . . . . . . . . . . . . . 25 8.2. PAUSED . . . . . . . . . . . . . . . . . . . . . . . . . 26
8.3. RESUME . . . . . . . . . . . . . . . . . . . . . . . . . 26 8.3. RESUME . . . . . . . . . . . . . . . . . . . . . . . . . 27
8.4. REFUSED . . . . . . . . . . . . . . . . . . . . . . . . . 27 8.4. REFUSED . . . . . . . . . . . . . . . . . . . . . . . . . 28
8.5. Transmission Rules . . . . . . . . . . . . . . . . . . . 28 8.5. Transmission Rules . . . . . . . . . . . . . . . . . . . 28
9. Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . 28 9. Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . 29
9.1. Offer-Answer Use . . . . . . . . . . . . . . . . . . . . 31 9.1. Offer-Answer Use . . . . . . . . . . . . . . . . . . . . 32
9.2. Declarative Use . . . . . . . . . . . . . . . . . . . . . 32 9.2. Declarative Use . . . . . . . . . . . . . . . . . . . . . 33
10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 32 10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 33
10.1. Offer-Answer . . . . . . . . . . . . . . . . . . . . . . 33 10.1. Offer-Answer . . . . . . . . . . . . . . . . . . . . . . 33
10.2. Point-to-Point Session . . . . . . . . . . . . . . . . . 34 10.2. Point-to-Point Session . . . . . . . . . . . . . . . . . 35
10.3. Point-to-Multipoint using Mixer . . . . . . . . . . . . 38 10.3. Point-to-Multipoint using Mixer . . . . . . . . . . . . 39
10.4. Point-to-Multipoint using Translator . . . . . . . . . . 40 10.4. Point-to-Multipoint using Translator . . . . . . . . . . 41
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44
12. Security Considerations . . . . . . . . . . . . . . . . . . . 44 12. Security Considerations . . . . . . . . . . . . . . . . . . . 45
13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 44 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 45
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 44 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 45
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 45 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 46
15.1. Normative References . . . . . . . . . . . . . . . . . . 45 15.1. Normative References . . . . . . . . . . . . . . . . . . 46
15.2. Informative References . . . . . . . . . . . . . . . . . 45 15.2. Informative References . . . . . . . . . . . . . . . . . 46
Appendix A. Changes From Earlier Versions . . . . . . . . . . . 46 Appendix A. Changes From Earlier Versions . . . . . . . . . . . 47
A.1. Modifications Between Version -02 and -03 . . . . . . . . 46 A.1. Modifications Between Version -02 and -03 . . . . . . . . 47
A.2. Modifications Between Version -01 and -02 . . . . . . . . 47 A.2. Modifications Between Version -01 and -02 . . . . . . . . 48
A.3. Modifications Between Version -00 and -01 . . . . . . . . 47 A.3. Modifications Between Version -00 and -01 . . . . . . . . 48
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 47 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 48
1. Introduction 1. Introduction
As real-time communication attracts more people, more applications As real-time communication attracts more people, more applications
are created; multimedia conversation applications being one example. are created; multimedia conversation applications being one example.
Multimedia conversation further exists in many forms, for example, Multimedia conversation further exists in many forms, for example,
peer-to-peer chat application and multiparty video conferencing peer-to-peer chat application and multiparty video conferencing
controlled by central media nodes, such as RTP Mixers. controlled by central media nodes, such as RTP Mixers.
Multimedia conferencing may involve many participants; each has its Multimedia conferencing may involve many participants; each has its
 End of changes. 14 change blocks. 
40 lines changed or deleted 52 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/