<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear Jan!<br>
</p>
<p>Thank you for your reply. But you have not answerred my question.<br>
</p>
<p>We are all clear/well aware on the fact that the policy states
(paraphrasing here: resources need to be registered and the
registions need to have contact information).<br>
</p>
<p>We are looking for the DEFINITION of "contact details of the End
User.". This is not directly defined (as far as i can tell) and is
therefore open for interpretation.</p>
<p>Unless i missed something?</p>
<p>Regards<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 1/12/24 09:21, Jan Ingvoldstad
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAEffzkwHhgPWiJn+KTvrtp=Chfcb8ZWE2C2fkSyqO++GiKjOtw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr"><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Jan 12, 2024 at
8:57 AM Sebastian Graf <<a
href="mailto:ripe-lists@sebastian-graf.at" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">ripe-lists@sebastian-graf.at</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear
Jan!<br>
</blockquote>
<div><br>
</div>
<div>Dear Sebastian, thanks for chiming in!</div>
<div> <br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
As mentioned in my previous e-mail: Would you please post
the section of <br>
the policy that you belive has the NCC's interpretation
differ from the <br>
actual wording/language used?<br>
</blockquote>
<div><br>
</div>
<div><a
href="https://www.ripe.net/participate/policies/proposals/2023-04"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.ripe.net/participate/policies/proposals/2023-04</a></div>
<div><br>
</div>
<div>
<h4>6.2 Network Infrastructure and End User Networks</h4>
<div>…</div>
<div><br>
</div>
<div>"When an End User has a network using public address
space this must be registered separately with the contact
details of the End User. Where the End User is an
individual rather than an organisation, the contact
information of the service provider may be substituted for
the End Users."</div>
<div><br>
</div>
<div><br>
</div>
<div>The removal of this text has seen many strange
arguments, such as GDPR (which is already covered by the
text being removed).</div>
<div><br>
</div>
<div><br>
</div>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Because i have yet to find a section that states explicitly
what is <br>
considered valid vs invalid contact information (other than
being out of <br>
date or information that does not provide a contact to the
user in a <br>
timely manner). Or a section that restricts what kind of
data is <br>
permissable for "contact information".</blockquote>
<div><br>
</div>
<div>As I understand it, the RIPE NCC's interpretation, and
the one that Tore leans on, is that the text does not mean
that organisation End User contact details must be
published, even though they are not individual users.</div>
<div><br>
</div>
<div>The argument therefore appears to be that the text "When
an End User has a network using public address space this
must be registered separately with the contact details of
the End User." should be read as "" in the current policy
document, and that changing "When an End User has a network
using public address space this must be registered
separately with the contact details of the End User." to ""
changes nothing in the policy.</div>
<div><br>
</div>
<div><br>
</div>
<div>My stance is that this changes the policy, but that it
changes the policy to be in line with current practice.</div>
<div><br>
</div>
<div>(As a side note, 10-15 years ago, my employer received
quite a lot of flak for NOT publishing contact details for
every single customer that had the use of single, dedicated
IP addresses, as part of web hosting or colocation services,
with rerference to this very policy. How times change.)<br>
</div>
<div><br>
</div>
</div>
<span class="gmail_signature_prefix">-- </span><br>
<div dir="ltr" class="gmail_signature">Jan</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
</body>
</html>