draft-ietf-avtcore-idms-08.txt   draft-ietf-avtcore-idms-09.txt 
AVTCore R. van Brandenburg AVTCore R. van Brandenburg
Internet-Draft H. Stokking Internet-Draft H. Stokking
Intended status: Standards Track O. van Deventer Intended status: Standards Track O. van Deventer
Expires: July 21, 2013 TNO Expires: September 20, 2013 TNO
F. Boronat F. Boronat
M. Montagud M. Montagud
Universitat Politecnica de Universitat Politecnica de
Valencia Valencia
K. Gross K. Gross
AVA Networks AVA Networks
January 17, 2013 March 19, 2013
Inter-destination Media Synchronization using the RTP Control Protocol Inter-destination Media Synchronization using the RTP Control Protocol
(RTCP) (RTCP)
draft-ietf-avtcore-idms-08 draft-ietf-avtcore-idms-09
Abstract Abstract
This document defines a new RTP Control Protocol (RTCP) Packet Type This document defines a new RTP Control Protocol (RTCP) Packet Type
and RTCP Extended Report (XR) Block Type to be used for achieving and RTCP Extended Report (XR) Block Type to be used for achieving
Inter-Destination Media Synchronization (IDMS). IDMS is the process Inter-Destination Media Synchronization (IDMS). IDMS is the process
of synchronizing playout across multiple geographically distributed of synchronizing playout across multiple geographically distributed
media receivers. Using the RTCP XR IDMS Reporting Block defined in media receivers. Using the RTCP XR IDMS Reporting Block defined in
this document, media playout information from participants in a this document, media playout information from participants in a
synchronization group can be collected. Based on the collected synchronization group can be collected. Based on the collected
skipping to change at page 2, line 6 skipping to change at page 2, line 6
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 July 21, 2013. This Internet-Draft will expire on September 20, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 3, line 28 skipping to change at page 3, line 28
8. RTCP Packet Type for IDMS (IDMS Settings) . . . . . . . . . . 12 8. RTCP Packet Type for IDMS (IDMS Settings) . . . . . . . . . . 12
9. Timing and NTP Considerations . . . . . . . . . . . . . . . . 13 9. Timing and NTP Considerations . . . . . . . . . . . . . . . . 13
10. On the use of presentation timestamps . . . . . . . . . . . . 15 10. On the use of presentation timestamps . . . . . . . . . . . . 15
11. SDP Signalling for RTCP IDMS Packet Type . . . . . . . . . . . 15 11. SDP Signalling for RTCP IDMS Packet Type . . . . . . . . . . . 15
12. SDP rules . . . . . . . . . . . . . . . . . . . . . . . . . . 16 12. SDP rules . . . . . . . . . . . . . . . . . . . . . . . . . . 16
12.1. Offer/Answer rules . . . . . . . . . . . . . . . . . . . . 16 12.1. Offer/Answer rules . . . . . . . . . . . . . . . . . . . . 16
12.2. Declarative cases . . . . . . . . . . . . . . . . . . . . 17 12.2. Declarative cases . . . . . . . . . . . . . . . . . . . . 17
13. Security Considerations . . . . . . . . . . . . . . . . . . . 17 13. Security Considerations . . . . . . . . . . . . . . . . . . . 17
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
14.1. RTCP IDMS Packet Type . . . . . . . . . . . . . . . . . . 18 14.1. RTCP IDMS Packet Type . . . . . . . . . . . . . . . . . . 18
14.2. RTCP XR IDMS Report Block . . . . . . . . . . . . . . . . 18 14.2. RTCP XR IDMS Report Block . . . . . . . . . . . . . . . . 19
14.3. RTCP-IDMS SDP Attribute . . . . . . . . . . . . . . . . . 19 14.3. RTCP-IDMS SDP Attribute . . . . . . . . . . . . . . . . . 19
14.4. Contact Information for Registrations . . . . . . . . . . 19 14.4. Contact Information for Registrations . . . . . . . . . . 19
15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 19 15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 20
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
16.1. Normative References . . . . . . . . . . . . . . . . . . . 20 16.1. Normative References . . . . . . . . . . . . . . . . . . . 20
16.2. Informative References . . . . . . . . . . . . . . . . . . 21 16.2. Informative References . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
Inter-Destination Media Synchronization (IDMS) refers to the playout Inter-Destination Media Synchronization (IDMS) refers to the playout
of media streams at two or more geographically distributed locations of media streams at two or more geographically distributed locations
in a time synchronized manner. It can be applied to both unicast and in a time synchronized manner. It can be applied to both unicast and
skipping to change at page 6, line 11 skipping to change at page 6, line 11
delay, this use case needs even more accuracy than the video wall use delay, this use case needs even more accuracy than the video wall use
case. Depending on the exact application, the need for accuracy can case. Depending on the exact application, the need for accuracy can
then be in the range of microseconds. then be in the range of microseconds.
5. Overview of IDMS operation 5. Overview of IDMS operation
This section provides a brief example of how the RTCP functionality This section provides a brief example of how the RTCP functionality
is used for achieving IDMS. The section is tutorial in nature and is used for achieving IDMS. The section is tutorial in nature and
does not contain any normative statements. does not contain any normative statements.
Alice's . . . . . . .tv:abc.com . . . . . . . . . Bob's Alice's . . . . . . .tv:abc.com . . . . . . . Bob's
TV (Sync Client) (Sync Server) Laptop (Sync Client) TV (Sync Client) (Sync Server) Laptop (Sync Client)
| | | | | |
| Media Session | | | Media Session | |
|<=====================>| | |<=====================>| |
| Invite(URL,Sync-group ID) | | Invite(URL,Sync-group ID) |
|------------------------------------------------->| |------------------------------------------------->|
| | Media Session Set-up | | | Media Session Set-up |
| |<========================>| | |<========================>|
| | | | | |
| Call set-up | | Call set-up |
|<================================================>| |<================================================>|
| | | | | |
| RTP Packet | RTP Packet | | RTP Packet | RTP Packet |
|<----------------------|------------------------->| |<----------------------|------------------------->|
| RR + XR IDMS Report | | | RR + XR IDMS Report | |
|---------------------->| RR + XR IDMS Report | |---------------------->| RR + XR IDMS Report |
| |<-------------------------| | |<-------------------------|
| RTCP IDMS Settings | RTCP IDMS Settings | | RTCP IDMS Settings | RTCP IDMS Settings |
|<----------------------|------------------------->| |<----------------------|------------------------->|
| | | | | |
Figure 1: Example of a typical IDMS session Figure 1: Example of a typical IDMS session
Alice is watching TV in her living room. At some point she sees that Alice is watching TV in her living room. At some point she sees that
a football game of Bob's favorite team is on. She sends him an a football game of Bob's favorite team is on. She sends him an
invite to watch the program together. Embedded in the invitation is invite to watch the program together. Embedded in the invitation is
the link to the media server and a unique sync-group identifier. the link to the media server and a unique sync-group identifier.
Bob, who is also at home, receives the invite on his laptop. He Bob, who is also at home, receives the invite on his laptop. He
accepts Alice's invitation and the RTP client on his laptop sets up a accepts Alice's invitation and the RTP client on his laptop sets up a
session to the media server. A VoIP connection to Alice's TV is also session to the media server. A VoIP connection to Alice's TV is also
set up, so that Alice and Bob can talk while watching the game set up, so that Alice and Bob can talk while watching the game
skipping to change at page 16, line 18 skipping to change at page 16, line 18
of SyncGroupId to include, see Section 12. of SyncGroupId to include, see Section 12.
The following is an example of the SDP attribute for IDMS. The following is an example of the SDP attribute for IDMS.
a=rtcp-idms:sync-group=42 a=rtcp-idms:sync-group=42
12. SDP rules 12. SDP rules
12.1. Offer/Answer rules 12.1. Offer/Answer rules
The SDP usage for IDMS follows the rules defined in RFC3611 in The SDP usage for IDMS follows the rules defined in [RFC4566] and
section 5 on SDP signalling, with the exception of what is stated section 5 of [RFC3611] on SDP signalling, with the exception of what
here. The IDMS usage of RTCP is a (loosely coupled) collaborative is stated here. The IDMS usage of RTCP is a (loosely coupled)
attribute, in the sense that receivers sent their status information collaborative attribute, in the sense that receivers sent their
and in response the MSAS (asynchronously) sends synchronization status information and in response the MSAS (asynchronously) sends
instructions. The rtcp-idms attribute thus indicates the ability to synchronization instructions. The rtcp-idms attribute thus indicates
send and receive indicated RTCP messages. This section defines how the ability to send and receive indicated RTCP messages. This
this SDP attribute should be used with regards to offer/answer. section defines how this SDP attribute should be used with regards to
offer/answer.
It is expected that in most cases, the rtcp-idms attribute will be It is expected that in most cases, the rtcp-idms attribute will be
used in an offer/answer context where receivers will have pre- used in an offer/answer context where receivers will have pre-
determined, through some means outside the scope of this document, a determined, through some means outside the scope of this document, a
SyncGroupId before the media session is setup. However, it is also SyncGroupId before the media session is setup. However, it is also
supported that the MSAS assigns such a SyncGroupId, for example if supported that the MSAS assigns such a SyncGroupId, for example if
the MSAS contains group management functionality. Thus, both the the MSAS contains group management functionality. Thus, both the
MSAS and the SC can insert the attribute and the SyncGroupId. MSAS and the SC can insert the attribute and the SyncGroupId.
Furthermore, it is allowed to insert the attribute for more than one Furthermore, it is allowed to insert the attribute for more than one
media stream, allowing an SC to become part of multiple media stream, allowing an SC to become part of multiple
skipping to change at page 20, line 11 skipping to change at page 20, line 19
Walraven, Ishan Vaishnavi and Rufael Mekuria. In addition the Walraven, Ishan Vaishnavi and Rufael Mekuria. In addition the
authors would like to thank Aidan Williams, Colin Perkins, Magnus authors would like to thank Aidan Williams, Colin Perkins, Magnus
Westerlund, Roni Even, Peter Musgrave, Ali Begen, Qin Wu and Rob Westerlund, Roni Even, Peter Musgrave, Ali Begen, Qin Wu and Rob
Koenen for their review comments and contributions to the text. Koenen for their review comments and contributions to the text.
16. References 16. References
16.1. Normative References 16.1. Normative References
[I-D.draft-ietf-avtcore-clksrc] [I-D.draft-ietf-avtcore-clksrc]
Williams, A., van Brandenburg, R., Stokking, H., and K. Williams, A., Gross, K., van Brandenburg, R., and H.
Gross, "RTP Clock Source Signalling, Stokking, "RTP Clock Source Signalling,
draft-ietf-avtcore-clksrc-01", October 2012. draft-ietf-avtcore-clksrc-03", October 2012.
[RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate
Requirement Levels, RFC 2119", March 1997. Requirement Levels, RFC 2119", March 1997.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications, RFC3550", July 2003. Applications, RFC3550", July 2003.
[RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and [RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and
Video conferences with Minimal Control, RFC3551", Video conferences with Minimal Control, RFC3551",
skipping to change at page 20, line 36 skipping to change at page 20, line 44
[RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed., [RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed.,
"RTP Control Protocol Extended Reports (RTCP XR), "RTP Control Protocol Extended Reports (RTCP XR),
RFC3611", November 2003. RFC3611", November 2003.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol, RFC4566", July 2006. Description Protocol, RFC4566", July 2006.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications, RFC5234", January 2008. Specifications, RFC5234", January 2008.
[RFC5760] Ott, J., Chesterfield, J., and E. Schooler, "RTP Control
Protocol (RTCP) Extensions for Single-Source Multicast
Sessions with Unicast Feedback, RFC5760", February 2010.
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, [RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms "Network Time Protocol Version 4: Protocol and Algorithms
Specifications, RFC5905", February 2010. Specifications, RFC5905", February 2010.
[TS183063] [TS183063]
"IMS-based IPTV stage 3 specification, TS 183 063 v3.4.1", "IMS-based IPTV stage 3 specification, TS 183 063 v3.4.1",
June 2010. June 2010.
16.2. Informative References 16.2. Informative References
[Boronat2009] [Boronat2009]
Boronat, F., Lloret, J., and M. Garcia, "Multimedia group Boronat, F., Lloret, J., and M. Garcia, "Multimedia group
and inter-stream synchronization techniques: a comparative and inter-stream synchronization techniques: a comparative
study, Elsevier Information Systems 34 (2009), pp. 108- study, Elsevier Information Systems 34 (2009), pp. 108-
131". 131".
[I-D.draft-ietf-leap-seconds] [I-D.draft-ietf-leap-seconds]
Gross, K. and R. Brandenburg, van, "RTP and Leap Seconds, Gross, K. and R. Brandenburg, van, "RTP and Leap Seconds,
draft-ietf-leap-seconds-01", October 2012. draft-ietf-avtcore-leap-second-02", October 2012.
[IEEE-1588] [IEEE-1588]
"1588-2008 - IEEE Standard for a Precision Clock "1588-2008 - IEEE Standard for a Precision Clock
Synchronization Protocol for Networked Measurement and Synchronization Protocol for Networked Measurement and
Control Systems", 2008. Control Systems", 2008.
[Ishibashi2006] [Ishibashi2006]
Ishibashi, Y., Nagasaka, M., and N. Fujiyoshi, "Subjective Ishibashi, Y., Nagasaka, M., and N. Fujiyoshi, "Subjective
Assessment of Fairness among users in multipoint Assessment of Fairness among users in multipoint
communications, Proceedings of the 2006 ACM SIGCHI communications, Proceedings of the 2006 ACM SIGCHI
skipping to change at page 22, line 24 skipping to change at page 22, line 24
TNO TNO
Brassersplein 2 Brassersplein 2
Delft 2612CT Delft 2612CT
the Netherlands the Netherlands
Phone: +31-88-866-7000 Phone: +31-88-866-7000
Email: oskar.vandeventer@tno.nl Email: oskar.vandeventer@tno.nl
Fernando Boronat Fernando Boronat
Universitat Politecnica de Valencia Universitat Politecnica de Valencia
IGIC Institute, Universitat Politecnica de Valencia-Campus de Gandia (UPV), C/ Paraninfo, 1, Grao de Gandia, C/ Paraninfo, 1, Grao de Gandia IGIC Institute, Universitat Politecnica de Valencia-Campus de Gandia
Valencia 46730 Valencia 46730
Spain Spain
Phone: +34 962 849 341 Phone: +34 962 849 341
Email: fboronat@dcom.upv.es Email: fboronat@dcom.upv.es
Mario Montagud Mario Montagud
Universitat Politecnica de Valencia Universitat Politecnica de Valencia
IGIC Institute, Universitat Politecnica de Valencia-Campus de Gandia (UPV), C/ Paraninfo, 1, Grao de Gandia, C/ Paraninfo, 1, Grao de Gandia IGIC Institute, Universitat Politecnica de Valencia-Campus de Gandia
Valencia 46730 Valencia 46730
Spain Spain
Phone: +34 962 849 341 Phone: +34 962 849 341
Email: mamontor@posgrado.upv.es Email: mamontor@posgrado.upv.es
Kevin Gross Kevin Gross
AVA Networks AVA Networks
Phone: +1-303-447-0517 Phone: +1-303-447-0517
 End of changes. 14 change blocks. 
46 lines changed or deleted 43 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/