| | Roxen Community: RFC 3068 An Anycast Prefix for 6to4 Relay Routers (Standards Track) (Site not responding. Last check: 2007-09-06) |
 | | Anycast routing is known to cause operational issues: since the sending 6to4 router does not directly identify the specific 6to4 relay router to which it forwards the packets, it is hard to identify the responsible router in case of failure, in particular when the failure is transient or intermittent. |
 | | Anycast solutions must thus include adequate monitoring of the routers performing the service, in order to promptly detect and correct failures, and also adequate fault isolation procedures, in order to find out the responsible element when needed, e.g., following a user's complaint. |
 | | The anycast technique introduces an additional risk, that a rogue router or a rogue AS would introduce a bogus route to the 6to4 anycast prefix, and thus divert the traffic. |
| community.roxen.com /developers/idocs/rfc/rfc3068.html (2383 words) |