On Fri, May 28, 2010 at 8:03 AM, Christopher Morrow <[email protected]> wrote: > > uhm, so my host has ip address A, it's got attachments to networks B, C, D. > > how does the world know that services on A are behind B, C, D except > for bgp telling them? > If you choose to tell them via DNS you're telling them "Find me at B" > and their packets (today) get addressed to B, not A. This only works, > today, if you tell them, in DNS, "A is me, send to A"... but then as > we move from B, C, D we have to tell the world with BGP how to find > us. >
A is edge address space and B, C and D are core address space, i.e. edge locators are not announced in DFZ but core locators are installed in DFZ. Also the edge locators do no longer need to be globally unique since a host is announced in DNS with a combination of an edge locator and one or several core locators. 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). -- patte _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
