Operation of Anycast Services
RFC 4786
also known as BCP 126
Revision differences
Document history
Date | By | Action |
---|---|---|
2023-12-12
|
(System) | Imported membership of rfc4786 in bcp126 via sync to the rfc-index |
2023-12-12
|
(System) | No history of BCP126 is currently available in the datatracker before this point |
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'As the Internet has grown, and as systems and networked services within enterprises have become more … Received changes through RFC Editor sync (changed abstract to 'As the Internet has grown, and as systems and networked services within enterprises have become more pervasive, many services with high availability requirements have emerged. These requirements have increased the demands on the reliability of the infrastructure on which those services rely. Various techniques have been employed to increase the availability of services deployed on the Internet. This document presents commentary and recommendations for distribution of services using anycast. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.') |
2015-10-14
|
(System) | Notify list changed from gih@telstra.net, jabley@isc.org, kurtis@kurtis.pp.se to gih@telstra.net |
2007-01-02
|
Amy Vezza | [Note]: 'RFC 4786 BCP 126' added by Amy Vezza |
2007-01-02
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2007-01-02
|
Amy Vezza | [Note]: 'RFC 4786' added by Amy Vezza |
2006-12-22
|
(System) | RFC published |