[Hipsec-rg] Re: Native HIP API questions in the hipsec-rg meeting

[[e-mail] (Joe Touch)]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9EBDEB70A4F1BDEC99148D14
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Lars Eggert wrote:

> now I'm confused. The slides in San Diego showed a binding from HITs to 
> interfaces. Yet this email talks about binding HITs to IP addresses. 
> Which is it? Were the slides in San Diego wrong?
> 
> The issue we raised in San Diego was that *nothing* in the current 
> sockets API ever binds to interfaces. Everything binds to IP addresses. 
> Even INADDR_ANY just means "any IP address."

Actually, there is a way to bind to an interface - used in multicast 
addresses, notably. It may also be required where a single unicast 
address is used on multiple interfaces; although that's possible, I 
don't know how well it's supported.

Joe

--------------enig9EBDEB70A4F1BDEC99148D14
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBIYacE5f5cImnZrsRAgSdAKCdQxsFQcCWPAEnDdg+7mlpYboezwCglFPF
Kn7yLI4DEOZCVcBTUO637gg=
=Gkr8
-----END PGP SIGNATURE-----

--------------enig9EBDEB70A4F1BDEC99148D14--