grow: anycast ops draft

Joe Abley <jabley@isc.org> Mon, 01 November 2004 20:32 UTC

Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27770 for <grow-archive@lists.ietf.org>; Mon, 1 Nov 2004 15:32:33 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id iA1KNrOs024902; Mon, 1 Nov 2004 12:23:53 -0800 (PST)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id iA1KNpHW024804; Mon, 1 Nov 2004 12:23:51 -0800 (PST)
Received: from felix.automagic.org (felix.hopcount.ca [204.152.186.101]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id iA1K41MX017991 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for <grow@lists.uoregon.edu>; Mon, 1 Nov 2004 12:04:03 -0800 (PST)
Received: from [199.212.90.23] (helo=[199.212.90.23]) by felix.automagic.org with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42 (FreeBSD)) id 1COiPH-000I7v-Jo for grow@lists.uoregon.edu; Mon, 01 Nov 2004 20:03:59 +0000
Mime-Version: 1.0 (Apple Message framework v619)
Content-Transfer-Encoding: 7bit
Message-Id: <18A3F56E-2C41-11D9-928C-000D93B24C7A@isc.org>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
To: grow@lists.uoregon.edu
From: Joe Abley <jabley@isc.org>
Subject: grow: anycast ops draft
Date: Mon, 01 Nov 2004 15:03:28 -0500
X-Mailer: Apple Mail (2.619)
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit

Kurtis Lindqvist and I squeezed this draft through before the cut-off:

   http://www.ietf.org/internet-drafts/draft-kurtis-anycast-bcp-00.txt

> Abstract
>
>    As the Internet has grown, many services with high availability
>    requirements have emerged.  The requirements of these services have
>    increased the demands on the reliability of the infrastructure on
>    which those services rely.
>
>    Many techniques have been employed to increase the availability of
>    services deployed on the Internet.  This document presents
>    operational experience of wide-scale service distribution using
>    anycast, and proposes a series of recommendations for others using
>    this approach.

Anycast distribution of services (the practice of injecting 
reachability information for an address into a routing system in 
multiple places, from autonomous nodes) is not at all a new idea; 
however, there are an increasing number of people using anycast 
approaches to distribute high-profile services, and few published 
guidelines for doing so. The aim of this document is to provide some 
guidelines.

There are many, many people with experience deploying anycast services 
whose thoughts and opinions are not in that -00 draft. Hopefully some 
of them are on this list, and they can help us make the draft better.

We have a brief slot in the grow meeting next Tuesday to introduce this 
draft, and we plan to propose that it becomes a working group document. 
If people on this list have a chance to review the draft before then, 
that would be great.


Joe

_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/