Re: [VCARDDAV] KIND:device

Simon Perreault <simon.perreault@viagenie.ca> Wed, 11 January 2012 19:01 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: vcarddav@ietfa.amsl.com
Delivered-To: vcarddav@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2020E21F84D6 for <vcarddav@ietfa.amsl.com>; Wed, 11 Jan 2012 11:01:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.179
X-Spam-Level:
X-Spam-Status: No, score=-2.179 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, J_CHICKENPOX_46=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ghhvpWuSjt1 for <vcarddav@ietfa.amsl.com>; Wed, 11 Jan 2012 11:01:35 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by ietfa.amsl.com (Postfix) with ESMTP id 81AFD21F84D4 for <vcarddav@ietf.org>; Wed, 11 Jan 2012 11:01:35 -0800 (PST)
Received: from balaise.nomis80.org (modemcable070.153-130-66.mc.videotron.ca [66.130.153.70]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B8DE421BD2; Wed, 11 Jan 2012 14:01:04 -0500 (EST)
Message-ID: <4F0DDC70.6020403@viagenie.ca>
Date: Wed, 11 Jan 2012 14:01:04 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0
MIME-Version: 1.0
To: Joe Marcus Clarke <jclarke@cisco.com>
References: <4F073CD8.1060102@stpeter.im> <1DE983233DBBEB4A81F18FABD8208D7614088000@XMB108FCNC.rim.net> <4F0B207B.70707@cisco.com> <4F0DA1F3.2070202@viagenie.ca> <4F0DD733.3000505@cisco.com>
In-Reply-To: <4F0DD733.3000505@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: CardDAV <vcarddav@ietf.org>
Subject: Re: [VCARDDAV] KIND:device
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vcarddav>
List-Post: <mailto:vcarddav@ietf.org>
List-Help: <mailto:vcarddav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jan 2012 19:01:36 -0000

On 01/11/2012 01:38 PM, Joe Marcus Clarke wrote:
> On 1/11/12 9:51 AM, Simon Perreault wrote:
>> On 01/09/2012 12:14 PM, Joe Marcus Clarke wrote:
>>> We did add UID as a holder for serial number.
>>
>> I'd be careful with that idea. What tells a vCard consumer that the UID
>> property also happens to contain a serial number? Seems like pointless
>> overloading to me. Better just create a new serial number property. It's
>> free, you know... ;)
>
> I do.  I was arguing that a "unique identifier" for a device would
> likely be a serial number since that is burned into the device.  Gonzalo
> and I were debating this further and I'm coming around to provisioning a
> serial number property vs. overloading UID.  But since UID can hold a
> text value like this, it would be legal to do a serial number here, right?

I'm not sure you understood my point.

Yes it would be *legal* for the UID property to hold a serial number.

The problem I'm thinking of would arise if, in *any* circumstance, you 
try to *interpret* the UID property as a serial number, or you try to 
*extract* a serial number from it. If you don't want to do that, fine, 
but then I'd still be curious as to why a randomly-generated UUID 
wouldn't be easier.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca