
From nobody Wed Jun  1 21:00:32 2016
Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C768212D0E0 for <insipid@ietfa.amsl.com>; Wed,  1 Jun 2016 21:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 B3s6QvXZ0elU for <insipid@ietfa.amsl.com>; Wed,  1 Jun 2016 21:00:28 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6917212D0CB for <insipid@ietf.org>; Wed,  1 Jun 2016 21:00:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=460; q=dns/txt; s=iport; t=1464840028; x=1466049628; h=from:content-transfer-encoding:subject:message-id:date: to:mime-version; bh=1pawlk+H+iSa5q+jFoU2DKjkbhqZMN9EL3zaOhaLywE=; b=dlNx/H2XFWBfgI66h7+5afqcrRYU+vCrbK6PGaA9vWZaiK0NJlNCVEHy k3U3Houfv0BlasmJYrNPZHhs/D1qY8OK9S27KIMu5dfRFWA0B11NMiaGO o1zaQoGYt9kG65zYgCWwvzW7fMzMXOyvZYbgS7Ba+gZCZQhhV22uDM2c4 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D8AQDYrk9X/4gNJK1egzq5c4IPAQ2Be?= =?us-ascii?q?odGOBQBAQEBAQEBZSeEb4ELAiYCiSGgNY9ikR0MASSBAYUmgXcIh1qCNSuCLgW?= =?us-ascii?q?YN44ggVMBjUiPTB4BAUKCBhyBZyCLLgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.26,404,1459814400"; d="scan'208";a="280752521"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Jun 2016 04:00:27 +0000
Received: from rtp-vpn1-510.cisco.com (rtp-vpn1-510.cisco.com [10.82.225.254]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u5240QiO001749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <insipid@ietf.org>; Thu, 2 Jun 2016 04:00:27 GMT
From: Paul Giralt <pgiralt@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <55234C8F-2A40-4B9E-8976-620A00FFEFF8@cisco.com>
Date: Thu, 2 Jun 2016 00:00:24 -0400
To: insipid@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/SsYq_HTYOA0QvV7cdNu4fGA0neI>
Subject: [Insipid] MUST or SHOULD for Type 4 / 5 UUIDs?
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2016 04:00:31 -0000

INSIPID WG,=20

Ben pointed out that we have an inconsistency in the draft. Section 4 =
states that endpoints SHOULD use Type 4 or Type 5 UUIDs when generating =
a Session Identifier, however Section 12 states that Type 4 or 5 MUST be =
used for privacy reasons.=20

I=E2=80=99m inclined to change the first to MUST and thereby require =
that only Type 4 or Type 5 UUID=E2=80=99s be used.=20

Does anyone have an issue with this change?=20

-Paul


From nobody Wed Jun  1 21:03:40 2016
Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D104E12D0FD for <insipid@ietfa.amsl.com>; Wed,  1 Jun 2016 21:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 mTok1tcXCD8V for <insipid@ietfa.amsl.com>; Wed,  1 Jun 2016 21:03:35 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90EB612D0E0 for <insipid@ietf.org>; Wed,  1 Jun 2016 21:03:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1826; q=dns/txt; s=iport; t=1464840215; x=1466049815; h=from:subject:date:message-id:to:mime-version; bh=8or+ReBzg2wq8z//jqO/hsffQBhiaPw3lvQFKOGNVxw=; b=Wcurjw+VHKpItQxhc+VeqDMIGSRLMDfJYM6TifKsKfKN9Zbg/+27tRJB fPkovYZJRRZxgjj+Wi++GygxAPxSNCndyuxTUSAGJVNT2cc3gMAq75+De xCjKBKn/N8F75svzbgNlbueVdvy0FvIOYIxevjSmBGeHE4d3hxVnX7bwW Q=;
X-Files: signature.asc : 842
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D8AQABr09X/5NdJa1egzq8Ag6BeodGO?= =?us-ascii?q?BQBAQEBAQEBZSeEb4EzAokhoDWPYpEdIw6GJ4F3glaFDII1K4IuBZg3gS+BfIp?= =?us-ascii?q?1CoFJFo0zhjOJGR4BQ4QJIIsuAQEB?=
X-IronPort-AV: E=Sophos;i="5.26,404,1459814400";  d="asc'?scan'208";a="108879045"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jun 2016 04:03:34 +0000
Received: from rtp-vpn1-510.cisco.com (rtp-vpn1-510.cisco.com [10.82.225.254]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u5243Xlt025012 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <insipid@ietf.org>; Thu, 2 Jun 2016 04:03:34 GMT
From: Paul Giralt <pgiralt@cisco.com>
X-Pgp-Agent: GPGMail 2.6b2
Content-Type: multipart/signed; boundary="Apple-Mail=_7C2A04B4-759C-4A7D-BF53-5D359535300D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Date: Thu, 2 Jun 2016 00:03:32 -0400
Message-Id: <EC7574F5-036F-4D93-94A3-02ECF80AD7C9@cisco.com>
To: insipid@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/R7DL5aEeGz--1iroK_Bo2DFCjzw>
Subject: [Insipid] Requirement for Intermediaries to Update Session ID for other parties
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2016 04:03:38 -0000

--Apple-Mail=_7C2A04B4-759C-4A7D-BF53-5D359535300D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

INSIPID WG,

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=E2=80=99d like to =
hear them.

Thanks,
-Paul


--Apple-Mail=_7C2A04B4-759C-4A7D-BF53-5D359535300D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXT7AUAAoJEADWV7cDInKsdVUP/jYYSvEbhAFBnGV2Vn1dM0LN
4Eh+fTj0nHuVFyLKgFOcyf+y48M/WOKVC5/Z4yCQB9D9AdnhebBmor78KjP+Z3DB
pb4epikBOTJp7g+5YcgW8YgR9WagRdliMp0qAi1hRLZvlvPCYmP0LtG9Jy53xdwt
1K7EJidvmiVU+ZcBJh5vTORy42vSqdq3OoqOkimzoe04MSarUKSP3wol3IaIaUkF
gLLXcOgwdpuX5czdBkwB3pUnCtmycoPZWrmzf8H9NGsmk8stsP+dc4/ER6whhHp5
dDhzUqswXnGnitGrPUUQUbICqFoAdHD9/HxjFOP3XKQdhqQYYuwK1S/ideAouRQB
Cx+4yQRG/aTiUe9oX1Wv4TkqUAS8NbOqXk8gYza7TtFjCvgGlnhjZA5QjQdXFLTr
/8/e/ndAJUA7jV1JkzGZDG8ciA8dxTRpZLeHELc/s+BQSuiqLU5/BRP72DLnzCYX
hYCKpiqGrtETisRpi8ArSyAzVENNIb8clxcUHxzflCtDNIG3bNwqIlL6x5xXBjMR
OkPNeSotlXL2KB4HxSe3G/c3D70Q3rm8iqzUm/DP7sNjtMlfUWBlKPEQ2Yq5bJU6
q6bBR0WkIYMd5Z4EujYGq1OqSE87GxxG1AOYBdWQi0AMOjI9m+BSum40h+CO6Lu8
RnwqgWJalQB/8/7hcxpr
=Oc7F
-----END PGP SIGNATURE-----

--Apple-Mail=_7C2A04B4-759C-4A7D-BF53-5D359535300D--


From nobody Thu Jun  2 00:01:16 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED18B12D119 for <insipid@ietfa.amsl.com>; Thu,  2 Jun 2016 00:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 GYzfJT28OFqC for <insipid@ietfa.amsl.com>; Thu,  2 Jun 2016 00:01:13 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAAA412B02D for <insipid@ietf.org>; Thu,  2 Jun 2016 00:01:12 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-32-574fd9b60ffa
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 66.24.27088.6B9DF475; Thu,  2 Jun 2016 09:01:10 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.154]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0294.000; Thu, 2 Jun 2016 09:01:09 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Giralt <pgiralt@cisco.com>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] MUST or SHOULD for Type 4 / 5 UUIDs?
Thread-Index: AQHRvINQyFCARoSFIEGWdNKLTlrq+Z/V0aEA
Date: Thu, 2 Jun 2016 07:01:09 +0000
Message-ID: <D375B4FE.990A%christer.holmberg@ericsson.com>
References: <55234C8F-2A40-4B9E-8976-620A00FFEFF8@cisco.com>
In-Reply-To: <55234C8F-2A40-4B9E-8976-620A00FFEFF8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5BB871FF83518F469676D815E44BFEB9@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHIsWRmVeSWpSXmKPExsUyM2K7je62m/7hBt+fm1jMv/+MyeJmw2NG ByaPKb83snosWfKTKYApissmJTUnsyy1SN8ugSvjTdcE9oJNbBWzf/5nbGCcztrFyMkhIWAi 0fH7DpQtJnHh3nq2LkYuDiGBI4wSy99NgnIWM0p8W7GBuYuRg4NNwEKi+582SIOIgJdE567v TCC2sIC1RO+F7WwQcRuJ//emMEPYRhIn328CW8AioCLx+8NzsDivgJXEnHOzwGwhoPpN97Yz gticArYSvTc2gNmMQAd9P7UGbD6zgLjErSfzmSAOFZBYsuc8M4QtKvHy8T+w+aICehJf7s1j hIgrSnx8tY8RoldP4sbUKWwg5zMD3Xl2lw9EWFti2cLXUOcISpyc+YRlAqP4LCTbZiHpnoXQ PQtJ9ywk3QsYWVcxihanFiflphsZ6aUWZSYXF+fn6eWllmxiBMbawS2/DXYwvnzueIhRgINR iYf3QZR/uBBrYllxZe4hRgkOZiURXr0bQCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8/i8Vw4UE 0hNLUrNTUwtSi2CyTBycUg2MfVfeWYX9Lz63VZWRXyPj6pzk6/pxB00Wbl+vwMTj9W0d3+XC nqdyezac6851/Tadk7mwKezuOkb34742L5ql7hxfr5f0S/1yJ09I5uY7N6+9W/N7xcKrJb1z WM+yfbDRz09UNRYoC2T4cjbq5sELkpkP7ryTLg0UjlPWqo9apD1jZcnPfh1HJZbijERDLeai 4kQAetK377ECAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/XFSzQx3Tcz1J3eWWafGuh75pgW8>
Subject: Re: [Insipid] MUST or SHOULD for Type 4 / 5 UUIDs?
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2016 07:01:15 -0000

Hi,

Is there a reason we put SHOULD in section 4? Backward compatibility?

Regards,

Christer


On 02/06/16 07:00, "insipid on behalf of Paul Giralt"
<insipid-bounces@ietf.org on behalf of pgiralt@cisco.com> wrote:

>INSIPID WG,=20
>
>Ben pointed out that we have an inconsistency in the draft. Section 4
>states that endpoints SHOULD use Type 4 or Type 5 UUIDs when generating a
>Session Identifier, however Section 12 states that Type 4 or 5 MUST be
>used for privacy reasons.
>
>I=B9m inclined to change the first to MUST and thereby require that only
>Type 4 or Type 5 UUID=B9s be used.
>
>Does anyone have an issue with this change?
>
>-Paul
>
>_______________________________________________
>insipid mailing list
>insipid@ietf.org
>https://www.ietf.org/mailman/listinfo/insipid


From nobody Thu Jun  2 04:01:11 2016
Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D508F12D153 for <insipid@ietfa.amsl.com>; Thu,  2 Jun 2016 04:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 ypqXlSk1asoS for <insipid@ietfa.amsl.com>; Thu,  2 Jun 2016 04:01:08 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 275E512D68C for <insipid@ietf.org>; Thu,  2 Jun 2016 04:01:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3128; q=dns/txt; s=iport; t=1464865264; x=1466074864; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=OjY6Vlo4PVuETKiCGasik+w6KBraSjJ3PnvXTB1vbfk=; b=BnX9UcOy4z1UBkfMGiKe7EuTU+xTESgDyrZWlqajMfBJ2ERcBLozSdBw kC1vJiFYuRpN5ogZmbOks9NwsXWI7dGKGSe28Er/6G9DqngPVCYaw9j+w ubiJZBrkkKgOKKotKh1dRnmzKeef/02LsMsJ0uA8va2msvibsBFHZ/WEA k=;
X-Files: signature.asc : 842
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AOAgBKEVBX/5NdJa1egzpWfQa6KYF5F?= =?us-ascii?q?wuFJUoCgTQ4FAEBAQEBAQFlJ4RFAQEBAwEBAQEgSwsFCwIBCBgqAgInCyUCBA4?= =?us-ascii?q?FDogZCA6wHJEjAQEBAQEBAQEBAQEBAQEBAQEBAQEBDgkFhieBdwiCTodBK4IuB?= =?us-ascii?q?Zg3AYMqgWiJDY8cj0sBHjaCBhyBS26JfX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.26,405,1459814400";  d="asc'?scan'208";a="110914005"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jun 2016 11:01:04 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u52B13V3032743 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 2 Jun 2016 11:01:04 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 2 Jun 2016 07:01:03 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1104.009; Thu, 2 Jun 2016 07:01:03 -0400
From: "Paul Giralt (pgiralt)" <pgiralt@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [Insipid] MUST or SHOULD for Type 4 / 5 UUIDs?
Thread-Index: AQHRvINR6ec6Tnr05kuK0Ahz0QaoWZ/WAxuAgABDBYA=
Date: Thu, 2 Jun 2016 11:01:03 +0000
Message-ID: <80673715-AE98-4C6C-BA60-BEBBA65215F3@cisco.com>
References: <55234C8F-2A40-4B9E-8976-620A00FFEFF8@cisco.com> <D375B4FE.990A%christer.holmberg@ericsson.com>
In-Reply-To: <D375B4FE.990A%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.123.195]
Content-Type: multipart/signed; boundary="Apple-Mail=_3DA88FF0-4C5C-49E5-835C-622A370C0349"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/vR1dIXYcXvsslZQg7zdR-Q4nVqk>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] MUST or SHOULD for Type 4 / 5 UUIDs?
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2016 11:01:10 -0000

--Apple-Mail=_3DA88FF0-4C5C-49E5-835C-622A370C0349
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I don=E2=80=99t see how having a MUST causes a backward compatibility =
issue. At the end of the day, a UUID is just a string of 32 characters =
and as long as that criteria is met, it really doesn=E2=80=99t matter =
how the string was generated. Any device following this draft would =
generate a Type 4 or 5 UUID and a pre-standard device might generate it =
in some other way and everything will work fine. We are specifically =
addressing how a behavior implementing this draft generates a UUID. An =
endpoint could end up using a non Type 4/5 UUID as a remote-uuid when =
interoperating with a pre-standard device, but the device following the =
standard is not generating the UUID in that case, so it is not violating =
the MUST clause in that case.

-Paul


> On Jun 2, 2016, at 3:01 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> Is there a reason we put SHOULD in section 4? Backward compatibility?
>=20
> Regards,
>=20
> Christer
>=20
>=20
> On 02/06/16 07:00, "insipid on behalf of Paul Giralt"
> <insipid-bounces@ietf.org on behalf of pgiralt@cisco.com> wrote:
>=20
>> INSIPID WG,
>>=20
>> Ben pointed out that we have an inconsistency in the draft. Section 4
>> states that endpoints SHOULD use Type 4 or Type 5 UUIDs when =
generating a
>> Session Identifier, however Section 12 states that Type 4 or 5 MUST =
be
>> used for privacy reasons.
>>=20
>> I=C2=B9m inclined to change the first to MUST and thereby require =
that only
>> Type 4 or Type 5 UUID=C2=B9s be used.
>>=20
>> Does anyone have an issue with this change?
>>=20
>> -Paul
>>=20
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
>=20


