Re: [rtcweb] [MMUSIC] FW: New Version Notification for draft-holmberg-mmusic-sdp-multiplex-negotiation-00.txt

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 16 September 2011 12:54 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82CC221F8B9B; Fri, 16 Sep 2011 05:54:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.533
X-Spam-Level:
X-Spam-Status: No, score=-6.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xbnryFxfhwc6; Fri, 16 Sep 2011 05:54:18 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 373EF21F8AF1; Fri, 16 Sep 2011 05:54:18 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c47ae000000b17-bd-4e73478078bf
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id B3.5A.02839.087437E4; Fri, 16 Sep 2011 14:56:32 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.250]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Fri, 16 Sep 2011 14:56:31 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roni Even <ron.even.tlv@gmail.com>, "'Muthu Arul Mozhi Perumal (mperumal)'" <mperumal@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, 'IETF - MMUSIC' <mmusic@ietf.org>
Date: Fri, 16 Sep 2011 14:56:29 +0200
Thread-Topic: [MMUSIC] [rtcweb] FW: New Version Notification for draft-holmberg-mmusic-sdp-multiplex-negotiation-00.txt
Thread-Index: Acxyyd6aOvfK+MMFTn6XQAfby+UjdAAASajQAGLLwtAAA5ebUAAClWrgAABEa6A=
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852233F1E831@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A05852233EDB29F@ESESSCMS0356.eemea.ericsson.se> <1D062974A4845E4D8A343C6538049202066492D5@XMB-BGL-414.cisco.com> <7F2072F1E0DE894DA4B517B93C6A05852233F1E768@ESESSCMS0356.eemea.ericsson.se> <4e73470f.e113440a.6fe3.ffffa2bb@mx.google.com>
In-Reply-To: <4e73470f.e113440a.6fe3.ffffa2bb@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [rtcweb] [MMUSIC] FW: New Version Notification for draft-holmberg-mmusic-sdp-multiplex-negotiation-00.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Sep 2011 12:54:19 -0000

Hi, 

>I think that you MUST have unique payload type numbers in all m-lines.
>As for parameters I am not sure what will be the outcome of 
>the bandwidth if they appear in both m-lines. Or for 
>encryption parameters if you offer SAVP/SAVPF.
> 
>BTW: This solution is not limited to RTCWEB, at least it does 
>not say it is.

That is why I submitted it to MMUSIC :)

Regards,

Christer



