Re: [MMUSIC] ISSUE1: SDP Attributes Multiplexing - Payload Type Analysis
Jonathan Lennox <jonathan@vidyo.com> Tue, 01 July 2014 15:07 UTC
Return-Path: <jonathan@vidyo.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32D8C1A0537 for <mmusic@ietfa.amsl.com>; Tue, 1 Jul 2014 08:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.87
X-Spam-Level: *
X-Spam-Status: No, score=1.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_16=0.6, J_CHICKENPOX_18=0.6, J_CHICKENPOX_19=0.6, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s-8XAqVfGsy7 for <mmusic@ietfa.amsl.com>; Tue, 1 Jul 2014 08:07:27 -0700 (PDT)
Received: from server209.appriver.com (server209e.appriver.com [8.31.233.120]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC6C51A0549 for <mmusic@ietf.org>; Tue, 1 Jul 2014 08:07:26 -0700 (PDT)
X-Note-AR-ScanTimeLocal: 7/1/2014 11:07:25 AM
X-Policy: GLOBAL - vidyo.com
X-Policy: GLOBAL - vidyo.com
X-Primary: jonathan@vidyo.com
X-Note: This Email was scanned by AppRiver SecureTide
X-Virus-Scan: V-
X-Note-SnifferID: 0
X-Note: TCH-CT/SI:0-280/SG:5 7/1/2014 11:06:58 AM
X-GBUdb-Analysis: 0, 162.209.16.213, Ugly c=0.867208 p=-0.979628 Source White
X-Signature-Violations: 0-0-0-26704-c
X-Note-419: 15.6003 ms. Fail:0 Chk:1337 of 1337 total
X-Note: SCH-CT/SI:0-1337/SG:1 7/1/2014 11:07:23 AM
X-Note: Spam Tests Failed:
X-Country-Path: ->UNITED STATES->
X-Note-Sending-IP: 162.209.16.213
X-Note-Reverse-DNS: mail2.vidyo.com
X-Note-Return-Path: jonathan@vidyo.com
X-Note: User Rule Hits:
X-Note: Global Rule Hits: G334 G335 G336 G337 G341 G342 G452
X-Note: Encrypt Rule Hits:
X-Note: Mail Class: VALID
X-Note: Headers Injected
Received: from [162.209.16.213] (HELO mail.vidyo.com) by server209.appriver.com (CommuniGate Pro SMTP 6.0.8) with ESMTPS id 109600245; Tue, 01 Jul 2014 11:07:25 -0400
Received: from 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62]) by 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77%13]) with mapi id 14.03.0195.001; Tue, 1 Jul 2014 10:07:24 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Harald Alvestrand <harald@alvestrand.no>
Thread-Topic: [MMUSIC] ISSUE1: SDP Attributes Multiplexing - Payload Type Analysis
Thread-Index: AQHPlTkoTSsSmgi9qkCGBpSoE1Vx4JuLpbSA
Date: Tue, 01 Jul 2014 15:07:24 +0000
Message-ID: <EFB18D89-924E-4DDC-A039-EA891898F6D2@vidyo.com>
References: <CAMRcRGRwxx=Z_pQN33CuU5+=EdB2oBn+xC5hf4J4YYtixE2vgA@mail.gmail.com> <53B14959.2090907@alvestrand.no>
In-Reply-To: <53B14959.2090907@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [160.79.219.114]
Content-Type: multipart/alternative; boundary="_000_EFB18D89924E4DDCA039EA891898F6D2vidyocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/W5a6yuqDPswSJTnv7jCoUmZZPCg
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] ISSUE1: SDP Attributes Multiplexing - Payload Type Analysis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jul 2014 15:07:29 -0000
On Jun 30, 2014, at 7:26 AM, Harald Alvestrand <harald@alvestrand.no<mailto:harald@alvestrand.no>> wrote: I agree with Bo's analysis concluding that IDENTICAL-PER-SSRC is likely not needed, and that situations where one has one SSRC in multiple media descriptions are probably a Bad Thing (I can't think of a case where it would represent anything but a bug). The use case for it, I think, would be a scenario where a single RTP packet stream can satisfy the intended semantics of more than one media description. My usual example is when I am in a conference, viewing both the current loudest speaker and also a specific person (say, my boss, or the customer). I send two separate media descriptions requesting both those items. During those times when that specific person is the loudest speaker, the server can save bandwidth by sending the single RTP packet stream carrying that person’s video only once. It sends the same SSRC in both media descriptions to indicate that that packet stream is intended to be consumed by both of them. Now, maybe we don’t want to support this use case, or maybe we want to support it in some way other than SDP-based signaling (as being too heavyweight for moving SSRCs around on the timescale of loudest-speaker timescale switching). But we should make that decision explicitly. IDENTICAL-PER-PT seems like a sensible thing to add. On 06/23/2014 05:36 AM, Suhas Nandakumar wrote: Hello All Continuing the discussions from London on analyzing multiplexing behavior for SDP attributes that are defined per Payload Type, I was thinking on making following changes to the draft-ietf-mmusic-sdp-mux-attributes-01. 1. Add new category called IDENTICAL-PER-PT to the SDP Attribute analysis framework in Section 4 which is defined as IDENTICAL-PER-PT: Attributes that define the RTP payload configuration on per Payload Type basis and MUST have identical values across all the media descriptions for a given RTP Payload Type when repeated. 2. Similarly add another category IDENTICAL-PER-SSRC to accommodate source level SDP attributes. IDENTICAL-PER-SSRC: Attributes that correspond to the individual RTP Packet Streams in a given RTP Session and MUST have identical values when repeated across multiple media description for a given SSRC. 3. For all the attributes that directly/indirectly impact codec configuration and packetization of the media, I have attempted to assign a SDP MUX category and provide some insights on how such a decision was made (wherever applicable) Attribute: a=ptime, a=maxptime Mux Category: IDENTICAL-PER-PT Notes: For a given codec the audio packetization time must be same if the PT is repeated. This will ensure that the RTP receiver can unambiguously decode the incoming audio packets. Attribute: a=framerate Mux Category: IDENTICAL-PER-PT Attribute: a=rtpmap Mux Category: IDENTICAL-PER-PT Attribute: a=fmtp Mux Category: IDENTICAL-PER-PT Notes: Attribute: a=rtcp-fb Mux Category: NORMAL Notes: Since the feedback messages are reported per SSRC, the category of NORMAL suffices. Attribute: a=depend (RFC5583) Mux Category: IDENTICAL-PER-PT Notes: Since each dependency identifies a unique RTP packetization and thus MUST be identified via unique Payload Type. Similarly if the Payload Type is repeated across media descriptions, they MUST represent the Identical codec configuration. Attribute: a=ssrc:xyz fmtp:<fmt> ... Mux Category: IDENTICAL-PER-PT Notes: RFC5576 says this : " Within a media stream, "ssrc" attributes with the same value of <ssrc-id> describe different attributes of the same media sources. Across media streams, <ssrc-id> values are not correlated (unless correlation is indicated by media-stream grouping or some other mechanism) and MAY be repeated. " Thus if the RTP Payload Type used to specify fmtp parameters is repeated, it MUST represent the same codec configuration. example: m=video ... a=rtpmap:98 VP8/90000 a=ssrc:12345 fmtp:98max-fr=15; max-fs-1200 m=video ... a=rtpmap:98 VP8/90000 a=ssrc:56789 fmtp:98 max-fr=15; max-fs-1200 Attribute: a=ssrc:xyz cname: .... Mux Category: IDENTICAL-PER-SSRC Notes: RFC5576 defines the identical requirement as it is. Attribute: a=imageattr Mux Category: IDENTICAL-PER-PT Attribute: a=framesize Mux Category: IDENTICAL-PER-PT Attributes: a=fec-source-flow, a=fec-repair-flow, a=repair-window Mux Category: NORMAL I believe these cover all PT scoped SDP attributes. Please let me know your thoughts and comments. Cheers Suhas Nandakumar _______________________________________________ mmusic mailing list mmusic@ietf.org<mailto:mmusic@ietf.org> https://www.ietf.org/mailman/listinfo/mmusic _______________________________________________ mmusic mailing list mmusic@ietf.org<mailto:mmusic@ietf.org> https://www.ietf.org/mailman/listinfo/mmusic
- [MMUSIC] ISSUE1: SDP Attributes Multiplexing - Pa… Suhas Nandakumar
- Re: [MMUSIC] ISSUE1: SDP Attributes Multiplexing … Bo Burman
- Re: [MMUSIC] ISSUE1: SDP Attributes Multiplexing … Suhas Nandakumar
- Re: [MMUSIC] ISSUE1: SDP Attributes Multiplexing … Harald Alvestrand
- Re: [MMUSIC] ISSUE1: SDP Attributes Multiplexing … Jonathan Lennox
- Re: [MMUSIC] ISSUE1: SDP Attributes Multiplexing … Jonathan Lennox
- Re: [MMUSIC] ISSUE1: SDP Attributes Multiplexing … Harald Alvestrand