IETF Logo Mail Archive

Re: [sipcore] 4028bis: forking

OKUMURA Shinji <ietf.shinji@gmail.com> Thu, 28 May 2020 06:35 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 8BF7A3A0414 for <sipcore@ietfa.amsl.com>; Wed, 27 May 2020 23:35:25 -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 dFASl89zlWD8 for <sipcore@ietfa.amsl.com>; Wed, 27 May 2020 23:35:24 -0700 (PDT)
Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (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 5BB423A0404 for <sipcore@ietf.org>; Wed, 27 May 2020 23:35:24 -0700 (PDT)
Received: by mail-pg1-x534.google.com with SMTP id s10so12951078pgm.0 for <sipcore@ietf.org>; Wed, 27 May 2020 23:35:24 -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=ZyXLaPcUdAdclc+0zr6iytQ+8ig/m0jRcl3TuZZ+1+o=; b=ZTolCgnbK8GuPJusVVOxcTTDfUFoNun+qPiUM7OwW19CqAMG3wrjKayn5kVHjooa9S txjtNvKA7NuY542DahCNZx8MQwxpDDiz0Vy7UHX22lmPhsOocV4axvVjKpL2BI445bM+ o0O7Vi/h78j9w/Qfqi53vlT/OqUmvo9yCuj3y/lqN8mnC8zhM2ula6muAXRrvyKOPTMD 3IRjjHuIQ6xNSfE1qJ7wALA+kHaBo6rqCt94nC6tmg6v1QLmrR5CVN48zr6o88rvEOsi L+Ot9kDNvA/omxNdgAupdQ270k+sqP9IK6TOJR5cItfTI+2QcF7kaDJli6tQg/gpq/ac QUCA==
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=ZyXLaPcUdAdclc+0zr6iytQ+8ig/m0jRcl3TuZZ+1+o=; b=TFwjLiFcQXklce755F0TnO5jGKAtuRvCvHhL3X3XlsEtPCM6FM+SXUh5uqGFyWD6wh YaLkDXTPZFCBXwIpu5LxQcmTcIsqEuKSHyZLjDn6KFgdvWbW3JHa0FZeKMMz9eTdTkpi TF5a4Fpq1ySTPCEf/wYC6DcEsnVwWegPF8MCNikSKEmKxg/urpNTRnjaDRooF6RycrJd vuW2qyCR4yVZdRE7cruBV2/O7nY5aZ1rfIDYI9rgimO61zzWw6dprNaBh9coEvhsYxgT Ck8EJ8bbKAzYQFMqNmRadOGf/voqVkYys4jNVJN07xQwoctyT1rr5rZ4atHWoX5W48F3 BeCQ==
X-Gm-Message-State: AOAM53182UDMUzDSWoVhIgriHD8fZKhAMadiFT2UYKS1zBJ+INmv6y+B fiC3uEYDWs4VhLYyeMM4wrLftu1G
X-Google-Smtp-Source: ABdhPJw7UWHxrmd6+xz1+DuzvGMxuMNw2259Vye9+qVzHZMoz8LePPVXW4HpjTpDJdkOitS0EbXN9Q==
X-Received: by 2002:a63:6dc7:: with SMTP id i190mr1459376pgc.171.1590647723445; Wed, 27 May 2020 23:35:23 -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 j10sm3961936pjf.9.2020.05.27.23.35.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 27 May 2020 23:35:22 -0700 (PDT)
From: OKUMURA Shinji <ietf.shinji@gmail.com>
To: sipcore@ietf.org
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org>
References: <e7963ad4-6423-cf44-1cba-d21536962738@gmail.com> <51de720d-638b-bd7a-6655-8cd950a2d2ef@alum.mit.edu>
Message-ID: <7fadcff5-f3fd-647a-4361-2ab46b2163be@gmail.com>
Date: Thu, 28 May 2020 15:35:19 +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: <51de720d-638b-bd7a-6655-8cd950a2d2ef@alum.mit.edu>
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/jPyiUSspsNeuAFWp71rfNnol_hI>
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:35:26 -0000

Hi,

The cause of the issue is the 422 response and the cause of the 422 response is the SE header.
I think the simple solution is to allow the proxy to increase the value of SE-header. RFC4028 also conditionally allows the proxy to increase the SE-value.
Honestly writing, INVITE request doesn't need a SE-header, I think it's enough for UAS to copy the MSE value into SE-header of 200 response.

Regards,
Shinji

On 2020/05/28 2:48, Paul Kyzivat wrote:
> Shinji,
> 
> On 5/27/20 4:12 AM, OKUMURA Shinji 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.
> 
> What do you think *should* happen?
> 
>      Thanks,
>      Paul

v2.23.0 | Report a Bug | By Email