IETF Logo Mail Archive

Re: [MMUSIC] New Version Notification for draft-even-mmusic-application-token-03.txt

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 02 June 2014 12:31 UTC

Return-Path: <christer.holmberg@ericsson.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 D01111A0313 for <mmusic@ietfa.amsl.com>; Mon, 2 Jun 2014 05:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level:
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FRT_BELOW2=2.154, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 CaNENWFuED6R for <mmusic@ietfa.amsl.com>; Mon, 2 Jun 2014 05:31:09 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 879E61A01EB for <mmusic@ietf.org>; Mon, 2 Jun 2014 05:31:08 -0700 (PDT)
X-AuditID: c1b4fb25-f79226d000004024-09-538c6e85ae16
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 43.5D.16420.58E6C835; Mon, 2 Jun 2014 14:31:01 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.28]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0174.001; Mon, 2 Jun 2014 14:31:00 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roni Even <ron.even.tlv@gmail.com>, 'Bernard Aboba' <bernard_aboba@hotmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] New Version Notification for draft-even-mmusic-application-token-03.txt
Thread-Index: AQHPVaN5WvGalTaPX0i13vmV4oIK3ZsMn3HrgAgEirCAABDMgIAAwXYAgAAylrCAACznAIBIO6jw
Date: Mon, 02 Jun 2014 12:31:00 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D34C62B@ESESSMB209.ericsson.se>
References: <20140411163112.6591.91881.idtracker@ietfa.amsl.com>, <760B7D45D1EFF74988DBF5C2122830C23E55A79C@szxpml507-mbx.exmail.huawei.com>, <7594FB04B1934943A5C02806D1A2204B1D2CC7BB@ESESSMB209.ericsson.se> <BLU181-W1855E4D4B8C81836A1DC6493530@phx.gbl> <011201cf5a21$8767a150$9636e3f0$@gmail.com> <7594FB04B1934943A5C02806D1A2204B1D2CD51D@ESESSMB209.ericsson.se> <014301cf5a51$45d2afc0$d1780f40$@gmail.com>
In-Reply-To: <014301cf5a51$45d2afc0$d1780f40$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D34C62BESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOIsWRmVeSWpSXmKPExsUyM+JvjW5rXk+wwZaHhhb7l1xmtti/+Dyz xdTlj1ks/rYzO7B47Jx1l93jcc8ZNo8lS34yebQ9u8MewBLFZZOSmpNZllqkb5fAlbHqQANb wdyCinVT37E1MJ5O6WLk4JAQMJG4fEKxi5ETyBSTuHBvPVsXIxeHkMBRRom7B5ewgCSEBBYx Smx5bAdSzyZgIdH9TxskLCJQJbH2QQ8biM0soCXxf+4VdhBbWCBeYtnNSYwQNQkSF5fPYYew oyTenF4NFmcRUJG42rOfCcTmFfCVOHDpKyvE3sXMEjMaVoAVcQLtOtT1DqyZEei476fWMEEs E5e49WQ+E8TRAhJL9pxnhrBFJV4+/scKYStK7DzbzgxRny8xddY9RohlghInZz5hmcAoOgvJ qFlIymYhKYOI60gs2P2JDcLWlli28DUzjH3mwGMmZPEFjOyrGEWLU4uTctONjPVSizKTi4vz 8/TyUks2MQJj8uCW36o7GC+/cTzEKMDBqMTDq+DdEyzEmlhWXJl7iFGag0VJnPeiRnWwkEB6 YklqdmpqQWpRfFFpTmrxIUYmDk6pBsYirc9lLwzN9SeWOH4VM2Tyk5iR0Kbj/0V3bu8c/4Xp 33psrB/dLQ7Q3DQts1hi35HkE2suFG+8e/NVzczS+PYtiew9c7vTVlxtcTn0Nvb4D+HzT8Rj TlnkVUv8MT9hcnZizGSem6vexXS885oaOlVa8SZ36L4FdTG2T5wYI3pufs1a2Z+d0qXEUpyR aKjFXFScCACfqqvnqgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/4_kA25XNI_XADE0pSHroAAZY45o
Cc: 'Jonathan Lennox' <jonathan@vidyo.com>
Subject: Re: [MMUSIC] New Version Notification for draft-even-mmusic-application-token-03.txt
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: Mon, 02 Jun 2014 12:31:12 -0000

Hi Roni,

What is the way forward regarding the draft?

Especially regarding the parts that BUNDLE need, i.e. the offerer being able to map received RTP packets from the answerer, we need to get done.

Regards,

Christer

From: Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: 17. huhtikuuta 2014 18:26
To: Christer Holmberg; 'Bernard Aboba'; mmusic@ietf.org
Cc: 'Jonathan Lennox'
Subject: RE: [MMUSIC] New Version Notification for draft-even-mmusic-application-token-03.txt

Hi,
Inline
Roni

From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Sent: 17 April, 2014 1:50 PM
To: Roni Even; 'Bernard Aboba'; mmusic@ietf.org<mailto:mmusic@ietf.org>
Cc: 'Jonathan Lennox'
Subject: RE: [MMUSIC] New Version Notification for draft-even-mmusic-application-token-03.txt

Hi,

>By no semantics we meant that it is just a token with no parameters that maps the RTP stream >(packet stream) to a description in the SDP m-line.

Well, then that IS the semantics :)

> (we agreed to take out the SSRC like functionality and have it at the end of the document as issues > that we may want to address for simulcast for example)
> It addressed the cases described by Christer where the RTP arrives before the SDP answer but also > on the send direction for cases where the offerer does not know the SSRC that will be used (see for > example of the three camera case bellow)

Is there a reason why you don't call the 'appId' attribute 'send-appId' instead?
[Roni Even] No reason and we may have a different name for appId, was discussed on the list. We assume appId is sent-appId

Also, assuming the previous answerer in a subsequent O/A exchange becomes the offerer, which attribute (if any) does it include in the Offer? You need to describe how a change of the Offerer/Answerer roles affect affects the usage.

[Roni Even] The current text talks about having the answer use the recv-appId as the appId.
We need to add text about subsequent offer/answer, do we mandate keeping current appId.

Other issue we have is if we need to send appId (send-appId) or can only send the recv-appId

Regards,

Christer

v2.23.0 | Report a Bug | By Email