--Apple-Mail=_3DA88FF0-4C5C-49E5-835C-622A370C0349
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXUBHtAAoJEADWV7cDInKsAlcP/09WWJ817lAao2BGleXpBRM4
r0yGvkEL5OV/pevzqmUCnM/C4Qh8YcF1hrqRAqM0a/+KWhqkjHmWIN39bCQWi052
GR4c6cbnCW9dXg0qWweKesTWnqSRSoLXK8zAZi36inCkckU5KAZlPUjaVhB8DF2p
+fm5jTIFVFxD5zvIDamH+yHLVbn3yeNAHgN7Hb858YLF8EVZ8ResF76O213yguSY
WEZ8pliRWFeMRFGR8zdN6QoUz8wDqafxzeyPvPkCT8f02m99+RpFZ+ktIVt2mbs2
GMo5FjQSuFyi33J6tVB80aiZKAuzjuTYWCAPZc3+yhmfmvdfVNWnzW57WKB96MGB
K6Dk2jNPndNwE0WL8fDYMAiiEFy1Wj9mCKAh6olW0WENRq5rQ/8y6hX5Wlnf65pj
ku3wzNYO96hmoY/JL8v/SRQeCNQr7voRrGKcu7u8qI4VynAe7UhGGhTK5qztGqBS
MxtwwFyexQGatDBNrHrBJfxvOsX8uVkFtN4c71n98FWXuLFN7VMg1iEgRmhwpcmG
2zMfJdqd4GQZI6P8p7kblBTJPQYWrCLQpfZyoouYkYqVK6GcCoa7TEeNQ6fFJQDj
DXGn/2xiCKD2OJ9s1bZSrGMY7uSoCCpsQV2JFdI0xJSHYec4l70MNS90gVNl50tl
yQDsoMJcpD6oU9iCLam8
=CMZ5
-----END PGP SIGNATURE-----

--Apple-Mail=_3DA88FF0-4C5C-49E5-835C-622A370C0349--


From nobody Tue Jun  7 09:42:02 2016
Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EC8E12D0F3 for <insipid@ietfa.amsl.com>; Tue,  7 Jun 2016 09:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=broadsoft-com.20150623.gappssmtp.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 1zi-jDQtxFLC for <insipid@ietfa.amsl.com>; Tue,  7 Jun 2016 09:41:59 -0700 (PDT)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (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 80B0812D7CB for <insipid@ietf.org>; Tue,  7 Jun 2016 09:41:59 -0700 (PDT)
Received: by mail-it0-x229.google.com with SMTP id h190so19786527ith.1 for <insipid@ietf.org>; Tue, 07 Jun 2016 09:41:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadsoft-com.20150623.gappssmtp.com; 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; d=1e100.net; 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 10.36.82.72 with SMTP id d69mr5530771itb.3.1465317718795; Tue, 07 Jun 2016 09:41:58 -0700 (PDT)
From: Brett Tate <brett@broadsoft.com>
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: <6b8d81020946d1e12b87064387164e51@mail.gmail.com>
To: insipid@ietf.org, Paul Giralt <pgiralt@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/57BBjZ8G1bklACKMnNVN7YEBKk8>
Subject: Re: [Insipid] Requirement for Intermediaries to Update Session ID for other parties
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2016 16:42:01 -0000

Hi,

> 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=E2=80=99d 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 switc=
h
to an incorrect value.


From nobody Tue Jun  7 12:20:15 2016
Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D1B612D504 for <insipid@ietfa.amsl.com>; Tue,  7 Jun 2016 12:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 uJb5f2qpdIwy for <insipid@ietfa.amsl.com>; Tue,  7 Jun 2016 12:20:11 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5AD812D0C5 for <insipid@ietf.org>; Tue,  7 Jun 2016 12:20:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3637; q=dns/txt; s=iport; t=1465327211; x=1466536811; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=f3XGkGkl3o49IpkbppVPmk7ML3ciVRrZ9dnHelP2PGY=; b=kgH0FMMdue94VY8d34SK9QwgsVCmLYK4SOHpSKM2G4c8GDNUErLyBU96 9UZkmW63xuSn4nA30R81ILAAJLfBrdAievv+A7AOpq+Hz9Udg/86wFZbs GaCOrQMepbMa9zteh235H3PW7hgkqfwYYUoJIUTgBTdLueU32eUZIMhMd E=;
X-Files: signature.asc : 842
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AlBQC1HVdX/5xdJa1cgz6BWbpmgXmGE?= =?us-ascii?q?wKBQjoSAQEBAQEBAWUnhEYBAQMBI1YFCwIBCEICAjIlAQEEDhOIGQirYZEbAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEBDg6GJ4F3CIJOh0Ergi4FmEsBgy2BaYkQgWqNN?= =?us-ascii?q?oY9iSEBJQQrggIFHBaBNYl+fwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.26,434,1459814400";  d="asc'?scan'208";a="112588362"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Jun 2016 19:20:10 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u57JKADf015632 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 7 Jun 2016 19:20:10 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 7 Jun 2016 15:20:09 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1104.009; Tue, 7 Jun 2016 15:20:09 -0400
From: "Paul Giralt (pgiralt)" <pgiralt@cisco.com>
To: Brett Tate <brett@broadsoft.com>
Thread-Topic: [Insipid] Requirement for Intermediaries to Update Session ID for other parties
Thread-Index: AdHA2312D/wUckGRTgeNOtz38IHE2AAN6GUA
Date: Tue, 7 Jun 2016 19:20:09 +0000
Message-ID: <BB58EF31-8935-456E-9783-BBFCF418F472@cisco.com>
References: <6b8d81020946d1e12b87064387164e51@mail.gmail.com>
In-Reply-To: <6b8d81020946d1e12b87064387164e51@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.81.96.60]
Content-Type: multipart/signed; boundary="Apple-Mail=_FE932CE8-E3D0-4152-9BE1-4ECA61161778"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/k3iKGnfpZoF6RkkWI1CKE8oys-M>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] Requirement for Intermediaries to Update Session ID for other parties
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2016 19:20:13 -0000

--Apple-Mail=_FE932CE8-E3D0-4152-9BE1-4ECA61161778
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Brett,

Thanks for the reply. I have some comments / questions inline. I=E2=80=99m=
 not trying to be argumentative in my comments - I really just want to =
make sure we have a strong argument for SHOULD so really just want to =
make sure these reasons are valid.


>=20
>=20
> 1) A proxy can't really do it.
>=20

Would a proxy ever do anything that would require it do to it? A proxy =
will just be forwarding messages back and forth for the most part.


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

Why would they =E2=80=9Cnot want to=E2=80=9D?


> 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.
>=20


The potential for glare is a potentially good argument, but is =E2=80=9Cex=
tra messaging=E2=80=9D really an issue?


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


This doesn=E2=80=99t seem like a good reason not to try to update.


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


This is a good one, although I would think re-INVITE is always available =
(or whatever is being used for session refresh), so is there really ever =
a case where there is no way to do it? I noticed you said =E2=80=9Cwilling=
 to use=E2=80=9D which I=E2=80=99m sure you did intentionally. That =
doesn=E2=80=99t mean there is no way, but if there was a requirement, =
then they would have to.


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

Simplest way to update would be whatever message is being used for =
session refresh. That should not cause problems.


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


How would this happen?


> 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.


Why would this happen?


--Apple-Mail=_FE932CE8-E3D0-4152-9BE1-4ECA61161778
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXVx5pAAoJEADWV7cDInKsLC8QAIlocNrwzWht3ls+iBzsuDVv
xoqAYhf79bloskAiT4nGkqDMpg+eOcgmhwMKkGdn4KqE+Vw6dUXjZI7NiesvIYM6
L3Aa1rFtE/yn6+8jFaRZ0r5pAWxvM51awf+jBn7kxQlbk6uC54yi0EksFz1KZxgg
cEWlE62d6JFpN8iIIO3Z9HgSIhR+oANUv8Ke6ZiM8f3WC+sPN82qSO9kVE9IOwDJ
rWAg7LGOGnvT5HS79mq32X7DJ1UMGmalLqrlYnRuWtGF+ilhjNwC8pALzkexYgdg
st6rGjJdaGS3Vhiqlvx41uq5iX0pt+HhHNMrOKcCnTg1U9pvDxU0PH4ZHyFOw9aY
BUpAhmJFlMX8iwdKdAMrVcpElsGLbW+oeDSIB5Wtboqju2GbLKdNnE8UyrQ2OLXv
9Pf2E7hvmaLpg/5722PAH8dlnSBYv8GyU9HYmC5gB9h/c6lfSc5O5D3LU5mDQ5xT
X9sq8PWbvWxTZsGYGr8bD+NIenjwwmQPWQaTfZ4OyeYZWwpcKAI11gP9AkB2+Tgt
jctWW6TZXsDDBoOJ03e84QhjDtE83cBBflQa0LNFIZogkdSRnf6Up/uHQA0CcAFV
XPqmJmDdjB2Y7nF9exYnohWhihv3ZnZEssnMD9mJemMvcyiKiEtlQ4LxDnS7Exwx
Z40ua4m1yW1tMayltedI
=xz8t
-----END PGP SIGNATURE-----

--Apple-Mail=_FE932CE8-E3D0-4152-9BE1-4ECA61161778--


From nobody Tue Jun  7 15:06:03 2016
Return-Path: <ben@nostrum.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B283B12D5FC; Tue,  7 Jun 2016 15:06:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=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 TevxMaMORXSq; Tue,  7 Jun 2016 15:05:57 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 4600312D89B; Tue,  7 Jun 2016 15:05:57 -0700 (PDT)
Received: from [10.0.1.4] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u57M5rl2068964 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 7 Jun 2016 17:05:54 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.4]
From: "Ben Campbell" <ben@nostrum.com>
To: "Paul Giralt" <pgiralt@cisco.com>
Date: Tue, 07 Jun 2016 17:05:56 -0500
Message-ID: <6825ACBF-84F5-4BE9-86F1-ED0F7A1423BA@nostrum.com>
In-Reply-To: <B78C35A8-98FD-4B75-900D-86B4B098A519@cisco.com>
References: <D126986C-5821-4DD3-AB10-CD54B2387491@nostrum.com> <B78C35A8-98FD-4B75-900D-86B4B098A519@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/rbn7x18iyDAUt0GxrHsIa7biPJg>
Cc: insipid@ietf.org, draft-ietf-insipid-session-id.all@ietf.org
Subject: Re: [Insipid] AD Evaluation of draft-ietf-insipid-session-id-22
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2016 22:06:02 -0000

Thanks for the response. Some more comments inline. I removed sections 
that do not seem to need further comment.

Thanks!

Ben.

On 30 May 2016, at 22:27, Paul Giralt wrote:

[...]

>
> [PG] While the draft is SIP-specific, the Session Identifier defined 
> in the draft is designed to be multi-protocol (e.g. the H.323 
> implementation described in H.460.27). If you feel we should be more 
> clear that the document is SIP-specific, but the identifier is 
> designed to be multi-protocol, I can modify.

I think there is room for clarification in the abstract. Perhaps 
something along the lines of "While the identifier is intended to work 
across multiple protocols, this document describes its usage in SIP."

>
>
>> - General
>>
>> - 4.1, 2nd paragraph: Why is the requirement for version 4 or 5 UUIDs
>> only a SHOULD? It seems like we should really avoid any sort of
>> persistent identifies in the UUID. If we really need the SHOULD, 
>> please
>> describe when it might be reasonable to choose otherwise.
>>
>
>
> [PG] The WG agreed on this because of existing endpoints that might 
> want to implement Session-ID but are currently generating other 
> identifiers using other mechanisms such as using the device MAC 
> address. This statement clearly contradicts Section 12 as you pointed 
> out below, so one of the two needs to change. I welcome WG feedback as 
> to which direction would be best. I tend to agree that this should be 
> a MUST and we should make all endpoints use version 4 or 5. Then 
> again, even if an endpoint did not conform to this, everything would 
> still work fine.

I haven't seen any work group feedback. I suggest sending a separate 
email for just this issue to the working group list to propose changing 
this to a MUST, and see if anyone objects.

>
>
>> - 4.2, 2nd paragraph: "such as when a UA first initiates a SIP 
>> request,"
>>
>> Should that be a SIP INVITE request, or SIP dialog-initiating 
>> request?
>>
>
>
> [PG] Cloud be any dialog-initiating request.

Then I suggest s/initiates a SIP request/initiates a potentially 
dialog-initiating SIP request/


>
>
>> -- 2nd to last paragraph: Is there a normative statement elsewhere 
>> than
>> devices other than conference-focuses MUST NOT reuse UUIDs? (Also, 
>> the
>> MUST in this paragraph belongs with the section on MDUs. If this text
>> means to simply point out that the MDU section has this requirement,
>> then please state it descriptively here.)
>>
>

[...]


>> -- last paragraph: I'm a bit uncomfortable with making storage
>> completely out of scope, due to the potential "information-at-rest"
>> security or privacy implications. (I note that RFC7206 cites 6872 for
>> this purpose).
>>
>
>
> [PG] In looking at 6872  we could site it here as well; however, if 
> the Session-ID is obscured in logs at res, it defeat the whole purpose 
> of having the Session-ID in the first place as you would not be able 
> to use it for troubleshooting. 6872 doesn’t really seem to mandate 
> much of anything and just has a lot of SHOULDs. If you feel strongly 
> on this, we could put a note to 6872 and highlight the fact that 
> Session-ID should be maintained in logs at rest to be effectively used 
> as a troubleshooting tool.

I think that since 7206, which was intended to be the requirements for 
this draft, cites 6872 then the solution really needs to cite it as 
well.

Also, SHOULD _is_ a mandate. Just not quite as strong of a mandate as 
MUST. I think that, if there's any SHOULDs there that do not apply, then 
this draft needs to explain that and why. Changing the SHOULD use 
version 4 or 5 to a MUST will help here, but that's also worth 
mentioning.



>
>
>> - 6, paragraph 8: Has the working group discussed the privacy
>> implications of requiring an endpoint to keep the same UUID after a
>> redirect, refer, or INVITE-with-replaces? It may be that the peer and
>> intermediaries already know the source of the 2nd dialog is the same
>> that of the first, but I think it's a topic that needs some mention 
>> in
>> the text.
>>
>
>
> [PG] Yes, the privacy implications have been discussed at length. The 
> whole point of the Session ID to allow a call to be tracked. Yes, it 
> can open privacy concerns, since intermediaries can potentially figure 
> out who has been talking to whom and for how long but this is not 
> significantly different than looking at SIP signaling itself. If we do 
> not mandate the same UUID in the situations described above, you end 
> up losing the relationship between the two call legs which again 
> defeats the purpose of having the Session-ID in the first place.

