<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="font-family: 'Segoe UI',Frutiger,'Frutiger Linotype','Dejavu Sans','Helvetica Neue',Arial,sans-serif; font-size: 14px;">
<div class="hiri-body-wrapper" contenteditable="true">
<div>Hi all,<br>
<br>
I fully agree with the below points made already by Mark and Andrew, which I needn't repeat.<br>
In addition to the issues surrounding the routing of the transfered prefix, it is also important to note that the below scenario would require punching a /26 sized hole in an existing prefix, which would be similarly problematic.<br>
I'd also point out that were the below hypothetical scenario to deteriorate onto litigation, AFRINIC could conceivably be joined as an interested party, thus wasting time and money on legal representation.<br>
For all these reasons, I strongly support limiting transfers to a minimum size of /24.<br>
<br>
Cheers,<br>
<br>
Ben<br>
</div>
</div>
<div class="hiri-signature-wrapper" contenteditable="false">--<br>
Sent from <a href="https://www.hiri.com/">Hiri</a></div>
<div class="hiri-extra" contenteditable="false">
<p>On 2017-07-22 11:35:49+02:00 Andrew Alston wrote:</p>
<blockquote style="padding-left:10px; border-left:1px solid #ccc; margin:0">
<div>
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style type="text/css"><!--
/* 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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I think it goes beyond just pressure on the ISP to accept the /26 – it’s trying to explain to the customer after the fact that despite you accepting it and propagating it (hopefully in
violation of your own policy), that their reachability is extremely limited. <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">End of the day – the customers don’t care that *<b>YOU</b>* are accepting it and that *<b>YOU</b>* are propagating it – what they care about is the fact that THEY can’t get somewhere, and
no matter how many times you explain the situation – you can find customers that simply don’t want to hear and give you tons of grief.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">As a result – I would say – just to avoid headaches for the ISP’s – language to limit this is pretty important<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Andrew<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Mark Tinka <mark.tinka@seacom.mu><br>
<b>Date: </b>Saturday, 22 July 2017 at 17:22<br>
<b>To: </b>Owen DeLong <owen@delong.com><br>
<b>Cc: </b>"rpd@afrinic.net" <rpd@afrinic.net><br>
<b>Subject: </b>Re: [rpd] AFRINIC Board ratifies Policy Proposal AFPUB-2016-V4-003-DRAFT03: IPv4 Resources transfer within the AFRINIC Region<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 21/Jul/17 21:00, Owen DeLong wrote:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="margin-left:1.5pt;margin-top:6.0pt;margin-right:1.5pt;margin-bottom:6.0pt;background-color:null !important;color:null !important">
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Do you honestly believe that if AfriNIC allows long transfers it will magically cause ISPs to start accepting long prefixes into the FIB?<o:p></o:p></p>
</div>
</blockquote>
<p class="MsoNormal">Not magically, but if an ISP obtains a /26 by way of transfer, they could put their service provider under pressure to route it. Of course, that exchange is outside of AFRINIC's scope, and I know any language to manage that could be over-reaching,
but I suppose what I'm trying to do is to remove the opportunity to have the discussion in the first place.<br>
<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-left:1.5pt;margin-top:6.0pt;margin-right:1.5pt;margin-bottom:6.0pt">
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I think it is prudent, but I think because those that might be gullible enough to buy a longer prefix are likely those who don’t really understand the ramifications resulting in some rather awkward subsequent arguments where AfriNIC is
dragged in despite being only the recorder of the transfer and not party to the terms of the sale so to speak.<o:p></o:p></p>
</div>
</blockquote>
<p class="MsoNormal">I have seen strange things in my day. This wouldn't surprise me in the least.<br>
<br>
But in all fairness, I'm not that horny for such text to be in policy. Something like this can easily self-correct if it did happen. But if the text were there, I wouldn't mind either.<br>
<br>
Mark.<br>
<br>
<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</body>
</html>