<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.iab-anycast-arch-implications" target="https://datatracker.ietf.org/doc/html/draft-iab-anycast-arch-implications-12">
   <front>
      <title>Architectural Considerations of IP Anycast</title>
      <author initials="D. R." surname="McPherson" fullname="Danny R. McPherson">
         <organization>Verisign, Inc.</organization>
      </author>
      <author initials="D. R." surname="Oran" fullname="David R. Oran">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="D." surname="Thaler" fullname="Dave Thaler">
         <organization>Microsoft Corporation</organization>
      </author>
      <author initials="E." surname="Osterweil" fullname="Eric Osterweil">
         <organization>Verisign, Inc.</organization>
      </author>
      <date month="November" day="4" year="2013" />
      <abstract>
	 <t>This memo discusses architectural implications of IP anycast and provides some historical analysis of anycast use by various IETF protocols.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-iab-anycast-arch-implications-12" />
   
</reference>
