Arifumi Matsumoto wrote:
is RFC 5014 what you are looking for ?
No, that seems to only deal with source address selection. It also
doesn't deal with IPv4 at all.
What I was thinking of is an API, where you supply a set of source
addresses and destination addresses and it returns a set of
On Mon, 29 Jun 2009 14:40:53 +0300, Aleksi Suhonen aleksi.suho...@tut.fi
wrote:
Thoughts? Comments? Or does it exist already and I'm just ignorant?
No. There is no standard API for this, and it is a major road block to
implementing dual-stack correctly in some scenarios.
The problem is simply
Hi,
Address selection happens in many places: in some cases it's supposed to
happen inside the kernel, in some cases inside a library and in some
cases in the application.
Would it make sense to create a uniform API so that no matter where it
takes place, it has access to all the same input
Hi,
is RFC 5014 what you are looking for ?
On 2009/06/29, at 20:40, Aleksi Suhonen wrote:
Hi,
Address selection happens in many places: in some cases it's
supposed to happen inside the kernel, in some cases inside a library
and in some cases in the application.
Would it make sense to
