Re: [Sipping] UA indentification and HIP

[Paul Kyzivat <[e-mail]>]

Does this really work for us?

It sounds like it only works for *hosts*. That doesn't sound like it 
covers the case of a UA (e.g. softphone) that may move from host to host 
while retaining its identity. Nor does it seem to cover the case of 
multiple UAs that share a host.

	Paul

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 [e-mail] for questions on current sip
> Use [e-mail] 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 [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP