Re: [Insipid] Requirement for Intermediaries to Update Session ID for other parties

Brett Tate <> Tue, 07 June 2016 16:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2EC8E12D0F3 for <>; Tue, 7 Jun 2016 09:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1zi-jDQtxFLC for <>; Tue, 7 Jun 2016 09:41:59 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c0b::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 80B0812D7CB for <>; Tue, 7 Jun 2016 09:41:59 -0700 (PDT)
Received: by with SMTP id h190so19786527ith.1 for <>; Tue, 07 Jun 2016 09:41:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=from:mime-version:thread-index:date:message-id:subject:to :content-transfer-encoding; bh=Ifbas5iuo1wkGW5RtOhU+zHETUjq5lwGmxA8cSfjN2g=; b=BfMbhTpqbcioPAXK01b/DjLSRPFwROoEyxNSIdBG7GTE5JH4uYhs9CUCUEkLnYs6Cp 5P561eeM3kmpHu/tgx6/Aqixx0JsuUeosHJNYAXPvy1IhLrrH2pmoiyNHAkFarK11OBb JY1rW46+rME0kUS5uGLqmKibjcRHrROGLxtwIKU1+IulZk0SquRRqCu+6MFsM7LcyFcB K7qrq/YZH2mCJVuaQ5QEItax/k94dCf+MO0FqEVfncEZFOl3J0su6M9Lgzh2B5nDYBwe PBFYlG+dwUaDURa24/FZlcrbZOYqisQH7ERKB4n8I0KRF8H1B+oOg+EeI0NYGfVuafOZ zZhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:content-transfer-encoding; bh=Ifbas5iuo1wkGW5RtOhU+zHETUjq5lwGmxA8cSfjN2g=; b=BdE623Y6SUNeygl1KGxcTFSpPN10RRh/+vkypakdRv3mfgN0AyeYqHR+/8ER7q/VMk pzGWJQLyZdSM2THysMNUcSaFHyENaeGcLzqfrqzjPYCxEsbg4r8BDaq00DZtHbHJf0qW i99AQkpsKWA840MrJuk+z0FR/rjolQuooq6wa1+qFa3lR88+tDwYdUw/B5lra/a2FNrl ugAYo9IxIYaqWY6GtyzAK9CApdlt92bf4RSQjnLd9gfNKRcEOlqZ3CvWkCuU2/2jP6Pm XbppA5KA0jZUnt83DGIkoIA0AkTOCPAcFOPxwR3Z0uxNO5mI17envIOdBFfXoB83L+/r vRgw==
X-Gm-Message-State: ALyK8tKb7nAvYkmjWR51M5EU6iklS5gNW1QpijSUdeCEYMZZ1krpT8Uph3M3nHQdR3d6muhnI8/XNOUzxAOVGdFZ
X-Received: by with SMTP id d69mr5530771itb.3.1465317718795; Tue, 07 Jun 2016 09:41:58 -0700 (PDT)
From: Brett Tate <>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdHA2312D/wUckGRTgeNOtz38IHE2A==
Date: Tue, 7 Jun 2016 12:41:58 -0400
Message-ID: <>
To:, Paul Giralt <>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [Insipid] Requirement for Intermediaries to Update Session ID for other parties
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 07 Jun 2016 16:42:01 -0000


> There are several references in the draft that indicate
> an Intermediary SHOULD update endpoints involved in a
> session if the session ID on one call leg changes, but
> it does not require it. Is there any reason why we should
> not change these to a MUST so that Intermediaries are
> required to update the Session ID for any participant it
> knows is out of sync?
> If there are good reasons for leaving as a SHOULD,
> I’d like to hear them.

The following are a few thoughts on the topic.

1) A proxy can't really do it.

2) I assume proxy B2BUA's that only initiate BYE's would not want to do it
except when sending BYE.

3) Because it causes extra traffic and potential for glare, the
administrator might not want the extra messaging to occur solely to update
the UUID.

4) The request might not reach the device that the intermediary is
attempting to update.  Thus, it could be completely useless extra traffic.

5) Methods that the intermediary is willing to use for the update might not
be within the received Allow header.

6) It can cause the intermediary to be part of an infinite change loop
unless use re-INVITE without offer.

7) The intermediary might not have auth credentials to allow the change to
be successful.

8) Because of race conditions and other things, the intermediary initiated
messaging intended to correct the UUID could cause other locations to switch
to an incorrect value.