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

Roman Shpount <roman@telurix.com> Fri, 26 February 2016 17:52 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 BC5DD1B2C95 for <mmusic@ietfa.amsl.com>; Fri, 26 Feb 2016 09:52:21 -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 2p9f49kFx_yC for <mmusic@ietfa.amsl.com>; Fri, 26 Feb 2016 09:52:20 -0800 (PST)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (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 8F2901B2C8E for <mmusic@ietf.org>; Fri, 26 Feb 2016 09:52:20 -0800 (PST)
Received: by mail-ig0-x22d.google.com with SMTP id z8so40596174ige.0 for <mmusic@ietf.org>; Fri, 26 Feb 2016 09:52:20 -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=Lx2HorjFjoFPgorODgb0gt1ZzaIQxF+toHBV+VtGNCo=; b=hsmvPI7fFZCgbdcPbCPWRdCqRG3pZL0cqAuRGQvY5G4NTLzSQHbD4TDSTsYd/EsLDX a2Xq4pedAG/PzYru13EJRRm/2tDmHP+dmM1DjbQT7ZPvtpb/rp6rzoh9K7DZXe0DQnsu 5LUhn34GKs5axk3a2tnzmgSXDuI2KXKDduwM+TLSYMLSlzTS0f4pw8KETbNAnfs407Gd joyxv22oq3L0Z/pPBNdEV5VihD/sf4vK8XDLE/pV30UmUbbN3A1pgMjmoBzB2plqEIsz EciWI8kJntfxQ0HjcZcUF9wT30VWuIDQTrKFpcBovkW2P7ojxXqPrF6mIDENhrhJX6ry rwvQ==
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=Lx2HorjFjoFPgorODgb0gt1ZzaIQxF+toHBV+VtGNCo=; b=f7w1kwDkGh95Fdqzc6YfDYEDg92st5XjqpNvSUEd+9ARLhuhINsms36x60ZL8n9aHh o5Z4cNowS4qKKR0etpC7UZNjr0y61M4BIYIwh06NPyVkyqFZrsOvgYzOVwLjNeL2MR6a dZu35FhZsR3teHMK5VA2BIqfhbv9ItM7T+weGqlUOJTL9OEhjfa2uYEPX4puzi4cymmz pVGp90AlBR5nGRazngJAyrY3OnoWXN+sst0YscnYwTsF5Typ4v44EoKXgxGKgRtCNsi0 Ssl85AcRVLdFwzyqMpO4JOIf932dDtvS8o7cbgT02ol6DCVuFlr0HgaaNDD05tPqy1Yf L13Q==
X-Gm-Message-State: AD7BkJJOBycKZgoidMjBbdE6ZL+MWLN8UeiXT8pUMK3wThxmfiFWZ5S7/orW7jDl6KMg8g==
X-Received: by 10.50.92.68 with SMTP id ck4mr4026653igb.93.1456509139965; Fri, 26 Feb 2016 09:52:19 -0800 (PST)
Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com. [209.85.213.169]) by smtp.gmail.com with ESMTPSA id n75sm5737753ioe.28.2016.02.26.09.52.18 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 26 Feb 2016 09:52:18 -0800 (PST)
Received: by mail-ig0-f169.google.com with SMTP id y8so40596032igp.1 for <mmusic@ietf.org>; Fri, 26 Feb 2016 09:52:18 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.43.194 with SMTP id y2mr4000396igl.96.1456509138037; Fri, 26 Feb 2016 09:52:18 -0800 (PST)
Received: by 10.36.105.77 with HTTP; Fri, 26 Feb 2016 09:52:17 -0800 (PST)
In-Reply-To: <56D08962.3060006@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B37E425AB@ESESSMB209.ericsson.se> <CBDE14F9-B68C-4471-9E24-0D7EA7821795@csperkins.org> <56CF9400.2020002@alum.mit.edu> <FDDE79D2-43D4-4382-92B4-4E22FFFEA8AC@csperkins.org> <56D074F4.2080401@alum.mit.edu> <2A2E7C19-3106-4A7D-B533-8A7267A9BAD4@csperkins.org> <56D07D29.2030500@alum.mit.edu> <CAD5OKxt0CBectoG5gpNsK4SPAu0JwnJOn7UimpKgt-TnFo+0zQ@mail.gmail.com> <56D08962.3060006@alum.mit.edu>
Date: Fri, 26 Feb 2016 12:52:17 -0500
X-Gmail-Original-Message-ID: <CAD5OKxtRB-f84=axhq_mkuyGXcq8nLCU2T6+6y=DNv9Ng1tKPQ@mail.gmail.com>
Message-ID: <CAD5OKxtRB-f84=axhq_mkuyGXcq8nLCU2T6+6y=DNv9Ng1tKPQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary="047d7bfea0b6c90aeb052caff591"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/IVzrYCxXlotVKPRy5qJaK3Rlo7w>
Cc: Colin Perkins <csp@csperkins.org>, "mmusic@ietf.org" <mmusic@ietf.org>
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: Fri, 26 Feb 2016 17:52:21 -0000

On Fri, Feb 26, 2016 at 12:20 PM, Paul Kyzivat <pkyzivat@alum.mit.edu>
wrote:

>
> The session remains, and so the PT bindings remain. But the O/A rules are
> negotiating which of those are to be used going forward. If the new offer
> no longer mentions some PTs that were previously bound, then it is saying
> that it doesn't want to receive them any more.
>
> It is becoming clear to me that it will be necessary to define PT bindings
> - what they are, when they are established, when they are forgotten, and
> the scope within which they live. Each participant will need to know these
> bindings, and they must agree on them, except for well defined signaling
> delays. I guess this is a lot like an RTP session, except that it is tied
> to O/A signaling.
>

One other thing to keep in mind is that RTP session creation and tear down
is not time synchronized with O/A. End point might still be receiving media
packets for the previous RTP session after O/A completes. If O/A happen
often enough, several O/A exchanges can complete while old RTP sessions
established by old O/A exchanges are still running. PT should uniquely
identify codec profile for all of them. In case of SIP, O/A exchanges
typically take more time then RTP session setup/tear down, so keeping track
of the last two O/A exchanges is typically enough.

Regards,
_____________
Roman Shpount