Re: [Sipping] UA indentification and HIP

Jonathan Rosenberg <jdrosen@dynamicsoft.com> Wed, 25 February 2004 20:07 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09514 for <sipping-archive@odin.ietf.org>; Wed, 25 Feb 2004 15:07:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw5JM-0007iD-OJ for sipping-archive@odin.ietf.org; Wed, 25 Feb 2004 15:07:16 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1PK7GBt029584 for sipping-archive@odin.ietf.org; Wed, 25 Feb 2004 15:07:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw5JL-0007h0-NM for sipping-web-archive@optimus.ietf.org; Wed, 25 Feb 2004 15:07:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09463 for <sipping-web-archive@ietf.org>; Wed, 25 Feb 2004 15:07:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aw5JI-0004ml-00 for sipping-web-archive@ietf.org; Wed, 25 Feb 2004 15:07:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aw5IF-0004ge-00 for sipping-web-archive@ietf.org; Wed, 25 Feb 2004 15:06:08 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Aw5HP-0004aW-00 for sipping-web-archive@ietf.org; Wed, 25 Feb 2004 15:05:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw5HC-0006cd-Ul; Wed, 25 Feb 2004 15:05:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw5GD-0005pH-Vb for sipping@optimus.ietf.org; Wed, 25 Feb 2004 15:04:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09127 for <sipping@ietf.org>; Wed, 25 Feb 2004 15:03:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aw5GB-0004SK-00 for sipping@ietf.org; Wed, 25 Feb 2004 15:03:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aw5FG-0004N6-00 for sipping@ietf.org; Wed, 25 Feb 2004 15:03:02 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 1Aw5EW-0004BP-00 for sipping@ietf.org; Wed, 25 Feb 2004 15:02:16 -0500
Received: from dynamicsoft.com ([63.113.46.35]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i1PK1fNr009302; Wed, 25 Feb 2004 15:01:42 -0500 (EST)
Message-ID: <403CFF0E.5070705@dynamicsoft.com>
Date: Wed, 25 Feb 2004 15:01:18 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
CC: sipping <sipping@ietf.org>, Cullen Jennings <fluffy@cisco.com>, bstucker@nortelnetworks.com
Subject: Re: [Sipping] UA indentification and HIP
References: <403B0C82.20407@ericsson.com>
In-Reply-To: <403B0C82.20407@ericsson.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Thanks for the brief intro, Gonzalo. I need to read more on HIP and its 
on my now-very-length reading list for the plane.

Let me anyway ask the main question I have not understood, which is how 
address resolution is done. So, lets say I want to send a message to a 
host, and I have obtained its HIT somehow. Presumably I need to 
translate that to the IP for the host. How is that done? If its DNS, 
then what is the difference between HIP and just using dynamic DNS and 
assigning a hostname to each host?

Or, is the proposal that a HIT is an address, not a name, in which case 
routes to it are injected into the IP routing infrastructure. I hope, 
and assume, that this is not the case, since thats equivalent to a host 
route for every host on the Internet... egads!

-Jonathan R.

Gonzalo Camarillo wrote:

> Folks,
> 
> the following two drafts describe how to indentify a particular UA using 
> globally unique identifiers:
> 
> http://www.ietf.org/internet-drafts/draft-stucker-sip-guid-00.txt
> http://www.ietf.org/internet-drafts/draft-jennings-sipping-instance-id-00.txt 
> 
> 
> Cullen pointed out that this work may be able to take advantage of the 
> work carried out in the HIP (Host Identity Protocol) WG, which 
> supplemental web page is:
> 
> http://hip.piuha.net/
> 
> Here you have a *very* brief introduction to HIP. I will also be 
> providing a brief introduction to the drafts above to the HIP community. 
> Hopefully, we will have a useful exchange of ideas between both WGs.
> 
> HIP consists of a layer between the network and the tranport layers 
> (e.g., between IP and TCP). It uses HIs (Host Identifiers) to identify 
> hosts. The idea is that, when a host changes its IP address, it keeps 
> its HI. This facilitates mobility, for instance.
> 
> HIs (Host Identifiers) are public keys, which may have different lengths 
> and formats. To resolve this, HIP defines the HITs (Host Identity Tags), 
> which are hashes of the HI. That is, a HIT is a hash of a public key. 
> They are 128 bit long, and can be used instead of IPv6 addresses in 
> socket calls. HIP also defines LSIs (Local Scope Indetifiers), that are 
> 32 bit long and can be used instead of IPv4 addresses in socket calls.
> 
> Regards,
> 
> Gonzalo
> 
> 
> This communication is confidential and intended solely for the 
> addressee(s). Any unauthorized review, use, disclosure or distribution 
> is prohibited. If you believe this message has been sent to you in 
> error, please notify the sender by replying to this transmission and 
> delete the message without disclosing it. Thank you.
> 
> E-mail including attachments is susceptible to data corruption, 
> interruption, unauthorized amendment, tampering and viruses, and we only 
> send and receive e-mails on the basis that we are not liable for any 
> such corruption, interception, amendment, tampering or viruses or any 
> consequences thereof.
> 
> 
> _______________________________________________
> 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
> 

-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
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