<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
Dear colleagues, I also see nothing wrong with it.
<div><br>
</div>
<div>A /29 PA allocation is given to a registry for the purpose of re-assigning and use within the policy. </div>
<div><br>
</div>
<div>End user however is expected to need a /48 PI for multihoming as that’s minimum routable. </div>
<div>If someone requires more, I’m more than happy for RIPE to run through checks on any such request, so long as they comply with the policy.</div>
<div><br>
</div>
<div>I’ve seen enough attempts to send SPAM through large quantities of V6 or to try to circumvent other limitations by attempt to use a large number of IPv6 to know that it is abused, and I appreciate every effort to weed illegitimate cases out by the NCC
for the good of the Internet.</div>
<div><br>
<div dir="ltr">
<div><font style="background-color: rgba(255, 255, 255, 0); font-size: 13pt;">With Kind Regards,</font><font style="background-color: rgba(255, 255, 255, 0); font-size: 13pt;"> </font></div>
<span style="background-color: rgba(255, 255, 255, 0);"><font>Dominik Nowacki</font><font> </font><font><br>
</font><font> </font><font><br>
Clouvider Limited is a limited company registered in England and Wales. Registered number: </font><a href="tel:08750969"><u>08750969</u></a><font>. Registered office: </font><a href=""><u>88 Wood Street, London, United Kingdom, EC2V 7RS</u></a><font>. </font></span><font><br>
</font></div>
<div dir="ltr"><br>
On 27 Feb 2019, at 07:30, Carlos Friaças via address-policy-wg <<a href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr"><span></span><br>
<span></span><br>
<span>On Wed, 27 Feb 2019, Kai 'wusel' Siering wrote:</span><br>
<span></span><br>
<blockquote type="cite"><span>Am 26.02.2019 um 23:13 schrieb Cynthia Revström:</span><br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>I have also been informed that this might be a rather unique case in regards to having multiple physical locations requiring PI space.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>It's not ? been there myself, and got really annoyed by the way the NCC entered spanish-inquisition-mode (like asking for physical location of DCs used, IMHO NOTB, and upstream mail contacts, again NOTB). That was pre-GDPR, these
days I'd follow up with "provide legal statement under GDPR that allows you to ask this question, and process any answer". Hrmpft.</span><br>
</blockquote>
<span></span><br>
<span>Hi,</span><br>
<span></span><br>
<span>I fail to understand how a DC location could in any way be related to a GDPR violation.</span><br>
<span></span><br>
<span>I also don't understand how asking for upstream mail contacts (i.e. professional ones, that any ASN should in theory have published, role or individual shouldn't make a difference) can violate GDPR.</span><br>
<span></span><br>
<span>I guess "purpose" for asking is quite easy to understand -- checking if an upstream really exists at that point in time, which may be part of the process.</span><br>
<span></span><br>
<span>Cheers,</span><br>
<span>Carlos</span><br>
<span></span><br>
<span></span><br>
<blockquote type="cite"><span>-kai</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span></blockquote>
</div>
</blockquote>
</div>
</body>
</html>