If a user would prefer _not_ to be tracked across a transfer or 
redirect, is the UA allowed to ignore this? Or is the ability of a 
provider to track the call across dialogs assumed to outweigh the user's 
preference? (I suspect the answer is, if you don't want to be tracked, 
don't use the mechanism in the first place.)

But whatever the answer, this is a privacy tradeoff, and should be 
documented in the draft. As it is, I see the word privacy exactly once 
in version 22. That will be a red flag during the IESG evaluation. A 
privacy considerations would be helpful.

>
>
>> -- paragraph 10: Both the MAY and MUST seem incorrect here. The MAY 
>> is a
>> statement of fact, and the MUST is a description of rules elsewhere 
>> in
>> the draft. I suggest using descriptive language for both.
>>
>
> [PG] I believe the first MUST needs to stay, but agree that the second 
> MAY and MUST should use descriptive language. I will correct to:

You are correct. I mean the second MUST.

>
>    An endpoint MUST assume that the UUID value of the peer endpoint 
> may
>    change at any time due to service interactions.  Section 8 
> discusses
>    how endpoints must handle remote UUID changes.
>

That works for me.

>
>> -7, first paragraph: Does the assumption of no "special treatment" 
>> means
>> the intermediary  passing the session-id unchanged? Removes it? 
>> Either?
>>
>
>
> [PG] It could be either depending on what the particular intermediary 
> does with headers it does not understand. We should assume it could be 
> either.
>

A note to that effect would be helpful. (I think the implication is that 
this puts no requirements whatsoever on intermediaries--is that 
correct?)

>
>> -- 4th paragraph: What happens when a B2BUA that does not implement
>> session-id aggregates responses? If it passes through the peer UUIDs
>> unchanged, does anything break? Can the UAC be misled about the UUID 
>> of
>> the resulting peer?
>>
>
>
> [PG] The UAC should be able to handle this, although there is a 
> potential for out of order messages to cause the UAC to be using a 
> remote UUID that is out of sync, however even this condition should 
> sort itself out.

A note to that effect would be helpful.


[...]

>
>
>> -- 2nd to last paragraph: Why are the SHOULDs not MUSTs? Can you
>> describe situations in which one might reasonably not follow the
>> SHOULDs?
>>
>
>
> [PG] I can’t find any reason for the first SHOULD and think it 
> should probably be a MUST. The second SHOULD is related to other 
> comments below about whether or not an intermediary is required to 
> update other participants in a session if it knows that the 
> participant has an out of sync Session-ID. I’m inclined to make this 
> a MUST as well, however I’ve been told there was some feedback from 
> the WG that some might not want to generate additional SIP signaling 
> for the sole purpose of updating a Session-ID.
>
> Is there any WG opinion as to why this should remain a SHOULD instead 
> of a MUST?

As with the version 4 and 5 issue, it's probably worth sending a 
separate email to the working group proposing something. Otherwise this 
is buried in a long review and people may not notice it. (I also suggest 
making it clear what the choice will be if people don't respond.)

>
>
>> -- last paragraph: The first "MAY" seems like a statement of fact. Is
>> the 2nd MAY appropriate? That is, intermediary allowed to _not_ do 
>> this,
>> and let endpoints get out of sync?
>>
>
>
> [PG] The first MAY should be may. The second is related to the 
> previous comment. If we allow intermediaries to not update a 
> participant when the Session-ID changes, then this statement is 
> accurate (so currently the draft is consistent), however if we change 
> the above SHOULD to a MUST, then this must change as well.

Okay.

>
>
>> -8, last paragraph: Why is the SHOULD not a MUST? When might one
>> reasonably not follow it?
>
>
> [PG] This is also related to the above two comments.

Okay.

>
>
>>
>> -9, 2nd paragraph: Does this assume that the conference is new to 
>> each
>> subsequent MCU? That is, one would never use this approach to bridge 
>> two
>> existing conferences that already have their own UUIDs?
>>
>
>
> [PG] Yes, this assumes the conference is new to each subsequent MCU. 
> The case of two existing conferences is not addressed in the draft.

A note to that effect might be helpful.

>
>
>> - 10.3: Why doesn't the b2bua send a re-invite to update the uuid as 
>> in
>> the next example?
>>
>
> [PG] This again goes back to the fact that updating the UUID is 
> currently optional. That said, we do say that intermediaries SHOULD 
> update the UUID and regardless of what decision is made regarding the 
> mandate to update the UUID, I agree this example should still include 
> the update as a best-practice, so I will modify regardless.

I agree. Examples should follow the SHOULDs unless they exist for the 
purpose of illustrating a violation of a SHOULD :-)

[...]

>
>
>> - 10.7, first bullet: It seems highly unlikely that a 3pcc server 
>> would
>> not be dialog stateful.
>>
>
>
> [PG] I agree, but any harm in leaving as is? Are we just stating the 
> obvious and we can leave it out entirely?

I guess it doesn't hurt anything either way.

>
>
>> - 11: This section creates MUST level requirements for an 
>> implementation
>> to be backwards compatible with a pre-standard, proprietary version.
>> That seems to be a stretch. Did the working group really intend that 
>> an
>> implementation could not choose not to implement this section?
>>
>
> [PG] Yes, this was the intention. The pre-standard version is a bit 
> more than just proprietary.

Well, section 1 explicitly uses the word "proprietary". Maybe that needs 
to change?


> It is my understanding that the pre-standard version is included as 
> part of the 3GPP Release 9 specification and there are 4-5 million 
> devices that currently implement that version. The WG felt it was 
> important enough to mandate interoperability.

We can run with this as a MUST, but I won't be surprised if we get 
objections during IETF last call or IESG evaluation. It might be helpful 
to include a note to the effect that, even thought the legacy version 
was not standards-track, it was heavily implemented and adopted by other 
SDOs.

(My personal preference [which I will not try to push over working group 
consensus] would to include this sort of guidance non-normatively, where 
you say something the effect of "there's a lot of implementations of 
"there's a lot of deployed 7329 implementations; if you care do these 
things.")

>
>
>> -- 4th bullet: Wny isn't the presence or absence of remote-uuid
>> sufficient for responses?
>>
>
> [PG] Great question. Some implementations of the pre-standard version 
> would blindly copy the contents of the request’s Session-ID header 
> into the response, so if they were to receive a standard version that 
> contains the remote-uuid, they would echo it back. This is to deal 
> with this possibility.

Okay. (Out of curiosity, is that allowed by 7329?)

[...]




>
>
>> -- 3rd paragraph: Is there an impact if something tampers with or 
>> lies
>> about session-Id values?
>>
>
>
> [PG] The only impact would be the inability to easily troubleshoot the 
> call. There should be no impact to the ability to complete and 
> interact with the call. Does this bear mentioning?
>

No, probably not.


[...]


From nobody Tue Jun  7 15:08:46 2016
Return-Path: <ben@nostrum.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A08D912D5FC; Tue,  7 Jun 2016 15:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=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 1NK6HbWQIxIo; Tue,  7 Jun 2016 15:08:39 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 310F312D89C; Tue,  7 Jun 2016 15:08:39 -0700 (PDT)
Received: from [10.0.1.4] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u57M8bNS069213 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 7 Jun 2016 17:08:37 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.4]
From: "Ben Campbell" <ben@nostrum.com>
To: "Paul Giralt" <pgiralt@cisco.com>
Date: Tue, 07 Jun 2016 17:08:39 -0500
Message-ID: <EC6B103C-B24A-4A83-BF82-97821F1DFC6D@nostrum.com>
In-Reply-To: <6825ACBF-84F5-4BE9-86F1-ED0F7A1423BA@nostrum.com>
References: <D126986C-5821-4DD3-AB10-CD54B2387491@nostrum.com> <B78C35A8-98FD-4B75-900D-86B4B098A519@cisco.com> <6825ACBF-84F5-4BE9-86F1-ED0F7A1423BA@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/QH-ibkCqYzMDTpeVe-0JTtomFGA>
Cc: insipid@ietf.org, draft-ietf-insipid-session-id.all@ietf.org
Subject: Re: [Insipid] AD Evaluation of draft-ietf-insipid-session-id-22
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2016 22:08:41 -0000

Oops, I see now that you already sent a separate note to the list :-)

On 7 Jun 2016, at 17:05, Ben Campbell wrote:

> [PG] The WG agreed on this because of existing endpoints that might 
> want to implement Session-ID but are currently generating other 
> identifiers using other mechanisms such as using the device MAC 
> address. This statement clearly contradicts Section 12 as you pointed 
> out below, so one of the two needs to change. I welcome WG feedback as 
> to which direction would be best. I tend to agree that this should be 
> a MUST and we should make all endpoints use version 4 or 5. Then 
> again, even if an endpoint did not conform to this, everything would 
> still work fine.
>
>
> I haven't seen any work group feedback. I suggest sending a separate 
> email for just this issue to the working group list to propose 
> changing this to a MUST, and see if anyone objects.


From nobody Sun Jun 12 12:40:54 2016
Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CBB312D544; Sun, 12 Jun 2016 12:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 wiXlZ3JrUpit; Sun, 12 Jun 2016 12:40:50 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54E7612D12E; Sun, 12 Jun 2016 12:40:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13096; q=dns/txt; s=iport; t=1465760450; x=1466970050; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=F4S7sHdsTg7F4MO7LyWD/M+F9cdeVu5WgLZwZGQ1lOU=; b=Q5S1zp3HnFTCTtTNDKCMMw9GXNEFEEw3dj8aLI9nrmXUNG7mcuK+LxQe FlkNOvyC0t1YUHFgvt9i1+I3u23D9D7D405WsSyCgpZxXokurNItki0+r NqlqhSGdoXTXMYFaf268NiZ+dHYfic7fmpKL5im1pGprzUGNe92GyhDrK 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAgBkul1X/5xdJa1dgz6BU7skgXmGF?= =?us-ascii?q?wKBITgUAQEBAQEBAWUnhEoBAQEDAWgKBwULAgEIGC4yJQIECgQFG4gNCL0SAQE?= =?us-ascii?q?BAQEBAQECAQEBAQEBAQEfhieBdwiBS4EDhBIRAQYCFIMsgi8FmGEBiHuCcII8g?= =?us-ascii?q?WkXhDuIZYZIiSUBHjaCBxyBS26IRAEGCBeBHgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.26,462,1459814400"; d="scan'208";a="284597799"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jun 2016 19:40:48 +0000
Received: from XCH-RTP-018.cisco.com (xch-rtp-018.cisco.com [64.101.220.158]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u5CJemPQ000872 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 12 Jun 2016 19:40:48 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-018.cisco.com (64.101.220.158) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Sun, 12 Jun 2016 15:40:47 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1104.009; Sun, 12 Jun 2016 15:40:47 -0400
From: "Paul Giralt (pgiralt)" <pgiralt@cisco.com>
To: Ben Campbell <ben@nostrum.com>
Thread-Topic: [Insipid] AD Evaluation of draft-ietf-insipid-session-id-22
Thread-Index: AQHRuux59mLaRBKMoUa3UJTzWSDdnJ/e3rwAgAdwDQ4=
Date: Sun, 12 Jun 2016 19:40:47 +0000
Message-ID: <B3B45B68-4788-42B3-81A8-76A6A9C85342@cisco.com>
References: <D126986C-5821-4DD3-AB10-CD54B2387491@nostrum.com> <B78C35A8-98FD-4B75-900D-86B4B098A519@cisco.com>, <6825ACBF-84F5-4BE9-86F1-ED0F7A1423BA@nostrum.com>
In-Reply-To: <6825ACBF-84F5-4BE9-86F1-ED0F7A1423BA@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/pMFxQ1rzsNux-ae_q7NnX-Fh-NQ>
Cc: "insipid@ietf.org" <insipid@ietf.org>, "draft-ietf-insipid-session-id.all@ietf.org" <draft-ietf-insipid-session-id.all@ietf.org>
Subject: Re: [Insipid] AD Evaluation of draft-ietf-insipid-session-id-22
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jun 2016 19:40:52 -0000

Ben, thanks for the comments. I will address these concerns and publish an =
update to the draft.=20

-Paul

Sent from my iPhone

> On Jun 7, 2016, at 6:05 PM, Ben Campbell <ben@nostrum.com> wrote:
>=20
> Thanks for the response. Some more comments inline. I removed sections th=
at do not seem to need further comment.
>=20
> Thanks!
>=20
> Ben.
>=20
> On 30 May 2016, at 22:27, Paul Giralt wrote:
>=20
> [...]
>=20
>>=20
>> [PG] While the draft is SIP-specific, the Session Identifier defined in =
the draft is designed to be multi-protocol (e.g. the H.323 implementation d=
escribed in H.460.27). If you feel we should be more clear that the documen=
t is SIP-specific, but the identifier is designed to be multi-protocol, I c=
an modify.
>=20
> I think there is room for clarification in the abstract. Perhaps somethin=
g along the lines of "While the identifier is intended to work across multi=
ple protocols, this document describes its usage in SIP."
>=20
>>=20
>>=20
>>> - General
>>>=20
>>> - 4.1, 2nd paragraph: Why is the requirement for version 4 or 5 UUIDs
>>> only a SHOULD? It seems like we should really avoid any sort of
>>> persistent identifies in the UUID. If we really need the SHOULD, please
>>> describe when it might be reasonable to choose otherwise.
>>=20
>>=20
>> [PG] The WG agreed on this because of existing endpoints that might want=
 to implement Session-ID but are currently generating other identifiers usi=
ng other mechanisms such as using the device MAC address. This statement cl=
early contradicts Section 12 as you pointed out below, so one of the two ne=
eds to change. I welcome WG feedback as to which direction would be best. I=
 tend to agree that this should be a MUST and we should make all endpoints =
use version 4 or 5. Then again, even if an endpoint did not conform to this=
, everything would still work fine.
>=20
> I haven't seen any work group feedback. I suggest sending a separate emai=
l for just this issue to the working group list to propose changing this to=
 a MUST, and see if anyone objects.
>=20
>>=20
>>=20
>>> - 4.2, 2nd paragraph: "such as when a UA first initiates a SIP request,=
"
>>>=20
>>> Should that be a SIP INVITE request, or SIP dialog-initiating request?
>>=20
>>=20
>> [PG] Cloud be any dialog-initiating request.
>=20
> Then I suggest s/initiates a SIP request/initiates a potentially dialog-i=
nitiating SIP request/
>=20
>=20
>>=20
>>=20
>>> -- 2nd to last paragraph: Is there a normative statement elsewhere than
>>> devices other than conference-focuses MUST NOT reuse UUIDs? (Also, the
>>> MUST in this paragraph belongs with the section on MDUs. If this text
>>> means to simply point out that the MDU section has this requirement,
>>> then please state it descriptively here.)
>=20
> [...]
>=20
>=20
>>> -- last paragraph: I'm a bit uncomfortable with making storage
>>> completely out of scope, due to the potential "information-at-rest"
>>> security or privacy implications. (I note that RFC7206 cites 6872 for
>>> this purpose).
>>=20
>>=20
>> [PG] In looking at 6872  we could site it here as well; however, if the =
Session-ID is obscured in logs at res, it defeat the whole purpose of havin=
g the Session-ID in the first place as you would not be able to use it for =
troubleshooting. 6872 doesn=92t really seem to mandate much of anything and=
 just has a lot of SHOULDs. If you feel strongly on this, we could put a no=
te to 6872 and highlight the fact that Session-ID should be maintained in l=
ogs at rest to be effectively used as a troubleshooting tool.
>=20
> I think that since 7206, which was intended to be the requirements for th=
is draft, cites 6872 then the solution really needs to cite it as well.
>=20
> Also, SHOULD _is_ a mandate. Just not quite as strong of a mandate as MUS=
T. I think that, if there's any SHOULDs there that do not apply, then this =
draft needs to explain that and why. Changing the SHOULD use version 4 or 5=
 to a MUST will help here, but that's also worth mentioning.
>=20
>=20
>=20
>>=20
>>=20
>>> - 6, paragraph 8: Has the working group discussed the privacy
>>> implications of requiring an endpoint to keep the same UUID after a
>>> redirect, refer, or INVITE-with-replaces? It may be that the peer and
>>> intermediaries already know the source of the 2nd dialog is the same
>>> that of the first, but I think it's a topic that needs some mention in
>>> the text.
>>=20
>>=20
>> [PG] Yes, the privacy implications have been discussed at length. The wh=
ole point of the Session ID to allow a call to be tracked. Yes, it can open=
 privacy concerns, since intermediaries can potentially figure out who has =
been talking to whom and for how long but this is not significantly differe=
nt than looking at SIP signaling itself. If we do not mandate the same UUID=
 in the situations described above, you end up losing the relationship betw=
een the two call legs which again defeats the purpose of having the Session=
-ID in the first place.
>=20
> If a user would prefer _not_ to be tracked across a transfer or redirect,=
 is the UA allowed to ignore this? Or is the ability of a provider to track=
 the call across dialogs assumed to outweigh the user's preference? (I susp=
ect the answer is, if you don't want to be tracked, don't use the mechanism=
 in the first place.)
>=20
> But whatever the answer, this is a privacy tradeoff, and should be docume=
nted in the draft. As it is, I see the word privacy exactly once in version=
 22. That will be a red flag during the IESG evaluation. A privacy consider=
