Re: [Sipping] Device Identity

Cullen Jennings <fluffy@cisco.com> Sun, 19 February 2006 02:39 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FAeTe-00081I-Rj; Sat, 18 Feb 2006 21:39:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FAeTd-00081D-Kn for sipping@ietf.org; Sat, 18 Feb 2006 21:39:09 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FAeTc-00054a-Be for sipping@ietf.org; Sat, 18 Feb 2006 21:39:09 -0500
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-2.cisco.com with ESMTP; 18 Feb 2006 18:39:08 -0800
Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com [171.70.93.57]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k1J2d5ub027860; Sat, 18 Feb 2006 18:39:06 -0800 (PST)
Received: from 10.21.97.248 ([10.21.97.248]) by vtg-um-e2k4.sj21ad.cisco.com ([171.70.93.57]) with Microsoft Exchange Server HTTP-DAV ; Sun, 19 Feb 2006 02:39:05 +0000
User-Agent: Microsoft-Entourage/11.2.1.051004
Date: Sat, 18 Feb 2006 18:39:26 -0800
Subject: Re: [Sipping] Device Identity
From: Cullen Jennings <fluffy@cisco.com>
To: "Dale R. Worley" <dworley@pingtel.com>, sipping <sipping@ietf.org>
Message-ID: <C01D1A5E.7484E%fluffy@cisco.com>
Thread-Topic: [Sipping] Device Identity
Thread-Index: AcY0/bLu8aQtI6DwEdqIcgARJEEJ/A==
In-Reply-To: <1140119345.4478.18.camel@maine.pingtel.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc:
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

Some early version of draft-jennings-sipping-instance-id define some of
this. However, people pointed out that UUID already was capable of doing
this, and even better UUID could work for softphone too. It seemed like UUID
was a super set of everything we need so I abandoned that draft.

It seems like a UUID in the +sip.instance meets the needs people have
identified.

Cullen

On 2/16/06 11:49 AM, "Dale R. Worley" <dworley@pingtel.com> wrote:

> On Thu, 2006-02-16 at 13:37 -0600, Dean Willis wrote:
>> Don't we have different underlying registries for different sorts of
>> MAC address: ethernet, token-ring, FDDI, etc.?
> 
> My belief (which may be wrong) is that all MACs are drawn from the same
> number space, which is managed and assigned by the IEEE.  If so, we
> don't need to have separate schemes for different sorts of MACs.
> 
> 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

_______________________________________________
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