draft-kurtis-anycast-bcp-00.txt

1
draft-kurtis-anycast-bcp-00.txt

• GROW WG
• IETF-61, November 9th 2004

2
Why?

• Document experiences
• Give guidelines and tips
• Document pit-falls
• We do not claim this complete
• We really want input and feedback from others
• Quite a few people have done this for quite a
  while

3
Anycast

• Making one or more service addresses available to
  a routing system at Anycast nodes in two or more
  discrete locations.

4
Goals

1. Coarse ("unbalanced") distribution of load across
   nodes, to allow infrastructure to scale to
   increased numbers of queries and to accommodate
   transient query peaks
2. Mitigation of non-distributed denial of service
   attacks by localizing damage to single anycast
   nodes
3. Constraint of distributed denial of service
   attacks or flash crowds to local regions around
   anycast nodes (perhaps restricting query traffic
   to local peering links, rather than paid transit
   circuits)
4. Triangulation of traffic sources, in the case of
   attack (or query) traffic which incorporates
   spoofed source addresses
5. Improvement of query response time, by reducing
   the network RTT between client and server with
   the provision of a local Anycast Node Reduction
   of a list of servers to a single, distributed
   address. For example, a large number of
   authoritative nameservers for a zone may be
   deployed using a small set of anycast service
   addresses this approach can increase the
   accessibility of zone data in the DNS without
   increasing the size of a referral response from a
   parent nameserver.

5
Design

• Protocol suitability
• Node placement
• Routing System
• Anycast within IGP
• Anycast within the Global Internet
• Routing Considerations

6
Design

• Data synchronization
• Node Autonomy

7
Service Management

• Monitoring
• Self-Healing Nodes
• This is the tricky bit in general

8
We would like to

• Get feedback
• Ask if this is work of interest to the working
  group