ations would be helpful.
>=20
>>=20
>>=20
>>> -- paragraph 10: Both the MAY and MUST seem incorrect here. The MAY is =
a
>>> statement of fact, and the MUST is a description of rules elsewhere in
>>> the draft. I suggest using descriptive language for both.
>>=20
>> [PG] I believe the first MUST needs to stay, but agree that the second M=
AY and MUST should use descriptive language. I will correct to:
>=20
> You are correct. I mean the second MUST.
>=20
>>=20
>>   An endpoint MUST assume that the UUID value of the peer endpoint may
>>   change at any time due to service interactions.  Section 8 discusses
>>   how endpoints must handle remote UUID changes.
>=20
> That works for me.
>=20
>>=20
>>> -7, first paragraph: Does the assumption of no "special treatment" mean=
s
>>> the intermediary  passing the session-id unchanged? Removes it? Either?
>>=20
>>=20
>> [PG] It could be either depending on what the particular intermediary do=
es with headers it does not understand. We should assume it could be either=
.
>=20
> A note to that effect would be helpful. (I think the implication is that =
this puts no requirements whatsoever on intermediaries--is that correct?)
>=20
>>=20
>>> -- 4th paragraph: What happens when a B2BUA that does not implement
>>> session-id aggregates responses? If it passes through the peer UUIDs
>>> unchanged, does anything break? Can the UAC be misled about the UUID of
>>> the resulting peer?
>>=20
>>=20
>> [PG] The UAC should be able to handle this, although there is a potentia=
l for out of order messages to cause the UAC to be using a remote UUID that=
 is out of sync, however even this condition should sort itself out.
>=20
> A note to that effect would be helpful.
>=20
>=20
> [...]
>=20
>>=20
>>=20
>>> -- 2nd to last paragraph: Why are the SHOULDs not MUSTs? Can you
>>> describe situations in which one might reasonably not follow the
>>> SHOULDs?
>>=20
>>=20
>> [PG] I can=92t find any reason for the first SHOULD and think it should =
probably be a MUST. The second SHOULD is related to other comments below ab=
out whether or not an intermediary is required to update other participants=
 in a session if it knows that the participant has an out of sync Session-I=
D. I=92m inclined to make this a MUST as well, however I=92ve been told the=
re was some feedback from the WG that some might not want to generate addit=
ional SIP signaling for the sole purpose of updating a Session-ID.
>>=20
>> Is there any WG opinion as to why this should remain a SHOULD instead of=
 a MUST?
>=20
> As with the version 4 and 5 issue, it's probably worth sending a separate=
 email to the working group proposing something. Otherwise this is buried i=
n a long review and people may not notice it. (I also suggest making it cle=
ar what the choice will be if people don't respond.)
>=20
>>=20
>>=20
>>> -- last paragraph: The first "MAY" seems like a statement of fact. Is
>>> the 2nd MAY appropriate? That is, intermediary allowed to _not_ do this=
,
>>> and let endpoints get out of sync?
>>=20
>>=20
>> [PG] The first MAY should be may. The second is related to the previous =
comment. If we allow intermediaries to not update a participant when the Se=
ssion-ID changes, then this statement is accurate (so currently the draft i=
s consistent), however if we change the above SHOULD to a MUST, then this m=
ust change as well.
>=20
> Okay.
>=20
>>=20
>>=20
>>> -8, last paragraph: Why is the SHOULD not a MUST? When might one
>>> reasonably not follow it?
>>=20
>>=20
>> [PG] This is also related to the above two comments.
>=20
> Okay.
>=20
>>=20
>>=20
>>>=20
>>> -9, 2nd paragraph: Does this assume that the conference is new to each
>>> subsequent MCU? That is, one would never use this approach to bridge tw=
o
>>> existing conferences that already have their own UUIDs?
>>=20
>>=20
>> [PG] Yes, this assumes the conference is new to each subsequent MCU. The=
 case of two existing conferences is not addressed in the draft.
>=20
> A note to that effect might be helpful.
>=20
>>=20
>>=20
>>> - 10.3: Why doesn't the b2bua send a re-invite to update the uuid as in
>>> the next example?
>>=20
>> [PG] This again goes back to the fact that updating the UUID is currentl=
y optional. That said, we do say that intermediaries SHOULD update the UUID=
 and regardless of what decision is made regarding the mandate to update th=
e UUID, I agree this example should still include the update as a best-prac=
tice, so I will modify regardless.
>=20
> I agree. Examples should follow the SHOULDs unless they exist for the pur=
pose of illustrating a violation of a SHOULD :-)
>=20
> [...]
>=20
>>=20
>>=20
>>> - 10.7, first bullet: It seems highly unlikely that a 3pcc server would
>>> not be dialog stateful.
>>=20
>>=20
>> [PG] I agree, but any harm in leaving as is? Are we just stating the obv=
ious and we can leave it out entirely?
>=20
> I guess it doesn't hurt anything either way.
>=20
>>=20
>>=20
>>> - 11: This section creates MUST level requirements for an implementatio=
n
>>> to be backwards compatible with a pre-standard, proprietary version.
>>> That seems to be a stretch. Did the working group really intend that an
>>> implementation could not choose not to implement this section?
>>=20
>> [PG] Yes, this was the intention. The pre-standard version is a bit more=
 than just proprietary.
>=20
> Well, section 1 explicitly uses the word "proprietary". Maybe that needs =
to change?
>=20
>=20
>> It is my understanding that the pre-standard version is included as part=
 of the 3GPP Release 9 specification and there are 4-5 million devices that=
 currently implement that version. The WG felt it was important enough to m=
andate interoperability.
>=20
> We can run with this as a MUST, but I won't be surprised if we get object=
ions during IETF last call or IESG evaluation. It might be helpful to inclu=
de a note to the effect that, even thought the legacy version was not stand=
ards-track, it was heavily implemented and adopted by other SDOs.
>=20
> (My personal preference [which I will not try to push over working group =
consensus] would to include this sort of guidance non-normatively, where yo=
u say something the effect of "there's a lot of implementations of "there's=
 a lot of deployed 7329 implementations; if you care do these things.")
>=20
>>=20
>>=20
>>> -- 4th bullet: Wny isn't the presence or absence of remote-uuid
>>> sufficient for responses?
>>=20
>> [PG] Great question. Some implementations of the pre-standard version wo=
uld blindly copy the contents of the request=92s Session-ID header into the=
 response, so if they were to receive a standard version that contains the =
remote-uuid, they would echo it back. This is to deal with this possibility=
.
>=20
> Okay. (Out of curiosity, is that allowed by 7329?)
>=20
> [...]
>=20
>=20
>=20
>=20
>>=20
>>=20
>>> -- 3rd paragraph: Is there an impact if something tampers with or lies
>>> about session-Id values?
>>=20
>>=20
>> [PG] The only impact would be the inability to easily troubleshoot the c=
all. There should be no impact to the ability to complete and interact with=
 the call. Does this bear mentioning?
>=20
> No, probably not.
>=20
>=20
> [...]


From nobody Tue Jun 14 11:08:34 2016
Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C49E512D880 for <insipid@ietfa.amsl.com>; Tue, 14 Jun 2016 11:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=broadsoft-com.20150623.gappssmtp.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 1dTpaGQbxR7R for <insipid@ietfa.amsl.com>; Tue, 14 Jun 2016 11:08:31 -0700 (PDT)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (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 338D412D881 for <insipid@ietf.org>; Tue, 14 Jun 2016 11:08:31 -0700 (PDT)
Received: by mail-qg0-x22c.google.com with SMTP id l44so88602874qgd.0 for <insipid@ietf.org>; Tue, 14 Jun 2016 11:08:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadsoft-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:thread-index:date:message-id:subject:to :content-transfer-encoding; bh=ypYilOZk9WRiRt90+b/iZfrSGlDnOstuJASyS8vhiuY=; b=2CnenrHO6CbE7H0Sg76HPOv+H+KjT38qWttwqOkIeDeQlVszwamoBH65f0t7DP6eiI k7gxA1gZGwWnb4ygC6IwYZQNCQcrr0gyMuigYqQmeB/MfYtsQBPKP2Q3zRQIEAfgq6Z9 DeraZj06wp4KFkJPN3MySiEM4Ww71KjGI/ed4bk6wPVSj1/nbuEs7jvpA3AqAePPMeID uiDgr8Wz++sCUcZgqPbr3NAKPWRaPcXdEe6P4BUNF2qyM2TIo2ypT7U3QpPwXeM3xmqM /4NN/6mMj6UrEjraFpekF2H6t35jGuQ81Hr2wwFLry6RRAT8XFzu9qY9GXaBXkCGcuCr P5Qg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:content-transfer-encoding; bh=ypYilOZk9WRiRt90+b/iZfrSGlDnOstuJASyS8vhiuY=; b=F6XHQ9DfO4YR9ri18hH01aGH5WV4sjyVi+NW2jBYVpXRk0zvqKpiuiXfdtNGzs2Oxa phBt+lr4GuqXosvmgtWb2RW6R9HRHUlEOprp2pdj1fNyLXfNaZbO1aiYxRykacIRB5pP ZOZ5rDTJ1itjHou/TWEQ1hwLies1QJwDGholq4Ltkyo5mWajKYCw91JCYQLEiTVAno1e 9dK2lwtWO7eJul0aROpQH785Q6MJpC8vACqB77DP4remE1Tvzb1qC/nGcoepLJWv9vmF UCj9+2N+4xzioNNX9LnY5HgHEaJNzfLrZP+iFos0f+t+EAE7PO73FfvXDb2IaTx6Gnmb ZMng==
X-Gm-Message-State: ALyK8tIS+ihT58QeflgYa2egSba9dY177mfCgzQdB868RRbCcCKWyBgHmmse1lrFt/XLeKriHzQfNn2s+VMdgHsS
X-Received: by 10.140.25.150 with SMTP id 22mr21077325qgt.34.1465927710093; Tue, 14 Jun 2016 11:08:30 -0700 (PDT)
From: Brett Tate <brett@broadsoft.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdHGZih5BiX31+N4TFqkNYiQW61mjw==
Date: Tue, 14 Jun 2016 14:08:29 -0400
Message-ID: <8caee4daa818f23c867a1bc7a742c063@mail.gmail.com>
To: insipid@ietf.org, "Paul Giralt (pgiralt)" <pgiralt@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/ysW5e__oNUGClPHrGvarQg-Uunc>
Subject: Re: [Insipid] Requirement for Intermediaries to Update Session ID for other parties
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2016 18:08:33 -0000

Hi,

Reply is inline.

> > 1) A proxy can't really do it.
>
> Would a proxy ever do anything that would require
> it do to it? A proxy will just be forwarding messages
> back and forth for the most part.

Concerning "ever do", the draft indicates "If an intermediary can
determine".  However, I'll assume that the draft isn't mandating a proxy to
morph into a B2BUA to satisfy the SHOULD (or proposed MUST).


> > 2) I assume proxy B2BUA's that only initiate BYE's
> > would not want to do it except when sending BYE.
>
> Why would they =E2=80=9Cnot want to=E2=80=9D?

Depending upon interpretation, it might require them to remain a B2BUA
longer than their current preference.  To avoid some of the impacts of
B2BUAs, some proxy B2BUAs want to act as proxy until (if ever) required to
morph into a B2BUA to release the call.  However, I'll assume that the draf=
t
isn't mandating a proxy to morph into a B2BUA to satisfy the SHOULD (or
proposed MUST) even though it might morph later for another reason.


> > 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.
>
> The potential for glare is a potentially good argument,
> but is =E2=80=9Cextra messaging=E2=80=9D really an issue?

If administrator disables compliance with the proposed mandate, I assume
that it wouldn't be because of "extra messaging" unless a highly involved
intermediary has a bug which causes the administrator controlled
intermediary to need to frequently initiate messaging 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.
>
> This doesn=E2=80=99t seem like a good reason not to try to update.

Concerning the proposed mandate, how many tries are mandated within a
session before a compliant intermediary can give up?


> > 5) Methods that the intermediary is willing to use
> > for the update might not be within the received Allow
> > header.
>
> This is a good one, although I would think re-INVITE is
> always available (or whatever is being used for session
> refresh), so is there really ever a case where there is
> no way to do it? I noticed you said =E2=80=9Cwilling to use=E2=80=9D
> which I=E2=80=99m sure you did intentionally. That doesn=E2=80=99t mean
> there is no way, but if there was a requirement, then
> they would have to.

I mentioned "willing to use" for two reasons.  One reason was because they
need to pick their poison; potential re-INVITE glare or potential change
loop.  The other reason is that the intermediary might not want to start
updating things while there is an outstanding request associated with the
session.


> > 6) It can cause the intermediary to be part of an
> > infinite change loop unless use re-INVITE without offer.
> >
>
> Simplest way to update would be whatever message is
> being used for session refresh. That should not cause
> problems.

If receive new UUID within response, you need to update other side; if you
receive new UUID within response, you need to update other side; repeat;
repeat; ...


> > 7) The intermediary might not have auth credentials
> > to allow the change to be successful.
>
> How would this happen?

Not all intermediaries have auth credentials to act as both endpoints withi=
n
the session.

Speaking of authentication, what is the proposed mandate concerning ACK for
failed authentication?  It sounds like the proposal could force a compliant
device to initiate additional messaging if the attacker supplies different
remote UUID within the ACK (i.e. intermediary notices that attacker's side
is not using the current/correct UUID).


> > 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.
>
> Why would this happen?

"Because of race conditions and other things"


From nobody Thu Jun 23 21:37:53 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: insipid@ietf.org
Delivered-To: insipid@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BE6D712D1CB; Thu, 23 Jun 2016 21:37:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160624043751.12660.23306.idtracker@ietfa.amsl.com>
Date: Thu, 23 Jun 2016 21:37:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/7Gffn8fwC-ULDs6VstpCD7wdpZE>
Cc: insipid@ietf.org
Subject: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2016 04:37:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the INtermediary-safe SIP session ID of the IETF.

        Title           : End-to-End Session Identification in IP-Based Multimedia Communication Networks 
        Authors         : Paul E. Jones
                          Gonzalo Salgueiro
                          Chris Pearce
                          Paul Giralt
	Filename        : draft-ietf-insipid-session-id-23.txt
	Pages           : 40
	Date            : 2016-06-23

Abstract:
   This document describes an end-to-end Session Identifier for use in
   IP-based multimedia communication systems that enables endpoints,
   intermediary devices, and management systems to identify a session
   end-to-end, associate multiple endpoints with a given multipoint
   conference, track communication sessions when they are redirected,
   and associate one or more media flows with a given communication
   session.  While the identifier is intended to work across multiple
   protocols, this document describes its usage in SIP.

   This document also describes a backwards compatibility mechanism for
   an existing session identifier implementation (RFC 7329) that is
   sufficiently different from the procedures defined in this document.

   This document obsoletes RFC 7329.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-insipid-session-id-23

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-insipid-session-id-23


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Jun 24 08:48:30 2016
Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F19A12DBC2 for <insipid@ietfa.amsl.com>; Fri, 24 Jun 2016 08:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 RuWEEsBkNN4a for <insipid@ietfa.amsl.com>; Fri, 24 Jun 2016 08:48:28 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE21812DAE9 for <insipid@ietf.org>; Fri, 24 Jun 2016 08:48:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3794; q=dns/txt; s=iport; t=1466783307; x=1467992907; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=czsanab7M6zk8tlWpL2B2x/RgdATERbpQKThRBD9hAc=; b=cb90pEizpY39Z/8t/k6cYBM7E9zstBEkvxczM++iKPj6GAGOR5F4vju1 14IKySB8EaAwIDquzbP72m+BD6b5Pm0TyqyHaTrPzxg8iKN8IUdS8mfPy PZ5YAgjxyNKuRTS86HkdxATk97MzyPpqbjE/7l5/3kdi8LdkGfK1nEHpA k=;
X-Files: signature.asc : 842
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAgBXVW1X/5JdJa1SCgGDPVZ9Brogg?= =?us-ascii?q?XsXC4UsSgKBMjgUAQEBAQEBAWUnhEwBAQEDAQEBASBFBgsFCwIBCBgqAgInCyU?= =?us-ascii?q?CBA4FDogaCA62UJA0AQEBAQEBAQEBAQEBAQEBAQEBAQEBDg6GKIF3glaEGGaCQ?= =?us-ascii?q?yuCLwWZAAGDLYFsbogsgWlOhAWIZ499AR42g3BuiDF/AQEB?=
X-IronPort-AV: E=Sophos;i="5.26,521,1459814400";  d="asc'?scan'208";a="289731288"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Jun 2016 15:48:26 +0000
Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u5OFmQoN021993 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 24 Jun 2016 15:48:26 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 24 Jun 2016 11:48:25 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1104.009; Fri, 24 Jun 2016 11:48:25 -0400
From: "Paul Giralt (pgiralt)" <pgiralt@cisco.com>
To: Ben Campbell <ben@nostrum.com>
Thread-Topic: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
Thread-Index: AQHRzdIv8M2blTO35k+l2Gt9c0ch+5/5BxMA
Date: Fri, 24 Jun 2016 15:48:25 +0000
Message-ID: <99E92338-11D2-404C-BEC7-EDEB9B0C2792@cisco.com>
References: <20160624043751.12660.23306.idtracker@ietfa.amsl.com>
In-Reply-To: <20160624043751.12660.23306.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.81.96.60]
Content-Type: multipart/signed; boundary="Apple-Mail=_07C278AA-FC7A-49B0-B565-D43D92703A98"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/zLY6mmnv5DacLiq--l4dkaMJ8wY>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2016 15:48:29 -0000

