Re: [MMUSIC] Offer/Answer PT Questions - text proposal

Roman Shpount <roman@telurix.com> Thu, 03 March 2016 16:30 UTC

Return-Path: <roman@telurix.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 8B21A1A710D for <mmusic@ietfa.amsl.com>; Thu, 3 Mar 2016 08:30:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 CO-OL4nxfKiz for <mmusic@ietfa.amsl.com>; Thu, 3 Mar 2016 08:30:00 -0800 (PST)
Received: from mail-ig0-x244.google.com (mail-ig0-x244.google.com [IPv6:2607:f8b0:4001:c05::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49A9F1A7030 for <mmusic@ietf.org>; Thu, 3 Mar 2016 08:30:00 -0800 (PST)
Received: by mail-ig0-x244.google.com with SMTP id sv7so2574257igc.1 for <mmusic@ietf.org>; Thu, 03 Mar 2016 08:30:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=6BXT1yWrn6YFsfMEvaQYTHXrVNvlQB70Rebah2XqjS4=; b=gvC5xLK/QKM14x8EGeSq39jyAV4+V1sAsDp5xNaae7LixXVMdCW+YEHZs6oyFb5J8Y b1Tokdh7dNPXK9r0O44H7EEYhCe+C+PAiA+Q1PH+CWwQTH+oRbv6BkIVgwxVKNcGEEyZ XEgodSJCD/Vogudy03XCjO2dJUlHUTf+2woXZnwC96XWHO6AYZy31Ruqrrmd+VSytuvv vZaDVRjj/0FCNjP/yjgL52SsdpXrJRqc9ev0ywGw4JyGsObJStqIxzF15UA1zxJ4SUj2 M4YUK2qdtYFZy5QKktR9Od72fQOWgDy6+kVzL6u/WkId+ipyS6PGkPODFvhcZ6RDABK2 zC2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=6BXT1yWrn6YFsfMEvaQYTHXrVNvlQB70Rebah2XqjS4=; b=ESVL9R5MZ258CjRxnFdTiDreouhDevjXQ6KEk1Xa56LYPrCgZpfgzz+e+e2vknaXqr NN1jy6oTRVVt50xwwYNxCDpXrKjJx3yOYPSooCVbe+penBhtovgnN3zZifMZkbCOl2k2 n7IxViVVfEyc/WbHvQ81IdTEmuSGQ+I3yFbi+Z4d149J/3hfKdY6F6lxWrUKargmCtT6 hlpLwAkVXNZVQHeb8wwhvbE1d5EblK/r8CvzmhCWYt0zw56qPtflS0MMdRDomEy8D7Lq RKHsEmvBqMjLc/7lmec4y6AelWuLU7HWwaXrLsgZGmjncxZa56wp8EPDKn1WklcO463q 23RA==
X-Gm-Message-State: AD7BkJLiQDU/6f+H4X/IGKpOi33xrvCKt5k/0/i0uX3yGxeZMJxHi5Prn8XaMW09eak/Gg==
X-Received: by 10.50.29.48 with SMTP id g16mr6788893igh.4.1457022599697; Thu, 03 Mar 2016 08:29:59 -0800 (PST)
Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com. [209.85.213.182]) by smtp.gmail.com with ESMTPSA id uh3sm3825065igb.18.2016.03.03.08.29.57 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 Mar 2016 08:29:57 -0800 (PST)
Received: by mail-ig0-f182.google.com with SMTP id i18so16880141igh.1 for <mmusic@ietf.org>; Thu, 03 Mar 2016 08:29:57 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.109.196 with SMTP id hu4mr6643936igb.24.1457022596884; Thu, 03 Mar 2016 08:29:56 -0800 (PST)
Received: by 10.36.105.77 with HTTP; Thu, 3 Mar 2016 08:29:56 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37E5622F@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37E425AB@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37E4BD38@ESESSMB209.ericsson.se> <56D463A3.8070007@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37E4D5E9@ESESSMB209.ericsson.se> <56D4B1F1.2070706@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37E4D951@ESESSMB209.ericsson.se> <66F2264B-3CA3-4650-88B6-89FC64D5FD29@csperkins.org> <7594FB04B1934943A5C02806D1A2204B37E4DB7C@ESESSMB209.ericsson.se> <56D4C0F5.50901@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37E4EAD1@ESESSMB209.ericsson.se> <56D5CAA0.2060901@alum.mit.edu> <CAD5OKxtdmhW-opmp2TQou5wYbz70FdUvftr1PAZb9YiW4crevA@mail.gmail.com> <56D5E81F.2040306@alum.mit.edu> <CAD5OKxtXzhP9L-V6O5NVtCN4aQHy9X8Fpkc0_xKdWmtR03h4KQ@mail.gmail.com> <56D5EE38.2060706@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37E54995@ESESSMB209.ericsson.se> <AFCC6C46-B945-4749-B20A-AB7EFBC2345F@csperkins.org> <56D76C61.6040109@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37E5622F@ESESSMB209.ericsson.se>
Date: Thu, 03 Mar 2016 11:29:56 -0500
X-Gmail-Original-Message-ID: <CAD5OKxsWynQKQHttXVYXdEUnvPd_3USbAcP4KYGvQe38fm+MtQ@mail.gmail.com>
Message-ID: <CAD5OKxsWynQKQHttXVYXdEUnvPd_3USbAcP4KYGvQe38fm+MtQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="089e011605a2513a7b052d278257"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/VeTEXQegy4qY-NICYtc1V159RKQ>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Offer/Answer PT Questions - text proposal
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Mar 2016 16:30:06 -0000

On Thu, Mar 3, 2016 at 4:51 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> >But suppose you are switched to another preexisting RTP session. It is
> new to you, but it isn't new, and has existing RTP bindings. And those
> might conflict with ones you had in your old RTP session.
> >
> >If you knew this was a new RTP session you could forget your old
> bindings, and start over.
> >
> >This sort of thing could happen if you are connecting to a conference
> server. First you are connected to an IVR to authenticate. That is your
> first RTP session. After that you are transferred into the conference.
> >That is your 2nd RTP session.
> >
> >If this is done via REFER, then you will see it as a new SIP and O/A
> session, and so will start out with an empty set of PT bindings.
> >
> >But if this is done via 3pcc, or a media relay, then we have the problem.
>
> So, then, perhaps we should allow PT re-binding within an O/A session, in
> case the underlying RTP session etc changes?
>

Yes, we should allow re-binding. This is what I was saying all along. The
only thing you need to do when re-bind PT is to change local transport or
mid so that you can decode incoming RTP packets using the right PT mapping.

To reiterate:

1. RTP session can start before the O/A session in cases of 3pcc and RTP
mixers.

2. It can continue after O/A session ends in cases 3pcc and RTP mixers

3. O/A session can migrate from one RTP session to another in case 3pcc or
RTP forwarders.

4. End point participating in O/A session does not always have access to
previous history of the RTP session it participates in and has no way to
determine when RTP session changes.

Most importantly, all of the above is irrelevant to solve the problem in
hand. Solution should be that O/A session should operate as if O/A session
is an RTP session until it encounters a conflict. If conflict is
encountered (since it is unavoidable in some architectures such as 3pcc and
RTP mixers), a recovery mechanism should be provided (allocate new local
transport and start the new RTP session).
_____________
Roman Shpount