I believe that Patrick is asking about outbound traffic routing, not
inbound.
Which is very reasonable question to ask.
Unfortunately, until we are prepared to make a much larger set of
changes, we do not have the tools to allow a host to choose which
outbound site connection is used by the hosts outbound traffic. (There
are many use cases which would like those capabilities, but we have not
found a good way to deliver them.)
yours,
Joel
Tony Li wrote:
On 6/4/10 5:21 AM, "Patrick Frejborg" <[email protected]> wrote:
A question regarding ILNP and multi-homing scenario.
The primary path from A towards Internet goes via attachment point B
and this is announced in DNS. Then ISP taking care of attachment point
B have some performance problems and the service is not good enough
for host A - he decides to switch to attachment point C and updates
DNS. But how does the packet get routed from host A to attachment
point C instead of B in large enterprise network where there could be
a lot of routers and some security nodes between the host and the
attachment points?
I don't want to tweak the local routing domain but when I change the
DNS records host A should start to use new attachment point (C), some
other hosts might still use the old one (B).
In ILNP, a host controls how packets arrive by changing the locators that
are advertised. Outbound, intra-domain packet routing is separate, and
COULD be based on the hosts source locator, but this is a separate
enhancement that we could make.
Once the host updates DNS with the C locator, it should also concurrently
send ICMP locator updates to its active correspondents and inform them of
the C locator.
Tony
_______________________________________________
rrg mailing list
[email protected]
http://www.irtf.org/mailman/listinfo/rrg
_______________________________________________
rrg mailing list
[email protected]
http://www.irtf.org/mailman/listinfo/rrg