--Apple-Mail=_07C278AA-FC7A-49B0-B565-D43D92703A98
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Ben,

I=E2=80=99m hoping this version of the draft addresses your concerns. =
Please let me know your thoughts on the latest changes.

Thanks,
-Paul

> On Jun 24, 2016, at 12:37 AM, internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the INtermediary-safe SIP session ID of =
the IETF.
>=20
>        Title           : End-to-End Session Identification in IP-Based =
Multimedia Communication Networks
>        Authors         : Paul E. Jones
>                          Gonzalo Salgueiro
>                          Chris Pearce
>                          Paul Giralt
> 	Filename        : draft-ietf-insipid-session-id-23.txt
> 	Pages           : 40
> 	Date            : 2016-06-23
>=20
> Abstract:
>   This document describes an end-to-end Session Identifier for use in
>   IP-based multimedia communication systems that enables endpoints,
>   intermediary devices, and management systems to identify a session
>   end-to-end, associate multiple endpoints with a given multipoint
>   conference, track communication sessions when they are redirected,
>   and associate one or more media flows with a given communication
>   session.  While the identifier is intended to work across multiple
>   protocols, this document describes its usage in SIP.
>=20
>   This document also describes a backwards compatibility mechanism for
>   an existing session identifier implementation (RFC 7329) that is
>   sufficiently different from the procedures defined in this document.
>=20
>   This document obsoletes RFC 7329.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-insipid-session-id-23
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-insipid-session-id-23
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


--Apple-Mail=_07C278AA-FC7A-49B0-B565-D43D92703A98
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXbVZJAAoJEADWV7cDInKsXxkP/0FjoT0G9q1Kq7I48tMLbIqY
u+Lxr2jD6maOYENkaZIZw7kTcOWi5v8Z0S0Fe3T2saKCBra6w5ZutvL7Msft/28P
vzKFM521kvxMiJegwqyJ+wZdGn0GD4PXykvpg4+pYGKuDKBlhL41yU37yrhHrigu
wVfRX+tyjmHdI8jBvt9IzU2NFdy5SHS/HOJkk/7naO3Q9+7uTcqVHg6sPnoO9MYC
pKrQ1t6Svz6Bz6ETawNNP2PPwM0cadHVaF+XlFGZCtGwrPApNgfvVfKEYw5u2VpG
fTU1Z8+//KpZg4yACOUsHZD5+6ZMqovVoxNURE2NRf3q45a4lC3Gd7ygWzYYPCYV
ps1GawGYNqf05uT2pz3V6q9UBet284J6eiSzh3Cmp5UdJAKdJyuDp370RVx4H8Sh
4z5CL0FcXZG5tE50/tmFdRfrvPmA2Zo10rXL/Qz5VzCWxahxBmRuBW+PXgwsS9DH
3z/+bk/SVlwca/MoovoKtInH55xxhcoa2e7zqW+Q0BFSFR7iyG0HVXopXwjUqygo
zwYla8lDrD21kbZBuKH9cj16EGt1xU8kup3IVBSkh39cF1F/6z04Wfpg8pl6oIMD
D6tvwZXcCYlof0F93Brse+y/KzLrCDyQvjXbv4zUp/Z+x1Erpz+Hsia1X3dyK6fi
KkqyDPFOjkBZOMZS/OG4
=aAp3
-----END PGP SIGNATURE-----

--Apple-Mail=_07C278AA-FC7A-49B0-B565-D43D92703A98--


From nobody Mon Jun 27 14:57:29 2016
Return-Path: <ben@nostrum.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A806312D8C2 for <insipid@ietfa.amsl.com>; Mon, 27 Jun 2016 14:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=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 5LWXqVFkJee8 for <insipid@ietfa.amsl.com>; Mon, 27 Jun 2016 14:57:25 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 07F2D12D993 for <insipid@ietf.org>; Mon, 27 Jun 2016 14:57:25 -0700 (PDT)
Received: from [10.0.1.4] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u5RLvKWn093728 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 27 Jun 2016 16:57:20 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.4]
From: "Ben Campbell" <ben@nostrum.com>
To: "Paul Giralt" <pgiralt@cisco.com>
Date: Mon, 27 Jun 2016 16:57:25 -0500
Message-ID: <48BA34F8-5D0A-4597-A3FA-D9E8392F4323@nostrum.com>
In-Reply-To: <99E92338-11D2-404C-BEC7-EDEB9B0C2792@cisco.com>
References: <20160624043751.12660.23306.idtracker@ietfa.amsl.com> <99E92338-11D2-404C-BEC7-EDEB9B0C2792@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/1TQkoe_TLKkVz6CF9rVfxhlKInM>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2016 21:57:28 -0000

Hi Paul,

That version mostly addresses my concerns. I have a couple of comments 
about the updated section 12:

- The text states that, since the session-IDs must not contain device or 
user identifying information, they have no privacy considerations. That 
sort of statement is a bit of a red flag during IESG review. In 
particular, it would be good to also say something about the use of a 
session-ID as a persistent identifier to correlate across session. As it 
is, 4.2 says they generate a new, previously unused UUID. Is there any 
normative text about reusing the UUID for more than one "session"? (Not 
counting the text about transfers, etc.).

- The statement that session-id "MUST NOT be used for billing purposes" 
will probably draw objections. I suggest that be changed ot "is not 
appropriate for billing purposes." (Not really new text, but the 
revisions drew my attention to it.)

Thanks!

Ben.

On 24 Jun 2016, at 10:48, Paul Giralt (pgiralt) wrote:

> Ben,
>
> I’m hoping this version of the draft addresses your concerns. Please 
> let me know your thoughts on the latest changes.
>
> Thanks,
> -Paul
>
>> On Jun 24, 2016, at 12:37 AM, internet-drafts@ietf.org wrote:
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories.
>> This draft is a work item of the INtermediary-safe SIP session ID of 
>> the IETF.
>>
>>        Title           : End-to-End Session Identification in 
>> IP-Based Multimedia Communication Networks
>>        Authors         : Paul E. Jones
>>                          Gonzalo Salgueiro
>>                          Chris Pearce
>>                          Paul Giralt
>> 	Filename        : draft-ietf-insipid-session-id-23.txt
>> 	Pages           : 40
>> 	Date            : 2016-06-23
>>
>> Abstract:
>>   This document describes an end-to-end Session Identifier for use in
>>   IP-based multimedia communication systems that enables endpoints,
>>   intermediary devices, and management systems to identify a session
>>   end-to-end, associate multiple endpoints with a given multipoint
>>   conference, track communication sessions when they are redirected,
>>   and associate one or more media flows with a given communication
>>   session.  While the identifier is intended to work across multiple
>>   protocols, this document describes its usage in SIP.
>>
>>   This document also describes a backwards compatibility mechanism 
>> for
>>   an existing session identifier implementation (RFC 7329) that is
>>   sufficiently different from the procedures defined in this 
>> document.
>>
>>   This document obsoletes RFC 7329.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/
>>
>> There's also a htmlized version available at:
>> https://tools.ietf.org/html/draft-ietf-insipid-session-id-23
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-insipid-session-id-23
>>
>>
>> Please note that it may take a couple of minutes from the time of 
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
>
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


From nobody Tue Jun 28 11:33:38 2016
Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3257012D552 for <insipid@ietfa.amsl.com>; Tue, 28 Jun 2016 11:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=broadsoft-com.20150623.gappssmtp.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 Hq6EH3-BbV2D for <insipid@ietfa.amsl.com>; Tue, 28 Jun 2016 11:33:34 -0700 (PDT)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 3240012D504 for <insipid@ietf.org>; Tue, 28 Jun 2016 11:33:34 -0700 (PDT)
Received: by mail-qk0-x22b.google.com with SMTP id t127so45815250qkf.1 for <insipid@ietf.org>; Tue, 28 Jun 2016 11:33:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadsoft-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:thread-index:date:message-id:subject:to; bh=d49kGF7Mms9+NvMO1rRVNwG7ug/alkv14AWxqD+T6b8=; b=u7DpvYIAwCPNcjUdHSkf8p7k8QvJd8vkd9al379jFoR/G/1DOBL9PcCeYDhumRV/8S SNpBVgpphCkNfO+Q+ca1EqD+z0vIeIVNkWpFXjL9UmXrQlQ2ml6pnAc0Rl33kJcKEyce c5krnKbpgnJKDtaQ0khbCsLpFynE8aluKVnH9HkfGR9K2kF1iWHx/0RdRArYSvifp/3P zQ1q2SMU50cnpkMaEf20AbMZqU2D0a9yNNQ8BcTnLNT3xy5po+3b9FcvZ+NaOzZoZ9Wq Jj6M7akr/WfUOnUSF4ENRkCMWOZiPtGLwoqhhMmDOWkuWFyGtKOC6D1+F8rahnH4tN8B 0ELA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to; bh=d49kGF7Mms9+NvMO1rRVNwG7ug/alkv14AWxqD+T6b8=; b=FAtxLa+SXA3ZXsPDJ8ZP1ENnQB95lRDtzPIHTkJtDuHxQDlrf6cRrmOfAtTtTZw/Q5 tJ9ZfZ5FxMhsDuJrWDihMZJTkcnXzDBJBxcXzO+oUFBBWldVm4Kgnw76kqn16mRNG2bh woHB3KkYaM3rFE/ezfry3Bl0NOmFvJUQHCSEAlBENugiq28R0dAL711G9wokq0+8We7S NWkx1cI5JSWDaQgPz8GMO24K6VAZ2F8kuNaYQ1bb8PWJhF8m6CdYeH00klfUZA8WWd3s YCx54HJpzh0zbha5pospJXrJragicIwbTZYGb+5xzAkc9ZwyK//C8+diEBSc6h8ylWRf AmWA==
X-Gm-Message-State: ALyK8tIl6JbT1svOoGGZe9Rb8e1jGBk7FYMtDhBe5IkYBjsB4jGt1m69yZQhZf3yysyT2HZR7ezvPMH97AL6044d
X-Received: by 10.55.138.67 with SMTP id m64mr4068694qkd.78.1467138813327; Tue, 28 Jun 2016 11:33:33 -0700 (PDT)
From: Brett Tate <brett@broadsoft.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdHRa3mN5MulHSFWQ++NJW6ws0igKA==
Date: Tue, 28 Jun 2016 14:33:32 -0400
Message-ID: <21575ee6e889d5d4fdd306e7ca579185@mail.gmail.com>
To: insipid@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/HO1foU0laMfCRNlXo1g3QoNuCms>
Subject: [Insipid] draft-ietf-insipid-session-id versus RFC 3323
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jun 2016 18:33:36 -0000

Hi,

Since the topic of privacy was raised... should the following snippet from
RFC 3323 cause the Session-ID to be removed by the privacy service?  If
not, why?  I thought I'd ask since Session-ID appears to be a
non-essential informational header.

RFC 3323 section 5.3:

"Note that the privacy service MUST remove any non-essential
informational headers that have been added by the user agent,
including the Subject, Call-Info, Organization, User-Agent, Reply-To
and In-Reply-To."

Thanks,
Brett


From nobody Tue Jun 28 13:07:25 2016
Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A4AD12D848 for <insipid@ietfa.amsl.com>; Tue, 28 Jun 2016 13:07:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 dbd8c1sYdh24 for <insipid@ietfa.amsl.com>; Tue, 28 Jun 2016 13:07:22 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CA8012D828 for <insipid@ietf.org>; Tue, 28 Jun 2016 13:06:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3218; q=dns/txt; s=iport; t=1467144383; x=1468353983; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=zObnH1TjMsjUU5RnPUP6E+6B7zvApbqoaxa1QD5nVOw=; b=kYVj72mWa7yZnjieSUFloycC3jmbB/8flfCpvAfTH+45fPlNfVWiagsH aTkM1hhXQg1mHwfFJQwX768USMgYgV4I7XUwkWipbf58bj2mnpTwkInUd zKG2peyUveVx2hjFZMCzXjBfFgDxD6Rpk7j0WS7z+ZWSdF7kRjvBXJv6w Q=;
X-Files: signature.asc : 842
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A1AgAG2HJX/49dJa1bgz6BWborgXuGG?= =?us-ascii?q?AKBNDgUAQEBAQEBAWUnhE0BAQMBI1YFCwIBCEICAjIlAgQKBBOIGgizbJAwAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEBDg6GKIF3CIJOhBGDMCuCLwWGBJJ+AYMtgWyGV?= =?us-ascii?q?4JJjySPfgEeNoIIHIFMiR9/AQEB?=
X-IronPort-AV: E=Sophos;i="5.26,542,1459814400";  d="asc'?scan'208";a="291107378"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Jun 2016 20:06:22 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u5SK6M8b007650 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 28 Jun 2016 20:06:22 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 28 Jun 2016 16:06:21 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1210.000; Tue, 28 Jun 2016 16:06:21 -0400
From: "Paul Giralt (pgiralt)" <pgiralt@cisco.com>
To: Ben Campbell <ben@nostrum.com>
Thread-Topic: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
Thread-Index: AQHRzdIv8M2blTO35k+l2Gt9c0ch+5/5BxMAgAUeHYCAAXNIgA==
Date: Tue, 28 Jun 2016 20:06:21 +0000
Message-ID: <22D19CAA-9CF5-4666-8839-20568FE3B35B@cisco.com>
References: <20160624043751.12660.23306.idtracker@ietfa.amsl.com> <99E92338-11D2-404C-BEC7-EDEB9B0C2792@cisco.com> <48BA34F8-5D0A-4597-A3FA-D9E8392F4323@nostrum.com>
In-Reply-To: <48BA34F8-5D0A-4597-A3FA-D9E8392F4323@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.81.96.60]
Content-Type: multipart/signed; boundary="Apple-Mail=_44C67915-BCC7-43E5-AF23-057304BC8FA6"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/Rioxui94CaS72ThHj_dBJt5_MGE>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jun 2016 20:07:24 -0000

--Apple-Mail=_44C67915-BCC7-43E5-AF23-057304BC8FA6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Ben,

Thanks for the guidance. See inline=E2=80=A6


> - The text states that, since the session-IDs must not contain device =
or user identifying information, they have no privacy considerations. =
That sort of statement is a bit of a red flag during IESG review. In =
particular, it would be good to also say something about the use of a =
session-ID as a persistent identifier to correlate across session.


Ok - I will fix this.


> As it is, 4.2 says they generate a new, previously unused UUID. Is =
there any normative text about reusing the UUID for more than one =
"session"? (Not counting the text about transfers, etc.).


The only the only text  is Section 6 which describes the conditions =
under which the UUID is maintained. The transfer / redirect cases are =
the only time a UUID is =E2=80=9Creused=E2=80=9D and even then, it=E2=80=99=
s not really being reused for a different =E2=80=9Csession=E2=80=9D but =
that depends on what you fine as being a session. That may be the issue =
- that we don=E2=80=99t clearly define what a session is.

I added an additional line at the end of paragraph 1 in section 4.2 to =
highlight the persistence of the UUID mentioned in Section 6:

	Section 6 describes how the UUIDs selected by the source and =
destination UAs persist
        for the duration of the session.

Not sure if that=E2=80=99s necessary, but I figured it can=E2=80=99t =
hurt.

Would it help if we give a clearer definition of what a =E2=80=9Csession=E2=
=80=9D means in the context of this specification?

