Le 27/03/2012 16:04, Erik Kline a écrit :
On 27 March 2012 13:50, Alexandru
Petrescu<alexandru.petre...@gmail.com> wrote:
Le 27/03/2012 15:45, Erik Kline a écrit :
IMHO, my home desktop should really be able to handle this too
(router selection needs to consider which source address was
picked from which router).
I think this is some of the stuff that 6man has been discussing.
Do you think that discussion may have concluded that it's not good
to have several default routes on the Client?
The discussion I'm referring to is about updating the source address
selection depending on the next hop. This is obviously a more
complicated issue overall, of course. Unless you get it right,
you're likely to run afoul of BCP38.
I see. One wouldn't appreciate be subject to Ingress Filtering.
As a sidenote, also there exist solutions in the 6man space about
selecting the source address and even about selecting a route if there
are two similar in the routing table.
RFC3484 comes to mind, which shows a policy table where the routes have
"precedence" fields. This means two default routes could be present in
the routing table, have a different preference, and be selected
according to some policy keyed by this preference value.
In Neighbor Discovery also exist distinctors to choose among several
default routes present in the Client.
Alex
_______________________________________________
mif mailing list
mif@ietf.org
https://www.ietf.org/mailman/listinfo/mif
