<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Hi All,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Before I actually type up and submit a policy proposal, I
wanted some opinions on the adoption of a policy regarding the allocation of
/24 prefix’s for the purpose of anycast.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>This could be done in two ways, either through a
modification of the current v4 allocation policy or through the addition of an
overriding policy, I think the former makes more sense however.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Very basic concept:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Because you cannot announce anything smaller than a /24 into
the global tables, in order to provide for anycast you need to announce an
entire /24, and in an anycast situation this is announced from multiple asn’s.
AfriNIC’s current v4 policy states that the minimum allocation size on
initial is a /22. To use a /22 for anycast when you potentially are only
using 3 addresses in the block is a huge waste.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Also, with anycast prefix’s it is potentially possible
to have multiple anycast blocks that are using only 2 or 3 addresses in the
prefix (see ASN 112 192.175.48.0/24 prefix that uses 3 address in the
/24). This means that a company that utilizes general allocation /24
space for the purposes of anycast could be in trouble when applying for more
space due to lack of space usage.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>To my knowledge RIPE also has a policy that allows for this
kind of allocation. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>If people think this is viable, I’ll type up a
proposed policy or a proposed modification and send it through, just trying to
get a sense of what the feeling is. If anyone wants more details on
anycast before commenting on the policy, feel free to drop me an email as well.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Andrew Alston <o:p></o:p></p>
<p class=MsoNormal>TENET – Chief Technology Officer<o:p></o:p></p>
</div>
</body>
</html>