> > -----Original Message-----
> > From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On 
> > Behalf Of Christer Holmberg
> > Sent: Friday, September 16, 2011 2:36 PM
> > To: Muthu Arul Mozhi Perumal (mperumal); rtcweb@ietf.org; IETF - 
> > MMUSIC
> > Subject: Re: [MMUSIC] [rtcweb] FW: New Version Notification 
> for draft- 
> > holmberg-mmusic-sdp-multiplex-negotiation-00.txt
> > 
> > 
> > Hi Muthu,
> > 
> > You suggestion looks good, and I'll implement it in the 
> next version 
> > of the draft.
> > 
> > Thanks!
> > 
> > Regards,
> > 
> > Christer
> > 
> > 
> > > -----Original Message-----
> > > From: Muthu Arul Mozhi Perumal (mperumal) 
> > > [mailto:mperumal@cisco.com]
> > > Sent: 16. syyskuuta 2011 14:26
> > > To: Christer Holmberg; rtcweb@ietf.org; IETF - MMUSIC
> > > Subject: RE: [rtcweb] FW: New Version Notification for 
> > > draft-holmberg-mmusic-sdp-multiplex-negotiation-00.txt
> > >
> > > The approach looks good overall. A quick comment on 
> section 5. SDP 
> > > Offer/Answer Procedures:
> > >
> > > |When an SDP offerer wants to offer multiplexed media, it inserts 
> > > |the same port number value for each "m=" line that is part of
> > > the offered
> > > |multiplex.  In addition, the SDP offerer inserts an SDP
> > > session-level
> > > |"a=group" attribute, with a "MULTIPLEX" value, and 
> assigns an SDP 
> > > |media-level "a=mid" attribute value for each "m=" line that
> > > is part of
> > > |the offered multiplex.
> > >
> > > Suggestion:
> > >
> > > An entity generating an SDP offer or answer describing 
> multiplexed 
> > > media does the following:
> > > 1. Inserts the same port number for each "m=" line that is part of
> > >    the multiplex.
> > > 2. Uses the same connection data ("c=" line) values for each media
> > >    stream that is part of the multiplex.
> > > 3. Inserts the same RTCP port number in the "a=rtcp" attribute for
> > >    each media stream that is part of the multiplex, when the RTCP
> > >    port is not the next higher (odd) port number following the RTP
> > >    port described in the "m=" line.
> > > 4. Inserts an "a=rtcp-mux" attribute for each media stream that is
> > >    part of the multiplex, when RTCP is multiplexed with RTP on the
> > >    same port.
> > > 5. Inserts an SDP session-level "a=group" attribute, with a 
> > > "MULTIPLEX"
> > >    value, and assigns an SDP media-level "a=mid" 
> attribute value for
> > >    each "m=" line that is part of the multiplex.
> > >
> > > Muthu
> > >
> > > |-----Original Message-----
> > > |From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> > > Behalf Of Christer Holmberg
> > > |Sent: Wednesday, September 14, 2011 4:17 PM
> > > |To: rtcweb@ietf.org
> > > |Subject: [rtcweb] FW: New Version Notification for
> > > draft-holmberg-mmusic-sdp-multiplex-negotiation-
> > > |00.txt
> > > |
> > > |
> > > |
> > > |Hi,
> > > |
> > > |I've submitted a draft in MMUSIC, which defines a mechanism and
> > > grouping framework extension in order
> > > |to negotiate multiplexing of media associated with multiple m=
> > lines.
> > > |
> > > |The main difference from Harald's previous proposal is that
> > > it defines
> > > the usage of the same port
> > > |number value for multiple m= lines, and every m= line is used to
> > > describe media even in the case of
> > > |multiplex.
> > > |
> > > |Comments are welcome :)
> > > |
> > > |Regards,
> > > |
> > > |Christer
> > > |
> > > |
> > > |
> > > |
> > > |> -----Original Message-----
> > > |> From: internet-drafts@ietf.org 
> [mailto:internet-drafts@ietf.org]
> > > |> Sent: 14. syyskuuta 2011 13:32
> > > |> To: Christer Holmberg
> > > |> Cc: Christer Holmberg
> > > |> Subject: New Version Notification for 
> > > |> draft-holmberg-mmusic-sdp-multiplex-negotiation-00.txt
> > > |>
> > > |> A new version of I-D,
> > > |> draft-holmberg-mmusic-sdp-multiplex-negotiation-00.txt 
> has been 
> > > |> successfully submitted by Christer Holmberg and posted to the 
> > > |> IETF repository.
> > > |>
> > > |> Filename:	 draft-holmberg-mmusic-sdp-multiplex-negotiation
> > > |> Revision:	 00
> > > |> Title:		 Multiplexing Negotiation Using Session
> > > |> Description Protocol (SDP) Port Numbers
> > > |> Creation date:	 2011-09-14
> > > |> WG ID:		 Individual Submission
> > > |> Number of pages: 9
> > > |>
> > > |> Abstract:
> > > |>    This document defines how to use the Session
> > > Description Protocol
> > > |>    (SDP) in order to negotiate the usage of multiplexed media.
> > > |>
> > > |>
> > > |>
> > > |>
> > > |>
> > > |> The IETF Secretariat
> > > |>
> > > |_______________________________________________
> > > |rtcweb mailing list
> > > |rtcweb@ietf.org
> > > |https://www.ietf.org/mailman/listinfo/rtcweb
> > >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www.ietf.org/mailman/listinfo/mmusic
> 
>