Cameron, >>> What is the expected behavior when that address becomes unavailable? >> >> reliability is achieved through anycast. there are multiple BRs advertising >> the same address into the IGP. >> did that address your question? >> > > Sorry, i have not really been able to find this out on my own. > > But, i thought there was tight coupling of the BR address resources > and CPE address assignments. > > Meaning BR1 has for me (the subscriber) the public address 1.1.1.1 > with ports 2000-3000 and that is communicated to CPE1 > > BR1 goes has a fault, goes off line. > > BR2 is now the closest anycast path to CPE1 > > My CPE is sending packets to BR2 (as anycast) assuming BR2 owns > 1.1.1.1 and port set 2000-3000.
the BR doesn't really have any port sets, although it could. the anycast address is an IPv6 address. > > But, how does BR2 know anything about 1.1.1.1? Does BR2 now announce > in BGP to the world it owns 1.1.1.1? > > Is that going to work? If so, where is it documented? > > Or, does the CPE have to reboot and get some new config assignment > based on BR2 now being the closest? > > How does this oscillating load (BR failure, shortest path changes, ... > ) associated with anycast bode for the IPv4 address reserves ? Seems > like the public IPv4 address pool on each BR would have to be > over-provisioned to handle some N*X level of load. > > Sorry if i am missing something obvious. sounds like we need to make this a little clearer in the draft. it isn't quite like you describe. the BR is used for out of domain traffic. other traffic is 'on-link'. e.g. the CE has a default route: 0.0.0.0/0 -> 2001::1, MAP0. 2001::1 is advertised from every BR. cheers, Ole _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
