Re: Any effort to try to make IPv6 API more uniform?

-----BEGIN PGP SIGNED MESSAGE-----

quoted

quoted

quoted

quoted

"Pekka" == Pekka Savola [off-list ref] writes:

    Pekka> In addition to IPv6 Basic & Advanced Sockets API document, I had a worry 
    Pekka> whether there would be any use trying to make some other API's more 
    Pekka> useful.

    Pekka> For example, currently there is no standard (or even "semi-standard") way 
    Pekka> of getting IPv6 address(es) of a node.  With IPv4 you can get this via 
    Pekka> ioctls or e.g. netlink.  Netlink is notably a Linux-only thing.

  It would be nice to have a "standard" iterator function for this.
  It would also be nice to be able to give it a hint, like:

  "if I were to connect to host X, proto Y, port Z, what would my IP{v4,v6} be?"

  This might even have to take a trip into the kernel to evaluate advanced
routing rules, etc. but would certainly simply things.

  It would also be nice if the interface to get the destination IP/port on
a UDP packet (gotten with IP_PKTINFO) was simpler. My ideal is that if you
provide recvfrom() a double sized sockaddr, that you'd get both src and dst.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBPZSGOoqHRg3pndX9AQFoYgP+IdAMviCVuCFoujLPbtrgX3pLE01O2v1T
kb0qgkleiYC5xDi3r6NCoqVAN6bGvwr3rZFFmhtUamoM6+Me/70a4Mi531jzBtTY
ewcxLXoc7KqplC4RKFpF9uAsy3kDGNiU6rJ8ROdFYfJwDs+Odl3dpOzeSpWXTBFZ
eTImxjz3GqE=
=OlKS
-----END PGP SIGNATURE-----