On Wed, 10 Sep 2014, Acee Lindem (acee) wrote:
The 2nd paragraph of Section 4 says:
The solution should start with the correct configuration of
the host. The host should be configured with the next hop addresses
and the prefixes supported in these next hops. This way the host
having received many prefixes will have the correct knowledge in
selecting the right source address and next hop when sending packets
to remote destinations.
That sounds like new functionality on the host. Not sure if that is
what caught Acee's attention, though.
Yes - Additionally, I agree with Mark’s statement on the HOMENET requirement
and would like to go on the record as saying that I’m certainly not against
correct source address selection by the host stacks ;^)
My opinion is that homenet shouldn't require new functionality in the host
stack for it to work, but if we can present suggestions for enhancements
in the host stack that makes things work better, and also enhance homenet
to take advantage of enhancements in host stacks to make things work
better, I'm all for that.
But our baseline is that a 10 year old host stack should work out of the
box with homenet, and I don't see us changing that.
--
Mikael Abrahamsson email: [email protected]
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