>=20
> - The statement that session-id "MUST NOT be used for billing =
purposes" will probably draw objections. I suggest that be changed ot =
"is not appropriate for billing purposes." (Not really new text, but the =
revisions drew my attention to it.)
>=20


Ok - fixed.


> Thanks!
>=20
> Ben.


--Apple-Mail=_44C67915-BCC7-43E5-AF23-057304BC8FA6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXcti9AAoJEADWV7cDInKs5yUP/0yFDWeXxnso6ovmLJU8oNKT
/5HAQfiL2Gv2/SzSfe73xTzebfRZxMGYvVfqSaEhVCtKAwZyEhzbmXgTzTKXh1qv
kgszFu7HbZ9ElTD/fi1fvhLAuNGQOgbBS1GZr7dWIJZjadQZyFDOcOBJSJxFyWU9
RtBQw2RcGHU29TtGcUIKMkGAnG6udZ957B7p6MA6e2T3hyzGlK8AwetW33DkbyIx
uVBH7zAex2Af+x1cjmuQEF0vbdlMr3v/KRZzgB/RbTMg+BY/qt2xcGTagak88Qxn
qlaQyXMu1Sl3qd3m0wrIZy7PxL4csV3QMFuKrhNGbGpiFL1guQbb/niorB8FQ9Ce
i42aclwChG6Zr5D7n3fYzr3z96HHVG5++vez65CPFHPq0QVMoFaKuvVLxKBiXITT
fcksZJvjxJL+GnYYvciQSSVwbZs2hE2B3LXOQ3O18sJ2qmDvL2UJV0VISF/GtqzB
E2FwEHR6JF6ak2asMe9MbmdiY4LctgUaci/DB/ORyH7Yp1cBDUINvn2IlXFrYvPj
XV38FzJ8PQxCYlrhA77Bh9iGPYu1S25IffQVfbdvMJfEUWZrQryqJvfX7HAnkGg/
ePk4AuGlwo2MtwHMMEZ/6q9NK+5q30v4HUPOjphnaHsW3uiaVGxAnyt/LYR2dkju
hhPWAizjM6/3skrJCHaM
=jsmZ
-----END PGP SIGNATURE-----

--Apple-Mail=_44C67915-BCC7-43E5-AF23-057304BC8FA6--


From nobody Tue Jun 28 18:59:24 2016
Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6BFE12B049 for <insipid@ietfa.amsl.com>; Tue, 28 Jun 2016 18:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 A1ZR2jgBg3Ta for <insipid@ietfa.amsl.com>; Tue, 28 Jun 2016 18:59:20 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A972B12B031 for <insipid@ietf.org>; Tue, 28 Jun 2016 18:59:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3826; q=dns/txt; s=iport; t=1467165560; x=1468375160; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=vDjzxornxREf6IEhRYWJYRkxfEkbhUWVWye3vOycopM=; b=NUYWjJTEfeVBP+/q34SKCBuEM3BlL+E5duSWw7qlWuxmTQ/nn4/bZTky qXuvpMXpebH0QaoGwNbVhbdExQm1aNyqQfQk5M+UbEoeryMih2pON7vep 5u+IQOCrVnIDq7p8Y6EwbIhWu0Q+9pKMiaF+ks5HS96b0pq71ASLxZEa4 M=;
X-Files: signature.asc : 842
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ABAgBDKnNX/40NJK1bgz5WfQa6NoF7F?= =?us-ascii?q?wuFLEoCgTM4FAEBAQEBAQFlJ4RMAQEBAwEBAQEgSwQHBQsCAQgYKgICJwslAQE?= =?us-ascii?q?EDgUOiBoIDrNFkC8BAQEBAQEBAQEBAQEBAQEBAQEBAQEOCQWGKIF3CIJOgTmGC?= =?us-ascii?q?CuCLwWZAwGDLYFsiSGPJZAAAR42ghWBW26IP38BAQE?=
X-IronPort-AV: E=Sophos;i="5.26,543,1459814400";  d="asc'?scan'208";a="291313570"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Jun 2016 01:59:19 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u5T1xJdS027699 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 Jun 2016 01:59:19 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 28 Jun 2016 21:59:18 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1210.000; Tue, 28 Jun 2016 21:59:18 -0400
From: "Paul Giralt (pgiralt)" <pgiralt@cisco.com>
To: Brett Tate <brett@broadsoft.com>
Thread-Topic: [Insipid] draft-ietf-insipid-session-id versus RFC 3323
Thread-Index: AdHRa3mN5MulHSFWQ++NJW6ws0igKAAX+N8A
Date: Wed, 29 Jun 2016 01:59:18 +0000
Message-ID: <D98EFE31-60FF-4038-8D81-36572B4A39CF@cisco.com>
References: <21575ee6e889d5d4fdd306e7ca579185@mail.gmail.com>
In-Reply-To: <21575ee6e889d5d4fdd306e7ca579185@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.123.194]
Content-Type: multipart/signed; boundary="Apple-Mail=_656DEF00-717F-44B5-A3A4-145C4D3CBE76"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/Ex-hUDhlGzWJaOdBobzzFumBmjs>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] draft-ietf-insipid-session-id versus RFC 3323
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 01:59:23 -0000

--Apple-Mail=_656DEF00-717F-44B5-A3A4-145C4D3CBE76
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Brett,

Looking through RFC 3323, the one section you called out was the one I =
also noticed could potentially apply. The question then becomes whether =
or not the Session-ID header is both =E2=80=9Cnon-essential=E2=80=9D and =
=E2=80=9Cinformational=E2=80=9D. I would say it is largely =
informational, however whether it is essential or not depends on your =
definition of essential. Could it be considered =E2=80=9Cessential=E2=80=9D=
 for troubleshooting? Maybe not because you could troubleshoot without =
it - it would just be more difficult - but it is not absolutely =
necessary (essential). However, a customer may have some diagnostic =
infrastructure in place that relies on the presence of the Session-ID =
header in which case then it is essential for their tools to work.

Also, the Session-ID behaves similar to a Call-ID header and 3323 does =
not mandate that the privacy service modify the Call-ID header (it MAY) =
and even then, the reason it gives for modifying Call-ID is "since the =
Call-ID commonly contains a hostname or IP address corresponding to the =
originating client=E2=80=9D which the Session-ID header does not provide =
as the Session Identifier itself does not reveal any information about =
the user or device. It can only potentially reveal a relationship =
between two parts of a session.

Are there any examples of other headers that implementers of 3323 have =
not removed based on the clause in section 5.3? Do you have a strong =
opinion either way? I can see arguments for and against removing it, so =
I don=E2=80=99t have a strong opinion. Either way, does it bear =
mentioning in the Session-ID specification?

-Paul



> On Jun 28, 2016, at 2:33 PM, Brett Tate <brett@broadsoft.com> wrote:
>=20
> Hi,
>=20
> Since the topic of privacy was raised... should the following snippet =
from
> RFC 3323 cause the Session-ID to be removed by the privacy service?  =
If
> not, why?  I thought I'd ask since Session-ID appears to be a
> non-essential informational header.
>=20
> RFC 3323 section 5.3:
>=20
> "Note that the privacy service MUST remove any non-essential
> informational headers that have been added by the user agent,
> including the Subject, Call-Info, Organization, User-Agent, Reply-To
> and In-Reply-To."
>=20
> Thanks,
> Brett
>=20
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


--Apple-Mail=_656DEF00-717F-44B5-A3A4-145C4D3CBE76
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXcyt1AAoJEADWV7cDInKsJ3cP/0403USyJ6VACg37mdwyKQ6E
Fm7Csh0JmckjFY5xzx2lWb5U76vQ9nezkcoKCmVWlakkFNisRkK1A6UnnDoDoOpJ
ciUIe7rRi1htxSVCWikR/cxClfumlG6AZpyERtsKIUroW6YMOTGJ11/2lsnHFtOk
TfuJMNGWLRKhkVifwn8wVkNcJdoAbZBOgbMxeGaWSZmBSILXmRb1k8wTgtVMWnBJ
kdbQSlLXa63ffhjEJEGq7VIiyxN7D0DZ+IlEhXHm4W5kJZFZtax17R9/yxy9KI8F
4HQV76Sa8J87drodnL/Is2xhSk7ajSXX4s+FoN8Q+LTmAhpyU9v/Y0GzzHR0tlDz
Sbw+PuPJ2XnKREchZM3YxGfYqU3TVVhdtcHIBtsw/WW0bZsrbqT4qrKk8mye9/v1
B1rp9219jkmMr7ym4QvH4RAZe0jDOBWhz5/9j5yWy1J6+kbKNnqxCAJ7lqlvUtvM
pLzPreTw4FUF5ZpunsUNkXrwU34KwZoJlTp8iPZqrTeuHbFV4K31fZnPxqbSNbgY
XLso5v+99Fk9SpISIM6h1EByeIK+I5of+3NFx8U3qMmByVha8IluUf6d1uQ3Grix
NnIPynGkodejUPevRotPIGgOiW2EJ4yIzh5Uq8NftNWUhUTVVyf1/IhU0Y16up9i
8i8ZHHQDRocW3KYqbya3
=DEty
-----END PGP SIGNATURE-----

--Apple-Mail=_656DEF00-717F-44B5-A3A4-145C4D3CBE76--


From nobody Wed Jun 29 12:47:23 2016
Return-Path: <brett@broadsoft.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D91F212D1A7 for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 12:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=broadsoft-com.20150623.gappssmtp.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 Phcc4-377q9H for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 12:47:20 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::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 CA74C12B020 for <insipid@ietf.org>; Wed, 29 Jun 2016 12:47:19 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id q79so107498053qke.0 for <insipid@ietf.org>; Wed, 29 Jun 2016 12:47:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadsoft-com.20150623.gappssmtp.com; s=20150623; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:content-transfer-encoding; bh=KTsLcNZYuL94mB1DD3h49WJ6AKx3csrv+o3MaqdbiwU=; b=T2+fOXkcFmuZprIVVXFSnoLYiTXKZ5fJyioqZZoqcmZIWQWv/DjO8GaOiH+dMdsptL vEetZCnV6nLAa7fRISskwFLzO0s39+kcGM4C0R2/UlGEegOEjXbfi6UDHqv+mVdrqTUK GgnAtSZubczfFZtEAPf5u1VmuOS+h7jtiZVRPTNHD1OtnKEOYkDhWO6SVlR0ZKPF9nbO szpWg5+xwuV4Re6E5JwBloW/4e3rioT3MRyl5o4wvXcABZ8uRQN2EkVkdmoFknE7obxt x5s2TUp446gNdPWO3cz+YnhfwrSX59VB9b1HGoS8BdZV7K6PdZO9AUHKgB0HBPCwhu4L cuUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:content-transfer-encoding; bh=KTsLcNZYuL94mB1DD3h49WJ6AKx3csrv+o3MaqdbiwU=; b=RlcZIuy6u7gLEOsPZZ0gevaNgSdBfTy2vI++umGeQ8HEf9d0gtam0ysei3a9gzF/Nz KNSI6O1huouy948AX5PuZ7V8LfVnMTWfoy7hsMjyC67G06qz+6d8wxX83atVJMrgdGYW GNAS/rRKwQJlIX9cuou+i+DqQAxZYLmEsq7yOkYpTHRpQnZF9c2ll/T/QipViHU47j37 +vZ7s4OgLpCH5VZlN1YEZP8LLM5eR/9LhmJYAYXWmFVQr+zVj5+aZpbNQCNoA2SQIQWT uZtzsJrH/Fjr87m2P41YKN1RNNJaF9Xv0V+7uaG+rc3lUkNsbM5cAsdpc871YJh4QrOI IFVA==
X-Gm-Message-State: ALyK8tKtV8UFPLj0uf6IBcFcTsZBTVwcICWj4JNfOfxDnjAQInxveghWF0RWvBB4Dgctc5FveHHBKxfOvy1MFzO2
X-Received: by 10.55.6.148 with SMTP id 142mr12153752qkg.206.1467229638947; Wed, 29 Jun 2016 12:47:18 -0700 (PDT)
From: Brett Tate <brett@broadsoft.com>
References: <21575ee6e889d5d4fdd306e7ca579185@mail.gmail.com> <D98EFE31-60FF-4038-8D81-36572B4A39CF@cisco.com>
In-Reply-To: <D98EFE31-60FF-4038-8D81-36572B4A39CF@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJYHjEyn2HnOUIArFJ66fkofx5w4wEVOIbFnusWd3A=
Date: Wed, 29 Jun 2016 15:47:18 -0400
Message-ID: <fe19523ad1cfdc0d74894e5ac2902753@mail.gmail.com>
To: "Paul Giralt (pgiralt)" <pgiralt@cisco.com>, insipid@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/dZypicDrC-X8922WQjDZ4Yo_LoU>
Subject: Re: [Insipid] draft-ietf-insipid-session-id versus RFC 3323
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 19:47:22 -0000

Hi,

Thanks for the response; reply is inline.

> Could it be considered =E2=80=9Cessential=E2=80=9D for troubleshooting?
> Maybe not because you could troubleshoot without it - it
> would just be more difficult - but it is not absolutely
> necessary (essential). However, a customer may have some
> diagnostic infrastructure in place that relies on the
> presence of the Session-ID header in which case then
> it is essential for their tools to work.

I agree that some administrators might not want Session-ID to be removed.


> Are there any examples of other headers that
> implementers of 3323 have not removed based on the
> clause in section 5.3?

I assume that vendors have applied the concept in a variety of ways with
various degrees of configurability.


> Do you have a strong opinion either way?  I can see
> arguments for and against removing it, so I don=E2=80=99t have
> a strong opinion.

I also do not have a strong opinion.


> Either way, does it bear mentioning in the Session-ID
> specification?

Depending upon interpretation, draft-ietf-insipid-session-id and RFC 3323
have conflicting mandates.

If the working group desires a specific behavior, it should likely be
discussed within the draft if RFC 3323 causes an ambiguity or conflict with
the desired behavior.

If the intermediary removes the Session-ID, I assume that a different (or
maybe the same) intermediary might add a different Session-ID.

As usual, the topic of privacy related to lawful intercept doesn't need to
be discussed.  I assume that some vendors will implement conferenced lawful
intercept as not being a conference.


From nobody Wed Jun 29 12:56:16 2016
Return-Path: <ben@nostrum.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9384912D1C1 for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 12:56:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=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 StrwlIN7hCiS for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 12:56:14 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 4F59C12D0BC for <insipid@ietf.org>; Wed, 29 Jun 2016 12:56:14 -0700 (PDT)
Received: from [10.0.1.4] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u5TJu97G060075 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 29 Jun 2016 14:56:09 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.4]
From: "Ben Campbell" <ben@nostrum.com>
To: "Paul Giralt" <pgiralt@cisco.com>
Date: Wed, 29 Jun 2016 14:56:08 -0500
Message-ID: <77585AF0-736F-4BE7-B7D8-E1979A962B58@nostrum.com>
In-Reply-To: <22D19CAA-9CF5-4666-8839-20568FE3B35B@cisco.com>
References: <20160624043751.12660.23306.idtracker@ietfa.amsl.com> <99E92338-11D2-404C-BEC7-EDEB9B0C2792@cisco.com> <48BA34F8-5D0A-4597-A3FA-D9E8392F4323@nostrum.com> <22D19CAA-9CF5-4666-8839-20568FE3B35B@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/9aocKdF1Ba2DLvkhYwMfDRgCX-M>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 19:56:15 -0000

On 28 Jun 2016, at 15:06, Paul Giralt (pgiralt) wrote:


[...]

>> As it is, 4.2 says they generate a new, previously unused UUID. Is 
>> there any normative text about reusing the UUID for more than one 
>> "session"? (Not counting the text about transfers, etc.).
>
>
>
> The only the only text  is Section 6 which describes the conditions 
> under which the UUID is maintained. The transfer / redirect cases are 
> the only time a UUID is “reused” and even then, it’s not really 
> being reused for a different “session” but that depends on what 
> you fine as being a session. That may be the issue - that we don’t 
> clearly define what a session is.

That text talks about when the UUID MUST NOT change. I'm looking for 
text that says a UUID value MUST NOT be reused across multiple 
"sessions" (as sessions are defined in this draft.) The point is to 
avoid an accidentally persistent identifier that could be used to track 
user/UA activity across multiple sessions.

