Re: [Sipping] Device Identity

"Dale R. Worley" <dworley@pingtel.com> Sat, 01 April 2006 20:10 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FPmQk-00030s-UN; Sat, 01 Apr 2006 15:10:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FPmQj-0002zS-Pb for sipping@ietf.org; Sat, 01 Apr 2006 15:10:41 -0500
Received: from mail.pingtel.com ([65.220.123.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FPmQi-0006if-II for sipping@ietf.org; Sat, 01 Apr 2006 15:10:41 -0500
Received: from localhost.localdomain (mail.pingtel.com [192.168.253.2]) by mail.pingtel.com (Postfix) with ESMTP id 407506C01C for <sipping@ietf.org>; Sat, 1 Apr 2006 15:10:40 -0500 (EST)
Subject: Re: [Sipping] Device Identity
From: "Dale R. Worley" <dworley@pingtel.com>
To: Sipping <sipping@ietf.org>
In-Reply-To: <43F4D194.6060303@cisco.com>
References: <91B3F82B94C8BF45991DE2D6988DDCD60300A42A@exbetasa03.tasa.telefonica.com.ar> <1140017704.7422.8.camel@cdhcp139.pingtel.com> <43F3556A.10109@cisco.com> <002001c6325a$53bae300$31713b51@BEMBUSTER> <1140027425.7422.23.camel@cdhcp139.pingtel.com> <A57AFAB7-7193-4342-A7B6-0F42BE6D464E@softarmor.com> <43F49C3E.8050509@cisco.com> <1140115756.4478.9.camel@maine.pingtel.com> <43F4D194.6060303@cisco.com>
Content-Type: text/plain
Date: Sat, 01 Apr 2006 15:10:40 -0500
Message-Id: <1143922240.2733.37.camel@niagra.pingtel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-7)
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

On Thu, 2006-02-16 at 14:25 -0500, Josh Littlefield wrote:
> Dale R. Worley wrote:
> >>>> It seems like these "MAC:" pseudo-URIs should be registered as a  proper
> >>>> URI scheme.
> > 
> > What if I write a section of the I-D that is a proper request to
> > register "MAC:" as a URI-scheme?  If it can stand alone as a
> > registration request, and also be a section of the I-D, I would think it
> > should be fairly easy to get it approved as a URI-scheme.
> > 
> > Dale
> 
> If this discussion is around the MAC: pseudo-URI in the 
> sipping-config-framework, I should point out that it does not use MAC: 
> as a URI scheme.  MAC: is a username convention used in a normal SIP: URI.

OK, I finally had a chance to look, and you're right.  So as far as the
config framework goes, there is no reason to define a MAC URN-namespace.

But I did do a search on the I-Ds I have accumulated, and found a few
instances where "MAC:xxxxxxx" *is* used as a URN.  draft-ietf-simple-
presence-data-model-07.txt and draft-ietf-simple-rpid-05.txt take the
approach of using a MAC URN as a device identifier.  Curiously, all the
examples use the syntax "mac:xxxxxxxxxx", whereas RFC 2141 makes it
clear that the syntax would have to be "urn:max:xxxxxxxxxxxx".

If the subject of these drafts were to advance toward standardization,
the "MAC URN" is something that would have to be cleared up.  But as
Josh points out, that need not be done for the config framework, as as
others have pointed out, suitable device-dependent "instance
identifiers" can be generated using the standardized UUID mechanism.

Dale



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP