[MMUSIC] [mmusic-trickle-ice-sip] : Conflict in Figure 10 against 4.1.1 & 4.1.2 | Race condition between 183 & INFO
ayush jain <jain.ayush09@gmail.com> Fri, 01 April 2016 04:50 UTC
Return-Path: <jain.ayush09@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17A7B12D0CE for <mmusic@ietfa.amsl.com>; Thu, 31 Mar 2016 21:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 XFwSxKkyXquS for <mmusic@ietfa.amsl.com>; Thu, 31 Mar 2016 21:50:50 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (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 855F012D0A5 for <mmusic@ietf.org>; Thu, 31 Mar 2016 21:50:50 -0700 (PDT)
Received: by mail-ob0-x22e.google.com with SMTP id m7so42679609obh.3 for <mmusic@ietf.org>; Thu, 31 Mar 2016 21:50:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc; bh=ExOwn2EU+fhDMGsrYpZwl+Zsr0UhZgLS7ggPgopm+GI=; b=Peul2gMbptBwZml7EBDbUnES88y9mjxpZ4rjfFGbpPK8pOArvYaNSeUXjX+LWoXAsj Dr7GcHA3twVuMK4RXlqdOK2dND9Wt0YQtfC6ZRTBtbTbCX7DAXcaYrPhD1/8V++D1SKn UeAwr5lY62gjssoRY5R6tuF1UAaZmyOf4SL+0YouEmnoxBjccD6mTEAgHIhK6UORXsPj 9BpdazLwhNam5lolqlS++2LU7eLxR+YvYRPg9v02Jxh1p2VSK9X2CX2I+kTaSa308QGG UOn5mUUwKKjTIGC3zagOk8v/0Tlx4PJ/Vk1lE+AfnDoGG99hhRBR8o/vfr4/U8Ae2QMg lC5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc; bh=ExOwn2EU+fhDMGsrYpZwl+Zsr0UhZgLS7ggPgopm+GI=; b=fBhvO9bKTS/aEniMdVB+P5ZCeiZ5HbKLV2dTFqCrWWpG8fytjecehLRJjxrXf+5+B8 fWUnS3yNOk7jkwMxNqjQ/aXixMhLOsd1qqj06Ws4tA2R2xfVfKlQTJgtob9k6IE8GBOL gZK3luJcJzg51rYBlZ3z5dRESHMsb/hj8HbdMMTjOzKcWX+DShdZWBbHGDoLOs5+RNxY HHzMJ0d79QvgYVdIXy6YH/waQhpwmi3UULxPR4xArRQ+VH+E2613wRz1XNT+lQTMSN1T BapiWdFRj/rM/w0yxzk0H8Fcd5woh2D2MTrRRx1/nb+ymDvKRZ5JcsrOoY9d2H5ejTz9 l7ug==
X-Gm-Message-State: AD7BkJLOFGcMliE1ZTQHl50Us0aeL4x5XhXRq1hEe9wvk99nvMoB/aVXV9bo2arvlW1dAgwjOzSufNNR7fKFAA==
MIME-Version: 1.0
X-Received: by 10.182.33.166 with SMTP id s6mr1615527obi.30.1459486249966; Thu, 31 Mar 2016 21:50:49 -0700 (PDT)
Received: by 10.76.101.165 with HTTP; Thu, 31 Mar 2016 21:50:49 -0700 (PDT)
Date: Fri, 01 Apr 2016 10:20:49 +0530
Message-ID: <CAAMRqPuGRw5zDxVUFaUkH0e6eRztfGXn6tf8wTm-7OH49xuv9Q@mail.gmail.com>
From: ayush jain <jain.ayush09@gmail.com>
To: mmusic@ietf.org
Content-Type: multipart/alternative; boundary="001a11c2de1c7be23f052f651fab"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/IsJnLxx8XbAMi_jCPce216koVvc>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: [MMUSIC] [mmusic-trickle-ice-sip] : Conflict in Figure 10 against 4.1.1 & 4.1.2 | Race condition between 183 & INFO
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Apr 2016 04:50:53 -0000
Hi, (Re-posting here as suggested by Paul) As per [draft-ietf-mmusic-trickle-ice-sip-03], Section - 5.4 - Fallback to Half Trickle, figure 10 depicts: - Bob initiating INFO immediately after responding with 183 (Answer) to Alice. But I believe that might create a race condition. Either 183 should be reliable (Prack) or else Bob should wait till it receives INFO from Alice as per 4.1.1 & 4.1.2. Reason being - While sending Info, Bob won't know otherwise whether 183 has been received by Alice. (Would be a race condition between 183 & Info, If 183 wins the race, its fine, other case, Alice would receive Info for a dialog which doesn't exist) Regards, _Ayush ---------- Forwarded message ---------- From: Thomas Stach <thomass.stach@gmail.com> Date: Thu, Mar 31, 2016 at 10:10 PM Subject: Re: SIP Usage for Trickle ICE - draft-ietf-mmusic-trickle-ice-sip-03 | Conflict in Figure 10 against 4.1.1 & 4.1.2 To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg < christer.holmberg@ericsson.com>, ayush jain <jain.ayush09@gmail.com>, " enrico.marocco@telecomitalia.it" <enrico.marocco@telecomitalia.it>, " emcho@jitsi.org" <emcho@jitsi.org> inline Am 2016-03-31 um 18:25 schrieb Paul Kyzivat: On 3/31/16 11:23 AM, Christer Holmberg wrote: Hi, I don't have the RFC in front of me, but Paul may have the answer :) I'll offer an opinion. See below. I see no reason why you should not be able to send INFO. 183 indicates that the UAS has received the INVITE, so... Regards, Christer Sent from my Windows Phone ------------------------------------------------------------------------ From: ayush jain <mailto:jain.ayush09@gmail.com> <jain.ayush09@gmail.com> Sent: â31/â03/â2016 09:55 To: Christer Holmberg <mailto:christer.holmberg@ericsson.com> <christer.holmberg@ericsson.com>; enrico.marocco@telecomitalia.it <mailto:enrico.marocco@telecomitalia.it> <enrico.marocco@telecomitalia.it>; thomass.stach@gmail.com <mailto:thomass.stach@gmail.com> <thomass.stach@gmail.com>; emcho@jitsi.org <mailto:emcho@jitsi.org> <emcho@jitsi.org> Subject: SIP Usage for Trickle ICE - draft-ietf-mmusic-trickle-ice-sip-03 | Conflict in Figure 10 against 4.1.1 & 4.1.2 Hello, Myself Ayush Jain, I was going through 'draft-ietf-mmusic-trickle-ice-sip-03' for the support of trickle ice in SIP Sessions. In Section - 5.4. Fallback to Half Trickle, figure 10 depicts: * Bob initiating INFO after responding with SDP answer to Alice using 183. But that won't be possible isn't it? Either 183 has to be reliable (Prack) or else Bob would have to wait till it receives INFO from Alice as per 4.1.1 & 4.1.2. Section 4.1 seems to say that this usage is invalid. In particular: o The dialog at both sides MUST be in early or confirmed state. As noted in 4.1.2, after Bob sends the unreliable 183 *he* has an early dialog, but he doesn't yet know if Alice knows that. If he does go ahead and send the INFO, and the 183 arrives first, then probably all will be well. But what if the 183 is lost, or delayed, and the INFO arrives first? In that case the INFO will have a dialog id that Alice doesn't know about yet. Alice *could* decide to treat the INFO as an indication that the dialog exists and go ahead and process it as such. But Alice isn't obligated to do that. Paul is spot on. We had exactly this discussion quite a while ago and it finally lead to the existing text in 4.1. So I think Bob should wait for some evidence that Alice knows about the dialog. And INFO from Alice would do it, but I guess that won't be coming in the half-trickle case. So the only safe way is to use a reliable 1xx and await the PRACK. Of course that won't work if Alice or Bob don't both support 100rel, but it seems reasonable to me to require that as part of trickle support. Well, in the half trickle-case Alice _supports_ Trickle, but caters for an answerer that doesn't. The INVITE includes the 'trickle-ice' option tag. So, Bob can rely on receiving the INFO. Regards Thomas My apologies if I misunderstood the same. Just curious to know. No need to apologize. It is a good question. It seems to identify a bug in the spec. I suggest you repost this to mmusic. Thanks, Paul Regards, _Ayush