>
> I added an additional line at the end of paragraph 1 in section 4.2 to 
> highlight the persistence of the UUID mentioned in Section 6:
>
> 	Section 6 describes how the UUIDs selected by the source and 
> destination UAs persist
>         for the duration of the session.
>
> Not sure if that’s necessary, but I figured it can’t hurt.
>
> Would it help if we give a clearer definition of what a “session” 
> means in the context of this specification?

While additional clarity rarely hurts, I did not find the concept of 
session in the draft to be particularly confusing, even if it did go 
beyond conventional ideas of what constitutes a session in SIP.


From nobody Wed Jun 29 13:10:10 2016
Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA79012D681 for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 13:10:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.946
X-Spam-Level: 
X-Spam-Status: No, score=-15.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 iPhp6XzNUL7B for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 13:10:06 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C05A512B03D for <insipid@ietf.org>; Wed, 29 Jun 2016 13:10:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7337; q=dns/txt; s=iport; t=1467231006; x=1468440606; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=atFBJT5OJOC3TUqLPkDyxAsL4ah8SffU3PpOalCLCu0=; b=gsq1LssgMxOeBaRK1OZUyfiwqajLdBOhrMjCi48lqe/cJ5j/ACC4M9UC W5pkyMyEDny/QEL4vkbGpU1n4KIIWhvNcMPWLDuX9DfIretmd4BRFPeHS 4AP8CusPJJ7IB34VdVhisHfngcAJ8qwVdV3RV2q9VsUOxwTVM/PgssG+h o=;
X-Files: signature.asc : 842
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ArAgA8KnRX/4sNJK1bgnBOgVm0Q4UBg?= =?us-ascii?q?XuGGAKBMjgUAQEBAQEBAWUnhE0BAQMBI1YQAgEIQgICMiUCBA4TiBoIs3iQFgE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEBAQ4OhiiBdwiCToQqgxcrgi8FhgSTAQGDLYFsh?= =?us-ascii?q?liCTIFphFSIaJACAR42gggcgUyJN38BAQE?=
X-IronPort-AV: E=Sophos;i="5.26,548,1459814400";  d="asc'?scan'208,217";a="123277539"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Jun 2016 20:10:05 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u5TKA5GO027038 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 Jun 2016 20:10:05 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 29 Jun 2016 16:10:04 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1210.000; Wed, 29 Jun 2016 16:10:04 -0400
From: "Paul Giralt (pgiralt)" <pgiralt@cisco.com>
To: Ben Campbell <ben@nostrum.com>
Thread-Topic: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
Thread-Index: AQHRzdIv8M2blTO35k+l2Gt9c0ch+5/5BxMAgAUeHYCAAXNIgIABj38AgAAD4AA=
Date: Wed, 29 Jun 2016 20:10:04 +0000
Message-ID: <49633303-629D-4CE3-A691-72D4E886080F@cisco.com>
References: <20160624043751.12660.23306.idtracker@ietfa.amsl.com> <99E92338-11D2-404C-BEC7-EDEB9B0C2792@cisco.com> <48BA34F8-5D0A-4597-A3FA-D9E8392F4323@nostrum.com> <22D19CAA-9CF5-4666-8839-20568FE3B35B@cisco.com> <77585AF0-736F-4BE7-B7D8-E1979A962B58@nostrum.com>
In-Reply-To: <77585AF0-736F-4BE7-B7D8-E1979A962B58@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.81.96.60]
Content-Type: multipart/signed; boundary="Apple-Mail=_E2CBADF0-3C4A-4C2C-A842-1A5224ACB16E"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/KGBRAhOP3yHn7yB_Qp0iNKEkUxQ>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 20:10:09 -0000

--Apple-Mail=_E2CBADF0-3C4A-4C2C-A842-1A5224ACB16E
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_9A709319-6542-45D4-8D42-16E22B005340"


--Apple-Mail=_9A709319-6542-45D4-8D42-16E22B005340
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

>=20
> That text talks about when the UUID MUST NOT change. I'm looking for =
text that says a UUID value MUST NOT be reused across multiple =
"sessions" (as sessions are defined in this draft.) The point is to =
avoid an accidentally persistent identifier that could be used to track =
user/UA activity across multiple sessions.

I see where you are coming from now. I hadn=E2=80=99t payed attention to =
the fact that the text in 4.2 is not normative. Currently the section =
reads:

	The SIP User Agent (UA) initiating a new session by transmitting =
a SIP
         request ("Alice"), i.e., a User Agent Client (UAC), will create =
a new,
         previously unused, UUID and transmit that to the ultimate =
destination UA
         ("Bob").  Likewise, the destination UA ("Bob"), i.e., a User =
Agent Server (UAS),
         will create a UUID and transmit that to the first UA ("Alice").

If I just change the =E2=80=9Cwill=E2=80=9D to MUST and expand on the =
UAS also having to create a previously-unused UUID like below, does this =
address the concern?

	The SIP User Agent (UA) initiating a new session by transmitting =
a SIP
         request ("Alice"), i.e., a User Agent Client (UAC), MUST create =
a new,
         previously unused, UUID and transmit that to the ultimate =
destination UA
         ("Bob").  Likewise, the destination UA ("Bob"), i.e., a User =
Agent Server (UAS),
         MUST create a new, previously unused, UUID and transmit that to =
the
	first UA ("Alice").

Alternatively, I could add some normative text in Section 6 for endpoint =
behavior, but I think just modifying the above should address the =
concern. Please let me know your thoughts.

-Paul


--Apple-Mail=_9A709319-6542-45D4-8D42-16E22B005340
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">That text talks about when the UUID MUST NOT =
change. I'm looking for text that says a UUID value MUST NOT be reused =
across multiple "sessions" (as sessions are defined in this draft.) The =
point is to avoid an accidentally persistent identifier that could be =
used to track user/UA activity across multiple sessions.</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">I see where you are coming from now. I =
hadn=E2=80=99t payed attention to the fact that the text in 4.2 is not =
normative. Currently the section reads:&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>The SIP =
User Agent (UA) initiating a new session by transmitting a =
SIP&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;request =
("Alice"), i.e., a User Agent Client (UAC), will create a =
new,&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;previously unused, UUID and transmit that to the ultimate =
destination UA&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;("Bob"). &nbsp;Likewise, the destination UA ("Bob"), i.e., a User =
Agent Server (UAS),&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;will create a UUID and transmit that to the first UA =
("Alice"). &nbsp;</div></div><div class=3D""><br class=3D""></div><div =
class=3D"">If I just change the =E2=80=9Cwill=E2=80=9D to MUST and =
expand on the UAS also having to create a previously-unused UUID like =
below, does this address the concern?&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>The SIP =
User Agent (UA) initiating a new session by transmitting a =
SIP&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;request =
("Alice"), i.e., a User Agent Client (UAC), MUST create a =
new,&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;previously unused, UUID and transmit that to the ultimate =
destination UA&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;("Bob"). &nbsp;Likewise, the destination UA ("Bob"), i.e., a User =
Agent Server (UAS),&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;MUST create a new, previously unused, UUID and transmit =
that to the&nbsp;</div><div class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>first UA ("Alice"). =
&nbsp;</div></div><div class=3D""><br class=3D""></div><div =
class=3D"">Alternatively, I could add some normative text in Section 6 =
for endpoint behavior, but I think just modifying the above should =
address the concern. Please let me know your thoughts.&nbsp;</div><div =
class=3D""><br class=3D""></div><div class=3D"">-Paul</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_9A709319-6542-45D4-8D42-16E22B005340--

--Apple-Mail=_E2CBADF0-3C4A-4C2C-A842-1A5224ACB16E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXdCscAAoJEADWV7cDInKsh+MQAIywKldpA9OCi2SZIgxjaiUw
NSM+QDjhR7lbfZP4xCkaTTPGmL+q7m9kjoGa4O+An6thHqQ74k8kLttFUL6jHCpf
LpVisnea77B+kcGl2nhkZPH/foTG3JB1hNCOXof1u0PwQgjS9fNPNbzHqHmg4rM2
WQ/q/LnVB0JfBer5bd8+b4ZFD2jqZbQzu9StYZjsi4Y8z9/oBVZfi9yfsOoEvL4V
eBnDS3ybK34B4uj5HRoImIrXkyxg3wvJ1ocLbpOw+0A1UiwBYReCZEpsRQsMIjzM
3pIqGxYJ9DLG09d0og/TjgK2aK2DcH7NVxoXEHQeLZLf4JDVz3F6dECsuYdlTrwz
WXBEnKmRwqGL5Ehi/FQIQ1zHnJs9jFAVkFUSl4UpGCjYlUZTNeb1Ki3k7MQ7gWMO
BmWpPKz2kZMtRnYjhi+EGz448tY+U95ubVQesf5EJ68c3Z/nsD52W5IqYfb2OEM+
02fLQUDwbOQ0Pj13wgzdjgVcix4nLjA6PjsSO04CmKVpOEUXwm6RM7p13ChA+FdI
p41MAPMDgt30PmY6E3CnJNzeP4zX5wCoNrfkZ+Y7NJsVtXnc+WTv9/P/0rMAxkR9
UwlgIGjt8NGg8303bLJzY0g49+zfFgPhUOlCFGMndP4kSpWHOdaE7Xm5gRDZdM+q
0sZsoFRYuzPqa0ahHyQY
=hALw
-----END PGP SIGNATURE-----

--Apple-Mail=_E2CBADF0-3C4A-4C2C-A842-1A5224ACB16E--


From nobody Wed Jun 29 13:11:19 2016
Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDBEA12D684 for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 13:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 bDWvc62V9qmL for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 13:11:17 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C62112B03D for <insipid@ietf.org>; Wed, 29 Jun 2016 13:10:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3378; q=dns/txt; s=iport; t=1467231058; x=1468440658; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=InFNALGlIWCxd5dfI+w5a+tafYjljMYaIEcJADoQctY=; b=JYq3864WciEHrGwRK1IvdI25xlX0vXeOu0g9oniUf8ppApka0nnHo9wS jh8W2mRQeaaPvN0tNrEMJsV4/DNF8peaI8fjXdJpixNUDnk9oz7ybc2/C RlpG+njWhmPqf+HuikCEoCyuKBA3w1woLQWhcTDZrnL1qNjct+w2qhBYg 0=;
X-Files: signature.asc : 842
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D5AQDnKnRX/5tdJa1bgz6BUwa5RIF7h?= =?us-ascii?q?hgCgTI4FAEBAQEBAQFlJ4RMAQEBAwEjRREFCwIBCBgqAgIyJQEBBA4FDogaCLN?= =?us-ascii?q?4kBYBAQEBAQEBAQEBAQEBAQEBAQEBAQEODoYogXcIgk6BOYYIK4IvBZkFAYMtg?= =?us-ascii?q?WyJJI8lkAIBHjaCAxKBW26ISX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.26,548,1459814400";  d="asc'?scan'208";a="120443179"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2016 20:10:57 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u5TKAvWP004785 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 Jun 2016 20:10:57 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 29 Jun 2016 16:10:56 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1210.000; Wed, 29 Jun 2016 16:10:56 -0400
From: "Paul Giralt (pgiralt)" <pgiralt@cisco.com>
To: Brett Tate <brett@broadsoft.com>
Thread-Topic: [Insipid] draft-ietf-insipid-session-id versus RFC 3323
Thread-Index: AdHRa3mN5MulHSFWQ++NJW6ws0igKAAX+N8AACVNQwAAANMmgA==
Date: Wed, 29 Jun 2016 20:10:56 +0000
Message-ID: <0FD350E3-5964-44CC-A0B4-A894219757C4@cisco.com>
References: <21575ee6e889d5d4fdd306e7ca579185@mail.gmail.com> <D98EFE31-60FF-4038-8D81-36572B4A39CF@cisco.com> <fe19523ad1cfdc0d74894e5ac2902753@mail.gmail.com>
In-Reply-To: <fe19523ad1cfdc0d74894e5ac2902753@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.81.96.60]
Content-Type: multipart/signed; boundary="Apple-Mail=_95E142D8-B1A9-4A11-8046-74B044AD77A6"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/YnFaG4JUWbCbg8N8_ZAsn77ZOiA>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] draft-ietf-insipid-session-id versus RFC 3323
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 20:11:19 -0000

--Apple-Mail=_95E142D8-B1A9-4A11-8046-74B044AD77A6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thanks Brett. Let me see if perhaps I can add a mention in the Security =
and Privacy considerations section. As usual thanks for your insight and =
feedback.

-Paul

> On Jun 29, 2016, at 3:47 PM, Brett Tate <brett@broadsoft.com> wrote:
>=20
> Hi,
>=20
> Thanks for the response; reply is inline.
>=20
>> Could it be considered =E2=80=9Cessential=E2=80=9D for =
troubleshooting?
>> Maybe not because you could troubleshoot without it - it
>> would just be more difficult - but it is not absolutely
>> necessary (essential). However, a customer may have some
>> diagnostic infrastructure in place that relies on the
>> presence of the Session-ID header in which case then
>> it is essential for their tools to work.
>=20
> I agree that some administrators might not want Session-ID to be =
removed.
>=20
>=20
>> Are there any examples of other headers that
>> implementers of 3323 have not removed based on the
>> clause in section 5.3?
>=20
> I assume that vendors have applied the concept in a variety of ways =
with
> various degrees of configurability.
>=20
>=20
>> Do you have a strong opinion either way?  I can see
>> arguments for and against removing it, so I don=E2=80=99t have
>> a strong opinion.
>=20
> I also do not have a strong opinion.
>=20
>=20
>> Either way, does it bear mentioning in the Session-ID
>> specification?
>=20
> Depending upon interpretation, draft-ietf-insipid-session-id and RFC =
3323
> have conflicting mandates.
>=20
> If the working group desires a specific behavior, it should likely be
> discussed within the draft if RFC 3323 causes an ambiguity or conflict =
with
> the desired behavior.
>=20
> If the intermediary removes the Session-ID, I assume that a different =
(or
> maybe the same) intermediary might add a different Session-ID.
>=20
> As usual, the topic of privacy related to lawful intercept doesn't =
need to
> be discussed.  I assume that some vendors will implement conferenced =
lawful
> intercept as not being a conference.


--Apple-Mail=_95E142D8-B1A9-4A11-8046-74B044AD77A6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXdCtPAAoJEADWV7cDInKsY6UP+wb5Bn9D+XJjWluSu3TQKQDY
Fwl2j4hBCVHI+yh05jbZ2LanHSbfk+gepxbhQIcqEaG08YpneBmjpy/JrfWPOQ05
IG5RHS0xppX0V6WzQrQnDDiffi2XzybIOydhcb928DSxpA4cT8j9xs+eK3QCPVhu
t/FeFyJKPuE2sQq2f/OCLuriDYLm08dbLqhjyU2jtKQDfhKeXOWCXbBWz4UlVFWB
wjAxbW2Z58byub/0vOsl2xUzf8h0R47h3ANv5y09M7WLJj5/JUqNcYKjal6Vmvmy
62v3asY4TNIDejxLwV3xtGZN1mPXFcOKQoMIFYDjSpY8piA3OQIYzSycpdpiZnAj
dRyWjExZYibMOdGXhP0bUu5gLU0LzDRnwO3Z0EvZU3JWnkwL97VpflS0L4Mu8LeL
QtukzClgwe6bgZNAtTSFH1zGFsBtFitUg7nHBfQ2j0Lez32ouO2y6/l5ceWSGASn
O1hNldvokpEnMpxyYO4GYfczU5WfBzgnPwMO8rb1mSRRqnWLHrHCGlM/4sHaVJNB
kZU3OFVjghxz7tMw3y6ET7EQ9NHomBVpIEYhQk4k27oMNMBOiTytSFNHH79zkImb
/04CZGqYFM+u+qKEoLirgYgmrn8MNAaB2tfFrVyA5a8Z98LkZWTDBY7a0NoOOZTP
L6UdQwy1rbcOiCIvUq2p
=UNgA
-----END PGP SIGNATURE-----

