Re: [Insipid] MUST or SHOULD for Type 4 / 5 UUIDs?

"Paul Giralt (pgiralt)" <pgiralt@cisco.com> Thu, 02 June 2016 11:01 UTC

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

I don’t 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’t 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:
> 
> 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,
>> 
>> 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¹m inclined to change the first to MUST and thereby require that only
>> Type 4 or Type 5 UUID¹s be used.
>> 
>> Does anyone have an issue with this change?
>> 
>> -Paul
>> 
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
>