OK, so the action I take is that I think there should be some text added
to explain this case. When I get to making the next revision, I'll send
you the text to make sure this is covered.
Thanks,
Gorry
Stig Venaas wrote:
Gorry Fairhurst wrote:
Stig Venaas wrote:
Gorry Fairhurst wrote:
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
BTW, why do you want or need to do this? Why do you not not want to
generate a standard Interface Identifier like everyone else?
Thomas
Hi Everyone,
I have an ethernet interface for which I am defining the Interface-ID
in a different manner.
For an ethernet interface with MAC