--Apple-Mail=_95E142D8-B1A9-4A11-8046-74B044AD77A6--


From nobody Wed Jun 29 13:12:24 2016
Return-Path: <ben@nostrum.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F229412D684 for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 13:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=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 6b8HXbddHpOc for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 13:12:18 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 6EA4912D677 for <insipid@ietf.org>; Wed, 29 Jun 2016 13:12:18 -0700 (PDT)
Received: from [10.0.1.4] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u5TKCFGv061511 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 29 Jun 2016 15:12:15 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.4]
From: "Ben Campbell" <ben@nostrum.com>
To: "Paul Giralt" <pgiralt@cisco.com>
Date: Wed, 29 Jun 2016 15:12:14 -0500
Message-ID: <DC35EA50-1505-41D3-B949-00A5A231366E@nostrum.com>
In-Reply-To: <49633303-629D-4CE3-A691-72D4E886080F@cisco.com>
References: <20160624043751.12660.23306.idtracker@ietfa.amsl.com> <99E92338-11D2-404C-BEC7-EDEB9B0C2792@cisco.com> <48BA34F8-5D0A-4597-A3FA-D9E8392F4323@nostrum.com> <22D19CAA-9CF5-4666-8839-20568FE3B35B@cisco.com> <77585AF0-736F-4BE7-B7D8-E1979A962B58@nostrum.com> <49633303-629D-4CE3-A691-72D4E886080F@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/DFqkla4y4meDHsQP4tGCcWJ6N_g>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 20:12:20 -0000

On 29 Jun 2016, at 15:10, Paul Giralt (pgiralt) wrote:

>>
>> That text talks about when the UUID MUST NOT change. I'm looking for 
>> text that says a UUID value MUST NOT be reused across multiple 
>> "sessions" (as sessions are defined in this draft.) The point is to 
>> avoid an accidentally persistent identifier that could be used to 
>> track user/UA activity across multiple sessions.
>
> I see where you are coming from now. I hadn’t payed attention to the 
> fact that the text in 4.2 is not normative. Currently the section 
> reads:
>
> 	The SIP User Agent (UA) initiating a new session by transmitting a 
> SIP
>          request ("Alice"), i.e., a User Agent Client (UAC), will 
> create a new,
>          previously unused, UUID and transmit that to the ultimate 
> destination UA
>          ("Bob").  Likewise, the destination UA ("Bob"), i.e., a User 
> Agent Server (UAS),
>          will create a UUID and transmit that to the first UA 
> ("Alice").
>
> If I just change the “will” to MUST and expand on the UAS also 
> having to create a previously-unused UUID like below, does this 
> address the concern?
>
> 	The SIP User Agent (UA) initiating a new session by transmitting a 
> SIP
>          request ("Alice"), i.e., a User Agent Client (UAC), MUST 
> create a new,
>          previously unused, UUID and transmit that to the ultimate 
> destination UA
>          ("Bob").  Likewise, the destination UA ("Bob"), i.e., a User 
> Agent Server (UAS),
>          MUST create a new, previously unused, UUID and transmit that 
> to the
> 	first UA ("Alice").
>
> Alternatively, I could add some normative text in Section 6 for 
> endpoint behavior, but I think just modifying the above should address 
> the concern. Please let me know your thoughts.
>
> -Paul

That, plus a sentence or two in the security considerations section 
talking about how that helps avoid cross-session persistent identifiers, 
would work for me.

Thanks!

Ben.


From nobody Wed Jun 29 13:36:50 2016
Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 432E512D77F for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 13:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 onL7t6ZPCw85 for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 13:36:47 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 104D612D77D for <insipid@ietf.org>; Wed, 29 Jun 2016 13:36:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1700; q=dns/txt; s=iport; t=1467232602; x=1468442202; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=jFjLfPYQeTNJ4kHQh5oODMKX8ntHi8cmj693mo/Npqg=; b=SxZWknp/SEdCak7e99fG16k9NKKUVMWf8b1nyT8ETfeXlE7vjW15jLoI uVbyBpt6ApJOzfzz4kRHrXe0YTtX0tWPSkfgvtZFOqlVbx8x4jJKHRqx3 YUAjLgu3dneCAV5hVV4eRcFAjog5a8C95VkwJO755nTzqFgCKj0PyFNhL k=;
X-Files: signature.asc : 842
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D5AQBSMHRX/5ldJa1bgz6BUwa5RYF7h?= =?us-ascii?q?hgCgTQ4FAEBAQEBAQFlJ4RMAQEBAwF5BQsCAQgYLjIlAgQOBQ6IGgjDfwEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQ4OhiiBdwiCTodsgi8BBJkFAYMtgWyJJIFTARWNP?= =?us-ascii?q?IZUiS4BHjaDcG6ISX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.26,548,1459814400";  d="asc'?scan'208";a="291517019"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2016 20:36:41 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u5TKaeNl028012 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 Jun 2016 20:36:41 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 29 Jun 2016 16:36:40 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1210.000; Wed, 29 Jun 2016 16:36:40 -0400
From: "Paul Giralt (pgiralt)" <pgiralt@cisco.com>
To: Ben Campbell <ben@nostrum.com>
Thread-Topic: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
Thread-Index: AQHRzdIv8M2blTO35k+l2Gt9c0ch+5/5BxMAgAUeHYCAAXNIgIABj38AgAAD4ACAAACgAIAABs8A
Date: Wed, 29 Jun 2016 20:36:39 +0000
Message-ID: <CC8B4EE1-1927-46EA-AA7C-1ACDE79F8F16@cisco.com>
References: <20160624043751.12660.23306.idtracker@ietfa.amsl.com> <99E92338-11D2-404C-BEC7-EDEB9B0C2792@cisco.com> <48BA34F8-5D0A-4597-A3FA-D9E8392F4323@nostrum.com> <22D19CAA-9CF5-4666-8839-20568FE3B35B@cisco.com> <77585AF0-736F-4BE7-B7D8-E1979A962B58@nostrum.com> <49633303-629D-4CE3-A691-72D4E886080F@cisco.com> <DC35EA50-1505-41D3-B949-00A5A231366E@nostrum.com>
In-Reply-To: <DC35EA50-1505-41D3-B949-00A5A231366E@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.81.96.60]
Content-Type: multipart/signed; boundary="Apple-Mail=_EB4E2EF3-FD7B-407A-853C-B546A04E4250"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/R0iQqYQcv5Jwzgxn4jvyeEy4bhE>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-23.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 20:36:49 -0000

--Apple-Mail=_EB4E2EF3-FD7B-407A-853C-B546A04E4250
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Jun 29, 2016, at 4:12 PM, Ben Campbell <ben@nostrum.com> wrote:
>=20
> That, plus a sentence or two in the security considerations section =
talking about how that helps avoid cross-session persistent identifiers, =
would work for me.
>=20
> Thanks!
>=20
> Ben.


Perfect. Will update with the other changes and push out a new update.

-Paul


--Apple-Mail=_EB4E2EF3-FD7B-407A-853C-B546A04E4250
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXdDFXAAoJEADWV7cDInKsT3sQAIpb8aRI3kXCYFBwhnXMP1Ks
67jx1QI7kmjaZdDZI+YEJ3KIlJ8VRPZNnE2xlPspjNGTb1G7BmjyUKoAgkZ3Alfc
dVAcdosrb7mbz0KSOYC8SLS1XeZppojnGd8XjTWb+38VBVlGebxHk4367vGgpjr/
QRlm0y+3A7i+5lDJRycVcK+AMCtYjeQi4EEQkarPSsMtEsPZjMN66lCyrPZ70tWm
Wp4aB4RmNQDLeuriQc3S8sMyyValGlb9CBQsY7zF/MRYxyoOJoc4G+H6S20xhagz
VKAOzDXZdkfOJWv4PTns1s5JyqYhFD/q7qgVbfhIRUWYqebnyX0uqH1jsSIC5c1U
rifSUEyhsDBS9DhG6Qu1qlfmb4BwqeDfGk7HBYHCduiByIve07ML1WM3OoGnyPnH
v4QX1n6x6M6jlAzskYJP3vVgIwJe4yb0vvz05z1BWuY3MrkJ9X4yTykS17Nqs17A
NAOxwaLtCWtVLes/CzJqKtNXd44tpIkgFkzta8ldaqj6uZa3lBptcKp+o4qmNoWs
BQ6ZnZqi0KIXSYk+i/Yv0RFd44aJQOngJJ5lxzP5PVTY4N8KhdhRY1cwnlt7s3ws
nEYXd/FYKLU4KQJ4a/2SyzoqldLFv3/2TDrj6SCdA0MQUEOqM8ydE3bw3Divz0yI
VFDVW8B0ESkjN5F1ZiUy
=Ismn
-----END PGP SIGNATURE-----

--Apple-Mail=_EB4E2EF3-FD7B-407A-853C-B546A04E4250--


From nobody Wed Jun 29 16:37:35 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: insipid@ietf.org
Delivered-To: insipid@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ADDF12DD44; Wed, 29 Jun 2016 16:37:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160629233734.30463.86831.idtracker@ietfa.amsl.com>
Date: Wed, 29 Jun 2016 16:37:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/jnSDKHW_weknhUH4oZuEKtqP0qs>
Cc: insipid@ietf.org
Subject: [Insipid] I-D Action: draft-ietf-insipid-session-id-24.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 23:37:34 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the INtermediary-safe SIP session ID of the IETF.

        Title           : End-to-End Session Identification in IP-Based Multimedia Communication Networks 
        Authors         : Paul E. Jones
                          Gonzalo Salgueiro
                          Chris Pearce
                          Paul Giralt
	Filename        : draft-ietf-insipid-session-id-24.txt
	Pages           : 41
	Date            : 2016-06-29

Abstract:
   This document describes an end-to-end Session Identifier for use in
   IP-based multimedia communication systems that enables endpoints,
   intermediary devices, and management systems to identify a session
   end-to-end, associate multiple endpoints with a given multipoint
   conference, track communication sessions when they are redirected,
   and associate one or more media flows with a given communication
   session.  While the identifier is intended to work across multiple
   protocols, this document describes its usage in SIP.

   This document also describes a backwards compatibility mechanism for
   an existing session identifier implementation (RFC 7329) that is
   sufficiently different from the procedures defined in this document.

   This document obsoletes RFC 7329.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-insipid-session-id-24

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-insipid-session-id-24


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Jun 29 16:44:40 2016
Return-Path: <pgiralt@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 104D312D949 for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 16:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 2B-P8rtNsKhb for <insipid@ietfa.amsl.com>; Wed, 29 Jun 2016 16:44:37 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DF0812D945 for <insipid@ietf.org>; Wed, 29 Jun 2016 16:44:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3850; q=dns/txt; s=iport; t=1467243874; x=1468453474; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=l9EFimzisaeS0R8BROAQeGgiYhCjvGa2MqSDa6XvcUU=; b=IDEhHgzEQY6RnnZzdPKMd8b+BQo0EYmmyYOSvOP3SRqH1fk069E/r2YU wx/HQhwC9+4yv1OWFzPsSqPtYH/hkxp6YQNbmRsNfrFVp76Cita+i7Tzr 9zzXX5Jfk2Gqzhfc+90QZbpz3M5BrVUZh9xHnFTRl9RaKsCmge2d8lXlF Q=;
X-Files: signature.asc : 842
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D6AQAkXHRX/4MNJK1RCgGDPVZ9uVGBe?= =?us-ascii?q?xcLhSxKAoE2OBQBAQEBAQEBZSeETAEBAQMBAQEBZQYLBQsLGC4nMBmIKAgOwmA?= =?us-ascii?q?BAQEBAQEBAwEBAQEBAQEBARAOhiiBd4JWhBh0gmCCLwWZBYMuglqINoFpToQGi?= =?us-ascii?q?GiQAx42hAwgMolIAQEB?=
X-IronPort-AV: E=Sophos;i="5.26,549,1459814400";  d="asc'?scan'208";a="118374482"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Jun 2016 23:44:33 +0000
Received: from rtp-vpn5-588.cisco.com (rtp-vpn5-588.cisco.com [10.82.234.78]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u5TNiWiY008130 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jun 2016 23:44:32 GMT
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_53D6C845-11AD-437F-81B5-B22DE80A3083"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: Paul Giralt <pgiralt@cisco.com>
In-Reply-To: <20160629233734.30463.86831.idtracker@ietfa.amsl.com>
Date: Wed, 29 Jun 2016 19:44:31 -0400
Message-Id: <5BF95E68-1D12-405E-9E0E-9FEF095B29CA@cisco.com>
References: <20160629233734.30463.86831.idtracker@ietfa.amsl.com>
To: ben@nostrum.com
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/wWmrPilV0CRSUS5CK5IyVC9SYbg>
Cc: insipid@ietf.org
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-session-id-24.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 23:44:39 -0000

--Apple-Mail=_53D6C845-11AD-437F-81B5-B22DE80A3083
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Ben / INSIPID WG,

I believe this latest draft addresses all outstanding feedback. Please =
let me know if any other changes are need before moving to the next step =
in the process.

Thanks,
-Paul


> On Jun 29, 2016, at 7:37 PM, internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the INtermediary-safe SIP session ID of =
the IETF.
>=20
>        Title           : End-to-End Session Identification in IP-Based =
Multimedia Communication Networks
>        Authors         : Paul E. Jones
>                          Gonzalo Salgueiro
>                          Chris Pearce
>                          Paul Giralt
> 	Filename        : draft-ietf-insipid-session-id-24.txt
> 	Pages           : 41
> 	Date            : 2016-06-29
>=20
> Abstract:
>   This document describes an end-to-end Session Identifier for use in
>   IP-based multimedia communication systems that enables endpoints,
>   intermediary devices, and management systems to identify a session
>   end-to-end, associate multiple endpoints with a given multipoint
>   conference, track communication sessions when they are redirected,
>   and associate one or more media flows with a given communication
>   session.  While the identifier is intended to work across multiple
>   protocols, this document describes its usage in SIP.
>=20
>   This document also describes a backwards compatibility mechanism for
>   an existing session identifier implementation (RFC 7329) that is
>   sufficiently different from the procedures defined in this document.
>=20
>   This document obsoletes RFC 7329.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-insipid-session-id-24
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-insipid-session-id-24
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid


--Apple-Mail=_53D6C845-11AD-437F-81B5-B22DE80A3083
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXdF1iAAoJEADWV7cDInKsbO4P/iiJfFxqQUrDDYnM8xF2+D/F
GSwSqMBgrFzmyblPi0M9uIsU2YDX48m7+YDPL9wLFQdcy/Z2+QzwmG5RGjymhVcF
3XMh+lzf2AdmS9W1I5bdzW06l/ejQiGEgEczVOJTxRPUM+L16rfgVSObG73al+wG
3rlw8fAfFrl9L++hgNBrfIwT1d2BQV50eLNs4DRbBBDpRG4JkHgkHrR+fr70Id5j
YwuE5qVFq9sgrLR2vMdvmW37orb3DEqf1Mekh7qq1hqXW2TysUu6Rez7nPZF8Abj
ZYEmCAQbwd4K3+3L0wkY6hRzI2T64Z2I3c7pC0RkaRQU6A2q8BlsFsLjNkod7gZs
DeEhrQQZb7LpJmxpTM2v3SJ8v/eUvcNutjz/DyL5LmEYXraURxbkv7ybUqZWbDwV
GXARXrgASW4XJ45KhBm5C8wiRH5zosfUbgL9/7OklBHeLVnxJotqPO8a4tPbhdB5
CsJlmzTt63yhVxODZL2zcPSXDW8VkZYy57cI87SRNa1q3L6tiJ/PbTFVqeC6UAqk
72chmxmrXv3RMG3iTcKQx5RUb7L90D++EajUzt7ga8Noc/psWqR2DtXQ0i/chwiy
UlgqWRfVR1H1iiDcUNdTIe0xxwbqno/X41NhvRY4IVv+XJMjmWBD/kxHpEUEvYzR
0efDZIyWRgp+z5lG0EN6
=Bw5V
-----END PGP SIGNATURE-----

--Apple-Mail=_53D6C845-11AD-437F-81B5-B22DE80A3083--

