draft-ietf-mmusic-rfc8843bis-00.txt   draft-ietf-mmusic-rfc8843bis-01.txt 
MMUSIC Working Group C. Holmberg MMUSIC Working Group C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Obsoletes: 8843 (if approved) H. Alvestrand Obsoletes: 8843 (if approved) H. Alvestrand
Updates: 3264, 5888, 7941 (if approved) Google Updates: 3264, 5888, 7941 (if approved) Google
Intended status: Standards Track C. Jennings Intended status: Standards Track C. Jennings
Expires: 7 November 2021 Cisco Expires: 6 December 2021 Cisco
6 May 2021 4 June 2021
Negotiating Media Multiplexing Using the Session Description Protocol Negotiating Media Multiplexing Using the Session Description Protocol
(SDP) (SDP)
draft-ietf-mmusic-rfc8843bis-00 draft-ietf-mmusic-rfc8843bis-01
Abstract Abstract
This specification defines a new Session Description Protocol (SDP) This specification defines a new Session Description Protocol (SDP)
Grouping Framework extension called 'BUNDLE'. The extension can be Grouping Framework extension called 'BUNDLE'. The extension can be
used with the SDP offer/answer mechanism to negotiate the usage of a used with the SDP offer/answer mechanism to negotiate the usage of a
single transport (5-tuple) for sending and receiving media described single transport (5-tuple) for sending and receiving media described
by multiple SDP media descriptions ("m=" sections). Such transport by multiple SDP media descriptions ("m=" sections). Such transport
is referred to as a BUNDLE transport, and the media is referred to as is referred to as a BUNDLE transport, and the media is referred to as
bundled media. The "m=" sections that use the BUNDLE transport form bundled media. The "m=" sections that use the BUNDLE transport form
skipping to change at page 1, line 48 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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 7 November 2021. This Internet-Draft will expire on 6 December 2021.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 27, line 16 skipping to change at page 27, line 16
stream corresponding to its SSRC. That RTP stream MUST then be stream corresponding to its SSRC. That RTP stream MUST then be
associated with the correct "m=" section within a BUNDLE group, for associated with the correct "m=" section within a BUNDLE group, for
additional processing, according to the following steps: additional processing, according to the following steps:
* If the MID associated with the RTP stream is not in the table * If the MID associated with the RTP stream is not in the table
mapping a MID to an "m=" section, then the RTP stream is not mapping a MID to an "m=" section, then the RTP stream is not
decoded and the payload data is discarded. decoded and the payload data is discarded.
* If the packet has a MID, and the packet's extended sequence number * If the packet has a MID, and the packet's extended sequence number
is greater than that of the last MID update, as discussed in is greater than that of the last MID update, as discussed in
[RFC7941], Section 4.2.2, update the MID associated with the RTP [RFC7941], Section 4.2.6, update the MID associated with the RTP
stream to match the MID carried in the RTP packet, and then update stream to match the MID carried in the RTP packet, and then update
the mapping tables to include an entry that maps the SSRC of that the mapping tables to include an entry that maps the SSRC of that
RTP stream to the "m=" section for that MID. RTP stream to the "m=" section for that MID.
* If the SSRC of the RTP stream is in the incoming SSRC mapping * If the SSRC of the RTP stream is in the incoming SSRC mapping
table, check that the payload type used by the RTP stream matches table, check that the payload type used by the RTP stream matches
a payload type included on the matching "m=" section. If so, a payload type included on the matching "m=" section. If so,
associate the RTP stream with that "m=" section. Otherwise, the associate the RTP stream with that "m=" section. Otherwise, the
RTP stream is not decoded and the payload data is discarded. RTP stream is not decoded and the payload data is discarded.
 End of changes. 4 change blocks. 
5 lines changed or deleted 5 lines changed or added

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