draft-ietf-mmusic-rid-11.txt   draft-ietf-mmusic-rid-12.txt 
Network Working Group P. Thatcher Network Working Group A. Roach (Editor)
Internet-Draft Google Internet-Draft Mozilla
Updates: 4855 (if approved) M. Zanaty Updates: 4855 (if approved) November 13, 2017
Intended status: Standards Track S. Nandakumar Intended status: Standards Track
Expires: January 20, 2018 Cisco Systems Expires: May 17, 2018
B. Burman
Ericsson
A. Roach
B. Campen
Mozilla
July 19, 2017
RTP Payload Format Restrictions RTP Payload Format Restrictions
draft-ietf-mmusic-rid-11 draft-ietf-mmusic-rid-12
Abstract Abstract
In this specification, we define a framework for specifying In this specification, we define a framework for specifying
restrictions on RTP streams in the Session Description Protocol. restrictions on RTP streams in the Session Description Protocol.
This framework defines a new "rid" SDP attribute to unambiguously This framework defines a new "rid" SDP attribute to unambiguously
identify the RTP Streams within a RTP Session and restrict the identify the RTP Streams within a RTP Session and restrict the
streams' payload format parameters in a codec-agnostic way beyond streams' payload format parameters in a codec-agnostic way beyond
what is provided with the regular Payload Types. what is provided with the regular Payload Types.
skipping to change at page 1, line 46 skipping to change at page 1, line 40
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 20, 2018. This Internet-Draft will expire on May 17, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 2, line 39 skipping to change at page 2, line 30
6.2. Answerer processing the SDP Offer . . . . . . . . . . . . 9 6.2. Answerer processing the SDP Offer . . . . . . . . . . . . 9
6.2.1. "a=rid"-unaware Answerer . . . . . . . . . . . . . . 9 6.2.1. "a=rid"-unaware Answerer . . . . . . . . . . . . . . 9
6.2.2. "a=rid"-aware Answerer . . . . . . . . . . . . . . . 9 6.2.2. "a=rid"-aware Answerer . . . . . . . . . . . . . . . 9
6.3. Generating the SDP Answer . . . . . . . . . . . . . . . . 10 6.3. Generating the SDP Answer . . . . . . . . . . . . . . . . 10
6.4. Offerer Processing of the SDP Answer . . . . . . . . . . 11 6.4. Offerer Processing of the SDP Answer . . . . . . . . . . 11
6.5. Modifying the Session . . . . . . . . . . . . . . . . . . 12 6.5. Modifying the Session . . . . . . . . . . . . . . . . . . 12
7. Use with Declarative SDP . . . . . . . . . . . . . . . . . . 12 7. Use with Declarative SDP . . . . . . . . . . . . . . . . . . 12
8. Interaction with Other Techniques . . . . . . . . . . . . . . 12 8. Interaction with Other Techniques . . . . . . . . . . . . . . 12
8.1. Interaction with VP8 Format Parameters . . . . . . . . . 13 8.1. Interaction with VP8 Format Parameters . . . . . . . . . 13
8.1.1. max-fr - Maximum Framerate . . . . . . . . . . . . . 13 8.1.1. max-fr - Maximum Framerate . . . . . . . . . . . . . 13
8.1.2. max-fs - Maximum Framesize, in VP8 Macroblocks . . . 14 8.1.2. max-fs - Maximum Framesize, in VP8 Macroblocks . . . 13
8.2. Interaction with H.264 Format Parameters . . . . . . . . 14 8.2. Interaction with H.264 Format Parameters . . . . . . . . 14
8.2.1. profile-level-id and max-recv-level - Negotiated Sub- 8.2.1. profile-level-id and max-recv-level - Negotiated Sub-
Profile . . . . . . . . . . . . . . . . . . . . . . . 15 Profile . . . . . . . . . . . . . . . . . . . . . . . 15
8.2.2. max-br / MaxBR - Maximum Video Bitrate . . . . . . . 15 8.2.2. max-br / MaxBR - Maximum Video Bitrate . . . . . . . 15
8.2.3. max-fs / MaxFS - Maximum Framesize, in H.264 8.2.3. max-fs / MaxFS - Maximum Framesize, in H.264
Macroblocks . . . . . . . . . . . . . . . . . . . . . 16 Macroblocks . . . . . . . . . . . . . . . . . . . . . 16
8.2.4. max-mbps / MaxMBPS - Maximum Macroblock Processing 8.2.4. max-mbps / MaxMBPS - Maximum Macroblock Processing
Rate . . . . . . . . . . . . . . . . . . . . . . . . 16 Rate . . . . . . . . . . . . . . . . . . . . . . . . 16
8.2.5. max-smbps - Maximum Decoded Picture Buffer . . . . . 16 8.2.5. max-smbps - Maximum Decoded Picture Buffer . . . . . 16
9. Format Parameters for Future Payloads . . . . . . . . . . . . 16 9. Format Parameters for Future Payloads . . . . . . . . . . . . 16
10. Formal Grammar . . . . . . . . . . . . . . . . . . . . . . . 17 10. Formal Grammar . . . . . . . . . . . . . . . . . . . . . . . 17
11. SDP Examples . . . . . . . . . . . . . . . . . . . . . . . . 18 11. SDP Examples . . . . . . . . . . . . . . . . . . . . . . . . 18
11.1. Many Bundled Streams using Many Codecs . . . . . . . . . 18 11.1. Many Bundled Streams using Many Codecs . . . . . . . . . 18
11.2. Scalable Layers . . . . . . . . . . . . . . . . . . . . 20 11.2. Scalable Layers . . . . . . . . . . . . . . . . . . . . 20
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
12.1. New SDP Media-Level attribute . . . . . . . . . . . . . 21 12.1. New SDP Media-Level attribute . . . . . . . . . . . . . 21
12.2. Registry for RID-Level Parameters . . . . . . . . . . . 22 12.2. Registry for RID-Level Parameters . . . . . . . . . . . 22
13. Security Considerations . . . . . . . . . . . . . . . . . . . 24 13. Security Considerations . . . . . . . . . . . . . . . . . . . 23
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 24 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
15.1. Normative References . . . . . . . . . . . . . . . . . . 24 15.1. Normative References . . . . . . . . . . . . . . . . . . 24
15.2. Informative References . . . . . . . . . . . . . . . . . 25 15.2. Informative References . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 26
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 26
1. Terminology 1. Terminology
The terms "Source RTP Stream", "Endpoint", "RTP Session", and "RTP The terms "Source RTP Stream", "Endpoint", "RTP Session", and "RTP
Stream" are used as defined in [RFC7656]. Stream" are used as defined in [RFC7656].
[RFC4566] and [RFC3264] terminology is also used where appropriate. [RFC4566] and [RFC3264] terminology is also used where appropriate.
2. Introduction 2. Introduction
skipping to change at page 24, line 28 skipping to change at page 24, line 4
such, they are not expected to contain information that would be such, they are not expected to contain information that would be
sensitive, were it observed by third-parties. sensitive, were it observed by third-parties.
14. Acknowledgements 14. Acknowledgements
Many thanks to review from Cullen Jennings, Magnus Westerlund, and Many thanks to review from Cullen Jennings, Magnus Westerlund, and
Paul Kyzivat. Thanks to Colin Perkins for input on future payload Paul Kyzivat. Thanks to Colin Perkins for input on future payload
type handing. type handing.
15. References 15. References
15.1. Normative References 15.1. Normative References
[I-D.ietf-avtext-rid] [I-D.ietf-avtext-rid]
Roach, A., Nandakumar, S., and P. Thatcher, "RTP Stream Roach, A., Nandakumar, S., and P. Thatcher, "RTP Stream
Identifier Source Description (SDES)", draft-ietf-avtext- Identifier Source Description (SDES)", draft-ietf-avtext-
rid-09 (work in progress), October 2016. rid-09 (work in progress), October 2016.
[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, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, RFC2119, March 1997, <https://www.rfc-editor.org/info/
<http://www.rfc-editor.org/info/rfc2119>. rfc2119>.
[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, DOI with Session Description Protocol (SDP)", RFC 3264, DOI
10.17487/RFC3264, June 2002, 10.17487/RFC3264, June 2002, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc3264>. editor.org/info/rfc3264>.
[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, DOI 10.17487/RFC3550, Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550,
July 2003, <http://www.rfc-editor.org/info/rfc3550>. July 2003, <https://www.rfc-editor.org/info/rfc3550>.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, DOI 10.17487/RFC4566, Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
July 2006, <http://www.rfc-editor.org/info/rfc4566>. July 2006, <https://www.rfc-editor.org/info/rfc4566>.
[RFC4855] Casner, S., "Media Type Registration of RTP Payload [RFC4855] Casner, S., "Media Type Registration of RTP Payload
Formats", RFC 4855, DOI 10.17487/RFC4855, February 2007, Formats", RFC 4855, DOI 10.17487/RFC4855, February 2007,
<http://www.rfc-editor.org/info/rfc4855>. <https://www.rfc-editor.org/info/rfc4855>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/ Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/
RFC5234, January 2008, RFC5234, January 2008, <https://www.rfc-editor.org/info/
<http://www.rfc-editor.org/info/rfc5234>. rfc5234>.
15.2. Informative References 15.2. Informative References
[H264] ITU-T Recommendation H.264, "Advanced video coding for [H264] ITU-T Recommendation H.264, "Advanced video coding for
generic audiovisual services (V9)", February 2014, generic audiovisual services (V9)", February 2014,
<http://www.itu.int/rec/T-REC-H.264-201304-I>. <http://www.itu.int/rec/T-REC-H.264-201304-I>.
[I-D.ietf-mmusic-sdp-bundle-negotiation] [I-D.ietf-mmusic-sdp-bundle-negotiation]
Holmberg, C., Alvestrand, H., and C. Jennings, Holmberg, C., Alvestrand, H., and C. Jennings,
"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-38 (work in progress), April 2017. negotiation-39 (work in progress), August 2017.
[I-D.ietf-mmusic-sdp-simulcast] [I-D.ietf-mmusic-sdp-simulcast]
Burman, B., Westerlund, M., Nandakumar, S., and M. Zanaty, Burman, B., Westerlund, M., Nandakumar, S., and M. Zanaty,
"Using Simulcast in SDP and RTP Sessions", draft-ietf- "Using Simulcast in SDP and RTP Sessions", draft-ietf-
mmusic-sdp-simulcast-09 (work in progress), July 2017. mmusic-sdp-simulcast-10 (work in progress), July 2017.
[I-D.ietf-payload-flexible-fec-scheme] [I-D.ietf-payload-flexible-fec-scheme]
Singh, V., Begen, A., Zanaty, M., and G. Mandyam, "RTP Singh, V., Begen, A., Zanaty, M., and G. Mandyam, "RTP
Payload Format for Flexible Forward Error Correction Payload Format for Flexible Forward Error Correction
(FEC)", draft-ietf-payload-flexible-fec-scheme-05 (work in (FEC)", draft-ietf-payload-flexible-fec-scheme-05 (work in
progress), July 2017. progress), July 2017.
[RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R. [RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R.
Hakenberg, "RTP Retransmission Payload Format", RFC 4588, Hakenberg, "RTP Retransmission Payload Format", RFC 4588,
DOI 10.17487/RFC4588, July 2006, DOI 10.17487/RFC4588, July 2006, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4588>. editor.org/info/rfc4588>.
[RFC5109] Li, A., Ed., "RTP Payload Format for Generic Forward Error [RFC5109] Li, A., Ed., "RTP Payload Format for Generic Forward Error
Correction", RFC 5109, DOI 10.17487/RFC5109, December Correction", RFC 5109, DOI 10.17487/RFC5109, December
2007, <http://www.rfc-editor.org/info/rfc5109>. 2007, <https://www.rfc-editor.org/info/rfc5109>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 5226, DOI IANA Considerations Section in RFCs", RFC 5226, DOI
10.17487/RFC5226, May 2008, 10.17487/RFC5226, May 2008, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5226>. editor.org/info/rfc5226>.
[RFC6184] Wang, Y., Even, R., Kristensen, T., and R. Jesup, "RTP [RFC6184] Wang, Y., Even, R., Kristensen, T., and R. Jesup, "RTP
Payload Format for H.264 Video", RFC 6184, DOI 10.17487/ Payload Format for H.264 Video", RFC 6184, DOI 10.17487/
RFC6184, May 2011, RFC6184, May 2011, <https://www.rfc-editor.org/info/
<http://www.rfc-editor.org/info/rfc6184>. rfc6184>.
[RFC6236] Johansson, I. and K. Jung, "Negotiation of Generic Image [RFC6236] Johansson, I. and K. Jung, "Negotiation of Generic Image
Attributes in the Session Description Protocol (SDP)", RFC Attributes in the Session Description Protocol (SDP)", RFC
6236, DOI 10.17487/RFC6236, May 2011, 6236, DOI 10.17487/RFC6236, May 2011, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6236>. editor.org/info/rfc6236>.
[RFC7656] Lennox, J., Gross, K., Nandakumar, S., Salgueiro, G., and [RFC7656] Lennox, J., Gross, K., Nandakumar, S., Salgueiro, G., and
B. Burman, Ed., "A Taxonomy of Semantics and Mechanisms B. Burman, Ed., "A Taxonomy of Semantics and Mechanisms
for Real-Time Transport Protocol (RTP) Sources", RFC 7656, for Real-Time Transport Protocol (RTP) Sources", RFC 7656,
DOI 10.17487/RFC7656, November 2015, DOI 10.17487/RFC7656, November 2015, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7656>. editor.org/info/rfc7656>.
[RFC7741] Westin, P., Lundin, H., Glover, M., Uberti, J., and F. [RFC7741] Westin, P., Lundin, H., Glover, M., Uberti, J., and F.
Galligan, "RTP Payload Format for VP8 Video", RFC 7741, Galligan, "RTP Payload Format for VP8 Video", RFC 7741,
DOI 10.17487/RFC7741, March 2016, DOI 10.17487/RFC7741, March 2016, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7741>. editor.org/info/rfc7741>.
Authors' Addresses Appendix A. Contributors
The following individuals have contributed significant text to this
document.
Peter Thatcher Peter Thatcher
Google Google
Email: pthatcher@google.com Email: pthatcher@google.com
Mo Zanaty Mo Zanaty
Cisco Systems Cisco Systems
Email: mzanaty@cisco.com Email: mzanaty@cisco.com
Suhas Nandakumar Suhas Nandakumar
Cisco Systems Cisco Systems
Email: snandaku@cisco.com Email: snandaku@cisco.com
Bo Burman Bo Burman
Ericsson Ericsson
Email: bo.burman@ericsson.com Email: bo.burman@ericsson.com
Adam Roach Byron Campen
Mozilla Mozilla
Email: bcampen@mozilla.com
Email: adam@nostrum.com Author's Address
Byron Campen Adam Roach
Mozilla Mozilla
Email: bcampen@mozilla.com Email: adam@nostrum.com
 End of changes. 34 change blocks. 
53 lines changed or deleted 48 lines changed or added

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