<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Dear all,</p>
<p>I also support RIPE NCC's initiative for dealing with those
ALLOCATED PI/UNSPECIFIED assignments.</p>
<p>By the way, our company holds one of these PIs in KPN's /16. And
as far as we are concerned an annual fee of 50 EUR would be okay,
too.</p>
<p>Kind Regards<br>
Stefan Schiele<br>
</p>
<br>
<div class="moz-cite-prefix">Am 18.08.2016 um 11:36 schrieb
<a class="moz-txt-link-abbreviated" href="mailto:herve.clement@orange.com">herve.clement@orange.com</a>:<br>
</div>
<blockquote
cite="mid:14344_1471513015_57B581B7_14344_1806_1_2AF4C0655C93DD4D9A005252D465A8082F85D8A0@OPEXCLILM21.corporate.adroot.infra.ftgroup"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@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:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Texte brut Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Arial","sans-serif";
color:black;
mso-fareast-language:EN-US;}
span.TextebrutCar
{mso-style-name:"Texte brut Car";
mso-style-priority:99;
mso-style-link:"Texte brut";
font-family:"Arial","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></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]-->
<div class="WordSection1">
<p class="MsoPlainText"><span
style="font-family:"Calibri","sans-serif""
lang="EN-US">Dear all,<o:p></o:p></span></p>
<p class="MsoPlainText"><span
style="font-family:"Calibri","sans-serif""
lang="EN-US"><o:p>�</o:p></span></p>
<p class="MsoPlainText"><span
style="font-family:"Calibri","sans-serif""
lang="EN-US">From my point of view I support this initiative
of the RIPE NCC as it brings more clarity and simplicity
regarding IPv4 resources management.<o:p></o:p></span></p>
<p class="MsoPlainText"><span
style="font-family:"Calibri","sans-serif""
lang="EN-US"><o:p>�</o:p></span></p>
<p class="MsoPlainText"><span
style="font-family:"Calibri","sans-serif""
lang="EN-US">Herv� Cl�ment<o:p></o:p></span></p>
<p class="MsoPlainText"><span
style="font-family:"Calibri","sans-serif""
lang="EN-US">Orange<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p>�</o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:FR">-----Message
d'origine-----<br>
De�: address-policy-wg
[<a class="moz-txt-link-freetext" href="mailto:address-policy-wg-bounces@ripe.net">mailto:address-policy-wg-bounces@ripe.net</a>] De la part de
Ingrid Wijte<br>
Envoy�: vendredi 5 ao�t 2016 15:41<br>
��: Gert Doering; Randy Bush<br>
Cc�: Larisa Yurkina; <a class="moz-txt-link-abbreviated" href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a><br>
Objet�: Re: [address-policy-wg] Update on ALLOCATED
PI/UNSPECIFIED</span></p>
<p class="MsoPlainText"><o:p>�</o:p></p>
<p class="MsoPlainText">Dear colleagues,<o:p></o:p></p>
<p class="MsoPlainText"><o:p>�</o:p></p>
<p class="MsoPlainText"><o:p>�</o:p></p>
<p class="MsoPlainText">>>> Also, it might lead to
deaggs (Markus' case) where a /14 that was
<o:p></o:p></p>
<p class="MsoPlainText">>>> originally "in one LIR"
would be "3x /16, plus some smaller
<o:p></o:p></p>
<p class="MsoPlainText">>>> fragments in the LIR" and
"lots of /24 PI managed by the NCC" now -
<o:p></o:p></p>
<p class="MsoPlainText">>>> so the /14 won't get a ROA,
and he'll have to announce more-specifics.<o:p></o:p></p>
<p class="MsoPlainText">>> lemme see if i get this.� to
have the owner registration correct,
<o:p></o:p></p>
<p class="MsoPlainText">>> some address space will have to
be broken up and owned by multiple
<o:p></o:p></p>
<p class="MsoPlainText">>> IRs, thus fragmenting routing?�
i like correct registration, but the
<o:p></o:p></p>
<p class="MsoPlainText">>> commons has become pretty
polluted.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>�</o:p></p>
<p class="MsoPlainText">The main issue that we (the WG and the
RIPE NCC) are trying to resolve is the lack of clarity around
the status and rights of these assignments. It�s not
necessarily the case that the End User registration is
incorrect. In many cases LIRs have put a lot of effort into
keeping this information up to date.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>�</o:p></p>
<p class="MsoPlainText">If there is a /16 �ALLOCATED
UNSPECIFIED� block that contains "real" Provider Independent
assignments, that /16 would indeed be split in order to carve
out that assignment. The LIR would end up with multiple PA
allocations instead of one /16. The PI resource holder would
be able to decide who their sponsoring LIR should be. It is
possible that they would remain with that same LIR, or they
could move to another sponsoring LIR and take their PI
assignment with them. If the resource holder is an LIR
themselves, the PI assignment could be registered under their
own LIR account.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>�</o:p></p>
<p class="MsoPlainText">This means that route and domain objects
would need to be updated. It�s also relevant to mention that
several LIRs already allow for more specific routes for the
assignments.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>�</o:p></p>
<p class="MsoPlainText">The LIRs will be able to request a new
ROA for their remaining blocks. The sponsoring LIR can request
a ROA on behalf of the PI resource holder, or the PI holder
can do that themselves if they wish.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>�</o:p></p>
<p class="MsoPlainText">I hope this answers your questions.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>�</o:p></p>
<p class="MsoPlainText">Ingrid Wijte<o:p></o:p></p>
<p class="MsoPlainText">RIPE NCC<o:p></o:p></p>
<p class="MsoPlainText"><o:p>�</o:p></p>
<p class="MsoPlainText">> I leave the definite answer to
Ingrid to answer.<o:p></o:p></p>
<p class="MsoPlainText">><o:p>�</o:p></p>
<p class="MsoPlainText">> My understanding of "normal"
NCC<->LIR stockkeeping is that PI is
<o:p></o:p></p>
<p class="MsoPlainText">> never living inside blocks that
"belong" to a given LIR.� So, the LIR
<o:p></o:p></p>
<p class="MsoPlainText">> would never be able to get a ROA
covering PI space.<o:p></o:p></p>
<p class="MsoPlainText">><o:p>�</o:p></p>
<p class="MsoPlainText">> For some of these "old" blocks,
there is a /16 which covers regular
<o:p></o:p></p>
<p class="MsoPlainText">> LIR/PA space, and "not real PI"
space, and the LIR can get a ROA that
<o:p></o:p></p>
<p class="MsoPlainText">> covers their PA space, and also
these "not real PI" blocks (because
<o:p></o:p></p>
<p class="MsoPlainText">> according to the NCC records, the
/16 "belongs" to the LIR).<o:p></o:p></p>
<p class="MsoPlainText">><o:p>�</o:p></p>
<p class="MsoPlainText">>� From an aggregation PoV, this is
ok-ish - but from a routing security
<o:p></o:p></p>
<p class="MsoPlainText">> PoV, I wonder if that's what we
want (the "not real PI" block might be
<o:p></o:p></p>
<p class="MsoPlainText">> routed totally elsewhere now).<o:p></o:p></p>
<p class="MsoPlainText">><o:p>�</o:p></p>
<p class="MsoPlainText">><o:p>�</o:p></p>
<p class="MsoPlainText">>>> So, to answer your
question: for those "swampy PI", it would alter
<o:p></o:p></p>
<p class="MsoPlainText">>>> their rights (contracts
according to 2007-01), costs (50 EUR/year)<o:p></o:p></p>
<p class="MsoPlainText">>> whoops.� that's gonna cause
unhappiness.<o:p></o:p></p>
<p class="MsoPlainText">> Dunno.� We (the RIPE community and
the NCC) rolled out 2007-01 to all
<o:p></o:p></p>
<p class="MsoPlainText">> the other PI holders, and the
amount of unhappiness was not very big.<o:p></o:p></p>
<p class="MsoPlainText">><o:p>�</o:p></p>
<p class="MsoPlainText">> Those cases that I was involved
with my "LIR admin-c" hat on, PI
<o:p></o:p></p>
<p class="MsoPlainText">> holders seemed to be happy to have
a clear contract with a known
<o:p></o:p></p>
<p class="MsoPlainText">> entity (us), and the assurance that
this would ensure that nobody else
<o:p></o:p></p>
<p class="MsoPlainText">> could make claims to their address
space.<o:p></o:p></p>
<p class="MsoPlainText">><o:p>�</o:p></p>
<p class="MsoPlainText">> Gert Doering<o:p></o:p></p>
<p class="MsoPlainText">>��������� -- assorted hats<o:p></o:p></p>
<p class="MsoPlainText"><o:p>�</o:p></p>
<p class="MsoPlainText"><o:p>�</o:p></p>
</div>
<pre>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</pre>
</blockquote>
<br>
</body>
</html>