draft-ietf-avtcore-mprtp-01.txt   draft-ietf-avtcore-mprtp-02.txt 
AVT Core Working Group V. Singh AVT Core Working Group V. Singh
Internet-Draft T. Karkkainen Internet-Draft callstats.io
Intended status: Experimental J. Ott Intended status: Experimental T. Karkkainen
Expires: January 7, 2016 S. Ahsan Expires: September 22, 2016 J. Ott
Technical University of Munich
S. Ahsan
Aalto University Aalto University
L. Eggert L. Eggert
NetApp NetApp
July 6, 2015 March 21, 2016
Multipath RTP (MPRTP) Multipath RTP (MPRTP)
draft-ietf-avtcore-mprtp-01 draft-ietf-avtcore-mprtp-02
Abstract Abstract
The Real-time Transport Protocol (RTP) is used to deliver real-time The Real-time Transport Protocol (RTP) is used to deliver real-time
content and, along with the RTP Control Protocol (RTCP), forms the content and, along with the RTP Control Protocol (RTCP), forms the
control channel between the sender and receiver. However, RTP and control channel between the sender and receiver. However, RTP and
RTCP assume a single delivery path between the sender and receiver RTCP assume a single delivery path between the sender and receiver
and make decisions based on the measured characteristics of this and make decisions based on the measured characteristics of this
single path. Increasingly, endpoints are becoming multi-homed, which single path. Increasingly, endpoints are becoming multi-homed, which
means that they are connected via multiple Internet paths. Network means that they are connected via multiple Internet paths. Network
skipping to change at page 1, line 46 skipping to change at page 1, line 48
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 January 7, 2016. This Internet-Draft will expire on September 22, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
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.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 39 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 40
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.3. Use-cases . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3. Use-cases . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Functional goals . . . . . . . . . . . . . . . . . . . . 5 2.1. Functional goals . . . . . . . . . . . . . . . . . . . . 5
2.2. Compatibility goals . . . . . . . . . . . . . . . . . . . 6 2.2. Compatibility goals . . . . . . . . . . . . . . . . . . . 6
3. RTP Topologies . . . . . . . . . . . . . . . . . . . . . . . 6 3. RTP Topologies . . . . . . . . . . . . . . . . . . . . . . . 6
4. MPRTP Architecture . . . . . . . . . . . . . . . . . . . . . 6 4. MPRTP Architecture . . . . . . . . . . . . . . . . . . . . . 6
5. Example Media Flow Diagrams . . . . . . . . . . . . . . . . . 8 5. Example Media Flow Diagrams . . . . . . . . . . . . . . . . . 8
5.1. Streaming use-case . . . . . . . . . . . . . . . . . . . 8 5.1. Streaming use-case . . . . . . . . . . . . . . . . . . . 8
skipping to change at page 3, line 31 skipping to change at page 3, line 31
11.5.1. In-band Signaling Example . . . . . . . . . . . . . 31 11.5.1. In-band Signaling Example . . . . . . . . . . . . . 31
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
12.1. MPRTP Header Extension . . . . . . . . . . . . . . . . . 32 12.1. MPRTP Header Extension . . . . . . . . . . . . . . . . . 32
12.2. MPRTCP Packet Type . . . . . . . . . . . . . . . . . . . 32 12.2. MPRTCP Packet Type . . . . . . . . . . . . . . . . . . . 32
12.3. SDP Attributes . . . . . . . . . . . . . . . . . . . . . 33 12.3. SDP Attributes . . . . . . . . . . . . . . . . . . . . . 33
12.3.1. "mprtp" attribute . . . . . . . . . . . . . . . . . 33 12.3.1. "mprtp" attribute . . . . . . . . . . . . . . . . . 33
13. Security Considerations . . . . . . . . . . . . . . . . . . . 34 13. Security Considerations . . . . . . . . . . . . . . . . . . . 34
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 34 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 34
15.1. Normative References . . . . . . . . . . . . . . . . . . 35 15.1. Normative References . . . . . . . . . . . . . . . . . . 35
15.2. Informative References . . . . . . . . . . . . . . . . . 35 15.2. Informative References . . . . . . . . . . . . . . . . . 36
Appendix A. Interoperating with Legacy Applications . . . . . . 37 Appendix A. Interoperating with Legacy Applications . . . . . . 37
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 37 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 38
B.1. Changes in draft-ietf-avtcore-mprtp-00 . . . . . . . . . 37 B.1. Changes in draft-ietf-avtcore-mprtp-01, and -02 . . . . . 38
B.2. Changes in draft-singh-avtcore-mprtp-10 . . . . . . . . . 37 B.2. Changes in draft-ietf-avtcore-mprtp-00 . . . . . . . . . 38
B.3. Changes in draft-singh-avtcore-mprtp-09 . . . . . . . . . 38 B.3. Changes in draft-singh-avtcore-mprtp-10 . . . . . . . . . 38
B.4. Changes in draft-singh-avtcore-mprtp-08 . . . . . . . . . 38 B.4. Changes in draft-singh-avtcore-mprtp-09 . . . . . . . . . 38
B.5. Changes in draft-singh-avtcore-mprtp-06 and -07 . . . . . 38 B.5. Changes in draft-singh-avtcore-mprtp-08 . . . . . . . . . 38
B.6. Changes in draft-singh-avtcore-mprtp-05 . . . . . . . . . 38 B.6. Changes in draft-singh-avtcore-mprtp-06 and -07 . . . . . 38
B.7. Changes in draft-singh-avtcore-mprtp-04 . . . . . . . . . 38 B.7. Changes in draft-singh-avtcore-mprtp-05 . . . . . . . . . 38
B.8. Changes in draft-singh-avtcore-mprtp-03 . . . . . . . . . 38 B.8. Changes in draft-singh-avtcore-mprtp-04 . . . . . . . . . 39
B.9. Changes in draft-singh-avtcore-mprtp-02 . . . . . . . . . 39 B.9. Changes in draft-singh-avtcore-mprtp-03 . . . . . . . . . 39
B.10. Changes in draft-singh-avtcore-mprtp-01 . . . . . . . . . 39 B.10. Changes in draft-singh-avtcore-mprtp-02 . . . . . . . . . 39
B.11. Changes in draft-singh-avtcore-mprtp-01 . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
1. Introduction 1. Introduction
Multi-homed endpoints are becoming common in today's Internet, e.g., Multi-homed endpoints are becoming common in today's Internet, e.g.,
devices that support multiple wireless access technologies such as 3G devices that support multiple wireless access technologies such as 3G
and Wireless LAN. This means that there is often more than one and Wireless LAN. This means that there is often more than one
network path available between two endpoints. Transport protocols, network path available between two endpoints. Transport protocols,
such as RTP, have not been designed to take advantage of the such as RTP, have not been designed to take advantage of the
availability of multiple concurrent paths and therefore cannot availability of multiple concurrent paths and therefore cannot
skipping to change at page 35, line 7 skipping to change at page 35, line 7
of the information it contains. of the information it contains.
Thanks to Roni Even , Miguel A. Garcia , Ralf Globisch , Christer Thanks to Roni Even , Miguel A. Garcia , Ralf Globisch , Christer
Holmberg , and Frederic Maze for providing valuable feedback on Holmberg , and Frederic Maze for providing valuable feedback on
earlier versions of this draft. earlier versions of this draft.
15. References 15. References
15.1. Normative References 15.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003. 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
2003, <http://www.rfc-editor.org/info/rfc3629>.
[RFC5760] Ott, J., Chesterfield, J., and E. Schooler, "RTP Control [RFC5760] Ott, J., Chesterfield, J., and E. Schooler, "RTP Control
Protocol (RTCP) Extensions for Single-Source Multicast Protocol (RTCP) Extensions for Single-Source Multicast
Sessions with Unicast Feedback", RFC 5760, February 2010. Sessions with Unicast Feedback", RFC 5760, DOI 10.17487/
RFC5760, February 2010,
<http://www.rfc-editor.org/info/rfc5760>.
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment [RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT) (ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", RFC 5245, April Traversal for Offer/Answer Protocols", RFC 5245, DOI
2010. 10.17487/RFC5245, April 2010,
<http://www.rfc-editor.org/info/rfc5245>.
[RFC5285] Singer, D. and H. Desineni, "A General Mechanism for RTP [RFC5285] Singer, D. and H. Desineni, "A General Mechanism for RTP
Header Extensions", RFC 5285, July 2008. Header Extensions", RFC 5285, DOI 10.17487/RFC5285, July
2008, <http://www.rfc-editor.org/info/rfc5285>.
[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", STD 64, RFC 3550, July 2003. Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550,
July 2003, <http://www.rfc-editor.org/info/rfc3550>.
[RFC5506] Johansson, I. and M. Westerlund, "Support for Reduced-Size [RFC5506] Johansson, I. and M. Westerlund, "Support for Reduced-Size
Real-Time Transport Control Protocol (RTCP): Opportunities Real-Time Transport Control Protocol (RTCP): Opportunities
and Consequences", RFC 5506, April 2009. and Consequences", RFC 5506, DOI 10.17487/RFC5506, April
2009, <http://www.rfc-editor.org/info/rfc5506>.
[RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey,
"Extended RTP Profile for Real-time Transport Control "Extended RTP Profile for Real-time Transport Control
Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, July Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, DOI
2006. 10.17487/RFC4585, July 2006,
<http://www.rfc-editor.org/info/rfc4585>.
[RFC5761] Perkins, C. and M. Westerlund, "Multiplexing RTP Data and [RFC5761] Perkins, C. and M. Westerlund, "Multiplexing RTP Data and
Control Packets on a Single Port", RFC 5761, April 2010. Control Packets on a Single Port", RFC 5761, DOI 10.17487/
RFC5761, April 2010,
<http://www.rfc-editor.org/info/rfc5761>.
15.2. Informative References 15.2. Informative References
[RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC
Text on Security Considerations", BCP 72, RFC 3552, July Text on Security Considerations", BCP 72, RFC 3552, DOI
2003. 10.17487/RFC3552, July 2003,
<http://www.rfc-editor.org/info/rfc3552>.
[RFC6182] Ford, A., Raiciu, C., Handley, M., Barre, S., and J. [RFC6182] Ford, A., Raiciu, C., Handley, M., Barre, S., and J.
Iyengar, "Architectural Guidelines for Multipath TCP Iyengar, "Architectural Guidelines for Multipath TCP
Development", RFC 6182, March 2011. Development", RFC 6182, DOI 10.17487/RFC6182, March 2011,
<http://www.rfc-editor.org/info/rfc6182>.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC [RFC4960] Stewart, R., Ed., "Stream Control Transmission Protocol",
4960, September 2007. RFC 4960, DOI 10.17487/RFC4960, September 2007,
<http://www.rfc-editor.org/info/rfc4960>.
[RFC5533] Nordmark, E. and M. Bagnulo, "Shim6: Level 3 Multihoming [RFC5533] Nordmark, E. and M. Bagnulo, "Shim6: Level 3 Multihoming
Shim Protocol for IPv6", RFC 5533, June 2009. Shim Protocol for IPv6", RFC 5533, DOI 10.17487/RFC5533,
June 2009, <http://www.rfc-editor.org/info/rfc5533>.
[RFC5117] Westerlund, M. and S. Wenger, "RTP Topologies", RFC 5117, [RFC5117] Westerlund, M. and S. Wenger, "RTP Topologies", RFC 5117,
January 2008. DOI 10.17487/RFC5117, January 2008,
<http://www.rfc-editor.org/info/rfc5117>.
[I-D.ietf-mmusic-rfc2326bis] [I-D.ietf-mmusic-rfc2326bis]
Schulzrinne, H., Rao, A., Lanphier, R., Westerlund, M., Schulzrinne, H., Rao, A., Lanphier, R., Westerlund, M.,
and M. Stiemerling, "Real Time Streaming Protocol 2.0 and M. Stiemerling, "Real Time Streaming Protocol 2.0
(RTSP)", draft-ietf-mmusic-rfc2326bis-40 (work in (RTSP)", draft-ietf-mmusic-rfc2326bis-40 (work in
progress), February 2014. progress), February 2014.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. DOI 10.17487/RFC3261, June 2002,
<http://www.rfc-editor.org/info/rfc3261>.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, June with Session Description Protocol (SDP)", RFC 3264, DOI
2002. 10.17487/RFC3264, June 2002,
<http://www.rfc-editor.org/info/rfc3264>.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
July 2006, <http://www.rfc-editor.org/info/rfc4566>.
[RFC6263] Marjou, X. and A. Sollaud, "Application Mechanism for [RFC6263] Marjou, X. and A. Sollaud, "Application Mechanism for
Keeping Alive the NAT Mappings Associated with RTP / RTP Keeping Alive the NAT Mappings Associated with RTP / RTP
Control Protocol (RTCP) Flows", RFC 6263, June 2011. Control Protocol (RTCP) Flows", RFC 6263, DOI 10.17487/
RFC6263, June 2011,
<http://www.rfc-editor.org/info/rfc6263>.
[I-D.singh-mmusic-mprtp-sdp-extension] [I-D.singh-mmusic-mprtp-sdp-extension]
Singh, V., Ott, J., Karkkainen, T., Globisch, R., and T. Singh, V., Ott, J., Karkkainen, T., Globisch, R., and T.
Schierl, "Multipath RTP (MPRTP) attribute in Session Schierl, "Multipath RTP (MPRTP) attribute in Session
Description Protocol", draft-singh-mmusic-mprtp-sdp- Description Protocol", draft-singh-mmusic-mprtp-sdp-
extension-04 (work in progress), September 2014. extension-04 (work in progress), September 2014.
[I-D.reddy-mmusic-ice-best-interface-pcp] [I-D.reddy-mmusic-ice-best-interface-pcp]
Reddy, T., Wing, D., Steeg, B., Penno, R., and V. Varun, Reddy, T., Wing, D., Steeg, B., Penno, R., and V. Varun,
"Improving ICE Interface Selection Using Port Control "Improving ICE Interface Selection Using Port Control
Protocol (PCP) Flow Extension", draft-reddy-mmusic-ice- Protocol (PCP) Flow Extension", draft-reddy-mmusic-ice-
best-interface-pcp-00 (work in progress), October 2013. best-interface-pcp-00 (work in progress), October 2013.
[I-D.wing-mmusic-ice-mobility] [I-D.wing-mmusic-ice-mobility]
Wing, D., Reddy, T., Patil, P., and P. Martinsen, Wing, D., Reddy, T., Patil, P., and P. Martinsen,
"Mobility with ICE (MICE)", draft-wing-mmusic-ice- "Mobility with ICE (MICE)", draft-wing-mmusic-ice-
mobility-07 (work in progress), June 2014. mobility-07 (work in progress), June 2014.
[I-D.ietf-rmcat-eval-criteria] [I-D.ietf-rmcat-eval-criteria]
Singh, V. and J. Ott, "Evaluating Congestion Control for Varun, V., Ott, J., and S. Holmer, "Evaluating Congestion
Interactive Real-time Media", draft-ietf-rmcat-eval- Control for Interactive Real-time Media", draft-ietf-
criteria-02 (work in progress), July 2014. rmcat-eval-criteria-05 (work in progress), March 2016.
[ACM-MPRTP] [ACM-MPRTP]
Singh, V., Ahsan, S., and J. Ott, "MPRTP: multipath Singh, V., Ahsan, S., and J. Ott, "MPRTP: multipath
considerations for real-time media", in Proc. of ACM considerations for real-time media", in Proc. of ACM
Multimedia Systems, MMSys, 2013. Multimedia Systems, MMSys, 2013.
Appendix A. Interoperating with Legacy Applications Appendix A. Interoperating with Legacy Applications
Some legacy endpoints may abort processing incoming packets, if they Some legacy endpoints may abort processing incoming packets, if they
are received from different source address. This may occur due to are received from different source address. This may occur due to
skipping to change at page 37, line 40 skipping to change at page 38, line 15
packets over multiple paths or detect if a path disappeared. packets over multiple paths or detect if a path disappeared.
An MPRTP receiver can only use one of its interface when An MPRTP receiver can only use one of its interface when
communicating with a legacy sender. communicating with a legacy sender.
Appendix B. Change Log Appendix B. Change Log
Note to the RFC-Editor: please remove this section prior to Note to the RFC-Editor: please remove this section prior to
publication as an RFC. publication as an RFC.
B.1. Changes in draft-ietf-avtcore-mprtp-00 B.1. Changes in draft-ietf-avtcore-mprtp-01, and -02
o Keep-alive versions, document needs review.
o Updated authors' affiliations.
B.2. Changes in draft-ietf-avtcore-mprtp-00
o Submitted as a WG item. o Submitted as a WG item.
B.2. Changes in draft-singh-avtcore-mprtp-10 B.3. Changes in draft-singh-avtcore-mprtp-10
o Editorial updates based on review comments. o Editorial updates based on review comments.
o Renamed length to encaps_length. o Renamed length to encaps_length.
B.3. Changes in draft-singh-avtcore-mprtp-09 B.4. Changes in draft-singh-avtcore-mprtp-09
o Editorial updates based on review comments. o Editorial updates based on review comments.
o Clarified use of a=rtcp-rsize. o Clarified use of a=rtcp-rsize.
o Fixed bug in block length of interface advertisements. o Fixed bug in block length of interface advertisements.
B.4. Changes in draft-singh-avtcore-mprtp-08 B.5. Changes in draft-singh-avtcore-mprtp-08
o Added reference to use of PCP for discovering new interfaces. o Added reference to use of PCP for discovering new interfaces.
B.5. Changes in draft-singh-avtcore-mprtp-06 and -07 B.6. Changes in draft-singh-avtcore-mprtp-06 and -07
o Added reference to Mobility ICE. o Added reference to Mobility ICE.
B.6. Changes in draft-singh-avtcore-mprtp-05 B.7. Changes in draft-singh-avtcore-mprtp-05
o SDP extensions moved to draft-singh-mmusic-mprtp-sdp-extension-00. o SDP extensions moved to draft-singh-mmusic-mprtp-sdp-extension-00.
Kept only the basic 'a=mprtp' attribute in this document. Kept only the basic 'a=mprtp' attribute in this document.
o Cleaned up ICE procedures for advertising only using in-band o Cleaned up ICE procedures for advertising only using in-band
signaling. signaling.
B.7. Changes in draft-singh-avtcore-mprtp-04 B.8. Changes in draft-singh-avtcore-mprtp-04
o Fixed missing 0xBEDE header in MPRTP header format. o Fixed missing 0xBEDE header in MPRTP header format.
o Removed connectivity checks and keep-alives from in-band o Removed connectivity checks and keep-alives from in-band
signaling. signaling.
o MPRTP and MPRTCP are multiplexed on a single port. o MPRTP and MPRTCP are multiplexed on a single port.
o MPRTCP packet headers optimized. o MPRTCP packet headers optimized.
o Made ICE optional o Made ICE optional
o Updated Sections: 7.1.2, 8.1.x, 11.2, 11.4, 11.6. o Updated Sections: 7.1.2, 8.1.x, 11.2, 11.4, 11.6.
o Added how to use MPRTP in RTSP (Section 12). o Added how to use MPRTP in RTSP (Section 12).
o Updated IANA Considerations section. o Updated IANA Considerations section.
B.8. Changes in draft-singh-avtcore-mprtp-03 B.9. Changes in draft-singh-avtcore-mprtp-03
o Added this change log. o Added this change log.
o Updated section 6, 7 and 8 based on comments from MMUSIC. o Updated section 6, 7 and 8 based on comments from MMUSIC.
o Updated section 11 (SDP) based on comments of MMUSIC. o Updated section 11 (SDP) based on comments of MMUSIC.
o Updated SDP examples with ICE and non-ICE in out-of-band signaling o Updated SDP examples with ICE and non-ICE in out-of-band signaling
scenario. scenario.
o Added Appendix A on interop with legacy. o Added Appendix A on interop with legacy.
o Updated IANA Considerations section. o Updated IANA Considerations section.
B.9. Changes in draft-singh-avtcore-mprtp-02 B.10. Changes in draft-singh-avtcore-mprtp-02
o MPRTCP protocol extensions use only one PT=210, instead of 210 and o MPRTCP protocol extensions use only one PT=210, instead of 210 and
211. 211.
o RTP header uses 1-byte extension instead of 2-byte. o RTP header uses 1-byte extension instead of 2-byte.
o Added section on RTCP Interval Calculations. o Added section on RTCP Interval Calculations.
o Added "mprtp-interface" attribute in SDP considerations. o Added "mprtp-interface" attribute in SDP considerations.
B.10. Changes in draft-singh-avtcore-mprtp-01 B.11. Changes in draft-singh-avtcore-mprtp-01
o Added MPRTP and MPRTCP protocol extensions and examples. o Added MPRTP and MPRTCP protocol extensions and examples.
o WG changed from -avt to -avtcore. o WG changed from -avt to -avtcore.
Editorial Comments Editorial Comments
[note-iceornot] Editor: Legacy applications do not require ICE for [note-iceornot] Editor: Legacy applications do not require ICE for
session establishment, therefore, MPRTP should not session establishment, therefore, MPRTP should not
require it as well. require it as well.
skipping to change at page 40, line 8 skipping to change at page 40, line 32
before. before.
[note-rtp-rtcp-mux] Editor: If a=mprtp is indicated, does the endpoint [note-rtp-rtcp-mux] Editor: If a=mprtp is indicated, does the endpoint
need to indicate a=rtcp-mux and a=rtcp-rsize? need to indicate a=rtcp-mux and a=rtcp-rsize?
because MPRTP mandates the use of RTP and RTCP because MPRTP mandates the use of RTP and RTCP
multiplexing, and Reduced-Size RTCP. multiplexing, and Reduced-Size RTCP.
Authors' Addresses Authors' Addresses
Varun Singh Varun Singh
Aalto University Nemu Dialogue Systems Oy
School of Electrical Engineering Runeberginkatu 4c A 4
Otakaari 5 A Helsinki 00100
Espoo, FIN 02150
Finland Finland
Email: varun.singh@iki.fi Email: varun.singh@iki.fi
URI: http://www.netlab.tkk.fi/~varun/ URI: http://www.callstats.io/
Teemu Karkkainen Teemu Karkkainen
Aalto University Technical University of Munich
School of Electrical Engineering Faculty of Informatics
Otakaari 5 A Boltzmannstrasse 3
Espoo, FIN 02150 Garching bei Muenchen, DE 85748
Finland Germany
Email: teemuk@comnet.tkk.fi
Email: kaerkkae@in.tum.de
Joerg Ott Joerg Ott
Aalto University Technical University of Munich
School of Electrical Engineering Faculty of Informatics
Otakaari 5 A Boltzmannstrasse 3
Espoo, FIN 02150 Garching bei Muenchen, DE 85748
Finland Germany
Email: jo@comnet.tkk.fi Email: ott@in.tum.de
Saba Ahsan Saba Ahsan
Aalto University Aalto University
School of Electrical Engineering School of Electrical Engineering
Otakaari 5 A Otakaari 5 A
Espoo, FIN 02150 Espoo, FIN 02150
Finland Finland
Email: saba.ahsan@aalto.fi Email: saba.ahsan@aalto.fi
Lars Eggert Lars Eggert
NetApp NetApp
Sonnenallee 1 Sonnenallee 1
Kirchheim 85551 Kirchheim 85551
Germany Germany
Phone: +49 151 12055791 Phone: +49 151 12055791
Email: lars@netapp.com Email: lars@netapp.com
URI: http://eggert.org/ URI: http://eggert.org/
 End of changes. 44 change blocks. 
74 lines changed or deleted 104 lines changed or added

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