IETF Logo Mail Archive

Re: [sipcore] 4028bis: forking

OKUMURA Shinji <ietf.shinji@gmail.com> Thu, 28 May 2020 06:34 UTC

Return-Path: <ietf.shinji@gmail.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C02B93A0404 for <sipcore@ietfa.amsl.com>; Wed, 27 May 2020 23:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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 GpPOm1Y3VZW5 for <sipcore@ietfa.amsl.com>; Wed, 27 May 2020 23:34:48 -0700 (PDT)
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (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 84C8F3A03F6 for <sipcore@ietf.org>; Wed, 27 May 2020 23:34:48 -0700 (PDT)
Received: by mail-pg1-x52b.google.com with SMTP id p21so12935161pgm.13 for <sipcore@ietf.org>; Wed, 27 May 2020 23:34:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=n3xfDEVXvfe6/GjQOMZDOkHcEkaq5G6jChSUtwJhswk=; b=eGlLTx3Cg6WWafZ8M07lA4TynnTnCwYYfxfy3U1uATiKrUCH0RhWgmg1kU7YeV/ySg PE4L8hKWbd+MIrgaJEz2N4IL8dz4YnffxUsz3pdLCZxBvLPbd27T9hqbVEs8yykAG18v QWRbCEyxI1LjkSj9jfH8QR+Ub7Z64CA2fVeED5AFVC+h1orpLpVG63j5o9xSw+JYFk4s 610DuxVAU/H+sY+UmYFDEMVC67jbDg2R+5RizSJZ/UMnp7oriq4mxyOL6lDdpTUPfRlj UHnyD/NQ8C//IxaBzueXhYKzlvi068kvpuYUog/Hb/W07haHr6fDt6M01p10NDMsTWPC +Yog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=n3xfDEVXvfe6/GjQOMZDOkHcEkaq5G6jChSUtwJhswk=; b=nDUa2i55uHZvp2/7uheO9gCBepkrIW8lB1RMB0bcyCsUyUgn6XgNWAzIw8l/pFIYac ewbhkeLkcV99QJDZ0d8yTmo63fLgZMf2qjXp9indzOEKgW7aE0AT27Rs8fgbYvdyCb0T MR5Recdtz0Bcre2ZCleIO/5OPT8xDuxS59d/nsDmdXOB2C4QwH1OueI4PWlQx8ZmWzq+ 82kqtZsGsFesrBu3OZrIjrw3PkK96yYvSCN0JCHnLk+2gICi/uWiIvwQc1RCEXrm1ndN 6Io60gVLtq8dVZSd4guBFJD64fCg8ZN3D59dJEmsuO2Vn7Mruxj20Q3pxi7nwGHM+bvW VsPQ==
X-Gm-Message-State: AOAM533DY/90eDt9j2wRJFXJGUfjmSQ66SJCbVlbZ8wDvua6SNN8X+b9 9QoVlVI+XoijM9mDqfBqC50=
X-Google-Smtp-Source: ABdhPJxCjpxqPNdIFLuZx0kkG6WZkBqYU/MzbJp8zDJG8ew3hs5rqZw4ngAiYhFiPM+heUjuGXHL1Q==
X-Received: by 2002:a63:63c6:: with SMTP id x189mr1499270pgb.36.1590647688043; Wed, 27 May 2020 23:34:48 -0700 (PDT)
Received: from [192.168.1.10] (x156176.ppp.asahi-net.or.jp. [122.249.156.176]) by smtp.gmail.com with ESMTPSA id 136sm3831155pfa.152.2020.05.27.23.34.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 27 May 2020 23:34:47 -0700 (PDT)
From: OKUMURA Shinji <ietf.shinji@gmail.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
References: <e7963ad4-6423-cf44-1cba-d21536962738@gmail.com> <6BD34002-7DC1-445B-94ED-3F3C7F5944C2@ericsson.com>
Message-ID: <6d5b0b50-0d12-e23a-0228-4fd30ebd5f14@gmail.com>
Date: Thu, 28 May 2020 15:34:44 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1
MIME-Version: 1.0
In-Reply-To: <6BD34002-7DC1-445B-94ED-3F3C7F5944C2@ericsson.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/yMLdlz0IH6PjwEEYr0prMmQW1yI>
Subject: Re: [sipcore] 4028bis: forking
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2020 06:34:50 -0000

Hi,

As you point out, the other responses(407, 420, ...) cause the same problem.
But session-timer is essentially a kind of pre-condition, so I'd like to avoid incoming calls to fail because of it. And I'd like to sort out also the rules in early dialog.

Regards,
Shinji

On 2020/05/27 19:16, Christer Holmberg wrote:
> Hi,
> 
> A proxy rejecting a request is not unique to the session-timer.
> 
> If Alice receives a 422 she can send a CANCEL (if other early dialogs have been established), and then a new initial INVITE.
> 
> Regards,
> 
> Christer
> 
> 
> On 27/05/2020, 11.12, "OKUMURA Shinji" <ietf.shinji@gmail.com> wrote:
> 
>      Hi,
> 
>      In following scenario,
>      (1) Alice sends INVITE.
>      (2) Proxy1 forks INVITE to Proxy2(for Bob) and Carol.
>      (4) Proxy2 rejects INVITE by 422.
>      (6) Carol accepts INVITE by 200.
> 
>      Eventually Bob never receive INVITE.
> 
>        Alice        Proxy1    Proxy2(->Bob)   Carol
>          |(1) INVITE  |            |    |       |
>          |SE:1800     |            |    |       |
>          |----------->|            |    |       |
>          |            |(2) INVITE  |    |       |
>          |            |SE:1800     |    |       |
>          |            |------------------------>|
>          |            |(3) INVITE  |    |       |
>          |            |SE:1800     |    |       |
>          |            |===========>|    |       |
>          |            |(4) 422     |            |
>          |            |MSE:3600    |            |
>          |            |<===========|            |
>          |            |(5) ACK     |            |
>          |            |===========>|            |
>          |            |(6) 200 OK               |
>          |            |SE:1800                  |
>          |            |<------------------------|
>          |(7) 200 OK  |                         |
>          |SE:1800     |                         |
>          |<-----------|                         |
>          |(8) ACK     |                         |
>          |----------->|                         |
>          |            |(9) ACK                  |
>          |            |------------------------>|
> 
>      I hope that 4028bis addresses this issue.
> 
>      Regards,
>      Shinji

v2.23.0 | Report a Bug | By Email